Net Moto

For:cll Printed on:Thu, Oct 12, 2000 03:37:47 From book:NET01 (OMC02) Issue 18 Rev0 Document:tabs Last saved
on:Thu, Oct 12, 2000 03:37:30 Document:tabs Last saved on:Thu, Oct 12, 2000 03:37:34 Document:tabs Last saved on:Thu, Oct 12, 2000 03:37:34 Document:tabs Last saved on:Thu, Oct 12, 2000 03:37:38 Document:cover Last saved on:Thu, Oct 12, 2000 03:37:30 Document:spine1 Last saved on:Thu, Oct 12, 2000 03:37:30 Document:spine2 Last saved on:Thu, Oct 12, 2000 03:37:30 Document:insidecover-legal Last saved on:Thu, Oct 12, 2000 03:37:30 Document:toc Last saved on:Thu, Oct 12, 2000 03:37:30 Document:Introduction Last saved on:Thu, Oct 12, 2000 03:37:30 Document:Warnings and Cautions Last saved on:Thu, Oct 12, 2000 03:37:30 ( ...)
CHAPTER 1 OVERVIEW
CHAPTER 2 GETTING STARTED
CHAPTER 3 NETWORK MANAGEMENT
CHAPTER 4 MAP AND TREE PROCEDURES
CHAPTER 5 FAULT MANAGEMENT
CHAPTER 6 EVENT MANAGEMENT 1
CHAPTER 7 EVENT MANAGEMENT 2
CHAPTER 8 DEVICE MANAGEMENT
CHAPTER 9 CONFIGURATION MANAGEMENT
CHAPTER 10 LOAD MANAGEMENT
CHAPTER 11 ADMINISTRATION PROCEDURES
CHAPTER 12 PERFORMANCE MANAGEMENT 1
CHAPTER 13 PERFORMANCE MANAGEMENT 2
CHAPTER 14 RECOMMENDED OPERATIONS
CHAPTER 15 RECOMMENDED REPORTS
INDEX
Cellular Infrastructure Group
ISSUE 18 REVISION 0
Software Release 4
NET01 (OMC02) OMC NETWORK OPERATIONS
FOR TRAINING PURPOSES ONLY
ISSUE 18 REVISION 0
Software Release 4
ISSUE 18 REVISION 0 Software Release 4
NET01 (OMC02) OMC Network Operations
E Motorola 1993 2000 All Rights Reserved Printed in the U.K.
EMOTOROLA LTD. 2000
NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY
ISSUE 18 REVISION 0
Copyrights, notices and trademarks

Copyrights
The Motorola products described in this document may include copyrighted Motorola computer programs stored in semiconductor memories or other media. Laws in the United States and other countries preserve for Motorola certain exclusive rights for copyright computer programs, including the exclusive right to copy or reproduce in any form the copyright computer program. Accordingly, any copyright Motorola computer programs contained in the Motorola products described in this document may not be copied or reproduced 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, except for the rights that arise by operation of law in the sale of a product.
Restrictions
The software described in this document is the property of Motorola. It is furnished under a license agreement and may be used and/or disclosed only in accordance with the terms of the agreement. Software and documentation are copyright 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.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola assumes no liability resulting from any inaccuracies or omissions in this document, or from the use of the information obtained herein. Motorola 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 does not assume any liability arising out of the application or use of any product or circuit described herein; neither does it convey license under its patent rights of others.
Trademarks
and MOTOROLA are trademarks of Motorola Inc. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited. Tandem, Integrity, Integrity S2, and Non-Stop-UX are trademarks of Tandem Computers Incorporated. X Window System, X and X11 are trademarks of the Massachusetts Institute of Technology. Looking Glass is a registered trademark of Visix Software Ltd. OSF/Motif is a trademark of the Open Software Foundation. Ethernet is a trademark of the Xerox Corporation. Wingz is a trademark and INFORMIX is a registered trademark of Informix Software Ltd. SUN, SPARC, and SPARCStation are trademarks of Sun Microsystems Computer Corporation. IBM is a registered trademark of International Business Machines Corporation. HP is a registered trademark of Hewlett Packard Inc. EMOTOROLA LTD. 2000
ii
ISSUE 18 REVISION 0
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Important notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cross references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . First aid in case of electric shock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Artificial respiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Burns treatment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reporting safety issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warning labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specific warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RF radiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Laser radiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Lifting equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Do not ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Battery supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Toxic material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Human exposure to radio frequency energy (PCS1900 only) . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximum permitted exposures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximum permitted exposure ceilings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power density measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Beryllium health and safety precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Health issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inhalation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Skin contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Eye contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handling procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disposal methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Product life cycle implications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Caution labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specific cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fibre optics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Static discharge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2000
1 1 1 1 1 2 2 3 3 3 3 4 4 4 5 5 5 5 6 6 6 6 6 6 6 7 7 7 7 8 8 8 8 9 10 10 10 11 11 11 11 12 12 12 12 12 13 13 13 13 13 13
iii
ISSUE 18 REVISION 0
Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Special handling techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Motorola GSM manual set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tandem OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scaleable OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Category number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Catalogue number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ordering manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14 14 14 15 15 15 15 16 16 16 17 17 17
Chapter 1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introducing the Motorola OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definition of OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Naming convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communication with GSM network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R network management functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event/alarm management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The OMC-R in GSM network management architecture . . . . . . . . . . . . . . . . . . . . . . . . . . Network hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The OMC-R configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The System Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SPARCstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optional processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R configuration summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scaleable configuration details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The OMC-R MMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMI user interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GUI interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The OMC-R GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introducing the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The command line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UNIX-based utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The OMC-R in a GSM network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A typical GSM network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RXCDR functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
i
11 11 12 12 13 13 13 13 13 14 14 14 15 15 15 15 15 17 17 18 18 18 18 19 19 19 111 111 112 112 113 113 113
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
BSS and RXCDR configuration (SITES) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RXCDR configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NE device containment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Containment relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CELL resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS hardware relating to traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS software relating to traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DRI/RTF groups - transceiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transceiving functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of RTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Redundancy (within a cell) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CELL configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Links in a GSM network: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Information on links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SITE link requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Physical links PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Physical link requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATH devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R connection to the network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transferring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X.21 connection configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operations and maintenance of a BSS or RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Simplified network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . O&M information flow between OMC-R and NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary of information flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Information flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R system configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Motorola OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical hardware configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communications handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communications software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet switch / multiplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . O&M network traffic capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Peak traffic capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2000
114 114 114 115 115 115 116 116 116 116 117 117 117 117 118 118 118 118 119 119 119 119 120 120 120 120 121 121 121 122 123 123 123 125 125 126 126 126 127 127 127 128 128 129 129 129 130 130
ISSUE 18 REVISION 0
OMC-R System Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to the System Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R GSM application software: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Processor software elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UNIX: Solaris 2.5.1 operating system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tools and applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The OMC-R database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RDBMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database schema: defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applications and utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The CM MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The SPARCstation configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the OMC-R MMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A standalone server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LAN configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMI Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Client Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GUI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Display Processor Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GUI Client - SPARCstation 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Night concentration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The OMC-R MMI: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Graphical User Interface (GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R front panel: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operator name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
131 131 131 134 135 136 136 136 138 138 138 138 138 139 139 139 139 140 141 141 142 142 142 142 143 144 144 145 145 145 146 146 146 147 148 148 149 149 149 149 149
vi
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Using the front panel icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example console messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load Management options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Find . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Xterm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other front panel icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
150 150 150 151 151 152 153 153 154 154 155 155 156 156 157 157 157
Chapter 2 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to Chapter 1 Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using a SPARCstation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitor controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging in to the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The RC.CNFG file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling resync on OMC startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Common Desktop Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CDE desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mouse button utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Right mouse button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Middle mouse button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Left mouse button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restarting/exiting the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restarting the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exiting the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
21 21 21 21 22 23 23 23 23 24 24 24 25 25 25 27 27 27 28 28 29 29 29 210
EMOTOROLA LTD. 2000
vii
ISSUE 18 REVISION 0
Front panel icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Expert desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Find . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other Front panel icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running a remote MMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remotely running the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing an OMC MMI window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using window controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Peripheral controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Window menu buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the text editor xedit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening xedit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing a file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The edit commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
211 211 211 211 212 213 213 214 215 216 217 217 218 218 219 219 220 220 220 221 221 221 222 222 222 223 223 223 224 225 225 225 225 226
Chapter 3 Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The network status summary (NSS) feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How the network status summary feature works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Map process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The EM proxy process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Different maps available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Map modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Consolidated alarm report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Map configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
viii
i
31 31 31 32 32 32 33 34 34 34 35 35 35
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
The map display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Map backgrounds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Map links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . State changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The alarms icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview to alarms icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm display window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The alarm summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of alarm summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How administrative and operational state changes work . . . . . . . . . . . . . . . . . . . . . . . . . . State changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How alarms work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Colours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How maps are configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to the CMMIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Two object groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Graphic objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Graphic objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MapNode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MapLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CommsLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ProxyCell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UserProfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automatically created network objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automatically created map display objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
36 36 36 36 36 37 38 38 38 38 39 39 39 310 310 311 311 312 313 313 313 314 314 314 314 314 315 315 315 316 316 316 316 316 316 316 317 318 318 318 319 319 320 320
Chapter 4 Map and Tree Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Using the map: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shared procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2000
i
41 41 41 41 42
ix
ISSUE 18 REVISION 0
Opening and closing a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Closing a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Map display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Map modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscriber mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Colour legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm severity colours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Moving and expanding nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Expanding a node cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Moving a node on the map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Expanding an NE map node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Node detailed view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contracting a map node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contained devices report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Organizing map nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Organize Nodes function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing map levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Zooming a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Zooming in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Zooming out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging in remotely from a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote login to a NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . No connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resync from a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resync a node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resync logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resync network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . No connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing alarms from a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing alarms from popup menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing OOS devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing network OOS devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing node OOS devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing OOS devices from popup menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
x
43 43 44 45 45 45 46 47 48 49 49 411 411 411 411 411 412 413 413 414 414 415 415 415 416 416 416 416 417 417 417 418 418 418 418 419 419 419 419 419 419 419 420 420 420 420 421 422 422 422 422 423
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Viewing a detailed view from a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing a detailed view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before deleting a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Moving from a map to the navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the navigation tree: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening and closing a navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening the navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Closing the navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Moving levels on a navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Panner and porthole . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the autoclose function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault management from navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Lock a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unlock a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shutdown a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INS a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reset a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reset a Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reassign a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Swap a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Devices supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking device status from the navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying OOS devices from the navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing OOS devices via the popup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing a navigation tree diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
424 424 424 425 426 426 426 427 427 427 428 428 428 429 429 429 430 430 430 430 432 432 432 432 433 433 433 434 434 435 435 435 436 437 438 440 440 440 440 441 441 441 442 442 443 443 443
Chapter 5 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fault management: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definition of fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Principles of FM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FM and the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other FM indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2000
i
51 51 51 51 52 52
xi
ISSUE 18 REVISION 0
Fault management at the NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FM process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Local maintenance terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Two states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administrative states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operational states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm category overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm severity overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Save alarm context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Buffering alarms and state change events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault indication at the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intermittent alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMIC alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OIC alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CERM feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definition of resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . When to perform a resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The resyncState process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The resyncAlarm process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Periodic Supervision of Accessibility (PSA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definition of PSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PSA failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disk usage exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Processor partition full . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handling: defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault handling process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing device states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parent device relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . On-site personnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault handling and remote login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote login interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xii
53 53 53 54 54 54 54 54 55 55 56 56 57 57 58 58 59 59 59 510 510 510 510 510 510 510 511 511 511 511 511 512 512 512 513 513 513 514 514 514 514 515 516 516 516 517 517 517
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Alarm clearing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clearing at the NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clearing at the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm throttling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to alarm throttling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intermittent alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing alarm throttles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault escalation procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
518 518 518 518 519 519 519 519 520 520
Chapter 6 Event Management 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Event and alarm management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Mgmt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Events and alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Primary functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm display window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How event and alarm management works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of EM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The difference between events and alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Events: defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarms: defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting events and alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event/alarm subscription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The subscription process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscription criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Thresholding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blacklist subscriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Events in alarm subscription lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event/alarm display windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Two types of windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Differences between event and alarm windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event/alarm subscription procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscription procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscription functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Alarm display window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reading the display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Consolidated alarm reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to consolidated alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Consolidated alarm report format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2000
i
61 61 61 61 62 63 63 63 63 64 65 65 65 65 66 66 66 66 66 66 67 68 68 68 68 69 69 69 610 610 610 610 611 611 611 611
xiii
ISSUE 18 REVISION 0
Alarm handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The handling process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm handling options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm clearing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The event display window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The event logfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to event logfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logfile creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logfile procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logfile location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Naming convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logfile rollover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The search event log window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event/alarm utilities invoked from the command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of event logfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Utility listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How the event log utilities are used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post-processing of event logfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Online printing of alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
612 612 612 612 612 613 613 613 613 614 614 614 614 614 615 615 616 616 617 618 618 618 618 619 619

Event management overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Events and alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking alarms from the network map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarms: the basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . After detecting an alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening an alarm window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Tools menu in the Alarm and Event windows . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of the Tools menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Tools menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an option in the Tools menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a utility to the CDE menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a utility to the CDE menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Consolidated alarm reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to consolidated alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Consolidated alarm report format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reconfiguration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functional Unit severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OOS devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The View menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Log Search menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xiv
i
71 71 71 72 73 73 73 73 74 75 75 75 75 76 76 77 77 77 78 78 79 710 711
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Using the alarm comment field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Entering an alarm comment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing or adding to an alarm comment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing subscription lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscription lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing available subscription lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening a subscription list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying NSS subscription lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blacklist subscription lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blacklist all events from selected device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blacklist this event from selected device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blacklist selected event from all devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a new subscription list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying a subscription list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Renaming a subscription list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a subscription list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing subscriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing subscriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying subscriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a subscription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding GPRS subscriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm handling: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Personalizing the display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening an alarm/event window from Event Mgmt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening an alarm/event window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault management actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Acknowledging an alarm arrival . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the subscriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handling an alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . When to handle an alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OIC alarm clearing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying events with history or from now for an NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of the Events With History function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of the Events From Now function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying events with history or from now . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Circuit Error Rate Monitor feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RCI alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CIC alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connectivity summary window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2000
712 712 712 714 715 715 715 716 716 717 718 719 720 720 721 722 723 723 724 724 724 725 726 726 729 730 730 730 731 731 731 731 732 733 733 733 734 734 734 735 735 735 735 736 737 737 737 737 738 738 738 740 741
xv
ISSUE 18 REVISION 0
Throttling alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing alarm throttles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the alarm throttle time period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting an alarm throttle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intermittent alarm throttling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging of events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Searching of event log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loading event logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sort criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the sort criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Filtering event logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reloading event logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying current active event logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing event log search window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling event logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling event logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creation of auto initiation files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AutoInit.CNFG template files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an AutoInit.CNFG file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the event logging utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using cel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using qfes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using ces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Input parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ces example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ces example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using sld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Output format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . sld example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . sld example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using dpr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to cron . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up a cron job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC alarm paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents of a page message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Truncated severity types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Paging performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Paging: how it works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Content of the paging configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Paging error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the paging modem at the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the contents of the pager configuration file . . . . . . . . . . . . . . . . . . . . . . . . Starting paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xvi
742 742 742 743 744 744 745 745 745 746 747 748 749 750 750 753 754 755 756 757 758 758 758 759 760 760 760 760 762 763 763 763 764 764 765 766 766 767 768 769 770 770 771 771 771 771 772 772 772 773 774 775 775 775
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Sending alarms to an e-mail address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description of e-mailing alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite: a Tools menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an e-mail alarm option in the Tools menu . . . . . . . . . . . . . . . . . . . . . . . . .
776 776 776 776
Chapter 8 Device Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Device management from the map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Locking a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unlocking a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INS a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resetting a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contained Devices window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resetting an NE from the command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC/RXCDR reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finding a Network Element, Site or Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Find feature overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Locating an NE, Site or Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Locating the parent of a Site or Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Examples of using find . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of the Call Trace function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to call trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call trace statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description of the Call Trace windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trace View window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Trace Detailed View window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Invoked Instances window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Abort Trace on Call window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trace Record View window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Call Trace function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a call trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing a call trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing call trace details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing trace records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Aborting a trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deactivating an active trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Tools menu in the Trace View window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of a Tools menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Tools menu in the Trace View window . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an option in the Trace View Tools menu . . . . . . . . . . . . . . . . . . . . . . . . . EAS alarm objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to Remote login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Three interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple Rlogin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging in remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2000
i
81 81 81 81 82 82 84 86 86 87 87 88 88 89 810 810 812 815 815 815 816 816 818 820 820 821 822 822 822 822 823 825 825 826 827 827 827 827 828 828 828 829 829 829 829 830
xvii
ISSUE 18 REVISION 0
Using TTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Beginning a TTY session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing security levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security level 1 activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security level 2 activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Change level procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminating a TTY session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Batch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Batch access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Beginning a BATCH session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ending a BATCH session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating command files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using batch from the command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The batch_rlogin utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Associated environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Associated parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Batch login exit codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exit codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A batch_rlogin example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BatchInput file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BatchOutput file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forms session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Worksheet cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying circuit status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying channel status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling Forms logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling Forms logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exiting a Forms session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
831 831 831 831 832 833 834 835 835 836 836 836 837 837 838 839 839 839 841 841 841 841 841 842 842 842 844 844 844 844 845 846 846 846 846 848 849 849 849
Chapter 9 Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of Configuration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Navigation form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Detailed views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How configuration management works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration management implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operational database parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The CM MIB function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changes to the network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration management from the OMC GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xviii
i
91 91 91 91 91 92 93 93 93 94 94 94 95
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Network configuration at the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description of network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definition of Navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uses of the Navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Detailed views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definition of detailed views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical detailed view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definition of audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC areas changed by audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How audit works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Periodic auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Admin Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of EAS alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EAS alarm form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software load management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of software load management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NE and OMC software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements of software load management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load Mgmt option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software inventory window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software load installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install Load dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a software load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Archiving a software load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NE software loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The NESoftware detailed view form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conventional download to a new NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CSFP database setup (for download) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Criteria for CSFP download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The activate_db script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CSFP options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to CSFP options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CSFP status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure CSFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download CSFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Swap CodeLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unconfigure CSFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download to CSFPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A two stage process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Criteria and guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CSFP download process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Aborting download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2000
96 96 98 98 98 99 910 910 910 911 912 912 912 913 914 914 915 915 915 916 916 916 916 917 918 918 919 920 920 921 921 921 922 924 924 925 926 926 926 926 927 927 927 927 927 928 928 928 929 929 929 929 930 930 930
xix
ISSUE 18 REVISION 0
Fallback to backup database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of backup databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The fallback_db utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NE database management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operational database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NE database management utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load management utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DataGen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to DataGen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DataGen configuration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Off-Line MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NE configuration changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network configuration status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X.121 DTE addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event and alarm subscription lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet switch / multiplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC - BSS remote login interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NE database upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TTY interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The batch_rlogin utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The batch user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The logfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command line example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command line example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
931 931 931 931 932 932 932 932 933 933 934 934 934 935 935 936 936 937 937 938 938 938 938 938 939 939 939 940 941 941 942 942 943 943
Chapter 10 Load Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Load management overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to Load management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of Downloading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software load information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Load management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selecting new software loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying upload/download status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling/disabling the download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling/ disabling downloads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xx
i
101 101 101 102 103 103 104 104 104 105 106 107 107 107
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Installing and removing software loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing a software load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing a software load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying NE database information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loading an NE database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NE database utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loading a database from tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loading a database from DataGen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loading a database from the off-line MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example of off-line MIB install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loading from a specified directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loading an existing database for CSFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating for normal /conventional download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating for CSFP download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downloading an NE database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conventional download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NE software detailed view form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete load flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conventional (live) downloading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking BSSspecific files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resetting a NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post-download checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Falling back to a previous live NE database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CSFP download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure CSFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downloading for CSFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Swapping a CSFP load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unconfigure CSFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CSFP Status form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Abort CSFP download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fallback to previous CSFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Aborting loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Aborting a bootload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uploading an NE database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uploading an object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Confirming compressed database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2000
108 108 108 1010 1011 1011 1011 1012 1013 1013 1013 1014 1015 1016 1018 1019 1020 1022 1022 1022 1024 1025 1025 1025 1026 1026 1026 1028 1028 1028 1029 1029 1030 1031 1032 1032 1032 1033 1034 1034 1035 1035 1036 1037 1037 1038 1038 1038 1040
xxi
ISSUE 18 REVISION 0
Chapter 11 Administration Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Administration: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM scheduled reports and logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening a user profile list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing a user profile list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing a user profile detailed view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing the user profile list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview and recommendations for audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to audit function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of audit procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audit functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended audit use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduled audits queuing support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Number of operations run at a given time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audit scenarios and NE basis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audit logs and expired logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Auditing a network via the navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to auditing a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Auditing a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Auditing a BSS/RXCDR via the navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to BSS/RXCDR auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Auditing a BSS/RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling an audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a scheduled audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying a scheduled audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing a list of scheduled audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a scheduled audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing audit logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing an audit log list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing an audit log list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Aborting an audit in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing an audit inconsistency report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing an inconsistency report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating database with inconsistencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting audit logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling an FM resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction FM resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a scheduled resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying a scheduled resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing resync schedule list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a scheduled resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxii
i
111 111 111 112 112 112 113 114 115 115 116 116 116 117 118 119 119 1110 1110 1111 1111 1112 1114 1114 1114 1115 1115 1116 1120 1121 1121 1122 1122 1123 1123 1125 1126 1126 1127 1129 1129 1129 1129 1130 1134 1136 1136
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Resynchronizing logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing a resync log list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing a resync log list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Aborting a resync in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resync report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing a resync report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing a resync report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a resync log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1137 1137 1137 1138 1139 1139 1139 1140 1141
Chapter 12 Performance Management 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of Performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistics: definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance management data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of PM data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the PM GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The selections window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening a stored selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Report options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running a new report from the PM GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reset file indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running stored reports from the command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running a report from the command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running a delimited report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running a scheduled report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing a report log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing PM reports on the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM on the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the OMC on the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM reports on the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Custom Statistics Manipulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of the window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a new custom statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
121 121 121 122 122 122 124 126 127 127 128 129 1210 1212 1212 1212 1212 1213 1213 1213 1214 1214 1215 1215 1215 1215 1217 1217 1217

Performance management overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to Performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM from the front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM from the Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM from the map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM from Contained Devices form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM Report Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM report logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2000
i
131 131 131 131 131 132 132 132 133 133 133 133 134
xxiii
ISSUE 18 REVISION 0
Statistics management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistics management menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying enabled statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistics intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying current intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the alarm threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Status window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clear Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running a new report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to Running a new report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running a new report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network elements and statistics menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Searching list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Report options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Start/end dates and times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sort criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Filter criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data scale factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Axis scale range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Saving reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delimited reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delimited report format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delimited report example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Display menu on PM reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reset file indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-numerical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-numerical data symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Custom Statistics Manipulation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a new custom statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Renaming a custom statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a custom statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Filtering custom statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Searching a custom statistic list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stored selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening a stored selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running a stored selection from the PM window . . . . . . . . . . . . . . . . . . . . . . . . . . . Running a stored selection from the selections window . . . . . . . . . . . . . . . . . . . . . Saving a stored selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure for saving a stored selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a stored selection to shortlist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxiv
135 135 135 136 137 139 139 1311 1311 1313 1313 1314 1315 1315 1315 1319 1320 1321 1322 1323 1325 1326 1327 1329 1330 1331 1332 1332 1332 1333 1334 1335 1335 1335 1336 1336 1338 1338 1338 1340 1341 1342 1343 1344 1344 1344 1346 1346 1346 1347 1348
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Completed reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening a completed report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a completed report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Renaming completed reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reloading the completed report list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Searching from a completed report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing PM reports on the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stored selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying graphical output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying the display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Days . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Saving graphical reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM report scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling a report from Selection Name window . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling a report from Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying a report schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a report schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing a report list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing a schedule detailed view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM reports logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing a PM reports logs list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing an PM reports list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing a PM report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a PM report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running a PM report from the command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running new PM reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stored selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Completed report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance management troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to PM troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMGUI.CFG file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM_RESYNCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Informix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FPOMCAUDIT file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1349 1349 1349 1350 1351 1352 1353 1354 1354 1354 1356 1356 1356 1356 1357 1357 1357 1358 1359 1360 1361 1362 1363 1363 1363 1364 1367 1368 1368 1368 1369 1369 1369 1370 1370 1371 1372 1372 1374 1374 1375 1375 1375 1377 1378 1379 1379 1379
Chapter 14 Recommended Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to recommended operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of chapter structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2000
i
141 141 142 142
xxv
ISSUE 18 REVISION 0
Recommended methods of fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of fault management facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Methods of fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault management based on historical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Real-time fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of fault management setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating multiple CDE workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up the display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up users for FM activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up alarm subscriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up a blacklist subscription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up alarm paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up e-mail alarm facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up and maintaining OMC maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Investigating alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm context sensitive help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm help installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optimization of process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Review event history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of logging faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ways of logging faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Keeping manual logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS command logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command logging enable/disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Response logging enable/disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set the command logging variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documenting network changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Change request forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Implementing the change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Escalating fault management problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Escalating problems internally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Escalating problems to Motorola . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended performance management tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of recommended performance management tasks . . . . . . . . . . . . . . . . Examining key statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing PM reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generating a report from the command line using Applix . . . . . . . . . . . . . . . . . . . Enabling and disabling neighbour cell statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring MTL connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hints for generating PM reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxvi
143 143 143 143 144 146 146 146 147 147 149 149 149 149 1410 1413 1413 1413 1414 1414 1415 1415 1416 1417 1417 1418 1418 1418 1421 1421 1422 1422 1422 1423 1423 1423 1423 1424 1424 1424 1425 1425 1426 1427 1427 1427 1428 1429 1430
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Cleaning up PM data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cleaning up PM statistics data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cleaning up PM device naming data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manually parsing PM statistics files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resynchronizing PM databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definition of PM Resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automatic PM Resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manually resynchronizing PM databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking enabled statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure for checking PM enabled stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Motorola PM and FM tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of Motorota Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance Management tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Gathering Tool (DGT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Health Analyst (NHA) tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Analysis Tool (CAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Counting Tool (ECT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Trace Product (CTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . site_outage utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . dri_status utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . rtf_status utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking ISG 6525 packet switch health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking ISG 6525 packet switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring ISG packet switch statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CPU utilization threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing packet switch configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Route selection table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Port record list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking ISG 6560 MPRouter health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking ISG 6560 MPRouter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring ISG 6560 MPRouter statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CPU utilization threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DTE address mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . At the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . At the OMCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting the OML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Possible faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load Management configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to Load managment configuration tasks . . . . . . . . . . . . . . . . . . . . . . . Backup BSS/RXCDR configuration database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deploy new BSS/RXCDR databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install new BSS/RXCDR database onto OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure a CSFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initiate download to BSS/RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enable/Disable database downloads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check all sites and devices after BSC/RXCDR reset . . . . . . . . . . . . . . . . . . . . . . . Unconfigure a CSFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fallback to old database at BSC/RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling an upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2000
1431 1431 1431 1433 1434 1434 1434 1434 1436 1436 1437 1439 1439 1440 1440 1440 1441 1441 1441 1441 1441 1442 1443 1443 1444 1444 1444 1445 1448 1449 1453 1454 1455 1455 1455 1456 1460 1461 1461 1461 1461 1463 1463 1464 1466 1466 1467 1468 1469 1470 1471 1472 1472 1473 1473 1474
xxvii
ISSUE 18 REVISION 0
Overview of regular procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hourly procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended procedure list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chase actions on Critical Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chase actions on Major Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Daily procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended procedure list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Analysis of PM statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Examination of event logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Weekly procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended procedure list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NE database checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical database directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uploading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup NE directory format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Weekly meeting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Weekly system procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking OMC version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check software version at a NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check system after changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backups and archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Routine administration procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedures described . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manually initiate alarm and state resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schedule alarm and state resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schedule configuration audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check alarm and state resync logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check configuration audit logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking LAN connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the ping utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example of output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1476 1476 1477 1477 1477 1477 1478 1478 1478 1479 1479 1480 1480 1480 1481 1481 1482 1482 1483 1483 1483 1484 1484 1485 1486 1486 1486 1487 1487 1488 1488 1489 1489 1489
Chapter 15 Recommended Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview of recommended reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of recommended reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance management (statistical) reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of performance management (statistical) reports . . . . . . . . . . . . . . . . . . . . Cell activity reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Paging reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Quality of service reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network status reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link and channel usage reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH performance reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Daily performance management reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Report Option fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to using the Report Options fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up a daily report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up a daily peak hour report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up a weekly historical trending graph report . . . . . . . . . . . . . . . . . . . . . . . . Setting up a delimited report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxviii
i
151 151 152 152 152 153 153 153 154 154 154 155 156 156 156 157 157 158
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Fault management reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of fault management reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
159 159
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I1
EMOTOROLA LTD. 2000
xxix
ISSUE 18 REVISION 0
xxx
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
General information
General information
Important notice
If this manual was obtained when you attended a Motorola training course, it will not be updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it was supplied under normal operational circumstances, to support a major software release, then corrections will be supplied automatically by Motorola in the form of General Manual Revisions (GMRs).
Purpose
Motorola Global System for Mobile Communications (GSM) Technical Education manuals are intended to support the delivery of Technical Education only and are not intended to replace the use of Customer Product Documentation. WARNING Failure to comply with Motorolas operation, installation and maintenance instructions may, in exceptional circumstances, lead to serious injury or death. These manuals are not intended to replace the system and equipment training offered by Motorola, although they can be used to supplement and enhance the knowledge gained through such training.
About this manual

This manual comprises of chapters taken from 68P02901W14-G (GMR01) and 68p02901W31-G (GMR01).
Objectives
On completion of this course the student will be able to: S S S S S S S S Understand the concepts of operating a network of BSSs and remote transcoders using an OMC-R. Use the OMC GUI to manage the processing of network element events/alarms. Use the OMC GUI to monitor the performance management data of network elements and generate reports. Understand the principles of GSM fault management and acquire practical experience of suing a Motorola OMC-R to perform fault management tasks. Use the OMC GUI to perform Load Management tasks. Understand the procedures required for OMC operating staff. Apply knowledge attained on the course to troubleshoot the system. Use the operating procedures detailed in the GSM manual Operating Information: GSM System Operation GSM-100-201.
EMOTOROLA LTD. 2000
General information
ISSUE 18 REVISION 0
Cross references
Throughout this manual, cross references are made to the chapter numbers and section names. The section name cross references are printed bold in text. This manual is divided into uniquely identified and numbered chapters that, in turn, 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.
Text conventions
The following conventions are used in the Motorola GSM manuals to represent keyboard input text, screen output text and special key sequences.
Input
Characters typed in at the keyboard are shown like this.
Output
Messages, prompts, file listings, directories, utilities, and environmental variables that appear on the screen are shown like this.
Special key sequences

Special key sequences are represented as follows: CTRL-c ALT-f | CR or RETURN Press the Control 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 (Enter) key. The Return key is identified with the symbol on both the X terminal and the SPARCstation keyboards. The SPARCstation keyboard Return key is also identified with the word Return.
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
First aid in case of electric shock
First aid in case of electric shock

Warning
WARNING Do not touch the victim with your bare hands until the electric circuit is broken. Switch off. If this is not possible, protect yourself with dry insulating material and pull or push the victim clear of the conductor.
Artificial respiration
In the event of an electric shock it may be necessary to carry out artificial respiration. Send for medical assistance immediately.
Burns treatment
If the patient is also suffering from burns, then, without hindrance to artificial respiration, carry out the following: 1. 2. 3. Do not attempt to remove clothing adhering to the burn. If help is available, or as soon as artificial respiration is no longer required, cover the wound with a dry dressing. Do not apply oil or grease in any form.
EMOTOROLA LTD. 2000
Reporting safety issues
ISSUE 18 REVISION 0
Reporting safety issues

Introduction
Whenever a safety issue arises, carry out the following procedure in all instances. Ensure that all site personnel are familiar with this procedure.
Procedure
Whenever a safety issue arises: 1. 2. 3. 4. Make the equipment concerned safe, for example, by removing power. Make no further attempt to tamper with the equipment. Report the problem directly to GSM MCSC +44 (0)1793 430040 (telephone) and follow up with a written report by fax +44 (0)1793 430987 (fax). Collect evidence from the equipment under the guidance of the MCSC.
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Warnings and cautions
Warnings and cautions

Introduction
The following describes how warnings and cautions are used in this manual and in all manuals of the Motorola GSM manual set.
Warnings
Definition
A warning is used to alert the reader to possible hazards that could cause loss of life, physical injury, or ill health. This includes hazards introduced during maintenance, for example, the use of adhesives and solvents, as well as those inherent in the equipment.
Example and format

WARNING Do not look directly into fibre optic cables or optical data in/out connectors. Laser radiation can come from either the data in/out connectors or unterminated fibre optic cables connected to data in/out connectors.
Cautions
Definition
A caution means that there is a possibility of damage to systems, or individual items of equipment within a system. However, this presents no danger to personnel.
Example and format

CAUTION Do not use test equipment that is beyond its calibration due date when testing Motorola base stations.
EMOTOROLA LTD. 2000
General warnings
ISSUE 18 REVISION 0
General warnings
Introduction
Observe the following warnings during all phases of operation, installation and maintenance of the equipment described in the Motorola GSM manuals. Failure to comply with these warnings, or with specific warnings elsewhere in the Motorola GSM manuals, violates safety standards of design, manufacture and intended use of the equipment. Motorola assumes no liability for the customers failure to comply with these requirements.
Warning labels
Personnel working with or operating Motorola equipment must comply with any warning labels fitted to the equipment. Warning labels must not be removed, painted over or obscured in any way.
Specific warnings
Warnings particularly applicable to the equipment are positioned on the equipment and within the text of this manual. These must be observed by all personnel at all times when working with the equipment, as must any other warnings given in text, on the illustrations and on the equipment.
High voltage
Certain Motorola equipment operates from a dangerous high voltage of 230 V ac single phase or 415 V ac three phase mains which is potentially lethal. Therefore, the areas where the ac mains power is present must not be approached until the warnings and cautions in the text and on the equipment have been complied with. To achieve isolation of the equipment from the ac supply, the mains input isolator must be set to off and locked. Within the United Kingdom (UK) regard must be paid to the requirements of the Electricity at Work Regulations 1989. There may also be specific country legislation which need to be complied with, depending on where the equipment is used.
RF radiation
High RF potentials and electromagnetic fields are present in the base station equipment when in operation. Ensure that all transmitters are switched off when any antenna connections have to be changed. Do not key transmitters connected to unterminated cavities or feeders. Refer to the following standards: S S ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3kHz to 300GHz. CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High Frequency (10kHz to 300GHz).
Laser radiation
Do not look directly into fibre optic cables or optical data in/out connectors. Laser radiation can come from either the data in/out connectors or unterminated fibre optic cables connected to data in/out connectors.
6
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
General warnings
Lifting equipment
When dismantling heavy assemblies, or removing or replacing equipment, the competent responsible person must ensure that adequate lifting facilities are available. Where provided, lifting frames must be used for these operations. When equipments have to be manhandled, reference must be made to the Manual Handling of Loads Regulations 1992 (UK) or to the relevant manual handling of loads legislation for the country in which the equipment is used.
Do not ...
... substitute parts or modify equipment. Because of the danger of introducing additional hazards, do not install substitute parts or perform any unauthorized modification of equipment. Contact Motorola if in doubt to ensure that safety features are maintained.
Battery supplies
Do not wear earth straps when working with standby battery supplies.
Toxic material
Certain Motorola equipment incorporates components containing the highly toxic material Beryllium or its oxide Beryllia or both. These materials are especially hazardous if: S S S Beryllium materials are absorbed into the body tissues through the skin, mouth, or a wound. The dust created by breakage of Beryllia is inhaled. Toxic fumes are inhaled from Beryllium or Beryllia involved in a fire.
See the Beryllium health and safety precautions section for further information.
EMOTOROLA LTD. 2000
Human exposure to radio frequency energy (PCS1900 only)
ISSUE 18 REVISION 0

Introduction
This equipment is designed to generate and radiate radio frequency (RF) energy. It should be installed and maintained only by trained technicians. Licensees of the Federal Communications Commission (FCC) using this equipment are responsible for insuring that its installation and operation comply with FCC regulations designed to limit human exposure to RF radiation in accordance with the American National Standards Institute IEEE Standard C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3kHz to 300GHz.
Definitions
This standard establishes two sets of maximum permitted exposure limits, one for controlled environments and another, that allows less exposure, for uncontrolled environments. These terms are defined by the standard, as follows:
Uncontrolled environment
Uncontrolled environments are locations where there is the exposure of individuals who have no knowledge or control of their exposure. The exposures may occur in living quarters or workplaces where there are no expectations that the exposure levels may exceed those shown for uncontrolled environments in the table of maximum permitted exposure ceilings.
Controlled environment
Controlled environments are locations where there is exposure that may be incurred by persons who are aware of the potential for exposure as a concomitant of employment, by other cognizant persons, or as the incidental result of transient passage through areas where analysis shows the exposure levels may be above those shown for uncontrolled environments but do not exceed the values shown for controlled environments in the table of maximum permitted exposure ceilings.
Maximum permitted exposures

The maximum permitted exposures prescribed by the standard are set in terms of different parameters of effects, depending on the frequency generated by the equipment in question. At the frequency range of this Personal Communication System equipment, 1930-1970MHz, the maximum permitted exposure levels are set in terms of power density, whose definition and relationship to electric field and magnetic field strengths are described by the standard as follows:
Power density (S)

Power per unit area normal to the direction of propagation, usually expressed in units of watts per square metre (W/m2) or, for convenience, units such as milliwatts per square centimetre (mW/cm2). For plane waves, power density, electric field strength (E) and magnetic field strength (H) are related by the impedance of free space, 377 ohms. In particular,
2 S + E + 377 377
H2
where E and H are expressed in units of V/m and A/m, respectively, and S in units of W/m 2. Although many survey instruments indicate power density units, the actual quantities measured are E or E2 or H or H2.
8
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Maximum permitted exposure ceilings

Within the frequency range, the maximum permitted exposure ceiling for uncontrolled environments is a power density (mW/cm2) that equals f/1500, where f is the frequency expressed in MHz, and measurements are averaged over a period of 30 minutes. The maximum permitted exposure ceiling for controlled environments, also expressed in mW/cm 2, is f/300 where measurements are averaged over 6 minutes. Applying these principles to the minimum and maximum frequencies for which this equipment is intended to be used yields the following maximum permitted exposure levels: Uncontrolled Environment 1930MHz Ceiling 1970MHz Controlled Environment 1930MHz 1970MHz
1.287mW/cm 2 1.313mW/cm 2 6.433mW/cm 2 6.567mW/cm 2
If you plan to operate the equipment at more than one frequency, compliance should be assured at the frequency which produces the lowest exposure ceiling (among the frequencies at which operation will occur). Licensees must be able to certify to the FCC that their facilities meet the above ceilings. Some lower power PCS devices, 100 milliwatts or less, are excluded from demonstrating compliance, but this equipment operates at power levels orders of magnitude higher, and the exclusion is not applicable. Whether a given installation meets the maximum permitted exposure ceilings depends, in part, upon antenna type, antenna placement and the output power to which this equipment is adjusted. The following example sets forth the distances from the antenna to which access should be prevented in order to comply with the uncontrolled and controlled environment exposure limits as set forth in the ANSI IEEE standards and computed above.
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Example calculation
For a base station with the following characteristics, what is the minimum distance from the antenna necessary to meet the requirements of an uncontrolled environment? Transmit frequency Base station cabinet output power, P Antenna feeder cable loss, CL Antenna input power Pin Antenna gain, G Using the following relationship: G + 4p r W Pin
2
1930MHz +39.0 dBm (8 watts) 2.0dB PCL = +39.02.0 = +37.0dB (5watts) 16.4dBi (43.65)
Where W is the maximum permissible power density in W/m2 and r is the safe distance from the antenna in metres, the desired distance can be calculated as follows: r+
GPin + 43.65 5 + 1.16m 4p W 4p 12.87
where W = 12.87 W/m2 was obtained from table listed above and converting from mW/cm 2 to W/m2. NOTE The above result applies only in the direction of maximum radiation of the antenna. Actual installations may employ antennas that have defined radiation patterns and gains that differ from the example set forth above. The distances calculated can vary depending on the actual antenna pattern and gain.
Power density measurements

While installation calculations such as the above are useful and essential in planning and design, validation that the operating facility using this equipment actually complies will require making power density measurements. For information on measuring RF fields for determining compliance with ANSI IEEE C95.1-1991, see IEEE Recommended Practice for the Measure of Potentially Hazardous Electromagnetic Fields - RF and Microwave, IEEE Std C95.3-1991. Copies of IEEE C95.1-1991 and IEEE C95.3-1991 may be purchased from the Institute of Electrical and Electronics Engineers, Inc., Attn: Publication Sales, 445 Hoes Lane, P.O. Box 1331, Piscattaway, NJ 08855-1331, (800) 678-IEEE or from ANSI, (212) 642-4900. Persons responsible for installation of this equipment are urged to consult these standards in determining whether a given installation complies with the applicable limits.
Other equipment
Whether a given installation meets ANSI standards for human exposure to radio frequency radiation may depend not only on this equipment but also on whether the environments being assessed are being affected by radio frequency fields from other equipment, the effects of which may add to the level of exposure. Accordingly, the overall exposure may be affected by radio frequency generating facilities that exist at the time the licensees equipment is being installed or even by equipment installed later. Therefore, the effects of any such facilities must be considered in site selection and in determining whether a particular installation meets the FCC requirements.
10
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Beryllium health and safety precautions

Introduction
Beryllium (Be), is a hard silver/white metal. It is stable in air, but burns brilliantly in Oxygen. With the exception of the naturally occurring Beryl ore (Beryllium Silicate), all Beryllium compounds and Beryllium metal are potentially highly toxic.
Health issues
Beryllium Oxide is used within some components as an electrical insulator. Captive within the component it presents no health risk whatsoever. However, if the component should be broken open and the Beryllium Oxide, which is in the form of dust, released, there exists the potential for harm.
Inhalation
Inhalation of Beryllium Oxide can lead to a condition known as Berylliosis, the symptoms of Berylliosis are similar to Pneumonia and may be identified by all or any of the following: Mild poisoning causes fever, shortness of breath, and a cough that produces yellow/green sputum, or occasionally bloodstained sputum. Inflammation of the mucous membranes of the nose, throat, and chest with discomfort, possibly pain, and difficulty with swallowing and breathing. Severe poisoning causes chest pain and wheezing which may progress to severe shortness of breath due to congestion of the lungs. Incubation period for lung symptoms is 220 days. Exposure to moderately high concentrations of Beryllium in air may produce a very serious condition of the lungs. The injured person may become blue, feverish with rapid breathing and raised pulse rate. Recovery is usual but may take several months. There have been deaths in the acute stage. Chronic response. This condition is more truly a general one although the lungs are mainly affected. There may be lesions in the kidneys and the skin. Certain features support the view that the condition is allergic. There is no relationship between the degree of exposure and the severity of response and there is usually a time lag of up to 10 years between exposure and the onset of the illness. Both sexes are equally susceptible. The onset of the illness is insidious but only a small number of exposed persons develop this reaction.
First aid
Seek immediate medical assistance. The casualty should be removed immediately from the exposure area and placed in a fresh air environment with breathing supported with Oxygen where required. Any contaminated clothing should be removed. The casualty should be kept warm and at rest until medical aid arrives.
EMOTOROLA LTD. 2000
11
ISSUE 18 REVISION 0
Skin contact
Possible irritation and redness at the contact area. Persistent itching and blister formations can occur which usually resolve on removal from exposure.
First aid
Wash area thoroughly with soap and water. If skin is broken seek immediate medical assistance.
Eye contact
May cause severe irritation, redness and swelling of eyelid(s) and inflammation of the mucous membranes of the eyes.
First aid
Flush eyes with running water for at least 15 minutes. Seek medical assistance as soon as possible.
Handling procedures
Removal of components from printed circuit boards (PCBs) is to take place only at Motorola approved repair centres. The removal station will be equipped with extraction equipment and all other protective equipment necessary for the safe removal of components containing Beryllium Oxide. If during removal a component is accidently opened, the Beryllium Oxide dust is to be wetted into a paste and put into a container with a spatula or similar tool. The spatula/tool used to collect the paste is also to be placed in the container. The container is then to be sealed and labelled. A suitable respirator is to be worn at all times during this operation. Components which are successfully removed are to be placed in a separate bag, sealed and labelled.
Disposal methods
Beryllium Oxide or components containing Beryllium Oxide are to be treated as hazardous waste. All components must be removed where possible from boards and put into sealed bags labelled Beryllium Oxide components. These bags must be given to the safety and environmental adviser for disposal. Under no circumstances are boards or components containing Beryllium Oxide to be put into the general waste skips or incinerated.
Product life cycle implications

Motorola GSM and analogue equipment includes components containing Beryllium Oxide (identified in text as appropriate and indicated by warning labels on the equipment). These components require specific disposal measures as indicated in the preceding (Disposal methods) paragraph. Motorola will arrange for the disposal of all such hazardous waste as part of its Total Customer Satisfaction philosophy and will arrange for the most environmentally friendly disposal available at that time.
12
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
General cautions
General cautions
Introduction
Observe the following cautions during operation, installation and maintenance of the equipment described in the Motorola GSM manuals. Failure to comply with these cautions or with specific cautions elsewhere in the Motorola GSM manuals may result in damage to the equipment. Motorola assumes no liability for the customers failure to comply with these requirements.
Caution labels
Personnel working with or operating Motorola equipment must comply with any caution labels fitted to the equipment. Caution labels must not be removed, painted over or obscured in any way.
Specific cautions
Cautions particularly applicable to the equipment are positioned within the text of this manual. These must be observed by all personnel at all times when working with the equipment, as must any other cautions given in text, on the illustrations and on the equipment.
Fibre optics
The bending radius of all fibre optic cables must not be less than 30 mm.
Static discharge
Motorola equipment contains CMOS devices that are vulnerable to static discharge. Although the damage caused by static discharge may not be immediately apparent, CMOS devices may be damaged in the long term due to static discharge caused by mishandling. Wear an approved earth strap when adjusting or handling digital boards. See Devices sensitive to static for further information.
EMOTOROLA LTD. 2000
13
Devices sensitive to static
ISSUE 18 REVISION 0
Devices sensitive to static

Introduction
Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer of insulation that is susceptible to damage from electrostatic charge. Such a charge applied to the leads of the device could cause irreparable damage. These charges can be built up on nylon overalls, by friction, by pushing the hands into high insulation packing material or by use of unearthed soldering irons. MOS devices are normally despatched from the manufacturers with the leads shorted together, for example, by metal foil eyelets, wire strapping, or by inserting the leads into conductive plastic foam. Provided the leads are shorted it is safe to handle the device.
Special handling techniques

In the event of one of these devices having to be replaced observe the following precautions when handling the replacement: S S S S S S Always wear an earth strap which must be connected to the electrostatic point (ESP) on the equipment. Leave the short circuit on the leads until the last moment. It may be necessary to replace the conductive foam by a piece of wire to enable the device to be fitted. Do not wear outer clothing made of nylon or similar man made material. A cotton overall is preferable. If possible work on an earthed metal surface. Wipe insulated plastic work surfaces with an anti-static cloth before starting the operation. All metal tools should be used and when not in use they should be placed on an earthed surface. Take care when removing components connected to electrostatic sensitive devices. These components may be providing protection to the device.
When mounted onto printed circuit boards (PCBs), MOS devices are normally less susceptible to electrostatic damage. However PCBs should be handled with care, preferably by their edges and not by their tracks and pins, they should be transferred directly from their packing to the equipment (or the other way around) and never left exposed on the workbench.
14
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Motorola GSM manual set

Introduction
The following manuals provide the information needed to operate, install and maintain the Motorola GSM equipment.
Generic manuals
The following are the generic manuals in the GSM manual set, these manuals are release dependent:
Category number
GSM-100-101 GSM-100-201 GSM-100-311 GSM-100-313 GSM-100-320 GSM-100-321 GSM-100-403 GSM-100-423 GSM-100-501 GSM-100-521 GSM-100-523 GSM-100-503 GSM-100-721
Name
System Information: General Technical Description: OMC in a GSM System Technical Description: BSS Implementation Technical Description: BSS Command Reference Installation & Configuration: GSM System Configuration Installation & Configuration: BSS Optimization Maintenance Information: Alarm Handling at the OMC Maintenance Information: Device State Transitions Maintenance Information: BSS Field Troubleshooting Maintenance Information: GSM Statistics Application Software Release Notes: BSS/RXCDR
Catalogue number
68P02901W01 68P02901W31 68P02901W36 68P02901W23 68P02901W17 68P02901W43 68P02901W26 68P02901W57 68P02901W51 68P02901W56 68P02901W72
Operating Information: GSM System Operation 68P02901W14 Technical Description: OMC Database Schema 68P02901W34
Tandem OMC
The following Tandem OMC manuals are part of the GSM manual set for systems deploying Tandem S300 and 1475:
Category number
GSM-100-202 GSM-100-712
Name
Operating Information: OMC System Administration Software Release Notes: OMC System
Catalogue number
68P02901W13 68P02901W71
EMOTOROLA LTD. 2000
15
ISSUE 18 REVISION 0
Scaleable OMC
The following Scaleable OMC manuals replace the equivalent Tandem OMC manuals in the GSM manual set:
Category number
GSM-100-202 GSM-100-413 GSM-100-712
Name
Catalogue number
Operating Information: Scaleable OMC System 68P02901W19 Administration Installation & Configuration: Scaleable OMC Clean Install Software Release Notes: Scaleable OMC System 68P02901W47 68P02901W74
Related manuals
The following are related Motorola GSM manuals:
Category number
GSM-001-103 GSM-002-103 GSM-005-103 GSM-008-403
Name
System Information: BSS Equipment Planning System Information: DataGen System Information: Advance Operational Impact Installation & Configuration: Expert Adviser
Catalogue number
68P02900W21 68P02900W22 68P02900W25 68P02900W36
Service manuals
The following are the service manuals in the GSM manual set, these manuals are not release dependent. The internal organization and makeup of service manual sets may vary, they may consist of from one to four separate manuals, but they can all be ordered using the overall catalogue number shown below:
Category number
GSM-100-020 GSM-100-030 GSM-105-020 GSM-106-020 GSM-201-020 GSM-202-020 GSM-101-SERIES GSM-103-SERIES GSM-102-SERIES GSM-200-SERIES
Name
Service Manual: BTS Service Manual: BSC/RXCDR Service Manual: M-Cell2 Service Manual: M-Cell6 Service Manual: M-Cellcity Service Manual: M-Cellaccess ExCell4 Documentation Set ExCell6 Documentation Set TopCell Documentation Set M-Cellmicro Documentation Set
Catalogue number
68P02901W37 68P02901W38 68P02901W75 68P02901W85 68P02901W95 68P02901W65 68P02900W50 68P02900W70 68P02901W80 68P02901W90
EMOTOROLA LTD. 2000
16
ISSUE 18 REVISION 0
Category number
The category number is used to identify the type and level of a manual. For example, manuals with the category number GSM-100-2xx contain operating information.
Catalogue number
The Motorola 68P catalogue number is used to order manuals.
Ordering manuals
All orders for Motorola manuals must be placed with your Motorola Local Office or Representative. Manuals are ordered using the catalogue number. Remember, specify the manual issue required by quoting the correct suffix letter.
EMOTOROLA LTD. 2000
17
ISSUE 18 REVISION 0
18
EMOTOROLA LTD. 2000
Chapter 1
Overview
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
ii
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Chapter 1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introducing the Motorola OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definition of OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Naming convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communication with GSM network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R network management functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event/alarm management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The OMC-R in GSM network management architecture . . . . . . . . . . . . . . . . . . . . . . . . . . Network hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The OMC-R configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The System Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SPARCstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optional processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R configuration summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scaleable configuration details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The OMC-R MMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMI user interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GUI interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The OMC-R GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introducing the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The command line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UNIX-based utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The OMC-R in a GSM network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A typical GSM network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RXCDR functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS and RXCDR configuration (SITES) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RXCDR configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NE device containment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Containment relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Site configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CELL resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS hardware relating to traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS software relating to traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DRI/RTF groups - transceiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transceiving functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of RTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Redundancy (within a cell) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2000
i
11 11 12 12 13 13 13 13 13 14 14 14 15 15 15 15 15 17 17 18 18 18 18 19 19 19 111 111 112 112 113 113 113 114 114 114 115 115 115 116 116 116 116 117 117 117 117
iii
ISSUE 18 REVISION 0
CELL configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Links in a GSM network: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Information on links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SITE link requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Physical links PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Physical link requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATH devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R connection to the network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transferring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X.21 connection configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operations and maintenance of a BSS or RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Simplified network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . O&M information flow between OMC-R and NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary of information flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Information flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R system configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Motorola OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical hardware configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communications handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communications software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet switch / multiplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . O&M network traffic capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Peak traffic capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R System Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to the System Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R GSM application software: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Processor software elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UNIX: Solaris 2.5.1 operating system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tools and applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The OMC-R database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RDBMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database schema: defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applications and utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
118 118 118 118 119 119 119 119 120 120 120 120 121 121 121 122 123 123 123 125 125 126 126 126 127 127 127 128 128 129 129 129 130 130 131 131 131 134 135 136 136 136 138 138 138 138 138 139 139 139 139 140
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
The CM MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The SPARCstation configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the OMC-R MMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A standalone server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LAN configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMI Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Client Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GUI Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Display Processor Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GUI Client - SPARCstation 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Night concentration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The OMC-R MMI: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Graphical User Interface (GUI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R front panel: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operator name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the front panel icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example console messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load Management options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Find . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Xterm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other front panel icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
141 141 142 142 142 142 143 144 144 145 145 145 146 146 146 147 148 148 149 149 149 149 149 150 150 150 151 151 152 153 153 154 154 155 155 156 156 157 157 157
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
vi
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Introducing the Motorola OMC-R

Definition of OMC-R
A simplified GSM network is shown at Figure 1-1. The OMC-R supports the day to day operations and maintenance of network components within a GSM network.
MSC
OMC-S
XCDR
OMC-R
BSC
BTS
BTS
BTS
Figure 1-1 T he OMCR in a GSM system

EMOTOROLA LTD. 2000
11
ISSUE 18 REVISION 0
Naming convention
An OMC-R configured to manage only Base Station Systems (BSS) and Remote Transcoders (RXCDR) is called an OMC-Radio (OMC-R). The Motorola OMC-R is configured to monitor Motorola base station equipment and will be referred to as an OMC-R in this manual to prevent confusion with other types of OMC.
Communication with GSM network

The Motorola OMC-R communicates with the GSM network using X.25 packet switching to exchange Operation and Maintenance (O&M) data with the Base Station Systems (BSS) and Transcoders (XCDRs) in the GSM network, via a Private or Public Switched Packet Data Network (PSPDN). The OMC-R can handle a GSM network of up to 120 Network Elements (NEs - the Motorola MSC, SGSN, OMC-R, BSS or RXCDR), the System Processor can be configured for up to 5,000 traffic channels, or up to 30,000 traffic channels.
12
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
OMC-R network management functions
OMC-R network management functions

Configuration management
Configuration management provides centralized software load management, database load management and the management of operating parameters. The OMC-R provides facilities to initiate uploads and downloads of NE operating software, or to back-up or download configuration databases for the different NEs. The OMC-R also provides the facilities to re-configure the operating parameters of NEs using the remote login facility and facilities to optimize via the GUI.
Event/alarm management
A primary function of an OMC-R is to maintain the quality of service to customers/users of the GSM network by monitoring the state of Motorola equipment in the network. Event or alarm messages containing information on the state of the different devices and links in the entire network are sent, via the X.25 network, to the OMC-R. These messages notify the operators of any potential problems occurring in the network. There is the optional Alarm notification via Paging feature which automatically notifies key personnel of certain alarm or state changes over a modem.
Fault management
Fault management provides the facility to change the status of any device using fault handling procedures. From the OMC-R, the GSM network operator can react to changes in the network and re-configure the site by taking devices in or out of service as required, thus maintaining continuity of service to mobile phone users. Fault management tasks can be performed from the map, the alarm window, Navigation tree, and through contained devices.
Performance management
Performance management provides collection and reporting of network performance statistics. The OMC-R collects, processes and stores performance statistics on the different NEs in the network, and provides reporting facilities for the presentation and printing of the processed statistics. These statistics can be then used to analyze network performance and aid long term planning.
EMOTOROLA LTD. 2000
13
The OMC-R in GSM network management architecture
ISSUE 18 REVISION 0
The OMC-R in GSM network management architecture

Network hierarchy
The position of the OMC within the GSM network management hierarchy, is shown in Figure 1-2.
BUSINESS MANAGEMENT FIVE-LAYER TMN MODEL (DEFINED IN ITU M.3010)
SERVICES MANAGEMENT
PHYSICAL IMPLEMENTATION OF THE LOWER THREE LAYERS
NETWORK MANAGEMENT
NMC
NETWORK ELEMENT MANAGEMENT
OMC-R
OMC-R
NETWORK ELEMENT LEVEL
NE
NE
NE
NE
NE
NE
Figure 1-2 GSM network management architecture
Network levels
Operation and Maintenance (O&M) management of the BSS and RXCDR can be performed at several network levels:
Local level
Local level monitoring, where reconfiguration, and software loading can be performed by connecting a personal computer to the BSC or RXCDR.
Regional level
The OMC-R provides facilities for performing functions on NEs at a regional level. Built-in alarm and event management, configuration management, and fault handling facilities enable operators at remote OMC-R sites to manage O&M in a consistent and standardized manner. The OMC-R provides monitoring and control for a number of BSSs in a specific geographical area. The prime function of the OMC-R, is to maintain the quality of service to customers/users by monitoring the performance of the radio equipment. Procedures are provided by which the radio resources can be dynamically reconfigured, and faults rectified from a single remote location. Additionally, the OMC-R provides databases for O&M data and system performance statistics.
Top level
The top level of network management is implemented by the Network Management Centre (NMC). An NMC could perform O&M functions at a network-wide level with OMC-Rs as its subordinates.
14
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
The OMC-R configuration

OMC-R configuration
The Scaleable OMC-R system configuration is shown in Figure 1-3. It is suitable for GSM networks with low-end (5k) or high-end (20k) traffic channels (TCHs). Each processor is a complete UNIX system, comprising the following: S S S S A System Processor. Several MMI processors (which also provide colour operator workstations). A GUI Server that is configured as an MMI. A laser printer.
The System Processor

The GSR4 System Processor is a UNIX system that runs the OMC-R application software that handles all O&M communication with the NE. It processes all incoming events, alarms, uploads/downloads, and performance statistics It also processes the setting up of remote login sessions to different NEs. The System Processor contains a database based on an INFORMIX Database Management System (DBMS), configured for storing performance statistics and subscription lists, enabling operators to monitor incoming events and alarms. The System Processor contains the Configuration Management Information Base (CM MIB) holding all the network and map configuration data.
SPARCstations
The remainder of the OMC-R is made up of SPARCUltras or SPARCstations, and is primarily concerned with running the OMC-R operator interface, known as the OMC-R Man Machine Interface (MMI). Typically the OMC-R configuration contains several SPARCstation 5s, which are GUI Clients. The GUI Server which is a much faster SPARCUltra or SPARCstation 20 runs the GUI processes while the GUI clients run the display interface. Each SPARCstation is a complete UNIX system. The SPARCstation 5s execute the OMC-R display software and provide the operator with workstations for the system processor.
Optional processors
Optional processors, such as those for OSI stack, Remote Login, and DataGen can be included into the basic OMC-R configuration. The processors that can be used are SPARCstation 20s or UltraSPARCs. The Network Health Analyst (NHA) can be used on a Sun Enterprise 3000 or 3500, and WWW Server on SPARCstation 5s.
EMOTOROLA LTD. 2000
15
ISSUE 18 REVISION 0
TO GSM NETWORK
SUN HSI/S card (4-port HSI / interface )
Sunlink X.25 package
X.25
OMC-R Application Software
System processor
OMC-R DATABASE (DBMS)
CONSOLE FOR OMC-R SYSTEM ADMINISTRATOR
System Processor
CM MIB
Applix cm_mi b MMI
Ultra 5
LOCAL AREA NETWORK (LAN)
MMI PROCESSOR
MMI
Workstation
Ultra 200E
SUN SPARCstation 5*
MMI PROCESSOR SUN SPARCstation 5*
MM I
Workstation
WWW SERVER PROCESSOR (optional) SUN SPARCstation 5* OSI PROCESSOR (optional) SUN SPARCstation 20 or SUN Ultra 200E* Network Health Analyst PROCESSOR (optional) Datagen/OffLine MIB PROCESSOR (optional) Laser Printer
Lexmark Optra RN+ printer (with software)
NHA processor*
DataGen/OffLine MIB processor*
*Optional
Figure 1-3 Typical Scaleable OMC-R system configuration

16
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
OMC-R configuration summary
OMC-R configuration summary

Scaleable configuration details
A summary of the Scaleable OMC-R configuration is as follows:
High-end TCH Scaleable OMC-R

The high-end TCH configuration of the Scaleable OMC-R provides support for 30,000 TCHs with a maximum of 120 NEs. The MMI interface is provided on SPARCstation 5/20 machines and UltraSPARCs. One of the high end machines must be configured as a server. A second can be configured as a server when the two will share the load of the clients for redundancy purposes should one server fail. Up to 10 MMI interfaces may be used in the OMC-R system. The GUI servers run the GUI sessions while the GUI clients run the display software only. The total number of GUI sessions supported is 10, as on the standard OMC-R. Each processor can support one GUI session.
Low-end TCH Scaleable OMC-R

The minimum configuration of the Scaleable OMC-R provides support for up to 5,000 TCHs with a maximum of 15 NEs. For very small systems, a SPARCstation Ultra 200E can be configured as a server. However, up to four additional machines may be added to the system. The GUI server runs the GUI sessions while the display processes are run on slower SPARCstation 5 machines which act as GUI clients. Each processor can support one GUI session.
EMOTOROLA LTD. 2000
17
The OMC-R MMI
ISSUE 18 REVISION 0
The OMC-R MMI

MMI user interfaces
The OMC-R MMI has two user interfaces to operate the OMC-R system: S S The Graphical User Interface (GUI). Command line interface.
GUI interface
The GUI presents the user with a Front Panel displaying icons that represent all the modules of the OMC-R.
Command line interface

The UNIX-based system utilities are executed at the command line of an Xterm window which is opened from the GUI Front Panel.
18
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
The OMC-R GUI
The OMC-R GUI

Introducing the GUI
The OMC-R MMI provides a Graphical User Interface (GUI), based on the Open Software Foundation Motif (OSF-Motif). The OMC-R GUI Front Panel is shown in Figure 1-4. An expert Front Panel that is smaller and does not have icon titles is also available, shown in Figure 1-5, to facilitate use by experienced personnel. The OMC-R GUI enables operators to interact with the OMC-R and to carry out network management functions. All maintenance, network reconfiguration, troubleshooting, and network administration, apart from equipment repair and replacement, can be executed through a single interface.
OMC-R Front Panel

The GUI Front Panel contains icons that represent different modules of the OMC-R MMI. A summary of the current alarms in the network is always displayed on the right hand side of the GUI Front Panel.
1 3 2
6 7
GSR4.11.6.1.3
16
15
14
13
12
11
9 10
Figure 1-4 The OMC-R GUI Front Panel
Figure 1-5 The Expert OMC-R Front Panel

EMOTOROLA LTD. 2000
19
The OMC-R GUI
ISSUE 18 REVISION 0
Table 1-1 describes the icons on the OMC-R GUI Front Panel. Table 1-1 Number 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. Description Operator name and OMC-R version number Access to OMC-R console Access to configuration management Access to event management Access to performance management Access to load management Access to find facility Alarm summary Incoming alarms display icon Front Panel exit button Access to OnLine Help Access to UNIX command line Access to administrative and scheduled functions Access to system event logs Remote access to BSS or RXCDR Access to network maps
110
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
The command line interface
The command line interface

UNIX-based utilities
UNIX-based utilities are provided to give additional network management functionality to the OMC-R MMI in the following functional areas: S S S S S S S Remote login. Synchronization of time with the OMC-R-BSS. Event management. Event log processing, searching and filtering event logs. Performance management. NE database management. System administration utilities.
EMOTOROLA LTD. 2000
111
The OMC-R in a GSM network
ISSUE 18 REVISION 0

A typical GSM network
A typical GSM network (900 MHz, 1800 MHz or 900/1800 MHz), is shown in Figure 1-6. It consists of an Operations and Maintenance Centre (OMC-R) and one or more Network Elements (NE or nodes), which may be a Base Station System (BSS), a Remote Transcoder (RXCDR), Mobile Switching Centre (MSC) or Cell Broadcast Centre (CBC).
MSC OMC-R CBC
X.25
64 kbit/s
X.25
VOICE TRAFFIC FROM BSS1 AND BSSn
O&M DATA FROM BSS1, BSSn, & RXCDR RXCDR
64 kbit/s 64 kbit/s 64 kbit/s 64 kbit/s 4x16kbit/s TRAFFIC
2Mbit/s link
64 kbit/s 64 kbit/slink
CBL CBL
MESSAGE INFO
2Mbit/s
64kbit/s O&M DATA
4x16kbit/s TRAFFIC
64kbit/s O&M DATA
2Mbit/s link BSS1 BSC BSC/BTS 2Mbit/s link MS BTS BTS MS MS 16 kbit/s traffic MS MS MS
BSSn
BTS 2Mbit/s link BTS BTS
Figure 1-6 T he OMCR in a GSM network
112
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
OMC-R functions
The OMC-R performs the following functions: S S Direct management of BSS and RXCDR and the links between them. Management of the NE devices associated with the links (on the RXCDR side) between the MSC, the BSSs and RXCDRs. This is all done using the O&M data packets sent to/from the NE. Monitoring of events and alarms, performing fault handling, NE re-configuration, NE software uploading and downloading, and performance data collection and reporting for all the NE under its control. Provides a centralized facility for network management of up to 120 NEs with up to 30,000 traffic channels for the Scaleable OMC-R.
RXCDR functions
The RXCDR routes the O&M data packets between the BSS and the OMC-R, and traffic channels (voice) between the BSS and MSC. The O&M data packets are routed between the OMC-R and the RXCDR using X.25 packet switching. Each 2 Mbit/s link between the BSSs and the RXCDR typically consists of two 64 kbit/s O&M links plus 120( ( 30 x 64 kbit/s) x (4 x16 kbit/s) ) traffic channels. The RXCDR is located between the MSC and the BSS, usually located in the same area as the MSC. This is the most efficient arrangement, as the primary feature of the RXCDR is that it converts the 64 kbit/s PCM output of the MSC to a 16 kbit/s rate required for transmission over the air interface (between the BSS and the MS). Thus, four 16 kbit/s channels from the RXCDR can be fitted on each 64 kbit/s terrestrial circuit. In this way, each 30 channel 2 Mbit/s PCM link can carry 120 GSM-specified channels with obvious cost savings.
Configurations
A BSS consists of a Base Site Controller (BSC) and one or more remote Base Transceiver Stations (BTS). Every BTS must be physically connected to its controlling BSC using a 2 Mbit/s link. A BTS can also be located in a BSC cabinet, thus creating a collocated BSC/BTS, usually connected using a LAN. A BSS configuration may have all BTS directly connected to the controlling BSC (spoke connection) or the BSS may be connected via another BTS (daisy chaining). A BTS may also have more than one connection to its controlling BSC for redundancy. At GSR4 BSCs are required to use the GPROC2 (second generation processor board). BSC capacity is expanded as a result of the faster processing and memory of the GPROC2, this means 100 sites can be supported.
EMOTOROLA LTD. 2000
113
BSS and RXCDR configuration (SITES)
ISSUE 18 REVISION 0
BSS and RXCDR configuration (SITES)

BSS configuration
In a GSM network, the BSS is configured to contain a series of one or more SITES. SITE 0 always contains the BSC equipment; it may also contain BTS equipment (collocated BSC and BTS connected by a LAN). Sites 1 to 100 contain only BTS equipment, they cannot contain the BSC. Thus there are 3 possible types of BSS site: S S S BSC site. BTS site. Collocated BSC and BTS site.
Example
An example configuration is shown in Figure 1-7.
REDUNDANT LINK 2 Mbit/s TERRESTRIAL OR MICROWAVE LINK
SITE 0 (BSC) MSI BOARD 2 MMS PORTS
SITE 1 (BTS)
SITE 2 (BTS)
SITE 3 (BTS)
2 Mbit/s link
2 Mbit/s TERRESTRIAL OR MICROWAVE LINK TO/FROM RXCDR
Figure 1-7 The naming convention and physical links of BSS
RXCDR configuration
An XCDR placed at the MSC is known as a Remote Transcoder (RXCDR), and is regarded as a separate NE (or node). Sometimes the transcoding functionality is located within a BSC. In the example above, (Figure 1-7), the transcoding hardware is regarded as a subset of the BSS SITE 0 configuration.
114
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
NE device containment
NE device containment
Containment relationship
There is a containment relationship between each entity in the GSM Network that is modelled at the OMC-R. This hierarchical structure is known as the Containment Tree. Each entity is contained within a container, which may consist of more than one entity known as containees. For example, an MMS is contained within an MSI, which in turn is contained within a SITE. This containment relationship is used for logical naming, configuration purposes and event management. For more details on containment relationships refer to Chapter 5 of this manual.
Ports
There are two MMS ports on an MSI board. There can be up to 64 MSI boards in a SITE and up to 100 SITEs in a BSS. An instance of an MMS can be uniquely identified to an MSI/XCDR card as follows:
Example
MMS port 1 on MSI board 2 in SITE 0 would be named MMS 2 1 X. The first digit is the parent MSI card, the second refers to the port number and the third is not required.
EMOTOROLA LTD. 2000
115
Site configuration
ISSUE 18 REVISION 0
Site configuration
CELL resources
In the Motorola implementation of GSM, a single BTS consists of one or more cabinets and controls one or more CELLs. The Motorola term CELL is equivalent to the GSM term BTS, since Motorola BTS sites can contain more than one cell. GSM requirements specify one cell per BTS. The different related resources of a CELL configuration are shown in Figure 1-8.
SITE
Radio Frequency
CELL
DRI Group
RTF Group
Neighbour
Handover Control
Power Control
DRI
RTF
Figure 1-8 Site configuration
BTS hardware relating to traffic

A BTS cabinet would contain one or more radio units. Each CELL is serviced by one or more carriers, each of which is serviced by a single radio unit. Each carrier has eight TDMA timeslots.
BTS software relating to traffic

From a software perspective, a BTS contains the following software devices/functions: S S S DRI Groups, which contains DRIs. There is one DRI Group per cell on each site for redundancy purposes. RTF Groups, which contain a number of Receive Transmit Functions (RTFs). There is one RTF Group per cell on each site for redundancy purposes. CELLs.
116
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
DRI/RTF groups - transceiving
DRI/RTF groups - transceiving

Transceiving functionality
Motorola has implemented transceiving functionality using the DRIs and RTFs. This provides the radio carrier which, in a GSM digital system, consists of eight TDMA timeslots. These digital channels carry speech and various control data. One of the more important of these control channels is the Broadcast Control Channel (BCCH). Every CELL must have at least one BCCH.
Types of RTF
RTFs are used to carry the traffic part of the call (speech or data). They are defined as functions rather than devices as they are a logical representation of the traffic, rather than relating to a physical piece of hardware. An RTF contains eight digital channels, one for each timeslot on the air interface. There are two types of RTF: S S BCCH (one of the timeslots is used as a BCCH) Non-BCCH
To provide redundancy of RTF traffic, it is possible to specify two routes or PATHs that are potentially able to carry the RTF traffic from the BTS to the BSC. These are called the Primary and Secondary PATHs. If two PATHs are available, the shorter will be the connected PATH and the longer will be the redundant PATH. If the PATH availability changes and a shorter PATH becomes available to the RTF, then a switchover will occur so that the RTF starts to use this new PATH. Refer to Physical links - PATH for more details of PATHS. Each RTF function, equipped to a remote SITE, uses two PCM (that is, 2 x 64 kbit/s, where 64 = 4 x16 kbit/s) timeslots per PATH device. Each OMC-R is limited to supporting a particular number of RTFs, this is called the RTF Limit, and is set by Motorola engineers during staging. Each OMC-R has a threshold RTF value, which is 90% of the RTF Limit.
Redundancy (within a cell)

The DRIGroup and RTFGroup are used to support transceiving redundancy for CELLs. Typically, for n RTFs there will be n+1 DRI devices equipped. When an RTF is equipped, it attaches itself to an available In Service (INS) DRI. If the DRI goes Out Of Service (OOS), the RTF will attach itself to another available DRI to maintain transceiving functionality to the CELL.
EMOTOROLA LTD. 2000
117
CELL configuration
ISSUE 18 REVISION 0
CELL configuration
Logical devices
A CELL contains the following logical devices: S S S Neighbour. Handover Control. Power Control.
Handover control
Handover means switching a call from a channel in a given CELL, to another channel in either the same or another CELL. This is done keeping disturbance to a minimum, ideally in a way not noticeable by the users. Handover control, is the functionality required to detect and effect a handover, in order to maintain acceptable service to the user.
Handover detection algorithm

There are a number of parameters used to detect when a handover should occur. A number of factors are input to this algorithm. These factors are as follows: S S S Uplink and downlink receive signal strength. Uplink and downlink receive signal quality. Power budget. When a power budget handover is enabled, the call will hand to a neighbouring cell at the point where a lower power budget can be achieved (both the MS and the BTS can reduce their TX power). S S Interference. Distance (between the BTS and the MS). NOTE Uplink is from the Mobile Station (MS) to the BTS, downlink is from the BTS to MS. There are thresholds supported for each measurement and when a threshold is exceeded, a handover may occur.
Power control
In order to reduce Radio Frequency interference in the network, and increase battery life on MSs, it is desirable to run all the BTSs and MSs in the network at the minimum TX power that provides adequate rxqual (quality) and rxlev (level) for a call. Power control is the functionality to detect and effect the modification of transmission power, both for the MS and BTS, in order to maintain an acceptable service to the user.
Power control detection algorithm

There are a number of parameters used to detect when power control should occur. A number of factors are input to this algorithm. These factors are: S S Uplink and downlink receive signal strength. Uplink and downlink receive signal quality.
There are thresholds supported for each measurement. When a threshold is exceeded transmission power modification may occur.
118
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Links in a GSM network: overview
Links in a GSM network: overview

Information on links
Note the following BSS link definitions: S S S All links to and within BSSs and RXCDRs are in reality links to and between SITEs. A link to a BSS, is a link to the SITE configured as a BSC within the BSS. Similarly, links within a BSS, those between the BSC and BTSs and between one BTS and another, are all links between SITEs.
SITE link requirements

Every SITE must contain at least one Multiple Serial Interface (MSI) board (NIU for MCellt), which is a communications controller that contains two 2 Mbit/s (MMS) ports.
Link Types
There are two types of links used in the GSM network: S S Physical links Logical links
EMOTOROLA LTD. 2000
119
Physical links PATH
ISSUE 18 REVISION 0
Physical links PATH

Connection
A physical link between two SITEs is made by connecting one MMS port of an MSI (NIU for MCell) card on one SITE, to one MMS port of an MSI (NIU for MCell) card on another SITE.
Physical link requirements

The following are physical link requirements: S S Every BSC must be physically connected to the OMC-R. A BSC may be directly connected to the OMC-R, or via the RXCDR or MSC. Similarly, every BSC must be physically connected to its controlling MSC. A BSC may be directly connected to its controlling MSC or it may be connected via an RXCDR. Every BTS must be physically connected to its controlling BSC. A BTS may be directly connected to its controlling BSC or it may be connected via another BTS (daisy chaining). A BTS may have more than one signalling and traffic connection to its controlling BSC giving load sharing and redundancy.
PATH devices
A PATH device defines the connectivity between a BSC site and BTS sites under its control. It is a logical representation of a 2 Mbit/s route between the BSC and a destination BTS. This connectivity specifies the physical route from the BSC, through intermediary BTSs to the destination BTS. A PATH may contain a route through a maximum of 10 BTS sites. The connection information between any two sites consists of an MSI (NIU for M-Cell)/MMS device at each end of the link.
BSC0
A BTS1
D
B BTS2 BTS3
PATH 1 = ABC PATH 2 = D
Figure 1-9 Example of path settings within a BSS Figure 1-9 shows two PATHs connecting BSC0 with BTS3, a PATH through BTS1 and BTS2, (ABC), and one direct connection between BSC0 and BTS3 (D).
120
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Logical links
Logical links
Introduction to links
The 2 Mbit/s physical links in the GSM network, are configured to carry (as well as the voice traffic channels) many logical links containing signalling information or O&M data. These links are monitored by the OMC-R.
Types of link
The types of logical link are shown in Figure 1-10. These links generate events, alarms, and performance statistics, at the BSC (or RXCDR) site where they are equipped. These are reported to the OMC-R. The different logical links are as follows: S Operation and Maintenance Link (OML). The purpose of the OML is to provide communication between an OMC-R and a BSC or RXCDR for transferring network management (O&M) data. Up to four OML links can be configured between an OMC-R and BSC or RXCDR; one OML is used at any one time, the other three OMLs exist for redundancy purposes. S Message Transfer Link (MTL). The purpose of the MTL is to provide a link for signalling information between the BSC and the MSC. In the Motorola system, when local transcoding is used, this is a physical connection between the BSC and the MSC. When a Remote Transcoder is used, the logical MTL is made up of two physical parts; the connection between the BSC and the RXCDR and the connection between the RXCDR and the MSC. When more than one MTL is configured between the BSC and MSC, both load sharing and redundancy are present. Up to 16 MTLs may be configured between a BSC and MSC. S Radio System Link (RSL). A signalling link between a BSC and a remote BTS is called a Radio System Link (RSL). The purpose of an RSL is to provide signalling information between a BSC and a remote BTS. The timeslots used, are chosen automatically by the Motorola software. This is to ensure that new BTSs, added to the network, can be communicated with on default timeslots. Each RSL link is associated with a PATH. It is possible to have multiple (up to eight) RSLs between a BSC and a remote BTS. For example, in Figure 1-10, there are two RSLs between BTS2 and the BSC. This is possible because of the daisy chain connection in the BSS. The two RSLs provide both load sharing and redundancy functions for the signalling link. S RXCDR to BSC Link (XBL). An XBL link may be configured between the BSC and the RXCDR for exchanging internal Fault Management (FM) data between them. S Cell Broadcast Link (CBL). A CBL link can be configured between the BSC or RXCDR and the Cell Broadcast Centre (CBC). This is used for downloading messages to broadcast along with other necessary information such as repetition rate and number of broadcasts.
EMOTOROLA LTD. 2000
121
Logical links
ISSUE 18 REVISION 0
Requirements
Note the following about logical links: S A BSC will always contain at least one OML (with a maximum of four), one MTL or XBL (depending on how it is connected to the MSC) and at least one RSL for each remote BTS under its control. An RXCDR will always contain at least one OML, and at least one XBL. A BTS will always contain at least one RSL.
S S
MSC
MTL 1
VOICE TRAFFIC
MTL2
VOICE TRAFFIC
OMCR

CBL
Different logical links: MTL:MSCBSC LINK

(C7 SIGNALLING INFORMATION)
OML:OMC-RBSC LINK
(O&M DATA)
X.25
2Mbit/s link OML1 2Mbit/s link OML2
XBL:RXCDRBSC LINK
(FAULT MANAGEMENT DATA)
RSL:BTSBSC LINK
(SIGNALLING INFORMATION)
CBL:BSCCBC Link
(MESSAGE INFORMATION)
RXCDR
Voice Traffic
OML3

MTL2 XBL2
OML2
XBL1
2Mbit/s link
OML1
2Mbit/s link
MTL1
CBL 2Mbit/s link
CBC CBC
BSC/BT S1
RSL11
BT S2
BT S3
RSL11
(BTS1 to BSC )
RSL12 (BTS1 to BSC ) RSL21 (BTS2 to BSC) RSL22 (BTS2 to BSC)
BSC
BT S1
RSL22
RSL12
BT S2
Figure 1-10 T he different logical links in a GSM network

122
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
OMC-R connection to the network

Transferring data
For every BSC in the network, one or two timeslots (64 kbit/s) on a 2 Mbit/s link is used to carry the O&M data between the BSC and RXCDR. All the timeslots from the different BSC-RXCDR links are grouped onto one or more 2 Mbit/s links by the RXCDR or the MSC. The RXCDR transfers the information to a packet switch / multiplexer. The X.21 links are connected to the OMC-R via a public or private X.25 network/switch. Illustrated in Figure 1-11 is the method of transferring O&M data between the BSS and the OMC-R.
X.21 connection configuration

The physical connection between the OMC-R processor and the packet switch / multiplexer consists of two to seven X.21 connections. Each physical connection can support up to 256 virtual circuits. There are four types of virtual circuits that can be made on the OML: S Event Interface (EI) transfers data packets (events and alarms), plus the OMC-R-BSS message from the NE to the OMC-R. The circuit is made by the NE calling the OMC-R. Bootload (BL), also called Download, transfers BSS software and BSS databases to the NE. The circuit is made by the NE calling the OMC-R. Upload (UL) transfers BSS database back-ups and raw statistics (performance data) to the OMC-R. The circuit is made by the OMC-R calling the NE. Remote login (RL) provides sessions for transfer of BSS MMI commands/responses to the NE. The circuit is made by the OMC-R calling the NE.
S S S
The virtual circuits EI and BL can be accepted on any of the X.21 connections on the OMC-R. Normally two connection are set up for EI and BL. If a given port is not working, then the packet switch / multiplexer will switch to a different port. The UL circuits consists of two processes and each is assigned to a single OMC-R connection. The RL is assigned to a single OMC-R connection.
EMOTOROLA LTD. 2000
123
ISSUE 18 REVISION 0
OMC-R
OMC-R SYSTEM PROCESSOR X.25

O&M Data Packets

Packet switch / multiplexer
X.21 connections (two to seven physical connections)
RXCDR

BSS2
64 kbit/s O&M TIMESLOT
2 Mbit/s link
NAILED CONNECTIONS (ONE PER O&M TIMESLOT)
RXCDR
2 Mbit/s link
BSS1

BSS3
2 Mbit/s link

BSS4
64 kbit/s O&M TIMESLOT
BSSn
Figure 1-11 Interconnection of network elements and OMC-R
124
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Operations and maintenance of a BSS or RXCDR
Operations and maintenance of a BSS or RXCDR

Simplified network
A simplified network showing some of the hardware devices in the different sites, and the links between them, is shown in Figure 1-12. BSS1 from Figure 1-11 is used as the example BSS.
X.25 RXCDR MTL LINK MSC MSC MSI X C D R RXCDR: SITE0 OML LINKS
OMCR
KSW MSI
XBL LINK
BSS MSI KSW MSI MSI DRI BSS1: SITE0 RCU COLLOCATED BSC/BTS
BTS BSS1: SITE1 BSS1: SITE2

MCell
BTS
RCU + DRI
K S W
M S I
RSL LINKS
N I U
M C U
TCU
Figure 1-12 Simplified GSM network showing devices and links of BSSs
EMOTOROLA LTD. 2000
125
O&M information flow between OMC-R and NEs
ISSUE 18 REVISION 0
O&M information flow between OMC-R and NEs

Summary of information flow
A summary of the information flow between the OMC-R and the NEs is shown in Figure 1-13. The primary function of the OMC-R is to monitor the health of the radio network.
OMC-R TO NE 1. MMI COMMANDS (VIA GUI OR REMOTE LOGIN) FAULT HANDLING SITE CONFIGURATION SITE RESETS 2. SOFTWARE and NE DATABASE DOWNLOADS 3. NE DATABASE DOWNLOADS OMC-R NE TO OMC-R 1. EVENTS & ALARMS 2. NE RESPONSES TO MMI COMMANDS 3. PERFORMANCE DATA (RAW STATISTICS) 4. NE DATABASE UPLOADS
NE
NE
NE
NE
NE
Figure 1-13 Information flow between the OMCR and BSSs
Information flow
All events (changes of state of a hardware device, link, or function) and alarms (changes which could be service affecting) are sent to the OMC-R, via the RXCDR and the X.25 packet switch, where they are processed into a standard format. The alarms can be configured to update a network map, which will give the operator a visual warning by causing the appropriate BTS or BSC to flash. The alarms or events can also be displayed on the operator terminals, within different windows, depending on how the network operator (or OMC-R administrator) has configured them. The RXCDR contains several of the same devices, links and functions as the BSS, and generates events and alarms in the same way. The network operator then takes action to handle the reported fault, by remote logging in to the BSS or RXCDR, diagnosing the problem, and taking appropriate action. Regardless of the number of BTSs, the BSS is regarded as a single NE, and runs only one software load, for example BSSGSM 1.4.0.x. When loading a BSS, the entire load is first sent to the BSC which then distributes the appropriate load objects to the configured BTS. A copy of the active BSS load is stored at the OMC-R, as is a copy of the previous version of the BSS software. These software loads must be compatible with the load installed on the OMC-R. The RXCDR receives the same software load as a BSS, it just implements a different part of it. Each BSS and RXCDR contains an operational database, in which the configuration data for all the devices and links in the SITES within the NE is stored. A backup copy of the active database is kept at the OMC-R. Performance measurements for the different BSS and RXCDR are periodically routed every 30 or 60 minutes to the OMC-R as raw statistics in a data file. This data is stored in a database at the OMC-R, and processed into statistics which provide valuable information for efficient network management and planning.
126
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
OMC-R system configuration
OMC-R system configuration

Motorola OMC-R
A typical hardware configuration of a Motorola OMC-R, is shown in Figure 1-14.
X.25 PACKET SWITCH TO GSM NETWORK
X.25 MULTIPLEXER OMC-R SYSTEM PROCESSOR
X.25 INTERFACE

Laser Printer
LOCAL AREA NETWORK (LAN)
OSI processor (optional)
OMC-R GUI client Operator Workstations + GUI Server
Figure 1-14 An example Motorola OMCR system configuration
Typical hardware configuration

Each processor is a complete UNIX system, and comprises a central System Processor and several Man-Machine Interface (MMI) processors that also provide colour operator workstations, and a laser printer. The GUI server is a fast high specification machine that allows older machines to run the display software while it runs the GUI sessions. NOTE Some systems may be configured differently; for specific information the OMC-R Bill Of Materials (BOM) should be consulted.
EMOTOROLA LTD. 2000
127
Communications handling
ISSUE 18 REVISION 0
Communications handling
Communications software
The OMC-R communications software, provides control and support for the protocol stacks which interface the OMC-R with the following: S Internal OMC-R communications: S TCP/IP. Ethernet. X.11.
The NEs in the GSM network - X.25.
The X.25 software is loaded in the System Processor, and the X.11 driver software is loaded in the MMI Processors. The remaining communication software is shared between the two processors. The operating processes are linked between machines by Interprocess Communication (IPC). The OMC-R network can be extended to include further MMI Processors, or secondary GUI servers, connected either locally or via a Wide Area Network (WAN). Bridges and gateways can also be used to connect to other computer systems such as an NMC, or other OMC-Rs.
128
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0

Connections
The OMC-R is connected to the GSM Network, to receive O&M data using a packet switch / multiplexer, (as shown in Figure 1-15). The Packet switch makes a maximum of 256 x X.25 virtual circuits available for the exchange of O&M data between the OMC-R and the NEs.
2 Mbit/s LINKS 2 Mbit/s LINKS
HSI Card
HSI Connections
SYSTEM PROCESSOR
OMC-R SYSTEM PROCESSOR
Figure 1-15 Example Packet switch / multiplexer connections
Packet switch
The connection between the System Processor and the packet switch could be direct or connected through a private or public packet data network.
EMOTOROLA LTD. 2000
129
O&M network traffic capacity
ISSUE 18 REVISION 0
O&M network traffic capacity

Peak traffic capacities
The System Processor supports the following O&M peak network traffic capacities: S S S 100 x X.25 packets per second, with a packet length of 128 bytes, aggregate. 100 kbit/s aggregate. The System Processor can be configured to handle up to 5,000 traffic channels, or up to 30,000 traffic channels, associated with a maximum of 120 NEs via the 256 x X.25 virtual circuits.
130
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
OMC-R System Processor

Introduction to the System Processor
The hardware configuration of the GSR4 System Processor (for example, the number of CPU processors, memory, disk capacity) can be varied depending on whether the low-end TCH or high-end TCH OMC-R is chosen. Thus, the Scaleable OMC-R provides easy and cost effective expansion from low-end TCH configuration to high-end TCH. The software requirements are the same for both the low-end and high-end Scaleable OMC-R configurations.
System Processor
System specifications
The System Processor software is installed on internal and external disks for the E3000 system and on Internal disks only on the E3500 system. All system and data areas are mirrored for redundancy.
SUN HSI/S card (4-port HSI interface)
E3000

Graphics Head
4 (or 7) x 2.1/4.2 Gb disks (Internal and External)

Or E3500
OMC-R System Processor System Processor

4 (or 8) x 9.1 Gb disks (Internal)
Graphics Head
Figure 1-16 Scaleable OMC-R - high-end System Processor The System Processor running Solaris 2.5.1 handles hardware failure by rebooting on failure, and configuring out the broken hardware. Table 1-2 (software) and Table 1-3 (hardware) show the specifications for the System Processor. The external disks require an additional disk controller that is already available.
EMOTOROLA LTD. 2000
131
ISSUE 18 REVISION 0
Table 1-2 GSR4 System Processor software requirements Software SUN Applicable to both low-end TCH and high-end TCH Solaris 2.5.1 Common Desktop Environment (CDE) 1.0.2 Solstice DiskSuite 4.1 Solstice Backup 5.1 (network edition) Sunlink X25 9.1 Solaris 2.5.1 AnswerBook NS Transition Kit 1.2 HSI/S driver software 2.0 Symon 1.3 SunVTS 2.01 OnLine 7.13.UC2 ESQL 7.13.UC3 ISQL 6.03 UC1 WINGZ 1.4.1A Interleaf IXI X window system TCSI Applixware Shareware Interleaf Worldview 2.01 Motif User Pack 1.2.4d 1 2 4d X11R5 Patch level 26 OSP 4.0.4 Applix Data 4.3 Applix Spreadsheet 4.3 TCL 7.4 TK 4.2 Expect 5.19 Netscape Enterprise Server ( (Webserver) ) 3.0 Netscape Navigator 4 FlexLM 6.0
Informix 7
Netscape p Licensing
132
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Table 1-3 System Processor hardware specifications using E3000 Hardware Model Processor (CPU) (Low-end TCH only) Sun Enterprise 3000 1 x 250/336MHz or 2 x 250/336 4 x 250MHz UltraSPARC-I (subject to change) MHz UltraSPARC-I (subject to change) 256 MB 1 MB (subject to change) Internal Disk 2.1 Gb SCSI2 disk (4 x 2.1 or 4 x 4.2) SparcStorage multipackSMCC 8.4/1.8 Gb (in 4 x 2.1 or 4 x 4.2 Gb disks) Backup I/O Slots I/O (GSM Network Connection) Printer Network Dial-in modem Console Drives I/O boards CPU memory boards 512 MB 1 MB (subject to change) Internal Disk 1 disk pack of 2.1 Gb SCSI2 disk (7x 2.1 or 7 x 4.2) SparcStorage multipackSMCC 14.7/29.4 Gb (in 7 x 2.1 or 7 x 4.2 Gb disks) (High-end TCH only)
Memory External Cache Disk Capacity
SMCC 1224 Gbyte DAT tape drive Fast Wide Intelligent SCSI Sbus. 1 x HSI/S card 2 x HSI/S card
Network printer Ethernet. Twisted pair interface ISG 3265 Fast (optional) Graphics Head Internal 644Mb CD-ROM 3.5 1.44Mb Internal Floppy 1 1 2 2
Connection to GSM Network

The Scaleable OMC-R uses Sunlink X.25 application software and connects to the network using the HSI/S card. This allows the Scaleable high-end OMC-R to be used where there is existing packet switching and multiplexing equipment available, or to be connected to a public packet switched network.
EMOTOROLA LTD. 2000
133
ISSUE 18 REVISION 0
Table 1-4 System Processor hardware specifications using E3500 Hardware Model Processor (CPU) Memory External Cache Disk Capacity Backup I/O Slots I/O (GSM Network Connection) Printer Network Dial-in modem Console Drives I/O boards CPU memory boards (Low-end TCH only) Sun Enterprise 3500 1/2 x 336 MHz 256 MB 1 MB (subject to change) Internal Disk = 4 x 9.1 Gb 4 x 336 MHz 512 MB 1 MB (subject to change) Internal Disk = 8 x 9.1 Gb (High-end TCH only)
SMCC 1224 Gbyte DAT tape drive 2 x Sbus slots SunFastEthernet 2 x FC-AL sockets 1 x HSI/S card Network printer Ethernet. Twisted pair interface ISG 3265 Fast (optional) Graphics Head Internal 644 Mb CD-ROM 3.5 1.44 Mb Internal Floppy 1 1 2 2 2 x HSI/S card
OMC-R application software impact

Existing system processor OMC-R application software has been ported to work on the Solaris 2.5.1 OS. There is no performance impact due to the Scaleable high-end OMC-R.
Feature description
Table 1-5 gives a comparison between the two Scaleable OMC-R configurations. Table 1-5 Scaleable OMC-R configurations (Maximum values) Feature Maximum traffic channels NEs supported Total GUI sessions supported Dial-up sessions per MMI processor Total remote dial-up sessions Remote login sessions Simultaneous downloads Simultaneous uploads Scaleable OMC-R low-end 5,000 15 5 1 2 6 6 4 120 10 1 2 20 12 15
. . . continued EMOTOROLA LTD. 2000
Scaleable OMC-R high-end 30,000 (minimum 5,000)
134
ISSUE 18 REVISION 0
Feature Sustained event rate Maximum event burst
Scaleable OMC-R low-end 8 alarms+2 state changes 20 events/s over 20 mins
Scaleable OMC-R high-end 12 alarms+3 state changes 60 events/s over 20 mins
External Interface (OMC-R to BSS)

The OMC-RBSS (rlogin) and the SMASENMASE interface will not be affected by the high-end Scaleable OMC-R.
Configuration
The configuration of the System Processor is shown in Figure 1-17. It uses a Solaris 2.5.1 UNIX operating system, and contains a Database Management System (DBMS) from Informix which is configured for storing the performance statistics. There is an Event Management Information Base (EM MIB) that contains the incoming events and alarms which update the map displays to present the operator with visual indication of alarms in the network. The System processor also contains the CM MIB which holds the configuration data required to run the network maps.
SYSTEM PROCESSOR Event Log OMC-RGSM GSR 4 SOLARIS (2.5.1) ETHERNET CONTROLLER CONSOLE FOR SYSTEM ADMINISTRATOR
OMC-R DATABASE [Informix]
Applix
X.25 HANDLER
CM MIB
cm_mib MMI
Figure 1-17 System Processor software configuration
EMOTOROLA LTD. 2000
135
OMC-R GSM application software: overview
ISSUE 18 REVISION 0

OMC-R processes
The functional software areas of the OMC-R are split between the OMC-R System Processor and the MMI processor. The processes of the OMC-R application software installed on the System Processor, the OMC-RGSM GSR 4, are shown in Figure 1-18. The operator is provided with a front end to all these processes at the OMC-R MMI, and additional front end functionality is provided by command line utilities.
OMC-RGSM GSR 4 (System Processor)
Configuration Management
Performance Management
SW Load Management
Event/Alarm Management
Device Management
Event Interface
Remote Login
Figure 1-18 OMC-RGSM (System Processor) software components
System Processor software elements

The software elements that constitute the System Processor software, perform the network element O&M management tasks, provide database storage facilities, and provide the interface to the network elements via the X.25 network. The OMC-R System Processor software elements are as follows: S Configuration Management. Configuration management allows the operator to perform network configuration tasks, and to maintain all details of the network configuration at the OMC-R. Performance Management. Performance management controls the collection, administration, processing, and storage of NE performance statistics. Software Load Management. Load management provides a facility for uploading and downloading NE software loads, and NE operational databases. It also provides a means of managing multiple copies of software loads for back-up purposes. Event/Alarm Management. Event/Alarm management provides a mechanism at the OMC-R for alarm surveillance. It manages events and alarms routed to the OMC-R from NEs, or generated within the OMC-R. NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000
136
ISSUE 18 REVISION 0
Remote Login. The remote login software manages the X.25 connection for remote login to network elements from the OMC-R. Remote login is a means by which the operator performs configuration management, fault management, and some performance management procedures at the network elements. Event Interface. The event interface handles the X.25 alarm connections to the network elements, then translates and forwards incoming events and alarms to the Event/Alarm Management functional software. Device Management. Device management allows the operator to perform fault management and configuration management at the OMC-R. The OMC-R supports most hardware devices and software functions located at the remote network elements.
EMOTOROLA LTD. 2000
137
UNIX: Solaris 2.5.1 operating system
ISSUE 18 REVISION 0
UNIX: Solaris 2.5.1 operating system

Platform
The SUN system processor operates under the Solaris 2.5.1 operating system. This provides the platform for the OMC-R software applications and provides facilities for system administration.
Advantages
The main advantages of this operating system are that it is designed to provide: S S An enhanced multi-architecture solution for systems to support Internet/Intranet connectivity. A system offering a scaleable, secure and reliable operating environment.
Features
The Solaris 2.5.1 release contains several 64-bit features, including Kernal Asynchronous Input/Output (KAIO), which facilitates the fast asynchronous transfer of large amounts of data between memory and disk. Included with this release is the Common Desktop Environment (CDE). This provides users with a flexible open user environment that has a common look and feel across all major UNIX desktops. This environment allows transparent access to network resources; and allows frequently used UNIX commands to be iconized. It is also possible to drag and drop between files and commands.
Tools and applications

The Solaris 2.5.1 Operating System includes the following tools and applications: S Solstice Backup 5.1 utilities. The Solstice Backup software allows a Solaris operating system server to provide automated, high performance backup, recovery and storage management services to machines on the network. Solstice Backup provides simple centralized administration, through a single unified view of the entire data management operation from any point on the network. Intuitive user interfaces simplify administrative tasks such as configuring clients and servers, and setting up backup schedules for file systems and databases. S Solstice AdminSuite 2.3. Solstice AdminSuite software provides an integrated collection of graphical user interfaces to perform administrative tasks such as managing hosts, users, groups, administrative data, file systems, disks, printers, and serial port devices. The Solaris operating system allows the OMC-R to be administered as a typical UNIX system.
138
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
The OMC-R database
The OMC-R database

RDBMS
The OMC-R database, maintained at the system processor, uses an industry standard Relational Database Management System (RDBMS) known as INFORMIX. The DBMS manages access to its own stored data and provides its own data protection. It is made up of a PM sub-schema and an EM sub-schema. The PM sub-schema is used for storing processed performance statistics from the GSM Network, while the EM sub-schema stores the subscription lists used to subscribe to incoming events and alarms (see Figure 1-19).
Database schema: defined

The OMC-R database may be thought of as a centralized data store for data that will need to be further manipulated, either by system users or other OMC-R application areas. A database schema is a data model of a precise, complete definition of the data to be stored. It provides a formal notation data model of tables, rows, columns, and keys. The tables in which the data is stored, are predefined by the database schema and their physical structure cannot be altered, only their contents can be manipulated.
RAW STATISTICS TABLES NETWORK CONFIGURATION TABLES
PM SUB-SCHEMA
PM REPORT TABLES
EM SUBSCRIPTION LISTS
EM SUB-SCHEMA
Figure 1-19 OMC-R database database schema breakdown
Database size
The database can be sized at installation to meet the requirements of the GSM Network. The disk is hardware mirrored to provide a high level of protection against loss of data in case of hardware failure.
EMOTOROLA LTD. 2000
139
The OMC-R database
ISSUE 18 REVISION 0
Applications and utilities

The management of the OMC-R database is accomplished using INFORMIX-OnLine utilities and OMC-R applications built around them. The OMC-R database supports the following applications: S Structured Query Language (SQL) and Applix access for custom reporting. SQL and Applix are industry standard languages, which can be used to write applications to extract performance management data from the database. Read-only access to the data is available. S Database back-up and administration utilities. The OMC-R system administrator is provided with a facility for on-line back-up of the OMC-R database. This avoids halting the OMC-R during routine back-up operations.
140
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
The CM MIB
The CM MIB
Configuration Data
The System Processor contains the CM Management Information Base (CM MIB) that holds all the configuration data needed for the network maps of the OMC-R MMI and for cell parameter optimisation. Information in the CM MIB includes lists of the various types of nodes in the GSM network, with their attributes and interconnections, as well as lists of maps containing nodes and connections on each map. All the MMI processors which run the NSS feature, communicate with the CM MIB using an internal process called cm_mib. The CM MIB can be populated with NE data by selecting: S S Audit. or Detailed View Forms (for each object).
EMOTOROLA LTD. 2000
141
The SPARCstation configuration
ISSUE 18 REVISION 0

Running the OMC-R MMI
SPARCstations are primarily concerned with running the OMC-R MMI. Typically the OMC-R configuration contains a single SPARCstation 20 or SPARCUltra 5/1, the GUI server, and several SPARCstation 5s known as GUI Client processors. The faster GUI server runs the GUI sessions while the slower machines run the display process only. Each SPARCstation is a complete UNIX system, which runs the same version. A typical configuration is shown in Figure 1-20.
SPARCUltra 5/1 MMI GUI SERVER SPARCstation 5 MMI GUI CLIENT SPARCstation 5 MMI GUI CLIENT LOCAL AREA NETWORK (LAN)
SPARCUltra 5/1 MMI GUI SERVER SPARCstation 5 MMI GUI CLIENT SPARCstation 5 MMI GUI CLIENT
TO SYSTEM PROCESSOR
Figure 1-20 OMC-R SPARCstation configuration
A standalone server
The OMC-R MMI expects all the SPARCstations to be configured as standalone NFS (Network File System) servers. The term server, used in this context, describes a central store for the software. This configuration allows each SPARC some degree of independence while still allowing resources to be shared.
LAN configurations
The SPARCstation 5s display the GUI and function as operator workstations. The OMC-R MMI software is made accessible over the LAN by configuring the SPARCstations in the following way: S A SPARCUltra1 is installed as a GUI Server to the SPARCstation 5s. This configuration allows the use of slower, older machines and the OMC-R GUI is made accessible to the 5s through NFS.
142
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Other configurations
Other network configurations may also exist, such as an MMI processor configured to run the OMC-R MMI from a remote site. In networks containing two OMC-Rs, a MMI processor in the local OMC-R is configured to monitor a remote OMC-R during the night shift (the local OMC-R is known as the night concentration centre).
EMOTOROLA LTD. 2000
143
MMI Processor
ISSUE 18 REVISION 0
MMI Processor
Server Client Relationship
Up to 10 additional processors can be added to the system. One of the machines must be configured as an GUI server. The additional machines mount the display software from the GUI server. The total number of GUI sessions supported is 10, as on the standard OMC-R. Each Processor will support one GUI session. An example of an GUI processor hardware configuration is shown in Table 1-6. The GUI processor will be configured with software as shown in Table 1-7. Table 1-6 GUI Processor hardware specifications Hardware Model Processor (CPU) Memory Disk Capacity Network CDROM Drives Printer Applicable to both Low End and High End Sparc 5 model 170E, Sparc Ultra 1 or Sparc Ultra 5 1 x 167MHz, 1 x 250MHz or 1 x 270 MHz 64 MB or 256 MB 1/2 x 2.1 or 4.2 Gbyte disk drives Ethernet. Twisted pair interface Internal CDROM drive. SMCC 3.5 1.44Mb Internal Floppy Network Printer Table 1-7 GUI Processor software specifications Software SUN Applicable to both Low End and High End Solaris 2.5.1 Solaris 2.5.1 OS patches Solstice Backup Client 5.1/Solstice AdminSuite 2.3 IConnect 7.13 UC2 X11 Release 5 Version 26 Motif 1.2.5G for SPARC 2.x single user licence Sun Solaris CDE 1.0.2 Ileaf Worldview 2.0.1 TCL Version 7.4 Expect Version 5.19 Applix 4.3 Wingz 1.4.1
Informix X11 Desktop Interleaf (GUI server only) TCL (GUI server only) Expect (GUI server only) Applix (GUI server only) Wingz
144
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
GUI Server
GUI Server
Overview
GSR2 (1.5.0.0) saw the introduction of GUI Servers and GUI clients alongside MMI Servers and MMI Clients, or as replacements for them. GSR4 (1.6.0.0) continues this trend, but with a higher minimum hardware specification to ensure adequate performance on the new release.
Display Processor Definitions

This matrix clarifies the differences between the MMI and GUI concepts. Table 1-8 Processor differences Processor GUI Files GUI Process GUI Display Number of processes per machine 1 1 N 1
MMI Server MMI Client GUI Server GUI Client
Local Remote Local Not applicable
Local Local Local Remote
Local Local Remote Local
The MMI Server and MMI Client machines have similar specifications, the MMI Server having additional RAM and disk space to enable it to serve files to the MMI Client. The GUI Server and GUI Client machines on the other hand are much more dissimilar the GUI Server being significantly more powerful to run the specified number of GUI sessions, the GUI Client simply acting as an X-display. For this reason, MMI Servers and MMI Clients can both be re-deployed as GUI clients, but only the high end MMI Server (Ultra 5) will have the power to run as a GUI Server.
EMOTOROLA LTD. 2000
145
GUI Client - SPARCstation 5
ISSUE 18 REVISION 0

Software configuration
The Sun Microsystems SPARCstation 5 (the operator workstations) displays the GUI. This GUI may be installed on either the System processor, or on a SPARCstations 20 that has been installed as a GUI server. In all cases the OMC-R MMI software is executed on the local SPARCstation 5s. A second SPARCstation 20 is also designated as a GUI server to half the GUI clients, giving redundancy in the event of a failure to a SPARCstation 20.
MMI PROCESSOR
SunOS MMI
OPERATOR WORKSTATION
Figure 1-21 SPARCstation 5/IPX hardware and software configuration
Hardware features
The SPARCstation 5s contain the following hardware features: S S Local Disk 535/424 Mb (minimum configuration). 20 inch colour terminal.
The SPARCstation 5s are complete UNIX systems and are loaded with the same UNIX operating system as the SPARCstation 20. They are usually configured as standalone NFS (Network File System) servers.
146
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Night concentration
Figure 1-22 shows a night concentration centre with one SPARCstation 20, which is configured as a GUI server for both region A and region B. This means that only one SPARCstation 20 is required.
PRINTER PRINTER GUI SERVER GUI SERVER GUI CLIENT SYSTEM PROCESSOR Leased Line Concentration centre Regional OMC-R A (local)
LAN
BRIDGE/ ROUTER
X.21
ROUTER
LAN
GUI SERVER (REGION A) GUI SERVER (REGION B)
PRINTER GUI SERVER GUI SERVER GUI CLIENT SYSTEM PROCESSOR Regional OMC-R B (Remote)
LAN
BRIDGE/ ROUTER
X.21
Figure 1-22 Night concentration configuration
EMOTOROLA LTD. 2000
147
The OMC-R MMI: overview
ISSUE 18 REVISION 0
The OMC-R MMI: overview

Graphical User Interface (GUI)
The OMC-R MMI provides a Graphical User Interface (GUI), which enables operators to easily interact with the OMC-R application software on the System Processor, and to carry out the various GSM network management functions. This means that apart from equipment repair and replacement, all site configuration changes, troubleshooting, audits, and network administration can be executed through a single focal point. The OMC-R GUI Front Panel and the icons are shown in Figure 1-23.
.1 1.6.1.3
Figure 1-23 T he OMCR GUI Front Panel
148
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
OMC-R front panel: overview
OMC-R front panel: overview

Icons
The OMC-R GUI Front Panel and the Expert panel contain the following icons: S S S S S S S S S S S S Console. Configuration Management (Config Mgmt). Event Management (Event Mgmt). Performance Management (Performance). Load Management (Load Mgmt). Find facility. Help. Xterm. Administration (Admin). Event Logs. Remote Login. Network Maps (Maps).
Other Front Panel icons

The system status display is positioned to the right of the icon controls. Counters indicate the number of each different alarm severity currently active throughout the system and the total number of alarms unhandled. S Alarms. This icon flashes if there is a new alarm, and audio indication is also given if the audio feature is enabled. Click on this icon to acknowledge the alarm and open an alarm window. Exit. Click on this button to exit from the OMC-R GUI.
Operator name
The operator name is displayed at the top left side of the GUI Front Panel. The operator name is assigned to the operators login ID in a set-up file. Management of the set-up file is the responsibility of the OMC-R System Administrator. For more information, refer to Operating Information: GSM System Operation (GSM-100-201) or Operating Information: Scaleable OMC-R System Administration (GSM-100-202).
Version number
The version number shows the OMC-R operating software version in use. The OMC-R operating software consists of two parts, the OMC-R MMI and the OMC-R application software. Both parts always have the same version number. The OMC-R operating software is usually compatible with two versions of NE operating software, for example, OMC-RGSM 1.6.0.0 is compatible with BSGSM 1.5.X.X.
Additional information
For complete information on the OMC-R Front Panel icons, refer to the OMC-R Online Help facility by clicking on the Help icon.
EMOTOROLA LTD. 2000
149
Using the front panel icons
ISSUE 18 REVISION 0

Console
Select this icon to display the OMC-R console window shown in Figure 1-24. This window is used to display information on OMC-R processes. Messages are displayed from the different processes of the OMC-R application software. A pop-up window is automatically displayed for all warning messages and to indicate an OMC-R process has failed.
Figure 1-24 OMC-R console window When the operator first displays the OMC-R console window, or when the options available on the OMC-R console menu bar are deselected, warning and information messages are displayed in the window.
Example console messages

Example messages which may be displayed in a console window are: S S At the start of an GUI session, a connection is established using the OMC-R Init process. If the connection fails a warning message will be displayed. When the MMI connection is successful a warning or information message will be displayed:
OMC-R Processes are initializing All Essential OMC-R Processes Have Been Started
S S
If an OMC-R process fails a warning message is displayed indicating which OMC-R process is affected. If the OMC-R Init process dies, a warning message is displayed, followed by an information message:
Restart the GUI to Reconnect to OMC-R Init Process
150
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Select this icon to display the Navigation Form. The Navigation Form gives a containment tree representation of all configurable objects. An object is any Network Element (NE) that can be configured from the Navigation Form. Information relating to the NE is stored at the CM Management Information Base (CM MIB). The attributes of the objects represented on the tree reflect their actual settings in the network. The attributes of these objects can be viewed, and changed using forms called Detailed Views. Cell parameters can be modified to improve the overall performance of the network. The changes can be propagated out onto the network using the audit function, but only if the object already exists or at the time of saving in an object detailed view. Audits are carried out to check if the same objects, and object attributes are consistent at the NE and the CM MIB.
Further Information
Refer to the Installation and Configuration: GSM System Configuration Manual, (GSM-100-403) for detailed information regarding Configuration procedures.
Event Management
Select this icon to monitor events and alarms generated by the NEs. The NEs report to the OMC-R through events. For example, an NE issues an event to the OMC-R to indicate that a statistics file is ready for collection. Alarms are a special type of event. Alarms are sent to indicate a fault condition, such as a communications failure. Groups of events and alarms are routed to the same display window through subscription lists. The main functions of Event Management are: S S S
EMOTOROLA LTD. 2000
Defining the subscription criteria for grouping event or alarm information. Monitoring any events or alarms subscribed to in an event or alarm display window. Handling alarms viewed in an alarm display window.
151
ISSUE 18 REVISION 0
Performance Management
Select this icon to gain access to the OMC-R Performance Management feature. This feature provides a pull down menu based window environment, based on Applix, to simplify data selection and give flexible report options. The Performance Management (PM) GUI also provides the Device Management of statistics for any Cell under the control of the OMC-R. PM GUI can also be accessed from the following: S S S Navigation tree. Network map. NE contained devices form.
152
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Load Management
The Software Load Management window will be displayed when the Load Management icon is selected on the OMC-R desktop panel. This window will display an overall view of the software load information for the entire network. The window, when opened, will be capable of displaying 25 NEs before a scrollbar is used.
Load Management options

For each NE, the following information is displayed: S S S S S S NE Name. NE Type. Download Enabled/Disabled. Complete Load Enabled/Disabled. Current and New software load. Current and New CSFP software load.
All software load related options currently available for an NE are selectable from pull down menus within this window. In addition, the NE Software form includes a field indicating if download is enabled or disabled. The default action for double clicking on an entry in the Load Management window opens the NE Detailed View form. Multiple selection will be permitted for the following menu options: S S S S Edit New Software Load. Edit New CSFP Software Load. Edit Download Enabled/Disabled. Edit Complete Load Enabled/Disabled.
When the Load Management window is opened, the entries in the window will be displayed in alphabetical order and according to NE type.
EMOTOROLA LTD. 2000
153
ISSUE 18 REVISION 0
Find
Select this icon to display the Find window. From this window the user can find NEs, Sites or Cells in the network by entering some or all of the following: S S S S S S S S S S NE Name Site Name Site Id Cell Name GSM Cell Id Open a Navigation Tree with the node found at its root Open a detailed view for a node Remote login (RLogin) Open a Contained Devices window for a node Open a map for a BSS
Once the NE, Site or Cell has been found the operator can do the following:
Refer to the manual Operating Information: GSM System Operation (GSM-100-201) for Find procedures.
Maps
Select this icon to display a scrollable map list. From this list display a map of all, or part of, the network. The network map shows Network Elements (NEs) and links on a solid colour background, or on a geographical background map (depending on what is set up by the network administrator). The operator monitors the state of the network from this window. The NEs and links are represented by different icon types, that is in-service, out-of-service and unknown state. Colours are used to represent the alarm states of the NEs. A change in the state of the node is represented by a different icon. Incoming alarms are reported by a colour change in the NE and link icons, and the Alarm icon flashing. An audible warning alarm is also available. The network map provides an option to display a Status Summary window which summarizes the alarm states in the NE, and details the administrative and operational states. The network map also provides Alarm Display windows for individual NEs displaying the incoming alarm messages enabling alarm handling to be performed. From the Options menu, it is possible to resynchronize alarm and state information for a device, or the complete network. Remote login to an NE is also available from the Options menu.
154
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Remote Login
This application enables the operator to have remote access to a Network Element. Select this icon to display a list of nodes on the network which can be logged into. Configuration of the BSS or RXCDR is done using TTY, Batch or Navigation tree. Refer to manual Technical Description: BSS Command Reference (GSM-100-321) for information on MMI commands.
Event logs
Select this icon to open a window for searching event logs. All events sent to the OMC-R are stored in Event Logs. It is possible to search and print Event Logs using this application. Logging of events can also be enabled or disabled from this application. A filtering option is also available to aid the search procedure.
EMOTOROLA LTD. 2000
155
ISSUE 18 REVISION 0
Administration
Select the Admin icon to view the Admin Options window. Administration is related to the audit and resync functions, which are also available in the Network and Configuration applications.
Administration options
The Admin Options window includes the following items: S Access Control - enables the OMC-R System Administrator to change the command partitioning options for all users. Depending on which security area the user has access to, they will be allowed/disallowed options on the OMC-R user interface that could be used to alter OMC-R/BSS information. Access control provides a level of safety so that OMC-R users cannot invoke commands accidentally/maliciously that they are not privileged to use, and also improves the way the OMC-R works by providing users with a more applicable selection of menu options from which to choose. S Audit Scheduler - enables the frequency of audits of the network to be scheduled. Select Audit Scheduler from the list to view the audit scheduler window. The audit scheduler window contains a list of all scheduled audits. Scheduled audits include Name, Status, Times, Types and Owner information. They can be one-shot or periodic. S Resync Scheduler - enables the frequency of a resync of the network to be scheduled. Select Resync Scheduler from the list to view the resync scheduler window. The resync scheduler window contains a list of all scheduled resyncs. Scheduled resyncs include Name, Status, Types, and Owner information. They can be one-shot or periodic. S PM Reports Scheduler - enables the frequency of a performance management report on the network to be scheduled. Select PM Reports Scheduler from the list to view the PM reports scheduler window. The reports scheduler window contains a list of all scheduled reports. Scheduled reports include Name, Status, Types, and Owner information. They can be one-shot or periodic. S S S S Audit Logs - enables the results of a network audit to be checked. Resync Logs - enables the results of a network resync to be checked. PM Reports Logs - enables performance management report logs to be checked. Audit Log Management - deletes Audit Logs after a predefined period of between 1 and 7 days.
If a scheduled audit or resync has not started, the operation can be deleted. If a scheduled audit and resync has already started, the scheduled operation can be aborted. The user can create, view, edit, and print scheduled audits and resyncs of the network, BSS, RXCDR, or SITE.
156
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Xterm
Selecting this icon opens an Xterm window. Multiple Xterm windows can be invoked; the limit is predefined by X window software.
Help
Select this icon to invoke the Online Help facility. Online Help for the Front Panel display and the Map function is provided. A Help option can also be selected from many of the windows shown throughout this manual. The Help option is described in the OMC-R Online Help facility.
Other front panel icons

The System Status Display is positioned to the right of the icon controls. Six counters indicate the corresponding numbers of each different severity of alarm currently active throughout the system, and the number of alarms that are Unhandled. There are two icons positioned beside the System Status Display:
Alarms
This icon flashes if there is a new alarm, and audio indication is also given if the audio feature is enabled (determined by the setting of the OMCAUDIBLESEVERITY environment variable). Click on this icon to acknowledge the alarm and open an alarm window. If there are no further alarms, the Alarm icon stops flashing.
EXIT
The EXIT soft button is located in the bottom right corner of the OMC-R front panel. When this button is clicked with the mouse, the user will be presented with a confirmation dialogue box, prompting the user to confirm that they wish to exit from the OMC-R front panel.
EMOTOROLA LTD. 2000
157
ISSUE 18 REVISION 0
158
EMOTOROLA LTD. 2000
Chapter 2
Getting Started
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
ii
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Chapter 2 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to Chapter 1 Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using a SPARCstation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitor controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging in to the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The RC.CNFG file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling resync on OMC startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Common Desktop Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CDE desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mouse button utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Right mouse button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Middle mouse button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Left mouse button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restarting/exiting the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restarting the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exiting the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Front panel icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Expert desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Find . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other Front panel icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running a remote MMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remotely running the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing an OMC MMI window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2000
i
21 21 21 21 22 23 23 23 23 24 24 24 25 25 25 27 27 27 28 28 29 29 29 210 211 211 211 211 212 213 213 214 215 216 217 217 218 218 219 219 220 220 220 221 221 221 222 222 222
iii
ISSUE 18 REVISION 0
Using window controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Peripheral controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Window menu buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the text editor xedit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening xedit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing a file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The edit commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
223 223 223 224 225 225 225 225 226
iv
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Introduction to Chapter 1 Getting started

Getting started
This chapter gives an introduction to operators of the Motorola GSM OMC detailing: S S S S S S S S S S S Logging in to the OMC. The Common Desktop Environment (CDE). Mouse button utilities. Restarting/exiting the GUI. Front panel icons. Running a remote MMI. Remotely running the OMC. Remote X-terminals. Printing an OMC window. Using window controls. Using the text editor xedit.
Terminology
Throughout this manual the following mouse terminology is used: S S S Click - means to press and release a button without moving the mouse. Double click - means to click a button twice in rapid succession. Drag - means to press a button, and hold the button while moving the mouse.
Using a SPARCstation overview

The SPARCstation colour monitor and SPARC system unit controls are shown in Figure 2-1, and described as follows: S S S S Use the BRIGHTNESS and CONTRAST controls to provide a screen display which is comfortable to view in existing ambient light conditions. Use the VERTICAL STATIC CONVERGENCE and HORIZONTAL STATIC CONVERGENCE controls to control the colour separation. Use the VERTICAL CENTRING control to set the vertical picture positioning. Set the monitor ON/OFF switch to ON, to apply the ac mains to the display. (The green LED Power On indicator on the monitor indicates that ac mains is available to the display). NOTE Figure 2-1 depicts a possible version of a SPARCstation; there can be some variations on the monitor controls.
EMOTOROLA LTD. 2000
21
ISSUE 18 REVISION 0
Monitor controls
This diagram shows the monitor controls for a SPARCstation. NOTE Later models of the SPARCstation may have some of the monitor controls replaced with a remote control device.
.
3.5 INCH SYST EM UNIT ON/OFF SWIT CH (AT REAR) MONIT OR ON/OFF SWIT CH
.
VERT ICAL ST AT IC CONVERGENCE POWER ON INDICAT OR SPARC 10/20 SYST EM UNIT ON/OFF SWIT CH (AT REAR) VERT ICAL CENT RING CONT RAST BRIGHT NESS
HORIZONT AL ST AT IC CONVERGENCE
Figure 2-1
SPARCstation monitor controls
22
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Logging in to the OMC

Prerequisite
Before attempting to log in (LOGIN) a valid account and password must be available.
Procedure
Log in to the OMC at the operator terminal as follows: omcuser 1. 2. Type in the omcuser ID and press the Return key, the omcuser ID is displayed as typed. Type in the password and press the Return key, the password is not displayed.
After switching ON or logging out, a login screen similar to Figure 2-2 displays. However, as the screen can be personalized it may have a different appearance.
trnmmi1 Login:
Figure 2-2
Login screen SPARCstation
Changing password
The password initially given with the ID should be changed immediately after the first successful LOGIN. The OMC processor password must be at least six characters long, and should consist of a mixture of alphabetic and numeric characters and symbols. Information on changing passwords can be obtained from the system administrator. It is important to change the password to something easily remembered but difficult to obtain. Do not use birthdays, first names or words which appear in a dictionary. The following are examples of passwords, suitable and unsuitable: S S
EMOTOROLA LTD. 2000
marion - is not a suitable password. mar10! - is much better.
23
ISSUE 18 REVISION 0
The RC.CNFG file

The RC.CNFG file is read by the ResyncController process on the system processor. The three options in the RC.CNFG file are detailed in Table 2-1. Table 2-1 OPTION ENABLERESYNC TIMER AUTORESYNC Description Used to enable or disable resync. Values Y/N Default: N
No. of seconds the OMC will 150 to 3600 wait for resync to complete. Default: 600 Used to enable or disable autoresyncs. Y/N Default: not set
Enabling resync
The OMC is shipped with resync disabled. To enable resync, edit the following file: /usr/gsm/config/global/RC.CNFG Change the following line:
ENABLERESYNC
to read:
ENABLERESYNC
Save the file and the change will then be picked up automatically.
Enabling resync on OMC startup

The OMC is shipped with resync on OMC startup disabled. Resync on OMC startup is a feature that results in a network resync being initiated every time the OMC starts up. To enable this feature the following steps should be followed : 1. 2. 3. 4. 5. 6. Select the Configuration Management icon from the GUI. Select the Network icon and open its Detailed View. Select Edit on the Network Detailed View. Change the Resync on Startup attribute to True. Select Save on the Network Detailed View. Exit the Network Detailed View. The resync on startup feature is now enabled.
24
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Common Desktop Environment

Introduction
The Common Desktop Environment (CDE) provides an industry standard desktop manager for the OMC and is provided on different SUN workstations. It supports operator configurable windows, reduced window clutter through the use of multiple panes, and a file manager which provides a graphical front end to the UNIX file system. A batch scheduler is also provided which allows the user to schedule cron jobs from the CDE. The different OMC users, such as root and omcadmin have customized desktop menus to enable them to quickly access some of the tool required to carry out their respective administrative and maintenance tasks on the OMC system.
CDE desktop
The CDE desktop enables each user to manage their work, providing windows, workspaces, controls, and the CDE Front Panel. A summary of the functionality provided is as follows: S S S S S Windows contain software applications and are framed with controls so that they can be moved, sized, or placed in additional workspaces. Workspaces are the screen areas where the user places the windows needed for work, arranges them, and closes them when done. Controls are provided to manipulate objects, select choices, or type information. Menus provide access to commands which manage windows and operate applications. The CDE Front Panel is a customizable collection of frequently used controls, available in every workspace.
CDE Front Panel

The CDE Front Panel provides controls, applications, and indicators used in everyday work. The CDE Front Panel also provides the workspace switch for selecting a workspace. For the root user the CDE Front Panel provides access to system administration utilities, such as add_user, add_group, add_host, Solstice Backup, and Port Manager. Extra workspaces can be created, for example a personal workspace is useful for keeping together all the tools and applications needed for weekly reports and other administrative tasks. This would prevent the workspace which contains the OMC applications from becoming cluttered.
File manager
File Manager which is accessible from the CDE Front Panel of the desktop provides a GUI to the UNIX file system, and can be used to create, find, and use workspace objects such as, files, folders, and applications. Each object is represented by an icon in File Manager. File Manager allows the user to do a number of things with these objects, for example, move, copy, open and delete.
EMOTOROLA LTD. 2000
25
ISSUE 18 REVISION 0
Style manager
Style manager is available from the CDE. It may be used to change desktop preferences such as colours, font, backdrop, keyboard click volume, mouse speed, screen lock, window behaviour and startup preferences.
Figure 2-3 Style Manager from the CDE desktop
26
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Mouse button utilities

Introduction
The mouse buttons can be used to access various utilities when logged in.
Right mouse button

The main functions available from the right mouse button (Figure 2-4), are the database load management utilities, and editor tools. Press and hold the right mouse button anywhere on the main screen background to view the Utilities menu. NOTE Not all the options shown below are always available; this menu can be configured by the System Administrator.
Figure 2-4
Default menu (using right mouse button)
EMOTOROLA LTD. 2000
27
ISSUE 18 REVISION 0
Middle mouse button

Press and hold the middle mouse button on the main background to view a default menu as displayed in Figure 2-5. These options allow the user to restart processes and utilities started during login. NOTE Not all the options shown below are always available; this menu can be configured by the System Administrator.
Figure 2-5 Default menu (using middle mouse button)
Left mouse button

Press and hold the left mouse button on the main background to view a default menu as displayed in Figure 2-6. These options are used to open new xterm windows and manipulate those already in existence. NOTE Not all the options shown below are always available; this menu can be configured by the System Administrator.
Figure 2-6 Default menu (using left mouse button)

28
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Restarting/exiting the GUI

Introduction
The Front Panel is automatically displayed after the login procedure is completed. However, there may be occasions where it is required to restart the Graphical User Interface (GUI).
Restarting the GUI

To restart the GUI the operator can click the middle mouse button to display the default menu and select StartGUI, or the following procedure can be used: 1. Double click on the Console window icon located bottom left of the desktop, to open the window. If the Console window icon is not visible, use the middle mouse button, and the Console option to select a new window. Enter the following command at the prompt: gui The GUI opens and the Front Panel is displayed. The window that the gui command was entered from will now function as a Console window for the GUI. No further UNIX commands can be entered in this window. If the command gui & is entered then the command is run in the background and UNIX commands can be entered in the normal way. 3. Minimize the window from which the GUI was started.
2.
EMOTOROLA LTD. 2000
29
ISSUE 18 REVISION 0
Exiting the GUI

To exit the GUI (that is, to close down the Front Panel and all processes associated with it) use the following procedure: Click on the Exit button located in the bottom right corner of the Front Panel display (Figure 2-7). The front panel display is closed, and all the processes initiated from the OMC are also closed down.
GSR4.1 - 1.6.1.0
Figure 2-7 Front Panel display In the confirmation window (Figure 2-8) click Yes to exit the GUI. Only the OMC and the associated MMI processes are closed by exiting in this manner.
Figure 2-8 Exiting GUI confirmation window
210
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Front panel icons
Front panel icons

Introduction
The Front Panel provides the top level controls (icons) and a display of the overall status of the network. Figure 2-7 shows the Front Panel display of the OMC. The name of the logged in operator is displayed at the top left of the Front Panel, and the software version number is shown below the operator name. The Front Panel includes ten GSM OMC icons, and an Xterm, Alarm and Help icon. Each icon represents a specific GSM OMC application. Click on an icon to select an OMC application.
Expert desktop
The Front Panel can be reduced in size to optimize screen coverage. To reduce the screen size of the Front Panel, right-click on the Front Panel and select Expert Desktop from the popup menu. The Front Panel is re-sized (Figure 2-9).
Figure 2-9 Expert desktop To return to the standard desktop, right-click on the expert desktop and select Standard Desktop from the popup menu. The standard desktop (NO TAG) is displayed.
Alarm summary
The alarm summary is not automatically shown within the expert desktop environment. To view the alarm summary window right-click on the expert desktop and select the Alarm Summary option from the popup menu. The Alarm Summary window (Figure 2-10) is displayed.
Figure 2-10 Alarm Summary window

EMOTOROLA LTD. 2000
211
Front panel icons
ISSUE 18 REVISION 0
Console
Select this icon to display the OMC Console window. This window is used to display information on OMC processes. Warning and information messages are displayed from the different processes of the OMC application software. A popup window is automatically displayed for all warning messages and to indicate an OMC process has failed.
Figure 2-11 OMC console window
Example console messages

Example messages which can be opened in a console window are: S S At the start of a GUI session, a connection is established using the OMC Init Process. If the connection fails a warning message is displayed. When the GUI connection is successful a warning or information message is displayed:
<Date + Time> NOTE: Connected to OMC Init Process
S S
If an OMC Process fails, a warning message is displayed indicating which OMC process is affected. If the OMC Init Process dies, a warning message is displayed, followed by an information message:
<Date + Time> WARNING: OMC Init Process is down Restart the MMI to Reconnect to OMC Init Process
212
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Front panel icons
Select this icon to display the Navigation Form. The Navigation Form is a family tree representation of all configurable objects. An object is any Network Element (NE) that is represented on the Navigation Form. Information relating to the NE is stored at the CM Management Information dataBase (MIB). Configuration is performed using detailed views. The attributes of the objects represented on the tree reflect their actual settings in the network. The attributes of these objects can be viewed, and changed using forms called Detailed Views. Cell parameters can be modified to improve the overall performance of the network, changes can be propagated out onto the network in two ways, using the audit function if the object already exists, or at the time of saving within an object detailed view. Audits are also carried out to ensure consistency between corresponding objects and their attributes at the NE and the CM MIB. Refer to the manual Installation & Configuration: GSM System Configuration, (GSM-100-403) for detailed information on Configuration procedures.
Event management
Select this icon to monitor events and alarms generated by the NEs. The NEs report to the OMC through events. For example, an NE issues an event to the OMC to inform it that a statistics file is ready for collection. Alarms are a special type of event. Alarms are sent to indicate a fault condition, such as a communications failure. Groups of events and alarms are filtered to display windows through subscription lists. The main functions of Event Management are: S S S Defining the subscription criteria for grouping event or alarm information. Monitoring any events or alarms subscribed to in an event or alarm display window. Handling alarms viewed in an alarm display window.
Refer to Event management: overview in Chapter 3 of this manual for an further information on Event Management functionality.
EMOTOROLA LTD. 2000
213
Front panel icons
ISSUE 18 REVISION 0
Select this icon to open the Performance Management window. The Performance Management window enables the user to produce reports specific to the performance of the network. Raw statistics are generated by an NE, collected and stored in the Performance Management(PM) database. Three main types of reports are provided: S S S Key statistics, which provide an indication of the quality of service being offered by the network. Raw statistics, which enables detailed analysis of performance. Raw statistics summaries reports (produces summary reports of a subset of raw statistics).
Reporting criteria can be selected, such as time period, number of cells, number of sites, and all reports can be output to the screen, file or printer. Refer to Performance management: overview in Chapter 7 of this manual for further information regarding Performance Management functionality.
214
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Front panel icons
Load management
This application enables the installation of new software loads, and deletion of old software loads. Select the Load Management icon to display the Software Load management window. S S in the Software Inventory Dialog window information is displayed on all software loads currently installed at the OMC. in the Software Load Management window a list is displayed of all BSS and RXCDRs in the system. Information is also displayed on software loads currently installed at each of the BSS and RXCDRs such as, Download, Complete Load, Current Software Load, New Software Load, Current CSFP Load and New CSFP Software Load statuses. Download Status is a dynamically updated window giving a status report on any software downloads in progress, with an option to abort. Upload Status is a dynamically updated window giving a status report on any software uploads in progress, with an option to abort.
S S
Refer to Load management: overview in Chapter 5 of this manual for further details on Load Management functionality.
EMOTOROLA LTD. 2000
215
Front panel icons
ISSUE 18 REVISION 0
Find
Select this icon to open the Find window. The Find feature is used to find NEs, Sites or Cells. The following information can be entered to find an NE, Site or Cell: S S S S S S S S S S NE Name. Site Name. Site Id. Cell Name. GSM Cell Id.
When the NE, Site or Cell has been found the operator can: Open the Navigation Tree with the node as its root. Open a Detailed View for a node. Perform a TTY Rlogin to a BSS. Open a Contained Devices window for a node. Open a Map for a BSS.
Refer to Finding a Network Element, Site or Cell in Chapter 4 of this manual for further details on Find functionality.
216
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Front panel icons
Maps
Select this icon to display a scrolling map list. From this list, select a map of all, or part of the network. The Network map shows Network Elements (NEs) and links on a solid colour background, or on a geographical background map (depending on what has been set up). The operator monitors the state of the network from this window. The NEs and links are represented by different icon types. Colours are used to represent the alarm states of the NEs. A change in the state of the node is represented by a different icon. Incoming alarms are reported by a colour change to the NE and link icons which are affected. The alarm icon on the Front Panel starts flashing. An audible warning alarm is also provided. The network map provides an option to open a Status Summary window which summarizes the alarm states in any selected NE. The network map also provides alarm/event display windows for selected NEs. These windows display the incoming alarm/event messages for an NE and allow alarm handling to be performed. From the Options menu, it is possible to resynchronize alarm and state information for a device, or the complete network. Remote login to a NE is also available from the Options menu. Refer to Using the map: overview in Chapter 2 of this manual for more information on the operation of the Network Management facility.
Remote Login
This application enables the operator to have remote access to a Network Element. Select this icon to display a list of nodes on the network which can be logged into. Programming the BSS or RXCDR is done using Base MMI commands. Rlogin provides three methods: TTY and Batch, which are command line based, or Forms, which is menu driven. Refer to manual Technical Description: BSS Command Reference, GSM-100-321 for information on Base MMI commands. Refer to Remote login in Chapter 4 for more information on Rlogin (TTY, Batch, or Forms methods).
EMOTOROLA LTD. 2000
217
Front panel icons
ISSUE 18 REVISION 0
Event logging
Select this icon to open a window for searching event logs. All events sent to the OMC are stored in Event Logs. It is possible to search and Print Event Logs using this application. Logging of events can also be enabled/disabled from this application. A filtering option is also available to aid the search procedure. Logging procedures are described in more detail in Logging of events in Chapter 3.
Administration
Select the Administration (Admin) icon to view the Admin Options window. Administration is related to the audit and resync functions, which are also available in the Network and Configuration applications. The Admin Options window includes the following eight items: S S Access Control - allows the setting of access to destructive command areas in the OMC. Audit Scheduler - enables an audit to be scheduled. Select Audit Scheduler from the list to view the audit scheduler window. The audit scheduler window contains a list of all scheduled audits. Scheduled audits require Name, Status, Times, Types and Owner information. They can be one off or periodic. Resync Scheduler - enables a resync to be scheduled. Select Resync Scheduler from the list to view the resync scheduler window. The resync scheduler window contains a list of all scheduled resyncs. Scheduled resyncs require Name, Status, Types, and Owner information. They can be one off or periodic. PM Report Scheduler - enables a performance management report to be scheduled. Audit Logs - displays the results of an audit. Resync Logs - displays the results of a resync. PM Report Logs - allows access to generated performance management reports. Audit Log Management to open audit log admin detailed view monitor.
S S S S S
If a scheduled audit or resync has not started, the operation can be deleted. If an audit and resync has started, the operation can be aborted through the respective log window. The user can create, view, edit, and print scheduled audits and resyncs of the network, BSS, RXCDR, or SITE. It is also possible to view and print audit logs and resync logs detailing the results of the operation. Refer to Administration: overview in Chapter 6 of this manual for more information on Admin functionality.
218
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Front panel icons
Help
Select this icon to invoke the Online Help facility. Online Help is provided for all features. A Help menu option can be selected from many of the windows shown throughout this manual.
Other Front panel icons

The System Status Display is positioned to the right of the icon controls. Five alarm severity counters are present each counter individually indicates the total number of alarms active throughout the system with a particular severity (see Chapter 3). A separate counter indicates the total number of unhandled alarms.
Xterm
Select this icon to open an Xterm window.
Alarms
This icon flashes if there is a new alarm, an audio indication is also given if the audio feature is enabled (determined by the setting of the OMCAUDIBLESEVERITY environment variable). Click on this icon to acknowledge the alarm. The alarm icon ceases flashing until the next alarm arrives. Alarms are described more detail in Checking alarms from the network map and other sections of Chapter 3 of this manual.
EMOTOROLA LTD. 2000
219
Running a remote MMI
ISSUE 18 REVISION 0
Running a remote MMI

Introduction
Where there is more than one OMC in the network, it is possible to hand over management of one OMC to another. This may be required during the night shift, and is known as night concentration.
Procedure
Use the following procedure to manage a remote OMC from a local MMI server processor: 1. Logout of the local MMI processor by entering the following command at the UNIX prompt: logout 2. Login to the local MMI processor using the remote user ID and password. Contact the OMC System Administrator for the user ID of the remote user. NOTE Only one OMC can be managed at any one time. To manage the local OMC when logged in as the remote user, it is necessary to logout of the remote OMC and login again as the local user.
220
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Remotely running the OMC
Remotely running the OMC

Introduction
The OMC GUI can be run using a workstation remotely located from the OMC.
Procedure
Use the following procedure to login and run the OMC GUI remotely: 1. 2. At the SPARCstation which will be used to run the GUI, login as described in Logging in to the OMC Open a UNIX shell and rlogin to the SPARCstation where the GUI to be run is located. To open a UNIX shell, click on the desktop, not in a window, and left click and select New Window from the popup menu, then release the left mouse button to open a shell window. 3. Set the environment variable DISPLAY to the local SPARCstation where the GUI is to be displayed, using one of the following commands: setenv DISPLAY <mmi_local>:0.0 where <mmi_local> is a recognizable host name on the remote SPARCstation. or setenv DISPLAY <address>:0.0 where <address> is the actual address for <mmi_local> in the /etc/hosts directory of the local SPARCstation. Example: setenv DISPLAY 111.1.11.1:0.0 4. Enter the following command to run the GUI: gui
EMOTOROLA LTD. 2000
221
Printing an OMC MMI window
ISSUE 18 REVISION 0
Printing an OMC MMI window

Introduction
An operator can print what is displayed in an X-window.
Procedure
Use the following procedure to print what is displayed in an X-window: 1. 2. 3. Position the window to be printed so that it is fully visible on the desktop. With the mouse pointer in the screen background area, select Print Window from the Root Menu popup menu. The mouse pointer will change to a +. Click in the window to be printed.
The system beeps once to indicate the start of the printing process and beeps twice to indicate the end of the process.
222
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Using window controls

Introduction
The window (Figure 2-12) shows the window controls that can be selected, using the mouse, at either the window peripheral controls or the window menu button.
WINDOW FRAME SECT ION WINDOW T IT LE BAR WINDOW MENU BUT T ON
MAXIMIZE MINIMIZE
SCROLL BAR
Figure 2-12 Window controls
NOTE Some windows do not have the scroll bar facility.
Peripheral controls
Use the window peripheral controls as follows: S S To move a window Click and hold the left mouse button in the window title bar and drag the mouse to move the window to a new position. To resize a window Click and hold the left mouse button in the window frame section and drag the mouse to size the window. The left or right sections will size horizontally while the top or bottom sections size vertically. The corner sections will size horizontally and vertically simultaneously. To minimize (iconize) a window Click with the left mouse button on the window Minimize button. To maximize/ restore a window Click with the left mouse button on the window Maximize/ Restore button. (The window occupies the full screen). To raise a window Click with the left mouse button on any part of the window.
S S S
EMOTOROLA LTD. 2000
223
ISSUE 18 REVISION 0
Window menu buttons

Click on the Window menu button with the left mouse button to access the Window menu. Window menu options are as follows: S S Restore is shown greyed out as the window is currently restored. Move. Move is indicated by the cursor.
Selecting this option by clicking on the left mouse button allows the window to be moved by moving the mouse. Clicking a second time sets the position. S Size. Size is indicated by the cursor.
Moving the cursor to an edge or corner of the window provides the sizing cursor. Clicking a second time sets the size of the window. S S S S S S S Minimize changes the window to an icon. Maximize enlarges the window to full screen size. Lower moves the window below the other windows on the screen. Occupy Workspace opens up occupy workspace window. Occupy All Workspaces opens up the window in all workspaces. Unoccupy Workspace removes the window from the workspace. Close where there is a Close option within the OMC application window (for example, as a button or as an option in the File menu) then the Close option on the window menu is inoperative. For many OMC application windows the procedure to close them is to select File Close from the window menu bar.
224
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Using the text editor xedit

Introduction
The SPARCstations are provided with an industry standard text editor, xedit. The text editor provides an easy to use window for creating and editing files without the need to use one of the command driven UNIX editors such as vi.
Opening xedit
To open the text editor xedit: From the SPARCstation background, with the mouse cursor not in a window, click the right mouse button and select X editor from the popup menu. The xedit window (Figure 2-13) is displayed. xedit Quit Save Load Use Control-S and Control-R to search
no file yet
Figure 2-13 An xedit window
Editing a file
The xedit window is divided into four areas, as follows: S Commands section. A set of command buttons which allow the operator to carry out the functions described in the next subsection. S S S Message window. Displays xedit messages. In addition, this window can be used as a scratch pad. Filename display. Displays the name of the file currently being edited. Edit window. Displays the text of the file that is being edited or created.
EMOTOROLA LTD. 2000
225
ISSUE 18 REVISION 0
The edit commands

The following command buttons are provided: S Quit. Quits the current editing session. If any changes have not been saved, textedit displays a warning message and allows the file to be saved. S Save. Stores a copy of the original, unedited file and then overwrites the original file with the edited contents. S Load. Loads the specified file and displays it in the Edit window. Control character key sequences can be used to edit the text within the Edit Window. See the xedit user manual for further details.
226
EMOTOROLA LTD. 2000
Chapter 3
Network Management
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
ii
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Chapter 3 Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The network status summary (NSS) feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How the network status summary feature works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Map process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The EM proxy process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Different maps available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Map modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Consolidated alarm report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Map configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The map display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Map backgrounds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Map links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . State changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The alarms icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview to alarms icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm display window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The alarm summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of alarm summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How administrative and operational state changes work . . . . . . . . . . . . . . . . . . . . . . . . . . State changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How alarms work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Colours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How maps are configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to the CMMIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Two object groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Graphic objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Graphic objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MapNode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MapLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
31 31 31 32 32 32 33 34 34 34 35 35 35 36 36 36 36 36 37 38 38 38 38 39 39 39 310 310 311 311 312 313 313 313 314 314 314 314 314
EMOTOROLA LTD. 2000
iii
ISSUE 18 REVISION 0
Configuration objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CommsLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ProxyCell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UserProfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automatically created network objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automatically created map display objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
315 315 315 316 316 316 316 316 316 316 317 318 318 318 319 319 320 320
iv
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
The network status summary (NSS) feature
The network status summary (NSS) feature

Maps
The role of the OMC in a GSM network is to allow network operators to perform network management functions to ensure that the network operates efficiently, and to ensure that the service to the customer is maintained. The OMC acts as a central collection point for measurement data used in the analysis of current performance and future planning of the network.
Features
The NSS features are as follows (refer to Figure 3-1): S S S Network maps. Alarms icon. Alarm summary.
Alarm summary
4.1 1.6.1.0
Launches network maps
Incoming alarms indicator
Figure 3-1 The network status summary options on the MMI front panel
EMOTOROLA LTD. 2000
31
How the network status summary feature works
ISSUE 18 REVISION 0

Map process
When a network map, for example, Network 1600b: Device Mode (see Figure 3-2), is selected via the Maps icon on the OMC front panel, a map process is invoked on the MMI processor.
MAP_ALARMS
State change events FROM NETWORK
MAP_EVENTS ALM_ALARMS
CM MIB
Test-Network map MAPNODES MAPLINKS MMI FRONT PANEL
Alarm events
Active NSS subscription list
EM Proxy MMI PROCESSOR
SYSTEM PROCESSOR
Figure 3-2 Map processes
Configuration data
All the configuration data needed to run the network map are stored in the CM MIB, which is maintained on the OMC System Processor. The CM MIB stores a series of managed objects to which relevant network configuration data and data needed to configure maps are assigned. For example, both a BSS and a Map are regarded as managed objects with different data. All the MMI processors that run the network maps communicate with the CM MIB using an internal process called cm_mib.
32
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
The EM proxy process

The EM Proxy process contains a list of all NEs, sites, cells, and links. The process examines the incoming alarm messages and compares it to the list. It updates the list if a change has occurred. Every two seconds a changed list is forwarded to the MMI processor. The list contains attributes which reflect the severity of the alarm and its handling state. These in turn update the Alarm Summary on the MMI front panel, and the attributes of the links and nodes on the active map, as configured in the CM MIB. The Contained Devices form and alarm icons are also updated. Similarly, incoming StateChangedEvents from SITEs and MMSs change the state of the attributes in the CM MIB. This reflects the administrative and operational states of the different SITE and CommsLink configuration objects, representing the physical devices in the network.
EMOTOROLA LTD. 2000
33
Network maps
ISSUE 18 REVISION 0
Network maps
Functionality
Network maps show status information on the network and enable the following different types of functionality to be invoked for a selected NE:
Current network configuration

Network maps present the current network topology. Network configurations can be updated using the Detailed Views and an Audit, initiated to ensure consistency between the MIB and the Network. A full network map, which displays all NEs and links in the network is available. Each NE can be expanded to show the SITEs and links within the NE. Maps can be zoomed or expanded when displayed, (refer to Figure 3-2). If the system is configured, more detailed maps of any part of the network can be displayed.
Alarm state
Incoming alarms are reported by a colour change in the NE and link icons on the map. The alarms icon on the front panel will also flash, and where available, there will be an audible warning.
MMS and SITE service states

The map display uses three different icon types to represent state changes in SITEs (represented by SITE map nodes) and MMS devices (represented by map links). Refer to State Changes in the Map Display section. The icon types represent in service (INS), out of service (OOS), and unknown states. These are determined by the operational and administrative states of the SITE or MMS.
An alarm display window for an NE or SITE on the map

Each map provides an alarm display window that subscribes only to incoming alarm messages for selected NEs or SITEs. This window allows standard alarm handling to be performed.
Remote login via TTY window for an NE on the map

Remote login, via a TTY window for a selected NE, allows BSS MMI commands to be sent to the NE. The responses to the commands can be monitored.
Provide resynchronization functions

The system checks the active alarm list for any unhandled alarms and retransmits any state changes that have occurred since the previous Resync operation.
Different maps available

The following maps are available for selection: S S One map showing the full network configuration, containing all configured nodes and links. One map for each BSS or RXCDR, containing all configured SITEs and links.
All other maps can be configured by the administrator.

34
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Network maps
Map modes
There are two map modes available from the View menu: S S Device Mode displays severities according to the impact of faults on devices. For example, a critical redundant device will produce a critical severity. Subscriber Mode displays severities according to the impact of faults on subscribers. For example, service, capacity or redundancy loss.
Consolidated alarm report

Consolidated alarm reports provide information about the OMC map so that the operator can identify problems in the network. This feature reduces the amount of alarms reported to the operator, and consolidates all the information relating to a failure in a report.
Map configuration
Different maps of the network can be displayed, depending on what type of information the operator needs to monitor. This is achieved by adding the new map configuration data to the CM MIB through the Detailed View forms and Audit. The OMC GUI provides facilities for the automated process, followed by operator input for longitude and latitude data. When the MIB is initially populated with data from configuration files, default maps are created. In the absence of any geographical map background files, the maps are displayed on a default map background consisting of a single solid colour. To use map backgrounds other than the default, a background map, usually a geographical map, is assigned to the map object which configures the network map.
EMOTOROLA LTD. 2000
35
The map display
ISSUE 18 REVISION 0
The map display

Map backgrounds
When maps are initially configured they are displayed on a default map background of a single solid colour. A background, usually a geographical map background, is assigned to the network map. Each map background is specified when defining the MapNode object. This map points to a physical file describing the actual shape of the background map.
Map links
Each map link represents one or more 2 Mbit/s links between the NEs or SITEs in the network. This is set when the map is configured. A cluster icon is used to represent a group of icons which are too close together to be displayed separately on the map.
Alarm reporting
If an icon on a map is flashing, it indicates that there are unhandled alarms for the device or devices it contains. Alarms from links cause both the link and the node, where the faulty MSI/MMS is contained, to flash. The icon colour will automatically be reset to the colour representing Clear (defaulted to green) when the operator clears the alarm, or an alarm clear message is received from the network.
State changes
The status of a SITE or MMS in the network determines whether it is in service (INS), that is, it is supporting (or able to support) user traffic, or out of service (OOS), that is, it is unable to support user traffic. The device status is determined by the administrative state (controlled by the operator) and the operational state (controlled by the NE fault management application). The different combinations of operational and administrative states determine whether the node or link is INS, OOS, or has an unknown state. For example, a SITE is INS if its operational state is enabled or busy, and its administrative state is unlocked. The normal state of a device is INS (busy/unlocked, or enabled/unlocked for a redundant device). An operator or the NE fault management software can take a device OOS by issuing a LOCK command, or a SHUT-DOWN command in the case of a DRI/RCU. A LOCK is intrusive as it terminates all activity on the device when the command is executed. The SHUTDOWN command permits the operator to specify a time interval before the device changes from UNLOCKED to LOCKED state. The map display uses different icon types to represent a change in state of devices. The following are indications of the icons for an INS, Unknown and OOS device:
An INS RXCDR
An Unknown RXCDR
36
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
The map display
An OOS RXCDR
Refer to the OMC Online Help facility for a complete description of the network map display, the subscription lists that control alarm and state changes, and icon colours.
EMOTOROLA LTD. 2000
37
The alarms icon
ISSUE 18 REVISION 0
The alarms icon

Overview to alarms icon
The Alarms icon is a network level indicator that flashes and emits an audible warning (where available) when new alarms are received at the OMC. The alarm summary situated to the left of the Alarms icon is simultaneously updated when alarms are received.
Alarm display window

The alarm display window can be opened by double clicking the alarms icon on the front panel with the mouse (Figure 3-3). A single click on the alarms icon will stop any audible alarms that are ringing. All the active alarm messages originating from the selected NE or SITE in the network will be displayed in the window, where the operator can handle faults. Figure 3-3 shows the alarm display with an alarm highlighted, and the popup menu that is available when the user clicks the right mouse button in the alarm display window.
Figure 3-3 Alarm display window
Refer to the OMC Online Help facility for more information on the alarm display window. The alarms subscribed to in the subscription list, which routes alarms to the display window, can be changed. Refer to Operation Information: GSM System Operation (GSM-100-201).
38
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
The alarm summary
The alarm summary

Overview of alarm summary
The alarm summary lists alarms of different severities in the network, and the number of unhandled alarms.
Display
The Alarm Summary (Figure 3-4) is displayed on the right side of the GUI front panel. It contains the following: S An up-to-date count of the different severities of the alarms in the Network. This list updates continuously to reflect incoming alarms, changes in alarm severity, or if the handling state of an alarm changes to Clear. S The number of unhandled alarms at the OMC.
ALARM SUMMARY
GSR 4.1 1.6.1.0
Figure 3-4 The alarm summary
EMOTOROLA LTD. 2000
39
How administrative and operational state changes work
ISSUE 18 REVISION 0
How administrative and operational state changes work

State changes
Administrative and operational state changes are only relevant for SITEs and links on the map. Figure 3-5 illustrates how the icons representing the SITEs or links are changed to reflect the change in state of the physical device.
MAP ON OPERATOR WORKSTATION
ICON REPRESENTING BTS1 ON THE MAP CHANGES TO OOS STATE
MAPNODE (BTS1) GUIState INS UNKNOWN OOS
MMI FRONT PANEL MAP MAPNODES (BTS1) MAPLINKS
MMI PROCESSOR
BTS1 OpState: Enabled AdminState: Locked GUIState:
Disabled Unlocked OOS
Busy Shutting Down | Not Equipped Unknown
OOS
INS
NETWORK OMC MSC BSS1 RXCDR BSS2 BTS1 MSI1 MMS1COMMSLINK
CM MIB
REPRESENTS PREVIOUS ATTRIBUTE SETTING
REPRESENTS NEW ATTRIBUTE SETTING
EM PROXY
StateChangeEvent SYSTEM PROCESSOR

MAP_EVENTS
ACTIVE NSS SUBSCRIPTION LISTS StateChangeEvent

(OPERATIONAL STATE OF BTS1 CHANGES TO DISABLED)
Figure 3-5 State changes on the map
310
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
How alarms work
How alarms work

Alarm icons
Incoming alarms are reported by a flashing MapNode or MapLink icon, coloured to represent different alarm severities. If an icon on a map is flashing, it denotes the presence of unhandled alarms for the device or devices it represents. Alarms from links cause both the MapLink and the MapNode containing the faulty MMS to flash and change colour.
1. ICON REPRESENTING BTS1 ON THE MAP CHANGES COLOUR TO RED AND STARTS FLASHING. ALARMS ICON ON MMI FRONT PANEL STARTS FLASHING. ALARMS SUMMARY WINDOW UPDATED.
MAP ON OPERATOR WORKSTATION
2.
MMI PROCESSOR MapNode (BTS1) Colour GUIState Flashing Yellow Blue Pink Turquoise Green Yes No Red MMI FRONT PANEL MAP MAPNODES (BTS1) MAPLINKS
BTS1 ALARM 001 AlarmState: Being Handled | Not Being Handled AlarmSeverity: Critical | Major | Minor | Warning | Investigate | Clear [message fields] ALARM 002 AlarmState: Being Handled | Not Being Handled AlarmSeverity: Critical | Major | Minor | Warning | Investigate | Clear [message fields] ALARM 003 AlarmState: Being Handled | Not Being Handled AlarmSeverity: Critical | Major | Minor | Warning | Investigate | Clear [message fields]
CRITICAL NOT HANDLED
CM MIB ALARM INFORMATION
EM PROXY CRITICAL ALARM EVENT

MAP_ALARMS ALM_ALARMS
Represents the previous attribute setting Represents new attribute setting (ALARM RECEIVED FROM BTS 1) CRITICAL ALARM EVENT
ACTIVE NSS SUBSCRIPTION LISTS SYSTEM PROCESSOR
Figure 3-6 Alarms and how they change on the map

EMOTOROLA LTD. 2000
311
How alarms work
ISSUE 18 REVISION 0
Colours
The colour of any displayed icon or link reflects the severity of alarms in the device or group of devices represented by the icon. The default colours are defined in Table 3-1. Table 3-1 Colour Red Yellow Blue Pink Turquoise Green Alarm Severity Critical Major Minor Warning Investigate Clear (no alarms) Default ON ON OFF OFF OFF n/a (always on)
When an icon represents a group of devices, (for example, a BSS represents all the devices in the BSC and BTSs within the BSS) an alarm occurrence in any device within the group will be shown at the displayed icon. In the event of alarms of different severities existing for the same device, or group of devices the display colour reflects the most severe alarm condition. The icon colour will automatically be reset to the Clear colour when the operator clears the alarm or an alarm clear message is received from the network.
312
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
How maps are configured
How maps are configured

Introduction to the CMMIB
The CM MIB stores a series of managed objects to which relevant configuration data is assigned. For example, both a BSS and a Map are considered to be managed objects requiring different data. All the MMI processors that run the Network Map communicate with the CM MIB using an internal process called cm_mib.
GRAPHIC OBJECTS
MAP NODE
MAP
MAP LINK
CONFIGURATION OBJECTS
NETWORK OMC BSS RXCDR MSC SITE MSI MMS RTF DRI CELL
COMMSLINK
Figure 3-7 The CM MIB showing the different groups of managed objects
Two object groups

There are two different groups of objects needed for maps: S Graphic objects. Used to build the different maps, and which take their data from the configuration objects. S Configuration objects. Hold all the data about the physical network. There is a containment relationship between the different managed objects.
EMOTOROLA LTD. 2000
313
Graphic objects
ISSUE 18 REVISION 0
Graphic objects
Graphic objects
There are three graphic objects in the CM MIB. Figure 3-8 shows the containment relationship between the graphic objects.
MAP
MAPNODE
MAPLINK
Figure 3-8 The containment relationship for the graphic objects
Map
The Map graphic object represents a map which appears in the Map List Display menu on selecting the Maps icon from the front panel. It defines the map name and the background map used with it.
MapNode
The MapNode graphic object specifies the type of NE or SITE to be represented on the map. A MapNode can represent any of the following configuration objects: OMC MSC RXCDR BSC BSCBTS BTS
MapLink
The MapLink graphic object represents one or more CommsLinks.
314
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Configuration objects
The containment relationship between the different configuration objects is shown in Figure 3-9. The objects are grouped into four logical groups, namely, Hardware Devices, Software Functions, Logical Links, and Radio Frequency. This reflects the physical configuration of the devices in the network, and determines the upward propagation of alarms. For example, an alarm from an MSI object will also be propagated to its parent SITE, which in turn is propagated to its parent BSS.
Map ProxyCell MapNode MapLink Network UserProfile
CM MIB
BSS RXCDR CommsLink MSC OMC SWInventory PCU NESoftware SITE SoftwareLoad
Hardware Devices
Software Functions
Logical Links
Radio Frequency
BTF
LCF
OMF
RSL
PATH
RTFGroup DRIGroupCELL RTF DRI
Cabinet CAGE
EAS
Processors
COMB
KSWpair
GCLK
IAS
LAN
TDM
MSI
GPROC
BSP
CSFP
FreqHopSys SMSCBmsg Neighbour TestNeighbourHandover/ TRX Power Control
* The Handover Control Objects are: RelTimAdvHC, RxlevDlHC, RxlevUlHC, RxqualDlHC, RxqualUlHC, SurrndCellHC ** The Power Control Objects are : RxlevDlPC, RxlevUlPC, RxqualDlPC, RxqualUlPC
Figure 3-9 The containment relationship for the configuration objects
Network
The Network configuration object represents the overall network being managed. There is only one Network configuration object in the MIB, and it is already configured on delivery.
EMOTOROLA LTD. 2000
315
ISSUE 18 REVISION 0
OMC
The OMC configuration object represents the Operations and Maintenance Centre. There is usually only one OMC object in the MIB.
SoftwareLoad
The SoftwareLoad object is used to point to a BSS or RXCDR software load currently stored in the OMC. A maximum of 2 147 483 647 SoftwareLoad objects can be contained within a SWInventory object.
MSC
The MSC configuration object represents the Mobile Switching Centre. The OMC does not directly manage the MSC, but manages the links between the BSSs, RXCDRs, and the MSC. There are usually only two of these objects in the MIB.
BSS
The BSS configuration object represents the Base Station System. Each BSS in the physical network (maximum of 120) is represented by an object.
RXCDR
The RXCDR configuration object represents the Remote Transcoder. There are as many of these objects as exist in the physical network (maximum of 120).
CommsLink
The CommsLink configuration object defines the two MMS ports in the different SITES that establish the 2 Mbit/s link between the SITES.
PCU
The Packet Control Unit (PCU) configuration object manages the packet radio interface, and also enables the interface from the BSS to the Serving GPRS Support Node (SGSN).
SITE
The SITE configuration object represents a BSS SITE in the network. The functionality of any given SITE depends on the devices it contains.
Hardware configuration
All the different hardware cages in a SITE are connected by a LAN, and configured as a BSC, a BTS, or a collocated BSC-BTS. SITE 0 must always contain the BSC functionality, and is configured as a BSC or a BSCBTS. The remaining SITEs may only be configured as BTSs. There are as many of these objects as exist in the physical network (maximum of 100 per BSS). An RXCDR can also have a SITE 0 associated with it.
316
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Hardware Devices
The Hardware Devices represent an abstract logical container class. It is used to group the different hardware devices on the BSS.
Cabinet
The cabinet object class describes a single cabinet within the site.
Cage
The cage object describes a single cage within a cabinet.
EAS
The EAS configuration object represents the detection of a single External Alarm System device within the site.
Processors
The processors object represents a logical container class. It provides a grouping for the GPROC (Generic Processor Boards) BSP (Base Site Control) and CSFP (Code Storage Facility) processors within the site.
KSWpair
The KSWpair object is used to represent a pair of KSW (Kiloport Switch board) devices which manage a single TDM highway.
GCLK
The GCLK object represent a Generic clock board. There is one per site.
IAS
The IAS configuration object represents the detection of an Internal Alarm Systems such as a power supply failure. There is one IAS device per cabinet.
LAN
The LAN object represents a single Local Area Network within a site.
TDM
The TDM object represents a single Time Division Multiplex highway within a site.
MSI
The MSI configuration object represents a Multiple Serial Interface (MSI) board which controls two MMS ports. There is a maximum of 101 MSIs at SITE 0 and 51 at other SITES.
EMOTOROLA LTD. 2000
317
ISSUE 18 REVISION 0
Software Functions
The Software Functions represent an abstract logical container class. It is used to group the different software functions on the BSC.
BTF
The BTF object represents a Base Transceiver Function. There is a single instance of this class in BSC site 0.
LCF
The LCF object represents a Link Control Function. There is a single instance of this class in BSC site 0.
OMF
The OMF object represents a OMF GPROC Function. There is a single instance of this class in BSC site 0.
Logical Links
The Logical Links represent an abstract logical container class. It provides the grouping for the various links present at the site.
RSL
The RSL represent a Radio Signalling Link. The RSL can only be contained within the remote BTS in which it terminates.
PATH
The PATH object specifies the path connection between a BSC and a specific BTS site. The path connection is described as a series of MMS connections between sites. There can be a maximum of 10 PATH objects contained in a SITE object.
Radio Frequency
The Radio Frequency represent an abstract logical container class. This provides the grouping for the various radio related objects.
RTFGroup
The RTFGroup object is used to represent a single RTF function grouping within a site. A maximum of 6 RTFGroup objects can be contained in a SITE object.
RTF
The RTF object is used to represent a single RTF function within a site. A maximum of 25 RTF objects can be contained in an RTFGroup object.
DRIGroup
The DRIGroup object is used to represent a single DRI device grouping within a site. It contains one or more DRIs which are connected to the same antenna and use the same portion of the TDM highway. A maximum of 6 DRIGroup objects can be contained in a SITE object.
318
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
DRI
The DRI object is used to represent a single Digital Radio Interface (DRI) device within a site. It provides the interface between the (D)RCU and the digital portion of a BSS. A maximum of 25 DRI objects can be contained in a DRIGroup object.
CELL
The CELL object is used to describe the cells within a BTS site. Up to 6 CELL objects can be created under a SITE object. A maximum of 250 CELLs can be contained within a BSS.
FreqHopSys
The FreqHopSys object is used to represent a single frequency hopping system within a cell.
SMSCBmsg
The SMSCBmsg object is used to represent a single Short Message Cell Broadcast (SMS CB) message within a cell.
Neighbour
The Neighbour object is used to identify a neighbour cell for a specific cell, that is, those cells to which it can handover calls. A maximum of 64 Neighbour objects can be created under a CELL object.
TestNeighbour
The TestNeighbour object is used to describe the test neighbour cells for a specific cell. One instance of this class represents one test neighbour cell.
Handover Control
Handover Control objects are RelTimAdvHC, RxlevDlHC, RxlevUlHC, RxqualDlHC, RxqualUlHC and SurrndCellHC. These objects describe the handover algorithms based on certain criteria. For more details refer to the OMC Online Help.
Power Control
Power Control objects are RxlevDlPC, RxlevUlPC, RxqualDlPC and RxqualUlPC. These objects describe the power control algorithms based on certain criteria. For more details refer to the OMC Online Help.
InterferAlg
The InterferAlg object is used to represent a single interference algorithm in a cell. Only one InterferAlg object can be contained in a CELL object.
ProxyCell
The ProxyCell object represents CELLs outside the current PLMN. A maximum of 500 ProxyCell objects can be contained in a SITE object.
UserProfile
The UserProfile object represents an OMC user who uses the OMC GUI. A maximum of 256 UserProfile objects can be contained in an OMC object.
EMOTOROLA LTD. 2000
319
ISSUE 18 REVISION 0
Automatically created network objects

The network objects which the cmMIB process creates automatically are as follows:
NESoftware
An NESoftware object is automatically created when a BSS or RXCDR object is created.
SWInventory
An SWInventory object is automatically created when an OMC object, with the active flag set to TRUE, is created.
MMS
An MMS object is automatically created when an MSI object is created.
TRX
A TRX object is automatically created in a CELL object when an RTF object of type BCCH is created at a SITE with its carrier attribute assigned to the relevant CELL.
Source
A Source object is automatically created when a Neighbour object is created if the CELL it identifies exists. Otherwise, a Source object is automatically created when the CELL object is created.
Automatically created map display objects

The map display objects which the cmMIB process creates automatically are as follows:
Map
A Map object is automatically created when a Network, BSS or RXCDR object is created.
MapNode
A MapNode object is automatically created when a BSS, OMC, MSC, RXCDR or SITE object is created and must be associated with an object of the relevant type.
MapLink
A MapLink object is automatically created when a CommsLink object is created.
320
EMOTOROLA LTD. 2000
Chapter 4
Map and Tree Procedures
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
ii
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Chapter 4 Map and Tree Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Using the map: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shared procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening and closing a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Closing a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Map display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Map modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscriber mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Colour legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm severity colours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Moving and expanding nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Expanding a node cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Moving a node on the map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Expanding an NE map node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Node detailed view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contracting a map node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contained devices report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Organizing map nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Organize Nodes function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing map levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Zooming a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Zooming in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Zooming out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging in remotely from a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote login to a NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . No connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resync from a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resync a node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resync logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resync network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . No connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2000
i
41 41 41 41 42 43 43 44 45 45 45 46 47 48 49 49 411 411 411 411 411 412 413 413 414 414 415 415 415 416 416 416 416 417 417 417 418 418 418 418 419 419 419 419 419 419 419
iii
ISSUE 18 REVISION 0
Viewing alarms from a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing alarms from popup menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing OOS devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing network OOS devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing node OOS devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing OOS devices from popup menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing a detailed view from a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing a detailed view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before deleting a map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Moving from a map to the navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the navigation tree: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening and closing a navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening the navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Closing the navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Moving levels on a navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Panner and porthole . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the autoclose function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault management from navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Lock a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unlock a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shutdown a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INS a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reset a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reset a Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reassign a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Swap a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Devices supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking device status from the navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
420 420 420 420 421 422 422 422 422 423 424 424 424 425 426 426 426 427 427 427 428 428 428 429 429 429 430 430 430 430 432 432 432 432 433 433 433 434 434 435 435 435 436 437 438 440 440 440 440
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Displaying OOS devices from the navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing OOS devices via the popup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing a navigation tree diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
441 441 441 442 442 443 443 443
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
vi
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Using the map: overview

Introduction
Selecting the Maps icon from the front panel displays the Map list. The Map list window contains a list of network map names. The list includes default maps and user-defined maps. Default maps are automatically generated by the system when the NEs are created using the configuration application. A full network map, and maps for each RXCDR and BSS in the network are created by default. A full network map displays BSS, RXCDR, OMC, MSC and Commslinks. BSS and RXCDR objects can be expanded to view SITEs. Maps may be either geographical or logical (no background). User-defined maps are typically set-up with a background geographical map of a particular region. The network map overlaid on the background geographical map contains the NEs of that specific region. User-defined maps are ordered, set up, and configured by the operator. NOTE Under no circumstances should the files SITE.map and NE.map be manually altered. Alteration of these files will cause serious errors.
Procedure list
The following is a list of general procedures for using maps: S S S S S S S S S S S S S Opening and closing a map. Moving and expanding map nodes. Organizing map nodes. Viewing next and previous map levels. Zooming a map. Printing a map. Logging in remotely from a map. Performing a resync from a map. Viewing alarms from a map. Viewing OOS devices. Viewing a detailed view or node status from a map. Moving from a map to the navigation tree. Deleting a map.
Shared procedures
The following procedures may be performed from either the Navigation Tree or the Map using the same methods. S S S S S
EMOTOROLA LTD. 2000
Viewing contained devices. Fault management. Load management. Viewing events and alarms. Viewing channel status.
41
ISSUE 18 REVISION 0
Further information
Further information on using the Network maps can be found in Online Help. Information on how the Network maps are set-up and configured can be found in Installation & Configuration: GSM System Configuration (GSM-100-403).
42
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Opening and closing a map

Opening a map
To open a Network map: 1. Select the Maps icon on the Front Panel to open a Map List window (Figure 4-1).
Figure 4-1
Map list window
The list includes both user-defined, and automatically generated maps. Refer to Online Help for an explanation of the difference between user-defined and automatically created maps.
EMOTOROLA LTD. 2000
43
ISSUE 18 REVISION 0
2.
Double click on a map name to open a map (Figure 4-2).
Figure 4-2 Map view window
Closing a map
Select File Close to close the map.
44
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Map display
Map display
Introduction
A map display consists of icons which represent GSM entities that are involved with the radio section of the GSM network. The links between these entities are also shown on the map display.
Map modes
There are two map modes, which display different information about the impact of faults: Subscriber mode. Device mode.
Map modes are selected from the View menu. See Figure 4-3.
Figure 4-3 The Map display View menu

EMOTOROLA LTD. 2000
45
Map display
ISSUE 18 REVISION 0
Subscriber mode
A map in this mode (see Figure 4-4) displays alarm severities according to the impact of faults on subscribers, for example, service, capacity, or redundancy loss.
Figure 4-4 Map in Subscriber mode An asterisk pattern on a node represents reconfigurations that are in progress, but the result of the reconfiguration is still pending. A question mark on a node indicates that the OMC has lost contact with it and does not know the correct severity. In this situation the colour represents the last known severity. New alarms cause icons to animate if the alarm impacts the node. Opening an alarm window from a map in this mode results in alarms impacting the node being displayed. As a result, alarms from a different node that impact the selected one are included in the display.
46
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Map display
Functional Unit severities on the subscriber map

Functional Unit (FU) severities are a snapshot of impacted sites or cells at the time of an alarm, they update the subscriber map. See also Consolidated alarm reporting in Chapter 3. FU severities on the subscriber map are independent of the alarm window. For example, an operator can clear an alarm manually and the alarm information is removed from the alarm window. However, if the problem has not been fixed the subscriber map still displays the subscriber impacts.
Device mode
A map in this mode displays severities according to the impact of faults on devices, for example, a critical redundant device will produce a critical severity. A question mark indicates that the OMC has lost contact with a site and does not know the correct severity. In this situation the colour represents the last known severity. New alarms cause icons to animate if the alarming device is on the node. As a result, all alarms on the node, including alarms that do not impact it, are displayed. If an alarm is cleared the device map is updated accordingly.
Figure 4-5 Map in Device mode

EMOTOROLA LTD. 2000
47
Map display
ISSUE 18 REVISION 0
Device map icon colours

The colour of a map icon will change depending on the level of alarm severity. The map icon colour will automatically reset to green when the operator clears the alarm or an alarm clear message is received from the NE. Map links can also have colours associated with them. Alarms associated with devices at each end of the link determine the link colour. If the devices have different alarm severities, the highest severity device alarm associated with the link determines the link colour.
Colour legend
The colour legend bar is used to explain the fault condition of each node. It represents different information depending on whether the map is in subscriber or device mode. Refer to Table 4-1. Select View Colour Legend to display the colour legend bar on the map. Table 4-1 Colour legend severity levels Severity level Critical* Major* Minor* Warning Investigate Normal Subscriber mode signifies a loss of service signifies a loss of capacity signifies a loss of redundancy signifies a potential problem signifies an ambiguous affect that should be investigated signifies that there are no alarms on a node NOTE *A loss of service, capacity, or redundancy always displays as, respectively, a critical, major, or minor severity in Subscriber mode. However, there are certain categories of alarms which the system determines as critical/major/minor even though there is no loss of service/capacity/redundancy to the subscriber. For example, a fire alarm will display as a critical alarm in Subscriber mode. Device mode signifies that a device is in a critical state signifies a device that has a major alarm signifies a device that has a minor alarm signifies a potential problem signifies an ambiguous affect that should be investigated signifies that there are no alarms on a node
48
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Map display
Alarm severity colours

Table 4-2 Colour Red Yellow Blue Pink Light Blue Green Alarm Severity Critical Major Minor Warning Investigate Normal (no alarms)
Alarm severity colours on map icons, on both subscriber and device maps, are usually as shown in Table 4-2.
Device states
A map icon can represent one of three states: S INS The normal state of a device is INS (busy/unlocked, or enabled/unlocked for a redundant device). S OOS An operator or the NE fault management software can take a device out of service (OOS) by issuing a lock command, or a shutdown command in the case of a DRI/RCU. NOTE A lock is intrusive,that is all activity on the device is terminated when the command is executed. A shutdown command permits traffic to be handed-off before the device is locked, by performing an intra-cell handover for the cells associated with the Transceiver unit being shutdown. S UNKNOWN The link to the node has been lost so the OMC is uncertain of its current severity.
EMOTOROLA LTD. 2000
49
Map display
ISSUE 18 REVISION 0
Icon name
INS
UNKNOWN
OOS
OMC MSC SGSN RXCDR RXCDR-Site
?
BSS BSC site BSCBTSsite BTS site GPRS PCU
? ? ? ? ?
Link
How State is determined OpState: AdminState: Enabled & Unlocked
INS
or Busy & Unlocked
UNKNOWN
or Any & Unknown Unknown & Any
OOS
All other combinations
Options: OpState: Enabled | Disabled | Busy | Unknown AdminState: Locked | Unlocked | Shutting Down | Not Equipped | Unknown
Figure 4-6 Map icons
Pending state
An asterisk, , on a node icon represents nodes in a pending state.
410
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Moving and expanding nodes

Prerequisite
A Network map must be open and displayed on the user terminal before attempting to move the nodes on a map. See in preceding chapter, Opening and closing a map.
Expanding a node cluster

If nodes have been added to a map without entering the X Y co-ordinates on the individual detailed views, they will be displayed in a cluster. To expand a node cluster out use the following procedure: 1. 2. Double click on the cluster to view the clustered nodes in more detail. Select View Full Zoom Out to contract any expanded nodes.
Moving a node on the map

To alter the position of a node on a map, perform the following procedure. 1. 2. 3. 4. 5. Select the required node. Hold down the SHIFT key, point to the node, and then hold down the centre mouse button and drag the node to its new location, keeping the mouse button held down. Release the mouse button. Release the SHIFT key. Select File Save to save the new location.
Expanding an NE map node

If the required node is contained within a cluster, the cluster must be expanded to view that node. See the procedure Expanding a node cluster. To expand a map node, use the following procedure: 1. 2. Click on the node to be expanded. Select View Expand to expand the node. NOTE Expanding a map node may create a cluster, which will then need to be opened as described earlier in this section. Expanding a map node is only valid for BSSs and RXCDRs.
EMOTOROLA LTD. 2000
411
ISSUE 18 REVISION 0
Node detailed view

If the required node is contained within a cluster, the cluster must be expanded to view that node. See earlier procedure Expanding a node cluster. To open a node detailed view, use the following procedure: 1. 2. 3. Click on the node to be expanded. Select Edit Detailed View to open the Detailed View. The Detailed View form will display (NO TAG).
Figure 4-7 Detailed View form

412
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Contracting a map node

To contract a map node perform the following procedure: NOTE A node must be initially in expanded form before it can be contracted. 1. 2. Select a node (at least one node must be selected). Select View Contract. All expanded nodes return to their original form.
Contained devices report

If the required node is contained within a cluster, the cluster must be expanded to view that node. See the procedure Expanding an NE map node. To open a node detailed view use the following procedure: 1. 2. Click on the node to be expanded and select Display Contained Devices from the menu bar. The Contained Devices report is displayed (Figure 4-8).
Refer to Online Help for a description of the columns in the Contained Devices report.
Figure 4-8 Contained Devices report
EMOTOROLA LTD. 2000
413
Organizing map nodes
ISSUE 18 REVISION 0
Organizing map nodes

Using the Organize Nodes function
The Organize Nodes function evenly distributes the nodes on a map over the map view, so that they are clearly visible. This avoids map nodes becoming clustered on the display. The Organize Map Nodes function does not take account of geographic backgrounds, existing coordinates, existing locations, or the relationships between them. To organize map nodes, use one of the following methods. NOTE Ensure that the map to be reorganized is not open.
From the Map List

In the Map List: 1. 2. Select the map name to organize. Select Edit Organize Nodes from the menu bar.
From an Xterm window

In an Xterm window at the command line prompt, type: /usr/gsm/current/sbin/OrganiseMapNodes <map_name> where, <map_name> is the name of the map to be organized.
414
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Viewing map levels
Viewing map levels

Prerequisite
A Network map must be open and displayed on the user terminal before attempting to expand a node to view contained elements. See the procedure, Opening and closing a map. If the required node is contained within a cluster, the cluster must be expanded to view that node. See procedure Moving and expanding nodes.
Procedure
NOTE The OMC Redraw Environment variable must be set for the View Map levels procedure to work correctly. For further information please refer to Operating Information: OMC System Administration (GSM-100-202). To view next and previous map levels: 1. 2. 3. Click on a node. Select View Next from the menu bar to view the next map level of the node. Select View Previous from the menu bar to view the previous map level of the node. .
EMOTOROLA LTD. 2000
415
Zooming a map
ISSUE 18 REVISION 0
Zooming a map
Prerequisite
A Network map must be open and displayed on the user terminal before attempting to zoom the map. See earlier procedure, Opening and closing a map.
Zooming in
To zoom in on a map: 1. 2. 3. Hold down the CTRL key while pressing the middle mouse button. Drag a rectangle over the area of the map to be zoomed. Release the mouse button and CTRL key. The selected area is displayed in zoomed format.
Zooming out
To zoom out on a map use select View Full Zoom Out. The map window returns to the original view.
416
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Printing a map
Printing a map
Introduction
A Network map must be open and displayed on the user terminal before attempting to print the map. See earlier procedure, Opening and closing a map.
Printing a map
To print a map select File Print from the menu bar. The diagram is printed to the default printer. The print process is documented in the status bar at the bottom of the window. NOTE Printing may take a few minutes.
EMOTOROLA LTD. 2000
417
Logging in remotely from a map
ISSUE 18 REVISION 0
Logging in remotely from a map

Prerequisite
A Network map must be open and displayed on the user terminal before attempting to login to a node on that map. See procedure, Opening and closing a map. If the required node is contained within a cluster, the cluster must be expanded to view that node. See procedure Moving and expanding map nodes.
Remote login to a NE
To remote login to a Network element from a map: 1. 2. Click on a node representing the required Network element. The text changes colour. Select Options Remote Login, which is greyed out for omcread users. A remote Xterm window logged in to the selected Network element is displayed.
No connection
In the case where a connection cannot be made with the selected network element, a window opens containing an appropriate error message. Press CR to close the window and return to the map window.
418
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Resync from a map
Resync from a map

Prerequisite
A Network map must be open and displayed on the user terminal before attempting to resync a node on that map. See procedure, Opening and closing a map. If the required node is contained within a cluster, the cluster must be expanded to view that node. See procedure Moving and expanding map nodes.
Resync a node
To resync a selected node from a map: 1. 2. Click on the node representing the Network element to be resynchronized. The text changes colour. Select Options Resync Selected Node from the menu bar to resync the Network element. The following message is displayed in the status bar at the end of the screen:
Resync Initiated - Look at Resync logs for status
Resync logs
To view Resync logs from a map, select Options Resync Logs from the menu bar to resync the logs. The Resync Logs window, Figure 4-9, opens.
Figure 4-9 Resync Logs window
Resync network
To resync the Network from a map select Options Resync Network from the menu bar. The following message is displayed in the status bar at the end of the screen:
Resync Initiated - Look at Resync logs for status
No connection
In the case where a connection cannot be made with the selected Network element, a failure is indicated in the resync logs window.
Further information
Information on Resync and accessing Resync Logs is contained in Administration procedures, Chapter 6.
EMOTOROLA LTD. 2000
419
Viewing alarms from a map
ISSUE 18 REVISION 0

Prerequisite
A Network map must be open and displayed on the user terminal before attempting to view alarms at a node on that map. See procedure Opening and closing a map. If the required node is contained within a cluster, the cluster must be expanded to view that node. See procedure Moving and expanding map nodes.
Procedure
To view alarms from a map: 1. 2. Click on a node representing the required Network element. The text changes colour. Select Display Alarms from the menu bar, or double-click on the node. The Alarms window for the selected node is displayed, and is dynamically updated as alarms occur. 3. Close the window by selecting File Close.
Viewing alarms from popup menu

To view alarms from a map popup menu: 1. 2. Click on a node representing the required Network element. The text changes colour. Click the right mouse button and select Alarms from the popup menu. The Alarm window Figure 4-10 opens. The Alarm window contains all the alarms for the selected Network Element and is dynamically updated as alarms occur. Close the window by selecting File Close.
3.
Figure 4-10 Alarm window

420
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Further information
Information on alarm handling is contained in Maintenance Information: Alarm Handling at the OMC (GSM-100-501).
EMOTOROLA LTD. 2000
421
Viewing OOS devices
ISSUE 18 REVISION 0
Viewing OOS devices

Prerequisite
A Network map must be open and displayed on the user terminal before attempting to view out of service (OOS) devices for that map. See earlier procedure, Opening and closing a map. To view any OOS devices, ensure resync is enabled. The procedure to enable resync is detailed in Operating Information: OMC System Administration, (GSM-100-202).
Viewing network OOS devices

To view the network OOS devices: Select Display All OOS Devices from the Map menu bar. The OOS Devices window for the network is displayed (Figure 4-11).
Figure 4-11 OOS devices window for a network
Viewing node OOS devices

NOTE If the required node is contained within a cluster, the cluster must be expanded to view that node. See procedure Moving and expanding map nodes . To view OOS devices at a Node: 1. Click on a node representing the required Network element. The text changes colour.
422
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Viewing OOS devices
2.
Select Display OOS Devices from the menu bar. The OOS Devices window for the selected node is displayed (Figure 4-12).
3.
Close the window by selecting File Close. Figure 4-12 OOS devices window for a node
Viewing OOS devices from popup menu

NOTE If the required node is contained within a cluster, the cluster must be expanded to view that node. See procedure Moving and expanding map nodes . To view OOS devices at a Node: 1. 2. Click on a node representing the required Network element. The text changes colour. Click the right mouse button and select OOS devices from the popup menu. The OOS Devices window for the selected node is displayed (Figure 4-12). 3. Close the window by selecting File Close.
EMOTOROLA LTD. 2000
423
Viewing a detailed view from a map
ISSUE 18 REVISION 0

Prerequisite
A Network map must be open and displayed on the user terminal before attempting to view a detailed view of a node on that map. See earlier procedure, Opening and closing a map. If the required node is contained within a cluster, the cluster must be expanded to view that node. See procedure Moving and expanding map nodes.
Viewing a detailed view

To view a detailed view window from a map: 1. 2. Click on a node representing the required Network element. The text changes colour. Select Edit Detailed View from the menu bar. (In the case of a Comms Link detailed view, select Options Detailed View). The Detailed View window for the selected node is displayed (Figure 4-13).
424
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Figure 4-13
Detailed View window
Further information
Configuration of Network elements and completion of the Detailed View forms are dealt with in Installation & Configuration: System Configuration, (GSM-100-403).
EMOTOROLA LTD. 2000
425
Deleting a map
ISSUE 18 REVISION 0
Deleting a map
Before deleting a map
It is important to note that deleting a map will delete the access to network elements contained within that map via the Maps icon on the front panel. This is the recommended mode of access for many functions. Deleting the map will not otherwise alter the configuration of a network.
Procedure
To delete a map: 1. Select the Maps icon on the Front Panel to display the Map List window (Figure 4-14).
Figure 4-14 2.
Map list window
Click on the name of the map to be deleted. The name is highlighted in inverse text.
3. 4.
Select Edit Delete from the menu bar. A delete confirmation box is displayed. Click OK button to confirm. The following message is displayed in the status bar at the bottom of the screen:
Element Deleted
NOTE Certain maps displayed within the Map List are Default Maps. Such Default Maps may not be deleted.
426
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Moving from a map to the navigation tree
Moving from a map to the navigation tree

Prerequisite
A Network map must be open and displayed on the user terminal before attempting to move to the Navigation tree from that map. See earlier procedure, Opening and closing a map. If the required node is contained within a cluster, the cluster must be expanded to view that node. See procedure Moving and expanding nodes on a map. NOTE If a map is not currently open, it may be easier to access the Navigation tree for the entire network by selecting the Config Mgmt icon from the Front Panel.
Procedure
To move to the Navigation Tree from a map: 1. 2. Click on a node representing the required Network element. The text changes colour. Select Display Navigation Tree from the menu bar. The Navigation tree window is displayed with the selected node as the root NE.
EMOTOROLA LTD. 2000
427
Using the navigation tree: overview
ISSUE 18 REVISION 0
Using the navigation tree: overview

Procedure list
The following is a list of procedures available from a Navigation Tree window: S S S S S S S Opening and closing a Navigation Tree. Moving levels on a Navigation Tree. Using the autoclose function. Checking device status. Viewing and printing cell configuration. Viewing neighbour data for a cell. Viewing available Comms links.
Further information
Further information on using the Navigation Tree can be found in On-line Help. Information on how the Navigation tree is set-up and configured can be found in Installation & Configuration: GSM System Configuration (GSM-100-403).
428
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Opening and closing a navigation tree
Opening and closing a navigation tree

Opening the navigation tree
To open a Navigation Tree: On the Front Panel display, select the Config Mgmt icon to display a Navigation Form window as shown in Figure 4-15.
Figure 4-15
Navigation Form window
Closing the navigation tree

To close a Navigation Tree: Select File Close from the menu bar.
EMOTOROLA LTD. 2000
429
Moving levels on a navigation tree
ISSUE 18 REVISION 0

Prerequisite
A Navigation Tree must be open and displayed on the user terminal before attempting to move levels on that tree. See procedure Opening and closing a navigation tree. NOTE In the event that the Config Mgmt MIB has no network object created, an empty Navigation Form is displayed and a special option exists to create a network. See Installation & Configuration: GSM System Configuration (GSM-100-403).
Procedure
To move levels on a Navigation Tree, assuming the tree is in the form shown in Figure 4-16: 1. To expand the Navigation Tree to the second level, click on the folder icon next to the Network object. The various class buttons are displayed, these represent classes of objects in the Configuration Management MIB. 2. 3. To open the branch of a tree under a button, click on the folder icon beside the button. To close the branch of a tree under a button, click again on the folder icon beside the button.
Panner and porthole

When the Navigation Tree diagram becomes larger in size than the display area of the Navigation Tree window (Figure 4-16) a panner/porthole arrangement is used to control what is being displayed. The tree is displayed in the porthole region, and what is displayed is controlled by means of a panner. To display different portions of the tree, use the following procedure to move the panner: 1. 2. Click and hold the left mouse button within the panner region, and move the mouse until the required area is in view within the porthole. Release the mouse button.
430
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Panner region
Figure 4-16 Navigation Form diagram, showing panner.
EMOTOROLA LTD. 2000
431
Using the autoclose function
ISSUE 18 REVISION 0
Using the autoclose function

Introduction
The Navigation Form supports an autoclose feature. When this feature is turned on, then expanding a certain branch of a tree results in the automatic closing of any other branches that might be open at that level. With the feature turned off, multiple branches of a tree at any given level might be open.
Prerequisite
A Navigation Tree must be open and displayed on the user terminal before setting autoclose. See procedure Opening and closing a navigation tree.
Procedure
To use the autoclose function: Select View Auto Close On/Off from the menu bar to toggle the function. The default is Off. NOTE The Autoclose function is a menu option, when selected the alternate state will be shown in the menu window, that is, with Autoclose On selected, Autoclose Off will display in the View menu.
432
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Fault management from navigation tree

Introduction
The facilities exist to perform fault management operations on certain devices from the Navigation Tree. NOTE Fault management can also be carried out from the Map, contained devices window,detailed views, MMI alarm windows, and via remote login to a BSS.
Lock a device
To lock a specific device from the Navigation Tree, proceed as follows: 1. 2. Select the specified instance from the Navigation Form. Select Fault Mgt Lock from the menu bar. A confirmation box opens with the following message:
Do you wish to lock device <device name> at site <site name>?
3.
Click OK. The following message is displayed in the status bar:

Locking Device....
NOTE In certain instances, for example, if the operator attempts to lock the last in service RSL between a BSC and a BTS, warning text is also displayed, similar to this example: Warning: Last Busy/Unlocked or Enabled/Unlocked RSL (RSL:0) will go out of service. A lock command is sent to the BSS. On receipt of a lock message from the OMC, the BSS attempts to lock the specified device and informs the operator of the success or failure of the operation within the status bar at the foot of the Map window. In the case of a successful operation, the Detailed View form is updated to show the new Administrative state. When the operational state of the device has been changed, the BSS informs the OMC of the success of the lock operation via the existing state change mechanism. NOTE Locking a BSS device immediately removes that device from service.
EMOTOROLA LTD. 2000
433
ISSUE 18 REVISION 0
Unlock a device
To unlock a specified device from the Navigation Tree, proceed as follows: 1. 2. Select the specified instance from the Navigation Tree form. Select Fault Mgt Unlock from the menu bar. An OMC dialogue box is displayed with the following message:
Do you wish to unlock device <device name> at site <site name>?
3.
Click OK. The following message is displayed in the status bar:

Unlocking Device...
An unlock command is sent to the BSS. On receipt of an unlock message from the OMC, the BSS attempts to unlock the specified device and inform the OMC of the success or failure of the operation. In the case of a successful operation, the Detailed View form is updated to show the new Administrative state. When the operational state of the device has been changed, the BSS informs the OMC of the success of the unlock device operation via the existing state change mechanism.
Shutdown a device
To shutdown a specified device (allow no new traffic to be accepted by the device) at a BSS from the Navigation Tree, proceed as follows: 1. 2. 3. Select a device instance (DRI or MTL) from the Navigation Form. Select Fault Mgt Shutdown from the menu bar. A confirmation box (Figure 4-17) is displayed with the following message:
Do you wish to Shutdown device <device name> at site <site name>?
The timer value associated with the shutdown operation can also be entered in the confirmation box. NOTE The timer value cannot be entered if the specified device is an MTL. Shutdown of MTL performs an inhibit and not a shutdown.
Figure 4-17 Shutdown timer confirmation window

434
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
4.
If the device is successfully shutdown, a message similar to the following is displayed in the status bar:
Shutting down device...
The result of the operation can be viewed in the Detailed View form.
INS a device
To INS a specified device from the Navigation Tree, proceed as follows: 1. 2. 3. Select the specified instance from the Navigation Form. Select Fault Mgt INS from the menu bar. A confirmation box is displayed with the following message:
Do you wish to INS device <device name> at site <site name>?
NOTE In certain instances, for example, if the operator attempts to INS a busy/unlocked DRI associated with a Cell, warning text is also displayed, similar to the following:
Do you wish to Reset device <device name> at site <site name>? Warning: Capacity at Cell <Cell name> may be temporarily reduced.
4.
Click OK.
Reset a device
To reset a specified device from the Navigation Tree, proceed as follows: 1. 2. 3. 4. Select the specified instance from the Navigation Form. Select Fault Mgt Reset from the menu bar. A confirmation box is displayed with the following message:
Do you wish to reset <device name>?
Click OK.
Reset a Site
An OMC operator can select an MCell Site object and perform a hard or a soft reset on the Site. (If the operator selects a Site that is not an MCell, then only a hard reset can be performed.) A soft reset means that only the currently running processes are re-started. A hard reset means that the entire Site is reset. To reset a Site from the navigation tree, carry out the following procedure: 1. 2. Select the specified Site from the navigation tree form. Select Fault Mgt Reset SITE Hard from the menu bar, refer to Figure 4-18. If the Site is MCell then Fault Mgt Reset Site Soft can also be selected. NOTE The Reset option on the Fault Management menu is greyed out for Site devices.
EMOTOROLA LTD. 2000
435
ISSUE 18 REVISION 0
3. 4.
A confirmation box is displayed with the following message:

Do you wish to Reset site <site name>?
Click OK.
The result of the operation can be viewed in Detailed View form.
Figure 4-18 Navigation tree with fault management menu
Reassign a device
The reassign action is used to reassign control of one device to another, it is valid for DRIs, SITEs, CBLs and MTLs. To reassign a specific device from the navigation tree, carry out the following procedure: 1. 2. Select the specified instance from the navigation tree form. Select Fault Mgt Reassign from the menu bar. The Reassign window opens. Refer to Figure 4-19. NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000
436
ISSUE 18 REVISION 0
3. 4.
Select a device in the window and click the Reassign button. A confirmation dialogue box is displayed with the following message:
Do you wish to reassign <device1> from <device2> to <device3> at <SITE>?
5.
Click OK.
Figure 4-19 Reassign window
Swap a device
Some devices operate in an active/standby mode, where the standby device acts as a backup to the active device. When the active device goes OOS the NE may automatically bring the standby device into service. Or an operator can force the standby device to be the active device, and vice versa, by invoking the swap operation. The swap action is valid only for GCLK, COMBproc, LAN and TDM devices. To swap a specific device from the navigation tree, carry out the following procedure: 1. 2. 3. Select the specified instance from the navigation tree form. Select Fault Mgt Swap from the menu bar. A confirmation dialogue box is displayed with the following message:
Do you wish to Swap <device name> devices at <SITE>?
4.
Click OK. NOTE The devices have to exist and also be in the correct state for the swap to succeed. If the devices are not in the correct state the following message is displayed in the status bar of the Navigation Form: Devices in incorrect state.
EMOTOROLA LTD. 2000
437
ISSUE 18 REVISION 0
Devices supported
The following table lists those devices which can be managed from the navigation tree and the functions which can be performed on them. All the logical groupings are contained in the SITE object. Table 4-3 Devices managed from navigation tree Logical Grouping NA NA Hard ware Devices Device Lock Unlock n n n Shutdown INS Reset Swap Reassign n
SITE PCU (GPRS) Cabinet CAGE DHP EAS IAS COMB COMBp n roc KSW air pair KSW GCLK LAN TDM MSI MMS n n n n n n n
n n
n n
n n
n n
n n
n n
n n
n n n n n
n n n n n n n
n n n n n n n
n n n n n n n n M-Cell
Pro cessors
CSFP BTP
GPROC n DPROC n (GPRS) BSP PSP (GPRS) n
438
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Logical Grouping
Device
Lock
Unlock
Shutdown
INS
Reset
Swap
Reassign
Software BTF Function LCF OMF Logical Links CBL MTL OML XBL RSL PATH GBL (GPRS) GDS (GPRS) GSL (GPRS) Radio Freq CELL Freq HopSys SMSCB msg Neigh bour Test Neigh bour RTF Group RTF DRI Group DRI NA Assoc_ BSC Conn_ Link n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n
EMOTOROLA LTD. 2000
439
Checking device status from the navigation tree
ISSUE 18 REVISION 0
Checking device status from the navigation tree

Prerequisite
A Navigation Tree must be open and displayed on the user terminal before checking device status using this method. See procedure Opening and closing a navigation tree.
Procedure
To check device status from the Navigation Tree: 1. 2. Double click on a device instance to open the relevant Detailed View. Select View State from the menu bar. The Detailed View window scrolls to the area in which status information is contained. NOTE If an instance other than a BSS, RXCDR or SITE instance is selected then a message is displayed to select the appropriate instance.
Further information
See also the procedure contained in this chapter for Viewing a detailed view from a map.
440
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Displaying OOS devices from the navigation tree

Prerequisite
A Navigation Tree must be open and displayed on the user terminal before displaying Out Of Service(OOS) devices using this method. See earlier procedure, Opening and closing a navigation tree. Ensure that Resync has been enabled by the System Administrator before checking for OOS devices. The enabling procedure is contained in Operating Information: OMC System Administration (GSM-100-202).
Procedure
To display OOS devices from the Navigation Tree: 1. 2. Click on the required network instance. The icon changes colour. Select Display OOS Devices from the menu bar. An OOS Devices Display window for the selected network instance is displayed. This window displays the OOS devices for the selected network instance. NOTE If an instance other than a BSS, RXCDR or SITE instance is selected then a message is displayed to the user to select an appropriate instance.
EMOTOROLA LTD. 2000
441
ISSUE 18 REVISION 0
Viewing OOS devices via the popup

To display OOS devices from the Navigation Tree: 1. 2. Click on the required network instance. The icon changes colour. Click the right mouse button and select OOS devices from the popup menu, as shown in Figure 4-20. An Out Of Service Devices Display window for the selected network instance is displayed. This window displays the OOS devices for the selected network instance.
Figure 4-20 Navigation Form window
Further information
See also the procedure contained in this chapter for Viewing OOS devices.
442
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Printing a navigation tree diagram

Prerequisite
A Navigation Tree must be open and displayed on the user terminal before printing the diagram. See procedure, Opening and closing a navigation tree.
Procedure
To print a Navigation Tree diagram: 1. Open the Navigation Tree to the required level. NOTE See the procedure on Moving levels on a navigation tree in this chapter for information to help with this. 2. Once the required Network elements are displayed on the Navigation Tree, select File Print from the menu bar. The diagram is printed to the default printer. The print process is documented in the status bar at the end of the window.
EMOTOROLA LTD. 2000
443
ISSUE 18 REVISION 0
444
EMOTOROLA LTD. 2000
Chapter 5
Fault Management
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
ii
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Chapter 5 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fault management: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definition of fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Principles of FM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FM and the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other FM indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault management at the NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FM process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Local maintenance terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Two states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administrative states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operational states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm category overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm severity overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Save alarm context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Buffering alarms and state change events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault indication at the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intermittent alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMIC alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OIC alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CERM feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definition of resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . When to perform a resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The resyncState process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The resyncAlarm process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Periodic Supervision of Accessibility (PSA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definition of PSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PSA failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disk usage exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Processor partition full . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handling: defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault handling process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing device states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parent device relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . On-site personnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2000
i
51 51 51 51 52 52 53 53 53 54 54 54 54 54 55 55 56 56 57 57 58 58 59 59 59 510 510 510 510 510 510 510 511 511 511 511 511 512 512 512 513 513 513 514 514 514 514 515 516 516 516
iii
ISSUE 18 REVISION 0
Fault handling and remote login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote login interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm clearing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clearing at the NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clearing at the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm throttling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to alarm throttling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intermittent alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing alarm throttles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault escalation procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
517 517 517 518 518 518 518 519 519 519 519 520 520
iv
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Fault management: overview

Definition of fault management
Fault Management (FM) provides the means to isolate and minimize the effects of faults in the network, thereby enabling the network to operate efficiently.
Principles of FM
The principles of FM are as follows: S S S S To pin-point the cause of a fault, by running tests on the NE devices to determine their ability to function correctly. Isolate the faulty element, by re-routing traffic and taking the faulty element out of service. Take corrective action to rectify the faulty device. Ensure that disruption to service (caused by the fault and any associated corrective action) is kept to a minimum.
Both the NEs and the OMC contain FM features which ensure that any faults occurring keep service disruption to a minimum.
FM and the OMC

The OMC provides fault indication facilities using event management to inform the operator of faults in the GSM network. Figure 5-1 shows an illustration of fault management at the OMC.
EMOTOROLA LTD. 2000
51
ISSUE 18 REVISION 0
Other FM indications
Performance statistics also provide useful information for analyzing fault conditions. The current health of the network (from the latest performance statistics reports) can be ascertained from the key statistics.
FM FEATURES:
D PERIODIC SUPERVISION OF ACCESSIBILITY OF OML (OMC-BSS) LINKS. ALARM BUFFER TO SAVE UP TO 100 ALARMS IF OML LINK IS LOST. PERIODIC RESYNCH WITH ALARM LISTS AT THE BSSS. ACTIVE
FAULT INDICATION:
D D D D D D MMI FRONT PANEL NETWORK MAP ICONS EVENT/ALARM DISPLAY WINDOWS PM REPORTS OOS DEVICE REPORT CONTAINED DEVICES REPORT
FAULT HANDLING:
D D D D D FROM MAP FROM NAVIGATION TREE FROM CONTAINED DEVICES REPORT ALARM HANDLING POPUP MENU REMOTE LOGIN TO NE
D D D
AUTOMATIC SWITCHOVER BY NE TO REDUNDANT DEVICE WHEN CRITICAL ALARM RECEIVED. LOCK/UNLOCK OF DEVICES AVAILABLE FROM MAP, NAVIGATION TREE, ALARM WINDOW AND CONTAINED DEVICES FORM
Paging Center System PROCESSOR

RLOGIN SESSION
pager
Modem
BSS MMI COMMANDS/RESPONSES VIA REMOTE LOGIN
X.25
EVENT & ALARM MESSAGES
ACTIVE EVENTS TABLE
MMI
ACTIVE SUBSCRIPTIONS
MMI PROCESSOR
EM ROUTER
BSS/RXCDR (CONTAINS INHERENT FM FEATURES)
EVENT LOGFILES
Figure 5-1 Fault management using the OMC
Refer to Maintenance Information: Alarm Handling at the OMC, GSM-100501, for complete fault handling procedures at the OMC. Refer to Maintenance Information: BSS/RXCDR, (GSM-100-523), for complete fault handling procedures at the BSS.
52
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Fault management at the NE
Fault management at the NE

FM process
Faults at an NE (BSC, BTS or RXCDR), or on the links between them, are detected by FM software on the NEs Generic Processor (GPROC) boards. The resultant event/alarms are placed in the NEs active alarms table (AET), and sent to the OMC, where they are displayed on the operator SPARCstation according to the subscription criteria. On receipt of a critical alarm, the FM software at the NE automatically takes the device out of service, and switches in a redundant device (if available). A visual presentation of BSS fault management is shown at Figure 5-2.
DEVICE STATUS:
D IN SERVICE (INS): BUSY/UNLOCKED ENABLED/UNLOCKED. OUT OF SERVICE (OOS): ANY OTHER STATE.
MS
(RCU BUSY/UNLOCKED)
ALARM & STATE CHANGE EVENTS BUFFER ACTIVE ALARMS LIST BSS/RXCDR X.25 TO OMC (VIA 2MB LINK)
Figure 5-2 BSS fault management
Local maintenance terminal

Alarms can be viewed using a personal computer, also known as a Local Maintenance Terminal (LMT), attached to the maintenance port of a BSC, BTS or RXCDR. Red light emitting diodes (LEDs) on individual boards and cabinets provide a visual warning of fault conditions. Alarms from the whole BSS can be viewed at the BSC. At a BTS or RXCDR, only alarms from that site can be viewed. LEDs at the network elements (NE) also provide information on fault conditions at the board level.
EMOTOROLA LTD. 2000
53
Device status
ISSUE 18 REVISION 0
Device status
Introduction to status
The status of any device at the BSS determines whether it is In Service (INS), where it is supporting (or able to support) user traffic, or Out Of Service (OOS), where it is unable to support user traffic. The normal state of a device is busy/unlocked (or enabled/unlocked for a redundant device).
Two states
The two device states are: S S Administrative. Operational.
The device status is determined by these two states.
Device states
Table 5-1 Determining different device states State OP State: ADMIN State: In Service (INS) Enabled Busy Any Unknown Out of Service (OOS)
Unknown All other combinations
Unlocked Unlocked Unknown Any
Administrative states
Administrative states are set by the operator using the GUI, the remote login facility at the OMC or locally at the site using a PC. An operator can remove a device from service or make a device available for service by changing its administrative state. S Unlocked The unlocked state is the normal operating state of the device. S Locked The locked state indicates the device is unavailable for normal operation. S Equipped This state indicates a device in the equipped state has been made known to the system. This is done via an entry being made in the NEs configuration database. S Not equipped This state indicates the device entry in the NEs configuration database has been removed.
54
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Device status
Operational states
Operational states are controlled by the NE fault management application. The three operational states are: S S S Enabled In the enabled state, the device is not supporting user traffic. Disabled In the disabled state, the device cannot support user traffic. Busy In the busy state, the device is supporting user traffic.
Further information
Operating Information: System Operation (GSM-100-201) describes how to change device status during fault handling.
EMOTOROLA LTD. 2000
55
Alarm categories
ISSUE 18 REVISION 0
Alarm categories
Alarm category overview
There are five possible failure categories for alarms. The alarm type field indicates the general category of system operation affected by the detected alarm condition. The different alarm types which can be generated by the NEs or the OMC are: S Communication Failure. This is an alarm relating to a fault in the transfer of data from one point to another (for example loss of signal or call establishment error). S Quality Of Service Failure. This is an alarm associated with a degradation in the quality of service (for example excessive response time or reduced bandwidth). S Processing Failure. A processing alarm failure is a software or processing fault (for example corrupt data or out of memory). S Equipment Failure. This is an alarm associated with an equipment fault, transmitter failure or power problem. S Environmental Failure. An environmental failure is an alarm associated with the room where the equipment is housed (for example smoke detection, fire etc).
56
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Alarm severities
Alarm severities
Alarm severity overview
There are six alarm severities. If the severity of an alarm changes at the NE, the alarm severity field of the message previously sent is dynamically updated (for example, the severity of an FMIC alarm changes from Critical to Clear upon receipt of a new alarm from the network. This occurs when the faulty device rectifies itself). The different types of alarm severities reported in the alarm severity field are as follows: S Critical. Indicates a service-affecting fault has occurred. Immediate corrective action is required (for example, a resource is completely out-of-service and its capability must be restored). S Major. Indicates a service-affecting fault has occurred. Urgent corrective action is required (for example, severe degradation in the capability of a resource, requiring its full capability to be restored). S Minor. Indicates the existence of a non-service-affecting fault. Corrective action should be taken to avoid a more serious fault (for example, while the detected alarm condition is not currently degrading, the service capability of the resource may eventually be affected). S Warning. Indicates the detection of a potential or impending service-affecting fault (before any significant effects have been noticed). Action should be taken to diagnose and correct the problem to prevent it from becoming a more serious service-affecting fault. S Clear. Indicates the clearing of a reported alarm. This alarm clears all alarms for a managed object having the same device type, device identifier, and alarm code (for example, an alarm is cleared from an NE, which in turn causes the severity level at the OMC to be set to CLEAR). S Investigate. Indicates the degradation of system performance in one or more sites or cells. Analysis should be carried out to determine the cause of the degradation.
EMOTOROLA LTD. 2000
57
Save alarm context
ISSUE 18 REVISION 0
Save alarm context

Buffering alarms and state change events
If the BSS detects that communication with the OMC has been lost it routes all BSS critical and major alarms, and all state change events to a buffer. When the BSS detects that communication with the OMC has been re-established, it starts sending the events/alarms in the buffer to the OMC in chronological order. When the buffer is empty normal event processing resumes at the BSS. This feature is known as save alarm context. NOTE When the buffer is full the oldest buffered information is overwritten. The event buffer can store up to a maximum of 100 events/alarms. If the BSS event buffer overflows, it generates an event to notify the OMC that event information has been lost. This event is sent as soon as communication with the OMC is re-established. The purpose of this event is to inform the operator that event/alarm information has been lost and it is necessary to perform manual actions to determine the status of the BSS. The overflow event buffer contains counts of the number and severity of events that were lost due to the overflow. When the OMC is reconnected to an NE an automatic resync of alarms/events occurs if the: S S OMC had been operational and the OML link had been lost and restored, that is, automatic resync of the BSS on OML restoration. OMC has been stopped and restarted and is set up to do a resync on startup.
58
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Fault indication at the OMC
Fault indication at the OMC

Notification
The alarms summary on the front panel of the GUI is updated to reflect any new alarms received by the OMC, and the icon representing the faulty node on the map changes to reflect the alarm of highest severity. The incoming messages in the open alarm and event display windows provide the operators with information on the exact source of the fault, its severity and time of occurrence. Figure 5-3 illustrates alarm notification at the OMC.
ALARM SUMMARY ALARMS ICON
GSR 4.1 1.6.1.0
Figure 5-3 Alarm reporting at the OMC
Multiple alarms
A single fault, for example a link failure, may generate more than one alarm. Subscription lists can be set up to display alarms of particular severities from selected sites to simplify fault detection. For example, an operator could monitor all critical and major alarms from a group of cells in a particular geographical area.
EMOTOROLA LTD. 2000
59
Alarms
ISSUE 18 REVISION 0
Alarms
Introduction to alarms
Alarms and state change events provide indications of faults resulting in loss of service or degradation of service, or as warnings of potential service-affecting faults. Events/alarms are also generated by the OMC, for example in the case of OML failure. There are three types of alarms, and operator action is dependent on the type of alarm received. The three alarm types are: S S S Intermittent alarms. Fault Management Initiated Clear alarms (FMIC). Operator Initiated Clear alarms (OIC).
Intermittent alarms
If an Intermittent alarm is received, no alarm clear message should be expected. Intermittent alarms are indicated in the alarm message displayed at the OMC. If the alarm occurs too frequently the operator may want to throttle the alarm by using an MMI command.
FMIC alarms
If an FMIC alarm is received, the fault management software of the NE clears the alarm when the problem is solved. The operator expects either an alarm clear message to be displayed or the device is taken out of service. Receipt of an alarm clear message indicates the alarm condition no longer exists. If notified that a device is out of service, the operator must initiate the repair or replacement procedure for that device.
OIC alarms
Receipt of an OIC alarm indicates that operator action is required to correct the fault. If the fault is serious, the operator initiates the repair or replacement procedure for that device. When repaired or replaced the device must be returned to service.
CERM feature
The Circuit Error Rate Monitor (CERM) feature is used to identify when discontinuity is detected in a circuit. An alarm is generated and sent to the OMC when the error count exceeds an operator specified threshold. The alarm identifies the RCI (Radio Channel Identifier) or CIC (Circuit Identity Code), and the path where the error is detected. RCI and CIC alarms are treated as FMIC alarms at the OMC. The BSS does not keep track of these alarms, and therefore a new alarm must be sent to clear a previously faulty RCI or CIC.
Refer to Maintenance Information: Alarm Handling at the OMC (GSM-100-501) for complete procedures on clearing alarms.
510
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Resync
Resync
Definition of resync
Resync (alarm and state synchronization) enables the alarm and device state information at the OMC to be updated to reflect the actual device state and alarm information at the NEs.
When to perform a resync

Resyncs should be performed in the following situations: S The resync operation needs to be performed when a link to a site has been down. Resync is automatically performed when an OOS device comes back into service, and when an out-of-service OML to an NE comes back into service. S The OMC periodically requests a system-wide alarm and state re-synchronization of every site in the managed network. It is possible to use the Resync Scheduler to set up scheduled resyncs on either the network, or on individual NEs. S A re-synchronization can be performed on OMC startup (user-configured), and involves the processes resyncState and resyncAlarm.
The resyncState process

The NE sends up information on the state of all CM MIB supported devices from each of its sites. This information is used by the Network Status Summary (NSS) feature, or by any event display window with the appropriate subscriptions to indicate if NE sites and links are operational. Performing a resync one site at a time reduces the possibility of having a backlog of events at the OMC.
The resyncAlarm process

If the result from the resyncState operation is positive, a resyncAlarm operation is invoked. The NE sends the active alarms on its active alarm list to the OMC. The alarms sent are compared with the alarms currently in the AET of the OMC. If there are any differences, the alarm messages in the AET are updated to include a resync indicator field. The different types of entries in this field are described in the following table: Entry [R] [R?] Description Alarm first seen at OMC after being sent due to resync. Alarm, previously sent during a resync, but at the end of subsequent resync is no longer in the BSS active alarm list. Alarm in OMC active event table, but no longer in BSS active alarm list. These alarms can be handled as a group.
[?]
EMOTOROLA LTD. 2000
511
Periodic Supervision of Accessibility (PSA)
ISSUE 18 REVISION 0
Periodic Supervision of Accessibility (PSA)

Definition of PSA
Periodic Supervision of Accessibility (PSA) periodically sends messages to BSSs requesting information on their current state. This verifies if the BSSs are operational or not.
PSA failure
If a BSS fails to respond to a PSA request for its status, the OMC will generate an alarm for that BSS. This alarm indicates that the BSS failed to respond to a message requesting its status, and may be indicative of a problem at the BSS. The OMC continues to send messages periodically to the BSS requesting its status. On receipt of a response message from the BSS, the OMC changes the alarm severity of the message to Clear. An alarm is also generated when the BSS informs the OMC that it is not operational. The OMC continues to send messages periodically to the BSS requesting its status. On being informed that the BSS has returned to operating correctly, the OMC changes the alarm severity of the message to Clear.
512
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Disk usage exceeded
Disk usage exceeded

System Processor partition full
An alarm is raised when either of two (upper and lower) threshold values of disk usage are exceeded on the /,the /home , the /usr, and the /usr/gsm/ne_data partitions of the System Processor. The System removes any logfiles older than three days from the $OMC_TOP/logs directory using routine maintenance cron jobs, or if the upper disk usage threshold is exceeded. The threshold value should return to the default value of 90%. The file $OMC_TOP/config/global/FM_audit.CNFG contains the values that are used for setting the timers for each audit and disk usage limits. These values are set at installation time and can only be changed by the system administrator.
Further information
For information on setting the related parameters, see Maintenance Information: Alarm Handling at the OMC, (GSM-100-501).
EMOTOROLA LTD. 2000
513
Fault handling
ISSUE 18 REVISION 0
Fault handling
Handling: defined
Alarm messages arriving at the OMC contain information on the type of fault, its source and severity. When the alarm is first displayed an operator takes responsibility for fixing the problem causing the alarm, and is then said to be handling the alarm. Any operator may handle any alarm not being handled by another operator. Only the operator currently handling a particular alarm may clear it. (Command partitioning is used to specify which users can perform which operations at the OMC. For example, it is possible to have an operator who cannot handle, un-handle, clear or remove alarms).
Fault handling process

Each alarm display window contains an alarm handling popup menu, as shown in Figure 5-4, that the operator uses to change the state of the alarm as fault management procedures are performed. The changes in alarm state are routed back to the Active Events Table (AET), therefore all operators who have subscribed to that alarm are aware of its state. For example, when an alarm is first displayed, an operator can change the state field from NEW to HANDLED by pointing to the alarm message text, clicking the right mouse button and selecting HANDLE. This change is routed back to the AET via the OMC MMI, and all windows displaying this alarm message update the alarm state field. When the operator begins handling an alarm the operator field is changed to the name of the operator handling the alarm. Group handling of alarms of the same type, or which relate to the same fault is possible. Having selected one alarm (using the left mouse button) other alarms can be selected by clicking on them with the middle mouse button.
Figure 5-4 The alarm handling popup menu
Alarm priority
Refer to Technical Description: GSM Alarm Handling at the OMC (GSM-100-501) for a listing of the order of priority in which alarms should be handled.
514
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Fault handling
Changing device states

An operator can take a device Out Of Service (OOS) by issuing a command to lock or shutdown the device. This can be done from the Map, the Navigation Tree, or from the Fault Mgt menu on the Contained Devices report (Figure 6-5).
Figure 5-5 Contained Devices report Locking the device is intrusive, in that all activity on the device is terminated when the command is executed. Shutting down a device permits traffic to be handed off before the device is locked by performing an intra-cell handover for the cells associated with the RCU being shutdown. OMC operators are informed of all state changes at NEs by an event message. Some devices operate in an active/standby mode, where the standby device acts as a backup to the active device. When the active device goes OOS the NE may automatically bring the standby device into service. Or an operator can choose the standby device to be the active device, and vice versa, by invoking the swap operation. The swap action is valid only for GCLK, COMBProc, LAN and TDM devices. This can be done from the Navigation Tree or the Contained Devices form, and selecting the Fault Mgt menu. An operator can reassign the control of one device to another. The reassign action is only valid for DRIs, SITEs, CBLs, and MTLs. This can be done from the Navigation Tree or the Contained Devices form. This facility not available for all devices at an NE. See Operating Information: System Operation manual, GSM-100-201 for a list of these devices.
EMOTOROLA LTD. 2000
515
Fault handling
ISSUE 18 REVISION 0
Parent device relationships

If changing the device state does not clear the alarms, when managing faults on BSS devices, the problem could possibly be solved by changing the state of the parent device. Details of device and parent relationships are shown in Figure 5-6.
DEVICE
RSL
1ST PARENT
MTL OML XBL MMS
2ND PARENT
MSI
3RD PARENT
CAGE CAB SITE BSS
COMB RCU
1ST PARENT
DRI
2ND PARENT
Figure 5-6 BSS device/parent relationships
On-site personnel
Sometimes it is necessary to send personnel on-site to replace faulty devices. All work performed at operational NEs by site engineers or technicians should be co-ordinated, monitored, logged and controlled by the OMC operators.
Refer to Maintenance Information: Technical Description: GSM Alarm Handling at the OMC (GSM-100-501) for fault handling procedures at the OMC. Refer to Maintenance Information: BSS/RXCDR (GSM-100-523) for complete fault handling procedures at the BSS.
516
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Fault handling and remote login
Fault handling and remote login

Remote login interface
The operator can remote login to an NE from the OMC and perform various FM functions, such as interrogating the faulty device using BSS MMI commands to find the cause of the fault. Remote login can be accessed from the Map, Navigation Tree, Contained Devices window, alarm windows or from the GUI Front Panel.
X.25
X.2 5 PROCESSOR SYSTEM
OPERATOR TERMINAL
MMI PROCESSOR
BSS/RXCDR
Figure 5-7 OMC - BSS remote login interface
See Operating Information: System Operation, (GSM-100-201) for information on the various Rlogin access methods.
EMOTOROLA LTD. 2000
517
Alarm clearing
ISSUE 18 REVISION 0
Alarm clearing
Requirements
When a fault has been rectified its associated alarm message must be cleared from both the active alarm list at the NE, and the active events table at the OMC.
Clearing at the NE
Intermittent alarms are cleared from the BSC/BTS active alarm list once they have been sent to the OMC. OIC (Operator Initiated Clear) and FMIC (Fault Management Initiated Clear) alarms are deleted from a BSC/BTS active alarm list by the NEs FM software once the cause of the fault has been rectified (for example after a reset). The NE then re-sends an alarm message to the OMC with its alarm severity set to clear.
Clearing at the OMC

OIC and Intermittent alarms can be set to clear by the operator, when the fault has been rectified, in the state field of the alarm display window. This informs other operators subscribing to alarms from that device or node that the problem has been fixed. The message may then be removed (using the alarm handling popup menu) from the AET of the OMC. Resync alarms with a [?] entry (alarms in OMC active event table, but no longer in BSS active alarm list after a resync) are deemed to be inactive alarms, and can be handled and cleared as a group. FMIC alarms are re-sent to the OMC with their severity set to clear by the NEs FM software when the fault has been rectified. The alarm state field can be set to clear using the alarm handling popup menu (dependent on the operator level, see Command Partitioning), and the alarm message can be removed from the AET at the OMC using the Remove option.
518
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Alarm throttling
Alarm throttling
Introduction to alarm throttling
Alarm throttling allows the operator to specify a throttle time period (minimum number of minutes) between reports for a particular intermittent alarm. In GSR4 alarm throttles can be viewed, created, edited and deleted from the Navigation Form.
Throttle time period

The throttle time period is set on a per (intermittent) alarm code, per device type, per BSS basis. Throttling is done for each device and for each of its intermittent alarm codes For example, throttling for DRI 0 0 0 alarm code 1 is handled separately from the throttling for DRI 0 1 0 alarm code 1, but would still use the same throttle time period defined for DRI alarm code 1. If an intermittent alarm from a device is the first alarm from the device to occur in that throttling period, it is reported. The number of times that alarm, from that device is throttled in the previous time period is included in the alarm message displayed. Subsequent such alarms from the same device which occur in the same time period are throttled.
Intermittent alarms
Alarm throttling can only be applied to alarms that belong to the intermittent alarm category. These alarms may occur frequently, but their non-serious nature means that the operator may wish to restrict the reporting of them to a pre-defined rate, except for alarms with a severity of critical.
Viewing alarm throttles

Alarm throttles can be viewed for BSSs or RXCDRs by selecting Alarm Throttles from the Config Mgt menu in the Navigation Form. The operator can change the time period for an alarm throttle for a device.
EMOTOROLA LTD. 2000
519
Fault escalation procedure
ISSUE 18 REVISION 0
Fault escalation procedure

Purpose
A fault escalation procedure should be established whereby any service-affecting fault condition existing on the network for longer than a predetermined threshold should be reported to the next level of management. If the fault persists longer than a second predetermined threshold the next higher level of management should be informed. A typical level for the first threshold would be one hour, but this period is at the discretion of the user.
520
EMOTOROLA LTD. 2000
Chapter 6
Event Management 1
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
ii
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0

Event and alarm management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Mgmt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Events and alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Primary functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm display window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How event and alarm management works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of EM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The difference between events and alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Events: defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarms: defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting events and alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event/alarm subscription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The subscription process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscription criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Thresholding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blacklist subscriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Events in alarm subscription lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event/alarm display windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Two types of windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Differences between event and alarm windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event/alarm subscription procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscription procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscription functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Alarm display window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reading the display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Consolidated alarm reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to consolidated alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Consolidated alarm report format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The handling process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm handling options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm clearing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The event display window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The event logfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to event logfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logfile creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logfile procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logfile location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Naming convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logfile rollover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2000
i
61 61 61 61 62 63 63 63 63 64 65 65 65 65 66 66 66 66 66 66 67 68 68 68 68 69 69 69 610 610 610 610 611 611 611 611 612 612 612 612 612 613 613 613 613 614 614 614 614 614 615 615
iii
ISSUE 18 REVISION 0
Logging events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The search event log window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event/alarm utilities invoked from the command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of event logfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Utility listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How the event log utilities are used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post-processing of event logfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Online printing of alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
616 616 617 618 618 618 618 619 619
iv
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Event and alarm management

Event Mgmt
OMC Event Management provides a centralized facility for reporting network-wide generated events and alarms, and for monitoring the status of the Network. Event Management monitors events and alarms generated by the NEs. Events and alarms are presented to operators according to specific subscription and threshold criteria.
Events and alarms

Network elements (NE) report to the OMC through events. For example, an NE issues an event to the OMC to indicate that a statistics file is ready for collection. Alarms are a special type of event. Alarms are sent to indicate a fault condition, such as a communications failure. Groups of events and alarms can be routed to the same display window through subscription lists.
Primary functions
The main functions of Event Management are as follows: S S S S S Collect and log all events and alarms sent to the OMC. Display events, and specified alarms, in event windows invoked from the OMC console or the network map. Display alarms in alarm windows, invoked from the network map or the OMC console of the MMI, that allow operators to perform alarm handling. Enable users to customize alarm and event windows using subscriptions to display particular events or alarms. Provide post-processing facilities to aid in the analysis of event logs, using the OMC MMI and utilities invoked from the UNIX command line.
As an enhancement to the Event Management functionality, the Alarm Notification via paging feature is available. This is used to automatically notify on-call personnel of certain alarms or events that have been reported to the OMC.
EMOTOROLA LTD. 2000
61
ISSUE 18 REVISION 0
Alarm display window

Figure 6-1 shows how incoming alarms are displayed on an operator workstation.
Alarm summary
4.1 1.6.1.0
Alarms icon
Figure 6-1 Alarm display window invoked from the Alarms icon
62
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
How event and alarm management works

Overview of EM
Figure 6-2 shows how event and alarm management functions. All events and alarms that arrive at the OMC from the NEs are collected and standardized by the event manager. This converts events into a single standard format recognizable by other event management processes and applications. Standardized events are then sent to the event routing process. The OMC application software, such as the network status summary application software (CM MIB) and performance management, also receives alarms and events data.
Notification
Events and alarms are generated by all the devices in different NEs in the network, and are reported to the NE Fault Management (FM) software. The NE translates them into standardized messages, and forwards them to the OMC. The OMC also generates internal alarms which, for example, indicate that the X.25 link has failed. There is also the optional Alarm Notification via paging feature which automatically notifies on-call personnel of certain alarms or state changes that have been reported to the OMC.
Event routing
The event routing process automatically sends all events and alarms to the event log. The process routes events and alarms that are subscribed to in an active subscription list in the Active Events Table (AET), and directs them to the appropriate subscribers. It also processes input from the operator. The event routing process allows the event log files to be accessed by both the OMC MMI and command line utilities.
EMOTOROLA LTD. 2000
63
ISSUE 18 REVISION 0
Alarm handling
The operator can change the state of some of the fields while performing Alarm Handling. The event routing process sends this information to the AET. This indicates the current handling state of the alarm to subscribers.
OMC MMI FEATURES: COMMAND-LINE INTERFACE:
S S S
EVENT & ALARM WINDOWS SUBSCRIPTION MENUS EVENT LOG SEARCH & PRINT
S S
POST-PROCESSING OF EVENT LOGS REAL-TIME PRINTING OF EVENTS/ALARMS pager
MAINTAINS ALL ACTIVE EVENTS & ALARMS
STORES ALL SUBSCRIPTION LISTS

EM SUB-SCHEMA (OMC DATABASE)
Paging Center modem
ACTIVE EVENTS TABLE

STANDARDIZATION/ COLLECTION
EM ROUTER
MMI
MMI PROCESSOR
X.25
Event & Alarm Messages SYSTEM PROCESSOR
ACTIVE SUBSCRIPTION LISTS EVENT LOGFILES
CM MIB
BSS/RXCDR (CONTAINS INHERENT FM FEATURES)
UPDATES THE NETWORK STATUS SUMMARY FEATURE STORES ALL RECEIVED EVENTS & ALARMS
Figure 6-2 Event/alarm management
64
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
The difference between events and alarms
The difference between events and alarms

Events: defined
Events are used to transfer information from NEs to the OMC. An event could be information relating to the state of a particular operation or device in the NE (for example, device change of state), or information on the beginning of a file transfer from an NE to the OMC. The following points summarize the main functions of events: S S S S S S Indication of a device change of state at an NE. Test result information. Information on traffic conditions. Indication of file transfer. Indication of measurement result. Indication of faulty device condition at an NE (alarm).
Alarms: defined
Alarms are events of a special category, that report failures of different severities in the network to the OMC. Since alarms are a type of event they are logged in the event log, and can be displayed in the event display windows at the operator workstations. Only six event types fit into the alarm category, and only these are displayed in alarm display windows. The following points summarize the main functions of alarms: S S S S S S Generated by the OMC and the NEs. Indication of communication failure. Indication of quality of service failure. Indication of processing failure. Indication of equipment failure. Indication of environmental failure.
Troubleshooting events and alarms

For complete information on clearing events and alarms refer to Maintenance Information: Alarm Handling at the OMC (GSM-100-501) manual.
EMOTOROLA LTD. 2000
65
Event/alarm subscription
ISSUE 18 REVISION 0
The subscription process
Event/alarm subscriptions enable certain events to be routed to specific operators or software applications according to certain criteria. Events that operators or application software can subscribe to can be defined in subscription lists. A subscription list can contain several different event/alarm subscriptions. The operator can modify the list by changing the event/alarm subscriptions already defined for that list. New subscriptions can also be created, and existing subscriptions can be modified or deleted. Default subscriptions are set up for OMC management applications when the system is started. A management application is one part of the OMC software. For example, when the Performance Management (PM) application subscribes to fileNEavailable events it will have access to statistics files, or when the name of the subscriber is defined in the pager.config file paging functions are accessible. It is possible to create a system-wide Auto Initiate file which is common to all operators, or an Auto Initiate file for each operator, that will automatically open the required windows at the start of an MMI session.
Subscription criteria
Typical subscription criteria are: S S S S S Device class (for example, BTS). Event type (for example, communications failure). Severity type. Error ID. Time.
Thresholding
The event subscription process allows thresholding of events. Thresholding is used to specify how many times an event must occur before it is reported to the operator. Thresholding information is defined within the subscription criteria.
Blocking
It is possible to block alarms/events for a specific subscription list. All events/alarms specified in this subscription will be blocked when the subscription list becomes active (is opened in an event/alarm display window). This does not affect event/alarm subscriptions specified for other subscription lists.
Blacklist subscriptions
A subscription list called BLACKLIST can be created to prevent specified alarms/events being displayed in an alarm display window or event display window. This subscription list can be created using the same procedure to create other subscription lists. All alarms/events subscribed to in a BLACKLIST subscription are switched off in any active alarm display window, or event display window. It overrides the active subscription list for these windows. The procedure for creating a BLACKLIST subscription list is described in Operating Information: GSM System Operation (GSM-100-201).
66
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Events in alarm subscription lists

Normally, the subscription lists selected for alarm display windows only subscribe to alarms. However, in certain circumstances event messages are also subscribed to. For example, when a SITE is first installed, some operators may want to include state change events from SITE resets with alarms in the alarm display windows. This allows event messages in alarm display windows to be handled with operator IDs assigned to the messages. This allows greater traceability. Events can be made eligible for alarm subscription lists by changing an MMI configuration file known as a Management Information Tree (MIT) file. This is carried out by Motorola personnel.
EMOTOROLA LTD. 2000
67
Event/alarm display windows
ISSUE 18 REVISION 0
Event/alarm display windows

Two types of windows
The OMC MMI provides two types of display windows for monitoring subscribed events and alarms at the OMC. The events displayed in each window depend on the subscription list selected for that window. The two types of display windows are as follows: S S Event display windows. Alarm display windows.
Before opening an event or alarm display window, the operator assigns a subscription list to the window that defines which event/alarm messages will be displayed in that window. All incoming events and alarms subscribed to will be displayed in the window.
Differences between event and alarm windows

A summary of the differences between event and alarm windows is shown below. Event windows Usually subscribe to both event and alarm messages. Alarm windows Should only subscribe to alarm messages, but may, in certain cases, be configured to display specific events.
Event/alarm messages cannot be handled. Alarm messages can be handled. Event messages have many formats. Windows are emptied if they are closed. Alarm messages have a standard format. Closing and opening a window has no effect on active alarms displayed. Alarms that are cleared are removed. If the same alarm arrives more than once, it is not displayed again at the OMC. An alarm remains in the alarm window until it is removed by the operator, or until a clear alarm message is received from its device of origin.
If the same event message arrives more than once it is displayed again at the OMC. Can hold up to 512 event/alarm messages. When 512 has been reached, the first messages in the window are dropped to make room for incoming messages.
Refer to the OMC Online Help facility for more information on the alarm display window.
68
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Event/alarm subscription procedures
Event/alarm subscription procedures

Subscription procedures
Refer to Operating Information: GSM System Operation (GSM-100-201) for complete details on event/alarm subscription procedures.
Subscription functions
The event subscription management process can perform the following functions: S S S S Create, modify, delete, rename and display subscription lists. Store and retrieve subscriptions and subscription list details from the OMC database. Create, modify, delete, rename and display subscriptions assigned to active subscription lists. Maintain subscription lists from management applications.
EMOTOROLA LTD. 2000
69
The Alarm display window
ISSUE 18 REVISION 0
The Alarm display window

Access
The alarm display window can be opened: S S S Automatically on startup using autoinitiation files. From the Maps or Alarms icons. From the Event Management icon.
Example display
An example alarm display window with the popup menu displayed is shown in Figure 6-3. All active alarms that are subscribed to in the selected subscription list are displayed in this window. A variable in the system can be set to cause a bell to ring at the OMC terminal when critical, major and/or minor alarms arrive at the OMC.
Figure 6-3 Example alarm display window
Reading the display

The format of the alarm message enables the operator to identify the faulty device (origin of alarm message), to see what type of fault has occurred and its severity. The menu options allow the format of the alarms displayed in the window to be changed. Subscriptions can also be changed, and cleared alarms can be removed from the window, and thus the AET. Alarm messages in the alarm display windows differ from the messages in the event display window. In the alarms display window the operator can interact with two fields when handling alarms, namely, the alarm state field and the operator field. The alarm state field of each message is initially set to NEW and the operator name field to NONE. By selecting the alarm, the alarm state changes from NEW to SEEN. This change is routed back to the AET via the MMI, and all windows subscribing to the alarm message receive an update to the alarm state field. Group handling of alarms of the same type, or alarms that relate to the same fault is possible. More than one alarm can be selected by clicking on them with the middle mouse button. Fault management operations are greyed out if more than one alarm is selected. Refer to the OMC Online Help facility for a full description of all the alarm message fields.
610
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Consolidated alarm reporting

Introduction to consolidated alarms
Consolidated alarm reporting provides information about the OMC GUI map so that an operator can identify and prioritize further investigation of problems in the network. Failures that require operator action, and devices that are out of service will generate alarms. Failures that are quickly recovered by the system and require no operator action will not generate alarms. This feature reduces the number of alarms reported to the operator, and consolidates all information relating to a failure in a single report.
Consolidated alarm report format

Consolidated alarms are generated when a reconfiguration occurs at a BSS. NOTE A reconfiguration is an operation that results in a BSS device changing state. A consolidated alarm can display: 1. 2. 3. 4. Alarm information. Alarm reconfiguration information. Functional Unit severities. OOS device information.
Alarms on map nodes can be viewed in terms of their impact on subscribers or devices. Refer to Network maps in Chapter 2. Figure 6-4 shows the format of a consolidated alarm report.
#Id State Operator Comment Alarm Type Device Class Device Instance Time Device Alarm Alarm Code Device Severity Clearing Info. Cage/Slot Reconfig. Info. Cause Operation Outcome Outage Time Secondary Status Config. Tag Affected FU FU Severity Impacted FUs Affected FU FU Severity OOS Devices OOS Device Operation State Admin. State Reason OOS Device Operation State Admin. State Reason
Figure 6-4 Format of a Consolidated Alarm Report
Refer to Operating Information: GSM System Operation (GSM-100201) for complete information on consolidated alarms.
EMOTOROLA LTD. 2000
611
Alarm handling
ISSUE 18 REVISION 0
Alarm handling
The handling process
When an alarm is first displayed, a GSM network operator takes responsibility for fixing the problem causing the alarm. Any operator may handle any alarm(s) not being handled by another operator, that is, any alarm in the alarm window that has a state field of NEW or SEEN. However, only the operator currently handling a particular alarm may clear it. Each alarm display window contains an alarm handling popup menu (refer to Figure 6-5) that the operator can use to change the state of the alarm(s). Otherwise the Fault Management menu from the menu bar can be used to clear the fault. The changes in alarm state are routed back to the AET, therefore, all operators subscribing to that alarm will know its state. When the operator has rectified the fault causing the alarm, the alarm state can be set to clear, this allows the alarm to be removed, using the alarm handling popup menu.
Alarm handling options

The alarm handling options in the alarm display window available by clicking the right mouse button, and the options available from the Fault Management window are listed in the below table. Popup menu options Handle Unhandle Clear Remove Comment Lock Unlock INS Help Lock Unlock Shutdown INS Reset Reset SITE> Hard or Soft Reassign Swap Fault Management menu
Alarm clearing
When a fault has been fixed, its associated alarm message must be cleared from both the AET at the OMC, and the active alarm list at the NE. Clearing the alarm depends upon the alarm being classified into one of three categories: S S S Fault Management Initiated Clear (FMIC). Operator Initiated Clear (OIC). Intermittent alarm.
Refer to Maintenance Information: Alarm Handling at the OMC (GSM-100501) for complete information on clearing alarms.
612
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
The event display window
The event display window

Access
Event windows are usually configured to display both events and alarms, sequentially displayed according to subscription criteria. Handling of event or alarm messages is not possible in event display windows. Event windows are opened by selecting the Event Mgt icon from the front panel of the OMC MMI. An example event display window is shown in Figure 6-6.
Example display
Figure 6-6 An example event display window The first line of an event/alarm message on arrival is always:
#0 NOT APPL *NONE*
Event messages can have many different formats depending on the type of information they contain. When an event window is opened it is initially empty. A maximum of 512 events/alarms can be displayed in a scrollable window. When a window is full, events/alarms at the top of the list are lost as new events come in. NOTE Events lost to the events display window will be stored, with all the other events, in the events logfile. By subscribing to both events and certain alarms, all incoming messages from a particular NE for instance, can be monitored. The operator can then monitor changes developing in the network.
Refer to the OMC Online Help facility for a full description of all the alarm message fields.
EMOTOROLA LTD. 2000
613
The event logfile
ISSUE 18 REVISION 0
The event logfile

Introduction to event logfile
All events/alarms are routed into an event logfile, which can contain up to 5000 events. All types of alarms/events are stored in the event logs. This includes events generated by a BSS, as well as events generated internally by the OMC. For example, changes to an alarm state field when alarm handling are displayed and updated. The contents of the event logfiles are read-only and cannot be changed.
Logfile creation
Event logfiles may be created in two ways: S Automatically. After 5000 events/alarms the file becomes full, it is then closed and a new logfile is opened with a new date and time stamp. This process is known as rollover. This takes place at midnight even if the previous event log is not full. S Manually. There is a menu option within the MMI that the OMC system administrator can use to disable an event log, then enable a new event log. However, while doing this events arriving at the OMC will be lost.
Logfile procedures
The event logfiles can be accessed using the MMI, or event log processing scripts. This is called post-processing of event logs. An operator can choose to examine events/alarms from the log, based on criteria such as type, time of occurrence or source. Full event logs remain in the file system until the OMC system administrator archives the existing logfiles. The OMC system administrator decides how many logfiles can remain in the file system before they are archived. Refer to Operating Information: OMC System Administration (GSM-100-202) for further details of logfile maintenance procedures.
Logfile location
All events and alarms generated in the network are logged at the OMC to ensure complete traceability within the GSM network. Event logs are stored in the $OMC_TOP/ne_data/ev_logs directory on the System Processor. This directory can also be accessed directly on the MMI processor using $EM_LOG variable, as it is mounted using Network File System (NFS).
614
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
The event logfile
Naming convention
Event logfiles are named using the creation date and time stamp. The file name format is: ev<YYYYMMDDHHMMSS> Where:
YYYY MM DD HH MM SS
is:
Year Month Day Hour Minute Second
Example
The following example event logfile was created on February 12, 2000 at 09.00: ev20000212090000
Logfile rollover
When the event logfile becomes full, it is closed and a new event logfile is opened with a new date and time stamp. This process is known as rollover.
EMOTOROLA LTD. 2000
615
Logging events
ISSUE 18 REVISION 0
Logging events
Event Logs
All events sent to the OMC are stored in Event Logs. It is possible to process Event Logs using this application. Logging of events can also be enabled or disabled from this application. The event logs option is invoked from the Event Logs icon on the Front panel and allows access to: S Search the event logfiles. This is accomplished by loading up to eight event logfiles into an event log search window, and performing searches on the events stored in the files using specified filter criteria as shown in Figure 6-7. S Enable or disable event logging. An OMC system administrator can disable logging, for example, during a maintenance period. It is important to understand that when event logging is disabled, all events and alarms arriving at and produced by the OMC are lost. Event logging cannot be enabled or disabled by a read-only user.
616
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Logging events
The search event log window

Figure 6-7 shows the search event log window that has been opened from the Event Logs icon of the front panel. When the search window is opened, the search criteria can be set so that only specified event messages are displayed.
Figure 6-7 Search event log window
EMOTOROLA LTD. 2000
617
Event/alarm utilities invoked from the command line
ISSUE 18 REVISION 0

Purpose of event logfiles
The event logfile processing utilities are invoked from the command line and are used for two main purposes: S S Post-processing of stored event logs. Printing critical alarms (real-time processing).
Utility listing
The utilities are defined as follows: S cel (Cat Event Log). Processes OMC event logs, which are in binary format, and writes the events to stdout in ASCII format. S qfes (Quick Filter Event Stream). Reads an event stream on stdin (which can be the output of cel or sld) and filters the events based on a single event filter. The output is written in ASCII format to stdout. S ces (Clean Event Stream). Reads an event stream on stdin, removes the start and end tags and writes the output in ASCII format to stdout. S sld (Subscription List Daemon). Receives events from the OMC event management process in real time and writes the events to stdout in ASCII format. S dpr (Direct Printing). Provides an interface between a continuous stream and UNIX file oriented commands, such as the print command lp.
How the event log utilities are used

An overview of the way the event and alarm processing utilities can be used is shown in Figure 6-8.
cel qfes* ces* POST PROCESSING
STDOUT
EM ROUTER
EVENT LOGFILES
sld
qfes*
ces*
dpr* REAL-TIME
PRINTER
* Denotes Optional
PROCESSING
Figure 6-8 Overview of the event log processing utilities available

618
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Post-processing of event logfiles

The post-processing utilities allow scripts to be written which automate the search functionality provided by the OMC MMI. These scripts can be run daily as cron jobs.
Online printing of alarms

The most useful application of real-time processing is directing events/alarms to a printer. This can be achieved using the sld and dpr utilities. The qfes utility may be used to filter events but as sld takes a subscription list as an input parameter, this may not be necessary. Event tags can be filtered using the ces utility.
EMOTOROLA LTD. 2000
619
ISSUE 18 REVISION 0
620
EMOTOROLA LTD. 2000
Chapter 7
Event Management 2
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
ii
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0

Event management overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Events and alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking alarms from the network map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarms: the basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . After detecting an alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening an alarm window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Tools menu in the Alarm and Event windows . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of the Tools menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Tools menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an option in the Tools menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a utility to the CDE menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a utility to the CDE menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Consolidated alarm reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to consolidated alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Consolidated alarm report format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reconfiguration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functional Unit severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OOS devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The View menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Log Search menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the alarm comment field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Entering an alarm comment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing or adding to an alarm comment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing subscription lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscription lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing available subscription lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening a subscription list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying NSS subscription lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blacklist subscription lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blacklist all events from selected device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blacklist this event from selected device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blacklist selected event from all devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a new subscription list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying a subscription list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Renaming a subscription list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a subscription list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing subscriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing subscriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying subscriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a subscription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding GPRS subscriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2000
i
71 71 71 72 73 73 73 73 74 75 75 75 75 76 76 77 77 77 78 78 79 710 711 712 712 712 714 715 715 715 716 716 717 718 719 720 720 721 722 723 723 724 724 724 725 726 726 729
iii
ISSUE 18 REVISION 0
Alarm handling: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Personalizing the display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening an alarm/event window from Event Mgmt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening an alarm/event window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault management actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Acknowledging an alarm arrival . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the subscriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handling an alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . When to handle an alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OIC alarm clearing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Further details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying events with history or from now for an NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of the Events With History function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of the Events From Now function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying events with history or from now . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Circuit Error Rate Monitor feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RCI alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CIC alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connectivity summary window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Throttling alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing alarm throttles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the alarm throttle time period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting an alarm throttle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intermittent alarm throttling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging of events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Searching of event log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loading event logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sort criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the sort criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Filtering event logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reloading event logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying current active event logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing event log search window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling event logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling event logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creation of auto initiation files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AutoInit.CNFG template files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an AutoInit.CNFG file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
730 730 730 731 731 731 731 732 733 733 733 734 734 734 735 735 735 735 736 737 737 737 737 738 738 738 740 741 742 742 742 743 744 744 745 745 745 746 747 748 749 750 750 753 754 755 756 757 758 758 758 759
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Using the event logging utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using cel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using qfes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using ces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Input parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ces example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ces example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using sld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Output format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . sld example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . sld example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using dpr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to cron . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up a cron job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC alarm paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents of a page message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Truncated severity types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Paging performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Paging: how it works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Content of the paging configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Paging error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the paging modem at the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the contents of the pager configuration file . . . . . . . . . . . . . . . . . . . . . . . . Starting paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sending alarms to an e-mail address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description of e-mailing alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite: a Tools menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an e-mail alarm option in the Tools menu . . . . . . . . . . . . . . . . . . . . . . . . .
760 760 760 760 762 763 763 763 764 764 765 766 766 767 768 769 770 770 771 771 771 771 772 772 772 773 774 775 775 775 776 776 776 776
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
vi
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Event management overview

Events and alarms
Event management provides operators at the OMC with a means of managing events and alarms generated by network elements (NEs) on the network. An event is a means by which an NE can report to the OMC. An NE can issue an event to tell the OMC that a statistics file is ready for collection. An alarm is a special type of event used to inform the operator that a fault condition, such as a communications failure, has occurred. The consolidated alarm reporting feature is designed to guide the OMC operator to the most important alarms in terms of impact to the customer. It is further used to guide the operator to the source of those alarms. Event management has the following main functions: S S Collection and logging of all events and alarms reaching the OMC. Presentation of all events and alarms according to subscription criteria.
This chapter shows how to monitor network events and alarms at the OMC, the procedure for handling alarms (detailed further in Maintenance Information: Alarm Handling at the OMC (GSM-100-501)) and how to obtain information from the event logs.
Alarm types
There are three alarm types: S S S FMIC Fault Management Initiated Clear. OIC Operator Initiated Clear. Intermittent.
FMIC
FMIC alarms are not cleared by operators but by the actual software at the NE (BSS or RXCDR) when the alarm fault has been resolved. If an FMIC alarm occurs, either an alarm clear message is displayed or the device is taken out of service. Receipt of an alarm clear message indicates that the alarm condition no longer exists. If an operator is notified that the device has been taken out of service, then the operator must initiate the repair or replacement procedure for the device. An OMC Administrator can clear FMIC alarms at the OMC, but a warning message is displayed. In cases where an FMIC alarm has been cleared at the OMC but the fault condition still exists at the NE, the alarm is again displayed at the OMC following the next alarm resynchronization.
OIC
An OIC alarm indicates that an operator action is required to correct the fault. When the fault has been investigated and resolved, the operator can use the del_act_alarm MMI command to manually clear the alarm at the NE. It is possible to clear OIC alarms in alarm displays at the OMC. However, if the fault condition has not been resolved and the alarm not cleared locally at the NE using the del_act_alarm command, then the alarm is again displayed at the OMC following the next alarm resynchronization.
EMOTOROLA LTD. 2000
71
ISSUE 18 REVISION 0
Intermittent
Intermittent alarms refer to transient non-serious alarms. No alarm clear messages should be expected from the NE for these. Intermittent alarms can be cleared in alarm displays at the OMC. Reporting of intermittent alarms (except those with a severity of critical) can be restricted to a predefined rate. This is done using alarm throttling at the NE. Refer to Throttling Alarms.
Subscriptions
Operators at the OMC must ensure that subscription lists are configured to monitor all BSSs and RXCDRs in the network, as well as the OMC. A subscription to an event specifies a device class, a device instance, an event type, severity of the event, error ID, the number and type of occurrences of the event. Events are then sorted according to these criteria. This chapter also details procedures to explain how to manage subscriptions: Procedures are included to: S S Create, modify, delete, rename and display subscription lists. Create, modify, delete, rename and display subscriptions.
72
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Checking alarms from the network map

Alarms: the basics
When a Critical or Major alarm occurs, this is indicated both by a flashing Alarm icon on the GUI Front Panel, and, if the Maps feature is enabled, the related location icon on the network map changes in colour from green, to red (critical) or yellow (major). This is the default setting. For more information on the general operation of the Network Maps feature, see Chapter 2 of this manual.
After detecting an alarm

For more information, see the Maintenance Information: Alarm Handling at the OMC (GSM-100-501) manual. For information on the meaning of the State fields, refer to Online Help. For information on accessing Alarm Context Sensitive Help, refer to What to do when an alarm occurs in Chapter 8 of this manual.
Further options
Chapter 2 contains procedures for opening windows from the Network map and Navigation Tree, where Status and Out of service (OOS) devices can be checked. See Viewing OOS devices and Displaying OOS devices from the navigation tree.
EMOTOROLA LTD. 2000
73
ISSUE 18 REVISION 0
Opening an alarm window

To open an alarm window from the Network Map, use the following procedure: 1. 2. 3. Select the Maps icon from the Front Panel. A map list window opens. From the Map list window, click on the map on which the required Network Element can be found. The selected map name is highlighted. Double click on the map name. A map window is displayed. NOTE It is possible to open a map which has no Network Elements displayed. In this case, it is impossible to open an Alarm window using this method. 4. 5. 6. 7. Click on the node of Network Element for which an Alarm window is required. Once selected the icon changes colour. Select Display Alarms from the menu bar. An Alarm window opens as shown in Figure 7-1. If there are no current alarms the window will be empty. To close an open alarm window, select File Close from the menu bar. Refer to the manual Maintenance Information: Alarm Handling at the OMC, (GSM-100-501) for procedures on handling alarms.
Figure 7-1 An alarm window
74
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Creating a Tools menu in the Alarm and Event windows
Creating a Tools menu in the Alarm and Event windows

Purpose of the Tools menu
The omcadmin user can create a Tools menu which can be selected by an operator from an Alarm or Event window. The omcadmin user can then add useful functions to the Tools menu as menu options. The menu options can then be quickly and easily selected by an operator. For example, the option to access one of the suite of Cell Optimization Tools, such as, Event Counting Tool (ECT) can be added to the Tools menu.
Creating a Tools menu

To create a Tools menu in the Alarm and Event windows, follow these steps: 1. omcadmin 2. Log in as the omcadmin user. Create the following directory: /usr/gsm/config/global/menus/motorola/subscription/tools When the GUI is restarted, the Tools menu appears in the Alarm and Event windows. Now add a menu option to it.
Creating an option in the Tools menu

To create a menu option in the Tools menu, follow these steps: 1. omcadmin 2. Log in as the omcadmin user. Create a file with a meaningful name in the directory: /usr/gsm/config/global/menus/motorola/subscription/tools The name of the file will appear as an option in the Tools menu. For example, to create a menu option called COP Tools to initiate the COP Tool, create a file called COP_Tools.sh. 3. In the file, type the UNIX command to be executed when the option is selected by an operator. For example, to follow the COP Tools example above, type: #! /bin/sh xterm iconic e /usr/gsm/ne_data/OTG/start_gui.tcl 4. Save the file. When the GUI is restarted, the option appears in the Tools menu. NOTE If the menu option is to be used by all users, ensure that the file has write permissions for all users. In the example given above, when the user selects the COP Tools menu option, the OMC creates an iconized window. When the operator opens the window it displays the COP tool set. If the COP tools set is not displayed, either the COP tools are not installed or they have been installed in a different directory.
EMOTOROLA LTD. 2000
75
Adding a utility to the CDE menu
ISSUE 18 REVISION 0

To add a utility to the CDE menu for an omcadmin user, follow these steps: 1. omcadmin 2. Log in as the omcadmin user. Type the following in the command line window: cd /home/omcadmin/.dt 3. If the machine is a GUI server, use a text editor such as vi to edit the file dtwmrc.GUIServer. If the machine is not a GUI server, edit the file dtwmrc.nonGUIServer. Enter the utility text into the Right Menu Description in the file. For example, to add the utilities dri_status and Network Reports to the CDE menu, enter: nolabel DRI Status nolabel Network Reports f.separator f.exec /usr/gsm/config/global/menus/motorola/subsc ription/tools/DRI_Status.sh f.separator f.exec /usr/gsm/config/global/menus/motorola/subsc ription/tools/Network_Reports.sh
4.
For further details on the utility dri_status, see NO TAGReporting utilities in Chapter 9. 5. 6. Save the file. Press the left mouse button, and select Restart from the popup menu. This restarts the workspace.
The utilities now appear in the CDE menu for an omcadmin user.
76
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0

Introduction to consolidated alarms
Consolidated alarm reporting provides sufficient information on the OMC GUI map so that an operator can identify and prioritize further investigation of problems in the network. This feature reduces the number of alarms reported to the operator and consolidates all information relating to a failure, making it accessible in a single report.
Consolidated alarm report format

A consolidated alarm can display: 1. 2. 3. 4. Alarm information. Alarm reconfiguration information. Functional Unit severities. OOS device information.
Alarms on map nodes can be viewed in terms of their impact on subscribers or devices. Refer to Map display in Chapter 2. Figure 7-2 shows the format of a consolidated alarm report.
#Id State Operator Comment Alarm Type Device Class Device Instance Time Device Alarm Alarm Code Device Severity Clearing Info. Cage/Slot Cause Operation Outcome Outage Time Secondary Status Config. Tag Reconfig. Info. Affected FU From FU Severity To FU Severity Impacted FUs Affected FU From FU Severity To FU Severity ... OOS Device Operation State Admin. State Reason OOS Device Operation State Admin. State Reason OOS Devices
Figure 7-2 Format of Consolidated Alarm Report
EMOTOROLA LTD. 2000
77
ISSUE 18 REVISION 0
Reconfiguration information
The details shown for a consolidated alarm vary, depending on whether the alarm is associated with a reconfiguration or not. NOTE A reconfiguration is an operation (manual or fault management initiated) that results in devices within a BSS changing state. Alarms that are associated with reconfigurations are called tagged alarms. These alarms have a tag, or number, which links all alarms and state changes associated with a reconfiguration. Table 7-1 describes the fields in a consolidated alarm that contain reconfiguration information. Table 7-1 Reconfiguration information Field Name Cause Description Cause of the reconfiguration. Types Fault; OMC request; LMT request; Initialization; Restoration; Remote Unequip; Equip; Unlock; Lock; Shutdown; Swap; Disable; Enable; Reset; LockUnlock; DisableEnableSoft; DisableEnableHard Alarm; Recovered outage; Advisory; Clear; Pending
Operation
Name of the operation taking place.
Outcome Outage Time Secondary Status
Outcome of the reconfiguration. Outage time for recovered outages. Indicates that an alarm is not the main alarm associated with a reconfiguration. A number that links together all alarms and state changes associated with a reconfiguration.
Config. Tag
Functional Unit severities

Functional Unit severities are a snapshot of impacted sites or cells at the time of an alarm. The severity is not necessarily caused by the alarm as a functional unit may be critical before an alarm occurs, and remain critical after the alarm. The list of impacted functional unit severities shows the severity before and after the reconfiguration so that an operator can determine if the alarm caused the severity to change.
78
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
OOS devices
OOS device alarms display a list of up to twenty OOS devices associated with a reconfiguration. An operator can select a device from the OOS device list in an alarm window and perform fault management operations on it. Use the following procedure to perform fault management operations on OOS devices in an alarm window: 1. 2. 3. In an alarm window click on an alarm that contains a list of OOS devices. The selected alarm background is highlighted. Click on an OOS device in the list appended to the end of the alarm. The selected OOS device is highlighted. Refer to Figure 7-3. Fault management operations can now be selected from the Fault Mgmt menu on the menu bar, or from the alarm window popup menu.
Figure 7-3 Alarm with OOS device
EMOTOROLA LTD. 2000
79
ISSUE 18 REVISION 0
The View menu

In an Alarm window, an operator can use the View menu options to exclude or include parts of a report from the display. Refer to Online Help for a description of these options.
Figure 7-4 View menu
710
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
The Log Search menu

An operator can select an alarm that occurs as a result of a reconfiguration and use the Log Search menu to run reports which are retrieved from event logs: S Associated Alarms. Selecting this option runs a report which searches the event logs for all alarms, both primary and secondary that are linked to the reconfiguration associated with the selected event. NOTE Secondary alarms are associated with a reconfiguration but do not cause it because they occur as a result of the reconfiguration. However, they may provide the operator with useful information regarding the fault condition. S Associated State Changes. Runs a report which searches the event logs for all devices that changed state due to the reconfiguration associated with the selected event. Associated Events. Runs a report which searches the event logs for associated alarms and associated state changes that occur as a result of a reconfiguration. Associated OOS Devices. Runs a report which searches the event logs for devices that went out of service as a result of a reconfiguration and remain OOS.
S S
Figure 7-5 Log Search menu
EMOTOROLA LTD. 2000
711
Using the alarm comment field
ISSUE 18 REVISION 0

Introduction
The alarm comment field is used during alarm handling for the recording of causes of alarms, and methods of solution (handling, clearing).
Entering an alarm comment

To enter an alarm comment, perform the following procedure: 1. 2. In an open alarm window, click on the alarm to be commented. The selected alarm background is highlighted. Right-click on the alarm. A popup menu is displayed as shown in Figure 7-6.
Figure 7-6
Opening the alarm comment window
712
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
3.
Select the Comment option and release the button. A comment window is displayed as in Figure 7-7.
Figure 7-7 Alarm comment window 4. 5. Click on the Comment area of the window. The cursor is highlighted and starts flashing. Any relevant comments can now be entered in this area. When the comment has been typed, click OK to save the comment and return to the alarm window. To cancel the comment, click Cancel. (Help is available by clicking on the Help button.)
EMOTOROLA LTD. 2000
713
ISSUE 18 REVISION 0
Viewing or adding to an alarm comment

To add a comment to an alarm field, use the following procedure: NOTE If an alarm already has a comment entered, which can be viewed, this is indicated by the addition of the field COMMENT in the first line of the alarm description in the alarm window. 1. 2. 3. 4. Open an Alarm Comment window. To add to the comment or edit the contents, click on the Comment area. The cursor will flash. Comments can be added, edited or deleted, as required. When the comment has been typed, click OK to save the comment and return to the alarm window. To cancel the comment, click Cancel. (Help is available by clicking Help.)
714
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Managing subscription lists

Subscription lists
A subscription list is used to define a window for monitoring events and/or alarms. The name given to the subscription list is the name which displays in the title bar of the related alarm/event window. Subsequently, subscriptions are used to select the group of events/alarms which are displayed in that window. Each subscription list may be defined as an event or alarm list and is given a unique name. Event lists are for display purposes only, and are empty when first opened. Alarm lists gather alarms or events, whether open or closed, and each alarm or event must be responded to by the operator. When created, a subscription list contains no subscriptions. Subscriptions are added to a subscription list to define the filter criteria for the events/alarms displayed in that window. Regardless of subscription list settings, all events and alarms are logged in the event log at the OMC. See the Logging of events section in this chapter. Related subscriptions may be grouped together into a single subscription list, for example, to monitor all events from a group of base stations. The subscription lists are stored in the OMC database. Each subscription list is given a unique name specified by the operator and may be displayed as an Event or Alarm window on a SPARCstation. This allows several windows to be set up simultaneously on the SPARCstations to monitor different parts of the network. All subscription lists (except hidden subscriptions) are available to all operators. All subscription list commands are entered by menu selection. The following sub-sections describe how to set up and manage subscription lists. These options can only be performed by an operator with read/write permission.
List of procedures
The following is a list of procedures for subscription list management: S S S S S S S Viewing available subscription lists. Opening a subscription list. Displaying NSS subscription lists. Creating new subscription lists. Modifying a subscription list. Renaming a subscription list. Deleting a subscription list.
EMOTOROLA LTD. 2000
715
ISSUE 18 REVISION 0
Viewing available subscription lists

A list of Subscription Lists which are currently configured can be obtained as follows: 1. Select the Event Mgmt icon on the Front Panel to open the Display Subscription Lists window. Subscription lists are displayed in a scrollable window as shown in Figure 7-8. Select the required Subscription List window.
2.
Figure 7-8 Display Subscription Lists window NOTE Operators should each be allocated a number of windows to monitor events and alarms for a specific set of NEs.
Opening a subscription list

To open a subscription list use the following procedure: 1. 2. 3. Open a Display Subscription Lists window as detailed in the previous procedure. Select the required subscription list. Click the Open button to open the subscription list.
716
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Displaying NSS subscription lists

The following procedure makes the subscription lists associated with the Network Status Summary (NSS) map feature temporarily visible, and enables changes to be made to these lists. omcadmin To display the NSS subscription list, perform the following procedure: 1. At the SPARCstation, log in to the MMI processor as omcadmin by using the user id: omcadmin 2. 3. 4. Enter the password when requested. Shut down the GUI that is automatically started by clicking the Exit button on the Front Panel display. Open a UNIX shell window and set the environment variable MMI_FILTER_CHARS_ADMIN by typing the following command: setenv MMI_FILTER_CHARS_ADMIN 5. Verify that the environment variable is correct by entering the following command: env | grep MMI_FILTER_CHARS_ADMIN The output should be as follows:
MMI_FILTER_CHARS_ADMIN=
6. 7. 8.
Run the GUI by executing the following command: gui Select the Event Mgmt option from the Front Panel. The Display Subscription List dialogue window is displayed. The three subscriptions lists .$MAP_ALARMS, $ALM_ALARMS and $ALM_Clear_Alarms are visible with some hidden event and application subscription lists. Click the subscription list to be modified/displayed. Click the Open button to display the Open Alarm display window. The Open Alarm Display window displays all alarms from the selected subscription list.
9.
10. 11. 12. 13.
Select the Subscription option from this window. When the required modifications to .$MAP_ALARMS and .$ALM_ALARMS are completed, exit the GUI by clicking the Exit button on the Front Panel display. Close the UNIX shell by typing the following command: exit Logout of the MMI processor by holding down the left mouse button and selecting the Quit, then the OK option. NOTE Under no circumstances should NSS subscription lists be deleted. If they are, the NSS feature will not function as described. Any changes to subscriptions in the .$MAP_ALARMS subscription list should also be made to the subscriptions in the .$ALM_ALARMS subscription list. Otherwise the NSS feature may not function properly. Subscription lists used internally by the OMC application software become visible during this procedure. Under no circumstances should these subscription lists be modified or deleted. If they are, the OMC will not function as described.
EMOTOROLA LTD. 2000
717
ISSUE 18 REVISION 0
Blacklist subscription lists

The Blacklist Subscription List is created to prevent specified alarms/events from being displayed in an alarm/event display window. All alarms/events subscribed to in the Blacklist Subscription List are switched off in any active alarm display window or event display window. A Blacklist Subscription List can only be created by an omcadmin user. Once the Blacklist Subscription List has been created, subscriptions can be displayed, added, modified, deleted or renamed by omcadmin. All alarms/events subscribed to in the Blacklist Subscription list are switched off in any active Alarm Display window or Event Display window. The blacklist overrides the active subscription list for these windows. NOTE Do not set-up the Blacklist Subscription list in BLOCKING mode.
718
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Blacklist all events from selected device

To blacklist all events from a selected device use the following procedure: NOTE Ensure blacklist subscription is available within display subscription lists, otherwise create blacklisting of events. Refer to Creating a new subscription list in this chapter. 1. Follow steps 1 to 3 of procedure Opening a subscription list.
Figure 7-9 Subscription Blacklist options 2. 3. Select an event, the event background is highlighted. Select Options Blacklist All events from selected device. Refer to Figure 7-9. This option blacklists all events from the selected device. Events from this device are not seen in the event/alarm window.
Figure 7-10 Confirmation window 4. 5. The confirmation window, Figure 7-10, is displayed. Click OK to proceed. Close the subscription window by selecting File Close.
Example
Where alarms are generated for sites or devices which are equipped in the BSS database, but not yet physically installed in the network, these devices can be blacklisted until they are installed, to avoid unnecessary impact reports being displayed in an alarm/event window.
EMOTOROLA LTD. 2000
719
ISSUE 18 REVISION 0
Blacklist this event from selected device

To blacklist selected events from a selected device use the following procedure: 1. 2. 3. Open a subscription list. The subscription list, Figure 7-9 is displayed. Select an event, the event background is highlighted. Select Options Blacklist This event from selected device. This option blacklists the highlighted event from the issuing device.
Figure 7-11 Confirmation window 4. 5. The confirmation window, Figure 7-11, is displayed. Click OK to proceed. Close the subscription window by selecting File Close.
Blacklist selected event from all devices

To blacklist selected events from a selected device use the following procedure: 1. 2. 3. Follow steps 1 to 3 of procedure Opening a subscription list. The subscription list, Figure 7-9 is displayed. Select the desired event, the event background is highlighted. Select Options Blacklist Selected event from all devices. This option blacklists the highlighted event from the device that the event emanated from.
Figure 7-12 Confirmation window 4. 5.

720
The confirmation window, Figure 7-12, is displayed. Click OK to proceed. Close the subscription window by selecting File Close. NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Creating a new subscription list

To create a new subscription list, login as omcadmin, and proceed as follows: omcadmin NOTE At any stage in this procedure the operation can be cancelled by clicking the Cancel button. 1. 2. Select the Event Mgmt icon on the Front Panel. The Display Subscription Lists window is displayed. Click the New button to open the New Subscription List box Figure 7-13.
Figure 7-13 New subscription list box 3. 4. Select the type of subscription list (Alarm or Event, Alarm is the default). Enter the required List Name (maximum of 31 alphanumeric characters). NOTE For a Blacklist Subscription list, the subscription list name must be BLACKLIST and must be entered in upper case type. 5. 6. If required, enter descriptive user information (maximum of 31 alphanumeric characters). This may help later in identifying the list. Check the entries. When correct, click OK. If entries are not correct, select Cancel, re-enter the information, and click OK. NOTE Subscription lists used internally by the OMC application software are only visible to the omcadmin user, using the procedure entitled Displaying NSS subscription lists.
EMOTOROLA LTD. 2000
721
ISSUE 18 REVISION 0
Modifying a subscription list

To modify a subscription list proceed as follows: 1. 2. 3. Select the Event Mgmt icon on the Front Panel. Click on the subscription list to be modified. Click the Modify button to display the Modify Subscription List box as in Figure 7-14.
Figure 7-14 4.
Modify Subscription List box
Make the required changes to User Information (maximum of 31 alphanumeric characters). The List Name cannot be changed using the Modify Subscription List option. Refer to the Renaming a subscription list procedure to rename the list.
5.
Check the modifications and if correct, click OK. If entries are not correct, select Cancel, re-enter the information, then click OK. NOTE At any stage in this procedure, the operation can be cancelled by clicking the Cancel button.
722
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Renaming a subscription list

To rename a subscription list proceed as follows: 1. 2. 3. Select the Event Mgmt icon on the Front Panel. Click the subscription list to be renamed. Click the Rename button to open the Rename Subscription List box as in Figure 7-15.
Figure 7-15 Rename Subscription List box 4. 5. The List Name is displayed. Enter the desired new name (maximum of 31 alphanumeric characters). If the new name is correct, click OK. If incorrect, select Cancel, re-enter the information, then click OK. NOTE Rename fails if the subscription list is open.
Deleting a subscription list

To delete a subscription list proceed as follows: 1. 2. 3. 4. Select the Event Mgmt icon on the Front Panel. The Display Subscription Lists window opens. Click on the subscription list required. Click the Delete button, a confirmation dialogue box is displayed. Click OK to delete the subscription list and clear the dialogue from the workspace. Click Cancel to abort the deletion. NOTE Delete will fail if the subscription list is open or contains active alarms.
EMOTOROLA LTD. 2000
723
Managing subscriptions
ISSUE 18 REVISION 0
Subscriptions
An operator subscribes to events by adding a subscription request for those events. For example, an operator could subscribe to all alarms with a severity level of Minor from BTS23. The Front Panel allows existing subscriptions to be displayed and subscriptions to be added, modified, deleted or renamed. A subscription request can be made to a single NE, to all NEs, or to a device or process within a NE. It is not possible for a single subscription request to be made to a range of NEs such as BSC01, BSC02, BSC06. In this case, a separate subscription request is required for each BSS/RXCDR. These could then be grouped into a subscription list. On installation, default subscriptions are set up for OMC applications. For example, the Performance Management (PM) application needs to subscribe to fileNEavailable events, to be aware of the availability of statistics files. All operator and OMC application subscriptions are maintained in the database on the system processor. More than one subscription list can contain subscriptions to the same event/alarm.
List of procedures
The following is a list of procedures for subscription: S S S S S S S Accessing subscriptions. Displaying subscriptions. Adding a subscription. Modifying a subscription. Renaming a subscription. Deleting a subscription. Viewing associated reconfiguration information.
724
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Accessing subscriptions
The following procedure outlines how to access subscriptions: 1. Select the Event Mgmt icon on the front panel. The Display Subscription Lists window opens, Figure 7-16.
Figure 7-16 Display Subscription Lists window 2. 3. Select the subscription list to be displayed. The selection is highlighted in inverse text. Click the Open button to display the selection (Figure 7-17). The opened Event (or Alarm) window displays all events (or alarms) from the selected event list.
Figure 7-17 Alarm window
EMOTOROLA LTD. 2000
725
ISSUE 18 REVISION 0
Displaying subscriptions
The following procedure outlines how to display subscriptions: 1. 2. 3. 4. 5. Open the relevant alarm/event window as detailed in the previous procedure Accessing subscriptions. Select Subscriptions Display Subscriptions from the menu bar, to open the Display Subscriptions window. Select the required subscription in the text area. Access the Add, Modify, Rename, and Delete windows associated with subscriptions using the subsequent procedures. To close the Display Subscriptions window, click on the Close button.
Adding a subscription
To add subscriptions to a subscription list carry out the following procedure: 1. 2. 3. Refer to the Accessing subscriptions and Displaying subscriptions procedures to open a subscription window. Click on the Add button at the bottom of the window. The Add Subscription box is displayed (Figure 7-18). In the Subscription Name field enter the name of the new subscription. Each name must be unique within a subscription list (maximum of 31 alphanumeric characters). Toggle to Normal or Blocking Subscription Type where: Normal displays all events/alarms specified in this subscription, when the subscription list becomes active. The default is Normal. Blocking does not display the events/alarms specified in this subscription, when the subscription list becomes active. Event/alarm subscriptions specified for other subscription lists are not affected. NOTE For the Blacklist subscription list (omcadmin operators only), do not use Blocking mode.
4.
726
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Figure 7-18 5.
Add Subscription window
From the Device Class field select the required device (using the scroll bar if necessary). See On-Line Help for listings of the available Device, Event and Severity types and Error IDs.
EMOTOROLA LTD. 2000
727
ISSUE 18 REVISION 0
6.
From the Device Instance field select: A network entity within the PLMN or the entire PLMN. A specific instance of the Device Class selected in Step 5, or all classes.
7.
The Event/Alarm Type area of the screen contains a list of known event types for example, processing failure, communications failure. From this list, determine those event types to be included in the new subscription. Select one event type from the display (default is allEvents). Toggle the Event/Alarm Type to Equal or Not Equal where: Equal means that the subscription is equal to the event type selected. Not Equal means that the subscription is not equal to the event type selected. This will include all types but the one selected.
8.
9.
The Severity Type area of the screen contains a list of known severity types. From this list, determine those severity types to be included in the new subscription. Select one severity type from the display (default is allSeverities ). Toggle the Severity Type to Equal or Not Equal where: Equal means that the subscription is equal to the event type selected. Not Equal means that the subscription is not equal to the event type selected. This will include all types but the one selected.
10.
11. 12.
The Error Id area of the screen contains a list of known error id names. Select the required Error Id name from the scrollable list (default is allErrors). Toggle the Error Id to Equal or Not Equal where: Equal means that the subscription will subscribe to all Events which have the same Error Id as that selected from the Error Id scrollable list. Not Equal means that the subscription will subscribe to all Events which do not have the same Error Id as that selected from the Error Id scrollable list.
13.
Enter into the Occurrences field an integer number that specifies how many events/alarms must be received before being displayed (default is 1, max value is 999,999). To set the time (hr:min:sec) schedule for the subscription, select one of the Time areas of the display. Click on the increasing/decreasing arrows until the desired start and end times are displayed (default is 00:00:00 -> 00:00:00, which signifies continuous). Click OK to add the subscription to the subscription list and clear work area.
14.
15.
728
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Adding GPRS subscriptions

It is possible to add a subscription based on any of the GPRS devices, that is: PCU, PSP, DPROC, GBL, GDS, GSL or NSVC. To create an alarm or event filtering subscription for a DPROC, the Hardware Type field in the Add Subscription window (Figure 7-18) must be set equal or not equal to one of the following, as relevant: All DPROC Types DPROC-PRP DPROC-PICP DPROC-FORCE DPROC DPROC-Unknown DPROC To create an event filtering subscription based on the GDS device, the Hardware Type field in the Alarm Subscription window (Figure 7-18) must be set equal or not equal to one of the following, as relevant: All GDS Types TRAU-GDS LAPD-GDS To create an event filtering subscription based on the PSP device, the Hardware Type field in the Alarm Subscription window (Figure 7-18) must be set equal or not equal to one of the following, as relevant: All PSP Types PSP-Motorola MPROC PSP-Unknown MPROC Some GPRS specific hardware types have been added to the list available when creating an alarm or event filtering subscription based on the existing MMS device. The Hardware Type field in the Alarm Subscription window (Figure 7-18) can be set equal or not equal to one of these, as relevant: MMS-ARTESYN NIB MMS-FORCE NIB MMS-Unknown NIB Some GPRS specific hardware types have been added to the list available when creating an alarm or event filtering subscription based on the existing MSI device. The Hardware Type field in the Alarm Subscription window (Figure 7-18) can be set equal or not equal to one of these, as relevant: MSI-ARTESYN NIB MSI-FORCE NIB MSI-Unknown NIB
EMOTOROLA LTD. 2000
729
Alarm handling: overview
ISSUE 18 REVISION 0
Alarm handling: overview

Personalizing the display
To monitor events and alarms open the required event and alarm windows. It is possible to create an Auto Initiate file either globally or for each individual user, which can open the required windows automatically on commencement of a GUI session. Refer to Creating auto initiation files. Some alarms can be easily handled using fault management operations detailed in Chapter 2. Refer to Online Help for information on the structure of the event/alarm messages, and the grades of alarm severity.
List of procedures
The following is a list of procedures for alarm handling: S S S S S Opening an alarm/event window from Event Mgmt. Acknowledging an alarm arrival. Checking subscriptions. Handling an alarm. Throttling alarms.
730
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Opening an alarm/event window from Event Mgmt

Alarm windows
When an alarm window is opened the window is dynamically updated as alarms occur. If the alarm window is iconized, alarms are still collected in the iconized window. An iconized alarm window changes its appearance from a quiet alarm clock symbol to a ringing alarm clock symbol when a new alarm is received.
Event windows
When opened, an event window is empty. It is recommended that event windows be iconized, as events continue to be collected when the event window is iconized. An iconized event window changes its appearance from a quiet alarm clock symbol to a ringing alarm clock symbol when an event is received.
Opening an alarm/event window

To open an Alarm or Event window, carry out the following procedure: 1. Select the Event Mgmt icon on the front panel. A Display Subscription Lists window opens as shown in Figure 7-19.
Figure 7-19 Display Subscription Lists window 2. 3. 4. 5. Select a subscription list. Click the Open button. The selected alarm/event window is displayed. Move and size the alarm/event window to a convenient position on the screen. Repeat the highlighting, moving and sizing for the required number of alarm/event windows. Five or six alarm or event windows can be displayed simultaneously. NOTE It is not possible to display a Detailed View of a PCU device, or a device contained by a PCU, from the Alarm or Event windows at this release.
EMOTOROLA LTD. 2000
731
ISSUE 18 REVISION 0
Fault management actions

If a fault management action (for example, Lock, Unlock, INS, Reset) is attempted for any GPRS device or link from the device instance of an alarm or event window, and it is not feasible, a message is displayed to inform the operator that GPRS service will be lost as appropriate. If a fault management action (for example, Lock, Unlock, INS, Reset) is attempted for any GPRS device from the device instance of an alarm or event window, and it is already in the specified state, the operator will be prompted to perform a PCU resync. If a fault management action (for example, Lock, Unlock, INS, Reset) is attempted for any GPRS device from the device instance of an alarm or event window, and the device does not exist at the BSS, the operator will be prompted to perform a PCU reset.
732
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Acknowledging an alarm arrival
Acknowledging an alarm arrival

Alarm logging
When an alarm arrives at the OMC, it is logged providing event logging is enabled, and displayed on any SPARCstation which has a matching subscription for that alarm. The status field is initially set to NEW and the operator name field to NONE.
Procedure
To acknowledge an alarm: 1. 2. Open an Alarm window, Figure 7-20 is displayed. Select an alarm. More than one alarm can be selected at the same time. Use the middle mouse button to select any additional alarms. 3. The highlighted alarm changes colour. For a critical alarm, the alarm text is displayed in black on a dull red background. The status changes to SEEN. The status is set first to HANDLING and subsequently to CLEAR as the operator deals with the fault which caused the alarm. An alarm can be removed from the window when the state has been set to clear. See the procedure Handling an alarm. NOTE By default, all Critical and Major Alarms are displayed on the map and in alarm windows invoked from the map. The Alarm total displayed on the Front Panel shows only Critical and Major Alarms. All other Alarm severities are set to zero.
Figure 7-20
Alarm handling popup menu
EMOTOROLA LTD. 2000
733
Checking the subscriptions
ISSUE 18 REVISION 0
Checking the subscriptions

Introduction
To check what is being monitored in an Event or Alarm window, select the Subscription option. Refer to the Managing subscriptions section in this chapter for a list of relevant procedures.
Procedure
To check the subscriptions in an Event or Alarm window: In the open Event/Alarm window, select Subscriptions Display Subscriptions from the menu bar. The Display Subscriptions window opens as shown in Figure 7-21.
Figure 7-21 Display Subscriptions window
734
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Handling an alarm
Handling an alarm
When to handle an alarm
Any operator may handle any alarm not being handled by another operator. Only the operator currently handling a particular alarm, or omcadmin user may clear it. (A read-only operator cannot Handle, Un-Handle, add comments, Clear or Remove alarms).
Procedure
Use the following procedure to handle an alarm: 1. 2. Select an alarm to change the Alarm state from NEW to SEEN. Click the right mouse button to bring up the Alarm handling popup menu, then: Select... Handle Un-Handle To... change the State field from SEEN to HANDLING. change the State field from HANDLING to NEW, (active only if Operator field indicates current operator). change the State field from HANDLING to CLEAR, (active only if the Operator field indicates current operator or user is omcadmin). The background of a CLEAR alarm is green. remove the Alarm from the text display area, (enabled only if the State field indicates CLEAR and user is omcadmin). add a comment in the comment field.
Clear
Remove
Comment
If more than one Alarm is selected at the same time, any option chosen is applied to all selected alarms. A warning message is displayed if an operation could not be propagated to all the selected Alarms or Events. NOTE The above items are greyed out for read-only users.
OIC alarm clearing

Operator Initiated Clear (OIC) alarm clearing automatically clears OIC alarms at the BSS, when they have been cleared at the OMC. Once the Clear option is selected from the Alarm handling popup menu, the OMC sends a clear request to the NE. If the alarms clear successfully, the BSS generates a confirmation message for the clear, and the state of the alarm at the OMC is changed to Cleared at the NE and in the Active Event Table (AET) at the OMC. The Alarm windows are then updated to show the alarm changing from Handled to Cleared. Clearing the alarm at the NE prevents the recurrence of the alarm at the OMC following a Resync. If the clear at the BSS fails, or times out after two minutes, an error box is displayed, and the AET is not changed. A maximum of 30 OIC alarms can be cleared simultaneously.
EMOTOROLA LTD. 2000
735
Handling an alarm
ISSUE 18 REVISION 0
Further details
Information on action which should be taken to investigate and clear alarms is given in: Maintenance Information: Alarm Handling at the OMC (GSM-100-501).
736
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Displaying events with history or from now for an NE
Displaying events with history or from now for an NE

Purpose of the Events With History function
The Events With History function allows an operator to open a window showing the recent event history for a selected network device. The OMC retrieves the recent events from the event log files. This function is useful when the operator is troubleshooting a problem and needs to know the sequence of event activity on the device up to the present time. An operator can select this function from a map display or the navigation tree.
Purpose of the Events From Now function

The Events From Now function allows an operator to open a window showing events that occur from the time the window is opened for a selected network element. This is useful when an operator is waiting for responses to actions that result in events. An operator can select this function from a map display or the navigation tree.
Displaying events with history or from now

To display events With History or From Now for an NE, follow these steps: 1. 2. Select the network element for the required event details. Select Display Events With History to display historical events for the network element. The OMC displays the With History window, which contains a list of the event history for the device. Alternatively, select Display Events From Now to display future events for the network element. The OMC displays the From Now window, which displays any events that occur for the device.
EMOTOROLA LTD. 2000
737
The Circuit Error Rate Monitor feature
ISSUE 18 REVISION 0

Introduction
The Circuit Error Rate Monitor (CERM) feature enables RCI (Radio Channel Identifier) and CIC (Circuit Identity Code) alarms to be generated when an error count threshold is exceeded. The alarms specify RCI/CIC path details. NOTE RCI and CIC alarms are treated as FMIC alarms at the OMC. A subscription list can be created to monitor RCI and CIC alarms. Refer to Managing subscriptions . Information on CERM configuration is given in: Installation and Configuration: GSM System Configuration (GSM-100-403)
RCI alarms
There are two types of RCI alarms: S S RCI alarm with Collocated BTS. All device information is included in the alarm window, so further investigation is not required. RCI alarm with Remote BTS. Not all the device information is included in the alarm window, therefore the operator will need to investigate further to obtain specific BTS information.
Use the following procedure to investigate an RCI alarm with Remote BTS: 1. 2. Select the RCI alarm. Select Options Show Connectivity from the menu bar, the Path Detailed View for the Path opens, see Figure 7-22.
738
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Figure 7-22 Path Detailed View Specific information relating to the RCI path alarm can be obtained in the Detailed View. Information on RCI alarm troubleshooting procedures is given in: Maintenance Information: Alarm Handling at the OMC (GSM-100-501)
EMOTOROLA LTD. 2000
739
ISSUE 18 REVISION 0
CIC alarms
There are two types of CIC alarms: S S CIC alarm with Local Transcoding. All device information is included in the alarm window, so further investigation is not required. CIC alarm with Remote Transcoding (Figure 7-23). Not all the device information is included in the alarm window, therefore the operator will need to investigate further to obtain specific remote transcoder information.
Use the following procedure to investigate a CIC alarm with remote transcoding: 1. 2. Select the CIC alarm. Select Options Show Connectivity from the menu bar, the Connectivity Summary window opens.
Figure 7-23 CIC alarm
740
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Connectivity summary window

The Connectivity Summary window lists the three MMS devices of the CIC part of the circuit, along with their State Information. These devices are the RXCDR>MSC MMS, the RXCDR>BSC MMS, and the BSC>RXCDR MMS. NOTE Double-clicking on a row with device information opens the devices Detailed View. Single-clicking selects a row, this allows access to the menu options relevant to that device. The MSI (Multiple Serial Interface) or MMS Detailed View or Parent Detailed View can be opened from the Edit menu. Select the Parent MSIs toggle button option on the View menu to display/hide Parent MSI information. When only MMS information is displayed, select View Parent MSIs and the list expands to display the parent MSI and its State Information for all rows for which MMS information was retrieved. If this option is selected when both MMS and MSI information is displayed then the list contracts to display only MMS information. Remote login to the parent NE is available when either an MMS or MSI row is selected. Select Options Remote Login and a RLogin window is displayed. The operator can Lock, Unlock, INS, and Reset devices using options on the Fault Mgt menu. Information on CIC alarm troubleshooting procedures is given in: Maintenance Information: Alarm Handling at the OMC (GSM-100-501)
EMOTOROLA LTD. 2000
741
Throttling alarms
ISSUE 18 REVISION 0
Throttling alarms
Introduction
Reporting of some alarms can be restricted so they are only reported if they exceed a pre-defined rate. This is called alarm throttling. For GSR4 BSSs only alarm throttles can be viewed, created, edited, and deleted from the Navigation Form. Alarms and alarm types are described in Maintenance Information: Alarm Handling at the OMC (GSM-100-501).
Viewing alarm throttles

To view alarm throttles use the following procedure: 1. 2. 3. Select the Config Mgmt icon on the Front Panel, a Navigation Form is displayed. Select the required BSS or RXCDR on the Navigation Form. Select Config Mgt Alarm Throttles from the menu bar, the Alarm Throttles window opens (Figure 7-24).
Figure 7-24 Alarm Throttles window
742
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Throttling alarms
Changing the alarm throttle time period

An alarm throttle time period can be changed for a device. Use the following procedure to change the time period: 1. 2. 3. 4. Follow steps 1 to 3 in the procedure Viewing alarm throttles to open an Alarm Throttles window. Refer to Figure 7-24. Select the required alarm throttle from the list. Select Edit Detailed View from the menu bar, the Alarm Throttle Detailed View is displayed. Refer to Figure 7-25. The alarm throttle time period can be changed in the Alarm Throttle Period field. The time period defines how many times, within a minute, a specific alarm can occur before the operator is informed.
Figure 7-25 Alarm Throttle Detailed View
EMOTOROLA LTD. 2000
743
Throttling alarms
ISSUE 18 REVISION 0
Deleting an alarm throttle

To delete an alarm throttle use the following procedure: 1. 2. 3. Follow steps 1 to 3 in the procedure Viewing alarm throttles to open an Alarm Throttles window. Refer to Figure 7-24. Select the required alarm throttle. Select Edit Delete. The message Deleting
object
is displayed in the status bar.
Intermittent alarm throttling

For pre-GSR4 BSSs intermittent alarms the throttle time period can be changed only from the command line. Intermittent alarms are transient, non-serious alarms. NOTE Parameters displayed within square parenthesis [] are optional. 1. To set the throttle time period for intermittent alarms, remote login to a BSS and enter the following MMI command: chg_throttle <device_name> <alarm_code> <throttle_count> The throttle time period is set by defining how many times, within a minute, a specific intermittent alarm can occur before the operator is informed. 2. To display the current throttle time period for an alarm, remote login to a BSS and enter the following MMI command: disp_throttle [<device_name> <alarm_code>]
Example setting the throttle time period

This example changes the throttle period for device MMS, alarm code 1 to 10 minutes: chg_throttle mms Where: mms 1 10 The system response is:
COMMAND ACCEPTED
10 is: device_name alarm_code throttle_count
Example displaying the throttle time period

This example displays the throttle period for device DRI, alarm code 66: disp_throttle dri Where: dri 66 The system response is:
Hardware version number: 3 Alarm Alarm Throttle Source Code DRI 66 Time 5 Alarm Description Host Counter Mismatch
66 is: device_name alarm_code
744
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Logging of events
Logging of events
Introduction
Click on the Logging icon to open the Event Log Search window. The Event Log Search window provides a means to search through events stored in the event log files, using certain criteria. CAUTION If the Event Logging function is disabled, events arriving at the OMC are lost and cannot be recovered. Logging options enable the user to open, view and print the contents of the Event Logs. Different search criteria can be applied through optional filters to enable post processing of selected Events. The normal and default state of the Event Log is enabled. When the Event Log is enabled all Events (and Alarms) arriving at the OMC or produced by the OMC are logged in a log file. When a log file becomes full (5000 events) it is automatically closed and a new file opened with a date/time stamp. An operator can disable logging, for example during maintenance periods. It is important to note that when Event logging is disabled, all Events and Alarms arriving and produced by the OMC are lost. Event logging can only be enabled or disabled by an omcadmin user.
List of procedures
The following is a list of procedures for event logging: S S S S S S S S S S S Searching event log files. Loading event logs. Changing the Event Log Search window format. Sorting event logs. Filtering event logs. Reloading event logs. Displaying event logs. Printing an event log. Enabling the event logging procedure. Disabling the event log procedure. Auto initiation files.
EMOTOROLA LTD. 2000
745
Logging of events
ISSUE 18 REVISION 0
Searching of event log files

Use the following procedure to search event log files: 1. At the Front Panel display select the Event Logging icon to open an Event Log Search window as shown in Figure 7-26. Multiple event log files can be loaded in this window.
Figure 7-26 Event Log Search Window 2. To open up to eight Event Log Search windows, select File Open New Window from the menu bar. Each new window opened is sequentially numbered in the title bar of the Event Log Search window, as shown in Figure 7-26. Windows initially have no open event log files and the text area is blank.
746
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Logging of events
Loading event logs

To load Event Logs into an Event Log Search window, carry out the following procedure: 1. With an Event Log Search window open, select Options Load Event Log from the menu bar, to open the File Selection window (Figure 7-27).
Figure 7-27 File Selection window 2. Select a directory in the Directories list, then an Event log filename in the Files list. NOTE The Filter field in the File Selection box enables a directory mask to be used to limit the number of files displayed. Edit the directory mask string in the Filter field, to specify the base directory to be examined and the search pattern. When the File Selection box is first displayed, the directory mask defaults to the value specified by the environment variable $EM_LOG . 3. Click OK to load the selected Event log into the Event Log Search window. NOTE Up to eight Event Log files can be loaded at any one time, within one MMI session, either in one Event Log Search window, or in up to eight different windows. 4. 5. Use the Event Log Search window scroll bars to view the events in the Event log. When the new file is loaded, the most recently defined filter is applied to its contents. Event messages from this file that satisfy the filter criteria are then displayed in the window. Refer to the Filtering event logs procedure for more information on Event Log filters.
EMOTOROLA LTD. 2000
747
Logging of events
ISSUE 18 REVISION 0
Changing format
Event Log messages can be displayed in one of two formats. Refer to Online Help for a description of the formats.
Full Format
Select View Full to display messages in Full format (Figure 7-28).
Figure 7-28 Full Format Event Log Search window
Wide Format
Select View Wide to display messages in Wide format.
748
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Logging of events
Sort criteria
Information is displayed in the Event Log Search window, according to sort criteria selected using the Sort option (Figure 7-29). There are two sort criteria as follows: S S Sort Field Any one of the nine Event message fields. List Order In either Ascending or Descending order.
Figure 7-29 Event Log Search - Sort menu options
EMOTOROLA LTD. 2000
749
Logging of events
ISSUE 18 REVISION 0
Setting the sort criteria

To set the Sort criteria, carry out the following procedure: 1. 2. With an Event Log Search window open and an Event log loaded, select Sort from the menu bar. To select a sort field from the Sort menu, click on the radio button associated with that field (Figure 7-29). The sort fields are mutually exclusive, that is, selecting one sort field automatically deselects all others. Click on the appropriate radio button in the Sort menu to select Ascending or Descending order.
3.
Filtering event logs

Event log files can be filtered to enable only selected event log information to be displayed. Use the following procedure to select filter criteria that can then be applied to Event log searches: 1. Refer to the Searching event log files procedure to open an Event Log Search window. NOTE Operations can also be performed on groups of events shown in an Event Log window. See Online Help for information on the Select, Select All and De-select All options.
750
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Logging of events
2.
Select Options Filter to open the Define Filter Criteria window (Figure 7-30).
Figure 7-30 Define Filter Criteria window 3. Click on the Normal or Exclude radio button to select Normal or Exclude type filtering. The default setting is Normal, where the filter checks for Event log titles corresponding to the information defined in the following steps. When Exclude is selected, the filter checks for all Event log titles which do not correspond to the information defined.
EMOTOROLA LTD. 2000
751
Logging of events
ISSUE 18 REVISION 0
4.
Use the Device Class, Hardware Type, Device Instance, Event Type, Severity Type and Error Id areas, if required, to select Equal/Not Equal error criteria for which to filter. These are selected as described in steps 5 to 7. NOTE It is not essential to select any of these criteria. If not required, simply omit these steps and enter a filter string commencing at step 15. See Online Help for listings of the available Device, Event and Severity types, Error IDs and Hardware types.
5. 6.
From the Device Class field select the required device (using the scroll bar if necessary). The Hardware Type area of the screen contains a list of hardware types. From this list, determine those hardware types to be included in the new subscription. Using the left mouse button, select one hardware type from the display. Toggle the Severity Type to Equal or Not Equal where: Equal this filters for logs containing the hardware type selected. Not Equal filters for logs not containing the hardware type selected. This will include all types but the one selected.
7.
8.
From the Device Instance field select: A network entity within the PLMN or the entire PLMN. A specific instance of the Device Class selected in Step 5, or all classes.
9.
The Event Type area of the screen contains a list of known event types, for example, processing failure, communications failure. From this list, determine those event types to be included in the filter criteria. Using the left mouse button, select one event type from the display (default is allEvents). Toggle the Event Type to Equal or Not Equal where: Equal filters for logs containing the event type selected. Not Equal filters for logs not containing the event type selected. This will include all types but the one selected.
10.
11.
The Severity Type area of the screen contains a list of known severity types. From this list, determine those severity types to be included in the new subscription. Select one severity type from the display (default is allSeverities). Toggle the Severity Type to Equal or Not Equal where: Equal filters for logs containing the severity type selected. Not Equal this filters for logs not containing the severity type selected. This will include all types but the one selected.
12.
13.
The Error Id area of the screen contains a list of known error id names. Select the required Error Id name from the scrollable list (default is allErrors).
752
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Logging of events
14.
Toggle the Error Id to Equal or Not Equal where: Equal filters for logs containing the Error ID selected. Not Equal this filters for logs not containing the Error ID selected. This will include all types but the one selected.
15.
To define a filter string, enter the string in the Filter String text box. The string must be alphanumeric with a maximum of 31 characters (the string is case sensitive). By selecting the wildcard option the Filter String will contain a wildcard, the search string bss with wildcard selected finds all entries containing bss, for example, bss01, bss02, bss03...... NOTE For subsequent searches, the previously defined filter criteria are used as the default filter string.
16.
To set the time (hr:min:sec) and date schedule for the subscription, select one of the Time areas of the display. Click on the increasing/decreasing arrows until the desired start and end times and dates are displayed (default is 00:00:00 -> 00:00:00, which signifies continuous). To apply the filter criteria to the event messages currently displayed in the Event Log Search window, click OK in the Define filter criteria window. The filter is also applied to new event log files loaded into the window if it is the last filter defined before the file is loaded.
17.
Reloading event logs

The complete contents of all loaded Event Log files can be reloaded into the search window. To reload the Event Log files, carry out the following procedure: With an Event Log Search window open, select Options Reload Event Logs (Figure 7-31). All the loaded Event Logs are reloaded with applied filters removed.
Figure 7-31 Event Log Search - Options menu

EMOTOROLA LTD. 2000
753
Logging of events
ISSUE 18 REVISION 0
Displaying current active event logs

A list of all the Event Logs that are currently loaded in the active Event Log Search window can be displayed, as shown in Figure 7-32. To display a list of currently loaded Event Logs, carry out the following: 1. With an Event Log Search window open, select Options Display Event Logs List. A list of all the Event Logs that are currently loaded in the active Event Log Search window are displayed in a Currently Loaded Event Logs window (Figure 7-32). NOTE The Currently Loaded Event Logs window also enables more Event Logs to be loaded and the already open event logs to be reloaded. 2. 3. Click on the Load button and refer to the Loading event logs procedure to load more Event Logs. Click on the Reload button and refer to the Reloading event logs procedure to reload Event logs.
Figure 7-32 Display Event Log List window
754
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Logging of events
Printing event log search window

To print the contents of an Event Log Search window carry out the following procedure: 1. Perform the procedures in the Loading an event log procedure, or, if a number of windows are already open, click the left mouse button with the mouse pointer in the window to be printed. Select File Print All. A menu of available printers is displayed. NOTE Select File Print Selected to print selected alarms and/or events in the window. 3. 4. Select a printer from the printer menu. Figure 7-33, the command confirmation window opens. Click Yes to include comments in the print out.
2.
Figure 7-33 Command confirmation window A confirmation window is displayed with the following message Printer Been Submitted. Click OK to continue.
Job has
NOTE The output of an Event Log Search window is always printed in full format. Refer to the Changing format procedure.
EMOTOROLA LTD. 2000
755
Logging of events
ISSUE 18 REVISION 0
Enabling event logging

This procedure can only be performed by omcadmin level users. The Options Enable Event Log selection is greyed out for other users. To enable event logging, proceed as follows: 1. 2. At the Front Panel display select the Event Logs icon to open an Event Log Search window. Select Options Enable Event Log to open the Enable Event Log confirmation window (Figure 7-34). This enables entry of a pathname and a filename (both are optional). Enter the pathname and filename, if required, using alphanumeric characters ( the maximum length for the pathname, and also the filename, is 31 characters).
3.
Figure 7-34 Enable Event Log confirmation window 4. If nothing is entered, click OK, and the default Event Log File is enabled, as follows: path = /usr/gsm/ne_data/ev_logs /ev<YYYYMMDDHHMMSS> filename = ev<ddmmyyyy-hhmm> Where: ddmmyyyy hhmm 5. is: the date of enable the time of enable
When the pathname and filename are correct, click OK to indicate that the file specified is to be used for event logging.
756
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Logging of events
Disabling event logging

CAUTION If the Event Log is disabled, events and alarms are routed to appropriate operator windows, BUT no events are logged at the OMC and the event history information is lost. Therefore the Event Log should normally be enabled and only disabled for specific maintenance tasks. This procedure can only be performed by omcadmin level users. The Disable Event Log menu option is greyed out for other users. To disable Event logging, perform the following procedure: 1. 2. 3. At the Front Panel display, select the Event Logs icon to open an Event Log Search window. Select Options Disable Event Log from the menu bar. The confirmation box (Figure 7-35) is displayed. Click OK to disable all Event logging.
Figure 7-35 Disable Event Log box
EMOTOROLA LTD. 2000
757
Creation of auto initiation files
ISSUE 18 REVISION 0

Introduction
To enable operators to define which subscription lists they subscribe to, an ASCII file is placed in their home directory. The file must be named AutoInit.CNFG . This ASCII file is also used to specify which icons or open windows display automatically at the beginning of each MMI session. The AutoInit.CNFG file will be opened and parsed on initiation of an MMI session. At the same time the alarm/event windows listed in the file will be created and displayed. An Auto Initiation file may be created, either for global usage, or for individual operators. In each case the file format is identical. The globally accessible file can be used to define windows which should appear for every operator. Such a file for global use should be placed in the directory: $(OMC_TOP)/config/global . On initiation of the MMI, the system will search for global and local examples of the AutoInit.CNFG file. If either is found, the system will attempt to load it. If both are found, then both will be loaded.
AutoInit.CNFG template files

Template AutoInit.CNFG files are contained in the directory /usr/gsm/config/global. These can be used to create a single standard AutoInit.CNFG file, or specific versions of AutoInit.CNFG for individual users. The template AutoInit.CNFG files provided are: S AutoInit.CNFG.map This template file contains instructions to create a file containing maps, which are automatically opened when the GUI starts:
# Fill in the name of the maps to be opened and uncomment the line # OpenMapDisplay <mapname> geom 188 98
AutoInit.CNFG.status This template file contains instructions to create a file containing device status displays, which are automatically opened when the GUI starts:
OpenUploadStatusDisplay geom 261 124 OpenDownloadStatusDisplay geom 144 478
AutoInit.CNFG.logs This template file contains instructions to create a file containing log displays which are automatically opened when the GUI starts:
OpenAuditLogDisplay geom 40 500 OpenResyncLogDisplay geom 214 152
AutoInit.CNFG.nav This template file contains instructions to create a file containing an entry for the Navigation Tree which are automatically opened when the GUI starts.
OpenConfigMgtDisplay geom 188 98
758
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Creating an AutoInit.CNFG file

To create a AutoInit.CNFG file carry out the following procedure: 1. 2. Use a text editor to create a file named AutoInit.CNFG. Create file records for each window to be automatically displayed. Each record must consist of a command specifying which type of window to display, along with the name of the display as follows: For an alarm display, use the command OpenAlarmDisplay <alarm subscription list name> For an event display, use the command OpenEventDisplay <event subscription list name> If the first field is not as shown in either of these examples, the operator is notified and file loading will continue with the next line. NOTE The alarm/event subscription list name must be specified exactly as the list name displays in the MMI. The name must be contained within double quotes. If the name does not exist, an error message is displayed, and file loading will continue with the next line. Any duplication of alarm/event display names within the files will not result in duplicate windows being opened. 3. An optional geometry co-ordinates field can be added to specify the position of an Event/Alarm window. This field takes the format: geom <Geometry> where Geometry is in the following format: <width>x<height>{}<xoffset>{}<yoffset> If a geom field does not exist, positioning of the window will be determined by the OSF-Motif software. 4. Add the following optional field to iconize the Event/alarm window: iconised 5. Repeat Steps 2 to 4 for each window to be opened automatically on initiation of the GUI. NOTE Initiation of the GUI will continue regardless of any errors in the AutoInit.CNFG file.
EMOTOROLA LTD. 2000
759
Using the event logging utilities
ISSUE 18 REVISION 0

Introduction
The following utilities can be used to display and manipulate event logs. A full description of the utilities is given in Online Help.
List of procedures
The following is a list of procedures for utilities: S S S S S S Using cat event log (cel). Using quick filter event stream (qfes). Using clean event stream (ces). Using subscription list daemon (sld). Using direct printing (dpr). Setting up a cron job.
Using cel
The Cat Event Log cel utility converts binary event logs to ASCII, and prints each event from each of the specified event logs (in full ASCII format) to stdout . It takes one or more arguments, the name(s) of the event log(s) to print and the date. The cel utility is found in /usr/gsm/current/bin . Run cel in the directory /usr/gsm/ne_data/ev_logs. NOTE A cron job should be created to generate an event report at regular intervals, using the cel, qfes and ces utilities (see Setting up a cron job). Use the ces, sld and dpr utilities for on-line printing of alarms.
Format
At a SPARCstation login as omcadmin. The cel input format is as follows: cel ev<YYYYMMDDHHmmSS>
760
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Examples
In the following example cel is used to process an event log that was created on 5th February 1993, at 14.00. The event log contains events/alarms generated after that date and time. (Only a sample of the output is shown): cel ev19930205140000
Startup BeginEvent #0 -NOT APPL -*NONE* . linkFailureEvent -BSS -Cork_1 -05/02/93 14:00:24 [30003] x25CircuitDown -Critical EndEvent BeginEvent #0 -HANDLING -. updateAlarmDisplayAddrEvent -omc -omc -05/02/93 14:52:43 EndEvent : :much more output : BeginEvent #0 -CLEARED -*NONE* linkFailureEvent -BSS -Dublin_1 -05/02/93 -15:30:02 [30003] xCircuitDown -Critical EndEvent Shutdown
In the following example cel is used to process two event logs: cel ev19930205140000 ev19930205183000 In the following example cel is used to process all event logs from the 5th February 1993: cel ev19930205* In the following example cel output is redirected to a file: cel ev19930205* > ascii_log NOTE ev19930205* will match all event logs that start with ev19930205.
EMOTOROLA LTD. 2000
761
ISSUE 18 REVISION 0
Using qfes
qfes filters events based on a single filter, then output in ASCII. After accessing the specified event logs using the cel utility, the operator can look for specific events in the accessed event logs. Use the qfes utility (found in /usr/gsm/current/bin ) to implement this. The qfes utility filters an event stream read from stdin against a single subscription specified on the command line. For an event to pass through the filter it must meet the criteria of the subscription record. It takes from 5 to 10 arguments. If the event meets the subscription criteria, it is printed (in full ASCII format) to stdout , or may be directed to a file. NOTE The first five arguments of the qfes command are mandatory arguments entered between quote marks. A null argument can be used for any of these arguments. A null argument must include the enclosing quote marks with no spaces between the quote marks. All arguments, including null arguments are separated by a space.
Format
The format for a subscription record is as follows : event_type device_type device_instance startTime endTime [ infostring [infostring [....]]]
Examples
In the following example qfes is used to filter all BSS Critical alarms from the Event Log which was created on 12th February 1993, at 21.00. Note that Critical is an infostring parameter. (Only a sample of the output is shown): cel ev19930212210000 | qfes BSS Critical
Startup BeginEvent #0 -NOT APPL -*NONE* linkFailureEvent -BSS -Cork3 -12/02/93 21:34:56 [30003] x25CircuitDown -Critical EndEvent BeginEvent #0 -NOT APPL -*NONE* linkFailureEvent -BSS -Cork5 -12/02/93 22:14:26 [30003] x25CircuitDown -Critical EndEvent Shutdown
In the following example qfes is used to filter linkFailureEvent for an RSL device on Cork_1 on 5th February 1993 between 09.00 and 09.30: cel ev19930205* | qfes linkFailureEvent RSL Cork_1 19930205090000 19930205093000 In the following example qfes is used to filter all DRIS stateChangeEvents on Dublin_7, SITE Blackrock, from event log generated on 1st January 1993: cel ev19930101* | qfes stateChangeEvent DRIS Dublin_7(Blackrock)
762
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Using ces
The ces removes header information which comes from filtering event logs, and output in ASCII. The ces utility takes an event stream read from stdin (as produced by cel, sld or qfes) and prints the events to stdout without the <Startup>, <Shutdown>, <BeginEvent>, <EndEvent> tags. The utility takes no arguments. The ces utility is located in: /usr/gsm/current/bin/ces .
Format
ces takes no arguments. The ces utility must be run from the MMI processor. ces does not have any specific environment requirements but accepts input generated by cel, sld or qfes.
Input parameters
None.
ces example 1
The ces utility filters <Startup> , <Shutdown> , <BeginEvent> and <EndEvent> tags from the event stream. cel ev19930212210000 | qfes BSS Critical | ces Only a sample of the output is shown below:
#0 NOT APPL *NONE* linkFailureEvent BSS Cork3 [30003] x25CircuitDown Critical #0 NOT APPL *NONE* linkFailureEvent BSS Cork5 [30003] x25CircuitDown Critical : : 15/02/93 10:34:56
15/02/93
11:14:26
EMOTOROLA LTD. 2000
763
ISSUE 18 REVISION 0
ces example 2
This is the same as Example 2 of sld (see Using sld section in this chapter). sld DRI_Alarms | ces | dpr i lp s lp onofullbreak
Using sld
The sld utility receives events from the OMC Event Management process in real time, and output in ASCII. The sld utility provides a command line interface to OMC Event Management (EM). The sld utility obtains events/alarms from EM in real-time, via the EM subscription mechanism, and outputs this information in ASCII text to stdout . The sld utility is located in: /usr/gsm/current/bin/sld The sld utility obtains alarm and event information from the EM process on the system processor based on a specified subscription list. The subscription list may be an Event List type, or update events may be forwarded to an alarm list type. The information received from EM is then translated to ASCII text and written to standard-output. CAUTION Do not handle Alarms using sld; this must be done using the Front Panel. If sld is used for this purpose, there is a risk of AET filling up, in which case any further Alarms would not be treated as such, but as Events. The sld utility must be run on the MMI Processor. sld requires the OMC to be running so that it can receive events from the OMC Event Management. sld also uses OMC environment variables such as $OMC_IPC_CONFIG (used to locate the OMC processes). It is recommended that sld is only run after sourcing the OMC environment variables file mmiCommon.sh which is located at: /usr/gsm/current/config/mmiCommon.[c]sh Add /usr/gsm/current/bin to the shell search path, $PATH, so that the full path to sld does not have to be specified as part of the command line. Format The sld utility takes a single parameter, a subscription list name. The subscription list name must be a valid Event/Alarm List type. The syntax for invoking the sld utility is as follows: sld <subscription_list_name> NOTE Stopping the OMC will not stop sld processes. If the OMC is stopped the sld process should be killed or interrupted. Use the keyboard command CTRL-c to shutdown the sld. The sld may be restarted once the OMC is functioning again.
764
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Output format
The output format from the sld utility is as follows:
Startup BeginEvent <Event information> EndEvent BeginEvent : : Shutdown
The contents of the output format are as follows: Where:

Startup
is: Text signifying that the sld utility has started. Text signifying the beginning of Alarm/Event information. This is printed for each event in an event log. The text of the event. Text signifying the end of Alarm/Event information. Text signifying that the sld utility has terminated.
BeginEvent
<Event information> EndEvent
Shutdown
EMOTOROLA LTD. 2000
765
ISSUE 18 REVISION 0
sld example 1
To monitor RCU alarms as they occur, open up an xterm window and input the command sld All_Alarms. For this to work the following must be true: S S The OMC must be up and running. A subscription list called All_Alarms must exist and must contain a subscription (by class) to all DRI events.
The sld utility obtains real-time Alarm and Event information from the EM process on the system processor based on the All_Alarms subscription list. The information received from EM is then translated to ASCII text and written to stdout . A sample of the output is as follows:
Startup BeginEvent #0 NOT APPL *NONE* . linkFailureEvent BSS Cork_1 [30003] x25CircuitDown Critical EndEvent
05/02/93
14:00:24
BeginEvent #0 HANDLING Thames . updateAlarmDisplayAddrEvent omc omc 05/02/93 14:52:43 EndEvent : more output : BeginEvent #0 CLEARED Thames linkFailureEvent BSS Dublin_1 05/02/93 15:30:02 [30003] xCircuitDown Critical EndEvent Shutdown
In the above example the output is sent to stdout
sld example 2
The sld utility is usually used with dpr to direct its output to an on-line printer: In this example, the sld utility directs incoming events/alarms subscribed to by the DRI_Alarms Subscription List through the ces utility and via dpr to the default printer. The ces utility is described in the ces section in this chapter, while the dpr utility is described in the dpr section in this chapter.
766
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Using dpr
The dpr utility provides an interface between a continuous input stream and a UNIX system command. The primary purpose for the dpr utility is to interface to file oriented commands such as lp. The commands used by the dpr utility are termed interface commands. The dpr utility reads data from stdin and writes the data to the interface command via a UNIX pipe. This type of data flow necessitates that the interface commands specified read data from stdin . The dpr utility is designed to operate with the the UNIX lp command for directing data to a dedicated line-printer device. The utility monitors the data input rate and attempts to produce the output at a rate which will not render the system inoperative. The dpr utility allows for output page formatting. It assumes the dedicated line printer device may be configured such that form feeds between files may be disabled. For devices on which form feeds may not be disabled, the dpr utility allows for output based only on fully formatted pages. The dpr utility must be run on the MMI processor and may be executed without any special set-ups to the environment, providing the interface commands are accessible/locatable during the dpr execution. The dpr utility takes several optional parameters. The dpr parameters may be used for controlling the operations of the dpr utility including page formatting.
EMOTOROLA LTD. 2000
767
ISSUE 18 REVISION 0
Format
The following must be typed as one line with no carriage returns: dpr [i <cmd>] [s <cmd>] [h <header>] [f <footer>] [p <page_length>] [t <top_margin>] [b <bottom_margin>] [r] Where: i <cmd> is: The initial interface command. The default command is cat. Usually the initial interface command begins the printing process, for example, i lp onofilebreak The subsequent interface command (optional). For example, s lp onofilebreak onobanner The page header. The header text is printed after the top margin. A single line is automatically skipped after the header is printed. The header can contain embedded carriage returns. The header can also contain the symbol %d that prints page numbers. The page footer. The footer text is printed before the bottom margin. A single line is automatically skipped before the footer is printed. The footer can contain embedded carriage returns. The footer can also contain the symbol %d that prints page numbers. The number of lines per page. The default is 66 lines. The number of lines that are reserved for the top margin. The number of lines that are reserved for the bottom margin. Restrict the output to full pages only.
s <cmd>
h <header>
f <footer>
p <page_length> t <top_margin> b <bottom_margin>
Any combination of parameters is allowed.

768
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Example
In this example, the sld utility directs incoming events/alarms subscribed to by the DRI_Alarms subscription list through the ces utility and via dpr to the default laser printer. sld DRI_Alarms | ces | dpr i lp s lp onobanner h DRI Alarms f %d r The initial interface command (i lp) begins printing. The subsequent interface command (s lp onobanner) sets the banner page of subsequent files off. The page will be printed with a header on each page reading DRI Alarms (h DRI Alarms) and a footer giving the page number (f %d). The r option restricts the printouts to full pages only, which is suited to laser printers. The ces utility is described in the ces section in this chapter, while the sld utility is described in the sld section in this chapter.
EMOTOROLA LTD. 2000
769
ISSUE 18 REVISION 0
Introduction to cron
A file cron allows commands to be executed automatically by scheduling their execution at a certain time and date, or on a regular time period. An example is shown as follows:
Example
To scan an event log for MTL, RSL, DRIS and OML alarms and save in four ASCII text files for later analysis.
cel cel cel cel ev19930212* ev19930212* ev19930212* ev19930212* | | | | qfes qfes qfes qfes MTL | ces > mtl.txt RSL | ces > rsl.txt DRIS RCU | ces > dris.txt linkFailureEvent | ces > mtl.txt
These commands could be put in a script file and submitted to cron. This script file needs to source the OMC environment.
Crontab file
A crontab file consists of lines of six fields each. These fields are separated by spaces or tabs. The first five are integer patterns that specify the following:
minute (0 -59) hour (0 -23) day of the month (1 -31) month of the year (1 -12) day of the week ( 0 -6 with 0 = Sunday)
Each of the patterns may either be an asterisk (meaning all legal values) or a list of elements separated by commas. An element is either a number, or two numbers separated by a minus sign (meaning an inclusive range).
Setting up a cron job

Information on cron is supplied in Chapter 2 of the manual Operating Information: OMC System Administration (GSM-100-202).
770
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
OMC alarm paging
OMC alarm paging

Overview of paging
The OMC alarm paging feature automatically notifies on-call personnel of certain alarms or state changes which have been reported to the OMC. Alarm paging requires a modem at the OMC and a TAP/IXO alphanumeric pager to receive the paging details. The omcadmin user can start and stop the paging function using the pager command line utility. When alarm paging has been set up and started, the OMC creates an sld process which continually checks incoming events to see if any match the subscriptions specified in the paging subscription list. When a match is found, the OMC reduces the size of the alarm details so that they fit into a page (usually 80 characters long). The OMC then looks in the pager.config to find the telephone number and PIN number of the pager to be contacted. The OMC then connects with the modem, dials the number, and logs in to a paging terminal. The alphanumeric message is then transmitted through the paging terminal to the alphanumeric pager of the on-call OMC operator. All pages are logged in the file: /usr/gsm/logs/PagingLog
Contents of a page message

A page message contains the following alarm or event details: S S S S S S Device id. includes the site number and device number where the alarm occurred. Error id. a unique five digit alarm error identifier. Severity a two digit truncated alarm severity type. Error Message up to 236 characters, but is dependent on the maximum page length of the pager model in use. State of alarm whether the alarm has been Handled (HA) or Cleared (CL). If the paging buffer is full, number of alarms dropped from the page.
Each transmitted page contains details of one alarm/state change.
Truncated severity types

Due to the constraints in the number of characters which can be displayed on an alphanumeric pager (in some cases, only 80 characters) the character strings representing the error message, are truncated. The Alarm severity is resolved as follows: Alarm Severity Critical Major Minor Investigate Warning Unhandled
EMOTOROLA LTD. 2000
Is resolved to... Cr Ma Mi In Wa Un
771
OMC alarm paging
ISSUE 18 REVISION 0
Paging performance
Sending a page through any paging system always incurs a delay, whether the paging transmission is automatic or manual. The delay incurred is because the following processes are involved: S S S S S S S Dialling into the service. Connecting with the service. Logging into the service. Acknowledgement of PIN. Transmission of page. Confirmation of transmission. Disconnect.
This type of delay limits the number of pages which can be transmitted in a given time frame. The OMC transmits one page per minute. In the event of subscribed alarms which occur within a very short space of each other, the OMC will buffer at least 10 alarms and subsequently issue the pages which contain the important details of the alarms.
Paging: how it works

Once alarms in the Paging list occur, the modem is initialized and the alarms are sent out to the pager which is specified by the PIN number and the Pager Service Provider number. In the case where Paging Service Providers do not use PIN numbers, or only support numeric pagers, different parameters in the configuration file must be specified. The Paging Service Provider must comply with the TAP/IXO protocol. An event subscription list exists called PAGING. This subscription list is one of the entries displayed when the Event Management icon of the GUI is clicked. omcadmin users have permission to subscribe events and alarms to this window. This subscription list contains the set of alarms and state changes which trigger the pager to be contacted and the alarms sent to it. An empty PAGING subscription list is set up by default and the OMC administrator can then add the necessary alarms which are to generate pages.
Content of the paging configuration file

The paging configuration file, which is used for setting the parameters used by the pager, can be found in /usr/gsm/config/local/pager.config and is constructed as follows: set TelephoneNum set PIN set SubscriptionListName PAGING set LocalAccess 9 set PageLength 80 set ECDC 1 set Timer 20 The values above are the default settings supplied in the pager.config file. A description of each parameter follows:
772
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
OMC alarm paging
set TelephoneNum
This is the telephone number of the paging service providers automatic answering paging terminal.
set PIN
This is the Personal Identification Number which the person carrying the pager requires in order to log into the paging service. Some paging services do not use PIN numbers, but have some form of identification number which is required to log into the paging service. This identification number can be used instead of the PIN number and is set by filling out the set PIN line of the configuration file.
set SubscriptionListName
The subscription list which is used to drive the pager, is specified by completing the set SubscriptionListName line of the pager.config file. The default subscription list which is used is the PAGING subscription list. You are advised to use this list and to subscribe the necessary alarms to this list.
set LocalAccess
The set LocalAccess line allows the user to specify what number is required to dial out of a building which contains a PABX switch, in the default case it is 9.
set PageLength
The set PageLength line allows the user to specify the number of characters which the pager is capable of receiving.
set ECDC
The set ECDC line sets up the modem to switch on or off Error Correction and Data Compression. The OMC modem settings must match the modem settings of the paging service. If the paging service does not use Error Correction and Data Compression, then set ECDC 0 must be specified in pager.config . If the paging service does use Error Correction and Data Compression, then set ECDC 1 must be specified in pager.config .
set Timer
The set Timer line in pager.config is used to specify the length of time the modem is to hold the line before releasing it, in cases where the modem is unable to connect with the paging service.
Paging error handling

The following conditions generate errors which are logged in /usr/gsm/logs/PagingLog: S S S S S
EMOTOROLA LTD. 2000
Invalid field in the pager initialization file. Unable to connect to serial port. Modem Error Conditions. Unable to spawn sld process. Unable to log into paging service.
773
OMC alarm paging
ISSUE 18 REVISION 0
Installing the paging modem at the OMC

Prerequisites
The following equipment is needed for alarm paging: S S S A Motorola Codex 3265FAST modem. Check that the modem can connect to pagers via the Paging Service Providers. An appropriate telephone cable. This should be supplied with the modem. A standard 25-pin straight-through serial cable which can be used with a SUN SPARC machine. This should also be provided with the modem.
Installing the modem for alarm paging

To install a modem at the OMC for alarm paging, follow these steps: 1. 2. Connect one end of the serial cable to the DTE port on the back of the modem and the other end to the serial port marked A/B on the back of the SUN SPARC. Connect one end of the telephone cable to the Dial Line port on the back of the modem and the other end to the telephone line outlet connector.
Reinitializing the alarm paging modem

Once installed, the modem should be reinitialized to delete any stored telephone phone numbers and reset to factory defaults. To do this follow these steps: 1. Press the following button on the front panel of the modem twice:
2.
Press the following button on the front panel until the modem displays Reinit Memory:
3.
Press the following button once:
The modem displays:

Reinit all Mem?
4.
Press the following key to reinitialize the modem memory:
774
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
OMC alarm paging
Defining the contents of the pager configuration file

To define the contents of the pager configuration file, follow these steps: 1. omcadmin 2. 3. 4. 5. Log in as an omcadmin user. If it does not already exist, create the subscription list you want the paging function to use. See Managing subscription lists for further details. Use a text editor, such as vi, to edit the file /usr/gsm/config/local/pager.config Specify the specific requirements for each parameter in the pager.config. Save the file.
Starting paging
To start the alarm paging process, follow these steps: 1. omcadmin 2. Log in as the omcadmin user. In the command line, type: pager start At initialization a test page is transmitted to ensure that the modem and service are working correctly, and the OMC displays the following message:
A test message id being transmitted, please wait
If the test is successful, the OMC displays the following message:

The message has been successfully transmitted. Please make sure the pager is switched on in order to receive page.
If the test is unsuccessful, the OMC displays an appropriate error message. This command starts the script: /usr/gsm/current/sbin/pager
Stopping paging
To stop the alarm paging process, follow these steps: 1. 2. Log in as the omcadmin user. In the command line, type: pager stop This command stops the script: /usr/gsm/current/sbin/pager
EMOTOROLA LTD. 2000
775
Sending alarms to an e-mail address
ISSUE 18 REVISION 0
Sending alarms to an e-mail address

Description of e-mailing alarms
A highlighted alarm or alarms appearing in an Alarm window can be sent to a predefined e-mail address using a menu option in the Tools menu.
Prerequisite: a Tools menu

A Tools menu must have been created before a menu option can be added to it. See Creating a Tools menu in the Alarm and Event windows for further details.
Creating an e-mail alarm option in the Tools menu

To create an e-mail alarm option in the Tools menu, follow these steps: 1. omcadmin 2. Log in as the omcadmin user. Create a file with a meaningful name in the directory: /usr/gsm/config/global/menus/motorola/subscription/tools The name of the file appears as a menu option in the Tools menu. For example, to create a menu option called Mail Alarm, create a file called Mail_Alarm.sh. 3. If you do not want to strip out the <BeginEvent> and <EndEvent> delimiters from the alarm, enter the following command in the file: #! /bin/sh mail <username> < $1 where, <username> is the e-mail address of the user or an OMC login username (for example, omcadmin). $1 e-mails the selected alarm or alarms. If you want to strip out the <BeginEvent> and <EndEvent> delimiters from the alarm, enter the following command in the file: #! /bin/sh cat $1 | ces >/tmp/al_mail mail <username> < $1 rm /tmp/al_mail 4. Save the file in the Tools menu directory: /usr/gsm/config/global/menus/motorola/subscription/tools
When the GUI is restarted, the option appears in the Tools menu. NOTE If the menu option is to be used by all users, ensure that the file has write permissions for all users.
776
EMOTOROLA LTD. 2000
Chapter 8
Device Management
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
ii
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Chapter 8 Device Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Device management from the map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Locking a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unlocking a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INS a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resetting a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contained Devices window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resetting an NE from the command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC/RXCDR reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finding a Network Element, Site or Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Find feature overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Locating an NE, Site or Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Locating the parent of a Site or Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Examples of using find . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of the Call Trace function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to call trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call trace statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description of the Call Trace windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trace View window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Trace Detailed View window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Invoked Instances window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Abort Trace on Call window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trace Record View window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Call Trace function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a call trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing a call trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing call trace details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing trace records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Aborting a trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deactivating an active trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Tools menu in the Trace View window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of a Tools menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Tools menu in the Trace View window . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an option in the Trace View Tools menu . . . . . . . . . . . . . . . . . . . . . . . . . EAS alarm objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to Remote login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Three interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple Rlogin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging in remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2000
i
81 81 81 81 82 82 84 86 86 87 87 88 88 89 810 810 812 815 815 815 816 816 818 820 820 821 822 822 822 822 823 825 825 826 827 827 827 827 828 828 828 829 829 829 829 830
iii
ISSUE 18 REVISION 0
Using TTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Beginning a TTY session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing security levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security level 1 activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security level 2 activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Change level procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminating a TTY session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Batch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Batch access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Beginning a BATCH session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ending a BATCH session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating command files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using batch from the command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The batch_rlogin utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Associated environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Associated parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Batch login exit codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exit codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A batch_rlogin example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BatchInput file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BatchOutput file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forms session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Worksheet cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying circuit status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying channel status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling Forms logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling Forms logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exiting a Forms session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
831 831 831 831 832 833 834 835 835 836 836 836 837 837 838 839 839 839 841 841 841 841 841 842 842 842 844 844 844 844 845 846 846 846 846 848 849 849 849
iv
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Device management from the map

Introduction
The device management feature supports fault management and configuration management activities at the OMC. The OMC supports most hardware devices and software functions located at the remote network element. The operator can lock, unlock, INS and reset SITE devices from the Map. NOTE The Detailed View facility is not available for the PCU device or any of its contained devices at this release. The detailed view is available for the SGSN device.
Locking a device
To lock a specified SITE device (a lock cannot be performed on SITE 0) from the map use the following procedure: 1. 2. 3. 4. Select the Maps icon on the Front Panel to open a Map List window. From the Map list, double click the network map on which the required device is located. Select the required Network Element. The selected NE icon changes colour. Select Fault Management Lock from the menu bar. A confirmation box is displayed with the following message:
Do you wish to lock site <site name>?
5.
Click OK. A lock command is sent to the device. On receipt of a lock message from the OMC, the BSS attempts to lock the specified device and informs the OMC of the success or failure of the operation.
Open the Detailed View form to check whether the Site has changed state. When the operational state of the device has been changed, the BSS informs the OMC of the success of the lock operation via the existing state change mechanism. NOTE The Detailed View facility is not available for the PCU device or any of its contained devices at this release. The detailed view is available for the SGSN device.
Unlocking a device
To unlock a specified SITE device from the Network map, use the following procedure: 1. 2. Select the Maps icon on the Front Panel to open a Map List window. From the Map list, double click the network map on which the required device is located.
EMOTOROLA LTD. 2000
81
ISSUE 18 REVISION 0
3. 4.
Select the required Network Element. The selected NE icon changes colour. Select Fault Management Unlock from the menu bar. A confirmation box is displayed with the following message:
Do you wish to unlock site <site name>?
5.
Click OK. An unlock command is sent to the BSS. On receipt of an unlock message from the OMC, the BSS attempts to unlock the specified device and informs the OMC of the success or failure of the operation.
INS a device
To bring a specified SITE device into service (INS) from the Network map, carry out the following procedure: 1. 2. 3. 4. 5. 6. 7. Select the Maps icon on the Front Panel to open a Map List window. From the Map list, double click the network map on which the required device is located. Select the required Network Element. The colour of the selected NE icon changes, default is purple. Select Fault Management INS from the menu bar. A confirmation box is displayed with the following message:
Do you wish to INS site <site name>?
Click OK. Close the window by selecting File Close.
Resetting a device
To reset a specified SITE device from the Network map, carry out the following procedure: 1.
82
Select the Maps icon on the Front Panel to open a Map List window. NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
2. 3. 4. 5.
From the Map list, double click the network map on which the required device is located. Select the required Network Element. The colour of the selected NE icon changes, default is purple. Select Fault Management Reset from the menu bar. A confirmation box is displayed with the following message:
Do you wish to Reset site <site name>?
6. 7.
Click OK. Close the window by selecting File Close.
EMOTOROLA LTD. 2000
83
ISSUE 18 REVISION 0
Contained Devices window

All hardware devices, software functions and links (except for Circuit Identity Code (CIC) circuits) contained in the CM MIB can be displayed in the Contained Devices window (Figure 8-1). Refer to Online Help for a description of the columns in the Contained Devices window. All devices in a specified NE can be displayed in the Contained Devices window by selecting View All Devices from the menu bar. All GPRS devices, software functions and links are fully supported by the Contained Devices window facilities.
Figure 8-1 Contained Devices window
Filtering devices
The operator can also exclude or include specific devices in the Contained Devices window. A filter can be applied on the basis of device, operator, or state; use the following procedure: 1. 2. 3. In a Contained Devices window select View Filter On, the Filter Dialog window opens. Refer to Figure 8-2. Select the required filter criteria. Click on the Apply button, the Contained Devices window changes to reflect the filter criteria selected. Click on the Save As Default button to save the filter criteria as the default for the Contained Devices window. The following message is displayed in the status bar:
Filter has been saved as default. This filter will be applied whenever you open the Contained Devices window.
When the Remove Default button is clicked, the following message is displayed in the status bar (but only if a default filter had been selected previously) :
The default filter has been removed. No filter will be applied when you open a Contained Devices window.
84
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
4.
Click on the Close button to close window.
Figure 8-2 Contained Devices: Filter Dialog window
EMOTOROLA LTD. 2000
85
Resetting an NE from the command line
ISSUE 18 REVISION 0

If problems occur in the network, the NE or devices may require resetting. A simpler facility exists for resetting devices from the network map, but is only valid for certain device types. Use the following procedures to reset devices not available from the map. See Using the map: overview in Chapter 2 for procedures using the Network Map. Online Help contains details of the types of devices which may not be accessed from the map. See Device management from the map at the beginning of this chapter for procedures on resetting certain devices from the Network map.
BSC/RXCDR reset
NOTE omcadmin Resetting the RXCDR will break the Operations and Maintenance Link (OML), Message Transfer Link (MTL), and voice channels for all associated BSC for the period of the reset (approx. five minutes). To reset a BSC or Remote Transcoder (RXCDR) from any SPARCstation, proceed as follows: 1. 2. 3. 4. Select the Remote Login icon on the Front Panel to display the list of Network nodes. Click on the node to be reset. Click the TTY button to open the TTY interface to the NE. Change level to level 2 by typing the following MMI command:
chg_1
The BSS will then respond with:
Enter password for security level you wish to access
Type in the password, if correct the BSS will respond with:

Current security level is 2
5.
Enter the following command: reset_site The BSS responds with a message
WARNING: Command will reboot site 0 Are you sure (y=yes, n=no) ?
6.
Answer y to this question. The BSS then responds with:

site reboots now!
The MTL and OML links drop out shortly afterwards. 7. 8.

86
Observe sites coming back on line using the Event window for this BSC. Carry out an Audit of the BSS as detailed in Chapter 6. NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
BTS reset
To reset a BTS, proceed as follows: omcadmin 1. 2. 3. 4. Select the Remote Login icon on the Front Panel to display the list of Network nodes. Click on the node to be reset. Click the TTY button to open the TTY interface to the NE. Change level to level 2 by typing the following MMI commands: chg_l The BSS will then respond with:

5.
Reset the BTS as follows: reset_site x Where: x is: BTS site number
Device reset
To reset a device, proceed as follows: omcadmin 1. 2. 3. 4. Select the Remote Login icon on the Front Panel to display the list of Network nodes. Click on the node to be reset. Click the TTY button to open the TTY interface to the NE. Change level to level 2 by typing the following MMI commands: chg_l The BSS will then respond with:

5.
Reset the device as follows: reset_device n <DEVICE_NAME> x y 0 Where: n is: location number of the site with the faulty device (n=0 at BSC or RXCDR). unique identity for the device. is the first device identifier. is the second device identifier.
<DEVICE_NAME> x y
For further information on <DEVICE_NAME>, refer to Technical Description: BSS Command Reference, (GSM-100-321).
EMOTOROLA LTD. 2000
87
Finding a Network Element, Site or Cell
ISSUE 18 REVISION 0

Find feature overview
The Find feature is used to find NEs, Sites or Cells. Click on the Find icon on the OMC Front Panel to open the Find window. The following information can be entered to find an NE, Site or Cell: S S S S S S S S S S S S S NE Name. Site Name. Site Id. Cell Name. GSM Cell Id.
This section also contains examples of using the find feature: Finding a Site using BSS name and Site Id. Finding the BSS parent of a Cell. Finding a Cell with a LAC.
Then when the NE, Site or Cell has been found the operator can: Open the Navigation Tree with the node as its root. Open a Detailed View for a node. Perform a TTY Rlogin to a BSS. Open a Contained Devices window for a node. Open a Map for a BSS.
88
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Figure 8-3 Find window
Locating an NE, Site or Cell

To locate an NE, Site, or Cell carry out the following procedure: 1. 2. Select the Find button from the OMC Front Panel, the Find window opens (Figure 8-3). Enter the name of the NE, Site, or Cell in the relevant Name field. An Id can be entered for a Site or Cell in the relevant Id field. Click on the Clear button to remove the text from all the fields. NOTE The search performs an exact match on Site Id or Cell Id and a partial match in all other fields. For example, Site Id: 1 is matched with site 1 but not site 10. The text string SS1 is matched with BSS1 and BSS10. The search is not case sensitive.
EMOTOROLA LTD. 2000
89
ISSUE 18 REVISION 0
3.
Click on the Find NE(s), Find Site(s), or Find Cell(s) button. Find NE(s) will display the network elements that match the criteria in all fields. If a Cell name is entered it will find the NE containing the Cell. Find SITE(s) will display the Sites that match the criteria in all fields. Find CELL(s) will display the Cells that match the criteria in all fields. NOTE If no text has been entered the search will display all NEs, Sites, or Cells in the network.
The result of a search is displayed in the Find Results box of the window. The heading indicates the class of objects found, that is, Network Elements, Site Name/Site Id, or Cells. NOTE If no match is found, an information box is displayed with the following message: No matching <object> was found. Where <object> is the Network Element, Site or Cell.
Locating the parent of a Site or Cell

The parent of a Cell or Site can be found using the following procedure: 1. 2. 3. Follow steps 1 to 3 of the procedure Locating an NE, Site or Cell. In the Find Results area of the Find window select the required Site or Cell. Click on the Find Parent button, the parent of the selected Site or Cell is displayed in the Find Results box.
Additional operations
When an NE, Site, or Cell has been located additional operations can be performed from the Find window, such as opening a Navigation Tree, Detailed View, Contained Devices window, or Map; or performing a Remote Login.
Navigation Tree
A Navigation Tree can be opened from the Find window using the following procedure: 1. 2. Select an NE, Site, or Cell in the Find Results box. In the Open section of the Find window click on the Navigation Tree button. A Navigation Tree opens with the selected NE, Site, or Cell at its root. NOTE Alternatively, double click on an NE, Site, or Cell in the Find Results box to open a Navigation Tree.
810
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Detailed View
A Detailed View can be opened from the Find window using the following procedure: 1. 2. Select an NE, Site, or Cell in the Find Results box. In the Open section of the Find window click on the Detailed View button. A Detailed View for the selected node opens.
RLogin
An Rlogin session can be started from the Find window using the following procedure: 1. 2. Select an NE, Site, or Cell in the Find Results box. In the Open section of the Find window click on the RLogin button. An Xterm opens from where a TTY remote login operation to the parent BSS can be performed.
Contained Devices
A Contained Devices window can be opened from the Find window using the following procedure: 1. 2. Select an NE or Site in the Find Results box. In the Open section of the Find window click on the Contained Devices button. A Contained Devices window opens for the selected NE or Site.
Map
A Map can be opened from the Find window using the following procedure: 1. 2. Select an NE in the Find Results box. In the Open section of the Find window click on the Map button. A Map opens for the selected NE.
EMOTOROLA LTD. 2000
811
ISSUE 18 REVISION 0
Examples of using find

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

To find a Site at a BSS by specifying the BSS name and the Site Id use the following procedure: 1. 2. 3. Select the Find button from the OMC Front Panel, the Find window opens. Enter the BSS name in the BSS Name field, then enter the Site Id in the Site Id field. Click on the Find Site(s) button, the result of the search is displayed in the Find Results box (Figure 8-4).
Figure 8-4 Find window with BSS name and Site id
812
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Finding the BSS parent of a Cell

To find the BSS parent of a Cell use the following procedure: 1. 2. 3. 4. 5. 6. Select the Find button from the OMC Front Panel, the Find window opens. Enter the name of the Cell in the Cell Name field, or its Id in the GSM Cell Id field. Click on the Find Cell(s) button, the result of the search is displayed in the Find Results box. Select the Cell in the Find Results box. Click on the Find Parent button, the parent Site of the Cell is displayed in the Find Results box. Select the Site and then click on the Find Parent button again, the parent BSS of the Cell is displayed in the Find Results box.
EMOTOROLA LTD. 2000
813
ISSUE 18 REVISION 0
Finding a Cell with a LAC

Cells with a particular Location Area Code (LAC) can be searched for, using the following procedure: 1. 2. 3. Select the Find button from the OMC Front Panel, the Find window opens. Enter the LAC in the third field of the GSM Cell Id. Click on the Find Cell(s) button, all Cell(s) with the specified LAC are displayed in the Find Results box (Figure 8-5). NOTE Additional information about GSM cell ids can be found in Technical Description: BSS Command Reference GSM-100-321 and Installation & Configuration: GSM System Configuration GSM-100-403.
Figure 8-5 Find window with Cell LAC
814
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Overview of the Call Trace function
Overview of the Call Trace function

Introduction to call trace
The call trace function enables an operator to trace the activities of various network elements (BSS, SITE, CELL, RTF) for events associated with a particular subscriber or equipment, or selected cells. An operator at an OMC, MSC or BSS can create a trace. Each trace has certain criteria associated with it, which the operator is required to specify to create a trace. For example, which calls are to be added to the trace log. From the OMC an operator can: S Create a trace. NOTE An operator can only create a call trace if the Call Trace function has been enabled in the User Profile List. S S S S Delete a trace from the OMC. View the trace criteria for active, deactivated, and completed traces. View the trace records associated with each trace. Perform other actions such as terminating a trace on a particular cell, or preventing an active trace from triggering any more new invoked instances by permanently deactivating the trace. NOTE Only one trace can be active on a specific call at any instant. The user should delete and recreate trace criteria if LCFs are added or reset. Care should be taken when creating traces to prevent the OML becoming flooded. Call trace expansion is detailed in Installation and Configuration: GSM System Configuration (GSM-100-403).
Call trace statuses

A Trace can have one of the following statuses: S S Active can still invoke new instances. Deactivated means either: Has been deactivated by the operator at the BSS or OMC. Has been deactivated internally by the BSS. The current time is outside the triggering period for the trace. NOTE Active and deactivated traces have call trace managed objects in the MIB (and at the BSS). S Completed a terminated trace. Managed objects for it does not exist at the BSS. They are included so that the operator has access to the trace record for completed traces.
EMOTOROLA LTD. 2000
815
Description of the Call Trace windows
ISSUE 18 REVISION 0

Trace View window
Displaying the Trace View window
To display the Trace View window, select the network element required from the Navigation tree, then select Options Call Trace View Traces from the menu bar. NOTE Alternatively, the Trace View window can be invoked from an NE detailed view by selecting Options Call Trace View Traces from the menu bar.
Contents of the Trace View window

The Trace View window (see Figure 8-6) displays basic details for all the call traces for a specific network element. The operator can select one trace on which to perform other activities. The Trace View window contains the following information for each trace: S S S S Name The name assigned by the operator for the trace. Trace Origin Indicates whether the trace has been activated from the MSC, OMC or MMI. Record Destination Indicates the destination for the trace data; OMC, MMI or both. Selector The type of trace selector; for example, IMSI, TMSI, IMEI, IMEISV, SCCP Number or nth call. S Selector Value The value for the particular selector type chosen; for example, IMSI number for IMSI. S S S S S Status The status of the trace; Active, Deactivated or Completed. Active calls The quantity of active calls. Completed calls The quantity of completed calls. Creation Time The date and time when the trace was first created. Scope The scope of the trace (BSS, SITE, CELL or RTF).
816
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Sorting traces
By default all traces are sorted by status, but the operator can sort traces by: S S S Trace Origin Status Creation date and time
Tasks available from the Trace View window

The following tasks are available from the Trace View window menu bar: S S S S S S View the trace records of one invoked instance of the selected trace. Display the Call Trace Detailed View window to view the details of the trace criteria for the selected trace. Deactivate the selected active trace. Delete the selected active, deactivated, or completed trace. Display the Abort Trace window to abort a trace on a particular call, for the selected active trace. Display the BSS Detailed View to view call trace related attributes of the BSS which contains the selected trace criteria.
Figure 8-6 Trace View window
EMOTOROLA LTD. 2000
817
ISSUE 18 REVISION 0
Call Trace Detailed View window

Displaying the Call Trace Detailed View window
The Call Trace Detailed View window can be displayed using one of the following methods: S S S Select a trace from the Trace View window and select the appropriate menu option. From the Trace Record View window and select the appropriate menu option. From the Trace View window by selecting the appropriate menu option. In this case, the scope of the trace is not populated.
The scope (BSS, SITE, CELL or RTF) of the trace is carried through to the Call Trace Detailed View window.
818
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Contents of the Call Trace Detailed View window

If the Call Trace Detailed View window is displayed for an existing trace, the window displays details of the call trace criteria. If the Call Trace Detailed View window is displayed for a new trace, the operator can enter a value for each of the attributes of the trace criteria. The trace criteria is a follows: S S Trace Name The name of the call trace. This field is optional. Trace Selector Determines which calls are added to the trace log. The operator can select the following: Nth Call Every nth call is traced. The operator can enter a value. The default is 1. IMSI The operator can enter the IMSI Number to be traced. IMEI The operator can enter the IMEI Number to be traced. IMEISV The operator can enter the IMEISV Number to be traced. TMSI The operator can enter the TMSI Number to be traced. SCCP# The operator can enter the SCCP# Number to be traced. S Trace Details Defines the event that triggers the trace, the maximum number of calls to be traced, and the start and end time of the trace. NOTE Maximum number of simultaneous calls can only be greater than 1, if Nth Call is selected in the Trace Selector field. S Record Details Defines the type of details logged in the call trace record. The default record type is set to Basic. The operator can change this to either Radio or Handover.
EMOTOROLA LTD. 2000
819
ISSUE 18 REVISION 0
Tasks available from the Call Trace Detailed View window

The Call Trace Detailed View window contains menu options which enable the operator to perform functions on a particular trace. The functions which can be performed include: S S S Activate a trace using the File Create menu option. Deactivate a trace. This is only available for active traces. Abort a trace on a call. Selecting this option displays the Abort Trace on Call window if there are still calls in progress for the trace criteria. This is only available for active and deactivated traces. View all calls, calls in progress, or completed calls for the trace criteria. Selecting this option displays the Invoked Instances window. NOTE The all calls, or calls in progress options are not applicable for completed trace criteria.
Invoked Instances window

This window is displayed by selecting any of the following options from the Trace View window: S S S View, All Calls. View, Calls in Progress. View, Completed Calls.
The title bar of this window displays the name of the BSS for the trace criteria, along with the trace criteria reference number and the option selected (All calls, Calls in Progress or Completed Calls). If the Invoked Instances window has been displayed to view trace records for a call, the the window displays a list of the SCCP numbers of currently invoked instances (sorted by invocation time) followed by a list of the completed instances (again sorted by invocation time) of the selected trace criteria. The status of each instance (Active or Completed) is displayed along with the date and time that the first trace record was received at the OMC. If the Invoked Instances window has been displayed to view trace records for a completed trace, the window displays a list of the SCCP numbers of all traces which were invoked during the lifetime of the selected trace.
Abort Trace on Call window

This window is displayed by selecting the Options, Abort Trace on Call menu option from the Trace View window. It enables the operator to select one or more calls in order to abort the active traces on those calls. The title bar of this window displays the name of the BSS for the trace criteria, along with the trace criteria reference number. The window will display a list of the calls currently in progress for the selected trace criteria. The date and time that the first trace record was received at the OMC is displayed. The first call in the list is selected by default.
820
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Trace Record View window

The Trace Record View window displays the trace records for an invoked instance, in chronological order. The display includes both the header and the body of the trace records. The display is dynamically updated to append the most recent trace records received by the OMC for a particular invoked instance. The Trace Record View window contains menu options which enable the operator to perform functions on a particular invoked instance. The functions which can be performed include: S S S S S Terminate an invoked instance. Display the Trace Criteria window to view the trace criteria associated with an invoked instance. Save the contents of the Trace Record View window to an ASCII file. Print the trace record. Enable the integration of external call trace data processing tools. When selected, this option displays a list of available tools.
EMOTOROLA LTD. 2000
821
Using the Call Trace function
ISSUE 18 REVISION 0

Creating a call trace
To create a call trace follow these steps: 1. 2. 3. 4. 5. Select the Config Mgmt icon on the Front Panel. The OMC displays the Navigation tree. In the Navigation tree, select a network element for the call trace. Select Options Call Trace Create Trace from the menu bar. The OMC displays the Call Trace Detailed View window. Enter the appropriate values in the Call Trace Detailed View window fields. Select File Create from the menu bar to activate the trace.
Viewing a call trace

To view an existing call trace follow these steps: 1. 2. 3. Select the Config Mgmt icon on the Front Panel. The OMC displays the Navigation tree. Select the required network element (BSS, SITE, CELL, RTF). Select Options Call Trace View Traces from the menu bar, the Trace View window opens. Refer to Figure 8-6. NOTE Alternatively, view call trace details from an NE detailed view by selecting Options Call Trace View Traces from the menu bar.
Viewing call trace details

To view call trace criteria for an existing trace, follow these steps: 1. 2. 3. 4. Select the Config Mgmt icon on the Front Panel, the Navigation tree is displayed. Select the required network element (BSS, SITE, CELL, RTF). Select Options Call Trace View Traces from the menu bar, the Trace View window opens. Select a trace and then select Edit Detailed View from the menu bar. The OMC displays the Call Trace Detailed View window. The detailed view window displays the criteria that the operator specified when the trace was set up.
Editing call trace details

Only the Trace Name field and Additional Information field can be modified, all other fields are read-only.
822
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Viewing trace records

To view trace records for a call, follow these steps: 1. 2. 3. 4. 5. 6. Select the Config Mgmt icon on the Front Panel, the Navigation Tree is displayed. Select the required element (BSS, SITE, CELL, RTF). Select Options Call Trace View Traces from the menu bar, the Trace View window opens. Select a trace. Select Display Calls, then select either All Calls, Calls in Progress, or Completed Calls, the Invoked Instances List window opens (Figure 8-7). Select a call from the list and select View Records, the Trace Record View window opens. The Trace Record View window (Figure 8-8) displays trace records for the selected call.
Figure 8-7 Invoked Instances List window
EMOTOROLA LTD. 2000
823
ISSUE 18 REVISION 0
Figure 8-8 Trace Record View window
824
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Aborting a trace
A trace can be aborted for an active cell. When a trace is aborted, the trace is terminated on an individual call or calls. To abort a call trace, follow these steps: 1. 2. 3. 4. 5. 6. Select the Config Mgmt icon on the Front Panel, the Navigation tree is displayed. Select the required network element (BSS, SITE, CELL, RTF). Select Options Call Trace View Traces from the menu bar, the Trace View window opens. Select a trace. Select Display Calls Calls in Progress, the Invoked Instances List window opens. Select a call or calls, then select Options Abort Trace. The call or calls are aborted. The OMC displays an abort confirmation message detailing the name of the origin and the SCCP numbers of the call(s) selected. 7. Click OK to confirm the abort.
Deactivating an active trace

An active trace can be deactivated. When an active trace is deactivated, any current calls are traced but no further calls matching the trace criteria are traced. When the existing calls are complete, the OMC deletes the trace. This is referred to as a graceful delete. NOTE Once a trace is deactivated it cannot be reactivated. To deactivate an active trace, follow these steps: 1. 2. 3. 4. 5. 6. Select the Config Mgmt icon on the Front Panel. This displays the Navigation tree. Select the required network element (BSS, SITE, CELL, RTF). Select Options Call Trace View Traces from the menu bar, the Trace View window opens. Select an active trace. Select Options Deactivate Trace from the menu bar. The OMC displays a confirmation message detailing the origin of the trace, see Figure 8-9. Click OK to confirm the deactivation.
EMOTOROLA LTD. 2000
825
ISSUE 18 REVISION 0
Figure 8-9 Deactivate Trace confirmation box
Deleting a trace
The trace criteria associated with an active, deactivated, or completed trace can be deleted. This will terminate any active or deactivated traces. The data record associated with a completed trace can also be deleted. To delete criteria and/or data records for a trace from the Trace View window, follow these steps: 1. 2. 3. 4. 5. Select the Config Mgmt icon on the Front Panel, the Navigation Tree is displayed. Select the required network element (BSS, SITE, CELL, RTF). Select Options Call Trace View Traces from the menu bar. The OMC opens the Trace View window. Select a trace. Select Options Remove Criteria to terminate all active or deactivated traces. Or, Select Options Remove Record to delete the call trace record for a completed trace. Or, Select Options Remove Criteria & Record to terminate all active and deactivated traces, and delete the call trace record for a completed trace. The OMC displays a confirmation message detailing the name of the trace criteria origin. 6. Click OK to confirm the deletion. NOTE Traces can also be deleted from the Call Trace Detailed View window.
826
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Creating a Tools menu in the Trace View window

Purpose of a Tools menu
An omcadmin user can create a Tools menu which is available to an operator from the Trace View window. The omcadmin user can add useful functions to the Tools menu as menu options. The menu options can then be quickly and easily selected by an operator. For example, the option to access the CTP tool can be added to the Tools menu.

To create a Tools menu in the Trace View window, follow these steps: 1. omcadmin 2. Log in as the omcadmin user. Create the following directory: /usr/gsm/config/global/menus/motorola/common/CallTrace/Tools When the GUI is restarted, the Tools menu appears in the Trace View window. Now add a menu option to it.
Creating an option in the Trace View Tools menu

To create an option in the Tools menu in the Trace View window, follow these steps: 1. omcadmin 2. Log in as the omcadmin user. Create a file with a meaningful name in the directory: /usr/gsm/config/global/menus/motorola/common/CallTrace/Tools The name of the file will appear as a menu option in the Tools menu. For example, to create a menu option called CTP to initiate the Call Trace Product tool, create a file called CTP_Tool.sh. 3. In the file, type the UNIX command to be executed when the option is selected by an operator. For example, to follow the CTP Tool example above, type: #! /bin/sh xterm iconic e /usr/gsm/ne_data/CTP/CTP_gui.tcl 4. Save the file. When the GUI is restarted, the option appears in the Tools menu. NOTE If the menu option is to be used by all users, ensure that the file has write permissions for all users. In the example given above, when the user selects the CTP Tool menu option, the OMC creates an iconized window. When the operator opens the window it displays the CTP GUI. If the CTP GUI is not displayed, either the CTP tool is not installed or it has been installed in a different directory.
EMOTOROLA LTD. 2000
827
EAS alarm objects
ISSUE 18 REVISION 0
EAS alarm objects

Introduction
BSS and RXCDR devices contain External Alarm System (EAS) alarm objects. These objects represent the alarms that are generated by the BSS EAS devices. Each BSS or RXCDR contains thirty four of these objects. They are created at the OMC via an audit. The EAS Alarms form combines all of the EAS alarms in one list.
Procedure
1. 2. 3. 4. From the Front Panel, select the Config Mgmt icon to open the Navigation Tree. Select the required BSS or RXCDR from the Navigation Form. Select Config Mgt EAS Alarms from the menu bar. The EAS Alarms form is displayed, see Figure 8-10. Select an alarm, then select Edit Detailed View. The EAS alarm detailed view is displayed.
Figure 8-10 EAS Alarms form
828
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Remote login
Remote login
Introduction to Remote login
This chapter introduces the Remote Login (RLogin) facility which allows remote access to a Base Station System (BSS) or a Remote Transcoder (RXCDR) to configure BSS or RXCDR equipment from the OMC. To use the Remote Login function for TTY and Batch sessions, select the Remote Login icon from the Front Panel to display a RLogin window. Forms sessions can be accessed from the Navigation Tree, refer to the Using Forms procedure. It is also possible to Remote Login to a Network Element by locating the required element on a Network Map, and selecting Remote Login from the Option menu, see Chapter 2 for further details of Remote Login from a map.
Three interfaces
There are three interfaces to connect with the two types of Network Elements (NEs) from the OMC: S S TTY a TTY session is a remote login to the BSS or RXCDR, with the facility to issue commands directly at a command line interface level. Batch a Batch session is a remote login to the NE with the facility to combine a number of TTY commands in a command file by executing a single command at the command line. Forms a Forms session is a remote login to a subset of the BSS MMI commands. This interface allows real-time monitoring of certain BSS functions in a user friendly environment. However, not all of the BSS related activities can be performed with a Forms session, therefore TTY must be used.
All interfaces permit commands to be passed to the BSS/RXCDR. For further information on the TTY, Batch, and Forms interfaces, refer to Online Help.
Multiple Rlogin
Multiple Rlogin is possible for Network Elements equipped with more than one GPROC, a maximum of four Rlogin sessions are allowed per Network Element. The OMC supports up to 20 remote login sessions to different Network Elements at any given time.
EMOTOROLA LTD. 2000
829
Remote login
ISSUE 18 REVISION 0
Logging in remotely
To select Remote Login for TTY and Batch, perform the following procedure: 1. Click the Remote Login icon on the front panel. A Remote Login window opens, as shown in Figure 8-11.
Figure 8-11 RLogin window 2. 3. Click on the required Network Element. The selection is highlighted in inverse text. Select either TTY or Batch access methods by clicking the appropriate button in the RLogin window. Help is available by clicking the Help button. NOTE It is possible to rlogin to a NE during a NE database upload. In this case, a message is displayed from the Forms Interface stating that the rlogin has been successful, and that a database upload is in progress. It is not possible to upload a NE database while remotely logged in to a NE.
830
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Using TTY
Using TTY
Introduction
A TTY session uses a terminal window for a selected site that accepts command line interface MMI commands. When the TTY button is clicked in the RLogin window, a terminal window opens. This is a remote login session with the selected BSS or RXCDR, into which the appropriate BSS commands are entered.
Knowledge of BSS commands is required to use the TTY Remote Login method. Information can be found in the Technical Description: BSS Command Reference (GSM100321).
Beginning a TTY session

NOTE If an unsuccessful login message is received at any time, press CR to close the Rlogin window. A list of available commands can be obtained by typing help at the NE prompt. To begin a TTY session: 1. 2. 3. 4. Select Remote Login from the Front Panel. The RLogin window opens. From the RLogin window, select the site to work on. Click on the TTY button. The TTY session window for the selected site is displayed as shown in Figure 8-12. Press CR to obtain the NE prompt >. NOTE The actual prompt provided by the NE is equipment-dependent. Throughout this section the > prompt is used for convenience.
EMOTOROLA LTD. 2000
831
Using TTY
ISSUE 18 REVISION 0
Figure 8-12 Starting a TTY session
Changing security levels

There are three available security levels, security level 1, security level 2 and optional security level 3. Security level 1 allows the entry of commands to monitor the system. Security level 2 allows the entry of commands to monitor and administer the system. The chg_level command is used to change to the appropriate security level.
832
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Using TTY
Security level 1 activity

Security level 1 commands are mainly system monitoring commands. For example, state is a security level 1 command that displays the status of devices and functions. When a TTY session is first set up, security level 1 commands can be entered.
Example
In the following example, the security level 1 command, state is executed to display the status of a specific function (refer to Figure 8-13). 1. To display the status of the BTF function enter the command: state bsc btf 0 2. After the system response, additional security level 1 commands can be typed at the NE prompt.
> state bsc btf 0 STATUS INFORMATION: Function BTF 000 Administration state: equipped Operational state: busy Reason code is 0 Time of last transition: Fri Apr 8 09:43:31 1998 Related Device/Function: GPROC 3 0 0 DRI Ids assigned: DRI 0 0 0 END OF STATUS REPORT >
Figure 8-13 Security level 1 activity
EMOTOROLA LTD. 2000
833
Using TTY
ISSUE 18 REVISION 0
Security level 2 activity

Security level 2 commands include system monitoring and system administration commands. For example, equip is a security level 2 command. To execute MMI commands that monitor and administer the system, the user must be in security level 2.
Example
In the following example, equip is executed to equip a cabinet at a BSC (refer to Figure 8-14). 1. Enter the command: equip bsc cab The base responds with:
Enter the cabinet identifier Enter the cabinet type number:
2. 3.
At the prompt, enter the appropriate configuration information. After the system response, additional security level 2 commands can be typed at the NE prompt. NOTE A list of all available commands can be obtained by entering help at the NE prompt.
> equip bsc CAB Enter the CABINET identifier: 13 Enter the CABINET type number: 1 COMMAND ACCEPTED >
Figure 8-14 Security level 2 activity
834
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Using TTY
Change level procedure

The chg_level command toggles between security levels 1, 2 and 3. To change security levels (Figure 8-15), perform the following procedure. 1. Enter the command: chg_level The base responds with:
Enter password for security level you wish to access...
2.
At the prompt, enter the password for the required security level. (The password is not echoed back to the screen). If it is correct, the base responds with:
> chg_level Enter password for security level you wish to access:.. Current security level is 2 >
Figure 8-15 Change security level
Terminating a TTY session

When all activity for the session is completed, the session must be terminated. To terminate a TTY session: 1. Enter the command: !logout The base responds with:
Logout indication received. Press <RET> to close window
2. 3.
At the prompt, press CR. The TTY session window is closed. Click on the Close button in the RLogin window or initiate another TTY or Batch session.
> !logout OMC>Logout indication received OMC>Press <RET> to close window
Figure 8-16 Terminating a TTY session

EMOTOROLA LTD. 2000
835
Using Batch
ISSUE 18 REVISION 0
Using Batch
Batch access
A Batch session uses a UNIX shell window that enables the execution of one or more BSS MMI commands from a pre-edited command file. When the Remote Login icon is selected the RLogin window opens, which contains a list of all available NEs in the system. Once a site is selected this opens a remote login session with the selected BSS or RXCDR and enables a file selection dialogue which allows the selection, viewing, editing, deleting and running of batch files.
Beginning a BATCH session

To begin a Batch session from the OMC: 1. 2. 3. 4. Select Remote Login from the Front Panel. The RLogin window opens. From the RLogin window select the required site. Click on the Batch button. The Batch File Selection window for the selected site is displayed (Figure 8-17). The Batch File selection window allows a number of operations to be performed: Action Click on the Run button. Result Checks the existence of the batch file and, if valid, invoke the batch_rlogin script with the parameters that have been entered in the window. Creates a new file. This invokes the xedit editor for the unnamed file. Views or modifies an existing file. This invokes the xedit editor for the chosen file. Deletes a selected file or directory. Begins a search based on criteria given in the Filter and Selection fields. On completion, all files matching the criteria are displayed in the Files list and all directories are displayed in the Directories list.
Click on the View/Edit button with no text in the Selection field. Click on the View/Edit button with a file entry in the Selection field. Click on the Delete button. Click on the Filter button.
5.
To control how the Batch process operates, the two toggle buttons can be used: Button Result Continue/terminate the execution of Batch when a command contained in the batch file fails to execute. Logs the output of the batch commands during batch file execution.
EMOTOROLA LTD. 2000
The Continue Batch Execution on Error toggle button The Log Batch Output toggle button.
836
ISSUE 18 REVISION 0
Using Batch
Figure 8-17 Batch File Selection window
Ending a BATCH session

Batch Manager processing can be terminated with the CTRL-\ character on the SPARCstation keyboard.
Creating command files

To create a command file for the Batch Manager, use a text editor. Details of xedit are given in Chapter 1 of this manual. The command file may be interspersed with comments for information. A commented line must have a # character in column one and a space character in column two.
EMOTOROLA LTD. 2000
837
Using Batch
ISSUE 18 REVISION 0
Using batch from the command line

The Batch Manager is designed as a standard UNIX filter. The interface available is a UNIX shell. To run the batch manager: 1. Enter the following command: batch_rlogin [bssname] < [commandfilename] > [logfilename] to execute a command file at a remote NE. Where: < > [commandfilename] [logfilename] is: the UNIX syntax for redirection of stdout the UNIX syntax for redirection of a pre-edited BSS command file is a file to which all output (and input) will be logged
Example
An example of the command line is as follows: batch_rlogin bss12 < passwd.cmdfile > passwd.logfile
838
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
The batch_rlogin utility

Prerequisites
The batch_rlogin utility is run from a UNIX shell window. The path ($COMMS_ROOT/bin/batch_rlogin ) for the utility is set when the operator is added to the OMC by using .addOMCuser.
Formats
Two formats are supported as follows:
Format 1
batch_rlogin ne_name [<command_file>] [<log_file>] Parameters: Where: ne_name is: The name of the BSS/RXCDR to which the batch file is sent. The name of the file which contains the BSS MMI commands to be sent to the BSS (or RXCDR) when the batch_rlogin command is executed. See the Command file section for a further description of this file. The name of the file in which responses from the BSS are stored. See the Log file section for a further description of this file.
command_file
log_file
EMOTOROLA LTD. 2000
839
ISSUE 18 REVISION 0
Format 2
batch_rlogin ne_name exit/noexit xterm/noxterm [<command_file>] [<log_file>] Parameters: Where: ne_name is: The name of the BSS/RXCDR to which the batch file will be sent. Determines whether the batch job will stop (exit) or continue (noexit) execution if a command fails. Determines whether or not an Xterm window is displayed showing the output of the executing batch commands. The name of the file which contains the BSS MMI commands to be sent to the BSS (or RXCDR) when the batch_rlogin command is executed. See the Command file section for a further description of this file. The name of the file in which responses from the BSS are stored. See the Log file section for a further description of this file.
exit/noexit
xterm/noxterm
command_file
log_file
840
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Command file
The command file used with batch_rlogin can be created using any standard text editor. This file can be interspersed with comments to aid readability and understanding of the file. A commented line has a # character in the first column and a space in the second column. Any line in the command file preceded by these characters will be recognised as a comment line by batch_rlogin and will not be executed.
Log file
The log file is created when batch_rlogin is executed. All input (comments and BSS commands in the command file) and output received from the NE, are logged in this file. If a log file name is not specified the output is directed to the screen (format 1 only). Outputs to the log file are as follows: S Comments and BSS commands from the command file and their respective BSS responses. Command file input is prefixed by: BATCH CMD > in the log file. NE responses are prefixed by: NE RESPONSE >. Time of the start and end of the batch processing. Descriptive error message if an error occurred during batch processing. An exit code. The exit codes are described in the Batch login exit codes section in this chapter.
S S S
The log file may be viewed using any text editor.
Terminating
If the process is running in the foreground batch_rlogin may be terminated by pressing CTRL-\ or Delete on the terminal keyboard.
Associated environment variables

The following environment variables are associated with the Batch Manager:
BATCH_IPC_TIMEOUT
This environment variable specifies the time period within which a response is expected when establishing a connection with the NE. The default value is 600 seconds, and valid values are any values greater than 0 seconds.
BATCH_NERESP_TIMEOUT
This environment variable specifies the time period that the batch_rlogin utility awaits a command response from the NE. After this time, the next command in the batch file is forwarded to the NE for execution. The default value is10 seconds, and valid values are any values greater than 0 seconds.
Associated parameters
Parameters that are associated with batch_rlogin are stdin and stdout.
EMOTOROLA LTD. 2000
841
Batch login exit codes
ISSUE 18 REVISION 0

Introduction
The table in this section lists the exit codes and messages which may be written to the log file.
Exit codes
Table 8-1 lists possible exit code numbers and associated messages which may be written to the log file when executing batch_rlogin . Table 8-1 Log file exit codes and messages
Exit code number

0 11 12 13 14 15 21 22 23 24 25 26 27 31 32 33 34 35 36 37 38 39 40 41 42 43 44 SUCCESS. OMC shutdown in progress. Network Element in use.
Message
Maximum number of remote login sessions exceeded. Database upload to/from NE in progress. Open RLogin request failed. Software error at remote login. X.25 error at remote login. Remote login session terminated by remote login engine. Could not get channel ID. Could not allocate buffer for IPC channel. Could not get channel group. IPC initialization failure. Invalid data in message header. Invalid data in data part of message. Invalid session ID sent to remote login. Software error detected. Invalid command length. Invalid message type. Invalid message source. NE specified as command line argument does not exist. Unexpected message type received from remote login. Error getting user/host name for open RLogin parameter 2. Batch: IPC_SEND : SS_MAX_MSG_EXCEEDED. Batch: IPC_SEND : SS_NON_EXISTENT_CHANNEL. Batch: IPC_SEND : SS_NO_ACCESS. Batch: IPC_SEND : SS_INVALID_MSG_TYPE.
EMOTOROLA LTD. 2000
842
ISSUE 18 REVISION 0
Exit code number

45 46 47 48 49 50 51 52 53 54 55 56 60 61 62 63 64 70 71 72 73 74 80 90 100 110
Message
Batch: IPC_SEND : SS_INVALID_MSG_ADDR. Batch: IPC_SEND : SS_TOOBIG. Batch: IPC_SEND : SS_NOROOM. Batch: IPC_SEND : SS_INTR. Batch: IPC_SEND : Unknown error condition. Command line argument specified incorrectly. Should be -exit or -noexit. Command file must be specified as command line argument. Batch: Command failed. Error opening command file for reading. Error opening output file for logging. Command line argument specified incorrectly. Should be -xterm or -noxterm. Batch ended: Output file already exists. Batch: IPC_RECEIVE : SS_MAX_MSG_EXCEEDED. Batch: IPC_RECEIVE : SS_NON_EXISTENT_CHANNEL. Batch: IPC_RECEIVE : SS_NO_ACCESS. Batch: IPC_RECEIVE : SS_INVALID_MSG_TYPE. Batch: IPC_RECEIVE : Unknown error condition. Incorrect invocation of log_err_exit() function. Error returned from parse_response(). Text file read failure. Incorrect invocation of get_rl_err() function. Incorrect invocation of get_rl_discon() function. Program interrupt signal received. IPC timeout received. Disconnect indication received. ErrorRL message received from remote login.
EMOTOROLA LTD. 2000
843
A batch_rlogin example
ISSUE 18 REVISION 0
Introduction
This section describes an example batch_rlogin at a BSS named BSS_Cork, using a command file (BatchInput ) and specifying a log file (BatchOutput ).
BatchInput file
The contents of the BatchInput file are as follows:
# demonstration of batch facility # command file disp_time state 0 OML 1 0 0 disp_equip 0 OML 1 0 0 # end of commands
Format
The following starts the batch_rlogin utility using the BatchInput file specified above: batch_rlogin BSS_Cork <BatchInput> BatchOutput
844
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
BatchOutput file
The contents of the BatchOutput file, created as the log file when the BatchInput file shown previously was used as the command file, are as shown:
================================================================== 920925 09:45:11 Batch File Started ================================================================== BatchRlogin : Login Completed Successfully Login completed successfully # demonstration of batch facility BATCH CMD > NE RESPONSE > Cust BSS MMI0115 > # command file BATCH CMD > NE RESPONSE > Cust BSS MMI0115 > BATCH CMD > disp_time NE RESPONSE > Fri Sep 25 09:46:44 1992 Cust BSS MMI0115 > BATCH CMD > stat e0 OML 1 0 0 NE RESPONSE > STATUS INFORMATION : Device: OML 1 0 0 0 Administration state : unlocked Operational state : busy Reason code: No Reason Time of last transition : Thu Sep 24 17:12:48 1992 Related Device/Function: None END OF STATUS REPORT Cust BSS MMI0115 > BATCH CMD > disp_equip 0 OML 1 0 0 NE RESPONSE > Device ID for the OML : 1 First MMS identifier for this device : 1 Second MMS identifier for this device : 0 Timeslot on MMS where this device appears : 1 Cust BSS MMI0115 > BATCH CMD > NE RESPONSE > Cust BSS MMI0115 > # end of commands ================================================================== 920925 09:45:15 Batch File Ended : SUCCESS Exit Code 0 ==================================================================
EMOTOROLA LTD. 2000
845
Using Forms
ISSUE 18 REVISION 0
Using Forms
Forms session
A Forms session is an interface to the BSS MMI. Forms are worksheets that are completed when performing certain activities relating to a BSS. A Forms session can only be used to display the circuit status for MMSs and the channel status for RTFs. The TTY function gives full functionality when performing BSS-related activities.
Worksheet cautions
The following cautions apply to all open worksheets: S S S S Do not use the delete key to change values as this will alter the default spreadsheet properties. Always overwrite the values. Do not click on another worksheet when the default worksheet (where values have just been entered) is active, as this will make that worksheet the active worksheet. Do not run any two commands at the same time. Always use the Exit button in the Status window to exit from Forms. The Close option from the Motif menu must never be used to close the window if any MMI commands are being processed.
Displaying circuit status

The status of all the terrestrial circuits on a specific 2.048 Mbit/s link can be displayed using the following procedure: 1. 2. 3. Click on the Config Mgmt icon on the Front Panel, the Navigation Tree is displayed. Select the required MMS. Select Display Circuit Status from the menu bar, the BSS MML Command Constructor initialization window opens, see Figure 8-18.
Figure 8-18 BSS MML Command Constructor initialization window
846
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Using Forms
4.
Click OK to proceed, the Display MMS Status Selector window opens (Figure 8-19). The display interval can be specified in the Display Interval field.
15
Figure 8-19 Display MMS Status Selector window NOTE Any problems with the connection are indicated by an Error message displaying. Click OK to cancel the Forms session. 5. Click on the Apply button, an Information box is displayed, then the MMS Status window opens (Figure 8-20). While the circuit status is updating in the MMS Status window, the buttons are greyed out. Once updating has been completed, the Redisplay button is available for the time set in the Display MMS Status Selected window, shown in Figure 8-19.
Figure 8-20 MMS Status window 6. Click Redisplay to interrupt the Display Interval and force an immediate update. To exit the window during the Display Interval, click Redisplay, and then Exit while this Redisplay is being performed.
EMOTOROLA LTD. 2000
847
Using Forms
ISSUE 18 REVISION 0
Local transcoding
In Local Transcoding, the window as shown in Figure 8-20 is displayed. The window shows the state of the 31 timeslots. A legend of all possible timeslot states, with a single letter and an associated colour to represent each state, is also displayed in the window.
Remote transcoding
In the case of Remote Transcoding the window shows the current state of the 31 timeslots for each of the four groups. The contents are updated after the time specified in the selector box.
Displaying channel status

To display the channel status use the following procedure: 1. 2. 3. Click on the Config Mgmt icon on the Front Panel, the Navigation Tree is displayed. Select the required RTF. Select Display Channel Status from the menu bar, the Display Channel Status Selector window opens. The display interval can be specified in the Display Interval field. Click on the Apply button, an Information box is displayed stating that Channel Status is initializing, then the Channel Status window opens (Figure 8-21).
4.
Figure 8-21 Channel Status window

848
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Using Forms
Enabling Forms logging

To enable the logging of a Forms session, use the following procedure: 1. 2. Open an MMS Status window, or a Channel Status window. Click on the Enable Logging button.
Disabling Forms logging

To disable the logging of a Forms session, use the following procedure: 1. 2. 3. Open an MMS Status window, or a Channel Status window. Click on the Disable Logging button. Logging of the Forms session will not be performed until logging has been re-enabled.
Exiting a Forms session

CAUTION Always use the Exit button in the MMS Status window to exit from Forms. The Close option from the Motif menu must never be used to close the window if any MMI commands are being processed. To exit a forms session click on the Exit button in the MMS Status window, or the Channel Status window.
EMOTOROLA LTD. 2000
849
Using Forms
ISSUE 18 REVISION 0
850
EMOTOROLA LTD. 2000
Chapter 9
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
ii
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Chapter 9 Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of Configuration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Navigation form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Detailed views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How configuration management works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration management implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operational database parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The CM MIB function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changes to the network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration management from the OMC GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network configuration at the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description of network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definition of Navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uses of the Navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Detailed views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definition of detailed views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical detailed view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definition of audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC areas changed by audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How audit works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Periodic auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Admin Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of EAS alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EAS alarm form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software load management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of software load management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NE and OMC software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements of software load management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load Mgmt option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software inventory window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software load installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install Load dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a software load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Archiving a software load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NE software loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The NESoftware detailed view form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conventional download to a new NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2000
i
91 91 91 91 91 92 93 93 93 94 94 94 95 96 96 98 98 98 99 910 910 910 911 912 912 912 913 914 914 915 915 915 916 916 916 916 917 918 918 919 920 920 921 921 921 922 924 924 925
iii
ISSUE 18 REVISION 0
CSFP database setup (for download) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Criteria for CSFP download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The activate_db script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CSFP options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to CSFP options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CSFP status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure CSFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download CSFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Swap CodeLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unconfigure CSFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download to CSFPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A two stage process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Criteria and guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CSFP download process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Aborting download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fallback to backup database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of backup databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The fallback_db utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NE database management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operational database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NE database management utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load management utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DataGen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to DataGen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DataGen configuration management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Off-Line MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NE configuration changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network configuration status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X.121 DTE addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event and alarm subscription lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet switch / multiplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC - BSS remote login interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NE database upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TTY interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The batch_rlogin utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The batch user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The logfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command line example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command line example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
926 926 926 926 927 927 927 927 927 928 928 928 929 929 929 929 930 930 930 931 931 931 931 932 932 932 932 933 933 934 934 934 935 935 936 936 937 937 938 938 938 938 938 939 939 939 940 941 941 942 942 943 943
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Overview of Configuration management
Configuration Management allows the operator to see the objects in the network and enables the creation, deletion and modification of network resources. A GSM network is constantly changing and growing with both hardware and software at the network elements (NEs). Operators need procedures to manage the introduction of new software and changes to operational databases at NEs, and to reconfigure existing NEs.
Functions
Configuration management at the OMC provides a centralized facility for performing the following tasks: S S S Network configuration. NE software load management. NE software download: S S Conventional download (monitoring and aborting only). CSFP (Code Storage Facility Processor) download (initiating, monitoring and aborting). Supplemental download.
NE operational database backup (monitoring and aborting only). Network re-configuration.
The Navigation form

Selecting the Config Mgmt icon invokes the Navigation form, which displays a tree-like representation of the network. Refer to the Navigation tree section in this chapter for more information.
Detailed views
The attributes of the objects represented on the tree reflect their actual settings in the network. The attributes of these objects can be viewed, and changed using Detailed View forms. Refer to the Detailed views section in this chapter for more information.
EMOTOROLA LTD. 2000
91
ISSUE 18 REVISION 0
Audits
Audits are carried out to check if objects and object attributes are consistent at the NE and the CM MIB, and to allow any differences to be corrected. Audit lists any inconsistencies between the NE database, the OMC database for the selected NE or Site, and their containees. These inconsistencies can be applied to the OMC or NE database (DB) as required. If the user applies the inconsistencies to the OMC, then objects not in the NE DB but in the OMC DM are deleted at the OMC. Objects in the NE DB are created in the OMC DB, and attribute value inconsistencies are updated in the OMC DB according to the NE.
92
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
How configuration management works

Configuration management implementation
Figure 9-1 presents an overview of how the different configuration management functions are implemented.
X.121 DTE ADDRESSING AT NE NETWORK CONFIGURATION
(VIA RLOGIN or SYSGEN or DATAGEN)
SOFTWARE LOAD MANAGEMENT NE DATABASE CHECKPOINTING
NETWORK NAVIGATION TREE

NETWORK MAPS BACKGROUND MAPs
NETWORK RECONFIGURATION
VIA CM MIB VIA REMOTE LOGIN
RLOGIN PROCESS
cmutil
X.121 DTE ADDRESSING AT OMC SOFTWARE UPLOAD/DOWNLOAD
OMC PROCESSOR
NE Software load copies MASTER GPROC
Current NE Software Load
Operational Database
Current New download enable NE1[Y/N] load to download download enable NEn [Y/N] load to download Database Copy
MPRouter CONFIGURATION
CSFP GPROC
CSFP NE Software Load
MMI
MMI PROCESSOR
X.25
NE1 NEn
Binary Binary
CSFP Operational Database

RLOGIN
CM MIB
BSS/RXCDR
Figure 9-1 Configuration management using the OMC
Operational database parameters

NEs are controlled by parameter settings in the Operational Database. The parameters vary from specifying what devices and functions are equipped at each SITE of the NE, to the RF control of each cell. When installing an NE the parameters of its operational database are set using Motorola supplied tools, such as Sysgen or DataGen. Thereafter the OMC can be used to change an NEs Operational database parameters, and thereby remotely control the NE. The OMC-BSS remote login interface (Rlogin) provides the facility to add, modify and display any of the operational database parameters. For example, the raw statistics needed to monitor the performance of any cells can be enabled or disabled.
EMOTOROLA LTD. 2000
93
ISSUE 18 REVISION 0
The CM MIB function

The CM MIB contains managed objects which model the parameters of the GSM network. It contains all the necessary network configuration information that an operator needs to check the devices and RF parameters in the network. The RF parameter settings can be changed in the CM MIB via the GUI, and propagated out to the network. The MIB is used to implement the GUIs Network Status Summary (NSS) feature which configures and runs the different network maps, and the alarm summary on the front panel of the OMC GUI. The MIB also maintains Call Trace objects for every call trace created from the OMC GUI. The invoked traces are not deleted at the MIB when the call traces are completed, as the OMC operator may wish to view call trace records associated with the completed calls. The Call Trace objects are deleted from the MIB only when call trace logfiles are deleted.
Changes to the network

In order for the OMC to communicate successfully with all the nodes in the network, it must always reflect the current state of the network. This enables it to perform Event Management, Performance Management, and Configuration Management functions such as NE database checkpointing and load management of the NEs. Any changes to the network configuration involving the download of a new database can be quickly entered in the CM MIB using an Audit procedure. Objects that are created or deleted, and object attributes that are changed at the OMC or at an NE will cause an automatic update at the OMC database. An update will only occur when the change has been successfully received at the BSS.
Areas of the OMC processor

Changes to the MIB are then propagated to different areas of the OMC Processor. This ensures that the entire OMC system can communicate correctly with the NEs. These areas are as follows: S S S NE.MAP SITE.MAP The PM sub-schema tables.
Load management
Software load management provides the operator with one central location from which to remotely load all the NEs with operating software. New software loads, for example, BSGSM 1.6.0.x, are installed on the OMC Processor, and later downloaded to the NEs under the control of the OMC GUI. The OMC GUI provides facilities to allow changes of software loads for NEs. A binary version of each NEs operational database is held at the OMC. This allows data to be recovered, if a failure occurs at the NE that results in a loss of data at the database, by downloading the backup database from the OMC. The process of updating the binary version of the operational database from the NE is known as Database Checkpointing.
94
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Configuration management from the OMC GUI

The OMC GUI provides a menu driven interface which allows the operator to perform the majority of Configuration Management (CM) network management functions. The CM options that can be accessed from the GUI Front Panel are shown in Figure 9-2.
CONFIG MGMT ALLOWS THE OPERATOR ACCESS TO THE CM MIB INCLUDES: D LOAD MGMT ALLOWS THE OPERATOR ACCESS TO SOFTWARE LOAD MANAGEMENT INCLUDES: D D D D
NAVIGATION FORMS which give a tree-like graphical representation of all or part of the network model. DETAILED VIEWS (one for each object) which give the values of the different attribute settings of the objects. These can then be changed, and propagated to the network.
SOFTWARE INVENTORY. NE SOFTWARE LOADS. DOWNLOAD STATUS. UPLOAD STATUS.
GSR 4.1 1.6.1.0
REMOTE LOGIN ALLOWS THE OPERATOR ACCESS TO BSS-MMI COMMANDS. TWO INTERFACES ARE PROVIDED: D D
ADMIN ALLOWS THE OPERATOR TO SCHEDULE AND MANAGE THE AUDIT AND RESYNC FUNCTIONS. D D
TTY BATCH
AUDIT ensures the CM MIB is up to date with the current Network configuration RESYNC ensures the state of the CM MIB objects is up to date with the current state of devices in the Network
Figure 9-2 OMC GUI Front panel showing configuration management options Some CM functions are performed by remote logging into the System Processor and using the UNIX command line to run utilities provided by Motorola, when performing database management for example.
EMOTOROLA LTD. 2000
95
Network configuration at the OMC
ISSUE 18 REVISION 0

Description of network configuration
The OMC must always remain up-to-date with the current network configuration. Figure 9-3 shows the objects in the MIB which represent the network. There are four logical groups beneath the Site object: Hardware devices. Software functions. Logical links. Radio frequency.
Beneath the Hardware devices there is a further logical group called Processors. These groupings allow ease of navigation down to a particular hardware device or software function. Refer to the Configuration objects section in Chapter 2. Changes can be made to attribute values for all objects. The update is sent to the NE, and if the NE indicates to the OMC that the update was successful the OMC database is updated accordingly. The MIB can be used to directly manage the RF parameters in the different CELLs in the network, and create/delete devices/functions under SITE from the Navigation Tree. The MIB also contains other objects which are used in Load Management, and in implementing the Network Status Summary (NSS) feature. This feature configures and runs the different network maps, and the alarm summary on the front panel of the OMC GUI (see Chapter 3 Event Management of this manual).
96
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
NAVIGATION TREES
GIVE TOPOGRAPHICAL VIEW OF NETWORK AND CONTAINED DEVICES

BSS1
DETAILED VIEWS OMC SYSTEM PROCESSOR AUDIT
DISPLAY PARAMETER SETTINGS. ALLOWS CHANGES TO BE MADE IN NE. IF SUCCESSFUL THE CM MIB DATABASE IS UPDATED. ENSURES THE PARAMETERS OF THE CM MIB AND NETWORK CORRESPOND

BSS2
X.25
CM MIB
Map
MapNode
MapLink Network

BSSn
Hardware Devices
BSS
RXCDR CommsLink
MSC
OMC SWInventory
PCU
NESoftware SITE
SoftwareLoad
Software Functions
Logical Links
Radio Frequency
BTF
LCF
OMF
RSL
PATH
RTFGroup DRIGroupCELL RTF DRI
Cabinet CAGE
EAS
Processors
COMB
KSWpair
GCLK
IAS
LAN
TDM
MSI
GPROC
BSP
CSFP
FreqHopSys SMSCBmsg Neighbour TestNeighbourHandover/ TRX Power Control
Figure 9-3 The containment relationship for the configuration objects
EMOTOROLA LTD. 2000
97
Navigation tree
ISSUE 18 REVISION 0
Navigation tree
Definition of Navigation tree
The Configuration Management (Config Mgmt) icon can be selected to open the Navigation Form (Figure 9-4). The Navigation Form gives a tree-like representation of the configurable objects in the network. An object represents network resources or components. Information relating to the NE is stored at the CM Management Information Base (CM MIB).
Uses of the Navigation tree

From the Navigation Tree, it is possible to create, delete, view, edit and audit certain objects. The Navigation Tree provides the following: S S A view of the Network device topography. The level of detail is selectable. Access to different detailed view forms for the following CM MIB objects: S S S Configuration objects, which are displayed on the Navigation tree to represent devices in the Network. Graphic objects - used for setting up the network maps used by the NSS feature. Objects used for Load Management - these are contained by either the BSS or RXCDR object.
Ability to create or delete objects from the CM MIB. Perform audits on Network/BSS/RXCDR/SITE objects. Print the portion of the CM MIB hierarchy being displayed.
Figure 9-4 The Navigation Form

98
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Navigation tree
The OMC Online Help facility can be selected by clicking on the Help icon on the Navigation form. This opens a drop down menu where contact sensitive help can be selected.
EMOTOROLA LTD. 2000
99
Detailed views
ISSUE 18 REVISION 0
Detailed views
Definition of detailed views
Detailed Views display the settings of object attributes, which correspond to the parameter settings of the device the object models in the network. Detailed Views are provided for all objects supported on the CM MIB. If the object type allows, the attribute values can be modified. Operations can be performed on the object using menu bar options. CELL parameters can be modified to improve the overall performance of the network, and changes can be propagated out into the network.
Typical detailed view

A typical Detailed View of a CELL object is shown in Figure 9-5. The attributes are displayed in appropriate groups. The Identification and Additional Information groups are provided in each objects Detailed View. These give information about the object, which the MIB requires. Other groups, such as General and Handover-General, are specific to the object and relate to a specific configurable database parameter in the NE.
Monitor mode
Detailed Views are always displayed in Monitor mode. In Monitor mode the user can read each data field, but not modify them.
Edit mode
The user must be in Edit mode, and have the appropriate permission level, to modify the attributes of an object. Once in Edit mode the object is locked in the CM MIB preventing any other users modifying it. In Edit mode additional options on the File menu are available, such as Save, Revert, and Delete.
910
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Detailed views
Figure 9-5 Cell detailed view
Refer to the OMC Online Help facility for complete details on the Navigation form.
EMOTOROLA LTD. 2000
911
Audit
ISSUE 18 REVISION 0
Audit
Definition of audit
Audit ensures that the OMC and NE databases are synchronized. New objects are automatically created in the CM MIB when necessary. The changes to the MIB are then propagated to different areas of the OMC processor. This ensures that the entire OMC system can communicate correctly with the NEs.
OMC areas changed by audit

The areas of the OMC Processor that undergo changes are: S NE.MAP This configuration file is maintained on the OMC System Processor, and is NFS mounted to the MMI servers. It contains details of all the nodes managed by the OMC. Details on the software load for each NE and the DTE addresses for the OMC - NE data communications protocol are held in the OMC System Processor. If a BSS resets, the OMC will know the software version to download and the download address. S SITE.MAP This is a configuration file that must be updated frequently, as it contains all the configuration information required by the OMC event management processes. S The PM sub-schema tables. The OMC database on the System Processor contains the PM sub-schema. This defines the different tables used for performance statistics storage and reporting. These tables must be maintained to reflect any changes to the network. Audits can also be scheduled on a periodic basis, for any or all Network, BSS, RXCDR and SITE objects.
912
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Audit
How audit works

Figure 9-6 shows how Audit is selected for a particular object. In this example a BSS object is selected. All objects contained by the BSS object are audited. See Operating Information: System Operation (GSM-100-201) for more information.
Figure 9-6 Selecting Audit for a particular object
EMOTOROLA LTD. 2000
913
Audit
ISSUE 18 REVISION 0
Periodic auditing
Periodic auditing operations can be accessed by selecting the Admin option on the GUI Front Panel (Figure 9-7).
Figure 9-7 Admin Options window
Admin Options
The Admin Options window includes the following items:
Controlling access
The Access Control selection on the Admin Options window allows the OMC System Administrator to change the command partitioning options for users.
Scheduling audits
The Audit Scheduler selection on the Admin Options window allows the operator to schedule an audit of the network, BSS, RXCDR or SITE.
Checking audits
The Audit Logs selection on the Admin Options window allows the operator to check the results of an object audit.
Scheduling a resync
The Resync Scheduler selection on the Admin Options window allows the operator to schedule a resync of the network, BSS, RXCDR and SITE.
Checking a resync
The Resync Logs selection on the Admin Options window allows the operator to check the results of a resynchronization.
Scheduling PM reports
The PM Reports Scheduler selection on the Admin Options window allows the operator to schedule a performance management report on the network.
914
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Audit
Checking PM reports
The PM Reports Logs selection on the Admin Options window allows the operator to check the results of a performance management report of the network. If a scheduled audit, resync or report has not started the operation can be deleted. If a scheduled audit and resynchronization has already started, the scheduled operation can be aborted. The user can create, view, edit, and print scheduled audits and carry out resynchronizations of the network, BSS, RXCDR, or SITE.
Audit Log management

The Audit Log management selection deletes audit logs after a predefined period of between one and seven days.
Refer to the OMC Online Help facility for complete information on Admin options. Refer to Operating Information: OMC System Administration (GSM-100-202) for complete information on the system administration procedures.
Overview of EAS alarm

BSS and RXCDR devices contain External Alarm System (EAS) alarm objects. These objects represent the alarms that are generated by the BSS EAS devices. Each BSS or RXCDR contains thirty-four of these objects. They are created at the OMC via an audit. The EAS alarms form combines all of the EAS alarms in one list.
EAS alarm form

The EAS alarm form is available by selecting Config Mgt EAS alarms from the Navigation Form menu bar (refer to Figure 9-6). The alarm form provides the user with a list that displays the alarm ID, Severity, and Alarm text. The operator can change the severity and alarm text of any EAS Alarm by selecting an alarm and invoking the Edit Detailed View option. This will display a Detailed View for the EAS alarm object.
EMOTOROLA LTD. 2000
915
Software load management
ISSUE 18 REVISION 0

Overview of software load management
Software load management provides the operator with a central location to remotely load all the network elements with operating software. New software loads are installed at the OMC, and later downloaded to the NEs under the OMCs control.
NE and OMC software

The NE operating software contains different objects that determine the operating capability of BSCs and BTSs. New NE software updates are released periodically. These updates are improved versions of existing functionality, or upgrades that introduce new facilities and features. The OMC operating software is usually compatible with at least two versions of NE operating software. For example, OMCGSM 1.6.0.X is compatible with BSGSM 1.5.1.X and BSGSM 1.5.0.x.
Requirements of software load management

The requirements of software load management can be summarized as follows: S S Management of NE loads. Load maintenance at the OMC for all NEs under its control. Software load archive. Software loads are archived at the OMC. A backup version of NE software should be maintained at the OMC, on a non-volatile medium, which can be reloaded in case of failure. Procedures are available for selective archiving/retrieval of individual files, or complete NE software loads. S Load installation at the OMC. The new software loads for NEs are first installed at the OMC from tape, DAT drive or CD-ROM. S S S S S Loading a network entity from the OMC. Specifying a NE software load for each NE in the network. Controlling conventional or supplemental download of software to the NE. If applicable, specifying a code storage facility processor (CSFP) software load for each NE in the network. Controlling a CSFP download of software to the NE. When the OMC downloads to a BSS/RXCDR, it transfers the appropriate objects to the BSC. These are required to operate that BSC and the corresponding BTSs under the control of the OMC. The BSC subsequently controls the loading of the BTSs.
916
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Load Mgmt option

The Load Mgmt option can be selected from the GUI Front panel, refer to Figure 9-8. The Software Load Management window displays the software load information for the network. The entries in this window are displayed in alphabetical order and according to NE type with BSSs preceding RXCDRs. Double clicking on an entry in this window opens the NE Detailed View form.
GSR 4.1-1.6.1.0
Figure 9-8 Load management from the OMC GUI front panel
EMOTOROLA LTD. 2000
917
ISSUE 18 REVISION 0
Software inventory window

The Software Inventory window tells the operator which software loads are available in the NE load directory. A current or new load that has been updated, may be deleted from the NE load directory by selecting Options Remove Load. From the Software Load Management window, select the required NE(s), then select Edit New Software Load, the Software Inventory window opens, refer to Figure 9-9.
Figure 9-9 Software Inventory window
Refer to the OMC Online Help facility for complete information on the Software Inventory window. Refer to Operation Information: Scaleable OMC System Administration (GSM-100-202) for procedures on managing software loads.
918
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Software load installation

Load installation is used to transfer the contents of the load tape, DAT tape or CD-ROM to a specific directory at the OMC. The Install Load window is displayed by selecting Options Install Load from the menu bar on the Software Inventory window. The Install Load window includes information required to install a Software load (BSS or RXCDR) from tape at the OMC.
MASTER GPROC Current NE Software Load
NEW SOFTWARE LOAD
CSFP GPROC
NEW SOFTWARE LOAD CURRENT SOFTWARE LOAD TO BE USED ON NE RESET SOFTWARE LOAD USED AS NEW CSFP LOAD DURING DOWNLOAD
CURRENT CSFP LOAD
BSS/RXCDR
OMC SYSTEM PROCESSOR
MMI
MMI PROCESSOR
Figure 9-10 New software load installation
EMOTOROLA LTD. 2000
919
ISSUE 18 REVISION 0
Install Load dialogue

The Install Load dialogue box contains the following information: S S S S Load name (as in Table 9-1). Tape Device. The name of the input device. Host Name. The name of the machine containing the tape device. Load Type. BSS, RXCDR or BSS and RXCDR.
Load names
The software load name is composed of a prefix followed by the version number of the software in the load. The prefix used depends on whether the software load is to be run on a BSS, an RXCDR, or BSS and RXCDR network entities. The following convention is used for the prefix: Table 9-1 Motorola GSM Load Naming Conventions Loads BSS RXCDR BSS and RXCDR Encrypted BSS Encrypted RXCDR Encrypted BSS and RXCDR BSGSM XRGSM BSGSM BSGSME XRGSME BSGSME Prefix
920
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Deleting a software load

A software load that is not a current load, new load, current CSFP load, or New CSFP load, for example, a load that has now been updated, may be deleted from the NE load directory. The Remove Load option can be selected from the Options menu in the Software Inventory window.
Figure 9-11 Remove Load option on the Software Inventory window NOTE Removing a load will overwrite the current load files at the NE load directory with the new load files.
Archiving a software load

Archiving software loads is an essential part of software load management. A backup version of all NE software should be maintained at the OMC on a non-volatile medium which can be reloaded in case of failure. It is therefore essential that both the new and the current version of the NE load software is archived. Procedures are available for selective archiving and retrieval of individual files or complete NE software loads.
NE software loads
When an NE resets, it usually boots from the software currently loaded on its Master GPROC. Every NE can have a software load assigned to it at the OMC. This allows an NE to boot from the load currently at the NE in the event of a reset, or the NE can download the assigned software load and boot from that instead. Each BSS and RXCDR object has an associated NESoftware object specifying the software load for conventional download and the software load for the CSFP download.
EMOTOROLA LTD. 2000
921
ISSUE 18 REVISION 0
The NESoftware detailed view form

An NESoftware detailed view form can be opened for a BSS and RXCDR from either the Load Mgt window or NE detailed view. Refer to Figure 9-12. The NESoftware detailed view form displays information about the software loads associated with an NE. It displays the software currently loaded at the NE, and the software load specified for conventional download. The CSFP load that is currently loaded at the NE is displayed, as is the new CSFP load to be downloaded. By editing the NESoftware detailed view the operator can change the load to be used for a conventional download, or a CSFP download. A flag can also be set which specifies that the complete object set of the load is downloaded (not just the ones which differ from those at the NE) if a conventional download is chosen.
922
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Figure 9-12 The NESoftware Detailed View
EMOTOROLA LTD. 2000
923
Conventional download to a new NE
ISSUE 18 REVISION 0

Download procedure
Figure 9-13 shows how the OMC is configured to allow a new NE load to be downloaded to the base. NOTE A conventional download of an NE load to the Base results in the NE being OOS for the whole time period of a download. The full download procedure is provided in Operating Information: GSM System Operation (GSM-100-201) in addition to the procedures for backing up the active database, and for specifying the database to be downloaded with the NE software.
CHECK THAT THE NE IS FUNCTIONING CORRECTLY
BACKUP THE CURRENTLY ACTIVE DATABASE AT THE NE
SPECIFY NEW SOFTWARE LOAD FOR THE NE
Use the NESoftware Detailed View
ACTIVATE THE DATABASE FOR THE NE
ENABLE THE DOWNLOAD FLAG FOR THAT NE
Use the NESoftware Detailed View
CHECK IF ANY FIRMWARE CHANGES ARE NEEDED AT THE NE BEFORE IT CAN RUN THE NEW LOAD
RESET THE NE TO BEGIN DOWNLOADING
Use Rlogin (reset_site MMI command)
CHECK THE STATUS OF THE DOWNLOAD
Use the Download Status window/ Check for associated alarms Tail the OMCaudit file
Figure 9-13 Conventional software download The operator should follow the above steps if there is no CSFP load at the NE to swap over or there are new NEs.
924
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Download process
When a download is initiated, the OMC supplies the NE with a list of objects that describes the latest new load for that NE. The NE determines whether the list is consistent with the software load that is presently installed. If not, the new load is downloaded. In the case of updated software, only the new objects are downloaded.
Steps
The download process steps are as follows: Step a. b. c. d. Process Download process is initiated from the OMC. The NE requests a list of objects from the OMC. The OMC sends the list of objects to the NE. The NE compares the list from the OMC with its current list of objects, and requests objects that it does not have. The NE can also be instructed to receive or send the complete load. The objects are downloaded.
e.
MASTER GPROC
Operational Database CSFP GPROC
reset_site Request object list

b
a NEW SOFTWARE LOAD FOR NE CURRENT NE SOFTWARE LOAD
Send object list for new load Request objects as required Download objects
e OMC System PROCESSOR
NE (BSS/RXCDR)
Figure 9-14 NE software downloading process
EMOTOROLA LTD. 2000
925
CSFP database setup (for download)
ISSUE 18 REVISION 0
CSFP database setup (for download)

Criteria for CSFP download
For each BSS there is a CSFP load directory, which contains the object list and the database object, to be downloaded to the BSS in the event of a CSFP download. The database object can only be downloaded if the CSFP device contains a code load. The database object is loaded into the CSFP directory, and the same software load that is running on the CSFP at the BSC is selected to be downloaded.
The activate_db script

The database to be downloaded must be loaded using the activate_db script. The database can be loaded onto the OMC using the load_db script and then moved into the CSFP directory using the activate_db script.
Refer to Operating Information: GSM System Operation (GSM100201) for more details of OMC utilities.
926
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
CSFP options
CSFP options
Introduction to CSFP options
The following options are available from the CSFP menu in the Software Load Management window: S S S S S CSFP Status Configure CSFP Download CSFP Swap CodeLoad Unconfigure CSFP
CSFP status
The CSFP Status window displays the status of the CSFP devices at the NE identified in the header of the window. This window can be used to monitor the progress of CSFP related commands. The CSFP Status window displays a scrollable list of all SITEs containing configured and unconfigured CSFP devices at the NE. The window is dynamically updated to reflect state changes that occur at CSFP devices. These devices change state when CSFP related commands are in progress, and when the commands are complete. Refer to Installation & Configuration: GSM System Configuration (GSM-100-403) for procedures relating to CSFP devices.
Configure CSFP
This option sends a request to the parent NE to configure a CSFP device at each of its SITEs. A dialogue box is displayed prompting the user to confirm the operation. The NE scans its SITEs, selects at most one GPROC on each SITE and equips that GPROC as a CSFP device. With M-Cell, there can now be two CSFP devices at site 0 (device 0 and 1). These can now be configured. The result of this operation is displayed on the status line of this form. The progress of the operation can be monitored on the CSFP Status form. The operation is considered successful if the SITE_0 CSFP device is configured at the BSC or RXCDR.
Download CSFP
The Download CSFP option is selected to download the new CSFP load from the OMC to all CSFP devices at the NE. If the operation completes successfully at SITE_0 (BSC or RXCDR), the value of the current CSFP load attribute is automatically set to the value of the new CSFP load attribute on this form.
EMOTOROLA LTD. 2000
927
CSFP options
ISSUE 18 REVISION 0
Swap CodeLoad
The Swap CodeLoad option causes a fast reset of the NE. SITES that contain a CSFP device boot from the software installed at this device. SITES that do not contain a CSFP device download software from the BSC and boot with this new software. The result of this operation is displayed on the status line of this form. The progress can be monitored on the CSFP Status form. To swap a code load, select the required NE from the Software Load Management window, then select CSFP Swap Code Load from the menu bar. A dialogue box is displayed, requesting confirmation. The dialogue box also displays the load name and load version that will be installed at the BSC. On clicking OK, the changes are executed.
Unconfigure CSFP
After a CSFP swap, if the new BSS database contains configured CSFPs, a copy of the old software instance will be retained. Where necessary, the old software can be restored quickly by executing the Swap CodeLoad option. If this fast fallback facility is not needed, the CSFP devices may be returned to their original functionality by selecting the Unconfigure CSFP option. The OMC generates a message and sends it to the BSS. The BSS unconfigures all the CSFPs. After the CSFPs are unconfigured it is recommended that the operator uploads the database to the OMC, as the OMC and BSS database level numbers will be different.
Refer to Technical Description: BSS Command Reference (GSM-100-321) for complete information on the CSFP Options.
928
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Download to CSFPs
Download to CSFPs
A two stage process
Downloading the new software load to the CSFPs is a two stage operation: 1. 2. The code and database objects must be downloaded from the OMC to the CSFP at the BSC. The objects must be downloaded from the BSC CSFP to the BTS CSFPs.
Criteria and guidelines

The OMC operator issues the download command once to download the BSC CSFP. The BSC proceeds with the rest of the download operation. The database in the CSFP directory must have CSFPs configured if fallback is required. The BSC only takes objects whose version in the BSC CSFP load differs from that in the OMC.
CSFP download process

The CSFP download process is as follows: Step a. Action The OMC operator selects a load to be downloaded at the OMC GUI. Result On saving this selection, the OMC copies the object lists for the load selected to the CSFP directory for this NE. The BSS accepts or rejects the download request. If a request is rejected it may be that a CSFP device is not configured at the BSC. When the BSC brings up the download VC, the OMCs downloader process generates a CSFPDownloadConnected event.
b.
The OMC sends the download message to the BSC using the Download CSFP option from the CSFP menu on the NE Software Detailed View. If accepted, the OMC waits for the BSC to bring up the download VC and requests the code object list for the CSFP load to be downloaded. When this operation is completed, the OMC downloader process generates a CSFPDownloadCompleted event to indicate that the download to the BSC CSFP has completed successfully. The current CSFPLoad attribute is updated to reflect the software load now running on the BSCs CSFP.
c.
d.
e.
The BSC continues to propagate the load to the CSFPs at the remote BTSs.
EMOTOROLA LTD. 2000
929
Download to CSFPs
ISSUE 18 REVISION 0
Download monitoring
The main methods used to monitor the CSFP download are: S S Monitoring the download events via the Event window. Monitoring the progress of objects downloading via the Download Status window.
Download control
If there are a number of BTSs in the network, the download may be controlled by locking the CSFP devices at the sites which the operator does not yet want downloaded. Locking a CSFP at a BTS causes the download to that site to be suspended, until the device is unlocked again.
Aborting download
There is an abort operation on the OMC GUI, which causes the OMC to pull down the download VC and abort the conventional, CSFP or Supplemental download currently in progress to the BSC. The CSFP download to the BSC or BTSs can be aborted by locking the CSFP device at the BSC. If the operator wishes to download a different CSFP load in the middle of a CSFP download, another load may be selected by setting the new CSFP load attribute and re-issuing a new Download CSFP command. The BSC aborts any active CSFP download (either OMCBSC or BSCBTS) and starts taking the new CSFP load.
930
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Fallback to backup database
Fallback to backup database

Overview of backup databases
If the new NE software version is downloaded to an NE and causes problems, the previous version can be restored.
The fallback_db utility

The fallback_db utility automatically performs a fallback to a specified backup database for a specific NE (<NE_Name>).
Refer to Operation Information: GSM System Operation (GSM-100-201) for the fallback procedure.
EMOTOROLA LTD. 2000
931
NE database management
ISSUE 18 REVISION 0
Operational database
Each NE has an operational database containing details of its current configuration. Information, such as, the hardware configuration of the different sites in a BSS, which devices have redundancy, what links have been configured, and what PM statistics have been enabled is contained in this database. The active NE database is always Object no. 2 of the software load running at the NE.
MASTER GPROC
CSFP GPROC
DATABASE COPIES DATABASE BACKUP (CHECKPOINTING) BSS1 BSS2 ACTIVE DATABASE FALLBACK DATABASE ACTIVE DATABASE FALLBACK DATABASE ACTIVE DATABASE FALLBACK DATABASE ACTIVE DATABASE FALLBACK DATABASE
X.25
BSSn Xcdr1
DATABASE DOWNLOADING (IF THE NE FAILS) SYSTEM PROCESSOR BSS/RXCDR
Figure 9-15 Database backup (checkpointing)
Database upload
A database upload, also known as checkpointing, should always be performed each time there are changes to the database, and before a software download. System data management is used to maintain sets of up-to-date backup operational databases at the OMC, in case a failure at the NE occurs (resulting in corruption of the configuration data at the node).
Database status
The following list details the status of the operational database in the OMC and BSS. S S S S A backup of the active database and a fallback database are maintained at the OMC for each node in the network. A BSS configuration database uses approximately 4.5 Mb of memory. All backup databases on the OMC are automatically compressed to save disk space, this reduces the size to 250 Kb. Backup databases for NEs are contained in backup directories, (dbDDMMYYYYhhmmss), in $DBROOT/NETYPE/NEspecific/<NE_Name> . NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000
932
ISSUE 18 REVISION 0
Backup
The previous fallback version of each NE database should be archived to release the memory space for the new database copies after every backup. Each NE database has an associated user comment file that allows a user comment about the particular database to be entered. Due to the large size of the databases, configuration changes at the NE and the subsequent database checkpointing result in a large traffic load on the O&M network. Therefore, database uploading should be carried out using locally-established procedures and frequency intervals, to ensure that the O&M network is not overloaded.
Refer to Operating Information: GSM System Operation (GSM-100-201) for information on upload, backup and archive procedures.
EMOTOROLA LTD. 2000
933
NE database management utilities
ISSUE 18 REVISION 0
NE database management utilities

Load management utilities
NE load management utilities, load_db and activate_db, are provided to enable new NE databases created to be unloaded from tape, DataGen or any machine on the LAN and configured as the active database for a particular NE. Another utility, database_info , gives a printout of relevant information of all new, active, backup and CSFP databases for any NE. Details of these utilities can be found in Operating Information: GSM System Operation (GSM100201).
Access
The utilities are available to the omcadmin user from the Database Mgt menu in the Software Load Management window.
Figure 9-16 NE database management utilities
934
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
DataGen
DataGen
Introduction to DataGen
DataGen is a GSM product used to create BSS databases off-line. DataGen can store past, current, and future versions in an Informix database. These databases can be transferred to the OMC, then they are downloaded to the live BSSs. DataGen runs on its own SPARC and can be integrated with the OMC if they are both on the same LAN. DataGen is generally used to make major changes to a network, for example, upgrades to the BSS software, frequency replans, and network expansion.
DataGen
NMC
OMCR
OSI
Local Area Network
System Processor
Network Management Centre Gateway Processor
Operator Workstations
BSC
X.25
BSC BSC
BSC
Figure 9-17 DataGen in a GSM environment.
EMOTOROLA LTD. 2000
935
DataGen
ISSUE 18 REVISION 0
DataGen configuration management

DataGen provides the user with the capability of performing off-line configuration of Motorola GSM network entities (NEs). The Informix database contains two types of information: S A representation of the information required to create a Sysgen script for all supported BSS releases. Included in this are details relating to syntax, parameters, elements, and their associated ranges for the MMI commands in the Sysgen script. S Configuration information for a specific BSS area. These areas are identified by country or network, name, software release, and configuration number. The configuration number allows multiple BSSs to exist within the DataGen database.
Figure 9-18 DataGen Main window
Off-Line MIB
The Off-line MIB is used to create new networks, visualise and validate networks before deployment into a live network. It has a common user interface with the online OMC. BSS binary files are used to create the network which is displayed as a tree-like representation called the Navigation Tree. It is possible to update multiple BSS binary files simultaneously, for example, propagating neighbour changes from one BSS binary file to another. The Navigation Tree allows: S S S Graphical editing of configuration management. Neighbour propagation. An interface to radio refrequency planning tools.
GSR 4.1 1.6.1.0
Figure 9-19 Off-line MIB Front panel

936
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
NE configuration changes
NE configuration changes
Procedure list
The configuration of CELL parameters in any NE in the GSM network can be changed via the CM MIB. From the OMC GUI, it is possible to change other operating parameters of any SITE, under the control of the OMC. Figure 9-20 lists some of the changes that are possible. All the changes are maintained in the NE operational database and, if changes are made, the database should be uploaded to the OMC.
EXAMPLES OF DIFFERENT CONFIGURATION TASKS D D D D D D D STATUS OF A SITE. ADD SOURCE CELL. ADD/CHANGE A NEIGHBOUR CELL. EQUIP/DISABLE DEVICES, FOR EXAMPLE, DRI. EQUIP/DISABLE FUNCTIONS, FOR EXAMPLE, RTF. ENABLE/DISABLE STATISTICS REPORTING FOR ALL OR SELECTED DEVICE TYPES. MODIFY THE RAW STATISTICS REPORTING INTERVAL.
GUI SESSION
X.25
RLOGIN SESSION
MMI
MMI PROCESSOR System ESSOR PROC-
BSS/RXCDR
Figure 9-20 Changing a SITE configuration
EMOTOROLA LTD. 2000
937
Network configuration status
ISSUE 18 REVISION 0
Network configuration status

Requirements
The OMC must always reflect the current state of the network to be able to communicate successfully with all the nodes on the network. The OMC must be up-to-date to perform EM, PM and functions, such as, NE database checkpointing and load management of the NEs. Large-scale changes to the network configuration, such as adding a BSS can be entered into the CM MIB by running an Audit procedure; smaller changes, such as changing parameters, can be performed directly via Detailed Views. NOTE Refer to the Audit section of this chapter for more information on how Audit works.
X.121 DTE addresses

All X.121 DTE addresses at both the OMC and NE must be assigned for the new BSC/RXCDR, and must be set at both the NE and at the OMC. Four identical NE X.121 DTE addresses and either two to seven OMC addresses must be set at the NE. The purpose of this addressing is to verify the calling address on the inbound X.25 packet. The NE rejects any connections where the address does not match. The X.121 addresses can be set using remote login (via BSS MMI commands) to the NE, or can be entered locally at the NE. At the OMC, the X.121 DTE NE address is stored in the Detailed View of the specific BSS or RXCDR. The OMC X.121 DTE addresses are also propagated to the NE.MAP file located at $CM_CFG_GLOBAL on the System Processor.
Event and alarm subscription lists

When adding a new NE to the network (or making changes to an existing NE), alarm and event subscription lists must be created (or modified) for that NE. This ensures that event and alarm display windows can be assigned these subscription lists, to separately monitor the event/alarm messages from the new NE, in case of initial problems.

When a new NE is added to the GSM network, the OML from the NE must be connected to the OMC via the X.25 network. This requires the Packet switch / multiplexer to be re-configured for the new NE and the OML connected to it. Similarly, removing a NE from the network requires the Packet switch / multiplexer to be re-configured to remove the BSC/RXCDR from the X.25 network.
938
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
OMC - BSS remote login interface

Remote Login
Remote login enables the operator to have remote access to a Base Station system (BSS), or a Remote Transcoder (RXCDR). A list of nodes on the network that can be logged into remotely is displayed. Access to BSS MMI commands is provided via remote login from the OMC. An operator using the MMI at the OMC establishes a connection between the OMC and the BSS over which BSS MMI commands can be exchanged. The remote login interface is used for Configuration Management, Fault Management and Performance Management functions. The number of remote login sessions depends directly on the number of GPROCs equipped for that NE (up to a maximum of four). The OMC supports up to 20 remote login sessions to different NEs at any given time. Controlled system access is implemented by the use of two security levels, with a password assigned to each level. Security level 1 enables the operator to access a limited command set and allows monitoring of the system only. Security level 2 enables the full command set to be used and is intended for monitoring and administrative work on the system. On logging in to the system the operator is automatically assigned to security level 1. The remote login interface provides three methods by which MMI commands can be sent to the BSS: S S TTY. Batch (batch_rlogin).
Forms
In GSR4 Forms are available for displaying the circuit status for MMSs and channel status for RTFs from the navigation form.
EMOTOROLA LTD. 2000
939
ISSUE 18 REVISION 0
NE database upload
It is possible to perform a remote login to a NE during a database upload. In this case, a message is displayed stating that the remote login was successful, but that a database upload was in progress.
OMC PROCESSOR
RLOGIN SESSION
MMI
MMI PROCESSOR
Figure 9-21 OMC - BSS remote login Interface
940
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
TTY interface
The TTY interface provides a VT100 terminal emulation window for the entry of BSS MMI commands. This presents the operator with an interface to the BSS MMI almost identical to a locally attached TTY terminal at the BSS or RXCDR. BSS MMI commands can then be entered, and executed line by line.
Command line interface window

When the TTY option is selected from the remote login menu on the OMC console (or from the NSS maps), a command-line interface window is displayed on the operator terminal as shown at Figure 9-22. From this window any of the BSS MMI commands can be used to re-configure the operational characteristics of a BSS or RXCDR.
OMC MESSAGE LINE BSS MMI COMMAND NE RESPONSE LINE
OMC >
Login completed successfully > reset_site
Cust BSS MMI0115
Command accepted: WARNING, Site reboots now! Status = 0 OMC > logout indication received OMC > Press <RET> to close window
Figure 9-22 TTY interface Refer to Technical Description: BSS Command Reference (GSM-100-321) for a description of the BSS MMI commands. Refer to Operating Information: GSM System Operation (GSM-100-201) for a description of how to use the TTY Interface.

This facility uses a command file to execute a sequence of BSS MMI commands. The command file is a text file containing a sequence of BSS MMI commands, which can be sent to the BSS and executed at any convenient time. Batch is available both as a GUI and as a utility, batch_rlogin , which can be run from the UNIX command line. The batch_rlogin utility enables the operator at the OMC to execute multiple BSS MMI commands from a pre-edited file via a remote login connection to a NE (BSS or RXCDR). The batch_rlogin utility has a user interface which can be selected from the RLogin window. Alternatively it can be run as a Motorola utility, batch_rlogin , which can be run from the UNIX command line.
EMOTOROLA LTD. 2000
941
ISSUE 18 REVISION 0
The batch user interface

When the user clicks on the Batch button in the RLogin window a File Selection window opens (Figure 9-23), this allows the user to select, view, edit and run batch files. A template file is available to allow easy access to add BTS on line.
Figure 9-23 Batch File Selection Window
The logfile
The input file used is created within a UNIX shell with a standard text editor of the operators choice. It is accessible via the View/Edit button on the Batch File Selection window. The commands are read line by line from the input file. Command responses are directed to the output log file. Commands and comments issued from the input file are logged to the output file. Responses from the NE, via remote login, are also logged to the log file. The OMC administrator should have no difficulty in reading and understanding the log file. If a log file name is omitted at the command line, normal output and errors are redirected to the terminal screen from which the batch_rlogin is executed. For information on the batch_rlogin procedures, refer to Operating Information: GSM System Operation (GSM-100-201). For information on the batch_rlogin , refer to the OMC Online Help facility.
942
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Command line example 1

The following example performs a batch rlogin at a BSS named BSS_Cork, using a command file, BatchInput , and specifying a log file, BatchOutput : batch_rlogin BSS_CORK BatchInput BatchOutput The contents of the BatchInput file are:
#demonstration of batch facility
#command file disp_time state 0 OML 1 0 0 #end of commands
Command line example 2

This example shows the contents of the BatchOutput file, which was the log_file created when the BatchInput file shown in Figure 9-24 was used as the command file.
950925
09:45:11
Batch File Started
BatchRlogin : Login Completed Successfully Login completed successfully demonstration of batch facility BATCH CMD > NE RESPONSE > Cust BSS MMI0115 > #command file BATCH CMD > NE RESPONSE > Cust BSS MMI0115 > BATCH CMD > disp_time NE RESPONSE > Fri Sep 25 09:46:44 1995 Cust BSS MMI0115 > BATCH CMD > statE 0 OML 1 0 0 NE RESPONSE > STATUS INFORMATION : administration state : unlocked Operational state : busy Reason code is 0 Time of last transition : Thu Sep 24 17:12:48 1992 Other identification : 255 255 255 255 END OF STATUS REPORT Cust BSS MMI0115 > BATCH CMD > NE RESPONSE > Cust BSS MMI0115 > #end of commands
950925
09:45:15
Batch File Ended : SUCCESS Exit Code 0
Figure 9-24 Example of output to log file

EMOTOROLA LTD. 2000
943
ISSUE 18 REVISION 0
944
EMOTOROLA LTD. 2000
Chapter 10
Load Management
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
ii
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Chapter 10 Load Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Load management overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to Load management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of Downloading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software load information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Load management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selecting new software loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying upload/download status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling/disabling the download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling/ disabling downloads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing and removing software loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing a software load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing a software load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying NE database information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loading an NE database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NE database utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loading a database from tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loading a database from DataGen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loading a database from the off-line MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example of off-line MIB install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loading from a specified directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loading an existing database for CSFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating for normal /conventional download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating for CSFP download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downloading an NE database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conventional download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NE software detailed view form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete load flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conventional (live) downloading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking BSSspecific files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resetting a NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post-download checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Falling back to a previous live NE database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2000
i
101 101 101 102 103 103 104 104 104 105 106 107 107 107 108 108 108 1010 1011 1011 1011 1012 1013 1013 1013 1014 1015 1016 1018 1019 1020 1022 1022 1022 1024 1025 1025 1025 1026 1026 1026 1028 1028 1028 1029 1029 1030 1031
iii
ISSUE 18 REVISION 0
CSFP download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure CSFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downloading for CSFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Swapping a CSFP load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unconfigure CSFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CSFP Status form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Abort CSFP download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fallback to previous CSFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Aborting loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Aborting a bootload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uploading an NE database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uploading an object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Confirming compressed database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1032 1032 1032 1033 1034 1034 1035 1035 1036 1037 1037 1038 1038 1038 1040
iv
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Load management overview

Introduction to Load management
Load management involves the transfer of objects from the OMC to the NE (downloading) and from the NE to the OMC (uploading). NOTE A BSS software load consists of a number of objects (approximately 90). An object is a file containing binary code. One of these objects (001) is a list of all the other objects. Another one of these objects is the NE database (002) which contains the configuration parameters for the specific NE.
Overview of Downloading
Downloading can be performed in two ways: S S Conventionally the transfer of objects to the master GPROC at the NE. This transfer takes the NE out of service. CSFP the transfer of objects to a specially configured GPROC at the NE while the NE is operational. The objects can then be quickly swapped by resetting the NE, minimizing NE downtime.
As CSFP download is a background task, the process of downloading may take several hours, but service is not affected. Operators are required to install a database and/or software load onto the OMC. A database must then be activated for a specific NE. A software load must be associated with a specific NE before downloading and a database must also be associated.
EMOTOROLA LTD. 2000
101
ISSUE 18 REVISION 0
List of procedures
The following is the list of procedures that should be followed in the NE software and database conventional downloading process:
Install the NE software
Check NE is functioning correctly
Backup the currently active database using the Upload database procedure
Select new software load required and set the Complete Load flag using the NE Software detailed view form
Specify the correct database to be installed using the Load and Activate database procedures
In the Software Load Mgt. window ensure that the download flag is set for the NE
Use an xterm window to confirm that all necessary files exist in the NEs directory under BSSspecific and are correctly timestamped
Use MMI command to reset relevant NE in order to begin downloading operation
Check that download operation is successful using the Download Status window
Carry out device management procedures, such as lock and unlock RSLs, if necessary
Schedule an audit for the NE
Figure 10-1 NE software and database downloading
102
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Software load information
Software load information

Software Load management window
Select the Load Mgmt Icon to open the Software Load Management window (Figure 10-2). This window displays the software load information for the network. The entries in the window are displayed in alphabetical order and according to NE type with BSSs preceding RXCDRs.
Figure 10-2 Software Load Management window NOTE The default action for double clicking on an entry in the Software Load Management window is to invoke the NE Detailed View form. Multiple selection is available for all Edit functions, by holding down the CTRL key and selecting the menu element(s) with the left mouse button. Error boxes are displayed when an error is encountered. Only one error box is displayed for the case of multiple selection and details the NE(s) where the command failed. Refer to Online Help for a description of the fields in the Software Load Management window.
EMOTOROLA LTD. 2000
103
Software loads
ISSUE 18 REVISION 0
Software loads
Introduction
The Software Load Management window displays a list of current software loads installed for all NEs. Options are provided to enable and disable downloads.
Selecting new software loads

The New Software Load and New CSFP Software Load options are available from the Edit menu if a single, or multiple NEs (of one type only that is either BSSs or RXCDRs), are selected in the Software Load Management window. Selecting either of these options invokes the Software Inventory Dialog (Figure 10-3), from which the user may then choose a new software load or a new CSFP software load for the selected NE(s). 1. 2. Click on the Load Mgmt icon. The Software Load Management window is displayed. Select the required NE from the Software Load Management window listing (to select multiple NEs press and hold the CTRL key and select the required NEs with the left mouse button). Select Edit New Software Load or Edit New CSFP Software Load from the menu bar. The Software Inventory Dialog window is displayed (Figure 10-3).
3.
Figure 10-3 Software Inventory Dialog 4. 5. Double click the required software version from the list. A confirmation window is displayed. Click OK to continue. NOTE If a new database is to be downloaded, check it has been loaded and activated at the OMC, or uploaded from a test BSS.
104
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Software loads
Displaying upload/download status

To display the Download or Upload status of a NE use the following procedure: 1. 2. 3. 4. Click on the Load Mgmt icon. The Software Load Management window is displayed. Select the required NE from the Software Load Management window listing. Select Load Mgt Upload Status/Download Status as required. The Upload Status or Download Status window is displayed. Click Close to close the window.
Download Status window

The Download Status window displays the status of all conventional, CSFP, and supplemental downloads currently active in the system. Each download can involve the transfer of a number of software objects. The window is updated at frequent intervals. The maximum number of downloads (conventional, CSFP, and supplemental) allowed to operate concurrently is configurable, the default is 8. The maximum number of CSFP downloads allowed to operate concurrently can be configured, the default number is 4. When a conventional or supplemental download to a network entity is aborted, download is disabled for this network entity. As a result, the network entity will not be allowed to initiate software downloads from the OMC. An alarm is generated if a download is attempted. If a CSFP download to a network entity is aborted, download is not disabled for this network entity.
Upload Status window

The Upload Status window displays the status of all software uploads currently active in the system. Each software upload involves the transfer of only one software object. The window is updated at frequent intervals. The maximum number of uploads from a single network entity that can operate concurrently is 1. The maximum number of uploads to the OMC that can operate concurrently is, by default, 8.
Figure 10-4 Upload Status window

EMOTOROLA LTD. 2000
105
Software loads
ISSUE 18 REVISION 0
Refer to Online Help for a description of the fields in the Download and Upload Status windows.
106
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Enabling/disabling the download
Enabling/disabling the download

Introduction
Disabling of software download is a safety option to help ensure no unnecessary downloads are performed.
Enabling/ disabling downloads

The enabling/disabling of downloads can be configured on an individual NE basis. It is possible to select a single or multiple NEs and invoke the Download Enable or Disable option. 1. 2. 3. 4. 5. 6. At the Front Panel display click on the Load Mgmt icon. The Software Load Management window is displayed. Select the required NE(S). (Multiple NEs can be selected by holding down the CTRL button and selecting the NEs with the left mouse button). Select Edit Download Enable/Disable as required. Click OK in the confirmation window. Status is confirmed by an Enabled/Disabled status in the download column for each NE. Select File Close from the menu bar to exit.
EMOTOROLA LTD. 2000
107
Installing and removing software loads
ISSUE 18 REVISION 0

Introduction
New software loads are typically installed at the OMC from tape or CD. The software load is later downloaded to the relevant NEs under operator control.
Installing a software load

To install a BSS software load at the OMC, proceed as follows: 1. 2. 3. Insert the tape into the system processor cartridge tape drive and close the door. At the Front Panel display select the Load Mgmt icon, the Software Load Management window is displayed. Select Load Mgt Software Inventory from the menu bar. A Software Inventory Form is displayed, from which a list of current software loads can be viewed and new software loads can be installed (omcadmin users only). Select Options Install Load from the menu bar, the Install Load window is displayed (Figure 10-5).
4.
Figure 10-5 Install Load window 5. 6. In the Load Name field, enter the name assigned to the load being installed, for example, BSGSM1.4.0.1 or XRGSM1.3.0.0 for non-encrypted loads. In the Tape Device field, enter the name of the tape device from where the software load is installed (normally /dev/rmt/ctape0 or /dev/rmt/dtape0 or /dev/rmt/0). Alternatively, a tar file can be specified here. If installing from CD, enter the path to the tar file on the CD. 7. In the Host Name field, enter the name of the host processor from which to install. This may be anywhere on the LAN, default is omc_splat, the system processor. NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000
108
ISSUE 18 REVISION 0
8.
Select the correct load type from the Load Type list: valid values are BSS, RXCDR and BSS & RXCDR (if BSS & RXCDR is selected the software will be loaded as both BSS & RXCDR loads), click on the OK button. The following message is displayed in an Error box if a value for the Load Name field has not been entered:
Must Enter a Value in Load Field Name
The following message is displayed in an Error box if no entry has been made in the Tape Device Field.
Must Enter a Value in Tape Device Field
In the event of the install load operation failing the following message is displayed in an Error box:
Install Load Operation Failed
If the install load operation is successfully started the following message is displayed in an Information box:
Install Load Operation Started
The following message is displayed in an Information box on completion of the install load operation:
Install Load Operation Succeeded
NOTE This operation may take a few minutes. 9. Close the Software Load Management window, the Install Load window and the Software Inventory window.
EMOTOROLA LTD. 2000
109
ISSUE 18 REVISION 0
Removing a software load

To remove a NE software load from the OMC, login as omcadmin and proceed as follows: 1. 2. 3. At the Front Panel display select the Load Mgmt icon, the Software Load Management window is displayed. Select Load Mgt Software Inventory from the menu bar. A Software Inventory window is displayed, through which a list of current software loads can be viewed or deleted and new software loads installed. NOTE The files containing a software load are removed when the load is deleted. 4. Select the load to be removed, then select Options Remove Load from the menu bar. NOTE It is not possible to delete a software load if it is being used as a current or new software load for a NE. 5. The following message is displayed in the status bar if the user attempts to select Options Remove Load before selecting a software load instance to remove:
Must Select a Software Load Instance
6.
The confirmation dialogue box shown in Figure 10-6 is displayed on selection of the remove load operation.
Figure 10-6 Confirmation box 7. 8. If the correct load has been selected click OK. This closes the confirmation box. The following message is displayed in the status bar if the remove operation is a failure:
Error : Software Load In Use
9.
The following message is displayed in the status bar if the remove operation is a success:
Remove Load Operation Succeeded
10.
Close the Software Load Management window and the Software Inventory window. NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000
1010
ISSUE 18 REVISION 0
Displaying NE database information

Introduction
Use the database_info command to display information about the active, backup, pending and new databases stored on the OMC.
Procedure
Proceed as follows: 1. 2. Select the Load Mgmt icon on the Front Panel, the Software Load Management window opens. Select Database Mgt Database Information from the menu bar, an Xterm window opens with the following prompt displayed:
Enter NE name :
3.
Enter the name of the NE for which the database information is to be displayed. The following information for active, CSFP, and backup databases in $DBROOT/<NE_TYPE>/<NE_TYPE>Specific/<NE_name> , and newly loaded databases in $DBROOT/databases/<NE_name> (known as pending / new databases) is displayed as follows:
Directory Name (CSFP, backup and pending databases only : Code Object Number: Code Object Name: Creation Time/Date: Database Level Number: Checksum: Size: User Comment:
EMOTOROLA LTD. 2000
1011
ISSUE 18 REVISION 0
Example
The following example shows the screen output when database_info is used to query the databases attached to the Cork NE. Operator input is given in a bold typeface.
Enter NE name :
Cork
Active Database: Code object number : 0x02 Code object name : dbase Creation time/date : 15:08 23 03 1998 Database Level No : 0x0000 0x003c Checksum : 0x0024a3c4 Size : 0x00012d32 User Comment : March 23 1997, neighbour 026 added Backup Database: Directory Name : [/usr/gsm/ne_data/dbroot/BSS/BSSspecific/Cork1/ db940612123455] Code object number : 0x02 Code object name : dbase Creation time/date : 15:08 23 03 1998 Database Level No : 0x0000 0x003c Checksum : 0x0024a3c4 Size : 0x00012d32 User Comment : March 23 1997,DRIs in Site02/Cell04 modified CSFP Database(s): Directory Name : /usr/gsm/ne_data/dbroot/BSS/BSSspecific/Cork1/ db940612123444 Code object number : 0x02 Code object name : dbase Creation time/date : 48:48 48 48 4800 Database Level No : 0x0000 0x003c Checksum : 0x0381193d Size : 0x00269e98 Pending/New Database(s): Directory Name : /usr/gsm/ne_data/dbroot/BSS/BSSspecific/Cork1/ db940612123444 Code object number : 0x02 Code object name : dbase] Creation time/date : 48:48 48 48 4800 Database Level No : 0x0000 0x003c Checksum : 0x0381193d Size : 0x00269e98 User Comment : March 23 1997 Press return to exit.....
1012
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Loading an NE database
Introduction
NE databases can be installed to the OMC from: S S S S S S Tape. CD-ROM. DataGen. Off-Line MIB. A user specified location. An existing database for CSFP.
NE database utilities
The NE database load management utilities can be accessed from the Database Mgt menu (Figure 10-7) in the Software Load Management window. The utilities are as follows: 1. 2. 3. 4. Load Database. This utility uses the load_db command to enable newly created databases to be loaded from tape, DataGen, CD-ROM, or a user definable source. Activate Database. This utility uses the activate_db command to select the relevant database to become the active database for a particular NE. Fallback Database. This utility uses the fallback_db command to return to a previous live database. Database Information. This utility uses the database_info command to display information of all active, backup, and newly loaded databases for any NE.
Figure 10-7 Software Load Management window displaying Database Mgt menu
EMOTOROLA LTD. 2000
1013
ISSUE 18 REVISION 0
Loading a database from tape

The following procedure describes how to load a NE database onto the OMC from a tape using an MMI/GUI terminal: 1. 2. 3. 4. Insert the tape containing the database(s) into the tape drive of the system processor. Select the Load Mgmt icon from the Front Panel, the Software Load Management window opens. Select Database Mgt Load Database from the menu bar, an xterm window opens. The following prompt is displayed:
1=Tape/Disk Drive. 2=Datagen. 3=OffLine MIB 4=User definable host and location. Enter database source(14) : <1>
5.
Select Tape/Disk Drive as the database source by entering 1. The following message is displayed:
1=Cartridge Tape Drive 2=DAT Drive 3=Floppy Disk Drive 4=CD-ROM Drive Enter database source(14) :
6.
The following message is displayed:

Enter the name of the host machine:
Enter the host machine name. 7. If there is a disk space problem, the following message is displayed:
/usr/gsm/current/bin/load_db: Insufficient disk space Need at least 10 MB of free space on ne_data partition
Contact the OMC system administrator to carry out maintenance on the ne_data partition and try again. 8. In the event of there being no tape in the drive the following message is displayed:
Error Accessing tape/floppy check tape/floppy and active. Script exiting.
9.
If more than one database exists on the tape, the following is displayed:
1 = < database name 1 > 2 = < database name 2 > * = .......... n = < database name n > Enter the database you require ? (1 n) : or A to load all databases :<A>
10.
Select the required database by entering the appropriate character. If an invalid selection is entered, a message is displayed detailing the valid range and giving the option of entering a new value. If the database selection is valid then the tape rewinds if necessary and the following is displayed:
Database to be loaded is database#1 Enter NE associated with database database#1:<NE_name>
11.
1014
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
12.
Enter the NE name, the following message is displayed:

Rewinding the tape ... Getting database ... Enter a comment string of max size 200 characters:<comment string>
13.
Enter a comment string if appropriate. The following messages are displayed:

Database file is in uncompressed format Converting database#1 into OMC format What name do you want for this dbload? ( database#1 ):<dbload name>
14.
Enter the appropriate load name. The database directory is created and the following message is displayed:
making directory /usr/gsm/ne_data/dbroot/databases/<NE_name>/<dbload name>...
15.
The procedure terminates successfully with the following message:

You will find your database in /usr/gsm/ne_data/dbroot/databases/<NE_name>/<dbload name> Do you want to activate this database?
16. 17.
The database can be activated by entering y, refer to the procedure Activating the database. Enter n if the database is not to be activated. If A had been selected in Step 9 and there are more databases to be loaded, then the procedure returns to Step 11, otherwise the following prompt is displayed:
Do you want to load another database? (y/n) :
18.
If another database is to be loaded enter y and return to Step 9, otherwise enter n and the following message is displayed:
Exiting out of ./load_db script
19.
Press CR to exit.
Loading a database from DataGen

The following procedure describes how to load an NE database onto the OMC from DataGen using an MMI/GUI terminal: 1. 2. 3. Select the Load Mgmt icon from the Front Panel, the Software Load Management window is displayed. Select Database Mgt Load Database from the menu bar, an xterm window opens. The following message is displayed:
1=Tape/Disk Drive. 2=Datagen. 3=OffLine MIB 4=User definable host and location. Enter database source(14) : 2
4.
Select DataGen as the database source by entering 2. The following message is displayed:
Enter NE associated with database : <NE_name>
5.
Enter the NE name, the following prompt is displayed:

1 = database#1 2 = database#2 If you want to load all databases enter A Enter the database you require ? (1 n) or A to load all databases :<1>
EMOTOROLA LTD. 2000
1015
ISSUE 18 REVISION 0
6.
If an invalid selection is made the prompt above is repeated until a valid entry is made, the following message is then displayed:
Database to be loaded is database#1 Getting database ...
7. 8.
When the database has been loaded the following prompt is displayed:
Enter comment string : <comment string>
Enter a comment string if appropriate, otherwise press CR. The following prompts are displayed:
Converting database#1 into OMC format What name do you want for this dbload? <dbload name>
9.
Enter the appropriate load name. The database directory is created and the following messages are displayed:
making directory /usr/gsm/ne_data/dbroot/databases/<NE_name>/<dbload name>... You will find your database in /usr/gsm/ne_data/dbroot/databases/<NE_name>/<dbload name> Do you want to activate this database?
10. 11.
Enter n if the database is not to be activated. If the option A had been selected in Step 5 and there are more databases to be loaded then the procedure returns to Step 6, otherwise the following prompt is displayed:
Enter the database you require (1N) or A to load all databases.
12.
Loading a database from the off-line MIB

The following procedure describes how to load an NE database onto the OMC from the Off-Line MIB using an MMI/GUI terminal: 1. 2. 3. Select the Load Mgmt icon from the Front Panel, the Software Load Management window is displayed. Select Database Mgt Load Database from the menu bar, an xterm window opens. The following message is displayed:
4.
Select Off-Line MIB as the database source by entering 3. The following message is displayed:
Enter the name of the host machine : <host_name>
5.
Enter the host machine name, the following message is displayed:

Contacting <host_name> ... database#1 database#2 database#3 database#4 Enter Network associated with database from OffLine MIB : <network_name>
1016
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
6.
Enter the network name, the following message is displayed:

Enter NE associated with database omc_db : <NE_name>
7.

Getting database ...
8.
When the database has been loaded the following prompt is displayed:
Enter comment string of max size 200 characters: <comment string>
9.
Converting database#1 into OMC format What name do you want for this dbload? <dbload name>
10.
Enter the appropriate load name. The database directory is created and the following messages are displayed:
making directory /usr/gsm/ne_data/dbroot/databases/<NE_name>/<dbload name>... You will find your database in /usr/gsm/ne_data/dbroot/databases/<NE_name>/<dbload name> Do you want to activate this database?
11.
The database can be activated by entering y, refer to the procedure Activating the database. Enter n if the database is not to be activated, the following message is displayed:
12.
EMOTOROLA LTD. 2000
1017
ISSUE 18 REVISION 0
Example of off-line MIB install

The following example shows the screen output during the execution of load_db to load a database from a the Off-Line MIB and store its database object file and database.list file in a directory. Operator input is given in a bold typeface.
1=Tape/Disk Drive. 2=Datagen. 3=OffLine MIB 4=User definable host and location. Enter database source(14) : 3 Error: OffLine MIB host variable (OLMHOST) not set. Enter correct host variable now Enter the name of the host machine : martins_datagen Contacting martins_datagen ... Cork Dublin1 Dublin2 Dublin3 Enter Network associated with database from OffLine MIB : Cork Enter NE associated with database omc_db : CorkBSS1 Getting database ... Enter a comment string of max size 200 characters : This is a demo. Checked database format. Converting CorkBSS1.002 into OMC format. What name do you want for this dbload? ( CorkBSS1.002 ) : martin.002 making directory /usr/gsm/ne_data/dbroot/databases/CorkBSS1/martin.002.... You will find your database in /usr/gsm/ne_data/dbroot/databases/CorkBSS1/martin.002 Do you want to activate this database? y 1=Active directory. 2=CSFP directory. Enter database destination(12) : 2 A database exists in /usr/gsm/ne_data/dbroot/BSS/BSSspecific/CorkBSS1/CSFP. It will be overwritten. Do you want to proceed anyway? (y,n) : y Proceeding to overwrite database in CorkBSS1/CSFP. martin.002 is now active for CorkBSS1/CSFP removing /usr/gsm/ne_data/dbroot/databases/CorkBSS1/martin.002 ..... activate_db script exiting Do you want to load another database? (y/n) : n Exiting out of ./load_db script Press RETURN to exit...
1018
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Loading from a specified directory

The following procedure describes how to load an NE database onto the OMC from a file using an MMI/GUI terminal: 1. 2. 3. Select the Load Mgmt icon from the Front Panel, the Software Load Management window opens. Select Database Mgt Load Database from the menu bar, an xterm window opens. The following message is displayed:
4.
Select User definable host and location as the database source by entering 4.The following prompt is displayed:
Enter the name of the host machine: <host machine name>
5.
Enter the host machine name (where the database is located), the following prompt is displayed:
Enter the full directory path for the database directory on <host machine name>
6.
Enter the full directory path, if more than one database exits, the following message is displayed:
1 = <database#1> 2 = <database#2> Enter the Database that you require (1N) or A to load all databases.
7.
Select the required database by entering the appropriate number. A prompt is displayed for the NE associated with the database:
Enter NE associated with database database#1: <NE_name>
8.

Getting database ... Enter comment string of max size 200 characters:
9.
Database file is in uncompressed format Converting database#1 into OMC format What name do you want for this dbload? (database#1):<dbload name>
10.
making directory /usr/gsm/ne_data/dbroot/databases/<NE_name>/<dbload name>....
11.

You will find your database in /usr/gsm/ne_data/dbroot/databases/<NE_name>/<dbload name> Do you want to activate this database?
12.
The database can be activated by entering y, refer to the procedure Activating the database. Enter n if the database is not to be activated, the following message is displayed:
EMOTOROLA LTD. 2000
1019
ISSUE 18 REVISION 0
13.
Exiting out of ./load_db script Press return to exit
14.
Press CR to exit.
Loading an existing database for CSFP

The following procedure describes how to load an existing database from the active directory so that it can be made the active CSFP database. 1. 2. 3. Select the Load Mgmt icon from the Front Panel, the Software Load Management window opens. Select Database Mgt Load Database from the menu bar, an xterm window opens. The following message is displayed:
4.
Select User definable host and location as the database source by entering 4. The following prompt is displayed:
Enter the name of the host machine. <host machine name>
5.
Enter the host machine name (where the database is located), the following prompt is displayed
Enter the full directory path for the database directory on <host machine name> $dbroot/bss/bssspecific/<bssname>.
6.
If more than one database exits on this path, the following message is displayed:
1 = <database#1> 2 = <database#2> Enter the Database that you require (1N) or A to load all databases.
7.
Select the required database by entering the appropriate number. A prompt is displayed for the NE associated with the database:
Enter NE associated with database database#1: <NE_name>
8.

Getting database ... Enter comment string of max size 200 characters:
9.
Database file is in uncompressed format Converting database#1 into OMC format What name do you want for this dbload? (database#1):<dbload name>
10.
making directory /usr/gsm/ne_data/dbroot/databases/<NE_name>/<dbload name>....
1020
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
11.

You will find your database in /usr/gsm/ne_data/dbroot/databases/<NE_name>/<dbload name> Do you want to load another database? (y/n) :
12.
Exiting out of ./load_db script Press return to exit
13.
Press CR to exit.
To activate the database for CSFP refer to the Activating for CSFP download procedure.
EMOTOROLA LTD. 2000
1021
Activating the database
ISSUE 18 REVISION 0

Introduction
Before downloading, and after installation, all databases need to be activated. This can be done in two ways, depending on whether the database is for: S S Normal/conventional download. CSFP download.
Activating for normal /conventional download

The following procedure describes how to make a selected database the active database for a specified NE. 1. 2. Select the Load Mgmt icon from the Front Panel, the Software Load Management window opens. Select Database Mgt Activate Database option from the menu bar. The following message is displayed:
Which NE does this database belong to?:
3.
Enter the name of the appropriate BSS or RXCDR. The following message is displayed:
1=Active directory 2=CSFP directory Enter database destination (12) :
4.
Enter 1 for an active directory. A list of the database loads in $DBROOT/databases/<NE_name> is displayed in the following format:
1 = < db_load name 1 > 2 = < db_load name 2 > * = .......... n = < db_load name n > Which database load do you want ? (1 n) :
In the event of an incorrect selection being made the following message is displayed:
activate_db: Error selecting database load Enter choice in range (1 to n).
5.
Enter the appropriate number (1 to <n>) corresponding to the db load name used when loading the database, and press CR. The following message is displayed:
Checking backup for <NE Name>, please wait
1022
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
6.
The previous message indicates that a check is being made on whether the current live database has been backed up. Each backup database is uncompressed, compared to the active database and recompressed. If a uncompression/recompression of any backup database fails, the following message is displayed:
Error: Unable to un(re)compress a backup database load Unable to check if this is a backup.
If the current live database has not been backed up, the following message is displayed:
No backup found Active database is not backed up.
A backup of the old (live) database is created and the current active database is overwritten. The following message is displayed:
Backing up active database before proceeding.
7.
On successful completion, the following messages are displayed:

<db_loadname n> is now active for <NE_name> removing /usr/gsm/ne_data/dbroot/databases/<NE_name>/<db_loadname n> Press RETURN to exit
8. 9.
The $DBROOT/databases directory now no longer contains the database selected in Step 4. If activation is unsuccessful, the following message is displayed:
copy of <directory> contents to new location failed
EMOTOROLA LTD. 2000
1023
ISSUE 18 REVISION 0
Activating for CSFP download

The following procedure describes how to make a selected database the active CSFP database directory for a specified NE so that the database can be downloaded via a CSFP download: 1. 2. Select the Load Mgmt icon from the Front Panel, the Software Load Management window opens. Select Database Mgt Activate Database option from the menu bar. The following message is displayed:
Which NE does this database belong to?
3.
Enter the name of the appropriate BSS or RXCDR. The following message is displayed:
1=Active directory 2=CSFP directory Enter database destination (12) :
4.
Enter 2 for a CSFP directory. A list of the database loads in $DBROOT/databases/<NE_name> is displayed in the following format:
1 = < database name 1 > 2 = < database name 2 > * = .......... n = < database name n > Which database load do you want ? (1 n) :
5.
Enter the appropriate number (1 to n) corresponding to the db load name which was used when loading the database, and press CR. The following message is displayed:
<db_loadname n> is now active for <NE_name>/CSFP removing /usr/gsm/ne_data/dbroot/databases/<db_loadname n>.... Press return to exit.
6. 7.
The $DBROOT/databases/<NE_name> directory now no longer contains the directory containing the database selected in Step 4. If the download is unsuccessful, the following message is displayed:
copy of <directory> contents to new location failed
1024
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Downloading an NE database
Downloading an NE database
Introduction
Load management downloading can be performed in two ways: S S Conventionally the transfer of objects to the master GPROC at the NE. This transfer takes the NE out of service. Code Storage Facility Processor (CSFP) the transfer of objects to a specifically configured GPROC at the NE while the NE is operational. The objects can then be swapped quickly by resetting the NE, thus minimizing NE downtime. As CSFP download is a background task, service is not affected.
Prerequisites
Before carrying out the download procedure ensure that the NE database has been backed up using the Uploading an NE database procedure. Prior to downloading an NE database, audit the BSS as described in Chapter 6 of this manual, and ensure that all sites and Transceiver units are up and that CSFP GPROCs are configured.
EMOTOROLA LTD. 2000
1025
Conventional download
ISSUE 18 REVISION 0
Introduction
Conventional downloading consists of the transfer of objects, including a database, from the OMC to the master GPROC at the NE. This transfer takes the NE out of service. Use the following steps in carrying out a conventional download: S S S S S S S S S Check the NE is functioning correctly. Upload the existing database. Complete the NE Software Detailed View form and ensure that the Download flag is enabled. Select the correct database for the download operation. Check the relevant directory, under BSSspecific, to ensure that all files are correctly set up. Reset the NE. Check the status of the download operation and view events. When successfully completed, check all BTSs and logical links are operational. Schedule an audit for the NE.
NE software detailed view form

Every network element in the system has a unique NE Software detailed view form. This form displays information about the software associated with the NE. By editing the detailed view form, the operator can change the load to be used for either conventional or CSFP downloading. The NE Software detailed view form can be invoked for a BSS or RXCDR by selecting Load Mgt NE Software from the Navigation Form. See Figure 10-8.
1026
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Figure 10-8 NE Software detailed view form The Current Software flag identifies the software load that is currently running on the NE. A prompt window is displayed should this field be empty, for example, if a NE is about to be installed. An entry is obtained by performing the Audit procedure. The New Software flag identifies the software load to be downloaded on the next reset. The Complete Load flag can be used to identify whether the NE is running the correct software code objects. It is also used to determine whether only a database download is required. Refer to the Complete load flag section.
EMOTOROLA LTD. 2000
1027
ISSUE 18 REVISION 0
Complete load flag

To set the Complete Load flag use the following procedure: 1. 2. 3. Select the Load Mgmt icon from the Front Panel, the Software Load Management window opens. For a NE database download select Edit Complete Load Disable. For a complete download select Edit Complete Load Enable.
Disable
This is the default setting. When the NE resets, the OMC sends the level number of the database currently installed at the OMC applicable to this NE. If the database level is different, a database download occurs. Missing or corrupt code objects are downloaded. The Complete Load flag should be set to Disable in order to perform a conventional download of a new database code object only.
Enable
When the Complete Load flag is set to Enable, and the NE resets, it requests a list of all the software code objects it should be running. The OMC sends a list of the objects and the NE compares this list against its installed load (if any). Should a discrepancy exist the NE then requests the OMC to download any missing or different objects. The Complete Load flag should be set to Enable in order to perform a conventional download of a new software code object release.
Conventional (live) downloading

To download a live NE database use the following procedure: 1. 2. 3. 4. 5. At the Front Panel select the Load Mgmt icon. The Software Load Management window is displayed. Select the required network element. Select Edit New Software Load from the menu bar, the Software Inventory Dialog window opens. Double-click on the software to be downloaded, a confirmation window opens. Click OK. The new software load is displayed in the New Software Load column in the Software Load Management window.
Checking BSSspecific files

Before the download process can be activated, all the relevant files must be present in the NE software directory structure. Use the following UNIX commands to check that correctly timestamped relevant files exist in each unique NE directory: cd $DBROOT/BSS/BSSspecific/NEname ls lai The creation date of all the files, except download.list , must be identical.
1028
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Resetting a NE
Use the following procedure to reset an NE: 1. 2. Select the required Network Element from the Load Management window. Select Bootload Reset NE. The following window, Figure 10-9, is displayed.
Figure 10-9 Reset NE confirmation window 3. Click OK to continue. The result of the operation is shown in the status bar of the Software Load Management window.
Post-download checks
When the NE software has been successfully downloaded to the Master GPROC on the BSC, the status of each BTS and each RSL can be checked (refer to Checking device status from the navigation tree in Chapter 2). BTSs or RSLs may need to be locked or unlocked in order to complete successful installation of the whole BSS structure. Finally, an audit should be scheduled for the NE (refer to Scheduling an audit in Chapter 6) and the OOS Devices window should be opened to check that no devices remain out of service (refer to Displaying OOS devices from the navigation tree in Chapter 2).
EMOTOROLA LTD. 2000
1029
ISSUE 18 REVISION 0
Falling back to a previous live NE database

If there is a problem with a new NE database, and CPS has been equipped, it is possible to fall back to a previous NE database. The fallback procedure is as follows: 1. 2. At the Front Panel display select the Load Mgmt icon. The Software Load Management window is displayed. Select Database Mgt Fallback Database from the menu bar. The following prompt is displayed:
Enter NE name : <NE_name>
If an invalid NE name is entered the following message and prompt are displayed:
NE_name is not a valid name Enter NE name : <NE_name>
3.
Enter the name of the NE for which a fall back to a previous database is to be performed. The system responds by displaying the database information of the backup database(s) for that NE:
Backup Database(s) for NE :<NE_name> Directory Name : [/usr/gsm/ne_data/dbroot/<NE_type>/<NE_type>specific/<NE_name>/db<YYYYMMDDHH MMSS>] Code object number : 0x02 Code object name : Database Creation time/date : 15:08 23 03 1998 Database Level No : 0x0000 0x003c Checksum : 0x0024a3c4 Size : 0x00012d32 User Comment : March 23 1998,DRIs in
4.
If there is more than one backup database a choice is required.

Are you sure you want to proceed with the fallback? Type Yes to proceed, anything else will abort operation :
If anything other than yes is entered the following is displayed:

Operation aborted. Press return to exit
5.
Enter Yes, the following message is displayed:

Checking backup for <NE_name>, please wait /usr/gsm/ne_data/dbroot/<NE_name>/<NE_name>specific/Cork/db<YYYYMMDDHHMMSS> is now active for <NE_name> Press return to exit
If the active database is not backed up the following message is displayed:

Checking backup for <NE_name>, please wait No backup found Active database is not backed up. Backing up active database before proceeding. db<YYYYMMDDHHMMSS> is now active for <NE_name> Press return to exit
1030
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Example
The following example shows the screen output when fallback_db is used to fallback to a previous database attached to the Cork NE. Operator input is given in bold typeface.
Enter NE name :
Cork
Backup Database(s) for NE : Cork Directory Name : [/usr/gsm/ne_data/dbroot/<NE_name>/<NE_name>specific/Cork/db950331164] Code object number : 0x02 Code object name : Database Creation time/date : 15:08 23 03 1998 Database Level No : 0x0000 0x003c Checksum : 0x0024a3c4 Size : 0x00012d32 User Comment : March 23 1998,DRIs in Are you sure you want to proceed with the fallback? Type Yes to proceed, anything else will abort operation : Yes db950331164 is now active for Cork
EMOTOROLA LTD. 2000
1031
CSFP download
ISSUE 18 REVISION 0
CSFP download
Introduction
The CSFP is a GPROC device which allows the transfer (download) of objects from the OMC to a specifically configured GPROC at the NE, while the NE is operational. The objects can then be swapped quickly by resetting the NE, thus minimizing NE downtime. Procedures involved with the CSFP feature are as follows: S S S S S Configure CSFP. CSFP download operation. Swap code object software. Unconfigure CSFP. Display status of CSFP download.
Configure CSFP
Before commencing a CSFP download, a second GPROC must be configured as a CSFP GPROC to accept the download. After a successful swap, CSFPs may be unconfigured and restored to their pre-configured functionality. The Configure CSFP option sends a request to the parent NE to configure a CSFP device at each of its SITEs. A confirmation box opens requesting confirmation of the operation. The NE scans its SITEs, selects at most one GPROC on each SITE, and equips that GPROC as a CSFP device. With M-Cell there can now be two CSFP devices at site 0, device 0 and 1. These can now be configured. The progress of the operation can be monitored on the CSFP Status form. Refer to CSFP Status form. The result of this operation is displayed on the status bar of the NE Detailed View form. In the Software Load Management window, select Load Mgt NE Detailed View to open the NE Detailed View form. The operation is considered successful if the SITE_0 CSFP device is configured at the BSC or RXCDR. Either CSFP device configuring makes the operation successful. To configure a CSFP use the following procedure: 1. 2. 3. 4. From the Front Panel select the Load Mgmt icon. The Software Load Management window opens. Select the required NE from the listing. Select CSFP Configure CSFP. A confirmation window is displayed (Figure 10-10). Click OK to continue.
Figure 10-10 CSFP confirmation

1032
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
CSFP download
Downloading for CSFP

To download a CSFP use the following procedure: 1. 2. 3. 4. 5. 6. Check the status of the NE to ensure there are no faults before the new CSFP database is loaded. Select the Load Mgmt icon from the Front Panel. The Software Load Management window is displayed. Select the required NE from the Software Load Management window listing. Select Edit Complete Load Enable from the menu bar. Select Edit New CSFP Software Load from the menu bar. The Software Inventory Dialog window opens. Double click on the required load version from the listing. A confirmation window is displayed, Figure 10-11.
Figure 10-11 CSFP confirmation window 7. 8. 9. 10. 11. On the confirmation window click OK to proceed. If a new CSFP database is to be downloaded, check it has been loaded and activated at the OMC, or uploaded from a test BSS. Select CSFP Download CSFP. A confirmation window is displayed. On the confirmation window click OK to proceed. The result of the process is displayed on the status bar of the Software Load Management window. Open an Event window to monitor the success or failure of events.
EMOTOROLA LTD. 2000
1033
CSFP download
ISSUE 18 REVISION 0
Swapping a CSFP load

CAUTION This swapover causes a fast reset of the NE. After the load has been downloaded to the BSS, a swapover may be performed. To perform a CSFP load swap, carry out the following procedure: 1. 2. 3. Select the Load Mgmt icon from the Front Panel. The Software Load Management window opens. Select CSFP Swap CodeLoad, all SITEs in the NE reset (that is, the current CSFP Load becomes the new CSFP load). If the current CSFP Load has not been set, then the following message is displayed in the status bar of the NE Software window:
Cannot perform Swap CSFP Operation Current CSFP Load Not Set
4. 5. 6.
Click on the Confirm button, a confirmation box is displayed. If the load name and version number to be swapped to are correct then click on the confirm button. If any CSFPs have not been downloaded then the following message is displayed:
Swap CSFP CodeLoad ?
Click on the Confirm button. One of the following warning messages may be displayed:
Warning: At least one BTS CSFP is not code loaded. Warning: OMC CSFP db level numbers dont match and at least one BTS CSFP is not code loaded. Warning: BSC and OMC current db level numbers dont match.
7. 8. 9.
The following message is displayed:

Do you really want to swap CSFP CodeLoads?
Click on the Confirm button, a confirmation box is displayed. Clicking No aborts the operation. If the Swap CodeLoad command fails, the operation is terminated and the following error message is displayed in the status bar of the form:
Swap CodeLoad Failed.....
10.
If the Swap CodeLoad command is successful the complete load flag is set to true and the following message is displayed in the status bar of the form:
Current Software Attribute has changed
NOTE The CSFP device at the BSC must be in a Busy/Unlocked state with reason code No Reason for the Swap CodeLoad command to be accepted.
Unconfigure CSFP
The Unconfigure CSFP option sends a request to the parent NE to restore all CSFP devices to their pre-configured state. The progress of the operation can be monitored on the CSFP Status form. NOTE If the BSC is M-Cell / New-Gen site, it will not unconfigure.
1034
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
CSFP download
CSFP Status form

The CSFP Status form displays the status of the CSFP devices at the network entity identified on the status bar of the form. This form is used to monitor the progress of CSFP related commands. The form is updated dynamically to reflect state changes that occur at the CSFP devices. These devices change state when CSFP related commands are in progress and when the commands complete. Each line entry represents a specific CSFP device and contains the following information: S S S S 1. 2. Site name. Operational state. Administrative state. Reason code. Select the Load Mgmt icon from the Front Panel. The Software Load Management window is displayed. Select CSFP CSFP Status from the menu bar, the CSFP Status form is displayed.
To display the status of a CSFP use the following procedure:
Figure 10-12 CSFP Status form
Abort CSFP download

To abort a CSFP download that is in progress use the following procedure: 1. 2. 3. Select the required Network Element in the Software Load Management window listing. Select CSFP Abort CSFP Download. A confirmation box is displayed. Click OK to continue. The result of the operation is displayed in the status bar of the Software Load Management window. The progress of the operation can be monitored on the CSFP Status form.
The software downloaded before the Abort command was issued remains at the SITE. If a CSFP download command is issued after an Abort, and the CSFP load to be transferred has not been changed, the new download command completes the original operation. It downloads software not already at the SITE.
EMOTOROLA LTD. 2000
1035
CSFP download
ISSUE 18 REVISION 0
Fallback to previous CSFP

CAUTION When the original CSFP swap was performed, the new database must have a CSFP equipped. If not, the old load would have been lost, and therefore unable to be used for fallback. Where a problem occurs with a CSFP load, it is possible to revert to the previous load. Fallback to a previous CSFP software load as follows: 1. 2. 3. 4. Click on the Load Mgmt icon on the Front Panel, the Software Load Management window opens. Select the required BSS or RXCDR. Select CSFP Swap Code Load. All SITEs in the NE reset, such that the current CSFP load becomes the new CSFP load. If the current CSFP load has not been set then the following message is displayed in the status bar of the Software Load Management window:
Unable to perform Swap Code Load. Current CSFP Load Not Set.
NOTE Refer to the Downloading for CSFP procedure to set the current CSFP load. 5. If any CSFPs have not been downloaded then a message similar to the following is displayed:
Swap CSFP Code Load?
6. 7.
Click on OK, a confirmation box is displayed, if the load name and version number to be swapped to are correct then click on OK. If the Swap Code Load command fails, the operation is terminated and an error message similar to the following is displayed in the status bar of the form:
Swap Code Load Failed.....
8.
If the Swap Code Load command is successful, the forced flag is set to true and the following message is displayed in the status bar of the window:
Current Software Attribute has changed
9. 10. 11.
In the Software Load Management window select File Save, a confirmation box is displayed. Click on OK, this saves the swap. Exit the Software Load Management window by selecting File Close.
1036
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Aborting loads
Aborting loads
Aborting a bootload
NOTE When an Abort Bootload command is issued, download is disabled for this network entity. As a result, the network entity will not be allowed to initiate software downloads from the OMC. To Abort a bootload (conventional download) that is in progress at the network entity use the following procedure: 1. 2. Select the required Network Element from the Software Load Management window. Select Bootload Abort Bootload. The Confirmation window Figure 10-13, is displayed.
Figure 10-13 Abort Load confirmation window 3. Click OK to continue. The result of the operation is displayed in the status bar of the Software Load Management window.
EMOTOROLA LTD. 2000
1037
Uploading an NE database
ISSUE 18 REVISION 0
Introduction
An upload must be performed each time there are changes to the database at the NE and also prior to a software download. The changes may have been performed locally or from the OMC.
Uploading an object
The Upload form allows you to upload database objects and software objects from a BSS or RXCDR network entity. The upload operation is not available to read-only users of the OMC. Information on uploads currently active in the system can be viewed in the Upload Status window. To upload a BSS or RXCDR network entity use the following procedure: 1. 2. Select a network entity from the Software Load Management window. Select Load Mgt Upload Object from the menu bar. The Upload Object form is displayed, Figure 10-14.
Figure 10-14 Upload Object form 3. Enter a comment in the Comment field (the comment should relate any information that may be useful for future interpretation). NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000
1038
ISSUE 18 REVISION 0
4. 5.
Click OK to continue, a confirmation window is displayed. Select Load Mgt Upload Status from the Software Load Management window, to open the Upload Status window (Figure 10-15). The status of the upload can be monitored in the Upload Status window. When the upload is complete, close the Upload Status window, and continue with compression confirmation procedure.
6.
Figure 10-15 Upload Status window
EMOTOROLA LTD. 2000
1039
ISSUE 18 REVISION 0
Confirming compressed database

When a database is uploaded from a NE, it is placed in the active directory of the NE, and the previously active database is relocated to a subdirectory named db<YYYYMMDDHHMMSS> , where <YYYYMMDDHHMMSS> refers to the date and time the upload was performed. Confirm that the previously active database is compressed as follows: 1. 2. At the Front Panel display click the Xterm icon to open a shell. Enter the following command to change to the appropriate directory: cd $DBROOT/BSS/BSSspecific or cd $DBROOT/RXCDR/RXCDRspecific 3. Use the following command to change to the appropriate BSS (or RXCDR) directory: cd <NE_name> 4. Check that the database has been compressed, that is the filename has a .Z extension. The database is be located within a sub-directory of Bnn BSSname, named db<YYYYMMDDHHMMSS> , where <YYYYMMDDHHMMSS> refers to the date and time that the upload was performed. Confirm that this subdirectory contains the required dBComment , database and database.list files. Check the subdirectory to confirm the backed up database is compressed (has a .Z extension). If two archived copies of the database exist, the oldest version should be archived to tape and deleted from the OMC by the OMC system administrator. 5. Enter details of the upload into the OMC log book specifying the reason for the upload, the directory it is backed up to, and the time and date.
1040
EMOTOROLA LTD. 2000
Chapter 11
Administration Procedures
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
ii
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Chapter 11 Administration Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Administration: overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM scheduled reports and logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening a user profile list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing a user profile list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing a user profile detailed view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing the user profile list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview and recommendations for audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to audit function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of audit procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audit functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended audit use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduled audits queuing support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Number of operations run at a given time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audit scenarios and NE basis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audit logs and expired logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Auditing a network via the navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to auditing a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Auditing a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Auditing a BSS/RXCDR via the navigation tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to BSS/RXCDR auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Auditing a BSS/RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling an audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a scheduled audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying a scheduled audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing a list of scheduled audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a scheduled audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing audit logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing an audit log list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing an audit log list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Aborting an audit in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing an audit inconsistency report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing an inconsistency report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating database with inconsistencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting audit logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling an FM resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction FM resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a scheduled resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying a scheduled resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing resync schedule list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a scheduled resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2000
i
111 111 111 112 112 112 113 114 115 115 116 116 116 117 118 119 119 1110 1110 1111 1111 1112 1114 1114 1114 1115 1115 1116 1120 1121 1121 1122 1122 1123 1123 1125 1126 1126 1127 1129 1129 1129 1129 1130 1134 1136 1136
iii
ISSUE 18 REVISION 0
Resynchronizing logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing a resync log list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing a resync log list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Aborting a resync in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resync report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing a resync report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing a resync report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a resync log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1137 1137 1137 1138 1139 1139 1139 1140 1141
iv
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Administration: overview
Administration: overview
Introduction
This chapter describes procedures relating to scheduling of audits, resyncs and the control of user access to the OMC. When the Admin icon is selected from the front panel, the Admin Options window (Figure 11-1) is displayed.
PM scheduled reports and logs

Scheduled PM Report and Log functions which are selectable from the Admin icon are detailed in the Performance Management chapter of this manual, Chapter 7.
EMOTOROLA LTD. 2000
111
Access control
ISSUE 18 REVISION 0
Access control
Introduction
The following procedures are outlined in this chapter. S S S S Opening the User Profile List window. Editing a User Profile. Printing a User Profile. Printing the User Profile List window.
Control of individual operator and security level operator access may be performed from the Access Control option. See Setting up fault management in Chapter 8 for recommendations on setting up users for fault management activities.
Command partitioning
The Command Partitioning feature provides a means of partitioning OMC users into different security areas. Depending on which security area an operator has access to, options is allowed/disallowed on the OMC user interface that could be used to alter OMC/BSS information. This provides a level of security that can be used to partition operators into work functions so that they can only access commands which are essential to their job role. It also improves OMC operability by giving users a smaller, easier and more applicable selection of menu options from which to choose. When an OMC user is added to the OMC system a user record is created automatically in the MIB database, giving default command partitions. The default partitions are as follows: OMC group has access to all command partitions except access control and OMCadmin. OMCread group has read only access to the command partitions. OMCadmin user has access to all command partitions, including access control and OMCadmin. NOTE Only the GUI is command partitioned, OMC UNIX scripts are unchanged. Please refer to Online Help, Administration for further details.
112
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Access control
Opening a user profile list

To open a user profile list, use the following procedure: 1. 2. 3. From the Front Panel display, select the Admin icon to display the Admin options window as shown in Figure 11-1. Select the Access Control option, by double clicking the left mouse button. The User Profile List window, Figure 11-2, displays. This window contains a list of user names and the command partitions the user has access to. If a user has read only access to a partition, a series of underscores is displayed in the relevant field.
Figure 11-2 User Profile List window
EMOTOROLA LTD. 2000
113
Access control
ISSUE 18 REVISION 0
Editing a user profile list

To edit a user profile, use the following procedure: 1. 2. Select the required name from the list. Double click on the selection. The User Profile Detailed View is displayed, as shown in Figure 11-3.
Figure 11-3 User Profile Detailed View window 3. Access to each partition may be enabled or disabled in the User Profile Detailed View. Select Edit Edit from the menu bar. The Edit option is highlighted with a diamond. Enable or disable the required options for the user profile by clicking on the Option buttons. Only destructive commands are partitioned, read access is allowed throughout. Please refer to On-Line Help for a list of OMC destructive commands. Save the user profile by selecting File Save from the menu bar. NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000
4.
5.
114
ISSUE 18 REVISION 0
Access control
Printing a user profile detailed view

To print a User Profile Detailed View, use the following procedure: 1. 2. In the User Profile Detailed View window select File Print from the menu bar. Close the User Profile Detailed View window.
Printing the user profile list

To print a User Profile List, use the following procedure: 1. 2. 3. Refer to the Opening a user profile list procedure and follow steps 13. The User Profile List window is opened as in Figure 11-2. Select File Print from the menu bar. Close the User Profile List window.
EMOTOROLA LTD. 2000
115
Overview and recommendations for audit
ISSUE 18 REVISION 0

Introduction to audit function
An audit can only be used to upload information about network elements (NEs) or Commslinks which exist, and are correctly configured as child elements of added BSSs and RXCDRs. An audit only obtains information on Commslinks internal to the BSS, that is, between SITEs. It does not provide information on Commslinks between NEs, such as BSS to RXCDR, RXCDR to OMC or RXCDR to MSC. Use the add procedures detailed in Installation and Configuration: GSM System Configuration (GSM-100-403) to manually create MSCs, OMCs, BSSs and RXCDRs, and the Commslinks between them. NOTE Permission must be obtained from the OMC System Administrator before auditing a network.
List of audit procedures

The following procedures are described: S S Auditing a network via the navigation tree. Auditing a BSS/RXCDR via the navigation tree.
For further details of audit scheduling see Scheduling an audit in this chapter.
116
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Audit functionality
The purpose of the Audit functional unit is to perform on-demand audits of the OMC CM MIB against the CM databases of selected BSS/RXCDR/SITEs in the GSM Network. The Audit function is invoked manually from Navigation tree, or scheduled using the Audit Scheduler. NOTE An Audit can only compare objects that are supported in both the OMC and BSS. Once an Audit has been invoked for the selected NE, the Audit checks if objects and object attributes are consistent at the NE and the CM MIB, and allows any differences to be corrected. An inconsistency list is produced if: S S S S An object exists in the MIB and not in the BSS. An object exists in the BSS and not in the MIB. An object exists in both the MIB and BSS but the attribute values differ. An object exists on both sides but are different versions.
When the user applies the inconsistencies to the OMC, objects not in the NE database (but in the OMC database) are deleted at the OMC. Objects in the NE database are created in the OMC database, and attribute value inconsistencies are updated in the OMC database to become the same as attributes in the NE. After a BSS or RXCDR has been upgraded to a new version of software, the OMC MIB may contain objects that are no longer supported by the new BSS/RXCDR software. Audit detects if there are any objects in the OMC MIB that are no longer supported by the version of software running on the BSS or RXCDR. Audit then deletes from the OMC MIB, objects that are no longer supported by the BSS/RXCDR software load. Each Audit has an Audit log which can be viewed. The log is stored in the MIB. The number of days for which these logs can be kept is configurable. Audit also creates temporary files in: S S /usr/gsm/logs/LISTDIR (pre GSR4) or /tmp/LISTDIR (GSR4 onwards) on the MIB.
These files contain objects and their attributes if Audit finds that these objects do not exist in either the BSS or MIB. These temporary files should not be altered in any way. Aborted/unapplied audits will have files in this directory. It is recommended to delete all files in this directory older than three days.
EMOTOROLA LTD. 2000
117
ISSUE 18 REVISION 0
Recommended audit use

The following are recommendations for audit use: S It is recommended to use the Audit scheduler to implement auditing of the network. Ensure each BSS is scheduled to be audited at least once per week. Use Audit Scheduler>Periodic>Apply to OMC. The Apply to OMC option requires no operator interaction. Use One Shot Audits (Via Nav tree or Scheduler) after a new BSS download, or if the OML has been down for a long time and there has been local maintenance work on the BSS. NOTE Normal CM changes via rlogin do not require an Audit of the BSS. If the OML is in service, and there is no MIB lock on the corresponding object, any database changes to existing devices/functions via rlogin are immediately propagated to the MIB. These are logged via attributeStateChangeEvents (AVCs) in the event logs. Any new devices created/deleted have corresponding objects created/deleted for them in the MIB. These are also logged via objectCreateEvents/ objectDeleteEvents in the event logs. S Network wide audits should only be scheduled where Audit is expected to highlight minor network configuration changes. Each Network wide Audit should be completed before the beginning of the CM morning operator shift. Evaluate how long on average it takes to complete a Network wide Audit on the Network. If it takes too long, use the BSS Audit. One Shot Audits should not be run if they conflict with Resync or cmutil. It is recommended to setup scheduled Audits as they will be queued if another process has control of the MIB lockfile. Audits can only be aborted during the collection phase. The apply phase is usually quite fast and it is recommended to allow it to complete. However, if problems do occur, the only way to stop the Audit is to initiate an OMC stop/start. Always check the Audit Inconsistencies logfile for failures on the Apply phase. One of the most common causes of failure to apply is dummy LACsCIDs in the MIB which prevent real Cells/Neighbours being Audited in. For multiple OMCs, setup shell scripts which will search the omcaudit logfiles for au : and cm : messages and report on failures. The OMC showing the most failures should be investigated before investigation of other OMCs.
118
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Scheduled audits queuing support

NOTE Queuing of scheduled Audits is supported from GSR4. Queuing support is used if more than one Audit is scheduled, and if the first Audit has not completed before the start time of the next Audit is reached (or a resynch or cmutil is also running). Queueing support ensures an Audit is queued, and run after a previous Audit is completed.
Number of operations run at a given time

It is only possible to run one of the following operations at any one time on the CM MIB: S S S S S Audit. Resync. MIB propagation. OOS Devices. cmutil.
Prior to GSR4, Audit creates a lockfile in the /tmp directory called .me.omclockfile. Audit typically deletes the /tmp/.me.omclockfile when it has: S S Finished generating the inconsistencies and Finished applying the inconsistencies to the OMC.
In GSR4, the lockfile created by Audit is set by an environment variable in /usr/gsm/current/config/Common.csh. with a default setting of: OMCLOCKFILE=/usr/gsm/config/global/locks/omc_locked When Resync, CMutil, Audit, Cell Parameter Propagation or RF export/import are enacted, the file omc_locked is created, containing the pid of the process currently locking the MIB. NOTE After upgrade to GSR4, ensure permissions of /usr/gsm/config/global/locks/ are: S owner omcadmin S group omc
EMOTOROLA LTD. 2000
119
ISSUE 18 REVISION 0
Audit scenarios and NE basis

Audit is typically used in one of the following scenarios: A. B. C. D. E. F. G. OMC started for the first time (a newly installed OMC system). A major OMC upgrade, for example from GSR3 to GSR4, requiring a partial MIB Migration. New NEs being added to the network. A BSS receiving a new database download, due to replan. Reparenting of Sites/Paths. OMC detection that network data is different from that in the CM MIB, and requests the operator for an Audit. Operator scheduled periodic Audit at the OMC.
Audit on a NE basis
Audit on a per NE basis is the preferred way of using Audit and is the recommended way to capture significant network changes. This includes Scenarios A to F above. In these scenarios, audits should be carried out and completed one NE at a time.
Network wide audits

In general, network wide audits are not recommended, though it is a selectable option from the Navigation Tree on the OMC GUI and from the Audit scheduler. Field experience has shown that Network wide Audit, initiated at the end of the last CM operator shift (typically 22.00 hours), has often not completed before the beginning of the morning CM operator shift. The Audit will lock the CM MIB while collecting/applying and if the Apply phase is running the Audit cannot be aborted. The recommendations for Network wide audits is as follows: S Network wide audits should only be used in cases where Audit is expected to highlight minor network configuration changes (Scenarios F and G above), and only if the changes are minor. Network wide audits should not be done on a network when there are NEs in the network that have not been previously audited (Scenarios A to E above, and Scenarios F and G if the changes are major).
Audit logs and expired logs

Audit logs require significant memory, so the number of Audit logs retained on the system should be kept to a minimum. The number of days that the Audit logs are held is determined by the attribute setting of the Audit Log Management window (GUI Front Panel> Admin>Audit Log Management). Audit logfiles older than this setting will be deleted the next time an Audit initiates. The recommended setting is one day. For a scheduled Audit, once an Audit has collected the inconsistencies, the Audit log can sometimes have a status of Expired on the Logfile. Expired means the Audit did not apply the inconsistencies to the OMC. The audit log is usually set to expired if an OMC stop/start occurs before the Audit is applied.
1110
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Auditing a network via the navigation tree

Introduction to auditing a network
An audit can only be used to upload information about network elements (NEs) or Commslinks which exist, and are correctly configured as child elements of added BSSs and RXCDRs. An audit only obtains information on Commslinks internal to the BSS, that is, between SITEs. It does not provide information on Commslinks between NEs, such as BSS to RXCDR, RXCDR to OMC or RXCDR to MSC. Use the add procedures detailed elsewhere in this chapter to manually create MSCs, OMCs, BSSs and RXCDRs, and the Commslinks between them. NOTE Permission must be obtained from the OMC System Administrator before auditing a network.
EMOTOROLA LTD. 2000
1111
ISSUE 18 REVISION 0
Auditing a network
The network can be audited either from its detailed view or from the navigation tree. To audit the entire network from the navigation tree, use the following procedure: 1. From the Front Panel, select the Config Mgmt icon to display a navigation tree form as shown in Figure 11-4.
Figure 11-4 Navigation tree form
1112
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
2. 3.
Ensure that the network instance button is selected, that is, that the network name is highlighted. From the navigation tree form menu bar, select Config Mgt Audit. The network audit is initiated and a confirmation box is displayed. The message requests the operator to look at the audit logs for the status.
4.
From the navigation tree form menu bar, select Config Mgt Audit logs (or via the Admin icon on the Front Panel Audit logs). The Audit logs window will contain the active audit log.
5. 6.
If the audit log reports inconsistencies found when finished, open the log file, check the inconsistencies found and if appropriate apply the inconsistencies to the MIB. Close the navigation tree window by selecting File Close from the menu bar.
EMOTOROLA LTD. 2000
1113
Auditing a BSS/RXCDR via the navigation tree
ISSUE 18 REVISION 0
Auditing a BSS/RXCDR via the navigation tree

Introduction to BSS/RXCDR auditing
An audit only obtains information on Commslinks internal to the BSS, that is, between SITEs. It does not provide information on Commslinks between NEs, such as BSS to RXCDR, RXCDR to OMC or RXCDR to MSC. Use the add procedures detailed elsewhere in this chapter to manually create MSCs, OMCs, BSSs and RXCDRs, and the Commslinks between them. NOTE Permission must be obtained from the OMC System Administrator before auditing a network.
Auditing a BSS/RXCDR
To audit an individual BSS or RXCDR, use the following procedure: 1. 2. 3. 4. 5. 6. From the Front Panel, select the Config Mgmt icon to display a navigation tree diagram. If the BSS/RXCDR button is not visible, click on the folder icon next to the network name to expand the navigation tree to the second level. Click on the folder item next to the BSS/RXCDR button to display all existing BSS/RXCDR instances. Click on the required BSS/RXCDR button, it changes colour. Select Config Mgt Audit from the menu bar. Alternatively, an audit can be initiated from the detailed view by selecting Edit Detailed View Options Audit. The element audit is initiated and a confirmation message is displayed directing the operator to refer to the audit logs. 7. From the navigation tree form menu bar, select Config Mgt Audit. The network audit is initiated and a confirmation box displayed. The message requests the operator to look at the audit logs for the status. From the navigation tree form menu bar, select Config Mgt Audit logs (or via the Admin icon on the Front Panel Audit logs). The Audit logs window will contain the active audit log. If the audit log reports inconsistencies, open this logfile, check the inconsistencies found and, if appropriate, apply the inconsistencies to the MIB. 8. Close the navigation tree window by selecting File Close from the menu bar.
1114
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Scheduling an audit
Scheduling an audit
List of procedures
The following is a list of procedures that are performed using the Audit Scheduler Admin Option: S S S S Scheduling an audit. Modifying a scheduled audit. Printing a scheduled audit list. Deleting a scheduled audit list. NOTE If the OMC-R timezone incorporates a daylight-saving scheme where a one or two hour offset is applied to the OMC during the summer months, care should be taken not to schedule an audit when the time is moved back at the end of the summer, it could accidently run twice; or when the clock is moved forward at the start of the summer, it might not run at all. The change from summer to winter time, and vice versa, usually occurs in the hours after midnight on a Friday, Saturday, or Sunday, depending on the country.
EMOTOROLA LTD. 2000
1115
Scheduling an audit
ISSUE 18 REVISION 0
Creating a scheduled audit

To schedule an audit, use the following procedures.
Creating a new audit schedule

To create the audit schedule, follow these steps: 1. Select the Admin icon from the Front Panel to open the Admin Options window (Figure 11-5).
Figure 11-5 Admin Options window 2. 3. Select the Audit Scheduler option. The selection is highlighted and outlined in black. Click OK. The Audit scheduler window, as shown in Figure 11-6, opens. This contains a list of all scheduled audits, detailing their Name, Status, Times, Types and Owner.
Figure 11-6 Audit Scheduler window

1116
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Scheduling an audit
4.
To create a new audit, select Edit Create from the Audit Scheduler window. The auSchedule Detailed View window is displayed as shown in Figure 11-7.
Figure 11-7 auSchedule Detailed View window
EMOTOROLA LTD. 2000
1117
Scheduling an audit
ISSUE 18 REVISION 0
Entering the audit schedule details

To enter the details of the audit schedule, follow these steps: 1. Click on the Scheduled Element button in the auSchedule Detailed View window (see Figure 11-7) to insert the elements to be audited. The network Navigation tree is displayed. Move to the Network Element to be audited. Further details on Navigation tree manipulation can be found in Online Help. NOTE It is valid to select either a BSS, RXCDR, SITE or the entire network to be audited. 3. Double click on the Network Element instance to be audited. The Navigation tree window closes and the selected Network Element is displayed in the Scheduled Element Name field.
2.
Setting the Execute Mode and times

There are two Execute modes to choose from on the auSchedule Detailed View: Oneshot and Periodic. Setting the Execute Mode field to Oneshot means that an audit can be scheduled to start at a set time, and once completed, it will not be rescheduled. Setting the Execute Mode to Periodic schedules an audit of a Network Element to start at a set time, to run to completion, and to be repeated after the time specified in the Interval field has elapsed. This will continue to repeat until the End Time has been achieved. To set the Execute Mode, follow these steps: 1. 2. To change the Execute Mode field from Periodic to Oneshot, or Oneshot to Periodic, click on the Execute Mode button. Hold the left mouse button down, and scroll to the required option. Once the option is highlighted, release the mouse button. The selected mode is displayed in the field. Click on the Start Time or End Time field depending on which one needs changing. The selected parameter is highlighted in black. NOTE Only the Start time field needs to be specified for Oneshot auditing. The date and times are shown in the following format:
Month/Day/Year Hour:Minute:Second
3.
4. 5.
Use the up/down arrow symbols to the right of the Start Time field to change the date and time to the required value. For Periodic Auditing, the End Time field must be set in the same way as for the Start Time field. This field should be set to the date and time after which this Audit function will not be restarted. NOTE This does not mean that an audit in progress will be stopped when this time has been achieved.
6.
For Oneshot Auditing, the End Time and Interval fields are disabled, so go to Setting the Update Mode procedure. NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000
1118
ISSUE 18 REVISION 0
Scheduling an audit
7. 8.
For Periodic Auditing, the Interval field must be set corresponding to the number of hours between the start of corresponding audits. The User Name field contains the name under which the operator has logged on to the system. This may be changed for the purpose of the current audit only.
Setting the Update Mode

When an audit is performed, the information obtained can be either: S S S Used to update the Network element in question Applied to the OMC Performed in interactive mode.
To set the Update Mode, follow these steps: 1. 2. Click on the Update Mode field. Click on the button to select the required Update Mode. NOTE Use the Audit scheduler to implement auditing of the network. Ensure each BSS is scheduled to be audited at least once per week. To do this use Audit Scheduler Periodic Apply to OMC menu options. The Apply to OMC menu option does not need operator interaction. If Audit is invoked from the Navigation Form, the Apply to OMC menu option is not available.
Initiating the scheduled audit

When all the information has been entered into the auSchedule Detailed View window, the scheduled audit can be created. To do this, follow these steps: 1. Select File Create from the menu bar. The new Scheduled Audit is created and can be viewed in the Audit Scheduler window. Any changes to a created network must be done. Refer to Modifying a scheduled audit procedure for more information. 2. 3. Close the Detailed View window by selecting File Close from the menu bar. Close the Audit Scheduler window by selecting File Close from the menu bar.
EMOTOROLA LTD. 2000
1119
Scheduling an audit
ISSUE 18 REVISION 0
Modifying a scheduled audit

All limitations which apply to Auditing must be adhered to when altering a Scheduled Audit. For more information, see the procedure for Scheduling an Audit. To modify a scheduled audit, use the following procedure: 1. Open an Audit Scheduler window. The Audit Scheduler window opens as in Figure 11-8.
Figure 11-8 Audit Scheduler window 2. 3. Select the audit to be modified. The selection is highlighted in black. To open this audit for modification, select Edit Modify from the Audit Scheduler window. The auSchedule Detailed View window is displayed as shown in Figure 11-7. Select Edit Edit from the menu bar. The Detailed View can now be edited. The File Revert option can be used before saving an edited auSchedule Detailed View to return all changed fields to the state they were in before editing took place. NOTE It is impossible to revert to a previous version after an edited version has been saved. 6. 7. 8. When all the required fields have been changed, select File Save from the menu bar. Close the Detailed view by selecting File Close from the menu bar. The altered Scheduled Audit can be viewed in the Audit Scheduler window. Close the Audit Scheduler window by selecting File Close from the menu bar.
4. 5.
1120
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Scheduling an audit
Printing a list of scheduled audits

To print a list of scheduled audits, use the following procedure: 1. 2. 3. 4. Refer to the Creating a scheduled audit procedure and follow steps 13. The Audit Scheduler window will then be open on the screen as in Figure 11-8. Select File Print from the menu bar. The print process is documented in the status bar at the bottom of the window. Close the Audit Scheduler window by selecting File Quit from the menu bar. Close the Admin Options window by clicking on the Cancel button.
Deleting a scheduled audit

Expired Scheduled Audits must be deleted from time to time to avoid excess memory being used. CAUTION Permission must be obtained from a OMC System Administrator before deleting pending scheduled audits. To delete a scheduled audit, use the following procedure: 1. 2. 3. 4. 5. Refer to the Creating a scheduled audit procedure and follow steps 13. The Audit Scheduler window will then be open on the screen as in Figure 11-8. Select the audit to be deleted. The selection is highlighted in black. Select Edit Delete from the Audit Scheduler window. A confirmation window is displayed. Click OK. The Scheduled Audit disappears from the Audit Scheduler window. The message Delete Complete is displayed in the status bar. Close the Audit Scheduler window by selecting File Close from the menu bar.
EMOTOROLA LTD. 2000
1121
Managing audit logs
ISSUE 18 REVISION 0
Managing audit logs

Viewing an audit log list
After an audit has taken place, information relating to this audit is placed in an audit log. This information can be accessed and printed. To view an audit log list, use the following procedure: 1. Select the Admin icon on the Front Panel to open the Admin Options window (Figure 11-9).
Figure 11-9 Admin Options window 2. 3. Select Audit Logs option, then click OK. The Audit Logs window, as shown in Figure 11-10, opens. This contains a list of all completed audits, detailing the Audited Item, Status, Errors experienced, Times, Types and Owner. Close the Audit Logs window by selecting File Close from the menu bar.
4.
Figure 11-10 Audit Logs window

1122
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Managing audit logs
Printing an audit log list

To print an audit log list, use the following procedure: 1. 2. 3. Refer to the Viewing an audit log list procedure and follow steps 13. The Audit Logs window is opened (Figure 11-10). To print the list of Audit Logs, select File Print from the menu bar. The output is sent to the default printer, the progress of the printing is detailed in the status bar. Close the Audit Log window by selecting File Close from the menu bar.
Aborting an audit in progress

As soon as a Audit commences, details of the audit are displayed in the Audit Log list. NOTE When an audit is in progress (known as the collection phase) the Status field in the Audit Log list is set to Active. Audits can only be aborted during the collection phase. The apply phase of an audit is usually quite quick and it is recommended that it is allowed to complete. However, if problems occur during the apply phase, the only way to stop the audit is to do an OMC stop/start. To abort an audit in progress, use the following procedure: 1. 2. Refer to the Viewing an audit log procedure and follow steps 13. The Audit Logs window opens (Figure 11-10). From the Audit Log list, select the audit to be aborted. The selected audit is highlighted in inverse text as shown in Figure 11-11. NOTE An audit in progress is denoted in the Audit Log list by the setting of the Status field to Active.
Figure 11-11 Audit Logs (Audit in progress) window

EMOTOROLA LTD. 2000
1123
Managing audit logs
ISSUE 18 REVISION 0
3.
Select Options Abort from the menu bar. A confirmation window is displayed as shown in Figure 11-12.
Figure 11-12 Abort confirmation window 4. Click OK. The confirmation window disappears and the Audit Log list is updated, with the Status field changed to Aborted as shown in Figure 11-13.
Figure 11-13 Audit Logs (Audit aborted) window 5. Close the Audit Log window by selecting File Close from the menu bar.
1124
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Managing audit logs
Viewing an audit inconsistency report

Types of inconsistencies
After an audit has taken place, information relating to the audit is placed in an Audit Log. Any inconsistencies found between the NE and OMC configuration database are placed in an inconsistency list. This information can be viewed and printed. An inconsistency list is produced if an object exists in the: S S S S MIB but not in the BSS. BSS but not in the MIB. MIB and the BSS, but the attribute values differ. MIB and the BSS, but the versions differ.
Viewing an audit inconsistency report

To view an Audit Inconsistency report for a particular audit, use the following procedure: 1. 2. Refer to the Viewing an audit log procedure and follow steps 13. The Audit Logs window is opened as in Figure 11-10. From the Audit Log list, select the audit from which any inconsistencies should be viewed. The selected audit is highlighted in inverse text. NOTE An Audit Inconsistency report is only completely valid for an audit with a Status field of either Finished or Applied. 3. Select File Open from the menu bar. An Audit Inconsistency report window is displayed as in Figure 11-14, detailing all elements where inconsistencies were found during the audit. See Online Help for a description of the fields in the report. 4. Close the Audit Inconsistency report by selecting File Close from the menu bar.
Figure 11-14 Audit Inconsistency report window

EMOTOROLA LTD. 2000
1125
Managing audit logs
ISSUE 18 REVISION 0
Printing an inconsistency report

To print an Audit Inconsistency Report, use the following procedure: 1. 2. 3. 4. Refer to the Viewing an audit log procedure and follow steps 13. The Audit Logs window is opened as in Figure 11-10. Select an Audit Log shown in this window from which the audit inconsistencies are to be printed. The selection is highlighted in inverse text. Select File Open from the menu bar. An Audit Inconsistency report window is displayed as in Figure 11-14. To print the Audit Inconsistency List, select File Print View from the Audit Inconsistency List window. The output is sent to the default printer, the progress of the printing is detailed in the status bar at the bottom of the window. Close the Audit Inconsistency List window by selecting File Close from the menu bar. Close the Audit Log window by selecting File Close from the menu bar. Close the Admin Options window by clicking Cancel.
5. 6. 7.
Updating database with inconsistencies

To update the database with the inconsistencies found during an audit, use the following procedure: 1. 2. Refer to the Viewing an audit inconsistency report procedure to open an Audit Inconsistency report window. If the Status column is set to Finished, the collection phase of the audit has completed. Select Options Apply to OMC, to update the configuration database at the OMC. A confirmation window is displayed. 3. Click OK to continue or Cancel to abort. The progress of the procedure is documented in the status bar. NOTE When an audit is in progress (known as the collection phase) the Status field in the Audit Log list is set to Active. Audits can only be aborted during the collection phase. The apply phase of an audit is usually quite quick and it is recommended that it is allowed to complete. However, if problems occur during the apply phase, the only way to stop the audit is to do an OMC stop/start. 4. When complete, select File Close to close the window.
1126
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Managing audit logs
Deleting audit logs

Audit Log Management deletes Audit logs after a predefined period. The period is configurable between one and seven days. The logs may also be deleted manually. NOTE If the OMC is stop/started, the Audit Logs remain undeleted until the period is reached after the restart.
Setting the audit logs delete period

The operator should set a period to retain the audit log files, after which the OMC automatically deletes the files. The default setting does not delete the Audit Logs. To set the delete period, use the following procedure: 1. 2. Select the Admin icon on the Front Panel. The Admin Options window, Figure 11-1, opens. Select the Audit Log Management option, then click OK. The Audit Log Management window, Figure 11-15, is displayed.
Figure 11-15 Audit Log Management window 3. 4.

EMOTOROLA LTD. 2000
Select Edit Edit. Enter the period after which the Audit Logs are to be deleted.
1127
Managing audit logs
ISSUE 18 REVISION 0
5.
Select File Save to complete the procedure. The following message is displayed in the status bar at the foot of the window:
Save completed
NOTE To quit without saving select File Close. A dialogue box containing the following is displayed:
There have been changes since you last saved. Pressing OK will exit your current interface without saving.
6.
Select File Close to close the window.
Deleting an audit log

Audits which have had their inconsistencies applied to the OMC are automatically deleted at the start of a new audit. The following procedure deletes the audit logs that have not had their inconsistencies applied to the OMC. To delete an Audit Log, use the following procedure: 1. 2. 3. Refer to the Viewing an audit log procedure and follow steps 1 to 3. The Audit Logs window is opened, as in Figure 11-10. Select the Audit Log to be deleted. The selection is highlighted in inverse text. Select Edit Delete from the menu bar. A confirmation of deletion dialogue box is displayed. It is also possible to select Edit Delete All if all the logs require deletion. Click OK in the confirmation box. The box closes and the selected Audit Log is removed from the list. Close the Audit Log window by selecting File Close from the menu bar.
4. 5.
1128
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Scheduling an FM resync
Introduction FM resync
Resync (alarm and state resynchronization) enables the alarm and device state information at the OMC to be updated to reflect the actual device state and alarm information at the NEs. The Resync operation can be performed by selecting a resync option on the Options menu of a map display or by scheduling a resync via the Admin icon. A resync operation needs to be performed, for example, when a link to a SITE has been down. This is automatic if the OML is restored and SITE becomes INS after an OOS state. The OMC can periodically request a system-wide alarm and state resynchronization of every SITE in the managed network. A resynchronization can also be carried out on OMC startup (user-configured). The following processes are involved: S S resyncState. resyncAlarm.
List of procedures
The following is a list of procedures that are performed using the Resync Scheduler Admin Option: S S S S Scheduling a resync. Modifying a scheduled resync. Printing a scheduled resync list. Deleting a scheduled resync.
Prerequisites
A resync can only be used to resynchronize Network Elements or Commslinks which exist, and are correctly configured as child elements of Added BSSs and RXCDRs. Use the Add procedures detailed in Installation and Configuration: GSM System Configuration (GSM-100-403) to create MSCs, OMCs, BSSs and RXCDRs, and the Commslinks between them. See Administration: overview for some important restrictions to note when using resync in a Network.
EMOTOROLA LTD. 2000
1129
ISSUE 18 REVISION 0
Creating a scheduled resync

To schedule a resync, use the following procedures.
Creating a new resync schedule

To create the resync schedule, follow these steps: 1. Select the Admin icon on the Front Panel to open the Admin Options window as shown in Figure 11-16.
Figure 11-16 2.
Admin Options window
Double click on the Resync Scheduler option. The Resync Scheduler window, as shown in Figure 11-17, opens. This contains a list of all scheduled resyncs, detailing their Name, Status, Times, Types and Owner.
Figure 11-17
Resync Scheduler window
1130
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
3.
To create a new resync, select Edit Create from the menu bar. The rsSchedule Detailed View window is displayed as shown in Figure 11-18.
Figure 11-18
rsSchedule Detailed View window
EMOTOROLA LTD. 2000
1131
ISSUE 18 REVISION 0
Entering the resync schedule details

To enter the details of the resync schedule, follow these steps: 1. 2. Click on the Scheduled Element button in the rsSchedule Detailed View window (see Figure 11-18). The network Navigation tree is displayed. Move to the Network Element to be resynchronized. Further details on Navigation tree manipulation can be found in Online Help. NOTE It is valid to select either a BSS, RXCDR, SITE or the entire network to be resynced. 3. Double click on the Network element instance to be resynchronized. The Navigation tree window closes and the selected Network Element is displayed in the Scheduled Element Name field.
Setting the Execute Mode and times

There are two Execute modes to choose from on the rsSchedule Detailed View: Oneshot and Periodic. Setting the Execute Mode field to Oneshot means that a resyn can be scheduled to start at a set time, and once completed, it will not be rescheduled. Setting the Execute Mode to Periodic schedules a resync of a Network Element to start at a set time, to run to completion, and to be repeated after the time specified in the Interval field has elapsed. This will continue to repeat until the End Time has been achieved. To set the Execute Mode, follow these steps: 1. 2. To change the Execute Mode field from Periodic to Oneshot, or Oneshot to Periodic, click on the button. Hold the left mouse button down, and scroll to the required option. Once this is highlighted, release the mouse button. The selected option is displayed on the Detailed View. Only the Start time field needs to be specified for Oneshot resynching. In this field, click the left mouse button once, when pointing to the parameter to change. The chosen parameter is highlighted in black. NOTE Only the Start time field needs to be specified for Oneshot auditing. The date and times are shown in the following format:
Month/Day/Year Hour:Minute:Second
3.
4. 5.
Use the up/down arrow symbols to the right of the Start Time field to change the parameter to its required value. For Periodic resynching, the End Time must be set in the same way as for the Start Time. This field should be set to the date and time after which this resync function will not be restarted.
1132
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
6.
For Oneshot resynching, the End Time and Interval fields are disabled, so go to Initiating the scheduled resync procedure. NOTE This does not mean that a resync in progress will be stopped when this time has been achieved.
7.
For Periodic resynching, the interval must be set corresponding to the number of hours between the start of corresponding resyncs.
Initiating the scheduled resync

When all the information has been entered into the rsSchedule Detailed View window, the scheduled resync can be created. To do this, follow these steps: 1. Select File Create from the main menu. The new Scheduled resync is created and can be viewed in the Resync Scheduler window. Any changes to a created network must be done using the procedure, Modifying a Scheduled Resync. 2. 3. Close the Detailed View window by selecting File Close from the menu bar. Close the Resync Scheduler window by selecting File Close from the menu bar.
EMOTOROLA LTD. 2000
1133
ISSUE 18 REVISION 0
Modifying a scheduled resync

To modify a scheduled resync, use the following procedure: 1. Refer to the Creating a scheduled resync procedure and follow steps 1 to 3. The Resync Scheduler window (Figure 11-19) will then be open.
Figure 11-19 Resync Scheduler window 2. 3. Select the resync to be modified. The selection is highlighted in black. To open this resync for modification, select Edit Modify from the Resync Scheduler window. The rsSchedule Detailed View window is displayed as shown in Figure 11-20. Select Edit Edit from the menu bar. The Detailed View can now be edited following the rules in the procedure Scheduling a resync. Select File Revert before saving an edited rsSchedule Detailed View to return all changed fields to the state they were in before editing took place. NOTE It is impossible to revert to a previous version after an edited version has been saved. 6. 7. 8. When all the required fields have been changed, select File Save from the menu bar. Close the Detailed View by selecting File Close from the menu bar. The altered Scheduled resync can be viewed in the Resync Scheduler window. Close the Resync Scheduler window by selecting File Close from the menu bar.
4. 5.
1134
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Figure 11-20
rsSchedule Detailed View window
EMOTOROLA LTD. 2000
1135
ISSUE 18 REVISION 0
Printing resync schedule list

To print a list of scheduled resyncs, use the following procedure: 1. Refer to the Scheduling a resync procedure and follow steps 1 to 3. The Resync Scheduler window will then be open on the screen as in Figure 11-21.
Figure 11-21 2.
Resync Scheduler window
To print the list of resyncs to the default printer, select File Print from the Resync Scheduler window. The print process is documented in the status bar at the bottom of the window. Close the Resync Scheduler window by selecting File Close from the menu bar. Close the Admin Options window, by clicking the Cancel button.
3. 4.
Deleting a scheduled resync

Expired Scheduled resyncs must be deleted from time to time to avoid excess memory being used. CAUTION Permission must be obtained from an OMC System administrator before deleting pending scheduled resyncs. To delete a scheduled resync, use the following procedure: 1. 2. 3. 4. 5.
1136
Refer to the Creating a scheduled resync procedure and follow steps 1 to 3. The Resync Scheduler window (Figure 11-21) will then be open on the screen. Select the resync to be deleted. The selection is highlighted in black. Select Edit Delete from the menu bar. The confirmation window opens. Click OK. The Scheduled Resync disappears from the Resync Scheduler window. The message Delete Complete is displayed in the status bar. Close the Resync Scheduler window by selecting File Close from the menu bar. NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Resynchronizing logs
List of procedures
The following is a list of procedures that are performed using the Resync Logs option in the Admin Options window: S S S S Viewing a resync log list. Printing a resync log list. Aborting a resync in progress. Viewing a resync report.
Viewing a resync log list

After a resync has taken place, information relating to this resync is placed in a Resync Report. These reports are accessed through the Resync Log list. To view a Resync Log list, use the following procedure: 1. 2. Select the Admin icon on the Front Panel to open the Admin Options window Figure 11-22. Select the Resync Logs option and click OK.
EMOTOROLA LTD. 2000
1137
ISSUE 18 REVISION 0
3.
The Resync Logs window, as shown in Figure 11-23, opens. This contains a list of all completed Resyncs, detailing the Resynced Item, Status, Errors experienced, Times, Types and Owner.
Figure 11-23 Resync Logs window 4. Close the Resync Logs window by selecting File Close from the menu bar.
Printing a resync log list

To print a resync log list, use the following procedure: 1. 2. Refer to the Viewing a resync log list procedure and follow steps 1 to 3. The Resync Logs list window opens as in Figure 11-23. To print the list of Resync Logs, select File Print from the menu bar. The output is sent to the default printer, the progress of the printing is detailed in the status bar at the bottom of the window. Close the Resync Logs window by selecting File Close from the menu bar.
3.
1138
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Aborting a resync in progress

As soon as a Scheduled Resync commences, see Scheduling a Resync, the details of that Resync are displayed in the Resync Log list. To abort a resync in progress, use the following procedure: 1. 2. Refer to the Viewing a resync log list procedure and follow steps 1 to 3. The Resync Logs list window opens as in Figure 11-23. From the Resync Log list, select the resync log to be aborted. The selected resync is highlighted in inverse text. NOTE A resync in progress is denoted in the Resync Log list by the setting of the Status field to Active. 3. 4. 5. Select Options Abort from the menu bar. A confirmation box is displayed. Click OK. The confirmation window closes and the Resync Log list is updated, with the aborted resync status changed to Aborting. Close the Resync Log window by selecting File Close from the menu bar.
Resync report
After a resync has taken place, information relating to this resync is placed in a Resync Report. Any inconsistencies found between the equipment set up at the resynced Network Element, and what the OMC expects to find is placed in the report. Note the distinction between a Resync Log, which is a general information message generated as the outcome of a resync, and a Resync report, which is a further extension to show the status of each site resync.
Viewing a resync report

To view a Resync Report for a particular Scheduled Resync, use the following procedure: 1. 2. Refer to the Viewing a resync log list procedure and follow steps 1 to 3. The Resync Logs list window opens as in Figure 11-23. From the Resync Log list, select the resync from which the report should be viewed. The selected resync is highlighted in inverse text. NOTE A Resync report is only completely valid for a resync with a Status field of Finished. 3. Select File Open from the menu bar. A Resync Report window is displayed as in Figure 11-24, detailing all elements where inconsistencies were found during the resync. See Online Help for details of the meaning of the fields in the report.
EMOTOROLA LTD. 2000
1139
ISSUE 18 REVISION 0
4.
Close the Resync Report by selecting File Close from the menu bar.
Figure 11-24 Resync Report window
Printing a resync report

To print a Resync Report, use the following procedure: 1. Refer to the Viewing a resync report procedure and follow steps 1 to 3. The Resync Report window opens as in Figure 11-25.
Figure 11-25 Resync Report window 2. To print the Resync Report, select File Print from the Resync Report window. The output is sent to the default printer, the progress of the printing is detailed in the status bar at the bottom of the window. Close the Resync report window by selecting File Close from the menu bar.
3.
1140
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Deleting a resync log

To delete a Resync Log, use the following procedure: 1. Refer to the Viewing a resync log list procedure and follow steps 1 to 3. The Resync Logs list window opens as in Figure 11-26.
Figure 11-26 Resync Logs list window 2. 3. Select the Resync Log to be deleted. The selection is highlighted in inverse text. Select Edit Delete from the menu bar. A confirmation of deletion box opens. It is also possible to select Edit Delete All if all the logs require deletion. 4. 5. Click OK. The confirmation box closes and the selected Resync Log is removed from the list. Close the Resync Log window by selecting File Close from the menu bar.
EMOTOROLA LTD. 2000
1141
ISSUE 18 REVISION 0
1142
EMOTOROLA LTD. 2000
Chapter 12
Performance Management 1
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
ii
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0

Performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of Performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistics: definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance management data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of PM data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the PM GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The selections window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening a stored selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Report options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running a new report from the PM GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reset file indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running stored reports from the command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running a report from the command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running a delimited report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running a scheduled report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing a report log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing PM reports on the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM on the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the OMC on the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM reports on the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Custom Statistics Manipulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of the window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a new custom statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
121 121 121 122 122 122 124 126 127 127 128 129 1210 1212 1212 1212 1212 1213 1213 1213 1214 1214 1215 1215 1215 1215 1217 1217 1217
EMOTOROLA LTD. 2000
iii
ISSUE 18 REVISION 0
iv
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Overview of Performance management
Performance Management (PM) allows the operator to produce and collect performance related data from Network Elements (NEs), and present the information in report format. PM provides the operator with the information necessary to perform the following network management functions: S S S S S S Monitoring of network traffic and equipment loading. Quality of service measurement and analysis. Efficient network management and planning. A historical record of network performance. Device management of statistics for any cell under OMC control. Fault management.
Statistics: definition
Raw statistics
Raw statistics are generated by an NE, collected and stored in the PM database.
Key statistics
Key statistics are derived by formulae which combine a number of raw statistics. Key statistics are normally used to monitor network performance.
EMOTOROLA LTD. 2000
121
Performance management data flow
ISSUE 18 REVISION 0

Overview of PM data flow
Figure 12-1 shows a functional representation of performance management data flow. Performance data is generated at the BSS and the RXCDR, and stored as a PM data file. Performance measurements include traffic measurements within the telecommunications system (both user and signalling traffic), quality of service measurements (delays in call setup) and availability measurements (the beginning and end times of service unavailability). At 30 or 60 minute intervals (defined by the user), the PM files are sent to the OMC. The OMC processing software (known as the parser) then converts the data in the files into raw statistics suitable for storing in the INFORMIX database at the OMC.
MMI PM FEATURES: COMMAND-LINE INTERFACE:
FOUR STEPS TO SUCCESSFUL PM:
S S S S
Measurement Collection Reporting Analysis
S S S
Key statistics reports Tabular & graphical reports Raw statistics menus and forms Tabular reports / graphical Output to screen, file, or printer
S S
Applix command lines Cron jobs
RAW DATA FILES X.25
PARSER KEY & RAW STATISTICS
MMI
FILTERS
OMC DATABASE
BSS/RXCDR OMC PROCESSOR
Figure 12-1 Performance management
Measurements
Measurement results are generated in Network Elements (NEs) and sent to the OMC as raw data via an X.25 network. The data files collected are processed into raw statistics, stored in the OMC database and can be archived onto tape. Reports can be obtained on any of the raw statistics, or key statistics which are calculated from the raw statistics. The results give a high level view of network performance, and can be analyzed to provide operators with the information needed for network management functions, such as, quality-of-service analysis, and planning the evolution of the Public Land Mobile Network (PLMN).
122
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Measurement types
There are six different measurement types, depending on the different physical quantities being measured. For example, a measurement can be expressed as a percentage or as a unit of time. It is possible to control the operational state of a measurement at network elements by executing certain commands from the OMC (for example to reset a value, read an individual value, or turn a measurement on or off). The different measurement types are described below: S Counter. A counter statistic is the cumulative value of an event reported by an application process. The application process increments or pegs the counter statistic by the reported value during an interval. The ALLOC_SDCCH statistic is an example of a counter statistic. S Counter array. Counter array statistics are the total number of times an event occurs and a breakdown of the causes or reasons why the event occurred during an interval. When an event occurs, the BSS increments the individual cause or reason by the value reported by the application at the interval expiry. The OK_ACC_PROC statistic is an example of a counter array statistic. S Gauge. Gauge statistics report the maximum and mean values of a statistic for an interval. The IDLE_TCH_INTF_BAND0 is an example of a gauge statistic. S Duration. A duration statistic is a group of values associated with timing of events controlled by an application process. The duration statistics include the total duration, mean, maximum, and minimum values. The FLOW_CONTROL_BARRED statistic is an example of a duration statistic. S Normal distribution. Normal distribution statistics are the number of times the reported value of an event falls within a specified range. A distribution statistic is a single row array of 10 bins, numbered 0-9. The BSS also saves the minimum reported value, the maximum reported value, and a calculated mean of the reported values. The OMC only reports the distribution mean, maximum and minimum values. The CPU_USAGE statistic is an example of a normal distribution statistic. S Weighted distribution. Weighted distribution statistics are the length of time that the reported value of an event falls within a specified range. These statistics are placed in a single row array of 10 bins, numbered 0-9, and a mean duration of the reported events. The minimum and maximum durations of the reported values are also saved and reported at the end of the interval. The BUSY_TCH statistic is an example of a weighted distribution statistic. NOTE The complete definition of individual raw statistics is given in Maintenance Information: GSM Statistics Application (GSM-100-503).
EMOTOROLA LTD. 2000
123
ISSUE 18 REVISION 0
Collection
Different raw statistic measurements are made at different device levels in each NE. A measurement can be thought of either as a peg count (an integer representing a count of something occurring in the network), or derived from a peg count that is recorded for a device at an NE. Some statistics are measured (pegged) at BSS level, some at GPROC level, and others at carrier level. Figure 12-2 shows the different raw statistics groupings and the levels at which they are pegged.
NE LEVEL
BSS
SITE LEVEL
GPROC
MTL
OML
CBL
RSL
XBL
CELL LEVEL
CELL
NEIGH
CARRIER (TIMESLOT) LEVEL
CARRIER
Figure 12-2 Different raw statistics groupings and peg levels
124
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Measurement administration
The PM GUI provides the Performance Measurement Administration features. This enables the operator to control (enable/disable and set threshold), and schedule PM data generation and collection for any cell under the control of the OMC. The maximum possible number of statistics that can be selected for the different device management operations are as follows: Device management operation type Clear value Status Read threshold Enable Disable Set alarm threshold All enabled statistics Current interval Interval start times Set interval NOTE * Statistics are not used for these device management operation types. The recommended raw statistics to be enabled for the different PM management functions, such as, quality of service measurement and analysis or monitoring of network traffic and equipment loading, are given in Maintenance Information: GSM Statistics Application (GSM-100-503). Statistics type all raw all raw all raw all raw all raw all raw * * * * Maximum allowed 100 16 16 16 16 16 * * * *
EMOTOROLA LTD. 2000
125
ISSUE 18 REVISION 0
Reporting
There are three main types of reports based on the following types of statistics: S S S Key statistics gives an indication of the quality of service being offered by the network. Raw statistics allows detailed analysis of performance. Raw statistics summaries reports allows summary reports of a subset of raw statistics.
Reporting criteria, such as time period, number of cells and number of sites, can be selected. All reports generated can be output to the screen, file or printer. The possible formats of the reports are as follows: S Pareto. Two-dimensional and three-dimensional bar graph and tabular reports (Figure 12-3). A Pareto report collates the Statistic(s) for the period between intervals. S Trend. Two-dimensional and three-dimensional bar (graphical), two-dimensional and three-dimensional line (graphical), and tabular reports. A Trend report collates the Statistic(s) value at the interval times. Once the report has been generated, it is possible to toggle between graphical 2D and graphical 3D, from line to bar graph, and from graphical to tabular data format.
Figure 12-3 An example pareto report
126
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
PM GUI
PM GUI
Accessing the PM GUI
The Performance Management GUI can be accessed from four different OMC GUI areas, namely: S S S S OMC front panel (see Figure 12-4). Navigation tree. Network map. NE contained devices form.
Selecting nodes or devices in Map/Navigation tree/NE contained devices windows and invoking Performance Management from these windows will transfer the device selections through to the PM Selections window (see Figure 12-5). The PM main window (see Figure 12-4) provides the facility to generate a new PM report (by selecting Selections), to access a previously generated report (by selecting Completed Reports), or to display a list of custom statistics and perform various operations on them (by selecting Custom Statistics Manipulation).
4.1 1.6.1.0
Figure 12-4 Invoking the Performance Management main menu
EMOTOROLA LTD. 2000
127
PM GUI
ISSUE 18 REVISION 0
The selections window

The Selections window is the starting point for the creation of a new report, or the running of a previously saved selection with or without modifications, and for performing device management operations. In the Selections window (see Figure 12-5) statistics, their parent devices and the report parameters can be chosen for a report. The devices and statistics required can be sorted and selected, and are easily modified if a change is required. The selections can be viewed on a per NE basis, per statistics group basis, or on a per operator basis. They can then be stored for later use, scheduled to run at a later date, or a report can be started immediately. Initially the Selections window contains a list of previously created selections, if any reports have been created.
Stored selection, viewed by operator name and type.
Figure 12-5 Selecting the parameters of a report A stored selection is a combination of Network Elements (NEs), statistics and report options. These selections are used to execute a report and can be saved to be used at a later time. A report can be chosen to run from the list of stored selections which can be modified, or the report can be run as it is. This window is also the starting point for the creation of a new report. The Edit, View and Filter menu options control how the stored selections are displayed. They can be displayed by operator name, as a shortlist of the commonly used selections, as a complete list of all selections, or as NE selections based on NE types or Statistics types. Once the stored selection has been highlighted, it can be opened by double-clicking on it or selecting File Open from the menu bar.
128
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
PM GUI
Opening a stored selection

Once the stored selection has been opened, the currently selected settings are displayed in the Selections window. The current NE devices and Statistics selected are highlighted, as shown in Figure 12-6. The NE and Statistics selection tables may be manipulated using menu options. The list may be expanded or contracted, all elements selected or deselected, filtered and searched.
Choosing the NE device type
Menu bar options
Expand/contract contained NE devices and statistics by double clicking
NE devices and statistics can be highlighted by clicking
Report options
Figure 12-6 Selecting current NE devices/statistics of a report

EMOTOROLA LTD. 2000
129
PM GUI
ISSUE 18 REVISION 0
Report options
The Report Options section of the Selections window controls the report type. To avoid delay, the options Format, Summary level, Output, and Time Mode must be selected correctly before running a report. The following Format options are available: Available Format Options Format Pareto (Tabular) Trend (Tabular) Pareto (Graphical) Trend (Graphical) Tabular Report ASCII Spreadsheet ASCII Spreadsheet Two dimensional bar graph (2DB) Three dimensional bar graph (3DB) Two dimensional line graph (2DL) Two dimensional bar graph (2DB) Three dimensional line graph (3DL) Three dimensional bar graph (3DB) Graphical Report
Tabular format
When either Trend (Tabular) or Pareto (Tabular) are selected in the Format field different results are produced, depending on the selections made in the Tabular Type and Output fields. Results with different Tabular Type and Output Selected Tabular Type ASCII ASCII ASCII Spreadsheet Spreadsheet Spreadsheet File Screen Printer File Screen Printer Output Result Static text file, that is, it cannot be edited. Static text table. Printed text file. Delimited file, see Running delimited reports76. Spreadsheet table, can be edited. Printed text file.
Summary Level Options

The following Summary Level options are available: S S S S None. PLMN. BSS/RXCDR. SITE.
1210
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
PM GUI
Output Options
The following Output options are available: S S S S Screen Opens a Report Window on the screen which can be viewed, altered, saved etc before printing. Printer
Prints the completed report to the default printer. File
Sends the report to a file.
Time Mode Options

The options available under Time Mode are: S S S Continuous. Blocked. Discrete.
To run or schedule a report the time period must be set. To select the desired interval mode enter the date <DDMMYYYY>, and time (24hr clock) for both start and end.
EMOTOROLA LTD. 2000
1211
Running reports
ISSUE 18 REVISION 0
Running reports
Running a new report from the PM GUI
A Selection window for a new report may be opened, without selected Network Elements, statistics and with default properties. To do this select New from the File menu, a new Selections window then opens. The window will be entitled Noname until renamed or saved. To run a new report select the Report Run option.
Reset file indicator

When an ASCII or Spreadsheet report is run, reset indicator data shows the Sites that did not have complete data. If all data was received for a specified Site and time, this does not display in the Reset File Indicator window. The Reset File Indicator window can be accessed from ASCII or Spreadsheet reports, and run to Screen or File. Reset file indicator data is always stored when a completed report is saved to file. NOTE Reset file indicator data is displayed at Site level regardless of the summary level at which the report is run.
Running stored reports from the command line

Running a stored report from the command line requires knowledge of the Applix command line utilities. Figure 12-7 shows an example of how a stored report can be run from the command line. When running Applix from the command line, the environment variable SQLEXEC should be set as follows, in the window where the command is to be run:
setenv SQLEXEC /usr/informix/lib/sqlrm
Commands in the format shown in Figure 12-7, can then be entered. The stored reports are generic for all statistics types (raw, key or customized), and all report types (detailed or summary). All specifications for the report are specified in the stored selection (such as, graphical/tabular, 2D/3D, detailed/summary, coverage on/off, Screen/Printer/File). Stored reports by default are located in /usr/gsm/ne_data/pm_reports.
Figure 12-7 Running stored report from command line

1212
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Running reports
Running a report from the command line

Running PM reports from the command line requires knowledge of the Applix command line utilities. When running Applix from the command line, the environment variable SQLEXEC should be set as follows, in the window where the command is to be run:
setenv SQLEXEC /usr/informix/lib/sqlrm
Running a delimited report

The purpose of delimited reporting is to export PM data in a tab delimited format. This facilitates the post processing of the data by applications outside the PMGUI. The delimited reports are for export only, and cannot be printed or opened via the completed reports window. In the selection window the following parameters should be selected: S S S Format field Trend (Tabular) or Pareto (Tabular). Tabular Type field Spreadsheet. Output field File.
Tabular, spreadsheet, and graphical reports which are run to screen and displayed in tabular format can be saved as delimited reports.
Running a scheduled report

The purpose of scheduled reporting is to provide a convenient mechanism to run reports on a regular recurring basis. Any stored selection can be scheduled to run at a different time to when the selection was stored (for example, when the network is less busy) either periodically, or on a once off basis. The stored selections scheduled for a report are displayed in the PM Reports Scheduler window which can be opened from the Admin icon of the OMC GUI front panel, or from the Report menu on the Selection window. (Refer to Figure 12-8.) Busy hour reports may be scheduled every day to analyse network efficiency. Each stored selection which is scheduled has an associated Detailed View which contains the relevant data on the running of the report. On execution the report is created and directed to the chosen output device.
Figure 12-8 PM Reports Scheduler window

EMOTOROLA LTD. 2000
1213
Running reports
ISSUE 18 REVISION 0
Viewing a report log

The purpose of the report log is to have a convenient mechanism to monitor the status of scheduled reports as shown in Figure 12-9. Progress of the report execution is continuously updated as the report is running. The PM reports log can be accessed from the Admin icon on the OMC GUI front panel.
Figure 12-9 PM Reports Logs window
Refer to Operating Information: GSM System Operation (GSM-100201) for procedures on how to run reports from the command line.
1214
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Accessing PM reports on the Web

PM on the Web
OMC Performance Management (PM) data reports can be accessed via a standard web browser, such as Netscape or Microsoft Explorer. This is an optional feature. This data is available in two formats: 1. 2. Text (ASCII) format. Tab-delimited or delimited format. This format allows reports to be post-processed using applications which may be external to the OMC. NOTE The web server must be configured to serve delimited reports with a specific MIME type, namely text/tabseparatedvalues (suffix .tsv).
Accessing the OMC on the Web

A client machine on the OMC LAN may have web access to the OMC (PM) data via a standard web browser. The username and password are validated before the web home page is displayed. Navigation through the OMC web page, and opening of reports is achieved via HTML hyperlinks.
PM reports on the Web

Generated PM reports in text or tab-delimited format are available on the web, as shown in Figure 12-10. When a text report is selected from the OMC web page, the selected report will be displayed within the web browser. The browser scroll bars can be used to navigate through the various pages of a report. When a delimited report is selected the result is dependent on the browser configuration. Refer to Running a delimited report in this chapter. The browser may store the data as a file on the client, or launch an application on the client and pass the retrieved data to the launched application. For example, on a PC with a spreadsheet application installed, the browser can be configured to automatically launch the application and import the data directly into the spreadsheet. Configuration of the web browser is done by the user.
EMOTOROLA LTD. 2000
1215
ISSUE 18 REVISION 0
Figure 12-10 PM Reports page
1216
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Custom Statistics Manipulation

Overview of the window
The Custom Statistics Manipulation window displays a list of custom statistics and provides various operations that can be performed on them. The custom statistics are stored in the PM database.
Creating a new custom statistic

A summary of how a new custom statistic is created is described below. 1. Select Custom Statistics Manipulation from the Performance Management window, the Custom Statistics Manipulation window is opened (see Figure 12-11).
Figure 12-11 The Custom Statistics Manipulation window
EMOTOROLA LTD. 2000
1217
ISSUE 18 REVISION 0
2.
Select File New. The Statistics Manipulation window, (see Figure 12-12), is displayed.
Figure 12-12 Statistics Manipulation window 3. Select the required device from the Device Type menu. Raw Statistics can be selected using the left mouse button. The relationship between the selected Raw Statistics and the Custom Statistic is displayed within the Formula list box. 4. To create a Custom Statistic formula, select the required Raw Statistic and the required formulae relationships from the buttons located between the two list boxes in the centre of the window. Enter a suitable description in the Description field located at the end of the window. Select File Save As from the menu bar and, when prompted, enter a name for the new custom statistic.
5. 6.
1218
EMOTOROLA LTD. 2000
Chapter 13
Performance Management 2
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
ii
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0

Performance management overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to Performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM from the front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM from the Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM from the map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM from Contained Devices form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM Report Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM report logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistics management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistics management menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying enabled statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistics intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying current intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the alarm threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Status window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clear Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running a new report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to Running a new report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running a new report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network elements and statistics menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Searching list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Report options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Start/end dates and times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sort criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Filter criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data scale factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Axis scale range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Saving reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delimited reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delimited report format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delimited report example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Display menu on PM reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reset file indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-numerical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-numerical data symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2000
i
131 131 131 131 131 132 132 132 133 133 133 133 134 135 135 135 136 137 139 139 1311 1311 1313 1313 1314 1315 1315 1315 1319 1320 1321 1322 1323 1325 1326 1327 1329 1330 1331 1332 1332 1332 1333 1334 1335 1335 1335 1336 1336
iii
ISSUE 18 REVISION 0
Custom Statistics Manipulation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a new custom statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Renaming a custom statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a custom statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Filtering custom statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Searching a custom statistic list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stored selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening a stored selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running a stored selection from the PM window . . . . . . . . . . . . . . . . . . . . . . . . . . . Running a stored selection from the selections window . . . . . . . . . . . . . . . . . . . . . Saving a stored selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure for saving a stored selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a stored selection to shortlist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Completed reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening a completed report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a completed report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Renaming completed reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reloading the completed report list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Searching from a completed report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing PM reports on the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stored selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying graphical output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying the display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Days . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Saving graphical reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM report scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling a report from Selection Name window . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling a report from Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying a report schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a report schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing a report list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing a schedule detailed view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM reports logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing a PM reports logs list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing an PM reports list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing a PM report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a PM report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
1338 1338 1338 1340 1341 1342 1343 1344 1344 1344 1346 1346 1346 1347 1348 1349 1349 1349 1350 1351 1352 1353 1354 1354 1354 1356 1356 1356 1356 1357 1357 1357 1358 1359 1360 1361 1362 1363 1363 1363 1364 1367 1368 1368 1368 1369 1369 1369 1370 1370 1371
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Running a PM report from the command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running new PM reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stored selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Completed report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance management troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to PM troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMGUI.CFG file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM_RESYNCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Informix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FPOMCAUDIT file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1372 1372 1374 1374 1375 1375 1375 1377 1378 1379 1379 1379
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
vi
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Performance management overview
Performance management overview

Introduction to Performance management
Performance related data is generated by the Network Elements in the network and written to a database at the OMC. The Performance Management application facilitates the presentation of the performance related information. This chapter describes procedures for collecting information on the performance of the network. Information can be collected on various statistics, and reports can be generated. This data can be presented in a graphical or tabular output format.
Statistics
The types of statistics used by OMC operators to monitor network performance are as follows:
Raw statistics
The OMC processes raw statistics generated by the BSS to create key, network health and custom statistics. These statistics include call processing, interface, and processor utilization measurements.
Key statistics
Key statistics are generated at the OMC by processing raw statistics generated by the BSS, using predefined algorithms. These statistics are designed to give an overall indication of the condition of the system and allow comparisons of similar time periods over time, to help detect congestion trends and possible performance degradation.
Network health statistics

Network health statistics are calculated at the OMC using a combination of raw and key statistics. These statistics are used to create BSS network performance reports. These reports provide an indication of the networks health from the subscribers perspective.
Custom statistics
The OMC permits the creation of custom statistics using the algebraic combination of existing raw and key statistics. Refer to Custom Statistics Manipulation window for procedures on creating custom statistics.
Reports
Scheduled reports are initiated from the PM report scheduler, invoked from either Performance Management or Admin. Completed reports can be opened from the Selections window; refer to Opening a completed report in this chapter. Performance Management data can also be accessed via a standard web browser. This is an optional feature. Refer to Accessing PM reports on the Web.
Further information on Performance Management (PM) statistics can be found in the manual Maintenance Information: GSM Statistics Application, (GSM-100-503) and in Online Help.
EMOTOROLA LTD. 2000
131
Accessing performance management
ISSUE 18 REVISION 0

Introduction
The Performance Management feature can be accessed from four OMC areas. These are: S S S S The OMC Front Panel. The Navigation Tree. The network map. The Contained Devices form. NOTE To invoke Performance Management from the navigation tree, network map or contained devices form the application must have been previously started from the front panel in the current session. When Performance Management has been selected from any of the above areas, the application is opened and the Performance Management menu window is displayed. Performance related data is generated by the Network Elements in the network and written to a database at the OMC. The Performance Management application facilitates the presentation of the performance related information. Error messages can be displayed on the status bar in windows or as an Information window as shown in Figure 13-1.
Figure 13-1 Typical error message multiple attempts at starting PM
PM from the front panel

Click the Performance icon to start the Performance Management application. Performance-related data is generated by the NEs and written to a database at the OMC. This application allows the presentation of performance-related information. The application must be initiated from the Front Panel icon before access is available from the Navigation Tree, the map or the Contained Devices form.
132
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
PM from the Navigation Tree

NOTE If any NE is currently selected on the Navigation Tree, the PM application passes the selected NE to the network logs list, using this NE as the base for the available statistics; otherwise all the network entities in the database will be available. Access Performance Management from the Navigation Tree by selecting Options Performance Mgt from the menu bar. Selecting a Network Element in the Navigation Tree before starting Performance Management automatically selects that NE in the PM window NE listings.
PM from the map

NOTE If any NE is currently selected on the Navigation Tree, the PM application passes the selected NE to the network logs list, using this NE as the base for the available statistics; otherwise all the network entities in the database will be available. Open a map from the Map List window, then select Options Performance Mgt from the menu bar to access Performance Management. Selecting a Network Element in the Map window before starting Performance Management automatically selects that NE in the PM window NE listings.
PM from Contained Devices form

NOTE If any NE is currently selected on the Navigation Tree, the PM application passes the selected NE to the network logs list, using this NE as the base for the available statistics; otherwise all the network entities in the database will be available. In the Contained Devices window select Options Performance Mgt from the menu bar to access Performance Management. Multiple NE selection is not supported from the Contained Devices form. Selecting a Network Element in the contained devices form before starting Performance Management automatically selects that NE in the PM window NE listings.
PM Report Scheduler
The PM Report Scheduler is used to input details to set, in advance, the timings and modes for the running of PM reports. The information about the output is sent to a PM Scheduled Report Log file. Performance Management logs can be printed, created, modified and deleted from the PM Report Scheduler option available in the Admin Options window and the PM GUI. For further information refer to PM report scheduler later in this chapter.
EMOTOROLA LTD. 2000
133
ISSUE 18 REVISION 0
PM report logs
Performance Management logs can be opened, printed and deleted from the PM report logs option available in the Admin Options window and the PM GUI. For further information refer to PM reports logs later in this chapter.
134
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Statistics management
Introduction
Statistics management allows the operator to perform Statistical manipulation at the BSS without remote login. Included in this section are the procedures for: S S S S S S S S S Enabling statistics at the BSS. Displaying enabled statistics. Disabling statistics. Viewing statistics intervals. Setting statistics interval. Displaying current intervals. Setting the alarm threshold. Viewing the status window. Clearing statistic values.
Statistics management menu

Statistics Management is available from the Selections window, Figure 13-2 and the Performance Management window, Figure 13-16. NOTE While a statistics management operation is in progress the window used to start the operation is disabled until the operation is completed.
Figure 13-2 Statistics Management menu
EMOTOROLA LTD. 2000
135
ISSUE 18 REVISION 0
Enabling statistics
The operator can enable statistics for a selected Network Entity using the Enable option. The enabled statistics will then be collected by the BSS and uploaded on to the OMC. To enable statistics use the following procedure: 1. From the OMC Front Panel click on the Performance icon. The PM Opening window (Figure 13-3) is displayed.
Figure 13-3 PM Opening window 2. Choose the Selections option. The Selections window (Figure 13-4) is displayed.
Figure 13-4 Selections window 3. 4. 5. Select File New. The Performance Management window opens. From the Network Element list select the required Network Element(s). Select the required statistic(s) from the Statistics list.
136
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
6.
Select Statistics Mgt Enable from the menu bar. The following message is displayed:
Statistic successfully enabled.
NOTE In the event that the Enable operation has failed, the following message will be displayed: Statistic not successfully enabled. Try again? Click the OK button to repeat the procedure.
Figure 13-5 Typical error message Enable statistic
Displaying enabled statistics

To display the enabled statistics for a particular Network Element use the following procedure: 1. 2. 3. Open the Performance Management window, refer to Accessing Performance Management . Select a Network Element from the Network Element list. Select Statistics Mgt All Enabled Statistics from the menu bar. The Device Dialog window (Figure 13-6) is displayed.
Figure 13-6 Device Dialog window

EMOTOROLA LTD. 2000
137
ISSUE 18 REVISION 0
4. 5.
Select the required Network Element from the Device Dialog window. Click on the Results button. The Display Enabled Statistics window, Figure 13-7, is displayed.
Figure 13-7 Display Enabled Statistics window 6. 7.

138
Click the Display Cell Wide Statistics button, a list of all the enabled statistics for the selected cell is displayed in the list box. Click Cancel to close the window. NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Disabling statistics
The operator can disable statistics for a selected Network Entity. The Disabled NE statistics will not then be collected by the BSS and uploaded on to the OMC. NOTE Disabling a statistic impacts any key statistics and custom statistics of which the statistic is a part. To disable statistics use the following operation: 1. 2. 3. 4. Open the Performance Management window, refer to Accessing Performance Management . From the Network Element list select the required Network Elements. Select the required statistic(s) from the Statistics list. Select Statistics Mgt Disable from the menu bar. The following message is displayed:
Statistic successfully disabled.
Statistics intervals
Statistics are collected at preset intervals of 30 or 60 minutes. To display the 12 previous intervals in which statistics were uploaded from the selected BSS use the following procedure: 1. 2. 3. Open the Performance Management window, refer to Accessing Performance Management . Select Statistics Mgt Interval Start Times from the menu bar, the Device Dialog window (Figure 13-6) is displayed. Select the Network element and click on Results, the Display Interval Start Times window (Figure 13-8 ) is displayed.
EMOTOROLA LTD. 2000
139
ISSUE 18 REVISION 0
4.
Click OK to close the window.
Figure 13-8 Display Interval Start Times window
1310
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Setting intervals
To set the interval times use the following procedure: 1. 2. Open the PM window, refer to Accessing Performance Management. Select Statistics Mgt Set Interval from the menu bar. The Set Interval window opens. Refer to Figure 13-9.
Figure 13-9 Set Interval window 3. 4. Select either 30 or 60 minutes from the Interval Duration dropdown list. Click OK to set the interval. Clicking Cancel will abort the operation.
Displaying current intervals

The intervals at which statistics are collected may be displayed from Display Current Intervals. To set the intervals refer to Setting intervals above. To display the Current Interval times use the following procedure: 1. 2. 3. Open the PM window, refer to Accessing Performance Management. Select the required Network Element. Select Statistics Mgt Current Interval from the menu bar. The Display Current Interval window (Figure 13-10) is displayed.
EMOTOROLA LTD. 2000
1311
ISSUE 18 REVISION 0
4.
Figure 13-10 Display Current Interval window
1312
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Setting the alarm threshold

Setting the Alarm Threshold defines the level at which, if exceeded, a statistic will be alarmed at the OMC. To set the Alarm Threshold level use the following procedure: NOTE Only certain statistics can be alarmed, for a list of alarmed statistics refer to GSM-100-503, Maintenance Information: GSM Statistics Application. 1. 2. 3. Open the PM window, refer to Accessing Performance Management. Select a Network Element and an alarmed statistic from the PM window. Select Statistics Mgt Set Alarm Threshold from the menu bar. The Set Alarm Threshold window (Figure 13-11) is displayed.
Figure 13-11 Set Alarm Threshold window 4. 5. Enter the Threshold level in the text box. Click OK to continue the operation. Click Cancel to abort the operation.
Status window
The Status window contains information on a statistics status (whether a statistic is enabled or disabled at the BSS). A statistic with a status of 1 is enabled, the statistic will be uploaded from the BSS to the OMC. A statistic with a status of 0 is disabled. To view the status of statistic(s) use the following procedure: 1. 2. 3. Open the Performance Management window. Select the required statistic from the PM window. Select Statistics Mgt Status from the menu bar. The Status window (Figure 13-12) is displayed.
EMOTOROLA LTD. 2000
1313
ISSUE 18 REVISION 0
4.
Figure 13-12 Status window
Clear Value
The Clear Value menu option is used to reset a Statistic value for a particular Network Element. The Statistic must have been enabled, the value will then be cleared for the current interval. To clear the value of a Statistic use the following procedure: 1. 2. 3. Open the PM window, refer to Accessing Performance Management. Select Network Elements and Statistics from the Performance Management window as required. Select Statistics Mgt Clear Value from the menu bar, a confirmation dialogue box (Figure 13-13) is displayed.
Figure 13-13 Clear Value confirmation window 4.

1314
Click OK to close the confirmation window. NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Running a new report

Introduction to Running a new report
Performance related data is generated by the Network Elements in the network and written to a database at the OMC. The Performance Management application facilitates the presentation of this performance related information in a report format. A report consists of multiple pages of graphical or tabular data. The report control options (menus and dialogues) provide facilities to navigate around the report, manipulate the data and modify the display.

NOTE Error/process messages may be displayed in the display bar at the foot of the Performance Management window (Figure 13-16). It is important to frequently refer to this area. To run a new report perform the following procedure: 1. 2. Access Performance Management, refer to Accessing Performance Management in this chapter. From the PM opening window (Figure 13-14), choose Selections.
Figure 13-14 PM Opening window
EMOTOROLA LTD. 2000
1315
ISSUE 18 REVISION 0
3.
Click OK, clicking Exit will abort the opening. The Selections window, Figure 13-15, opens. This window is the start point for the creation of a new report, or to return to a previously stored selection with or without modifications. The Selections window contains a list of previously selected report criteria, if reports have been previously created and saved.
Figure 13-15 Selections window
1316
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
4.
Select File New from the menu bar. The Performance Management window (Figure 13-16) opens.
Device type selection box
Figure 13-16 Performance Management window NOTE For multiple selections from the Network Elements/Statistics listings hold down the CTRL key and select the required option. 5. 6. 7. 8. 9.
EMOTOROLA LTD. 2000
Select the Device Type, refer to Device Type in this section. Select the required Network Elements. To manipulate the Network Elements menu refer to Network elements and statistics menus. Select the required Statistics. To manipulate the Statistics menu refer to Network elements and statistics menus. Select the required report options. Refer to Report options. Select the start/end dates and times and interval mode. Refer to Start/End dates.
1317
ISSUE 18 REVISION 0
10.
Click the Run button. The report will now run. A typical graphical report is shown in Figure 13-17.
Figure 13-17 A Pareto 3-D bar graph report 11. Select File Close to close the window. The report format may be changed to/from Graphical and Tabular. In the event that the Performance Management window was not correctly filled out an error message will display at either the status bar or in a message window as shown in Figure 13-18.
Figure 13-18 Typical error messages report generation
1318
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Device type
Selecting the Device Type selection box, as shown in Figure 13-16, alters the Statistics available within a Report. Device types are: S S S S S S S S S S S S S S BSS. Cell. Neighbour. Carrier. GPROC. MTL. CBL. OML. RSL. XBL. DYNET_Group. GBL. GSL. DPROC.
The default value is Cell.
EMOTOROLA LTD. 2000
1319
ISSUE 18 REVISION 0
Network elements and statistics menu

The Network Element and Statistics selection tables may be manipulated using the popup menus available from the right mouse button in the list window boxes, see Figure 13-19. The list may be expanded and contracted, all elements selected/deselected, filtered and searched.
Figure 13-19 PM window with popup menu
Expand All
To view all the subgroups within the list, select the Expand All option from the popup network elements and statistics menu.
Contract All
To minimize the list, select Contract All from the network elements and statistics popup menu.
1320
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Select All
To select all the elements in the list, select Select All from the network elements and statistics popup menu.
Deselect All
To deselect all the elements in the list, select Deselect All from the network elements and statistics popup menu.
Searching list
To search a list select Search from the network elements and statistics popup menu. To search a Network Element list use the following procedure: 1. Select Search from the Network Elements popup menu. The Search window (Figure 13-20) is displayed.
Figure 13-20 Search window 2. Enter the search string of the Network Element that is required. By selecting the wildcard option the search string ends in a wildcard, the search string BSS with wildcard selected finds the next entry containing the term BSS, for example, BSS01. Searches can be performed either forwards or backwards through the list to the end or start. 3. 4. Click Find to start search. If the Network Element found is not required, click Deselect. Then click Find to continue the search. If the Network Element found is one of several required, click Find again to search for the next NE. The original NE remains selected.
EMOTOROLA LTD. 2000
1321
ISSUE 18 REVISION 0
Filtering
The filtering option can be accessed for a Network Elements list or a Statistics list, as follows. 1. Select the filter option from the required popup menu. The Filter window (Figure 13-21) is displayed.
Figure 13-21 Filter window 2. Enter the Filter String. The Filter String filters in all applicable groups within the list. By selecting the wildcard option the Filter String contains a wildcard, the search string BSS with wildcard selected will find all entries containing the term BSS, for example, BSS01, BSS02, BSS3...... 3. Click on Filter. (Click Cancel to abort the operation.)
1322
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Report options
The Report Options section of the Performance Management window (Figure 13-16) controls the report type. The options Format, Summary Level, Output, Time Mode and Display Mode must be selected correctly before running a report. Format The following Format options are available: Table 13-1 Format Pareto (Tabular) Trend (Tabular) Pareto (Graphical) Trend (Graphical) Tabular Report ASCII Spreadsheet ASCII Spreadsheet Two dimensional bar graph (2DB) Three dimensional bar graph (3DB) Two dimensional line graph (2DL) Two dimensional bar graph (2DB) Three dimensional line graph (3DL) Three dimensional bar graph (3DB) Graphical Report
Trend reports are supported in all time modes, refer to the Time Mode section. In Continuous mode, one value is displayed for each time interval between the start date / start time and end date / end time (for example, 00:00 on 1st December to 16:00 on 3rd December). In Blocked mode, a value is displayed for each interval between the start time and end time, for each day between start date and end date (for example, 00:00 to 16:00 on the 1st, 2nd and 3rd December). In Discrete mode, a value is displayed for each interval between the start time and end time, for the start date and end date, (for example, 00:00 to 16:00 on the 1st and 3rd December). The displaying of data for a full period is more efficient than null filling unrequested time periods. Pareto reports are supported in all time modes. In Continuous mode, one value is displayed for the complete time period selected. In Blocked mode, multiple values may be displayed, for example, when using a Short Term database, a Pareto graph in Blocked mode displays a single value for each day between the specified start and end times. In Discrete mode, two values are displayed, one for first and one for last day between the specified start and end times.
EMOTOROLA LTD. 2000
1323
ISSUE 18 REVISION 0
Tabular format
When either Trend(Tabular) or Pareto(Tabular) are selected in the Format field different results are produced (see Table 13-2), depending on the selections made in the Tabular Type and Output fields. Table 13-2 Tabular Type ASCII ASCII ASCII Spreadsheet Spreadsheet Spreadsheet Output Screen Printer File Screen Printer File Result Static text table, that is, it cannot be edited. Printed text file. Static text file. Spreadsheet table, can be edited. Printed text file. Delimited file, see Delimited reports.
Summary Level
The following Summary Level options are available: None, PLMN, BSS/RXCDR, SITE, PCU. The latter has been added when running DPROC,GSL, and GBL reports.
Output
The following output options are available: The Screen option produces a report window on the screen, which can then be viewed or altered before printing. The Printer option prints the completed report to the default printer. The File option opens a Completed Report Output File Name window. Enter the report name. Click OK from this window to proceed, Cancel to return to the Selection Name window, or Help to open a help page. Time Mode The options available under Time Mode are Blocked, Discrete and Continuous. In Blocked mode, when using a Short Term database, the data collected each day between starttime and endtime is used to generate the report. This is typically used to generate busy hour daily reports. In Discrete mode, when using a Short Term database, data collected on startdate and enddate only, between starttime and endtime, is used to generate the report. In Continuous mode, when using a Short Term database, all data collected between startdate/starttime and enddate/endtime is used to generate the report.
1324
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Start/end dates and times

To run or schedule a report, the time period must be set. The period set specifies the time for which the statistics are collected. The report is generated using the statistics specified within the start and end dates. To Enter the Start/End dates, use the following procedure: 1. 2. Open a PM window, refer to Accessing Performance Management in Operating Information:GSM System Operation (GSM-100-201). Select the required Interval Mode, Absolute or Relative. In absolute mode, date and time are specified. In relative mode, day and time are specified, relative to the time at which the report is being run. 3. Enter the Start and End dates in the fields. The date format is DDMMYYYY, the time format is 24 hour.
Figure 13-22 Interval Mode section In the event that the start/end date fields are incorrectly entered an error message will display at either the status bar or in an error message window as shown in Figure 13-23.
Figure 13-23 Typical error message start/end date fields incorrect
EMOTOROLA LTD. 2000
1325
ISSUE 18 REVISION 0
Sort criteria
The sort option sorts the statistics in an ascending/descending statistical value order. This option is enabled only for Pareto reports. 1. 2. Select the statistics that require filtering from the statistics list (Figure 13-16). Select Options Sort Criteria from the menu bar. The Sort Criteria window (Figure 13-24) is displayed.
Figure 13-24 Sort Criteria window 3. 4. 5. Select either Ascending (from lowest to highest), Descending (from highest to lowest) or Off (no numerical order) as required. Select the statistic required from the menu. Click OK to continue.
1326
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Filter criteria
The filter option filters Network Entities in statistical value order for up to four statistics. This option is enabled only for Pareto reports. 1. Highlight the statistics that require filtering from the statistics list (Figure 13-16). NOTE A maximum of four statistics may be filtered at any one time. There is a maximum of 14 raw statistics which can be selected from the statistics list in the Performance Management window. 2. Select Options Filter Criteria from the menu bar. The Filter Criteria window (Figure 13-25) is displayed.
Figure 13-25 Filter Criteria window 3. Click on either Filter In/Out as desired. Filter In includes all the selected Network Entities whose statistical values are within the set range. Filter Out discloses all the selected statistics within the set range. Select the required statistic from the list menu. Enter the filter required range for the statistic. The left entry box should contain the lower value in the filter range and the right box should contain the upper value. Repeat steps 4 and 5, if more statistics are required. From the list menu If Filter removes all data, select either Turn filter off and continue (default) or Stop processing report. See Table 13-3.
4. 5. 6. 7.
EMOTOROLA LTD. 2000
1327
ISSUE 18 REVISION 0
8.
Click OK to continue or Cancel to exit. If the range limits are incorrect, a warning window is displayed. Table 13-3 Filter setting return no data options Option Action Reset data [Y/N] Result
Reset indicator data shows Sites that do not have complete data Turn filter off and continue Stop processing report Turn filter off and processes report. Stops processing report. N N Report Generated A message window is displayed:
Current Filter settings return no data. Exiting Performance Management Report OK
Turn filter off and continue
Turn filter off and processes report. Stops processing report but reports on reset file data.
Report generated with Reset file indicator data. A report is generated stating current filter settings return no data and displays reset file indicator data.
Stop processing report
NOTE Refer to: The Display menu on PM reports, Reset file indicator for details on reset indicator data.
1328
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Data scale factor

The Data Scale Factor scales the Yaxis of the display. Each statistic may have an individual scaling factor. This option is enabled only for Graphical reports. 1. Select Options Data Scale Factor from the menu bar. The Data Scale Factor window (Figure 13-26) is displayed.
Figure 13-26 Data Scale Factor window 2. 3. 4. Select the On button to activate the option. Select the required statistic to be scaled from the Statistic Name list. Enter the scale factor in the Data Scale Factor field. NOTE A Scale factor of 2 will double the Yaxis scaling, a scale factor of 0.5 will halve it. 5. Click OK to continue.
EMOTOROLA LTD. 2000
1329
ISSUE 18 REVISION 0
Axis scale range

To change the axis scale range of the report use the following procedure (This option is enabled only for Graphical reports): 1. Select Options Axis Scale Range from the menu bar. The Axis Scale Range window (Figure 13-27) is displayed.
Figure 13-27 Axis Scale Range window 2. Select either Automatic or Manual (default is Automatic). Automatic will optimise automatically the axis scale range for the data. 3. 4. If Manual is selected, enter the required values in the Lower and Upper data boxes. Click OK to continue. Figure 13-28 shows a typical error message for changing the axis scale range.
Figure 13-28 Typical error message scale out of range
1330
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Saving reports
There are a number of different Save Report boxes that can display depending on the format of the PM report that is being saved.
Saving tabular/spreadsheet reports

To save an unnamed tabular/spreadsheet report use the following procedure: 1. 2. 3. Select File Save or Save As from the menu bar. A Save Report box is displayed. Enter the filename in the FileName field. From the Format list select ASCII, Delimited, or Spreadsheet. When the Delimited option is selected, a note is displayed indicating that this option is only for data that will be exported. See Figure 13-29. 4. Click OK to save the file.
Figure 13-29 Save Report box (tabular/spreadsheet)
Saving tabular/ASCII reports

To save an unnamed tabular/ASCII report use the following procedure: 1. 2. 3. Select File Save As from the menu bar. A Save Report box is displayed (Figure 13-30). Enter the filename in the FileName field. Click OK to save the file.
Figure 13-30 Save Report box (tabular/ASCII)

EMOTOROLA LTD. 2000
1331
Delimited reports
ISSUE 18 REVISION 0
Delimited reports
Introduction
Performance management delimited reports are for export only. They are intended for users who want to post-process PM data using applications outside the PMGUI. They cannot be printed and cannot be opened via the Completed Reports window. Refer to Completed reports.
Procedure
Delimited reports are generated using the following procedure: 1. 2. 3. 4. 5. Open a Performance Management window, refer to Accessing Performance Management in this chapter. In the Format field select Trend (Tabular) or Pareto (Tabular). In the Tabular Type field select Spreadsheet. In the Output field select File. Click the Run button on the toolbar to run the report. The message displayed on the status bar indicates that the report is being written to the delimited reports directory.
Tabular, spreadsheet, and graphical reports which are run to screen and displayed in tabular format, can be saved as delimited reports. Refer to Saving reports.
1332
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Delimited reports
Delimited report format

Table 13-4 displays the format of a delimited report. It is presented here in a table format for clarity. In an actual report file, fields of the report are separated by a tab character. Table 13-4 Delimited report format <Report Type> <Report Title> Start Date: <date> Start Time: <time> End Date: <date> End Time: <time> Time Mode: <time mode>
Device Name Date <Unique Device Name> ... <Date>
Time <Time>
<statistic 1> <statistic 1 value> ...
...
...
<Device Type> Statistics Summary <Device Name>
Coverage Type
Explanation
<statistic 1>
<statistic 2>
<statistic 3>
% Coverage
<% coverage for statistic 1> <# rows retrieved for statistic 1> <Explanation of # of expected rows> ... <Expected # rows retrieved for statistic 1> ...
<% coverage for statistic 2> <# rows retrieved for statistic 2> <Expected # rows retrieved for statistic 2> ...
<% coverage for statistic 3> <# rows retrieved for statistic 3> <Expected # rows retrieved for statistic 3> ...
Rows Retrieved Rows Expected
...
...
EMOTOROLA LTD. 2000
1333
Delimited reports
ISSUE 18 REVISION 0
Delimited report example

Figure 13-31 and Figure 13-32 show examples of how a pareto and trend delimited report are displayed in a spreadsheet window.
Figure 13-31 Pareto delimited report
Figure 13-32 Trend delimited report
1334
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
The Display menu on PM reports

Introduction
On PM reports the Display menu is used to display information about reset indicator data and non-numerical data.
Reset file indicator

When an ASCII or Spreadsheet report is run reset indicator data shows the Sites that did not have complete data. If all data was received for a specified Site and time this does not display in the Reset File Indicator window. The Reset file indicator window can be accessed from ASCII or Spreadsheet reports run to Screen or File. On a report select Display Reset Indicator to display reset file indicator data. The data is displayed in a new window in ASCII format (Figure 13-33). Reset file indicator data is always stored when a completed report is saved to file. NOTE Reset file indicator data is displayed at Site level regardless of the summary level at which the report is run.
Figure 13-33 Reset File Indicator window

EMOTOROLA LTD. 2000
1335
ISSUE 18 REVISION 0
Non-numerical data
Non-numerical data can be returned in a PM report, for example if no data was received from a device or a statistic is not applicable to the BSS release. To display the 0 entries which are non-numerical select Display Show Null Values (Figure 13-34) from the menu bar, or, in the case of graphical reports, select the Tabular toggle button. This non-numerical entries are highlighted with the appropriate symbols. Refer to Non-numerical data symbols.
Figure 13-34 Pareto (Graphical) report showing Display menu
Non-numerical data symbols

Non-numerical data is represented in PM reports by the symbols: ?, N/A, and /0 .
?
A question mark in a report means that no data was received from a device at a particular time (Figure 13-35). In the case of calculated statistics this may indicate that some of the data used in the calculation was missing. Graphically this is represented as 0.
N/A
This is used to indicate that the statistic chosen is not applicable to a particular BSS due to its release load. For example, certain statistics are new in GSR4, so a GSR3 BSS cannot report on those statistics.
1336
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
/0
This symbol is used for calculated statistics only. It indicates that the calculation of the statistics resulted in a divide-by-zero error. This may occur when a key statistic is being calculated and a raw statistic divisor in the key statistic is equal to zero. The key statistic cannot then be calculated.
Figure 13-35 Pareto (Tabular) report
EMOTOROLA LTD. 2000
1337
Custom Statistics Manipulation window
ISSUE 18 REVISION 0

Introduction
The Custom Statistics Manipulation window displays a list of custom statistics and provides the means to perform various operations on them. The custom statistics are stored in the PM database.
Creating a new custom statistic

Use the following procedure to create a new custom statistic: 1. Open the Performance Management window (refer to Accessing performance management in this chapter). The Performance Management window is displayed. Select Custom Statistics Manipulation and click OK. The Custom Statistics Manipulation window, Figure 13-36, is displayed.
2.
Figure 13-36 The Custom Statistics Manipulation window
1338
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
3.
Select File New. The Statistics Manipulation window, Figure 13-37, is displayed.
Figure 13-37 Statistics Manipulation window 4. Select the required device type from the Device Type list. The Statistics Manipulation window contains a list of Raw Statistics. The relationship between the selected Raw Statistic(s) and the Custom Statistic is displayed within the Formula listing. The Copy button allows the selection of one or more rows in the Formula list box. The Paste button is enabled if a statistic has been cut or copied from the Raw Statistics list box (otherwise it is greyed out). Users can then paste a statistic into the Formula list box. The Delete button allows the deletion of one or more rows from the Formula list box. NOTE Deleted rows cannot be pasted. 5. To create a Custom Statistic formula select the required raw statistic(s) from the Raw Statistics list, and then the required formulae relationship +, , *, /, (, ).
EMOTOROLA LTD. 2000
1339
ISSUE 18 REVISION 0
Where: +
is: The addition of two consecutive items in the formula window, (a parenthetic expression is considered as one item). The subtraction of the two consecutive items in the formula window. The multiplication of the two consecutive items in the formula window. The division of the two consecutive items in the formula window. Parenthesis.
( or )
Clicking on any of these operators copies them into the last row of the Formula list box. 6. In the event that a numerical value is required within the formulae, enter the numerical value in the Add field, then click Add. The value is displayed on the next line of the Formula list. Select the Statistic Unit (if required). Enter a suitable description within the Description field. NOTE A description must be entered before the Custom Statistic is saved. 9. 10. Select File Save As from the menu bar. Enter a suitable name for the custom statistic in the Statistic Name field. No spaces are allowed within the name, where a space is required it is recommended that an underscore (_) be used.
7. 8.
Renaming a custom statistic

To rename a custom statistic use the following procedure: 1. 2. Open the Performance Management window, select Custom Statistics Manipulation and click OK. The Custom Statistics Manipulation window opens. Select the custom statistic required.
1340
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
3.
Select Edit Rename from the menu bar. The Rename Custom Statistic window, Figure 13-38, opens.
Figure 13-38 Rename custom statistic window 4. Enter the new name, without spaces, in the New Name field and click OK. NOTE It may be necessary to Reload the Custom Statistics Manipulation window before the renamed custom statistic is visible.
Deleting a custom statistic

To delete a custom statistic use the following procedure: 1. 2. 3. 4. Open the Performance Management window, select Custom Statistics Manipulation. Select the custom statistic required. Select Edit Delete from the menu bar. A delete box is displayed. Check that the custom statistic to be deleted is named within the Delete box , click OK to proceed with the deletion. NOTE It may be necessary to Reload the Custom Statistics Manipulation window before the renamed custom statistic is visible.
EMOTOROLA LTD. 2000
1341
ISSUE 18 REVISION 0
Filtering custom statistics

In the Custom Statistics Manipulation window use the Filter menu to filter the custom statistics available in the window, Figure 13-39. Device types are: S S S S S S S S S S BSS/RXCDR. CELL. NEIGHBOUR. CARRIER. GPROC. MTL. CBL. OML. RSL. XBL.
The default device is Cell.
Figure 13-39 The Custom Statistics Manipulation Filter menu
1342
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Searching a custom statistic list

To search a Network Element list use the following procedure: 1. Select Options Search from the menu bar in the Custom Statistics Manipulation window. The Search window (Figure 13-40) opens.
Figure 13-40 Search window 2. Enter the search string of the required Network Element. By selecting the wildcard option the search string ends in a wildcard, the search string BSS with wildcard selected finds the next entry containing the term BSS, for example, BSS01. Searches can be performed either forwards or backwards through the list to the end or start. 3. 4. Click Find to start search. If the Network Element found is not required, click Deselect. Then click Find to continue the search. If the Network Element found is one of several required, click Find again to search for the next NE. The original NE remains selected.
EMOTOROLA LTD. 2000
1343
Stored selections
ISSUE 18 REVISION 0
Stored selections
Introduction
A previously stored selection may be opened directly from the Stored Selections window.
Opening a stored selection

To open a stored selection use the following procedure: 1. 2. 3. Click on the PM icon from the Front Panel. The PM Opening window is displayed (Figure 13-41). From the PM opening window (Figure 13-41), choose Selections. The option is highlighted. Click OK. The Selections window, Figure 13-15, is displayed. Clicking Exit will abort the operation.
Figure 13-41 PM opening window 4. Select the required selection. The text background is highlighted.
1344
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Stored selections
5.
Select File Open from the menu bar. The Performance Management window (Figure 13-42) opens.
Figure 13-42 Performance Management window

EMOTOROLA LTD. 2000
1345
Stored selections
ISSUE 18 REVISION 0
Running a stored selection from the PM window

To run a stored selection from the PM window, use the following procedure: 1. 2. Follow steps 1 to 5 of procedure Opening a stored selection. From the Performance Management window (Figure 13-42) click the Run button. The report runs and the report window opens, this may cause a delay. 3. 4. A confirmation window is displayed after a delay, clicking OK continues the process. Clicking Abandon halts the process. Close the report by selecting File Close from the menu bar.
Running a stored selection from the selections window

To run a stored selection (full report only) from the selections window, use the following procedure: 1. 2. 3. Follow steps 1 to 3 of procedure Running a new report. From the Selections window, Figure 13-15, click the Run button. The report runs and the report window opens. Close the report by selecting File Close from the menu bar.
Saving a stored selection

Once all parameters have been entered in the PM window, a selection may be stored. The selection will be added to the Selections list, the default is Full Selection. A selection list may be saved in the following list formats: S S S S S Complete List Lists all stored selections. Short list Used for frequently accessed selections. NE selection list A list of selections containing only selected Network Elements, that is, with no statistics selected. Statistic selection list A list of selections containing only selected statistics, that is, with no Network Elements selected. Full selection list Full list of all stored selections.
1346
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Stored selections
Procedure for saving a stored selection

To save a selection use the following procedure: 1. 2. Open a PM window and enter the required variables. Select File Save, or File Save As if altering a previously stored Selection. The Save Stored Selection window opens, Figure 13-43.
Figure 13-43 Save Stored Selection window 3. 4. 5. Enter the name in the Selection Name field. Select the required format options from the list. Click OK to save the selection. Clicking Cancel will abort the operation. Figure 13-44 shows a typical error message for saving a stored selection.
Figure 13-44 Typical error message report already exists
EMOTOROLA LTD. 2000
1347
Stored selections
ISSUE 18 REVISION 0
Adding a stored selection to shortlist

A stored selection may be added to the shortlist from the Stored Selections window. The shortlist provides a place for the most frequently accessed selections. To add a stored selection to the shortlist use the following procedure: 1. 2. 3. Open the Stored Selections window. Click the stored selection that will be added to the list. Select Edit Shortlist Add. Check the status bar to confirm that the selection has been added to the shortlist.
1348
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Completed reports
Completed reports
Prerequisites
Completed reports may be saved and reviewed. Once a report has been saved it may be regenerated using the Completed Reports window. The report displays in the same format that it was last saved as.
Opening a completed report

To open a completed report use the following procedure: 1. 2. From the Performance Management opening window, select Completed Reports. Click OK. The Completed Reports window is displayed. NOTE Delimited reports cannot be opened via the Completed reports window. 3. 4. Select the required completed report from the list displayed in the Completed Reports window (Figure 13-45). Select File Open from the menu bar. The report window opens.
Figure 13-45 Completed Reports window
EMOTOROLA LTD. 2000
1349
Completed reports
ISSUE 18 REVISION 0
Deleting a completed report

To delete a completed report from the Completed Report list: 1. 2. 3. Follow Steps 1 and 2 of procedure Opening a completed report in this section. Select the completed report to be deleted from the Completed Report list. Select Edit Delete from the menu bar. The delete confirmation window, as in Figure 13-46, is displayed.
Figure 13-46 Complete Report Deletion confirmation window 4. 5. Check that the name within the window is correct. Click OK to delete the named report or Cancel to abort the operation. Close the Completed Report window by selecting File Close.
1350
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Completed reports
Renaming completed reports

To rename a completed report use the following procedure: 1. 2. 3. Follow steps 1 to 2 of procedure Opening a completed report in this section. Select the completed report to be renamed from the Completed Report list. Select Edit Rename from the menu bar. The Rename Completed Report window, as in Figure 13-47, opens.
Figure 13-47 Complete Report rename confirmation window 4. 5. Enter the new report name in the New Name field. Check that the name within the window is correct. Click OK to rename the named report or Cancel to abort the operation. In the event that the New Name field is incorrectly entered an error message is displayed, as shown in Figure 13-48.
Figure 13-48 Typical error message renaming a completed report 6. Close the Completed Report window by selecting File Close.
EMOTOROLA LTD. 2000
1351
Completed reports
ISSUE 18 REVISION 0
Reloading the completed report list

Reloading resynchronizes the Network Element and Statistics with the database. To reload the completed report list use the following procedure: 1. 2. Follow steps 1 to 2 of procedure Opening a completed report in this section. Select File Reload from the menu bar. The Reload confirmation window, Figure 13-49, is displayed. Reloading the completed reports list after selections have been made from the NE or Statistics lists may cause operations to be lost.
Figure 13-49 Resync Completed Reports widow 3. 4. Click OK to update the list or Cancel to abort the operation. Close the Completed Report window by selecting File Close.
1352
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Completed reports
Searching from a completed report

To search the Completed Report list, use the following procedure: 1. 2. Follow Steps 1 to 2 of procedure Opening a completed report in this section. Select Options Search from the menu bar. The Search window (Figure 13-50) is displayed.
Figure 13-50 Search Completed Report window 3. Enter the search string of the completed report list that is required. By selecting the wildcard option the search string ends in a wildcard, the search string BSS with wildcard selected finds the next entry containing the term BSS, for example, BSS01. Searches can be performed either forwards or backwards through the list to the end or start. 4. Click Find to start the search. Click Cancel to abort the operation. If the Network Element found is one of several required, click Find again to search for the next. The original element found is still selected. Figure 13-51 shows a typical error message generated when searching a list.
Figure 13-51 Typical error message searching
EMOTOROLA LTD. 2000
1353
ISSUE 18 REVISION 0

Introduction
OMC Performance Management (PM) data can be accessed via a standard web browser, such as Netscape or Microsoft Explorer. This is an optional feature. This data is available in two formats: 1. 2. Text (ASCII) format. Tab-delimited, or delimited, format. This format allows reports to be post-processed, using tools which may be external to the OMC. NOTE The web server must be configured to serve delimited reports with a specific MIME type, namely text/tab-separated-values (with a .tsv suffix).
Procedure
To access PM report data use the following procedure: 1. 2. 3. 4. 5. 6. Using a web browser, connect to the OMC via the appropriate URL. A Username/Password dialogue box is displayed. Enter a valid username and password, and press Enter. The OMC Home page opens. Click on the Performance Management icon. A list of stored reports is displayed, see Figure 13-52. To select a report, click on the hyperlink associated with it. When a text (ASCII) report is selected, it opens within the web browser. When a delimited report is selected the result is dependent on the browser configuration. For example, on a PC with a spreadsheet application installed, the browser can be configured to automatically launch the application and load the report data directly into a spreadsheet, thus allowing the data to be processed further.
1354
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Figure 13-52 PM Reports page
EMOTOROLA LTD. 2000
1355
Modifying selections
ISSUE 18 REVISION 0
Modifying selections
Stored selections
A Selection (completed PM report window) may be saved and reused as a template. Opening a previously Stored Selection is performed from the Selections window.
Prerequisites
To open the PM Selections window, follow this procedure: 1. 2. 3. Access performance management, please refer to Accessing performance management in this chapter. From the PM opening window, Figure 13-53, highlight Selections. Click OK. Clicking Exit will abort the opening.
Figure 13-53 PM Opening window The Performance Management window (Figure 13-42) opens.
Procedure
To change the report criteria, perform the following procedure from the PM Selections Name window. NOTE Error/process messages may be displayed in the display bar at the foot of the Performance Management window (Figure 13-16). It is important to frequently refer to this area. 1. 2. 3. 4. 5. 6. Open a completed report window. Select the required Network Elements. To manipulate the Network Elements menu refer to Network elements and statistics menu in this chapter. Select the required Statistics. To manipulate the Statistics menu refer to Network elements and statistics menu in this chapter. Select the report options. Refer to Report options in this chapter. Select the start/end dates and times and interval mode. Refer to Start/end dates and times in this chapter. The report may be run by selecting Report Run from the menu bar or saved for later use. Refer to Saving a completed report in this chapter. NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000
1356
ISSUE 18 REVISION 0
Modifying graphical output

Prerequisites
Once a graphical report has been run it may be viewed in several formats, refer to Modifying the display below. A graphical report may also be converted to or from a tabular report, refer to Devices in this section.
Modifying the display

The display may be manipulated to achieve the required output in both graphical and tabular reports. The following options can be accessed from the Options menu: Sort (refer to Sort criteria). Filter (refer to Filter criteria). Data Scale Factor (refer to Data scale factor). Axis Scale Range (refer to Axis scale range). The 2D Line, 2D Bar, 3D Line and 3D Bar options (refer to Report options) are available from the Graphic menu.
Figure 13-54 Pareto (Graphical) report
EMOTOROLA LTD. 2000
1357
ISSUE 18 REVISION 0
Displaying devices
To display the Devices/Statistics/Days along the Xaxis in the report, select the Devices/Statistics/Days options from the menu at the bottom of the report window. The following message is displayed on the status bar:
Reformatting charts
The selected variable(s) are visible on the screen for both tabular and graphical output. Unselected variables will not be shown until re-selected.
Graphical
Select Graphical to change the format from Tabular to Graphical.
Tabular
Select Tabular to change the format from Graphical to Tabular.
Coverage
To display a graphical representation of the overall coverage for the statistics displayed, select Coverage On.
Stack
To place the statistics on top of each other in graphical format select Stack.
1358
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Devices
To display a device, use the following procedure: 1. Click Goto (Figure 13-55).
Figure 13-55 Report Device options 2. 3. Select the required device from list, as shown in Figure 13-56. Click OK to continue.
Figure 13-56 Goto device window
Devices
Click the right arrow (>) to move to the next device. Click the left arrow (<) to move to the previous device.
EMOTOROLA LTD. 2000
1359
ISSUE 18 REVISION 0
Statistics
To display a particular statistic, use the following procedure: 1. Click Goto (Figure 13-57).
Figure 13-57 Report Statistics options 2. 3. Click the required statistic from list, as shown in Figure 13-58. Click OK to continue.
Figure 13-58 Goto statistic window
Statistics
Click the right arrow (>) to move to the next statistic. Click the left arrow (<) to move to the previous statistic.
1360
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Days
To display a particular day (this may be used in non-continuous mode only) use the following procedure: 1. Click Goto (Figure 13-59).
Figure 13-59 Report Days options 2. 3. Select the required day from the list, as shown in Figure 13-60. Click OK to continue.
Figure 13-60 Goto day window
Days
Click the right arrow (>) to move to the next day. Click the left arrow (<) to move to the previous day.
EMOTOROLA LTD. 2000
1361
ISSUE 18 REVISION 0
Saving graphical reports

To save an unnamed graphical report use the following procedure: 1. 2. 3. Select File Save or Save As from the menu bar. A Save Report box is displayed (Figure 13-61). Enter the filename in the FileName field. Click OK to save the file. NOTE To enable the Format options on the Save Report box, select the Tabular options button to change the format from Graphical to Tabular. Refer to Displaying devices.
Figure 13-61 Save Report box (graphical)
1362
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
PM report scheduler
PM report scheduler
List of procedures
Performance Management reports may be scheduled using the PM scheduler. The following is a list of procedures that are performed using the Audit Scheduler Admin Option: S S S S S S Scheduling a report from Selection Name window. Scheduling a report from Admin. Modifying a report schedule. Deleting a report schedule. Printing a schedule list. Printing a Detailed View.
Reports may be scheduled to run at a particular time, or over a particular time period. NOTE If the OMC-R timezone incorporates a daylight-saving scheme where a one or two hour offset is applied to the OMC during the summer months, care should be taken not to schedule PM reports when the time is moved back at the end of the summer, they could accidently run twice; or when the clock is moved forward at the start of the summer, they might not run at all. The change from summer to winter time, or from winter to summer, usually occurs in the hours after midnight on a Friday, Saturday, or Sunday, depending on the country.
Scheduling a report from Selection Name window

To schedule a PM report from the PM Selection Name window, use the following procedure: 1. 2. 3. Open the Selection Name window, refer to Accessing Performance Management in this chapter. Complete the procedures in the Selection Name window, then select Report Schedule. The PM Report Scheduler window opens. To create a new PM report schedule, select File Create from the PM Report Scheduler window (Figure 13-63). The pmSchedule Detailed View window is displayed as shown in Figure 13-64. Enter the relevant details, (to create a report refer to Running a new report), Report Name, Status, Times, Modes, Output, Host/Display names and Owner. Save the scheduled report by selecting File Save. Close the pmSchedule Detailed View window by selecting File Close.
4. 5. 6.
EMOTOROLA LTD. 2000
1363
PM report scheduler
ISSUE 18 REVISION 0
Scheduling a report from Admin

To schedule a PM report from the Admin icon on the GUI Front Panel, use the following procedure: NOTE To create a scheduled report, a report must first have been created within Performance Management and the Performance Management function must have been invoked. See Accessing performance management in this chapter. 1. Select the Admin icon on the Front Panel to open the Admin Options window (Figure 13-62).
Figure 13-62 Admin Options window 2. Select PM Reports Scheduler, the selection is highlighted in black.
1364
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
PM report scheduler
3.
Click OK. The PM Reports Scheduler window, as shown in Figure 13-63, opens. This contains a list of all scheduled reports, detailing their Name, Status, Times, Modes, Output, Host/Display names and Owner.
Figure 13-63 PM Report Scheduler window 4. To create a new PM report schedule, select Edit Create from the PM Reports Scheduler window. The pmSchedule Detailed View window is displayed as shown in Figure 13-64. Enter the relevant details (to create a report, refer to section Running a new report in this chapter) Report Name, Status, Times, Modes, Output, Host/Display names and Owner. NOTE Check the status bar at the foot of the window for messages. 6. Save the scheduled report by selecting File Save.
5.
EMOTOROLA LTD. 2000
1365
PM report scheduler
ISSUE 18 REVISION 0
7.
Close the pmSchedule Detailed View window by selecting File Close.
Figure 13-64 pmSchedule Detailed View window
1366
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
PM report scheduler
Modifying a report schedule

To modify a created schedule, use the following procedure: 1. Select a report from the list on the PM Scheduler window.
Figure 13-65 PM Scheduler window 2. 3. 4. 5. 6. Select Edit Modify, as shown in Figure 13-65. The pmSchedule Detailed View window opens. Select Edit Edit from the menu bar. Change any details incorrectly entered in the Detailed View. Save and close the Detailed View.
EMOTOROLA LTD. 2000
1367
PM report scheduler
ISSUE 18 REVISION 0
Deleting a report schedule

To delete a report schedule use the following procedure: 1. 2. 3. 4. Refer to the Scheduling a report from Admin procedure and follow Steps 1 to 3. The PM Scheduler window opens (Figure 13-63). Delete the required schedule. Select File Delete. In the confirmation window click OK. Select FIle Close.
Printing a report list

To print a list of scheduled audits, use the following procedure: 1. 2. 3. 4. Refer to the Scheduling a report from Admin procedure and follow Steps 1 to 3. The PM Scheduler window opens. Select File Print from the PM Scheduler window. The print process is documented in the status bar. Close the PM Report Scheduler window by selecting File Close from the menu bar. Close the Admin Options window by clicking the Cancel button.
Printing a schedule detailed view

To print a schedule Detailed View, use the following procedure: 1. 2. 3. 4. Refer to the Scheduling a report from selection name window procedure and follow Steps 1 to 4. The pmSchedule Detailed View window opens. Select File Print from the pmSchedule Detailed View window. The print process is documented in the status bar. Close the pmSchedule Detailed View window by selecting File Close from the menu bar. Close the Admin Options window by clicking the Cancel button.
1368
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
PM reports logs
PM reports logs
List of procedures
The following is a list of procedures that are performed using the PM Reports Logs Admin Option: S S S S Viewing a PM reports logs list. Printing an Audit Log list. Deleting a PM Report. Viewing a PM Report.
Viewing a PM reports logs list

After a report has been generated, information relating to this report is placed in a report log. This information can be accessed and printed. To view a PM reports logs list, use the following procedure: 1. Select the Admin icon on the Front Panel to open the Admin options window (Figure 13-66).
Figure 13-66 Admin Options window 2. Select PM Reports Logs, then click OK.
EMOTOROLA LTD. 2000
1369
PM reports logs
ISSUE 18 REVISION 0
3.
The PM Reports Log window, as shown in Figure 13-67, is displayed. This contains a list of all completed reports.
Figure 13-67 PM Reports Logs window 4. Close the PM Reports Logs window by selecting File Close.
Printing an PM reports list

To print the PM Reports Logs list, use the following procedure: 1. 2. 3. Refer to the Viewing a PM reports logs list procedure and follow Steps 1 to 3. The PM Reports Logs window opens. To print the PM Reports Logs list, select File Print. The output is sent to the default printer. The printing process is detailed in the status bar. Close the PM Reports Logs window by selecting File Close.
Viewing a PM report
To view a PM report for a particular Scheduled Report, use the following procedure: NOTE To view a report from the Reports Logs List, the Performance Management Feature must be invoked. 1. 2. 3. 4. Refer to the Viewing a PM reports logs list procedure and follow Steps 1 to 3. The PM Reports Logs window opens. From the PM Reports Logs list, select the required report. The selected report is highlighted in inverse text. Select File Open from the menu bar. The PM report opens. Close the PM report by selecting File Close.
1370
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
PM reports logs
Deleting a PM report
To delete a PM report, use the following procedure: 1. 2. 3. Refer to the Viewing a PM reports logs list procedure and follow Steps 1 to 3. The PM Reports Logs List window opens. Select the report to be deleted. The selection is highlighted in inverse text. Select Edit Delete from the menu bar. A deletion confirmation dialogue box is displayed. It is also possible to select Edit Delete All if all the logs require deletion. Click OK to continue. Close the PM Reports Logs List window by selecting File Close.
4. 5.
EMOTOROLA LTD. 2000
1371
Running a PM report from the command line
ISSUE 18 REVISION 0

Running new PM reports
Running PM reports from the command line requires knowledge of the Applix command line utilities. The syntax for running a new PM report is as follows: applix add macro pmreport pass cmdl <argument(s)> <device type(s)><statistic(s)> NOTE When reports are run to file, a filename argument can be given, reportname. The following arguments are available: Table 13-5 Argument sdate edate stime etime tmode Description Start Date End Date Start time End time Time mode Format options <ddmmyyyy> <ddmmyyyy> <hh:mm> <hh:mm> blocked continuous discrete ASCII Spreadsheet 2DBAR 3DBAR 2DLINE 3DLINE paretotabular trendtabular paretographical trendgraphical screen file printer 60 30 PLMN NONE BSSRXCDR SITE CELL
EMOTOROLA LTD. 2000
reptype
ASCII or Spreadsheet Graphical
fmode
ASCII report Spreadsheet Graphical
output
Output type
res sumlevel
Resolution Summary level
1372
ISSUE 18 REVISION 0
Parameters
The <device type(s)> parameter can be: bss;rxcdr;site;gproc;cell;carrier;nbr;xbl;cbl;mtl;rsl; oml NOTE Device names are case sensitive. Summary level CELL is only applicable to carrier device type. The <statistic(s)> parameter can be: stat raw <raw_stat> (Raw statistics) stat custom <custom_stat> (Custom statistics) stat key <key_stat> (Key statistics) stat raw <raw_stat> stat custom <custom_stat> stat key <key_stat> (Raw, custom, and key statistics)
Examples
This example specifies that the PM report will start at 23:00 on 8th April 1997 and finish at midnight. The report will be in a pareto-tabular spreadsheet format, output to a file called test.out . It will contain raw and key statistics on all BSSs, SITEs and CELLs, summed up to BSSRXCDR level. applix add macro pmreport pass cmdl sdate 08041997 edate 08041997 stime 23:00 etime 00:00 tmode BLOCKED output file reportname test.out reptype spreadsheet FMODE paretotabular bss all site all cell all res 60 sumlevel BSSRXCDR stat raw rf_losses_sd_alloc_tch key sdcch_traffic The following example specifies that the PM report will start at 22:00 on 22nd June 1997 and finish at 23:00. The report will be a trend-tabular ASCII report, output to screen. It will contain raw, key and custom statistics on BSS-1 and all SITEs and CELLs. applix add macro pmreport pass cmdl sdate 22061997 edate 22061997 stime 22:00 etime 23:00 tmode CONTINUOUS output screen reptype ASCII FMODE trendtabular bss BSS1 site all cell all res 60 sumlevel NONE stat raw rf_losses_sd alloc_tch key sdcch_traffic custom test_stat NOTE When running the command line in C shell a \ is required as a line break. This is not required in bourne shell. Only one space is allowed between each option.
EMOTOROLA LTD. 2000
1373
ISSUE 18 REVISION 0
Stored selection
The syntax used to run a stored selection from the command line is as follows: applix add macro pmreport pass fs <stored selection name> Where: <stored selection name> is: The name of the stored PM report.
Completed report
The syntax used to run a completed report from the command line is as follows: applix add macro pmreport pass sr <reportName> .<loginName>.<yyyymmdd>.<hh:mm>.<Stats type>.<report type>
Example
In this example the Schedule1 completed report is run. The report was last saved by omcadmin at 19:22 on 24th September 1997. applix add macro pmreport pass sr Schedule1.omcadmin.19970924.19:22.CELL.txt
1374
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Performance management troubleshooting

Introduction to PM troubleshooting
This section contains a number of questions that are frequently asked by customers about performance management. The answers are supplied below.
Statistics
Where to find a description of each raw and key statistic?
The manual Maintenance Information: GSM Statistics Application GSM-100-503 gives a full explanation of each raw and key statistic.
How to change half-hourly statistic reporting to hourly statistic reporting?

This can be carried out using the following procedure: 1. Enter 60 in the Resolution field on the Performance Management window. Ensure that the number entered is a multiple of the basic reporting interval, that is, 30 minutes, otherwise the report will fail. Select Statistic Management Set Interval from the Selections window menu bar to open the Set Interval window. Refer to the Setting intervals procedure. This changes the value of the reporting interval to 60 or 30 in the PM_INFO table of OMC database. Perform a TTY session to the specific BSS and enter the following command: chg_element stat_interval <interval time in minutes> <Site No.> Heres an example: chg_element stat_interval 30 0 This will set the interval to 30 for Site 0 Verify that this interval is set by entering the following: disp_element stat_interval <site No.> 4. 5. Stop the OMC. The OMC can collect statistics files from network elements at 30 (default) or 60 minute intervals. This is controlled by an environment variable, PM_HOURLY_STATS, at the OMC. To set it to 60, login to the OMC and enter the following in an xterm window: setenv PM_HOURLY_STATS ON To revert back to a 30 minute collection interval enter the following: unsetenv PM_HOURLY_STATS 6. Start the OMC. NOTE Both the interval at the OMC and the statistic interval at the connected sites must be set at the same value, that is, both at either 30 or 60 minutes. If the values are different it is possible the Parser will reject the statistics file.
2.
3.
EMOTOROLA LTD. 2000
1375
ISSUE 18 REVISION 0
What are the different types of statistics and what do they mean?
There are six statistical data types: S S S S S S Counter: cumulative value is increased by n each time the statistic is pegged, the number of occurrences of an event within an interval. Gauge: reports current value of statistic. Duration: measures the duration of an event. Normal Distribution: records the number of times that a statistical element is at a specific value. Weighted Distribution: records the duration for which a statistical element is at a specific value. Counter Array: this is the same as a counter statistic, except it also includes a list of bin values. These are split into specified ranges or causes and are incremented with the total when the statistic pegged falls within their specific range or cause.
How does the OMC receive statistics?

Asynch initiates the upload of statistics files from the network entities on receipt of a file_NE_available event from that network entity. These events are routed through the OMC event manager router process. When a file has been successfully uploaded this process informs the parser to parse the uploaded statistics file by sending an ipc message to the parser. The parser process parses the uploaded statistics files, interpreting their binary format and storing the statistics in the database in a number of tables.
1376
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Which statistics are alarmable?

The following is a current list of alarmable stats: S S S S S S S S S S S S S S RF_LOSSES_TCH RF_LOSSES_SD ACCESS_PER_PCH MA_REQ_FROM_MSC MA_CMD_TO_MS_BLKD TOTAL_CALLS ALLOC_SDCCH ALLOC_SDCCH_FAIL ALLOC_TCH ALLOC_TCH_FAIL BUSY_TCH BUSY_SDCCH OK_ACC_PROC INTRA_CELL_HO INTRA_CELL_HO_LOSTMS INTRA_CELL_HO_RETURN OUT_INTRA_BSS_HO OUT_INTRA_BSS_HO_PRI_BLK OUT_INTRA_BSS_HO_LOSTMS OUT_INTRA_BSS_HO_RETURN OUT_INTER_BSS_HO OUT_INTER_BSS_HO_LOSTMS IN_INTRA_BSS_HO IN_INTER_BSS_HO
S S S
PM reports
What do Continuous, Blocked, and Discrete signify in a PM report?
Continuous: the report generated is of the whole duration from the start date/time to the end date/time, and all intervals of data in between are used. This can be used to monitor trend over a long period of time, for example, last week. Blocked: the report generated is for all days from start date to end date, and for all intervals between start time and end time for each day. This can be used to report on a specific duration, for example, a busy hour for each day. Discrete: the report generated for the start day and end day, and for all intervals between start time and end time for both days. This can be used to compare data of two specific days for the same interval span.
What is the difference between absolute and relative time mode?

The start date/time and end date/time is specified for all reports. Dates and times can be specified in one of the following ways: S S Absolute Mode: Dates and times in this mode are treated as normal. Relative Mode: Dates and times specified in this mode are treated as offset in the past from the current date and time. This is particularly useful for running reports periodically.
EMOTOROLA LTD. 2000
1377
ISSUE 18 REVISION 0
What is the difference between /0, ?, and N/A in PM reports?

On a report the symbols /0, ? or N/A may display as values for certain time intervals. The symbol /0 indicates a divide-by-zero error. This may occur when a key statistic is being calculated and a raw statistic divisor in the key statistic formula is equal to zero. The key statistic cannot then be calculated. The ? symbol is used to signify a null value, and indicates that no value was received for this statistic for this interval. In the case of key statistics it indicates that no value was received for one or more of the component raw statistics. It should be checked that all relevant statistics are enabled for the device. The N/A symbol means that the statistic in question is not applicable to the software release at the BSS. For example, certain statistics are new to GSR4, so a GSR3 BSS cannot report on these statistics. The values can be seen on graphical reports in GSR4 onwards by selecting Display Show Nulls from the menu bar on a graphical report.
How are PM reports run from the command line?

Refer to the procedure Running a PM report from the command line.
PMGUI.CFG file
What is the PMGUI.CFG file?
The pmgui.cfg file is in two locations in the directory structure. The pmgui.cfg file which is located at /usr/gsm/current/config is used for installation purposes only and can be ignored. The pmgui.cfg file which is referenced by the PM GUI is located in /usr/gsm/config/global . This contains the following definitions: PMGUI_DATABASE: this is usually set to omc_db. PMGUI_SSDIR: this is the directory into which graphical reports are saved from the PM GUI. It can be edited to reference a specific directory. NOTE Always ensure that the permissions are set correctly on this directory. PMGUI_TABDIR: this is the directory into which tabular, (ascii), reports are saved from the PM GUI. It is editable in the same way as PMGUI_SSDIR. PMGUI_DELDIR: this is the directory into which delimited reports are saved from the PM GUI. It is editable in the same way as PMGUI_SSDIR. PMGUI_CUSTOM_STATISTICLIMIT: this limits the number of custom statistics that can be defined. It is defaulted to 50, but can be edited. PMGUI_SHORTLISTLIMIT: this limits the number of stored selections that can be saved on the shortlist that displays when the stored selections list window is opened. It can be edited. PMGUI_TREND_LEGEND_LIMIT, PMGUI_PARETO_LEGEND_LIMIT, and PMGUI_PARETO_GROUP_LIMIT: these setting are used to display graphical reports. They are set to the optimum values for the current version of the software, so there should be no need to alter them. PMGUI_PRINTER: this is the name of the printer to which the PM GUI prints reports. It is defaulted to lp, which must be changed to a connected printer in order to print. PMGUI_STATISTIC_RANGE: these are the BER statistic bin ranges and should not be modified.
1378
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
PM_RESYNCH
When and why should PM_RESYNCH be performed?
This should be done to ensure that the information on network elements in the MIB and OMC databases are in sync. For example, if a new element is added to the network on the navigation tree this is not automatically be reflected in the OMC database, therefore the OMC database needs to be updated. To do this perform a pm_resynch on the new network element on the Navigation tree.
Informix
What to do if an informix environmental variable is not set
All the informix environment variables can be set up at once by sourcing the following file /usr/gsm/config/global/pmInfxUserConfig.csh .
FPOMCAUDIT file
What is logged in the pmguiaudit files and the fpomcaudit files?
The pmguiaudit file logs event in the PM GUI. The fpomcaudit files maintain a record of the interpretation of the statistics files by the Parser. To access it and see the Parser logging to it in real time, while in the /usr/gsm/logs directory enter: tail f /usr/gsm/logs/fpomcaudit<date + time stamp> This is an example of successful parsing of a statistics file:
951019111658 (25337) FP : FILE HEADER : NE Type 31 : NE Id 1 : Time 1995522 13:0:0:0 : Duration 1800: V 203 225 103 0
This is an example of unsuccessful parsing of a statistics file:

951019111658 (25337) FP : FILE HEADER : NE Type 31 : NE Id 1 : Time 1995522 13:0:0:0 : Duration 1800: V 203 225 103 0 951019111658 (25337) FP : Unable to add stats to the PM database, DB error FAIL. 2 code : 0
Sample reasons for unsuccessful statistic files: S S S S Invalid data in the file, for example an invalid number. Time stamp of the statistic file is outside the parser tolerance limit. Statistic file has already been parsed. Duplicate statistical values of a non-duplicate statistic.
What does Invalid duration signify in the fpomcaudit file?

The fpomcaudit files can be found at the following location: /usr/gsm/logs . An invalid duration message is displayed if the parser reads the header of a statistics file from the BSS and discovers that the interval at which statistics files are being sent up from the BSS does not match the interval at which the parser is expecting to receive them. For example, if the parser is set to receive statistics files every 30 minutes, it will not parse statistics files which arrive every sixty minutes from a BSS. In this case the unparsed statistics file will be written to a directory allocated to that NE underneath /usr/gsm/ne_data/raw_stats . The name of the unparsed file will be appended with .bad_header.
EMOTOROLA LTD. 2000
1379
ISSUE 18 REVISION 0
1380
EMOTOROLA LTD. 2000
Chapter 14
Recommended Operations
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
ii
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Chapter 14 Recommended Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction to recommended operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of chapter structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended methods of fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of fault management facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Methods of fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault management based on historical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Real-time fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of fault management setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating multiple CDE workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up the display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up users for FM activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up alarm subscriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up a blacklist subscription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up alarm paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up e-mail alarm facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up and maintaining OMC maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Investigating alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm context sensitive help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm help installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optimization of process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Review event history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of logging faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ways of logging faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Keeping manual logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS command logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command logging enable/disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Response logging enable/disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set the command logging variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documenting network changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Change request forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Implementing the change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Escalating fault management problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Escalating problems internally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Escalating problems to Motorola . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended performance management tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of recommended performance management tasks . . . . . . . . . . . . . . . . Examining key statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EMOTOROLA LTD. 2000
i
141 141 142 142 143 143 143 143 144 146 146 146 147 147 149 149 149 149 1410 1413 1413 1413 1414 1414 1415 1415 1416 1417 1417 1418 1418 1418 1421 1421 1422 1422 1422 1423 1423 1423 1423 1424 1424 1424 1425 1425 1426
iii
ISSUE 18 REVISION 0
Setting up performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing PM reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generating a report from the command line using Applix . . . . . . . . . . . . . . . . . . . Enabling and disabling neighbour cell statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring MTL connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hints for generating PM reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cleaning up PM data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cleaning up PM statistics data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cleaning up PM device naming data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manually parsing PM statistics files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resynchronizing PM databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definition of PM Resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automatic PM Resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manually resynchronizing PM databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking enabled statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure for checking PM enabled stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Motorola PM and FM tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of Motorota Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance Management tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Gathering Tool (DGT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Health Analyst (NHA) tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Analysis Tool (CAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Counting Tool (ECT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Trace Product (CTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . site_outage utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . dri_status utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . rtf_status utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking ISG 6525 packet switch health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking ISG 6525 packet switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring ISG packet switch statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CPU utilization threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing packet switch configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Route selection table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Port record list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking ISG 6560 MPRouter health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking ISG 6560 MPRouter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring ISG 6560 MPRouter statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CPU utilization threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DTE address mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . At the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . At the OMCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting the OML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Possible faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
1427 1427 1427 1428 1429 1430 1431 1431 1431 1433 1434 1434 1434 1434 1436 1436 1437 1439 1439 1440 1440 1440 1441 1441 1441 1441 1441 1442 1443 1443 1444 1444 1444 1445 1448 1449 1453 1454 1455 1455 1455 1456 1460 1461 1461 1461 1461 1463 1463 1464
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Load Management configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to Load managment configuration tasks . . . . . . . . . . . . . . . . . . . . . . . Backup BSS/RXCDR configuration database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deploy new BSS/RXCDR databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install new BSS/RXCDR database onto OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure a CSFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initiate download to BSS/RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enable/Disable database downloads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check all sites and devices after BSC/RXCDR reset . . . . . . . . . . . . . . . . . . . . . . . Unconfigure a CSFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fallback to old database at BSC/RXCDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling an upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of regular procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hourly procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended procedure list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chase actions on Critical Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chase actions on Major Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Daily procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended procedure list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Analysis of PM statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Examination of event logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Weekly procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended procedure list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NE database checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical database directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uploading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup NE directory format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Weekly meeting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Weekly system procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking OMC version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check software version at a NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check system after changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backups and archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Routine administration procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedures described . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manually initiate alarm and state resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schedule alarm and state resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schedule configuration audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check alarm and state resync logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check configuration audit logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking LAN connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the ping utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example of output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1466 1466 1467 1468 1469 1470 1471 1472 1472 1473 1473 1474 1476 1476 1477 1477 1477 1477 1478 1478 1478 1479 1479 1480 1480 1480 1481 1481 1482 1482 1483 1483 1483 1484 1484 1485 1486 1486 1486 1487 1487 1488 1488 1489 1489 1489
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
vi
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Introduction to recommended operations

Purpose of this chapter
This chapter provides recommendations on how to set up and operate the OMC applications. It is primarily focussed on providing recommendations relating to the Fault Management and Performance Management applications. Recommendations relating to System Administration and Configuration Management are supplied in Operating Information: Scaleable OMC System Administration (GSM-100-202) and Installation and Configuration: GSM System Configuration (GSM-100-403), respectively. Where appropriate, details of recommended tasks are provided as step-by-step procedures. Alternatively suggestions are supplied on the approaches which can be taken using OMC applications and other Motorola tools or utilities. Use this chapter in conjunction with Chapters 1 to 7, which provide basic information about the OMC system functions. Chapter 9 provides details of recommended PM and FM reports.
EMOTOROLA LTD. 2000
141
ISSUE 18 REVISION 0
Overview of chapter structure

This chapter has the following structure: S Fault management recommendations for: S Using the Fault Management application Setting up Alarm handling Logging faults Documenting system changes Escalating problems
Performance management recommendations for: Using the Performance Management application Setting up Cleaning up Resynchronizing PM databases Checking enabled statistics
S S
Useful Motorola tools and utilities Troubleshooting: Checking packet switch health Checking router health Checking DTE addressing Checking the OML Checking the LAN connection
S S
Load management configuration tasks Regular activities: Hourly procedures Daily procedures Weekly procedures Weekly system check procedures Routine administration procedures
Prerequisite
Throughout this manual, it is assumed that the Resync function has been enabled. For information on enabling the Resync function see Operating Information: OMC System Administration (GSM-100-202).
142
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Recommended methods of fault management

Overview of fault management facilities
Fault management operations can be carried out on most devices using the following: S S S Map. Refer to Device management from the map in Chapter 4. Navigation tree. Refer to Fault management from navigation tree in Chapter 2 for a list of devices which are supported from the Navigation tree. Alarm window (available from the Fault Management menu; some options can also be accessed from the alarm popup menu). Refer to Checking alarms from the network map in Chapter 3 for further details. Contained Devices window. Refer to Device management from a map in Chapter 4 for further details. Detailed Views. Refer to Viewing a detailed view from a map in Chapter 2 for further details. Using remote login to a BSS. Refer to Remote login in Chapter 4 for further details.
S S S
Methods of fault management

Fault management provides the means to isolate and minimize the effects of faults within the GSM network, and so enabling the network to operate in an efficient manner. Fault management can be handled in either of the following ways: S S Fault management based on historical data using performance statistics and event logs. Real-time fault management using alarms.
Fault management based on historical data

Use this method to identify faults on the network using the statistics generated by the network elements. The most effective interface to this statistical information is the PM GUI application, see Front panel icons in Chapter 1, and Chapter 7. Historical analysis can also be performed by: S S Post-processing event logs, see Using the event logging utilities in Chapter 3. The Event Counting Tool (ECT), Cell Analysis Tool (CAT), and Call Trace Product (CTP), see Motorola PM and FM tools in this chapter for further information.
Motorola offers additional tools to analyse statistical data, for example, MARS. Ask the Motorola local office for details.
EMOTOROLA LTD. 2000
143
ISSUE 18 REVISION 0
Real-time fault management

Use the real-time fault management method to monitor faults occurring on the network, by observing alarms and events as they occur. The following GUI functionality can be used to perform real-time fault management. These functions can be used separately, but they are integrated to enable the operator to identify and respond to an alarm quickly and efficiently.
Using subscriber mode map

Subscriber mode map takes advantage of the Consolidated alarms feature, which requires separate training before it can be fully employed in the OMC. The Subscriber mode map provides a high level view of the impact of faults in the network on subscribers. This is useful for background monitoring of alarm activity in a large network where the operator may be expected to perform activities other than alarm handling. When used in conjunction with the detailed consolidated alarm information, the Subscriber mode map provides an effective means of real-time fault monitoring. See Map display in Chapter 2 for further details.
Using device mode map

Device mode map provides an overview of the problems occurring at devices in the network. This is useful for background monitoring of alarm activity in a large network where the operator is expected to perform activities other than alarm handling. See Map display in Chapter 2 for further details.
Access to alarm detail

In Subscriber and Device modes access to the alarm detail is available from popup menu options. Subscriber and Device modes also allow access to recent event history on a selected device (see Displaying events with history or from now for an NE in Chapter 3), and access to an NE using Remote login (see Logging in remotely from a map in Chapter 2).
Using map display

If the operator is not completely dedicated to handling alarms using the Alarm windows, the map display can provide an effective means of fault monitoring. The map displays are also useful for operators on night shifts where staff levels are reduced and alarm occurrence reduced. In small networks where the number of NEs can be easily viewed in a map, this method can prove very effective.
Using Alarms Originating Within PLMN window

Display this alarm window by double clicking on the Alarm icon on the Front Panel. This window provides a single view of the alarms that are active in the network. The window reflects the detail of the alarm summary count values. When a new alarm arrives in the OMC it is routed to this window from where the operator can view and handle it appropriately.
144
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Using subscription lists alarm displays/event displays

Subscription lists and subscriptions underpin the map and alarm/event displays. They also have specific applications, such as in blacklists and paging. The subscription lists offer the ability to create specific views of alarms occurring in the network. They offer the flexibility of setting up alarm displays based on device, for example, All alarms for BSSSwindon. Alternatively, displays based on alarm type, for example, All critical MTL alarms in the network. The Alarm windows can be defined once, and then can be manually or automatically invoked by the AutoInit.CNFG file when the user logs in and displays the GUI. See Creation of auto initiation files in Chapter 3 for further details. Subscription lists can be used in a variety of ways due to their flexibility. However, Motorola suggest that a strategy for using Alarm and Event windows be adopted and maintained consistently according to the role of the operator within the OMC.
Using the Tools menu

A Tools menu can be created in the Alarm and Event windows. Menu options can be added to give access to key tools, such as: S S S S Full COP tool set. e-mail alarms. ECT or CAT. Customer specific tools.
See Creating a Tools menu in the Alarm and Event windows in Chapter 3 for further details. Standard menu options available within an Alarm window give the operator access to the primary functions required to act on alarms in the system.
EMOTOROLA LTD. 2000
145
Setting up fault management
ISSUE 18 REVISION 0

Overview of fault management setup
Motorola recommend the following facilities are set up to allow fault management to be used effectively and efficiently. 1. 2. 3. 4. Create multiple CDE workspaces for various fault management activities or displays. Configure map and subscription lists for automatic start up at login using the AutoInit.CNFG file. See Creation of auto initiation files in Chapter 3. Enable the FM Resync function so that it occurs automatically, see Logging in to the OMC in Chapter 1 for further details. Create a Tools menu and menu options in the Alarm and Event windows to allow operators to access useful features and utilities easily and quickly. For example, if the OMC utilities site_outage, dri_status, rtf_status are installed at the OMC, include them in an appropriate script and add them to the Tools menu. Operators can then use these to generate specific outage or device status reports. See Creating a Tools menu in the Alarm and Event windows in Chapter 3 for further details. Create a Tools menu and menu options in the Call Trace window. Display the Call Trace window from the Navigation tree. See Creating a Tools menu in the Trace View window in Chapter 4 for further details.
5.
Creating multiple CDE workspaces

Set up multiple CDE workspaces when a window (known as a CDE workspace) is required for each fault management activity an operator may need to monitor. For example, a high level map display can be open in one workspace, while a second workspace could contain the All Alarms window, and a third workspace could show SITE outage alarms, MTL outages, and so on. To create multiple CDE workspaces, follow these steps: 1. 2. 3. 4. Position the cursor/pointer in CDE panel. Press the right mouse button. A popup menu appears. Select Add Workspace. A new workspace is displayed on the CDE panel. In the GUI interface display the window or the information to be made into a workspace. For example, for a workspace to contain the Navigation tree, display the Navigation tree. Position the cursor in the top left corner of the window to be made into a workspace. Press the right mouse button. A popup menu is displayed. Select Occupy Workspace from the menu. The GUI window is now a workspace which you can open and close when needed from the CDE panel. Repeat until all the workspaces needed are created. NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000
5. 6. 7. 8.
146
ISSUE 18 REVISION 0
Setting up the display

One OMC Operator and two OMC SPARCstations should be allocated to each region. The SPARCstations should be divided into two distinct uses as follows: S One SPARCstation setup to monitor the events and alarms through the map. This monitoring SPARCstation should typically display a map of the region of the network being monitored, iconized event windows for each BSS and the Front Panel and an iconized OOS Device window for the network or region as necessary. See Figure 14-1. See Chapters 1 and 2 for full details of the Front Panel, and Map and Tree procedures. One SPARCstation for interactive operations such as Configuration Management and Performance Management, Remote Login sessions to Network Elements and Administration.
FRONT PANEL
ALL EVENT S MAP BSS's
OOS DEVICES
Figure 14-1 A recommended screen setup
Setting up users for FM activities

Command partitioning provides a means of dividing OMC users into different security areas. Depending on which security area a user has access to, functions are allowed or disallowed according to whether they could be used to alter OMC/BSS information. This provides a level of security that can be used to categorize users into work functions so that they can only access commands which are essential to their job role. It also improves OMC usability by giving users a smaller, easier and more applicable selection of menu options from which to choose. Only the GUI is command partitioned. OMC UNIX scripts are unchanged. Motorola recommend that users are set up with the permissions shown in Table 14-1. Use this information when completing the User Profile Detailed view window. Also see Access control in Chapter 6 for full details on how to set up command partitioning.
EMOTOROLA LTD. 2000
147
ISSUE 18 REVISION 0
Table 14-1 Recommended Setup for FM users Activity Enable/ Disable Permissions Not necessary for FM Supervisor/ Operator Supervisor Description of activity All action options under Load Management in the GUI TTY and batch Rlogin Changes to the subscriptions and subscription lists Handle alarms option in Alarm window Device administration of BSS devices after creation Enable/Disable statistics on BSS via GUI Create, save, and delete options under network icon Create/delete/edit of all detailed views/commslink Cell parameter propagation Audit scheduler and logs. All audit and PMresync options via GUI Resync scheduler and logs options listed Change command partitioning options for all users Modify blacklist and pager subscriptions. Enable/disable event logging
Load Management Disable (LM)* BSS Remote Login (RLog)* Subscription Management (Subs)* Alarm Handling (Alarms)* Enable Enable
Enable
Supervisor/ Operator Supervisor/ Operator Supervisor/ Operator (optional) Supervisor/ Operator (optional) Not necessary for FM Not necessary for FM Not necessary for FM FM Supervisor Not necessary for FM Not necessary for FM
Fault Management Enable commands (FM)* Statistics Management (Stat) Map Management (Map)* Enable
Enable
Configuration Disable Management (CM) Cell Propagation (cellProp) Audit Disable Disable
Resync Access Control (Access) OMC Administration (Admin) ConfiDialog Call Trace
Enable Disable
Disable
Disable Enable
Not necessary for FM Supervisor Enable Call Trace operation from the GUI
* Indicates suggested for FM operator/supervisor The user profile should reflect the activities of the role being performed. For example, an FM Supervisor should have the ability to modify subscriptions.
148
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Setting up alarm subscriptions

If Alarm windows are being used at the BSS/RXCDR level for fault monitoring, they can be set up to meet the exact needs of the FM operators using event management subscription lists. For example, the following subscriptions to alarms can be set up for monitoring BSS/RXCDR alarms by severity: S S S S S Critical Alarms Major Alarms EAS Alarms Minor Alarms with a threshold of 5. Warning Alarms with a threshold of 10.
A separate event subscription list for each BSS/RXCDR should be set up to subscribe to All Events. These windows should normally be opened and iconized. The order in which the icons are arranged on the screen can reflect the order of importance of the Network Elements. For example, a BSS in a densely populated area with high traffic volume is probably more important than one in a rural area with lower traffic density. When more than one event occurs, the operator can then quickly assess the priority to deal with the faults. It is also useful to have a dedicated subscription list for OMC alarms (System Processor, Disk Space, Parser and EM Disconnected) that can be monitored by the System Administrator. See Chapter 3 for information on viewing and setting the event subscriptions.
Setting up a blacklist subscription

A blacklist subscription can be set up to protect an operator from seeing alarms that require no action. Blacklist subscription lists in Chapter 3 describes how to do this. However, as all alarms generated by the system may indicate a fault, extreme care should be taken before blacklisting any alarms. Motorola recommend that blacklists are only set up following discussions with the Motorola local office. In general, the use of blacklists should be avoided.
Setting up alarm paging

Alarm paging allows the creation of a Paging list for out-of-hours alarm handling support. Once set up, alarm paging notifies the on-call holder of the pager when a particular alarm occurs. See OMC paging list in Chapter 3 for further details.
Setting up e-mail alarm facility

This function allows selected alarms to be e-mailed to an specific OMC user. This facility is useful when fault management problems need to be escalated to more experienced OMC users. See Sending alarms to an e-mail address in Chapter 3 for further details.
EMOTOROLA LTD. 2000
149
ISSUE 18 REVISION 0
Setting up and maintaining OMC maps

For further information refer to Installation & Configuration: GSM System Configuration GSM-100-403.
Adding user defined regional map

To add a user defined regional map, follow these steps: 1. 2. 3. 4. Select the Maps icon on the Front Panel to open the Map List window. Select Edit Create to open a blank map detailed view. Enter the required information in the detailed view. Select File Create to add the map to the Map List.
Installing a new map background file

To install a map background file on the OMC, follow these steps: 1. 2. At the system processor, login as omcadmin. Open a shell and change to the directory containing the map background files. To do this, type the following command: cd /usr/gsm/config/global/maps 3. Load the tape containing the map background file into the processor tape drive and enter the command: tar xvfop /dev/rsto. 4. 5. Verify that the map background file has been loaded into the directory with the .map extension. Copy the map into the directory: /usr/gsm/config/global/maps
Adding and Changing a map background

To change a background to a map, follow these steps: 1. 2. 3. 4. 5. 6. 7. Select the Maps icon on the Front Panel to open the Map List window. Select the required map. Select Edit Detailed View to open the Map detailed view. Select Edit Edit. Delete the name in the Map Background field and add a new background map file name. Select File Save to save the new configuration. Select File Close to close the detailed view.
1410
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Adding a map node

To add a map node, follow these steps: NOTE This should only be done manually for the top level of the network. Anything below BSS level is catered for by audit. 1. 2. 3. 4. 5. 6. Select the Maps icon on the Front Panel to open the Map List window. Double click on a map name to open a map. Select Edit Map Node Create, the MapNode detailed view opens. Add the X and Y coordinates of the node then click on the Source Node button to open the Navigation tree. Double click on an instance button of the NE to be added to the map. The MapNode detailed view is reopened. Select File Create, and then File Close to add the new node to the map.
Deleting a map node

To delete a map node, follow these steps: NOTE This should only be done manually for the top level of the network. Anything below BSS level is catered for by audit. 1. 2. 3. 4. 5. 6. 7. Select the Maps icon on the Front Panel to open the Map List window. Double click on a map name to open a map. Select the map node to be deleted. Select Edit MapNode Detailed View to open the MapNode detailed view. Select Edit Edit. Select File Delete, a confirmation dialogue box opens. Click OK to delete the map node.
EMOTOROLA LTD. 2000
1411
ISSUE 18 REVISION 0
Add links to a map

To add links to a map, carry out the following procedure: NOTE This should only be done manually for the top level of the network. Anything below BSS level is catered for by audit. 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. Select the Maps icon on the Front Panel to open the Map List window. Double click on a map name to open a map. Select Edit Map Link Create to open the MapLink detailed view. Click on the Source CommsLink button to open the CommsLink list. Click on the Node A button to open the Navigation tree. In the Navigation tree double click on an instance button of the CommsLink element to be added. Double click on the required CommsLink in the list to reopen the CommsLink list. Click on the Node B button to open the Navigation tree. In the Navigation tree double click on an instance button of the CommsLink element to be added. Double click on the required CommsLink in the list to reopen the CommsLink list. Click on the Apply Filter button to add the CommsLink to the list. Double click on the required CommsLink in the list to open the Map Link detailed view. Select File Create to create the map link. Select File Close to close the detailed view.
Delete links from a map

To delete links from a map, carry out the following procedure: 1. 2. 3. 4. 5. 6. Select the Maps icon on the Front Panel to open the Map List window. Double click on a map name to open a map. Select Edit MapLink Detailed View to open the MapLink detailed view. Select Edit Edit. Select File Delete, a confirmation dialogue box opens. Click OK to delete the map link.
1412
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Alarm handling
Alarm handling
Alarm notification
The OMC operator is made aware of any alarm in the network from the Map Nodes and Links by changing colours and flashing icons. An alarm summary and alarm indication icon is displayed on the Front Panel and an audio alarm is sounded if enabled. Device Status is obtained from the network map but can also be obtained from the Navigation Tree, and remote login to a NE (Batch and TTY).
Investigating alarms
Before taking action to rectify a fault, obtain more information about the fault. Information can be obtained from the following: S S S S S S Opening the next level map to isolate the problem to a specific SITE at the NE. See Viewing map levels in Chapter 2. Opening an Alarm window for the NE or SITE from the map. See Checking alarms from the network map in Chapter 3. Check the alarm comment field to see if a comment has been added previously. See Using the alarm comment field in Chapter 3. De-iconizing the event window associated with the NE where the fault is occurring. See Opening an alarm/event window from Event Mgmt in Chapter 3. Obtaining a report on OOS devices for the alarmed BSS/RXCDR or SITE. See Displaying OOS devices from the navigation tree in Chapter 2. Viewing configuration and status of alarmed devices from the Navigation Form and Detailed View Forms. See Checking device status from the navigation tree in Chapter 2. If applicable, displaying the Traffic Channel Form or MMS Status. See Using Forms in Chapter 4 for the relevant procedures. Remotely logging into BSC/RXCDR from the map to obtain a state report or to execute other MMI commands. See Logging in remotely from a map in Chapter 2. Getting PM reports, as appropriate (on the second terminal). See Performance management: overview in Chapter 7 for Performance Management information.
S S
EMOTOROLA LTD. 2000
1413
Alarm handling
ISSUE 18 REVISION 0
Alarm handling
Initiate the following after information about the fault has been obtained: S S Log fault time, symptoms and operator name in the Fault Log. Take action to clear the fault. Clearing the fault involves action from the OMC (for example, resetting a device), contacting Field Support Engineers or the Link Operator. S If more than one fault occurs at a time, deal with the highest priority fault first. Highest Priority implies a fault affecting the greatest number of subscribers, therefore highest loss of call revenue. If the fault is not cleared within a pre-defined period, perform escalation procedure. Contact the Local Motorola Office (or the Motorola Customer Support Centre (MCSC)) if further assistance is required. Update the alarm comment field with any actions taken. Log the clear time and details of action taken.
S S S S
For information on alarm handling refer to Maintenance Information: Alarm Handling at the OMC, (GSM-100-501).
Alarm context sensitive help

Context sensitive alarm help provides on-line context sensitive information on any selected alarm when alarm handling. To access context sensitive help use the following procedure: 1. 2. 3. In the alarm window, select the alarm which requires enquiry. The alarm is highlighted. Click the right mouse button, the popup menu is displayed (as shown in Figure 14-2), select Help from the menu. The Worldview window for the selected alarm is displayed. Select File Close to close the window. NOTE The Worldview on-line document has a Notes facility where the operator can enter notes on the alarm handling information contained. This information is stored with the Worldview file and can be viewed or edited by other operators.
1414
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Alarm handling
Figure 14-2 Accessing the context sensitive alarm information
Alarm help installation and configuration

Refer to manual Installation & Configuration: OMC Clean Install, (GSM-100-413) for further information on installing Alarm Context Sensitive Online Help.
Optimization of process
The aim of the OMC operator should be to ensure that the network, as represented by the nodes and links on the map, is maintained in an error free state. Therefore the model of the network (MIB) must be kept up-to-date and all alarms handled and cleared as soon as possible. All service affecting faults should be tracked and logged. Remember to read the manuals and Online Help. Familiarity with the network components make the network easier to operate.
EMOTOROLA LTD. 2000
1415
Alarm handling
ISSUE 18 REVISION 0
Review event history

To get a better understanding of the cause of the alarm, when the alarm cannot be cleared using the standard procedures, the event history needs to be reviewed. All the recent events associated with the selected alarm are displayed. To display recent event history at a network element from a map or the Navigation tree, follow these steps: 1. 2. 3. 4. 5. 6. 7. 8. Select the network element icon that generated the alarm. Press the right mouse button to display a popup menu. Select Alarms to display the alarm window. Select the alarm required to display event history. Press the right mouse button to display a popup menu. Select either Events With History, or Events from Now. Find out the date/time of alarm from selected alarm in Alarm window. Search the event history window for alarms around that time.
1416
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Overview of logging faults
Overview of logging faults

Ways of logging faults
Faults and the correction of faults need to be logged for audit trail purposes. Faults and fixes can be logged in the following ways: S S Manually using logbooks, forms, or spreadsheets. See Keeping manual logs for further details. Automatically by the OMC using log files. See BSS command logging for further details.
Changes made to the network should also be logged. See Documenting network changes for further details.
EMOTOROLA LTD. 2000
1417
Keeping manual logs
ISSUE 18 REVISION 0
Keeping manual logs

Procedure
All operator activities at the OMC should be manually logged. It is particularly important that every occurrence of a Critical or Major alarm is logged and the related action to this alarm is logged. The time the alarm occurred, and the time it is cleared should be logged. The name of the operator and the names of any associated people should also be indicated in the log. The alarm comment field (see Using the alarm comment field in Chapter 3) should also be updated any time actions are taken relating to a particular alarm. Include information on cause of the alarm, if known, and how it was dealt with. Many spreadsheet options are available for PC use, or it may be preferable to maintain a handwritten logbook.
Typical logs
The following diagrams display two typical log pages, Figure 14-3 and Figure 14-4.
1418
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
EMOTOROLA LTD. 2000

Entity SIT E BSC/CELLName B10 B10/4 B10/20 B10/157 B10/35 B10/57 B1018 B10/34 B10/34 B09 B09/122 B09/122 B09/122 B09/165 B09/165 B09/165 X04 X04 B10 B10 B10 B10/4 B10/20 B10/157 B10/35 B10/57 B10/18 Necton Ickeburgh Castle Acre Bernie Arms West Lynn Kings Lynn KINGS LYNN X X X X X X KINGS LYNN KINGS LYNN DEREHAM DEREHAM Fakenham X X 14 254 0 14 254 MSS 9 0 MT L 0 0 MSI 5 Fakenham X X Fakenham X X Watton X X Watton X X Watton X X DEREHAM X 254 Cockley X X MMS 6 Device failed Down due to change GPROC, AIB, T 43 Down due to change GPROC, AIB, T 43 Down due to change GPROC, AIB, T 43 Down due to change GPROC, AIB, T 43 Down due to change GPROC, AIB, T 43 Down due to change GPROC, AIB, T 43 0 MSI 9 Bit error OOS threshold exceeded Device failed Signalling link OOS Bit error OOS threshold exceeded 0 MMS 5 Device failed Out due to 0 MT L 0 Out due to 0 MT L 0 Out due to 0 MT L 0 Out due to 0 MT L 0 Out due to 0 MT L 0 Out due to 0 MT L 0 Clockley X X Ickeburgh X X Necton X X Bernie Arms X X Castle Acre X X West Lynn X X Kings Lynn X X KINGS LYNN X A B C D Planned Outage due Outage Cr-no min Opto Alarm Device MW T ype T ype/id ALARM OR EVENT (SW initiated resets) OMC/RXCDR/BSS/MT L/OML/SIT E/CELL 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 LK BF SF NBG MR LK T W AT AT JFK JFK JFK JFK JFK JFK JFK LK LK LK LK LK MJ MJ MJ MJ MJ MJ
Event T ime
Sign
Clear Sign T ime
0.00
LK
0.41
0.00
LK
1.06
0.00
NBG
1.46
0.00
NBG
1.52
0.00
MR
2.30
0.00
BW
4.26
0.00
DCW 3.09
0.00
AT
3.54
0.00
AT
3.56
3.56
BT
4.10
3.56
BT
4.37
3.56
BT
4.39
NET01 (OMC02): OMC Network Operations
3.56
BT
4.42
3.56
BT
4.40
3.56
BT
4.42
3.56
BT
4.45
Figure 14-3 Typical Log page 1
10.06
LK
10.06
10.06
LK
10.19
10.08
LK
10.11
10.08
LK
10.20
10.08
LK
10.20
10.08
MJ
10.20
10.08
MJ
10.20
10.08
MJ
10.20
10.08
MJ
10.20
10.08
MJ
10.20
Keeping manual logs
1419
10.08
MJ
10.20
Keeping manual logs
1420
GSM KGA Work Order Mol Help T rouble Report Motorola Cct. No. CELL OUT AGE Not planned Planned 1.06 1.46 1.52 2.30 4.26 3.09 3.54 3.56 0.41 0.43 0.46 0.44 0.46 0.49 0.12 0.12 0.12 0.12 0.12 0.12
ACT ION T AKEN BY OPERAT OR, CFE OR SW Lock (NMC Initiated resets), (Automatiic fault clearing) Unlock
OUT DUE T O RET ROFIT MOT OROLA
10
11
12
13
NET01 (OMC02): OMC Network Operations
14
15
16
Figure 14-4 Typical log page 2
17
CLEARED IT SELF
18
CLEARED IT SELF
19
Down due to X04 failure
20
21
22
CLEARED BY IT SELF
23
CLEARED BY IT SELF
24
CLEARED BY IT SELF
25
CLEARED BY IT SELF
EMOTOROLA LTD. 2000
26
CLEARED BY IT SELF
ISSUE 18 REVISION 0
27
CLEARED BY IT SELF
ISSUE 18 REVISION 0
BSS command logging
BSS command logging

Introduction
The BSS command logging function enables logging of both BSS MMI commands and BSS MMI responses at the OMC. To change parameters, send commands to a BSS, using the the Navigation Tree or TTY, and Batch methods. Responses to these commands are returned to the OMC. Enable or disable logging of these commands and responses as required. Changes made via the Navigation tree are not logged with BSS command logging.
Command log example

*** Session 1 Log User: omcadmin Host: lismib1 Session: 1 ***
Time: 09:45:05 User: omcadmin Response: MMIRAM 0115 > Time: 09:45:41 Source: Forms Command: state bsc SITE 0 0 0
User: omcadmin
Session: 1
Time: 09:45:42 User: omcadmin Session: 1 Response: STATUS INFORMATION: Device: SITE 0 0 0 Administration state: UNLOCKED Operational state: BUSY Reason code: NO REASON Time of last transition: Tue Jan 27 20:25:25 1998 Related Device/Function: None END OF STATUS REPORT MMIRAM 0115 > *** Session 1 Log User: omcadmin Host: lismib1 Session: 1 ***
Time: 09:45:57 User: omcadmin Response: MMIRAM 0116 > Time: 09:46:20 Command: disp_dte Source: TTY
User: omcadmin
Session: 1
Time: 09:46:20 User: omcadmin Response: BSC DTE addresses: Address #0: 23466811570001 Address #1: 23466811570001 Address #2: 23466811570001 Address #3: 23466811570001 OMCR DTE addresses: Address #0: 23466823020041 Address #1: 23466823020042 Address #2: 23466823020061 Address #3: 23466823020062 Address #4: 23466823020000 Address #5: 23466823020099 Address #6: Zero length address Address #7: Zero length address CBC DTE address: Address #0: Zero length address BSC CBC DTE address: Address #0: Zero length address MMIRAM 0116 >
Session: 1
EMOTOROLA LTD. 2000
1421
BSS command logging
ISSUE 18 REVISION 0
Command logging enable/disable

To check whether or not command logging is enabled or disabled, type the following command in an Xterm window: env | grep RL To disable logging of BSS commands, log in to the system processor and set the environmental variable RL_LOGCMDS to NO, by editing the appropriate line in the /usr/gsm/config/global/sysProcConfig.csh file: setenv RL_LOGCMDS NO The default value of the command logging environment variable ( RL_LOGCMDS ) is YES. To enable command logging, edit the line in the sysProcConfig.csh file to read: setenv RL_LOGCMDS YES
Response logging enable/disable

The default value of the response logging environment variable ( RL_LOGRESPS ) is NO. To enable logging of BSS responses, set the environmental variable RL_LOGRESPS to YES, by editing the appropriate line in the /usr/gsm/config/global/sysProcConfig.csh file: setenv RL_LOGRESPS YES To disable response logging, edit the line in the sysProcConfig.csh file to read: setenv RL_LOGRESPS NO The variable RL_LOGCMDS takes preference over the command RL_LOGRESPS, therefore if RL_LOGCMDS is set to NO, and RL_LOGRESPS is set to YES, BSS commands and responses will not be logged. NOTE For changes made to the /usr/gsm/config/global/sysProcConfig.csh file to take effect, the OMC must be stopped and restarted. See the procedure Restarting the GUI. For further information on RL_LOGRESPS and RL_LOGRESPS refer to Operating Information: OMC System Administration, (GSM-100-202).
Set the command logging variable

All log files are stored on the single processor in the directory $OMC_TOP/logs/bss . There is only one log file per BSS, per day, which is created by the first session and appended by subsequent sessions. The same file is used for TTY and Forms sessions. When the designated directory is not available, the default directory is /usr/tmp . To set the path to the log directory, use the command logging environment variable RL_BSSLOGDIR as follows: setenv RL_BSSLOGDIR $OMC_TOP/logs/bss To view log files at the system processor or a MMI processor, change to the $OMC_TOP/logs/bss directory and use a text editor. For further information on RL_BSSLOGDIR refer to Operating Information: OMC System Administration, (GSM-100-202).
1422
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Documenting network changes
Documenting network changes

Background
As the size of the network increases, additional equipment and changes to the frequency plan will be required as determined by the Network Planning Engineers. Procedures must be devised to enable the OMC operator to introduce the changes into the network with minimal disruption of services.
Change request forms

It is recommended that documents be prepared to ensure smooth implementation of system changes, and to record details of the changes made. The following forms fulfil the requirements: S S S A Change Request form, which supports the administration of the change. A Change Request Info form, which provides a summary of the information associated with the proposed change. A Result From Implementation form, which is to be completed after the change has been made. It will provide an official record of the result of the change and the actual impact on the network.
The Network Planning Engineers should also provide documented procedures for the implementation of changes.
Implementing the change

There is no generic procedural script available to implement changes. To implement system changes, carry out manual procedures, such as: S S Check that the correct version of the database resides at the OMC. Ensure that a fallback database is available when enabling statistics.
EMOTOROLA LTD. 2000
1423
Escalating fault management problems
ISSUE 18 REVISION 0
Escalating fault management problems

Escalating problems internally
To facilitate the escalation of issues, the OMC provides the ability to: S e-mail alarms to another user from the Alarm windows. For example, e-mail alarms of a particular severity to a supervisor. See Sending alarms to an e-mail address in Chapter 3 for further details. Automatically call a Paging device when a specific alarm is received at the OMC. For example, this pager could belong to a technical user or a member of the Motorola support staff. See OMC paging list in Chapter 3 for further information. Remote login and use the Data Gathering Tool (DGT) to gather essential information about the problem. See Remote login in Chapter 4, and, if available, the Data Gathering Tool (DGT) documentation for further information.
Escalating problems to Motorola

A formal escalation process should be established between operating organizations and the Motorola local office. Ensure details of problems are passed on at all stages of the occurrence. This helps to build up a profile of the problem. If necessary, this problem profile can be passed to the Customer Network Resolution Centre at Motorola in the form of a Service Request (SR). The Data Gathering Tool (DGT) can also be used to collect vital information about a problem. See Motorola PM and FM tools later in this chapter for more details of DGT. Motorola recommend that operating organizations use a similar form to that used by CNRC for SRs. This ensures that all the necessary information about the problem is captured. Operating organizations can then log this form efficiently and, if necessary, send it to the Customer Network Resolution Centre.
1424
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Recommended performance management tasks

Overview of recommended performance management tasks
Generating reports
The performance management application provides the ability to generate a wide range of reports based on the statistics generated by the network elements. These statistics are stored at the OMC for a maximum of seven days. After seven days the statistics are automatically deleted by the omc_db_maint script. The OMC provides a PM GUI interface to enable the user to take advantage of existing Key Statistics and Network Health reports, or to create customized statistics reports (see Running a new report in Chapter 7 for further details). Chapter 9 gives details of recommended performance management reports. Raw statistics data is gathered hourly or half-hourly by the OMC. The PM GUI allows access to these statistics using Motorola Key Statistics and Network Health reports. Alternatively, an operator can create custom reports using the PM GUI and raw statistics. An operator can harness a variety of statistics using statistical reports. These can be set up to run automatically at regular intervals using the PM Scheduler (see PM report scheduler in Chapter 7 for further details). The reports can then be reviewed to assist in the identification of faults or to highlight abnormal system behaviour when compared to the normal pattern. A comprehensive list of reports is provided in Chapter 9. If used regularly for monitoring the same data values, the PM GUI enables operators to understand the activity in the network. The Motorola OMC PM application provides a much greater level of detail for the radio subsystem performance because it takes advantage of performance counters at the carrier level. Therefore the PM application provides a very effective means of performing detailed analysis of faults and optimization data within the BSS subsystem.
Motorola PM tools
The Network Health Analyst (NHA) provides an intelligent reporting tool for identifying problems in the network by interpreting statistics, alarms, and events. This includes a number of reports to assist in troubleshooting problems. Motorola also provides a Cell Analysis Tool (CAT) for specific fault finding on cells. CAT is part of the Cell Optimization Product (COP) product, and is used for detailed analysis of cell activity. Motorola offers additional optimization services such as the Intelligent Optimization Service (IOS). The MARS (Motorola Analysis and Reporting System) provides the ability to store and analyse long-term statistics, Details of these can be obtained from the Motorola local office.
Database information
The PM Database Schema is also supplied with each OMC software release and allows an operator to extract data by other means, such as using a third party product which provide custom interfaces to the OMC database. See Technical Description: OMC Database Schema (GSM-100-313) for further details.
EMOTOROLA LTD. 2000
1425
ISSUE 18 REVISION 0
Examining key statistics

The most important Performance Management (PM) statistics are the Key Statistics which should be examined daily. Each morning, print out and examine the Key Statistics for the previous 24 hours, and identify any readings that deviate from normal. For example: S S A low total_calls reading could indicate a potential problem and a high reading could indicate a need for additional capacity. High RF losses at a cell associated with a particular BTS should be investigated as it could indicate an antenna problem.
1426
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Setting up performance management

Preparing PM reports
The recommended procedure for preparing PM reports is: 1. 2. Identify a set of reports to be produced regularly, see Chapter 9 for a list of some of the reports. Create the reports using the PM GUI, see Running a new report in Chapter 7 and Chapter 9 for further details. To create periodic reports Motorola recommend the use of Relative Interval Mode. Schedule the reports to run at regular intervals using the PM Scheduler option in the Front Panel Admin Options window. The schedule can be printed and reviewed. See PM report scheduler in Chapter 7 for further details.
3.
Generating a report from the command line using Applix

To generate individual reports from the command line, use the following Applix command: applix add macro pmreport pass fs <report_name> The options available are: fs creates a report based on the full selection of the parameters selected. sr uses an existing stored report. cmd enables specific parameters to be included in the report. See Running a PM report from the command line in Chapter 7 for further information about using the Applix command.
EMOTOROLA LTD. 2000
1427
ISSUE 18 REVISION 0
Enabling and disabling neighbour cell statistics

Before generating reports for neighbour cells, enable the statistics for the neighbour cells. The statistics for the neighbour cells are generated until disabled. To enable or disable neighbour cell statistics, follow these steps: 1. 2. 3. 4. 5. 6. 7. From the PM GUI, click the Project Management icon. Select File New from the menu bar. Select Device Type Neighbour from the menu bar. Select the network element next to the neighbour cell. Select the neighbour statistic or statistics to be enabled or disabled in the Statistics window. Select Statistics Mgmt from the menu bar. Select Enable to enable the selected statistic for the neighbour cell, or select Disable to disable the statistic.
The statistic or statistics are generated for the neighbour cell. Reports can now be generated using these statistics.
1428
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Monitoring MTL connectivity

To monitor real-time MTL connectivity, follow these steps: 1. Create an Alarm subscription list (see Managing subscription lists in Chapter 3 for further details) with a meaningful name. For example, name the subscription list MTLConnectivity. Create an alarm subscription to contain the following information (see Managing subscriptions in Chapter 3 for further details): Device Instance: PLMN Event Type: CommunicationFailure Severity Type: Critical Error Id: 0. MTL: Signalling Link Failure See Maintenance Information: Alarm handling at the OMC (GSM-100-501) for further details of alarm error ids. 3. Create an alarm subscription to contain the following information: Device Instance: PLMN Event Type: CommunicationFailure Severity Type: Critical Error Id: 0. BSS: Last MTL Link Failure Signalling Point Inaccessible 4. Create an alarm subscription to contain the following information: Device Instance: PLMN Event Type: CommunicationFailureEvent Severity Type: Critical Error Id: 0. MTL: Signalling Link Failure 5. Create an alarm subscription to contain the following information: Device Instance: PLMN Event Type: CommunicationFailureEvent Severity Type: Critical Error Id: 0. BSS: Last MTL Link Failure Signalling Point Inaccessible The alarm subscription list window now provides an overview of activity on the MTL links for the entire network.
2.
EMOTOROLA LTD. 2000
1429
ISSUE 18 REVISION 0
Hints for generating PM reports

Use the following facilities when creating customized reports. For a list of recommended reports and details of how to create them, see Chapter 9.
Searching for a statistic

To find a statistic for use in a report, use the Find feature. To use the Find feature to search for a statistic within the PM GUI, follow these steps: 1. 2. 3. 4. 5. 6. Position the cursor in the PM GUI. Select a network element. Position the cursor in the Statistics window. Press the right mouse button to display a popup menu. Enter the name of the statistic to search for, for example, TOTAL_CALLS. Click Find to start the search. When the statistic is found it is highlighted for selection. See Running a new report in Chapter 7 for further details about the Find option. See Maintenance Information: GSM Statistics Application (GSM-100-503) for a list of all statistics.
Filtering report lists

The filter option in the PM GUI allows devices and statistics to be selected in sequence by providing a second window in which to enter selections. This makes it easier to build up complex queries. To select devices and statistics in sequence, follow these steps: 1. 2. 3. 4. 5. Position the cursor in the PM GUI. Select a network element or a statistics list. Press the right mouse button to display a popup menu. Enter the filter string in the Filter String field, for example, BSS05 or TOTAL_CALLS. Click Filter. See Running a new report in Chapter 7 for further details of the Filter option. From the same popup menu, use the Filter option as an easy method of making selections for the report.
1430
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Cleaning up PM data
Cleaning up PM data
Cleaning up PM statistics data
The file /usr/gsm/config/global/pmgui.cfg contains environment information required to set up PM GUI operation, such as default paths and report limitations. The directories listed in the pmgui.cfg file must be regularly cleaned up and, where necessary, any important reports must be moved to other directories which have more space. The following are default directories where reports are stored: /usr/gsm/ne_data/pm_reports/graphical /usr/gsm/ne_data/pm_reports/tabular /usr/gsm/ne_data/pm_reports/delimited The PM GUI logs errors to a file called /usr/gsm/logs/pmguiaudit<date>, which is cleaned up automatically by the system.
Cleaning up PM device naming data

The device naming data in the PM statistics database needs to be regularly cleaned up to ensure that the actual device names on the network are reflected in the PM GUI. Typically this cleanup should occur after a network element has been deleted from, or moved within the network. To clean up device naming data, use the utilities shown in the following table. These utilities can be found in the directory /usr/gsm/current/sbin: Script delete_BSS [bss_name] <bss_name> Description Removes the BSS naming data and its containees. Use this utility to delete all network entities for a given BSS_name(s). The specified BSS(s) will also be deleted. Removes the site naming data and its containees. Use this utility to delete all network entities for a given SITE_name(s). The specified SITE(s) will also be deleted. Removes the cell naming data and its containees. Use this utility to delete all network entities for a given cell_name(s). The specified cell(s) will also be deleted.
delete_SITE <bss_name> <site_name> [site_name ...]
delete_CELL <bss_name> <site_name> <cell_name> [cell_name ...]
EMOTOROLA LTD. 2000
1431
Cleaning up PM data
ISSUE 18 REVISION 0
Script delete_CARRIER <bss_name> <site_name> <cell_name> <carrier_name> [carrier_name] delete_OLDCARRIERS <#intervals>
Description Removes the carrier naming data and its containees. Use this utility to delete all network entities for a given carrier_name(s). Removes the oldcarriers naming data and its containees. Use this utility to delete all carrier entries in the entity table where there have been no new statistics for a specified number of time intervals. This will leave any underlying statistics without an entity, but this will be cleaned up the next time omc_db_maint is run.
NOTE The statistics themselves are cleaned up by the routine maintenance function omc_db_maint after seven days have elapsed.
1432
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Cleaning up PM data
Manually parsing PM statistics files

Parsing is the process of moving statistical data from the BSS statistics file to the PM database omc_db. The utility /usr/gsm/current/bin/pm_manual_parse allows statistics files which the automatic parser failed to parse to be manually parsed. The automatic parser process may have failed to parse the files due to changing between hourly and half-hourly statistics, for example. pm_manual_parse also allows the manual parsing of a full directory of files. pm_manual_parse accepts relative or absolute pathnames to the statistics file as parameters when submitting a statistics file for parsing.
Operating Information: Scaleable OMC System Administration (GSM-100-201) also details the pm_manual_parse utility.
Manually parsing PM statistics files

To manually parse PM statistics files, follow these steps: 1. omcadmin 2. Login as as the user omcadmin. At the command line, type: cd /usr/gsm/ne_data/raw_stats/100,0 3. At the command line, type: ls l This displays a list of directories, one for every BSS. An example of a directory name is 31,1. 4. 5. 6. 7. For each directory listed in step 3, perform steps 5 to 7. cd to the BSS directory. mv all files from filename.bad_header to another file name. For each file, enter: pm_manual_parse <filename>.
Using the pm_manual_parse sleep option

pm_manual_parse supports a sleep option. The sleep option is a optional command line switch which gives the option of waiting for a specified period between parsing successive files. For example, the following command allows10 seconds to elapse before parsing the second file: pm_manual_parse s10 <filename1> <filename2> The sleep value cannot be zero or negative. For example, use pm_manual_parse when receiving error messages in the parser log file /usr/gsm/logs/fpomcauditYYYYMMDD after a software upgrade. Such an error message could be:
Invalid Duration which will result in a .bad_header file.
Set the PM_HOURLY_STATS variable, do an OMC stop/start, then manually parse the files which have been renamed to: filename.bad_header.
EMOTOROLA LTD. 2000
1433
Resynchronizing PM databases
ISSUE 18 REVISION 0
Definition of PM Resync
The PM resynchronizing function (PM Resync) ensures that the information in the Performance Management statistics database (omc_db) is consistent with the information in the Configuration database (MIB). For example, PM Resync checks that the cell names stored in the PM database are the same as those stored in the MIB database. If the PM resync process does not run, out-of-date device names may appear in the PM GUI devices lists. See Technical Description: OMC in a GSM System (GSM-100-201) for further details about the PM Resync function.
Automatic PM Resync
The PM Resync function is automatically performed in background for the network at regular intervals by the PM Proxy process. The automatic PM Resync will only occur when changes have been made in the MIB database that should have been made in the PM database. If the OMC finds a conflict during the automatic PM Resync, it provides a default name for the network element based on its RDN. The automatic PM Resync subscribes to attributeChangeEvents for BSS, RXCDR, SITE and CELL devices from the Configuration database (MIB) and updates the PM database accordingly.
Manually resynchronizing PM databases

If inconsistencies occur between the OMC databases, or if the automatic PM Resync process will not run for some time and changes have been made to the device data, use the PM Resync option in the GUI to manually resynchronize the information. If this does not correct the naming or version inconsistency, raise an issue with the Motorola local office. If a cell has been added to a BTS, perform a manual PM Resync on that BTS to ensure the PM and MIB data are the same. Similarly, if a BTS is moved from one BSS to another, resynchronize the BSS. NOTE The automatic PM Resync functionality will not delete network elements from the database. Instead, use a Motorola utility such as delete_BSS and delete_SITE to remove the network elements from the PM database as necessary.
1434
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Performing a manual PM Resync

To perform a manual PM Resync, follow these steps: 1. 2. 3. From the map display or Navigation tree, select a network element that needs resynchronizing. For example, select the Network, a BSC, a SITE, and so on. Select Edit Detailed View from the menu bar. The OMC displays the detailed view window. Select Options PM Resync from the menu bar. The following message displays in the status line: PM Resync Initiated The data relating to the device selected is synchronized in the databases.
EMOTOROLA LTD. 2000
1435
Checking enabled statistics
ISSUE 18 REVISION 0

Procedure for checking PM enabled stats
To check which PM statistics have been enabled, use one of the following methods: 1. 2. 3. From the Selections window in the GUI, select Statistics Mgt All Enabled Statistics, see Statistics Management in Chapter 7 for further details. Use TTY commands for an individual network element. Use TTY commands and scripts to access multiple BSSs.
Single BSS check using TTY rlogin

Use the following MMI BSS commands to check which statistics have been enabled at a CELL/SITE/BSS: disp_enable_stat cell_number=<cell id> or disp_enable_stat <site number> or disp_enable_stat BSS
Multiple BSS checks using scripting and TTY rlogin

It is possible to combine shell scripting with the correct TTY commands and log the output to a file, which can then be further analysed or parsed. This requires a knowledge of UNIX shell scripting. NOTE Limitations to this method are that it assumes the same LAC for the whole BSC, and you have to change the network code and country code (0 0 1 & 0 1 in this example) to match your network. Also note it assumes that the BSS loads are correctly named (BSGSME...) during load install. NOTE Using cut and paste from this example may lead to some lines being split.
1436
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Example script
The following example script checks for enabled statistics per cell versus a reference cell per BSC and reports which statistics need to be enabled.
#!/bin/ksh # Script to check for enabled statistics per cell versus a reference # cell per BSC and report which statistics need to be enabled. # Can be run for a BSC or the whole OMC (by default) # Limitation: it assumes the same LAC for the whole BSC. # Written by J Moffitt (Motorola) 23rd December 1998 if [ $1 != ] then bscs=$1 check_exists=grep >.*$1 /usr/gsm/config/global/NE.MAP if [ $check_exists = ] then echo NE $1 does not exist on this OMC exit 1 fi else bscs=grep >.*BSGSME /usr/gsm/config/global/NE.MAP| awk {print $2} fi # Loop to check enabled stats status of each cell under each BSC # on the OMC or the selected BSC for i in echo $bscs do echo Log file for bscname $i >>bsc_enable_stat.log echo >>bsc_enable_stat.log echo disp_bss >>bsc_cmd.file batch_rlogin $i <bsc_cmd.file >>bsc_enable_stat.log.$$ rm bsc_cmd.file # make up command file to enable the disabled stats echo chg_l >>bsc_enable_stat.$i.cmd echo 3stooges >>bsc_enable_stat.$i.cmd echo 4beatles >>bsc_enable_stat.$i.cmd # get enabled stats for first live cell on BSC and use as a reference # to check all other cells with lac_id=cat bsc_enable_stat.log.$$|fgrep v unavailable |grep 655| cut c4245|head 1 cell_id=cat bsc_enable_stat.log.$$|fgrep v unavailable |grep 655| cut c5459|head 1 echo disp_enable_stat cell_number=0 0 1 0 1 $lac_id $cell_id >>bsc_cmd.file batch_rlogin $i <bsc_cmd.file >>bsc_reference_stat.log.$$ rm bsc_cmd.file echo reference cell id is 0 0 1 0 1 $lac_id $cell_id. >>bsc_enable_stat.log # exclude unnecessary text sed n //,/MMIRAM/p bsc_ref_stat.log.$$ rm bsc_reference_stat.log.$$
bsc_reference_stat.log.$$ |sed /MMI_RAM/d >>
# loop through each cell and compare it with the reference cells set of # enabled statistics cell_id=cat bsc_enable_stat.log.$$|fgrep v unavailable |grep 655| cut c5459 rm bsc_enable_stat.log.$$ for j in echo $cell_id do echo disp_enable_stat cell_number=0 0 1 0 1 $lac_id $j >>bsc_cmd.file batch_rlogin $i <bsc_cmd.file >>bsc_enable_stat.log.$$ rm bsc_cmd.file # exclude unnecessary text from the comparision sed n //,/MMIRAM/p bsc_enable_stat.log.$$ |sed /MMIRAM/d >>bsc_enb_stat.log.$$ rm bsc_enable_stat.log.$$
EMOTOROLA LTD. 2000
1437
ISSUE 18 REVISION 0
# compare set of enabled stats for current cell with set of enabled # statistics for the reference cell diff bsc_enb_stat.log.$$ bsc_ref_stat.log.$$ > res_cmp.log.$$ no_of_diffs=egrep ^< res_cmp.log.$$|wc l if [ $no_of_diffs eq 0 ] then echo Same stats are enabled for cell 0 0 1 0 1 $lac_id $j as reference cell >> bsc_enable_stat.log else # loop through and setup scripts of stats to be enabled echo Script for stats to be enabled for cell 0 0 1 0 1 $lac_id $j >> bsc_enable_stat.log stats_to_be_enabled=egrep ^< res_cmp.log.$$|sed s/^<// for k in echo ${stats_to_be_enabled} do # convert stats name to lower case before writing to file el_name=echo $k|tr [AZ] [az] echo will enable stat ${el_name} for cell_number 0 0 1 0 1 $lac_id $j >> bsc_enable_stat.log echo stat_mode ${el_name} on all cell_number=0 0 1 0 1 $lac_id $j >>bsc_enable_stat.$i.cmd done fi rm done # run script to enable the disabled stats echo enabling the disabled stats for BSC $i >>bsc_enable_stat.log batch_rlogin $i <bsc_enable_stat.$i.cmd >>bsc_enable_stat.log rm bsc_enable_stat.$i.cmd rm bsc_ref_stat.log.$$ done echo Log file is in $PWD/bsc_enable_stat.log. Please check logfile bsc_enb_stat.log.$$ res_cmp.log.$$
1438
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Motorola PM and FM tools

Overview of Motorota Tools
Table 14-2 shows which Motorola tools can be used to perform specific OMC operational activities. Table 14-2 Motorola Tools Motorola Tool/Utility
Network Health Analyst (NHA) Cell Analysis Tool (CAT) Event Counting Tool (ECT) Data Gathering Tool (DGT)
Fault Diagno sis n n
Status Reporting
Performance Reporting
Outage Reporting
Alarm and Event data
Availability
n n
Purchasable
COP Purchasable COP Purchasable
n n n n
Free tool
site_outage
OMC utility
Included in GSR4 1600h Included in GSR4 1600h Included in GSR4 1600h
dri_status
OMC utility
rtf_status
OMC utility
Note: CAT, CTP and ECT are included in the Cell Optimization Product (COP) NOTE The OMC utilities included in GSR4 (1600h onwards) are optional for installation with the OMC-R but may provide additional tools to the operator.
EMOTOROLA LTD. 2000
1439
ISSUE 18 REVISION 0
Performance Management tools

Table 14-3 shows the performance management activities that can be performed using the Performance Management GUI, Network Health Analyst (NHA), and Cell Analysis Tool (CAT). Table 14-3 Performance management tools PM Activity Handover reports Quality of service Cell activity Congestion reports Sleeping cells Device status TCH performance Link and channel usage n n PM GUI n n n n n NHA n n n n n n n CAT
Data Gathering Tool (DGT)

The Data Gathering Tool (DGT) collects all the relevant data relating to a specified problem and copies it to tape or file, together with a problem description. The file or tape is then sent to Motorola for analysis. DGT is designed to run on a Motorola OMC-R MMI terminal. The primary object of this tool is to gather all the necessary information for the analysis of all OMC/BSS GSM problem reports. DGT is available through a GUI front-end and employs a daily cron job for automatic collection of BSS SWFM files should they be required. See the Data Gathering Tool (DGT) documentation for further information.
Network Health Analyst (NHA) tool

The Network Health Analyst (NHA) tool automatically monitors Motorola network elements using statistic, event, and configuration information available at the OMC-R. Using this information the NHA can detect when the performance of key aspects of the GSM network deteriorate below an acceptable level. The NHA runs on a Sun platform connected to the OMC-R and can be used by all users involved in the operations of a Motorola GSM network. The NHA is an optional tool. To order NHA for your network contact your local office. If available, see the Network Health Analyst (NHA) documentation for more information.
1440
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Cell Analysis Tool (CAT)

The Cell Analysis Tool (CAT) provides information about the GSM network cell performance. It allows the user to find out quickly which cells currently have problems, or which cells may have problems in the near future. For further details, see System Information: Cell Optimization Product (COP) (GSM-TOOLS-001).
Event Counting Tool (ECT)

The ECT provides information about the number and type of events and alarms generated throughout the network. It extracts data from the event log files for specified dates. ECT allows the user to generate reports on individual network elements, groups of elements, or the whole network. For further details, see System Information: Cell Optimization Product (COP) (GSM-TOOLS-001).
Call Trace Product (CTP)

The CTP is designed to help operators of GSM900 and DCS1800 communication networks tune and optimize their systems. CTP allows Call Trace data to be analysed and decoded. For further details, see System Information: Cell Optimization Product (COP) (GSM-TOOLS-001).
site_outage utility
site_outage is an OMC utility that generates a report or list of the quantity and duration of outages of sites over a period of time. The default period is 24 hours. site_outage can work over multiple OMCs and can be scheduled to run daily using the UNIX command cron. site_outage can be found in the following directory: /usr/gsm/current/sbin For further details see NO TAGReporting utilities in Chapter 9.
dri_status utility
dri_status is an OMC utility that generates a report of the DRIs that are OOS. dri_status can work over multiple OMCs. and can be scheduled to run daily using the UNIX command cron. dri_status can be found in the following directory: /usr/gsm/current/sbin For further details see NO TAGReporting utilities in Chapter 9.
EMOTOROLA LTD. 2000
1441
ISSUE 18 REVISION 0
rtf_status utility
rtf_status is an OMC utility that generates a report of the RTFs that are OOS. rtf_status can work over multiple OMCs, and can be scheduled to run daily using the UNIX command cron. rtf_status can be found in the following directory: /usr/gsm/current/sbin For further details see NO TAGReporting utilities in Chapter 9.
1442
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Troubleshooting
Troubleshooting
Introduction to troubleshooting
This section provides additional information that can contribute to the effective operation of the OMC and its associated interfaces within the network. The following troubleshooting activities are described: S S S S S Checking ISG 6525 packet switch health Checking ISG 6560 MPRouter health DTE address mapping Troubleshooting the OML Checking LAN connections
EMOTOROLA LTD. 2000
1443
Checking ISG 6525 packet switch health
ISSUE 18 REVISION 0

Introduction
Check the X.25 packet switch periodically. Figure 14-5 illustrates the interconnections of the X.25 packet switch (ISG (formerly CODEX) 6525) and multiplexer (MUX).
ISG 6525 OMC X.25 Packet Switch
ISG 6250 M U X G.703 links to NEs
Figure 14-5 ISG interconnections The connection between the system processor and the ISG 6525 could be an option such as a Private Exchange Packet Data Network (PXPDN) and may require the use of interface converters. A printer may be permanently connected to the ISG 6525 or the MUX to enable alarms to be printed as they occur. Alarms generated by the ISG equipment cannot be displayed within the OMC applications. However, it is possible to remote login to the packet switch. It is not possible to monitor the operation of the MUX directly from the OMC. Monitor the MUX by connecting a PC into the MUX maintenance terminal. Any major problem with the MUX results in a link being dropped, and the fact is recorded in the ISG 6525 link statistics.
Checking ISG 6525 packet switch

Check the X.25 packet switch by remotely logging into the ISG 6525 from a SPARCstation as follows: 1. From a SPARCstation Xterm window, remote login to the system processor using the command: rlogin <hostname> where <hostname> is the name of the system processor. 2. 3. Enter the password when requested. Type /opt/SUNWconn/bin/pad.
1444
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
4.
The prompt changes to pad. Then type: call port<port no.>.<dteaddress> where <port no.> is the port number and <dteaddress> is the node address of packet switch with the digits 98 appended, for example: 31107879999098 node address For example: sub address
call port2a.31107879999098
5. Enter the password after the Enter Password prompt. The user level password is sufficient for the health checks of the ISG equipment. The ISG 6525 main menu is displayed. 6. Enter quit to return to the shell.
Monitoring ISG packet switch statistics

This procedure describes how to monitor ISG 6525 and MUX statistics on a SPARCstation. Each week monitor the following two statistics: S S S Node Stats. Detailed Port Stat. Detailed Link Stats.
After logging in, the main menu is displayed. Proceed as follows: 1. 2. Select option 5 (Status/Statistics) from the ISG 6525 main menu and the Status/Statistics menu (Figure 14-6) is displayed. Node Stats. Select option 1 to display the first Detailed Node Statistics page (Figure 14-7), and check the following statistics: Last watchdog timeout event. A watchdog timeout should not occur during normal operation. If a date and time displays indicating that a timeout has occurred, obtain a Fatal Error Report (see ISG 6500 series product documentation) and, if necessary, contact Motorola to report the condition. Power Supply status. The power supply should be UP. If the power supply fails an alarm results. Fan Status. The fan status should be UP. If the fan fails an alarm results.
EMOTOROLA LTD. 2000
1445
ISSUE 18 REVISION 0
Node: <Nodename> Address: <Address> Date: 3 MAR1998 Time: 10:31:31 Menu Status/Statistics Path: (Main.5)
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12.
Node Stats Detailed Port Stats MUX Channel Detailed Link Stats (Unauthorised) Detailed PAD Stats Call Summary Stats Hardware Stats (Unauthorised) (Unauthorised) (Unauthorised) Software Option Statistics
Enter Selection:
Figure 14-6 Status/statistics menu
Node: <Nodename> Detailed Node Statistics
Address: 100 Date: 3MAR1993 Time: 12:19:26 Page: 1 of 6
Node number: 1 Product Type: Packet switch Software source: PROM Software revision: 2.10 (Mon Jan 7 14:29:18 EST 1991) Last power on event: Last reset button event: Last node boot Last watchdog timeout event: Last configuration change: 19 NOV1998 15:31:01 24JAN1998 12:55:27 30JAN1998 12:16:53 22NOV1998 09:15:45 30JAN1998 12:12:15
Power Supply status: Fan Status: Configuration memory: 32768 bytes available, 3766 bytes (11%) used Press any key to continue (ESC to exit) . . .
Figure 14-7 Detailed node statistics (page 1)
1446
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Routing statistics: Current Maximum Calls in place: 64 65 Calls per second: 0 0 PVC connections: 0 0 Buffer pool statistics: Buffers available: 3692, used 120 (3%), maximum used 153 (4%) Node Throughput: Current Maximum Characters/Sec 64 65 Packets/sec: 557 608 Press any key to continue (ESC to exit) . . . Figure 14-8 Detailed node statistics (page 2) 3. Press any key to display page 2 of the Detailed Node Statistics (Figure 14-8), and check the following statistics: Buffer pool statistics. The maximum used percentage should be not more than 2% above the used percentage value. Packets/sec. Where a single CPU is used the number of packets per second should not exceed 7080. If this value is exceeded check the capacity of the switch. If more than one CPU is used there is separate stats page for each CPU, the number of packets/sec for each CPU should be checked.
4. 5. 6.
After checking the packets/sec for each CPU, press ESC to return to the Status/Statistics menu. Select option 4 from the Status/Statistics menu to obtain the Detailed Link Statistics report (Figure 14-9). Check the following columns: Type should always be X.25.
Stateshould always be UP. Speed CRC errors Link down should be 64k. number of errors should be low. should be 0.
EMOTOROLA LTD. 2000
1447
ISSUE 18 REVISION 0
7.
If the state of the X.25 link is down, then the time that the link dropped is displayed in the State date/time column. If the link is down this means that either a BSC has reset or there is a problem with a transmission node.
Node: Nodename Detailed Link Statistics
Address: 100
Date: 3MAR1991 Time: 12:22:02 Page: 1 of 1
entity === p1
Type subtype ==== X25
state == UP
speed === 64 k
State CRC Link Data frames Utilization date/time errors down in/out in/out ==== === === ===== ===== 0 0 0 0%
Press any key to continue (ESC to exit) . . .
Figure 14-9 Detailed Link Statistics page 8. 9. 10. 11. 12. 13. When the Detailed Link Stats have been checked press ESC to return to the Status/Statistics menu. Select option 11 to reset all Stats. Type y to confirm reset of statistics. Press ESC to return to the ISG 6525 main menu. Select option 1 (Logout). To exit from the PAD process, type quit.
CPU utilization threshold

The ISG CPU runs background diagnostic tests on hardware and checks processed data communications traffic. CPU utilization is the amount of time spent checking traffic as a percentage of total time. If the specified CPU utilization threshold is exceeded an alarm is generated and the operator must notify the system administrator immediately. The threshold should normally be set at 75% (refer to the ISG 6500 series product documentation which is supplied with the OMC).
1448
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Printing packet switch configuration

To obtain a printout of the configuration of the ISG 6500 series packet switch, carry out the following procedure. 1. root rlogin <host name> Where <host name> is the name of the system processor. 2. 3. Enter the password when requested. Type /opt/SUNWconn/bin/pad. The prompt changes to PAD:. 4. Then type: call port<port no.>.<dteaddress> Where: <port no.> <dteaddress> is: the port number the node address of the packet switch with the digits 98 appended Remote login to the system processor using the command:
Example call port 0a.31107879999098 port node number address sub address
EMOTOROLA LTD. 2000
1449
ISSUE 18 REVISION 0
5.
Enter the system administrators password after the Enter Password: prompt. The ISG manager level password is required for printing the configuration of the ISG equipment. The ISG 6500 main menu (Figure 14-10) is displayed.
Node: nodename Menu: Main Address: 100 Date: 2 JAN1995 Time: 22:48:32 Path: (Main.6)
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17.
Logout Examine List Monitor Status/Statistics Configure Boot Update System Parameters Copy/Insert Record Delete Record Port/Station/Channel Control Diagnostics Default Node Print Configuration Configuration Save/Restore Flash Memory LAN Control Menu
Enter Selection:
Figure 14-10 Packet switch main menu (managers options) 6. 7. 8. Go to the next step to print the ISG configuration, or to step17 to list the configuration on the screen. Select option 14 (Print Configuration) from the main menu. Select option 1 from the Print Configuration menu (Figure 14-11) to choose the record types to be printed.
Node: Nodename Address: 100 Date: 4 JUL1994 Time: 10:32:32 Menu: Print Configuration Path: (Main.14) 1. Select Record T ypes 2. Print Selected Records 3. Change Print Parameters Enter Selection:
Figure 14-11 Print configuration menu
1450
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
9.
A list of record types that can be printed is displayed (Figure 14-12). Enter the number beside the record type, for the record to be printed. Any combination of record types may be selected by summing (for example 1+2+3+......). Enter ALL to select all record types. Press ESC to return to the Print Configuration Menu.
Print Selections
1) 3) 5) 7) 9) 11) 13) 15) 17)
* Node Record * Route Selection Table * Outbound Call Translation Table * PVC Setup Table * NUI/Password Table * Remote PAD Parameter Table * Management Record * PVC Broadcast Output Table * Calling Addr Translation Table
2) 4) 6) 8) 10) 12) 14) 16)
* Port Records * Inbound Call Translation Table * PAD Prompt Table * Mnemonic Table * PAD Profile Table * MUX Channels * SVC Broadcast Output Table * Software Key Table
Select Record Types:
Figure 14-12 Record types 10. 11. The Print Configuration menu (Figure 14-11) is re-displayed. Select option 3 to enable the configuration data to be saved to a log file. Press the CR key to proceed to the next step without entering a printer address. The following is displayed:
Echo to CTP: No/
12. 13. 14.
Type Yes and press the CR key. Press the ESC key to return to the Print Configuration menu (Figure 14-11). With the mouse pointer in the Xterm window, hold down the CTRL key and the left mouse button. An Xterm popup menu is displayed. Select Log to File from the menu. Anything subsequently displayed in the Xterm window is saved to an Xterm log file. To print the packet switch configuration, select option 2, press any key to continue. Figure 14-13 is an example of the response from the ISG when the Print Selected Records option is chosen. NOTE To close the log file press and hold the CTRL key and the left mouse button simultaneously. An Xterm is displayed, containing the popup menu. Select the DeSelect Log To File option.
15.
16.
Press any key to continue and re-display the Print Configuration menu; go back to step 6. NOTE Pressing escape returns to the main menu.
17. 18.
Select option 3 (List) from the main menu. A list of record types is displayed. Select an item from the list by entering its number, for example 3 for Route Selection Table. It is recommended that listings be obtained for Port and Node parameters and Route Selection Tables.
EMOTOROLA LTD. 2000
1451
ISSUE 18 REVISION 0
19.
To logout, press ESC until the display returns to the main menu. Select option 1 to logout. The following message is displayed:
Call Cleared.
The prompt is displayed indicating that the command line has returned to the PAD process. 20. To exit from the PAD process, type the following command: quit 21. Log out by typing the following: exit
Print Selected Configuration Records There are no entries for the following record types: Inbound Call Translation Table Outbound Call Translation Table PVC Setup Table NUI/Password Table MUX Channels Management Record SVC Broadcast Output Table PVC Broadcast Output Table Software Key Table Calling Addr Translation Table (3) OMCNET 4JUL1994 10:34 Print(0) CONNECTED TO PAD3 Sending the following record types: Node Record Port Records Route Selection Table (2) OMCNET 4JUL1994 10:34 CPU UTILIZATION>THRESHOLD ON CARD 1 PAD Prompt Table Mnemonic Table PAD Profile Table Remote PAD Parameter Table Clearing the call to printer... Waiting 2 seconds. (3) OMCNET 4JUL1994 10:35 Print(0) DISCONNECTED FROM PAD3 Press any key to continue (ESC to exit ) ...
Figure 14-13 Example response to Print Selected Records
1452
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Route selection table

Each Route selection table record consists of an Entry number, Address, Destination port and Priority where: S S S S Entry number is used to reference this Routing Table record. Address is the Network address for calls routed beyond this node (not needed for calls to this node). Destination port is the port to which calls with this network address will be routed. Priority if more than one port is listed in a route selection entry, the port selected for call forwarding is based on the least load and highest priority.
Node: Nodename Menu: List Address: 100 Date: 4 JUL1994 Time: 10:37:37 Path:(Main.3)
1. Node 2. Port 3. Route Selection Table 4. Inbound Call Translation Table 5. Outbound Call Translation Table 6. PAD Prompt Table 7. PVC Setup Table 8. Mnemonic Table 9. NUI/Password Table 10. PAD Profile Table 11. Remote PAD Parameter Table 12. MUX Channel 13. Management 14. SVC Broadcast Output Table 15. PVC Broadcast Output Table 16. Software Key Table 17. Calling Addr Translation Table Enter Selection: Figure 14-14 List of record types
Example
[1], 79310104010141, x252, 1, (blank), 1, (blank), 1, (blank), 1, (blank), 1, (blank), 1, (blank), 1, (blank), 1. Entry number: 1 Address: 79310104010141 #1 Port: x252 #1 Priority: 1 #2 Port: (blank) #2 Priority: 1 #3 Port: (blank) #3 Priority: 1 #4 Port: (blank) #4 Priority: 1 #5 Port: (blank) #5 Priority: 1 #6 Port: (blank) #6 Priority: 1 #7 Port: (blank) #7 Priority: 1 #8 Port: (blank) #8 Priority: 1
EMOTOROLA LTD. 2000
1453
ISSUE 18 REVISION 0
Port record list

The parameters associated with each port are contained in this list.
Example
Port Record List [1], X25, DTR, INT, 6400, DCE, NORM, 7, NORM, 2, 128, 128, NONE, NONE, NONE, CAUSE, 4, 0, , , OFF, 2 0, 1, 32, 1, SABM, 30, 40, 10, 5, 0, 180, 180, 200, 180, NONE, 0, (blank), (blank), , , , , ,
Port Number: 1 Port Type: X25 Connection Type: DTR Clock Source: INT Clock Speed: 64000 Link Address: DCE Number of PVC Channels: 0 Starting PVC Channel Number: 1 Number of SVC Channels: 32 Starting SVC Channel Number: 1 Initial Frame: SABM T1 Transmission Retry Timer (1/10 sec): 30 T4 Poll Timer: 40 N2 Transmission Tries: 10 Frame Sequence Counting: NORM K Frame Window: 7 Packet Sequence Counting: NORM W Packet Window: 2 P Packet Size: 128 Maximum Negotiated Packet Size: 128 Data Queue Upper Threshold: 5 Data Queue lower Threshold: 0 Restart Timer: 180 Reset Timer: 180 Call Timer: 200 Clear Timer: 180 Facilities to delete from Outbound Calls: NONE Facilities to add to Outbound Calls: NONE Facilities to bar in Outbound Calls: NONE Facilities to bar in Inbound Calls: NONE+ X.25 Options: CAUSE Number of Routing Digits in Call User Data: 4 Number of prefix Address Digits stripped from Outgoing Calls: 0 Number of prefix Address Digits stripped from Incoming Calls: 0 Restricted Connection Destination: (blank) Port Address: (blank) CUG Membership: ,,,,,,, Billing Records: OFF Number of Subaddress Digits in X.25 Address: 2
Each parameter is described in the ISG 6500 series product documentation (Network Operations Manual, Chapter 3).
1454
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Checking ISG 6560 MPRouter health

Introduction
All OMC communication with BSCs is based on X.25. With the Scaleable OMC platform a combined packet switch / multiplexer is used, the ISG 6560 MPRouter. Check the ISG 6560 MPRouter periodically. Figure 14-15 illustrates the interconnections of the ISG (formerly CODEX) 6560 to the OMC.
OMC
ISG 6560 MPRouter
G.703 links to NEs
Figure 14-15 ISG 6560 connections
Checking ISG 6560 MPRouter

Check the router by remotely logging into the ISG 6560 MPRouter from a SPARCstation as follows: 1. From a SPARCstation Xterm window, remote login to the system processor using the command: rlogin <hostname> where <hostname> is the name of the system processor. 2. 3. Enter the password when requested. Type: /opt/SUNWconn/bin/pad 4. The prompt changes to pad. Then type:
call <link number><dteaddress>

Where: <link number> is: the number of the link (link values are determined by what is contained in the x25.config file) the node address of the router with the digits 98 appended
<dteaddress>
EMOTOROLA LTD. 2000
1455
ISSUE 18 REVISION 0
5.
Enter the password after the Enter Password prompt. The user level password will be sufficient for the health checks of the ISG equipment. The ISG 6560 main menu will be displayed.
6.
Enter quit to return to the shell.
Monitoring ISG 6560 MPRouter statistics

This procedure describes how to monitor ISG 6560 MPRouter statistics on a SPARCstation. Each week monitor the following statistics: S S S Node Stat. Detailed Port Stat. Detailed Link Stat.
After logging in, the main menu will be displayed. Proceed as follows: 1. 2. Select option 5 (Status/statistics) from the ISG 6560 main menu and the Status/Statistics menu (Figure 14-16) is displayed. Node Stats. Select option 1 to display the first Detailed Node Statistics page (Figure 14-17), and check the following statistics: Last watchdog timeout event. A watchdog timeout should not occur during normal operation. If a date and time displays indicating that a timeout has occurred, obtain a Fatal Error Report (see ISG 6500 series product documentation) and, if necessary, contact Motorola to report the condition. Running Power Supplies. The power supply should be UP. If the power supply fails an alarm will result. Fan Status. The fan status should be UP. If the fan fails an alarm will result.
1456
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Node: Menu
<Nodename> Status/statistics
Address: 9200 Date: 3 MAR1998 Time: 10:31:31 Path: (Main.5)
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18.
Node Stat Detailed Port Stat Flash to Flash Transfer Stat Detailed Link Stat Detailed master MX25 Station Detailed PAD Stat Network Services Stats Nest Inventory Reset master MX25 Station Sta Reset Port Stats Reset All Stats Software Option Statistics Detailed SDLC Station Stats Reset SDLC Station Stats FRI Station Statistics DCP Statistics Internal DSD Stat Reset Internal DSD Stats
19. Detailed XDLC Station Stats 20. Reset XDLC Station Stats 21. Bridge Statistics 22. LAN Connection Statistics 23. FRA Station Statistics 24. TFTP Statistics 25. Router Stats 26. LLC to SDLC Statistics 27. ISDN Channel Statistics 28. Detailed NCI Statistics 29. Reset NCI Statistics 30. SNMP Statistics 31. Detailed DORA Statistics 32. Reset DORA Statistics 33. Detailed DORM Statistics 34. Reset DORM Statistics 35. Detailed NUIC Stats 36. Reset NUIC Stats
Enter Selection:
Figure 14-16 Status/statistics menu
EMOTOROLA LTD. 2000
1457
ISSUE 18 REVISION 0
Address: 100 Date: 23JAN1998 Time: 12:19:26 Page: 1 of 8
Node number: 100 Product Type: ISG 6560 Node Serial #: 3719459 PROM revision: V1.0 Code revision, Current: V4.96.06i02v01 Size: 3495372 bytes Bank: 1 ISDN BRI Switch Types available: ETSI, BTNR Code Revision, Alternate: None Bank: 2
Last power up or reset: 16JAN1998 15:31:01 Last node boot 01FEB1998 12:16:53 Last watchdog timeout event: <none> Last configuration change: 03FEB1998 12:12:15
Power Supply Status: GOOD Compressed config memory (CMEM): 32768 bytes available, 11212 bytes (34%) used Uncompressed config memory (DRAM): 65366 bytes available, 26092 bytes (40%) used Press any key to continue (ESC to exit) . . .
Figure 14-17 Detailed node statistics (page 1)
1458
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Address: 100 Date: 23JAN1998 Time: 6:47:25 Page: 2 of 8
Routing statistics: Current Calls in place: 6 Calls per second: 0 PVC connections: 0
Maximum 13 3 0
Data Buffers available: 4989, used 163 (3%), maximum used 205 (4%) Packet Buffers available: 580, used 0 (0%), times exhausted: 0 Management Packet Buffers available: 57, used: 0 (0%), times exhausted Node Throughput: Current Characters/sec 0 Packets/sec: 35 Maximum 0 104
Front Panel LED display: BLANK Power: ON Status: OFF Service: OFF
Figure 14-18 Detailed node statistics (page 2) 3. Press any key to display page 2 of the Detailed Node Statistics (Figure 14-18), and check the following statistics: 4. 5. 6. Buffer pool statistics. The maximum used percentage should be not more than 2% above the used percentage value. Packets/sec.
After checking the packets/sec, press ESC to return to the Status/Statistics menu. Select option 4 from the Status/Statistics menu to obtain the Detailed Link Statistics report (Figure 14-19). Check the following columns: Type State Speed CRC errors Link down should always be X.25. should always be UP. should be 64k. number of errors should be low. should be 0.
EMOTOROLA LTD. 2000
1459
ISSUE 18 REVISION 0
7.
If the state of the X.25 link is down, then the time that the link dropped will be displayed in the State date/time column. If the link is down this will mean that either a BSC has reset or there is a problem with a transmission node.
Node: Nodename Detailed Link Statistics
entity === p1 p2
Type subtype ==== X25 X25
state == UP UP
speed === 64 k
State CRC Link Data frames Utilization date/time errors down in/out in/out ==== === === ===== ===== 1258 1258 0 0 0 0 0 0 0% 0%
Figure 14-19 Detailed Link Statistics page 8. 9. 10. 11. 12. When the Detailed Link Stats have been checked press ESC to return to the Status/Statistics menu. Select option 11 to reset all Stats. Type y to confirm reset of statistics. Press ESC to return to the ISG 6560 main menu. To exit from the PAD process, type quit.
CPU utilization threshold

The ISG 6560 CPU runs background diagnostic tests on hardware and checks processed data communications traffic. CPU utilization is the amount of time spent checking traffic as a percentage of total time. If the specified CPU utilization threshold is exceeded an alarm is generated and the operator must notify the system administrator immediately. The threshold should normally be set at 75% (refer to the ISG 6500 series product documentation which is supplied with the OMC).
1460
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
DTE address mapping
DTE address mapping

Introduction
It is important to ensure that the X.121 DTE (Data Terminal Equipment) addresses are correctly specified in all the Network Elements, including the packet switch.
At the BSS
BSS addresses
Four BSS X.121 addresses may be set at the BSS. These are referred to as addresses 0 to 3. Although the BSS allows four X.121 DTE addresses to be stored in NVRAM, it only uses the first address. The others can be null.
OMCR addresses
Seven OMCR addresses must be set at the BSS (0 to 6). Addresses 0 and 1 are used for Alarm Reporting (evt_iface). The BSS will continuously alternate between these two addresses in its attempt to set up an alarm virtual circuit. Addresses 2 and 3 are used for bootload. Addresses 5 and 6 are used for upload. Address 4 is used for remote login.
At the OMCR
BSS X.121 DTE addresses
On adding an NE to the OMC, the DTE address for the BSS is entered on the appropriate detailed view form.
EMOTOROLA LTD. 2000
1461
DTE address mapping
ISSUE 18 REVISION 0
OMC X.121 DTE addresses

The OMC X.121 DTE addresses are stored in the x25_config file. This file contains 7 entries as follows: Entries 1 and 2 refer to bootload. Entry 1 should be configured to use a port on a different sync controller to entry 5. Entries 3 and 4 refer to Alarms (evt_iface). Entry 2 should be configured to use a port on a different sync controller to entry 6. Entry 5 refers to remote login. Entries 6 and 7 refer to upload.
The following is a typical example of an x25_config file:

more x25_config rlogin ' disp_dte
OMC
79310104011043 79310104010044 79310104010151 79310104011052 79310104010146 79310104010045 79310104010047 bootload bootload evt_iface evt_iface rlogin upload upload
BSS
evt_iface evt_iface bootload bootload rlogin upload upload 51 = 0 52 = 1 43 = 2 44 = 3 46 = 4 45 = 5 47 = 6
Initial entry of BSS:

BSS DTE addresses: Address #0: 79320101010000 Address #1: Zero length address Address #2: Zero length address Address #3: Zero length address
OMC DTE addresses: Address #0: 79310104010151 Address #1: 79310104010052 Address #2: 79310104010043 Address #3: 79310104010044 Address #4: 79310104010045 Address #5: 79310104010146 Address #6: 79310104010147 Address #7: Zero length address
1462
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Troubleshooting the OML

Link failures
A link failure occurs when the virtual circuit has been broken. NOTE A virtual circuit creates and maintains the X.25 link between the OMC and an NE. Network Elements are responsible for maintaining communication functionality for alarms, events, uploads, downloads, and rlogin. If the virtual circuit link is broken, the OMC is disconnected from the NE(s), thus, creating a link failure.
SYST EM PROCESSOR X.25 PACKET SWIT CH V.35 1 OML 2 G.703 RXCDR BSC (G.708) GPROC 4 GPROC MUX G.703 3 Any NE
X 2 5
DIALUP MODEM
PC
DIALUP MODEM
DIALUP MODEM
OPTIONAL DIALUP MODEM LINK TO NE MAINTENANCE PORT (CUSTOMER PROVIDED)
Figure 14-20 OMC and GSM physical links
Types of X.25 link failures

Link failures are usually related to the X.25 link. A link failure may be either partial or complete. The link may be broken for one or more of the NE-related functions, that is alarms, events, uploads, downloads, and rlogin.
Partial link failure

Partial link failure for NE-related communication occurs when one or more NE-related functions are lost while others remain. For example, it is possible to have a link failure for alarms while retaining rlogin capabilities. This may be possible because more than one virtual circuit may exist simultaneously or alarm capability may be carried by one link. Thus, the rlogin capability may continue to function.
EMOTOROLA LTD. 2000
1463
ISSUE 18 REVISION 0
Complete link failure

Complete link failure for OMC/NE-related communication occurs when all NE-related functions are lost. For example, if the X.25 link on the OMC processor is stopped, every type of link to the NE will fail. The following is a typical example of how to switch to a redundant OML:
#4 NOT APPL *NONE* linkFailureEvent BSS B01 (BSC Cork01):0 SITE 02/08/1994 05:26:00 [30003] X25CircuitDown FMIC Critical / Serial No 12 HW Version 3
Check device status using the detailed view form for the relevant OML and MMS
Ensure redundant OML is in correct service state
Lock the faulty OML. The redundant OML is automatically switched
Investigate problem using GSM-100-501
Inform CFE that site visit is possible
When primary OML is available, unlock and perform lock on redundant OML
Check that device status is unlocked and busy
Audit the affected BSS or RXCDR
Possible faults
Failure of the OML can be caused by any of the following problems: 1. System processor/X.25 packet switch link If a physical link failure between the system processor and the X.25 packet switch occurs, carry out the following checks, refer to Operating Information: OMC System Administration, GSM-100-202: 2. Check system processor X.25 port. Check X.25 packet switch port.
X.25 packet switch/multiplexer link If a physical link failure between X.25 packet switch and the multiplexer occurs, carry out the following checks, refer to the Installation & Configuration: GSM System Configuration GSM-100-403: Check X.25 packet switch port. Check multiplexer port. NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000
1464
ISSUE 18 REVISION 0
3.
Multiplexer/NE link If a physical link failure between the multiplexer and the NE occurs, carry out the following checks, refer to Installation & Configuration: GSM System Configuration GSM-100-403: Check if the NE has reset. Check MSI board on which the OML is located. Check the multiplexer port.
4.
RXCDR/BSC link If a physical link failure between the RXCDR and the BSC occurs, carry out the following checks, refer to Checking device status from the navigation tree in Chapter 2: Check MSI board on which the XBL is located at the BSC. Check appropriate XCDR board at the RXCDR.
5.
NE X.25 process If a NE X.25 process failure occurs, carry out the following checks, refer to Fault management from navigation tree in Chapter 2: At the NE, locally (or via optional modem) lock and then unlock the OML. Reset the NE to re-establish the OML.
6.
Sync controller board If the system processor sync controller board fails, carry out the following procedure, refer to Operating Information: OMC System Administration, GSM-100-202: Replace the sync controller board and then restart X.25 on the appropriate ports of the new board.
7.
X.25 packet switch port If there is a X.25 packet switch port failure, carry out the following procedures, refer to the Installation & Configuration: GSM System Configuration GSM-100-403: If capacity is available, move the affected traffic to a different port. If no spare capacity is available, replace the board.
8.
Multiplexer port If there is a multiplexer port failure, carry out the following procedures, refer to the Installation & Configuration: GSM System Configuration GSM-100-403: If capacity is available, move the affected traffic to a different port. If no spare capacity is available, replace the board.
EMOTOROLA LTD. 2000
1465
Load Management configuration tasks
ISSUE 18 REVISION 0

Introduction to Load managment configuration tasks
The following Load Management configuration tasks are described in this section (for further information on Load Management procedures see Chapter 5): S S S S S S S S S S S Backup BSS/RXCDR configuration database. Deploy new BSS/RXCDR databases using CSFP. Deploy new BSS/RXCDR databases without CSFP. Install new BSS/RXCDR database onto OMC. Initiate download to BSS/RXCDR and monitor progress. Enable/Disable database downloads. Check all sites and devices come into correct service after BSC/RXCDR reset. Unconfigure a CSFP. Configure a CSFP. Fallback to old database at BSC/RXCDR. Schedule an upload.
1466
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Backup BSS/RXCDR configuration database

A BSS/RXCDR configuration database is backed up at the OMC by copying the database file from the BSS to the OMC file system. This process is a file transfer process known as upload. Upload should be initiated from the Load Mgt icon on the OMC Front Panel ( it can also be initiated from the map, the navigation tree or the contained devices form). 1. 2. 3. 4. 5. 6. 7. Select the Load Mgmt icon on the Front Panel to open the Software Load Management window. Select a BSS or RXCDR from the list. Select Load Mgt Upload Object from the menu bar to open the Upload window. Optionally enter a comment to identify the object and click OK. Select Load Mgt Upload Status from the menu bar to open the Upload Status window. Monitor the upload (this could take 20 minutes). Check for success.
EMOTOROLA LTD. 2000
1467
ISSUE 18 REVISION 0
Deploy new BSS/RXCDR databases

With CSFP
The overall task of deploying a new database using CSFP involves the following steps: 1. 2. 3. 4. 5. 6. Load/install/activate new BSS/RXCDR configuration database onto OMC (refer to Install new BSS/RXCDR configuration database onto OMC task). Configure the CSFP on the target BSS/RXCDR and verify the status of the CSFP prior to the download (refer to Configure a CSFP task). Download the database to the CSFP (refer to Initiate download of new database to BSS/RXCDR task). Swap the CSFP current and the new database (refer to Swap current and new CSFP loads task). Verify that all sites and devices come into service correctly (refer to Check all sites and devices after BSC/RXCDR reset task). Unconfigure the CSFPs when the new configuration has been verified (refer to Unconfigure a CSFP task).
Without CSFP
The overall task of deploying a new database without CSFP involves the following steps: 1. 2. 3. Load/install/activate new BSS/RXCDR configuration database onto OMC (refer to Install new BSS/RXCDR configuration database onto OMC task). Download the database and monitor the download status (refer to Initiate download of new database to BSS/RXCDR task). Verify that all sites and devices come into service correctly (refer to Check all sites and devices after BSC/RXCDR reset task).
1468
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Install new BSS/RXCDR database onto OMC

New NE databases created by Motorola personnel are installed at the OMC from tape, CD-ROM, DataGen or any machine on the LAN and configured as the active database for a particular NE. These databases are later downloaded to the NEs under the OMCs control. NOTE The database can be installed from tape, CD, DataGen or user defined source. The following steps describe the installation from the tape only.
General procedure
To install a new database from tape, carry out the following procedure: 1. 2. 3. 4. 5. 6. 7. 8. 9. Insert the tape containing the database into the tape drive of the system processor. Select the Load Mgmt icon from the Front Panel, the Software Load Management window opens. Select Database Mgt Load Database from the menu bar, an xterm window opens. Enter 1 to select the Tape/Disk Drive. Enter 1 to select the system processor Tape Drive. Enter the appropriate character to select the required database. Enter the NE name and a comment, if required, in response to the prompts. Enter the appropriate <Load name> to create the database directory. On termination of the installation, a message is displayed that identifies where in the OMC file structure the database can be found.
Normal download
To activate a normal download, carry out the following procedure: 1. 2. 3. 4. 5. Select the Load Mgmt icon from the Front Panel, the Software Load Management window opens. Select Database Mgt Activate Database from the menu bar, an xterm window opens. Enter the name of the appropriate BSS or RXCDR. Enter 1 for an Active directory. Enter the appropriate number corresponding to the database load name and press CR. The specified database is now active.
EMOTOROLA LTD. 2000
1469
ISSUE 18 REVISION 0
CSFP download
To activate a CSFP download, carry out the following procedure: 1. 2. 3. 4. 5. Select the Load Mgmt icon from the Front Panel, the Software Load Management window opens. Select Database Mgt Activate Database from the menu bar, an xterm window opens. Enter the name of the appropriate BSS or RXCDR. Enter 2 for a CSFP directory. Enter the appropriate number corresponding to the database load name and press CR. The specified database is now active.
Configure a CSFP
To remove the need for the NE to be OOS for the whole of the time period of a download, CSFP devices can be configured at the BSC and remote BTSs. To configure CSFPs, carry out the following procedure: 1. 2. 3. Select the Load Mgmt icon on the front panel to open the Software Load Management window. Select the required BSS/RXCDR. Select CSFP Configure CSFP to open a confirmation box with the following message:
Do you really want to Configure CSFPs at <Site_name>?
4. 5.
Click OK to request parent NE to configure a CSFP device at each of its sites. To check the operational status of the CSFPs, select Options CSFP Status from the NESoftware window. Ensure that the CSFPs are in a disabled/unlocked No Code status so that a download can take place. Upload the database to the OMC.
6.
1470
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Initiate download to BSS/RXCDR

A download supplies the NE with a list of objects which describe the latest new load for that particular NE. The NE determines whether the list is consistent with the software load that is presently installed. If not, the new load is downloaded.
CSFP download
To carry out a CSFP download, carry out the following procedure: 1. 2. 3. 4. Select the Load Mgmt icon on the Front Panel to open the Software Load Management window. Select the required BSS/RXCDR. Select Edit New CSFP Load button to open the Software Inventory Dialog window. Double click on the load to be downloaded. The Software Inventory Dialog window closes and the software load is displayed as the value of New CSFP Load on the Software Load Management window. Load and activate the database for the CSFP. Select CSFP Download CSFP to open a confirmation box. Click OK. Select Load Mgt DownLoad Status to open the DownLoad Status window. Carry out the Check all sites and devices after BSC/RXCDR reset task.
5. 6. 7. 8. 9.
Normal download
To carry out a normal download, carry out the following procedure: 1. 2. 3. 4. Select the Load Mgmt icon on the Front Panel to open the Software Load Management window. Select the required BSS/RXCDR. Select Edit New Software Load to open the Software Inventory Dialog window. Double click on the load to be downloaded. The Software Inventory Dialog window closes and the software load is displayed as the value of New Software Load on the Software Load Management window. Select Edit Complete Load Enable from the menu bar. Select Load Mgt DownLoad Status to open the DownLoad Status window. Open an Event window to monitor the download operation. Check the status of BTS and RSL through the Event window. Audit the BSS.
5. 6. 7. 8. 9.
EMOTOROLA LTD. 2000
1471
ISSUE 18 REVISION 0
Enable/Disable database downloads

To ensure that particular loads are enabled, carry out the following procedure: 1. 2. 3. 4. 5. 6. Select the Load Mgmt icon on the Front Panel to open the Software Load Management window. Select the required NE(S). (Multiple NEs may be selected by holding down the CTRL button and selecting the NEs with the left mouse button). Select Edit Download Enable/Disable as required. Click OK in the confirmation window. Status is confirmed by an Enabled/Disabled status in the download column for each NE. Select File Close from the menu bar to exit.
Check all sites and devices after BSC/RXCDR reset

To ensure that all sites and devices are in the correct state after a BSC/RXCDR reset, carry out the following procedure: 1. 2. 3. Select the Maps icon on the front panel to open a Map List window. Double click on the Map name to open the map. Click on the site, and from the popup menu select OOS Devices to open the OOS Devices window for the site.
1472
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Unconfigure a CSFP
To restore a CSFP to its pre-configured CSFP functionality, carry out the following procedure: 1. 2. 3. 4. 5. Select the Load Mgmt icon on the Front Panel to open the Navigation tree. Select the required BSS/RXCDR. Select CSFP Unconfigure CSFP to open a confirmation box. Click OK to request parent NE to unconfigure a CSFP device at each of its sites. Upload the database.
Fallback to old database at BSC/RXCDR

There are at least two cases of fallback to a previous load: S S Fallback to previous database without CSFP. Fallback to previous database with CSFP.
The latter is the recommended fallback. 1. 2. 3. 4. Select the Load Mgmt icon from the Front Panel, the Software Load Management window opens. Select Database Mgt Fallback Database from the menu bar, an xterm window opens. Enter the NE name for which a fallback to a previous database is required. The system displays the database information of the backup database for that NE. Enter the number for the required database, and type Yes to proceed with the fallback.
Fallback to CSFP load

To fallback to an old CSFP load, carry out the following procedure: 1. 2. 3. 4. Select the Load Mgmt icon on the Front Panel to open the Navigation tree. Select the required BSS/RXCDR. Select CSFP Swap Code Load to change the current CSFP load to the new CSFP load, a confirmation box is displayed If the load name and version number to be swapped to are correct then click on the OK button to confirm the load name and version number.
EMOTOROLA LTD. 2000
1473
ISSUE 18 REVISION 0
Scheduling an upload
The schedule script gives the user the ability to schedule uploads from NEs at a given time. This script can only be run from the /usr/gsm/current/bin directory on the System Processor. This script can only execute while the OMC is running. Messages relating to the scheduler process are logged in the omcaudit file. The user has to be a member of the omc group. The user can create scheduled operations to run in the future by giving the time that the scheduled operation is supposed to be run. This would be similar to setting this operation up as a cron job. Scheduled operations should not be scheduled to run at the same time as statistic uploads. The maximum number of operations that can scheduled is 100. This is due to a limitation of the UNIX at command. The cron process on the System Processor must be running. On cutover to a new release the files must be relocated to the new /usr/gsm/current/bin directory.
Usage
The usage of the script is: schedule a ne_name timespec schedule l schedule L schedule r schedule R For example, schedule a BSS01 199807281830.00 schedule a NAME Where, a l L r adds a schedule operation. lists the scheduled operations the user has created. lists all scheduled operations recorded for all user ids. removes a scheduled operation. A list of operations will be displayed. Select the operation to be removed by specifying the job id. removes all scheduled operations for the current user. YYYYMMDDhhmm.SS
For example, to set up a scheduled operation for 1pm on August 30th 1999 for NE BSS01, the syntax usage is as follows : schedule a BSS01 199908301300.00
1474
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
UNIX at command
The script uses the UNIX at command to schedule operations. The schedule script uses the UNIX at command to run request_upload at a specified time. This sends a request to the uploader to upload a database from the NE which has been passed to request_upload as an argument.
EMOTOROLA LTD. 2000
1475
Overview of regular procedures
ISSUE 18 REVISION 0
Overview of regular procedures

List of procedures
The following procedures are provided in the remaining sections of this chapter: S S S S S Hourly procedures Daily procedures Weekly procedures Weekly system check procedures Routine administration procedures
1476
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Hourly procedures
Hourly procedures
Recommended procedure list
The following actions are recommended for hourly procedures: S S S S S Chase actions on Critical Alarms. Chase actions on Major Alarms. Check total_calls stats to ensure sites have been call processing (see Performance Management in Chapter 7 of this manual). Obtain a current OOS device report to ensure all NEs are operating as expected. See Displaying OOS devices from the navigation tree in Chapter 2. Confirm the map status.
Chase actions on Critical Alarms

Check the map for any nodes indicating Critical Alarms. Any outstanding Critical Alarms should be dealt with immediately following the procedure described in Maintenance Information: Alarm Handling at the OMC, (GSM-100-501) manual. If any Critical Alarm has not been cleared within one hour of its appearance, it should be escalated as described in this manual.
Chase actions on Major Alarms

Major Alarms should be dealt with as described in the procedures contained in Maintenance Information: Alarm Handling at the OMC, (GSM-100-501). If using a procedure results in a device requiring locking and unlocking in a quiet period, ensure this requirement has been logged so that the necessary action can be taken. See Chapter 3 and Device Management from the mapin Chapter 4 for easy methods of device locking/unlocking from alarm windows and from the map. The alarm should be cleared so that a later recurrence, should there be one, is observed. NOTE For some Internal Alarm System (IAS) alarms, if a device failure is the second failure (there is an existing Alarm for the same type of device) the effect is to raise the severity of the alarm. Whenever an IAS alarm is displayed, check the Operator Log to determine if an Alarm has already been logged for this device type. If an Alarm has been raised on the device previously and the device has not been repaired, raise the Severity level of the Alarms on the failed devices.
EMOTOROLA LTD. 2000
1477
Daily procedures
ISSUE 18 REVISION 0
Daily procedures
Introduction
The OMC operator must be aware of all faults in the network at all times and control the resolution of those faults. Site visits and configuration changes should be supervised by the OMC operator. It is the responsibility of the OMC operator to minimise downtime and ensure that the best possible service is provided to the user of the network under all circumstances.

The following daily procedures are recommended: 1. omcuser 2. Investigate outstanding alarms by using the following: Maps (are all nodes and links green and In Service) Event windows Out of Service (OOS) Device Display Event Log Search and Print (for more detailed information) NOTE Each Critical/Major Alarm from the previous 24 hours should be examined to ensure that no problems have been overlooked. Investigate any faults which have not been cleared. 3. 4. Examine fault log from previous day. Examine an OOS Device report for the whole network. Check why any OOS devices are OOS. See Displaying OOS devices from the navigation tree in Chapter 2. Check re-sync and audit logs. See Auditing logs and Resynchronizing logs in Chapter 6. Check that all daily system back-up routines and checklist, have been performed by the System Administrator, refer to Operating Information: OMC System Administration, (GSM-100-202). Check that scheduled network configuration changes have been successfully made and recorded. Ensure the MIB and maps are up to date. Check the Navigation Form. If not up to date, run an audit on the sites which are outdated. Audits can be scheduled to run overnight, when the traffic load is lightest. See Scheduling an audit in Chapter 6 for audit scheduling procedures. At the beginning of each shift, the OMC operator should review the state of the network and take any necessary action to deal with the outstanding issues.
5. 6.
7.
1478
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Daily procedures
Analysis of PM statistics
The most important Performance Management (PM) statistics are the Key Statistics which should be examined daily. Each morning, print out and examine the key statistics for the previous 24 hours, and identify any readings that deviate from normal (procedures for printing out key statistics are described in Chapter 7). For example: S S A low total_calls reading could indicate a potential problem and a high reading could indicate a need for additional capacity. High RF losses at a cell associated with a particular Base Transceiver Station (BTS). This should be investigated as it could indicate an antenna problem.
Examination of event logs

Each morning, run the Event Log processing scripts and examine the results for any inconsistencies. Alternatively, use the Event Log Search and Print feature to examine the Event Logs.
Event log scripts

Instructions for the use of the following scripts are provided in Using the event logging utilities in Chapter 3: S S S S S sld cel qfes ces dpr
Comparison of event logs

Each morning, examine the Event Log print outs for the previous 24 hours for any outstanding Critical alarms or Major alarms. For details of actions to be taken, refer to Checking alarms from the network map in Chapter 3 of this manual.
EMOTOROLA LTD. 2000
1479
Weekly procedures
ISSUE 18 REVISION 0
Weekly procedures
The following weekly procedures are recommended: S S S S Check Audit schedules and update. See Scheduling an audit in Chapter 6 of this manual. NE Database checks. OMC System changes. Hold a weekly meeting as described.
NE database checks
Network Elements (NE) database checks are required for the following reasons: S S S To ensure that the NE has the same database as the OMC. This can be seen from an Audit Inconsistency list, detailed in Auditing logs in Chapter 6. To clear out old databases and keep only the last three. To check if an upload has been made after NE database changes. When changes are made, they must be logged using whichever method has been decided by the customer.
When configuration changes at an NE database are made, the MIB is updated by performing an audit. It is also necessary to upload the NE database to the OMC to ensure the OMC has an up-to-date copy. There should be a maximum of three databases on the system for any BSS or RXCDR at any one time. For more information on the database checking procedure see Operating Information: OMC System Administration, (GSM-100-202).
1480
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Weekly procedures
Typical database directory structure

A typical BSS database directory structure is shown in Figure 14-21. There is a similar directory structure for a RXCDR.
YORK
00.00.00.00.02 database.list download.list current database
$DBROOT/ BSS/ BSS<name>
db950228122300 CSFP directory
00.00.00.00.02 database.list 00.02.00.00.02 YORK_BSGSM1.6.0.0 database.list download.list CSFP directory OTHER BSSs
fallback database for current load database for fallback load
Figure 14-21 A typical BSS database directory structure
Uploading
The Base Station Controller (BSC) holds the master copy of the database for the BSS, which is downloaded to the BTS when required. It is this master copy which is uploaded to the OMC. NE software load procedures are initiated by the OMC operator, refer to Load management: overview in Chapter 5. If any changes are made by Man Machine Interface (MMI) commands, to the master copy of the database, either at the BSC or OMC, the database must be uploaded to the OMC. An upload of the database must be made after any of the following has occurred: S S S A new database has been downloaded to the site since the last upload. One or more MMIs commands have been performed on the site either locally or from the OMC. A week has elapsed since the last upload from the BSC. (This is a precautionary measure).
EMOTOROLA LTD. 2000
1481
Weekly procedures
ISSUE 18 REVISION 0
Backup NE directory format

Backup NE directory names have the following format: <NE name>_<loadname>_<date time stamp> For example: PURTON_BSGSM1.5.0.0.0_951211203457 Where the load name is the existing current load and the date time stamp details when the change was effected.
Weekly meeting
It is recommended that a weekly meeting be scheduled between representatives from OMC Operators and the Motorola local office to discuss: S S S S Any outstanding Service Affecting faults from the previous week. Review configuration changes and planned maintenance work from the previous week. Planned work for the week ahead. Any issues relating to the future planning or expansion of the network.
A summary weekly report should be prepared prior to the meeting and actions agreed at the meeting should be recorded and circulated.
1482
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Weekly system procedures

Introduction
Periodically, for example, each week: S S Check the OMC audit logs for any software changes that have been made to the OMC Ensure that the correct software versions are installed at the MMI processors, system processor and NEs.
Checking OMC version

The version number of the OMC code running on the system processor can be determined using either the system processor console or any SPARCstation as follows: 1. omcadmin From the system processor console, login as omcadmin using the user id: omcadmin or from a SPARCstation, remote login to the system processor using the command: rlogin <hostname> where <hostname> is the name of the system processor. or if not omcadmin, perform the user switch using the command: su omcadmin 2. 3. Enter the password when requested. Change directories to /usr/gsm/current/bin by entering the following: cd $SYS_ROOT/bin 4. Enter the following command to determine the version number: /usr/ccs/bin/what omcinit 5. If using a SPARCstation: Logout as omcadmin using the command: logout Logout from the system processor using the keys: Ctrl-c 6. If using the system processor console logout using the command: logout Either,
EMOTOROLA LTD. 2000
1483
ISSUE 18 REVISION 0
Check software version at a NE

Check the version number of the code running at a NE as follows: 1. omcuser 2. 3. 4. Click on the node to be investigated. Click the TTY button to open the TTY interface to the NE. Enter the following MMI command at the CUST_MMI prompt: disp_version The response shows the software load version. 5. Close the TTY window by typing the following command: !logout Select the Remote Login icon on the front panel to display the list of Network nodes.
Check system after changes

After an upgrade to the OMC system, it is important to confirm that the software versions at each NE and on both OMC platforms (system processor and MMI processors) are compatible. Carry out the following procedure: omcuser 1. Refer to operator records to see what version of the OMC software should be running. Compare the OMC version with that displayed on the Front Panel display to confirm that the versions on system processor and MMI processor are the same and agree with the version in the records. Refer to the corresponding Release Notes for the OMC release to determine which versions of NE code are compatible with the RXCDR and OMC releases. Determine the releases at each NE and confirm that these are compatible with those specified in the OMC Release Notes. Confirm that the current load and new load displayed in the NE Software Loads window (see Chapter 5) are the same as the load displayed using the disp_version command. Any discrepancy is serious, as on the next reset the NE will take the new load as specified at the OMC. Either the new load must be amended or it must be downloaded to the BSS. The course of action to take depends on which load the BSS or RXCDR should have.
2. 3. 4.
1484
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Backups and archives

Each week, ensure that all scheduled backups and archives have been performed and that backup tapes are correctly labelled and stored.
EMOTOROLA LTD. 2000
1485
Routine administration procedures
ISSUE 18 REVISION 0

Procedures described
The following routine administration procedures are described: S S S S S Manually initiate network wide alarm and state resync. Set up and verify a schedule for network wide alarm and state resync. Set up and verify a schedule for configuration audits. Check alarm and state resync logs. Check configuration audit logs.
Manually initiate alarm and state resync

To manually initiate a resynchronization, carry out the following procedure (for further information please refer to Resync from a map in Chapter 2 of this manual): 1. 2. 3. 4. 5. Select the Maps icon on the front panel to display the Map List. Select the Network map from the Map List to display the Network map. Select Options Resync Network from this window to start resync. Select Options Resync Logs to view the resync logs. Check the resync results.
1486
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Schedule alarm and state resync

To resynchronize NEs on a regular basis, carry out the following procedure (for further information please refer to Scheduling a resync in Chapter 6 of this manual): 1. 2. 3. 4. 5. Select the Admin icon on the Front Panel to open the Admin Options window. Select the Resync Scheduler option to open the Resync Scheduler window. Select Edit Create from this window to open the rsSchedule Detailed View window. To insert the elements to be resynchronized, click the Scheduled Element button to open the Navigation tree. Select the Network element to be synchronized and double click to close the Navigation tree and insert the Network element in the Scheduled Element Name field. Select Periodic in the Execute Mode field. Enter start time and end time in the appropriate fields. Set the Interval field to 24 hours. Select File Create to create the new Scheduled resync. Select File Close to close the rsSchedule Detailed View window and check that the schedule is in the Resync scheduler window. Select File Close to close the Resync Scheduler window.
6. 7. 8. 9. 10. 11.
Schedule configuration audits

To carry out a configuration audit on a regular basis, carry out the following procedure (for further information please refer to Scheduling an audit in Chapter 6 of this manual): 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11.
EMOTOROLA LTD. 2000
Select the Admin icon on the Front Panel to open the Admin Options window. Select the Audit Scheduler option to open the Audit Scheduler window. Select Edit Create from this window to open the auSchedule Detailed View window. To insert the elements to be audited, select the Scheduled Element button to open the Navigation tree. Select the Network element to be audited and double click to close the Navigation tree and insert the Network element in the Scheduled Element Name field. Select Periodic in the Execute Mode field. Enter start time and end time in the appropriate fields. Set the Interval field to 24 hours. Select File Create to create the new Scheduled Audit. Select File Close to close the auSchedule Detailed View window and check that the schedule is in the Audit scheduler window. Select File Close to close the Audit Scheduler window.
1487
ISSUE 18 REVISION 0
Check alarm and state resync logs

To check the alarm and state resync logs, carry out the following procedure (for further information please refer to Resynchronizing logs in Chapter 6 of this manual): 1. 2. 3. 4. 5. Select the Admin icon on the front panel to open the Admin Options window. Select the Resync Logs option to open the Resync Logs window. Select the log of interest. Double click to display the full report. Check the report which contains a list of all completed resyncs, detailing the resynced item, status, errors experienced, times, types and owner. Select File Close to close the Resync Logs window.
Check configuration audit logs

To check the configuration audit logs, carry out the following procedure (for further information please refer to Audit logs in Chapter 6 of this manual): 1. 2. 3. 4. 5. Select Admin icon on the front panel to open the Admin Options window. Select the Audit logs option to open the Audit Logs window. Select the log of interest. Double click to display the full report. Check the report which contains a list of all completed audits, detailing the audited item, status, errors experienced, times, types and owner. Select File Close to close the Audit Logs window.
1488
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Checking LAN connections

Using the ping utility
All SPARCstations must be accessible from the system processor. The UNIX ping utility may be used to verify that the SPARCstations and system processor can communicate with each other, via the Local Area Network (LAN) (Refer to Figure 14-22). The ping utility is located in /usr/sbin on a Sun Sparc or E3000 series.
BNC terminator BNC T-connector BNC terminator
15-pin D-type
Ethernet T ransceivers Ethernet T ransceiver Other MMI Processors
Ethernet IOC System Processor
MMI Processor
Figure 14-22 Typical OMC connection of the LAN
System processor to MMI processors

To verify communication between the SPARCstations and the system processor, proceed as follows: 1. 2. Log into system processor locally. Check communications between the system processor and each SPARCstation in turn by entering the following: ping s <SPARCstation hostname> or ping s <SPARCstation IP address>
Example of output
If communication is possible between the system processor and a SPARCstation, the following output is produced:
PING<Terminal IP address>: 56 data bytes 64 bytes from<SPARCstation IP address>: 64 bytes from<SPARCstation IP address>: 64 bytes from<SPARCstation IP address>: 64 bytes from<SPARCstation IP address>: 64 bytes from<SPARCstation IP address>:
seq=0. seq=1. seq=2. seq=3. seq=4.
time=0. time=0. time=0. time=0. time=0.
ms ms ms ms ms
If no communication is possible, contact the System Administrator.

EMOTOROLA LTD. 2000
1489
ISSUE 18 REVISION 0
1490
EMOTOROLA LTD. 2000
Chapter 15
Recommended Reports
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
ii
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Chapter 15 Recommended Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview of recommended reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of recommended reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance management (statistical) reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of performance management (statistical) reports . . . . . . . . . . . . . . . . . . . . Cell activity reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Paging reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Quality of service reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network status reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link and channel usage reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH performance reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Daily performance management reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Report Option fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to using the Report Options fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up a daily report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up a daily peak hour report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up a weekly historical trending graph report . . . . . . . . . . . . . . . . . . . . . . . . Setting up a delimited report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault management reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of fault management reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
151 151 152 152 152 153 153 153 154 154 154 155 156 156 156 157 157 158 159 159
EMOTOROLA LTD. 2000
iii
ISSUE 18 REVISION 0
iv
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Overview of recommended reports
Overview of recommended reports

Types of recommended reports
There are two groups of recommended reports: S Performance management reports These reports enable the performance of the network to be monitored and managed to its optimum level. By generating performance management reports regularly, users can familiarise themselves with the optimum performance of their network and consequently recognise potential performance blackspots. Performance management reports use the statistics generated by the network elements and sent to the OMC at regular intervals. See Overview of performance management (statistical) reports for further details. If you need to know more about the individual statistics used in reports, see Maintenance Information: GSM Statistics Application (GSM-100-503) S Fault management reports These reports enable faults to be monitored and corrected. Most of these reports are created using the OMC GUI, see Overview of fault management reports for further details.
EMOTOROLA LTD. 2000
151
Performance management (statistical) reports
ISSUE 18 REVISION 0

Types of performance management (statistical) reports
Performance management reports use the statistics sent at regular intervals from the network elements to the OMC. NOTE Ensure statistics have been enabled before attempting to generate network performance reports. See Statistics management in Chapter 7 for further details. Performance management reports can help to manage and monitor the performance of the network. Reports can be created to show the following types of network information: S S S S S S S Cell activity Handovers Paging Quality of service Network status Link and channel usage TCH performance
The following sections list the reports Motorola recommended are created in each of these categories. Further reports can be created, if required, see Running a new report in Chapter 7. See Daily performance management reports in this chapter for a list of the reports Motorola recommend are created each day.
Cell activity reports

A number of reports can be created to show cell activity.
Peak hour reports

Peak hour activity is shown in the following reports: S S S S Total calls per cell report, see NO TAGCreating a total calls per cell report Call setup report, see NO TAGCreating a call setup report Dropped calls report, see NO TAGCreating a dropped calls report Call success rate report, see NO TAGCreating a call success rate report
Traffic load reports

Traffic load information is shown in the following reports: S S
152
Total calls per cell report, see NO TAGCreating a total calls per cell report Mean traffic per cell report, see NO TAGCreating a mean traffic per cell report NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Congestion reports
Congestion information is shown in the following reports: S S S S SDCCH blocking report, see Creating an SDCCH blocking report SDCCH access report, see Creating an SDCCH access report TCH blocking report, see Creating a TCH blocking report Worst 10 cells for TCH blocking report, see Creating a worst 10 cells for TCH blocking report
Sleeping cells reports

Sleeping cell information is shown in the following reports: S S Total calls per cell report, see Creating a total calls per cell report Attempted handovers report, see Creating an attempted handovers report
Handover reports
Handover information is shown in the following reports: S S S S S S Intra-BSS handover report, see Creating an intra-BSS handover report Inter-BSS handover reports, see Creating inter-BSS handover reports Inter-cell handover report, see Creating an inter-cell handover report Handover failure rate report, see Creating handover failure rate report Worst 10 cells for handover failure report, see Creating a worst 10 cells for handover failure report Handover cause report, see Creating a handover cause report
Paging reports
Paging information is shown in the following reports: S S Air interface paging report, see Creating an air interface paging report MSC paging report, see Creating an MSC paging report
Quality of service reports

Quality of service information is shown in the following reports: S S S S
EMOTOROLA LTD. 2000
Call setup report, see Creating a call setup report Worst 10 cells for call setup report, see Creating a worst 10 cells for call setup report Dropped calls report, see Creating a dropped calls report Call success rate report, see Creating a call success rate report
153
ISSUE 18 REVISION 0
Network status reports

Network status information is shown in the following reports: S S S S S S S Networkwide call success rate report, see Creating a networkwide call success rate report Networkwide call volume report, see Creating a networkwide call volume report Device status report, see Fault management reports Network outages report, see Fault management reports Outstanding alarms report, see Fault management reports GPROC utilization report, see Creating a GPROC utilization report Inhibited devices report, see Fault management reports
Link and channel usage reports

Link and channel usage information is shown in the following reports: S MTL utilization reports: S S S S S MTL congestion report, see Creating an MTL congestion report MTL MSU receive report, see Creating an MTL MSU receive report MTL MSU transmit report, see Creating an MTL MSU transmit report MTL link failure report, see Creating an MTL link failure report MTL unavailable report, see Creating an MTL unavailable report MTL in service report, see Creating an MTL in service report
CBL rejected frames report, see Creating a CBL rejected frames report OML rejected frames report, see Creating an OML rejected frames report RSL rejected frames report, see Creating an RSL rejected frames report XBL rejected frames report, see Creating an XBL rejected frames report Traffic channel usage report, see Creating a traffic channel usage report
TCH performance reports

TCH performance information is shown in the following reports: S S Mean path balance report, see Creating a mean path balance report Downlink receive quality per carrier report, see Creating a downlink receive quality per carrier report NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000
154
ISSUE 18 REVISION 0
Daily performance management reports

Motorola recommends the following reports are created each day to help manage the performance of the network: S Network health reports: S Networkwide call success rate report, see Creating a networkwide call success rate report Networkwide call volume report, see Creating a networkwide call volume report
Cell health reports: Dropped calls report, see Creating a dropped calls report Mean traffic report, see Creating a mean traffic per cell report SDCCH access report, see Creating an SDCCH access report Call success rate report, see Creating a call success rate report Total calls per cell report, see Creating a total calls per cell report
Congestion reports: SDCCH blocking report, see Creating s SDCCH blocking report TCH blocking report, see Creating a TCH blocking report Cell congestion report, see Creating a cell congestion report
Worst cells reports: Worst 10 cells for dropped calls report, see Creating a worst 10 cells for dropped calls report Worst 10 cells for congestion report, see Creating a worst 10 cells for congestion report Worst 10 cells for SDCCH access report, see Creating a worst 10 cells for SDCCH access report Worst 10 cells for SDCCH blocking report, see Creating a worst 10 cells for SDCCH blocking report Worst 10 cells for TCH blocking report, see Creating a worst 10 cells for TCH blocking report Worst 10 cells for handover failure report, see Creating a worst 10 cells for handover failure report
Cells with zero calls report, see Creating a cells with zero calls report
EMOTOROLA LTD. 2000
155
Using the Report Option fields
ISSUE 18 REVISION 0

Introduction to using the Report Options fields
This section provides recommendations on how to use the PM GUI Report Option fields (see Running a new report in Chapter 7) to produce the following types of PM reports: S S S S Daily Daily peak hour Weekly historical trend Delimited
Setting up a daily report

To set up a report to run daily, follow these steps: 1. 2. Select the statistics to be included in the report. Set the Report Options fields in the Performance Management window as shown in Table 15-1. Table 15-1 Daily report setup Field Format Tabular Type Output Time Mode Summary Level Interval Mode 3. 4. Select Option ... Trend, Graphical, or Tabular ASCII Screen or Printer Continuous None Relative
Save the report selections, see Stored selections in Chapter 7. Use PM scheduler to schedule the report to run daily, see PM report scheduler in Chapter 7.
156
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Setting up a daily peak hour report

To set up a report to run daily at peak hours, follow these steps: 1. 2. Select the statistics to be included in the report. Set the Report Options fields in the Performance Management window as shown in Table 15-2. Table 15-2 Daily report setup Field Format Tabular Type Output Time Mode Summary Level Interval Mode Start, End Select Option ... Trend ASCII Screen or Printer Blocked None Relative Enter the start and end times of the networks peak hours.
3. 4.
Setting up a weekly historical trending graph report

To set up a graphical report to show historical weekly trends, follow these steps: 1. 2. Select the statistics to be included in the report. Set the Report Options fields in the Performance Management window as shown in Table 15-3. Table 15-3 Daily report setup Field Format Tabular Type Output Time Mode Summary Level Interval Mode Start Day End Day Select Option ... Pareto ASCII Screen or Printer Continuous None Relative 1 5
EMOTOROLA LTD. 2000
157
ISSUE 18 REVISION 0
3. 4.
Setting up a delimited report

To transfer statistical report data to another application, create a delimited file. To set up a delimited file for exporting to another application, follow these steps: 1. 2. Select the statistics to be included in the report. Set the Report Options fields in the Performance Management window as shown in Table 15-4. Table 15-4 Daily report setup Field Format Tabular Type Output Time Mode 3. 4. Select Option ... Pareto or Tabular Spreadsheet File Continuous
158
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Fault management reports

List of fault management reports
Fault management reports help an operator to identify and manage faults in the network. Fault management reports can be created to show: S S S S S Device status, including OOS devices and inhibited devices, see Reporting OOS devices. Network outages, see Reporting outage times. Contained devices, see Creating a contained devices report. Outstanding alarms, see Creating an outstanding alarms report. Whether or not a cell is carrying traffic, see Displaying whether a cell is carrying traffic
EMOTOROLA LTD. 2000
159
ISSUE 18 REVISION 0
1510
EMOTOROLA LTD. 2000
Index
EMOTOROLA LTD. 2000
I1
ISSUE 18 REVISION 0
I2
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Symbols
$EM_LOG, 644
A
Abort loads, bootload, 1037 Aborting audit in progress, 1115 resync in progress, 1131 traces, 813 Access Control, 155 Access control, 113 command partitioning, 113 user profile list, 114 Accessing PM, 132 Accessing remote login, 819 Acknowledging alarm arrival, 631 activate_db, 926, 934 Activating a database for CSFP download, 1024 for normal download, 1022 Active event logs, 651 Active events table (AET), 53 Admin, 111 audit restrictions, 112 overview, 218 resync logs, 1129 scheduling a resync, 1122 scheduling an audit, 117 Admin icon, use of, 155 Administration, options, 155 AET, 53, 513, 718 Alarm actions, 144 help, 145 intermittent, 513 investigation, 144 notification, 144 reporting, 36 threshold, 1312 types FMIC, 61 intermittent, 61 OIC, 61 Alarm comment field, 610, 1452
EMOTOROLA LTD. 2000
Alarm display window, 52, 58 access, 510 definition, 58 Alarm handling, 513, 629, 145 CLEAR, 631 HANDLING, 631 optimising, 146 options, 513 SEEN, 631 Alarm state, 34 Alarm subscription lists, events, 57 Alarm throttles deleting, 641 time period, 640 viewing, 639 Alarm window opening from event mgmt, 630 opening from map, 63 Alarm/Event subscription, 56 Alarms acknowledging, 631 categories, 76 CERM, 710 clearing, 633, 718 colours, 36, 311 comment field, 610, 144, 1452 critical, 147, 148 major, 148 definition, 55, 710 disk usage, 713 display window, 37 FMIC, 710 handling, 54, 633 IAS, 147 icon, 219 intermittent, 710 introduction, 61 logging, 631 major, 147 multiple, 79 NEW, 633 OIC, 710 OIC alarm clearing, 633 opening window, 630 removing, 633 save alarm context, 78 SEEN, 633 severities, 77 summary, 79 summary window, 38 throttling, 639, 719 unhandle, 633 view, 63 view menu, 68 viewing from map, 420, 63 viewing from map popup, 420
I3
ISSUE 18 REVISION 0
Alarms icon, 156, 310 Alarms severity, icon colour, 311 Archives, scheduling, 1451 Audit, 111 aborting while in progress, 1115 audit logs, 1113 definition, 912 inconsistency report, 1116 restrictions, 112 Audit inconsistency report, 1117 printing, 1118 updating database, 1118 viewing, 1117 Audit log management, 1120 Audit logs, 155 deleting, 1119 printing list of, 1114 viewing , 1113 Audit scheduler, 155 Audits, 92 Auto Initiate file, 56, 510 Auto initiation file, 654 creation of, 654 Auto initiation of windows, 629 autoinit.cnfg, 654 Axis scale, 1329
Batch method of remote login, 826 creating command files, 827 exit codes, 832 exiting session, 827 starting a batch session, 826 BATCH_IPC_TIMEOUT, environment variable, 831 BATCH_NERESP_TIMEOUT, environment variable, 831 batch_rlogin, 941 BCCH, 115 Bill of materials, BOM, 126 Blacklist, 616, 143 Blacklisting events/alarms, 56 BOM, bill of materials, 126 BSC, 1411 BSS, 111, 818, 820, 1411 find BSS parent of a cell, 87 operation and maintenance, 125 BSS command logging. See Command logging BSS object, 315 BSS response logging. See Response logging BSSspecific, 1028 BTS, 1411 RCU, DRI, 114
C
Call trace, 812, 94 aborting a trace, 813 deactivate a trace, 814 deleting a trace, 816 trace records, 814 trace view window, 812 view traces, 812 CBC, 119 CBL, 119 CDE. See Common Desktop Environment cel, 519, 656 Cell exception report, 1436 find, 86 BSS parent, 810 with a LAC, 810 with zero calls, 1437 Cell configuration, logical devices, 116 CERM, 710 CERM feature, 635 CIC alarms, 637 RCI alarms, 635 NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000
B
Background maps, 36 Backups, scheduling, 1451 Batch, 818, 941 Batch manager (batch_rlogin) associated parameters, 831 command file creation, 831 command file format, 831 environment variables, 831 formats, 829 input file example, 834 log file creation, 831 exit codes, 832 format, 831 output file example, 835 path to, 829 running, 829 terminating, 831
I4
ISSUE 18 REVISION 0
ces, 519 ces (Clean Event Stream), 659 examples, 659, 660 Change request forms, 1455 Change requests, implementation, 1455 Changing device states, 715 Changing security level in TTY, 821 Changing the network, 94 Channel status, 838 Checking a resync, 914 Checking audits, 914 Checking subscriptions, 632 chg_level, 824 chg_throttle, 641 CIC alarms, 637 Circuit Error Rate Monitor feature, 635 Circuit Identity Code alarms, 637 Circuit status, 836 CLEAR, 631 Clear value, 1314 Closing a window, 224 CM MIB, 144, 32, 94 automatically created objects MMS, 319 NESoftware, 319 Source, 319 SWInventory, 319 TRX, 319 call trace, 94 definition, 312 Command log file, 1456 Command logging, 1456 disable, 1457 enable, 1457 setting variable, 1457 Command partitioning, 113 Common Desktop Environment, 25 file manager, 25 front panel, 25 style manager, 25 CommsLink object, 315
EMOTOROLA LTD. 2000
Completed reports, 1349 deleting, 1350 list search, 1353 opening, 1349 reloading, 1352 renaming, 1351 Config Mgmt, overview, 213 Config Mgmt icon, use of, 150 Configuration changes, 937 Configuration mgt, 136, 91 functions, 91 Configuration objects, 314 Configuration status, 938 Configure CSFP, 1032 Configure CSFP , 927 Console example messages, 149, 213 overview, 212 Console icons, use of, 149 Consolidated alarms, 512, 65 config tag, 66 functional unit severity, 66 log search menu, 68 OOS devices, 67 reconfiguration information, 66 report format, 512, 65 view menu, 68 Contained devices report, 83 filtering devices, 83 from find window, 88 Containment, managed objects, 113 Creating command files using batch, 827 Criteria filter, 1327 sort/filter, 1326 Critical alarms, 147, 148 cron, 666 setting up, 666 CSFP abort download, 1035 configure CSFP, 1032 database activation, 1024 download, 1032 fallback to previous SW load, 1036 introduction, 101 loading an existing database, 1020 status, 927 status form, 1035 unconfigure, 1034 CSFP download, 926, 929 abort, 929 monitoring, 929 process, 929
I5
ISSUE 18 REVISION 0
Current intervals, 1311 Custom statistic, 1338 copying and pasting, 1338 creating, 1338 deleting, 1341 filtering, 1342 renaming, 1340 searching a list, 1343 Custom statistics manipulation, Creating a new custom statistic, 1217 Custom Statistics Manipulation window, 1338
Device administrative state, 74 operational state, 75 Device management, devices supported, 440 Device management from map INS a device, 82 locking a device, 81 Resetting a device, 82 unlocking a device, 81 Device Mgt, 136 Device mode, 47 Device reset. See Resetting devices Device status, 74, 144 viewing from Navigation tree, 442 Devices, graph, 1359 Directory structure, database, 1411 Disable event logging, 653 software download, 107 disp_throttle, 641 disp_version, 1450 Display active event logs, 651 database information, 1011 enabled statistics, 137 modifying, 1357 setenv, 221 Downlink, 116 Download CSFP, 927 Download process, 924 Download status, 152, 105 Downloading, overview, 101 Downloading an NE database conventional download, 1028 CSFP download, 1025 dpr, 519 dpr (Data Printer), 663 command line format, 664 example, 665 DRI, 114, 115 DTE address mapping, 1478
D
Daily procedures, 148 Data, scalefactor, 1328 Database backup, 1412 directory structure, 1411 timestamp, 1412 upload, 1411 Database checkpointing, 94 Database checks, NE, 1410 Database management, 932 activating databases, 1022, 1024 backup, 933 utilities, 934 Database schema definition, 139 size, 139 Database upload, 932 database_info, 934, 1011 DataGen, 93, 1015 DBMS, 134 Deactivate a trace, 814 Deleting map, 428 scheduled audit, 1112 trace, 816 Delimited reports, 1331 Detailed view definition, 910 edit mode, 910 from find window, 87 monitor mode, 910 viewing from map, 426
I6
E
EAS alarm objects, 817 Editing a file Xedit commands, 226 Xedit, 225 NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
EM proxy process, 33 EM sub schema, 139 EM utilities ces, 659 dpr, 664 sld, 661 Enable event logging, 652 software download, 107 Environment variable $EM_LOG, 644 BATCH_IPC_TIMEOUT, 831 BATCH_NERESP_TIMEOUT, 831 DISPLAY, 221 MMI_FILTERS_CHARS_ADMIN, 615 OMCaudibleseverity, 219 RL_LOGCDMS, 1457 RL_LOGRESPS, 1457 Ethernet, 127 Ethernet support, 138 Event display window, 58 definition, 58 Event interface, 136 Event log, search window, 518 Event Logfile archiving, 515 creation, 515 definition, 515 location, 515 naming, 516 rollover, 515
Event logging, 642 cel, 656 ces, 659 cron, 666 disabling, 653 display active event logs, 651 dpr, 663 enabling, 652 filtering, 647 full format, 645 list order, 646 loading event logs, 644 message format, 645 multiple files, 643 opening, 643 printing search windows, 651 qfes, 658 reloading event logs, 650 search window, 642 searching, 643 sld, 660 sort criteria, 646 sort field, 646 utilities, 656 wide format, 645 Event logs, 517, 149 scripts, 149 search and print, 149 Event logs icon, 517 use of, 154 Event management introduction, 61 subscription lists, 613 subscriptions, 622 Event mgmt alarm windows, 630 event windows, 630 overview, 214 Event Mgmt icon, use of, 150 Event windows, 630 configuring, 514 opening from event mgmt, 630 Event/alarm mgt, 136, 51 functions, 51 Event/alarm subscription, 56, 59 blacklist, 56 blocking, 56 criteria, 56 functions, 59 thresholding, 56
EMOTOROLA LTD. 2000
I7
ISSUE 18 REVISION 0
Event/alarm utilities, 519 cel, 519 ces, 519 dpr, 519 post processing, 520 qfes, 519 sld, 519 use, 520 Events definition, 55 introduction, 61 opening window, 630 Events in alarm subscription lists, 57 Example batch_rlogin command format, 834 input file, 834 output file, 835 Exiting batch session, 827 forms session, 839 TTY session, 824 Expert desktop, 211 Expert front panel, 17
Fault management, 53 alarm popup menu, 1421 alarm window, 1421 OOS devices, 67 definition, 71 from map, 81 from navigation tree, 435 local maintenance terminal, 73 principles, 71 process, 73 Fault management from nav tree, 435, 1421 INS a device, 437, 1423 lock a device, 435, 1421 reassign a device, 438, 1425 reset a device, 437, 1423 reset a site, 437, 1423 shutdown a device, 436, 1422 swap a device, 439, 1425 unlock a device, 436, 1422 Fault Management Initiated Clear. See FMIC Fault management initiated clear (FMIC), 513, 710 fileNEavailable, 622 Filter, criteria, 1327 Filtering event logs, 647 event messages, 647 NE listing, 1322 statistics listing, 1322 Find, 85 BSS parent of cell, 810 cell with LAC, 810 contained devices, 88 detailed view, 87 examples, 89 map, 88 navigation tree, 87 NE, site, cell, 86 overview, 216, 85 parent of site or cell, 87 rlogin, 88 site, 89 use of, 153 window, 153 FMIC, 513, 61, 710 clearing, 718
F
Fallback, definition, 931 Fallback to previous database, 1030 Fallback to previous SW load, CSFP, 1036 Fallback_db, 1030 fallback_dl, 931 Fault escalation, 720 Fault handling definition, 714 process, 714 remote login, 717 Fault log, 148
I8
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Forms, 818 disabling logging, 839 displaying channel status, 838 displaying circuit status, 836 enabling logging, 839 exiting, 839 local transcoding, 838 remote transcoding, 838 worksheet cautions, 836 FPOMCAUDIT file, 1379 invalid duration, 1379 Front panel icons, 211 admin, 218 alarms, 219 config mgmt, 213 console, 212 event mgmt, 214 find, 216 help, 219 load mgmt, 215 logging, 218 network, 217 performance, 214 remote login, 217 use of, 149 xterm, 219 Full zoom out, 411 Functional unit severities, 66 on the map, 47
Hardware devices, 316 Help, 145 overview, 219 Help icon, use of, 156 Hierarchy, network, 125 Hourly procedures, 147
I
IAS alarm, 147 Icons network, 41 OMC front panel, 147 In service (INS) state, 34 Information flow, OMC and NEs, 124 INFORMIX, 140 Informix, environmental variables, 1379 INS a device from map, 82 INS device, 437 Installing a software load, 108 Installing an NE database, 1013 from a specified directory, 1019 from DataGen, 1015 from OffLine MIB, 1016 from tape, 1014 Interfaces, GUI, command line, 16 Intermittent, 61 Intermittent alarms, 719 clearing, 718 Intervals, 139 current, 1311 setting, 1311 ISG 6525 packet switch, 1461 CPU utilization, 1465 displaying stats, 1462 ISG 6560 MPRouter, 1472 displaying stats, 1473 ISG 6560 router, CPU utilization, 1477 ISG packet switch port record list, 1471 print configuration, 1466 route selection table, 1470
G
GPROC2, 111 Graphic objects, maps, 313 Graphical output modifying, 1357 saving, 1362 Graphical User Interface (GUI), OMC MMI, 146 GSM network, 110 GUI, 142 exiting, 210 restarting, 29
H
HANDLING, 631 Handling alarms, 633 overview, 629 Handover control, 116
EMOTOROLA LTD. 2000
K
Key statistics, 151, 125
I9
ISSUE 18 REVISION 0
L
LAN checking connections, 1483 ping, 1483 Link failure, 1480 Links add, 1447 delete, 1447 maps, 36 physical/logical, 117 Load event log, file selection window, 644 Load management, 94 BSSspecific files, 1028 complete load flag, 1028 conventional download, 1026 CSFP, 101 Database Mgt menu, 1013 database_info, 1011 definition, 916 disabling software download, 107 displaying database info, 1011 downloading database, 1025 enabling software download, 107 fallback to previous database, 1030 fallback_db, 1031 installing a SW load, 108 installing NE database, 1013 introduction, 101 loading NE database, 1013 NE database utilities, 1013 NE software loads, 104 options, 152 removing a SW load, 109 requirements, 916 resetting an NE, 1029 swapping a CSFP load, 1034 unconfigure CSFP, 1034 uploading an NE database, 1038
Load mgmt, overview, 215 Load Mgmt icon, use of, 152 load_db, 926, 934 Loading an NE database from a specified directory, 1019 from DataGen, 1015 from OffLine MIB, 1016 from tape, 1014 Local maintenance terminal, 73 Local transcoding, 838 Lock device, 435 Locking a device from map, 81 Logbook, 147, 148 examples, 1452, 1453, 1454 keeping of, 1452 logging network changes, 1455 Logging alarms, 631 events. See Event logging overview, 218 Logging in remotely. See Remote login Logical groups, 314 Hardware devices, 316 Logical links, 317 Radio frequency, 317 Software functions, 317 Logical link, OML, MTL, RSL, XBL, CBL, 119 Logical links, 317 Login screen, 23
M
Major alarms, 147, 148 Management information tree (MIT), 57
I10
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Map, 32 add, 1445 add a node, 1446 add links, 1447 automatically created objects Map, 319 MapLink, 319 MapNode, 319 background, 1445 background file, 1445 changing level, 415 closing, 44 configuration, 35 delete a node, 1446 delete links, 1447 deleting, 428, 1445 display, 153 contracting a node, 413 expanding a node, 411 expanding a node cluster, 411 from find window, 88 full zoom out, 411 INS a device, 82 links, 36 locking a device, 81 moving a node, 411 moving to navigation tree, 429 opening, 43 printing, 417 remote login, 418 resetting a device, 82 resync from, 419 set up, 1445 state changes, 36 unlocking a device, 81 viewing alarms, 420, 63 viewing detailed view, 426 viewing OOS devices, 422, 424 zooming, 416 Map display, 45 alarm severity colours, 49 colour legend, 48 device states, 49 map icons, 410 Map list, 41 Map modes device mode, 47 subscriber mode, 46
MapLink, 313 MapNode, 313 Maps, 217, 34 background maps, 36 configuration objects, 312 graphic objects, 312 introduction to, 41 Maps icon, 31 use of, 153 Measurement types, 123 MIB objects, 96 MIT, 57 MMI command line interface, 19 configurations, 141 Graphical User Interface (GUI), 146 GUI front panel, 17 operator name field, 147 processors, 141 running, 220 version number field, 147 MMI_FILTER_CHARS_ADMIN, 615 MMS, MSI, 113 Modifying graphical output, 1357 selections, 1356 Modifying a scheduled audit, 1111 Motorola OMC, typical configuration, 126 Mouse, terminology, 21 Mouse button controls left, 28 middle, 28 right, 27 MSC object, 315 MSI, MMS, 113, 123 MSI object, 316 MTL, 119 Multiplexer, 121, 128
N
Navigation form, 91
EMOTOROLA LTD. 2000
I11
ISSUE 18 REVISION 0
Navigation tree alarm throttling, 639 autoclose, 434 checking device status, 442 closing, 431 definition, 98 fault management, 435 from find window, 87 introduction, 430 moving level, 432 opening, 431 opening from map, 429 panner, 432 porthole, 432 printing, 445 use of, 98 viewing OOS devices, 443 NE find, 86 menu, 1319 software version, 1450 NE database checks, 1410 backup NE directories, 1412 uploading, 1411 NE database utilities, 1013 NE software detailed view form, 1026 NE software load, detailed view, 922 NE software loads, 152, 104 NE software version, 1450 NE.MAP, 94, 912 Network devices, 123 hierarchy, 125 traffic capacity, 129 Network changes, 1455 Network configuration, 34 Network File System (NFS), 141 Network management centre, NMC, 125 Network map, 32 configuration, 35 overview, 217 Network maps, 34 Network Maps icon, use of, 153 Network object, 314 Network planning, 1455 Network status summary, 31
I12
NFS (Network File System), 141 Night concentration, 220 Night concentration configuration, 143 NMC, 125 Node add, 1446 contracting, 413 delete, 1446 expanding , 411 moving on map, 411 Node cluster, expanding, 411 Nonnumerical data, symbols ?, 1336 /0, 1336 N/A, 1336 NonStopUX A22 IPM02, 138 NSS, 94 features, 31 NSS subscription lists, displaying, 615
O
Objects definition, 98 Map, automatic creation of, 319 MapLink, automatic creation of, 319 MapNode, automatic creation of, 319 MMS, automatic creation of, 319 NESoftware, automatic creation of, 319 Source, automatic creation of, 319 SWInventory, automatic creation of, 319 TRX, automatic creation of, 319 OIC, 513, 61, 710 clearing, 718 OIC alarm clearing, 633 OMC logging in, 23 login screen, 23 running remotely, 220, 221 OMC database, 139 OMC functions, 111 OMC MMI, Graphical User Interface (GUI), 146 OMC object, 315 OMC system changes, 1449 OMC system configuration hardware impact, 135 single platform processor, 13 NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
OMCR basic configuration, 13 command line interface, 19 communication with GSM network, 11 definition, 11 GUI front panel, 17 Network management functions, 12 processes, 136 OMCaudibleseverity, enabling alarms icon, 219 OMCINIT, 149 OML, 119 troubleshooting, 1480 Online help, 156 OOS devices fault management, 67 in a consolidated alarm, 67 viewing from map, 422, 424 viewing from navigation tree, 443 Opening stored selection, 128 Operating system, NonStopUX A22 IPM02, 138 Operator Initiated Clear. See OIC Operator initiated clear (OIC), 513, 710 Out of service (OOS) state, 34, 715
Performance mgt, 136, 121 accessing PM GUI, 126 command line reports, 1212 data flow, 122 main window, 126 measurements, 122 reports, 125 Periodic auditing, 914 Periodic supervision of accessibility (PSA), 712 Physical link, PATH, 118 ping utility, 1483 Planning a network, 1455 PM accessing, 132 completed reports, 1349 from contained devices, 133 from front panel, 132 from map, 133 from nav tree, 133 opening window, 1315 PM report logs, 134 PM report scheduler, 133, 1363 deleting a schedule, 1368 from Admin, 1364 modifying a schedule, 1367 printing a report schedule, 1368 printing a schedule detailed view, 1368 Selection Name window, 1363 PM reports delimited, 1331 display menu, 1335 format, 1323 pareto, 1323 trend, 1323 interval mode absolute, 1325 relative, 1325 nonnumerical data, 1336 symbols, 1336 output, 1324 reset file indicator data, 1335 saving, 1330 summary level, 1324 tabular format, 1324 time mode, 1323, 1324 blocked, 1324 continuous, 1324 discrete, 1324 PM Reports Logs, 155 PM reports on Web, 1215, 1354
P
Packet switch, 121, 128 See also ISG 6525 packet switch Panner, 432 Pareto, 125 Password, rules for choosing, 23 PATH, physical link, 118 Performance, overview, 214 Performance icon, use of, 151 Performance management analysis, 149 command line reports, 1372 introduction, 131 reports, 131 statistics, 131 Performance measurements, 124
EMOTOROLA LTD. 2000
I13
ISSUE 18 REVISION 0
PM Reports Scheduler, 155 PM sub schema, 139, 94, 912 PM troubleshooting, 1375 fpomcaudit file, 1379 invalid duration, 1379 informix environmental variable, 1379 key statistic, 1375 pm reports, 1377 ?, 1378 /0, 1378 absolute time mode, 1377 blocked, 1377 continuous, 1377 discrete, 1377 from the command line, 1378 N/A, 1378 relative time mode, 1377 pm_resynch, 1379 pmgui.cfg file, 1378 pmguiaudit file, 1379 raw statistic, 1375 statistics, 1375 alarmable, 1377 asynch, 1376 data types, 1376 halfhourly reporting, 1375 hourly reporting, 1375 parser, 1376 to the OMC, 1376 PM_RESYNCH, 1379 PMGUI.CFG file, 1378 PMGUIAUDIT file, 1379 Porthole, 432 Power budget, 116 Power control, 116 Printing event log search window, 651 map, 417 navigation tree, 445 scheduled audit, 1112 Private exchange packet data network, PXPDN, 128 Procedures daily, 148 hourly, 147 weekly, 1410 Processor code version, 1449 Protocol stacks, TCP/IP, Ethernet, X11, X25, 127 PSA, definition, 712 PXPDN, 128
I14
Q
qfes, 519, 658
R
Radio Channel Identifier alarms, 635 Radio frequency, 317 Raw statistics, 151, 125 measuring, groupings, 123 rc.cnfg, 24 RCI alarms, 635 RCU, 114 RDBMS, 139 Reassign a device, 715 Reassign device, 438 Reloading event logs, 650 Remote login, 136, 818, 939 accessing, 819 batch, 818 batch, 941 batch access, 826 forms, 818 from find window, 88 from map, 418 no connection, 418 overview, 217 starting a TTY session, 820 TTY, 818 TTY interface, 941 using forms, 836 using TTY, 820 Remote login icon, 154 Remote transcoding, 838 Removing a software load, 109 Report formats, 125 Reset device, 437 Reset file indicator, 1211, 1335 Resetting a device from map, 82 Resetting an NE, 1029 Resetting devices BSC, 1458 BTS, 1459 from command line, 1458, 1459 RXCDR, 1458 Site, 437, 1423 Response logging, 1457
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Resync, 111 aborting while in progress, 1131 definition, 711 enabling, 24 from map, 419 a node, 419 network, 419 no connection, 419 rc.cnfg, 24 Resync function, 142 Resync logs, 155 deleting, 1133 introduction, 1129 printing list of, 1130 viewing list, 1129 Resync report, 1131 printing, 1132 viewing, 1131 Resync scheduler, 155 resyncAlarm, 711 resyncState, 711 RL_LOGRESPS, 1457 Rollover, 515 Routine administration tasks, 1438 RSL, 119 RTF, 115 BCCH, 115 nonBCCH, 115 Running a delimited report, 1213 Running a scheduled report, 1213 Running report using command line, 1212 using PM GUI, 1211 RXCDR, 818, 820, 1411 functions, 111 operation and maintenance, 125 RXCDR object, 315
Scheduling a resync, 914, 1122 creating, 1123 deleting, 1128 modifying, 1126 printing reschedule list, 1128 Scheduling an audit, 117, 118 deleting, 1112 modifying, 1111 printing, 1112 Scheduling audits, 914 Screen, setup, 142 Search completed report list, 1353 NE listing, 1319 statistics listing, 1319 Search event log window, 518 Security levels, 939 SEEN, 631 Selections, modifying, 1356 Selections window, 127 Shutdown device, 436 Single platform processor, 13 Site, find, 86, 89 Site configuration, CELL, 114 SITE object, 315 SITE.MAP, 94, 912 sld, 519 sld (Subscription List Daemon), 660 examples, 662 output format, 661 Software elements, system processor, 136 Software functions, 317 Software inventory, 152 Software inventory window, 917 Software load archive, 921 delete, 921 Software load installation, 919 criteria, 920 load names, 920 Software Load Management window, 103 Database Mgt menu, 1013
S
Save alarm context, 78 Saving, PM reports, 1330 Scale, axis, 1329
EMOTOROLA LTD. 2000
Software load mgt, 136 Software loads, new, 104 Sort, criteria, 1326 SPARC station setup, 142 setup checklist, 143
I15
ISSUE 18 REVISION 0
SPARCstation, 13 SPARCstation 5/IPX, 145 disk size, 145 SQL, 140 State changes admin and operational, 39 on map display, 36 Statistics alarmable, 1377 analysis of, 149 clear value, 1314 custom, 131, 1338 data types, 1376 disabling, 139 enabling, 136 intervals, 139 key, 131, 1375 menu, 1319 raw, 131, 1375 status window, 1313 total_calls, 149 Statistics management, 135 Status summary window, 34 Sub schema, EM, PM, 139 Subscriber mode, 46 Subscription lists, 938 blacklist, 616 creating new, 619 deleting, 621 displaying NSS, 615 introduction, 613 modifying, 620 opening, 614 renaming, 621 viewing available, 614 Subscriptions accessing, 623 adding, 624 blocking, 624 checking, 632 deleting, 628 displaying, 624 introduction, 62, 622 modifying, 627 normal, 624 renaming, 627 Swap a device, 715 Swap CodeLoad, 928 Swap device, 439 Swapping a CSFP load, 1034
I16
Sysgen, 93 System changes, 1449 System processor, software elements, 136 System status display, 156
T
TCP/IP, 138 Throttling alarms, 639 definition, 719 intermittent, 719 total_calls, 149 Trace records, 814 Trace View window, 812 Traces deactivate, 814 delete, 816 view, 812 Traffic capacity, network, 129 Transceiving, DRI/RTF groups, 115 Trend, 125 Troubleshooting, OML, 1480 TTY, 818, 820, 941, 1450, 1459 changing security level, 821 chg_level, 824 exiting, 824 starting session, 820 TTY interface, 941
U
Unconfigure CSFP, 928 Unlock device, 436 Unlocking a device from map, 81 Uplink, 116 Upload status, 152, 105 Uploading, database, 1038, 1411 User profile list, 114 Using a SPARCstation, 21 monitor controls, 22
W
WAN, 127 Weekly procedures, 1410 NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000
ISSUE 18 REVISION 0
Wide area network, 127 Window changing size, 223 closing, 224 Window controls, 223 menu buttons, 224 peripheral, 223
X11, 127 XBL, 119 Xedit, 225 edit commands, 226 editing a file, 225 opening, 225 Xterm icon, 219 opening window, 28 Xterm icon, 156
X
X.121 address, 938 X.121 DTE addresses, 1478 X.21 address, 121 X.25, 127
Z
Zooming a map, 416
EMOTOROLA LTD. 2000
I17
ISSUE 18 REVISION 0
I18
EMOTOROLA LTD. 2000

Net Moto

Загружено:

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

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

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

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

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

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

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

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

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

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

Net Moto

Загружено:

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

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

For:cll Printed on:Thu, Oct 12, 2000 03:37:47 From book:NET01 (OMC02) Issue 18 Rev0 Document:tabs Last saved

CHAPTER 2 GETTING STARTED

CHAPTER 3 NETWORK MANAGEMENT

CHAPTER 4 MAP AND TREE PROCEDURES

CHAPTER 5 FAULT MANAGEMENT

CHAPTER 6 EVENT MANAGEMENT 1

CHAPTER 7 EVENT MANAGEMENT 2

CHAPTER 8 DEVICE MANAGEMENT

CHAPTER 9 CONFIGURATION MANAGEMENT

CHAPTER 10 LOAD MANAGEMENT

CHAPTER 11 ADMINISTRATION PROCEDURES

CHAPTER 12 PERFORMANCE MANAGEMENT 1

CHAPTER 13 PERFORMANCE MANAGEMENT 2

CHAPTER 14 RECOMMENDED OPERATIONS

CHAPTER 15 RECOMMENDED REPORTS

Cellular Infrastructure Group

NET01 (OMC02) OMC NETWORK OPERATIONS

FOR TRAINING PURPOSES ONLY

NET01 (OMC02) OMC NETWORK OPERATIONS

FOR TRAINING PURPOSES ONLY

NET01 (OMC02) OMC NETWORK OPERATIONS

ISSUE 18 REVISION 0 Software Release 4

NET01 (OMC02) OMC Network Operations

E Motorola 1993 2000 All Rights Reserved Printed in the U.K.

EMOTOROLA LTD. 2000

NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY

Copyrights, notices and trademarks

NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY

NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY

NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY

NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

Chapter 2 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

EMOTOROLA LTD. 2000

NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY

Chapter 3 Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

Chapter 4 Map and Tree Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY

NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

Chapter 5 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY

NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

Chapter 6 Event Management 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY

Chapter 7 Event Management 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY

NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

776 776 776 776

Chapter 8 Device Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY

Chapter 9 Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

NET01 (OMC02): OMC Network Operations FOR TRAINING PURPOSES ONLY

Chapter 10 Load Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .