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 . . . . . . . . . .
24–hour 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

i

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

Operating Information: OMC-R System Administration

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

Operating Information: OMC-R System Administration

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
. .
. .
. .
. .
. .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

v

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

Operating Information: OMC-R System Administration

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

Operating Information: OMC-R System Administration

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 . . . . . . . . . . . . . . . . . .

x

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

68P02901W19-S
Oct 2009

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling/disabling the Print Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disk mirroring checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Analyzing OMC-R process errors. . Installing CDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Moving a machine with a forced link speed . . . . . . . Overview of Onperf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . StorEdge Enterprise Backup tape error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical Vol Mgr troubleshooting . . . . . . . . . . . . . . X. . . . . . . . . . . . . . . . . . . . . . Starting x25tool . Checking disk mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database failure . . StorEdge Enterprise Backup problems. . . . . . . . . . . . . . . . . . . . . . Loading a history file. . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of CDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of system processes . . . . . .Operating Information: OMC-R System Administration File access problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Long response times to commands. . . . . . . . . . . . . . . . . . . . . Procedure to recover from CDE login failure. . . Normal operation of CDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resetting boot devices . . . . . . . . . . Configuring CDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Problems adding/updating statistics in PM database. Device busy error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical Vol Mgr problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . .25 trace on the system processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting onperf from the CDE front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unmounting a device . . . . . . . . . . . . . . . . Displaying x25stat . . . . . . . . . . . . . . . . . . Common Desktop Environment problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other CDE problems . . . . . . . . . . . . . . . . Onperf utilities . . . . . . . . . . . . . . . . . . . . . Starting onperf from the command line . . . . . . . . . . . . . . . . . . . . . . . . . metastat output . . . . . . . . . . . Procedure to free up DVD-ROM drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device busy error . . . . . . . . . Checking if packets can be sent and received . . . . . . . . . . Overview of X. . . . Overview of CDE login failure . . . . . . . . . . GUI process . . . . . . . . . . . . . . . . . . . . Stale NFS file handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replacing hard disk on system processor Sunfire/Netra 440/Netra 20 . . . . . . . . DVD-ROM drive not ejecting . . . . . . . . . . . . . . . Procedure to reset a boot device . . . . . OMC-R software process errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting the LAN . . . . . . . . . . . . . . . . . . . . . . Checking the performance of the LAN . . . . . Database failure . . . . . . . . . . Saving Graph Tool configurations . Ejecting DVD-ROMs . . . . . . CDE login failure. . . . . . . . . . . . . . . . . . . . Errors in user profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bootup problems . . . . . . . . . . . . . . . . . . . . . . . . 68P02901W19-S Oct 2009 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selecting metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recovering from other Logical Vol Mgr problems . GUI processor failure to access event log files . Errors accessing a user's home directory . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 alarms . . . System processor hardware LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Daily administration checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R alarms . . . . . . . . . . . . . . . . . . . . . . Reading the database schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recording details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the system processor hardware . . . . . . . . . . . . . . . . . . . . . . . . . Checking disk usage . . . . . . . . . . . . . . . Checking databases . . . . . . . . 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 . . . . . . . . . Using neighbor statistics. . . Setting FM audit and disk usage limits . . . . . . . . . . Defragmenting tables (MIB database) . . . . . . . . Power failure on the system processor . Overview of setting FM audit and disk usage limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking cron jobs. . . . . . Weekly administration checklist . . . . . . . . . . . . . . . . . Checking core dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking disk mirroring . . . . . . Raising the maximum limit of neighbor statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking X. . . . Power failure on a GUI processor . . . . Disk space usage on the system processor . . . . . . . . . . . . . . . . . . . . . . . . Checking for successful parsing of statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Support for IP Multipathing in Solaris10/GSR9 on Sunfire platforms . . . . Configuring a Timeserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CPU and memory usage alarms . . . . . . Overview of alarms . . . . . . . . . . . . . . . . . . Monthly administration checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Neighbor statistics alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Limitations on use of neighbor statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up a night concentration centre . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database alarms . . . . . . . . . . . . . . Adding extra logical logs to the PM database server . . . . . . . . . . . . . . . . . . . . . . . . .CNFG parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cyclic Neighbor Statistics feature (PMCyclic) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware failure alarms . . . . . X. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General administration checklists . Displaying system processor status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activity tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring database space usage and fragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client and server partition details . . . . . . . . . . . . . Power failure on all machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking OMC-R log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using dbaccess . . . . . . . . . . . . . . . . . . . Neighbor statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68P02901W19-S Oct 2009 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checklist for PM database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Contents Monitoring tools . . . . . . . . . . . . . . . . . . . . . . . . . . Power failure. . . . . . . . . . . . . . . . . . . . . . Overview of recovery from power failure . . . . . . . . xii . . . . Emptying and defragmenting one or more PM statistics tables . . . . . . . . . . . Checklist for CM database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking and recovering database tables . . . . . . . . . . . FM_audit. . . . . . . . . . . .

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

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: Non—user configurable variables in the Common.csh file . . . . . . . .
6-2: Non—user 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

1

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

Q

Sep 2004

Issue Q – GSM Software Release 7 Half Rate

R

Nov 2006

Issue R – GSM Software Release 8 GMR02

S

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 4–1 in Chapter 4.

Incorporation of Change Notices
The following Change Notices (CN) are incorporated in this document:

2

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

3

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:

4

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.

24–hour support
If you have problems regarding the operation of your equipment, contact the Customer Network
Resolution Center (CNRC) for immediate assistance. The 24–hour telephone numbers are listed
at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center
contact information. Alternatively if you do not have access to CNRC or the internet, contact
the Local Motorola 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

5

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 24–hour
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.

6

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

7

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:

8

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 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.

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 recipient’s
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

9

10 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 Yönetmeliğine Uygundur.

CMM labeling and disclosure table CMM labeling and disclosure table ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ The People’s 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. and has an Environmental Friendly Use Period (EFUP) in years. such as battery modules.) Two items are used to demonstrate compliance. 68P02901W19-S Oct 2009 11 . the label and the disclosure table. The label is placed in a customer visible position on the product. Certain field-replaceable parts. can have a different EFUP and are marked separately. 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. • Logo 1 means the product contains no substances in excess of the maximum concentration value for materials identified in the China Management Methods regulation. The Disclosure table is intended only to communicate compliance with China requirements. The EFUP indicated by the Logo 2 label applies to a product and all its parts. It is not intended to communicate compliance with EU RoHS or any other environmental requirements. The example shown uses 50 years. • 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.

are covered in the Release Notes that accompany the individual software release. The document set covers encryption as if fully implemented. 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. and maintain the Motorola equipment. A banner is oversized text on the bottom of the page. Ordering documents and CD-ROMs With internet access available.com. 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.motorola. or contact your Motorola account representative. install. download. for example. data passing between certain elements in the network is encrypted. or order documents (original or revised).Motorola document set Motorola document set ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ The Motorola document sets provide the information to operate. PRELIMINARY — UNDER DEVELOPMENT. Document banner definitions A banner indicates that some information contained in the document is not yet approved for general customer use. to view. Limitations on the encryption included in the particular software being delivered. Data encryption In order to avoid electronic eavesdropping. visit the Motorola Lifecycles Customer web page at https://mynetworksupport. 12 68P02901W19-S Oct 2009 . order hard-copy documents or CD-ROMs from your Motorola Local Office or Representative. Without internet access available.

Chapter 1 Introduction to the OMC-R ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 68P02901W19-S Oct 2009 1-1 .

• Weekly procedures on page 1-30. • Routine system administration procedures on page 1-26. Overviews of the daily. Netra 440. NOTE Throughout this manual. weekly and monthly procedures are also included. • Additional procedures on page 1-33. refer to Installation and Configuration: OMC-R Clean Install (68P02901W47). • Daily procedures on page 1-28. 1-2 68P02901W19-S Oct 2009 . as well as other routine procedures that must be performed by the OMC-R system administrator. • Monthly procedures on page 1-32. • Configuring the OMC-R SunFire and Netra system processors on page 1-9. and {34618} M4000 and M5000 based systems. NOTE For detailed information regarding OMC-R hardware and software installation. and identifies the OMC-R hardware and software components provided for each system. Netra 20. • Connecting to the LAN on page 1-24.Overview Chapter 1: Introduction to the OMC-R Overview ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ This chapter provides an overview of the OMC-R hardware configuration for SunFire 4800/4900. The following topics are described in this chapter: • OMC-R system configuration on page 1-3. $OMC_TOP is used to describe the top level directory structure /usr/omc.

Sunblade 150). • A Graphical User Interface (GUI) Server (for example. Lexmark Optra S1650). Each processor is a complete UNIX system.25 Packet Switched protocol. is shown in Figure 1-1.Operating Information: OMC-R System Administration 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. The OMC-R interfaces with the cellular network through the use of X. SunFire 4800/4900. with optional equipment. Netra 440). • A laser printer. Netra 20. suitable for LAN connection (for example. An Ethernet Local Area Network (LAN) enables interaction between all processors. • Several GUI client processors which provide operator workstations. 68P02901W19-S 1-3 Oct 2009 . Typical hardware architecture of Motorola OMC-R.

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

the memory. this is based on the assumption that the appropriate number of GUI servers and memory are in use. The following formula gives the number of permitted 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. 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. OMC-R specifications are shown in Table 1-1. However. and CPU speed of the GUI server are used to determine the number of permitted GUI sessions. This formula has been implemented in the corecheck_gui script. For GUI Servers. 68P02901W19-S 1-5 Oct 2009 .Operating Information: OMC-R System Administration GUI sessions and GUI server memory The OMC-R can be configured to utilize an optional laser printer. The corecheck_gui script is used to start GUI sessions. the maximum number of GUI sessions supported is 60 for a Sunfire and 30 for other Single Platform systems.

• CPU class. • CPU speed. • Number of events arriving per second. including cache. Operator workstations The OMC-R system comprises of a single platform system processor and a number of operator workstations. 1-6 68P02901W19-S Oct 2009 . Each operator workstation is a complete UNIX system and runs the OMC-R Graphical User Interface (GUI). • Link capacity of the Local Area Network. They are as follows: • Real memory or the physical Random Access Memory (RAM) available within the platform.Factors influencing Processing Capability of GUI Servers Table 1-2 Chapter 1: Introduction to the OMC-R 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. • Disk access speed. Other factors affecting the performance of the GUI Server are: • Number of FM operators (Open GUIs / MMI Windows).

NOTE If an NHA processor is connected to the OMC-R.0.Operating Information: OMC-R System Administration 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.x contains the software requirements for all other OMC-R platforms. 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.0. 68P02901W19-S 1-7 Oct 2009 .9. then retain the NIS as the naming service for the OMC-R LAN.

3 — — — StorEdge Enterprise Backup Client 7.7 — — — zlib 1.6 — — — Enscript 1.1 — — — Perl 5.3 — — — RTF licence — — — Yes Title FlexNet INFORMIX-IDS OSP 1-8 68P02901W19-S Oct 2009 .3 — — — Sun VTS 6.6.00.Software requirements Chapter 1: Introduction to the OMC-R Table 1-3 Software requirements (Single Platform Processor) Revision version Media Number of volumes Licence key required GSR9 DVD 1900.UC8 — — — INFORMIX-Client SDK 2.1 — — — EPAK 3.2.4.61 — — — 10 — — — 10.4.9 — — — Sun SunLink X25 9.32 — — — 5.x DVD 1 — Sun Solaris 10 — — — Solaris Logical Volume Manager 11.2 — — — StorEdge Enterprise Backup Server 7.3 — — — Applix Spreadsheet 6 — — — Applix Data 6 — — — Mozilla 1.2 — — Yes TCL 8.6 — — — TK 8.2.81 — — — INFORMIX-ISQL 7.7 — — — Python 2.0.

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.Operating Information: OMC-R System Administration 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. • Checking disk configuration. NOTE Configuration is initially performed by Motorola. Table 1-4 SunFire 4800/4900 hardware requirements Equipment Quantity Description OMC-R platform 1 SunFire 4800/4900 (including 4 x CPUs) CPUs 4 900 MHz (minimum) US-III Memory 1 Minimum 4 GB Memory (8 x 512 MB DIMMs) Internal drives 2 36 GB SCSI CPU memory board 2 DVD-ROM drive 1 SCSI Continued 68P02901W19-S 1-9 Oct 2009 . • Installing and configuring cards. • Configuring hard drives. • Connecting peripherals.

Checking Netra 20 hardware requirements Table 1-4 Chapter 1: Introduction to the OMC-R SunFire 4800/4900 hardware requirements (Continued) Equipment Quantity Description DAT drive 1 4MM DDS4 SCSI/Ethernet combo (Sun Swift) 2 Dual port SCSI 160 HBA LVD (Jasper) 2 Serial I/O 3 4 port Synch 12 73 GB drives 1 All ac power 1 X 3310 JBOD SCSI 160 LVD disk array System and Disk Array Checking Netra 20 hardware requirements 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 1 Netra 20 (including two CPUs) CPUs 2 900 MHz (minimum) US-III Memory 1 Minimum 4 GB Memory (8 x 512 MB DIMMs) Internal drives 2 36 GB or 73 GB DVD-ROM drive 1 SCSI DAT drive 1 4MM DDS4 Dual port SCSI 160 HBA LVD (Jasper) 2 Serial I/O 2 4 port Synch 12 73 GB drives 1 All ac power 1 X 3310 JBOD SCSI 160 LVD disk array System and Disk Array Checking Netra 440 hardware requirements 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 .

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 ensure that the configuration switch on the D240 is in the split bus position.Operating Information: OMC-R System Administration Table 1-6 Connecting peripherals Netra 440 hardware requirements (Continued) Equipment Description Quantity CPUs 2 1280 MHz (minimum) US-IIIi Memory 1 Minimum 4 GB Memory (8 x 512 MB DIMMs) Internal drives 2 73 GB DVD-ROM drive 1 SCSI Dual port SCSI 320 HBA LVD (Jasper320) 2 Serial I/O 2 4 port Synch 12 73 GB drive System and Disk Array 1 All ac power QGE (Quad 1000 Mbit Ethernet) 1 1 X 3310 JBOD SCSI 160 LVD disk array External Tape Drive Connecting peripherals Connecting peripherals to a SunFire 4800/4900 Figure 1-4 illustrates the peripheral connections to a SunFire 4800/4900. and Figure 1-4. Figure 1-2 68P02901W19-S StorEdge 3310 Disk Array 1-11 Oct 2009 .

Connecting peripherals 1-12 Chapter 1: Introduction to the OMC-R Figure 1-3 D240 Media Tray Figure 1-4 Connecting peripherals on a SunFire 4800/4900 68P02901W19-S Oct 2009 .

6 If a Sun rack is used. 4 Connect a cable from SCSI+Ethernet card 1 to the top left connector of the D240. Once the Netra 20 and StorEdge 3310 Disk Array (Figure 1-6) are mounted. connect a serial port splitter cable to SC0 serial and connect ttyb to the frame manager. 2 Connect a cable from UltraSCSI card 1 to lower port A of the 3310. Connecting peripherals to a Netra 20 Figure 1-5 illustrates the peripheral connections to a Netra 20. 5 Connect Ethernet cables to SCSI+Ethernet card 0 and both SC0 and SC1. attach the two SCSI cables as follows: Figure 1-5 68P02901W19-S Connecting peripherals on a Netra 20 1-13 Oct 2009 .Operating Information: OMC-R System Administration Connecting peripherals 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 1 Connect a cable from UltraSCSI card 0 to lower port B of the 3310. 3 Connect a cable from SCSI+Ethernet card 0 to the top right connector of the D240.

When powered up. both TERM lights on the array should be lit. 2 Ensure that the terminal connected to the Serial Port console remains connected for the duration of the installation.Connecting peripherals Chapter 1: Introduction to the OMC-R 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 1 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. 68P02901W19-S Oct 2009 .

Operating Information: OMC-R System Administration Connecting peripherals to a Netra 440 Connecting peripherals to a Netra 440 Figure 1-7 68P02901W19-S Connecting Peripherals on a Netra 440 1-15 Oct 2009 .

3 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. 68P02901W19-S Oct 2009 . 2 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. When powered up. both TERM lights on the array should be lit.Connecting peripherals to a Netra 440 Figure 1-8 Chapter 1: Introduction to the OMC-R 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 1 Ensure that the two Ultra SCSI cards are installed in slots PCI 2 and PCI 4.

Card configuration Table 1-7 specifies the location of the cards for a SunFire 4800/4900.Operating Information: OMC-R System Administration 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 1 Install the HSI cards into the pci slots in the SunFire or Netra.25 network equipment using the cables provided. 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 . 2 Connect the HSI cards to the external X. as described in the Sun Hardware Guide. 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-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. Figure 1-9 1-18 Netra 20/440 internal disk slots 68P02901W19-S Oct 2009 . 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.Configuring hard drives Chapter 1: Introduction to the OMC-R Table 1-9 specifies the location of the cards for a Netra 440.

6 GB 9. Netra 20 and Netra 440 The single platform processor controls either twelve 73 GB disks or {34618} 146 GB disks. The logical disk partitions critical for the boot process are amended during the Solaris operating system installation.8 GB 7. For these servers.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. The JumpStart procedure incorporates Solaris Logical Volume Manager to set up the metadevices. 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.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. The disks are shipped from Sun with a default partition configuration. the metadevice numbers are generated dynamically. Table 1-11 highlights the partitioning details used for the SunFire 4800/4900 and Netra 20 servers.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 . Netra 20 and Netra 440 Disk configuration SunFire 4800/4900. Table 1-11 and Table 1-12 are based on 146 GB disks.Operating Information: OMC-R System Administration Disk configuration SunFire 4800/4900.8 GB 6.8 GB primary_disk mirror_disk d25 d26 d27 d60 omc_db _root 2.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. Table 1-12 highlights the partitioning details used for the Netra 440 servers.0 GB 2.

0 GB 2.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 .Disk configuration SunFire 4800/4900.0 GB primary_disk mirror_disk d25 d26 d27 d155 omc_db _logs 2.0 GB primary_disk mirror_disk d25 d26 d27 d170 mib_db1 2.0 GB primary_disk mirror_disk d25 d26 d27 d165 mib_db _logs 2.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.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.0 GB primary_disk mirror_disk d25 d26 d27 d160 mib_db2 2. Netra 20 and Netra 440 Table 1-11 Chapter 1: Introduction to the OMC-R 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 d150 mib_db 2.0 GB 2.0 GB 2.0 GB 2.0 GB 2.

8 GB primary_disk mirror_disk d25 d26 d27 d60 omc_db _root 2.0 GB primary_disk mirror_disk d25 d26 d27 d165 mib_db 2.0 GB primary_disk mirror_disk d25 d26 d27 d175 mib_db2 2.0 GB primary_disk mirror_disk d25 d26 d27 d170 omc_db _logs 2. Netra 20 and Netra 440 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.0 GB primary_disk mirror_disk d25 d26 d27 d185 mib_db1 2.Operating Information: OMC-R System Administration Table 1-12 File System Disk configuration SunFire 4800/4900.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 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 .

Netra 20 and Netra 440 Table 1-13 Chapter 1: Introduction to the OMC-R OMC-R Single Platform Disk Partition Layout Partition Size Location / 8.264GB Application Stripe omc_db5 11.264GB Application Stripe omc_db10 11.264GB Application Stripe omc_db_logs 2.1GB Primary Disk S4 /usr 13.264GB Application Stripe omc_db9 11.264GB Application Stripe omc_db8 11.048GB (new) Application Stripe /usr/omc/logs/bss_sec 8.9GB Application Stripe /usr/omc 6.264GB Application Stripe omc_db11 11.8GB (increased by 4GB) Primary Disk S0 swap 4.0GB Application Stripe omc_db1 11.048GB Application Stripe omc_db2 11.048GB Application Stripe omc_db_temp 2.8GB Primary Disk S1 /var 20.048GB (new) Application Stripe lod_db1 10GB (new) Application Stripe Continued 1-22 68P02901W19-S Oct 2009 .264GB Application Stripe omc_db12 11.048GB Application Stripe mib_db 2.3GB (increased by 2GB) Application Stripe omc_db_root 2.7GB Primary Disk S5 Total 64.5GB Primary Disk S3 /opt 7.Disk configuration SunFire 4800/4900.4GB Application Stripe /usr/omc/ne_data/raw_stats 13.264GB Application Stripe omc_db6 11.0GB Application Stripe omc_db4 11.048GB Application Stripe mib_db2 2.048GB Application Stripe mib_db1 2.0GB (new) Application Stripe /usr/omc/logs/sleeping_cell 2.264GB Application Stripe /solbak 8.264GB Application Stripe /usr/omc/ne_data 16.048GB Application Stripe omc_db3 11.264GB Application Stripe omc_db7 11.9GB Primary Disk /omcgen 7.264GB Application Stripe mib_db_logs 2.0GB Application Stripe /home 10.

the root partition on a Netra 440 is on slice c0t8d0s0 on the main disk and on slice c1t8d0s0 on the mirror disk. Netra 20 and Netra 440 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. For example. Netra 440s use c0 and c1. 68P02901W19-S 1-23 Oct 2009 . the root partition on a Netra 20 is on slice c1t8d0s0 on the main disk and on slice c3t8d0s0 on the mirror disk. Instead of c1 and c3.Operating Information: OMC-R System Administration Table 1-13 Disk configuration SunFire 4800/4900. However.

During normal OMC-R operation the processors NFS mount file systems across the network. The LAN may be extended to cater to remote workstations or for the addition of optional processors. 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 processor must be connected to the LAN before software installation begins or backup is performed.Connecting to the LAN Chapter 1: Introduction to the OMC-R Connecting to the LAN ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Overview of connecting to the LAN All processors that constitute the OMC-R system. 1-24 68P02901W19-S Oct 2009 . Each OMC-R system is provided with a Hub that can be installed for normal operation or used for testing. use an Ethernet Local Area Network (LAN) for interaction.

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 .Operating Information: OMC-R System Administration 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.

Informix.Routine system administration procedures Chapter 1: Introduction to the OMC-R 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. In each case. Recommended routine procedures are described in the sections that follow. Certain special procedures may be required depending on individual customer requirements. a reference is made to the relevant section in this manual for the actual procedure. 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 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. All the results from these procedures as well as any system changes should be recorded in a log book. and omcadmin.

Operating Information: OMC-R System Administration • 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. 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 . • A list of contact names. telephone numbers.

every five minutes). 1-28 68P02901W19-S Oct 2009 . 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. Refer to Chapter 12 Backup Server Installation and Configuration. Inspect the omc_db_maint log file to ensure that omc_db_maint runs successfully. and configuration data) is copied to ASCII files and then deleted from the PM database by the omc_db_maint utility. This can be carried out in conjunction with unloading the database using the omc_db_maint utility. Back up the INFORMIX databases Perform a level 2 backup of the two databases on the system processor. This procedure may be automated using cron. OMC-R stopped during raw statistics collection period) can be manually submitted using the pm_manual_parse utility. Refer to Administering the PM database using the omc_db_maint utility on page 8-23 for further information. the regular statistics. Refer to Administering the PM database using the omc_db_maint utility on page 8-23. Manually parse any unparsed statistics files Any raw statistics files that may have escaped processing by the Performance Management (PM) file parser (for example. These procedures should be carried out daily by the OMC-R system administrator. subscription lists.log_MIB are located in the /usr/informix directory on the system processor.log_OMC and online. the database disk usage should be monitored daily. Refer to Database utilities on page 8-4.Daily procedures Chapter 1: Introduction to the OMC-R Daily procedures ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ INFORMIX database daily procedures The following procedures concern the INFORMIX databases. A purge operation should be performed on the database on a daily basis (for example. deleting statistics). Monitor the PM database disk usage To ensure that the PM database functions effectively. Check the INFORMIX log files Inspect the database log files (online. The database log files online.log_OMC and online. Unload and purge the PM database on the system processor The data stored in the PM database (for example. The data in the ASCII files can be archived to tape and then deleted.log_MIB) for errors and to ensure that check-pointing is occurring regularly (for example. When the omc_db_maint utility is used.

25 application management on page 9-3. Any core dump files found should be dealt with as described in Core file generation on page 13-6. Back up the UNIX file systems A daily backup of all the OMC-R UNIX file systems should be carried out using StorEdge Enterprise.25 connectivity Procedures for checking X. check the mail report sent from cron to root and omcadmin on each of the relevant processors (for example. Check for core dump files All OMC-R user accounts should be checked to see if any core dump files exist. Miscellaneous daily procedures The following are miscellaneous procedures which should be carried out daily by the OMC-R system administrator. located in the $OMC_TOP/logs directory. Check the system processor hardware Procedures for inspecting the hardware are described in Checking the system processor hardware on page 13-99. 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. 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.25 connectivity are described in X. Check X. should be inspected for errors and abnormalities.Operating Information: OMC-R System Administration UNIX file systems daily procedures UNIX file systems daily procedures The following procedure concerns UNIX file systems. the system processor and GUI server). This procedure should be carried out on a daily basis 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 OMC-R log files The OMC-R log files. 68P02901W19-S 1-29 Oct 2009 .

This can become a weekly task as alarms are generated when the disk becomes full. UNIX file systems weekly procedures The following procedures concern the UNIX file systems. 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. Roll the database log (online. These procedures should be carried out on a weekly basis by the OMC-R system administrator. This procedure is automated using cron. 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. These procedures should be carried out on a weekly basis by the OMC-R system administrator. 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). 1-30 68P02901W19-S Oct 2009 . This procedure may 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. 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.Weekly procedures Chapter 1: Introduction to the OMC-R Weekly procedures ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ INFORMIX database weekly procedures The following procedures concern the INFORMIX databases. as described in Chapter 12 Backup Server Installation and Configuration. This procedure can be automated using cron (refer to System cron jobs on page 5-3).log script.log) The database log file should be moved to a time-stamped file using the roll_online.

user account files and network files should be checked for unwanted entries. 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. Additionally. This procedure can be automated using cron (refer to System cron jobs on page 5-3). 68P02901W19-S 1-31 Oct 2009 . log files in /var/log should be checked for unwanted system access attempts.Operating Information: OMC-R System Administration 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. Monitor user security For security reasons.

This procedure should be carried out on a monthly basis by the OMC-R system administrator. 1-32 68P02901W19-S Oct 2009 . Inform all other OMC-R users to change passwords regularly.Monthly procedures Chapter 1: Introduction to the OMC-R Monthly procedures ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ UNIX file systems monthly procedures The following procedure concerns the UNIX file systems. as described in Chapter 12 Backup Server Installation and Configuration. 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. 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. For details of this procedure refer to Scheduling cron jobs from the command line on page 5-14. omcadmin and Informix on the system and GUI processors. Truncate cron log file Shorten the cron log file each month to maintain a reasonable file size.

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. 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. NE load management maintenance Archive and remove any NE software loads and databases that are no longer required. Complete file system backup Perform a complete file system backup in the following cases: • Before and after initial installation of the OMC-R software. Refer to Database utilities on page 8-4. These additional procedures are conducted on a needs basis. • Before a disk partition size is changed. 68P02901W19-S 1-33 Oct 2009 . Refer to Chapter 12 Backup Server Installation and Configuration.Operating Information: OMC-R System Administration Additional procedures Additional procedures ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Additional event driven procedures There are certain event driven procedures which are carried out by the OMC-R system administrator.

cartridge. and after every change to the configuration of the system. The following procedures are needed: 1-34 • Tape drive cleaning . due to system halts or OMC-R errors occurring). 68P02901W19-S Oct 2009 . • Replacement of toner.refer to the Solaris 10 Administrator's Guide. the action to be taken is described in Core file generation on page 13-6. Refer to OMC-R system information on page 13-8. Hardware maintenance Hardware maintenance procedures should be carried out in accordance with the instructions of the manufacturers. and other printer components .refer to the relevant printer maintenance manual. A process id report listing should be made using the ps command for the system and GUI processors. System core dumps System core dump files may be produced (for example. This is produced when the systat utility is run.Hard copy listings (printouts) Chapter 1: Introduction to the OMC-R Hard copy listings (printouts) Hard copy listings of various files and system information should be made after initial installation of the OMC-R. • Clean the monitor screens. If system core dump files are produced.

Chapter 2 System management ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 68P02901W19-S Oct 2009 2-1 .

• Security overview on page 2-36. • Administering user accounts with usertool on page 2-12. • Restartable processes on page 2-49. 68P02901W19-S Oct 2009 . • CDE utilities available to an omcadmin login on page 2-18. • Cleaning up OMC-R software loads on page 2-28. • Configuration and installation of a remote terminal on page 2-59. • Capacity control on page 2-46. • Controlling user activity on the system on page 2-40. • Installing OMC-R Help on page 2-45. • Graceful shutdown on mains failure on page 2-57. • OMC software management on page 2-24. • Setting the locale on the OMC-R on page 2-69. • Removing OMC-R night concentration centre configuration on page 2-67.Overview Chapter 2: System management Overview ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ The following topics are described in this chapter: 2-2 • Overview of the Common Desktop Environment (CDE) on page 2-3. • Monitor alternative OMC-R from GUI server on page 2-65. • Controlling user passwords on page 2-42. • Administering group accounts with usertool on page 2-8. • CDE utilities available to either root or omcadmin login on page 2-20. • NE database maintenance on page 2-30. • Network file security on page 2-44. • Archiving old OMC-R user files on page 2-23. • General administration checklists on page 2-74. • Remote system processor setup on page 2-63. • Printing current OMC-R processes on page 2-35.

and is provided on the different SUN workstations. The CDE supports: • Operator configurable windows on startup. Figure 2-1 Root user desktop Figure 2-2 OMC admin user desktop 68P02901W19-S 2-3 Oct 2009 . The CDE provides an industry standard desktop manager for the OMC-R. • Reduced window clutter through use of multiple panes. The display of the desktop depends upon the type of login. • The OMC admin desktop (Figure 2-2). There are two desktops displayed in the CDE: • The Root user desktop (Figure 2-1).Operating Information: OMC-R System Administration 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). • A File Manager which provides a graphical front end to the UNIX file system.

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

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. These utilities are available from the front panel of the CDE desktop. • File Manager. The OMC Admin menu is displayed (Figure 2-3). • Help Manager. Procedure 2-1 68P02901W19-S Accessing usertool from the CDE desktop 1 Login to the system processor as user root. 2 Click on the System Administration icon. 2-5 Oct 2009 . • Cron job scheduler. • Mail. The root CDE desktop is displayed (Figure 2-1).Operating Information: OMC-R System Administration Utilities common to the omcadmin and root CDE desktops Utilities common to the omcadmin and root CDE desktops The following utilities are common to both the omcadmin and the root CDE desktops.

2 Execute the following command: export DISPLAY /usr/omc/current/sbin/OMC_Sync Figure 2-4 2-6 Usertool main window 68P02901W19-S Oct 2009 . execute the following DISPLAY command: DISPLAY=TerminalDisplay:0. Or If logged in to the server remotely. execute the following DISPLAY command: DISPLAY=omc_splat:0.Accessing usertool Chapter 2: System management 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. This can be found in the /etc/hosts file.0 Where TerminalDisplay is the TCP/IP address setting of the terminal being used for remote login.0 Where omc_splat is the TCP/IP address setting of the system processor.

The highlighted field can be modified by typing or deleting as required. or select Cancel to quit. On this screen. the CDE settings and MIB profiles are also updated automatically. if the user is a member of the omc group. one field is highlighted with a bar which can be moved with the cursor keys. After adding. a screen containing all the relevant fields which can be modified appears.Operating Information: OMC-R System Administration Accessing usertool Once an option is chosen. 68P02901W19-S 2-7 Oct 2009 . 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. Once all the fields are correctly filled in. deleting or modifying users. select Done to save changes. the relevant user or group operation is performed. 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.

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. SMC) is preferred. the groups Informix. 2-8 68P02901W19-S Oct 2009 . modify or delete groups. if the appropriate access privileges are granted. LDAP) is in use. Before assigning users to a specific group. omc and omcread exist. • Delete a group.Administering group accounts with usertool Chapter 2: System management Administering group accounts with usertool ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Overview of group management functions in usertool The following section describes the group management functions in usertool. • Add a group. NOTE After a clean install of an OMC-R system. or another tool (for example. The usertool supports the following group management tasks. 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. • Rename a group. If another naming service (for example. Group management is used to add any groups to which the users are assigned. The group management functions in usertool are used to manage the group file in the NIS database centralized on the system processor. there is no need to add. Under normal circumstances. • Modify a group. make sure that the group exists.

Operating Information: OMC-R System Administration 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 ID (GID) Group ID specifies a group identification number used by the system to identify a user's primary group.9). A group name contains lower case alphabetical characters (a . By default. Spaces are not allowed. Reserved GIDs include 60001 (nobody). GIDs are kept below 60000. 60002 (no access) and 65534 (no group). A group name is between 1 to 8 characters long. Figure 2-5 68P02901W19-S Group administration utility 2-9 Oct 2009 . the groups omc. Group Group specifies a name used by the system to identify a user group. To minimize the amount of software incompatibility. omcread and Informix are present along with the standard operating system groups.z) and digits (0 .

Modifying group accounts Use the following procedure to modify a group account. 3 Enter a unique Group name and Group ID (GID). 4 Enter the new name for the group and press return to complete the process. select Done by highlighting it with the cursor key and pressing Enter. select Modify group. 3 Enter the name of the group to be renamed. 4 To commit the changes. select Done by highlighting it with the cursor key and pressing Enter. Procedure 2-4 Modifying a group account 1 Follow the procedure Accessing usertool on page 2-5. 2 From the usertool main window. The Group administration utility is displayed as in Figure 2-5. 4 To commit the changes. Procedure 2-5 2-10 Renaming a user group account 1 Follow the procedure Accessing usertool on page 2-5. 3 Modify the group name and/or GID as required. 68P02901W19-S Oct 2009 . select Rename group.Adding a group Chapter 2: System management Adding a group Use the following procedure to add a new user group. 2 From the usertool main window. Renaming group accounts Use the following procedure to rename a user group. The Group administration utility is displayed as in (Figure 2-5). Procedure 2-3 Adding a new user group 1 Follow the procedure Accessing usertool on page 2-5. select Add group. 2 From the usertool main window.

select Delete group. 2 From the usertool main window. select Done by highlighting it with the cursor key and pressing Enter. 2-11 Oct 2009 . 4 To commit. Procedure 2-6 68P02901W19-S Deleting a user group account 1 Follow the procedure Accessing usertool on page 2-5. 3 Enter the name of the group to be deleted.Operating Information: OMC-R System Administration Deleting group accounts Deleting group accounts Use the following procedure to delete a user group.

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

2 Enter the following command: cd /etc/dt/config/C 3 Edit the sys. It is advisable that the first character is a lower case letter (a-z). 68P02901W19-S 2-13 Oct 2009 .Operating Information: OMC-R System Administration 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. 4 Comment out the three command lines that start with dtsmcmd. User management parameters The different user management windows can contain combinations of the following parameters described in this section. 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. Although Full name is an optional control. copy it from the /usr/dt/config/C directory. 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 highly recommended that a value be entered in this field.session file. such as a user's full name or role. Full name Full Name is a control that specifies notes about the user account. 5 Save the file. Procedure 2-7 Ensuring the correct GUI colors appear for all users 1 Login as root. The UID should be unique. as it is required by specific command line Operation and Maintenance utilities such as cmdLineAudit. If this file does not exist. It is good practice to have sequentially increasing UIDs to aid in system administration. User name User name specifies a login name the user will use when logging onto the OMC system.

Figure 2-6 2-14 User administration utility 68P02901W19-S Oct 2009 . The default shell is the C shell. Account locked Setting account locked to y means that this account cannot be accessed.User management parameters Chapter 2: System management Group Group specifies a group ID number or group name that the operating system assigns to files created by the user. Secondary groups Secondary groups is an optional control that is not used in the Motorola configuration. The C shell is mandatory for OMC users. The default setting is n. 111 for a restricted omcread account. and 109 for an Informix account. but it specifies one or more groups to which the user belongs. The default setting is n (unlocked). Standard group numbers are 110 for a normal OMC operator account. Change password Setting change password to y forces the user to enter a new account when accessing this account for the first time. Shell Shell specifies the login shell to be used.

• If the OSI Processor is to be integrated or configured later. • If the OSI Processor is already integrated with or connected to the OMC. select Add user. The User administration utility is displayed as in Figure 2-6. 3 Enter a unique user name and modify the default user creation parameters as required. 68P02901W19-S 2-15 Oct 2009 . NOTE It is highly recommended that a value is entered in the Full name field. for some reason. 2 From the usertool main window. 4 Highlight Done and select it by pressing the Enter key. omcadmin and Informix should not be modified. NOTE • The user privileges and profile are updated in the MIB database. Modifying a user account NOTE Under normal circumstances users root. each new OMC user will be automatically entered into the relevant /usr/omc/config/global/system_table file of the Security Application. This completes user creation.Operating Information: OMC-R System Administration Adding a user Adding a user Use the following procedure to add a new user. as it is required by specific command line Operation and Maintenance utilities such as cmdLineAudit. or if. 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. Procedure 2-8 Adding a new user 1 Follow the procedure Accessing usertool on page 2-5. 5 Enter the user account password twice.

Renaming a user account NOTE Under normal circumstances users root. and Informix should not be renamed. omcadmin and Informix should not be deleted. 3 Enter the name of the user to be modified and modify parameters as required. select Modify user. 4 Enter the new name for the user and press return to complete the process. select Done by highlighting it with the cursor key and pressing Enter. 4 To commit the changes. 2 From the usertool main window. Procedure 2-9 Modifying a user account 1 Follow the procedure Accessing usertool on page 2-5. 2 From the usertool main window. Deleting a user account NOTE Under normal circumstances users root. Use the following procedure to rename a user account. 3 Enter the name of the user to be renamed.Renaming a user account Chapter 2: System management Use the following procedure to modify a user account. select Rename user. Procedure 2-10 Renaming a user account 1 Follow the procedure Accessing usertool on page 2-5. 2-16 68P02901W19-S Oct 2009 . omcadmin. The User administration utility is displayed as in Figure 2-6.

NOTE The user profile is also deleted from the MIB database. 4 To commit to deleting the group.Operating Information: OMC-R System Administration Deleting a user account Use the following procedure to delete a user account. 3 Enter the name of the user to be deleted. 2 From the usertool main window. select Done by highlighting it with the cursor key and pressing Enter. Procedure 2-11 Deleting a user account 1 Follow the procedure Accessing usertool on page 2-5. select Delete user. 68P02901W19-S 2-17 Oct 2009 .

as shown in Figure 2-8. Figure 2-7 2-18 Displaying the omcadmin CDE desktop GUI client graphical CDE login screen 68P02901W19-S Oct 2009 . select Remote Login from the Options menu. Procedure 2-12 1 From the GUI Client graphical CDE login screen. as shown in Figure 2-7. 2 Type the hostname of a GUI server that exists in the /etc/hosts file of the GUI client. 4 Enter the username omcadmin and password. 3 The GUI server graphical CDE login screen appears.CDE utilities available to an omcadmin login Chapter 2: System management CDE utilities available to an omcadmin login ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Displaying the omcadmin CDE desktop Use the following procedure to display the omcadmin CDE desktop. and click OK. then click OK to display the CDE desktop.

• Informix.Operating Information: OMC-R System Administration 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. • Install Icon. 68P02901W19-S 2-19 Oct 2009 . Other database monitoring utilities can be added using the CDE desktop controls. The following options are available from this menu.

then click OK to display the root CDE desktop. as shown in Figure 2-7. 4 Enter the username root and password.CDE utilities available to either root or omcadmin login Chapter 2: System management CDE utilities available to either root or omcadmin login ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Displaying the root CDE desktop Use the following procedure to display the root CDE desktop. select Remote Login from the Options menu. 3 The GUI server graphical CDE login screen appears. 2 Type in the hostname of a GUI server that exists in the /etc/hosts file of the GUI Client. and click OK. as shown in Figure 2-8. Procedure 2-13 1 From the GUI client graphical CDE login screen. Figure 2-9 2-20 Displaying the root CDE desktop GUI client graphical CDE login screen 68P02901W19-S Oct 2009 .

• File Manager. screen lock. keyboard click volume. 2-21 Oct 2009 .Operating Information: OMC-R System Administration 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 Style Manager can be accessed from the CDE desktop and is used to change desktop attributes relating to colors. font. and startup preferences to create a customized desktop. window behavior. 2 Click on the icon in the Style Manager window to select the item that is to be customized. • Style Manager. mouse speed. Procedure 2-14 68P02901W19-S Opening the Style Manager 1 Invoke the Style Manager by entering the command: /usr/dt/bin/dtstyle The Style Manager window is displayed. Use the following procedure to open the Style Manager. backdrop.

• Search for an object. find. accessed through the CDE front panel. • Customize the File Manager View. Each object is represented by an icon in the File Manager.File Manager Chapter 2: System management File Manager The File Manager (Figure 2-11). Figure 2-11 2-22 File Manager. copy. • Change permissions on objects. main window (Home) 68P02901W19-S Oct 2009 . The File Manager is used to create. File Manager allows the following operations to be performed: • Move. and delete objects. and applications. and use workspace objects such as files. open. folders. provides a GUI to the UNIX file system. • Open an Xterminal.

Procedure 2-15 68P02901W19-S Checking home accounts of users for unmodified files 1 Login to the system processor as user root. 2-23 Oct 2009 . Use the UNIX command tar to archive the files to tape. 2 Execute the following to select the OMC-R user files that need to be archived: find /home -mtime +14 -print > /usr/tmp/listing 3 The file /usr/tmp/listing may contain a list of user files that need to be archived or removed from the system.Operating Information: OMC-R System Administration 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.

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

The swtool utility should be used.16.Operating Information: OMC-R System Administration 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. Note that this causes an outage for the duration of the cutover. select the Remove a release option. Otherwise. associated test objects. From the OMC Releases menu in swtool. you can select the default option since the software is normally installed from the DVD in the local DVD-ROM drive. 4. NOTE A current release cannot be removed. Cutover. the cutover script is automatically executed once the software installation is complete. When prompted for the path of the software. if any. Insert the DVD containing the new software releases in the local DVD drive. are automatically removed. If cutover is selected. The following menu options are displayed: Install release 1.17. 1900.18. 1900. NOTE Old software releases should no longer be removed using the rm command. Removing old software It is important to delete old releases and retain only a few requisite software releases. Your choice: If you wish to install the software and cutover in a single step. Remove which release? Select the release to be removed. 68P02901W19-S 2-25 Oct 2009 . Install OMC Software Release Only. 3. 2. None. If a software release is removed. Done. Install OMC Software Release and Cutover Machine. The relevant software packages for the system are then installed. 1900. select Install OMC Software Release and Cutover Machine. select Install OMC Software Release Only.

A menu is displayed containing all the test objects available in that directory. therefore the majority of test objects are supplied as Solaris patches. 4. Show files in a test object. Manage releases. It is assumed that the object is relevant to the system Single Platform Processor or GUI server on the correct load. Display software inventory. 2-26 68P02901W19-S Oct 2009 . The selected test object is installed automatically.Test objects Chapter 2: System management Test objects The OMC software is supplied as Solaris packages. select the Install a test object option. enter the directory containing the test object (TAR) file. 4. View test object history. A menu similar to the following is displayed. Your Choice: Installing the test objects From the Test objects menu in swtool. such as whether the OMC needs to be stopped during the installation. Select the correct test object. When prompted. Manage test objects. 5. The following options are displayed: Test objects 1. 3. 2. Main menu. Execute the swtool utility as user root. 3. Quit. 2. Motorola software tool 1. Your choice: Select the Manage test objects option. NOTE Read the relevant release notes for each test object for details about installation or removal. The following prompt is displayed: Install test object from which directory? [/]. Remove a test object. Install a test object.

select the View test object history option. along with the date and time at which the action was taken. select the Show files in a test object option. select the Remove a test object option. A menu is displayed containing all the test objects installed on the system.Operating Information: OMC-R System Administration Test objects Removing the test objects From the Test objects menu in swtool. Select the correct test object to remove it automatically. Test object history From the Test objects menu in swtool. A screen is displayed with a history of all the test objects installed on and removed from the system using swtool. Select a test object to view all the files the test object modifies. Files modified by a test object From the Test objects menu in swtool. 68P02901W19-S 2-27 Oct 2009 . A menu appears displaying all the test objects installed on the system.

tar> rm -rf <omcloaddirectory> 4 Move the tar file to a file system with sufficient storage space. Procedure 2-16 2-28 Keeping software loads on the system processor 1 Login as the user root. the script produces an error message. If the /usr/omc/sbin/cutover script fails to execute correctly and the /usr/omc file system is over 85% full. To avoid the file system becoming full and to ensure that the cutover script runs correctly. the script produces a warning message. If the /usr/omc file system is over 80% full. cd /usr/omc tar cvf <tarfilename. Keeping software loads Use the following procedure to keep software loads on the system processor.8. <omcloaddirectory> is the name of the OMC-R software load. NOTE This procedure must not be used with the current software load.x.0.Cleaning up OMC-R software loads Chapter 2: System management 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. The operator can then decide whether or not to continue with the script.tar> <omcloaddirectory> where <tarfilename. 68P02901W19-S Oct 2009 . 3 Enter the following commands: compress <tarfilename. There may be two OMC-R application software loads in this directory. the file system becomes full and the cutover script used to cutover to a new OMC-R software load may fail. the current software load and the previous software load. clean up the /usr/omc directory regularly. 2 Enter the following commands on the system processor. If too many OMC-R application software loads are stored in /usr/omc.tar> is the name of the new tar file. for example.0. 1.

Z> tar xvf <tarfilename.tar.tar 2-29 Oct 2009 . 3 Enter the following commands: cd /usr/omc uncompress <tarfilename.Operating Information: OMC-R System Administration Using a tarred software load Using a tarred software load Use the following procedure to use a tarred OMC-R software load.tar> rm tarfilename.Z /usr/omc where <pathname> is the directory path name the tar file is stored. 2 Enter the following command: mv /<pathname>/tarfilename. Procedure 2-17 68P02901W19-S Using a tarred software load 1 Login as the user root.tar.

NOTE Avoid submitting several files simultaneously for manual processing. Use the following procedure to archive to a DAT tape drive. for example. 2-30 68P02901W19-S Oct 2009 . 2 Enter the following command: tar cvf /dev/rmt/0 db_name/* where db_name is the name of the NE database directory. db920913171522/*. ne_specific is either BSS-specific or RXCDR-specific. Archiving and removing a NE database Before a NE database is removed from the file system. BSS or RXCDR.NE database maintenance Chapter 2: System management 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. entering the commands in sequence. it should be archived. as this may adversely affect automatic processing. for example. bss1. for example. Procedure 2-18 1 Archiving the NE database to a DAT tape drive Enter the following command: cd $OMC_TOP/ne_data/dbroot/ne_type/ne_specific/ne_name where: ne_type is the NE type. Part of the procedures to be performed on a daily basis is to check if any raw statistics have escaped processing by the parser. 3 When the database has been archived to tape. ne_name is the name of the NE database directory. 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.

BSS or RXCDR. /bin/find $OMC_TOP/ne_data/raw_stats/100. If the utility does not succeed in sending the supplied filename to the parser. For more information. 3 Enter the following command: rm -r specific_fallback_load_dir where specific_fallback_load_dir is the name of the fallback directory to be removed. failed_load or no_db_storage. Procedure 2-19 Submitting raw statistics files to the parser 1 Login using login id omcadmin. Manual parsing of statistics checklist Follow the procedure (Table 2-2) to manually parse statistics files.*“ -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. The speed of parsing depends on the time of day that the command is executed. Removing NE fallback software load directories Use the following procedure to remove a NE fallback software load directory. for example. ne_specific is either BSS-specific or RXCDR-specific. using the following command: $PM_ROOT/bin/pm_manual_parse filename where filename is from the parser list. refer to Database utilities on page 8-4.0 -name “*. entering the commands in sequence. an appropriate error message is displayed on the screen. Copy the checklist provided in Table 2-2 to record the checks. should be submitted one at a time. Procedure 2-20 Removing a NE fallback software load directory 1 Login using login id omcadmin. 68P02901W19-S 2-31 Oct 2009 .Operating Information: OMC-R System Administration 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. 2 Check if any raw statistics files have escaped processing by the parser by entering the following command (typed as a single line). 3 Files which do not have a suffix of bad_header. 2 Enter the following: cd $OMC_TOP/ne_data/dbroot/ne_type/ne_specific where: ne_type is the NE type.

edit the OMC. As user omcadmin execute the following command: $PM_ROOT/bin/pm_manual_parse <filename> Check for any error messages from the pm_manual_parse utility. Uncomment the setting for PM_HOURLY_STATS and alter the environment variable so it looks like either of the following.Manual parsing of statistics checklist Table 2-2 Serial number Chapter 2: System management Manual parsing of statistics checklist Method Check 1 Check that the parser process is running.CNFG file.*“ -mtime +1 -print > /usr/tmp/parser_list 4 Submit any files found by the find command that do not have a suffix of bad_header. depending on the requirement at the BSS: PM_HOURLY_STATS=ON Or: PM_HOURLY_STATS=OFF Save and exit the file. This variable must be set to either ON or OFF to match the setting of the BSS.0 -name “*. verify the setting of the PM_HOURLY_STATS environment variable. 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>. or no_db_storage one at a time to the parser. As user omcadmin execute the following commands: /bin/find $OMC_TOP/ne_data/raw_stats/100.bad_header filename pm_manual_parse filename Continued 2-32 68P02901W19-S Oct 2009 . failed_load. As user omcadmin execute the following commands: cd /usr/omc/config/global Using the vi editor. As user omcadmin execute the following command: echo $FMPATH This environment variable should be set to: /usr/omc/ne_data/raw_stats 3 Check if any raw statistics files have escaped processing by the parser.bad_header files exist. 5 Where . As user omcadmin execute the following command: ps -elf | grep + | grep Parser 2 Check that the FMPATH environment variable is set.

7 If the Parser process fails and is restarted. 20050405000016 FP : FILE HEADER : NE Type 31 : NE Id 1 : Time 2005-4-4 1900 : V 1900 20050405000016 complete. Refer to Using neighbor statistics on page 13-91 in Chapter 12 for further details about raising the maximum limit of neighbor statistics. check whether the statistics collection and parsing operation resume without manual intervention. Parsing Output 20050405000016 (22027) FP : File added to Parser List.csh file.1/1 68P02901W19-S 2-33 Oct 2009 .Operating Information: OMC-R System Administration Table 2-2 Manual parsing of statistics checklist Manual parsing of statistics checklist (Continued) Serial number Method Check NOTE This workaround only temporarily sets the value of PM_HOURLY_STATS. To make the change a permanent one. 6 Check that the manual parse was successful.0/31. set the value of the PM_HOURLY_STATS variable in the /usr/omc/config/global/pmProcConfig. As user omcadmin execute the following command: tail -f $SYS_LOG/fpomcaudit<yyyymmdd> Successful parsing output is shown in Parsing Output. As user omcadmin execute the following commands: cd /usr/omc/logs ls -l fpomc* 9 As user omcadmin execute the following commands: 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 environment variable. 8 Check that the fpomcaudit log file is rolled over and that old logfiles are removed successfully by the maintain_script cronjob. If an omc stop and start is performed on the system. this change is overwritten. (4701:2) PML: BIN File /usr/omc/ne_data/raw_stats/100. 20050405000017 20050405000017 (22027) 23:30:0:825 : Duration (22027) FP : UNL preparation for current statsfile (4701:1) PML: PM_I_PARSFILE_MSG received. As user omcadmin execute the following command: tail -40 $SYS_LOG/fpomcaudit<yyyymmdd> The log file shows that files are being parsed again successfully.

0/31.0/31. 20050405000034 (4701:9) PML: BIN File /usr/omc/ne _data/raw_stats/100.23:30:0-4:4: 2005 Loading started. 20050405003017 (4701:1) PML: PM_I_PARSFILE_MSG received 20050405003017 (4701:2) PML: BIN File /usr/omc/ne_data/raw_stats/100.0/31.0:0:0-5:4:2005 deleted.0/31. 20050405003034 (4701:9) PML: BIN File /usr/omc/ne_data/raw_stats/100.0:0:0-5:4:2005 Loading started. See Database utilities on page 8-4 in Chapter 8 for further details of the pm_manual_parse utility. 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.23:30:0-4:4:2005 Loading completed.23:30:0-4:4 :2005 deleted 20050405003016 (22027) FP : File added to Parser List.1/1.1/1.0/31.1/1. 2-34 68P02901W19-S Oct 2009 .Manual parsing of statistics checklist Chapter 2: System management . 20050405000034 (4701:9) PML: BIN File /usr/omc/ne_data/raw_stats/100.1/10:0:0-5:4:2005 Loading completed.1/1. 20050405003034 (4701:9) PML: BIN File /usr/omc/ne_data/raw_stats/100.

a printout of the processes running on both the system and GUI processors should be made.Operating Information: OMC-R System Administration 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. 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 1 Enter the following command to obtain printable files of processes: ps -elf > filename 2 To print a file enter the following command: lp filename 2-35 Oct 2009 .

. the netstat function is disabled in GSR9. login id omcadmin). The security of the OMC-R system is the responsibility of the system administrator. to use the function turn it on manually. The OMC-R cannot support more than 200 users. 2-36 • Enabled connection logging (inetd connections. • Whether users require special privileges (for example. • Enabled ftp connection logging. who should pay particular attention to the following: • The number of users on the OMC-R system.rhosts file). normal OMC-R software access (for example. • Ensuring that all remote X terminals have a unique local configuration file setup. or restricted OMC-R software access (for example.Security overview Chapter 2: System management 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. Services A summary of the changes is listed as follows. This means certain services may have to be manually re-enabled to re-introduce functionality which was previously relied upon. the system has been made more secure by default. For example. including the storage of all tapes. NOTE The number of users supported by the OMC-R at any time is 200. group id omc). • 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. group id omcread). • Disabled sendmail (except for local mail). /var/log/connlog). As part of GSR9. • Tape archiving and backup procedures. • Any network file that contains security-related information (for example. The text in brackets details some of the files and settings affected by the changes. • The regular update of OMC-R user passwords. 68P02901W19-S Oct 2009 .

rstat S90webconsole rsh S50apache To view a complete list of the services that are operational. etc). • NIS no longer mandatory. at (/etc/cron.eklogin rstat login .allow /etc/cron. spray. • Restrict cron. 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 .d/cron.d/at. • Disabled root login (unless on console). • Disabled root ftp access (/etc/ftpd/ftpusers). run the following command as user root: svcs 68P02901W19-S 2-37 Oct 2009 . apache.Operating Information: OMC-R System Administration Services • Disabled public tty access (mesgn).rlogin rusers login . and many more). ip_forward_src_routed. ip_respond_to_timestamp. • Improved TCP sequence numbers (TCP_STRONG_ISS=2).allow). • Log failed logins (SYSLOG_FAILED_LOGINS=0). • ssh available for use.rusers S90webm rpc . • Limit valid shells (/etc/shells). • Disabled any unused services (finger. • Network stack tweaks (ip_ignore_redirect.klogin gss rexec rquota kshell ipp-listener shell rfc1179 finger S42nackmod telnet S47pppd ftp S73cachefs_daemon rpc .

• Root cannot ftp into the box. perform the following as user root: svcamd disable <service> This stops the service and prevent it from automatically starting on boot-up. it implies that the service is not managed under the Solaris10 Service Management Facility. 68P02901W19-S Oct 2009 . This restarts the service and configure it to start automatically on boot-up. • Extra connection logging (in /var/adm/messages. run the following as user root: /etc/rc2_d/S87x25net start Enabling and disabling services If a particular service (for example. /var/log/authlog and /var/log/connlog). : legacy_run 15:03:14 lrc:/etc/rc2_d/S87x25net . including disabled services. /var/adm/loginlog. • System accounts locked. Stop and start the service by running the script by passing a start/stop parameter. • /etc/shells file limits valid shells. Using the S87x25net example shown to start the service. Similarly. to disable a service.Enabling and disabling services Chapter 2: System management To view a complete list of services. 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. run the following command as user root: svcs -a NOTE If a service is labeled lrc as shown in the following example. Other security changes In addition to the disabling of many services. such as sendmail) is required. other changes have been made in GSR9 as follows: 2-38 • Root can only log in directly through console (not directly through telnet).

• Stack exec protection.Operating Information: OMC-R System Administration • Network stack tuning. • Cron and at job access limited. 68P02901W19-S Other security changes 2-39 Oct 2009 .

• Database administration is performed using the informix login id on the system processor. Login id informix 2-40 • The login id informix is the owner of the OMC Relational Database Management System (INFORMIX). 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. • The home directory for informix is /usr/informix. This user is able to remove the OMC software. It is the responsibility of the system administrator to change the omcadmin passwords. The passwords must be changed regularly. and its group id is informix. • The home directory for omcadmin follows the same path as all the OMC users (/home) and belongs to the group omc. edit. • 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.Controlling user activity on the system Chapter 2: System management Controlling user activity on the system ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Login IDs for system control To control all user activities on the OMC system. • The root owner can control. • The login id root should only be used by the system administrator. protection or grouping. the root owner can delete any file on any of the processors file systems. • The login id omcadmin is used by both the system administrator and the OMC Operator. or manipulate any other user of that UNIX system. Login id omcadmin • The login id omcadmin is set up with the same user id on all processors. 68P02901W19-S Oct 2009 . regardless of their ownership. In particular. and usually runs the OMC activities. • The login id informix is only used by the system administrator. • This login id is the owner of the OMC software.

• omcadmin. whereas OMC users in the omcread group can only perform non-destructive tasks.Operating Information: OMC-R System Administration System security System security It is important to restrict the number of personnel that use and know the passwords of the login ids: • root. Any number of OMC users with an individual login id can be added to the system. OMC users in the group omc can perform all the usual network operator tasks. The group id given to OMC users can either be omc or omcread. 68P02901W19-S 2-41 Oct 2009 . • informix.

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

Operating Information: OMC-R System Administration Packet Switch passwords Packet Switch passwords The password of the Packet Switch is the responsibility of the system administrator. 68P02901W19-S 2-43 Oct 2009 . The process of setting or changing the Packet Switch password is described in the manufacturer's documentation.

NFS is used by the OMC-R software to remotely mount the Event Log file system onto GUI processors. The . • Network File System (NFS). 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. Figure 2-12 shows how different software packages are secured to avoid unauthorized access.Network file security Chapter 2: System management 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). list local file systems that can be accessed by other hosts on the network with NFS capabilities. The /etc/dfs/dfstab file on the system processor and the /etc/vfstab file on other SPARC based processors. • File Transfer Protocol (FTP). The file /etc/dfs/dfstab lists the file systems that can be accessed by other hosts with NFS. 2-44 68P02901W19-S Oct 2009 . It can also be used to remotely mount any other file system.rhosts file should only contain entries for hosts on the local OMC-R network.

as a package of the form MOTh1900xx where xx indicates the point release of the load installed.Operating Information: OMC-R System Administration 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. 68P02901W19-S 2-45 Oct 2009 .

The alarms and events are displayed at one or all OMCs in the network. but the user has to confirm this dialog box once every hour while the RTF limit continues exceed the OMC-R RTF limit. a dialog box to this effect is displayed. but does not exceed the RTF limit. The OMC-R has a threshold RTF value of 90 percent of the RTF limit. or set outside the permissible range of 2 to 48 hours. TCHs are also not a reliable measure of capacity because their number may change dynamically. respectively. by displaying an alarm GUI error dialog box. If the number of configured RTFs exceeds the OMC-R RTF limit. The alarms are only generated the first time the threshold is exceeded. This ensures that operators are aware of the additional hardware and/or software licenses required to support further traffic channels. the default value of 12 hours is used. The OMC-R checks the number of configured RTFs when an RTF is being created. a major severity alarm is generated. 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 new limit comes into effect immediately with subsequent effect on any related alarms. The result of the audit (actual usage) is compared with the license file per feature. 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. the Licence Audit Tool generates a corresponding event. 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. Capacity control mechanism An OMC-R can support only a particular number of RTFs. This check is also performed during OMC-R startup. If the interval parameter is not set. 2-46 68P02901W19-S Oct 2009 . The audit is triggered by a configurable interval parameter in the OMC software. the RTF limit. RTF is used as a measurement instead of TCH because it is a more accurate measure of the capacity of the system. If the usage is within the limit.Capacity control Chapter 2: System management 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. as configured during installation. The RTF limit is set during staging and can only be modified with the assistance of Motorola. An alarm is generated for each feature where the license usage is exceeded. and there is no easy way to calculate a reliable total. This dialog box does not affect OMC-R operation. If this number exceeds the threshold RTF value. If the limit is changed. This dialog box informs the user that the OMC-R is exceeding its licensed RTF capacity. A critical alarm is generated if the value exceeds the RTF limit. Feature Capacity Licensing and Audit The Licence Audit tool monitors the usage of carriers across the network on a per feature basis.

Operating Information: OMC-R System Administration Licence violation alarms Licence violation alarms The following alarms are produced in the case of license violation: • 30039 OMC-R Capacity Ceiling Violation. Updating RTF license limit To execute the following procedure.com for further information. too many RTFs in MIB Critical • LicenseAuditNotAvailableAlarm Critical • LicenseFileNotAvailableAlarm Critical • LicenseViolationAlarm Critical NOTE If any of the above mentioned alarms occur.omc process: kill -15 <lmgrd.omc process id number: ps -ef | grep lmgrd. inform the Motorola support group.mot. too many NEs in MIB Critical • 30038 OMC-R Capacity Ceiling Violation. contact sysdep_cro@ecid.cig. Use the following procedure to update the RTF license limit. Procedure 2-22 Updating the RTF license limit 1 Login as root on the system processor and remove the old license file: rm /opt/omc/license_tools/license_file 2 Obtain the lmgrp.omc 3 Terminate the lmgrp. 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.omc pid number> Continued 68P02901W19-S 2-47 Oct 2009 .

for example. 10 Enter the checksum when prompted. Invoke New License 2. 8 Enter NE limit. 6 Enter the encryption key when prompted. 128. Quit ====================================================== Enter Option: 5 Enter 1 to invoke New License option. when prompted. please refer to System Information: License Audit (68P02901W59). 1000. for example. 86B0997EFF9. 131. The following output is displayed: Are you happy with these entries [y/n]? 11 Enter y if all entries are acceptable. 23-Oct-2003. For specific details on configuring licenses with this tool.Updating RTF license limit Chapter 2: System management 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. for example. 9 Enter the Licence issue date. for example. 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. when prompted. for example. 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. 7 Enter the new updated RTF Licence limit. 2-48 68P02901W19-S Oct 2009 .

On the first failure. as well as with processes that may recover after longer intervals. current remote login sessions will be disconnected and will need to be reconnected. • nameserver. GUIs will need to be restarted if the entire OMC-R restarts. it is necessary to perform a manual OMC-R stop or start. or if certain other processes are restarted.Operating Information: OMC-R System Administration Restartable processes Restartable processes ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Restartable and non-restartable processes Processes running on the OMC-R are divided into two categories after startup: • Restartable. the entire OMC-R is restarted. • Critical (non-restartable). 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 (non-restartable) process fails. or hangs. If this process fails. For example. The command line utility omctool is provided to enable the OMC-R system administrator to forcibly restart a process. Any process that fails may lose operations that were in progress when it failed. Restarting processes The OMC-R attempts to start failed restartable processes indefinitely. if the RLogin process stops and restarts. • em_lm_main. then the entire OMC-R is restarted automatically. If a critical process fails. The following processes are critical processes: • em_main. If this does not restart the process. A restartable process is a process which is restarted automatically if it fails. five further attempts will be made at intervals of 150 seconds and thereafter every 900 seconds. • cm. NOTE An automatic OMC-R restart does not take place if the nameserver critical process fails. This enables the OMC-R to cope with processes that cannot be restarted without operator intervention. 68P02901W19-S 2-49 Oct 2009 . If a restartable process exits suddenly. a restart is attempted immediately. it is restarted without operator intervention.

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

NOTE: An OMC Process Has restarted . then the remote login functionality is unavailable. The OMC system administrator should also examine the omcaudit log to see why the process died in the first place. the console displays a message similar to the following: Thu Dec 11 15:04:18 2003 .NAME The user should ensure that the process restarts successfully by examining the console. and ensure that this message does not continually repeat. When a process fails to respond to polling the console shows the following message: Thu Dec 11 15:53:46 2003 . certain operations may fail. Process fails to respond to a periodic health check The OMCINIT process periodically polls other processes to make sure they have not hung. 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. then only that process is restarted. the OMC-R should restart automatically. if RLogin fails to start.WARNING: An OMC Process is not responding to Polling .Operating Information: OMC-R System Administration Messages in the OMC-R console and audit log Process restarts When a process is restarted. If the process is critical. Depending on which processes did not start.NAME If the process is restartable. then the entire OMC-R is shut down and restarted. the OMC-R system administrator should examine the omcaudit log files to determine which processes did not start and what is wrong with them. The OMC-R system administrator should check that the process is shut down and restarted. 68P02901W19-S 2-51 Oct 2009 . The OMC-R system administrator should check that the OMC-R is restarted and remains up.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. For example. 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 .

any currently active resyncs will fail because the BSS cannot communicate with the OMC-R. GUIs can be restarted.WARNING: PMproxy unable to access PM Database This message is unlikely to appear. The console displays a warning message that the Event Interface has died and is being restarted. a message similar to the following is displayed on the console: Thu Dec 11 12:12:16 2003 . warning that ResyncCtrl has died and is being restarted. Event Interface dies If the Event Interface EVTIF dies. The user may restart the failed resync when the Event Interface process restarts. 2-52 68P02901W19-S Oct 2009 .Messages in the OMC-R console and audit log Chapter 2: System management OMC-R starts successfully If all OMC-R processes have started successfully. PM proxy cannot access PM database If the PM proxy cannot access the PM database. Event Interface dies during an audit If the Event Interface dies. any currently active audit is aborted. connections are dropped. The console displays a warning message that the Event Interface has died and is being restarted. Event Interface dies during a resync If the Event Interface dies. The user may restart the aborted audit when the Event Interface process restarts. any currently active resyncs are aborted and the process is restarted. The console displays a warning message that this process has died and is being restarted. The user may restart aborted resyncs when the ResyncCtrl process restarts. A console message appears. report the problem to Motorola. The NE should reconnect when the Event Interface restarts. ResyncCtrl dies during a resync If the ResyncCtrl process dies. If it does appear.

After all the processes have been shut down. The console displays a warning message that the uploader has died and is being restarted. 68P02901W19-S 2-53 Oct 2009 . A console message appears stating which monitor process has died. informing the user to restart the GUI to reconnect to the OMCINIT process. a message box appears to inform the user that the channel has died and the download status window is closed. A console message appears. GUIs will have to be restarted manually. Downloader dies during a download If the downloader dies. 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 user must then restart the GUI. Monitor process dies If the monitor process dies. Download status can be invoked again when the downloader has restarted. current uploads are aborted. Statistics file uploads will be retried automatically. a message box appears in addition to the console message. 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. The upload status window is closed. it terminates its remaining processes and then restarts all processes under it. Event Manager dies during alarm or event display If the Event Manager dies due to event overload. warning that the upload IPC channel has been deleted. this is reported in a console message. The monitor process itself is restarted by OMCINIT.Operating Information: OMC-R System Administration Messages in the OMC-R console and audit log Uploader dies during an upload If the uploader dies. The user must restart the GUI. downloads should resume automatically. Unlike uploads. a console message appears warning that the downloader has died and is being restarted. The console displays a warning message that the OMCINIT process is shutting down. If a download status window is active. If the uploader dies during an active upload. When the processes are restarted. all OMC-R processes are restarted. Upload status can be invoked again when the uploader has restarted and any aborted database uploads have to be restarted manually. If alarm or event windows associated with this EM channel are open. a message appears on the console to inform the user.

OMCINIT process dies If OMCINIT dies. If the X25_EVT1 and X25_EVT2 processes fail.The console displays a warning message that this process has failed and OMCINIT is shutting down. all processes it has started are shut down. all the processes are restarted. new downloads will not be initiated. After all OMC-R processes have been shut down. X25_UPL2. A console message appears. A console message will appear warning that this process has died and OMCINIT is shutting down. As with the EM. This corrects itself when the process restarts. all of the OMC-R processes will shut down if this critical process fails. uploads will be interrupted.25 processes restart The X25_BTL1 and X25_BTL2 processes handle downloads. A console message appears telling the user to restart the GUI to connect to the OMCINIT process. but the user will have to restart audits and resyncs. When they restart. stats collection and parsing should resume without operator intervention. Parser process restarts If the PARSER process fails and is restarted. and resyncs will fail. 2-54 68P02901W19-S Oct 2009 . As with the EM. If they die. Console messages will appear warning that the X. Then the user must restart the GUI. X. Configuration Manager dies The Configuration Manager is a critical process. remote login sessions will have to be restarted after this process has restarted. Operator initiated uploads (as opposed to statistics) will have to be restarted. 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. warning that the process has died and is being restarted. all the processes are restarted.Messages in the OMC-R console and audit log Chapter 2: System management EM List Manager dies The EM List Manager is a critical process. The user must then restart the GUI. events. A minder application omcminder then restarts OMCINIT. If the X25_UPL1. X25_UPL3 or X25_UPL4 processes fail. After all OMC processes have been shut down. audits. all the OMC-R processes will shut down if the EM List Manager critical process fails. NEs should reconnect again.25 process has died and is being restarted. A console message appears telling the user to restart the GUI to connect to the OMCINIT process. If the X25_RLOG process fails. The console displays a warning message that the OMCINIT process is down. The user must restart the GUI when this message appears.

current remote login sessions will fail and will need to be retried.Operating Information: OMC-R System Administration omctool utility FCCHAN process restarts If the FCCHAN process fails. 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. omctool utility CAUTION The omctool application should only be used by the OMC system administrator under the direction of Motorola. • Restart a process. NOTE If the option to generate log files is selected.LIST) with the -m option. only the batch output log file is generated. If the RLogin process stops and restarts. 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. FMMGR process restarts If the FMMGR process fails. it is restarted without operator intervention. Remote login process restarts If for any reason a remote login process RLogin should die. The omctool utility can be used to: • Switch debugging on or off for a process. • Reconfigure a process. A console message will appear warning users that this process has died and is being restarted. A console message will appear warning that the process has died and is being restarted. it will be restarted. 68P02901W19-S 2-55 Oct 2009 . A console message appears warning that this process has died and is being restarted. it will be restarted without operator intervention. or • Its mnemonic name (given in STARTUP.

omctool utility Chapter 2: System management The action to be taken must be specified by: • The -r option to restart the process.CNFG file to be re-read and therefore does not require the process to be restarted. the -d debugging option generates large files and will impair system performance. • The -d on or -d off option to switch debugging ON or OFF. • The -c option to reconfigure the process. The information that it produces is of use to only Motorola engineers. In particular. This causes the OMC. 2-56 68P02901W19-S Oct 2009 . The omctool utility should only be used under the direction of Motorola.

When the UPS battery is close to depletion. The system is then shut down. The activation of these scripts is dependent on the UPS and is thus outside the scope of this description. the OMC will shut down. • If the operator issues an omc stop command during OMC startup. In this case. the OMC informs all OMC users through the OMC console window. the OMC will continue to function normally. NOTE Only users who are logged into functioning machines are informed. Implementation of graceful shutdown Graceful shutdown is implemented by the introduction of a set of OMC software scripts. 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. 2-57 Oct 2009 . the OMC can operate without a UPS installed. 68P02901W19-S • When the mains power to the UPS is restored. a further message is sent to any remaining users. Sufficient time is allowed for this message to reach all active users before the shutdown occurs. • If the UPS indicates a low battery condition. The system processor can be powered by a Smart Uninterruptible Power Supply (Smart UPS). As this feature is optional. • If the mains power to the UPS fails.Operating Information: OMC-R System Administration 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 OMC logs UPS events in the system processor audit file. Any GUI users are warned when the system processor is switched over to the UPS. the OMC informs all OMC users through the OMC console window that a shutdown is no longer pending. the OMC will shut down. These scripts are run under the control of the UPS software when certain UPS events occur. All users will be informed that a shutdown is about to occur. Supporting software runs on the system processor and a serial cable connected to the UPS delivers status information to it.

UPS setup Chapter 2: System management UPS setup To ensure maximum protection for the OMC. 2-58 68P02901W19-S Oct 2009 . This ensures that repeated mains failures do not cause uncontrolled power cuts at 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. 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.

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

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 . This necessitates the provision of a mechanism to enable single workstation access to multiple system processors. it is necessary that an operator be able to hand over management of one network region to another OMC-R during the night shift.OMC-R night concentration centre configuration Chapter 2: System management OMC-R night concentration centre configuration For large systems that contain multiple OMC-R networks.

Prerequisites for setup of a night concentration centre The following procedures must be completed before commencing the setup of a night concentration centre.Operating Information: OMC-R System Administration 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. • Night concentration procedures do not support the use of NIS. 68P02901W19-S 2-61 Oct 2009 . • local_gui: The hostname of the local GUI server processor. The operator has to log out and login again as a different user to gain access to the remote OMC-R. Refer to Installation and Configuration: OMC-R Clean Install (68P02901W47) for details. The remote OMC-R that the operator accesses. One of these is the operators local OMC-R system. • Access to the OMC-R systems is mutually exclusive. • A minimum 64 KB digital leased line is required to run the OMC remotely. • remote_user: The username of the account used to access the remote OMC-R. It is recommended that the information be entered in Table 2-3 and Table 2-4. Each special user accesses a specific remote OMC-R which is specified during initial set-up of the night concentration feature. • The local and remote OMC-R systems must have version GSR9 of the OMC-R software installed. The others are remote OMC-R systems that are normally monitored at night. 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. • The hostname and IP addresses of the different processors must be obtained for each remote OMC-R. • remote_sys: The hostname of the remote system processor. • The GUI server used for this feature is unable to support any clients. depends on the user that the operator logs in as.

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. It is recommended that the information be entered in Table 2-4. 2-62 68P02901W19-S Oct 2009 . They can be copied and used to record this information.Prerequisites for setup of a night concentration centre Table 2-3 Chapter 2: System management 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.

Use the following procedure to change the files: Procedure 2-23 68P02901W19-S Updating host file entries with hostname 1 Edit the /etc/hosts file on the remote_sys processor and check that the hostname of the local_gui processor is present. 3 Once all changes have been made. 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. Describes how to mount certain file systems.Operating Information: OMC-R System Administration 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. If the entry is not listed.equiv file using a suitable text editor: Where: <local_gui> is Hostname of the local GUI server. If the entry is not listed. The following procedures are outlined: • Updating host file entries. equivalent hosts file. execute the following commands as user root: cd /var/yp /usr/ccs/bin/make 2-63 Oct 2009 . Describes how to change host file entries. • Exporting file changes. add a line similar to the following to the hosts. 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.equiv file on the remote_sys processor and check that the hostname of the local_gui processor is present. • Creation of a new account. 2 Edit the /etc/hosts. and rhosts file.

root=sparc0:<local_gui> /usr/omc/config/global share -F nfs -o rw=sparc0:<local_gui>. 2-64 68P02901W19-S Oct 2009 . 2 Execute the following command on each of the remote system processors. The account is also created on the remote_sys processors with the same username and UID as that created on the local machine.root=sparc0:<local_gui> /home share -F nfs -o rw=sparc0:<local_gui>.Exporting file changes Chapter 2: System management 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>. as user root: shareall Creation of new account An account must be created to use the remote OMC-R.root=sparc0:<local_gui> /usr/omc/ne_data share -F nfs -o rw=sparc0:<local_gui>.root=sparc0:<local_gui> /usr/omc/ne_data/raw_stats Where: <local_gui> is Hostname of the local GUI server.

/usr/omc/config/global /usr/omc/ne_data /usr/omc/ne_data/raw_stats /home • The GUI server must have an entry for the Remote system processor in each of /etc/hosts.Operating Information: OMC-R System Administration 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).equiv. • The NIS Domain name on each OMC-R on the LAN must be unique. /etc/hosts. • The Remote system processor must have an entry for the GUI server in each of /etc/hosts. /etc/hosts.equiv. • Ensure that the Remote system processor is NFS-sharing the following file systems to the GUI server. 68P02901W19-S 2-65 Oct 2009 . • The maps for each NIS Domain must contain a complete list of all system processor hostnames on the LAN.

21 remote_sys omc_splat omc_pm omc_4gl 3 To switch over to an alternative OMC-R.1 localhost 111.11.13 guiclient1 111.1 localhost 111.111.111.12 local_gui 111. execute the following command: /usr/omc/current/sbin/SwitchSPLAT <remote_sys> Where: <remote_sys> is the hostname of the Remote system processor.111.111.111.111.0.11.11. the GUI server /etc/hosts file should be similar to the following: 127.111.111.111.111.14 netprinter 111.12 local_gui 111.0.0.Switching to an alternative OMC-R Chapter 2: System management Switching to an alternative OMC-R Use the following procedure to switch over to an alternative OMC-R. Procedure 2-25 Switching to an alternative OMC-R 1 Log on to the GUI server root and ensure that there is no GUI running on the GUI server.21 remote_sys Edit the GUI server /etc/hosts file so that the remote_sys is aliased to omc_splat.11.0. omc_pm and omc_4gl: 127.111.11.11 local_sys omc_splat omc_pm omc_4gl 111.13 guiclient1 111.111. NOTE The GUI server reboots automatically.111. 2 Initially.11 local_sys 111.111.11. 2-66 68P02901W19-S Oct 2009 .14 netprinter 111.

Hostfile changes Remove references to the remote system processor from /etc/hosts. • Host file changes. /etc/hosts. 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. 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.Operating Information: OMC-R System Administration 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 following procedures are described: • Deletion of the OMC-R remote user account. The procedures listed in Table 2-5 are outlined. 68P02901W19-S 2-67 Oct 2009 .equiv. 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 . • Deletion of the OMC-R remote user account. 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. Export file changes Edit the /etc/dfs/dfstab file on each of the remote_sys processors.Remote system processor rollback Chapter 2: System management 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. Deletion of OMC-R remote user accounts Refer to Administering user accounts with usertool on page 2-12 for details on administering user accounts. Remove the reference to the local_gui processor.

UTF-8 cs_CZ cs_CZ. .BIG5HK@stroke zh_HK.UTF-8@radical zh_HK.ISO8859-1 . iso_8859_7 iso_8859_9 hi_IN.BIG5HK@radical zh_HK.ISO8859-2 cz de de.BIG5HK zh_HK.ISO8859-15 Continued 68P02901W19-S 2-69 Oct 2009 .BIG5 zh_TW.ISO8859-1 iso_8859_13 iso_8859_15 iso_8859_2 iso_8859_5 es es_CR es_CR.EUC zh_TW.UTF-8 zh_HK.UTF-8@stroke zh_TW zh_TW.Operating Information: OMC-R System Administration Setting the locale on the OMC-R Setting the locale on the OMC-R ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ The following procedure demonstrates how the locale on the OMC-R can be changed. Procedure 2-26 1 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.UTF-8 ja en_AU en_AU.ISO8859-1 en_NZ en_NZ.ISO8859-1 es_GT es_GT.

de_DE.ISO8859-15@euro de_CH . common zh zh. lv_LV.ISO8859-2 .ISO8859-15@euro de_DE.ISO8859-5 et_EE et_EE.UTF-8 de_DE. . .UTF-8 sh_BA.UTF-8 de_AT de_AT.ISO8859-1 hu hu_HU hu_HU.ISO8859-2@bosnia sl_SI Continued 2-70 68P02901W19-S Oct 2009 . ru_RU.Setting the locale on the OMC-R Procedure 2-26 Chapter 2: System management Changing the locale of OMC-R (Continued) de. bg_BG bg_BG. .ISO8859-13 mk_MK mk_MK. .UTF-8@euro fr fr_CH fr_CH.ISO8859-2 ru .UTF-8 .ISO8859-5 nr ro_RO ro_RO.GBK zh.ISO8859-1 de_AT.KOI8-R ru_RU.ISO8859-15 de_AT.ISO8859-2 pl . .ISO8859-15 hr_HR hr_HR.ISO8859-5 ru_RU.

UTF-8 en_US. tr tr_TR tr_TR.ISO8859-15@euro es_MX es_MX.UTF-8 ko ko.ISO8859-1@nynorsk no_NY sv sv.ISO8859-15 . .ISO8859-15 sv. .Operating Information: OMC-R System Administration Procedure 2-26 Setting the locale on the OMC-R Changing the locale of OMC-R (Continued) .ISO8859-15 sv_SE.ISO8859-1 da_DK.ISO8859-15 en_US. en_US.ISO8859-1 da da.ISO8859-15 da_DK da_DK. .ISO8859-15@euro sv_SE.ISO8859-1 es_BO es_BO.UTF-8 sv_SE sv_SE.ISO8859-9 tr_TR.ISO8859-1 es_CL Continued 68P02901W19-S 2-71 Oct 2009 .UTF-8 ar .EUC ko_KR.UTF-8@euro es_AR es_AR.UTF-8 he he_IL he_IL.ISO8859-1@bokmal no_NO.ISO8859-1 fr_CA fr_CA.UTF-8 sv_SE.UTF-8 ko_KR.ISO8859-1 sv_SE. no no_NO no_NO.

ISO8859-15 it.ISO8859-15 es.TIS620 th_TH.ISO8859-1 es_VE es_VE.ISO8859-1 pt_BR pt_BR.ISO8859-15 .ISO8859-1 it_IT.ISO8859-1 pt_PT.ISO8859-15@euro th th_TH th_TH.UTF-8 .ISO8859-1 es_ES.ISO8859-1 ca_ES. es.ISO8859-1 ca ca_ES ca_ES.UTF-8 it_IT.ISO8859-15 Continued 2-72 68P02901W19-S Oct 2009 .ISO8859-15 pt_PT pt_PT.UTF-8 es_ES.ISO8859-11 th_TH.UTF-8@euro pt pt.ISO8859-15@euro it_IT.UTF-8 fr_BE.ISO8859-15@euro es_ES.UTF-8@euro it it.ISO8859-1 fr_FR.UTF-8 it_IT it_IT.Setting the locale on the OMC-R Procedure 2-26 Chapter 2: System management Changing the locale of OMC-R (Continued) . .ISO8859-15 es_ES.ISO8859-15 pt_PT.UTF-8 es_ES es_ES.UTF-8@euro fr_FR fr_FR.ISO8859-15 it_IT. . . fr_BE. es_UY es_UY.

UTF-8@euro nl nl.ISO8859-1 nl_BE. # This file looks like a shell script. # # Lines of this file should be of the form VAR=value. # TZ=Eire CMASK=022 LANG=no_NO # 3 68P02901W19-S As user root.UTF-8 pt_PT. or any of the LC_* environment variables.Operating Information: OMC-R System Administration Procedure 2-26 Setting the locale on the OMC-R Changing the locale of OMC-R (Continued) fr_FR. some shell constructs # (i.5 99/05/26 # # This file is /etc/default/init. edit the /etc/default/init file and add your chosen locale. but are ignored.ISO8859-15 nl_BE.UTF-8 el_GR.dfl 1.e.ISO8859-1 nl_NL. but it is not.ISO8859-15@euro ar_SA. LANG.UTF-8 fr_FR. reboot the box by executing the following command: /usr/sbin/shutdown -g0 -i6 -y 2-73 Oct 2009 .ISO8859-15 nl_NL. export commands) are allowed in this file.ISO8859-15@euro nl_NL nl_NL.UTF-8 2 As user root.ISO8859-15@euro fr_FR. /etc/TIMEZONE is a symlink to this file. To maintain # compatibility with old versions of /etc/TIMEZONE.UTF-8 nl_BE. where VAR is one of # TZ.ISO8859-15 nl_BE nl_BE..UTF-8 nl_NL. For example: # @(#)init. CMASK.

Also use the output of this command to check for rogue processes running on your system. Copy the checklist provided in Chapter 13 to record the checks. 4 Check the omc_db_maint log file to ensure that: • PM statistics are unloaded and deleted successfully.General administration checklists Chapter 2: System management General administration checklists ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Daily administration checklist Use the following procedure to perform the daily administration tasks. • Applications are connected and reconnected successfully. 3 Check the output of cron jobs from users root. 2 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. and sys.yyyy. • Disk space is not being consumed. Procedure 2-27 Performing daily administration tasks – initial checks 1 Check the file system capacity: As user root.mm. NOTE These procedures must be executed by an experienced Systems Administrator.dd Continued 2-74 68P02901W19-S Oct 2009 . omcadmin. and that the capacity does not exceeded 90%. it is advisable that the file system is cleaned up. As user root execute the following commands: cd $OMC_TOP/logs more omc_db_maint. If the file system exceeds 90%. 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. execute the following command: df -k Ensure that all necessary file systems are mounted. • PM Fragments are created for the next days statistics.

Refer to the Checklist Manual parsing of statistics in NE database maintenance on page 2-30. 3 Perform a backup of the UNIX file system. Refer to Chapter 12 Backup Server Installation and Configuration.25. 2 Perform a Level 2 backup of the CM database. 7 Check the system processor hardware. 4 Check the status of the disk mirroring and ensure that all sub-mirrors are in an Okay state.Operating Information: OMC-R System Administration Procedure 2-27 Performing daily administration tasks – initial checks (Continued) 5 Check the IDS log files for both PM and MIB INFORMIX DB errors and checkpointing: As user omcadmin execute the following commands: tail -f $INFORMIXDIR/online. 6 Check the integrity of X. by entering the following commands as user root: metastat | more Refer to Checking disk mirroring on page 13-47. 2-75 Oct 2009 . 6 Check that the PM database is online by entering the following commands as user omcadmin: omc_env onmonitor 7 Check that the CM database is online by entering the following commands as user omcadmin: mib_env onmonitor Procedure 2-28 68P02901W19-S Daily administration checklist Performing daily administration tasks – creating backups 1 Perform a Level 2 backup of the PM database. Refer to OMC-R log and error files on page 4-3. by entering the following command as user root: /usr/platform/sun4u/sbin/prtdiag -v 8 Manually parse any unparsed statistics files. 5 Check the OMC-R log files in /usr/omc/logs for unusual output or error messages.log_MIB These log files should show that checkpoints are completed successfully and in particular when the server is initialized.log_OMC tail -f $INFORMIXDIR/online. by entering the following commands as user root: /opt/SUNWconn/bin/x25stat Refer to x25stat output on page 2-76.

Daily administration checklist Chapter 2: System management 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 7 128 129 16 16 129 Restart 0 1 Restart confirm 1 0 RNR 0 0 1119 12536 Resets 1 0 RR Reset confirms 0 1 Diagnostic 0 0 Interrupts 0 0 Registration 0 0 Reg confirm Packets (total) Bytes (total) 0 0 18126 3124 1783971 207183 ------------------------------------Running totals ------------------------------------Tot no of VCs established 2-76 135 Connections refused 0 Connections currently open 3 Max connections open 7 68P02901W19-S Oct 2009 .

socal/sf (scsi-3) 501-3060 5 SBus 25 1 HSI SUNW.hme 1 SBus 25 3 SUNW.0 7 15 1 400 8.0 US-II 10. Intrlv.hme 5 SBus 25 3 5 SBus 25 13 SUNW.501-2253 1 SBus 25 1 HSI SUNW. Brd --- ---- Bank MB Status --------- Condition ----- ------ Speed -- ------ 3 0 256 Active OK 60ns 2-way A 7 0 256 Active OK 60ns 2-way A Factor With ----- ========================= IO Cards ========================= --- Bus Freq Brd ---- ---- Type MHz ---------- Slot Name ---------------------------- Model -------------------- 1 SBus 25 0 cgsix SUNW.0 3 7 1 400 8.fas/sd (block) 1 SBus 25 13 SUNW.Operating Information: OMC-R System Administration Daily administration checklist 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.0 =========================Memory ========================= Intrlv.fas/sd (block) SUNW.0 US-II 10.0 US-II 10.501-1725-01 1 SBus 25 3 SUNW. Mask --- --- ------- ----- ------ ------ ---- 3 6 0 400 8.501-1725-01 5 SBus 25 3 SUNW.0 US-II 10.0 7 14 0 400 8.socal/sf (scsi-3) 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 .

0v OK Peripheral 5.2.Daily administration checklist ---- ------ Disk OK PPS OK Chapter 2: System management System Temperatures (Celsius): -----------------------------Brd State Current Min Max Trend --- ----- ------- --- --- ------ 1 OK 46 42 46 stable 3 OK 33 28 36 stable 5 OK 42 38 42 stable 7 OK 32 27 35 stable CLK OK 36 33 36 stable Power Supplies: --------------Supply Status ------- ------ 1 OK 3 OK PPS OK System 3.9.4.0v OK Peripheral 12v OK Auxilary 5.3v precharge OK System 5. 7 1997/12/08 15:39 iPOST 3. 8 1999/02/19 14:25 Board 3: OBP POST 3.0v precharge OK AC Power OK =========================HW Revisions ========================= ASIC Revisions: --------------Brd FHC AC SBus0 SBus1 PCI0 PCI1 FEPS Board Type Attributes --- --- -- ----- ----- ---- ---- ---- ---------- ---------- 1 1 5 3 1 5 5 1 5 7 1 5 1 1 22 Dual-SBus-SOC+ 100 MHz Capable CPU 100 MHz Capable 1 1 22 Dual-SBus-SOC+ 100 MHz Capable CPU 100 MHz Capable System Board PROM revisions: ---------------------------- 2-78 Board 1: FCODE 1.8.10 1999/02/19 14:23 68P02901W19-S Oct 2009 .0v OK Peripheral 5.3v OK System 5.21 1999/02/19 14:33 3.0v precharge OK Peripheral 12v precharge OK System 3.

ddmmyyyy online. 3 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. Copy the checklist provided in Chapter 13 to record the checks.log_MIB. Refer to Chapter 12 Backup Server Installation and Configuration. 7 Perform an archive of old OMC-R user files by entering the following commands as user root: find /home -mtime +14 -print > /usr/tmp/listing tar -c / usr/tmp/listing /dev/rmt/0 8 Perform a Level 1 backup of the PM database.8.Operating Information: OMC-R System Administration Weekly administration checklist Board 5: FCODE 1.21 1999/02/19 14:33 3.9.2.log_OMC. Continued 68P02901W19-S 2-79 Oct 2009 . 7 1997/12/08 15:39 iPOST 3. Procedure 2-29 Performing weekly administration tasks 1 Check that the Informix online logs are rolled over successfully. 5 Check the file system capacity by entering the following commands as user root: df -k 6 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.log_OMC Ensure that online logs exist in the following format: online.10 1999/02/19 14:23 Weekly administration checklist Use the following procedure to perform the weekly administration tasks.4.ddmmyyyy 2 Perform a backup of the UNIX file system. 4 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. 9 Perform a Level 1 backup of the CM database. 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. by entering the following commands as user omcadmin: cd /usr/informix ls -l online. 8 1999/02/19 14:25 Board 7: OBP POST 3.log_MIB ls -l online.

and informix. Monthly administration checklist Use the following procedure to perform the monthly administration tasks. 4 Change the standard installation passwords for user root. Refer to Administering user accounts with usertool on page 2-12. Procedure 2-30 2-80 Performing monthly administration tasks 1 Perform a backup of the UNIX file system.Monthly administration checklist Procedure 2-29 10 Chapter 2: System management Performing weekly administration tasks (Continued) System security should be monitored by the system administrator. 3 Perform a Level 0 backup of the CM database. 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 . and inform the required users. Refer to Chapter 12 Backup Server Installation and Configuration. 2 Perform a Level 0 backup of the PM database. Copy the checklist provided in Chapter 13 to record the checks. 5 Truncate the cron log file. omcadmin. Refer to Security overview on page 2-36 for further details about important security aspects.

Chapter 3 Ancillary Devices ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 68P02901W19-S Oct 2009 3-1 .

• Troubleshooting the modem on page 3-19.Overview Chapter 3: Ancillary Devices Overview ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ This chapter contains installation. The following topics are described in this chapter: • • 3-2 Configuring the serial port with Serial Port Manager on page 3-3. and troubleshooting information for OMC-R ancillary devices. configuration. Introduction to modem installation on page 3-7. 68P02901W19-S Oct 2009 . • Adding a printer on page 3-25.

or deletion. • Quick visual status of each port. • Testing the modem installation procedure.Operating Information: OMC-R System Administration Configuring the serial port with Serial Port Manager Configuring the serial port with Serial Port Manager ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Overview of Serial Port Manager The Serial Port Manager enables the system administrator to manage serial port services for terminals and modems. • Installing a modem. 3 Select the Port Manager option. NOTE A modem cannot be connected to the SunFire 4800. The following procedures are outlined in this section: • Adding a modem. 3-3 Oct 2009 . modification. 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. Procedure 3-1 68P02901W19-S Accessing the Serial Port Manager 1 Login to the system processor as root. It features the following operations: • Templates for common terminal and modem configurations. • Setting an additional baud rate. • Multiple port setup. Accessing Serial Port Manager Use the following procedure to access the Serial Port Manager. 2 Click on the system administration icon.

No Connection: The port service is initialized but not configured.Serial Port Manager parameters Chapter 3: Ancillary Devices Serial Port Manager parameters The following functions can be handled using the Serial Port Manager. • Initialize Only . • Terminal Type: Specifies the terminal type connected to the port. • Service: Specifies that the service for the specified port is turned on. More. The More and Expert modes each show progressively more configuration data and controls.Dial In Only: Users may dial in to the modem but cannot dial out. Basic detail • Port: Lists the port selected from the Serial Port Manager main window. and Expert.Hardwired: Users may log in through a terminal directly connected to the system. • Modem . These levels of detail are called modes. Detail The Modify window provides information about the port in three levels: Basic. • Modem . • Baud Rate: Specifies the line speed used to communicate with the device. 3-4 68P02901W19-S Oct 2009 . The Detail command buttons at the top of the window are used to display the other modes. • Modem . Basic detail mode is displayed by default. Template This field specifies the preconfigured template used to configure the port from the pull down menu.Dial Out Only: Users may dial out from the modem but cannot dial in. The following templates are available: • Terminal . Use this to initialize the port connection without actually connecting a device to the port.Bidirectional: Users may either dial in or out from the modem.

If this option is not checked. • Software Carrier: Specifies that the software carrier detection feature is used. • Connect on Carrier: Specifies that a ports associate service is immediately invoked when a connect indication is received. • Bidirectional: Specifies that the port line is used in both directions. • Login Prompt: Shows the prompt after a connection is made.Operating Information: OMC-R System Administration Serial Port Manager parameters More detail • Initialize Only: Specifies that the port software is initialized but not configured. Expert detail • Create utmp Entry: Specifies that a utmp entry is created upon login. • Port Monitor Tag: Specifies the port monitor name to be used for this port. • Streams Modules: Shows the streams modules that are pushed before the service is started. • Service Tag: Shows the service tag associated with this port. • Comment: Shows a text description of the service. 68P02901W19-S 3-5 Oct 2009 . • Timeout: Specifies the number of seconds before a port is closed if the open process on port succeeds and input data is not received. if any. • Service: Shows the program that is run upon connection. the hardware carrier detection signal is used. This item must be checked if a login service is used.

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. 3 Click OK. The Modify window appears in Basic Detail mode. 5 Click OK to configure the port. 4 Change the values of the template entries as required. 2 Enter a baud rate entry from the /etc/ttydefs file that provides seven bits. 2 From the Edit menu. 68P02901W19-S Oct 2009 . 3 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. select the port that is to be used with a modem. Procedure 3-2 Adding a modem 1 In the Serial Port Manager main window. select Modify. Procedure 3-3 3-6 Setting an alternative baud rate 1 Select Other from the Baud Rate menu. even parity service.Adding a modem Chapter 3: Ancillary Devices Adding a modem Use the following procedure to add a modem.

If a remote OMC-R operator terminal is required. Remote access to the OMC-R through a modem can provide TTY (character based) access to the OMC-R. there are three data links present. It does not provide a method to remotely access the graphical functions of the OMC-R. The modem is configured for both dial-in and dial-out access. Data links When connecting two platforms with modems. 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).Operating Information: OMC-R System Administration 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. NOTE The procedures described here may conflict with other programs or serial port users. Support engineers make use of remote access to diagnose and rectify problems. Connect the modem to an unused port or disable the port monitor services. Figure 3-1 68P02901W19-S Data links between two platforms 3-7 Oct 2009 . Any serial port modem is supported. it should be connected to the OMC-R using LAN routers over a synchronous link operating at speeds of at least 64 kbps.

2 k). In the following example.6 kbps. make the DCE link appear to operate at 20+ kbps. • Verifying port monitor services. While using a system which shares ports A and B. such as the platform 10. in theory. • DCE rate = 9. Initial modem setup NOTE The root password is required to install or modify files for modem installation.4 kbps. Physical connection Install the modem on the SPARCstation. The initial platform setup involves the two activities mentioned as follows: 3-8 • Defining the dial-in serial port characteristics. Password protection and other security features are described in the modem user guide. The modems may use data compression on the DCE link. • Local DTE rate = 38. The bottleneck would then be the remote DTE rate (19. using either ttya or ttyb (serial port A or B).Rates Chapter 3: Ancillary Devices Rates Data is transferred at the same rate as the slowest link. Any 20 to 25-pin cable is acceptable although only pins 1 to 8 and pin 20 are necessary. The Motorola 3460 Fast'R modem contains various security features to restrict or prevent access. NOTE Do not use a null modem cross-over cable or a null modem gender adapter cable. and if port B is to be used for the modem port.2 kbps. This is helpful if the DCE link is the slowest link. This splitter cable is available from SunExpress (part number: X985A or 530-1869/C9). data compression on the DCE link could. and make sure that the RS232 cable is a straight-through cable. • Remote DTE rate = 19. 68P02901W19-S Oct 2009 . use the splitter cable (port A can be accessed directly without the splitter).

- /usr/bin/login . the above definition uses eight data bits with no parity transfers. the following two lines are displayed as one line on the screen: zsmon ttymon ttyb u root /dev/term/b . 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 u root /dev/term/a . 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. 68P02901W19-S 3-9 Oct 2009 .9600 ldterm.Operating Information: OMC-R System Administration Initial modem setup Define dial-in serial port characteristics Add the following entries to the /etc/ttydefs file. remove them by typing the following command on the platform as user root. Also. Verify current port monitor services Verify that there are no port monitor services on the port to be connected to the modem.that is ttya or ttyb> This can also be achieved by using the serial port manager available under CDE when logged in as root. 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. ttcompat login: . ipmadm -p zsmon -r -s <SVCTAG value from the above. Modem to serial port speeds should be faster than modem to modem speeds in order to prevent bottlenecks. ttcompat login: .vt100 y #Terminal Also. by typing the following command on the platform as user root.9600 ldterm.vt100 y #Terminal If there are services present. and selecting Delete or Disable for the port. as indicated in the output displayed.- /usr/bin/login . The login services need to be removed or disabled before a new ttydefs entry can be used.

use /b). Configuring tip NOTE Always use the same speed to tip to the modem as the login process is set to use. otherwise a carriage return is not sent. If an OK prompt is not returned. The following procedure assumes that the modem is to be connected using port b. For ttyb. try a different port or cable. After the connect message type: AT An OK prompt is returned. tip -38400 /dev/cua/a (38400 sets the connection speed. alter the procedure accordingly. NOTE Ensure that tip is executed in a shell without scrolling enabled. If the modem is to be connected using port a. Verify that the modem is responding to commands. enter the following command on the platform as user root. Ensure that the modem responds to AT command before continuing with the subsequent sections. 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 . /a assumes ttya.Communicating with the modem Chapter 3: Ancillary Devices Communicating with the modem Once the port monitor services have been deleted or disabled.

Operating Information: OMC-R System Administration Procedure 3-4 Controlling modem access Configuring the tip utility (Continued) NOTE When using a 28. and for a 9600 modem. chmod 700 /usr/bin/tip NOTE Changing the permissions of tip may affect other users or programs that need to use tip. even if power is lost. the OMC-R Test Mobile feature. for example. To allow only root users the ability to log out using the modem. for a 14. See the modem users guide for a complete list of the Hayes command set. Controlling modem access Control the modem communication by setting the permissions of the tip utility. chown uucp /dev/cua/b 3 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. Once the modem is set up.8 k modem.4 k modem use 19200. For port a: chmod 666 /dev/cua/a. the configuration can be stored in the non-volatile memory in the modem. use 9600. set the tip permissions to 700 by entering the following command on the platform as user root. 68P02901W19-S 3-11 Oct 2009 . 2 Change the permissions and the owner of the modem port. check the /etc/remote file for errors to the modem entry. Modem setup and Initialization The modem is set up using Hayes AT commands. It should only be necessary to configure the modem once. chown uucp /dev/cua/a For port b: chmod 666 /dev/cua/b. use 38400. If not.

enter the correct AT command for the modem type and DTE rate (Table 3-1). Continued 3-12 68P02901W19-S Oct 2009 . &F Reset Modem to default factory settings.Configuring the Serial Port Modem Chapter 3: Ancillary Devices 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. Table 3-1 Modem initialization commands Modem type DTE rate Motorola 3460 38400 AT&FQ2*DE19*FL3&D2&C1*CL0S0=2&Y1&W1 19200 AT&FQ2*DE12*FL3&D2&C1*CL0S0=2&Y1&W1 9600 Motorola 326X Initialization command AT&FQ2*DE8*FL3&D2&C1*CL0S0=2&Y1&W1 38400 AT&FQ2*DE15*FL3&D2&C1*AA2&Y1&W1 19200 AT&FQ2*DE12*FL3&D2&C1*AA2&Y1&W1 9600 AT&FQ2*DE8*FL3&D2&C1*AA2&Y1&W1 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. exit the tip utility by typing a carriage return followed by a tilde (~) character which is followed by a period (. Notes The four factory default option sets are restored to their original settings. all stored telephone numbers are deleted. The AT command configures the modem and stores the setup in the non-volatile memory. Table 3-2 Syntax of the AT command Symbol Meaning AT Enter command mode.) character. 2 After setting up the modem. Procedure 3-5 Configuring the Motorola 3460 and 326X modems 1 At the OK prompt.

the modem does not auto answer. Saving changes When using AT commands or front panel options to alter the modem settings. *DE15 sets a DTE rate of 38400. After a few seconds. This command determines how the modem interprets the DTR signal. 68P02901W19-S 3-13 Oct 2009 . the modem does not enter them into memory. &D2 DTR Control = Discon. If DTR is low. DE Fix DTE rate. it automatically uses option set 1. determined by the option set where the new customized option set is saved. After selecting the option set most suited to the application (using the ATZn command). test.*DE12 sets a DTE rate of 19200.24 Circuit 109). signifying that the option set has been successfully saved in the non-volatile memory of the modem. &W1 Save Changes = 1. or escape mode. When the modem is powered up. &C1 DCD Control = Normal. DCD is on in data mode. if the changes are not saved. The modem hangs up and enters the command mode when an on-to-off DTR transition is detected. This determines how the modem sets DCD signals. It is off when the modem is disconnected from the telephone line. The modem will answer incoming calls after two rings (*AA2) or after X rings where X is defined in the S0 register (S0=X). while the modem is in data. The modem signals the DTE with DCD on EIA/TIA 232-D Pin 8 (V.*DE8 sets a DTE rate of 9600. the front panel displays Save Completed. enter the following: AT&W<n> Where is <n> a value between 1 to 4. The local DTE uses DTR (pin 20) to signal the modem. See the paragraph Saving changes.Operating Information: OMC-R System Administration Table 3-2 Configuring the Serial Port Modem 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. The modem front panel displays Saving options. &Y1 Power Up In = 1. *AA2 Answer = Ring #2. *FL3 Flow Control = RTS/CTS. Normal DCD is off during dialing and also while the modem is in training with the remote modem. Check specific in country requirements regarding auto-answer modems. and modifying any required configuration settings.

Table 3-3 AT commands and result codes for country-specific modem configuration Country AT command (hexadecimal) Result Code (decimal) Argentina AT%T19.34 52 Continued 3-14 68P02901W19-S Oct 2009 .0.25 37 Denmark AT%T19.Configuring the MultiModem MT5634ZBA Global Chapter 3: Ancillary Devices Configuring the MultiModem MT5634ZBA Global Set country configuration Use the following procedure to set up the MultiModem MT5634ZBA with the appropriate country configuration: Procedure 3-6 Setting country configuration 1 Execute the following command to load the factory settings as active configuration: AT&F0 2 Execute the following command to set the country code: AT%T19.34 52 China AT%T19.0.0.0.0.nn Where: nn is the Country Code (Table 3-3).0.0.34 52 France AT%T19.01 1 Austria AT%T19.34 52 Belgium AT%T19.0.0.34 52 Czech Republic AT%T19.0.0.34 52 Brazil AT%T19.34 52 Cyprus AT%T19.34 52 Finland AT%T19.0.0.34 52 Canada AT%T19. 3 Execute the following command to save as factory default: AT&F&W 4 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.34 52 Australia AT%T19.

30 48 Poland AT%T19.0.0.0.30 48 Iceland AT%T19.0.0.0.30 48 Ireland AT%T19.34 52 Singapore AT%T19.0.30 48 Spain AT%T19.30 48 Portugal AT%T19.34 52 Switzerland AT%T19.0.34 52 New Zealand AT%T19.0.34 52 Italy AT%T19.0.34 52 Greece AT%T19.0.34 52 Turkey AT%T19.10 16 Korea AT%T19.0.0.34 52 Japan AT%T19.0.34 52 U.0.0.0.30 48 South Africa AT%T19.0.34 52 Netherlands AT%T19.34 52 Slovenia AT%T19.35 53 Slovak Republic AT%T19.0.30 48 Liechtenstein AT%T19.0.0.0. AT%T19.34 52 Luxembourg AT%T19.0.34 52 United States AT%T19.Operating Information: OMC-R System Administration Configuring the MultiModem MT5634ZBA Global 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 India AT%T19.0.30 48 Indonesia AT%T19.0.34 52 Hong Kong AT%T19.34 52 3-15 Oct 2009 .K.09 9 Norway AT%T19.34 52 Mexico AT%T19.34 52 Sweden AT%T19.0.30 48 Hungary AT%T19.0.0.34 52 Philippines AT%T19.0.34 52 Russia AT%T19.0.

AT commands The AT commands that are used when initializing the MultiModem MT5634ZBA are described in Table 3-4. AT&K3 Enable CTS/RTS hardware flow control. AT&D2 If DTR drops while in online data mode. enter: AT$SB38400&K3&D2&C1S0=2&Q0&W0 • For a 19200 DTE rate. After setting up the modem. and goes low when the carrier signal is not detected. ATS0=2 Sets the number of rings until the modem answers. the modem hangs up. 3-16 68P02901W19-S Oct 2009 . AT&Q0 Enables result codes. the modem will not answer or dial. AT&W0 Stores the current modem settings in non-volatile memory and loads them in place of the factory defaults at power-on. Table 3-4 MultiModem MT5634ZBA initialization AT commands AT command AT$SBnnnnn Description Set serial port to nnnnn bps.Configuring the MultiModem MT5634ZBA Global Chapter 3: Ancillary Devices 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$SB19200&K3&D2&C1S0=2&Q0&W0 • For a 9600 DTE rate.) character. If the signal is not present. followed by a period (. exit the tip utility by typing a carriage return followed by a tilde (~) character. These changes then loaded in place of the factory defaults at power-on. or following the ATZ command. AT&C1 DCD goes high when the remote modem carrier signal is detected. enter: AT$SB9600&K3&D2&C1S0=2&Q0&W0 This configures the modem and stores the current modem settings in the non-volatile memory.

2 Click on port a or b with the left mouse button to select the port to be used by the modem. 6 Set Baud Rate to the desired baud rate of the modem.9600 ldterm.Operating Information: OMC-R System Administration Enabling the login process 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 Enabling the login process 1 To view the Serial Port Manager window. 5 Select Bi-directional from template. 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 . 8 Verify that all the amended fields are correct and click the OK button. and click the serial port manager icon. select port manager from the tools icon.dialup n #modem Bidirectional If a port monitor has not been configured for that port. 7 Set Terminal type to vt100. enter the following command at the # prompt: pmadm -p zsmon -l An example output is: PMTAG PMTYPE SVCTAG FLGS ID <PMSPECIFIC> zsmon ttymon ttya u root /dev/term/a . 3 Select modify from the Edit menu. 4 Select the expert display. 9 Close all the open windows. The Serial Port Manager: Modify window appears./usr/bin/login . 10 To verify that a port monitor has been configured. Refer to Table 3-5 for the available baud rate settings. ttcompat login: .

instruct the modem to hang-up the line by typing: +++ ATH 3-18 68P02901W19-S Oct 2009 . If problems occur.Remote connection and file transfers Chapter 3: Ancillary Devices Remote connection and file transfers To test the modem. refer to Troubleshooting the modem on page 3-19. login. Once the login is successful. password and log out information. contact Customer Network Resolution Centre (CNRC) for a telephone number.

the modem never picks up the phone. All ports busy This message indicates that another process has control of the port. • Nothing happens when trying to tip the modem. • Modem hangs up after answering a call and negotiation.Operating Information: OMC-R System Administration Troubleshooting the modem Troubleshooting the modem ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Problem symptoms Solutions for the following problems are detailed in this section: • All ports busy.password failed. • Login message is corrupt. • Modifying eeprom settings. 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. • Cannot log in . 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. • Modems do not disconnect properly. • No login prompt. for that port. • Corruption from platform with remote system login. • No utmpx entry. • On dialing the platform. • Permission denied or link down. Continued 68P02901W19-S 3-19 Oct 2009 .

enter the following command at the # prompt for the appropriate device: fuser /dev/cua/a An example output is: /dev/cua/a: 652o 651o Based on the example output. If necessary. a getty process or a defunct tip/cu process. change the permissions and ownership of the modem port by entering. 5 Another process has the port open. If there is a lock file. ensuring that the correct device has been specified. the device will be left with an owner of the last cu user. 4 Check for a lock file in /var/spool/locks. LK. NOTE If cu is abruptly terminated. 2 Check that the details have been entered correctly in /etc/remote. This occurs because the driver is waiting at an unlinkable level for the device to respond. If the process is defunct it cannot be terminated and a reboot will be necessary.032. enter the following command: ps -ef | grep tip As root.001. for example. At the # prompt.All ports busy Chapter 3: Ancillary Devices 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 Enter the following command: tip -<9600> /dev/cua/a replacing <9600> with the appropriate connection speed for the device.028. 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. Use the ps command to determine if the process is still active. for example. If the message All ports busy is displayed. then cat the file. This could be another tip session. The number displayed is the Process ID (PID). 3 There could be a permissions problem on the device. Remove the lock file. enter the following commands: ps -ef | grep 652 ps -ef | grep 651 Continued 3-20 68P02901W19-S Oct 2009 . terminate the process.

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.58 is the child process for term/b. kill the process using the Serial port manager. REMOVE the device (do not leave a dangling cable. The command to remove the service is: pmadm -r -p zsmon -s <SVCTAG> (use pmadm -l to determine SVCTAG). Select the port from the Edit menu and delete the port service. 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 An example output is: 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 .Operating Information: OMC-R System Administration Procedure 3-8 No login prompt Modem troubleshooting: all ports busy (Continued) The PIDs are 652 and 651. the modem is active or the modem is asserting Data Carrier Detect (DCD) all the time. (The modem is no longer configured for dial-in). Refer to the modem documentation for further details. Configure the modem so that the DCD is asserted only when a carrier is detected from the remote modem. PID of 172. If the process using the port is /usr/bin/login or ttymon. 7 Bring the system down and then back to multi-user mode. 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 An example output is: 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. 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. 6 If the process is ttymon. then somebody has dialed the machine.

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. If one modem cannot manage to connect to the other modem. NOTE The modem must be able to lock the modem speed and match the port monitor speed configured using the Serial Port Manager.tvi925 n #modem -Bidirectional 4 Check and verify that the port monitor services baud rate matches the modem baud rate. the modem hangs up. 5 Use the tip utility and connect back to the modem. 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 An example output is: zsmon ttymon ttya u root /dev/term/a . ttcompat login: . and verify the modem configuration. Use the following procedure to correct this problem: Procedure 3-10 Modem troubleshooting: corruption from platform 1 Check the modem speed and make certain that it matches the speed of the platform.9600 ldterm. When to modify the eeprom settings Do not change the eeproms unless trying to get a terminal working at boot prom level.- /usr/bin/login .When to modify the eeprom settings Procedure 3-9 3 Chapter 3: Ancillary Devices Modem troubleshooting: no login prompt (Continued) If the ttymon process TTY has not changed to term/b. 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. 3-22 68P02901W19-S Oct 2009 . Check the settings of both modems. 2 Connect the modem using tip.

* and remove that file. FollowProcedure 3-13 to correct this problem: Procedure 3-13 68P02901W19-S Modem troubleshooting: modem not answering 1 Check if the modem is set up for auto answer (*AA2) for Motorola Modems or ATS0=2 for MultiModem. 3 Check the permissions and ownership on the serial device (/dev/cua/a or /dev/cua/b). The modem must be configured so that the Data Carrier Detect (DCD) is asserted only when a carrier is detected from the remote modem. 2 Check if the proper port is being used. 3-23 Oct 2009 . NOT in a command tool. Modems do not disconnect properly The modem does not disconnect properly or a user stays logged in even after disconnecting. use the following procedure to correct this problem: Procedure 3-12 Modem troubleshooting: no response to tip 1 Check the cabling to the modem. 3 Ensure that tip is being used in a shell tool.Operating Information: OMC-R System Administration 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. The modem is not configured correctly. Nothing happens when trying to tip the modem If this situation occurs. When dialing into the SPARC the modem never answers the phone This situation indicates that the modem is not configured correctly. Procedure 3-11 Modem troubleshooting: permission denied or link down 1 Ensure that dv=/dev/cua/a or dv=/dev/cua/b are present in the hardwire entry of the /etc/remote file. 2 Ensure that the Data Terminal Ready (DTR) light is lit on the modem which indicates that the DTR is asserted from the platform. 2 Check in /var/spool/locks for a lock file LCK. Refer to the modem documentation for further details.

but it does if LF or CTRL-J is pressed. Cannot login. 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. password fails This situation indicates a parity problem. If this situation occurs then reconfigure the remote computers serial port setup for eight data bits. one stop bit and no parity.Login message is corrupt Chapter 3: Ancillary Devices Login message is corrupt The login message is corrupt and nothing happens when RETURN is pressed. 3-24 68P02901W19-S Oct 2009 .

Operating Information: OMC-R System Administration

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

1

Print a page to verify the printer settings.

2

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.

3

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

Chapter 3: Ancillary Devices

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

Operating Information: OMC-R System Administration

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

Chapter 3: Ancillary Devices

68P02901W19-S
Oct 2009

Chapter

4
OMC-R Log Files

68P02901W19-S
Oct 2009

4-1

Overview

Chapter 4: OMC-R Log Files

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.
The following topics are described in this chapter:

4-2

OMC-R log and error files on page 4-3.

Checking audit log files on page 4-11.

68P02901W19-S
Oct 2009

Operating Information: OMC-R System Administration

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

Chapter 4: OMC-R Log Files

OMC-R Log files on the system processor

68P02901W19-S
Oct 2009

Operating Information: OMC-R System Administration

OMC-R log files on the GUI server

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

OMC-R log files on the GUI server

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

Chapter 4: OMC-R Log Files

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

Operating Information: OMC-R System Administration

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:

2

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:
As user omcadmin execute the following commands:
cd $OMC_TOP/logs/bss
tail -50 bssname_yyyymmdd
This allows you to see all command line activities performed on a
particular BSS.

3

Check the Configuration Management log file:
As user omcadmin execute the following commands:
cd $OMC_TOP/logs
tail -50 cm_omcaudit_yyyymmdd
Configuration Management activities are logged to this file.
Continued

68P02901W19-S

4-7
Oct 2009

Checking OMC-R log files

Chapter 4: OMC-R Log Files

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:
As user omcadmin execute the following commands:
cd $OMC_TOP/logs
more cutover.nnnn
This log file says whether the cutover has been successful.

5

If problems are experienced adding or updating statistics in the PM
database then check for the existence of dbms log files:
As user omcadmin execute the following commands:
cd $OMC_TOP/logs
more dbms.nnnn
This dbms log file contains error information.

6

Check the fpomcaudityyyymmdd log file for successful statistic parsing.
As user omcadmin execute the following command:
tail -f $SYS_LOG/fpomcaudityyyymmdd

7

If problems occur with Interprocess communication then check if an
IPC log file exists in /usr/omc/logs/ipc directory.
As user omcadmin execute the following commands:
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.

8

Check the omc_db_maint log file to ensure that:

PM statistics are unloaded and deleted successfully.

PM fragments are created for parsing the next days statistics.

Applications are connected and reconnected successfully when
required.

As user root execute the following commands:
cd $OMC_TOP/logs
more omc_db_maint.yyyy.mm.dd
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.
As user omcadmin execute the following commands:
cd $OMC_TOP/logs/usrauditlogs
tail -50 pmguiaudityyyymmdd
Continued

4-8

68P02901W19-S
Oct 2009

As user omcadmin monitor the output of the maintain_script cron job to ensure that it deletes log files on a regular basis. As user omcadmin execute the following commands: For the PM DB: cd /usr/informix more online.ddmmyyyy For the CM DB: cd /usr/informix more online.log_OMC.Operating Information: OMC-R System Administration Procedure 4-1 11 Checking OMC-R log files Checking the OMC-R log files (Continued) Check the Informix online logs for DB errors relating to the PM and CM databases. As user omcadmin execute the following commands: cd $OMC_TOP/logs /usrauditlogs/ tail -50 usraudityyyymmdd Continued 68P02901W19-S 4-9 Oct 2009 . As user omcadmin execute the following commands: 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. cd /var/mail more omcadmin | grep maintain_script 14 Check the usraudit log file for errors relating to the GUI.log_MIB. 13 Monitor the disk space used by the various log files.ddmmyyyy 12 Check the omcaudit log for messages relating to OMC-R activity.

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. As user omcadmin. Service error code: 0 Error Level: 4 To confirm whether it is for redundant upload request or not.Checking OMC-R log files Chapter 4: OMC-R Log Files Procedure 4-1 15 Checking the OMC-R log files (Continued) Check the fcaudit log file for errors relating to the event logs. 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. 4-10 68P02901W19-S Oct 2009 .

Use different methods for checking audit log files in a: • Single OMC-R environment. Checking audit log files in a single OMC-R environment In a single OMC-R environment.Operating Information: OMC-R System Administration 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. • Multiple OMC-R environment. 4-11 Oct 2009 . 501 The line has failed to apply. 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. Table 4-1 68P02901W19-S Audit apply result codes Code Meaning 500 The line has not been applied to the MIB database. as shown in Table 4-1. 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. especially in an environment where the system administrator cannot afford to run multiple GUIs. The aurecordtable9 contains a status column. 502 The row has been successfully applied to the MIB database. which displays a code indicating the result of the audit apply. Checking audit log files in a multiple OMC-R environment In a multiple OMC-R environment.

oidinstleft group by 1.logoidinstrite = l. 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 .logoidinstleft = l.oidclass and r.logoidtomid = l.logoidtomid = l. 3 Enter the following SQL statements in Audit_apply_check. if an audit is taking a long time to complete): Procedure 4-2 Checking the current state of audits 1 Login as omcadmin on the system processor. select l.oidinstrite and r.logoidinstleft = l.logoidinstrite = l.oidtomid and r.oidinstleft group by 1.oidclass and r. select l.Checking audit log files in a multiple OMC-R environment Chapter 4: OMC-R Log Files Checking the current state of audits Use the following procedure to see the current state of audits (for example. 4 Enter the following: mib_env isql mib_db <Audit_apply_check.oidclass and r. aurecordtable9 r where r.logoidtomid = l.oidinstrite and r. aurecordtable9 r where r.logoidclass = l.status = 502 and r.oidtomid and r.out 5 Open the Audit_apply_check. aurecordtable9 r where r.status = 501 and r.oidtomid and r. select l.status = 500 and r.logoidinstleft = l. 2 Create a new file (using the vi editor for example) called Audit_apply_check.count(*) not_appl from aulogtable9 l.logoidclass = l.count(*) failed from aulogtable9 l.sql.rootname audit.sql >Audit_apply_check.count(*) applied from aulogtable9 l.logoidclass = l.rootname audit.sql: set isolation to dirty read.out file.logoidinstrite = l.rootname audit.oidinstleft group by 1.oidinstrite and r.

NOTE It is possible for an audit to fail with some lines still with the not_appl state. 68P02901W19-S Oct 2009 4-13 . repeat step 4 and step 5 several times. This is because the lines relied on previous lines which did not apply successfully.Operating Information: OMC-R System Administration Procedure 4-2 6 Checking audit log files in a multiple OMC-R environment Checking the current state of audits (Continued) To see if the not_appl value is decreasing.

Checking audit log files in a multiple OMC-R environment 4-14 Chapter 4: OMC-R Log Files 68P02901W19-S Oct 2009 .

Chapter 5 OMC-R Cron Jobs ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 68P02901W19-S Oct 2009 5-1 .

68P02901W19-S Oct 2009 .Overview Chapter 5: OMC-R Cron Jobs Overview ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ These are installed to perform various maintenance tasks for both system and GUI processors. This is installed in the directory $OMC_TOP/current/install_splat. These scripts are designed to work on a specific area of the logs. • Scheduling cron jobs using the batch scheduler on page 5-9. The following topics are described in this chapter: 5-2 • System cron jobs on page 5-3. Several log maintenance scripts are available to maintain the log files on the different processors. NOTE Most of these scripts need omcadmin as login id. • Checking cron jobs on page 5-18. A recommended cron script exists for each processor. All of these scripts can be executed from the command line or through cron. • Scheduling cron jobs from the command line on page 5-14.

68P02901W19-S 5-3 Oct 2009 .Operating Information: OMC-R System Administration 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.

the omcadmin file in the /var/mail directory should be checked for error messages. the sys file in the /var/mail directory should be checked for error messages.sh • checkValidlockPID NOTE To check the output of the omcadmin cron jobs.sh • maintain_ct.cron jobs on the system processor Chapter 5: OMC-R Cron Jobs 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. sys cron jobs The following system cron jobs are executed on the system processor: • sa1 • sa2 These cron jobs are used for performance collection. 5-4 68P02901W19-S Oct 2009 . NOTE To check the output of the sys cron jobs.

the root 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.Operating Information: OMC-R System Administration 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 omcadmin file in the /var/mail directory should be checked for error messages. NOTE To check the output of the sys cron jobs. 68P02901W19-S 5-5 Oct 2009 . omcadmin cron jobs The following omcadmin cron jobs can be run on the system processor: • maintain_script. NOTE To check the output of the omcadmin cron jobs. • checkValidLockPID. the sys file in the /var/mail directory should be checked for error messages.

-d <days> the age of the files to be selected (default value is one day). NOTE Only one of the options shown within the chevrons (l. archive. r. -c to clear the database log file. A separate invocation is needed every time to list. -a the mode which archives selected files to tape using the UNIX command cpio. <directory> the system directory.Recommended cron jobs Chapter 5: OMC-R Cron Jobs Recommended cron jobs maintain_script (root or omcadmin) This script will list. or remove maintenance log files. a. archive. /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. -r the mode which removes selected files from the system. for example. and clear files of a specified age from a specified directory. -t <device> the tape device for archiving the files (default value is dev/rmt/0 on the system processor). or c) can be selected at one time. remove. 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 . omcaudit\*. <filename> the file to be removed.

log sar_per_day (root) This script generates a system activity report data file. /usr/omc/current/sbin/update_mib_statistics roll_paging_log (omcadmin) This script performs a daily rollover of the PagingLog file. /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/current/sbin/core_presence 68P02901W19-S 5-7 Oct 2009 . /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_ct_logs roll_online. /usr/omc/sbin/roll_online. /usr/omc/current/sbin/sar_per_day update_mib_statistics (omcadmin) This script updates statistics for all tables in the CM database.log (root) This script performs a rollover of the online. /usr/omc/sbin/roll_paging_log core_presence (omcadmin) This script notifies user omcadmin of any core files.log file.Operating Information: OMC-R System Administration Recommended cron jobs onmode_mib (root) This script frees up memory segments for CM database.

then updates sites according to the NE map. /usr/omc/current/sbin/site_timesynch [passwd 1] [passwd 2]. $OMC_TOP/current/sbin/omc_db_maint site_timesynch (omcadmin) This script gets the date on the system processor. /usr/omc/current/sbin/timesynch bss_dt_load. /usr/omc/current/sbin/bss_dt_load. /usr/omc/sbin/monitor_log app_vrt_display (root) This script ensures that applix virtual display is running. <passwd 2>. /usr/omc/current/sbin/app_vrt_display omc_db_maint (root) This script performs PM database maintenance. checkValidLockPID (omcadmin) This script removes any invalid lock files..sh (omcadmin) This script loads default date times into BSS datetimes. [passwd n] Where <passwd 1>.sh (omcadmin) This script deletes call trace logs.sh maintain_ct.Recommended cron jobs Chapter 5: OMC-R Cron Jobs monitor_log (root) This script monitors the OMC and the system processor for performance. /usr/omc/current/sbin 5-8 68P02901W19-S Oct 2009 . 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.

4 To clear the details. Minute. A window show in Figure 5-1 is displayed. 2 To display details of the cron job that is currently running. click Get active crontab. simply click the cron job in the list. The details are displayed. as shown in Figure 5-2.Operating Information: OMC-R System Administration 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. 5-9 Oct 2009 . Day of month. 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. Month. 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 1 To activate the cron scheduler click the CRON icon on the CDE desktop environment. click Clear gadgets. 3 To display details of any listed cron job. for example. A list of scheduled cron jobs is displayed in the top half of the window. Day of week and the cron command. These include Hour. removed or modified. These cron jobs can be added to.

Displaying cron jobs Figure 5-1 5-10 Chapter 5: OMC-R Cron Jobs Batch scheduler main window 68P02901W19-S Oct 2009 .

Operating Information: OMC-R System Administration Figure 5-2 68P02901W19-S Displaying cron jobs Batch scheduler main window: selected cron job 5-11 Oct 2009 .

Day of month. Day of week and the cron job command. 4 Click Install to set the new cron job to run on the system or GUI processor. 68P02901W19-S Oct 2009 . 5 Click Install to set the modified schedule 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. 4 Click OK to replace the pre-existing schedule with the modified cron job schedule. 2 Modify the variables as required. 5-12 2 Modify the variables as required. Its details are displayed. The Modify command button is enabled. for example. Minute. for example. as shown in Figure 5-2. A Notify message box is displayed as shown in Figure 5-3. Its details are displayed.Adding a new cron job Chapter 5: OMC-R Cron Jobs Adding a new cron job Use the following procedure to add a new cron job using the batch scheduler: Procedure 5-2 1 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. 3 Click Add. Month. as shown in Figure 5-2. 3 Click Modify. These include Hour.

A Notify message box is displayed as shown in Figure 5-3. 4 Click Install to set the modified crontab to run on the system or GUI processor. Its details are displayed.Operating Information: OMC-R System Administration 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 1 From the Batch scheduler main window (Figure 5-1) highlight the cron job. 5-13 Oct 2009 . 3 Click OK to remove the cron job. 2 Click Remove.

To check the results of jobs run using cron. • Removing cron jobs. • Adding cron jobs. • Cron maintenance procedure. The mail file for the user is located in /var/mail. 5-14 68P02901W19-S Oct 2009 .Scheduling cron jobs from the command line Chapter 5: OMC-R Cron Jobs 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. execute the following command: crontab -l NOTE To view a user's crontab file. • Printing crontab files. • Checking cron jobs. Viewing crontab files To view a user's existing crontab. This file can be viewed to check the output from the cron job. login to the relevant processor and using the mail tool check that all cron jobs have run successfully. 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. The user is informed through mail regarding unsuccessful cron jobs. root and omcadmin). it is necessary for the user to log in.

rm /tmp/cron_list. 3 Re-submit the edited temporary file to cron for execution using crontab as follows: crontab /tmp/cron_list. The first five fields are the integer patterns that specify the following: • Minutes (0-59). For example.tmp 2 Add the new job (comment and activation line) to the temporary file. • A hardcopy printout of the cron jobs running on the system should be kept safe.tmp 4 Enter the following command to remove the temporary file. at 15 minutes past midnight. • Hour (0-23). # 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. 0 denotes Sunday. Procedure 5-5 Adding cron jobs: example 1 List the cron jobs currently running to a temporary file as follows: crontab -l > /tmp/cron_list. NOTE To add commands to a user's crontab. 5-15 Oct 2009 . which are more than seven days old from the system. it is necessary for the user to log in. • Day of the week (0-6).Operating Information: OMC-R System Administration Adding cron jobs Adding cron jobs Use the following example procedure to add a new job that removes all database files. This may be used for reference during system troubleshooting.tmp NOTE 68P02901W19-S • It is not recommended to set up cron jobs that archive files to tape. • Day of the month (1-31). • Month of the year (1-12). For example.

it is necessary for the user to log in.tmp 2 Delete the required activation line and relevant comment lines from the temporary file.Removing cron jobs Chapter 5: OMC-R 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. Procedure 5-6 Deleting cron jobs: example 1 List the cron jobs currently running to a temporary file by entering: crontab -l > /tmp/cron_list. Use the following procedure regularly to avoid a cron log file becoming too large. 68P02901W19-S Oct 2009 . which must be regularly maintained. Procedure 5-7 5-16 cron maintenance procedure 1 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.tmp cron maintenance procedure Log files of cron jobs are produced. 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 3 Resubmit the edited temporary file to cron for execution by entering: crontab /tmp/cron_list.tmp 4 To remove the temporary file enter: rm /tmp/cron_list. 2 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.

5-17 Oct 2009 . a printout of it should be made. Several different crontab files may exist: each of the users.Operating Information: OMC-R System Administration Printing crontab files Printing crontab files Each time a crontab file is modified. 2 Enter the command: mv /tmp/cron_log /var/cron/log 3 Obtain a printout of files by entering: /usr/ucb/lpr <filename> Where <filename> is the name of the crontab file to be printed. 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 Printing crontab files 1 Login to the processor where the crontab file has been set up using the relevant login id.

As user sys execute the following command: crontab -l 8 Check the /var/cron/log file to ensure that all crons executed are logged to this file. then it should be changed. Procedure 5-9 Checking cron jobs 1 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. Copy the checklist in Table 14-4 to record the checks. As user root execute the following command: more /etc/default/cron | grep CRONLOG 4 If the CRONLOG variable is set to NO. Save the file. As user root execute the following command: more /var/cron/log 9 Check that the /var/cron/log file is rolled over to avoid disk space issues. As user omcadmin execute the following command: crontab -l 7 Check that the system cronjobs are set up correctly. As user root execute the following command: cd /var/cron ls -l Continued 5-18 68P02901W19-S Oct 2009 . As user root edit the /etc/default/cron file and change the CRONLOG setting to YES. As user root execute the following command: crontab -l 6 Check that the cron jobs are set up correctly for user omcadmin.d/FIFO /usr/sbin/cron 3 Check that the CRONLOG variable has been set to YES to ensure that cron logging is done. 5 Check that the cron jobs are set up correctly for user root. As user root execute the following commands: rm -f /etc/cron. 2 Start the cron daemon if it is not running.Checking cron jobs Chapter 5: OMC-R Cron Jobs Checking cron jobs ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Checklist for cron jobs Use the following procedure to check cron jobs.

11 Check the output of root cron jobs for any errors. 5-19 . 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.<ddmmyyyy>where <ddmmyyyy> is the date of the log.Operating Information: OMC-R System Administration Procedure 5-9 68P02901W19-S Oct 2009 Checklist for cron jobs Checking cron jobs (Continued) 10 Log files should exist in the format log. 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 root execute the following commands: cd /var/mail more root | grep <cronjobname> 12 Check the output of omcadmin cron jobs for any errors.

Checklist for cron jobs 5-20 Chapter 5: OMC-R Cron Jobs 68P02901W19-S Oct 2009 .

Chapter 6 OMC-R Environment variables ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 68P02901W19-S Oct 2009 6-1 .

Overview Chapter 6: OMC-R Environment variables Overview ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ The following topics are described in this chapter: 6-2 • Customizing the OMC-R user environment on page 6-3. 68P02901W19-S Oct 2009 . • Setting the time for the OMC-R and NEs on page 6-36. • Setting the status of the Consolidated Alarms on page 6-29. • User configurable environment variables on page 6-5. • Non user configurable environment variables on page 6-31. • Changing an environment variable on page 6-26.

Operating Information: OMC-R System Administration 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.private file If the .cshrc. NOTE There is a separate /usr/omc/current/env directory on each processor. the new environment variable definition may not become current until the user logs in again. a mapping between function keys and strings must be set up in this file.private file is an X resource file which is used to set up function keys.private file exists.private) located in the user's home directory. In particular.cshrc. the string is printed in the X-Term window. Individual users can program function keys by placing a translation table in their . NOTE When an environment variable is redefined. A function key can be associated with a string. and whenever the user runs a C shell.Xdefaults.private file is used to specify user-specific values for the environment variables. When the key is pressed and an X-Term window is displayed.xxxx files. The association between the function key and the string is specified in a translation table in an X resources file. it is done using the user's xxxx. which are used by all OMC users.Xdefaults. The . it is done in the $OMC_TOP/current/env/.cshrc. it is executed when a user logs in.private file for a user.Xdefaults. If all the environments of OMC-R users need to be customized.private file.private files (for example. 68P02901W19-S 6-3 Oct 2009 . . cshrc. NOTE Only the OMC-R system administrator can customize the . . Many X attributes for personal display can be customized by specifying them in this file.private file The .Xdefaults.

all existing translations are deleted.Xdefaults. and typically the operator finishes off the command and then presses RETURN. If an argument for the string begins with 0x the argument is taken as a hexadecimal number. 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. The user. In the previous example. • When the F2 key is pressed.XTerm*VT100. 6-4 68P02901W19-S Oct 2009 . The argument 0xd inserts the ASCII carriage return character.. the string disp_equip 0 is printed on the screen followed by a carriage return.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. when programming function keys. the string disp_dev_s is printed on the screen.private file Chapter 6: OMC-R Environment variables Example The format of the translation table is shown in the following example: . and the corresponding ASCII character is inserted. the translation table specifies that for all X-Terms of type VT100. The keyword override is important because without it. only wants to change certain translations. A carriage return is not sent. 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.

used by the system processes interacting with the PM database.csh file. • /usr/omc/current/config/env/mibProcConfig. To set a non-default value for any of these variables. which are automatically updated if any changes are made in the .csh Defines the variables used by the system processors. There are . 68P02901W19-S 6-5 Oct 2009 . • /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 default values of these environment variables are defined in the /usr/omc/current/config/env/pmProcConfig. make the change in the /usr/omc/config/global/env/pmProcConfig.csh Defines the variables used by the MIB processes.sh versions of these files (Bourne Shells). cannot be modified. these are sourced as a secondary set of values. System processes and PM database configurable variables This section lists the user configurable environment variables.csh versions. Where values are set in the /usr/omc/config/global/env location.Operating Information: OMC-R System Administration 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.csh Defines the variables used by the GUI processes which interact with the GUI server or clients. the set of values in the /usr/omc/current/config/env location are initially sourced. • /usr/omc/current/config/env/mmiProcConfig. which interact with the PM database. are defined in the following files: • /usr/omc/current/config/env/pmProcConfig. for the OMC-R applications. The User configurable environment variables.csh file. which interact with the MIB database.

the value is 0). The maximum value that this environment variable is set to is 12 and the minimum is 4. COUNTRY_CODE The COUNTRY_CODE environment variable defined by the GSM operator license. The default value for this environment variable is OFF. The default value for the environment variable is 0. this can slow down the startup process. If it is set to ON. and for Mid-end or High-end systems the default is 12. starting with cells that have the oldest date for last enabled neighbor statistics (see Using neighbor statistics on page 13-91). is set to /usr/informix. • If the environment variable is not set (that is. The feature enables neighbor statistics for cells in rotation. ENABLE_CYCLIC_NBRS The ENABLE_CYCLIC_NBRS when set to ON activates the Cyclic Neighbors Feature. • If set to 1. 6-6 68P02901W19-S Oct 2009 . It is used in conjunction with MAX_CSFP_BLP. it allows the upload session even though the Rlogin session is active. the environment variable aborts the upload request if the Rlogin session is active. INFORMIXSERVER The INFORMIXSERVER environment variable is used to identify the server name of the PM Informix Server instance and by default. However. MAX_BOOTLOADS This environment variable is set to limit the maximum download capacity. For Low-end systems the default is 6. is set to omc_sys. AUTOSTART_PMGUI The AUTOSTART_PMGUI when set to OFF. A value of 8 is used by the system processes if the environment variable is not set or has exceeded permitted range. the PMGUI will start automatically in the background as the GUI starts.System processes and PM database configurable variables Chapter 6: OMC-R Environment variables ABORT_UPL_RL_IN_PROG The environment variable ABORT_UPL_RL_IN_PROG aborts the upload request when the Rlogin session is active. 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.

NO_OF_PARSERS NO_OF_PARSES is by default set to integer size. To increase the allowed number of CSFP downloads to a higher fraction of the total allowed downloads. This variable defines the number of parser processes that can run simultaneously. it is reset to one less than the value of the MAX_BOOTLOADS variable. If the defaults are maintained. MMI_CLEAR_INACTIVE_FMIC The MMI_CLEAR_INACTIVE_FMIC environment variable is set to TRUE for all users. this variable has a default setting of 3. This prevents all the download capacity from being used by the CSFP downloads. It is set on to enable all users to clear inactive FMIC alarms from the system. set MAX_CSFP_BLP to a higher value.Operating Information: OMC-R System Administration System processes and PM database configurable variables 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. MMI_ENABLE_FMIC The MMI_ENABLE_FMIC environment variable is set to 1 to ensure that FMIC is enabled on the MMI. this variable has a default setting of 6. ensuring spare capacity for a conventional download in the event of an NE losing power momentarily. 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. For a High-end and Mid-end system. This environment variable is always set to 1.1. For a Low-end system. or some other transient fault. 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. If MAX_CSFP_BLP is set to a value outside this permitted range. It has a range of 0 or 1. 68P02901W19-S 6-7 Oct 2009 . For a Low-end system. or the variable is not set. A default value of 4 is used if the environment variable is not set or an invalid value is specified. NETWORK_CODE The NETWORK CODE environment variable is defined by the GSM operator license. The permitted range of values is between 1 and MAX_BOOTLOADS . the OMC-R limits the number of CSFP downloads to one half of the maximum allowable number of downloads.

by default. • On a Mid-capacity or High-end system.System processes and PM database configurable variables Chapter 6: OMC-R Environment variables OMC_TOP The OMC_TOP environment variable is used by the OMC-R software is. the statistics sampling interval (30 minutes or 1 hour). the parser processes statistics for a maximum of 92160 neighbors per network in a 30 minute interval. When the table is 100 percent full. It determines the interval at which the OMC-R receives BSS the statistical files. is set to /usr/omc.CNFG file and the /usr/omc/config/global/pmProcConfig. In this case PM_MAX_NEIGHBORS can be increased to 4000. alarm 30026 is raised. The possible settings are: • ON sets the interval to 1 hour. nbr_statistics. The maximum number of cells with neighbor statistics enabled varies with the type of system: • On a Low-end system.csh: setenv PM_HOURLY_STATS ON An OMC stop/start is required.csh file. The size of the PM database neighbor statistic table. this table starts to fill up. and the number of days for which the statistics are kept. the parser processes statistics for a maximum of 4000 neighbors per network in a 30 minute interval. no further neighbor statistics are parsed. 6-8 68P02901W19-S Oct 2009 . is defined as: PM_MAX_NEIGHBORS*48*7 Where is 48 7 the number of intervals in a day. PM_MAX_NEIGHBORS The PM_MAX_NEIGHBORS variable defines the maximum number of cells in the network that can have neighbor statistics enabled. PM_HOURLY_STATS The PM_HOURLY_STATS variable is defined in the /usr/omc/config/global/OMC. the number of days storage. Factors to take into account are: the number of cells for which neighbor statistics are enabled. Refer to Using neighbor statistics on page 13-91 for additional checks and procedures that must be performed when modifying the PM_MAX_NEIGHBORS. If too many cells have the neighbor statistics enabled. For a permanent change add the following statement to the file /usr/omc/config/global/pmProcConfig. The number of enabled neighbor statistics should be adjusted to ensure that the table does not become 100 percent full. In this case PM_MAX_NEIGHBORS can be increased to 92160. • Any other value sets the interval to 30 minutes. When nbr_statistics is 70 percent full.

Case 2: 145|CFG_KEEP_NMC_FILE|1 Result: This will keep the NMC file without deleting.csh and pmProcConfig. Usage of this flag Flag CFG_KEEP_NMC_FILE Case:1 145|CFG_KEEP_NMC_FILE|0 Result: This NMC file is deleted. When this variable is set to 1.Operating Information: OMC-R System Administration System processes and PM database configurable variables CFG_KEEP_STATS_FILE This variable is defined in /usr/gsm/current/config/pmloader. 145|CFG_KEEP_STAT_FILE|1 Result: This will keep the Parsed file (bin file) and append parsed to the parsed file. The variable STATE_ON_AUDIT should be set to the same value in both the mibProcConfig. 68P02901W19-S 6-9 Oct 2009 . CFG_KEEP_NMC_FILE This variable is defined in /usr/gsm/current/config/pmloader. this variable is set to 62 seconds. By default. waits for a reply from the event manager. the OMC-R performs a state resynchronization when an audit is completed.cfg. 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. STATE_ON_AUDIT The STATE_ON_AUDIT environment variable ensures that the device statistics on the MIB are updated correctly after an audit. SUB_RES_TIME The SUB_RES_TIME variable defines the length of time the pm_main.cfg.csh files.

To set a non-default value for any of these variables. the delay will automatically reset to 0 minutes.csh file. The default values of these environment variables are defined in the /usr/omc/current/config/env/mibProcConfig. The default value for the UPL_KEEP_STATS_FILE variable is OFF. then ATC_TIMEOUT needs to be modified. If ATC_TIMEOUT is not set.MIB processes used by environment variables Chapter 6: OMC-R 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.debugcompressfile extension. It is not recommended to change this environment variable. modify the /usr/omc/config/global/env/mibProcConfig. modify the /usr/omc/config/global/env/mibProcConfig. and then terminates.csh file.csh file. To set a non-default value for any of these variables. ATC_TIMEOUT The ATC_TIMEOUT environment variable is set in the /usr/omc/current/config/env/mibProcConfig. If this time exceeds. if the Resync on startup flag is enabled in the Network detailed view. the CM database retries the propagation for the length of time specified by ATC_TIMEOUT. The value of ATC_TIMEOUT is specified in tenths of a second.0/RXCDR with a . The delay allows the connections to NEs to be re-established after an OMC stop/start. AU_APPLY_DELETES_FIRST The AU_APPLY_DELETES_FIRST variable is set to ON by default. the CM database propagates this change to all the neighbors pointing to that cell. MIB processes used by environment variables This section lists the user configurable environment variables. the propagation fails for this neighbor. This time lapse or delay is measured in minutes. and the maximum value is 10. 6-10 68P02901W19-S Oct 2009 . The default value is 1200. If any of the neighbors are in edit. If the user sets a value more then 10 minutes. the system continues until each failed update has been retried once. When a change is made to an attribute of a cell. These compressed statistics files can be found in directories /usr/omc/ne_data/raw_stats/100. The default value for the AUTORESYNCDELAY variable is 0. AUTORESYNCDELAY The AUTORESYNCDELAY environment variable is introduced to define the time required to start the Network Resync on startup.0/BSS or /usr/omc/ne_data/raw_stats/100.csh file. If there are a large number of neighbors. This allows the audit process to apply all delete actions before attempting create and update. used by the MIB processes interacting with the MIB database. RTFs or DRIs. The ATC_TIMEOUT environment variable is related to the neighbor propagation feature.

which are over 30 days old. To switch the H2_DUALBAND flag ON. 68P02901W19-S 6-11 Oct 2009 . DEL_CELLX_FILES The DEL_CELLX_FILES is used to set up the automatic deletion of CellXchange backup files.sh When the DEL_CELLX_FILES variable is set to ON. are deleted. CT_1208LOG The CT_1208LOG variable is default set to $OMC_TOP/ne_data/ct_logs.Operating Information: OMC-R System Administration MIB processes used by environment variables 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. set to /usr/informix. H2_DUALBAND The H2_DUALBAND flag switches on MIB support for the Dual BAND Horizon II feature. which are stored in the directory /usr/omc/config/global/cellX.csh /usr/omc/config/global/env/Common.csh This requires an OMC stop/start. This environment variable specifies the location where the call trace logs are saved. change the H2_DUALBAND environment variable from OFF to ON in the following files: • /usr/omc/current/config/Common. By default the DEL_CELLX_FILES variable is set to OFF. change DEL_CELLX_FILES from OFF to ON in both of the following files: /usr/omc/config/global/env/Common.BACKUP extension in the directory /usr/omc/config/global/cellX. This is the name of the CM database. By default it is switched OFF. This variable is by default. INFORMIXDIR The INFORMIX environment variable defines where the Informix software is installed on the system. any files with the .sh • /usr/omc/current/config/Common. To switch on the auto-deletion of backup files. DBNAME The DBNAME variable is default set to mib_db.

The PER_SITE_AUDIT environment variable default value is set in the /usr/omc/current/config/env/Common.csh file. PER_SITE_AUDIT_DEBUG The PER_SITE_AUDIT_DEBUG flag switches on debugging for the Per Site Audit feature.sh file as follows: NX_ENABLE_TIMESLOTS=1 export NX_ENABLE_TIMESLOTS 4 Update the Common.csh file. 2 Enter the following command: cd /usr/omc/config/global/env 3 Update the Common. is set to /usr/omc. 2 Enter the following command: cd /usr/omc/config/global/env Continued 6-12 68P02901W19-S Oct 2009 . Use the following procedure to enable the Upstream and Downstream TS MMS options: Procedure 6-1 Enabling the Upstream and Downstream TS MMS options 1 Log on as omcadmin. PER_SITE_AUDIT The PER_SITE_AUDIT flag switches on MIB support for the Per Site Audit feature. OMC_TOP The OMC_TOP environment variable is used by the OMC-R software and. extra messages are output to the /usr/omc/logs/omcaudit<date> file during a Per Site Audit. If this flag is enabled. It requires an OMC stop or start. the NX_ENABLE_TIMESLOTS environment variable must be set.csh file as follows: setenv NX_ENABLE_TIMESLOTS 1 5 Stop and start the OMC. Use the following procedure to enable PER_SITE_AUDIT_DEBUG: Procedure 6-2 Enabling PER_SITE_AUDIT_DEBUG 1 Log on as omcadmin. modify the /usr/omc/config/global/env/Common. by default. To enable the Upstream and Downstream TS MMS options. To set a non-default value for any of these variables.MIB processes used by environment variables Chapter 6: OMC-R Environment variables 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.

This RECIPROCATE_NBR default set to TRUE. 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. set the USE_LONG_SITE_NAME variable to ON to launch the OMC GUI. the operator is able to create a SITE name of maximum 41 characters else it restricts to 31 characters. These environment variables are defined in the /usr/omc/config/global/mmiProcConfig. USE_LONG_SITE_NAME When the variable USE_LONG_SITE_NAME is set to ON. GUI processes environment variables This section lists the user configurable GUI processes environment variables. 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.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.sh file as follows: PER_SITE_AUDIT_DEBUG=ON export PER_SITE_AUDIT_DEBUG 4 Update the Common.csh file. The ADDINFO_IN_HEX variable has a default value of 1 and a valid range of 0 or 1.Operating Information: OMC-R System Administration Procedure 6-2 GUI processes environment variables Enabling PER_SITE_AUDIT_DEBUG (Continued) 3 Update the Common. For example. set this variable to 0.csh file. If the OMC already has a SITE name with a maximum of 31 characters. when CELL B is defined as the Neighbor of CELL A. 68P02901W19-S 6-13 Oct 2009 . To switch off the additional alarm information. 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. ADDINFO_IN_HEX This environmental variable is present in the /usr/omc/current/config/Common.

2 Enter the following command: cd /usr/omc/config/global/env 3 Update the file Common. a different valid RDN instance can still be chosen when creating a device. the Auto Populate Cell ID feature is enabled. The AUTO_GEN_RDN variable is set to 0 by default (disabled). if an RTF has already been created under an associated RTF Group. as it is unnecessary to enter details in the GSM Cell ID field for an RTF.csh as follows: setenv AUTO_GEN_RDN 1 5 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. • If this variable is set to 1. • If this variable is set to any other value.GUI processes environment variables Chapter 6: OMC-R Environment variables 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. the GSM Cell ID field is auto populated with the Cell ID that the RTF Group belongs to. It also helps to prevent devices from being created out of sequence. 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. other than the first radio equipped to that RTF Group. The AUTO_POP_CELLID variable is set to 0 by default (disabled). • If this variable is set to any other value. the Auto Generate RDN feature is disabled. 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. the Auto Populate Cell ID feature is disabled. 68P02901W19-S Oct 2009 . Use the following procedure to enable the AUTO_GEN_RDN variable: Procedure 6-3 Enabling AUTO_GEN_RDN 1 Login as omcadmin.sh as follows: AUTO_GEN_RDN=1 export AUTO_GEN_RDN 4 Update the file Common. Although the RDN instance is created automatically. This saves time. When enabled. the Auto Generate RDN feature is enabled. 6-14 • If this variable is set to 1.

BSS_NAMING This variable can be used to display BSS parameter names in the Detailed View.csh as follows: setenv AUTO_POP_CELLID 1 5 Stop and restart the OMC-R as described in Manual startup and shutdown of OMC-R software on page 7-12 in order to activate these changes.8. omc_db. otherwise they are displayed with OMC names. By default it is set to 0 (disabled). AUTOSTART_PMGUI This environment variable is associated with the PM GUI automatic start operation. COUNTRY_CODE The COUNTRY_CODE environmental variable is defined by the GSM operator license. AX_LANG This variable is used to override the language used in the ax_prof file. 2 Enter the following command: cd /usr/omc/current/config 3 Update the file Common. BSS_VER This variable defines the BSS software version for example.0.Operating Information: OMC-R System Administration GUI processes environment variables Use the following procedure to enable the AUTO_POP_CELLID: Procedure 6-4 Enabling AUTO_POP_CELLID 1 Log on as omcadmin. 68P02901W19-S 6-15 Oct 2009 .sh as follows: AUTO_POP_CELLID=1 export AUTO_POP_CELLID 4 Update the file Common. BSGSM 1. See also the LANGUAGE variable.0. DBNAME This variable defines the database name for example. If BSS_NAMING is set then the attributes are displayed with BSS names.

By default. DOUBLE_CLICK_NEXT The DOUBLE_CLICK_NEXT environment variable is associated with the Map Display. to reduce the amount of e-mail being generated when alarms are reassigned. it is set to /usr/informix. It enables or disables the automatic e-mail notification. 6-16 68P02901W19-S Oct 2009 . to remove a cleared alarm. DEFAULT_REMOVE_CLEARED_ALARM This environment variable is associated with the Automatic Clearing of the Alarms operation. 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.GUI processes environment variables Chapter 6: OMC-R Environment variables DEF_GSM_CELL_ID This environment variable is the default GSM Cell ID. LANGUAGE The LANGUAGE variable defines the language set used within the OMC-R. 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 is set to the $COUNTRY_CODE$NETWORK_CODE-0000-000 variable by default. in seconds. DEFAULT_REMOVE_CLEARED_ALARM_TIME This environment variable is associated with the Automatic Clearing of the Alarms operation. By default this variable is defined as FALSE (=0) (disabled). It enables or disables the removal of a cleared alarm. It sets the allowable interval.

It has a default value of 110. It has a default value of 180.Operating Information: OMC-R System Administration GUI processes environment variables MAXCHANGENOTIFYCALLS This environment variable is present in the /usr/omc/current/config/Common. To set a non-default value for this variable modify the /usr/omc/config/global/env/Common. It allows the OMC system administrator to specify the number of status queries processed by the GUI. MMI_ALARM_STATE_WIDTH The MMI_ALARM_STATE_WIDTH environment variable specifies the pixel width of the Alarm State field. 68P02901W19-S 6-17 Oct 2009 .csh file: setenv MAXCHANGENOTIFYCALLS <value>.csh file.csh. This environment variable is set to TRUE for all users to enable all users to clear inactive FMIC alarms from the system. 4 All GUIs should be restarted in order to activate MAXCHANGENOTIFYCALLS.csh file. 3 Add the following line at the end of the Common. MMI_EVENT_ID_WIDTH The MMI_EVENT_ID_WIDTH environment variable specifies the pixel width of the Event ID field. Use the following procedure to set the value of the environment variable MAXCHANGENOTIFYCALLS: Procedure 6-5 Setting the value of MAXCHANGENOTIFYCALLS 1 Login as user omcadmin on the single platform processor. It has a default value of 35. NOTE Motorola does not recommend modification of this variable from its default value. 2 Locate the file: /usr/omc/config/global/env/Common. It has a default value of 1000. MMI_EVENT_ADDITIONAL_INFO_WIDTH The MMI_EVENT_ADDITIONAL_INFO_WIDTH environment variable specifies the pixel width of the Event Additional Information field.csh file. MMI_CLEAR_INACTIVE_FMIC This environmental variable default value is set in the /usr/omc/current/config/env/pmProcConfig.

6-18 68P02901W19-S Oct 2009 . MMI_EVENT_OBJ_INSTANCE_WIDTH The MMI_EVENT_OBJ_INSTANCE_WIDTH environment variable specifies the pixel width of the Object Instance field. NETWORK_CODE As defined by customer. MMI_EVT_FILTER_NUM_LOGS This environment variable defines the number of filter event logs. It has a default value of 120. 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 180. MMI_EVENT_OBJ_CLASS_WIDTH The MMI_EVENT_OBJ_CLASS_WIDTH environment variable specifies the pixel width of the Object Class field. 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 165. It has a default value of 80. It has a default value of 220. • NOT NULL: The alarm window starts as unsplit. MMI_EVENT_TYPE_WIDTH The MMI_EVENT_TYPE_WIDTH environment variable specifies the pixel width of the Event Type field. Values: • NULL: The alarm window starts as normal (split). It has a default value of 650. MMI_START_WINDOW_AS_UNSPLIT The MMI_START_WINDOW_AS_UNSPLIT environment variable determines whether the Alarm window will start as split or unsplit.GUI processes environment variables Chapter 6: OMC-R Environment variables 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 2.

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. major. minor. major. • If this variable is set to two. The valid range for this environment variable is 0 to 3 which indicates: • If this variable is set to zero. OMCFEATURES This environment variable enables or disables the OMC-R features. OMC_TOP The OMC_TOP environment variable is used by the OMC-R software and. and minor alarms and the OMC-R will beep for critical. OMCAUDIBLESEVERITY. and investigate alarms. 68P02901W19-S 6-19 Oct 2009 . is set to /usr/omc. the hooter will sound for critical and major alarms and the OMC-R will beep for critical. the hooter will sound for critical alarms and the OMC-R will beep for critical and major alarms. the hooter will never sound and the OMC-R will beep for critical alarms. and minor alarms. REGION The REGION environment variable determines whether regions are used in the OMC-R GUI. PRINTER is set to lp. allowing a user to print to the printer device lp. The various alarm severities are described in Maintenance Information: Alarm Handling at the OMC-R (68P02901W26) manual. PRINTER The PRINTER variable specifies the printer device used for printing. major. by default.Operating Information: OMC-R System Administration GUI processes environment variables OMCAUDIBLESEVERITY The OMCAUDIBLESEVERITY environment variable affects the generation of the alarm as well as the alarm severity. Both these operations are dictated by the values of the GUI process environment variable. 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. • If this variable is set to one. The default value is 0 (disabled). the hooter will sound for critical. By default. • If this variable is set to three.

modify the /usr/omc/config/global/env/Common. The variable can be set to 0 or 1. • If this variable is set to 0. To set a non-default value for this variable.csh file. The default value is FALSE. SCROLL_TO_BOTTOM The SCROLL_TO_BOTTOM environment variable is associated with the PLMN alarm window. Use the following procedure to enable RESYNC_LOCKING: Procedure 6-6 Enabling AUTO_GEN_RDN 1 Log on as omcadmin. 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. • If this variable is set to 1. 2 Enter the following command: cd /usr/omc/config/global/env 3 Update the file Common.GUI processes environment variables Chapter 6: OMC-R Environment variables RESYNC_LOCKING The RESYNC_LOCKING environment variable value is by default located in the /usr/omc/current/config/env/Common. The RESYNC_LOCKING variable is set to 0 by default (disabled). 6-20 68P02901W19-S Oct 2009 .csh file.sh as follows: RESYNC_LOCKING=1 export RESYNC_LOCKING 4 Update the file Common. Resync Locking is enabled. To reconfigure this variable use Procedure 1 in Changing an environment variable on page 6-26. 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 is used by the OMC-R software to allow or prevent any other operation to be run parallel with a Resync operation. which displays all output arriving from the BSS. and by default the variable is set to 1. SITE_NAMING This environment variable is associated with the Navigation Tree Site Name IDs.csh as follows: setenv RESYNC_LOCKING 1 5 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. When SCROLL_TO_BOTTOM is set to TRUE. Resync Locking is disabled and any operation can run in parallel with a Resync operation.

If the environmental variable is not set. 68P02901W19-S 6-21 Oct 2009 . To reconfigure this variable refer to procedure 2 in Changing an environment variable on page 6-26. use procedure 2 in Changing an environment variable on page 6-26. If this timer value is exceeded. If set to YES then any responses are logged along with the commands. or is set to an invalid value. If RL_LOGCMDS is set to NO and RL_LOGRESPS is set to YES then no logging is performed. To reconfigure this variable. To reconfigure this variable. 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. The valid range of values for this variable is between 1 and 90. 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. RL_LOGRESPS The RL_LOGRESPS environment variable enables logging of the BSS command responses. Setting this environment variable to any non positive value (including zero) results in no timeout supervision being performed. The variable RL_LOGCMDS takes precedence over this variable. the default value of 60 is used. It has a default value of 1200 seconds and a range of any positive or negative value or 0. To reconfigure this variable. RL_SESSIONS The RL_SESSIONS environmental variable specifies the maximum number of simultaneous remote login sessions allowed.CNFG file. It has a default value of NO (not to log the responses) and valid options of YES or NO. It has a default value of YES (ON) and valid options of YES or NO. use procedure 2 in Changing an environment variable on page 6-26. the user is logged out of their remote login session. RL_LOGCMDS The RL_LOGCMDS environment variable controls the logging facility of the BSS commands.Operating Information: OMC-R System Administration RLOGIN variables RLOGIN variables The Remote Login variables are set in the $OMC_TOP/config/global/OMC.

To reconfigure this variable use procedure 2 in Changing an environment variable on page 6-26. 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. (where FMMGR is the mnemonic process). meaning that the alarm is triggered by just one error. FM_audit variables The FM_audit variables are set in the $OMC_TOP/config/global/FM_audit.25 connection establishment phase. meaning that the alarm is triggered by just one error. 6-22 68P02901W19-S Oct 2009 . 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. 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.FM_audit variables Chapter 6: OMC-R Environment variables RL_TIMER_NC The RL_TIMER_NC environment variable is used as a timeout variable for the X. To reconfigure the variable. It has a default value of NO (OFF) and provides valid options of NO or YES. 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. It has a default value of NO (OFF) and valid options of NO or YES. The default is 0. FM_CPU_AUDIT The FM_CPU_AUDIT environment variable controls whether a CPU audit is run. 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. use procedure 2 in Changing an environment variable on page 6-26. The default is 0. (where FMMGR is the mnemonic process). To reconfigure the variable use procedure 2 in Changing an environment variable on page 6-26. FM_MEM_AUDIT The FM_MEM_AUDIT environment variable controls whether a Memory audit is run.CNFG file. It has a default value of 25 seconds and a valid range of any positive integer.

CSM is enabled for sleeping carrier detection. CSM is disabled (the default). To reconfigure these variables. The system allows any combination of the three functions to be enabled. use procedure 2 in Changing an environment variable on page 6-26. If the call success rate falls below this threshold. or zero to disable that function: • If all three digits are set to zero. CSMMAIN variables The Call Success Monitoring process (CSMMAIN) requires three variables that are set in the $OMC_TOP/config/global/omc. • If the first digit is set to 1. The default is 80%. This is used to detect sleeping carriers. meaning that the alarm is triggered by just one error. CALL_SUCCESS_THRESHOLD The CALL_SUCCESS_THRESHOLD environment variable defines the minimum acceptable percentage of successful calls per cell. 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. This variable ensures that CSMMAIN does not raise an alarm when there are very few calls on a cell in an interval. It is a three digit binary number in which each digit can be set to 1 to enable a CSM function. the CSMMAIN process generates an alarm. (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.Operating Information: OMC-R System Administration 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. • If the third digit is set to 1. CSM is enabled for sleeping cell detection. 68P02901W19-S 6-23 Oct 2009 . CSM is enabled for sleeping timeslot detection. The default is 0. • If the second digit is set to 1.CNFG file. This variable is set once per network and cannot be set on an individual cell basis. The default is 25.

If AUTORESYNC is set to Y. The range of values allowed for MAX_AUTO_RESYNCS is 1 to MAX_RESYNCS –1. AUTORESYNC The environment variable AUTORESYNC enables remote sites to be resynchronized to the OMC-R automatically if. If MAX_AUTO_RESYNCS is out of this range. then this variable is set to a default value of 10. Out of the ten variables. MAX_AUTO_RESYNCS This variable is used to define the number of auto resync allowed to happen at a time. By default it is set to 600. so unlike other environment variables. a link malfunctions between the two and then comes back into service. It specifies the time in seconds. two slots are allotted to auto resync and the remaining eight slots for manual resync. The active resync table is defined based on this variable. are contained in the following file on the system processor: /usr/omc/config/global/RC. 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. then the default value is used for both.CNFG The ResyncCtrl process periodically reads the RC. No auto resync is processed as it is disabled. Autosynchronization occurs automatically. then this variable is set to a default value of 2. If AUTORESYNC is set to N and MAX_RESYNCS equals 10. MAX_RESYNCS is set to 10 and MAX_AUTO_RESYNCS is set to 2. 6-24 68P02901W19-S Oct 2009 . regardless of the setting of the environment variable ENABLERESYNC. any variables changed in this file are picked up without having to perform an OMC-R software stop and start. If MAX_AUTO_RESYNCS is set greater than or equal to number of MAX_RESYNCS. TIMER The environment variable TIMER sets the duration Resync Control waits for a resync to complete. ENABLERESYNC The environment variable ENABLERESYNC can be set to Y or N to turn resynchronization ON or OFF. for example. The default value is 10. then all the ten resync slots are used for manual resync.ResyncCtrl variables Chapter 6: OMC-R Environment variables ResyncCtrl variables The environment variables that the Resync Control feature uses. If MAX_RESYNCS is out of this range. then a maximum of ten resync control variables are processed at a time. The range of values allowed for MAX_RESYNCS is 1 to 15. By default this is set to N.CNFG file. MAX_RESYNCS This variable is used to define the number of active resyncs allowed to happen at a time. The duration is set between the values 150 and 3600. MAX_RESYNCS and MAX_AUTO_RESYNCS. The default value is 2.

The default value is 40 as per GSR9 1900.35 load onwards. The default value is 30 as per GSR9 1900.CNFG 4 OMC start 6-25 Oct 2009 .Operating Information: OMC-R System Administration 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. when this timer was introduced. Follow Procedure 6-7 to increase the timer value: Procedure 6-7 68P02901W19-S Increasing the timer value 1 Login as omcadmin 2 OMC stop 3 Increase the value of OMCINIT_DYING_TIME in /usr/gsm/current/config/INIT. It is used by OMC-R processes during OMC shutdown.CNFG.34 load. This parameter is user configurable and is present in the file /usr/gsm/current/config/INIT. In case the processes need more time to exit gracefully the timer value can be increased suitably.

csh /usr/omc/config/global/env/mibProcConfig. use of one of the two methods. • Verify whether the variable is set up correctly by echoing it to the screen. • Log out and logging back in again. Continued 6-26 68P02901W19-S Oct 2009 .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 using the vi editor. • Method 1 Used for changing an environment variable in any of the following files: /usr/omc/config/global/env/mmiProcConfig. If turning off an environment variable. use the following procedure to modify the ATC_TIMEOUT variable: Procedure 6-8 Changing an environment variable using Method 1 (Example 1) 1 Login as omcadmin on the system processor and change the directory: cd /usr/omc/config/global/ 2 Modify the ATC_TIMEOUT environment variable in the mibProcConfig. • Stop the OMC-R by issuing the omc stop command.Changing an environment variable Chapter 6: OMC-R Environment variables Changing an environment variable ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Methods for changing an environment variable To Change an environmental variable. This sources the environment files automatically.csh file in /usr/omc/config/global/env where the variable is defined and make the necessary change. For example.csh /usr/omc/config/global/env/pmProcConfig. it is not sufficient to remove the line or comment it out. • Restart the OMC-R by issuing the omc start command. Instead comment out the old line and add a new line containing an unsetenv <variable_name>.

Example 2: The following procedure modifies the CSMMAIN variables: 68P02901W19-S 6-27 Oct 2009 . 4 Log out and login again.csh 3 Stop the OMC-R as described in Manual startup and shutdown of OMC-R software on page 7-12. • Use the utility omctool to reconfigure the process associated with this environment variable. Reconfiguration occurs at the next poll.sh file.CNFG 3 Invoke the omctool utility using the following parameters: omctool -m RLOGIN -c Reconfiguration takes place at the next poll. login as omcadmin and check if a new value is assigned: echo $ATC_TIMEOUT 6 In the same window. see omctool utility in the Restartable processes on page 2-49 section.CNFG file using the vi editor: vi OMC.Operating Information: OMC-R System Administration Procedure 6-8 (Continued) Methods for changing an environment variable Changing an environment variable using Method 1 (Example 1) The change is automatically propagated to the mibProcConfig. Method 2 The method involves the following: • Login as omcadmin and edit the appropriate environment variable within the OMC. 5 In a new Xterm window.CNFG file. restart the OMC-R as described in Manual startup and shutdown of OMC-R software on page 7-12. • OMCINIT periodically polling selected processes to check for particular external events that may have occurred. Use the following command to edit the file: vi mibProcConfig. Example 1: The following procedure modifies the RL_LOGCMDS variable: Procedure 6-9 Changing an environment variable using Method 2 (Example 1) 1 Login as omcadmin on the system processor and change directory: cd /usr/omc/config/global/ 2 Modify the RL_LOGCMDS entry in the OMC. An example is the RLOGIN mnemonic process. The process can be defined by its mnemonic name. For more information on mnemonic processes.

CNFG file using the vi editor: vi OMC.Methods for changing an environment variable Procedure 6-10 Chapter 6: OMC-R Environment variables Changing an environment variable using Method 2 (Example 2) 1 Login as omcadmin on the system processor and change directory as follows: cd /usr/omc/config/global/env 2 Modify the CSMMAIN variables in the OMC.CNFG 3 Invoke the omctool utility using the following parameters: omctool -m PARSER_1 -c Reconfiguration happens at the next poll. 68P02901W19-S Oct 2009 . Example 3: The following procedure modifies the Parser variables: Procedure 6-11 6-28 Changing an environment variable using Method 2 (Example 3) 1 Login as omcadmin on the system processor and change the directory as follows: cd /usr/omc/config/global/env 2 Modify the Parser variables in the OMC.CNFG file using the vi editor: vi OMC.CNFG 3 Invoke the omctool utility with the appropriate parameters: omctool -m CSMMAIN -c Reconfiguration happens at the next poll.

secondary alarms are suppressed. Setting status of the consolidated alarms Use the following procedure to set the status of the Consolidated Alarms. NOTE Refer to OMC-R Online Help. • Level 3 The subscriber mode map is default.Operating Information: OMC-R System Administration 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. secondary alarms are suppressed.csh • /usr/omc/config/global/env/mibProcConfig. secondary alarms are displayed. The line entry value in the three files is SETENV CONSOLIDATION 3. Procedure 6-12 1 Setting the status of consolidated alarms Login to the system processor as omcadmin and change the directory as follows: cd /usr/omc/config/global/env Continued 68P02901W19-S 6-29 Oct 2009 . • Level 2 The device mode map is default. Network Operation manual for the Consolidated Alarms operation. The line entry value in the three files is SETENV CONSOLIDATION 2. The line entry value in the three files is SETENV CONSOLIDATION 1.csh • /usr/omc/config/global/env/mmiProcConfig.csh There are three possible levels of consolidation: • Level 1 The device mode map is default. The status of the Consolidated Alarms is set up in the following files: • /usr/omc/config/global/env/pmProcConfig.

csh and mmiProcConfig.csh file using the vi editor: vi pmProcConfig. 3 for Level 3. 6-30 4 Repeat step 1 to step 3 for the files mibProcConfig. 6 Restart all the GUI server or clients.csh file using the vi editor. 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 1 Login to the system processor as omcadmin and change the directory as follows: cd /usr/omc/config/global/env 2 Open the pmProcConfig. 68P02901W19-S Oct 2009 . 5 Stop and restart the OMC-R as described in Manual startup and shutdown of OMC-R software on page 7-12 in order to activate these changes. 2 for Level 2. 3 for Level 3.csh Where <x>is: 1 for Level 1. 2 for Level 2. 7 Restart all the GUI servers or clients. UNSETENV CONSOLIDATION Close the pmProcConfig.csh files.csh and mmiProcConfig.csh 3 Delete the SETENV CONSOLIDATION <x> line entry and enter the following line entries: vi pmProcConfig. 5 Repeat step 1 to step 3 for the files mibProcConfig.Disabling the status of consolidated alarms Procedure 6-12 Chapter 6: OMC-R Environment variables Setting the status of consolidated alarms (Continued) 2 Open the pmProcConfig.csh file using the vi editor: vi pmProcConfig. 6 Stop and restart the OMC-R as described in Manual startup and shutdown of OMC-R software on page 7-12 in order to activate these changes.csh 3 Enter the following line entry at the end of the file: SETENV CONSOLIDATION <x> Where <x> is: 1 for Level 1.csh file using the vi editor. 4 Close the pmProcConfig.csh files.

Operating Information: OMC-R System Administration Non user configurable environment variables Non user configurable environment variables ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Introduction to 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. which interact with the GUI server or clients. NOTE The variables should only be changed by qualified personnel under guidance from Motorola Support.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 .sh versions of these files (Bourne Shells).csh versions. • /usr/omc/current/config/env/mmiProcConfig. The non-user configurable environment variables that are specified in the /usr/omc/current/config/env/Common. Contact Motorola Support for further information. which are automatically updated if changes are made in the . There are .csh file are listed in Table 6-1. Table 6-1 Non—user configurable variables in the Common.csh Defines the variables used by the system processes.csh Defines the variables used by the GUI processes. Any unauthorized changes may not be supported by Motorola and may result in system and/or performance degradation.

cfg IPC_HELP_TEXT $CM_ROOT/config/ipc_help2.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.Introduction to non user configurable environment variables Table 6-1 Chapter 6: OMC-R Environment variables Non—user configurable variables in the Common.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 1 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 .

csh file are listed in Table 6-2.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 0 AUTO_POP_CELLID 0 AXHOME $OMC_TOP/current/bin/axhome BATCH_IPC_TIMEOUT 600 BATCH_NERESP_TIMEOUT 30 BSS_VER BSGSM_1. Table 6-2 Non—user configurable variables in the mmiProcConfig.Operating Information: OMC-R System Administration Table 6-1 Introduction to non user configurable environment variables Non—user configurable variables in the Common.0.6.x CMAUDITDIR $OMC_TOP/logs CM_LOG $OMC_TOP/logs CM_ROOT $OMC_TOP/current Continued 68P02901W19-S 6-33 Oct 2009 .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.

$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 .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 0 EM_LOG $OMC_TOP/ne_data/ev_logs EM_ROOT $OMC_TOP/current ENABLE_ACCESS_LOG 0 EP_ALARM_SUB_LIST_NAME ‘.$EP_EVENTS’ EP_IPCQ_READ_TIMEOUT 1 EP_NUMBER_IPCQ_READS 10 INFORMIXDIR /usr/informix IPC_CONFIG $SYS_CONFIG/ipc.cfg IPC_HELP_TEXT $CM_ROOT/config/ipc_help2.$ALM_ALARMS’ MMI_DAEMON /usr/omc/current/bin/mmi_daemon MMI_EVT_DEFAULT_SUBSLIST _NAME ‘.Introduction to non user configurable environment variables Chapter 6: OMC-R Environment variables Table 6-2 Non—user configurable variables in the mmiProcConfig.txt LDM_LOG $OMC_TOP/logs LDM_ROOT $OMC_TOP/current LISTTMPDIR $OMC_TOP/logs/ListDir LOG_TO_SCREEN 1 MMI_ALARM_PIXMAP siren_on MMI_ALM_DEFAULT_SUBSLIST _NAME ‘.$MAP_ALARMS’ EP_EVENT_SUB_LIST_NAME ‘.

csh file (Continued) Variable name Value MMI_ROOT $OMC_TOP/current/config 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 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 0 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 1 UIDPATH $MSCONFIG/uid/%U USE_CACHE 1 XAPPLRESDIR $OMC_TOP/current/config XPATH /usr/openwin/bin 68P02901W19-S 6-35 Oct 2009 .cfg OMC_HELP_PATH $OMC_TOP/config/local/help OMC_IPC_CONFIG $NMSROOT/config/ipc.Operating Information: OMC-R System Administration Introduction to non user configurable environment variables Table 6-2 Non—user configurable variables in the mmiProcConfig.

• Setting up a cron job to synchronize the NE time with the time at the OMC-R. This is the local time. 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. 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. Thu Dec 14 14:56 SGT 2005 6-36 68P02901W19-S Oct 2009 . it is important that the time of NEs and all processors at the OMC-R are kept consistent. Use the following procedure to display the current system date. Resetting the time The system processor is the master clock server. NOTE Entering date on the command line results in the date and time being displayed according to what is specified in /etc/default/init.Setting the time for the OMC-R and NEs Chapter 6: OMC-R Environment variables 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. • Setting up a cron job to keep the GUI time synchronized to the system processor time. For example. Procedure 6-14 1 Display the current system date Enter the following command: 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.

taking particular care to set the system processor time accurately. 2 Change the processor time using the following command: date -u <hhmm> For example. 68P02901W19-S 6-37 Oct 2009 . The GUI processor clocks must be set to the same time as the system processor clock whenever the system processor clock is changed. which is applied. 3 Ensure that date -u shows the same time on all processors (to within one or two minutes). The time zone files are in the /usr/share/lib/zoneinfo directory. Default time zones in OMC-R In UNIX. Configuring system time to local time To configure the system time to local time. set the time on all the machines. Procedure 6-16 Configuring the system time to local time 1 Login as root. The offset may vary at different times of the year. taking particular care to set the system processor time accurately. The command sets time to the nearest minute. date -u 2259 sets the time to 22:59 GMT.Operating Information: OMC-R System Administration Configuring system time to GMT Configuring system time to GMT To configure the system time to GMT. set the time on all the machines. date 2259 sets the time to 22:59 local time. Reference the files in this area for a list of precompiled time zones. 3 Ensure that date shows the same time on all processors (to within one or two minutes). a time zone is a compiled data file containing information about the offset from GMT. The command sets time to the nearest minute. Use the following procedure on each processor to configure the system time to local time. The GUI clocks must be set to the same time as the system processor clock whenever the system processor clock is changed. Use the following procedure on each processor to configure the system time: Procedure 6-15 Configuring the system time to GMT 1 Login as root. 2 Change the processor time using the following command: date <hhmm> For example.

The NAME of the zone is used as a time zone. To check if a time zone is behaving correctly. Asia.Non default time zones in OMC-R without daylight saving Chapter 6: OMC-R Environment variables 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. 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. it shows that the zone Asia/Calcutta offset 5 hours and 30 minutes ahead of GMT. If the desired time zone has not already been compiled. and they corrupt the terminal display. The letters displayed are IST. In addition. For example. 6-38 68P02901W19-S Oct 2009 . see Checking the time zone. 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. search for the appropriate country or city name. In the time zone file. These are compiled time zone files. The uncompiled time zone file has to be compiled before it is used. if the source file is Asia then the directory is /usr/share/lib/zoneinfo/asia. For example. Once the time zone is set. This setup must be repeated for each processor in the OMC-R. For example. it is advisable to check to see if the time zone works as expected. The compiled data files are stored in the directory /usr/share/lib/zoneinfo/<source_filename. 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.

The compiled data files are stored in the directory /usr/share/lib/zoneinfo/<source_filename>. 68P02901W19-S 6-39 Oct 2009 . 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 6 2:00 MET%s In the example. Daylight saving for this example follows the M-Eur rules. If the desired time zone has not already been compiled. Their use is recommended because they support daylight saving. and is called MET.Operating Information: OMC-R System Administration 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. 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. 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. For example. The NAME of the zone may be used as a time zone. and corrupt the terminal display. the time is one hour ahead of GMT. search for the appropriate country or city name. 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. For example. a prefix is added to indicate daylight saving. For example. This prefix is indicated by %s. The uncompiled time zone has to be compiled before it can be used. In the time zone file. Europe. During summer.

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 0 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. Procedure 6-17 1 Setting the time zone 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. • The daylight saving suffix is DST. it is advisable to check to see if the time zone works as expected. Once the time zone is set. The Europe file contains daylight saving settings. Examples: To use Middle European Time (MET). These settings follow the M-Eur rules. • At 02:00 on the last Sunday in March the clock is advanced one hour. enter the complete zone name: TZ=<continent>/<city> To set the time zone for Calcutta. The second rule detailed in this file denotes the following: • Daylight saving ends at 02:00 on the last Sunday in October. enter: TZ=MET To use a city-specific time zone. enter: TZ=Asia/Calcutta Continued 6-40 68P02901W19-S Oct 2009 .Setting the time zone Chapter 6: OMC-R Environment variables Europe file format These rules are given elsewhere in the Europe file. Setting the time zone Use the following procedure to set the time zone: NOTE This procedure requires all processors at the OMC-R to be rebooted.

Operating Information: OMC-R System Administration 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. The timesynch script should be run at a period of low activity. Continued 68P02901W19-S 6-41 Oct 2009 . Log in to the system processor as omcadmin. daily at 30 minutes past midnight. 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). 5 Enter the following command: omc start 6 To confirm if the new time zone has taken effect. reboot the respective machines using the shutdown command: /usr/sbin/shutdown -g0 -i6 -y 4 After all the machines have restarted. NOTE It is strongly recommended that the timesynch script should be run on all the OMC-R systems. 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. and enter the following command: omc stop 3 As <root> on the system processor and all the GUI processors. For example. 2 Stop the OMC-R processes. Procedure 6-18 1 Synchronizing the time at the OMC-R Login as root on the relevant GUI processor. enter the following command: date Synchronizing the time at the OMC-R The timesynch script synchronizes the GUI processor clock with the clock on the system processor.

open a terminal window and enter man crontab Synchronizing the time at the NEs The site_timesynch script synchronizes the NE time with the time on the system processor. 2 and 3 until all GUI processors have been configured. This saves having to check and reset NE duration manually. if daylight saving changes take place at 02:00 on Sunday mornings. For example. • Once every week. 4 Repeat steps 1. 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. using the example given as a template. • After any daylight saving changes. site_timesynch should be run shortly after 03:00 on Sundays. Refer to Scheduling cron jobs using the batch scheduler on page 5-9 for details.Synchronizing the time at the NEs Procedure 6-18 2 Chapter 6: OMC-R Environment variables 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. add it. in the early morning. • At a quiet time For example. 68P02901W19-S Oct 2009 . For details of the syntax of the crontab file. 3 If the line entry is missing.

Operating Information: OMC-R System Administration

Synchronizing the time at the NEs

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

Synchronizing the time at the NEs

1

Login as omcadmin on the system processor.

2

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

3

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.

4

Repeat steps 1, 2 and 3 until all the GUI processors have been
configured.

5

For details of the syntax of the crontab file, open a terminal window
and enter:
man crontab

6-43

Synchronizing the time at the NEs

6-44

Chapter 6: OMC-R Environment variables

68P02901W19-S
Oct 2009

Chapter

7
System startup and shutdown

68P02901W19-S
Oct 2009

7-1

Overview

Chapter 7: System startup and shutdown

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.
The following topics are described in this chapter:

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 Information: OMC-R System Administration

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

Chapter 7: System startup and shutdown

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

Operating Information: OMC-R System Administration

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

Chapter 7: System 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

Operating Information: OMC-R System Administration

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

3

0

S

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

Chapter 7: System startup and shutdown

/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

Operating Information: OMC-R System Administration

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.

1

Login to the system processor as root.

2

Enter the following to shut down the processor:
/usr/sbin/shutdown -is -g0 -y
The system processor restarts in the single user mode.

3

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

Chapter 7: System startup and shutdown

Procedure 7-2

Switching the GUI processor from multiuser mode to single user mode

1

Login to the GUI processor as root

2

Enter the following command to shut down the processor:
shutdown -h now

3

From the OK prompt, type:
boot -s
The GUI processor restarts in the single user mode.

4

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

68P02901W19-S 7-11 Oct 2009 . for example. This command is similar to the init 0 command but does not run the rc0 scripts. To reboot the system. multi-user mode. execute the following command as user root. The reboot command The /user/sbin/reboot command performs a clean shutdown and brings the system to run level 3 by default. 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.-r This parameter allows the reconfiguration of the system. the addition of a peripheral device. reboot -. reboot Some useful parameters can be included in this command.Operating Information: OMC-R System Administration Bringing the system up from PROM mode Bringing the system up from PROM mode To bring the system up from PROM mode.-s This parameter enables the system to switch on to a single user mode after a reboot: reboot -. for example.

Procedure 7-3 Starting the OMC-R software manually 1 Login to the system processor as omcadmin. The UNIX ps utility displays processes operational. 2 Enter the following command: omc stop 3 Logout the system processor. Starting up OMC-R software Use the following procedure to start the OMC-R software manually. 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.Manual startup and shutdown of OMC-R software Chapter 7: System startup and shutdown 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. 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 1 Login to the system processor as omcadmin. 2 Enter the following command: omc start 3 Log out the system processor. The automatic method is built into the appropriate processor startup or shutdown routine. if the OMC-R software is running on the system. while the manual method is started from the command line. 7-12 68P02901W19-S Oct 2009 .

Operating Information: OMC-R System Administration Checking system processor processes Checking system processor processes To check the processes running on the system processor. and enter: ps -ef |grep + If the OMC software is running. carry out the following procedure. Procedure 7-5 1 Checking processes running on the system processor Login to the system processor as omcadmin. 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 ? 0:00 /usr/omc/current/bin/x25appl + 1 omcadmin 814 798 0 Aug 16 ? 0:00 /usr/omc/current/bin/EventInterface + omcadmin 817 798 0 Aug 16 ? 0:00 /usr/omc/current/bin/x25appl + 5 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 ? 0:00 /usr/omc/current/bin/x25appl + 6 omcadmin 821 798 0 Aug 16 ? 0:00 /usr/omc/current/bin/x25appl + 7 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 ? 0:00 /usr/omc/current/bin/x25appl + 3 omcadmin 831 798 0 Aug 16 ? 0:00 /usr/omc/current/bin/x25appl + 4 omcadmin 832 798 0 Aug 16 ? Continued 68P02901W19-S 7-13 Oct 2009 .

Checking system processor processes Procedure 7-5 Chapter 7: System startup and shutdown 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 omcadmin 1064 1058 0 Aug 16 ? 0:03 /usr/omc/current/bin/resync +q +c /usr/omc/current/config -r informix +i 8 +a 4 omcadmin 1065 1058 0 Aug 16 ? 0:03 /usr/omc/current/bin/pmProxy +q +c. 68P02901W19-S Oct 2009 . /usr/omc/current/config -r informix +i 7 +a omcadmin 1060 1058 0 Aug 16 ? 0:03 /usr/omc/current/bin/emProxy +q +c /usr/omc/current/config -r informix +i 12 +a omcadmin 1063 1058 0 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 /usr/omc/current/config -r informix +i 4 +a 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 /usr/omc/current/config -r informix +i 9 +a 40 omcadmin 1067 1058 0 Aug 16 ? 0:02 /usr/omc/current/bin/callTrace +q +c /usr/omc/current/config -r informix +i 20 omcadmin 1068 1058 0 Aug 16 ? 0:12 /usr/omc/current/bin/NetExp +q +c /usr/omc/current/config -r informix +i 25 +a omcadmin 1069 1058 0 Aug 16 ? 0:05 /usr/omc/current/bin/OmcPyTom +q +c /usr/omc/current/config -r informix +i 27 + omcadmin 1070 1058 0 Aug 16 ? 0:04 /usr/omc/current/bin/gprsTrace +q +c /usr/omc/current/config -r informix +i 28 omcadmin 26597 26572 0 15:23:58 pts/2 0:00 grep + somc57:omcadmin > 2 7-14 Log out the system processor.

Chapter 8 Database Management ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 68P02901W19-S Oct 2009 8-1 .

is used to store Configuration Management and Fault Management (FM) data. • Additional database maintenance procedures on page 8-32. Only personnel belonging to the group omc have write access to the tables within the CM database.Overview Chapter 8: Database Management Overview ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ This chapter describes the administrative procedures required to maintain the two INFORMIX databases. are initially installed on the system processor by Motorola personnel. • Checking the CM database on page 8-39. The following topics are described in this chapter: 8-2 • Overview of database management on page 8-3. • CM Database . and all relevant INFORMIX application modules. • Shutdown and startup of the PM and CM databases on page 8-16.The Configuration Management database (formerly the MIB database). For more information. • Dropping and Recreating the PM database on page 8-30. • PM Database . 68P02901W19-S Oct 2009 . • INFORMIX directory structure on page 8-13. refer to Installation and Configuration: OMC-R Clean Install (68P02901W47) manual. Both databases. Each database is managed by a separate INFORMIX Dynamic Server (IDS) Version 10. • Setting the onconfig parameters on page 8-26. • Checking the PM database on page 8-34.The Performance Management database (formerly the OMC database). is used to store Performance Management data and Event Management subscriptions along with subscription lists. • Database utilities on page 8-4. • Administering the PM database using the omc_db_maint utility on page 8-23.

Operating Information: OMC-R System Administration 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. $INFORMIXDIR/online. The /usr/omc/current/sbin/bss_dt_load. 68P02901W19-S 8-3 Oct 2009 . The cron job roll_online.sh cron job runs every night before midnight to automatically load default dates and times into the bss_datetimes table in the PM database. The IDS log file for the PM database. 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).log_OMC. is checked for errors and check-pointing.log performs an automatic roll-over of this log file.

logged into the system processor. 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 . The omc_db_maint utility is run. as user id informix.Database utilities Chapter 8: Database Management 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.

Use the following procedure to invoke onmonitor utility: Procedure 8-1 Invoking the onmonitor utility 1 Login to the system processor as root. the menus will not work properly. All onmonitor commands can be performed from the command line. press e to exit the command line. even if the help text indicates otherwise. CAUTION Do not use the function keys (F1. a status menu will appear which allows the interrogation of database parameters but does not allow any changes. If this should happen.informix NOTE If the onmonitor utility is invoked as any user other than informix. 68P02901W19-S 8-5 Oct 2009 . For further information regarding these commands. refer to the INFORMIX Administrator's Guide documentation.Operating Information: OMC-R System Administration onmonitor utility onmonitor utility The onmonitor utility is used for INFORMIX database management purposes. according to the required database. as they do not always work as expected. To access the PM database enter: omc_env To access the CM database enter: mib_env 5 Enter the following command to start the onmonitor utility: onmonitor NOTE If onmonitor is run with an incorrect screen configuration. Use the CTRL-character key combination or left arrow key. 2 Switch user to informix: su . 3 Ensure the TERM variable is set to vt100: setenv TERM vt100 4 Setup the correct environment. F2 and so on) when working with IDS.

after midnight). If the amount of data in the database is growing substantially.omc_db_maint utility Chapter 8: Database Management 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 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). potentially causing loss of PM statistics. 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. In addition there is a utility. the utility should never be interrupted or killed before it has run to completion. the db_disconnect utility is also called by the omc_db_maint utility (refer to db_disconnect utility for further details). The omc_db_maint utility is used to unload and delete the PM statistics and report on the database disk usage. NOTE The percentage of database space used report entered into the omc_db_maint log file is checked once a week. The disk usage report is placed into the omc_db_maint log file which is located in the $OMC_TOP/logs directory. 8-6 68P02901W19-S Oct 2009 . To ensure that the OMC-R software does not need to be stopped. The scheduling of the cron job should ideally be performed during low activity periods (for example. pm_purge_check. 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). 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). Procedures for running omc_db_maint both manually and as a cron job are described in Administering the PM database using the omc_db_maint utility on page 8-23. further investigation is advised.

in exceptional circumstances. 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. but an unload operation to $UNLOAD_DIR is not performed. pm_purge_data [-force|-FORCE] Where is -force optional parameter to force the deletion of data that has not been unloaded. pm_purge_data utility The pm_purge_data utility is responsible for the purging of expired statistics from the Performance Management database. -force The optional parameter to force the deletion of data that has not been unloaded. 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. A command line option can be invoked to override this behavior and force the deletion of statistics that have not been unloaded. 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. 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. It is usually run as a cron job from within the omc_db_maint utility.Operating Information: OMC-R System Administration 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. An example. -unload The optional parameter to suppress the unload operation. However. 68P02901W19-S 8-7 Oct 2009 . pm_daily_unload. The Parser must be disconnected while this utility is running.

This utility. The pm_purge_check utility runs every hour. until 23:02. If the utility should find that omc_db_maint has not successfully purged the database. The utility accepts no command line parameters. into the directory $OMC_TOP/ne_data/unload_stats/unload_dir. and will continue to send alarms until the problem is rectified. However. pm_purge_check utility The pm_purge_check utility is responsible for ensuring the daily purge of data has occurred. On receipt of this alarm the operator should investigate and correct any issues with omc_db_maint. 07:02. is usually invoked from within the omc_db_maint utility. 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 .mm. when the alarm will be cleared. and should run every hour until 23:00.yyyy. and that space has been prepared in the database ready for the following days statistics.dd where <yyyy> refers to the current year. db_disconnect utility The db_disconnect utility informs OMC-R applications to either disconnect from or reconnect to the database. 08:02. <mm> to the current month and <dd> to the current day in this month. then it sends a major alarm to the OMC. as well as a snapshot of all nonstatistics data. This utility should form part of any database maintenance procedure which affects the tables used by these applications. For example. which is stored in $OMC_TOP/current/sbin. if omc_db_maint is scheduled to start at 04:02 then pm_purge_check should be scheduled to start at 06:02. it can be invoked from the command line in exceptional circumstances. The data is stored in compressed. | delimited ASCII files.pm_daily_unload utility Chapter 8: Database Management pm_daily_unload utility The pm_daily_unload utility unloads yesterdays statistics. The utility resides in $OMC_TOP/current/sbin and accepts no command line parameters. 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).

the following alias must be entered: omc_env The utility is invoked with a set of parameters which specify the operations to perform. Manually running db_pm_maint To run db_pm_maint on the PM database. therefore. 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. 68P02901W19-S 8-9 Oct 2009 . NOTE The $DBMS_ROOT environment variable is only set when the user is logged into the system processor as omcadmin. To ensure that the database does not become full. not usually be run manually. The syntax for invocation is: db_pm_maint [-e] Where is -e entity consistency. the db_pm_maint utility must be run regularly to delete any entities from the PM database for which there are no statistics. pmProxy. NOTE It is necessary to include the -e flag when running db_pm_maint. csm and the Event Manager (EM) applications if the OMC-R database has to be brought online.Operating Information: OMC-R System Administration 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. delete all those entities for which there are no statistics. db_pm_maint utility Most of the PM database data storage is allocated to PM statistics.

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 . Use the following procedure to run the omc_db_ckspace utility: Procedure 8-2 Running the omc_db_ckspace utility 1 Login to the system processor as omcadmin. therefore. If neither PM nor CM database is declared. The syntax for invocation is: omc_db_ckspace [-u] [-f] {omc | mib} Where is -u update statistics for database(s). omc_db_ckspace will run on the PM database by default. 2 Disconnect the database by entering the following command: $DBMS_ROOT/sbin/db_disconnect disconnect 3 To run the utility on the PM database. mib CM database. -f full table listing printed. omc PM database. It can be run against both the PM and CM databases. It is run as part of the omc_db_maint utility and would.omc_db_ckspace utility Chapter 8: Database Management omc_db_ckspace utility The omc_db_ckspace utility presents information on all DBSpace allocation and all TBLSpace allocation in summary format. 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. not usually be run directly. enter the following: $DBMS_ROOT/sbin/omc_db_ckspace omc To run the utility on the CM database. Manually running omc_db_ckspace The omc_db_ckspace utility is located in the directory $DBMS_ROOT/sbin.

the TBLSpace section shows how much of that allocation is actually free. 2 Enter the following to check that the $FMPATH environment variable is set: echo $FMPATH FMPATH is set to /usr/omc/ne_data/raw_stats.csh) identifies the base UNIX directory in which all uploaded statistics are stored before being presented to the parser. so that data contained in the files can be inserted into the PM database. which files need to be parsed. 4 Enter the following command to reconnect the database: $DBMS_ROOT/sbin/db_disconnect connect 5 Log out of the system processor. Although the above output indicates that the PM database is 78 percent full. Use the following procedure to run the pm_manual_parse utility: Procedure 8-3 Running the pm_manual_parse utility 1 Login to the system processor as omcadmin. The <value> parameter is an integer less than 9999. The utility informs the parser. • The file must be globally readable. The reason for this apparent discrepancy is that the database has been sized for one extent. • Both absolute and relative path names are allowed. All uploaded statistics files are globally readable by default. pm_manual_parse utility The utility pm_manual_parse is used to parse raw PM statistics files that have been missed by the parser.Operating Information: OMC-R System Administration Procedure 8-2 pm_manual_parse utility Running the omc_db_ckspace utility (Continued) The output provides descriptions of all DBSpaces and all TBLSpaces. This environment variable (set by default in sysCommon. 3 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. Continued 68P02901W19-S 8-11 Oct 2009 . • <filename> is the specified file to be parsed. The <filename> parameter must satisfy the following criteria: • The specified file must exist.

To see if the parse was successful. 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. 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. • Wild cards are allowed for file names to allow submission of multiple files. If not. 68P02901W19-S Oct 2009 .pm_manual_parse utility Chapter 8: Database Management Procedure 8-3 4 8-12 Running the pm_manual_parse utility (Continued) • The file must be an uploaded statistics file which has not yet been parsed. the file contents will not be added to the statistics database.

68P02901W19-S 8-13 Oct 2009 . on the relevant processor. is located by the environment variable $INFORMIXDIR (set to /usr/informix).Operating Information: OMC-R System Administration INFORMIX directory structure INFORMIX directory structure ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Overview of the INFORMIX directory structure When the INFORMIX products are installed. The PM database scripts on the system processor can be located by using the environment variable $DBMS_ROOT (set to $OMC_TOP/current). 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. and the OMC-R software loaded. the IDS databases initialized. The INFORMIX databases message logs are held in $INFORMIXDIR on the system processor.

Figure 8-1 8-14 INFORMIX directory structure on the system processor 68P02901W19-S Oct 2009 .INFORMIX directory structure on the system processor Chapter 8: Database Management INFORMIX directory structure on the system processor Figure 8-1 shows the INFORMIX directory structure on the system processor.

to allow for the connection of client software to the IDS. NOTE There are no databases located on a GUI processor. 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 . All databases reside on the system processor.Operating Information: OMC-R System Administration INFORMIX directory structure on the GUI processor INFORMIX directory structure on the GUI processor The GUI processor also contains INFORMIX products. The GUI processor is merely a client for connection purposes.

by pressing m. 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 Shutting down the PM database through onmonitor 1 Login to the system processor as omcadmin. 7 Select the Mode menu. The Mode menu is displayed as shown in Figure 8-4. as follows: $DBMS_ROOT/sbin/db_disconnect disconnect 3 Switch to user root and enter the root password: su .root 4 Switch to user informix: su .informix 5 Set the correct environment: cd /usr/omc/config/global omc_env 6 Start onmonitor utility: onmonitor The Status menu is displayed as shown in Figure 8-3. Continued 8-16 68P02901W19-S Oct 2009 .Shutdown and startup of the PM and CM databases Chapter 8: Database Management 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. disconnect all OMC-R applications from the database using the db_disconnect utility. 2 If the OMC-R applications are still running.

. the following prompt is displayed: Do you really want to shutdown? (y/n) Answer no (n) to terminate the shutdown procedure. . . 68P02901W19-S 10 Exit onmonitor by pressing e twice.Operating Information: OMC-R System Administration Procedure 8-4 8 Shutting down the PM database through onmonitor 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 prompt is displayed: Do you want to see the list of user threads? (y/n) Answer yes (y) to list the active user threads. please wait . please wait . The following message is displayed: Shutting down. . NOTE Where there is no prompt for user threads. . The database enters Quiescent mode. 11 Log out of the system processor. or after the active user threads have been listed. . Answer yes (y) to place the database into Quiescent mode. 8-17 Oct 2009 . 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. 9 Select Take Off-line by pressing two keys SHIFT-T. • If there are no users. The following message is displayed: Shutting down. select Immediate Shutdown to put the INFORMIX RDBMS directly into Quiescent mode.

4 Select the Mode menu. Use the following procedure to shut down the CM database using onmonitor: Procedure 8-5 Shutting down the CM database using onmonitor 1 Login to the system processor as root and switch to user informix: su .Shutting down the CM database through onmonitor Chapter 8: Database Management 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. Continued 8-18 68P02901W19-S Oct 2009 . The Mode menu is displayed as shown in Figure 8-4.informix 2 Set the correct environment: mib_env 3 Start the onmonitor utility: onmonitor The Status menu is displayed as shown in Figure 8-3. by pressing m. Refer to Chapter 7 System startup and shutdown for stopping the OMC-R software.

. . or after the active user threads have been listed. then log out of the system processor. please wait . The following message is displayed: Shutting down. . Starting up the PM database through onmonitor Use the following procedure to start up the PM database using the onmonitor utility: 68P02901W19-S 8-19 Oct 2009 . Shutdown is complete when the Mode menu returns and the state line indicates Off-Line.Operating Information: OMC-R System Administration 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. select Immediate-Shutdown to put the INFORMIX RDBMS directly into Quiescent mode. The following message is displayed: Shutting down. • If there are no users. . the following prompt is displayed: Do you want to see the list of user threads? (y/n) Answer yes (y) to list the active user threads. Answer yes (y) to place the database into Quiescent mode. . 7 Exit onmonitor by pressing e twice. the following prompt is displayed: Do you really want to shutdown? (y/n) Answer no (n) to terminate the shutdown procedure. Select take offline by pressing two keys SHIFT-t. . • 6 The database enters Quiescent mode. please wait . NOTE Where there is no prompt for user threads. The INFORMIX RDBMS changes state from Quiescent mode to Off-Line mode.

omcadmin Enter the omcadmin password. they may be connected using the db_disconnect utility using the following commands: su . The Mode menu is displayed as shown in Figure 8-6. 5 Select Startup by pressing s. 4 Select the Mode menu. This displays messages similar to the following: Initializing please wait Press return to continue. then type: $DBMS_ROOT/sbin/db_disconnect connect Figure 8-5 The onmonitor Status menu indicating Offline state Figure 8-6 Mode menu indicating Offline state 68P02901W19-S Oct 2009 . 8 If the OMC-R applications are already running.Starting up the PM database through onmonitor Procedure 8-6 Chapter 8: Database Management Starting up the PM database using onmonitor 1 Login to the system processor as root and switch to user informix: su . 8-20 6 Select On-Line by pressing o. by pressing m. 7 Exit onmonitor by pressing e twice.informix 2 Set the correct environment. omc_env 3 Start the onmonitor utility: onmonitor The Status menu is displayed as shown in Figure 8-5.

Operating Information: OMC-R System Administration 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 1 Login to the system processor as root and switch to user informix: su . Figure 8-7 Mode menu indicating offline state Figure 8-8 The onmonitor Status menu indicating online state 68P02901W19-S 8-21 Oct 2009 . 4 Select the Mode menu as shown in Figure 8-7. 7 Exit onmonitor by pressing e. 5 Select Startup.informix 2 Set the correct environment background by entering the following commands: mib_env 3 Enter onmonitor and ensure the Startup menu is displayed. 8 Log out of the system processor. This will display messages similar to the following: Initialising please wait Press return to continue 6 Select On-Line by pressing O.

d/informix file.d/informix file. This script is executed at bootup.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. The automatic shutdown scripts are executed and both databases will be shut down. 8-22 68P02901W19-S Oct 2009 . Shutting down automatically The automatic shutdown scripts for the CM and PM databases are held in the /etc/init. The automatic startup script for the PM and CM databases is held in the /etc/init. The automatic startup script is executed. Use the following procedure to execute the automatic startup script: Procedure 8-8 Starting databases automatically using the startup script 1 Login to the system processor as root. 2 Enter the following: svcadm disable -st informix/pm for the PM Database and svcadm disable -st informix/cm for the CM Database. 2 Enter the following: svcadm enable -st informix/pm for the PM Database and svcadm enable -st informix/cm for the CM Database. Use the following procedure to execute the automatic shutdown script: Procedure 8-9 Stopping databases automatically using the shutdown script 1 Login to the system processor as root. NOTE The /etc/init.Starting up databases automatically Chapter 8: Database Management Starting up databases automatically To start up both databases automatically. These scripts are executed when the system is shut down. a script needs to be executed.

if you run out of disk space in the destination directory). This utility can be run either as a cron job or using a manual procedure. The omc_db_maint utility is located in the directory $OMC_TOP/current/sbin on the system processor. Refer to the section on the omc_db_maint utility for more information. 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. The scheduling of the cron job should ideally be performed during low activity periods (for example. This behavior can be overridden by using the -force parameter to omc_db_maint. It is recommended that the omc_db_maint utility be run daily as a cron job. within the root crontab file. It unloads and deletes PM statistics and reports on disk space used by the PM database. 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. is as follows: Continued 68P02901W19-S 8-23 Oct 2009 . See Automatic Checking Of Maintenance for more information on monitoring the overnight maintenance.Operating Information: OMC-R System Administration Administering the PM database using the omc_db_maint utility Administering the PM database using the omc_db_maint utility ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Using omc_db_maint The omc_db_maint utility provides a tool for administering the PM database.

check the omc_db_maint log file to ensure that the operation completed successfully: more $OMC_TOP/logs/omc_db_maint. Procedure 8-11 Running the omc_db_maint utility manually 1 Login to the system processor as root. Running omc_db_maint manually CAUTION The omc_db_maint script should not be interrupted or killed before it has run to completion. 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. 4 Check the PM database log file online.<yyyy>. if one is not already created. 3 Record the PM database disk usage information in the system administrator log book.Running omc_db_maint manually Procedure 8-10 Chapter 8: Database Management 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. <mm> to the current month and <dd> to the current day in this month. by entering the following: more /usr/informix/online. 2 Execute the omc_db_maint utility as follows: $OMC_TOP/current/sbin/omc_db_maint Continued 8-24 68P02901W19-S Oct 2009 . Use the following procedure to run the omc_db_maint utility manually.log_OMC 5 Archive the unloaded statistics to tape and remove them from the file system.log_OMC for errors.<mm>. referring to other sections of this manual where indicated.<dd> Where <yyyy> refers to the current year.

For example. 3 Check the omc_db_maint log file to ensure that the operation completed successfully: more $OMC_TOP/logs/omc_db_maint. if omc_db_maint is scheduled to run at 02:45 (see above). 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: more $OMC_TOP/logs/omc_db_maint.<mm>.<dd> Having investigated and corrected any problems omc_db_maint can be run manually to perform the maintenance. Once the maintenance has been completed successfully. and should run every hour until 23:00.<yyyy>.log_OMC 6 Archive the unloaded statistics to tape and remove them from the file system. If that space is not available for any reason the Parser will not be able to parse statistics into the database.<dd> Where <yyyy> refers to the current year. the pm_purge_check utility will automatically clear any outstanding alarms when it next runs. 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. 4 Record the PM database disk usage information in the system administrator log book.<mm>. 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. 68P02901W19-S 8-25 Oct 2009 . Refer to omc_db_maint utility for information regarding optional parameters and Running omc_db_maint Manually for the correct procedure for manual invocation.<yyyy>. This utility must be run as a cron job and should be scheduled to start 2 hours after the omc_db_maint utility.log_OMC for errors by entering the following: more /usr/informix/online. 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. <nn> to the current month and <dd> to the current day in this month. 5 Check the PM database log file online.Operating Information: OMC-R System Administration 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.

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). this parameter must be assigned to the maximum value held during the period covered by the backup. The procedure uses the TAPE parameters as an example. • /usr/informix/etc/onconfig_MIB the configuration file for the CM database. The configuration files hold many parameters associated with each respective IDS. Store the hard copy with the backup tapes. substitute TAPE for the required parameter for checking: Procedure 8-12 Checking onconfig parameters 1 Login to the system processor as root and switch user to informix: su . The configuration files are as follows: • /usr/informix/etc/onconfig_OMC the configuration file for the PM database.Setting the onconfig parameters Chapter 8: Database Management Setting the onconfig parameters ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ onconfig file overview Each Informix Dynamic Server has a configuration file. 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). Store the hard copy with the backup tapes.When restoring either the CM or PM databases from backup tapes. 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). An example of a parameter is: • Max # of Logical Logs . Checking onconfig parameters Use the following procedure to check parameter settings within /$INFORMIXDIR/etc/$ONCONFIG.informix 2 Change the directory by entering the following command: cd $OMC_TOP/config/global 3 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 .

For CM database enter: mib_env . enter the alias: omc_env For the CM database. Changing onconfig parameters CAUTION It is not recommended to change /$INFORMIXDIR/etc/$ONCONFIG parameters unless absolutely necessary. run the onmonitor utility and change the parameters. This procedure describes. onstat -c | grep TAPE . as an example.Operating Information: OMC-R System Administration Procedure 8-12 Changing onconfig parameters Checking onconfig parameters (Continued) For PM database enter: omc_env .informix 2 Set the TERM environment variable: setenv TERM vt100 3 Set the correct environment by selecting one of the following: For the PM database. The parameters supplied by Motorola have been chosen following extensive performance testing. Use the following procedure to change parameters in /$INFORMIXDIR/etc/$ONCONFIG. 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. The parameters should only be changed on the advice of INFORMIX-trained Motorola personnel. enter alias: mib_env Continued 68P02901W19-S 8-27 Oct 2009 . Refer to Changing onconfig parameters. changing the Max # of Logical Logs parameter using the onmonitor utility: Procedure 8-13 Changing onconfig parameters 1 Login to the system processor as root and switch user to informix: su .

. 5 Using the space bar. 7 Enter y. 10 Screen output similar to the following is displayed: SHARED MEMORY: Make desired changes and press ESC to record changes. and press RETURN. The following is displayed: Do you really want to shutdown? (y/n) ----------------------Online------. ----------Offline------. select the Exit option to return to the initial Setup menu. The following is displayed: PARAMETERS: initialise Shared-Memory perFormance data-Replication . -------- 9 Select the Shared Memory option using the space bar. Press F2 or CTRL-F for field-level help.. The following is displayed: MODES: Startup Online Graceful-Shutdown Immediate-Shutdown. Bring INFORMIX-Online to quiescent mode from offline.Press CTRL-W for 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. 6 Using the space bar. SegSize (K) [10800] Optical Cache Size (K) [128] Continued 8-28 68P02901W19-S Oct 2009 . select the Take Offline option and press RETURN. initialise root dbspace and shared memory configuration.Press CTRL-W for Help. select the Mode option and press RETURN.Press CTRL-W for Help.Press CTRL-W for Help. Press Interrupt to abort changes...Changing onconfig parameters Procedure 8-13 4 Chapter 8: Database Management 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 RETURN. 8 Using the space bar. ----------------------Online------.

the Shared Memory Setup window can be closed by pressing the interrupt key. 8-29 Oct 2009 . 14 Bring the database back online. change the Max # of Logical Logs parameter to the maximum value held during the period covered by the tape backup. 15 Select the Exit option.Operating Information: OMC-R System Administration Procedure 8-13 Changing onconfig parameters 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. 68P02901W19-S 13 If no changes are required. then select Exit again to close onmonitor utility and return to the command line prompt. 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. This is usually CTRL-c or DELETE. In this example procedure. 12 Press ESC to save the changes.

omc_env Continued 8-30 68P02901W19-S Oct 2009 .MM.14). enter the following commands as user omcadmin: cd /usr/omc/current/sbin db_create omc_db 5 To load up customer specifics enter the following for these tables as user omcadmin.2004. Contact Motorola Support for further information. 4 To recreate the PM database. The specific .drop database omc_db.YYYY.Dropping and Recreating the PM database Chapter 8: Database Management Dropping and Recreating the PM database ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ CAUTION This procedure is a drastic measure. enter the following command as user informix: svcadm restart -st informix/pm (to verify that the PM database engine is online again). unload_dir.05.DD (for example. and the PM database should only be dropped and recreated if absolutely necessary. Use the following procedure to drop and then recreate the PM database: Procedure 8-14 Dropping and Recreating the PM database 1 Shut down the OMC-R processes by logging in to the system processor as user omcadmin and entering the following command: omc stop 2 To drop the PM database. 3 Enter the following commands as user omcadmin: omc_env dbexport omc_db -ss isql .unl files that are being loaded must be uncompressed in the dated unload directory before the sql load commands are executed. where <unl_dir> is the name of the unload directory in the format: unload_dir.

load from /usr/omc/ne_data/unload_stats/<unl_dir>/stored_selections. load from /usr/omc/ne_data/unload_stats/<unl_dir>/custom_statistics.unl insert into subscriptions.unl insert into custom_statistics. load from /usr/omc/ne_data/unload_stats/<unl_dir>/entity. 7 Restart the OMC-R processes by entering the following command as user omcadmin: omc start 8-31 Oct 2009 .Operating Information: OMC-R System Administration Procedure 8-14 Dropping and Recreating the PM database Dropping and Recreating the PM database (Continued) isql omc_db load from /usr/omc/ne_data/unload_stats/<unl_dir>/subscriptions. are loaded by default when the PM database is created.unl insert into stored_selections. load from /usr/omc/ne_data/unload_stats/<unl_dir>/subscription_list. 68P02901W19-S 6 The Motorola shipped defaults.unl insert into entity. stored in /usr/omc/current/config.unl insert into subscription_list.

To ascertain the name of the statistic name and details. Checking for excess of 32000 statistics For a procedure to perform this task.unl and the subscription_list. 2 Enter the following commands on the system processor: omc_env isql omc_db unload to subscriptions. onto a specified tape device: Procedure 8-15 Backing up subscription data from the PM database 1 Login as omcadmin. through the creation of two UNIX files. Continued 8-32 68P02901W19-S Oct 2009 .unl select * from subscription_list. unload to subscription_list.unl select * from subscriptions. pass into this script the of the hex_id.unl files are created in omcadmin home directory. The subscriptions.of the statistic. Backing up subscription data Use the following procedure to backup subscriptions and subscription list data from the PM database. Checking stat details The statinfo script is located in /usr/omc/current/sbin/statinfo. NOTE The subscription data is still retained in the PM database. refer to section Using neighbor statistics on page 13-91 in Chapter 12 Backup Server Installation and Configuration.Additional database maintenance procedures Chapter 8: Database Management 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. 3 Use CTRL-c to exit from the isql utility. 4 Load a DAT tape into the tape drive of the system processor.

unl files to tape by executing the following commands: tar -cvf /dev/rmt/0n subscriptions.unl files from omcadmin home directory.Operating Information: OMC-R System Administration Procedure 8-15 68P02901W19-S Backing up subscription data Backing up subscription data from the PM database (Continued) 5 Backup the subscriptions.unl and the subscription_list.unl 8-33 Oct 2009 .unl mt -f /dev/rmt/0 rewind 6 Remove the subscriptions.unl tar -uvf /dev/rmt/0n subscription_list.unl and the subscription_list. if no longer required: rm subscriptions.unl rm subscription_list.

log_OMC This log file should show that checkpoints are completed successfully. in particular when the server is initialized. Copy the checklist in Table 14-6 to record the checks.mm. 2 Check the IDS log file for errors and check-pointing by entering the following command as user omcadmin: tail -f $INFORMIXDIR/online. As user root execute the following commands: cd $OMC_TOP/logs more omc_db_maint. • Disk space is not being consumed.ddmmyyyy 4 Check the output of the onmode_pm cron job by entering the following commands as user omcadmin: cd /var/mail more omcadmin | grep onmode_pm 5 Check the omc_db_maint log file to ensure that: • PM statistics are unloaded and deleted successfully. 3 Check that the IDS log files are rolled over by entering the following commands as user omcadmin: cd $INFORMIXDIR ls -l online. follow the procedure below. Continued 8-34 68P02901W19-S Oct 2009 . • Applications are disconnected and reconnected successfully when required.yyyy.Checking the PM database Chapter 8: Database Management Checking the PM database ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Check the PM database To check the PM database. Procedure 8-16 Checking the PM database 1 Check that the PM database is online by entering the following commands as user omcadmin: omc_env onmonitor This utility reports that the database is in an online mode.dd 6 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.log_OMC* Log files should exist in the form: online.log_OMC.

467968 Kbytes Userthreads 68P02901W19-S 8-35 Oct 2009 .UC4 -- On-Line -.Operating Information: OMC-R System Administration 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 8 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. 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. 9 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.40.Up 09:48:19 -.

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

On-Line -- Up 09:50:36 -.35 1674 0 ixda-R RA-pgsused lchwaits 459 537 34 onstat -d output for PM database A typical example for the onstat -d utility output display for the PM database is shown as follows: IBM Informix Dynamic Server Version 9.96 isamtot open write rollbk 473705 2247 99.78 11. 2047 maximum 8-37 Oct 2009 .467968 Kbytes Dbspaces address number fchunk nchunks 1 1 flags owner N flags name 2490e7d8 1 0x20001 informix rootdbs 25198948 2 0x20001 2 1 N informix omc_db_plog 25198a98 3 0x20001 3 1 N informix omc_db_llog 25198be8 4 0x60001 4 1 N B informix omc_db_sp1 25198d38 5 0x60001 5 1 N B informix omc_db_sp2 25198e88 6 0x60001 6 1 N B informix omc_db_sp3 25199018 7 0x60001 7 1 N B informix omc_db_sp4 25199168 8 0x60001 8 1 N B informix omc_db_sp5 251992b8 9 0x60001 9 1 N B informix omc_db_sp6 25199408 10 0x60001 10 1 N B informix omc_db_sp7 25199558 11 0x60001 11 1 N B informix omc_db_sp8 251996a8 12 0x60001 12 1 N B informix omc_db_sp9 251997f8 13 0x60001 13 1 N B informix omc_db_sp10 25199948 14 0x60001 14 1 N B informix omc_db_sp11 25199a98 15 0x60001 15 1 N B informix omc_db_sp12 25199be8 16 0x2001 16 1 N T 68P02901W19-S informix omc_db_temp 16 active.1 bufwaits lokwaits lockreqs ckpwaits compress 1013573 1056 117 ovuserthread numckpts 0 1 24 7855 0 ovlock syscpu 249 seqscans 38 A idx-RA commit 0 gp_read gp_write 0 15 192674 0 0 flushes 0 0 425 delete gp_alloc gp_free 0 deadlks 20238 0 0 4 rewrite 18798 gp_rewrt gp_del 1868 96.40.UC4 -.Operating Information: OMC-R System Administration 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 0 da-RA 85.

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

log_OMC This log file should show that checkpoints are completed successfully. 2 Check the IDS log file for errors and check-pointing by entering the following commands as user omcadmin: tail -f $INFORMIXDIR/online.Operating Information: OMC-R System Administration Checking the CM database Checking the CM database ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Check the CM database Use the following procedure to check the CM database. Procedure 8-17 Checking the CM database 1 Check that the MIB database is online by entering the following commands as user omcadmin: mib_env onmonitor This utility reports that the database is in an online mode.ddmmyyyy 4 Check the output of the onmode_mib cron job by entering the following commands as user omcadmin: cd /var/mail more omcadmin | grep onmode_mib 5 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. 3 Check that the IDS log files are rolled over by entering the following commands as user omcadmin: cd $INFORMIXDIR ls -l online.log_OMC* Log files should exist of the form online. 7 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 An entry should exist similar to the following: inf7_MIB_serv 5010/tcp Continued 68P02901W19-S 8-39 Oct 2009 . Copy the checklist in Table 14-7 to record the checks. The output should be similar to that shown in the section omc_db_ckspace utility on page 8-10.log_OMC. in particular when the server is initialized. 6 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.

9 Check the status of the dbspaces and chunks of the CM IDS by entering the following commands as user informix: onstat -d Output should be similar to that shown in the section onstat -d output for CM database on page 8-42. An example line entry is shown as follows: inf7_MIB_serv 5010/tcp # MIB database Informix DSA instance 8-40 68P02901W19-S Oct 2009 . 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: more /usr/informix/etc/onconfig | grep TAPEDEV 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.CM sqlhosts file Chapter 8: Database Management Procedure 8-17 Checking the CM database (Continued) 8 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.

148480 Kbytes Userthreads address flags sessid nreads nwrites 1120f018 ---P--D 1 0 0 0 root 0 - 0 1 0 - 0 root 0 44 112102 0 - 0 0 0 0 omcadmin 0 112114a8 Y--P--.26 11a26888 0 23 - 0 112126f0 omcadmin - 11213f50 Y--P--.31 0 119950c8 0 11214568 Y--P--.23 omcadmin - 119d3cc0 0 Y--P--.33 omcadmin - 40 1 11b35c10 0 0 11215dc8 Y--P--. 24 bufwrits %cached 99.32 11b548d8 0 0 11a2c518 0 1 omcadmin - 0 112157b0 Y--P--.27 1 298 0 11213320 Y--P--.40. maximum concurrent Profile dskreads pagreads bufreads %cached dskwrits pagwrits 1589 1716 188887 128 total.29 38 0 11215198 11aedea0 0 omcadmin - 1 omcadmin Y--P--.11 0 tty 38 0 0 user omcadmin - 0 22 active.Up 23:23:25 -.34 56 omcadmin 11bc02b8 0 1 49 0 0 112169f8 11c00598 0 0 11217010 Y--P--.Operating Information: OMC-R System Administration 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: IBM Informix Dynamic Server Version 9.24 1 root 0 58 0 11211ac0 ---P--D 15 0 0 - 0 11210e90 Y--P--.25 11995c88 0 1 1 omcadmin console 0 11212d08 Y--P--.21 11bae8a8 0 1 root 34 - 0 0 0 112120d8 Y--P--.30 33 omcadmin - 0 11214b80 Y--P--.28 omcadmin - 11d47700 0 1 0 11213938 Y--P--.47 1 29 0 112163e0 Y--P--.UC4 -- On-Line -.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 0 0 8-41 Oct 2009 .19 1 41 1 11990eb8 0 55 omcadmin - 1 omcadmin 43 omcadmin - 11aaa168 0 1 41 11aaad78 0 Y--P--.16 2255 85.10 117f5fc8 0 tout locks 260 1120fc48 ---P--F root omcadmin 0 0 0 root 0 11210878 ---P--B 12 console wait 103 1120f630 ---P--F 0 0 60 ---P--.

32766 maximum 8-42 68P02901W19-S Oct 2009 .UC4 -.onstat -d output for CM database 0 Chapter 8: Database Management 0 syscpu 5 0 0 ovlock numckpts flushes 0 564 0 0 139122 ixda-RA idx-RA da-RA usercpu 18.40.On-Line -- Up 23:23:57 -.55 ckpwaits 0 0 2 RA-pgsused lchwaits onstat -d output for CM database A typical example for the onstat -d utility output display for the CM database is shown as follows: IBM Informix Dynamic Server Version 9.75 bufwaits lokwaits lockreqs deadlks compress seqscans 155 990 ovuserthread ovbuff 0 dltouts 0 1. 2047 maximum Chunks address chunk/dbs free bpages 921598 475696 2 2 PO-- 256000 11904018 3 3 1023998 PO-797280 size 767997 4 1 PO-- /dev/mib_db_logs 583624 921601 PO-102399 /dev/mib_db 11904328 5 PO-- 2 /dev/mib_db 1123fdf0 2 177100 256003 /dev/mib_db_logs 119041a0 4 102346 offset flags pathname 1110e928 1 /dev/mib_db1 5 2 5 active.148480 Kbytes Dbspaces address number fchunk nchunks flags owner flags name 1110e7d8 1 0x20001 1 1 N informix rootdbs 119044b0 2 0x20001 2 1 N informix physdbs 11904600 3 0x20001 3 1 N informix logsdbs 11904750 4 0x2001 4 1 N T informix tempdbs 119048a0 5 0x20001 5 1 N informix mib_db_sp1 5 active.

Operating Information: OMC-R System Administration Dropping and Recreating the CM database Dropping and Recreating the CM database ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ CAUTION This procedure is a drastic measure. enter the following command as user informix: svcadm restart -st informix/cm (to verify that the CM database engine is online again). 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 Dropping and Recreating the CM database 1 Shut down the OMC-R processes by logging in to the system processor as user omcadmin and entering the following command: omc stop 2 To drop the CM database. enter the following commands as user root: cd /usr/omc/sbin cm_setup 5 Restart the OMC-R processes by entering the following command as user omcadmin: omc start 8-43 .drop database mib_db. 3 Enter the following commands as user omcadmin: mib_env dbexport mib_db -ss isql . 4 To recreate the CM database. and the CM database should only be dropped and recreated if absolutely necessary.

Dropping and Recreating the CM database 8-44 Chapter 8: Database Management 68P02901W19-S Oct 2009 .

25 management ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 68P02901W19-S Oct 2009 9-1 .Chapter 9 X.

25 directory structure on page 9-8.25 management Overview ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ This chapter provides a technical description of X. • Updating X. The following topics are described in this chapter: 9-2 • X.Overview Chapter 9: X. • Starting and stopping X.25 connectivity on page 9-18.25 on page 9-9.25 commands on page 9-7. • Replacing the HSI card on page 9-17.25 application management on page 9-3.25 link configuration on page 9-13. 68P02901W19-S Oct 2009 . • Checking X.25 management functions. • X. • Basic X.

25 software application controls the routing of the data from the OMC-R system processor. The X. to the individual network elements.25 application management X. The following configuration file is required to configure the X. Configuring OMC-R processes for X.25 connections. the X. through the packet switch and multiplexer.Operating Information: OMC-R System Administration X.25 application management ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Overview of the X.25 The OMC-R applications that handle incoming or make outgoing X. must be configured in the OMC-R software. Figure 9-1 Centralized use of X.25 The full procedure required to configure X.25 connections: /usr/omc/config/global/x25_config 68P02901W19-S 9-3 Oct 2009 .25 software The X. This data is sent using the packet switch protocol.25 application is implemented for the OMC-R using SunLink X. When installation has been completed.25 Configuring X.25 for the OMC-R is described in the Installation and Configuration: OMC-R Clean Install (68P02901W47) manual.25 software will load and execute automatically in accordance with the startup or shutdown procedure.25.

Port/link identifier: This field is the link identifier used by the application.Configuring OMC-R processes for X. It is possible to run each X.25 management Each line in the x25_config file contains 11 fields.25 link configured within SunLink X. as illustrated in Figure 9-2.OMC_PU X25 128 2 50 NOTE The number of OMC_PU application processes may vary depending on the TCH capacity of the machine.OMC_RL X25 128 2 500 6 x25_chan6 0 71271213 H .25 connectivity. The 11 fields of the x25_config are defined as follows: Record number: The record number within the file.25 Chapter 9: X. This is described in the Installation and Configuration: OMC-R Clean Install (68P02901W47) manual. Figure 9-2 x25_config configuration file details. Any other value in this field indicates that the process listens for incoming calls. X.25 channel number: In the format x25_chann where n is the channel number.25. Each link will be associated with either an E1 channel or a HSI port. X. 9-4 68P02901W19-S Oct 2009 . Process call characteristic: The process call characteristic field.121 application address: The local X. A value of . X. The value of this field corresponds to the X. H is the only option available. Each E1 channel is associated with a specific NE.25 application process on a single HSI port.indicates that the process makes calls. 1 x25_chan1 0 2345678 H g_bootload OMC_BL X25 128 2 50 2 x25_chan2 1 87654321 H g_bootload OMC_BL X25 128 2 50 3 x25_chan3 2 6161616 H g_ei OMC_EI X25 128 2 500 4 x25_chan4 3 21312131 H g_ei OMC_EI X25 128 2 500 5 x25_chan5 2 53253232 H .OMC_PU X25 128 2 50 7 x25_chan7 1 31413141 H .25 card type: This field refers to the HSI card used in the system processor for X.121 address for an application (maximum 14 digits).

Remote Login.25 appl OMC-R service provider applications on the system processor.25 packet size to be used over connection.Operating Information: OMC-R System Administration Rules for the x25_config file Application process: X. • OMC_EI .25 is centralized into separate X.25 packet switch through the SunLink X.25 application. For redundancy purposes. not by the end users. 68P02901W19-S 9-5 Oct 2009 . Window size: Maximum X. entry 3 should be configured to use a different link/port to entry 4. • OMC_RL . OMC X. Upload. Packet size: Maximum X. For high-capacity systems. 2. This utility will be run by the OMC-R system administrator. there are two additional OMC_PU lines. Protocol: Protocol being used by a process. OMC-R system processor applications (EventInterface. For redundancy. The only valid value in this field is X25. It returns the number and type of SVCs currently open.25 interface. • OMC_PU . The x25appl applications are the only applications to interface directly to the X. 5. The x25appl applications communicate with the OMC-R applications using the Motorola IPC mechanism. Download and Rlogin) currently interface to the x25appl applications. Poll time-out: Time-out value specified in poll system call (seconds). The first and second lines are for the bootloader (incoming calls). The third and fourth lines are for the event interface (incoming calls). The additional lines are required because there are four upload channels. entry 6 should be configured to use a different link/port to entry 7.25 application design The use of X. For redundancy. The fifth line is for the remote login (outgoing calls).Upload. The x25stat utility is provided to query the status of the centralized X.Event Interface. Rules for the x25_config file Each entry is separated by a space.Bootload. 3. The sixth and seventh lines are for the uploader (outgoing calls).25 window size to be used over connection. 4. The order of entries in the file is significant and is as follows: 1. Outgoing calls are made on demand when requested by the remote login and upload applications.25 application process can be one of the following: • OMC_BL . entry 1 should be configured to use a different link/port to entry 2.

25 application design Chapter 9: X. A x25appl process is to be restarted to pick up changes made to the x25_config file. 9-6 68P02901W19-S Oct 2009 . This is not the same as stopping and starting the X. they can be restarted without restarting the whole OMC-R.25 system of the OMC-R. Refer to Restartable processes on page 2-49. that is. described in Starting and stopping X.OMC X.25 management NOTE The x25appl processes are restartable processes.25 on page 9-9.

25 commands ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Starting and stopping X.25 commands. This tool enables the user to stop and start the X.25 commands For further details of X. The start or stop commands are run using the X. refer to the Managing SunLink X.25 X. Further details of X.25 may be started or stopped on a single link.25 service. which may reconfigure a link actively.25 tool.Operating Information: OMC-R System Administration Basic X. and stop and start a single link. 68P02901W19-S 9-7 Oct 2009 .25 tool is used when updating the configuration of a link.2 manual. Procedures to start or stop a single link or the X. 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. or may be started and stopped as a service. NOTE Stopping and starting the SUN X. or store new link configuration information when the link is restarted.25 link configuration The X. without bringing down the service.25 must be fully shut down.25 service must be run as user root.25 9.25 commands Basic X. Updating X.

25 on bootup of the system processor.25 directory structure ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ The directory structure relevant to X.25 license facilities.d/S87x25net Network daemon for starting or stopping X. Table 9-1 Files and utilities for X. /opt/SUNWconn/x25/bin /x25stat Displays link statistics. /etc/rc2.25 management 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. All files and utilities are immediately under the root (/). 68P02901W19-S Oct 2009 .25 configuration and administration utility.25 configuration and maintenance on the system processor is shown in Table 9-1.d/x25. /etc/init. /etc/opt/SUNWconn/x25 /netconf Describes the configuration of the STREAMS network constructed by X25netc.25 directory structure Chapter 9: X. /etc/opt/SUNWconn/x25 /config Directory containing configuration files. /opt/SUNWconn/x25/bin /pad User interface to pad facilities. /opt/SUNWconn/x25/bin /x25info Provides useful status information.control Starts all the necessary daemons and brings up the software.X. /opt/SUNWconn/x25/bin /x25tool X. /opt/SUNWconn/x25/bin /x25trace Protocol level tracing facility. /opt/SUNWste X.

25 software.0 3 Execute the following command: cd /opt/SUNWconn/bin .2 window is displayed on the system processor as shown in Figure 9-3. for example.25. the OMC-R should be stopped as described in Manual startup and shutdown of OMC-R software on page 7-12. 9-9 Oct 2009 .25 the hardware or upgrading software./x25tool & The x25tool 9.25 Starting and stopping X. The x25tool enables the user to stop and start the X.25 ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Stopping OMC-R processes Before doing major reconfiguration on X. replacing X. Starting up the x25tool Use the following procedure to start the x25tool: Procedure 9-1 68P02901W19-S Starting the x25tool 1 Login to the system processor as user root. 2 Set the DISPLAY variable to the system processor by entering the following commands: /bin/csh cd / setenv DISPLAY omc_splat:0. Overview of the x25tool The x25tool provides a graphical interface to the parameters required to configure and maintain the SunLink X.25 service and must be run as user root.Operating Information: OMC-R System Administration Starting and stopping X.

Starting up the x25tool Figure 9-3 9-10 Chapter 9: X.2 window 68P02901W19-S Oct 2009 .25 management x25tool 9.

25 Starting X.25 software: Procedure 9-2 1 Start the x25tool as described in Starting up the x25tool on page 9-9.25 has been started.25 software X25 Message window: process started 9-11 Oct 2009 .25 Use the following procedure to start the SunLink X. The message window shown in Figure 9-4 indicates that X. 2 From the Network menu select Start X.Operating Information: OMC-R System Administration Starting X. Figure 9-4 68P02901W19-S Starting the SunLink X.25.

2 From the Network menu select Stop X.25 Chapter 9: X.25 management Stopping X. Figure 9-5 9-12 Stopping the SunLink X.25 software X25 Message window: process stopped 68P02901W19-S Oct 2009 .25 Use the following procedure to stop the SunLink X.Stopping X.25 software: Procedure 9-3 1 Start the x25tool as described in the previous section. The message window shown in Figure 9-5 indicates that the X.25 has been stopped.25.

4 Make the necessary changes.25 link.25 on page 9-9.25 parameters To update the configuration of the X. 3 Click Modify on the right side of the x25tool window. Reconfiguration is possible on the active links such that the X. Use the following procedure to configure the X. 9-13 Oct 2009 . 5 Click Apply to save the changes and close the window. as shown in Figure 9-6.25 service need not be stopped. The Link Editor window is displayed.25 link configuration Updating X.25 link requires the user to interface with the x25tool. carry out the following procedure.25 link: Procedure 9-4 68P02901W19-S Configuring X. 2 To modify an existing HSI link.25 parameters 1 Invoke the x25tool window as described in Starting and stopping X. Updating the configuration of the X. select the link in the x25tool window.Operating Information: OMC-R System Administration Updating X.25 link configuration ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Configuring X.

25 management Link editor window 68P02901W19-S Oct 2009 .Configuring X.25 parameters Figure 9-6 9-14 Chapter 9: X.

4 Make the necessary changes. 9-15 Oct 2009 . click LAPB.Operating Information: OMC-R System Administration Configuring LAPB parameters 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 1 Select the link in the x25tool window. The Link Editor window is displayed. WAN. 3 Under Advanced Configuration on the right side of the Link Editor. The LAPB and WAN Parameters window is displayed. 5 Click Apply. 2 Click Modify on the right side of the x25tool window. as shown in Figure 9-6. as shown in Figure 9-7.

Configuring LAPB parameters Figure 9-7 9-16 Chapter 9: X.25 management LAPB and WAN parameters window 68P02901W19-S Oct 2009 .

8 Power up the system.25 as described in Starting and stopping X.omcadmin: svcadm disable omc 3 Stop SunLink X. 4 Use the following commands to inform all users that maintenance to the X. 6 Power off the system processor. 2 Enter the following commands: su . 7 Remove and replace the network interface card by following the instructions in the HSI installation guide. 9-17 Oct 2009 .25 HSI card is to be carried out: wall<hit enter> System coming down immediately for vital maintenance<hit enter> ^d 5 Bring the system down to the PROM mode: /usr/sbin/shutdown -i5 -g0 -y The PROM monitor mode OK prompt is displayed.Operating Information: OMC-R System Administration Replacing the HSI card Replacing the HSI card ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Replacing the HSI card Use the following procedure to stop and start X.25 on page 9-9.25 to enable the HSI card to be replaced: Procedure 9-6 68P02901W19-S Replacing the HSI card 1 Login to the system processor as user root.

25 connectivity Chapter 9: X. 2 Check the integrity of x25 by entering the following commands as user root: /opt/SUNWconn/bin/x25stat Refer to x25stat output on page 2-76 for example.25 connectivity checklist Use the following procedure to check X. output of the netstat command. Copy the checklist provided in Table 14-8 to record the checks. Procedure 9-7 9-18 Checking X. The correct entries are required to configure x25 connections.25 management Checking X. 68P02901W19-S Oct 2009 .25 connectivity 1 Check the contents of the x25_config file by entering the following commands as user root: cd /usr/omc/config/global more x25_config The file contents should be similar to the example shown in Figure 9-2.Checking X.25 connectivity ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ X. output. 3 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.25 connectivity.

the system may restart or hang until the operator resets the machine manually.25tool to restart the X.. <09/29/05 14:26:05> X.. the operator can see output similar to the following from the X.25 : Creating link 0.25 : link 3 has been started <09/29/05 14:26:05> X. 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..25 : Creating link 3. <09/29/05 14:26:05> X.please wait <09/29/05 14:26:05> X. the X. If one of the HSI cards is out of service. the X25 software fails to start.25 recovery from HSI failure X.. 68P02901W19-S 9-19 Oct 2009 .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.25tool: <09/29/05 14:26:00> <09/29/05 14:26:05> Starting the X. <09/29/05 14:26:05> X. <09/29/05 14:26:05> X. Using the X.25 software will attempt to start up but will fail to start.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..25 : Creating link 1.25 : link 1 has been started <09/29/05 14:26:05> X.25 software..25 : link 2 has been started <09/29/05 14:26:05> X.25 : link 0 has been started <09/29/05 14:26:05> X.25 : Creating link 4... An IB module failure implies that the onboard HSI card is rendered out of service. <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).. <09/29/05 14:26:05> X.25 : Can't create level 2 for link 4 <09/29/05 14:26:06> X.25 : Creating link 2.Operating Information: OMC-R System Administration X. Even though there may be still at least one remaining working HSI card. and the X25 software is restarted or the system is rebooted.25 : failed to open driver "/dev/hihp4" : No such device <09/29/05 14:26:05> X.25 software .

The following issues may arise: • PM Statistics uploads do not swap over to the next available x25appl with a working HSI link.002) uploads will swap over to an available HSI link for the same BSS. 9-20 68P02901W19-S Oct 2009 .Issue C: OMC-R configuration to allow X25 operate using the remaining hardware Chapter 9: X. This occurs until the faulty hardware can be replaced. then the OMC-R application does not use the other available HSI links as configured in the x25_config file.25 management Issue C: OMC-R configuration to allow X25 operate using the remaining hardware When the HSI links that service statistics and uploads goes down. • BSS database (. and the second attempt will succeed on the next available x25appl. However users may have to request the upload a second time as the first request may fail.

.25tool to start the X. Continued 68P02901W19-S 9-21 Oct 2009 . X. X.Operating Information: OMC-R System Administration Recovery Recovery ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Issue A: Recovery from a Sun IB module/IO board hardware failure After the system is rebooted.25 : link 0 has been started X.. X. Use the X....25 : Creating link 3.25 : Creating link 0..25 : Creating link 2. X. X. as one of the IB modules (and hence HSI cards) is out of service then the X25 software may fail to start.25 software and view the output.25 : Creating link 1.. This corresponds to the failure of the IB8 module on a SunFire4800..25 links associated with the out-of-service IB module (HSI card)..25 : failed to open driver "/dev/hihp4" : No such device X. The sample output shown above indicates that X.25 : link 1 has been started X.please wait X. A sample output is as follows: Starting the X..25 : link 4 has been stopped The network failed to come up correctly.25 : Can't create level 2 for link 4 X.25 : link 2 has been started X. The following procedure describes how to restart the X25 software: Procedure 9-8 1 Restarting the X25 software Identify the X.25 fails to start link 4.25 : Creating link 4.25 software .25 : link 3 has been started X.

cfg.orig link_config_0007.cfg -rwxr-xr-x 1 root other 2249 Nov 16 17:08 link_config_0003.25 software.25 management Restarting the X25 software (Continued) Remove the link files associated with the failed HSI card.cfg link_config_0007. Proceed to recovery method for Issue C below to reconfigure the x25_config file.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. and the X25 software is restarted or the system is rebooted. This indicates that all the files associated with the HSI card have to be renamed as follows: mv mv mv mv link_config_0004. execute the following command to rename the corresponding link_config_000x.cfg -rwxr-xr-x 1 root other 2249 Nov 16 17:08 link_config_0001. X25 tries to use faulty ports which are still configured in the x25_config file.cfg -rwxr-xr-x 1 root other 2249 Nov 16 17:08 link_config_0004.cfg. However until the hardware is replaced.25_config file.cfg link_config_0004.orig link_config_0005. Until the HSI card is replaced. For each of the links found to be out of service in step 1.cfg.cfg link_config_0006.cfg -rwxr-xr-x 1 root other 2249 Nov 16 17:08 link_config_0005.cfg -rwxr-xr-x 1 root other 2249 Nov 16 17:08 link_config_0006.cfg -rwxr-xr-x 1 root other 2249 Nov 16 17:08 link_config_0005. follow all of the recovery steps for Issue A above to ensure that X25 software will start.orig 3 Use X.cfg -rwxr-xr-x 1 root other 2249 Nov 16 17:08 link_config_0007. 9-22 68P02901W19-S Oct 2009 .25 software. 4 Proceed to recovery method for Issue C below to reconfigure the X.cfg -rwxr-xr-x 1 root other 2249 Nov 16 17:08 link_config_0002. rename the corresponding link_config_000x.orig link_config_0006.cfg link_config_0005.cfg. to be able to start the X. Issue B: Recovery from HSI card hardware failure If one of the HSI cards is out of service.25 tool to restart the X.cfg The sample output shown above indicates that link 4 failed to start up.cfg file as follows: As user root.Issue B: Recovery from HSI card hardware failure Procedure 9-8 2 Chapter 9: X. the X25 software does not start.

In the example shown in step 1. 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 1 Editing the x25_config file As user omcadmin.orig Continued 68P02901W19-S 9-23 Oct 2009 . 6 and 7 are out of service. execute the following commands to backup the x25_config file: cd /usr/omc/config/global cp –p x25_config x25_config.OMC_RL X25 128 2 500 6 x25_chan6 1 511205 H . 3 As user omcadmin.OMC_PU X25 512 7 50 8 x25_chan8 0 511201 H g_bootload OMC_BL X25 128 2 50 9 x25_chan9 4 511201 H g_bootload OMC_BL X25 128 2 50 10 x25_chan10 0 511201 H g_bootload OMC_BL X25 128 2 50 11 x25_chan11 4 511201 H g_bootload OMC_BL X25 128 2 50 2 Determine the bad ports.Operating Information: OMC-R System Administration 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. 5. execute the following command to determine the HSI ports mapped to the different OMC applications: cd /usr/omc/config/global/ cat x25_config The following example shows a sample output where the numbers in the third column correspond to the HSI port identifier: 1 x25_chan1 0 511201 H g_bootload OMC_BL X25 128 2 50 2 x25_chan2 4 511201 H g_bootload OMC_BL X25 128 2 50 3 x25_chan3 1 511203 H g_ei OMC_EI X25 128 2 500 4 x25_chan4 5 511203 H g_ei OMC_EI X25 128 2 500 5 x25_chan5 5 511205 H . the OMC-R application does not automatically use the other available HSI links configured in the x25_config file.OMC_PU X25 512 7 50 7 x25_chan7 5 511205 H . ports 4. Use the x25 tool to determine which ports are not at NORMAL state.

OMC_PU X25 512 7 50 7 x25_chan7 1 511205 H . 5.Issue C: Recovery of OMC-R configuration to allow X25 operate using the remaining hardware Chapter 9: X.OMC_RL X25 128 2 500 6 x25_chan6 1 511205 H . stop the OMC-R using the following command: omc stop Restart the OMC-R using the following command: omc start 7 Replace the modified x25_config file with the original copy. 8 Move all the link files renamed during the recovery method. 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.OMC_PU X25 512 7 50 8 x25_chan8 0 511201 H g_bootload OMC_BL X25 128 2 50 9 x25_chan9 0 511201 H g_bootload OMC_BL X25 128 2 50 10 x25_chan10 0 511201 H g_bootload OMC_BL X25 128 2 50 11 x25_chan11 0 511201 H g_bootload OMC_BL X25 128 2 50 9-24 5 Once the above changes have been made to the x25_config file. 68P02901W19-S Oct 2009 . 6 and 7 from the x25_config file and save the file. restart x25 software using x25 tool. The following output shows the x25_config file: 1 x25_chan1 0 511201 H g_bootload OMC_BL X25 128 2 50 2 x25_chan2 0 511201 H g_bootload OMC_BL X25 128 2 50 3 x25_chan3 1 511203 H g_ei OMC_EI X25 128 2 500 4 x25_chan4 1 511203 H g_ei OMC_EI X25 128 2 500 5 x25_chan5 1 511205 H .25 management Procedure 9-9 4 Editing the x25_config file (Continued) As user omcadmin. Delete references to ports 4. 6 As user omcadmin.

Chapter 10 OMC Utilities ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 68P02901W19-S Oct 2009 10-1 .

Operation and maintenance utilities

Chapter 10: OMC Utilities

Operation and maintenance utilities

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 CTRL–c while any of the scripts are executing and allow all scripts to
complete execution once they are started.

Operation and maintenance utilities
The utilities provided are listed in Table 10-1. They are described in detail in the following
sections.

10-2

68P02901W19-S
Oct 2009

Operating Information: OMC-R System Administration

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

Chapter 10: OMC Utilities

Installation
Adding operation and maintenance utilities package
Check whether the OMC utilities package is already installed by executing the following
command as user root:
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
commands as user root:
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

Operating Information: OMC-R System Administration

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

Chapter 10: OMC Utilities

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

Operating Information: OMC-R System Administration

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

Chapter 10: OMC Utilities

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

0

laurel

1600d2_test

rfd6rfd6 001-01-1-4

40

0

laurel

1600d2_test

rfd6rfd6 001-01-1-4

50

1

somc_cust

D1_BSS_1002

D1_BSS_1002:SITE-0:

001-01-1-2 60 0

0

somc_cust

D1_BSS_1002

D1_BSS_1002:SITE-0

001-01-1-4 40

0

Enter the pattern - part of cellid or site name or BSC name
Or ’q’ to quit

10-8

68P02901W19-S
Oct 2009

Operating Information: OMC-R System Administration

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.

All users have the ability to use this utility.
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

Chapter 10: OMC Utilities

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

1

BSS-1006

BSS-1006:SITE-4:

001-01-1-41

4

BSS-1006

BSS-1006:SITE-4:

035-02-04-0

4

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

Operating Information: OMC-R System Administration

net_reports

Site Name and RTF
_________________
BSC

SITE NAME

CELLID

ARFCN

TYPE

BSS-1006

BSS-1006:SITE-4:

001-01-1-41

90

0

1600d2_test

1600d2_test:SITE-1:

001-01-1-1

25

0

1600d2_test

1600d2_test:SITE-1:

001-01-1-6

75

0

1600d2_test

1600d2_test:SITE-1:

001-01-1-6

85

1

Site Cell and BSIC
_______________
BSC

SITE

CELLID

BSIC

BSS-1006

BSS-1006:SITE-1:

035-02-1-0

0

BSS-1006

BSS-1006:SITE-4:

001-01-1-41

16

BSS-1006

BSS-1006:SITE-4:

035-02-0-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

Chapter 10: OMC Utilities

Name & GSM Cell ID & Location: Region: Region1
______________________________________
BSC

SITE

Cell ID

Location

BSS-1006

BSS-1006:SITE-1:

035-02-1-0

1

BSS-1006

BSS-1006:SITE-4:

001-01-1-41

4

BSS-1006

BSS-1006:SITE-4:

035-02-0-0

4

Site Name and RTF: Region: Region1
______________________________
BSC

SITE NAME

CELLID

ARFCN

TYPE

BSS-1006

BSS-1006:SITE-4:

001-01-1-41

90

0

1600d2_test

1600d2_test:SITE-1: 001-01-1-1

25

0

1600d2_test

1600d2_test:SITE-1: 01-01-1-6

75

0

1600d2_test

1600d2_test:SITE-1: 001-01-1-6

85

1

Site Cell and BSIC: Region: Region1
_____________________________

10-12

BSC

SITE

CELLID

BSIC

BSS-1006

BSS-1006:SITE-1:

035-02-1-0

0

BSS-1006

BSS-1006:SITE-4:

001-01-1-41

16

BSS-1006

BSS-1006:SITE-4:

035-02-0-0

0

1600d2_test

rfd6rfd6

001-01-1-2

68P02901W19-S
Oct 2009

Operating Information: OMC-R System Administration

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.

All users have the ability to use this utility.

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

00000 68P02901W19-S Oct 2009 .00000 1600d2_test 1600d2_test:SITE-1: 0 0 0 0 1998-12-16 17:14:12.00000 0 1 0 0 SITE-10: BSS1018 BSS1018: 1 1 0 0 SITE-11: 10-14 2005-05-13 17:22:04.00000 1 1 0 0 2005-05-13 1 7:22:06.00000 SITE-10: BSS1018 BSS1018: 2005-05-13 2005-05-13 17:22:06.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 3 0 0 2005-06-16 0 SITE-75: BSS1018 BSS1018: 12:29:54.dri_status Chapter 10: OMC Utilities 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: 1 1 0 0 1999-02-10 10:46:05.00000 0 1 0 0 SITE-11: BSS1018 BSS1018: 2005-05-13 17:22:05.00000 0 0 0 0 SITE-10: BSS1018 BSS1018: 17:22:05.

All users have the ability to use this utility. Usage rtf_status [ -c directory] The option available is: -c directory Name of the directory where the output is to be stored.Operating Information: OMC-R System Administration rtf_status rtf_status This utility enables the user to generate a list of the RTFs which are OOS on a single OMC only. If -c is not used. The user can generate a report for individual OMCs. using batch_rlogin scripts. It is only run on a single OMC. The user can display the output on their terminal and save the file to /tmp or to a user defined directory. the default directory is /tmp. Input laurel:omcadmin > rtf_status –c /home/omcadmin Output This utility generates RTF Device Status information. NOTE The rtf_status utility uses batch_rlogin. Only users with BSS Remote Login privileges should have access to this utility. 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 .

Number of Matched Outages. StartTime and EndTime should be entered in the format HHMMSS. The user can generate a report for a single OMC or all OMCs in the Network. Even if the -b option has been used. Start Time. NOTE Unmatched Critical and Clear Alarms can distort the data. 10-16 68P02901W19-S Oct 2009 .lst. The default is All. If -c is not used. -c directory Name of the directory where the output is to be stored. If neither -d nor -e is used. the default directory is /tmp. the input from -f takes preference. Outage Time. the default is the OMCs in omc. site_outage is being run from. -d Produces a detailed report showing: Site. End Date. If no date or time is entered. All users have the ability to use this utility. The occurrence of these alarms is identified by the utility. This option is used to display the report to the user. -l Produces a list of OMCs in the network from which the user must select one. then both detailed and summarized report is generated. Produces a report for OMCname. % OOS Duration Per Period. Start Date. Even if the -a option has been used. the default will be the previous 24 hours. If -b is not used. -b OMCname OMCname is an OMC.site_outage Chapter 10: OMC Utilities 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. End Time and Outage Time. StartDate and EndDate StartDate and EndDate should be entered in the format yyyymmdd. -e Produces a summarized report showing: Site. Alarms Unmatched and Clears Unmatched. -f Prompts the user to enter the IP address of the terminal. the input from -l take preference. site_outage run from. 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.

.21619 NOTE To view all data in the report.3 Alarms Clears Unmatched Unmatched 0 1 10-17 Oct 2009 .. Close Reports or Control C to exit. Output OMC laurel Detailed 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 1 0... maximize the output window.. Retrieving information from OMC laurel The reports are being generated Please Wait ..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 . Detailed report is in /tmp/SiteDetail..21619 Summary report is in /tmp/SiteSummary.Operating Information: OMC-R System Administration site_outage Input laurel:omcadmin > site_outage Please Wait ..

Only the users with BSS Remote Login privileges should have access to this utility. enter 'p' (proceed with add_nei) To quit: enter 'q' 68P02901W19-S Oct 2009 . the OMC administrator can modify these files. both ways. 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. The user should ensure that these values are appropriate to the network. Where necessary. NOTE The add_nei utility uses batch_rlogin.add_nei Chapter 10: OMC Utilities add_nei This utility enables the user to add neighbors both ways. regardless of the OMC on which they reside. 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. Template files This utility uses pre-defined files containing default values. Only the omcadmin or Configuration Management experts should have the ability to use this utility. using batch_rlogin. and make the updates appropriately.

. Input laurel:omcadmin > del_nei — — — — — — — — — — — — — — — — — — — — — — — — — — del_nei will delete neighbors. both ways.. NOTE The del_nei utility uses 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’ N Now collecting ARFCNs and BSICs for RFPlan. somc12.. enter ’p’ (proceed with del_nei) To quit: enter ’q’ 68P02901W19-S 242-53512) 10-19 Oct 2009 . To input Source Cell: enter ’LAC-CI’ (for example: If sources now input. laurel...Operating Information: OMC-R System Administration 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. using batch_rlogin. Only the omcadmin or Configuration Management experts should have the ability to use this utility.. regardless of the OMC on which they reside. Only the users with BSS Remote Login privileges should have access to this utility.

Only the omcadmin or Configuration Management experts should have the ability to use this utility.in Enter Control C to Quit window. _______________________________ Generating the discrepancies in the OMC Completed.nei_sync Chapter 10: OMC Utilities 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. 10-20 68P02901W19-S Oct 2009 . Only the users with knowledge of the cmutil operation should use this utility. 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. Input laurel:omcadmin > nei_sync Output This script is to find out and correct the discrepancies in the bsic and bcch of neighbours. NOTE The nei_sync utility requires the use of cmutil.

Output in /usr/omc/current/sbin/udata/proxygen.. somc18.. laurel.. Now collecting BSICs. Processing ...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. laurel...Operating Information: OMC-R System Administration proxy_sync proxy_sync This utility enables the user to generate a list of required Proxy Cells and add them to an OMC..Generating BCCH and BSIC of proxies . Putting the proxycells in cmutil format. reparent_site This utility enables the user to reparent a site from BSS to BSS and across OMCs.. 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..op Number of proxycells for this OMC = 0 Running cmutil to add the new proxies .. 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. 68P02901W19-S 10-21 Oct 2009 .. somc18.. Only the users with knowledge of the cmutil operation should use this utility.

Retrieving Network-entities/containment. Input laurel:omcadmin > reparent_site BSS1017:SITE-8: BSS_1016 Performing the necessary checks for reparent_site Checking that the links are disconnected. . <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. Getting the list of OMCs on the network.inp Hierarchical extraction of BSS1017:SITE-8: in progress .. . Deleting a SITE Creating input file BSS1017:SITE-8:. Hierarchical extraction of BSS1017:SITE-8: completed The deletion will fail if any of the forms for the objects are open for edit. Locating the BSS on which BSS1017:SITE-8: resides. Press Return if you do not want the LAC to change. <RETURN> The RDN instance is unchanged Gathering a list of cells which will be created as proxy cells. Deleting Network-entities/containment. anything else will abort operation: Y 10-22 68P02901W19-S Oct 2009 . <RETURN> The site name is now BSS1017:SITE-8: Enter the LAC that the site will be given on the new BSS. . . Extracting the Site information Deleting site BSS1017:SITE-8: Verifying Network-entities/containment.reparent_site Chapter 10: OMC Utilities Only the omcadmin or Configuration Management experts should have the ability to use this utility. Please ensure this is not the case and will not be at any time while this script is running. Press Return if you do not want the RDN to change. Enter the name that the site will be given on the new BSS Press Return if you do not want the name to change.. Locating OMC on which BSS_1016 resides. Type “Y” to proceed. .

Operating Information: OMC-R System Administration 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: 0 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 . All users have the ability to use this utility.

ne_counter Chapter 10: OMC Utilities 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 .

otherwise the full path should be given.Operating Information: OMC-R System Administration 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. Table 10-2 OMC utilities: recommended execution mechanisms Utility Recommended execution finder Command line/Tools/CDE net_reports Command line/Tools/CDE dri_status Command line/Tools/CDE/cron rtf_status Command line/Tools/CDE/cron site_outage Command line/Tools/CDE/cron 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 Command line/Tools/CDE These utilities can be invoked on a Client machine when remotely logged in to the OMC System Processor. If /usr/omc/current/sbin is in the user’s PATH. The following table lists the recommended execution mechanisms. allow all the scripts to complete execution once they are started. Command line CAUTION Do not execute a CTRL–C while any of the scripts are executing. only the utility name is required. for example: dri_status –r Region1 or 68P02901W19-S 10-25 Oct 2009 . The utilities are contained in /usr/omc/current/sbin and can be invoked from the command line by typing the utility’s name and the appropriate options.

exec “/usr/dt/bin/dtterm -title Network_Reports -e rsh omc_splat /usr/omc/current/sbin/net_reports” Alternatively.separator ### # # Utilities sub-menu description # ### Menu OMC_GEN_utils { ”DRI Status” f.menu OMC_GEN_utils no-label 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 . execute the following commands as omcadmin: cd /usr/omc/current/env vi .separator Network Reports f.exec “/usr/dt/bin/dtterm -title Dri_Status-e rsh omc_splat /usr/omc/current/sbin/dri_status -f” no-label f.exec ”/usr/dt/bin/dtterm -title DRI_Status -e rsh omc_splat /usr/omc/current/sbin/dri_status -f ” “SITE Status” f.separator DRI Status f.cron and at Chapter 10: OMC Utilities /usr/omc/current/sbin/dri_status –r Region1 cron and at The utilities can be executed using cron and/or at.separator OMC General Utilities f. This file is located in: /usr/omc/current/sbin/udata CDE menu To add a utility to the CDE menu.dtwmrc Add the following to the Right Menu Description: no-label f. create a separate sub-menu list: no-label f. A sample cron file (utilities_cron) is provided.

such as HierDelete and cmutil. NOTE This script should be run on machines during periods when there is no MIB activity. and then to re-audit in the affected site. use the –r parameter. • Relationship corruptions – incorrect. The inconsistencies. the script can be run in cleanup mode. depending on the setting of the environment variable LOG_TO_USRAUDIT. • To execute in Cleanup Mode.Operating Information: OMC-R System Administration cleanMib cleanMib ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Introduction The cleanMib script replaces the MIBCleanup script. Type the following commands in the xterm: cleanMib –r or cleanMib –c 68P02901W19-S Oct 2009 10-27 . The cleanMib script should be run in report mode first. If orphans are detected. on a stable MIB. and also cause the cmMib process to exit. Open an xterm from the Single Platform Processor. Running cleanMib The script may be executed in two different modes: • To execute in Report Mode. The inconsistency report can be examined and if any inconsistencies are found. if found. These types of corruptions to prevent the success of some MIB actions. The inconsistencies are also logged to a cleanMib logfile in /usr/omc/logs. • Invalid DN corruptions – objects with NULL DN strings. The cleanMib detects or repairs the following types of database corruption: • Orphan corruptions – objects with invalid or missing parent objects. then it is recommended that HierDelete is executed on the affected site after the cleanMib script has been run in cleanup mode. are written to the omcaudit logfile or usraudit logfile. use the –c parameter. duplicate or missing relationships. The cleanMib script searches for corruptions in the MIB database and fixes them.

Running cleanMib 10-28 Chapter 10: OMC Utilities 68P02901W19-S Oct 2009 .

Chapter 11 Network Information Services (NIS) ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 68P02901W19-S Oct 2009 11-1 .

However. However. The use of NIS allows a task. The following topics are described in this chapter: 11-2 • NIS normal operation on page 11-3. • Changing user/group/host information on page 11-8. that previously would have been performed on the network. to be performed on the central administration system. Motorola does not provide documentation or support for alternative naming services on the OMC-R. • NIS files and utilities on page 11-5. only a master server (the system processor) and clients are used. Network Information Services (NIS) is a distributed naming service from Solaris. it is possible to configure an alternative naming service on the OMC-R. the purpose of which is to ease the administration of computing environments comprising different machines.Overview Chapter 11: Network Information Services (NIS) Overview ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ NOTE NIS is configured as the default naming service in the OMC-R environment. in the OMC-R environment. The NIS feature uses the concept of a master server and optional replicated server(s) and client machines. 68P02901W19-S Oct 2009 .

a system must belong to the NIS domain. All systems share a common set of maps. Domain The NIS domain is a collection of systems using the same NIS database. the default OMC-R domain is called omcadmin. 68P02901W19-S 11-3 Oct 2009 . The NIS client runs processes that request data from the maps on the NIS servers. NOTE If more than one OMC-R system is connected to the same LAN.Operating Information: OMC-R System Administration NIS normal operation NIS normal operation ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ This section contains a glossary of the various terms used within the normal NIS environment. A client can also act as a server. The NIS server is a machine storing a set of maps which are available to network hosts such as clients. Each domain has a unique name. Map All maps except /etc/mail/aliases are stored in /var/yp/<domainname> on the system processor. each OMC-R must have a unique NIS domain name. Servers and clients Because the network is database-oriented. for example. To participate in NIS. A server can also act as a client. The file /etc/mail/aliases must always be stored in /etc/mail (/etc/aliases is a hard link to /etc/mail/aliases). system machines are arranged in two categories: servers and clients.

11-4 68P02901W19-S Oct 2009 . Propagation Propagation is the process by which a master server updates the data in slave servers with new information entered in its own database. relative because a server can be a master for one system database and a slave for another system database. A slave holds a copy of this database and serves as a backup for the database.Masters and slaves Chapter 11: Network Information Services (NIS) 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. Propagation therefore ensures consistency of database information. The terms master and slaves are however.

• ypxfrd The ypxfrd daemon is a service that transfers complete NIS maps efficiently. This daemon only runs on NIS server machines that have a complete NIS database. The daemon must run on every machine that has the NIS client process.Operating Information: OMC-R System Administration NIS files and utilities NIS files and utilities ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ The NIS service is composed of the following elements.yppasswd daemon is a service that modifies the NIS password map.yppasswd The rpc. The daemon changes the network password associated with a particular user in the NIS database. Here are some of the NIS daemons: • ypserv The ypserv is a daemon typically activated at system startup. 68P02901W19-S 11-5 Oct 2009 . • ypbind The ypbind is a daemon service typically activated at system startup. NOTE Binding is a process that remembers the address at which the server daemon was listening for requests. This daemon should be run on a master server. some of which are part of the Solaris distribution: Daemons Daemons are important to the functionality of the operating system. • rpc. Daemons are programs that run in the background to manage certain system functions. The prime function of the ypserv daemon is to look up maps in its local database of maps. This daemon remembers all information that lets all NIS client processes on a node communicate with some NIS server process. 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.

• ypmatch The ypmatch command prints the values associated with one or more keys from the NIS name services map specified by the map name. The command is run only on the master server by the Make file in /var/yp. • makedbm The makedbm command creates DBM files for the NIS map. that supplies the NIS name service to the NIS client or that is the master for a map. 11-6 68P02901W19-S Oct 2009 . after the master databases are changed. • ypxfr The ypxfr command moves the NIS map in the default domain from a master server to a slave server. • yppoll The yppoll command returns the order number of a ypserv process and the master server for the named map. • ypset The ypset command points the daemon ypbind to a particular server.Utilities Chapter 11: Network Information Services (NIS) 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. Auxiliary utilities • yppush The yppush utility copies a new version of the NIS map from a master NIS server to the slave NIS servers. • ypwhich The ypwhich command returns the name of the server.

home 68P02901W19-S 11-7 Oct 2009 .Operating Information: OMC-R System Administration 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.

if configured. Illegal characters are: !“£$%^&*(){}~@?>:<| . If there is no entry for the user in the /etc/passwd map.Changing user/group/host information Chapter 11: Network Information Services (NIS) Changing user/group/host information ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Recommended method The recommended method of changing user or. digits and minus signs (-). 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. verify that the user exists in the /etc/passwd map. Refer to the set of procedures in the section Administering group accounts with usertool on page 2-8. The NIS must then be updated to allow the changes to be propagated throughout the network. Letters must be lower case. If a user is not being recognized on a machine. one must be created in /etc/passwd and /etc/shadow files. Changing host name NOTE A host name must be at least two characters: it can contain letters. NOTE This method is highly recommended because it updates the NIS automatically. >!]. 11-8 68P02901W19-S Oct 2009 . – group information is using the OMC_Sync script to invoke the user tool utility.

If a group is not being recognized on a machine. The NIS must then be updated to allow the changes to be propagated throughout the network.Operating Information: OMC-R System Administration Procedure 11-1 Adding a new group to the NIS domain Adding a new user to the NIS domain from the command line 1 Login to the system processor as user root. 3 Update the password map by entering the following commands: cd /var/yp /usr/ccs/bin/make passwd 4 Execute the following command to set the NIS password: yppasswd <newusername> where <newusername> is passed as a parameter. If there is no entry for the user in the /etc/group/etc/passwd map. Procedure 11-2 Adding a new group to the NIS domain from the command line 1 Login to the system as root. 2 Use the groupadd utility to add the user entry to the /etc/passwd. Enter the following command: useradd usrID NOTE The useradd utility only adds a user to the local system. Enter the following command: groupadd grpID Continued 68P02901W19-S 11-9 Oct 2009 . NOTE The length of the username parameter is restricted to eight characters. 2 Use the useradd utility to add the user entry to the /etc/passwd and /etc/shadow files. Adding a new group to the NIS domain Use the following procedure to add a new group to the NIS domain from the command line. It cannot be used to change information supplied by the NIS name service. 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. one must be created in the /etc/group file. verify that the group exists in the /etc/group/etc/passwd map.

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. 11-10 68P02901W19-S Oct 2009 . NIS server checks Check that the ypserv daemon is running on the NIS server by executing the following command. If this is not the case and the nsswitch. The first column contains the name of the map. 3 Update the group map by entering the following commands: cd /var/yp /usr/ccs/bin/make group nsswitch. The second column contains the method.conf file is set to files. The template nsswitch files are /etc/nsswitch.files.conf The nsswitch. if the file had the following entries the system looks for host information through NIS. • networks:files.conf file is a configuration file for the name service switch. and network information through the local file. 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. 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. In its basic format. The file controls whether the system looks at NIS or files. the file contains two columns. it cannot be used to change information supplied by the NIS name service.conf Chapter 11: Network Information Services (NIS) 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. as user root on the NIS server: ps -elf | grep ypserv If the daemon is running. • hosts:nis.nis and /etc/nsswitch.nsswitch. For example.30/usr/lib /netsvc/yp/ypserv If the daemon is not running.

ypmatch fkey mapname This command matches a key with an entry in a map. the hosts file to add a new host). 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. 2 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. Updating the NIS maps manually Use the following procedure to update NIS files manually: Procedure 11-3 Updating the NIS maps manually 1 Edit the file (for example. ypwhich -m This command gives a list of all the available maps and their masters. modify or delete users. 68P02901W19-S Oct 2009 Description 11-11 . ypcat map_or_alias_name This command shows the contents of the NIS files. 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.Operating Information: OMC-R System Administration Updating the NIS maps manually NOTE The domain name is generally set to omcadmin. groups or hosts. NIS troubleshooting commands The following commands can be used for troubleshooting purposes. ypcat -x This command gives a list of all the map nicknames. ypwhich -m mapname This command lists the master server for a particular map.

NIS troubleshooting commands 11-12 Chapter 11: Network Information Services (NIS) 68P02901W19-S Oct 2009 .

Chapter 12 Backup Server Installation and Configuration ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 68P02901W19-S Oct 2009 12-1 .

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

the hard disk is a focal point of failure because of the constantly moving parts. 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. If the data on that disk is not recoverable. New groups can be set up although the default group setup is sufficient. • Client configuration A client is the host which is required to be backed up. However. there are several methods of recovering the system. as it needs to be a client to perform the backups of itself. The clients can be configured to use the groups. it is recommended to check that the device has been installed correctly. 68P02901W19-S 12-3 Oct 2009 . If there is data on the disk which is easily recoverable. Although this rarely happens. This also includes the server. It gives the details of the complete and incremental backups performed and also when these are overridden.Operating Information: OMC-R System Administration 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. • Schedule configuration The schedule configuration is an important part of the backup configuration. • Group configuration Group configuration specifies when a backup is running and has control of clients within the group. • 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. it can be copied onto the new disk.

When restoring the GUI processor. Legato Informix Module License (For each client): A Legato Informix Module license is needed for Backup of the Informix Databases on the Server. Software Licenses EBS Network Edition License: EBS Network Edition License file is needed for the backups of the GSM OMC-R Server. 12-4 68P02901W19-S Oct 2009 . When restoring the system processor. nwrecover is always called from the system processor.Software Installation Chapter 12: Backup Server Installation and Configuration Software Installation ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ The StorEdge Enterprise Backup software is delivered on the GSR9 1. The Legato Informix Module license is supplied by Motorola and can be installed on the Single Platform Processor.9.lib /var/install/lib cp /cdrom/cdrom0/suninstall/data/package_list \ /var/install/data cp /var/install/backup/tape-mgr /var/install/bin 2 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.0. License file is supplied by Motorola and can be installed on the GSM OMC-R. nwrecover is always called from the GUI processor. the Administration GUI utility is always called from the system processor.0. To install the software.X Additional OMC Software DVDROM. perform the following tasks as user root: Procedure 12-1 Installing the Backup Server software 1 Execute the following commands as user root: {34618} cp –rp /cdrom/cdrom0/suninstall/backup /var/install cp /cdrom/cdrom0/suninstall/lib/backup.

68P02901W19-S 12-5 Oct 2009 . you can enter n (and the software will work for 30 days) or enter y if you have purchased a license code. Unix Client are required on the Backup Server. 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. 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. 2 Execute the following command as user root: /var/install/backup/setup_backup_server.Operating Information: OMC-R System Administration 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. 7 If the Bootstrap is already configured. Otherwise follow Procedure 12-4to configure it. the default is valid). select Quit. 6 To Do you wish to configure the licensing information …. 4 Select correct Device Media Type for your tape drive. 8 The script returns to the Main Menu. 5 Enter a name to use for the tape and it will be labelled and mounted. then do not reconfigure it.sh 3 Select Option 1.

refer Configuring Bootstrap Notification through E-mail on page 12-6. 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. Bootstrap copied to local file Enter option: 2 If Option 1 is selected. requesting confirmation of the enabler code. an ERROR message is followed by the message given below: Do you wish to enter another license enabler code (y|n) (default:n)? 4 If another Enabler Code is to be entered. Select Delivery Option: 1. otherwise enter n to continue to the Bootstrap Notification Configuration. Output like the following is displayed: ** BOOTSTRAP CONFIGURATION Bootstrap Information is required to allow for a fast recovery. follow these steps: Procedure 12-4 1 Bootstrap Notification Configuration Bootstrap information will then need to be configured. Output like the following is displayed: Enter enabler code for license: 3 Enter the Enabler Code. Bootstrap via e-mail 2. enter y. If Option 2 is selected. Enter Yes (case-sensitive) to accept the Enabler Code.Configuring Bootstrap Notifications Procedure 12-3 1 Chapter 12: Backup Server Installation and Configuration 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 2 Select y to configure the license for the Sun StorEdge Enterprise Backup Server Software. A message is displayed. Configuring Bootstrap Notifications To configure the Bootstrap notifications. follow these steps: 12-6 68P02901W19-S Oct 2009 . If the Enabler code is invalid/incorrect.

Operating Information: OMC-R System Administration Configuring Bootstrap Notification to local file NOTE For email notifications to operate. Configuring Bootstrap Notification to local file To configure the Bootstrap notifications to local file. A message like the following is displayed: Option "1: Bootstrap via e-mail" selected Enter e-mail address: 2 Enter the E-mail address. 4 Bootstrap notification is setup. A prompt requesting a confirmation on the E-mail address entered is displayed. 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. 12-7 Oct 2009 . a mailhost must be configured in /etc/hosts or DBS on the Backup Server. Data recovery takes considerably long time if this information is unavailable. 3 Enter Yes (case-sensitive) to continue. follow these steps: CAUTION It is important that a copy of the bootstrap notification file is available to allow for a fast recovery. • Copy the file to a remote location in case a restore needs to take place. The recommendations are to: 68P02901W19-S • Print a copy of the file and place it in the system folder.

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. 4 Bootstrap notification will be setup. 3 Enter Yes (case-sensitive) to continue. 1. Quit Enter Option: 5 12-8 68P02901W19-S Oct 2009 . A message similar to the following is displayed: Option "2.Configuring Bootstrap Notification to local file Procedure 12-6 1 Chapter 12: Backup Server Installation and Configuration Bootstrap Notification to local file Configuration Select Option 2 to automatically configure Bootstrap Notifications to be stored locally in a file. Delete Backup Client 5. Add Backup Client 3. /bootstrap/bootstrap.txt). Update Backup Client 4. Initialize Backup Server 2. 5 Select option 5 to quit the setup program. A prompt requesting a confirmation on the file entered is displayed.

10 Generic January 2005 logout Creating /usr/informix/etc/ixbar.10 Generic January 2005 logout 6 68P02901W19-S Execute the following command as user root: svcadm enable omc 12-9 Oct 2009 . 5 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. 3 Select y to continue. If there is no need to restore the database logical logs. Logical log backups are necessary to recover recent database updates. SunOS 5.Operating Information: OMC-R System Administration 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 1 Execute the following command as user root: /usr/omc/sbin/Configure_Informix 2 Execute the following command as user root: svcadm disable omc pkill nameserver /usr/omc/sbin/configure_solstice NOTE This step causes an OMC outage.1 for CM Database Instance Sun Microsystems Inc. 4 Select y to back up logical logs. select n.2 for PM Database Instance Sun Microsystems Inc. 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. 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. SunOS 5.

and Informix_IX2. Enabling or Disabling a Group Backup Once the backup clients are added. The crontab entries are automatically created by the /usr/omc/sbin/configure_solstice script. 5 Once all the backup clients have been created. and it is disabled. the default group's start time is 3:33.sh 2 Select option 2 to add a backup client. NOTE Once a client is registered with the Backup Server. For the SPLAT. Informix_IX2 4 If there is a GUI server. Informix_PM 4. 3 Enter the hostname of the system to be backed up. 2. before enabling or disabling a backup client. Select the option number corresponding to the client to be created. Informix_IX1. The times are as follows: • Default group runs at 01:30 Daily. select option 5 to exit the script. NOTE Ensure that the backup client belonging to the backup group exists. Follow Procedure 12-9 to enable or disable a Group Backup client. Informix_IX1 5.Completing backup server setup Chapter 12: Backup Server Installation and Configuration Completing backup server setup Follow Procedure 12-8 to set up backup clients. create each of the following client types by repeatedly selecting option 2 to add a client. such as. Informix_CM.cfg. Procedure 12-8 Completing backup server setup 1 Execute the following command as user root: /var/install/backup/setup_backup_server. Informix_PM. the backup groups are enabled or disabled according to the default settings in the configuration file /var/install/backup/backup_set. it is automatically setup to backup to the Backup Server at a time designated by that group. enter the name of the GUI server and select GUI_SERVER as the server type. 12-10 68P02901W19-S Oct 2009 . There are several backup client types. • Informix ixbar files groups run at 03:40 Daily. Informix_CM 3. Backups of Informix databases are controlled by a crontab entry. After the backup server is configured.

before deleting a backup client. displays the following message: There is a cron job set defaultly for INFORMIX_CM & INFORMIX_PM backup. 68P02901W19-S 12-11 Oct 2009 . 4 Select the option number of the backup client. To disable the group. 3 Select the hostname of the system from the machine list. NOTE Ensure that the backup client exists.. 6 Select option 5 to exit the script. Selecting the backup client as Informix_CM or Informix_PM. NOTE The group backup for the clients Informix_CM and Informix_PM is disabled by default. enter d. Deleting a Group Backup client Follow Procedure 12-10 to delete a 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.sh 2 Select option 3 to update a backup client..Operating Information: OMC-R System Administration Procedure 12-9 Deleting a Group Backup client Enabling or Disabling a Group Backup client 1 Execute the following command as user root: /var/install/backup/setup_backup_server. 5 Repeat step 2 to step 4 to update all the backup clients. enter e. So NSR group INFORMIX_CM or INFORMIX_PM is not permitted to enable auto start! Quit updating.

4 Select the option number of the backup client.sh 2 Select option 4 to delete a backup client. the backup of all clients in the backup group starts. to quit the GUI interface. 6 If you want to perform an incremental backup instead of a full backup. Please see group completion details for more information. select Default. When the backup is complete. 5 Repeat step 2 to step 4 for all the backup clients to be deleted. 7 Press Esc and select Yes to apply the changes. 4 Click Next until the name of the group is the desired group (for example. 1 Succeeded with warning(s). then both will be backed up in parallel. 8 Select Quit. type visual and a GUI is displayed. 9 Type quit. INFORMIX_IX2). Total 1 client(s). Once the changes have been applied. (For all file systems. May 16 05:30:26 zuk14omc11 root: Sun StorEdge(TM) Enterprise Backup savegroup: (notice) Default completed. to quit nsradmin. 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. the following message gets displayed on the screen. change the value of the option force incremental to yes. If there are two clients in the PM Backup group.) 5 Select Edit and change autostart to Start Now. 3 Select the hostname of the system from the machine list. 6 Select option 5 to exit the script. 3 Click Select and NSR Group. 12-12 68P02901W19-S Oct 2009 .Manually starting a Group Backup Procedure 12-10 Chapter 12: Backup Server Installation and Configuration Deleting a backup client 1 Execute the following command as user root: /var/install/backup/setup_backup_server. Procedure 12-11 Enable backups {34618} 1 Execute the following command as user root: nsradmin 2 At the nsradmin> prompt.

Table 12-2 Log files produced by client machines Log Type Log File Location Backup Logfiles /usr/omc/logs/bar_mib.1 and ixbar.2 For example: cp ixbar.log /usr/omc/logs/bar_omc.2.<most recent date> ixbar. 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. as shown in the following commands.122546 ixbar.1 cp ixbar.log Backup Status Logfiles /nsr/logs Manual backup of Informix databases Procedure 12-12 Full Backup of Informix databases {34618} 1 To setup the ixbar files.1.1 Continued 68P02901W19-S 12-13 Oct 2009 .1.<most recent date> ixbar. execute the following commands as user Informix: cd /usr/informix/etc (If there are no ixbar.) cp ixbar.2 in this directory. produce them by copying the latest version from files taken as backup.Operating Information: OMC-R System Administration Manual backup of Informix databases Log files (Backup server) The log files produced by the backup are located in the following directory.2006109.

2009-05-07 23:17:09 13310 13308 Begin level 1 backup mib_db_sp1. the backup succeeded: 2009-05-07 23:17:07 13310 13308 Completed level 1 backup rootdbs (Storage Manager copy ID: 1241709427 1241709428). 13308 Successfully connected to 2009-05-07 23:17:11 13310 13308 Completed backup logical log 25 (Storage Manager copy ID: 1241709431 1241709432). 2009-05-07 23:17:08 13310 13308 Completed level 1 backup logsdbs (Storage Manager copy ID: 1241709428 1241709430). mib_db_sp1 Completed (Requested Level 1).Manual backup of Informix databases Procedure 12-12 2 Chapter 12: Backup Server Installation and Configuration 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. 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. 2009-05-07 23:17:11 13325 13323 /usr/informix/bin/onbar_d -b -l 2009-05-07 23:17:11 13325 returning 0 (0x00) 13323 /usr/informix/bin/onbar_d complete. Continued 12-14 68P02901W19-S Oct 2009 . Can't start another. logsdbs. 2009-05-07 23:17:09 13310 13308 Completed level 1 backup physdbs (Storage Manager copy ID: 1241709429 1241709432). 2009-05-07 23:17:07 13310 13308 Begin level 1 backup logsdbs. 2009-05-07 23:17:10 13310 Storage Manager. 2009-05-07 23:17:10 13310 13308 Completed level 1 backup mib_db_sp1 (Storage Manager copy ID: 1241709430 1241709434). 2009-05-07 23:17:10 13310 13308 Archive on rootdbs. 2009-05-07 23:17:09 13310 13308 Begin level 1 backup physdbs. physdbs.

omc_db_sp11. 4 68P02901W19-S 2009-05-07 23:18:31 13391 13389 /usr/informix/bin/onbar_d -b -l 2009-05-07 23:18:31 13391 returning 0 (0x00) 13389 /usr/informix/bin/onbar_d complete. 2009-05-07 23:18:31 13358 13356 Completed backup logical log 23 (Storage Manager copy ID: 1241709510 1241709511). 2009-05-07 23:18:29 13358 13356 Completed level 1 backup omc_db_sp9 (Storage Manager copy ID: 1241709509 1241709524). 2009-05-07 23:18:27 13358 13356 Begin level 1 backup omc_db_sp8. omc_db_sp3. omc_db_sp5. 2009-05-07 23:18:27 13358 13356 Completed level 1 backup omc_db_sp7 (Storage Manager copy ID: 1241709507 1241709520). omc_db_sp7. 12-15 Oct 2009 . 2009-05-07 23:18:26 13358 13356 Begin level 1 backup omc_db_sp7. omc_db_sp9 Completed (Requested Level 1). the backup succeeded: Onbar activity log file: /usr/omc/logs/bar_omc.Operating Information: OMC-R System Administration Procedure 12-12 3 Manual backup of Informix databases 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.log 2009-05-07 23:18:26 13358 13356 Completed level 1 backup omc_db_sp6 (Storage Manager copy ID: 1241709506 1241709518). omc_db_llog. omc_db_sp8. omc_db_plog. Execute the Procedure 12-11 again to backup group INFORMIX_IX2. 2009-05-07 23:18:29 13358 13356 Archive on rootdbs. 2009-05-07 23:18:29 13385 13383 (-43395) A log backup is already running. 2009-05-07 23:18:29 13385 13383 /usr/informix/bin/onbar_d -b -l 2009-05-07 23:18:29 13358 13356 Begin backup logical log 23. Backup Informix ixbar files: Execute the Procedure 12-11 to backup group INFORMIX_IX1. omc_db_sp4. 2009-05-07 23:18:28 13358 13356 Completed level 1 backup omc_db_sp8 (Storage Manager copy ID: 1241709508 1241709522). 2009-05-07 23:18:31 13397 13395 /usr/informix/bin/onbar_d -b -l 2009-05-07 23:18:31 13397 returning 0 (0x00) 13395 /usr/informix/bin/onbar_d complete. omc_db_sp6. omc_db_sp12. 2009-05-07 23:18:28 13358 13356 Begin level 1 backup omc_db_sp9. 2009-05-07 23:18:29 13358 13356 Successfully connected to Storage Manager. omc_db_sp10. Can't start another. omc_db_sp1. omc_db_sp2.

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.Backing up the GUI Server File System Procedure 12-13 Chapter 12: Backup Server Installation and Configuration Incremental Backup of Informix databases {34618} 1 To perform an incremental backup (that is. Follow the Procedure 12-12. Above. 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. 12-16 68P02901W19-S Oct 2009 . changes since last full backup) of the Informix databases. Backing up the GUI Server File System • Overview to backing up file systems using backup_MMI utility. • Procedure for backing up file systems using backup_MMI utility. replace the occurrences of the line onbar -b -w -L 0with onbar -b -w -L 1. NOTE Ensure there is no CD/DVD in the CD/DVD drive before performing the backup.

ensuring that it is not write-protected. 5 The following output is displayed: Valid Backup Tape Types D. QUIT Enter Choice: Enter Y when the tape light has stopped flashing and is permanently lit green. R .Operating Information: OMC-R System Administration Backing up the GUI Server File System 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 1 Log in to the GUI Server using the login id: root. . QUIT Enter Backup Tape Type: Enter the appropriate backup tape type: D . Continued 68P02901W19-S 12-17 Oct 2009 .for a local backup to the tape drive on the GUI Server. Quit Utility Enter Choice: Enter one of the following: L . DAT C.for a remote backup to the tape drive on the Single Platform Processor./backup_MMI. 6 The following prompt is displayed: Is there a writeable DAT/Cartridge tape loaded in the Tape Drive ? Y. Local Backup to the MMI/GUI Processor R. 2 Insert a new labeled DAT tape into the appropriate processor tape drive. CARTRIDGE Q. 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. YES to continue Q.for DAT tape drive. 3 Change to the /usr/omc/current/sbin directory by entering the following command: cd /usr/omc/current/sbin 4 Enter the following command to run the backup_MMI utility. Remote Backup to the Single Platform Processor Q.

Backing up the GUI Server File System Procedure 12-14 (Continued) 7 Chapter 12: Backup Server Installation and Configuration Performing a backup of the UNIX file systems on the GUI Server The following prompt is displayed: Enter Local Tape Device (Default is /dev/rmt/0) (Q to QUIT). As shown in the Table 12-3 below.89% done. the backup is being performed on a Sunblade 150 GUI Server. finished in 0:13 DUMP: 87. 8 In this example. DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files] DUMP: 42.75MB) on 1 volume at 1937 KB/sec DUMP: DUMP IS DONE Backing up the /omcgen filesystem DUMP: Date of this level 0 dump: Wed Jul 06 12:01:35 2005 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/md/rdsk/d10 (sunblade3:/omcgen) to somc57:/dev/rmt/0n. to a tape drive on the Single Platform Processor.76MB). /usr/omc will be Number 3. DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Writing 32 Kilobyte records DUMP: Estimated 5223950 blocks (2550. Output similar to the following example is displayed. NOTE The order in which the file systems are backed up is important when it comes to the restore. In the example below / (root) will be Number 1. 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. /omcgen will be Number 2. finished in 0:02 DUMP: 5223934 blocks (2550. DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Writing 32 Kilobyte records DUMP: Estimated 604 blocks (302KB). DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files] DUMP: 574 blocks (287KB) on 1 volume at 2064 KB/sec Continued 12-18 68P02901W19-S Oct 2009 . Enter the backup tape device name as /dev/rmt/0n.66% done.

A log file is kept in /usr/omc/logs/backup_MMI. there are three file systems that have been backed up. NOTE The confidence check command line in step 9 must be entered once for each partition that has been backed up. replace the faulty tape and repeat the backup procedure from step 2. If an error is returned. In this procedure. therefore it is necessary to enter this command a total of three times.Operating Information: OMC-R System Administration Procedure 12-14 (Continued) Backing up the GUI Server File System Performing a backup of the UNIX file systems on the GUI Server DUMP: DUMP IS DONE Backing up the /usr/omc filesystem DUMP: Date of this level 0 dump: Wed Jul 06 12:01:37 2005 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/md/rdsk/d15 (sunblade3:/usr/omc) to somc57:/dev/rmt/0n.<datestamp>. write-protect. DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Writing 32 Kilobyte records DUMP: DUMP: DUMP: DUMP: DUMP: Estimated 919936 blocks (449. 11 If the confidence check performed in step 9 is successful. in this example two more times in order to check the complete backup. 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 . Dumping (Pass III) [directories] Dumping (Pass IV) [regular files] 919934 blocks (449.19MB). label. and store the tape(s).19MB) on 1 volume at 2490 KB/sec DUMP IS DONE 9 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.

This will be used during the disaster recovery.restore solbak Continued 12-20 68P02901W19-S Oct 2009 . otherwise the system cannot be restored using this method. and at the ok prompt.Disaster Recovery Chapter 12: Backup Server Installation and Configuration Disaster Recovery ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Disaster Recovery GSM OMC-R server CAUTION Bootstrap information MUST be available. Procedure 12-16 1 Disaster Recovery: Starting JumpStart Insert the latest JumpStart media onto the client machine. it can be recovered by executing the following procedure: Procedure 12-15 Recovery of bootstrap information 1 Insert the latest backup tape into the tape drive. 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. Recovery of bootstrap information In the event that bootstrap information is unavailable. 2 Execute the following command as user root: /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. it is the latest bootstrap information of your system. execute as user root: Boot cdrom -.

44.178 Enter the machine's netmask: 255.85 Entering backup tape device information NOTE The questions relate to the backup tape device connected to the Backup Server.3.3. INFORMATION WILL ONLY BE ASKED FOR ONCE! ================================================= Basic Disaster Recovery Information ================================================= Press Enter to continue. follow this step: Procedure 12-17 Disaster Recovery: Entering network information The user is prompted to enter the platform’s network information. 3 Entering network information To enter the platform network information.255. Respond to each prompt with the correct information.Operating Information: OMC-R System Administration Procedure 12-16 2 Disaster Recovery GSM OMC-R server Disaster Recovery: Starting JumpStart (Continued) Once the server has booted from the installation media. IMPORTANT: THIS INFORMATION MUST BE CORRECT FOR THE DISASTER RECOVERY TO COMPLETE.0 Enter the machine's default router (leave blank if not required): 175. an information window similar to the following is displayed.44. 68P02901W19-S 12-21 Oct 2009 .255. Enter the machine's primary hostname: somc85 Enter the machine's IP address: 175.

Disaster Recovery GSM OMC-R server Chapter 12: Backup Server Installation and Configuration To enter the backup tape device information. follow this step: Procedure 12-19 Disaster Recovery: Entering bootstrap information The user is prompted to enter the bootstrap 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. Enter Local Tape Device to be restored from: /dev/rmt/0hbn Valid media types are: 1. Respond to each prompt with the correct information. DLT 7000 4. DDS4 2. Respond to each prompt with the correct information. LTO-3 Enter Number for Device Media Type: 1 Entering bootstrap information To enter the bootstrap information. Enter latest bootstrap saveset id: 2808799757 Enter starting file number: 22 Enter starting record number: 0 12-22 68P02901W19-S Oct 2009 . DAT72 3.

>1 hour). a command prompt will be available. 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. 2 Installation of OS is begun (takes a long time. follow this step: Procedure 12-20 Disaster Recovery: Confirming the installation information {34618} 1 Recovery begins once all the requested information has been provided. 4 Log in to the system as root and follow Procedure 12-1 to install the Backup Server software. 3 Once the OS is installed. 5 Create a Tape device using nsradmin /usr/sbin/nsr/nsradmin Select visual by typing visual The following screen gets displayed. Save your settings by pressing the Escape key and selecting Yes with the Return key.Operating Information: OMC-R System Administration Disaster Recovery GSM OMC-R server Confirming the disaster recovery information To confirm the disaster recovery information entered. Continued 68P02901W19-S 12-23 Oct 2009 .

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 0 backup1_Jun15 2 Enter the latest bootstrap save set ID (ssid) when requested. Type Quit and return at the prompt to return to the OS shell. Continued 12-24 68P02901W19-S Oct 2009 . this value is 235292161. In the example above.Disaster Recovery GSM OMC-R server Procedure 12-20 (Continued) Chapter 12: Backup Server Installation and Configuration Disaster Recovery: Confirming the installation information Select Quit.

R/ nsrmmdbasm -r /solbak/nsr/mm/mmvolume6/ /solbak/nsr/mm/ scanner: ssid 3870043393: scan complete scanner: ssid 3870043393: 548 KB. If the on-line index for backup1 was lost. after you have shut down the service. insert the tape containing the saveset identified by the bootstrap information into the tape drive on the OMC-R and press RETURN. Then restart the service.R/nsrjb.R/mot. this value is 56. 4 Enter the starting record number (record) when requested.R/servers /solbak/nsr/res.res /solbak/nsr/res...res /solbak/nsr/res. they are now recovered in the 'res. Otherwise.R/temip. The output of the mmrecov command will be similar to the example below: Scanning /dev/rmt/0mbn for save set 3870043393.res /solbak/nsr/res.R' directory.R/nsr. the system starts retrieving the server configuration information from the tape. 10 file(s) /dev/rmt/0mbn: Mount operation in progress /dev/rmt/0mbn: verifying label.R/nsrla.Operating Information: OMC-R System Administration Procedure 12-21 Disaster Recovery GSM OMC-R server Recovering using Backup Server configuration (Continued) 3 Enter the starting file number (file) when requested. just restart the service. Copy or move them to the 'res' directory. NOTE Once all requested information has been entered and the tape has been inserted in the drive. this value is 0. moving backward 2 file(s) /dev/rmt/0mbn: mounted 4mm tape backup1_June15 (write protected) If your resource files were lost.res /solbak/nsr/res. scanner: scanning 4mm tape backup1_June15 on /dev/rmt/0mbn /nsr /nsr: file exists. At this point. In the example above. overwriting /solbak/nsr/res. Continued 68P02901W19-S 12-25 Oct 2009 . In the example above. it can be recovered using the nsrck command.res /solbak/nsr/res. this may take a while.

orig mv res.R res 7 Restart NetWorker services: As user root: /usr/sbin/nsr/nsrexecd /usr/sbin/nsr/nsrd 8 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 . 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 6 {34618} Rename the recovered Backup Server Configuration files: As user root: cd /nsr mv res res.Disaster Recovery GSM OMC-R server Procedure 12-21 5 Chapter 12: Backup Server Installation and Configuration Recovering using Backup Server configuration (Continued) Once the server configuration information has been successfully retrieved.

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 & 2 Select the root file system (/) for restore from the left pane in the nwrecover main window. 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) Recover the Necessary Filesystems Use the following procedure to recover the necessary filesystems: Procedure 12-22 Recover the Necessary Filesystems {34618} NOTE A graphical display is needed for the rest of the procedure.Operating Information: OMC-R System Administration Procedure 12-21 9 Recover the Necessary Filesystems Recovering using Backup Server configuration (Continued) 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. Once a file system has been selected for restore. the check box gets ticked. Continued 68P02901W19-S 12-27 Oct 2009 .

The /dev and /devices directories. 7 The selection of file systems for restoration is now complete.Recover the Necessary Filesystems Procedure 12-22 3 Chapter 12: Backup Server Installation and Configuration Recover the Necessary Filesystems (Continued) Once the root file system has been selected. 6 Navigate to the /etc directory and deselect the file path_to_inst. 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: /usr/omc/ne_data/raw_stats /usr/omc/ne_data/e1mon Expand the /usr/omc/logs file system by double click and select: /usr/omc/logs/bss_sec /usr/omc/logs/sleeping_cell 4 Deselect the /dev and /devices directories as they are not to be restored. click the Start button. To begin the restore. 5 Navigate to the /directory and deselect the /solbak/nsr directory. must not be restored as these are configured by the Operating System installation. together with the /etc/path_to_inst file. Continued 12-28 68P02901W19-S Oct 2009 .

9.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 / /usr/bin/nwrecover & Continued 68P02901W19-S 12-29 Oct 2009 .0. proceed to step 22 directly. A Recover Status window will be displayed. You should continue steps 14 to 21. the recovery of the filesystem is complete. it is incomplete. 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. 9 The restore will restore these filesystems. Click OK to proceed. If the output matches the following lines. indicating the current status of the Restore. 11 Click Cancel to return to the nwrecover main window 12 Click File and Exit to quit nwrecover. 10 When a Recover completion time message appears in the Recover Status window. Skip steps 14 to 21. 13 Check /usr/omc. # ls /usr/omc 14 1.0.Operating Information: OMC-R System Administration Procedure 12-22 Recover the Necessary Filesystems Recover the Necessary Filesystems (Continued) 8 A Conflict Resolution window is displayed. # ls /usr/omc logs lost+found ne_data If the output matches the following lines. it is complete. the program should? Click OK to proceed.

A Recover Status window will be displayed. 20 Click Cancel to return to the nwrecover main window 21 Click File and Exit to quit nwrecover. 17 A Conflict Resolution window is displayed. Click OK to proceed. 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. check if the /usr/omc restore is complete. 19 When a Recover completion time message appears in the Recover Status window. Continued 12-30 68P02901W19-S Oct 2009 . To begin the restore.Recover the Necessary Filesystems Procedure 12-22 15 Chapter 12: Backup Server Installation and Configuration Recover the Necessary Filesystems (Continued) 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 /usr/omc/ne_data/raw_stats /usr/omc/ne_data/e1mon Expand the /usr/omc/logs file system by double click and select /usr/omc/logs/bss_sec /usr/omc/logs/sleeping_cell 16 The selection of file systems for restoration is now complete. click the Start button. 18 The restore command will restore /usr/omc. the program should? Click OK to proceed. indicating the current status of the Restore. the recovery of /usr/omc is complete.

Repeat the steps until all the restore is save set to a same time point. as part of a disaster recovery operation. select the name of the appropriate save set. 23 Run init 6 to reboot the system. Click Recover. 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. start them). In the Save Set Recover Status dialog box. skip this step (step 22). The OMC and informix service are online (if available offline. execute step 23.Operating Information: OMC-R System Administration Procedure 12-22 22 Recovering Informix databases Recover the Necessary Filesystems (Continued) If you have an incremental filesystem backup to restore. click Start to begin the recovery. The OMC system is ready to use. In the Instances list box. is as follows: Procedure 12-23 Recovering Informix databases {34618} 1 Execute the following command as user root: 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 . select the version of the save set based the backup history and the time point you want to restore to. select Save Set Recover from the Options menu. The recovery status appears in the Save Set Recover Status dialog box. after completing the following set of instructions. continue with Procedure 12-23 to restore the latest data available in your system. Now the full and incremental backup of the system are restored completely. Start the restore program by issuing the following commands as the user root: /usr/bin/nwrecover & In the nwrecover program. Recovering Informix databases The procedure to recover Informix databases. From the Save Set Name list. Else.

To begin the restore. Click OK to proceed. Set your display and enter the following commands: Start the restore program by issuing the following commands as user root: cd /usr/informix/etc /usr/bin/nwrecover & Select ixbar. The selection of ixbar files for restoration is now complete. NOTE A graphical display is needed for the rest of the procedure. a blue tick appears in the square check box.2 for restore from the left pane in the nwrecover main window. A Conflict Resolution window is displayed. click the Start button. A Recover Status window will be displayed. Continued 12-32 68P02901W19-S Oct 2009 . Click Cancel to return to the nwrecover main window. Once a file has been selected for restore. the program should? Click OK to proceed. 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 restoration process restores these files. the recovery of the filesystem is complete.Recovering Informix databases Chapter 12: Backup Server Installation and Configuration Procedure 12-23 2 Recovering Informix databases (Continued) Restore ixbar files from latest tape. When a Recover completion time message appears in the Recover Status window. indicating the current status of the Restore.1 and ixbar. Click File and Exit to quit nwrecover.

1 cp ixbar. If no latest ixbar.2.<most recent date> ixbar.1.122546 ixbar. produce them by copying the latest version from the files taken as backup. following the given set of commands. Bring the database to quiescent mode by issuing the following command as user informix: onmode -sy Once the database has changed to quiescent mode.Operating Information: OMC-R System Administration Procedure 12-23 3 Recovering Informix databases Recovering Informix databases (Continued) Perform a physical restore of the dbspaces for the CM database by issuing the following commands as user informix: cd /usr/informix/etc (We need the latest ixbar files to restore the informix data to the latest time point.1 and ixbar.<most recent date> ixbar. Continued 68P02901W19-S 12-33 Oct 2009 .2006109.2 For example: cp ixbar. 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.1. check the /usr/informix/bar_act. the CM database will be in fast-recovery mode.log.2 is available in this directory. Once the database restore is complete.1 mib_env onbar -r -w –p To check the status of a restore using onbar.) cp ixbar.

12-34 68P02901W19-S Oct 2009 . Bring the database to quiescent mode by issuing the following command as user informix: onmode -sy Once the database has changed to quiescent mode. The informix database is ready to use. the PM database will be in fast recovery mode. Once the database restore has completed. check the file /usr/informix/bar_act.log. svcadm enable svc:/application/informix/cm svcadm enable svc:/application/informix/pm Ensure svc:/application/informix/cm and svc:/application/informix/pm online 5 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.Recovering Informix databases Procedure 12-23 4 Chapter 12: Backup Server Installation and Configuration Recovering Informix databases (Continued) Perform a physical restore of the dbspaces for the PM database by executing the following commands as user informix: omc_env onbar -r -w -p To check the status of a restore using onbar. 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.

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 .Operating Information: OMC-R System Administration Recovery Recovery ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Introduction This section describes how to recover files and database which may become corrupted either through accidental deletion or other failure.

2 have been selected for recovery. In the example below. 12-36 68P02901W19-S Oct 2009 . In the next screen. navigate to the directory and/or files which are to be recovered and select them.1 and ixbar. select Overwrite existing file when prompted. Figure 12-2 File selection window for recovery Press the Start button to starts the recovery. the files ixbar.Introduction Chapter 12: Backup Server Installation and Configuration Using the UI. The recovery checks whether the required tape is online.

Procedure 12-24 68P02901W19-S PM database recovery 1 As user root. follow the procedure below. if requested. 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 . 3 Once the recovery has completed. issue the following command: omc_env svcadm disable svc:/application/informix/pm onbar –r 2 Mount the required tape.Operating Information: OMC-R System Administration Figure 12-3 Database recovery Recover status Database recovery To recover either the PM or MIB (CM) databases.

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 .Database recovery Chapter 12: Backup Server Installation and Configuration Procedure 12-25 12-38 MIB (CM) database recovery 1 As user root. if requested. execute the following command: mib_env svcadm disable svc:/application/informix/cm onbar –r 2 Mount the required tape. 3 Once the recovery is complete.

StorEdge Enterprise Backup Server GUI As of Solaris 10. select Edit à Preferences.sun. 12-39 Oct 2009 . Highlight Helper Applications under Navigator. nwadmin. if it exists. Click OK.Operating Information: OMC-R System Administration Additional Tools Additional Tools ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ This section details various tools that. the StorEdge Enterprise Backup Server GUI. may be of use.com for further details. a Java web-based interface has been introduced.jnlp Open it with: /usr/j2se/jre/javaws/javaws 6 Ensure that the Open it with: is selected. 5 Add the following information: MIME Type: application/x-java-jnlp-file Extension: . 3 Ensure that the DISPLAY is set correctly.java directory. Configuring Java Version NOTE The Java-based interface has an additional layer that allows the management of multiple OMC-R Backup Servers. Procedure 12-26 68P02901W19-S StorEdge Enterprise Backup Server: Java Configuration 1 Login to the Single Platform Processor as user root. the StorEdge Enterprise Backup Server GUI can be configured. Instead. is no longer available. Open a browser window by executing the following command: /usr/sfw/bin/mozilla & 4 In the browser window. and select New Type. Once the OMC-R Backup Server is installed. Documentation on how to use this is not included in this feature – reference docs. while not part of the OMC-R backup server. 7 Click OK to save out of Preferences. 2 Remove the /.

The default username/password is administrator. 2 Ensure that the DISPLAY is set correctly. Click Next on Welcome to the Configuration Window. Double-click the entry in the main window – another window. then select New. 2 Right-click Registrations. Otherwise. 11 Add Backup Server hostname on Add Sun StorEdge EBS Servers. Open a browser window by executing the following command: /usr/sfw/bin/mozilla & 3 Connect to the following URL: http://<server>:10000 Where <server> is the fully qualified GSM OMC-R hostname. 9 Click Next on Set Legato License Manager Server Name. 7 Accept the License agreement. 3 Complete the necessary attributes. click Next to retain the default password. 10 Click Next on Set Database Backup Server window. 68P02901W19-S Oct 2009 . and select the OMC-R Backup Server hostname. configuration is required. 12 The GUI is displayed. 6 On first login. Click the Enterprise button. 4 Click Start button to start the Enterprise Manager.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 1 A browser is installed by default on the OMC-R Backup Server and can be run as user root. 8 Change the administrator password if required. and then click OK. 5 A login dialog box is displayed. is displayed. and click Next. click Configuration. 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 1 From the StorEdge Enterprise Backup Server GUI Administration window.

Unmount 3. Status 5. Mount 2.com. label.001 nsrmm -l test. and tape status information. un-mount. Tape Management While tape management is done by the StorEdge Enterprise Backup Server GUI. and AUTOMATICALLY re-label the tape if a label already exists – query to mount the tape after labelling is also displayed. see Sun StorEdge Enterprise Backup Software 7. Label 4. 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 Continued 68P02901W19-S 12-41 Oct 2009 .3 Administration Guide (Sun Doc ID: 819-4972) from docs. Exit 3 Select appropriate option. a very basic interface has been designed to allow the user to have access to simple tape functionality such as mount. Tape Management from the command line Use the table below to manage tapes from the command line.Operating Information: OMC-R System Administration Tape Management NOTE For further information. Launching Basic Tape Management Interface Procedure 12-29 Tape Management Launching Menu 1 Execute the following command as user root: /var/install/bin/tape-mgr 2 The following menu is displayed: Tape Menu =========== 1.sun. NOTE The label option will prompt for a label name.

Tape Management Chapter 12: Backup Server Installation and Configuration 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 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 .001 mounted on /dev/rmt/0mbn. write enabled Unmount a tape /usr/sbin/nsr/nsrmm –u <tape label> /usr/sbin/nsr/nsrmm –u test.

If this is the first time. Enter Option: 2 Adding Client Enter Client hostname: somc85 Setting up SSH between the Backup Server and somc85. Sample output from backup client creation The following is a sample output from backup client creation. Responses are highlighted.Operating Information: OMC-R System Administration 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. the root password for somc85 has to be supplied. 68P02901W19-S 12-43 Oct 2009 .

saveset: "Informix:/omc_mib1". Initialize Backup Server 2. No resources found for query: name: Informix_Schedule. GUI_SERVER 2. Informix_PM 4. type: NSR Group. No resources found for query: name: somc85. Informix_IX2 Enter choice : 2 Server type chosen is: Informix_CM No resources found for query: name: INFORMIX_CM Directives. Informix_CM 3. type: NSR client. type: NSR schedule. No resources found for query: name: INFORMIX_CM. Delete Backup Client 5.Sample output from backup client creation Chapter 12: Backup Server Installation and Configuration Select Server Type ================== 1. Update Backup Client 4. Quit Enter Option: 2 Adding Client Enter Client hostname: somc85 Setting up SSH between the Backup Server and somc85 If this is the first time. Add Backup Client 3. Informix_IX1 5. Select Server Type ================== 12-44 68P02901W19-S Oct 2009 . ================== Backup Server Menu ================== 1.. the root password for somc85 has to be supplied.. Creating. type: NSR directive. Schedule Informix_Schedule does not exist.

Informix_PM 4. ================== Backup Server Menu ================== 1. GUI_SERVER 2. override: . Update Backup Client 4. type: NSR schedule. No resources found for query: name: INFORMIX_PM. Add Backup Client 3. type: NSR directive. period: Week. type: NSR client. Informix_IX2 Sample output from backup client creation Enter choice : 3 Server type chosen is: Informix_PM No resources found for query: name: INFORMIX_PM Directives. comment: . Quit 68P02901W19-S 12-45 Oct 2009 . Informix_CM 3. Informix_IX1 5. Delete Backup Client 5. saveset: "Informix:/omc_sys1". No resources found for query: name: somc85. name: Informix_Schedule. type: NSR Group. Initialize Backup Server 2.Operating Information: OMC-R System Administration 1. action: full full full full full full full.

No resources found for query: name: somc85. type: NSR directive. ================== Backup Server Menu ================== 1. type: NSR schedule. saveset: /usr/informix/etc/ixbar. type: NSR client. period: Week. name: Informix_Schedule. type: NSR Group. Informix_PM 4. Initialize Backup Server 2. Update Backup Client 4. No resources found for query: name: INFORMIX_IX1. override: . Informix_IX1 5.1. GUI_SERVER 2. Select Server Type ================== 1.Sample output from backup client creation Chapter 12: Backup Server Installation and Configuration Enter Option: 2 Adding Client Enter Client hostname: somc85 Setting up SSH between the Backup Server and somc85 If this is the first time. comment: . Quit 12-46 68P02901W19-S Oct 2009 . Informix_IX2 Enter choice : 4 Server type chosen is: Informix_IX1 No resources found for query: name: INFORMIX_IX1 Directives. action: full full full full full full full. the root password for somc85 has to be supplied. Informix_CM 3. Delete Backup Client 5. Add Backup Client 3.

saveset: /usr/informix/etc/ixbar. type: NSR client. override: . type: NSR Group. action: full full full full full full full. Informix_PM 4. Select Server Type ================== 1.Operating Information: OMC-R System Administration Sample output from backup client creation Enter Option: 2 Adding Client Enter Client hostname: somc85 Setting up SSH between the Backup Server and somc85 If this is the first time. period: Week. Informix_CM 3. Delete Backup Client 5. Add Backup Client 3.2. No resources found for query: name: INFORMIX_IX2. the root password for somc85 has to be supplied. name: Informix_Schedule. Quit 68P02901W19-S 12-47 Oct 2009 . comment: . ================== Backup Server Menu 1. Initialize Backup Server 2. Update Backup Client 4. Informix_IX2 Enter choice : 5 Server type chosen is: Informix_IX2 No resources found for query: name: INFORMIX_IX2 Directives. No resources found for query: name: somc85. type: NSR schedule. Informix_IX1 5. type: NSR directive. GUI_SERVER 2.

2 Insert a new labelled DAT tape into the appropriate processor tape drive. 3 Change directory to /usr/omc/current/sbin by executing the following command: cd /usr/omc/current/sbin Continued 12-48 68P02901W19-S Oct 2009 . CAUTION Ensure that there is no CD/DVD in the CD/DVD drive before performing the backup.Backup and Restore using the Standard Solaris suite of utilities Chapter 12: Backup Server Installation and Configuration Enter Option: 5 Exiting at user request Backup and Restore using the Standard Solaris suite of utilities 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. ensuring that it is not write-protected. 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 1 Log in to the Single Platform Processor as user root.

39MB) DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files] DUMP: 18. DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Writing 32 Kilobyte records DUMP: Estimated 12739366 blocks (6220./backup_splat The following prompt is displayed: Is there a writable DAT tape loaded in the Tape.50MB) DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files] DUMP: 304062 blocks (148. Please enter YES to continue:YES 5 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. DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Writing 32 Kilobyte records DUMP: Estimated 304120 blocks (148.47MB) on 1 volume at 1664 KB/sec DUMP: DUMP IS DONE DUMP: Level 0 dump on Fri Jan 05 13:56:27 2007 Backing up the /usr filesystem DUMP: Date of this level 0 dump: Fri Jan 05 13:58:01 2007 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/md/rdsk/d20 (somc85:/usr) to /dev/rmt/0n.52% done.Operating Information: OMC-R System Administration Procedure 12-30 4 Backup and Restore using the Standard Solaris suite of utilities Backing up file systems using backup_splat utility (Continued) Enter the following command to run the backup_splat utility. finished in 0:44 Continued 68P02901W19-S 12-49 Oct 2009 . . 6 Output similar to the following is displayed: 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: Date of last level 0 dump: the epoch DUMP: Dumping /dev/md/rdsk/d0 (somc85:/) to /dev/rmt/0n.

09MB).75MB) on 1 volume at 2007 KB/sec DUMP: DUMP IS DONE DUMP: Level 0 dump on Fri Jan 05 15:00:02 2007 Backing up the /omcgen filesystem DUMP: Date of this level 0 dump: Fri Jan 05 15:00:54 2007 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/md/rdsk/d30 (somc85:/omcgen) to /dev/rmt/0n.29% done.00% done. finished in 0:01 DUMP: 12739326 blocks (6220. Continued 12-50 68P02901W19-S Oct 2009 . finished in 0:37 DUMP: 49. DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Writing 32 Kilobyte records DUMP: Estimated 270522 blocks (132.76MB). DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Writing 32 Kilobyte records DUMP: Estimated 198172 blocks (96.06MB) on 1 volume at 2338 KB/sec DUMP: DUMP IS DONE DUMP: Level 0 dump on Fri Jan 05 14:59:02 2007 Backing up the /opt filesystem DUMP: Date of this level 0 dump: Fri Jan 05 15:00:02 2007 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/md/rdsk/d15 (somc85:/opt) to /dev/rmt/0n. finished in 0:21 DUMP: 79.85% done.26% done. finished in 0:31 DUMP: 64. DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files] DUMP: 198142 blocks (96. finished in 0:13 DUMP: 98.Backup and Restore using the Standard Solaris suite of utilities Procedure 12-30 Chapter 12: Backup Server Installation and Configuration Backing up file systems using backup_splat utility (Continued) DUMP: 35.37MB) on 1 volume at 1744 KB/sec DUMP: DUMP IS DONE DUMP: Level 0 dump on Fri Jan 05 13:58:01 2007 Backing up the /var filesystem DUMP: Date of this level 0 dump: Fri Jan 05 14:59:02 2007 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/md/rdsk/d10 (somc85:/var) to /dev/rmt/0n.08% done. DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files] DUMP: 270462 blocks (132.

19MB) on 1 volume at 2740 KB/sec DUMP: DUMP IS DONE DUMP: Level 0 dump on Fri Jan 05 15:00:55 2007 Backing up the /usr/omc filesystem DUMP: Date of this level 0 dump: Fri Jan 05 15:00:58 2007 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/md/rdsk/d40 (somc85:/usr/omc) to /dev/rmt/0n. DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files] DUMP: 1142078 blocks (557.66MB) on 1 volume at 2513 KB/sec DUMP: DUMP IS DONE DUMP: Level 0 dump on Fri Jan 05 15:00:58 2007 Backing up the /usr/omc/logs filesystem DUMP: Date of this level 0 dump: Fri Jan 05 15:04:46 2007 DUMP: Date of last level 0 dump: the epoch Continued 68P02901W19-S 12-51 Oct 2009 . DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Writing 32 Kilobyte records DUMP: Estimated 4484 blocks (2.68MB). DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Writing 32 Kilobyte records DUMP: Estimated 1142136 blocks (557.Operating Information: OMC-R System Administration Procedure 12-30 Backup and Restore using the Standard Solaris suite of utilities Backing up file systems using backup_splat utility (Continued) DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Writing 32 Kilobyte records DUMP: Estimated 608 blocks (304KB).19MB). DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files] DUMP: 574 blocks (287KB) on 1 volume at 2296 KB/sec DUMP: DUMP IS DONE DUMP: Level 0 dump on Fri Jan 05 15:00:54 2007 Backing up the /home filesystem DUMP: Date of this level 0 dump: Fri Jan 05 15:00:55 2007 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/md/rdsk/d35 (somc85:/home) to /dev/rmt/0n. DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files] DUMP: 4478 blocks (2.

DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Writing 32 Kilobyte records DUMP: Estimated 101078 blocks (49.00MB).35MB). DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Writing 32 Kilobyte records DUMP: Estimated 1136 blocks (568KB).Backup and Restore using the Standard Solaris suite of utilities Procedure 12-30 Chapter 12: Backup Server Installation and Configuration Backing up file systems using backup_splat utility (Continued) DUMP: Dumping /dev/md/rdsk/d45 (somc85:/usr/omc/logs) to /dev/rmt/0n.34MB) on 1 volume at 2176 KB/sec DUMP: DUMP IS DONE DUMP: Level 0 dump on Fri Jan 05 15:04:52 2007 Backing up the /usr/omc/ne_data/raw_stats filesystem DUMP: Date of this level 0 dump: Fri Jan 05 15:05:17 2007 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/md/rdsk/d55 (somc85:/usr/omc/ne_data/raw_stats) to /dev/rmt/0n.00MB) on 1 volume at 1103 KB/sec DUMP: DUMP IS DONE DUMP: Level 0 dump on Fri Jan 05 15:04:46 2007 Backing up the /usr/omc/ne_data filesystem DUMP: Date of this level 0 dump: Fri Jan 05 15:04:52 2007 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/md/rdsk/d50 (somc85:/usr/omc/ne_data) to /dev/rmt/0n. DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files] DUMP: 101054 blocks (49. DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files] DUMP: 1086 blocks (543KB) on 1 volume at 2728 KB/sec DUMP: DUMP IS DONE DUMP: Level 0 dump on Fri Jan 05 15:05:17 2007 Backing up the /solbak filesystem DUMP: Date of this level 0 dump: Fri Jan 05 15:05:19 2007 Continued 12-52 68P02901W19-S Oct 2009 . DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Writing 32 Kilobyte records DUMP: Estimated 12296 blocks (6. DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files] DUMP: 12286 blocks (6.

Operating Information: OMC-R System Administration Procedure 12-30 Backup and Restore using the Standard Solaris suite of utilities Backing up file systems using backup_splat utility (Continued) DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/md/rdsk/d60 (somc85:/solbak) to /dev/rmt/0n. DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Writing 32 Kilobyte records DUMP: Estimated 852 blocks (426KB). DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files] DUMP: 830 blocks (415KB) on 1 volume at 2455 KB/sec DUMP: DUMP IS DONE DUMP: Level 0 dump on Fri Jan 05 15:05:19 2007 Backing up the /usr/omc/logs/bss_sec filesystem DUMP: Date of this level 0 dump: Fri Jan 05 15:05:20 2007 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/md/rdsk/d65 (somc85:/usr/omc/logs/bss_sec) to /dev/rmt/0n. DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files] DUMP: 574 blocks (287KB) on 1 volume at 2224 KB/sec DUMP: DUMP IS DONE DUMP: Level 0 dump on Fri Jan 05 15:05:20 2007 Backing up the /usr/omc/logs/sleeping_cell filesystem DUMP: Date of this level 0 dump: Fri Jan 05 15:05:21 2007 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/md/rdsk/d70 (somc85:/usr/omc/logs/sleeping_cell) to /dev/rmt/0n. DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Writing 32 Kilobyte records DUMP: Estimated 604 blocks (302KB). DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files] DUMP: 318 blocks (159KB) on 1 volume at 3697 KB/sec DUMP: DUMP IS DONE DUMP: Level 0 dump on Fri Jan 05 15:05:21 2007 Continued 68P02901W19-S 12-53 Oct 2009 . DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Writing 32 Kilobyte records DUMP: Estimated 348 blocks (174KB).

68P02901W19-S Oct 2009 . DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Writing 32 Kilobyte records DUMP: Estimated 860 blocks (430KB). NOTE Repeat this seven more times in order to check the complete backup. In this example. A log file is kept in /usr/omc/logs/backup_splat.Backup and Restore using the Standard Solaris suite of utilities Procedure 12-30 Chapter 12: Backup Server Installation and Configuration Backing up file systems using backup_splat utility (Continued) Backing up the /zones filesystem DUMP: Date of this level 0 dump: Fri Jan 05 15:05:22 2007 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/md/rdsk/d75 (somc85:/zones) to /dev/rmt/0n.. DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files] DUMP: 830 blocks (415KB) on 1 volume at 2470 KB/sec DUMP: DUMP IS DONE DUMP: Level 0 dump on Fri Jan 05 15:05:22 2007 Backing up the /usr/omc/ne_data/e1mon filesystem DUMP: Date of this level 0 dump: Fri Jan 05 15:05:23 2007 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/md/rdsk/d80 (somc85:/usr/omc/ne_data/e1mon) to /dev/rmt/0n. DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Writing 32 Kilobyte records DUMP: Estimated 348 blocks (174KB).. The confidence check command line must be entered once for each partition that has been backed up. 8 12-54 Make the tape write-protected..<datestamp>. there are seven file systems that have been backed up. therefore it is necessary to enter this command a total of eight times. plus one additional time for the tar files at the front of the backup 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. DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files] DUMP: 318 blocks (159KB) on 1 volume at 2789 KB/sec DUMP: DUMP IS DONE DUMP: Level 0 dump on Fri Jan 05 15:05:23 2007 Backup completed REWINDING TAPE.

sh The recommended tape sizes for Informix are: 68P02901W19-S 12-55 Oct 2009 .Operating Information: OMC-R System Administration Backing up the PM and CM Databases Backing up the PM and CM Databases • Default DAT parameters. • Overview of IDS message log files for the PM Database. The following levels of backup exist: • Level 0 . • Monitoring the active message log files for the PM Database. • View Archived message log files for the CM Database. • The tape blocking factor/size is 1024 KB for the DAT tape. • Level 1 . • The tape device is /dev/rmt/0. • Backing up the PM Database. The following parameters apply to the default DAT drive. Level of backup The level of backup is required when performing the archive procedure.weekly backup. • Monitoring the active message log files for the CM Database. • The tape size (in KB) is 4000000 for the DAT tape. • Backing up the CM Database.monthly backup. • Checking and changing tape parameters. • Level 2 . Checking and changing tape parameters As user Informix execute the following command: /usr/omc/sbin/set_tape_parameters. • View Archived message log files for the PM 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. • Level of backup. • Overview of IDS message log files for the CM Database.daily backup.

. 2 Set the following environment variable: setenv TERM vt100 3 Set the correct environment for the database archive. For CM database.000 • DDS4 — 38. then use the following procedure to change the tape parameters: Procedure 12-31 Checking and changing tape parameters 1 Login to the System Processor as user informix. For the PM database.. ––––––––––––––––On–line––––––––– Press CTRL–W for Help ––––– This will bring up the Archive menu: ARCHIVE: Tape Parameters Exit Change tape device or tape characteristics ––––––––––––––––––On–line––––– Press CTRL–W for Help ––––– 6 Select the Tape Parameters option to bring up the Tape Parameters menu: Press ESC to change tape parameters. 4 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 Force–Ckpt .sh will only set the tape parameters for the default DDS3 device.000 The utility /usr/omc/sbin/set_tape_parameters. Archive Logical-Logs Exit Status menu to view Dynamic Server ––––––––––––––––On–line––––––––– Press CTRL–W for Help ––––– 5 Select the Archive option from the onmonitor menu by using the space bar to toggle between options: Informix–Online: .Backing up the PM and CM Databases Chapter 12: Backup Server Installation and Configuration • DDS3 — 20. Archive Logical–Logs Exit Change tape device or tape characteristics.. enter the alias mib_env. MODIFYING TAPE PARAMETERS Tape Device [/dev/rmt/0] Continued 12-56 68P02901W19-S Oct 2009 .. Press F2 or CTRL-F for field level help. enter the alias omc_env. If you have DDS4 or DAT72. Press Interrupt to return to the Archive menu.000.000.000.000 • DAT72 — 70.

Press RETURN. Backing up the PM Database Procedure 12-32 Back up the PM database to the Single Platform Processor 1 Login to the Single Platform Processor using login id root and switch user to informix: su — informix 2 Set the following environment variable: setenv TERM vt100 3 Set the correct environment for the database archive. If the archive is interrupted. Output similar to the following is displayed: 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. the block size set to 1024 and the tape size set to 38000000. This is usually CTRL-c or the DELETE key. Continued 68P02901W19-S 12-57 Oct 2009 . For the PM database. For example. ensure the tape device is set to /dev/rmt/0. Press ESC to commit any changes.Operating Information: OMC-R System Administration Procedure 12-31 Backing up the PM and CM Databases 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. Select the Exit option again to exit the onmonitor utility.sh 5 Start the archive by entering the following command: ontape —s —L <archive_level> Where <archive_level> is the level of archive. then the archive copy is corrupted and a new archive will have to be initiated to perform a backup. to start a level 0 archive enter ontape –s –L 0. or CTRL-C to quit without saving. 7 Select the Exit option to exit the Archive menu. enter the alias: omc_env 4 As user Informix execute the following command: /usr/omc/sbin/set_tape_parameters.

log_OMC . 2.log_OMC. to indicate the sequence in which the tapes must be mounted if used to restore the database. 8 If an error occurs during the archive. a message is displayed indicating which tapes are required to restore the database to its present state. 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. If an error is returned. write protect. The logical log information can be ignored as logical logs are not currently used. 68P02901W19-S Oct 2009 . 9 When the archive is complete. 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. As these files increase continuously in size.archived message log file for PM database.log.Backing up the PM and CM Databases Procedure 12-32 (Continued) 6 Chapter 12: Backup Server Installation and Configuration Back up the PM database to the Single Platform Processor Output similar to the following is displayed: 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. label. the user is prompted when a change of tape is needed. This tape contains the following the following logical logs: 3 Program over 7 If the archive requires more than one tape. The tapes must be labelled 1. • /usr/informix/online.active message log file for PM database.<ddmmyyyy> . and store the tape(s). Overview of IDS message log files for the PM Database Each Informix Dynamic Server requires a message log file. replace the faulty tape and repeat the backup procedure from step 5. 3. The message log files are owned by informix and held on the Single Platform Processor as follows: 12-58 • /usr/informix/online. The message also indicates the logical log at which to start to restore the system after the backup tapes have been mounted. 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. and so on.

informix 2 Set up the correct environment: For PM database enter: omc_env 3 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>). Using the unix tail command.log_OMC. execute: tail -f $INFORMIXDIR/online.informix 2 Display the appropriate timestamped message log file. Use the following procedure to view the PM database message logs: Procedure 12-33 Viewing the PM database message logs 1 Login to the Single Platform Processor using login id root and switch user to informix: su . 12-59 Oct 2009 .log_OMC 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 1 Login to the Single Platform Processor using login id root and switch user to informix: su . For PM database timestamped message log file enter: view /usr/informix/online. The <sleep_time> specifies the number of seconds the process will be put to sleep before rechecking the IDS message log file. month and year the log file was created.<ddmmyyyy> Where <ddmmyyyy> is the day.Operating Information: OMC-R System Administration Backing up the PM and CM Databases 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.

If the archive is interrupted. Press RETURN.Backing up the PM and CM Databases Chapter 12: Backup Server Installation and Configuration 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 1 Login to the Single Platform Processor using login id root and switch user to informix: su — informix 2 Set the following environment variable: setenv TERM vt100 3 Set the correct environment for the database archive.sh 5 Start the archive by entering the following command: ontape —s —L <archive_level> Where <archive_level> is the level of archive. mib_env 4 As user Informix execute the following command: /usr/omc/sbin/set_tape_parameters. This is usually CTRL-c or the DELETE key. This tape contains the following the following logical logs: 3 Program over Continued 12-60 68P02901W19-S Oct 2009 . Output similar to the following is displayed: 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. 6 Output similar to the following is displayed: 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. For example. then the archive copy is corrupted. to start a level 0 archive enter ontape -s –L 0.

<ddmmyyyy> – archived message log file for CM database. label.log_MIB – active message log file for CM database. The cron job is /usr/omc/sbin/roll_online. 9 When the archive is complete. 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. 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. 68P02901W19-S 12-61 Oct 2009 . The logical log information can be ignored as logical logs are not currently used. and so on. 3. 8 If an error occurs during the archive. to indicate the sequence in which the tapes must be mounted if used to restore the database. The tapes must be labeled 1. • /usr/informix/online. 2. a message is displayed indicating which tapes are required to restore the database to its present state. which can then be archived and removed from the file system. write protect. The message log files are owned by informix and held on the Single Platform Processor as follows: • /usr/informix/online. 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.Operating Information: OMC-R System Administration Procedure 12-35 (Continued) Backing up the PM and CM Databases Back up the CM database to the Single Platform Processor 7 If the archive requires more than one tape.log_MIB. If an error is returned. the user is prompted when a change of tape is needed.log. The message also indicates the logical log at which to start to restore the system after the backup tapes have been mounted. 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. and store the tape(s). As these files increase continuously in size.

Use the following procedure to view the CM database message logs: Procedure 12-36 View the CM database message logs 1 Log in to the Single Platform Processor using login id root and switch user to informix: su — informix 2 Set up the correct environment: mib_env 3 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>). 1 Log in to the Single Platform Processor using login ID root and switch user to informix:su — informix 2 Display the appropriate timestamped message log file. 68P02901W19-S Oct 2009 . Using the unix tail command. execute: tail —f $INFORMIXDIR/online.log_MIB.Backing up the PM and CM Databases Chapter 12: Backup Server Installation and Configuration 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. month and year the log file was created. The <sleep_time> specifies the number of seconds the process will be put to sleep before rechecking the IDS message log file. For PM database timestamped message log file enter:view /usr/informix/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.<ddmmyyyy> Where <ddmmyyyy> is the day.

• JumpStarting the Single Platform Processor. This utility enables recovery of all Single Platform Processor file systems that have been stored on a backup tape using the backup_splat utility.Operating Information: OMC-R System Administration Restoring Single Platform Processor file systems 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. The task of restoring file systems to the Single Platform Processor involves the following procedures: • Shutting down the Single Platform Processor. • Restoring the databases. The data can be restored on a brand new set of disks or on disks that have become corrupt. 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 . CAUTION The procedure destroys any data on the disks and overwrites the disks with data from the backup tape. Before commencing the restore procedure.

• Creating the /etc/hosts. JumpStarting the Netra Single Platform Processor For the clean install of the Netra Single Platform. 2 Enter the following commands to inform all users that a complete system restore is to be performed: wall System coming down immediately ^d 3 Bring the system down to PROM mode: /usr/sbin/shutdown -i0 -g0 -y The PROM monitor mode ok prompt is displayed. Follow all the instructions provided in the procedure excluding the following sections: • The /etc/dfs/dfstab file. refer to the procedure given in Chapter 2 of the Installation and Conguration: OMC-R Clean Install (68P02901W47).equiv file. Complete the following procedure to restore the Netra Single Platform Processor: Procedure 12-39 JumpStarting the Netra Single Platform Processor 1 Insert the Motorola JumpStart DVD in the DVD-ROM drive of the System Processor. 3 Enter the following command at the ok prompt and press RETURN: boot cdrom –. • Modifying the /etc/hosts file. • Creating the /.rhosts file. Continued 12-64 68P02901W19-S Oct 2009 . 2 Insert the latest Full System backup tape in the DAT drive of the System Processor.Restoring Single Platform Processor file systems Chapter 12: Backup Server Installation and Configuration 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 1 Log in to the Single Platform Processor as user root.restore Follow the on-screen prompts.

we have to construct a list of the NIS servers. 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. the system needs to be rebooted to restart services by running the following command as user root: /usr/sbin/shutdown -i6 -g0 –y 6 Once the system has rebooted./hosts . execute the following commands to attach the HSIP drivers as user root: rem_drv HSIP add_drv HSIP 5 The Netra Single Platform Processor then restores the full system backup from tape and upon completion returns with the console login./ipnodes 7 If NIS is used as the naming service. instance #0 pci1214.334. one per line. then the following message is displayed: pci1214. compare the two files /etc/inet/hosts and /etc/inet/hosts.334.334.Operating Information: OMC-R System Administration Procedure 12-39 4 Restoring Single Platform Processor file systems JumpStarting the Netra Single Platform Processor (Continued) Once the system has rebooted./ipnodes ln –s .postmerge .334. type a <control D> or a return on a line by itself. instance #0 (driver not attached) pci1214. Continue to add the names for YP servers in the order of preference.postmerge. instance #1 If the HSIP drivers are not attached. At this point. When you are done with the list./hosts rm ./hosts. need to manually update /etc/inet/hosts by executing the following command: cd /etc/inet/ cp . 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 . execute the following as root: ypinit -m In order for NIS to operate successfully. if there are differences between the two files. instance #1 (driver not attached) If the HSIP drivers are not attached.

some part of the system (perhaps the yp itself) won't work. 138 bytes total Continued 12-66 68P02901W19-S Oct 2009 . The remainder of the procedure should take 5 to 10 minutes. please remember to go back and redo manually whatever fails.. Do you want this procedure to quit on non-fatal errors? [y/n: n] OK. Questions will all be asked at the beginning of the procedure. If you don't.... 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. 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. Building /var/yp/omcadmin/ypservers. longest 10 bytes.Restoring Single Platform Processor file systems Procedure 12-39 Chapter 12: Backup Server Installation and Configuration JumpStarting the Netra Single Platform Processor (Continued) Installing the YP database will require that you answer a few questions.

• Modifying the /etc/hosts file. updated netmasks updated timezone updated auto. If there are running slave yp servers.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. 8 The system needs to be rebooted to restart services by executing the following command as user root:/usr/sbin/shutdown -i6 -g0 -y 9 If you need to restore the databases too. Follow all the instructions provided in the procedure excluding the following sections: • The /etc/dfs/dfstab file. Procedure 12-40 to restore the Sunfire 4800/4900.equiv file.Operating Information: OMC-R System Administration Procedure 12-39 Restoring Single Platform Processor file systems JumpStarting the Netra Single Platform Processor (Continued) /usr/lib/netsvc/yp/mkalias /var/yp/‘domainname‘/mail. 68P02901W19-S 12-67 Oct 2009 . If there are no running slaves.master updated auto. run ypinit on those hosts which are to be slave servers.aliases /var/yp/domainname/mail. 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. updated aliases updated publickey updated netid /usr/sbin/makedbm /etc/netmasks /var/yp/‘domainname‘/netmasks. • Creating the /etc/hosts.byaddr.rhosts file.byaddr. • Creating the /. please execute the following command as user root:svcadm clear svc:/system/basicreg:default svcadm disable omc 10 After logging in. refer to the procedure given in Chapter 2 of the Installation and Conguration: OMC-R Clean Install (68P02901W47). run yppush now for any data bases which have been changed.

Inc...... Copying IO prom to Cpu dram {/N0/SB2/P2} @(#) lpost 5.00000020 [00000010] {/N0/SB2/P2} System PCI IO post code running from memory {/N0/SB2/P2} @(#) lpost 5..13. 3 Enter the following command at the ok prompt..13. the server does not start up automatically after power on or reset...... All rights reserved. setenv auto-boot? False Screen output similar to the following is displayed: auto-boot? = false 4 Enter the following command to reboot the server..2 2005/06/21 12:33 {/N0/SB2/P2} Copyright 2001 Sun Microsystems.Restoring Single Platform Processor file systems Procedure 12-40 Chapter 12: Backup Server Installation and Configuration JumpStarting the SunFire Single Platform Processor 1 Insert the Motorola JumpStart DVD in the DVD-ROM drive of the Single Platform Processor... Inc. .. 2 Insert the latest Full System backup tape in the DAT drive of the Single Platform Processor....2 2005/06/21 12:33 {/N0/SB2/P2} Copyright 2001 Sun Microsystems.. Continued 12-68 68P02901W19-S Oct 2009 .... reset-all Screen output similar to the following is displayed: Resetting . and press RETURN. If auto-boot is set to false...{/N0/SB2/P2} Running PCI IO Controller Basic Tests {/N0/SB2/P2} Jumping to memory 00000000. All rights reserved..... and press RETURN...

334. Select the device path associated with the DVD-ROM drive (this is the first line of the previous screen output). 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. instance #0 pci1214.0:f Target 2 Unit 0 Processor SUN D240 2 Target 4 Unit 0 Disk SEAGATE ST34371W SUN4. If this string contains "scsi".0/pci@19.334.0:f to the string. Paste this device path after nvalias cdrom. and press RETURN.0:f or nvalias cdrom /ssm@0.0 in this example refers to Target 6 and unit 0 where the DVD-ROM resides on the SCSI bus.0:f At the OK> prompt.700000/pci@2/SUNW. 7 Once the system has rebooted. the following message is displayed: pci1214.isptwo@4/sd@6. If it contains "isptwo".700000/pci@2/scsi@2/disk@6.700000/pci@2/SUNW.restore The system is jumpstarted without any prompts and the file systems are automatically restored. append /sd@6.334. The 6.0:f to the string.334.Operating Information: OMC-R System Administration Procedure 12-40 5 Restoring Single Platform Processor file systems JumpStarting the SunFire Single Platform Processor (Continued) Enter the following command to identify all the devices attached to the SCSI bus. execute the following command: boot cdrom -. instance #1 If the HSIP drivers are not attached. instance #0 (driver not attached) pci1214. For example: nvalias cdrom /ssm@0.0/pci@19. append /disk@6. instance #1 (driver not attached) Continued 68P02901W19-S 12-69 Oct 2009 .0/pci@19.2G7462 Target 6 Unit 0 Removable Read Only device TOSHIBA DVD-ROM SD-M14011009 6 Type nvalias cdrom at the OK> prompt.isptwo@4/sd@6. probe-scsi-all Screen output similar to the following is displayed: /ssm@0.

we have to construct a list of the NIS servers./ipnodes 10 If NIS is used as the naming service.Restoring Single Platform Processor file systems Procedure 12-40 Chapter 12: Backup Server Installation and Configuration JumpStarting the SunFire Single Platform Processor (Continued) If the HSIP drivers are not attached. execute the following as root: ypinit -m In order for NIS to operate successfully. please remember to go back and redo manually whatever fails. When you are done with the list.postmerge . the system needs to be rebooted to restart services by executing the following command as user root: /usr/sbin/shutdown -i6 -g0 –y 9 Once the system has rebooted. type a <control D> or a return on a line by itself. 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. need to manually update /etc/inet/hosts by executing the following command: cd /etc/inet/ cp . some part of the system (perhaps the yp itself) won't work./ipnodes ln –s . one per line./hosts . Continue to add the names for YP servers in the order of preference. Questions will be asked at the beginning of the procedure. compare the two files /etc/inet/hosts and /etc/inet/hosts. 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. If you don't.postmerge If there are differences between the two files. The yp domain directory is /var/yp/omcadmin Can we destroy the existing /var/yp/omcadmin and its contents? [y/n: n] y Continued 12-70 68P02901W19-S Oct 2009 ./hosts rm . At this point. Do you want this procedure to quit on non-fatal errors? [y/n: n] OK./hosts.

home updated ageing. Building /var/yp/omcadmin/ypservers. updated netmasks updated timezone updated auto. 138 bytes total /usr/lib/netsvc/yp/mkalias /var/yp/‘domainname‘/mail. longest 10 bytes.. run ypinit on those hosts which are to be slave servers. If there are no running slaves. Running /var/yp /Makefile..byaddr. Continued 68P02901W19-S 12-71 Oct 2009 . The remainder of the procedure should take 5 to 10 minutes.master updated auto.Operating Information: OMC-R System Administration Procedure 12-40 Restoring Single Platform Processor file systems JumpStarting the SunFire Single Platform Processor (Continued) There will be no further questions.. updated aliases updated publickey updated netid /usr/sbin/makedbm /etc/netmasks /var/yp/‘domainname‘/netmasks. run yppush now for any data bases which have been changed.byaddr. 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. 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.aliases /var/yp/domainname/mail.

equiv file. please execute the following command as user root: svcadm clear svc:/system/basicreg:default svcadm disable omc 13 After logging in. • Modifying the /etc/hosts file. 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.equiv file.Restoring Single Platform Processor file systems Procedure 12-40 Chapter 12: Backup Server Installation and Configuration JumpStarting the SunFire Single Platform Processor (Continued) 11 The system needs to be rebooted to restart services by executing the following command as user root: /usr/sbin/shutdown -i6 -g0 -y 12 If you need to restore the databases too.rhosts. Procedure 12-41 Platform Processor JumpStarting the SunSparc Enterprise M4000/M5000 Single 1 Insert the Motorola JumpStart DVD in the DVD-ROM drive of the Single Platform Processor. • Creating the /etc/hosts. and press RETURN. If auto-boot is set to false. 2 Insert the latest Full System backup tape in the DAT drive of the Single Platform Processor. 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: • The /etc/dfs/dfstab file. the server does not start up automatically after power on or reset. 3 Enter the following command at the OK prompt. setenv auto-boot? false Screen output similar to the following is displayed: auto-boot? = false Continued 12-72 68P02901W19-S Oct 2009 . Follow Procedure 12-41 to JumpStart the SunSparc Enterprise M4000/M5000. • Creating the /.

3..0 (2008/ 04/18 09:15) POST Sequence 02 Banner LSB#00 (XSB#00-0): POST 2.3... reset-all Screen output similar to the following is displayed: Resetting.Operating Information: OMC-R System Administration Restoring Single Platform Processor file systems Procedure 12-41 JumpStarting the SunSparc Enterprise M4000/M5000 Single Platform Processor (Continued) 4 Enter the following command to reboot the server. 5dc04 Continued 68P02901W19-S 12-73 Oct 2009 . POST Sequence 01 CPU Check LSB#02 (XSB#01-0): POST 2. and press RETURN.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..

restore The system jump starts without any prompts and automatically restores the file systems.Restoring Single Platform Processor file systems Chapter 12: Backup Server Installation and Configuration Procedure 12-41 JumpStarting the SunSparc Enterprise M4000/M5000 Single Platform Processor (Continued) Sun SPARC Enterprise M5000 Server. 6 Once the system has rebooted. 5 At the OK> prompt.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. instance #1 • If the HSIP drivers are not attached: pciex1214.3350.3350.3350. Reboot the system to restart services by executing the following command as user root: /usr/sbin/shutdown -i6 -g0 –y Continued 12-74 68P02901W19-S Oct 2009 . Inc. On completion the SunSparc returns with the console login. instance #0 pciex1214. All rights reserved. instance #0 (driver not attached) pciex1214. execute the following command as user root: prtconf | grep pciex1214 Screen outputs similar to the following are displayed: • If the HSIP drivers are attached: pciex1214. using Domain console Copyright 2008 Sun Microsystems. execute the following command: boot cdrom -.

Continued 68P02901W19-S 12-75 Oct 2009 . Add one YP server name per line in the order of preference. On completion. type <control D> or Return on a line by itself.Operating Information: OMC-R System Administration Restoring Single Platform Processor file systems Procedure 12-41 JumpStarting the SunSparc Enterprise M4000/M5000 Single Platform Processor (Continued) 8 If the NIS is used as the naming service. 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. execute the following as root: ypinit -m To operate the NIS successfully. construct a list of the NIS servers. Questions are asked at the beginning of the procedure.

. updated netmasks updated timezone updated auto. longest 10 bytes.byaddr. 138bytes total /usr/lib/netsvc/yp/mkalias /var/yp/‘domainname‘/mail.aliases: 12 aliases. 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. updated aliases updated publickey updated netid /usr/sbin/makedbm /etc/netmasks /var/yp/‘domainname‘/netmasks.byaddr.Restoring Single Platform Processor file systems Chapter 12: Backup Server Installation and Configuration Procedure 12-41 JumpStarting the SunSparc Enterprise M4000/M5000 Single Platform Processor (Continued) 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.master updated auto.home updated ageing Continued 12-76 68P02901W19-S Oct 2009 . Can we destroy the existing /var/yp/omcadmin and its contents? [y/n: n] y After the last query. the procedure takes 5 minutes to 10 minutes to complete..Running /var/ yp /Makefile. The YP domain directory is /var/yp/omcadmin...aliases /var/yp/domainname/mail. Building /var/yp/omcadmin/ypservers.

• Final Configuration Tasks on page 12-86. • Preparing to restore the databases on page 12-78. • Restoring the PM database on page 12-82. 68P02901W19-S 12-77 Oct 2009 . to recover from the database changes.Operating Information: OMC-R System Administration Restoring databases on the Single Platform Processor Procedure 12-41 JumpStarting the SunSparc Enterprise M4000/M5000 Single Platform Processor (Continued) 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. proceed to Restoring databases on the Single Platform Processor on page 12-77. If there are running slave YP servers. execute the following command: yppush If there are no running slaves. • Taking databases offline and re-initializing INFORMIX on page 12-78. on hosts to be slave servers. Restoring databases on the Single Platform Processor • Overview of restoring databases on page 12-77. • Restoring the CM database on page 12-78. 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. execute the following command: ypinit 9 Execute the following command as user root: svcadm clear svc:/system/basicreg:default svcadm disable omc 10 After logging in.

The databases are restored using the backup tapes in the order they were taken. 2 Set up correct environment for the CM Database: mib_env 3 Ensure that the IDS is in Offline mode: svcadm disable –t informix/cm 4 Set up correct environment for the PM Database: omc_env 5 Ensure that the IDS is in Offline mode: 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 1 Log in to the Single Platform Processor as user root and execute the following commands: /usr/omc/sbin/gcon file /usr/omc/sbin/Configure_Informix /usr/omc/sbin/Initialize_Informix -CM 2 Switch to user informix: su – informix Continued 12-78 68P02901W19-S Oct 2009 . Taking databases offline and re-initializing INFORMIX Before performing the restore from tape. • The last daily (level 2) backup. both the PM and CM databases must be taken offline and INFORMIX must be re-initialized. • The last weekly (level 1) backup. Use the following procedure: Procedure 12-42 Taking databases offline and re-initializing INFORMIX 1 Log in to the Single Platform Processor as user informix. if it occurred after the last weekly backup. locate the following tapes: • The last monthly (level 0) backup.Restoring databases on the Single Platform Processor Chapter 12: Backup Server Installation and Configuration Preparing to restore the databases Before starting the restore process. if it occurred after the last monthly backup.

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 .sh 6 To restore from tape. Press the RETURN key to continue.Operating Information: OMC-R System Administration Procedure 12-43 Restoring databases on the Single Platform Processor Restore the CM database (Continued) 3 Set up correct environment: mib_env 4 Ensure that the IDS is in Offline mode: svcadm disable –t informix/cm 5 As user Informix. execute the following command: /usr/omc/sbin/set_tape_parameters. If more than one tape was used to back up the CM database. 8 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. 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 7 Load the tape marked (CM database) Level 0 Backup into the Single Platform Processor tape drive. the system prompts for further tapes to be entered in sequence.

/dev/mib_db_logs 3 3 78903 192000 7627 PO.Restoring databases on the Single Platform Processor Procedure 12-43 Chapter 12: Backup Server Installation and Configuration Restore the CM database (Continued) 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 2 20001 2 1 N informix physdbs 3 20001 3 1 N informix logsdbs 4 2001 4 1 N T informix tempdbs 5 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_db1 Continue restore? (y/n) Enter y to continue the restore./dev/mib_db_logs 4 4 921601 102399 102346 PO. Continued 12-80 68P02901W19-S Oct 2009 ./dev/mib_db 5 5 2 767998 767945 PO.

logpos 0x1309018 10:28:11 Physical Restore of rootdbs. 0 Rolled Back. 10:30:15 Quiescent Mode Press Ctrl-c to exit out of the tail -f command at any time. 10:30:10 Physical Recovery Complete: 0 Pages Restored 10:30:10 Logical Recovery Started. logsdbs. 0 Committed. 0 Bad Locks 10:30:14 Bringing system to Quiescent Mode with no Logical Restore. or y for a level 1 or 2 archive. check the contents of online. 11 For a level 0 archive. Continued 68P02901W19-S 12-81 Oct 2009 . 10:30:10 10 recovery worker threads will be started.log_MIB as follows: tail -f /usr/informix/online. Checkpoint loguniq 13. 12 The following text is displayed: Program over. The following text is displayed: Do you want to restore log tapes? (y/n) Enter n.Operating Information: OMC-R System Administration Procedure 12-43 9 Restoring databases on the Single Platform Processor Restore the CM database (Continued) The following text is displayed: Do you want to back up the logs? (y/n) Enter n.log_MIB Output similar to the following example is displayed: 10:28:10 Checkpoint Completed: duration was 0 seconds. mib_db_sp1 Completed. physdbs. 0 Open. logpos 0x1309018 10:30:10 Physical Recovery Started. 13 In a separate login session. 10:28:11 Checkpoint Completed: duration was 0 seconds 10:28:11 Checkpoint loguniq 13. 10 The following text is displayed: Restore a level 1 or 2 archive (y/n) Enter n. 10:30:13 Logical Recovery Complete.

Press the RETURN key to continue. 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 7 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.Restoring databases on the Single Platform Processor Procedure 12-43 Chapter 12: Backup Server Installation and Configuration Restore the CM database (Continued) 14 Remove the backup tape from the tape drive. 8 Output similar to the following example is displayed: Archive Tape Information Tape type: Archive Backup Tape Online version: Informix Dynamic Server 2000 Version 10. the system prompts for further tapes to be entered in sequence.sh 6 To restore from tape. 15 Once Quiescent Mode is displayed in the log.00. execute the following command: /usr/omc/sbin/set_tape_parameters.00 UC4 Continued 12-82 68P02901W19-S Oct 2009 . 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 1 Log in to the Single Platform Processor as user root and execute the following: /usr/omc/sbin/gcon file /usr/omc/sbin/Configure_Informix /usr/omc/sbin/Initialize_Informix -PM 2 Switch to user informix: su – informix 3 Set up correct environment: omc_env 4 Ensure that the IDS is in Offline mode: svcadm disable –t informix/pm 5 As user Informix.

Operating Information: OMC-R System Administration Procedure 12-44 Restoring databases on the Single Platform Processor 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] 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 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 5 20001 5 1 N informix omc_db_sp2 6 20001 6 1 N informix omc_db_sp3 7 20001 7 1 N informix omc_db_sp4 8 20001 8 1 N informix omc_db_sp5 9 20001 9 1 N informix omc_db_sp6 Continued 68P02901W19-S 12-83 Oct 2009 .

Restoring databases on the Single Platform Processor Procedure 12-44 Chapter 12: Backup Server Installation and Configuration Restore the PM database (Continued) 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 4 4 2 1024098 241186 PO./dev/omc_db_logs 3 3 127003 396800 12747 PO./dev/omc_db5 9 9 2 1023998 487565 PO. Continued 12-84 68P02901W19-S Oct 2009 ./dev/omc_db_temp Continue restore? (y/n) Enter y to continue the restore./dev/omc_db2 6 6 2 1023998 650740 PO. 9 The following text is displayed: Do you want to back up the logs? (y/n) Enter n. 10 The following text is displayed: Restore a level 1 archive (y/n) Enter n./dev/omc_db6 10 10 2 1023998 1023945 PO./dev/omc_db3 7 7 2 1023998 183648 PO./dev/omc_db1 5 5 2 1024098 215855 PO./dev/omc_db4 8 8 2 1023998 773840 PO.

0 Committed. 14 Once Quiescent Mode is displayed in the log. The following text is displayed: Do you want to restore log tapes? (y/n) Enter n.Operating Information: OMC-R System Administration Procedure 12-44 11 Restoring databases on the Single Platform Processor Restore the PM database (Continued) For a level 0 archive. 10:36:47 Checkpoint loguniq 13. 10:39:14 Logical Recovery Started. 0 Open. The following text is displayed: Program over 12 In a separate login session. 10:39:18 Logical Recovery Complete.log_OMC Output similar to the following example is displayed: 10:36:47 Checkpoint Completed: duration was 0 seconds. 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 . 0 Rolled Back. 10:39:14 10 recovery worker threads will be started. logpos 0x469018 10:39:14 Physical Recovery Started. 0 Bad Locks 10:39:19 Bringing system to Quiescent Mode with no Logical Restore. check the contents of the online.log_OMC as follows: tail -f /usr/informix/online. 68P02901W19-S 13 Remove the backup tape from the tape drive. 10:39:20 Quiescent Mode Press Ctrl-c to exit out of the tail -f command at any time. or y for a level 1 or 2 archive. 10:39:14 Physical Recovery Complete: 0 Pages Restored.

is available for the processor being restored. 2 Execute the omc_db_maint utility as follows: $OMC_TOP/current/sbin/omc_db_maint 3 $OMC_TOP/current/sbin/omc_db_maint: more $OMC_TOP/logs/omc_db_maint. perform the following commands: Procedure 12-45 Final Configuration Tasks 1 Log in as user root. • JumpStarting the GUI Server Processor on page 12-87.Restoring GUI Server file systems using ufsrestore utility Chapter 12: Backup Server Installation and Configuration Final Configuration Tasks When the databases are fully restored. 4 As user omcadmin. Restoring GUI Server file systems using ufsrestore utility • Overview to restoring GUI Server file systems using ufsrestore utility on page 12-86. • Overview of restoring the GUI Server file system on page 12-93. make sure that a copy of the most recent set of complete file system level 0 backup tapes created using backup_MMI. 12-86 68P02901W19-S Oct 2009 . CAUTION The procedure destroys any data on the disks and overwrites the disks with data from the backup tape.<mm>to the current month. Before commencing the restore procedure. • Restoring /omcgen file system on page 12-96. 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. and <dd> to the current day in this month.<yy><mm><dd> Where <yy>refers to the current year. • Rebooting the GUI Server on page 12-97. • Restoring root (/) file system on page 12-94. • Restoring /usr/omc file system on page 12-96. execute the following command: svcadm enable omc At this stage the Single Platform Processor has been restored.

to continue Press Enter to continue. After the install questions have completed. An incorrect answer may very likely cause problems. 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. the system will be wiped and installed from scratch. a Sunblade 150 GUI Server. 3 When the boot command is entered. as an example. Press -=ENTER=. you will have a chance to approve or change your settings. It is essential that you provide correct answers to all of the following questions. enter the following command to perform a hands-free installation of Solaris 10 and all StorEdge Enterprise products on the GUI Server: boot cdrom Screen output similar to the following is displayed: The following is sample output that can be expected during the install. you can accept it by pressing the ENTER key. If a default response exists. 2 From the ok prompt. 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 ([]). Continued 68P02901W19-S 12-87 Oct 2009 . Once the settings have been approved.Operating Information: OMC-R System Administration Restoring GUI Server file systems using ufsrestore utility This procedure uses. with the following file systems: / /omcgen /usr/omc JumpStarting the GUI Server Processor Procedure 12-46 Jumpstart a GUI Server 1 Insert the GSR9 DVD in the DVD-ROM drive of the GUI Server.

Screen output similar to the following appears: Motorola GSM OMC-R GUI Server Installation ========================================== 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 Server’s primary hostname: Enter the hostname. NOTE A host name must be of at least two characters. Example: 255. This should be set to the IP address that your GSM OMC-R GUI Server will be known as on your local LAN. 5 A prompt is displayed requiring the IP address to be entered. Screen output similar to the following is displayed: Your GSM OMC-R GUI Server needs to have an IP address associated with the primary hostname. It can contain letters. Enter the GSM OMC-R GUI Server’s IP address: Enter the IP address. 6 A prompt is displayed requiring the Netmask address to be entered. This should be set to the netmask that your GSM OMC-R GUI Server will on your local LAN. Screen output similar to the following is displayed: Your GSM OMC-R GUI Server needs to have a netmask associated with the primary IP address. Illegal characters are: !”£$%^&*(){}~@?>:<|. Continued 12-88 68P02901W19-S Oct 2009 .Restoring GUI Server file systems using ufsrestore utility Procedure 12-46 4 Chapter 12: Backup Server Installation and Configuration Jumpstart a GUI Server (Continued) A prompt is displayed requiring the hostname to be entered.[]_.255.0 Enter the GSM OMC-R GUI Server’s netmask: Enter the Netmask address. digits and minus signs (-). Letters must be lower case.255.

type n and then press Enter. Contact your system administrator for help. 9 If DNS is to be configured. The installation then proceeds to configure DNS. The installation will then continue to configure a timeserver. enter the requested value: Enter the Common Platform GSM OMCR’s 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. 8 A prompt is displayed that gives an option to configure DNS. press Enter and the following prompt is displayed: Enter the default router’s IP address: Enter the default router’s IP address. press Enter. Continued 68P02901W19-S 12-89 Oct 2009 . The user is prompted to enter the DNS Domain name and DNS server IP addresses. enter y. 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. If a default router is not required. Do you want to configure DNS? (y/n) [n]: n If DNS is not required. Screen output similar to the following is displayed: Motorola GSM OMC-R GUI Server Installation ========================================== 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. Screen output similar to the following is displayed: Motorola GSM OMC-R GUI Server Installation Motorola GSM OMC-R GUI Server Installation 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. After each prompt. it is necessary to type in the Domain name and to supply a primary DNS IP address.Operating Information: OMC-R System Administration Procedure 12-46 7 Restoring GUI Server file systems using ufsrestore utility Jumpstart a GUI Server (Continued) A prompt is displayed that gives an option to configure a Default Router.

g. The following message is displayed: Enter the timeserver’s name or IP address: Enter the timeserver name or IP address. and the installation continues to configure the NIS Domain name. omcadmin Enter the NIS domain name: omcadmin Enter the NIS Domain name. if you specify a name. 11 A prompt is displayed to enter the NIS Domain. 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 . press Enter. you must either have configured DNS or you must add an entry to /etc/inet/hosts for your timeserver.Restoring GUI Server file systems using ufsrestore utility Procedure 12-46 10 Chapter 12: Backup Server Installation and Configuration Jumpstart a GUI Server (Continued) A prompt is displayed that gives an option to configure a timeserver. However. If there is no timeserver to be configured. 12 A prompt is displayed requiring OMC-R server information: Motorola GSM OMC-R GUI Server Installation ========================================== OMC-R Server Configuration Your GSM OMC-R GUI Server must be connected to an OMC-R server. Screen output similar to the following is displayed: Motorola GSM OMC-R GUI Server Installation ========================================== 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. Screen output similar to the following is displayed: Motorola GSM OMC-R GUI Server Installation ========================================== NIS domain setup Your GSM OMC-R GUI Server requires Network Information Services (NIS) The NIS domain is a character string e. Do you want to configure a timeserver? (y/n) [n]: n If a timeserver is to be configured. enter y.

Enter the Common Platform GSM OMCR’s timezone: Continued 68P02901W19-S 12-91 Oct 2009 . . Contact your system administrator for help. press Enter and type in the timezone. Do you want to configure a printer?: n 14 A prompt is displayed to configure a timezone. US/Eastern US/Central US/Mountain US/Pacific Japan Enter the GSM OMC-R GUI Server’s timezone: Type y and press Enter to get a list of timezones. . You can configure a printer at this time or later.Operating Information: OMC-R System Administration Procedure 12-46 13 Restoring GUI Server file systems using ufsrestore utility Jumpstart a GUI Server (Continued) A prompt is displayed requiring Printer information: Motorola GSM OMC-R GUI Server Installation ========================================== Printer Configuration Your GSM OMC-R GUI Server may have a printer attached. Australia/West Brazil/Acre Brazil/DeNoronha Brazil/East Brazil/West Canada/Atlantic If your timezone is known. Press the space bar to navigate this list. Australia/ACT Australia/Broken_Hill . Motorola GSM OMC-R GUI Server Installation ========================================== Timezone Configuration Your Sun-Based GSM OMC-R GUI Server will need to have a timezone configured.

press Enter to accept.3. Type in any updated values as necessary. Press Return to step through all the configuration values that have been entered from point 4 onwards. Motorola Common Platform GSM OMCR GUI Server Installation .33.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.255. 16 The password configuration prompt appears next.0 SPLAT_NAME: somc57 SPLAT_IP: 175.44.Summary =================================================================== Primary Interface Printer ------------------------HOSTNAME: somc5 Install printer?: n IP: 175. However.255.4 Networking ---------Default Router: 175.Restoring GUI Server file systems using ufsrestore utility Procedure 12-46 15 Chapter 12: Backup Server Installation and Configuration Jumpstart a GUI Server (Continued) A summary of all of the values entered is presented. type y and press Enter.44. These values will be in square brackets. Enter and confirm the passwords for the users when prompted.3.44.Password Configuration ========================================== The system will now prompt you for passwords for the following users: root Enter root’s password: Re-Enter root’s password: Continued 12-92 68P02901W19-S Oct 2009 . if a value needs to be modified.111 NETMASK: 255. Screen output similar to the following is displayed: Motorola GSM OMC-R GUI Server Installation Configuration .

44. Refer to the backup_MMI <datestamp> log file for the particular system. continue with a similar format as below for restoring these file systems. the GUI Server’s tape drive or the Single Platform Processor tape drive. 2 If you are using the tape drive on the GUI Server Processor then.227 NETMASK: 255. 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 .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. as user root on the Single Platform Processor. Motorola GSM OMC-R GUI Server Installation .255.3. The following procedure describes how to perform a complete GUI Server filesystem restore using the tape drive in the Single Platform Processor.0 Would you like to enable network services? (y/n) [n]: n Note: Entering y enables debugging mode. as user root on the GUI Server processor. 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.255. The log files for this section can be found in /var/install/logs. If extra file systems are to be restored. The GUI Processor reboots automatically. 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. Use the following procedure to prepare for the restore: Procedure 12-47 Prepare for the restore 1 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. 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.Operating Information: OMC-R System Administration Procedure 12-46 17 Restoring GUI Server file systems using ufsrestore utility Jumpstart a GUI Server (Continued) The final prompt gives the option to enable the Network Services.

set mode anyway? [yn] Enter y. a tape drive on the GUI Server. Continued 12-94 68P02901W19-S Oct 2009 . Specify next volume #: When the following prompt is displayed. that is.equiv > add /etc/ssh > add /etc/mail/sendmail. Procedure 12-48 1 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. All warnings regarding the files already existing and those related to being unable to create soft links. Follow Procedure 12-48 if you are using a local tape drive. Specify next volume #: 2 The following prompt is displayed: Directories already exist. Restoring root (/) file system Use the following procedure to restore the first volume on the tape (/ file system). only customizations are restored.Restoring GUI Server file systems using ufsrestore utility Procedure 12-47 Chapter 12: Backup Server Installation and Configuration Prepare for the restore (Continued) 3 As user root. Unless you know which volume your file(s) are on you should start with the last volume and work towards the first. As the / file system has already been restored during the GUI server jumpstart. enter 1.cf > extract You have not read any volumes yet. can be ignored. 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. 4 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.

‘? [yn] Enter y. 3 The following prompt is displayed: Directories already exist. Procedure 12-49 1 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. 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. 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 4 68P02901W19-S Execute the following command: ufsrestore > quit 12-95 Oct 2009 . Additional extractions can be configured as part of this procedure. If prompted for a password. ufsrestore ufsrestore ufsrestore ufsrestore ufsrestore 2 > > > > > add /etc/inet/* add /etc/hosts.cf extract The following prompt is displayed: set owner / mode for ’. enter the root password of the Single Platform Processor. As the / file system has already been restored during the GUI server jumpstart. 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. only customizations are restored.‘? [yn] Enter y.equiv add /etc/ssh add /etc/mail/sendmail.Operating Information: OMC-R System Administration Procedure 12-48 3 Restoring GUI Server file systems using ufsrestore utility Restoring the first volume on the tape (/ file system) (Continued) The following prompt is displayed: set owner / mode for ’.

that is. a tape drive on the GUI Server. 12-96 68P02901W19-S Oct 2009 . that is. enter the root password of the Single Platform Processor. Procedure 12-51 Using the Single Platform Processor Enter the following commands: 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. a tape drive on the GUI Server. enter the root password of the Single Platform Processor. If prompted for a password. If prompted for a password. 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. Procedure 12-52 Restoring /usr/omc file system Enter the following commands: 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. can be safely ignored.Restoring GUI Server file systems using ufsrestore utility Chapter 12: Backup Server Installation and Configuration Restoring /omcgen file system All warnings regarding files already existing and those related to being unable to create soft links. Follow Procedure 12-50 if you are using a local tape drive. Follow Procedure 12-52 if you are using a local tape drive. Procedure 12-50 Using a local tape drive Enter the following commands: 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.

Before commencing the restore procedure. 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 Screen output similar to the following is displayed: Rewinding Tape . Rebooting the GUI Server Reboot the GUI Server by entering the following command as user root: /usr/sbin/shutdown -i6 -g0 –y Selective File restore using restore_splat This utility enables selective restore of data from any Single Platform Processor file system that has been stored on a backup tape. Please Wait Ufs directory number 1 File System to restore /home Ufs directory number 2 File System to restore /solbak Ufs directory number 3 File System to restore /omcgen Ufs directory number 4 File System to restore /usr/omc Ufs directory number Continued 68P02901W19-S 12-97 Oct 2009 .Operating Information: OMC-R System Administration Procedure 12-53 Selective File restore using restore_splat Using the Single Platform Processor Enter the following commands: 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. 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.

. Please Wait Warning: ./lost and found: File exists Warning: ./omcadmin: File exists Warning: ./omcread: File exist 68P02901W19-S Oct 2009 .Selective File restore using restore_splat Procedure 12-54 Chapter 12: Backup Server Installation and Configuration Perform a selective restore (Continued) 5 File System to restore /usr/omc/ne_data Ufs directory number 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 ..

Chapter 13 Troubleshooting ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 68P02901W19-S Oct 2009 13-1 .

• Device busy error on page 13-49. • CDE login failure on page 13-36. • OMC-R system information on page 13-8. • Troubleshooting the LAN on page 13-37. • File access problems on page 13-24. • Onperf utilities on page 13-53. • Checking and recovering database tables on page 13-70. • Checking the system processor hardware on page 13-99.25 failure on page 13-39. • Configuring a Timeserver on page 13-102. • Power failure on page 13-97. • Replacing hard disk on system processor Sunfire/Netra 440/Netra 20 on page 13-43. • StorEdge Enterprise Backup problems on page 13-51. • Moving a machine with a forced link speed on page 13-41. • Logical Vol Mgr troubleshooting on page 13-42. • Setting FM audit and disk usage limits on page 13-88. • X. • Common Desktop Environment problems on page 13-33. 68P02901W19-S Oct 2009 . • Checking disk mirroring on page 13-47. • OMC-R software process errors on page 13-25.Overview Chapter 13: Troubleshooting Overview ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ The following topics are described in this chapter: 13-2 • Assessing a problem on page 13-3. • Ejecting DVD-ROMs on page 13-50. • Alarms on page 13-78. • Resetting boot devices on page 13-28. • Using neighbor statistics on page 13-91. • Full file systems on page 13-21. • Database failure on page 13-52. • Core file generation on page 13-6.

ensure that the information acquired is collated before telephoning the support personnel. B dropped. When contacting the Customer Network Resolution Centre at the end of a problem diagnosis. provides a solution. A printout of any GUI displays. 68P02901W19-S 13-3 Oct 2009 . Details of database access at the time of the fault. • 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. • Problem title (a one-line description of the problem).Operating Information: OMC-R System Administration 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. Any event log details produced. • Date and time of fault. contact the local Customer Network Resolution Centre with the information requested in the checklist that follows. The load details on the BSS at the time of the fault. Any software fault management events. For example: A called B. Preliminary checklist Ensure that the following information is readily available when contacting the local Motorola support centre: • Operator name. Location of B. Contacting Motorola In the event of a support requirement. including the call scenario at the time of the fault. and if possible.

problems with the event manager or X. Keep a printout of relevant parts of the audit log file and the IPC log files (where appropriate). For example. Fault severity. This should be archived to tape and sent to Motorola. As soon as possible. Details of a core dump file. • Urgency of response required: Immediate. Next software release. 13-4 68P02901W19-S Oct 2009 . In a future software release. Does not affect the day-to-day running capabilities of the OMC-R software.25 fall into this category. Serious . including the following OMC-R details: Any error messages. This can be determined from the audit log or the GUI menu option that was being used when the problem occurred. Annoying . if one has been produced.indicates a problem that may affect operations by being an inconvenience or producing misleading or redundant outputs.indicates that a major portion of system functionality is affected.indicates fault correction is required to ensure that the software conforms to certain standards. but the fault does not prevent the system from meeting its primary requirements. System configuration details. Cosmetic . Note the processor and component (or area) of the system affected. System configuration details.indicates that the problem impacts the critical functionality of the system.Preliminary checklist Chapter 13: Troubleshooting The BSS software version. categorized as follows: Service affected . The OMC-R software version. • Detailed description of the problem.

usually causing the affected processor to reboot. • Operating system halt (panic) If the UNIX operating system on any of the processors detects an internal error.25 software. network connections (for example. • Power failures An ac power failure causes the OMC-R processors to reboot when the power is restored. This is known as a panic condition. or misuse of GUI command procedures. it can stop processing. Uninterruptible Power Supplies (UPSs) could be used to power all the OMC-R hardware components. Such failures can be caused by hardware malfunction. the whole OMC-R system must be restarted and a core dump taken. packet switch). such as an OMC-R stop/start. Further troubleshooting information can be found in the manual OMC-R Online Help. thus providing some tolerance to power failures. Network Operation. The error message must be identified. • Hardware failures A hardware failure on one of the SPARC processors is likely to stop that processor functioning. X. • Network Element (NE) connection failure Connections between the OMC-R and the NEs can fail intermittently or permanently. must be taken. 68P02901W19-S 13-5 Oct 2009 . and the area of the system affected must be located and the remedial action. In some cases.Operating Information: OMC-R System Administration 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.

Application core dumps If a fatal error occurs during the operation of either the application programs or the GUI modules. the user omcadmin is mailed.n) and Operating System (OS) name list (unix. core. core_presence utility The core_presence utility checks for the occurrence of a core file on the system processor. The parameter n increases each time the savecore utility is run. If a core file is found. 13-6 68P02901W19-S Oct 2009 . in the following directory: $OMC_TOP/logs Retrieve the memory dumps and return them to Motorola for analysis. and is the same value for both the files. the savecore utility copies it to the /var/adm/crash directory. 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.n) should be archived to tape and removed from the disk as soon as possible. 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. Operating system core dumps If a fatal error occurs within the operating system of the system processor.Core file generation Chapter 13: Troubleshooting Core file generation ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Overview of generating core files The gcore command provides a core image of a running process. The memory dump files (core. After reboot. the respective programs will terminate and create a memory dump. a memory dump is written on the dump partition of the system disk.

contact Sun support for instructions on how to address them. generate a core file of the process. 3 If the system processor has any kernel problems. execute the following commands: gcore -o <filename> <process_id> Where <filename> and <process_id> are the file name and process ID of that particular OMC-R process. Copy the checklist provided in Table 14-9 to record the checks. execute the following commands: 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. 2 If an OMC-R process is causing severe problems.Operating Information: OMC-R System Administration Checking core dumps Checking core dumps Use the following procedure to check core dumps. Procedure 13-1 68P02901W19-S Checking core dumps 1 Check the presence of a core file when a fatal error occurs during the operation of either the application programs or the GUI modules. As user root. remove them as they can consume large amounts of disk space. The output from the gcore command indicates the name and location of the core file. As user root. 13-7 Oct 2009 . 4 If core files are not required.

03. 3:16 ‘7 users load average: 0. system activity and system swap areas used by the memory manager. 0. Additionally.Z Where: is: mm the month. OMC-R log files The log files stored in /usr/omc/logs/sys_info directories are generated every 10 minutes on the system processor. process list.05 13-8 68P02901W19-S Oct 2009 . 0. System uptime The following command shows how long the system has been up: /usr/ucb/uptime In response to this command. xx the minute the file was generated. Examining these files can determine whether specified processes are running and can reveal the behavior of the system. hh the hour. The commands described in this section are used to access the information contained in the sys_info files. disk status. showing system up time.054.OMC-R system information Chapter 13: Troubleshooting OMC-R system information ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Obtaining system information When a problem occurs on the OMC-R. The sys_info files have the following naming convention: statmmddhhxx. information can be retrieved from the log files stored in the /usr/omc/logs and the /usr/omc/logs/sys_info directories. dd the day of that month. an output similar to the following example is displayed: 1:28pm up 2day(s). the systat script can be used to create a file that reflects the status of the system.

PID Process id of the process. each column having a column heading. Size of the swappable processes image in main memory. PRI The priority of the process. Higher number means lower priority. the meaning of which is explained in Table 13-1. ADDR SZ Memory address of the process. PPID C The process id of the parent process. an output similar to the following example is issued: SunOS The following command: uname -a produces a more detailed response. used in priority computation. NI Nice value. Processor utilization for scheduling. Table 13-1 Output from ps -elf command Meaning Column heading F Flags associated with the process. Continued 68P02901W19-S 13-9 Oct 2009 . UID The login name of the process owner.Operating Information: OMC-R System Administration Machine architecture Machine architecture The following command gives the details of the machine architecture: uname In response to this command.9 Generic_118558-02 sun4u sparc SUNW. as follows: SunOS somc57 5.Ultra-Enterprise Current processes The following command gives the information about what processes are running: /bin/ps -elf | more Output is displayed in columns. S The state of the process.

STIME Starting time of the process given in hours. it is necessary to take note of the state of the file systems. If the file systems are filling up. whereby functionality may be affected.State of the file systems Table 13-1 Chapter 13: Troubleshooting Output from ps -elf command (Continued) Meaning Column heading WCHAN The address of an event for which a process is sleeping. The message is printed when there is no controlling terminal. 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 0 0 0% /proc mnttab 0 0 0 0% /etc/mnttab fd 0 0 0 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% /usr/omc/ne_data/raw_stats Quite often when the file systems are full. Integrity of X. it is necessary to purge unwanted files. there are problems with the OMC-R. CMD The full command name and its arguments. it is necessary to ensure the integrity of X. This information is recorded in the sys_info files using the output of the /bin/df -k command.25.25 communications For the system to work correctly and to ensure proper communication between the devices. minutes and seconds. STIME is given in months and days. TTY The controlling terminal of the process. This is done by executing the following command as user root: /opt/SUNWconn/bin/x25stat The /opt/SUNWconn/bin/x25stat file shows the statistics for the X.25 port for which it is run. TIME The cumulative execution time of the process. 13-10 68P02901W19-S Oct 2009 . State of the file systems In any system. If process at the time of executing the ps command has been running for more than 24 hours.

* *.32841 Idle *.----.* Unbound Idle *.sunrpc 68P02901W19-S TCP: IPv4 Swind Send-Q Rwind State----------.------ ------.------Idle *.32790 Idle Idle *.32771 0 0 49152 0 LISTEN *.* *.32772 0 0 49152 0 LISTEN *.lockd *.32777 *.7938 Idle Idle *.---------.* *.nfsd *.177 Idle Idle *.-------------------.* *.sunrpc Unbound *.syslog Idle *. 0 0 0 0 49152 0 49152 0 49152 0 IDLE 0 IDLE 0 LISTEN *.----. *.----177 Idle Local Address Recv-Q Remote Address *.Operating Information: OMC-R System Administration 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 -------------.ntp Idle *.32775 Idle Idle Idle *.32797 *.32794 Idle Idle Unbound *.* Unbound UDP: IPv6 Unbound Local Address Remote Address State If ------.* Idle *.--------------------------------.32773 13-11 Oct 2009 .32792 Idle localhost.ntp Idle somc57.32801 Idle *.8937 dle *.32776 Idle Unbound *.32781 Idle Idle Idle Idle *.32847 *.* *.1023 *.32791 *.32771 *.1022 32789 *.ntp *.-----.1023 0 0 49152 0 BOUND *.

some processes may need to communicate with processes outside of their own machine.cfg file gives the channel number used by OMC-R processes needed to communicate externally to the machine on which the processes are stored.32778 0 0 49152 0 LISTEN *.System resources Chapter 13: Troubleshooting 0 0 49152 0 LISTEN *. 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. The /usr/omc/current/config/ipc. In the OMC-R.cfg file. /usr/bin/sar -ru | more This command sends its output to the sys_info file.shell 0 0 49152 0 LISTEN *.dtspc 0 0 49152 0 LISTEN *.* 0 0 49152 0 LISTEN The local address is machinename. This can be done using the ipc command.32774 0 0 49152 0 LISTEN *.shell *. The column state shows what condition the connection is in.32786 0 0 49152 0 LISTEN *.printer 0 0 49152 0 LISTEN *. 13-12 68P02901W19-S Oct 2009 .32782 0 0 49152 0 LISTEN *.ipc_channel specified in the ipc.

Operating Information: OMC-R System Administration 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 Chapter 13: Troubleshooting %sys %wio %idle 00:20:00 0 1 0 99 00:40:00 0 0 0 99 01:00:00 0 1 0 99 01:20:00 0 0 0 99 01:40:00 0 0 0 99 02:00:00 0 0 0 99 02:20:00 0 0 0 0 0 99 02:40:00 0 99 03:00:00 1 1 0 98 03:20:00 0 0 0 99 03:40:00 0 0 0 99 04:00:00 0 0 0 99 04:20:00 3 1 1 95 04:40:00 0 0 0 0 0 0 99 05:00:00 0 0 99 05:20:00 0 99 05:40:00 0 0 0 99 06:00:00 0 0 0 99 06:20:00 0 0 0 99 06:40:00 1 1 0 98 07:00:00 0 0 0 99 07:20:00 0 0 0 99 07:40:00 0 0 0 99 08:00:00 0 0 0 99 08:20:00 0 0 0 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 .

11 0 0 12 root 0 - 0 2539e608 0 1 0 9 0 0 0 0 27 0 24a6bf50 Y--P--.80 254bcd18 0 0 root 0 24a6a0d8 ---P--B 0 24a6a6f0 Y--P--.86 68P02901W19-S 1 1 omcadmin console 1 omcadmin console omcadmin - 0 252ac928 0 0 24a6c568 Y--P--.84 2551b918 0 0 24a6d7b0 Y--P--.On-Line -.40.81 omcadmin console 254f08c8 0 254e8328 0 Y--P--.10 console 0 24a694a8 0 0 0 0 root 0 root 0 1 omcadmin - 2 0 25525f28 13-15 Oct 2009 .Operating Information: OMC-R System Administration PM database status onstat -ukp | more IBM Informix Dynamic server Version 9.Up 04:58:21 -.82 1 - 0 24a6b938 Y--P--- omcadmin console 254e8e20 0 31 0 root 79 console 0 omcadmin console 24a6b320 ---P--D 15 0 0 - omcadmin 1 24a6ad08 Y--P--.83 0 0 omcadmin 1 0 0 0 24a6cb80 0 24a6d198 Y--P--.UC4 -.467968 Kbytes Userthreads address flags sessid locks nreads 1 user tty wait tout nwrites 24a67018 ---P--D root - 0 0 0 75 70 24a67630 ---P--F 0 root 0 903 24a67c48 --- 0 0 P--F 0 0 root - 0 0 723 24a68260 ---P--F 0 - 0 0 ---P--F 0 0 0 root 0 root 0 69 24a68878 - 0 0 0 24a68e90 ---P--F 0 - 0 0 ---P--F 0 0 - 0 24a69ac0 ---P--.85 25525430 0 24a6ddc8 Y--P--.

95 68P02901W19-S Oct 2009 .87 omcadmin console 0 255aaa30 0 1 0 24a6e9f8 Y--P--.92 25686728 0 1 0 omcadmin 0 25 active.78 25615ed80 1 1 console 1 0 0 omcadmin console 0 Y--P--. 128 total. 75000 total. 26 maximum concurrent Locks address wtlist owner lklist type key#/bsiz a110f98 0 HDR+S 100002 0 204 S S 0 S 0 S 100002 0 0 S 0 24a6ddc8 0 a42fcb8 0 100002 204 S 24a6d198 0 204 24a6e9f8 0 a42cdcc 100002 204 S 100002 24a6f628 0 0 100002 a417a84 0 S 204 0 S 24a70258 0 a433330 0 204 a412048 0 24a6c568 0 0 0 24a6fc40 a4121ec 0 204 0 a111094 S 100002 a4120f0 0 204 100002 100002 204 24a6ad08 0 204 0 100002 204 S a41209c 0 S 204 a11cfe0 0 100002 24a6bf50 a111040 0 24a6f010 0 24a6b938 0 0 100002 S 204 0 100002 0 24a6e3e0 0 a11113c 0 100002 rowid a110fec 0 204 24a6d7b0 0 a1110e8 0 0 0 100002 24a6cb80 0 0 tblsnum 24a6a6f0 0 0 204 S 15 active. 0 lock table overflows Profile dskreads pagreads bufreads %cached dskwrits pagwrits bufwrits %cached 3797 6447 13-16 60428 4059 537450 99.PM database status 0 Chapter 13: Troubleshooting 1 10 0 24a6e3e0 Y--P--.91 0 omcadmin - 0 24a6fc40 omcadmin console 0 2563fbc0 0 24a70258 Y--P--.89 25615120 0 24a6f628 Y--P--.88 255f8640 0 1 0 omcadmin - 0 24a6f010 Y--P--. 32768 hash buckets.29 1844 96.

Up 4 days 19:04:44 -.UC4 -On-Line -.19 11990eb8 0 1 0 1 41 0 11212d08 Y--P--.25 - 68P02901W19-S 11995c88 0 1 omcadmin 55 0 11213938 13-17 Oct 2009 .Operating Information: OMC-R System Administration 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.23 1 root - 47 11210260 ---P--- 11 1 tty nwrites 1120f018 ---P--D 0 1120fc48 ---P--F 0 0 user 298 omcadmin console 0 0 root 0 0 112120d8 omcadmin - 119d3cc0 0 0 112126f0 Y--P--.148480 Kbytes Userthreads address flags sessid wait tout locks nreads 1 root 0 - 47 0 0 279 1120f630 ---P--F 0 0 0 0 0 root 1167 root - - 0 11210878 ---P--B 12 0 0 0 omcadmin console 58 0 0 root 0 0 0 0 0 - 0 11210e90 Y--P--.10 117f5fc8 0 0 112114a8 Y--P--.21 11bae8a8 0 omcadmin - 1 34 0 11211ac0 ---P--D 15 - 0 Y--P--.40.24 omcadmin - 119950c8 0 0 11213320 Y--P--.

CM database status Chapter 13: Troubleshooting Y--P--.26 0 1 omcadmin 43 11a26888 0 11213f50 Y--P--.47 1 40 0 49 omcadmin - 1 0 11217010 Y-- omcadmin - 1 29 omcadmin - 11d47700 0 0 22 active.30 omcadmin - 11aedea0 0 0 112157b0 Y--P--.31 11b35c10 0 1 Y--P--.32 0 1 1 33 0 11215dc8 omcadmin 56 11b548d8 0 112163e0 Y--P--.28 11aaa168 0 1 41 23 omcadmin 0 11214b80 Y--P-29 omcadmin 38 1 11aaad78 0 1 0 11215198 Y--P--.27 omcadmin - 11a2c518 0 0 11214568 Y--P--. 128 total. 24 maximum concurrent Locks address wtlist owner lklist type tblsnum key#/bsiz a10ef98 0 HDR+S 0 100002 S 205 0 100002 HDR+S S 207 0 S 207 0 112163e0 0 207 11217010 0 0 S S a10f1e4 0 100002 a410048 0 207 0 112114a8 0 207 0 12120d8 0 13-18 0 112157b0 100002 a10f190 0 S a10f094 0 207 a10f13c 0 S 100002 0 100002 11214b80 0 0 100002 100002 11213320 0 207 a10f0e8 0 100002 a10efec a10f040 0 11213f50 0 0 0 112126f0 0 207 rowid 11210e90 0 100002 a41009c 0 S a4100f0 0 S 1 100002 207 11212d08 0 207 0 a410144 0 68P02901W19-S Oct 2009 .34 1c00598 0 1 P--.33 omcadmin - 11bc02b8 0 0 112169f8 Y--P--.

75000 total. 68P02901W19-S 13-19 Oct 2009 . 0 lock table overflows Profile dskreads pagreads bufreads %cached dskwrits pagwrits bufwrits %cached 1759 1886 900303 11443 88. The format of the systat script is as follows: systat There are no parameters supported by the script.15 0 usercpu 0 ovlock 0 15 compress seqscans 159 0 0 syscpu 0 lokwaits lockreqs deadlks 0 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. process list. showing system up time. 32768 hash buckets.33 2.80 1285 rewrite 115326 10626 2868 start delete 147445 102 commit 285872 4791 0 gp_read gp_write gp_rewrt gp_del gp_alloc gp_free gp_curs 0 0 0 0 ovuserthread ovbuff numckpts flushes 0 70. It can be run on the system processor.Operating Information: OMC-R System Administration 11213938 0 207 0 S S 11214568 100002 a4101ec 0 100002 207 0 11215198 0 207 0 11215dc8 0 0 100002 a410198 0 0 systat script S a410240 0 S 100002 207 S 100002 207 a410438 0 112169f8 0 0 16 active. The systat script is intended to run as a cron job and removes files older than seven days automatically. system activity and system swap areas used by the memory manager. disk status.77 isamtot open read write rollbk 776978 147 99. The script is located in $OMC_TOP/current/sbin.

refer to the Solaris AnswerBook.systat script Chapter 13: Troubleshooting 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 1 Login the system processor omcadmin and enter the password when requested. 0. enter the following command: zcat /usr/omc/logs/sys_info/<filename>.06.09.131.Z | more 5 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.05 who: console Apr 6 14:58 root pts/1 (10.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 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. the user prompt is displayed.9 Generic_ 118558-02 sun4u sparc SUNW. 3 To view the output files execute the command: ls -t /usr/omc/logs/sys_info/stat* | more 4 The name of the file to be viewed is the first filename in the list.6.Ultra-Enterprise /usr/ucb/uptime: 11:52am up 4 day(s). 21:14. 0. To display the contents of the output stat file. load average: 0. 2 Enter the following to run the systat script: /usr/omc/current/sbin/systat When the script is complete. 2 users. 13-20 68P02901W19-S Oct 2009 .

Identifying full file systems A file system shows it is full if its capacity is at 100%. look for any large files not expected to be present. 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.Operating Information: OMC-R System Administration Full file systems Full file systems ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Full file systems If file systems are filling up. 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. this indicates that the amount of data being stored is more than the system supports. the following command looks for any files larger than 1 Mbyte on the root file system. or that an administrator has made an error when trying to take a backup. 68P02901W19-S 13-21 Oct 2009 . For example. find / -size +1048576c -print If the root file system is full. Check which file system is creating the problem by executing the following command: df -k After identifying the problematic file system. Freeing up further disk space on the system processor If the previous procedure ( Identifying full file systems on page 13-21) does not rectify the problem.

as in the following example. deleting the files wherever necessary in order to maintain the usage of the disk file system below 85%. Continued 13-22 68P02901W19-S Oct 2009 . If in doubt. If this command results in any output. 2 Follow the steps in Procedure 12-6. then do not delete this directory. parser files. Use the following procedure to check if a file or directory is being used before removing a file or directory. 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. modify the cron jobs to run some of the maintenance scripts more frequently. Procedure 13-4 Removing a file or directory 1 Perform any in-house procedures for checking if a file or directory can be safely removed. • Raw statistics files. 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. • Core files. locate and remove any of the following files that are no longer required. 2 Execute the following command: env | grep <name> where <name> is the name of the file or directory to be deleted. 4 Execute the omc_db_maint script more frequently to clean up old cron logs.Removing files or directories Chapter 13: Troubleshooting Procedure 13-3 1 Freeing up further disk space on the system processor Identify. 3 If the system continually runs above the recommended values. do not delete the file or directory. For example. ev_logs and other OMC-R logs. • Log files.

for example. As user root. 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. execute the following commands: cd directorypath rm -f filename 3 Check the amount of available free memory and how active the system is by entering the following command as user root: /usr/bin/sar -ru | more 4 Check how full the file systems are by entering the following command as user root: df -k | more 5 For file systems that are over 100% full. log files and statistic files. Procedure 13-5 68P02901W19-S Checking disk usage 1 Check the disk usage of the system by entering the following command as user root: du -k | more 2 Remove any files that are not required and use too much disk space. old core files. 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 . Copy the checklist provided in Table 14-10 to record the checks.Operating Information: OMC-R System Administration Procedure 13-4 3 Checking disk usage Removing a file or directory (Continued) For files.

5 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). 2 Make sure that an entry exists for the NFS client in the /etc/dfs/dfstab file of the NFS server. this needs to be rectified using the following procedure: Procedure 13-6 Handling stale NFS file 1 Login as root on the NFS server. 13-24 68P02901W19-S Oct 2009 . use the Network File System (NFS).File access problems Chapter 13: Troubleshooting 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. execute the following commands: umountall -F nfs mountall If this solution does not work. 3 Execute the following command: shareall 4 As user root on the NFS client. reboot the NFS client by executing the following command: shutdown -i6 -g0 -y Remounting of the shared files automatically starts when the machine reboots.

4 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 /usr/omc/current/config -r informix +i 8 +a 4 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 /usr/omc/current/config -r informix +i 14 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 /usr/omc/current/bin/x25appl + 2 omcadmin 680 656 0 12:31:10 ? /usr/omc/current/bin/x25appl + 1 omcadmin 679 656 0 12:31:10 ? 0:00 0:00 Continued 68P02901W19-S 13-25 Oct 2009 . 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.Operating Information: OMC-R System Administration OMC-R software process errors OMC-R software process errors ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Analyzing OMC-R process errors If an OMC-R software error occurs. Use the following procedure to analyze OMC-R software process errors: Procedure 13-7 Analyzing OMC-R process errors 1 Check the error message displayed. Refer to Manual startup and shutdown of OMC-R software on page 7-12 for the procedure to stop and start the OMC-R. 3 Stop and restart the OMC-R software if the OMC-R software problem is severe. 2 Examine all the relevant OMC-R user's home directory structure for a core dump.

• emProxy . • downloader .Performance Manager Parser.X. • em_main .) 6 If the fault cannot be rectified. • cm and cmMib .Event Management List Manager.Load Management Uploader.Performance Manager Async. • RLogin . • uploader . • pm_main .Configuration Management.Event Management Router. • Parser . 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 .Load Management Downloader.Event Management Proxy.List of system processes Chapter 13: Troubleshooting Procedure 13-7 Analyzing OMC-R process errors (Continued) /usr/omc/current/bin/EventInterface + omcadmin 682 656 0 12:31:10 ? 0:00 /usr/omc/current/bin/x25appl + 5 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 /usr/omc/current/bin/x25appl + 6 omcadmin 686 656 0 12:31:11 ? 0:00 /usr/omc/current/bin/x25appl + 7 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 /usr/omc/current/bin/x25appl + 3 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.Remote Login. (Refer to Printing current OMC-R processes on page 2-35 for further information. 68P02901W19-S Oct 2009 . • em_lm_main .25 Applications.

Network Expansion.Call Success Monitor. 68P02901W19-S 13-27 Oct 2009 .Name server. GUI process GUI process There is one GUI process: gui . • smase .Operating Information: OMC-R System Administration • fm_audit .OMC Python.Event Interface. • Event_Interface . • audit . • gprsTrace . • pmProxy . • CSM_MAIN .OMC-R Graphical User Interface. • scheduler . • monitor . • resync .Resync Controller. • nameserver .GPRS Trace.Monitor.Audit.Gateway.GUI.SMASE.Resync. • ResyncCtrl .Scheduler. • gateway .PM Loader. • PmLoader .Call Trace. • OmcPyTom .OMC-R fault management audit. • NetExp . • callTrace .Performance Manager Proxy. • gui .

or 1 Bring the system to PROM level by executing the following commands as root: shutdown -i0 -g0 -y 2 This will power the processor down to PROM level. N440. When the OK prompt is displayed. enter the following command: setenv use-nvramrc? true 3 Proceed with specifying the boot disk block. 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. enter the following command: show-disks 4 On a Netra 440 which has been configured according to Installation and Configuration: OMC-R Clean Install (68P02901W47). At the OK prompt. 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. this command displays the following output: Continued 13-28 68P02901W19-S Oct 2009 .Resetting boot devices Chapter 13: Troubleshooting Resetting boot devices ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Bootup problems If a processor boots up in read-only mode or does not boot at all. SF4800.

c0t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@0. c1t31d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> Continued 68P02901W19-S 13-29 Oct 2009 .700000/scsi@1.0 2.0:a indicates slice 0 of disk 0 which is located in target 8.1/disk@8.1/disk b) /pci@1f.600000/pci@0/pci@9/LSILogic.0 4.0 3.600000/pci@0/pci@9/LSILogic.600000/pci@0/pci@8/pci@0/scsi@1/sd@0.sas@0/sd@16. SF4800.600000/pci@0/pci@9/LSILogic.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.Operating Information: OMC-R System Administration Procedure to reset a boot device Procedure 13-8 {34618} Resetting a boot device for a N20.600000/pci@0/pci@9/LSILogic. (For example. c1t22d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@0.) nvalias mirrordisk /pci@1d. c1t26d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@0.sas@0/sd@19.700000/scsi@2. c0t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@0.0:a nvalias bootdisk /pci@1d.0:a 6 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 7 Reboot the processor by entering the following command: boot Procedure 13-9 {34618} Resetting a boot device on an M4000 or M5000 1 Insert the Jumpstart DVD into the DVD-ROM drive on the Single Platform Processor. c1t27d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@0.0 5. N440.0 6. At the PROM level.700000/scsi@2. a disk@8.600000/pci@0/pci@8/pci@0/scsi@1/sd@1. c1t25d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@0.700000/scsi@2/disk g) /pci@1d.sas@0/sd@1b.1/disk h) /pci@1d.700000/scsi@2.sas@0/sd@1a. 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. or SF4900 (Continued) a) /pci@1f.0 1.600000/ide@d/cdrom d) /pci@1e.1/disk f) /pci@1d.1/disk@8.700000/scsi@1. type: ok boot cdrom -s 2 In SINGLE USER MODE.600000/ide@d/disk e) /pci@1d.700000/scsi@2/disk c) /pci@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).0 12.600000/pci@0/pci@9/LSILogic.0 7.600000/pci@0/pci@9/LSILogic.0 8. it is a boot device. do more to check it: # ls /a If the output is similar to the following display.log net sbin var devices kernel omcgen solbak vol Continued 13-30 68P02901W19-S Oct 2009 . # mkdir /a # mount /dev/dsk/c1t22d0s0 /a If the output is similar to following display. c2t25d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@10. c2t22d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@10.Try the next one: NOTICE: mount: not a UFS magic number (0x0) mount: /dev/dsk/c1t22d0s0 is not this fstype Otherwise.600000/pci@0/pci@9/LSILogic.sas@0/sd@1f. c2t30d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@10.sas@0/sd@16.600000/pci@0/pci@9/LSILogic. c2t28d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@10. c1t32d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@0.sas@0/sd@1e. First check the disks connected to c1 (Controller 1).600000/pci@0/pci@9/LSILogic.0 11.Procedure to reset a boot device Procedure 13-9 Chapter 13: Troubleshooting {34618} Resetting a boot device on an M4000 or M5000 (Continued) /pci@0.0 13.sas@0/sd@19.600000/pci@0/pci@9/LSILogic.sas@0/sd@1c.sas@0/sd@20.sas@0/sd@18.sas@0/sd@15. INFORMIXTMP etc lib opt system zones – – – – bin export lost+found platform tmp cdrom home mnt proc usr dev jvp. c2t24d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@10. c2t21d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> /pci@10. Try to mount the disks on /a one by one. it is not a boot device.0 9.600000/pci@0/pci@9/LSILogic.0 10.600000/pci@0/pci@9/LSILogic.

Type ^Y ( Control-Y ) to insert it in the command line.600000/pci@0/pci@9/LSILogic. execute the following commands: # ls -l /dev/dsk/c1t22d0s0 lrwxrwxrwx 1 root root 63 Apr 14 01:34 /dev/dsk/c1t22d0s0 -> .g.sas@0/sd@15. 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. e.600000/pci@0/pci@9/LSILogic./../.0:a 6 At PROM level.sas@0/disk d) /pci@0./devices/pci@10..600000/pci@0/pci@9/LSILogic.sas@0/disk has been selected.. ok nvalias mydev ^Y Continued 68P02901W19-S 13-31 Oct 2009 .600000/pci@0/pci@8/pci@0/scsi@1/disk q) NO SELECTION Enter Selection.. 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.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.Operating Information: OMC-R System Administration Procedure 13-9 4 Procedure to reset a boot device {34618} Resetting a boot device on an M4000 or M5000 (Continued) Now unmount the disk mounted on controller 1: # umount /a Repeat step 3 to find the boot mirror disk connected to c2 (controller 2).0:a # ls -l /dev/dsk/c2t21d0s0 lrwxrwxrwx 1 root root 64 Apr 14 01:34 /dev/dsk/c2t21d0s0 -> .600000/pci@0/pci@9/LSILogic. q to quit: c /pci@0.600000/pci@0/pci@9/LSILogic./devices/pci@0.600000/pci@0/pci@8/pci@0/scsi@1/disk c) /pci@0.sas@0/disk b) /pci@10.sas@0/sd@16.

Procedure to reset a boot device Procedure 13-9 Chapter 13: Troubleshooting {34618} Resetting a boot device on an M4000 or M5000 (Continued) for creating devalias mydev for /pci@10.0:a Now enter the SCSI id of the disk according the boot device name in given in step 5.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 Choose entries c and a from the list and set boot device by entering the following command. sas@0/disk@15.600000/pci@0/pci@9/ LSILogic. 7 13-32 Reboot the processor by entering the following command: ok boot 68P02901W19-S Oct 2009 . ok nvalias bootdisk /pci@0.

Users root and omcadmin have personalized front panel configuration files $HOME/. A current.dt directory which contains all of the user specific configuration information. This directory contains the customized configuration files (*. the files most likely to be changed are in $HOME/. A default system wide .dt) are also included in this directory. If a user customizes their session. Installing CDE CDE is installed along with the Solaris operating system using JumpStart as part of the upgrade/clean install on the GUI server.dt/sessions/current. The session is customized for root.dtprofile is located in /etc/dt/config/sys. Configuring CDE CDE is configured at installation time.dt action files are essentially callbacks for some of the menu items in the front panel.fp. The sys. The *.old directory also exists with the previous configuration.dt extension (the contents of which are irrelevant) in the directory /etc/dt/appconfig/appmanager/C/Desktop_Apps. Configuration files are copied from /usr/omc/config/local to /etc/dt/appconfig/types/C. Every user.dtwmrc. Generic session files are located in /etc/dt/config/C. icons and so on.fp) which describe the composition of the front panel. A generic dtwmrc file is located in /etc/dt/config/C/sys. omcadmin and other.dt/types/dtwm.dtprofile. Icon files are located in /etc/dt/appconfig/icons/C. including root and omcadmin. a CDE session will start automatically. 68P02901W19-S 13-33 Oct 2009 .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 action file should have a corresponding file with the same name without the .Operating Information: OMC-R System Administration 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. The file sys/resources contains the number of workspaces (defaults to one channel OMC-R). Once a user has logged into one of the machines. menu items. Action files (of the form *. should have a $HOME/.

and correct any errors in the above files. the user should select the options menu from the login screen. User root has an omc_admin icon which provides an interface to the User Admin. Both root and omcadmin have a CRON icon that allows access through a GUI to the crontab files. remove the control file which disables the Print Manager access to other users. This is the default window manager for OMC-R operators and administrators.dtprofile: DTSOURCEPROFILE=true If this occurs. • $HOME/. only the root user has access to the Print Manager. • $HOME/. Group Admin. 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. and StorEdge Enterprise Backup utilities. To enable other users to access this. then select Failsafe session.Normal operation of CDE Chapter 13: Troubleshooting Normal operation of CDE CDE starts automatically.profile (for users of Bourne shell and Korn shell). 13-34 68P02901W19-S Oct 2009 . Errors in user profiles Errors in the following files could potentially stop users from logging onto the system: • $HOME/. It runs until the operator or administrator logs out.login (for C shell users) if the following line is uncommented in $HOME/. If this directory is not correctly mounted then the user receives an error on login. Enabling/disabling the Print Manager By default.dtprofile. select sessions. Executing shareall (as root) on the system processor followed by mountall can clear up this problem.

dt/errorlog can be useful for diagnosing errors. This file should be removed in order to rerun the CDE setup.fpbak file has to be copied to each user's directory using the following procedure. the following file should exist: /etc/dt/.fpbak /home/username/. the Printer. The files $HOME/.dt/startlog and $HOME/.Operating Information: OMC-R System Administration 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 1 Login as root and enter the following commands: cd /etc/dt/appconfig/types/C mv Printer. 68P02901W19-S 13-35 Oct 2009 .fp Printer.fpbak 2 Restart the CDE Worksession using the Restart option from the pulldown options of the left mouse button. Other CDE problems If CDE has been set up.cde_configured. Disabling the Print Manager If the Print Manager needs to be disabled on a per user basis.fp 2 Restart the CDE Work session using the Restart option from the pull down options of the left mouse button.dt/types/Printer. Procedure 13-11 Disabling the Print Manager 1 Login as root and enter the following command (on one line): cp /etc/dt/appconfig/types/C/Printer.

Procedure to recover from CDE login failure Use the following procedure to rectify the CDE configuration. NOTE In the case of user root CDE configuration being corrupt.dt/. 13-36 2 Reconfigure the affected user's CDE environment by entering the following commands: rm /home/<user_name>/.CDE login failure Chapter 13: Troubleshooting CDE login failure ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Overview of CDE login failure If a user cannot login through the CDE desktop. use the telnet application from another processor in order to gain access. either on a user level or on a system wide level.cde_configured /usr/omc/current/sbin/CDE_setup <user_name> 3 If this fails to work. 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. this indicates that the CDE configuration has become corrupt. 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 .

or events or alarms are arriving late. bridges. 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. the GUI) and the server (the Motif window manager). 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. To check the LAN to a remote GUI server. there is a LAN performance problem. 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. If windows and forms are very slow to update. If the updates to the screen are slow.025 percent or more of Ipkts or Opkts).Operating Information: OMC-R System Administration Troubleshooting the LAN Troubleshooting the LAN ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Long response times to commands If the response times to commands are becoming long. and check that there are not too many processors connected to the LAN. 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 0 525302 Net/Dest 0 0 Address 8232 loopback 0 localhost hme0 1500 somc57 Ipkts Ierrs Opkts 2416840 0 somc57 Oerrs Collis 2416840 1705354 0 0 Check for the following scenarios: • The number of Ierrs or Oerrs is high (0. there may be a backlog of X traffic. Taking a long time to open maps or access large files remotely could be due to NFS mount problems.11 protocol is used to pass windowing information between the client (for example.11 over the LAN. and so on). or the command can be run directly from the command line. this may be related to the use of X. • Collis (collisions) is greater than 10 percent of Ipkts or Opkts. Check the LAN (routers. 68P02901W19-S 13-37 Oct 2009 . If any of the above are true. and LAN performance tests should be run. NOTE The nestat output can be found in the /usr/omc/logs/sys_info/stat* files which are run every 10 minutes. The X.

3 If the LAN interface is not running.: can be used to specify remote access privileges to certain trusted hosts.101 175. use the ping utility to determine the connectivity status of the LAN. Each host within the OMC-R LAN must have a unique line entry specified within this file. check the LAN cabling and associated hardware. User file ~omcadmin/. check the following LAN files: User file /etc/hosts: contains the information that maps the Internet addresses to the host names. 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.101: is alive 13-38 2 If the LAN interface is running.41. 68P02901W19-S Oct 2009 .3. 4 If the fault cannot be rectified.equiv. collect all the information before contacting the local Motorola support centre. Each line contains the name of the remote system and the users who have access rights to it.rhosts: can be used to specify trusted hosts at a user level.3.41. User file /etc/hosts. Refer to the Solaris AnswerBook for further information.Checking if packets can be sent and received Chapter 13: Troubleshooting Checking if packets can be sent and received If there is a failure within the LAN.

25 trace on the system processor As user root.25 trace on the system processor Use the following procedure to use the X. all synchronous ports are traced at Level 3 (X. It is recommended to assign the output to a file.25 failure X.Operating Information: OMC-R System Administration X. Network Operation for information on alarm handling. Starting x25tool Refer to Starting and stopping X.25 failure ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Overview of X. Tracing the synchronous communication uses the X25trace utility. should be performed in consultation with a Motorola engineer. X. Refer to the manual OMC-R Online Help.25 trace procedure: Procedure 13-14 1 Running X.25).25 failure Alarms are indicated on the relevant NE subscription window(s).25). Tracing can be performed at either Level 2 (LAPB) or Level 3 (X. NOTE Analysis of data produced from tracing a synchronous port or executing the x25stat utility on a particular port.25. display the status of the X. By default. • X.25 by entering the following command: /opt/SUNWconn/bin/x25stat Continued 68P02901W19-S 13-39 Oct 2009 .25 on page 9-9 for procedures on starting and stopping the X.25 status utilities. The following troubleshooting aids should be used to determine the possible fault: • Synchronous communications trace. It is strongly recommended that the tracing utility is not left running in the background for long periods of time.

The x25trace command requires root permissions to execute. In this example. the X.25 utilities.25 Packet layer interface for link 0. Note down the process id number that is displayed. taken when the network is known to be working correctly. Reset the packet counts regularly.25 data to be input/output to/from the X.Displaying x25stat Chapter 13: Troubleshooting Procedure 13-14 Running X. 3 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 4 Display X. the trace is performed on Level 3.25. and observe any changes in packet count distribution. Enter the following to start the trace: /opt/SUNWconn/bin/x25trace -i /dev/x25 -l 0 > trace_link0 & Allow enough time for X. 5 If the fault cannot be rectified. 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 The following is displayed: PER LINK STATISTICS FOR X25 ____________________________ Link : 0 State : Unknown ------------------------------------- Packet type TX RX ------------------------------------0 0 confirm 0 RNR Restart 0 0 Resets RR 0 0 0 Interrupts 0 0 Registration (total) 0 0 Restart 0 Diagnostic 0 0 0 0 0 0 0 Reg confirm 0 0 0 Reset confirms 13-40 0 Call accept 0 0 Call 0 Packets Bytes (total) 0 68P02901W19-S Oct 2009 .25 link. It is also useful to keep some x25stat outputs.25 trace on the system processor (Continued) 2 The x25trace command captures information about each packet and /or frame sent and received by SunLink X. These samples can be used later to compare with output taken when the network is not working correctly. collate all the information before contacting the local Motorola support centre.

d/S31linkspeed 68P02901W19-S 13-41 Oct 2009 . If the Single Platform Processor is later moved to a network port which is not 100 Mbps full duplex.Operating Information: OMC-R System Administration 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. In order to re-instate auto negotiation. Ensure that the task is completed as user root on the Single Platform Processor by executing the following command: rm /etc/rc2. the script /etc/rc2.d/S31linkspeed needs to be removed. the Single Platform Processor may not be able to connect to the network.

Recovery should only be performed by a Solaris Logical Vol Mgr expert.Logical Vol Mgr troubleshooting Chapter 13: 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. 13-42 68P02901W19-S Oct 2009 . NOTE Incorrect maintenance and administration of Logical Vol Mgr could cause the system to crash and possibly lose the information held on the disks. or a file system problem caused by file system corruption.

Use the following procedure to recover a lost disk : Procedure 13-15 Recovering a lost disk 1 Change to the following directory: cd /sbin 2 To obtain the Logical Vol Mgr status.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. 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 0 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 . The problem is highlighted under Logical Vol Mgr as all metadevices using that disk are in a maintenance state.

When the disk has been replaced (this can be done with the machine running)./dev/rdsk/c0t2d0s2 metareplace -e d20 c0t2d0s0 Continued 13-44 68P02901W19-S Oct 2009 . 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 .Replacing hard disk on system processor Sunfire/Netra 440/Netra 20 Procedure 13-15 Chapter 13: Troubleshooting 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 0 No Okay Yes c1t10d0s0 0 No Okay Yes c1t11d0s0 0 No Okay Yes c1t12d0s0 0 No Okay Yes c1t13d0s0 0 No Okay Yes Hot Spare d27: Submirror of d25 State: Okay Size: 1433371008 blocks (683 GB) Stripe 0: (interlace: 512 blocks) Device Start Block Dbase State Reloc c3t9d0s0 0 No Okay Yes c3t10d0s0 0 No Okay Yes c3t11d0s0 0 No Okay Yes c3t12d0s0 0 No Okay Yes c3t13d0s0 0 No Okay Yes Hot Spare NOTE State: Needs maintenance indicates that a problem has occurred. and Logical Vol Mgr needs to be re-enabled to use that disk. the disk requires repartitioning.

the mirrors begin to resync. 4 Resynchronizing can be checked by entering the following command: metastat | grep Resync Output similar to the following is displayed: d20: Mirror Submirror 0: d101 State: Resyncing Submirror 1: d100 State: Okay Resync in progress: 12 % done Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 262960 blocks d101: Submirror of d20 State: Resyncing Size: 262960 blocks Stripe 0: Device c0t2d0s0 Start Block 0 Dbase State Hot Spare No Resyncing d100: Submirror of d20 State: Okay Size: 262960 blocks Stripe 0: Device c1t2d0s0 68P02901W19-S Start Block 0 Dbase State Hot Spare No Okay 13-45 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) Output similar to the following is displayed: d20: device c0t2d0s0 is enabled When this has been done for each device that was in a maintenance state.

as follows: d20: Mirror Submirror 0: d101 State: Needs maintenance Submirror 1: d100 State: Okay Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 262960 blocks d101: Submirror of d20 State: Needs maintenance Size: 262960 blocks Stripe 0: Device Start Block c0t2d0s0 0 No Dbase State Hot Spare Maintenance d100: Submirror of d20 State: Needs maintenance Size: 262960 blocks Stripe 0: Device c1t2d0s0 Start Block 0 No Dbase State Hot Spare Maintenance This problem can be fixed by shutting the machine down to single user mode and running fsck on the affected file system. 13-46 68P02901W19-S Oct 2009 . Recovering from other Logical Vol Mgr problems Other problems with Logical Vol Mgr should be handled by a Solaris Logical Vol Mgr expert. The machine should then be rebooted and the problem should have been fixed. Errors on other slices of that disk would highlight a more serious problem. This can be confirmed by running metastat on the metadevice.Recovering from other Logical Vol Mgr problems Chapter 13: Troubleshooting File system corruption usually causes both sides of the mirror to require maintenance. but only on that slice of the disk.

Refer to Logical Vol Mgr troubleshooting on page 13-42 in this chapter for the procedure to recover a lost disk. execute the following command: metadb 4 If the system does not have sufficient state databases then they must be created. execute the following command: 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.0 GB) d126: Submirror of d125 State: Okay : Size: 4197717 blocks (2. You can copy the checklist provided in Table 14-11 to record the checks. execute the following command: 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 Write option: parallel (default) Size: 4197717 blocks (2.0 GB) Device d128 Start Block 0 Device: c0t1d0s0 (2. Any subdisks that need maintenance should be repaired. As user root. 2 Check for any subdisks that require maintenance using the metastat command. follow the procedure below. As user root. 3 Check that the system has at least three state databases on each mirror.0 GB) 68P02901W19-S No Yes State Reloc Hot Spare Okay State: Okay Device 0 Dbase No Stripe 0 No d128: Soft Partition Size: 4198400 blocks Start Block Dbase Reloc Extent Start Block c0t1d0s0 Block 13-47 Oct 2009 . As user root. Table 13-2 Disk mirroring checklist Method Check 1 Check the Logical Vol Mgr status.Operating Information: OMC-R System Administration Checking disk mirroring Checking disk mirroring ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Disk mirroring checklist To check disk mirroring.

0 GB) 4198400 Size: 4197717 blocks State: Okay No Size: Dbase Reloc Extent Start Block 66854923 State: Okay Pass: 1 68P02901W19-S Oct 2009 .0 GB) 66854923 State: Okay Stripe 0: Reloc Hot Spare Device d129 d129: Soft Partition c2t5d0s0 0 Device 0 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.metastat output Chapter 13: Troubleshooting count 0 Submirror of d125 (2.

Operating Information: OMC-R System Administration Device busy error Device busy error ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Device busy error If an attempt to mount a device has failed. this indicates that the device contains an active file such as an open file. If an attempt to unmount a device has failed. close all the files under that mount point. a mount point. Unmounting a device To unmount a device containing active processes. Then try to unmount again. quit any programs started from there and change directories out of that hierarchy. 68P02901W19-S 13-49 Oct 2009 . This message also occurs when trying to enable accounting that is already enabled. a current directory. this indicates that the device was already mounted. or a running program.

the following procedure can be used to manually eject the DVD-ROM. 2 Type the following command to stop volume management: svcadm disable volfs 3 Press the eject button on the DVD tray to manually eject the DVD.Ejecting DVD-ROMs Chapter 13: Troubleshooting 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. 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 1 Login as root. 4 Type the following command to restart volume management: svcadm enable volfs 68P02901W19-S Oct 2009 .

2 From the StorEdge Enterprise Backup Server GUI Administration window. or if the backup tape in the tape drive has not been mounted and/or labeled.Operating Information: OMC-R System Administration 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. 3 Click on the Mount icon to mount the tape. The tape should then be mounted and the backup will continue. 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 1 Check if the correct tape is inserted in the tape drive. If a new tape has been inserted then the tape should first be labelled by clicking Label. 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. and should be mounted in the usual way. click Devices and select the tape driver (/dev/rmt/0cbn) from the Device list. 13-51 Oct 2009 .

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. Use the following procedure to investigate database failure: Procedure 13-18 Investigating a database failure 1 Examine the online log. the log file should be examined to locate the problem. Refer to Database utilities on page 8-4 for further details about onmonitor. Other sections in this manual give more details of the procedures involved. There should be one dbms log file per error that occurs.Database failure Chapter 13: Troubleshooting Database failure ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Database failure In the event of a failure of the INFORMIX database. use the following UNIX command: ls -l 13-52 68P02901W19-S Oct 2009 .nnnnnnnn. Refer to Database utilities on page 8-4 for further information. 2 Use the Mode menu selection of onmonitor to determine the mode of operation. 4 If the fault cannot be rectified. 3 Examine the software log files in $OMC_TOP/logs. Problems adding/updating statistics in PM database If problems are being experienced with PM statistics. collate all the information before contacting the local Motorola support centre. where nnnnnnnn is a unique integer identifying the log file. Refer to OMC-R log and error files on page 4-3 for further information. The filename will be of the form dbms. To find out when the log was created.

The Onperf utilities perform the following basic functions: • Display the values of online metrics in the Graph Tool window. or stored for later playback.PM database. 68P02901W19-S 13-53 Oct 2009 . The user selects items to be measured. These may be displayed graphically in real time. 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 1 Login to the system processor as user omcadmin. select onperf . • Save online metric values to a file. • To monitor the CM database. click the INFORMIX icon and select one of the following options from the Database Applications menu.Operating Information: OMC-R System Administration 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. • To monitor the PM database. The Onperf utilities are implemented in INFORMIX and run on the system processor.MIB database. Either selection causes the Graph Tool window (Figure 13-1) to be displayed. • Allow review of online metric values from a file. 2 On the CDE front panel. select onperf .

Starting onperf from the command line Figure 13-1 Chapter 13: Troubleshooting 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 1 Login to the system processor as user omcadmin.0 3 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 . 2 Enter the following command: setenv DISPLAY omc_splat:0.

The history file is displayed in the Graph Tool window. enter a directory path that includes wildcards. select the Open History File option. 5 Click OK. NOTE A history file consists of metrics data previously saved by the data collector. 2 From the Graph menu (Figure 13-2). 4 Enter the path name of a history file in the selection box to load into the Graph Tool. To help find a history file. 3 The standard Select File dialog box is displayed as shown in Figure 13-3. The Graph Tool window is displayed as shown in Figure 13-1. click on the OnPerf icon for the application database. In the Filter edit box.Operating Information: OMC-R System Administration Procedure 13-21 Loading a history file Loading and displaying a history file 1 From the CDE desktop environment. specify a wildcard filter. Figure 13-2 Graph menu ti-GSM-Graph_menu-00056-ai-sw 68P02901W19-S 13-55 Oct 2009 . All files that satisfy the filter are listed on the right. Click on the Filter command button at the bottom of the window.

Loading a history file Figure 13-3 Chapter 13: Troubleshooting Select file dialog box ti-GSM-Select_file_dialog_box-00057-ai-sw 13-56 68P02901W19-S Oct 2009 .

then click the Filter command button. Enter a directory path that includes wildcards in the Filter edit box. There is no difference in functionality between the new Graph Tool and the original Graph Tool. select the Configure menu and click Save Configuration As (refer to Figure 13-4). 3 To help find a directory in which to write the file. a wildcard filter may be specified. 2 To save a new configuration. Configuration information includes the set of histogram buffers.Operating Information: OMC-R System Administration 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 1 From the Graph menu. This creates a new Graph Tool. All files that satisfy the filter will be listed. select New. the active graph and activity tools. These tools may be closed in any order. Figure 13-4 Configure menu ti-GSM-Configure_menu-00058-ai-sw 68P02901W19-S 13-57 Oct 2009 . enter a file name in the selection box to store the present Graph Tool configuration. In the Save File dialog box that appears. 4 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).

3 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. 2 A Select Metrics window is displayed with the metric class selected. 4 Select a metric from this list. 5 Click Add.Selecting metrics Chapter 13: Troubleshooting Selecting metrics Use the following procedure to select metrics to be displayed: Procedure 13-23 Selecting metrics to be displayed 1 From the Metrics menu. The metric is added to the list box on the right. select a metric class. 6 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 .

the relevant metric scopes are the tblspace names that correspond to tables that are currently open to a thread. there is only one metric scope. • For the virtual processor class. the relevant metric scopes are the active sessions. Each virtual processor metric represents an aggregate of activity for all online virtual processors of the indicated class. These are called action tables.Operating Information: OMC-R System Administration Viewing metrics The following bullet points list the metric classes available and their relevant metric scopes: • For the disk chunks class. KIO. To obtain measurements for a single fragment. the relevant metric scopes are the online virtual processor classes: CPU. the relevant metric scopes are any of the physical processors for the computer running online. • For the physical processor class. the relevant metric scopes are chunk pathnames for the online database server. • For the tblspace metric class. aggregate. For fragmented tables. the tblspace represents the sum of all fragments for that table. • For the disk spindle class. identified by user login and host name. as illustrated in Figure 13-6: Figure 13-6 View menu ti-GSM-View_menu-00060-ai-sw 68P02901W19-S 13-59 Oct 2009 . the relevant metric scopes are the dbspaces for fragments that are currently open to a thread. • For the disk sessions class. AIO. and so on. the relevant metric scopes are the pathnames of the disk devices or cooked files used by the online database server. the metric can be viewed in various formats. or total for an aggregate of all the physical processors. These are called active table fragments. The scope for these metrics is the database server as a whole. A tblspace name is a composite of the database and the table that it refers to. use the fragment metric class. • For the fragment metric class. Viewing metrics By selecting any of the options from the View menu. • For the server class.

the scale is reduced. Onperf repaints the Graph Tool in the line format as shown in Figure 13-7. and vice versa. To change the scale or appearance of an individual metric.Viewing metrics Chapter 13: Troubleshooting Line Plot When this option is selected. This box has buttons for setting the metric scale. style and width. 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. 13-60 68P02901W19-S Oct 2009 . color. When the zoom bar is raised. This displays the Customize Metric dialog box. These can be displayed by selecting the View menu option Show null values. NOTE The line graph may contain hidden data values. click on the legend for that metric. The zoom bar adjusts the scale of the horizontal time axis. The pan bar allows movement along the horizontal time axis.

which has buttons for setting metric scale. 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. the Graph Tool is redrawn in horizontal bar format as shown in Figure 13-8. color. This brings up the Customize Metric dialog box.Operating Information: OMC-R System Administration Viewing metrics Horizontal Bar Graph When this option is selected. 68P02901W19-S 13-61 Oct 2009 . style and width.

the Graph Tool is redrawn in vertical bar format as shown in Figure 13-9.Viewing metrics Chapter 13: Troubleshooting Vertical Bar Graph When this option is selected. the vertical axis represents the scale of the metric measurement. To change the scale or appearance of an individual metric. color. This brings up the Customize Metric dialog box. which has buttons for setting metric scale. 13-62 68P02901W19-S Oct 2009 . click on the legend for that metric. Figure 13-9 Vertical line graph ti-GSM-Vertical_line_graph-00063-ai-sw In this format. style and width.

The last sampled values are displayed in the legend next to the metric name.Operating Information: OMC-R System Administration Viewing metrics Pie Chart When this option is selected. the Graph Tool is repainted in pie chart format as shown in Figure 13-10. but not the values themselves. Figure 13-10 Pie chart ti-GSM-Pie_chart-00064-ai-sw The pie charts show the relative sizes between metrics. 68P02901W19-S 13-63 Oct 2009 .

A typical Status Tool window is displayed in Figure 13-11.Monitoring tools Chapter 13: Troubleshooting Monitoring tools The monitor tools include the Status Tool and the Query Tree. Figure 13-11 Status tool ti-GSM-Status_tool-00065-ai-sw 13-64 68P02901W19-S Oct 2009 . These are described below: Status Tool The Status Tool monitors the state of the data collector and the database server.

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. the large detail window displays the iterations that comprise the execution plan for the query. The Query Tree tool has two options: Select Session and Quit. This provides a map of the overall query. not all the iterators fit into the detail window. In some cases. When a session which is running a query is chosen. Figure 13-12 Query Tree ti-GSM-Query_Tree-00066-ai-sw 68P02901W19-S 13-65 Oct 2009 . The left pane shows the iterators as small icons.Operating Information: OMC-R System Administration 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 Graph menu has options for closing the graph. opening a new graph. or another activity tool. based on some suitable metric. This metric represents the total number of I/O operations involving the chunk. • Session activity. Disk Activity Tool The Disk Activity Tool displays activities for chunks. The horizontal bar graph view is used. Each of these activity tools displays information about a particular database activity. ranked according to the Disk Operations metric.Activity tools Chapter 13: Troubleshooting Activity tools There are five different activity tools: • Disk activity. There are two activity tool menus: the Graph menu and the Tools menu. The metric class is Disk Chunk and the metric scope is the chunk pathname. • Disk capacity. and exiting Onperf. • Physical processor activity. status tool. Figure 13-13 Disk Activity Tool ti-GSM-Disk_Activity_Tool-00067-ai-sw 13-66 68P02901W19-S Oct 2009 . The Tools menu has options to display the Query Tree tool. The scale of an activity tool cannot be changed from within the tool itself. • Virtual processor activity.

Operating Information: OMC-R System Administration Activity tools Disk Capacity Tool The Disk Capacity Tool displays chunks ranked according to the free disk space available in megabytes. Figure 13-14 Disk Capacity Tool ti-GSM-Disk_Capacity_Tool-00068-ai-sw 68P02901W19-S 13-67 Oct 2009 . The horizontal bar graph view is used.

The metric class is Session and the metric scope is the host name.Activity tools Chapter 13: Troubleshooting Session Activity Tool The Session Activity Tool displays the sessions for the database server. Figure 13-15 Session Activity Tool ti-GSM-Session_Activity_Tool-00069-ai-sw 13-68 68P02901W19-S Oct 2009 . This metric represents the total number of ISAM calls and PDQ calls per second. The horizontal bar graph view is used.

The scale of the Virtual Processor Activity Tool cannot be changed manually.Operating Information: OMC-R System Administration 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. Figure 13-16 Virtual Processor Activity Tool ti-GSM-Virtual_Processor_Activity_Tool-00070-ai-sw 68P02901W19-S 13-69 Oct 2009 .

To use these commands. login as omcadmin.Checking and recovering database tables Chapter 13: Troubleshooting 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. 13-70 68P02901W19-S Oct 2009 .

The TBS Pages section shows the number of pages: • Allocated to data 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. • Allocated to tables but which are currently empty. 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 .Operating Information: OMC-R System Administration Monitoring database space usage and fragmentation omc_db_ckspace command The usage lines in the /usr/omc/logs/omc_db_maint* log files come from omc_db_ckspace. • Allocated to tables. so inserts into one table can fail even if there is free space in other tables. available to the server). 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. • NOT allocated to tables. 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. the above example does not show the distribution of free space among the tables. Also. • With data on them.

The Free pages are permanently allocated to one table. The Extent column shows the number of table fragments. 2047 maximum The oncheck -pe command is as good as an input to a shell script. so you can see which chunks belong to each dbspace). omc_db_ckspace gives a very simple overview of the situation. The output is unwieldy and would need filtering for your purposes. then each chunk in the second part of the output (with dbspace and chunk numbers. 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 1 3 1 1 6 1 1 N informix N informix omc_db_plog 31026728 N informix omc_db_llog 31026790 5 omc_db_sp1 310267f8 6 1 2 1 5 1 N informix N informix omc_db_sp2 6 active. It lists each chunk within each dbspace. the db_ckspace and db_cktab commands give a clear picture about database space usage. The onstat -d command is similar to the db_ckspace command as it shows each dbspace in the first part of the output. including unallocated space. 2047 maximum Chunks address 31026148 1 2 2 905 2 1 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 6 2 bpages flags pathname 17113 PO-/dev/omc_db_root 31026220 5 2 1024098 1024045 4 40962 158718 2 40958 70915 1024098 797169PO-/dev/omc_db1 PO-/dev/omc_db2 6 active. so they comprise part of the TBS Pages Free value in the output from omc_db_ckspace. which should not be relied upon. but not currently used by it. If there are more than 16.Monitoring database space usage and fragmentation Chapter 13: Troubleshooting 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 5 1 15 11 1 2 26 23 3 5 6719 109 4105 1 1 1 5639 5639 0 5 2292 31 9162 The Pages column shows the number of pages allocated to the table. 13-72 68P02901W19-S Oct 2009 . consider defragmenting the table. Combining commands When used together. and every tablespace fragment (extent) of every table. and the Used and Free columns show the number of pages with and without data respectively.

68P02901W19-S 13-73 Oct 2009 . NOTE A database can be created from the above output file by typing: isql . use the alter index <indexname> to cluster command. The following defragmenting procedure: • Does not cause any loss of data from the MIB. To get all information about a database (so that it can be recreated from scratch). which sorts the data in a table into the key value order of the nominated index. • Can be used on any table. but this is likely to be too much to read easily. enter the following command: dbschema -d <dbname> -ss -p all <outputfile> If you omit <outputfile>.<commandfile> where <commandfile> is the <outputfile> from dbschema. • Normally reduces the number of extents to three or fewer. To do this. 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 does not normally require an outage. then deleting the old tablespace and renaming the new one. by executing an SQL command which forces INFORMIX to rebuild the table. To show just the synonyms in the database. INFORMIX implements this by sorting the data into a new tablespace. output is sent to stdout. NOTE The following procedures should only be carried out with the advice of a Motorola Engineer.Operating Information: OMC-R System Administration Reading the database schema Reading the database schema Use the command dbschema to get information about the structure of a database. • Depending on how much contiguous free space is present. provided there is sufficient free space in the dbspace to create a second copy of the table. It is normally easy to defragment them non-destructively.

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). enter the following command: dbschema -d dbname -t tablename 4 Look at the names of indexes. It normally reduces the number of extents to two (there is no need to get a table into a single extent). try again after a few minutes. use that. <CTRL>-C 6 If you see the message table is locked. and defragment the statistics table at the same time. with an outage time of less than two minutes. It must only be used on tables which do not have views (this includes all tables whose names end in _statistics. NOTE The following procedures should only be carried out with the advice of a Motorola Engineer.Emptying and defragmenting one or more PM statistics tables Chapter 13: Troubleshooting Use this procedure to defragment tables: Procedure 13-24 Defragmenting tables (MIB database) 1 Login as omcadmin or informix on the system processor. 2 Enter the following command: mib_env 3 To find the name of an index to cluster. Otherwise. you may need to schedule an omc stop or start (cluster the index after the omc stop but before the omc start). 13-74 68P02901W19-S Oct 2009 . It is possible to complete the process within five minutes. If one of the definitions is create cluster index <indexname>. enter the following command: isql dbname alter index indexname to cluster. It requires a short PM outage (typically. less than five minutes). Emptying and defragmenting one or more PM statistics tables This is the quick and easy way to remove troublesome statistics. If there are no unique indexes. This procedure results in all the statistics in the affected table being lost. choose an index defined with create unique index <indexname>. If the table is locked permanently. 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. 5 To cluster the index.

) 7 To get the schema of the table(s). 2 Enter the following command: omc_env 3 To determine the size of the table(s) and to find the size of the database table currently being used. enter the following commands: isql omc_db alter table tablename next size size_in_kb. (The <CTRL>-C is to quit isql.sql 8 To disconnect the OMC-R processes (outage start). 5 To alter the next size of the table(s). enter the following command: isql omc_db tablename. enter the following command: db_disconnect disconnect 9 To drop the table(s). enter the following command: dbschema -d omc_db -t tablename -ss -p all tablename. <CTRL>-C 10 To recreate the empty table(s). the size of the cell_statistics table in the above example is 100535 pages multiplied by 2 KB page size equals 201070 KB. enter the following command: db_disconnect connect 13-75 Oct 2009 . 6 Repeat the alter table line in step 5 for each table you want to empty. 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 4 Multiply the value in the Used column by two to get the size in kilobytes. enter the following: isql omc_db drop table tablename.Operating Information: OMC-R System Administration Emptying and defragmenting one or more PM statistics tables Use the following procedure to empty and defragment PM statistics tables: Procedure 13-25 Emptying and defragmenting PM statistics tables 1 Login as omcadmin on the system processor. <CTRL>-C where <tablename> is the table name and <size_in_kb> is the size (in kilobytes) of the table. For example.sql 11 To reconnect the OMC-R processes (outage end).

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. Continued 13-76 68P02901W19-S Oct 2009 . NOTE The following procedures should only be carried out with the advice of a Motorola Engineer.Adding extra logical logs to the PM database server Chapter 13: Troubleshooting Adding extra logical logs to the PM database server If the OMC-R installation has some unused space left in the Logical Log dbspace. Use the following procedure to add extra logs. you can add extra logs. 2 Enter the following command: omc_env 3 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 The first part of this output shows the dbspaces. 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 Adding extra logical logs to the PM database server 1 Login as informix on the system processor. which make up the dbspaces. These logs will increase the resilience of the server against transactions that take a long time to update. The second part shows the chunks.

00 When you add a logical log. 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. 6 To find the size of the existing logs. you can use: onparams -a -d omc_db_llog -s 20480 13-77 Oct 2009 . the logs are 10240 pages. which is 20480 KB: address number a57cfc8 1F------ 7 68P02901W19-S Adding extra logical logs to the PM database server flagsuniqid beginsize used%used 0307835 102400 0.Operating Information: OMC-R System Administration Procedure 13-26 Adding extra logical logs to the PM database server (Continued) 4 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). use the following command to specify the size (in kilobytes): onparams -a -d DBspace [-s size] In this example. 5 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.

refer to Maintenance Information: Alarm Handling at the OMC-R (68P02901W26) manual. For more information on alarm handling procedures. • Frequency of events arrival. 13-78 68P02901W19-S Oct 2009 . The correct alarm number is displayed.Alarms Chapter 13: Troubleshooting 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. and reopen it. refer to OMC-R Online Help. close the PLMN alarm window. • X. Network Operation. NOTE If the number of alarms in the PLMN alarm window does not match with the OMC main board.25 lines connected to the system processor. • Database. For more information on the alarms. Such alarms fall into the following categories: • Disk space usage on the system processor. • System processor failure.

Use the following procedure to resolve the alarm: Procedure 13-28 68P02901W19-S Resolving the LowerLimitDiskUsage (30011) alarm 1 Raise the value of the lower threshold limit (if less than 80 percent) in the configuration file $OMC_TOP/config/global/FM_audit.Operating Information: OMC-R System Administration 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 • /usr/omc/ne_data/raw_stats • /tmp • /solbak The default value of the upper threshold is 90 percent.CNFG file. 2 Check the disk usage of all the partitions. 13-79 Oct 2009 . When the threshold value is exceeded. the system removes any log files older than three days from the $OMC_TOP/logs. The default value of the lower threshold is 80 percent.CNFG file for further details of the FM_audit. 2 Perform the disk full procedures. The threshold value should return to 90 percent.CNFG. Use the following procedure to resolve the alarm: Procedure 13-27 Resolving the UpperLimitDiskUsage (30010) alarm 1 Raise the value of the upper threshold limit (if less than 90 percent) in the file $OMC_TOP/config/global/FM_audit. LowerLimitDiskUsage (30011) alarm An alarm is raised when the lower threshold of disk usage is exceeded on the /.CNFG. Refer to FM_audit. /home. /usr and /usr/omc/ne_data partitions of the system processor.

Immediate action must be taken to reduce the CPU activity by expanding the lower CPU load limit. 2 Monitor the alarm. Use the following procedure to resolve the alarm: Procedure 13-29 13-80 Resolving the CPU load exceeds lower limit (30061) alarm 1 Check the CPU load on the system processor. This fault condition may occur if the CPU load is high.CPU and memory usage alarms Chapter 13: Troubleshooting 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. and if it does not clear. 3 Raise the value of the threshold CPU limit. The following are possible causes for this alarm: • The CPU load on the system processor has reached its maximum capacity. 68P02901W19-S Oct 2009 . • The upper limit threshold of the CPU load was lowered. If the CPU becomes overloaded. NOTE The CPU load exceeds upper limit alarm indicates that the CPU is completely overloaded. carry out further investigations to determine which processes are overloading the CPU. the OMC-R may not function correctly.

This fault condition could occur if the memory usage is high. and if it does not clear. the OMC-R may not function correctly. NOTE The memory usage exceeding the upper limit alarm indicates that the memory is completely exhausted. and requires that the memory is made available by expanding the lower memory usage limit. 68P02901W19-S 13-81 Oct 2009 . carry out further investigations to see which processes are using too much CPU. Current memory usage is high.Operating Information: OMC-R System Administration CPU and memory usage alarms 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. Immediate action must be taken to free up the memory. Use the following procedure to resolve the alarm: Procedure 13-30 Resolving the CPU load exceeds upper limit (30062) alarm 1 Check the CPU load on the system processor. 2 Monitor the alarm. If the memory usage is too high. The CPU is completely overloaded. • The upper limit threshold of CPU load was lowered. 3 Raise the value of the threshold CPU load limit. The following are the possible causes for this alarm: • The CPU load on the system processor has reached maximum capacity. Immediate action must be taken to reduce the CPU activity. 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.

2 Monitor the alarm. carry out further investigations to see which processes are using too much memory. • The upper limit threshold of memory usage was lowered. 68P02901W19-S Oct 2009 . and if it does not clear. carry out further investigations to see which processes are using too much memory. 3 Raise the value of the threshold memory usage limit. The following are possible causes for this alarm: • Memory usage by the system processor has reached maximum capacity. 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. 3 Raise the value of the threshold memory usage limit. 2 Monitor the alarm. Memory is completely used up. Use the following procedure to resolve the alarm: Procedure 13-31 alarm Resolving the Memory usage exceeding the lower limit (30063) 1 Check the memory usage on the system processor. Use the following procedure to resolve the alarm: Procedure 13-32 13-82 Resolving the Memory usage exceeds upper limit (30064) alarm 1 Check the memory usage on the system processor.CPU and memory usage alarms Chapter 13: Troubleshooting The following are possible causes for this alarm: • The memory usage on the system processor has reached its maximum capacity. and if it does not clear. • The upper limit threshold of memory usage was lowered. Immediate action must be taken to free up memory.

This usually means that the EM list manager has not been reconnected after completion of maintenance. parserDisconnectedTooLong (30004) alarm This alarm is raised when the parser has been disconnected from the OMC-R database for longer than 10800 seconds. 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. 68P02901W19-S 13-83 Oct 2009 . If the EM list manager is disconnected from the database for a long time. 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. Use the following procedure to resolve the alarm: Procedure 13-33 Resolving the parserDisconnectedTooLong (30004) alarm 1 If omc_db_maint has finished executing. run this command: $DBMS_BIN/db_disconnect connect parser 2 Check to see if the Event Manager (EM) needs to be connected by trying to create a subscription list. If not.Operating Information: OMC-R System Administration Database alarms Database alarms Three alarms are raised when the Performance Manager and the Event Manager are disconnected from the database. the major alarm 30004 parserDisconnectedTooLong is generated. Refer to the corrective action for the alarm parserDisconnectedTooLong. Refer to the corrective action for the alarm parserDisconnectedTooLong. Two of these are warnings that can lead to the major alarm 30004 parserDisconnectedTooLong being generated if the cause of the alarm continues. If this fails. check the omc_db_maint logs to see if the command db_disconnect connect parser has been executed. the major alarm 30004 parserDisconnectedTooLong is generated. If the parser is disconnected from the database for a long time.

• Check the upper/lower thresholds of the databases to verify that they are no longer exceeded. The following are the possible causes for this alarm: • The database usage by the system processor caused the database to reach its maximum capacity. the OMC-R system administrator should keep a close watch on the space used. 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. If the database space is full. • The various OMC-R databases are filling up too quickly for the defined maintenance procedures. Raise the value of the threshold database limit (if lower than 90%).Database alarms Chapter 13: Troubleshooting 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. and the database space allocations are adequate. However. NOTE The database upper limit alarm indicates that the database is completely full. • The upper limit threshold of database usage was lowered. and requires that space be made available by expanding the lower database limit. The OMC-R may not function correctly if it cannot write into the database. Use the following procedure to resolve the alarm: • 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. the OMC-R may not function correctly because it may not have the ability to write into the database. Current database usage is high. • The various OMC-R databases are not being maintained properly. This fault condition could occur if the database space usage is high. action should be taken to free up space immediately. If the database becomes full. NOTE There is still room in the database. Action should be taken to free up space in the database immediately. 13-84 68P02901W19-S Oct 2009 .

25 on page 9-9 for further details of the procedure to stop and start X. 5 Investigate the necessity of increasing the regularity (frequency) with which the various maintenance and archive scripts are run (or executed). Login as root and enter the following command: /opt/SUNWconn/bin/x25stat -L This shows the status of the connections.25 alarms 1 Check for related errors.25 process state as follows: Determine the state of alarm VCs to all NEs. Use the following procedure to resolve the alarm: Procedure 13-35 68P02901W19-S Resolving X. check the system processor X. following the above order. 7 Check the upper/lower thresholds of the databases to verify that they are no longer exceeded. 4 Check that the physical link has not been removed or accidentally cut.25 alarms Use the following procedure to resolve the alarm: Procedure 13-34 Resolving the Database exceeding the lower limit (30019) alarm 1 In the Alarm window. contact the local Motorola office. If no VCs exist. Refer to Starting and stopping X.25. 6 Review database space allocations to determine whether there is a space shortage. check the error reason field in the alarm message to determine the cause(s) of this alarm.25 Network Interface Card.25 alarms A Level123 Failure alarm is raised when there is a Layer1/Layer2/Layer3 failure on the system processor X. 3 Check the X.25 line. MUX and NE. 7 If problems persist. 5 Check the X. 2 Stop and start the X. 13-85 Oct 2009 . for example.25 on the link indicated by the alarm.25 log files. X. 3 Verify that the database maintenance procedures currently in operation comply with those recommended in this manual. 30013 solarisHardwareFailure.Operating Information: OMC-R System Administration X. packet switch. 6 Check the X.25 NICs. 2 Check the database usage in the system processor database to which the error relates. Determine where the shortage is located. 4 Raise the value of the threshold database limit (if lower than 90%).

2 Check that a slow communication link to a GUI is not causing a backlog of events. these particular alarms could be throttled or blacklisted. Use the following procedure to resolve the alarm: Procedure 13-36 Resolving Hardware failure alarms 1 Check to see if maintenance is being performed on the system processor. Use the following procedure to resolve the alarm: Procedure 13-37 13-86 Resolving the OMCOverloadedWithEvents (30021) alarm 1 Check the reason for the arrival of several events at the OMC-R. 2 Refer to the Sun System Administration manual for further information on dealing with Sun hardware unit failure. 68P02901W19-S Oct 2009 . If there are a large number of similar alarms. 3 Check the performance of the system processor to see if it is functioning correctly. 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.Hardware failure alarms Chapter 13: Troubleshooting Hardware failure alarms An alarm is raised when a system processor hardware unit is out of service. 3 If problems persist. contact the local Motorola office.

If there are a large number of similar alarms. 13-87 Oct 2009 . these particular alarms could be throttled or blacklisted. Use the following procedure to resolve the alarm: Procedure 13-38 Resolving the OMCOverloadedEventsDiscarded (30022 alarm) 1 Check the reason for the arrival of so many events at the OMC-R. 2 Check the number of cells of each BSC which enable the critical statistics reporting to ensure it is less than 90. Use the following procedure to resolve the alarm: Procedure 13-39 68P02901W19-S Resolving the Criticalstatseventsdiscarded (30078 alarm) 1 Check the number of BSCs which enable the critical statistics reporting to ensure it is less than 30. • There are too many cells enabling the critical statistics reporting per BSC at a time. The following are the possible causes for this alarm: • There are too many BSCs enabling the critical statistics reporting at a time. 2 Check that a slow communication link to a GUI is not causing a backlog of events. 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. 3 Check the performance of the system processor to see if it is functioning correctly.Operating Information: OMC-R System Administration 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.

FM_audit.CNFG parameters The FM_audit.Setting FM audit and disk usage limits Chapter 13: Troubleshooting 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 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 .CNFG contains user defined values that are used for setting the FM audit timers and disk usage limits.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.

68P02901W19-S 13-89 Oct 2009 .Operating Information: OMC-R System Administration FM_audit. Root partition lower limit = 80%. Ne_data partition lower limit = 80%. System processor hardware audit count = 2 minutes.CNFG parameters 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. Raw statistics partition lower limit = 80%. Timings should be considered as estimates. Raw statistics partition upper limit = 90%. StorEdge Enterprise Backup partition lower limit = 80%. /tmp partition lower limit = 80%. Memory use lower limit = 80%. Database use lower limit on the system processor = 80%. StorEdge Enterprise Backup partition upper limit = 90%. Home partition lower limit = 80%. Memory audit count = 20 minutes. Database use upper limit on the system processor = 90%. NOTE The audit counts are the times between each audit (wait times) and do not include the time taken to run the audits. Database audit count = 6 hours. Root partition upper limit = 90%. Home partition upper limit = 90%. CPU audit count = 20 minutes. CPU load upper limit = 90%. X. Ne_data partition upper limit = 90%. /tmp partition upper limit = 90%.25 audit count = 1 minute. CPU load lower limit = 80%. Usr partition upper limit = 90%. Usr partition lower limit = 80%.

CNFG file.FM_audit. system processor CPU 2 ID number =14. NOTE The FM audit and disk usage limits should only be changed by qualified personnel under guidance from Motorola Support. To change a FM audit timer or disk usage limit value.CNFG parameters Chapter 13: Troubleshooting Memory use upper limit = 90%. edit the appropriate line entry in the $OMC_TOP/config/global/FM_audit. system processor CPU 1 ID number =11. Number of HSI ports = 8. Remove cores count = 3. system processor CPU 0 ID number =10. system processor CPU 3 ID number =15. 13-90 68P02901W19-S Oct 2009 . Contact Motorola Support for further information.

When PMCyclic has used this file. also referred to as PMCyclic. Do not enable the neighbor statistics on more than 16 cells per BSS. PMCyclic uses /usr/omc/ne_data/nha_nbrs/nha_neighbours. starting with cells that have the oldest date for the last enabled neighbor statistics. This section describes how to enable the neighbor statistics and the limitations that should be placed on their use. The user creates a file listing the cells where the neighbor statistics are to be enabled.previous. If a /usr/omc/ne_data/nha_nbrs/nha_neighbours file does not exist. it moves it to: /usr/omc/ne_data/nha_nbrs/nha_neighbours. /usr/omc/ne_data/nha_nbrs/operator_nbr. This feature. and is read from. When that work is complete. enables neighbor statistics for cells in rotation. Limitations on use of neighbor statistics When performing optimization or fault finding work. the statistics should be disabled. use the Cyclic Neighbor Statistics feature (PMCyclic). To automatically enable the neighbor statistics for specific cells using a cron job. This file should be created in. This file is read from /usr/omc/ne_data/nha_nbrs/nha_neighbours. The Motorola NHA tool creates a file containing a list of cell ids where the neighbor statistics are to be enabled.previous. The Cyclic Neighbor Statistics feature automatically enables the neighbor statistics for cells in a BSS in the following sequence: • User-defined cells.Operating Information: OMC-R System Administration Using neighbor statistics Using neighbor statistics ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Neighbor statistics Neighbor statistics are a valuable resource used in optimizing and fault finding. it is recommended that the neighbor statistics should be enabled only on specific cells. Cyclic Neighbor Statistics feature (PMCyclic) Neighbor statistics for a cell can be enabled automatically using the Cyclic Neighbor Statistics feature. • NHA-defined cells. 68P02901W19-S 13-91 Oct 2009 .

create the file operator_nbr in /usr/omc/ne_data/nha_nbrs. then in the NHA-defined file. If the neighbor statistics for a cell cannot be enabled because this limit has already been exceeded. For example. and so on. b. NOTE If the same cells are always specified in the operator. all currently enabled neighbor statistics are disabled. and BSS8 Cell4 has 28/3/01 in its Last Date Neighbor Statistics Enabled record. the same BSSs will always be selected in the Cyclic phase. In a cyclic pattern across other BSSs in the network. The Cyclic phase starts at the BSS associated with the first cell id in the user-defined file. The Cyclic phase enables neighbor statistics for the cell with the oldest date in its Last Date Neighbor Statistics Enabled record. Once the BSS limit is exceeded. 3 If required. a. Enter one GSM Cell Id or cell name per line. and the maximum number of cells with the neighbor statistics enabled per BSS has not been exceeded. the Cyclic phase of PMCyclic is run. create the NHA file using the NHA tool. it is no longer possible to enable the neighbor statistics for 16 cells per BSS. for each BSS 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. This is also shown in the following table. Continued 13-92 68P02901W19-S Oct 2009 . The Cyclic phase then moves on to the next BSS in the network. the Cell Id is recorded in the log file. 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. the Cyclic phase enables neighbor statistics for Cell4.and/or NHA-defined files. Use the following procedure to run PMCyclic: Procedure 13-40 Running PMCyclic 1 Login as omcadmin.Cyclic Neighbor Statistics feature (PMCyclic) • Chapter 13: Troubleshooting If the environmental variable ENABLE_CYCLIC_NBRS is set to ON. 2 If required. which will run automatically each night. Each time PMCyclic is run. c. if BSS8 Cell3 has 28/5/01 in its Last Date Neighbor Statistics Enabled record. At the BSSs containing cells listed in the nha_neighbours file. At the BSSs containing cells listed in the operator_nbr file. Running PMCyclic PMCyclic is a cron job. See NHA manual for further details.

To avoid generating alarm 30026 the variable PM_MAX_NEIGHBOURS can be raised if neighbor statistics are in use. the nbr_statistics table. If the entire space that is allocated has been used.>: 6.> is the number of hours after which PMCyclic should be run. that is. This variable sets the size of the PM database space allocated to neighbor statistics. OMC: tooManyNeighbourStats This alarm is generated when 70 percent of the space in the PM database allocated to the neighbor statistics. Refer to User configurable environment variables on page 6-5 for further details. 68P02901W19-S 13-93 Oct 2009 . use the following command: setup_cyclic_nbr <no. Cyclic Enabled Neighbor Statistics: • Cell Id or name. 24. Neighbor statistics alarm If too many neighbor statistics are enabled. On receiving alarm 30026. 5 To run PMCyclic. set the environment variable ENABLE_CYCLIC_NBRS to ON. the following alarm is generated: 30026.> Where <no. The following are valid values for <no. The log file also records cells that could not be enabled because the maximum number of cells per BSS limit had been reached. 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. Refer to User configurable environment variables on page 6-5 for a complete description of this variable. • Whether enabling of the neighbor statistics for a cell was a Success or a Failure. the following command runs PMCyclic every six hours (four times a day). neighbor statistics will be discarded to prevent the PM database from becoming full.Operating Information: OMC-R System Administration Procedure 13-40 Neighbor statistics alarm Running PMCyclic (Continued) 4 If the Cyclic phase of PMCyclic is to be run. take immediate steps to disable the unwanted neighbor statistics. This log file is deleted after 7 days by another cron job. 24 hours divided by 6 equals 4: setup_cyclic_nbr 6 To run PMCyclic once a day. 12. For example. NHA Enabled Neighbor Statistics. has been occupied by statistics.

Use the following procedure to modify the table sizes: 13-94 68P02901W19-S Oct 2009 . • (Optionally) modify the sizes of the nbr_statistics and nbr_entity tables. the variable PM_MAX_NEIGHBOURS which limits the neighbor statistics can be increased to 2800. 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 Mid-Range OMC-R. 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. 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. 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.Raising the maximum limit of neighbor statistics Chapter 13: Troubleshooting Raising the maximum limit of neighbor statistics On a Low-Range OMC-R. On a High-Range OMC-R. It will be of most benefit if the nbr_statistics table is becoming excessively fragmented. The following additional checks and actions should also be performed: • Monitor the nbr_statistics table. NOTE The following procedures should only be carried out with the advice of a Motorola Engineer. This should be monitored on an ongoing basis using the db_cktab utility. the parser is able to process statistics for a maximum of 2800 neighbors per network in a 30 minute interval. In this case. 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 procedure is optional and there will be a slight improvement in the OMC-R performance.

For more information on dbaccess. 9 Update the initial and next extent sizes in the schema files. and multiplying it by 2. db_cktab -d omc_db -t nbr_entity.sql dbschema -t nbr_entity -d omc_db nbr_ent. 8 The sizes of the tables can be calculated in kilobytes by taking the number of pages for each table. as obtained from step 4. 10 Recreate both tables as follows: dbaccess omc_db nbr_stat.Operating Information: OMC-R System Administration Procedure 13-41 68P02901W19-S Raising the maximum limit of neighbor statistics Modifying the sizes of the nbr_statistics and nbr_entity tables 1 Enter omc_env and press RETURN. 3 omcadmin unloads both the tables using dbaccess.unl This completes the resizing of the extents and reloading of both the tables. 2 Obtain the sizes of the tables with the db_cktab command. 13-95 Oct 2009 . Ensure correct substitution of the table name being used. obtained in step 3.sql 5 Drop both the tables from the database. see Using dbaccess. with the values generated by step 8.sql 11 Reload each table as follows: omc_db_load_table -d omc_db nbr_statistics. drop table nbr_statistics. db_cktab -d omc_db -t nbr_statistics. 4 Get the schema of both tables as follows: dbschema -t nbr_statistics -d omc_db nbr_stat.sql dbaccess omc_db nbr_ent.unl omc_db_load_table -d omc_db nbr_entity. 6 Start the INFORMIX ISQL utility and connect to the OMC-R database: /usr/informix/bin/isql omc_db 7 Enter the query language option and type the SQL commands below. drop table nbr_entity.

unl select * from nbr_statistics. 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.unl select * from nbr_entity. enter the following command: unload to nbr_entity. this may have an adverse effect on the performance of the OMC-R. 5 To return to the operating system. 4 Finally. 68P02901W19-S Oct 2009 .Using dbaccess Chapter 13: Troubleshooting 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. press Ctrl-C. 13-96 2 Enter the following: dbaccess omc_db - 3 Then enter the following command: unload to nbr_statistics. NOTE If the files are unloaded to a directory that is too small.

This section provides procedures to recover from: • Power failure on all machines on page 13-97. Restarting the GUI sessions When the OMC Startup Complete message is displayed on the system processor console. then in the event of a power failure the system and GUI processors have no graceful shutdown. • Power failure on the system processor on page 13-98. the power switches must be turned on.Operating Information: OMC-R System Administration 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). 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. Use the appropriate procedure in this section to recover from power failure where an UPS is not installed. see the particular Sun system manual for the respective system Platform processor. If problems occur upon power restoration. each user may have to restart their GUI session. • Power failure on a GUI processor on page 13-98. Restarting the OMC-R When power has been restored to all machines. Power failure on all machines In the event of a power failure on the system and GUI processors. After power restore To restart the system and GUI processors. If this option is not used. For information on powering on the system processor. contact the local Motorola representative. 68P02901W19-S 13-97 Oct 2009 . turn off the power switches. start the OMC-R.

It is still possible to manage and monitor the network as normal from all other machines. A GUI session may then be started on a GUI server and any of its connected GUI clients. 3 Restart the GUI sessions when the OMC Startup Complete message is displayed on the system processor console. it is not possible to run the GUI from this machine or any of its connected GUI clients. 13-98 68P02901W19-S Oct 2009 . 2 When power is restored the system processor power switches must be turned on. and the OMC-R started.Power failure on the system processor Chapter 13: Troubleshooting Power supply unit failure On the system and GUI processors. If the power to the system processor fails. Power failure on the system processor Access to the OMC-R software is not possible during a power failure on the system processor. perform the following procedure: Procedure 13-43 Recovering from power failure on the system processor 1 Exit from the GUI sessions on the GUI processor. 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. When the power is restored the machine reboots automatically. if the power supply unit fails. contact the local Motorola representative immediately. If a power failure occurs on a GUI server. All features are available. it is not possible to run the GUI from this machine. Power failure on a GUI processor If a power failure occurs on a GUI client.

shows a typical output text for this command.0 3 14 1 7 0 ---.Operating Information: OMC-R System Administration 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. 806-7336-12) for explanations of various LEDs on the Netra 20.0 6 0 400 8.-----10.0 ======================== Memory 68P02901W19-S 13-99 Oct 2009 .0 US-II US-II Ecache 10. 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. 805-7363-12) for explanations of various LEDs on the Sunfire 4800. Mask -----. 817-3883-11) for explanations of various LEDs on the Netra 440.3 1 400 400 8. 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. Netra 440 Refer to Netra 440 Server Service Manual (Part No.0 US-II 10.0 8.0 7 US-II 10.0 7 15 CPU CPU Brd Impl. Netra 20 Refer to Netra AC100/DC100 Services and System Reference Manual (Part No.

501-1725-01 5 3 SUNW.fas/sd (block) 1 13 3060 5 SUNW.-------------------.501-1725-01 1 SBus 25 3 25 3 25 SBus 5 SBus SUNW. Brd ----- OK ------- -- 60 ns Active OK A =================== ====== IO Cards ==================== ===== Bus Freq Brd Type MHz Name ---- Slot Model --- ---- ---- ------ ---------------------------.--OK 42 OK 34 --------.3v OK Peripheral5.Unit OK PPS OK System Temperatures (Celsius): -----------------------------Brd State -----3 42 Current --.socal/sf (scsi-3) 25 1 SUNW.--------.hme 1 SBus SBus fas/sd (block) 5 25 25 SBus 3 25 socal/sf (scsi-3) 501- HSI SUNW.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.Disk BLINKING Fans: ----.1 SBus 25 0 SUNW.501-2253 1 cgsix SBus 25 1 HSI SUNW.3 ---- 0 ------- 1024 2-way A 7 60 ns 2-way Speed ---------- 1024 Bank Factor Active 0 Intrlv.1 OK PPS OK System 5. 13 SUNW.0v 13-100 ----.hme SBus 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 -----.0v 68P02901W19-S Oct 2009 .Displaying system processor status Chapter 13: Troubleshooting ========================= Intrlv.Supply -----. MB Status Condition With --.

8.--- ---------- 22 Dual-SBus-SOC+ 5 1 CPU Capable 7 1 1 -- ---------.9.30 2002/10/25 14:04 13-101 Oct 2009 .0v precharge OK AC Power OK ========================= HW Revisions ==================== ASIC Revisions: ----------.0v OK Peripheral 5.Operating Information: OMC-R System Administration Displaying system processor status OK Peripheral12v OK Auxilary 5.0v precharge 12v precharge OK Peripheral OK System 3.30 2002/10/25 14:04 FCODE 1.8.30 2002/10/25 14:02 2002/10/25 14:03 OBP OBP iPOST 3.4.30 2002/10/25 14:03 Board 3: 2002/10/25 14:03 Board 5: POST 3.2.30 3.9.4.1 100 MHz Capable 3 22 PCI1 ----1 1 ----- 5 ---- 1 1 5 100 MHz Capable 5 Dual-SBus-SOC+ 5 1 100 MHz CPU 100 MHz Capable System Board PROM revisions: --------------------------.3v precharge OK System 5.Board 1: FCODE 1.30 3.30 2002/10/25 14:03 Board 7: 68P02901W19-S POST 3.Brd FHC FEPS Board Type ---- ---- AC SBus0 SBus1 PCI0 Attributes --.30 2002/10/25 14:02 iPOST 3.2.

d/xntpd stop /etc/init.127.Configuring a Timeserver Chapter 13: Troubleshooting 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. If a hostname is specified.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.d/xntpd start 68P02901W19-S Oct 2009 . edit the /etc/inet/ntp. local clock # fudge 127. 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.127. enter the IP address or the name of the Timeserver in the /etc/inet/ntp.drift # path for drift file 3 13-102 Stop the ntp daemon and restart by executing the following commands as user root: /etc/init. either the DNS must be configured or the hostname must be added to /etc/inet/hosts. The ntp. Add the appropriate entries to the ntp.1 prefer # LCL. To configure the OMC-R to use an NTP Timeserver.127. local clock fudge 127.1 stratum 12 # increase stratum peer somc1 prefer # Miscellaneous stuff driftfile /etc/ntp.conf file using a text editor.conf file on the OMC-R.conf file as shown below: # The following lines were added to force this machine # to serve localtime server 127. carry out the following procedure: Procedure 13-44 1 Configuring the OMC-R to use an NTP Timeserver As user root.1.1 prefer # LCL.1.1. To use a local LAN Timeserver.drift # path for drift file 2 Comment out the lines with # referring to LCL.127. local clock and increase stratum.1.1 stratum 12 # increase stratum # peer timeserver prefer # Miscellaneous stuff driftfile /etc/ntp.

50.21 netmask + broadcast + group ipmp2 deprecated -failover standby up 2 68P02901W19-S Oct 2009 Run the following commands as user root: ifconfig ce1 podge_priv netmask + broadcast + group ipmp2 up ifconfig ce1 addif 10.22 netmask + broadcast + deprecated -failover up ifconfig ce3 10.50.ce3 files by adding the following entries: /etc/hostname.ce1 and /etc/hostname.50.Operating Information: OMC-R System Administration Support for IP Multipathing in Solaris10/GSR9 on Sunfire platforms Support for IP Multipathing in Solaris10/GSR9 on Sunfire platforms ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ IP Multipathing is supported in Solaris10/GSR9 on Sunfire platforms.22 netmask + broadcast + deprecated -failover up /etc/hostname.21 netmask + broadcast + group ipmp2 deprecated -failover standby up 13-103 . To configure IP multipathing. complete the following as user root: Procedure 13-45 1 Configuring IP Multipathing Update the /etc/hostname.50.50.ce3 10.50.ce1 podge_priv netmask + broadcast + group ipmp2 up addif 10.50.50.

Support for IP Multipathing in Solaris10/GSR9 on Sunfire platforms 13-104 Chapter 13: Troubleshooting 68P02901W19-S Oct 2009 .

Chapter 14 Checklists ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 68P02901W19-S Oct 2009 14-1 .

General administration checklists on page 14-3. Client and server partition details on page 14-21.Overview Chapter 14: Checklists Overview ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ This chapter provides copies of the various checklists. • Recording details on page 14-20. • Checking databases on page 14-10. 14-2 68P02901W19-S Oct 2009 . Checking databases on page 14-10. • Checking disk usage on page 14-16. Weekly administration checklist on page 14-5. The following checklists are provided in this chapter: • General administration checklists on page 14-3.25 connectivity on page 14-14. • Checking cron jobs on page 14-7. Checklist for CM database on page 14-12. These lists can be copied and used to record checks and other information so that they can be saved for future reference. • Checking core dumps on page 14-15. • Checking X. referred to in the rest of the manual. Setting up a night concentration centre on page 14-20. • Checking disk mirroring on page 14-17. Monthly administration checklist on page 14-6. • Checking for successful parsing of statistics on page 14-18.

[-] Check • PM statistics older than a set timeframe are deleted successfully. Table 14-1 Daily administration checklist Method Checked? Check the file system capacity. Continued 68P02901W19-S 14-3 Oct 2009 . omcadmin and sys. Execute the following command as user root: df -k Any file systems with a 90-100% capacity must be cleaned up for unwanted files or directories. Check the IDS log files for both PM and MIB INFORMIX DB errors and checkpointing. Execute the following command as user root: du | more Terminate processes that are not required and are consuming disk capacity. in particular when the server is initialized.dd [-] Execute the following commands as user omcadmin: tail -f $INFORMIXDIR/online. As user root. [-] Check the disk usage capacity of the system.Operating Information: OMC-R System Administration General administration checklists General administration checklists ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Daily administration checklist To check daily administration.log_MIB These log files should show that checkpoints are completed successfully.mm. [-] Check the output of cron mail jobs from user root.yyyy. follow the procedure in Daily administration checklist on page 2-74. Copy the checklist in Table 14-1 to record the checks. 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: Execute the following commands as user root: cd $OMC_TOP/logs more omc_db_maint. • Applications are connected and reconnected successfully when required. • Disk space is not being consumed.log_OMC tail -f $INFORMIXDIR/online.

[-] Check the system processor hardware.Daily administration checklist Table 14-1 Chapter 14: Checklists Daily administration checklist (Continued) Check 14-4 Method Checked? Check if the PM database is online. Execute the following command as user root: /usr/platform/sun4u/sbin/prtdiag -v. [-] Check the OMC-R log files in /usr/omc/logs for unusual output or error messages. [-] Check the integrity of x25. [-] Perform a backup of the UNIX filesystem. Refer to Chapter 12 Backup Server Installation and Configuration. Execute the following commands as user omcadmin: omc_env onstat | more [-] Check if the CM database is online. [-] Perform a Level 2 backup of the CM database. Refer to OMC-R log and error files on page 4-3. [-] Check the status of the disk mirroring and ensure all submirrors are in an OK state. Execute the following commands as user omcadmin: mib_env onstat | more [-] Perform a Level 2 backup of the PM database. See x25stat output on page 2-76. Execute the following command as user root: metastat | more Refer to Checking disk mirroring on page 14-17. Refer to the checklist for manual parsing of statistics in NE database maintenance on page 2-30. [-] Manually parse any unparsed statistics files. Execute the following command as user root: /opt/SUNWconn/bin/x25stat. [-] 68P02901W19-S Oct 2009 .

execute the following command: df -k [-] Check the disk usage capacity of the system. Table 14-2 Weekly administration checklist Method Checked? Check to see if the Informix online logs are rolled over successfully. As user root.ddmmyyyy online. 68P02901W19-S Refer to Security overview on page 2-36 for further details about important security aspects. Refer to Chapter 12 Backup Server Installation and Configuration. execute the following commands: 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. follow the procedure in Weekly administration checklist in Chapter 2 System management. execute the following command: du |more Terminate processes that are not required and are consuming disk capacity. execute the following commands: cd /usr/informix ls -l online. [-] Archive and remove unloaded PM database files on the system processor.log_OMCEnsure that online logs exist with the format: online. As user root. execute the following command: /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. [-] Check the file system capacity. [-] Archive and remove old OMC-R log files on the system processor and GUI servers. execute the following commands: maintain_script -a -d 7 -t /dev/rmt/0 /usr/omc/ne_data/raw_stats parsed\* This archives raw statistical bad header files older than seven days. maintain_script -r -d 7 /usr/omc/ne_data/raw_stats parsed\* This removes raw statistical bad header files older than seven days after the archive. to record the checks. As user root. [-] 14-5 Oct 2009 . Copy the checklist in Table 14-2.log_OMC. As user root. [-] Perform a Level 1 backup of the CM database.Operating Information: OMC-R System Administration Weekly administration checklist Weekly administration checklist To check weekly administration. As user omcadmin.log_MIB ls -l online.log_MIB.ddmmyyyy [-] Perform a backup of the Unix file system. As user root. [-] Perform an archive of old OMC-R user files. [-] System administrator should monitor system security.

omcadmin. [-] Perform a Level 0 backup of the CM database. As user root. [-] Change the standard installation passwords for user root.Monthly administration checklist Chapter 14: Checklists Monthly administration checklist To check monthly administration. [-] Truncate the cron log file. and informix. Refer to Administering user accounts with usertool on page 2-12. Table 14-3 Monthly administration checklist Check Perform a backup of the Unix file system. 14-6 Method Checked? Refer to Chapter 12 Backup Server Installation and Configuration. to record the checks. execute the following commands: tail -100 /var/cron/log > /tmp/cron_log mv /tmp/cron_log /var/cron/log [-] 68P02901W19-S Oct 2009 . and inform the necessary people of such changes. [-] Perform a Level 0 backup of the PM database. follow the procedure in Monthly administration checklist in Chapter 2. Copy the checklist in Table 14-3.

As user root. As user root. Copy the checklist in Table 14-4. As user root. As user root. As user omcadmin. As user root. execute the following commands: cd /var/cron ls -l Log files should exist in the format log. execute the following command: crontab -l [-] Check if the system cronjobs are setup correctly. it needs to be started. As user root. As user sys. then it should be changed. execute the following command: crontab -l [-] Check the /var/cron/log file to ensure all crons executed are logged to this file. execute the following command: more /etc/default/cron | grep CRONLOG [-] If the CRONLOG variable is set to NO. execute the following command: more /var/cron/log [-] Check if the /var/cron/log file is rolled over to avoid disk space issues. [-] Check if the cron jobs are setup correctly for user root.Operating Information: OMC-R System Administration Checking cron jobs Checking cron jobs ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ To check cron jobs. execute the following commands: rm -f /etc/cron.ddmmyyyy [-] Check the output of root's cron jobs for any errors. As user root.d/FIFO /usr/sbin/cron [-] Check if the CRONLOG variable is set to YES to ensure cron logging is done. Save the file. As user sys. to record the checks. execute the following commands: cd /var/mail more sys | grep cronjobname [-] 68P02901W19-S 14-7 Oct 2009 . execute the following command: crontab -l [-] Check if the cron jobs are setup correctly for user omcadmin. As user root. [-] If the cron daemon is not operational. Table 14-4 Cron job checklist Check Method Checked? Check if the cron daemon is operational on the system. execute the following commands: cd /var/mail more root | grep cronjobname [-] Check the output of omcadmin's cron jobs for any errors. follow the procedure in Checking cron jobs on page 5-18 in Chapter 5. execute the following command: ps -elf | grep cron A /usr/sbin/cron process is displayed. edit the /etc/default/cron file and change the CRONLOG setting to yes. As user root. execute the following commands: cd /var/mail more omcadmin | grep cronjobname [-] Check the output of the system's cron jobs for any errors.

execute the following commands: cd $OMC_TOP/logs more dbms. execute the following commands: cd $OMC_TOP/logs/bss tail -50 bssname_yyyymmdd All command line activities performed on a particular BSS can be viewed. Table 14-5 OMC-R log files checklist Method Check Check if omc log files are created in the correct directory paths. execute the following commands: cd $OMC_TOP/logs tail -50 cm_omcaudit_yyyymmdd Configuration Management activities are logged to this file. [-] When a cutover has been performed. [-] If problems are experienced adding or updating statistics in the PM database. Copy the checklist in Table 14-5. As user omcadmin.Checking OMC-R log files Chapter 14: Checklists Checking OMC-R log files ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ To check the OMC-R log files. check the cutover log file to see if it has been successful. to record the checks. use the procedure in Chapter 4. As user omcadmin. Checked? On the system processor: [-] • OMC-R logs are placed in the /usr/omc/logs directory. • OMC-R logs are placed in the /usr/omc/logs directory. execute the following command: tail -f $SYS_LOG/fpomcaudityyyymmdd [-] Continued 14-8 68P02901W19-S Oct 2009 . • Event logs are placed in the /usr/omc/ne_data/ev_logs directory. As user omcadmin. [-] Check the fpomcaudityyyymmdd log file for successful parsing of statistics files. • Event logs are placed in the /usr/omc/ne_data/ev_logs directory. then check for the existence of dbms log files. Check the BSS log files.nnnn This log file states whether the cutover has been successful. As user omcadmin. • Informix logs are placed in the /usr/informix directory. As user omcadmin.nnnn This dbms log file contains error information. [-] Check the Configuration Management log file. execute the following commands: cd $OMC_TOP/logs more cutover.

[-] Monitor the disk space used by the various log files. 68P02901W19-S 14-9 Oct 2009 .log_OMC. For the PM DB: cd /usr/informix more online.log_MIB. execute the following commands: cd /usr/omc/logs/ipc more ipclogfile name These log files are usually of the format AF032959. As user omcadmin. [-] Check the pmguiaudit log file for errors relating to pmgui.ddmmyyyy For the CM DB: cd /usr/informix more online. [-] Check the omc_db_maint log file to ensure the following: As user rootWilling.Operating Information: OMC-R System Administration Table 14-5 Checking OMC-R log files OMC-R log files checklist (Continued) Check Method Checked? If problems occur with Interprocess communication. • Applications are connected and reconnected successfully when required. • Disk space is not being consumed.yyyy. Refer to OMC-R system information on page 13-8. As user omcadmin. As user omcadmin. monitor the output of the maintain_script cron job to ensure that it deletes log files on a regular basis.d [-] Check the system stats files in /usr/omc/logs/sys_info for system information. As user omcadmin. execute the following commands. then check if an IPC log file exists in /usr/omc/logs/ipc directory.ddmmyyyy [-] Check the omcaudit log for messages relating to OMC-R activity.0001 (Internet address id). execute the following commands: cd $OMC_TOP/logs more omc_db_maint. execute the following commands: cd $OMC_TOP/logs tail -50 pmguiaudityyyymmdd [-] Check the informix online logs for DB errors relating to the PM and CM databases. cd /var/mail more omcadmin | grep maintain_script [-] • PM statistics are deleted successfully. execute the following commands: 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.mm. As user omcadmin. This log file shows an error report.

log_OMC This log file shows that checkpoints are completed successfully. [-] Check the output of the onmode_pm cron job. cat the /usr/omc/current/env/. to record the checks. To run the updateLocalMaint script execute the following command: setenv CM_LOCAL_MAINT TRUE. follow the procedure in the section Checking the PM database on page 8-34 in Chapter 8. execute the following command: tail -f $INFORMIXDIR/online.log_OMC* Log files should exist of the format online. Copy the checklist in Table 14-6. As user omcadmin.Checking databases Chapter 14: Checklists Checking databases ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Two checklists are provided in this section.log_OMC. and the other to check the CM database. As user root. Table 14-6 PM database checklist Check Method Checked? Check if the omc_env alias is setup. execute the following commands: cd /var/mail more root | grep onmode_pm. [-] Check if the IDS log files are rolled over.csh’. As user omcadmin. execute the following commands: cd $INFORMIXDIR ls -l online. in particular when the server is initialized.ddmmyyyy. [-] Check if the PM database is online. [-] Continued 14-10 68P02901W19-S Oct 2009 .cshrc file and ensure it contains the following line: alias omc_env ‘source /usr/omc/config/global/pmInfxUserConfig. As user omcadmin. Checklist for PM database To check the PM database. [-] Check the IDS log file for errors and checkpointing. enter the following: omc_env onstat | more This utility reports that the database is in online mode. one to check the PM database.

yyyy. As user omcadmin. execute the following commands: cd $OMC_TOP/logs more omc_db_maint.Operating Information: OMC-R System Administration 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? As user root.dd. [-] • PM statistics are deleted successfully. As user informix. As user informix. [-] Check if the PM sqlhosts file has the correct entries for the Informix Server. As user omcadmin. As user omcadmin. [-] Check the status of the dbspaces and chunks of the PM IDS. • Disk space is not being consumed. [-] Check the /etc/services file to ensure a port number exists for the PM IDS. execute the following command: onstat | more Output should be similar to that shown in onstat output for PM database section in Chapter 8. 68P02901W19-S 14-11 Oct 2009 . execute the following command: more /usr/informix/etc/onconfig | grep TAPEDEV. • Applications are connected and reconnected successfully when required.mm. [-] When performing an archive of the PM DB ensure the TAPEDEV parameter is set to /dev/rmt/0. execute the following commands: 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. execute the following command: onstat -d Output should be similar to that shown in onstat -d output for PM database section in Chapter 8. execute the following command: more /usr/informix/etc/sqlhosts_OMC Output should look similar to the example shown in PM sqlhosts in Chapter 8.

execute the following commands: cd /var/mail more root | grep onmode_mib . As user omcadmin. Copy the checklist in Table 14-7.cshrc file and ensure it contains the following line: alias mib_env ‘source /usr/omc/config/global/mibInfxUserConfig. [-] Continued 14-12 68P02901W19-S Oct 2009 . As user informix. execute the following command: onstat | more Output should be similar to that shown in the section onstat output for CM database on page 8-41. [-] Check if the CM database sqlhosts file has the correct entries for the Informix Server. As user root. [-] Check the shared memory structure of the CM IDS. As user omcadmin. As user omcadmin. As user omcadmin. in particular when the server is initialized. [-] Check the dbspace and tblspace allocation for the CM IDS.csh’ To run the updateLocalMaint script execute the following command: setenv CM_LOCAL_MAINT TRUE. execute the following commands: 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.log_OMC* Log files should exist of the format online. execute the following commands: cd $INFORMIXDIR ls -l online. [-] Check the IDS log file for errors and checkpointing.log_OMC.log_OMC This log file should show that checkpoints are completed successfully.Checklist for CM database Chapter 14: Checklists Checklist for CM database To check the CM database.ddmmyyyy [-] Check the output of the onmode_mib cron job. [-] Check if the MIB database is online. enter the following command: mib_env onstat | more This utility reports that the database is in online mode. [-] Check if the IDS log files are rolled over. execute the following command: tail -f $INFORMIXDIR/online. follow the procedure in the section Checking the CM database on page 8-39 in Chapter 8. As user omcadmin. Table 14-7 CM database checklist Check Method Checked? Check if the mib_env alias is setup. As user omcadmin. [-] Check the /etc/services file to ensure a port number exists for the CM IDS. execute the following command: more /usr/informix/etc/sqlhosts_MIB Output should look similar to the example shown in the section MIB sqlhosts file in Chapter 8. execute the following commands: more /etc/services An entry should exist similar to the following: inf7_MIB_serv 5010/tcp. cat the /usr/omc/current/env/. to record the checks.

[-] 68P02901W19-S 14-13 Oct 2009 . [-] When performing an archive of the CM DB ensure the TAPEDEV parameter is set to /dev/rmt/0. execute the following command: more /usr/informix/etc/onconfig | grep TAPEDEV . execute the following command: onstat -d Output should be similar to that shown in the section onstat -d output for CM database on page 8-42.Operating Information: OMC-R System Administration Table 14-7 Checklist for CM database CM database checklist (Continued) Check Method Checked? Check the status of the dbspaces and chunks of the CM IDS. As user informix. As user omcadmin.

[-] Check the status of the network.Checking X. As user root.25 connectivity on page 9-18 in Chapter 9. As user root. [-] 68P02901W19-S Oct 2009 . output. follow the procedure in Checking X. output of the netstat command. Table 14-8 14-14 X.25 connectivity ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ To check X. execute the following command: cd /usr/omc/config/global more x25_config The file contents should look like the example shown in Figure 9-2. [-] Check the integrity of x25. execute the following command: /opt/SUNWconn/bin/x25stat Refer to x25stat output on page 2-76 for example. As user root.25 connectivity. The correct entries are required to configure x25 connections.25 connectivity Chapter 14: Checklists Checking X. For example.25 connectivity checklist Check Method Checked? Check the contents of the x25_config file. execute the following command: /usr/bin/netstat -a Refer to OMC-R system information on page 13-8 in Chapter 12. Copy the checklist in Table 14-8 and use to record the checks.

[-] [-] If the system processor is having some kernel problems. As user root. cd /usr/omc/logs rm -f corefilename [-] 68P02901W19-S 14-15 Oct 2009 . [-] If an OMC-R process is causing severe problems. execute the following commands: 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. 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. As user root. If core files are not required. execute the following command: gcore -o <filename> <process_id> where <filename> and <process_id> are of the particular OMC-R process. follow the procedure in Checking core dumps in Chapter 12. monitor the core files in the /usr/omc/logs directory. [-] Monitor old core files in the /usr/omc/logs/usraudit logs directory. Check the output of the core_presence utility. it exists in /usr/omc/logs. then generate a core of the kernel. remove them as they consume large amounts of disk space. execute the following commands: cd /var/mail more omcadmin | grep core_presence If a core file is generated.Operating Information: OMC-R System Administration Checking core dumps Checking core dumps ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ To check core dumps. generate a core file of the process. As user root. As user root. Copy the checklist shown in Table 14-9 to record the checks.

follow the procedure in Checking disk usage in Chapter 12. As user root. execute the following command: /usr/bin/sar -ru | more [-] Check whether the file systems are full. As user root. Copy the checklist in Table 14-10. execute the following command: cd directorypath rm -f filename [-] Check the available free memory.Checking disk usage Chapter 14: Checklists Checking disk usage ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ To check disk usage. As user root. As user root. to record the checks. As user root. Table 14-10 Disk usage checklist Check 14-16 Method Checked? Check the disk usage of the system. old core files. execute the following command: find filesystem -size +1048576c -print | more [-] 68P02901W19-S Oct 2009 . execute the following command: du -k | more [-] Remove files that are not required and use a lot of disk space. check for existing files that are over 1 Mbyte and analyze the possibility of removing such files. for example. execute the following command: df -k | more [-] For file systems that are over 100% full. statistic files. log files.

create them.Operating Information: OMC-R System Administration Checking disk mirroring Checking disk mirroring ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ To check disk mirroring. [-] Check if the system has at least 3 state databases on each mirror. execute the following command: metadb [-] If the system does not have sufficient state databases. execute the following command: 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. As user root. metadb -f -d /dev/dsk/c1t2d0s3 /dev/dsk/c2t2d0s3 [-] Check 68P02901W19-S 14-17 Oct 2009 . Refer to Logical Vol Mgr troubleshooting on page 13-42 in Chapter 12 for the procedure to recover a lost disk. follow the procedure in Checking the CM database on page 8-39 in Chapter 12. As user root. Copy the checklist in Table 14-11. execute the following command: metadb -a -f slice-1 slice 2 etc For example. Table 14-11 Disk mirroring checklist Method Checked? Check the DiskSuite status. to record the checks. Subdisks needing maintenance have to be repaired. As user root.

As user omcadmin. execute the following command: cd /usr/omc/logs ls -l fpomc* [-] Continued 14-18 68P02901W19-S Oct 2009 . As user omcadmin. As user omcadmin.*“ -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. As user omcadmin. execute the following command: ps -elf | grep + | grep Parser [-] Check if the FMPATH environment variable is set.0 -name “*. As user omcadmin. execute the following commands: /bin/find $OMC_TOP/ne_data/raw_stats/100. execute the following command: tail -40 $SYS_LOG/fpomcaudityyyymmdd. execute the following commands: echo $FMPATH This environment variable should be set to: /usr/omc/ne_data/raw_stats [-] Check if any raw statistics files have escaped processing by the parser. [-] Check if the fpomcaudit logfile is rolled over and old log files are removed successfully by the maintain_script cronjob. As user omcadmin. execute the following command: $PM_ROOT/bin/pm_manual_parse filename Check for any error messages from the pm_manual_parse utility. execute the following command: tail -f $SYS_LOG/fpomcaudityyyymmdd Successful parsing output is shown in Parsing output in Chapter 2. The log file shows that files are being parsed again successfully. the stats collection and parsing resumes without manual intervention. [-] Check if the manual parse was successful. [-] Check that even if the Parser process fails and is restarted.Checking for successful parsing of statistics Chapter 14: Checklists 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 Manual parsing of statistics checklist Check Method Checked? Check if the parser process is operational. As user omcadmin.

Operating Information: OMC-R System Administration Table 14-12 Checking for successful parsing of statistics 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. [-] 68P02901W19-S 14-19 Oct 2009 . Refer to Using neighbor statistics on page 13-91 in Chapter 12 for further details about rasing the maximum limit of neighbor statistics. execute the following command: omc_env cd /usr/omc/current/sbin db_disconnect connect parser [-] Monitor the value of the neighbor statistics environment variable. As user omcadmin.

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.Recording details Chapter 14: Checklists Recording details ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ There are two procedures that require details of machines and accounts to be recorded and kept for future reference. and Jump starting GUI server/client processor in Chapter 11. They are Setting up a night concentration centre in Chapter 2. 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. Copy the following tables. 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 . 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.

enter the details and store the information safely. Copy the following tables.Operating Information: OMC-R System Administration Client and server partition details Client and server partition details The procedure to which these tables apply is described in JumpStarting GUI server/client processor in Chapter 11. Log and JumpStart details Backup Log partitions JumpStart partitions / /usr/omc /gen 68P02901W19-S Oct 2009 14-21 . Table 14-15 Client and server details GUI client / server name Table 14-16 Filesystem GUI client / server IP address Filesystem.

Client and server partition details 14-22 Chapter 14: Checklists 68P02901W19-S Oct 2009 .

. . . . 12-58 View Archived message log files for the CM Database . . . . . . 3-16 . . . . . . . . . . . . . 12-55 Monitoring the active message log files for the CM database . . . . 12-60 Backing up the PM Database . . . . . . 12-16 Procedure for backing up file systems using backup_MMI utility . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-62 Backing up the PM and CM Databases (contd. . . . . . . 12-59 Overview of IDS message log files for the CM Database . 12-16 Overview to backing up file systems using backup_MMI utility . . . . 2-46 Capacity control mechanism . . . vari. . . . . . . . . . . . . . . . . . . . . AUTOSTART_PMGUI . . . . . . . . . . . . . . . . . . . . . . . . . . .25 . . . . . . . 12-55 Backing up the CM database . . . . . 4-11 6-24 . .) Monitoring the active message log files for the PM Database . . . 3-19 . . . . . . . . . ADDINFO_IN_HEX environment able . 12-55 Default DAT tape parameters . . . . . . . . . . . . . . . . . 6-23 . . . . alarms . 13-50 CDE . . . 13-33 IX-1 . . . 2-46 CD-ROM eject failure . . . . . . . . . . . 3-12 . . . . database . . . . . . . . . . . . . . . . . . 6-10 . . . . . . . . . . . . . . . . . . . 68P02901W19-S Oct 2009 . . . . . . . AT command description . . . . 6-10 . . . . . . . . . . . . . . . . . ATC_TIMEOUT environment variable . . . . . . . . OMC events . AUTORESYNC environment variable . . . . . . . . . AUTORESYNCDELAY environment variable . . . hardware failure . . . . . . . . . . . . . . . . 13-28 C Call Success Monitoring . . . . . . . . . for MultiModem. . . . . . . . . . . . . . . . . . . 3-7 8-32 A ABORT_UPL_RL_IN_PROG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-57 Checking and changing tape parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-55 Level of backup . . . . . . 13-66 . . . . . . . . . . disk space usage . 6-23 environment . . . . . . 12-17 Backing up the PM and CM Databases . . . . . . CALL_SUCCESS_THRESHOLD variable . . . . . . . . . . . . . . . . . . . . . neighbour statistics . . . . . log files . 6-6 . . 6-13 13-78 13-83 13-79 13-86 2-47 . . . . . . . audit limits . . . . . . . 3460 Fast'R modem . . . . . 12-61 Overview of IDS message log files for the PM Database . . . 12-59 bootup troubleshooting . . . . X. . . . . . . . . . . . . . . . . 12-62 View Archived message log files for the PM Database . 13-88 . .Index Index ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ 32000 statistics checking for an excess . licence violation. all ports busy . activity tools . . . . capacity control . . . . . . . 4-5 13-93 13-86 13-85 . . . . . . . . . . . . . . . . . . . . . . . . . . . audit log files checking for success . . . . . . . . . . . . . . . . . . . . . . . . 6-6 B Backing up the GUI Server File System . . 2-3. . . . .

. . . . . . . . 2-28 using a tarred software load . . . 5-14 maintaining cron log files . . . . . 2-74. . . . . . . . . . . . . . . . . . . . . . . 1-24 core dumps . . . . 8-9 environment variable used by . . . . . . . . . . . . . . . . . . . . . . . System Processor hardware. 14-8 PM database . . . . . . . . 2-28 reasons for cleaning up loads . . . . . 13-6 checking . . . . . 9-18. 6-10 dbms log files . . . . . . . . . . . . . . 6-16 Detail Serial Port Manager. . .Index Configuring the SunFire and Netra System Processors . . . . . .cshrc. 2-31 monthly administration . . . . . . 5-9 command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28 . . . . . . . . . db_config files. . 8-39 checking and recovering tables . . . . . . . . . . 4-7. . 13-88 X. . . . . 6-11 Cyclic Neighbour Statistics feature . . . . . . 14-16 general administration . . . . . . . . . . . database maintenance . . . . . . . . . 5-3 removing . . . . . . . . . . . . . . . . 1-29 . . . . . . . . . . . . . db_disconnect utility . 8-4 CM sqlhosts file . . . 14-3 disk mirroring. . . . . . . . . 13-70 onconfig file . . . .) installing . . . . . . . . . . . 14-6 OMC log files . . . . . . . . . . . .25 connectivity . 14-15 daily administration . 1-9 Connecting peripherals SunFire 4800/4900 and Netra 20/440. 5-5 on the System Processor . . . . . . . . . . . . . . . . . . . . 1-24 D daily procedures core dump files . . . . . . . . . . . . . . . . . . . . . . . . 2-19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6 core_presence utility core_presence (omcadmin) . . . . . . . 2-3 configuration files . . . . . 2-29 CM database checking . . . . . . . . . . . . . . . 13-73 monitoring space and fragmentation . . . . . 6-23 CSMMAIN process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29 . . . . . . . . . . . . . . 1-11 Connecting to the LAN LAN . . . 1-29 . . . . . 8-26 reading the database scheme . 5-17 viewing . . . . . . . . . . . . . 4-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 crontab files printing . . . . . . . . . . . . . . 8-39. . 14-12 core dumps . . . . . . . . . . . 2-80. . 5-16 modifying . . . . . . . . . . . . . . . . . . . . . 1-29 . . . . . . . . 8-22 starting up . . . . . . . . . . 2-14 critical processes . 6-3 CSM_ENABLED environment variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-79. . . . . . 1-29 . . . . . . . . . . 6-23 CT_1208LOG . . . . . . . . . . . . . . . . . . .private file . . . . . . . . . 13-36 troubleshooting . . . . . . 5-14 . . . . 5-5 on GUI Processors . . . . IX-2 db_disconnect utility (contd. . 6-11 Comment User Management . . . . . . . . . . . . . . . . . . . . 13-70 defragmenting tables . . . . 6-42 system . . 5-13. 13-52 DEF_GSM_CELL_ID environment variable . . . . . .) . . . cron jobs . 5-12. . . . OMC-R log files . . 9-3 Configuring the OMC-R based LAN . . . . 14-15 removing . . 13-33 login failure . 6-6 Create Home Dir User Management . . . . . . . . . . . . . . . . . 5-5 timesynch . 6-41 verifying . . . . . . . . . 13-91 CDE (contd. . . . . . . .CNFG file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14 Common Desktop Environment CDE . 8-18. 5-12 omcadmin . . . . . . . 8-34. . . . 8-40 CM_NMC_AUTO_NUM environment variable . . . . . . . . . . . 5-15 batch scheduler . 3-14 COUNTRY_CODE . . . . 13-88 FM_audit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7. . . . . . . 8-16 db_pm_maint utility dbpmmaint utility . . . . 13-73 shutting down. . . . . . . . . 13-87 cron jobs adding . . . . 3-4 68P02901W19-S Oct 2009 . . . . 14-14 Cleaning up OMC-R software loads keeping software loads . . . . . . . . . 14-3 manual parsing of statistics . 8-8 dbdisconnect utility . . . . . . . . . . . . . . . . UNIX file system maintenance Database Applications menu . . . 13-94 . . . . . . . . . . . . . . . . . . . . . . . 2-49 Criticalstatseventsdiscarded (30078 alarm) . . . . . . . 13-6 running process . . . . . . . . . . . 5-16 site_timesynch . 8-21 to 8-22 utilities . . . . 13-34 Checklists CM database . . . 14-5 X. . . . . . . . . . 2-74. 14-10 weekly administration. . . . . . . . . 5-7 corepresence utility . 13-7. . . . . 13-23. . 13-6 Country Code use in AT command . .25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-47 disk usage.

. . . . . . . . . . . . . . . . . . . OMCFEATURES . . . . . . RECIPROCATE_NBR . . . . . . . . . . 6-15 BSS_VER . . . . MMI_EVENT_ADDITIONAL_INFO_WIDTH . . 6-6 ENABLERESYNC . . . . . . 6-9 CFG_KEEP_STATS_FILE . . . . . . . . . . . . . . . . . . MMI_EVENT_OBJ_CLASS_WIDTH . . MMI_CLEAR_INACTIVE_FMIC . . . . . . . . . . . . . . . . . . . . usage limits . . . . . . . . . . . 13-79 . . . . . . . . . . . . . . . . . . MAX_AUTO_RESYNCS . 3-9 . . . . MMI_EVENT_TYPE_WIDTH. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13 ATC_TIMEOUT . . 1-19 . . . . . . . . . . . . . . . . . . . . . . . . . . .Index dial-in serial port . . . . 6-7. RL_SESSIONS . . . . . . . . . . . . . . MMI_ALARM_STATE_WIDTH . . . . . . . . . . 6-13 ALG_WARNING . . 6-16 DEL_CELLX_FILES . . . . . . . . . Disk Capacity Tool . . . . . . . . checking disk freeing up . . . . . . . . . . . . . . . . . . 6-15 CALL_SUCCESS_THRESHOLD . . 3-17 environment variable modifying . . . . . . . . . . 3-22 EMDisconnectedFromDB alarm. . . . . . . . . . . . MMI_EVENT_ID_WIDTH . 6-15 DEF_GSM_CELL_ID. . . . . . 13-91 ENABLE_CYCLIC_NBRS env . . . . . . . . . . . . . . . . . . . . . . . . . disk space alarms . . . . . . . . . . . . . . . . . . . . . . . . . . MMI_ENABLE_FMIC . . . . 6-22 FM_IERROR_ALLOWED . . . . . . PRINTER . . . . . . . . . . . . . . . . . . . . 6-11 DOUBLE_CLICK_NEXT . . . . . . . . . . MMI_EVENT_OPERATOR_NAME_WIDTH . . . 13-88 E eeprom settings . . . . . . . . . . . 6-23 CFG_KEEP_NMC_FILE . . . . . . 6-8. . . . . RL_TIMER_NC . . . . . . . . . . . . . . . . . 6-11 COUNTRY_CODE . Disk configuration SunFire and Netra . . . . . . . . . 14-17 . . . . . . . . 6-6. . . . . usage. . . . . . . . . . . . . 13-47. . . . . . . . PM_MAX_NEIGHBOURS . .) checking . . . . . . . . . MAX_CSFP_BLP . . INFORMIXDIR . 6-22 68P02901W19-S Oct 2009 environment variables (contd. 6-24 ABORT_UPL_RL_IN_PROG . . . . . . 6-26 environment variables . . . 6-16 ENABLE_CYCLIC_NBRS . . . 6-10 AUTORESYNC . . . . MMI_EVT_FILTER_NUM_LOGS . . . . . . . . . . . . . . 6-24 AUTORESYNCDELAY . . . . . . 6-9 CM_NMC_AUTO_NUM . . . . . . . . . . 6-22 FM_OERROR_ALLOWED . . . . . . . . . . . . . . . . . 6-22 FM_MEM_AUDIT . . . . . LANGUAGE . . . . . Disabling status of Consolidated Alarms. . . MMI_EVENT_INFO_WIDTH. . . . . INDFORMIXSERVER . . . . . 6-11. . . . . . . . . . . . . . 13-83 ENABLE_AUTO_EMAIL_ON_REASSIGN environment variable . MMI_START_WINDOW_AS_UNSPLIT . . . 6-30 . . . . . . . . . . OMCREDRAW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RL_LOGCMDS . . . . . . . . MMI_EVENT_OBJ_INSTANCE_WIDTH . . . . . RL_TIMER_DT . . . . . . . . . . 6-16 ENABLE_AUTO_EMAIL_ON_REASSIGN . . OMC_TOP . . . . . . . . . . . . . . . . . RL_LOGRESPS . . . . . . . . . . . . . . . . . . . 14-16 . . disk mirroring (contd. . . . . . . . . . . . . . . . . . 13-21 . . . 13-23. . . . . . . OMCAUDIBLESEVERITY . . . 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 . 6-11. . . . . . . . . . . MIN_TOTAL_CS . MAX_BOOTLOADS . . . NX_ENABLE_TIMESLOTS . . . . . . . . log files . . . . . . . . . . . . . . . . . . . . . PER_SITE_AUDIT_DEBUG . . Disk Activity Tool . . . . . . . . . . . . . . 13-67 . . MAX_UPLOADS_PER_CHAN . . . . . . NO_OF_PARSERS . . . . . PM_HOURLY_STATS . 6-6 ENABLERESYNC environment variable. . . . . . . 6-16 DEFAULT_REMOVE_CLEARED_ALARM_TIME . . . . . 6-6 ADDINFO_IN_HEX . disk mirroring . . . . . 6-15 AX_LANG . . . . . . . . . . . . . REGION. 6-12. . . 6-23 DBNAME . . . . . . 6-24 enabling login for modems . 6-16 ENABLE_CYCLIC_NBRS environment variable . . . . . . MMI_EVENT_TIME_WIDTH. 6-6. . . . . 6-15 CSM_ENABLED . . . . 13-66 . . . . . . . . . . 6-7. . . . . . . . . . . . . . . . . 6-6. . . . . . . . . . . . . . . . . . . . . . PER_SITE_AUDIT . . 6-16 DEFAULT_REMOVE_CLEARED_ALARM . . . 6-10 AUTOSTART_PMGUI . . . . . . . . . . . . . . . . . . . . . . 6-10 AU_APPLY_DELETES_FIRST . . NETWORK_CODE. . . . . . . . . . . . . . . . . . . . . . . . . 6-15 BSS_NAMING. . . . . . . . . . .) FM_OHUNG_ALLOWED . . . . 6-24 FM_CPU_AUDIT . . . . . . . . . . . . . . .

. . . . . . . 4-5 . . . . 13-61 I INFORMIX database IX-4 68P02901W19-S Oct 2009 . . . 2-9 . . . . . 6-23 . . . . . . . . . . . . . .CNFG file . . . . . . . . . . . . Group Name Group Management . . . . 2-67 GUI Server log files . . . . . . . . 6-24 . . . . . . . 9-7. . . . 2-22 FM_IERROR_ALLOWED environment variable . . . . . . . . . . . file transfers and modems . . . . . . . . . . . . . . . 6-9 . . . . . . . . . . . . . . . . . . . 2-10 . 13-25. . 13-38 . . . . . . environment variables (contd. . . . . . . . . . . . . . . 6-13 GUI Processors processes . . . . . . . . . . . 6-3 G gcore command . hosts file . . . . . event log files . . 2-13 GUI processes environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FM_OHUNG_ALLOWED environment variable . . . . .equiv file HSI/S cards replacing . . . 2-10 . . . . . .) SITE_NAMING . . . . . . . 2-9 H Hard copy listings. 13-54 . . . . . . . . . . . . . . . . . . . 13-27 shutting down. . . . . . . . . . . . . . . . . . . . . renaming . . . .equiv file event alarms . . . . . . . . . . . . . . . . . . 2-9 . . . 2-44 13-38 13-38 13-86 . . . . . host name changing . Group Management . 7-9 single user mode . . . . . UPL_KEEP STATS_FILE . . . . 6-22 6-22 . . . 13-53 . . . . . 2-8 . . . . . 6-10 . . . . . . . . . . . . . . . . . . 13-57 . . . .Index /etc/dfs/dfstab file . 13-21 . . . . . . Graph Tool . . . . . . . . . . . . . . . . . hardware failure alarm history file loading . . . /etc/hosts. modifying . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9 GUI server rollback . . . . . . function keys . . . . . . . . . . . . 13-6 . . . . . . . . . 2-11 . deleting . . . . . . Overview . . . . . . . . . . . 6-13 . . . . . . . . . . . . . . . . GUI ensuring the correct colours appear . . . . . . adding . . Horizontal Bar Graph Graph Tool . . . . . . . . . FM_CPU_AUDIT environment variable . . . . . . . 4-5 13-24 . . . . . . . . . 6-9 . . . . . . . . . . . . . . . . . TTY_FILTER. . . . home directories access failures . . . SUB_RES_TIME. . . 1-34 . . . TIMER . . . . hosts. . . . . . . . . . . . . . . . . . . . . FM_MEM_AUDIT environment variable. . . . . . . . 13-34 . . . . . . . . . . saving configurations Group ID Group Management . . . . . . . . . . . . . 13-88 . 9-17 . . . . . . 3-18 . . . . 6-20 . . . . . . . FM_audit. . . file systems freeing space . USE_LONG_SITE_NAME . . . . . 11-8 . . . . . . . . . . . . . 13-38 . . . . . 6-20 . . 13-86 . . . . . . . . 2-10 . . . . /etc/hosts file . . . . . . . . . . . . . . . . . . 6-22 F File Manager . . . . . . STATE_ON_AUDIT . troubleshooting . . . . 6-22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FM_OERROR_ALLOWED environment variable . .

. . . . . . . . . . . . . . 6-6 6-6 3-7 6-31 . . . 8-13 . . . . . . testing connection . . . . . . . . . . . . . . . . . . . . . . . CM database . . . . INFORMIX database logs . . . . . 6-18 MMI_START_WINDOW_AS_UNSPLIT environment variable . . . . . . 4-5 4-5 4-6 5-6 1-29 13-8 . . . . . 6-18 MMI_EVENT_OBJ_INSTANCE_WIDTH environment variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PM database . . . . . . . . 4-5 . . . . . . . . . . . . . . . . . . . 13-36 . . . . . . . . . . . . . 6-13 mmi utility . . . . . . . 6-18 MMI_EVENT_TYPE_WIDTH environment variable . . . password fails. . . . 3-27 M maintain_script utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ids . . . . . . . . . . . . . . . . . 3-21 . . . . . . 6-23 Miscellaneous daily procedures . . . . . . . . . 8-16 1-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lp command . . . . . 8-15 . . . . . . . . 13-79 . . . . . . . . . . . . Introduction to setting the status of the Consolidated Alarms . . . 4-6 event logs . 3-24 . . . Line Plot Graph Tool . . . . 8-13 . . . . . . . . environment variables log files (contd. . . . . . . . . . . . . . . . . . 2-55. . . failure . . . . . . . . . . . . . 13-52 . . . 1-29 MMI processes GUI processes. . 6-29 . . . . . . . . . . . Local GUI server rollback . . . . . . . 2-67 1-26 . . 6-18 MMI_EVENT_OBJ_CLASS_WIDTH environment variable . . sys_info files . 3-10 IX-5 . . . . . . . . . . audit . . . . . 13-59 MIN_TOTAL_CS environment variable . . . . . . GUI Processor files . . . . . . 1-30 . . . . . . . . 5-6 MAX_BOOTLOADS environment variable . . . . . 6-18 MMI_EVENT_OPERATOR_NAME_WIDTH environment variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . routine procedures . . . . . . . . . . . . . . . . . IPC logs . . . . . . . 13-38 13-38 13-37 6-16 13-85 . . . . . . . . . . . . . 6-6 MAX_CSFP_BLP environment variable . . . 6-27 modem adding . . . . . . . . . . . login corrupt message . . Installing a modem . . . . . . . . . . . . . . System Processor files . . . . . . . . . . . . . . . . . . maintaining . login prompt troubleshooting for modems LowerLimitDiskUsage alarm . . . . . . . . failure . . . . . . . . . . . . . . . 13-52 . . . . . . . . . 13-83 . . . . . . . . . . . . . . 13-58 viewing . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 communicating . . 6-18 mnemonic process name . . . . . . . . . 4-6 L LAN failure . . INFORMIX database (contd. . . . . . . . . . . . . . . . 6-7. . . . . . . . . . . . . . . . . 6-7 metrics selecting . . . Quiescent mode . . . . . . . . . . 6-17 MMI_CLEAR_INACTIVE_FMIC environment variable . . . . variable . . 4-5 . . . . . . . . . . . . . . . . . . . . . . . . . 6-7 MAX_UPLOADS_PER_CHAN environment variable . . . . . dbms . . . . . . . . . . 4-11 4-5. . . . 6-7 MMI_EVENT_ADDITIONAL_INFO_WIDTH environment variable . . . . . . . . . . 13-60 . . . . . . 6-18 MMI_EVT_FILTER_NUM_LOGS environment variable . . . . .Index INFORMIXDIR . . . . . . . . . log files alarm logs. . . . . . . . . 6-17 68P02901W19-S Oct 2009 MMI_EVENT_ID_WIDTH environment variable . . . . . . . . . . . . . . . . . . . . . . . . . . log files . . . . . . . . . . . 6-18 MMI_EVENT_TIME_WIDTH environment variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14 . . . . . . . . . . . . . . LANGUAGE environment Level123Failure alarm . . . . . 6-17 MMI_ENABLE_FMIC environment variable . . . . . . . . . 7-4 MMI_ALARM_STATE_WIDTH environment variable . . . . . . . . 2-40 . . . . . 3-24 . . . . . routine procedures . . . 6-17 MMI_EVENT_INFO_WIDTH environment variable . INFORMIXSERVER . . . . . . . . . . . . . . . files . . . . . . . . IPC log files . . . . . . Introduction to non user configurable environment variables . log book. . . . .) alarms . . . . . . . . . . . . . . . .) . . . .

. . . . 1-32 . . . . multiuser mode GUI Processor . . . . . . . 7-12 . controlling access . . . . . . . . . . . . . SPARCstation setup . . . . . installing . . . . . . . . . . . . . . . . . . . . . . . . . eeprom settings . . . . . . . . . . . . . . . . . . . . . . . . . UNIX file system . . . . . . 13-94 . . disconnection problems . . 13-94 . omc_db_maint (root) . . . . . . . naming conventions . . neighbour statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . data links . . . resizing . . . . hangs up . . . . . System Processor . 2-61. . . . . . . . . . . . . . 2-46 . . . . . . . . . . . NHA tool . . . . . NX_ENABLE_TIMESLOTS environment variable . . . . . . . . MT5634ZBA modem . 3-14 . 2-35 2-49 to 2-50 . . . . . . . . . . . . 7-12 omcdbckspace utility . . . . . . . 1-7 1-7 2-67 68P02901W19-S Oct 2009 . . monitor_diskspace utility monthly procedures . . monitor_ct_logs utility . . . 2-30 2-30 2-31 1-33 .) . . . . . . . . . . . . . . . . . . . . . . . starting up . . . . . . . . . . . . . . . . . . . OMC processes . . . . . . stale file handling . . . . limitations on use . . . . . . . . . . . . . . . . . . . . . permission denied. . . . 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 . . . . . . . . . . . . . Motorola contacting. transfers . . errors . . . . . . . 5-8 8-7. . . . . . . . . . . . removing NE fallback software . . . . . . . . . . 13-49 . . . . . . . . . . . . . . . . . . . 11-5. . . . . . . . . . . . . . . . 1-32 . . . . . . . . . . . . . . . . . . . . . 13-27 7-13. . . . . . . . . . . . rates . Night concentration centre configuration . . . . . . . . . . . . . . . . . . . .) modem (contd. . . . . . . . 13-3 3-12 . . . . . . . . . . no login prompt . . . . . . . . . . . . . . 5-7 . . . . restarting . . . mounting a device troubleshooting . . . . . . . . 7-9 7-9 N nbr_entity table resizing . . . . . . . omcdbmaint utility . . . . . . . . . . . . . OMC event alarms . . . . . . . . . . . OMC-R remote user accounts deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NFS . . . . . . . . . . . . . . . . . . . . . . . troubleshooting . . . printing . . . . . . . . . . . . . . . . . . . . Netra System Processor configuring . . . . . . . . . . . . displaying . . . . . . . . . . . . . . . . . . . . . . . . . . . . remote connection and file setup . . . . . . . . . . 3-14 . Network File System NFS . . . . . . . . . . . . . . . 13-94 . . . . 8-10 . . 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 . . testing NIS server. . . . . . . . 13-25 . . . . . . . . . . . . Motorola 3460 modem . . . . . . . . . . . shutting down. . . . . . . . . . . . . . . omc_db_maint utility automatic (cron) procedure . . . . . . . . . . . . . . . 8-6 to OMC-R JumpStart CD . . NIS commands . . . prerequisites for setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . network status . . omc_db_ckspace utility IX-6 omc_db_ckspace utility (contd. . . .) configuring . . . . . . . . . . . . . . . . . . . . 6-42 13-91 13-93 13-91 13-91 13-91 13-94 13-94 . . . . . 8-23 . . . software requirements . . NIS domain adding a group . . . NE maintenance synchronizing times . . . . . . . . . . . 13-86 . 8-23 to 8-24 . nbr_statistics table . . . . . . . routine procedures . .Index modem (contd. . . . . . . . . . . . . . . . . tipping . . . . . . . . . . . . does not pick up . . . . . . . 5-7 . enabling cyclically . . . . . . . . . . . . . 3-19 . . . NEIGHBOUR variable. . . . . . . . alarm . . . . . . . . . . . . physical connection . . raising maximum limit . . . . enabling login . . . . . . . . . . . . . . . . . . . . . . . . . MultiModem . 13-25 . NE database maintenance archiving/removing an NE database PM database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . adding a user . . . enabling. . . . . . . . . . . . . . . . .

. . . . . 13-87 . . . . . . . . . . . . . . . 8-16 . . . . . . . . . . . . . . . . . . . . . . . 2-57 on all processors . . . . 8-13 emptying and defragmenting statistics tables . . . . . . OMC_TOP environment variable . 2-42 conventions . . . . . . . . . . . . . 3-9 power failure . . . 13-70 onconfig file . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6 to 8-7 monitoring space and fragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-53 . . . . 13-52 PM_HOURLY_STATS environment variable . . . . . 3-27 configuring . . . . . . . . . . . . 6-36 IX-7 . . 1-33 PM sqlhosts file . . . . . . . . . 3-25 PRINTER environment variable . . . . . . 8-26 . . 3-25 address . . . . . . . . . . 6-19 2-55. . . . . . . . . . . . . . . . . . . . . . . . . . 8-26 reading the database schema . . . . . . . . 8-3. . . . . . 13-53 . . . . 13-14 utilities . . 2-14 Print Manager disabling . . . . . . . . . . onstat -d output for CM database onstat -d output for PM database onstat output for CM database . . onmode_pm utility . . . . . . . . . . . . . . 8-16. . . . 3-23 Pie Chart Graph Tool . . . . . . 3-27 printing . . . . . . 13-83 password login failure . . . . . . . . . . . . . . . . . . . . 8-41 . . 13-94 PMCyclic . . . . . . . . . . . . . . . OMCREDRAW environment variable . . . . . . . . 8-4 PM raw statistics maintenance . . . . . . . . . . . .def file . . . . . . . . . . . . . . . . . . . . . . 2-42 Packet Switch . . . 13-34 printer adding . . 1-33 6-19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . omctool utility. . . . . . . . . 6-19 6-19 onmode_mib utility . . . . . . . . . . . . onperf_pm utility . . . . 5-6 8-5. . . . 13-70 configuration files . . . . . . . 8-35 . . . . . . . . . . . . . . . . . . . 2-49. . . . . . . . . . . onconfig file . . . . . . 3-25 checking installation . . . . . . . . . . . . . . . . . . . . . 6-8 PMMAXNEIGHBOURS environment variable . . . . . . . . . . 13-86 . . . . . . . . . 3-27 processes OMC processes . . . . . . . . . . . . 3-26 name . . . . . . . . . . . . . 2-43 parserDisconnectedTooLong alarm . . . . . . . OMCFEATURES environment variable OMCOverloadedEventsDiscarded alarm . . . . 8-11 troubleshooting . . . . 3-24 Password User Management . . . . . . . . . . . . . . . . . . . . 1-7 P Packet Switch passwords . . . . . . . . . . . . . . . . 13-91 PMDisconnectedFromDB alarm . . . . . . . . . . . . . . . . . 2-14 passwords. . . . . . . . . . . 13-98 restarting GUI sessions . . . . . . . . onperf_mib utility . . . . . . . . . . . . . . 13-97 restarting the OMC-R . . . 13-26 processor times synchronizing . . . 13-97 on GUI server and clients . 13-34 enabling. . Optional processors . . . . . . . . . . . . . . 8-22 status . 13-98 power supply unit failure . . . . . . . . . . . 13-76 checking . . . 8-37 . . . . . . . . . 8-35 PM statistics parsing . . . . 13-97 UPS . . . . . . . . . . . . . . 8-34 checking and recovering tables . . . . . . . 8-22 starting up . . . . . . . 6-27 . . . . . 6-8 68P02901W19-S Oct 2009 pm_manual_parse utility . . . . . . 2-57 graceful shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32 permission denied or link down . . 8-42 . 13-63 PM database adding extra logical logs to DB server . . . . . . 3-27 configuration file . . . . . . . . . . . . . . . . . . . . 13-83 port monitor services . . . . . . . . . . . . OMCAUDIBLESEVERITY environment variable . . . 4-5. . . . . . . . . 6-19 printer. . . onstat output for PM database . . . . . . . . . . OMCOverloadedWithEvents alarm . . . . . . . . 2-43 routine procedures . . . . . 8-11 pm_manual_parse utility . . . . . . . . . . . . . . . . . 13-98 Primary Group User Management . . . . . 13-98 on the System Processor . . . . . . . . . . . . . . onmonitor utility . . . . . . . . . . 13-74 maintenance . . . . . . . . 2-30. . . . . . . . . . . .Index OMC-R users user accounts . . 5-7 . . . . . . . . 13-94 directory structures . . . . . . . . . . . . . 8-11 PM_MAX_NEIGHBOURS environment variable . . . . . . . . . . . . . . . . . . 8-19. . 1-6 . . . Operator workstations . . . . 13-73 shutting down. . .

. . . . . . . . . . . RL_SESSIONS environment variable . . 1-33 1-28 1-34 1-30 1-32 1-33 1-34 1-34 1-32 1-30 1-30 . . . . . . . . . . . . . . 2-44 login ids. . . . . . . . . . . 13-68 Setting status of Consolidated Alarms . . . . . . . . . . . . . 5-7 . . . . . . . . . . . . . . . . . . subscriptions backing up . . . . . . . . . . . . roll_paging_log utility . . . . . . . . . . . . . . . .rhosts file rhosts file . . . . . . . . . . . . . . . . 5-7 . . . . . 6-21 . remote login SPARCstation corruption . . SPARCstation corruption. . . . . . . . . . . . . . . . . . . . . . . . . . . . run levels . . . . . . . . 2-36. . . . . . . . . . . Remote monitoring station configuration . . . setup . . . . . . monthly . . . . . . . . . . . 8-16 R RC. . . . . . . . . . . . . . . . . 3-8 13-64 13-51 2-21 8-32 8-32 1-19 68P02901W19-S Oct 2009 . 6-21 . RL_LOGCMDS environment variable . . . . . . . . . . . . . . .CNFG file . . . . . . . . . . Enabling or Disabling a Group Backup . 2-41 Security related weekly procedures . RLOGIN variables . . . . . . . . . . . . 3-6 setting baud rate . . 2-59 2-49 6-24 . . . . 7-9 System Processor . . . . . . . . . . . . 13-6 Secondary Groups User Management . . . . . . . . . . . . . routine procedures complete file backup . . . . . . . . . 7-4. . . . . . . . . . . . . 5-8 12-11 12-10 13-25 13-42 3-22 . . . . . . . . . . . . . . RL_LOGRESPS environment variable . . . . . . . . . . . . . 1-26 2-46 2-47 7-3. . . 7-7 Single platform processor rollback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 Session Activity Tool .Index Q Q3 naming . . . . . . . . . . . . . . . subscription lists backing up . . . . . . . . 13-65 Quiescent mode INFORMIX database . . . . . . . . . . . . . . . StorEdge Enterprise Backup troubleshooting . . system configuration . . 6-24 6-19 3-18 . . updating licence . . . proce. . . . . . . . . . . . . . . . . 6-22 . . . . . . . . . . . Running Night Concentration procedure . . . . . . . . . . . . 3-6 Serial Port Manager. . . . restartable processes . . . . . . . 5-7 savecore utility . . 2-64 exporting file changes. . . . . . . . . . . . . INFORMIX database . . . . 6-21 . . . . . . 3-22 . . . . . . . . . . . . . . . . . . . . . . . 13-38 . . . . . . . . . . . . . . . . . . . . ResyncCtrl process . . . . . . . RTF limit . 1-31 serial port . . . . . . UNIX file systems . Software Installation Deleting a Group Backup client . . . . . . . . . . . . . . REGION environment variable . . . . . . . . . . . . . 6-29 Setting up a Night Concentration Centre creating a new account . . RL_TIMER_NC environment variable . . . . . 7-7 . Style Manager . . . . . . . . . . . . . . . . . RL_TIMER_DT environment variable . . . . . . . . . . . . . . . . . . . . . Routine system administration dures . . . . . . software processes OMC processes . . . 2-66 S sar_per_day utility . Solaris Logical Vol Mgr disk configuration troubleshooting . Status Tool . . system core dumps . . . 2-68 single user mode GUI Processor . . . . . . . 1-28. . . 2-63 shutdown utility . . . SunFire System Processor . . . . . 2-64 updating host file entries . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11 Query Tree . . . . . . . . . . . . . 6-21 . . . . . . . . . . . . . 7-9 site_timesynch utility IX-8 site_timesynch utility (contd. . . . . . . . . . . . . . . weekly . . . .) site_timesynch (omcadmin) . . . . . . . . . . daily . . . . . SunFire and Netra disk configuration . . . remote connection . . . . . . . . . . . 2-14 security . . NE database maintenance . . . . . . . . . . . . . . . . 3-3 adding a modem . . . . . . . . . . . . . . . . . . . . 6-21 . UNIX file system . . . . roll_online utility . . . . . . . . . . . . . . hardware maintenance . . . .

. . . . . . . . 13-26 . . . . system core dumps core dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7 UPL_KEEP_STATS_FILE environment variable . . sys_info files . . . . . . . . . . . . 13-8 user accounts adding . . . . . . . CM database status . . . . . . 1-4 processes . . . . . . . . . 2-15 renaming . . . . . . . . . . . . . . . . . . . . . . . . . 2-16 modifying . . 6-36 synchronizing . . . 2-13 68P02901W19-S Oct 2009 User Management . . . . . . . . . . . . . . . . . 13-86 log files . . . . . . . . . . X. . . . . . . . . . . . . . .) configuring . . . . . . . 2-8 /usr/gsm/logs/sys_info files . . 6-20 . . . . . . . . . . . . . . . . . . . . . . . . architecture . . . . . .) . . . . . . . . . 6-10 UpperLimitDiskUsage alarm . . . . 13-8 system resources . . . 1-9 9-3 9-3 13-6 . . . . . . . . . System Processor . . . . . . . . . . . . . 13-9. . . . TIMER environment variable tipping a modem . . . . . . . . . . . swap space System Processor . . . . . 13-99 environment variables . . . . 13-12 system resources System Processor . . . . . . . . . . . . . . . . . . . 13-34 User-configurable environment variables . . . . . . . 2-12 to 2-13 adding . . . . . . . . . . . . . . . . . 6-41 system uptime . . 13-9 . . . 7-3 shutting down. . . . . .25 communications . . . . . . 2-58 uptime . . . 6-5 System processes and PM database configurable variables . . . 6-36. . 2-16 User Name User Management . . . . . . . . . . . . . . . . . traffic channel capacity RTF limit . . . . .Index SunFire System Processor (contd. . . . . . . . . . TTY_FILTER environment variable . 13-12 system time setting . . . . . . 13-8 13-14 6-36 13-8 13-17 13-11 13-14 13-9 13-8 13-10 13-19 . . . 13-25 to 13-26 run level . . . . . . . . . . . . . . . . . . . . . . . . 13-6 displaying status . . . . . . 1-33 checking for old files . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6. . . . . . . . X. . . . . . . System Processor (contd. . 2-46 . . . . . . . troubleshooting for modems . . . . . . . . . . . . 13-9 T Template Serial Port Manager. . . . . . . .25 . . . . . . . . . . . . . . . . . . . . . 2-42 user profiles errors . .25 . . . . . . . . . 1-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . system processes OMC software processes . . . . . . . . . . . . . . . . . . . . . . . . . 6-31 hardware failure alarm . . . . . . . . . . . . . . . Typical hardware for OMC-R system 3-4 6-37 6-24 3-23 . . . . . . 13-9 update_mib_statistics utility. . . . . synchronizing processor times sys_info files . . . . . . . . . 13-98 setup . . . . . . . . . . . . . . . 7-6. systat utility . . . . . . . . . . . . . . . . . 7-9 starting up . 7-9 single user mode . . . . . . 3-24 IX-9 . . . . . . SunLink X. . . . . . . . . . . . . . . . . . network status . . . 7-5. . . 2-15 deleting . . . . . . . . . . . 13-8 utmpx entry . . . . . . . 2-23 deleting . . . . . . . . . 1-33 user environment customising . . . . . . . . . . 4-3 OMC-R specifications SUN ULTRA ENTERPRISE 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13 user passwords . . system processes . . . . 13-14 sy