Motorola B2B Collateral Branding UK Manual Cover insert A4 Text Field Template (02/10/07)

Sign o� ........................................ date ................ Sht no 1 of 1 ag-UK-Manual Cover insert A4 Text Fields Template-00001-v02-ai-sw

Customer Documetation UK 2007

OMC-R System Administration

68P02901W19-S

Operating Information

GSR9

Using this template follow these procedures.

1. Complete all the text fields using provided spreadsheet and specification information2. Save file using appropriate naming title/convention in PDF format

© 2009 Motorola, Inc. All Rights Reserved.

Accuracy

While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes noliability resulting from any inaccuracies or omissions in this document, or from use of the information obtainedherein. 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 contenthereof with no obligation to notify any person of revisions or changes. Motorola, Inc. does not assume any liabilityarising out of the application or use of any product, software, or circuit described herein; neither does it conveylicense under its patent rights or the rights of others. It is possible that this publication may contain references to, orinformation about Motorola products (machines and programs), programming, or services that are not announcedin your country. Such references or information must not be construed to mean that Motorola intends to announcesuch Motorola products, programming, or services in your country.

Copyrights

This document, Motorola products, and 3rd Party Software products described in this document may includeor describe copyrighted Motorola and other 3rd Party supplied computer programs stored in semiconductormemories or other media. Laws in the United States and other countries preserve for Motorola, its licensors, andother 3rd Party supplied software certain exclusive rights for copyrighted material, including the exclusive rightto 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 theMotorola 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 purchaseof Motorola products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, anylicense 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 aproduct.

Restrictions

Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No partof the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, ortranslated into any language or computer language, in any form or by any means, without prior written permissionof Motorola, Inc.

License Agreements

The software described in this document is the property of Motorola, Inc and its licensors. It is furnished by expresslicense 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 NOTdesigned, manufactured, or intended for use as on-line control equipment in the following hazardous environmentsrequiring fail-safe controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft CommunicationSystems, 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 servicenames are the property of their respective owners.

The CE mark confirms Motorola, Inc. statement of compliance with EU directives applicable to this product. Copiesof the Declaration of Compliance and installation information in accordance with the requirements of EN50385 canbe 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 CustomerNetwork Resolution Center contact information. Alternatively if you do not have access to CNRC or theinternet, contact the Local Motorola Office.

Oct 2009

Tableof

Contents

Contents■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

Operating Information: OMC-R System AdministrationRevision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Version information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Resolution of Service Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Incorporation of Change Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Cross references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Contacting Motorola . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524–hour support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Questions and comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Security advice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Warnings, cautions, and notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Warnings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8General safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Electromagnetic energy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Caring for the environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9EU countries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Non-EU countries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

CMM labeling and disclosure table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Motorola document set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Ordering documents and CD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Document banner definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Data encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 1: Introduction to the OMC-ROverview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2OMC-R system configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Introduction to OMC-R system configuration . . . . . . . . . . . . . . . . . . . . . . . . 1-3Typical hardware architecture of OMC-R system . . . . . . . . . . . . . . . . . . . . . . 1-4OMC-R specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4GUI sessions and GUI server memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Factors influencing Processing Capability of GUI Servers . . . . . . . . . . . . . . . . . . 1-6Operator workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Optional processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Software requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Configuring the OMC-R SunFire and Netra system processors . . . . . . . . . . . . . . . . . 1-9

68P02901W19-S i

Oct 2009

Contents

Overview to SunFire and Netra configuration . . . . . . . . . . . . . . . . . . . . . . . . 1-9Checking SunFire hardware requirements. . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Checking Netra 20 hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . 1-10Checking Netra 440 hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . 1-10Connecting peripherals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11Connecting peripherals to a Netra 440 . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15Installing and configuring cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17Configuring hard drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18Disk configuration SunFire 4800/4900, Netra 20 and Netra 440. . . . . . . . . . . . . . . 1-19

Connecting to the LAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24Overview of connecting to the LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24Configuring the OMC-R based LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24

Routine system administration procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26Introduction to routine system administration procedures . . . . . . . . . . . . . . . . . . 1-26Daily log book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26

Daily procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28INFORMIX database daily procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28UNIX file systems daily procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29Miscellaneous daily procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29

Weekly procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30INFORMIX database weekly procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30UNIX file systems weekly procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30Security-related weekly procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31

Monthly procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32UNIX file systems monthly procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32Security-related monthly procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32

Additional procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33Additional event driven procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33Complete file system backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33NE load management maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33PM raw statistics maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33OMC-R user accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33Hard copy listings (printouts) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34System core dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34Hardware maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34

Chapter 2: System managementOverview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Overview of the Common Desktop Environment (CDE) . . . . . . . . . . . . . . . . . . . . . 2-3

Overview of the CDE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Utilities available from the root CDE desktop . . . . . . . . . . . . . . . . . . . . . . . . 2-4Utilities common to the omcadmin and root CDE desktops . . . . . . . . . . . . . . . . . 2-5Accessing usertool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Administering group accounts with usertool . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8Overview of group management functions in usertool . . . . . . . . . . . . . . . . . . . . 2-8Group Management parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9Adding a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Modifying group accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Renaming group accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Deleting group accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

Administering user accounts with usertool. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12Overview of user management functions in usertool . . . . . . . . . . . . . . . . . . . . 2-12Ensuring the correct GUI colors appear . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13User management parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13Adding a user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15Modifying a user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15Renaming a user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16

ii 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Contents

Deleting a user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16CDE utilities available to an omcadmin login. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18

Displaying the omcadmin CDE desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18Database Applications menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

CDE utilities available to either root or omcadmin login . . . . . . . . . . . . . . . . . . . . . 2-20Displaying the root CDE desktop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20Overview of utilities common to root and omcadmin . . . . . . . . . . . . . . . . . . . . . 2-21Style Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21File Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

Archiving old OMC-R user files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23Checking home accounts for unmodified files . . . . . . . . . . . . . . . . . . . . . . . . 2-23

OMC software management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24Introduction to OMC software management . . . . . . . . . . . . . . . . . . . . . . . . . 2-24Software loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24Installing new software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25Removing old software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25Test objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26

Cleaning up OMC-R software loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28Reasons for cleaning up OMC-R software loads . . . . . . . . . . . . . . . . . . . . . . . 2-28Keeping software loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28Using a tarred software load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29

NE database maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30Login id for NE database maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30Archiving and removing a NE database . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30Maintaining NE raw statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30Removing NE fallback software load directories . . . . . . . . . . . . . . . . . . . . . . . 2-31Manual parsing of statistics checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31

Printing current OMC-R processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35Overview of printing OMC-R processes . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35Procedure to print OMC-R processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35

Security overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36Overview of the OMC-R system security . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36Enabling and disabling services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38Other security changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38

Controlling user activity on the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40Login IDs for system control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40System security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41

Controlling user passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42Overview of controlling user passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42User passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42Password conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42Packet Switch passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43

Network file security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44Controlling access to network files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44Network File System (NFS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44

Installing OMC-R Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45Capacity control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46

Overview of capacity control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46Capacity control mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46Feature Capacity Licensing and Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46Licence violation alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47Updating RTF license limit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47

Restartable processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49Restartable and non-restartable processes. . . . . . . . . . . . . . . . . . . . . . . . . . 2-49Restarting processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49Messages in the OMC-R console and audit log . . . . . . . . . . . . . . . . . . . . . . . . 2-50omctool utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55

68P02901W19-S iii

Oct 2009

Contents

Graceful shutdown on mains failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57Graceful shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57Implementation of graceful shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57Features of graceful shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57UPS setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58

Configuration and installation of a remote terminal . . . . . . . . . . . . . . . . . . . . . . . 2-59Introduction to the setup of a remote monitoring terminal. . . . . . . . . . . . . . . . . . 2-59Single OMC-R monitoring configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59OMC-R night concentration centre configuration . . . . . . . . . . . . . . . . . . . . . . 2-60Night concentration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-61Naming conventions for a night concentration centre . . . . . . . . . . . . . . . . . . . . 2-61Prerequisites for setup of a night concentration centre . . . . . . . . . . . . . . . . . . . 2-61

Remote system processor setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-63Introduction to setting up night concentration . . . . . . . . . . . . . . . . . . . . . . . . 2-63Updating host file entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-63Exporting file changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64Creation of new account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64

Monitor alternative OMC-R from GUI server. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-65Prerequisites for switching to an alternative OMC-R. . . . . . . . . . . . . . . . . . . . . 2-65Switching to an alternative OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-66

Removing OMC-R night concentration centre configuration . . . . . . . . . . . . . . . . . . . 2-67Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-67Local GUI server rollback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-67Deletion of OMC-R remote user accounts . . . . . . . . . . . . . . . . . . . . . . . . . . 2-67Remote system processor rollback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-68

Setting the locale on the OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69General administration checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-74

Daily administration checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-74Weekly administration checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-79Monthly administration checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-80

Chapter 3: Ancillary DevicesOverview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Configuring the serial port with Serial Port Manager . . . . . . . . . . . . . . . . . . . . . . 3-3

Overview of Serial Port Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Accessing Serial Port Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Serial Port Manager parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Adding a modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6Setting an alternative baud rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

Installing a modem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Introduction to modem installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Background information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Data links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Rates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Physical connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Initial modem setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Communicating with the modem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10Configuring tip. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10Controlling modem access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11Modem setup and Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11Configuring the Serial Port Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12Configuring the MultiModem MT5634ZBA Global . . . . . . . . . . . . . . . . . . . . . . 3-14Enabling the login process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17Remote connection and file transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18

Troubleshooting the modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19Problem symptoms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19All ports busy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19

iv 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Contents

No login prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21When to modify the eeprom settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22Corruption from platform with remote system logging in . . . . . . . . . . . . . . . . . . 3-22Modem hangs up after answering a call and negotiation. . . . . . . . . . . . . . . . . . . 3-22Permission denied or link down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23Modems do not disconnect properly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23Nothing happens when trying to tip the modem . . . . . . . . . . . . . . . . . . . . . . . 3-23When dialing into the SPARC the modem never answers the phone . . . . . . . . . . . . . 3-23Login message is corrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24Cannot login, password fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24No utmpx entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24

Adding a printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25Overview of adding printers to the OMC-R. . . . . . . . . . . . . . . . . . . . . . . . . . 3-25Assigning printer name and address on the network. . . . . . . . . . . . . . . . . . . . . 3-25Configuring a printer connected to a GUI processor . . . . . . . . . . . . . . . . . . . . . 3-26Configuring a network printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26Checking the printer status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27Printing a file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27Printer configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27

Chapter 4: OMC-R Log FilesOverview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2OMC-R log and error files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

OMC-R log files on the system processor . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3OMC-R log files on the GUI server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5Problems with parsing statistics and maintenance of the PM database . . . . . . . . . . . 4-5Event and alarm logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5INFORMIX database log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5Interprocess communication (IPC) logging. . . . . . . . . . . . . . . . . . . . . . . . . . 4-6Environment variables for log files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6Other environment variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7Checking OMC-R log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Checking audit log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11Introduction to checking audit logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11Checking audit log files in a single OMC-R environment . . . . . . . . . . . . . . . . . . . 4-11Checking audit log files in a multiple OMC-R environment. . . . . . . . . . . . . . . . . . 4-11

Chapter 5: OMC-R Cron JobsOverview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2System cron jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

cron jobs on the system processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3cron jobs on GUI processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5Recommended cron jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Scheduling cron jobs using the batch scheduler . . . . . . . . . . . . . . . . . . . . . . . . . 5-9Overview of the batch scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9Displaying cron jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9Adding a new cron job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12Modifying an existing cron job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12Removing a cron job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

Scheduling cron jobs from the command line . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14Overview of scheduling cron jobs from the command line . . . . . . . . . . . . . . . . . . 5-14Viewing crontab files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14Verifying cron jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14Adding cron jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15Removing cron jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16cron maintenance procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16

68P02901W19-S v

Oct 2009

Contents

Printing crontab files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17Checking cron jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18

Checklist for cron jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18

Chapter 6: OMC-R Environment variablesOverview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Customizing the OMC-R user environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

Customizing a user environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3.cshrc.private file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3.Xdefaults.private file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

User configurable environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5Introduction to the user configurable environment variables . . . . . . . . . . . . . . . . 6-5System processes and PM database configurable variables . . . . . . . . . . . . . . . . . 6-5MIB processes used by environment variables . . . . . . . . . . . . . . . . . . . . . . . . 6-10GUI processes environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13RLOGIN variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21FM_audit variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22CSMMAIN variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23ResyncCtrl variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24OMC-R Startup/Shutdown Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25

Changing an environment variable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26Methods for changing an environment variable . . . . . . . . . . . . . . . . . . . . . . . 6-26

Setting the status of the Consolidated Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . 6-29Introduction to setting the status of the Consolidated Alarms . . . . . . . . . . . . . . . . 6-29Setting status of the consolidated alarms . . . . . . . . . . . . . . . . . . . . . . . . . . 6-29Disabling the status of consolidated alarms . . . . . . . . . . . . . . . . . . . . . . . . . 6-30

Non user configurable environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . 6-31Introduction to non user configurable environment variables . . . . . . . . . . . . . . . . 6-31

Setting the time for the OMC-R and NEs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36Reason for setting the system time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36Overview of setting the time at the OMC-R and NEs . . . . . . . . . . . . . . . . . . . . . 6-36Resetting the time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36Configuring system time to GMT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-37Configuring system time to local time . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-37Default time zones in OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-37Non default time zones in OMC-R without daylight saving . . . . . . . . . . . . . . . . . . 6-38Non default time zones in OMC-R with daylight saving . . . . . . . . . . . . . . . . . . . 6-39Setting the time zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-40Synchronizing the time at the OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-41Synchronizing the time at the NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-42

Chapter 7: System startup and shutdownOverview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2Operating modes (run levels) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

Operating modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Run levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Controlling run levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

System processor startup and shutdown sequences . . . . . . . . . . . . . . . . . . . . . . . 7-5Startup and shutdown scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5Directories associated with startup and shutdown . . . . . . . . . . . . . . . . . . . . . . 7-6Sequential ordering of the startup and shutdown processes . . . . . . . . . . . . . . . . . 7-7Identifying a run level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7Changing a run level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

Switching to single user mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9Switching the system processor to single user mode. . . . . . . . . . . . . . . . . . . . . 7-9Switching a GUI processor to single user mode . . . . . . . . . . . . . . . . . . . . . . . 7-9

vi 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Contents

Switching to PROM mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10The halt command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Bringing the system up from PROM mode . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11The reboot command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11

Manual startup and shutdown of OMC-R software . . . . . . . . . . . . . . . . . . . . . . . . 7-12Overview of manual startup and shutdown. . . . . . . . . . . . . . . . . . . . . . . . . . 7-12Starting up OMC-R software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12Shutting down OMC-R software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12Checking system processor processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

Chapter 8: Database ManagementOverview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2Overview of database management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

PM database maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3Database utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

Overview of the database utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4onmonitor utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5omc_db_maint utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6pm_purge_data utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7pm_daily_unload utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8pm_purge_check utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8db_disconnect utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8db_pm_maint utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9omc_db_ckspace utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10pm_manual_parse utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11

INFORMIX directory structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13Overview of the INFORMIX directory structure . . . . . . . . . . . . . . . . . . . . . . . 8-13INFORMIX directory structure on the system processor . . . . . . . . . . . . . . . . . . . 8-14INFORMIX directory structure on the GUI processor . . . . . . . . . . . . . . . . . . . . 8-15

Shutdown and startup of the PM and CM databases . . . . . . . . . . . . . . . . . . . . . . . 8-16Database shutdown and startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16Shutting down the PM database through onmonitor . . . . . . . . . . . . . . . . . . . . . 8-16Shutting down the CM database through onmonitor . . . . . . . . . . . . . . . . . . . . . 8-18Starting up the PM database through onmonitor . . . . . . . . . . . . . . . . . . . . . . 8-19Starting up the CM database through onmonitor . . . . . . . . . . . . . . . . . . . . . . 8-21Starting up databases automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22Shutting down automatically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22

Administering the PM database using the omc_db_maint utility . . . . . . . . . . . . . . . . . 8-23Using omc_db_maint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23Running omc_db_maint as a cron job . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23Running omc_db_maint manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-24Automatic Checking Of Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25

Setting the onconfig parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26onconfig file overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26Checking onconfig parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26Changing onconfig parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27

Dropping and Recreating the PM database . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30Additional database maintenance procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32

Overview of additional database maintenance procedures . . . . . . . . . . . . . . . . . . 8-32Checking for excess of 32000 statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32Checking stat details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32Backing up subscription data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32

Checking the PM database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34Check the PM database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34PM sqlhosts file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35onstat output for PM database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35onstat -d output for PM database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-37

68P02901W19-S vii

Oct 2009

Contents

Checking the CM database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39Check the CM database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39CM sqlhosts file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-40onstat output for CM database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-41onstat -d output for CM database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-42

Dropping and Recreating the CM database . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-43

Chapter 9: X.25 managementOverview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2X.25 application management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

Overview of the X.25 software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3Configuring X.25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3Configuring OMC-R processes for X.25 . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3Rules for the x25_config file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5OMC X.25 application design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5

Basic X.25 commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7Starting and stopping X.25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7Replacing the HSI card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7Updating X.25 link configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7Further details of X.25 commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7

X.25 directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8Starting and stopping X.25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9

Stopping OMC-R processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9Overview of the x25tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9Starting up the x25tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9Starting X.25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11Stopping X.25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12

Updating X.25 link configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13Configuring X.25 parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13Configuring LAPB parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15

Replacing the HSI card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17Replacing the HSI card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17

Checking X.25 connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18X.25 connectivity checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18

X.25 recovery from HSI failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19Issue A: Sun IB module/IO board hardware failure. . . . . . . . . . . . . . . . . . . . . . 9-19Issue B: HSI card hardware failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19Issue C: OMC-R configuration to allow X25 operate using the remaining hardware . . . . . 9-20

Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21Issue A: Recovery from a Sun IB module/IO board hardware failure . . . . . . . . . . . . . 9-21Issue B: Recovery from HSI card hardware failure. . . . . . . . . . . . . . . . . . . . . . 9-22Issue C: Recovery of OMC-R configuration to allow X25 operate using the remaininghardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-23

Chapter 10: OMC UtilitiesOperation and maintenance utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Overview of utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2Operation and maintenance utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2Alarm/Event Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4Rollback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7Utility execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7Finder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8net_reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9dri_status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13

viii 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Contents

rtf_status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15site_outage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16add_nei . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18del_nei . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19nei_sync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20proxy_sync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21reparent_site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21ne_counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-23

Utility execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-25Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-25Command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-25cron and at. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26CDE menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26

cleanMib . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-27Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-27Running cleanMib . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-27

Chapter 11: Network Information Services (NIS)Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2NIS normal operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3

Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3Servers and clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3Masters and slaves. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4

NIS files and utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5Daemons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6Auxiliary utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6Affected files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7

Changing user/group/host information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8Recommended method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8Changing host name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8Adding a new user to the NIS domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8Adding a new group to the NIS domain . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9nsswitch.conf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10NIS server checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10Updating the NIS maps manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11NIS troubleshooting commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11

Chapter 12: Backup Server Installation and ConfigurationIntroduction to StorEdge Enterprise Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2

StorEdge Enterprise features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4

Invoking the StorEdge Enterprise Backup utilities . . . . . . . . . . . . . . . . . . . . . . 12-4Software Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4Backup Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5Configuring Sun StorEdge Enterprise Backup Server Licenses . . . . . . . . . . . . . . . 12-5Configuring Bootstrap Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6Configuring Bootstrap Notification through E-mail . . . . . . . . . . . . . . . . . . . . . 12-6Configuring Bootstrap Notification to local file . . . . . . . . . . . . . . . . . . . . . . . 12-7Setting up the backup server software . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9Completing backup server setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10Enabling or Disabling a Group Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10Deleting a Group Backup client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11Manually starting a Group Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12

68P02901W19-S ix

Oct 2009

Contents

Manual backup of Informix databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13Backing up the GUI Server File System . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16

Disaster Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-20Disaster Recovery GSM OMC-R server. . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-20Recover the Necessary Filesystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-27Recovering Informix databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-31

Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-35Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-35Database recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-37

Additional Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-39StorEdge Enterprise Backup Server GUI . . . . . . . . . . . . . . . . . . . . . . . . . . 12-39Licensing the Sun StorEdge EBS Server using the Administration Window . . . . . . . . . 12-40Tape Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-41

Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-43Installation log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-43Sample output from backup client creation . . . . . . . . . . . . . . . . . . . . . . . . . 12-43Backup and Restore using the Standard Solaris suite of utilities. . . . . . . . . . . . . . . 12-48Backing up the PM and CM Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-55Restoring Single Platform Processor file systems . . . . . . . . . . . . . . . . . . . . . . 12-63Restoring databases on the Single Platform Processor. . . . . . . . . . . . . . . . . . . . 12-77Restoring GUI Server file systems using ufsrestore utility . . . . . . . . . . . . . . . . . . 12-86Selective File restore using restore_splat . . . . . . . . . . . . . . . . . . . . . . . . . . 12-97

Chapter 13: TroubleshootingOverview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2Assessing a problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3

Overview of troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3Contacting Motorola . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3Preliminary checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3General problem descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5

Core file generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6Overview of generating core files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6Application core dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6Generating a core of an OMC-R process . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6Operating system core dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6core_presence utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6Checking core dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7

OMC-R system information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8Obtaining system information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8OMC-R log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8System uptime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8Machine architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9Current processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9State of the file systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10Integrity of X.25 communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10Network status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-11System resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12Swap space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-14PM database status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-14CM database status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-17systat script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-19

Full file systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-21Full file systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-21Identifying full file systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-21Freeing up further disk space on the system processor . . . . . . . . . . . . . . . . . . . 13-21Removing files or directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-22Checking disk usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-23

x 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Contents

File access problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-24Stale NFS file handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-24GUI processor failure to access event log files . . . . . . . . . . . . . . . . . . . . . . . . 13-24

OMC-R software process errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-25Analyzing OMC-R process errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-25List of system processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-26GUI process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-27

Resetting boot devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-28Bootup problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-28Procedure to reset a boot device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-28

Common Desktop Environment problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-33Overview of CDE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-33Installing CDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-33Configuring CDE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-33Normal operation of CDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-34Errors in user profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-34Errors accessing a user's home directory . . . . . . . . . . . . . . . . . . . . . . . . . . 13-34Enabling/disabling the Print Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-34Other CDE problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-35

CDE login failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-36Overview of CDE login failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-36Procedure to recover from CDE login failure. . . . . . . . . . . . . . . . . . . . . . . . . 13-36

Troubleshooting the LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-37Long response times to commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-37Checking the performance of the LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-37Checking if packets can be sent and received . . . . . . . . . . . . . . . . . . . . . . . . 13-38

X.25 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-39Overview of X.25 failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-39Starting x25tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-39X.25 trace on the system processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-39Displaying x25stat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-40

Moving a machine with a forced link speed . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-41Logical Vol Mgr troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-42

Logical Vol Mgr problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-42Replacing hard disk on system processor Sunfire/Netra 440/Netra 20 . . . . . . . . . . . . . . 13-43Recovering from other Logical Vol Mgr problems . . . . . . . . . . . . . . . . . . . . . . 13-46

Checking disk mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-47Disk mirroring checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-47metastat output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-47

Device busy error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-49Device busy error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-49Unmounting a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-49

Ejecting DVD-ROMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-50DVD-ROM drive not ejecting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-50Procedure to free up DVD-ROM drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-50

StorEdge Enterprise Backup problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-51StorEdge Enterprise Backup tape error . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-51

Database failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-52Database failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-52Problems adding/updating statistics in PM database. . . . . . . . . . . . . . . . . . . . . 13-52

Onperf utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-53Overview of Onperf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-53Starting onperf from the CDE front panel . . . . . . . . . . . . . . . . . . . . . . . . . . 13-53Starting onperf from the command line . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-54Loading a history file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-54Saving Graph Tool configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-57Selecting metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-58Viewing metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-59

68P02901W19-S xi

Oct 2009

Contents

Monitoring tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-64Activity tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-66

Checking and recovering database tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-70Monitoring database space usage and fragmentation . . . . . . . . . . . . . . . . . . . . 13-70Reading the database schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-73Defragmenting tables (MIB database) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-73Emptying and defragmenting one or more PM statistics tables . . . . . . . . . . . . . . . 13-74Adding extra logical logs to the PM database server . . . . . . . . . . . . . . . . . . . . . 13-76

Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-78Overview of alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-78Disk space usage on the system processor . . . . . . . . . . . . . . . . . . . . . . . . . . 13-79CPU and memory usage alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-80Database alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-83X.25 alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-85Hardware failure alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-86OMC-R alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-86

Setting FM audit and disk usage limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-88Overview of setting FM audit and disk usage limits . . . . . . . . . . . . . . . . . . . . . 13-88FM_audit.CNFG parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-88

Using neighbor statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-91Neighbor statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-91Limitations on use of neighbor statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-91Cyclic Neighbor Statistics feature (PMCyclic) . . . . . . . . . . . . . . . . . . . . . . . . 13-91Neighbor statistics alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-93Raising the maximum limit of neighbor statistics . . . . . . . . . . . . . . . . . . . . . . 13-94Using dbaccess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-96

Power failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-97Overview of recovery from power failure . . . . . . . . . . . . . . . . . . . . . . . . . . 13-97Power failure on all machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-97Power failure on the system processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-98Power failure on a GUI processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-98

Checking the system processor hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-99System processor hardware LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-99Displaying system processor status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-99

Configuring a Timeserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-102Support for IP Multipathing in Solaris10/GSR9 on Sunfire platforms . . . . . . . . . . . . . . 13-103

Chapter 14: ChecklistsOverview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2General administration checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3

Daily administration checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3Weekly administration checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-5Monthly administration checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6

Checking cron jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7Checking OMC-R log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-8Checking databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-10

Checklist for PM database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-10Checklist for CM database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-12

Checking X.25 connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-14Checking core dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-15Checking disk usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-16Checking disk mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-17Checking for successful parsing of statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-18Recording details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-20

Setting up a night concentration centre . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-20Client and server partition details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-21

xii 68P02901W19-S

Oct 2009

Listof

Figures

List of Figures■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

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

68P02901W19-S xiii

Oct 2009

List of Figures

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

xiv 68P02901W19-S

Oct 2009

Listof

Tables

List of Tables■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

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

68P02901W19-S xv

Oct 2009

List of Tables

Table 14-11: Disk mirroring checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-17Table 14-12: Manual parsing of statistics checklist . . . . . . . . . . . . . . . . . . . . . . . 14-18Table 14-13: Hostname and IP addresses for different processors . . . . . . . . . . . . . . . . 14-20Table 14-14: User name and ID for remote system. . . . . . . . . . . . . . . . . . . . . . . . 14-20Table 14-15: Client and server details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-21Table 14-16: Filesystem, Log and JumpStart details . . . . . . . . . . . . . . . . . . . . . . . 14-21

xvi 68P02901W19-S

Oct 2009

AboutThisManual

Operating Information: OMC-R SystemAdministration

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

What is covered in this manual?

This manual provides the OMC-R system administrator with the technical information andprocedures to administer an OMC-R on a daily basis. Throughout this manual, the term OMCrefers to OMC-R (Operation and Maintenance Centre-Radio).

Some of the screen illustrations in this manual are shown with NT Windows characteristicsinstead of UNIX window characteristics. However, functionality is not affected, and all otherdetails in the screen illustrations are correct.

This manual describes procedures for managing the system, the users, the database, X.25, NISand 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 1

Oct 2009

Revision history

Revision history■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The following sections show the revision status of this document.

Version information

The following table lists the supported versions of this manual in order of issue:

Issue Date of issue Remarks

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:

Service Request CMBP Number Remarks

SR 2211808 N/A Added a note under the section Securityoverview.

SR 2241385 N/A Added a new environment variable under thesection User configurable environmentvariables.

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:

CN Date CN Number Title

N/A N/A N/A

2 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 allpersonnel engaged in such activities be properly trained by Motorola.

Motorola disclaims all liability whatsoever, implied or expressed, for any risk of damage, loss orreduction 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 byMotorola. They can be used to supplement and enhance the knowledge gained through suchtraining.

NOTEIf this document was obtained when attending a Motorola training course, it is notupdated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If itwas supplied under normal operational circumstances, to support a major softwarerelease, then Motorola automatically supplies corrections and posts on the Motorolacustomer 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 arenot numbered, but are individually named at the top of each page, and are listed in the table ofcontents.

68P02901W19-S 3

Oct 2009

Text conventions

Text conventions

The following conventions are used in the Motorola documents to represent keyboard inputtext, screen output text, and special key sequences.

Input

Characters typed in at the keyboard are shown like this sentence.Items of interest within a command appear like this sentence.

Output

Messages, prompts, file listings, directories, utilities, and environmental

variables that appear on the screen are shown like this sentence.

Items of interest within a screen display appear like this sentence.

Special key sequences

Special key sequences are represented as follows:

CTRL-c or CTRL+C Press the Ctrl and C keys at the same time.

CTRL-SHIFT-c orCTRL+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.

4 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 NetworkResolution Center (CNRC) for immediate assistance. The 24–hour telephone numbers are listedat https://mynetworksupport.motorola.com. Select Customer Network Resolution Centercontact information. Alternatively if you do not have access to CNRC or the internet, contactthe 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) andprovide 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 5

Oct 2009

Security advice

Security advice■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Motorola systems and equipment provide security parameters that the operator configuresbased on their particular operating environment. Motorola recommends setting and usingthese parameters following industry recognized security practices. Consider protecting theconfidentiality, integrity, and availability of information and assets. Assets include the abilityto communicate, information about the nature of the communications, and information aboutthe parties involved.

In certain instances, Motorola makes specific recommendations regarding security practices.The implementation of these recommendations and final responsibility for the security of thesystem lies with the operator of the system.

Contact the Customer Network Resolution Center (CNRC) for assistance. The 24–hourtelephone numbers are listed at https://mynetworksupport.motorola.com. Select CustomerNetwork Resolution Center contact information, from the menu located to the left of theLogin box. Alternatively if you do not have access to CNRC or the internet, contact the LocalMotorola 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 alldocuments of this Motorola document set.

Warnings

Warnings precede instructions that contain potentially hazardous situations. Warnings areused to alert the reader to possible hazards that could cause loss of life or physical injury. Awarning has the following format:

WARNINGWarning 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 presentsno danger to personnel. A caution has the following format:

CAUTIONCaution 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 additionalinformation to help the reader understand a topic or concept. A note has the following format:

NOTENote text.

68P02901W19-S 7

Oct 2009

Safety

Safety■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

General safety

The following general safety guidelines apply to Motorola equipment:

• The power jack and mating plug of the power cable must meet InternationalElectrotechnical Commission (IEC) safety standards.

NOTERefer to Grounding Guideline for Cellular Radio Installations – 68P81150E62.

• Power down or unplug the equipment before servicing.

• Using non-Motorola parts for repair could damage the equipment or void warranty.Contact Motorola Warranty and Repair for service and repair instructions.

• Portions of Motorola equipment may be damaged from exposure to electrostatic discharge.Use precautions to prevent damage.

Electromagnetic energy

Relevant standards (USA and EC) applicable when working with RF equipment are:

• ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposureto Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.

• Council recommendation of 12 July 1999 on the limitation of exposure of the generalpublic to electromagnetic fields (0 Hz to 300 GHz) (1999/519/EC) and respective nationalregulations.

• Directive 2004/40/EC of the European Parliament and of the Council of 29 April 2004 onthe minimum health and safety requirements regarding the exposure of workers to therisks arising from physical agents (electromagnetic fields) (18th individual Directive withinthe meaning of Article 16(1) of Directive 89/391/EEC).

8 68P02901W19-S

Oct 2009

Caring for the environment

Caring for the environment■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The following information describes national or regional requirements for the disposal ofMotorola supplied equipment and for the approved disposal of surplus packaging.

Contact the Customer Network Resolution Center (CNRC) for assistance. The 24–hourtelephone numbers are listed at https://mynetworksupport.motorola.com. Select CustomerNetwork Resolution Center contact information. Alternatively if you do not have accessto CNRC or the internet, contact the Local Motorola Office.

EU countries

The following information is provided to enable regulatory compliance with the EuropeanUnion (EU) directives and any amendments to these directives when using Motorola equipmentin 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 conjunctionwith a recycling partner ensures that equipment is collected and recycled according to therequirements 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’sresponsibility to ensure that packaging materials are collected and recycled according to therequirements of EU environmental law.

Non-EU countries

In non-EU countries, dispose of Motorola equipment and all surplus packaging in accordancewith national and regional regulations.

68P02901W19-S 9

Oct 2009

Non-EU countries

Turkey

Article 7 of the European Union (EU) Directive 2002/96/EC Waste Electrical and ElectronicEquipment (WEEE)

The Government of Turkey requests a statement of conformity with the EEE regulation beprovided with all electrical and electronic equipment. This statement of EEE conformity (inTurkish) is: EEE Yönetmeliğine Uygundur.

10 68P02901W19-S

Oct 2009

CMM labeling and disclosure table

CMM labeling and disclosure table■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The People’s Republic of China requires that our products comply with China ManagementMethods (CMM) environmental regulations. (China Management Methods refers to theregulation Management Methods for Controlling Pollution by Electronic Information Products.)Two items are used to demonstrate compliance; the label and the disclosure table.

The label is placed in a customer visible position on the product.

• Logo 1 means the product contains no substances in excess of the maximum concentrationvalue for materials identified in the China Management Methods regulation.

• Logo 2 means that the product may contain substances in excess of the maximumconcentration value for materials identified in the China Management Methods regulation,and has an Environmental Friendly Use Period (EFUP) in years. The example shownuses 50 years.

Logo 1 Logo 2

The Environmental Friendly Use Period (EFUP) is the period (in years) during which the Toxicand 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 theEIP. The EFUP indicated by the Logo 2 label applies to a product and all its parts. Certainfield-replaceable parts, such as battery modules, can have a different EFUP and are markedseparately.

The Disclosure table is intended only to communicate compliance with China requirements.It is not intended to communicate compliance with EU RoHS or any other environmentalrequirements.

68P02901W19-S 11

Oct 2009

Motorola document set

Motorola document set■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The Motorola document sets provide the information to operate, install, and maintain theMotorola equipment.

Ordering documents and CD-ROMs

With internet access available, to view, download, or order documents (original or revised), visitthe Motorola Lifecycles Customer web page at https://mynetworksupport.motorola.com, orcontact your Motorola account representative.

Without internet access available, order hard-copy documents or CD-ROMs from your MotorolaLocal Office or Representative.

If Motorola changes the content of a document after the original printing date, Motorolapublishes a new version with the same part number but a different revision character.

Document banner definitions

A banner indicates that some information contained in the document is not yet approved forgeneral customer use. A banner is oversized text on the bottom of the page, for example,PRELIMINARY — UNDER DEVELOPMENT.

Data encryption

In order to avoid electronic eavesdropping, data passing between certain elements in thenetwork is encrypted. In order to comply with the export and import requirements of particularcountries, this encryption occurs at different levels. The encryption may be individuallystandardized or may not be present at all in some parts of the network in which it is normallyimplemented. The document set covers encryption as if fully implemented. Limitations on theencryption included in the particular software being delivered, are covered in the Release Notesthat accompany the individual software release.

12 68P02901W19-S

Oct 2009

Chapter

1

Introduction to the OMC-R■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

68P02901W19-S 1-1

Oct 2009

Overview Chapter 1: Introduction to the OMC-R

Overview■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This chapter provides an overview of the OMC-R hardware configuration for SunFire 4800/4900,Netra 20, Netra 440, and {34618} M4000 and M5000 based systems, and identifies the OMC-Rhardware and software components provided for each system.

Overviews of the daily, weekly and monthly procedures are also included, as well as otherroutine procedures that must be performed by the OMC-R system administrator.

NOTEFor detailed information regarding OMC-R hardware and software installation, referto Installation and Configuration: OMC-R Clean Install (68P02901W47).

The following topics are described in this chapter:

• OMC-R system configuration on page 1-3.

• Configuring the OMC-R SunFire and Netra system processors on page 1-9.

• Connecting to the LAN on page 1-24.

• Routine system administration procedures on page 1-26.

• Daily procedures on page 1-28.

• Weekly procedures on page 1-30.

• Monthly procedures on page 1-32.

• Additional procedures on page 1-33.

NOTEThroughout this manual, $OMC_TOP is used to describe the top level directorystructure /usr/omc.

1-2 68P02901W19-S

Oct 2009

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, SunFire 4800/4900,Netra 20, Netra 440).

• A Graphical User Interface (GUI) Server (for example, Sunblade 150).

• Several GUI client processors which provide operator workstations.

• A laser printer, suitable for LAN connection (for example, Lexmark Optra S1650).

Each processor is a complete UNIX system. An Ethernet Local Area Network (LAN) enablesinteraction between all processors.

The OMC-R interfaces with the cellular network through the use of X.25 Packet Switchedprotocol.

Typical hardware architecture of Motorola OMC-R, with optional equipment, is shown inFigure 1-1.

68P02901W19-S 1-3

Oct 2009

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.

Figure 1-1 Typical hardware architecture of OMC-R SunFire/Netra system

OMC-R specifications

The SunFire 4800/4900, Netra 20, or Netra 440 is a UNIX system that acts as the OMC-Rsystem processor, running the OMC-R application software which handles all Operation andMaintenance communication with the Network Elements (NEs). A Packet Switch/Multiplexerand the system processor HSI/P hardware enable the OMC-R to interface with the GSM network.The OMC-R system processor processes all incoming events, alarms, uploads, downloads,performance statistics, and the setting up of remote login sessions to different NEs.

The OMC-R system processor contains two databases constructed on an INFORMIX RelationalDatabase Management System model (RDBMS). One database (PM) is configured for storingperformance statistics and subscription lists, the other (CM) is configured for network and mapconfiguration data which enables operators to monitor incoming events and alarms through theuse of map displays.

The OMC-R system processor uses the Solaris 10 Operating System (OS) as the UNIX platform.

In addition to the OMC-R system processor, Graphical User Interface (GUI) Servers and Clientsbased on SUN ULTRASparc processors can be used as operator workstations to manage andmonitor NE's.

1-4 68P02901W19-S

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.

OMC-R specifications are shown in Table 1-1.

Table 1-1 OMC-R specifications (maximum values)

Feature Netra 20/Netra 440 Sunfire

Total GUI sessions supported 30 60

Remote login sessions 30 90

Simultaneous downloads 12 36

Simultaneous uploads 32 64

Sustained event rate 12 alarms +3 state changes

16 alarms +4 state changes

Maximum event burstover 20 minutes

32 alarms +8 state changes

64 alarms +16 state changes

GUI sessions and GUI server memory

In Table 1-1, the maximum number of GUI sessions supported is 60 for a Sunfire and 30 forother Single Platform systems. However, this is based on the assumption that the appropriatenumber of GUI servers and memory are in use.

For GUI Servers, the memory, and CPU speed of the GUI server are used to determine thenumber of permitted GUI sessions.

The following formula gives the number of permitted GUI sessions. This formula has beenimplemented in the corecheck_gui script. The corecheck_gui script is used to start GUI sessions.

Maximums_GUIs = (Memory X CPU speed) / 39060) + 1

Where is

Memory the GUI server memory

CPU Speed the CPU clock speed of theGUI server

Where:

Table 1-2 details the number of GUI sessions each GUI server configuration is capable ofsupporting.

68P02901W19-S 1-5

Oct 2009

Factors influencing Processing Capability of GUI Servers Chapter 1: Introduction to the OMC-R

Table 1-2 GUI sessions per GUI server platform

Platform/Memory (MB) CPU(MHz) Sunblade 150

256 270 -

256 360 -

256 400 -

512 270 -

512 360 -

512 400 -

1024 650 12

Factors influencing Processing Capability of GUI Servers

Test results have indicated that there are five main factors limiting the number of GUIs ona GUI server. They are as follows:

• Real memory or the physical Random Access Memory (RAM) available within the platform.

• CPU speed.

• CPU class, including cache.

• Disk access speed.

• Link capacity of the Local Area Network.

Other factors affecting the performance of the GUI Server are:

• Number of FM operators (Open GUIs / MMI Windows).

• Number of events arriving per second.

Operator workstations

The OMC-R system comprises of a single platform system processor and a number of operatorworkstations. Each operator workstation is a complete UNIX system and runs the OMC-RGraphical User Interface (GUI).

1-6 68P02901W19-S

Oct 2009

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.

Optional processors

Optional processors can be added to the basic OMC-R configuration:

• OSI (Open Systems Interconnect) processor

• Datagen

• Network Health Analyst (NHA)

Software requirements

GSM OMC-R GSR9 DVD 1.9.0.0.x contains the software requirements for all other OMC-Rplatforms.

NOTEIf an NHA processor is connected to the OMC-R, then retain the NIS as the namingservice for the OMC-R LAN.

68P02901W19-S 1-7

Oct 2009

Software requirements Chapter 1: Introduction to the OMC-R

Table 1-3 Software requirements (Single Platform Processor)

Title Revision version Media Number ofvolumes

Licence keyrequired

GSR9 DVD 1900.x DVD 1 —

Sun Solaris 10 — — —

Solaris LogicalVolume Manager

11.9 — — —

Sun SunLink X25 9.2 — — Yes

TCL 8.4.6 — — —

TK 8.4.6 — — —

Enscript 1.6.1 — — —

EPAK 3.0.7 — — —

zlib 1.2.1 — — —

Perl 5.61 — — —

FlexNet 10 — — —

INFORMIX-IDS 10.00.UC8 — — —

INFORMIX-ClientSDK

2.81 — — —

INFORMIX-ISQL 7.32 — — —

OSP 5.3 — — —

ApplixSpreadsheet

6 — — —

Applix Data 6 — — —

Mozilla 1.7 — — —

Python 2.2.3 — — —

Sun VTS 6.2 — — —

StorEdgeEnterpriseBackup Server

7.3 — — —

StorEdgeEnterpriseBackup Client

7.3 — — —

RTF licence — — — Yes

1-8 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Configuring the OMC-R SunFire and Netra system processors

Configuring the OMC-R SunFire and Netra systemprocessors

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Overview to SunFire and Netra configuration

Perform the following operations to configure the OMC-R SunFire 4800/4900 orNetra 20/Netra 440 system processor:

• Checking hardware requirements.

• Connecting peripherals.

• Installing and configuring cards.

• Configuring hard drives.

• Checking disk configuration.

NOTEConfiguration is initially performed by Motorola. Refer to Installation andConfiguration: OMC-R Clean Install (68P02901W47) for further details.

Checking SunFire hardware requirements

Typical requirements for an OMC-R SunFire 4800/4900 platform are detailed in Table 1-4.

Table 1-4 SunFire 4800/4900 hardware requirements

Equipment Quantity Description

OMC-R platform 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

Checking Netra 20 hardware requirements Chapter 1: Introduction to the OMC-R

Table 1-4 SunFire 4800/4900 hardware requirements (Continued)

Equipment Quantity Description

DAT drive 1 4MM DDS4

SCSI/Ethernet combo(Sun Swift)

2

Dual port SCSI 160 HBALVD (Jasper)

2

Serial I/O 3 4 port Synch

1 X 3310 JBOD SCSI 160LVD disk array

12 73 GB drives

System and Disk Array 1 All ac power

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 Quantity Description

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 HBALVD (Jasper)

2

Serial I/O 2 4 port Synch

1 X 3310 JBOD SCSI 160LVD disk array

12 73 GB drives

System and Disk Array 1 All ac power

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 Quantity Description

OMC-R platform 1 Netra 440 (includingtwo CPUs)

Continued

1-10 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Connecting peripherals

Table 1-6 Netra 440 hardware requirements (Continued)

Equipment Quantity Description

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 HBALVD (Jasper320)

2

Serial I/O 2 4 port Synch

1 X 3310 JBOD SCSI 160LVD disk array

12 73 GB drive

System and Disk Array 1 All ac power

QGE (Quad 1000 MbitEthernet)

1

External Tape Drive

Connecting peripherals

Connecting peripherals to a SunFire 4800/4900

Figure 1-4 illustrates the peripheral connections to a SunFire 4800/4900. Once the SunFire4800/4900, D240 media tray (Figure 1-3) and StorEdge 3310 Disk Array (Figure 1-2) havebeen mounted, cables need to be attached.

Refer Figure 1-2, Figure 1-3, and Figure 1-4, and ensure that the configuration switch on theD240 is in the split bus position.

Figure 1-2 StorEdge 3310 Disk Array

68P02901W19-S 1-11

Oct 2009

Connecting peripherals Chapter 1: Introduction to the OMC-R

Figure 1-3 D240 Media Tray

Figure 1-4 Connecting peripherals on a SunFire 4800/4900

1-12 68P02901W19-S

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.

2 Connect a cable from UltraSCSI card 1 to lower port A of the 3310.

3 Connect a cable from SCSI+Ethernet card 0 to the top right connectorof the D240.

4 Connect a cable from SCSI+Ethernet card 1 to the top left connectorof the D240.

5 Connect Ethernet cables to SCSI+Ethernet card 0 and both SC0 andSC1.

6 If a Sun rack is used, connect a serial port splitter cable to SC0 serialand connect ttyb to the frame manager.

Connecting peripherals to a Netra 20

Figure 1-5 illustrates the peripheral connections to a Netra 20. Once the Netra 20 and StorEdge3310 Disk Array (Figure 1-6) are mounted, attach the two SCSI cables as follows:

Figure 1-5 Connecting peripherals on a Netra 20

68P02901W19-S 1-13

Oct 2009

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 Connecting the SCSI cables to a Netra 20

1 Ensure that the cable from UltraSCSI 0 on the Netra goes to the lowerslot B on the disk array and the cable from UltraSCSI 1 on the Netragoes to the lower slot A on the disk array. When powered up, bothTERM lights on the array should be lit.

2 Ensure that the terminal connected to the Serial Port console remainsconnected for the duration of the installation.

1-14 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 Connecting Peripherals on a Netra 440

68P02901W19-S 1-15

Oct 2009

Connecting peripherals to a Netra 440 Chapter 1: Introduction to the OMC-R

Figure 1-8 Netra 440 connected to StorEdge 3310 Array

Use the following procedure to attach the two SCSI cables to a Netra 440:

Procedure 1-3 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.

2 Connect the top most port (Port 1) of the Ultra SCSI card in PCI 2 to thebottom right-most SCSI port (A) of the StorEdge 3310.

3 Connect the top-most port (Port 1) of the Ultra SCSI card in PCI 4 to thebottom left-most SCSI port (B) of the StorEdge 3310. When powered up,both TERM lights on the array should be lit.

1-16 68P02901W19-S

Oct 2009

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, asdescribed in the Sun Hardware Guide.

2 Connect the HSI cards to the external X.25 network equipment usingthe cables provided.

Card configuration

Table 1-7 specifies the location of the cards for a SunFire 4800/4900.

Table 1-7 Location of cards for a SunFire

Board Slot Card description

Slot 1 HSI 1

Slot 4 UltraSCSI 1

Slot 5 SCSI + Ethernet 1

IB8

Slot 6 HSI 2

Slot 1 HSI 0

Slot 4 UltraSCSI 0

IB6

Slot 5 SCSI + Ethernet

Table 1-8 specifies the location of the cards for a Netra 20.

Table 1-8 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

68P02901W19-S 1-17

Oct 2009

Configuring hard drives Chapter 1: Introduction to the OMC-R

Table 1-9 specifies the location of the cards for a Netra 440.

Table 1-9 Location of cards for a Netra 440

Slot Card description

Slot 0 HSI 0

Slot 1 HSI 1

Slot 2 UltraSCSI 0

Slot 4 UltraSCSI 1

Configuring hard drives

Table 1-10 specifies the internal configuration of hard drives in the Netra 20.

Table 1-10 Internal configuration of hard drives in the Netra 20/440

Slot location Disk name Disk sizes allowed

Slot 0 c2t0d0 73 GB

Slot 1 c2t1d0 73 GB

Figure 1-9 illustrates the internal disk slots in the Netra 20/440.

Figure 1-9 Netra 20/440 internal disk slots

1-18 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Disk configuration SunFire 4800/4900, Netra 20 and Netra 440

Disk configuration SunFire 4800/4900, Netra 20 and Netra 440

The single platform processor controls either twelve 73 GB disks or {34618} 146 GB disks.Table 1-11 and Table 1-12 are based on 146 GB disks. The disks are shipped from Sun witha default partition configuration. The logical disk partitions critical for the boot processare amended during the Solaris operating system installation. The JumpStart procedureincorporates Solaris Logical Volume Manager to set up the metadevices. For these servers, themetadevice numbers are generated dynamically.

Table 1-11 highlights the partitioning details used for the SunFire 4800/4900 and Netra 20servers.

Table 1-12 highlights the partitioning details used for the Netra 440 servers.

Table 1-11 Disk partitioning for SunFire 4800/4900 and Netra 20 servers

FileSystem SF Size Netra

SizeSub Mirror 0

StripeSub Mirror 1

StripeMirrorDisk

Sub Mirror0

SubMirror 1

SoftPartition

/ 17 GB 17 GB c1t8d0s0 c3t8d0s0 d0 d1 d2 none

Swap 9.6 GB 9.6 GB c1t8d0s1 c3t8d0s1 d5 d6 d7 none

/var 41 GB 41 GB c1t8d0s3 c3t8d0s3 d10 d11 d12 none

/opt 34 GB 34 GB c1t8d0s4 c3t8d0s4 d15 d16 d17 none

/usr 27 GB 27 GB c1t8d0s5 c3t8d0s5 d20 d21 d22 none

/omcgen 6.8 GB 6.8 GB primary_disk* mirror_disk* d25 d26 d27 d30

/home 10 GB 10 GB primary_disk mirror_disk d25 d26 d27 d35

/usr/omc 5.9 GB 5.9 GB primary_disk mirror_disk d25 d26 d27 d40

/usr/omc/ne_data

16 GB 16 GB primary_disk mirror_disk d25 d26 d27 d50

/usr/omc/ne_data/raw_stats

12 GB 12 GB primary_disk mirror_disk d25 d26 d27 d55

solbak 7.8 GB 7.8 GB primary_disk mirror_disk d25 d26 d27 d60

omc_db_root

2.0 GB 2.0 GB primary_disk mirror_disk d25 d26 d27 d85

omc_db1 13 GB 11 GB primary_disk mirror_disk d25 d26 d27 d90

omc_db2 13 GB 11 GB primary_disk mirror_disk d25 d26 d27 d95

omc_db3 13 GB 11 GB primary_disk mirror_disk d25 d26 d27 d100

omc_db4 13 GB 11 GB primary_disk mirror_disk d25 d26 d27 d105

omc_db5 13 GB 11 GB primary_disk mirror_disk d25 d26 d27 d110

omc_db6 13 GB 11 GB primary_disk mirror_disk d25 d26 d27 d115

omc_db7 13 GB 11 GB preliminaries mirror_disk d25 d26 d27 d120

omc_db8 13 GB 11 GB primary_disk mirror_disk d25 d26 d27 d125

omc_db9 13 GB 11 GB primary_disk mirror_disk d25 d26 d27 d130

Continued

68P02901W19-S 1-19

Oct 2009

Disk configuration SunFire 4800/4900, Netra 20 and Netra 440 Chapter 1: Introduction to the OMC-R

Table 1-11 Disk partitioning for SunFire 4800/4900 and Netra 20 servers (Continued)

FileSystem SF Size Netra

SizeSub Mirror 0

StripeSub Mirror 1

StripeMirrorDisk

Sub Mirror0

SubMirror 1

SoftPartition

omc_db10 13 GB 11 GB primary_disk mirror_disk d25 d26 d27 d135

omc_db11 13 GB 11 GB primary_disk mirror_disk d25 d26 d27 d140

omc_db12 13 GB 11 GB primary_disk mirror_disk d25 d26 d27 d145

omc_db_temp

2.0 GB 2.0 GB primary_disk mirror_disk d25 d26 d27 d155

omc_db_logs

2.0 GB 2.0 GB primary_disk mirror_disk d25 d26 d27 d150

mib_db 2.0 GB 2.0 GB primary_disk mirror_disk d25 d26 d27 d170

mib_db1 2.0 GB 2.0 GB primary_disk mirror_disk d25 d26 d27 d160

mib_db2 2.0 GB 2.0 GB primary_disk mirror_disk d25 d26 d27 d165

mib_db_logs

2.0 GB 2.0 GB primary_disk mirror_disk d25 d26 d27 d175

NOTE

• *primary_disk: c1t9d0s0 c1t10d0s0 c1t11d0s0 c1t12d0s0 c1t13d0s0

• *mirror_disk: c3t9d0s0 c3t10d0s0 c3t11d0s0 c3t12d0s0 c3t13d0s0

Table 1-12 Disk partitioning for Netra 440 servers

FileSystem Size Sub Mirror 0

StripeSub Mirror 1

StripeMirrorDisk

SubMirror 0

SubMirror 1

SoftPartition

/ 17 GB c0t8d0s0 c1t8d0s0 d0 d1 d2 none

Swap 9.6 GB c1t8d0s1 c3t8d0s1 d5 d6 d7 none

/var 41 GB c0t8d0s3 c1t8d0s3 d10 d11 d12 none

/opt 34 GB c0t8d0s4 c1t8d0s4 d15 d16 d17 none

/usr 27 GB c0t8d0s5 c1t8d0s5 d20 d21 d22 none

/omcgen 6.8 GB primary_disk* mirror_disk* d25 d26 d27 d30

/home 10 GB primary_disk mirror_disk d25 d26 d27 d35

/usr/omc 5.9 GB primary_disk mirror_disk d25 d26 d27 d40

/usr/omc/ne_data

16 GB primary_disk mirror_disk d25 d26 d27 d50

/usr/omc/ne_data/raw_stats

12 GB primary_disk mirror_disk d25 d26 d27 d55

Continued

1-20 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Disk configuration SunFire 4800/4900, Netra 20 and Netra 440

Table 1-12 Disk partitioning for Netra 440 servers (Continued)

FileSystem Size Sub Mirror 0

StripeSub Mirror 1

StripeMirrorDisk

SubMirror 0

SubMirror 1

SoftPartition

solbak 7.8 GB primary_disk mirror_disk d25 d26 d27 d60

omc_db_root

2.0 GB primary_disk mirror_disk d25 d26 d27 d85

omc_db1 11 GB primary_disk mirror_disk d25 d26 d27 d90

omc_db2 11 GB primary_disk mirror_disk d25 d26 d27 d95

omc_db3 11 GB primary_disk mirror_disk d25 d26 d27 d100

omc_db4 11 GB primary_disk mirror_disk d25 d26 d27 d105

omc_db5 11 GB primary_disk mirror_disk d25 d26 d27 d110

omc_db6 11 GB primary_disk mirror_disk d25 d26 d27 d115

omc_db7 11 GB primary_disk mirror_disk d25 d26 d27 d120

omc_db8 11 GB primary_disk mirror_disk d25 d26 d27 d125

omc_db9 11 GB primary_disk mirror_disk d25 d26 d27 d130

omc_db10 11 GB primary_disk mirror_disk d25 d26 d27 d135

omc_db11 11 GB primary_disk mirror_disk d25 d26 d27 d140

omc_db12 11 GB primary_disk mirror_disk d25 d26 d27 d145

omc_db_temp

2.0 GB primary_disk mirror_disk d25 d26 d27 d170

omc_db_logs

2.0 GB primary_disk mirror_disk d25 d26 d27 d165

mib_db 2.0 GB primary_disk mirror_disk d25 d26 d27 d185

mib_db1 2.0 GB primary_disk mirror_disk d25 d26 d27 d175

mib_db2 2.0 GB primary_disk mirror_disk d25 d26 d27 d180

mib_db_logs

2.0 GB primary_disk mirror_disk d25 d26 d27 d190

NOTE

• *primary_disk: c0t9d0s0 c0t10d0s0 c0t11d0s0 c0t12d0s0 c0t13d0s0

• *mirror_disk: c1t9d0s0 c1t10d0s0 c1t11d0s0 c1t12d0s0 c1t13d0s0

68P02901W19-S 1-21

Oct 2009

Disk configuration SunFire 4800/4900, Netra 20 and Netra 440 Chapter 1: Introduction to the OMC-R

Table 1-13 OMC-R Single Platform Disk Partition Layout

Partition Size Location

/ 8.8GB (increased by 4GB) Primary Disk S0

swap 4.8GB Primary Disk S1

/var 20.5GB Primary Disk S3

/opt 7.1GB Primary Disk S4

/usr 13.7GB Primary Disk S5

Total 64.9GB Primary Disk

/omcgen 7.0GB Application Stripe

/home 10.9GB Application Stripe

/usr/omc 6.0GB Application Stripe

omc_db1 11.264GB Application Stripe

omc_db5 11.264GB Application Stripe

omc_db9 11.264GB Application Stripe

/usr/omc/ne_data 16.4GB Application Stripe

/usr/omc/ne_data/raw_stats 13.3GB (increased by 2GB) Application Stripe

omc_db_root 2.048GB Application Stripe

omc_db2 11.264GB Application Stripe

omc_db6 11.264GB Application Stripe

omc_db10 11.264GB Application Stripe

omc_db_logs 2.048GB Application Stripe

omc_db3 11.264GB Application Stripe

omc_db7 11.264GB Application Stripe

omc_db11 11.264GB Application Stripe

/solbak 8.0GB Application Stripe

omc_db4 11.264GB Application Stripe

omc_db8 11.264GB Application Stripe

omc_db12 11.264GB Application Stripe

mib_db_logs 2.048GB Application Stripe

omc_db_temp 2.048GB Application Stripe

mib_db 2.048GB Application Stripe

mib_db1 2.048GB Application Stripe

mib_db2 2.048GB (new) Application Stripe

/usr/omc/logs/bss_sec 8.0GB (new) Application Stripe

/usr/omc/logs/sleeping_cell 2.048GB (new) Application Stripe

lod_db1 10GB (new) Application Stripe

Continued

1-22 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Disk configuration SunFire 4800/4900, Netra 20 and Netra 440

Table 1-13 OMC-R Single Platform Disk Partition Layout (Continued)

Partition Size Location

lod_db2 10GB (new) Application Stripe

lod_db3 10GB (new) Application Stripe

/zones 10GB (new) Application Stripe

/usr/omc/ne_data/e1mon 1GB (new) Application Stripe

Total 262GB

NOTE* Netra 440s have different controller numbers than those shown in the table. Insteadof c1 and c3, Netra 440s use c0 and c1. For example, the root partition on a Netra20 is on slice c1t8d0s0 on the main disk and on slice c3t8d0s0 on the mirror disk.However, the root partition on a Netra 440 is on slice c0t8d0s0 on the main diskand on slice c1t8d0s0 on the mirror disk.

68P02901W19-S 1-23

Oct 2009

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, use an Ethernet Local Area Network (LAN) forinteraction. The LAN may be extended to cater to remote workstations or for the addition ofoptional processors.

Each processor must be connected to the LAN before software installation begins or backup isperformed. During normal OMC-R operation the processors NFS mount file systems across thenetwork.

Configuring the OMC-R based LAN

The means of asynchronous communication between the OMC-R processors and workstations istwisted pair cabling which may be connected to a customer LAN/WAN backbone network byusing a Hub or Router or Bridge or Gateway.

Each OMC-R system is provided with a Hub that can be installed for normal operation or usedfor testing.

1-24 68P02901W19-S

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

NOTEThe SQE switch on the Ethernet transceivers should normally be set to OFF. Theswitch should only be set to ON if the processors are to be connected through arouter to a local network where SQE is implemented.

To reduce the impact of a hub failure, a spare hub is provided with the OMC-R.

68P02901W19-S 1-25

Oct 2009

Routine system administration procedures 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 andadminister to the OMC-R system. Certain special procedures may be required depending onindividual customer requirements.

Recommended routine procedures are described in the sections that follow. In each case, areference is made to the relevant section in this manual for the actual procedure. All the resultsfrom these procedures as well as any system changes should be recorded in a log book.

Daily log book

The following items should be recorded by the system administrator in a daily log book thatresides permanently by the system processor console:

• Details of all the procedures that have been performed as user root, Informix, andomcadmin. These should be laid out in chronological order and should include thefollowing 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

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.

• A list of contact names, telephone numbers, and the responsibilities of personnel involvedin daily activities.

• Contact information for any emergency services that may be required.

68P02901W19-S 1-27

Oct 2009

Daily procedures Chapter 1: Introduction to the OMC-R

Daily procedures■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

INFORMIX database daily procedures

The following procedures concern the INFORMIX databases. These procedures should becarried out daily by the OMC-R system administrator.

Back up the INFORMIX databases

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

Monitor the PM database disk usage

To ensure that the PM database functions effectively, the database disk usage should bemonitored daily. When the omc_db_maint utility is used, the omc_db_maint log file containsthe disk usage information required. Refer to Administering the PM database using theomc_db_maint utility on page 8-23 for further information.

Unload and purge the PM database on the system processor

The data stored in the PM database (for example, the regular statistics, subscription lists, andconfiguration data) is copied to ASCII files and then deleted from the PM database by theomc_db_maint utility. This procedure may be automated using cron.

A purge operation should be performed on the database on a daily basis (for example, deletingstatistics). This can be carried out in conjunction with unloading the database using theomc_db_maint utility. Refer to Administering the PM database using the omc_db_maintutility on page 8-23.

Inspect the omc_db_maint log file to ensure that omc_db_maint runs successfully. Refer toAdministering the PM database using the omc_db_maint utility on page 8-23.

The data in the ASCII files can be archived to tape and then deleted.

Check the INFORMIX log files

Inspect the database log files (online.log_OMC and online.log_MIB) for errors and to ensurethat check-pointing is occurring regularly (for example, every five minutes). The databaselog files online.log_OMC and online.log_MIB are located in the /usr/informix directoryon the system processor.

Manually parse any unparsed statistics files

Any raw statistics files that may have escaped processing by the Performance Management (PM)file parser (for example, OMC-R stopped during raw statistics collection period) can be manuallysubmitted using the pm_manual_parse utility. Refer to Database utilities on page 8-4.

1-28 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration UNIX file systems daily procedures

UNIX file systems daily procedures

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

Back up the UNIX file systems

A daily backup of all the OMC-R UNIX file systems should be carried out using StorEdgeEnterprise.

Miscellaneous daily procedures

The following are miscellaneous procedures which should be carried out daily by the OMC-Rsystem administrator.

Check that all cron jobs have completed successfully

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

Check the OMC-R log files

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

Check for core dump files

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

Check the system processor hardware

Procedures for inspecting the hardware are described in Checking the system processorhardware on page 13-99.

Check X.25 connectivity

Procedures for checking X.25 connectivity are described in X.25 application management onpage 9-3.

68P02901W19-S 1-29

Oct 2009

Weekly procedures Chapter 1: Introduction to the OMC-R

Weekly procedures■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

INFORMIX database weekly procedures

The following procedures concern the INFORMIX databases. These procedures should becarried out on a weekly basis by the OMC-R system administrator.

Roll the database log (online.log)

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

UNIX file systems weekly procedures

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

Back up UNIX file systems

A weekly backup of the UNIX file systems (instead of a daily backup) should be carried out usingStorEdge Enterprise, as described in Chapter 12 Backup Server Installation and Configuration.

Archive and remove old OMC-R log files on the system processor andGUI servers

OMC-R log files should be archived onto tape and unwanted log files removed from the diskfile system using the maintain_script utility.

This procedure may be automated using cron (refer to System cron jobs on page 5-3).

Archive and remove unloaded PM database files on the system processor

The ASCII files created by the daily unloading of PM statistics should be archived to tape andremoved from the disk file system using the maintain_script utility.

This procedure can be automated using cron (refer to System cron jobs on page 5-3).

Monitor the UNIX file system disk usage

To ensure that the OMC system functions effectively, the disk usage should be monitored usingthe UNIX command df or the systat utility (refer to OMC-R system information on page 13-8and Full file systems on page 13-21). This can become a weekly task as alarms are generatedwhen the disk becomes full.

1-30 68P02901W19-S

Oct 2009

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 toArchiving old OMC-R user files on page 2-23.

This procedure can be automated using cron (refer to System cron jobs on page 5-3).

Security-related weekly procedures

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

Monitor user security

For security reasons, user account files and network files should be checked for unwantedentries. Additionally, log files in /var/log should be checked for unwanted system accessattempts.

68P02901W19-S 1-31

Oct 2009

Monthly procedures Chapter 1: Introduction to the OMC-R

Monthly procedures■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

UNIX file systems monthly procedures

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

Back up UNIX file systems

A monthly backup of the UNIX file systems (instead of a daily/weekly backup) should be carriedout using StorEdge Enterprise, as described in Chapter 12 Backup Server Installation andConfiguration.

Truncate cron log file

Shorten the cron log file each month to maintain a reasonable file size. For details of thisprocedure refer to Scheduling cron jobs from the command line on page 5-14.

Security-related monthly procedures

The following security-related procedure should be carried out monthly by the OMC-R systemadministrator.

Change passwords

Change the passwords from the standard installation passwords for root, omcadmin andInformix on the system and GUI processors.

Inform all other OMC-R users to change passwords regularly.

1-32 68P02901W19-S

Oct 2009

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 systemadministrator. These additional procedures are conducted on a needs basis.

Complete file system backup

Perform a complete file system backup in the following cases:

• Before and after initial installation of the OMC-R software.

• Before a disk partition size is changed.

Refer to Chapter 12 Backup Server Installation and Configuration.

NE load management maintenance

Archive and remove any NE software loads and databases that are no longer required.

PM raw statistics maintenance

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

OMC-R user accounts

New OMC-R users should be added and old users deleted, as described in Administering useraccounts with usertool on page 2-12.

68P02901W19-S 1-33

Oct 2009

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 initialinstallation of the OMC-R, and after every change to the configuration of the system.

A process id report listing should be made using the ps command for the system and GUIprocessors. This is produced when the systat utility is run. Refer to OMC-R system informationon page 13-8.

System core dumps

System core dump files may be produced (for example, due to system halts or OMC-R errorsoccurring). If system core dump files are produced, the action to be taken is described inCore file generation on page 13-6.

Hardware maintenance

Hardware maintenance procedures should be carried out in accordance with the instructionsof the manufacturers. The following procedures are needed:

• Tape drive cleaning - refer to the Solaris 10 Administrator's Guide.

• Replacement of toner, cartridge, and other printer components - refer to the relevantprinter maintenance manual.

• Clean the monitor screens.

1-34 68P02901W19-S

Oct 2009

Chapter

2

System management■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

68P02901W19-S 2-1

Oct 2009

Overview Chapter 2: System management

Overview■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The following topics are described in this chapter:

• Overview of the Common Desktop Environment (CDE) on page 2-3.

• Administering group accounts with usertool on page 2-8.

• Administering user accounts with usertool on page 2-12.

• CDE utilities available to an omcadmin login on page 2-18.

• CDE utilities available to either root or omcadmin login on page 2-20.

• Archiving old OMC-R user files on page 2-23.

• OMC software management on page 2-24.

• Cleaning up OMC-R software loads on page 2-28.

• NE database maintenance on page 2-30.

• Printing current OMC-R processes on page 2-35.

• Security overview on page 2-36.

• Controlling user activity on the system on page 2-40.

• Controlling user passwords on page 2-42.

• Network file security on page 2-44.

• Installing OMC-R Help on page 2-45.

• Capacity control on page 2-46.

• Restartable processes on page 2-49.

• Graceful shutdown on mains failure on page 2-57.

• Configuration and installation of a remote terminal on page 2-59.

• Remote system processor setup on page 2-63.

• Monitor alternative OMC-R from GUI server on page 2-65.

• Removing OMC-R night concentration centre configuration on page 2-67.

• Setting the locale on the OMC-R on page 2-69.

• General administration checklists on page 2-74.

2-2 68P02901W19-S

Oct 2009

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). The CDE provides an industry standard desktop manager for the OMC-R, and is providedon the different SUN workstations.

The CDE supports:

• Operator configurable windows on startup.

• Reduced window clutter through use of multiple panes.

• A File Manager which provides a graphical front end to the UNIX file system.

There are two desktops displayed in the CDE:

• The Root user desktop (Figure 2-1).

• The OMC admin desktop (Figure 2-2).

The display of the desktop depends upon the type of login.

Figure 2-1 Root user desktop

Figure 2-2 OMC admin user desktop

68P02901W19-S 2-3

Oct 2009

Utilities available from the root CDE desktop Chapter 2: System management

Utilities available from the root CDE desktop

The following CDE desktop tools are described in this chapter:

• Administration.

• StorEdge Enterprise Backup.

NOTEThese tools are only available to a user logged in as root.

These utilities are available from the root CDE desktop, OMC Admin menu, admin_tool option(Figure 2-3).

Figure 2-3 Root user desktop with OMC Admin menu displayed (partial view)

NOTEThe Adminsuite product has become obsolete in Solaris 10. A new tool called usertoolreplaces Adminsuite for administering users and groups.

2-4 68P02901W19-S

Oct 2009

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. Theseutilities are available from the front panel of the CDE desktop.

• File Manager.

• Cron job scheduler.

• Mail.

• Help Manager.

Accessing usertool

Use one of the following procedures to access usertool.

Accessing usertool from the root CDE desktop

Use the following procedure to access the usertool from the CDE desktop.

Procedure 2-1 Accessing usertool from the CDE desktop

1 Login to the system processor as user root. The root CDE desktopis displayed (Figure 2-1).

2 Click on the System Administration icon. The OMC Admin menuis displayed (Figure 2-3).

68P02901W19-S 2-5

Oct 2009

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 Accessing user tool from the Command Line Interface

1 If logged in as user root, execute the following DISPLAY command:

DISPLAY=omc_splat:0.0

Where omc_splat is the TCP/IP address setting of the systemprocessor. This can be found in the /etc/hosts file.OrIf logged in to the server remotely, execute the following DISPLAYcommand:DISPLAY=TerminalDisplay:0.0

Where TerminalDisplay is the TCP/IP address setting of the terminalbeing used for remote login.

2 Execute the following command:export DISPLAY/usr/omc/current/sbin/OMC_Sync

Figure 2-4 Usertool main window

2-6 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Accessing usertool

Once an option is chosen, a screen containing all the relevant fields which can be modifiedappears. On this screen, one field is highlighted with a bar which can be moved with the cursorkeys. The highlighted field can be modified by typing or deleting as required. Once all the fieldsare correctly filled in, select Done to save changes, or select Cancel to quit.

Username : joe Full Name :

Joe Operator Home directory : /home/joe UID

: 500 Group : omc

Secondary groups : Account locked : n

Change password : n

Shell : /bin/csh Done Cancel

If any fields are in conflict, a message to that effect will be displayed:

Username : joe Full Name :

Joe Operator Home directory : /home/joe UID

: 110 UID already in use Group

: omc Secondary groups

: Account locked : n Change password : n Shell :

/bin/csh Done Cancel

Done Cancel

Once Done is chosen, the relevant user or group operation is performed. After adding, deletingor modifying users, the CDE settings and MIB profiles are also updated automatically, if theuser is a member of the omc group.

68P02901W19-S 2-7

Oct 2009

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.

The group management functions in usertool are used to manage the group file in the NISdatabase centralized on the system processor, if the appropriate access privileges are granted.

The usertool supports the following group management tasks.

• Add a group.

• Modify a group.

• Rename a group.

• Delete a group.

NOTEAfter a clean install of an OMC-R system, the groups Informix, omc and omcreadexist. Under normal circumstances, there is no need to add, modify or delete groups.

Before assigning users to a specific group, make sure that the group exists. Group managementis used to add any groups to which the users are assigned.

The Motorola recommended group IDs are as follows:

Informix 109

omc 110

omcread 111

NOTEThe usertool utility described in the following section is designed for local/NISaccounts only. If another naming service (for example, LDAP) is in use, or anothertool (for example, SMC) is preferred, some manual steps are required in order toconfigure MIB profiles.

The procedure for this is: /usr/omc/current/sbin/OMC_SysProc_Synchronise actionparameters.

2-8 68P02901W19-S

Oct 2009

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

Group specifies a name used by the system to identify a user group. A group name containslower case alphabetical characters (a - z) and digits (0 - 9). Spaces are not allowed. A groupname is between 1 to 8 characters long. By default, the groups omc, omcread and Informixare present along with the standard operating system groups.

Group ID (GID)

Group ID specifies a group identification number used by the system to identify a user's primarygroup. To minimize the amount of software incompatibility, GIDs are kept below 60000.Reserved GIDs include 60001 (nobody), 60002 (no access) and 65534 (no group).

Figure 2-5 Group administration utility

68P02901W19-S 2-9

Oct 2009

Adding a group Chapter 2: System management

Adding a group

Use the following procedure to add a new user group.

Procedure 2-3 Adding a new user group

1 Follow the procedure Accessing usertool on page 2-5.

2 From the usertool main window, select Add group. The Groupadministration utility is displayed as in Figure 2-5.

3 Enter a unique Group name and Group ID (GID).

4 To commit the changes, select Done by highlighting it with the cursorkey and pressing Enter.

Modifying group accounts

Use the following procedure to modify a group account.

Procedure 2-4 Modifying a group account

1 Follow the procedure Accessing usertool on page 2-5.

2 From the usertool main window, select Modify group. The Groupadministration utility is displayed as in (Figure 2-5).

3 Modify the group name and/or GID as required.

4 To commit the changes, select Done by highlighting it with the cursorkey and pressing Enter.

Renaming group accounts

Use the following procedure to rename a user group.

Procedure 2-5 Renaming a user group account

1 Follow the procedure Accessing usertool on page 2-5.

2 From the usertool main window, select Rename group.

3 Enter the name of the group to be renamed.

4 Enter the new name for the group and press return to complete the process.

2-10 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Deleting group accounts

Deleting group accounts

Use the following procedure to delete a user group.

Procedure 2-6 Deleting a user group account

1 Follow the procedure Accessing usertool on page 2-5.

2 From the usertool main window, select Delete group.

3 Enter the name of the group to be deleted.

4 To commit, select Done by highlighting it with the cursor key andpressing Enter.

68P02901W19-S 2-11

Oct 2009

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 inthe NIS database centralized on the system processor. A user account enables a user to login to a system and provides the access to a home directory.

The user management functions in usertool are used to perform the following user managementtasks.

• Add a new user account.

• Modify a user account.

• Rename a user account.

• Delete a user account.

• Change a users password.

NOTEAfter adding, deleting or modifying users, the CDE settings and MIB profiles areupdated automatically if the user is a member of the omc group.

A root user can manage user accounts in the NIS domain.

Before assigning users to specific groups, ensure that the groups exist. Before adding useraccounts, group management should be used to check any groups to which users are assigned.See Administering group accounts with usertool on page 2-8.

The Motorola recommended group IDs are as follows.

Informix 109

omc 110

omcread 111

NOTETo ensure that the correct GUI colors appear for all users, follow the procedure inthe section Ensuring the correct GUI colors appear.

2-12 68P02901W19-S

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.

Procedure 2-7 Ensuring the correct GUI colors appear for all users

1 Login as root.

2 Enter the following command:cd /etc/dt/config/C

3 Edit the sys.session file. If this file does not exist, copy it from the/usr/dt/config/C directory.

4 Comment out the three command lines that start with dtsmcmd.

5 Save the file.

User management parameters

The different user management windows can contain combinations of the following parametersdescribed in this section.

User name

User name specifies a login name the user will use when logging onto the OMC system. A username should be a unique name composed of 1-8 upper case or lower case alphabetical characters(A-Z, a-z) or digits (0-9). It is advisable that the first character is a lower case letter (a-z).

Full name

Full Name is a control that specifies notes about the user account, such as a user's full nameor role. Although Full name is an optional control, it is highly recommended that a value beentered in this field, as it is required by specific command line Operation and Maintenanceutilities such as cmdLineAudit.

Home directory

Home directory shows the default home directory for the user and can be edited as required.

User ID (UID)

User ID specifies a unique number by which the operating system can identify a user. The UIDshould be unique. It is good practice to have sequentially increasing UIDs to aid in systemadministration.

68P02901W19-S 2-13

Oct 2009

User management parameters Chapter 2: System management

Group

Group specifies a group ID number or group name that the operating system assigns to filescreated by the user. Standard group numbers are 110 for a normal OMC operator account, 111for a restricted omcread account, and 109 for an Informix account.

Secondary groups

Secondary groups is an optional control that is not used in the Motorola configuration, but itspecifies one or more groups to which the user belongs.

Account locked

Setting account locked to y means that this account cannot be accessed. The default settingis n (unlocked).

Change password

Setting change password to y forces the user to enter a new account when accessing thisaccount for the first time. The default setting is n.

Shell

Shell specifies the login shell to be used. The default shell is the C shell. The C shell ismandatory for OMC users.

Figure 2-6 User administration utility

2-14 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Adding a user

Adding a user

Use the following procedure to add a new user.

Procedure 2-8 Adding a new user

1 Follow the procedure Accessing usertool on page 2-5.

2 From the usertool main window, select Add user. The Useradministration utility is displayed as in Figure 2-6.

3 Enter a unique user name and modify the default user creationparameters as required.

NOTEIt is highly recommended that a value is entered in theFull name field, as it is required by specific command lineOperation and Maintenance utilities such as cmdLineAudit.

4 Highlight Done and select it by pressing the Enter key.

5 Enter the user account password twice. This completes user creation.

NOTE

• The user privileges and profile are updated in the MIB database.

• If the OSI Processor is already integrated with or connected to the OMC,each new OMC user will be automatically entered into the relevant/usr/omc/config/global/system_table file of the Security Application.

• If the OSI Processor is to be integrated or configured later, or if, for somereason, the users on the OMC and the OSI (the Security Application) are outof synchronization, the user entries in both applications must be synchronizedmanually using the OMC Security Synchronization tool.

Modifying a user account

NOTEUnder normal circumstances users root, omcadmin and Informix should not bemodified.

68P02901W19-S 2-15

Oct 2009

Renaming a user account Chapter 2: System management

Use the following procedure to modify a user account.

Procedure 2-9 Modifying a user account

1 Follow the procedure Accessing usertool on page 2-5.

2 From the usertool main window, select Modify user. The Useradministration utility is displayed as in Figure 2-6.

3 Enter the name of the user to be modified and modify parameters asrequired.

4 To commit the changes, select Done by highlighting it with the cursorkey and pressing Enter.

Renaming a user account

NOTEUnder normal circumstances users root, omcadmin, and Informix should not berenamed.

Use the following procedure to rename a user account.

Procedure 2-10 Renaming a user account

1 Follow the procedure Accessing usertool on page 2-5.

2 From the usertool main window, select Rename user.

3 Enter the name of the user to be renamed.

4 Enter the new name for the user and press return to complete the process.

Deleting a user account

NOTEUnder normal circumstances users root, omcadmin and Informix should not bedeleted.

2-16 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Deleting a user account

Use the following procedure to delete a user account.

Procedure 2-11 Deleting a user account

1 Follow the procedure Accessing usertool on page 2-5.

2 From the usertool main window, select Delete user.

3 Enter the name of the user to be deleted.

4 To commit to deleting the group, select Done by highlighting it withthe cursor key and pressing Enter.

NOTEThe user profile is also deleted from the MIB database.

68P02901W19-S 2-17

Oct 2009

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.

Procedure 2-12 Displaying the omcadmin CDE desktop

1 From the GUI Client graphical CDE login screen, as shown inFigure 2-7, select Remote Login from the Options menu.

2 Type the hostname of a GUI server that exists in the /etc/hosts fileof the GUI client, and click OK.

3 The GUI server graphical CDE login screen appears, as shown inFigure 2-8.

4 Enter the username omcadmin and password, then click OK todisplay the CDE desktop.

Figure 2-7 GUI client graphical CDE login screen

2-18 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Database Applications menu

Figure 2-8 GUI server graphical CDE login screen

Database Applications menu

Click on the INFORMIX icon from the omcadmin CDE desktop to display the DatabaseApplications menu. The following options are available from this menu.

• Install Icon.

• Informix.

Other database monitoring utilities can be added using the CDE desktop controls.

68P02901W19-S 2-19

Oct 2009

CDE utilities available to either root or omcadmin login 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.

Procedure 2-13 Displaying the root CDE desktop

1 From the GUI client graphical CDE login screen, as shown inFigure 2-7, select Remote Login from the Options menu.

2 Type in the hostname of a GUI server that exists in the /etc/hosts fileof the GUI Client, and click OK.

3 The GUI server graphical CDE login screen appears, as shown inFigure 2-8.

4 Enter the username root and password, then click OK to display theroot CDE desktop.

Figure 2-9 GUI client graphical CDE login screen

2-20 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Overview of utilities common to root and omcadmin

Figure 2-10 GUI server graphical CDE login screen

Overview of utilities common to root and omcadmin

The following CDE utilities are common to both a root and an omcadmin login.

• Style Manager.

• File Manager.

Style Manager

Style Manager can be accessed from the CDE desktop and is used to change desktop attributesrelating to colors, font, backdrop, keyboard click volume, mouse speed, screen lock, windowbehavior, and startup preferences to create a customized desktop.

Use the following procedure to open the Style Manager.

Procedure 2-14 Opening the Style Manager

1 Invoke the Style Manager by entering the command:/usr/dt/bin/dtstyleThe Style Manager window is displayed.

2 Click on the icon in the Style Manager window to select the item thatis to be customized.

68P02901W19-S 2-21

Oct 2009

File Manager Chapter 2: System management

File Manager

The File Manager (Figure 2-11), accessed through the CDE front panel, provides a GUI to theUNIX file system. The File Manager is used to create, find, and use workspace objects suchas files, folders, and applications. Each object is represented by an icon in the File Manager.File Manager allows the following operations to be performed:

• Move, copy, open, and delete objects.

• Open an Xterminal.

• Change permissions on objects.

• Search for an object.

• Customize the File Manager View.

Figure 2-11 File Manager, main window (Home)

2-22 68P02901W19-S

Oct 2009

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 notbeen modified for the last two weeks.

Procedure 2-15 Checking home accounts of users for unmodified files

1 Login to the system processor as user root.

2 Execute the following to select the OMC-R user files that need to bearchived:find /home -mtime +14 -print > /usr/tmp/listing

3 The file /usr/tmp/listing may contain a list of user files that need tobe archived or removed from the system. Use the UNIX commandtar to archive the files to tape.

68P02901W19-S 2-23

Oct 2009

OMC software management Chapter 2: System management

OMC software management■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section describes the OMC software management.

Introduction to OMC software management

The OMC-R software is supplied as five standard Solaris packages. These are as follows.

• MOTs1900 Software for the Single Platform Processor for 1900 under /usr/omc.

• MOTs1900x Software for the Single Platform Processor for 1900.x under /usr/omc/1.9.0.0.x.

• MOTc1900 Software for the GUI server for 1900 under /usr/omc.

• MOTc1900x Software for the GUI server for 1900.x under /usr/omc/1.9.0.0.x.

• MOTh1900x Help files for 1900.x.

The OMC-R software and test objects can be installed, viewed and removed using the swtoolutility, located in /usr/omc/sbin. This utility can be run by any user to view the installed softwarereleases and test objects. To install and remove software, login as root.

Software loads

To manage OMC-R software loads, execute the swtool utility as the root user. Using the optionsavailable in this menu software can be installed or removed.

The following menu is displayed:

Motorola Software Tool1. Display software inventory2. Manage releases3. Manage test objects4. QuitYour choice:

Select the manage releases option.

The following options are displayed:

1. Install a release.2. Remove a release.3. Main menuYour choice:

2-24 68P02901W19-S

Oct 2009

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 releaseoption from the OMC Releases menu in swtool. Insert the DVD containing the new softwarereleases in the local DVD drive. The following menu options are displayed:

Install release

1. Install OMC Software Release and Cutover Machine.

2. Install OMC Software Release Only.

3. Cutover.

4. Done.

Your choice:

If you wish to install the software and cutover in a single step, select Install OMC SoftwareRelease and Cutover Machine. Otherwise, select Install OMC Software Release Only.When prompted for the path of the software, you can select the default option since the softwareis normally installed from the DVD in the local DVD-ROM drive.

The relevant software packages for the system are then installed. If cutover is selected, thecutover script is automatically executed once the software installation is complete. Note thatthis causes an outage for the duration of the cutover.

Removing old software

It is important to delete old releases and retain only a few requisite software releases.

NOTEOld software releases should no longer be removed using the rm command. Theswtool utility should be used.

From the OMC Releases menu in swtool, select the Remove a release option.

1900.16.

1900.17.

1900.18.

None.

Remove which release?

Select the release to be removed.

NOTEA current release cannot be removed.

If a software release is removed, associated test objects, if any, are automatically removed.

68P02901W19-S 2-25

Oct 2009

Test objects Chapter 2: System management

Test objects

The OMC software is supplied as Solaris packages, therefore the majority of test objects aresupplied as Solaris patches. Execute the swtool utility as user root. A menu similar to thefollowing is displayed.

NOTERead the relevant release notes for each test object for details about installation orremoval, such as whether the OMC needs to be stopped during the installation.

Motorola software tool

1. Display software inventory.

2. Manage releases.

3. Manage test objects.

4. Quit.

Your choice:

Select the Manage test objects option.

The following options are displayed:

Test objects

1. Install a test object.

2. Remove a test object.

3. View test object history.

4. Show files in a test object.

5. Main menu.

Your Choice:

Installing the test objects

From the Test objects menu in swtool, select the Install a test object option. The followingprompt is displayed:

Install test object from which directory? [/].

When prompted, enter the directory containing the test object (TAR) file. A menu is displayedcontaining all the test objects available in that directory. Select the correct test object. Theselected test object is installed automatically. It is assumed that the object is relevant to thesystem Single Platform Processor or GUI server on the correct load.

2-26 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Test objects

Removing the test objects

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

Test object history

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

Files modified by a test object

From the Test objects menu in swtool, select the Show files in a test object option. A menuappears displaying all the test objects installed on the system. Select a test object to view allthe files the test object modifies.

68P02901W19-S 2-27

Oct 2009

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 loadcurrently running on the OMC-R. There may be two OMC-R application software loads in thisdirectory, the current software load and the previous software load.

If too many OMC-R application software loads are stored in /usr/omc, the file system becomesfull and the cutover script used to cutover to a new OMC-R software load may fail.

If the /usr/omc/sbin/cutover script fails to execute correctly and the /usr/omc file system isover 85% full, the script produces an error message.

If the /usr/omc file system is over 80% full, the script produces a warning message. Theoperator can then decide whether or not to continue with the script.

To avoid the file system becoming full and to ensure that the cutover script runs correctly,clean up the /usr/omc directory regularly.

Keeping software loads

Use the following procedure to keep software loads on the system processor.

NOTEThis procedure must not be used with the current software load.

Procedure 2-16 Keeping software loads on the system processor

1 Login as the user root.

2 Enter the following commands on the system processor.cd /usr/omctar cvf <tarfilename.tar> <omcloaddirectory>where<tarfilename.tar> is the name of the new tar file.<omcloaddirectory> is the name of the OMC-R software load, forexample, 1.8.0.0.x.

3 Enter the following commands:compress <tarfilename.tar>rm -rf <omcloaddirectory>

4 Move the tar file to a file system with sufficient storage space.

2-28 68P02901W19-S

Oct 2009

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.

Procedure 2-17 Using a tarred software load

1 Login as the user root.

2 Enter the following command:mv /<pathname>/tarfilename.tar.Z /usr/omcwhere<pathname> is the directory path name the tar file is stored.

3 Enter the following commands:cd /usr/omcuncompress <tarfilename.tar.Z>tar xvf <tarfilename.tar>rm tarfilename.tar

68P02901W19-S 2-29

Oct 2009

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 thesystem processor as omcadmin.

Archiving and removing a NE database

Before a NE database is removed from the file system, it should be archived. Use the followingprocedure to archive to a DAT tape drive, entering the commands in sequence.

Procedure 2-18 Archiving the NE database to a DAT tape drive

1 Enter the following command:cd $OMC_TOP/ne_data/dbroot/ne_type/ne_specific/ne_name

where: ne_type is the NE type,for example, BSS or RXCDR, ne_specific is either BSS-specific orRXCDR-specific, ne_name is the name of the NE database directory,for example, bss1.

2 Enter the following command:tar cvf /dev/rmt/0 db_name/*where db_name is the name of the NE database directory, for example,db920913171522/*.

3 When the database has been archived to tape, it can be removed usingthe following command:rm -r db_name

Maintaining NE raw statistics

All procedures relating to raw statistics maintenance should be carried out while logging intothe system processor as omcadmin.

Part of the procedures to be performed on a daily basis is to check if any raw statistics haveescaped processing by the parser.

NOTEAvoid submitting several files simultaneously for manual processing, as this mayadversely affect automatic processing.

2-30 68P02901W19-S

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.

Procedure 2-19 Submitting raw statistics files to the parser

1 Login using login id omcadmin.

2 Check if any raw statistics files have escaped processing by the parserby entering the following command (typed as a single line)./bin/find $OMC_TOP/ne_data/raw_stats/100,0 -name “*.*“-mtime +1 -print > /usr/tmp/parser_listIf this command does not produce any output it means that none of theold statistics files have escaped processing.

3 Files which do not have a suffix of bad_header, failed_load orno_db_storage, should be submitted one at a time, using the followingcommand:$PM_ROOT/bin/pm_manual_parse filenamewhere filename is from the parser list.

If the utility does not succeed in sending the supplied filename to the parser, an appropriateerror message is displayed on the screen. The speed of parsing depends on the time of day thatthe command is executed.

For more information, refer to Database utilities on page 8-4.

Removing NE fallback software load directories

Use the following procedure to remove a NE fallback software load directory, entering thecommands in sequence.

Procedure 2-20 Removing a NE fallback software load directory

1 Login using login id omcadmin.

2 Enter the following:cd $OMC_TOP/ne_data/dbroot/ne_type/ne_specificwhere: ne_type is the NE type,for example, BSS or RXCDR, ne_specific is either BSS-specific orRXCDR-specific.

3 Enter the following command:rm -r specific_fallback_load_dirwhere specific_fallback_load_dir is the name of the fallback directoryto be removed.

Manual parsing of statistics checklist

Follow the procedure (Table 2-2) to manually parse statistics files. Copy the checklist providedin Table 2-2 to record the checks.

68P02901W19-S 2-31

Oct 2009

Manual parsing of statistics checklist Chapter 2: System management

Table 2-2 Manual parsing of statistics checklist

Serialnumber Check Method

1 Check that the parserprocess is running.

As user omcadmin execute the following command:ps -elf | grep + | grep Parser

2 Check that the FMPATHenvironment variable isset.

As user omcadmin execute the following command:echo $FMPATHThis environment variable should be set to:/usr/omc/ne_data/raw_stats

3 Check if any raw statisticsfiles have escapedprocessing by the parser.

As user omcadmin execute the following commands:/bin/find $OMC_TOP/ne_data/raw_stats/100,0-name “*.*“ -mtime +1 -print >/usr/tmp/parser_list

4 Submit any files found bythe find command thatdo not have a suffix ofbad_header, failed_load,or no_db_storage one ata time to the parser.

As user omcadmin execute the following command:$PM_ROOT/bin/pm_manual_parse <filename>Check for any error messages from thepm_manual_parse utility.

5 Where .bad_headerfiles exist, verifythe setting of thePM_HOURLY_STATSenvironment variable.This variable must be setto either ON or OFF tomatch the setting of theBSS.

As user omcadmin execute the following commands:cd /usr/omc/config/global

Using the vi editor, edit the OMC.CNFG file.Uncomment the setting for PM_HOURLY_STATS andalter the environment variable so it looks like eitherof the following, depending on the requirement at theBSS:

PM_HOURLY_STATS=ON

Or:

PM_HOURLY_STATS=OFF

Save and exit the file, then execute the followingcommand as user omcadmin:omctool -m PARSER_1 -cThen execute the following commands for all fileswith a bad_header extension:mv <filename>.bad_header filenamepm_manual_parse filename

Continued

2-32 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Manual parsing of statistics checklist

Table 2-2 Manual parsing of statistics checklist (Continued)

Serialnumber Check Method

NOTEThis workaround only temporarily sets thevalue of PM_HOURLY_STATS. If an omcstop and start is performed on the system,this change is overwritten.To make the change a permanentone, set the value of thePM_HOURLY_STATS variable in the/usr/omc/config/global/pmProcConfig.cshfile.

6 Check that the manualparse was successful.

As user omcadmin execute the following command:tail -f $SYS_LOG/fpomcaudit<yyyymmdd>Successful parsing output is shown in ParsingOutput.

7 If the Parser process failsand is restarted, checkwhether the statisticscollection and parsingoperation resume withoutmanual intervention.

As user omcadmin execute the following command:tail -40 $SYS_LOG/fpomcaudit<yyyymmdd>The log file shows that files are being parsed againsuccessfully.

8 Check that thefpomcaudit log file isrolled over and that oldlogfiles are removedsuccessfully by themaintain_script cronjob.

As user omcadmin execute the following commands:cd /usr/omc/logsls -l fpomc*

9 If theparserDisconnectedTooLongalarm is raised thenthe parser must beconnected to thedatabase.

As user omcadmin execute the following commands:cd /usr/omc/current/sbindb_disconnectconnect parser

10 Monitor the value ofthe neighbor statisticsenvironment variable.

Refer to Using neighbor statistics on page 13-91in Chapter 12 for further details about raising themaximum limit of neighbor statistics.

Parsing Output

20050405000016 (22027) FP : File added to Parser List. 20050405000016 (22027)

FP : FILE HEADER : NE Type 31 : NE Id 1 : Time 2005-4-4 23:30:0:825 : Duration

1900 : V 1900 20050405000016 (22027) FP : UNL preparation for current statsfile

complete. 20050405000017 (4701:1) PML: PM_I_PARSFILE_MSG received.

20050405000017 (4701:2) PML:

BIN File /usr/omc/ne_data/raw_stats/100,0/31,1/1

68P02901W19-S 2-33

Oct 2009

Manual parsing of statistics checklist Chapter 2: System management

- 23:30:0-4:4:

2005 Loading started. 20050405000034 (4701:9) PML: BIN File /usr/omc/ne

_data/raw_stats/100,0/31,1/1- 23:30:0-4:4:2005 Loading completed. 20050405000034

(4701:9) PML: BIN File /usr/omc/ne_data/raw_stats/100,0/31,1/1- 23:30:0-4:4

:2005 deleted

20050405003016 (22027)

FP : File added to Parser List. 20050405003016 (22027) FP :

FILE HEADER : NE Type 31 : NE Id 1 : Time 2005-4-5 0:0:0:825 : Duration 1800 :

V 1800 20050405003016 (22027) FP : UNL preparation for current statsfile

complete.

20050405003017 (4701:1) PML: PM_I_PARSFILE_MSG received 20050405003017

(4701:2) PML: BIN File /usr/omc/ne_data/raw_stats/100,0/31,1/1- 0:0:0-5:4:2005

Loading

started. 20050405003034 (4701:9) PML:

BIN File /usr/omc/ne_data/raw_stats/100,0/31,1/1-

0:0:0-5:4:2005 Loading completed. 20050405003034 (4701:9) PML: BIN File

/usr/omc/ne_data/raw_stats/100,0/31,1/1- 0:0:0-5:4:2005 deleted.

See Database utilities on page 8-4 in Chapter 8 for further details of the pm_manual_parse utility.

2-34 68P02901W19-S

Oct 2009

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, a printout of theprocesses running on both the system and GUI processors should be made.

Procedure to print OMC-R processes

Use the following procedure to produce files of processes on the system and GUI processors:

Procedure 2-21 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

68P02901W19-S 2-35

Oct 2009

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 considerationsof the OMC-R system.

The security of the OMC-R system is the responsibility of the system administrator, who shouldpay particular attention to the following:

• The number of users on the OMC-R system.

NOTEThe number of users supported by the OMC-R at any time is 200. The OMC-Rcannot support more than 200 users.

• Whether users require special privileges (for example, login id omcadmin), normalOMC-R software access (for example, group id omc), or restricted OMC-R software access(for example, group id omcread).

• The regular update of OMC-R user passwords.

• Any network file that contains security-related information (for example, .rhosts file).

• Tape archiving and backup procedures, including the storage of all tapes.

• Checking for unauthorized access to the OMC-R system through the X.25 or LAN interfaces.

• Ensuring that the remote X terminals have screen lock enabled.

• Ensuring that all remote X terminals have a unique local configuration file setup.

As part of GSR9, the system has been made more secure by default. This means certain servicesmay have to be manually re-enabled to re-introduce functionality which was previously reliedupon. For example, the netstat function is disabled in GSR9; to use the function turn it onmanually.

Services

A summary of the changes is listed as follows. The text in brackets details some of the files andsettings affected by the changes.

• Enabled connection logging (inetd connections, /var/log/connlog).

• Enabled ftp connection logging.

• Disabled sendmail (except for local mail).

2-36 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Services

• Disabled public tty access (mesgn).

• Disabled root ftp access (/etc/ftpd/ftpusers).

• Disabled root login (unless on console).

• Restrict cron, at (/etc/cron.d/cron.allow /etc/cron.d/at.allow).

• Limit valid shells (/etc/shells).

• Improved TCP sequence numbers (TCP_STRONG_ISS=2).

• Log failed logins (SYSLOG_FAILED_LOGINS=0).

• Network stack tweaks (ip_ignore_redirect, ip_forward_src_routed, ip_respond_to_time-stamp, and many more).

• Disabled any unused services (finger, spray, apache, etc).

• NIS no longer mandatory.

• ssh available for use.

A list of standard Solaris 10 services which are disabled by default by the Solaris 10 OMC-Rinstall is as follows:

power S75seaport

autofs S76snmpdx

rpc_udp S77dmi

rpc_tcp S82initsma

rpc_ticotsord S90samba

ktkt_warn login - rlogin

rusers login - eklogin

rstat login - klogin

gss rexec

rquota kshell

ipp-listener shell

rfc1179 finger

S42nackmod telnet

S47pppd ftp

S73cachefs_daemon rpc - rusers

S90webm rpc - rstat

S90webconsole rsh

S50apache

To view a complete list of the services that are operational, run the following command asuser root:svcs

68P02901W19-S 2-37

Oct 2009

Enabling and disabling services Chapter 2: System management

To view a complete list of services, including disabled services, run the following command asuser root:svcs -a

NOTEIf a service is labeled lrc as shown in the following example, it implies that the serviceis not managed under the Solaris10 Service Management Facility. Stop and start theservice by running the script by passing a start/stop parameter. :

legacy_run 15:03:14 lrc:/etc/rc2_d/S87x25net

. Using the S87x25net example shown to start the service, run the following as userroot:/etc/rc2_d/S87x25net start

Enabling and disabling services

If a particular service (for example, such as sendmail) is required, it can be re-enabled byperforming the following steps as user root:

svcamd enable <service>

Where Is

service the name of the service to beenabled.

This restarts the service and configure it to start automatically on boot-up. Similarly, to disablea service, perform the following as user root:

svcamd disable <service>

This stops the service and prevent it from automatically starting on boot-up.

Other security changes

In addition to the disabling of many services, other changes have been made in GSR9 as follows:

• Root can only log in directly through console (not directly through telnet).

• Root cannot ftp into the box.

• System accounts locked.

• /etc/shells file limits valid shells.

• Extra connection logging (in /var/adm/messages, /var/adm/loginlog, /var/log/authlogand /var/log/connlog).

2-38 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Other security changes

• Network stack tuning.

• Stack exec protection.

• Cron and at job access limited.

68P02901W19-S 2-39

Oct 2009

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 system administrator should use threedifferent login IDs as follows:

Login id root

• Superuser root can access all files within a particular UNIX system, regardless of theirownership, protection or grouping.

• The root owner can control, edit, or manipulate any other user of that UNIX system. Inparticular, the root owner can delete any file on any of the processors file systems.

• The system processor has a designated root owner with an associated password and allother SPARC-based processors have a designated root owner with a different password.The passwords must be changed regularly.

• The login id root should only be used by the system administrator.

Login id omcadmin

• The login id omcadmin is set up with the same user id on all processors.

• This login id is the owner of the OMC software, and usually runs the OMC activities. Thisuser is able to remove the OMC software.

• The home directory for omcadmin follows the same path as all the OMC users (/home)and belongs to the group omc.

• The login id omcadmin is used by both the system administrator and the OMC Operator.It is the responsibility of the system administrator to change the omcadmin passwords.

Login id informix

• The login id informix is the owner of the OMC Relational Database Management System(INFORMIX).

• Database administration is performed using the informix login id on the system processor.

• The home directory for informix is /usr/informix, and its group id is informix.

• The login id informix is only used by the system administrator.

2-40 68P02901W19-S

Oct 2009

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 thelogin ids:

• root.

• omcadmin.

• informix.

Any number of OMC users with an individual login id can be added to the system. The groupid given to OMC users can either be omc or omcread. OMC users in the group omc canperform all the usual network operator tasks, whereas OMC users in the omcread group canonly perform non-destructive tasks.

68P02901W19-S 2-41

Oct 2009

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 OMCsystem, and is responsible for controlling user passwords and issuing guidelines for selectingsensible passwords.

User passwords

User activity on the OMC system is controlled by issuing passwords to each login user. This isparticularly important for controlling access to the OMC using the following login ids: root,informix and omcadmin.

When installing a new user on the system, the user's real name should be entered. Passwordsshould be altered at regular intervals and OMC users should be made aware that their logindirectory paths can be changed.

NOTEThe login id omcadmin is used by both the Operator and the OMC systemadministrator.

Password conventions

Passwords chosen by the user should follow certain guidelines to maintain security on thesystem.

Password naming conventions should be as follows:

• Passwords should be at least six characters in length, and should include digits and/orpunctuation marks.

• Monthly password changes are recommended.

Users should be discouraged from any of the following practices:

• Matching anything in the user's UNIX account information, such as login id.

• Matching anything in the spelling dictionary of the system.

• Having three or more repeated characters, for example, aaa.

2-42 68P02901W19-S

Oct 2009

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. Theprocess of setting or changing the Packet Switch password is described in the manufacturer'sdocumentation.

68P02901W19-S 2-43

Oct 2009

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 throughthe following software:

• Transmission Control Protocol/Internet Protocol (TCP/IP).

• Network File System (NFS).

• File Transfer Protocol (FTP).

Figure 2-12 shows how different software packages are secured to avoid unauthorized access.

Figure 2-12 Software security through Remote Execution and NFS

Network File System (NFS)

The Network File System (NFS) permits several hosts on a network to share files over thenetwork. NFS is used by the OMC-R software to remotely mount the Event Log file systemonto GUI processors. It can also be used to remotely mount any other file system. The file/etc/dfs/dfstab lists the file systems that can be accessed by other hosts with NFS.

The /etc/dfs/dfstab file on the system processor and the /etc/vfstab file on other SPARC basedprocessors, list local file systems that can be accessed by other hosts on the network withNFS capabilities.

The .rhosts file should only contain entries for hosts on the local OMC-R network.

2-44 68P02901W19-S

Oct 2009

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, asa package of the form MOTh1900xx where xx indicates the point release of the load installed.

68P02901W19-S 2-45

Oct 2009

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, by displaying an alarm GUI error dialogbox. This ensures that operators are aware of the additional hardware and/or software licensesrequired to support further traffic channels.

RTF is used as a measurement instead of TCH because it is a more accurate measure of thecapacity of the system.

Capacity control mechanism

An OMC-R can support only a particular number of RTFs, the RTF limit. RTFs are used tomeasure system capacity in preference to radios because there may be redundant radios thatare not counted in the RTF total. TCHs are also not a reliable measure of capacity because theirnumber may change dynamically, and there is no easy way to calculate a reliable total. TheOMC-R has a threshold RTF value of 90 percent of the RTF limit. The RTF limit is set duringstaging and can only be modified with the assistance of Motorola. If the limit is changed, thenew limit comes into effect immediately with subsequent effect on any related alarms.

The OMC-R checks the number of configured RTFs when an RTF is being created. If this numberexceeds the threshold RTF value, but does not exceed the RTF limit, a major severity alarm isgenerated. A critical alarm is generated if the value exceeds the RTF limit. This check is alsoperformed during OMC-R startup. The alarms are only generated the first time the thresholdis exceeded. If the number of configured RTFs either falls below the limit or threshold valueswhen an RTF is deleted, the alarm is changed to major severity or cleared, respectively.

If the number of configured RTFs exceeds the OMC-R RTF limit, a dialog box to this effect isdisplayed. This dialog box informs the user that the OMC-R is exceeding its licensed RTFcapacity. This dialog box does not affect OMC-R operation, but the user has to confirm thisdialog box once every hour while the RTF limit continues exceed the OMC-R RTF limit.

Feature Capacity Licensing and Audit

The Licence Audit tool monitors the usage of carriers across the network on a per feature basis.Information is gathered by running scheduled audits against the OMC-R CM database to producea report indicating the number of RTFs equipped in the database to support each feature.

The audit is triggered by a configurable interval parameter in the OMC software. If the intervalparameter is not set, or set outside the permissible range of 2 to 48 hours, the default value of12 hours is used. The result of the audit (actual usage) is compared with the license file perfeature. An alarm is generated for each feature where the license usage is exceeded. If theusage is within the limit, the Licence Audit Tool generates a corresponding event. The alarmsand events are displayed at one or all OMCs in the network, as configured during installation.

2-46 68P02901W19-S

Oct 2009

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, too many NEs in MIB Critical

• 30038 OMC-R Capacity Ceiling Violation, too many RTFs in MIB Critical

• LicenseAuditNotAvailableAlarm Critical

• LicenseFileNotAvailableAlarm Critical

• LicenseViolationAlarm Critical

NOTEIf any of the above mentioned alarms occur, inform the Motorola support group.

Updating RTF license limit

To execute the following procedure, the parameters originally provided by Motorola are neededand they are listed as follows:

• Encryption Key

• RTF Ceiling limit

• Licence issue date

• Licence checksum

If the above parameters have been mislaid, contact sysdep_cro@ecid.cig.mot.com for furtherinformation.

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 process id number:ps -ef | grep lmgrd.omc

3 Terminate the lmgrp.omc process:kill -15 <lmgrd.omc pid number>

Continued

68P02901W19-S 2-47

Oct 2009

Updating RTF license limit Chapter 2: System management

Procedure 2-22 Updating the RTF license limit (Continued)

4 Start the OMC License Administration Tool:/usr/omc/current/sbin/populate_licenseThe following window is displayed:

======================================================OMC License Administration Tool-------------------------------

1. Invoke New License2. Quit

======================================================Enter Option:

5 Enter 1 to invoke New License option.

6 Enter the encryption key when prompted, for example, 86B0997EFF9.

7 Enter the new updated RTF Licence limit, when prompted, for example,1000.

8 Enter NE limit, for example, 128.

9 Enter the Licence issue date, when prompted, for example,23-Oct-2003.

10 Enter the checksum when prompted, for example, 131. The followingoutput is displayed: Are you happy with these entries [y/n]?

11 Enter y if all entries are acceptable.The following output is displayed: Modifying the license_examplefileCopying license_file to /opt/omc/license_tools/license_file

NOTEFor Feature Capacity and Licensing, the licensed capacity for every feature that can be licensed isupdated through the License Administration Tool by executing the following script:/usr/omc/current/sbin/populate_license gThis invokes a GUI interface. For specific details on configuring licenses with this tool, pleaserefer to System Information: License Audit (68P02901W59).

2-48 68P02901W19-S

Oct 2009

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.

• Critical (non-restartable).

A restartable process is a process which is restarted automatically if it fails. If a restartableprocess exits suddenly, or hangs, it is restarted without operator intervention.

A critical process is a process which must start correctly before the OMC-R can continue tostart up and remain running. If a critical process fails, the entire OMC-R is restarted. Thefollowing processes are critical processes:

• em_main.

• em_lm_main.

• cm.

• nameserver.

NOTEAn automatic OMC-R restart does not take place if the nameserver critical processfails. If this process fails, it is necessary to perform a manual OMC-R stop or start.

Restarting processes

The OMC-R attempts to start failed restartable processes indefinitely. On the first failure, arestart is attempted immediately. If this does not restart the process, five further attempts willbe made at intervals of 150 seconds and thereafter every 900 seconds.

This enables the OMC-R to cope with processes that cannot be restarted without operatorintervention, as well as with processes that may recover after longer intervals.

If a critical (non-restartable) process fails, then the entire OMC-R is restarted automatically.GUIs will need to be restarted if the entire OMC-R restarts, or if certain other processes arerestarted.

Any process that fails may lose operations that were in progress when it failed. For example,if the RLogin process stops and restarts, current remote login sessions will be disconnectedand will need to be reconnected.

The command line utility omctool is provided to enable the OMC-R system administrator toforcibly restart a process.

68P02901W19-S 2-49

Oct 2009

Messages in the OMC-R console and audit log Chapter 2: System management

NOTEThis utility should only be used under the direction of Motorola.

Messages in the OMC-R console and audit log

All GUI users will see messages displayed on the console as processes restart. In some cases,operations and/or the entire GUI has to be restarted.

The OMC-R keeps a record of all failed processes in the omcaudit file. The OMC-R systemadministrator can investigate what has gone wrong by examining this file.

NOTEStatistic file uploads are automatically retried.

Process dies

When a process is dying, or has died, the console displays a message similar to the following:

Thu Dec 11 15:04:17 2003 - WARNING: An OMC

Process Has Died. It will be Restarted - NAME

or

Thu Dec 11 15:04:17 2003 - WARNING: An OMC

Process Has Died - NAME

If the process is restartable, then the operator should monitor the console to confirm thatthe process restarts.

If the process is critical, all GUIs will have to be restarted when the OMC restarts. If a GUIrestart is necessary, users are notified that the GUI has been disconnected from the systemprocessor when they try to use it.

The OMC-R system administrator should examine the omcaudit log files. If the logs containseveral regular entries indicating that there is something wrong with the operation of thisprocess, the OMC-R system administrator should attempt to determine the cause.

2-50 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Messages in the OMC-R console and audit log

Process restarts

When a process is restarted, the console displays a message similar to the following:

Thu Dec 11 15:04:18 2003 - NOTE: An OMC Process

Has restarted - NAME

The user should ensure that the process restarts successfully by examining the console.

The OMC system administrator should also examine the omcaudit log to see why the processdied in the first place. The omcaudit file contains an entry similar to the following:

2003-12-11 15:04:18 (20005) [OMCINIT] NAME has restarted

Critical processes start successfully

If critical processes have been started but other processes did not start, the OMC-R systemadministrator should examine the omcaudit log files to determine which processes did notstart and what is wrong with them.

Depending on which processes did not start, certain operations may fail. For example, if RLoginfails to start, then the remote login functionality is unavailable.

System shuts down

When the OMC-R system shuts down the console displays a message similar to the following:

Thu Dec 11 10:10:41 2003 - WARNING: OMC Processes Have Been Shutdown

If the shutdown is due to the death of a critical process rather than an administrator request toshut down, the OMC-R should restart automatically.

Process fails to respond to a periodic health check

The OMCINIT process periodically polls other processes to make sure they have not hung.When a process fails to respond to polling the console shows the following message:

Thu Dec 11 15:53:46 2003 - WARNING: An OMC Process is not

responding to Polling - NAME

If the process is restartable, then only that process is restarted. The OMC-R systemadministrator should check that the process is shut down and restarted, and ensure that thismessage does not continually repeat.

If the process is critical, then the entire OMC-R is shut down and restarted. The OMC-R systemadministrator should check that the OMC-R is restarted and remains up.

68P02901W19-S 2-51

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, GUIs can be restarted.

PM proxy cannot access PM database

If the PM proxy cannot access the PM database, a message similar to the following is displayedon the console:

Thu Dec 11 12:12:16 2003 - WARNING: PMproxy unable to access PM Database

This message is unlikely to appear. If it does appear, report the problem to Motorola.

ResyncCtrl dies during a resync

If the ResyncCtrl process dies, any currently active resyncs are aborted and the process isrestarted. A console message appears, warning that ResyncCtrl has died and is being restarted.

The user may restart aborted resyncs when the ResyncCtrl process restarts.

Event Interface dies

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

Event Interface dies during a resync

If the Event Interface dies, any currently active resyncs will fail because the BSS cannotcommunicate with the OMC-R. The console displays a warning message that the Event Interfacehas died and is being restarted.

The user may restart the failed resync when the Event Interface process restarts.

Event Interface dies during an audit

If the Event Interface dies, any currently active audit is aborted. The console displays a warningmessage that the Event Interface has died and is being restarted.

The user may restart the aborted audit when the Event Interface process restarts.

2-52 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Messages in the OMC-R console and audit log

Uploader dies during an upload

If the uploader dies, current uploads are aborted. The console displays a warning message thatthe uploader has died and is being restarted.

If the uploader dies during an active upload, a message box appears in addition to the consolemessage, warning that the upload IPC channel has been deleted. The upload status windowis closed.

Upload status can be invoked again when the uploader has restarted and any aborted databaseuploads have to be restarted manually. Statistics file uploads will be retried automatically.

Downloader dies during a download

If the downloader dies, a console message appears warning that the downloader has diedand is being restarted.

If a download status window is active, a message box appears to inform the user that thechannel has died and the download status window is closed.

Download status can be invoked again when the downloader has restarted. Unlike uploads,downloads should resume automatically.

Monitor process dies

If the monitor process dies, it terminates its remaining processes and then restarts allprocesses under it. The monitor process itself is restarted by OMCINIT.

GUIs will have to be restarted manually.

A console message appears stating which monitor process has died. A message box alsoappears informing the user that the system processes have died and the GUI should be restartedwhen the processes have been restarted.

When the processes are restarted, a message appears on the console to inform the user. Theuser must then restart the GUI.

Event Manager dies during alarm or event display

If the Event Manager dies due to event overload, this is reported in a console message. Ifalarm or event windows associated with this EM channel are open, they will be closed. TheEvent Manager is a critical process and all the OMC-R processes will shut down as a result ofthis process expiry. The console displays a warning message that the OMCINIT process isshutting down.

After all the processes have been shut down, all OMC-R processes are restarted. A consolemessage appears, informing the user to restart the GUI to reconnect to the OMCINIT process.The user must restart the GUI.

68P02901W19-S 2-53

Oct 2009

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. As with the EM, all the OMC-R processes will shutdown if the EM List Manager critical process fails.The console displays a warning message thatthis process has failed and OMCINIT is shutting down.

After all OMC-R processes have been shut down, all the processes are restarted. A consolemessage appears telling the user to restart the GUI to connect to the OMCINIT process. Theuser must then restart the GUI.

Configuration Manager dies

The Configuration Manager is a critical process. As with the EM, all of the OMC-R processeswill shut down if this critical process fails. A console message will appear warning that thisprocess has died and OMCINIT is shutting down.

After all OMC processes have been shut down, all the processes are restarted. A consolemessage appears telling the user to restart the GUI to connect to the OMCINIT process. Thenthe user must restart the GUI.

OMCINIT process dies

If OMCINIT dies, all processes it has started are shut down. The console displays a warningmessage that the OMCINIT process is down.

A minder application omcminder then restarts OMCINIT. All OMC-R processes are restartedand a console message appears warning that the user must restart the GUI to reconnect to theOMCINIT process. The user must restart the GUI when this message appears.

X.25 processes restart

The X25_BTL1 and X25_BTL2 processes handle downloads. If they die, new downloads willnot be initiated. This corrects itself when the process restarts.

If the X25_EVT1 and X25_EVT2 processes fail, events, audits, and resyncs will fail. When theyrestart, NEs should reconnect again, but the user will have to restart audits and resyncs.

If the X25_UPL1, X25_UPL2, X25_UPL3 or X25_UPL4 processes fail, uploads will beinterrupted. Operator initiated uploads (as opposed to statistics) will have to be restarted.

If the X25_RLOG process fails, remote login sessions will have to be restarted after this processhas restarted.

Console messages will appear warning that the X.25 process has died and is being restarted.

Parser process restarts

If the PARSER process fails and is restarted, stats collection and parsing should resume withoutoperator intervention. A console message appears, warning that the process has died and isbeing restarted.

2-54 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration omctool utility

FCCHAN process restarts

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

FMMGR process restarts

If the FMMGR process fails, it is restarted without operator intervention. A console messageappears warning that this process has died and is being restarted.

Remote login process restarts

If for any reason a remote login process RLogin should die, it will be restarted. A consolemessage will appear warning users that this process has died and is being restarted.

If the RLogin process stops and restarts, current remote login sessions will fail and will needto be retried. The OMC-R system administrator should check for failed batch_rlogin jobs byexamining the output in the /usr/omc/config/global/batch/output log file.

NOTEIf the option to generate log files is selected, only the batch output log file isgenerated.

omctool utility

CAUTIONThe omctool application should only be used by the OMC system administrator underthe direction of Motorola.

The omctool utility can be used to:

• Switch debugging on or off for a process.

• Restart a process.

• Reconfigure a process.

This utility is used with the following options:

omctool [-p pid] | [-m mnemonic] [-d on/off] | [-r] | [-c]

The process to be adjusted must be specified by either:

• Its process ID with the -p option, or

• Its mnemonic name (given in STARTUP.LIST) with the -m option.

68P02901W19-S 2-55

Oct 2009

omctool utility Chapter 2: System management

The action to be taken must be specified by:

• The -r option to restart the process.

• The -c option to reconfigure the process. This causes the OMC.CNFG file to be re-readand therefore does not require the process to be restarted.

• The -d on or -d off option to switch debugging ON or OFF.

The omctool utility should only be used under the direction of Motorola. In particular, the -ddebugging option generates large files and will impair system performance. The informationthat it produces is of use to only Motorola engineers.

2-56 68P02901W19-S

Oct 2009

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 powerand to shut down gracefully during longer power outages.

The system processor can be powered by a Smart Uninterruptible Power Supply (Smart UPS).Supporting software runs on the system processor and a serial cable connected to the UPSdelivers status information to it. Any GUI users are warned when the system processor isswitched over to the UPS. When the UPS battery is close to depletion, a further message is sentto any remaining users. The system is then shut down.

As this feature is optional, the OMC can operate without a UPS installed.

Implementation of graceful shutdown

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

Features of graceful shutdown

The graceful shutdown function provides the following UPS support facilities:

• The OMC can detect UPS events and generate OMC alarms when these events occur.

• The OMC logs UPS events in the system processor audit file.

• If the mains power to the UPS fails, the OMC informs all OMC users through the OMCconsole window. In this case, the OMC will continue to function normally.

NOTEOnly users who are logged into functioning machines are informed.

• When the mains power to the UPS is restored, the OMC informs all OMC usersthrough the OMC console window that a shutdown is no longer pending.

• If the UPS indicates a low battery condition, the OMC will shut down. All userswill be informed that a shutdown is about to occur. Sufficient time is allowed forthis message to reach all active users before the shutdown occurs.

• If the operator issues an omc stop command during OMC startup, the OMCwill shut down.

68P02901W19-S 2-57

Oct 2009

UPS setup Chapter 2: System management

UPS setup

To ensure maximum protection for the OMC, the UPS should be configured so that it will notpower up after restoration of mains power until there is enough battery capacity to completelyreboot and shut down the system processor. This ensures that repeated mains failures do notcause uncontrolled power cuts at the OMC. The system is not powered up until the UPS hassufficient reserves to permit it to power up the OMC completely and then shut it down again ifthe mains supply to the UPS fails during the startup.

2-58 68P02901W19-S

Oct 2009

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. Remoteterminals may be used simply to monitor a regional OMC-R from a remote location, or for thepurpose of night concentration where several OMC-Rs are monitored from one central point.

Single OMC-R monitoring configuration

The following section describes the configuration of a remote SUN terminal. The single OMC-Rmonitoring configuration is illustrated in Figure 2-13. The remote monitoring station is used tomonitor just one regional OMC-R.

Figure 2-13 Single monitoring station configuration

The link protocol between the sites is X.21 which supports the TCP/IP WAN connection. Thebridge or router at the regional OMC-R end may provide several other routes to other routersor bridges at other sites.

The Sunblade 150 at the monitoring station is configured as a GUI server so that the OMC-Rsoftware executes locally. The same users must be added on the GUI server as are added at theregional OMC-R. The remote Sunblade 150 must still NFS mount the /usr/omc/config/global,/usr/omc/ne_data, /usr/omc/ne_data/raw_stats and /home.

68P02901W19-S 2-59

Oct 2009

OMC-R night concentration centre configuration Chapter 2: System management

OMC-R night concentration centre configuration

For large systems that contain multiple OMC-R networks, it is necessary that an operator beable to hand over management of one network region to another OMC-R during the night shift.

This necessitates the provision of a mechanism to enable single workstation access to multiplesystem processors.

Figure 2-14 shows a configuration where the night concentration centre consists of oneSunblade 150 configured as a GUI server for both region A and region B.

Figure 2-14 Night concentration centre configuration

2-60 68P02901W19-S

Oct 2009

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.One of these is the operators local OMC-R system. The others are remote OMC-R systemsthat are normally monitored at night.

• Access to the OMC-R systems is mutually exclusive. The operator has to log out and loginagain as a different user to gain access to the remote OMC-R. The remote OMC-R thatthe operator accesses, depends on the user that the operator logs in as. Each specialuser accesses a specific remote OMC-R which is specified during initial set-up of thenight concentration feature.

• Night concentration procedures do not support the use of NIS.

• The GUI server used for this feature is unable to support any clients.

• A minimum 64 KB digital leased line is required to run the OMC remotely.

Naming conventions for a night concentration centre

The following naming conventions are used when describing the setup of a night concentrationcentre:

• local_sys: The hostname of the local system processor.

• remote_sys: The hostname of the remote system processor.

• local_gui: The hostname of the local GUI server processor.

• remote_user: The username of the account used to access the remote OMC-R.

Prerequisites for setup of a night concentration centre

The following procedures must be completed before commencing the setup of a nightconcentration centre.

• The local and remote OMC-R systems must have version GSR9 of the OMC-R softwareinstalled. Refer to Installation and Configuration: OMC-R Clean Install (68P02901W47)for details.

• The hostname and IP addresses of the different processors must be obtained for eachremote OMC-R. It is recommended that the information be entered in Table 2-3 andTable 2-4.

68P02901W19-S 2-61

Oct 2009

Prerequisites for setup of a night concentration centre Chapter 2: System management

Table 2-3 Hostname and IP addresses for different processors

System Hostname IP address

local_sys

remote_sys

local_gui

• The Username and User Identifier Number (UID) from the account of the user of theremote OMC-R system must be obtained. It is recommended that the information beentered in Table 2-4.

Table 2-4 User name and ID for remote system

Account User name UID

Account for user of remoteOMC-R system.

NOTECopies of the above tables are provided in Chapter 13. They can be copiedand used to record this information.

2-62 68P02901W19-S

Oct 2009

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. Thefollowing procedures are outlined:

• Updating host file entries.

Describes how to change host file entries.

• Exporting file changes.

Describes how to mount certain file systems.

• Creation of a new account.

Describes how to create an account to use the remote OMC-R.

Updating host file entries

Each of the remote system processors must contain the hostname of the local GUI server in itshost file, equivalent hosts file, and rhosts file. Use the following procedure to change the files:

Procedure 2-23 Updating host file entries with hostname

1 Edit the /etc/hosts file on the remote_sys processor and check thatthe hostname of the local_gui processor is present. If the entry isnot listed, add a line similar to the following to the hosts file using asuitable text editor:<IP address> <local_gui>Where:<IP>is IP address of GUI server<local_gui> is Hostname of the local GUI server.

2 Edit the /etc/hosts.equiv file on the remote_sys processor and checkthat the hostname of the local_gui processor is present. If the entryis not listed, add a line similar to the following to the hosts.equiv fileusing a suitable text editor:Where:<local_gui> is Hostname of the local GUI server.

3 Once all changes have been made, execute the following commands asuser root:cd /var/yp/usr/ccs/bin/make

68P02901W19-S 2-63

Oct 2009

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 thelocal GUI server to mount certain file systems:

Procedure 2-24 Setting mount permissions at the GUI server

1 Edit the /etc/dfs/dfstab file on each of the remote_sys processors andadd the hostname of the local_gui processor to the list of hosts withmount permissions:

share -F nfs -o rw=sparc0:<local_gui>,root=sparc0:<local_gui>/homeshare -F nfs -o rw=sparc0:<local_gui>,root=sparc0:<local_gui>/usr/omc/ne_datashare -F nfs -o rw=sparc0:<local_gui>,root=sparc0:<local_gui>/usr/omc/config/globalshare -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.

2 Execute the following command on each of the remote systemprocessors, as user root:shareall

Creation of new account

An account must be created to use the remote OMC-R. The account is also created on theremote_sys processors with the same username and UID as that created on the local machine.

2-64 68P02901W19-S

Oct 2009

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 requirementsmust be fulfilled:

• Each system processor on the LAN must be a NIS master (this is standard under thecurrent supported OMC-R configuration).

• The NIS Domain name on each OMC-R on the LAN must be unique.

• The maps for each NIS Domain must contain a complete list of all system processorhostnames on the LAN.

• Ensure that the Remote system processor is NFS-sharing the following file systems tothe 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,/etc/hosts.equiv.

• The Remote system processor must have an entry for the GUI server in each of /etc/hosts,/etc/hosts.equiv.

68P02901W19-S 2-65

Oct 2009

Switching to an alternative OMC-R 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 runningon the GUI server.

2 Initially, the GUI server /etc/hosts file should be similar to the following:

127.0.0.1 localhost111.111.11.12 local_gui111.111.111.11 local_sys omc_splat omc_pm omc_4gl111.111.11.14 netprinter111.111.11.13 guiclient1111.111.111.21 remote_sys

Edit the GUI server /etc/hosts file so that the remote_sys is aliased toomc_splat, omc_pm and omc_4gl:

127.0.0.1 localhost111.111.11.12 local_gui111.111.111.11 local_sys111.111.11.14 netprinter111.111.11.13 guiclient1111.111.111.21 remote_sys omc_splat omc_pm omc_4gl

3 To switch over to an alternative OMC-R, execute the followingcommand:

/usr/omc/current/sbin/SwitchSPLAT <remote_sys>

Where:

<remote_sys> is the hostname of the Remote system processor.

NOTEThe GUI server reboots automatically.

2-66 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Removing OMC-R night concentration centre configuration

Removing OMC-R night concentration centreconfiguration

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Introduction

The procedures in this section describe how to undo the OMC-R night concentration centreconfiguration. The procedures listed in Table 2-5 are outlined.

Table 2-5 Procedures to remove OMC-R night concentration configuration

Procedure Description

Local GUI server rollback Describes the GUI server file modifications required whenremoving the OMC night concentration centre configuration.

Remote system processorrollback

Describes the Remote system processor file modificationsrequired when removing the OMC night concentration centreconfiguration.

Local GUI server rollback

This section describes the GUI server file modifications which must be made when removing theOMC-R night concentration centre configuration.

The following procedures are described:

• Deletion of the OMC-R remote user account.

• Host file changes.

Deletion of OMC-R remote user accounts

Refer to Administering user accounts with usertool on page 2-12 for details on administeringuser accounts.

Hostfile changes

Remove references to the remote system processor from /etc/hosts, /etc/hosts.equiv.

68P02901W19-S 2-67

Oct 2009

Remote system processor rollback Chapter 2: System management

Remote system processor rollback

This section describes the Remote system processor file modifications which must be madewhen removing the OMC-R night concentration centre configuration. The following files mayhave been changed on the Remote system processor:

/etc/dfs/dfstab /etc/hosts.equiv /etc/hosts

The following procedures are outlined:

• Export file changes.

• Deletion of the OMC-R remote user account.

Export file changes

Edit the /etc/dfs/dfstab file on each of the remote_sys processors. Remove the referenceto the local_gui processor.

Deletion of OMC-R remote user accounts

Refer to Administering user accounts with usertool on page 2-12 for details on administeringuser accounts.

2-68 68P02901W19-S

Oct 2009

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 Changing the locale of OMC-R

1 Execute the following command as user root to display all the supportedlocales:locale -a

Sample out put:POSIXCiso_8859_1zh_HK.BIG5HKzh_HK.BIG5HK@radicalzh_HK.BIG5HK@strokezh_HK.UTF-8zh_HK.UTF-8@radicalzh_HK.UTF-8@strokezh_TW zh_TW.BIG5zh_TW.EUCzh_TW.UTF-8jaen_AUen_AU.ISO8859-1en_NZen_NZ.ISO8859-1iso_8859_13iso_8859_15iso_8859_2iso_8859_5eses_CRes_CR.ISO8859-1es_GTes_GT.ISO8859-1..iso_8859_7iso_8859_9hi_IN.UTF-8cs_CZcs_CZ.ISO8859-2czdede.ISO8859-15

Continued

68P02901W19-S 2-69

Oct 2009

Setting the locale on the OMC-R Chapter 2: System management

Procedure 2-26 Changing the locale of OMC-R (Continued)

de.UTF-8de_ATde_AT.ISO8859-1de_AT.ISO8859-15de_AT.ISO8859-15@eurode_CH..de_DE.ISO8859-15@eurode_DE.UTF-8de_DE.UTF-8@eurofrfr_CHfr_CH.ISO8859-1huhu_HUhu_HU.ISO8859-2pl..

commonzhzh.GBKzh.UTF-8..bg_BGbg_BG.ISO8859-5et_EEet_EE.ISO8859-15hr_HRhr_HR.ISO8859-2..lv_LV.ISO8859-13mk_MKmk_MK.ISO8859-5nrro_ROro_RO.ISO8859-2ru..ru_RU.ISO8859-5ru_RU.KOI8-Rru_RU.UTF-8sh_BA.ISO8859-2@bosniasl_SI

Continued

2-70 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Setting the locale on the OMC-R

Procedure 2-26 Changing the locale of OMC-R (Continued)

.

.trtr_TRtr_TR.ISO8859-9tr_TR.UTF-8en_US.UTF-8koko.UTF-8ko_KR.EUCko_KR.UTF-8hehe_ILhe_IL.UTF-8ar..en_US.ISO8859-15en_US.ISO8859-15@euroes_MXes_MX.ISO8859-1fr_CAfr_CA.ISO8859-1dada.ISO8859-15da_DKda_DK.ISO8859-1da_DK.ISO8859-15..nono_NOno_NO.ISO8859-1@bokmalno_NO.ISO8859-1@nynorskno_NYsvsv.ISO8859-15sv.UTF-8sv_SEsv_SE.ISO8859-1sv_SE.ISO8859-15sv_SE.ISO8859-15@eurosv_SE.UTF-8sv_SE.UTF-8@euroes_ARes_AR.ISO8859-1es_BOes_BO.ISO8859-1es_CL

Continued

68P02901W19-S 2-71

Oct 2009

Setting the locale on the OMC-R Chapter 2: System management

Procedure 2-26 Changing the locale of OMC-R (Continued)

.

.es_UYes_UY.ISO8859-1es_VEes_VE.ISO8859-1pt_BRpt_BR.ISO8859-1caca_ESca_ES.ISO8859-1ca_ES.ISO8859-15..es.ISO8859-15es.UTF-8es_ESes_ES.ISO8859-1es_ES.ISO8859-15es_ES.ISO8859-15@euroes_ES.UTF-8es_ES.UTF-8@euroitit.ISO8859-15it.UTF-8it_ITit_IT.ISO8859-1it_IT.ISO8859-15it_IT.ISO8859-15@euroit_IT.UTF-8it_IT.UTF-8@europtpt.ISO8859-15pt_PTpt_PT.ISO8859-1pt_PT.ISO8859-15pt_PT.ISO8859-15@eurothth_THth_TH.ISO8859-11th_TH.TIS620th_TH.UTF-8..fr_BE.UTF-8fr_BE.UTF-8@eurofr_FRfr_FR.ISO8859-1fr_FR.ISO8859-15

Continued

2-72 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Setting the locale on the OMC-R

Procedure 2-26 Changing the locale of OMC-R (Continued)

fr_FR.ISO8859-15@eurofr_FR.UTF-8fr_FR.UTF-8@euronlnl.ISO8859-15nl_BEnl_BE.ISO8859-1nl_BE.ISO8859-15nl_BE.ISO8859-15@euronl_NLnl_NL.ISO8859-1nl_NL.ISO8859-15nl_NL.ISO8859-15@euroar_SA.UTF-8el_GR.UTF-8pt_PT.UTF-8nl_BE.UTF-8nl_NL.UTF-8

2 As user root, edit the /etc/default/init file and add your chosen locale.

For example:# @(#)init.dfl 1.5 99/05/26## This file is /etc/default/init. /etc/TIMEZONE is a symlink tothis file.# This file looks like a shell script, but it is not. Tomaintain# compatibility with old versions of /etc/TIMEZONE, some shellconstructs# (i.e., export commands) are allowed in this file, but areignored.## Lines of this file should be of the form VAR=value, where VARis one of# TZ, LANG, CMASK, or any of the LC_* environment variables.#TZ=EireCMASK=022LANG=no_NO#

3 As user root, reboot the box by executing the following command:/usr/sbin/shutdown -g0 -i6 -y

68P02901W19-S 2-73

Oct 2009

General administration checklists Chapter 2: System management

General administration checklists■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Daily administration checklist

Use the following procedure to perform the daily administration tasks. Copy the checklistprovided in Chapter 13 to record the checks.

NOTEThese procedures must be executed by an experienced Systems Administrator.

Procedure 2-27 Performing daily administration tasks – initial checks

1 Check the file system capacity:As user root, execute the following command:df -kEnsure that all necessary file systems are mounted, and that thecapacity does not exceeded 90%. If the file system exceeds 90%, it isadvisable that the file system is cleaned up.

2 Check the disk usage capacity of the system: by entering the followingcommand as user root:du | moreTerminate processes that are not required and are unnecessarilyconsuming disk capacity. Also use the output of this command to checkfor rogue processes running on your system.

3 Check the output of cron jobs from users root, omcadmin, and sys.As user root examine the output from the cron jobs in the followingfiles for errors/messages:more /var/mail/omcadminmore /var/mail/rootmore /var/mail/sysInvestigate the cron jobs that appear to be troublesome.

4 Check the omc_db_maint log file to ensure that:

• PM statistics are unloaded and deleted successfully.

• Disk space is not being consumed.

• Applications are connected and reconnected successfully.

• PM Fragments are created for the next days statistics.

As user root execute the following commands:cd $OMC_TOP/logsmore omc_db_maint.yyyy.mm.dd

Continued

2-74 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Daily administration checklist

Procedure 2-27 Performing daily administration tasks – initial checks (Continued)

5 Check the IDS log files for both PM and MIB INFORMIX DB errors andcheckpointing:As user omcadmin execute the following commands:tail -f $INFORMIXDIR/online.log_OMCtail -f $INFORMIXDIR/online.log_MIBThese log files should show that checkpoints are completed successfullyand in particular when the server is initialized.

6 Check that the PM database is online by entering the followingcommands as user omcadmin:omc_envonmonitor

7 Check that the CM database is online by entering the followingcommands as user omcadmin:mib_envonmonitor

Procedure 2-28 Performing daily administration tasks – creating backups

1 Perform a Level 2 backup of the PM database.

2 Perform a Level 2 backup of the CM database.

3 Perform a backup of the UNIX file system.Refer to Chapter 12 Backup Server Installation and Configuration.

4 Check the status of the disk mirroring and ensure that all sub-mirrorsare in an Okay state, by entering the following commands as user root:metastat | moreRefer to Checking disk mirroring on page 13-47.

5 Check the OMC-R log files in /usr/omc/logs for unusual output or errormessages. Refer to OMC-R log and error files on page 4-3.

6 Check the integrity of X.25, by entering the following commands asuser root:/opt/SUNWconn/bin/x25statRefer to x25stat output on page 2-76.

7 Check the system processor hardware, by entering the followingcommand as user root:/usr/platform/sun4u/sbin/prtdiag -v

8 Manually parse any unparsed statistics files. Refer to the ChecklistManual parsing of statistics in NE database maintenance on page 2-30.

68P02901W19-S 2-75

Oct 2009

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 138 10

Call accept 7 128

Clear 129 16

Clear Confirm 16 129

Restart 0 1

Restart confirm 1 0

RNR 0 0

RR 1119 12536

Resets 1 0

Reset confirms 0 1

Diagnostic 0 0

Interrupts 0 0

Registration 0 0

Reg confirm 0 0

Packets (total) 18126 3124

Bytes (total) 1783971 207183

-------------------------------------

Running totals

-------------------------------------

Tot no of VCs established 135

Connections refused 0

Connections currently open 3

Max connections open 7

2-76 68P02901W19-S

Oct 2009

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

--- --- ------- ----- ------ ------ ----

3 6 0 400 8.0 US-II 10.0

3 7 1 400 8.0 US-II 10.0

7 14 0 400 8.0 US-II 10.0

7 15 1 400 8.0 US-II 10.0

=========================Memory =========================

Intrlv. Intrlv. Brd Bank MB Status Condition Speed Factor With

--- ---- -- ------ --------- ----- ------ -----

3 0 256 Active OK 60ns 2-way A

7 0 256 Active OK 60ns 2-way A

========================= IO Cards =========================

Bus Freq Brd Type MHz Slot Name Model

--- ---- ---- ---------- ---------------------------- --------------------

1 SBus 25 0 cgsix SUNW,501-2253

1 SBus 25 1 HSI SUNW,501-1725-01

1 SBus 25 3 SUNW,hme

1 SBus 25 3 SUNW,fas/sd (block)

1 SBus 25 13 SUNW,socal/sf (scsi-3) 501-3060

5 SBus 25 1 HSI SUNW,501-1725-01

5 SBus 25 3 SUNW,hme

5 SBus 25 3 SUNW,fas/sd (block)

5 SBus 25 13 SUNW,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 YELLOW GREEN Normal

ON OFF BLINKING

Fans:

-----

Unit Status

68P02901W19-S 2-77

Oct 2009

Daily administration checklist Chapter 2: System management

---- ------

Disk OK

PPS OK

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.3v OK

System 5.0v OK

Peripheral 5.0v OK

Peripheral 12v OK

Auxilary 5.0v OK

Peripheral 5.0v precharge OK

Peripheral 12v precharge OK

System 3.3v precharge OK

System 5.0v precharge OK

AC Power OK

=========================HW Revisions =========================

ASIC Revisions:

---------------

Brd FHC AC SBus0 SBus1 PCI0 PCI1 FEPS Board Type Attributes

--- --- -- ----- ----- ---- ---- ---- ---------- ----------

1 1 5 1 1 22 Dual-SBus-SOC+ 100 MHz Capable

3 1 5 CPU 100 MHz Capable

5 1 5 1 1 22 Dual-SBus-SOC+ 100 MHz Capable

7 1 5 CPU 100 MHz Capable

System Board PROM revisions:

----------------------------

Board 1: FCODE 1.8. 7 1997/12/08 15:39 iPOST 3.4. 8 1999/02/19 14:25

Board 3: OBP 3.2.21 1999/02/19 14:33 POST 3.9.10 1999/02/19 14:23

2-78 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Weekly administration checklist

Board 5: FCODE 1.8. 7 1997/12/08 15:39 iPOST 3.4. 8 1999/02/19 14:25

Board 7: OBP 3.2.21 1999/02/19 14:33 POST 3.9.10 1999/02/19 14:23

Weekly administration checklist

Use the following procedure to perform the weekly administration tasks. Copy the checklistprovided in Chapter 13 to record the checks.

Procedure 2-29 Performing weekly administration tasks

1 Check that the Informix online logs are rolled over successfully, byentering the following commands as user omcadmin:cd /usr/informixls -l online.log_MIBls -l online.log_OMCEnsure that online logs exist in the following format:online.log_MIB.ddmmyyyyonline.log_OMC.ddmmyyyy

2 Perform a backup of the UNIX file system.Refer to Chapter 12 Backup Server Installation and Configuration.

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

4 Archive and remove unloaded PM database files on the systemprocessor by entering the following commands as user root:maintain_script -a -d 7 -t /dev/rmt/0/usr/omc/ne_data/raw_stats parsed\*This will archive raw statistical bad header files older than seven days.maintain_script -r -d 7 /usr/omc/ne_data/raw_stats parsed\*This will remove raw statistical bad header files older than seven daysafter they have been archived.

5 Check the file system capacity by entering the following commands asuser root:df -k

6 Check the disk usage capacity of the system by entering the followingcommands as user root:du |moreTerminate processes that are not required and are consuming diskcapacity.

7 Perform an archive of old OMC-R user files by entering the followingcommands as user root:find /home -mtime +14 -print > /usr/tmp/listingtar -c / usr/tmp/listing /dev/rmt/0

8 Perform a Level 1 backup of the PM database.

9 Perform a Level 1 backup of the CM database.

Continued

68P02901W19-S 2-79

Oct 2009

Monthly administration checklist Chapter 2: System management

Procedure 2-29 Performing weekly administration tasks (Continued)

10 System security should be monitored by the system administrator.Refer to Security overview on page 2-36 for further details aboutimportant security aspects.

Monthly administration checklist

Use the following procedure to perform the monthly administration tasks. Copy the checklistprovided in Chapter 13 to record the checks.

Procedure 2-30 Performing monthly administration tasks

1 Perform a backup of the UNIX file system. Refer to Chapter 12 BackupServer Installation and Configuration.

2 Perform a Level 0 backup of the PM database.

3 Perform a Level 0 backup of the CM database.

4 Change the standard installation passwords for user root, omcadmin,and informix, and inform the required users. Refer to Administeringuser accounts with usertool on page 2-12.

5 Truncate the cron log file, by entering the following command as userroot:tail -100 /var/cron/log > /tmp/cron_log mv /tmp/cron_log/var/cron/log

2-80 68P02901W19-S

Oct 2009

Chapter

3

Ancillary Devices■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

68P02901W19-S 3-1

Oct 2009

Overview Chapter 3: Ancillary Devices

Overview■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This chapter contains installation, configuration, and troubleshooting information for OMC-Rancillary devices.

The following topics are described in this chapter:

• Configuring the serial port with Serial Port Manager on page 3-3.

• Introduction to modem installation on page 3-7.

• Troubleshooting the modem on page 3-19.

• Adding a printer on page 3-25.

3-2 68P02901W19-S

Oct 2009

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 forterminals and modems. Using the Serial Port Manager to configure serial port software allowsthe system administrator to set up terminals and modems without having to manually edit andcreate the necessary files. It features the following operations:

• Templates for common terminal and modem configurations.

• Multiple port setup, modification, or deletion.

• Quick visual status of each port.

The following procedures are outlined in this section:

• Adding a modem.

• Setting an additional baud rate.

• Installing a modem.

• Testing the modem installation procedure.

NOTEA modem cannot be connected to the SunFire 4800.

Accessing Serial Port Manager

Use the following procedure to access the Serial Port Manager.

Procedure 3-1 Accessing the Serial Port Manager

1 Login to the system processor as root.

2 Click on the system administration icon.

3 Select the Port Manager option.

68P02901W19-S 3-3

Oct 2009

Serial Port Manager parameters Chapter 3: Ancillary Devices

Serial Port Manager parameters

The following functions can be handled using the Serial Port Manager.

Template

This field specifies the preconfigured template used to configure the port from the pull downmenu. The following templates are available:

• Terminal - Hardwired:

Users may log in through a terminal directly connected to the system.

• Modem - Dial In Only:

Users may dial in to the modem but cannot dial out.

• Modem - Dial Out Only:

Users may dial out from the modem but cannot dial in.

• Modem - Bidirectional:

Users may either dial in or out from the modem.

• Initialize Only - No Connection:

The port service is initialized but not configured. Use this to initialize the port connectionwithout actually connecting a device to the port.

Detail

The Modify window provides information about the port in three levels: Basic, More, and Expert.These levels of detail are called modes. Basic detail mode is displayed by default. The Detailcommand buttons at the top of the window are used to display the other modes. The More andExpert modes each show progressively more configuration data and controls.

Basic detail

• Port:

Lists the port selected from the Serial Port Manager main window.

• Service:

Specifies that the service for the specified port is turned on.

• Baud Rate:

Specifies the line speed used to communicate with the device.

• Terminal Type:

Specifies the terminal type connected to the port.

3-4 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Serial Port Manager parameters

More detail

• Initialize Only:

Specifies that the port software is initialized but not configured.

• Bidirectional:

Specifies that the port line is used in both directions.

• Software Carrier:

Specifies that the software carrier detection feature is used. If this option is not checked,the hardware carrier detection signal is used.

• Login Prompt:

Shows the prompt after a connection is made.

• Comment:

Shows a text description of the service, if any.

• Service Tag:

Shows the service tag associated with this port.

• Port Monitor Tag:

Specifies the port monitor name to be used for this port.

Expert detail

• Create utmp Entry:

Specifies that a utmp entry is created upon login. This item must be checked if a loginservice is used.

• Connect on Carrier:

Specifies that a ports associate service is immediately invoked when a connect indication isreceived.

• Service:

Shows the program that is run upon connection.

• Streams Modules:

Shows the streams modules that are pushed before the service is started.

• Timeout:

Specifies the number of seconds before a port is closed if the open process on portsucceeds and input data is not received.

68P02901W19-S 3-5

Oct 2009

Adding a modem Chapter 3: Ancillary Devices

Adding a modem

Use the following procedure to add a modem.

Procedure 3-2 Adding a modem

1 In the Serial Port Manager main window, select the port that is to beused with a modem.

2 From the Edit menu, select Modify. The Modify window appears inBasic Detail mode.

3 Choose the modem configuration that closely matches the modemservice from the Template menu. Refer to Serial Port Managerparameters on page 3-4 for descriptions of each field in the window.

4 Change the values of the template entries as required.

5 Click OK to configure the port.

Setting an alternative baud rate

The following procedure describes the user of other option to select a baud rate that doesnot appear on the Baud Rate menu.

Procedure 3-3 Setting an alternative baud rate

1 Select Other from the Baud Rate menu.

2 Enter a baud rate entry from the /etc/ttydefs file that provides sevenbits, even parity service.

3 Click OK.

3-6 68P02901W19-S

Oct 2009

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 Microsystemsplatform running Solaris 10 with CDE. Any serial port modem is supported.

The modem is configured for both dial-in and dial-out access.

Background information

The modem can be used for remote access to the OMC-R (dial-in to the OMC-R) and also foraccessing external computer systems from the OMC-R (dial-out from the OMC-R).

Remote access to the OMC-R through a modem can provide TTY (character based) access to theOMC-R. It does not provide a method to remotely access the graphical functions of the OMC-R.If a remote OMC-R operator terminal is required, it should be connected to the OMC-R usingLAN routers over a synchronous link operating at speeds of at least 64 kbps.

Support engineers make use of remote access to diagnose and rectify problems.

NOTEThe procedures described here may conflict with other programs or serial port users.Connect the modem to an unused port or disable the port monitor services.

Data links

When connecting two platforms with modems, there are three data links present.

Figure 3-1 Data links between two platforms

68P02901W19-S 3-7

Oct 2009

Rates Chapter 3: Ancillary Devices

Rates

Data is transferred at the same rate as the slowest link. The modems may use data compressionon the DCE link. This is helpful if the DCE link is the slowest link.

In the following example, data compression on the DCE link could, in theory, make the DCE linkappear to operate at 20+ kbps. The bottleneck would then be the remote DTE rate (19.2 k).

• Local DTE rate = 38.4 kbps.

• DCE rate = 9.6 kbps.

• Remote DTE rate = 19.2 kbps.

The Motorola 3460 Fast'R modem contains various security features to restrict or preventaccess. Password protection and other security features are described in the modem user guide.

Physical connection

Install the modem on the SPARCstation, using either ttya or ttyb (serial port A or B), and makesure that the RS232 cable is a straight-through cable. Any 20 to 25-pin cable is acceptablealthough only pins 1 to 8 and pin 20 are necessary.

NOTEDo not use a null modem cross-over cable or a null modem gender adapter cable.

While using a system which shares ports A and B, such as the platform 10, and if port B is to beused for the modem port, use the splitter cable (port A can be accessed directly without thesplitter). This splitter cable is available from SunExpress (part number: X985A or 530-1869/C9).

Initial modem setup

NOTEThe root password is required to install or modify files for modem installation.

The initial platform setup involves the two activities mentioned as follows:

• Defining the dial-in serial port characteristics.

• Verifying port monitor services.

3-8 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Initial modem setup

Define dial-in serial port characteristics

Add the following entries to the /etc/ttydefs file. These are the serial port characteristicspresented 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 tomatch hardware flow control at the modem. Also, the above definition uses eight data bits withno parity transfers.

NOTE14400 baud and 28800 baud rates are the modem to modem speeds and 19200 baudand 38400 baud are the speeds the modem uses to communicate with the serialport. Modem to serial port speeds should be faster than modem to modem speeds inorder to prevent bottlenecks.

Verify current port monitor services

Verify that there are no port monitor services on the port to be connected to the modem, bytyping the following command on the platform as user root.

pmadm -p zsmon -l

An example output is:

PMTAG PMTYPE SVCTAG FLGS ID <PMSPECIFIC>

The following two lines are displayed as one line on the screen:

zsmon ttymon ttya u root /dev/term/a - -

/usr/bin/login - 9600 ldterm, ttcompat login: - vt100 y #Terminal

Also, the following two lines are displayed as one line on the screen:

zsmon ttymon ttyb u root /dev/term/b - -

/usr/bin/login - 9600 ldterm, ttcompat login: - vt100 y #Terminal

If there are services present, as indicated in the output displayed, remove them by typing thefollowing command on the platform as user root.

ipmadm -p zsmon -r -s <SVCTAG value from the above,that is ttya or ttyb>

This can also be achieved by using the serial port manager available under CDE when logged inas root, and selecting Delete or Disable for the port.

The login services need to be removed or disabled before a new ttydefs entry can be used.

68P02901W19-S 3-9

Oct 2009

Communicating with the modem Chapter 3: Ancillary Devices

Communicating with the modem

Once the port monitor services have been deleted or disabled, enter the following command onthe platform as user root.

NOTEEnsure that tip is executed in a shell without scrolling enabled, otherwise a carriagereturn is not sent.

tip -38400 /dev/cua/a

(38400 sets the connection speed, /a assumes ttya. For ttyb, use /b).

Verify that the modem is responding to commands. After the connect message type:

AT

An OK prompt is returned.

If an OK prompt is not returned, try a different port or cable. Ensure that the modem respondsto AT command before continuing with the subsequent sections.

Configuring tip

NOTEAlways use the same speed to tip to the modem as the login process is set to use. Thefollowing procedure assumes that the modem is to be connected using port b. If themodem is to be connected using port a, alter the procedure accordingly.

Use the following procedure to configure the tip utility by modifying the /etc/remote file:

Procedure 3-4 Configuring the tip utility

1 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

Operating Information: OMC-R System Administration Controlling modem access

Procedure 3-4 Configuring the tip utility (Continued)

NOTEWhen using a 28.8 k modem, use 38400; for a 14.4 k modemuse 19200, and for a 9600 modem, use 9600.

2 Change the permissions and the owner of the modem port.For port a:

chmod 666 /dev/cua/a; chown uucp /dev/cua/a

For port b:

chmod 666 /dev/cua/b; chown uucp /dev/cua/b

3 After modifying the /etc/remote file and changing the permissions ofthe ports, use tip by entering the following command at the # prompt:tip modem

A connected message should be displayed. If not, check the /etc/remote file for errorsto the modem entry.

Controlling modem access

Control the modem communication by setting the permissions of the tip utility.

To allow only root users the ability to log out using the modem, set the tip permissions to 700by entering the following command on the platform as user root.

chmod 700 /usr/bin/tip

NOTEChanging the permissions of tip may affect other users or programs that need to usetip, for example, the OMC-R Test Mobile feature.

Modem setup and Initialization

The modem is set up using Hayes AT commands. Once the modem is set up, the configurationcan be stored in the non-volatile memory in the modem. It should only be necessary to configurethe modem once, even if power is lost. See the modem users guide for a complete list of theHayes command set.

68P02901W19-S 3-11

Oct 2009

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 moredetails on modems, refer to the modem documents that accompany the modem.

Procedure 3-5 Configuring the Motorola 3460 and 326X modems

1 At the OK prompt, enter the correct AT command for the modem typeand DTE rate (Table 3-1).The AT command configures the modem and stores the setup in thenon-volatile memory.

2 After setting up the modem, exit the tip utility by typing a carriagereturn followed by a tilde (~) character which is followed by a period(.) character.

Table 3-1 Modem initialization commands

Modem type DTE rate Initialization command

Motorola3460

38400 AT&FQ2*DE19*FL3&D2&C1*CL0S0=2&Y1&W1

19200 AT&FQ2*DE12*FL3&D2&C1*CL0S0=2&Y1&W1

9600 AT&FQ2*DE8*FL3&D2&C1*CL0S0=2&Y1&W1

Motorola326X

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

NOTEThe syntax of the AT commands is specified in the Motorola 3460 Fast'R User Guide.

Description of AT commands used in the initialization string

The syntax of the AT command is as follows:

AT&FQ2*DE15*FL3&D2&C1*AA2&Y&W1

The syntax is explained in Table 3-2.

Table 3-2 Syntax of the AT command

Symbol Meaning Notes

AT Enter command mode.

&F ResetModem to defaultfactory settings.

The four factory default option sets are restored totheir original settings; all stored telephone numbersare deleted.

Continued

3-12 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Configuring the Serial Port Modem

Table 3-2 Syntax of the AT command (Continued)

Symbol Meaning Notes

Q2 RsltCode = Orig. Result codes are output to the DTE when operatingas an originating modem.

DE Fix DTE rate. *DE15 sets a DTE rate of 38400.*DE12 sets a DTErate of 19200.*DE8 sets a DTE rate of 9600.

*FL3 Flow Control =RTS/CTS.

&D2 DTR Control = Discon. The modem hangs up and enters the commandmode when an on-to-off DTR transition is detected,while the modem is in data, test, or escape mode. IfDTR is low, the modem does not auto answer. Thiscommand determines how the modem interpretsthe DTR signal. The local DTE uses DTR (pin 20) tosignal the modem.

&C1 DCD Control = Normal. Normal DCD is off during dialing and also whilethe modem is in training with the remote modem.DCD is on in data mode. It is off when the modemis disconnected from the telephone line. Thisdetermines how the modem sets DCD signals. Themodem signals the DTE with DCD on EIA/TIA 232-DPin 8 (V.24 Circuit 109).

*AA2 Answer = Ring #2. The modem will answer incoming calls after tworings (*AA2) or after X rings where X is defined inthe S0 register (S0=X). Check specific in countryrequirements regarding auto-answer modems.

&Y1 Power Up In = 1. When the modem is powered up, it automaticallyuses option set 1.

&W1 Save Changes = 1. See the paragraph Saving changes.

Saving changes

When using AT commands or front panel options to alter the modem settings, if the changes arenot saved, the modem does not enter them into memory. After selecting the option set mostsuited to the application (using the ATZn command), and modifying any required configurationsettings, enter the following:

AT&W<n>

Where is

<n> a value between 1 to 4, determined by the option set where thenew customized option set is saved.

The modem front panel displays Saving options. After a few seconds, the front panel displaysSave Completed, signifying that the option set has been successfully saved in the non-volatilememory of the modem.

68P02901W19-S 3-13

Oct 2009

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 appropriatecountry configuration:

Procedure 3-6 Setting country configuration

1 Execute the following command to load the factory settings as activeconfiguration:AT&F0

2 Execute the following command to set the country code:AT%T19,0,nn

Where:nn is the Country Code (Table 3-3).

3 Execute the following command to save as factory default:AT&F&W

4 Execute the following command to display the Result Codes and toverify the correct country has been configured (Table 3-3):ATI9

Country Code and Result Code

Table 3-3 specifies the correct AT command and Result Code for each country.

Table 3-3 AT commands and result codes for country-specific modem configuration

Country AT command (hexadecimal) Result Code (decimal)

Argentina AT%T19,0,34 52

Australia AT%T19,0,01 1

Austria AT%T19,0,34 52

Belgium AT%T19,0,34 52

Brazil AT%T19,0,34 52

Canada AT%T19,0,34 52

China AT%T19,0,34 52

Cyprus AT%T19,0,34 52

Czech Republic AT%T19,0,25 37

Denmark AT%T19,0,34 52

Finland AT%T19,0,34 52

France AT%T19,0,34 52

Continued

3-14 68P02901W19-S

Oct 2009

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)

Country AT command (hexadecimal) Result Code (decimal)

Germany AT%T19,0,34 52

Greece AT%T19,0,34 52

Hong Kong AT%T19,0,30 48

Hungary AT%T19,0,30 48

Iceland AT%T19,0,34 52

India AT%T19,0,30 48

Indonesia AT%T19,0,30 48

Ireland AT%T19,0,34 52

Italy AT%T19,0,34 52

Japan AT%T19,0,10 16

Korea AT%T19,0,30 48

Liechtenstein AT%T19,0,34 52

Luxembourg AT%T19,0,34 52

Mexico AT%T19,0,34 52

Netherlands AT%T19,0,34 52

New Zealand AT%T19,0,09 9

Norway AT%T19,0,34 52

Philippines AT%T19,0,30 48

Poland AT%T19,0,30 48

Portugal AT%T19,0,34 52

Russia AT%T19,0,34 52

Singapore AT%T19,0,30 48

South Africa AT%T19,0,35 53

Slovak Republic AT%T19,0,34 52

Slovenia AT%T19,0,30 48

Spain AT%T19,0,34 52

Sweden AT%T19,0,34 52

Switzerland AT%T19,0,34 52

Turkey AT%T19,0,34 52

U.K. AT%T19,0,34 52

United States AT%T19,0,34 52

68P02901W19-S 3-15

Oct 2009

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 followingcommands at the prompt:

• For a 38400 DTE rate, enter:

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

• For a 19200 DTE rate, enter:

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

• For a 9600 DTE rate, enter:

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

This configures the modem and stores the current modem settings in the non-volatile memory.These changes then loaded in place of the factory defaults at power-on.

AT commands

The AT commands that are used when initializing the MultiModem MT5634ZBA are described inTable 3-4.

Table 3-4 MultiModem MT5634ZBA initialization AT commands

AT command Description

AT$SBnnnnn Set serial port to nnnnn bps.

AT&K3 Enable CTS/RTS hardware flow control.

AT&D2 If DTR drops while in online data mode, the modem hangs up.If the signal is not present, the modem will not answer or dial.

AT&C1 DCD goes high when the remote modem carrier signal isdetected, and goes low when the carrier signal is not detected.

ATS0=2 Sets the number of rings until the modem answers.

AT&Q0 Enables result codes.

AT&W0 Stores the current modem settings in non-volatile memoryand loads them in place of the factory defaults at power-on, orfollowing the ATZ command.

After setting up the modem, exit the tip utility by typing a carriage return followed by a tilde (~)character, followed by a period (.) character.

3-16 68P02901W19-S

Oct 2009

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 modemfrom a remote host (bi-directional modem service):

Procedure 3-7 Enabling the login process

1 To view the Serial Port Manager window, select port manager from thetools icon, and click the serial port manager icon.

2 Click on port a or b with the left mouse button to select the port to beused by the modem.

3 Select modify from the Edit menu. The Serial Port Manager: Modifywindow appears.

4 Select the expert display.

5 Select Bi-directional from template.

6 Set Baud Rate to the desired baud rate of the modem. Refer to Table 3-5for the available baud rate settings.

7 Set Terminal type to vt100.

8 Verify that all the amended fields are correct and click the OK button.

9 Close all the open windows.

10 To verify that a port monitor has been configured, enter the followingcommand at the # prompt:pmadm -p zsmon -lAn example output is:

PMTAG PMTYPE SVCTAG FLGS ID <PMSPECIFIC>zsmon ttymon ttya u root /dev/term/a - -/usr/bin/login - 9600 ldterm, ttcompat login: - dialup n #modem-BidirectionalIf a port monitor has not been configured for that port, return to step 2and try again.

Table 3-5 Modem baud rate settings

Modem baud rate Setting required

28800 38400 m

14400 19200 m

9600 9600 m

68P02901W19-S 3-17

Oct 2009

Remote connection and file transfers Chapter 3: Ancillary Devices

Remote connection and file transfers

To test the modem, contact Customer Network Resolution Centre (CNRC) for a telephonenumber, login, password and log out information.

If problems occur, refer to Troubleshooting the modem on page 3-19.

Once the login is successful, instruct the modem to hang-up the line by typing:

+++ ATH

3-18 68P02901W19-S

Oct 2009

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.

• No login prompt.

• Modifying eeprom settings.

• Corruption from platform with remote system login.

• Modem hangs up after answering a call and negotiation.

• Permission denied or link down.

• Modems do not disconnect properly.

• Nothing happens when trying to tip the modem.

• On dialing the platform, the modem never picks up the phone.

• Login message is corrupt.

• Cannot log in - password failed.

• No utmpx entry.

All ports busy

This message indicates that another process has control of the port. Follow Procedure 3-8 torectify the problem:

Procedure 3-8 Modem troubleshooting: all ports busy

1 Disable or delete the port monitor using the serial port manage,for that port, or by using the following commands: Enter thefollowing command to disable the port monitor service of port a:/usr/sbin/pmadm -d -p zsmon -s ttya.

Continued

68P02901W19-S 3-19

Oct 2009

All ports busy Chapter 3: Ancillary Devices

Procedure 3-8 Modem troubleshooting: all ports busy (Continued)

Enter the following command to enable the port monitor service of porta:

/usr/sbin/pmadm -e -p zsmon -s ttya

Enter the following command:tip -<9600> /dev/cua/areplacing <9600> with the appropriate connection speed for thedevice.

2 Check that the details have been entered correctly in /etc/remote,ensuring that the correct device has been specified.

3 There could be a permissions problem on the device. If necessary,change the permissions and ownership of the modem port by entering,for example, the following commands at the # prompt:chmod 666 /dev/cua/achown uucp /dev/cua/als -Ll /dev/cua/ato verify permissions and ownership.

NOTEIf cu is abruptly terminated, the device will be left with anowner of the last cu user.

4 Check for a lock file in /var/spool/locks. If there is a lock file, forexample, LK.032.028.001, then cat the file. The number displayed isthe Process ID (PID). Use the ps command to determine if the processis still active. Remove the lock file. If the message All ports busy isdisplayed, terminate the process. If the process is defunct it cannotbe terminated and a reboot will be necessary. This occurs because thedriver is waiting at an unlinkable level for the device to respond.

5 Another process has the port open. This could be another tip session,a getty process or a defunct tip/cu process. At the # prompt, enterthe following command:

ps -ef | grep tip

As root, enter the following command at the # prompt for theappropriate device:fuser /dev/cua/aAn example output is:

/dev/cua/a: 652o 651o

Based on the example output, enter the following commands:ps -ef | grep 652ps -ef | grep 651

Continued

3-20 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration No login prompt

Procedure 3-8 Modem troubleshooting: all ports busy (Continued)

The PIDs are 652 and 651.If the process using the port is /usr/bin/login or ttymon, thensomebody has dialed the machine, the modem is active or the modem isasserting Data Carrier Detect (DCD) all the time. Configure the modemso that the DCD is asserted only when a carrier is detected from theremote modem. Refer to the modem documentation for further details.

6 If the process is ttymon, kill the process using the Serial portmanager. Select the port from the Edit menu and delete the portservice. (The modem is no longer configured for dial-in).The command to remove the service is:pmadm -r -p zsmon -s <SVCTAG>(use pmadm -l to determine SVCTAG).

7 Bring the system down and then back to multi-user mode. Thecommand is:/usr/sbin/shutdown -i6 -g0 -ySometimes a complete reboot may be necessary to achieve a hardwarereset on the port before rebooting.REMOVE the device (do not leave a dangling cable; remove the deviceat the platform) and DELETE the port monitor.

No login prompt

Use the following procedure if a login prompt does not appear.

Procedure 3-9 Modem troubleshooting: no login prompt

1 Check if a ttymon process is started by typing the following commandat the # prompt:ps -ef | grep ttymonAn example output is:

root 208 204 80 Sep21 ? 0:01 /usr/lib/saf/ttymon

root 17258 208 2 10:42:43 ? 0:00 /usr/lib/saf/ttymon

Where:PID of 208 is the parent ttymon process.PID of 172.58 is the child process for term/b.

2 Check if the ttymon process TTY has changed from ? to term/b bytyping the following command at the # prompt:ps -ef | grep ttymonAn example output is:

root 208 204 80 Sep21 ? 0:01 /usr/lib/saf/ttymon

root 17258 208 6 10:42:43 term/b 0:00 /usr/lib/saf/ttymon

Continued

68P02901W19-S 3-21

Oct 2009

When to modify the eeprom settings Chapter 3: Ancillary Devices

Procedure 3-9 Modem troubleshooting: no login prompt (Continued)

3 If the ttymon process TTY has not changed to term/b, check if theserial port has been configured properly and the port monitor serviceis present by typing the following command at the # prompt:pmadm -p zsmon -lAn example output is:

zsmon ttymon ttya

u root /dev/term/a - -

/usr/bin/login - 9600 ldterm,

ttcompat login: - tvi925 n

#modem -Bidirectional

4 Check and verify that the port monitor services baud rate matches themodem baud rate.

5 Use the tip utility and connect back to the modem.

When to modify the eeprom settings

Do not change the eeproms unless trying to get a terminal working at boot prom level.

Corruption from platform with remote system logging in

This is usually an indication that the modem speed and the configured port monitor speed arenot matched. 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 speedof the platform.

2 Connect the modem using tip, and verify the modem configuration.

NOTEThe modem must be able to lock the modem speed andmatch the port monitor speed configured using the SerialPort Manager.

Modem hangs up after answering a call and negotiation

This is probably because one or both the modems are forced to use a particular connectionspeed or compression protocol. If one modem cannot manage to connect to the other modem,the modem hangs up. Check the settings of both modems.

3-22 68P02901W19-S

Oct 2009

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

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 thehardwire entry of the /etc/remote file.

2 Check in /var/spool/locks for a lock file LCK.* and remove that file.

3 Check the permissions and ownership on the serial device (/dev/cua/aor /dev/cua/b).

Modems do not disconnect properly

The modem does not disconnect properly or a user stays logged in even after disconnecting.

The modem is not configured correctly. The modem must be configured so that the Data CarrierDetect (DCD) is asserted only when a carrier is detected from the remote modem. Refer tothe modem documentation for further details.

Nothing happens when trying to tip the modem

If this situation occurs, use the following procedure to correct this problem:

Procedure 3-12 Modem troubleshooting: no response to tip

1 Check the cabling to the modem.

2 Check if the proper port is being used.

3 Ensure that tip is being used in a shell tool, NOT in a command tool.

When dialing into the SPARC the modem never answers thephone

This situation indicates that the modem is not configured correctly, FollowProcedure 3-13 tocorrect this problem:

Procedure 3-13 Modem troubleshooting: modem not answering

1 Check if the modem is set up for auto answer (*AA2) for MotorolaModems or ATS0=2 for MultiModem.

2 Ensure that the Data Terminal Ready (DTR) light is lit on the modemwhich indicates that the DTR is asserted from the platform.

68P02901W19-S 3-23

Oct 2009

Login message is corrupt Chapter 3: Ancillary Devices

Login message is corrupt

The login message is corrupt and nothing happens when RETURN is pressed, but it does ifLF or CTRL-J is pressed.

If this situation occurs then reconfigure the remote computers serial port setup for eight databits, one stop bit and no parity.

Cannot login, password fails

This situation indicates a parity problem. The originating terminal or tip session is using aparity 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 portmonitor services and the environment variable TERM is also set to vt100 on both the localand remote host.

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 connectedanywhere on the LAN and is not restricted to being connected to the system processor orone of the GUI processors.

For information on adding and setting up a printer on the LAN, please refer to the manual thataccompanied 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 hostname to the /etc/hosts file of the single platform processor.

Use the following procedure to verify the printer setup:

Procedure 3-14 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 networkas follows:ping <hostname>Replace <hostname> with the name of the printer set in the /etc/hostsfile.

3 If the printer does not respond to the ping command, check thefollowing:

• Make sure all physical connections, bridges, and routers areworking correctly.

• From the setup page, check that the IP protocol is enabled.

• Check that the IP address is set correctly on the printer operator'spanel.

68P02901W19-S 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 isattached).

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 entitieson 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 printermust 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>

NOTEOn a non Lexmark or SPARC printer E printer ASCII print jobs may not be sent to theprinter correctly, causing the print output to appear jumbled.

To fix this change the setting CR After LF to Yes. Refer to the printer manual fordetails 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 forprinting.

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 3-27

Oct 2009

Printer configuration file Chapter 3: Ancillary Devices

3-28 68P02901W19-S

Oct 2009

Chapter

4

OMC-R Log Files■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

68P02901W19-S 4-1

Oct 2009

Overview Chapter 4: OMC-R Log Files

Overview■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The OMC-R maintains log and error files, separate for each application. The log files aregrouped into log directories according to the different functional areas. Log files contain startupand 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:

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

• Checking audit log files on page 4-11.

4-2 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_logsand the INFORMIX log directory /usr/informix contain the log files shown in the followingcharts.

OMC-R log files on the system processor

The following chart, Figure 4-1, shows the file structure under each of the three log directoriesmentioned above.

NOTESome miscellaneous log files exist in the /usr/omc/logs directory depending on theactivity 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 Chapter 4: OMC-R Log Files

Figure 4-1 OMC-R Log files on the system processor

4-4 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 onthe GUI server.

Figure 4-2 OMC-R log files on the GUI server

NOTEThere is no INFORMIX log directory on the GUI server.

Problems with parsing statistics and maintenance of the PMdatabase

The fpomcaudit and omcaudit logfiles can be monitored for any issues related to the parsing ofPM statistics and maintenance of the OMC database. For information related to the maintenanceof 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. Thisdirectory 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. Allother 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 createdin $GLOBAL_LOG_DIR. This environment variable is defined as /usr/omc/logs/ipc. If a serioussystem problem exists (for example, failure of an OMC-R application), this area may growrapidly in size. Accordingly, the directory should be examined daily. Entries may be deletedfollowing 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 /tmpfails, 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 fromwhich 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 theCommon.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 thisvariable is not defined in the environment variable files.

Other environment variables

To modify other environment variables, refer to User configurable environment variables onpage 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 inTable 14-5 to record the checks.

Procedure 4-1 Checking the OMC-R log files

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

• {34164} Critical statistics log files are placed in the/usr/omc/ne_data/critical_stats directory.

On the GUI processor:

• OMC-R logs are placed in the /usr/omc/logs directory.

• Event logs are placed in the /usr/omc/ne_data/ev_logs directory.

2 Check the BSS log files:As user omcadmin execute the following commands:cd $OMC_TOP/logs/bsstail -50 bssname_yyyymmdd

This allows you to see all command line activities performed on aparticular BSS.

3 Check the Configuration Management log file:As user omcadmin execute the following commands:cd $OMC_TOP/logstail -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 Checking the OMC-R log files (Continued)

4 When a cutover has been performed check the cutover log file to see ifit has been successful:As user omcadmin execute the following commands:cd $OMC_TOP/logsmore cutover.nnnn

This log file says whether the cutover has been successful.

5 If problems are experienced adding or updating statistics in the PMdatabase then check for the existence of dbms log files:As user omcadmin execute the following commands:cd $OMC_TOP/logsmore 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 anIPC log file exists in /usr/omc/logs/ipc directory.As user omcadmin execute the following commands:cd /usr/omc/logs/ipcmore ipclogfile name

These log files are usually of the format AF032959.0001 (Internetaddress 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 whenrequired.

As user root execute the following commands:cd $OMC_TOP/logsmore 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/usrauditlogstail -50 pmguiaudityyyymmdd

Continued

4-8 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Checking OMC-R log files

Procedure 4-1 Checking the OMC-R log files (Continued)

11 Check the Informix online logs for DB errors relating to the PM andCM databases.As user omcadmin execute the following commands:For the PM DB:cd /usr/informixmore online.log_OMC.ddmmyyyy

For the CM DB:cd /usr/informixmore online.log_MIB.ddmmyyyy

12 Check the omcaudit log for messages relating to OMC-R activity.As user omcadmin execute the following commands:cd /usr/omc/logstail -f omcaudityyyymmdd

Refer to Restartable processes on page 2-49 for further details aboutmessages in the omc audit and console log.

13 Monitor the disk space used by the various log files.As user omcadmin monitor the output of the maintain_script cronjob to ensure that it deletes log files on a regular basis.cd /var/mailmore omcadmin | grep maintain_script

14 Check the usraudit log file for errors relating to the GUI.As user omcadmin execute the following commands:cd $OMC_TOP/logs/usrauditlogs/tail -50usraudityyyymmdd

Continued

68P02901W19-S 4-9

Oct 2009

Checking OMC-R log files Chapter 4: OMC-R Log Files

Procedure 4-1 Checking the OMC-R log files (Continued)

15 Check the fcaudit log file for errors relating to the event logs.As user omcadmin, execute the following commands:cd $OMC_TOP/logstail -f fcaudityyyymmdd

NOTEThe following error reported in the fcaudit log because ofmultiple file upload request can be ignored safely and it doesnot cause any missing statistics:

No matching event found for file transfer completed event.Service error code: 0Error Level: 4

To confirm whether it is for redundant upload request or not, checkthe omcaudit log for the following message:

handle_xfer: Requested file already exists, redundant upload

This message should correspond to the following message in thefcaudit log:

No matching event found for file transfer request response

There could be 1 or 2 seconds reported time mismatch betweenomcaudit log and fcaudit log because of message propagation betweenprocesses.

4-10 68P02901W19-S

Oct 2009

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.

Use different methods for checking audit log files in a:

• Single OMC-R environment.

• Multiple OMC-R environment.

Checking audit log files in a single OMC-R environment

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

Checking audit log files in a multiple OMC-R environment

In a multiple OMC-R environment, especially in an environment where the system administratorcannot afford to run multiple GUIs, the following methods can be used to check audit log files.

Checking what has been applied

The aurecordtable9 contains a row for each line in an audit log. The aurecordtable9 containsa status column, which displays a code indicating the result of the audit apply, as shown inTable 4-1.

Table 4-1 Audit apply result codes

Code Meaning

500 The line has not been applied to the MIB database.

501 The line has failed to apply.

502 The row has been successfully applied to the MIB database.

68P02901W19-S 4-11

Oct 2009

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, if an audit is takinga long time to complete):

Procedure 4-2 Checking the current state of audits

1 Login as omcadmin on the system processor.

2 Create a new file (using the vi editor for example) calledAudit_apply_check.sql.

3 Enter the following SQL statements in Audit_apply_check.sql:set isolation to dirty read;select l.rootname audit,count(*) not_appl from aulogtable9l, aurecordtable9 rwhere r.status = 500and r.logoidclass = l.oidclassand r.logoidtomid = l.oidtomidand r.logoidinstrite = l.oidinstriteand r.logoidinstleft = l.oidinstleftgroup by 1;select l.rootname audit,count(*) appliedfrom aulogtable9 l, aurecordtable9 rwhere r.status = 502and r.logoidclass = l.oidclassand r.logoidtomid = l.oidtomidand r.logoidinstrite = l.oidinstriteand r.logoidinstleft = l.oidinstleftgroup by 1;select l.rootname audit,count(*) failedfrom aulogtable9 l, aurecordtable9 rwhere r.status = 501and r.logoidclass = l.oidclassand r.logoidtomid = l.oidtomidand r.logoidinstrite = l.oidinstriteand r.logoidinstleft = l.oidinstleftgroup by 1;

4 Enter the following:mib_envisql mib_db <Audit_apply_check.sql>Audit_apply_check.out

5 Open the Audit_apply_check.out file. The output should look similarto the following:

auditnot_applLAB_BSC2:SITE-16: 51LAB_BSC2:SITE-10: 42

audit appliedLAB_BSC2:SITE-0:1LAB_BSC2:SITE-10: 1

audit failedLAB_BSC2:SITE-10: 11

Continued

4-12 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Checking audit log files in a multiple OMC-R environment

Procedure 4-2 Checking the current state of audits (Continued)

6 To see if the not_appl value is decreasing, repeat step 4 and step 5several times.

NOTEIt is possible for an audit to fail with some lines still with thenot_appl state. This is because the lines relied on previouslines which did not apply successfully.

68P02901W19-S 4-13

Oct 2009

Checking audit log files in a multiple OMC-R environment Chapter 4: OMC-R Log Files

4-14 68P02901W19-S

Oct 2009

Chapter

5

OMC-R Cron Jobs■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

68P02901W19-S 5-1

Oct 2009

Overview Chapter 5: OMC-R Cron Jobs

Overview■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

These are installed to perform various maintenance tasks for both system and GUI processors.A recommended cron script exists for each processor. This is installed in the directory$OMC_TOP/current/install_splat.

Several log maintenance scripts are available to maintain the log files on the differentprocessors. These scripts are designed to work on a specific area of the logs. All of these scriptscan be executed from the command line or through cron.

NOTEMost of these scripts need omcadmin as login id.

The following topics are described in this chapter:

• System cron jobs on page 5-3.

• Scheduling cron jobs using the batch scheduler on page 5-9.

• Scheduling cron jobs from the command line on page 5-14.

• Checking cron jobs on page 5-18.

5-2 68P02901W19-S

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

NOTETo check the output of the root cron jobs, the root file in the /var/mail directoryshould be checked for error messages.

68P02901W19-S 5-3

Oct 2009

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

• maintain_ct.sh

• checkValidlockPID

NOTETo check the output of the omcadmin cron jobs, the omcadmin file in the /var/maildirectory should be checked for error messages.

sys cron jobs

The following system cron jobs are executed on the system processor:

• sa1

• sa2

These cron jobs are used for performance collection.

NOTETo check the output of the sys cron jobs, the sys file in the /var/mail directory shouldbe checked for error messages.

5-4 68P02901W19-S

Oct 2009

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

NOTETo check the output of the root cron jobs, the root file in the /var/mail directoryshould be checked for error messages.

omcadmin cron jobs

The following omcadmin cron jobs can be run on the system processor:

• maintain_script.

• checkValidLockPID.

NOTETo check the output of the omcadmin cron jobs, the omcadmin file in the /var/maildirectory 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.

NOTETo check the output of the sys cron jobs, the sys file in the /var/mail directory shouldbe checked for error messages.

68P02901W19-S 5-5

Oct 2009

Recommended cron jobs Chapter 5: OMC-R Cron Jobs

Recommended cron jobs

maintain_script (root or omcadmin)

This script will list, archive, remove, and clear files of a specified age from a specified directory.

/usr/omc/sbin/maintain_script

The following shows the syntax of this script:

maintain_script < -l | -a | -r | -c > [ -d <days> ] [ -t <device> ] [<directory>] [ <filename> ]

Where: is:

-l the mode which lists the selected files.

-a the mode which archives selected files to tape using theUNIX command cpio.

-r the mode which removes selected files from the system.

-c to clear the database log file.

-d <days> the age of the files to be selected (default value is one day).

-t <device> the tape device for archiving the files (default value isdev/rmt/0 on the system processor).

<directory> the system directory.

<filename> the file to be removed, for example, omcaudit\*.

NOTEOnly one of the options shown within the chevrons (l, a, r, or c) can be selected atone time. A separate invocation is needed every time to list, archive, or removemaintenance log files.

systat (root)

This script monitors the status of the system:

/usr/omc/sbin/systat

onmode_pm (root)

This script frees up memory segments for PM database.

/usr/omc/sbin/onmode_pm

5-6 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Recommended cron jobs

onmode_mib (root)

This script frees up memory segments for CM database.

/usr/omc/sbin/onmode_mib

monitor_diskspace (root)

This script monitors the disk capacity of the /usr/omc/ne_data/raw_stats/nmc_stats directory.

/usr/omc/sbin/monitor_diskspace

monitor_ct_logs (root)

This script checks disk space on the /usr/omc/ne_data/ct_logs directory, and will remove oldlogs if space exceeds a certain limit.

/usr/omc/sbin/monitor_ct_logs

roll_online.log (root)

This script performs a rollover of the online.log file.

/usr/omc/sbin/roll_online.log

sar_per_day (root)

This script generates a system activity report data file.

/usr/omc/current/sbin/sar_per_day

update_mib_statistics (omcadmin)

This script updates statistics for all tables in the CM database.

/usr/omc/current/sbin/update_mib_statistics

roll_paging_log (omcadmin)

This script performs a daily rollover of the PagingLog file.

/usr/omc/sbin/roll_paging_log

core_presence (omcadmin)

This script notifies user omcadmin of any core files.

/usr/omc/current/sbin/core_presence

68P02901W19-S 5-7

Oct 2009

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/sbin/monitor_log

app_vrt_display (root)

This script ensures that applix virtual display is running.

/usr/omc/current/sbin/app_vrt_display

omc_db_maint (root)

This script performs PM database maintenance.

$OMC_TOP/current/sbin/omc_db_maint

site_timesynch (omcadmin)

This script gets the date on the system processor, then updates sites according to the NE map.

/usr/omc/current/sbin/site_timesynch [passwd 1] [passwd 2].. [passwd n]

Where <passwd 1>, <passwd 2>, and <passwd n> are optional level 2 passwords for each NEwith a level 2 password set.

timesynch (root)

This script resets the GUI processor time from the system processor.

/usr/omc/current/sbin/timesynch

bss_dt_load.sh (omcadmin)

This script loads default date times into BSS datetimes.

/usr/omc/current/sbin/bss_dt_load.sh

maintain_ct.sh (omcadmin)

This script deletes call trace logs.

checkValidLockPID (omcadmin)

This script removes any invalid lock files.

/usr/omc/current/sbin

5-8 68P02901W19-S

Oct 2009

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

The CDE environment provides a batch scheduler which allows the user to schedule cron jobsfrom the CDE environment on the system and GUI processors.

Displaying cron jobs

Use the following procedure to display cron jobs using the batch scheduler:

Procedure 5-1 Displaying cron jobs using the batch scheduler

1 To activate the cron scheduler click the CRON icon on the CDE desktopenvironment. A window show in Figure 5-1 is displayed. A list ofscheduled cron jobs is displayed in the top half of the window. Thesecron jobs can be added to, removed or modified.

2 To display details of the cron job that is currently running, click Getactive crontab. The details are displayed, for example, as shown inFigure 5-2. These include Hour, Minute, Day of month, Month, Dayof week and the cron command.

3 To display details of any listed cron job, simply click the cron job inthe list.

4 To clear the details, click Clear gadgets.

68P02901W19-S 5-9

Oct 2009

Displaying cron jobs Chapter 5: OMC-R Cron Jobs

Figure 5-1 Batch scheduler main window

5-10 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Displaying cron jobs

Figure 5-2 Batch scheduler main window: selected cron job

68P02901W19-S 5-11

Oct 2009

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 Adding a new cron job using the batch scheduler

1 From the Batch scheduler main window (Figure 5-1) highlight one of thepre-existing cron jobs.

Its details are displayed, for example, as shown in Figure 5-2. These includeHour, Minute, Day of month, Month, Day of week and the cron job command.

2 Modify the variables as required.

3 Click Add.

4 Click Install to set the new cron job to run on the system or GUI processor.

Modifying an existing cron job

Use the following procedure to modify an existing cron job using the batch scheduler:

Procedure 5-3 Modifying an existing cron job using the batch scheduler

1 From the Batch scheduler main window (Figure 5-1) highlight one ofthe pre-existing cron jobs.

Its details are displayed, for example, as shown in Figure 5-2.

2 Modify the variables as required. The Modify command button isenabled.

3 ClickModify.A Notify message box is displayed as shown in Figure 5-3.

4 Click OK to replace the pre-existing schedule with the modified cronjob schedule.

5 Click Install to set the modified schedule to run on the system orGUI processor.

5-12 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Removing a cron job

Figure 5-3 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 Removing a cron job using the batch scheduler

1 From the Batch scheduler main window (Figure 5-1) highlight the cronjob. Its details are displayed.

2 Click Remove.A Notify message box is displayed as shown in Figure 5-3.

3 Click OK to remove the cron job.

4 Click Install to set the modified crontab to run on the system or GUIprocessor.

68P02901W19-S 5-13

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 processorusing the command line:

• Viewing cron jobs.

• Checking cron jobs.

• Adding cron jobs.

• Removing cron jobs.

• Cron maintenance procedure.

• Printing crontab files.

Viewing crontab files

To view a user's existing crontab, execute the following command:

crontab -l

NOTETo view a user's crontab file, it is necessary for the user to log in.

Verifying cron jobs

Results of administration jobs that are run using the cron utility are mailed to the owner of thespecific job (for example, root and omcadmin).

The mail file for the user is located in /var/mail. This file can be viewed to check the outputfrom the cron job.

To check the results of jobs run using cron, login to the relevant processor and using themail tool check that all cron jobs have run successfully. The user is informed through mailregarding unsuccessful cron jobs.

5-14 68P02901W19-S

Oct 2009

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, which aremore than seven days old from the system, at 15 minutes past midnight.

NOTETo add commands to a user's crontab, it is necessary for the user to log in.

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

2 Add the new job (comment and activation line) to the temporaryfile. For example,# Remove database files older than 7 days#15 00 * * * env OMC_TOP=/usr/omc /usr/omc/sbin/maintain_script -r -dThe crontab file consists of six fields. The first five fields are theinteger patterns that specify the following:

• Minutes (0-59).

• Hour (0-23).

• Day of the month (1-31).

• Month of the year (1-12).

• Day of the week (0-6). For example, 0 denotes Sunday.

3 Re-submit the edited temporary file to cron for execution usingcrontab as follows:crontab /tmp/cron_list.tmp

4 Enter the following command to remove the temporary file.rm /tmp/cron_list.tmp

NOTE

• It is not recommended to set up cron jobs that archivefiles to tape.

• A hardcopy printout of the cron jobs running on thesystem should be kept safe. This may be used forreference during system troubleshooting.

68P02901W19-S 5-15

Oct 2009

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, whichare more than seven days old at 15 minutes past midnight.

NOTETo remove a cron job from a user's crontab file, it is necessary for the user to log in.

Procedure 5-6 Deleting cron jobs: example

1 List the cron jobs currently running to a temporary file by entering:crontab -l > /tmp/cron_list.tmp

2 Delete the required activation line and relevant comment lines fromthe temporary file, as shown in the example:

# Remove database files older than 7 days#15 00 * * * env OMC_TOP=/usr/omc /usr/omc/sbin/maintain_script-r -d7

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

cron maintenance procedure

Log files of cron jobs are produced, which must be regularly maintained. Use the followingprocedure regularly to avoid a cron log file becoming too large.

Procedure 5-7 cron maintenance procedure

1 Login as root and enter the following command:tail -100 /var/cron/log > /tmp/cron_logThis takes the last 100 lines of the cron log file and places it in atemporary directory.

2 Copy the log file back to its original directory as follows:mv /tmp/cron_log /var/cron/logThe 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-16 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Printing crontab files

Printing crontab files

Each time a crontab file is modified, a printout of it should be made. Several different crontabfiles may exist: each of the users, root and omcadmin can have a crontab file on the systemprocessor and any of the GUI processors.

Use the following procedure to obtain a crontab file that are printed:

Procedure 5-8 Printing crontab files

1 Login to the processor where the crontab file has been set up usingthe relevant login id.

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.

68P02901W19-S 5-17

Oct 2009

Checking cron jobs Chapter 5: OMC-R Cron Jobs

Checking cron jobs■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Checklist for cron jobs

Use the following procedure to check cron jobs. Copy the checklist in Table 14-4 to recordthe checks.

Procedure 5-9 Checking cron jobs

1 Check that the cron daemon is running on the system. As user rootexecute the following command:ps -elf | grep cronA/usr/sbin/cronprocess is displayed.

2 Start the cron daemon if it is not running. As user root execute thefollowing commands:rm -f /etc/cron.d/FIFO/usr/sbin/cron

3 Check that the CRONLOG variable has been set to YES to ensure thatcron logging is done. As user root execute the following command:more /etc/default/cron | grep CRONLOG

4 If the CRONLOG variable is set to NO, then it should be changed. Asuser root edit the/etc/default/cronfile and change theCRONLOGsetting to YES. Save the file.

5 Check that the cron jobs are set up correctly for user root. As userroot execute the following command:crontab -l

6 Check that the cron jobs are set up correctly for user omcadmin. Asuser omcadmin execute the following command:crontab -l

7 Check that the system cronjobs are set up correctly. As user sysexecute the following command:crontab -l

8 Check the /var/cron/log file to ensure that all crons executed arelogged to this 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 spaceissues. As user root execute the following command:cd /var/cronls -l

Continued

5-18 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Checklist for cron jobs

Procedure 5-9 Checking cron jobs (Continued)

10 Log files should exist in the format log.<ddmmyyyy>where <ddmmyyyy>is the date of the log.

11 Check the output of root cron jobs for any errors. As user root executethe following commands:cd /var/mailmore root | grep <cronjobname>

12 Check the output of omcadmin cron jobs for any errors. As user rootexecute the following commands:cd /var/mailmore omcadmin | grep <cronjobname>

13 Check the output of the system cron jobs for any errors. As user sysexecute the following commands:cd /var/mailmore sys | grep <cronjobname>Where <cronjobname> is the name of the cron job whose output youare checking.

68P02901W19-S 5-19

Oct 2009

Checklist for cron jobs Chapter 5: OMC-R Cron Jobs

5-20 68P02901W19-S

Oct 2009

Chapter

6

OMC-R Environment variables■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

68P02901W19-S 6-1

Oct 2009

Overview Chapter 6: OMC-R Environment variables

Overview■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The following topics are described in this chapter:

• Customizing the OMC-R user environment on page 6-3.

• User configurable environment variables on page 6-5.

• Changing an environment variable on page 6-26.

• Setting the status of the Consolidated Alarms on page 6-29.

• Non user configurable environment variables on page 6-31.

• Setting the time for the OMC-R and NEs on page 6-36.

6-2 68P02901W19-S

Oct 2009

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, it is done using the user'sxxxx.private files (for example, cshrc.private) located in the user's home directory.

If all the environments of OMC-R users need to be customized, it is done in the$OMC_TOP/current/env/.xxxx files, which are used by all OMC users.

NOTEThere is a separate /usr/omc/current/env directory on each processor.

.cshrc.private file

If the .cshrc.private file exists, it is executed when a user logs in, and whenever the user runsa C shell. The .cshrc.private file is used to specify user-specific values for the environmentvariables.

NOTEWhen an environment variable is redefined, the new environment variable definitionmay not become current until the user logs in again.

.Xdefaults.private file

The .Xdefaults.private file is an X resource file which is used to set up function keys. Many Xattributes for personal display can be customized by specifying them in this file. In particular, amapping between function keys and strings must be set up in this file.

NOTEOnly the OMC-R system administrator can customize the .Xdefaults.private filefor a user.

A function key can be associated with a string. When the key is pressed and an X-Term windowis displayed, the string is printed in the X-Term window.

The association between the function key and the string is specified in a translation table in anX resources file. Individual users can program function keys by placing a translation table intheir .Xdefaults.private file.

68P02901W19-S 6-3

Oct 2009

.Xdefaults.private file Chapter 6: OMC-R Environment variables

Example

The format of the translation table is shown in the following example:

.XTerm*VT100.Translations: #override \

<Key>F1: string(“disp_equip 0“)string(0xd)

\n\ <Key>F2: string(disp_dev_s)

NOTENo spaces should follow the \ character on the same line.

In the previous example, the translation table specifies that for all X-Terms of type VT100,the translation of key functions to strings overrides any previously defined function for keysF1 and F2.

The translation of each key is as follows:

• When the F1 key is pressed, the string disp_equip 0 is printed on the screen followed by acarriage return. If an argument for the string begins with 0x the argument is taken as ahexadecimal number, and the corresponding ASCII character is inserted. The argument0xd inserts the ASCII carriage return character.

• When the F2 key is pressed, the string disp_dev_s is printed on the screen. A carriagereturn is not sent, and typically the operator finishes off the command and then pressesRETURN.

The keyword override is important because without it, all existing translations are deleted. Theuser, when programming function keys, only wants to change certain translations.

Translations should be separated by the sequence \n. A back slash (\) should be placed at theend of each line except the last to indicate that the translation table is continued on the next line.

6-4 68P02901W19-S

Oct 2009

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, cannot bemodified.

• /usr/omc/config/global/env

This location contains a set of empty files where a non-default value of an environmentvariable is required, the value should be set in the correct file at this location.

Where environment variables are sourced by the OMC-R applications, the set of values inthe /usr/omc/current/config/env location are initially sourced. Where values are set in the/usr/omc/config/global/env location, these are sourced as a secondary set of values.

The User configurable environment variables, for the OMC-R applications, are defined in thefollowing files:

• /usr/omc/current/config/env/pmProcConfig.csh

Defines the variables used by the system processors, which interact with the PM database.

• /usr/omc/current/config/env/mibProcConfig.csh

Defines the variables used by the MIB processes, which interact with the MIB database.

• /usr/omc/current/config/env/mmiProcConfig.csh

Defines the variables used by the GUI processes which interact with the GUI server orclients.

There are .sh versions of these files (Bourne Shells), which are automatically updated if anychanges are made in the .csh versions.

System processes and PM database configurable variables

This section lists the user configurable environment variables, used by the system processesinteracting with the PM database.

The default values of these environment variables are defined in the /usr/omc/current/con-fig/env/pmProcConfig.csh file. To set a non-default value for any of these variables, make thechange in the /usr/omc/config/global/env/pmProcConfig.csh file.

68P02901W19-S 6-5

Oct 2009

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 Rloginsession is active.

• If the environment variable is not set (that is, the value is 0), it allows the upload sessioneven though the Rlogin session is active.

• If set to 1, the environment variable aborts the upload request if the Rlogin session is active.

The default value for the environment variable is 0.

AUTOSTART_PMGUI

The AUTOSTART_PMGUI when set to OFF. If it is set to ON, the PMGUI will start automaticallyin the background as the GUI starts. However, this can slow down the startup process.

COUNTRY_CODE

The COUNTRY_CODE environment variable defined by the GSM operator license.

ENABLE_CYCLIC_NBRS

The ENABLE_CYCLIC_NBRS when set to ON activates the Cyclic Neighbors Feature. Thefeature enables neighbor statistics for cells in rotation, starting with cells that have the oldestdate for last enabled neighbor statistics (see Using neighbor statistics on page 13-91). Thedefault value for this environment variable is OFF.

The ENABLE_CYCLIC_NBRS variable is set using the command:

setenv ENABLE_CYCLIC_NBRS ON

INFORMIXDIR

The INFORMIXDIR environment variable defines the path to where Informix is installed on thesystem and by default, is set to /usr/informix.

INFORMIXSERVER

The INFORMIXSERVER environment variable is used to identify the server name of the PMInformix Server instance and by default, is set to omc_sys.

MAX_BOOTLOADS

This environment variable is set to limit the maximum download capacity. It is used inconjunction withMAX_CSFP_BLP. The maximum value that this environment variable is set tois 12 and the minimum is 4. For Low-end systems the default is 6, and for Mid-end or High-endsystems the default is 12. A value of 8 is used by the system processes if the environmentvariable is not set or has exceeded permitted range.

6-6 68P02901W19-S

Oct 2009

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 downloadsto a value which is less than the maximum allowable number of downloads set byMAX_BOOTLOADS. This prevents all the download capacity from being used by the CSFPdownloads, ensuring spare capacity for a conventional download in the event of an NE losingpower momentarily, or some other transient fault.

For a Low-end system, this variable has a default setting of 3. For a High-end and Mid-endsystem, this variable has a default setting of 6.

If the defaults are maintained, the OMC-R limits the number of CSFP downloads to one half of themaximum allowable number of downloads. To increase the allowed number of CSFP downloadsto a higher fraction of the total allowed downloads, setMAX_CSFP_BLP to a higher value.

The permitted range of values is between 1 andMAX_BOOTLOADS - 1. IfMAX_CSFP_BLP isset to a value outside this permitted range, or the variable is not set, it is reset to one less thanthe value of the MAX_BOOTLOADS variable.

MAX_UPLOADS_PER_CHAN

The MAX_UPLOADS_PER_CHAN environment variable specifies the maximum number ofsimultaneous uploads per channel that are allowed at the OMC-R.

For a Low-end system, the default value is 2. For High-end and Mid-end systems the defaultvalue is 8. It has a valid range of 2 to 8. A default value of 4 is used if the environment variableis not set or an invalid value is specified.

MMI_CLEAR_INACTIVE_FMIC

TheMMI_CLEAR_INACTIVE_FMIC environment variable is set to TRUE for all users. It is seton to enable all users to clear inactive FMIC alarms from the system.

MMI_ENABLE_FMIC

TheMMI_ENABLE_FMIC environment variable is set to 1 to ensure that FMIC is enabled onthe MMI. It has a range of 0 or 1.

NETWORK_CODE

The NETWORK CODE environment variable is defined by the GSM operator license.

NO_OF_PARSERS

NO_OF_PARSES is by default set to integer size. This variable defines the number of parserprocesses that can run simultaneously.

This environment variable is always set to 1.

68P02901W19-S 6-7

Oct 2009

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, by default, is set to/usr/omc.

PM_HOURLY_STATS

The PM_HOURLY_STATS variable is defined in the /usr/omc/config/global/OMC.CNFG fileand the /usr/omc/config/global/pmProcConfig.csh file. It determines the interval at whichthe OMC-R receives BSS the statistical files.

The possible settings are:

• ON sets the interval to 1 hour.

• Any other value sets the interval to 30 minutes.

For a permanent change add the following statement to the file /usr/omc/config/global/pm-ProcConfig.csh:

setenv PM_HOURLY_STATS ON

An OMC stop/start is required.

PM_MAX_NEIGHBORS

The PM_MAX_NEIGHBORS variable defines the maximum number of cells in the network thatcan have neighbor statistics enabled. The size of the PM database neighbor statistic table,nbr_statistics, is defined as:

PM_MAX_NEIGHBORS*48*7

Where is

48 the number of intervals in a day.

7 the number of days storage.

If too many cells have the neighbor statistics enabled, this table starts to fill up. Whennbr_statistics is 70 percent full, alarm 30026 is raised. When the table is 100 percent full, nofurther neighbor statistics are parsed.

The number of enabled neighbor statistics should be adjusted to ensure that the table doesnot become 100 percent full. Factors to take into account are: the number of cells for whichneighbor statistics are enabled; the statistics sampling interval (30 minutes or 1 hour); and thenumber of days for which the statistics are kept. The maximum number of cells with neighborstatistics enabled varies with the type of system:

• On a Low-end system, the parser processes statistics for a maximum of 4000 neighbors pernetwork in a 30 minute interval. In this case PM_MAX_NEIGHBORS can be increasedto 4000.

• On a Mid-capacity or High-end system, the parser processes statistics for a maximum of92160 neighbors per network in a 30 minute interval. In this case PM_MAX_NEIGHBORScan be increased to 92160.

Refer to Using neighbor statistics on page 13-91 for additional checks and procedures that mustbe performed when modifying the PM_MAX_NEIGHBORS.

6-8 68P02901W19-S

Oct 2009

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

145|CFG_KEEP_STAT_FILE|1

Result: This will keep the Parsed file (bin file) and append parsed to the parsed file.

Usage of this flag:

Flag CFG_KEEP_STATS_FILE

Case:1

145|CFG_KEEP_STAT_FILE|0

Result: This Parsed file (bin file) is deleted.

CFG_KEEP_NMC_FILE

This variable is defined in /usr/gsm/current/config/pmloader.cfg.

Usage of this flag

Flag CFG_KEEP_NMC_FILE

Case:1

145|CFG_KEEP_NMC_FILE|0

Result: This NMC file is deleted.

Case 2:

145|CFG_KEEP_NMC_FILE|1

Result: This will keep the NMC file without deleting.

STATE_ON_AUDIT

The STATE_ON_AUDIT environment variable ensures that the device statistics on the MIB areupdated correctly after an audit. When this variable is set to 1, the OMC-R performs a stateresynchronization when an audit is completed.

The variable STATE_ON_AUDIT should be set to the same value in both themibProcConfig.cshand pmProcConfig.csh files.

SUB_RES_TIME

The SUB_RES_TIME variable defines the length of time the pm_main, waits for a reply from theevent manager. By default, this variable is set to 62 seconds.

68P02901W19-S 6-9

Oct 2009

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 thecompressed statistics file. These compressed statistics files can be found in directories/usr/omc/ne_data/raw_stats/100,0/BSS or /usr/omc/ne_data/raw_stats/100,0/RXCDR witha .debugcompressfile extension.

The default value for the UPL_KEEP_STATS_FILE variable is OFF.

MIB processes used by environment variables

This section lists the user configurable environment variables, used by the MIB processesinteracting with the MIB database.

The default values of these environment variables are defined in the /usr/omc/current/con-fig/env/mibProcConfig.csh file. To set a non-default value for any of these variables, modifythe /usr/omc/config/global/env/mibProcConfig.csh file.

AUTORESYNCDELAY

The AUTORESYNCDELAY environment variable is introduced to define the time required tostart the Network Resync on startup, if the Resync on startup flag is enabled in the Networkdetailed view. This time lapse or delay is measured in minutes. The delay allows the connectionsto NEs to be re-established after an OMC stop/start.

The default value for the AUTORESYNCDELAY variable is 0, and the maximum value is 10. Ifthe user sets a value more then 10 minutes, the delay will automatically reset to 0 minutes.

ATC_TIMEOUT

The ATC_TIMEOUT environment variable is set in the /usr/omc/current/config/env/mibProc-Config.csh file. To set a non-default value for any of these variables, modify the/usr/omc/config/global/env/mibProcConfig.csh file.

The ATC_TIMEOUT environment variable is related to the neighbor propagation feature.

When a change is made to an attribute of a cell, the CM database propagates this change to allthe neighbors pointing to that cell. If any of the neighbors are in edit, the CM database retriesthe propagation for the length of time specified by ATC_TIMEOUT. If this time exceeds, thepropagation fails for this neighbor.

The value of ATC_TIMEOUT is specified in tenths of a second. The default value is 1200.

If there are a large number of neighbors, RTFs or DRIs, then ATC_TIMEOUT needs to bemodified.

If ATC_TIMEOUT is not set, the system continues until each failed update has been retriedonce, and then terminates.

AU_APPLY_DELETES_FIRST

The AU_APPLY_DELETES_FIRST variable is set to ON by default. This allows the audit processto apply all delete actions before attempting create and update. It is not recommended tochange this environment variable.

6-10 68P02901W19-S

Oct 2009

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 OperatingInformation: OSI System Administration (68P02901W10) manual for details.

CT_1208LOG

The CT_1208LOG variable is default set to $OMC_TOP/ne_data/ct_logs. This environmentvariable specifies the location where the call trace logs are saved.

DBNAME

The DBNAME variable is default set to mib_db. This is the name of the CM database.

DEL_CELLX_FILES

The DEL_CELLX_FILES is used to set up the automatic deletion of CellXchange backup files,which are stored in the directory /usr/omc/config/global/cellX.

By default the DEL_CELLX_FILES variable is set to OFF.

To switch on the auto-deletion of backup files, change DEL_CELLX_FILES from OFF to ON inboth of the following files:

/usr/omc/config/global/env/Common.csh

/usr/omc/config/global/env/Common.sh

When the DEL_CELLX_FILES variable is set to ON, any files with the .BACKUP extension in thedirectory /usr/omc/config/global/cellX, which are over 30 days old, are deleted.

H2_DUALBAND

The H2_DUALBAND flag switches on MIB support for the Dual BAND Horizon II feature. Bydefault it is switched OFF.

To switch the H2_DUALBAND flag ON, change the H2_DUALBAND environment variable fromOFF to ON in the following files:

• /usr/omc/current/config/Common.sh

• /usr/omc/current/config/Common.csh

This requires an OMC stop/start.

INFORMIXDIR

The INFORMIX environment variable defines where the Informix software is installed on thesystem. This variable is by default, set to /usr/informix.

68P02901W19-S 6-11

Oct 2009

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 pathcontains no time slot switch or multiple non-adjacent switches. To enable the Upstream andDownstream TS MMS options, the NX_ENABLE_TIMESLOTS environment variable must be set.

Use the following procedure to enable the Upstream and Downstream TS MMS options:

Procedure 6-1 Enabling the Upstream and Downstream TS MMS options

1 Log on as omcadmin.

2 Enter the following command:cd /usr/omc/config/global/env

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

4 Update the Common.csh file as follows:setenv NX_ENABLE_TIMESLOTS 1

5 Stop and start the OMC.

OMC_TOP

The OMC_TOP environment variable is used by the OMC-R software and, by default, is set to/usr/omc.

PER_SITE_AUDIT

The PER_SITE_AUDIT flag switches on MIB support for the Per Site Audit feature. It requires anOMC stop or start.

The PER_SITE_AUDIT environment variable default value is set in the /usr/omc/current/con-fig/env/Common.csh file. To set a non-default value for any of these variables, modify the/usr/omc/config/global/env/Common.csh file.

PER_SITE_AUDIT_DEBUG

The PER_SITE_AUDIT_DEBUG flag switches on debugging for the Per Site Audit feature. If thisflag is enabled, extra messages are output to the /usr/omc/logs/omcaudit<date> file during aPer Site Audit.

Use the following procedure to enable PER_SITE_AUDIT_DEBUG:

Procedure 6-2 Enabling PER_SITE_AUDIT_DEBUG

1 Log on as omcadmin.

2 Enter the following command:cd /usr/omc/config/global/env

Continued

6-12 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration GUI processes environment variables

Procedure 6-2 Enabling PER_SITE_AUDIT_DEBUG (Continued)

3 Update the Common.sh file as follows:PER_SITE_AUDIT_DEBUG=ONexport PER_SITE_AUDIT_DEBUG

4 Update the Common.csh file as follows:setenv PER_SITE_AUDIT_DEBUG ON

RECIPROCATE_NBR

The RECIPROCATE_NBR determines if a Reciprocal Neighbor is automatically created when auser creates a Neighbor for a cell. For example, when CELL B is defined as the Neighbor ofCELL A, the OMC-R assumes that CELL A is also the Neighbor of CELL B and creates theReciprocal Neighbor relationship between CELL A and CELL B. This RECIPROCATE_NBRdefault set to TRUE.

USE_LONG_SITE_NAME

When the variable USE_LONG_SITE_NAME is set to ON, the operator is able to create a SITEname of maximum 41 characters else it restricts to 31 characters.

If the OMC already has a SITE name with a maximum of 31 characters, set theUSE_LONG_SITE_NAME variable to ON to launch the OMC GUI.

GUI processes environment variables

This section lists the user configurable GUI processes environment variables.

These environment variables are defined in the /usr/omc/config/global/mmiProcConfig.cshfile.

ADDINFO_IN_HEX

This environmental variable is present in the /usr/omc/current/config/Common.csh file.

The ADDINFO_IN_HEX environment variable displays additional alarm information (with theexception of EAS alarms) in hex. Additional information for EAS alarms is displayed in ASCIItext.

The ADDINFO_IN_HEX variable has a default value of 1 and a valid range of 0 or 1. To switchoff the additional alarm information, set this variable to 0.

ALG_WARNING

The ALG_WARNING by default set to Y. This environment variable determines whether or not awarning should be issued on the last in-service ALG.

68P02901W19-S 6-13

Oct 2009

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 populateof the Relative Distinguished Name (RDN) instance field with the next available RDN instancewhen creating a device through the OMC-R GUI. This enables the OMC-R operator to createdevices in the correct order without having to find out what the next RDN instance number is inthe sequence. It also helps to prevent devices from being created out of sequence. Althoughthe RDN instance is created automatically, a different valid RDN instance can still be chosenwhen creating a device.

The AUTO_GEN_RDN variable is set to 0 by default (disabled).

• If this variable is set to 1, the Auto Generate RDN feature is enabled.

• If this variable is set to any other value, the Auto Generate RDN feature is disabled.

Use the following procedure to enable the AUTO_GEN_RDN variable:

Procedure 6-3 Enabling AUTO_GEN_RDN

1 Login as omcadmin.

2 Enter the following command:cd /usr/omc/config/global/env

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

4 Update the file Common.csh as follows:setenv AUTO_GEN_RDN 1

5 Stop and restart the OMC-R as described in Manual startup andshutdown of OMC-R software on page 7-12 to activate these changes.

AUTO_POP_CELLID

The AUTO_POP_CELLID environment variable is used to enable or disable the automaticpopulation of Cell IDs when creating an RTF in the RTF Detailed View. When enabled, the GSMCell ID field is auto populated with the Cell ID that the RTF Group belongs to, if an RTF hasalready been created under an associated RTF Group. This saves time, as it is unnecessaryto enter details in the GSM Cell ID field for an RTF, other than the first radio equipped tothat RTF Group.

The AUTO_POP_CELLID variable is set to 0 by default (disabled).

• If this variable is set to 1, the Auto Populate Cell ID feature is enabled.

• If this variable is set to any other value, the Auto Populate Cell ID feature is disabled.

6-14 68P02901W19-S

Oct 2009

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.

2 Enter the following command:cd /usr/omc/current/config

3 Update the file Common.sh as follows:AUTO_POP_CELLID=1export AUTO_POP_CELLID

4 Update the file Common.csh as follows:setenv AUTO_POP_CELLID 1

5 Stop and restart the OMC-R as described in Manual startup andshutdown of OMC-R software on page 7-12 in order to activate thesechanges.

AUTOSTART_PMGUI

This environment variable is associated with the PM GUI automatic start operation. By default itis set to 0 (disabled).

AX_LANG

This variable is used to override the language used in the ax_prof file. See also the LANGUAGEvariable.

BSS_NAMING

This variable can be used to display BSS parameter names in the Detailed View. If BSS_NAMINGis set then the attributes are displayed with BSS names, otherwise they are displayed withOMC names.

BSS_VER

This variable defines the BSS software version for example, BSGSM 1.8.0.0.

COUNTRY_CODE

The COUNTRY_CODE environmental variable is defined by the GSM operator license.

DBNAME

This variable defines the database name for example, omc_db.

68P02901W19-S 6-15

Oct 2009

GUI processes environment variables Chapter 6: OMC-R Environment variables

DEF_GSM_CELL_ID

This environment variable is the default GSM Cell ID. It is set to the $COUNTRY_CODE-$NETWORK_CODE-0000-000 variable by default.

DEFAULT_REMOVE_CLEARED_ALARM

This environment variable is associated with the Automatic Clearing of the Alarms operation. Itenables or disables the removal of a cleared alarm.

DEFAULT_REMOVE_CLEARED_ALARM_TIME

This environment variable is associated with the Automatic Clearing of the Alarms operation. Itsets the allowable interval, in seconds, to remove a cleared alarm.

DOUBLE_CLICK_NEXT

The DOUBLE_CLICK_NEXT environment variable is associated with the Map Display. By defaultthis variable is defined as FALSE (=0) (disabled).

ENABLE_AUTO_EMAIL_ON_REASSIGN

The ENABLE_AUTO_EMAIL_ON_REASSIGN environment variable is associated with the autoe-mail on the Alarm Reassignment operation. It enables or disables the automatic e-mailnotification, to reduce the amount of e-mail being generated when alarms are reassigned. Bydefault this variable is defined as TRUE (=1) (enabled).

INFORMIXDIR

The INFORMIXDIR environment variable defines the path to where Informix is installed on thesystem. By default, it is set to /usr/informix.

LANGUAGE

The LANGUAGE variable defines the language set used within the OMC-R.

6-16 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration GUI processes environment variables

MAXCHANGENOTIFYCALLS

This environment variable is present in the /usr/omc/current/config/Common.csh file. Itallows the OMC system administrator to specify the number of status queries processed by theGUI. It has a default value of 1000.

NOTEMotorola does not recommend modification of this variable from its default value.

Use the following procedure to set the value of the environment variableMAXCHANGENOTI-FYCALLS:

Procedure 6-5 Setting the value of MAXCHANGENOTIFYCALLS

1 Login as user omcadmin on the single platform processor.

2 Locate the file: /usr/omc/config/global/env/Common.csh.

3 Add the following line at the end of the Common.csh file:setenv MAXCHANGENOTIFYCALLS <value>.

4 All GUIs should be restarted in order to activateMAXCHANGENOTIFYCALLS.

MMI_ALARM_STATE_WIDTH

TheMMI_ALARM_STATE_WIDTH environment variable specifies the pixel width of the AlarmState field. It has a default value of 110.

MMI_CLEAR_INACTIVE_FMIC

This environmental variable default value is set in the /usr/omc/current/con-fig/env/pmProcConfig.csh file. To set a non-default value for this variable modify the/usr/omc/config/global/env/Common.csh file.

This environment variable is set to TRUE for all users to enable all users to clear inactiveFMIC alarms from the system.

MMI_EVENT_ADDITIONAL_INFO_WIDTH

The MMI_EVENT_ADDITIONAL_INFO_WIDTH environment variable specifies the pixelwidth of the Event Additional Information field. It has a default value of 180.

MMI_EVENT_ID_WIDTH

The MMI_EVENT_ID_WIDTH environment variable specifies the pixel width of the Event IDfield. It has a default value of 35.

68P02901W19-S 6-17

Oct 2009

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 EventInformation field. It has a default value of 650.

MMI_EVENT_OBJ_CLASS_WIDTH

TheMMI_EVENT_OBJ_CLASS_WIDTH environment variable specifies the pixel width of theObject Class field. It has a default value of 220.

MMI_EVENT_OBJ_INSTANCE_WIDTH

TheMMI_EVENT_OBJ_INSTANCE_WIDTH environment variable specifies the pixel width ofthe Object Instance field. It has a default value of 180.

MMI_EVENT_OPERATOR_NAME_WIDTH

TheMMI_EVENT_OPERATOR_NAME_WIDTH environment variable specifies the pixel widthof the Operator Name field. It has a default value of 80.

MMI_EVENT_TIME_WIDTH

TheMMI_EVENT_TIME_WIDTH environment variable specifies the pixel width of the EventTime field. It has a default value of 120.

MMI_EVENT_TYPE_WIDTH

The MMI_EVENT_TYPE_WIDTH environment variable specifies the pixel width of the EventType field. It has a default value of 165.

MMI_EVT_FILTER_NUM_LOGS

This environment variable defines the number of filter event logs. It has a default value of 2.

MMI_START_WINDOW_AS_UNSPLIT

The MMI_START_WINDOW_AS_UNSPLIT environment variable determines whether theAlarm window will start as split or unsplit. Values:

• NULL: The alarm window starts as normal (split).

• NOT NULL: The alarm window starts as unsplit.

NETWORK_CODE

As defined by customer.

6-18 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration GUI processes environment variables

OMCAUDIBLESEVERITY

The OMCAUDIBLESEVERITY environment variable affects the generation of the alarm aswell as the alarm severity. A beep is emanated from the sound card as the alarm is generatedand a hooter sets off the distinctive alarm sound depending upon the severity of the alarm.Both these operations are dictated by the values of the GUI process environment variable,OMCAUDIBLESEVERITY.

The valid range for this environment variable is 0 to 3 which indicates:

• If this variable is set to zero, the hooter will sound for critical, major, and minor alarms andthe OMC-R will beep for critical, major, minor, and investigate alarms.

• If this variable is set to one, the hooter will never sound and the OMC-R will beep forcritical alarms.

• If this variable is set to two, the hooter will sound for critical alarms and the OMC-R willbeep for critical and major alarms.

• If this variable is set to three, the hooter will sound for critical and major alarms and theOMC-R will beep for critical, major, and minor alarms.

The various alarm severities are described in Maintenance Information: Alarm Handling atthe OMC-R (68P02901W26) manual.

OMCFEATURES

This environment variable enables or disables the OMC-R features.

OMCREDRAW

The OMCREDRAW environment variable enables the map to display an update in the samewindow when either Next or Previous is selected from the View menu.

OMC_TOP

The OMC_TOP environment variable is used by the OMC-R software and, by default, is set to/usr/omc.

PRINTER

The PRINTER variable specifies the printer device used for printing. By default, PRINTERis set to lp, allowing a user to print to the printer device lp.

REGION

The REGION environment variable determines whether regions are used in the OMC-R GUI.The default value is 0 (disabled).

68P02901W19-S 6-19

Oct 2009

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.csh file. To set a non-default value for this variable,modify the /usr/omc/config/global/env/Common.csh file. The variable is used by the OMC-Rsoftware to allow or prevent any other operation to be run parallel with a Resync operation.

The RESYNC_LOCKING variable is set to 0 by default (disabled).

• If this variable is set to 1, Resync Locking is enabled.

• If this variable is set to 0, Resync Locking is disabled and any operation can run in parallelwith a Resync operation.

Use the following procedure to enable RESYNC_LOCKING:

Procedure 6-6 Enabling AUTO_GEN_RDN

1 Log on as omcadmin.

2 Enter the following command:cd /usr/omc/config/global/env

3 Update the file Common.sh as follows:RESYNC_LOCKING=1export RESYNC_LOCKING

4 Update the file Common.csh as follows:setenv RESYNC_LOCKING 1

5 Stop and restart the OMC-R as described in Manual startup andshutdown of OMC-R software on page 7-12 to activate these changes.

SCROLL_TO_BOTTOM

The SCROLL_TO_BOTTOM environment variable is associated with the PLMN alarm window.When SCROLL_TO_BOTTOM is set to TRUE, the alarms output is pushed to the bottom ofthe alarm window so that the latest alarm can be viewed immediately on opening the PLMNalarm window. The default value is FALSE. To reconfigure this variable use Procedure 1 inChanging an environment variable on page 6-26.

SITE_NAMING

This environment variable is associated with the Navigation Tree Site Name IDs. The defaultvalue is 0 (disabled).

TTY_FILTER

The TTY_FILTER environment variable is used to enable remote login sessions to filterasynchronous output from the BSS. The variable can be set to 0 or 1, and by default the variableis set to 1, which displays all output arriving from the BSS.

6-20 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration RLOGIN variables

RLOGIN variables

The Remote Login variables are set in the $OMC_TOP/config/global/OMC.CNFG file.

RL_LOGCMDS

The RL_LOGCMDS environment variable controls the logging facility of the BSS commands. Ithas a default value of YES (ON) and valid options of YES or NO.

This variable takes precedence over the variable RL_LOGRESPS: if RL_LOGCMDS is set toNO and RL_LOGRESPS set to YES then no logging is performed. To reconfigure this variablerefer to procedure 2 in Changing an environment variable on page 6-26.

RL_LOGRESPS

The RL_LOGRESPS environment variable enables logging of the BSS command responses. Ifset to YES then any responses are logged along with the commands.

It has a default value of NO (not to log the responses) and valid options of YES or NO.

The variable RL_LOGCMDS takes precedence over this variable. If RL_LOGCMDS is set to NOand RL_LOGRESPS is set to YES then no logging is performed. To reconfigure this variable,use procedure 2 in Changing an environment variable on page 6-26.

RL_SESSIONS

The RL_SESSIONS environmental variable specifies the maximum number of simultaneousremote login sessions allowed.

The valid range of values for this variable is between 1 and 90.

If the environmental variable is not set, or is set to an invalid value, the default value of 60 isused. To reconfigure this variable, use procedure 2 in Changing an environment variable onpage 6-26.

RL_TIMER_DT

The RL_TIMER_DT environment variable is used as a timeout value for data transfer. If thistimer value is exceeded, the user is logged out of their remote login session.

It has a default value of 1200 seconds and a range of any positive or negative value or 0. Settingthis environment variable to any non positive value (including zero) results in no timeoutsupervision being performed. To reconfigure this variable, use procedure 2 in Changing anenvironment variable on page 6-26.

68P02901W19-S 6-21

Oct 2009

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.25 connectionestablishment phase.

It has a default value of 25 seconds and a valid range of any positive integer. The defaultvalue is used if the environment value is set to a non positive value (including zero) results inthe default value being used. To reconfigure this variable use procedure 2 in Changing anenvironment variable on page 6-26.

FM_audit variables

The FM_audit variables are set in the $OMC_TOP/config/global/FM_audit.CNFG file.

FM_CPU_AUDIT

The FM_CPU_AUDIT environment variable controls whether a CPU audit is run.

If set to YES then Critical or Major alarms is raised if the CPU load goes above thresholds thatare set in the FM_audit.CNFG file.

It has a default value of NO (OFF) and provides valid options of NO or YES.

To reconfigure the variable, use procedure 2 in Changing an environment variable on page 6-26.(where FMMGR is the mnemonic process).

FM_MEM_AUDIT

The FM_MEM_AUDIT environment variable controls whether a Memory audit is run.

If set to YES then Critical/Major alarms is raised if Memory usage goes above thresholds thatare set in the FM_audit.CNFG file.

It has a default value of NO (OFF) and valid options of NO or YES.

To reconfigure the variable use procedure 2 in Changing an environment variable on page 6-26.(where FMMGR is the mnemonic process).

FM_IERROR_ALLOWED

The FM_IERROR_ALLOWED environment variable specifies the number of input packet errorsthat are permitted within a sample period before an alarm is triggered.

The default is 0, meaning that the alarm is triggered by just one error.

FM_OERROR_ALLOWED

The FM_OERROR_ALLOWED environment variable specifies the number of output packeterrors that are permitted within a sample period before an alarm is triggered.

The default is 0, meaning that the alarm is triggered by just one error.

6-22 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration CSMMAIN variables

FM_OHUNG_ALLOWED

The FM_OHUNG_ALLOWED environment variable specifies the number of transmit hungerrors that are permitted within a sample period before an alarm is triggered.

The default is 0, meaning that the alarm is triggered by just one error.

CSMMAIN variables

The Call Success Monitoring process (CSMMAIN) requires three variables that are set in the$OMC_TOP/config/global/omc.CNFG file.

To reconfigure these variables, use procedure 2 in Changing an environment variable on page6-26. (where CSMMAIN is the mnemonic process).

CSM_ENABLED

The CSM_ENABLED environment variable controls the way in which the Call SuccessMonitoring (CSM) feature is used. It is a three digit binary number in which each digit can beset to 1 to enable a CSM function, or zero to disable that function:

• If all three digits are set to zero, CSM is disabled (the default).

• If the first digit is set to 1, CSM is enabled for sleeping cell detection.

• If the second digit is set to 1, CSM is enabled for sleeping carrier detection.

• If the third digit is set to 1, CSM is enabled for sleeping timeslot detection.

The system allows any combination of the three functions to be enabled.

CALL_SUCCESS_THRESHOLD

The CALL_SUCCESS_THRESHOLD environment variable defines the minimum acceptablepercentage of successful calls per cell. The default is 80%.

This is used to detect sleeping carriers. If the call success rate falls below this threshold, theCSMMAIN process generates an alarm. This variable is set once per network and cannotbe set on an individual cell basis.

MIN_TOTAL_CALLS

TheMIN_TOTAL_CALLS environment variable determines the minimum total number of callsthat must be made on a cell before the CSMMAIN process tries to detect a sleeping carrier.The default is 25.

This variable ensures that CSMMAIN does not raise an alarm when there are very few calls ona cell in an interval.

68P02901W19-S 6-23

Oct 2009

ResyncCtrl variables Chapter 6: OMC-R Environment variables

ResyncCtrl variables

The environment variables that the Resync Control feature uses, are contained in the followingfile on the system processor: /usr/omc/config/global/RC.CNFG

The ResyncCtrl process periodically reads the RC.CNFG file, so unlike other environmentvariables, any variables changed in this file are picked up without having to perform an OMC-Rsoftware stop and start.

AUTORESYNC

The environment variable AUTORESYNC enables remote sites to be resynchronized to theOMC-R automatically if, for example, a link malfunctions between the two and then comesback into service.

The AUTORESYNC variable can be set to Y or N to enable or disable autosynchronization andautomatically defaults to Y if it is not selected. Autosynchronization occurs automatically,regardless of the setting of the environment variable ENABLERESYNC.

If AUTORESYNC is set to Y, MAX_RESYNCS is set to 10 and MAX_AUTO_RESYNCS is setto 2, then a maximum of ten resync control variables are processed at a time. Out of the tenvariables, two slots are allotted to auto resync and the remaining eight slots for manual resync.If AUTORESYNC is set to N and MAX_RESYNCS equals 10, then all the ten resync slots areused for manual resync. No auto resync is processed as it is disabled.

ENABLERESYNC

The environment variable ENABLERESYNC can be set to Y or N to turn resynchronization ONor OFF. By default this is set to N.

MAX_RESYNCS

This variable is used to define the number of active resyncs allowed to happen at a time. Theactive resync table is defined based on this variable. The default value is 10. The range ofvalues allowed for MAX_RESYNCS is 1 to 15. If MAX_RESYNCS is out of this range, thenthis variable is set to a default value of 10.

MAX_AUTO_RESYNCS

This variable is used to define the number of auto resync allowed to happen at a time. The defaultvalue is 2. The range of values allowed forMAX_AUTO_RESYNCS is 1 toMAX_RESYNCS –1.IfMAX_AUTO_RESYNCS is out of this range, then this variable is set to a default value of 2.

IfMAX_AUTO_RESYNCS is set greater than or equal to number ofMAX_RESYNCS, then thedefault value is used for both, MAX_RESYNCS andMAX_AUTO_RESYNCS.

TIMER

The environment variable TIMER sets the duration Resync Control waits for a resync tocomplete. It specifies the time in seconds.

The duration is set between the values 150 and 3600. By default it is set to 600.

6-24 68P02901W19-S

Oct 2009

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 tocleanup and exit gracefully. It is used by OMC-R processes during OMC shutdown.

The default value is 30 as per GSR9 1900.34 load, when this timer was introduced. The defaultvalue is 40 as per GSR9 1900.35 load onwards.

This parameter is user configurable and is present in the file /usr/gsm/current/config/INIT.CNFG.In case the processes need more time to exit gracefully the timer value can be increased suitably.

Follow Procedure 6-7 to increase the timer value:

Procedure 6-7 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.CNFG

4 OMC start

68P02901W19-S 6-25

Oct 2009

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, use of one of the two methods.

• Method 1

Used for changing an environment variable in any of the following files:

/usr/omc/config/global/env/mmiProcConfig.csh

/usr/omc/config/global/env/pmProcConfig.csh

/usr/omc/config/global/env/mibProcConfig.csh

• Method 2

Used for changing an environment variable in the following file:

OMC.CNFG

Method 1

The method involves the following:

• Edit the customizable version of the .csh file in /usr/omc/config/global/env where thevariable is defined and make the necessary change. If turning off an environment variable,it is not sufficient to remove the line or comment it out. Instead comment out the old lineand add a new line containing an unsetenv <variable_name>.

• Stop the OMC-R by issuing the omc stop command.

• Log out and logging back in again. This sources the environment files automatically.

• Restart the OMC-R by issuing the omc start command.

• Verify whether the variable is set up correctly by echoing it to the screen.

For example, use the following procedure to modify the ATC_TIMEOUT variable:

Procedure 6-8 Changing an environment variable using Method 1 (Example 1)

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 themibProcConfig.csh file using the vi editor.

Continued

6-26 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Methods for changing an environment variable

Procedure 6-8 Changing an environment variable using Method 1 (Example 1)(Continued)

The change is automatically propagated to the mibProcConfig.sh file.Use the following command to edit the file:vi mibProcConfig.csh

3 Stop the OMC-R as described in Manual startup and shutdown ofOMC-R software on page 7-12.

4 Log out and login again.

5 In a new Xterm window, login as omcadmin and check if a new valueis assigned:echo $ATC_TIMEOUT

6 In the same window, restart the OMC-R as described in Manual startupand shutdown of OMC-R software on page 7-12.

Method 2

The method involves the following:

• Login as omcadmin and edit the appropriate environment variable within the OMC.CNFGfile.

• Use the utility omctool to reconfigure the process associated with this environmentvariable. The process can be defined by its mnemonic name. An example is the RLOGINmnemonic process. For more information on mnemonic processes, see omctool utility inthe Restartable processes on page 2-49 section.

• OMCINIT periodically polling selected processes to check for particular external eventsthat may have occurred. Reconfiguration occurs at the next poll.

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.CNFG file using the vieditor:vi OMC.CNFG

3 Invoke the omctool utility using the following parameters:omctool -m RLOGIN -cReconfiguration takes place at the next poll.

Example 2: The following procedure modifies the CSMMAIN variables:

68P02901W19-S 6-27

Oct 2009

Methods for changing an environment variable Chapter 6: OMC-R Environment variables

Procedure 6-10 Changing an environment variable using Method 2 (Example 2)

1 Login as omcadmin on the system processor and change directoryas follows:cd /usr/omc/config/global/env

2 Modify the CSMMAIN variables in the OMC.CNFG file using the vieditor:vi OMC.CNFG

3 Invoke the omctool utility with the appropriate parameters:omctool -m CSMMAIN -cReconfiguration happens at the next poll.

Example 3: The following procedure modifies the Parser variables:

Procedure 6-11 Changing an environment variable using Method 2 (Example 3)

1 Login as omcadmin on the system processor and change the directoryas 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 using the following parameters:omctool -m PARSER_1 -cReconfiguration happens at the next poll.

6-28 68P02901W19-S

Oct 2009

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. Thestatus of the Consolidated Alarms is set up in the following files:

• /usr/omc/config/global/env/pmProcConfig.csh

• /usr/omc/config/global/env/mibProcConfig.csh

• /usr/omc/config/global/env/mmiProcConfig.csh

There are three possible levels of consolidation:

• Level 1

The device mode map is default, secondary alarms are displayed. The line entry value inthe three files is SETENV CONSOLIDATION 1.

• Level 2

The device mode map is default, secondary alarms are suppressed. The line entry value inthe three files is SETENV CONSOLIDATION 2.

• Level 3

The subscriber mode map is default, secondary alarms are suppressed. The line entryvalue in the three files is SETENV CONSOLIDATION 3.

NOTERefer to OMC-R Online Help, Network Operation manual for the ConsolidatedAlarms operation.

Setting status of the consolidated alarms

Use the following procedure to set the status of the Consolidated Alarms.

Procedure 6-12 Setting the status of consolidated alarms

1 Login to the system processor as omcadmin and change the directoryas follows:cd /usr/omc/config/global/env

Continued

68P02901W19-S 6-29

Oct 2009

Disabling the status of consolidated alarms Chapter 6: OMC-R Environment variables

Procedure 6-12 Setting the status of consolidated alarms (Continued)

2 Open the pmProcConfig.csh file using the vi editor:vi pmProcConfig.csh

3 Enter the following line entry at the end of the file:SETENV CONSOLIDATION <x>Where <x> is:1 for Level 1.2 for Level 2.3 for Level 3.

4 Close the pmProcConfig.csh file using the vi editor.

5 Repeat step 1 to step 3 for the files mibProcConfig.csh andmmiProcConfig.csh files.

6 Stop and restart the OMC-R as described in Manual startup andshutdown of OMC-R software on page 7-12 in order to activate thesechanges.

7 Restart all the GUI servers or clients.

Disabling the status of consolidated alarms

Use the following procedure to disable the status of the consolidated alarms:

Procedure 6-13 Disabling the status of the consolidated alarms

1 Login to the system processor as omcadmin and change the directoryas follows:cd /usr/omc/config/global/env

2 Open the pmProcConfig.csh file using the vi editor:vi pmProcConfig.csh

3 Delete the SETENV CONSOLIDATION <x> line entry and enter thefollowing line entries:vi pmProcConfig.cshWhere <x>is:1 for Level 1.2 for Level 2.3 for Level 3.

UNSETENV CONSOLIDATIONClose the pmProcConfig.csh file using the vi editor.

4 Repeat step 1 to step 3 for the files mibProcConfig.csh andmmiProcConfig.csh files.

5 Stop and restart the OMC-R as described in Manual startup andshutdown of OMC-R software on page 7-12 in order to activate thesechanges.

6 Restart all the GUI server or clients.

6-30 68P02901W19-S

Oct 2009

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 thefollowing files:

• /usr/omc/current/config/env/Common.csh

Defines the variables used by the system processes.

• /usr/omc/current/config/env/mmiProcConfig.csh

Defines the variables used by the GUI processes, which interact with the GUI server orclients.

There are .sh versions of these files (Bourne Shells), which are automatically updated if changesare made in the .csh versions.

NOTEThe variables should only be changed by qualified personnel under guidance fromMotorola Support. Any unauthorized changes may not be supported by Motorola andmay result in system and/or performance degradation. Contact Motorola Supportfor further information.

The non-user configurable environment variables that are specified in the/usr/omc/current/config/env/Common.csh file are listed in Table 6-1.

Table 6-1 Non—user configurable variables in the Common.csh file

Variable name Value

ADMIN_BIN $ADMIN_ROOT/sbin

ADMIN_ROOT $OMC_TOP/current

AUDITDIR $OMC_TOP/logs

AU_ALF_DIR $OMC_TOP/logs/ListDir

CMAUDITDIR $OMC_TOP/logs

CMUTIL_LOG $OMC_TOP/logs

CM_CFG_GLOB $OMC_TOP/config/global

CM_LOG $OMC_TOP/logs

CM_ROOT $OMC_TOP/current

COMMS_LOG $OMC_TOP/logs

Continued

68P02901W19-S 6-31

Oct 2009

Introduction to non user configurable environment variables Chapter 6: OMC-R Environment variables

Table 6-1 Non—user configurable variables in the Common.csh file (Continued)

Variable name Value

COMMS_ROOT $OMC_TOP/current

{34164}CRITICAL_STATS_LOG

$OMC_TOP/ne_data/critical_stats

CT_LOG $OMC_TOP/ne_data/ct_logs

DATAGENHOST Host name of DataGen processor (if DataGen is enabled)

DBDATE DMY4-

DBMS_LOG $OMC_TOP/logs

DBMS_ROOT $OMC_TOP/current

DBNAME /mib_db

DBPATH //omc_sys

DBROOT $OMC_TOP/ne_data/dbroot

DEFAULT_SHUTDOWN_TIME 30

EM_LOG $OMC_TOP/ne_data/ev_logs

EM_POLL_COUNT 800

EM_ROOT $OMC_TOP/current

EM_RX_QSIZE_ALARM 5120

EM_RX_QSIZE_FLUSH 10240

EM_TX_QSIZE_MMI 5120

FMPATH $OMC_TOP/ne_data/raw_stats

GLOBAL_LOG_DIR $OMC_TOP/logs/ipc

INFORMIXDIR /usr/informix

IPC_CONFIG /usr/omc/current/config/ipc.cfg

IPC_HELP_TEXT $CM_ROOT/config/ipc_help2.txt

LDM_LOG $OMC_TOP/logs

LDM_ROOT $OMC_TOP/current

LMAUDITDIR $OMC_TOP/logs

LMBINDIR $OMC_TOP/current/bin

LMDATA $OMC_TOP/current/config

LMTEMPDIR $DBROOT/tmp

LOG_TO_SCREEN 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

Operating Information: OMC-R System Administration Introduction to non user configurable environment variables

Table 6-1 Non—user configurable variables in the Common.csh file (Continued)

Variable name Value

OMC_TOP /usr/omc

PM_ASYNC_LOG $OMC_TOP/logs

PM_LOG $OMC_TOP/logs

PM_LOG_FILE $PM_LOG

PM_PARSER_LOG $PM_LOG

PM_ROOT $OMC_TOP/current

PS “ps -ef”

RETRY_TIMEOUT 15

RL_BSSLOGDIR $OMC_TOP/logs/bss

RL_TIMER_IPC 60

SYS_BIN $SYS_ROOT/bin

SYS_CONFIG $SYS_ROOT/config

SYS_LOG $OMC_TOP/logs

SYS_ROOT $OMC_TOP/current

UNLOAD_DIR $OMC_TOP/ne_data/unload_stats

The non-user configurable environment variables that are specified in the/usr/omc/current/config/env/mmiProcConfig.csh file are listed in Table 6-2.

Table 6-2 Non—user configurable variables in the mmiProcConfig.csh file

Variable name Value

OMC_TOP /usr/omc

ADMIN_BIN $ADMIN_ROOT/sbin

ADMIN_ROOT $OMC_TOP/current

APPLIX $OMC_TOP/current/bin/PMGUI

AUDITDIR $OMC_TOP/logs

AUTO_GEN_RDN 0

AUTO_POP_CELLID 0

AXHOME $OMC_TOP/current/bin/axhome

BATCH_IPC_TIMEOUT 600

BATCH_NERESP_TIMEOUT 30

BSS_VER BSGSM_1.6.0.x

CMAUDITDIR $OMC_TOP/logs

CM_LOG $OMC_TOP/logs

CM_ROOT $OMC_TOP/current

Continued

68P02901W19-S 6-33

Oct 2009

Introduction to non user configurable environment variables Chapter 6: OMC-R Environment variables

Table 6-2 Non—user configurable variables in the mmiProcConfig.csh file(Continued)

Variable name Value

CMUTIL_LOG $OMC_TOP/logs

COMMS_LOG $OMC_TOP/logs

COMMS_ROOT $OMC_TOP/current

CURRENT $OMC_TOP/current

DBNAME omc_db

DBPATH //omc_sys

DBROOT $OMC_TOP/ne_data/dbroot

DOUBLE_CLICK_NEXT 0

EM_LOG $OMC_TOP/ne_data/ev_logs

EM_ROOT $OMC_TOP/current

ENABLE_ACCESS_LOG 0

EP_ALARM_SUB_LIST_NAME ‘.$MAP_ALARMS’

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

‘.$ALM_ALARMS’

MMI_DAEMON /usr/omc/current/bin/mmi_daemon

MMI_EVT_DEFAULT_SUBSLIST_NAME

‘.$EVT_EVENTS’

MMI_LOG $OMC_TOP/logs

MMI_NO_ALARM_PIXMAP siren_off

MMI_OOS_ON_PIXMAP “oos_pixmap_on”

MMI_OOS_PIXMAP “oos_pixmap”

MMI_OOS_SUB_NAME “.$SC_EVENTS”

MMI_PRIMARY_FONT ‘-*-helvetica-medium-r-normal–*-140-*’

Continued

6-34 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Introduction to non user configurable environment variables

Table 6-2 Non—user configurable variables in the mmiProcConfig.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

OMC_HELP_PATH $OMC_TOP/config/local/help

OMC_IPC_CONFIG $NMSROOT/config/ipc.cfg

OMCTOP $OMC_TOP

PMGUI /usr/omc/current/bin/PMGUI

PM_ASYNC_LOG /usr/omc/logs

PM_LOG $OMC_TOP/logs

PM_LOG_FILE /usr/omc/log

PM_PARSER_LOG /usr/omc/logs

PM_ROOT $OMC_TOP/current

SITE_NAMING 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

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 correcttime against them, it is important that the time of NEs and all processors at the OMC-R arekept consistent.

Overview of setting the time at the OMC-R and NEs

This section describes the following procedures:

• Resetting the time and time zone at the OMC-R.

• Setting up a cron job to keep the GUI time synchronized to the system processor time.

• Setting up a cron job to synchronize the NE time with the time at the OMC-R.

Resetting the time

The system processor is the master clock server. The system date (which in UNIX means thedate and time) on the system processor is the default time setting for the OMC-R network.

Use the following procedure to display the current system date.

Procedure 6-14 Display the current system date

1 Enter the following command:date -uThis 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.

NOTEEntering date on the command line results in the dateand time being displayed according to what is specified in/etc/default/init. This is the local time. For example,Thu Dec 14 14:56 SGT 2005

6-36 68P02901W19-S

Oct 2009

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, taking particular care toset the system processor time accurately. Use the following procedure on each processor toconfigure 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 -u <hhmm>For example, date -u 2259 sets the time to 22:59 GMT. The commandsets time to the nearest minute.

3 Ensure that date -u shows the same time on all processors (to withinone or two minutes).

The GUI processor clocks must be set to the same time as the systemprocessor clock whenever the system processor clock is changed.

Configuring system time to local time

To configure the system time to local time, set the time on all the machines, taking particularcare to set the system processor time accurately. Use the following procedure on each processorto configure the system time to local time.

Procedure 6-16 Configuring the system time to local time

1 Login as root.

2 Change the processor time using the following command:date <hhmm>For example, date 2259 sets the time to 22:59 local time. Thecommand sets time to the nearest minute.

3 Ensure that date shows the same time on all processors (to withinone or two minutes).

The GUI clocks must be set to the same time as the system processorclock whenever the system processor clock is changed.

Default time zones in OMC-R

In UNIX, a time zone is a compiled data file containing information about the offset from GMT,which is applied. The offset may vary at different times of the year.

The time zone files are in the /usr/share/lib/zoneinfo directory. Reference the files in this areafor a list of precompiled time zones.

68P02901W19-S 6-37

Oct 2009

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 notrecommended because they do not support daylight saving.

If the desired time zone has not already been compiled, view the appropriate source filefrom the following:

• Africa

• Asia

• Australia

• Europe

• North America

• South America

NOTEDo not try to view files starting with capital letters. These are compiled time zonefiles, and they corrupt the terminal display.

The uncompiled time zone file has to be compiled before it is used. Use the following commandsto compile the file:

cd /usr/share/lib/zoneinfo

zic <source_filename>

where source_filename is the name of the source file. For example, Asia.

The compiled data files are stored in the directory /usr/share/lib/zoneinfo/<source_filename.For example, if the source file is Asia then the directory is /usr/share/lib/zoneinfo/asia. Thissetup must be repeated for each processor in the OMC-R.

In the time zone file, search for the appropriate country or city name. The NAME of the zone isused as a time zone. For example, the entry for India reads:

# India

# Zone NAME GMTOFF RULES FORMAT [UNTIL]

Zone Asia/Calcutta 5:30 - IST

This shows that the time zone name for Calcutta is Asia/Calcutta. In addition, it shows that thezone Asia/Calcutta offset 5 hours and 30 minutes ahead of GMT. The letters displayed are IST.

Once the time zone is set, it is advisable to check to see if the time zone works as expected. Tocheck if a time zone is behaving correctly, see Checking the time zone.

6-38 68P02901W19-S

Oct 2009

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. Their use isrecommended because they support daylight saving.

If the desired time zone has not already been compiled, view the appropriate source filefrom the following:

• Africa

• Asia

• Australia

• Europe

• North America

• South America

NOTEDo not try to view files starting with capital letters as these are compiled time zonefiles, and corrupt the terminal display.

The uncompiled time zone has to be compiled before it can be used. Use the followingcommands to compile the file:

cd /usr/share/lib/zoneinfo

zic <source_filename>

where <source_filename> is the name of the source file. For example, Europe. The compileddata files are stored in the directory /usr/share/lib/zoneinfo/<source_filename>.

For example, if the source file is Europe then the directory is /usr/share/lib/zoneinfo/Asia>.This setup must be repeated for each processor in the OMC-R. In the time zone file, search forthe appropriate country or city name. The NAME of the zone may be used as a time zone. Forexample, the entry for Sweden includes daylight saving rules:

# Sweden

# Zone NAME GMTOFF RULES FORMAT [UNIL]

Zone Europe/Stockholm 1:00 - MET 1980 Apr 6 2:00

1:00 M-Eur MET%s

In the example, the time is one hour ahead of GMT, and is called MET. During summer, a prefixis added to indicate daylight saving. This prefix is indicated by %s. Daylight saving for thisexample follows the M-Eur rules.

68P02901W19-S 6-39

Oct 2009

Setting the time zone Chapter 6: OMC-R Environment variables

Europe file format

These rules are given elsewhere in the Europe file. The Europe file contains daylight savingsettings. These settings follow theM-Eur rules. The Europe file is given as follows:

# Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S

Rule M-Eur 1981 max - Mar lastSun 2:00s 1:00 “ DST“

Rule M-Eur 1996 max - Oct lastSun 2:00s 0 -

The first rule detailed in this file denotes the following:

• Daylight saving starts at 02:00 on the last Sunday in March.

• At 02:00 on the last Sunday in March the clock is advanced one hour.

• The daylight saving suffix is DST.

The second rule detailed in this file denotes the following:

• Daylight saving ends at 02:00 on the last Sunday in October.

Once the time zone is set, it is advisable to check to see if the time zone works as expected.

Setting the time zone

Use the following procedure to set the time zone:

NOTEThis procedure requires all processors at the OMC-R to be rebooted.

Procedure 6-17 Setting the time zone

1 Login to each processor (System and GUIs) as user root and edit the/etc/default/init file to contain the line:TZ=<time zone>Where <time zone> is the selected time zone. Examples:To use Middle European Time (MET), enter:TZ=METTo use a city-specific time zone, enter the complete zone name:TZ=<continent>/<city>To set the time zone for Calcutta, enter:TZ=Asia/Calcutta

Continued

6-40 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Synchronizing the time at the OMC-R

Procedure 6-17 Setting the time zone (Continued)

NOTEThis form of time zone must first be compiled on allprocessors using zic.

2 Stop the OMC-R processes. Log in to the system processor asomcadmin, and enter the following command:omc stop

3 As <root> on the system processor and all the GUI processors, rebootthe respective machines using the shutdown command:/usr/sbin/shutdown -g0 -i6 -y

4 After all the machines have restarted, log in as <omcadmin> on thesystem processor and enter the following command:omc stopWait until the OMC-R processes have stopped (OMC-R processesattempt 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, enter the followingcommand:date

Synchronizing the time at the OMC-R

The timesynch script synchronizes the GUI processor clock with the clock on the systemprocessor.

NOTEIt is strongly recommended that the timesynch script should be run on all theOMC-R systems.

The timesynch script should be run at a period of low activity. For example, daily at 30 minutespast midnight.

Use the following procedure to check if the timesynch script has been set up as a cron job onevery GUI processor and indicates suitable parameters.

Procedure 6-18 Synchronizing the time at the OMC-R

1 Login as root on the relevant GUI processor.

Continued

68P02901W19-S 6-41

Oct 2009

Synchronizing the time at the NEs Chapter 6: OMC-R Environment variables

Procedure 6-18 Synchronizing the time at the OMC-R (Continued)

2 Enter the following command to locate the timesynch line entry in theroot crontab file:crontab -l | grep timesynchScreen 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 midnightevery day.

3 If the line entry is missing, add it, using the example given as atemplate.Refer to Scheduling cron jobs using the batch scheduler on page 5-9for details.

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

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

man crontab

Synchronizing the time at the NEs

The site_timesynch script synchronizes the NE time with the time on the system processor.This saves having to check and reset NE duration manually.

NOTEIt is strongly recommended to schedule the site_timesynch script on all the OMC-Rsystems.

The site_timesynch script should be executed:

• At least 10 minutes after the timesynch script.

• At a quiet time For example, in the early morning.

• Once every week.

• After any daylight saving changes. For example, if daylight saving changes take place at02:00 on Sunday mornings, site_timesynch should be run shortly after 03:00 on Sundays.

6-42 68P02901W19-S

Oct 2009

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 anomcadmin 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 omcadmincrontab file:crontab -l | grep site_timesynchScreen 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 optionalBSS/RXCDR level 2 passwords of each BSS/RXCDR NE that has a level2 password set. If level 2 passwords are not set at the BSS/RXCDR, thenthe site_timesynch command requires no passwords as parameters.This example runs the site_timesynch script at 03:10 every Sunday.

3 If the line entry is missing, add it, using the example given as atemplate.Refer to Scheduling cron jobs using the batch scheduler on page 5-9for details on setting up cron jobs.

4 Repeat steps 1, 2 and 3 until all the GUI processors have beenconfigured.

5 For details of the syntax of the crontab file, open a terminal windowand enter:man crontab

68P02901W19-S 6-43

Oct 2009

Synchronizing the time at the NEs Chapter 6: OMC-R Environment variables

6-44 68P02901W19-S

Oct 2009

Chapter

7

System startup and shutdown■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

68P02901W19-S 7-1

Oct 2009

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 inthe 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-offoperations of the hardware.

CAUTIONAll users must be informed before changing the state of any of the processors, sinceuser processes could be terminated.

The system processor and the optional GUI processors have been initially configured (oninstallation) to enter multiuser mode (run level 3) automatically after power-on and bootingsequences have been completed. The result of a successful startup is the login display.

CAUTIONThe GUI processor must not be run in the background using >gui &. The GUIexecutable constantly reads the input from the terminal in which it was started. If theGUI is run in the background and the connection with the terminal is lost, this maycause the GUI to hang. It also prevents the operator from providing Motorola withdiagnostic data if for some reason there was an error reported on the GUI functionality.

The following topics are described in this chapter:

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

7-2 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 (orstates or run levels), which vary according to the type of operation required. All processorsnormally operate in run level 3.

CAUTIONThe system administrator should issue a UNIX wall command before changing themode on any processor. This command notifies other users of an impending systemchange.

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 integritychecks 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 consoleterminal is usable in this mode.

• Run level 2:

Run level 2 is a multiuser mode where all local file systems are mounted, port monitorservices 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 defaultstartup 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 systemis shut down (just as if run level 0 had been entered), and then automatically rebootedto the default run level.

• Run level S:

Run level S brings the system to the single user level. At this user level, some file systemsare 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 refersto 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 newrun level. Scripts starting with K are called with an argument of stop, whereas scriptsstarting 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 thefiles 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.dexecute a script in /etc/init.d, by means of a softlink. Also, the name of this script is equalto the name portion of the file.

In Solaris10, many system processes which were previously organized under the /etc/rcn.d arenow managed by the Service Management Facility (SMF). For further details on SMF, manuallystarting, 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 andshutdown are as follows:

• rc0

Executed by shutdown command to run the scripts in the rc0.d directory for systemchange 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 inupward or downward transitions to all system run levels.

The system processor and the optional GUI processors have been initially configured (oninstallation) to enter multiuser mode (run level 3) automatically after power-on and bootingsequences 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 andINFORMIX are shown in Figure 7-1.

Figure 7-1 Startup and shut down directory structures on the system processor

7-6 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 tohave 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 thesystem 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 dothis, 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 is

-y Shut down the system without asking for confirmation(optional). If not specified, then system administrator mustconfirm process termination.

-g<grace_period>

The time in seconds that the system waits after notifying theusers that the system is going to shutdown. The default valueis 60 seconds.

-i<init_state>

The run level to be entered.

7-8 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 databaseand also has several OMC-R applications running on it. Sometimes, it is necessary to partiallyshut 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 INFORMIXdatabase 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 usermode:

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 -yThe 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 willhave 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 processorfrom 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 -sThe 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 rebootingthe system are disregarded.

Switching to PROM mode

The system must be halted or shut down when performing certain maintenance or administrativetasks, 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 cleanshutdown and brings the system to PROM monitor level, it does not run the rc0 scripts. It isrecommended that the halt command is not used, if changes have been made to the rc0 scripts.

7-10 68P02901W19-S

Oct 2009

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, execute the following command as user root atthe OK prompt:

boot

This command will shut down and bring the system up to run level 3, multi-user mode.

The reboot command

The /user/sbin/reboot command performs a clean shutdown and brings the system to run level 3by default. This command is similar to the init 0 command but does not run the rc0 scripts.

To reboot the system, execute the following command as user root.

reboot

Some useful parameters can be included in this command, for example,

reboot -- -s

This parameter enables the system to switch on to a single user mode after a reboot:

reboot -- -r

This parameter allows the reconfiguration of the system, for example, the addition of aperipheral device.

68P02901W19-S 7-11

Oct 2009

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 softwareentities manually. The automatic method is built into the appropriate processor startup orshutdown routine, while the manual method is started from the command line.

The UNIX ps utility displays processes operational, if the OMC-R software is running on thesystem.

Starting up OMC-R software

Use the following procedure to start the OMC-R software manually.

Procedure 7-3 Starting the OMC-R software manually

1 Login to the system processor as omcadmin.

2 Enter the following command:omc start

3 Log out the system processor.

Shutting down OMC-R software

Use the following procedure to stop the OMC-R software manually.

Procedure 7-4 Stopping the OMC-R software manually

1 Login to the system processor as omcadmin.

2 Enter the following command:omc stop

3 Logout the system processor.

NOTEIt is recommended to run the tail command during OMC startup. It should be ofthe form tail -f /usr/omc/logs/omcaudityyyymmdd where yyyymmdd is the currentdate.

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, carry out the following procedure.

Procedure 7-5 Checking processes running on the system processor

1 Login to the system processor as omcadmin, and enter:ps -ef |grep +If the OMC software is running, output similar to the following isdisplayed:

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 + 2omcadmin 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 + 1omcadmin 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 + 5omcadmin 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 + 6omcadmin 821 798 0 Aug 16 ?0:00 /usr/omc/current/bin/x25appl + 7omcadmin 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 + FPCHAN_1 FPADMCHAN_1omcadmin 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 + 3omcadmin 831 798 0 Aug 16 ?0:00 /usr/omc/current/bin/x25appl + 4omcadmin 832 798 0 Aug 16 ?

Continued

68P02901W19-S 7-13

Oct 2009

Checking system processor processes Chapter 7: System startup and shutdown

Procedure 7-5 Checking processes running on the system processor (Continued)

0:32 /usr/omc/current/bin/fm_audit +omcadmin 954 798 0 Aug 16 ?0:00 /usr/omc/current/bin/ResyncCtrl +omcadmin 1062 1058 0 Aug 16 ?0:03/usr/omc/current/bin/gateway +q +c/usr/omc/current/config -r informix +i 5 +aomcadmin 1064 1058 0 Aug 16 ?0:03 /usr/omc/current/bin/resync +q +c/usr/omc/current/config -r informix +i 8 +a 4omcadmin 1065 1058 0 Aug 16 ?0:03 /usr/omc/current/bin/pmProxy +q +c./usr/omc/current/config -r informix +i 7 +aomcadmin 1060 1058 0 Aug 16 ?0:03 /usr/omc/current/bin/emProxy +q +c/usr/omc/current/config -r informix +i 12 +aomcadmin 1063 1058 0 Aug 16 ?0:03/usr/omc/current/bin/scheduler +q +c/usr/omc/current/config -r informix +i 14omcadmin 1058 1 0 Aug 16 ?0:02 /usr/omc/current/bin/monitor +q +c/usr/omc/current/config -r informix +i 4 +aomcadmin 1055 1 0 Aug 16 ?0:02 /usr/omc/current/OSP/bin/nameserver+i 900 +a 9001 +ns 900 localhost 9001omcadmin 1066 1058 0 Aug 16 ?0:03 /usr/omc/current/bin/audit +q +c/usr/omc/current/config -r informix +i 9 +a 40omcadmin 1067 1058 0 Aug 16 ?0:02 /usr/omc/current/bin/callTrace +q +c/usr/omc/current/config -r informix +i 20omcadmin 1068 1058 0 Aug 16 ?0:12 /usr/omc/current/bin/NetExp +q +c/usr/omc/current/config -r informix +i 25 +aomcadmin 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 28omcadmin 26597 26572 0 15:23:58 pts/20:00 grep +somc57:omcadmin >

2 Log out the system processor.

7-14 68P02901W19-S

Oct 2009

Chapter

8

Database Management■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

68P02901W19-S 8-1

Oct 2009

Overview Chapter 8: Database Management

Overview■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This chapter describes the administrative procedures required to maintain the two INFORMIXdatabases.

• PM Database - The Performance Management database (formerly the OMC database), isused to store Performance Management data and Event Management subscriptions alongwith subscription lists.

• CM Database - The Configuration Management database (formerly the MIB database), isused to store Configuration Management and Fault Management (FM) data. Only personnelbelonging to the group omc have write access to the tables within the CM database.

Each database is managed by a separate INFORMIX Dynamic Server (IDS) Version 10. Bothdatabases, and all relevant INFORMIX application modules, are initially installed on the systemprocessor by Motorola personnel. For more information, refer to Installation and Configuration:OMC-R Clean Install (68P02901W47) manual.

The following topics are described in this chapter:

• Overview of database management on page 8-3.

• Database utilities on page 8-4.

• INFORMIX directory structure on page 8-13.

• Shutdown and startup of the PM and CM databases on page 8-16.

• Administering the PM database using the omc_db_maint utility on page 8-23.

• Setting the onconfig parameters on page 8-26.

• Dropping and Recreating the PM database on page 8-30.

• Additional database maintenance procedures on page 8-32.

• Checking the PM database on page 8-34.

• Checking the CM database on page 8-39.

8-2 68P02901W19-S

Oct 2009

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. This utility isrun as a root cron job or it is run manually (see Administering the PM database using theomc_db_maint utility on page 8-23).

The IDS log file for the PM database, $INFORMIXDIR/online.log_OMC, is checked for errorsand check-pointing. The cron job roll_online.log performs an automatic roll-over of this log file.

The /usr/omc/current/sbin/bss_dt_load.sh cron job runs every night before midnight toautomatically load default dates and times into the bss_datetimes table in the PM database.

68P02901W19-S 8-3

Oct 2009

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 inthe administration of the PM and CM databases as follows:

• /usr/informix/bin/onmonitor

• /usr/omc/current/sbin/omc_db_maint

• /usr/omc/current/sbin/db_disconnect

• /usr/omc/current/sbin/db_pm_maint

• /usr/omc/current/sbin/pm_daily_unload

• /usr/omc/current/sbin/pm_purge_check

• /usr/omc/current/sbin/omc_db_ckspace

• /usr/omc/current/bin/pm_manual_parse

The onmonitor utility is run, logged into the system processor, as user id informix. Theomc_db_maint utility is run, logged into the system processor, as user id root. All other utilitiesare run as user id omcadmin unless stated.

8-4 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration onmonitor utility

onmonitor utility

The onmonitor utility is used for INFORMIX database management purposes.

Use the following procedure to invoke onmonitor utility:

Procedure 8-1 Invoking the onmonitor utility

1 Login to the system processor as root.

2 Switch user to informix:su - informix

NOTEIf the onmonitor utility is invoked as any user other thaninformix, a status menu will appear which allows theinterrogation of database parameters but does not allowany changes.

3 Ensure the TERM variable is set to vt100:setenv TERM vt100

4 Setup the correct environment, according to the required database.To access the PM database enter:omc_envTo access the CM database enter:mib_env

5 Enter the following command to start the onmonitor utility:onmonitor

NOTEIf onmonitor is run with an incorrect screen configuration,the menus will not work properly. If this should happen,press e to exit the command line.

CAUTIONDo not use the function keys (F1, F2 and so on) whenworking with IDS, even if the help text indicates otherwise,as they do not always work as expected. Use theCTRL-character key combination or left arrow key.

All onmonitor commands can be performed from the command line. For further informationregarding these commands, refer to the INFORMIX Administrator's Guide documentation.

68P02901W19-S 8-5

Oct 2009

omc_db_maint utility Chapter 8: Database Management

omc_db_maint utility

Use of omc_db_maint

CAUTIONInterrupting an invocation of the omc_db_maint utility before it completes can causedatabase corruption. For this reason, the utility should never be interrupted or killedbefore it has run to completion.

The omc_db_maint utility is used to unload and delete the PM statistics and reporton the database disk usage. The omc_db_maint utility is located in the directory$OMC_TOP/current/sbin and invoked using login id root.

Sub-utilities run within omc_db_maint

The omc_db_maint utility calls the pm_purge_data utility to perform PM statisticsmaintenance (refer to pm_purge_data utility for further details) and pm_daily_unload toperform the daily unload of the previous days statistics (refer to pm_daily_unload utility forfurther details). In addition there is a utility, pm_purge_check, whose function is to check thatthe maintenance has completed successfully and to raise an alarm if it detects any problems(refer to pm_purge_check utility for further details).

The disk usage report is generated using the omc_db_ckspace utility (refer to omc_db_ckspaceutility on page 8-10 for further details). The disk usage report is placed into the omc_db_maintlog file which is located in the $OMC_TOP/logs directory.

NOTEThe percentage of database space used report entered into the omc_db_maintlog file is checked once a week. If the amount of data in the database is growingsubstantially, further investigation is advised.

To ensure that the OMC-R software does not need to be stopped, potentially causing loss ofPM statistics, the db_disconnect utility is also called by the omc_db_maint utility (refer todb_disconnect utility for further details).

Recommendations on the use of omc_db_maint

It is recommended that the omc_db_maint utility should be run daily as a cron job. Thescheduling of the cron job should ideally be performed during low activity periods (for example,after midnight).

Procedures for running omc_db_maint both manually and as a cron job are described inAdministering the PM database using the omc_db_maint utility on page 8-23.

8-6 68P02901W19-S

Oct 2009

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 databasedelete and unload settings, the following parameters are possible when invoking omc_db_maintfrom 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 deleteoperation.

-unload The optional parameter to suppress the unloadoperation.

-force The optional parameter to force the deletion ofdata that has not been unloaded.

An example, on the use of command line parameters for omc_db_maint to perform the deletionbut not the unload:

$OMC_TOP/current/sbin/omc_db_maint -unload

The parameters delete any expired PM statistics from the PM database, but an unload operationto $UNLOAD_DIR is not performed.

pm_purge_data utility

The pm_purge_data utility is responsible for the purging of expired statistics fromthe Performance Management database. It is usually run as a cron job from within theomc_db_maint utility. However, in exceptional circumstances, it can be run from the commandline. The pm_purge_data utility is located in the directory $OMC_TOP/current/sbin andinvoked 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 beenunloaded by the daily unload utility, pm_daily_unload. A command line option can be invokedto override this behavior and force the deletion of statistics that have not been unloaded.

pm_purge_data [-force|-FORCE]

Where is

-force optional parameter to force the deletion ofdata that has not been unloaded.

The Parser must be disconnected while this utility is running. See Administering the PMdatabase using the omc_db_maint utility on page 8-23 for more information on manuallydisconnecting and connecting the Parser and other utilities.

68P02901W19-S 8-7

Oct 2009

pm_daily_unload utility Chapter 8: Database Management

pm_daily_unload utility

The pm_daily_unload utility unloads yesterdays statistics, as well as a snapshot of all non-statistics data, into the directory $OMC_TOP/ne_data/unload_stats/unload_dir.yyyy.mm.ddwhere <yyyy> refers to the current year, <mm> to the current month and <dd> to thecurrent day in this month.

The data is stored in compressed, | delimited ASCII files. This utility, which is stored in$OMC_TOP/current/sbin, is usually invoked from within the omc_db_maint utility. However,it can be invoked from the command line in exceptional circumstances. The utility accepts nocommand line parameters.

pm_purge_check utility

The pm_purge_check utility is responsible for ensuring the daily purge of data has occurred,and that space has been prepared in the database ready for the following days statistics. Theutility must be run as a cron job and should be scheduled to start 2 hours after the databasemaintenance utility (omc_db_maint), and should run every hour until 23:00.

For example, if omc_db_maint is scheduled to start at 04:02 then pm_purge_checkshould be scheduled to start at 06:02, 07:02, 08:02, until 23:02. The utility resides in$OMC_TOP/current/sbin and accepts no command line parameters.

If the utility should find that omc_db_maint has not successfully purged the database, then itsends a major alarm to the OMC. On receipt of this alarm the operator should investigate andcorrect any issues with omc_db_maint. The pm_purge_check utility runs every hour, and willcontinue to send alarms until the problem is rectified, when the alarm will be cleared.

db_disconnect utility

The db_disconnect utility informs OMC-R applications to either disconnect from or reconnectto the database. This utility should form part of any database maintenance procedure whichaffects the tables used by these applications.

Example connect procedures

To connect all applications to the database enter:

$DBMS_ROOT/sbin/db_disconnect connect

To connect the Event Manager application to the database enter:

$DBMS_ROOT/sbin/db_disconnect connect em

To connect the pmProxy application to the database enter:

$DBMS_ROOT/sbin/db_disconnect connect pmproxy

8-8 68P02901W19-S

Oct 2009

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, pmProxy, csm and the Event Manager (EM)applications if the OMC-R database has to be brought online.

NOTEThe $DBMS_ROOT environment variable is only set when the user is logged into thesystem processor as omcadmin.

db_pm_maint utility

Most of the PM database data storage is allocated to PM statistics. To ensure that the databasedoes not become full, the db_pm_maint utility must be run regularly to delete any entities fromthe PM database for which there are no statistics.

The pathname for db_pm_maint utility is:

$DBMS_ROOT/sbin/db_pm_maint

The db_pm_maint utility is run once a week as part of the omc_db_maint utility and would,therefore, not usually be run manually.

Manually running db_pm_maint

To run db_pm_maint on the PM database, the following alias must be entered:

omc_env

The utility is invoked with a set of parameters which specify the operations to perform. Thesyntax for invocation is:

db_pm_maint [-e]

Where is

-e entity consistency; delete all those entities for which thereare no statistics.

NOTEIt is necessary to include the -e flag when running db_pm_maint.

68P02901W19-S 8-9

Oct 2009

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 TBLSpaceallocation in summary format. It can be run against both the PM and CM databases. It is run aspart of the omc_db_maint utility and would, therefore, not usually be run directly.

Manually running omc_db_ckspace

The omc_db_ckspace utility is located in the directory $DBMS_ROOT/sbin.

The syntax for invocation is:

omc_db_ckspace [-u] [-f] {omc | mib}

Where is

-u update statistics for database(s).

-f full table listing printed.

omc PM database.

mib CM database.

If neither PM nor CM database is declared, omc_db_ckspace will run on the PM databaseby default.

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.

2 Disconnect the database by entering the following command:$DBMS_ROOT/sbin/db_disconnect disconnect

3 To run the utility on the PM database, enter the following:$DBMS_ROOT/sbin/omc_db_ckspace omcTo run the utility on the CM database, enter the following:$DBMS_ROOT/sbin/omc_db_ckspace mibOutput similar to the following is displayed:

DBSpace: all dbspacesDBS Pages Allocated: 204799

DBS Pages Used: 159782DBS Pages Free: 45017

OMC Database space used has reached 78.0189%specified DBMS_MAX_SPACE_USED 95%

TBLSpaceTBS Pages Allocated: 159449

TBS Pages Used: 1148TBS Pages Free: 158301

Continued

8-10 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration pm_manual_parse utility

Procedure 8-2 Running the omc_db_ckspace utility (Continued)

The output provides descriptions of all DBSpaces and all TBLSpaces.Although the above output indicates that the PM database is 78percent full, the TBLSpace section shows how much of that allocationis actually free. The reason for this apparent discrepancy is that thedatabase has been sized for one extent.

4 Enter the following command to reconnect the database:$DBMS_ROOT/sbin/db_disconnect connect

5 Log out of the system processor.

pm_manual_parse utility

The utility pm_manual_parse is used to parse raw PM statistics files that have been missed bythe parser. The utility informs the parser, which files need to be parsed, so that data containedin the files can be inserted into the PM database.

Use the following procedure to run the pm_manual_parse utility:

Procedure 8-3 Running the pm_manual_parse utility

1 Login to the system processor as omcadmin.

2 Enter the following to check that the $FMPATH environment variableis set:echo $FMPATHFMPATH is set to /usr/omc/ne_data/raw_stats. This environmentvariable (set by default in sysCommon.csh) identifies the base UNIXdirectory in which all uploaded statistics are stored before beingpresented to the parser.

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 systemto sleep between sending consecutive files to the parser. The<value> parameter is an integer less than 9999.

• <filename> is the specified file to be parsed.

The <filename> parameter must satisfy the following criteria:

• The specified file must exist.

• Both absolute and relative path names are allowed.

• The file must be globally readable. All uploaded statistics filesare globally readable by default.

Continued

68P02901W19-S 8-11

Oct 2009

pm_manual_parse utility Chapter 8: Database Management

Procedure 8-3 Running the pm_manual_parse utility (Continued)

• The file must be an uploaded statistics file which has not yet beenparsed. If not, the file contents will not be added to the statisticsdatabase.

• Wild cards are allowed for file names to allow submission ofmultiple files.An error message is displayed if the utility does not succeed insending the supplied <filename> to the PM File Parser, or if theparser exits because any of the criteria for the file names arenot met.

4 To see if the parse was successful, enter the command:tail -f $SYS_LOG/fpomcaudityymmddThis displays the last ten lines in the log file fpomcaudityymmdd. Anyerrors that may have occurred during the parsing procedure are shown.

8-12 68P02901W19-S

Oct 2009

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 IDS databases initialized, and the OMC-Rsoftware loaded, directory structures similar to those shown in Figure 8-1 and Figure 8-2 willhave been formed.

The top of the INFORMIX directory structure, on the relevant processor, is located by theenvironment variable $INFORMIXDIR (set to /usr/informix). The PM database scripts onthe system processor can be located by using the environment variable $DBMS_ROOT (setto $OMC_TOP/current).

The INFORMIX databases message logs are held in $INFORMIXDIR on the system processor.

68P02901W19-S 8-13

Oct 2009

INFORMIX directory structure on the system processor Chapter 8: Database Management

INFORMIX directory structure on the system processor

Figure 8-1 shows the INFORMIX directory structure on the system processor.

Figure 8-1 INFORMIX directory structure on the system processor

8-14 68P02901W19-S

Oct 2009

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, to allow for the connection of clientsoftware to the IDS.

NOTEThere are no databases located on a GUI processor. All databases reside on thesystem processor. The GUI processor is merely a client for connection purposes.

Figure 8-2 shows the INFORMIX directory structure on a GUI processor.

Figure 8-2 INFORMIX directory structure on a GUI processor

68P02901W19-S 8-15

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

2 If the OMC-R applications are still running, disconnect all OMC-Rapplications from the database using the db_disconnect utility, asfollows:$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/globalomc_env

6 Start onmonitor utility:onmonitorThe Status menu is displayed as shown in Figure 8-3.

7 Select the Mode menu, by pressing m. The Mode menu is displayed asshown in Figure 8-4.

Continued

8-16 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Shutting down the PM database through onmonitor

Procedure 8-4 Shutting down the PM database through onmonitor (Continued)

8 Select Graceful Shutdown by pressing g and respond to one of thefollowing:

• If there are any users accessing the database, the followingprompt is displayed:Do you want to see the list of user threads? (y/n)

Answer yes (y) to list the active user threads.

NOTEWhere there is no prompt for user threads, selectImmediate Shutdown to put the INFORMIX RDBMSdirectly into Quiescent mode.

• If there are no users, or after the active user threads have beenlisted, the following prompt is displayed:Do you really want to shutdown? (y/n)

Answer no (n) to terminate the shutdown procedure.

Answer yes (y) to place the database into Quiescent mode. Thefollowing message is displayed:

Shutting down, please wait . . . .

The database enters Quiescent mode.

9 Select Take Off-line by pressing two keys SHIFT-T. The followingmessage is displayed:

Shutting down, please wait . . . .

The INFORMIX RDBMS changes state from Quiescent mode to Off-Linemode. Shutdown is complete when the Mode menu returns and thestate line indicates Off-Line.

10 Exit onmonitor by pressing e twice.

11 Log out of the system processor.

68P02901W19-S 8-17

Oct 2009

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

NOTEThe OMC-R software must be stopped before the CM database is manually startedup or shut down. Refer to Chapter 7 System startup and shutdown for stopping theOMC-R software.

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

2 Set the correct environment:mib_env

3 Start the onmonitor utility:onmonitorThe Status menu is displayed as shown in Figure 8-3.

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

Continued

8-18 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Starting up the PM database through onmonitor

Procedure 8-5 Shutting down the CM database using onmonitor (Continued)

5 Select Graceful Shutdown by pressing g and respond to one of thefollowing:

• If there are any users accessing the database, the followingprompt is displayed:

Do you want to see the list of user threads? (y/n)

Answer yes (y) to list the active user threads.

NOTEWhere there is no prompt for user threads, selectImmediate-Shutdown to put the INFORMIX RDBMS directlyinto Quiescent mode.

• If there are no users, or after the active user threads have beenlisted, the following prompt is displayed:

Do you really want to shutdown? (y/n)

Answer no (n) to terminate the shutdown procedure.

Answer yes (y) to place the database into Quiescent mode. Thefollowing message is displayed:

Shutting down, please wait . . . .

• The database enters Quiescent mode.

6 Select take offline by pressing two keys SHIFT-t. The followingmessage is displayed:

Shutting down, please wait . . . .

The INFORMIX RDBMS changes state from Quiescent mode to Off-Linemode. Shutdown is complete when the Mode menu returns and thestate line indicates Off-Line.

7 Exit onmonitor by pressing e twice, then log out of the systemprocessor.

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

Starting up the PM database through onmonitor Chapter 8: Database Management

Procedure 8-6 Starting up the PM database using onmonitor

1 Login to the system processor as root and switch to user informix:su - informix

2 Set the correct environment.omc_env

3 Start the onmonitor utility:onmonitorThe Status menu is displayed as shown in Figure 8-5.

4 Select the Mode menu, by pressing m.The Mode menu is displayed as shown in Figure 8-6.

5 Select Startup by pressing s.This displays messages similar to the following:

Initializing please wait

Press return to continue.

6 Select On-Line by pressing o.

7 Exit onmonitor by pressing e twice.

8 If the OMC-R applications are already running, they may be connectedusing the db_disconnect utility using the following commands:su - omcadminEnter the omcadmin password, 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

8-20 68P02901W19-S

Oct 2009

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

2 Set the correct environment background by entering the followingcommands:mib_env

3 Enter onmonitor and ensure the Startup menu is displayed.

4 Select the Mode menu as shown in Figure 8-7.

5 Select Startup. This will display messages similar to the following:

Initialising please wait

Press return to continue

6 Select On-Line by pressing O.

7 Exit onmonitor by pressing e.

8 Log out of the system processor.

Figure 8-7 Mode menu indicating offline state

Figure 8-8 The onmonitor Status menu indicating online state

68P02901W19-S 8-21

Oct 2009

Starting up databases automatically Chapter 8: Database Management

Starting up databases automatically

To start up both databases automatically, a script needs to be executed.

The automatic startup script for the PM and CM databases is held in the /etc/init.d/informixfile. This script is executed at bootup.

Use the following procedure to execute the automatic startup script:

Procedure 8-8 Starting databases automatically using the startup script

1 Login to the system processor as root.

2 Enter the following:svcadm enable -st informix/pmfor the PM Database andsvcadm enable -st informix/cmfor the CM Database. The automatic startup script is executed.

Shutting down automatically

The automatic shutdown scripts for the CM and PM databases are held in the/etc/init.d/informix file. These scripts are executed when the system is shut down.

Use the following procedure to execute the automatic shutdown script:

Procedure 8-9 Stopping databases automatically using the shutdown script

1 Login to the system processor as root.

2 Enter the following:svcadm disable -st informix/pmfor the PM Database andsvcadm disable -st informix/cmfor the CM Database. The automatic shutdown scripts are executedand both databases will be shut down.

NOTEThe /etc/init.d directory contains files that are linked intothe various run states as described in System processorstartup and shutdown sequences on page 7-5.

8-22 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Administering the PM database using the omc_db_maint utility

Administering the PM database using theomc_db_maint utility

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Using omc_db_maint

The omc_db_maint utility provides a tool for administering the PM database. It unloads anddeletes PM statistics and reports on disk space used by the PM database.

The omc_db_maint utility is located in the directory $OMC_TOP/current/sbin on the systemprocessor.

This utility can be run either as a cron job or using a manual procedure.

It is recommended that the omc_db_maint utility be run daily as a cron job. The schedulingof the cron job should ideally be performed during low activity periods (for example, aftermidnight).

NOTEThe omc_db_maint utility will not purge data if that data has not been previouslyunloaded by omc_db_maint for any reason (for example, if you run out of disk spacein the destination directory). This behavior can be overridden by using the -forceparameter to omc_db_maint. Refer to the section on the omc_db_maint utility formore information. See Automatic Checking Of Maintenance for more informationon monitoring the overnight maintenance.

Running omc_db_maint as a cron job

To run omc_db_maint automatically as a cron job and to check and log the results:

Procedure 8-10 Running omc_db_maint automatically as a cron job

1 Login to the system processor as root and ensure an omc_db_maintline entry exists in the root crontab file:more /usr/spool/cron/crontabs/rootA typical line entry for omc_db_maint, within the root crontab file, isas follows:

Continued

68P02901W19-S 8-23

Oct 2009

Running omc_db_maint manually Chapter 8: Database Management

Procedure 8-10 Running omc_db_maint automatically as a cron job (Continued)

# Execute omc_db_maint at 04:02 each day

02 04 * * * env OMC_TOP=/usr/omc/usr/omc/current/sbin/omc_db_maint

Create a suitable line entry, if one is not already created.

NOTERefer to Chapter 2 System Management for details onsetting up a cron job either by using the Batch Scheduler orby using the command line.

2 When the cron job has been run, check the omc_db_maint log file toensure that the operation completed successfully:more $OMC_TOP/logs/omc_db_maint.<yyyy>.<mm>.<dd>Where <yyyy> refers to the current year, <mm> to the current monthand <dd> to the current day in this month.

3 Record the PM database disk usage information in the systemadministrator log book.

4 Check the PM database log file online.log_OMC for errors, byentering the following:more /usr/informix/online.log_OMC

5 Archive the unloaded statistics to tape and remove them from the filesystem.

Running omc_db_maint manually

CAUTIONThe omc_db_maint script should not be interrupted or killed before it has runto completion.

Use the following procedure to run the omc_db_maint utility manually, referring to othersections of this manual where indicated.

Procedure 8-11 Running the omc_db_maint utility manually

1 Login to the system processor as root.

2 Execute the omc_db_maint utility as follows:$OMC_TOP/current/sbin/omc_db_maint

Continued

8-24 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Automatic Checking Of Maintenance

Procedure 8-11 Running the omc_db_maint utility manually (Continued)

NOTERefer to the section omc_db_maint utility for the use ofoptional parameters.

3 Check the omc_db_maint log file to ensure that the operationcompleted successfully:more $OMC_TOP/logs/omc_db_maint.<yyyy>.<mm>.<dd>Where <yyyy> refers to the current year, <nn> to the current monthand <dd> to the current day in this month.

4 Record the PM database disk usage information in the systemadministrator log book.

5 Check the PM database log file online.log_OMC for errors by enteringthe following:more /usr/informix/online.log_OMC

6 Archive the unloaded statistics to tape and remove them from the filesystem.

Automatic Checking Of Maintenance

When the omc_db_maint utility is run every night it prepares space in the database to acceptthe following days data. If that space is not available for any reason the Parser will not be ableto parse statistics into the database.

A utility pm_purge_check is provided to monitor the PM database and to raise an alarm if itfinds that omc_db_maint has failed to purge the database. This utility must be run as a cronjob and should be scheduled to start 2 hours after the omc_db_maint utility, and should runevery hour until 23:00.

For example, if omc_db_maint is scheduled to run at 02:45 (see above), then the cron table entryfor pm_purge_check will look like:

45 04-23 * * * env OMC_TOP=/usr/omc /usr/omc/current/sbin/pm_purge_check

This will run pm_purge_check at 04:45 and 45 minutes past the hour until 23:45.

On receipt of an alarm to indicate the maintenance has not been successful the operator shouldcheck the omc_db_maint log file for errors:

more $OMC_TOP/logs/omc_db_maint.<yyyy>.<mm>.<dd>

Having investigated and corrected any problems omc_db_maint can be run manually to performthe maintenance. Refer to omc_db_maint utility for information regarding optional parametersand Running omc_db_maint Manually for the correct procedure for manual invocation.

Once the maintenance has been completed successfully, the pm_purge_check utility willautomatically clear any outstanding alarms when it next runs.

68P02901W19-S 8-25

Oct 2009

Setting the onconfig parameters Chapter 8: Database Management

Setting the onconfig parameters■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

onconfig file overview

Each Informix Dynamic Server has a configuration file. The configuration files are as follows:

• /usr/informix/etc/onconfig_OMC the configuration file for the PM database.

• /usr/informix/etc/onconfig_MIB the configuration file for the CM database.

The configuration files hold many parameters associated with each respective IDS. Any changesmade to the parameters in these files should be recorded and a hard copy of the changed fileprinted (noting the date of alteration of the file). Store the hard copy with the backup tapes.

An example of a parameter is:

• Max # of Logical Logs - When restoring either the CM or PM databases from backuptapes, this parameter must be assigned to the maximum value held during the periodcovered by the backup.

The required value for this parameter is stored in the file /$INFORMIXDIR/etc/$ONCONFIG(where the variable $ONCONFIG can be either onconfig_OMC or onconfig_MIB).

Any changes made to the parameters in these files should be recorded and a hard copy of thechanged file printed (noting the date of alteration of the file). Store the hard copy with thebackup tapes.

Checking onconfig parameters

Use the following procedure to check parameter settings within /$INFORMIXDIR/etc/$ON-CONFIG. The procedure uses the TAPE parameters as an example; substitute TAPE for therequired parameter for checking:

Procedure 8-12 Checking onconfig parameters

1 Login to the system processor as root and switch user to informix:su - 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 tapeparameters by entering either of the following lines:

Continued

8-26 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Changing onconfig parameters

Procedure 8-12 Checking onconfig parameters (Continued)

For PM database enter:omc_env ; onstat -c | grep TAPE.For CM database enter:mib_env ; onstat -c | grep TAPEAn output similar to the following will be displayed:

TAPEDEV /dev/rmt/0TAPEBLK 64TAPESIZE 4000000LTAPEDEV /dev/nullLTAPEBLK 16LTAPESIZE 10240

4 If the parameters are not as required, run the onmonitor utility and changethe parameters. Refer to Changing onconfig parameters.

Changing onconfig parameters

CAUTIONIt is not recommended to change /$INFORMIXDIR/etc/$ONCONFIG parameters unlessabsolutely necessary. The parameters supplied by Motorola have been chosenfollowing extensive performance testing. The parameters should only be changed onthe advice of INFORMIX-trained Motorola personnel.

Use the following procedure to change parameters in /$INFORMIXDIR/etc/$ONCONFIG.This procedure describes, as an example, changing the Max # of Logical Logs parameterusing the onmonitor utility:

Procedure 8-13 Changing onconfig parameters

1 Login to the system processor as root and switch user to informix:su - 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, enter the alias:omc_envFor the CM database, enter alias:mib_env

Continued

68P02901W19-S 8-27

Oct 2009

Changing onconfig parameters Chapter 8: Database Management

Procedure 8-13 Changing onconfig parameters (Continued)

4 Enter the following command to start the onmonitor utility:onmonitorThe following is displayed:

INFORMIX-Online: Status Parameters Dbspaces Mode Force-CkptStatus menu to view INFORMIX-Online.----------------------Online------- Press CTRL-W for Help.

5 Using the space bar, select the Mode option and press RETURN. Thefollowing is displayed:

MODES: Startup Online Graceful-Shutdown Immediate-Shutdown...Bring INFORMIX-Online to quiescent mode from offline.----------------------Online------- Press CTRL-W for Help.

6 Using the space bar, select the Take Offline option and press RETURN.The following is displayed:

Do you really want to shutdown? (y/n)

----------------------Online------- Press CTRL-W for Help.

7 Enter y.

8 Using the space bar, select the Exit option to return to the initial Setupmenu. Press RETURN. The following is displayed:

PARAMETERS: initialise Shared-Memory perFormancedata-Replication ...initialise root dbspace and shared memory configuration.

----------Offline------- Press CTRL-W for Help. --------

9 Select the Shared Memory option using the space bar, and pressRETURN.

10 Screen output similar to the following is displayed:

SHARED MEMORY: Make desired changes and pressESC to record changes. Press Interrupt to abort changes.

Press F2 or CTRL-Ffor field-level help. SHARED MEMORY PARAMETERS

Server Number [0] Server Name [omc_sys1]Server Aliases [omc_sys]Dbspace Temp [omc_db_temp]Deadlock Timeout [60] Secs Number of Page Cleaners [5]Forced Residency [Y] Stack Size (K) [32]Non Res. SegSize (K) [10800] Optical Cache Size (K) [128]

Continued

8-28 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Changing onconfig parameters

Procedure 8-13 Changing onconfig parameters (Continued)

Physical Log Buffer Size [128] K Dbspace Down Option [0]Logical Log Buffer Size [128] K Preserve Log For Log Backup[N]Max # of Logical Logs [20] Transaction Timeout [300]Max # of Locks [75000] Long TX HWM [50]Max # of Buffers [4000] Long TX HWM Exclusive [60]Index Page Fill Factor [90]Add SegSize (K) [1024]Total Memory (K) [0]Resident Shared Memory size [14986] Kbytes Page Size [2]Kbytes

11 Move to the fields requiring alteration using the arrow or tab keys andoverwrite the existing values. In this example procedure, change theMax # of Logical Logs parameter to the maximum value held duringthe period covered by the tape backup.

12 Press ESC to save the changes. The following screen output willappear:

Do you want to keep these changes to the parameters? (y/n)

Enter y to install the new values.

13 If no changes are required, the Shared Memory Setup window can beclosed by pressing the interrupt key. This is usually CTRL-c or DELETE.

14 Bring the database back online.

15 Select the Exit option, then select Exit again to close onmonitor utilityand return to the command line prompt.

68P02901W19-S 8-29

Oct 2009

Dropping and Recreating the PM database Chapter 8: Database Management

Dropping and Recreating the PM database■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

CAUTIONThis procedure is a drastic measure, and the PM database should only be dropped andrecreated if absolutely necessary. Contact Motorola Support for further information.

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 processoras user omcadmin and entering the following command:omc stop

2 To drop the PM database, enter the following command as userinformix:svcadm restart -st informix/pm(to verify that the PM database engine is online again).

3 Enter the following commands as user omcadmin:omc_envdbexport omc_db -ssisql - -drop database omc_db;

4 To recreate the PM database, enter the following commands as useromcadmin:cd /usr/omc/current/sbindb_create omc_db

5 To load up customer specifics enter the following for these tablesas user omcadmin, where <unl_dir> is the name of the unloaddirectory in the format: unload_dir.YYYY.MM.DD (for example,unload_dir.2004.05.14). The specific .unl files that are being loadedmust be uncompressed in the dated unload directory before the sqlload commands are executed.

omc_env

Continued

8-30 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Dropping and Recreating the PM database

Procedure 8-14 Dropping and Recreating the PM database (Continued)

isql omc_db -load from/usr/omc/ne_data/unload_stats/<unl_dir>/subscriptions.unlinsert into subscriptions;

load from/usr/omc/ne_data/unload_stats/<unl_dir>/subscription_list.unlinsert into subscription_list;

load from /usr/omc/ne_data/unload_stats/<unl_dir>/entity.unlinsert into entity;

load from/usr/omc/ne_data/unload_stats/<unl_dir>/stored_selections.unlinsert into stored_selections;

load from/usr/omc/ne_data/unload_stats/<unl_dir>/custom_statistics.unlinsert into custom_statistics;

6 The Motorola shipped defaults, stored in /usr/omc/current/config,are loaded by default when the PM database is created.

7 Restart the OMC-R processes by entering the following command asuser omcadmin:omc start

68P02901W19-S 8-31

Oct 2009

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 forregular maintenance of the databases in the OMC-R.

Checking for excess of 32000 statistics

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

Checking stat details

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

Backing up subscription data

Use the following procedure to backup subscriptions and subscription list data from the PMdatabase, through the creation of two UNIX files, onto a specified tape device:

Procedure 8-15 Backing up subscription data from the PM database

1 Login as omcadmin.

2 Enter the following commands on the system processor:omc_envisql omc_db -unload to subscriptions.unl select * from subscriptions;unload to subscription_list.unl select * fromsubscription_list;

NOTEThe subscription data is still retained in the PM database.

3 Use CTRL-c to exit from the isql utility.The subscriptions.unl and the subscription_list.unl files arecreated in omcadmin home directory.

4 Load a DAT tape into the tape drive of the system processor.

Continued

8-32 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Backing up subscription data

Procedure 8-15 Backing up subscription data from the PM database (Continued)

5 Backup the subscriptions.unl and the subscription_list.unl filesto tape by executing the following commands:tar -cvf /dev/rmt/0n subscriptions.unltar -uvf /dev/rmt/0n subscription_list.unlmt -f /dev/rmt/0 rewind

6 Remove the subscriptions.unl and the subscription_list.unl filesfrom omcadmin home directory, if no longer required:rm subscriptions.unlrm subscription_list.unl

68P02901W19-S 8-33

Oct 2009

Checking the PM database Chapter 8: Database Management

Checking the PM database■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Check the PM database

To check the PM database, follow the procedure below. Copy the checklist in Table 14-6to record the checks.

Procedure 8-16 Checking the PM database

1 Check that the PM database is online by entering the followingcommands as user omcadmin:omc_envonmonitorThis utility reports that the database is in an online mode.

2 Check the IDS log file for errors and check-pointing by entering thefollowing command as user omcadmin:tail -f $INFORMIXDIR/online.log_OMCThis log file should show that checkpoints are completed successfully,in particular when the server is initialized.

3 Check that the IDS log files are rolled over by entering the followingcommands as user omcadmin:cd $INFORMIXDIRls -l online.log_OMC*Log files should exist in the form:online.log_OMC.ddmmyyyy

4 Check the output of the onmode_pm cron job by entering the followingcommands as user omcadmin:cd /var/mailmore omcadmin | grep onmode_pm

5 Check the omc_db_maint log file to ensure that:

• PM statistics are unloaded and deleted successfully.

• Disk space is not being consumed.

• Applications are disconnected and reconnected successfully whenrequired.As user root execute the following commands:

cd $OMC_TOP/logs

more omc_db_maint.yyyy.mm.dd

6 Check that the PM sqlhosts file has the correct entries for the InformixServer by entering the following commands as user omcadmin:more /usr/informix/etc/sqlhosts_OMCOutput should look similar to the example shown in PM sqlhosts.

Continued

8-34 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration PM sqlhosts file

Procedure 8-16 Checking the PM database (Continued)

7 Check the /etc/services file to ensure that a port number exists for thePM IDS by entering the following command as user omcadmin:more /etc/servicesAn entry should exist similar to the following:

inf7_OMC_serv 5000/tcp

8 Check the shared memory structure of the PM IDS by entering thefollowing command as user informix:onstatOutput should be similar to that shown in onstat output for PMdatabase section.

9 Check the status of the dbspaces and chunks of the PM IDS by enteringthe following commands as user informix:onstat -dOutput should be similar to that shown in onstat -d output for PMdatabase section.

10 When performing an archive of the PM DB ensure that the TAPEDEVparameter is set to /dev/rmt/0 by entering the following commandsas 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 entryis shown as follows:

inf7_OMC_serv 5000/tcp # OMC database I

nformix DSA instance

onstat output for PM database

A typical example for the onstat utility output display for the PM database is shown as follows:

IBM Informix Dynamic Server Version 9.40.UC4 --

On-Line -- Up 09:48:19 -- 467968 Kbytes Userthreads

68P02901W19-S 8-35

Oct 2009

onstat output for PM database Chapter 8: Database Management

address flags sessid user tty wait tout locks

nreads nwrites 24a67018 ---P--D 1 root -

0 0 0 80 136 24a67630 ---P--F 0

root - 0 0 0 0 893 24a67c48 ---P--F

0 root - 0 0 0 0

729 24a68260 ---P--F 0 root -

0 0 0 0 62 24a68878 ---P--F

0 root - 0 0 0 0

0 24a68e90 ---P--F 0 root - 0

0 0 0 0 24a694a8 ---P--F

0 root - 0 0 0 0

0 24a69ac0 ---P--- 11 root - 0

0 0 0 0 24a6a0d8 ---P--B 12

root - 0 0 0 30

64 24a6a6f0 Y--P--- 80 omcadmin console

2546c248 0 1 26 0 24a6ad08

Y--P--- 81 omcadmin console 25595e30

0 1 0 0 24a6b320 ---P--D 15

root - 0 0 0 0 0

24a6b938 Y--P--- 10 omcadmin console

2546c6f8 0 1 8 0 24a6bf50

Y--P--- 82 omcadmin console 255c3890 0

1 0 0 24a6c568 Y--P--- 83

omcadmin console 25595fc8 0 1 0 0

24a6cb80 Y--P--- 84 omcadmin console

25610dd8 0 1 0 0 24a6d198

Y--P--- 85 omcadmin console 256358e0

0 1 0 0 24a6d7b0 Y--P--- 86

omcadmin console 2566f3d8 0 1 0

0 24a6ddc8 Y--P--- 87 omcadmin -

2566fed0 0 1 12 0 24a6e3e0

Y--P--- 88 omcadmin - 256909d8 0

1 0 0 24a6e9f8 Y--P--- 89

omcadmin - 256d6590 0 1

0 0 24a6f010 Y--P--- 90

omcadmin - 256f10c8 0 1 0 0

24a6f628 Y--P--- 79 omcadmin console

256f1e80 0 1 0 0 24a6fc40 Y--P--- 92

omcadmin console 25720a78 0

0 24a70258 Y--P--- 93

omcadmin console 1 0 25757678 0

1 0 0 25 active, 128 total, 26 maximum

8-36 68P02901W19-S

Oct 2009

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 99.35 1868

6645 61471 96.96 isamtot open

start read write rewrite delete commit

rollbk 473705 18798 20238 192674 7855

2247 7060 425 0 gp_read gp_write

gp_rewrt gp_del gp_alloc gp_free

gp_curs 0 0 0 0

0 0 0 ovlock ovuserthread

ovbuff usercpu syscpu numckpts

flushes 0 0 0 85.78 11.1

4 15 249 bufwaits lokwaits lockreqs

deadlks dltouts ckpwaits compress

seqscans 38 0 1013573 0

0 1 1056 1674 ixda-R

A idx-RA da-RA RA-pgsused lchwaits

24 117 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.40.UC4 -- On-Line --

Up 09:50:36 -- 467968 Kbytes Dbspaces address number flags

fchunk nchunks flags owner name 2490e7d8 1 0x20001

1 1 N 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 informix omc_db_temp 16 active, 2047 maximum

68P02901W19-S 8-37

Oct 2009

onstat -d output for PM database Chapter 8: Database Management

Chunks address chunk/dbs offset size free bpages flags

pathname 2490e928 1 1 2 1023998 998794 PO--

/dev/omc_db_root 25197158 2 2 2 256000 129000

PO-- /dev/omc_db_logs 251972e0 3 3 256003 767997 383944

PO-- /dev/omc_db_logs 25197468 4 4 2 2047998

1171728 PO-B /dev/omc_db1 251975f0 5 5 2 2047998

1171728 PO-B /dev/omc_db2 25197778 6 6 2

2047998 1171728 PO-B /dev/omc_db3 25197900 7 7

2 2047998 1171728 PO-B /dev/omc_db4 25197a88

8 8 2 2047998 1171728 PO-B /dev/omc_db5

25197c10 9 9 2 2047998 1171728 PO-B /dev/omc_db6

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_db_temp

16 active, 32766 maximum Expanded chunk capacity mode: enabled

8-38 68P02901W19-S

Oct 2009

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. Copy the checklist in Table 14-7to record the checks.

Procedure 8-17 Checking the CM database

1 Check that the MIB database is online by entering the followingcommands as user omcadmin:mib_envonmonitorThis utility reports that the database is in an online mode.

2 Check the IDS log file for errors and check-pointing by entering thefollowing commands as user omcadmin:tail -f $INFORMIXDIR/online.log_OMCThis log file should show that checkpoints are completed successfully,in particular when the server is initialized.

3 Check that the IDS log files are rolled over by entering the followingcommands as user omcadmin:cd $INFORMIXDIRls -l online.log_OMC*Log files should exist of the form online.log_OMC.ddmmyyyy

4 Check the output of the onmode_mib cron job by entering the followingcommands as user omcadmin:cd /var/mailmore omcadmin | grep onmode_mib

5 Check the dbspace and tblspace allocation for the CM IDSby entering the following commands as user omcadmin:cd$DBMS_ROOT/SBINomc_db_ckspace mib. The output should be similarto that shown in the section omc_db_ckspace utility on page 8-10.

6 Check that the CM database sqlhosts file has the correct entries forthe Informix Server by entering the following commands as useromcadmin:more /usr/informix/etc/sqlhosts_MIBOutput should look similar to the example shown in the section CMsqlhosts file on page 8-40.

7 Check the /etc/services file to ensure that a port number exists for theCM IDS by entering the following commands as user omcadmin:more /etc/servicesAn entry should exist similar to the following:inf7_MIB_serv 5010/tcp

Continued

68P02901W19-S 8-39

Oct 2009

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 thefollowing commands as user informix:onstatoutput is similar to thatshown in the section onstat output for CM database on page 8-41.

9 Check the status of the dbspaces and chunks of the CM IDS by enteringthe following commands as user informix:onstat -dOutput should be similar to that shown in the section onstat -d outputfor CM database on page 8-42.

10 When performing an archive of the CM DB ensure that the TAPEDEVparameter is set to /dev/rmt/0 by entering the following commandsas 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 60k_MIB_shm omc_mib

ontlitcp omc_splat inf7_MIB_serv omc_sys ontlitcp

omc_splat inf7_OMC_serv mcMIB175003041066 ontlitcp s

omc31 mcMIB

A corresponding port number must also exist in the /etc/services file. An example line entryis shown as follows:

inf7_MIB_serv 5010/tcp # MIB database Informix

DSA instance

8-40 68P02901W19-S

Oct 2009

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

On-Line -- Up 23:23:25 -- 148480 Kbytes Userthreads

address flags sessid user tty wait tout locks

nreads nwrites 1120f018 ---P--D 1 root -

0 0 0 38 103 1120f630 ---P--F 0 root

- 0 0 0 0 260 1120fc48 ---P--F

0 root - 0 0 0 0 44 112102

60 ---P--- 11 root - 0 0 0 0

0 11210878 ---P--B 12 root - 0 0

0 0 0 11210e90 Y--P--- 10 omcadmin

console 117f5fc8 0 1 58 0 112114a8 Y--P--- 21

omcadmin - 11bae8a8 0 1 34

0 11211ac0 ---P--D 15 root - 0 0

0 0 0 112120d8 Y--P--- 23

omcadmin - 119d3cc0 0 1 298 0 112126f0

Y--P--- 19 omcadmin console 11990eb8 0 1 0

0 11212d08 Y--P--- 24 omcadmin - 119950c8

0 1 41 0 11213320 Y--P--- 25 omcadmin -

11995c88 0 1 55 0 11213938 Y--P--- 26

omcadmin - 11a26888 0 1 43 0

11213f50 Y--P--- 27 omcadmin - 11a2c518 0

1 23 0 11214568 Y--P--- 28 omcadmin -

11aaa168 0 1 41 0 11214b80 Y--P--- 29

omcadmin - 11aaad78 0 1 38 0 11215198

Y--P--- 30 omcadmin - 11aedea0 0 1 29

0 112157b0 Y--P--- 31 omcadmin - 11b35c10 0

1 33 0 11215dc8 Y--P--- 32 omcadmin

- 11b548d8 0 1 56 0 112163e0 Y--P--- 33

omcadmin - 11bc02b8 0 1 49 0 112169f8

Y--P--- 34 omcadmin - 11c00598 0

1 40 0 11217010 Y--P--- 47 omcadmin -

11d47700 0 1 0 0 22 active,

maximum concurrent Profile dskreads pagreads bufreads

%cached dskwrits pagwrits 128 total, 24 bufwrits %cached

1589 1716 188887 99.16 326 702

2255 85.54 isamtot open start read write rewrite

delete commit rollbk 161392 23657 30306 60035 46

2059 1 1133 0 gp_read gp_write

gp_rewrt gp_del gp_alloc gp_free gp_curs 0 0 0

68P02901W19-S 8-41

Oct 2009

onstat -d output for CM database Chapter 8: Database Management

0 0 0 0 ovlock ovuserthread ovbuff usercpu

syscpu numckpts flushes 0 0 0 18.75 1.55

5 564 bufwaits lokwaits lockreqs deadlks dltouts ckpwaits

compress seqscans 155 0 139122 0 0 0 2

990 ixda-RA idx-RA da-RA 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 asfollows:

IBM Informix Dynamic Server Version 9.40.UC4 -- On-Line --

Up 23:23:57 -- 148480 Kbytes Dbspaces address number flags

fchunk nchunks flags owner 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,

2047 maximum Chunks address chunk/dbs offset size

free bpages flags pathname 1110e928 1 1 2

921598 475696 PO-- /dev/mib_db 1123fdf0 2

2 2 256000 177100 PO-- /dev/mib_db_logs

11904018 3 3 256003 767997 583624 PO--

/dev/mib_db_logs 119041a0 4 4 921601 102399

102346 PO-- /dev/mib_db 11904328 5 5 2

1023998 797280 PO-- /dev/mib_db1 5 active,

32766 maximum

8-42 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Dropping and Recreating the CM database

Dropping and Recreating the CM database■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

CAUTIONThis procedure is a drastic measure, and the CM database should only be dropped andrecreated if absolutely necessary. Contact Motorola Support for further information.

Use the following procedure to drop and then recreate the CM database:

Procedure 8-18 Dropping and Recreating the CM database

1 Shut down the OMC-R processes by logging in to the system processoras user omcadmin and entering the following command:omc stop

2 To drop the CM database, enter the following command as userinformix:svcadm restart -st informix/cm(to verify that the CM database engine is online again).

3 Enter the following commands as user omcadmin:mib_envdbexport mib_db -ssisql - -drop database mib_db;

4 To recreate the CM database, enter the following commands as userroot:cd /usr/omc/sbincm_setup

5 Restart the OMC-R processes by entering the following command asuser omcadmin:omc start

68P02901W19-S 8-43

Oct 2009

Dropping and Recreating the CM database Chapter 8: Database Management

8-44 68P02901W19-S

Oct 2009

Chapter

9

X.25 management■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

68P02901W19-S 9-1

Oct 2009

Overview Chapter 9: X.25 management

Overview■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This chapter provides a technical description of X.25 management functions.

The following topics are described in this chapter:

• X.25 application management on page 9-3.

• Basic X.25 commands on page 9-7.

• X.25 directory structure on page 9-8.

• Starting and stopping X.25 on page 9-9.

• Updating X.25 link configuration on page 9-13.

• Replacing the HSI card on page 9-17.

• Checking X.25 connectivity on page 9-18.

9-2 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration X.25 application management

X.25 application management■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Overview of the X.25 software

The X.25 software application controls the routing of the data from the OMC-R system processor,through the packet switch and multiplexer, to the individual network elements. This data is sentusing the packet switch protocol.

When installation has been completed, the X.25 software will load and execute automatically inaccordance with the startup or shutdown procedure.

The X.25 application is implemented for the OMC-R using SunLink X.25.

Figure 9-1 Centralized use of X.25

Configuring X.25

The full procedure required to configure X.25 for the OMC-R is described in the Installation andConfiguration: OMC-R Clean Install (68P02901W47) manual.

Configuring OMC-R processes for X.25

The OMC-R applications that handle incoming or make outgoing X.25 connections, must beconfigured in the OMC-R software. The following configuration file is required to configurethe X.25 connections:

/usr/omc/config/global/x25_config

68P02901W19-S 9-3

Oct 2009

Configuring OMC-R processes for X.25 Chapter 9: X.25 management

Each line in the x25_config file contains 11 fields, as illustrated in Figure 9-2.

Figure 9-2 x25_config configuration file details.

1 x25_chan1 0 2345678 H g_bootload OMC_BL X25 128 2 50

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_RL X25 128 2 500

6 x25_chan6 0 71271213 H - OMC_PU X25 128 2 50

7 x25_chan7 1 31413141 H - OMC_PU X25 128 2 50

NOTEThe number of OMC_PU application processes may vary depending on the TCHcapacity of the machine. This is described in the Installation and Configuration:OMC-R Clean Install (68P02901W47) manual.

The 11 fields of the x25_config are defined as follows:

Record number: The record number within the file.

X.25 channel number: In the format x25_chann where n is the channel number.

Port/link identifier: This field is the link identifier used by the application. The value of thisfield corresponds to the X.25 link configured within SunLink X.25. Each link will be associatedwith either an E1 channel or a HSI port. Each E1 channel is associated with a specific NE. It ispossible to run each X.25 application process on a single HSI port.

X.121 application address: The local X.121 address for an application (maximum 14 digits).

X.25 card type: This field refers to the HSI card used in the system processor for X.25connectivity. H is the only option available.

Process call characteristic: The process call characteristic field. A value of - indicates thatthe process makes calls. Any other value in this field indicates that the process listens forincoming calls.

9-4 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Rules for the x25_config file

Application process: X.25 application process can be one of the following:

• OMC_BL - Bootload.

• OMC_EI - Event Interface.

• OMC_RL - Remote Login.

• OMC_PU - Upload.

Protocol: Protocol being used by a process. The only valid value in this field is X25.

Packet size: Maximum X.25 packet size to be used over connection.

Window size: Maximum X.25 window size to be used over connection.

Poll time-out: Time-out value specified in poll system call (seconds).

Rules for the x25_config file

Each entry is separated by a space. The order of entries in the file is significant and is as follows:

1. The first and second lines are for the bootloader (incoming calls). For redundancypurposes, entry 1 should be configured to use a different link/port to entry 2.

2. The third and fourth lines are for the event interface (incoming calls). For redundancy,entry 3 should be configured to use a different link/port to entry 4.

3. The fifth line is for the remote login (outgoing calls).

4. The sixth and seventh lines are for the uploader (outgoing calls). For redundancy, entry 6should be configured to use a different link/port to entry 7.

5. For high-capacity systems, there are two additional OMC_PU lines. The additional lines arerequired because there are four upload channels.

OMC X.25 application design

The use of X.25 is centralized into separate X.25 appl OMC-R service provider applicationson the system processor. OMC-R system processor applications (EventInterface, Upload,Download and Rlogin) currently interface to the x25appl applications.

The x25appl applications are the only applications to interface directly to the X.25 packetswitch through the SunLink X.25 interface. The x25appl applications communicate with theOMC-R applications using the Motorola IPC mechanism. Outgoing calls are made on demandwhen requested by the remote login and upload applications.

The x25stat utility is provided to query the status of the centralized X.25 application. Thisutility will be run by the OMC-R system administrator, not by the end users. It returns thenumber and type of SVCs currently open.

68P02901W19-S 9-5

Oct 2009

OMC X.25 application design Chapter 9: X.25 management

NOTEThe x25appl processes are restartable processes, that is, they can be restartedwithout restarting the whole OMC-R. A x25appl process is to be restarted to pickup changes made to the x25_config file. Refer to Restartable processes on page2-49. This is not the same as stopping and starting the X.25 system of the OMC-R,described in Starting and stopping X.25 on page 9-9.

9-6 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Basic X.25 commands

Basic X.25 commands■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Starting and stopping X.25

X.25 may be started or stopped on a single link, or may be started and stopped as a service.Procedures to start or stop a single link or the X.25 service must be run as user root.

The start or stop commands are run using the X.25 tool. This tool enables the user to stop andstart the X.25 service, and stop and start a single link.

NOTEStopping and starting the SUN X.25 system on the OMC-R is NOT the same asrestarting a x25appl process.

Replacing the HSI card

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

Updating X.25 link configuration

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

Further details of X.25 commands

For further details of X.25 commands, refer to the Managing SunLink X.25 9.2 manual.

68P02901W19-S 9-7

Oct 2009

X.25 directory structure Chapter 9: X.25 management

X.25 directory structure■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The directory structure relevant to X.25 configuration and maintenance on the system processoris shown in Table 9-1. All files and utilities are immediately under the root (/).

Table 9-1 Files and utilities for X.25 configuration and maintenance

File or utility Description

/usr/omc/config/global/x25_config

Configuration file for OMC applications which handleincoming or make outgoing calls.

/etc/rc2.d/S87x25net Network daemon for starting or stopping X.25 on bootup ofthe system processor.

/etc/init.d/x25.control Starts all the necessary daemons and brings up the software.

/opt/SUNWconn/x25/bin/x25tool

X.25 configuration and administration utility.

/opt/SUNWconn/x25/bin/x25stat

Displays link statistics.

/opt/SUNWconn/x25/bin/x25trace

Protocol level tracing facility.

/opt/SUNWconn/x25/bin/x25info

Provides useful status information.

/etc/opt/SUNWconn/x25/netconf

Describes the configuration of the STREAMS networkconstructed by X25netc.

/etc/opt/SUNWconn/x25/config

Directory containing configuration files.

/opt/SUNWconn/x25/bin/pad

User interface to pad facilities.

/opt/SUNWste X.25 license facilities.

9-8 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Starting and stopping X.25

Starting and stopping X.25■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Stopping OMC-R processes

Before doing major reconfiguration on X.25, for example, replacing X.25 the hardwareor upgrading software, the OMC-R should be stopped as described in Manual startup andshutdown of OMC-R software on page 7-12.

Overview of the x25tool

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

Starting up the x25tool

Use the following procedure to start the x25tool:

Procedure 9-1 Starting the x25tool

1 Login to the system processor as user root.

2 Set the DISPLAY variable to the system processor by entering thefollowing commands:/bin/cshcd /setenv DISPLAY omc_splat:0.0

3 Execute the following command:cd /opt/SUNWconn/bin./x25tool &The x25tool 9.2 window is displayed on the system processor as shownin Figure 9-3.

68P02901W19-S 9-9

Oct 2009

Starting up the x25tool Chapter 9: X.25 management

Figure 9-3 x25tool 9.2 window

9-10 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Starting X.25

Starting X.25

Use the following procedure to start the SunLink X.25 software:

Procedure 9-2 Starting the SunLink X.25 software

1 Start the x25tool as described in Starting up the x25tool on page 9-9.

2 From the Network menu select Start X.25. The message window shownin Figure 9-4 indicates that X.25 has been started.

Figure 9-4 X25 Message window: process started

68P02901W19-S 9-11

Oct 2009

Stopping X.25 Chapter 9: X.25 management

Stopping X.25

Use the following procedure to stop the SunLink X.25 software:

Procedure 9-3 Stopping the SunLink X.25 software

1 Start the x25tool as described in the previous section.

2 From the Network menu select Stop X.25. The message window shownin Figure 9-5 indicates that the X.25 has been stopped.

Figure 9-5 X25 Message window: process stopped

9-12 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Updating X.25 link configuration

Updating X.25 link configuration■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Configuring X.25 parameters

To update the configuration of the X.25 link, carry out the following procedure. Updating theconfiguration of the X.25 link requires the user to interface with the x25tool. Reconfiguration ispossible on the active links such that the X.25 service need not be stopped.

Use the following procedure to configure the X.25 link:

Procedure 9-4 Configuring X.25 parameters

1 Invoke the x25tool window as described in Starting and stopping X.25on page 9-9.

2 To modify an existing HSI link, select the link in the x25tool window.

3 ClickModify on the right side of the x25tool window.The Link Editor window is displayed, as shown in Figure 9-6.

4 Make the necessary changes.

5 Click Apply to save the changes and close the window.

68P02901W19-S 9-13

Oct 2009

Configuring X.25 parameters Chapter 9: X.25 management

Figure 9-6 Link editor window

9-14 68P02901W19-S

Oct 2009

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 Changing parameters in the LAPB configuration

1 Select the link in the x25tool window.

2 ClickModify on the right side of the x25tool window.The Link Editor window is displayed, as shown in Figure 9-6.

3 Under Advanced Configuration on the right side of the Link Editor,click LAPB, WAN.The LAPB and WAN Parameters window is displayed, as shown inFigure 9-7.

4 Make the necessary changes.

5 Click Apply.

68P02901W19-S 9-15

Oct 2009

Configuring LAPB parameters Chapter 9: X.25 management

Figure 9-7 LAPB and WAN parameters window

9-16 68P02901W19-S

Oct 2009

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 to enable the HSI card to be replaced:

Procedure 9-6 Replacing the HSI card

1 Login to the system processor as user root.

2 Enter the following commands:su - omcadmin: svcadmdisable omc

3 Stop SunLink X.25 as described in Starting and stopping X.25 on page 9-9.

4 Use the following commands to inform all users that maintenance to the X.25HSI 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 -yThe PROM monitor mode OK prompt is displayed.

6 Power off the system processor.

7 Remove and replace the network interface card by following the instructionsin the HSI installation guide.

8 Power up the system.

68P02901W19-S 9-17

Oct 2009

Checking X.25 connectivity Chapter 9: X.25 management

Checking X.25 connectivity■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

X.25 connectivity checklist

Use the following procedure to check X.25 connectivity. Copy the checklist provided inTable 14-8 to record the checks.

Procedure 9-7 Checking X.25 connectivity

1 Check the contents of the x25_config file by entering the followingcommands as user root:cd /usr/omc/config/globalmore x25_configThe file contents should be similar to the example shown in Figure 9-2.The correct entries are required to configure x25 connections.

2 Check the integrity of x25 by entering the following commands asuser root:/opt/SUNWconn/bin/x25statRefer to x25stat output on page 2-76 for example, output.

3 Check the status of the network by entering the following commandsas user root:/usr/bin/netstat -aRefer to OMC-R system information on page 13-8 for example, outputof the netstat command.

9-18 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration X.25 recovery from HSI failure

X.25 recovery from HSI failure■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Issue A: Sun IB module/IO board hardware failure

In the event of an IB module/IO module failure on a Sun (SF4800/4900/E3x00) platform, thesystem may restart or hang until the operator resets the machine manually. An IB module failureimplies that the onboard HSI card is rendered out of service. When the system restarts, it doesnot detect the difference between a badly configured system and a system where one of the HSIcards was faulty. Even though there may be still at least one remaining working HSI card, theX.25 software will attempt to start up but will fail to start. Using the X.25tool to restart the X.25software, the operator can see output similar to the following from the X.25tool:

<09/29/05 14:26:00>

<09/29/05 14:26:05> Starting the X.25 software - please wait

<09/29/05 14:26:05> X.25 : Creating link 0...

<09/29/05 14:26:05> X.25 : link 0 has been started

<09/29/05 14:26:05> X.25 : Creating link 1...

<09/29/05 14:26:05> X.25 : link 1 has been started

<09/29/05 14:26:05> X.25 : Creating link 2...

<09/29/05 14:26:05> X.25 : link 2 has been started

<09/29/05 14:26:05> X.25 : Creating link 3...

<09/29/05 14:26:05> X.25 : link 3 has been started

<09/29/05 14:26:05> X.25 : Creating link 4...

<09/29/05 14:26:05> X.25 : failed to open driver "/dev/hihp4" : No such device

<09/29/05 14:26:05> X.25 : Can't create level 2 for link 4

<09/29/05 14:26:06> X.25 : link 4 has been stopped

<09/29/05 14:26:06>

<09/29/05 14:26:07> The network failed to come up correctly.

<09/29/05 14:26:07>

The operator is advised to call their local Sun hardware support to replace the faulty hardware

Issue B: HSI card hardware failure

A HSI card failure alone should not cause the system to reboot (unlike an IB module failure).If one of the HSI cards is out of service, and the X25 software is restarted or the system isrebooted, the X25 software fails to start.

68P02901W19-S 9-19

Oct 2009

Issue C: OMC-R configuration to allow X25 operate using the remaining hardware Chapter 9: X.25 management

Issue C: OMC-R configuration to allow X25 operate using theremaining hardware

When the HSI links that service statistics and uploads goes down, then the OMC-R applicationdoes not use the other available HSI links as configured in the x25_config file. This occursuntil the faulty hardware can be replaced.

The following issues may arise:

• PM Statistics uploads do not swap over to the next available x25appl with a workingHSI link.

• BSS database (.002) uploads will swap over to an available HSI link for the same BSS.

However users may have to request the upload a second time as the first request may fail, andthe second attempt will succeed on the next available x25appl.

9-20 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Recovery

Recovery■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Issue A: Recovery from a Sun IB module/IO board hardwarefailure

After the system is rebooted, as one of the IB modules (and hence HSI cards) is out of servicethen the X25 software may fail to start. The following procedure describes how to restart theX25 software:

Procedure 9-8 Restarting the X25 software

1 Identify the X.25 links associated with the out-of-service IB module (HSIcard). Use the X.25tool to start the X.25 software and view the output. Asample output is as follows:

Starting the X.25 software - please wait

X.25 : Creating link 0...

X.25 : link 0 has been started

X.25 : Creating link 1...

X.25 : link 1 has been started

X.25 : Creating link 2...

X.25 : link 2 has been started

X.25 : Creating link 3...

X.25 : link 3 has been started

X.25 : Creating link 4...

X.25 : failed to open driver "/dev/hihp4" : No such device

X.25 : Can't create level 2 for link 4

X.25 : link 4 has been stopped

The network failed to come up correctly.

The sample output shown above indicates that X.25 fails to start link 4. Thiscorresponds to the failure of the IB8 module on a SunFire4800.

Continued

68P02901W19-S 9-21

Oct 2009

Issue B: Recovery from HSI card hardware failure Chapter 9: X.25 management

Procedure 9-8 Restarting the X25 software (Continued)

2 Remove the link files associated with the failed HSI card, to be able to startthe X.25 software.For each of the links found to be out of service in step 1, rename thecorresponding link_config_000x.cfg file as follows:As user root, execute the following command to rename the correspondinglink_config_000x.cfg file:cd /etc/opt/SUNWconn/x25/configExecute the following command to list out all the link files:ls -l link_config*

A sample output is shown below:

-rwxr-xr-x 1 root other 2249 Nov 16 17:08 link_config_0000.cfg

-rwxr-xr-x 1 root other 2249 Nov 16 17:08 link_config_0001.cfg

-rwxr-xr-x 1 root other 2249 Nov 16 17:08 link_config_0002.cfg

-rwxr-xr-x 1 root other 2249 Nov 16 17:08 link_config_0003.cfg

-rwxr-xr-x 1 root other 2249 Nov 16 17:08 link_config_0004.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_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_0007.cfg

The sample output shown above indicates that link 4 failed to start up. Thisindicates that all the files associated with the HSI card have to be renamedas follows:

mv link_config_0004.cfg link_config_0004.cfg.origmv link_config_0005.cfg link_config_0005.cfg.origmv link_config_0006.cfg link_config_0006.cfg.origmv link_config_0007.cfg link_config_0007.cfg.orig

3 Use X.25 tool to restart the X.25 software.

4 Proceed to recovery method for Issue C below to reconfigure the X.25_configfile.

Issue B: Recovery from HSI card hardware failure

If one of the HSI cards is out of service, and the X25 software is restarted or the system isrebooted, the X25 software does not start.

However until the hardware is replaced, follow all of the recovery steps for Issue A above toensure that X25 software will start.

Until the HSI card is replaced, X25 tries to use faulty ports which are still configured in thex25_config file.

Proceed to recovery method for Issue C below to reconfigure the x25_config file.

9-22 68P02901W19-S

Oct 2009

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

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

When the HSI link that is servicing statistics and uploads goes down, the OMC-R applicationdoes not automatically use the other available HSI links configured in the x25_config file.The following procedure details the workaround to edit the x25_config file and remove thereferences to the out-of-service x25 links, restart x25 and the OMC-R application:

Procedure 9-9 Editing the x25_config file

1 As user omcadmin, execute the following command to determine the HSIports 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 thethird 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 - OMC_RL X25 128 2 500

6 x25_chan6 1 511205 H - OMC_PU X25 512 7 50

7 x25_chan7 5 511205 H - OMC_PU X25 512 7 50

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. Use the x25 tool to determine which ports arenot at NORMAL state. In the example shown in step 1, ports 4, 5, 6 and7 are out of service.

3 As user omcadmin, execute the following commands to backup thex25_config file:cd /usr/omc/config/globalcp –p x25_config x25_config.orig

Continued

68P02901W19-S 9-23

Oct 2009

Issue C: Recovery of OMC-R configuration to allow X25 operate using the remaining hardware Chapter 9: X.25 management

Procedure 9-9 Editing the x25_config file (Continued)

4 As user omcadmin, edit the x25_config file (using vi or other editors) toreplace references to the out-of-service HSI ports with in-service ports onthe remaining HSI card. Delete references to ports 4, 5, 6 and 7 from thex25_config file and save the file. The following output shows the x25_configfile:

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 - OMC_RL X25 128 2 500

6 x25_chan6 1 511205 H - OMC_PU X25 512 7 50

7 x25_chan7 1 511205 H - OMC_PU X25 512 7 50

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

5 Once the above changes have been made to the x25_config file, restart x25software using x25 tool.

6 As user omcadmin, stop the OMC-R using the following command:omc stopRestart 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.

9-24 68P02901W19-S

Oct 2009

Chapter

10

OMC Utilities■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

68P02901W19-S 10-1

Oct 2009

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 havebeen packaged as MOTu1900, on the GSR9 CD-ROM.

These utilities were developed by Motorola to improve specific routine Operation andMaintenance (O and M) activities. The utilities are intended to provide interim solutions forOMC operators, particularly in a multi-OMC-R environment.

The utilities are supplementary to the full OMC-R Release. Support will be provided directlyfrom the OMC Customer Support group.

This chapter also describes the purpose, installation and execution of the OMC utilities, and theoutput generated by them.

NOTEIt is recommended to reinstall the operation and maintenance utilities whenperforming a major upgrade to a new release as they may change from release torelease.

CAUTIONDo not execute a CTRL–c while any of the scripts are executing and allow all scripts tocomplete 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 followingsections.

10-2 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Alarm/Event Window

Table 10-1 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 systemprocessor.

Alarm/Event Window

The utilities can be invoked from the Tools menu on the Alarm Window.

Click on the AlarmWindow icon or the Event Management icon to bring up the AlarmWindow.

There is a new pull-down menu called Tools in this window. The utilities have now beencategorized 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 followingcommand 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 thepackage 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 followingcommands as user root:cd /cdrom/cdrom0/s0/suninstall/Packagespkgadd -d MOTu1900 all

Install Utilities

An installation utility is provided to install the utilities and their associated files and directorieson to the OMC System Processor at /usr/omc/current/sbin. Only the OMC administrator canperform the installation and rollback of these utilities.

NOTE

• In the case of multiple OMCs, ensure that they are trusted hosts of each otherand that the users are common to all OMCs.

• The existing stty echoe and stty erase commands in the .cshrc for omcadminand all other users must be commented out.

10-4 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 andmaintenance utilities package.

Execute the following commands as user root:cd /home/omcadmin/Utilities_Install./install_utilities.sh

NOTESample input and output data are used in the examples below.

This install script sets up these OMC Utilities across multiple OMCs Enter thehostname 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 .acefiles across the hosts laurel

Creating the script which collects the required bsic and rfplan dataand puts into rfplan.txt and bsicnet.txt generating the getdata.shfile which will then be used by the finder script to rsh into eachomc 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 SystemProcessor 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 cleanupcan be performed. Once the installation is complete, as user omcadmin, enter the followingcommand:

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 invokedfrom 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 CELLID, and returns its essential details regardless of the OMC on which it resides. On the firstinvocation 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.txtrfplan.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 Togenerate a fresh RF and BSIC plan of the network now: enter ’yes’. OR to use theold 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 fromthe 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 Source

Target

ADJ_CI

TGT_CI

ADJ_BCCH

TGT_BCCH

ADJ_BSIC

TGT_BSIC

BSS-1006 001-01-1-41 001-01-1-6 75 11

001-01-1-6 75 16

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

_____________________________

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

10-12 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 thesystem 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 containthe DRIs under the given region.

-b OMCname OMCname is an OMC. Produces a report for OMCname. If -b isnot used, the default is the OMCs in omc.lst.

-l This produces a list of OMCs in the network from which the usermust select one. Even if the -b option has been used, the inputfrom -l takes preference.

-c directory Name of directory where the output is to be stored. If -c is notused, 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

dri_status Chapter 10: OMC Utilities

Output

OMC: laurel

DRI REPORT 1999/05/05 16:18:11

______________________________________

BSC

RDNINSTANCE

SITE

RDNINSTANCE

DRIGROUP

DRI

ADMIN

STATE

OP

STATE

TRANSMISSION

TIME

BSS_100 BSS_100:SITE-4: 1 1 0 0 1999-02-10

10:46:05.00000

1600d2_test 1600d2_test:SITE-1: 0 0 0 0 1998-12-16

17:14:12.00000

Sample output when region option is used:

OMC: somc153

___________________

Region:region1

______________________

DRI REPORT 2005/06/17 11:32:17

_____________________________

BSC SITE DRI

RDNINSTANCE

DRIGROUP

RDNINSTANCE

ADMIN

STATE

OP

STATE

TRANSMISSION

TIME

BSS1009 BSS1009:

SITE-75:

3 0 0 0 2005-06-16

12:29:54.00000

BSS1018 BSS1018:

SITE-10:

0 0 0 0 2005-05-13

17:22:05.00000

BSS1018 BSS1018:

SITE-10:

0 1 0 0 2005-05-13

17:22:05.00000

BSS1018 BSS1018:

SITE-10:

1 1 0 0 2005-05-13

17:22:04.00000

BSS1018 BSS1018:

SITE-11:

0 1 0 0 2005-05-13

17:22:06.00000

BSS1018 BSS1018:

SITE-11:

1 1 0 0 2005-05-13 1

7:22:06.00000

10-14 68P02901W19-S

Oct 2009

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 OMConly. The user can display the output on their terminal and save the file to /tmp or to a userdefined directory.

The user can generate a report for individual OMCs.

Usage

rtf_status [ -c directory]

The option available is:

-c directory Name of the directory where the output is to be stored. If -c is notused, the default directory is /tmp.

NOTEThe rtf_status utility uses batch_rlogin. Only users with BSS Remote Login privilegesshould have access to this utility.

All users have the ability to use this utility.

Input

laurel:omcadmin > rtf_status –c /home/omcadmin

Output

This utility generates RTF Device Status information, using batch_rlogin scripts.

It is only run on a single OMC.

Check the following RTFs in bss-1017

Check the following RTFs in bss-1016

RTF 0 0 at 2

RTF 0 1 at 2

RTF 0 2 at 2

RTF 0 3 at 2

RTF 0 4 at 2

RTF 0 5 at 2

RTF 1 1 at 4

68P02901W19-S 10-15

Oct 2009

site_outage Chapter 10: OMC Utilities

site_outage

This utility enables the user to generate a list of SITE Outage times based on Last RSL alarms inthe event logs and thus calculate the amount of time that the site was Out Of Service.

The user can generate a report for a single OMC or all OMCs in the Network. The default is All.

Usage

site_outage [ -a termAddress ] [-b OMCname ] [ -c directory ] [ -defl] StartDateStartTime EndDate EndTime

The options available are:

-a termAddress termAddress is the IP address of the terminal, site_outage run from.This option is used to display the report to the user.

-b OMCname OMCname is an OMC. Produces a report for OMCname. If -b is notused, the default is the OMCs in omc.lst.

-c directory Name of the directory where the output is to be stored.

If -c is not used, the default directory is /tmp.

-d Produces a detailed report showing: Site, Start Date, Start Time, EndDate, End Time and Outage Time.

-e Produces a summarized report showing: Site, Outage Time, Number ofMatched Outages, % OOS Duration Per Period, Alarms Unmatched andClears Unmatched.

-f Prompts the user to enter the IP address of the terminal, site_outageis being run from. Even if the -a option has been used, the input from-f takes preference.

-l Produces a list of OMCs in the network from which the user mustselect one. Even if the -b option has been used, the input from -l takepreference.

If neither -d nor -e is used, then both detailed and summarized report is generated.

StartDate and EndDate

StartDate and EndDate should be entered in the format yyyymmdd.

StartTime and EndTime should be entered in the format HHMMSS.

If no date or time is entered, the default will be the previous 24 hours.

All users have the ability to use this utility.

NOTEUnmatched Critical and Clear Alarms can distort the data. The occurrence of thesealarms is identified by the utility.

10-16 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration site_outage

Input

laurel:omcadmin > site_outage

Please Wait .....

Retrieving information from OMC laurel

The reports are being generated

Please Wait .....

Close Reports or Control C to exit.

Detailed report is in /tmp/SiteDetail.21619

Summary report is in /tmp/SiteSummary.21619

NOTETo view all data in the report, maximize the output window.

Output

OMC laurel

Detailed Site Outage Report

____________________________

Time Period 04/05/1999 16:24:13 - 05/05/1999 16:24:13

Site Start

Date

Start

Time

End

Date

End

Time

Outage Time

(HH:MM:SS)

BSS_1016(BSS_1016:SITE-2:): 5/05/1999 12:39:26 5/05/1999 12:39:54 0:0:28

BSS_1016(BSS_1016:SITE-2:): Not Found 5/05/1999 12:26:51

OMC laurel

Summarised Site Outage Report

______________________________

Time Period 04/05/1999 16:24:13 - 05/05/1999 16:24:13

Site Outage Time

(HH:MM:SS)

No. OfMatched

Outages

%OOSDuration

Per Period

Alarms

Unmatched

Clears

Unmatched

BSS_1016(BSS_1016:SITE-2:)

0:0:28 1 0.3 0 1

68P02901W19-S 10-17

Oct 2009

add_nei Chapter 10: OMC Utilities

add_nei

This utility enables the user to add neighbors both ways, regardless of the OMC on whichthey reside.

Only the omcadmin or Configuration Management experts should have the ability to use thisutility.

NOTEThe add_nei utility uses batch_rlogin. Only the users with BSS Remote Loginprivileges should have access to this utility.

Template files

This utility uses pre-defined files containing default values. The user should ensure that thesevalues are appropriate to the network, and make the updates appropriately. Where necessary,the OMC administrator can modify these files.

The template files for the neighbors can be found in:

/usr/omc/current/sbin/udata/templates

Input

laurel:omcadmin > add_nei

— — — — — — — — — — — — — — — — — — — — — — — — — —

add_nei will add neighbors, both ways, using batch_rlogin. It uses neighbour

templates stored in /usr/omc/current/sbin/udata/templates

The add_nei utility uses BSIC and BCCH frequency plans which are taken from

the MIB databases of all the OMCs

To get a new RF/BSIC plan: enter 'new' or 'N'

To use the old RF/BSIC plans: press Return

To quit: enter 'q'

Do you want to use default Country Code [001] and Network Code [01] for

Source Cell y/n ?

y

Do you want to use default Country Code [001] and Network Code [01] for

Neighbor Cell y/n ?

y

To input Source Cell: enter 'LAC-CI' (for example: 242-53512)

If sources now input, enter 'p' (proceed with add_nei)

To quit: enter 'q'

10-18 68P02901W19-S

Oct 2009

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-directoriesbeneath this:

/usr/omc/current/sbin/udata/neigh

del_nei

This utility enables the user to delete neighbors both ways, regardless of the OMC on whichthey reside.

Only the omcadmin or Configuration Management experts should have the ability to use thisutility.

NOTEThe del_nei utility uses batch_rlogin. Only the users with BSS Remote Loginprivileges should have access to this utility.

Input

laurel:omcadmin > del_nei

— — — — — — — — — — — — — — — — — — — — — — — — — —

del_nei will delete neighbors, both ways, using batch_rlogin.

del_nei uses BSIC and BCCH frequency plans which are taken

from the MIB databases of all the OMCs

To get a new RF/BSIC plan: enter ’new’ or ’N’

To use the old RF/BSIC plans: press Return

To quit: enter ’q’

N

Now collecting ARFCNs and BSICs for RFPlan...

laurel...

somc12...

To input Source Cell: enter ’LAC-CI’ (for example: 242-53512)

If sources now input, enter ’p’ (proceed with del_nei)

To quit: enter ’q’

68P02901W19-S 10-19

Oct 2009

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-directoriesbeneath this:

/usr/omc/current/sbin/udata/neigh

nei_sync

This utility enables the user to find and correct discrepancies in the BSIC and BCCH ofneighbors.

Only the omcadmin or Configuration Management experts should have the ability to use thisutility.

NOTEThe nei_sync utility requires the use of cmutil. Only the users with knowledge of thecmutil operation should use this utility.

Input

laurel:omcadmin > nei_sync

Output

This script is to find out and correct

the discrepancies in the bsic and

bcch of neighbours.

_______________________________

Generating the discrepancies in the OMC

Completed.

The full list of Neighbour discrepancies is in

/usr/omc/current/sbin/udata/neierr.txt

Any discrepancies to be resolved are in /usr/omc/current/sbin/udata/cmnei.in

Enter Control C to Quit window.

10-20 68P02901W19-S

Oct 2009

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 anOMC. Only the omcadmin or Configuration Management experts should have the ability touse this utility.

NOTEThe proxy_sync utility requires the use of cmutil. Only the users with knowledge ofthe cmutil operation should use this utility.

Input

laurel:omcadmin > proxy_sync

Output

This script is for Proxy Cell generation and addition to OMC

_____________________________________________________

Generating the Cells in the OMC

Generating the Cells from the neighbor list which are outside this OMC

Generating Network Wide Frequency plan

Now collecting ARFCNs for RFPlan...

laurel...

somc18..

Now collecting BSICs...

laurel...

somc18...

Processing - Generating BCCH and BSIC of proxies ...

Putting the proxycells in cmutil format...

Output in /usr/omc/current/sbin/udata/proxygen.op

Number of proxycells for this OMC = 0

Running cmutil to add the new proxies - ignore the error messages

which say object already existing

Running to cmutil to update the values of BCCH and BSIC

Addition and Updates finished successfully

Enter Control C to Quit window.

reparent_site

This utility enables the user to reparent a site from BSS to BSS and across OMCs.

68P02901W19-S 10-21

Oct 2009

reparent_site Chapter 10: OMC Utilities

Only the omcadmin or Configuration Management experts should have the ability to use thisutility.

Input

laurel:omcadmin > reparent_site BSS1017:SITE-8: BSS_1016

Performing the necessary checks for reparent_site

Checking that the links are disconnected.

Getting the list of OMCs on the network.

Locating OMC on which BSS_1016 resides.

Locating the BSS on which BSS1017:SITE-8: resides.

Enter the name that the site will be given on the new BSS

Press Return if you do not want the name to change.

<RETURN>

The site name is now BSS1017:SITE-8:

Enter the LAC that the site will be given on the new BSS.

Press Return if you do not want the LAC to change.

<RETURN>

The LAC is unchanged

The current RDN instance of BSS1017:SITE-8: = 8

8 is unused on BSS_1016

Enter the RDN instance that the site will be given on the new BSS.

Press Return if you do not want the RDN to change.

<RETURN>

The RDN instance is unchanged

Gathering a list of cells which will be created as proxy cells.

Extracting the Site information

Deleting site BSS1017:SITE-8:

Verifying Network-entities/containment.

Retrieving Network-entities/containment. . . .

Deleting Network-entities/containment. . .

Deleting a SITE

Creating input file BSS1017:SITE-8:.inp

Hierarchical extraction of BSS1017:SITE-8: in progress ...

Hierarchical extraction of BSS1017:SITE-8: completed

The deletion will fail if any of the forms for the objects are open for edit.

Please ensure this is not the case and will not be at any time while this

script is running.

Type “Y” to proceed, anything else will abort operation:

Y

10-22 68P02901W19-S

Oct 2009

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 thecontents of the CM MIB on a per OMC basis.

All users have the ability to use this utility.

Usage: ne_counter [ -r regionName ]

Input

laurel:omcadmin > ne_counter

Output

Network Entity Counter for laurel

__________________________________

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

Number of TCH(Speech): 15742

Enter Control C to quit

68P02901W19-S 10-23

Oct 2009

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

Operating Information: OMC-R System Administration Utility execution

Utility execution■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Overview

This section describes different execution mechanisms to invoke the utilities from the OMCenvironment and the procedures required to implement them. The following table lists therecommended execution mechanisms.

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

Command line

CAUTIONDo not execute a CTRL–C while any of the scripts are executing; allow all the scripts tocomplete execution once they are started.

The utilities are contained in /usr/omc/current/sbin and can be invoked from the commandline by typing the utility’s name and the appropriate options. If /usr/omc/current/sbin is inthe user’s PATH, only the utility name is required; otherwise the full path should be given, forexample:

dri_status –r Region1

or

68P02901W19-S 10-25

Oct 2009

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.

A sample cron file (utilities_cron) is provided. This file is located in:

/usr/omc/current/sbin/udata

CDE menu

To add a utility to the CDE menu, execute the following commands as omcadmin:cd /usr/omc/current/envvi .dtwmrc

Add the following to the Right Menu Description:

no-label f.separator

DRI Status f.exec “/usr/dt/bin/dtterm -title Dri_Status-e

rsh omc_splat /usr/omc/current/sbin/dri_status -f”

no-label f.separator

Network Reports f.exec “/usr/dt/bin/dtterm -title Network_Reports -e

rsh omc_splat /usr/omc/current/sbin/net_reports”

Alternatively, create a separate sub-menu list:

no-label f.separator

OMC General Utilities f.menu OMC_GEN_utils

no-label f.separator

###

#

# Utilities sub-menu description

#

###

Menu OMC_GEN_utils

{

”DRI Status” f.exec ”/usr/dt/bin/dtterm -title

DRI_Status -e rsh omc_splat /usr/omc/current/sbin/dri_status -f ”

“SITE Status” f.exec ”/usr/dt/bin/dtterm -title

SITE_Outage -e rsh omc_splat /usr/omc/current/sbin/site_outage”

}

10-26 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration cleanMib

cleanMib■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Introduction

The cleanMib script replaces the MIBCleanup script. The cleanMib script searches forcorruptions in the MIB database and fixes them.

The cleanMib detects or repairs the following types of database corruption:

• Orphan corruptions – objects with invalid or missing parent objects.

• Relationship corruptions – incorrect, duplicate or missing relationships.

• Invalid DN corruptions – objects with NULL DN strings.

These types of corruptions to prevent the success of some MIB actions, such as HierDelete andcmutil, and also cause the cmMib process to exit.

NOTEThis script should be run on machines during periods when there is no MIB activity.The cleanMib script should be run in report mode first, on a stable MIB. Theinconsistencies, if found, are written to the omcaudit logfile or usraudit logfile,depending on the setting of the environment variable LOG_TO_USRAUDIT.

The inconsistencies are also logged to a cleanMib logfile in /usr/omc/logs.

The inconsistency report can be examined and if any inconsistencies are found, the scriptcan be run in cleanup mode.

If orphans are detected, then it is recommended that HierDelete is executed on the affected siteafter the cleanMib script has been run in cleanup mode, and then to re-audit in the affected site.

Running cleanMib

The script may be executed in two different modes:

• To execute in Report Mode, use the –r parameter.

• To execute in Cleanup Mode, use the –c parameter.

Open an xterm from the Single Platform Processor. Type the following commands in the xterm:cleanMib –rorcleanMib –c

68P02901W19-S 10-27

Oct 2009

Running cleanMib Chapter 10: OMC Utilities

10-28 68P02901W19-S

Oct 2009

Chapter

11

Network Information Services (NIS)■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

68P02901W19-S 11-1

Oct 2009

Overview Chapter 11: Network Information Services (NIS)

Overview■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

NOTENIS is configured as the default naming service in the OMC-R environment. However,it is possible to configure an alternative naming service on the OMC-R. Motorola doesnot provide documentation or support for alternative naming services on the OMC-R.

Network Information Services (NIS) is a distributed naming service from Solaris, the purpose ofwhich is to ease the administration of computing environments comprising different machines.The use of NIS allows a task, that previously would have been performed on the network, to beperformed on the central administration system.

The NIS feature uses the concept of a master server and optional replicated server(s) and clientmachines. However, in the OMC-R environment, only a master server (the system processor)and clients are used.

The following topics are described in this chapter:

• NIS normal operation on page 11-3.

• NIS files and utilities on page 11-5.

• Changing user/group/host information on page 11-8.

11-2 68P02901W19-S

Oct 2009

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.

Map

All maps except /etc/mail/aliases are stored in /var/yp/<domainname> on the systemprocessor. The file /etc/mail/aliases must always be stored in /etc/mail (/etc/aliases is a hardlink to /etc/mail/aliases).

Domain

The NIS domain is a collection of systems using the same NIS database. All systems share acommon set of maps.

To participate in NIS, a system must belong to the NIS domain. Each domain has a unique name,for example, the default OMC-R domain is called omcadmin.

NOTEIf more than one OMC-R system is connected to the same LAN, each OMC-R musthave a unique NIS domain name.

Servers and clients

Because the network is database-oriented, system machines are arranged in two categories:servers and clients.

The NIS server is a machine storing a set of maps which are available to network hosts suchas clients. A server can also act as a client.

The NIS client runs processes that request data from the maps on the NIS servers. A client canalso act as a server.

68P02901W19-S 11-3

Oct 2009

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.

A slave holds a copy of this database and serves as a backup for the database. The terms masterand slaves are however, relative because a server can be a master for one system database anda slave for another system database.

Propagation

Propagation is the process by which a master server updates the data in slave servers withnew information entered in its own database. Propagation therefore ensures consistency ofdatabase information.

11-4 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration NIS files and utilities

NIS files and utilities■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The NIS service is composed of the following elements, some of which are part of the Solarisdistribution:

Daemons

Daemons are important to the functionality of the operating system. Daemons are programsthat run in the background to manage certain system functions.

Here are some of the NIS daemons:

• ypserv

The ypserv is a daemon typically activated at system startup. This daemon only runs onNIS server machines that have a complete NIS database. The prime function of the ypservdaemon is to look up maps in its local database of maps.

• ypbind

The ypbind is a daemon service typically activated at system startup. This daemonremembers all information that lets all NIS client processes on a node communicate withsome NIS server process. The daemon must run on every machine that has the NIS clientprocess.

NOTEBinding is a process that remembers the address at which the server daemonwas listening for requests. Binding creates a relationship between a client and aserver such that the client will always go to that address for information anddetermines whether a relationship is bound or unbound.

• ypxfrd

The ypxfrd daemon is a service that transfers complete NIS maps efficiently. This daemonshould be run on a master server.

• rpc.yppasswd

The rpc.yppasswd daemon is a service that modifies the NIS password map. The daemonchanges the network password associated with a particular user in the NIS database.

68P02901W19-S 11-5

Oct 2009

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

• ypwhich

The ypwhich command returns the name of the server, that supplies the NIS name serviceto the NIS client or that is the master for a map.

• yppoll

The yppoll command returns the order number of a ypserv process and the master serverfor the named map.

• ypmatch

The ypmatch command prints the values associated with one or more keys from the NISname services map specified by the map name.

Auxiliary utilities

• yppush

The yppush utility copies a new version of the NIS map from a master NIS server to theslave NIS servers. The command is run only on the master server by the Make file in/var/yp, after the master databases are changed.

• ypset

The ypset command points the daemon ypbind to a particular server.

• ypxfr

The ypxfr command moves the NIS map in the default domain from a master server toa slave server.

• makedbm

The makedbm command creates DBM files for the NIS map.

11-6 68P02901W19-S

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

68P02901W19-S 11-7

Oct 2009

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, – group information is using the OMC_Syncscript to invoke the user tool utility. Refer to the set of procedures in the section Administeringgroup accounts with usertool on page 2-8.

NOTEThis method is highly recommended because it updates the NIS automatically, ifconfigured.

Changing host name

NOTEA host name must be at least two characters: it can contain letters, digits and minussigns (-). Letters must be lower case. Illegal characters are: !“£$%^&*(){}~@?>:<|. >!].

Adding a new user to the NIS domain

NOTEChanges should only be made on the system processor through the OMC-R admin iconas user root because this is the master NIS server. If a user is not being recognizedon a machine, verify that the user exists in the /etc/passwd map.

If there is no entry for the user in the /etc/passwd map, one must be created in/etc/passwd and /etc/shadow files. The NIS must then be updated to allow thechanges to be propagated throughout the network.

11-8 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Adding a new group to the NIS domain

Procedure 11-1 Adding a new user to the NIS domain from the command line

1 Login to the system processor as user root.

2 Use the useradd utility to add the user entry to the /etc/passwd and/etc/shadow files. Enter the following command:useradd usrID

NOTEThe useradd utility only adds a user to the local system. Itcannot be used to change information supplied by the NISname service.

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.

NOTEThe length of the username parameter is restricted to eightcharacters.

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.

NOTEChanges should only be made on the system processor through the OMC-R admin iconas user root because this is the master NIS server. If a group is not being recognizedon a machine, verify that the group exists in the /etc/group/etc/passwd map.

If there is no entry for the user in the /etc/group/etc/passwd map, one must becreated in the /etc/group file. The NIS must then be updated to allow the changes tobe propagated throughout the network.

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:groupadd grpID

Continued

68P02901W19-S 11-9

Oct 2009

nsswitch.conf Chapter 11: Network Information Services (NIS)

Procedure 11-2 Adding a new group to the NIS domain from the command line(Continued)

NOTEThe groupadd utility only adds a group to the local system,it cannot be used to change information supplied by the NISname service.

3 Update the group map by entering the following commands:cd /var/yp/usr/ccs/bin/make group

nsswitch.conf

The nsswitch.conf file is a configuration file for the name service switch. The file controlswhether the system looks at NIS or files.

The template nsswitch files are /etc/nsswitch.nis and /etc/nsswitch.files. In its basic format,the file contains two columns. The first column contains the name of the map. The secondcolumn contains the method. For example, if the file had the following entries the system looksfor host information through NIS, and network information through the local file.

• hosts:nis.

• networks:files.

NIS server checks

Check that the ypserv daemon is running on the NIS server by executing the followingcommand, as user root on the NIS server:

ps -elf | grep ypserv

If the daemon is running, output similar to the following text (all on one line) is displayed:

8 S root 151 1 0 41 20 60634ce0 220 6072d5de Jul 20 ? 14;30/usr/lib

/netsvc/yp/ypserv

If the daemon is not running, enter the following command as user root to start the daemon:

/usr/lib/netsvc/yp/ypserv

The client must have a correct entry in its own /etc/hosts file to be able to locate the NIS serveror centralised information. If this is not the case and the nsswitch.conf file is set to files, theypcat command displays the following error:

RPC failure: RPC failure on yp operation

Check the clients /etc/defaultdomain file and make sure that the domain name is correct.

11-10 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Updating the NIS maps manually

NOTEThe domain name is generally set to omcadmin.

Check the /var/yp/binding/domainname/ypservers file on the client and make sure that it hasentries for the master and any replicated servers.

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, the hosts file to add a new host).

2 Execute the following commands to propagate the changes throughoutthe network:cd/var/yp/usr/ccs/bin/make mapname

NOTENIS is updated automatically when the OMC-R_Admin utilityis used to add, modify or delete users, groups or hosts.

NIS troubleshooting commands

The following commands can be used for troubleshooting purposes.

Commands Description

ypcat mapname This command gives a list of all the valuesin a map.

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

ypcat -x This command gives a list of all the mapnicknames.

ypwhich -m This command gives a list of all theavailable maps and their masters.

ypwhich -m mapname This command lists the master server for aparticular map.

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

ypcat map_or_alias_name This command shows the contents of theNIS files.

68P02901W19-S 11-11

Oct 2009

NIS troubleshooting commands Chapter 11: Network Information Services (NIS)

11-12 68P02901W19-S

Oct 2009

Chapter

12

Backup Server Installation and Configuration■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

68P02901W19-S 12-1

Oct 2009

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 onany processor within the OMC-R system. It is assumed that the appropriate license is obtained.It also supports the Informix utility, onbar, and in the backup and restore of the Informixdatabases. Refer to Installation and Configuration: OMC-R Clean Install (68P02901W47) forfurther details. There are three main interactive utilities in StorEdge Enterprise Backup.

The Networker GUI: This java application is accessed using the mozilla web browser onthe OMC-R.

nwbackup, for backing up complete UNIX file systems or parts. In particular, the utility is usedfor marking the file systems required to be backed up and then performing the actual file systembackup to the specified labelled tape. It can be invoked manually or can be scheduled. The useof nwbackup is not recommended for making regular backups.

nwrecover, for restoring complete UNIX file systems or parts. In particular, the utility is usedfor restoring the file systems that were initially backed up on tape media using the nwbackuputility or by a scheduled backup.

The above utilities are normally used in an interactive environment. However, they can beinvoked from the UNIX command line. This method is not used except in a disaster recoverysituation. The StorEdge Enterprise Backup is configured, within the OMC-R environment, asone server module and several client modules:

• server module is the main part of the program, installed on the single platform processor.It controls the physical media devices, internal processes of the backup or restore andcommunicates with the client modules.

• client module is installed on each processor within the OMC-R system including thesingle platform processor. The client module informs the server module to perform thebackup in case of manual backups.

The backup and restore procedures are configured to be performed from the server (singleplatform processor). However, the procedures can be configured so that backup or restore canbe performed from other processors, which have access to local tape drives.

Perform complete file system backups after each major installation or reconfiguration of theOMC-R such as disk repartitioning. These types of file system backup are normally performedin single user mode to ensure resilience and reliability. Create two tape sets of the OMC-Rbackup, with one complete set stored offsite.

To avoid the OMC-R being shut down (to single user mode) during normal operational activity,the backup process can be performed in multi-user mode. However, in multi-user mode, thefile systems can be in a changing state and the backup tapes may not reflect the file systemsaccurately. Operator intervention may be required to change the tapes during the backupor restore.

12-2 68P02901W19-S

Oct 2009

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. However, itis recommended to check that the device has been installed correctly.

• Schedule configuration

The schedule configuration is an important part of the backup configuration. It givesthe details of the complete and incremental backups performed and also when theseare overridden.

• Group configuration

Group configuration specifies when a backup is running and has control of clients withinthe group. New groups can be set up although the default group setup is sufficient. Theclients can be configured to use the groups.

• Client configuration

A client is the host which is required to be backed up. This also includes the server, as itneeds to be a client to perform the backups of itself.

• Mounting the tape backup media

• Manual backups

• Restoring files

• Recovering the OMC-R system after a disaster

It is possible that one of the disks on the OMC-R system fails at some point. Although this rarelyhappens, the hard disk is a focal point of failure because of the constantly moving parts.

If there is data on the disk which is easily recoverable, it can be copied onto the new disk. If thedata on that disk is not recoverable, there are several methods of recovering the system, forexample:

• Restoring a non system disk

• Restoring the backup indexes

• Restoring the system disk

NOTEThe term Backup Server refers to the Single Platform Processor server.

68P02901W19-S 12-3

Oct 2009

Software Installation Chapter 12: Backup Server Installation and Configuration

Software Installation■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The StorEdge Enterprise Backup software is delivered on the GSR9 1.9.0.0.X Additional OMCSoftware DVDROM. To install the software, 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/installcp /cdrom/cdrom0/suninstall/lib/backup.lib /var/install/libcp /cdrom/cdrom0/suninstall/data/package_list \/var/install/datacp /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, the Administration GUI utilityis always called from the system processor.

When restoring the system processor, nwrecover is always called from the system processor.

When restoring the GUI processor, nwrecover is always called from the GUI processor.

Software Licenses

EBS Network Edition License: EBS Network Edition License file is needed for thebackups of the GSM OMC-R Server. License file is supplied by Motorola and can be installedon the GSM OMC-R.

Legato Informix Module License (For each client): A Legato Informix Module licenseis needed for Backup of the Informix Databases on the Server. The Legato Informix Modulelicense is supplied by Motorola and can be installed on the Single Platform Processor.

12-4 68P02901W19-S

Oct 2009

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.

2 Execute the following command as user root:/var/install/backup/setup_backup_server.sh

3 Select Option 1.Enter Local Tape Device (Q to Quit): [/dev/rmt/0c]Press Enter to select default or enter the path to device (unless another tapedrive has been connected, the default is valid).

4 Select correct Device Media Type for your tape drive.

5 Enter a name to use for the tape and it will be labelled and mounted.

6 To Do you wish to configure the licensing information …, you can entern (and the software will work for 30 days) or enter y if you have purchased alicense code.

7 If the Bootstrap is already configured, then do not reconfigure it. Otherwisefollow Procedure 12-4to configure it.

8 The script returns to the Main Menu, select Quit.

Configuring Sun StorEdge Enterprise Backup Server Licenses

Follow Procedure 12-3, to configure the Sun StorEdge Enterprise Backup Server Licenses:

NOTEEBS Network Edition for Solaris and EBS Module for Informix, Unix Client arerequired on the Backup Server.

68P02901W19-S 12-5

Oct 2009

Configuring Bootstrap Notifications Chapter 12: Backup Server Installation and Configuration

Procedure 12-3 Sun StorEdge Enterprise Backup Server License Configuration

1 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 ServerSoftware. Output like the following is displayed:

Enter enabler code for license:

3 Enter the Enabler Code. A message is displayed, requesting confirmation of theenabler code. Enter Yes (case-sensitive) to accept the Enabler Code.If the Enabler code is invalid/incorrect, an ERROR message is followedby 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, enter y, otherwise enter n to continueto the Bootstrap Notification Configuration.

Configuring Bootstrap Notifications

To configure the Bootstrap notifications, follow these steps:

Procedure 12-4 Bootstrap Notification Configuration

1 Bootstrap information will then need to be configured. Output like thefollowing is displayed:

** BOOTSTRAP CONFIGURATION

Bootstrap Information is required to allow

for a fast recovery.

Select Delivery Option:

1. Bootstrap via e-mail

2. Bootstrap copied to local file

Enter option:

2 If Option 1 is selected, refer Configuring Bootstrap Notification throughE-mail on page 12-6.

If Option 2 is selected, refer Configuring Bootstrap Notification to localfile on page 12-7.

Configuring Bootstrap Notification through E-mail

To configure the Bootstrap notifications through e-mail, follow these steps:

12-6 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Configuring Bootstrap Notification to local file

NOTEFor email notifications to operate, a mailhost must be configured in /etc/hosts or DBSon the Backup Server.

Procedure 12-5 Bootstrap Notification through E-mail Configuration

1 Select Option 1 to automatically configure the Bootstrap Notifications to besent through e-mail. A message like the following is displayed:

Option "1: Bootstrap via e-mail" selected

Enter e-mail address:

2 Enter the E-mail address. A prompt requesting a confirmation on the E-mailaddress entered is displayed.

3 Enter Yes (case-sensitive) to continue.

4 Bootstrap notification is setup.

Configuring Bootstrap Notification to local file

To configure the Bootstrap notifications to local file, follow these steps:

CAUTIONIt is important that a copy of the bootstrap notification file is available to allow fora fast recovery. Data recovery takes considerably long time if this information isunavailable. The recommendations are to:

• Print a copy of the file and place it in the system folder.

• Copy the file to a remote location in case a restore needs to take place.

68P02901W19-S 12-7

Oct 2009

Configuring Bootstrap Notification to local file Chapter 12: Backup Server Installation and Configuration

Procedure 12-6 Bootstrap Notification to local file Configuration

1 Select Option 2 to automatically configure Bootstrap Notifications to bestored locally in a file. A message similar to the following is displayed:

Option "2. Bootstrap copied to local file" selected

Enter file (absolute path):

2 Enter absolute path to the file to be created containing the bootstrapinformation (for example, /bootstrap/bootstrap.txt). A prompt requestinga confirmation on the file entered is displayed.

3 Enter Yes (case-sensitive) to continue.

4 Bootstrap notification will be setup.

5 Select option 5 to quit the setup program.

1. Initialize Backup Server

2. Add Backup Client

3. Update Backup Client

4. Delete Backup Client

5. Quit

Enter Option:

5

12-8 68P02901W19-S

Oct 2009

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 omcpkill nameserver/usr/omc/sbin/configure_solstice

NOTEThis step causes an OMC outage.

3 Select y to continue.

4 Select y to back up logical logs. Logical log backups are necessary torecover recent database updates. If there is no need to restore the databaselogical logs, select n.

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. Bear in mind that storing

Logical Logs may require additional tapes and that the

database could fail if tapes are not changed when the Informix

Engine requests them to be changed.

Will you be storing Logical Logs ? [y n] y

Re-Starting the PM Database Instance

Re-Starting the CM Database Instance

Creating /usr/informix/etc/ixbar.2 for PM Database Instance

Sun Microsystems Inc. SunOS 5.10 Generic January 2005

logout

Creating /usr/informix/etc/ixbar.1 for CM Database Instance

Sun Microsystems Inc. SunOS 5.10 Generic January 2005

logout

6 Execute the following command as user root:svcadm enable omc

68P02901W19-S 12-9

Oct 2009

Completing backup server setup Chapter 12: Backup Server Installation and Configuration

Completing backup server setup

Follow Procedure 12-8 to set up backup clients.

Procedure 12-8 Completing backup server setup

1 Execute the following command as user root:/var/install/backup/setup_backup_server.sh

2 Select option 2 to add a backup client. There are several backup clienttypes, such as, Informix_CM, Informix_PM, Informix_IX1, and Informix_IX2.

3 Enter the hostname of the system to be backed up. For the SPLAT, createeach of the following client types by repeatedly selecting option 2 to add aclient. Select the option number corresponding to the client to be created.2. Informix_CM3. Informix_PM4. Informix_IX15. Informix_IX2

4 If there is a GUI server, enter the name of the GUI server and selectGUI_SERVER as the server type.

5 Once all the backup clients have been created, select option 5 to exit thescript.

NOTEOnce a client is registered with the Backup Server, it is automatically setup to backupto the Backup Server at a time designated by that group. The times are as follows:

• Default group runs at 01:30 Daily.

• Informix ixbar files groups run at 03:40 Daily.

After the backup server is configured, the default group's start time is 3:33, andit is disabled.

Backups of Informix databases are controlled by a crontab entry. The crontab entriesare automatically created by the /usr/omc/sbin/configure_solstice script.

Enabling or Disabling a Group Backup

Once the backup clients are added, the backup groups are enabled or disabled according to thedefault settings in the configuration file /var/install/backup/backup_set.cfg.

Follow Procedure 12-9 to enable or disable a Group Backup client.

NOTEEnsure that the backup client belonging to the backup group exists, before enablingor disabling a backup client.

12-10 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Deleting a Group Backup client

Procedure 12-9 Enabling or Disabling a Group Backup client

1 Execute the following command as user root:/var/install/backup/setup_backup_server.sh

2 Select option 3 to update a backup client.

3 Select the hostname of the system from the machine list.

4 Select the option number of the backup client. The following message isdisplayed:

Do you want to Enable (Press e) or Disable (Press d)the group backup for Informix_IX1?

To enable the group, enter e.To disable the group, enter d.

5 Repeat step 2 to step 4 to update all the backup clients.

NOTEThe group backup for the clients Informix_CM and Informix_PM isdisabled by default.Selecting the backup client as Informix_CM or Informix_PM, displaysthe following message:

There is a cron job set defaultly for INFORMIX_CM& INFORMIX_PM backup.

So NSR group INFORMIX_CM or INFORMIX_PM is notpermitted to enable auto start!

Quit updating...

6 Select option 5 to exit the script.

Deleting a Group Backup client

Follow Procedure 12-10 to delete a backup client.

NOTEEnsure that the backup client exists, before deleting a backup client.

68P02901W19-S 12-11

Oct 2009

Manually starting a Group Backup Chapter 12: Backup Server Installation and Configuration

Procedure 12-10 Deleting a backup client

1 Execute the following command as user root:/var/install/backup/setup_backup_server.sh

2 Select option 4 to delete a backup client.

3 Select the hostname of the system from the machine list.

4 Select the option number of the backup client.

5 Repeat step 2 to step 4 for all the backup clients to be deleted.

6 Select option 5 to exit the script.

Manually starting a Group Backup

Use the following procedure to initiate a manual backup of a group:

NOTEBackups are done at a group level and not at a client level. If there are two clients inthe PM Backup group, then both will be backed up in parallel.

Procedure 12-11 Enable backups{34618}

1 Execute the following command as user root:nsradmin

2 At the nsradmin> prompt, type visual and a GUI is displayed.

3 Click Select and NSR Group.

4 Click Next until the name of the group is the desired group (for example,INFORMIX_IX2). (For all file systems, select Default.)

5 Select Edit and change autostart to Start Now.

6 If you want to perform an incremental backup instead of a full backup, changethe value of the option force incremental to yes.

7 Press Esc and select Yes to apply the changes. Once the changes have beenapplied, the backup of all clients in the backup group starts.

8 Select Quit, to quit the GUI interface.

9 Type quit, to quit nsradmin. When the backup is complete, the followingmessage gets displayed on the screen.

May 16 05:30:26 zuk14omc11 root: Sun StorEdge(TM)Enterprise Backup savegroup: (notice) Default completed,Total 1 client(s), 1 Succeeded with warning(s).Please see group completion details for more information.

12-12 68P02901W19-S

Oct 2009

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.

Table 12-1 Log files produced by backup server

Log Type Log File Location

Backup Server Configuration Logfiles /var/install/logs

OMC-R Backup Server Status Logfiles /nsr/logs

Log files (Client machines)

The log files produced by the client machines are located in the following directory.

Table 12-2 Log files produced by client machines

Log Type Log File Location

Backup Logfiles /usr/omc/logs/bar_mib.log/usr/omc/logs/bar_omc.log

Backup Status Logfiles /nsr/logs

Manual backup of Informix databases

Procedure 12-12 Full Backup of Informix databases{34618}

1 To setup the ixbar files, execute the following commands as user Informix:cd /usr/informix/etc(If there are no ixbar.1 and ixbar.2 in this directory, produce them by copyingthe latest version from files taken as backup, as shown in the followingcommands.)cp ixbar.1.<most recent date> ixbar.1cp ixbar.2.<most recent date> ixbar.2

For example:

cp ixbar.1.2006109.122546 ixbar.1

Continued

68P02901W19-S 12-13

Oct 2009

Manual backup of Informix databases Chapter 12: Backup Server Installation and Configuration

Procedure 12-12 Full Backup of Informix databases (Continued)

2 To backup the PM database execute the following commands as userInformix:mib_envonbar -b -w -L 0onbar –m

If the output matches the following line, the backup succeeded:

2009-05-07 23:17:07 13310 13308 Completed level 1 backup rootdbs(Storage Manager copy ID: 1241709427 1241709428).

2009-05-07 23:17:07 13310 13308 Begin level 1 backup logsdbs.

2009-05-07 23:17:08 13310 13308 Completed level 1 backup logsdbs(Storage Manager copy ID: 1241709428 1241709430).

2009-05-07 23:17:09 13310 13308 Begin level 1 backup physdbs.

2009-05-07 23:17:09 13310 13308 Completed level 1 backup physdbs(Storage Manager copy ID: 1241709429 1241709432).

2009-05-07 23:17:09 13310 13308 Begin level 1 backup mib_db_sp1.

2009-05-07 23:17:10 13310 13308 Completed level 1 backup mib_db_sp1(Storage Manager copy ID: 1241709430 1241709434).

2009-05-07 23:17:10 13310 13308 Archive on rootdbs, logsdbs, physdbs,mib_db_sp1 Completed (Requested Level 1).

2009-05-07 23:17:10 13319 13317 /usr/informix/bin/onbar_d -b -l

2009-05-07 23:17:10 13310 13308 Begin backup logical log 25.

2009-05-07 23:17:10 13319 13317 (-43395) A log backup isalready running. Can't start another.

2009-05-07 23:17:10 13310 13308 Successfully connected toStorage Manager.

2009-05-07 23:17:11 13310 13308 Completed backup logical log 25(Storage Manager copy ID: 1241709431 1241709432).

2009-05-07 23:17:11 13325 13323 /usr/informix/bin/onbar_d -b -l

2009-05-07 23:17:11 13325 13323 /usr/informix/bin/onbar_d complete,returning 0 (0x00)

Continued

12-14 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Manual backup of Informix databases

Procedure 12-12 Full Backup of Informix databases (Continued)

3 To backup the CM database execute the following commands as userInformix:

omc_envonbar -b -w -L 0onbar -m

If the output matches the following line, the backup succeeded:

Onbar activity log file: /usr/omc/logs/bar_omc.log

2009-05-07 23:18:26 13358 13356 Completed level 1 backup omc_db_sp6(Storage Manager copy ID: 1241709506 1241709518).

2009-05-07 23:18:26 13358 13356 Begin level 1 backup omc_db_sp7.

2009-05-07 23:18:27 13358 13356 Completed level 1 backup omc_db_sp7(Storage Manager copy ID: 1241709507 1241709520).

2009-05-07 23:18:27 13358 13356 Begin level 1 backup omc_db_sp8.

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:28 13358 13356 Begin level 1 backup omc_db_sp9.

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:29 13358 13356 Archive on rootdbs, omc_db_llog,omc_db_plog, omc_db_sp1, omc_db_sp10, omc_db_sp11, omc_db_sp12,omc_db_sp2, omc_db_sp3, omc_db_sp4, omc_db_sp5, omc_db_sp6,omc_db_sp7, omc_db_sp8, omc_db_sp9 Completed

(Requested Level 1).

2009-05-07 23:18:29 13385 13383 /usr/informix/bin/onbar_d -b -l

2009-05-07 23:18:29 13358 13356 Begin backup logical log 23.

2009-05-07 23:18:29 13358 13356 Successfullyconnected to Storage Manager.

2009-05-07 23:18:29 13385 13383 (-43395) A log backup isalready running. Can't start another.

2009-05-07 23:18:31 13358 13356 Completed backup logical log 23(Storage Manager copy ID: 1241709510 1241709511).

2009-05-07 23:18:31 13391 13389 /usr/informix/bin/onbar_d -b -l

2009-05-07 23:18:31 13391 13389 /usr/informix/bin/onbar_d complete,returning 0 (0x00)

2009-05-07 23:18:31 13397 13395 /usr/informix/bin/onbar_d -b -l

2009-05-07 23:18:31 13397 13395 /usr/informix/bin/onbar_d complete,returning 0 (0x00)

4 Backup Informix ixbar files:Execute the Procedure 12-11 to backup group INFORMIX_IX1.Execute the Procedure 12-11 again to backup group INFORMIX_IX2.

68P02901W19-S 12-15

Oct 2009

Backing up the GUI Server File System Chapter 12: Backup Server Installation and Configuration

Procedure 12-13 Incremental Backup of Informix databases{34618}

1 To perform an incremental backup (that is, changes since last full backup)of the Informix databases. Follow the Procedure 12-12. Above, replace theoccurrences of the line onbar -b -w -L 0with onbar -b -w -L 1.

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.

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

The backup may be performed to a local tape drive (that is attached to the GUI Server) orremotely to the Single Platform Processor tape drive.

NOTEEnsure there is no CD/DVD in the CD/DVD drive before performing the backup.

12-16 68P02901W19-S

Oct 2009

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 Serverautomatically:

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.

2 Insert a new labeled DAT tape into the appropriate processor tape drive,ensuring that it is not write-protected.

3 Change to the /usr/omc/current/sbin directory by entering the followingcommand:cd /usr/omc/current/sbin

4 Enter the following command to run the backup_MMI utility../backup_MMI.The following prompt is displayed:

Please indicate whether a local backup to the MMI/GUI Processor orremote backup to the Single Platform Processor is requiredL. Local Backup to the MMI/GUI ProcessorR. Remote Backup to the Single Platform ProcessorQ. Quit UtilityEnter Choice:Enter one of the following:L - for a local backup to the tape drive on the GUI Server.R - for a remote backup to the tape drive on the Single Platform Processor.

5 The following output is displayed:

Valid Backup Tape TypesD. DATC. CARTRIDGEQ. QUITEnter Backup Tape Type:

Enter the appropriate backup tape type: D - for DAT tape drive.

6 The following prompt is displayed:

Is there a writeable DAT/Cartridge tape loaded in the Tape Drive ?Y. YES to continueQ. QUITEnter Choice:

Enter Y when the tape light has stopped flashing and is permanently lit green.

Continued

68P02901W19-S 12-17

Oct 2009

Backing up the GUI Server File System Chapter 12: Backup Server Installation and Configuration

Procedure 12-14 Performing a backup of the UNIX file systems on the GUI Server(Continued)

7 The following prompt is displayed:Enter Local Tape Device (Default is /dev/rmt/0)(Q to QUIT).

Enter the backup tape device name as /dev/rmt/0n.

8 In this example, the backup is being performed on a Sunblade 150 GUI Server,to a tape drive on the Single Platform Processor.

NOTEThe order in which the file systems are backed up is important whenit comes to the restore. As shown in the Table 12-3 below.

In the example below / (root) will be Number 1, /omcgen will be Number 2,/usr/omc will be Number 3.

Output similar to the following example is displayed.

FILESYSTEM BACKUP TO somc57 TAPE DEVICE /dev/rmt/0n

Attempting to archive the following partitions://omcgen/usr/omcBacking up the / filesystemDUMP: Date of this level 0 dump: Wed Jul 06 11:39:01 2005DUMP: Date of last level 0 dump: the epochDUMP: Dumping /dev/md/rdsk/d0 (sunblade3:/) tosomc57:/dev/rmt/0n.DUMP: Mapping (Pass I) [regular files]DUMP: Mapping (Pass II) [directories]DUMP: Writing 32 Kilobyte recordsDUMP: Estimated 5223950 blocks (2550.76MB).DUMP: Dumping (Pass III) [directories]DUMP: Dumping (Pass IV) [regular files]DUMP: 42.89% done, finished in 0:13DUMP: 87.66% done, finished in 0:02DUMP: 5223934 blocks (2550.75MB) on 1 volume at 1937 KB/secDUMP: DUMP IS DONEBacking up the /omcgen filesystemDUMP: Date of this level 0 dump: Wed Jul 06 12:01:35 2005DUMP: Date of last level 0 dump: the epochDUMP: Dumping /dev/md/rdsk/d10 (sunblade3:/omcgen) tosomc57:/dev/rmt/0n.DUMP: Mapping (Pass I) [regular files]DUMP: Mapping (Pass II) [directories]DUMP: Writing 32 Kilobyte recordsDUMP: 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

Operating Information: OMC-R System Administration Backing up the GUI Server File System

Procedure 12-14 Performing a backup of the UNIX file systems on the GUI Server(Continued)

DUMP: DUMP IS DONE

Backing up the /usr/omc filesystemDUMP: Date of this level 0 dump: Wed Jul 06 12:01:37 2005DUMP: Date of last level 0 dump: the epochDUMP: Dumping /dev/md/rdsk/d15 (sunblade3:/usr/omc) tosomc57:/dev/rmt/0n.DUMP: Mapping (Pass I) [regular files]DUMP: Mapping (Pass II) [directories]DUMP: Writing 32 Kilobyte records

DUMP: Estimated 919936 blocks (449.19MB).DUMP: Dumping (Pass III) [directories]DUMP: Dumping (Pass IV) [regular files]DUMP: 919934 blocks (449.19MB) on 1 volume at 2490 KB/secDUMP: 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, in this example two more times in order to check the completebackup.

NOTEThe confidence check command line in step 9 must be entered oncefor each partition that has been backed up. In this procedure, thereare three file systems that have been backed up, therefore it isnecessary to enter this command a total of three times.

11 If the confidence check performed in step 9 is successful, write-protect, label,and store the tape(s). If an error is returned, replace the faulty tape and repeatthe backup procedure from step 2.A log file is kept in /usr/omc/logs/backup_MMI.<datestamp>.

Fill out the table below with the details:

Table 12-3 Order of backing up file systems

Number File system

1

2

3

4

68P02901W19-S 12-19

Oct 2009

Disaster Recovery Chapter 12: Backup Server Installation and Configuration

Disaster Recovery■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Disaster Recovery GSM OMC-R server

CAUTIONBootstrap information MUST be available; otherwise the system cannot be restoredusing this method.

Bootstrap information is automatically stored on the Single Platform Processor.Execute the following command as user root to list the bootstraps:mminfo –B

{34618} After the backup, you should run this command to get the last row, it is thelatest bootstrap information of your system. This will be used during the disasterrecovery.

Recovery of bootstrap information

In the event that bootstrap information is unavailable, it can be recovered by executing thefollowing procedure:

Procedure 12-15 Recovery of bootstrap information

1 Insert the latest backup tape into the tape drive.

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 followingcommand:/usr/sbin/nsr/nsrmm

NOTEThe outputs displayed below are examples of GSM OMC-R disaster recovery.

Procedure 12-16 Disaster Recovery: Starting JumpStart

1 Insert the latest JumpStart media onto the client machine, and at the okprompt, execute as user root:Boot cdrom -- restore solbak

Continued

12-20 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Disaster Recovery GSM OMC-R server

Procedure 12-16 Disaster Recovery: Starting JumpStart (Continued)

2 Once the server has booted from the installation media, an informationwindow similar to the following is displayed.

IMPORTANT:

THIS INFORMATION MUST BE CORRECT FOR THE DISASTER

RECOVERY TO COMPLETE.

INFORMATION WILL ONLY BE ASKED FOR ONCE!

=================================================

Basic Disaster Recovery Information

=================================================

3 Press Enter to continue.

Entering network information

To enter the platform network information, follow this step:

Procedure 12-17 Disaster Recovery: Entering network information

The user is prompted to enter the platform’s network information. Respond toeach prompt with the correct information.

Enter the machine's primary hostname: somc85

Enter the machine's IP address: 175.3.44.178

Enter the machine's netmask: 255.255.255.0

Enter the machine's default router (leave blank if not

required): 175.3.44.85

Entering backup tape device information

NOTEThe questions relate to the backup tape device connected to the Backup Server.

68P02901W19-S 12-21

Oct 2009

Disaster Recovery GSM OMC-R server Chapter 12: Backup Server Installation and Configuration

To enter the backup tape device information, follow this procedure:

Procedure 12-18 Disaster Recovery: Entering backup tape device information

The user is prompted to enter the backup tape device information. Respondto each prompt with the correct information.

Enter Local Tape Device to be restored from: /dev/rmt/0hbn

Valid media types are:

1. DDS4

2. DAT72

3. DLT 7000

4. LTO-3

Enter Number for Device Media Type: 1

Entering bootstrap information

To enter the bootstrap information, follow this step:

Procedure 12-19 Disaster Recovery: Entering bootstrap information

The user is prompted to enter the bootstrap information. Respond to eachprompt with the correct information.

Enter latest bootstrap saveset id: 2808799757

Enter starting file number: 22

Enter starting record number: 0

12-22 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Disaster Recovery GSM OMC-R server

Confirming the disaster recovery information

To confirm the disaster recovery information entered, follow this step:

Procedure 12-20 Disaster Recovery: Confirming the installation information{34618}

1 Recovery begins once all the requested information has been provided.

2 Installation of OS is begun (takes a long time, >1 hour).

3 Once the OS is installed, a command prompt will be available.

4 Log in to the system as root and follow Procedure 12-1 to install the BackupServer software.

5 Create a Tape device using nsradmin/usr/sbin/nsr/nsradminSelect visual by typing visualThe following screen gets displayed.

Select Create (Using arrow keys and pressing return to select )Select NSR deviceAccept default or edit the name to suite your tape device setting and selectmedia type, For example 4mm 20GB or DAT72.Save your settings by pressing the Escape key and selecting Yes with theReturn key.

Continued

68P02901W19-S 12-23

Oct 2009

Disaster Recovery GSM OMC-R server Chapter 12: Backup Server Installation and Configuration

Procedure 12-20 Disaster Recovery: Confirming the installation information(Continued)

Select Quit.Type Quit and return at the prompt to return to the OS shell.

Recovery using Bootstrap Saveset IDs

Use the following procedure to recover the Backup Server configuration:

Procedure 12-21 Recovering using Backup Server configuration

1 Enter the following command as user root:/usr/sbin/nsr/mmrecovThe following is an example of a typical bootstrap notification:

July 16 09:44 2003 backup1's bootstrap information Page 1

date time level ssid file record volume

07/11/06 01:35:18 full 235292161 56 0

backup1_Jun15

2 Enter the latest bootstrap save set ID (ssid) when requested. In the exampleabove, this value is 235292161.

Continued

12-24 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Disaster Recovery GSM OMC-R server

Procedure 12-21 Recovering using Backup Server configuration (Continued)

3 Enter the starting file number (file) when requested. In the example above,this value is 56.

4 Enter the starting record number (record) when requested. In the exampleabove, this value is 0. At this point, insert the tape containing the savesetidentified by the bootstrap information into the tape drive on the OMC-Rand press RETURN.

NOTEOnce all requested information has been entered and the tape hasbeen inserted in the drive, the system starts retrieving the serverconfiguration information from the tape.

The output of the mmrecov command will be similar to the example below:

Scanning /dev/rmt/0mbn for save set 3870043393; this

may take a while...

scanner: scanning 4mm tape backup1_June15 on /dev/rmt/0mbn

/nsr

/nsr: file exists, overwriting

/solbak/nsr/res.R/servers

/solbak/nsr/res.R/nsrla.res

/solbak/nsr/res.R/nsrjb.res

/solbak/nsr/res.R/mot.res

/solbak/nsr/res.R/temip.res

/solbak/nsr/res.R/nsr.res

/solbak/nsr/res.R/

nsrmmdbasm -r /solbak/nsr/mm/mmvolume6/

/solbak/nsr/mm/

scanner: ssid 3870043393: scan complete

scanner: ssid 3870043393: 548 KB, 10 file(s)

/dev/rmt/0mbn: Mount operation in progress

/dev/rmt/0mbn: verifying label, moving backward 2 file(s)

/dev/rmt/0mbn: mounted 4mm tape backup1_June15 (write protected)

If your resource files were lost, they are now recovered in the

'res.R' directory. Copy or move them to the 'res'

directory, after you have shut down the service. Then restart

the service. Otherwise, just restart the service.

If the on-line index for backup1 was lost, it can be recovered using thensrck command.

Continued

68P02901W19-S 12-25

Oct 2009

Disaster Recovery GSM OMC-R server Chapter 12: Backup Server Installation and Configuration

Procedure 12-21 Recovering using Backup Server configuration (Continued)

5 Once the server configuration information has been successfully retrieved,shutdown the NetWorker services by executing the following commandas 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 /nsrmv res res.origmv 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 followingcommand:ps -ef | grep nsrOutput 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

Operating Information: OMC-R System Administration Recover the Necessary Filesystems

Procedure 12-21 Recovering using Backup Server configuration (Continued)

9 Recover the indexes:As user root:

/usr/sbin/nsr/nsrck -L7

Output of the command is similar to the following:

nsrck: checking index for 'backup1'

nsrck: The file index for client 'backup1' will be recovered.

nsrck: Recovering index savesets of 'backup1' from 'backup1'

NSR server ‘backup1‘: busy

recover: waiting 30 seconds then retrying

Recover completion time: Fri Jun 15 14:41:06 200

nsrck: completed recovery of index for client 'backup1'

nsrck: /solbak/nsr/index/backup1 contains 417850 records

occupying 66 MB

nsrck: Completed checking 1 client(s)

Recover the Necessary Filesystems

Use the following procedure to recover the necessary filesystems:

Procedure 12-22 Recover the Necessary Filesystems{34618}

NOTEA graphical display is needed for the rest of the procedure.

1 Set your display and enter the following commands:Start the restore program by issuing the following commands as user root:

cd //usr/bin/nwrecover &

2 Select the root file system (/) for restore from the left pane in the nwrecovermain window. Once a file system has been selected for restore, the checkbox gets ticked.

Continued

68P02901W19-S 12-27

Oct 2009

Recover the Necessary Filesystems Chapter 12: Backup Server Installation and Configuration

Procedure 12-22 Recover the Necessary Filesystems (Continued)

3 Once the root file system has been selected, all directories which are mountpoints 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.

5 Navigate to the /directory and deselect the /solbak/nsr directory.

6 Navigate to the /etc directory and deselect the file path_to_inst.The /dev and /devices directories, together with the /etc/path_to_instfile, must not be restored as these are configured by the Operating Systeminstallation.

7 The selection of file systems for restoration is now complete. To begin therestore, click the Start button.

Continued

12-28 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Recover the Necessary Filesystems

Procedure 12-22 Recover the Necessary Filesystems (Continued)

8 A Conflict Resolution window is displayed.Select No for the question:Do you want to be prompted when conflict occurs?Select Overwrite the existing file for the question:When conflict occurs, the program should? Click OK to proceed.Click OK to proceed.

9 The restore will restore these filesystems. A Recover Status window will bedisplayed, indicating the current status of the Restore.

10 When a Recover completion time message appears in the Recover Statuswindow, the recovery of the filesystem is complete.

11 Click Cancel to return to the nwrecover main window

12 Click File and Exit to quit nwrecover.

13 Check /usr/omc.If the output matches the following lines, it is incomplete. You shouldcontinue steps 14 to 21.

# ls /usr/omc

logs lost+found ne_data

If the output matches the following lines, it is complete. Skip steps 14 to 21,proceed to step 22 directly.

# ls /usr/omc

1.9.0.0.34 config lib lost+found sbin

cdrom_install current logs ne_data sec

14 Start the restore program by issuing the following commands as user root torestore /usr/omc again:

cd //usr/bin/nwrecover &

Continued

68P02901W19-S 12-29

Oct 2009

Recover the Necessary Filesystems Chapter 12: Backup Server Installation and Configuration

Procedure 12-22 Recover the Necessary Filesystems (Continued)

15 Expand the /usr file system by double click and select:

/usr/omc

Expand the /usr/omc file system by double click and select

/usr/omc/logs

/usr/omc/ne_data

Expand the /usr/omc/ne_data by double click and select

/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. To begin therestore, click the Start button.

17 A Conflict Resolution window is displayed.Select No for the question:Do you want to be prompted when conflict occurs?Select Overwrite the existing file for the question:When conflict occurs, the program should? Click OK to proceed.Click OK to proceed.

18 The restore command will restore /usr/omc. A Recover Status window willbe displayed, indicating the current status of the Restore.

19 When a Recover completion time message appears in the Recover Statuswindow, the recovery of /usr/omc is complete.

20 Click Cancel to return to the nwrecover main window

21 Click File and Exit to quit nwrecover.check if the /usr/omc restore is complete.

Continued

12-30 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Recovering Informix databases

Procedure 12-22 Recover the Necessary Filesystems (Continued)

22 If you have an incremental filesystem backup to restore, continue withProcedure 12-23 to restore the latest data available in your system, aftercompleting the following set of instructions. Else, skip this step (step 22),execute step 23.Start the restore program by issuing the following commands as the userroot:

/usr/bin/nwrecover &

In the nwrecover program, select Save Set Recover from the Options menu.From the Save Set Name list, select the name of the appropriate save set.In the Instances list box, select the version of the save set based the backuphistory and the time point you want to restore to.Click Recover.In the Save Set Recover Status dialog box, click Start to begin therecovery.The recovery status appears in the Save Set Recover Status dialog box.Repeat the steps until all the restore is save set to a same time point.

23 Run init 6 to reboot the system.Now the full and incremental backup of the system are restored completely.The OMC and informix service are online (if available offline, start them).The OMC system is ready to use. Only the data taken as backup before yoursystem backup is availableYou should recover the data taken as backup after the system backup byexecuting the steps given in Procedure 12-23.

Recovering Informix databases

The procedure to recover Informix databases, as part of a disaster recovery operation, is asfollows:

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_Informixsvcadm disable svc:/application/informix/cmsvcadm disable svc:/application/informix/pm

Continued

68P02901W19-S 12-31

Oct 2009

Recovering Informix databases Chapter 12: Backup Server Installation and Configuration

Procedure 12-23 Recovering Informix databases (Continued)

2 Restore ixbar files from latest tape.

NOTEA graphical display is needed for the rest of the procedure.

Set your display and enter the following commands:Start the restore program by issuing the following commands as user root:cd /usr/informix/etc/usr/bin/nwrecover &

Select ixbar.1 and ixbar.2 for restore from the left pane in the nwrecovermain window. Once a file has been selected for restore, a blue tick appearsin the square check box.The selection of ixbar files for restoration is now complete. To begin therestore, click the Start button.A Conflict Resolution window is displayed.Select No for the question:Do you want to be prompted when conflict occurs?Select Overwrite the existing file for the question:When conflict occurs, the program should? Click OK to proceed.Click OK to proceed.

The restoration process restores these files. A Recover Status window willbe displayed, indicating the current status of the Restore.When a Recover completion time message appears in the Recover Statuswindow, the recovery of the filesystem is complete.Click Cancel to return to the nwrecover main window.Click File and Exit to quit nwrecover.

Continued

12-32 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Recovering Informix databases

Procedure 12-23 Recovering Informix databases (Continued)

3 Perform a physical restore of the dbspaces for the CM database by issuingthe following commands as user informix:cd /usr/informix/etc

(We need the latest ixbar files to restore the informix data to the latest timepoint. If no latest ixbar.1 and ixbar.2 is available in this directory, producethem by copying the latest version from the files taken as backup, followingthe given set of commands.)

cp ixbar.1.<most recent date> ixbar.1cp ixbar.2.<most recent date> ixbar.2For example:cp ixbar.1.2006109.122546 ixbar.1mib_envonbar -r -w –p

To check the status of a restore using onbar, check the/usr/informix/bar_act.log.Once the database restore is complete, the CM database will be infast-recovery mode. Bring the database to quiescent mode by issuing thefollowing command as user informix:onmode -sy

Once the database has changed to quiescent mode, bring the databaseonline by issuing the following command as user informix until the outputis similar to:

onmode -m

onmode: System is already online.

Continued

68P02901W19-S 12-33

Oct 2009

Recovering Informix databases Chapter 12: Backup Server Installation and Configuration

Procedure 12-23 Recovering Informix databases (Continued)

4 Perform a physical restore of the dbspaces for the PM database by executingthe following commands as user informix:omc_envonbar -r -w -p

To check the status of a restore using onbar, check the file/usr/informix/bar_act.log.Once the database restore has completed, the PM database will be infast recovery mode. Bring the database to quiescent mode by issuing thefollowing command as user informix:

onmode -sy

Once the database has changed to quiescent mode, bring the databaseonline by issuing the following command as user informix until the outputis similar to:

onmode -m

onmode: System is already online.

svcadm enable svc:/application/informix/cmsvcadm 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 simultaneouslyrestored completely. The informix database is ready to use.

12-34 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Recovery

Recovery■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Introduction

This section describes how to recover files and database which may become corrupted eitherthrough accidental deletion or other failure.

Recovery of a file or selection of files

Start the main recovery GUI by entering the following command as user root:nwrecover

A screen similar to the following is displayed.

Figure 12-1 Recover window

68P02901W19-S 12-35

Oct 2009

Introduction Chapter 12: Backup Server Installation and Configuration

Using the UI, navigate to the directory and/or files which are to be recovered and select them.In the example below, the files ixbar.1 and ixbar.2 have been selected for recovery.

Figure 12-2 File selection window for recovery

Press the Start button to starts the recovery. In the next screen, select Overwrite existing filewhen prompted. The recovery checks whether the required tape is online.

12-36 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Database recovery

Figure 12-3 Recover status

Database recovery

To recover either the PM or MIB (CM) databases, follow the procedure below.

Procedure 12-24 PM database recovery

1 As user root, issue the following command:omc_envsvcadm disable svc:/application/informix/pmonbar –r

2 Mount the required tape, if requested.

3 Once the recovery has completed, bring the database back online byexecuting the following commands as user root:onmode –kysvcadm enable svc:/application/informix/pm

68P02901W19-S 12-37

Oct 2009

Database recovery Chapter 12: Backup Server Installation and Configuration

Procedure 12-25 MIB (CM) database recovery

1 As user root, execute the following command:mib_envsvcadm disable svc:/application/informix/cmonbar –r

2 Mount the required tape, if requested.

3 Once the recovery is complete, bring the database back online by executingthe following commands as user root:onmode –kysvcadm enable svc:/application/informix/cm

12-38 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Additional Tools

Additional Tools■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This section details various tools that, while not part of the OMC-R backup server, may be of use.

StorEdge Enterprise Backup Server GUI

As of Solaris 10, the StorEdge Enterprise Backup Server GUI, nwadmin, is no longer available.Instead, a Java web-based interface has been introduced. Once the OMC-R Backup Server isinstalled, the StorEdge Enterprise Backup Server GUI can be configured.

Configuring Java Version

NOTEThe Java-based interface has an additional layer that allows the management ofmultiple OMC-R Backup Servers. Documentation on how to use this is not included inthis feature – reference docs.sun.com for further details.

Procedure 12-26 StorEdge Enterprise Backup Server: Java Configuration

1 Login to the Single Platform Processor as user root.

2 Remove the /.java directory, if it exists.

3 Ensure that the DISPLAY is set correctly. Open a browser window byexecuting the following command:/usr/sfw/bin/mozilla &

4 In the browser window, select Edit ààà Preferences. Highlight HelperApplications under Navigator, and select New Type.

5 Add the following information:MIME Type: application/x-java-jnlp-fileExtension: .jnlpOpen it with: /usr/j2se/jre/javaws/javaws

6 Ensure that the Open it with: is selected. Click OK.

7 Click OK to save out of Preferences.

68P02901W19-S 12-39

Oct 2009

Licensing the Sun StorEdge EBS Server using the Administration Window Chapter 12:Backup Server Installation and Configuration

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 canbe run as user root.

2 Ensure that the DISPLAY is set correctly. Open a browser window byexecuting the following command:/usr/sfw/bin/mozilla &

3 Connect to the following URL: http://<server>:10000Where <server> is the fully qualified GSM OMC-R hostname.

4 Click Start button to start the Enterprise Manager.

5 A login dialog box is displayed. The default username/password isadministrator.

6 On first login, configuration is required.

7 Accept the License agreement.Click Next onWelcome to the Configuration Window.

8 Change the administrator password if required. Otherwise, click Next toretain the default password.

9 Click Next on Set Legato License Manager Server Name.

10 Click Next on Set Database Backup Server window.

11 Add Backup Server hostname on Add Sun StorEdge EBS Servers, andclick Next.

12 The GUI is displayed. Click the Enterprise button, and select the OMC-RBackup Server hostname. Double-click the entry in the main window –another window, is displayed.

Licensing the Sun StorEdge EBS Server using the AdministrationWindow

Use the following procedure to license the Sun StorEdge EBS Server by using the administratorwindow:

Procedure 12-28 License a Sun StorEdge EBS server by using the Administrationwindow

1 From the StorEdge Enterprise Backup Server GUI Administrationwindow, click Configuration.

2 Right-click Registrations, then select New.

3 Complete the necessary attributes, and then click OK.

12-40 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Tape Management

NOTEFor further information, see Sun StorEdge Enterprise Backup Software 7.3Administration Guide (Sun Doc ID: 819-4972) from docs.sun.com.

Tape Management

While tape management is done by the StorEdge Enterprise Backup Server GUI, a very basicinterface has been designed to allow the user to have access to simple tape functionality such asmount, un-mount, label, and tape status 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. Mount

2. Unmount

3. Label

4. Status

5. Exit

3 Select appropriate option.

NOTEThe label option will prompt for a label name, andAUTOMATICALLY re-label the tape if a label already exists –query to mount the tape after labelling is also displayed.

Tape Management from the command line

Use the table below to manage tapes from the command line.

Table 12-4 Tape Management from the command line

Activity Command Example

Label a tape /usr/sbin/nsr/nsrmm –l<tape label>

/usr/sbin/nsr/nsrmm–l test.001nsrmm -l test.001

Continued

68P02901W19-S 12-41

Oct 2009

Tape Management Chapter 12: Backup Server Installation and Configuration

Table 12-4 Tape Management from the command line (Continued)

Activity Command Example

Mount a tape /usr/sbin/nsr/nsrmm –m<tape label>

/usr/sbin/nsrmm –mtest.0014mm tape test.001mounted on/dev/rmt/0mbn, writeenabled

Unmount a tape /usr/sbin/nsr/nsrmm –u<tape label>

/usr/sbin/nsr/nsrmm–u test.001Unmounted device:/dev/rmt/0mbn

Query tape status /usr/sbin/nsr/nsrmm /usr/sbin/nsr/nsrmm(nothing) mountedon 4mm tape/dev/rmt/0mbn

12-42 68P02901W19-S

Oct 2009

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.

Sample output from backup client creation

The following is a sample output from backup client creation.

Responses are highlighted.

Enter Option: 2

Adding Client

Enter Client hostname: somc85

Setting up SSH between the Backup Server and somc85.

If this is the first time, the root password for somc85 has to be supplied.

68P02901W19-S 12-43

Oct 2009

Sample output from backup client creation Chapter 12: Backup Server Installation and Configuration

Select Server Type

==================

1. GUI_SERVER

2. Informix_CM

3. Informix_PM

4. Informix_IX1

5. Informix_IX2

Enter choice : 2

Server type chosen is: Informix_CM

No resources found for query:

name: INFORMIX_CM Directives;

type: NSR directive;

No resources found for query:

name: Informix_Schedule;

type: NSR schedule;

Schedule Informix_Schedule does not exist. Creating...

No resources found for query:

name: INFORMIX_CM;

type: NSR Group;

No resources found for query:

name: somc85;

saveset: "Informix:/omc_mib1";

type: NSR client;

==================

Backup Server Menu

==================

1. Initialize Backup Server

2. Add Backup Client

3. Update Backup Client

4. Delete Backup Client

5. 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, the root password for somc85 has to be supplied.

Select Server Type

==================

12-44 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Sample output from backup client creation

1. GUI_SERVER

2. Informix_CM

3. Informix_PM

4. Informix_IX1

5. Informix_IX2

Enter choice : 3

Server type chosen is: Informix_PM

No resources found for query:

name: INFORMIX_PM Directives;

type: NSR directive;

type: NSR schedule;

name: Informix_Schedule;

comment: ;

period: Week;

action: full full full full full full full;

override: ;

No resources found for query:

name: INFORMIX_PM;

type: NSR Group;

No resources found for query:

name: somc85;

saveset: "Informix:/omc_sys1";

type: NSR client;

==================

Backup Server Menu

==================

1. Initialize Backup Server

2. Add Backup Client

3. Update Backup Client

4. Delete Backup Client

5. Quit

68P02901W19-S 12-45

Oct 2009

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, the root password for somc85 has to be supplied.

Select Server Type

==================

1. GUI_SERVER

2. Informix_CM

3. Informix_PM

4. Informix_IX1

5. Informix_IX2

Enter choice : 4

Server type chosen is: Informix_IX1

No resources found for query:

name: INFORMIX_IX1 Directives;

type: NSR directive;

type: NSR schedule;

name: Informix_Schedule;

comment: ;

period: Week;

action: full full full full full full full;

override: ;

No resources found for query:

name: INFORMIX_IX1;

type: NSR Group;

No resources found for query:

name: somc85;

saveset: /usr/informix/etc/ixbar.1;

type: NSR client;

==================

Backup Server Menu

==================

1. Initialize Backup Server

2. Add Backup Client

3. Update Backup Client

4. Delete Backup Client

5. Quit

12-46 68P02901W19-S

Oct 2009

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, the root password for somc85 has to be supplied.

Select Server Type

==================

1. GUI_SERVER

2. Informix_CM

3. Informix_PM

4. Informix_IX1

5. Informix_IX2

Enter choice : 5

Server type chosen is: Informix_IX2

No resources found for query:

name: INFORMIX_IX2 Directives;

type: NSR directive;

type: NSR schedule;

name: Informix_Schedule;

comment: ;

period: Week;

action: full full full full full full full;

override: ;

No resources found for query:

name: INFORMIX_IX2;

type: NSR Group;

No resources found for query:

name: somc85;

saveset: /usr/informix/etc/ixbar.2;

type: NSR client;

==================

Backup Server Menu

1. Initialize Backup Server

2. Add Backup Client

3. Update Backup Client

4. Delete Backup Client

5. Quit

68P02901W19-S 12-47

Oct 2009

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 UNIXfile system using the backup_splat utility. The backup is performed to a local tape drive.

CAUTIONEnsure that there is no CD/DVD in the CD/DVD drive before performing the backup.

Backing up file systems using backup_splat utility

Use the following procedure to perform a backup of the UNIX file systems on the SinglePlatform 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.

2 Insert a new labelled DAT tape into the appropriate processor tape drive, ensuringthat it is not write-protected.

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

Operating Information: OMC-R System Administration Backup and Restore using the Standard Solaris suite of utilities

Procedure 12-30 Backing up file systems using backup_splat utility (Continued)

4 Enter the following command to run the backup_splat utility../backup_splatThe following prompt is displayed:

Is there a writable DAT tape loaded in the Tape.

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

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.

DUMP: Mapping (Pass I) [regular files]

DUMP: Mapping (Pass II) [directories]

DUMP: Writing 32 Kilobyte records

DUMP: Estimated 304120 blocks (148.50MB)

DUMP: Dumping (Pass III) [directories]

DUMP: Dumping (Pass IV) [regular files]

DUMP: 304062 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.

DUMP: Mapping (Pass I) [regular files]

DUMP: Mapping (Pass II) [directories]

DUMP: Writing 32 Kilobyte records

DUMP: Estimated 12739366 blocks (6220.39MB)

DUMP: Dumping (Pass III) [directories]

DUMP: Dumping (Pass IV) [regular files]

DUMP: 18.52% done, finished in 0:44

Continued

68P02901W19-S 12-49

Oct 2009

Backup and Restore using the Standard Solaris suite of utilities Chapter 12: Backup Server Installation and Configuration

Procedure 12-30 Backing up file systems using backup_splat utility (Continued)

DUMP: 35.08% done, finished in 0:37

DUMP: 49.00% done, finished in 0:31

DUMP: 64.85% done, finished in 0:21

DUMP: 79.29% done, finished in 0:13

DUMP: 98.26% done, finished in 0:01

DUMP: 12739326 blocks (6220.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.

DUMP: Mapping (Pass I) [regular files]

DUMP: Mapping (Pass II) [directories]

DUMP: Writing 32 Kilobyte records

DUMP: Estimated 270522 blocks (132.09MB).

DUMP: Dumping (Pass III) [directories]

DUMP: Dumping (Pass IV) [regular files]

DUMP: 270462 blocks (132.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.

DUMP: Mapping (Pass I) [regular files]

DUMP: Mapping (Pass II) [directories]

DUMP: Writing 32 Kilobyte records

DUMP: Estimated 198172 blocks (96.76MB).

DUMP: Dumping (Pass III) [directories]

DUMP: Dumping (Pass IV) [regular files]

DUMP: 198142 blocks (96.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.

Continued

12-50 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Backup and Restore using the Standard Solaris suite of utilities

Procedure 12-30 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).

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: Mapping (Pass I) [regular files]

DUMP: Mapping (Pass II) [directories]

DUMP: Writing 32 Kilobyte records

DUMP: Estimated 4484 blocks (2.19MB).

DUMP: Dumping (Pass III) [directories]

DUMP: Dumping (Pass IV) [regular files]

DUMP: 4478 blocks (2.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: Mapping (Pass I) [regular files]

DUMP: Mapping (Pass II) [directories]

DUMP: Writing 32 Kilobyte records

DUMP: Estimated 1142136 blocks (557.68MB).

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

Backup and Restore using the Standard Solaris suite of utilities Chapter 12: Backup Server Installation and Configuration

Procedure 12-30 Backing up file systems using backup_splat utility (Continued)

DUMP: Dumping /dev/md/rdsk/d45 (somc85:/usr/omc/logs) to /dev/rmt/0n.

DUMP: Mapping (Pass I) [regular files]

DUMP: Mapping (Pass II) [directories]

DUMP: Writing 32 Kilobyte records

DUMP: Estimated 12296 blocks (6.00MB).

DUMP: Dumping (Pass III) [directories]

DUMP: Dumping (Pass IV) [regular files]

DUMP: 12286 blocks (6.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: Mapping (Pass I) [regular files]

DUMP: Mapping (Pass II) [directories]

DUMP: Writing 32 Kilobyte records

DUMP: Estimated 101078 blocks (49.35MB).

DUMP: Dumping (Pass III) [directories]

DUMP: Dumping (Pass IV) [regular files]

DUMP: 101054 blocks (49.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.

DUMP: Mapping (Pass I) [regular files]

DUMP: Mapping (Pass II) [directories]

DUMP: Writing 32 Kilobyte records

DUMP: Estimated 1136 blocks (568KB).

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

Operating Information: OMC-R System Administration Backup and Restore using the Standard Solaris suite of utilities

Procedure 12-30 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: 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 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 348 blocks (174KB).

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

Backup and Restore using the Standard Solaris suite of utilities Chapter 12: Backup Server Installation and Configuration

Procedure 12-30 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: Mapping (Pass I) [regular files]

DUMP: Mapping (Pass II) [directories]

DUMP: Writing 32 Kilobyte records

DUMP: Estimated 860 blocks (430KB).

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

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

7 Perform a confidence check on the tape(s) by entering the following command:dd if=/dev/rmt/0n of=/dev/null bs=1024k.

NOTERepeat this seven more times in order to check the complete backup.The confidence check command line must be entered once for eachpartition that has been backed up, plus one additional time for the tarfiles at the front of the backup tape. In this example, there are sevenfile systems that have been backed up, therefore it is necessary to enterthis command a total of eight times.

8 Make the tape write-protected. A log file is kept in/usr/omc/logs/backup_splat.<datestamp>.

12-54 68P02901W19-S

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.

• Level of backup.

• Checking and changing tape parameters.

• Backing up the PM Database.

• Overview of IDS message log files for the PM Database.

• Monitoring the active message log files for the PM Database.

• View Archived message log files for the PM Database.

• Backing up the CM Database.

• Overview of IDS message log files for the CM Database.

• Monitoring the active message log files for the CM Database.

• View Archived message log files for the CM Database.

Default DAT tape parameters

Tape parameters should be checked for the Single Platform Processor default DAT drive beforebacking up or restoring the databases. The following parameters apply to the default DAT drive.

• The tape device is /dev/rmt/0.

• The tape blocking factor/size is 1024 KB for the DAT tape.

• The tape size (in KB) is 4000000 for the DAT tape.

Level of backup

The level of backup is required when performing the archive procedure.The following levels of backup exist:

• Level 0 - monthly backup.

• Level 1 - weekly backup.

• Level 2 - daily backup.

Checking and changing tape parameters

As user Informix execute the following command:/usr/omc/sbin/set_tape_parameters.sh

The recommended tape sizes for Informix are:

68P02901W19-S 12-55

Oct 2009

Backing up the PM and CM Databases Chapter 12: Backup Server Installation and Configuration

• DDS3 — 20,000,000

• DDS4 — 38,000,000

• DAT72 — 70,000,000

The utility /usr/omc/sbin/set_tape_parameters.sh will only set the tape parameters for thedefault DDS3 device. If you have DDS4 or DAT72, then use the following procedure to changethe tape parameters:

Procedure 12-31 Checking and changing tape parameters

1 Login to the System Processor as user informix.

2 Set the following environment variable:setenv TERM vt100

3 Set the correct environment for the database archive. For CM database,enter the alias mib_env. For the PM database, enter the alias omc_env.

4 Check the tape parameters by using the onmonitor utility. The followingexample shows an sample output for a DDS4 tape:

Dynamic Server: Status Parameters Dbspaces Mode Force–Ckpt ...

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 barto toggle between options:

Informix–Online: ... Archive Logical–Logs Exit

Change tape device or tape characteristics.

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

Press Interrupt to return to the Archive menu.

Press F2 or CTRL-F for field level help.

MODIFYING TAPE PARAMETERS

Tape Device [/dev/rmt/0]

Continued

12-56 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Backing up the PM and CM Databases

Procedure 12-31 Checking and changing tape parameters (Continued)

Block Size [ 1024] Kbytes Tape Size [ 38000000]Kbytes

Log Tape Device [/dev/null]

Block Size [64] Kbytes Tape Size [ 2000000]Kbytes

For the default DAT drive, ensure the tape device is set to /dev/rmt/0, theblock size set to 1024 and the tape size set to 38000000. Press ESC tocommit any changes, or CTRL-C to quit without saving.

7 Select the Exit option to exit the Archive menu. Select the Exit option againto exit the onmonitor utility.

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 toinformix:su — informix

2 Set the following environment variable:setenv TERM vt100

3 Set the correct environment for the database archive.For the PM database, enter the alias:omc_env

4 As user Informix execute the following command:/usr/omc/sbin/set_tape_parameters.sh

5 Start the archive by entering the following command:ontape —s —L <archive_level>Where <archive_level> is the level of archive. For example, to start a level 0archive enter ontape –s –L 0.

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 interruptkey. This is usually CTRL-c or the DELETE key. If the archive is interrupted,then the archive copy is corrupted and a new archive will have to be initiatedto perform a backup.Press RETURN.

Continued

68P02901W19-S 12-57

Oct 2009

Backing up the PM and CM Databases Chapter 12: Backup Server Installation and Configuration

Procedure 12-32 Back up the PM database to the Single Platform Processor(Continued)

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.

This tape contains the following the following logical logs:

3

Program over

7 If the archive requires more than one tape, the user is prompted when achange of tape is needed.The tapes must be labelled 1, 2, 3, and so on, to indicate the sequence inwhich the tapes must be mounted if used to restore the database.

8 If an error occurs during the archive, an error message is displayed followedby the message:

Please mount tape and press Return to continue

The archive procedure can be interrupted to fix any problems beforepressing the RETURN key.

9 When the archive is complete, a message is displayed indicating which tapesare required to restore the database to its present state. The messagealso indicates the logical log at which to start to restore the system afterthe backup tapes have been mounted. The logical log information can beignored as logical logs are not currently used.

10 Perform a confidence check on the tape(s) by entering the followingcommand:dd if=/dev/rmt/0 of=/dev/null bs=1024k

11 If the confidence check performed in step 10 is successful, write protect,label, and store the tape(s). If an error is returned, replace the faulty tapeand repeat the backup procedure from step 5.

Overview of IDS message log files for the PM Database

Each Informix Dynamic Server requires a message log file. As these files increase continuouslyin size, they are not suitable for archiving with the other log files therefore a cron job is requiredto move the message log files to a time-stamped file, which can then be archived and removedfrom the file system. The cron job is /usr/omc/sbin/roll_online.log. The message log files areowned by informix and held on the Single Platform Processor as follows:

• /usr/informix/online.log_OMC - active message log file for PM database.

• /usr/informix/online.log_OMC.<ddmmyyyy> - archived message log file for PM database.

12-58 68P02901W19-S

Oct 2009

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.

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 toinformix:su - 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 theonstat utility or the tail command:Using onstat utility:onstat -mA -r option can be included to allow the process sleep time to be specified asa parameter (onstat -m -r <sleep_time>). The <sleep_time> specifiesthe number of seconds the process will be put to sleep before recheckingthe IDS message log file.Using the unix tail command, execute:tail -f $INFORMIXDIR/online.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 Monitoring timestamped IDS message log files

1 Login to the Single Platform Processor using login id root and switch user toinformix:su - informix

2 Display the appropriate timestamped message log file.For PM database timestamped message log file enter:view /usr/informix/online.log_OMC.<ddmmyyyy>Where <ddmmyyyy> is the day, month and year the log file was created.

68P02901W19-S 12-59

Oct 2009

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 ProcessorDAT 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 toinformix:su — informix

2 Set the following environment variable:setenv TERM vt100

3 Set the correct environment for the database archive.mib_env

4 As user Informix execute the following command:/usr/omc/sbin/set_tape_parameters.sh

5 Start the archive by entering the following command:ontape —s —L <archive_level>Where <archive_level> is the level of archive. For example, to start a level 0archive enter ontape -s –L 0.

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 interruptkey. This is usually CTRL-c or the DELETE key. If the archive is interrupted,then the archive copy is corrupted.Press RETURN.

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.

This tape contains the following the following logical logs:

3

Program over

Continued

12-60 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Backing up the PM and CM Databases

Procedure 12-35 Back up the CM database to the Single Platform Processor(Continued)

7 If the archive requires more than one tape, the user is prompted when achange of tape is needed.The tapes must be labeled 1, 2, 3, and so on, to indicate the sequence inwhich the tapes must be mounted if used to restore the database.

8 If an error occurs during the archive, an error message is displayed followedby the message:Please mount tape and press Return to continueThe archive procedure can be interrupted to fix any problems beforepressing the RETURN key.

9 When the archive is complete, a message is displayed indicating which tapesare required to restore the database to its present state. The messagealso indicates the logical log at which to start to restore the system afterthe backup tapes have been mounted. The logical log information can beignored as logical logs are not currently used.

10 Perform a confidence check on the tape(s) by entering the followingcommand:dd if=/dev/rmt/0 of=/dev/null bs=1024k

11 If the confidence check performed in step 10 is successful, write protect,label, and store the tape(s). If an error is returned, replace the faulty tapeand repeat the backup procedure from step 5.

Overview of IDS message log files for the CM Database

Each Informix Dynamic Server requires a message log file. As these files increase continuouslyin size, they are not suitable for archiving with the other log files therefore a cron job is requiredto move the message log files to a time-stamped file, which can then be archived and removedfrom the file system. The cron job is /usr/omc/sbin/roll_online.log. The message log files areowned by informix and held on the Single Platform Processor as follows:

• /usr/informix/online.log_MIB – active message log file for CM database.

• /usr/informix/online.log_MIB.<ddmmyyyy> – archived message log file for CM database.

68P02901W19-S 12-61

Oct 2009

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.

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 userto 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 theonstat utility or the tail command:Using onstat utility:onstat —mA –r option can be included to allow the process sleep time to be specified asa parameter (onstat —m -r <sleep_time>). The <sleep_time> specifiesthe number of seconds the process will be put to sleep before recheckingthe IDS message log file.Using the unix tail command, execute:tail —f $INFORMIXDIR/online.log_MIB

View Archived message log files for the CM Database

Use the following procedure to monitor timestamped IDS message log files:

Procedure 12-37 Monitoring the timestamped IDS message log files.

1 Log in to the Single Platform Processor using login ID root and switch userto informix:su — informix

2 Display the appropriate timestamped message log file.For PM database timestamped message log file enter:view/usr/informix/online.log_MIB.<ddmmyyyy>Where <ddmmyyyy> is the day, month and year the log file was created.

12-62 68P02901W19-S

Oct 2009

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.This utility enables recovery of all Single Platform Processor file systems that have been storedon a backup tape using the backup_splat utility. The data can be restored on a brand new set ofdisks or on disks that have become corrupt.

CAUTIONThe procedure destroys any data on the disks and overwrites the disks with datafrom the backup tape.

The task of restoring file systems to the Single Platform Processor involves the followingprocedures:

• Shutting down the Single Platform Processor.

• JumpStarting the Single Platform Processor.

• Restoring the databases.

Before commencing the restore procedure, ensure that a copy of the most recent set of SinglePlatform Processor complete file system level 0 backup tapes (created using the backup_splatutility) is available.

68P02901W19-S 12-63

Oct 2009

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.

2 Enter the following commands to inform all users that a complete systemrestore is to be performed:wallSystem 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.

JumpStarting the Netra Single Platform Processor

For the clean install of the Netra Single Platform, refer to the procedure given in Chapter2 of the Installation and Conguration: OMC-R Clean Install (68P02901W47). Follow all theinstructions provided in the procedure excluding the following sections:

• The /etc/dfs/dfstab file.

• Modifying the /etc/hosts file.

• Creating the /etc/hosts.equiv file.

• Creating the /.rhosts file.

Complete the following procedure to restore the Netra Single Platform Processor:

Procedure 12-39 JumpStarting the Netra Single Platform Processor

1 Insert the Motorola JumpStart DVD in the DVD-ROM drive of the SystemProcessor.

2 Insert the latest Full System backup tape in the DAT drive of the SystemProcessor.

3 Enter the following command at the ok prompt and press RETURN:boot cdrom –- restore

Follow the on-screen prompts.

Continued

12-64 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Restoring Single Platform Processor file systems

Procedure 12-39 JumpStarting the Netra Single Platform Processor (Continued)

4 Once the system has rebooted, execute the following command as user root:prtconf | grep pci1214

Screen output similar to the following is displayed to notify that the HSIPdrivers are attached:

pci1214,334, instance #0

pci1214,334, instance #1

If the HSIP drivers are not attached, then the following message is displayed:

pci1214,334, instance #0 (driver not attached)

pci1214,334, instance #1 (driver not attached)

If the HSIP drivers are not attached, execute the following commands to attachthe HSIP drivers as user root:rem_drv HSIPadd_drv HSIP

5 The Netra Single Platform Processor then restores the full system backupfrom tape and upon completion returns with the console login. At this point,the system needs to be rebooted to restart services by running the followingcommand as user root:/usr/sbin/shutdown -i6 -g0 –y

6 Once the system has rebooted, compare the two files /etc/inet/hosts and/etc/inet/hosts.postmerge, if there are differences between the two files, needto manually update /etc/inet/hosts by executing the following command: cd/etc/inet/cp ./hosts.postmerge ./hostsrm ./ipnodesln –s ./hosts ./ipnodes

7 If NIS is used as the naming service, execute the following as root:

ypinit -m

In order for NIS to operate successfully, we have to construct alist of the NIS servers. Continue to add the names for YP serversin the order of preference, one per line. When you are done withthe list, type a <control D> or a return on a line by itself.next host to add:mercia

next host to add:

The current list of yp servers looks like this:

mercia

Is this correct? [y/n: ] y

Continued

68P02901W19-S 12-65

Oct 2009

Restoring Single Platform Processor file systems Chapter 12: Backup Server Installation and Configuration

Procedure 12-39 JumpStarting the Netra Single Platform Processor (Continued)

Installing the YP database will require that you answer a few questions.Questions will all be asked at the beginning of the procedure.

Do you want this procedure to quit on non-fatal errors? [y/n: n]

OK, please remember to go back and redo manually whatever fails.If you don't, some part of the system (perhaps the yp itself) won'twork.

The yp domain directory is /var/yp/omcadmin

Can we destroy the existing /var/yp/omcadmin and itscontents? [y/n: n] y

There will be no further questions. The remainder of theprocedure should take 5 to 10 minutes.

Building /var/yp/omcadmin/ypservers...

Running /var/yp /Makefile...

updated passwd

updated group

updated hosts

updated ipnodes

updated ethers

updated networks

updated rpc

updated services

updated protocols

updated netgroup

updated bootparams

/var/yp/omcadmin/mail.aliases: 12 aliases, longest 10 bytes, 138

bytes total

Continued

12-66 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Restoring Single Platform Processor file systems

Procedure 12-39 JumpStarting the Netra Single Platform Processor (Continued)

/usr/lib/netsvc/yp/mkalias /var/yp/‘domainname‘/mail.aliases/var/yp/domainname/mail.byaddr;

updated aliases

updated publickey

updated netid

/usr/sbin/makedbm /etc/netmasks /var/yp/‘domainname‘/netmasks.byaddr;

updated netmasks

updated timezone

updated auto.master

updated auto.home

updated ageing

updated auth_attr

updated exec_attr

updated prof_attr

updated user_attr

updated audit_user

mercia has been set up as a yp master server without any errors.

If there are running slave yp servers, run yppush now for any data bases whichhave been changed. If there are no running slaves, run ypinit on those hostswhich are to be slave servers.

8 The system needs to be rebooted to restart services by executing the followingcommand as user root:/usr/sbin/shutdown -i6 -g0 -y

9 If you need to restore the databases too, please execute the following commandas user root:svcadm clear svc:/system/basicreg:defaultsvcadm disable omc

10 After logging in, please refer to section “Restoring databases on theSingle Platform Processor” on page 12-58 in documentation “W19Operating_Information_OMC-R_System_Administration”

JumpStarting the SunFire Single Platform Processor

For the clean install of the SunFire Single Platform, refer to the procedure given in Chapter2 of the Installation and Conguration: OMC-R Clean Install (68P02901W47). Follow all theinstructions provided in the procedure excluding the following sections:

• The /etc/dfs/dfstab file.

• Modifying the /etc/hosts file.

• Creating the /etc/hosts.equiv file.

• Creating the /.rhosts file.

Procedure 12-40 to restore the Sunfire 4800/4900.

68P02901W19-S 12-67

Oct 2009

Restoring Single Platform Processor file systems Chapter 12: Backup Server Installation and Configuration

Procedure 12-40 JumpStarting the SunFire Single Platform Processor

1 Insert the Motorola JumpStart DVD in the DVD-ROM drive of the SinglePlatform Processor.

2 Insert the latest Full System backup tape in the DAT drive of the SinglePlatform Processor.

3 Enter the following command at the ok prompt, and press RETURN. Ifauto-boot is set to false, the server does not start up automatically afterpower on or reset.setenv auto-boot? False

Screen output similar to the following is displayed:

auto-boot? = false

4 Enter the following command to reboot the server, and press RETURN.reset-all

Screen output similar to the following is displayed:

Resetting ...

Copying IO prom to Cpu dram

{/N0/SB2/P2}

@(#) lpost 5.13.2 2005/06/21 12:33

{/N0/SB2/P2}

Copyright 2001 Sun Microsystems, Inc. All rights reserved.

..............................{/N0/SB2/P2}

Running PCI IO Controller

Basic Tests

{/N0/SB2/P2}

Jumping to memory 00000000.00000020 [00000010]

{/N0/SB2/P2}

System PCI IO post code running from memory

{/N0/SB2/P2} @(#)

lpost 5.13.2 2005/06/21 12:33

{/N0/SB2/P2} Copyright 2001 Sun

Microsystems, Inc. All rights reserved.

Continued

12-68 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Restoring Single Platform Processor file systems

Procedure 12-40 JumpStarting the SunFire Single Platform Processor (Continued)

5 Enter the following command to identify all the devices attached to theSCSI bus, and press RETURN.probe-scsi-all

Screen output similar to the following is displayed:

/ssm@0,0/pci@19,700000/pci@2/SUNW,isptwo@4/sd@6,0:f

Target

2

Unit 0 Processor SUN D240 2

Target 4

Unit

0 Disk SEAGATE ST34371W SUN4.2G7462

Target 6

Unit

0 Removable Read Only device TOSHIBA DVD-ROM SD-M14011009

6 Type nvalias cdrom at the OK> prompt.Select the device path associated with the DVD-ROM drive (this is the firstline of the previous screen output). Paste this device path after nvaliascdrom.If this string contains "scsi", append /disk@6,0:f to the string.If it contains "isptwo", append /sd@6,0:f to the string.The 6,0 in this example refers to Target 6 and unit 0 where the DVD-ROMresides on the SCSI bus.For example:nvalias cdrom/ssm@0,0/pci@19,700000/pci@2/SUNW,isptwo@4/sd@6,0:fornvalias cdrom /ssm@0,0/pci@19,700000/pci@2/scsi@2/disk@6,0:fAt the OK> prompt, execute the following command:boot cdrom -- restore

The system is jumpstarted without any prompts and the file systems areautomatically restored.

7 Once the system has rebooted, execute the following command as user root:prtconf | grep pci1214

Screen output similar to the following is displayed to notify that the HSIPdrivers are attached:

pci1214,334, instance #0

pci1214,334, instance #1

If the HSIP drivers are not attached, the following message is displayed:

pci1214,334, instance #0 (driver not attached)

pci1214,334, instance #1 (driver not attached)

Continued

68P02901W19-S 12-69

Oct 2009

Restoring Single Platform Processor file systems Chapter 12: Backup Server Installation and Configuration

Procedure 12-40 JumpStarting the SunFire Single Platform Processor (Continued)

If the HSIP drivers are not attached, execute the following commands toattach the HSIP drivers as user root:rem_drv HSIPadd_drv HSIP

8 The Sunfire Single Platform Processor then restores the full system backupfrom tape and upon completion returns with the console login. At thispoint, the system needs to be rebooted to restart services by executingthe following command as user root:/usr/sbin/shutdown -i6 -g0 –y

9 Once the system has rebooted, compare the two files /etc/inet/hosts and/etc/inet/hosts.postmergeIf there are differences between the two files, need to manually update/etc/inet/hosts by executing the following command:cd /etc/inet/cp ./hosts.postmerge ./hostsrm ./ipnodesln –s ./hosts ./ipnodes

10 If NIS is used as the naming service, execute the following as root:ypinit -mIn order for NIS to operate successfully, we have to constructa list of the NIS servers. Continue to add the names for YPservers in the order of preference, one per line. When you aredone with the list, type a <control D> or a return on a line byitself.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 afew questions. Questions will be asked at thebeginning of the procedure.

Do you want this procedure to quit on non-fatalerrors? [y/n: n]

OK, please remember to go back and redo manually whatever fails.If you don't, some part of the system (perhaps the yp itself) won'twork.

The yp domain directory is /var/yp/omcadmin

Can we destroy the existing /var/yp/omcadmin and itscontents? [y/n: n] y

Continued

12-70 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Restoring Single Platform Processor file systems

Procedure 12-40 JumpStarting the SunFire Single Platform Processor (Continued)

There will be no further questions. The remainder of theprocedure should take 5 to 10 minutes.

Building /var/yp/omcadmin/ypservers...

Running /var/yp /Makefile...

updated passwd

updated group

updated hosts

updated ipnodes

updated ethers

updated networks

updated rpc

updated services

updated protocols

updated netgroup

updated bootparams

/var/yp/omcadmin/mail.aliases: 12 aliases, longest 10 bytes, 138

bytes total/usr/lib/netsvc/yp/mkalias /var/yp/‘domainname‘/mail.aliases/var/yp/domainname/mail.byaddr;

updated aliases

updated publickey

updated netid

/usr/sbin/makedbm /etc/netmasks /var/yp/‘domainname‘/netmasks.byaddr;

updated netmasks

updated timezone

updated auto.master

updated auto.home

updated ageing.

updated auth_attr

updated exec_attr

updated prof_attr

updated user_attr

updated audit_user

mercia has been set up as a yp master server without any errors.

If there are running slave yp servers, run yppush now for any data baseswhich have been changed. If there are no running slaves, run ypinit onthose hosts which are to be slave servers.

Continued

68P02901W19-S 12-71

Oct 2009

Restoring Single Platform Processor file systems Chapter 12: Backup Server Installation and Configuration

Procedure 12-40 JumpStarting the SunFire Single Platform Processor (Continued)

11 The system needs to be rebooted to restart services by executing thefollowing command as user root:/usr/sbin/shutdown -i6 -g0 -y

12 If you need to restore the databases too, please execute the followingcommand as user root:svcadm clear svc:/system/basicreg:defaultsvcadm disable omc

13 After logging in, please refer to section “Restoring databases on theSingle Platform Processor” on page 12-59 in documentation “W19Operating_Information_OMC-R_System_Administration”

JumpStarting the SunEnterprise M4000/M5000 Single Platform Processor

{34618}

For the Clean Install of the SunFire Single Platform, refer to the procedure given in Chapter 2 ofthe Installation and Conguration: OMC-R Clean Install (68P02901W47).Follow the proceduresexcluding the following sections:

• The /etc/dfs/dfstab file.

• Modifying the /etc/hosts file.

• Creating the /etc/hosts.equiv file.

• Creating the /.rhosts.equiv file.

Follow Procedure 12-41 to JumpStart the SunSparc Enterprise M4000/M5000.

Procedure 12-41 JumpStarting the SunSparc Enterprise M4000/M5000 SinglePlatform Processor

1 Insert the Motorola JumpStart DVD in the DVD-ROM drive of the Single PlatformProcessor.

2 Insert the latest Full System backup tape in the DAT drive of the Single PlatformProcessor.

3 Enter the following command at the OK prompt, and press RETURN.If auto-boot is set to false, the server does not start up automatically after poweron or reset.setenv auto-boot? false

Screen output similar to the following is displayed:

auto-boot? = false

Continued

12-72 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Restoring Single Platform Processor file systems

Procedure 12-41 JumpStarting the SunSparc Enterprise M4000/M5000 SinglePlatform Processor (Continued)

4 Enter the following command to reboot the server, and press RETURN.reset-all

Screen output similar to the following is displayed:

Resetting...

POST Sequence 01 CPU Check

LSB#02 (XSB#01-0): POST 2.3.0 (2008/04/18 09:15)

POST Sequence 02 Banner

LSB#00 (XSB#00-0): POST 2.3.0 (2008/04/18 09:15

POST Sequence 03 Fatal Check

POST Sequence 04 CPU Register

POST Sequence 05 STICK

POST Sequence 06 MMU

POST Sequence 07 Memory Initialize

POST Sequence 08 Memory

POST Sequence 09 Raw UE In Cache

POST Sequence 0A Floating Point Unit

POST Sequence 0B SC

POST Sequence 0C Cacheable Instruction

POST Sequence 0D Softint

POST Sequence 0E CPU Cross Call

POST Sequence 0F CMU-CH

POST Sequence 10 PCI-CH

POST Sequence 11 Master Device

POST Sequence 12 DSCP

POST Sequence 13 SC Check Before STICK Diag

POST Sequence 14 STICK Stop

POST Sequence 15 STICK Start

POST Sequence 16 Error CPU Check

POST Sequence 17 System Configuration

POST Sequence 18 System Status Check

POST Sequence 19 System Status Check After Sync

POST Sequence 1A OpenBoot Start...

POST Sequence Complete.

5dc04

Continued

68P02901W19-S 12-73

Oct 2009

Restoring Single Platform Processor file systems Chapter 12: Backup Server Installation and Configuration

Procedure 12-41 JumpStarting the SunSparc Enterprise M4000/M5000 SinglePlatform Processor (Continued)

Sun SPARC Enterprise M5000 Server, using Domainconsole

Copyright 2008 Sun Microsystems, Inc. Allrights reserved.

5 At the OK> prompt, execute the following command:boot cdrom -- restoreThe system jump starts without any prompts and automatically restores the filesystems.

6 Once the system has rebooted, 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,3350, instance #0

pciex1214,3350, instance #1

• If the HSIP drivers are not attached:

pciex1214,3350, instance #0 (driver not attached)

pciex1214,3350, instance #1 (driver not attached)

Execute the following commands to attach the HSIP drivers as user root:rem_drv HSIPadd_drv HSIP

7 The SunSparc Single Platform Processor then restores the full system backupfrom the tape.On completion the SunSparc returns with the console login.Reboot the system to restart services by executing the following command asuser root:/usr/sbin/shutdown -i6 -g0 –y

Continued

12-74 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Restoring Single Platform Processor file systems

Procedure 12-41 JumpStarting the SunSparc Enterprise M4000/M5000 SinglePlatform Processor (Continued)

8 If the NIS is used as the naming service, execute the following as root:ypinit -m

To operate the NIS successfully, construct a list of the NIS servers.Add one YP server name per line in the order of preference.On completion, type <control D> or Return on a line by itself.Next host to add:

Next host to add:mercia

Next host to add:The current list of yp servers looks like this:mercia

Is this correct? [y/n: ] y

Installing the YP database requires answering a few questions.Questions are asked at the beginning of the procedure.

Continued

68P02901W19-S 12-75

Oct 2009

Restoring Single Platform Processor file systems Chapter 12: Backup Server Installation and Configuration

Procedure 12-41 JumpStarting the SunSparc Enterprise M4000/M5000 SinglePlatform Processor (Continued)

Do you want this procedure to quiton non-fatal errors? [y/n]: n

NOTEManually redo the failed steps to prevent system failure or YPdatabase failure.

The YP domain directory is /var/yp/omcadmin.

Can we destroy the existing /var/yp/omcadmin and itscontents? [y/n: n] y

After the last query, the procedure takes 5 minutes to 10 minutes to complete.

Building /var/yp/omcadmin/ypservers...Running /var/yp /Makefile...

updated passwd

updated group

updated hosts

updated ipnodes

updated ethers

updated networks

updated rpc

updated services

updated protocols

updated netgroup

updated bootparams

/var/yp/omcadmin/mail.aliases: 12 aliases, longest 10 bytes,138bytes total

/usr/lib/netsvc/yp/mkalias /var/yp/‘domainname‘/mail.aliases

/var/yp/domainname/mail.byaddr;

updated aliases

updated publickey

updated netid

/usr/sbin/makedbm /etc/netmasks /var/yp/‘domainname‘/netmasks.byaddr;

updated netmasks

updated timezone

updated auto.master

updated auto.home

updated ageing

Continued

12-76 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Restoring databases on the Single Platform Processor

Procedure 12-41 JumpStarting the SunSparc Enterprise M4000/M5000 SinglePlatform 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.

If there are running slave YP servers, to recover from the database changes,execute the following command:yppush

If there are no running slaves, on hosts to be slave servers, execute the followingcommand:ypinit

9 Execute the following command as user root:svcadm clear svc:/system/basicreg:defaultsvcadm disable omc

10 After logging in, proceed to Restoring databases on the Single PlatformProcessor on page 12-77.

Restoring databases on the Single Platform Processor

• Overview of restoring databases on page 12-77.

• Preparing to restore the databases on page 12-78.

• Taking databases offline and re-initializing INFORMIX on page 12-78.

• Restoring the CM database on page 12-78.

• Restoring the PM database on page 12-82.

• Final Configuration Tasks on page 12-86.

Overview of restoring databases

A restoration of the INFORMIX databases must now be performed.The restore option of the ontape utility is used to restore the complete database structure.

68P02901W19-S 12-77

Oct 2009

Restoring databases on the Single Platform Processor Chapter 12: Backup Server Installation and Configuration

Preparing to restore the databases

Before starting the restore process, locate the following tapes:

• The last monthly (level 0) backup.

• The last weekly (level 1) backup, if it occurred after the last monthly backup.

• The last daily (level 2) backup, if it occurred after the last weekly backup.

The databases are restored using the backup tapes in the order they were taken.

Taking databases offline and re-initializing INFORMIX

Before performing the restore from tape, both the PM and CM databases must be taken offlineand INFORMIX must be re-initialized. 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.

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

Operating Information: OMC-R System Administration Restoring databases on the Single Platform Processor

Procedure 12-43 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.sh

6 To restore from tape, enter the following command:ontape –r

The system displays the following message:

Please mount tape 1 on /dev/rmt/0 and press return to continue

7 Load the tape marked (CM database) Level 0 Backup into the SinglePlatform Processor tape drive.If more than one tape was used to back up the CM database, the systemprompts for further tapes to be entered in sequence.Press the RETURN key to continue.

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

Restoring databases on the Single Platform Processor Chapter 12: Backup Server Installation and Configuration

Procedure 12-43 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_db_logs

3

3 78903 192000 7627 PO- /dev/mib_db_logs

4

4 921601 102399 102346 PO- /dev/mib_db

5

5 2 767998 767945 PO- /dev/mib_db1

Continue restore? (y/n)

Enter y to continue the restore.

Continued

12-80 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Restoring databases on the Single Platform Processor

Procedure 12-43 Restore the CM database (Continued)

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 or 2 archive (y/n)

Enter n.

11 For a level 0 archive, or y for a level 1 or 2 archive. The following text isdisplayed:

Do you want to restore log tapes? (y/n)

Enter n.

12 The following text is displayed:

Program over.

13 In a separate login session, check the contents of online.log_MIB as follows:tail -f /usr/informix/online.log_MIB

Output similar to the following example is displayed:

10:28:10 Checkpoint Completed: duration was 0 seconds.

Checkpoint loguniq 13, logpos 0x1309018

10:28:11 Physical

Restore of rootdbs, physdbs, logsdbs, mib_db_sp1 Completed.

10:28:11

Checkpoint Completed: duration was 0 seconds

10:28:11 Checkpoint

loguniq 13, logpos 0x1309018

10:30:10 Physical Recovery Started.

10:30:10

Physical Recovery Complete: 0 Pages Restored

10:30:10 Logical

Recovery Started.

10:30:10 10 recovery worker threads will be started.

10:30:13 Logical Recovery Complete.

0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks

10:30:14

Bringing system to Quiescent Mode with no Logical Restore.

10:30:15

Quiescent Mode

Press Ctrl-c to exit out of the tail -f command at any time.

Continued

68P02901W19-S 12-81

Oct 2009

Restoring databases on the Single Platform Processor Chapter 12: Backup Server Installation and Configuration

Procedure 12-43 Restore the CM database (Continued)

14 Remove the backup tape from the tape drive.

15 Once Quiescent Mode is displayed in the log, enter the following commandsas user informix to bring the CM database back online:mib_envonmode -msvcadm 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 thefollowing:/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, execute the following command:/usr/omc/sbin/set_tape_parameters.sh

6 To restore from tape, enter the following command:ontape –rThe 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 SinglePlatform Processor tape drive.If more than one tape was used to back up the PM database, the systemprompts for further tapes to be entered in sequence.Press the RETURN key to continue.

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

Continued

12-82 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Restoring databases on the Single Platform Processor

Procedure 12-44 Restore the PM database (Continued)

Archive date: Thu Jan 17 12:24:13 2006

User id: informix

Terminal id: /dev/pts/1

Archive level: 0

Tape device: /dev/rmt/0

Tape blocksize (in k): 64

Tape size (in k): 4000000

Tape number in series: 1

Spaces to restore:

1 [rootdbs]

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 Chapter 12: Backup Server Installation and Configuration

Procedure 12-44 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

3 3 127003 396800 12747

PO- /dev/omc_db_logs

4 4 2 1024098

241186 PO- /dev/omc_db1

5 5 2 1024098

215855 PO- /dev/omc_db2

6 6 2 1023998

650740 PO- /dev/omc_db3

7 7 2 1023998

183648 PO- /dev/omc_db4

8 8 2 1023998

773840 PO- /dev/omc_db5

9 9 2 1023998

487565 PO- /dev/omc_db6

10 10 2 1023998

1023945 PO- /dev/omc_db_temp

Continue restore? (y/n)

Enter y to continue the restore.

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.

Continued

12-84 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Restoring databases on the Single Platform Processor

Procedure 12-44 Restore the PM database (Continued)

11 For a level 0 archive, or y for a level 1 or 2 archive. The following text isdisplayed:

Do you want to restore log tapes? (y/n)

Enter n.The following text is displayed:

Program over

12 In a separate login session, check the contents of the online.log_OMC asfollows:tail -f /usr/informix/online.log_OMC

Output similar to the following example is displayed:

10:36:47 Checkpoint Completed: duration was 0 seconds.

10:36:47

Checkpoint loguniq 13, logpos 0x469018

10:39:14 Physical

Recovery Started.

10:39:14 Physical Recovery Complete: 0 Pages

Restored.

10:39:14 Logical Recovery Started.

10:39:14

10 recovery worker threads will be started.

10:39:18 Logical

Recovery Complete.

0 Committed, 0 Rolled Back, 0

Open, 0 Bad Locks

10:39:19 Bringing system to Quiescent Mode

with no Logical Restore.

10:39:20 Quiescent Mode

Press Ctrl-c to exit out of the tail -f command at any time.

13 Remove the backup tape from the tape drive.

14 Once Quiescent Mode is displayed in the log, enter the following commandsas user informix to bring the PM database back online:omc_envonmode -msvcadm enable informix/pm

68P02901W19-S 12-85

Oct 2009

Restoring GUI Server file systems using ufsrestore utility Chapter 12: Backup Server Installation and Configuration

Final Configuration Tasks

When the databases are fully restored, perform the following commands:

Procedure 12-45 Final Configuration Tasks

1 Log in as user root.

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.<yy><mm><dd>

Where <yy>refers to the current year,<mm>to the current month, and<dd> to the current day in this month.

4 As user omcadmin, execute the following command:svcadm enable omc

At this stage the Single Platform Processor has been restored.

Restoring GUI Server file systems using ufsrestore utility

• Overview to restoring GUI Server file systems using ufsrestore utility on page 12-86.

• JumpStarting the GUI Server Processor on page 12-87.

• Overview of restoring the GUI Server file system on page 12-93.

• Restoring root (/) file system on page 12-94.

• Restoring /usr/omc file system on page 12-96.

• Restoring /omcgen file system on page 12-96.

• Rebooting the GUI Server on page 12-97.

Overview to restoring GUI Server file systems using ufsrestore utility

The data that has been stored on backup tapes can be restored on a brand new set of disksfor disks that have become corrupt.

CAUTIONThe procedure destroys any data on the disks and overwrites the disks with datafrom the backup tape.

Before commencing the restore procedure, make sure that a copy of the most recent setof complete file system level 0 backup tapes created using backup_MMI, is available for theprocessor being restored.

12-86 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Restoring GUI Server file systems using ufsrestore utility

This procedure uses, as an example, a Sunblade 150 GUI Server, with the following file systems://omcgen/usr/omc

JumpStarting the GUI Server Processor

Procedure 12-46 Jumpstart a GUI Server

1 Insert the GSR9 DVD in the DVD-ROM drive of the GUI Server.

2 From the ok prompt, enter the following command to perform a hands-freeinstallation of Solaris 10 and all StorEdge Enterprise products on the GUIServer:boot cdrom

Screen output similar to the following is displayed:

The following is sample output that can be expected during the install.

3 When the boot command is entered, screen output similar to the followingis displayed:

Motorola GSM OMC-R GUI Server Installation

==========================================

Now you will be prompted to enter information to customise

your GSM OMC-R GUI Server. It is essential that you provide

correct answers to all of the following questions.

An incorrect answer may very likely cause problems. Refer to

your install documentation if you are not sure which values to supply for

any of the questions

The default response (where one is provided) is in square brackets ([]).

If a default response exists, you can accept it by pressing the

ENTER key.

After the install questions have completed, you will have a

chance to approve or change your settings.

Once the settings have been approved, the system will be wiped and

installed from scratch.

Press -=ENTER=- to continue

Press Enter to continue.

Continued

68P02901W19-S 12-87

Oct 2009

Restoring GUI Server file systems using ufsrestore utility Chapter 12: Backup Server Installation and Configuration

Procedure 12-46 Jumpstart a GUI Server (Continued)

4 A prompt is displayed requiring the hostname to be entered.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.

NOTEA host name must be of at least two characters. It can containletters, digits and minus signs (-). Letters must be lower case.Illegal characters are: !ӣ$%^&*(){}~@?>:<|.[]_.

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. This should be set

to the IP address that your GSM OMC-R GUI Server will be

known as on your local LAN.

Enter the GSM OMC-R GUI Server’s IP address:

Enter the IP address.

6 A prompt is displayed requiring the Netmask address to be entered.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.

This should be set to the netmask that your GSM OMC-R GUI Server will

on your local LAN.

Example: 255.255.255.0

Enter the GSM OMC-R GUI Server’s netmask:

Enter the Netmask address.

Continued

12-88 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Restoring GUI Server file systems using ufsrestore utility

Procedure 12-46 Jumpstart a GUI Server (Continued)

7 A prompt is displayed that gives an option to configure a Default Router.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.

Contact your system administrator for help

Do you want to configure a default router? (y/n) [y]: y

If a default router is to be configured, press Enter and the following promptis displayed:

Enter the default router’s IP address:

Enter the default router’s IP address.If a default router is not required, type n and then press Enter. Theinstallation then proceeds to configure DNS.

8 A prompt is displayed that gives an option to configure DNS.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.

Contact your system administrator for help.

Do you want to configure DNS? (y/n) [n]: n

If DNS is not required, press Enter. The installation will then continue toconfigure a timeserver.

9 If DNS is to be configured, enter y.The user is prompted to enter the DNS Domain name and DNS server IPaddresses. After each prompt, 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, it is necessary to type in the Domain name andto supply a primary DNS IP address.

Continued

68P02901W19-S 12-89

Oct 2009

Restoring GUI Server file systems using ufsrestore utility Chapter 12: Backup Server Installation and Configuration

Procedure 12-46 Jumpstart a GUI Server (Continued)

10 A prompt is displayed that gives an option to configure a timeserver.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. However, if you specify a name, you must either have configured

DNS or you must add an entry to /etc/inet/hosts for your timeserver.

Do you want to configure a timeserver? (y/n) [n]: n

If a timeserver is to be configured, enter y. The following message isdisplayed:

Enter the timeserver’s name or IP address:

Enter the timeserver name or IP address.If there is no timeserver to be configured, press Enter, and the installationcontinues to configure the NIS Domain name.

11 A prompt is displayed to enter the NIS Domain.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) to be enabled.

The NIS domain is a character string e.g. omcadmin

Enter the NIS domain name: omcadmin

Enter the NIS Domain name.

12 A prompt is displayed requiring OMC-R server information:

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.

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

Operating Information: OMC-R System Administration Restoring GUI Server file systems using ufsrestore utility

Procedure 12-46 Jumpstart a GUI Server (Continued)

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

You can configure a printer at this time or later.

Contact your system administrator for help.

Do you want to configure a printer?: n

14 A prompt is displayed to configure a timezone.

Motorola GSM OMC-R GUI Server Installation

==========================================

Timezone Configuration

Your Sun-Based GSM OMC-R GUI Server will need to have a timezone

configured.

US/Eastern US/Central US/Mountain US/Pacific Japan

Enter the GSM OMC-R GUI Server’s timezone:

Type y and press Enter to get a list of timezones.

Press the space bar to navigate this list.

Australia/ACT

Australia/Broken_Hill

.

.

.

Australia/West

Brazil/Acre

Brazil/DeNoronha

Brazil/East

Brazil/West

Canada/Atlantic

If your timezone is known, press Enter and type in the timezone.

Enter the Common Platform GSM OMCR’s timezone:

Continued

68P02901W19-S 12-91

Oct 2009

Restoring GUI Server file systems using ufsrestore utility Chapter 12: Backup Server Installation and Configuration

Procedure 12-46 Jumpstart a GUI Server (Continued)

15 A summary of all of the values entered is presented. Screen output similarto the following is displayed:

Motorola GSM OMC-R GUI Server Installation Configuration - Summary

===================================================================

Primary Interface Printer

-------------------------

HOSTNAME: somc5 Install printer?: n

IP: 175.33.44.111

NETMASK: 255.255.255.0

SPLAT_NAME: somc57

SPLAT_IP: 175.3.44.4

Networking

----------

Default Router: 175.3.44.84 Domain:

NIS domain: omcadmin

DNS TIME

--—---—

Primary: TIMESERVER:

Secondary: TIMEZONE: Eire

Tertiary:

Would you like to make changes to the above values? (y/n) [n]

If all of the values are correct, press Enter to accept.However, if a value needs to be modified, type y and press Enter.Press Return to step through all the configuration values that have beenentered from point 4 onwards. These values will be in square brackets. Typein any updated values as necessary.

16 The password configuration prompt appears next.Enter and confirm the passwords for the users when prompted.

Motorola Common Platform GSM OMCR GUI Server Installation - Password

Configuration

==========================================

The system will now prompt you for passwords for the following users:

root

Enter root’s password:

Re-Enter root’s password:

Continued

12-92 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Restoring GUI Server file systems using ufsrestore utility

Procedure 12-46 Jumpstart a GUI Server (Continued)

17 The final prompt gives the option to enable the Network Services.

Motorola GSM OMC-R GUI Server Installation - Network Services

Configuration

==========================================

This GSM OMC-R GUI Server can take advantage of advanced network services

during this installation.

This GSM OMC-R GUI Server will need to be connected to the network

via the eri0

interface and it will be configured using the following information

IP: 175.3.44.227

NETMASK: 255.255.255.0

Would you like to enable network services? (y/n) [n]: n

Note: Entering y enables debugging mode.

The log files for this section can be found in /var/install/logs.The GUI Processor reboots automatically.

Overview of restoring the GUI Server file system

The following procedures assume that /(root)/usr/omc and /omcgen are the only file systemsbeing restored. Refer to the backup_MMI <datestamp> log file for the particular system. Ifextra file systems are to be restored, continue with a similar format as below for restoringthese file systems.

A GUI Server complete filesystem restore may be performed from the tape drive attached locallyto the GUI Server or from a tape drive attached to the Single Platform Processor. The followingprocedure describes how to perform a complete GUI Server filesystem restore using the tapedrive in the Single Platform Processor. 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 intothe tape drive that will be used to perform the restore (that is, the GUIServer’s tape drive or the Single Platform Processor tape drive.

2 If you are using the tape drive on the GUI Server Processor then, as userroot on the GUI Server processor, ensure that the tape is rewound to thebeginning by entering the following command:mt -f /dev/rmt/0 rewIf you are using the tape drive on the Single Platform Processor then, asuser root on the Single Platform Processor, ensure that the tape is rewoundto the beginning by entering the following command:mt –f /dev/rmt/0 rew

Continued

68P02901W19-S 12-93

Oct 2009

Restoring GUI Server file systems using ufsrestore utility Chapter 12: Backup Server Installation and Configuration

Procedure 12-47 Prepare for the restore (Continued)

3 As user root, execute the following command on the GUI Server:/var/install/bin/check_linkYour system administrator can inform you if you need to force a full duplexlink.

4 Retrieve the order in which the filesystems were backed up from the table inthe Procedure for backing up file systems using backup_MMI utilitysection of this guide.

Restoring root (/) file system

Use the following procedure to restore the first volume on the tape (/ file system).All warnings regarding the files already existing and those related to being unable to create softlinks, can be ignored. Follow Procedure 12-48 if you are using a local tape drive, that is, a tapedrive on the GUI Server. As the / file system has already been restored during the GUI serverjumpstart, only customizations are restored.

Procedure 12-48 Restoring the first volume on the tape (/ file system)

1 Execute the following commands:cd /ufsrestore if /dev/rmt/0nufsrestore > add /etc/inet/*ufsrestore > add /etc/hosts.equivufsrestore > add /etc/sshufsrestore > add /etc/mail/sendmail.cfufsrestore > extract

You have not read any volumes yet.

Unless you know which volume your file(s) are on you should

start with the last volume and work towards the first.

Specify next volume #:

When the following prompt is displayed, enter 1.

Specify next volume #:

2 The following prompt is displayed:

Directories already exist, set mode anyway? [yn]

Enter y.

Continued

12-94 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Restoring GUI Server file systems using ufsrestore utility

Procedure 12-48 Restoring the first volume on the tape (/ file system) (Continued)

3 The following prompt is displayed:

set owner / mode for ’.‘? [yn]

Enter y. The following error can be safely ignored:

Cannot set directory permissions: Operation not applicable

Cannot set directory ownership: Operation not applicable

Then quit to exit.

Follow Procedure 12-49 if you are using a tape drive located on the Single Platform Processorand the tape drive is used for backup. As the / file system has already been restored duringthe GUI server jumpstart, only customizations are restored. Additional extractions can beconfigured as part of this procedure. If prompted for a password, enter the root password ofthe Single Platform Processor.

Procedure 12-49 Using a tape drive located on the Single Platform Processor

1 Execute the following commands:cd /ssh <splat_ip_address> “dd if=/dev/rmt/0n” | ufsrestore if -

where <splat_ip_addr> is the IP Address of the Single Platform Processor.

ufsrestore > add /etc/inet/*ufsrestore > add /etc/hosts.equivufsrestore > add /etc/sshufsrestore > add /etc/mail/sendmail.cfufsrestore > extract

2 The following prompt is displayed:

set owner / mode for ’.‘? [yn]

Enter y.

3 The following prompt is displayed:

Directories already exist, set mode anyway? [yn]

Enter y.

The following error can be safely ignored:

Cannot set directory permissions: Operation not applicable

Cannot set directory ownership: Operation not applicable

4 Execute the following command:ufsrestore > quit

68P02901W19-S 12-95

Oct 2009

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 softlinks, can be safely ignored.

Follow Procedure 12-50 if you are using a local tape drive, that is, a tape drive on the GUIServer.

Procedure 12-50 Using a local tape drive

Enter the following commands:cd /omcgenufsrestore rf /dev/rmt/0n

Follow Procedure 12-51 if you are using a tape drive on the Single Platform Processor andthe tape drive is used for backup. If prompted for a password, enter the root password ofthe Single Platform Processor.

Procedure 12-51 Using the Single Platform Processor

Enter the following commands:cd /omcgenssh <splat_ip_address> “dd if=/dev/rmt/0n” | ufsrestore rf –rm restoresymtable

Where <splat_ip_addr> is the IP Address of the Single Platform Processor.

Restoring /usr/omc file system

All warnings regarding the files already existing and those related to being unable to create softlinks, can be safely ignored. Follow Procedure 12-52 if you are using a local tape drive, thatis, a tape drive on the GUI Server.

Procedure 12-52 Restoring /usr/omc file system

Enter the following commands:cd /usr/omcufsrestore rf /dev/rmt/0nrm restoresymtable

Follow Procedure 12-53 if you are using a tape drive on the Single Platform Processor andthe tape drive is used for backup. If prompted for a password, enter the root password ofthe Single Platform Processor.

12-96 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Selective File restore using restore_splat

Procedure 12-53 Using the Single Platform Processor

Enter the following commands:cd /usr/omcssh <splat_ip_address> “dd if=/dev/rmt/0n” | ufsrestore rf –rm restoresymtable

where <splat_ip_addr> is the IP Address of the Single Platform Processor.

Rebooting the GUI Server

Reboot the GUI Server by entering the following command as user root:/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 thathas been stored on a backup tape. Before commencing the restore procedure, ensure that acopy of the most recent set of Single Platform Processor complete file system level 0 backuptapes (created using the backup_splat utility) is available. Use the following procedure toperform a selective restore:

Procedure 12-54 Perform a selective restore

1 As user root, execute the following commands:mt -f /dev/rmt/0 rewindtar xf /dev/rmt/0 /tmp/restore_splat

Screen output similar to the following is displayed:

Rewinding 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

Selective File restore using restore_splat Chapter 12: Backup Server Installation and Configuration

Procedure 12-54 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 outputsimilar to the following is displayed:

Recovering /home ... Please Wait

Warning: ./lost and found: File exists

Warning: ./omcadmin: File exists

Warning: ./omcread: File exist

12-98 68P02901W19-S

Oct 2009

Chapter

13

Troubleshooting■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

68P02901W19-S 13-1

Oct 2009

Overview Chapter 13: Troubleshooting

Overview■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

The following topics are described in this chapter:

• Assessing a problem on page 13-3.

• Core file generation on page 13-6.

• OMC-R system information on page 13-8.

• Full file systems on page 13-21.

• File access problems on page 13-24.

• OMC-R software process errors on page 13-25.

• Resetting boot devices on page 13-28.

• Common Desktop Environment problems on page 13-33.

• CDE login failure on page 13-36.

• Troubleshooting the LAN on page 13-37.

• X.25 failure on page 13-39.

• Moving a machine with a forced link speed on page 13-41.

• Logical Vol Mgr troubleshooting on page 13-42.

• Replacing hard disk on system processor Sunfire/Netra 440/Netra 20 on page 13-43.

• Checking disk mirroring on page 13-47.

• Device busy error on page 13-49.

• Ejecting DVD-ROMs on page 13-50.

• StorEdge Enterprise Backup problems on page 13-51.

• Database failure on page 13-52.

• Onperf utilities on page 13-53.

• Checking and recovering database tables on page 13-70.

• Alarms on page 13-78.

• Setting FM audit and disk usage limits on page 13-88.

• Using neighbor statistics on page 13-91.

• Power failure on page 13-97.

• Checking the system processor hardware on page 13-99.

• Configuring a Timeserver on page 13-102.

13-2 68P02901W19-S

Oct 2009

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. Eachdescription includes a procedure that identifies the specific problem, and if possible, providesa solution.

Contacting Motorola

In the event of a support requirement, contact the local Customer Network Resolution Centrewith the information requested in the checklist that follows.

When contacting the Customer Network Resolution Centre at the end of a problem diagnosis,ensure that the information acquired is collated before telephoning the support personnel.

Preliminary checklist

Ensure that the following information is readily available when contacting the local Motorolasupport centre:

• Operator name.

• Date and time of fault.

• Problem title (a one-line description of the problem).

• What task the operator was doing up to 30 minutes before the fault occurred.

• Details of the BSS circumstances at the time of the problem, including the call scenario atthe time of the fault. For example:

A called B; B dropped.

Location of B.

The load details on the BSS at the time of the fault.

Any software fault management events.

Any event log details produced.

Details of database access at the time of the fault.

A printout of any GUI displays.

68P02901W19-S 13-3

Oct 2009

Preliminary checklist Chapter 13: Troubleshooting

The BSS software version.

System configuration details.

• Detailed description of the problem, including the following OMC-R details:

Any error messages.

System configuration details.

Note the processor and component (or area) of the system affected. This can bedetermined from the audit log or the GUI menu option that was being used when theproblem occurred. Keep a printout of relevant parts of the audit log file and the IPClog files (where appropriate).

The OMC-R software version.

Details of a core dump file, if one has been produced. This should be archived totape and sent to Motorola.

Fault severity, categorized as follows:

Service affected - indicates that the problem impacts the critical functionality of thesystem. For example, problems with the event manager or X.25 fall into this category.

Serious - indicates that a major portion of system functionality is affected, but thefault does not prevent the system from meeting its primary requirements.

Annoying - indicates a problem that may affect operations by being an inconvenienceor producing misleading or redundant outputs.

Cosmetic - indicates fault correction is required to ensure that the software conformsto certain standards. Does not affect the day-to-day running capabilities of theOMC-R software.

• Urgency of response required:

Immediate.

As soon as possible.

Next software release.

In a future software release.

13-4 68P02901W19-S

Oct 2009

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 internalerror. The error message must be identified, and the area of the system affected must belocated and the remedial action, such as an OMC-R stop/start, must be taken.

• Network Element (NE) connection failure

Connections between the OMC-R and the NEs can fail intermittently or permanently. Suchfailures can be caused by hardware malfunction, X.25 software, network connections (forexample, packet switch), or misuse of GUI command procedures.

• Operating system halt (panic)

If the UNIX operating system on any of the processors detects an internal error, it can stopprocessing. This is known as a panic condition, usually causing the affected processor toreboot. In some cases, the whole OMC-R system must be restarted and a core dump taken.

• Hardware failures

A hardware failure on one of the SPARC processors is likely to stop that processorfunctioning.

• Power failures

An ac power failure causes the OMC-R processors to reboot when the power is restored.Uninterruptible Power Supplies (UPSs) could be used to power all the OMC-R hardwarecomponents, thus providing some tolerance to power failures.

Further troubleshooting information can be found in the manual OMC-R Online Help, NetworkOperation.

68P02901W19-S 13-5

Oct 2009

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. It may be necessary to invokethis command in order to troubleshoot the OMC-R system problems and also produce a coredump of the system processor kernel so that this information can be analyzed by Motorola.

Application core dumps

If a fatal error occurs during the operation of either the application programs or the GUImodules, the respective programs will terminate and create a memory dump, core, in thefollowing directory:

$OMC_TOP/logs

Retrieve the memory dumps and return them to Motorola for analysis.

Generating a core of an OMC-R process

The gcore command has the following syntax:

gcore -o <filename> <process_id>

where <filename> is the file name and <process_id> is the process id of the OMC-R processfor which the core file is generated.

Operating system core dumps

If a fatal error occurs within the operating system of the system processor, a memory dump iswritten on the dump partition of the system disk. After reboot, the savecore utility copies it tothe /var/adm/crash directory. The memory dump files (core.n) and Operating System (OS)name list (unix.n) should be archived to tape and removed from the disk as soon as possible.The parameter n increases each time the savecore utility is run, and is the same value forboth the files.

core_presence utility

The core_presence utility checks for the occurrence of a core file on the system processor. If acore file is found, the user omcadmin is mailed.

13-6 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Checking core dumps

Checking core dumps

Use the following procedure to check core dumps. Copy the checklist provided in Table 14-9to record the checks.

Procedure 13-1 Checking core dumps

1 Check the presence of a core file when a fatal error occurs during theoperation of either the application programs or the GUI modules.As user root, execute the following commands:cd /usr/omc/logs/usrauditlogsls -l core*A core file should exist at the exact time that the fatal error occurredand should be in compressed format.

2 If an OMC-R process is causing severe problems, generate a core fileof the process. As user root, execute the following commands:gcore -o <filename> <process_id>Where <filename> and <process_id> are the file name and processID of that particular OMC-R process.The output from the gcore command indicates the name and locationof the core file.

3 If the system processor has any kernel problems, contact Sun supportfor instructions on how to address them.

4 If core files are not required, remove them as they can consume largeamounts of disk space.

68P02901W19-S 13-7

Oct 2009

OMC-R system information Chapter 13: Troubleshooting

OMC-R system information■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Obtaining system information

When a problem occurs on the OMC-R, information can be retrieved from the log files stored inthe /usr/omc/logs and the /usr/omc/logs/sys_info directories. The commands described inthis section are used to access the information contained in the sys_info files.

Additionally, the systat script can be used to create a file that reflects the status of the system,showing system up time, process list, disk status, system activity and system swap areas usedby the memory manager.

OMC-R log files

The log files stored in /usr/omc/logs/sys_info directories are generated every 10 minutes onthe system processor. Examining these files can determine whether specified processes arerunning and can reveal the behavior of the system.

The sys_info files have the following naming convention:

statmmddhhxx.Z

Where: is:

mm the month.

dd the day of that month.

hh the hour.

xx the minute the file was generated.

System uptime

The following command shows how long the system has been up:

/usr/ucb/uptime

In response to this command, an output similar to the following example is displayed:

1:28pm up 2day(s), 3:16 ‘7 users

load average: 0.03, 0.054, 0.05

13-8 68P02901W19-S

Oct 2009

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, an output similar to the following example is issued:

SunOS

The following command:

uname -a

produces a more detailed response, as follows:

SunOS somc57 5.9 Generic_118558-02 sun4u sparc SUNW,Ultra-Enterprise

Current processes

The following command gives the information about what processes are running:

/bin/ps -elf | more

Output is displayed in columns, each column having a column heading, the meaning of whichis explained in Table 13-1.

Table 13-1 Output from ps -elf command

Column heading Meaning

F Flags associated with the process.

S The state of the process.

UID The login name of the process owner.

PID Process id of the process.

PPID The process id of the parent process.

C Processor utilization for scheduling.

PRI The priority of the process. Higher number means lower priority.

NI Nice value, used in priority computation.

ADDR Memory address of the process.

SZ Size of the swappable processes image in main memory.

Continued

68P02901W19-S 13-9

Oct 2009

State of the file systems Chapter 13: Troubleshooting

Table 13-1 Output from ps -elf command (Continued)

Column heading Meaning

WCHAN The address of an event for which a process is sleeping.

STIME Starting time of the process given in hours, minutes and seconds. Ifprocess at the time of executing the ps command has been running formore than 24 hours, STIME is given in months and days.

TTY The controlling terminal of the process. The message is printed whenthere is no controlling terminal.

TIME The cumulative execution time of the process.

CMD The full command name and its arguments.

State of the file systems

In any system, it is necessary to take note of the state of the file systems. This information isrecorded in the sys_info files using the output of the /bin/df -k command. Sample output isas follows:

/bin/df -k

Filesystem kbytes used avail capacity Mounted on

/dev/md/dsk/d0 10152430 3099747 6951159 31% /

/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

/dev/md/dsk/d10 11903248 13966 11770250 1% /home

/dev/md/dsk/d15 8051300 8892 7961895 1% /solbak

/dev/md/dsk/d20 7056714 7025 6979122 1% /omcgen

/dev/md/dsk/d25 6049124 561066 5427567 10% /usr/omc

/dev/md/dsk/d30 16533099 66910 16300859 1% /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, there are problems with the OMC-R, wherebyfunctionality may be affected. If the file systems are filling up, it is necessary to purge unwantedfiles.

Integrity of X.25 communications

For the system to work correctly and to ensure proper communication between the devices, it isnecessary to ensure the integrity of X.25. This is done by executing the following command asuser root:

/opt/SUNWconn/bin/x25stat

The /opt/SUNWconn/bin/x25stat file shows the statistics for the X.25 port for which it is run.

13-10 68P02901W19-S

Oct 2009

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

-------------- -------------------- ------- *.sunrpc

Idle *.* Unbound *.32771

Idle *.1023 Idle

*.32775 Idle *.32776

Idle *.1022 Idle *.32777

Idle *.32781 Idle *.

32789 Idle *.*

Unbound *.32790 Idle *.32791

Idle *.lockd Idle

*.syslog Idle *.32792

Idle *.ntp Idle localhost.ntp

Idle somc57.ntp Idle

*.32794 Idle *.*

Unbound *.* Unbound *.32797

Idle *.7938 Idle

*.32801 Idle *.nfsd

Idle *.177 Idle *.8937

Idle *.32841 dle *.32847

Idle *.* Unbound

*.* Unbound UDP: IPv6 Local Address

Remote Address State If

------- --------------------------------- ---------- ----- *.

177 Idle TCP: IPv4

Local Address Remote Address Swind Send-Q Rwind

Recv-Q State----------- ----- ------ ----- ------

------- *.* 0 0 49152 0 IDLE

*.sunrpc 0 0 49152 0 LISTEN

.* 0 0 49152 0 IDLE *.1023

0 0 49152 0 BOUND *.32771

0 0 49152 0 LISTEN *.32772

0 0 49152 0 LISTEN *.32773

68P02901W19-S 13-11

Oct 2009

System resources Chapter 13: Troubleshooting

0 0 49152 0 LISTEN *.32774

0 0 49152 0 LISTEN *.dtspc

0 0 49152 0 LISTEN *.32778

0 0 49152 0 LISTEN *.32782

0 0 49152 0 LISTEN *.32786

0 0 49152 0 LISTEN *.printer

0 0 49152 0 LISTEN *.shell

0 0 49152 0 LISTEN *.shell

*.* 0 0 49152 0 LISTEN

The local address is machinename.ipc_channel specified in the ipc.cfg file.

The /usr/omc/current/config/ipc.cfg file gives the channel number used by OMC-R processesneeded to communicate externally to the machine on which the processes are stored.

The column state shows what condition the connection is in.

In the OMC-R, some processes may need to communicate with processes outside of their ownmachine. This can be done using the ipc command.

System resources

The following command gives useful information regarding the amount of available free memoryand also gives an indication of how busy the machine is.

/usr/bin/sar -ru | more

This command sends its output to the sys_info file.

13-12 68P02901W19-S

Oct 2009

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 117919

10731795 Average 118258

10733635 00:00:00 %usr

68P02901W19-S 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 99 02:40:00

0 0 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 99 05:00:00

0 0 0 99 05:20:00

0 0 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 swaplo blocks

free /dev/md/dsk/d5 85,5

16 9244784 9244784

PM database status

The following commands provide information on the status of the PM database and should beexecuted as user Informix:omc_env

13-14 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration PM database status

onstat -ukp | more

IBM Informix Dynamic server Version

9.40.UC4 -- On-Line -- Up 04:58:21

-- 467968 Kbytes Userthreads address

flags sessid user tty wait tout

locks nreads nwrites 24a67018 ---P--D

1 root - 0 0 0 75

70 24a67630 ---P--F 0 root -

0 0 0 0 903 24a67c48 ---

P--F 0 root - 0 0 0

0 723 24a68260 ---P--F 0 root

- 0 0 0 0 69 24a68878

---P--F 0 root - 0 0 0

0 0 24a68e90 ---P--F 0 root

- 0 0 0 0 0 24a694a8

---P--F 0 root - 0 0 0

0 0 24a69ac0 ---P--- 11 root -

0 0 0 0 0 24a6a0d8 ---P--B

12 root - 0 0 0 31

0 24a6a6f0 Y--P--- 10 omcadmin

console 2539e608 0 1 9 0

24a6ad08 Y--P--- 80 omcadmin console

254bcd18 0 1 0 0

24a6b320 ---P--D 15 root - 0

0 0 0 0 24a6b938 Y--P---

79 omcadmin console 252ac928 0 1

27 0 24a6bf50 Y--P--- 81

omcadmin console 254f08c8 0 1 0

0 24a6c568 Y--P--- 82 omcadmin

console 254e8328 0 1 0 0 24a6cb80

Y--P--- 83 omcadmin console

254e8e20 0 1 0 0 24a6d198 Y--P--- 84

omcadmin console 2551b918 0

1 0 0 24a6d7b0 Y--P--- 85

omcadmin - 25525430 0 1 2 0

24a6ddc8 Y--P--- 86 omcadmin - 25525f28

68P02901W19-S 13-15

Oct 2009

PM database status Chapter 13: Troubleshooting

0 1 10 0 24a6e3e0 Y--P--- 87

omcadmin console 255aaa30 0 1

0 0 24a6e9f8 Y--P--- 88 omcadmin -

255f8640 0 1 0 0 24a6f010 Y--P--- 89

omcadmin - 25615120 0 1 0 0

24a6f628 Y--P--- 78 omcadmin console

25615ed80 1 0 0 24a6fc40

Y--P--- 91 omcadmin console 2563fbc0

0 1 0 0 24a70258 Y--P--- 92 omcadmin

console 25686728 0 1 0 0 25 active,

128 total, 26 maximum concurrent Locks address

wtlist owner lklist type tblsnum rowid

key#/bsiz a110f98 0 24a6a6f0 0

HDR+S 100002 204 0 a110fec 0 24a6bf50

0 S 100002 204 0 a111040 0

24a6cb80 0 S 100002 204 0 a111094

0 24a6d7b0 0 S 100002 204 0

a1110e8 0 24a6e3e0 0 S 100002 204

0 a11113c 0 24a6f010 0 S

100002 204 0 a11cfe0 0 24a6fc40

0 S 100002 204 0 a412048 0

24a6b938 0 S 100002 204 0

a41209c 0 24a6ad08 0 S 100002

204 0 a4120f0 0 24a6c568 0 S

100002 204 0 a4121ec 0 24a6d198 0

S 100002 204 0 a417a84 0 24a6e9f8

0 S 100002 204 0 a42cdcc

0 24a6ddc8 0 S 100002 204 0

a42fcb8 0 24a70258 0 S 100002 204

0 a433330 0 24a6f628 0 S

100002 204 0 15 active, 75000 total,

32768 hash buckets, 0 lock table overflows Profile dskreads

pagreads bufreads %cached dskwrits pagwrits bufwrits

%cached 3797 4059 537450 99.29 1844

6447 60428 96.95

13-16 68P02901W19-S

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 beexecuted as user informix:mib_envonstat -ukp | more

IBM Informix Dynamic server Version 9.40.UC4 --

On-Line -- Up 4 days 19:04:44 -- 148480 Kbytes

Userthreads address flags sessid user tty

wait tout locks nreads nwrites 1120f018 ---P--D

1 root - 0 0

0 47 279 1120f630 ---P--F 0 root -

0 0 0 0 1167

1120fc48 ---P--F 0 root - 0 0

0 0 47 11210260 ---P---

11 root - 0 0 0 0 0

11210878 ---P--B 12 root -

0 0 0 0 0 11210e90 Y--P--- 10

omcadmin console 117f5fc8 0

1 58 0 112114a8 Y--P--- 21 omcadmin -

11bae8a8 0 1

34 0 11211ac0 ---P--D 15 root

- 0 0 0 0 0 112120d8

Y--P--- 23 omcadmin - 119d3cc0 0

1 298 0 112126f0 Y--P--- 19

omcadmin console 11990eb8 0 1 0

0 11212d08 Y--P--- 24

omcadmin - 119950c8 0 1 41

0 11213320 Y--P--- 25 omcadmin

- 11995c88 0 1 55 0 11213938

68P02901W19-S 13-17

Oct 2009

CM database status Chapter 13: Troubleshooting

Y--P--- 26 omcadmin - 11a26888

0 1 43 0 11213f50 Y--P--- 27

omcadmin - 11a2c518 0 1 23

0 11214568 Y--P--- 28 omcadmin -

11aaa168 0 1 41 0 11214b80 Y--P-29

omcadmin - 11aaad78 0 1

38 0 11215198 Y--P--- 30

omcadmin - 11aedea0 0 1 29

0 112157b0 Y--P--- 31 omcadmin -

11b35c10 0 1 33 0 11215dc8

Y--P--- 32 omcadmin - 11b548d8

0 1 56 0 112163e0 Y--P--- 33

omcadmin - 11bc02b8 0 1 49

0 112169f8 Y--P--- 34 omcadmin - 1

1c00598 0 1 40 0 11217010 Y--

P--- 47 omcadmin - 11d47700 0

1 0 0 22 active, 128 total, 24

maximum concurrent Locks address wtlist

owner lklist type tblsnum rowid

key#/bsiz a10ef98 0 11210e90 0

HDR+S 100002 205 0 a10efec

0 112126f0 0 HDR+S 100002

207 0 a10f040 0 11213320 0

S 100002 207 0 a10f094 0

11213f50 0 S 100002 207 0

a10f0e8 0 11214b80 0 S

100002 207 0 a10f13c 0 112157b0

0 S 100002 207 0

a10f190 0 112163e0 0 S

100002 207 0 a10f1e4 0

11217010 0 S 100002 207 0

a410048 0 112114a8 0 S

100002 207 0 a41009c 0 1

12120d8 0 S 100002 207

0 a4100f0 0 11212d08 0

S 100002 207 0 a410144 0

13-18 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration systat script

11213938 0 S 100002

207 0 a410198 0 11214568

0 S 100002 207 0

a4101ec 0 11215198 0 S

100002 207 0 a410240 0

11215dc8 0 S 100002 207

0 a410438 0

112169f8 0 S 100002 207

0 16 active, 75000 total, 32768 hash

buckets, 0 lock table overflows Profile

dskreads pagreads bufreads %cached

dskwrits pagwrits bufwrits %cached 1759

1886 900303 99.80 1285 2868

11443 88.77 isamtot open start

read write rewrite delete commit

rollbk 776978 115326 147445 285872

147 10626 102 4791 0

gp_read gp_write gp_rewrt gp_del

gp_alloc gp_free gp_curs 0 0 0

0 0 0 0 ovlock

ovuserthread ovbuff usercpu syscpu

numckpts flushes 0 0 0

70.33 2.15 15 2764 bufwaits

lokwaits lockreqs deadlks dltouts ckpwaits

compress seqscans 159 0 668644

0 0 0 102 4117

systat script

The systat script is used to create a file that reflects the status of the system, showingsystem up time, process list, disk status, system activity and system swap areas used bythe memory manager. It can be run on the system processor. The script is located in$OMC_TOP/current/sbin.

The systat script is intended to run as a cron job and removes files older than seven daysautomatically.

The format of the systat script is as follows:

systat

There are no parameters supported by the script.

68P02901W19-S 13-19

Oct 2009

systat script 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 whenrequested.

2 Enter the following to run the systat script:/usr/omc/current/sbin/systatWhen the script is complete, the user prompt is displayed.

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.To display the contents of the output stat file, enter the followingcommand:zcat /usr/omc/logs/sys_info/<filename>.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.9 Generic_

118558-02 sun4u sparc SUNW,Ultra-Enterprise

/usr/ucb/uptime: 11:52am up 4 day(s), 21:14, 2

users, load average: 0.09, 0.06, 0.05 who: root

console Apr 6 14:58 root pts/1 Apr 11 08:53

(10.131.6.108) /usr/ucb/vmstat 5 5: kthr memory

page disk faults cpu r b w 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 1 0 0 0 0 0 0 0 0 0

722 657 798 0 0 100 0 0 0 5281144 789528

0 0 0 0 0 0 0 8 8 8 0 743 675 812 0 0 100 0 0 0

5280944 789336 5 30 0 0 0 0 0 0 0 0 0 736

742 809 0 0 100 0 0 0 5281088 789480 0 1

0 0 0 0 0 0 0 0 0 719 670 802 0 0 100

/usr/bin/sar -r 5 5:

For further information on interpreting the output file, refer to the Solaris AnswerBook.

13-20 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Full file systems

Full file systems■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Full file systems

If file systems are filling up, this indicates that the amount of data being stored is more than thesystem supports, or that an administrator has made an error when trying to take a backup.

Identifying full file systems

A file system shows it is full if its capacity is at 100%.

Check which file system is creating the problem by executing the following command:

df -k

After identifying the problematic file system, look for any large files not expected to be present.For example, the following command looks for any files larger than 1 Mbyte on the root filesystem.

find / -size +1048576c -print

If the root file system is full, check the /dev/rmt directory for any large files because an error innaming a backup device can result in a file containing data that should have been taken a backup being created in the /dev/rmt directory.

Freeing up further disk space on the system processor

If the previous procedure ( Identifying full file systems on page 13-21) does not rectify theproblem, data must be archived by performing the following procedure on the system processor:

NOTEThis procedure should not be necessary if the routine procedures have been carriedout as recommended.

68P02901W19-S 13-21

Oct 2009

Removing files or directories Chapter 13: Troubleshooting

Procedure 13-3 Freeing up further disk space on the system processor

1 Identify, locate and remove any of the following files that are no longerrequired.

• Core files.

• Log files.

• Raw statistics files.

2 Follow the steps in Procedure 12-6, deleting the files wherevernecessary in order to maintain the usage of the disk file system below85%.

3 If the system continually runs above the recommended values, modifythe cron jobs to run some of the maintenance scripts more frequently.

4 Execute the omc_db_maint script more frequently to clean up oldcron logs, parser files, ev_logs and other OMC-R logs.

Removing files or directories

CAUTIONThis procedure checks if a file or directory is being referenced by any environmentvariables but does not guarantee that a file or directory can be deleted safely. If indoubt, do not delete the file or directory.

Use the following procedure to check if a file or directory is being used before removing afile or directory.

Procedure 13-4 Removing a file or directory

1 Perform any in-house procedures for checking if a file or directory canbe safely removed.

2 Execute the following command:env | grep <name>where <name> is the name of the file or directory to be deleted.If this command results in any output, as in the following example,then do not delete this directory. For example, the following outputis displayed for the directory name ListDir:env | grep ListDir

LISTTMPDIR=/usr/omc/logs/ListDir

Since there is an output the directory ListDir should not be deleted.

Continued

13-22 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Checking disk usage

Procedure 13-4 Removing a file or directory (Continued)

3 For files, execute the following command as user root:rm filenameExecute the following command to remove directories that are nolonger required:rm -rf directory name

Checking disk usage

Use the following procedure to check disk usage. Copy the checklist provided in Table 14-10to record the checks.

Procedure 13-5 Checking disk usage

1 Check the disk usage of the system by entering the following commandas user root:du -k | more

2 Remove any files that are not required and use too much disk space,for example, old core files, log files and statistic files.As user root, execute the following commands:cd directorypathrm -f filename

3 Check the amount of available free memory and how active the systemis 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 commandas user root:df -k | more

5 For file systems that are over 100% full, check for existing files thatare over 1 Mbyte and analyze the possibility of removing such files byentering the following command as user root:find filesystem -size +1048576c -print | more

68P02901W19-S 13-23

Oct 2009

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,this needs to be rectified using the following procedure:

Procedure 13-6 Handling stale NFS file

1 Login as root on the NFS server.

2 Make sure that an entry exists for the NFS client in the /etc/dfs/dfstabfile of the NFS server.

3 Execute the following command:shareall

4 As user root on the NFS client, execute the following commands:umountall -F nfsmountallIf this solution does not work, reboot the NFS client by executing thefollowing command:shutdown -i6 -g0 -yRemounting of the shared files automatically starts when the machinereboots.

5 Check that all file systems have been mounted on the NFS client byissuing 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 processordirectory structure ($OMC_TOP/ne_data/ev_logs), use the Network File System (NFS).

13-24 68P02901W19-S

Oct 2009

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, the audit logs ($OMC_TOP/logs) or the error messages fromthe system processor or GUI applications console screen can be used to analyze the problem.

Use the following procedure to analyze OMC-R software process errors:

Procedure 13-7 Analyzing OMC-R process errors

1 Check the error message displayed.

2 Examine all the relevant OMC-R user's home directory structure for acore dump.

3 Stop and restart the OMC-R software if the OMC-R software problem issevere. Refer to Manual startup and shutdown of OMC-R software onpage 7-12 for the procedure to stop and start the OMC-R.

4 Use the following UNIX commands to display process information onthe 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 4omcadmin 722 656 0 12:31:13 ? 0:00/usr/omc/current/bin/x25appl + 4omcadmin 958 953 0 12:31:44 ? 0:03/usr/omc/current/bin/scheduler +q +c/usr/omc/current/config -r informix +i 14omcadmin 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 + 2omcadmin 680 656 0 12:31:10 ? 0:00/usr/omc/current/bin/x25appl + 1omcadmin 679 656 0 12:31:10 ? 0:00

Continued

68P02901W19-S 13-25

Oct 2009

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 + 5omcadmin 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 + 6omcadmin 686 656 0 12:31:11 ? 0:00/usr/omc/current/bin/x25appl + 7omcadmin 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_1omcadmin 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 + 3omcadmin 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 fullyoperational processes. (Refer to Printing current OMC-R processes onpage 2-35 for further information.)

6 If the fault cannot be rectified, collate all the information beforecontacting the local Motorola support centre.

List of system processes

The following is a list of system processes:

• x25appl - X.25 Applications.

• emProxy - Event Management Proxy.

• em_main - Event Management Router.

• cm and cmMib - Configuration Management.

• em_lm_main - Event Management List Manager.

• downloader - Load Management Downloader.

• uploader - Load Management Uploader.

• RLogin - Remote Login.

• Parser - Performance Manager Parser.

• pm_main - Performance Manager Async.

13-26 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration GUI process

• fm_audit - OMC-R fault management audit.

• ResyncCtrl - Resync Controller.

• audit - Audit.

• smase - SMASE.

• resync - Resync.

• monitor - Monitor.

• pmProxy - Performance Manager Proxy.

• gateway - Gateway.

• scheduler - Scheduler.

• callTrace - Call Trace.

• gui - GUI.

• Event_Interface - Event Interface.

• PmLoader - PM Loader.

• CSM_MAIN - Call Success Monitor.

• nameserver - Name server.

• NetExp - Network Expansion.

• OmcPyTom - OMC Python.

• gprsTrace - GPRS Trace.

GUI process

There is one GUI process:

gui - OMC-R Graphical User Interface.

68P02901W19-S 13-27

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, the boot device will have tobe reset.

Procedure to reset a boot device

{34618} Use one of the following two procedures (Procedure 13-8 {34618} Resetting a bootdevice for a N20, N440, SF4800, or SF4900 on page 13-29 or Procedure 13-9 {34618} Resettinga boot device on an M4000 or M5000 on page 13-30:

Procedure 13-8 {34618} Resetting a boot device for a N20, N440, SF4800, orSF4900

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. When the OK prompt isdisplayed, enter the following command:setenv use-nvramrc? true

3 Proceed with specifying the boot disk block. At the OK prompt, enter thefollowing command:show-disks

4 On a Netra 440 which has been configured according to Installation andConfiguration: OMC-R Clean Install (68P02901W47), this command displaysthe following output:

Continued

13-28 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Procedure to reset a boot device

Procedure 13-8 {34618} Resetting a boot device for a N20, N440, SF4800, orSF4900 (Continued)

a) /pci@1f,700000/scsi@2,1/disk

b) /pci@1f,700000/scsi@2/disk

c) /pci@1e,600000/ide@d/cdrom

d) /pci@1e,600000/ide@d/disk

e) /pci@1d,700000/scsi@2,1/disk

f) /pci@1d,700000/scsi@2/disk

g) /pci@1d,700000/scsi@1,1/disk

h) /pci@1d,700000/scsi@1/disk

5 Choose entries e and g from the list and then set the device by entering thefollowing command followed by the SCSI id of the disk which is to be used.(For example, a disk@8,0:a indicates slice 0 of disk 0 which is located intarget 8.)nvalias mirrordisk /pci@1d,700000/scsi@2,1/disk@8,0:anvalias bootdisk /pci@1d,700000/scsi@1,1/disk@8,0:a

6 Make the settings permanent so that the processor will always rememberwhat 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 PlatformProcessor. At the PROM level, type:ok boot cdrom -s

2 In SINGLE USER MODE, run format to check all the disks in SPLAT:# formatOutput similar to the following is displayed for a SparcEnterprise M5000:

AVAILABLE DISK SELECTIONS:

0. c0t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@0,01. c0t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@1,02. c1t22d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>/pci@0,600000/pci@0/pci@9/LSILogic,sas@0/sd@16,03. c1t25d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>/pci@0,600000/pci@0/pci@9/LSILogic,sas@0/sd@19,04. c1t26d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>/pci@0,600000/pci@0/pci@9/LSILogic,sas@0/sd@1a,05. c1t27d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>/pci@0,600000/pci@0/pci@9/LSILogic,sas@0/sd@1b,06. c1t31d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>

Continued

68P02901W19-S 13-29

Oct 2009

Procedure to reset a boot device Chapter 13: Troubleshooting

Procedure 13-9 {34618} Resetting a boot device on an M4000 or M5000 (Continued)

/pci@0,600000/pci@0/pci@9/LSILogic,sas@0/sd@1f,07. c1t32d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>/pci@0,600000/pci@0/pci@9/LSILogic,sas@0/sd@20,08. c2t21d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>/pci@10,600000/pci@0/pci@9/LSILogic,sas@0/sd@15,09. c2t22d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>/pci@10,600000/pci@0/pci@9/LSILogic,sas@0/sd@16,010. c2t24d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>/pci@10,600000/pci@0/pci@9/LSILogic,sas@0/sd@18,011. c2t25d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>/pci@10,600000/pci@0/pci@9/LSILogic,sas@0/sd@19,012. c2t28d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>/pci@10,600000/pci@0/pci@9/LSILogic,sas@0/sd@1c,013. c2t30d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>/pci@10,600000/pci@0/pci@9/LSILogic,sas@0/sd@1e,0

Specify disk (enter the disk number): ^D

3 Now search for the boot devices in the external disks list (c0t0d0 and c0t1d0need not be checked). First check the disks connected to c1(Controller 1).Try to mount the disks on /a one by one.# mkdir /a# mount /dev/dsk/c1t22d0s0 /aIf the output is similar to following display, it is not a boot device.Try thenext one:

NOTICE: mount: not a UFS magic number (0x0)

mount: /dev/dsk/c1t22d0s0 is not this fstype

Otherwise, do more to check it:# ls /aIf the output is similar to the following display, it is a boot device.

INFORMIXTMP etc lib opt system

zones – – – –

bin export lost+found platform tmp

cdrom home mnt proc usr

dev jvp.log net sbin var

devices kernel omcgen solbak vol

Continued

13-30 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Procedure to reset a boot device

Procedure 13-9 {34618} Resetting a boot device on an M4000 or M5000 (Continued)

4 Now unmount the disk mounted on controller 1:# umount /aRepeat step 3 to find the boot mirror disk connected to c2(controller 2).An example similar to the following:# mount /dev/dsk/c2t21d0s0 /a# ls /a

INFORMIXTMP etc lib opt system

zones – – – –

bin export lost+found platform tmp

cdrom home mnt proc usr

dev jvp.log net sbin var

devices kernel omcgen solbak vol

The given example shows that bootdisk is /dev/dsk/c1t22d0s0 and themirrordisk is /dev/dsk/c2t21d0s0.

5 To retrieve the boot device physical names from their logical names andrecord them, execute the following commands:# ls -l /dev/dsk/c1t22d0s0lrwxrwxrwx 1 root root 63 Apr 14 01:34/dev/dsk/c1t22d0s0 ->../../devices/pci@0,600000/pci@0/pci@9/LSILogic,sas@0/sd@16,0:a# ls -l /dev/dsk/c2t21d0s0lrwxrwxrwx 1 root root 64 Apr 14 01:34/dev/dsk/c2t21d0s0 ->../../devices/pci@10,600000/pci@0/pci@9/LSILogic,sas@0/sd@15,0:a

6 At PROM level, set boot device by executing the following command:

# shutdown –i0 –g0 –y

The following is displayed

ok setenv use-nvramrc? True

ok show-disks

a) /pci@10,600000/pci@0/pci@9/LSILogic,sas@0/disk

b) /pci@10,600000/pci@0/pci@8/pci@0/scsi@1/disk

c) /pci@0,600000/pci@0/pci@9/LSILogic,sas@0/disk

d) /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/disk

q) NO SELECTION

Enter Selection, q to quit: c

/pci@0,600000/pci@0/pci@9/LSILogic,sas@0/disk has been selected.

Type ^Y ( Control-Y ) to insert it in the command line.

e.g. ok nvalias mydev ^Y

Continued

68P02901W19-S 13-31

Oct 2009

Procedure to reset a boot device Chapter 13: Troubleshooting

Procedure 13-9 {34618} Resetting a boot device on an M4000 or M5000 (Continued)

for creating devalias mydev for /pci@10,600000/pci@0/pci@9/LSILogic,sas@0/disk

Choose entries c and a from the list and set boot device by enteringthe following command.ok nvalias bootdisk/pci@0,600000/pci@0/pci@9/LSILogic,sas@0/disk@16,0:aok nvalias mirrordisk/pci@10,600000/pci@0/pci@9/LSILogic,sas@0/disk@15,0:a

Now enter the SCSI id of the disk according the boot device name in givenin step 5.

7 Reboot the processor by entering the following command:ok boot

13-32 68P02901W19-S

Oct 2009

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 thatprovides a consistent look and feel across UNIX environments.

Once a user has logged into one of the machines, a CDE session will start automatically. Thesession is customized for root, omcadmin and other.

Installing CDE

CDE is installed along with the Solaris operating system using JumpStart as part of theupgrade/clean install on the GUI server.

Configuring CDE

CDE is configured at installation time. Configuration files are copied from /usr/omc/config/localto /etc/dt/appconfig/types/C. This directory contains the customized configuration files (*.fp)which describe the composition of the front panel, menu items, icons and so on. Action files (ofthe form *.dt) are also included in this directory. Every action file should have a correspondingfile with the same name without the .dt extension (the contents of which are irrelevant) in thedirectory /etc/dt/appconfig/appmanager/C/Desktop_Apps.

The *.dt action files are essentially callbacks for some of the menu items in the frontpanel. Users root and omcadmin have personalized front panel configuration files$HOME/.dt/types/dtwm.fp.

A generic dtwmrc file is located in /etc/dt/config/C/sys.dtwmrc. A default system wide.dtprofile is located in /etc/dt/config/sys.dtprofile.

Icon files are located in /etc/dt/appconfig/icons/C.

Generic session files are located in /etc/dt/config/C. The file sys/resources contains thenumber of workspaces (defaults to one channel OMC-R). The sys.session file is processedonce for new CDE users and contains commands to start up the File Manager and CDE Helpautomatically when a new user logs on for the first time.

Every user, including root and omcadmin, should have a $HOME/.dt directory which containsall of the user specific configuration information. If a user customizes their session, the filesmost likely to be changed are in $HOME/.dt/sessions/current. A current.old directoryalso exists with the previous configuration.

68P02901W19-S 13-33

Oct 2009

Normal operation of CDE Chapter 13: Troubleshooting

Normal operation of CDE

CDE starts automatically. This is the default window manager for OMC-R operators andadministrators. It runs until the operator or administrator logs out.

User root has an omc_admin icon which provides an interface to the User Admin, Group Admin,and StorEdge Enterprise Backup utilities.

Both root and omcadmin have a CRON icon that allows access through a GUI to the crontabfiles.

Errors in user profiles

Errors in the following files could potentially stop users from logging onto the system:

• $HOME/.dtprofile.

• $HOME/.profile (for users of Bourne shell and Korn shell).

• $HOME/.login (for C shell users) if the following line is uncommented in $HOME/.dtprofile:

DTSOURCEPROFILE=true

If this occurs, the user should select the options menu from the login screen, select sessions,then select Failsafe session, and correct any errors in the above files.

Errors accessing a user's home directory

The home directories of the OMC-R users on the system processor are located in /home bydefault. If this directory is not correctly mounted then the user receives an error on login.Executing shareall (as root) on the system processor followed by mountall can clear up thisproblem.

Enabling/disabling the Print Manager

By default, only the root user has access to the Print Manager. To enable other users to accessthis, remove the control file which disables the Print Manager access to other users.

13-34 68P02901W19-S

Oct 2009

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/Cmv Printer.fp Printer.fpbak

2 Restart the CDE Worksession using the Restart option from thepulldown options of the left mouse button.

Disabling the Print Manager

If the Print Manager needs to be disabled on a per user basis, the Printer.fpbak file has to becopied to each user's directory using the following procedure.

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.fpbak/home/username/.dt/types/Printer.fp

2 Restart the CDE Work session using the Restart option from the pulldown options of the left mouse button.

Other CDE problems

If CDE has been set up, the following file should exist: /etc/dt/.cde_configured. This file shouldbe removed in order to rerun the CDE setup.

The files $HOME/.dt/startlog and $HOME/.dt/errorlog can be useful for diagnosing errors.

68P02901W19-S 13-35

Oct 2009

CDE login failure Chapter 13: Troubleshooting

CDE login failure■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Overview of CDE login failure

If a user cannot login through the CDE desktop, this indicates that the CDE configuration hasbecome corrupt, either on a user level or on a system wide level.

Procedure to recover from CDE login failure

Use the following procedure to rectify the CDE configuration, allowing users to login throughthe CDE desktop:

Procedure 13-12 Rectifying the CDE configuration to allow users to login throughthe CDE desktop

1 Login to the relevant processor as user root.

NOTEIn the case of user root CDE configuration being corrupt,use the telnet application from another processor in orderto gain access.

2 Reconfigure the affected user's CDE environment by entering thefollowing commands:rm /home/<user_name>/.dt/.cde_configured/usr/omc/current/sbin/CDE_setup <user_name>

3 If this fails to work, this means the system wide configuration iscorrupt. This may be rectified using the following commands:rm /etc/dt/.cde_configured/usr/omc/current/sbin/CDE_setup root

13-36 68P02901W19-S

Oct 2009

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, the OMC-R system administrator shouldcheck usage of the LAN.

Checking the performance of the LAN

The following command can be used to measure LAN bandwidth:

netstat -i

Name Mtu Net/Dest Address Ipkts Ierrs Opkts Oerrs Collis

Queue lo0 8232 loopback localhost 2416840 0 2416840

0 0 0 hme0 1500 somc57 somc57 1705354 0

525302 0 0 0

Check for the following scenarios:

• The number of Ierrs or Oerrs is high (0.025 percent or more of Ipkts or Opkts).

• Collis (collisions) is greater than 10 percent of Ipkts or Opkts.

If any of the above are true, there is a LAN performance problem. Check the LAN (routers,bridges, and so on), and check that there are not too many processors connected to the LAN.

The ping and spray commands can also be used if a particular processor on the LAN issuspected to be the cause of the problem.

If windows and forms are very slow to update, this may be related to the use of X.11 overthe LAN. The X.11 protocol is used to pass windowing information between the client (forexample, the GUI) and the server (the Motif window manager). If the updates to the screenare slow, or events or alarms are arriving late, there may be a backlog of X traffic, and LANperformance tests should be run.

To check the LAN to a remote GUI server, the GUI could be run on the remote GUI server withthe DISPLAY environment variable set back to the local processor to see if distance to theremote processor is a factor.

Taking a long time to open maps or access large files remotely could be due to NFS mountproblems.

Timeouts for each NFS mount can be increased if problems are occurring due to load on theLAN or when the distance between processors is great.

NOTEThe nestat output can be found in the /usr/omc/logs/sys_info/stat* files which arerun every 10 minutes, or the command can be run directly from the command line.

68P02901W19-S 13-37

Oct 2009

Checking if packets can be sent and received Chapter 13: Troubleshooting

Checking if packets can be sent and received

If there is a failure within the LAN, use the ping utility to determine the connectivity status ofthe LAN. Refer to the Solaris AnswerBook for further information.

Use the following procedure to use the UNIX ping command to confirm that the LAN interfaceis running:

Procedure 13-13 Using the ping command to confirm that the LAN interface isrunning

1 Enter one of the following on the processor to be interrogated:ping <remote_hostname>orping <remote_host_internet_address>Example:

/usr/sbin/ping 175.3.41.101

175.3.41.101: is alive

2 If the LAN interface is running, check the following LAN files:User file /etc/hosts: contains the information that maps the Internetaddresses to the host names. Each host within the OMC-R LAN musthave a unique line entry specified within this file.User file /etc/hosts.equiv.: can be used to specify remote accessprivileges to certain trusted hosts.User file ~omcadmin/.rhosts: can be used to specify trusted hosts ata user level. Each line contains the name of the remote system and theusers who have access rights to it.

3 If the LAN interface is not running, check the LAN cabling andassociated hardware.

4 If the fault cannot be rectified, collect all the information beforecontacting the local Motorola support centre.

13-38 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration X.25 failure

X.25 failure■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Overview of X.25 failure

Alarms are indicated on the relevant NE subscription window(s). Refer to the manual OMC-ROnline Help, Network Operation for information on alarm handling.

The following troubleshooting aids should be used to determine the possible fault:

• Synchronous communications trace.

• X.25 status utilities.

Tracing the synchronous communication uses the X25trace utility. Tracing can be performed ateither Level 2 (LAPB) or Level 3 (X.25). By default, all synchronous ports are traced at Level 3(X.25). It is strongly recommended that the tracing utility is not left running in the backgroundfor long periods of time. It is recommended to assign the output to a file.

NOTEAnalysis of data produced from tracing a synchronous port or executing the x25statutility on a particular port, should be performed in consultation with a Motorolaengineer.

Starting x25tool

Refer to Starting and stopping X.25 on page 9-9 for procedures on starting and stopping theX.25.

X.25 trace on the system processor

Use the following procedure to use the X.25 trace procedure:

Procedure 13-14 Running X.25 trace on the system processor

1 As user root, display the status of the X.25 by entering the followingcommand:/opt/SUNWconn/bin/x25stat

Continued

68P02901W19-S 13-39

Oct 2009

Displaying x25stat Chapter 13: Troubleshooting

Procedure 13-14 Running X.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.25. The x25trace commandrequires root permissions to execute. In this example, the trace isperformed on Level 3, the X.25 Packet layer interface for link 0. Enterthe following to start the trace:/opt/SUNWconn/bin/x25trace -i /dev/x25 -l 0 > trace_link0 &Allow enough time for X.25 data to be input/output to/from the X.25link. Note down the process id number that is displayed.

3 Terminate the x25trace process and examine the trace output data fileby entering the following command:kill -9 <x25trace process id number>cat trace_link0

4 Display X.25 utilities.Reset the packet counts regularly, and observe any changes in packetcount distribution. It is also useful to keep some x25stat outputs,taken when the network is known to be working correctly. Thesesamples can be used later to compare with output taken when thenetwork is not working correctly.

5 If the fault cannot be rectified, collate all the information beforecontacting the local Motorola support centre.

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 0The following is displayed:

PER LINK STATISTICS FOR X25 ____________________________

Link :

0 State : Unknown -------------------------------------

Packet type TX

RX ------------------------------------- Call 0

0 Call accept

0 0 Restart 0 0 Restart

confirm 0 0

RNR 0 0 RR 0 0

Resets 0 0

Reset confirms 0 0 Diagnostic

0 0 Interrupts

0 0 Registration 0 0

Reg confirm 0 0 Packets

(total) 0 0 Bytes (total)

0 0

13-40 68P02901W19-S

Oct 2009

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 Processorwill no longer auto negotiate the network speed. If the Single Platform Processor is latermoved to a network port which is not 100 Mbps full duplex, the Single Platform Processormay not be able to connect to the network. In order to re-instate auto negotiation, the script/etc/rc2.d/S31linkspeed needs to be removed.

Ensure that the task is completed as user root on the Single Platform Processor by executingthe following command:rm /etc/rc2.d/S31linkspeed

68P02901W19-S 13-41

Oct 2009

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 causedby the loss of a physical disk, or a file system problem caused by file system corruption.

NOTEIncorrect maintenance and administration of Logical Vol Mgr could cause the systemto crash and possibly lose the information held on the disks. Recovery should only beperformed by a Solaris Logical Vol Mgr expert.

13-42 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Replacing hard disk on system processor Sunfire/Netra 440/Netra 20

Replacing hard disk on system processor Sunfire/Netra440/Netra 20

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Errors on the console and in /var/adm/messages help to identify the disk that is causing aproblem. The problem is highlighted under Logical Vol Mgr as all metadevices using that diskare in a maintenance state.

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, enter the following command:metastat | moreOutput 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

Replacing hard disk on system processor Sunfire/Netra 440/Netra 20 Chapter 13: Troubleshooting

Procedure 13-15 Recovering a lost disk (Continued)

d26: Submirror of d25

State: Okay

Size: 1433371008 blocks (683 GB)

Stripe 0: (interlace: 512 blocks)

Device Start Block Dbase State Reloc Hot Spare

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

d27: Submirror of d25

State: Okay

Size: 1433371008 blocks (683 GB)

Stripe 0: (interlace: 512 blocks)

Device Start Block Dbase State Reloc Hot Spare

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

NOTEState: Needs maintenance indicates that a problem hasoccurred.

When the disk has been replaced (this can be done with the machinerunning), the disk requires repartitioning, and Logical Vol Mgr needsto be re-enabled to use that disk.

3 For example, the following commands are used to recover from theabove error once a new disk has been installed:prtvtoc /dev/dsk/c1t2d0s2 | fmthard -s - /dev/rdsk/c0t2d0s2metareplace -e d20 c0t2d0s0

Continued

13-44 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Replacing hard disk on system processor Sunfire/Netra 440/Netra 20

Procedure 13-15 Recovering a lost disk (Continued)

Output similar to the following is displayed:

d20: device c0t2d0s0 is enabled

When this has been done for each device that was in a maintenancestate, 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 Start Block Dbase State Hot Spare

c0t2d0s0 0 No Resyncing

d100: Submirror of d20

State: Okay

Size: 262960 blocks

Stripe 0:

Device Start Block Dbase State Hot Spare

c1t2d0s0 0 No Okay

68P02901W19-S 13-45

Oct 2009

Recovering from other Logical Vol Mgr problems Chapter 13: Troubleshooting

File system corruption usually causes both sides of the mirror to require maintenance, but onlyon that slice of the disk. Errors on other slices of that disk would highlight a more seriousproblem, 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 Dbase State Hot Spare

c0t2d0s0 0 No Maintenance

d100: Submirror of d20

State: Needs maintenance

Size: 262960 blocks

Stripe 0:

Device Start Block Dbase State Hot Spare

c1t2d0s0 0 No Maintenance

This problem can be fixed by shutting the machine down to single user mode and running fsckon the affected file system. The machine should then be rebooted and the problem should havebeen fixed. This can be confirmed by running metastat on the metadevice.

Recovering from other Logical Vol Mgr problems

Other problems with Logical Vol Mgr should be handled by a Solaris Logical Vol Mgr expert.

13-46 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Checking disk mirroring

Checking disk mirroring■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Disk mirroring checklist

To check disk mirroring, follow the procedure below. You can copy the checklist provided inTable 14-11 to record the checks.

Table 13-2 Disk mirroring checklist

Check Method

1 Check the Logical Vol Mgrstatus.

As user root, execute the following command:metastatA stable set of Logical Vol Mgr mirrors shouldlook similar to the example shown in the sectionmetastat output on page 13-47.

2 Check for any subdisks thatrequire maintenance usingthe metastat command. Anysubdisks that need maintenanceshould be repaired.

Refer to Logical Vol Mgr troubleshooting on page13-42 in this chapter for the procedure to recovera lost disk.

3 Check that the system has atleast three state databases oneach mirror.

As user root, execute the following command:metadb

4 If the system does not havesufficient state databases thenthey must be created.

As user root, execute the following command:metadb -a -f <slice 1> <slice 2> <slice 3etc>For example:metadb -f -d /dev/dsk/c1t2d0s3/dev/dsk/c2t2d0s3

metastat output

d125: Mirror Submirror 0: d126 State: Okay

Submirror 1: d127 State: Okay Pass: 1 Read

option: roundrobin (default) Write option: parallel (default)

Size: 4197717 blocks (2.0 GB) d126: Submirror of d125

State: Okay Size: 4197717 blocks (2.0 GB) Stripe 0

: Device Start Block Dbase State Reloc Hot Spare

d128 0 No Okay No d128: Soft Partition

Device: c0t1d0s0 State: Okay Size: 4198400 blocks

(2.0 GB) Device Start Block Dbase Reloc c0t1d0s0

0 No Yes Extent Start Block Block

68P02901W19-S 13-47

Oct 2009

metastat output Chapter 13: Troubleshooting

count 0 66854923 4198400 d127:

Submirror of d125 State: Okay Size: 4197717 blocks

(2.0 GB) Stripe 0: Device Start Block Dbase State

Reloc Hot Spare d129 0 No Okay No

d129: Soft Partition Device: c2t5d0s0 State: Okay Size:

4198400 blocks (2.0 GB) Device Start Block Dbase Reloc

c2t5d0s0 0 No Yes Extent Start Block

Block count 0 66854923

4198400 d120: Mirror Submirror 0: d121 State: Okay

Submirror 1: d122 State: Okay Pass: 1

13-48 68P02901W19-S

Oct 2009

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 was already mounted.

If an attempt to unmount a device has failed, this indicates that the device contains an active filesuch as an open file, a current directory, a mount point, or a running program.

This message also occurs when trying to enable accounting that is already enabled.

Unmounting a device

To unmount a device containing active processes, close all the files under that mount point,quit any programs started from there and change directories out of that hierarchy. Then try tounmount again.

68P02901W19-S 13-49

Oct 2009

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 thecommand eject cdrom, the following procedure can be used to manually eject the DVD-ROM.

Procedure to free up DVD-ROM drive

Use the following procedure to eject a DVD-ROM from the DVD-ROM drive of a SPARC processorwhen the eject cdrom command fails to work:

Procedure 13-16 Procedure to free up a DVD-ROM drive

1 Login as root.

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.

4 Type the following command to restart volume management:svcadm enable volfs

13-50 68P02901W19-S

Oct 2009

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 intothe tape drive, or if the backup tape in the tape drive has not been mounted and/or labeled.An unmounted tape is indicated by the following error in the pending field of the StorEdgeEnterprise Backup utility:

Tape from default pool not mounted, waiting

Use the following procedure to mount a new tape to be used in a backup:

Procedure 13-17 Mounting a new tape to use in a backup

1 Check if the correct tape is inserted in the tape drive.

2 From the StorEdge Enterprise Backup Server GUI Administrationwindow, click Devices and select the tape driver (/dev/rmt/0cbn)from the Device list.

3 Click on the Mount icon to mount the tape. The tape should then bemounted and the backup will continue.If a new tape has been inserted then the tape should first be labelledby clicking Label, and should be mounted in the usual way.

68P02901W19-S 13-51

Oct 2009

Database failure Chapter 13: Troubleshooting

Database failure■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Database failure

In the event of a failure of the INFORMIX database, the log file should be examined to locate theproblem. Other sections in this manual give more details of the procedures involved.

Use the following procedure to investigate database failure:

Procedure 13-18 Investigating a database failure

1 Examine the online log. Refer to Database utilities on page 8-4 forfurther information.

2 Use the Mode menu selection of onmonitor to determine the mode ofoperation. Refer to Database utilities on page 8-4 for further detailsabout onmonitor.

3 Examine the software log files in $OMC_TOP/logs. Refer to OMC-Rlog and error files on page 4-3 for further information.

4 If the fault cannot be rectified, collate all the information beforecontacting the local Motorola support centre.

Problems adding/updating statistics in PM database

If problems are being experienced with PM statistics, check whether dbms log files are present.These log files are created when problems are encountered during adding or updating statisticsin the PM database. There should be one dbms log file per error that occurs.

The filename will be of the form dbms.nnnnnnnn, where nnnnnnnn is a unique integeridentifying the log file.

To find out when the log was created, use the following UNIX command:

ls -l

13-52 68P02901W19-S

Oct 2009

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 PerformanceManagement (PM) and Configuration Management (CM) databases. The user selects items tobe measured. These may be displayed graphically in real time, or stored for later playback.

The Onperf utilities are implemented in INFORMIX and run on the system processor.

The Onperf utilities perform the following basic functions:

• Display the values of online metrics in the Graph Tool window.

• Save online metric values to a file.

• Allow review of online metric values from a file.

Starting onperf from the CDE front panel

Use the following procedure from the CDE front panel to start the onperf utility for the PM orCM databases:

Procedure 13-19 Starting onperf from the CDE front panel

1 Login to the system processor as user omcadmin.

2 On the CDE front panel, click the INFORMIX icon and select one of thefollowing options from the Database Applications menu.

• To monitor the PM database, select onperf - PM database.

• To monitor the CM database, select onperf - MIB database.

Either selection causes the Graph Tool window (Figure 13-1) to bedisplayed.

68P02901W19-S 13-53

Oct 2009

Starting onperf from the command line Chapter 13: Troubleshooting

Figure 13-1 Displaying the OnPerf utility window

ti-GSM-Displaying_the_OnPerf_utility_window-00080-ai-sw

Starting onperf from the command line

The onperf utility may be invoked from the UNIX command line as an alternative to startingfrom the CDE front panel.

Procedure 13-20 Starting the onperf utility from the command line

1 Login to the system processor as user omcadmin.

2 Enter the following command:setenv DISPLAY omc_splat:0.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

Operating Information: OMC-R System Administration Loading a history file

Procedure 13-21 Loading and displaying a history file

1 From the CDE desktop environment, click on the OnPerf icon for theapplication database. The Graph Tool window is displayed as shownin Figure 13-1.

2 From the Graph menu (Figure 13-2), select the Open History Fileoption.

3 The standard Select File dialog box is displayed as shown inFigure 13-3.

4 Enter the path name of a history file in the selection box to load intothe Graph Tool.

5 Click OK. The history file is displayed in the Graph Tool window.

NOTEA history file consists of metrics data previously saved by thedata collector. To help find a history file, specify a wildcardfilter. In the Filter edit box, enter a directory path thatincludes wildcards. Click on the Filter command button atthe bottom of the window. All files that satisfy the filter arelisted on the right.

Figure 13-2 Graph menu

ti-GSM-Graph_menu-00056-ai-sw

68P02901W19-S 13-55

Oct 2009

Loading a history file Chapter 13: Troubleshooting

Figure 13-3 Select file dialog box

ti-GSM-Select_file_dialog_box-00057-ai-sw

13-56 68P02901W19-S

Oct 2009

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, select New. This creates a new Graph Tool.There is no difference in functionality between the new Graph Tool andthe original Graph Tool. These tools may be closed in any order.

2 To save a new configuration, select the Configure menu and clickSave Configuration As (refer to Figure 13-4). In the Save File dialogbox that appears, enter a file name in the selection box to store thepresent Graph Tool configuration. Configuration information includesthe set of histogram buffers, the active graph and activity tools.

3 To help find a directory in which to write the file, a wildcard filter maybe specified. Enter a directory path that includes wildcards in theFilter edit box, then click the Filter command button. All files thatsatisfy the filter will be listed.

4 When a configuration has been previously saved to a file, the SaveConfiguration option can be used to update that graph configurationfile (refer to Figure 13-4).

Figure 13-4 Configure menu

ti-GSM-Configure_menu-00058-ai-sw

68P02901W19-S 13-57

Oct 2009

Selecting metrics 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, select a metric class.

2 A Select Metrics window is displayed with the metric class selected.

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 tothe selected scope.

4 Select a metric from this list.

5 Click Add. The metric is added to the list box on the right.

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

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, the relevant metric scopes are chunk pathnames for the onlinedatabase server.

• For the disk spindle class, the relevant metric scopes are the pathnames of the disk devicesor cooked files used by the online database server.

• For the fragment metric class, the relevant metric scopes are the dbspaces for fragmentsthat are currently open to a thread. These are called active table fragments.

• For the physical processor class, the relevant metric scopes are any of the physicalprocessors for the computer running online, or total for an aggregate of all the physicalprocessors.

• For the server class, there is only one metric scope, aggregate. The scope for these metricsis the database server as a whole.

• For the disk sessions class, the relevant metric scopes are the active sessions, identified byuser login and host name.

• For the tblspace metric class, the relevant metric scopes are the tblspace names thatcorrespond to tables that are currently open to a thread. These are called action tables.A tblspace name is a composite of the database and the table that it refers to. Forfragmented tables, the tblspace represents the sum of all fragments for that table. Toobtain measurements for a single fragment, use the fragment metric class.

• For the virtual processor class, the relevant metric scopes are the online virtual processorclasses: CPU, AIO, KIO, and so on. Each virtual processor metric represents an aggregateof activity for all online virtual processors of the indicated class.

Viewing metrics

By selecting any of the options from the View menu, the metric can be viewed in variousformats, as illustrated in Figure 13-6:

Figure 13-6 View menu

ti-GSM-View_menu-00060-ai-sw

68P02901W19-S 13-59

Oct 2009

Viewing metrics Chapter 13: Troubleshooting

Line Plot

When this option is selected, Onperf repaints the Graph Tool in the line format as shownin Figure 13-7.

Figure 13-7 Line plot graph

ti-GSM-Line_plot_graph-00061-ai-sw

In this format, the window includes two scroll bars: a horizontal pan bar and a vertical zoombar. The zoom bar adjusts the scale of the horizontal time axis. When the zoom bar is raised,the scale is reduced, and vice versa. The pan bar allows movement along the horizontal timeaxis. To change the scale or appearance of an individual metric, click on the legend for thatmetric. This displays the Customize Metric dialog box. This box has buttons for setting themetric scale, color, style and width.

NOTEThe line graph may contain hidden data values. These can be displayed by selectingthe View menu option Show null values.

13-60 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Viewing metrics

Horizontal Bar Graph

When this option is selected, the Graph Tool is redrawn in horizontal bar format as shownin Figure 13-8.

Figure 13-8 Horizontal bar graph

ti-GSM-Horizontal_bar_graph-00062-ai-sw

In this format, the horizontal axis represents the scale of each metric. To change the scale orappearance of an individual metric, click on the legend for that metric. This brings up theCustomize Metric dialog box, which has buttons for setting metric scale, color, style and width.

68P02901W19-S 13-61

Oct 2009

Viewing metrics Chapter 13: Troubleshooting

Vertical Bar Graph

When this option is selected, the Graph Tool is redrawn in vertical bar format as shown inFigure 13-9.

Figure 13-9 Vertical line graph

ti-GSM-Vertical_line_graph-00063-ai-sw

In this format, the vertical axis represents the scale of the metric measurement. To change thescale or appearance of an individual metric, click on the legend for that metric. This bringsup the Customize Metric dialog box, which has buttons for setting metric scale, color, styleand width.

13-62 68P02901W19-S

Oct 2009

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 inFigure 13-10.

Figure 13-10 Pie chart

ti-GSM-Pie_chart-00064-ai-sw

The pie charts show the relative sizes between metrics, but not the values themselves. The lastsampled values are displayed in the legend next to the metric name.

68P02901W19-S 13-63

Oct 2009

Monitoring tools Chapter 13: Troubleshooting

Monitoring tools

The monitor tools include the Status Tool and the Query Tree. These are described below:

Status Tool

The Status Tool monitors the state of the data collector and the database server. A typicalStatus Tool window is displayed in Figure 13-11.

Figure 13-11 Status tool

ti-GSM-Status_tool-00065-ai-sw

13-64 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Monitoring tools

Query Tree

The Query Tree window allows the performance of individual queries to be monitored. Atypical Query Tree window is displayed in Figure 13-12. The Query Tree tool has two options:Select Session and Quit. When a session which is running a query is chosen, the large detailwindow displays the iterations that comprise the execution plan for the query. The Query Treetool represents each iteration by a box that includes a dial indicating tuples per second anda number indicating the input tuples for the iteration. In some cases, not all the iterators fitinto the detail window. The left pane shows the iterators as small icons. This provides a mapof the overall query.

Figure 13-12 Query Tree

ti-GSM-Query_Tree-00066-ai-sw

68P02901W19-S 13-65

Oct 2009

Activity tools Chapter 13: Troubleshooting

Activity tools

There are five different activity tools:

• Disk activity.

• Session activity.

• Disk capacity.

• Physical processor activity.

• Virtual processor activity.

Each of these activity tools displays information about a particular database activity, basedon some suitable metric.

The scale of an activity tool cannot be changed from within the tool itself. There are two activitytool menus: the Graph menu and the Tools menu. The Graph menu has options for closing thegraph, opening a new graph, and exiting Onperf. The Tools menu has options to display theQuery Tree tool, status tool, or another activity tool.

Disk Activity Tool

The Disk Activity Tool displays activities for chunks, ranked according to the Disk Operationsmetric. The metric class is Disk Chunk and the metric scope is the chunk pathname. Thismetric represents the total number of I/O operations involving the chunk. The horizontal bargraph view is used.

Figure 13-13 Disk Activity Tool

ti-GSM-Disk_Activity_Tool-00067-ai-sw

13-66 68P02901W19-S

Oct 2009

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 inmegabytes. The horizontal bar graph view is used.

Figure 13-14 Disk Capacity Tool

ti-GSM-Disk_Capacity_Tool-00068-ai-sw

68P02901W19-S 13-67

Oct 2009

Activity tools Chapter 13: Troubleshooting

Session Activity Tool

The Session Activity Tool displays the sessions for the database server. The metric class isSession and the metric scope is the host name. This metric represents the total number of ISAMcalls and PDQ calls per second. The horizontal bar graph view is used.

Figure 13-15 Session Activity Tool

ti-GSM-Session_Activity_Tool-00069-ai-sw

13-68 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Activity tools

Virtual processor Activity Tool

The Virtual processor Activity Tool displays the virtual processors configured for thedatabase server. The horizontal bar graph view is used. The scale of the Virtual ProcessorActivity Tool cannot be changed manually.

Figure 13-16 Virtual Processor Activity Tool

ti-GSM-Virtual_Processor_Activity_Tool-00070-ai-sw

68P02901W19-S 13-69

Oct 2009

Checking and recovering database tables 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.

To use these commands, login as omcadmin.

13-70 68P02901W19-S

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.These lines are similar to the following:

DBS Pages Allocated: 309981 DBS Pages Used: 309981 DBS Pages

Free: 0 Warning: OMC Database space used has reached 100% specified

DBMS_MAX_SPACE_USED 80%

TBLSpace TBS Pages Allocated: 251748 TBS Pages Used: 7108 TBS

Pages Free: 244640

The DBS Pages section shows the number of pages:

• In all DB spaces (that is, available to the server).

• Allocated to tables.

• NOT allocated to tables.

The TBS Pages section shows the number of pages:

• Allocated to data tables.

• With data on them.

• Allocated to tables but which are currently empty.

The example above illustrates that the database can appear to be full (from the DBS Pagessection) although there may be plenty of space left within the tables. Also, the above exampledoes not show the distribution of free space among the tables, so inserts into one table can faileven if there is free space in other tables. Once space has been allocated to a specific table, it isNEVER freed up into the general pool without manual intervention.

db_ckspace command

The command db_ckspace shows the amount of space used in each chunk and in each dbspace.The output is similar to:

On-Line Instance: DBSpace AllocUsedFree Device

rootdbs 309981 167263 142718 /dev/rvol/omc_db

==================================

309981 167263 142718 rootdbs Total

=============================

Total 309981 167263 142718

68P02901W19-S 13-71

Oct 2009

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 Free Extent DataPg

#Rows subscriptions 1239 20 1219 1 11

84 subscription_list 20 5 15 1 2 31

bss_datetimes 26 23 3 5 6719

bss_statistics 109 4105 1 1 1

cell_statistics 5639 5639 0 5 2292 9162

The Pages column shows the number of pages allocated to the table, and the Used and Freecolumns show the number of pages with and without data respectively. The Free pages arepermanently allocated to one table, but not currently used by it, so they comprise part of theTBS Pages Free value in the output from omc_db_ckspace. The Extent column shows thenumber of table fragments. If there are more than 16, consider defragmenting the table.

Combining commands

When used together, the db_ckspace and db_cktab commands give a clear picture aboutdatabase space usage. omc_db_ckspace gives a very simple overview of the situation, whichshould not be relied upon.

The onstat -d command is similar to the db_ckspace command as it shows each dbspace in thefirst part of the output, then each chunk in the second part of the output (with dbspace andchunk numbers, so you can see which chunks belong to each dbspace). The output is similarto the following:

Dbspaces address number flags fchunk nchunks flags ownername

310260e0 1 1 1 1 N informix rootdbs 31026658 2 1 2 1 N informix

omc_db_temp 310266c0 3 1 3 1 N informix omc_db_plog 31026728

4 1 4 1 N informix omc_db_llog 31026790 5 1 5 1 N informix

omc_db_sp1 310267f8 6 1 6 1 N informix omc_db_sp2 6 active,

2047 maximum

Chunks address chk/dbs offset sizefree bpages flags pathname

31026148 1 1 2 51198 17113 PO-/dev/omc_db_root 31026220

2 2 2 204798 204745PO-/dev/omc_db_temp 310262f8 3 3 2 40958

905 PO-/dev/omc_db_logs 310263d0 4 4 40962 158718 70915

PO-/dev/omc_db_logs 310264a8 5 5 2 1024098 797169PO-/dev/omc_db1

31026580 6 6 2 1024098 1024045 PO-/dev/omc_db2 6 active,

2047 maximum

The oncheck -pe command is as good as an input to a shell script. It lists each chunk withineach dbspace, and every tablespace fragment (extent) of every table, including unallocatedspace. The output is unwieldy and would need filtering for your purposes.

13-72 68P02901W19-S

Oct 2009

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.

To get all information about a database (so that it can be recreated from scratch), enter thefollowing command:

dbschema -d <dbname> -ss -p all <outputfile>

If you omit <outputfile>, output is sent to stdout, but this is likely to be too much to read easily.

NOTEA database can be created from the above output file by typing:

isql - <commandfile>

where <commandfile> is the <outputfile> from dbschema.

To show just the synonyms in the database, enter the following command:

dbschema -s all -d <dbname>

Defragmenting tables (MIB database)

The MIB database tables are small compared to those on the PM database. It is normally easy todefragment them non-destructively, by executing an SQL command which forces INFORMIXto rebuild the table. To do this, use the alter index <indexname> to cluster command,which sorts the data in a table into the key value order of the nominated index. INFORMIXimplements this by sorting the data into a new tablespace, then deleting the old tablespaceand renaming the new one.

NOTEThe following procedures should only be carried out with the advice of a MotorolaEngineer.

The following defragmenting procedure:

• Does not cause any loss of data from the MIB.

• Can be used on any table, provided there is sufficient free space in the dbspace to create asecond copy of the table.

• Normally reduces the number of extents to three or fewer.

• Depending on how much contiguous free space is present, it does not normally requirean outage.

68P02901W19-S 13-73

Oct 2009

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, enter the following command:dbschema -d dbname -t tablename

4 Look at the names of indexes. If one of the definitions is create clusterindex <indexname>, use that. Otherwise, choose an index definedwith create unique index <indexname>. If there are no uniqueindexes, choose an index that looks as though it is frequently used (it isunlikely to cause any major performance problems even if you choosean inappropriate index).

5 To cluster the index, enter the following command:isql dbname -alter index indexname to cluster;<CTRL>-C

6 If you see the message table is locked, try again after a few minutes. Ifthe table is locked permanently, you may need to schedule an omc stopor start (cluster the index after the omc stop but before the omc start).

NOTEDo not follow the procedure in Customer Service BulletinCSB-98-015, because it does not cater for views or any otherconstructs you might encounter away from the statisticstables.

Emptying and defragmenting one or more PM statistics tables

This is the quick and easy way to remove troublesome statistics, and defragment the statisticstable at the same time. It is possible to complete the process within five minutes, with anoutage time of less than two minutes.

This procedure results in all the statistics in the affected table being lost. It must only be usedon tables which do not have views (this includes all tables whose names end in _statistics. Itnormally reduces the number of extents to two (there is no need to get a table into a singleextent). It requires a short PM outage (typically, less than five minutes).

NOTEThe following procedures should only be carried out with the advice of a MotorolaEngineer.

13-74 68P02901W19-S

Oct 2009

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.

2 Enter the following command:omc_env

3 To determine the size of the table(s) and to find the size of the databasetable currently being used, enter the following command:db_cktab -d omc_dbThe output is similar to the following:

Table Name (Number): Pages Used Free Extent DataPg #Rowsnbr_statistics (0x01000040): 1000 775 225 1443 18532carrier_statistics (0x01000030): 166910 166133 777 15 49610297671cell_statistics (0x01000006):100632 10053597 19 27620165715

4 Multiply the value in the Used column by two to get the size inkilobytes. For example, the size of the cell_statistics table in the aboveexample is 100535 pages multiplied by 2 KB page size equals 201070KB.

5 To alter the next size of the table(s), enter the following commands:isql omc_db -alter table tablename next size size_in_kb;<CTRL>-Cwhere <tablename> is the table name and <size_in_kb> is the size(in kilobytes) of the table.

6 Repeat the alter table line in step 5 for each table you want to empty.(The <CTRL>-C is to quit isql.)

7 To get the schema of the table(s), enter the following command:dbschema -d omc_db -t tablename -ss -p all tablename.sql

8 To disconnect the OMC-R processes (outage start), enter the followingcommand:db_disconnect disconnect

9 To drop the table(s), enter the following:isql omc_db -drop table tablename;<CTRL>-C

10 To recreate the empty table(s), enter the following command:isql omc_db tablename.sql

11 To reconnect the OMC-R processes (outage end), enter the followingcommand:db_disconnect connect

68P02901W19-S 13-75

Oct 2009

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, you canadd extra logs. These logs will increase the resilience of the server against transactions thattake a long time to update.

NOTEThe following procedures should only be carried out with the advice of a MotorolaEngineer.

Use the following procedure to add extra logs, repeating this procedure until there is no roomleft 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.

2 Enter the following command:omc_env

3 Enter the following command to see if there is any space left on thelogical log partition:onstat -dThe output looks like this:

Dbspacesaddress number flags fchunk nchunks flags ownername310260e0 1 1 1 1 N informix rootdbs31026658 2 1 2 1 N informix omc_db_temp310266c0 3 1 3 1 N informix omc_db_plog31026728 4 1 4 1 N informix omc_db_llog31026790 5 1 5 1 N informix omc_db_sp1310267f8 6 1 6 1 N informix omc_db_sp26 active, 2047 maximum

Chunksaddress chk/dbs offset sizefree bpages flags pathname31026148 1 1 2 51198 17113 PO-/dev/omc_db_root31026220 2 2 2 204798 204745PO-/dev/omc_db_temp310262f8 3 3 2 40958 905 PO-/dev/omc_db_logs310263d0 4 4 40962 158718 70915 PO-/dev/omc_db_logs310264a8 5 5 2 1024098 797169PO-/dev/omc_db131026580 6 6 2 1024098 1024045 PO-/dev/omc_db26 active, 2047 maximum

The first part of this output shows the dbspaces. The second partshows the chunks, which make up the dbspaces.

Continued

13-76 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Adding extra logical logs to the PM database server

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_llogdbspace (30 k or 45 k systems) or the omc_db_logs dbspace (5 ksystems), and note the dbspace number (4 in the example above).

5 Find the corresponding number in the dbs column of the Chunks list(there can be several chunks to one dbspace). The amount of freespace can be determined by examining the free column.

6 To find the size of the existing logs, enter the following command:onstat -lThis shows the log file size in 2 k pages in the last part of the output. Inthe following example, the logs are 10240 pages, which is 20480 KB:

address number flagsuniqid beginsize used%useda57cfc8 1F------ 0307835 102400 0.00

7 When you add a logical log, use the following command to specify thesize (in kilobytes):onparams -a -d DBspace [-s size]In this example, you can use:onparams -a -d omc_db_llog -s 20480

68P02901W19-S 13-77

Oct 2009

Alarms Chapter 13: Troubleshooting

Alarms■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Overview of alarms

Certain OMC-R alarms cannot be handled by the operator and will be referred to the systemadministrator for corrective action. Such alarms fall into the following categories:

• Disk space usage on the system processor.

• Database.

• X.25 lines connected to the system processor.

• System processor failure.

• Frequency of events arrival.

For more information on alarm handling procedures, refer to OMC-R Online Help, NetworkOperation. For more information on the alarms, refer to Maintenance Information: AlarmHandling at the OMC-R (68P02901W26) manual.

NOTEIf the number of alarms in the PLMN alarm window does not match with the OMCmain board, close the PLMN alarm window, and reopen it. The correct alarm numberis displayed.

13-78 68P02901W19-S

Oct 2009

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

When the threshold value is exceeded, the system removes any log files older than three daysfrom the $OMC_TOP/logs. The threshold value should return to 90 percent.

Use the following procedure to resolve the alarm:

Procedure 13-27 Resolving the UpperLimitDiskUsage (30010) alarm

1 Raise the value of the upper threshold limit (if less than 90 percent) inthe file $OMC_TOP/config/global/FM_audit.CNFG.

2 Perform the disk full procedures.

LowerLimitDiskUsage (30011) alarm

An alarm is raised when the lower threshold of disk usage is exceeded on the /, /home, /usr and/usr/omc/ne_data partitions of the system processor. The default value of the lower thresholdis 80 percent.

Use the following procedure to resolve the alarm:

Procedure 13-28 Resolving the LowerLimitDiskUsage (30011) alarm

1 Raise the value of the lower threshold limit (if less than 80 percent) inthe configuration file $OMC_TOP/config/global/FM_audit.CNFG.Refer to FM_audit.CNFG file for further details of theFM_audit.CNFG file.

2 Check the disk usage of all the partitions.

68P02901W19-S 13-79

Oct 2009

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 thesystem processor at the OMC-R. This fault condition may occur if the CPU load is high.Immediate action must be taken to reduce the CPU activity by expanding the lower CPU loadlimit.

If the CPU becomes overloaded, the OMC-R may not function correctly.

NOTEThe CPU load exceeds upper limit alarm indicates that the CPU is completelyoverloaded.

The following are possible causes for this alarm:

• The CPU load on the system processor has reached its maximum capacity.

• The upper limit threshold of the CPU load was lowered.

Use the following procedure to resolve the alarm:

Procedure 13-29 Resolving the CPU load exceeds lower limit (30061) alarm

1 Check the CPU load on the system processor.

2 Monitor the alarm, and if it does not clear, carry out furtherinvestigations to determine which processes are overloading the CPU.

3 Raise the value of the threshold CPU limit.

13-80 68P02901W19-S

Oct 2009

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 systemprocessor at the OMC-R. The CPU is completely overloaded.

Immediate action must be taken to reduce the CPU activity.

The following are the possible causes for this alarm:

• The CPU load on the system processor has reached maximum capacity.

• The upper limit threshold of CPU load was lowered.

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, and if it does not clear, carry out furtherinvestigations to see which processes are using too much CPU.

3 Raise the value of the threshold CPU load limit.

Memory usage exceeds lower limit (30063) alarm

An alarm is raised when the lower threshold limits for memory usage have been exceeded by thesystem processor at the OMC-R. Current memory usage is high, and requires that the memory ismade available by expanding the lower memory usage limit.

This fault condition could occur if the memory usage is high. Immediate action must be taken tofree up the memory. If the memory usage is too high, the OMC-R may not function correctly.

NOTEThe memory usage exceeding the upper limit alarm indicates that the memory iscompletely exhausted.

68P02901W19-S 13-81

Oct 2009

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.

• The upper limit threshold of memory usage was lowered.

Use the following procedure to resolve the alarm:

Procedure 13-31 Resolving the Memory usage exceeding the lower limit (30063)alarm

1 Check the memory usage on the system processor.

2 Monitor the alarm, and if it does not clear, carry out furtherinvestigations to see which processes are using too much memory.

3 Raise the value of the threshold memory usage limit.

Memory usage exceeds upper limit (30064) alarm

An alarm is raised when the upper threshold for memory usage has been exceeded by thesystem processor at the OMC-R. Memory is completely used up.

Immediate action must be taken to free up memory.

The following are possible causes for this alarm:

• Memory usage by the system processor has reached maximum capacity.

• The upper limit threshold of memory usage was lowered.

Use the following procedure to resolve the alarm:

Procedure 13-32 Resolving the Memory usage exceeds upper limit (30064) alarm

1 Check the memory usage on the system processor.

2 Monitor the alarm, and if it does not clear, carry out furtherinvestigations to see which processes are using too much memory.

3 Raise the value of the threshold memory usage limit.

13-82 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Database alarms

Database alarms

Three alarms are raised when the Performance Manager and the Event Manager aredisconnected from the database. Two of these are warnings that can lead to the major alarm30004 parserDisconnectedTooLong being generated if the cause of the alarm continues.

parserDisconnectedTooLong (30004) alarm

This alarm is raised when the parser has been disconnected from the OMC-R database forlonger than 10800 seconds.

Use the following procedure to resolve the alarm:

Procedure 13-33 Resolving the parserDisconnectedTooLong (30004) alarm

1 If omc_db_maint has finished executing, check the omc_db_maintlogs to see if the command db_disconnect connect parser has beenexecuted. If not, run this command:$DBMS_BIN/db_disconnect connect parser

2 Check to see if the Event Manager (EM) needs to be connected bytrying to create a subscription list. If this fails, enter the followingcommand:$DBMS_BIN/db_disconnect connect em

PMDisconnectedFromDB (30007)

This alarm is only a warning and is generated when the PM parser has been disconnectedas a part of routine database maintenance.

If the parser is disconnected from the database for a long time, the major alarm 30004parserDisconnectedTooLong is generated.

Refer to the corrective action for the alarm parserDisconnectedTooLong.

EMDisconnectedFromDB (30008)

This alarm is only a warning and is generated when the EM list manager has been disconnectedas part of routine database maintenance.

If the EM list manager is disconnected from the database for a long time, the major alarm30004 parserDisconnectedTooLong is generated. This usually means that the EM listmanager has not been reconnected after completion of maintenance.

Refer to the corrective action for the alarm parserDisconnectedTooLong.

68P02901W19-S 13-83

Oct 2009

Database alarms Chapter 13: Troubleshooting

Database exceeds upper limit (30014) alarm

An alarm is raised when the upper threshold of database usage have been exceeded by thesystem processor at the OMC-R. The database is completely full.

If the database space is full, action should be taken to free up space immediately. The OMC-Rmay 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 reachits maximum capacity.

• Check that the frequency of running the maintenance, and the database space allocationsare adequate.

• Check the upper/lower thresholds of the databases to verify that they are no longerexceeded. Raise the value of the threshold database limit (if lower than 90%).

Database exceeds lower limit (30019) alarm

An alarm is raised when the lower threshold limits of database usage have been exceeded by thesystem processor at the OMC-R. Current database usage is high, and requires that space bemade available by expanding the lower database limit.

This fault condition could occur if the database space usage is high. Action should be taken tofree up space in the database immediately. If the database becomes full, the OMC-R may notfunction correctly because it may not have the ability to write into the database.

NOTEThe database upper limit alarm indicates that the database is completely full.

The following are the possible causes for this alarm:

• The database usage by the system processor caused the database to reach its maximumcapacity.

• The various OMC-R databases are not being maintained properly.

• The various OMC-R databases are filling up too quickly for the defined maintenanceprocedures.

• The upper limit threshold of database usage was lowered.

NOTEThere is still room in the database. However, the OMC-R system administratorshould keep a close watch on the space used.

13-84 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration X.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, check the error reason field in the alarm message todetermine the cause(s) of this alarm.

2 Check the database usage in the system processor database to which the errorrelates.

3 Verify that the database maintenance procedures currently in operation complywith those recommended in this manual.

4 Raise the value of the threshold database limit (if lower than 90%).

5 Investigate the necessity of increasing the regularity (frequency) with which thevarious maintenance and archive scripts are run (or executed).

6 Review database space allocations to determine whether there is a spaceshortage. Determine where the shortage is located.

7 Check the upper/lower thresholds of the databases to verify that they are nolonger exceeded.

X.25 alarms

A Level123 Failure alarm is raised when there is a Layer1/Layer2/Layer3 failure on the systemprocessor X.25 line.

Use the following procedure to resolve the alarm:

Procedure 13-35 Resolving X.25 alarms

1 Check for related errors, for example, 30013solarisHardwareFailure.

2 Stop and start the X.25 on the link indicated by the alarm.Refer to Starting and stopping X.25 on page 9-9 for further details ofthe procedure to stop and start X.25.

3 Check the X.25 Network Interface Card.

4 Check that the physical link has not been removed or accidentally cut.

5 Check the X.25 log files.

6 Check the X.25 process state as follows:Determine the state of alarm VCs to all NEs.Login as root and enter the following command:/opt/SUNWconn/bin/x25stat -LThis shows the status of the connections.If no VCs exist, check the system processor X.25 NICs, packet switch,MUX and NE, following the above order.

7 If problems persist, contact the local Motorola office.

68P02901W19-S 13-85

Oct 2009

Hardware failure alarms Chapter 13: Troubleshooting

Hardware failure alarms

An alarm is raised when a system processor hardware unit is out of service.

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

2 Refer to the Sun System Administration manual for further informationon dealing with Sun hardware unit failure.

3 If problems persist, contact the local Motorola office.

OMC-R alarms

OMCOverloadedWithEvents (30021) alarm

The OMCOverloadedWithEvents alarm (30021) indicates the rate of events arriving at theOMC-R is too fast and a backlog of events is occurring.

Use the following procedure to resolve the alarm:

Procedure 13-37 Resolving the OMCOverloadedWithEvents (30021) alarm

1 Check the reason for the arrival of several events at the OMC-R. Ifthere are a large number of similar alarms, these particular alarmscould be throttled or blacklisted.

2 Check that a slow communication link to a GUI is not causing a backlogof events.

3 Check the performance of the system processor to see if it isfunctioning correctly.

13-86 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration OMC-R alarms

OMCOverloadedEventsDiscarded (30022 alarm)

The OMCOverloadedEventsDiscarded alarm (30022) indicates that too many events arefrequently arriving at the OMC-R and the events are discarded.

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. Ifthere are a large number of similar alarms, these particular alarmscould be throttled or blacklisted.

2 Check that a slow communication link to a GUI is not causing a backlogof events.

3 Check the performance of the system processor to see if it isfunctioning correctly.

Criticalstatseventsdiscarded (30078 alarm)

{34164}

The Criticalstatseventsdiscarded alarm (30078) is generated to notify OMC-R softwareapplications and operators that the number of critical statistics events has exceeded theestablished limit and is becoming overloaded with events that are discarded without processingor logging.

The following are the possible causes for this alarm:

• There are too many BSCs enabling the critical statistics reporting at a time.

• There are too many cells enabling the critical statistics reporting per BSC at a time.

Use the following procedure to resolve the alarm:

Procedure 13-39 Resolving the Criticalstatseventsdiscarded (30078 alarm)

1 Check the number of BSCs which enable the critical statistics reportingto ensure it is less than 30.

2 Check the number of cells of each BSC which enable the criticalstatistics reporting to ensure it is less than 90.

68P02901W19-S 13-87

Oct 2009

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 contains user defined values that are usedfor setting the FM audit timers and disk usage limits.

FM_audit.CNFG parameters

The FM_audit.CNFG file is read once a minute, consequently changes to this file do not requirethe OMC-R to be stopped and restarted.

An example of the FM_audit.CNFG configuration file for a High-End platform, showing therecommended 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

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

X.25 audit count = 1 minute.

System processor hardware audit count = 2 minutes.

Database audit count = 6 hours.

NOTEThe audit counts are the times between each audit (wait times) and do not include thetime taken to run the audits. Timings should be considered as estimates.

CPU audit count = 20 minutes.

Memory audit count = 20 minutes.

Usr partition lower limit = 80%.

Usr partition upper limit = 90%.

Ne_data partition lower limit = 80%.

Ne_data partition upper limit = 90%.

Root partition lower limit = 80%.

Root partition upper limit = 90%.

Home partition lower limit = 80%.

Home partition upper limit = 90%.

Raw statistics partition lower limit = 80%.

Raw statistics partition upper limit = 90%.

/tmp partition lower limit = 80%.

/tmp partition upper limit = 90%.

StorEdge Enterprise Backup partition lower limit = 80%.

StorEdge Enterprise Backup partition upper limit = 90%.

Database use lower limit on the system processor = 80%.

Database use upper limit on the system processor = 90%.

CPU load lower limit = 80%.

CPU load upper limit = 90%.

Memory use lower limit = 80%.

68P02901W19-S 13-89

Oct 2009

FM_audit.CNFG parameters Chapter 13: Troubleshooting

Memory use upper limit = 90%.

Remove cores count = 3.

Number of HSI ports = 8.

system processor CPU 0 ID number =10.

system processor CPU 1 ID number =11.

system processor CPU 2 ID number =14.

system processor CPU 3 ID number =15.

To change a FM audit timer or disk usage limit value, edit the appropriate line entry in the$OMC_TOP/config/global/FM_audit.CNFG file.

NOTEThe FM audit and disk usage limits should only be changed by qualified personnelunder guidance from Motorola Support. Contact Motorola Support for furtherinformation.

13-90 68P02901W19-S

Oct 2009

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. This sectiondescribes how to enable the neighbor statistics and the limitations that should be placed ontheir use.

Limitations on use of neighbor statistics

When performing optimization or fault finding work, it is recommended that the neighborstatistics should be enabled only on specific cells. When that work is complete, the statisticsshould be disabled.

Do not enable the neighbor statistics on more than 16 cells per BSS.

To automatically enable the neighbor statistics for specific cells using a cron job, use the CyclicNeighbor Statistics feature (PMCyclic).

Cyclic Neighbor Statistics feature (PMCyclic)

Neighbor statistics for a cell can be enabled automatically using the Cyclic Neighbor Statisticsfeature. This feature, also referred to as PMCyclic, enables neighbor statistics for cells inrotation, starting with cells that have the oldest date for the last enabled neighbor statistics.

The Cyclic Neighbor Statistics feature automatically enables the neighbor statistics for cells ina BSS in the following sequence:

• User-defined cells. The user creates a file listing the cells where the neighborstatistics are to be enabled. This file should be created in, and is read from,/usr/omc/ne_data/nha_nbrs/operator_nbr.

• NHA-defined cells. The Motorola NHA tool creates a file containing a list ofcell ids where the neighbor statistics are to be enabled. This file is read from/usr/omc/ne_data/nha_nbrs/nha_neighbours. When PMCyclic has used thisfile, it moves it to: /usr/omc/ne_data/nha_nbrs/nha_neighbours.previous. If a/usr/omc/ne_data/nha_nbrs/nha_neighbours file does not exist, PMCyclic uses/usr/omc/ne_data/nha_nbrs/nha_neighbours.previous.

68P02901W19-S 13-91

Oct 2009

Cyclic Neighbor Statistics feature (PMCyclic) Chapter 13: Troubleshooting

• If the environmental variable ENABLE_CYCLIC_NBRS is set to ON, and the maximumnumber of cells with the neighbor statistics enabled per BSS has not been exceeded, theCyclic phase of PMCyclic is run.

The Cyclic phase enables neighbor statistics for the cell with the oldest date in its LastDate Neighbor Statistics Enabled record, for each BSS in the network. For example, ifBSS8 Cell3 has 28/5/01 in its Last Date Neighbor Statistics Enabled record, and BSS8 Cell4has 28/3/01 in its Last Date Neighbor Statistics Enabled record, the Cyclic phase enablesneighbor statistics for Cell4. The Cyclic phase starts at the BSS associated with the firstcell id in the user-defined file, then in the NHA-defined file. The Cyclic phase then moveson to the next BSS in the network, and so on. This is also shown in the following table.

a. At the BSSs containing cells listed in the operator_nbr file.

b. At the BSSs containing cells listed in the nha_neighbours file.

c. In a cyclic pattern across other BSSs in the network.

The Cyclic phase limits the number of cells enabled up to 80% of the value ofPM_MAX_NEIGHBOURS divided by 16*32 (BSS Limit) in total. Once the BSS limit isexceeded, it is no longer possible to enable the neighbor statistics for 16 cells per BSS.

NOTEIf the same cells are always specified in the operator- and/or NHA-defined files,the same BSSs will always be selected in the Cyclic phase.

Maximum number of cells with enabled neighbor statistics per BSS

The maximum number of cells per BSS that can have the neighbor statistics enabled is 16. If theneighbor statistics for a cell cannot be enabled because this limit has already been exceeded,the Cell Id is recorded in the log file.

Running PMCyclic

PMCyclic is a cron job, which will run automatically each night. Each time PMCyclic is run, allcurrently enabled neighbor statistics are disabled.

Use the following procedure to run PMCyclic:

Procedure 13-40 Running PMCyclic

1 Login as omcadmin.

2 If required, create the file operator_nbr in/usr/omc/ne_data/nha_nbrs. Enter one GSM Cell Id or cell nameper line.

3 If required, create the NHA file using the NHA tool. See NHA manualfor further details.

Continued

13-92 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Neighbor statistics alarm

Procedure 13-40 Running PMCyclic (Continued)

4 If the Cyclic phase of PMCyclic is to be run, set the environmentvariable ENABLE_CYCLIC_NBRS to ON. Refer to User configurableenvironment variables on page 6-5 for further details.

5 To run PMCyclic, use the following command:setup_cyclic_nbr <no.>Where <no.> is the number of hours after which PMCyclic should berun.The following are valid values for <no.>: 6, 12, 24.For example, the following command runs PMCyclic every six hours(four times a day), that is, 24 hours divided by 6 equals 4:setup_cyclic_nbr 6To run PMCyclic once a day, use the following command:setup_cyclic_nbr

PMCyclic log file

The progress of PMCyclic is recorded in the following log file:

/usr/omc/logs/nbr_stats<YYYYMMDD>

The log file records the following information by grouping the cells according to whether theyare Operator Enabled Neighbor Statistics, NHA Enabled Neighbor Statistics, Cyclic EnabledNeighbor Statistics:

• Cell Id or name.

• Whether enabling of the neighbor statistics for a cell was a Success or a Failure.

The log file also records cells that could not be enabled because the maximum number ofcells per BSS limit had been reached.

This log file is deleted after 7 days by another cron job.

Neighbor statistics alarm

If too many neighbor statistics are enabled, the following alarm is generated:

30026. OMC: tooManyNeighbourStats

This alarm is generated when 70 percent of the space in the PM database allocated to theneighbor statistics, the nbr_statistics table, has been occupied by statistics. If the entirespace that is allocated has been used, neighbor statistics will be discarded to prevent thePM database from becoming full.

On receiving alarm 30026, take immediate steps to disable the unwanted neighbor statistics.

To avoid generating alarm 30026 the variable PM_MAX_NEIGHBOURS can be raised ifneighbor statistics are in use. This variable sets the size of the PM database space allocatedto neighbor statistics. Refer to User configurable environment variables on page 6-5 for acomplete description of this variable.

68P02901W19-S 13-93

Oct 2009

Raising the maximum limit of neighbor statistics Chapter 13: Troubleshooting

Raising the maximum limit of neighbor statistics

On a Low-Range OMC-R, the parser is able to process statistics for a maximum of 2800 neighborsper network in a 30 minute interval. In this case, the variable PM_MAX_NEIGHBOURS whichlimits the neighbor statistics can be increased to 2800.

On a Mid-Range OMC-R, the parser is able to process statistics for a maximum of 92160neighbors per network in a 30 minute interval. In this case PM_MAX_NEIGHBOURS can beincreased to 92160.

On a High-Range OMC-R, the parser is able to process statistics for a maximum of 18000neighbors per network in a 30 minute interval.

The procedure to change this limit is described in User configurable environment variables onpage 6-5.

The following additional checks and actions should also be performed:

• Monitor the nbr_statistics table.

• (Optionally) modify the sizes of the nbr_statistics and nbr_entity tables.

Monitoring the nbr_statistics table

The nbr_statistics table in the PM database may start to fragment due to the increase inthe neighbor statistics being stored. This should be monitored on an ongoing basis using thedb_cktab utility. Enter the following commands:

omc_env

db_cktab -d omc_db nbr_statistics

Modifying the database configuration files

The following database configuration files should also be modified to take into account theincreased number of neighbors:

/usr/omc/current/config/db_config.

Modifying the sizes of the nbr_statistics and nbr_entity tables

The following procedure modifies the extents of the nbr_statistics and nbr_entity tables. Thisprocedure is optional and there will be a slight improvement in the OMC-R performance. It willbe of most benefit if the nbr_statistics table is becoming excessively fragmented.

NOTEThe following procedures should only be carried out with the advice of a MotorolaEngineer.

Use the following procedure to modify the table sizes:

13-94 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Raising the maximum limit of neighbor statistics

Procedure 13-41 Modifying the sizes of the nbr_statistics and nbr_entity tables

1 Enter omc_env and press RETURN.

2 Obtain the sizes of the tables with the db_cktab command.db_cktab -d omc_db -t nbr_statistics;db_cktab -d omc_db -t nbr_entity;

3 omcadmin unloads both the tables using dbaccess. For moreinformation on dbaccess, see Using dbaccess.

4 Get the schema of both tables as follows:dbschema -t nbr_statistics -d omc_db nbr_stat.sqldbschema -t nbr_entity -d omc_db nbr_ent.sql

5 Drop both the tables from the database.

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.Ensure correct substitution of the table name being used.drop table nbr_statistics;drop table nbr_entity;

8 The sizes of the tables can be calculated in kilobytes by taking thenumber of pages for each table, obtained in step 3, and multiplyingit by 2.

9 Update the initial and next extent sizes in the schema files, as obtainedfrom step 4, with the values generated by step 8.

10 Recreate both tables as follows:dbaccess omc_db nbr_stat.sqldbaccess omc_db nbr_ent.sql

11 Reload each table as follows:omc_db_load_table -d omc_db nbr_statistics.unlomc_db_load_table -d omc_db nbr_entity.unlThis completes the resizing of the extents and reloading of both thetables.

68P02901W19-S 13-95

Oct 2009

Using dbaccess Chapter 13: Troubleshooting

Using dbaccess

Use the following procedure to use dbaccess:

Procedure 13-42 Using dbaccess

1 Ensure that the current directory is large enough to hold the unloadedtables. This can be done by checking the number of 2 K pages detailedin the output of step 2 inModifying the sizes of the nbr_statisticsand nbr_entity tables.

NOTEIf the files are unloaded to a directory that is too small,this may have an adverse effect on the performance of theOMC-R.

2 Enter the following:dbaccess omc_db -

3 Then enter the following command:unload to nbr_statistics.unl select * from nbr_statistics;

4 Finally, enter the following command:unload to nbr_entity.unl select * from nbr_entity;

5 To return to the operating system, press Ctrl-C.

13-96 68P02901W19-S

Oct 2009

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 onpage 2-57).

If this option is not used, then in the event of a power failure the system and GUI processorshave no graceful shutdown. This section provides procedures to recover from:

• Power failure on all machines on page 13-97.

• Power failure on the system processor on page 13-98.

• Power failure on a GUI processor on page 13-98.

Use the appropriate procedure in this section to recover from power failure where an UPSis not installed.

Power failure on all machines

In the event of a power failure on the system and GUI processors, turn off the power switches.

After power restore

To restart the system and GUI processors, the power switches must be turned on.

For information on powering on the system processor, see the particular Sun system manualfor the respective system Platform processor.

Restarting the OMC-R

When power has been restored to all machines, start the OMC-R.

Refer to Manual startup and shutdown of OMC-R software on page 7-12 for further details ofstarting and stopping the OMC-R software.

Restarting the GUI sessions

When the OMC Startup Complete message is displayed on the system processor console, eachuser may have to restart their GUI session.

If problems occur upon power restoration, contact the local Motorola representative.

68P02901W19-S 13-97

Oct 2009

Power failure on the system processor Chapter 13: Troubleshooting

Power supply unit failure

On the system and GUI processors, if the power supply unit fails, contact the local Motorolarepresentative immediately.

Power failure on the system processor

Access to the OMC-R software is not possible during a power failure on the system processor.

If the power to the system processor fails, perform the following procedure:

Procedure 13-43 Recovering from power failure on the system processor

1 Exit from the GUI sessions on the GUI processor.

2 When power is restored the system processor power switches mustbe turned on, and the OMC-R started. Refer to Manual startup andshutdown of OMC-R software on page 7-12 for further details ofstarting and stopping the OMC-R software.

3 Restart the GUI sessions when the OMC Startup Complete messageis displayed on the system processor console.

Power failure on a GUI processor

If a power failure occurs on a GUI client, it is not possible to run the GUI from this machine.

If a power failure occurs on a GUI server, it is not possible to run the GUI from this machine orany of its connected GUI clients.

It is still possible to manage and monitor the network as normal from all other machines. Allfeatures are available.

When the power is restored the machine reboots automatically. A GUI session may then bestarted on a GUI server and any of its connected GUI clients.

13-98 68P02901W19-S

Oct 2009

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. 805-7363-12) forexplanations of various LEDs on the Sunfire 4800.

Netra 20

Refer to Netra AC100/DC100 Services and System Reference Manual (Part No. 806-7336-12)for explanations of various LEDs on the Netra 20.

Netra 440

Refer to Netra 440 Server Service Manual (Part No. 817-3883-11) for explanations of variousLEDs on the Netra 440.

Displaying system processor status

The following command can be used to display the status and operating conditions of a SUNplatform:

/usr/platform/sun4u/sbin/prtdiag -v

The following example, shows a typical output text for this command.

Example

System Configuration: Sun Microsystems

sun4u 5-slot Sunfire 4800 System

clock frequency: 100 MHz Memory size:

2048 Mb =========================

CPUs =========================

Run Ecache CPU CPU Brd

CPU Module MHz MB Impl. Mask

--- --- ------- ----- ------ ------ ---- 3 6 0

400 8.0 US-II 10.0 3 7 1 400

8.0 US-II 10.0 7 14 0 400 8.0

US-II 10.0 7 15 1 400 8.0 US-II

10.0 ======================== Memory

68P02901W19-S 13-99

Oct 2009

Displaying system processor status Chapter 13: Troubleshooting

=========================

Intrlv. Intrlv. Brd Bank

MB Status Condition Speed Factor

With --- ----- ---- ------- ---------- ----- ------- --

----- 3 0 1024 Active OK 60 ns

2-way A 7 0 1024 Active OK

60 ns 2-way A ===================

====== IO Cards ====================

===== Bus Freq Brd Type MHz Slot

Name Model --- ---- ---- ------

---- ---------------------------- -------------------- 1

SBus 25 0 cgsix

SUNW,501-2253 1 SBus 25 1

HSI SUNW,501-1725-01 1

SBus 25 3 SUNW,hme 1 SBus

25 3 SUNW,fas/sd (block) 1 SBus

25 13 SUNW,socal/sf (scsi-3) 501-

3060 5 SBus 25 1 HSI

SUNW,501-1725-01 5 SBus 25

3 SUNW,hme 5 SBus 25 3 SUNW,

fas/sd (block) 5 SBus 25 13 SUNW,

socal/sf (scsi-3) 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 GREEN Normal

ON OFF BLINKING Fans: ----- Unit

Status ---- ------ Disk OK PPS OK System

Temperatures (Celsius): ------------------------------

Brd State Current Min Max Trend --- ------- -

------ --- --- ----- 1 OK 43 42 44 stable

3 OK 34 32 36 stable 5 OK 42

42 42 stable 7 OK 32 30 34 stable CLK

OK 38 38 39 stable Power Supplies: ------

--------- Supply Status ---------

------ 1 OK 3

OK PPS OK System 3.3v

OK System 5.0v OK Peripheral5.0v

13-100 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Displaying system processor status

OK Peripheral12v OK Auxilary 5.0v

OK Peripheral 5.0v precharge OK Peripheral

12v precharge OK System 3.3v precharge

OK System 5.0v precharge OK AC Power

OK ========================= HW

Revisions ==================== ASIC Revisions:

----------- Brd FHC AC SBus0 SBus1 PCI0 PCI1

FEPS Board Type Attributes --- --- -- ----- ----- ----

---- ---- ---------- ---------- 1 1 5 1 1

22 Dual-SBus-SOC+ 100 MHz Capable 3 1 5

CPU 100 MHz Capable 5 1

5 1 1 22 Dual-SBus-SOC+ 100 MHz

Capable 7 1 5 CPU 100

MHz Capable System Board PROM revisions: ----------

------------------ Board 1: FCODE 1.8.30 2002/10/25 14:02

iPOST 3.4.30 2002/10/25 14:03 Board 3: OBP 3.2.30

2002/10/25 14:03 POST 3.9.30 2002/10/25 14:04

Board 5: FCODE 1.8.30 2002/10/25 14:02 iPOST

3.4.30 2002/10/25 14:03 Board 7: OBP 3.2.30

2002/10/25 14:03 POST 3.9.30 2002/10/25 14:04

68P02901W19-S 13-101

Oct 2009

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 tosynchronize the time with the rest of the network.

To use a local LAN Timeserver, enter the IP address or the name of the Timeserver in the/etc/inet/ntp.conf file on the OMC-R. If a hostname is specified, either the DNS must beconfigured or the hostname must be added to /etc/inet/hosts.

To configure the OMC-R to use an NTP Timeserver, carry out the following procedure:

Procedure 13-44 Configuring the OMC-R to use an NTP Timeserver

1 As user root, edit the /etc/inet/ntp.conf file using a text editor. Add theappropriate entries to the ntp.conf file as shown below:

# The following lines were added to force this machine# to serve localtimeserver 127.127.1.1 prefer # LCL, local clockfudge 127.127.1.1 stratum 12 # increase stratum# peer timeserver prefer# Miscellaneous stuffdriftfile /etc/ntp.drift # path for drift file

2 Comment out the lines with # referring to LCL, local clock and increasestratum. Uncomment the lines referring to peer timeserver preferline substituting the IP address or the hostname of the Timeserver on thelocal LAN for timeserver. The ntp.conf file should now be similar to thefollowing example where somc1 is the hostname of the Timeserver on thelocal LAN:

# The following lines were added to force this machine# to serve localtime# server 127.127.1.1 prefer # LCL, local clock# fudge 127.127.1.1 stratum 12 # increase stratumpeer somc1 prefer# Miscellaneous stuffdriftfile /etc/ntp.drift # path for drift file

3 Stop the ntp daemon and restart byexecuting the following commands as user root:/etc/init.d/xntpd stop/etc/init.d/xntpd start

13-102 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Support for IP Multipathing in Solaris10/GSR9 on Sunfire platforms

Support for IP Multipathing in Solaris10/GSR9 onSunfire platforms

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

IP Multipathing is supported in Solaris10/GSR9 on Sunfire platforms. To configure IPmultipathing, complete the following as user root:

Procedure 13-45 Configuring IP Multipathing

1 Update the /etc/hostname.ce1 and /etc/hostname.ce3 files by addingthe following entries:

/etc/hostname.ce1

podge_priv netmask + broadcast + group ipmp2 up addif 10.50.50.22

netmask + broadcast + deprecated -failover up

/etc/hostname.ce3

10.50.50.21 netmask + broadcast + group ipmp2 deprecated

-failover standby up

2 Run the following commands as user root:ifconfig ce1 podge_priv netmask + broadcast + group ipmp2 upifconfig ce1 addif 10.50.50.22 netmask + broadcast + deprecated-failover upifconfig ce3 10.50.50.21 netmask + broadcast + group ipmp2deprecated -failover standby up

68P02901W19-S 13-103

Oct 2009

Support for IP Multipathing in Solaris10/GSR9 on Sunfire platforms Chapter 13: Troubleshooting

13-104 68P02901W19-S

Oct 2009

Chapter

14

Checklists■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

68P02901W19-S 14-1

Oct 2009

Overview Chapter 14: Checklists

Overview■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

This chapter provides copies of the various checklists, referred to in the rest of the manual.These lists can be copied and used to record checks and other information so that they can besaved for future reference.

The following checklists are provided in this chapter:

• General administration checklists on page 14-3.

General administration checklists on page 14-3.

Weekly administration checklist on page 14-5.

Monthly administration checklist on page 14-6.

• Checking cron jobs on page 14-7.

• Checking databases on page 14-10.

Checking databases on page 14-10.

Checklist for CM database on page 14-12.

• Checking X.25 connectivity on page 14-14.

• Checking core dumps on page 14-15.

• Checking disk usage on page 14-16.

• Checking disk mirroring on page 14-17.

• Checking for successful parsing of statistics on page 14-18.

• Recording details on page 14-20.

Setting up a night concentration centre on page 14-20.

Client and server partition details on page 14-21.

14-2 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration General administration checklists

General administration checklists■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Daily administration checklist

To check daily administration, follow the procedure in Daily administration checklist on page2-74. Copy the checklist in Table 14-1 to record the checks.

Table 14-1 Daily administration checklist

Check Method Checked?

Check the file systemcapacity.

Execute the following command as user root:df -kAny file systems with a 90-100% capacity must becleaned up for unwanted files or directories.

[-]

Check the disk usage capacityof the system.

Execute the following command as user root:du | moreTerminate processes that are not required and areconsuming disk capacity.

[-]

Check the output of cronmail jobs from user root,omcadmin and sys.

As user root, examine the output from the cronjobs in the following files for errors or messages:more /var/mail/omcadminmore /var/mail/rootmore /var/mail/sys

[-]

Check the omc_db_maint logfile to ensure the following:

• PM statistics older thana set timeframe aredeleted successfully.

• Disk space is not beingconsumed.

• Applications areconnected andreconnectedsuccessfully whenrequired.

Execute the following commands as user root:cd $OMC_TOP/logsmore omc_db_maint.yyyy.mm.dd

[-]

Check the IDS log files forboth PM and MIB INFORMIXDB errors and checkpointing.

Execute the following commands as useromcadmin:tail -f $INFORMIXDIR/online.log_OMCtail -f $INFORMIXDIR/online.log_MIBThese log files should show that checkpoints arecompleted successfully, in particular when theserver is initialized.

[-]

Continued

68P02901W19-S 14-3

Oct 2009

Daily administration checklist Chapter 14: Checklists

Table 14-1 Daily administration checklist (Continued)

Check Method Checked?

Check if the PM database isonline.

Execute the following commands as useromcadmin:omc_envonstat | more

[-]

Check if the CM database isonline.

Execute the following commands as useromcadmin:mib_envonstat | more

[-]

Perform a Level 2 backup ofthe PM database.

[-]

Perform a Level 2 backup ofthe CM database.

[-]

Perform a backup of the UNIXfilesystem.

Refer to Chapter 12 Backup Server Installationand Configuration.

[-]

Check the status of the diskmirroring and ensure allsubmirrors are in an OKstate.

Execute the following command as user root:metastat | moreRefer to Checking disk mirroring on page 14-17.

[-]

Check the OMC-R log filesin /usr/omc/logs for unusualoutput or error messages.

Refer to OMC-R log and error files on page 4-3. [-]

Check the integrity of x25. Execute the following command as user root:/opt/SUNWconn/bin/x25stat.See x25stat output on page 2-76.

[-]

Check the system processorhardware.

Execute the following command as user root:/usr/platform/sun4u/sbin/prtdiag -v.

[-]

Manually parse any unparsedstatistics files.

Refer to the checklist for manual parsing ofstatistics in NE database maintenance on page2-30.

[-]

14-4 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Weekly administration checklist

Weekly administration checklist

To check weekly administration, follow the procedure inWeekly administration checklist inChapter 2 System management. Copy the checklist in Table 14-2, to record the checks.

Table 14-2 Weekly administration checklist

Check Method Checked?

Check to see if theInformix online logs arerolled over successfully.

As user omcadmin, execute the following commands:cd /usr/informixls -l online.log_MIBls -l online.log_OMCEnsure that online logsexist with the format:online.log_MIB.ddmmyyyyonline.log_OMC.ddmmyyyy

[-]

Perform a backup of theUnix file system.

Refer to Chapter 12 Backup Server Installation andConfiguration.

[-]

Archive and remove oldOMC-R log files on thesystem processor andGUI servers.

As user root, execute the following command:/usr/omc/current/sbin/archive -r -d 7 -t/dev/rmt/0This archives all log files older than seven days to tapeand removes the files after they have been archived.

[-]

Archive and removeunloaded PM databasefiles on the systemprocessor.

As user root, 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 olderthan seven days.maintain_script -r -d 7/usr/omc/ne_data/raw_stats parsed\*This removes raw statistical bad header files olderthan seven days after the archive.

[-]

Check the file systemcapacity.

As user root, execute the following command:df -k

[-]

Check the disk usagecapacity of the system.

As user root, execute the following command:du |moreTerminate processes that are not required and areconsuming disk capacity.

[-]

Perform an archive of oldOMC-R user files.

As user root, execute the following commands:find /home -mtime +14 -print >/usr/tmp/listingtar -c /usr/tmp/listing /dev/rmt/0

[-]

Perform a Level 1 backupof the PM database.

[-]

Perform a Level 1 backupof the CM database.

[-]

System administratorshould monitor systemsecurity.

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

[-]

68P02901W19-S 14-5

Oct 2009

Monthly administration checklist Chapter 14: Checklists

Monthly administration checklist

To check monthly administration, follow the procedure inMonthly administration checklistin Chapter 2. Copy the checklist in Table 14-3, to record the checks.

Table 14-3 Monthly administration checklist

Check Method Checked?

Perform a backup of theUnix file system.

Refer to Chapter 12 Backup Server Installation andConfiguration.

[-]

Perform a Level 0 backupof the PM database.

[-]

Perform a Level 0 backupof the CM database.

[-]

Change the standardinstallation passwords foruser root, omcadmin,and informix, and informthe necessary people ofsuch changes.

Refer to Administering user accounts with usertoolon page 2-12.

[-]

Truncate the cron logfile.

As user root, execute the following commands:tail -100 /var/cron/log > /tmp/cron_logmv /tmp/cron_log /var/cron/log

[-]

14-6 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Checking cron jobs

Checking cron jobs■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

To check cron jobs, follow the procedure in Checking cron jobs on page 5-18 in Chapter 5. Copythe checklist in Table 14-4, to record the checks.

Table 14-4 Cron job checklist

Check Method Checked?

Check if the cron daemon isoperational on the system.

As user root, execute the following command:ps -elf | grep cronA /usr/sbin/cron process is displayed.

[-]

If the cron daemon is notoperational, it needs to bestarted.

As user root, execute the following commands:rm -f /etc/cron.d/FIFO/usr/sbin/cron

[-]

Check if the CRONLOGvariable is set to YES toensure cron logging is done.

As user root, execute the following command:more /etc/default/cron | grep CRONLOG

[-]

If the CRONLOG variable isset to NO, then it should bechanged.

As user root, edit the /etc/default/cron fileand change the CRONLOG setting to yes. Savethe file.

[-]

Check if the cron jobs aresetup correctly for user root.

As user root, execute the following command:crontab -l

[-]

Check if the cron jobs aresetup correctly for useromcadmin.

As user omcadmin, execute the followingcommand:crontab -l

[-]

Check if the system cronjobsare setup correctly.

As user sys, execute the following command:crontab -l

[-]

Check the /var/cron/log file toensure all crons executed arelogged to this file.

As user root, execute the following command:more /var/cron/log

[-]

Check if the /var/cron/log fileis rolled over to avoid diskspace issues.

As user root, execute the following commands:cd /var/cronls -lLog files should exist in the formatlog.ddmmyyyy

[-]

Check the output of root'scron jobs for any errors.

As user root, execute the following commands:cd /var/mailmore root | grep cronjobname

[-]

Check the output ofomcadmin's cron jobs forany errors.

As user root, execute the following commands:cd /var/mailmore omcadmin | grep cronjobname

[-]

Check the output of thesystem's cron jobs for anyerrors.

As user sys, execute the following commands:cd /var/mailmore sys | grep cronjobname

[-]

68P02901W19-S 14-7

Oct 2009

Checking OMC-R log files Chapter 14: Checklists

Checking OMC-R log files■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

To check the OMC-R log files, use the procedure in Chapter 4. Copy the checklist in Table 14-5,to record the checks.

Table 14-5 OMC-R log files checklist

Check Method Checked?

Check if omc log files arecreated in the correctdirectory paths.

On the system processor:

• OMC-R logs are placed in the /usr/omc/logsdirectory.

• Event logs are placed in the/usr/omc/ne_data/ev_logs directory.

• Informix logs are placed in the /usr/informixdirectory.

• OMC-R logs are placed in the /usr/omc/logsdirectory.

• 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/bsstail -50 bssname_yyyymmddAll command line activities performed on a particularBSS can be viewed.

[-]

Check the ConfigurationManagement log file.

As user omcadmin, execute the following commands:cd $OMC_TOP/logstail -50 cm_omcaudit_yyyymmddConfiguration Management activities are logged tothis file.

[-]

When a cutover has beenperformed, check thecutover log file to see if ithas been successful.

As user omcadmin, execute the following commands:cd $OMC_TOP/logsmore cutover.nnnnThis log file states whether the cutover has beensuccessful.

[-]

If problems areexperienced addingor updating statistics inthe PM database, thencheck for the existence ofdbms log files.

As user omcadmin, execute the following commands:cd $OMC_TOP/logsmore dbms.nnnnThis dbms log file contains error information.

[-]

Check thefpomcaudityyyymmddlog file for successfulparsing of statistics files.

As user omcadmin, execute the following command:tail -f $SYS_LOG/fpomcaudityyyymmdd

[-]

Continued

14-8 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Checking OMC-R log files

Table 14-5 OMC-R log files checklist (Continued)

Check Method Checked?

If problems occurwith Interprocesscommunication, thencheck if an IPC log fileexists in /usr/omc/logs/ipcdirectory.

As user omcadmin, execute the following commands:cd /usr/omc/logs/ipcmore ipclogfile nameThese log files are usually of the formatAF032959.0001 (Internet address id). This log fileshows an error report.

[-]

Check the omc_db_maintlog file to ensure thefollowing:

• PM statistics aredeleted successfully.

• Disk space is notbeing consumed.

• Applications areconnected andreconnectedsuccessfully whenrequired.

As user rootWilling, execute the followingcommands:cd $OMC_TOP/logsmore omc_db_maint.yyyy.mm.d

[-]

Check the systemstats files in/usr/omc/logs/sys_infofor system information.

Refer to OMC-R system information on page 13-8. [-]

Check the pmguiaudit logfile for errors relating topmgui.

As user omcadmin, execute the following commands:cd $OMC_TOP/logstail -50 pmguiaudityyyymmdd

[-]

Check the informixonline logs for DB errorsrelating to the PM andCM databases.

As user omcadmin, execute the following commands.For the PM DB:cd /usr/informixmore online.log_OMC.ddmmyyyyFor the CM DB:cd /usr/informixmore online.log_MIB.ddmmyyyy

[-]

Check the omcaudit logfor messages relating toOMC-R activity.

As user omcadmin, execute the following commands:cd /usr/omc/logstail -f omcaudityyyymmddRefer to Restartable processes in this chapter forfurther details about messages in the omc audit andconsole log.

[-]

Monitor the disk spaceused by the various logfiles.

As user omcadmin, monitor the output of themaintain_script cron job to ensure that it deleteslog files on a regular basis.cd /var/mailmore omcadmin | grep maintain_script

[-]

68P02901W19-S 14-9

Oct 2009

Checking databases Chapter 14: Checklists

Checking databases■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

Two checklists are provided in this section, one to check the PM database, and the otherto check the CM database.

Checklist for PM database

To check the PM database, follow the procedure in the section Checking the PM database onpage 8-34 in Chapter 8. Copy the checklist in Table 14-6, to record the checks.

Table 14-6 PM database checklist

Check Method Checked?

Check if the omc_envalias is setup.

cat the /usr/omc/current/env/.cshrc file and ensureit contains the following line: alias omc_env ‘source/usr/omc/config/global/pmInfxUserConfig.csh’.To run the updateLocalMaint script execute thefollowing command: setenv CM_LOCAL_MAINT TRUE.

[-]

Check if the PMdatabase is online.

As user omcadmin, enter the following:omc_envonstat | moreThis utility reports that the database is in online mode.

[-]

Check the IDS logfile for errors andcheckpointing.

As user omcadmin, execute the following command:tail -f $INFORMIXDIR/online.log_OMCThis log file shows that checkpoints are completedsuccessfully, in particular when the server is initialized.

[-]

Check if the IDS logfiles are rolled over.

As user omcadmin, execute the following commands:cd $INFORMIXDIRls -l online.log_OMC*Log files should exist of the formatonline.log_OMC.ddmmyyyy.

[-]

Check the output ofthe onmode_pm cronjob.

As user root, execute the following commands:cd /var/mailmore root | grep onmode_pm.

[-]

Continued

14-10 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Checklist for PM database

Table 14-6 PM database checklist (Continued)

Check Method Checked?

Check theomc_db_maint logfile to ensure thefollowing:

• PM statisticsare deletedsuccessfully.

• Disk spaceis not beingconsumed.

• Applicationsare connectedandreconnectedsuccessfullywhen required.

As user root, execute the following commands:cd $OMC_TOP/logsmore omc_db_maint.yyyy.mm.dd.

[-]

Check if the PMsqlhosts file has thecorrect entries forthe Informix Server.

As user omcadmin, execute the following command:more /usr/informix/etc/sqlhosts_OMCOutput should look similar to the example shown in PMsqlhosts in Chapter 8.

[-]

Check the/etc/services fileto ensure a portnumber exists for thePM IDS.

As user omcadmin, execute the following commands:more /etc/servicesAn entry should exist similar to the following:inf7_OMC_serv 5000/tcp

[-]

Check the sharedmemory structure ofthe PM IDS.

As user informix, execute the following command:onstat | moreOutput should be similar to that shown in onstat outputfor PM database section in Chapter 8.

[-]

Check the status ofthe dbspaces andchunks of the PMIDS.

As user informix, execute the following command:onstat -dOutput should be similar to that shown in onstat -doutput for PM database section in Chapter 8.

[-]

When performing anarchive of the PM DBensure the TAPEDEVparameter is set to/dev/rmt/0.

As user omcadmin, execute the following command:more /usr/informix/etc/onconfig | grep TAPEDEV.

[-]

68P02901W19-S 14-11

Oct 2009

Checklist for CM database Chapter 14: Checklists

Checklist for CM database

To check the CM database, follow the procedure in the section Checking the CM database onpage 8-39 in Chapter 8. Copy the checklist in Table 14-7, to record the checks.

Table 14-7 CM database checklist

Check Method Checked?

Check if themib_env aliasis setup.

cat the /usr/omc/current/env/.cshrc file and ensureit contains the following line: alias mib_env ‘source/usr/omc/config/global/mibInfxUserConfig.csh’To run the updateLocalMaint script execute the followingcommand: setenv CM_LOCAL_MAINT TRUE.

[-]

Check if theMIB databaseis online.

As user omcadmin, enter the following command:mib_envonstat | moreThis utility reports that the database is in online mode.

[-]

Check the IDS logfile for errors andcheckpointing.

As user omcadmin, execute the following command:tail -f $INFORMIXDIR/online.log_OMCThis log file should show that checkpoints are completedsuccessfully, in particular when the server is initialized.

[-]

Check if the IDSlog files are rolledover.

As user omcadmin, execute the following commands:cd $INFORMIXDIRls -l online.log_OMC*Log files should exist of the formatonline.log_OMC.ddmmyyyy

[-]

Check theoutput of theonmode_mib cronjob.

As user root, execute the following commands:cd /var/mailmore root | grep onmode_mib.

[-]

Check thedbspace andtblspaceallocation for theCM IDS.

As user omcadmin, execute the following commands:cd $DBMS_ROOT/SBINomc_db_ckspace mibThe output should be similar to that shown in the sectionomc_db_ckspace utility on page 8-10.

[-]

Check if the CMdatabase sqlhostsfile has thecorrect entriesfor the InformixServer.

As user omcadmin, execute the following command:more /usr/informix/etc/sqlhosts_MIBOutput should look similar to the example shown in thesection MIB sqlhosts file in Chapter 8.

[-]

Check the/etc/services fileto ensure a portnumber exists forthe CM IDS.

As user omcadmin, execute the following commands:more /etc/servicesAn entry should exist similar to the following:inf7_MIB_serv 5010/tcp.

[-]

Check the sharedmemory structureof the CM IDS.

As user informix, execute the following command:onstat | moreOutput should be similar to that shown in the section onstatoutput for CM database on page 8-41.

[-]

Continued

14-12 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Checklist for CM database

Table 14-7 CM database checklist (Continued)

Check Method Checked?

Check the statusof the dbspacesand chunks of theCM IDS.

As user informix, execute the following command:onstat -dOutput should be similar to that shown in the section onstat-d output for CM database on page 8-42.

[-]

When performingan archive of theCM DB ensurethe TAPEDEVparameter is setto /dev/rmt/0.

As user omcadmin, execute the following command:more /usr/informix/etc/onconfig | grep TAPEDEV.

[-]

68P02901W19-S 14-13

Oct 2009

Checking X.25 connectivity Chapter 14: Checklists

Checking X.25 connectivity■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

To check X.25 connectivity, follow the procedure in Checking X.25 connectivity on page 9-18 inChapter 9. Copy the checklist in Table 14-8 and use to record the checks.

Table 14-8 X.25 connectivity checklist

Check Method Checked?

Check the contents of thex25_config file.

As user root, execute the following command:cd /usr/omc/config/globalmore x25_configThe file contents should look like the example shownin Figure 9-2. The correct entries are required toconfigure x25 connections.

[-]

Check the integrity ofx25.

As user root, execute the following command:/opt/SUNWconn/bin/x25statRefer to x25stat output on page 2-76 for example,output.

[-]

Check the status of thenetwork.

As user root, execute the following command:/usr/bin/netstat -aRefer to OMC-R system information on page 13-8in Chapter 12. For example, output of the netstatcommand.

[-]

14-14 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Checking core dumps

Checking core dumps■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

To check core dumps, follow the procedure in Checking core dumps in Chapter 12. Copy thechecklist shown in Table 14-9 to record the checks.

Table 14-9 Core dumps checklist

Check Method Checked?

Check the presence ofa core file when a fatalerror occurs during theoperation of either theapplication programs orthe GUI modules.

As user root, execute the following commands:cd /usr/omc/logsls -l core*A core file should exist at the correct time the fatalerror occurred and should be in compressed format.

[-]

If an OMC-R process iscausing severe problems,generate a core file ofthe process.

As user root, execute the following command:gcore -o <filename> <process_id>where <filename> and <process_id> are of theparticular OMC-R process.

[-]

If the system processoris having some kernelproblems, then generatea core of the kernel.

[-]

Check the output of thecore_presence utility.

As user root, execute the following commands:cd /var/mailmore omcadmin | grep core_presenceIf a core file is generated, it exists in /usr/omc/logs.

[-]

Monitor oldcore files in the/usr/omc/logs/usrauditlogs directory.

As user root, monitor the core files in the/usr/omc/logsdirectory. If core files are not required, remove themas they consume large amounts of disk space.cd /usr/omc/logsrm -f corefilename

[-]

68P02901W19-S 14-15

Oct 2009

Checking disk usage Chapter 14: Checklists

Checking disk usage■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

To check disk usage, follow the procedure in Checking disk usage in Chapter 12. Copy thechecklist in Table 14-10, to record the checks.

Table 14-10 Disk usage checklist

Check Method Checked?

Check the disk usage ofthe system.

As user root, execute the following command:du -k | more

[-]

Remove files that are notrequired and use a lot ofdisk space, for example,old core files, log files,statistic files.

As user root, execute the following command:cd directorypathrm -f filename

[-]

Check the available freememory.

As user root, execute the following command:/usr/bin/sar -ru | more

[-]

Check whether the filesystems are full.

As user root, execute the following command:df -k | more

[-]

For file systems that areover 100% full, checkfor existing files thatare over 1 Mbyte andanalyze the possibility ofremoving such files.

As user root, execute the following command:find filesystem -size +1048576c -print | more

[-]

14-16 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Checking disk mirroring

Checking disk mirroring■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

To check disk mirroring, follow the procedure in Checking the CM database on page 8-39 inChapter 12. Copy the checklist in Table 14-11, to record the checks.

Table 14-11 Disk mirroring checklist

Check Method Checked?

Check the DiskSuitestatus.

As user root, execute the following command:metastatA stable set of disksuite mirrors should looksimilar to the example shown in the section metastatoutput on page 13-47.

[-]

Check for any subdisksthat require maintenanceusing the metastatcommand. Subdisksneeding maintenancehave to be repaired.

Refer to Logical Vol Mgr troubleshooting on page13-42 in Chapter 12 for the procedure to recovera lost disk.

[-]

Check if the system hasat least 3 state databaseson each mirror.

As user root, execute the following command: metadb [-]

If the system does nothave sufficient statedatabases, create them.

As user root, execute the following command:metadb -a -f slice-1 slice 2 etcFor example,metadb -f -d /dev/dsk/c1t2d0s3/dev/dsk/c2t2d0s3

[-]

68P02901W19-S 14-17

Oct 2009

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

As user omcadmin, execute the followingcommand:ps -elf | grep + | grep Parser

[-]

Check if the FMPATHenvironment variable isset.

As user omcadmin, execute the followingcommands:echo $FMPATHThis environment variable should be set to:/usr/omc/ne_data/raw_stats

[-]

Check if any raw statisticsfiles have escapedprocessing by the parser.

As user omcadmin, execute the followingcommands:/bin/find$OMC_TOP/ne_data/raw_stats/100,0-name “*.*“ -mtime +1 -print >/usr/tmp/parser_list

[-]

Submit any files foundby the find commandthat do not have asuffix of .bad_headeror fatal_header to theparser.

As user omcadmin, execute the followingcommand:$PM_ROOT/bin/pm_manual_parse filenameCheck for any error messages from thepm_manual_parse utility.

[-]

Check if the manual parsewas successful.

As user omcadmin, execute the followingcommand:tail -f $SYS_LOG/fpomcaudityyyymmddSuccessful parsing output is shown in Parsingoutput in Chapter 2.

[-]

Check that even if theParser process fails andis restarted, the statscollection and parsingresumes without manualintervention.

As user omcadmin, execute the followingcommand:tail -40 $SYS_LOG/fpomcaudityyyymmdd.The log file shows that files are being parsedagain successfully.

[-]

Check if the fpomcauditlogfile is rolled overand old log files areremoved successfullyby the maintain_scriptcronjob.

As user omcadmin, execute the followingcommand:cd /usr/omc/logsls -l fpomc*

[-]

Continued

14-18 68P02901W19-S

Oct 2009

Operating Information: OMC-R System Administration Checking for successful parsing of statistics

Table 14-12 Manual parsing of statistics checklist (Continued)

Check Method Checked?

If theparserDisconnectedTooLong alarm is raised thentheparser must be connectedto thedatabase.

As user omcadmin, execute the followingcommand:omc_envcd /usr/omc/current/sbindb_disconnectconnect parser

[-]

Monitor the value ofthe neighbor statisticsenvironment variable.

Refer to Using neighbor statistics on page 13-91in Chapter 12 for further details about rasingthe maximum limit of neighbor statistics.

[-]

68P02901W19-S 14-19

Oct 2009

Recording details Chapter 14: Checklists

Recording details■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

There are two procedures that require details of machines and accounts to be recorded andkept for future reference. They are Setting up a night concentration centre in Chapter 2,and Jump starting GUI server/client processor in Chapter 11.

Setting up a night concentration centre

The procedure to which these tables apply is described in Prerequisites for setup of a nightconcentration centre in Chapter 2.

Copy the following tables, enter the details and store the information safely.

Record the hostname and IP addresses of the different processors for each remote OMC-R inTable 14-13 and Table 14-14.

Table 14-13 Hostname and IP addresses for different processors

System Hostname IP address

local_sys

remote_sys

local_gui

Record the Username and User Identifier Number (UID) from the account of the user of theremote OMC-R system in Table 14-14.

Table 14-14 User name and ID for remote system

Account User name UID

Account for user or remoteOMC-R system

14-20 68P02901W19-S

Oct 2009

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/clientprocessor in Chapter 11.

Copy the following tables, enter the details and store the information safely.

Table 14-15 Client and server details

GUI client / server name GUI client / server IP address

Table 14-16 Filesystem, Log and JumpStart details

Filesystem Backup Log partitions JumpStart partitions

/

/usr/omc

/gen

68P02901W19-S 14-21

Oct 2009

Client and server partition details Chapter 14: Checklists

14-22 68P02901W19-S

Oct 2009

Index

Index■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

■

■

■

■

32000 statisticschecking for an excess . . . . . . . . . 8-32

3460 Fast'R modem . . . . . . . . . . . . . 3-7

A

ABORT_UPL_RL_IN_PROG . . . . . . . . . 6-6activity tools . . . . . . . . . . . . . . . 13-66ADDINFO_IN_HEX environment vari-able . . . . . . . . . . . . . . . . . . . . 6-13alarms . . . . . . . . . . . . . . . . . . 13-78database . . . . . . . . . . . . . . . . 13-83disk space usage . . . . . . . . . . . . 13-79hardware failure . . . . . . . . . . . . 13-86licence violation. . . . . . . . . . . . . 2-47log files . . . . . . . . . . . . . . . . . . 4-5neighbour statistics . . . . . . . . . . . 13-93OMC events . . . . . . . . . . . . . . . 13-86X.25. . . . . . . . . . . . . . . . . . . 13-85

all ports busy . . . . . . . . . . . . . . . 3-19AT commanddescription . . . . . . . . . . . . . . . 3-12for MultiModem. . . . . . . . . . . . . 3-16ATC_TIMEOUT environment variable . . . 6-10audit limits . . . . . . . . . . . . . . . . 13-88audit log fileschecking for success . . . . . . . . . . 4-11AUTORESYNC environment variable . . . 6-24AUTORESYNCDELAY environment vari-able . . . . . . . . . . . . . . . . . . . . 6-10AUTOSTART_PMGUI . . . . . . . . . . . . 6-6

B

Backing up the GUI Server File System . . 12-16Overview to backing up file systems usingbackup_MMI utility . . . . . . . . . . . 12-16Procedure for backing up file systems usingbackup_MMI utility . . . . . . . . . . . 12-17Backing up the PM and CM Databases . . 12-55Backing up the CM database . . . . . . 12-60Backing up the PM Database . . . . . . 12-57Checking and changing tape parame-ters . . . . . . . . . . . . . . . . . . . 12-55Default DAT tape parameters . . . . . . 12-55Level of backup . . . . . . . . . . . . . 12-55Monitoring the active message log files for theCM database . . . . . . . . . . . . . . 12-62

Backing up the PM and CM Databases (contd.)Monitoring the active message log files for thePM Database . . . . . . . . . . . . . . 12-59Overview of IDS message log files for the CMDatabase . . . . . . . . . . . . . . . . 12-61Overview of IDS message log files for the PMDatabase . . . . . . . . . . . . . . . . 12-58View Archived message log files for the CMDatabase . . . . . . . . . . . . . . . . 12-62View Archived message log files for the PMDatabase . . . . . . . . . . . . . . . . 12-59bootuptroubleshooting . . . . . . . . . . . . . 13-28

C

Call Success Monitoring . . . . . . . . . 6-23CALL_SUCCESS_THRESHOLD environmentvariable . . . . . . . . . . . . . . . . . . 6-23capacity control . . . . . . . . . . . . . . 2-46

Capacity control mechanism . . . . . . . 2-46CD-ROMeject failure . . . . . . . . . . . . . . . 13-50CDE. . . . . . . . . . . . . . . . . . 2-3, 13-33

68P02901W19-S IX-1

Oct 2009

Index

CDE (contd.)installing . . . . . . . . . . . . . . . . 13-33login failure . . . . . . . . . . . . . . . 13-36troubleshooting . . . . . . . . . . . . . 13-34ChecklistsCM database . . . . . . . . . . . 8-39, 14-12core dumps . . . . . . . . . . . . 13-7, 14-15daily administration. . . . . . . . . 2-74, 14-3disk mirroring. . . . . . . . . . . . . . 13-47disk usage. . . . . . . . . . . . 13-23, 14-16general administration . . . . . . . 2-74, 14-3manual parsing of statistics . . . . . . . 2-31monthly administration . . . . . . . 2-80, 14-6OMC log files . . . . . . . . . . . . 4-7, 14-8PM database . . . . . . . . . . . 8-34, 14-10weekly administration. . . . . . . . 2-79, 14-5X.25 connectivity . . . . . . . . . 9-18, 14-14Cleaning up OMC-R software loadskeeping software loads . . . . . . . . . 2-28reasons for cleaning up loads . . . . . . 2-28using a tarred software load . . . . . . 2-29CM databasechecking . . . . . . . . . . . . . . . . 8-39checking and recovering tables . . . . . 13-70defragmenting tables . . . . . . . . . . 13-73monitoring space and fragmentation . . 13-70onconfig file. . . . . . . . . . . . . . . 8-26reading the database scheme . . . . . . 13-73shutting down. . . . . . . . . . . . 8-18, 8-22starting up . . . . . . . . . . . . 8-21 to 8-22utilities . . . . . . . . . . . . . . . . . . 8-4CM sqlhosts file . . . . . . . . . . . . . . 8-40CM_NMC_AUTO_NUM environmentvariable . . . . . . . . . . . . . . . . . . 6-11CommentUser Management . . . . . . . . . . . 2-14Common Desktop EnvironmentCDE. . . . . . . . . . . . . . . . . . . . 2-3configuration files . . . . . . . . . . . . . 13-88FM_audit.CNFG file . . . . . . . . . . . 13-88X.25. . . . . . . . . . . . . . . . . . . . 9-3Configuring the OMC-R based LAN . . . . 1-24

Configuring the SunFire and Netra SystemProcessors . . . . . . . . . . . . . . . . . 1-9Connecting peripheralsSunFire 4800/4900 and Netra 20/440. . 1-11

Connecting to the LANLAN . . . . . . . . . . . . . . . . . . . 1-24core dumps . . . . . . . . . . . . . . . . 13-6checking . . . . . . . . . . . . . 13-7, 14-15removing . . . . . . . . . . . . . . . . 13-6running process. . . . . . . . . . . . . 13-6core_presence utilitycore_presence (omcadmin) . . . . . . . . 5-7corepresence utility . . . . . . . . . . . 13-6Country Codeuse in AT command . . . . . . . . . . . 3-14COUNTRY_CODE . . . . . . . . . . . . . . 6-6Create Home DirUser Management . . . . . . . . . . . 2-14critical processes . . . . . . . . . . . . . 2-49Criticalstatseventsdiscarded (30078alarm). . . . . . . . . . . . . . . . . . . 13-87cron jobsadding . . . . . . . . . . . . . . . 5-12, 5-15batch scheduler . . . . . . . . . . . . . . 5-9command line . . . . . . . . . . . . . . 5-14maintaining cron log files . . . . . . . . 5-16modifying . . . . . . . . . . . . . . . . 5-12omcadmin. . . . . . . . . . . . . . . . . 5-5on GUI Processors . . . . . . . . . . . . 5-5on the System Processor . . . . . . . . . 5-3removing . . . . . . . . . . . . . . 5-13, 5-16site_timesynch . . . . . . . . . . . . . 6-42system . . . . . . . . . . . . . . . . . . 5-5timesynch . . . . . . . . . . . . . . . . 6-41verifying . . . . . . . . . . . . . . . . 5-14crontab filesprinting . . . . . . . . . . . . . . . . . 5-17viewing . . . . . . . . . . . . . . . . . 5-14.cshrc.private file . . . . . . . . . . . . . . 6-3CSM_ENABLED environment variable . . 6-23CSMMAIN process . . . . . . . . . . . . 6-23CT_1208LOG . . . . . . . . . . . . . . . 6-11Cyclic Neighbour Statistics feature . . . . 13-91

D

daily procedurescore dump files . . . . . . . . . . . . . 1-29cron jobs . . . . . . . . . . . . . . . . 1-29database maintenance . . . . . . . . . 1-28OMC-R log files . . . . . . . . . . . . . 1-29System Processor hardware. . . . . . . 1-29UNIX file system maintenance . . . . . 1-29Database Applications menu . . . . . . . 2-19db_config files. . . . . . . . . . . . . . . 13-94db_disconnect utility . . . . . . . . . . . . 8-8

db_disconnect utility (contd.)dbdisconnect utility . . . . . . . . . . . 8-16db_pm_maint utilitydbpmmaint utility . . . . . . . . . . . . . 8-9environment variable used by . . . . . . 6-10dbms log files . . . . . . . . . . . . . 4-5, 13-52DEF_GSM_CELL_ID environment vari-able . . . . . . . . . . . . . . . . . . . . 6-16DetailSerial Port Manager. . . . . . . . . . . . 3-4

IX-2 68P02901W19-S

Oct 2009

Index

dial-in serial port . . . . . . . . . . . . . . 3-9Disabling status of Consolidated Alarms. . 6-30Disk Activity Tool . . . . . . . . . . . . . 13-66Disk Capacity Tool . . . . . . . . . . . . 13-67Disk configurationSunFire and Netra . . . . . . . . . . . 1-19disk mirroring

disk mirroring (contd.)checking . . . . . . . . . . . . 13-47, 14-17disk spacealarms . . . . . . . . . . . . . . . . . 13-79checking disk usage. . . . . . . 13-23, 14-16freeing up . . . . . . . . . . . . . . . . 13-21usage limits . . . . . . . . . . . . . . . 13-88

E

eeprom settings . . . . . . . . . . . . . . 3-22EMDisconnectedFromDB alarm. . . . . . 13-83ENABLE_AUTO_EMAIL_ON_REASSIGNenvironment variable . . . . . . . . . . . 6-16ENABLE_CYCLIC_NBRS environmentvariable . . . . . . . . . . . . . . . . . . 13-91ENABLE_CYCLIC_NBRS env . . . . . . . 6-6ENABLERESYNC environment variable. . 6-24enabling loginfor modems . . . . . . . . . . . . . . . 3-17environment variablemodifying . . . . . . . . . . . . . . . . 6-26environment variables . . . . . . . . . . 6-24ABORT_UPL_RL_IN_PROG . . . . . . . . 6-6ADDINFO_IN_HEX . . . . . . . . . . . 6-13ALG_WARNING . . . . . . . . . . . . . 6-13ATC_TIMEOUT . . . . . . . . . . . . . 6-10AU_APPLY_DELETES_FIRST . . . . . . 6-10AUTORESYNC . . . . . . . . . . . . . 6-24AUTORESYNCDELAY . . . . . . . . . . 6-10AUTOSTART_PMGUI . . . . . . . . 6-6, 6-15AX_LANG . . . . . . . . . . . . . . . . 6-15BSS_NAMING. . . . . . . . . . . . . . 6-15BSS_VER . . . . . . . . . . . . . . . . 6-15CALL_SUCCESS_THRESHOLD . . . . . 6-23CFG_KEEP_NMC_FILE . . . . . . . . . . 6-9CFG_KEEP_STATS_FILE . . . . . . . . . 6-9CM_NMC_AUTO_NUM . . . . . . . . . 6-11COUNTRY_CODE . . . . . . . . . . 6-6, 6-15CSM_ENABLED. . . . . . . . . . . . . 6-23DBNAME . . . . . . . . . . . . . . 6-11, 6-15DEF_GSM_CELL_ID. . . . . . . . . . . 6-16DEFAULT_RE-MOVE_CLEARED_ALARM . . . . . . . 6-16DEFAULT_RE-MOVE_CLEARED_ALARM_TIME . . . . 6-16DEL_CELLX_FILES . . . . . . . . . . . 6-11DOUBLE_CLICK_NEXT . . . . . . . . . 6-16ENABLE_AUTO_EMAIL_ON_REAS-SIGN . . . . . . . . . . . . . . . . . . 6-16ENABLE_CYCLIC_NBRS . . . . . . . . . 6-6ENABLERESYNC . . . . . . . . . . . . 6-24FM_CPU_AUDIT . . . . . . . . . . . . 6-22FM_IERROR_ALLOWED . . . . . . . . 6-22FM_MEM_AUDIT . . . . . . . . . . . . 6-22FM_OERROR_ALLOWED . . . . . . . . 6-22

environment variables (contd.)FM_OHUNG_ALLOWED . . . . . . . . 6-23INDFORMIXSERVER . . . . . . . . . . . 6-6INFORMIXDIR . . . . . . . . 6-6, 6-11, 6-16LANGUAGE . . . . . . . . . . . . . . . 6-16log files . . . . . . . . . . . . . . . . . . 4-6MAX_AUTO_RESYNCS . . . . . . . . . 6-24MAX_BOOTLOADS . . . . . . . . . . . . 6-6MAX_CSFP_BLP . . . . . . . . . . . . . 6-7MAX_UPLOADS_PER_CHAN . . . . . . . 6-7MIN_TOTAL_CS. . . . . . . . . . . . . 6-23MMI_ALARM_STATE_WIDTH . . . . . . 6-17MMI_CLEAR_INACTIVE_FMIC . . . 6-7, 6-17MMI_ENABLE_FMIC . . . . . . . . . . . 6-7MMI_EVENT_ADDI-TIONAL_INFO_WIDTH . . . . . . . . . 6-17MMI_EVENT_ID_WIDTH . . . . . . . . 6-17MMI_EVENT_INFO_WIDTH. . . . . . . 6-18MMI_EVENT_OBJ_CLASS_WIDTH . . . 6-18MMI_EVENT_OBJ_IN-STANCE_WIDTH . . . . . . . . . . . . 6-18MMI_EVENT_OPERA-TOR_NAME_WIDTH . . . . . . . . . . 6-18MMI_EVENT_TIME_WIDTH. . . . . . . 6-18MMI_EVENT_TYPE_WIDTH. . . . . . . 6-18MMI_EVT_FILTER_NUM_LOGS. . . . . 6-18MMI_START_WINDOW_AS_UNSPLIT . . 6-18NETWORK_CODE. . . . . . . . . . 6-7, 6-18NO_OF_PARSERS . . . . . . . . . . . . . 6-7NX_ENABLE_TIMESLOTS . . . . . . . 6-12OMC_TOP. . . . . . . . . . . 6-8, 6-12, 6-19OMCAUDIBLESEVERITY . . . . . . . . 6-19OMCFEATURES . . . . . . . . . . . . 6-19OMCREDRAW. . . . . . . . . . . . . . 6-19PER_SITE_AUDIT . . . . . . . . . . . . 6-12PER_SITE_AUDIT_DEBUG . . . . . . . 6-12PM_HOURLY_STATS . . . . . . . . . . . 6-8PM_MAX_NEIGHBOURS . . . . . . . . . 6-8PRINTER . . . . . . . . . . . . . . . . 6-19RECIPROCATE_NBR . . . . . . . . . . 6-13REGION. . . . . . . . . . . . . . . . . 6-19RL_LOGCMDS . . . . . . . . . . . . . 6-21RL_LOGRESPS . . . . . . . . . . . . . 6-21RL_SESSIONS . . . . . . . . . . . . . 6-21RL_TIMER_DT . . . . . . . . . . . . . 6-21RL_TIMER_NC . . . . . . . . . . . . . 6-22

68P02901W19-S IX-3

Oct 2009

Index

environment variables (contd.)SITE_NAMING . . . . . . . . . . . . . 6-20STATE_ON_AUDIT . . . . . . . . . . . . 6-9SUB_RES_TIME. . . . . . . . . . . . . . 6-9TIMER . . . . . . . . . . . . . . . . . 6-24TTY_FILTER. . . . . . . . . . . . . . . 6-20UPL_KEEP STATS_FILE. . . . . . . . . 6-10USE_LONG_SITE_NAME . . . . . . . . 6-13

/etc/dfs/dfstab file . . . . . . . . . . . . . 2-44/etc/hosts file . . . . . . . . . . . . . . . 13-38/etc/hosts.equiv file . . . . . . . . . . . . 13-38event alarms . . . . . . . . . . . . . . . 13-86event log files . . . . . . . . . . . . . . . . 4-5troubleshooting . . . . . . . . . . . . . 13-24

F

File Manager . . . . . . . . . . . . . . . 2-22file systemsfreeing space . . . . . . . . . . . . . . 13-21file transfersand modems . . . . . . . . . . . . . . 3-18FM_audit.CNFG file . . . . . . . . . . . . 13-88FM_CPU_AUDIT environment variable . . 6-22

FM_IERROR_ALLOWED environmentvariable . . . . . . . . . . . . . . . . . . 6-22FM_MEM_AUDIT environment variable. . 6-22FM_OERROR_ALLOWED environmentvariable . . . . . . . . . . . . . . . . . . 6-22FM_OHUNG_ALLOWED environmentvariable . . . . . . . . . . . . . . . . . . 6-23function keys . . . . . . . . . . . . . . . . 6-3

G

gcore command . . . . . . . . . . . . . . 13-6Graph Tool . . . . . . . . . . . . . . . . 13-53saving configurations . . . . . . . . . . 13-57Group IDGroup Management . . . . . . . . . . . . 2-9Group Management . . . . . . . . . . . . . 2-9adding . . . . . . . . . . . . . . . . . 2-10deleting . . . . . . . . . . . . . . . . . 2-11modifying . . . . . . . . . . . . . . . . 2-10Overview . . . . . . . . . . . . . . . . . 2-8renaming . . . . . . . . . . . . . . . . 2-10Group NameGroup Management . . . . . . . . . . . . 2-9

GUIensuring the correct colours appear . . 2-13

GUI processesenvironment variables . . . . . . . . . 6-13GUI Processorsprocesses . . . . . . . . . . . . 13-25, 13-27shutting down. . . . . . . . . . . . . . . 7-9single user mode . . . . . . . . . . . . . 7-9GUI serverrollback . . . . . . . . . . . . . . . . . 2-67GUI Serverlog files . . . . . . . . . . . . . . . . . . 4-5

H

Hard copy listings. . . . . . . . . . . . . 1-34hardware failure alarm . . . . . . . . . . 13-86history fileloading . . . . . . . . . . . . . . . . . 13-54home directoriesaccess failures . . . . . . . . . . . . . 13-34Horizontal Bar GraphGraph Tool . . . . . . . . . . . . . . . 13-61

host namechanging . . . . . . . . . . . . . . . . 11-8hosts file . . . . . . . . . . . . . . . . . 13-38hosts.equiv file . . . . . . . . . . . . . . 13-38HSI/S cardsreplacing . . . . . . . . . . . . . . 9-7, 9-17

I

INFORMIX database

IX-4 68P02901W19-S

Oct 2009

Index

INFORMIX database (contd.)alarms . . . . . . . . . . . . . . . . . 13-83CM database . . . . . . . . . . . . . . 8-13failure. . . . . . . . . . . . . . . . . . 13-52GUI Processor files . . . . . . . . . . . 8-15log files . . . . . . . . . . . . . . . . . . 4-5PM database . . . . . . . . . . . . . . 8-13Quiescent mode . . . . . . . . . . . . . 8-16routine procedures . . . . . . . . . 1-28, 1-30System Processor files . . . . . . . . . 8-14

INFORMIXDIR . . . . . . . . . . . . . . . 6-6INFORMIXSERVER . . . . . . . . . . . . . 6-6Installing a modem . . . . . . . . . . . . . 3-7Introduction to non user configurableenvironment variables . . . . . . . . . . 6-31Introduction to setting the status of theConsolidated Alarms . . . . . . . . . . . 6-29IPC log files . . . . . . . . . . . . . . . . . 4-6

L

LANfailure. . . . . . . . . . . . . . . . . . 13-38files . . . . . . . . . . . . . . . . . . . 13-38testing connection . . . . . . . . . . . 13-37LANGUAGE environment variable . . . . 6-16Level123Failure alarm . . . . . . . . . . 13-85Line PlotGraph Tool . . . . . . . . . . . . . . . 13-60Local GUI serverrollback . . . . . . . . . . . . . . . . . 2-67log book. . . . . . . . . . . . . . . . . . 1-26log filesalarm logs. . . . . . . . . . . . . . . . . 4-5audit . . . . . . . . . . . . . . . . . . 4-11dbms . . . . . . . . . . . . . . . . 4-5, 13-52environment variables . . . . . . . . . . 4-6

log files (contd.)event logs . . . . . . . . . . . . . . . . . 4-5INFORMIX database logs . . . . . . . . . 4-5IPC logs . . . . . . . . . . . . . . . . . . 4-6maintaining . . . . . . . . . . . . . . . . 5-6routine procedures . . . . . . . . . . . 1-29sys_info files . . . . . . . . . . . . . . 13-8logincorrupt message . . . . . . . . . . . . 3-24failure. . . . . . . . . . . . . . . . . . 13-36ids . . . . . . . . . . . . . . . . . . . 2-40password fails. . . . . . . . . . . . . . 3-24login prompttroubleshooting for modems . . . . . . 3-21LowerLimitDiskUsage alarm . . . . . . . 13-79lp command . . . . . . . . . . . . . . . . 3-27

M

maintain_script utility . . . . . . . . . . . . 5-6MAX_BOOTLOADS environment variable . . 6-6MAX_CSFP_BLP environment variable . . . 6-7MAX_UPLOADS_PER_CHAN environmentvariable . . . . . . . . . . . . . . . . . . . 6-7metricsselecting . . . . . . . . . . . . . . . . 13-58viewing . . . . . . . . . . . . . . . . . 13-59MIN_TOTAL_CS environment variable . . 6-23Miscellaneous daily procedures . . . . . . 1-29MMI processesGUI processes. . . . . . . . . . . . . . 6-13mmi utility . . . . . . . . . . . . . . . . . 7-4MMI_ALARM_STATE_WIDTH environmentvariable . . . . . . . . . . . . . . . . . . 6-17MMI_CLEAR_INACTIVE_FMIC environmentvariable . . . . . . . . . . . . . . . . 6-7, 6-17MMI_ENABLE_FMIC environment vari-able . . . . . . . . . . . . . . . . . . . . . 6-7MMI_EVENT_ADDITIONAL_INFO_WIDTHenvironment variable . . . . . . . . . . . 6-17

MMI_EVENT_ID_WIDTH environmentvariable . . . . . . . . . . . . . . . . . . 6-17MMI_EVENT_INFO_WIDTH environmentvariable . . . . . . . . . . . . . . . . . . 6-18MMI_EVENT_OBJ_CLASS_WIDTH environmentvariable . . . . . . . . . . . . . . . . . . 6-18MMI_EVENT_OBJ_INSTANCE_WIDTHenvironment variable . . . . . . . . . . . 6-18MMI_EVENT_OPERATOR_NAME_WIDTHenvironment variable . . . . . . . . . . . 6-18MMI_EVENT_TIME_WIDTH environmentvariable . . . . . . . . . . . . . . . . . . 6-18MMI_EVENT_TYPE_WIDTH environmentvariable . . . . . . . . . . . . . . . . . . 6-18MMI_EVT_FILTER_NUM_LOGS environmentvariable . . . . . . . . . . . . . . . . . . 6-18MMI_START_WINDOW_AS_UNSPLITenvironment variable . . . . . . . . . . . 6-18mnemonic process name . . . . . . . 2-55, 6-27modemadding . . . . . . . . . . . . . . . . . . 3-6communicating . . . . . . . . . . . . . 3-10

68P02901W19-S IX-5

Oct 2009

Index

modem (contd.)configuring . . . . . . . . . . . . . . . 3-10controlling access . . . . . . . . . . . . 3-11data links . . . . . . . . . . . . . . . . . 3-7disconnection problems . . . . . . . . . 3-23does not pick up . . . . . . . . . . . . 3-23eeprom settings . . . . . . . . . . . . . 3-22enabling login. . . . . . . . . . . . . . 3-17hangs up . . . . . . . . . . . . . . . . 3-22installing . . . . . . . . . . . . . . . . . 3-7permission denied. . . . . . . . . . . . 3-23physical connection . . . . . . . . . . . . 3-8rates . . . . . . . . . . . . . . . . . . . 3-8remote connection and file transfers . . 3-18setup . . . . . . . . . . . . . . . . . . 3-11SPARCstation setup . . . . . . . . . . . . 3-8tipping . . . . . . . . . . . . . . . . . 3-23

modem (contd.)troubleshooting . . . . . . . . . . . . . 3-19monitor_ct_logs utility . . . . . . . . . . . 5-7monitor_diskspace utility . . . . . . . . . . 5-7monthly procedures . . . . . . . . . . . . 1-32UNIX file system . . . . . . . . . . . . 1-32Motorolacontacting. . . . . . . . . . . . . . . . 13-3Motorola 3460 modem . . . . . . . . . . 3-12mounting a devicetroubleshooting . . . . . . . . . . . . . 13-49MT5634ZBA modem . . . . . . . . . . . 3-14MultiModem . . . . . . . . . . . . . . . 3-14multiuser modeGUI Processor . . . . . . . . . . . . . . 7-9System Processor . . . . . . . . . . . . . 7-9

N

nbr_entity tableresizing . . . . . . . . . . . . . . . . . 13-94nbr_statistics table . . . . . . . . . . . . 13-94resizing . . . . . . . . . . . . . . . . . 13-94NE database maintenancearchiving/removing an NE database . . 2-30PM database . . . . . . . . . . . . . . 2-30removing NE fallback software . . . . . 2-31routine procedures . . . . . . . . . . . 1-33NE maintenancesynchronizing times. . . . . . . . . . . 6-42neighbour statistics . . . . . . . . . . . . 13-91alarm . . . . . . . . . . . . . . . . . . 13-93enabling. . . . . . . . . . . . . . . . . 13-91enabling cyclically . . . . . . . . . . . 13-91limitations on use . . . . . . . . . . . . 13-91raising maximum limit . . . . . . . . . 13-94NEIGHBOUR variable. . . . . . . . . . . 13-94Netra System Processorconfiguring . . . . . . . . . . . . . . . . 1-9

Network File SystemNFS . . . . . . . . . . . . . . . . . . . 2-44network status . . . . . . . . . . . . . . 13-11NFS . . . . . . . . . . . . . . . . . . . . 2-44stale file handling . . . . . . . . . . . . 13-24NHA tool . . . . . . . . . . . . . . . . . 13-91Night concentration centreconfiguration . . . . . . . . . . . . . . 2-60naming conventions. . . . . . . . . . . 2-61prerequisites for setup . . . . . . 2-61, 14-20NIScommands . . . . . . . . . . . . 11-5, 11-11testing NIS server. . . . . . . . . . . . 11-10troubleshooting . . . . . . . . . . . . . 11-11NIS domainadding a group . . . . . . . . . . . . . 11-9adding a user . . . . . . . . . . . . . . 11-8no login prompt . . . . . . . . . . . . . . 3-21NX_ENABLE_TIMESLOTS environmentvariable . . . . . . . . . . . . . . . . . . 6-12

O

OMCcapacity . . . . . . . . . . . . . . . . . 2-46OMC event alarms . . . . . . . . . . . . 13-86OMC processes . . . . . . . . . . . . . . 13-27displaying . . . . . . . . . . . . . 7-13, 13-25errors . . . . . . . . . . . . . . . . . . 13-25printing . . . . . . . . . . . . . . . . . 2-35restarting . . . . . . . . . . . . . 2-49 to 2-50shutting down. . . . . . . . . . . . . . 7-12starting up . . . . . . . . . . . . . . . 7-12omc_db_ckspace utility

omc_db_ckspace utility (contd.)omcdbckspace utility . . . . . . . . . . 8-10omc_db_maint utilityautomatic (cron) procedure . . . . . . . 8-23omc_db_maint (root) . . . . . . . . . . . 5-8omcdbmaint utility . . 8-6 to 8-7, 8-23 to 8-24OMC-RJumpStart CD . . . . . . . . . . . . . . . 1-7software requirements . . . . . . . . . . 1-7OMC-R remote user accountsdeletion . . . . . . . . . . . . . . . . . 2-67

IX-6 68P02901W19-S

Oct 2009

Index

OMC-R usersuser accounts . . . . . . . . . . . . . . 1-33OMC_TOP environment variable . . . . . 6-19OMCAUDIBLESEVERITY environmentvariable . . . . . . . . . . . . . . . . . . 6-19OMCFEATURES environment variable . . 6-19OMCOverloadedEventsDiscardedalarm . . . . . . . . . . . . . . . . . . . 13-87OMCOverloadedWithEvents alarm . . . . 13-86OMCREDRAW environment variable . . . 6-19omctool utility. . . . . . . . . . . . . 2-55, 6-27onconfig file . . . . . . . . . . . . . . . . 8-26

onmode_mib utility . . . . . . . . . . . . . 5-7onmode_pm utility . . . . . . . . . . . . . 5-6onmonitor utility . . . . . . . . . . . 8-5, 8-16onperf_mib utility . . . . . . . . . . . . . 13-53onperf_pm utility . . . . . . . . . . . . . 13-53onstat -d output for CM database . . . . . 8-42onstat -d output for PM database . . . . . 8-37onstat output for CM database . . . . . . 8-41onstat output for PM database . . . . . . 8-35Operator workstations . . . . . . . . . . . 1-6Optional processors . . . . . . . . . . . . . 1-7

P

Packet Switch passwords . . . . . . . . . 2-43parserDisconnectedTooLong alarm . . . . 13-83passwordlogin failure . . . . . . . . . . . . . . . 3-24PasswordUser Management . . . . . . . . . . . 2-14passwords. . . . . . . . . . . . . . . . . 2-42conventions . . . . . . . . . . . . . . . 2-42Packet Switch . . . . . . . . . . . . . . 2-43routine procedures . . . . . . . . . . . 1-32permission denied or link down . . . . . . 3-23Pie ChartGraph Tool . . . . . . . . . . . . . . . 13-63PM databaseadding extra logical logs to DBserver . . . . . . . . . . . . . . . . . . 13-76checking . . . . . . . . . . . . . . . . 8-34checking and recovering tables . . . . . 13-70configuration files. . . . . . . . . . . . 13-94directory structures . . . . . . . . . . . 8-13emptying and defragmenting statisticstables . . . . . . . . . . . . . . . . . . 13-74maintenance . . . . . . . . . . 8-3, 8-6 to 8-7monitoring space and fragmentation . . 13-70onconfig file. . . . . . . . . . . . . . . 8-26reading the database schema . . . . . . 13-73shutting down. . . . . . . . . . . . 8-16, 8-22starting up . . . . . . . . . . . . . 8-19, 8-22status . . . . . . . . . . . . . . . . . . 13-14utilities . . . . . . . . . . . . . . . . . . 8-4PM raw statistics maintenance . . . . . . 1-33PM sqlhosts file . . . . . . . . . . . . . . 8-35PM statisticsparsing . . . . . . . . . . . . . . . 2-30, 8-11pm_manual_parse utility . . . . . . . . 8-11troubleshooting . . . . . . . . . . . 4-5, 13-52PM_HOURLY_STATS environment vari-able . . . . . . . . . . . . . . . . . . . . . 6-8

pm_manual_parse utility . . . . . . . . . 8-11PM_MAX_NEIGHBOURS environmentvariable . . . . . . . . . . . . . . . . . . . 6-8PMMAXNEIGHBOURS environmentvariable . . . . . . . . . . . . . . . . . 13-94PMCyclic . . . . . . . . . . . . . . . . . 13-91PMDisconnectedFromDB alarm. . . . . . 13-83port monitor services . . . . . . . . . . . . 3-9power failure . . . . . . . . . . . . . . . 2-57graceful shutdown . . . . . . . . . . . 2-57on all processors . . . . . . . . . . . . 13-97on GUI server and clients . . . . . . . . 13-98on the System Processor . . . . . . . . 13-98power supply unit failure . . . . . . . . 13-98restarting GUI sessions . . . . . . . . . 13-97restarting the OMC-R . . . . . . . . . . 13-97UPS . . . . . . . . . . . . . . . . . . . 13-98Primary GroupUser Management . . . . . . . . . . . 2-14Print Managerdisabling . . . . . . . . . . . . . . . . 13-34enabling. . . . . . . . . . . . . . . . . 13-34printeradding . . . . . . . . . . . . . . . . . 3-25address . . . . . . . . . . . . . . . . . 3-25checking installation . . . . . . . . . . 3-27configuration file . . . . . . . . . . . . 3-27configuring . . . . . . . . . . . . . . . 3-26name . . . . . . . . . . . . . . . . . . 3-25PRINTER environment variable . . . . . . 6-19printer.def file. . . . . . . . . . . . . . . 3-27printing . . . . . . . . . . . . . . . . . . 3-27processesOMC processes . . . . . . . . . . 2-49, 13-26processor timessynchronizing . . . . . . . . . . . . . . 6-36

68P02901W19-S IX-7

Oct 2009

Index

Q

Q3 naming . . . . . . . . . . . . . . . . 6-11Query Tree . . . . . . . . . . . . . . . . 13-65

Quiescent modeINFORMIX database . . . . . . . . . . 8-16

R

RC.CNFG file . . . . . . . . . . . . . . . 6-24REGION environment variable . . . . . . 6-19remote connection . . . . . . . . . . . . 3-18remote loginSPARCstation corruption . . . . . . . . 3-22Remote monitoring stationconfiguration . . . . . . . . . . . . . . 2-59restartable processes . . . . . . . . . . . 2-49ResyncCtrl process . . . . . . . . . . . . 6-24.rhosts filerhosts file . . . . . . . . . . . . . . . . 13-38RL_LOGCMDS environment variable . . . 6-21RL_LOGRESPS environment variable . . . 6-21RL_SESSIONS environment variable . . . 6-21RL_TIMER_DT environment variable . . . 6-21RL_TIMER_NC environment variable . . . 6-22RLOGIN variables. . . . . . . . . . . . . 6-21roll_online utility . . . . . . . . . . . . . . 5-7roll_paging_log utility . . . . . . . . . . . . 5-7

routine procedurescomplete file backup . . . . . . . . . . 1-33daily . . . . . . . . . . . . . . . . . . 1-28hardware maintenance . . . . . . . . . 1-34INFORMIX database . . . . . . . . 1-28, 1-30monthly . . . . . . . . . . . . . . . . . 1-32NE database maintenance . . . . . . . 1-33system configuration . . . . . . . . . . 1-34system core dumps . . . . . . . . . . . 1-34UNIX file system . . . . . . . . . . . . 1-32UNIX file systems . . . . . . . . . . . . 1-30weekly . . . . . . . . . . . . . . . . . 1-30Routine system administration proce-dures . . . . . . . . . . . . . . . . . . . 1-26RTF limit . . . . . . . . . . . . . . . . . 2-46updating licence . . . . . . . . . . . . 2-47run levels . . . . . . . . . . . . . . . . 7-3, 7-7Running Night Concentrationprocedure . . . . . . . . . . . . . . . . 2-66

S

sar_per_day utility . . . . . . . . . . . . . 5-7savecore utility . . . . . . . . . . . . . . 13-6Secondary GroupsUser Management . . . . . . . . . . . 2-14security . . . . . . . . . . . . . . . . 2-36, 2-44login ids. . . . . . . . . . . . . . . . . 2-41Security related weekly procedures. . . . 1-31serial port . . . . . . . . . . . . . . . . . . 3-3adding a modem . . . . . . . . . . . . . 3-6setting baud rate . . . . . . . . . . . . . 3-6Serial Port Manager. . . . . . . . . . . . . 3-3Session Activity Tool . . . . . . . . . . . 13-68Setting status of Consolidated Alarms . . 6-29Setting up a Night Concentration Centrecreating a new account . . . . . . . . . 2-64exporting file changes. . . . . . . . . . 2-64updating host file entries . . . . . . . . 2-63shutdown utility . . . . . . . . . . . . . 7-4, 7-7Single platform processorrollback . . . . . . . . . . . . . . . . . 2-68single user modeGUI Processor . . . . . . . . . . . . . . 7-9System Processor . . . . . . . . . . . . . 7-9site_timesynch utility

site_timesynch utility (contd.)site_timesynch (omcadmin) . . . . . . . . 5-8Software InstallationDeleting a Group Backup client . . . . . 12-11Enabling or Disabling a GroupBackup . . . . . . . . . . . . . . . . . 12-10software processesOMC processes . . . . . . . . . . . . . 13-25Solaris Logical Vol Mgr disk configurationtroubleshooting . . . . . . . . . . . . . 13-42SPARCstationcorruption. . . . . . . . . . . . . . . . 3-22setup . . . . . . . . . . . . . . . . . . . 3-8Status Tool . . . . . . . . . . . . . . . . 13-64StorEdge Enterprise Backuptroubleshooting . . . . . . . . . . . . . 13-51Style Manager . . . . . . . . . . . . . . 2-21subscription listsbacking up . . . . . . . . . . . . . . . 8-32subscriptionsbacking up . . . . . . . . . . . . . . . 8-32SunFire and Netradisk configuration . . . . . . . . . . . . 1-19SunFire System Processor

IX-8 68P02901W19-S

Oct 2009

Index

SunFire System Processor (contd.)configuring . . . . . . . . . . . . . . . . 1-9SunLink X.25 . . . . . . . . . . . . . . . . 9-3X.25. . . . . . . . . . . . . . . . . . . . 9-3swap spaceSystem Processor . . . . . . . . . . . . 13-14synchronizing processor times . . . . . . 6-36sys_info files . . . . . . . . . . . . . . . 13-8CM database status . . . . . . . . . . . 13-17network status . . . . . . . . . . . . . 13-11PM database status . . . . . . . . . . . 13-14system processes . . . . . . . . . . . . 13-9System Processor . . . . . . . . . . . . 13-8X.25 communications . . . . . . . . . . 13-10systat utility. . . . . . . . . . . . . . 5-6, 13-19system core dumpscore dumps . . . . . . . . . . . . . . . 13-6system processesOMC software processes . . . . . . . . 13-26sys_info files . . . . . . . . . . . . . . 13-9System Processor . . . . . . . . . . . . . . 1-4architecture. . . . . . . . . . . . . . . 13-9

System Processor (contd.)core . . . . . . . . . . . . . . . . . . . 13-6displaying status . . . . . . . . . . . . 13-99environment variables . . . . . . . . . 6-31hardware failure alarm . . . . . . . . . 13-86log files . . . . . . . . . . . . . . . . . . 4-3OMC-R specificationsSUN ULTRA ENTERPRISE 3000 . . . . 1-4processes . . . . . . . . 13-9, 13-25 to 13-26run level . . . . . . . . . . . . . . . . . 7-3shutting down. . . . . . . . . . . . . 7-6, 7-9single user mode . . . . . . . . . . . . . 7-9starting up . . . . . . . . . . . . . . 7-5, 7-9swap space . . . . . . . . . . . . . . . 13-14sys_info files . . . . . . . . . . . . . . 13-8system resources . . . . . . . . . . . . 13-12system resourcesSystem Processor . . . . . . . . . . . . 13-12system timesetting . . . . . . . . . . . . . . . . . 6-36synchronizing . . . . . . . . . . . . 6-36, 6-41system uptime . . . . . . . . . . . . . . 13-8

T

TemplateSerial Port Manager. . . . . . . . . . . . 3-4time zonesetting . . . . . . . . . . . . . . . . . 6-37TIMER environment variable . . . . . . . 6-24tipping a modem . . . . . . . . . . . . . 3-23

traffic channel capacityRTF limit . . . . . . . . . . . . . . . . 2-46troubleshootingfor modems . . . . . . . . . . . . . . . 3-19TTY_FILTER environment variable . . . . 6-20Typical hardware for OMC-R system . . . . 1-4

U

uname command . . . . . . . . . . . . . 13-9update_mib_statistics utility. . . . . . . . . 5-7UPL_KEEP_STATS_FILE environmentvariable . . . . . . . . . . . . . . . . . . 6-10UpperLimitDiskUsage alarm . . . . . . . 13-79UPS . . . . . . . . . . . . . . . . . 2-57, 13-98setup . . . . . . . . . . . . . . . . . . 2-58uptime . . . . . . . . . . . . . . . . . . 13-8user accountsadding . . . . . . . . . . . . . . . . . 1-33checking for old files . . . . . . . . . . 2-23deleting . . . . . . . . . . . . . . . . . 1-33user environmentcustomising . . . . . . . . . . . . . . . . 6-3User IDUser Management . . . . . . . . . . . 2-13

User Management . . . . . . . . . 2-12 to 2-13adding . . . . . . . . . . . . . . . . . 2-15deleting . . . . . . . . . . . . . . . . . 2-16modifying . . . . . . . . . . . . . . . . 2-15renaming . . . . . . . . . . . . . . . . 2-16User NameUser Management . . . . . . . . . . . 2-13user passwords . . . . . . . . . . . . . . 2-42user profileserrors . . . . . . . . . . . . . . . . . . 13-34User-configurable environment variables . . 6-5System processes and PMdatabase configurablevariables . . . . . . . . . . . . . . . . . 6-5usertool . . . . . . . . . . . . . . . . . . . 2-8/usr/gsm/logs/sys_info files . . . . . . . . 13-8utmpx entry . . . . . . . . . . . . . . . . 3-24

68P02901W19-S IX-9

Oct 2009

Index

V

Vertical Bar GraphGraph Tool . . . . . . . . . . . . . . . 13-62

Virtual Processor Activity Tool . . . . . . 13-69

W

weekly proceduresdatabase files . . . . . . . . . . . . . . 1-30

weekly procedures (contd.)UNIX file system . . . . . . . . . . . . 1-30

X

X.25 . . . . . . . . . . . . . . . . . . . . . 9-3alarm . . . . . . . . . . . . . . . . . . 13-85checking connectivity . . . . . . . . . . 9-18commands . . . . . . . . . . . . . . . . 9-7configuration . . . . . . . . . . . . . . . 9-3configuration files. . . . . . . . . . . . . 9-3directory structure . . . . . . . . . . . . 9-8failure. . . . . . . . . . . . . . . . . . 13-39integrity of X.25 communications . . . . 13-10LAPB configuration . . . . . . . . . . . 9-15OMC implementation . . . . . . . . . . . 9-5starting . . . . . . . . . . . . . . . 9-7, 9-11stopping. . . . . . . . . . . . . . . 9-7, 9-12

X.25 (contd.)updating link configuration . . . . . 9-7, 9-13X25from HSI failureRecovery . . . . . . . . . . . . . . . 9-19

x25_config file. . . . . . . . . . . . . . . . 9-3x25stat utility . . . . . . . . . . . . . . . 13-39x25tool . . . . . . . . . . . . . . . . . . . 9-9starting up x25tool . . . . . . . . . . . . 9-9starting X.25 . . . . . . . . . . . . . . 9-11stopping X.25 . . . . . . . . . . . . . . 9-12x25trace utility . . . . . . . . . . . . . . 13-39.Xdefaults.private file . . . . . . . . . . . . 6-3

IX-10 68P02901W19-S

Oct 2009