Omc-R System Adm

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

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
2
2
2
3
3
3
4
5
5
5
5
6
7
7
7
7
8
8
8
9
9
9
11
12
12
12
12
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OMC-R system configuration. . . . . . . . . . . . . . . . . .
Introduction to OMC-R system configuration . . . . . . .
Typical hardware architecture of OMC-R system . . . . .
OMC-R specifications . . . . . . . . . . . . . . . . . . .
GUI sessions and GUI server memory . . . . . . . . . . .
Factors influencing Processing Capability of GUI Servers .
Operator workstations . . . . . . . . . . . . . . . . . . .
Optional processors . . . . . . . . . . . . . . . . . . . .
Software requirements. . . . . . . . . . . . . . . . . . .
Configuring the OMC-R SunFire and Netra system processors
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-2
1-3
1-3
1-4
1-4
1-5
1-6
1-6
1-7
1-7
1-9
Revision history . . . . . . . . . . . .
Version information . . . . . . . .
Resolution of Service Requests . .
Incorporation of Change Notices. .
General information . . . . . . . . . .
Purpose . . . . . . . . . . . . . .
Cross references . . . . . . . . . .
Text conventions . . . . . . . . . .
Contacting Motorola . . . . . . . . . .
24hour support . . . . . . . . . .
Questions and comments . . . . .
Errors . . . . . . . . . . . . . . .
Security advice. . . . . . . . . . . . .
Warnings, cautions, and notes . . . . .
Warnings. . . . . . . . . . . . . .
Cautions . . . . . . . . . . . . . .
Notes . . . . . . . . . . . . . . .
Safety . . . . . . . . . . . . . . . . .
General safety . . . . . . . . . . .
Electromagnetic energy . . . . . .
Caring for the environment . . . . . .
EU countries . . . . . . . . . . . .
Non-EU countries . . . . . . . . .
CMM labeling and disclosure table . .
Motorola document set . . . . . . . .
Ordering documents and CD-ROMs
Document banner definitions . . .
Data encryption . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 1: Introduction to the OMC-R
68P02901W19-S
Oct 2009
Contents
Overview to SunFire and Netra configuration . . . . . . .

Checking SunFire hardware requirements. . . . . . . . .
Checking Netra 20 hardware requirements . . . . . . . .
Checking Netra 440 hardware requirements . . . . . . .
Connecting peripherals . . . . . . . . . . . . . . . . . .
Connecting peripherals to a Netra 440 . . . . . . . . . .
Installing and configuring cards . . . . . . . . . . . . . .
Configuring hard drives . . . . . . . . . . . . . . . . . .
Disk configuration SunFire 4800/4900, Netra 20 and Netra
Connecting to the LAN . . . . . . . . . . . . . . . . . . . . .
Overview of connecting to the LAN . . . . . . . . . . . .
Configuring the OMC-R based LAN . . . . . . . . . . . .
Routine system administration procedures. . . . . . . . . . .
Introduction to routine system administration procedures .
Daily log book . . . . . . . . . . . . . . . . . . . . . . .
Daily procedures . . . . . . . . . . . . . . . . . . . . . . . .
INFORMIX database daily procedures . . . . . . . . . . .
UNIX file systems daily procedures . . . . . . . . . . . .
Miscellaneous daily procedures . . . . . . . . . . . . . .
Weekly procedures . . . . . . . . . . . . . . . . . . . . . . .
INFORMIX database weekly procedures . . . . . . . . . .
UNIX file systems weekly procedures . . . . . . . . . . .
Security-related weekly procedures . . . . . . . . . . . .
Monthly procedures . . . . . . . . . . . . . . . . . . . . . .
UNIX file systems monthly procedures. . . . . . . . . . .
Security-related monthly procedures . . . . . . . . . . .
Additional procedures . . . . . . . . . . . . . . . . . . . . .
Additional event driven procedures . . . . . . . . . . . .
Complete file system backup. . . . . . . . . . . . . . . .
NE load management maintenance . . . . . . . . . . . .
PM raw statistics maintenance. . . . . . . . . . . . . . .
OMC-R user accounts . . . . . . . . . . . . . . . . . . .
Hard copy listings (printouts) . . . . . . . . . . . . . . .
System core dumps . . . . . . . . . . . . . . . . . . . .
Hardware maintenance . . . . . . . . . . . . . . . . . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
440 .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-9
1-9
1-10
1-10
1-11
1-15
1-17
1-18
1-19
1-24
1-24
1-24
1-26
1-26
1-26
1-28
1-28
1-29
1-29
1-30
1-30
1-30
1-31
1-32
1-32
1-32
1-33
1-33
1-33
1-33
1-33
1-33
1-34
1-34
1-34
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-2
2-3
2-3
2-4
2-5
2-5
2-8
2-8
2-9
2-10
2-10
2-10
2-11
2-12
2-12
2-13
2-13
2-15
2-15
2-16
Chapter 2: System management

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of the Common Desktop Environment (CDE) . . . .
Overview of the CDE . . . . . . . . . . . . . . . . . . . .
Utilities available from the root CDE desktop . . . . . . .
Utilities common to the omcadmin and root CDE desktops
Accessing usertool . . . . . . . . . . . . . . . . . . . . .
Administering group accounts with usertool . . . . . . . . . .
Overview of group management functions in usertool . . .
Group Management parameters . . . . . . . . . . . . . .
Adding a group . . . . . . . . . . . . . . . . . . . . . .
Modifying group accounts . . . . . . . . . . . . . . . . .
Renaming group accounts . . . . . . . . . . . . . . . . .
Deleting group accounts . . . . . . . . . . . . . . . . . .
Administering user accounts with usertool. . . . . . . . . . .
Overview of user management functions in usertool . . .
Ensuring the correct GUI colors appear . . . . . . . . . .
User management parameters . . . . . . . . . . . . . . .
Adding a user . . . . . . . . . . . . . . . . . . . . . . .
Modifying a user account . . . . . . . . . . . . . . . . .
Renaming a user account . . . . . . . . . . . . . . . . .
ii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02901W19-S
Oct 2009
Deleting a user account . . . . . . . . . . . . . . .

CDE utilities available to an omcadmin login. . . . . . .
Displaying the omcadmin CDE desktop . . . . . . .
Database Applications menu . . . . . . . . . . . . .
CDE utilities available to either root or omcadmin login .
Displaying the root CDE desktop. . . . . . . . . . .
Overview of utilities common to root and omcadmin .
Style Manager . . . . . . . . . . . . . . . . . . . .
File Manager. . . . . . . . . . . . . . . . . . . . .
Archiving old OMC-R user files . . . . . . . . . . . . .
Checking home accounts for unmodified files . . . .
OMC software management . . . . . . . . . . . . . . .
Introduction to OMC software management . . . . .
Software loads . . . . . . . . . . . . . . . . . . . .
Installing new software . . . . . . . . . . . . . . .
Removing old software. . . . . . . . . . . . . . . .
Test objects . . . . . . . . . . . . . . . . . . . . .
Cleaning up OMC-R software loads . . . . . . . . . . .
Reasons for cleaning up OMC-R software loads . . .
Keeping software loads . . . . . . . . . . . . . . .
Using a tarred software load . . . . . . . . . . . . .
NE database maintenance . . . . . . . . . . . . . . . .
Login id for NE database maintenance. . . . . . . .
Archiving and removing a NE database . . . . . . .
Maintaining NE raw statistics . . . . . . . . . . . .
Removing NE fallback software load directories . . .
Manual parsing of statistics checklist . . . . . . . .
Printing current OMC-R processes . . . . . . . . . . . .
Overview of printing OMC-R processes . . . . . . .
Procedure to print OMC-R processes . . . . . . . .
Security overview . . . . . . . . . . . . . . . . . . . .
Overview of the OMC-R system security . . . . . . .
Services . . . . . . . . . . . . . . . . . . . . . . .
Enabling and disabling services . . . . . . . . . . .
Other security changes . . . . . . . . . . . . . . .
Controlling user activity on the system . . . . . . . . .
Login IDs for system control . . . . . . . . . . . . .
System security . . . . . . . . . . . . . . . . . . .
Controlling user passwords . . . . . . . . . . . . . . .
Overview of controlling user passwords . . . . . . .
User passwords . . . . . . . . . . . . . . . . . . .
Password conventions . . . . . . . . . . . . . . . .
Packet Switch passwords . . . . . . . . . . . . . .
Network file security . . . . . . . . . . . . . . . . . . .
Controlling access to network files. . . . . . . . . .
Network File System (NFS) . . . . . . . . . . . . .
Installing OMC-R Help . . . . . . . . . . . . . . . . . .
Capacity control . . . . . . . . . . . . . . . . . . . . .
Overview of capacity control . . . . . . . . . . . . .
Capacity control mechanism . . . . . . . . . . . . .
Feature Capacity Licensing and Audit . . . . . . . .
Licence violation alarms . . . . . . . . . . . . . . .
Updating RTF license limit. . . . . . . . . . . . . .
Restartable processes . . . . . . . . . . . . . . . . . .
Restartable and non-restartable processes. . . . . .
Restarting processes . . . . . . . . . . . . . . . . .
Messages in the OMC-R console and audit log . . . .
omctool utility . . . . . . . . . . . . . . . . . . . .
68P02901W19-S
Oct 2009
Contents
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-16
2-18
2-18
2-19
2-20
2-20
2-21
2-21
2-22
2-23
2-23
2-24
2-24
2-24
2-25
2-25
2-26
2-28
2-28
2-28
2-29
2-30
2-30
2-30
2-30
2-31
2-31
2-35
2-35
2-35
2-36
2-36
2-36
2-38
2-38
2-40
2-40
2-41
2-42
2-42
2-42
2-42
2-43
2-44
2-44
2-44
2-45
2-46
2-46
2-46
2-46
2-47
2-47
2-49
2-49
2-49
2-50
2-55
iii
Contents
Graceful shutdown on mains failure . . . . . . . . . . . . . .

Graceful shutdown . . . . . . . . . . . . . . . . . . . . .
Implementation of graceful shutdown . . . . . . . . . . .
Features of graceful shutdown . . . . . . . . . . . . . . .
UPS setup . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration and installation of a remote terminal . . . . . .
Introduction to the setup of a remote monitoring terminal.
Single OMC-R monitoring configuration . . . . . . . . . .
OMC-R night concentration centre configuration . . . . .
Night concentration overview . . . . . . . . . . . . . . .
Naming conventions for a night concentration centre . . .
Prerequisites for setup of a night concentration centre . .
Remote system processor setup . . . . . . . . . . . . . . . .
Introduction to setting up night concentration . . . . . . .
Updating host file entries . . . . . . . . . . . . . . . . .
Exporting file changes . . . . . . . . . . . . . . . . . . .
Creation of new account . . . . . . . . . . . . . . . . . .
Monitor alternative OMC-R from GUI server. . . . . . . . . .
Prerequisites for switching to an alternative OMC-R. . . .
Switching to an alternative OMC-R . . . . . . . . . . . .
Removing OMC-R night concentration centre configuration . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . .
Local GUI server rollback . . . . . . . . . . . . . . . . .
Deletion of OMC-R remote user accounts . . . . . . . . .
Remote system processor rollback . . . . . . . . . . . . .
Setting the locale on the OMC-R . . . . . . . . . . . . . . . .
General administration checklists . . . . . . . . . . . . . . .
Daily administration checklist . . . . . . . . . . . . . . .
Weekly administration checklist . . . . . . . . . . . . . .
Monthly administration checklist . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-57
2-57
2-57
2-57
2-58
2-59
2-59
2-59
2-60
2-61
2-61
2-61
2-63
2-63
2-63
2-64
2-64
2-65
2-65
2-66
2-67
2-67
2-67
2-67
2-68
2-69
2-74
2-74
2-79
2-80
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-2
3-3
3-3
3-3
3-4
3-6
3-6
3-7
3-7
3-7
3-7
3-8
3-8
3-8
3-10
3-10
3-11
3-11
3-12
3-14
3-17
3-18
3-19
3-19
3-19
Chapter 3: Ancillary Devices

Overview . . . . . . . . . . . . . . . . . . . . . . .
Configuring the serial port with Serial Port Manager
Overview of Serial Port Manager . . . . . . . .
Accessing Serial Port Manager . . . . . . . . .
Serial Port Manager parameters . . . . . . . . .
Adding a modem . . . . . . . . . . . . . . . . .
Setting an alternative baud rate . . . . . . . . .
Installing a modem. . . . . . . . . . . . . . . . . .
Introduction to modem installation . . . . . . .
Background information . . . . . . . . . . . . .
Data links . . . . . . . . . . . . . . . . . . . .
Rates. . . . . . . . . . . . . . . . . . . . . . .
Physical connection . . . . . . . . . . . . . . .
Initial modem setup . . . . . . . . . . . . . . .
Communicating with the modem . . . . . . . . .
Configuring tip. . . . . . . . . . . . . . . . . .
Controlling modem access . . . . . . . . . . . .
Modem setup and Initialization . . . . . . . . .
Configuring the Serial Port Modem . . . . . . .
Configuring the MultiModem MT5634ZBA Global
Enabling the login process . . . . . . . . . . . .
Remote connection and file transfers . . . . . .
Troubleshooting the modem . . . . . . . . . . . . .
Problem symptoms. . . . . . . . . . . . . . . .
All ports busy . . . . . . . . . . . . . . . . . .
iv
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02901W19-S
Oct 2009
Contents
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-21
3-22
3-22
3-22
3-23
3-23
3-23
3-23
3-24
3-24
3-24
3-25
3-25
3-25
3-26
3-26
3-27
3-27
3-27
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OMC-R log and error files . . . . . . . . . . . . . . . . . . . . . . . . .
OMC-R log files on the system processor . . . . . . . . . . . . . . .
OMC-R log files on the GUI server . . . . . . . . . . . . . . . . . . .
Problems with parsing statistics and maintenance of the PM database
Event and alarm logging . . . . . . . . . . . . . . . . . . . . . . . .
INFORMIX database log file . . . . . . . . . . . . . . . . . . . . . .
Interprocess communication (IPC) logging. . . . . . . . . . . . . . .
Environment variables for log files. . . . . . . . . . . . . . . . . . .
Other environment variables. . . . . . . . . . . . . . . . . . . . . .
Checking OMC-R log files . . . . . . . . . . . . . . . . . . . . . . .
Checking audit log files . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to checking audit logs . . . . . . . . . . . . . . . . . .
Checking audit log files in a single OMC-R environment . . . . . . . .
Checking audit log files in a multiple OMC-R environment. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-2
4-3
4-3
4-5
4-5
4-5
4-5
4-6
4-6
4-7
4-7
4-11
4-11
4-11
4-11
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5-2
5-3
5-3
5-5
5-6
5-9
5-9
5-9
5-12
5-12
5-13
5-14
5-14
5-14
5-14
5-15
5-16
5-16
No login prompt . . . . . . . . . . . . . . . . . . . . . . . . . .
When to modify the eeprom settings . . . . . . . . . . . . . . . .
Corruption from platform with remote system logging in . . . . .
Modem hangs up after answering a call and negotiation. . . . . .
Permission denied or link down . . . . . . . . . . . . . . . . . .
Modems do not disconnect properly . . . . . . . . . . . . . . . .
Nothing happens when trying to tip the modem . . . . . . . . . .
When dialing into the SPARC the modem never answers the phone
Login message is corrupt . . . . . . . . . . . . . . . . . . . . .
Cannot login, password fails . . . . . . . . . . . . . . . . . . . .
No utmpx entry . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a printer . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of adding printers to the OMC-R. . . . . . . . . . . . .
Assigning printer name and address on the network. . . . . . . .
Configuring a printer connected to a GUI processor . . . . . . . .
Configuring a network printer . . . . . . . . . . . . . . . . . . .
Checking the printer status . . . . . . . . . . . . . . . . . . . .
Printing a file . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printer configuration file . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 4: OMC-R Log Files
Chapter 5: OMC-R Cron Jobs

Overview . . . . . . . . . . . . . . . . . . . . . . . . .
System cron jobs . . . . . . . . . . . . . . . . . . . . .
cron jobs on the system processor . . . . . . . . . .
cron jobs on GUI processors . . . . . . . . . . . . .
Recommended cron jobs . . . . . . . . . . . . . . .
Scheduling cron jobs using the batch scheduler . . . . .
Overview of the batch scheduler . . . . . . . . . . .
Displaying cron jobs . . . . . . . . . . . . . . . . .
Adding a new cron job . . . . . . . . . . . . . . . .
Modifying an existing cron job . . . . . . . . . . . .
Removing a cron job . . . . . . . . . . . . . . . . .
Scheduling cron jobs from the command line . . . . . .
Overview of scheduling cron jobs from the command
Viewing crontab files. . . . . . . . . . . . . . . . .
Verifying cron jobs . . . . . . . . . . . . . . . . . .
Adding cron jobs . . . . . . . . . . . . . . . . . . .
Removing cron jobs . . . . . . . . . . . . . . . . .
cron maintenance procedure. . . . . . . . . . . . .
68P02901W19-S
Oct 2009
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
line
. .
. .
. .
. .
. .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Contents
Printing crontab files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Checking cron jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checklist for cron jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-17
5-18
5-18
Chapter 6: OMC-R Environment variables

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Customizing the OMC-R user environment. . . . . . . . . . . .
Customizing a user environment . . . . . . . . . . . . . . .
.cshrc.private file . . . . . . . . . . . . . . . . . . . . . .
.Xdefaults.private file . . . . . . . . . . . . . . . . . . . .
User configurable environment variables . . . . . . . . . . . .
Introduction to the user configurable environment variables
System processes and PM database configurable variables .
MIB processes used by environment variables . . . . . . . .
GUI processes environment variables . . . . . . . . . . . .
RLOGIN variables . . . . . . . . . . . . . . . . . . . . . .
FM_audit variables. . . . . . . . . . . . . . . . . . . . . .
CSMMAIN variables . . . . . . . . . . . . . . . . . . . . .
ResyncCtrl variables . . . . . . . . . . . . . . . . . . . . .
OMC-R Startup/Shutdown Timers . . . . . . . . . . . . . .
Changing an environment variable. . . . . . . . . . . . . . . .
Methods for changing an environment variable . . . . . . .
Setting the status of the Consolidated Alarms . . . . . . . . . .
Introduction to setting the status of the Consolidated Alarms
Setting status of the consolidated alarms . . . . . . . . . .
Disabling the status of consolidated alarms . . . . . . . . .
Non user configurable environment variables . . . . . . . . . .
Introduction to non user configurable environment variables
Setting the time for the OMC-R and NEs. . . . . . . . . . . . .
Reason for setting the system time . . . . . . . . . . . . .
Overview of setting the time at the OMC-R and NEs . . . . .
Resetting the time . . . . . . . . . . . . . . . . . . . . . .
Configuring system time to GMT. . . . . . . . . . . . . . .
Configuring system time to local time . . . . . . . . . . . .
Default time zones in OMC-R . . . . . . . . . . . . . . . .
Non default time zones in OMC-R without daylight saving . .
Non default time zones in OMC-R with daylight saving . . .
Setting the time zone . . . . . . . . . . . . . . . . . . . .
Synchronizing the time at the OMC-R . . . . . . . . . . . .
Synchronizing the time at the NEs . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-2
6-3
6-3
6-3
6-3
6-5
6-5
6-5
6-10
6-13
6-21
6-22
6-23
6-24
6-25
6-26
6-26
6-29
6-29
6-29
6-30
6-31
6-31
6-36
6-36
6-36
6-36
6-37
6-37
6-37
6-38
6-39
6-40
6-41
6-42
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7-2
7-3
7-3
7-3
7-4
7-5
7-5
7-6
7-7
7-7
7-7
7-9
7-9
7-9
Chapter 7: System startup and shutdown

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operating modes (run levels) . . . . . . . . . . . . . . . . . .
Operating modes. . . . . . . . . . . . . . . . . . . . . . .
Run levels . . . . . . . . . . . . . . . . . . . . . . . . . .
Controlling run levels . . . . . . . . . . . . . . . . . . . .
System processor startup and shutdown sequences . . . . . . .
Startup and shutdown scripts . . . . . . . . . . . . . . . .
Directories associated with startup and shutdown . . . . . .
Sequential ordering of the startup and shutdown processes .
Identifying a run level . . . . . . . . . . . . . . . . . . . .
Changing a run level . . . . . . . . . . . . . . . . . . . . .
Switching to single user mode . . . . . . . . . . . . . . . . . .
Switching the system processor to single user mode. . . . .
Switching a GUI processor to single user mode . . . . . . .
vi
68P02901W19-S
Oct 2009
Contents
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7-10
7-10
7-11
7-11
7-12
7-12
7-12
7-12
7-13
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of database management . . . . . . . . . . . . . .
PM database maintenance . . . . . . . . . . . . . . . . .
Database utilities . . . . . . . . . . . . . . . . . . . . . . .
Overview of the database utilities . . . . . . . . . . . . .
onmonitor utility . . . . . . . . . . . . . . . . . . . . . .
omc_db_maint utility . . . . . . . . . . . . . . . . . . . .
pm_purge_data utility . . . . . . . . . . . . . . . . . . .
pm_daily_unload utility . . . . . . . . . . . . . . . . . .
pm_purge_check utility . . . . . . . . . . . . . . . . . .
db_disconnect utility . . . . . . . . . . . . . . . . . . . .
db_pm_maint utility . . . . . . . . . . . . . . . . . . . .
omc_db_ckspace utility. . . . . . . . . . . . . . . . . . .
pm_manual_parse utility . . . . . . . . . . . . . . . . . .
INFORMIX directory structure. . . . . . . . . . . . . . . . .
Overview of the INFORMIX directory structure . . . . . .
INFORMIX directory structure on the system processor . .
INFORMIX directory structure on the GUI processor . . .
Shutdown and startup of the PM and CM databases . . . . . .
Database shutdown and startup . . . . . . . . . . . . . .
Shutting down the PM database through onmonitor . . . .
Shutting down the CM database through onmonitor . . . .
Starting up the PM database through onmonitor . . . . .
Starting up the CM database through onmonitor . . . . .
Starting up databases automatically . . . . . . . . . . . .
Shutting down automatically. . . . . . . . . . . . . . . .
Administering the PM database using the omc_db_maint utility
Using omc_db_maint . . . . . . . . . . . . . . . . . . . .
Running omc_db_maint as a cron job . . . . . . . . . . .
Running omc_db_maint manually . . . . . . . . . . . . .
Automatic Checking Of Maintenance . . . . . . . . . . .
Setting the onconfig parameters . . . . . . . . . . . . . . . .
onconfig file overview . . . . . . . . . . . . . . . . . . .
Checking onconfig parameters. . . . . . . . . . . . . . .
Changing onconfig parameters . . . . . . . . . . . . . .
Dropping and Recreating the PM database . . . . . . . . . .
Additional database maintenance procedures . . . . . . . . .
Overview of additional database maintenance procedures .
Checking for excess of 32000 statistics . . . . . . . . . .
Checking stat details. . . . . . . . . . . . . . . . . . . .
Backing up subscription data . . . . . . . . . . . . . . .
Checking the PM database . . . . . . . . . . . . . . . . . . .
Check the PM database . . . . . . . . . . . . . . . . . .
PM sqlhosts file . . . . . . . . . . . . . . . . . . . . . .
onstat output for PM database . . . . . . . . . . . . . . .
onstat -d output for PM database . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8-2
8-3
8-3
8-4
8-4
8-5
8-6
8-7
8-8
8-8
8-8
8-9
8-10
8-11
8-13
8-13
8-14
8-15
8-16
8-16
8-16
8-18
8-19
8-21
8-22
8-22
8-23
8-23
8-23
8-24
8-25
8-26
8-26
8-26
8-27
8-30
8-32
8-32
8-32
8-32
8-32
8-34
8-34
8-35
8-35
8-37
Switching to PROM mode . . . . . . . . . . .

The halt command . . . . . . . . . . . . . . .
Bringing the system up from PROM mode . . .
The reboot command . . . . . . . . . . . . .
Manual startup and shutdown of OMC-R software .
Overview of manual startup and shutdown. . .
Starting up OMC-R software . . . . . . . . . .
Shutting down OMC-R software . . . . . . . .
Checking system processor processes . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 8: Database Management
68P02901W19-S
Oct 2009
vii
Contents
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8-39
8-39
8-40
8-41
8-42
8-43
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
X.25 application management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of the X.25 software . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring X.25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring OMC-R processes for X.25 . . . . . . . . . . . . . . . . . . . . . . . .
Rules for the x25_config file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OMC X.25 application design . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Basic X.25 commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting and stopping X.25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacing the HSI card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating X.25 link configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Further details of X.25 commands . . . . . . . . . . . . . . . . . . . . . . . . . . .
X.25 directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting and stopping X.25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stopping OMC-R processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of the x25tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting up the x25tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting X.25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stopping X.25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating X.25 link configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring X.25 parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring LAPB parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacing the HSI card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacing the HSI card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking X.25 connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
X.25 connectivity checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
X.25 recovery from HSI failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Issue A: Sun IB module/IO board hardware failure. . . . . . . . . . . . . . . . . . .
Issue B: HSI card hardware failure . . . . . . . . . . . . . . . . . . . . . . . . . .
Issue C: OMC-R configuration to allow X25 operate using the remaining hardware . .
Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Issue A: Recovery from a Sun IB module/IO board hardware failure . . . . . . . . . .
Issue B: Recovery from HSI card hardware failure. . . . . . . . . . . . . . . . . . .
Issue C: Recovery of OMC-R configuration to allow X25 operate using the remaining
hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9-2
9-3
9-3
9-3
9-3
9-5
9-5
9-7
9-7
9-7
9-7
9-7
9-8
9-9
9-9
9-9
9-9
9-11
9-12
9-13
9-13
9-15
9-17
9-17
9-18
9-18
9-19
9-19
9-19
9-20
9-21
9-21
9-22
. . .
9-23
Checking the CM database. . . . . . . . .

Check the CM database . . . . . . . .
CM sqlhosts file . . . . . . . . . . . .
onstat output for CM database . . . . .
onstat -d output for CM database . . .
Dropping and Recreating the CM database
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 9: X.25 management
Chapter 10: OMC Utilities

Operation and maintenance utilities . .
Overview of utilities . . . . . . . .
Operation and maintenance utilities
Alarm/Event Window. . . . . . . .
Installation. . . . . . . . . . . . .
Rollback . . . . . . . . . . . . . .
Cleanup . . . . . . . . . . . . . .
Utility execution . . . . . . . . . .
Finder . . . . . . . . . . . . . . .
net_reports. . . . . . . . . . . . .
dri_status . . . . . . . . . . . . .
viii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
10-2
10-2
10-2
10-3
10-4
10-6
10-7
10-7
10-8
10-9
10-13
68P02901W19-S
Oct 2009
rtf_status. . . . .
site_outage. . . .
add_nei . . . . .
del_nei . . . . . .
nei_sync . . . . .
proxy_sync . . . .
reparent_site. . .
ne_counter . . . .
Utility execution . . .
Overview. . . . .
Command line . .
cron and at. . . .
CDE menu . . . .
cleanMib . . . . . . .
Introduction . . .
Running cleanMib
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Contents
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
10-15
10-16
10-18
10-19
10-20
10-21
10-21
10-23
10-25
10-25
10-25
10-26
10-26
10-27
10-27
10-27
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
11-2
11-3
11-3
11-3
11-3
11-4
11-4
11-5
11-5
11-6
11-6
11-7
11-8
11-8
11-8
11-8
11-9
11-10
11-10
11-11
11-11
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
12-2
12-3
12-4
12-4
12-4
12-5
12-5
12-6
12-6
12-7
12-9
12-10
12-10
12-11
12-12
Chapter 11: Network Information Services (NIS)

Overview . . . . . . . . . . . . . . . . . .
NIS normal operation . . . . . . . . . . .
Map . . . . . . . . . . . . . . . . . .
Domain . . . . . . . . . . . . . . . .
Servers and clients. . . . . . . . . . .
Masters and slaves. . . . . . . . . . .
Propagation . . . . . . . . . . . . . .
NIS files and utilities. . . . . . . . . . . .
Daemons . . . . . . . . . . . . . . . .
Utilities . . . . . . . . . . . . . . . .
Auxiliary utilities . . . . . . . . . . . .
Affected files . . . . . . . . . . . . . .
Changing user/group/host information . . .
Recommended method. . . . . . . . .
Changing host name . . . . . . . . . .
Adding a new user to the NIS domain .
Adding a new group to the NIS domain
nsswitch.conf . . . . . . . . . . . . .
NIS server checks . . . . . . . . . . .
Updating the NIS maps manually . . .
NIS troubleshooting commands . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 12: Backup Server Installation and Configuration

Introduction to StorEdge Enterprise Backup. . . . . . .
StorEdge Enterprise features . . . . . . . . . . . .
Software Installation . . . . . . . . . . . . . . . . . . .
Invoking the StorEdge Enterprise Backup utilities . .
Software Licenses . . . . . . . . . . . . . . . . . .
Backup Server Configuration . . . . . . . . . . . .
Configuring Sun StorEdge Enterprise Backup Server
Configuring Bootstrap Notifications . . . . . . . . .
Configuring Bootstrap Notification through E-mail .
Configuring Bootstrap Notification to local file . . .
Setting up the backup server software . . . . . . .
Completing backup server setup . . . . . . . . . . .
Enabling or Disabling a Group Backup . . . . . . .
Deleting a Group Backup client . . . . . . . . . . .
Manually starting a Group Backup . . . . . . . . . .
68P02901W19-S
Oct 2009
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
Licenses
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
ix
Contents
Manual backup of Informix databases . . . . . . . . . . . . . . . . . . .

Backing up the GUI Server File System . . . . . . . . . . . . . . . . . .
Disaster Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disaster Recovery GSM OMC-R server. . . . . . . . . . . . . . . . . . .
Recover the Necessary Filesystems . . . . . . . . . . . . . . . . . . . .
Recovering Informix databases . . . . . . . . . . . . . . . . . . . . . .
Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Database recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Additional Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
StorEdge Enterprise Backup Server GUI . . . . . . . . . . . . . . . . .
Licensing the Sun StorEdge EBS Server using the Administration Window
Tape Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation log files . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sample output from backup client creation . . . . . . . . . . . . . . . .
Backup and Restore using the Standard Solaris suite of utilities . . . . . .
Backing up the PM and CM Databases. . . . . . . . . . . . . . . . . . .
Restoring Single Platform Processor file systems . . . . . . . . . . . . .
Restoring databases on the Single Platform Processor. . . . . . . . . . .
Restoring GUI Server file systems using ufsrestore utility . . . . . . . . .
Selective File restore using restore_splat . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
12-13
12-16
12-20
12-20
12-27
12-31
12-35
12-35
12-37
12-39
12-39
12-40
12-41
12-43
12-43
12-43
12-48
12-55
12-63
12-77
12-86
12-97
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
13-2
13-3
13-3
13-3
13-3
13-5
13-6
13-6
13-6
13-6
13-6
13-6
13-7
13-8
13-8
13-8
13-8
13-9
13-9
13-10
13-10
13-11
13-12
13-14
13-14
13-17
13-19
13-21
13-21
13-21
13-21
13-22
13-23
Chapter 13: Troubleshooting

Overview . . . . . . . . . . . . . . . . . . . . . . . . . .
Assessing a problem . . . . . . . . . . . . . . . . . . . .
Overview of troubleshooting . . . . . . . . . . . . . .
Contacting Motorola . . . . . . . . . . . . . . . . . .
Preliminary checklist. . . . . . . . . . . . . . . . . .
General problem descriptions . . . . . . . . . . . . .
Core file generation . . . . . . . . . . . . . . . . . . . .
Overview of generating core files . . . . . . . . . . .
Application core dumps . . . . . . . . . . . . . . . .
Generating a core of an OMC-R process . . . . . . . .
Operating system core dumps . . . . . . . . . . . . .
core_presence utility . . . . . . . . . . . . . . . . . .
Checking core dumps . . . . . . . . . . . . . . . . .
OMC-R system information . . . . . . . . . . . . . . . .
Obtaining system information . . . . . . . . . . . . .
OMC-R log files . . . . . . . . . . . . . . . . . . . .
System uptime . . . . . . . . . . . . . . . . . . . . .
Machine architecture . . . . . . . . . . . . . . . . .
Current processes . . . . . . . . . . . . . . . . . . .
State of the file systems . . . . . . . . . . . . . . . .
Integrity of X.25 communications . . . . . . . . . . .
Network status. . . . . . . . . . . . . . . . . . . . .
System resources . . . . . . . . . . . . . . . . . . .
Swap space . . . . . . . . . . . . . . . . . . . . . .
PM database status . . . . . . . . . . . . . . . . . .
CM database status . . . . . . . . . . . . . . . . . .
systat script . . . . . . . . . . . . . . . . . . . . . .
Full file systems . . . . . . . . . . . . . . . . . . . . . .
Full file systems . . . . . . . . . . . . . . . . . . . .
Identifying full file systems . . . . . . . . . . . . . .
Freeing up further disk space on the system processor
Removing files or directories. . . . . . . . . . . . . .
Checking disk usage . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02901W19-S
Oct 2009
File access problems . . . . . . . . . . . . . . . . . . . . . . . . . .

Stale NFS file handling . . . . . . . . . . . . . . . . . . . . . .
GUI processor failure to access event log files . . . . . . . . . . .
OMC-R software process errors . . . . . . . . . . . . . . . . . . . .
Analyzing OMC-R process errors. . . . . . . . . . . . . . . . . .
List of system processes . . . . . . . . . . . . . . . . . . . . . .
GUI process . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resetting boot devices . . . . . . . . . . . . . . . . . . . . . . . . .
Bootup problems . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure to reset a boot device . . . . . . . . . . . . . . . . . .
Common Desktop Environment problems . . . . . . . . . . . . . . .
Overview of CDE . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing CDE . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring CDE . . . . . . . . . . . . . . . . . . . . . . . . . .
Normal operation of CDE . . . . . . . . . . . . . . . . . . . . .
Errors in user profiles . . . . . . . . . . . . . . . . . . . . . . .
Errors accessing a user's home directory . . . . . . . . . . . . .
Enabling/disabling the Print Manager . . . . . . . . . . . . . . .
Other CDE problems . . . . . . . . . . . . . . . . . . . . . . . .
CDE login failure. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of CDE login failure . . . . . . . . . . . . . . . . . . .
Procedure to recover from CDE login failure. . . . . . . . . . . .
Troubleshooting the LAN . . . . . . . . . . . . . . . . . . . . . . .
Long response times to commands. . . . . . . . . . . . . . . . .
Checking the performance of the LAN . . . . . . . . . . . . . . .
Checking if packets can be sent and received . . . . . . . . . . .
X.25 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of X.25 failure . . . . . . . . . . . . . . . . . . . . . .
Starting x25tool . . . . . . . . . . . . . . . . . . . . . . . . . .
X.25 trace on the system processor . . . . . . . . . . . . . . . .
Displaying x25stat . . . . . . . . . . . . . . . . . . . . . . . . .
Moving a machine with a forced link speed . . . . . . . . . . . . . .
Logical Vol Mgr troubleshooting . . . . . . . . . . . . . . . . . . . .
Logical Vol Mgr problems . . . . . . . . . . . . . . . . . . . . .
Replacing hard disk on system processor Sunfire/Netra 440/Netra 20 .
Recovering from other Logical Vol Mgr problems . . . . . . . . .
Checking disk mirroring . . . . . . . . . . . . . . . . . . . . . . . .
Disk mirroring checklist . . . . . . . . . . . . . . . . . . . . . .
metastat output . . . . . . . . . . . . . . . . . . . . . . . . . .
Device busy error . . . . . . . . . . . . . . . . . . . . . . . . . . .
Device busy error . . . . . . . . . . . . . . . . . . . . . . . . .
Unmounting a device . . . . . . . . . . . . . . . . . . . . . . .
Ejecting DVD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . .
DVD-ROM drive not ejecting . . . . . . . . . . . . . . . . . . . .
Procedure to free up DVD-ROM drive . . . . . . . . . . . . . . .
StorEdge Enterprise Backup problems. . . . . . . . . . . . . . . . .
StorEdge Enterprise Backup tape error . . . . . . . . . . . . . .
Database failure . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Database failure . . . . . . . . . . . . . . . . . . . . . . . . . .
Problems adding/updating statistics in PM database. . . . . . . .
Onperf utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of Onperf . . . . . . . . . . . . . . . . . . . . . . . .
Starting onperf from the CDE front panel . . . . . . . . . . . . .
Starting onperf from the command line . . . . . . . . . . . . . .
Loading a history file. . . . . . . . . . . . . . . . . . . . . . . .
Saving Graph Tool configurations . . . . . . . . . . . . . . . . .
Selecting metrics . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing metrics . . . . . . . . . . . . . . . . . . . . . . . . . .
68P02901W19-S
Oct 2009
Contents
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
13-24
13-24
13-24
13-25
13-25
13-26
13-27
13-28
13-28
13-28
13-33
13-33
13-33
13-33
13-34
13-34
13-34
13-34
13-35
13-36
13-36
13-36
13-37
13-37
13-37
13-38
13-39
13-39
13-39
13-39
13-40
13-41
13-42
13-42
13-43
13-46
13-47
13-47
13-47
13-49
13-49
13-49
13-50
13-50
13-50
13-51
13-51
13-52
13-52
13-52
13-53
13-53
13-53
13-54
13-54
13-57
13-58
13-59
xi
Contents
Monitoring tools . . . . . . . . . . . . . . . . . . . . . . . . .
Activity tools . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking and recovering database tables . . . . . . . . . . . . . .
Monitoring database space usage and fragmentation . . . . . .
Reading the database schema . . . . . . . . . . . . . . . . . .
Defragmenting tables (MIB database) . . . . . . . . . . . . . .
Emptying and defragmenting one or more PM statistics tables .
Adding extra logical logs to the PM database server . . . . . . .
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of alarms . . . . . . . . . . . . . . . . . . . . . . .
Disk space usage on the system processor . . . . . . . . . . . .
CPU and memory usage alarms . . . . . . . . . . . . . . . . .
Database alarms . . . . . . . . . . . . . . . . . . . . . . . . .
X.25 alarms . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hardware failure alarms . . . . . . . . . . . . . . . . . . . . .
OMC-R alarms . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting FM audit and disk usage limits . . . . . . . . . . . . . . .
Overview of setting FM audit and disk usage limits . . . . . . .
FM_audit.CNFG parameters . . . . . . . . . . . . . . . . . . .
Using neighbor statistics. . . . . . . . . . . . . . . . . . . . . . .
Neighbor statistics . . . . . . . . . . . . . . . . . . . . . . . .
Limitations on use of neighbor statistics . . . . . . . . . . . . .
Cyclic Neighbor Statistics feature (PMCyclic) . . . . . . . . . .
Neighbor statistics alarm . . . . . . . . . . . . . . . . . . . .
Raising the maximum limit of neighbor statistics . . . . . . . .
Using dbaccess . . . . . . . . . . . . . . . . . . . . . . . . .
Power failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of recovery from power failure . . . . . . . . . . . .
Power failure on all machines . . . . . . . . . . . . . . . . . .
Power failure on the system processor . . . . . . . . . . . . . .
Power failure on a GUI processor . . . . . . . . . . . . . . . .
Checking the system processor hardware . . . . . . . . . . . . . .
System processor hardware LEDs . . . . . . . . . . . . . . . .
Displaying system processor status . . . . . . . . . . . . . . .
Configuring a Timeserver . . . . . . . . . . . . . . . . . . . . . .
Support for IP Multipathing in Solaris10/GSR9 on Sunfire platforms
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
13-64
13-66
13-70
13-70
13-73
13-73
13-74
13-76
13-78
13-78
13-79
13-80
13-83
13-85
13-86
13-86
13-88
13-88
13-88
13-91
13-91
13-91
13-91
13-93
13-94
13-96
13-97
13-97
13-97
13-98
13-98
13-99
13-99
13-99
13-102
13-103
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
14-2
14-3
14-3
14-5
14-6
14-7
14-8
14-10
14-10
14-12
14-14
14-15
14-16
14-17
14-18
14-20
14-20
14-21
Chapter 14: Checklists

Overview . . . . . . . . . . . . . . . . . . .
General administration checklists . . . . . .
Daily administration checklist . . . . . .
Weekly administration checklist . . . . .
Monthly administration checklist . . . .
Checking cron jobs. . . . . . . . . . . . . .
Checking OMC-R log files . . . . . . . . . .
Checking databases . . . . . . . . . . . . .
Checklist for PM database . . . . . . . .
Checklist for CM database . . . . . . . .
Checking X.25 connectivity . . . . . . . . .
Checking core dumps . . . . . . . . . . . .
Checking disk usage . . . . . . . . . . . . .
Checking disk mirroring . . . . . . . . . . .
Checking for successful parsing of statistics .
Recording details . . . . . . . . . . . . . .
Setting up a night concentration centre .
Client and server partition details . . . .
xii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02901W19-S
Oct 2009
List
of
Figures
List of Figures
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
1-1: Typical hardware architecture of OMC-R SunFire/Netra system. . . .

1-2: StorEdge 3310 Disk Array . . . . . . . . . . . . . . . . . . . . . . .
1-3: D240 Media Tray . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-4: Connecting peripherals on a SunFire 4800/4900 . . . . . . . . . . .
1-5: Connecting peripherals on a Netra 20 . . . . . . . . . . . . . . . . .
1-6: StorEdge 3310 Array . . . . . . . . . . . . . . . . . . . . . . . . .
1-7: Connecting Peripherals on a Netra 440 . . . . . . . . . . . . . . . .
1-8: Netra 440 connected to StorEdge 3310 Array . . . . . . . . . . . . .
1-9: Netra 20/440 internal disk slots . . . . . . . . . . . . . . . . . . . .
1-10: LAN connections . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1: Root user desktop . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-2: OMC admin user desktop . . . . . . . . . . . . . . . . . . . . . . .
2-3: Root user desktop with OMC Admin menu displayed (partial view) . .
2-4: Usertool main window . . . . . . . . . . . . . . . . . . . . . . . . .
2-5: Group administration utility . . . . . . . . . . . . . . . . . . . . . .
2-6: User administration utility . . . . . . . . . . . . . . . . . . . . . . .
2-7: GUI client graphical CDE login screen. . . . . . . . . . . . . . . . .
2-8: GUI server graphical CDE login screen . . . . . . . . . . . . . . . .
2-9: GUI client graphical CDE login screen . . . . . . . . . . . . . . . .
2-10: GUI server graphical CDE login screen . . . . . . . . . . . . . . .
2-11: File Manager, main window (Home) . . . . . . . . . . . . . . . . .
2-12: Software security through Remote Execution and NFS. . . . . . . .
2-13: Single monitoring station configuration . . . . . . . . . . . . . . .
2-14: Night concentration centre configuration . . . . . . . . . . . . . .
3-1: Data links between two platforms . . . . . . . . . . . . . . . . . . .
4-1: OMC-R Log files on the system processor . . . . . . . . . . . . . . .
4-2: OMC-R log files on the GUI server . . . . . . . . . . . . . . . . . . .
5-1: Batch scheduler main window . . . . . . . . . . . . . . . . . . . . .
5-2: Batch scheduler main window: selected cron job . . . . . . . . . . .
5-3: Notify message box for modifying a cron job . . . . . . . . . . . . .
7-1: Startup and shut down directory structures on the system processor .
7-2: Sequence of startup and shutdown processes on the system processor
8-1: INFORMIX directory structure on the system processor. . . . . . . .
8-2: INFORMIX directory structure on a GUI processor . . . . . . . . . .
8-3: The onmonitor Status menu indicating Online state . . . . . . . . . .
8-4: Mode menu indicating Online state . . . . . . . . . . . . . . . . . .
8-5: The onmonitor Status menu indicating Offline state . . . . . . . . . .
8-6: Mode menu indicating Offline state . . . . . . . . . . . . . . . . . .
8-7: Mode menu indicating offline state . . . . . . . . . . . . . . . . . .
8-8: The onmonitor Status menu indicating online state . . . . . . . . . .
9-1: Centralized use of X.25 . . . . . . . . . . . . . . . . . . . . . . . .
9-2: x25_config configuration file details. . . . . . . . . . . . . . . . . .
9-3: x25tool 9.2 window . . . . . . . . . . . . . . . . . . . . . . . . . .
9-4: X25 Message window: process started . . . . . . . . . . . . . . . .
9-5: X25 Message window: process stopped . . . . . . . . . . . . . . . .
68P02901W19-S
Oct 2009
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-4
1-11
1-12
1-12
1-13
1-14
1-15
1-16
1-18
1-25
2-3
2-3
2-4
2-6
2-9
2-14
2-18
2-19
2-20
2-21
2-22
2-44
2-59
2-60
3-7
4-4
4-5
5-10
5-11
5-13
7-6
7-7
8-14
8-15
8-18
8-18
8-20
8-20
8-21
8-21
9-3
9-4
9-10
9-11
9-12
xiii
List of Figures
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
xiv
9-6: Link editor window . . . . . . . . . .

9-7: LAPB and WAN parameters window . .
12-1: Recover window . . . . . . . . . . .
12-2: File selection window for recovery . .
12-3: Recover status . . . . . . . . . . . .
13-1: Displaying the OnPerf utility window .
13-2: Graph menu . . . . . . . . . . . . .
13-3: Select file dialog box . . . . . . . . .
13-4: Configure menu . . . . . . . . . . .
13-5: Select Metrics . . . . . . . . . . . .
13-6: View menu . . . . . . . . . . . . . .
13-7: Line plot graph . . . . . . . . . . . .
13-8: Horizontal bar graph . . . . . . . . .
13-9: Vertical line graph . . . . . . . . . .
13-10: Pie chart . . . . . . . . . . . . . .
13-11: Status tool . . . . . . . . . . . . .
13-12: Query Tree . . . . . . . . . . . . .
13-13: Disk Activity Tool . . . . . . . . . .
13-14: Disk Capacity Tool . . . . . . . . .
13-15: Session Activity Tool . . . . . . . .
13-16: Virtual Processor Activity Tool . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9-14
9-16
12-35
12-36
12-37
13-54
13-55
13-56
13-57
13-58
13-59
13-60
13-61
13-62
13-63
13-64
13-65
13-66
13-67
13-68
13-69
68P02901W19-S
Oct 2009
List
of
Tables
List of Tables
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
1-1: OMC-R specifications (maximum values) . . . . . . . . . . . . . . . . .

1-2: GUI sessions per GUI server platform. . . . . . . . . . . . . . . . . . .
1-3: Software requirements (Single Platform Processor) . . . . . . . . . . .
1-4: SunFire 4800/4900 hardware requirements . . . . . . . . . . . . . . .
1-5: Netra 20 hardware requirements . . . . . . . . . . . . . . . . . . . . .
1-6: Netra 440 hardware requirements . . . . . . . . . . . . . . . . . . . .
1-7: Location of cards for a SunFire . . . . . . . . . . . . . . . . . . . . . .
1-8: Location of cards for a Netra 20 . . . . . . . . . . . . . . . . . . . . .
1-9: Location of cards for a Netra 440 . . . . . . . . . . . . . . . . . . . . .
1-10: Internal configuration of hard drives in the Netra 20/440 . . . . . . . .
1-11: Disk partitioning for SunFire 4800/4900 and Netra 20 servers . . . . .
1-12: Disk partitioning for Netra 440 servers . . . . . . . . . . . . . . . . .
1-13: OMC-R Single Platform Disk Partition Layout . . . . . . . . . . . . . .
2-1: Action and parameters . . . . . . . . . . . . . . . . . . . . . . . . . .
2-2: Manual parsing of statistics checklist . . . . . . . . . . . . . . . . . . .
2-3: Hostname and IP addresses for different processors . . . . . . . . . . .
2-4: User name and ID for remote system . . . . . . . . . . . . . . . . . . .
2-5: Procedures to remove OMC-R night concentration configuration . . . . .
3-1: Modem initialization commands . . . . . . . . . . . . . . . . . . . . .
3-2: Syntax of the AT command . . . . . . . . . . . . . . . . . . . . . . . .
3-3: AT commands and result codes for country-specific modem configuration
3-4: MultiModem MT5634ZBA initialization AT commands . . . . . . . . . .
3-5: Modem baud rate settings . . . . . . . . . . . . . . . . . . . . . . . .
4-1: Audit apply result codes . . . . . . . . . . . . . . . . . . . . . . . . .
6-1: Nonuser configurable variables in the Common.csh file . . . . . . . .
6-2: Nonuser configurable variables in the mmiProcConfig.csh file . . . .
9-1: Files and utilities for X.25 configuration and maintenance . . . . . . . .
10-1: List of OMC utilities . . . . . . . . . . . . . . . . . . . . . . . . . . .
10-2: OMC utilities: recommended execution mechanisms . . . . . . . . . .
12-1: Log files produced by backup server. . . . . . . . . . . . . . . . . . .
12-2: Log files produced by client machines . . . . . . . . . . . . . . . . . .
12-3: Order of backing up file systems. . . . . . . . . . . . . . . . . . . . .
12-4: Tape Management from the command line . . . . . . . . . . . . . . .
13-1: Output from ps -elf command . . . . . . . . . . . . . . . . . . . . . .
13-2: Disk mirroring checklist . . . . . . . . . . . . . . . . . . . . . . . . .
14-1: Daily administration checklist . . . . . . . . . . . . . . . . . . . . . .
14-2: Weekly administration checklist . . . . . . . . . . . . . . . . . . . . .
14-3: Monthly administration checklist . . . . . . . . . . . . . . . . . . . .
14-4: Cron job checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14-5: OMC-R log files checklist . . . . . . . . . . . . . . . . . . . . . . . .
14-6: PM database checklist . . . . . . . . . . . . . . . . . . . . . . . . . .
14-7: CM database checklist . . . . . . . . . . . . . . . . . . . . . . . . . .
14-8: X.25 connectivity checklist . . . . . . . . . . . . . . . . . . . . . . .
14-9: Core dumps checklist . . . . . . . . . . . . . . . . . . . . . . . . . .
14-10: Disk usage checklist . . . . . . . . . . . . . . . . . . . . . . . . . .
68P02901W19-S
Oct 2009
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-5
1-6
1-8
1-9
1-10
1-10
1-17
1-17
1-18
1-18
1-19
1-20
1-22
2-9
2-32
2-62
2-62
2-67
3-12
3-12
3-14
3-16
3-17
4-11
6-31
6-33
9-8
10-3
10-25
12-13
12-13
12-19
12-41
13-9
13-47
14-3
14-5
14-6
14-7
14-8
14-10
14-12
14-14
14-15
14-16
xv
List of Tables
Table
Table
Table
Table
Table
Table
xvi
14-11:
14-12:
14-13:
14-14:
14-15:
14-16:
Disk mirroring checklist . . . . . . . . . . . . . . .

Manual parsing of statistics checklist . . . . . . . .
Hostname and IP addresses for different processors .
User name and ID for remote system. . . . . . . . .
Client and server details . . . . . . . . . . . . . . .
Filesystem, Log and JumpStart details . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
14-17
14-18
14-20
14-20
14-21
14-21
68P02901W19-S
Oct 2009
About
This
Manual
Operating Information: OMC-R System

Administration
What is covered in this manual?

This manual provides the OMC-R system administrator with the technical information and
procedures to administer an OMC-R on a daily basis. Throughout this manual, the term OMC
refers to OMC-R (Operation and Maintenance Centre-Radio).
Some of the screen illustrations in this manual are shown with NT Windows characteristics
instead of UNIX window characteristics. However, functionality is not affected, and all other
details in the screen illustrations are correct.
This manual describes procedures for managing the system, the users, the database, X.25, NIS
and security, and for performing troubleshooting. The manual is organized as follows:
Introduction to the OMC-R system.
System management, including the Common Desktop Environment (CDE).
Ancillary devices.
OMC-R log files.
OMC-R cron jobs.
Environment variables.
System startup and shutdown.
Database management.
X.25 management.
Network Information Services.
File system backup and restore.
Troubleshooting.
Checklists.
68P02901W19-S
Oct 2009
Revision history
Revision history
The following sections show the revision status of this document.
Version information
The following table lists the supported versions of this manual in order of issue:
Issue
Date of issue
Remarks
Sep 2004
Issue Q GSM Software Release 7 Half Rate
Nov 2006
Issue R GSM Software Release 8 GMR02
Oct 2009
Issue S GSM Software Release 9
Resolution of Service Requests

The following Service Requests are resolved in this document:
Remarks
Service Request
CMBP Number
SR 2211808
N/A
Added a note under the section Security

overview.
SR 2241385
N/A
Added a new environment variable under the

section User configurable environment
variables.
SR 2272058
MOTCM01113155
Amended output in Step 2, Procedure 13-14.
SR 2282187
MOTCM01125030
Updated partitioning data for SunFire 4800/4900,

and Netra20/440 in Chapter 1.
SR 2333572
MOTCM01237311
Updated procedure 41 in Chapter 4.
Incorporation of Change Notices

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

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

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

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

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

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

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

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

A banner indicates that some information contained in the document is not yet approved for
general customer use. A banner is oversized text on the bottom of the page, for example,
PRELIMINARY UNDER DEVELOPMENT.
Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the
network is encrypted. In order to comply with the export and import requirements of particular
countries, this encryption occurs at different levels. The encryption may be individually
standardized or may not be present at all in some parts of the network in which it is normally
implemented. The document set covers encryption as if fully implemented. Limitations on the
encryption included in the particular software being delivered, are covered in the Release Notes
that accompany the individual software release.
12
68P02901W19-S
Oct 2009
Chapter
1
Introduction to the OMC-R
68P02901W19-S
Oct 2009
1-1
Overview
Overview
This chapter provides an overview of the OMC-R hardware configuration for SunFire 4800/4900,
Netra 20, Netra 440, and {34618} M4000 and M5000 based systems, and identifies the OMC-R
hardware and software components provided for each system.
Overviews of the daily, weekly and monthly procedures are also included, as well as other
routine procedures that must be performed by the OMC-R system administrator.
NOTE
For detailed information regarding OMC-R hardware and software installation, refer
to Installation and Configuration: OMC-R Clean Install (68P02901W47).
The following topics are described in this chapter:
OMC-R system configuration on page 1-3.
Configuring the OMC-R SunFire and Netra system processors on page 1-9.
Connecting to the LAN on page 1-24.
Routine system administration procedures on page 1-26.
Daily procedures on page 1-28.
Weekly procedures on page 1-30.
Monthly procedures on page 1-32.
Additional procedures on page 1-33.
NOTE
Throughout this manual, $OMC_TOP is used to describe the top level directory
structure /usr/omc.
1-2
68P02901W19-S
Oct 2009
OMC-R system configuration
OMC-R system configuration
Introduction to OMC-R system configuration

The OMC-R typically consists of the following:
A system processor (also known as the Single Platform Processor, SunFire 4800/4900,
Netra 20, Netra 440).
A Graphical User Interface (GUI) Server (for example, Sunblade 150).
Several GUI client processors which provide operator workstations.
A laser printer, suitable for LAN connection (for example, Lexmark Optra S1650).
Each processor is a complete UNIX system. An Ethernet Local Area Network (LAN) enables
interaction between all processors.
The OMC-R interfaces with the cellular network through the use of X.25 Packet Switched
protocol.
Typical hardware architecture of Motorola OMC-R, with optional equipment, is shown in
Figure 1-1.
68P02901W19-S
1-3
Oct 2009
Typical hardware architecture of OMC-R system
Typical hardware architecture of OMC-R system

Typical hardware architecture of an OMC-R SunFire/Netra system is shown in Figure 1-1.
Figure 1-1
Typical hardware architecture of OMC-R SunFire/Netra system
OMC-R specifications
The SunFire 4800/4900, Netra 20, or Netra 440 is a UNIX system that acts as the OMC-R
system processor, running the OMC-R application software which handles all Operation and
Maintenance communication with the Network Elements (NEs). A Packet Switch/Multiplexer
and the system processor HSI/P hardware enable the OMC-R to interface with the GSM network.
The OMC-R system processor processes all incoming events, alarms, uploads, downloads,
performance statistics, and the setting up of remote login sessions to different NEs.
The OMC-R system processor contains two databases constructed on an INFORMIX Relational
Database Management System model (RDBMS). One database (PM) is configured for storing
performance statistics and subscription lists, the other (CM) is configured for network and map
configuration data which enables operators to monitor incoming events and alarms through the
use of map displays.
The OMC-R system processor uses the Solaris 10 Operating System (OS) as the UNIX platform.
In addition to the OMC-R system processor, Graphical User Interface (GUI) Servers and Clients
based on SUN ULTRASparc processors can be used as operator workstations to manage and
monitor NE's.
1-4
68P02901W19-S
Oct 2009
GUI sessions and GUI server memory
The OMC-R can be configured to utilize an optional laser printer.

OMC-R specifications are shown in Table 1-1.
Table 1-1
OMC-R specifications (maximum values)

Feature
Netra 20/Netra 440
Sunfire
Total GUI sessions supported
30
60
Remote login sessions
30
90
Simultaneous downloads
12
36
Simultaneous uploads
32
64
Sustained event rate
12 alarms +
3 state changes
16 alarms +
4 state changes
Maximum event burst

over 20 minutes
32 alarms +
8 state changes
64 alarms +
16 state changes
GUI sessions and GUI server memory

In Table 1-1, the maximum number of GUI sessions supported is 60 for a Sunfire and 30 for
other Single Platform systems. However, this is based on the assumption that the appropriate
number of GUI servers and memory are in use.
For GUI Servers, the memory, and CPU speed of the GUI server are used to determine the
number of permitted GUI sessions.
The following formula gives the number of permitted GUI sessions. This formula has been
implemented in the corecheck_gui script. The corecheck_gui script is used to start GUI sessions.
Maximums_GUIs = (Memory X CPU speed) / 39060) + 1
Where
is
Memory
the GUI server memory
CPU Speed
the CPU clock speed of the

GUI server
Where:
Table 1-2 details the number of GUI sessions each GUI server configuration is capable of
supporting.
68P02901W19-S
1-5
Oct 2009
Factors influencing Processing Capability of GUI Servers
Table 1-2
GUI sessions per GUI server platform
Platform/Memory (MB)
CPU
(MHz)
Sunblade 150
256
270
256
360
256
400
512
270
512
360
512
400
1024
650
12
Factors influencing Processing Capability of GUI Servers

Test results have indicated that there are five main factors limiting the number of GUIs on
a GUI server. They are as follows:
Real memory or the physical Random Access Memory (RAM) available within the platform.
CPU speed.
CPU class, including cache.
Disk access speed.
Link capacity of the Local Area Network.
Other factors affecting the performance of the GUI Server are:
Number of FM operators (Open GUIs / MMI Windows).
Number of events arriving per second.
Operator workstations
The OMC-R system comprises of a single platform system processor and a number of operator
workstations. Each operator workstation is a complete UNIX system and runs the OMC-R
Graphical User Interface (GUI).
1-6
68P02901W19-S
Oct 2009
Optional processors
The operator workstations consist of a possible combination of the following:

GUI server:
High-end Sunblade 150
N210
GUI client:
Low end Sunblade 150
Refer to the Software Release Notes: OMC-R System (68P02901W74) for configuration details.
Optional processors
Optional processors can be added to the basic OMC-R configuration:
OSI (Open Systems Interconnect) processor
Datagen
Network Health Analyst (NHA)
Software requirements
GSM OMC-R GSR9 DVD 1.9.0.0.x contains the software requirements for all other OMC-R
platforms.
NOTE
If an NHA processor is connected to the OMC-R, then retain the NIS as the naming
service for the OMC-R LAN.
68P02901W19-S
1-7
Oct 2009
Software requirements
Table 1-3
Software requirements (Single Platform Processor)

Revision version
Media
Number of
volumes
Licence key
required
GSR9 DVD
1900.x
DVD
Sun Solaris
10
Solaris Logical
Volume Manager
11.9
Sun SunLink X25
9.2
Yes
TCL
8.4.6
TK
8.4.6
Enscript
1.6.1
EPAK
3.0.7
zlib
1.2.1
Perl
5.61
10
10.00.UC8
INFORMIX-Client
SDK
2.81
INFORMIX-ISQL
7.32
5.3
Applix
Spreadsheet
Applix Data
Mozilla
1.7
Python
2.2.3
Sun VTS
6.2
StorEdge
Enterprise
Backup Server
7.3
StorEdge
Enterprise
Backup Client
7.3
RTF licence
Yes
Title
FlexNet
INFORMIX-IDS
OSP
1-8
68P02901W19-S
Oct 2009
Configuring the OMC-R SunFire and Netra system processors
Configuring the OMC-R SunFire and Netra system

processors
Overview to SunFire and Netra configuration

Perform the following operations to configure the OMC-R SunFire 4800/4900 or
Netra 20/Netra 440 system processor:
Checking hardware requirements.
Connecting peripherals.
Installing and configuring cards.
Configuring hard drives.
Checking disk configuration.
NOTE
Configuration is initially performed by Motorola. Refer to Installation and
Configuration: OMC-R Clean Install (68P02901W47) for further details.
Checking SunFire hardware requirements

Typical requirements for an OMC-R SunFire 4800/4900 platform are detailed in Table 1-4.
Table 1-4
SunFire 4800/4900 hardware requirements
Equipment
Quantity
Description
OMC-R platform
SunFire 4800/4900 (including 4 x CPUs)
CPUs
900 MHz (minimum) US-III
Memory
Minimum 4 GB Memory (8 x 512 MB DIMMs)
Internal drives
36 GB SCSI
CPU memory board
DVD-ROM drive
SCSI
Continued
68P02901W19-S
1-9
Oct 2009
Checking Netra 20 hardware requirements
Table 1-4
SunFire 4800/4900 hardware requirements (Continued)
Equipment
Quantity
Description
DAT drive
4MM DDS4
SCSI/Ethernet combo
(Sun Swift)
Dual port SCSI 160 HBA

LVD (Jasper)
Serial I/O
4 port Synch
12
73 GB drives
All ac power
1 X 3310 JBOD SCSI 160

LVD disk array
System and Disk Array

Typical requirements for an OMC-R Netra 20 platform are detailed in Table 1-5.
Table 1-5
Netra 20 hardware requirements
Equipment
Description
Quantity
OMC-R platform
Netra 20 (including two CPUs)
CPUs
900 MHz (minimum) US-III
Memory
Minimum 4 GB Memory (8 x 512 MB DIMMs)
Internal drives
36 GB or 73 GB
DVD-ROM drive
SCSI
DAT drive
4MM DDS4

LVD (Jasper)
Serial I/O
4 port Synch
12
73 GB drives
All ac power

LVD disk array

Typical requirements for an OMC-R Netra 440 platform are detailed in Table 1-6.
Table 1-6
Netra 440 hardware requirements
Equipment
OMC-R platform
Quantity
1
Description
Netra 440 (including
two CPUs)
Continued
1-10
68P02901W19-S
Oct 2009
Table 1-6
Connecting peripherals
Netra 440 hardware requirements (Continued)
Equipment
Description
Quantity
CPUs
1280 MHz (minimum)

US-IIIi
Memory
Minimum 4 GB Memory
(8 x 512 MB DIMMs)
Internal drives
73 GB
DVD-ROM drive
SCSI

LVD (Jasper320)
Serial I/O
4 port Synch
12
73 GB drive
All ac power
QGE (Quad 1000 Mbit

Ethernet)

LVD disk array
External Tape Drive
Connecting peripherals to a SunFire 4800/4900
Figure 1-4 illustrates the peripheral connections to a SunFire 4800/4900. Once the SunFire
4800/4900, D240 media tray (Figure 1-3) and StorEdge 3310 Disk Array (Figure 1-2) have
been mounted, cables need to be attached.
Refer Figure 1-2, Figure 1-3, and Figure 1-4, and ensure that the configuration switch on the
D240 is in the split bus position.
Figure 1-2
68P02901W19-S
StorEdge 3310 Disk Array
1-11
Oct 2009
1-12
Figure 1-3
D240 Media Tray
Figure 1-4
Connecting peripherals on a SunFire 4800/4900
68P02901W19-S
Oct 2009
Use the following procedure to connect the SCSI cables for a SunFire 4800/4900:
Procedure 1-1
Connecting the SCSI cables to a SunFire 4800/4900
Connect a cable from UltraSCSI card 0 to lower port B of the 3310.
Connect a cable from UltraSCSI card 1 to lower port A of the 3310.
Connect a cable from SCSI+Ethernet card 0 to the top right connector

of the D240.
Connect a cable from SCSI+Ethernet card 1 to the top left connector

of the D240.
Connect Ethernet cables to SCSI+Ethernet card 0 and both SC0 and

SC1.
If a Sun rack is used, connect a serial port splitter cable to SC0 serial
and connect ttyb to the frame manager.
Connecting peripherals to a Netra 20

Figure 1-5 illustrates the peripheral connections to a Netra 20. Once the Netra 20 and StorEdge
3310 Disk Array (Figure 1-6) are mounted, attach the two SCSI cables as follows:
Figure 1-5
68P02901W19-S
Connecting peripherals on a Netra 20
1-13
Oct 2009
Figure 1-6
StorEdge 3310 Array
Use the following procedure to attach the two SCSI cables to a Netra 20:
Procedure 1-2
1-14
Connecting the SCSI cables to a Netra 20
Ensure that the cable from UltraSCSI 0 on the Netra goes to the lower
slot B on the disk array and the cable from UltraSCSI 1 on the Netra
goes to the lower slot A on the disk array. When powered up, both
TERM lights on the array should be lit.
Ensure that the terminal connected to the Serial Port console remains
connected for the duration of the installation.
68P02901W19-S
Oct 2009
Figure 1-7
68P02901W19-S
Connecting Peripherals on a Netra 440
1-15
Oct 2009
Figure 1-8
Netra 440 connected to StorEdge 3310 Array
Use the following procedure to attach the two SCSI cables to a Netra 440:
Procedure 1-3
1-16
Procedure to attach two SCSI cables to a Netra 440
Ensure that the two Ultra SCSI cards are installed in slots PCI 2 and PCI 4.
Connect the top most port (Port 1) of the Ultra SCSI card in PCI 2 to the
bottom right-most SCSI port (A) of the StorEdge 3310.
Connect the top-most port (Port 1) of the Ultra SCSI card in PCI 4 to the
bottom left-most SCSI port (B) of the StorEdge 3310. When powered up,
both TERM lights on the array should be lit.
68P02901W19-S
Oct 2009
Installing and configuring cards
Installing and configuring cards

Installing the HSI cards
The following procedure describes how to install and connect HSI cards for the SunFire or Netra:
Procedure 1-4
Installing the HSI cards in the SunFire or Netra
Install the HSI cards into the pci slots in the SunFire or Netra, as
described in the Sun Hardware Guide.
Connect the HSI cards to the external X.25 network equipment using
the cables provided.
Card configuration
Table 1-7 specifies the location of the cards for a SunFire 4800/4900.
Table 1-7
Location of cards for a SunFire
Board
Slot
Card description
IB8
Slot 1
HSI 1
Slot 4
UltraSCSI 1
Slot 5
SCSI + Ethernet 1
Slot 6
HSI 2
Slot 1
HSI 0
Slot 4
UltraSCSI 0
Slot 5
SCSI + Ethernet
IB6
Table 1-8 specifies the location of the cards for a Netra 20.
Table 1-8
68P02901W19-S
Location of cards for a Netra 20

Slot
Card description
Slot 1
UltraSCSI 1
Slot 2
UltraSCSI 0
Slot 3
HSI 1
Slot 4
HSI 0
1-17
Oct 2009
Configuring hard drives
Table 1-9 specifies the location of the cards for a Netra 440.
Table 1-9
Location of cards for a Netra 440

Slot
Card description
Slot 0
HSI 0
Slot 1
HSI 1
Slot 2
UltraSCSI 0
Slot 4
UltraSCSI 1
Configuring hard drives

Table 1-10 specifies the internal configuration of hard drives in the Netra 20.
Table 1-10
Internal configuration of hard drives in the Netra 20/440
Slot location
Disk name
Disk sizes allowed
Slot 0
c2t0d0
73 GB
Slot 1
c2t1d0
73 GB
Figure 1-9 illustrates the internal disk slots in the Netra 20/440.
Figure 1-9
1-18
Netra 20/440 internal disk slots
68P02901W19-S
Oct 2009
Disk configuration SunFire 4800/4900, Netra 20 and Netra 440

The single platform processor controls either twelve 73 GB disks or {34618} 146 GB disks.
Table 1-11 and Table 1-12 are based on 146 GB disks. The disks are shipped from Sun with
a default partition configuration. The logical disk partitions critical for the boot process
are amended during the Solaris operating system installation. The JumpStart procedure
incorporates Solaris Logical Volume Manager to set up the metadevices. For these servers, the
metadevice numbers are generated dynamically.
Table 1-11 highlights the partitioning details used for the SunFire 4800/4900 and Netra 20
servers.
Table 1-12 highlights the partitioning details used for the Netra 440 servers.
Table 1-11
File
System
Disk partitioning for SunFire 4800/4900 and Netra 20 servers

SF Size
Netra
Size
Sub Mirror 0
Stripe
Sub Mirror 1
Stripe
Mirror
Disk
Sub Mirror
0
Sub
Mirror 1
17 GB
17 GB
c1t8d0s0
c3t8d0s0
d0
d1
d2
none
Swap
9.6 GB
9.6 GB
c1t8d0s1
c3t8d0s1
d5
d6
d7
none
/var
41 GB
41 GB
c1t8d0s3
c3t8d0s3
d10
d11
d12
none
/opt
34 GB
34 GB
c1t8d0s4
c3t8d0s4
d15
d16
d17
none
/usr
27 GB
27 GB
c1t8d0s5
c3t8d0s5
d20
d21
d22
none
/omcgen
6.8 GB
6.8 GB
primary_disk*
mirror_disk*
d25
d26
d27
d30
/home
10 GB
10 GB
primary_disk
mirror_disk
d25
d26
d27
d35
/usr/omc
5.9 GB
5.9 GB
primary_disk
mirror_disk
d25
d26
d27
d40
/usr/omc
/ne_data
16 GB
16 GB
primary_disk
mirror_disk
d25
d26
d27
d50
/usr/omc/
ne_data/
raw_stats
12 GB
12 GB
primary_disk
mirror_disk
d25
d26
d27
d55
solbak
7.8 GB
7.8 GB
primary_disk
mirror_disk
d25
d26
d27
d60
omc_db
_root
2.0 GB
2.0 GB
primary_disk
mirror_disk
d25
d26
d27
d85
omc_db1
13 GB
11 GB
primary_disk
mirror_disk
d25
d26
d27
d90
omc_db2
13 GB
11 GB
primary_disk
mirror_disk
d25
d26
d27
d95
omc_db3
13 GB
11 GB
primary_disk
mirror_disk
d25
d26
d27
d100
omc_db4
13 GB
11 GB
primary_disk
mirror_disk
d25
d26
d27
d105
omc_db5
13 GB
11 GB
primary_disk
mirror_disk
d25
d26
d27
d110
omc_db6
13 GB
11 GB
primary_disk
mirror_disk
d25
d26
d27
d115
omc_db7
13 GB
11 GB
preliminaries
mirror_disk
d25
d26
d27
d120
omc_db8
13 GB
11 GB
primary_disk
mirror_disk
d25
d26
d27
d125
omc_db9
13 GB
11 GB
primary_disk
mirror_disk
d25
d26
d27
d130
Soft
Partition
Continued
68P02901W19-S
1-19
Oct 2009
Table 1-11
Disk partitioning for SunFire 4800/4900 and Netra 20 servers (Continued)
File
System
SF Size
Netra
Size
Sub Mirror 0
Stripe
Sub Mirror 1
Stripe
Mirror
Disk
Sub Mirror
0
Sub
Mirror 1
omc_db10
13 GB
11 GB
primary_disk
mirror_disk
d25
d26
d27
d135
omc_db11
13 GB
11 GB
primary_disk
mirror_disk
d25
d26
d27
d140
omc_db12
13 GB
11 GB
primary_disk
mirror_disk
d25
d26
d27
d145
omc_db
_temp
2.0 GB
2.0 GB
primary_disk
mirror_disk
d25
d26
d27
d155
omc_db
_logs
2.0 GB
2.0 GB
primary_disk
mirror_disk
d25
d26
d27
d150
mib_db
2.0 GB
2.0 GB
primary_disk
mirror_disk
d25
d26
d27
d170
mib_db1
2.0 GB
2.0 GB
primary_disk
mirror_disk
d25
d26
d27
d160
mib_db2
2.0 GB
2.0 GB
primary_disk
mirror_disk
d25
d26
d27
d165
mib_db
_logs
2.0 GB
2.0 GB
primary_disk
mirror_disk
d25
d26
d27
d175
Soft
Partition
NOTE
*primary_disk: c1t9d0s0 c1t10d0s0 c1t11d0s0 c1t12d0s0 c1t13d0s0
*mirror_disk: c3t9d0s0 c3t10d0s0 c3t11d0s0 c3t12d0s0 c3t13d0s0
Table 1-12
Disk partitioning for Netra 440 servers

Size
Sub Mirror 0
Stripe
Sub Mirror 1
Stripe
Mirror
Disk
Sub
Mirror 0
Sub
Mirror 1
Soft
Partition
17 GB
c0t8d0s0
c1t8d0s0
d0
d1
d2
none
Swap
9.6 GB
c1t8d0s1
c3t8d0s1
d5
d6
d7
none
/var
41 GB
c0t8d0s3
c1t8d0s3
d10
d11
d12
none
/opt
34 GB
c0t8d0s4
c1t8d0s4
d15
d16
d17
none
/usr
27 GB
c0t8d0s5
c1t8d0s5
d20
d21
d22
none
/omcgen
6.8 GB
primary_disk*
mirror_disk*
d25
d26
d27
d30
/home
10 GB
primary_disk
mirror_disk
d25
d26
d27
d35
/usr/omc
5.9 GB
primary_disk
mirror_disk
d25
d26
d27
d40
/usr/omc
/ne_data
16 GB
primary_disk
mirror_disk
d25
d26
d27
d50
/usr/omc/
ne_data/
raw_stats
12 GB
primary_disk
mirror_disk
d25
d26
d27
d55
File
System
Continued
1-20
68P02901W19-S
Oct 2009
Table 1-12
File
System
Disk partitioning for Netra 440 servers (Continued)

Size
Sub Mirror 0
Stripe
Sub Mirror 1
Stripe
Mirror
Disk
Sub
Mirror 0
Sub
Mirror 1
Soft
Partition
solbak
7.8 GB
primary_disk
mirror_disk
d25
d26
d27
d60
omc_db
_root
2.0 GB
primary_disk
mirror_disk
d25
d26
d27
d85
omc_db1
11 GB
primary_disk
mirror_disk
d25
d26
d27
d90
omc_db2
11 GB
primary_disk
mirror_disk
d25
d26
d27
d95
omc_db3
11 GB
primary_disk
mirror_disk
d25
d26
d27
d100
omc_db4
11 GB
primary_disk
mirror_disk
d25
d26
d27
d105
omc_db5
11 GB
primary_disk
mirror_disk
d25
d26
d27
d110
omc_db6
11 GB
primary_disk
mirror_disk
d25
d26
d27
d115
omc_db7
11 GB
primary_disk
mirror_disk
d25
d26
d27
d120
omc_db8
11 GB
primary_disk
mirror_disk
d25
d26
d27
d125
omc_db9
11 GB
primary_disk
mirror_disk
d25
d26
d27
d130
omc_db10
11 GB
primary_disk
mirror_disk
d25
d26
d27
d135
omc_db11
11 GB
primary_disk
mirror_disk
d25
d26
d27
d140
omc_db12
11 GB
primary_disk
mirror_disk
d25
d26
d27
d145
omc_db
_temp
2.0 GB
primary_disk
mirror_disk
d25
d26
d27
d170
omc_db
_logs
2.0 GB
primary_disk
mirror_disk
d25
d26
d27
d165
mib_db
2.0 GB
primary_disk
mirror_disk
d25
d26
d27
d185
mib_db1
2.0 GB
primary_disk
mirror_disk
d25
d26
d27
d175
mib_db2
2.0 GB
primary_disk
mirror_disk
d25
d26
d27
d180
mib_db
_logs
2.0 GB
primary_disk
mirror_disk
d25
d26
d27
d190
NOTE
68P02901W19-S
*primary_disk: c0t9d0s0 c0t10d0s0 c0t11d0s0 c0t12d0s0 c0t13d0s0
*mirror_disk: c1t9d0s0 c1t10d0s0 c1t11d0s0 c1t12d0s0 c1t13d0s0
1-21
Oct 2009
Table 1-13
OMC-R Single Platform Disk Partition Layout
Partition
Size
Location
8.8GB (increased by 4GB)
Primary Disk S0
swap
4.8GB
Primary Disk S1
/var
20.5GB
Primary Disk S3
/opt
7.1GB
Primary Disk S4
/usr
13.7GB
Primary Disk S5
Total
64.9GB
Primary Disk
/omcgen
7.0GB
Application Stripe
/home
10.9GB
Application Stripe
/usr/omc
6.0GB
Application Stripe
omc_db1
11.264GB
Application Stripe
omc_db5
11.264GB
Application Stripe
omc_db9
11.264GB
Application Stripe
/usr/omc/ne_data
16.4GB
Application Stripe
/usr/omc/ne_data/raw_stats
13.3GB (increased by 2GB)
Application Stripe
omc_db_root
2.048GB
Application Stripe
omc_db2
11.264GB
Application Stripe
omc_db6
11.264GB
Application Stripe
omc_db10
11.264GB
Application Stripe
omc_db_logs
2.048GB
Application Stripe
omc_db3
11.264GB
Application Stripe
omc_db7
11.264GB
Application Stripe
omc_db11
11.264GB
Application Stripe
/solbak
8.0GB
Application Stripe
omc_db4
11.264GB
Application Stripe
omc_db8
11.264GB
Application Stripe
omc_db12
11.264GB
Application Stripe
mib_db_logs
2.048GB
Application Stripe
omc_db_temp
2.048GB
Application Stripe
mib_db
2.048GB
Application Stripe
mib_db1
2.048GB
Application Stripe
mib_db2
2.048GB (new)
Application Stripe
/usr/omc/logs/bss_sec
8.0GB (new)
Application Stripe
/usr/omc/logs/sleeping_cell
2.048GB (new)
Application Stripe
lod_db1
10GB (new)
Application Stripe
Continued
1-22
68P02901W19-S
Oct 2009
Table 1-13
OMC-R Single Platform Disk Partition Layout (Continued)
Partition
Size
Location
lod_db2
10GB (new)
Application Stripe
lod_db3
10GB (new)
Application Stripe
/zones
10GB (new)
Application Stripe
/usr/omc/ne_data/e1mon
1GB (new)
Application Stripe
Total
262GB
NOTE
* Netra 440s have different controller numbers than those shown in the table. Instead
of c1 and c3, Netra 440s use c0 and c1. For example, the root partition on a Netra
20 is on slice c1t8d0s0 on the main disk and on slice c3t8d0s0 on the mirror disk.
However, the root partition on a Netra 440 is on slice c0t8d0s0 on the main disk
and on slice c1t8d0s0 on the mirror disk.
68P02901W19-S
1-23
Oct 2009
Connecting to the LAN
Overview of connecting to the LAN

All processors that constitute the OMC-R system, use an Ethernet Local Area Network (LAN) for
interaction. The LAN may be extended to cater to remote workstations or for the addition of
optional processors.
Each processor must be connected to the LAN before software installation begins or backup is
performed. During normal OMC-R operation the processors NFS mount file systems across the
network.
Configuring the OMC-R based LAN

The means of asynchronous communication between the OMC-R processors and workstations is
twisted pair cabling which may be connected to a customer LAN/WAN backbone network by
using a Hub or Router or Bridge or Gateway.
Each OMC-R system is provided with a Hub that can be installed for normal operation or used
for testing.
1-24
68P02901W19-S
Oct 2009
Configuring the OMC-R based LAN
The LAN connection of a typical OMC-R system is shown in Figure 1-10.
Figure 1-10
LAN connections
NOTE
The SQE switch on the Ethernet transceivers should normally be set to OFF. The
switch should only be set to ON if the processors are to be connected through a
router to a local network where SQE is implemented.
To reduce the impact of a hub failure, a spare hub is provided with the OMC-R.
68P02901W19-S
1-25
Oct 2009
Routine system administration procedures
Routine system administration procedures
Introduction to routine system administration procedures

Motorola recommends that procedures be performed regularly in order to maintain and
administer to the OMC-R system. Certain special procedures may be required depending on
individual customer requirements.
Recommended routine procedures are described in the sections that follow. In each case, a
reference is made to the relevant section in this manual for the actual procedure. All the results
from these procedures as well as any system changes should be recorded in a log book.
Daily log book

The following items should be recorded by the system administrator in a daily log book that
resides permanently by the system processor console:
Details of all the procedures that have been performed as user root, Informix, and
omcadmin. These should be laid out in chronological order and should include the
following information:
Date
Time
Processor
Operator
Task description
A list of backup and archive tapes containing the following information:

Date
Processor
Unique tape number
Description
Read instructions
Storage location of tapes
1-26
68P02901W19-S
Oct 2009
Daily log book
A list of file printouts containing the following information:

Date
File name
Storage location of printouts
The local Motorola support center contact number.
A list of contact names, telephone numbers, and the responsibilities of personnel involved
in daily activities.
Contact information for any emergency services that may be required.
68P02901W19-S
1-27
Oct 2009
Daily procedures
Daily procedures
INFORMIX database daily procedures

The following procedures concern the INFORMIX databases. These procedures should be
carried out daily by the OMC-R system administrator.
Back up the INFORMIX databases

Perform a level 2 backup of the two databases on the system processor. Refer to Chapter 12
Backup Server Installation and Configuration.
Monitor the PM database disk usage

To ensure that the PM database functions effectively, the database disk usage should be
monitored daily. When the omc_db_maint utility is used, the omc_db_maint log file contains
the disk usage information required. Refer to Administering the PM database using the
omc_db_maint utility on page 8-23 for further information.
Unload and purge the PM database on the system processor

The data stored in the PM database (for example, the regular statistics, subscription lists, and
configuration data) is copied to ASCII files and then deleted from the PM database by the
omc_db_maint utility. This procedure may be automated using cron.
A purge operation should be performed on the database on a daily basis (for example, deleting
statistics). This can be carried out in conjunction with unloading the database using the
omc_db_maint utility. Refer to Administering the PM database using the omc_db_maint
utility on page 8-23.
Inspect the omc_db_maint log file to ensure that omc_db_maint runs successfully. Refer to
Administering the PM database using the omc_db_maint utility on page 8-23.
The data in the ASCII files can be archived to tape and then deleted.
Check the INFORMIX log files

Inspect the database log files (online.log_OMC and online.log_MIB) for errors and to ensure
that check-pointing is occurring regularly (for example, every five minutes). The database
log files online.log_OMC and online.log_MIB are located in the /usr/informix directory
on the system processor.
Manually parse any unparsed statistics files

Any raw statistics files that may have escaped processing by the Performance Management (PM)
file parser (for example, OMC-R stopped during raw statistics collection period) can be manually
submitted using the pm_manual_parse utility. Refer to Database utilities on page 8-4.
1-28
68P02901W19-S
Oct 2009
UNIX file systems daily procedures
UNIX file systems daily procedures

The following procedure concerns UNIX file systems. This procedure should be carried out on a
daily basis by the OMC-R system administrator.
Back up the UNIX file systems

A daily backup of all the OMC-R UNIX file systems should be carried out using StorEdge
Enterprise.
Miscellaneous daily procedures

The following are miscellaneous procedures which should be carried out daily by the OMC-R
system administrator.
Check that all cron jobs have completed successfully

To ensure that all cron jobs have run successfully, check the mail report sent from cron to root
and omcadmin on each of the relevant processors (for example, the system processor and GUI
server). Refer to CDE utilities available to either root or omcadmin login on page 2-20 and
Scheduling cron jobs from the command line on page 5-14.
Check the OMC-R log files

The OMC-R log files, located in the $OMC_TOP/logs directory, should be inspected for errors
and abnormalities. The logging structure is described in OMC-R log and error files on page
4-3 and descriptions of the possible errors are listed in OMC-R software process errors on
page 13-25.
Check for core dump files

All OMC-R user accounts should be checked to see if any core dump files exist. Any core dump
files found should be dealt with as described in Core file generation on page 13-6.
Check the system processor hardware

Procedures for inspecting the hardware are described in Checking the system processor
hardware on page 13-99.
Check X.25 connectivity

Procedures for checking X.25 connectivity are described in X.25 application management on
page 9-3.
68P02901W19-S
1-29
Oct 2009
Weekly procedures
Weekly procedures
INFORMIX database weekly procedures

The following procedures concern the INFORMIX databases. These procedures should be
carried out on a weekly basis by the OMC-R system administrator.
Roll the database log (online.log)

The database log file should be moved to a time-stamped file using the roll_online.log script.
This procedure is automated using cron.
UNIX file systems weekly procedures

The following procedures concern the UNIX file systems. These procedures should be carried
out on a weekly basis by the OMC-R system administrator.
Back up UNIX file systems

A weekly backup of the UNIX file systems (instead of a daily backup) should be carried out using
StorEdge Enterprise, as described in Chapter 12 Backup Server Installation and Configuration.
Archive and remove old OMC-R log files on the system processor and
GUI servers
OMC-R log files should be archived onto tape and unwanted log files removed from the disk
file system using the maintain_script utility.
This procedure may be automated using cron (refer to System cron jobs on page 5-3).
Archive and remove unloaded PM database files on the system processor

The ASCII files created by the daily unloading of PM statistics should be archived to tape and
removed from the disk file system using the maintain_script utility.
This procedure can be automated using cron (refer to System cron jobs on page 5-3).
Monitor the UNIX file system disk usage

To ensure that the OMC system functions effectively, the disk usage should be monitored using
the UNIX command df or the systat utility (refer to OMC-R system information on page 13-8
and Full file systems on page 13-21). This can become a weekly task as alarms are generated
when the disk becomes full.
1-30
68P02901W19-S
Oct 2009
Security-related weekly procedures
Archive and remove old OMC-R user files

Any old files in the home accounts of OMC-R users should be archived and removed. Refer to
Archiving old OMC-R user files on page 2-23.
This procedure can be automated using cron (refer to System cron jobs on page 5-3).
Security-related weekly procedures

The following is a security-related procedure that should be carried out on a weekly basis by
the OMC-R system administrator.
Monitor user security

For security reasons, user account files and network files should be checked for unwanted
entries. Additionally, log files in /var/log should be checked for unwanted system access
attempts.
68P02901W19-S
1-31
Oct 2009
Monthly procedures
Monthly procedures
UNIX file systems monthly procedures

The following procedure concerns the UNIX file systems. This procedure should be carried out
on a monthly basis by the OMC-R system administrator.
Back up UNIX file systems

A monthly backup of the UNIX file systems (instead of a daily/weekly backup) should be carried
out using StorEdge Enterprise, as described in Chapter 12 Backup Server Installation and
Configuration.
Truncate cron log file

Shorten the cron log file each month to maintain a reasonable file size. For details of this
procedure refer to Scheduling cron jobs from the command line on page 5-14.
Security-related monthly procedures

The following security-related procedure should be carried out monthly by the OMC-R system
administrator.
Change passwords
Change the passwords from the standard installation passwords for root, omcadmin and
Informix on the system and GUI processors.
Inform all other OMC-R users to change passwords regularly.
1-32
68P02901W19-S
Oct 2009
Additional procedures
Additional procedures
Additional event driven procedures

There are certain event driven procedures which are carried out by the OMC-R system
administrator. These additional procedures are conducted on a needs basis.
Complete file system backup

Perform a complete file system backup in the following cases:
Before and after initial installation of the OMC-R software.
Before a disk partition size is changed.
Refer to Chapter 12 Backup Server Installation and Configuration.
NE load management maintenance

Archive and remove any NE software loads and databases that are no longer required.
PM raw statistics maintenance

Unparsed PM raw statistics files in the $OMC_TOP/ne_data/raw_stats directory structure
should be monitored to determine if they need to be archived to tape and/or removed from the
disk file system. Refer to Database utilities on page 8-4.
OMC-R user accounts

New OMC-R users should be added and old users deleted, as described in Administering user
accounts with usertool on page 2-12.
68P02901W19-S
1-33
Oct 2009
Hard copy listings (printouts)
Hard copy listings (printouts)

Hard copy listings of various files and system information should be made after initial
installation of the OMC-R, and after every change to the configuration of the system.
A process id report listing should be made using the ps command for the system and GUI
processors. This is produced when the systat utility is run. Refer to OMC-R system information
on page 13-8.
System core dumps

System core dump files may be produced (for example, due to system halts or OMC-R errors
occurring). If system core dump files are produced, the action to be taken is described in
Core file generation on page 13-6.
Hardware maintenance
Hardware maintenance procedures should be carried out in accordance with the instructions
of the manufacturers. The following procedures are needed:
1-34
Tape drive cleaning - refer to the Solaris 10 Administrator's Guide.
Replacement of toner, cartridge, and other printer components - refer to the relevant
printer maintenance manual.
Clean the monitor screens.
68P02901W19-S
Oct 2009
Chapter
2
System management
68P02901W19-S
Oct 2009
2-1
Overview
Overview
2-2
Overview of the Common Desktop Environment (CDE) on page 2-3.
Administering group accounts with usertool on page 2-8.
Administering user accounts with usertool on page 2-12.
CDE utilities available to an omcadmin login on page 2-18.
CDE utilities available to either root or omcadmin login on page 2-20.
Archiving old OMC-R user files on page 2-23.
OMC software management on page 2-24.
Cleaning up OMC-R software loads on page 2-28.
NE database maintenance on page 2-30.
Printing current OMC-R processes on page 2-35.
Security overview on page 2-36.
Controlling user activity on the system on page 2-40.
Controlling user passwords on page 2-42.
Network file security on page 2-44.
Installing OMC-R Help on page 2-45.
Capacity control on page 2-46.
Restartable processes on page 2-49.
Graceful shutdown on mains failure on page 2-57.
Configuration and installation of a remote terminal on page 2-59.
Remote system processor setup on page 2-63.
Monitor alternative OMC-R from GUI server on page 2-65.
Removing OMC-R night concentration centre configuration on page 2-67.
Setting the locale on the OMC-R on page 2-69.
General administration checklists on page 2-74.
68P02901W19-S
Oct 2009
Overview of the Common Desktop Environment (CDE)
Overview of the Common Desktop Environment (CDE)
Overview of the CDE

The following sections describe the utilities available through the Common Desktop Environment
(CDE). The CDE provides an industry standard desktop manager for the OMC-R, and is provided
on the different SUN workstations.
The CDE supports:
Operator configurable windows on startup.
Reduced window clutter through use of multiple panes.
A File Manager which provides a graphical front end to the UNIX file system.
There are two desktops displayed in the CDE:
The Root user desktop (Figure 2-1).
The OMC admin desktop (Figure 2-2).
The display of the desktop depends upon the type of login.
Figure 2-1
Root user desktop
Figure 2-2
OMC admin user desktop
68P02901W19-S
2-3
Oct 2009
Utilities available from the root CDE desktop
Utilities available from the root CDE desktop

The following CDE desktop tools are described in this chapter:
Administration.
StorEdge Enterprise Backup.
NOTE
These tools are only available to a user logged in as root.
These utilities are available from the root CDE desktop, OMC Admin menu, admin_tool option
(Figure 2-3).
Figure 2-3
Root user desktop with OMC Admin menu displayed (partial view)
NOTE
The Adminsuite product has become obsolete in Solaris 10. A new tool called usertool
replaces Adminsuite for administering users and groups.
2-4
68P02901W19-S
Oct 2009

The following utilities are common to both the omcadmin and the root CDE desktops. These
utilities are available from the front panel of the CDE desktop.
File Manager.
Cron job scheduler.
Mail.
Help Manager.
Accessing usertool
Use one of the following procedures to access usertool.
Accessing usertool from the root CDE desktop

Use the following procedure to access the usertool from the CDE desktop.
Procedure 2-1
68P02901W19-S
Accessing usertool from the CDE desktop
Login to the system processor as user root. The root CDE desktop
is displayed (Figure 2-1).
Click on the System Administration icon. The OMC Admin menu

is displayed (Figure 2-3).
2-5
Oct 2009
Accessing usertool
Accessing usertool from the Root Command Line Interface

Use the following procedure to access usertool from the Root Command Line Interface:
Procedure 2-2
1
Accessing user tool from the Command Line Interface
If logged in as user root, execute the following DISPLAY command:

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

export DISPLAY
/usr/omc/current/sbin/OMC_Sync
Figure 2-4
2-6
Usertool main window
68P02901W19-S
Oct 2009
Accessing usertool
Once an option is chosen, a screen containing all the relevant fields which can be modified
appears. On this screen, one field is highlighted with a bar which can be moved with the cursor
keys. The highlighted field can be modified by typing or deleting as required. Once all the fields
are correctly filled in, select Done to save changes, or select Cancel to quit.
Username
: joe
Joe Operator
Full Name
Home directory
: 500
Secondary groups
Change password
: /home/joe
Group
UID
: omc
Account locked
: n
: n
Shell
: /bin/csh
Done
Cancel
If any fields are in conflict, a message to that effect will be displayed:

Username
: joe
Joe Operator
Home directory
: 110
: omc
: Account locked
/bin/csh Done
Done
Full Name
: /home/joe
:
UID
UID already in use
Group
Secondary groups
: n
Change password
: n
Shell
Cancel
Cancel
Once Done is chosen, the relevant user or group operation is performed. After adding, deleting
or modifying users, the CDE settings and MIB profiles are also updated automatically, if the
user is a member of the omc group.
68P02901W19-S
2-7
Oct 2009
Administering group accounts with usertool
Administering group accounts with usertool
Overview of group management functions in usertool

The following section describes the group management functions in usertool.
The group management functions in usertool are used to manage the group file in the NIS
database centralized on the system processor, if the appropriate access privileges are granted.
The usertool supports the following group management tasks.
Add a group.
Modify a group.
Rename a group.
Delete a group.
NOTE
After a clean install of an OMC-R system, the groups Informix, omc and omcread
exist. Under normal circumstances, there is no need to add, modify or delete groups.
Before assigning users to a specific group, make sure that the group exists. Group management
is used to add any groups to which the users are assigned.
The Motorola recommended group IDs are as follows:
Informix
109
omc
110
omcread
111
NOTE
The usertool utility described in the following section is designed for local/NIS
accounts only. If another naming service (for example, LDAP) is in use, or another
tool (for example, SMC) is preferred, some manual steps are required in order to
configure MIB profiles.
The procedure for this is: /usr/omc/current/sbin/OMC_SysProc_Synchronise action
parameters.
2-8
68P02901W19-S
Oct 2009
Group Management parameters
Where action and parameters are as follows:
Table 2-1
Action and parameters
After
Action
Parameters
Creating a user
newuser
username
Modifying a user
modifyuser
username
Renaming a user
renameuser
oldname newname
Deleting a user
deleteuser
username
Group Management parameters

The different group management windows can contain combinations of the following parameters.
Group
Group specifies a name used by the system to identify a user group. A group name contains
lower case alphabetical characters (a - z) and digits (0 - 9). Spaces are not allowed. A group
name is between 1 to 8 characters long. By default, the groups omc, omcread and Informix
are present along with the standard operating system groups.
Group ID (GID)
Group ID specifies a group identification number used by the system to identify a user's primary
group. To minimize the amount of software incompatibility, GIDs are kept below 60000.
Reserved GIDs include 60001 (nobody), 60002 (no access) and 65534 (no group).
Figure 2-5
68P02901W19-S
Group administration utility
2-9
Oct 2009
Adding a group
Adding a group
Use the following procedure to add a new user group.
Procedure 2-3
Adding a new user group
Follow the procedure Accessing usertool on page 2-5.
From the usertool main window, select Add group. The Group
administration utility is displayed as in Figure 2-5.
Enter a unique Group name and Group ID (GID).
To commit the changes, select Done by highlighting it with the cursor

key and pressing Enter.
Modifying group accounts

Use the following procedure to modify a group account.
Procedure 2-4
Modifying a group account
From the usertool main window, select Modify group. The Group
administration utility is displayed as in (Figure 2-5).
Modify the group name and/or GID as required.

Renaming group accounts

Use the following procedure to rename a user group.
Procedure 2-5
2-10
Renaming a user group account
From the usertool main window, select Rename group.
Enter the name of the group to be renamed.
Enter the new name for the group and press return to complete the process.
68P02901W19-S
Oct 2009
Deleting group accounts
Deleting group accounts

Use the following procedure to delete a user group.
Procedure 2-6
68P02901W19-S
Deleting a user group account
From the usertool main window, select Delete group.
Enter the name of the group to be deleted.
To commit, select Done by highlighting it with the cursor key and

pressing Enter.
2-11
Oct 2009
Administering user accounts with usertool
Administering user accounts with usertool
Overview of user management functions in usertool

The user management functions in usertool enable the management of OMC user accounts in
the NIS database centralized on the system processor. A user account enables a user to log
in to a system and provides the access to a home directory.
The user management functions in usertool are used to perform the following user management
tasks.
Add a new user account.
Modify a user account.
Rename a user account.
Delete a user account.
Change a users password.
NOTE
After adding, deleting or modifying users, the CDE settings and MIB profiles are
updated automatically if the user is a member of the omc group.
A root user can manage user accounts in the NIS domain.
Before assigning users to specific groups, ensure that the groups exist. Before adding user
accounts, group management should be used to check any groups to which users are assigned.
See Administering group accounts with usertool on page 2-8.
The Motorola recommended group IDs are as follows.
Informix
109
omc
110
omcread
111
NOTE
To ensure that the correct GUI colors appear for all users, follow the procedure in
the section Ensuring the correct GUI colors appear.
2-12
68P02901W19-S
Oct 2009
Ensuring the correct GUI colors appear
Ensuring the correct GUI colors appear

Use the following procedure to ensure the correct GUI colors appear for all users.
Procedure 2-7
Ensuring the correct GUI colors appear for all users
Login as root.
Enter the following command:

cd /etc/dt/config/C
Edit the sys.session file. If this file does not exist, copy it from the
/usr/dt/config/C directory.
Comment out the three command lines that start with dtsmcmd.
Save the file.
User management parameters

The different user management windows can contain combinations of the following parameters
described in this section.
User name
User name specifies a login name the user will use when logging onto the OMC system. A user
name should be a unique name composed of 1-8 upper case or lower case alphabetical characters
(A-Z, a-z) or digits (0-9). It is advisable that the first character is a lower case letter (a-z).
Full name
Full Name is a control that specifies notes about the user account, such as a user's full name
or role. Although Full name is an optional control, it is highly recommended that a value be
entered in this field, as it is required by specific command line Operation and Maintenance
utilities such as cmdLineAudit.
Home directory
Home directory shows the default home directory for the user and can be edited as required.
User ID (UID)
User ID specifies a unique number by which the operating system can identify a user. The UID
should be unique. It is good practice to have sequentially increasing UIDs to aid in system
administration.
68P02901W19-S
2-13
Oct 2009
User management parameters
Group
Group specifies a group ID number or group name that the operating system assigns to files
created by the user. Standard group numbers are 110 for a normal OMC operator account, 111
for a restricted omcread account, and 109 for an Informix account.
Secondary groups
Secondary groups is an optional control that is not used in the Motorola configuration, but it
specifies one or more groups to which the user belongs.
Account locked
Setting account locked to y means that this account cannot be accessed. The default setting
is n (unlocked).
Change password
Setting change password to y forces the user to enter a new account when accessing this
account for the first time. The default setting is n.
Shell
Shell specifies the login shell to be used. The default shell is the C shell. The C shell is
mandatory for OMC users.
Figure 2-6
2-14
User administration utility
68P02901W19-S
Oct 2009
Adding a user
Adding a user
Use the following procedure to add a new user.
Procedure 2-8
Adding a new user
From the usertool main window, select Add user. The User
Enter a unique user name and modify the default user creation
parameters as required.
NOTE
It is highly recommended that a value is entered in the
Full name field, as it is required by specific command line
Operation and Maintenance utilities such as cmdLineAudit.
4
Highlight Done and select it by pressing the Enter key.
Enter the user account password twice. This completes user creation.
NOTE
The user privileges and profile are updated in the MIB database.
If the OSI Processor is already integrated with or connected to the OMC,

each new OMC user will be automatically entered into the relevant
/usr/omc/config/global/system_table file of the Security Application.
If the OSI Processor is to be integrated or configured later, or if, for some

reason, the users on the OMC and the OSI (the Security Application) are out
of synchronization, the user entries in both applications must be synchronized
manually using the OMC Security Synchronization tool.
Modifying a user account
NOTE
Under normal circumstances users root, omcadmin and Informix should not be
modified.
68P02901W19-S
2-15
Oct 2009
Renaming a user account
Use the following procedure to modify a user account.
Procedure 2-9
Modifying a user account
From the usertool main window, select Modify user. The User
Enter the name of the user to be modified and modify parameters as

required.

NOTE
Under normal circumstances users root, omcadmin, and Informix should not be
renamed.
Use the following procedure to rename a user account.
Procedure 2-10
From the usertool main window, select Rename user.
Enter the name of the user to be renamed.
Enter the new name for the user and press return to complete the process.
Deleting a user account
NOTE
Under normal circumstances users root, omcadmin and Informix should not be
deleted.
2-16
68P02901W19-S
Oct 2009
Use the following procedure to delete a user account.
Procedure 2-11
From the usertool main window, select Delete user.
Enter the name of the user to be deleted.
To commit to deleting the group, select Done by highlighting it with

the cursor key and pressing Enter.
NOTE
The user profile is also deleted from the MIB database.
68P02901W19-S
2-17
Oct 2009
CDE utilities available to an omcadmin login
CDE utilities available to an omcadmin login
Displaying the omcadmin CDE desktop

Use the following procedure to display the omcadmin CDE desktop.
Procedure 2-12
1
From the GUI Client graphical CDE login screen, as shown in

Figure 2-7, select Remote Login from the Options menu.
Type the hostname of a GUI server that exists in the /etc/hosts file
of the GUI client, and click OK.
The GUI server graphical CDE login screen appears, as shown in

Figure 2-8.
Enter the username omcadmin and password, then click OK to

display the CDE desktop.
Figure 2-7
2-18
Displaying the omcadmin CDE desktop
GUI client graphical CDE login screen
68P02901W19-S
Oct 2009
Figure 2-8
Database Applications menu
GUI server graphical CDE login screen
Database Applications menu

Click on the INFORMIX icon from the omcadmin CDE desktop to display the Database
Applications menu. The following options are available from this menu.
Install Icon.
Informix.
Other database monitoring utilities can be added using the CDE desktop controls.
68P02901W19-S
2-19
Oct 2009
CDE utilities available to either root or omcadmin login
CDE utilities available to either root or omcadmin login
Displaying the root CDE desktop

Use the following procedure to display the root CDE desktop.
Procedure 2-13
1
From the GUI client graphical CDE login screen, as shown in

Figure 2-7, select Remote Login from the Options menu.
Type in the hostname of a GUI server that exists in the /etc/hosts file
of the GUI Client, and click OK.
The GUI server graphical CDE login screen appears, as shown in

Figure 2-8.
Enter the username root and password, then click OK to display the
root CDE desktop.
Figure 2-9
2-20
Displaying the root CDE desktop
GUI client graphical CDE login screen
68P02901W19-S
Oct 2009
Figure 2-10
Overview of utilities common to root and omcadmin
GUI server graphical CDE login screen
Overview of utilities common to root and omcadmin

The following CDE utilities are common to both a root and an omcadmin login.
Style Manager.
File Manager.
Style Manager
Style Manager can be accessed from the CDE desktop and is used to change desktop attributes
relating to colors, font, backdrop, keyboard click volume, mouse speed, screen lock, window
behavior, and startup preferences to create a customized desktop.
Use the following procedure to open the Style Manager.
Procedure 2-14
68P02901W19-S
Opening the Style Manager
Invoke the Style Manager by entering the command:

/usr/dt/bin/dtstyle
The Style Manager window is displayed.
Click on the icon in the Style Manager window to select the item that
is to be customized.
2-21
Oct 2009
File Manager
File Manager
The File Manager (Figure 2-11), accessed through the CDE front panel, provides a GUI to the
UNIX file system. The File Manager is used to create, find, and use workspace objects such
as files, folders, and applications. Each object is represented by an icon in the File Manager.
File Manager allows the following operations to be performed:
Move, copy, open, and delete objects.
Open an Xterminal.
Change permissions on objects.
Search for an object.
Customize the File Manager View.
Figure 2-11
2-22
File Manager, main window (Home)
68P02901W19-S
Oct 2009
Archiving old OMC-R user files
Archiving old OMC-R user files
Checking home accounts for unmodified files

Use the following procedure to check the home accounts of OMC-R users for files that have not
been modified for the last two weeks.
Procedure 2-15
68P02901W19-S
Checking home accounts of users for unmodified files
Login to the system processor as user root.
Execute the following to select the OMC-R user files that need to be
archived:
find /home -mtime +14 -print > /usr/tmp/listing
The file /usr/tmp/listing may contain a list of user files that need to
be archived or removed from the system. Use the UNIX command
tar to archive the files to tape.
2-23
Oct 2009
OMC software management
OMC software management
This section describes the OMC software management.
Introduction to OMC software management

The OMC-R software is supplied as five standard Solaris packages. These are as follows.
MOTs1900 Software for the Single Platform Processor for 1900 under /usr/omc.
MOTs1900x Software for the Single Platform Processor for 1900.x under /usr/omc/1.9.0.0.x.
MOTc1900 Software for the GUI server for 1900 under /usr/omc.
MOTc1900x Software for the GUI server for 1900.x under /usr/omc/1.9.0.0.x.
MOTh1900x Help files for 1900.x.
The OMC-R software and test objects can be installed, viewed and removed using the swtool
utility, located in /usr/omc/sbin. This utility can be run by any user to view the installed software
releases and test objects. To install and remove software, login as root.
Software loads
To manage OMC-R software loads, execute the swtool utility as the root user. Using the options
available in this menu software can be installed or removed.
The following menu is displayed:
Motorola Software Tool
1. Display software inventory
2. Manage releases
3. Manage test objects
4. Quit
Your choice:
Select the manage releases option.
The following options are displayed:
1. Install a release.
2. Remove a release.
3. Main menu
Your choice:
2-24
68P02901W19-S
Oct 2009
Installing new software
Installing new software

The simplest method of installing new software releases is to choose the Install a release
option from the OMC Releases menu in swtool. Insert the DVD containing the new software
releases in the local DVD drive. The following menu options are displayed:
Install release
1.
Install OMC Software Release and Cutover Machine.
2.
Install OMC Software Release Only.
3.
Cutover.
4.
Done.
Your choice:
If you wish to install the software and cutover in a single step, select Install OMC Software
Release and Cutover Machine. Otherwise, select Install OMC Software Release Only.
When prompted for the path of the software, you can select the default option since the software
is normally installed from the DVD in the local DVD-ROM drive.
The relevant software packages for the system are then installed. If cutover is selected, the
cutover script is automatically executed once the software installation is complete. Note that
this causes an outage for the duration of the cutover.
Removing old software

It is important to delete old releases and retain only a few requisite software releases.
NOTE
Old software releases should no longer be removed using the rm command. The
swtool utility should be used.
From the OMC Releases menu in swtool, select the Remove a release option.
1900.16.
1900.17.
1900.18.
None.
Remove which release?
Select the release to be removed.
NOTE
A current release cannot be removed.
If a software release is removed, associated test objects, if any, are automatically removed.
68P02901W19-S
2-25
Oct 2009
Test objects
Test objects
The OMC software is supplied as Solaris packages, therefore the majority of test objects are
supplied as Solaris patches. Execute the swtool utility as user root. A menu similar to the
following is displayed.
NOTE
Read the relevant release notes for each test object for details about installation or
removal, such as whether the OMC needs to be stopped during the installation.
Motorola software tool

1.
Display software inventory.
2.
Manage releases.
3.
Manage test objects.
4.
Quit.
Your choice:
Select the Manage test objects option.
The following options are displayed:
Test objects
1.
Install a test object.
2.
Remove a test object.
3.
View test object history.
4.
Show files in a test object.
5.
Main menu.
Your Choice:
Installing the test objects

From the Test objects menu in swtool, select the Install a test object option. The following
prompt is displayed:
Install test object from which directory?
[/].
When prompted, enter the directory containing the test object (TAR) file. A menu is displayed
containing all the test objects available in that directory. Select the correct test object. The
selected test object is installed automatically. It is assumed that the object is relevant to the
system Single Platform Processor or GUI server on the correct load.
2-26
68P02901W19-S
Oct 2009
Test objects
Removing the test objects

From the Test objects menu in swtool, select the Remove a test object option. A menu is
displayed containing all the test objects installed on the system. Select the correct test object
to remove it automatically.
Test object history

From the Test objects menu in swtool, select the View test object history option. A screen is
displayed with a history of all the test objects installed on and removed from the system using
swtool, along with the date and time at which the action was taken.
Files modified by a test object

From the Test objects menu in swtool, select the Show files in a test object option. A menu
appears displaying all the test objects installed on the system. Select a test object to view all
the files the test object modifies.
68P02901W19-S
2-27
Oct 2009
Cleaning up OMC-R software loads
Reasons for cleaning up OMC-R software loads

The directory /usr/omc on the system processor contains the OMC-R application software load
currently running on the OMC-R. There may be two OMC-R application software loads in this
directory, the current software load and the previous software load.
If too many OMC-R application software loads are stored in /usr/omc, the file system becomes
full and the cutover script used to cutover to a new OMC-R software load may fail.
If the /usr/omc/sbin/cutover script fails to execute correctly and the /usr/omc file system is
over 85% full, the script produces an error message.
If the /usr/omc file system is over 80% full, the script produces a warning message. The
operator can then decide whether or not to continue with the script.
To avoid the file system becoming full and to ensure that the cutover script runs correctly,
clean up the /usr/omc directory regularly.
Keeping software loads

Use the following procedure to keep software loads on the system processor.
NOTE
This procedure must not be used with the current software load.
Procedure 2-16
2-28
Keeping software loads on the system processor
Login as the user root.
Enter the following commands on the system processor.

cd /usr/omc
tar cvf <tarfilename.tar> <omcloaddirectory>
where
<tarfilename.tar> is the name of the new tar file.
<omcloaddirectory> is the name of the OMC-R software load, for
example, 1.8.0.0.x.
Enter the following commands:

compress <tarfilename.tar>
rm -rf <omcloaddirectory>
Move the tar file to a file system with sufficient storage space.
68P02901W19-S
Oct 2009
Using a tarred software load

Use the following procedure to use a tarred OMC-R software load.
Procedure 2-17
68P02901W19-S
Login as the user root.

mv /<pathname>/tarfilename.tar.Z /usr/omc
where
<pathname> is the directory path name the tar file is stored.

cd /usr/omc
uncompress <tarfilename.tar.Z>
tar xvf <tarfilename.tar>
rm tarfilename.tar
2-29
Oct 2009
NE database maintenance
Login id for NE database maintenance

All procedures relating to NE database maintenance should be carried out while logged into the
system processor as omcadmin.
Archiving and removing a NE database

Before a NE database is removed from the file system, it should be archived. Use the following
procedure to archive to a DAT tape drive, entering the commands in sequence.
Procedure 2-18
1
Archiving the NE database to a DAT tape drive

cd $OMC_TOP/ne_data/dbroot/ne_type/ne_specific/ne_name
where: ne_type is the NE type,
for example, BSS or RXCDR, ne_specific is either BSS-specific or
RXCDR-specific, ne_name is the name of the NE database directory,
for example, bss1.

tar cvf /dev/rmt/0 db_name/*
where db_name is the name of the NE database directory, for example,
db920913171522/*.
When the database has been archived to tape, it can be removed using
the following command:
rm -r db_name
Maintaining NE raw statistics

All procedures relating to raw statistics maintenance should be carried out while logging into
the system processor as omcadmin.
Part of the procedures to be performed on a daily basis is to check if any raw statistics have
escaped processing by the parser.
NOTE
Avoid submitting several files simultaneously for manual processing, as this may
adversely affect automatic processing.
2-30
68P02901W19-S
Oct 2009
Removing NE fallback software load directories
Procedure to submit files to the parser

Use the following procedure to manually submit raw statistics files to the parser.
Procedure 2-19
Submitting raw statistics files to the parser
Login using login id omcadmin.
Check if any raw statistics files have escaped processing by the parser
by entering the following command (typed as a single line).
/bin/find $OMC_TOP/ne_data/raw_stats/100,0 -name *.*
-mtime +1 -print > /usr/tmp/parser_list
If this command does not produce any output it means that none of the
old statistics files have escaped processing.
Files which do not have a suffix of bad_header, failed_load or

no_db_storage, should be submitted one at a time, using the following
command:
$PM_ROOT/bin/pm_manual_parse filename
where filename is from the parser list.
If the utility does not succeed in sending the supplied filename to the parser, an appropriate
error message is displayed on the screen. The speed of parsing depends on the time of day that
the command is executed.
For more information, refer to Database utilities on page 8-4.
Removing NE fallback software load directories

Use the following procedure to remove a NE fallback software load directory, entering the
commands in sequence.
Procedure 2-20
Removing a NE fallback software load directory
Login using login id omcadmin.
Enter the following:

cd $OMC_TOP/ne_data/dbroot/ne_type/ne_specific
where: ne_type is the NE type,
for example, BSS or RXCDR, ne_specific is either BSS-specific or
RXCDR-specific.

rm -r specific_fallback_load_dir
where specific_fallback_load_dir is the name of the fallback directory
to be removed.
Manual parsing of statistics checklist

Follow the procedure (Table 2-2) to manually parse statistics files. Copy the checklist provided
in Table 2-2 to record the checks.
68P02901W19-S
2-31
Oct 2009
Table 2-2
Serial
number

Method
Check
Check that the parser

process is running.
As user omcadmin execute the following command:

ps -elf | grep + | grep Parser
Check that the FMPATH

environment variable is
set.

echo $FMPATH
This environment variable should be set to:
Check if any raw statistics

files have escaped
processing by the parser.
As user omcadmin execute the following commands:

/bin/find $OMC_TOP/ne_data/raw_stats/100,0
-name *.* -mtime +1 -print >
/usr/tmp/parser_list
Submit any files found by

the find command that
do not have a suffix of
bad_header, failed_load,
or no_db_storage one at
a time to the parser.

$PM_ROOT/bin/pm_manual_parse <filename>
Check for any error messages from the
pm_manual_parse utility.
Where .bad_header
files exist, verify
the setting of the
PM_HOURLY_STATS
environment variable.
This variable must be set
to either ON or OFF to
match the setting of the
BSS.

cd /usr/omc/config/global
Using the vi editor, edit the OMC.CNFG file.

Uncomment the setting for PM_HOURLY_STATS and
alter the environment variable so it looks like either
of the following, depending on the requirement at the
BSS:
PM_HOURLY_STATS=ON
Or:
PM_HOURLY_STATS=OFF
Save and exit the file, then execute the following
command as user omcadmin:
omctool -m PARSER_1 -c
Then execute the following commands for all files
with a bad_header extension:
mv <filename>.bad_header filename
pm_manual_parse filename
Continued
2-32
68P02901W19-S
Oct 2009
Table 2-2
Manual parsing of statistics checklist (Continued)
Serial
number
Method
Check
NOTE
This workaround only temporarily sets the
value of PM_HOURLY_STATS. If an omc
stop and start is performed on the system,
this change is overwritten.
To make the change a permanent
one, set the value of the
PM_HOURLY_STATS variable in the
/usr/omc/config/global/pmProcConfig.csh
file.
6
Check that the manual

parse was successful.

tail -f $SYS_LOG/fpomcaudit<yyyymmdd>
Successful parsing output is shown in Parsing
Output.
If the Parser process fails

and is restarted, check
whether the statistics
collection and parsing
operation resume without
manual intervention.

tail -40 $SYS_LOG/fpomcaudit<yyyymmdd>
The log file shows that files are being parsed again
successfully.
Check that the

fpomcaudit log file is
rolled over and that old
logfiles are removed
successfully by the
maintain_script cronjob.

cd /usr/omc/logs
ls -l fpomc*

If the
parserDisconnectedTooLongcd /usr/omc/current/sbin
db_disconnect
alarm is raised then
connect parser
the parser must be
connected to the
database.
10
Monitor the value of

the neighbor statistics
Refer to Using neighbor statistics on page 13-91

in Chapter 12 for further details about raising the
maximum limit of neighbor statistics.
Parsing Output
20050405000016
(22027) FP : File added to Parser List. 20050405000016
FP : FILE HEADER : NE Type 31 : NE Id 1 : Time 2005-4-4

1900 : V 1900 20050405000016
complete. 20050405000017
20050405000017
(22027)
23:30:0:825 : Duration
(22027) FP : UNL preparation for current statsfile
(4701:1) PML: PM_I_PARSFILE_MSG received.
(4701:2) PML:
BIN File /usr/omc/ne_data/raw_stats/100,0/31,1/1
68P02901W19-S
2-33
Oct 2009
- 23:30:0-4:4:
2005 Loading started. 20050405000034
(4701:9) PML: BIN File /usr/omc/ne
_data/raw_stats/100,0/31,1/1- 23:30:0-4:4:2005 Loading completed. 20050405000034

(4701:9) PML: BIN File /usr/omc/ne_data/raw_stats/100,0/31,1/1- 23:30:0-4:4
:2005 deleted
20050405003016
(22027)
FP : File added to Parser List. 20050405003016 (22027) FP :

FILE HEADER : NE Type 31 : NE Id 1 : Time 2005-4-5
V 1800 20050405003016
0:0:0:825 : Duration 1800 :
(22027) FP : UNL preparation for current statsfile
complete.
20050405003017
(4701:1) PML: PM_I_PARSFILE_MSG received 20050405003017
(4701:2) PML: BIN File /usr/omc/ne_data/raw_stats/100,0/31,1/1- 0:0:0-5:4:2005

Loading
started. 20050405003034
(4701:9) PML:
BIN File /usr/omc/ne_data/raw_stats/100,0/31,1/10:0:0-5:4:2005 Loading completed. 20050405003034
(4701:9) PML: BIN File
/usr/omc/ne_data/raw_stats/100,0/31,1/1- 0:0:0-5:4:2005 deleted.

See Database utilities on page 8-4 in Chapter 8 for further details of the pm_manual_parse utility.
2-34
68P02901W19-S
Oct 2009
Printing current OMC-R processes
Printing current OMC-R processes
Overview of printing OMC-R processes

When the OMC-R software has been installed and is running correctly, a printout of the
processes running on both the system and GUI processors should be made.
Procedure to print OMC-R processes

Use the following procedure to produce files of processes on the system and GUI processors:
Procedure 2-21
68P02901W19-S
Producing files of processes on System and GUI processors
Enter the following command to obtain printable files of processes:

ps -elf > filename
To print a file enter the following command:

lp filename
2-35
Oct 2009
Security overview
Security overview
Overview of the OMC-R system security

The following sections provide technical descriptions of the security management considerations
of the OMC-R system.
The security of the OMC-R system is the responsibility of the system administrator, who should
pay particular attention to the following:
The number of users on the OMC-R system.
NOTE
The number of users supported by the OMC-R at any time is 200. The OMC-R
cannot support more than 200 users.
Whether users require special privileges (for example, login id omcadmin), normal
OMC-R software access (for example, group id omc), or restricted OMC-R software access
(for example, group id omcread).
The regular update of OMC-R user passwords.
Any network file that contains security-related information (for example, .rhosts file).
Tape archiving and backup procedures, including the storage of all tapes.
Checking for unauthorized access to the OMC-R system through the X.25 or LAN interfaces.
Ensuring that the remote X terminals have screen lock enabled.
Ensuring that all remote X terminals have a unique local configuration file setup.
As part of GSR9, the system has been made more secure by default. This means certain services
may have to be manually re-enabled to re-introduce functionality which was previously relied
upon. For example, the netstat function is disabled in GSR9; to use the function turn it on
manually.
Services
A summary of the changes is listed as follows. The text in brackets details some of the files and
settings affected by the changes.
2-36
Enabled connection logging (inetd connections, /var/log/connlog).
Enabled ftp connection logging.
Disabled sendmail (except for local mail).
68P02901W19-S
Oct 2009
Services
Disabled public tty access (mesgn).
Disabled root ftp access (/etc/ftpd/ftpusers).
Disabled root login (unless on console).
Restrict cron, at (/etc/cron.d/cron.allow /etc/cron.d/at.allow).
Limit valid shells (/etc/shells).
Improved TCP sequence numbers (TCP_STRONG_ISS=2).
Log failed logins (SYSLOG_FAILED_LOGINS=0).
Network stack tweaks (ip_ignore_redirect, ip_forward_src_routed, ip_respond_to_timestamp, and many more).
Disabled any unused services (finger, spray, apache, etc).
NIS no longer mandatory.
ssh available for use.
A list of standard Solaris 10 services which are disabled by default by the Solaris 10 OMC-R
install is as follows:
power
S75seaport
autofs
S76snmpdx
rpc_udp
S77dmi
rpc_tcp
S82initsma
rpc_ticotsord
S90samba
ktkt_warn
login - rlogin
rusers
login - eklogin
rstat
login - klogin
gss
rexec
rquota
kshell
ipp-listener
shell
rfc1179
finger
S42nackmod
telnet
S47pppd
ftp
S73cachefs_daemon
rpc - rusers
S90webm
rpc - rstat
S90webconsole
rsh
S50apache
To view a complete list of the services that are operational, run the following command as
user root:
svcs
68P02901W19-S
2-37
Oct 2009
Enabling and disabling services
To view a complete list of services, including disabled services, run the following command as
user root:
svcs -a
NOTE
If a service is labeled lrc as shown in the following example, it implies that the service
is not managed under the Solaris10 Service Management Facility. Stop and start the
service by running the script by passing a start/stop parameter. :
legacy_run
15:03:14 lrc:/etc/rc2_d/S87x25net
. Using the S87x25net example shown to start the service, run the following as user
root:
/etc/rc2_d/S87x25net start
Enabling and disabling services

If a particular service (for example, such as sendmail) is required, it can be re-enabled by
performing the following steps as user root:
svcamd enable <service>
Where
Is
service
the name of the service to be

enabled.
This restarts the service and configure it to start automatically on boot-up. Similarly, to disable
a service, perform the following as user root:
svcamd disable <service>
This stops the service and prevent it from automatically starting on boot-up.
Other security changes

In addition to the disabling of many services, other changes have been made in GSR9 as follows:
2-38
Root can only log in directly through console (not directly through telnet).
Root cannot ftp into the box.
System accounts locked.
/etc/shells file limits valid shells.
Extra connection logging (in /var/adm/messages, /var/adm/loginlog, /var/log/authlog

and /var/log/connlog).
68P02901W19-S
Oct 2009
Network stack tuning.
Stack exec protection.
Cron and at job access limited.
68P02901W19-S
Other security changes
2-39
Oct 2009
Controlling user activity on the system
Controlling user activity on the system
Login IDs for system control

To control all user activities on the OMC system, the system administrator should use three
different login IDs as follows:
Login id root
Superuser root can access all files within a particular UNIX system, regardless of their
ownership, protection or grouping.
The root owner can control, edit, or manipulate any other user of that UNIX system. In
particular, the root owner can delete any file on any of the processors file systems.
The system processor has a designated root owner with an associated password and all
other SPARC-based processors have a designated root owner with a different password.
The passwords must be changed regularly.
The login id root should only be used by the system administrator.
Login id omcadmin
The login id omcadmin is set up with the same user id on all processors.
This login id is the owner of the OMC software, and usually runs the OMC activities. This
user is able to remove the OMC software.
The home directory for omcadmin follows the same path as all the OMC users (/home)
and belongs to the group omc.
The login id omcadmin is used by both the system administrator and the OMC Operator.
It is the responsibility of the system administrator to change the omcadmin passwords.
Login id informix
2-40
The login id informix is the owner of the OMC Relational Database Management System
(INFORMIX).
Database administration is performed using the informix login id on the system processor.
The home directory for informix is /usr/informix, and its group id is informix.
The login id informix is only used by the system administrator.
68P02901W19-S
Oct 2009
System security
System security
It is important to restrict the number of personnel that use and know the passwords of the
login ids:
root.
omcadmin.
informix.
Any number of OMC users with an individual login id can be added to the system. The group
id given to OMC users can either be omc or omcread. OMC users in the group omc can
perform all the usual network operator tasks, whereas OMC users in the omcread group can
only perform non-destructive tasks.
68P02901W19-S
2-41
Oct 2009
Controlling user passwords
Controlling user passwords
Overview of controlling user passwords

The system administrator maintains control of the number of users who have access to the OMC
system, and is responsible for controlling user passwords and issuing guidelines for selecting
sensible passwords.
User passwords
User activity on the OMC system is controlled by issuing passwords to each login user. This is
particularly important for controlling access to the OMC using the following login ids: root,
informix and omcadmin.
When installing a new user on the system, the user's real name should be entered. Passwords
should be altered at regular intervals and OMC users should be made aware that their login
directory paths can be changed.
NOTE
The login id omcadmin is used by both the Operator and the OMC system
administrator.
Password conventions
Passwords chosen by the user should follow certain guidelines to maintain security on the
system.
Password naming conventions should be as follows:
Passwords should be at least six characters in length, and should include digits and/or
punctuation marks.
Monthly password changes are recommended.
Users should be discouraged from any of the following practices:
2-42
Matching anything in the user's UNIX account information, such as login id.
Matching anything in the spelling dictionary of the system.
Having three or more repeated characters, for example, aaa.
68P02901W19-S
Oct 2009
Packet Switch passwords
Packet Switch passwords

The password of the Packet Switch is the responsibility of the system administrator. The
process of setting or changing the Packet Switch password is described in the manufacturer's
documentation.
68P02901W19-S
2-43
Oct 2009
Network file security
Network file security
Controlling access to network files

Certain security measures must be taken to ensure that no unauthorized access is made through
the following software:
Transmission Control Protocol/Internet Protocol (TCP/IP).
Network File System (NFS).
File Transfer Protocol (FTP).
Figure 2-12 shows how different software packages are secured to avoid unauthorized access.
Figure 2-12
Software security through Remote Execution and NFS
Network File System (NFS)

The Network File System (NFS) permits several hosts on a network to share files over the
network. NFS is used by the OMC-R software to remotely mount the Event Log file system
onto GUI processors. It can also be used to remotely mount any other file system. The file
/etc/dfs/dfstab lists the file systems that can be accessed by other hosts with NFS.
The /etc/dfs/dfstab file on the system processor and the /etc/vfstab file on other SPARC based
processors, list local file systems that can be accessed by other hosts on the network with
NFS capabilities.
The .rhosts file should only contain entries for hosts on the local OMC-R network.
2-44
68P02901W19-S
Oct 2009
Installing OMC-R Help
Installing OMC-R Help
The English version of the OMC-R Help is automatically installed as part of the Clean Install, as
a package of the form MOTh1900xx where xx indicates the point release of the load installed.
68P02901W19-S
2-45
Oct 2009
Capacity control
Capacity control
Overview of capacity control

The capacity control feature warns the user when the number of Radio Transceiver Functions
(RTFs) in the OMC-R exceeds the number purchased, by displaying an alarm GUI error dialog
box. This ensures that operators are aware of the additional hardware and/or software licenses
required to support further traffic channels.
RTF is used as a measurement instead of TCH because it is a more accurate measure of the
capacity of the system.
Capacity control mechanism

An OMC-R can support only a particular number of RTFs, the RTF limit. RTFs are used to
measure system capacity in preference to radios because there may be redundant radios that
are not counted in the RTF total. TCHs are also not a reliable measure of capacity because their
number may change dynamically, and there is no easy way to calculate a reliable total. The
OMC-R has a threshold RTF value of 90 percent of the RTF limit. The RTF limit is set during
staging and can only be modified with the assistance of Motorola. If the limit is changed, the
new limit comes into effect immediately with subsequent effect on any related alarms.
The OMC-R checks the number of configured RTFs when an RTF is being created. If this number
exceeds the threshold RTF value, but does not exceed the RTF limit, a major severity alarm is
generated. A critical alarm is generated if the value exceeds the RTF limit. This check is also
performed during OMC-R startup. The alarms are only generated the first time the threshold
is exceeded. If the number of configured RTFs either falls below the limit or threshold values
when an RTF is deleted, the alarm is changed to major severity or cleared, respectively.
If the number of configured RTFs exceeds the OMC-R RTF limit, a dialog box to this effect is
displayed. This dialog box informs the user that the OMC-R is exceeding its licensed RTF
capacity. This dialog box does not affect OMC-R operation, but the user has to confirm this
dialog box once every hour while the RTF limit continues exceed the OMC-R RTF limit.
Feature Capacity Licensing and Audit

The Licence Audit tool monitors the usage of carriers across the network on a per feature basis.
Information is gathered by running scheduled audits against the OMC-R CM database to produce
a report indicating the number of RTFs equipped in the database to support each feature.
The audit is triggered by a configurable interval parameter in the OMC software. If the interval
parameter is not set, or set outside the permissible range of 2 to 48 hours, the default value of
12 hours is used. The result of the audit (actual usage) is compared with the license file per
feature. An alarm is generated for each feature where the license usage is exceeded. If the
usage is within the limit, the Licence Audit Tool generates a corresponding event. The alarms
and events are displayed at one or all OMCs in the network, as configured during installation.
2-46
68P02901W19-S
Oct 2009
Licence violation alarms
Licence violation alarms

The following alarms are produced in the case of license violation:
30039 OMC-R Capacity Ceiling Violation, too many NEs in MIB Critical
30038 OMC-R Capacity Ceiling Violation, too many RTFs in MIB Critical
LicenseAuditNotAvailableAlarm Critical
LicenseFileNotAvailableAlarm Critical
LicenseViolationAlarm Critical
NOTE
If any of the above mentioned alarms occur, inform the Motorola support group.
Updating RTF license limit

To execute the following procedure, the parameters originally provided by Motorola are needed
and they are listed as follows:
Encryption Key
RTF Ceiling limit
Licence issue date
Licence checksum
If the above parameters have been mislaid, contact sysdep_cro@ecid.cig.mot.com for further
information.
Use the following procedure to update the RTF license limit.
Procedure 2-22
Updating the RTF license limit
Login as root on the system processor and remove the old license file:
rm /opt/omc/license_tools/license_file
Obtain the lmgrp.omc process id number:

ps -ef | grep lmgrd.omc
Terminate the lmgrp.omc process:

kill -15 <lmgrd.omc pid number>
Continued
68P02901W19-S
2-47
Oct 2009
Updating RTF license limit
Procedure 2-22
4
Updating the RTF license limit (Continued)
Start the OMC License Administration Tool:

/usr/omc/current/sbin/populate_license
The following window is displayed:
======================================================
OMC License Administration Tool
------------------------------1.
Invoke New License
2.
Quit
======================================================
Enter Option:
5
Enter 1 to invoke New License option.
Enter the encryption key when prompted, for example, 86B0997EFF9.
Enter the new updated RTF Licence limit, when prompted, for example,
1000.
Enter NE limit, for example, 128.
Enter the Licence issue date, when prompted, for example,

23-Oct-2003.
10
Enter the checksum when prompted, for example, 131. The following
output is displayed: Are you happy with these entries [y/n]?
11
Enter y if all entries are acceptable.

The following output is displayed: Modifying the license_example
file
Copying license_file to /opt/omc/license_tools/license_file
NOTE
For Feature Capacity and Licensing, the licensed capacity for every feature that can be licensed is
updated through the License Administration Tool by executing the following script:
/usr/omc/current/sbin/populate_license g
This invokes a GUI interface. For specific details on configuring licenses with this tool, please
refer to System Information: License Audit (68P02901W59).
2-48
68P02901W19-S
Oct 2009
Restartable processes
Restartable processes
Restartable and non-restartable processes

Processes running on the OMC-R are divided into two categories after startup:
Restartable.
Critical (non-restartable).
A restartable process is a process which is restarted automatically if it fails. If a restartable

process exits suddenly, or hangs, it is restarted without operator intervention.
A critical process is a process which must start correctly before the OMC-R can continue to
start up and remain running. If a critical process fails, the entire OMC-R is restarted. The
following processes are critical processes:
em_main.
em_lm_main.
cm.
nameserver.
NOTE
An automatic OMC-R restart does not take place if the nameserver critical process
fails. If this process fails, it is necessary to perform a manual OMC-R stop or start.
Restarting processes
The OMC-R attempts to start failed restartable processes indefinitely. On the first failure, a
restart is attempted immediately. If this does not restart the process, five further attempts will
be made at intervals of 150 seconds and thereafter every 900 seconds.
This enables the OMC-R to cope with processes that cannot be restarted without operator
intervention, as well as with processes that may recover after longer intervals.
If a critical (non-restartable) process fails, then the entire OMC-R is restarted automatically.
GUIs will need to be restarted if the entire OMC-R restarts, or if certain other processes are
restarted.
Any process that fails may lose operations that were in progress when it failed. For example,
if the RLogin process stops and restarts, current remote login sessions will be disconnected
and will need to be reconnected.
The command line utility omctool is provided to enable the OMC-R system administrator to
forcibly restart a process.
68P02901W19-S
2-49
Oct 2009
Messages in the OMC-R console and audit log
NOTE
This utility should only be used under the direction of Motorola.

All GUI users will see messages displayed on the console as processes restart. In some cases,
operations and/or the entire GUI has to be restarted.
The OMC-R keeps a record of all failed processes in the omcaudit file. The OMC-R system
administrator can investigate what has gone wrong by examining this file.
NOTE
Statistic file uploads are automatically retried.
Process dies
When a process is dying, or has died, the console displays a message similar to the following:
Thu Dec 11 15:04:17 2003 - WARNING: An OMC
Process Has Died. It will be Restarted - NAME
or
Thu Dec 11 15:04:17 2003 - WARNING: An OMC
Process Has Died - NAME
If the process is restartable, then the operator should monitor the console to confirm that
the process restarts.
If the process is critical, all GUIs will have to be restarted when the OMC restarts. If a GUI
restart is necessary, users are notified that the GUI has been disconnected from the system
processor when they try to use it.
The OMC-R system administrator should examine the omcaudit log files. If the logs contain
several regular entries indicating that there is something wrong with the operation of this
process, the OMC-R system administrator should attempt to determine the cause.
2-50
68P02901W19-S
Oct 2009
Process restarts
When a process is restarted, the console displays a message similar to the following:
Thu Dec 11 15:04:18 2003 - NOTE: An OMC Process

Has restarted - NAME
The user should ensure that the process restarts successfully by examining the console.
The OMC system administrator should also examine the omcaudit log to see why the process
died in the first place. The omcaudit file contains an entry similar to the following:
2003-12-11 15:04:18 (20005) [OMCINIT] NAME has restarted
Critical processes start successfully

If critical processes have been started but other processes did not start, the OMC-R system
administrator should examine the omcaudit log files to determine which processes did not
start and what is wrong with them.
Depending on which processes did not start, certain operations may fail. For example, if RLogin
fails to start, then the remote login functionality is unavailable.
System shuts down

When the OMC-R system shuts down the console displays a message similar to the following:
Thu Dec 11 10:10:41 2003 - WARNING: OMC Processes Have Been Shutdown
If the shutdown is due to the death of a critical process rather than an administrator request to
shut down, the OMC-R should restart automatically.
Process fails to respond to a periodic health check

The OMCINIT process periodically polls other processes to make sure they have not hung.
When a process fails to respond to polling the console shows the following message:
Thu Dec 11 15:53:46 2003 - WARNING: An OMC Process is not

responding to Polling - NAME
If the process is restartable, then only that process is restarted. The OMC-R system
administrator should check that the process is shut down and restarted, and ensure that this
message does not continually repeat.
If the process is critical, then the entire OMC-R is shut down and restarted. The OMC-R system
administrator should check that the OMC-R is restarted and remains up.
68P02901W19-S
2-51
Oct 2009
OMC-R starts successfully

If all OMC-R processes have started successfully, GUIs can be restarted.
PM proxy cannot access PM database

If the PM proxy cannot access the PM database, a message similar to the following is displayed
on the console:
Thu Dec 11 12:12:16 2003 - WARNING: PMproxy unable to access PM Database
This message is unlikely to appear. If it does appear, report the problem to Motorola.
ResyncCtrl dies during a resync

If the ResyncCtrl process dies, any currently active resyncs are aborted and the process is
restarted. A console message appears, warning that ResyncCtrl has died and is being restarted.
The user may restart aborted resyncs when the ResyncCtrl process restarts.
Event Interface dies

If the Event Interface EVTIF dies, connections are dropped. The console displays a warning
message that this process has died and is being restarted. The NE should reconnect when
the Event Interface restarts.
Event Interface dies during a resync

If the Event Interface dies, any currently active resyncs will fail because the BSS cannot
communicate with the OMC-R. The console displays a warning message that the Event Interface
has died and is being restarted.
The user may restart the failed resync when the Event Interface process restarts.
Event Interface dies during an audit

If the Event Interface dies, any currently active audit is aborted. The console displays a warning
message that the Event Interface has died and is being restarted.
The user may restart the aborted audit when the Event Interface process restarts.
2-52
68P02901W19-S
Oct 2009
Uploader dies during an upload

If the uploader dies, current uploads are aborted. The console displays a warning message that
the uploader has died and is being restarted.
If the uploader dies during an active upload, a message box appears in addition to the console
message, warning that the upload IPC channel has been deleted. The upload status window
is closed.
Upload status can be invoked again when the uploader has restarted and any aborted database
uploads have to be restarted manually. Statistics file uploads will be retried automatically.
Downloader dies during a download

If the downloader dies, a console message appears warning that the downloader has died
and is being restarted.
If a download status window is active, a message box appears to inform the user that the
channel has died and the download status window is closed.
Download status can be invoked again when the downloader has restarted. Unlike uploads,
downloads should resume automatically.
Monitor process dies

If the monitor process dies, it terminates its remaining processes and then restarts all
processes under it. The monitor process itself is restarted by OMCINIT.
GUIs will have to be restarted manually.
A console message appears stating which monitor process has died. A message box also
appears informing the user that the system processes have died and the GUI should be restarted
when the processes have been restarted.
When the processes are restarted, a message appears on the console to inform the user. The
user must then restart the GUI.
Event Manager dies during alarm or event display

If the Event Manager dies due to event overload, this is reported in a console message. If
alarm or event windows associated with this EM channel are open, they will be closed. The
Event Manager is a critical process and all the OMC-R processes will shut down as a result of
this process expiry. The console displays a warning message that the OMCINIT process is
shutting down.
After all the processes have been shut down, all OMC-R processes are restarted. A console
message appears, informing the user to restart the GUI to reconnect to the OMCINIT process.
The user must restart the GUI.
68P02901W19-S
2-53
Oct 2009
EM List Manager dies

The EM List Manager is a critical process. As with the EM, all the OMC-R processes will shut
down if the EM List Manager critical process fails.The console displays a warning message that
this process has failed and OMCINIT is shutting down.
After all OMC-R processes have been shut down, all the processes are restarted. A console
message appears telling the user to restart the GUI to connect to the OMCINIT process. The
user must then restart the GUI.
Configuration Manager dies

The Configuration Manager is a critical process. As with the EM, all of the OMC-R processes
will shut down if this critical process fails. A console message will appear warning that this
process has died and OMCINIT is shutting down.
After all OMC processes have been shut down, all the processes are restarted. A console
message appears telling the user to restart the GUI to connect to the OMCINIT process. Then
the user must restart the GUI.
OMCINIT process dies

If OMCINIT dies, all processes it has started are shut down. The console displays a warning
message that the OMCINIT process is down.
A minder application omcminder then restarts OMCINIT. All OMC-R processes are restarted
and a console message appears warning that the user must restart the GUI to reconnect to the
OMCINIT process. The user must restart the GUI when this message appears.
X.25 processes restart

The X25_BTL1 and X25_BTL2 processes handle downloads. If they die, new downloads will
not be initiated. This corrects itself when the process restarts.
If the X25_EVT1 and X25_EVT2 processes fail, events, audits, and resyncs will fail. When they
restart, NEs should reconnect again, but the user will have to restart audits and resyncs.
If the X25_UPL1, X25_UPL2, X25_UPL3 or X25_UPL4 processes fail, uploads will be
interrupted. Operator initiated uploads (as opposed to statistics) will have to be restarted.
If the X25_RLOG process fails, remote login sessions will have to be restarted after this process
has restarted.
Console messages will appear warning that the X.25 process has died and is being restarted.
Parser process restarts

If the PARSER process fails and is restarted, stats collection and parsing should resume without
operator intervention. A console message appears, warning that the process has died and is
being restarted.
2-54
68P02901W19-S
Oct 2009
omctool utility
FCCHAN process restarts

If the FCCHAN process fails, it will be restarted without operator intervention. A console
message will appear warning that the process has died and is being restarted.
FMMGR process restarts

If the FMMGR process fails, it is restarted without operator intervention. A console message
appears warning that this process has died and is being restarted.
Remote login process restarts

If for any reason a remote login process RLogin should die, it will be restarted. A console
message will appear warning users that this process has died and is being restarted.
If the RLogin process stops and restarts, current remote login sessions will fail and will need
to be retried. The OMC-R system administrator should check for failed batch_rlogin jobs by
examining the output in the /usr/omc/config/global/batch/output log file.
NOTE
If the option to generate log files is selected, only the batch output log file is
generated.
omctool utility
CAUTION
The omctool application should only be used by the OMC system administrator under
the direction of Motorola.
The omctool utility can be used to:
Switch debugging on or off for a process.
Restart a process.
Reconfigure a process.
This utility is used with the following options:

omctool [-p pid] | [-m mnemonic] [-d on/off] | [-r] | [-c]
The process to be adjusted must be specified by either:
Its process ID with the -p option, or
Its mnemonic name (given in STARTUP.LIST) with the -m option.
68P02901W19-S
2-55
Oct 2009
omctool utility
The action to be taken must be specified by:
The -r option to restart the process.
The -c option to reconfigure the process. This causes the OMC.CNFG file to be re-read
and therefore does not require the process to be restarted.
The -d on or -d off option to switch debugging ON or OFF.
The omctool utility should only be used under the direction of Motorola. In particular, the -d
debugging option generates large files and will impair system performance. The information
that it produces is of use to only Motorola engineers.
2-56
68P02901W19-S
Oct 2009
Graceful shutdown on mains failure
Graceful shutdown on mains failure
Graceful shutdown
The optional graceful shutdown feature allows the OMC to survive short interruptions in power
and to shut down gracefully during longer power outages.
The system processor can be powered by a Smart Uninterruptible Power Supply (Smart UPS).
Supporting software runs on the system processor and a serial cable connected to the UPS
delivers status information to it. Any GUI users are warned when the system processor is
switched over to the UPS. When the UPS battery is close to depletion, a further message is sent
to any remaining users. The system is then shut down.
As this feature is optional, the OMC can operate without a UPS installed.
Implementation of graceful shutdown

Graceful shutdown is implemented by the introduction of a set of OMC software scripts.
These scripts are run under the control of the UPS software when certain UPS events occur.
The activation of these scripts is dependent on the UPS and is thus outside the scope of this
description.
Features of graceful shutdown

The graceful shutdown function provides the following UPS support facilities:
The OMC can detect UPS events and generate OMC alarms when these events occur.
The OMC logs UPS events in the system processor audit file.
If the mains power to the UPS fails, the OMC informs all OMC users through the OMC
console window. In this case, the OMC will continue to function normally.
NOTE
Only users who are logged into functioning machines are informed.
68P02901W19-S
When the mains power to the UPS is restored, the OMC informs all OMC users
through the OMC console window that a shutdown is no longer pending.
If the UPS indicates a low battery condition, the OMC will shut down. All users
will be informed that a shutdown is about to occur. Sufficient time is allowed for
this message to reach all active users before the shutdown occurs.
If the operator issues an omc stop command during OMC startup, the OMC
will shut down.
2-57
Oct 2009
UPS setup
UPS setup
To ensure maximum protection for the OMC, the UPS should be configured so that it will not
power up after restoration of mains power until there is enough battery capacity to completely
reboot and shut down the system processor. This ensures that repeated mains failures do not
cause uncontrolled power cuts at the OMC. The system is not powered up until the UPS has
sufficient reserves to permit it to power up the OMC completely and then shut it down again if
the mains supply to the UPS fails during the startup.
2-58
68P02901W19-S
Oct 2009
Configuration and installation of a remote terminal
Configuration and installation of a remote terminal
Introduction to the setup of a remote monitoring terminal

This section describes the installation and configuration of a remote SUN terminal. Remote
terminals may be used simply to monitor a regional OMC-R from a remote location, or for the
purpose of night concentration where several OMC-Rs are monitored from one central point.
Single OMC-R monitoring configuration

The following section describes the configuration of a remote SUN terminal. The single OMC-R
monitoring configuration is illustrated in Figure 2-13. The remote monitoring station is used to
monitor just one regional OMC-R.
Figure 2-13
Single monitoring station configuration
The link protocol between the sites is X.21 which supports the TCP/IP WAN connection. The
bridge or router at the regional OMC-R end may provide several other routes to other routers
or bridges at other sites.
The Sunblade 150 at the monitoring station is configured as a GUI server so that the OMC-R
software executes locally. The same users must be added on the GUI server as are added at the
regional OMC-R. The remote Sunblade 150 must still NFS mount the /usr/omc/config/global,
/usr/omc/ne_data, /usr/omc/ne_data/raw_stats and /home.
68P02901W19-S
2-59
Oct 2009
OMC-R night concentration centre configuration
OMC-R night concentration centre configuration

For large systems that contain multiple OMC-R networks, it is necessary that an operator be
able to hand over management of one network region to another OMC-R during the night shift.
This necessitates the provision of a mechanism to enable single workstation access to multiple
system processors.
Figure 2-14 shows a configuration where the night concentration centre consists of one
Sunblade 150 configured as a GUI server for both region A and region B.
Figure 2-14
2-60
Night concentration centre configuration
68P02901W19-S
Oct 2009
Night concentration overview
Night concentration overview

The following are the requirements for the night concentration centre configuration:
A single workstation configured as GUI server is able to access multiple system processors.
One of these is the operators local OMC-R system. The others are remote OMC-R systems
that are normally monitored at night.
Access to the OMC-R systems is mutually exclusive. The operator has to log out and login
again as a different user to gain access to the remote OMC-R. The remote OMC-R that
the operator accesses, depends on the user that the operator logs in as. Each special
user accesses a specific remote OMC-R which is specified during initial set-up of the
night concentration feature.
Night concentration procedures do not support the use of NIS.
The GUI server used for this feature is unable to support any clients.
A minimum 64 KB digital leased line is required to run the OMC remotely.
Naming conventions for a night concentration centre

The following naming conventions are used when describing the setup of a night concentration
centre:
local_sys: The hostname of the local system processor.
remote_sys: The hostname of the remote system processor.
local_gui: The hostname of the local GUI server processor.
remote_user: The username of the account used to access the remote OMC-R.
Prerequisites for setup of a night concentration centre

The following procedures must be completed before commencing the setup of a night
concentration centre.
The local and remote OMC-R systems must have version GSR9 of the OMC-R software
installed. Refer to Installation and Configuration: OMC-R Clean Install (68P02901W47)
for details.
The hostname and IP addresses of the different processors must be obtained for each
remote OMC-R. It is recommended that the information be entered in Table 2-3 and
Table 2-4.
68P02901W19-S
2-61
Oct 2009
Prerequisites for setup of a night concentration centre
Table 2-3
Hostname and IP addresses for different processors

Hostname
System
IP address
local_sys
remote_sys
local_gui
The Username and User Identifier Number (UID) from the account of the user of the
remote OMC-R system must be obtained. It is recommended that the information be
entered in Table 2-4.
Table 2-4
User name and ID for remote system
Account
User name
UID
Account for user of remote

OMC-R system.
NOTE
Copies of the above tables are provided in Chapter 13. They can be copied
and used to record this information.
2-62
68P02901W19-S
Oct 2009
Remote system processor setup
Remote system processor setup
Introduction to setting up night concentration

This section describes how to set up a remote system processor for night concentration. The
following procedures are outlined:
Updating host file entries.

Describes how to change host file entries.
Exporting file changes.

Describes how to mount certain file systems.
Creation of a new account.

Describes how to create an account to use the remote OMC-R.
Updating host file entries

Each of the remote system processors must contain the hostname of the local GUI server in its
host file, equivalent hosts file, and rhosts file. Use the following procedure to change the files:
Procedure 2-23
68P02901W19-S
Updating host file entries with hostname
Edit the /etc/hosts file on the remote_sys processor and check that
the hostname of the local_gui processor is present. If the entry is
not listed, add a line similar to the following to the hosts file using a
suitable text editor:
<IP address> <local_gui>
Where:
<IP>is IP address of GUI server
<local_gui> is Hostname of the local GUI server.
Edit the /etc/hosts.equiv file on the remote_sys processor and check

that the hostname of the local_gui processor is present. If the entry
is not listed, add a line similar to the following to the hosts.equiv file
using a suitable text editor:
Where:
Once all changes have been made, execute the following commands as
user root:
cd /var/yp
/usr/ccs/bin/make
2-63
Oct 2009
Exporting file changes
Exporting file changes

Use the following procedure to ensure that each of the remote system processors will allow the
local GUI server to mount certain file systems:
Procedure 2-24
1
Setting mount permissions at the GUI server
Edit the /etc/dfs/dfstab file on each of the remote_sys processors and

add the hostname of the local_gui processor to the list of hosts with
mount permissions:
share -F nfs -o rw=sparc0:<local_gui>,root=sparc0:<local_gui>

/home
/usr/omc/ne_data
/usr/omc/config/global
Where:
2
Execute the following command on each of the remote system

processors, as user root:
shareall
Creation of new account

An account must be created to use the remote OMC-R. The account is also created on the
remote_sys processors with the same username and UID as that created on the local machine.
2-64
68P02901W19-S
Oct 2009
Monitor alternative OMC-R from GUI server
Monitor alternative OMC-R from GUI server
Prerequisites for switching to an alternative OMC-R

Before switching to an alternative OMC-R from the GUI server the following requirements
must be fulfilled:
Each system processor on the LAN must be a NIS master (this is standard under the
current supported OMC-R configuration).
The NIS Domain name on each OMC-R on the LAN must be unique.
The maps for each NIS Domain must contain a complete list of all system processor
hostnames on the LAN.
Ensure that the Remote system processor is NFS-sharing the following file systems to
the GUI server.
/usr/omc/config/global
/usr/omc/ne_data
/home
The GUI server must have an entry for the Remote system processor in each of /etc/hosts,
/etc/hosts.equiv.
The Remote system processor must have an entry for the GUI server in each of /etc/hosts,
/etc/hosts.equiv.
68P02901W19-S
2-65
Oct 2009
Switching to an alternative OMC-R

Use the following procedure to switch over to an alternative OMC-R.
Procedure 2-25
Log on to the GUI server root and ensure that there is no GUI running
on the GUI server.
Initially, the GUI server /etc/hosts file should be similar to the following:
127.0.0.1
localhost
111.111.11.12 local_gui
111.111.111.11 local_sys omc_splat omc_pm omc_4gl
111.111.11.14 netprinter
111.111.11.13 guiclient1
111.111.111.21 remote_sys
Edit the GUI server /etc/hosts file so that the remote_sys is aliased to
omc_splat, omc_pm and omc_4gl:
127.0.0.1
localhost
111.111.11.12 local_gui
111.111.111.11 local_sys
111.111.11.14 netprinter
111.111.11.13 guiclient1
111.111.111.21 remote_sys omc_splat omc_pm omc_4gl
3
To switch over to an alternative OMC-R, execute the following

command:
/usr/omc/current/sbin/SwitchSPLAT <remote_sys>
Where:
<remote_sys> is the hostname of the Remote system processor.
NOTE
The GUI server reboots automatically.
2-66
68P02901W19-S
Oct 2009
Removing OMC-R night concentration centre configuration
Removing OMC-R night concentration centre

configuration
Introduction
The procedures in this section describe how to undo the OMC-R night concentration centre
configuration. The procedures listed in Table 2-5 are outlined.
Table 2-5
Procedures to remove OMC-R night concentration configuration
Procedure
Description
Local GUI server rollback
Describes the GUI server file modifications required when

removing the OMC night concentration centre configuration.
Remote system processor

rollback
Describes the Remote system processor file modifications

required when removing the OMC night concentration centre
configuration.
Local GUI server rollback

This section describes the GUI server file modifications which must be made when removing the
OMC-R night concentration centre configuration.
The following procedures are described:
Deletion of the OMC-R remote user account.
Host file changes.
Deletion of OMC-R remote user accounts

Refer to Administering user accounts with usertool on page 2-12 for details on administering
user accounts.
Hostfile changes
Remove references to the remote system processor from /etc/hosts, /etc/hosts.equiv.
68P02901W19-S
2-67
Oct 2009
Remote system processor rollback
Remote system processor rollback

This section describes the Remote system processor file modifications which must be made
when removing the OMC-R night concentration centre configuration. The following files may
have been changed on the Remote system processor:
/etc/dfs/dfstab /etc/hosts.equiv /etc/hosts
The following procedures are outlined:
Export file changes.
Deletion of the OMC-R remote user account.
Export file changes

Edit the /etc/dfs/dfstab file on each of the remote_sys processors. Remove the reference
to the local_gui processor.
Deletion of OMC-R remote user accounts

Refer to Administering user accounts with usertool on page 2-12 for details on administering
user accounts.
2-68
68P02901W19-S
Oct 2009
Setting the locale on the OMC-R
The following procedure demonstrates how the locale on the OMC-R can be changed.
Procedure 2-26
Changing the locale of OMC-R
Execute the following command as user root to display all the supported
locales:
locale -a
Sample out put:
POSIX
C
iso_8859_1
zh_HK.BIG5HK
zh_HK.BIG5HK@radical
zh_HK.BIG5HK@stroke
zh_HK.UTF-8
zh_HK.UTF-8@radical
zh_HK.UTF-8@stroke
zh_TW zh_TW.BIG5
zh_TW.EUC
zh_TW.UTF-8
ja
en_AU
en_AU.ISO8859-1
en_NZ
en_NZ.ISO8859-1
iso_8859_13
iso_8859_15
iso_8859_2
iso_8859_5
es
es_CR
es_CR.ISO8859-1
es_GT
es_GT.ISO8859-1
.
.
iso_8859_7
iso_8859_9
hi_IN.UTF-8
cs_CZ
cs_CZ.ISO8859-2
cz
de
de.ISO8859-15
Continued
68P02901W19-S
2-69
Oct 2009
Procedure 2-26
Changing the locale of OMC-R (Continued)
de.UTF-8
de_AT
de_AT.ISO8859-1
de_AT.ISO8859-15
de_AT.ISO8859-15@euro
de_CH
.
.
de_DE.ISO8859-15@euro
de_DE.UTF-8
de_DE.UTF-8@euro
fr
fr_CH
fr_CH.ISO8859-1
hu
hu_HU
hu_HU.ISO8859-2
pl
.
.
common
zh
zh.GBK
zh.UTF-8
.
.
bg_BG
bg_BG.ISO8859-5
et_EE
et_EE.ISO8859-15
hr_HR
hr_HR.ISO8859-2
.
.
lv_LV.ISO8859-13
mk_MK
mk_MK.ISO8859-5
nr
ro_RO
ro_RO.ISO8859-2
ru
.
.
ru_RU.ISO8859-5
ru_RU.KOI8-R
ru_RU.UTF-8
sh_BA.ISO8859-2@bosnia
sl_SI
Continued
2-70
68P02901W19-S
Oct 2009
Procedure 2-26
.
.
tr
tr_TR
tr_TR.ISO8859-9
tr_TR.UTF-8
en_US.UTF-8
ko
ko.UTF-8
ko_KR.EUC
ko_KR.UTF-8
he
he_IL
he_IL.UTF-8
ar
.
.
en_US.ISO8859-15
en_US.ISO8859-15@euro
es_MX
es_MX.ISO8859-1
fr_CA
fr_CA.ISO8859-1
da
da.ISO8859-15
da_DK
da_DK.ISO8859-1
da_DK.ISO8859-15
.
.
no
no_NO
no_NO.ISO8859-1@bokmal
no_NO.ISO8859-1@nynorsk
no_NY
sv
sv.ISO8859-15
sv.UTF-8
sv_SE
sv_SE.ISO8859-1
sv_SE.ISO8859-15
sv_SE.ISO8859-15@euro
sv_SE.UTF-8
sv_SE.UTF-8@euro
es_AR
es_AR.ISO8859-1
es_BO
es_BO.ISO8859-1
es_CL
Continued
68P02901W19-S
2-71
Oct 2009
Procedure 2-26
.
.
es_UY
es_UY.ISO8859-1
es_VE
es_VE.ISO8859-1
pt_BR
pt_BR.ISO8859-1
ca
ca_ES
ca_ES.ISO8859-1
ca_ES.ISO8859-15
.
.
es.ISO8859-15
es.UTF-8
es_ES
es_ES.ISO8859-1
es_ES.ISO8859-15
es_ES.ISO8859-15@euro
es_ES.UTF-8
es_ES.UTF-8@euro
it
it.ISO8859-15
it.UTF-8
it_IT
it_IT.ISO8859-1
it_IT.ISO8859-15
it_IT.ISO8859-15@euro
it_IT.UTF-8
it_IT.UTF-8@euro
pt
pt.ISO8859-15
pt_PT
pt_PT.ISO8859-1
pt_PT.ISO8859-15
pt_PT.ISO8859-15@euro
th
th_TH
th_TH.ISO8859-11
th_TH.TIS620
th_TH.UTF-8
.
.
fr_BE.UTF-8
fr_BE.UTF-8@euro
fr_FR
fr_FR.ISO8859-1
fr_FR.ISO8859-15
Continued
2-72
68P02901W19-S
Oct 2009
Procedure 2-26
fr_FR.ISO8859-15@euro
fr_FR.UTF-8
fr_FR.UTF-8@euro
nl
nl.ISO8859-15
nl_BE
nl_BE.ISO8859-1
nl_BE.ISO8859-15
nl_BE.ISO8859-15@euro
nl_NL
nl_NL.ISO8859-1
nl_NL.ISO8859-15
nl_NL.ISO8859-15@euro
ar_SA.UTF-8
el_GR.UTF-8
pt_PT.UTF-8
nl_BE.UTF-8
nl_NL.UTF-8
2
As user root, edit the /etc/default/init file and add your chosen locale.
For example:
# @(#)init.dfl 1.5 99/05/26
#
# This file is /etc/default/init. /etc/TIMEZONE is a symlink to
this file.
# This file looks like a shell script, but it is not. To
maintain
# compatibility with old versions of /etc/TIMEZONE, some shell
constructs
# (i.e., export commands) are allowed in this file, but are
ignored.
#
# Lines of this file should be of the form VAR=value, where VAR
is one of
# TZ, LANG, CMASK, or any of the LC_* environment variables.
#
TZ=Eire
CMASK=022
LANG=no_NO
#
68P02901W19-S
As user root, reboot the box by executing the following command:

/usr/sbin/shutdown -g0 -i6 -y
2-73
Oct 2009
General administration checklists
Daily administration checklist

Use the following procedure to perform the daily administration tasks. Copy the checklist
provided in Chapter 13 to record the checks.
NOTE
These procedures must be executed by an experienced Systems Administrator.
Procedure 2-27
Performing daily administration tasks initial checks
Check the file system capacity:

As user root, execute the following command:
df -k
Ensure that all necessary file systems are mounted, and that the
capacity does not exceeded 90%. If the file system exceeds 90%, it is
advisable that the file system is cleaned up.
Check the disk usage capacity of the system: by entering the following
command as user root:
du | more
Terminate processes that are not required and are unnecessarily
consuming disk capacity. Also use the output of this command to check
for rogue processes running on your system.
Check the output of cron jobs from users root, omcadmin, and sys.
As user root examine the output from the cron jobs in the following
files for errors/messages:
more /var/mail/omcadmin
more /var/mail/root
more /var/mail/sys
Investigate the cron jobs that appear to be troublesome.
Check the omc_db_maint log file to ensure that:
PM statistics are unloaded and deleted successfully.
Disk space is not being consumed.
Applications are connected and reconnected successfully.
PM Fragments are created for the next days statistics.
As user root execute the following commands:

cd $OMC_TOP/logs
more omc_db_maint.yyyy.mm.dd
Continued
2-74
68P02901W19-S
Oct 2009
Procedure 2-27
Performing daily administration tasks initial checks (Continued)
Check the IDS log files for both PM and MIB INFORMIX DB errors and
checkpointing:
tail -f $INFORMIXDIR/online.log_OMC
tail -f $INFORMIXDIR/online.log_MIB
These log files should show that checkpoints are completed successfully
and in particular when the server is initialized.
Check that the PM database is online by entering the following

commands as user omcadmin:
omc_env
onmonitor
Check that the CM database is online by entering the following

mib_env
onmonitor
Procedure 2-28
68P02901W19-S
Performing daily administration tasks creating backups
Perform a Level 2 backup of the PM database.
Perform a Level 2 backup of the CM database.
Perform a backup of the UNIX file system.

Check the status of the disk mirroring and ensure that all sub-mirrors
are in an Okay state, by entering the following commands as user root:
metastat | more
Refer to Checking disk mirroring on page 13-47.
Check the OMC-R log files in /usr/omc/logs for unusual output or error
messages. Refer to OMC-R log and error files on page 4-3.
Check the integrity of X.25, by entering the following commands as

user root:
/opt/SUNWconn/bin/x25stat
Refer to x25stat output on page 2-76.
Check the system processor hardware, by entering the following

/usr/platform/sun4u/sbin/prtdiag -v
Manually parse any unparsed statistics files. Refer to the Checklist

Manual parsing of statistics in NE database maintenance on page 2-30.
2-75
Oct 2009
x25stat output
The following is an example of the output from x25stat:
GLOBAL STATISTICS FOR X25
------------------------------------Packet type
TX
RX
------------------------------------Call
Call accept
Clear
Clear Confirm
138
10
128
129
16
16
129
Restart
Restart confirm
RNR
1119
12536
Resets
RR
Reset confirms
Diagnostic
Interrupts
Registration
Reg confirm
Packets (total)
Bytes (total)
18126
3124
1783971
207183
------------------------------------Running totals
------------------------------------Tot no of VCs established
2-76
135
Connections refused
Connections currently open
Max connections open
68P02901W19-S
Oct 2009
prtdiag output
The following is an example of the output from prtdiag:
System Configuration:
Sun Microsystems
sun4u 5-slot Sun Enterprise
System clock frequency: 100 MHz

Memory size:
512Mb
========================= CPUs =========================

Run
Ecache
CPU
CPU
Brd
CPU
Module
MHz
MB
Impl.
Mask
---
---
-------
-----
------
------
----
400
8.0
US-II
10.0
400
8.0
US-II
10.0
14
400
8.0
US-II
10.0
15
400
8.0
US-II
10.0
=========================Memory =========================
Intrlv. Intrlv. Brd
---
----
Bank
MB
Status
---------
Condition
-----
------
Speed
--
------
256
Active
OK
60ns
2-way
256
Active
OK
60ns
2-way
Factor
With
-----
========================= IO Cards =========================

---
Bus
Freq Brd
----
----
Type
MHz
----------
Slot
Name
----------------------------
Model
--------------------
SBus
25
cgsix
SUNW,501-2253
SBus
25
HSI
SUNW,501-1725-01
SBus
25
SUNW,hme
SBus
25
SUNW,fas/sd (block)
SBus
25
13
SUNW,socal/sf (scsi-3)
501-3060
SBus
25
HSI
SUNW,501-1725-01
SBus
25
SUNW,hme
SBus
25
SBus
25
13
SUNW,fas/sd (block)
501-3060
No failures found in System

===========================
No System Faults found
========================= Environmental Status ======================
Keyswitch position is in Normal Mode
System Power Status: Minimum Available
System LED Status:
GREEN
ON
YELLOW
GREEN Normal
OFF
BLINKING
Fans:
----Unit
68P02901W19-S
Status
2-77
Oct 2009
----
------
Disk
OK
PPS
OK
System Temperatures (Celsius):

-----------------------------Brd
State
Current
Min
Max
Trend
---
-----
-------
---
---
------
OK
46
42
46
stable
OK
33
28
36
stable
OK
42
38
42
stable
OK
32
27
35
stable
CLK
OK
36
33
36
stable
Power Supplies:
--------------Supply
Status
-------
------
OK
OK
PPS
OK
System 3.3v
OK
System 5.0v
OK
Peripheral 5.0v
OK
Peripheral 12v
OK
Auxilary 5.0v
OK
Peripheral 5.0v precharge
OK
Peripheral 12v precharge
OK
System 3.3v precharge
OK
System 5.0v precharge
OK
AC Power
OK
=========================HW Revisions =========================

ASIC Revisions:
--------------Brd
FHC
AC
SBus0
SBus1
PCI0
PCI1
FEPS
Board Type
Attributes
---
---
--
-----
-----
----
----
----
----------
----------
22
Dual-SBus-SOC+
100 MHz Capable
CPU
100 MHz Capable
22
Dual-SBus-SOC+
100 MHz Capable
CPU
100 MHz Capable
System Board PROM revisions:

----------------------------
2-78
Board 1:
FCODE 1.8. 7 1997/12/08 15:39
iPOST 3.4. 8 1999/02/19 14:25
Board 3:
OBP
POST
3.2.21 1999/02/19 14:33
3.9.10 1999/02/19 14:23
68P02901W19-S
Oct 2009
Weekly administration checklist
Board 5:
FCODE 1.8. 7 1997/12/08 15:39
iPOST 3.4. 8 1999/02/19 14:25
Board 7:
OBP
POST
3.2.21 1999/02/19 14:33
3.9.10 1999/02/19 14:23

Use the following procedure to perform the weekly administration tasks. Copy the checklist
Procedure 2-29
Performing weekly administration tasks
Check that the Informix online logs are rolled over successfully, by
entering the following commands as user omcadmin:
cd /usr/informix
ls -l online.log_MIB
ls -l online.log_OMC
Ensure that online logs exist in the following format:
online.log_MIB.ddmmyyyy
online.log_OMC.ddmmyyyy
Perform a backup of the UNIX file system.

Archive and remove old OMC-R log files on the system processor and
GUI servers by entering the following commands as user root:
/usr/omc/current/sbin/archive -r -d 7 -t /dev/rmt/0
This will archive all log files older than seven days to tape and remove
the files after they have been archived.
Archive and remove unloaded PM database files on the system

processor by entering the following commands as user root:
maintain_script -a -d 7 -t /dev/rmt/0
/usr/omc/ne_data/raw_stats parsed\*
This will archive raw statistical bad header files older than seven days.
maintain_script -r -d 7 /usr/omc/ne_data/raw_stats parsed\*
This will remove raw statistical bad header files older than seven days
after they have been archived.
Check the file system capacity by entering the following commands as

user root:
df -k
Check the disk usage capacity of the system by entering the following
commands as user root:
du |more
Terminate processes that are not required and are consuming disk
capacity.
Perform an archive of old OMC-R user files by entering the following

find /home -mtime +14 -print > /usr/tmp/listing
tar -c / usr/tmp/listing /dev/rmt/0

Continued
68P02901W19-S
2-79
Oct 2009
Monthly administration checklist
Procedure 2-29
10
Performing weekly administration tasks (Continued)
System security should be monitored by the system administrator.

Refer to Security overview on page 2-36 for further details about
important security aspects.

Use the following procedure to perform the monthly administration tasks. Copy the checklist
Procedure 2-30
2-80
Performing monthly administration tasks
Perform a backup of the UNIX file system. Refer to Chapter 12 Backup

Server Installation and Configuration.
Change the standard installation passwords for user root, omcadmin,

and informix, and inform the required users. Refer to Administering
user accounts with usertool on page 2-12.
Truncate the cron log file, by entering the following command as user
root:
tail -100 /var/cron/log > /tmp/cron_log mv /tmp/cron_log
/var/cron/log
68P02901W19-S
Oct 2009
Chapter
3
Ancillary Devices
68P02901W19-S
Oct 2009
3-1
Overview
Overview
This chapter contains installation, configuration, and troubleshooting information for OMC-R
ancillary devices.
3-2
Configuring the serial port with Serial Port Manager on page 3-3.
Introduction to modem installation on page 3-7.
Troubleshooting the modem on page 3-19.
Adding a printer on page 3-25.
68P02901W19-S
Oct 2009
Overview of Serial Port Manager

The Serial Port Manager enables the system administrator to manage serial port services for
terminals and modems. Using the Serial Port Manager to configure serial port software allows
the system administrator to set up terminals and modems without having to manually edit and
create the necessary files. It features the following operations:
Templates for common terminal and modem configurations.
Multiple port setup, modification, or deletion.
Quick visual status of each port.
The following procedures are outlined in this section:
Adding a modem.
Setting an additional baud rate.
Installing a modem.
Testing the modem installation procedure.
NOTE
A modem cannot be connected to the SunFire 4800.
Accessing Serial Port Manager

Use the following procedure to access the Serial Port Manager.
Procedure 3-1
68P02901W19-S
Accessing the Serial Port Manager
Login to the system processor as root.
Click on the system administration icon.
Select the Port Manager option.
3-3
Oct 2009
Serial Port Manager parameters

The following functions can be handled using the Serial Port Manager.
Template
This field specifies the preconfigured template used to configure the port from the pull down
menu. The following templates are available:
Terminal - Hardwired:
Users may log in through a terminal directly connected to the system.
Modem - Dial In Only:

Users may dial in to the modem but cannot dial out.
Modem - Dial Out Only:

Users may dial out from the modem but cannot dial in.
Modem - Bidirectional:
Users may either dial in or out from the modem.
Initialize Only - No Connection:

The port service is initialized but not configured. Use this to initialize the port connection
without actually connecting a device to the port.
Detail
The Modify window provides information about the port in three levels: Basic, More, and Expert.
These levels of detail are called modes. Basic detail mode is displayed by default. The Detail
command buttons at the top of the window are used to display the other modes. The More and
Expert modes each show progressively more configuration data and controls.
Basic detail
Port:
Lists the port selected from the Serial Port Manager main window.
Service:
Specifies that the service for the specified port is turned on.
Baud Rate:
Specifies the line speed used to communicate with the device.
Terminal Type:
Specifies the terminal type connected to the port.
3-4
68P02901W19-S
Oct 2009
More detail
Initialize Only:
Specifies that the port software is initialized but not configured.
Bidirectional:
Specifies that the port line is used in both directions.
Software Carrier:
Specifies that the software carrier detection feature is used. If this option is not checked,
the hardware carrier detection signal is used.
Login Prompt:
Shows the prompt after a connection is made.
Comment:
Shows a text description of the service, if any.
Service Tag:
Shows the service tag associated with this port.
Port Monitor Tag:

Specifies the port monitor name to be used for this port.
Expert detail
Create utmp Entry:

Specifies that a utmp entry is created upon login. This item must be checked if a login
service is used.
Connect on Carrier:
Specifies that a ports associate service is immediately invoked when a connect indication is
received.
Service:
Shows the program that is run upon connection.
Streams Modules:
Shows the streams modules that are pushed before the service is started.
Timeout:
Specifies the number of seconds before a port is closed if the open process on port
succeeds and input data is not received.
68P02901W19-S
3-5
Oct 2009
Adding a modem
Adding a modem
Use the following procedure to add a modem.
Procedure 3-2
Adding a modem
In the Serial Port Manager main window, select the port that is to be
used with a modem.
From the Edit menu, select Modify. The Modify window appears in
Basic Detail mode.
Choose the modem configuration that closely matches the modem

service from the Template menu. Refer to Serial Port Manager
parameters on page 3-4 for descriptions of each field in the window.
Change the values of the template entries as required.
Click OK to configure the port.
Setting an alternative baud rate

The following procedure describes the user of other option to select a baud rate that does
not appear on the Baud Rate menu.
Procedure 3-3
3-6
Setting an alternative baud rate
Select Other from the Baud Rate menu.
Enter a baud rate entry from the /etc/ttydefs file that provides seven
bits, even parity service.
Click OK.
68P02901W19-S
Oct 2009
Installing a modem
Installing a modem
Introduction to modem installation

This section describes the installation and configuration of a modem to a Sun Microsystems
platform running Solaris 10 with CDE. Any serial port modem is supported.
The modem is configured for both dial-in and dial-out access.
Background information
The modem can be used for remote access to the OMC-R (dial-in to the OMC-R) and also for
accessing external computer systems from the OMC-R (dial-out from the OMC-R).
Remote access to the OMC-R through a modem can provide TTY (character based) access to the
OMC-R. It does not provide a method to remotely access the graphical functions of the OMC-R.
If a remote OMC-R operator terminal is required, it should be connected to the OMC-R using
LAN routers over a synchronous link operating at speeds of at least 64 kbps.
Support engineers make use of remote access to diagnose and rectify problems.
NOTE
The procedures described here may conflict with other programs or serial port users.
Connect the modem to an unused port or disable the port monitor services.
Data links
When connecting two platforms with modems, there are three data links present.
Figure 3-1
68P02901W19-S
Data links between two platforms
3-7
Oct 2009
Rates
Rates
Data is transferred at the same rate as the slowest link. The modems may use data compression
on the DCE link. This is helpful if the DCE link is the slowest link.
In the following example, data compression on the DCE link could, in theory, make the DCE link
appear to operate at 20+ kbps. The bottleneck would then be the remote DTE rate (19.2 k).
Local DTE rate = 38.4 kbps.
DCE rate = 9.6 kbps.
Remote DTE rate = 19.2 kbps.
The Motorola 3460 Fast'R modem contains various security features to restrict or prevent
access. Password protection and other security features are described in the modem user guide.
Physical connection
Install the modem on the SPARCstation, using either ttya or ttyb (serial port A or B), and make
sure that the RS232 cable is a straight-through cable. Any 20 to 25-pin cable is acceptable
although only pins 1 to 8 and pin 20 are necessary.
NOTE
Do not use a null modem cross-over cable or a null modem gender adapter cable.
While using a system which shares ports A and B, such as the platform 10, and if port B is to be
used for the modem port, use the splitter cable (port A can be accessed directly without the
splitter). This splitter cable is available from SunExpress (part number: X985A or 530-1869/C9).
Initial modem setup
NOTE
The root password is required to install or modify files for modem installation.
The initial platform setup involves the two activities mentioned as follows:
3-8
Defining the dial-in serial port characteristics.
Verifying port monitor services.
68P02901W19-S
Oct 2009
Initial modem setup
Define dial-in serial port characteristics

Add the following entries to the /etc/ttydefs file. These are the serial port characteristics
presented by the answering side:
38400m:38400 hupcl:38400 hupcl crtscts::38400m
19200m:19200 hupcl:19200 hupcl crtscts::19200m
9600m:9600 -clocal hupcl:9600 -clocal hupcl crtscts::9600m
The above definitions turn on hardware flow control (crtscts) at the serial port which is set to
match hardware flow control at the modem. Also, the above definition uses eight data bits with
no parity transfers.
NOTE
14400 baud and 28800 baud rates are the modem to modem speeds and 19200 baud
and 38400 baud are the speeds the modem uses to communicate with the serial
port. Modem to serial port speeds should be faster than modem to modem speeds in
order to prevent bottlenecks.
Verify current port monitor services

Verify that there are no port monitor services on the port to be connected to the modem, by
typing the following command on the platform as user root.
pmadm -p zsmon -l
An example output is:
PMTAG
PMTYPE SVCTAG FLGS ID <PMSPECIFIC>
The following two lines are displayed as one line on the screen:
zsmon
ttymon ttya
root /dev/term/a - -
/usr/bin/login - 9600 ldterm, ttcompat login:
- vt100 y #Terminal
Also, the following two lines are displayed as one line on the screen:
zsmon
ttymon ttyb
root /dev/term/b - -
/usr/bin/login - 9600 ldterm, ttcompat login:
- vt100 y #Terminal
If there are services present, as indicated in the output displayed, remove them by typing the
following command on the platform as user root.
ipmadm -p zsmon -r -s <SVCTAG value from the above,that is ttya or ttyb>
This can also be achieved by using the serial port manager available under CDE when logged in
as root, and selecting Delete or Disable for the port.
The login services need to be removed or disabled before a new ttydefs entry can be used.
68P02901W19-S
3-9
Oct 2009
Communicating with the modem
Communicating with the modem

Once the port monitor services have been deleted or disabled, enter the following command on
the platform as user root.
NOTE
Ensure that tip is executed in a shell without scrolling enabled, otherwise a carriage
return is not sent.
tip -38400 /dev/cua/a
(38400 sets the connection speed, /a assumes ttya. For ttyb, use /b).
Verify that the modem is responding to commands. After the connect message type:
AT
An OK prompt is returned.
If an OK prompt is not returned, try a different port or cable. Ensure that the modem responds
to AT command before continuing with the subsequent sections.
Configuring tip
NOTE
Always use the same speed to tip to the modem as the login process is set to use. The
following procedure assumes that the modem is to be connected using port b. If the
modem is to be connected using port a, alter the procedure accordingly.
Use the following procedure to configure the tip utility by modifying the /etc/remote file:
Procedure 3-4
1
Configuring the tip utility
For ttyb:
hardwire:\
:dv=/dev/term/b:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D:
Add the next two lines after the above entry:
modem:\
:dv=dev/cua/b:br#9600:el=^C^S^Q^U^Z:ie=%$:oe=^D:pa=even
Continued
3-10
68P02901W19-S
Oct 2009
Procedure 3-4
Controlling modem access
Configuring the tip utility (Continued)
NOTE
When using a 28.8 k modem, use 38400; for a 14.4 k modem
use 19200, and for a 9600 modem, use 9600.
2
Change the permissions and the owner of the modem port.

For port a:
chmod 666 /dev/cua/a; chown uucp /dev/cua/a
For port b:
chmod 666 /dev/cua/b; chown uucp /dev/cua/b
After modifying the /etc/remote file and changing the permissions of

the ports, use tip by entering the following command at the # prompt:
tip modem
A connected message should be displayed. If not, check the /etc/remote file for errors
to the modem entry.
Controlling modem access

Control the modem communication by setting the permissions of the tip utility.
To allow only root users the ability to log out using the modem, set the tip permissions to 700
by entering the following command on the platform as user root.
chmod 700 /usr/bin/tip
NOTE
Changing the permissions of tip may affect other users or programs that need to use
tip, for example, the OMC-R Test Mobile feature.
Modem setup and Initialization

The modem is set up using Hayes AT commands. Once the modem is set up, the configuration
can be stored in the non-volatile memory in the modem. It should only be necessary to configure
the modem once, even if power is lost. See the modem users guide for a complete list of the
Hayes command set.
68P02901W19-S
3-11
Oct 2009
Configuring the Serial Port Modem

Use the following example procedures to set up the Motorola 3460 and 326X modems. For more
details on modems, refer to the modem documents that accompany the modem.
Procedure 3-5
Configuring the Motorola 3460 and 326X modems
At the OK prompt, enter the correct AT command for the modem type
and DTE rate (Table 3-1).
The AT command configures the modem and stores the setup in the
non-volatile memory.
After setting up the modem, exit the tip utility by typing a carriage
return followed by a tilde (~) character which is followed by a period
(.) character.
Table 3-1
Modem initialization commands
Modem type
DTE rate
Motorola
3460
38400
AT&FQ2*DE19*FL3&D2&C1*CL0S0=2&Y1&W1
19200
9600
Motorola
326X
Initialization command
38400
AT&FQ2*DE15*FL3&D2&C1*AA2&Y1&W1
19200
9600
NOTE
The syntax of the AT commands is specified in the Motorola 3460 Fast'R User Guide.
Description of AT commands used in the initialization string

The syntax of the AT command is as follows:
AT&FQ2*DE15*FL3&D2&C1*AA2&Y&W1
The syntax is explained in Table 3-2.
Table 3-2
Syntax of the AT command
Symbol
Meaning
AT
Enter command mode.
&F
Reset Modem to default

factory settings.
Notes
The four factory default option sets are restored to

their original settings; all stored telephone numbers
are deleted.
Continued
3-12
68P02901W19-S
Oct 2009
Table 3-2
Syntax of the AT command (Continued)

Meaning
Symbol
Notes
Q2
RsltCode = Orig.
Result codes are output to the DTE when operating

as an originating modem.
DE
Fix DTE rate.
*DE15 sets a DTE rate of 38400.*DE12 sets a DTE

rate of 19200.*DE8 sets a DTE rate of 9600.
*FL3
Flow Control =
RTS/CTS.
&D2
DTR Control = Discon.
The modem hangs up and enters the command

mode when an on-to-off DTR transition is detected,
while the modem is in data, test, or escape mode. If
DTR is low, the modem does not auto answer. This
command determines how the modem interprets
the DTR signal. The local DTE uses DTR (pin 20) to
signal the modem.
&C1
DCD Control = Normal.
Normal DCD is off during dialing and also while

the modem is in training with the remote modem.
DCD is on in data mode. It is off when the modem
is disconnected from the telephone line. This
determines how the modem sets DCD signals. The
modem signals the DTE with DCD on EIA/TIA 232-D
Pin 8 (V.24 Circuit 109).
*AA2
Answer = Ring #2.
The modem will answer incoming calls after two

rings (*AA2) or after X rings where X is defined in
the S0 register (S0=X). Check specific in country
requirements regarding auto-answer modems.
&Y1
Power Up In = 1.
When the modem is powered up, it automatically

uses option set 1.
&W1
Save Changes = 1.
See the paragraph Saving changes.
Saving changes
When using AT commands or front panel options to alter the modem settings, if the changes are
not saved, the modem does not enter them into memory. After selecting the option set most
suited to the application (using the ATZn command), and modifying any required configuration
settings, enter the following:
AT&W<n>
Where
is
<n>
a value between 1 to 4, determined by the option set where the

new customized option set is saved.
The modem front panel displays Saving options. After a few seconds, the front panel displays
Save Completed, signifying that the option set has been successfully saved in the non-volatile
memory of the modem.
68P02901W19-S
3-13
Oct 2009

Set country configuration
Use the following procedure to set up the MultiModem MT5634ZBA with the appropriate
country configuration:
Procedure 3-6
Setting country configuration
Execute the following command to load the factory settings as active

configuration:
AT&F0
Execute the following command to set the country code:

AT%T19,0,nn
Where:
nn is the Country Code (Table 3-3).
Execute the following command to save as factory default:

AT&F&W
Execute the following command to display the Result Codes and to

verify the correct country has been configured (Table 3-3):
ATI9
Country Code and Result Code

Table 3-3 specifies the correct AT command and Result Code for each country.
Table 3-3
AT commands and result codes for country-specific modem configuration

Country
AT command (hexadecimal)
Result Code (decimal)
Argentina
AT%T19,0,34
52
Australia
AT%T19,0,01
Austria
AT%T19,0,34
52
Belgium
AT%T19,0,34
52
Brazil
AT%T19,0,34
52
Canada
AT%T19,0,34
52
China
AT%T19,0,34
52
Cyprus
AT%T19,0,34
52
Czech Republic
AT%T19,0,25
37
Denmark
AT%T19,0,34
52
Finland
AT%T19,0,34
52
France
AT%T19,0,34
52
Continued
3-14
68P02901W19-S
Oct 2009
Table 3-3 AT commands and result codes for country-specific modem configuration
(Continued)
68P02901W19-S
Country
AT command (hexadecimal)
Result Code (decimal)
Germany
AT%T19,0,34
52
Greece
AT%T19,0,34
52
Hong Kong
AT%T19,0,30
48
Hungary
AT%T19,0,30
48
Iceland
AT%T19,0,34
52
India
AT%T19,0,30
48
Indonesia
AT%T19,0,30
48
Ireland
AT%T19,0,34
52
Italy
AT%T19,0,34
52
Japan
AT%T19,0,10
16
Korea
AT%T19,0,30
48
Liechtenstein
AT%T19,0,34
52
Luxembourg
AT%T19,0,34
52
Mexico
AT%T19,0,34
52
Netherlands
AT%T19,0,34
52
New Zealand
AT%T19,0,09
Norway
AT%T19,0,34
52
Philippines
AT%T19,0,30
48
Poland
AT%T19,0,30
48
Portugal
AT%T19,0,34
52
Russia
AT%T19,0,34
52
Singapore
AT%T19,0,30
48
South Africa
AT%T19,0,35
53
Slovak Republic
AT%T19,0,34
52
Slovenia
AT%T19,0,30
48
Spain
AT%T19,0,34
52
Sweden
AT%T19,0,34
52
Switzerland
AT%T19,0,34
52
Turkey
AT%T19,0,34
52
U.K.
AT%T19,0,34
52
United States
AT%T19,0,34
52
3-15
Oct 2009
Initialize modem
The MultiModem MT5634ZBA can now be set up and initialized by entering one of the following
commands at the prompt:
For a 38400 DTE rate, enter:

AT$SB38400&K3&D2&C1S0=2&Q0&W0

AT$SB19200&K3&D2&C1S0=2&Q0&W0

AT$SB9600&K3&D2&C1S0=2&Q0&W0
This configures the modem and stores the current modem settings in the non-volatile memory.
These changes then loaded in place of the factory defaults at power-on.
AT commands
The AT commands that are used when initializing the MultiModem MT5634ZBA are described in
Table 3-4.
Table 3-4
MultiModem MT5634ZBA initialization AT commands
AT command
AT$SBnnnnn
Description
Set serial port to nnnnn bps.
AT&K3
Enable CTS/RTS hardware flow control.
AT&D2
If DTR drops while in online data mode, the modem hangs up.
If the signal is not present, the modem will not answer or dial.
AT&C1
DCD goes high when the remote modem carrier signal is

detected, and goes low when the carrier signal is not detected.
ATS0=2
Sets the number of rings until the modem answers.
AT&Q0
Enables result codes.
AT&W0
Stores the current modem settings in non-volatile memory

and loads them in place of the factory defaults at power-on, or
following the ATZ command.
After setting up the modem, exit the tip utility by typing a carriage return followed by a tilde (~)
character, followed by a period (.) character.
3-16
68P02901W19-S
Oct 2009
Enabling the login process

Use the following procedure to create a port monitor service to allow login through a modem
from a remote host (bi-directional modem service):
Procedure 3-7
To view the Serial Port Manager window, select port manager from the
tools icon, and click the serial port manager icon.
Click on port a or b with the left mouse button to select the port to be
used by the modem.
Select modify from the Edit menu. The Serial Port Manager: Modify
window appears.
Select the expert display.
Select Bi-directional from template.
Set Baud Rate to the desired baud rate of the modem. Refer to Table 3-5
for the available baud rate settings.
Set Terminal type to vt100.
Verify that all the amended fields are correct and click the OK button.
Close all the open windows.
10
To verify that a port monitor has been configured, enter the following
command at the # prompt:
pmadm -p zsmon -l
PMTAG PMTYPE SVCTAG FLGS ID <PMSPECIFIC>
zsmon ttymon ttya u root /dev/term/a - /usr/bin/login - 9600 ldterm, ttcompat login: - dialup n #modem
Bidirectional
If a port monitor has not been configured for that port, return to step 2
and try again.
Table 3-5
68P02901W19-S
Modem baud rate settings
Modem baud rate
Setting required
28800
38400 m
14400
19200 m
9600
9600 m
3-17
Oct 2009
Remote connection and file transfers
Remote connection and file transfers

To test the modem, contact Customer Network Resolution Centre (CNRC) for a telephone
number, login, password and log out information.
If problems occur, refer to Troubleshooting the modem on page 3-19.
Once the login is successful, instruct the modem to hang-up the line by typing:
+++ ATH
3-18
68P02901W19-S
Oct 2009
Troubleshooting the modem
Troubleshooting the modem
Problem symptoms
Solutions for the following problems are detailed in this section:
All ports busy.
No login prompt.
Modifying eeprom settings.
Corruption from platform with remote system login.
Modem hangs up after answering a call and negotiation.
Permission denied or link down.
Modems do not disconnect properly.
Nothing happens when trying to tip the modem.
On dialing the platform, the modem never picks up the phone.
Login message is corrupt.
Cannot log in - password failed.
No utmpx entry.
All ports busy

This message indicates that another process has control of the port. Follow Procedure 3-8 to
rectify the problem:
Procedure 3-8
1
Modem troubleshooting: all ports busy
Disable or delete the port monitor using the serial port manage,
for that port, or by using the following commands: Enter the
following command to disable the port monitor service of port a:
/usr/sbin/pmadm -d -p zsmon -s ttya.
Continued
68P02901W19-S
3-19
Oct 2009
All ports busy
Procedure 3-8
Modem troubleshooting: all ports busy (Continued)
Enter the following command to enable the port monitor service of port
a:
/usr/sbin/pmadm -e -p zsmon -s ttya
tip -<9600> /dev/cua/a
replacing <9600> with the appropriate connection speed for the
device.
2
Check that the details have been entered correctly in /etc/remote,

ensuring that the correct device has been specified.
There could be a permissions problem on the device. If necessary,

change the permissions and ownership of the modem port by entering,
for example, the following commands at the # prompt:
chmod 666 /dev/cua/a
chown uucp /dev/cua/a
ls -Ll /dev/cua/a
to verify permissions and ownership.
NOTE
If cu is abruptly terminated, the device will be left with an
owner of the last cu user.
4
Check for a lock file in /var/spool/locks. If there is a lock file, for

example, LK.032.028.001, then cat the file. The number displayed is
the Process ID (PID). Use the ps command to determine if the process
is still active. Remove the lock file. If the message All ports busy is
displayed, terminate the process. If the process is defunct it cannot
be terminated and a reboot will be necessary. This occurs because the
driver is waiting at an unlinkable level for the device to respond.
Another process has the port open. This could be another tip session,
a getty process or a defunct tip/cu process. At the # prompt, enter
ps -ef | grep tip
As root, enter the following command at the # prompt for the
appropriate device:
fuser /dev/cua/a
/dev/cua/a: 652o 651o
Based on the example output, enter the following commands:
ps -ef | grep 652
ps -ef | grep 651
Continued
3-20
68P02901W19-S
Oct 2009
Procedure 3-8
No login prompt
Modem troubleshooting: all ports busy (Continued)
The PIDs are 652 and 651.

If the process using the port is /usr/bin/login or ttymon, then
somebody has dialed the machine, the modem is active or the modem is
asserting Data Carrier Detect (DCD) all the time. Configure the modem
so that the DCD is asserted only when a carrier is detected from the
remote modem. Refer to the modem documentation for further details.
6
If the process is ttymon, kill the process using the Serial port
manager. Select the port from the Edit menu and delete the port
service. (The modem is no longer configured for dial-in).
The command to remove the service is:
pmadm -r -p zsmon -s <SVCTAG>
(use pmadm -l to determine SVCTAG).
Bring the system down and then back to multi-user mode. The
command is:
/usr/sbin/shutdown -i6 -g0 -y
Sometimes a complete reboot may be necessary to achieve a hardware
reset on the port before rebooting.
REMOVE the device (do not leave a dangling cable; remove the device
at the platform) and DELETE the port monitor.
No login prompt
Use the following procedure if a login prompt does not appear.
Procedure 3-9
1
Modem troubleshooting: no login prompt
Check if a ttymon process is started by typing the following command

at the # prompt:
ps -ef | grep ttymon
root
208
root
17258 208
204
80
2
Sep21
? 0:01 /usr/lib/saf/ttymon
10:42:43 ? 0:00 /usr/lib/saf/ttymon
Where:
PID of 208 is the parent ttymon process.
PID of 172.58 is the child process for term/b.
2
Check if the ttymon process TTY has changed from ? to term/b by

typing the following command at the # prompt:
ps -ef | grep ttymon
root
208
204
root
17258 208
80
6
Sep21
0:01 /usr/lib/saf/ttymon
10:42:43 term/b 0:00 /usr/lib/saf/ttymon

Continued
68P02901W19-S
3-21
Oct 2009
When to modify the eeprom settings
Procedure 3-9
3
Modem troubleshooting: no login prompt (Continued)
If the ttymon process TTY has not changed to term/b, check if the
serial port has been configured properly and the port monitor service
is present by typing the following command at the # prompt:
pmadm -p zsmon -l
zsmon ttymon ttya
u
root
/dev/term/a - -
/usr/bin/login - 9600 ldterm,

ttcompat login:
- tvi925 n
#modem -Bidirectional
4
Check and verify that the port monitor services baud rate matches the
modem baud rate.
Use the tip utility and connect back to the modem.
When to modify the eeprom settings

Do not change the eeproms unless trying to get a terminal working at boot prom level.
Corruption from platform with remote system logging in

This is usually an indication that the modem speed and the configured port monitor speed are
not matched. Use the following procedure to correct this problem:
Procedure 3-10
Modem troubleshooting: corruption from platform
Check the modem speed and make certain that it matches the speed
of the platform.
Connect the modem using tip, and verify the modem configuration.
NOTE
The modem must be able to lock the modem speed and
match the port monitor speed configured using the Serial
Port Manager.
Modem hangs up after answering a call and negotiation

This is probably because one or both the modems are forced to use a particular connection
speed or compression protocol. If one modem cannot manage to connect to the other modem,
the modem hangs up. Check the settings of both modems.
3-22
68P02901W19-S
Oct 2009
Permission denied or link down
Permission denied or link down

Use the following procedure if a permission denied or link down message appears from the
tip utility.
Procedure 3-11
Modem troubleshooting: permission denied or link down
Ensure that dv=/dev/cua/a or dv=/dev/cua/b are present in the

hardwire entry of the /etc/remote file.
Check in /var/spool/locks for a lock file LCK.* and remove that file.
Check the permissions and ownership on the serial device (/dev/cua/a

or /dev/cua/b).
Modems do not disconnect properly

The modem does not disconnect properly or a user stays logged in even after disconnecting.
The modem is not configured correctly. The modem must be configured so that the Data Carrier
Detect (DCD) is asserted only when a carrier is detected from the remote modem. Refer to
the modem documentation for further details.
Nothing happens when trying to tip the modem

If this situation occurs, use the following procedure to correct this problem:
Procedure 3-12
Modem troubleshooting: no response to tip
Check the cabling to the modem.
Check if the proper port is being used.
Ensure that tip is being used in a shell tool, NOT in a command tool.
When dialing into the SPARC the modem never answers the
phone
This situation indicates that the modem is not configured correctly, FollowProcedure 3-13 to
correct this problem:
Procedure 3-13
68P02901W19-S
Modem troubleshooting: modem not answering
Check if the modem is set up for auto answer (*AA2) for Motorola
Modems or ATS0=2 for MultiModem.
Ensure that the Data Terminal Ready (DTR) light is lit on the modem
which indicates that the DTR is asserted from the platform.
3-23
Oct 2009
Login message is corrupt
Login message is corrupt

The login message is corrupt and nothing happens when RETURN is pressed, but it does if
LF or CTRL-J is pressed.
If this situation occurs then reconfigure the remote computers serial port setup for eight data
bits, one stop bit and no parity.
Cannot login, password fails

This situation indicates a parity problem. The originating terminal or tip session is using a
parity that is different from that used by the ttymon.
No utmpx entry
There is no utmpx entry and the user must execute login from the lowest level shell.
If this situation occurs ensure that the terminal type is set to vt100 when setting up the port
monitor services and the environment variable TERM is also set to vt100 on both the local
and remote host.
3-24
68P02901W19-S
Oct 2009
Adding a printer
Adding a printer
Overview of adding printers to the OMC-R

It is possible to add a printer on the Ethernet LAN of the OMC-R. The printer can be connected
anywhere on the LAN and is not restricted to being connected to the system processor or
one of the GUI processors.
For information on adding and setting up a printer on the LAN, please refer to the manual that
accompanied the printer.
Assigning printer name and address on the network

Assign the printer name and address on the network by adding the printer IP address and host
name to the /etc/hosts file of the single platform processor.
Use the following procedure to verify the printer setup:
Procedure 3-14
68P02901W19-S
Assigning printer name and address
Print a page to verify the printer settings.
Issue a ping command from any processor on the OMC-R network

as follows:
ping <hostname>
Replace <hostname> with the name of the printer set in the /etc/hosts
file.
If the printer does not respond to the ping command, check the
following:
Make sure all physical connections, bridges, and routers are

working correctly.
From the setup page, check that the IP protocol is enabled.
Check that the IP address is set correctly on the printer operator's

panel.
3-25
Oct 2009
Configuring a printer connected to a GUI processor
Configuring a printer connected to a GUI processor

Jobs are spooled to the system processor for printing (or the processor to which the printer is
attached).
To add a local printer, execute the following command on the host processor as user root:
/usr/omc/current/sbin/Configure_Printer
Follow the instructions on the screen.
Configuring a network printer

Network printers have their own network cards in them and therefore exist as separate entities
on the network. This category of printer includes the SPARC printer E and Lexmark Optra range.
Network printers can be configured from the front panel to set their IP addresses. Each printer
must be set up in the hosts file. They must be able to run the ping command:
/usr/sbin/ping <printer_hostname>
where <printer_hostname> is the hostname of the network printer.
This should return the following message:
<printer_hostname> is alive
/usr/omc/current/sbin/Configure_Printer
The user will be prompted to enter the
<printer_hostname>
NOTE
On a non Lexmark or SPARC printer E printer ASCII print jobs may not be sent to the
printer correctly, causing the print output to appear jumbled.
To fix this change the setting CR After LF to Yes. Refer to the printer manual for
details on how to do this.
3-26
68P02901W19-S
Oct 2009
Checking the printer status
Checking the printer status

To check whether the installation is complete enter the following command:
lpstat -t
Screen output similar to the following is displayed:
Scheduler is running system default destination:
laser device for laser: /dev/null laser accepting
requests since Jun 24 15:36 printer laser
(login terminal) is idle. enabled since Jun 29 10:55
Printing a file
To print a file use the lp command in the following format:
lp <filename>
Printer configuration file

A printer configuration file provides support for multiple printers defined by the user.
The default printer configuration file is /usr/omc/current/config/printer.def.
The printer configuration file contains information in the following format:
<printer_alias> <print_command>
Where
is
<printer_alias>
a user friendly name for the printer,

displayed to the user.
<print_command>
the executable script used for

printing.
Error messages are displayed to the user if:
An incorrect printing type is specified in the printer configuration file.
The printer script specified in the printer configuration file does not exist in
/usr/omc/current/bin on the GUI processor.
The printer script is not executable.
A default script called mmiPrint is provided in /usr/gsm/current/bin on the GUI processor.

Other scripts may also be used, but must be located in the same directory.
68P02901W19-S
Oct 2009
3-27
Printer configuration file
3-28
68P02901W19-S
Oct 2009
Chapter
4
OMC-R Log Files
68P02901W19-S
Oct 2009
4-1
Overview
Overview
The OMC-R maintains log and error files, separate for each application. The log files are
grouped into log directories according to the different functional areas. Log files contain startup
and shut down information for the different applications and in some cases, error messages.
Some applications generate their own error files.
4-2
OMC-R log and error files on page 4-3.
Checking audit log files on page 4-11.
68P02901W19-S
Oct 2009
OMC-R log and error files
OMC-R log and error files
The main log directory $OMC_TOP/logs, the event log directory $OMC_TOP/ne_data/ev_logs
and the INFORMIX log directory /usr/informix contain the log files shown in the following
charts.
OMC-R log files on the system processor

The following chart, Figure 4-1, shows the file structure under each of the three log directories
mentioned above.
NOTE
Some miscellaneous log files exist in the /usr/omc/logs directory depending on the
activity on the system. Examples of these log files are cleanMIB and upgrade.
68P02901W19-S
4-3
Oct 2009
OMC-R log files on the system processor
Figure 4-1
4-4
OMC-R Log files on the system processor
68P02901W19-S
Oct 2009
OMC-R log files on the GUI server

The following chart shows the file structure under the main log directory $OMC_TOP/logs on
the GUI server.
Figure 4-2
NOTE
There is no INFORMIX log directory on the GUI server.
Problems with parsing statistics and maintenance of the PM

database
The fpomcaudit and omcaudit logfiles can be monitored for any issues related to the parsing of
PM statistics and maintenance of the OMC database. For information related to the maintenance
of the OMC database, refer to Bulletin GSM_G_OMCR_053 and Bulletin GSM_G_OMCR_056.
Event and alarm logging

Events and alarms are logged under the directory structure $OMC_TOP/ne_data/ev_logs. This
directory is exported by the system processor and mounted, using the Network File System
(NFS) method, on the optional GUI processors. The GUI menus are used to access the logs. All
other files are used for OMC-R internals and troubleshooting.
INFORMIX database log file

The system log files used by the INFORMIX software on the system processor
(defined as a parameter in the onconfig file) are /usr/informix/online.log_MIB and
/usr/informix/online.log_OMC. These files are located in /usr/informix/.
68P02901W19-S
4-5
Oct 2009
Interprocess communication (IPC) logging
Interprocess communication (IPC) logging

Whenever there is a problem within IPC, a file containing information of the problem is created
in $GLOBAL_LOG_DIR. This environment variable is defined as /usr/omc/logs/ipc. If a serious
system problem exists (for example, failure of an OMC-R application), this area may grow
rapidly in size. Accordingly, the directory should be examined daily. Entries may be deleted
following consultation with Motorola support personnel.
IPC messages (error or otherwise) are always logged to a file in the directory specified by
$GLOBAL_LOG_DIR. If $GLOBAL_LOG_DIR is undefined, all messages are logged in
/tmp/$LOCAL_LOG_DIR. If $LOCAL_LOG_DIR is undefined, the default is set to /tmp.
Where possible, the file in $LOCAL_LOG_DIR is moved, on completion, to $GLOBAL_LOG_DIR.
If the initial write to $LOCAL_LOG_DIR fails, the error messages are temporarily logged in
/tmp (before the attempt to move them to $GLOBAL_LOG_DIR). If this initial write to /tmp
fails, the message is displayed on one of the processor consoles.
Setting the $NO_FILE_LOG variable stops the error logger from logging messages to file. If the
$LOG_TO_SCREEN environment variable is set, the messages are logged to the window from
which the OMC was started, regardless of the value of $NO_FILE_LOG.
Environment variables for log files

A number of environment variables are set up to aid the fault tracking process, as follows:
$OMC_IPC_CONFIG
The name of the low-level IPC configuration file. By default this variable is defined as
$SYS_CONFIG/ipc.cfg in the Common.csh file.
$NO_FILE_LOG=1
This variable stops the error logger from generating files in the $GLOBAL_LOG_DIR directory.
By default this variable is not defined in the Common.csh file.
$LOG_TO_SCREEN=1
This variable causes the error logger to dump its contents on the screen should it be invoked.
By default this variable is defined as TRUE (=1) in the Common.csh file.
$GLOBAL_LOG_DIR
This variable give the location to which error logs are moved. If undefined, the default is
/tmp/$LOCAL_LOG_DIR. By default this variable is defined as /usr/omc/logs/ipc in the
Common.csh file.
4-6
68P02901W19-S
Oct 2009
Other environment variables
$LOCAL_LOG_DIR
The location to which error logs are moved. If undefined, the default is /tmp. By default this
variable is not defined in the environment variable files.
Other environment variables

To modify other environment variables, refer to User configurable environment variables on
page 6-5 for their descriptions and the appropriate values for the system and GUI processors.
Checking OMC-R log files

Use the following procedure to check the OMC-R log files. Copy the checklist provided in
Table 14-5 to record the checks.
Procedure 4-1
1
Checking the OMC-R log files
Check that OMC-R log files are created in the correct directory paths:
On the system processor:
OMC-R logs are placed in the /usr/omc/logs directory.
Event logs are placed in the /usr/omc/ne_data/ev_logs directory.
Informix logs are placed in the /usr/informix directory.
Call Trace logs are placed in the /usr/omc/ne_data/ct_logs

directory.
{34164} Critical statistics log files are placed in the

/usr/omc/ne_data/critical_stats directory.
On the GUI processor:
OMC-R logs are placed in the /usr/omc/logs directory.
Event logs are placed in the /usr/omc/ne_data/ev_logs directory.
Check the BSS log files:

cd $OMC_TOP/logs/bss
tail -50 bssname_yyyymmdd
This allows you to see all command line activities performed on a
particular BSS.
Check the Configuration Management log file:

cd $OMC_TOP/logs
tail -50 cm_omcaudit_yyyymmdd
Configuration Management activities are logged to this file.
Continued
68P02901W19-S
4-7
Oct 2009
Procedure 4-1
4
Checking the OMC-R log files (Continued)
When a cutover has been performed check the cutover log file to see if
it has been successful:
cd $OMC_TOP/logs
more cutover.nnnn
This log file says whether the cutover has been successful.
If problems are experienced adding or updating statistics in the PM

database then check for the existence of dbms log files:
cd $OMC_TOP/logs
more dbms.nnnn
This dbms log file contains error information.
Check the fpomcaudityyyymmdd log file for successful statistic parsing.

tail -f $SYS_LOG/fpomcaudityyyymmdd
If problems occur with Interprocess communication then check if an

IPC log file exists in /usr/omc/logs/ipc directory.
cd /usr/omc/logs/ipc
more ipclogfile name
These log files are usually of the format AF032959.0001 (Internet
address id).
This log file shows an error report.
PM fragments are created for parsing the next days statistics.
Applications are connected and reconnected successfully when

required.

cd $OMC_TOP/logs
9
Check the system stats files for system information.

Refer to OMC-R system information on page 13-8.
10
Check the pmguiaudit log file for errors relating to pmgui.

cd $OMC_TOP/logs/usrauditlogs
tail -50 pmguiaudityyyymmdd
Continued
4-8
68P02901W19-S
Oct 2009
Procedure 4-1
11
Check the Informix online logs for DB errors relating to the PM and
CM databases.
For the PM DB:
cd /usr/informix
more online.log_OMC.ddmmyyyy
For the CM DB:
cd /usr/informix
more online.log_MIB.ddmmyyyy
12
Check the omcaudit log for messages relating to OMC-R activity.

cd /usr/omc/logs
tail -f omcaudityyyymmdd
Refer to Restartable processes on page 2-49 for further details about
messages in the omc audit and console log.
13
Monitor the disk space used by the various log files.

As user omcadmin monitor the output of the maintain_script cron
job to ensure that it deletes log files on a regular basis.
cd /var/mail
more omcadmin | grep maintain_script
14
Check the usraudit log file for errors relating to the GUI.
cd $OMC_TOP/logs
/usrauditlogs/
tail -50
usraudityyyymmdd
Continued
68P02901W19-S
4-9
Oct 2009
Procedure 4-1
15
Check the fcaudit log file for errors relating to the event logs.
As user omcadmin, execute the following commands:
cd $OMC_TOP/logs
tail -f fcaudityyyymmdd
NOTE
The following error reported in the fcaudit log because of
multiple file upload request can be ignored safely and it does
not cause any missing statistics:
No matching event found for file transfer completed event.
Service error code: 0
Error Level: 4
To confirm whether it is for redundant upload request or not, check

the omcaudit log for the following message:
handle_xfer: Requested file already exists, redundant upload
This message should correspond to the following message in the
fcaudit log:
No matching event found for file transfer request response
There could be 1 or 2 seconds reported time mismatch between
omcaudit log and fcaudit log because of message propagation between
processes.
4-10
68P02901W19-S
Oct 2009
Checking audit log files
Checking audit log files
Introduction to checking audit logs

It is recommended to routinely check the success of audit applies to the MIB.
Use different methods for checking audit log files in a:
Single OMC-R environment.
Multiple OMC-R environment.
Checking audit log files in a single OMC-R environment

In a single OMC-R environment, use the OMC-R GUI to check that the success of the audit
applies by opening the audit log files and checking the success or failures of the different log
files.
Checking audit log files in a multiple OMC-R environment

In a multiple OMC-R environment, especially in an environment where the system administrator
cannot afford to run multiple GUIs, the following methods can be used to check audit log files.
Checking what has been applied

The aurecordtable9 contains a row for each line in an audit log. The aurecordtable9 contains
a status column, which displays a code indicating the result of the audit apply, as shown in
Table 4-1.
Table 4-1
68P02901W19-S
Audit apply result codes

Code
Meaning
500
The line has not been applied to the MIB database.
501
The line has failed to apply.
502
The row has been successfully applied to the MIB database.
4-11
Oct 2009
Checking the current state of audits

Use the following procedure to see the current state of audits (for example, if an audit is taking
a long time to complete):
Procedure 4-2
Checking the current state of audits
Login as omcadmin on the system processor.
Create a new file (using the vi editor for example) called

Audit_apply_check.sql.
Enter the following SQL statements in Audit_apply_check.sql:

set isolation to dirty read;
select l.rootname audit,count(*) not_appl from aulogtable9
l, aurecordtable9 r
where r.status = 500
and r.logoidclass = l.oidclass
and r.logoidtomid = l.oidtomid
and r.logoidinstrite = l.oidinstrite
and r.logoidinstleft = l.oidinstleft
group by 1;
select l.rootname audit,count(*) applied
from aulogtable9 l, aurecordtable9 r
group by 1;
select l.rootname audit,count(*) failed
from aulogtable9 l, aurecordtable9 r
group by 1;

mib_env
isql mib_db <Audit_apply_check.sql
>Audit_apply_check.out
Open the Audit_apply_check.out file. The output should look similar

to the following:
auditnot_appl
LAB_BSC2:SITE-16: 51
LAB_BSC2:SITE-10: 42
audit applied
LAB_BSC2:SITE-0:1
LAB_BSC2:SITE-10: 1
audit failed
LAB_BSC2:SITE-10:
11
Continued
4-12
68P02901W19-S
Oct 2009
Procedure 4-2
6
Checking the current state of audits (Continued)
To see if the not_appl value is decreasing, repeat step 4 and step 5

several times.
NOTE
It is possible for an audit to fail with some lines still with the
not_appl state. This is because the lines relied on previous
lines which did not apply successfully.
68P02901W19-S
Oct 2009
4-13
4-14
68P02901W19-S
Oct 2009
Chapter
5
OMC-R Cron Jobs
68P02901W19-S
Oct 2009
5-1
Overview
Overview
These are installed to perform various maintenance tasks for both system and GUI processors.
A recommended cron script exists for each processor. This is installed in the directory
$OMC_TOP/current/install_splat.
Several log maintenance scripts are available to maintain the log files on the different
processors. These scripts are designed to work on a specific area of the logs. All of these scripts
can be executed from the command line or through cron.
NOTE
Most of these scripts need omcadmin as login id.
5-2
System cron jobs on page 5-3.
Scheduling cron jobs using the batch scheduler on page 5-9.
Scheduling cron jobs from the command line on page 5-14.
Checking cron jobs on page 5-18.
68P02901W19-S
Oct 2009
System cron jobs
System cron jobs
cron jobs on the system processor

The s90cronjob script contains recommended cron jobs for the following utilities:
root cron jobs

The following root cron jobs are run on the system processor:
maintain_script
systat
onmode_pm
onmode_mib
monitor_diskspace
monitor_ct_logs
roll_online.log
sar_per_day
omc_db_maint
app_vrt_display
monitor_log
NOTE
To check the output of the root cron jobs, the root file in the /var/mail directory
should be checked for error messages.
68P02901W19-S
5-3
Oct 2009
cron jobs on the system processor
omcadmin cron jobs

The following omcadmin cron jobs are run on the system processor:
update_mib_statistics
maintain_script
roll_paging_log
core_presence
pm_purge_check
site_timesynch
bss_dt_load.sh
maintain_ct.sh
checkValidlockPID
NOTE
To check the output of the omcadmin cron jobs, the omcadmin file in the /var/mail
directory should be checked for error messages.
sys cron jobs

The following system cron jobs are executed on the system processor:
sa1
sa2
These cron jobs are used for performance collection.
NOTE
To check the output of the sys cron jobs, the sys file in the /var/mail directory should
be checked for error messages.
5-4
68P02901W19-S
Oct 2009
cron jobs on GUI processors
cron jobs on GUI processors

root cron jobs
The s90cronjob_mmi script contains recommended cron jobs for the following utilities:
timesynch
systat
maintain_script
app_vrt_display
NOTE
To check the output of the root cron jobs, the root file in the /var/mail directory
should be checked for error messages.
omcadmin cron jobs

The following omcadmin cron jobs can be run on the system processor:
maintain_script.
checkValidLockPID.
NOTE
To check the output of the omcadmin cron jobs, the omcadmin file in the /var/mail
directory should be checked for error messages.
sys cron jobs

The following system cron jobs are executed on the GUI processor:
sa1
sa2
These cron jobs are used for performance collection.
NOTE
To check the output of the sys cron jobs, the sys file in the /var/mail directory should
be checked for error messages.
68P02901W19-S
5-5
Oct 2009
Recommended cron jobs

maintain_script (root or omcadmin)
This script will list, archive, remove, and clear files of a specified age from a specified directory.
/usr/omc/sbin/maintain_script
The following shows the syntax of this script:
maintain_script < -l | -a | -r | -c > [ -d <days> ] [ -t <device> ] [
<directory>] [ <filename> ]
Where:
is:
-l
the mode which lists the selected files.
-a
the mode which archives selected files to tape using the

UNIX command cpio.
-r
the mode which removes selected files from the system.
-c
to clear the database log file.
-d <days>
the age of the files to be selected (default value is one day).
-t <device>
the tape device for archiving the files (default value is

dev/rmt/0 on the system processor).
<directory>
the system directory.
<filename>
the file to be removed, for example, omcaudit\*.
NOTE
Only one of the options shown within the chevrons (l, a, r, or c) can be selected at
one time. A separate invocation is needed every time to list, archive, or remove
maintenance log files.
systat (root)
This script monitors the status of the system:
/usr/omc/sbin/systat
onmode_pm (root)
This script frees up memory segments for PM database.
/usr/omc/sbin/onmode_pm
5-6
68P02901W19-S
Oct 2009
onmode_mib (root)
This script frees up memory segments for CM database.
/usr/omc/sbin/onmode_mib
monitor_diskspace (root)
This script monitors the disk capacity of the /usr/omc/ne_data/raw_stats/nmc_stats directory.
/usr/omc/sbin/monitor_diskspace
monitor_ct_logs (root)
This script checks disk space on the /usr/omc/ne_data/ct_logs directory, and will remove old
logs if space exceeds a certain limit.
/usr/omc/sbin/monitor_ct_logs
roll_online.log (root)
This script performs a rollover of the online.log file.
/usr/omc/sbin/roll_online.log
sar_per_day (root)
This script generates a system activity report data file.
/usr/omc/current/sbin/sar_per_day
update_mib_statistics (omcadmin)
This script updates statistics for all tables in the CM database.
/usr/omc/current/sbin/update_mib_statistics
roll_paging_log (omcadmin)
This script performs a daily rollover of the PagingLog file.
/usr/omc/sbin/roll_paging_log
core_presence (omcadmin)
This script notifies user omcadmin of any core files.
/usr/omc/current/sbin/core_presence
68P02901W19-S
5-7
Oct 2009
monitor_log (root)
This script monitors the OMC and the system processor for performance.
/usr/omc/sbin/monitor_log
app_vrt_display (root)
This script ensures that applix virtual display is running.
/usr/omc/current/sbin/app_vrt_display
omc_db_maint (root)
This script performs PM database maintenance.
$OMC_TOP/current/sbin/omc_db_maint
site_timesynch (omcadmin)
This script gets the date on the system processor, then updates sites according to the NE map.
/usr/omc/current/sbin/site_timesynch [passwd 1] [passwd 2]..
[passwd n]
Where <passwd 1>, <passwd 2>, and <passwd n> are optional level 2 passwords for each NE
with a level 2 password set.
timesynch (root)
This script resets the GUI processor time from the system processor.
/usr/omc/current/sbin/timesynch
bss_dt_load.sh (omcadmin)
This script loads default date times into BSS datetimes.
/usr/omc/current/sbin/bss_dt_load.sh
maintain_ct.sh (omcadmin)
This script deletes call trace logs.
checkValidLockPID (omcadmin)
This script removes any invalid lock files.
/usr/omc/current/sbin
5-8
68P02901W19-S
Oct 2009
Scheduling cron jobs using the batch scheduler
Scheduling cron jobs using the batch scheduler
Overview of the batch scheduler

The following sections outline some of the CDE utilities common to both a root and an omcadmin
login.
The CDE environment provides a batch scheduler which allows the user to schedule cron jobs
from the CDE environment on the system and GUI processors.
Displaying cron jobs

Use the following procedure to display cron jobs using the batch scheduler:
Procedure 5-1
68P02901W19-S
Displaying cron jobs using the batch scheduler
To activate the cron scheduler click the CRON icon on the CDE desktop
environment. A window show in Figure 5-1 is displayed. A list of
scheduled cron jobs is displayed in the top half of the window. These
cron jobs can be added to, removed or modified.
To display details of the cron job that is currently running, click Get
active crontab. The details are displayed, for example, as shown in
Figure 5-2. These include Hour, Minute, Day of month, Month, Day
of week and the cron command.
To display details of any listed cron job, simply click the cron job in
the list.
To clear the details, click Clear gadgets.
5-9
Oct 2009
Figure 5-1
5-10
Batch scheduler main window
68P02901W19-S
Oct 2009
Figure 5-2
68P02901W19-S
Batch scheduler main window: selected cron job
5-11
Oct 2009
Adding a new cron job
Adding a new cron job

Use the following procedure to add a new cron job using the batch scheduler:
Procedure 5-2
Adding a new cron job using the batch scheduler
From the Batch scheduler main window (Figure 5-1) highlight one of the
pre-existing cron jobs.
Its details are displayed, for example, as shown in Figure 5-2. These include
Hour, Minute, Day of month, Month, Day of week and the cron job command.
Modify the variables as required.
Click Add.
Click Install to set the new cron job to run on the system or GUI processor.
Modifying an existing cron job

Use the following procedure to modify an existing cron job using the batch scheduler:
Procedure 5-3
1
Modifying an existing cron job using the batch scheduler
From the Batch scheduler main window (Figure 5-1) highlight one of
the pre-existing cron jobs.
Its details are displayed, for example, as shown in Figure 5-2.
5-12
Modify the variables as required. The Modify command button is

enabled.
Click Modify.
A Notify message box is displayed as shown in Figure 5-3.
Click OK to replace the pre-existing schedule with the modified cron

job schedule.
Click Install to set the modified schedule to run on the system or

GUI processor.
68P02901W19-S
Oct 2009
Figure 5-3
Removing a cron job
Notify message box for modifying a cron job
Removing a cron job

Use the following procedure to remove a cron job using the batch scheduler:
Procedure 5-4
68P02901W19-S
Removing a cron job using the batch scheduler
From the Batch scheduler main window (Figure 5-1) highlight the cron
job. Its details are displayed.
Click Remove.
A Notify message box is displayed as shown in Figure 5-3.
Click OK to remove the cron job.
Click Install to set the modified crontab to run on the system or GUI
processor.
5-13
Oct 2009
Scheduling cron jobs from the command line
Scheduling cron jobs from the command line
Overview of scheduling cron jobs from the command line

This section describes how to perform the following procedures on a system or GUI processor
using the command line:
Viewing cron jobs.
Checking cron jobs.
Adding cron jobs.
Removing cron jobs.
Cron maintenance procedure.
Printing crontab files.
Viewing crontab files

To view a user's existing crontab, execute the following command:
crontab -l
NOTE
To view a user's crontab file, it is necessary for the user to log in.
Verifying cron jobs

Results of administration jobs that are run using the cron utility are mailed to the owner of the
specific job (for example, root and omcadmin).
The mail file for the user is located in /var/mail. This file can be viewed to check the output
from the cron job.
To check the results of jobs run using cron, login to the relevant processor and using the
mail tool check that all cron jobs have run successfully. The user is informed through mail
regarding unsuccessful cron jobs.
5-14
68P02901W19-S
Oct 2009
Adding cron jobs
Adding cron jobs

Use the following example procedure to add a new job that removes all database files, which are
more than seven days old from the system, at 15 minutes past midnight.
NOTE
To add commands to a user's crontab, it is necessary for the user to log in.
Procedure 5-5
Adding cron jobs: example
List the cron jobs currently running to a temporary file as follows:

crontab -l > /tmp/cron_list.tmp
Add the new job (comment and activation line) to the temporary
file. For example,
# Remove database files older than 7 days
#
15 00 * * * env OMC_TOP=/usr/omc /usr/omc/sbin/maintain_script -r -d
The crontab file consists of six fields. The first five fields are the
integer patterns that specify the following:
Minutes (0-59).
Hour (0-23).
Day of the month (1-31).
Month of the year (1-12).
Day of the week (0-6). For example, 0 denotes Sunday.
Re-submit the edited temporary file to cron for execution using

crontab as follows:
crontab /tmp/cron_list.tmp
Enter the following command to remove the temporary file.

rm /tmp/cron_list.tmp
NOTE
68P02901W19-S
It is not recommended to set up cron jobs that archive

files to tape.
A hardcopy printout of the cron jobs running on the

system should be kept safe. This may be used for
reference during system troubleshooting.
5-15
Oct 2009
Removing cron jobs
Removing cron jobs

Use the following example procedure to delete a cron job that removes all database files, which
are more than seven days old at 15 minutes past midnight.
NOTE
To remove a cron job from a user's crontab file, it is necessary for the user to log in.
Procedure 5-6
Deleting cron jobs: example
List the cron jobs currently running to a temporary file by entering:

crontab -l > /tmp/cron_list.tmp
Delete the required activation line and relevant comment lines from
the temporary file, as shown in the example:
#
Remove database files older than 7 days
#
15 00 * * * env OMC_TOP=/usr/omc /usr/omc/sbin/maintain_script
-r -d7
Resubmit the edited temporary file to cron for execution by entering:

crontab /tmp/cron_list.tmp
To remove the temporary file enter:

rm /tmp/cron_list.tmp
cron maintenance procedure

Log files of cron jobs are produced, which must be regularly maintained. Use the following
procedure regularly to avoid a cron log file becoming too large.
Procedure 5-7
5-16
cron maintenance procedure
Login as root and enter the following command:

tail -100 /var/cron/log > /tmp/cron_log
This takes the last 100 lines of the cron log file and places it in a
temporary directory.
Copy the log file back to its original directory as follows:

mv /tmp/cron_log /var/cron/log
The cron log file has been temporarily truncated to a size of 100 lines.
It will start to increase as soon as the next cron job is executed.
68P02901W19-S
Oct 2009
Printing crontab files

Each time a crontab file is modified, a printout of it should be made. Several different crontab
files may exist: each of the users, root and omcadmin can have a crontab file on the system
processor and any of the GUI processors.
Use the following procedure to obtain a crontab file that are printed:
Procedure 5-8
68P02901W19-S
Login to the processor where the crontab file has been set up using
the relevant login id.
Enter the command:

Obtain a printout of files by entering:

/usr/ucb/lpr <filename>
Where <filename> is the name of the crontab file to be printed.
5-17
Oct 2009
Checking cron jobs
Checking cron jobs
Checklist for cron jobs

Use the following procedure to check cron jobs. Copy the checklist in Table 14-4 to record
the checks.
Procedure 5-9
Checking cron jobs
Check that the cron daemon is running on the system. As user root
execute the following command:
ps -elf | grep cron
A
/usr/sbin/cron
process is displayed.
Start the cron daemon if it is not running. As user root execute the
following commands:
rm -f /etc/cron.d/FIFO
/usr/sbin/cron
Check that the CRONLOG variable has been set to YES to ensure that
cron logging is done. As user root execute the following command:
more /etc/default/cron | grep CRONLOG
If the CRONLOG variable is set to NO, then it should be changed. As

user root edit the
/etc/default/cron
file and change the
CRONLOG
setting to YES. Save the file.
Check that the cron jobs are set up correctly for user root. As user
root execute the following command:
crontab -l
Check that the cron jobs are set up correctly for user omcadmin. As
user omcadmin execute the following command:
crontab -l
Check that the system cronjobs are set up correctly. As user sys
crontab -l
Check the /var/cron/log file to ensure that all crons executed are
logged to this file. As user root execute the following command:
more /var/cron/log
Check that the /var/cron/log file is rolled over to avoid disk space
issues. As user root execute the following command:
cd /var/cron
ls -l
Continued
5-18
68P02901W19-S
Oct 2009
Procedure 5-9
68P02901W19-S
Oct 2009
Checking cron jobs (Continued)
10
Log files should exist in the format log.<ddmmyyyy>where <ddmmyyyy>

is the date of the log.
11
Check the output of root cron jobs for any errors. As user root execute
the following commands:
cd /var/mail
more root | grep <cronjobname>
12
Check the output of omcadmin cron jobs for any errors. As user root
execute the following commands:
cd /var/mail
more omcadmin | grep <cronjobname>
13
Check the output of the system cron jobs for any errors. As user sys
execute the following commands:
cd /var/mail
more sys | grep <cronjobname>
Where <cronjobname> is the name of the cron job whose output you
are checking.
5-19
5-20
68P02901W19-S
Oct 2009
Chapter
6
OMC-R Environment variables
68P02901W19-S
Oct 2009
6-1
Overview
Overview
6-2
Customizing the OMC-R user environment on page 6-3.
User configurable environment variables on page 6-5.
Changing an environment variable on page 6-26.
Setting the status of the Consolidated Alarms on page 6-29.
Non user configurable environment variables on page 6-31.
Setting the time for the OMC-R and NEs on page 6-36.
68P02901W19-S
Oct 2009
Customizing the OMC-R user environment
Customizing the OMC-R user environment
Customizing a user environment

If an individual OMC-R user's environment needs to be customized, it is done using the user's
xxxx.private files (for example, cshrc.private) located in the user's home directory.
If all the environments of OMC-R users need to be customized, it is done in the
$OMC_TOP/current/env/.xxxx files, which are used by all OMC users.
NOTE
There is a separate /usr/omc/current/env directory on each processor.
.cshrc.private file
If the .cshrc.private file exists, it is executed when a user logs in, and whenever the user runs
a C shell. The .cshrc.private file is used to specify user-specific values for the environment
variables.
NOTE
When an environment variable is redefined, the new environment variable definition
may not become current until the user logs in again.
.Xdefaults.private file
The .Xdefaults.private file is an X resource file which is used to set up function keys. Many X
attributes for personal display can be customized by specifying them in this file. In particular, a
mapping between function keys and strings must be set up in this file.
NOTE
Only the OMC-R system administrator can customize the .Xdefaults.private file
for a user.
A function key can be associated with a string. When the key is pressed and an X-Term window
is displayed, the string is printed in the X-Term window.
The association between the function key and the string is specified in a translation table in an
X resources file. Individual users can program function keys by placing a translation table in
their .Xdefaults.private file.
68P02901W19-S
6-3
Oct 2009
.Xdefaults.private file
Example
The format of the translation table is shown in the following example:
.XTerm*VT100.Translations: #override \
<Key>F1: string(disp_equip 0)string(0xd)
\n\
<Key>F2: string(disp_dev_s)
NOTE
No spaces should follow the \ character on the same line.
In the previous example, the translation table specifies that for all X-Terms of type VT100,
the translation of key functions to strings overrides any previously defined function for keys
F1 and F2.
The translation of each key is as follows:
When the F1 key is pressed, the string disp_equip 0 is printed on the screen followed by a
carriage return. If an argument for the string begins with 0x the argument is taken as a
hexadecimal number, and the corresponding ASCII character is inserted. The argument
0xd inserts the ASCII carriage return character.
When the F2 key is pressed, the string disp_dev_s is printed on the screen. A carriage
return is not sent, and typically the operator finishes off the command and then presses
RETURN.
The keyword override is important because without it, all existing translations are deleted. The
user, when programming function keys, only wants to change certain translations.
Translations should be separated by the sequence \n. A back slash (\) should be placed at the
end of each line except the last to indicate that the translation table is continued on the next line.
6-4
68P02901W19-S
Oct 2009
User configurable environment variables
User configurable environment variables
Introduction to the user configurable environment variables

The user configurable environment variables are stored in two locations:
/usr/omc/current/config/env
The files in this location contain a set of default environment variable values, cannot be
modified.
/usr/omc/config/global/env
This location contains a set of empty files where a non-default value of an environment
variable is required, the value should be set in the correct file at this location.
Where environment variables are sourced by the OMC-R applications, the set of values in
the /usr/omc/current/config/env location are initially sourced. Where values are set in the
/usr/omc/config/global/env location, these are sourced as a secondary set of values.
The User configurable environment variables, for the OMC-R applications, are defined in the
following files:
/usr/omc/current/config/env/pmProcConfig.csh
Defines the variables used by the system processors, which interact with the PM database.
/usr/omc/current/config/env/mibProcConfig.csh
Defines the variables used by the MIB processes, which interact with the MIB database.
/usr/omc/current/config/env/mmiProcConfig.csh
Defines the variables used by the GUI processes which interact with the GUI server or
clients.
There are .sh versions of these files (Bourne Shells), which are automatically updated if any
changes are made in the .csh versions.
System processes and PM database configurable variables

This section lists the user configurable environment variables, used by the system processes
interacting with the PM database.
The default values of these environment variables are defined in the /usr/omc/current/config/env/pmProcConfig.csh file. To set a non-default value for any of these variables, make the
change in the /usr/omc/config/global/env/pmProcConfig.csh file.
68P02901W19-S
6-5
Oct 2009
ABORT_UPL_RL_IN_PROG
The environment variable ABORT_UPL_RL_IN_PROG aborts the upload request when the Rlogin
session is active.
If the environment variable is not set (that is, the value is 0), it allows the upload session
even though the Rlogin session is active.
If set to 1, the environment variable aborts the upload request if the Rlogin session is active.
The default value for the environment variable is 0.
AUTOSTART_PMGUI
The AUTOSTART_PMGUI when set to OFF. If it is set to ON, the PMGUI will start automatically
in the background as the GUI starts. However, this can slow down the startup process.
COUNTRY_CODE
The COUNTRY_CODE environment variable defined by the GSM operator license.
ENABLE_CYCLIC_NBRS
The ENABLE_CYCLIC_NBRS when set to ON activates the Cyclic Neighbors Feature. The
feature enables neighbor statistics for cells in rotation, starting with cells that have the oldest
date for last enabled neighbor statistics (see Using neighbor statistics on page 13-91). The
default value for this environment variable is OFF.
The ENABLE_CYCLIC_NBRS variable is set using the command:
setenv ENABLE_CYCLIC_NBRS ON
INFORMIXDIR
The INFORMIXDIR environment variable defines the path to where Informix is installed on the
system and by default, is set to /usr/informix.
INFORMIXSERVER
The INFORMIXSERVER environment variable is used to identify the server name of the PM
Informix Server instance and by default, is set to omc_sys.
MAX_BOOTLOADS
This environment variable is set to limit the maximum download capacity. It is used in
conjunction with MAX_CSFP_BLP. The maximum value that this environment variable is set to
is 12 and the minimum is 4. For Low-end systems the default is 6, and for Mid-end or High-end
systems the default is 12. A value of 8 is used by the system processes if the environment
variable is not set or has exceeded permitted range.
6-6
68P02901W19-S
Oct 2009
MAX_CSFP_BLP
The MAX_CSFP_BLP environment variable is set to limit the number of CSFP downloads
to a value which is less than the maximum allowable number of downloads set by
MAX_BOOTLOADS. This prevents all the download capacity from being used by the CSFP
downloads, ensuring spare capacity for a conventional download in the event of an NE losing
power momentarily, or some other transient fault.
For a Low-end system, this variable has a default setting of 3. For a High-end and Mid-end
system, this variable has a default setting of 6.
If the defaults are maintained, the OMC-R limits the number of CSFP downloads to one half of the
maximum allowable number of downloads. To increase the allowed number of CSFP downloads
to a higher fraction of the total allowed downloads, set MAX_CSFP_BLP to a higher value.
The permitted range of values is between 1 and MAX_BOOTLOADS - 1. If MAX_CSFP_BLP is
set to a value outside this permitted range, or the variable is not set, it is reset to one less than
the value of the MAX_BOOTLOADS variable.
MAX_UPLOADS_PER_CHAN
The MAX_UPLOADS_PER_CHAN environment variable specifies the maximum number of
simultaneous uploads per channel that are allowed at the OMC-R.
For a Low-end system, the default value is 2. For High-end and Mid-end systems the default
value is 8. It has a valid range of 2 to 8. A default value of 4 is used if the environment variable
is not set or an invalid value is specified.
MMI_CLEAR_INACTIVE_FMIC
The MMI_CLEAR_INACTIVE_FMIC environment variable is set to TRUE for all users. It is set
on to enable all users to clear inactive FMIC alarms from the system.
MMI_ENABLE_FMIC
The MMI_ENABLE_FMIC environment variable is set to 1 to ensure that FMIC is enabled on
the MMI. It has a range of 0 or 1.
NETWORK_CODE
The NETWORK CODE environment variable is defined by the GSM operator license.
NO_OF_PARSERS
NO_OF_PARSES is by default set to integer size. This variable defines the number of parser
processes that can run simultaneously.
This environment variable is always set to 1.
68P02901W19-S
6-7
Oct 2009
OMC_TOP
The OMC_TOP environment variable is used by the OMC-R software is, by default, is set to
/usr/omc.
PM_HOURLY_STATS
The PM_HOURLY_STATS variable is defined in the /usr/omc/config/global/OMC.CNFG file
and the /usr/omc/config/global/pmProcConfig.csh file. It determines the interval at which
the OMC-R receives BSS the statistical files.
The possible settings are:
ON sets the interval to 1 hour.
Any other value sets the interval to 30 minutes.
For a permanent change add the following statement to the file /usr/omc/config/global/pmProcConfig.csh:
setenv PM_HOURLY_STATS ON
An OMC stop/start is required.
PM_MAX_NEIGHBORS
The PM_MAX_NEIGHBORS variable defines the maximum number of cells in the network that
can have neighbor statistics enabled. The size of the PM database neighbor statistic table,
nbr_statistics, is defined as:
PM_MAX_NEIGHBORS*48*7
Where
is
48
7
the number of intervals in a day.

the number of days storage.
If too many cells have the neighbor statistics enabled, this table starts to fill up. When
nbr_statistics is 70 percent full, alarm 30026 is raised. When the table is 100 percent full, no
further neighbor statistics are parsed.
The number of enabled neighbor statistics should be adjusted to ensure that the table does
not become 100 percent full. Factors to take into account are: the number of cells for which
neighbor statistics are enabled; the statistics sampling interval (30 minutes or 1 hour); and the
number of days for which the statistics are kept. The maximum number of cells with neighbor
statistics enabled varies with the type of system:
On a Low-end system, the parser processes statistics for a maximum of 4000 neighbors per
network in a 30 minute interval. In this case PM_MAX_NEIGHBORS can be increased
to 4000.
On a Mid-capacity or High-end system, the parser processes statistics for a maximum of

92160 neighbors per network in a 30 minute interval. In this case PM_MAX_NEIGHBORS
can be increased to 92160.
Refer to Using neighbor statistics on page 13-91 for additional checks and procedures that must
be performed when modifying the PM_MAX_NEIGHBORS.
6-8
68P02901W19-S
Oct 2009
CFG_KEEP_STATS_FILE
This variable is defined in /usr/gsm/current/config/pmloader.cfg.
145|CFG_KEEP_STAT_FILE|1
Result: This will keep the Parsed file (bin file) and append parsed to the parsed file.
Usage of this flag:
Flag CFG_KEEP_STATS_FILE
Case:1
145|CFG_KEEP_STAT_FILE|0
Result: This Parsed file (bin file) is deleted.
CFG_KEEP_NMC_FILE
This variable is defined in /usr/gsm/current/config/pmloader.cfg.
Usage of this flag
Flag CFG_KEEP_NMC_FILE
Case:1
145|CFG_KEEP_NMC_FILE|0
Result: This NMC file is deleted.
Case 2:
145|CFG_KEEP_NMC_FILE|1
Result: This will keep the NMC file without deleting.
STATE_ON_AUDIT
The STATE_ON_AUDIT environment variable ensures that the device statistics on the MIB are
updated correctly after an audit. When this variable is set to 1, the OMC-R performs a state
resynchronization when an audit is completed.
The variable STATE_ON_AUDIT should be set to the same value in both the mibProcConfig.csh
and pmProcConfig.csh files.
SUB_RES_TIME
The SUB_RES_TIME variable defines the length of time the pm_main, waits for a reply from the
event manager. By default, this variable is set to 62 seconds.
68P02901W19-S
6-9
Oct 2009
MIB processes used by environment variables
UPL_KEEP_STATS_FILE
The UPL_KEEP_STATS_FILE variable is set to ON to maintain a copy of the
compressed statistics file. These compressed statistics files can be found in directories
/usr/omc/ne_data/raw_stats/100,0/BSS or /usr/omc/ne_data/raw_stats/100,0/RXCDR with
a .debugcompressfile extension.
The default value for the UPL_KEEP_STATS_FILE variable is OFF.

This section lists the user configurable environment variables, used by the MIB processes
interacting with the MIB database.
The default values of these environment variables are defined in the /usr/omc/current/config/env/mibProcConfig.csh file. To set a non-default value for any of these variables, modify
the /usr/omc/config/global/env/mibProcConfig.csh file.
AUTORESYNCDELAY
The AUTORESYNCDELAY environment variable is introduced to define the time required to
start the Network Resync on startup, if the Resync on startup flag is enabled in the Network
detailed view. This time lapse or delay is measured in minutes. The delay allows the connections
to NEs to be re-established after an OMC stop/start.
The default value for the AUTORESYNCDELAY variable is 0, and the maximum value is 10. If
the user sets a value more then 10 minutes, the delay will automatically reset to 0 minutes.
ATC_TIMEOUT
The ATC_TIMEOUT environment variable is set in the /usr/omc/current/config/env/mibProcConfig.csh file. To set a non-default value for any of these variables, modify the
/usr/omc/config/global/env/mibProcConfig.csh file.
The ATC_TIMEOUT environment variable is related to the neighbor propagation feature.
When a change is made to an attribute of a cell, the CM database propagates this change to all
the neighbors pointing to that cell. If any of the neighbors are in edit, the CM database retries
the propagation for the length of time specified by ATC_TIMEOUT. If this time exceeds, the
propagation fails for this neighbor.
The value of ATC_TIMEOUT is specified in tenths of a second. The default value is 1200.
If there are a large number of neighbors, RTFs or DRIs, then ATC_TIMEOUT needs to be
modified.
If ATC_TIMEOUT is not set, the system continues until each failed update has been retried
once, and then terminates.
AU_APPLY_DELETES_FIRST
The AU_APPLY_DELETES_FIRST variable is set to ON by default. This allows the audit process
to apply all delete actions before attempting create and update. It is not recommended to
change this environment variable.
6-10
68P02901W19-S
Oct 2009
CM_NMC_AUTO_NUM
The CM_NMC_AUTO_NUM variable is used for the OSI Q3 interface. Refer to Operating
Information: OSI System Administration (68P02901W10) manual for details.
CT_1208LOG
The CT_1208LOG variable is default set to $OMC_TOP/ne_data/ct_logs. This environment
variable specifies the location where the call trace logs are saved.
DBNAME
The DBNAME variable is default set to mib_db. This is the name of the CM database.
DEL_CELLX_FILES
The DEL_CELLX_FILES is used to set up the automatic deletion of CellXchange backup files,
which are stored in the directory /usr/omc/config/global/cellX.
By default the DEL_CELLX_FILES variable is set to OFF.
To switch on the auto-deletion of backup files, change DEL_CELLX_FILES from OFF to ON in
both of the following files:
/usr/omc/config/global/env/Common.csh
/usr/omc/config/global/env/Common.sh
When the DEL_CELLX_FILES variable is set to ON, any files with the .BACKUP extension in the
directory /usr/omc/config/global/cellX, which are over 30 days old, are deleted.
H2_DUALBAND
The H2_DUALBAND flag switches on MIB support for the Dual BAND Horizon II feature. By
default it is switched OFF.
To switch the H2_DUALBAND flag ON, change the H2_DUALBAND environment variable from
OFF to ON in the following files:
/usr/omc/current/config/Common.sh
/usr/omc/current/config/Common.csh
This requires an OMC stop/start.
INFORMIXDIR
The INFORMIX environment variable defines where the Informix software is installed on the
system. This variable is by default, set to /usr/informix.
68P02901W19-S
6-11
Oct 2009
NX_ENABLE_TIMESLOTS
The Upstream and Downstream TS MMS options are not available if the corresponding path
contains no time slot switch or multiple non-adjacent switches. To enable the Upstream and
Downstream TS MMS options, the NX_ENABLE_TIMESLOTS environment variable must be set.
Use the following procedure to enable the Upstream and Downstream TS MMS options:
Procedure 6-1
Enabling the Upstream and Downstream TS MMS options
Log on as omcadmin.

cd /usr/omc/config/global/env
Update the Common.sh file as follows:

NX_ENABLE_TIMESLOTS=1
export NX_ENABLE_TIMESLOTS
Update the Common.csh file as follows:

setenv NX_ENABLE_TIMESLOTS 1
Stop and start the OMC.
OMC_TOP
The OMC_TOP environment variable is used by the OMC-R software and, by default, is set to
/usr/omc.
PER_SITE_AUDIT
The PER_SITE_AUDIT flag switches on MIB support for the Per Site Audit feature. It requires an
OMC stop or start.
The PER_SITE_AUDIT environment variable default value is set in the /usr/omc/current/config/env/Common.csh file. To set a non-default value for any of these variables, modify the
/usr/omc/config/global/env/Common.csh file.
PER_SITE_AUDIT_DEBUG
The PER_SITE_AUDIT_DEBUG flag switches on debugging for the Per Site Audit feature. If this
flag is enabled, extra messages are output to the /usr/omc/logs/omcaudit<date> file during a
Per Site Audit.
Use the following procedure to enable PER_SITE_AUDIT_DEBUG:
Procedure 6-2
Enabling PER_SITE_AUDIT_DEBUG
Log on as omcadmin.

Continued
6-12
68P02901W19-S
Oct 2009
Procedure 6-2
GUI processes environment variables
Enabling PER_SITE_AUDIT_DEBUG (Continued)
Update the Common.sh file as follows:

PER_SITE_AUDIT_DEBUG=ON
export PER_SITE_AUDIT_DEBUG
Update the Common.csh file as follows:

setenv PER_SITE_AUDIT_DEBUG ON
RECIPROCATE_NBR
The RECIPROCATE_NBR determines if a Reciprocal Neighbor is automatically created when a
user creates a Neighbor for a cell. For example, when CELL B is defined as the Neighbor of
CELL A, the OMC-R assumes that CELL A is also the Neighbor of CELL B and creates the
Reciprocal Neighbor relationship between CELL A and CELL B. This RECIPROCATE_NBR
default set to TRUE.
USE_LONG_SITE_NAME
When the variable USE_LONG_SITE_NAME is set to ON, the operator is able to create a SITE
name of maximum 41 characters else it restricts to 31 characters.
If the OMC already has a SITE name with a maximum of 31 characters, set the
USE_LONG_SITE_NAME variable to ON to launch the OMC GUI.

This section lists the user configurable GUI processes environment variables.
These environment variables are defined in the /usr/omc/config/global/mmiProcConfig.csh
file.
ADDINFO_IN_HEX
This environmental variable is present in the /usr/omc/current/config/Common.csh file.
The ADDINFO_IN_HEX environment variable displays additional alarm information (with the
exception of EAS alarms) in hex. Additional information for EAS alarms is displayed in ASCII
text.
The ADDINFO_IN_HEX variable has a default value of 1 and a valid range of 0 or 1. To switch
off the additional alarm information, set this variable to 0.
ALG_WARNING
The ALG_WARNING by default set to Y. This environment variable determines whether or not a
warning should be issued on the last in-service ALG.
68P02901W19-S
6-13
Oct 2009
AUTO_GEN_RDN
The AUTO_GEN_RDN environment variable is used to enable or disable the automatic populate
of the Relative Distinguished Name (RDN) instance field with the next available RDN instance
when creating a device through the OMC-R GUI. This enables the OMC-R operator to create
devices in the correct order without having to find out what the next RDN instance number is in
the sequence. It also helps to prevent devices from being created out of sequence. Although
the RDN instance is created automatically, a different valid RDN instance can still be chosen
when creating a device.
The AUTO_GEN_RDN variable is set to 0 by default (disabled).
If this variable is set to 1, the Auto Generate RDN feature is enabled.
If this variable is set to any other value, the Auto Generate RDN feature is disabled.
Use the following procedure to enable the AUTO_GEN_RDN variable:
Procedure 6-3
Enabling AUTO_GEN_RDN
Login as omcadmin.

Update the file Common.sh as follows:

AUTO_GEN_RDN=1
export AUTO_GEN_RDN
Update the file Common.csh as follows:

setenv AUTO_GEN_RDN 1
Stop and restart the OMC-R as described in Manual startup and

shutdown of OMC-R software on page 7-12 to activate these changes.
AUTO_POP_CELLID
The AUTO_POP_CELLID environment variable is used to enable or disable the automatic
population of Cell IDs when creating an RTF in the RTF Detailed View. When enabled, the GSM
Cell ID field is auto populated with the Cell ID that the RTF Group belongs to, if an RTF has
already been created under an associated RTF Group. This saves time, as it is unnecessary
to enter details in the GSM Cell ID field for an RTF, other than the first radio equipped to
that RTF Group.
The AUTO_POP_CELLID variable is set to 0 by default (disabled).
6-14
If this variable is set to 1, the Auto Populate Cell ID feature is enabled.
If this variable is set to any other value, the Auto Populate Cell ID feature is disabled.
68P02901W19-S
Oct 2009
Use the following procedure to enable the AUTO_POP_CELLID:
Procedure 6-4
Enabling AUTO_POP_CELLID
Log on as omcadmin.

cd /usr/omc/current/config

AUTO_POP_CELLID=1
export AUTO_POP_CELLID

setenv AUTO_POP_CELLID 1

shutdown of OMC-R software on page 7-12 in order to activate these
changes.
AUTOSTART_PMGUI
This environment variable is associated with the PM GUI automatic start operation. By default it
is set to 0 (disabled).
AX_LANG
This variable is used to override the language used in the ax_prof file. See also the LANGUAGE
variable.
BSS_NAMING
This variable can be used to display BSS parameter names in the Detailed View. If BSS_NAMING
is set then the attributes are displayed with BSS names, otherwise they are displayed with
OMC names.
BSS_VER
This variable defines the BSS software version for example, BSGSM 1.8.0.0.
COUNTRY_CODE
The COUNTRY_CODE environmental variable is defined by the GSM operator license.
DBNAME
This variable defines the database name for example, omc_db.
68P02901W19-S
6-15
Oct 2009
DEF_GSM_CELL_ID
This environment variable is the default GSM Cell ID. It is set to the $COUNTRY_CODE$NETWORK_CODE-0000-000 variable by default.
DEFAULT_REMOVE_CLEARED_ALARM
This environment variable is associated with the Automatic Clearing of the Alarms operation. It
enables or disables the removal of a cleared alarm.
DEFAULT_REMOVE_CLEARED_ALARM_TIME
This environment variable is associated with the Automatic Clearing of the Alarms operation. It
sets the allowable interval, in seconds, to remove a cleared alarm.
DOUBLE_CLICK_NEXT
The DOUBLE_CLICK_NEXT environment variable is associated with the Map Display. By default
this variable is defined as FALSE (=0) (disabled).
ENABLE_AUTO_EMAIL_ON_REASSIGN
The ENABLE_AUTO_EMAIL_ON_REASSIGN environment variable is associated with the auto
e-mail on the Alarm Reassignment operation. It enables or disables the automatic e-mail
notification, to reduce the amount of e-mail being generated when alarms are reassigned. By
default this variable is defined as TRUE (=1) (enabled).
INFORMIXDIR
The INFORMIXDIR environment variable defines the path to where Informix is installed on the
system. By default, it is set to /usr/informix.
LANGUAGE
The LANGUAGE variable defines the language set used within the OMC-R.
6-16
68P02901W19-S
Oct 2009
MAXCHANGENOTIFYCALLS
This environment variable is present in the /usr/omc/current/config/Common.csh file. It
allows the OMC system administrator to specify the number of status queries processed by the
GUI. It has a default value of 1000.
NOTE
Motorola does not recommend modification of this variable from its default value.
Use the following procedure to set the value of the environment variable MAXCHANGENOTIFYCALLS:
Procedure 6-5
Setting the value of MAXCHANGENOTIFYCALLS
Login as user omcadmin on the single platform processor.
Locate the file: /usr/omc/config/global/env/Common.csh.
Add the following line at the end of the Common.csh file:

setenv MAXCHANGENOTIFYCALLS <value>.
All GUIs should be restarted in order to activate

MAXCHANGENOTIFYCALLS.
MMI_ALARM_STATE_WIDTH
The MMI_ALARM_STATE_WIDTH environment variable specifies the pixel width of the Alarm
State field. It has a default value of 110.
MMI_CLEAR_INACTIVE_FMIC
This environmental variable default value is set in the /usr/omc/current/config/env/pmProcConfig.csh file. To set a non-default value for this variable modify the
/usr/omc/config/global/env/Common.csh file.
This environment variable is set to TRUE for all users to enable all users to clear inactive
FMIC alarms from the system.
MMI_EVENT_ADDITIONAL_INFO_WIDTH
The MMI_EVENT_ADDITIONAL_INFO_WIDTH environment variable specifies the pixel
width of the Event Additional Information field. It has a default value of 180.
MMI_EVENT_ID_WIDTH
The MMI_EVENT_ID_WIDTH environment variable specifies the pixel width of the Event ID
field. It has a default value of 35.
68P02901W19-S
6-17
Oct 2009
MMI_EVENT_INFO_WIDTH
The MMI_EVENT_INFO_WIDTH environment variable specifies the pixel width of the Event
Information field. It has a default value of 650.
MMI_EVENT_OBJ_CLASS_WIDTH
The MMI_EVENT_OBJ_CLASS_WIDTH environment variable specifies the pixel width of the
Object Class field. It has a default value of 220.
MMI_EVENT_OBJ_INSTANCE_WIDTH
The MMI_EVENT_OBJ_INSTANCE_WIDTH environment variable specifies the pixel width of
the Object Instance field. It has a default value of 180.
MMI_EVENT_OPERATOR_NAME_WIDTH
The MMI_EVENT_OPERATOR_NAME_WIDTH environment variable specifies the pixel width
of the Operator Name field. It has a default value of 80.
MMI_EVENT_TIME_WIDTH
The MMI_EVENT_TIME_WIDTH environment variable specifies the pixel width of the Event
Time field. It has a default value of 120.
MMI_EVENT_TYPE_WIDTH
The MMI_EVENT_TYPE_WIDTH environment variable specifies the pixel width of the Event
Type field. It has a default value of 165.
MMI_EVT_FILTER_NUM_LOGS
This environment variable defines the number of filter event logs. It has a default value of 2.
MMI_START_WINDOW_AS_UNSPLIT
The MMI_START_WINDOW_AS_UNSPLIT environment variable determines whether the
Alarm window will start as split or unsplit. Values:
NULL: The alarm window starts as normal (split).
NOT NULL: The alarm window starts as unsplit.
NETWORK_CODE
As defined by customer.
6-18
68P02901W19-S
Oct 2009
OMCAUDIBLESEVERITY
The OMCAUDIBLESEVERITY environment variable affects the generation of the alarm as
well as the alarm severity. A beep is emanated from the sound card as the alarm is generated
and a hooter sets off the distinctive alarm sound depending upon the severity of the alarm.
Both these operations are dictated by the values of the GUI process environment variable,
OMCAUDIBLESEVERITY.
The valid range for this environment variable is 0 to 3 which indicates:
If this variable is set to zero, the hooter will sound for critical, major, and minor alarms and
the OMC-R will beep for critical, major, minor, and investigate alarms.
If this variable is set to one, the hooter will never sound and the OMC-R will beep for
critical alarms.
If this variable is set to two, the hooter will sound for critical alarms and the OMC-R will
beep for critical and major alarms.
If this variable is set to three, the hooter will sound for critical and major alarms and the
OMC-R will beep for critical, major, and minor alarms.
The various alarm severities are described in Maintenance Information: Alarm Handling at
the OMC-R (68P02901W26) manual.
OMCFEATURES
This environment variable enables or disables the OMC-R features.
OMCREDRAW
The OMCREDRAW environment variable enables the map to display an update in the same
window when either Next or Previous is selected from the View menu.
OMC_TOP
The OMC_TOP environment variable is used by the OMC-R software and, by default, is set to
/usr/omc.
PRINTER
The PRINTER variable specifies the printer device used for printing. By default, PRINTER
is set to lp, allowing a user to print to the printer device lp.
REGION
The REGION environment variable determines whether regions are used in the OMC-R GUI.
The default value is 0 (disabled).
68P02901W19-S
6-19
Oct 2009
RESYNC_LOCKING
The RESYNC_LOCKING environment variable value is by default located in the
/usr/omc/current/config/env/Common.csh file. To set a non-default value for this variable,
modify the /usr/omc/config/global/env/Common.csh file. The variable is used by the OMC-R
software to allow or prevent any other operation to be run parallel with a Resync operation.
The RESYNC_LOCKING variable is set to 0 by default (disabled).
If this variable is set to 1, Resync Locking is enabled.
If this variable is set to 0, Resync Locking is disabled and any operation can run in parallel
with a Resync operation.
Use the following procedure to enable RESYNC_LOCKING:
Procedure 6-6
Enabling AUTO_GEN_RDN
Log on as omcadmin.


RESYNC_LOCKING=1
export RESYNC_LOCKING

setenv RESYNC_LOCKING 1

shutdown of OMC-R software on page 7-12 to activate these changes.
SCROLL_TO_BOTTOM
The SCROLL_TO_BOTTOM environment variable is associated with the PLMN alarm window.
When SCROLL_TO_BOTTOM is set to TRUE, the alarms output is pushed to the bottom of
the alarm window so that the latest alarm can be viewed immediately on opening the PLMN
alarm window. The default value is FALSE. To reconfigure this variable use Procedure 1 in
Changing an environment variable on page 6-26.
SITE_NAMING
This environment variable is associated with the Navigation Tree Site Name IDs. The default
value is 0 (disabled).
TTY_FILTER
The TTY_FILTER environment variable is used to enable remote login sessions to filter
asynchronous output from the BSS. The variable can be set to 0 or 1, and by default the variable
is set to 1, which displays all output arriving from the BSS.
6-20
68P02901W19-S
Oct 2009
RLOGIN variables
RLOGIN variables
The Remote Login variables are set in the $OMC_TOP/config/global/OMC.CNFG file.
RL_LOGCMDS
The RL_LOGCMDS environment variable controls the logging facility of the BSS commands. It
has a default value of YES (ON) and valid options of YES or NO.
This variable takes precedence over the variable RL_LOGRESPS: if RL_LOGCMDS is set to
NO and RL_LOGRESPS set to YES then no logging is performed. To reconfigure this variable
refer to procedure 2 in Changing an environment variable on page 6-26.
RL_LOGRESPS
The RL_LOGRESPS environment variable enables logging of the BSS command responses. If
set to YES then any responses are logged along with the commands.
It has a default value of NO (not to log the responses) and valid options of YES or NO.
The variable RL_LOGCMDS takes precedence over this variable. If RL_LOGCMDS is set to NO
and RL_LOGRESPS is set to YES then no logging is performed. To reconfigure this variable,
use procedure 2 in Changing an environment variable on page 6-26.
RL_SESSIONS
The RL_SESSIONS environmental variable specifies the maximum number of simultaneous
remote login sessions allowed.
The valid range of values for this variable is between 1 and 90.
If the environmental variable is not set, or is set to an invalid value, the default value of 60 is
used. To reconfigure this variable, use procedure 2 in Changing an environment variable on
page 6-26.
RL_TIMER_DT
The RL_TIMER_DT environment variable is used as a timeout value for data transfer. If this
timer value is exceeded, the user is logged out of their remote login session.
It has a default value of 1200 seconds and a range of any positive or negative value or 0. Setting
this environment variable to any non positive value (including zero) results in no timeout
supervision being performed. To reconfigure this variable, use procedure 2 in Changing an
environment variable on page 6-26.
68P02901W19-S
6-21
Oct 2009
FM_audit variables
RL_TIMER_NC
The RL_TIMER_NC environment variable is used as a timeout variable for the X.25 connection
establishment phase.
It has a default value of 25 seconds and a valid range of any positive integer. The default
value is used if the environment value is set to a non positive value (including zero) results in
the default value being used. To reconfigure this variable use procedure 2 in Changing an
environment variable on page 6-26.
FM_audit variables
The FM_audit variables are set in the $OMC_TOP/config/global/FM_audit.CNFG file.
FM_CPU_AUDIT
The FM_CPU_AUDIT environment variable controls whether a CPU audit is run.
If set to YES then Critical or Major alarms is raised if the CPU load goes above thresholds that
are set in the FM_audit.CNFG file.
It has a default value of NO (OFF) and provides valid options of NO or YES.
To reconfigure the variable, use procedure 2 in Changing an environment variable on page 6-26.
(where FMMGR is the mnemonic process).
FM_MEM_AUDIT
The FM_MEM_AUDIT environment variable controls whether a Memory audit is run.
If set to YES then Critical/Major alarms is raised if Memory usage goes above thresholds that
are set in the FM_audit.CNFG file.
It has a default value of NO (OFF) and valid options of NO or YES.
To reconfigure the variable use procedure 2 in Changing an environment variable on page 6-26.
(where FMMGR is the mnemonic process).
FM_IERROR_ALLOWED
The FM_IERROR_ALLOWED environment variable specifies the number of input packet errors
that are permitted within a sample period before an alarm is triggered.
The default is 0, meaning that the alarm is triggered by just one error.
FM_OERROR_ALLOWED
The FM_OERROR_ALLOWED environment variable specifies the number of output packet
errors that are permitted within a sample period before an alarm is triggered.
6-22
68P02901W19-S
Oct 2009
CSMMAIN variables
FM_OHUNG_ALLOWED
The FM_OHUNG_ALLOWED environment variable specifies the number of transmit hung
errors that are permitted within a sample period before an alarm is triggered.
CSMMAIN variables
The Call Success Monitoring process (CSMMAIN) requires three variables that are set in the
$OMC_TOP/config/global/omc.CNFG file.
To reconfigure these variables, use procedure 2 in Changing an environment variable on page
6-26. (where CSMMAIN is the mnemonic process).
CSM_ENABLED
The CSM_ENABLED environment variable controls the way in which the Call Success
Monitoring (CSM) feature is used. It is a three digit binary number in which each digit can be
set to 1 to enable a CSM function, or zero to disable that function:
If all three digits are set to zero, CSM is disabled (the default).
If the first digit is set to 1, CSM is enabled for sleeping cell detection.
If the second digit is set to 1, CSM is enabled for sleeping carrier detection.
If the third digit is set to 1, CSM is enabled for sleeping timeslot detection.
The system allows any combination of the three functions to be enabled.
CALL_SUCCESS_THRESHOLD
The CALL_SUCCESS_THRESHOLD environment variable defines the minimum acceptable
percentage of successful calls per cell. The default is 80%.
This is used to detect sleeping carriers. If the call success rate falls below this threshold, the
CSMMAIN process generates an alarm. This variable is set once per network and cannot
be set on an individual cell basis.
MIN_TOTAL_CALLS
The MIN_TOTAL_CALLS environment variable determines the minimum total number of calls
that must be made on a cell before the CSMMAIN process tries to detect a sleeping carrier.
The default is 25.
This variable ensures that CSMMAIN does not raise an alarm when there are very few calls on
a cell in an interval.
68P02901W19-S
6-23
Oct 2009
ResyncCtrl variables
ResyncCtrl variables
The environment variables that the Resync Control feature uses, are contained in the following
file on the system processor: /usr/omc/config/global/RC.CNFG
The ResyncCtrl process periodically reads the RC.CNFG file, so unlike other environment
variables, any variables changed in this file are picked up without having to perform an OMC-R
software stop and start.
AUTORESYNC
The environment variable AUTORESYNC enables remote sites to be resynchronized to the
OMC-R automatically if, for example, a link malfunctions between the two and then comes
back into service.
The AUTORESYNC variable can be set to Y or N to enable or disable autosynchronization and
automatically defaults to Y if it is not selected. Autosynchronization occurs automatically,
regardless of the setting of the environment variable ENABLERESYNC.
If AUTORESYNC is set to Y, MAX_RESYNCS is set to 10 and MAX_AUTO_RESYNCS is set
to 2, then a maximum of ten resync control variables are processed at a time. Out of the ten
variables, two slots are allotted to auto resync and the remaining eight slots for manual resync.
If AUTORESYNC is set to N and MAX_RESYNCS equals 10, then all the ten resync slots are
used for manual resync. No auto resync is processed as it is disabled.
ENABLERESYNC
The environment variable ENABLERESYNC can be set to Y or N to turn resynchronization ON
or OFF. By default this is set to N.
MAX_RESYNCS
This variable is used to define the number of active resyncs allowed to happen at a time. The
active resync table is defined based on this variable. The default value is 10. The range of
values allowed for MAX_RESYNCS is 1 to 15. If MAX_RESYNCS is out of this range, then
this variable is set to a default value of 10.
MAX_AUTO_RESYNCS
This variable is used to define the number of auto resync allowed to happen at a time. The default
value is 2. The range of values allowed for MAX_AUTO_RESYNCS is 1 to MAX_RESYNCS 1.
If MAX_AUTO_RESYNCS is out of this range, then this variable is set to a default value of 2.
If MAX_AUTO_RESYNCS is set greater than or equal to number of MAX_RESYNCS, then the
default value is used for both, MAX_RESYNCS and MAX_AUTO_RESYNCS.
TIMER
The environment variable TIMER sets the duration Resync Control waits for a resync to
complete. It specifies the time in seconds.
The duration is set between the values 150 and 3600. By default it is set to 600.
6-24
68P02901W19-S
Oct 2009
OMC-R Startup/Shutdown Timers
OMC-R Startup/Shutdown Timers

OMCINIT_DYING_TIME
The variable OMCINIT_DYING_TIME indicates the maximum time given for a process to
cleanup and exit gracefully. It is used by OMC-R processes during OMC shutdown.
The default value is 30 as per GSR9 1900.34 load, when this timer was introduced. The default
value is 40 as per GSR9 1900.35 load onwards.
This parameter is user configurable and is present in the file /usr/gsm/current/config/INIT.CNFG.
In case the processes need more time to exit gracefully the timer value can be increased suitably.
Follow Procedure 6-7 to increase the timer value:
Procedure 6-7
68P02901W19-S
Increasing the timer value
Login as omcadmin
OMC stop
Increase the value of OMCINIT_DYING_TIME in

/usr/gsm/current/config/INIT.CNFG
OMC start
6-25
Oct 2009
Changing an environment variable
Changing an environment variable
Methods for changing an environment variable

To Change an environmental variable, use of one of the two methods.
Method 1
Used for changing an environment variable in any of the following files:
/usr/omc/config/global/env/mmiProcConfig.csh
/usr/omc/config/global/env/pmProcConfig.csh
/usr/omc/config/global/env/mibProcConfig.csh
Method 2
Used for changing an environment variable in the following file:
OMC.CNFG
Method 1
The method involves the following:
Edit the customizable version of the .csh file in /usr/omc/config/global/env where the
variable is defined and make the necessary change. If turning off an environment variable,
it is not sufficient to remove the line or comment it out. Instead comment out the old line
and add a new line containing an unsetenv <variable_name>.
Stop the OMC-R by issuing the omc stop command.
Log out and logging back in again. This sources the environment files automatically.
Restart the OMC-R by issuing the omc start command.
Verify whether the variable is set up correctly by echoing it to the screen.
For example, use the following procedure to modify the ATC_TIMEOUT variable:
Procedure 6-8
Changing an environment variable using Method 1 (Example 1)
Login as omcadmin on the system processor and change the directory:

cd /usr/omc/config/global/
Modify the ATC_TIMEOUT environment variable in the

mibProcConfig.csh file using the vi editor.
Continued
6-26
68P02901W19-S
Oct 2009
Procedure 6-8
(Continued)
The change is automatically propagated to the mibProcConfig.sh file.

Use the following command to edit the file:
vi mibProcConfig.csh
3
Stop the OMC-R as described in Manual startup and shutdown of

OMC-R software on page 7-12.
Log out and login again.
In a new Xterm window, login as omcadmin and check if a new value

is assigned:
echo $ATC_TIMEOUT
In the same window, restart the OMC-R as described in Manual startup

and shutdown of OMC-R software on page 7-12.
Method 2
The method involves the following:
Login as omcadmin and edit the appropriate environment variable within the OMC.CNFG
file.
Use the utility omctool to reconfigure the process associated with this environment
variable. The process can be defined by its mnemonic name. An example is the RLOGIN
mnemonic process. For more information on mnemonic processes, see omctool utility in
the Restartable processes on page 2-49 section.
OMCINIT periodically polling selected processes to check for particular external events
that may have occurred. Reconfiguration occurs at the next poll.
Example 1: The following procedure modifies the RL_LOGCMDS variable:
Procedure 6-9
Login as omcadmin on the system processor and change directory:

Modify the RL_LOGCMDS entry in the OMC.CNFG file using the vi

editor:
vi OMC.CNFG
Invoke the omctool utility using the following parameters:

omctool -m RLOGIN -c
Reconfiguration takes place at the next poll.
Example 2: The following procedure modifies the CSMMAIN variables:
68P02901W19-S
6-27
Oct 2009
Procedure 6-10
Login as omcadmin on the system processor and change directory

as follows:
Modify the CSMMAIN variables in the OMC.CNFG file using the vi

editor:
vi OMC.CNFG
Invoke the omctool utility with the appropriate parameters:

omctool -m CSMMAIN -c
Reconfiguration happens at the next poll.
Example 3: The following procedure modifies the Parser variables:
Procedure 6-11
6-28
Login as omcadmin on the system processor and change the directory

as follows:
Modify the Parser variables in the OMC.CNFG file using the vi editor:
vi OMC.CNFG
Invoke the omctool utility using the following parameters:

omctool -m PARSER_1 -c
Reconfiguration happens at the next poll.
68P02901W19-S
Oct 2009
Setting the status of the Consolidated Alarms
Setting the status of the Consolidated Alarms
Introduction to setting the status of the Consolidated Alarms

The CONSOLIDATION environment variable sets the status of the Consolidated Alarms. The
status of the Consolidated Alarms is set up in the following files:
/usr/omc/config/global/env/pmProcConfig.csh
/usr/omc/config/global/env/mibProcConfig.csh
/usr/omc/config/global/env/mmiProcConfig.csh
There are three possible levels of consolidation:
Level 1
The device mode map is default, secondary alarms are displayed. The line entry value in
the three files is SETENV CONSOLIDATION 1.
Level 2
The device mode map is default, secondary alarms are suppressed. The line entry value in
the three files is SETENV CONSOLIDATION 2.
Level 3
The subscriber mode map is default, secondary alarms are suppressed. The line entry
value in the three files is SETENV CONSOLIDATION 3.
NOTE
Refer to OMC-R Online Help, Network Operation manual for the Consolidated
Alarms operation.
Setting status of the consolidated alarms

Use the following procedure to set the status of the Consolidated Alarms.
Procedure 6-12
1
Setting the status of consolidated alarms
Login to the system processor as omcadmin and change the directory

as follows:
Continued
68P02901W19-S
6-29
Oct 2009
Disabling the status of consolidated alarms
Procedure 6-12
Setting the status of consolidated alarms (Continued)
Open the pmProcConfig.csh file using the vi editor:

vi pmProcConfig.csh
Enter the following line entry at the end of the file:

SETENV CONSOLIDATION <x>
Where <x> is:
1 for Level 1.
2 for Level 2.
3 for Level 3.
Close the pmProcConfig.csh file using the vi editor.
Repeat step 1 to step 3 for the files mibProcConfig.csh and

mmiProcConfig.csh files.

changes.
Restart all the GUI servers or clients.
Disabling the status of consolidated alarms

Use the following procedure to disable the status of the consolidated alarms:
Procedure 6-13
Disabling the status of the consolidated alarms
Login to the system processor as omcadmin and change the directory

as follows:
Open the pmProcConfig.csh file using the vi editor:

vi pmProcConfig.csh
Delete the SETENV CONSOLIDATION <x> line entry and enter the
following line entries:
vi pmProcConfig.csh
Where <x>is:
1 for Level 1.
2 for Level 2.
3 for Level 3.
UNSETENV CONSOLIDATION
Close the pmProcConfig.csh file using the vi editor.
6-30
Repeat step 1 to step 3 for the files mibProcConfig.csh and

mmiProcConfig.csh files.

changes.
Restart all the GUI server or clients.
68P02901W19-S
Oct 2009
Non user configurable environment variables
Non user configurable environment variables

Non user configurable environment variables for the OMC-R applications are defined in the
following files:
/usr/omc/current/config/env/Common.csh
Defines the variables used by the system processes.
/usr/omc/current/config/env/mmiProcConfig.csh
Defines the variables used by the GUI processes, which interact with the GUI server or
clients.
There are .sh versions of these files (Bourne Shells), which are automatically updated if changes
are made in the .csh versions.
NOTE
The variables should only be changed by qualified personnel under guidance from
Motorola Support. Any unauthorized changes may not be supported by Motorola and
may result in system and/or performance degradation. Contact Motorola Support
for further information.
The non-user configurable environment variables that are specified in the
/usr/omc/current/config/env/Common.csh file are listed in Table 6-1.
Table 6-1
Nonuser configurable variables in the Common.csh file
Variable name
Value
ADMIN_BIN
$ADMIN_ROOT/sbin
ADMIN_ROOT
$OMC_TOP/current
AUDITDIR
$OMC_TOP/logs
AU_ALF_DIR
$OMC_TOP/logs/ListDir
CMAUDITDIR
$OMC_TOP/logs
CMUTIL_LOG
$OMC_TOP/logs
CM_CFG_GLOB
$OMC_TOP/config/global
CM_LOG
$OMC_TOP/logs
CM_ROOT
$OMC_TOP/current
COMMS_LOG
$OMC_TOP/logs
Continued
68P02901W19-S
6-31
Oct 2009
Table 6-1
Nonuser configurable variables in the Common.csh file (Continued)
Variable name
Value
COMMS_ROOT
$OMC_TOP/current
{34164}
CRITICAL_STATS_LOG
$OMC_TOP/ne_data/critical_stats
CT_LOG
$OMC_TOP/ne_data/ct_logs
DATAGENHOST
Host name of DataGen processor (if DataGen is enabled)
DBDATE
DMY4-
DBMS_LOG
$OMC_TOP/logs
DBMS_ROOT
$OMC_TOP/current
DBNAME
/mib_db
DBPATH
//omc_sys
DBROOT
$OMC_TOP/ne_data/dbroot
DEFAULT_SHUTDOWN_TIME
30
EM_LOG
$OMC_TOP/ne_data/ev_logs
EM_POLL_COUNT
800
EM_ROOT
$OMC_TOP/current
EM_RX_QSIZE_ALARM
5120
EM_RX_QSIZE_FLUSH
10240
EM_TX_QSIZE_MMI
5120
FMPATH
$OMC_TOP/ne_data/raw_stats
GLOBAL_LOG_DIR
$OMC_TOP/logs/ipc
INFORMIXDIR
/usr/informix
IPC_CONFIG
/usr/omc/current/config/ipc.cfg
IPC_HELP_TEXT
$CM_ROOT/config/ipc_help2.txt
LDM_LOG
$OMC_TOP/logs
LDM_ROOT
$OMC_TOP/current
LMAUDITDIR
$OMC_TOP/logs
LMBINDIR
$OMC_TOP/current/bin
LMDATA
$OMC_TOP/current/config
LMTEMPDIR
$DBROOT/tmp
LOG_TO_SCREEN
NUMBER_OF_RETRIES
720
OMC_IPC_CONFIG
$SYS_CONFIG/ipc.cfg
OMC_SYSTEM_CONFIG
$SYS_ROOT/config/system_config
OMC_SYSTEM_RAW_CONFIG
$SYS_ROOT/config/sys_raw_cfg
Continued
6-32
68P02901W19-S
Oct 2009
Table 6-1
Nonuser configurable variables in the Common.csh file (Continued)
Variable name
Value
OMC_TOP
/usr/omc
PM_ASYNC_LOG
$OMC_TOP/logs
PM_LOG
$OMC_TOP/logs
PM_LOG_FILE
$PM_LOG
PM_PARSER_LOG
$PM_LOG
PM_ROOT
$OMC_TOP/current
PS
ps -ef
RETRY_TIMEOUT
15
RL_BSSLOGDIR
$OMC_TOP/logs/bss
RL_TIMER_IPC
60
SYS_BIN
$SYS_ROOT/bin
SYS_CONFIG
$SYS_ROOT/config
SYS_LOG
$OMC_TOP/logs
SYS_ROOT
$OMC_TOP/current
UNLOAD_DIR
$OMC_TOP/ne_data/unload_stats
The non-user configurable environment variables that are specified in the

/usr/omc/current/config/env/mmiProcConfig.csh file are listed in Table 6-2.
Table 6-2
Nonuser configurable variables in the mmiProcConfig.csh file
Variable name
Value
OMC_TOP
/usr/omc
ADMIN_BIN
$ADMIN_ROOT/sbin
ADMIN_ROOT
$OMC_TOP/current
APPLIX
$OMC_TOP/current/bin/PMGUI
AUDITDIR
$OMC_TOP/logs
AUTO_GEN_RDN
AUTO_POP_CELLID
AXHOME
$OMC_TOP/current/bin/axhome
BATCH_IPC_TIMEOUT
600
BATCH_NERESP_TIMEOUT
30
BSS_VER
BSGSM_1.6.0.x
CMAUDITDIR
$OMC_TOP/logs
CM_LOG
$OMC_TOP/logs
CM_ROOT
$OMC_TOP/current
Continued
68P02901W19-S
6-33
Oct 2009
Table 6-2 Nonuser configurable variables in the mmiProcConfig.csh file

(Continued)
Variable name
Value
CMUTIL_LOG
$OMC_TOP/logs
COMMS_LOG
$OMC_TOP/logs
COMMS_ROOT
$OMC_TOP/current
CURRENT
$OMC_TOP/current
DBNAME
omc_db
DBPATH
//omc_sys
DBROOT
$OMC_TOP/ne_data/dbroot
DOUBLE_CLICK_NEXT
EM_LOG
$OMC_TOP/ne_data/ev_logs
EM_ROOT
$OMC_TOP/current
ENABLE_ACCESS_LOG
EP_ALARM_SUB_LIST_NAME
.$MAP_ALARMS
EP_EVENT_SUB_LIST_NAME
.$EP_EVENTS
EP_IPCQ_READ_TIMEOUT
EP_NUMBER_IPCQ_READS
10
INFORMIXDIR
/usr/informix
IPC_CONFIG
$SYS_CONFIG/ipc.cfg
IPC_HELP_TEXT
$CM_ROOT/config/ipc_help2.txt
LDM_LOG
$OMC_TOP/logs
LDM_ROOT
$OMC_TOP/current
LISTTMPDIR
$OMC_TOP/logs/ListDir
LOG_TO_SCREEN
MMI_ALARM_PIXMAP
siren_on
MMI_ALM_DEFAULT_SUBSLIST
_NAME
.$ALM_ALARMS
MMI_DAEMON
/usr/omc/current/bin/mmi_daemon
MMI_EVT_DEFAULT_SUBSLIST
_NAME
.$EVT_EVENTS
MMI_LOG
$OMC_TOP/logs
MMI_NO_ALARM_PIXMAP
siren_off
MMI_OOS_ON_PIXMAP
oos_pixmap_on
MMI_OOS_PIXMAP
oos_pixmap
MMI_OOS_SUB_NAME
.$SC_EVENTS
MMI_PRIMARY_FONT
-*-helvetica-medium-r-normal*-140-*
Continued
6-34
68P02901W19-S
Oct 2009
Table 6-2 Nonuser configurable variables in the mmiProcConfig.csh file

(Continued)
Variable name
Value
MMI_ROOT
MSGDIR
$COMMS_ROOT/config
NMSCONFIG
$NMSROOT/config
NMSROOT
$OMC_TOP/current
NS_ID
900
NS_MACHINE
localhost
NS_PORT_NUM
9001
OMCCONFIG
$NMSROOT/config/nms.cfg
OMC_HELP_PATH
$OMC_TOP/config/local/help
OMC_IPC_CONFIG
$NMSROOT/config/ipc.cfg
OMCTOP
$OMC_TOP
PMGUI
/usr/omc/current/bin/PMGUI
PM_ASYNC_LOG
/usr/omc/logs
PM_LOG
$OMC_TOP/logs
PM_LOG_FILE
/usr/omc/log
PM_PARSER_LOG
/usr/omc/logs
PM_ROOT
$OMC_TOP/current
SITE_NAMING
SYS_BIN
$SYS_ROOT/bin
SYS_CONFIG
$SYSROOT/config
SYS_CONFIG_BATCH
$OMC_TOP/config/global/batch
SYS_CONFIG_BATCH_OUTPUT
$OMC_TOP/config/global/batch
SYS_LOG
$OMC_TOP/logs
SYS_ROOT
$OMC_TOP/current
TTY_FILTER
UIDPATH
$MSCONFIG/uid/%U
USE_CACHE
XAPPLRESDIR
XPATH
/usr/openwin/bin
68P02901W19-S
6-35
Oct 2009
Setting the time for the OMC-R and NEs
Setting the time for the OMC-R and NEs
Reason for setting the system time

To ensure that statistics are correctly parsed, and that log file entries appear with the correct
time against them, it is important that the time of NEs and all processors at the OMC-R are
kept consistent.
Overview of setting the time at the OMC-R and NEs

This section describes the following procedures:
Resetting the time and time zone at the OMC-R.
Setting up a cron job to keep the GUI time synchronized to the system processor time.
Setting up a cron job to synchronize the NE time with the time at the OMC-R.
Resetting the time

The system processor is the master clock server. The system date (which in UNIX means the
date and time) on the system processor is the default time setting for the OMC-R network.
Use the following procedure to display the current system date.
Procedure 6-14
1
Display the current system date

date -u
This displays the date and time in GMT:
Thu Dec 11 14:56:51 GMT 2003
The time may be set to GMT or set to local time.
NOTE
Entering date on the command line results in the date
and time being displayed according to what is specified in
/etc/default/init. This is the local time. For example,
Thu Dec 14 14:56 SGT 2005
6-36
68P02901W19-S
Oct 2009
Configuring system time to GMT
Configuring system time to GMT

To configure the system time to GMT, set the time on all the machines, taking particular care to
set the system processor time accurately. Use the following procedure on each processor to
configure the system time:
Procedure 6-15
Configuring the system time to GMT
Login as root.
Change the processor time using the following command:

date -u <hhmm>
For example, date -u 2259 sets the time to 22:59 GMT. The command
sets time to the nearest minute.
Ensure that date -u shows the same time on all processors (to within
one or two minutes).
The GUI processor clocks must be set to the same time as the system
processor clock whenever the system processor clock is changed.
Configuring system time to local time

To configure the system time to local time, set the time on all the machines, taking particular
care to set the system processor time accurately. Use the following procedure on each processor
to configure the system time to local time.
Procedure 6-16
Configuring the system time to local time
Login as root.
Change the processor time using the following command:

date <hhmm>
For example, date 2259 sets the time to 22:59 local time. The
command sets time to the nearest minute.
Ensure that date shows the same time on all processors (to within
one or two minutes).
The GUI clocks must be set to the same time as the system processor
clock whenever the system processor clock is changed.
Default time zones in OMC-R

In UNIX, a time zone is a compiled data file containing information about the offset from GMT,
which is applied. The offset may vary at different times of the year.
The time zone files are in the /usr/share/lib/zoneinfo directory. Reference the files in this area
for a list of precompiled time zones.
68P02901W19-S
6-37
Oct 2009
Non default time zones in OMC-R without daylight saving
Non default time zones in OMC-R without daylight saving

There are a number of other GMT time zones without daylight saving rules. Their use is not
recommended because they do not support daylight saving.
If the desired time zone has not already been compiled, view the appropriate source file
from the following:
Africa
Asia
Australia
Europe
North America
South America
NOTE
Do not try to view files starting with capital letters. These are compiled time zone
files, and they corrupt the terminal display.
The uncompiled time zone file has to be compiled before it is used. Use the following commands
to compile the file:
cd /usr/share/lib/zoneinfo
zic <source_filename>
where source_filename is the name of the source file. For example, Asia.
The compiled data files are stored in the directory /usr/share/lib/zoneinfo/<source_filename.
For example, if the source file is Asia then the directory is /usr/share/lib/zoneinfo/asia. This
setup must be repeated for each processor in the OMC-R.
In the time zone file, search for the appropriate country or city name. The NAME of the zone is
used as a time zone. For example, the entry for India reads:
# India
# Zone
Zone
NAME
GMTOFF
Asia/Calcutta
5:30
RULES
-
FORMAT [UNTIL]
IST
This shows that the time zone name for Calcutta is Asia/Calcutta. In addition, it shows that the
zone Asia/Calcutta offset 5 hours and 30 minutes ahead of GMT. The letters displayed are IST.
Once the time zone is set, it is advisable to check to see if the time zone works as expected. To
check if a time zone is behaving correctly, see Checking the time zone.
6-38
68P02901W19-S
Oct 2009
Non default time zones in OMC-R with daylight saving
Non default time zones in OMC-R with daylight saving

There are a number of other GMT time zones with daylight saving rules. Their use is
recommended because they support daylight saving.
If the desired time zone has not already been compiled, view the appropriate source file
from the following:
Africa
Asia
Australia
Europe
North America
South America
NOTE
Do not try to view files starting with capital letters as these are compiled time zone
files, and corrupt the terminal display.
The uncompiled time zone has to be compiled before it can be used. Use the following
commands to compile the file:
cd /usr/share/lib/zoneinfo
zic <source_filename>
where <source_filename> is the name of the source file. For example, Europe. The compiled
data files are stored in the directory /usr/share/lib/zoneinfo/<source_filename>.
For example, if the source file is Europe then the directory is /usr/share/lib/zoneinfo/Asia>.
This setup must be repeated for each processor in the OMC-R. In the time zone file, search for
the appropriate country or city name. The NAME of the zone may be used as a time zone. For
example, the entry for Sweden includes daylight saving rules:
# Sweden
# Zone
Zone
NAME
GMTOFF
Europe/Stockholm
1:00
1:00
RULES
-
FORMAT [UNIL]
MET
M-Eur
1980 Apr
2:00
MET%s
In the example, the time is one hour ahead of GMT, and is called MET. During summer, a prefix
is added to indicate daylight saving. This prefix is indicated by %s. Daylight saving for this
example follows the M-Eur rules.
68P02901W19-S
6-39
Oct 2009
Setting the time zone
Europe file format

These rules are given elsewhere in the Europe file. The Europe file contains daylight saving
settings. These settings follow the M-Eur rules. The Europe file is given as follows:
# Rule
NAME
FROM
TO
AT
SAVE
Rule
M-Eur
1981
max
TYPE
-
IN
Mar
lastSun
ON
2:00s
1:00
Rule
M-Eur
1996
max
Oct
lastSun
2:00s
LETTER/S
DST
-
The first rule detailed in this file denotes the following:
Daylight saving starts at 02:00 on the last Sunday in March.
At 02:00 on the last Sunday in March the clock is advanced one hour.
The daylight saving suffix is DST.
The second rule detailed in this file denotes the following:
Daylight saving ends at 02:00 on the last Sunday in October.
Once the time zone is set, it is advisable to check to see if the time zone works as expected.

Use the following procedure to set the time zone:
NOTE
This procedure requires all processors at the OMC-R to be rebooted.
Procedure 6-17
1
Login to each processor (System and GUIs) as user root and edit the
/etc/default/init file to contain the line:
TZ=<time zone>
Where <time zone> is the selected time zone. Examples:
To use Middle European Time (MET), enter:
TZ=MET
To use a city-specific time zone, enter the complete zone name:
TZ=<continent>/<city>
To set the time zone for Calcutta, enter:
TZ=Asia/Calcutta
Continued
6-40
68P02901W19-S
Oct 2009
Procedure 6-17
Synchronizing the time at the OMC-R
Setting the time zone (Continued)
NOTE
This form of time zone must first be compiled on all
processors using zic.
2
Stop the OMC-R processes. Log in to the system processor as

omcadmin, and enter the following command:
omc stop
As <root> on the system processor and all the GUI processors, reboot
the respective machines using the shutdown command:
/usr/sbin/shutdown -g0 -i6 -y
After all the machines have restarted, log in as <omcadmin> on the

system processor and enter the following command:
omc stop
Wait until the OMC-R processes have stopped (OMC-R processes
attempt to start when the system processor reboots).

omc start
To confirm if the new time zone has taken effect, enter the following
command:
date

The timesynch script synchronizes the GUI processor clock with the clock on the system
processor.
NOTE
It is strongly recommended that the timesynch script should be run on all the
OMC-R systems.
The timesynch script should be run at a period of low activity. For example, daily at 30 minutes
past midnight.
Use the following procedure to check if the timesynch script has been set up as a cron job on
every GUI processor and indicates suitable parameters.
Procedure 6-18
1
Login as root on the relevant GUI processor.

Continued
68P02901W19-S
6-41
Oct 2009
Synchronizing the time at the NEs
Procedure 6-18
2
Synchronizing the time at the OMC-R (Continued)
Enter the following command to locate the timesynch line entry in the
root crontab file:
crontab -l | grep timesynch
Screen output similar to the following should appear:
30 00 * * * env OMC_TOP=/usr/omc /usr/omc/current/sbin/timesynch
This example runs the timesynch script at 30 minutes past midnight
every day.
If the line entry is missing, add it, using the example given as a
template.
Refer to Scheduling cron jobs using the batch scheduler on page 5-9
for details.
Repeat steps 1, 2 and 3 until all GUI processors have been configured.
For details of the syntax of the crontab file, open a terminal window and enter
man crontab

The site_timesynch script synchronizes the NE time with the time on the system processor.
This saves having to check and reset NE duration manually.
NOTE
It is strongly recommended to schedule the site_timesynch script on all the OMC-R
systems.
The site_timesynch script should be executed:
6-42
At least 10 minutes after the timesynch script.
At a quiet time For example, in the early morning.
Once every week.
After any daylight saving changes. For example, if daylight saving changes take place at
02:00 on Sunday mornings, site_timesynch should be run shortly after 03:00 on Sundays.
68P02901W19-S
Oct 2009
Use the following procedure to check that the site_timesynch script has been set up as an
omcadmin cron job on the system processor and indicates suitable parameters.
Procedure 6-19
Enter the following to locate the timesynch line entry in the omcadmin
crontab file:
crontab -l | grep site_timesynch
Screen output similar to the following should appear:
10 03 * * 0 env OMC_TOP=
/usr/omc /usr/omc/current/sbin/site_timesynch
[passwd 1] [passwd 2]..[passwd n]
Where <passwd 1>, <passwd 2>, <passwd n> are optional
BSS/RXCDR level 2 passwords of each BSS/RXCDR NE that has a level
2 password set. If level 2 passwords are not set at the BSS/RXCDR, then
the site_timesynch command requires no passwords as parameters.
This example runs the site_timesynch script at 03:10 every Sunday.
68P02901W19-S
Oct 2009
If the line entry is missing, add it, using the example given as a
template.
Refer to Scheduling cron jobs using the batch scheduler on page 5-9
for details on setting up cron jobs.
Repeat steps 1, 2 and 3 until all the GUI processors have been
configured.
For details of the syntax of the crontab file, open a terminal window
and enter:
man crontab
6-43
6-44
68P02901W19-S
Oct 2009
Chapter
7
System startup and shutdown
68P02901W19-S
Oct 2009
7-1
Overview
Overview
This chapter describes the startup and shutdown procedures for the OMC-R system hardware,
software applications and processes. An emergency procedure is also included, which is used in
the event of an external power failure. It is described in the section Power failure on page 13-97.
The OMC-R system administrator should be familiar with the power-on, booting, and power-off
operations of the hardware.
CAUTION
All users must be informed before changing the state of any of the processors, since
user processes could be terminated.
The system processor and the optional GUI processors have been initially configured (on
installation) to enter multiuser mode (run level 3) automatically after power-on and booting
sequences have been completed. The result of a successful startup is the login display.
CAUTION
The GUI processor must not be run in the background using >gui &. The GUI
executable constantly reads the input from the terminal in which it was started. If the
GUI is run in the background and the connection with the terminal is lost, this may
cause the GUI to hang. It also prevents the operator from providing Motorola with
diagnostic data if for some reason there was an error reported on the GUI functionality.
7-2
Operating modes (run levels) on page 7-3.
System processor startup and shutdown sequences on page 7-5.
Switching to single user mode on page 7-9.
Manual startup and shutdown of OMC-R software on page 7-12.
68P02901W19-S
Oct 2009
Operating modes (run levels)
Operating modes (run levels)
Operating modes
The system processor and optional GUI processors can be in one of the several modes (or
states or run levels), which vary according to the type of operation required. All processors
normally operate in run level 3.
CAUTION
The system administrator should issue a UNIX wall command before changing the
mode on any processor. This command notifies other users of an impending system
change.
Run levels
The system processor and GUI processors can be in one of the modes (run levels) as given below:
Run level 0:
Run level 0 is in PROM mode level. Enter this level to carry out hardware integrity
checks or to power off the system. Entering this run level resets the system completely.
Installation and updating operating system software is carried out in this state.
Run level 1:
Run level 1 is single user mode, used mainly to install and remove software packages,
and also to make a complete backup and restore of the file systems. Only the console
terminal is usable in this mode.
Run level 2:
Run level 2 is a multiuser mode where all local file systems are mounted, port monitor
services are started, print spooler services are started, and network services are started.
Run level 3:
Run level 3 is a multiuser mode with remote file systems mounted. This is the default
startup mode for the system processor, which is specified in the /etc/inittab file.
Run level 4:
Run level 4 is Not used.
68P02901W19-S
7-3
Oct 2009
Controlling run levels
Run level 5:
Run level 5 performs a soft power-down of the system.
Run level 6:
Run level 6 is a transitory state. When it is entered from a running system, the system
is shut down (just as if run level 0 had been entered), and then automatically rebooted
to the default run level.
Run level S:
Run level S brings the system to the single user level. At this user level, some file systems
are mounted and user logins are disabled.
Controlling run levels

The OMC-R system run level can be controlled with the shutdown and init commands.
7-4
68P02901W19-S
Oct 2009
System processor startup and shutdown sequences
System processor startup and shutdown sequences
Startup and shutdown scripts

The scripts in the directories /etc/rcn.d are used to start or stop the processes, where n refers
to the run level.
The script file names in the directories /etc/rcn.d appear as:
S00name
or
K00name
The file names can be divided into three parts:
S or K
Defines whether the process should be started (S) or stopped (K) upon entering the new
run level. Scripts starting with K are called with an argument of stop, whereas scripts
starting with S are called with an argument of start.
00
The sequence number. This is a number from 00 to 99, indicating the order in which the
files are started (S00, S01, S02 and so on), or stopped (K00, K01, K02 and so on).
name
The name of the subsystem being started or stopped. Usually, the files in /etc/rcn.d
execute a script in /etc/init.d, by means of a softlink. Also, the name of this script is equal
to the name portion of the file.
In Solaris10, many system processes which were previously organized under the /etc/rcn.d are
now managed by the Service Management Facility (SMF). For further details on SMF, manually
starting, stopping and monitoring the services, refer to Chapter 2 System management.
68P02901W19-S
7-5
Oct 2009
Directories associated with startup and shutdown
Directories associated with startup and shutdown

The three main directory structures (all within the /etc directory), associated with startup and
shutdown are as follows:
rc0
Executed by shutdown command to run the scripts in the rc0.d directory for system
change to run levels 0, 5 and 6.
rc3
Executed by init command to run scripts in rc2.d and rc3.d on transition to run level 3.
init.d
Contains actual executable that is called by the scripts in the rcn directories. Used in
upward or downward transitions to all system run levels.
The system processor and the optional GUI processors have been initially configured (on
installation) to enter multiuser mode (run level 3) automatically after power-on and booting
sequences have been completed. The result of a successful startup is the login display.
Chart of directory structures on the system processor

The directory structures and files relating to the startup and shut down of the OMC-R and
INFORMIX are shown in Figure 7-1.
Figure 7-1
7-6
Startup and shut down directory structures on the system processor
68P02901W19-S
Oct 2009
Sequential ordering of the startup and shutdown processes
Sequential ordering of the startup and shutdown processes

The sequential order of the startup and shutdown processes is important. It is not advisable to
have more than one script to any sequence number.
Flow of startup and shutdown sequence on the system processor

The order in which the OMC software and INFORMIX must be started and shutdown on the
system processor is shown in Figure 7-2.
Figure 7-2
Sequence of startup and shutdown processes on the system processor
Identifying a run level

To identify a run level on the host machine, execute the following command as user root:
who -r
An output similar to the following example is given:
run-leve3 Aug 9 11 99
Changing a run level

Only a system administrator (login id root or a group id of sys) can change a run levels. To do
this, the shutdown utility is used.
The syntax for the shutdown utility on the system processor is as follows:
68P02901W19-S
7-7
Oct 2009
Changing a run level
/usr/sbin/shutdown [-y] [-g <grace_period>] [-i <init_state>]

Where
7-8
is
-y
Shut down the system without asking for confirmation

(optional). If not specified, then system administrator must
confirm process termination.
-g
<grace_period>
The time in seconds that the system waits after notifying the
users that the system is going to shutdown. The default value
is 60 seconds.
-i
<init_state>
The run level to be entered.
68P02901W19-S
Oct 2009
Switching to single user mode
Switching to single user mode
Switching the system processor to single user mode

The system processor uses INFORMIX Dynamic Server (IDS) to implement the OMC-R database
and also has several OMC-R applications running on it. Sometimes, it is necessary to partially
shut down the system processor or to stop some of the applications on it.
The procedures for shutting down and starting up the OMC software and the INFORMIX
database are described in Manual startup and shutdown of OMC-R software on page 7-12.
Once the OMC database is in the offline mode and the OMC applications have been stopped.
Use the following procedure to switch the system processor from multiuser to a single user
mode:
Procedure 7-1
Switching the system processor from multiuser to a single user mode.
Enter the following to shut down the processor:

/usr/sbin/shutdown -is -g0 -y
The system processor restarts in the single user mode.
To bring the processor back to the multiuser mode enter:

init 3
Switching a GUI processor to single user mode

If any OMC-R users are logged onto the GUI processor - GUI server or any GUI client - they will
have a GUI application running. Sometimes, it is necessary to partially shut down the processor.
Procedure
When any GUI applications have been stopped, follow Procedure 7-2 to switch the GUI processor
from a multiuser mode to a single user mode.
68P02901W19-S
7-9
Oct 2009
Switching to PROM mode
Procedure 7-2
Switching the GUI processor from multiuser mode to single user mode
Login to the GUI processor as root
Enter the following command to shut down the processor:

shutdown -h now
From the OK prompt, type:

boot -s
The GUI processor restarts in the single user mode.
To bring the processor back to the multiuser mode, press CTRL-d.

Any information displayed related to INFORMIX that appears on rebooting
the system are disregarded.
Switching to PROM mode

The system must be halted or shut down when performing certain maintenance or administrative
tasks, for example, adding or removing hardware or performing file system maintenance tasks.
To bring the system to PROM monitor level, execute the following command as user root.
init 0
A system response as shown below is given:
INIT: New run level:0
The system is coming down. Please wait.
System services are now being stopped.
Print services stopped.
Jan 17 15:32 venus syslogd: going down signal 15
The system is down.
Halted.
Program terminated.
The halt command

Using the halt command is similar to using init 0. While this command performs a clean
shutdown and brings the system to PROM monitor level, it does not run the rc0 scripts. It is
recommended that the halt command is not used, if changes have been made to the rc0 scripts.
7-10
68P02901W19-S
Oct 2009
Bringing the system up from PROM mode
Bringing the system up from PROM mode

To bring the system up from PROM mode, execute the following command as user root at
the OK prompt:
boot
This command will shut down and bring the system up to run level 3, multi-user mode.
The reboot command

The /user/sbin/reboot command performs a clean shutdown and brings the system to run level 3
by default. This command is similar to the init 0 command but does not run the rc0 scripts.
To reboot the system, execute the following command as user root.
reboot
Some useful parameters can be included in this command, for example,
reboot -- -s
This parameter enables the system to switch on to a single user mode after a reboot:
reboot -- -r
This parameter allows the reconfiguration of the system, for example, the addition of a
peripheral device.
68P02901W19-S
7-11
Oct 2009
Manual startup and shutdown of OMC-R software
Manual startup and shutdown of OMC-R software
Overview of manual startup and shutdown

This section describes the procedures used to start up and shut down the OMC-R software
entities manually. The automatic method is built into the appropriate processor startup or
shutdown routine, while the manual method is started from the command line.
The UNIX ps utility displays processes operational, if the OMC-R software is running on the
system.
Starting up OMC-R software

Use the following procedure to start the OMC-R software manually.
Procedure 7-3
Starting the OMC-R software manually
Login to the system processor as omcadmin.

omc start
Log out the system processor.
Shutting down OMC-R software

Use the following procedure to stop the OMC-R software manually.
Procedure 7-4
Stopping the OMC-R software manually

omc stop
Logout the system processor.
NOTE
It is recommended to run the tail command during OMC startup. It should be of
the form tail -f /usr/omc/logs/omcaudityyyymmdd where yyyymmdd is the current
date.
7-12
68P02901W19-S
Oct 2009
Checking system processor processes

To check the processes running on the system processor, carry out the following procedure.
Procedure 7-5
1
Checking processes running on the system processor
Login to the system processor as omcadmin, and enter:

ps -ef |grep +
If the OMC software is running, output similar to the following is
displayed:
omcadmin
805
798 0
Aug 16 ?
0:01 /usr/omc/current/bin/em_main +
omcadmin
816
798 0
Aug 16 ?
0:00 /usr/omc/current/bin/x25appl + 2
omcadmin
813
798 0
Aug 16 ?
0:00 /usr/omc/current/bin/downloader +
omcadmin
806
798 0 Aug 16 ?
0:00 /usr/omc/current/bin/em_lm_main +
omcadmin 812
798 0
Aug 16 ?
0:00 /usr/omc/current/bin/cm +
omcadmin 815
798 0
Aug 16 ?
omcadmin
814
798 0
Aug 16 ?
0:00 /usr/omc/current/bin/EventInterface +
omcadmin
817
798 0
Aug 16 ?
omcadmin 819
798 0
Aug 16 ?
0:00 /usr/omc/current/bin/RLogin +
omcadmin
818
798 0
Aug 16 ?
0:00 /usr/omc/current/bin/uploader +
omcadmin
820
798 0
Aug 16 ?
omcadmin 821
798 0
Aug 16 ?
omcadmin
822
798 0
Aug 16 ?
0:05 /usr/omc/current/bin/PmLoader +
omcadmin
823
798 0
Aug 16 ? 0
:00 /usr/omc/current/bin/Parser + F
PCHAN_1 FPADMCHAN_1
omcadmin
828
798
0
Aug 16 ?
0:00 /usr/omc/current/bin/pm_main +
omcadmin
829 798 0
Aug 16 ?
0:00 /usr/omc/current/bin/CSM_MAIN +
omcadmin 830
798 0
Aug 16 ?
omcadmin
831
798 0
Aug 16 ?
omcadmin
832
798 0 Aug 16 ?
Continued
68P02901W19-S
7-13
Oct 2009
Procedure 7-5
Checking processes running on the system processor (Continued)
0:32 /usr/omc/current/bin/fm_audit +
omcadmin 954
798 0
Aug 16 ?
0:00 /usr/omc/current/bin/ResyncCtrl +
omcadmin 1062 1058 0
Aug 16 ?0:03
/usr/omc/current/bin/gateway +q +c
/usr/omc/current/config -r informix +i 5 +a
Aug 16 ?
0:03 /usr/omc/current/bin/resync +q +c
/usr/omc/current/config -r informix +i 8 +a 4
Aug 16 ?
0:03 /usr/omc/current/bin/pmProxy +q +c.
Aug 16 ?
0:03 /usr/omc/current/bin/emProxy +q +c
Aug 16 ?0:03
/usr/omc/current/bin/scheduler +q +c
/usr/omc/current/config -r informix +i 14
omcadmin 1058
1 0
Aug 16 ?
0:02 /usr/omc/current/bin/monitor +q +c
omcadmin 1055
1 0
Aug 16 ?
0:02 /usr/omc/current/OSP/bin/nameserver
+i 900 +a 9001 +ns 900 localhost 9001
omcadmin 1066 1058 0 Aug 16 ?
0:03 /usr/omc/current/bin/audit +q +c
Aug 16 ?
0:02 /usr/omc/current/bin/callTrace +q +c
Aug 16 ?
0:12 /usr/omc/current/bin/NetExp +q +c
Aug 16 ?
0:05 /usr/omc/current/bin/OmcPyTom +q +c
/usr/omc/current/config -r informix +i 27 +
Aug 16 ?
0:04 /usr/omc/current/bin/gprsTrace +q +c
omcadmin 26597 26572 0 15:23:58 pts/2
0:00 grep +
somc57:omcadmin >
2
7-14
Log out the system processor.
68P02901W19-S
Oct 2009
Chapter
8
Database Management
68P02901W19-S
Oct 2009
8-1
Overview
Overview
This chapter describes the administrative procedures required to maintain the two INFORMIX
databases.
PM Database - The Performance Management database (formerly the OMC database), is

used to store Performance Management data and Event Management subscriptions along
with subscription lists.
CM Database - The Configuration Management database (formerly the MIB database), is

used to store Configuration Management and Fault Management (FM) data. Only personnel
belonging to the group omc have write access to the tables within the CM database.
Each database is managed by a separate INFORMIX Dynamic Server (IDS) Version 10. Both
databases, and all relevant INFORMIX application modules, are initially installed on the system
processor by Motorola personnel. For more information, refer to Installation and Configuration:
OMC-R Clean Install (68P02901W47) manual.
8-2
Overview of database management on page 8-3.
Database utilities on page 8-4.
INFORMIX directory structure on page 8-13.
Shutdown and startup of the PM and CM databases on page 8-16.
Setting the onconfig parameters on page 8-26.
Dropping and Recreating the PM database on page 8-30.
Additional database maintenance procedures on page 8-32.
Checking the PM database on page 8-34.
Checking the CM database on page 8-39.
68P02901W19-S
Oct 2009
Overview of database management
Overview of database management
PM database maintenance
Maintenance on the PM database is carried out by the omc_db_maint utility. This utility is
run as a root cron job or it is run manually (see Administering the PM database using the
omc_db_maint utility on page 8-23).
The IDS log file for the PM database, $INFORMIXDIR/online.log_OMC, is checked for errors
and check-pointing. The cron job roll_online.log performs an automatic roll-over of this log file.
The /usr/omc/current/sbin/bss_dt_load.sh cron job runs every night before midnight to
automatically load default dates and times into the bss_datetimes table in the PM database.
68P02901W19-S
8-3
Oct 2009
Database utilities
Database utilities
Overview of the database utilities

This section provides a brief description of the procedures for the scripts and utilities used in
the administration of the PM and CM databases as follows:
/usr/informix/bin/onmonitor
/usr/omc/current/sbin/omc_db_maint
/usr/omc/current/sbin/db_disconnect
/usr/omc/current/sbin/db_pm_maint
/usr/omc/current/sbin/pm_daily_unload
/usr/omc/current/sbin/pm_purge_check
/usr/omc/current/sbin/omc_db_ckspace
/usr/omc/current/bin/pm_manual_parse
The onmonitor utility is run, logged into the system processor, as user id informix. The
omc_db_maint utility is run, logged into the system processor, as user id root. All other utilities
are run as user id omcadmin unless stated.
8-4
68P02901W19-S
Oct 2009
onmonitor utility
onmonitor utility
The onmonitor utility is used for INFORMIX database management purposes.
Use the following procedure to invoke onmonitor utility:
Procedure 8-1
Invoking the onmonitor utility
Switch user to informix:

su - informix
NOTE
If the onmonitor utility is invoked as any user other than
informix, a status menu will appear which allows the
interrogation of database parameters but does not allow
any changes.
3
Ensure the TERM variable is set to vt100:

setenv TERM vt100
Setup the correct environment, according to the required database.

To access the PM database enter:
omc_env
To access the CM database enter:
mib_env
Enter the following command to start the onmonitor utility:

onmonitor
NOTE
If onmonitor is run with an incorrect screen configuration,
the menus will not work properly. If this should happen,
press e to exit the command line.
CAUTION
Do not use the function keys (F1, F2 and so on) when
working with IDS, even if the help text indicates otherwise,
as they do not always work as expected. Use the
CTRL-character key combination or left arrow key.
All onmonitor commands can be performed from the command line. For further information
regarding these commands, refer to the INFORMIX Administrator's Guide documentation.
68P02901W19-S
8-5
Oct 2009
omc_db_maint utility
Use of omc_db_maint
CAUTION
Interrupting an invocation of the omc_db_maint utility before it completes can cause
database corruption. For this reason, the utility should never be interrupted or killed
before it has run to completion.
The omc_db_maint utility is used to unload and delete the PM statistics and report
on the database disk usage. The omc_db_maint utility is located in the directory
$OMC_TOP/current/sbin and invoked using login id root.
Sub-utilities run within omc_db_maint

The omc_db_maint utility calls the pm_purge_data utility to perform PM statistics
maintenance (refer to pm_purge_data utility for further details) and pm_daily_unload to
perform the daily unload of the previous days statistics (refer to pm_daily_unload utility for
further details). In addition there is a utility, pm_purge_check, whose function is to check that
the maintenance has completed successfully and to raise an alarm if it detects any problems
(refer to pm_purge_check utility for further details).
The disk usage report is generated using the omc_db_ckspace utility (refer to omc_db_ckspace
utility on page 8-10 for further details). The disk usage report is placed into the omc_db_maint
log file which is located in the $OMC_TOP/logs directory.
NOTE
The percentage of database space used report entered into the omc_db_maint
log file is checked once a week. If the amount of data in the database is growing
substantially, further investigation is advised.
To ensure that the OMC-R software does not need to be stopped, potentially causing loss of
PM statistics, the db_disconnect utility is also called by the omc_db_maint utility (refer to
db_disconnect utility for further details).
Recommendations on the use of omc_db_maint

It is recommended that the omc_db_maint utility should be run daily as a cron job. The
scheduling of the cron job should ideally be performed during low activity periods (for example,
after midnight).
Procedures for running omc_db_maint both manually and as a cron job are described in
8-6
68P02901W19-S
Oct 2009
pm_purge_data utility
Command line parameters for omc_db_maint

To control omc_db_maint database maintenance activities and override the default database
delete and unload settings, the following parameters are possible when invoking omc_db_maint
from the command line:
$OMC_TOP/current/sbin/omc_db_maint [-delete|-DELETE] [-unload|-UNLOAD]
[-force|-FORCE]
Where
is
-delete
The optional parameter to suppress the delete

operation.
-unload
The optional parameter to suppress the unload

operation.
-force
The optional parameter to force the deletion of

data that has not been unloaded.
An example, on the use of command line parameters for omc_db_maint to perform the deletion
but not the unload:
$OMC_TOP/current/sbin/omc_db_maint -unload
The parameters delete any expired PM statistics from the PM database, but an unload operation
to $UNLOAD_DIR is not performed.
pm_purge_data utility
The pm_purge_data utility is responsible for the purging of expired statistics from
the Performance Management database. It is usually run as a cron job from within the
omc_db_maint utility. However, in exceptional circumstances, it can be run from the command
line. The pm_purge_data utility is located in the directory $OMC_TOP/current/sbin and
invoked using login id omcadmin.
Command line parameters for pm_purge_data

By default the pm_purge_data utility will not purge statistics if they have not previously been
unloaded by the daily unload utility, pm_daily_unload. A command line option can be invoked
to override this behavior and force the deletion of statistics that have not been unloaded.
pm_purge_data [-force|-FORCE]
Where
is
-force
optional parameter to force the deletion of

data that has not been unloaded.
The Parser must be disconnected while this utility is running. See Administering the PM
database using the omc_db_maint utility on page 8-23 for more information on manually
disconnecting and connecting the Parser and other utilities.
68P02901W19-S
8-7
Oct 2009
pm_daily_unload utility
pm_daily_unload utility
The pm_daily_unload utility unloads yesterdays statistics, as well as a snapshot of all nonstatistics data, into the directory $OMC_TOP/ne_data/unload_stats/unload_dir.yyyy.mm.dd
where <yyyy> refers to the current year, <mm> to the current month and <dd> to the
current day in this month.
The data is stored in compressed, | delimited ASCII files. This utility, which is stored in
$OMC_TOP/current/sbin, is usually invoked from within the omc_db_maint utility. However,
it can be invoked from the command line in exceptional circumstances. The utility accepts no
command line parameters.
pm_purge_check utility
The pm_purge_check utility is responsible for ensuring the daily purge of data has occurred,
and that space has been prepared in the database ready for the following days statistics. The
utility must be run as a cron job and should be scheduled to start 2 hours after the database
maintenance utility (omc_db_maint), and should run every hour until 23:00.
For example, if omc_db_maint is scheduled to start at 04:02 then pm_purge_check
should be scheduled to start at 06:02, 07:02, 08:02, until 23:02. The utility resides in
$OMC_TOP/current/sbin and accepts no command line parameters.
If the utility should find that omc_db_maint has not successfully purged the database, then it
sends a major alarm to the OMC. On receipt of this alarm the operator should investigate and
correct any issues with omc_db_maint. The pm_purge_check utility runs every hour, and will
continue to send alarms until the problem is rectified, when the alarm will be cleared.
db_disconnect utility
The db_disconnect utility informs OMC-R applications to either disconnect from or reconnect
to the database. This utility should form part of any database maintenance procedure which
affects the tables used by these applications.
Example connect procedures

To connect all applications to the database enter:
$DBMS_ROOT/sbin/db_disconnect connect
To connect the Event Manager application to the database enter:
$DBMS_ROOT/sbin/db_disconnect connect em
To connect the pmProxy application to the database enter:
$DBMS_ROOT/sbin/db_disconnect connect pmproxy
8-8
68P02901W19-S
Oct 2009
db_pm_maint utility
To connect the parser application to the database enter:

$DBMS_ROOT/sbin/db_disconnect connect parser
To connect the csm application to the database enter:
$DBMS_ROOT/sbin/db_disconnect connect csm
This utility should be used for the Parser, pmProxy, csm and the Event Manager (EM)
applications if the OMC-R database has to be brought online.
NOTE
The $DBMS_ROOT environment variable is only set when the user is logged into the
system processor as omcadmin.
db_pm_maint utility
Most of the PM database data storage is allocated to PM statistics. To ensure that the database
does not become full, the db_pm_maint utility must be run regularly to delete any entities from
the PM database for which there are no statistics.
The pathname for db_pm_maint utility is:
$DBMS_ROOT/sbin/db_pm_maint
The db_pm_maint utility is run once a week as part of the omc_db_maint utility and would,
therefore, not usually be run manually.
Manually running db_pm_maint

To run db_pm_maint on the PM database, the following alias must be entered:
omc_env
The utility is invoked with a set of parameters which specify the operations to perform. The
syntax for invocation is:
db_pm_maint [-e]
Where
is
-e
entity consistency; delete all those entities for which there

are no statistics.
NOTE
It is necessary to include the -e flag when running db_pm_maint.
68P02901W19-S
8-9
Oct 2009
omc_db_ckspace utility
The omc_db_ckspace utility presents information on all DBSpace allocation and all TBLSpace
allocation in summary format. It can be run against both the PM and CM databases. It is run as
part of the omc_db_maint utility and would, therefore, not usually be run directly.
Manually running omc_db_ckspace

The omc_db_ckspace utility is located in the directory $DBMS_ROOT/sbin.
The syntax for invocation is:
omc_db_ckspace [-u] [-f] {omc | mib}
Where
is
-u
update statistics for database(s).
-f
full table listing printed.
omc
PM database.
mib
CM database.
If neither PM nor CM database is declared, omc_db_ckspace will run on the PM database

by default.
Use the following procedure to run the omc_db_ckspace utility:
Procedure 8-2
Running the omc_db_ckspace utility
Disconnect the database by entering the following command:

$DBMS_ROOT/sbin/db_disconnect disconnect
To run the utility on the PM database, enter the following:

$DBMS_ROOT/sbin/omc_db_ckspace omc
To run the utility on the CM database, enter the following:
$DBMS_ROOT/sbin/omc_db_ckspace mib
Output similar to the following is displayed:
DBSpace: all dbspaces
DBS Pages Allocated: 204799
DBS Pages Used: 159782
DBS Pages Free: 45017
OMC Database space used has reached 78.0189%
specified DBMS_MAX_SPACE_USED 95%
TBLSpace
TBS Pages Allocated: 159449
TBS Pages Used: 1148
TBS Pages Free: 158301
Continued
8-10
68P02901W19-S
Oct 2009
Procedure 8-2
pm_manual_parse utility
Running the omc_db_ckspace utility (Continued)
The output provides descriptions of all DBSpaces and all TBLSpaces.

Although the above output indicates that the PM database is 78
percent full, the TBLSpace section shows how much of that allocation
is actually free. The reason for this apparent discrepancy is that the
database has been sized for one extent.
4
Enter the following command to reconnect the database:

Log out of the system processor.
The utility pm_manual_parse is used to parse raw PM statistics files that have been missed by
the parser. The utility informs the parser, which files need to be parsed, so that data contained
in the files can be inserted into the PM database.
Use the following procedure to run the pm_manual_parse utility:
Procedure 8-3
Running the pm_manual_parse utility
Enter the following to check that the $FMPATH environment variable

is set:
echo $FMPATH
FMPATH is set to /usr/omc/ne_data/raw_stats. This environment
variable (set by default in sysCommon.csh) identifies the base UNIX
directory in which all uploaded statistics are stored before being
presented to the parser.
Enter the following to invoke the pm_manual_parse utility:

$PM_ROOT/bin/pm_manual_parse [-s <value>] <filename>
Where:
-s <value> is an optional sleep parameter that allows the system

to sleep between sending consecutive files to the parser. The
<value> parameter is an integer less than 9999.
<filename> is the specified file to be parsed.
The <filename> parameter must satisfy the following criteria:
The specified file must exist.
Both absolute and relative path names are allowed.
The file must be globally readable. All uploaded statistics files

are globally readable by default.
Continued
68P02901W19-S
8-11
Oct 2009
Procedure 8-3
8-12
Running the pm_manual_parse utility (Continued)
The file must be an uploaded statistics file which has not yet been
parsed. If not, the file contents will not be added to the statistics
database.
Wild cards are allowed for file names to allow submission of

multiple files.
An error message is displayed if the utility does not succeed in
sending the supplied <filename> to the PM File Parser, or if the
parser exits because any of the criteria for the file names are
not met.
To see if the parse was successful, enter the command:

tail -f $SYS_LOG/fpomcaudityymmdd
This displays the last ten lines in the log file fpomcaudityymmdd. Any
errors that may have occurred during the parsing procedure are shown.
68P02901W19-S
Oct 2009
INFORMIX directory structure
INFORMIX directory structure
Overview of the INFORMIX directory structure

When the INFORMIX products are installed, the IDS databases initialized, and the OMC-R
software loaded, directory structures similar to those shown in Figure 8-1 and Figure 8-2 will
have been formed.
The top of the INFORMIX directory structure, on the relevant processor, is located by the
environment variable $INFORMIXDIR (set to /usr/informix). The PM database scripts on
the system processor can be located by using the environment variable $DBMS_ROOT (set
to $OMC_TOP/current).
The INFORMIX databases message logs are held in $INFORMIXDIR on the system processor.
68P02901W19-S
8-13
Oct 2009
INFORMIX directory structure on the system processor

Figure 8-1 shows the INFORMIX directory structure on the system processor.
Figure 8-1
8-14
68P02901W19-S
Oct 2009
INFORMIX directory structure on the GUI processor
INFORMIX directory structure on the GUI processor

The GUI processor also contains INFORMIX products, to allow for the connection of client
software to the IDS.
NOTE
There are no databases located on a GUI processor. All databases reside on the
system processor. The GUI processor is merely a client for connection purposes.
Figure 8-2 shows the INFORMIX directory structure on a GUI processor.
Figure 8-2
68P02901W19-S
INFORMIX directory structure on a GUI processor
8-15
Oct 2009
Shutdown and startup of the PM and CM databases
Shutdown and startup of the PM and CM databases
Database shutdown and startup

The PM and CM databases can be shut down and started up manually using the onmonitor
utility. Scripts also exist to perform an automatic shutdown and startup.
Shutting down the PM database through onmonitor

Use the following procedure to shut down the PM database using the onmonitor utility:
Procedure 8-4
If the OMC-R applications are still running, disconnect all OMC-R

applications from the database using the db_disconnect utility, as
follows:
$DBMS_ROOT/sbin/db_disconnect disconnect
Switch to user root and enter the root password:

su - root
Switch to user informix:

su - informix
Set the correct environment:

omc_env
Start onmonitor utility:

onmonitor
The Status menu is displayed as shown in Figure 8-3.
Select the Mode menu, by pressing m. The Mode menu is displayed as

shown in Figure 8-4.
Continued
8-16
68P02901W19-S
Oct 2009
Procedure 8-4
8
Shutting down the PM database through onmonitor (Continued)
Select Graceful Shutdown by pressing g and respond to one of the

following:
If there are any users accessing the database, the following

Do you want to see the list of user threads? (y/n)
Answer yes (y) to list the active user threads.
NOTE
Where there is no prompt for user threads, select
Immediate Shutdown to put the INFORMIX RDBMS
directly into Quiescent mode.
If there are no users, or after the active user threads have been
listed, the following prompt is displayed:
Do you really want to shutdown? (y/n)
Answer no (n) to terminate the shutdown procedure.
Answer yes (y) to place the database into Quiescent mode. The
following message is displayed:
Shutting down, please wait . . . .
The database enters Quiescent mode.
Select Take Off-line by pressing two keys SHIFT-T. The following

message is displayed:
The INFORMIX RDBMS changes state from Quiescent mode to Off-Line
mode. Shutdown is complete when the Mode menu returns and the
state line indicates Off-Line.
68P02901W19-S
10
Exit onmonitor by pressing e twice.
11
8-17
Oct 2009
Shutting down the CM database through onmonitor
Figure 8-3
The onmonitor Status menu indicating Online state
Figure 8-4
Mode menu indicating Online state
Shutting down the CM database through onmonitor
NOTE
The OMC-R software must be stopped before the CM database is manually started
up or shut down. Refer to Chapter 7 System startup and shutdown for stopping the
OMC-R software.
Use the following procedure to shut down the CM database using onmonitor:
Procedure 8-5
Shutting down the CM database using onmonitor
Login to the system processor as root and switch to user informix:

su - informix
Set the correct environment:

mib_env
Start the onmonitor utility:

onmonitor
Select the Mode menu, by pressing m.

The Mode menu is displayed as shown in Figure 8-4.
Continued
8-18
68P02901W19-S
Oct 2009
Procedure 8-5
5
Starting up the PM database through onmonitor
Shutting down the CM database using onmonitor (Continued)
Select Graceful Shutdown by pressing g and respond to one of the

following:
If there are any users accessing the database, the following

Do you want to see the list of user threads? (y/n)
Answer yes (y) to list the active user threads.
NOTE
Where there is no prompt for user threads, select
Immediate-Shutdown to put the INFORMIX RDBMS directly
into Quiescent mode.
If there are no users, or after the active user threads have been
listed, the following prompt is displayed:
Answer no (n) to terminate the shutdown procedure.
Answer yes (y) to place the database into Quiescent mode. The
following message is displayed:
The database enters Quiescent mode.
Select take offline by pressing two keys SHIFT-t. The following

message is displayed:
The INFORMIX RDBMS changes state from Quiescent mode to Off-Line
mode. Shutdown is complete when the Mode menu returns and the
state line indicates Off-Line.
Exit onmonitor by pressing e twice, then log out of the system

processor.

Use the following procedure to start up the PM database using the onmonitor utility:
68P02901W19-S
8-19
Oct 2009
Procedure 8-6
Starting up the PM database using onmonitor

su - informix
Set the correct environment.

omc_env
Start the onmonitor utility:

onmonitor
Select the Mode menu, by pressing m.

The Mode menu is displayed as shown in Figure 8-6.
Select Startup by pressing s.

This displays messages similar to the following:
Initializing please wait
Press return to continue.
8-20
Select On-Line by pressing o.
Exit onmonitor by pressing e twice.
If the OMC-R applications are already running, they may be connected

using the db_disconnect utility using the following commands:
su - omcadmin
Enter the omcadmin password, then type:
Figure 8-5
The onmonitor Status menu indicating Offline state
Figure 8-6
Mode menu indicating Offline state
68P02901W19-S
Oct 2009
Starting up the CM database through onmonitor
Starting up the CM database through onmonitor

Use the following procedure to start up the CM database using onmonitor:
Procedure 8-7
Starting up the CM database using onmonitor

su - informix
Set the correct environment background by entering the following

commands:
mib_env
Enter onmonitor and ensure the Startup menu is displayed.
Select the Mode menu as shown in Figure 8-7.
Select Startup. This will display messages similar to the following:

Initialising please wait
Press return to continue
Select On-Line by pressing O.
Exit onmonitor by pressing e.
Figure 8-7
Mode menu indicating offline state
Figure 8-8
The onmonitor Status menu indicating online state
68P02901W19-S
8-21
Oct 2009
Starting up databases automatically
Starting up databases automatically

To start up both databases automatically, a script needs to be executed.
The automatic startup script for the PM and CM databases is held in the /etc/init.d/informix
file. This script is executed at bootup.
Use the following procedure to execute the automatic startup script:
Procedure 8-8
Starting databases automatically using the startup script

svcadm enable -st informix/pm
for the PM Database and
svcadm enable -st informix/cm
for the CM Database. The automatic startup script is executed.
Shutting down automatically

The automatic shutdown scripts for the CM and PM databases are held in the
/etc/init.d/informix file. These scripts are executed when the system is shut down.
Use the following procedure to execute the automatic shutdown script:
Procedure 8-9
Stopping databases automatically using the shutdown script

svcadm disable -st informix/pm
for the PM Database and
svcadm disable -st informix/cm
for the CM Database. The automatic shutdown scripts are executed
and both databases will be shut down.
NOTE
The /etc/init.d directory contains files that are linked into
the various run states as described in System processor
startup and shutdown sequences on page 7-5.
8-22
68P02901W19-S
Oct 2009
Administering the PM database using the omc_db_maint utility
Administering the PM database using the

Using omc_db_maint
The omc_db_maint utility provides a tool for administering the PM database. It unloads and
deletes PM statistics and reports on disk space used by the PM database.
The omc_db_maint utility is located in the directory $OMC_TOP/current/sbin on the system
processor.
This utility can be run either as a cron job or using a manual procedure.
It is recommended that the omc_db_maint utility be run daily as a cron job. The scheduling
of the cron job should ideally be performed during low activity periods (for example, after
midnight).
NOTE
The omc_db_maint utility will not purge data if that data has not been previously
unloaded by omc_db_maint for any reason (for example, if you run out of disk space
in the destination directory). This behavior can be overridden by using the -force
parameter to omc_db_maint. Refer to the section on the omc_db_maint utility for
more information. See Automatic Checking Of Maintenance for more information
on monitoring the overnight maintenance.
Running omc_db_maint as a cron job

To run omc_db_maint automatically as a cron job and to check and log the results:
Procedure 8-10
1
Running omc_db_maint automatically as a cron job
Login to the system processor as root and ensure an omc_db_maint

line entry exists in the root crontab file:
more /usr/spool/cron/crontabs/root
A typical line entry for omc_db_maint, within the root crontab file, is
as follows:
Continued
68P02901W19-S
8-23
Oct 2009
Running omc_db_maint manually
Procedure 8-10
Running omc_db_maint automatically as a cron job (Continued)
# Execute omc_db_maint at 04:02 each day

02 04 * * * env OMC_TOP=
/usr/omc/usr/omc/current/sbin/omc_db_maint
Create a suitable line entry, if one is not already created.
NOTE
Refer to Chapter 2 System Management for details on
setting up a cron job either by using the Batch Scheduler or
by using the command line.
2
When the cron job has been run, check the omc_db_maint log file to
ensure that the operation completed successfully:
more $OMC_TOP/logs/omc_db_maint.<yyyy>.<mm>.<dd>
Where <yyyy> refers to the current year, <mm> to the current month
and <dd> to the current day in this month.
Record the PM database disk usage information in the system

administrator log book.
Check the PM database log file online.log_OMC for errors, by

entering the following:
more /usr/informix/online.log_OMC
Archive the unloaded statistics to tape and remove them from the file
system.
Running omc_db_maint manually
CAUTION
The omc_db_maint script should not be interrupted or killed before it has run
to completion.
Use the following procedure to run the omc_db_maint utility manually, referring to other
sections of this manual where indicated.
Procedure 8-11
Running the omc_db_maint utility manually
Execute the omc_db_maint utility as follows:

Continued
8-24
68P02901W19-S
Oct 2009
Procedure 8-11
Automatic Checking Of Maintenance
Running the omc_db_maint utility manually (Continued)
NOTE
Refer to the section omc_db_maint utility for the use of
optional parameters.
3
Check the omc_db_maint log file to ensure that the operation

completed successfully:
Where <yyyy> refers to the current year, <nn> to the current month
and <dd> to the current day in this month.
Record the PM database disk usage information in the system

administrator log book.
Check the PM database log file online.log_OMC for errors by entering

the following:
more /usr/informix/online.log_OMC
Archive the unloaded statistics to tape and remove them from the file
system.
Automatic Checking Of Maintenance

When the omc_db_maint utility is run every night it prepares space in the database to accept
the following days data. If that space is not available for any reason the Parser will not be able
to parse statistics into the database.
A utility pm_purge_check is provided to monitor the PM database and to raise an alarm if it
finds that omc_db_maint has failed to purge the database. This utility must be run as a cron
job and should be scheduled to start 2 hours after the omc_db_maint utility, and should run
every hour until 23:00.
For example, if omc_db_maint is scheduled to run at 02:45 (see above), then the cron table entry
for pm_purge_check will look like:
45 04-23 * * *
env OMC_TOP=/usr/omc /usr/omc/current/sbin/pm_purge_check
This will run pm_purge_check at 04:45 and 45 minutes past the hour until 23:45.
On receipt of an alarm to indicate the maintenance has not been successful the operator should
check the omc_db_maint log file for errors:
Having investigated and corrected any problems omc_db_maint can be run manually to perform
the maintenance. Refer to omc_db_maint utility for information regarding optional parameters
and Running omc_db_maint Manually for the correct procedure for manual invocation.
Once the maintenance has been completed successfully, the pm_purge_check utility will
automatically clear any outstanding alarms when it next runs.
68P02901W19-S
8-25
Oct 2009
Setting the onconfig parameters
Setting the onconfig parameters
onconfig file overview

Each Informix Dynamic Server has a configuration file. The configuration files are as follows:
/usr/informix/etc/onconfig_OMC the configuration file for the PM database.
/usr/informix/etc/onconfig_MIB the configuration file for the CM database.
The configuration files hold many parameters associated with each respective IDS. Any changes
made to the parameters in these files should be recorded and a hard copy of the changed file
printed (noting the date of alteration of the file). Store the hard copy with the backup tapes.
An example of a parameter is:
Max # of Logical Logs - When restoring either the CM or PM databases from backup
tapes, this parameter must be assigned to the maximum value held during the period
covered by the backup.
The required value for this parameter is stored in the file /$INFORMIXDIR/etc/$ONCONFIG
(where the variable $ONCONFIG can be either onconfig_OMC or onconfig_MIB).
Any changes made to the parameters in these files should be recorded and a hard copy of the
changed file printed (noting the date of alteration of the file). Store the hard copy with the
backup tapes.
Checking onconfig parameters

Use the following procedure to check parameter settings within /$INFORMIXDIR/etc/$ONCONFIG. The procedure uses the TAPE parameters as an example; substitute TAPE for the
required parameter for checking:
Procedure 8-12
Checking onconfig parameters
Login to the system processor as root and switch user to informix:

su - informix
Change the directory by entering the following command:

cd $OMC_TOP/config/global
Check that the onconfig parameters match up with the system tape
parameters by entering either of the following lines:
Continued
8-26
68P02901W19-S
Oct 2009
Procedure 8-12
Changing onconfig parameters
Checking onconfig parameters (Continued)
For PM database enter:

omc_env ; onstat -c | grep TAPE
.
For CM database enter:
mib_env ; onstat -c | grep TAPE
An output similar to the following will be displayed:
TAPEDEV
/dev/rmt/0
TAPEBLK
64
TAPESIZE 4000000
LTAPEDEV /dev/null
LTAPEBLK 16
LTAPESIZE 10240
4
If the parameters are not as required, run the onmonitor utility and change
the parameters. Refer to Changing onconfig parameters.
CAUTION
It is not recommended to change /$INFORMIXDIR/etc/$ONCONFIG parameters unless
absolutely necessary. The parameters supplied by Motorola have been chosen
following extensive performance testing. The parameters should only be changed on
the advice of INFORMIX-trained Motorola personnel.
Use the following procedure to change parameters in /$INFORMIXDIR/etc/$ONCONFIG.
This procedure describes, as an example, changing the Max # of Logical Logs parameter
using the onmonitor utility:
Procedure 8-13
Login to the system processor as root and switch user to informix:

su - informix
Set the TERM environment variable:

setenv TERM vt100
Set the correct environment by selecting one of the following:

For the PM database, enter the alias:
omc_env
For the CM database, enter alias:
mib_env
Continued
68P02901W19-S
8-27
Oct 2009
Procedure 8-13
4
Changing onconfig parameters (Continued)
Enter the following command to start the onmonitor utility:

onmonitor
The following is displayed:
INFORMIX-Online: Status Parameters Dbspaces Mode Force-Ckpt
Status menu to view INFORMIX-Online.
----------------------Online------- Press CTRL-W for Help.
Using the space bar, select the Mode option and press RETURN. The
following is displayed:
MODES: Startup Online Graceful-Shutdown Immediate-Shutdown...
Bring INFORMIX-Online to quiescent mode from offline.
Using the space bar, select the Take Offline option and press RETURN.
Enter y.
Using the space bar, select the Exit option to return to the initial Setup
menu. Press RETURN. The following is displayed:
PARAMETERS:
initialise Shared-Memory perFormance
data-Replication ...
initialise root dbspace and shared memory configuration.
----------Offline------- Press CTRL-W for Help. --------
Select the Shared Memory option using the space bar, and press
RETURN.
10

SHARED MEMORY: Make desired changes and press
ESC to record changes. Press Interrupt to abort changes.
Press F2 or CTRL-F
for field-level help.
SHARED MEMORY PARAMETERS
Server Number [0] Server Name [omc_sys1]

Server Aliases [omc_sys]
Dbspace Temp [omc_db_temp]
Deadlock Timeout [60] Secs Number of Page Cleaners [5]
Forced Residency [Y] Stack Size (K) [32]
Non Res. SegSize (K) [10800] Optical Cache Size (K) [128]
Continued
8-28
68P02901W19-S
Oct 2009
Procedure 8-13
Changing onconfig parameters (Continued)
Physical Log Buffer Size [128] K Dbspace Down Option [0]

Logical Log Buffer Size [128] K Preserve Log For Log Backup
[N]
Max # of Logical Logs [20] Transaction Timeout [300]
Max # of Locks [75000] Long TX HWM [50]
Max # of Buffers [4000] Long TX HWM Exclusive [60]
Index Page Fill Factor [90]
Add SegSize (K) [1024]
Total Memory (K) [0]
Resident Shared Memory size [14986] Kbytes Page Size [2]
Kbytes
11
Move to the fields requiring alteration using the arrow or tab keys and
overwrite the existing values. In this example procedure, change the
Max # of Logical Logs parameter to the maximum value held during
the period covered by the tape backup.
12
Press ESC to save the changes. The following screen output will
appear:
Do you want to keep these changes to the parameters? (y/n)
Enter y to install the new values.
68P02901W19-S
13
If no changes are required, the Shared Memory Setup window can be

closed by pressing the interrupt key. This is usually CTRL-c or DELETE.
14
Bring the database back online.
15
Select the Exit option, then select Exit again to close onmonitor utility
and return to the command line prompt.
8-29
Oct 2009
Dropping and Recreating the PM database
CAUTION
This procedure is a drastic measure, and the PM database should only be dropped and
recreated if absolutely necessary. Contact Motorola Support for further information.
Use the following procedure to drop and then recreate the PM database:
Procedure 8-14
Shut down the OMC-R processes by logging in to the system processor

as user omcadmin and entering the following command:
omc stop
To drop the PM database, enter the following command as user

informix:
svcadm restart -st informix/pm
(to verify that the PM database engine is online again).
Enter the following commands as user omcadmin:

omc_env
dbexport omc_db -ss
isql - drop database omc_db;
To recreate the PM database, enter the following commands as user

omcadmin:
cd /usr/omc/current/sbin
db_create omc_db
To load up customer specifics enter the following for these tables

as user omcadmin, where <unl_dir> is the name of the unload
directory in the format: unload_dir.YYYY.MM.DD (for example,
unload_dir.2004.05.14). The specific .unl files that are being loaded
must be uncompressed in the dated unload directory before the sql
load commands are executed.
omc_env
Continued
8-30
68P02901W19-S
Oct 2009
Procedure 8-14
Dropping and Recreating the PM database (Continued)
isql omc_db load from

/usr/omc/ne_data/unload_stats/<unl_dir>/subscriptions.unl
insert into subscriptions;
load from
/usr/omc/ne_data/unload_stats/<unl_dir>/subscription_list.unl
insert into subscription_list;
load from /usr/omc/ne_data/unload_stats/<unl_dir>/entity.unl
insert into entity;
load from
/usr/omc/ne_data/unload_stats/<unl_dir>/stored_selections.unl
insert into stored_selections;
load from
/usr/omc/ne_data/unload_stats/<unl_dir>/custom_statistics.unl
insert into custom_statistics;
68P02901W19-S
The Motorola shipped defaults, stored in /usr/omc/current/config,

are loaded by default when the PM database is created.
Restart the OMC-R processes by entering the following command as

user omcadmin:
omc start
8-31
Oct 2009
Additional database maintenance procedures
Additional database maintenance procedures
Overview of additional database maintenance procedures

This section describes some additional database maintenance procedures that are used for
regular maintenance of the databases in the OMC-R.
Checking for excess of 32000 statistics

For a procedure to perform this task, refer to section Using neighbor statistics on page 13-91
in Chapter 12 Backup Server Installation and Configuration.
Checking stat details

The statinfo script is located in /usr/omc/current/sbin/statinfo. To ascertain the name of the
statistic name and details, pass into this script the of the hex_id.of the statistic.
Backing up subscription data

Use the following procedure to backup subscriptions and subscription list data from the PM
database, through the creation of two UNIX files, onto a specified tape device:
Procedure 8-15
Backing up subscription data from the PM database
Login as omcadmin.
Enter the following commands on the system processor:

omc_env
isql omc_db unload to subscriptions.unl select * from subscriptions;
unload to subscription_list.unl select * from
subscription_list;
NOTE
The subscription data is still retained in the PM database.
3
Use CTRL-c to exit from the isql utility.

The subscriptions.unl and the subscription_list.unl files are
created in omcadmin home directory.
Load a DAT tape into the tape drive of the system processor.
Continued
8-32
68P02901W19-S
Oct 2009
Procedure 8-15
68P02901W19-S
Backing up subscription data
Backing up subscription data from the PM database (Continued)
Backup the subscriptions.unl and the subscription_list.unl files

to tape by executing the following commands:
tar -cvf /dev/rmt/0n subscriptions.unl
tar -uvf /dev/rmt/0n subscription_list.unl
mt -f /dev/rmt/0 rewind
Remove the subscriptions.unl and the subscription_list.unl files

from omcadmin home directory, if no longer required:
rm subscriptions.unl
rm subscription_list.unl
8-33
Oct 2009
Checking the PM database
Check the PM database

To check the PM database, follow the procedure below. Copy the checklist in Table 14-6
to record the checks.
Procedure 8-16
Check that the PM database is online by entering the following

omc_env
onmonitor
This utility reports that the database is in an online mode.
Check the IDS log file for errors and check-pointing by entering the
following command as user omcadmin:
This log file should show that checkpoints are completed successfully,
in particular when the server is initialized.
Check that the IDS log files are rolled over by entering the following
cd $INFORMIXDIR
ls -l online.log_OMC*
Log files should exist in the form:
Check the output of the onmode_pm cron job by entering the following
cd /var/mail
more omcadmin | grep onmode_pm
Disk space is not being consumed.
Applications are disconnected and reconnected successfully when

required.
cd $OMC_TOP/logs
Check that the PM sqlhosts file has the correct entries for the Informix
Server by entering the following commands as user omcadmin:
more /usr/informix/etc/sqlhosts_OMC
Output should look similar to the example shown in PM sqlhosts.
Continued
8-34
68P02901W19-S
Oct 2009
Procedure 8-16
7
PM sqlhosts file
Checking the PM database (Continued)
Check the /etc/services file to ensure that a port number exists for the
PM IDS by entering the following command as user omcadmin:
more /etc/services
An entry should exist similar to the following:
inf7_OMC_serv
5000/tcp
Check the shared memory structure of the PM IDS by entering the

following command as user informix:
onstat
Output should be similar to that shown in onstat output for PM
database section.
Check the status of the dbspaces and chunks of the PM IDS by entering
the following commands as user informix:
onstat -d
Output should be similar to that shown in onstat -d output for PM
database section.
10
When performing an archive of the PM DB ensure that the TAPEDEV

parameter is set to /dev/rmt/0 by entering the following commands
as user omcadmin:
more /usr/informix/etc/onconfig | grep TAPEDEV
PM sqlhosts file
The PM sqlhosts file is located as:
/usr/informix/etc/sqlhosts_OMC
A typical example of the contents of the sqlhosts_OMC file is shown as follows:
omc_sys1
onipcshm
omc_splat
60k_OMC_shm
omc_sys
ontlitcp
omc_splat
inf7_OMC_serv
omc_mib
ontlitcp
omc_splat
inf7_MIB_serv
mcOMC175003041066 ontlitcp
somc31
mcOMC
A corresponding port number must also exist in the /etc/services file. An example line entry
is shown as follows:
inf7_OMC_serv 5000/tcp
# OMC database I
nformix DSA instance
onstat output for PM database

A typical example for the onstat utility output display for the PM database is shown as follows:
IBM Informix Dynamic Server Version 9.40.UC4
--
On-Line -- Up 09:48:19 -- 467968 Kbytes Userthreads
68P02901W19-S
8-35
Oct 2009
onstat output for PM database
address flags
sessid
user
tty
nreads
nwrites 24a67018 ---P--D 1
root
root
80
729 24a68260 ---P--F

0
root
893 24a67c48 ---P--F
root
62 24a68878 ---P--F
root
0 24a694a8 ---P--F
root
0 24a69ac0 ---P--- 11
0
tout locks
-
136 24a67630 ---P--F 0
0 24a68e90 ---P--F 0
0
wait
root
root
0 24a6a0d8 ---P--B 12
root
30
64 24a6a6f0 Y--P--- 80
omcadmin console
2546c248 0
0 24a6ad08
26
Y--P--- 81
0
omcadmin console
0
root
24a6b938 Y--P--- 10
2546c6f8 0
25610dd8 0
25595fc8 0
0 24a6d198
256358e0
0 24a6d7b0 Y--P--- 86
omcadmin console
2566f3d8 0
0 24a6ddc8 Y--P--- 87
1
0 24a6e3e0
omcadmin -
omcadmin -
12
Y--P--- 88
256909d8 0
0 24a6e9f8 Y--P--- 89
omcadmin 0
255c3890 0
omcadmin console
0
omcadmin console
0
Y--P--- 85
2566fed0 0
0 24a6c568 Y--P--- 83
24a6cb80 Y--P--- 84
0 24a6bf50
omcadmin console
omcadmin console
omcadmin console
Y--P--- 82
1
25595e30
0 24a6b320 ---P--D 15
256d6590 0
0 24a6f010 Y--P--- 90
omcadmin -
256f10c8 0
24a6f628 Y--P--- 79
256f1e80 0
omcadmin console
0
omcadmin console
0 24a6fc40 Y--P--- 92
25720a78 0
0 24a70258 Y--P--- 93
omcadmin console 1
1
8-36
0 25757678 0
0 25 active, 128 total, 26 maximum
68P02901W19-S
Oct 2009
onstat -d output for PM database
concurrent Profile dskreads pagreads bufreads %

cached dskwrits pagwrits bufwrits %cached
3668
4226
561452
6645
61471
start
read
7060
gp_curs 0
ovbuff
usercpu
dltouts
da-RA
85.78
11.1
bufwaits lokwaits lockreqs

ckpwaits compress
1013573
1056
117
ovuserthread
numckpts
24
7855
ovlock
syscpu
249
seqscans 38
A idx-RA
commit
0 gp_read gp_write
15
192674
0
0
flushes 0
425
delete
gp_alloc gp_free
deadlks
20238
rewrite
18798
gp_rewrt gp_del
1868
96.96 isamtot open
write
rollbk 473705
2247
99.35
1674
0
ixda-R
RA-pgsused lchwaits
459
537
34

A typical example for the onstat -d utility output display for the PM database is shown as follows:
-- On-Line --
Up 09:50:36 -- 467968 Kbytes Dbspaces address number

fchunk
nchunks
flags
owner
flags
name 2490e7d8 1
0x20001
informix rootdbs 25198948 2
0x20001
informix omc_db_plog 25198a98 3
0x20001
informix omc_db_llog 25198be8 4
0x60001
informix omc_db_sp1 25198d38 5
0x60001
informix omc_db_sp2 25198e88 6
0x60001
informix omc_db_sp3 25199018 7
0x60001
0x60001
informix omc_db_sp5 251992b8 9
0x60001
0x60001
10
0x60001
11
informix omc_db_sp8 251996a8 12
0x60001
12
informix omc_db_sp9 251997f8 13
0x60001
13
0x60001
14
informix omc_db_sp11 25199a98 15
0x60001
15
informix omc_db_sp12 25199be8 16
0x2001
16
N T
68P02901W19-S
informix omc_db_temp 16 active, 2047 maximum
8-37
Oct 2009
Chunks address chunk/dbs

pathname 2490e928 1
offset
/dev/omc_db_root 25197158 2
PO--
PO-B
1171728
bpages
129000
256003
767997
4
2047998
1171728
2047998
1171728
2047998
/dev/omc_db2 25197778 6
PO-B
383944
/dev/omc_db1 251975f0 5
PO-B
PO--
256000
3
flags
998794
/dev/omc_db_logs 25197468 4
1171728
free
1023998
/dev/omc_db_logs 251972e0 3
PO--
size
2047998
2
2047998
2
/dev/omc_db3 25197900 7
PO-B
/dev/omc_db4 25197a88
1171728
PO-B
PO-B
/dev/omc_db5
25197c10 9
2047998
1171728
25197d98 10
10
2047998
1171728
PO-B
/dev/omc_db7
25198018 11
11
2047998
1171728
PO-B
/dev/omc_db8
251981a0 12
12
2047998
1171728
PO-B
/dev/omc_db9
25198328 13
13
2047998
1171728
PO-B
/dev/omc_db10
251984b0 14
14
2047998
1146126
PO-B
/dev/omc_db11
25198638 15
15
2047998
1146126
PO-B
/dev/omc_db12
251987c0 16
16
1023998
1023945
PO--
/dev/omc_db6
/dev/omc_db_temp
16 active, 32766 maximum Expanded chunk capacity mode: enabled
8-38
68P02901W19-S
Oct 2009
Checking the CM database
Check the CM database

Use the following procedure to check the CM database. Copy the checklist in Table 14-7
Procedure 8-17
Check that the MIB database is online by entering the following

mib_env
onmonitor
This utility reports that the database is in an online mode.
Check the IDS log file for errors and check-pointing by entering the
following commands as user omcadmin:
This log file should show that checkpoints are completed successfully,
in particular when the server is initialized.
Check that the IDS log files are rolled over by entering the following
cd $INFORMIXDIR
Log files should exist of the form online.log_OMC.ddmmyyyy
Check the output of the onmode_mib cron job by entering the following
cd /var/mail
more omcadmin | grep onmode_mib
Check the dbspace and tblspace allocation for the CM IDS

by entering the following commands as user omcadmin:cd
$DBMS_ROOT/SBINomc_db_ckspace mib. The output should be similar
to that shown in the section omc_db_ckspace utility on page 8-10.
Check that the CM database sqlhosts file has the correct entries for
the Informix Server by entering the following commands as user
omcadmin:
more /usr/informix/etc/sqlhosts_MIB
Output should look similar to the example shown in the section CM
sqlhosts file on page 8-40.
Check the /etc/services file to ensure that a port number exists for the
CM IDS by entering the following commands as user omcadmin:
more /etc/services
inf7_MIB_serv 5010/tcp
Continued
68P02901W19-S
8-39
Oct 2009
CM sqlhosts file
Procedure 8-17
Checking the CM database (Continued)
Check the shared memory structure of the CM IDS by entering the

following commands as user informix:onstatoutput is similar to that
shown in the section onstat output for CM database on page 8-41.
Check the status of the dbspaces and chunks of the CM IDS by entering
onstat -d
Output should be similar to that shown in the section onstat -d output
for CM database on page 8-42.
10
When performing an archive of the CM DB ensure that the TAPEDEV

parameter is set to /dev/rmt/0 by entering the following commands
as user omcadmin:
CM sqlhosts file
The CM sqlhosts file is located as:
/usr/informix/etc/sqlhosts_MIB
A typical example of the contents of the sqlhosts_MIB file is shown as follows:
omc_mib1
onipcshm
omc_splat
ontlitcp
omc_splat
inf7_MIB_serv omc_sys
omc_splat
inf7_OMC_serv mcMIB175003041066 ontlitcp
omc31
60k_MIB_shm omc_mib
ontlitcp
s
mcMIB
A corresponding port number must also exist in the /etc/services file. An example line entry
is shown as follows:
inf7_MIB_serv 5010/tcp
# MIB database Informix
DSA instance
8-40
68P02901W19-S
Oct 2009
onstat output for CM database
onstat output for CM database

A typical example for the onstat utility output display for the CM database is shown as follows:
--
On-Line -- Up 23:23:25 -- 148480 Kbytes Userthreads

address
flags
sessid
nreads
nwrites 1120f018 ---P--D 1
root
root
44 112102
omcadmin
0 112114a8 Y--P--- 21
11bae8a8 0
root
34
0 112120d8 Y--P--- 23
omcadmin -
119d3cc0 0
Y--P--- 19
1
41
1
11990eb8 0
55
omcadmin -
omcadmin 43
omcadmin -
11aaa168 0
41
11aaad78 0
Y--P--- 30
33
omcadmin -
0 11214b80 Y--P--- 29
38
0 11215198
11aedea0 0
omcadmin -
omcadmin Y--P--- 34
56
omcadmin
11bc02b8 0
49
0 112169f8
11c00598 0
0 11217010 Y--P--- 47
1
29
0 112163e0 Y--P--- 33
omcadmin -
40
11b35c10 0
0 11215dc8 Y--P--- 32
11b548d8 0
11a2c518 0
omcadmin -
0 112157b0 Y--P--- 31
119950c8
0 11214568 Y--P--- 28
omcadmin -
11d47700 0
0 11213938 Y--P--- 26
11a26888 0
23
0 112126f0
omcadmin -
11213f50 Y--P--- 27
298
0 11213320 Y--P--- 25
11995c88 0
omcadmin console
0 11212d08 Y--P--- 24
root
58
0 11211ac0 ---P--D 15
0
-
0 11210e90 Y--P--- 10
117f5fc8 0
tout locks
260 1120fc48 ---P--F
root
omcadmin 0
0
root
0 11210878 ---P--B 12
console
wait
103 1120f630 ---P--F 0

0
60 ---P--- 11
0
tty
38
user
omcadmin -
0 22 active,
maximum concurrent Profile dskreads pagreads bufreads

%cached dskwrits pagwrits
1589
1716
188887
128 total, 24 bufwrits %cached

99.16
2255
85.54 isamtot open
delete
commit
2059
gp_rewrt gp_del
68P02901W19-S
rollbk 161392
1
1133
326
start
23657
702
read
30306
write
60035
rewrite
46
0 gp_read gp_write
gp_alloc gp_free
gp_curs 0
8-41
Oct 2009
onstat -d output for CM database
0
syscpu
ovlock
numckpts flushes 0
564
139122
ixda-RA idx-RA
da-RA
usercpu
18.75
bufwaits lokwaits lockreqs deadlks
compress seqscans 155

990
ovuserthread ovbuff
dltouts
1.55
ckpwaits
RA-pgsused lchwaits

A typical example for the onstat -d utility output display for the CM database is shown as
follows:
-- On-Line --
Up 23:23:57 -- 148480 Kbytes Dbspaces address number

fchunk
nchunks
flags
owner
flags
name 1110e7d8 1
0x20001
informix rootdbs 119044b0 2
0x20001
informix physdbs 11904600 3
0x20001
informix logsdbs 11904750 4
0x2001
N T
informix tempdbs 119048a0 5
0x20001
informix mib_db_sp1 5 active,
2047 maximum Chunks address chunk/dbs

free
bpages
921598
475696
PO--
256000
11904018 3
1023998
PO-797280
size
767997
4
1
PO--
/dev/mib_db_logs
583624
921601
PO-102399
/dev/mib_db 11904328 5
PO--
/dev/mib_db 1123fdf0 2
177100
256003
/dev/mib_db_logs 119041a0 4
102346
offset
flags pathname 1110e928 1
/dev/mib_db1
5 active,
32766 maximum
8-42
68P02901W19-S
Oct 2009
CAUTION
This procedure is a drastic measure, and the CM database should only be dropped and
recreated if absolutely necessary. Contact Motorola Support for further information.
Use the following procedure to drop and then recreate the CM database:
Procedure 8-18
68P02901W19-S
Oct 2009
Shut down the OMC-R processes by logging in to the system processor

as user omcadmin and entering the following command:
omc stop
To drop the CM database, enter the following command as user

informix:
svcadm restart -st informix/cm
(to verify that the CM database engine is online again).
Enter the following commands as user omcadmin:

mib_env
dbexport mib_db -ss
isql - drop database mib_db;
To recreate the CM database, enter the following commands as user

root:
cd /usr/omc/sbin
cm_setup
Restart the OMC-R processes by entering the following command as

user omcadmin:
omc start
8-43
8-44
68P02901W19-S
Oct 2009
Chapter
9
X.25 management
68P02901W19-S
Oct 2009
9-1
Overview
Overview
This chapter provides a technical description of X.25 management functions.

9-2
X.25 application management on page 9-3.
Basic X.25 commands on page 9-7.
X.25 directory structure on page 9-8.
Starting and stopping X.25 on page 9-9.
Updating X.25 link configuration on page 9-13.
Replacing the HSI card on page 9-17.
Checking X.25 connectivity on page 9-18.
68P02901W19-S
Oct 2009
X.25 application management
X.25 application management
Overview of the X.25 software

The X.25 software application controls the routing of the data from the OMC-R system processor,
through the packet switch and multiplexer, to the individual network elements. This data is sent
using the packet switch protocol.
When installation has been completed, the X.25 software will load and execute automatically in
accordance with the startup or shutdown procedure.
The X.25 application is implemented for the OMC-R using SunLink X.25.
Figure 9-1
Centralized use of X.25
Configuring X.25
The full procedure required to configure X.25 for the OMC-R is described in the Installation and
Configuration: OMC-R Clean Install (68P02901W47) manual.
Configuring OMC-R processes for X.25

The OMC-R applications that handle incoming or make outgoing X.25 connections, must be
configured in the OMC-R software. The following configuration file is required to configure
the X.25 connections:
/usr/omc/config/global/x25_config
68P02901W19-S
9-3
Oct 2009
Configuring OMC-R processes for X.25
Each line in the x25_config file contains 11 fields, as illustrated in Figure 9-2.
Figure 9-2
x25_config configuration file details.
1 x25_chan1 0 2345678 H g_bootload OMC_BL X25 128 2 50

3 x25_chan3 2 6161616 H g_ei OMC_EI X25 128 2 500
5 x25_chan5 2 53253232 H - OMC_RL X25 128 2 500
6 x25_chan6 0 71271213 H - OMC_PU X25 128 2 50
7 x25_chan7 1 31413141 H - OMC_PU X25 128 2 50
NOTE
The number of OMC_PU application processes may vary depending on the TCH
capacity of the machine. This is described in the Installation and Configuration:
OMC-R Clean Install (68P02901W47) manual.
The 11 fields of the x25_config are defined as follows:
Record number: The record number within the file.
X.25 channel number: In the format x25_chann where n is the channel number.
Port/link identifier: This field is the link identifier used by the application. The value of this
field corresponds to the X.25 link configured within SunLink X.25. Each link will be associated
with either an E1 channel or a HSI port. Each E1 channel is associated with a specific NE. It is
possible to run each X.25 application process on a single HSI port.
X.121 application address: The local X.121 address for an application (maximum 14 digits).
X.25 card type: This field refers to the HSI card used in the system processor for X.25
connectivity. H is the only option available.
Process call characteristic: The process call characteristic field. A value of - indicates that
the process makes calls. Any other value in this field indicates that the process listens for
incoming calls.
9-4
68P02901W19-S
Oct 2009
Rules for the x25_config file
Application process: X.25 application process can be one of the following:
OMC_BL - Bootload.
OMC_EI - Event Interface.
OMC_RL - Remote Login.
OMC_PU - Upload.
Protocol: Protocol being used by a process. The only valid value in this field is X25.
Packet size: Maximum X.25 packet size to be used over connection.
Window size: Maximum X.25 window size to be used over connection.
Poll time-out: Time-out value specified in poll system call (seconds).
Rules for the x25_config file

Each entry is separated by a space. The order of entries in the file is significant and is as follows:
1.
The first and second lines are for the bootloader (incoming calls). For redundancy
purposes, entry 1 should be configured to use a different link/port to entry 2.
2.
The third and fourth lines are for the event interface (incoming calls). For redundancy,
entry 3 should be configured to use a different link/port to entry 4.
3.
The fifth line is for the remote login (outgoing calls).
4.
The sixth and seventh lines are for the uploader (outgoing calls). For redundancy, entry 6
should be configured to use a different link/port to entry 7.
5.
For high-capacity systems, there are two additional OMC_PU lines. The additional lines are
required because there are four upload channels.
OMC X.25 application design

The use of X.25 is centralized into separate X.25 appl OMC-R service provider applications
on the system processor. OMC-R system processor applications (EventInterface, Upload,
Download and Rlogin) currently interface to the x25appl applications.
The x25appl applications are the only applications to interface directly to the X.25 packet
switch through the SunLink X.25 interface. The x25appl applications communicate with the
OMC-R applications using the Motorola IPC mechanism. Outgoing calls are made on demand
when requested by the remote login and upload applications.
The x25stat utility is provided to query the status of the centralized X.25 application. This
utility will be run by the OMC-R system administrator, not by the end users. It returns the
number and type of SVCs currently open.
68P02901W19-S
9-5
Oct 2009
OMC X.25 application design
NOTE
The x25appl processes are restartable processes, that is, they can be restarted
without restarting the whole OMC-R. A x25appl process is to be restarted to pick
up changes made to the x25_config file. Refer to Restartable processes on page
2-49. This is not the same as stopping and starting the X.25 system of the OMC-R,
described in Starting and stopping X.25 on page 9-9.
9-6
68P02901W19-S
Oct 2009
Basic X.25 commands
Basic X.25 commands
Starting and stopping X.25

X.25 may be started or stopped on a single link, or may be started and stopped as a service.
Procedures to start or stop a single link or the X.25 service must be run as user root.
The start or stop commands are run using the X.25 tool. This tool enables the user to stop and
start the X.25 service, and stop and start a single link.
NOTE
Stopping and starting the SUN X.25 system on the OMC-R is NOT the same as
restarting a x25appl process.
Replacing the HSI card

When the OMC-R network card is to be replaced, X.25 must be fully shut down.
Updating X.25 link configuration

The X.25 tool is used when updating the configuration of a link, which may reconfigure a link
actively, without bringing down the service, or store new link configuration information when
the link is restarted.
Further details of X.25 commands

For further details of X.25 commands, refer to the Managing SunLink X.25 9.2 manual.
68P02901W19-S
9-7
Oct 2009
X.25 directory structure
X.25 directory structure
The directory structure relevant to X.25 configuration and maintenance on the system processor
is shown in Table 9-1. All files and utilities are immediately under the root (/).
Table 9-1
Files and utilities for X.25 configuration and maintenance
File or utility
9-8
Description
/usr/omc/config/global/
x25_config
Configuration file for OMC applications which handle

incoming or make outgoing calls.
/etc/rc2.d/S87x25net
Network daemon for starting or stopping X.25 on bootup of

the system processor.
/etc/init.d/x25.control
Starts all the necessary daemons and brings up the software.
/opt/SUNWconn/x25/bin
/x25tool
X.25 configuration and administration utility.
/x25stat
Displays link statistics.
/x25trace
Protocol level tracing facility.
/x25info
Provides useful status information.
/etc/opt/SUNWconn/x25
/netconf
Describes the configuration of the STREAMS network

constructed by X25netc.
/etc/opt/SUNWconn/x25
/config
Directory containing configuration files.
/pad
User interface to pad facilities.
/opt/SUNWste
X.25 license facilities.
68P02901W19-S
Oct 2009
Stopping OMC-R processes

Before doing major reconfiguration on X.25, for example, replacing X.25 the hardware
or upgrading software, the OMC-R should be stopped as described in Manual startup and
shutdown of OMC-R software on page 7-12.
Overview of the x25tool

The x25tool provides a graphical interface to the parameters required to configure and maintain
the SunLink X.25 software. The x25tool enables the user to stop and start the X.25 service and
must be run as user root.
Starting up the x25tool

Use the following procedure to start the x25tool:
Procedure 9-1
68P02901W19-S
Starting the x25tool
Set the DISPLAY variable to the system processor by entering the

following commands:
/bin/csh
cd /
setenv DISPLAY omc_splat:0.0

cd /opt/SUNWconn/bin
./x25tool &
The x25tool 9.2 window is displayed on the system processor as shown
in Figure 9-3.
9-9
Oct 2009
Starting up the x25tool
Figure 9-3
9-10
x25tool 9.2 window
68P02901W19-S
Oct 2009
Starting X.25
Starting X.25
Use the following procedure to start the SunLink X.25 software:
Procedure 9-2
Start the x25tool as described in Starting up the x25tool on page 9-9.
From the Network menu select Start X.25. The message window shown
in Figure 9-4 indicates that X.25 has been started.
Figure 9-4
68P02901W19-S
Starting the SunLink X.25 software
X25 Message window: process started
9-11
Oct 2009
Stopping X.25
Stopping X.25
Use the following procedure to stop the SunLink X.25 software:
Procedure 9-3
Start the x25tool as described in the previous section.
From the Network menu select Stop X.25. The message window shown
in Figure 9-5 indicates that the X.25 has been stopped.
Figure 9-5
9-12
Stopping the SunLink X.25 software
X25 Message window: process stopped
68P02901W19-S
Oct 2009
Configuring X.25 parameters

To update the configuration of the X.25 link, carry out the following procedure. Updating the
configuration of the X.25 link requires the user to interface with the x25tool. Reconfiguration is
possible on the active links such that the X.25 service need not be stopped.
Use the following procedure to configure the X.25 link:
Procedure 9-4
68P02901W19-S
Invoke the x25tool window as described in Starting and stopping X.25

on page 9-9.
To modify an existing HSI link, select the link in the x25tool window.
Click Modify on the right side of the x25tool window.

The Link Editor window is displayed, as shown in Figure 9-6.
Make the necessary changes.
Click Apply to save the changes and close the window.
9-13
Oct 2009
Figure 9-6
9-14
Link editor window
68P02901W19-S
Oct 2009
Configuring LAPB parameters

Use the following procedure to change parameters in the LAPB configuration:
Procedure 9-5
68P02901W19-S
Changing parameters in the LAPB configuration
Select the link in the x25tool window.
Click Modify on the right side of the x25tool window.

The Link Editor window is displayed, as shown in Figure 9-6.
Under Advanced Configuration on the right side of the Link Editor,

click LAPB, WAN.
The LAPB and WAN Parameters window is displayed, as shown in
Figure 9-7.
Make the necessary changes.
Click Apply.
9-15
Oct 2009
Figure 9-7
9-16
LAPB and WAN parameters window
68P02901W19-S
Oct 2009

Use the following procedure to stop and start X.25 to enable the HSI card to be replaced:
Procedure 9-6
68P02901W19-S

su - omcadmin: svcadm
disable omc
Stop SunLink X.25 as described in Starting and stopping X.25 on page 9-9.
Use the following commands to inform all users that maintenance to the X.25
HSI card is to be carried out:
wall<hit enter>
System coming down immediately for vital maintenance<hit enter>
^d
Bring the system down to the PROM mode: /usr/sbin/shutdown -i5 -g0 -y
The PROM monitor mode OK prompt is displayed.
Power off the system processor.
Remove and replace the network interface card by following the instructions
in the HSI installation guide.
Power up the system.
9-17
Oct 2009
Checking X.25 connectivity
X.25 connectivity checklist

Use the following procedure to check X.25 connectivity. Copy the checklist provided in
Procedure 9-7
9-18
Check the contents of the x25_config file by entering the following

more x25_config
The file contents should be similar to the example shown in Figure 9-2.
The correct entries are required to configure x25 connections.
Check the integrity of x25 by entering the following commands as

user root:
Refer to x25stat output on page 2-76 for example, output.
Check the status of the network by entering the following commands

as user root:
/usr/bin/netstat -a
Refer to OMC-R system information on page 13-8 for example, output
of the netstat command.
68P02901W19-S
Oct 2009
X.25 recovery from HSI failure
X.25 recovery from HSI failure
Issue A: Sun IB module/IO board hardware failure

In the event of an IB module/IO module failure on a Sun (SF4800/4900/E3x00) platform, the
system may restart or hang until the operator resets the machine manually. An IB module failure
implies that the onboard HSI card is rendered out of service. When the system restarts, it does
not detect the difference between a badly configured system and a system where one of the HSI
cards was faulty. Even though there may be still at least one remaining working HSI card, the
X.25 software will attempt to start up but will fail to start. Using the X.25tool to restart the X.25
software, the operator can see output similar to the following from the X.25tool:
<09/29/05 14:26:00>
<09/29/05 14:26:05> Starting the X.25 software - please wait
<09/29/05 14:26:05> X.25 : Creating link 0...
<09/29/05 14:26:05> X.25 : link 0 has been started
<09/29/05 14:26:05> X.25 : Creating link 1...
<09/29/05 14:26:05> X.25 : Creating link 2...
<09/29/05 14:26:05> X.25 : Creating link 3...
<09/29/05 14:26:05> X.25 : Creating link 4...
<09/29/05 14:26:05> X.25 : failed to open driver "/dev/hihp4" : No such device
<09/29/05 14:26:05> X.25 : Can't create level 2 for link 4
<09/29/05 14:26:06> X.25 : link 4 has been stopped
<09/29/05 14:26:06>
<09/29/05 14:26:07> The network failed to come up correctly.
<09/29/05 14:26:07>
The operator is advised to call their local Sun hardware support to replace the faulty hardware
Issue B: HSI card hardware failure

A HSI card failure alone should not cause the system to reboot (unlike an IB module failure).
If one of the HSI cards is out of service, and the X25 software is restarted or the system is
rebooted, the X25 software fails to start.
68P02901W19-S
9-19
Oct 2009
Issue C: OMC-R configuration to allow X25 operate using the remaining hardware
Issue C: OMC-R configuration to allow X25 operate using the

remaining hardware
When the HSI links that service statistics and uploads goes down, then the OMC-R application
does not use the other available HSI links as configured in the x25_config file. This occurs
until the faulty hardware can be replaced.
The following issues may arise:
PM Statistics uploads do not swap over to the next available x25appl with a working
HSI link.
BSS database (.002) uploads will swap over to an available HSI link for the same BSS.
However users may have to request the upload a second time as the first request may fail, and
the second attempt will succeed on the next available x25appl.
9-20
68P02901W19-S
Oct 2009
Recovery
Recovery
Issue A: Recovery from a Sun IB module/IO board hardware

failure
After the system is rebooted, as one of the IB modules (and hence HSI cards) is out of service
then the X25 software may fail to start. The following procedure describes how to restart the
X25 software:
Procedure 9-8
Restarting the X25 software
Identify the X.25 links associated with the out-of-service IB module (HSI
card). Use the X.25tool to start the X.25 software and view the output. A
sample output is as follows:
Starting the X.25 software - please wait

X.25 : Creating link 0...
X.25 : link 0 has been started
X.25 : failed to open driver "/dev/hihp4" : No such device
X.25 : Can't create level 2 for link 4
X.25 : link 4 has been stopped
The network failed to come up correctly.
The sample output shown above indicates that X.25 fails to start link 4. This
corresponds to the failure of the IB8 module on a SunFire4800.
Continued
68P02901W19-S
9-21
Oct 2009
Issue B: Recovery from HSI card hardware failure
Procedure 9-8
2
Restarting the X25 software (Continued)
Remove the link files associated with the failed HSI card, to be able to start
the X.25 software.
For each of the links found to be out of service in step 1, rename the
corresponding link_config_000x.cfg file as follows:
As user root, execute the following command to rename the corresponding
link_config_000x.cfg file:
cd /etc/opt/SUNWconn/x25/config
Execute the following command to list out all the link files:
ls -l link_config*
A sample output is shown below:
-rwxr-xr-x 1 root other 2249 Nov 16 17:08 link_config_0000.cfg
The sample output shown above indicates that link 4 failed to start up. This
indicates that all the files associated with the HSI card have to be renamed
as follows:
mv
mv
mv
mv
link_config_0004.cfg
link_config_0004.cfg.orig
Use X.25 tool to restart the X.25 software.
Proceed to recovery method for Issue C below to reconfigure the X.25_config

file.
Issue B: Recovery from HSI card hardware failure

If one of the HSI cards is out of service, and the X25 software is restarted or the system is
rebooted, the X25 software does not start.
However until the hardware is replaced, follow all of the recovery steps for Issue A above to
ensure that X25 software will start.
Until the HSI card is replaced, X25 tries to use faulty ports which are still configured in the
x25_config file.
Proceed to recovery method for Issue C below to reconfigure the x25_config file.
9-22
68P02901W19-S
Oct 2009

Recovery of OMC-R configuration to allow X25 operate using the remaining hardware
Issue C:
Issue C: Recovery of OMC-R configuration to allow X25 operate

using the remaining hardware
When the HSI link that is servicing statistics and uploads goes down, the OMC-R application
does not automatically use the other available HSI links configured in the x25_config file.
The following procedure details the workaround to edit the x25_config file and remove the
references to the out-of-service x25 links, restart x25 and the OMC-R application:
Procedure 9-9
Editing the x25_config file
As user omcadmin, execute the following command to determine the HSI

ports mapped to the different OMC applications:
cat x25_config
The following example shows a sample output where the numbers in the
third column correspond to the HSI port identifier:

5 x25_chan5 5 511205 H - OMC_RL X25 128 2 500
6 x25_chan6 1 511205 H - OMC_PU X25 512 7 50
7 x25_chan7 5 511205 H - OMC_PU X25 512 7 50
2
Determine the bad ports. Use the x25 tool to determine which ports are
not at NORMAL state. In the example shown in step 1, ports 4, 5, 6 and
7 are out of service.
As user omcadmin, execute the following commands to backup the

x25_config file:
cp p x25_config x25_config.orig
Continued
68P02901W19-S
9-23
Oct 2009
Issue C: Recovery of OMC-R configuration to allow X25 operate using the remaining hardware Chapter 9: X.25 management
Procedure 9-9
4
Editing the x25_config file (Continued)
As user omcadmin, edit the x25_config file (using vi or other editors) to

replace references to the out-of-service HSI ports with in-service ports on
the remaining HSI card. Delete references to ports 4, 5, 6 and 7 from the
x25_config file and save the file. The following output shows the x25_config
file:

5 x25_chan5 1 511205 H - OMC_RL X25 128 2 500
6 x25_chan6 1 511205 H - OMC_PU X25 512 7 50
7 x25_chan7 1 511205 H - OMC_PU X25 512 7 50
9-24
Once the above changes have been made to the x25_config file, restart x25
software using x25 tool.
As user omcadmin, stop the OMC-R using the following command:

omc stop
Restart the OMC-R using the following command:
omc start
Replace the modified x25_config file with the original copy.
Move all the link files renamed during the recovery method.
68P02901W19-S
Oct 2009
Chapter
10
OMC Utilities
68P02901W19-S
Oct 2009
10-1
Overview of utilities
This chapter describes the contents of a version of supplementary OMC Utilities. These have
been packaged as MOTu1900, on the GSR9 CD-ROM.
These utilities were developed by Motorola to improve specific routine Operation and
Maintenance (O and M) activities. The utilities are intended to provide interim solutions for
OMC operators, particularly in a multi-OMC-R environment.
The utilities are supplementary to the full OMC-R Release. Support will be provided directly
from the OMC Customer Support group.
This chapter also describes the purpose, installation and execution of the OMC utilities, and the
output generated by them.
NOTE
It is recommended to reinstall the operation and maintenance utilities when
performing a major upgrade to a new release as they may change from release to
release.
CAUTION
Do not execute a CTRLc while any of the scripts are executing and allow all scripts to
complete execution once they are started.

The utilities provided are listed in Table 10-1. They are described in detail in the following
sections.
10-2
68P02901W19-S
Oct 2009
Table 10-1
Alarm/Event Window
List of OMC utilities
Utility
Purpose
finder
Find Device Function
net_reports
Useful Network Reports
dri_status
DRI Status (OOS/Undefined) report
rtf_status
RTF Status (OOS) Report
site_outage
SITE Outage Time Report
add_nei
Add Neighbor both ways
del_nei
Delete Neighbor
nei_sync
Neighbor Synchronization
proxy_sync
Proxy Cell Synchronization
reparent_site
SITE Reparenting
ne_counter
NE and TCH Count Report
These utilities can be invoked on a client machine when remotely logged in to the OMC system
processor.
Alarm/Event Window
The utilities can be invoked from the Tools menu on the Alarm Window.
Click on the Alarm Window icon or the Event Management icon to bring up the Alarm Window.
There is a new pull-down menu called Tools in this window. The utilities have now been
categorized into three areas:
Neighbor Utilities
Network Reports
Status Reports
68P02901W19-S
10-3
Oct 2009
Installation
Installation
Adding operation and maintenance utilities package
Check whether the OMC utilities package is already installed by executing the following
pkginfo -l MOTu1900
If the output of this command is as follows, then proceed to the Add Packages section:
ERROR: information for MOTu1900 was not found
If the output of this command shows that this package is already installed, then remove the
package by executing the following command as user root:
pkgrm MOTu1900
Add Packages
Insert the GSR9 DVD into the DVD-ROM drive and add the package by executing the following
cd /cdrom/cdrom0/s0/suninstall/Packages
pkgadd -d MOTu1900 all
Install Utilities
An installation utility is provided to install the utilities and their associated files and directories
on to the OMC System Processor at /usr/omc/current/sbin. Only the OMC administrator can
perform the installation and rollback of these utilities.
NOTE
10-4
In the case of multiple OMCs, ensure that they are trusted hosts of each other
and that the users are common to all OMCs.
The existing stty echoe and stty erase commands in the .cshrc for omcadmin
and all other users must be commented out.
68P02901W19-S
Oct 2009
Installation
Input
Files associated with the operation and maintenance utilities can be copied to
/home/omcadmin/Utilities_Install upon successful installation of the operation and
maintenance utilities package.
Execute the following commands as user root:
cd /home/omcadmin/Utilities_Install
./install_utilities.sh
NOTE
Sample input and output data are used in the examples below.
This install script sets up these OMC Utilities across multiple OMCs Enter the
hostname and q to finish hostname list or Control C to Exit laurel
Enter the hostname and q to finish hostname list or Control C to Exit q
1 hostname(s) is/are entered laurel
Enter the three digit Mobile Country Code 655
Enter the two digit Mobile Network Code 01
The Mobile Country Code 655
The Mobile Network Code 01
Are the Mobile Country Code and Mobile Network Code correct: (y/n)? y
Output
Creating the directories and copying the essential .sh and .ace
files across the hosts laurel
Creating the script which collects the required bsic and rfplan data
and puts into rfplan.txt and bsicnet.txt generating the getdata.sh
file which will then be used by the finder script to rsh into each
omc and get the data - the RF part laurel
68P02901W19-S
10-5
Oct 2009
Rollback
Directories
The files and directories necessary to support the utilities are listed below:
/usr/omc/current/sbin/ace
arfcn.ace
bsic_reg.ace
dri2.ace
name_cl_r.ace
neisync.ace
arfcn_reg.ace
check_nei.ace
dri2_reg.ace
nei.ace
proxy_sync.ace
bsic.ace
chk_nei_r.ace
name_cell.ace
nei_reg.ace
rtfsite.ace
/usr/omc/current/sbin/ubin
addtime
chk_region
difftime2
get_date2
getdata.sh
gethostd.sh
percenttime
/usr/omc/current/sbin/udata
utilities_cron
omc.lst
Rollback
This will remove the utilities and their associated files from directories on the OMC System
Processor at /usr/omc/current/sbin.
10-6
68P02901W19-S
Oct 2009
Cleanup
Input
laurel:omcadmin>
/home/omcadmin/Utilities_Install/delete_utilities.sh
Output
Script to remove the utilities files.
Enter the hostname or q to quit laurel
Enter the hostname or q to quit q
1 hostname(s) is/are entered laurel
Removing the directories and deleting the files across the hosts...... laurel
Deleted . /usr/omc/current/sbin/dri_status Deleted .
/usr/omc/current/sbin/rtf_status
Deleted . /usr/omc/current/sbin/finder Deleted .
/usr/omc/current/sbin/net_reports
Deleted . /usr/omc/current/sbin/add_nei Deleted .
/usr/omc/current/sbin/del_nei
Deleted . /usr/omc/current/sbin/proxy_sync
Deleted . /usr/omc/current/sbin/nei_sync
Deleted . /usr/omc/current/sbin/ne_counter
Deleted . /usr/omc/current/sbin/site_outage
Cleanup
If the operator is completely happy with the operation and maintenance utilities, the cleanup
can be performed. Once the installation is complete, as user omcadmin, enter the following
command:
laurel:omcadmin>
rm -rf /home/omcadmin/Utilities_Install
Utility execution
Once installed, the utilities are contained in /usr/omc/current/sbin and can simply be invoked
from the command line by typing the utility name and the necessary parameters, for example:
dri_status -c /home/omcadmin
68P02901W19-S
10-7
Oct 2009
Finder
Finder
This utility enables the user to input a pattern, for example, a part of a SITE name or CELL
ID, and returns its essential details regardless of the OMC on which it resides. On the first
invocation of the finder utility, a fresh RF and BSIC plan should be created.
This results in creation of the following two files:
/usr/omc/current/sbin/udata/bsicnet.txt
rfplan.txt
All users have the ability to use this utility.
Input
laurel:omcadmin> finder
---------------------------------------------------Script to find CELLs, SITEs, BSCs or SMS CB MESSAGES
----------------------------------------------------
The BSIC and BCCHFREQ are taken from the MIB databases of all the OMCs To
generate a fresh RF and BSIC plan of the network now: enter yes. OR to use the
old RF and BSIC plans: press RETURN. OR to exit: press CTRL-C (^C).yes
Now collecting ARFCNs and BSICs for RFPlan... laurel
somc_cust...
Enter the pattern - part of cellid or site name or BSC name Or q to quit 01
Output
Frequencies
Hostname
BTS
Cell
ARFCN
TYPE
laurel
1600d2_test
rfd6rfd6 001-01-1-2
60
laurel
1600d2_test
rfd6rfd6 001-01-1-4
40
laurel
1600d2_test
rfd6rfd6 001-01-1-4
50
somc_cust
D1_BSS_1002
D1_BSS_1002:SITE-0:
001-01-1-2 60 0
somc_cust
D1_BSS_1002
D1_BSS_1002:SITE-0
001-01-1-4 40
Enter the pattern - part of cellid or site name or BSC name

Or q to quit
10-8
68P02901W19-S
Oct 2009
net_reports
net_reports
This utility provides the user with a menu of options for generating different reports from
the OMC.
The following network reports are available:
Neighbor List.
Name and GSM Cell ID and Location.
Adjacency Discrepancies.
SITE Name and RTFs.
SITE Cell and BSIC.

Usage: net_reports [ -r regionName ]
Input
laurel:omcadmin >
net_reports
***********************************
*
OMC/BSS Network Reports
Version GSR9
MOTOROLA
***********************************
1. Neighbor List
2. Name and Gsmcellid and Location
3. Adjacency Discrepancies
4. Site Name and RTFs
5. Site Cell and BSIC
6. Quit
Choose menu option:
68P02901W19-S
10-9
Oct 2009
net_reports
Output
Neighbour List
_____________
BSC
CELL ID
NEIGH CELL ID
BSIC
FREQ
BSS-1006
001-01-1-41
001-01-1-2
16
60
BSS-1006
001-01-1-41
001-01-1-1
16
25
BSS-1006
001-01-1-41
001-01-1-6
16
25
BSS-1006
001-01-1-41
001-01-1-3
16
30
BSS-1006
001-01-1-41
001-01-1-4
16
40
Quitting Network Reports

Exit any open reports to complete
Name & GSM Cell ID & Location

___________________________
BSC
SITE
Cell ID
Location
BSS-1006
BSS-1006:SITE-1:
035-02-1-0
BSS-1006
BSS-1006:SITE-4:
001-01-1-41
BSS-1006
BSS-1006:SITE-4:
035-02-04-0
Adjacency Discrepancies
_____________________
BSC
BSS-1006
10-10
Source
ADJ_CI
ADJ_BCCH
ADJ_BSIC
Target
TGT_CI
TGT_BCCH
TGT_BSIC
001-01-1-41
001-01-1-6
75
11
001-01-1-6
75
16
68P02901W19-S
Oct 2009
net_reports
Site Name and RTF

_________________
BSC
SITE NAME
CELLID
ARFCN
TYPE
BSS-1006
BSS-1006:SITE-4:
001-01-1-41
90
1600d2_test
1600d2_test:SITE-1:
001-01-1-1
25
1600d2_test
1600d2_test:SITE-1:
001-01-1-6
75
1600d2_test
1600d2_test:SITE-1:
001-01-1-6
85
Site Cell and BSIC

_______________
BSC
SITE
CELLID
BSIC
BSS-1006
BSS-1006:SITE-1:
035-02-1-0
BSS-1006
BSS-1006:SITE-4:
001-01-1-41
16
BSS-1006
BSS-1006:SITE-4:
035-02-0-0
1600d2_test
rfd6rfd6
001-01-1-2
Sample reports if executed with region option:
Neighbour List: Region: Region1

___________________________
BSC
CELL ID
NEIGH CELL ID
BSIC
FREQ
BSS-1006
001-01-1-41
001-01-1-2
16
60
BSS-1006
001-01-1-41
001-01-1-1
16
25
BSS-1006
001-01-1-41
001-01-1-6
11
75
BSS-1006
001-01-1-41
001-01-1-3
16
30
BSS-1006
001-01-1-41
001-01-1-4
16
40
68P02901W19-S
10-11
Oct 2009
net_reports
Name & GSM Cell ID & Location: Region: Region1

______________________________________
BSC
SITE
Cell ID
Location
BSS-1006
BSS-1006:SITE-1:
035-02-1-0
BSS-1006
BSS-1006:SITE-4:
001-01-1-41
BSS-1006
BSS-1006:SITE-4:
035-02-0-0
Site Name and RTF: Region: Region1

______________________________
BSC
SITE NAME
CELLID
ARFCN
TYPE
BSS-1006
BSS-1006:SITE-4:
001-01-1-41
90
1600d2_test
1600d2_test:SITE-1: 001-01-1-1
25
1600d2_test
1600d2_test:SITE-1: 01-01-1-6
75
1600d2_test
1600d2_test:SITE-1: 001-01-1-6
85
Site Cell and BSIC: Region: Region1

_____________________________
10-12
BSC
SITE
CELLID
BSIC
BSS-1006
BSS-1006:SITE-1:
035-02-1-0
BSS-1006
BSS-1006:SITE-4:
001-01-1-41
16
BSS-1006
BSS-1006:SITE-4:
035-02-0-0
1600d2_test
rfd6rfd6
001-01-1-2
68P02901W19-S
Oct 2009
dri_status
dri_status
This utility enables the user to generate a list of the DRIs which are OOS or Undefined in the
system over multiple OMCs. The users can provide the directory location to store the report.
Otherwise, the report would be saved in a file in the /tmp directory.
The user can generate a report for individual OMCs or for all OMCs together.
Usage
dri_status [ -r regionName ] [ -b OMCname ] [ -c directory] [ - l ]
The options available are:
-r regionName
Name of the region. If -r is used, the report generated will contain

the DRIs under the given region.
-b OMCname
OMCname is an OMC. Produces a report for OMCname. If -b is

not used, the default is the OMCs in omc.lst.
-l
This produces a list of OMCs in the network from which the user
must select one. Even if the -b option has been used, the input
from -l takes preference.
-c directory
Name of directory where the output is to be stored. If -c is not

used, the default directory is /tmp.
Input
laurel:omcadmin
> dri_status
This utility generates Device Status information,
to ensure it is up to date it is recommended that
a Network wide Resync should be performed.
Retrieving information from OMC laurel
Output in /tmp/dri19990505161811
68P02901W19-S
10-13
Oct 2009
dri_status
Output
OMC: laurel
DRI REPORT 1999/05/05 16:18:11
______________________________________
BSC
SITE
DRIGROUP ADMIN
OP
TRANSMISSION
RDNINSTANCE
RDNINSTANCE
DRI
STATE
STATE
TIME
BSS_100
BSS_100:SITE-4:
0 0
1999-02-10
10:46:05.00000
1600d2_test
1600d2_test:SITE-1: 0
0 0
1998-12-16
17:14:12.00000
Sample output when region option is used:

OMC: somc153
___________________
Region:region1
______________________
DRI REPORT 2005/06/17 11:32:17
_____________________________
BSC
SITE
BSS1009 BSS1009:
DRI
DRIGROUP ADMIN
OP
TRANSMISSION
RDN
INSTANCE
RDN
STATE
INSTANCE
STATE
TIME
2005-06-16
SITE-75:
BSS1018 BSS1018:
12:29:54.00000
0
SITE-10:
BSS1018 BSS1018:
17:22:05.00000
0
SITE-10:
BSS1018 BSS1018:
SITE-11:
10-14
2005-05-13
17:22:04.00000
SITE-11:
BSS1018 BSS1018:
2005-05-13
17:22:05.00000
SITE-10:
BSS1018 BSS1018:
2005-05-13
2005-05-13
17:22:06.00000
2005-05-13 1
7:22:06.00000
68P02901W19-S
Oct 2009
rtf_status
rtf_status
This utility enables the user to generate a list of the RTFs which are OOS on a single OMC
only. The user can display the output on their terminal and save the file to /tmp or to a user
defined directory.
The user can generate a report for individual OMCs.
Usage
rtf_status [ -c directory]
The option available is:
-c directory
Name of the directory where the output is to be stored. If -c is not

used, the default directory is /tmp.
NOTE
The rtf_status utility uses batch_rlogin. Only users with BSS Remote Login privileges
should have access to this utility.
Input
laurel:omcadmin > rtf_status c /home/omcadmin
Output
This utility generates RTF Device Status information, using batch_rlogin scripts.
It is only run on a single OMC.
Check the following RTFs in bss-1017
Check the following RTFs in bss-1016
RTF 0 0 at 2
RTF 0 1 at 2
RTF 0 2 at 2
RTF 0 3 at 2
RTF 0 4 at 2
RTF 0 5 at 2
RTF 1 1 at 4
68P02901W19-S
10-15
Oct 2009
site_outage
site_outage
This utility enables the user to generate a list of SITE Outage times based on Last RSL alarms in
the event logs and thus calculate the amount of time that the site was Out Of Service.
The user can generate a report for a single OMC or all OMCs in the Network. The default is All.
Usage
site_outage [ -a termAddress ] [-b OMCname ]
StartTime EndDate EndTime
[ -c directory ]
[ -defl] StartDate
The options available are:

-a termAddress
termAddress is the IP address of the terminal, site_outage run from.

This option is used to display the report to the user.
-b OMCname
OMCname is an OMC. Produces a report for OMCname. If -b is not

used, the default is the OMCs in omc.lst.
-c directory
Name of the directory where the output is to be stored.

If -c is not used, the default directory is /tmp.
-d
Produces a detailed report showing: Site, Start Date, Start Time, End
Date, End Time and Outage Time.
-e
Produces a summarized report showing: Site, Outage Time, Number of

Matched Outages, % OOS Duration Per Period, Alarms Unmatched and
Clears Unmatched.
-f
Prompts the user to enter the IP address of the terminal, site_outage

is being run from. Even if the -a option has been used, the input from
-f takes preference.
-l
Produces a list of OMCs in the network from which the user must
select one. Even if the -b option has been used, the input from -l take
preference.
If neither -d nor -e is used, then both detailed and summarized report is generated.
StartDate and EndDate
StartDate and EndDate should be entered in the format yyyymmdd.
StartTime and EndTime should be entered in the format HHMMSS.
If no date or time is entered, the default will be the previous 24 hours.
NOTE
Unmatched Critical and Clear Alarms can distort the data. The occurrence of these
alarms is identified by the utility.
10-16
68P02901W19-S
Oct 2009
site_outage
Input
laurel:omcadmin > site_outage
Please Wait .....
Retrieving information from OMC laurel
The reports are being generated
Please Wait .....
Close Reports or Control C to exit.
Detailed report is in /tmp/SiteDetail.21619
Summary report is in /tmp/SiteSummary.21619
NOTE
To view all data in the report, maximize the output window.
Output
OMC laurel
Detailed Site Outage Report
____________________________
Time Period 04/05/1999 16:24:13 - 05/05/1999 16:24:13
Site
Start
Start
End
End
Outage Time
Date
Time
Date
Time
(HH:MM:SS)
BSS_1016(BSS_1016:SITE-2:): 5/05/1999
12:39:26 5/05/1999 12:39:54
BSS_1016(BSS_1016:SITE-2:): Not Found
5/05/1999 12:26:51
0:0:28
OMC laurel
Summarised Site Outage Report
______________________________
Time Period 04/05/1999 16:24:13 - 05/05/1999 16:24:13
Site
Outage Time
(HH:MM:SS)
BSS_1016
0:0:28
(BSS_1016:SITE-2:)
68P02901W19-S
No. Of
Matched
%OOS
Duration
Outages
Per Period
0.3
Alarms
Clears
Unmatched
Unmatched
10-17
Oct 2009
add_nei
add_nei
This utility enables the user to add neighbors both ways, regardless of the OMC on which
they reside.
Only the omcadmin or Configuration Management experts should have the ability to use this
utility.
NOTE
The add_nei utility uses batch_rlogin. Only the users with BSS Remote Login
privileges should have access to this utility.
Template files
This utility uses pre-defined files containing default values. The user should ensure that these
values are appropriate to the network, and make the updates appropriately. Where necessary,
the OMC administrator can modify these files.
The template files for the neighbors can be found in:
/usr/omc/current/sbin/udata/templates
Input
laurel:omcadmin > add_nei

add_nei will add neighbors, both ways, using batch_rlogin. It uses neighbour
templates stored in /usr/omc/current/sbin/udata/templates
The add_nei utility uses BSIC and BCCH frequency plans which are taken from
the MIB databases of all the OMCs
To get a new RF/BSIC plan:
enter 'new' or 'N'
To use the old RF/BSIC plans:
press Return
To quit:
enter 'q'
Do you want to use default Country Code [001] and Network Code [01] for
Source Cell y/n
y
Do you want to use default Country Code [001] and Network Code [01] for
Neighbor Cell y/n ?
y
10-18
To input Source Cell:
enter 'LAC-CI'
(for example:
242-53512)
If sources now input,
enter 'p'
(proceed with add_nei)
To quit:
enter 'q'
68P02901W19-S
Oct 2009
del_nei
Output
The result files can be found in the neigh directory and the batch files are in the sub-directories
beneath this:
/usr/omc/current/sbin/udata/neigh
del_nei
This utility enables the user to delete neighbors both ways, regardless of the OMC on which
they reside.
utility.
NOTE
The del_nei utility uses batch_rlogin. Only the users with BSS Remote Login
privileges should have access to this utility.
Input
laurel:omcadmin > del_nei

del_nei will delete neighbors, both ways, using batch_rlogin.
del_nei uses BSIC and BCCH frequency plans which are taken
from the MIB databases of all the OMCs
To get a new RF/BSIC plan:
enter new or N
To use the old RF/BSIC plans:
press Return
To quit:
enter q
Now collecting ARFCNs and BSICs for RFPlan...

laurel...
somc12...
To input Source Cell:
enter LAC-CI
(for example:
If sources now input,
enter p
(proceed with del_nei)
To quit:
enter q
68P02901W19-S
242-53512)
10-19
Oct 2009
nei_sync
Output
The result files can be found in the neigh directory and the batch files are in the sub-directories
beneath this:
/usr/omc/current/sbin/udata/neigh
nei_sync
This utility enables the user to find and correct discrepancies in the BSIC and BCCH of
neighbors.
utility.
NOTE
The nei_sync utility requires the use of cmutil. Only the users with knowledge of the
cmutil operation should use this utility.
Input
laurel:omcadmin > nei_sync
Output
This script is to find out and correct
the discrepancies in the bsic and
bcch of neighbours.
_______________________________
Generating the discrepancies in the OMC
Completed.
The full list of Neighbour discrepancies is in
/usr/omc/current/sbin/udata/neierr.txt
Any discrepancies to be resolved are in /usr/omc/current/sbin/udata/cmnei.in
Enter Control C to Quit window.
10-20
68P02901W19-S
Oct 2009
proxy_sync
proxy_sync
This utility enables the user to generate a list of required Proxy Cells and add them to an
OMC. Only the omcadmin or Configuration Management experts should have the ability to
use this utility.
NOTE
The proxy_sync utility requires the use of cmutil. Only the users with knowledge of
the cmutil operation should use this utility.
Input
laurel:omcadmin > proxy_sync
Output
This script is for Proxy Cell generation and addition to OMC
_____________________________________________________
Generating the Cells in the OMC
Generating the Cells from the neighbor list which are outside this OMC
Generating Network Wide Frequency plan
Now collecting ARFCNs for RFPlan...
laurel...
somc18..
Now collecting BSICs...
laurel...
somc18...
Processing - Generating BCCH and BSIC of proxies ...
Putting the proxycells in cmutil format...
Output in /usr/omc/current/sbin/udata/proxygen.op
Number of proxycells for this OMC = 0
Running cmutil to add the new proxies - ignore the error messages
which say object already existing
Running to cmutil to update the values of BCCH and BSIC
Addition and Updates finished successfully
Enter Control C to Quit window.
reparent_site
This utility enables the user to reparent a site from BSS to BSS and across OMCs.
68P02901W19-S
10-21
Oct 2009
reparent_site
utility.
Input
laurel:omcadmin > reparent_site BSS1017:SITE-8: BSS_1016
Performing the necessary checks for reparent_site
Checking that the links are disconnected.
Getting the list of OMCs on the network.
Locating OMC on which BSS_1016 resides.
Locating the BSS on which BSS1017:SITE-8: resides.
Enter the name that the site will be given on the new BSS
Press Return if you do not want the name to change.
<RETURN>
The site name is now BSS1017:SITE-8:
Enter the LAC that the site will be given on the new BSS.
Press Return if you do not want the LAC to change.
<RETURN>
The LAC is unchanged
The current RDN instance of BSS1017:SITE-8: = 8
8 is unused on BSS_1016
Enter the RDN instance that the site will be given on the new BSS.
Press Return if you do not want the RDN to change.
<RETURN>
The RDN instance is unchanged
Gathering a list of cells which will be created as proxy cells.
Extracting the Site information
Deleting site BSS1017:SITE-8:
Verifying Network-entities/containment.
Retrieving Network-entities/containment. . . .
Deleting Network-entities/containment. . .
Deleting a SITE
Creating input file BSS1017:SITE-8:.inp
Hierarchical extraction of BSS1017:SITE-8: in progress ...
Hierarchical extraction of BSS1017:SITE-8: completed
The deletion will fail if any of the forms for the objects are open for edit.
Please ensure this is not the case and will not be at any time while this
script is running.
Type Y to proceed, anything else will abort operation:
Y
10-22
68P02901W19-S
Oct 2009
ne_counter
ne_counter
This utility enables the user to get a count of the NEs and TCHs in their network based on the
contents of the CM MIB on a per OMC basis.
Usage: ne_counter [ -r regionName ]
Input
laurel:omcadmin > ne_counter
Output
Network Entity Counter for laurel
__________________________________
Number of NEs:
BSSs:
20
RXCDRs:
34
54
Number of Sites:
BSCs:
BSC\BTS:
19
BTSs:
520
573
Number of Cells:
1242
Number of RTFs:
2123
BCCH:
1242
Non-BCCH: 881
Number of DRIs:
2125
Number of Neighbours:
15011
Number of TCH(Model):
9936
Number of TCH(Total):
16984
Number of TCH(Speech):
15742
Enter Control C to quit
68P02901W19-S
10-23
Oct 2009
ne_counter
Output when region option used:

Network Entity Counter for laurel Region:
Region1
___________________________________________________
Number of NEs: 54
BSSs: 20
RXCDRs: 34
Number of Sites: 573
BSCs: 0
BSC\BTS: 19
BTSs: 520
Number of Cells: 1242
Number of RTFs: 2123
BCCH: 1242
Non-BCCH: 881
Number of DRIs: 2125
Number of Neighbours: 15011
Number of TCH(Model): 9936
Number of TCH(Total): 16984
10-24
68P02901W19-S
Oct 2009
Utility execution
Utility execution
Overview
This section describes different execution mechanisms to invoke the utilities from the OMC
environment and the procedures required to implement them. The following table lists the
recommended execution mechanisms.
Table 10-2
OMC utilities: recommended execution mechanisms
Utility
Recommended execution
finder
Command line/Tools/CDE
net_reports
dri_status
Command line/Tools/CDE/cron
rtf_status
site_outage
add_nei
Command line/CDE
del_nei
Command line/CDE
nei_sync
Command line/CDE
proxy_sync
Command line/CDE
reparent_site
Command line
ne_counter
These utilities can be invoked on a Client machine when remotely logged in to the OMC System
Processor.
Command line
CAUTION
Do not execute a CTRLC while any of the scripts are executing; allow all the scripts to
complete execution once they are started.
The utilities are contained in /usr/omc/current/sbin and can be invoked from the command
line by typing the utilitys name and the appropriate options. If /usr/omc/current/sbin is in
the users PATH, only the utility name is required; otherwise the full path should be given, for
example:
dri_status r Region1
or
68P02901W19-S
10-25
Oct 2009
cron and at
/usr/omc/current/sbin/dri_status r Region1
cron and at
The utilities can be executed using cron and/or at.
A sample cron file (utilities_cron) is provided. This file is located in:
/usr/omc/current/sbin/udata
CDE menu
To add a utility to the CDE menu, execute the following commands as omcadmin:
cd /usr/omc/current/env
vi .dtwmrc
Add the following to the Right Menu Description:
no-label
f.separator
DRI Status
f.exec /usr/dt/bin/dtterm -title Dri_Status-e

rsh omc_splat /usr/omc/current/sbin/dri_status -f
no-label
f.separator
Network Reports
f.exec /usr/dt/bin/dtterm -title Network_Reports -e

rsh omc_splat /usr/omc/current/sbin/net_reports
Alternatively, create a separate sub-menu list:

no-label
f.separator
OMC General Utilities
f.menu OMC_GEN_utils
no-label
f.separator
###
#
# Utilities sub-menu description
#
###
Menu OMC_GEN_utils
{
DRI Status
f.exec /usr/dt/bin/dtterm -title
DRI_Status -e rsh omc_splat /usr/omc/current/sbin/dri_status -f

SITE Status
f.exec /usr/dt/bin/dtterm -title
SITE_Outage -e rsh omc_splat /usr/omc/current/sbin/site_outage

}
10-26
68P02901W19-S
Oct 2009
cleanMib
cleanMib
Introduction
The cleanMib script replaces the MIBCleanup script. The cleanMib script searches for
corruptions in the MIB database and fixes them.
The cleanMib detects or repairs the following types of database corruption:
Orphan corruptions objects with invalid or missing parent objects.
Relationship corruptions incorrect, duplicate or missing relationships.
Invalid DN corruptions objects with NULL DN strings.
These types of corruptions to prevent the success of some MIB actions, such as HierDelete and
cmutil, and also cause the cmMib process to exit.
NOTE
This script should be run on machines during periods when there is no MIB activity.
The cleanMib script should be run in report mode first, on a stable MIB. The
inconsistencies, if found, are written to the omcaudit logfile or usraudit logfile,
depending on the setting of the environment variable LOG_TO_USRAUDIT.
The inconsistencies are also logged to a cleanMib logfile in /usr/omc/logs.
The inconsistency report can be examined and if any inconsistencies are found, the script
can be run in cleanup mode.
If orphans are detected, then it is recommended that HierDelete is executed on the affected site
after the cleanMib script has been run in cleanup mode, and then to re-audit in the affected site.
Running cleanMib
The script may be executed in two different modes:
To execute in Report Mode, use the r parameter.
To execute in Cleanup Mode, use the c parameter.
Open an xterm from the Single Platform Processor. Type the following commands in the xterm:
cleanMib r
or
cleanMib c
68P02901W19-S
Oct 2009
10-27
Running cleanMib
10-28
68P02901W19-S
Oct 2009
Chapter
11
Network Information Services (NIS)
68P02901W19-S
Oct 2009
11-1
Overview
Overview
NOTE
NIS is configured as the default naming service in the OMC-R environment. However,
it is possible to configure an alternative naming service on the OMC-R. Motorola does
not provide documentation or support for alternative naming services on the OMC-R.
Network Information Services (NIS) is a distributed naming service from Solaris, the purpose of
which is to ease the administration of computing environments comprising different machines.
The use of NIS allows a task, that previously would have been performed on the network, to be
performed on the central administration system.
The NIS feature uses the concept of a master server and optional replicated server(s) and client
machines. However, in the OMC-R environment, only a master server (the system processor)
and clients are used.
11-2
NIS normal operation on page 11-3.
NIS files and utilities on page 11-5.
Changing user/group/host information on page 11-8.
68P02901W19-S
Oct 2009
NIS normal operation
NIS normal operation
This section contains a glossary of the various terms used within the normal NIS environment.
Map
All maps except /etc/mail/aliases are stored in /var/yp/<domainname> on the system
processor. The file /etc/mail/aliases must always be stored in /etc/mail (/etc/aliases is a hard
link to /etc/mail/aliases).
Domain
The NIS domain is a collection of systems using the same NIS database. All systems share a
common set of maps.
To participate in NIS, a system must belong to the NIS domain. Each domain has a unique name,
for example, the default OMC-R domain is called omcadmin.
NOTE
If more than one OMC-R system is connected to the same LAN, each OMC-R must
have a unique NIS domain name.
Servers and clients

Because the network is database-oriented, system machines are arranged in two categories:
servers and clients.
The NIS server is a machine storing a set of maps which are available to network hosts such
as clients. A server can also act as a client.
The NIS client runs processes that request data from the maps on the NIS servers. A client can
also act as a server.
68P02901W19-S
11-3
Oct 2009
Masters and slaves
Masters and slaves

A copy of the database exists on every server and the servers are designated as master or slaves.
A master server is the machine where the database was originally created and is maintained.
A slave holds a copy of this database and serves as a backup for the database. The terms master
and slaves are however, relative because a server can be a master for one system database and
a slave for another system database.
Propagation
Propagation is the process by which a master server updates the data in slave servers with
new information entered in its own database. Propagation therefore ensures consistency of
database information.
11-4
68P02901W19-S
Oct 2009
NIS files and utilities
NIS files and utilities
The NIS service is composed of the following elements, some of which are part of the Solaris
distribution:
Daemons
Daemons are important to the functionality of the operating system. Daemons are programs
that run in the background to manage certain system functions.
Here are some of the NIS daemons:
ypserv
The ypserv is a daemon typically activated at system startup. This daemon only runs on
NIS server machines that have a complete NIS database. The prime function of the ypserv
daemon is to look up maps in its local database of maps.
ypbind
The ypbind is a daemon service typically activated at system startup. This daemon
remembers all information that lets all NIS client processes on a node communicate with
some NIS server process. The daemon must run on every machine that has the NIS client
process.
NOTE
Binding is a process that remembers the address at which the server daemon
was listening for requests. Binding creates a relationship between a client and a
server such that the client will always go to that address for information and
determines whether a relationship is bound or unbound.
ypxfrd
The ypxfrd daemon is a service that transfers complete NIS maps efficiently. This daemon
should be run on a master server.
rpc.yppasswd
The rpc.yppasswd daemon is a service that modifies the NIS password map. The daemon
changes the network password associated with a particular user in the NIS database.
68P02901W19-S
11-5
Oct 2009
Utilities
Utilities
The following common utilities are used with NIS:
ypcat
The ypcat command prints values in the NIS name service map specified by the main
map name.
ypwhich
The ypwhich command returns the name of the server, that supplies the NIS name service
to the NIS client or that is the master for a map.
yppoll
The yppoll command returns the order number of a ypserv process and the master server
for the named map.
ypmatch
The ypmatch command prints the values associated with one or more keys from the NIS
name services map specified by the map name.
Auxiliary utilities
yppush
The yppush utility copies a new version of the NIS map from a master NIS server to the
slave NIS servers. The command is run only on the master server by the Make file in
/var/yp, after the master databases are changed.
ypset
The ypset command points the daemon ypbind to a particular server.
ypxfr
The ypxfr command moves the NIS map in the default domain from a master server to
a slave server.
makedbm
The makedbm command creates DBM files for the NIS map.
11-6
68P02901W19-S
Oct 2009
Affected files
Affected files
NIS affects the following files:
/etc/passwd
/etc/group
/etc/inet/hosts (/etc/hosts)
/etc/aliases
/etc/bootparams
/etc/automaster
/etc/auto.home
68P02901W19-S
11-7
Oct 2009
Changing user/group/host information
Changing user/group/host information
Recommended method
The recommended method of changing user or, group information is using the OMC_Sync
script to invoke the user tool utility. Refer to the set of procedures in the section Administering
group accounts with usertool on page 2-8.
NOTE
This method is highly recommended because it updates the NIS automatically, if
configured.
Changing host name
NOTE
A host name must be at least two characters: it can contain letters, digits and minus
signs (-). Letters must be lower case. Illegal characters are: !$%^&*(){}~@?>:<|
. >!].
Adding a new user to the NIS domain
NOTE
Changes should only be made on the system processor through the OMC-R admin icon
as user root because this is the master NIS server. If a user is not being recognized
on a machine, verify that the user exists in the /etc/passwd map.
If there is no entry for the user in the /etc/passwd map, one must be created in
/etc/passwd and /etc/shadow files. The NIS must then be updated to allow the
changes to be propagated throughout the network.
11-8
68P02901W19-S
Oct 2009
Procedure 11-1
Adding a new user to the NIS domain from the command line
Use the useradd utility to add the user entry to the /etc/passwd and
/etc/shadow files. Enter the following command:
useradd usrID
NOTE
The useradd utility only adds a user to the local system. It
cannot be used to change information supplied by the NIS
name service.
3
Update the password map by entering the following commands:

cd /var/yp
/usr/ccs/bin/make passwd
Execute the following command to set the NIS password:

yppasswd <newusername>
where <newusername> is passed as a parameter.
NOTE
The length of the username parameter is restricted to eight
characters.

Use the following procedure to add a new group to the NIS domain from the command line.
NOTE
Changes should only be made on the system processor through the OMC-R admin icon
as user root because this is the master NIS server. If a group is not being recognized
on a machine, verify that the group exists in the /etc/group/etc/passwd map.
If there is no entry for the user in the /etc/group/etc/passwd map, one must be
created in the /etc/group file. The NIS must then be updated to allow the changes to
be propagated throughout the network.
Procedure 11-2
Adding a new group to the NIS domain from the command line
Login to the system as root.
Use the groupadd utility to add the user entry to the /etc/passwd.
groupadd grpID
Continued
68P02901W19-S
11-9
Oct 2009
nsswitch.conf
Procedure 11-2
(Continued)
Adding a new group to the NIS domain from the command line
NOTE
The groupadd utility only adds a group to the local system,
it cannot be used to change information supplied by the NIS
name service.
3
Update the group map by entering the following commands:

cd /var/yp
/usr/ccs/bin/make group
nsswitch.conf
The nsswitch.conf file is a configuration file for the name service switch. The file controls
whether the system looks at NIS or files.
The template nsswitch files are /etc/nsswitch.nis and /etc/nsswitch.files. In its basic format,
the file contains two columns. The first column contains the name of the map. The second
column contains the method. For example, if the file had the following entries the system looks
for host information through NIS, and network information through the local file.
hosts:nis.
networks:files.
NIS server checks

Check that the ypserv daemon is running on the NIS server by executing the following
command, as user root on the NIS server:
ps -elf | grep ypserv
If the daemon is running, output similar to the following text (all on one line) is displayed:
8 S
root
151
1 0 41 20 60634ce0
220 6072d5de Jul 20 ? 14;30/usr/lib
/netsvc/yp/ypserv
If the daemon is not running, enter the following command as user root to start the daemon:
/usr/lib/netsvc/yp/ypserv
The client must have a correct entry in its own /etc/hosts file to be able to locate the NIS server
or centralised information. If this is not the case and the nsswitch.conf file is set to files, the
ypcat command displays the following error:
RPC failure: RPC failure on yp operation
Check the clients /etc/defaultdomain file and make sure that the domain name is correct.
11-10
68P02901W19-S
Oct 2009
Updating the NIS maps manually
NOTE
The domain name is generally set to omcadmin.
Check the /var/yp/binding/domainname/ypservers file on the client and make sure that it has
entries for the master and any replicated servers.

Use the following procedure to update NIS files manually:
Procedure 11-3
Edit the file (for example, the hosts file to add a new host).
Execute the following commands to propagate the changes throughout

the network:
cd/var/yp
/usr/ccs/bin/make mapname
NOTE
NIS is updated automatically when the OMC-R_Admin utility
is used to add, modify or delete users, groups or hosts.
NIS troubleshooting commands

The following commands can be used for troubleshooting purposes.
Commands
ypcat mapname
This command gives a list of all the values

in a map.
ypcat -k mapname
This command gives a list of all the keys

and values in a map.
ypcat -x
This command gives a list of all the map

nicknames.
ypwhich -m
This command gives a list of all the

available maps and their masters.
ypwhich -m mapname
This command lists the master server for a

particular map.
ypmatch fkey mapname
This command matches a key with an entry

in a map.
ypcat map_or_alias_name
This command shows the contents of the

NIS files.
68P02901W19-S
Oct 2009
Description
11-11
NIS troubleshooting commands
11-12
68P02901W19-S
Oct 2009
Chapter
12
Backup Server Installation and Configuration
68P02901W19-S
Oct 2009
12-1
Introduction to StorEdge Enterprise Backup
Introduction to StorEdge Enterprise Backup
StorEdge Enterprise Backup supports the backing up and restoring of UNIX file systems on
any processor within the OMC-R system. It is assumed that the appropriate license is obtained.
It also supports the Informix utility, onbar, and in the backup and restore of the Informix
databases. Refer to Installation and Configuration: OMC-R Clean Install (68P02901W47) for
further details. There are three main interactive utilities in StorEdge Enterprise Backup.
The Networker GUI: This java application is accessed using the mozilla web browser on
the OMC-R.
nwbackup, for backing up complete UNIX file systems or parts. In particular, the utility is used
for marking the file systems required to be backed up and then performing the actual file system
backup to the specified labelled tape. It can be invoked manually or can be scheduled. The use
of nwbackup is not recommended for making regular backups.
nwrecover, for restoring complete UNIX file systems or parts. In particular, the utility is used
for restoring the file systems that were initially backed up on tape media using the nwbackup
utility or by a scheduled backup.
The above utilities are normally used in an interactive environment. However, they can be
invoked from the UNIX command line. This method is not used except in a disaster recovery
situation. The StorEdge Enterprise Backup is configured, within the OMC-R environment, as
one server module and several client modules:
server module is the main part of the program, installed on the single platform processor.
It controls the physical media devices, internal processes of the backup or restore and
communicates with the client modules.
client module is installed on each processor within the OMC-R system including the
single platform processor. The client module informs the server module to perform the
backup in case of manual backups.
The backup and restore procedures are configured to be performed from the server (single
platform processor). However, the procedures can be configured so that backup or restore can
be performed from other processors, which have access to local tape drives.
Perform complete file system backups after each major installation or reconfiguration of the
OMC-R such as disk repartitioning. These types of file system backup are normally performed
in single user mode to ensure resilience and reliability. Create two tape sets of the OMC-R
backup, with one complete set stored offsite.
To avoid the OMC-R being shut down (to single user mode) during normal operational activity,
the backup process can be performed in multi-user mode. However, in multi-user mode, the
file systems can be in a changing state and the backup tapes may not reflect the file systems
accurately. Operator intervention may be required to change the tapes during the backup
or restore.
12-2
68P02901W19-S
Oct 2009
StorEdge Enterprise features
StorEdge Enterprise features

The StorEdge Enterprise Backup provides the following features:
Device configuration
The backup device is usually configured during the installation of the software. However, it
is recommended to check that the device has been installed correctly.
Schedule configuration
The schedule configuration is an important part of the backup configuration. It gives
the details of the complete and incremental backups performed and also when these
are overridden.
Group configuration
Group configuration specifies when a backup is running and has control of clients within
the group. New groups can be set up although the default group setup is sufficient. The
clients can be configured to use the groups.
Client configuration
A client is the host which is required to be backed up. This also includes the server, as it
needs to be a client to perform the backups of itself.
Mounting the tape backup media
Manual backups
Restoring files
Recovering the OMC-R system after a disaster
It is possible that one of the disks on the OMC-R system fails at some point. Although this rarely
happens, the hard disk is a focal point of failure because of the constantly moving parts.
If there is data on the disk which is easily recoverable, it can be copied onto the new disk. If the
data on that disk is not recoverable, there are several methods of recovering the system, for
example:
Restoring a non system disk
Restoring the backup indexes
Restoring the system disk
NOTE
The term Backup Server refers to the Single Platform Processor server.
68P02901W19-S
12-3
Oct 2009
Software Installation
The StorEdge Enterprise Backup software is delivered on the GSR9 1.9.0.0.X Additional OMC
Software DVDROM. To install the software, perform the following tasks as user root:
Procedure 12-1
Installing the Backup Server software

{34618}
cp rp /cdrom/cdrom0/suninstall/backup /var/install
cp /cdrom/cdrom0/suninstall/lib/backup.lib /var/install/lib
cp /cdrom/cdrom0/suninstall/data/package_list \
/var/install/data
cp /var/install/backup/tape-mgr /var/install/bin
The software installation program to execute is

/var/install/bin/tpp_installer
Invoking the StorEdge Enterprise Backup utilities

When backing up the system processor or a GUI processor, the Administration GUI utility
is always called from the system processor.
When restoring the system processor, nwrecover is always called from the system processor.
When restoring the GUI processor, nwrecover is always called from the GUI processor.
Software Licenses
EBS Network Edition License: EBS Network Edition License file is needed for the
backups of the GSM OMC-R Server. License file is supplied by Motorola and can be installed
on the GSM OMC-R.
Legato Informix Module License (For each client): A Legato Informix Module license
is needed for Backup of the Informix Databases on the Server. The Legato Informix Module
license is supplied by Motorola and can be installed on the Single Platform Processor.
12-4
68P02901W19-S
Oct 2009
Backup Server Configuration
Backup Server Configuration

Use the following procedure to configure the Backup Server:
Procedure 12-2
Configuring Backup Server
{34618}
1
Insert a blank tape into the tape drive.
Execute the following command as user root:

/var/install/backup/setup_backup_server.sh
Select Option 1.
Enter Local Tape Device (Q to Quit): [/dev/rmt/0c]
Press Enter to select default or enter the path to device (unless another tape
drive has been connected, the default is valid).
Select correct Device Media Type for your tape drive.
Enter a name to use for the tape and it will be labelled and mounted.
To Do you wish to configure the licensing information , you can enter

n (and the software will work for 30 days) or enter y if you have purchased a
license code.
If the Bootstrap is already configured, then do not reconfigure it. Otherwise

follow Procedure 12-4to configure it.
The script returns to the Main Menu, select Quit.
Configuring Sun StorEdge Enterprise Backup Server Licenses

Follow Procedure 12-3, to configure the Sun StorEdge Enterprise Backup Server Licenses:
NOTE
EBS Network Edition for Solaris and EBS Module for Informix, Unix Client are
required on the Backup Server.
68P02901W19-S
12-5
Oct 2009
Configuring Bootstrap Notifications
Procedure 12-3
1
Sun StorEdge Enterprise Backup Server License Configuration
Output like the following is displayed:

** LICENSE CONFIGURATION
Do you wish to configure the licensing information now? (default:y):Y
Select y to configure the license for the Sun StorEdge Enterprise Backup Server
Software. Output like the following is displayed:
Enter enabler code for license:
Enter the Enabler Code. A message is displayed, requesting confirmation of the

enabler code. Enter Yes (case-sensitive) to accept the Enabler Code.
If the Enabler code is invalid/incorrect, an ERROR message is followed
by the message given below:
Do you wish to enter another license enabler code (y|n) (default:n)?
If another Enabler Code is to be entered, enter y, otherwise enter n to continue

to the Bootstrap Notification Configuration.
Configuring Bootstrap Notifications

To configure the Bootstrap notifications, follow these steps:
Procedure 12-4
1
Bootstrap Notification Configuration
Bootstrap information will then need to be configured. Output like the

following is displayed:
** BOOTSTRAP CONFIGURATION
Bootstrap Information is required to allow
for a fast recovery.
Select Delivery Option:
1. Bootstrap via e-mail
2. Bootstrap copied to local file
Enter option:
If Option 1 is selected, refer Configuring Bootstrap Notification through

E-mail on page 12-6.
If Option 2 is selected, refer Configuring Bootstrap Notification to local
file on page 12-7.
Configuring Bootstrap Notification through E-mail

To configure the Bootstrap notifications through e-mail, follow these steps:
12-6
68P02901W19-S
Oct 2009
Configuring Bootstrap Notification to local file
NOTE
For email notifications to operate, a mailhost must be configured in /etc/hosts or DBS
on the Backup Server.
Procedure 12-5
1
Bootstrap Notification through E-mail Configuration
Select Option 1 to automatically configure the Bootstrap Notifications to be

sent through e-mail. A message like the following is displayed:
Option "1: Bootstrap via e-mail" selected
Enter e-mail address:
Enter the E-mail address. A prompt requesting a confirmation on the E-mail

address entered is displayed.
Enter Yes (case-sensitive) to continue.
Bootstrap notification is setup.

To configure the Bootstrap notifications to local file, follow these steps:
CAUTION
It is important that a copy of the bootstrap notification file is available to allow for
a fast recovery. Data recovery takes considerably long time if this information is
unavailable. The recommendations are to:
68P02901W19-S
Print a copy of the file and place it in the system folder.
Copy the file to a remote location in case a restore needs to take place.
12-7
Oct 2009
Procedure 12-6
Bootstrap Notification to local file Configuration
Select Option 2 to automatically configure Bootstrap Notifications to be

stored locally in a file. A message similar to the following is displayed:
Option "2.
Bootstrap copied to local file" selected
Enter file (absolute path):

2
Enter absolute path to the file to be created containing the bootstrap

information (for example, /bootstrap/bootstrap.txt). A prompt requesting
a confirmation on the file entered is displayed.
Enter Yes (case-sensitive) to continue.
Bootstrap notification will be setup.
Select option 5 to quit the setup program.

1. Initialize Backup Server
2. Add Backup Client
3. Update Backup Client
4. Delete Backup Client
5. Quit
Enter Option:
5
12-8
68P02901W19-S
Oct 2009
Setting up the backup server software
Setting up the backup server software

Follow Procedure 12-7 to configure Informix to use the Backup Server.
Procedure 12-7
Configuring Informix Backup to use the Backup Server

/usr/omc/sbin/Configure_Informix

svcadm disable omc
pkill nameserver
/usr/omc/sbin/configure_solstice
NOTE
This step causes an OMC outage.
3
Select y to continue.
Select y to back up logical logs. Logical log backups are necessary to

recover recent database updates. If there is no need to restore the database
logical logs, select n.
The script generates an output like the following:

WARNING : Running this script will result in the
PM and CM Databases being stopped and started
Do you wish to continue ? [y n] y
Will you be storing Logical Logs. Bear in mind that storing
Logical Logs may require additional tapes and that the
database could fail if tapes are not changed when the Informix
Engine requests them to be changed.
Will you be storing Logical Logs ? [y n] y
Re-Starting the PM Database Instance
Re-Starting the CM Database Instance
Creating /usr/informix/etc/ixbar.2 for PM Database Instance
Sun Microsystems Inc.
SunOS 5.10
Generic January 2005
logout
Creating /usr/informix/etc/ixbar.1 for CM Database Instance
Sun Microsystems Inc.
SunOS 5.10
Generic January 2005
logout
6
68P02901W19-S

svcadm enable omc
12-9
Oct 2009
Completing backup server setup

Follow Procedure 12-8 to set up backup clients.
Procedure 12-8

Select option 2 to add a backup client. There are several backup client
types, such as, Informix_CM, Informix_PM, Informix_IX1, and Informix_IX2.
Enter the hostname of the system to be backed up. For the SPLAT, create
each of the following client types by repeatedly selecting option 2 to add a
client. Select the option number corresponding to the client to be created.
2. Informix_CM
3. Informix_PM
4. Informix_IX1
5. Informix_IX2
If there is a GUI server, enter the name of the GUI server and select
GUI_SERVER as the server type.
Once all the backup clients have been created, select option 5 to exit the
script.
NOTE
Once a client is registered with the Backup Server, it is automatically setup to backup
to the Backup Server at a time designated by that group. The times are as follows:
Default group runs at 01:30 Daily.
Informix ixbar files groups run at 03:40 Daily.
After the backup server is configured, the default group's start time is 3:33, and
it is disabled.
Backups of Informix databases are controlled by a crontab entry. The crontab entries
are automatically created by the /usr/omc/sbin/configure_solstice script.
Enabling or Disabling a Group Backup

Once the backup clients are added, the backup groups are enabled or disabled according to the
default settings in the configuration file /var/install/backup/backup_set.cfg.
Follow Procedure 12-9 to enable or disable a Group Backup client.
NOTE
Ensure that the backup client belonging to the backup group exists, before enabling
or disabling a backup client.
12-10
68P02901W19-S
Oct 2009
Procedure 12-9
Deleting a Group Backup client
Enabling or Disabling a Group Backup client

Select option 3 to update a backup client.
Select the hostname of the system from the machine list.
Select the option number of the backup client. The following message is
displayed:
Do you want to Enable (Press e) or Disable (Press d)
the group backup for Informix_IX1?
To enable the group, enter e.
To disable the group, enter d.
Repeat step 2 to step 4 to update all the backup clients.
NOTE
The group backup for the clients Informix_CM and Informix_PM is
disabled by default.
Selecting the backup client as Informix_CM or Informix_PM, displays
the following message:
There is a cron job set defaultly for INFORMIX_CM
& INFORMIX_PM backup.
So NSR group INFORMIX_CM or INFORMIX_PM is not
permitted to enable auto start!
Quit updating...
6
Select option 5 to exit the script.
Deleting a Group Backup client

Follow Procedure 12-10 to delete a backup client.
NOTE
Ensure that the backup client exists, before deleting a backup client.
68P02901W19-S
12-11
Oct 2009
Manually starting a Group Backup
Procedure 12-10
Deleting a backup client

Select option 4 to delete a backup client.
Select the hostname of the system from the machine list.
Select the option number of the backup client.
Repeat step 2 to step 4 for all the backup clients to be deleted.
Select option 5 to exit the script.
Manually starting a Group Backup

Use the following procedure to initiate a manual backup of a group:
NOTE
Backups are done at a group level and not at a client level. If there are two clients in
the PM Backup group, then both will be backed up in parallel.
Procedure 12-11
Enable backups
{34618}
1

nsradmin
At the nsradmin> prompt, type visual and a GUI is displayed.
Click Select and NSR Group.
Click Next until the name of the group is the desired group (for example,
INFORMIX_IX2). (For all file systems, select Default.)
Select Edit and change autostart to Start Now.
If you want to perform an incremental backup instead of a full backup, change

the value of the option force incremental to yes.
Press Esc and select Yes to apply the changes. Once the changes have been
applied, the backup of all clients in the backup group starts.
Select Quit, to quit the GUI interface.
Type quit, to quit nsradmin. When the backup is complete, the following
message gets displayed on the screen.
May 16 05:30:26 zuk14omc11 root: Sun StorEdge(TM)

Enterprise Backup savegroup: (notice) Default completed,
Total 1 client(s), 1 Succeeded with warning(s).
Please see group completion details for more information.
12-12
68P02901W19-S
Oct 2009
Manual backup of Informix databases
Log files (Backup server)

The log files produced by the backup are located in the following directory.
Table 12-1
Log files produced by backup server

Log Type
Log File Location
Backup Server Configuration Logfiles
/var/install/logs
OMC-R Backup Server Status Logfiles
/nsr/logs
Log files (Client machines)

The log files produced by the client machines are located in the following directory.
Table 12-2
Log files produced by client machines

Log Type
Log File Location
Backup Logfiles
/usr/omc/logs/bar_mib.log
/usr/omc/logs/bar_omc.log
Backup Status Logfiles
/nsr/logs

Procedure 12-12
Full Backup of Informix databases
{34618}
1
To setup the ixbar files, execute the following commands as user Informix:
cd /usr/informix/etc
(If there are no ixbar.1 and ixbar.2 in this directory, produce them by copying
the latest version from files taken as backup, as shown in the following
commands.)
cp ixbar.1.<most recent date> ixbar.1
For example:
cp ixbar.1.2006109.122546 ixbar.1
Continued
68P02901W19-S
12-13
Oct 2009
Procedure 12-12
2
Full Backup of Informix databases (Continued)
To backup the PM database execute the following commands as user

Informix:
mib_env
onbar -b -w -L 0
onbar m
If the output matches the following line, the backup succeeded:
2009-05-07 23:17:07 13310 13308 Completed level 1 backup rootdbs
(Storage Manager copy ID: 1241709427 1241709428).
2009-05-07 23:17:07 13310
13308 Begin level 1 backup logsdbs.
2009-05-07 23:17:08 13310 13308 Completed level 1 backup logsdbs

2009-05-07 23:17:09 13310
13308 Begin level 1 backup physdbs.
2009-05-07 23:17:09 13310 13308 Completed level 1 backup physdbs

2009-05-07 23:17:09 13310
13308 Begin level 1 backup mib_db_sp1.
2009-05-07 23:17:10 13310 13308 Completed level 1 backup mib_db_sp1

2009-05-07 23:17:10 13310 13308 Archive on rootdbs, logsdbs, physdbs,
mib_db_sp1 Completed (Requested Level 1).
2009-05-07 23:17:10 13319
13317 /usr/informix/bin/onbar_d -b -l
2009-05-07 23:17:10 13310
13308 Begin backup logical log 25.
2009-05-07 23:17:10 13319 13317 (-43395) A log backup is

already running. Can't start another.
2009-05-07 23:17:10 13310
Storage Manager.
13308 Successfully connected to
2009-05-07 23:17:11 13310 13308 Completed backup logical log 25

2009-05-07 23:17:11 13325
2009-05-07 23:17:11 13325

returning 0 (0x00)
13323 /usr/informix/bin/onbar_d complete,
Continued
12-14
68P02901W19-S
Oct 2009
Procedure 12-12
3
Full Backup of Informix databases (Continued)
To backup the CM database execute the following commands as user

Informix:
omc_env
onbar -b -w -L 0
onbar -m
If the output matches the following line, the backup succeeded:
Onbar activity log file: /usr/omc/logs/bar_omc.log

2009-05-07 23:18:26 13358 13356 Completed level 1 backup omc_db_sp6
2009-05-07 23:18:26 13358
13356 Begin level 1 backup omc_db_sp7.

2009-05-07 23:18:27 13358

2009-05-07 23:18:28 13358

2009-05-07 23:18:29 13358 13356 Archive on rootdbs, omc_db_llog,
omc_db_plog, omc_db_sp1, omc_db_sp10, omc_db_sp11, omc_db_sp12,
omc_db_sp2, omc_db_sp3, omc_db_sp4, omc_db_sp5, omc_db_sp6,
omc_db_sp7, omc_db_sp8, omc_db_sp9 Completed
(Requested Level 1).
2009-05-07 23:18:29 13385
2009-05-07 23:18:29 13358
13356 Begin backup logical log 23.
2009-05-07 23:18:29 13358 13356 Successfully

connected to Storage Manager.
2009-05-07 23:18:29 13385 13383 (-43395) A log backup is
already running. Can't start another.
2009-05-07 23:18:31 13358 13356 Completed backup logical log 23
68P02901W19-S
2009-05-07 23:18:31 13391
2009-05-07 23:18:31 13391

returning 0 (0x00)
2009-05-07 23:18:31 13397
2009-05-07 23:18:31 13397

returning 0 (0x00)
Backup Informix ixbar files:

Execute the Procedure 12-11 to backup group INFORMIX_IX1.
Execute the Procedure 12-11 again to backup group INFORMIX_IX2.
12-15
Oct 2009
Backing up the GUI Server File System
Procedure 12-13
Incremental Backup of Informix databases
{34618}
1
To perform an incremental backup (that is, changes since last full backup)
of the Informix databases. Follow the Procedure 12-12. Above, replace the
occurrences of the line onbar -b -w -L 0with onbar -b -w -L 1.
Overview to backing up file systems using backup_MMI utility.
Procedure for backing up file systems using backup_MMI utility.
Overview to backing up file systems using backup_MMI utility

This section describes how to perform backups of the GUI Server UNIX file system using the
backup_MMI utility.
The backup may be performed to a local tape drive (that is attached to the GUI Server) or
remotely to the Single Platform Processor tape drive.
NOTE
Ensure there is no CD/DVD in the CD/DVD drive before performing the backup.
12-16
68P02901W19-S
Oct 2009
Procedure for backing up file systems using backup_MMI utility

Use the following procedure to perform a backup of the UNIX file systems on the GUI Server
automatically:
Procedure 12-14
Performing a backup of the UNIX file systems on the GUI Server
Log in to the GUI Server using the login id: root.
Insert a new labeled DAT tape into the appropriate processor tape drive,
ensuring that it is not write-protected.
Change to the /usr/omc/current/sbin directory by entering the following

command:
Enter the following command to run the backup_MMI utility.

./backup_MMI.
The following prompt is displayed:
Please indicate whether a local backup to the MMI/GUI Processor or
remote backup to the Single Platform Processor is required
L. Local Backup to the MMI/GUI Processor
R. Remote Backup to the Single Platform Processor
Q. Quit Utility
Enter Choice:
Enter one of the following:
L - for a local backup to the tape drive on the GUI Server.
R - for a remote backup to the tape drive on the Single Platform Processor.
The following output is displayed:

Valid Backup Tape Types
D. DAT
C. CARTRIDGE
Q. QUIT
Enter Backup Tape Type:
Enter the appropriate backup tape type: D - for DAT tape drive.

Is there a writeable DAT/Cartridge tape loaded in the Tape Drive ?
Y. YES to continue
Q. QUIT
Enter Choice:
Enter Y when the tape light has stopped flashing and is permanently lit green.
Continued
68P02901W19-S
12-17
Oct 2009
Procedure 12-14
(Continued)
7

Enter Local Tape Device (Default is /dev/rmt/0)
(Q to QUIT).
Enter the backup tape device name as /dev/rmt/0n.
In this example, the backup is being performed on a Sunblade 150 GUI Server,
to a tape drive on the Single Platform Processor.
NOTE
The order in which the file systems are backed up is important when
it comes to the restore. As shown in the Table 12-3 below.
In the example below / (root) will be Number 1, /omcgen will be Number 2,
/usr/omc will be Number 3.
Output similar to the following example is displayed.
FILESYSTEM BACKUP TO somc57 TAPE DEVICE /dev/rmt/0n
Attempting to archive the following partitions:
/
/omcgen
/usr/omc
Backing up the / filesystem
DUMP: Date of this level 0 dump: Wed Jul 06 11:39:01 2005
DUMP: Date of last level 0 dump: the epoch
DUMP: Dumping /dev/md/rdsk/d0 (sunblade3:/) to
somc57:/dev/rmt/0n.
DUMP: Mapping (Pass I) [regular files]
DUMP: Mapping (Pass II) [directories]
DUMP: Writing 32 Kilobyte records
DUMP: Estimated 5223950 blocks (2550.76MB).
DUMP: Dumping (Pass III) [directories]
DUMP: Dumping (Pass IV) [regular files]
DUMP: 42.89% done, finished in 0:13
DUMP: 5223934 blocks (2550.75MB) on 1 volume at 1937 KB/sec
DUMP: DUMP IS DONE
Backing up the /omcgen filesystem
DUMP: Dumping /dev/md/rdsk/d10 (sunblade3:/omcgen) to
somc57:/dev/rmt/0n.
DUMP: Estimated 604 blocks (302KB).
DUMP: 574 blocks (287KB) on 1 volume at 2064 KB/sec
Continued
12-18
68P02901W19-S
Oct 2009
Procedure 12-14
(Continued)
DUMP: DUMP IS DONE

Backing up the /usr/omc filesystem
DUMP: Dumping /dev/md/rdsk/d15 (sunblade3:/usr/omc) to
somc57:/dev/rmt/0n.
DUMP:
DUMP:
DUMP:
DUMP:
DUMP:
Estimated 919936 blocks (449.19MB).

Dumping (Pass III) [directories]
Dumping (Pass IV) [regular files]
919934 blocks (449.19MB) on 1 volume at 2490 KB/sec
DUMP IS DONE
Perform a confidence check on the tape(s) by entering the following command:

dd if=/dev/rmt/0n of=/dev/null bs=1024k
10
Repeat step 9, in this example two more times in order to check the complete
backup.
NOTE
The confidence check command line in step 9 must be entered once
for each partition that has been backed up. In this procedure, there
are three file systems that have been backed up, therefore it is
necessary to enter this command a total of three times.
11
If the confidence check performed in step 9 is successful, write-protect, label,

and store the tape(s). If an error is returned, replace the faulty tape and repeat
the backup procedure from step 2.
A log file is kept in /usr/omc/logs/backup_MMI.<datestamp>.
Fill out the table below with the details:
Table 12-3
Order of backing up file systems
Number
File system
1
2
3
4
68P02901W19-S
12-19
Oct 2009
Disaster Recovery
Disaster Recovery
Disaster Recovery GSM OMC-R server
CAUTION
Bootstrap information MUST be available; otherwise the system cannot be restored
using this method.
Bootstrap information is automatically stored on the Single Platform Processor.
Execute the following command as user root to list the bootstraps:
mminfo B
{34618} After the backup, you should run this command to get the last row, it is the
latest bootstrap information of your system. This will be used during the disaster
recovery.
Recovery of bootstrap information

In the event that bootstrap information is unavailable, it can be recovered by executing the
following procedure:
Procedure 12-15
Recovery of bootstrap information
Insert the latest backup tape into the tape drive.

/usr/sbin/nsr/scanner B
<device>
The tape device can be determined by examining the output of the following
command:
/usr/sbin/nsr/nsrmm
NOTE
The outputs displayed below are examples of GSM OMC-R disaster recovery.
Procedure 12-16
1
Disaster Recovery: Starting JumpStart
Insert the latest JumpStart media onto the client machine, and at the ok
prompt, execute as user root:
Boot cdrom -- restore solbak
Continued
12-20
68P02901W19-S
Oct 2009
Procedure 12-16
2
Disaster Recovery: Starting JumpStart (Continued)
Once the server has booted from the installation media, an information
window similar to the following is displayed.
IMPORTANT:
THIS INFORMATION MUST BE CORRECT FOR THE DISASTER
RECOVERY TO COMPLETE.
INFORMATION WILL ONLY BE ASKED FOR ONCE!
=================================================
Basic Disaster Recovery Information
=================================================
Press Enter to continue.
Entering network information

To enter the platform network information, follow this step:
Procedure 12-17
Disaster Recovery: Entering network information
The user is prompted to enter the platforms network information. Respond to

each prompt with the correct information.
Enter the machine's primary hostname: somc85
Enter the machine's IP address: 175.3.44.178
Enter the machine's netmask: 255.255.255.0
Enter the machine's default router (leave blank if not
required): 175.3.44.85
Entering backup tape device information
NOTE
The questions relate to the backup tape device connected to the Backup Server.
68P02901W19-S
12-21
Oct 2009
To enter the backup tape device information, follow this procedure:
Procedure 12-18
Disaster Recovery: Entering backup tape device information
The user is prompted to enter the backup tape device information. Respond
to each prompt with the correct information.
Enter Local Tape Device to be restored from: /dev/rmt/0hbn
Valid media types are:
1. DDS4
2. DAT72
3. DLT 7000
4. LTO-3
Enter Number for Device Media Type: 1
Entering bootstrap information

To enter the bootstrap information, follow this step:
Procedure 12-19
Disaster Recovery: Entering bootstrap information
The user is prompted to enter the bootstrap information. Respond to each

prompt with the correct information.
Enter latest bootstrap saveset id: 2808799757
Enter starting file number: 22
Enter starting record number: 0
12-22
68P02901W19-S
Oct 2009
Confirming the disaster recovery information

To confirm the disaster recovery information entered, follow this step:
Procedure 12-20
Disaster Recovery: Confirming the installation information
{34618}
1
Recovery begins once all the requested information has been provided.
Installation of OS is begun (takes a long time, >1 hour).
Once the OS is installed, a command prompt will be available.
Log in to the system as root and follow Procedure 12-1 to install the Backup
Server software.
Create a Tape device using nsradmin

/usr/sbin/nsr/nsradmin
Select visual by typing visual
The following screen gets displayed.
Select Create (Using arrow keys and pressing return to select )

Select NSR device
Accept default or edit the name to suite your tape device setting and select
media type, For example 4mm 20GB or DAT72.
Save your settings by pressing the Escape key and selecting Yes with the
Return key.
Continued
68P02901W19-S
12-23
Oct 2009
Procedure 12-20
(Continued)
Disaster Recovery: Confirming the installation information
Select Quit.
Type Quit and return at the prompt to return to the OS shell.
Recovery using Bootstrap Saveset IDs

Use the following procedure to recover the Backup Server configuration:
Procedure 12-21
1
Recovering using Backup Server configuration
Enter the following command as user root:

/usr/sbin/nsr/mmrecov
The following is an example of a typical bootstrap notification:
July 16 09:44 2003
date
07/11/06 01:35:18
backup1's bootstrap information Page 1
time
level ssid
full 235292161
file
56
record
volume
backup1_Jun15
2
Enter the latest bootstrap save set ID (ssid) when requested. In the example
above, this value is 235292161.
Continued
12-24
68P02901W19-S
Oct 2009
Procedure 12-21
Recovering using Backup Server configuration (Continued)
Enter the starting file number (file) when requested. In the example above,
this value is 56.
Enter the starting record number (record) when requested. In the example
above, this value is 0. At this point, insert the tape containing the saveset
identified by the bootstrap information into the tape drive on the OMC-R
and press RETURN.
NOTE
Once all requested information has been entered and the tape has
been inserted in the drive, the system starts retrieving the server
configuration information from the tape.
The output of the mmrecov command will be similar to the example below:
Scanning /dev/rmt/0mbn for save set 3870043393; this
may take a while...
scanner: scanning 4mm tape backup1_June15 on /dev/rmt/0mbn
/nsr
/nsr: file exists, overwriting
/solbak/nsr/res.R/servers
/solbak/nsr/res.R/nsrla.res
/solbak/nsr/res.R/nsrjb.res
/solbak/nsr/res.R/mot.res
/solbak/nsr/res.R/temip.res
/solbak/nsr/res.R/nsr.res
/solbak/nsr/res.R/
nsrmmdbasm -r /solbak/nsr/mm/mmvolume6/
/solbak/nsr/mm/
scanner: ssid 3870043393: scan complete
scanner: ssid 3870043393: 548 KB, 10 file(s)
/dev/rmt/0mbn: Mount operation in progress
/dev/rmt/0mbn: verifying label, moving backward 2 file(s)
/dev/rmt/0mbn: mounted 4mm tape backup1_June15 (write protected)
If your resource files were lost, they are now recovered in the
'res.R' directory.
Copy or move them to the 'res'
directory, after you have shut down the service.
Then restart
the service. Otherwise, just restart the service.

If the on-line index for backup1 was lost, it can be recovered using the
nsrck command.
Continued
68P02901W19-S
12-25
Oct 2009
Procedure 12-21
5
Once the server configuration information has been successfully retrieved,

shutdown the NetWorker services by executing the following command
as user root:
/usr/sbin/nsr/nsr_shutdown
Output of the command is similar to the following:
nsr_shutdown will kill the following processes
1598? S 0:00 /usr/sbin/nsr/nsrexecd -s backup1
1622? S 0:00 /usr/sbin/nsr/nsrexecd -s backup1
1665? S 0:00 /usr/sbin/nsr/nsrexecd
1668? S 0:00 /usr/sbin/nsr/nsrexecd
1669? S 0:00 /usr/sbin/nsr/nsrd
1680? S 0:00 /usr/sbin/nsr/nsrmmdbd
1681? S 0:00 /usr/sbin/nsr/nsrindexd
1682? S 0:00 /usr/sbin/nsr/nsrmmd -n 1
{34618} Rename the recovered Backup Server Configuration files:

As user root:
cd /nsr
mv res res.orig
mv res.R res
Restart NetWorker services:

As user root:
/usr/sbin/nsr/nsrexecd
/usr/sbin/nsr/nsrd
Confirm that the networker processes have started by issuing the following
command:
ps -ef | grep nsr
Output similar to the following should appear:
root 385 382 0 Feb 05 ? 0:36 /usr/sbin/nsr/nsrexecd

root 386 1 0 Feb 05 ? 1:23 /usr/sbin/nsr/nsrd
root 501 386 0 Feb 05 ? 0:18 /usr/sbin/nsr/nsrmmdbd
root 507 386 0 Feb 05 ? 0:06 /usr/sbin/nsr/nsrindexd
root 521 386 0 Feb 05 ? 0:07 /usr/sbin/nsr/nsrmmd -n 1
Continued
12-26
68P02901W19-S
Oct 2009
Procedure 12-21
9
Recover the Necessary Filesystems
Recover the indexes:

As user root:
/usr/sbin/nsr/nsrck -L7
Output of the command is similar to the following:
nsrck: checking index for 'backup1'

nsrck: The file index for client 'backup1' will be recovered.
nsrck: Recovering index savesets of 'backup1' from 'backup1'
NSR server backup1: busy
recover: waiting 30 seconds then retrying
Recover completion time: Fri Jun 15 14:41:06 200
nsrck: completed recovery of index for client 'backup1'
nsrck: /solbak/nsr/index/backup1 contains 417850 records
occupying 66 MB
nsrck: Completed checking 1 client(s)

Use the following procedure to recover the necessary filesystems:
Procedure 12-22
{34618}
NOTE
A graphical display is needed for the rest of the procedure.
1
Set your display and enter the following commands:

Start the restore program by issuing the following commands as user root:
cd /
/usr/bin/nwrecover &
Select the root file system (/) for restore from the left pane in the nwrecover
main window. Once a file system has been selected for restore, the check
box gets ticked.
Continued
68P02901W19-S
12-27
Oct 2009
Procedure 12-22
3
Recover the Necessary Filesystems (Continued)
Once the root file system has been selected, all directories which are mount
points must also be selected.
Mount points include:
/
/usr
/var
/opt
/omcgen
/home
/solbak
/zones
Expand the /usr file system and select
/usr/omc
Expand the /usr/omc file system by double click and select:
/usr/omc/logs
/usr/omc/ne_data
Expand the /usr/omc/ne_data by double click and select:
Expand the /usr/omc/logs file system by double click and select:
4
Deselect the /dev and /devices directories as they are not to be restored.
Navigate to the /directory and deselect the /solbak/nsr directory.
Navigate to the /etc directory and deselect the file path_to_inst.

The /dev and /devices directories, together with the /etc/path_to_inst
file, must not be restored as these are configured by the Operating System
installation.
The selection of file systems for restoration is now complete. To begin the
restore, click the Start button.
Continued
12-28
68P02901W19-S
Oct 2009
Procedure 12-22
A Conflict Resolution window is displayed.

Select No for the question:
Do you want to be prompted when conflict occurs?
Select Overwrite the existing file for the question:
When conflict occurs, the program should? Click OK to proceed.
Click OK to proceed.
The restore will restore these filesystems. A Recover Status window will be
displayed, indicating the current status of the Restore.
10
When a Recover completion time message appears in the Recover Status

window, the recovery of the filesystem is complete.
11
Click Cancel to return to the nwrecover main window
12
Click File and Exit to quit nwrecover.
13
Check /usr/omc.
If the output matches the following lines, it is incomplete. You should
continue steps 14 to 21.
# ls /usr/omc
logs
lost+found
ne_data
If the output matches the following lines, it is complete. Skip steps 14 to 21,
proceed to step 22 directly.
# ls /usr/omc
14
1.9.0.0.34
config
lib
lost+found
sbin
cdrom_install
current
logs
ne_data
sec
Start the restore program by issuing the following commands as user root to
restore /usr/omc again:
cd /
Continued
68P02901W19-S
12-29
Oct 2009
Procedure 12-22
15
Expand the /usr file system by double click and select:
/usr/omc
Expand the /usr/omc file system by double click and select
/usr/omc/logs
/usr/omc/ne_data
Expand the /usr/omc/ne_data by double click and select
Expand the /usr/omc/logs file system by double click and select
16
The selection of file systems for restoration is now complete. To begin the
17

18
The restore command will restore /usr/omc. A Recover Status window will
be displayed, indicating the current status of the Restore.
19

window, the recovery of /usr/omc is complete.
20
Click Cancel to return to the nwrecover main window
21

check if the /usr/omc restore is complete.
Continued
12-30
68P02901W19-S
Oct 2009
Procedure 12-22
22
Recovering Informix databases
If you have an incremental filesystem backup to restore, continue with

Procedure 12-23 to restore the latest data available in your system, after
completing the following set of instructions. Else, skip this step (step 22),
execute step 23.
Start the restore program by issuing the following commands as the user
root:
In the nwrecover program, select Save Set Recover from the Options menu.
From the Save Set Name list, select the name of the appropriate save set.
In the Instances list box, select the version of the save set based the backup
history and the time point you want to restore to.
Click Recover.
In the Save Set Recover Status dialog box, click Start to begin the
recovery.
The recovery status appears in the Save Set Recover Status dialog box.
Repeat the steps until all the restore is save set to a same time point.
23
Run init 6 to reboot the system.

Now the full and incremental backup of the system are restored completely.
The OMC and informix service are online (if available offline, start them).
The OMC system is ready to use. Only the data taken as backup before your
system backup is available
You should recover the data taken as backup after the system backup by
executing the steps given in Procedure 12-23.

The procedure to recover Informix databases, as part of a disaster recovery operation, is as
follows:
Procedure 12-23
{34618}
1

svcadm disable omc
/usr/omc/sbin/gcon file
/usr/omc/sbin/Initialize_Informix
svcadm disable svc:/application/informix/cm
svcadm disable svc:/application/informix/pm
Continued
68P02901W19-S
12-31
Oct 2009
Procedure 12-23
2
Recovering Informix databases (Continued)
Restore ixbar files from latest tape.
NOTE
A graphical display is needed for the rest of the procedure.
Set your display and enter the following commands:

Start the restore program by issuing the following commands as user root:
Select ixbar.1 and ixbar.2 for restore from the left pane in the nwrecover
main window. Once a file has been selected for restore, a blue tick appears
in the square check box.
The selection of ixbar files for restoration is now complete. To begin the
The restoration process restores these files. A Recover Status window will
be displayed, indicating the current status of the Restore.
window, the recovery of the filesystem is complete.
Click Cancel to return to the nwrecover main window.
Continued
12-32
68P02901W19-S
Oct 2009
Procedure 12-23
3
Perform a physical restore of the dbspaces for the CM database by issuing

(We need the latest ixbar files to restore the informix data to the latest time
point. If no latest ixbar.1 and ixbar.2 is available in this directory, produce
them by copying the latest version from the files taken as backup, following
the given set of commands.)
For example:
cp ixbar.1.2006109.122546 ixbar.1
mib_env
onbar -r -w p
To check the status of a restore using onbar, check the
/usr/informix/bar_act.log.
Once the database restore is complete, the CM database will be in
fast-recovery mode. Bring the database to quiescent mode by issuing the
onmode -sy
Once the database has changed to quiescent mode, bring the database
online by issuing the following command as user informix until the output
is similar to:
onmode -m
onmode: System is already online.
Continued
68P02901W19-S
12-33
Oct 2009
Procedure 12-23
4
Perform a physical restore of the dbspaces for the PM database by executing

omc_env
onbar -r -w -p
To check the status of a restore using onbar, check the file
/usr/informix/bar_act.log.
Once the database restore has completed, the PM database will be in
fast recovery mode. Bring the database to quiescent mode by issuing the
onmode -sy
Once the database has changed to quiescent mode, bring the database
online by issuing the following command as user informix until the output
is similar to:
onmode -m
onmode: System is already online.
svcadm enable svc:/application/informix/cm
svcadm enable svc:/application/informix/pm
Ensure svc:/application/informix/cm and svc:/application/informix/pm online
Execute the following command to start omc as user omcadmin:

omc start
Now the latest backup of informix (full and increment) are simultaneously
restored completely. The informix database is ready to use.
12-34
68P02901W19-S
Oct 2009
Recovery
Recovery
Introduction
This section describes how to recover files and database which may become corrupted either
through accidental deletion or other failure.
Recovery of a file or selection of files

Start the main recovery GUI by entering the following command as user root:
nwrecover
A screen similar to the following is displayed.
Figure 12-1
68P02901W19-S
Recover window
12-35
Oct 2009
Introduction
Using the UI, navigate to the directory and/or files which are to be recovered and select them.
In the example below, the files ixbar.1 and ixbar.2 have been selected for recovery.
Figure 12-2
File selection window for recovery
Press the Start button to starts the recovery. In the next screen, select Overwrite existing file
when prompted. The recovery checks whether the required tape is online.
12-36
68P02901W19-S
Oct 2009
Figure 12-3
Database recovery
Recover status
Database recovery
To recover either the PM or MIB (CM) databases, follow the procedure below.
Procedure 12-24
68P02901W19-S
PM database recovery
As user root, issue the following command:

omc_env
svcadm disable svc:/application/informix/pm
onbar r
Mount the required tape, if requested.
Once the recovery has completed, bring the database back online by
executing the following commands as user root:
onmode ky
svcadm enable svc:/application/informix/pm
12-37
Oct 2009
Database recovery
Procedure 12-25
12-38
MIB (CM) database recovery

mib_env
svcadm disable svc:/application/informix/cm
onbar r
Mount the required tape, if requested.
Once the recovery is complete, bring the database back online by executing
the following commands as user root:
onmode ky
svcadm enable svc:/application/informix/cm
68P02901W19-S
Oct 2009
Additional Tools
Additional Tools
This section details various tools that, while not part of the OMC-R backup server, may be of use.
StorEdge Enterprise Backup Server GUI

As of Solaris 10, the StorEdge Enterprise Backup Server GUI, nwadmin, is no longer available.
Instead, a Java web-based interface has been introduced. Once the OMC-R Backup Server is
installed, the StorEdge Enterprise Backup Server GUI can be configured.
Configuring Java Version
NOTE
The Java-based interface has an additional layer that allows the management of
multiple OMC-R Backup Servers. Documentation on how to use this is not included in
this feature reference docs.sun.com for further details.
Procedure 12-26
68P02901W19-S
StorEdge Enterprise Backup Server: Java Configuration
Login to the Single Platform Processor as user root.
Remove the /.java directory, if it exists.
Ensure that the DISPLAY is set correctly. Open a browser window by

executing the following command:
/usr/sfw/bin/mozilla &
In the browser window, select Edit Preferences. Highlight Helper

Applications under Navigator, and select New Type.
Add the following information:

MIME Type: application/x-java-jnlp-file
Extension: .jnlp
Open it with: /usr/j2se/jre/javaws/javaws
Ensure that the Open it with: is selected. Click OK.
Click OK to save out of Preferences.
12-39
Oct 2009
Licensing the Sun StorEdge EBS Server using the Administration Window
Backup Server Installation and Configuration
Chapter 12:
Launching the StorEdge Enterprise Backup Server GUI

Procedure 12-27
StorEdge Enterprise Backup Server: Launching GUI
A browser is installed by default on the OMC-R Backup Server and can

be run as user root.
Ensure that the DISPLAY is set correctly. Open a browser window by

executing the following command:
/usr/sfw/bin/mozilla &
Connect to the following URL: http://<server>:10000

Where <server> is the fully qualified GSM OMC-R hostname.
Click Start button to start the Enterprise Manager.
A login dialog box is displayed. The default username/password is

administrator.
On first login, configuration is required.
Accept the License agreement.

Click Next on Welcome to the Configuration Window.
Change the administrator password if required. Otherwise, click Next to

retain the default password.
Click Next on Set Legato License Manager Server Name.
10
Click Next on Set Database Backup Server window.
11
Add Backup Server hostname on Add Sun StorEdge EBS Servers, and
click Next.
12
The GUI is displayed. Click the Enterprise button, and select the OMC-R
Backup Server hostname. Double-click the entry in the main window
another window, is displayed.
Licensing the Sun StorEdge EBS Server using the Administration

Window
Use the following procedure to license the Sun StorEdge EBS Server by using the administrator
window:
Procedure 12-28
window
12-40
License a Sun StorEdge EBS server by using the Administration
From the StorEdge Enterprise Backup Server GUI Administration

window, click Configuration.
Right-click Registrations, then select New.
Complete the necessary attributes, and then click OK.
68P02901W19-S
Oct 2009
Tape Management
NOTE
For further information, see Sun StorEdge Enterprise Backup Software 7.3
Administration Guide (Sun Doc ID: 819-4972) from docs.sun.com.
Tape Management
While tape management is done by the StorEdge Enterprise Backup Server GUI, a very basic
interface has been designed to allow the user to have access to simple tape functionality such as
mount, un-mount, label, and tape status information.
Launching Basic Tape Management Interface

Procedure 12-29
Tape Management Launching Menu

/var/install/bin/tape-mgr
The following menu is displayed:

Tape Menu
===========
1. Mount
2. Unmount
3. Label
4. Status
5. Exit
Select appropriate option.
NOTE
The label option will prompt for a label name, and
AUTOMATICALLY re-label the tape if a label already exists
query to mount the tape after labelling is also displayed.
Tape Management from the command line

Use the table below to manage tapes from the command line.
Table 12-4
Tape Management from the command line
Activity
Label a tape
Command
/usr/sbin/nsr/nsrmm l
<tape label>
Example
/usr/sbin/nsr/nsrmm
l test.001
nsrmm -l test.001
Continued
68P02901W19-S
12-41
Oct 2009
Tape Management
Table 12-4
Tape Management from the command line (Continued)
Activity
12-42
Command
Example
Mount a tape
/usr/sbin/nsr/nsrmm m
<tape label>
/usr/sbin/nsrmm m
test.001
4mm tape test.001
mounted on
/dev/rmt/0mbn, write
enabled
Unmount a tape
/usr/sbin/nsr/nsrmm u
<tape label>
/usr/sbin/nsr/nsrmm
u test.001
Unmounted device:
/dev/rmt/0mbn
Query tape status
/usr/sbin/nsr/nsrmm
/usr/sbin/nsr/nsrmm
(nothing) mounted
on 4mm tape
/dev/rmt/0mbn
68P02901W19-S
Oct 2009
Additional Information
Additional Information
This section provides additional information about the Installation log files.
Installation log files

The installation log files are found in: /var/install/logs directory.
Sample output from backup client creation

The following is a sample output from backup client creation.
Responses are highlighted.
Enter Option: 2
Adding Client
Enter Client hostname: somc85
Setting up SSH between the Backup Server and somc85.
If this is the first time, the root password for somc85 has to be supplied.
68P02901W19-S
12-43
Oct 2009
Select Server Type

==================
1.
GUI_SERVER
2.
Informix_CM
3.
Informix_PM
4.
Informix_IX1
5.
Informix_IX2
Enter choice : 2
Server type chosen is: Informix_CM
No resources found for query:
name: INFORMIX_CM Directives;
type: NSR directive;
name: Informix_Schedule;
type: NSR schedule;
Schedule Informix_Schedule does not exist. Creating...
name: INFORMIX_CM;
type: NSR Group;
name: somc85;
saveset: "Informix:/omc_mib1";
type: NSR client;
==================
Backup Server Menu
==================
5. Quit
Enter Option: 2
Adding Client
Setting up SSH between the Backup Server and somc85
Select Server Type
==================
12-44
68P02901W19-S
Oct 2009
1.
GUI_SERVER
2.
Informix_CM
3.
Informix_PM
4.
Informix_IX1
5.
Informix_IX2
Enter choice : 3
Server type chosen is: Informix_PM
name: INFORMIX_PM Directives;
type: NSR schedule;
comment: ;
period: Week;
action: full full full full full full full;
override: ;
name: INFORMIX_PM;
type: NSR Group;
name: somc85;
saveset: "Informix:/omc_sys1";
type: NSR client;
==================
Backup Server Menu
==================
5. Quit
68P02901W19-S
12-45
Oct 2009
Enter Option: 2
Adding Client
Select Server Type
==================
1.
GUI_SERVER
2.
Informix_CM
3.
Informix_PM
4.
Informix_IX1
5.
Informix_IX2
Enter choice : 4
Server type chosen is: Informix_IX1
name: INFORMIX_IX1 Directives;
type: NSR schedule;
comment: ;
period: Week;
override: ;
name: INFORMIX_IX1;
type: NSR Group;
name: somc85;
saveset: /usr/informix/etc/ixbar.1;
type: NSR client;
==================
Backup Server Menu
==================
5. Quit
12-46
68P02901W19-S
Oct 2009
Enter Option: 2
Adding Client
Select Server Type
==================
1.
GUI_SERVER
2.
Informix_CM
3.
Informix_PM
4.
Informix_IX1
5.
Informix_IX2
Enter choice : 5
Server type chosen is: Informix_IX2
name: INFORMIX_IX2 Directives;
type: NSR schedule;
comment: ;
period: Week;
override: ;
name: INFORMIX_IX2;
type: NSR Group;
name: somc85;
saveset: /usr/informix/etc/ixbar.2;
type: NSR client;
==================
Backup Server Menu
5. Quit
68P02901W19-S
12-47
Oct 2009
Backup and Restore using the Standard Solaris suite of utilities
Enter Option: 5
Exiting at user request

Backing up the Single Platform Processor and MMI file systems
Overview to backing up file systems using backup_splat utility
Procedure for backing up file systems using the backup_splat utility
Overview to backing up PM and CM databases
Backing up the PM database
Backing up the CM database
Overview to backing up file systems using the backup_MMI utility
Procedure for backing up file systems using backup_MMI utility
Overview to backing up file systems using backup_splat utility

This section describes how to perform backups of the Single Platform Processor Server UNIX
file system using the backup_splat utility. The backup is performed to a local tape drive.
CAUTION
Ensure that there is no CD/DVD in the CD/DVD drive before performing the backup.
Backing up file systems using backup_splat utility

Use the following procedure to perform a backup of the UNIX file systems on the Single
Platform Processor Server automatically:
Procedure 12-30
Backing up file systems using backup_splat utility
Log in to the Single Platform Processor as user root.
Insert a new labelled DAT tape into the appropriate processor tape drive, ensuring
that it is not write-protected.
Change directory to /usr/omc/current/sbin by executing the following command:

Continued
12-48
68P02901W19-S
Oct 2009
Procedure 12-30
4
Backing up file systems using backup_splat utility (Continued)
Enter the following command to run the backup_splat utility.

./backup_splat
Is there a writable DAT tape loaded in the Tape.
Please enter YES to continue:YES
The following output is displayed:

Enter Backup Tape Device (Default is /dev/rmt/0):
Enter the backup tape device name (if the default is not correct) and press
RETURN.

FULL FILE BACKUP
a /tmp/restore_splat 2 tape blocks
a /tmp/backup_list 1 tape blocks
Backing up the / filesystem
DUMP: Date of this level 0 dump: Fri Jan 05 13:56:27 2007
DUMP: Dumping /dev/md/rdsk/d0 (somc85:/) to /dev/rmt/0n.
DUMP: Estimated 304120 blocks (148.50MB)
DUMP: DUMP IS DONE
DUMP: Level 0 dump on Fri Jan 05 13:56:27 2007
Backing up the /usr filesystem
DUMP: Dumping /dev/md/rdsk/d20 (somc85:/usr) to /dev/rmt/0n.
DUMP: Estimated 12739366 blocks (6220.39MB)
Continued
68P02901W19-S
12-49
Oct 2009
Procedure 12-30

DUMP: DUMP IS DONE
Backing up the /var filesystem
DUMP: Dumping /dev/md/rdsk/d10 (somc85:/var) to /dev/rmt/0n.
DUMP: DUMP IS DONE
Backing up the /opt filesystem
DUMP: Dumping /dev/md/rdsk/d15 (somc85:/opt) to /dev/rmt/0n.
DUMP: DUMP IS DONE
Backing up the /omcgen filesystem
DUMP: Dumping /dev/md/rdsk/d30 (somc85:/omcgen) to /dev/rmt/0n.
Continued
12-50
68P02901W19-S
Oct 2009
Procedure 12-30

DUMP: DUMP IS DONE
Backing up the /home filesystem
DUMP: Dumping /dev/md/rdsk/d35 (somc85:/home) to /dev/rmt/0n.
DUMP: DUMP IS DONE
Backing up the /usr/omc filesystem
DUMP: Dumping /dev/md/rdsk/d40 (somc85:/usr/omc) to /dev/rmt/0n.
DUMP: DUMP IS DONE
Backing up the /usr/omc/logs filesystem
Continued
68P02901W19-S
12-51
Oct 2009
Procedure 12-30
DUMP: Dumping /dev/md/rdsk/d45 (somc85:/usr/omc/logs) to /dev/rmt/0n.

DUMP: DUMP IS DONE
Backing up the /usr/omc/ne_data filesystem
DUMP: Dumping /dev/md/rdsk/d50 (somc85:/usr/omc/ne_data) to /dev/rmt/0n.
DUMP: DUMP IS DONE
Backing up the /usr/omc/ne_data/raw_stats filesystem
DUMP: Dumping /dev/md/rdsk/d55 (somc85:/usr/omc/ne_data/raw_stats)
to /dev/rmt/0n.
DUMP: DUMP IS DONE
Backing up the /solbak filesystem
Continued
12-52
68P02901W19-S
Oct 2009
Procedure 12-30

DUMP: Dumping /dev/md/rdsk/d60 (somc85:/solbak) to /dev/rmt/0n.
DUMP: DUMP IS DONE
Backing up the /usr/omc/logs/bss_sec filesystem
DUMP: Dumping /dev/md/rdsk/d65 (somc85:/usr/omc/logs/bss_sec)
to /dev/rmt/0n.
DUMP: DUMP IS DONE
Backing up the /usr/omc/logs/sleeping_cell filesystem
DUMP: Dumping /dev/md/rdsk/d70 (somc85:/usr/omc/logs/sleeping_cell)
to /dev/rmt/0n.
DUMP: DUMP IS DONE
Continued
68P02901W19-S
12-53
Oct 2009
Procedure 12-30
Backing up the /zones filesystem

DUMP: Dumping /dev/md/rdsk/d75 (somc85:/zones) to /dev/rmt/0n.
DUMP: DUMP IS DONE
Backing up the /usr/omc/ne_data/e1mon filesystem
DUMP: Dumping /dev/md/rdsk/d80 (somc85:/usr/omc/ne_data/e1mon)
to /dev/rmt/0n.
DUMP: DUMP IS DONE
Backup completed
REWINDING TAPE....
7
Perform a confidence check on the tape(s) by entering the following command:

dd if=/dev/rmt/0n of=/dev/null bs=1024k.
NOTE
Repeat this seven more times in order to check the complete backup.
The confidence check command line must be entered once for each
partition that has been backed up, plus one additional time for the tar
files at the front of the backup tape. In this example, there are seven
file systems that have been backed up, therefore it is necessary to enter
this command a total of eight times.
8
12-54
Make the tape write-protected. A log file is kept in

/usr/omc/logs/backup_splat.<datestamp>.
68P02901W19-S
Oct 2009
Backing up the PM and CM Databases
Default DAT parameters.
Level of backup.
Checking and changing tape parameters.
Backing up the PM Database.
Overview of IDS message log files for the PM Database.
Monitoring the active message log files for the PM Database.
View Archived message log files for the PM Database.
Backing up the CM Database.
Overview of IDS message log files for the CM Database.
Monitoring the active message log files for the CM Database.
View Archived message log files for the CM Database.
Default DAT tape parameters

Tape parameters should be checked for the Single Platform Processor default DAT drive before
backing up or restoring the databases. The following parameters apply to the default DAT drive.
The tape device is /dev/rmt/0.
The tape blocking factor/size is 1024 KB for the DAT tape.
The tape size (in KB) is 4000000 for the DAT tape.
Level of backup
The level of backup is required when performing the archive procedure.
The following levels of backup exist:
Level 0 - monthly backup.
Level 1 - weekly backup.
Level 2 - daily backup.
Checking and changing tape parameters

As user Informix execute the following command:
/usr/omc/sbin/set_tape_parameters.sh
The recommended tape sizes for Informix are:
68P02901W19-S
12-55
Oct 2009
DDS3 20,000,000
DDS4 38,000,000
DAT72 70,000,000
The utility /usr/omc/sbin/set_tape_parameters.sh will only set the tape parameters for the
default DDS3 device. If you have DDS4 or DAT72, then use the following procedure to change
the tape parameters:
Procedure 12-31
Checking and changing tape parameters
Login to the System Processor as user informix.
Set the following environment variable:

setenv TERM vt100
Set the correct environment for the database archive. For CM database,
enter the alias mib_env. For the PM database, enter the alias omc_env.
Check the tape parameters by using the onmonitor utility. The following
example shows an sample output for a DDS4 tape:
Dynamic Server: Status Parameters Dbspaces Mode ForceCkpt ...
Archive Logical-Logs Exit Status menu to view Dynamic Server
Online
Press CTRLW for Help
Select the Archive option from the onmonitor menu by using the space bar
to toggle between options:
InformixOnline: ... Archive LogicalLogs Exit
Change tape device or tape characteristics.
Online
This will bring up the Archive menu:
ARCHIVE: Tape Parameters Exit
Change tape device or tape characteristics
Online
Select the Tape Parameters option to bring up the Tape Parameters menu:
Press ESC to change tape parameters.
Press Interrupt to return to the Archive menu.
Press F2 or CTRL-F for field level help.
MODIFYING TAPE PARAMETERS
Tape Device [/dev/rmt/0]
Continued
12-56
68P02901W19-S
Oct 2009
Procedure 12-31
Checking and changing tape parameters (Continued)
Block Size [ 1024] Kbytes Tape Size [ 38000000]Kbytes

Log Tape Device [/dev/null]
Block Size [64] Kbytes Tape Size [ 2000000]Kbytes
For the default DAT drive, ensure the tape device is set to /dev/rmt/0, the
block size set to 1024 and the tape size set to 38000000. Press ESC to
commit any changes, or CTRL-C to quit without saving.
7
Select the Exit option to exit the Archive menu. Select the Exit option again
to exit the onmonitor utility.
Backing up the PM Database

Procedure 12-32
Back up the PM database to the Single Platform Processor
Login to the Single Platform Processor using login id root and switch user to
informix:
su informix

setenv TERM vt100
Set the correct environment for the database archive.

For the PM database, enter the alias:
omc_env

Start the archive by entering the following command:

ontape s L <archive_level>
Where <archive_level> is the level of archive. For example, to start a level 0
archive enter ontape s L 0.
Please mount tape 1 on /dev/rmt/0 and press Return to continue

The archive can be terminated at any point of time by pressing the interrupt
key. This is usually CTRL-c or the DELETE key. If the archive is interrupted,
then the archive copy is corrupted and a new archive will have to be initiated
to perform a backup.
Press RETURN.
Continued
68P02901W19-S
12-57
Oct 2009
Procedure 12-32
(Continued)
6
Back up the PM database to the Single Platform Processor
10 percent done
20 percent done
40 percent done
60 percent done
100 percent done
Please label this tape as number 1 in the archive tape sequence.
This tape contains the following the following logical logs:
3
Program over
7
If the archive requires more than one tape, the user is prompted when a
change of tape is needed.
The tapes must be labelled 1, 2, 3, and so on, to indicate the sequence in
which the tapes must be mounted if used to restore the database.
If an error occurs during the archive, an error message is displayed followed

by the message:
Please mount tape and press Return to continue
The archive procedure can be interrupted to fix any problems before
pressing the RETURN key.
When the archive is complete, a message is displayed indicating which tapes

are required to restore the database to its present state. The message
also indicates the logical log at which to start to restore the system after
the backup tapes have been mounted. The logical log information can be
ignored as logical logs are not currently used.
10
Perform a confidence check on the tape(s) by entering the following

command:
dd if=/dev/rmt/0 of=/dev/null bs=1024k
11
If the confidence check performed in step 10 is successful, write protect,

label, and store the tape(s). If an error is returned, replace the faulty tape
and repeat the backup procedure from step 5.
Overview of IDS message log files for the PM Database

Each Informix Dynamic Server requires a message log file. As these files increase continuously
in size, they are not suitable for archiving with the other log files therefore a cron job is required
to move the message log files to a time-stamped file, which can then be archived and removed
from the file system. The cron job is /usr/omc/sbin/roll_online.log. The message log files are
owned by informix and held on the Single Platform Processor as follows:
12-58
/usr/informix/online.log_OMC - active message log file for PM database.
/usr/informix/online.log_OMC.<ddmmyyyy> - archived message log file for PM database.
68P02901W19-S
Oct 2009
Monitoring the active message log files for the PM Database

The IDS active message logs can be viewed using the onstat utility or the UNIX tail command.
Use the following procedure to view the PM database message logs:
Procedure 12-33
Viewing the PM database message logs
informix:
su - informix
Set up the correct environment:

For PM database enter:
omc_env
Monitor the last few lines of the chosen message log by using either the
onstat utility or the tail command:
Using onstat utility:
onstat -m
A -r option can be included to allow the process sleep time to be specified as
a parameter (onstat -m -r <sleep_time>). The <sleep_time> specifies
the number of seconds the process will be put to sleep before rechecking
the IDS message log file.
Using the unix tail command, execute:
View Archived message log files for the PM Database

Use the following procedure to monitor timestamped IDS message log files:
Procedure 12-34
68P02901W19-S
Monitoring timestamped IDS message log files
informix:
su - informix
Display the appropriate timestamped message log file.

For PM database timestamped message log file enter:
view /usr/informix/online.log_OMC.<ddmmyyyy>
Where <ddmmyyyy> is the day, month and year the log file was created.
12-59
Oct 2009
Backing up the CM database

Use the following procedure to back up the CM database to the Single Platform Processor
DAT drive:
Procedure 12-35
Back up the CM database to the Single Platform Processor
informix:
su informix

setenv TERM vt100
Set the correct environment for the database archive.

mib_env

Start the archive by entering the following command:

ontape s L <archive_level>
Where <archive_level> is the level of archive. For example, to start a level 0
archive enter ontape -s L 0.
Please mount tape 1 on /dev/rmt/0 and press Return to continue
The archive can be terminated at any point of time by pressing the interrupt
key. This is usually CTRL-c or the DELETE key. If the archive is interrupted,
then the archive copy is corrupted.
Press RETURN.
6
10 percent done
20 percent done
40 percent done
60 percent done
100 percent done
Please label this tape as number 1 in the archive tape sequence.
This tape contains the following the following logical logs:
3
Program over
Continued
12-60
68P02901W19-S
Oct 2009
Procedure 12-35
(Continued)
Back up the CM database to the Single Platform Processor
If the archive requires more than one tape, the user is prompted when a
change of tape is needed.
The tapes must be labeled 1, 2, 3, and so on, to indicate the sequence in
which the tapes must be mounted if used to restore the database.
If an error occurs during the archive, an error message is displayed followed

by the message:
Please mount tape and press Return to continue
The archive procedure can be interrupted to fix any problems before
pressing the RETURN key.
When the archive is complete, a message is displayed indicating which tapes

are required to restore the database to its present state. The message
also indicates the logical log at which to start to restore the system after
the backup tapes have been mounted. The logical log information can be
ignored as logical logs are not currently used.
10
Perform a confidence check on the tape(s) by entering the following

command:
dd if=/dev/rmt/0 of=/dev/null bs=1024k
11
If the confidence check performed in step 10 is successful, write protect,

label, and store the tape(s). If an error is returned, replace the faulty tape
and repeat the backup procedure from step 5.
Overview of IDS message log files for the CM Database

Each Informix Dynamic Server requires a message log file. As these files increase continuously
in size, they are not suitable for archiving with the other log files therefore a cron job is required
to move the message log files to a time-stamped file, which can then be archived and removed
from the file system. The cron job is /usr/omc/sbin/roll_online.log. The message log files are
owned by informix and held on the Single Platform Processor as follows:
/usr/informix/online.log_MIB active message log file for CM database.
/usr/informix/online.log_MIB.<ddmmyyyy> archived message log file for CM database.
68P02901W19-S
12-61
Oct 2009
Monitoring the active message log files for the CM database

The IDS active message logs can be viewed using the onstat utility or the UNIX tail command.
Use the following procedure to view the CM database message logs:
Procedure 12-36
View the CM database message logs
Log in to the Single Platform Processor using login id root and switch user
to informix:
su informix
Set up the correct environment:

mib_env
Monitor the last few lines of the chosen message log by using either the
onstat utility or the tail command:
Using onstat utility:
onstat m
A r option can be included to allow the process sleep time to be specified as
a parameter (onstat m -r <sleep_time>). The <sleep_time> specifies
the number of seconds the process will be put to sleep before rechecking
the IDS message log file.
Using the unix tail command, execute:
tail f $INFORMIXDIR/online.log_MIB
View Archived message log files for the CM Database

Use the following procedure to monitor timestamped IDS message log files:
Procedure 12-37
12-62
Monitoring the timestamped IDS message log files.
Log in to the Single Platform Processor using login ID root and switch user
to informix:su informix
Display the appropriate timestamped message log file.

For PM database timestamped message log file enter:view
/usr/informix/online.log_MIB.<ddmmyyyy>
Where <ddmmyyyy> is the day, month and year the log file was created.
68P02901W19-S
Oct 2009
Restoring Single Platform Processor file systems
Full file system restore on page 12-63
Shutting down the Single Platform Processor on page 12-64
JumpStarting the Netra Single Platform Processor on page 12-64
JumpStarting the SunFire Single Platform Processor on page 12-67
JumpStarting the SunEnterprise M4000/M5000 Single Platform Processor on page 12-72
Full file system restore

Restoring Single Platform Processor file systems can be achieved using the ufsrestore utility.
This utility enables recovery of all Single Platform Processor file systems that have been stored
on a backup tape using the backup_splat utility. The data can be restored on a brand new set of
disks or on disks that have become corrupt.
CAUTION
The procedure destroys any data on the disks and overwrites the disks with data
from the backup tape.
The task of restoring file systems to the Single Platform Processor involves the following
procedures:
Shutting down the Single Platform Processor.
JumpStarting the Single Platform Processor.
Restoring the databases.
Before commencing the restore procedure, ensure that a copy of the most recent set of Single
Platform Processor complete file system level 0 backup tapes (created using the backup_splat
utility) is available.
68P02901W19-S
12-63
Oct 2009
Shutting down the Single Platform Processor

Use the following procedure to perform a shutdown of the Single Platform Processor:
Procedure 12-38
Shutting down the Single Platform Processor
Log in to the Single Platform Processor as user root.
Enter the following commands to inform all users that a complete system
restore is to be performed:
wall
System coming down immediately
^d
Bring the system down to PROM mode:

The PROM monitor mode ok prompt is displayed.
JumpStarting the Netra Single Platform Processor

For the clean install of the Netra Single Platform, refer to the procedure given in Chapter
2 of the Installation and Conguration: OMC-R Clean Install (68P02901W47). Follow all the
instructions provided in the procedure excluding the following sections:
The /etc/dfs/dfstab file.
Modifying the /etc/hosts file.
Creating the /etc/hosts.equiv file.
Creating the /.rhosts file.
Complete the following procedure to restore the Netra Single Platform Processor:
Procedure 12-39
JumpStarting the Netra Single Platform Processor
Insert the Motorola JumpStart DVD in the DVD-ROM drive of the System
Processor.
Insert the latest Full System backup tape in the DAT drive of the System
Processor.
Enter the following command at the ok prompt and press RETURN:

boot cdrom - restore
Follow the on-screen prompts.
Continued
12-64
68P02901W19-S
Oct 2009
Procedure 12-39
4
JumpStarting the Netra Single Platform Processor (Continued)
Once the system has rebooted, execute the following command as user root:
prtconf | grep pci1214
Screen output similar to the following is displayed to notify that the HSIP
drivers are attached:
pci1214,334, instance #0
If the HSIP drivers are not attached, then the following message is displayed:
pci1214,334, instance #0 (driver not attached)
If the HSIP drivers are not attached, execute the following commands to attach
the HSIP drivers as user root:
rem_drv HSIP
add_drv HSIP
The Netra Single Platform Processor then restores the full system backup
from tape and upon completion returns with the console login. At this point,
the system needs to be rebooted to restart services by running the following
/usr/sbin/shutdown -i6 -g0 y
Once the system has rebooted, compare the two files /etc/inet/hosts and
/etc/inet/hosts.postmerge, if there are differences between the two files, need
to manually update /etc/inet/hosts by executing the following command: cd
/etc/inet/
cp ./hosts.postmerge ./hosts
rm ./ipnodes
ln s ./hosts ./ipnodes
If NIS is used as the naming service, execute the following as root:

ypinit -m
In order for NIS to operate successfully, we have to construct a
list of the NIS servers. Continue to add the names for YP servers
in the order of preference, one per line. When you are done with
the list, type a <control D> or a return on a line by itself.
next host to add:mercia
next host to add:
The current list of yp servers looks like this:
mercia
Is this correct?
[y/n: ] y
Continued
68P02901W19-S
12-65
Oct 2009
Procedure 12-39
Installing the YP database will require that you answer a few questions.
Questions will all be asked at the beginning of the procedure.
Do you want this procedure to quit on non-fatal errors? [y/n: n]
OK, please remember to go back and redo manually whatever fails.
If you don't, some part of the system (perhaps the yp itself) won't
work.
The yp domain directory is /var/yp/omcadmin
Can we destroy the existing /var/yp/omcadmin and its
contents? [y/n: n] y
There will be no further questions. The remainder of the
procedure should take 5 to 10 minutes.
Building /var/yp/omcadmin/ypservers...
Running /var/yp /Makefile...
updated passwd
updated group
updated hosts
updated ipnodes
updated ethers
updated networks
updated rpc
updated services
updated protocols
updated netgroup
updated bootparams
/var/yp/omcadmin/mail.aliases: 12 aliases, longest 10 bytes, 138
bytes total
Continued
12-66
68P02901W19-S
Oct 2009
Procedure 12-39
/usr/lib/netsvc/yp/mkalias /var/yp/domainname/mail.aliases
/var/yp/domainname/mail.byaddr;
updated aliases
updated publickey
updated netid
/usr/sbin/makedbm /etc/netmasks /var/yp/domainname/netmasks.byaddr;
updated netmasks
updated timezone
updated auto.master
updated auto.home
updated ageing
updated auth_attr
updated exec_attr
updated prof_attr
updated user_attr
updated audit_user
mercia has been set up as a yp master server without any errors.
If there are running slave yp servers, run yppush now for any data bases which
have been changed. If there are no running slaves, run ypinit on those hosts
which are to be slave servers.
8
The system needs to be rebooted to restart services by executing the following

command as user root:/usr/sbin/shutdown -i6 -g0 -y
If you need to restore the databases too, please execute the following command
as user root:svcadm clear svc:/system/basicreg:default
svcadm disable omc
10
After logging in, please refer to section Restoring databases on the

Single Platform Processor on page 12-58 in documentation W19
Operating_Information_OMC-R_System_Administration
JumpStarting the SunFire Single Platform Processor

For the clean install of the SunFire Single Platform, refer to the procedure given in Chapter
2 of the Installation and Conguration: OMC-R Clean Install (68P02901W47). Follow all the
instructions provided in the procedure excluding the following sections:
Creating the /.rhosts file.
Procedure 12-40 to restore the Sunfire 4800/4900.
68P02901W19-S
12-67
Oct 2009
Procedure 12-40
JumpStarting the SunFire Single Platform Processor
Insert the Motorola JumpStart DVD in the DVD-ROM drive of the Single
Platform Processor.
Insert the latest Full System backup tape in the DAT drive of the Single
Platform Processor.
Enter the following command at the ok prompt, and press RETURN. If

auto-boot is set to false, the server does not start up automatically after
power on or reset.
setenv auto-boot? False
auto-boot? = false
Enter the following command to reboot the server, and press RETURN.
reset-all
Resetting ...
Copying IO prom to Cpu dram
{/N0/SB2/P2}
@(#) lpost 5.13.2 2005/06/21 12:33
{/N0/SB2/P2}
Copyright 2001 Sun Microsystems, Inc. All rights reserved.
..............................{/N0/SB2/P2}
Running PCI IO Controller
Basic Tests
{/N0/SB2/P2}
Jumping to memory 00000000.00000020 [00000010]
{/N0/SB2/P2}
System PCI IO post code running from memory
{/N0/SB2/P2} @(#)
lpost 5.13.2 2005/06/21 12:33
{/N0/SB2/P2} Copyright 2001 Sun
Microsystems, Inc. All rights reserved.
Continued
12-68
68P02901W19-S
Oct 2009
Procedure 12-40
5
JumpStarting the SunFire Single Platform Processor (Continued)
Enter the following command to identify all the devices attached to the
SCSI bus, and press RETURN.
probe-scsi-all
/ssm@0,0/pci@19,700000/pci@2/SUNW,isptwo@4/sd@6,0:f
Target
2
Unit 0 Processor SUN D240 2
Target 4
Unit
0 Disk SEAGATE ST34371W SUN4.2G7462
Target 6
Unit
0 Removable Read Only device TOSHIBA DVD-ROM SD-M14011009
Type nvalias cdrom at the OK> prompt.

Select the device path associated with the DVD-ROM drive (this is the first
line of the previous screen output). Paste this device path after nvalias
cdrom.
If this string contains "scsi", append /disk@6,0:f to the string.
If it contains "isptwo", append /sd@6,0:f to the string.
The 6,0 in this example refers to Target 6 and unit 0 where the DVD-ROM
resides on the SCSI bus.
For example:
nvalias cdrom
/ssm@0,0/pci@19,700000/pci@2/SUNW,isptwo@4/sd@6,0:f
or
nvalias cdrom /ssm@0,0/pci@19,700000/pci@2/scsi@2/disk@6,0:f
At the OK> prompt, execute the following command:
boot cdrom -- restore
The system is jumpstarted without any prompts and the file systems are
automatically restored.
prtconf | grep pci1214
Screen output similar to the following is displayed to notify that the HSIP
drivers are attached:
If the HSIP drivers are not attached, the following message is displayed:
Continued
68P02901W19-S
12-69
Oct 2009
Procedure 12-40
If the HSIP drivers are not attached, execute the following commands to
attach the HSIP drivers as user root:
rem_drv HSIP
add_drv HSIP
8
The Sunfire Single Platform Processor then restores the full system backup
from tape and upon completion returns with the console login. At this
point, the system needs to be rebooted to restart services by executing
the following command as user root:
Once the system has rebooted, compare the two files /etc/inet/hosts and
/etc/inet/hosts.postmerge
If there are differences between the two files, need to manually update
/etc/inet/hosts by executing the following command:
cd /etc/inet/
cp ./hosts.postmerge ./hosts
rm ./ipnodes
ln s ./hosts ./ipnodes
10
If NIS is used as the naming service, execute the following as root:

ypinit -m
In order for NIS to operate successfully, we have to construct
a list of the NIS servers. Continue to add the names for YP
servers in the order of preference, one per line. When you are
done with the list, type a <control D> or a return on a line by
itself.
next host to add:mercia
next host to add:
The current list of yp servers looks like this:
mercia
Is this correct?
[y/n: ] y
Installing the YP database will require that you answer a

few questions. Questions will be asked at the
beginning of the procedure.
Do you want this procedure to quit on non-fatal
errors? [y/n: n]
OK, please remember to go back and redo manually whatever fails.
If you don't, some part of the system (perhaps the yp itself) won't
work.
The yp domain directory is /var/yp/omcadmin
Continued
12-70
68P02901W19-S
Oct 2009
Procedure 12-40
There will be no further questions. The remainder of the

procedure should take 5 to 10 minutes.
Building /var/yp/omcadmin/ypservers...
Running /var/yp /Makefile...
updated passwd
updated group
updated hosts
updated ipnodes
updated ethers
updated networks
updated rpc
updated services
updated protocols
updated netgroup
updated bootparams
/var/yp/omcadmin/mail.aliases: 12 aliases, longest 10 bytes, 138
bytes total
updated aliases
updated publickey
updated netid
updated netmasks
updated timezone
updated auto.master
updated auto.home
updated ageing.
updated auth_attr
updated exec_attr
updated prof_attr
updated user_attr
updated audit_user
If there are running slave yp servers, run yppush now for any data bases
which have been changed. If there are no running slaves, run ypinit on
those hosts which are to be slave servers.
Continued
68P02901W19-S
12-71
Oct 2009
Procedure 12-40
11
The system needs to be rebooted to restart services by executing the

following command as user root:
12
If you need to restore the databases too, please execute the following
svcadm clear svc:/system/basicreg:default
svcadm disable omc
13
After logging in, please refer to section Restoring databases on the

Single Platform Processor on page 12-59 in documentation W19
Operating_Information_OMC-R_System_Administration
JumpStarting the SunEnterprise M4000/M5000 Single Platform Processor

{34618}
For the Clean Install of the SunFire Single Platform, refer to the procedure given in Chapter 2 of
the Installation and Conguration: OMC-R Clean Install (68P02901W47).Follow the procedures
excluding the following sections:
Creating the /.rhosts.equiv file.
Follow Procedure 12-41 to JumpStart the SunSparc Enterprise M4000/M5000.
Procedure 12-41
Platform Processor
JumpStarting the SunSparc Enterprise M4000/M5000 Single
Insert the Motorola JumpStart DVD in the DVD-ROM drive of the Single Platform
Processor.
Insert the latest Full System backup tape in the DAT drive of the Single Platform
Processor.
Enter the following command at the OK prompt, and press RETURN.

If auto-boot is set to false, the server does not start up automatically after power
on or reset.
setenv auto-boot? false
auto-boot? = false
Continued
12-72
68P02901W19-S
Oct 2009
Procedure 12-41 JumpStarting the SunSparc Enterprise M4000/M5000 Single

Platform Processor (Continued)
4
Enter the following command to reboot the server, and press RETURN.
reset-all
Resetting...
POST Sequence 01 CPU Check
LSB#02 (XSB#01-0): POST 2.3.0 (2008/
04/18 09:15)
POST Sequence 02 Banner
LSB#00 (XSB#00-0): POST 2.3.0 (2008/
04/18 09:15
POST Sequence 03 Fatal Check
POST Sequence 04 CPU Register
POST Sequence 05 STICK
POST Sequence 06 MMU
POST Sequence 07 Memory Initialize
POST Sequence 08 Memory
POST Sequence 09 Raw UE In Cache
POST Sequence 0A Floating Point Unit
POST Sequence 0B SC
POST Sequence 0C Cacheable Instruction
POST Sequence 0D Softint
POST Sequence 0E CPU Cross Call
POST Sequence 0F CMU-CH
POST Sequence 10 PCI-CH
POST Sequence 11 Master Device
POST Sequence 12 DSCP
POST Sequence 13 SC Check Before STICK Diag
POST Sequence 14 STICK Stop
POST Sequence 15 STICK Start
POST Sequence 16 Error CPU Check
POST Sequence 17 System Configuration
POST Sequence 18 System Status Check
POST Sequence 19 System Status Check After Sync
POST Sequence 1A OpenBoot Start...
POST Sequence Complete.
5dc04
Continued
68P02901W19-S
12-73
Oct 2009

Sun SPARC Enterprise M5000 Server, using Domain
console
Copyright 2008 Sun Microsystems, Inc. All
rights reserved.
5
At the OK> prompt, execute the following command:

boot cdrom -- restore
The system jump starts without any prompts and automatically restores the file
systems.
prtconf | grep pciex1214
Screen outputs similar to the following are displayed:
If the HSIP drivers are attached:

pciex1214,3350, instance #0
pciex1214,3350, instance #1
If the HSIP drivers are not attached:

pciex1214,3350, instance #0 (driver not attached)
pciex1214,3350, instance #1 (driver not attached)
Execute the following commands to attach the HSIP drivers as user root:
rem_drv HSIP
add_drv HSIP
7
The SunSparc Single Platform Processor then restores the full system backup
from the tape.
On completion the SunSparc returns with the console login.
Reboot the system to restart services by executing the following command as
user root:
Continued
12-74
68P02901W19-S
Oct 2009

8
If the NIS is used as the naming service, execute the following as root:
ypinit -m
To operate the NIS successfully, construct a list of the NIS servers.
Add one YP server name per line in the order of preference.
On completion, type <control D> or Return on a line by itself.
Next host to add:
Next host to add:mercia
Next host to add:
The current list of yp servers looks like this:mercia
Is this correct? [y/n: ] y
Installing the YP database requires answering a few questions.
Questions are asked at the beginning of the procedure.
Continued
68P02901W19-S
12-75
Oct 2009

Do you want this procedure to quit
on non-fatal errors? [y/n]: n
NOTE
Manually redo the failed steps to prevent system failure or YP
database failure.
The YP domain directory is /var/yp/omcadmin.
After the last query, the procedure takes 5 minutes to 10 minutes to complete.
Building /var/yp/omcadmin/ypservers...Running /var/
yp /Makefile...
updated passwd
updated group
updated hosts
updated ipnodes
updated ethers
updated networks
updated rpc
updated services
updated protocols
updated netgroup
updated bootparams
/var/yp/omcadmin/mail.aliases: 12 aliases, longest 10 bytes,
138bytes total
updated aliases
updated publickey
updated netid
updated netmasks
updated timezone
updated auto.master
updated auto.home
updated ageing
Continued
12-76
68P02901W19-S
Oct 2009
Restoring databases on the Single Platform Processor

updated auth_attr
updated exec_attr
updated prof_attr
updated user_attr
updated audit_user
If there are running slave YP servers, to recover from the database changes,
yppush
If there are no running slaves, on hosts to be slave servers, execute the following
command:
ypinit
9

svcadm clear svc:/system/basicreg:default
svcadm disable omc
10
After logging in, proceed to Restoring databases on the Single Platform

Processor on page 12-77.
Overview of restoring databases on page 12-77.
Preparing to restore the databases on page 12-78.
Taking databases offline and re-initializing INFORMIX on page 12-78.
Restoring the CM database on page 12-78.
Restoring the PM database on page 12-82.
Final Configuration Tasks on page 12-86.
Overview of restoring databases

A restoration of the INFORMIX databases must now be performed.
The restore option of the ontape utility is used to restore the complete database structure.
68P02901W19-S
12-77
Oct 2009
Preparing to restore the databases

Before starting the restore process, locate the following tapes:
The last monthly (level 0) backup.
The last weekly (level 1) backup, if it occurred after the last monthly backup.
The last daily (level 2) backup, if it occurred after the last weekly backup.
The databases are restored using the backup tapes in the order they were taken.
Taking databases offline and re-initializing INFORMIX

Before performing the restore from tape, both the PM and CM databases must be taken offline
and INFORMIX must be re-initialized. Use the following procedure:
Procedure 12-42
Taking databases offline and re-initializing INFORMIX
Log in to the Single Platform Processor as user informix.
Set up correct environment for the CM Database:

mib_env
Ensure that the IDS is in Offline mode:

svcadm disable t informix/cm
Set up correct environment for the PM Database:

omc_env

svcadm disable t informix/pm
Restoring the CM database

Use the following procedure to restore the CM database:
Procedure 12-43
Restore the CM database
Log in to the Single Platform Processor as user root and execute the
following commands:
/usr/omc/sbin/Initialize_Informix -CM

su informix
Continued
12-78
68P02901W19-S
Oct 2009
Procedure 12-43
Restore the CM database (Continued)
Set up correct environment:

mib_env

svcadm disable t informix/cm
As user Informix, execute the following command:

To restore from tape, enter the following command:

ontape r
The system displays the following message:
Please mount tape 1 on /dev/rmt/0 and press return to continue
Load the tape marked (CM database) Level 0 Backup into the Single
Platform Processor tape drive.
If more than one tape was used to back up the CM database, the system
prompts for further tapes to be entered in sequence.
Press the RETURN key to continue.
Output similar to the following example is displayed:

Archive Tape Information
Tape type:
Archive Backup Tape
Online version: Informix Dynamic Server
2000 Version 10.00.00 UC4
User
id: informix
Terminal id: /dev/pts/1

Archive
level: 0
Tape device: /dev/rmt/0

Tape
blocksize (in k): 64
Tape size (in k): 4000000

Tape
number in series: 1
Continued
68P02901W19-S
12-79
Oct 2009
Procedure 12-43
Spaces to restore:
1
[rootdbs]
2 [omc_db_plog]
3 [omc_db_llog]
4 [omc_db_sp1]
5 [omc_db_sp2]
6 [omc_db_sp3]
7 [omc_db_sp4]
8 [omc_db_sp5]
9 [omc_db_sp6]
Archive
Information Informix
Dynamic Server 2000 Copyright(C) 1986-1999 Informix Software, Inc

Initialization Time 01/17/2006 09:18:24
System Page Size 2048
Version 8
Archive CheckPoint Time 01/17/2006 13:04:21
Dbspaces
number
flags fchunk nchunks flags owner name

1
30001 1 1 N informix rootdbs
20001 2 1 N informix physdbs
20001 3 1 N informix logsdbs
2001 4 1 N T informix tempdbs
20001 5 1 N informix mib_db_sp1
Chunks chk/dbs
offset size free bpages flags pathname
1 1
2 921598 303981 PO- /dev/mib_db
2 2
2 78900 0 PO- /dev/mib_db_logs
3
3 78903 192000 7627 PO- /dev/mib_db_logs
4
4 921601 102399 102346 PO- /dev/mib_db
5
5 2 767998 767945 PO- /dev/mib_db1
Continue restore? (y/n)
Enter y to continue the restore.
Continued
12-80
68P02901W19-S
Oct 2009
Procedure 12-43
9
The following text is displayed:

Do you want to back up the logs? (y/n)
Enter n.
10

Restore a level 1 or 2 archive (y/n)
Enter n.
11
For a level 0 archive, or y for a level 1 or 2 archive. The following text is

displayed:
Do you want to restore log tapes? (y/n)
Enter n.
12

Program over.
13
In a separate login session, check the contents of online.log_MIB as follows:

tail -f /usr/informix/online.log_MIB
10:28:10 Checkpoint Completed: duration was 0 seconds.
Checkpoint loguniq 13, logpos 0x1309018
10:28:11 Physical
Restore of rootdbs, physdbs, logsdbs, mib_db_sp1 Completed.
10:28:11
Checkpoint Completed: duration was 0 seconds
10:28:11 Checkpoint
loguniq 13, logpos 0x1309018
10:30:10 Physical Recovery Started.
10:30:10
Physical Recovery Complete: 0 Pages Restored
10:30:10 Logical
Recovery Started.
10:30:10 10 recovery worker threads will be started.
10:30:13 Logical Recovery Complete.
0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks
10:30:14
Bringing system to Quiescent Mode with no Logical Restore.
10:30:15
Quiescent Mode
Press Ctrl-c to exit out of the tail -f command at any time.
Continued
68P02901W19-S
12-81
Oct 2009
Procedure 12-43
14
Remove the backup tape from the tape drive.
15
Once Quiescent Mode is displayed in the log, enter the following commands
as user informix to bring the CM database back online:
mib_env
onmode -m
svcadm enable informix/cm
Restoring the PM database

Use the following procedure to restore the PM database:
Procedure 12-44
Restore the PM database
Log in to the Single Platform Processor as user root and execute the
following:
/usr/omc/sbin/Initialize_Informix -PM

su informix
Set up correct environment:

omc_env

svcadm disable t informix/pm
As user Informix, execute the following command:

To restore from tape, enter the following command:

ontape r
The system displays the following message:
Please mount tape 1 on /dev/rmt/0 and press return to continue
Load the tape marked (PM database) Level 0 Backup into the Single
Platform Processor tape drive.
If more than one tape was used to back up the PM database, the system
prompts for further tapes to be entered in sequence.
Press the RETURN key to continue.

Archive Tape Information
Tape type:
Archive Backup Tape
Online version: Informix Dynamic Server
2000 Version 10.00.00 UC4
Continued
12-82
68P02901W19-S
Oct 2009
Procedure 12-44
Restore the PM database (Continued)
Archive date: Thu Jan 17 12:24:13 2006

User
id: informix
Terminal id: /dev/pts/1

Archive
level: 0
Tape device: /dev/rmt/0

Tape
blocksize (in k): 64
Tape size (in k): 4000000

Tape
number in series: 1
Spaces to restore:
1
[rootdbs]
[omc_db_plog]
[omc_db_llog]
[omc_db_sp1]
[omc_db_sp2]
[omc_db_sp3]
[omc_db_sp4]
[omc_db_sp5]
[omc_db_sp6]
Archive Information
Informix
Dynamic Server 2000 Copyright(C) 1986-1999 Informix Software, Inc.
Initialization
Time 01/17/2006 09:18:24
System Page Size 2048
Version 8
Archive CheckPoint Time 01/17/2006 12:24:16
Dbspaces
number
flags fchunk nchunks flags owner name
1 30001 1 1 N informix rootdbs
2 20001 2 1 N informix omc_db_plog
3 20001 3 1 N informix omc_db_llog
4 20001 4 1 N informix omc_db_sp1
Continued
68P02901W19-S
12-83
Oct 2009
Procedure 12-44
10 2001 10 1 N T informix omc_db_temp

Chunks
chk/dbs offset size free bpages flags
pathname
1 1 2 307198 295554 PO/dev/omc_db_root
2 2 2 127000 0
PO- /dev/omc_db_logs
3 3 127003 396800 12747
PO- /dev/omc_db_logs
4 4 2 1024098
241186 PO- /dev/omc_db1
5 5 2 1024098
6 6 2 1023998
7 7 2 1023998
8 8 2 1023998
9 9 2 1023998
10 10 2 1023998
1023945 PO- /dev/omc_db_temp
Continue restore? (y/n)
Enter y to continue the restore.
9

Do you want to back up the logs? (y/n)
Enter n.
10

Restore a level 1 archive (y/n)
Enter n.
Continued
12-84
68P02901W19-S
Oct 2009
Procedure 12-44
11
For a level 0 archive, or y for a level 1 or 2 archive. The following text is

displayed:
Do you want to restore log tapes? (y/n)
Enter n.
Program over
12
In a separate login session, check the contents of the online.log_OMC as

follows:
tail -f /usr/informix/online.log_OMC
10:36:47 Checkpoint Completed: duration was 0 seconds.
10:36:47
Checkpoint loguniq 13, logpos 0x469018
10:39:14 Physical
Recovery Started.
10:39:14 Physical Recovery Complete: 0 Pages
Restored.
10:39:14 Logical Recovery Started.
10:39:14
10 recovery worker threads will be started.
10:39:18 Logical
Recovery Complete.
0 Committed, 0 Rolled Back, 0
Open, 0 Bad Locks
10:39:19 Bringing system to Quiescent Mode
with no Logical Restore.
10:39:20 Quiescent Mode
Press Ctrl-c to exit out of the tail -f command at any time.
68P02901W19-S
13
Remove the backup tape from the tape drive.
14
Once Quiescent Mode is displayed in the log, enter the following commands
as user informix to bring the PM database back online:
omc_env
onmode -m
svcadm enable informix/pm
12-85
Oct 2009
Restoring GUI Server file systems using ufsrestore utility
Final Configuration Tasks

When the databases are fully restored, perform the following commands:
Procedure 12-45
Final Configuration Tasks
Log in as user root.
Execute the omc_db_maint utility as follows:

$OMC_TOP/current/sbin/omc_db_maint:
more $OMC_TOP/logs/omc_db_maint.<yy><mm><dd>
Where <yy>refers to the current year,<mm>to the current month, and
<dd> to the current day in this month.
As user omcadmin, execute the following command:

svcadm enable omc
At this stage the Single Platform Processor has been restored.
Overview to restoring GUI Server file systems using ufsrestore utility on page 12-86.
JumpStarting the GUI Server Processor on page 12-87.
Overview of restoring the GUI Server file system on page 12-93.
Restoring root (/) file system on page 12-94.
Restoring /usr/omc file system on page 12-96.
Restoring /omcgen file system on page 12-96.
Rebooting the GUI Server on page 12-97.
Overview to restoring GUI Server file systems using ufsrestore utility

The data that has been stored on backup tapes can be restored on a brand new set of disks
for disks that have become corrupt.
CAUTION
The procedure destroys any data on the disks and overwrites the disks with data
from the backup tape.
Before commencing the restore procedure, make sure that a copy of the most recent set
of complete file system level 0 backup tapes created using backup_MMI, is available for the
processor being restored.
12-86
68P02901W19-S
Oct 2009
This procedure uses, as an example, a Sunblade 150 GUI Server, with the following file systems:
/
/omcgen
/usr/omc
JumpStarting the GUI Server Processor

Procedure 12-46
Jumpstart a GUI Server
Insert the GSR9 DVD in the DVD-ROM drive of the GUI Server.
From the ok prompt, enter the following command to perform a hands-free

installation of Solaris 10 and all StorEdge Enterprise products on the GUI
Server:
boot cdrom
The following is sample output that can be expected during the install.
When the boot command is entered, screen output similar to the following
is displayed:
Motorola GSM OMC-R GUI Server Installation
==========================================
Now you will be prompted to enter information to customise
your GSM OMC-R GUI Server. It is essential that you provide
correct answers to all of the following questions.
An incorrect answer may very likely cause problems. Refer to
your install documentation if you are not sure which values to supply for
any of the questions
The default response (where one is provided) is in square brackets ([]).
If a default response exists, you can accept it by pressing the
ENTER key.
After the install questions have completed, you will have a
chance to approve or change your settings.
Once the settings have been approved, the system will be wiped and
installed from scratch.
Press -=ENTER=- to continue
Press Enter to continue.
Continued
68P02901W19-S
12-87
Oct 2009
Procedure 12-46
4
Jumpstart a GUI Server (Continued)
A prompt is displayed requiring the hostname to be entered.

Screen output similar to the following appears:
==========================================
Primary Interface Configuration
Your GSM OMC-R GUI Server needs to have a primary interface name
(hostname) that should be set to the name that your GSM OMC-R GUI Server
will be known as on your local LAN
Enter the GSM OMC-R GUI Servers primary hostname:
Enter the hostname.
NOTE
A host name must be of at least two characters. It can contain
letters, digits and minus signs (-). Letters must be lower case.
Illegal characters are: !$%^&*(){}~@?>:<|.[]_.
5
A prompt is displayed requiring the IP address to be entered.

Your GSM OMC-R GUI Server needs to have an IP address
associated with the primary hostname. This should be set
to the IP address that your GSM OMC-R GUI Server will be
known as on your local LAN.
Enter the GSM OMC-R GUI Servers IP address:
Enter the IP address.
A prompt is displayed requiring the Netmask address to be entered.

Your GSM OMC-R GUI Server needs to have a netmask associated
with the primary IP address.
This should be set to the netmask that your GSM OMC-R GUI Server will
on your local LAN.
Example: 255.255.255.0
Enter the GSM OMC-R GUI Servers netmask:
Enter the Netmask address.
Continued
12-88
68P02901W19-S
Oct 2009
Procedure 12-46
7
A prompt is displayed that gives an option to configure a Default Router.

==========================================
Default Router Configuration
Your GSM OMC-R GUI Server will need a default router to access any local
LAN network devices that do not reside on any local subnets it is
connected to
This should be the address of the router on your local LAN.
Contact your system administrator for help
Do you want to configure a default router? (y/n) [y]: y
If a default router is to be configured, press Enter and the following prompt
is displayed:
Enter the default routers IP address:
Enter the default routers IP address.
If a default router is not required, type n and then press Enter. The
installation then proceeds to configure DNS.
A prompt is displayed that gives an option to configure DNS.

DNS Configuration
Your GSM OMC-R GUI Server will need to have DNS configured to use
hostnames to access your LAN network devices rather than using
their IP addresses.
Contact your system administrator for help.
Do you want to configure DNS? (y/n) [n]: n
If DNS is not required, press Enter. The installation will then continue to
configure a timeserver.
If DNS is to be configured, enter y.

The user is prompted to enter the DNS Domain name and DNS server IP
addresses. After each prompt, enter the requested value:
Enter the Common Platform GSM OMCRs domain:
Enter the LAN primary DNS server IP address:
Enter the LAN secondary DNS server IP address:
Enter the LAN tertiary DNS server IP address:
If you are configuring DNS, it is necessary to type in the Domain name and
to supply a primary DNS IP address.
Continued
68P02901W19-S
12-89
Oct 2009
Procedure 12-46
10
A prompt is displayed that gives an option to configure a timeserver.

==========================================
Timeserver Configuration
Your GSM OMC-R GUI Server can use a ntp timeserver on your local LAN
to sync the time with the rest of your network
You can enter an IP address or a name of a timeserver to use on your
network. However, if you specify a name, you must either have configured
DNS or you must add an entry to /etc/inet/hosts for your timeserver.
Do you want to configure a timeserver? (y/n) [n]: n
If a timeserver is to be configured, enter y. The following message is
displayed:
Enter the timeservers name or IP address:
Enter the timeserver name or IP address.
If there is no timeserver to be configured, press Enter, and the installation
continues to configure the NIS Domain name.
11
A prompt is displayed to enter the NIS Domain.

==========================================
NIS domain setup
Your GSM OMC-R GUI Server requires Network Information Services (NIS)
The NIS domain is a character string e.g. omcadmin
Enter the NIS domain name: omcadmin
Enter the NIS Domain name.
12
A prompt is displayed requiring OMC-R server information:

==========================================
OMC-R Server Configuration
Your GSM OMC-R GUI Server must be connected to an OMC-R server.
Enter the OMC-R server hostname: <server_hostname>
Enter the OMC-R server IP address: <server_ip_address>
Continued
12-90
68P02901W19-S
Oct 2009
to be enab
Procedure 12-46
13
A prompt is displayed requiring Printer information:

==========================================
Printer Configuration
Your GSM OMC-R GUI Server may have a printer attached.
You can configure a printer at this time or later.
Contact your system administrator for help.
Do you want to configure a printer?: n
14
A prompt is displayed to configure a timezone.

==========================================
Timezone Configuration
Your Sun-Based GSM OMC-R GUI Server will need to have a timezone
configured.
US/Eastern US/Central US/Mountain US/Pacific Japan
Enter the GSM OMC-R GUI Servers timezone:
Type y and press Enter to get a list of timezones.
Press the space bar to navigate this list.
Australia/ACT
Australia/Broken_Hill
.
.
.
Australia/West
Brazil/Acre
Brazil/DeNoronha
Brazil/East
Brazil/West
Canada/Atlantic
If your timezone is known, press Enter and type in the timezone.
Enter the Common Platform GSM OMCRs timezone:
Continued
68P02901W19-S
12-91
Oct 2009
Procedure 12-46
15
A summary of all of the values entered is presented. Screen output similar

to the following is displayed:
Motorola GSM OMC-R GUI Server Installation Configuration - Summary
===================================================================
Primary Interface Printer
------------------------HOSTNAME: somc5 Install printer?: n
IP: 175.33.44.111
NETMASK: 255.255.255.0
SPLAT_NAME: somc57
SPLAT_IP: 175.3.44.4
Networking
---------Default Router: 175.3.44.84 Domain:
NIS domain: omcadmin
DNS TIME
-----
Primary: TIMESERVER:
Secondary: TIMEZONE: Eire
Tertiary:
Would you like to make changes to the above values? (y/n) [n]
If all of the values are correct, press Enter to accept.
However, if a value needs to be modified, type y and press Enter.
Press Return to step through all the configuration values that have been
entered from point 4 onwards. These values will be in square brackets. Type
in any updated values as necessary.
16
The password configuration prompt appears next.

Enter and confirm the passwords for the users when prompted.
Motorola Common Platform GSM OMCR GUI Server Installation - Password
Configuration
==========================================
The system will now prompt you for passwords for the following users:
root
Enter roots password:
Re-Enter roots password:
Continued
12-92
68P02901W19-S
Oct 2009
Procedure 12-46
17
The final prompt gives the option to enable the Network Services.
Motorola GSM OMC-R GUI Server Installation - Network Services
Configuration
==========================================
This GSM OMC-R GUI Server can take advantage of advanced network services
during this installation.
This GSM OMC-R GUI Server will need to be connected to the network
via the eri0
interface and it will be configured using the following information
IP: 175.3.44.227
NETMASK: 255.255.255.0
Would you like to enable network services? (y/n) [n]: n
Note: Entering y enables debugging mode.
The log files for this section can be found in /var/install/logs.
The GUI Processor reboots automatically.
Overview of restoring the GUI Server file system

The following procedures assume that /(root)/usr/omc and /omcgen are the only file systems
being restored. Refer to the backup_MMI <datestamp> log file for the particular system. If
extra file systems are to be restored, continue with a similar format as below for restoring
these file systems.
A GUI Server complete filesystem restore may be performed from the tape drive attached locally
to the GUI Server or from a tape drive attached to the Single Platform Processor. The following
procedure describes how to perform a complete GUI Server filesystem restore using the tape
drive in the Single Platform Processor. Use the following procedure to prepare for the restore:
Procedure 12-47
Prepare for the restore
Load the most recent level 0 backup tape for this GUI Server processor into
the tape drive that will be used to perform the restore (that is, the GUI
Servers tape drive or the Single Platform Processor tape drive.
If you are using the tape drive on the GUI Server Processor then, as user
root on the GUI Server processor, ensure that the tape is rewound to the
beginning by entering the following command:
mt -f /dev/rmt/0 rew
If you are using the tape drive on the Single Platform Processor then, as
user root on the Single Platform Processor, ensure that the tape is rewound
to the beginning by entering the following command:
mt f /dev/rmt/0 rew
Continued
68P02901W19-S
12-93
Oct 2009
Procedure 12-47
Prepare for the restore (Continued)
As user root, execute the following command on the GUI Server:

/var/install/bin/check_link
Your system administrator can inform you if you need to force a full duplex
link.
Retrieve the order in which the filesystems were backed up from the table in
the Procedure for backing up file systems using backup_MMI utility
section of this guide.
Restoring root (/) file system

Use the following procedure to restore the first volume on the tape (/ file system).
All warnings regarding the files already existing and those related to being unable to create soft
links, can be ignored. Follow Procedure 12-48 if you are using a local tape drive, that is, a tape
drive on the GUI Server. As the / file system has already been restored during the GUI server
jumpstart, only customizations are restored.
Procedure 12-48
Restoring the first volume on the tape (/ file system)
Execute the
cd /
ufsrestore
ufsrestore
ufsrestore
ufsrestore
ufsrestore
ufsrestore
following commands:
if /dev/rmt/0n
> add /etc/inet/*
> add /etc/hosts.equiv
> add /etc/ssh
> add /etc/mail/sendmail.cf
> extract
You have not read any volumes yet.

Unless you know which volume your file(s) are on you should
start with the last volume and work towards the first.
Specify next volume #:
When the following prompt is displayed, enter 1.
Specify next volume #:
2

Directories already exist, set mode anyway? [yn]
Enter y.
Continued
12-94
68P02901W19-S
Oct 2009
Procedure 12-48
3
Restoring the first volume on the tape (/ file system) (Continued)

set owner / mode for .? [yn]
Enter y. The following error can be safely ignored:
Cannot set directory permissions: Operation not applicable

Cannot set directory ownership: Operation not applicable
Then quit to exit.
Follow Procedure 12-49 if you are using a tape drive located on the Single Platform Processor
and the tape drive is used for backup. As the / file system has already been restored during
the GUI server jumpstart, only customizations are restored. Additional extractions can be
configured as part of this procedure. If prompted for a password, enter the root password of
the Single Platform Processor.
Procedure 12-49
Using a tape drive located on the Single Platform Processor
Execute the following commands:

cd /
ssh <splat_ip_address> dd if=/dev/rmt/0n | ufsrestore if where <splat_ip_addr> is the IP Address of the Single Platform Processor.
ufsrestore
ufsrestore
ufsrestore
ufsrestore
ufsrestore
>
>
>
>
>
add /etc/inet/*
add /etc/hosts.equiv
add /etc/ssh
add /etc/mail/sendmail.cf
extract

set owner / mode for .? [yn]
Enter y.

Directories already exist, set mode anyway? [yn]
Enter y.
The following error can be safely ignored:
Cannot set directory permissions: Operation not applicable
Cannot set directory ownership: Operation not applicable
68P02901W19-S

ufsrestore > quit
12-95
Oct 2009
Restoring /omcgen file system

All warnings regarding files already existing and those related to being unable to create soft
links, can be safely ignored.
Follow Procedure 12-50 if you are using a local tape drive, that is, a tape drive on the GUI
Server.
Procedure 12-50
Using a local tape drive

cd /omcgen
ufsrestore rf /dev/rmt/0n
Follow Procedure 12-51 if you are using a tape drive on the Single Platform Processor and
the tape drive is used for backup. If prompted for a password, enter the root password of
Procedure 12-51
Using the Single Platform Processor

cd /omcgen
ssh <splat_ip_address> dd if=/dev/rmt/0n | ufsrestore rf
rm restoresymtable
Where <splat_ip_addr> is the IP Address of the Single Platform Processor.
Restoring /usr/omc file system

All warnings regarding the files already existing and those related to being unable to create soft
links, can be safely ignored. Follow Procedure 12-52 if you are using a local tape drive, that
is, a tape drive on the GUI Server.
Procedure 12-52
Restoring /usr/omc file system

cd /usr/omc
ufsrestore rf /dev/rmt/0n
rm restoresymtable
Follow Procedure 12-53 if you are using a tape drive on the Single Platform Processor and
the tape drive is used for backup. If prompted for a password, enter the root password of
12-96
68P02901W19-S
Oct 2009
Procedure 12-53
Selective File restore using restore_splat
Using the Single Platform Processor

cd /usr/omc
ssh <splat_ip_address> dd if=/dev/rmt/0n | ufsrestore rf
rm restoresymtable
where <splat_ip_addr> is the IP Address of the Single Platform Processor.
Rebooting the GUI Server

Reboot the GUI Server by entering the following command as user root:

This utility enables selective restore of data from any Single Platform Processor file system that
has been stored on a backup tape. Before commencing the restore procedure, ensure that a
copy of the most recent set of Single Platform Processor complete file system level 0 backup
tapes (created using the backup_splat utility) is available. Use the following procedure to
perform a selective restore:
Procedure 12-54
1
Perform a selective restore
As user root, execute the following commands:

mt -f /dev/rmt/0 rewind
tar xf /dev/rmt/0 /tmp/restore_splat
Rewinding Tape ... Please Wait
Ufs directory number
1 File System to restore /home
2 File System to restore /solbak
3 File System to restore /omcgen
4 File System to restore /usr/omc
Continued
68P02901W19-S
12-97
Oct 2009
Procedure 12-54
Perform a selective restore (Continued)
5 File System to restore /usr/omc/ne_data

6 File System to restore /usr/omc/ne_data/raw_stats
Please enter the corresponding number of the
File System you wish to restore
2
Select the file system you wish to restore and press RETURN. Screen output
similar to the following is displayed:
Recovering
12-98
/home ... Please Wait
Warning:
./lost and found: File exists
Warning:
./omcadmin: File exists
Warning:
./omcread: File exist
68P02901W19-S
Oct 2009
Chapter
13
Troubleshooting
68P02901W19-S
Oct 2009
13-1
Overview
Overview
13-2
Assessing a problem on page 13-3.
Core file generation on page 13-6.
OMC-R system information on page 13-8.
Full file systems on page 13-21.
File access problems on page 13-24.
OMC-R software process errors on page 13-25.
Resetting boot devices on page 13-28.
Common Desktop Environment problems on page 13-33.
CDE login failure on page 13-36.
Troubleshooting the LAN on page 13-37.
X.25 failure on page 13-39.
Moving a machine with a forced link speed on page 13-41.
Logical Vol Mgr troubleshooting on page 13-42.
Replacing hard disk on system processor Sunfire/Netra 440/Netra 20 on page 13-43.
Checking disk mirroring on page 13-47.
Device busy error on page 13-49.
Ejecting DVD-ROMs on page 13-50.
StorEdge Enterprise Backup problems on page 13-51.
Database failure on page 13-52.
Onperf utilities on page 13-53.
Checking and recovering database tables on page 13-70.
Alarms on page 13-78.
Setting FM audit and disk usage limits on page 13-88.
Using neighbor statistics on page 13-91.
Power failure on page 13-97.
Checking the system processor hardware on page 13-99.
Configuring a Timeserver on page 13-102.

68P02901W19-S
Oct 2009
Assessing a problem
Assessing a problem
Overview of troubleshooting
This chapter provides details regarding the resolution of problems in specific areas. Each
description includes a procedure that identifies the specific problem, and if possible, provides
a solution.
Contacting Motorola
In the event of a support requirement, contact the local Customer Network Resolution Centre
with the information requested in the checklist that follows.
When contacting the Customer Network Resolution Centre at the end of a problem diagnosis,
ensure that the information acquired is collated before telephoning the support personnel.
Preliminary checklist
Ensure that the following information is readily available when contacting the local Motorola
support centre:
Operator name.
Date and time of fault.
Problem title (a one-line description of the problem).
What task the operator was doing up to 30 minutes before the fault occurred.
Details of the BSS circumstances at the time of the problem, including the call scenario at
the time of the fault. For example:
A called B; B dropped.
Location of B.
The load details on the BSS at the time of the fault.
Any software fault management events.
Any event log details produced.
Details of database access at the time of the fault.
A printout of any GUI displays.
68P02901W19-S
13-3
Oct 2009
Preliminary checklist
The BSS software version.

System configuration details.
Detailed description of the problem, including the following OMC-R details:

Any error messages.
System configuration details.
Note the processor and component (or area) of the system affected. This can be
determined from the audit log or the GUI menu option that was being used when the
problem occurred. Keep a printout of relevant parts of the audit log file and the IPC
log files (where appropriate).
The OMC-R software version.
Details of a core dump file, if one has been produced. This should be archived to
tape and sent to Motorola.
Fault severity, categorized as follows:
Service affected - indicates that the problem impacts the critical functionality of the
system. For example, problems with the event manager or X.25 fall into this category.
Serious - indicates that a major portion of system functionality is affected, but the
fault does not prevent the system from meeting its primary requirements.
Annoying - indicates a problem that may affect operations by being an inconvenience
or producing misleading or redundant outputs.
Cosmetic - indicates fault correction is required to ensure that the software conforms
to certain standards. Does not affect the day-to-day running capabilities of the
OMC-R software.
Urgency of response required:

Immediate.
As soon as possible.
Next software release.
In a future software release.
13-4
68P02901W19-S
Oct 2009
General problem descriptions
General problem descriptions

The following incidents can interrupt or halt the operation of the OMC-R system:
OMC-R software application halt

The OMC-R software applications can stop working as a result of detecting an internal
error. The error message must be identified, and the area of the system affected must be
located and the remedial action, such as an OMC-R stop/start, must be taken.
Network Element (NE) connection failure

Connections between the OMC-R and the NEs can fail intermittently or permanently. Such
failures can be caused by hardware malfunction, X.25 software, network connections (for
example, packet switch), or misuse of GUI command procedures.
Operating system halt (panic)

If the UNIX operating system on any of the processors detects an internal error, it can stop
processing. This is known as a panic condition, usually causing the affected processor to
reboot. In some cases, the whole OMC-R system must be restarted and a core dump taken.
Hardware failures
A hardware failure on one of the SPARC processors is likely to stop that processor
functioning.
Power failures
An ac power failure causes the OMC-R processors to reboot when the power is restored.
Uninterruptible Power Supplies (UPSs) could be used to power all the OMC-R hardware
components, thus providing some tolerance to power failures.
Further troubleshooting information can be found in the manual OMC-R Online Help, Network
Operation.
68P02901W19-S
13-5
Oct 2009
Core file generation
Core file generation
Overview of generating core files

The gcore command provides a core image of a running process. It may be necessary to invoke
this command in order to troubleshoot the OMC-R system problems and also produce a core
dump of the system processor kernel so that this information can be analyzed by Motorola.
Application core dumps

If a fatal error occurs during the operation of either the application programs or the GUI
modules, the respective programs will terminate and create a memory dump, core, in the
following directory:
$OMC_TOP/logs
Retrieve the memory dumps and return them to Motorola for analysis.
Generating a core of an OMC-R process

The gcore command has the following syntax:
gcore -o <filename> <process_id>
where <filename> is the file name and <process_id> is the process id of the OMC-R process
for which the core file is generated.
Operating system core dumps

If a fatal error occurs within the operating system of the system processor, a memory dump is
written on the dump partition of the system disk. After reboot, the savecore utility copies it to
the /var/adm/crash directory. The memory dump files (core.n) and Operating System (OS)
name list (unix.n) should be archived to tape and removed from the disk as soon as possible.
The parameter n increases each time the savecore utility is run, and is the same value for
both the files.
core_presence utility
The core_presence utility checks for the occurrence of a core file on the system processor. If a
core file is found, the user omcadmin is mailed.
13-6
68P02901W19-S
Oct 2009
Checking core dumps
Checking core dumps

Use the following procedure to check core dumps. Copy the checklist provided in Table 14-9
Procedure 13-1
68P02901W19-S
Checking core dumps
Check the presence of a core file when a fatal error occurs during the
operation of either the application programs or the GUI modules.
cd /usr/omc/logs/usrauditlogs
ls -l core*
A core file should exist at the exact time that the fatal error occurred
and should be in compressed format.
If an OMC-R process is causing severe problems, generate a core file

of the process. As user root, execute the following commands:
Where <filename> and <process_id> are the file name and process
ID of that particular OMC-R process.
The output from the gcore command indicates the name and location
of the core file.
If the system processor has any kernel problems, contact Sun support
for instructions on how to address them.
If core files are not required, remove them as they can consume large
amounts of disk space.
13-7
Oct 2009
OMC-R system information
OMC-R system information
Obtaining system information

When a problem occurs on the OMC-R, information can be retrieved from the log files stored in
the /usr/omc/logs and the /usr/omc/logs/sys_info directories. The commands described in
this section are used to access the information contained in the sys_info files.
Additionally, the systat script can be used to create a file that reflects the status of the system,
showing system up time, process list, disk status, system activity and system swap areas used
by the memory manager.
OMC-R log files

The log files stored in /usr/omc/logs/sys_info directories are generated every 10 minutes on
the system processor. Examining these files can determine whether specified processes are
running and can reveal the behavior of the system.
The sys_info files have the following naming convention:
statmmddhhxx.Z
Where:
is:
mm
the month.
dd
the day of that month.
hh
the hour.
xx
the minute the file was generated.
System uptime
The following command shows how long the system has been up:
/usr/ucb/uptime
In response to this command, an output similar to the following example is displayed:
1:28pm up 2day(s), 3:16 7 users
load average: 0.03, 0.054, 0.05
13-8
68P02901W19-S
Oct 2009
Machine architecture
Machine architecture
The following command gives the details of the machine architecture:
uname
In response to this command, an output similar to the following example is issued:
SunOS
The following command:
uname -a
produces a more detailed response, as follows:
SunOS somc57 5.9 Generic_118558-02 sun4u sparc SUNW,Ultra-Enterprise
Current processes
The following command gives the information about what processes are running:
/bin/ps -elf | more
Output is displayed in columns, each column having a column heading, the meaning of which
is explained in Table 13-1.
Table 13-1
Output from ps -elf command

Meaning
Column heading
F
Flags associated with the process.
The state of the process.
UID
The login name of the process owner.
PID
Process id of the process.
PPID
C
The process id of the parent process.

Processor utilization for scheduling.
PRI
The priority of the process. Higher number means lower priority.
NI
Nice value, used in priority computation.
ADDR
SZ
Memory address of the process.

Size of the swappable processes image in main memory.
Continued
68P02901W19-S
13-9
Oct 2009
State of the file systems
Table 13-1
Output from ps -elf command (Continued)

Meaning
Column heading
WCHAN
The address of an event for which a process is sleeping.
STIME
Starting time of the process given in hours, minutes and seconds. If

process at the time of executing the ps command has been running for
more than 24 hours, STIME is given in months and days.
TTY
The controlling terminal of the process. The message is printed when

there is no controlling terminal.
TIME
The cumulative execution time of the process.
CMD
The full command name and its arguments.
State of the file systems

In any system, it is necessary to take note of the state of the file systems. This information is
recorded in the sys_info files using the output of the /bin/df -k command. Sample output is
as follows:
/bin/df -k
Filesystem
/dev/md/dsk/d0
kbytes
used
10152430 3099747
avail capacity
6951159
31%
Mounted on
/
/proc
0%
/proc
mnttab
0%
/etc/mnttab
fd
0%
/dev/fd
swap
5364032
96
5363936
1%
/var/run
swap
5364384
448
5363936
1%
/tmp
13966 11770250
/dev/md/dsk/d10
11903248
1%
/home
/dev/md/dsk/d15
8051300
8892
7961895
1%
/solbak
/dev/md/dsk/d20
7056714
7025
6979122
1%
/omcgen
561066
/dev/md/dsk/d25
6049124
5427567
10%
/dev/md/dsk/d30
16533099
66910 16300859
1%
/usr/omc
/usr/omc/ne_data
/dev/md/dsk/d35
11391149
11326 11265912
1%
Quite often when the file systems are full, there are problems with the OMC-R, whereby
functionality may be affected. If the file systems are filling up, it is necessary to purge unwanted
files.
Integrity of X.25 communications

For the system to work correctly and to ensure proper communication between the devices, it is
necessary to ensure the integrity of X.25. This is done by executing the following command as
user root:
The /opt/SUNWconn/bin/x25stat file shows the statistics for the X.25 port for which it is run.
13-10
68P02901W19-S
Oct 2009
Network status
Network status
The following command is run to provide information on the network status:
/usr/bin/netstat -a | more
The following is an example of the output from this command:
UDP: IPv4
Local Address
Remote Address
State
-------------- -------------------- ------Idle
*.*
Idle
*.32775
Idle
Idle
Idle
*.32777
*.32781
Idle
Idle
Idle
Idle
*.32791
*.lockd
*.syslog
Idle
*.ntp
Idle
*.32792
Idle localhost.ntp
Idle somc57.ntp
*.32794
Idle
Idle
Unbound
*.*
*.*
Unbound
Idle
*.32801
Idle
*.32797
*.7938
Idle
Idle
*.177
Idle
Idle
*.32841
Idle
*.*
*.
*.*
*.32790
Idle
Idle
*.32776
Idle
Unbound
*.32771
*.1023
*.1022
32789
*.sunrpc
Unbound
*.nfsd
*.8937
dle
*.32847
*.*
Unbound UDP: IPv6
Unbound
Local Address
Remote Address
State
If
------- --------------------------------- ---------- ----177
Idle
Local Address
Recv-Q
Remote Address
*.*
*.sunrpc
68P02901W19-S
TCP: IPv4
Swind Send-Q Rwind
State----------- ----- ------ ----- ------
------.*
*.
0
0
0 49152
0 49152
0 49152
0 IDLE
0 IDLE
0 LISTEN
*.1023
0 49152
0 BOUND
*.32771
0 49152
0 LISTEN
*.32772
0 49152
0 LISTEN
*.32773
13-11
Oct 2009
System resources
0 49152
0 LISTEN
*.32774
0 49152
0 LISTEN
*.dtspc
0 49152
0 LISTEN
*.32778
0 49152
0 LISTEN
*.32782
0 49152
0 LISTEN
*.32786
0 49152
0 LISTEN
*.printer
0 49152
0 LISTEN
*.shell
*.shell
0 49152
0 LISTEN
*.* 0
0 49152
0 LISTEN
The local address is machinename.ipc_channel specified in the ipc.cfg file.

The /usr/omc/current/config/ipc.cfg file gives the channel number used by OMC-R processes
needed to communicate externally to the machine on which the processes are stored.
The column state shows what condition the connection is in.
In the OMC-R, some processes may need to communicate with processes outside of their own
machine. This can be done using the ipc command.
System resources
The following command gives useful information regarding the amount of available free memory
and also gives an indication of how busy the machine is.
/usr/bin/sar -ru | more
This command sends its output to the sys_info file.
13-12
68P02901W19-S
Oct 2009
System resources
Sample output is as follows:

SunOS somc57 5.9 Generic_118558-02 sun4u
04/08/2005 00:00:00 freemem
freeswap 00:20:00
118510
10734392 00:40:00 118443

10734170 01:00:00
118442
10734271 01:20:00 118422

10733998 01:40:00
118413
10734157 02:00:00 118412

10734188 02:20:00
118401
10734049 02:40:00 118379

10734015 03:00:00
118370
10733974 03:20:00 118365

10733922 03:40:00
118353
10733975 04:00:00 118342

10733986 04:20:00
118841
10737609 04:40:00 118304

10733643 05:00:00
118296
10733653 05:20:00 118200

10733568 05:40:00
118185
10733548 06:00:00 118179

10733589 06:20:00
118160
10733495 06:40:00 117957

10731470 07:00:00
118008
10732557 07:20:00 118041

10733015 07:40:00
118017
10732776 08:00:00 118011

10732811 08:20:00
118004
10732808 08:40:00 117986

10732692 09:00:00
10731795 Average
10733635 00:00:00
68P02901W19-S
117919
118258
%usr
13-13
Oct 2009
Swap space
%sys
%wio
%idle 00:20:00
99 00:40:00
99 01:00:00
99 01:20:00
99 01:40:00
99 02:00:00
99 02:20:00
0
0
0
0
99 02:40:00
0
99 03:00:00
98 03:20:00
99 03:40:00
99 04:00:00
99 04:20:00
95 04:40:00
0
0
99 05:00:00
0
0
99 05:20:00
0
99 05:40:00
99 06:00:00
99 06:20:00
99 06:40:00
98 07:00:00
99 07:20:00
99 07:40:00
99 08:00:00
99 08:20:00
99
Swap space
The following command gives information regarding swap space:
# /etc/swap -l
swapfile
dev
free /dev/md/dsk/d5
swaplo blocks
85,5
16 9244784 9244784
PM database status
The following commands provide information on the status of the PM database and should be
executed as user Informix:
omc_env
13-14
68P02901W19-S
Oct 2009
PM database status
onstat -ukp | more

IBM Informix Dynamic server Version
9.40.UC4
-- On-Line -- Up 04:58:21
-- 467968 Kbytes Userthreads address

flags
sessid
locks nreads
1
user
tty
wait
tout
nwrites 24a67018 ---P--D
root
75
70 24a67630 ---P--F 0
root
903 24a67c48 ---
P--F 0
root
723 24a68260 ---P--F 0
---P--F 0
0
root
0
root
69 24a68878
0 24a68e90 ---P--F 0
-
---P--F 0
0 24a69ac0 ---P--- 11
12
root
0
-
2539e608 0
1
27
0 24a6bf50 Y--P--- 81
omcadmin console
254f08c8 0
254e8328 0
Y--P--- 83
omcadmin
1
0 24a6cb80
0 24a6d198 Y--P--- 84
2551b918 0
0 24a6d7b0 Y--P--- 85
25525430 0
24a6ddc8 Y--P--- 86
68P02901W19-S
omcadmin console
1
omcadmin console
omcadmin -
252ac928 0
0 24a6c568 Y--P--- 82
0 24a6b938 Y--P---
omcadmin console
254e8e20 0
31
root
79
console
omcadmin console
24a6b320 ---P--D 15
0
0
-
omcadmin
1
24a6ad08 Y--P--- 80
254bcd18 0
0
root
0 24a6a0d8 ---P--B
0 24a6a6f0 Y--P--- 10
console
0 24a694a8
0
root
root
omcadmin -
0
25525f28
13-15
Oct 2009
PM database status
10
0 24a6e3e0 Y--P--- 87
omcadmin console
0
255aaa30 0
0 24a6e9f8 Y--P--- 88
255f8640 0
omcadmin -
0 24a6f010 Y--P--- 89
25615120 0
24a6f628 Y--P--- 78
25615ed80
console
omcadmin console
0
Y--P--- 91
0
omcadmin -
0 24a6fc40
omcadmin console
0
2563fbc0
0 24a70258 Y--P--- 92
25686728 0
omcadmin
0 25 active,
128 total, 26 maximum concurrent Locks address

wtlist
owner
lklist
type
key#/bsiz a110f98 0
HDR+S
100002
204
0
S
100002
24a6ddc8 0
a42fcb8 0
100002
204
24a6d198 0
204
24a6e9f8
0
a42cdcc
100002
204
100002
24a6f628 0
0
100002
a417a84 0
S
204
24a70258 0
a433330 0
204
a412048 0
24a6c568 0
0
24a6fc40
a4121ec 0
204
a111094
100002
a4120f0 0
204
100002
100002
204
24a6ad08 0
204
100002
204
a41209c 0
204
a11cfe0 0
100002
24a6bf50
a111040 0
24a6f010 0
24a6b938 0
100002
S
204
100002
24a6e3e0 0
a11113c 0
100002
rowid
a110fec 0
204
24a6d7b0 0
a1110e8 0
0
100002
24a6cb80 0
0
tblsnum
24a6a6f0 0
0
204
15 active, 75000 total,
32768 hash buckets, 0 lock table overflows Profile dskreads

pagreads bufreads %cached dskwrits pagwrits bufwrits
%cached 3797
6447
13-16
60428
4059
537450
99.29
1844
96.95
68P02901W19-S
Oct 2009
CM database status
CM database status
The following commands provide status information on the CM database and should be
executed as user informix:
mib_env
onstat -ukp | more
IBM Informix Dynamic server Version 9.40.UC4 -On-Line -- Up 4 days 19:04:44 -- 148480 Kbytes
Userthreads address flags
sessid
wait
tout locks nreads
root
47
279 1120f630 ---P--F 0

0
root
1167
root
11210878 ---P--B 12
0
omcadmin console
58
0
0
root
0
0
0
0 11210e90 Y--P--- 10
117f5fc8 0
0 112114a8 Y--P--- 21
11bae8a8 0
omcadmin -
34
0 11211ac0 ---P--D 15
Y--P--- 23
1
root -
47 11210260 ---P---
11
tty
nwrites 1120f018 ---P--D

0
1120fc48 ---P--F 0
0
user
298
omcadmin console
root
0 112120d8
omcadmin -
119d3cc0 0
0 112126f0 Y--P--- 19
11990eb8 0
41
0 11212d08 Y--P--- 24
omcadmin -
119950c8 0
0 11213320 Y--P--- 25
-
68P02901W19-S
11995c88 0
omcadmin
55
0 11213938
13-17
Oct 2009
CM database status
Y--P--- 26
0
omcadmin 43
11a26888
0 11213f50 Y--P--- 27
omcadmin -
11a2c518 0
0 11214568 Y--P--- 28
11aaa168 0
41
23
omcadmin 0 11214b80 Y--P-29
omcadmin 38
11aaad78 0
0 11215198 Y--P--- 30
omcadmin -
11aedea0 0
0 112157b0 Y--P--- 31
11b35c10 0
Y--P--- 32
0
33
0 11215dc8
omcadmin 56
11b548d8
0 112163e0 Y--P--- 33
omcadmin -
11bc02b8 0
0 112169f8 Y--P--- 34
1c00598 0
P--- 47
40
49
omcadmin -
0 11217010 Y--
omcadmin -
29
omcadmin -
11d47700 0
0 22 active, 128 total, 24
maximum concurrent Locks address wtlist

owner
lklist
type
tblsnum
key#/bsiz a10ef98 0
HDR+S
0
100002
205
0
100002
HDR+S
207
S
207
112163e0 0
207
11217010 0
0
S
a10f1e4 0
100002
a410048 0
207
112114a8 0
207
12120d8 0
13-18
112157b0
100002
a10f190 0
a10f094 0
207
a10f13c 0
100002
0
100002
11214b80 0
0
100002
100002
11213320 0
207
a10f0e8 0
100002
a10efec
a10f040 0
11213f50 0
112126f0 0
207
rowid
11210e90 0
100002
a41009c 0
S
a4100f0 0
S
1
100002
207
11212d08 0
207
a410144 0
68P02901W19-S
Oct 2009
11213938 0
207
S
S
11214568
100002
a4101ec 0
100002
207
11215198 0
207
11215dc8 0
0
100002
a410198 0
systat script
a410240 0
S
100002
207
100002
207
a410438 0
112169f8 0
0
16 active, 75000 total, 32768 hash
buckets, 0 lock table overflows Profile

dskreads pagreads bufreads %cached
dskwrits pagwrits bufwrits %cached 1759
1886
900303
11443
88.77 isamtot open
read
write
rollbk 776978
147
99.80
1285
rewrite
115326
10626
2868
start
delete
147445
102
commit
285872
4791
gp_read gp_write gp_rewrt gp_del

gp_alloc gp_free
gp_curs 0
ovuserthread ovbuff
numckpts flushes 0
70.33
2.15
0
usercpu
ovlock
0
15
compress seqscans 159

0
syscpu
lokwaits lockreqs deadlks

0
2764
dltouts
0
bufwaits
ckpwaits
668644
102
4117
systat script
The systat script is used to create a file that reflects the status of the system, showing
system up time, process list, disk status, system activity and system swap areas used by
the memory manager. It can be run on the system processor. The script is located in
$OMC_TOP/current/sbin.
The systat script is intended to run as a cron job and removes files older than seven days
automatically.
The format of the systat script is as follows:
systat
There are no parameters supported by the script.
68P02901W19-S
13-19
Oct 2009
systat script
Procedure to run systat

Use the following procedure to run the systat script on the system processor:
Procedure 13-2
Running the systat script on the system processor
Login the system processor omcadmin and enter the password when
requested.
Enter the following to run the systat script:

/usr/omc/current/sbin/systat
When the script is complete, the user prompt is displayed.
To view the output files execute the command:

ls -t /usr/omc/logs/sys_info/stat* | more
The name of the file to be viewed is the first filename in the list.
To display the contents of the output stat file, enter the following
command:
zcat /usr/omc/logs/sys_info/<filename>.Z | more
The contents of the file should look similar to the following:

Start of systat log Mon Apr 11 11:52:19 GMT
2005 uname details: SunOS somc57 5.9 Generic_
118558-02 sun4u sparc SUNW,Ultra-Enterprise
/usr/ucb/uptime:
11:52am
up 4 day(s), 21:14, 2
users, load average: 0.09, 0.06, 0.05 who:

console
Apr 6 14:58 root
pts/1
(10.131.6.108) /usr/ucb/vmstat 5 5:
page
disk
faults
cpu
r b w
root
Apr 11 08:53
kthr
memory
swap
free re
mf pi
po fr de sr m0 m1 m2 m5 in sy cs us sy id 0 0 0
5315600 853096 13 192 1 1 1 0 0 2 1 1 0 728 1109
830 0 1 99 0 0 0 5281144 789528 0
722 657 798 0 0 100
0 0 0 0 0 0 0 8 8 8 0
5280944 789336 5
742 809 0
30
1 0 0 0 0 0 0 0 0 0
0 0 0 5281144 789528
743 675 812 0 0 100 0 0 0
0 0 0 0 0 0 0
0 100 0 0 0 5281088 789480 0
0 0 0 0 0 0 0 0 0 719
0 736
1
670 802 0 0 100
/usr/bin/sar -r 5 5:
For further information on interpreting the output file, refer to the Solaris AnswerBook.
13-20
68P02901W19-S
Oct 2009
Full file systems
Full file systems
Full file systems

If file systems are filling up, this indicates that the amount of data being stored is more than the
system supports, or that an administrator has made an error when trying to take a backup.
Identifying full file systems

A file system shows it is full if its capacity is at 100%.
Check which file system is creating the problem by executing the following command:
df -k
After identifying the problematic file system, look for any large files not expected to be present.
For example, the following command looks for any files larger than 1 Mbyte on the root file
system.
find / -size +1048576c -print
If the root file system is full, check the /dev/rmt directory for any large files because an error in
naming a backup device can result in a file containing data that should have been taken a back
up being created in the /dev/rmt directory.

If the previous procedure ( Identifying full file systems on page 13-21) does not rectify the
problem, data must be archived by performing the following procedure on the system processor:
NOTE
This procedure should not be necessary if the routine procedures have been carried
out as recommended.
68P02901W19-S
13-21
Oct 2009
Removing files or directories
Procedure 13-3
1
Identify, locate and remove any of the following files that are no longer
required.
Core files.
Log files.
Raw statistics files.
Follow the steps in Procedure 12-6, deleting the files wherever

necessary in order to maintain the usage of the disk file system below
85%.
If the system continually runs above the recommended values, modify

the cron jobs to run some of the maintenance scripts more frequently.
Execute the omc_db_maint script more frequently to clean up old

cron logs, parser files, ev_logs and other OMC-R logs.
Removing files or directories
CAUTION
This procedure checks if a file or directory is being referenced by any environment
variables but does not guarantee that a file or directory can be deleted safely. If in
doubt, do not delete the file or directory.
Use the following procedure to check if a file or directory is being used before removing a
file or directory.
Procedure 13-4
Removing a file or directory
Perform any in-house procedures for checking if a file or directory can

be safely removed.

env | grep <name>
where <name> is the name of the file or directory to be deleted.
If this command results in any output, as in the following example,
then do not delete this directory. For example, the following output
is displayed for the directory name ListDir:
env | grep ListDir
LISTTMPDIR=/usr/omc/logs/ListDir
Since there is an output the directory ListDir should not be deleted.
Continued
13-22
68P02901W19-S
Oct 2009
Procedure 13-4
3
Checking disk usage
Removing a file or directory (Continued)
For files, execute the following command as user root:

rm filename
Execute the following command to remove directories that are no
longer required:
rm -rf directory name
Checking disk usage

Use the following procedure to check disk usage. Copy the checklist provided in Table 14-10
Procedure 13-5
68P02901W19-S
Checking disk usage
Check the disk usage of the system by entering the following command
as user root:
du -k | more
Remove any files that are not required and use too much disk space,
for example, old core files, log files and statistic files.
cd directorypath
rm -f filename
Check the amount of available free memory and how active the system
is by entering the following command as user root:
Check how full the file systems are by entering the following command
as user root:
df -k | more
For file systems that are over 100% full, check for existing files that
are over 1 Mbyte and analyze the possibility of removing such files by
entering the following command as user root:
find filesystem -size +1048576c -print | more
13-23
Oct 2009
File access problems
File access problems
Stale NFS file handling

If shared files or file systems on the NFS server have not been remounted on the NFS Client,
this needs to be rectified using the following procedure:
Procedure 13-6
Handling stale NFS file
Login as root on the NFS server.
Make sure that an entry exists for the NFS client in the /etc/dfs/dfstab
file of the NFS server.

shareall
As user root on the NFS client, execute the following commands:

umountall -F nfs
mountall
If this solution does not work, reboot the NFS client by executing the
following command:
shutdown -i6 -g0 -y
Remounting of the shared files automatically starts when the machine
reboots.
Check that all file systems have been mounted on the NFS client by
issuing the following command:
df -k
GUI processor failure to access event log files

If the GUI processors are unable to examine the event log files held within the system processor
directory structure ($OMC_TOP/ne_data/ev_logs), use the Network File System (NFS).
13-24
68P02901W19-S
Oct 2009
OMC-R software process errors
OMC-R software process errors
Analyzing OMC-R process errors

If an OMC-R software error occurs, the audit logs ($OMC_TOP/logs) or the error messages from
the system processor or GUI applications console screen can be used to analyze the problem.
Use the following procedure to analyze OMC-R software process errors:
Procedure 13-7
Analyzing OMC-R process errors
Check the error message displayed.
Examine all the relevant OMC-R user's home directory structure for a
core dump.
Stop and restart the OMC-R software if the OMC-R software problem is
severe. Refer to Manual startup and shutdown of OMC-R software on
page 7-12 for the procedure to stop and start the OMC-R.
Use the following UNIX commands to display process information on

the system processor:
ps -ef | grep +
The system processor returns output similar to the following:
omcadmin
667
656 0 12:31:07 ?
0:00
/usr/omc/current/bin/em_lm_main +
omcadmin
959
953 0 12:31:44 ?
0:03
/usr/omc/current/bin/resync +q +c
omcadmin 722
656 0 12:31:13 ?
0:00
/usr/omc/current/bin/x25appl + 4
omcadmin
958
953 0 12:31:44 ?
0:03
/usr/omc/current/bin/scheduler +q +c
omcadmin 666
656 0 12:31:07 ?
0:00
/usr/omc/current/bin/em_main +
omcadmin
677
656 0 12:31:10 ?
0:00
/usr/omc/current/bin/cm +
omcadmin
678
656 0 12:31:10 ?
0:00
/usr/omc/current/bin/downloader +
omcadmin
681
656 0 12:31:10 ?
0:00
omcadmin
680
656 0 12:31:10 ?
omcadmin
679
656 0 12:31:10 ?
0:00
0:00
Continued
68P02901W19-S
13-25
Oct 2009
List of system processes
Procedure 13-7
Analyzing OMC-R process errors (Continued)
/usr/omc/current/bin/EventInterface +
omcadmin
682
656 0 12:31:10 ?
0:00
omcadmin
683
656 0 12:31:10 ?
0:00
/usr/omc/current/bin/uploader +
omcadmin
684
656 0 12:31:10 ?
0:00
/usr/omc/current/bin/RLogin +
omcadmin
685
656 0 12:31:11 ?
0:00
omcadmin
686
656 0 12:31:11 ?
0:00
omcadmin
687
656 0 12:31:11 ?
0:00
/usr/omc/current/bin/PmLoader +
omcadmin
688
656 0 12:31:11 ?
0:00
/usr/omc/current/bin/Parser + FPCHAN_1 FPADMCHAN_1
omcadmin
701
656 0 12:31:12 ?
0:00
/usr/omc/current/bin/pm_main +
omcadmin 721
656 0 12:31:13 ?
0:00
omcadmin
720
656 0 12:31:13 ?
0:00
/usr/omc/current/bin/CSM_MAIN +
omcadmin
957
953 0 12:31:44 ?
0:03
/usr/omc/current/bin/gateway +q +c /usr/omc/current/config -r
5
Compare this information with that previously taken on the same fully
operational processes. (Refer to Printing current OMC-R processes on
page 2-35 for further information.)
If the fault cannot be rectified, collate all the information before

contacting the local Motorola support centre.
List of system processes

The following is a list of system processes:
13-26
x25appl - X.25 Applications.
emProxy - Event Management Proxy.
em_main - Event Management Router.
cm and cmMib - Configuration Management.
em_lm_main - Event Management List Manager.
downloader - Load Management Downloader.
uploader - Load Management Uploader.
RLogin - Remote Login.
Parser - Performance Manager Parser.
pm_main - Performance Manager Async.

68P02901W19-S
Oct 2009
fm_audit - OMC-R fault management audit.
ResyncCtrl - Resync Controller.
audit - Audit.
smase - SMASE.
resync - Resync.
monitor - Monitor.
pmProxy - Performance Manager Proxy.
gateway - Gateway.
scheduler - Scheduler.
callTrace - Call Trace.
gui - GUI.
Event_Interface - Event Interface.
PmLoader - PM Loader.
CSM_MAIN - Call Success Monitor.
nameserver - Name server.
NetExp - Network Expansion.
OmcPyTom - OMC Python.
gprsTrace - GPRS Trace.
GUI process
GUI process
There is one GUI process:
gui - OMC-R Graphical User Interface.
68P02901W19-S
13-27
Oct 2009
Resetting boot devices
Resetting boot devices
Bootup problems
If a processor boots up in read-only mode or does not boot at all, the boot device will have to
be reset.
Procedure to reset a boot device

{34618} Use one of the following two procedures (Procedure 13-8 {34618} Resetting a boot
device for a N20, N440, SF4800, or SF4900 on page 13-29 or Procedure 13-9 {34618} Resetting
a boot device on an M4000 or M5000 on page 13-30:
Procedure 13-8
SF4900
{34618} Resetting a boot device for a N20, N440, SF4800, or
Bring the system to PROM level by executing the following commands as root:
shutdown -i0 -g0 -y
This will power the processor down to PROM level. When the OK prompt is
displayed, enter the following command:
setenv use-nvramrc? true
Proceed with specifying the boot disk block. At the OK prompt, enter the
following command:
show-disks
On a Netra 440 which has been configured according to Installation and

Configuration: OMC-R Clean Install (68P02901W47), this command displays
the following output:
Continued
13-28
68P02901W19-S
Oct 2009
Procedure 13-8 {34618} Resetting a boot device for a N20, N440, SF4800, or
SF4900 (Continued)
a) /pci@1f,700000/scsi@2,1/disk
b) /pci@1f,700000/scsi@2/disk
c) /pci@1e,600000/ide@d/cdrom
d) /pci@1e,600000/ide@d/disk
e) /pci@1d,700000/scsi@2,1/disk
f) /pci@1d,700000/scsi@2/disk
g) /pci@1d,700000/scsi@1,1/disk
h) /pci@1d,700000/scsi@1/disk
5
Choose entries e and g from the list and then set the device by entering the
following command followed by the SCSI id of the disk which is to be used.
(For example, a disk@8,0:a indicates slice 0 of disk 0 which is located in
target 8.)
nvalias mirrordisk /pci@1d,700000/scsi@2,1/disk@8,0:a
nvalias bootdisk /pci@1d,700000/scsi@1,1/disk@8,0:a
Make the settings permanent so that the processor will always remember
what the boot device is set to by entering the following command:
setenv boot-device bootdisk mirrordisk
Reboot the processor by entering the following command:

boot
Procedure 13-9
{34618} Resetting a boot device on an M4000 or M5000
Insert the Jumpstart DVD into the DVD-ROM drive on the Single Platform
Processor. At the PROM level, type:
ok boot cdrom -s
In SINGLE USER MODE, run format to check all the disks in SPLAT:
# format
Output similar to the following is displayed for a SparcEnterprise M5000:
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@0,0
/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@1,0
/pci@0,600000/pci@0/pci@9/LSILogic,sas@0/sd@16,0
/pci@0,600000/pci@0/pci@9/LSILogic,sas@0/sd@1a,0
/pci@0,600000/pci@0/pci@9/LSILogic,sas@0/sd@1b,0
Continued
68P02901W19-S
13-29
Oct 2009
Procedure 13-9
{34618} Resetting a boot device on an M4000 or M5000 (Continued)
/pci@0,600000/pci@0/pci@9/LSILogic,sas@0/sd@1f,0
/pci@10,600000/pci@0/pci@9/LSILogic,sas@0/sd@1c,0
/pci@10,600000/pci@0/pci@9/LSILogic,sas@0/sd@1e,0
Specify disk (enter the disk number): ^D
3
Now search for the boot devices in the external disks list (c0t0d0 and c0t1d0
need not be checked). First check the disks connected to c1
(Controller 1).
Try to mount the disks on /a one by one.
# mkdir /a
# mount /dev/dsk/c1t22d0s0 /a
If the output is similar to following display, it is not a boot device.Try the
next one:
NOTICE: mount: not a UFS magic number (0x0)
mount: /dev/dsk/c1t22d0s0 is not this fstype
Otherwise, do more to check it:
# ls /a
If the output is similar to the following display, it is a boot device.
INFORMIXTMP
etc
lib
opt
system
zones
bin
export
lost+found
platform
tmp
cdrom
home
mnt
proc
usr
dev
jvp.log
net
sbin
var
devices
kernel
omcgen
solbak
vol
Continued
13-30
68P02901W19-S
Oct 2009
Procedure 13-9
4
Now unmount the disk mounted on controller 1:

# umount /a
Repeat step 3 to find the boot mirror disk connected to c2
(controller 2).
An example similar to the following:
# mount /dev/dsk/c2t21d0s0 /a
# ls /a
INFORMIXTMP
etc
lib
opt
system
zones
bin
export
lost+found
platform
tmp
cdrom
home
mnt
proc
usr
dev
jvp.log
net
sbin
var
devices
kernel
omcgen
solbak
vol
The given example shows that bootdisk is /dev/dsk/c1t22d0s0 and the

mirrordisk is /dev/dsk/c2t21d0s0.
5
To retrieve the boot device physical names from their logical names and
record them, execute the following commands:
# ls -l /dev/dsk/c1t22d0s0
lrwxrwxrwx 1 root root 63 Apr 14 01:34
/dev/dsk/c1t22d0s0 ->
../../devices/pci@0,600000/pci@0/pci@9/LSILogic,sas@0/sd@16,0:a
# ls -l /dev/dsk/c2t21d0s0
lrwxrwxrwx 1 root root 64 Apr 14 01:34
/dev/dsk/c2t21d0s0 ->
../../devices/pci@10,600000/pci@0/pci@9/LSILogic,sas@0/sd@15,0:a
At PROM level, set boot device by executing the following command:

# shutdown i0 g0 y
The following is displayed
ok setenv use-nvramrc? True
ok show-disks
a) /pci@10,600000/pci@0/pci@9/LSILogic,sas@0/disk
b) /pci@10,600000/pci@0/pci@8/pci@0/scsi@1/disk
c) /pci@0,600000/pci@0/pci@9/LSILogic,sas@0/disk
d) /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/disk
q) NO SELECTION
Enter Selection, q to quit: c
/pci@0,600000/pci@0/pci@9/LSILogic,sas@0/disk has been selected.
Type ^Y ( Control-Y ) to insert it in the command line.
e.g. ok nvalias mydev ^Y
Continued
68P02901W19-S
13-31
Oct 2009
Procedure 13-9
for creating devalias mydev for /pci@10,600000/pci@0/pci@9/

LSILogic,sas@0/disk
Choose entries c and a from the list and set boot device by entering
the following command.
ok nvalias bootdisk
/pci@0,600000/pci@0/pci@9/LSILogic,sas@0/disk@16,0:a
ok nvalias mirrordisk
/pci@10,600000/pci@0/pci@9/LSILogic,
sas@0/disk@15,0:a
Now enter the SCSI id of the disk according the boot device name in given
in step 5.
7
13-32
Reboot the processor by entering the following command:

ok boot
68P02901W19-S
Oct 2009
Common Desktop Environment problems
Common Desktop Environment problems
Overview of CDE
The Common Desktop Environment (CDE) provides an easy to use graphical user interface that
provides a consistent look and feel across UNIX environments.
Once a user has logged into one of the machines, a CDE session will start automatically. The
session is customized for root, omcadmin and other.
Installing CDE
CDE is installed along with the Solaris operating system using JumpStart as part of the
upgrade/clean install on the GUI server.
Configuring CDE
CDE is configured at installation time. Configuration files are copied from /usr/omc/config/local
to /etc/dt/appconfig/types/C. This directory contains the customized configuration files (*.fp)
which describe the composition of the front panel, menu items, icons and so on. Action files (of
the form *.dt) are also included in this directory. Every action file should have a corresponding
file with the same name without the .dt extension (the contents of which are irrelevant) in the
directory /etc/dt/appconfig/appmanager/C/Desktop_Apps.
The *.dt action files are essentially callbacks for some of the menu items in the front
panel. Users root and omcadmin have personalized front panel configuration files
$HOME/.dt/types/dtwm.fp.
A generic dtwmrc file is located in /etc/dt/config/C/sys.dtwmrc. A default system wide
.dtprofile is located in /etc/dt/config/sys.dtprofile.
Icon files are located in /etc/dt/appconfig/icons/C.
Generic session files are located in /etc/dt/config/C. The file sys/resources contains the
number of workspaces (defaults to one channel OMC-R). The sys.session file is processed
once for new CDE users and contains commands to start up the File Manager and CDE Help
automatically when a new user logs on for the first time.
Every user, including root and omcadmin, should have a $HOME/.dt directory which contains
all of the user specific configuration information. If a user customizes their session, the files
most likely to be changed are in $HOME/.dt/sessions/current. A current.old directory
also exists with the previous configuration.
68P02901W19-S
13-33
Oct 2009
Normal operation of CDE
Normal operation of CDE

CDE starts automatically. This is the default window manager for OMC-R operators and
administrators. It runs until the operator or administrator logs out.
User root has an omc_admin icon which provides an interface to the User Admin, Group Admin,
and StorEdge Enterprise Backup utilities.
Both root and omcadmin have a CRON icon that allows access through a GUI to the crontab
files.
Errors in user profiles

Errors in the following files could potentially stop users from logging onto the system:
$HOME/.dtprofile.
$HOME/.profile (for users of Bourne shell and Korn shell).
$HOME/.login (for C shell users) if the following line is uncommented in $HOME/.dtprofile:

DTSOURCEPROFILE=true
If this occurs, the user should select the options menu from the login screen, select sessions,
then select Failsafe session, and correct any errors in the above files.
Errors accessing a user's home directory

The home directories of the OMC-R users on the system processor are located in /home by
default. If this directory is not correctly mounted then the user receives an error on login.
Executing shareall (as root) on the system processor followed by mountall can clear up this
problem.
Enabling/disabling the Print Manager

By default, only the root user has access to the Print Manager. To enable other users to access
this, remove the control file which disables the Print Manager access to other users.
13-34
68P02901W19-S
Oct 2009
Other CDE problems
Enabling the Print Manager

Use the following procedure to enable the print manager for all users:
Procedure 13-10
Enabling the Print Manager
Login as root and enter the following commands:

cd /etc/dt/appconfig/types/C
mv Printer.fp Printer.fpbak
Restart the CDE Worksession using the Restart option from the
pulldown options of the left mouse button.
Disabling the Print Manager

If the Print Manager needs to be disabled on a per user basis, the Printer.fpbak file has to be
copied to each user's directory using the following procedure.
Procedure 13-11
Disabling the Print Manager
Login as root and enter the following command (on one line):
cp /etc/dt/appconfig/types/C/Printer.fpbak
/home/username/.dt/types/Printer.fp
Restart the CDE Work session using the Restart option from the pull
down options of the left mouse button.
Other CDE problems

If CDE has been set up, the following file should exist: /etc/dt/.cde_configured. This file should
be removed in order to rerun the CDE setup.
The files $HOME/.dt/startlog and $HOME/.dt/errorlog can be useful for diagnosing errors.
68P02901W19-S
13-35
Oct 2009
CDE login failure
CDE login failure
Overview of CDE login failure

If a user cannot login through the CDE desktop, this indicates that the CDE configuration has
become corrupt, either on a user level or on a system wide level.
Procedure to recover from CDE login failure

Use the following procedure to rectify the CDE configuration, allowing users to login through
the CDE desktop:
Procedure 13-12
the CDE desktop
1
Rectifying the CDE configuration to allow users to login through
Login to the relevant processor as user root.
NOTE
In the case of user root CDE configuration being corrupt,
use the telnet application from another processor in order
to gain access.
13-36
Reconfigure the affected user's CDE environment by entering the

following commands:
rm /home/<user_name>/.dt/.cde_configured
/usr/omc/current/sbin/CDE_setup <user_name>
If this fails to work, this means the system wide configuration is

corrupt. This may be rectified using the following commands:
rm /etc/dt/.cde_configured
/usr/omc/current/sbin/CDE_setup root
68P02901W19-S
Oct 2009
Troubleshooting the LAN
Troubleshooting the LAN
Long response times to commands

If the response times to commands are becoming long, the OMC-R system administrator should
check usage of the LAN.
Checking the performance of the LAN

The following command can be used to measure LAN bandwidth:
netstat -i
Name
Mtu
Queue lo0
0
525302
Net/Dest
0
Address
8232 loopback
0
localhost
hme0 1500 somc57
Ipkts
Ierrs Opkts
2416840 0
somc57
Oerrs Collis
2416840
1705354 0
Check for the following scenarios:
The number of Ierrs or Oerrs is high (0.025 percent or more of Ipkts or Opkts).
Collis (collisions) is greater than 10 percent of Ipkts or Opkts.
If any of the above are true, there is a LAN performance problem. Check the LAN (routers,
bridges, and so on), and check that there are not too many processors connected to the LAN.
The ping and spray commands can also be used if a particular processor on the LAN is
suspected to be the cause of the problem.
If windows and forms are very slow to update, this may be related to the use of X.11 over
the LAN. The X.11 protocol is used to pass windowing information between the client (for
example, the GUI) and the server (the Motif window manager). If the updates to the screen
are slow, or events or alarms are arriving late, there may be a backlog of X traffic, and LAN
performance tests should be run.
To check the LAN to a remote GUI server, the GUI could be run on the remote GUI server with
the DISPLAY environment variable set back to the local processor to see if distance to the
remote processor is a factor.
Taking a long time to open maps or access large files remotely could be due to NFS mount
problems.
Timeouts for each NFS mount can be increased if problems are occurring due to load on the
LAN or when the distance between processors is great.
NOTE
The nestat output can be found in the /usr/omc/logs/sys_info/stat* files which are
run every 10 minutes, or the command can be run directly from the command line.
68P02901W19-S
13-37
Oct 2009
Checking if packets can be sent and received
Checking if packets can be sent and received

If there is a failure within the LAN, use the ping utility to determine the connectivity status of
the LAN. Refer to the Solaris AnswerBook for further information.
Use the following procedure to use the UNIX ping command to confirm that the LAN interface
is running:
Procedure 13-13
running
1
Using the ping command to confirm that the LAN interface is
Enter one of the following on the processor to be interrogated:

ping <remote_hostname>
or
ping <remote_host_internet_address>
Example:
/usr/sbin/ping 175.3.41.101
175.3.41.101: is alive
13-38
If the LAN interface is running, check the following LAN files:

User file /etc/hosts: contains the information that maps the Internet
addresses to the host names. Each host within the OMC-R LAN must
have a unique line entry specified within this file.
User file /etc/hosts.equiv.: can be used to specify remote access
privileges to certain trusted hosts.
User file ~omcadmin/.rhosts: can be used to specify trusted hosts at
a user level. Each line contains the name of the remote system and the
users who have access rights to it.
If the LAN interface is not running, check the LAN cabling and
associated hardware.
If the fault cannot be rectified, collect all the information before

68P02901W19-S
Oct 2009
X.25 failure
X.25 failure
Overview of X.25 failure

Alarms are indicated on the relevant NE subscription window(s). Refer to the manual OMC-R
Online Help, Network Operation for information on alarm handling.
The following troubleshooting aids should be used to determine the possible fault:
Synchronous communications trace.
X.25 status utilities.
Tracing the synchronous communication uses the X25trace utility. Tracing can be performed at
either Level 2 (LAPB) or Level 3 (X.25). By default, all synchronous ports are traced at Level 3
(X.25). It is strongly recommended that the tracing utility is not left running in the background
for long periods of time. It is recommended to assign the output to a file.
NOTE
Analysis of data produced from tracing a synchronous port or executing the x25stat
utility on a particular port, should be performed in consultation with a Motorola
engineer.
Starting x25tool
Refer to Starting and stopping X.25 on page 9-9 for procedures on starting and stopping the
X.25.
X.25 trace on the system processor

Use the following procedure to use the X.25 trace procedure:
Procedure 13-14
1
Running X.25 trace on the system processor
As user root, display the status of the X.25 by entering the following
command:
Continued
68P02901W19-S
13-39
Oct 2009
Displaying x25stat
Procedure 13-14
Running X.25 trace on the system processor (Continued)
The x25trace command captures information about each packet and

/or frame sent and received by SunLink X.25. The x25trace command
requires root permissions to execute. In this example, the trace is
performed on Level 3, the X.25 Packet layer interface for link 0. Enter
the following to start the trace:
/opt/SUNWconn/bin/x25trace -i /dev/x25 -l 0 > trace_link0 &
Allow enough time for X.25 data to be input/output to/from the X.25
link. Note down the process id number that is displayed.
Terminate the x25trace process and examine the trace output data file
by entering the following command:
kill -9 <x25trace process id number>
cat trace_link0
Display X.25 utilities.

Reset the packet counts regularly, and observe any changes in packet
count distribution. It is also useful to keep some x25stat outputs,
taken when the network is known to be working correctly. These
samples can be used later to compare with output taken when the
network is not working correctly.

Displaying x25stat
The following procedure describes how to display the X.25 status:
Enter the following command to display the X.25 status for link 0:
/opt/SUNWconn/bin/x25stat -l 0
PER LINK STATISTICS FOR X25 ____________________________
Link
0 State
: Unknown -------------------------------------
Packet type
TX
RX ------------------------------------0
confirm
RNR
Restart
0
Resets
RR
0
Interrupts
Registration
(total)
0
0
Restart
0
Diagnostic
0
0
0
0
0
Reg confirm
Reset confirms
13-40
Call accept
0
Call
Packets
Bytes (total)
68P02901W19-S
Oct 2009
Moving a machine with a forced link speed
Moving a machine with a forced link speed
The fix for the performance problem described above means that the Single Platform Processor
will no longer auto negotiate the network speed. If the Single Platform Processor is later
moved to a network port which is not 100 Mbps full duplex, the Single Platform Processor
may not be able to connect to the network. In order to re-instate auto negotiation, the script
/etc/rc2.d/S31linkspeed needs to be removed.
Ensure that the task is completed as user root on the Single Platform Processor by executing
rm /etc/rc2.d/S31linkspeed
68P02901W19-S
13-41
Oct 2009
Logical Vol Mgr troubleshooting
Logical Vol Mgr troubleshooting
Logical Vol Mgr problems

The most common problem that might affect Logical Vol Mgr would either be disk failure caused
by the loss of a physical disk, or a file system problem caused by file system corruption.
NOTE
Incorrect maintenance and administration of Logical Vol Mgr could cause the system
to crash and possibly lose the information held on the disks. Recovery should only be
performed by a Solaris Logical Vol Mgr expert.
13-42
68P02901W19-S
Oct 2009
Operating Information: OMC-R System Administration Replacing hard disk on system processor Sunfire/Netra 440/Netra 20
Replacing hard disk on system processor Sunfire/Netra

440/Netra 20
Errors on the console and in /var/adm/messages help to identify the disk that is causing a
problem. The problem is highlighted under Logical Vol Mgr as all metadevices using that disk
are in a maintenance state.
Use the following procedure to recover a lost disk :
Procedure 13-15
Recovering a lost disk
Change to the following directory:

cd /sbin
To obtain the Logical Vol Mgr status, enter the following command:
metastat | more
Output data similar to the following is displayed for a Sunfire 4900:
d135: Soft Partition
Device: d25
State: Okay
Size: 23072768 blocks (11 GB)
Extent
Start Block
Block count
386202624
23072768
d25: Mirror
Submirror 0: d26
State: Okay
Submirror 1: d27
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 1433371008 blocks (683 GB)
Continued
68P02901W19-S
13-43
Oct 2009
Replacing hard disk on system processor Sunfire/Netra 440/Netra 20
Procedure 13-15
Recovering a lost disk (Continued)
d26: Submirror of d25

State: Okay
Size: 1433371008 blocks (683 GB)
Stripe 0: (interlace: 512 blocks)
Device
Start Block
Dbase
State
Reloc
c1t9d0s0
No
Okay
Yes
c1t10d0s0
No
Okay
Yes
c1t11d0s0
No
Okay
Yes
c1t12d0s0
No
Okay
Yes
c1t13d0s0
No
Okay
Yes
Hot Spare

State: Okay
Size: 1433371008 blocks (683 GB)
Stripe 0: (interlace: 512 blocks)
Device
Start Block
Dbase
State
Reloc
c3t9d0s0
No
Okay
Yes
c3t10d0s0
No
Okay
Yes
c3t11d0s0
No
Okay
Yes
c3t12d0s0
No
Okay
Yes
c3t13d0s0
No
Okay
Yes
Hot Spare
NOTE
State: Needs maintenance indicates that a problem has
occurred.
When the disk has been replaced (this can be done with the machine
running), the disk requires repartitioning, and Logical Vol Mgr needs
to be re-enabled to use that disk.
3
For example, the following commands are used to recover from the
above error once a new disk has been installed:
prtvtoc /dev/dsk/c1t2d0s2 | fmthard -s - /dev/rdsk/c0t2d0s2
metareplace -e d20 c0t2d0s0
Continued
13-44
68P02901W19-S
Oct 2009
Operating Information: OMC-R System Administration Replacing hard disk on system processor Sunfire/Netra 440/Netra 20
Procedure 13-15
Recovering a lost disk (Continued)

d20: device c0t2d0s0 is enabled
When this has been done for each device that was in a maintenance
state, the mirrors begin to resync.
4
Resynchronizing can be checked by entering the following command:

metastat | grep Resync
d20: Mirror
Submirror 0: d101
State: Resyncing
Submirror 1: d100
State: Okay
Resync in progress: 12 % done
Pass: 1
Size: 262960 blocks
State: Resyncing
Size: 262960 blocks
Stripe 0:
Device
c0t2d0s0
Start Block
0
Dbase State Hot Spare

No
Resyncing

State: Okay
Size: 262960 blocks
Stripe 0:
Device
c1t2d0s0
68P02901W19-S
Start Block
0

No
Okay
13-45
Oct 2009
Recovering from other Logical Vol Mgr problems
File system corruption usually causes both sides of the mirror to require maintenance, but only
on that slice of the disk. Errors on other slices of that disk would highlight a more serious
problem, as follows:
d20: Mirror
Submirror 0: d101
State: Needs maintenance
Submirror 1: d100
State: Okay
Pass: 1
Size: 262960 blocks
Size: 262960 blocks
Stripe 0:
Device
Start Block
c0t2d0s0
No
Maintenance

Size: 262960 blocks
Stripe 0:
Device
c1t2d0s0
Start Block
0
No
Maintenance
This problem can be fixed by shutting the machine down to single user mode and running fsck
on the affected file system. The machine should then be rebooted and the problem should have
been fixed. This can be confirmed by running metastat on the metadevice.
Recovering from other Logical Vol Mgr problems

Other problems with Logical Vol Mgr should be handled by a Solaris Logical Vol Mgr expert.
13-46
68P02901W19-S
Oct 2009
Checking disk mirroring
Disk mirroring checklist

To check disk mirroring, follow the procedure below. You can copy the checklist provided in
Table 13-2

Method
Check
1
Check the Logical Vol Mgr

status.

metastat
A stable set of Logical Vol Mgr mirrors should
look similar to the example shown in the section
metastat output on page 13-47.
Check for any subdisks that

require maintenance using
the metastat command. Any
subdisks that need maintenance
should be repaired.
Refer to Logical Vol Mgr troubleshooting on page

13-42 in this chapter for the procedure to recover
a lost disk.
Check that the system has at

least three state databases on
each mirror.

metadb
If the system does not have

sufficient state databases then
they must be created.

metadb -a -f <slice 1> <slice 2> <slice 3
etc>
For example:
metadb -f -d /dev/dsk/c1t2d0s3
/dev/dsk/c2t2d0s3
metastat output
d125: Mirror
Submirror 0: d126
Submirror 1: d127
State: Okay
State: Okay
option: roundrobin (default)
Pass: 1
Read
Size: 4197717 blocks (2.0 GB) d126: Submirror of d125

State: Okay
:
Size: 4197717 blocks (2.0 GB)
Device
d128
Start Block
0
Device: c0t1d0s0
(2.0 GB)
68P02901W19-S
No
Yes
State Reloc Hot Spare

Okay
State: Okay
Device
0
Dbase
No
Stripe 0
No
Size: 4198400 blocks
Start Block
Dbase Reloc
Extent
Start Block
c0t1d0s0
Block
13-47
Oct 2009
metastat output
count
Submirror of d125
(2.0 GB)
66854923
State: Okay
Stripe 0:
Reloc Hot Spare
Device
d129

c2t5d0s0
0
Device
Block count
4198400
d120: Mirror
No
d127:
State
Okay
Start Block
No
Dbase
State: Okay
Yes
0
Submirror 0: d121
Submirror 1: d122
13-48
Start Block
Device: c2t5d0s0
4198400 blocks (2.0 GB)
4198400
Size: 4197717 blocks
State: Okay
No
Size:
Dbase Reloc
Extent
Start Block
66854923
State: Okay
Pass: 1
68P02901W19-S
Oct 2009
Device busy error
Device busy error
Device busy error

If an attempt to mount a device has failed, this indicates that the device was already mounted.
If an attempt to unmount a device has failed, this indicates that the device contains an active file
such as an open file, a current directory, a mount point, or a running program.
This message also occurs when trying to enable accounting that is already enabled.
Unmounting a device
To unmount a device containing active processes, close all the files under that mount point,
quit any programs started from there and change directories out of that hierarchy. Then try to
unmount again.
68P02901W19-S
13-49
Oct 2009
Ejecting DVD-ROMs
Ejecting DVD-ROMs
DVD-ROM drive not ejecting

If a DVD-ROM cannot be ejected from the DVD-ROM drive of a SPARC processor using the
command eject cdrom, the following procedure can be used to manually eject the DVD-ROM.
Procedure to free up DVD-ROM drive

Use the following procedure to eject a DVD-ROM from the DVD-ROM drive of a SPARC processor
when the eject cdrom command fails to work:
Procedure 13-16
13-50
Procedure to free up a DVD-ROM drive
Login as root.
Type the following command to stop volume management:

svcadm disable volfs
Press the eject button on the DVD tray to manually eject the DVD.
Type the following command to restart volume management:

svcadm enable volfs
68P02901W19-S
Oct 2009
StorEdge Enterprise Backup problems
StorEdge Enterprise Backup problems
StorEdge Enterprise Backup tape error

StorEdge Enterprise Backup will not perform a backup if a tape has not been inserted into
the tape drive, or if the backup tape in the tape drive has not been mounted and/or labeled.
An unmounted tape is indicated by the following error in the pending field of the StorEdge
Enterprise Backup utility:
Tape from default pool not mounted, waiting
Use the following procedure to mount a new tape to be used in a backup:
Procedure 13-17
68P02901W19-S
Mounting a new tape to use in a backup
Check if the correct tape is inserted in the tape drive.
From the StorEdge Enterprise Backup Server GUI Administration

window, click Devices and select the tape driver (/dev/rmt/0cbn)
from the Device list.
Click on the Mount icon to mount the tape. The tape should then be
mounted and the backup will continue.
If a new tape has been inserted then the tape should first be labelled
by clicking Label, and should be mounted in the usual way.
13-51
Oct 2009
Database failure
Database failure
Database failure
In the event of a failure of the INFORMIX database, the log file should be examined to locate the
problem. Other sections in this manual give more details of the procedures involved.
Use the following procedure to investigate database failure:
Procedure 13-18
Investigating a database failure
Examine the online log. Refer to Database utilities on page 8-4 for
further information.
Use the Mode menu selection of onmonitor to determine the mode of

operation. Refer to Database utilities on page 8-4 for further details
about onmonitor.
Examine the software log files in $OMC_TOP/logs. Refer to OMC-R

log and error files on page 4-3 for further information.

Problems adding/updating statistics in PM database

If problems are being experienced with PM statistics, check whether dbms log files are present.
These log files are created when problems are encountered during adding or updating statistics
in the PM database. There should be one dbms log file per error that occurs.
The filename will be of the form dbms.nnnnnnnn, where nnnnnnnn is a unique integer
identifying the log file.
To find out when the log was created, use the following UNIX command:
ls -l
13-52
68P02901W19-S
Oct 2009
Onperf utilities
Onperf utilities
Overview of Onperf
The Onperf utilities provide GUIs for displaying system resource information on the Performance
Management (PM) and Configuration Management (CM) databases. The user selects items to
be measured. These may be displayed graphically in real time, or stored for later playback.
The Onperf utilities are implemented in INFORMIX and run on the system processor.
The Onperf utilities perform the following basic functions:
Display the values of online metrics in the Graph Tool window.
Save online metric values to a file.
Allow review of online metric values from a file.
Starting onperf from the CDE front panel

Use the following procedure from the CDE front panel to start the onperf utility for the PM or
CM databases:
Procedure 13-19
Starting onperf from the CDE front panel
Login to the system processor as user omcadmin.
On the CDE front panel, click the INFORMIX icon and select one of the
following options from the Database Applications menu.
To monitor the PM database, select onperf - PM database.
To monitor the CM database, select onperf - MIB database.
Either selection causes the Graph Tool window (Figure 13-1) to be

displayed.
68P02901W19-S
13-53
Oct 2009
Starting onperf from the command line
Figure 13-1
Displaying the OnPerf utility window
ti-GSM-Displaying_the_OnPerf_utility_window-00080-ai-sw
Starting onperf from the command line

The onperf utility may be invoked from the UNIX command line as an alternative to starting
from the CDE front panel.
Procedure 13-20
Starting the onperf utility from the command line
Login to the system processor as user omcadmin.

setenv DISPLAY omc_splat:0.0
Select one of the following options:
To monitor the PM database, enter onperf_pm
To monitor the CM database, enter onperf_mib
Loading a history file

Use the following procedure to load and display a history file on the Graph Tool:
13-54
68P02901W19-S
Oct 2009
Procedure 13-21
Loading and displaying a history file
From the CDE desktop environment, click on the OnPerf icon for the
application database. The Graph Tool window is displayed as shown
in Figure 13-1.
From the Graph menu (Figure 13-2), select the Open History File
option.
The standard Select File dialog box is displayed as shown in

Figure 13-3.
Enter the path name of a history file in the selection box to load into
the Graph Tool.
Click OK. The history file is displayed in the Graph Tool window.
NOTE
A history file consists of metrics data previously saved by the
data collector. To help find a history file, specify a wildcard
filter. In the Filter edit box, enter a directory path that
includes wildcards. Click on the Filter command button at
the bottom of the window. All files that satisfy the filter are
listed on the right.
Figure 13-2
Graph menu
ti-GSM-Graph_menu-00056-ai-sw
68P02901W19-S
13-55
Oct 2009
Figure 13-3
Select file dialog box
ti-GSM-Select_file_dialog_box-00057-ai-sw
13-56
68P02901W19-S
Oct 2009
Saving Graph Tool configurations
Saving Graph Tool configurations

Use the following procedure to save a Graph Tool configuration:
Procedure 13-22
Saving a Graph Tool configuration
From the Graph menu, select New. This creates a new Graph Tool.
There is no difference in functionality between the new Graph Tool and
the original Graph Tool. These tools may be closed in any order.
To save a new configuration, select the Configure menu and click

Save Configuration As (refer to Figure 13-4). In the Save File dialog
box that appears, enter a file name in the selection box to store the
present Graph Tool configuration. Configuration information includes
the set of histogram buffers, the active graph and activity tools.
To help find a directory in which to write the file, a wildcard filter may
be specified. Enter a directory path that includes wildcards in the
Filter edit box, then click the Filter command button. All files that
satisfy the filter will be listed.
When a configuration has been previously saved to a file, the Save

Configuration option can be used to update that graph configuration
file (refer to Figure 13-4).
Figure 13-4
Configure menu
ti-GSM-Configure_menu-00058-ai-sw
68P02901W19-S
13-57
Oct 2009
Selecting metrics
Selecting metrics
Use the following procedure to select metrics to be displayed:
Procedure 13-23
Selecting metrics to be displayed
From the Metrics menu, select a metric class.
A Select Metrics window is displayed with the metric class selected.
Select one of the valid metric scopes in the list box on the left
(Figure 13-5). The list box in the centre shows the metrics available to
the selected scope.
Select a metric from this list.
Click Add. The metric is added to the list box on the right.
Click OK to display the metrics in the Graph Tool.
Figure 13-5
Select Metrics
ti-GSM-Select_Metrics-00059-ai-sw
13-58
68P02901W19-S
Oct 2009
Viewing metrics
The following bullet points list the metric classes available and their relevant metric scopes:
For the disk chunks class, the relevant metric scopes are chunk pathnames for the online
database server.
For the disk spindle class, the relevant metric scopes are the pathnames of the disk devices
or cooked files used by the online database server.
For the fragment metric class, the relevant metric scopes are the dbspaces for fragments
that are currently open to a thread. These are called active table fragments.
For the physical processor class, the relevant metric scopes are any of the physical
processors for the computer running online, or total for an aggregate of all the physical
processors.
For the server class, there is only one metric scope, aggregate. The scope for these metrics
is the database server as a whole.
For the disk sessions class, the relevant metric scopes are the active sessions, identified by
user login and host name.
For the tblspace metric class, the relevant metric scopes are the tblspace names that
correspond to tables that are currently open to a thread. These are called action tables.
A tblspace name is a composite of the database and the table that it refers to. For
fragmented tables, the tblspace represents the sum of all fragments for that table. To
obtain measurements for a single fragment, use the fragment metric class.
For the virtual processor class, the relevant metric scopes are the online virtual processor
classes: CPU, AIO, KIO, and so on. Each virtual processor metric represents an aggregate
of activity for all online virtual processors of the indicated class.
Viewing metrics
By selecting any of the options from the View menu, the metric can be viewed in various
formats, as illustrated in Figure 13-6:
Figure 13-6
View menu
ti-GSM-View_menu-00060-ai-sw
68P02901W19-S
13-59
Oct 2009
Viewing metrics
Line Plot
When this option is selected, Onperf repaints the Graph Tool in the line format as shown
in Figure 13-7.
Figure 13-7
Line plot graph
ti-GSM-Line_plot_graph-00061-ai-sw
In this format, the window includes two scroll bars: a horizontal pan bar and a vertical zoom
bar. The zoom bar adjusts the scale of the horizontal time axis. When the zoom bar is raised,
the scale is reduced, and vice versa. The pan bar allows movement along the horizontal time
axis. To change the scale or appearance of an individual metric, click on the legend for that
metric. This displays the Customize Metric dialog box. This box has buttons for setting the
metric scale, color, style and width.
NOTE
The line graph may contain hidden data values. These can be displayed by selecting
the View menu option Show null values.
13-60
68P02901W19-S
Oct 2009
Viewing metrics
Horizontal Bar Graph

When this option is selected, the Graph Tool is redrawn in horizontal bar format as shown
in Figure 13-8.
Figure 13-8
Horizontal bar graph
ti-GSM-Horizontal_bar_graph-00062-ai-sw
In this format, the horizontal axis represents the scale of each metric. To change the scale or
appearance of an individual metric, click on the legend for that metric. This brings up the
Customize Metric dialog box, which has buttons for setting metric scale, color, style and width.
68P02901W19-S
13-61
Oct 2009
Viewing metrics
Vertical Bar Graph

When this option is selected, the Graph Tool is redrawn in vertical bar format as shown in
Figure 13-9.
Figure 13-9
Vertical line graph
ti-GSM-Vertical_line_graph-00063-ai-sw
In this format, the vertical axis represents the scale of the metric measurement. To change the
scale or appearance of an individual metric, click on the legend for that metric. This brings
up the Customize Metric dialog box, which has buttons for setting metric scale, color, style
and width.
13-62
68P02901W19-S
Oct 2009
Viewing metrics
Pie Chart
When this option is selected, the Graph Tool is repainted in pie chart format as shown in
Figure 13-10.
Figure 13-10
Pie chart
ti-GSM-Pie_chart-00064-ai-sw
The pie charts show the relative sizes between metrics, but not the values themselves. The last
sampled values are displayed in the legend next to the metric name.
68P02901W19-S
13-63
Oct 2009
Monitoring tools
Monitoring tools
The monitor tools include the Status Tool and the Query Tree. These are described below:
Status Tool
The Status Tool monitors the state of the data collector and the database server. A typical
Status Tool window is displayed in Figure 13-11.
Figure 13-11
Status tool
ti-GSM-Status_tool-00065-ai-sw
13-64
68P02901W19-S
Oct 2009
Monitoring tools
Query Tree
The Query Tree window allows the performance of individual queries to be monitored. A
typical Query Tree window is displayed in Figure 13-12. The Query Tree tool has two options:
Select Session and Quit. When a session which is running a query is chosen, the large detail
window displays the iterations that comprise the execution plan for the query. The Query Tree
tool represents each iteration by a box that includes a dial indicating tuples per second and
a number indicating the input tuples for the iteration. In some cases, not all the iterators fit
into the detail window. The left pane shows the iterators as small icons. This provides a map
of the overall query.
Figure 13-12
Query Tree
ti-GSM-Query_Tree-00066-ai-sw
68P02901W19-S
13-65
Oct 2009
Activity tools
Activity tools
There are five different activity tools:
Disk activity.
Session activity.
Disk capacity.
Physical processor activity.
Virtual processor activity.
Each of these activity tools displays information about a particular database activity, based
on some suitable metric.
The scale of an activity tool cannot be changed from within the tool itself. There are two activity
tool menus: the Graph menu and the Tools menu. The Graph menu has options for closing the
graph, opening a new graph, and exiting Onperf. The Tools menu has options to display the
Query Tree tool, status tool, or another activity tool.
Disk Activity Tool

The Disk Activity Tool displays activities for chunks, ranked according to the Disk Operations
metric. The metric class is Disk Chunk and the metric scope is the chunk pathname. This
metric represents the total number of I/O operations involving the chunk. The horizontal bar
graph view is used.
Figure 13-13
Disk Activity Tool
ti-GSM-Disk_Activity_Tool-00067-ai-sw
13-66
68P02901W19-S
Oct 2009
Activity tools
Disk Capacity Tool

The Disk Capacity Tool displays chunks ranked according to the free disk space available in
megabytes. The horizontal bar graph view is used.
Figure 13-14
Disk Capacity Tool
ti-GSM-Disk_Capacity_Tool-00068-ai-sw
68P02901W19-S
13-67
Oct 2009
Activity tools
Session Activity Tool

The Session Activity Tool displays the sessions for the database server. The metric class is
Session and the metric scope is the host name. This metric represents the total number of ISAM
calls and PDQ calls per second. The horizontal bar graph view is used.
Figure 13-15
Session Activity Tool
ti-GSM-Session_Activity_Tool-00069-ai-sw
13-68
68P02901W19-S
Oct 2009
Activity tools
Virtual processor Activity Tool

The Virtual processor Activity Tool displays the virtual processors configured for the
database server. The horizontal bar graph view is used. The scale of the Virtual Processor
Activity Tool cannot be changed manually.
Figure 13-16
Virtual Processor Activity Tool
ti-GSM-Virtual_Processor_Activity_Tool-00070-ai-sw
68P02901W19-S
13-69
Oct 2009
Checking and recovering database tables
Checking and recovering database tables
Monitoring database space usage and fragmentation

Overview of monitoring commands
The following OMC-R commands monitor the space left in a database server:
omc_db_ckspace
db_ckspace
db_cktab
The following INFORMIX commands also monitor the space left in a database server:
onstat -d
oncheck -pe
These commands work for the MIB and PM servers.
To use these commands, login as omcadmin.
13-70
68P02901W19-S
Oct 2009
omc_db_ckspace command
The usage lines in the /usr/omc/logs/omc_db_maint* log files come from omc_db_ckspace.
These lines are similar to the following:
DBS Pages Allocated:
Free:
309981 DBS Pages Used:
309981 DBS Pages
0 Warning: OMC Database space used has reached 100% specified
DBMS_MAX_SPACE_USED 80%
TBLSpace TBS Pages Allocated: 251748 TBS Pages Used: 7108 TBS
Pages Free: 244640
The DBS Pages section shows the number of pages:
In all DB spaces (that is, available to the server).
Allocated to tables.
NOT allocated to tables.
The TBS Pages section shows the number of pages:
Allocated to data tables.
With data on them.
Allocated to tables but which are currently empty.
The example above illustrates that the database can appear to be full (from the DBS Pages
section) although there may be plenty of space left within the tables. Also, the above example
does not show the distribution of free space among the tables, so inserts into one table can fail
even if there is free space in other tables. Once space has been allocated to a specific table, it is
NEVER freed up into the general pool without manual intervention.
db_ckspace command
The command db_ckspace shows the amount of space used in each chunk and in each dbspace.
The output is similar to:
On-Line Instance: DBSpace AllocUsedFree
rootdbs 309981
167263
Device
142718 /dev/rvol/omc_db
==================================
309981 167263
142718 rootdbs Total
=============================
Total
68P02901W19-S
309981
167263
142718
13-71
Oct 2009
db_cktab command
db_cktab -d <dbname> shows the free space within each table. The output is similar to:
Connecting to database omc_db Table Name
(Number):
Pages
Used
#Rows subscriptions
Free Extent DataPg
1239
84 subscription_list
20
20
bss_datetimes
bss_statistics
cell_statistics
1219
15
11
26
23
6719
109
4105
5639
5639
2292
31
9162
The Pages column shows the number of pages allocated to the table, and the Used and Free
columns show the number of pages with and without data respectively. The Free pages are
permanently allocated to one table, but not currently used by it, so they comprise part of the
TBS Pages Free value in the output from omc_db_ckspace. The Extent column shows the
number of table fragments. If there are more than 16, consider defragmenting the table.
Combining commands
When used together, the db_ckspace and db_cktab commands give a clear picture about
database space usage. omc_db_ckspace gives a very simple overview of the situation, which
should not be relied upon.
The onstat -d command is similar to the db_ckspace command as it shows each dbspace in the
first part of the output, then each chunk in the second part of the output (with dbspace and
chunk numbers, so you can see which chunks belong to each dbspace). The output is similar
to the following:
Dbspaces address
310260e0 1
1 1
number flags fchunk nchunks flags ownername

1
N informix rootdbs 31026658 2
omc_db_temp 310266c0 3
4
1 4
1 3
1 6
N informix
N informix omc_db_plog 31026728
N informix omc_db_llog 31026790 5
omc_db_sp1 310267f8 6
1 2
1 5
N informix
N informix omc_db_sp2 6 active,
2047 maximum
Chunks address
31026148 1
2
2
905
chk/dbs offset sizefree

2
204798
51198
204745PO-/dev/omc_db_temp 310262f8 3 3
PO-/dev/omc_db_logs 310263d0 4
PO-/dev/omc_db_logs 310264a8 5
31026580 6
bpages flags pathname
17113 PO-/dev/omc_db_root 31026220
5 2
1024098 1024045
4 40962
158718
40958
70915
1024098 797169PO-/dev/omc_db1
PO-/dev/omc_db2 6 active,
2047 maximum
The oncheck -pe command is as good as an input to a shell script. It lists each chunk within
each dbspace, and every tablespace fragment (extent) of every table, including unallocated
space. The output is unwieldy and would need filtering for your purposes.
13-72
68P02901W19-S
Oct 2009
Reading the database schema
Reading the database schema

Use the command dbschema to get information about the structure of a database.
To get all information about a database (so that it can be recreated from scratch), enter the
following command:
dbschema -d <dbname> -ss -p all <outputfile>
If you omit <outputfile>, output is sent to stdout, but this is likely to be too much to read easily.
NOTE
A database can be created from the above output file by typing:
isql - <commandfile>
where <commandfile> is the <outputfile> from dbschema.
To show just the synonyms in the database, enter the following command:
dbschema -s all -d <dbname>
Defragmenting tables (MIB database)

The MIB database tables are small compared to those on the PM database. It is normally easy to
defragment them non-destructively, by executing an SQL command which forces INFORMIX
to rebuild the table. To do this, use the alter index <indexname> to cluster command,
which sorts the data in a table into the key value order of the nominated index. INFORMIX
implements this by sorting the data into a new tablespace, then deleting the old tablespace
and renaming the new one.
NOTE
The following procedures should only be carried out with the advice of a Motorola
Engineer.
The following defragmenting procedure:
Does not cause any loss of data from the MIB.
Can be used on any table, provided there is sufficient free space in the dbspace to create a
second copy of the table.
Normally reduces the number of extents to three or fewer.
Depending on how much contiguous free space is present, it does not normally require
an outage.
68P02901W19-S
13-73
Oct 2009
Emptying and defragmenting one or more PM statistics tables
Use this procedure to defragment tables:
Procedure 13-24
Defragmenting tables (MIB database)
Login as omcadmin or informix on the system processor.

mib_env
To find the name of an index to cluster, enter the following command:

dbschema -d dbname -t tablename
Look at the names of indexes. If one of the definitions is create cluster

index <indexname>, use that. Otherwise, choose an index defined
with create unique index <indexname>. If there are no unique
indexes, choose an index that looks as though it is frequently used (it is
unlikely to cause any major performance problems even if you choose
an inappropriate index).
To cluster the index, enter the following command:

isql dbname alter index indexname to cluster;
<CTRL>-C
If you see the message table is locked, try again after a few minutes. If
the table is locked permanently, you may need to schedule an omc stop
or start (cluster the index after the omc stop but before the omc start).
NOTE
Do not follow the procedure in Customer Service Bulletin
CSB-98-015, because it does not cater for views or any other
constructs you might encounter away from the statistics
tables.

This is the quick and easy way to remove troublesome statistics, and defragment the statistics
table at the same time. It is possible to complete the process within five minutes, with an
outage time of less than two minutes.
This procedure results in all the statistics in the affected table being lost. It must only be used
on tables which do not have views (this includes all tables whose names end in _statistics. It
normally reduces the number of extents to two (there is no need to get a table into a single
extent). It requires a short PM outage (typically, less than five minutes).
NOTE
Engineer.
13-74
68P02901W19-S
Oct 2009
Use the following procedure to empty and defragment PM statistics tables:
Procedure 13-25
Emptying and defragmenting PM statistics tables

omc_env
To determine the size of the table(s) and to find the size of the database
table currently being used, enter the following command:
db_cktab -d omc_db
The output is similar to the following:
Table Name (Number): Pages Used Free Extent DataPg #Rows
nbr_statistics (0x01000040):
1000 775
225 1443 18532
carrier_statistics (0x01000030): 166910 166133 777 15 49610
297671
cell_statistics (0x01000006):100632
10053597 19 27620
165715
68P02901W19-S
Multiply the value in the Used column by two to get the size in
kilobytes. For example, the size of the cell_statistics table in the above
example is 100535 pages multiplied by 2 KB page size equals 201070
KB.
To alter the next size of the table(s), enter the following commands:
isql omc_db alter table tablename next size size_in_kb;
<CTRL>-C
where <tablename> is the table name and <size_in_kb> is the size
(in kilobytes) of the table.
Repeat the alter table line in step 5 for each table you want to empty.
(The <CTRL>-C is to quit isql.)
To get the schema of the table(s), enter the following command:

dbschema -d omc_db -t tablename -ss -p all tablename.sql
To disconnect the OMC-R processes (outage start), enter the following

command:
db_disconnect disconnect
To drop the table(s), enter the following:

isql omc_db drop table tablename;
<CTRL>-C
10
To recreate the empty table(s), enter the following command:

isql omc_db tablename.sql
11
To reconnect the OMC-R processes (outage end), enter the following

command:
db_disconnect connect
13-75
Oct 2009
Adding extra logical logs to the PM database server

If the OMC-R installation has some unused space left in the Logical Log dbspace, you can
add extra logs. These logs will increase the resilience of the server against transactions that
take a long time to update.
NOTE
Engineer.
Use the following procedure to add extra logs, repeating this procedure until there is no room
left on the logical log dbspace (INFORMIX notifies the user when there is no space left):
Procedure 13-26
Login as informix on the system processor.

omc_env
Enter the following command to see if there is any space left on the
logical log partition:
onstat -d
The output looks like this:
Dbspaces
address number flags fchunk nchunks flags ownername
310260e0 1 1 1 1
N informix rootdbs
31026658 2 1 2 1
N informix omc_db_temp
310266c0 3 1 3 1 N informix omc_db_plog
31026728 4 1 4 1
N informix omc_db_llog
31026790 5 1 5 1
N informix omc_db_sp1
310267f8 6 1 6 1
N informix omc_db_sp2
6 active, 2047 maximum
Chunks
address chk/dbs offset sizefree
bpages flags pathname
31026148 1
1
2 51198
17113 PO-/dev/omc_db_root
31026220 2
2
2 204798 204745PO-/dev/omc_db_temp
310262f8 3 3
2 40958
905
PO-/dev/omc_db_logs
310263d0 4
4 40962 158718 70915 PO-/dev/omc_db_logs
310264a8 5
5 2 1024098 797169PO-/dev/omc_db1
31026580 6
6
2 1024098 1024045
PO-/dev/omc_db2
6 active, 2047 maximum
The first part of this output shows the dbspaces. The second part
shows the chunks, which make up the dbspaces.
Continued
13-76
68P02901W19-S
Oct 2009
Procedure 13-26
Adding extra logical logs to the PM database server (Continued)
Find the line in the first part of the output for the omc_db_llog
dbspace (30 k or 45 k systems) or the omc_db_logs dbspace (5 k
systems), and note the dbspace number (4 in the example above).
Find the corresponding number in the dbs column of the Chunks list
(there can be several chunks to one dbspace). The amount of free
space can be determined by examining the free column.
To find the size of the existing logs, enter the following command:
onstat -l
This shows the log file size in 2 k pages in the last part of the output. In
the following example, the logs are 10240 pages, which is 20480 KB:
address number
a57cfc8 1F------
68P02901W19-S
flagsuniqid
beginsize used%used
0307835 102400 0.00
When you add a logical log, use the following command to specify the
size (in kilobytes):
onparams -a -d DBspace [-s size]
In this example, you can use:
onparams -a -d omc_db_llog -s 20480
13-77
Oct 2009
Alarms
Alarms
Overview of alarms
Certain OMC-R alarms cannot be handled by the operator and will be referred to the system
administrator for corrective action. Such alarms fall into the following categories:
Disk space usage on the system processor.
Database.
X.25 lines connected to the system processor.
System processor failure.
Frequency of events arrival.
For more information on alarm handling procedures, refer to OMC-R Online Help, Network
Operation. For more information on the alarms, refer to Maintenance Information: Alarm
Handling at the OMC-R (68P02901W26) manual.
NOTE
If the number of alarms in the PLMN alarm window does not match with the OMC
main board, close the PLMN alarm window, and reopen it. The correct alarm number
is displayed.
13-78
68P02901W19-S
Oct 2009
Disk space usage on the system processor
Disk space usage on the system processor

UpperLimitDiskUsage (30010) alarm
An alarm is raised when the upper threshold of disk usage is exceeded on any of the following
partitions of the system processor:
/home
/usr
/usr/omc/ne_data
/tmp
/solbak
The default value of the upper threshold is 90 percent.

When the threshold value is exceeded, the system removes any log files older than three days
from the $OMC_TOP/logs. The threshold value should return to 90 percent.
Use the following procedure to resolve the alarm:
Procedure 13-27
Resolving the UpperLimitDiskUsage (30010) alarm
Raise the value of the upper threshold limit (if less than 90 percent) in
the file $OMC_TOP/config/global/FM_audit.CNFG.
Perform the disk full procedures.
LowerLimitDiskUsage (30011) alarm

An alarm is raised when the lower threshold of disk usage is exceeded on the /, /home, /usr and
/usr/omc/ne_data partitions of the system processor. The default value of the lower threshold
is 80 percent.
Procedure 13-28
68P02901W19-S
Resolving the LowerLimitDiskUsage (30011) alarm
Raise the value of the lower threshold limit (if less than 80 percent) in
the configuration file $OMC_TOP/config/global/FM_audit.CNFG.
Refer to FM_audit.CNFG file for further details of the
FM_audit.CNFG file.
Check the disk usage of all the partitions.
13-79
Oct 2009
CPU and memory usage alarms

CPU load exceeds lower limit (30061) alarm
An alarm is raised when the lower threshold limits for CPU load have been exceeded by the
system processor at the OMC-R. This fault condition may occur if the CPU load is high.
Immediate action must be taken to reduce the CPU activity by expanding the lower CPU load
limit.
If the CPU becomes overloaded, the OMC-R may not function correctly.
NOTE
The CPU load exceeds upper limit alarm indicates that the CPU is completely
overloaded.
The following are possible causes for this alarm:
The CPU load on the system processor has reached its maximum capacity.
The upper limit threshold of the CPU load was lowered.
Procedure 13-29
13-80
Resolving the CPU load exceeds lower limit (30061) alarm
Check the CPU load on the system processor.
Monitor the alarm, and if it does not clear, carry out further
investigations to determine which processes are overloading the CPU.
Raise the value of the threshold CPU limit.
68P02901W19-S
Oct 2009
CPU load exceeds upper limit (30062) alarm

An alarm is raised when the upper threshold limit for CPU load has been exceeded by the system
processor at the OMC-R. The CPU is completely overloaded.
Immediate action must be taken to reduce the CPU activity.
The following are the possible causes for this alarm:
The CPU load on the system processor has reached maximum capacity.
The upper limit threshold of CPU load was lowered.
Procedure 13-30
Resolving the CPU load exceeds upper limit (30062) alarm
Check the CPU load on the system processor.
investigations to see which processes are using too much CPU.
Raise the value of the threshold CPU load limit.
Memory usage exceeds lower limit (30063) alarm

An alarm is raised when the lower threshold limits for memory usage have been exceeded by the
system processor at the OMC-R. Current memory usage is high, and requires that the memory is
made available by expanding the lower memory usage limit.
This fault condition could occur if the memory usage is high. Immediate action must be taken to
free up the memory. If the memory usage is too high, the OMC-R may not function correctly.
NOTE
The memory usage exceeding the upper limit alarm indicates that the memory is
completely exhausted.
68P02901W19-S
13-81
Oct 2009
The memory usage on the system processor has reached its maximum capacity.
The upper limit threshold of memory usage was lowered.
Procedure 13-31
alarm
Resolving the Memory usage exceeding the lower limit (30063)
Check the memory usage on the system processor.
investigations to see which processes are using too much memory.
Raise the value of the threshold memory usage limit.
Memory usage exceeds upper limit (30064) alarm

An alarm is raised when the upper threshold for memory usage has been exceeded by the
system processor at the OMC-R. Memory is completely used up.
Immediate action must be taken to free up memory.
Memory usage by the system processor has reached maximum capacity.
The upper limit threshold of memory usage was lowered.
Procedure 13-32
13-82
Resolving the Memory usage exceeds upper limit (30064) alarm
Check the memory usage on the system processor.
investigations to see which processes are using too much memory.
Raise the value of the threshold memory usage limit.
68P02901W19-S
Oct 2009
Database alarms
Database alarms
Three alarms are raised when the Performance Manager and the Event Manager are
disconnected from the database. Two of these are warnings that can lead to the major alarm
30004 parserDisconnectedTooLong being generated if the cause of the alarm continues.
parserDisconnectedTooLong (30004) alarm

This alarm is raised when the parser has been disconnected from the OMC-R database for
longer than 10800 seconds.
Procedure 13-33
Resolving the parserDisconnectedTooLong (30004) alarm
If omc_db_maint has finished executing, check the omc_db_maint

logs to see if the command db_disconnect connect parser has been
executed. If not, run this command:
$DBMS_BIN/db_disconnect connect parser
Check to see if the Event Manager (EM) needs to be connected by

trying to create a subscription list. If this fails, enter the following
command:
$DBMS_BIN/db_disconnect connect em
PMDisconnectedFromDB (30007)
This alarm is only a warning and is generated when the PM parser has been disconnected
as a part of routine database maintenance.
If the parser is disconnected from the database for a long time, the major alarm 30004
parserDisconnectedTooLong is generated.
Refer to the corrective action for the alarm parserDisconnectedTooLong.
EMDisconnectedFromDB (30008)
This alarm is only a warning and is generated when the EM list manager has been disconnected
as part of routine database maintenance.
If the EM list manager is disconnected from the database for a long time, the major alarm
30004 parserDisconnectedTooLong is generated. This usually means that the EM list
manager has not been reconnected after completion of maintenance.
Refer to the corrective action for the alarm parserDisconnectedTooLong.
68P02901W19-S
13-83
Oct 2009
Database alarms
Database exceeds upper limit (30014) alarm

An alarm is raised when the upper threshold of database usage have been exceeded by the
system processor at the OMC-R. The database is completely full.
If the database space is full, action should be taken to free up space immediately. The OMC-R
may not function correctly if it cannot write into the database.
Check whether the database usage by the system processor caused the database to reach
its maximum capacity.
Check that the frequency of running the maintenance, and the database space allocations
are adequate.
Check the upper/lower thresholds of the databases to verify that they are no longer
exceeded. Raise the value of the threshold database limit (if lower than 90%).
Database exceeds lower limit (30019) alarm

An alarm is raised when the lower threshold limits of database usage have been exceeded by the
system processor at the OMC-R. Current database usage is high, and requires that space be
made available by expanding the lower database limit.
This fault condition could occur if the database space usage is high. Action should be taken to
free up space in the database immediately. If the database becomes full, the OMC-R may not
function correctly because it may not have the ability to write into the database.
NOTE
The database upper limit alarm indicates that the database is completely full.
The database usage by the system processor caused the database to reach its maximum
capacity.
The various OMC-R databases are not being maintained properly.
The various OMC-R databases are filling up too quickly for the defined maintenance
procedures.
The upper limit threshold of database usage was lowered.
NOTE
There is still room in the database. However, the OMC-R system administrator
should keep a close watch on the space used.
13-84
68P02901W19-S
Oct 2009
X.25 alarms
Procedure 13-34
Resolving the Database exceeding the lower limit (30019) alarm
In the Alarm window, check the error reason field in the alarm message to
determine the cause(s) of this alarm.
Check the database usage in the system processor database to which the error
relates.
Verify that the database maintenance procedures currently in operation comply

with those recommended in this manual.
Raise the value of the threshold database limit (if lower than 90%).
Investigate the necessity of increasing the regularity (frequency) with which the
various maintenance and archive scripts are run (or executed).
Review database space allocations to determine whether there is a space

shortage. Determine where the shortage is located.
Check the upper/lower thresholds of the databases to verify that they are no
longer exceeded.
X.25 alarms
A Level123 Failure alarm is raised when there is a Layer1/Layer2/Layer3 failure on the system
processor X.25 line.
Procedure 13-35
68P02901W19-S
Resolving X.25 alarms
Check for related errors, for example, 30013

solarisHardwareFailure.
Stop and start the X.25 on the link indicated by the alarm.
Refer to Starting and stopping X.25 on page 9-9 for further details of
the procedure to stop and start X.25.
Check the X.25 Network Interface Card.
Check that the physical link has not been removed or accidentally cut.
Check the X.25 log files.
Check the X.25 process state as follows:

Determine the state of alarm VCs to all NEs.
Login as root and enter the following command:
/opt/SUNWconn/bin/x25stat -L
This shows the status of the connections.
If no VCs exist, check the system processor X.25 NICs, packet switch,
MUX and NE, following the above order.
If problems persist, contact the local Motorola office.
13-85
Oct 2009
Hardware failure alarms
Hardware failure alarms

An alarm is raised when a system processor hardware unit is out of service.
Procedure 13-36
Resolving Hardware failure alarms
Check to see if maintenance is being performed on the system

processor.
Refer to the Sun System Administration manual for further information

on dealing with Sun hardware unit failure.
If problems persist, contact the local Motorola office.
OMC-R alarms
OMCOverloadedWithEvents (30021) alarm
The OMCOverloadedWithEvents alarm (30021) indicates the rate of events arriving at the
OMC-R is too fast and a backlog of events is occurring.
Procedure 13-37
13-86
Resolving the OMCOverloadedWithEvents (30021) alarm
Check the reason for the arrival of several events at the OMC-R. If
there are a large number of similar alarms, these particular alarms
could be throttled or blacklisted.
Check that a slow communication link to a GUI is not causing a backlog

of events.
Check the performance of the system processor to see if it is

functioning correctly.
68P02901W19-S
Oct 2009
OMC-R alarms
OMCOverloadedEventsDiscarded (30022 alarm)

The OMCOverloadedEventsDiscarded alarm (30022) indicates that too many events are
frequently arriving at the OMC-R and the events are discarded.
Procedure 13-38
Resolving the OMCOverloadedEventsDiscarded (30022 alarm)
Check the reason for the arrival of so many events at the OMC-R. If
there are a large number of similar alarms, these particular alarms
could be throttled or blacklisted.
Check that a slow communication link to a GUI is not causing a backlog

of events.
Check the performance of the system processor to see if it is

functioning correctly.
Criticalstatseventsdiscarded (30078 alarm)

{34164}
The Criticalstatseventsdiscarded alarm (30078) is generated to notify OMC-R software
applications and operators that the number of critical statistics events has exceeded the
established limit and is becoming overloaded with events that are discarded without processing
or logging.
There are too many BSCs enabling the critical statistics reporting at a time.
There are too many cells enabling the critical statistics reporting per BSC at a time.
Procedure 13-39
68P02901W19-S
Resolving the Criticalstatseventsdiscarded (30078 alarm)
Check the number of BSCs which enable the critical statistics reporting
to ensure it is less than 30.
Check the number of cells of each BSC which enable the critical
statistics reporting to ensure it is less than 90.
13-87
Oct 2009
Setting FM audit and disk usage limits
Setting FM audit and disk usage limits
Overview of setting FM audit and disk usage limits

The file $OMC_TOP/config/global/FM_audit.CNFG contains user defined values that are used
for setting the FM audit timers and disk usage limits.
FM_audit.CNFG parameters
The FM_audit.CNFG file is read once a minute, consequently changes to this file do not require
the OMC-R to be stopped and restarted.
An example of the FM_audit.CNFG configuration file for a High-End platform, showing the
recommended default values:
FM_DISK_AUD_CNT 20 FM_X25_AUD_CNT 1
FM_HARDWARE_AUD_CNT 2 FM_DBASE_AUD_CNT
360 FM_CPU_AUD_CNT 20 FM_MEM_AUD_CNT
20 FM_USR_GSM_PART_LOWER_LIMIT 80
FM_USR_GSM_PART_UPPER_LIMIT
90 FM_NEDATA_PART_LOWER_LIMIT
80 FM_NEDATA_PART_UPPER_LIMIT
90 FM_ROOT_PART_LOWER_LIMIT
80 FM_ROOT_PART_UPPER_LIMIT
90 FM_HOME_PART_LOWER_LIMIT
80 FM_HOME_PART_UPPER_LIMIT
90 FM_RAWSTATS_LOWER_LIMIT
80 FM_RAWSTATS_UPPER_LIMIT
90 FM_TMP_PART_LOWER_LIMIT
80 FM_TMP_PART_UPPER_LIMIT
90 FM_SOLBAK_PART_LOWER_LIMIT
80 FM_SOLBAK_PART_UPPER_LIMIT
90 FM_DBASE_USE_LOWER_LIMIT
80 FM_DBASE_USE_UPPER_LIMIT
90 FM_CPU_LOAD_LOWER_LIMIT
80 FM_CPU_LOAD_UPPER_LIMIT
90 FM_MEM_USE_LOWER_LIMIT
80 FM_MEM_USE_UPPER_LIMIT
90 FM_REMOVE_CORES_AGE 3
13-88
68P02901W19-S
Oct 2009
NUM_HSI_PORTS 8 FM_CPU0SYSTEM_ID
10 FM_CPU1SYSTEM_ID
11 FM_CPU2SYSTEM_ID
14 FM_CPU3SYSTEM_ID 15
where:
Disk audit count = 20 minutes.
X.25 audit count = 1 minute.
System processor hardware audit count = 2 minutes.
Database audit count = 6 hours.
NOTE
The audit counts are the times between each audit (wait times) and do not include the
time taken to run the audits. Timings should be considered as estimates.
CPU audit count = 20 minutes.
Memory audit count = 20 minutes.
Usr partition lower limit = 80%.
Usr partition upper limit = 90%.
Ne_data partition lower limit = 80%.
Ne_data partition upper limit = 90%.
Root partition lower limit = 80%.
Root partition upper limit = 90%.
Home partition lower limit = 80%.
Home partition upper limit = 90%.
Raw statistics partition lower limit = 80%.
Raw statistics partition upper limit = 90%.
/tmp partition lower limit = 80%.
/tmp partition upper limit = 90%.
StorEdge Enterprise Backup partition lower limit = 80%.
StorEdge Enterprise Backup partition upper limit = 90%.
Database use lower limit on the system processor = 80%.
Database use upper limit on the system processor = 90%.
CPU load lower limit = 80%.
CPU load upper limit = 90%.
Memory use lower limit = 80%.
68P02901W19-S
13-89
Oct 2009
Memory use upper limit = 90%.

Remove cores count = 3.
Number of HSI ports = 8.
system processor CPU 0 ID number =10.
To change a FM audit timer or disk usage limit value, edit the appropriate line entry in the
$OMC_TOP/config/global/FM_audit.CNFG file.
NOTE
The FM audit and disk usage limits should only be changed by qualified personnel
under guidance from Motorola Support. Contact Motorola Support for further
information.
13-90
68P02901W19-S
Oct 2009
Using neighbor statistics
Using neighbor statistics
Neighbor statistics
Neighbor statistics are a valuable resource used in optimizing and fault finding. This section
describes how to enable the neighbor statistics and the limitations that should be placed on
their use.
Limitations on use of neighbor statistics

When performing optimization or fault finding work, it is recommended that the neighbor
statistics should be enabled only on specific cells. When that work is complete, the statistics
should be disabled.
Do not enable the neighbor statistics on more than 16 cells per BSS.
To automatically enable the neighbor statistics for specific cells using a cron job, use the Cyclic
Neighbor Statistics feature (PMCyclic).
Cyclic Neighbor Statistics feature (PMCyclic)

Neighbor statistics for a cell can be enabled automatically using the Cyclic Neighbor Statistics
feature. This feature, also referred to as PMCyclic, enables neighbor statistics for cells in
rotation, starting with cells that have the oldest date for the last enabled neighbor statistics.
The Cyclic Neighbor Statistics feature automatically enables the neighbor statistics for cells in
a BSS in the following sequence:
User-defined cells. The user creates a file listing the cells where the neighbor
statistics are to be enabled. This file should be created in, and is read from,
/usr/omc/ne_data/nha_nbrs/operator_nbr.
NHA-defined cells. The Motorola NHA tool creates a file containing a list of
cell ids where the neighbor statistics are to be enabled. This file is read from
/usr/omc/ne_data/nha_nbrs/nha_neighbours. When PMCyclic has used this
file, it moves it to: /usr/omc/ne_data/nha_nbrs/nha_neighbours.previous. If a
/usr/omc/ne_data/nha_nbrs/nha_neighbours file does not exist, PMCyclic uses
/usr/omc/ne_data/nha_nbrs/nha_neighbours.previous.
68P02901W19-S
13-91
Oct 2009
Cyclic Neighbor Statistics feature (PMCyclic)
If the environmental variable ENABLE_CYCLIC_NBRS is set to ON, and the maximum

number of cells with the neighbor statistics enabled per BSS has not been exceeded, the
Cyclic phase of PMCyclic is run.
The Cyclic phase enables neighbor statistics for the cell with the oldest date in its Last
Date Neighbor Statistics Enabled record, for each BSS in the network. For example, if
BSS8 Cell3 has 28/5/01 in its Last Date Neighbor Statistics Enabled record, and BSS8 Cell4
has 28/3/01 in its Last Date Neighbor Statistics Enabled record, the Cyclic phase enables
neighbor statistics for Cell4. The Cyclic phase starts at the BSS associated with the first
cell id in the user-defined file, then in the NHA-defined file. The Cyclic phase then moves
on to the next BSS in the network, and so on. This is also shown in the following table.
a.
At the BSSs containing cells listed in the operator_nbr file.
b.
At the BSSs containing cells listed in the nha_neighbours file.
c.
In a cyclic pattern across other BSSs in the network.
The Cyclic phase limits the number of cells enabled up to 80% of the value of
PM_MAX_NEIGHBOURS divided by 16*32 (BSS Limit) in total. Once the BSS limit is
exceeded, it is no longer possible to enable the neighbor statistics for 16 cells per BSS.
NOTE
If the same cells are always specified in the operator- and/or NHA-defined files,
the same BSSs will always be selected in the Cyclic phase.
Maximum number of cells with enabled neighbor statistics per BSS

The maximum number of cells per BSS that can have the neighbor statistics enabled is 16. If the
neighbor statistics for a cell cannot be enabled because this limit has already been exceeded,
the Cell Id is recorded in the log file.
Running PMCyclic
PMCyclic is a cron job, which will run automatically each night. Each time PMCyclic is run, all
currently enabled neighbor statistics are disabled.
Use the following procedure to run PMCyclic:
Procedure 13-40
Running PMCyclic
Login as omcadmin.
If required, create the file operator_nbr in

/usr/omc/ne_data/nha_nbrs. Enter one GSM Cell Id or cell name
per line.
If required, create the NHA file using the NHA tool. See NHA manual
for further details.
Continued
13-92
68P02901W19-S
Oct 2009
Procedure 13-40
Neighbor statistics alarm
Running PMCyclic (Continued)
If the Cyclic phase of PMCyclic is to be run, set the environment

variable ENABLE_CYCLIC_NBRS to ON. Refer to User configurable
environment variables on page 6-5 for further details.
To run PMCyclic, use the following command:

setup_cyclic_nbr <no.>
Where <no.> is the number of hours after which PMCyclic should be
run.
The following are valid values for <no.>: 6, 12, 24.
For example, the following command runs PMCyclic every six hours
(four times a day), that is, 24 hours divided by 6 equals 4:
setup_cyclic_nbr 6
To run PMCyclic once a day, use the following command:
setup_cyclic_nbr
PMCyclic log file

The progress of PMCyclic is recorded in the following log file:
/usr/omc/logs/nbr_stats<YYYYMMDD>
The log file records the following information by grouping the cells according to whether they
are Operator Enabled Neighbor Statistics, NHA Enabled Neighbor Statistics, Cyclic Enabled
Neighbor Statistics:
Cell Id or name.
Whether enabling of the neighbor statistics for a cell was a Success or a Failure.
The log file also records cells that could not be enabled because the maximum number of
cells per BSS limit had been reached.
This log file is deleted after 7 days by another cron job.
Neighbor statistics alarm

If too many neighbor statistics are enabled, the following alarm is generated:
30026. OMC: tooManyNeighbourStats
This alarm is generated when 70 percent of the space in the PM database allocated to the
neighbor statistics, the nbr_statistics table, has been occupied by statistics. If the entire
space that is allocated has been used, neighbor statistics will be discarded to prevent the
PM database from becoming full.
On receiving alarm 30026, take immediate steps to disable the unwanted neighbor statistics.
To avoid generating alarm 30026 the variable PM_MAX_NEIGHBOURS can be raised if
neighbor statistics are in use. This variable sets the size of the PM database space allocated
to neighbor statistics. Refer to User configurable environment variables on page 6-5 for a
complete description of this variable.
68P02901W19-S
13-93
Oct 2009
Raising the maximum limit of neighbor statistics

On a Low-Range OMC-R, the parser is able to process statistics for a maximum of 2800 neighbors
per network in a 30 minute interval. In this case, the variable PM_MAX_NEIGHBOURS which
limits the neighbor statistics can be increased to 2800.
On a Mid-Range OMC-R, the parser is able to process statistics for a maximum of 92160
neighbors per network in a 30 minute interval. In this case PM_MAX_NEIGHBOURS can be
increased to 92160.
On a High-Range OMC-R, the parser is able to process statistics for a maximum of 18000
neighbors per network in a 30 minute interval.
The procedure to change this limit is described in User configurable environment variables on
page 6-5.
The following additional checks and actions should also be performed:
Monitor the nbr_statistics table.
(Optionally) modify the sizes of the nbr_statistics and nbr_entity tables.
Monitoring the nbr_statistics table

The nbr_statistics table in the PM database may start to fragment due to the increase in
the neighbor statistics being stored. This should be monitored on an ongoing basis using the
db_cktab utility. Enter the following commands:
omc_env
db_cktab -d omc_db nbr_statistics
Modifying the database configuration files

The following database configuration files should also be modified to take into account the
increased number of neighbors:
/usr/omc/current/config/db_config.
Modifying the sizes of the nbr_statistics and nbr_entity tables

The following procedure modifies the extents of the nbr_statistics and nbr_entity tables. This
procedure is optional and there will be a slight improvement in the OMC-R performance. It will
be of most benefit if the nbr_statistics table is becoming excessively fragmented.
NOTE
Engineer.
Use the following procedure to modify the table sizes:
13-94
68P02901W19-S
Oct 2009
Procedure 13-41
68P02901W19-S
Modifying the sizes of the nbr_statistics and nbr_entity tables
Enter omc_env and press RETURN.
Obtain the sizes of the tables with the db_cktab command.

db_cktab -d omc_db -t nbr_statistics;
db_cktab -d omc_db -t nbr_entity;
omcadmin unloads both the tables using dbaccess. For more

information on dbaccess, see Using dbaccess.
Get the schema of both tables as follows:

dbschema -t nbr_statistics -d omc_db nbr_stat.sql
dbschema -t nbr_entity -d omc_db nbr_ent.sql
Drop both the tables from the database.
Start the INFORMIX ISQL utility and connect to the OMC-R database:
/usr/informix/bin/isql omc_db
Enter the query language option and type the SQL commands below.
Ensure correct substitution of the table name being used.
drop table nbr_statistics;
drop table nbr_entity;
The sizes of the tables can be calculated in kilobytes by taking the

number of pages for each table, obtained in step 3, and multiplying
it by 2.
Update the initial and next extent sizes in the schema files, as obtained
from step 4, with the values generated by step 8.
10
Recreate both tables as follows:

dbaccess omc_db nbr_stat.sql
dbaccess omc_db nbr_ent.sql
11
Reload each table as follows:

omc_db_load_table -d omc_db nbr_statistics.unl
omc_db_load_table -d omc_db nbr_entity.unl
This completes the resizing of the extents and reloading of both the
tables.
13-95
Oct 2009
Using dbaccess
Using dbaccess
Use the following procedure to use dbaccess:
Procedure 13-42
1
Using dbaccess
Ensure that the current directory is large enough to hold the unloaded
tables. This can be done by checking the number of 2 K pages detailed
in the output of step 2 in Modifying the sizes of the nbr_statistics
and nbr_entity tables.
NOTE
If the files are unloaded to a directory that is too small,
this may have an adverse effect on the performance of the
OMC-R.
13-96

dbaccess omc_db -
Then enter the following command:

unload to nbr_statistics.unl select * from nbr_statistics;
Finally, enter the following command:

unload to nbr_entity.unl select * from nbr_entity;
To return to the operating system, press Ctrl-C.
68P02901W19-S
Oct 2009
Power failure
Power failure
Overview of recovery from power failure

The system processor can be powered by a UPS (see Graceful shutdown on mains failure on
page 2-57).
If this option is not used, then in the event of a power failure the system and GUI processors
have no graceful shutdown. This section provides procedures to recover from:
Power failure on all machines on page 13-97.
Power failure on the system processor on page 13-98.
Power failure on a GUI processor on page 13-98.
Use the appropriate procedure in this section to recover from power failure where an UPS
is not installed.
Power failure on all machines

In the event of a power failure on the system and GUI processors, turn off the power switches.
After power restore

To restart the system and GUI processors, the power switches must be turned on.
For information on powering on the system processor, see the particular Sun system manual
for the respective system Platform processor.
Restarting the OMC-R

When power has been restored to all machines, start the OMC-R.
Refer to Manual startup and shutdown of OMC-R software on page 7-12 for further details of
starting and stopping the OMC-R software.
Restarting the GUI sessions

When the OMC Startup Complete message is displayed on the system processor console, each
user may have to restart their GUI session.
If problems occur upon power restoration, contact the local Motorola representative.
68P02901W19-S
13-97
Oct 2009
Power failure on the system processor
Power supply unit failure

On the system and GUI processors, if the power supply unit fails, contact the local Motorola
representative immediately.
Power failure on the system processor

Access to the OMC-R software is not possible during a power failure on the system processor.
If the power to the system processor fails, perform the following procedure:
Procedure 13-43
Recovering from power failure on the system processor
Exit from the GUI sessions on the GUI processor.
When power is restored the system processor power switches must

be turned on, and the OMC-R started. Refer to Manual startup and
shutdown of OMC-R software on page 7-12 for further details of
starting and stopping the OMC-R software.
Restart the GUI sessions when the OMC Startup Complete message
is displayed on the system processor console.
Power failure on a GUI processor

If a power failure occurs on a GUI client, it is not possible to run the GUI from this machine.
If a power failure occurs on a GUI server, it is not possible to run the GUI from this machine or
any of its connected GUI clients.
It is still possible to manage and monitor the network as normal from all other machines. All
features are available.
When the power is restored the machine reboots automatically. A GUI session may then be
started on a GUI server and any of its connected GUI clients.
13-98
68P02901W19-S
Oct 2009
Checking the system processor hardware
Checking the system processor hardware
System processor hardware LEDs

Sunfire 4800
Refer to SunFire 6800/4810/4800/3800 Systems Service Manual (Part No. 805-7363-12) for
explanations of various LEDs on the Sunfire 4800.
Netra 20
Refer to Netra AC100/DC100 Services and System Reference Manual (Part No. 806-7336-12)
for explanations of various LEDs on the Netra 20.
Netra 440
Refer to Netra 440 Server Service Manual (Part No. 817-3883-11) for explanations of various
LEDs on the Netra 440.
Displaying system processor status

The following command can be used to display the status and operating conditions of a SUN
platform:
/usr/platform/sun4u/sbin/prtdiag -v
The following example, shows a typical output text for this command.
Example
System Configuration:
sun4u 5-slot
Sun Microsystems
Sunfire 4800 System
clock frequency: 100 MHz Memory size:

2048 Mb =========================
CPUs =========================
Run
CPU
---
Module
---
MHz
MB
-------
-----
400
8.0
8.0
US-II
US-II
Ecache
10.0 7
US-II
10.0 7
15
CPU
CPU Brd
Impl.
Mask
------ -----10.0 3
14
1
7
0
---- 3
1
400
400
8.0
400
8.0
US-II
10.0 ======================== Memory
68P02901W19-S
13-99
Oct 2009
=========================
Intrlv.
MB
Status
Condition
With --- --------- 3
----
-------
1024
2-way
A 7
60 ns
2-way
Speed
----------
1024
Bank
Factor
Active
Intrlv. Brd
-----
OK
-------
--
60 ns
Active
OK
A ===================
====== IO Cards ====================

=====
Bus
Freq Brd
Type
MHz
Name
----
Slot
Model ---
----
----
------
---------------------------- -------------------- 1
SBus
25
SUNW,501-2253 1
cgsix
SBus
25
HSI
SUNW,501-1725-01 1
SBus
25
25
25
SBus
5
SBus
25
SUNW,501-1725-01 5
3 SUNW,hme
SBus
SUNW,fas/sd (block) 1
13
3060 5
SUNW,hme 1
SBus
SBus
fas/sd (block) 5
25
25
SBus
25
socal/sf (scsi-3)
501-
HSI
SUNW,
13
SUNW,
501-3060 No failures found
in System ===========================
No System Faults found =================
===== Most recent AC Power Failure: =======
====================== Wed Sep
8 23:35:21
2004 ========================= Environmental

Status ============ Keyswitch position is in Normal
Mode System Power Status: Minimum Available System
LED Status:
GREEN
YELLOW
ON
Status ----
GREEN Normal
OFF
------ Disk
BLINKING Fans: ----- Unit
OK PPS
OK System
Temperatures (Celsius): -----------------------------Brd
State
-----3
42
Current
--- --OK
42
OK
34
--------- Supply
------ 1
OK PPS
OK System 5.0v
13-100
----- 1
OK
38
Max
Trend ---
OK
32
stable 7
38
Min
39
36
-------
43
42
stable 5
32
44
stable
OK
30
34
42
stable CLK
stable Power Supplies: -----Status --------OK 3

OK System 3.3v
OK Peripheral5.0v
68P02901W19-S
Oct 2009
OK Peripheral12v
OK Auxilary 5.0v
OK Peripheral 5.0v precharge

12v precharge
OK Peripheral
OK System 3.3v precharge
OK System 5.0v precharge
OK AC Power
OK ========================= HW
Revisions ==================== ASIC Revisions:
----------- Brd FHC
FEPS
Board Type
----
----
AC
SBus0
SBus1
PCI0
Attributes --- ---
----------
22
Dual-SBus-SOC+
CPU
Capable 7
1
1
--
---------- 1
100 MHz Capable 3

22
PCI1
----1
-----
----
5
100 MHz Capable 5
Dual-SBus-SOC+
100 MHz
CPU
100
MHz Capable System Board PROM revisions: --------------------------- Board 1:
FCODE 1.8.30 2002/10/25 14:02
iPOST 3.4.30 2002/10/25 14:03 Board 3:

2002/10/25 14:03
Board 5:
POST
3.4.30 2002/10/25 14:03 Board 7:
68P02901W19-S
POST
3.2.30
3.9.30 2002/10/25 14:04
FCODE 1.8.30 2002/10/25 14:02
2002/10/25 14:03
OBP
OBP
iPOST
3.2.30
3.9.30 2002/10/25 14:04
13-101
Oct 2009
Configuring a Timeserver
Configuring a Timeserver
The OMC-R can optionally be configured to use an NTP Timeserver on the local LAN to
synchronize the time with the rest of the network.
To use a local LAN Timeserver, enter the IP address or the name of the Timeserver in the
/etc/inet/ntp.conf file on the OMC-R. If a hostname is specified, either the DNS must be
configured or the hostname must be added to /etc/inet/hosts.
To configure the OMC-R to use an NTP Timeserver, carry out the following procedure:
Procedure 13-44
Configuring the OMC-R to use an NTP Timeserver
As user root, edit the /etc/inet/ntp.conf file using a text editor. Add the
appropriate entries to the ntp.conf file as shown below:
# The following lines were added to force this machine
# to serve localtime
server 127.127.1.1 prefer # LCL, local clock
fudge 127.127.1.1 stratum 12 # increase stratum
# peer timeserver prefer
# Miscellaneous stuff
driftfile /etc/ntp.drift # path for drift file
Comment out the lines with # referring to LCL, local clock and increase
stratum. Uncomment the lines referring to peer timeserver prefer
line substituting the IP address or the hostname of the Timeserver on the
local LAN for timeserver. The ntp.conf file should now be similar to the
following example where somc1 is the hostname of the Timeserver on the
local LAN:
# The following lines were added to force this machine
# to serve localtime
# server 127.127.1.1 prefer # LCL, local clock
# fudge 127.127.1.1 stratum 12 # increase stratum
peer somc1 prefer
# Miscellaneous stuff
driftfile /etc/ntp.drift # path for drift file
13-102
Stop the ntp daemon and restart by

executing the following commands as user root:
/etc/init.d/xntpd stop
/etc/init.d/xntpd start
68P02901W19-S
Oct 2009
Support for IP Multipathing in Solaris10/GSR9 on

Sunfire platforms
IP Multipathing is supported in Solaris10/GSR9 on Sunfire platforms. To configure IP

multipathing, complete the following as user root:
Procedure 13-45
1
Configuring IP Multipathing
Update the /etc/hostname.ce1 and /etc/hostname.ce3 files by adding

the following entries:
/etc/hostname.ce1
podge_priv netmask + broadcast + group ipmp2 up addif 10.50.50.22
netmask + broadcast + deprecated -failover up
/etc/hostname.ce3
10.50.50.21 netmask + broadcast + group ipmp2 deprecated
-failover standby up
68P02901W19-S
Oct 2009
Run the following commands as user root:

ifconfig ce1 podge_priv netmask + broadcast + group ipmp2 up
ifconfig ce1 addif 10.50.50.22 netmask + broadcast + deprecated
-failover up
ifconfig ce3 10.50.50.21 netmask + broadcast + group ipmp2
deprecated -failover standby up
13-103
13-104
68P02901W19-S
Oct 2009
Chapter
14
Checklists
68P02901W19-S
Oct 2009
14-1
Overview
Overview
This chapter provides copies of the various checklists, referred to in the rest of the manual.
These lists can be copied and used to record checks and other information so that they can be
saved for future reference.
The following checklists are provided in this chapter:

Weekly administration checklist on page 14-5.
Monthly administration checklist on page 14-6.
Checking cron jobs on page 14-7.
Checking databases on page 14-10.

Checking databases on page 14-10.
Checklist for CM database on page 14-12.
Checking X.25 connectivity on page 14-14.
Checking core dumps on page 14-15.
Checking disk usage on page 14-16.
Checking disk mirroring on page 14-17.
Checking for successful parsing of statistics on page 14-18.
Recording details on page 14-20.

Setting up a night concentration centre on page 14-20.
Client and server partition details on page 14-21.
14-2
68P02901W19-S
Oct 2009

To check daily administration, follow the procedure in Daily administration checklist on page
2-74. Copy the checklist in Table 14-1 to record the checks.
Table 14-1

Method
Checked?
Check the file system

capacity.

df -k
Any file systems with a 90-100% capacity must be
cleaned up for unwanted files or directories.
[-]
Check the disk usage capacity

of the system.

du | more
Terminate processes that are not required and are
consuming disk capacity.
[-]
Check the output of cron

mail jobs from user root,
omcadmin and sys.
As user root, examine the output from the cron

jobs in the following files for errors or messages:
more /var/mail/omcadmin
more /var/mail/root
more /var/mail/sys
[-]
Check the omc_db_maint log

file to ensure the following:

cd $OMC_TOP/logs
[-]
Execute the following commands as user

omcadmin:
tail -f $INFORMIXDIR/online.log_MIB
These log files should show that checkpoints are
completed successfully, in particular when the
server is initialized.
[-]
Check
PM statistics older than

a set timeframe are
deleted successfully.
Disk space is not being

consumed.
Applications are
connected and
reconnected
successfully when
required.
Check the IDS log files for

both PM and MIB INFORMIX
DB errors and checkpointing.
Continued
68P02901W19-S
14-3
Oct 2009
Table 14-1
Daily administration checklist (Continued)
Check
14-4
Method
Checked?
Check if the PM database is

online.

omcadmin:
omc_env
onstat | more
[-]
Check if the CM database is

online.

omcadmin:
mib_env
onstat | more
[-]
Perform a Level 2 backup of

the PM database.
[-]
Perform a Level 2 backup of

the CM database.
[-]
Perform a backup of the UNIX

filesystem.
Refer to Chapter 12 Backup Server Installation

and Configuration.
[-]
Check the status of the disk

mirroring and ensure all
submirrors are in an OK
state.

metastat | more
Refer to Checking disk mirroring on page 14-17.
[-]
Check the OMC-R log files

in /usr/omc/logs for unusual
output or error messages.
Refer to OMC-R log and error files on page 4-3.
[-]
Check the integrity of x25.

/opt/SUNWconn/bin/x25stat.
See x25stat output on page 2-76.
[-]
Check the system processor

hardware.

/usr/platform/sun4u/sbin/prtdiag -v.
[-]
Manually parse any unparsed

statistics files.
Refer to the checklist for manual parsing of

statistics in NE database maintenance on page
2-30.
[-]
68P02901W19-S
Oct 2009

To check weekly administration, follow the procedure in Weekly administration checklist in
Chapter 2 System management. Copy the checklist in Table 14-2, to record the checks.
Table 14-2

Method
Checked?
Check to see if the

Informix online logs are
rolled over successfully.

cd /usr/informix
ls -l online.log_MIB
ls -l online.log_OMCEnsure that online logs
exist with the format:
online.log_MIB.ddmmyyyy
[-]
Perform a backup of the

Unix file system.
Refer to Chapter 12 Backup Server Installation and

Configuration.
[-]
Archive and remove old

OMC-R log files on the
system processor and
GUI servers.

/usr/omc/current/sbin/archive -r -d 7 -t
/dev/rmt/0
This archives all log files older than seven days to tape
and removes the files after they have been archived.
[-]
Archive and remove

unloaded PM database
files on the system
processor.

maintain_script -a -d 7 -t /dev/rmt/0
This archives raw statistical bad header files older
than seven days.
maintain_script -r -d 7
This removes raw statistical bad header files older
than seven days after the archive.
[-]
Check the file system

capacity.

df -k
[-]
Check the disk usage

capacity of the system.

du |more
Terminate processes that are not required and are
consuming disk capacity.
[-]
Perform an archive of old

OMC-R user files.

find /home -mtime +14 -print >
/usr/tmp/listing
tar -c /usr/tmp/listing /dev/rmt/0
[-]
Check
Perform a Level 1 backup

of the PM database.
[-]

of the CM database.
[-]
System administrator
should monitor system
security.
68P02901W19-S
Refer to Security overview on page 2-36 for further

details about important security aspects.
[-]
14-5
Oct 2009

To check monthly administration, follow the procedure in Monthly administration checklist
in Chapter 2. Copy the checklist in Table 14-3, to record the checks.
Table 14-3
Check
Perform a backup of the
Unix file system.
14-6
Method
Checked?
Refer to Chapter 12 Backup Server Installation and

Configuration.
[-]

of the PM database.
[-]

of the CM database.
[-]
Change the standard

installation passwords for
user root, omcadmin,
and informix, and inform
the necessary people of
such changes.
Refer to Administering user accounts with usertool

on page 2-12.
[-]
Truncate the cron log

file.

tail -100 /var/cron/log > /tmp/cron_log
[-]
68P02901W19-S
Oct 2009
Checking cron jobs
Checking cron jobs
To check cron jobs, follow the procedure in Checking cron jobs on page 5-18 in Chapter 5. Copy
the checklist in Table 14-4, to record the checks.
Table 14-4
Cron job checklist

Check
Method
Checked?
Check if the cron daemon is

operational on the system.

ps -elf | grep cron
A /usr/sbin/cron process is displayed.
[-]
If the cron daemon is not

operational, it needs to be
started.

rm -f /etc/cron.d/FIFO
/usr/sbin/cron
[-]
Check if the CRONLOG

variable is set to YES to
ensure cron logging is done.

more /etc/default/cron | grep CRONLOG
[-]
If the CRONLOG variable is

set to NO, then it should be
changed.
As user root, edit the /etc/default/cron file

and change the CRONLOG setting to yes. Save
the file.
[-]
Check if the cron jobs are

setup correctly for user root.

crontab -l
[-]
Check if the cron jobs are

setup correctly for user
omcadmin.
As user omcadmin, execute the following

command:
crontab -l
[-]
Check if the system cronjobs

are setup correctly.
As user sys, execute the following command:

crontab -l
[-]
Check the /var/cron/log file to

ensure all crons executed are
logged to this file.

more /var/cron/log
[-]
Check if the /var/cron/log file

is rolled over to avoid disk
space issues.

cd /var/cron
ls -l
Log files should exist in the format
log.ddmmyyyy
[-]
Check the output of root's

cron jobs for any errors.

cd /var/mail
more root | grep cronjobname
[-]
Check the output of

omcadmin's cron jobs for
any errors.

cd /var/mail
more omcadmin | grep cronjobname
[-]
Check the output of the

system's cron jobs for any
errors.
As user sys, execute the following commands:

cd /var/mail
more sys | grep cronjobname
[-]
68P02901W19-S
14-7
Oct 2009
To check the OMC-R log files, use the procedure in Chapter 4. Copy the checklist in Table 14-5,
Table 14-5
OMC-R log files checklist

Method
Check
Check if omc log files are
created in the correct
directory paths.
Checked?
On the system processor:
[-]
OMC-R logs are placed in the /usr/omc/logs

directory.
Event logs are placed in the

/usr/omc/ne_data/ev_logs directory.
Informix logs are placed in the /usr/informix

directory.
OMC-R logs are placed in the /usr/omc/logs

directory.
Event logs are placed in the

/usr/omc/ne_data/ev_logs directory.
Check the BSS log files.

cd $OMC_TOP/logs/bss
tail -50 bssname_yyyymmdd
All command line activities performed on a particular
BSS can be viewed.
[-]
Check the Configuration

Management log file.

cd $OMC_TOP/logs
tail -50 cm_omcaudit_yyyymmdd
Configuration Management activities are logged to
this file.
[-]
When a cutover has been

performed, check the
cutover log file to see if it
has been successful.

cd $OMC_TOP/logs
more cutover.nnnn
This log file states whether the cutover has been
successful.
[-]
If problems are
experienced adding
or updating statistics in
the PM database, then
check for the existence of
dbms log files.

cd $OMC_TOP/logs
more dbms.nnnn
This dbms log file contains error information.
[-]
Check the
fpomcaudityyyymmdd
log file for successful
parsing of statistics files.

[-]
Continued
14-8
68P02901W19-S
Oct 2009
Table 14-5
OMC-R log files checklist (Continued)
Check
Method
Checked?
If problems occur
with Interprocess
communication, then
check if an IPC log file
exists in /usr/omc/logs/ipc
directory.

cd /usr/omc/logs/ipc
more ipclogfile name
These log files are usually of the format
AF032959.0001 (Internet address id). This log file
shows an error report.
[-]
Check the omc_db_maint

log file to ensure the
following:
As user rootWilling, execute the following

commands:
cd $OMC_TOP/logs
more omc_db_maint.yyyy.mm.d
[-]
Check the system

stats files in
/usr/omc/logs/sys_info
for system information.
Refer to OMC-R system information on page 13-8.
[-]
Check the pmguiaudit log

file for errors relating to
pmgui.

cd $OMC_TOP/logs
tail -50 pmguiaudityyyymmdd
[-]
Check the informix

online logs for DB errors
relating to the PM and
CM databases.
As user omcadmin, execute the following commands.

For the PM DB:
cd /usr/informix
more online.log_OMC.ddmmyyyy
For the CM DB:
cd /usr/informix
more online.log_MIB.ddmmyyyy
[-]
Check the omcaudit log

for messages relating to
OMC-R activity.

cd /usr/omc/logs
tail -f omcaudityyyymmdd
Refer to Restartable processes in this chapter for
further details about messages in the omc audit and
console log.
[-]
Monitor the disk space

used by the various log
files.
As user omcadmin, monitor the output of the

maintain_script cron job to ensure that it deletes
log files on a regular basis.
cd /var/mail
more omcadmin | grep maintain_script
[-]
PM statistics are
deleted successfully.
Disk space is not

being consumed.
Applications are
connected and
reconnected
successfully when
required.
68P02901W19-S
14-9
Oct 2009
Checking databases
Checking databases
Two checklists are provided in this section, one to check the PM database, and the other
to check the CM database.
Checklist for PM database

To check the PM database, follow the procedure in the section Checking the PM database on
page 8-34 in Chapter 8. Copy the checklist in Table 14-6, to record the checks.
Table 14-6
PM database checklist
Check
Method
Checked?
Check if the omc_env

alias is setup.
cat the /usr/omc/current/env/.cshrc file and ensure

it contains the following line: alias omc_env source
/usr/omc/config/global/pmInfxUserConfig.csh.
To run the updateLocalMaint script execute the
following command: setenv CM_LOCAL_MAINT TRUE.
[-]
Check if the PM
database is online.
As user omcadmin, enter the following:

omc_env
onstat | more
This utility reports that the database is in online mode.
[-]
Check the IDS log

file for errors and
checkpointing.

This log file shows that checkpoints are completed
successfully, in particular when the server is initialized.
[-]
Check if the IDS log

files are rolled over.

cd $INFORMIXDIR
Log files should exist of the format
online.log_OMC.ddmmyyyy.
[-]
Check the output of

the onmode_pm cron
job.

cd /var/mail
more root | grep onmode_pm.
[-]
Continued
14-10
68P02901W19-S
Oct 2009
Table 14-6
Checklist for PM database
PM database checklist (Continued)
Check
Check the
omc_db_maint log
file to ensure the
following:
Method
Checked?

cd $OMC_TOP/logs
more omc_db_maint.yyyy.mm.dd.
[-]
Check if the PM
sqlhosts file has the
correct entries for
the Informix Server.

more /usr/informix/etc/sqlhosts_OMC
Output should look similar to the example shown in PM
sqlhosts in Chapter 8.
[-]
Check the
/etc/services file
to ensure a port
number exists for the
PM IDS.

more /etc/services
inf7_OMC_serv 5000/tcp
[-]
Check the shared

memory structure of
the PM IDS.
As user informix, execute the following command:

onstat | more
Output should be similar to that shown in onstat output
for PM database section in Chapter 8.
[-]
Check the status of

the dbspaces and
chunks of the PM
IDS.

onstat -d
Output should be similar to that shown in onstat -d
output for PM database section in Chapter 8.
[-]
When performing an
archive of the PM DB
ensure the TAPEDEV
parameter is set to
/dev/rmt/0.

more /usr/informix/etc/onconfig | grep TAPEDEV.
[-]
PM statistics
are deleted
successfully.
Disk space
is not being
consumed.
Applications
are connected
and
reconnected
successfully
when required.
68P02901W19-S
14-11
Oct 2009
Checklist for CM database

To check the CM database, follow the procedure in the section Checking the CM database on
page 8-39 in Chapter 8. Copy the checklist in Table 14-7, to record the checks.
Table 14-7
CM database checklist
Check
Method
Checked?
Check if the
mib_env alias
is setup.
cat the /usr/omc/current/env/.cshrc file and ensure

it contains the following line: alias mib_env source
/usr/omc/config/global/mibInfxUserConfig.csh
To run the updateLocalMaint script execute the following
command: setenv CM_LOCAL_MAINT TRUE.
[-]
Check if the
MIB database
is online.
As user omcadmin, enter the following command:

mib_env
onstat | more
This utility reports that the database is in online mode.
[-]
Check the IDS log

file for errors and
checkpointing.

This log file should show that checkpoints are completed
successfully, in particular when the server is initialized.
[-]
Check if the IDS

log files are rolled
over.

cd $INFORMIXDIR
Log files should exist of the format
[-]
Check the
output of the
onmode_mib cron
job.

cd /var/mail
more root | grep onmode_mib
.
[-]
Check the
dbspace and
tblspace
allocation for the
CM IDS.

cd $DBMS_ROOT/SBIN
omc_db_ckspace mib
The output should be similar to that shown in the section
omc_db_ckspace utility on page 8-10.
[-]
Check if the CM
database sqlhosts
file has the
correct entries
for the Informix
Server.

more /usr/informix/etc/sqlhosts_MIB
Output should look similar to the example shown in the
section MIB sqlhosts file in Chapter 8.
[-]
Check the
/etc/services file
to ensure a port
number exists for
the CM IDS.

more /etc/services
inf7_MIB_serv 5010/tcp.
[-]
Check the shared

memory structure
of the CM IDS.

onstat | more
Output should be similar to that shown in the section onstat
output for CM database on page 8-41.
[-]
Continued
14-12
68P02901W19-S
Oct 2009
Table 14-7
CM database checklist (Continued)
Check
Method
Checked?
Check the status

of the dbspaces
and chunks of the
CM IDS.

onstat -d
Output should be similar to that shown in the section onstat
-d output for CM database on page 8-42.
[-]
When performing
an archive of the
CM DB ensure
the TAPEDEV
parameter is set
to /dev/rmt/0.

.
[-]
68P02901W19-S
14-13
Oct 2009
To check X.25 connectivity, follow the procedure in Checking X.25 connectivity on page 9-18 in
Chapter 9. Copy the checklist in Table 14-8 and use to record the checks.
Table 14-8
14-14
X.25 connectivity checklist
Check
Method
Checked?
Check the contents of the

x25_config file.

more x25_config
The file contents should look like the example shown
in Figure 9-2. The correct entries are required to
configure x25 connections.
[-]
Check the integrity of

x25.

Refer to x25stat output on page 2-76 for example,
output.
[-]
Check the status of the

network.

/usr/bin/netstat -a
Refer to OMC-R system information on page 13-8
in Chapter 12. For example, output of the netstat
command.
[-]
68P02901W19-S
Oct 2009
Checking core dumps
Checking core dumps
To check core dumps, follow the procedure in Checking core dumps in Chapter 12. Copy the
checklist shown in Table 14-9 to record the checks.
Table 14-9
Core dumps checklist
Check
Method
Checked?
Check the presence of

a core file when a fatal
error occurs during the
operation of either the
application programs or
the GUI modules.

cd /usr/omc/logs
ls -l core*
A core file should exist at the correct time the fatal
error occurred and should be in compressed format.
[-]
If an OMC-R process is
causing severe problems,
generate a core file of
the process.

where <filename> and <process_id> are of the
particular OMC-R process.
[-]
[-]
If the system processor

is having some kernel
problems, then generate
a core of the kernel.
Check the output of the
core_presence utility.

cd /var/mail
more omcadmin | grep core_presence
If a core file is generated, it exists in /usr/omc/logs.
[-]
Monitor old
core files in the
/usr/omc/logs/usraudit
logs directory.
As user root, monitor the core files in the

/usr/omc/logs
directory. If core files are not required, remove them
as they consume large amounts of disk space.
cd /usr/omc/logs
rm -f corefilename
[-]
68P02901W19-S
14-15
Oct 2009
Checking disk usage
Checking disk usage
To check disk usage, follow the procedure in Checking disk usage in Chapter 12. Copy the
checklist in Table 14-10, to record the checks.
Table 14-10
Disk usage checklist
Check
14-16
Method
Checked?
Check the disk usage of

the system.

du -k | more
[-]
Remove files that are not

required and use a lot of
disk space, for example,
old core files, log files,
statistic files.

cd directorypath
rm -f filename
[-]
Check the available free

memory.

[-]
Check whether the file

systems are full.

df -k | more
[-]
For file systems that are

over 100% full, check
for existing files that
are over 1 Mbyte and
analyze the possibility of
removing such files.

find filesystem -size +1048576c -print | more
[-]
68P02901W19-S
Oct 2009
To check disk mirroring, follow the procedure in Checking the CM database on page 8-39 in
Chapter 12. Copy the checklist in Table 14-11, to record the checks.
Table 14-11

Method
Checked?
Check the DiskSuite

status.

metastatA stable set of disksuite mirrors should look
similar to the example shown in the section metastat
output on page 13-47.
[-]
Check for any subdisks

that require maintenance
using the metastat
command. Subdisks
needing maintenance
have to be repaired.
Refer to Logical Vol Mgr troubleshooting on page

13-42 in Chapter 12 for the procedure to recover
a lost disk.
[-]
Check if the system has

at least 3 state databases
on each mirror.
As user root, execute the following command: metadb
[-]
If the system does not

have sufficient state
databases, create them.

metadb -a -f slice-1 slice 2 etc
For example,
metadb -f -d /dev/dsk/c1t2d0s3
/dev/dsk/c2t2d0s3
[-]
Check
68P02901W19-S
14-17
Oct 2009
Checking for successful parsing of statistics
Use a copy of this checklist to record that all steps to manually parse the statistics are performed.
Table 14-12
Check
Method
Checked?
Check if the parser process

is operational.

command:
ps -elf | grep + | grep Parser
[-]
Check if the FMPATH

environment variable is
set.

commands:
echo $FMPATH
This environment variable should be set to:
[-]
Check if any raw statistics

files have escaped
processing by the parser.

commands:
/bin/find
$OMC_TOP/ne_data/raw_stats/100,0
-name *.* -mtime +1 -print >
/usr/tmp/parser_list
[-]
Submit any files found

by the find command
that do not have a
suffix of .bad_header
or fatal_header to the
parser.

command:
$PM_ROOT/bin/pm_manual_parse filename
Check for any error messages from the
pm_manual_parse utility.
[-]
Check if the manual parse

was successful.

command:
Successful parsing output is shown in Parsing
output in Chapter 2.
[-]
Check that even if the

Parser process fails and
is restarted, the stats
collection and parsing
resumes without manual
intervention.

command:
tail -40 $SYS_LOG/fpomcaudityyyymmdd.
The log file shows that files are being parsed
again successfully.
[-]
Check if the fpomcaudit

logfile is rolled over
and old log files are
removed successfully
by the maintain_script
cronjob.

command:
cd /usr/omc/logs
ls -l fpomc*
[-]
Continued
14-18
68P02901W19-S
Oct 2009
Table 14-12
Manual parsing of statistics checklist (Continued)
Check
Method
Checked?
If the
parserDisconnectedToo
Long alarm is raised then
the
parser must be connected
to the
database.

command:
omc_env
db_disconnect
connect parser
[-]
Monitor the value of

the neighbor statistics
Refer to Using neighbor statistics on page 13-91

in Chapter 12 for further details about rasing
the maximum limit of neighbor statistics.
[-]
68P02901W19-S
14-19
Oct 2009
Recording details
Recording details
There are two procedures that require details of machines and accounts to be recorded and
kept for future reference. They are Setting up a night concentration centre in Chapter 2,
and Jump starting GUI server/client processor in Chapter 11.
Setting up a night concentration centre

The procedure to which these tables apply is described in Prerequisites for setup of a night
concentration centre in Chapter 2.
Copy the following tables, enter the details and store the information safely.
Record the hostname and IP addresses of the different processors for each remote OMC-R in
Table 14-13 and Table 14-14.
Table 14-13
Hostname and IP addresses for different processors
System
Hostname
IP address
local_sys
remote_sys
local_gui
Record the Username and User Identifier Number (UID) from the account of the user of the
remote OMC-R system in Table 14-14.
Table 14-14
User name and ID for remote system

Account
User name
UID
Account for user or remote

OMC-R system
14-20
68P02901W19-S
Oct 2009
Client and server partition details

The procedure to which these tables apply is described in JumpStarting GUI server/client
processor in Chapter 11.
Copy the following tables, enter the details and store the information safely.
Table 14-15
Client and server details
GUI client / server name
Table 14-16
Filesystem
GUI client / server IP address
Filesystem, Log and JumpStart details

Backup Log partitions
JumpStart partitions
/
/usr/omc
/gen
68P02901W19-S
Oct 2009
14-21
14-22
68P02901W19-S
Oct 2009
Index
Index
32000 statistics
checking for an excess . . . . . . . . .
3460 Fast'R modem . . . . . . . . . . . . .
3-7
8-32
A
ABORT_UPL_RL_IN_PROG . . .
activity tools . . . . . . . . . .
ADDINFO_IN_HEX environment
able . . . . . . . . . . . . . . .
alarms . . . . . . . . . . . . .
database . . . . . . . . . . .
disk space usage . . . . . . .
hardware failure . . . . . . .
licence violation. . . . . . . .
log files . . . . . . . . . . . .
neighbour statistics . . . . . .
OMC events . . . . . . . . . .
X.25 . . . . . . . . . . . . . .
. . .
. . .
vari. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
all ports busy . . . . . . . . . . . . . .

AT command
description . . . . . . . . . . . . . .
for MultiModem. . . . . . . . . . . .
ATC_TIMEOUT environment variable . .
audit limits . . . . . . . . . . . . . . .
audit log files
checking for success . . . . . . . . .
AUTORESYNC environment variable . .
AUTORESYNCDELAY environment variable . . . . . . . . . . . . . . . . . . .
AUTOSTART_PMGUI . . . . . . . . . .
. . . 6-6
. . 13-66
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-13
13-78
13-83
13-79
13-86
2-47
. 4-5
13-93
13-86
13-85
3-19
.
3-12
.
3-16
.
6-10
. 13-88
.
.
4-11
6-24
.
6-10
. . 6-6
B
Backing up the GUI Server File System . . 12-16
Overview to backing up file systems using
backup_MMI utility . . . . . . . . . . . 12-16
Procedure for backing up file systems using
backup_MMI utility . . . . . . . . . . . 12-17
Backing up the PM and CM Databases . . 12-55
Backing up the CM database . . . . . . 12-60
Backing up the PM Database . . . . . . 12-57
Checking and changing tape parameters . . . . . . . . . . . . . . . . . . . 12-55
Default DAT tape parameters . . . . . . 12-55
Level of backup . . . . . . . . . . . . . 12-55
Monitoring the active message log files for the
CM database . . . . . . . . . . . . . . 12-62
Backing up the PM and CM Databases (contd.)

Monitoring the active message log files for the
PM Database . . . . . . . . . . . . . . 12-59
Overview of IDS message log files for the CM
Database . . . . . . . . . . . . . . . . 12-61
Overview of IDS message log files for the PM
Database . . . . . . . . . . . . . . . . 12-58
View Archived message log files for the CM
Database . . . . . . . . . . . . . . . . 12-62
View Archived message log files for the PM
Database . . . . . . . . . . . . . . . . 12-59
bootup
troubleshooting . . . . . . . . . . . . . 13-28
C
Call Success Monitoring . . .
CALL_SUCCESS_THRESHOLD
variable . . . . . . . . . . . .
capacity control . . . . . . . .
68P02901W19-S
Oct 2009
. . . . . .
6-23
environment
. . . . . .
6-23
. . . . . .
2-46
Capacity control mechanism . . . . . . .

2-46
CD-ROM
eject failure . . . . . . . . . . . . . . . 13-50
CDE . . . . . . . . . . . . . . . . . . 2-3, 13-33
IX-1
Index
Configuring the SunFire and Netra System

Processors . . . . . . . . . . . . . . . . . 1-9
SunFire 4800/4900 and Netra 20/440. .
1-11
LAN . . . . . . . . . . . . . . . . . . .
1-24
core dumps . . . . . . . . . . . . . . . .
13-6
checking . . . . . . . . . . . . . 13-7, 14-15
removing . . . . . . . . . . . . . . . .
13-6
running process . . . . . . . . . . . . .
13-6
core_presence utility
core_presence (omcadmin) . . . . . . . . 5-7
corepresence utility . . . . . . . . . . .
13-6
Country Code
use in AT command . . . . . . . . . . .
3-14
COUNTRY_CODE . . . . . . . . . . . . . . 6-6
Create Home Dir
User Management . . . . . . . . . . .
2-14
critical processes . . . . . . . . . . . . .
2-49
Criticalstatseventsdiscarded (30078
alarm) . . . . . . . . . . . . . . . . . . . 13-87
cron jobs
adding . . . . . . . . . . . . . . . 5-12, 5-15
batch scheduler . . . . . . . . . . . . . . 5-9
command line . . . . . . . . . . . . . .
5-14
maintaining cron log files . . . . . . . .
5-16
modifying . . . . . . . . . . . . . . . .
5-12
omcadmin . . . . . . . . . . . . . . . . . 5-5
on GUI Processors . . . . . . . . . . . . 5-5
on the System Processor . . . . . . . . . 5-3
removing . . . . . . . . . . . . . . 5-13, 5-16
site_timesynch . . . . . . . . . . . . .
6-42
system . . . . . . . . . . . . . . . . . . 5-5
timesynch . . . . . . . . . . . . . . . .
6-41
verifying . . . . . . . . . . . . . . . .
5-14
crontab files
printing . . . . . . . . . . . . . . . . .
5-17
viewing . . . . . . . . . . . . . . . . .
5-14
.cshrc.private file . . . . . . . . . . . . . . 6-3
CSM_ENABLED environment variable . .
6-23
CSMMAIN process . . . . . . . . . . . .
6-23
CT_1208LOG . . . . . . . . . . . . . . .
6-11
Cyclic Neighbour Statistics feature . . . . 13-91
CDE (contd.)
installing . . . . . . . . . . . . . . . . 13-33
login failure . . . . . . . . . . . . . . . 13-36
troubleshooting . . . . . . . . . . . . . 13-34
Checklists
CM database . . . . . . . . . . . 8-39, 14-12
core dumps . . . . . . . . . . . . 13-7, 14-15
daily administration . . . . . . . . . 2-74, 14-3
disk mirroring. . . . . . . . . . . . . . 13-47
disk usage. . . . . . . . . . . . 13-23, 14-16
general administration . . . . . . . 2-74, 14-3
manual parsing of statistics . . . . . . .
2-31
monthly administration . . . . . . . 2-80, 14-6
OMC log files . . . . . . . . . . . . 4-7, 14-8
PM database . . . . . . . . . . . 8-34, 14-10
weekly administration. . . . . . . . 2-79, 14-5
X.25 connectivity . . . . . . . . . 9-18, 14-14
keeping software loads . . . . . . . . .
2-28
reasons for cleaning up loads . . . . . .
2-28
using a tarred software load . . . . . .
2-29
CM database
checking . . . . . . . . . . . . . . . .
8-39
checking and recovering tables . . . . . 13-70
defragmenting tables . . . . . . . . . . 13-73
monitoring space and fragmentation . . 13-70
onconfig file . . . . . . . . . . . . . . .
8-26
reading the database scheme . . . . . . 13-73
shutting down. . . . . . . . . . . . 8-18, 8-22
starting up . . . . . . . . . . . . 8-21 to 8-22
utilities . . . . . . . . . . . . . . . . . . 8-4
CM sqlhosts file . . . . . . . . . . . . . .
8-40
CM_NMC_AUTO_NUM environment
variable . . . . . . . . . . . . . . . . . .
6-11
Comment
User Management . . . . . . . . . . .
2-14
Common Desktop Environment
CDE . . . . . . . . . . . . . . . . . . . . 2-3
configuration files . . . . . . . . . . . . . 13-88
FM_audit.CNFG file . . . . . . . . . . . 13-88
X.25 . . . . . . . . . . . . . . . . . . . . 9-3
Configuring the OMC-R based LAN . . . .
1-24
D
daily procedures
core dump files . . . . . . . .
cron jobs . . . . . . . . . . .
database maintenance . . . .
OMC-R log files . . . . . . . .
System Processor hardware. .
UNIX file system maintenance
Database Applications menu . .
db_config files. . . . . . . . . .
db_disconnect utility . . . . . .
IX-2
db_disconnect utility (contd.)

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-29
.
1-29
.
1-28
.
1-29
.
1-29
.
1-29
.
2-19
. 13-94
. . 8-8
dbdisconnect utility . . . . . . . . . . .
8-16
db_pm_maint utility
dbpmmaint utility . . . . . . . . . . . . . 8-9
environment variable used by . . . . . .
6-10
dbms log files . . . . . . . . . . . . . 4-5, 13-52
DEF_GSM_CELL_ID environment variable . . . . . . . . . . . . . . . . . . . .
6-16
Detail
Serial Port Manager. . . . . . . . . . . . 3-4
68P02901W19-S
Oct 2009
Index
dial-in serial port . . . . . . . . . . . .

Disabling status of Consolidated Alarms.
Disk Activity Tool . . . . . . . . . . . .
Disk Capacity Tool . . . . . . . . . . .
Disk configuration
SunFire and Netra . . . . . . . . . .
disk mirroring
. . 3-9
.
6-30
. 13-66
. 13-67
.
disk mirroring (contd.)

checking . .
disk space
alarms . . .
checking disk
freeing up . .
usage limits .
1-19
. . . . . . . . . .
. . . .
usage.
. . . .
. . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
13-47, 14-17
. . . . . 13-79
. 13-23, 14-16
. . . . . 13-21
. . . . . 13-88
E
eeprom settings . . . . . . . . . . . . . .
3-22
EMDisconnectedFromDB alarm. . . . . . 13-83
ENABLE_AUTO_EMAIL_ON_REASSIGN
environment variable . . . . . . . . . . .
6-16
ENABLE_CYCLIC_NBRS environment
variable . . . . . . . . . . . . . . . . . . 13-91
ENABLE_CYCLIC_NBRS env . . . . . . . 6-6
ENABLERESYNC environment variable. .
6-24
enabling login
for modems . . . . . . . . . . . . . . .
3-17
environment variable
modifying . . . . . . . . . . . . . . . .
6-26
environment variables . . . . . . . . . .
6-24
ABORT_UPL_RL_IN_PROG . . . . . . . . 6-6
ADDINFO_IN_HEX . . . . . . . . . . .
6-13
ALG_WARNING . . . . . . . . . . . . .
6-13
ATC_TIMEOUT . . . . . . . . . . . . .
6-10
AU_APPLY_DELETES_FIRST . . . . . .
6-10
AUTORESYNC . . . . . . . . . . . . .
6-24
AUTORESYNCDELAY . . . . . . . . . .
6-10
AUTOSTART_PMGUI . . . . . . . . 6-6, 6-15
AX_LANG . . . . . . . . . . . . . . . .
6-15
BSS_NAMING. . . . . . . . . . . . . .
6-15
BSS_VER . . . . . . . . . . . . . . . .
6-15
CALL_SUCCESS_THRESHOLD . . . . .
6-23
CFG_KEEP_NMC_FILE . . . . . . . . . . 6-9
CFG_KEEP_STATS_FILE . . . . . . . . . 6-9
CM_NMC_AUTO_NUM . . . . . . . . .
6-11
COUNTRY_CODE . . . . . . . . . . 6-6, 6-15
CSM_ENABLED . . . . . . . . . . . . .
6-23
DBNAME . . . . . . . . . . . . . . 6-11, 6-15
DEF_GSM_CELL_ID. . . . . . . . . . .
6-16
DEFAULT_REMOVE_CLEARED_ALARM . . . . . . .
6-16
DEFAULT_REMOVE_CLEARED_ALARM_TIME . . . .
6-16
DEL_CELLX_FILES . . . . . . . . . . .
6-11
DOUBLE_CLICK_NEXT . . . . . . . . .
6-16
ENABLE_AUTO_EMAIL_ON_REASSIGN . . . . . . . . . . . . . . . . . .
6-16
ENABLE_CYCLIC_NBRS . . . . . . . . . 6-6
ENABLERESYNC . . . . . . . . . . . .
6-24
FM_CPU_AUDIT . . . . . . . . . . . .
6-22
FM_IERROR_ALLOWED . . . . . . . .
6-22
FM_MEM_AUDIT . . . . . . . . . . . .
6-22
FM_OERROR_ALLOWED . . . . . . . .
6-22
68P02901W19-S
Oct 2009
environment variables (contd.)

FM_OHUNG_ALLOWED . . . . . . . .
INDFORMIXSERVER . . . . . . . . . . .
INFORMIXDIR . . . . . . . . 6-6, 6-11,
LANGUAGE . . . . . . . . . . . . . . .
log files . . . . . . . . . . . . . . . . . .
MAX_AUTO_RESYNCS . . . . . . . . .
MAX_BOOTLOADS . . . . . . . . . . . .
MAX_CSFP_BLP . . . . . . . . . . . . .
MAX_UPLOADS_PER_CHAN . . . . . . .
MIN_TOTAL_CS . . . . . . . . . . . . .
MMI_ALARM_STATE_WIDTH . . . . . .
MMI_CLEAR_INACTIVE_FMIC . . . 6-7,
MMI_ENABLE_FMIC . . . . . . . . . . .
MMI_EVENT_ADDITIONAL_INFO_WIDTH . . . . . . . . .
MMI_EVENT_ID_WIDTH . . . . . . . .
MMI_EVENT_INFO_WIDTH. . . . . . .
MMI_EVENT_OBJ_CLASS_WIDTH . . .
MMI_EVENT_OBJ_INSTANCE_WIDTH . . . . . . . . . . . .
MMI_EVENT_OPERATOR_NAME_WIDTH . . . . . . . . . .
MMI_EVENT_TIME_WIDTH. . . . . . .
MMI_EVENT_TYPE_WIDTH. . . . . . .
MMI_EVT_FILTER_NUM_LOGS . . . . .
MMI_START_WINDOW_AS_UNSPLIT . .
NETWORK_CODE. . . . . . . . . . 6-7,
NO_OF_PARSERS . . . . . . . . . . . . .
NX_ENABLE_TIMESLOTS . . . . . . .
OMC_TOP . . . . . . . . . . . 6-8, 6-12,
OMCAUDIBLESEVERITY . . . . . . . .
OMCFEATURES . . . . . . . . . . . .
OMCREDRAW. . . . . . . . . . . . . .
PER_SITE_AUDIT . . . . . . . . . . . .
PER_SITE_AUDIT_DEBUG . . . . . . .
PM_HOURLY_STATS . . . . . . . . . . .
PM_MAX_NEIGHBOURS . . . . . . . . .
PRINTER . . . . . . . . . . . . . . . .
RECIPROCATE_NBR . . . . . . . . . .
REGION. . . . . . . . . . . . . . . . .
RL_LOGCMDS . . . . . . . . . . . . .
RL_LOGRESPS . . . . . . . . . . . . .
RL_SESSIONS . . . . . . . . . . . . .
RL_TIMER_DT . . . . . . . . . . . . .
RL_TIMER_NC . . . . . . . . . . . . .
6-23
6-6
6-16
6-16
4-6
6-24
6-6
6-7
6-7
6-23
6-17
6-17
6-7
6-17
6-17
6-18
6-18
6-18
6-18
6-18
6-18
6-18
6-18
6-18
6-7
6-12
6-19
6-19
6-19
6-19
6-12
6-12
6-8
6-8
6-19
6-13
6-19
6-21
6-21
6-21
6-21
6-22
IX-3
Index
/etc/dfs/dfstab file .
/etc/hosts file . . .
/etc/hosts.equiv file
event alarms . . .
event log files . . .
troubleshooting .
environment variables (contd.)

SITE_NAMING . . . . .
STATE_ON_AUDIT . . .
SUB_RES_TIME. . . . .
TIMER . . . . . . . . .
TTY_FILTER. . . . . . .
UPL_KEEP STATS_FILE .
USE_LONG_SITE_NAME
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-20
. . 6-9
. . 6-9
.
6-24
.
6-20
.
6-10
.
6-13
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-44
13-38
13-38
13-86
. 4-5
13-24
.
.
6-22
6-22
6-22
F
File Manager . . . . . . . . . . . . .
file systems
freeing space . . . . . . . . . . . .
file transfers
and modems . . . . . . . . . . . .
FM_audit.CNFG file . . . . . . . . . .
FM_CPU_AUDIT environment variable
. .
2-22
FM_IERROR_ALLOWED environment
variable . . . . . . . . . . . . . . . . .
FM_MEM_AUDIT environment variable.
FM_OERROR_ALLOWED environment
variable . . . . . . . . . . . . . . . . .
FM_OHUNG_ALLOWED environment
variable . . . . . . . . . . . . . . . . .
function keys . . . . . . . . . . . . . .
. . 13-21
. .
3-18
. . 13-88
. .
6-22
.
6-23
. . 6-3
G
gcore command . . . .
Graph Tool . . . . . .
saving configurations
Group ID
Group Management .
Group Management . .
adding . . . . . . .
deleting . . . . . . .
modifying . . . . . .
Overview . . . . . .
renaming . . . . . .
Group Name
Group Management .
GUI
ensuring the correct colours appear . .
2-13
GUI processes
environment variables . . . . . . . . .
6-13
GUI Processors
processes . . . . . . . . . . . . 13-25, 13-27
shutting down. . . . . . . . . . . . . . . 7-9
single user mode . . . . . . . . . . . . . 7-9
GUI server
rollback . . . . . . . . . . . . . . . . .
2-67
GUI Server
log files . . . . . . . . . . . . . . . . . . 4-5
. . . . . . . . . .
13-6
. . . . . . . . . . 13-53
. . . . . . . . . . 13-57
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . 2-9
. . 2-9
.
2-10
.
2-11
.
2-10
. . 2-8
.
2-10
. . . . . . . . . . .
2-9
H
Hard copy listings. . .
hardware failure alarm
history file
loading . . . . . . .
home directories
access failures . . .
Horizontal Bar Graph
Graph Tool . . . . .
host name
changing . .
hosts file . . .
hosts.equiv file
HSI/S cards
replacing . .
. . . . . . . . . .
1-34
. . . . . . . . . . 13-86
. . . . . . . . . . 13-54
. . . . . . . . . . 13-34
. . . . . . . . . . . . . .
11-8
. . . . . . . . . . . . . . 13-38
. . . . . . . . . . . . . . 13-38
. . . . . . . . . . . .
9-7, 9-17
. . . . . . . . . . 13-61
I
INFORMIX database
IX-4
68P02901W19-S
Oct 2009
Index
INFORMIXDIR . . . . . . . . . . . . .
INFORMIXSERVER . . . . . . . . . . .
Installing a modem . . . . . . . . . . .
Introduction to non user configurable
Introduction to setting the status of the
Consolidated Alarms . . . . . . . . . .
IPC log files . . . . . . . . . . . . . . .
INFORMIX database (contd.)

alarms . . . . . . . .
CM database . . . . .
failure . . . . . . . . .
GUI Processor files . .
log files . . . . . . . .
PM database . . . . .
Quiescent mode . . . .
routine procedures . .
System Processor files
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . 13-83
. .
8-13
. . 13-52
. .
8-15
. . . 4-5
. .
8-13
. .
8-16
1-28, 1-30
. .
8-14
. .
. .
. .
.
6-6
6-6
3-7
6-31
.
6-29
. . 4-6
L
LAN
failure . . . . . . . . .
files . . . . . . . . . .
testing connection . .
LANGUAGE environment
Level123Failure alarm .
Line Plot
Graph Tool . . . . . .
Local GUI server
rollback . . . . . . . .
log book. . . . . . . . .
log files
alarm logs. . . . . . .
audit . . . . . . . . .
dbms . . . . . . . . .
environment variables
log files (contd.)

. . . . .
. . . . .
. . . . .
variable
. . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
13-38
13-38
13-37
6-16
13-85
. . . . . . . . . 13-60
. . . . . . . . .
. . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-67
1-26
. . . 4-5
. .
4-11
4-5, 13-52
. . . 4-6
event logs . . . . . . . . . .
INFORMIX database logs . .
IPC logs . . . . . . . . . . .
maintaining . . . . . . . . .
routine procedures . . . . .
sys_info files . . . . . . . .
login
corrupt message . . . . . .
failure . . . . . . . . . . . .
ids . . . . . . . . . . . . .
password fails. . . . . . . .
login prompt
troubleshooting for modems
LowerLimitDiskUsage alarm .
lp command . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-5
4-5
4-6
5-6
1-29
13-8
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-24
. 13-36
.
2-40
.
3-24
. . . . . .
3-21
. . . . . . 13-79
. . . . . .
3-27
M
maintain_script utility . . . . . . . . . . . . 5-6
MAX_BOOTLOADS environment variable . . 6-6
MAX_CSFP_BLP environment variable . . . 6-7
MAX_UPLOADS_PER_CHAN environment
variable . . . . . . . . . . . . . . . . . . . 6-7
metrics
selecting . . . . . . . . . . . . . . . . 13-58
viewing . . . . . . . . . . . . . . . . . 13-59
MIN_TOTAL_CS environment variable . .
6-23
Miscellaneous daily procedures . . . . . .
1-29
MMI processes
GUI processes. . . . . . . . . . . . . .
6-13
mmi utility . . . . . . . . . . . . . . . . . 7-4
MMI_ALARM_STATE_WIDTH environment
variable . . . . . . . . . . . . . . . . . .
6-17
MMI_CLEAR_INACTIVE_FMIC environment
variable . . . . . . . . . . . . . . . . 6-7, 6-17
MMI_ENABLE_FMIC environment variable . . . . . . . . . . . . . . . . . . . . . 6-7
MMI_EVENT_ADDITIONAL_INFO_WIDTH
6-17
68P02901W19-S
Oct 2009
MMI_EVENT_ID_WIDTH environment
variable . . . . . . . . . . . . . . . . . .
6-17
MMI_EVENT_INFO_WIDTH environment
variable . . . . . . . . . . . . . . . . . .
6-18
MMI_EVENT_OBJ_CLASS_WIDTH environment
variable . . . . . . . . . . . . . . . . . .
6-18
MMI_EVENT_OBJ_INSTANCE_WIDTH
6-18
MMI_EVENT_OPERATOR_NAME_WIDTH
6-18
MMI_EVENT_TIME_WIDTH environment
variable . . . . . . . . . . . . . . . . . .
6-18
MMI_EVENT_TYPE_WIDTH environment
variable . . . . . . . . . . . . . . . . . .
6-18
MMI_EVT_FILTER_NUM_LOGS environment
variable . . . . . . . . . . . . . . . . . .
6-18
MMI_START_WINDOW_AS_UNSPLIT
6-18
mnemonic process name . . . . . . . 2-55, 6-27
modem
adding . . . . . . . . . . . . . . . . . . 3-6
communicating . . . . . . . . . . . . .
3-10
IX-5
Index
modem (contd.)
modem (contd.)
configuring . . . . . . . .
controlling access . . . . .
data links . . . . . . . . .
disconnection problems . .
does not pick up . . . . .
eeprom settings . . . . . .
enabling login . . . . . . .
hangs up . . . . . . . . .
installing . . . . . . . . .
permission denied. . . . .
physical connection . . . .
rates . . . . . . . . . . .
remote connection and file
setup . . . . . . . . . . .
SPARCstation setup . . . .
tipping . . . . . . . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
transfers
. . . . .
. . . . .
. . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-10
3-11
3-7
3-23
3-23
3-22
3-17
3-22
3-7
3-23
3-8
3-8
3-18
3-11
3-8
3-23
troubleshooting . . . .
monitor_ct_logs utility .
monitor_diskspace utility
monthly procedures . . .
UNIX file system . . .
Motorola
contacting. . . . . . .
Motorola 3460 modem .
mounting a device
troubleshooting . . . .
MT5634ZBA modem . .
MultiModem . . . . . .
multiuser mode
GUI Processor . . . .
System Processor . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-19
. . 5-7
. . 5-7
.
1-32
.
1-32
. . . . . . . . .
. . . . . . . . .
13-3
3-12
. . . . . . . . . 13-49
. . . . . . . . .
3-14
. . . . . . . . .
3-14
. . . . . . . . . .
. . . . . . . . . .
7-9
7-9
N
nbr_entity table
resizing . . . . . . . . . . . . . . .
nbr_statistics table . . . . . . . . . .
resizing . . . . . . . . . . . . . . .
archiving/removing an NE database
PM database . . . . . . . . . . . .
removing NE fallback software . . .
routine procedures . . . . . . . . .
NE maintenance
synchronizing times . . . . . . . . .
neighbour statistics . . . . . . . . . .
alarm . . . . . . . . . . . . . . . .
enabling. . . . . . . . . . . . . . .
enabling cyclically . . . . . . . . .
limitations on use . . . . . . . . . .
raising maximum limit . . . . . . .
NEIGHBOUR variable. . . . . . . . .
Netra System Processor
configuring . . . . . . . . . . . . .
Network File System

NFS . . . . . . . . . . . . . . . . . . .
network status . . . . . . . . . . . . . .
NFS . . . . . . . . . . . . . . . . . . . .
stale file handling . . . . . . . . . . . .
NHA tool . . . . . . . . . . . . . . . . .
Night concentration centre
configuration . . . . . . . . . . . . . .
naming conventions . . . . . . . . . . .
prerequisites for setup . . . . . . 2-61,
NIS
commands . . . . . . . . . . . . 11-5,
testing NIS server. . . . . . . . . . . .
troubleshooting . . . . . . . . . . . . .
NIS domain
adding a group . . . . . . . . . . . . .
adding a user . . . . . . . . . . . . . .
no login prompt . . . . . . . . . . . . . .
NX_ENABLE_TIMESLOTS environment
variable . . . . . . . . . . . . . . . . . .
. . 13-94
. . 13-94
. . 13-94
.
.
.
.
.
.
.
.
2-30
2-30
2-31
1-33
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-42
13-91
13-93
13-91
13-91
13-91
13-94
13-94
. . .
1-9
2-44
13-11
2-44
13-24
13-91
2-60
2-61
14-20
11-11
11-10
11-11
11-9
11-8
3-21
6-12
O
OMC
capacity . . . . . . .
OMC event alarms . .
OMC processes . . . .
displaying . . . . . .
errors . . . . . . . .
printing . . . . . . .
restarting . . . . . .
shutting down. . . .
starting up . . . . .
IX-6
omc_db_ckspace utility (contd.)

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . .
2-46
. . . 13-86
. . . 13-27
7-13, 13-25
. . . 13-25
. . .
2-35
2-49 to 2-50
. . .
7-12
. . .
7-12
omcdbckspace utility . . . . .
automatic (cron) procedure . .
omc_db_maint (root) . . . . .
omcdbmaint utility . . 8-6 to
OMC-R
JumpStart CD . . . . . . . . .
software requirements . . . .
OMC-R remote user accounts
deletion . . . . . . . . . . . .
. . . . .
8-10
. . . . .
8-23
. . . . . . 5-8
8-7, 8-23 to 8-24
. . . . . .
. . . . . .
. . . . .
1-7
1-7
2-67
68P02901W19-S
Oct 2009
Index
OMC-R users
user accounts . . . . . . . . . . . .
OMC_TOP environment variable . . .
OMCAUDIBLESEVERITY environment
variable . . . . . . . . . . . . . . . .
OMCFEATURES environment variable
OMCOverloadedEventsDiscarded
alarm . . . . . . . . . . . . . . . . .
OMCOverloadedWithEvents alarm . .
OMCREDRAW environment variable .
omctool utility. . . . . . . . . . . . .
onconfig file . . . . . . . . . . . . . .
. .
. .
1-33
6-19
. .
. .
6-19
6-19
onmode_mib utility . . . . . . .
onmode_pm utility . . . . . . .
onmonitor utility . . . . . . . .
onperf_mib utility . . . . . . . .
onperf_pm utility . . . . . . . .
onstat output for CM database .
onstat output for PM database .
Operator workstations . . . . .
Optional processors . . . . . . .
. . 13-87
. . 13-86
. .
6-19
2-55, 6-27
. .
8-26
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . 5-7
. . . 5-6
8-5, 8-16
. . 13-53
. . 13-53
. .
8-42
. .
8-37
. .
8-41
. .
8-35
. . . 1-6
. . . 1-7
P
Packet Switch passwords . . . . . . . . .
2-43
parserDisconnectedTooLong alarm . . . . 13-83
password
login failure . . . . . . . . . . . . . . .
3-24
Password
User Management . . . . . . . . . . .
2-14
passwords. . . . . . . . . . . . . . . . .
2-42
conventions . . . . . . . . . . . . . . .
2-42
Packet Switch . . . . . . . . . . . . . .
2-43
routine procedures . . . . . . . . . . .
1-32
permission denied or link down . . . . . .
3-23
Pie Chart
Graph Tool . . . . . . . . . . . . . . . 13-63
PM database
adding extra logical logs to DB
server . . . . . . . . . . . . . . . . . . 13-76
checking . . . . . . . . . . . . . . . .
8-34
checking and recovering tables . . . . . 13-70
configuration files . . . . . . . . . . . . 13-94
directory structures . . . . . . . . . . .
8-13
emptying and defragmenting statistics
tables . . . . . . . . . . . . . . . . . . 13-74
maintenance . . . . . . . . . . 8-3, 8-6 to 8-7
monitoring space and fragmentation . . 13-70
onconfig file . . . . . . . . . . . . . . .
8-26
reading the database schema . . . . . . 13-73
shutting down. . . . . . . . . . . . 8-16, 8-22
starting up . . . . . . . . . . . . . 8-19, 8-22
status . . . . . . . . . . . . . . . . . . 13-14
utilities . . . . . . . . . . . . . . . . . . 8-4
PM raw statistics maintenance . . . . . .
1-33
PM sqlhosts file . . . . . . . . . . . . . .
8-35
PM statistics
parsing . . . . . . . . . . . . . . . 2-30, 8-11
pm_manual_parse utility . . . . . . . .
8-11
troubleshooting . . . . . . . . . . . 4-5, 13-52
PM_HOURLY_STATS environment variable . . . . . . . . . . . . . . . . . . . . . 6-8
68P02901W19-S
Oct 2009
pm_manual_parse utility . . . . . . . . .
8-11
PM_MAX_NEIGHBOURS environment
variable . . . . . . . . . . . . . . . . . . . 6-8
PMMAXNEIGHBOURS environment
variable . . . . . . . . . . . . . . . . . 13-94
PMCyclic . . . . . . . . . . . . . . . . . 13-91
PMDisconnectedFromDB alarm . . . . . . 13-83
port monitor services . . . . . . . . . . . . 3-9
power failure . . . . . . . . . . . . . . .
2-57
graceful shutdown . . . . . . . . . . .
2-57
on all processors . . . . . . . . . . . . 13-97
on GUI server and clients . . . . . . . . 13-98
on the System Processor . . . . . . . . 13-98
power supply unit failure . . . . . . . . 13-98
restarting GUI sessions . . . . . . . . . 13-97
restarting the OMC-R . . . . . . . . . . 13-97
UPS . . . . . . . . . . . . . . . . . . . 13-98
Primary Group
User Management . . . . . . . . . . .
2-14
Print Manager
disabling . . . . . . . . . . . . . . . . 13-34
enabling. . . . . . . . . . . . . . . . . 13-34
printer
adding . . . . . . . . . . . . . . . . .
3-25
address . . . . . . . . . . . . . . . . .
3-25
checking installation . . . . . . . . . .
3-27
configuration file . . . . . . . . . . . .
3-27
configuring . . . . . . . . . . . . . . .
3-26
name . . . . . . . . . . . . . . . . . .
3-25
PRINTER environment variable . . . . . .
6-19
printer.def file . . . . . . . . . . . . . . .
3-27
printing . . . . . . . . . . . . . . . . . .
3-27
processes
OMC processes . . . . . . . . . . 2-49, 13-26
processor times
synchronizing . . . . . . . . . . . . . .
6-36
IX-7
Index
Q
Q3 naming . . . . . . . . . . . . . . . .
6-11
Query Tree . . . . . . . . . . . . . . . . 13-65
Quiescent mode
INFORMIX database . . . . . . . . . .
8-16
R
RC.CNFG file . . . . . . . . . . . . .
REGION environment variable . . . .
remote connection . . . . . . . . . .
remote login
SPARCstation corruption . . . . . .
Remote monitoring station
configuration . . . . . . . . . . . .
restartable processes . . . . . . . . .
ResyncCtrl process . . . . . . . . . .
.rhosts file
rhosts file . . . . . . . . . . . . . .
RL_LOGCMDS environment variable .
RL_LOGRESPS environment variable .
RL_SESSIONS environment variable .
RL_TIMER_DT environment variable .
RL_TIMER_NC environment variable .
RLOGIN variables . . . . . . . . . . .
roll_online utility . . . . . . . . . . .
roll_paging_log utility . . . . . . . . .
. .
. .
. .
6-24
6-19
3-18
. .
3-22
. .
. .
. .
2-59
2-49
6-24
.
.
.
.
.
.
.
.
.
routine procedures
complete file backup . . . .
daily . . . . . . . . . . . .
hardware maintenance . . .
INFORMIX database . . . .
monthly . . . . . . . . . . .
NE database maintenance .
system configuration . . . .
system core dumps . . . . .
UNIX file system . . . . . .
UNIX file systems . . . . . .
weekly . . . . . . . . . . .
Routine system administration
dures . . . . . . . . . . . . .
RTF limit . . . . . . . . . . .
updating licence . . . . . .
run levels . . . . . . . . . . .
Running Night Concentration
procedure . . . . . . . . . .
. 13-38
.
6-21
.
6-21
.
6-21
.
6-21
.
6-22
.
6-21
. . 5-7
. . 5-7
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
proce. . . .
. . . .
. . . .
. . . .
. .
. .
. .
1-28,
. .
. .
. .
. .
. .
. .
. .
.
.
.
.
1-33
1-28
1-34
1-30
1-32
1-33
1-34
1-34
1-32
1-30
1-30
.
.
.
1-26
2-46
2-47
7-3, 7-7
. . . . . .
2-66
S
sar_per_day utility . . . . . . . . . . . . . 5-7
savecore utility . . . . . . . . . . . . . .
13-6
Secondary Groups
User Management . . . . . . . . . . .
2-14
security . . . . . . . . . . . . . . . . 2-36, 2-44
login ids. . . . . . . . . . . . . . . . .
2-41
Security related weekly procedures . . . .
1-31
serial port . . . . . . . . . . . . . . . . . . 3-3
adding a modem . . . . . . . . . . . . . 3-6
setting baud rate . . . . . . . . . . . . . 3-6
Serial Port Manager. . . . . . . . . . . . . 3-3
Session Activity Tool . . . . . . . . . . . 13-68
Setting status of Consolidated Alarms . .
6-29
Setting up a Night Concentration Centre
creating a new account . . . . . . . . .
2-64
exporting file changes. . . . . . . . . .
2-64
updating host file entries . . . . . . . .
2-63
shutdown utility . . . . . . . . . . . . . 7-4, 7-7
Single platform processor
rollback . . . . . . . . . . . . . . . . .
2-68
single user mode
GUI Processor . . . . . . . . . . . . . . 7-9
System Processor . . . . . . . . . . . . . 7-9
site_timesynch utility
IX-8
site_timesynch utility (contd.)

site_timesynch (omcadmin) . . . . . . .
Deleting a Group Backup client . . . . .
Enabling or Disabling a Group
Backup . . . . . . . . . . . . . . . . .
software processes
OMC processes . . . . . . . . . . . . .
Solaris Logical Vol Mgr disk configuration
SPARCstation
corruption. . . . . . . . . . . . . . . .
setup . . . . . . . . . . . . . . . . . .
Status Tool . . . . . . . . . . . . . . . .
StorEdge Enterprise Backup
Style Manager . . . . . . . . . . . . . .
subscription lists
backing up . . . . . . . . . . . . . . .
subscriptions
backing up . . . . . . . . . . . . . . .
SunFire and Netra
disk configuration . . . . . . . . . . . .
SunFire System Processor
5-8
12-11
12-10
13-25
13-42
3-22
. 3-8
13-64
13-51
2-21
8-32
8-32
1-19
68P02901W19-S
Oct 2009
Index
SunFire System Processor (contd.)

configuring . . . . . . . . .
SunLink X.25 . . . . . . . . .
X.25 . . . . . . . . . . . . .
swap space
System Processor . . . . . .
synchronizing processor times
sys_info files . . . . . . . . .
CM database status . . . . .
network status . . . . . . .
PM database status . . . . .
system processes . . . . . .
System Processor . . . . . .
X.25 communications . . . .
systat utility . . . . . . . . . .
system core dumps
core dumps . . . . . . . . .
system processes
OMC software processes . .
sys_info files . . . . . . . .
System Processor . . . . . . .
architecture . . . . . . . . .
System Processor (contd.)
. . . . . . .
. . . . . . .
. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. .
. .
. .
. .
. .
. .
. .
. .
. .
5-6,
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
core . . . . . . . . . . . . . . . . . . .
13-6
displaying status . . . . . . . . . . . . 13-99
6-31
hardware failure alarm . . . . . . . . . 13-86
log files . . . . . . . . . . . . . . . . . . 4-3
OMC-R specifications
SUN ULTRA ENTERPRISE 3000 . . . . 1-4
processes . . . . . . . . 13-9, 13-25 to 13-26
run level . . . . . . . . . . . . . . . . . 7-3
shutting down. . . . . . . . . . . . . 7-6, 7-9
single user mode . . . . . . . . . . . . . 7-9
starting up . . . . . . . . . . . . . . 7-5, 7-9
swap space . . . . . . . . . . . . . . . 13-14
sys_info files . . . . . . . . . . . . . .
13-8
system resources . . . . . . . . . . . . 13-12
system resources
System Processor . . . . . . . . . . . . 13-12
system time
setting . . . . . . . . . . . . . . . . .
6-36
synchronizing . . . . . . . . . . . . 6-36, 6-41
system uptime . . . . . . . . . . . . . .
13-8
13-14
6-36
13-8
13-17
13-11
13-14
13-9
13-8
13-10
13-19
. . . . . .
.
.
.
.
1-9
9-3
9-3
13-6
. 13-26
.
13-9
. . 1-4
.
13-9
T
Template
Serial Port Manager. . . .
time zone
setting . . . . . . . . . .
TIMER environment variable
tipping a modem . . . . . .
. . . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
traffic channel capacity

RTF limit . . . . . . . . . . . . .
troubleshooting
for modems . . . . . . . . . . . .
TTY_FILTER environment variable .
Typical hardware for OMC-R system
3-4
6-37
6-24
3-23
. . .
2-46
. . .
3-19
. . .
6-20
. . . . 1-4
U
uname command . . . . . . . . . . . . .
13-9
update_mib_statistics utility. . . . . . . . . 5-7
UPL_KEEP_STATS_FILE environment
variable . . . . . . . . . . . . . . . . . .
6-10
UpperLimitDiskUsage alarm . . . . . . . 13-79
UPS . . . . . . . . . . . . . . . . . 2-57, 13-98
setup . . . . . . . . . . . . . . . . . .
2-58
uptime . . . . . . . . . . . . . . . . . .
13-8
user accounts
adding . . . . . . . . . . . . . . . . .
1-33
checking for old files . . . . . . . . . .
2-23
deleting . . . . . . . . . . . . . . . . .
1-33
user environment
customising . . . . . . . . . . . . . . . . 6-3
User ID
User Management . . . . . . . . . . .
2-13
68P02901W19-S
Oct 2009
User Management . . . . . . . . . 2-12 to 2-13

adding . . . . . . . . . . . . . . . . .
2-15
deleting . . . . . . . . . . . . . . . . .
2-16
modifying . . . . . . . . . . . . . . . .
2-15
renaming . . . . . . . . . . . . . . . .
2-16
User Name
User Management . . . . . . . . . . .
2-13
user passwords . . . . . . . . . . . . . .
2-42
user profiles
errors . . . . . . . . . . . . . . . . . . 13-34
User-configurable environment variables . . 6-5
System processes and PM database configurable
variables . . . . . . . . . . . . . . . . . 6-5
usertool . . . . . . . . . . . . . . . . . . . 2-8
/usr/gsm/logs/sys_info files . . . . . . . .
13-8
utmpx entry . . . . . . . . . . . . . . . .
3-24
IX-9
Index
V
Vertical Bar Graph
Graph Tool . . . . . . . . . . . . . . . 13-62
Virtual Processor Activity Tool . . . . . . 13-69
W
weekly procedures
database files . . . . . . . . . . . . . .
weekly procedures (contd.)

1-30
UNIX file system . . . . . . . . . . . .
1-30
X
X.25 . . . . . . . . . . . . . . . .
alarm . . . . . . . . . . . . . .
checking connectivity . . . . . .
commands . . . . . . . . . . .
configuration . . . . . . . . . .
configuration files . . . . . . . .
directory structure . . . . . . .
failure . . . . . . . . . . . . . .
integrity of X.25 communications
LAPB configuration . . . . . . .
OMC implementation . . . . . .
starting . . . . . . . . . . . . .
stopping. . . . . . . . . . . . .
IX-10
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . 9-3
. 13-85
.
9-18
. . 9-7
. . 9-3
. . 9-3
. . 9-8
. 13-39
. 13-10
.
9-15
. . 9-5
9-7, 9-11
9-7, 9-12
X.25 (contd.)
updating link configuration
X25
from HSI failure
Recovery . . . . . . . .
x25_config file. . . . . . . .
x25stat utility . . . . . . . .
x25tool . . . . . . . . . . .
starting up x25tool . . . .
starting X.25 . . . . . . .
stopping X.25 . . . . . . .
x25trace utility . . . . . . .
.Xdefaults.private file . . . .
. . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9-7, 9-13
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9-19
. 9-3
13-39
. 9-9
. 9-9
9-11
9-12
13-39
. 6-3
68P02901W19-S
Oct 2009

Omc-R System Adm

Загружено:

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

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

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

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

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

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

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

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

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

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

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

Omc-R System Adm

Загружено:

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

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

OMC-R System Administration

2009 Motorola, Inc. All Rights Reserved.

Operating Information: OMC-R System Administration

Chapter 1: Introduction to the OMC-R

Overview to SunFire and Netra configuration . . . . . . .

Chapter 2: System management

Operating Information: OMC-R System Administration

Deleting a user account . . . . . . . . . . . . . . .

Graceful shutdown on mains failure . . . . . . . . . . . . . .

Chapter 3: Ancillary Devices

Operating Information: OMC-R System Administration

Chapter 4: OMC-R Log Files

Chapter 5: OMC-R Cron Jobs

Printing crontab files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 6: OMC-R Environment variables

Chapter 7: System startup and shutdown

Operating Information: OMC-R System Administration

Switching to PROM mode . . . . . . . . . . .

Chapter 8: Database Management

Checking the CM database. . . . . . . . .

Chapter 9: X.25 management

Chapter 10: OMC Utilities

Operating Information: OMC-R System Administration

Chapter 11: Network Information Services (NIS)

Chapter 12: Backup Server Installation and Configuration

Manual backup of Informix databases . . . . . . . . . . . . . . . . . . .

Chapter 13: Troubleshooting

Operating Information: OMC-R System Administration

File access problems . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 14: Checklists

1-1: Typical hardware architecture of OMC-R SunFire/Netra system. . . .

9-6: Link editor window . . . . . . . . . .

1-1: OMC-R specifications (maximum values) . . . . . . . . . . . . . . . . .

Disk mirroring checklist . . . . . . . . . . . . . . .

Operating Information: OMC-R System

What is covered in this manual?

Introduction to the OMC-R system.

System management, including the Common Desktop Environment (CDE).

OMC-R log files.

OMC-R cron jobs.

System startup and shutdown.

Network Information Services.

File system backup and restore.

The following sections show the revision status of this document.

Issue Q GSM Software Release 7 Half Rate

Issue R GSM Software Release 8 GMR02

Issue S GSM Software Release 9

Resolution of Service Requests

Added a note under the section Security

Added a new environment variable under the

Amended output in Step 2, Procedure 13-14.

Updated partitioning data for SunFire 4800/4900,

Updated procedure 41 in Chapter 4.

Incorporation of Change Notices

Special key sequences

Press the Ctrl and C keys at the same time.

Press the Ctrl, Shift, and C keys at the same time.

Press the Alt and F keys at the same time.

Press the pipe symbol key.

Press the Return or Enter key.

Motorola appreciates feedback from the users of our documents.

Questions and comments

The document type