Upgrade Guide For 1.9.0.0.29

Software Release Notes: OMC-R System
1994 - 2008 Motorola, Inc. All Rights Reserved
68P02901W74-S
1.9.0.0.29
Mar 2008
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes no liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained herein. Motorola, Inc. reserves the right to make changes to any products described herein to improve reliability, function, or design, and reserves the right to revise this document and to make changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Motorola, Inc. does not assume any liability arising out of the application or use of any product, software, or circuit described herein; neither does it convey license under its patent rights or the rights of others. It is possible that this publication may contain references to, or information about Motorola products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that Motorola intends to announce such Motorola products, programming, or services in your country.
Copyrights
This document, Motorola products, and 3 Party Software products described in this document may include or describe copyrighted Motorola and other 3rd Party supplied computer programs stored in semiconductor memories or other media. Laws in the United States and other countries preserve for Motorola, its licensors, and other 3rd Party supplied software certain exclusive rights for copyrighted material, including the exclusive right to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly, any copyrighted material of Motorola, its licensors, or the 3rd Party software supplied material contained in the Motorola products described in this document may not be copied, reproduced, reverse engineered, distributed, merged or modified in any manner without the express written permission of Motorola. Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any license under the copyrights, patents or patent applications of Motorola or other 3rd Party supplied software, except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of a product. A list of 3rd Party supplied software copyrights are contained in the Supplemental information section of this document.
rd
Restrictions
Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, without prior written permission of Motorola, Inc.
License Agreements
The software described in this document is the property of Motorola, Inc and its licensors. It is furnished by express license agreement only and may be used only in accordance with the terms of such an agreement.
High Risk Materials

Components, units, or 3 Party products used in the product described herein are NOT fault-tolerant and are NOT designed, manufactured, or intended for use as on-line control equipment in the following hazardous environments requiring fail-safe controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft Communication Systems, Air Traffic Control, Life Support, or Weapons Systems (High Risk Activities). Motorola and its supplier(s) specifically disclaim any expressed or implied warranty of fitness for such High Risk Activities.
rd
Trademarks
MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners.
The CE mark confirms Motorola, Inc. statement of compliance with EU directives applicable to this product. Copies of the Declaration of Compliance and installation information in accordance with the requirements of EN50385 can be obtained from the local Motorola representative or by contacting the Customer Network Resolution Center (CNRC). The 24hour telephone numbers are listed at https://mynetworksupport.motorola.com.Select Customer Network Resolution Center contact information. Alternatively if you do not have access to CNRC or the internet, contact the Local Motorola Office.
1.9.0.0.29
Mar 2008
Table of Contents
Contents
Software Release Notes: OMC-R System Revision History..................................................................................................................................... 2 Version information......................................................................................................................... 2 Resolution of Service Requests ....................................................................................................... 2 Incorporation of Change Notices .................................................................................................... 2 General information ............................................................................................................................... 3 Purpose ........................................................................................................................................... 3 Cross references ............................................................................................................................. 3 Text conventions ............................................................................................................................. 4 Contacting Motorola .............................................................................................................................. 5 24 hour support............................................................................................................................... 5 Questions and comments ................................................................................................................ 5 Errors .............................................................................................................................................. 5 Security Advice ...................................................................................................................................... 6 Warnings, cautions, and notes ............................................................................................................... 7 Warnings ......................................................................................................................................... 7 Cautions .......................................................................................................................................... 7 Notes ............................................................................................................................................... 7 Safety ..................................................................................................................................................... 8 General safety ................................................................................................................................. 8 Electromagnetic energy .................................................................................................................. 8 Caring for the environment ................................................................................................................... 9 In EU countries ............................................................................................................................... 9 In non-EU countries ........................................................................................................................ 9 CMM labeling and disclosure table ..................................................................................................... 10 Motorola document set ........................................................................................................................ 11 Ordering documents and CD-ROMs .............................................................................................. 11 Document banner definitions ........................................................................................................ 11 Data encryption ............................................................................................................................. 11 Third Party computer software and trademarks.................................................................................. 12 Computer Software ....................................................................................................................... 12 Trademarks ................................................................................................................................... 12
Chapter 1 About this release ................................................................................... 1-1

General information about the release notes...................................................................................... 1-2 Introduction.................................................................................................................................. 1-2
68P02901W74-S Mar 2008
1.9.0.0.29
Contents
Chapter descriptions .................................................................................................................... 1-2 Nomenclature, release load identification ................................................................................... 1-2 Deliverables: DVD-ROMs .................................................................................................................... 1-3 Media ........................................................................................................................................... 1-3 New features in 1.9.0.0.29.................................................................................................................. 1-4 New features in OMC-R ............................................................................................................... 1-4 New statistics in 1.9.0.0.29................................................................................................................. 1-6 Statistics modified in 1.9.0.0.29 ......................................................................................................... 1-8
Chapter 2 Open issues..............................................................................................2-1

Open issues......................................................................................................................................... 2-2 Overview ...................................................................................................................................... 2-2 Service affecting (P1) ................................................................................................................... 2-2 Serious (P2).................................................................................................................................. 2-2 Low priority (P3) .......................................................................................................................... 2-2 Information provided.................................................................................................................... 2-3 Open issues listing .............................................................................................................................. 2-4 Open P1 (service affecting) SRs.......................................................................................................... 2-6 Open P2 (serious) SRs ........................................................................................................................ 2-7 SR 843068 .................................................................................................................................... 2-7 SR 953935 .................................................................................................................................... 2-7 SR 986629 .................................................................................................................................... 2-8 SR 1013247 .................................................................................................................................. 2-9 SR 1028815 .................................................................................................................................. 2-9 Open P3 (annoying) SRs ................................................................................................................... 2-11 SR 785800 .................................................................................................................................. 2-11 SR 793917 .................................................................................................................................. 2-11 SR 801466 .................................................................................................................................. 2-12 SR 924436 .................................................................................................................................. 2-13 SR 927080 .................................................................................................................................. 2-13 SR 927396 .................................................................................................................................. 2-14 SR 933593 .................................................................................................................................. 2-14 SR 953037 .................................................................................................................................. 2-15 SR 966247 .................................................................................................................................. 2-16 SR 966277 .................................................................................................................................. 2-16 SR 970404 .................................................................................................................................. 2-17 SR 975526 .................................................................................................................................. 2-18 SR 976242 .................................................................................................................................. 2-18 SR 979854 .................................................................................................................................. 2-19 SR 981119 .................................................................................................................................. 2-19 SR 982303 .................................................................................................................................. 2-20
68P02901W74-S
ii
1.9.0.0.29
Mar 2008
Contents
SR 982322 .................................................................................................................................. 2-21 SR 982885 .................................................................................................................................. 2-21 SR 982898 .................................................................................................................................. 2-22 SR 983646 .................................................................................................................................. 2-22 SR 990661 .................................................................................................................................. 2-23 SR 992326 .................................................................................................................................. 2-23 SR 992935 .................................................................................................................................. 2-24 SR 995685 .................................................................................................................................. 2-24 SR 997420 .................................................................................................................................. 2-25 SR 997957 .................................................................................................................................. 2-26 SR 1000467 ................................................................................................................................ 2-27 SR 1010601 ................................................................................................................................ 2-27 SR 1007649 ................................................................................................................................ 2-28 SR 1010203 ................................................................................................................................ 2-29 SR 1012726 ................................................................................................................................ 2-29 SR 1013313 ................................................................................................................................ 2-30 SR 1013317 ................................................................................................................................ 2-31 SR 1023792 ................................................................................................................................ 2-31 SR 1027636 ................................................................................................................................ 2-32
Chapter 3 Resolved issues ....................................................................................... 3-1

Resolved issues listing ........................................................................................................................ 3-2 SR 927975 .................................................................................................................................... 3-2 SR 929496 .................................................................................................................................... 3-2 SR 996185 .................................................................................................................................... 3-2 SR 996258 .................................................................................................................................... 3-2 SR 997353 .................................................................................................................................... 3-2 SR 997430 .................................................................................................................................... 3-2 SR 997957 .................................................................................................................................... 3-2 SR 998042 .................................................................................................................................... 3-3 SR 998712 .................................................................................................................................... 3-3 SR 999631 .................................................................................................................................... 3-3 SR 1000429 .................................................................................................................................. 3-3 SR 1005026 .................................................................................................................................. 3-3 SR 1005296 .................................................................................................................................. 3-3 SR 1005391 .................................................................................................................................. 3-3 SR 1006580 .................................................................................................................................. 3-3 SR 1008403 .................................................................................................................................. 3-4
Chapter 4 Compatibility ........................................................................................... 4-1

OMC-R systems supported by this release.......................................................................................... 4-2 OMC-R BSS compatibility................................................................................................................. 4-3
68P02901W74-S Mar 2008
1.9.0.0.29
iii
Contents
Jumpstart ............................................................................................................................................ 4-5 M-Cell compatibility............................................................................................................................ 4-6
Chapter 5 Hardware and firmware requirements .....................................................5-1

Hardware and firmware requirements ............................................................................................... 5-2 Hardware requirements summary ............................................................................................... 5-2
Chapter 6 Software management .............................................................................6-1

Software installation ........................................................................................................................... 6-2 Introduction.................................................................................................................................. 6-2 Pre-upgrade, upgrade and rollback procedures........................................................................... 6-2 Clean install procedures............................................................................................................... 6-2 Open issues affecting upgrade/installation .................................................................................. 6-2 Upgrade requirements........................................................................................................................ 6-3 Introduction.................................................................................................................................. 6-3 Impact and interaction ................................................................................................................. 6-3 Feature traceability...................................................................................................................... 6-3
Chapter 7 MMI changes............................................................................................7-1

MMI changes introduced in GSR9 ...................................................................................................... 7-2 Commands .......................................................................................................................................... 7-3 New commands ............................................................................................................................ 7-3 Modified commands ..................................................................................................................... 7-3 Deleted commands ....................................................................................................................... 7-4 Parameters.......................................................................................................................................... 7-5 New parameters........................................................................................................................... 7-5 Modified parameters .................................................................................................................... 7-6 Deleted parameters...................................................................................................................... 7-7 Alarms................................................................................................................................................. 7-8 New alarms .................................................................................................................................. 7-8 Modified alarms ........................................................................................................................... 7-9 Deleted alarms ............................................................................................................................. 7-9 Statistics ........................................................................................................................................... 7-10 New statistics ............................................................................................................................. 7-10 Modified statistics ...................................................................................................................... 7-11 Deleted statistics ........................................................................................................................ 7-12 Timers ............................................................................................................................................... 7-13 New timers ................................................................................................................................. 7-13 Modified timers .......................................................................................................................... 7-13 Deleted timers ............................................................................................................................ 7-13
68P02901W74-S
iv
1.9.0.0.29
Mar 2008
List of Tables
List of Tables
Table 1-1 New features in OMC-R 1.9.0.0.29 release............................................................................... 1-4 Table 1-2 New features in OMC-R ............................................................................................................ 1-4 Table 2-1 Information provided on open issues ........................................................................................ 2-3 Table 2-2 Open issues reported in GSR9 1.9.0.0.29 ................................................................................. 2-4 Table 4-1 GSR9 1.9.0.0 BSS/OMC-R/DataGen System Service Packs ...................................................... 4-3 Table 4-2 GSR9 and GSR8 BSS loads compatible with GSR9 1.9.0.0.29 OMC-R load.............................. 4-4
68P02901W74-S Mar 2008
1.9.0.0.29
List of Tables
68P02901W74-S
vi
1.9.0.0.29
Mar 2008
About This Manual
This manual provides an overall description of the features, changes and enhancements that are provided with release GSR9 1.9.0.0.29 for the OMC-R.
68P02901W74-S Mar 2008
1.9.0.0.29
Revision History
Revision History
Version information
The following table lists the versions of this manual in order of manual issue: Manual issue Q R S Date of issue Apr 2005 Jun 2007 Mar 2008 Remarks Issue Q - GSM Software Release 7 Half Rate Issue R - GSM Software Release 8 Issue S - GSM Software Release 9 (1.9.0.0.29)
Resolution of Service Requests

The following Service Requests are now resolved in this manual: Service Request NA CMBP Number NA Remarks NA
Incorporation of Change Notices

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

Special key sequences are represented as follows: CRTL-c or CTRL+C CTRL-SHIFT-c or CTRL+SHIFT+C ALT-f or ALT+F ALT+SHIFT+F11 | RETURN or ENTER Press the Ctrl and C keys at the same time. Press the Ctrl, Shift, and C keys at the same time. Press the Alt and F keys at the same time. Press the Alt, Shift, and F11 keys at the same time. Press the pipe symbol key. Press the Return or Enter key.
68P02901W74-S
1.9.0.0.29
Mar 2008
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, please contact the Customer Network Resolution Center (CNRC) for immediate assistance. The 24-hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center contact information. Alternatively if you do not have access to CNRC or the internet, contact the Local Motorola Office.
Questions and comments

Send questions and comments regarding user documentation to the email address: mydocs@motorola.com.
Errors
To report a documentation error, call the CNRC (Customer Network Resolution Center) and provide the following information to enable CNRC to open an SR (Service Request): the document type the document title, part number, and revision character the page number(s) with the error a detailed description of the error and if possible the proposed solution
68P02901W74-S Mar 2008
1.9.0.0.29
Security Advice
Security Advice
Motorola systems and equipment provide security parameters that can be configured by the operator based on their particular operating environment. Motorola recommends setting and using these parameters following industry recognized security practices. Security aspects to be considered are protecting the confidentiality, integrity, and availability of information and assets. Assets include the ability to communicate, information about the nature of the communications, and information about the parties involved. In certain instances Motorola makes specific recommendations regarding security practices, however the implementation of these recommendations and final responsibility for the security of the system lies with the operator of the system. Please contact the Customer Network Resolution Center (CNRC) for assistance. The 24 hour telephone numbers are listed at https://mynetworksupport.motorola.com/. Select Customer Network Resolution Center contact information, from the menu located to the left of the Login box. Alternatively if you do not have access to CNRC or the internet, contact the Local Motorola Office.
68P02901W74-S
1.9.0.0.29
Mar 2008
Warnings, cautions, and notes
Warnings, cautions, and notes

The following describes how warnings and cautions are used in this document and in all documents of this Motorola document set.
Warnings
Warnings precede instructions that contain potentially hazardous situations. Warnings are used to alert the reader to possible hazards that could cause loss of life or physical injury. A warning has the following format:
Warning text and consequence for not following the instructions in the warning.
Cautions
Cautions precede instructions and are used when there is a possibility of damage to systems, software, or individual items of equipment within a system. However, this damage presents no danger to personnel. A caution has the following format:
Caution text and consequence for not following the instructions in the caution.
Notes
A note means that there is a possibility of an undesirable situation or provides additional information to help the reader understand a topic or concept. A note has the following format:
Note text.
68P02901W74-S Mar 2008
1.9.0.0.29
Safety
Safety
General safety
The following general safety guidelines apply to Motorola equipment: The power jack and mating plug of the power cable must meet International Electrotechnical Commission (IEC) safety standards.
Refer to Grounding Guideline for Cellular Radio Installations 68P81150E62. Power down or unplug the equipment before servicing. Using non-Motorola parts for repair could damage the equipment or void warranty. Contact Motorola Warranty and Repair for service and repair instructions. Portions of Motorola equipment may be damaged from exposure to electrostatic discharge. Use precautions to prevent damage.
Electromagnetic energy
Relevant standards (USA and EC) applicable when working with RF equipment are::
ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.
Council recommendation of 12 July 1999 on the limitation of exposure of the general public to electromagnetic fields (0 Hz to 300 GHz) (1999/519/EC) and respective national regulations. on the minimum health and safety requirements regarding the exposure of workers to the risks arising from physical agents (electromagnetic fields) (18th individual Directive within the meaning of Article 16(1) of Directive 89/391/EEC).
Directive 2004/40/EC of the European Parliament and of the Council of 29 April 2004
68P02901W74-S
1.9.0.0.29
Mar 2008
Caring for the environment
Caring for the environment

The following information describes national or regional requirements for the disposal of Motorola supplied equipment and for the approved disposal of surplus packaging. Contact the Customer Network Resolution Center (CNRC) for assistance. The 24hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center contact information. Alternatively if you do not have access to CNRC or the internet, contact the Local Motorola Office.
In EU countries
The following information is provided to enable regulatory compliance with the European Union (EU) directives identified and any amendments made to these directives when using Motorola equipment in EU countries.
Disposal of Motorola equipment

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

Do not dispose of surplus packaging in landfill sites. In the EU, it is the individual recipients responsibility to ensure that packaging materials are collected and recycled according to the requirements of EU environmental law.
In non-EU countries
In non-EU countries, dispose of Motorola Networks equipment and all surplus packaging in accordance with national and regional regulations.
68P02901W74-S Mar 2008
1.9.0.0.29
CMM labeling and disclosure table
CMM labeling and disclosure table

The Peoples Republic of China require that our products comply with China Management Methods (CMM) environmental regulations. (China Management Methods refers to the regulation Management Methods for Controlling Pollution by Electronic Information Products.) Two items are used to demonstrate compliance; the label and the disclosure table. The label is placed in a customer visible position on the product. Logo 1 means the product contains no substances in excess of the maximum concentration value for materials identified in the China Management Methods regulation. Logo 2 means that the product may contain substances in excess of the maximum concentration value for materials identified in the China Management Methods regulation, and has an Environmental Friendly Use Period (EFUP) in years, fifty years in the example shown.
Logo 1
Logo 2
The Environmental Friendly Use Period (EFUP) is the period (in years) during which the Toxic and Hazardous Substances (T&HS) contained in the Electronic Information Product (EIP) will not leak or mutate causing environmental pollution, or bodily injury from the use of the EIP. The EFUP indicated by the Logo 2 label applies to a product and all its parts. Certain field-replaceable parts, such as battery modules, can have a different EFUP and are marked separately. The Disclosure table is intended only to communicate compliance with China requirements. It is not intended to communicate compliance with EU RoHS or any other environmental requirements.
68P02901W74-S
10
1.9.0.0.29
Mar 2008
Motorola document set
Motorola document set

The Motorola document sets provide the information needed to operate, install and maintain the Motorola equipment.
Ordering documents and CD-ROMs

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

A banner (oversized text on the bottom of the page, for example, not yet approved for general customer use.
PRELIMINARY UNDER DEVELOPMENT) indicates that some information contained in the document is
Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the network is encrypted. In order to comply with the export and import requirements of particular countries, this encryption occurs at different levels as individually standardized, or may not be present at all in some parts of the network in which it is normally implemented. The document set, of which this document is a part, covers encryption as if fully implemented. Because the rules differ in individual countries, limitations on the encryption included in the particular software being delivered, are covered in the Release Notes that accompany the individual software release.
68P02901W74-S Mar 2008
1.9.0.0.29
11
Third Party computer software and trademarks
Third Party computer software and trademarks
Computer Software
The following is a list of the 3rd party computer software copyrights contained within this Motorola product.
Vendor
<Vendor name>
Copyright
Copyright YYYY All Rights Reserved.
Trademarks
Java Technology and/or J2ME: Java and all other Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. UNIX: UNIX is a registered trademark of The Open Group in the United States and other countries.
68P02901W74-S
12
1.9.0.0.29
Mar 2008
Chapter 1
Chapter 1 About this release
68P02901W74-S Mar 2008
1.9.0.0.29
1-1
General information about the release notes
Chapter 1: About this release
General information about the release notes
Introduction
This manual is intended to provide an overall description of the features, changes and enhancements that are provided with release GSR9 1.9.0.0.29 for the OMC-R and to make the user aware of any special operating notes and/or procedures prior to installing this software release in their network. More detailed information can be found in the appropriate GSM Customer Documentation manual. When more specific information is available, a reference to the appropriate manual is provided.
Chapter descriptions
Release information
Chapter 1 provides information on the media provided with 1.9.0.0.29, and information on new features and statistics. Chapter 2 provides a list of open issues. Chapter 3 provides a list of issues resolved in this release. Chapter 4 provides information on compatibility. Chapter 5 provides information on the hardware and firmware requirements. Chapter 6 provides information on software management. Chapter 7 provides information on GSR9 MMI changes.
Information on OMC Utilities can be found in the Online Help.
Nomenclature, release load identification

This release is GSR9 1.9.0.0.29.
68P02901W74-S
1-2
1.9.0.0.29
Mar 2008
Deliverables: DVD-ROMs
Deliverables: DVD-ROMs
Media
DVDROM: Jumpstart/Patches/OMC-R Software
The Jumpstart, Patches and OMC-R Software are included on two DVD-ROMs which are provided with the Netra20 System Processor, SunFire4800 System Processor, the Netra 440 System Processor, SunBlade 150 GUI Server, Netra210 GUI Server and SunBlade 150 GUI Client.
68P02901W74-S Mar 2008
1.9.0.0.29
1-3
New features in 1.9.0.0.29

Information: GSM Overview 68P02901W01 and summarized below.
The new features that are provided with software release GSR9 are described in System
Table 1-1 New features in OMC-R 1.9.0.0.29 release

Feature Number 31565 33397 33863 Feature Name Add parameter for AGCH flow control manually disable and add stats to display AGCH message discard Add paging discard stats for RCC feature related link UL retransmissions measurement
New features in OMC-R

The new OMC-R features provided in GSR9 are listed in Table 1-1.
Table 1-2 New features in OMC-R

Feature Number 23306 25423/4 25663 25867 26481 26740 27236 27508 27703 27717 27955 28000 28337 28351 28398 28938 30365 30828 Feature Name BSC High Load Protection Mechanism Phase 2 Software Patching Secure Services New Drop Call Rate classes distinguishing between TCH and SDCCH Support for Horizon II Micro cabinet identifier PSI cards 4 Branch Receive Diversity BSS User Security Management Quality of Service (QoS) - Phase 2 Support of RESUME at intra BSC level Flexi-PCU interworking with Legacy PCU Rolling Blackouts BSC Signaling Link Set Capacity and Flexibility Evolved PCU (Enhanced PCU) Increasing the capacity of the BSC Support of Incell as an optional parameter Software support for High Power variant of Horizon II Micro CTU2-D Continued
68P02901W74-S
1-4
1.9.0.0.29
Mar 2008
Feature Number 25002 22169 32340 28486 31400 29972 27982 27983 27752 27751 22266 31565 33397 33863
Feature Name TDM Availability Enhancements Support 96 MSI at BSC Cell OOS Enhancement CMCC statistics TD-SCDMA Interworking Port GSM platforms(OMC server and adjuncts) to Solaris 10 GSR9 O&M Platform Clean Install Procedures GSR9 O&M Platform Upgrade Procedures 3GPP upgrade to release6 for 2G element manager FM and CM functionality 3GPP Release 6 Performance Management IRP 2G RSL dimensioning statistics Add parameter for AGCH flow control manually disable and add stats to display AGCH message discard Add paging discard stats for RCC feature related link UL retransmissions measurement
68P02901W74-S Mar 2008
1.9.0.0.29
1-5
New statistics in 1.9.0.0.29

The following statistics are introduced in this release. IA_CS_MSGS_SENT IA_CS_MSGS_DISCARDED IA_IAR_MSGS_PER_AGCH IA_PS_MSGS_SENT IA_PS_MSGS_DISCARDED IAR_CS_MSGS_SENT IAR_CS_MSGS_DISCARDED IAR_PS_MSGS_SENT IAR_PS_MSGS_DISCARDED CS_PAGING_MSGS_FROM_MSC CS_PAGING_MSGS_FROM_MSC_DISCARD_MAX_PAGE CS_PAGING_MSGS_FROM_MSC_DISCARD_RSL_LCF CS_PAGING_MSGS_FROM_MSC_MTL_LCF CS_PAGING_MSGS_FROM_MSC_RRSM CS_PAGING_MSGS_FROM_MSC_RSL_LCF CS_PAGING_MSGS_FROM_MSC_RSS_ABIS CS_PAGING_MSGS_FROM_MSC_RSS_L1 UL_RLC_NACK_BLKS UL_RLC_NACK_BLKS_CS_1 UL_RLC_NACK_BLKS_CS_2 UL_RLC_NACK_BLKS_CS_3 UL_RLC_NACK_BLKS_CS_4 UL_RLC_NACK_BLKS_MCS_1 UL_RLC_NACK_BLKS_MCS_2 UL_RLC_NACK_BLKS_MCS_3 UL_RLC_NACK_BLKS_MCS_4 UL_RLC_NACK_BLKS_MCS_5 UL_RLC_NACK_BLKS_MCS_6 UL_RLC_NACK_BLKS_MCS_7 UL_RLC_NACK_BLKS_MCS_8 UL_RLC_NACK_BLKS_MCS_9 UL_RLC_STALLED_BLKS UL_RLC_STALLED_BLKS_CS_1 UL_RLC_STALLED_BLKS_CS_2 UL_RLC_STALLED_BLKS_CS_3 UL_RLC_STALLED_BLKS_CS_4 UL_RLC_STALLED_BLKS_MCS_1
68P02901W74-S
1-6
1.9.0.0.29
Mar 2008
UL_RLC_STALLED_BLKS_MCS_2 UL_RLC_STALLED_BLKS_MCS_3 UL_RLC_STALLED_BLKS_MCS_4 UL_RLC_STALLED_BLKS_MCS_5 UL_RLC_STALLED_BLKS_MCS_6 UL_RLC_STALLED_BLKS_MCS_7 UL_RLC_STALLED_BLKS_MCS_8 UL_RLC_STALLED_BLKS_MCS_9
68P02901W74-S Mar 2008
1.9.0.0.29
1-7
Statistics modified in 1.9.0.0.29
Statistics modified in 1.9.0.0.29

The following statistics are modified in this release. ASSGN_RES_REQ_INNER_Z_PRE_GSR17602B ASSGN_RES_REQ_INNER_Z_PRE_GSR18002A ASSGN_RES_REQ_PRE_GSR17602BT3 ASSGN_RES_REQ_PRE_GSR18002A DL_LLC_FRAMES_GB_OVER1280 DL_LLC_FRAMES_PCU_OVER1280 DL_LLC_TRAFFIC_VOLUME_INDICATOR HO_REQ_INNER_ZONE_PRE_GSR17602BT3 HO_REQ_INNER_ZONE_PRE_GSR18002A HO_REQ_PRE_GSR17602BT3 HO_REQ_PRE_GSR18002A TCH_BLOCKING_RATE_INN_ZONE_PRE_17602BT3 TCH_BLOCKING_RATE_INN_ZONE_PRE_18002A TCH_BLOCKING_RATE_PRE_17602BT3 TCH_BLOCKING_RATE_PRE_18002A TCH_BLOCKING_RATE_OUT_ZONE_PRE_17602BT3 TCH_BLOCKING_RATE_OUT_ZONE_PRE_18002A TCH_MEAN_ARRIVAL_RATE TCH_MEAN_ARRIVAL_RATE_PRE_GSR17602BT3 TCH_MEAN_ARRIVAL_RATE_PRE_GSR18002A TCH_PREEMPT_NO_Q_ALLOC_PRE_GSR18002A TCH_Q_REMOVED_PRE_GSR17602BT3 TCH_Q_REMOVED_PRE_GSR18002A UL_LLC_FRAMES_OVER1280 UL_LLC_TRAFFIC_VOLUME_INDICATOR
68P02901W74-S
1-8
1.9.0.0.29
Mar 2008
Chapter 2
Chapter 2 Open issues
68P02901W74-S Mar 2008
1.9.0.0.29
2-1
Open issues
Chapter 2: Open issues
Open issues
Overview
Open issues are tracked as Service Requests (SRs). This chapter details Service Affecting (P1), Serious (P2) and Low Priority (P3) Problem Reports and Design Change Requests that are outstanding at the time of the release. Problems that are known at the time of the release are included. This chapter also provides information about any workarounds that exist for these open problems.
Service affecting (P1)

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

A low priority problem report is one that affects a minor functional requirement of the system. P3 problem reports do not prevent the system from meeting its primary functional requirements.
68P02901W74-S
2-2
1.9.0.0.29
Mar 2008
Open issues
Information provided
The information provided on each open issue is explained in Table 2-1.
Table 2-1 Information provided on open issues

Section SR number Operations area Description Customer impact CQSR state Cause Workaround Type of information The problem reference number. Short description of operation being performed when problem occurs. A detailed description of the problem. Provides information on service related difficulties that the customer may experience. Current state of the SR. Describes the steps or operations which cause the problem to occur. Describes the steps to perform the required operation without causing the problem, as described, to occur. Describes any preventative action which could be implemented to minimize occurrence. Describes the steps necessary to return the system to normal operation.
Prevention Recovery
68P02901W74-S Mar 2008
1.9.0.0.29
2-3
Open issues listing
Open issues listing

Table 2-2 lists the SRs which have been reported in the GSR9 1.9.0.0.29 release.
Table 2-2 Open issues reported in GSR9 1.9.0.0.29

SR 843068 953935 986629 1013247 1028815 785800 793917 801466 924436 927080 927396 933593 953037 966247 966277 970404 975526 976242 979854 981119 982303 982322 982885 982898 983646 990661 992326 992935 995685 997420 997957 1000467 Severity P2 P2 P2 P2 P2 P3 P3 P3 P3 P3 P3 P3 P3 P3 P3 P3 P3 P3 P3 P3 P3 P3 P3 P3 P3 P3 P3 P3 P3 P3 P3 P3 Operations area Fault Management Sys Admin CMMIB Sys Admin Sys Admin Sys Admin Database Backup and Restore Sys Admin Sys Admin Informix DB Sys Admin Sys Admin Sys Admin Sys Admin Sys Admin/Database OMC-R GUI NetEx OMC Utilities Sys Admin Sys Admin Sys Admin CMMIB Event Management CMMIB PM GUI Performance Management Performance Management Performance Management Performance Management NetEx Performance Management Continued
68P02901W74-S
2-4
1.9.0.0.29
Mar 2008
Open issues listing
SR 1007649 1010203 1010601 1012726 1013313 1013317 1023792 1027636
Severity P3 P3 P3 P3 P3 P3 P3 P3
Operations area Sys Admin Performance Management Sys Admin GUI RF Planning Interface RF Planning Interface Resync Sys Admin
When majority of SunBlade-150 GUI Servers are used, color performance related issues will be experienced in the OMC-R GUI. It causes more noticeable color and resource issues in GSR9, and it is related to the number of colors the system is configured to support. The active application will use all available color resources and will return them when the application is closed. For instance, when Netscape is running it will use the colors from the OMC-R GUI. So, distorted colors may be seen. To workaround this issue when OMC-R and Online Help are open at the same time, toggle between the two applications. The Netra210, which is now available, will resolve this issue.
68P02901W74-S Mar 2008
1.9.0.0.29
2-5
Open P1 (service affecting) SRs
Open P1 (service affecting) SRs

There are no P1 (service affecting) SRs in this release.
68P02901W74-S
2-6
1.9.0.0.29
Mar 2008
Open P2 (serious) SRs
SR 843068
Operations Area: Fault Management Description
Alarm GSL Link Disconnected is cleared incorrectly on OMC-R when the last GBL Failed.
Customer impact
The alarm GSL Link Disconnected is incorrectly cleared at the OMC-R during the Resync operation.
CQSR State
CQSR State: Originated. The issue needs further investigation to get to the exact root cause and provide a feasible solution.
Cause
Due to the legacy design of OMC, this issue is seen on devices with multiple parent hierarchy such as GSL links which are connected to PCU as well as BSC. During Resync, OMC expects the alarm to be in the parent, but it may be present in the other parent. And thus OMC incorrectly clears the alarm.
Workaround
N/A.
Prevention
N/A.
Recovery
N/A.
SR 953935
Operations Area: Sys Admin Description
The Tool Bar Menu cannot pop-up by the mouse's left and middle key for the OMC users.
Customer impact
The CDE does not operate correctly. Re-installation of the CDE may be required as an extra step during an upgrade. This is currently documented in the Upgrade Guide.
CQSR State
Originated. It is a duplicate of SR 953928 for which a fix has been identified.
68P02901W74-S Mar 2008
1.9.0.0.29
2-7
Cause
There is a software bug in the initialization of the CDE during an upgrade.
Workaround
/usr/omc/current./sbin/cde_install should be run after an upgrade to ensure that CDE is configured correctly.
Prevention
N/A.
Recovery
Same as workaround.
SR 986629
Operations Area: CMMIB Description
The range for the attributes bs_fdd_arfcn and fdd_arfcn in OMC-R need to be changed from (10562 10838) to (0 16383).
Customer impact
The user will not be able to create or modify Blind Source Neighbor cell with values 0 to 10561 (both inclusive) and 10839 to 16383 (both inclusive) for the attribute bs_fdd_arfcn from OMCR GUI, CMUtil, and CellXExport. The user will not be able to create the Utran Neighbor cell with values 0 to 10561 (both inclusive) and 10839 to 16383 (both inclusive) for the attribute fdd_arfcn from OMCR GUI, CMUtil, and CellX. Even after an Audit, the Blind Source Neighbor and Utran Neighbor Detailed Views will show the values within the old range only. The new range will be supported from BSS MMI.
CQSR State
Originated. The fix will be delivered in the next OMC-R Service Pack.
Cause
The support for the new range is provided only by the BSS and not by the OMC-R.
Workaround
N/A.
Prevention
Use the old range value while creating or modifying Blind Source Neighbor cell or Utran Neighbor cell from OMCR GUI, CMUtil, and CellXExport.
Recovery
N/A.
68P02901W74-S
2-8
1.9.0.0.29
Mar 2008
SR 1013247
During an OMC-R upgrade to GSR9, the upgrade appears to detect that the detach of d121 mirror fails, and stops the upgrade with a fatal error. However, if the upgrade script is run a second time manually, no errors are reported and the upgrade is successful.
Customer impact
The customer risk is low due to rare occurrence. This issue has only been reported by one customer where their system had been upgraded from GSR7 to GSR8 to GSR9, and has not been reproduced in any lab testing.
CQSR State
Assessed. Development is attempting to reproduce this issue in the lab environment.
Cause
Unknown.
Workaround
N/A.
Prevention
N/A.
Recovery
If this issue is seen during the normal upgrade procedure, run the script /var/install/upgrade/scripts/upgrade again.
SR 1028815
Unix accounts created by the customer that contain the word root in the account causes failures in the upgrade process from GSR8 to GSR9.
Customer impact
The upgrade fails as other applications and processes will not be able to access important settings needed from the GSR8 side.
CQSR State
Originated. This CQSR is still under investigation.
Cause
Script that migrates settings from GSR8 to GSR9 gets confused when UNIX user accounts exist that contains the word root. This is seen in the field with a ldaproot username, but will occur where root appears anywhere in the account username.
68P02901W74-S Mar 2008
1.9.0.0.29
2-9
Workaround
Rename the account not to include root prior to the upgrade, perform the upgrade and then rename the user account back. Alternatively remove the user prior to the upgrade and reinstate it post upgrade.
Prevention
Do not use UNIX accounts which contain the word root.
Recovery
If the workaround or prevention methods are not followed and the upgrade fails, the only method to recover the system is to perform a rollback to GSR8 and then follow either the Prevention or workaround advice.
68P02901W74-S
2-10
1.9.0.0.29
Mar 2008
Open P3 (annoying) SRs
SR 785800
WAS - PM does not launch from the OMC-R GUI for first time only.
Customer impact
End the GUI session and re-launch it to start the PM.
CQSR state
CQSR State: Assessed.
Cause
Font path variable used by the PM tool does not have the correct locations included when the OMC-R GUI is launched for the first time.
Workaround
Re-launch the OMC-R GUI and select the PM tool.
Prevention
N/A.
Recovery
As per the workaround.
SR 793917
Operations Area: Database Description
The PM loader reports the following error during a cutover on GSR9: INFO: Configuring PM Loader... FATAL ERROR: Unsuccessful iteration of PM Loader DB Objects creation However, the PM loader completes successfully and the cutover continues.
Customer impact
There is no impact to the customer except for the display of the error message.
CQSR State
68P02901W74-S Mar 2008
1.9.0.0.29
2-11
Cause
Failure of the script s53pmupgrade.
Workaround
N/A.
Prevention
N/A.
Recovery
N/A.
SR 801466
Operations Area: Backup and Restore Description
During the installation of the Backup and Restore software, the user has to select whether to reconfigure the bootstrap configuration. If the user accepts the default value n and does not enter explicitly, the error message Invalid response is displayed.
Customer impact
There is no impact as the user has to enter n explicitly.
CQSR State
Cause
The software does not correctly handle the default response.
Workaround
The user must enter n explicitly.
Prevention
N/A.
Recovery
N/A.
68P02901W74-S
2-12
1.9.0.0.29
Mar 2008
SR 924436
The upgrade procedure does not verify that the verify_platform step has been successfully performed.
Customer impact
The operator must perform the verify_platform step (otherwise the upgrade will fail) and deal with any errors indicated.
CQSR State
CQSR State: Originated.The issue is still under investigation.
Cause
No check is performed by the upgrade procedure.
Workaround
Manually check the verify_platform output.
Prevention
Do not run the upgrade procedure until the verify_platform step is successful.
Recovery
N/A.
SR 927080
During upgrade, HSI driver is not installed correctly.
Customer impact
Impact is low as a workaround is available.
CQSR State
Cause
The following error message is displayed in the /usr/omc/logs files: FM_AUDIT(1453) FM_get_line_status(): can't open /usr/omc/current/config/fm/disconnect, error is 2..
Workaround
Install the drivers for the HSI after the upgrade and restart the OMC-R as follows:
68P02901W74-S Mar 2008
1.9.0.0.29
2-13
devfsadm omc stop omc start
Prevention
N/A.
Recovery
Perform the workaround.
SR 927396
Operations Area: Informix DB Description
During upgrade, warning messages are displayed when the PM database is loading.
Customer impact
There is no impact as the PM database continues to load.
CQSR State
Cause
Unknown.
Workaround
N/A.
Prevention
N/A.
Recovery
N/A.
SR 933593
Misleading error message in omcaudit log file when X.25 card is loaded.
Customer impact
Impact is low.
CQSR State
68P02901W74-S
2-14
1.9.0.0.29
Mar 2008
Cause
The misleading error message is displayed in the omcaudit log file in /usr/omc/logs: FM_setup_x25_audit() failed :- There is no X.25 card loaded
Workaround
N/A.
Prevention
N/A.
Recovery
N/A.
SR 953037
Upgrading a Netra 210 GUI server from GSR8 to GSR9 does not clean up some temporary files after the upgrade.
Customer impact
The impact is low. Temporary files used during the upgrade remains on the hard disk. Space occupied does not cause any problems.
CQSR State
Cause
Unknown.
Workaround
N/A.
Prevention
N/A.
Recovery
After the successful upgrade of the Netra 210 GUI server, manually remove the temporary files from /var/install/upgrade/Netra-210.
68P02901W74-S Mar 2008
1.9.0.0.29
2-15
SR 966247
Unable to perform ufsrestore on a GSR9 GUI server where the restore tape resides on the OMCR SPLAT server.
Customer impact
The impact is medium. The operator cannot perform a restore over the network. Restores from a local tape drive are not affected.
CQSR State
Cause
GUI server is unable to perform a remote mount of the tape drive.
Workaround
Clean install the GUI server.
Prevention
N/A.
Recovery
N/A.
SR 966277
The W19 OMCR Sys Admin manual contains ambiguity as to whether the OMC utilities should be installed as user root or user omcadmin. The manual states that the commands should be entered as user root, but the example prompts show the user as omcadmin.
Customer impact
If the OMC utilities are installed as user omcadmin, the install does not complete successfully and the utilities do not function correctly.
CQSR State
Assessed. Clarification will be added to the next version of the W19 manual.
CQSR State
Originated. The issue is still under investigation.
68P02901W74-S
2-16
1.9.0.0.29
Mar 2008
Cause
When installing the OMC utilities as user omcadmin, the install does not complete successfully and the utilities do not work correctly.
Workaround
Install the OMC utilities as user root.
Prevention
Same as workaround.
Recovery
N/A.
SR 970404
Operations Area: Sys Admin/Database Description
One of the soft partitions under the GSR9 disk configuration was not setup correctly. Hence, the PM database instance could not configure the new temp dbspace added in GSR9.
Customer impact
The impact is medium. If this issue occurs and the operator is performing large database transactions, typically RF imports/exports, the operations will fail owing to the lack of temp dbspace. However, this issue has occurred only once on the customer network.
CQSR State
Assessed.
Cause
Unknown.
Workaround
Manually create the d180 soft partition using the Solaris disk tools and then create the temp dbspace. This operation should only be carried out by Motorola field engineers after consultation with Motorola Sys Admin development via the normal support channels.
Prevention
N/A.
Recovery
N/A.
68P02901W74-S Mar 2008
1.9.0.0.29
2-17
SR 975526
Operations Area: OMC-R GUI Description
Alarm icon is grayed out when opening the GUI.
Customer impact
The alarm icon functions even if it is grayed out, but this can mislead the operator.
CQSR State
Cause
Unknown. Other icons are functioning correctly on the GUI. The graying could be due to some issues in the color resources in the system.
Workaround
The alarm icon functions even if it is grayed out.
Prevention
N/A.
Recovery
N/A.
SR 976242
Operations Area: NetEx Description
Due to breaks in the AEC connection, the NetExp process stops functioning.
Customer impact
The impact is high. The OMC has to be started manually.
CQSR State
Cause
Unknown.
Workaround
N/A.
Prevention
N/A.
68P02901W74-S
2-18
1.9.0.0.29
Mar 2008
Recovery
N/A.
SR 979854
Operations Area: OMC Utilities Description
The OMC Utilities in GSR9 uses secure services to operate. This causes the incompatibility issues between the GSR8 and GSR9 OMC Utilities until all the OMC-Rs are upgraded.
Customer impact
Low. Configure ssh on the GSR8 systems for this to work or install the OMC Utilities after all the OMC-Rs are upgraded to GSR9.
CQSR State
Cause
OMC Utilities use secure services in GSR9.
Workaround
Configure the secure services on the GSR8 OMC-Rs or install the OMC Utilities after all the OMC-Rs are upgraded to GSR9.
Prevention
N/A.
Recovery
N/A.
SR 981119
omc_db_maint fails sometimes.
Customer impact
If the omc_db_maint script fails the operators needs to rerun it at a later date. If they fail to do so, the database fragment for next days statistics will not be created. The issue has only been seen on a couple of installations both internal and external to Motorola.
CQSR State
68P02901W74-S Mar 2008
1.9.0.0.29
2-19
Cause
The Informix database shutdown takes longer than the time expected by omc_db_maint leading it to incorrectly assume that the shutdown has failed.
Workaround
N/A.
Prevention
N/A.
Recovery
N/A.
SR 982303
Temporary log files stored in the /tmp directory on the OMC-R are not deleted. On some systems there can be more than 20000 files.
Customer impact
In theory if left unchecked, the /tmp directory would continue to fill up, eventually consuming all available disk space, causing the OMC-R to stop working. However, in practice this scenario has not been reported on any customer system.
CQSR State
Cause
Some OMC-R scripts which update the fragments in the PM database do not remove their log files later.
Workaround
The System Administrator should manually remove older log files in /tmp on a regular basis, or setup a cron job to do this automatically.
Prevention
N/A.
Recovery
N/A.
68P02901W74-S
2-20
1.9.0.0.29
Mar 2008
SR 982322
The /etc/cron.d/cron.allow file is not preserved during the upgrade to GSR9.
Customer impact
Medium. Users other than root and omcadmin will not be able to update or add new crontab entries.
CQSR State
Assessed.
Cause
The /etc/cron.d/cron.allow file is overwritten with a default file.
Workaround
Make a backup copy of the /etc/cron.d/cron.allow file before the upgrade and restore this file after the upgrade has completed.
Prevention
N/A.
Recovery
N/A.
SR 982885
Suspected memory leak (CmMib process).
Customer impact
Large amount of memory is taken by CmMib process. A memory leak in CmMib process could eventually cause the system to crash.
CQSR State
Cause
Unknown.
Workaround
N/A.
Prevention
N/A.
68P02901W74-S Mar 2008
1.9.0.0.29
2-21
Recovery
N/A.
SR 982898
Operations Area: Event Management Description
Suspected memory leak (emProxy process).
Customer impact
Memory usage of emProxy is too high , and it may cause the crash of emProxy process.
CQSR State
Cause
Unknown.
Workaround
N/A.
Prevention
N/A.
Recovery
N/A.
SR 983646
REGION enabled impacts IOS collection performance.
Customer impact
While several tty sessions are ongoing (around 25), if the operator tries to start one more tty session then the new tty session may fail.
CQSR State
Cause
Unknown.
Workaround
N/A.
68P02901W74-S
2-22
1.9.0.0.29
Mar 2008
Prevention
N/A.
Recovery
N/A.
SR 990661
Operations Area: PM GUI Description
HSP MTL - MTL Utilization Key Statistic Formula wrong in OMC PM (GSR9).
Customer impact
Wrong values are displayed for the key statistic MTL Utilization.
CQSR State
Assessed. The solution will be made available as a Test Object 1900.29-t3 and will be merged into the next GSR9 service Pack.
Cause
Wrong Coefficients mentioned in the requirement of the MTL Utilization key statistic.
Workaround
Customer can define their own custom statistic using correct coefficients in the MTL Utilization key statistic formula.
Prevention
N/A.
Recovery
As per workaround.
SR 992326
Operations Area: Performance Management Description
Default value for the statistics TCH_PREEMPT_NO_Q_ALLOC is displayed as ? if the eMLPP feature is not purchased.
Customer impact
User will see junk value in the GUI for this statistic only if eMLPP feature is not purchased.
CQSR State
Assessed: The fix will be delivered in the next GSR9 Service Pack.
68P02901W74-S Mar 2008
1.9.0.0.29
2-23
Cause
The statistic is not initialized.
Workaround
N/A.
Prevention
N/A.
Recovery
N/A.
SR 992935
OMC-R GUI crashes when a network level PM Resync is performed.
Customer impact
The user needs to restart OMC-R GUI.
CQSR State
Assessed. Initial investigation completed.
Cause
The issue occurs only while doing a network wide Resync.
Workaround
Perform PM Resync on BSS or SITE level.
Prevention
Do PM Resync only on individual NE level.
Recovery
Restart the OMC-R GUI.
SR 995685
The segment number present in the GDP logs saved in OMC does not have the correct value. The logs are uploaded from the BSS.
Customer impact
Low.
68P02901W74-S
2-24
1.9.0.0.29
Mar 2008
CQSR State
Assessed. The Fix has been identified and verification is in progress.
Cause
GDBP upload from PCU and OMF.
Workaround
N/A.
Prevention
N/A.
Recovery
N/A.
SR 997420
GDBP upload requests fail while uploading the statistics files.
Customer impact
Unknown.
CQSR State
Originated: The issue is still under investigation.
Cause
GDBP Upload. Further Investigation is needed to identify the root cause.
Workaround
Upload the GDBP Files when statistic files to be uploaded are less in number or when the load is less.
Prevention
Same as workaround.
Recovery
Same as workaround.
68P02901W74-S Mar 2008
1.9.0.0.29
2-25
SR 997957
Operations Area: NetEx Description
The copy site operation takes more time than expected and is not able to copy the statistics data for a cell.
Customer impact
The statistics data for a cell is not copied during a copy site. Also the copy cell operation takes more time than expected.
CQSR State
Assessed.
Cause
The problem occurs when the statistic CALLS_QUEUED is enabled for a cell which the user is trying to copy.
Workaround
Disable the statistic CALLS_QUEUED from OMC-R Performance Management form and perform Copy Site. Detailed procedure is as follows. Identify the SITE to Copy. From OMC-R Main GUI Form, click Performance Icon. Select Report templates and click OK. In the Report Form select File ->New. In the New Form Select the SITE to be copied from the Device list in left panel. Select the Statistic CALLS_QUEUED in the right panel. To search the statistic right click in the right panel and select search, keeping the mouse pressed. From the Menu select Statistics Mgmt ->Disable. In the same Form select the device to copy in the left panel. Select the statistics in the right panel. From Menu select Statistics Mgmt ->Status.
To check the status of the statistic, perform the following procedure.
Prevention
Same as workaround.
Recovery
The Copy Site operation will be completed taking more time during each copy cell step. Each Copy cell takes approximately 1 hour of additional time to be completed.
68P02901W74-S
2-26
1.9.0.0.29
Mar 2008
SR 1000467
A new entity appears in the Networks Element list in the PM Reports GUI.
Customer impact
Low. An unexpected BSS entity is seen in the Network Elements list which has no data in it. The raw statistics data will be present under the correct BSS.
CQSR State
Originated. This CQSR is still under investigation.
Cause
Drop or Recreate the PM database. Perform PM Resync. Parse a raw stats file.
Workaround
N/A.
Prevention
N/A.
Recovery
N/A.
SR 1010601
During the commit phase of an OMC-R upgrade from GSR8 to GSR9, a metadb is created on /dev/dsk/c<X>t13d0s7 but is not created on /dev/dsk/c<Y>t13d0s7 (where c<X> and c<Y> refer to the controllers in use on the customer system, for example c0 and c1, or c1 and c3).
Customer impact
There is minimal customer impact because the metadb information is available on /dev/dsk/c<X>t13d0s7.
CQSR State
Assessed.
Cause
The root cause is not yet identified.
68P02901W74-S Mar 2008
1.9.0.0.29
2-27
Workaround
N/A.
Prevention
N/A.
Recovery
Run the following command as user root to add the missing metadb (controller c1 is the example used in this command): metadb -a -f /dev/dsk/c1t13d0s7
SR 1007649
When performing a clean install of the OMC-R and there is no setting specified for the default router, the installation enters interactive mode and waits for the user to configure the router manually. This occurs after the pre-install questions have been answered, that is, the install should complete automatically without any further user interaction.
Customer impact
The impact is generally low, as customers will typically install an OMC into an existing network and will specify a default router during the pre-install phase. The impact is that if the default router is not specified, and the user leaves the install to complete automatically after answering the pre-install questions, they will come back to the machine 1-2 hours later and see that the install has actually only proceeded a few steps and is now waiting for the user to enter additional router information.
CQSR State
Assessed. A fix is available which will be delivered into the next software release.
Cause
When no default router is specified, the installation enters interactive mode and waits for the user to enter additional information.
Workaround
N/A.
Prevention
Ensure that a valid default router is specified during the pre-install phase.
Recovery
N/A.
68P02901W74-S
2-28
1.9.0.0.29
Mar 2008
SR 1010203
PM statistics formula error in the requirement.
Customer impact
Incorrect values will be reported for the following key statistics: TCH_TRAFFIC_CARRIED_FR SDCCH_TRAFFIC_CARRIED TCH_TRAFFIC_CARRIED_HR TCH_TRAFFIC_CARRIED
CQSR State
Assessed.
Cause
Incorrect formula is defined in MotorolaDefinedStats.as file which is used for calculating the values for the above key stats.
Workaround
N/A.
Prevention
N/A.
Recovery
N/A.
SR 1012726
Operations Area: GUI Description
The four attributes init_dl_cs, init_ul_cs, egprs_init_dl_cs, and egprs_init_ul_cs are modifiable from the GUI only when gprs_enabled is 0. But when the user first changes any of these attributes and then changes the gprs_enabled from 0 to 1 then in the CELL Detailed View the modified value for the attribute is also shown after a save operation. This creates the impression that the modified value for the attribute is saved which is not the case.
Customer impact
Low. The modified value is not saved. On re-opening the Detailed View, the correct value is displayed.
CQSR State
Assessed: The SR will be delivered into the next GSR9 Service Pack.
68P02901W74-S Mar 2008
1.9.0.0.29
2-29
Cause
From the Cell Detailed View, in Edit mode modify gprs_enabled to 0. Modify any of the above mentioned attributes. Revert gprs_enabled back to 1 and perform Save. The OMC-R software was handling this scenario internally but no message was displayed on the GUI.
Workaround
Modify gprs_enabled and any of the four attributes separately.
Prevention
Same as workaround.
Recovery
Close and reopen the CELL Detailed View. The correct values will be displayed.
SR 1013313
Operations Area: CellX Description
For a dual band cell, the RTF data is incorrectly processed and saved by CellxExport.
Customer impact
Medium.
CQSR State
Assessed. Fix has been identified and verification is in progress.
Cause
This occurs only when the CellxExport is performed for a dual band cell.
Workaround
N/A.
Prevention
N/A.
Recovery
N/A.
68P02901W74-S
2-30
1.9.0.0.29
Mar 2008
SR 1013317
Operations Area: RF Planning Interface Description
If Hopping Support Number1 and Hopping Support Number2 along with MobileAllocationList1 and MobileAllocationList2 are modified in the input file to a CellxImport operation, HSN1 and MobileAllocList1 get updated in OMC GUI but HSN2 and MobileAllocList2 remain unchanged.
Customer impact
User will not be able to modify the hopping systems using cellXImport.
CQSR State
Assessed. A fix will be merged into the next GSR9 Service Pack.
Cause
The issue happens only if Hopping Support Number1 and Hopping Support Number2 along with MobileAllocationList1 and MobileAllocationList2 are modified in the input file. Improper handling of Hopping support list.
Workaround
Modify the values in two separate cellXImport operation.
Prevention
Same as workaround.
Recovery
Same as workaround.
SR 1023792
Operations Area: Resync Description
The maximum number of auto resync is beyond the value of MAX_AUTO_RESYNC_RESERVED_SLOTS.
Customer impact
Low. The issue will not have any impacts on the day to day operation.
CQSR State
Originated: The issue is still under investigation.
Cause
Due to a change in logic of Resync active table handling, when too many auto resync are run, the total number of resync can be one more than the maximum allowed value.
68P02901W74-S Mar 2008
1.9.0.0.29
2-31
Workaround
N/A.
Prevention
N/A.
Recovery
N/A.
SR 1027636
Customer created OMCR users that have a username starting with omc are not migrated during a GSR8 to GSR9 upgrade. This does not impact the Motorola created omcadmin and omcread users.
Customer impact
These affected user accounts are lost during upgrade and need to be recreated if required in GSR9.
CQSR State
Originated. This CQSR is under investigation.
Cause
Attempt to upgrade an OMCR from GSR8 with customer created user accounts starting with omc and upgrade to GSR9. Following the upgrade the user accounts and associated home directories do not exist in the GSR9 system.
Workaround
Customers can rename these accounts before the upgrade, perform the upgrade and then in GSR9 rename the accounts back to their original names.
Prevention
Do not create user accounts starting with omc.
Recovery
If the workaround is not followed and user accounts started with omc existed in GSR8 then following the upgrade to GSR9 the accounts would need to be recreated. Home directory files can be restored from a backup taken prior to the upgrade or by mounting the GSR8 partitions and copying the files.
68P02901W74-S
2-32
1.9.0.0.29
Mar 2008
Chapter 3
Chapter 3 Resolved issues
68P02901W74-S Mar 2008
1.9.0.0.29
3-1
Resolved issues listing
Chapter 3: Resolved issues

All SRs that are fixed in this release will be pulled up to future 1.9.0.0 releases.
SR 927975
Clarify Case: N/A. Title: 190024: N440 OMC-R Clean install-Error message on Installation of NIS failed.
SR 929496
Clarify Case: N/A. Title: RTT OMC 1900.24 not able to overwrite id_rsa file when ssh-keygen -t rsa.
SR 996185
Clarify Case: N/A. Title: Fake alarm against performance_management team.
SR 996258
Clarify Case: N/A. Title: To enable Resync to correct the DRI RTF data discrepancy.
SR 997353
Clarify Case: N/A. Title: GSR9 FP1 Key stats.
SR 997430
Clarify Case: N/A. Title: FR33863 (UL retransmission calculation).
SR 997957
Clarify Case: N/A. Title: Site reparent by datagen failed.
68P02901W74-S
3-2
1.9.0.0.29
Mar 2008
SR 998042
Clarify Case: N/A. Title: 26881: EXT_UL_DUR description incorrect at GSR9 OMCR On line help.
SR 998712
Clarify Case: N/A. Title: The abnormal values of BUSY_TCH_MAX & BUSY_TCH_MEAN stats.
SR 999631
Clarify Case: N/A. Title: RTT-T: The button of Monitor somewhere not valuable - NESoftwareForm - Edit and revert from Edit.
SR 1000429
Clarify Case: N/A. Title: S02SetupServices does not copy Informix service scripts.
SR 1005026
Clarify Case: N/A. Title: Cannot create customer statistic with TCH_Q_REMOVED_Pre_18002a raw stats.
SR 1005296
Clarify Case: N/A. Title: FHS can impact GPRS_enable result abnormally.
SR 1005391
Clarify Case: N/A. Title: FR33397 - PM support.
SR 1006580
Clarify Case: N/A. Title: FR31565 - PM support.
68P02901W74-S Mar 2008
1.9.0.0.29
3-3
Chapter 3: Resolved issues
SR 1008403
Clarify Case: N/A. Title: 26881: Impacts of BSS SR 1005970.
68P02901W74-S
3-4
1.9.0.0.29
Mar 2008
Chapter 4
Chapter 4 Compatibility
68P02901W74-S Mar 2008
1.9.0.0.29
4-1
OMC-R systems supported by this release
Chapter 4: Compatibility
OMC-R systems supported by this release

GSR9 1.9.0.0.29 software load supports the following OMC-R systems: Existing OMC-R systems An upgrade is required for these systems (as described in Chapter 5 Hardware and firmware requirements). New OMC-R systems A clean install is required. This updates the OMC-R software to the version GSR9 1.9.0.0.29.
68P02901W74-S
4-2
1.9.0.0.29
Mar 2008
OMC-R BSS compatibility

The different compatibility types are defined as follows:
N compatibility
The OSS load in a given SSPR works fully with the BSS load in the given SSPR on the current loadline. It also supports all the subsequent BSS loads, up to (but not including) the next SSPR.
N-1 compatibility
The OSS load in a given SSPR (for example, GSR9) is compatible with all the BSS loads since (and including) the latest SSPR of the previous loadline (for example, GSR8).
Standard Service Packs

Standard Service Packs deliver solutions that do not require support in any of the other adjunct products. OMC-R Service Packs give full support to all BSS and DataGen loads released from last System Service Packs up to but not including next System Service Pack.
System Service Packs

System Service Packs deliver solutions for issues that require combined support in BSS and OMC-R or DataGen. Solutions are fully supported in BSS, OMC-R and DataGen service packs and are made available in a coordinated timeframe. If a customer deploys a single product from a System Service pack (that is, only OMC load but not BSS load), then the system fixes will not be supported and some anomalies will be seen. However, the products should function together unless specifically stated in the Release Notes. OMC-R 1.9.0.0.29 is the first service pack to be delivered on GSR9 and it is a System Service Pack. The latest released GSR9 System Service Pack is a combination of the following loads:
Table 4-1 GSR9 1.9.0.0 BSS/OMC-R/DataGen System Service Packs

GSR9 1.9.0.0 BSS/OMC-R/DataGen System Service Packs BSS 1.9.0.0.1e-t1 DataGen 1.9.0.0.28 OMC-R 1.9.0.0.29 Available Feb 2008
Any customer upgrading to any of these individual loads or later versions should upgrade all System Elements to the latest System Service Pack standard. The customer is requested to check with the Motorola representative for the latest available versions of software for the most appropriate combinations to maintain system integrity. The GSR9 1.9.0.0.29 software is fully compatible with BSGSM-1.8.0.0 loads released from the last System Service Pack and further Standard Service pack.
68P02901W74-S Mar 2008
1.9.0.0.29
4-3
The GSR9 1.9.0.0.29 OMC-R software load is compatible with the following GSR9 and GSR8 BSS software loads:
Table 4-2 GSR9 and GSR8 BSS loads compatible with GSR9 1.9.0.0.29 OMC-R load
GSR8 BSS load Names 1800.2f 1800.30 1800.31 1800.31-t1 1800.31-t2 1800.32 1800.33 1800.34 1800.35 GSR9 BSS load Names 1900.1b-t5 1900.1b.t6 1900.1b.t7 1900.1c 1900.1c.t1 1900.1c.t2 1900.1c.t3 1900.1d 1900.1e-t1
System Impacting SRs fixed in 1900.29 load

OMC SR Number: 1008403 Operations Area: GUI Description: The default value for the attribute gprs_bs_cv_max is modified to 8. BSS SR Number: 1005970 Clarify Case: N/A. Compatibility Impacts: No Impacts on OMC BSS compatibility.
68P02901W74-S
4-4
1.9.0.0.29
Mar 2008
Jumpstart
Jumpstart
The recommended versions of Jumpstart for the GSM OMC-R 1.9.0.0.29 release are as follows: GSR9 1900 DVD including OMC Software and Jumpstart, containing Solaris 10 Operating System for Netra 20, Netra 440, SunFire 4800/4900, SunBlade 150 GUI Server, Netra 210 GUI Server and SunBlade 150 GUI Client. GSR9 1900 DVD containing additional OMC software.
For a list of the supported configurations for the GUI server and client, refer to the GSM OMC-R 1.9.0.0 Upgrade/Migration Guide (OSS-GSR9-CUSTSUP-UG-001). Also, refer to Installation and Configuration: OMC-R Clean Install (68P02901W47).
68P02901W74-S Mar 2008
1.9.0.0.29
4-5
M-Cell compatibility
M-Cell compatibility
Release GSR9 1.9.0.0.29 fully supports the MCell range of products.
68P02901W74-S
4-6
1.9.0.0.29
Mar 2008
Chapter 5
Chapter 5 Hardware and firmware requirements
68P02901W74-S Mar 2008
1.9.0.0.29
5-1
Hardware and firmware requirements
Chapter 5: Hardware and firmware requirements
Hardware and firmware requirements
Hardware requirements summary

The Sun Ultra 10, Ultra 60 and E3500 will not be supported in GSR9 (all releases). These platforms will reach the end of service life with Sun by the end of 2007. Refer to bulletin GSM_G_OMCR_079 for further details.
68P02901W74-S
5-2
1.9.0.0.29
Mar 2008
Chapter 6
Chapter 6 Software management
68P02901W74-S Mar 2008
1.9.0.0.29
6-1
Software installation
Chapter 6: Software management
Software installation
Introduction
This section provides all the necessary procedures required to install the OMC-R software release GSR9 1.9.0.0.29. In order for the user to run the OMC-R application software delivered in this release, the necessary hardware and software requirements for the OMC-R system must be satisfied. The complete list of requirements for the Single Platform and GUI server as required for this release is given in the Upgrade requirements section of this chapter.
Pre-upgrade, upgrade and rollback procedures

Refer to the GSM OMC-R 1.9.0.0 Upgrade/Migration Guide (OSS-GSR9-CUSTSUP-UG-001) for pre-upgrade, upgrade and rollback procedures.
Clean install procedures

Refer to the manual Installation and Configuration: OMC Clean Install (68P02901W47) for the complete set of procedures for a clean install of GSR9 (1.9.0.0.29).
Open issues affecting upgrade/installation

Refer to Chapter 2 Open issues.
68P02901W74-S
6-2
1.9.0.0.29
Mar 2008
Upgrade requirements
Introduction
This section gives a list of requirements for upgrading the OMC-R system from release 1.8.x.0 to GSR9 1.9.x.0: OMC-R 1.8.0.0 to 1.9.0.0
Impact and interaction

As part of a major upgrade, if the option to save the PM data is chosen, the operator is informed of current data volume and the size of the target file system.
Feature traceability
This feature is identified as follows: RDP number: 27983 Feature description: GSM OMC-R 1.9.0.0 Upgrade/Migration Guide (OSS-GSR9CUSTSUP-UG-001)
68P02901W74-S Mar 2008
1.9.0.0.29
6-3
Chapter 6: Software management
68P02901W74-S
6-4
1.9.0.0.29
Mar 2008
Chapter 7
Chapter 7 MMI changes
68P02901W74-S Mar 2008
1.9.0.0.29
7-1
MMI changes introduced in GSR9
Chapter 7: MMI changes
MMI changes introduced in GSR9

This chapter lists the changes to commands, parameters, alarms, statistics and timers introduced by GSR9. For complete information, refer to:
Technical Description: BSS Command Reference (68P02901W23) for commands and parameters. Maintenance Information: Alarm Handling at the OMC (68P02901W26) for alarms. Maintenance Information: GSM Statistics Application (68P02901W56) for statistics. Maintenance Information: BSS Timers (68P02901W58) for timers.
68P02901W74-S
7-2
1.9.0.0.29
Mar 2008
Commands
Commands
New commands
The following commands are introduced OMC-R GSR9 release: login logout chg_cmd_level
Modified commands
The following commands are modified in OMC-R GSR9 release: ins_device reset _device add_conn del_conn disp_mms_ts_usage mod_conn chg_stat_prop disp_enable_stat disp_stat_prop disp_stats stat_mode chg_element disp_element chg_audit_sched device_audit query_audits disp_version chg_csfp disp_cfsp disp_equipment equip modify_value unequip unlock_device lock_device state copy_cell
68P02901W74-S Mar 2008
1.9.0.0.29
7-3
Commands
diagnose_device disp_cal_data chg_level add_nvsc alarm_mode assess cage_audit del_act_alarm del_nvsc disp_bss disp_nvsc disp_processor mod_nvsc reset_site site_audit soft_reset status_mode disp_rtf_channel disp_hdlc reassign disp_processor add_neighbor disp_cell_status disp_traffic
Deleted commands
No commands are deleted in OMC-R GSR9 release.
68P02901W74-S
7-4
1.9.0.0.29
Mar 2008
Parameters
Parameters
New parameters
The following parameters are introduced in OMC-R GSR9 release: qos_mbr_enabled thp_stream_weight streamDngdEnabled mtbr_dngd_enabled pfm_sig_enabled arp_streaming_1 arp_streaming_2 arp_streaming_3 arp_i_be_1 arp_i_be_2 arp_i_be_3 arp_bg_1 arp_bg_2 arp_bg_3 bsp_ovld_protect ext_ul_dur trau_fillfrm_thr eth_rx_errors_thr eth_tx_errors_thr dspErrGenThresh dspErrClrThresh dspErrorInc fer_meas_period streaming_enabled dtm_enabled td_enabled tdm_switch cell_barred_delay max_dtm_ts max_lapdm ext_utbf_nodata tdd_qoffset tddMultiratRprtng tdd_gprs_qoffset
68P02901W74-S Mar 2008
1.9.0.0.29
7-5
Parameters
_cell_b_33520_1 _cell_b_33520_2 tdd_arfcn tdd_cell_param tdd_tstd_mode tdd_sctd_mode ext_pdchs mtl_rate csfp_flow base_ip_address gds_subnet_mask gds_rtr_ip_addr prp_fanout_mode gds_connectivity bsc_eth pcu_eth
Modified parameters
The following parameters are modified in OMC-R GSR9 release: gprs_ul_dl_bias pcu_redundancy primary_pcu diversityFlag pcu_red_map_01 pcu_red_map_02 pcu_red_map_11 pcu_red_map_12 pcu_red_map_21 pcu_red_map_22 gprs_mac_mode gprs_dl_pwr_mode thp_be_weight max_tx_bts rr_t3142 dri_density cabinet_type max_mtls audit_type gds_type dproc_type
68P02901W74-S
7-6
1.9.0.0.29
Mar 2008
Parameters
Deleted parameters
The following parameters are deleted in OMC-R GSR9 release: arp_signal_sele pfc_be_arp
68P02901W74-S Mar 2008
1.9.0.0.29
7-7
Alarms
Alarms
New alarms
The following alarms are introduced in OMC-R GSR9 release: 5. TDM: Bus swap could not be initiated 229. TDM: Swap audit failure 52. BSP: BSP CPU Safe Overload 53. BSP: BSP CPU critical overload 0. ETH: Ethernet Link Disconnected 1. ETH: Excessive PSI_TRAU FILL FRAME TX 2. ETH: Excessive ETH RX ERRORS 3. ETH: Excessive ETH TX ERRORS 4. ETH: Unsupported Auto-Negotiated Signaling Rate 5. ETH: DSW/DSWX Switching Hardware Required 1. GDS: IP address mismatch 2. GDS: Protocol failure 39. PPROC: Software failure 239. PPROC: Process safe test Audit Failure 0. PSI: Re-Initialized Unexpectedly 1. PSI: Hard Reset 2. PSI: Watchdog timer expired 3. PSI: Clock B signal loss 4. PSI: Clock A signal loss 5. PSI: Assigned timeslot counter underflow 6. PSI: Assigned timeslot counter overflow 7. PSI: TDM parity error 11. PSI: DSP 0 Audit 12. PSI: DSP 1 Audit Failure 13. PSI: DSP 2 Audit Failure 14. PSI: DSP 3 Audit Failure 15. PSI: DSP 4 Audit Failure 16. PSI: DSP 5 Audit Failure 17. PSI: DSP 6 Audit Failure 18. PSI: DSP 7 Audit Failure 19. PSI: DSP 8 Audit Failure 20. PSI: DSP 9 Audit Failure 21. PSI: DSP 10 Audit Failure 22. PSI: DSP 11 Audit Failure
68P02901W74-S
7-8
1.9.0.0.29
Mar 2008
Alarms
23. PSI: DSP 12 Audit Failure 24. PSI: DSP 13 Audit Failure 25. PSI: DSP 14 Audit Failure 26. PSI: DSP 15 Audit Failure 224. PSI: Safe test Audit Failure 231. PSI: TDM interface configuration failure 232. PSI: Processor bus communication failure 50000/50001/50002 OMC: Field engineer password to be changed 88. DPROC: Max temperature exceeded 92. DPROC: High temperature exceeded 0. PPROC: Processor Communications Failure 9. PPROC: PPROC Reset Detected 22. PPROC: SWFM Indication 42. MMS: DSW/DSWX switching hardware required, BSC is now operating in Single Rate mode 5. TDM: Bus swap could not be initiated 229. TDM: Swap audit failure 30077. define patchLevelInstallFailed
Modified alarms
The following alarms are modified in OMC-R GSR9 release: 45. BSS: Circuit fault detected on GPRS circuit 46. BSS: Circuit fault cleared on GPRS circuit 39. DPROC: Software failure 239. DPROC: Process safe test audit failure
Deleted alarms
No alarms are deleted in OMC-R GSR9 release.
68P02901W74-S Mar 2008
1.9.0.0.29
7-9
Statistics
Statistics
New statistics
The following statistics are introduced in OMC-R GSR9 release: HO_BLKD_BSP_OVERLOAD EXT_UL_EXITS EXT_UL_USF_USAGE PFC_GBR_DL PFC_GBR_UL PFC_TRANSFER_DELAY PFC_PREEMPTIONS_TRAFFIC_CLASS PFC_REJECTION_TRAFFIC_CLASS PFC_ADMISSION_TRAFFIC_CLASS GTTP_DL_LLC GTTP_UL_LLC DTM_REQ_REC DTM_TS_USAGE DTM_TS_INTRLV_DEPTH DTM_REQ_SUCCESS DTM_REQ_REJ DTM_ASSIGN_FAILURE DTM_ESTABLISHMENT DCCH_DTM_PAGE_REQS DTM_BUSY_PDTCH NO_DTM_AVAIL_TIME UL_BUSY_PDTCH_WITH_ACTIVITY DL_BUSY_PDTCH_WITH_ACTIVITY DTM_REQ_REJ UL_RADIO_BLKS_GMSK_3_TS UL_RADIO_BLKS_GMSK_4_TS UL_RADIO_BLKS_8PSK_3_TS UL_RADIO_BLKS_8PSK_4_TS UL_TBF_TIME_GMSK_3_TS UL_TBF_TIME_GMSK_4_TS UL_TBF_TIME_8PSK_4_TS UL_TBF_TIME_8PSK_3_TS TCH_PREEMPT_NO_Q_ALLOC AVG_SIMUL_UL_TBFS
68P02901W74-S
7-10
1.9.0.0.29
Mar 2008
Statistics
AVG_SIMUL_DL_TBFS BLOCKED_DL_TBFS INSUFF_RSL_BANDWDT INSUFF_RESOURCE TBF_REJ_QOS_CONST NUM_SUSP_RESU_RCVD MS_RA_CAP MTP_SL_ERROR_RATE_HSP MTL_LINK_RATE PROCESSOR_SAFE_OVERLOAD PROCESSOR_CRITICAL_OVERLOAD RSL_TX_OCTETS RSL_RX_OCTETS RSL_LINK_INS RSL_LINK_RATE PRP_LOAD GCI_FOR_64KPD_DEMAND GCI_FOR_32KPD_DEMAND GCI_FOR_16KPD_DEMAND TBF_SESSIONS ETH_RX_ERROR ETH_TX_ERROR ETH_RX_BYTE ETH_RX_PKT ETH_TX_BYTE ETH_TX_PSI_TRAU_FILL_FRAME_TX
Modified statistics
The following statistics are modified in OMC-R GSR9 release: CPU_USAGE PRP_PD_DEMAND TOTAL_GCI_FOR_PD_DEMAND AIR_DL_TBF_FAILURES AIR_UL_TBF_FAILURES MA_CMD_TO_MS_BLKD RF_LOSSES_TCH RF_LOSSES_TCH_HR MTL_UTILISATION_RX MTL_UTILISATION_TX PDU_DISCARD_LLC
68P02901W74-S Mar 2008
1.9.0.0.29
7-11
Statistics
PFC_DOWNGRADE_FAILURE PFC_DOWNGRADE_SUCCESS TCH_Q_REMOVED PFC_REJ_DGRD_PRMPT_PRP RF_LOSSES_SD PFC_ADMISSION_SUCCESS PFC_ADMISSION_REJECTION PFC_REJECT_CAUSES DL_LLC_DATA_VOLUME UL_LLC_DATA_VOLUME PFC_UPGRADE PFC_PREEMPTIONS
Deleted statistics
No statistics are deleted in OMC-R GSR9 release.
68P02901W74-S
7-12
1.9.0.0.29
Mar 2008
Timers
Timers
New timers
The following timers are introduced in OMC-R GSR9 release: bssgp_t4_timer ss7_hsp_l2_t1
Modified timers
No timers are modified in OMC-R GSR9 release.
Deleted timers
No timers are deleted in OMC-R GSR9 release.
68P02901W74-S Mar 2008
1.9.0.0.29
7-13
GSM OMC-R 1.9.0.0 Upgrade/Migration Guide

OSS-GSR9-CUSTSUP-UG-001 Abstract
This document describes the procedure for an upgrade/migration from GSR8 to GSR9
Audience: Customer Information Authoring Organization: System Administration Development, Swindon Version: 1.7 Status: Released 6 December 2007
2005, Motorola General Business Use
1.0
1.0 2.0 3.0 4.0 5.0
5.1 5.2 5.3 5.4 5.5 5.6 5.7
Table of Contents
Table of Contents .......................................................................................................................2 Revision History .........................................................................................................................4 References...................................................................................................................................5 Glossary of Terms ......................................................................................................................6 General Information..................................................................................................................7
SUMMARY ............................................................................................................................................................. 7 OVERALL PROCEDURE WORK FLOW ..................................................................................................................... 8 SCOPE, PURPOSE AND AUDIENCE .......................................................................................................................... 8 DOCUMENT FORMAT CONVENTIONS ..................................................................................................................... 9 ADJUNCT PRODUCTS .............................................................................................................................................. 9 PROCEDURE IMPACTS ............................................................................................................................................ 9 LOGGING AND TRACKING CONVENTION ................................................................................................................ 9
6.0
6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8
Preparation...............................................................................................................................10
SYSTEM STABILITY CHECKS ................................................................................................................................ 10 UPGRADE PREREQUISITES ................................................................................................................................... 11 MIGRATION PREREQUISITES ................................................................................................................................ 12 SYSTEMS BACKUP ............................................................................................................................................... 13 VERIFY THE GSR9 DVD MEDIA ......................................................................................................................... 13 CREATE THE UPGRADE DIRECTORY .................................................................................................................... 14 GENERAL PREPARATION ...................................................................................................................................... 15 CONFIGURING THE VERIFY, UPGRADE AND MIGRATION PHASES FOR THE SINGLE PLATFORM PROCESSOR ........ 17
7.0
7.1 7.2 7.3
Single Platform Processor and GUI Server - Verification Procedure Tasks .....................19
VERIFY THE SINGLE PLATFORM PROCESSOR ....................................................................................................... 19 VERIFY THE GUI SERVER .................................................................................................................................... 19 EXAMINE VERIFY LOGFILES ................................................................................................................................ 20
8.0
8.1 8.2 8.3 8.4 8.5 8.6 8.7 8.8 8.9 8.10 8.11 8.12 8.13
Single Platform Processor - Upgrade Procedure Tasks .......................................................21

UPGRADE PROCEDURE WORK FLOW ................................................................................................................... 21 TOOLS AND ADJUNCT PRODUCTS ........................................................................................................................ 21 UPGRADE AND REBOOT THE SINGLE PLATFORM PROCESSOR .............................................................................. 22 EXAMINE UPGRADE LOGFILES ............................................................................................................................ 25 INSTALL ADDITIONAL SOFTWARE PATCHES ......................................................................................................... 25 INSTALL STOREDGE BACKUP SOFTWARE ............................................................................................................ 27 NETWORK PERFORMANCE PROBLEM ................................................................................................................... 28 MANDATORY PM DATABASE TASKS ................................................................................................................... 28 CHECK OMC AUDIT LOG FILE FOR POSSIBLE ERRORS .......................................................................................... 31 TOOLS AND ADJUNCT PRODUCTS ........................................................................................................................ 31 COMPLETE FILESYSTEM BACKUP ........................................................................................................................ 32 RE-MIRROR THE SYSTEM .................................................................................................................................... 32 EXAMINE COMMIT LOGFILES .............................................................................................................................. 32
9.0
9.1 9.2 9.3 9.4 9.5 9.6 9.7
Single Platform Processor - Rollback Procedure Tasks.......................................................34

TOOLS AND ADJUNCT PRODUCTS ........................................................................................................................ 34 BACK OUT PROCEDURE SCENARIO ONE ........................................................................................................... 34 BACK OUT PROCEDURE SCENARIO TWO .......................................................................................................... 35 EXAMINE ROLLBACK LOGFILES .......................................................................................................................... 36 RETAIN ROLLBACK DIRECTORY .......................................................................................................................... 36 TOOLS AND ADJUNCT PRODUCTS ........................................................................................................................ 37 MANDATORY PM DATABASE TASKS ................................................................................................................... 37
10.0
10.1 10.2 10.3
Single Platform Processor Migration Procedure Tasks.................................................40

SINGLE PLATFORM PROCESSOR MIGRATION PROCEDURE WORK FLOW .............................................................. 40 CLEAN INSTALL THE TARGET (SF4900) PLATFORM ............................................................................................ 40 TOOLS AND ADJUNCT PRODUCTS ........................................................................................................................ 41
_________________________________________________________________________________________________ Doc ID: OSS-GSR8-CUSTSUP-RLS-003 Doc Version: 3.0 2
2005, Motorola General Business Use 10.4 10.5 10.6 10.7 10.8 10.9 10.10 UPDATE TARGET (SF4900) PLATFORM IP ADDRESS AND DOMAIN .................................................................. 41 MIGRATE THE SOURCE (E3500) PLATFORM ...................................................................................................... 42 EXAMINE MIGRATION LOGFILES ......................................................................................................................... 43 UPDATE TARGET (SF4900) PLATFORM IP ADDRESS......................................................................................... 44 MANDATORY PM DATABASE TASKS ................................................................................................................... 45 CHECK OMC AUDIT LOG FILE FOR POSSIBLE ERRORS .......................................................................................... 47 NETWORK PERFORMANCE PROBLEM ............................................................................................................... 47
11.0
11.1 11.2
Single Platform Processor - Migration Rollback Procedure Tasks .................................48

SINGLE PLATFORM PROCESSOR MIGRATION ROLLBACK ..................................................................................... 48 MANDATORY PM DATABASE TASKS ................................................................................................................... 48
12.0
12.1 12.2 12.3 12.4 12.5 12.6 12.7 12.8 12.9 12.10 12.11 12.12
GUI Server - Upgrade Procedure Tasks ............................................................................51

GUI SERVER UPGRADE PROCEDURE WORK FLOW .............................................................................................. 51 COP TOOLS/NHA PRE-UPGRADE WORKAROUNDS ............................................................................................ 51 REBOOT THE GUI SERVER ................................................................................................................................... 52 UPGRADE AND REBOOT THE GUI SERVER ........................................................................................................... 52 ACTIVATE SECURE SERVICES ON THE GUI SERVER ............................................................................................. 54 EXAMINE UPGRADE LOGFILES ............................................................................................................................ 55 INSTALL ADDITIONAL SOFTWARE PATCHES ......................................................................................................... 55 COP TOOLS/NHA POST-UPGRADE WORKAROUNDS........................................................................................... 58 POST-UPGRADE PROCEDURE FOR NETRA 210 GUI SERVER ................................................................................ 58 COMPLETE FILESYSTEM BACKUP .................................................................................................................... 58 COMMIT THE SYSTEM ...................................................................................................................................... 58 EXAMINE COMMIT LOGFILES .......................................................................................................................... 59
13.0
13.1 13.2 13.3 13.4 13.5
GUI Server - Rollback Procedure Tasks............................................................................61

ROLLBACK PROCEDURE SCENARIO ONE ........................................................................................................... 61 ROLLBACK PROCEDURE SCENARIO TWO .......................................................................................................... 62 ROLLBACK PROCEDURE SCENARIO THREE ....................................................................................................... 62 EXAMINE ROLLBACK LOGFILES .......................................................................................................................... 63 RETAIN ROLLBACK DIRECTORY .......................................................................................................................... 63
A
A.1 A.2 A.3
Trouble Shooting......................................................................................................................64
VERIFY DISK CHECK ........................................................................................................................................... 64 MIB DATABASE MIGRATION ............................................................................................................................... 64 HOW TO CORRECT A POTENTIAL SYSTEM PERFORMANCE PROBLEM ..................................................................... 64
B
B.1 B.2
Upgrade Logging and Tracking Convention.........................................................................66

LOGGING ............................................................................................................................................................. 66 TRACKING ........................................................................................................................................................... 66
C
C.1 C.2 C.3 C.4
Single Platform Processor - Typical Script Output ..............................................................70

VERIFY SCRIPT .................................................................................................................................................... 70 UPGRADE SCRIPT ................................................................................................................................................. 72 COMMIT/MIRROR SCRIPT .................................................................................................................................... 90 ROLLBACK SCRIPT............................................................................................................................................... 94
D
D.1 D.2 D.3 D.4 D.5
GUI Server - Typical Script Output.......................................................................................96

MIRROR SCRIPT ................................................................................................................................................... 96 VERIFY SCRIPT .................................................................................................................................................... 97 UPGRADE SCRIPT ................................................................................................................................................. 99 ROLLBACK SCRIPTS ........................................................................................................................................... 103 COMMIT SCRIPT................................................................................................................................................. 105
E
E.1
Migration - Typical Script Output .......................................................................................107

MIGRATE
SCRIPT ............................................................................................................................................... 107
F COP TOOLS Gui Server related workarounds .....................................................................112 G NHA GUI Server related workarounds...............................................................................114 H Manual ssh Configuration.....................................................................................................115
H.1 H.2 MIGRATION SCENARIO ...................................................................................................................................... 115 GUI SERVER SCENARIO ..................................................................................................................................... 115
Configuring secure services for multiple OMC-Rs................................................................117
2.0
0.1 1.0 1.1 1.2 1.3
Revision History
Date
13th Dec 2006 24th Jan 2007 31st Jan 2007 26th Apr 2007 22nd June 2007
Version
Author
Sys Admin Development Sys Admin Development Sys Admin Development Sys Admin Development Sys Admin Development
Description
Original Draft Released Released 1900.17 Add workaround for X25 link and subsequent reboot Updated workarounds for load 1900.24 under parent CQSR 904019/CR 916741: Removed workarounds: CQSR 892993/857290 Setting up ssh keys after upgrade CQSR 845047 X25 setup after upgrade Added workarounds: CQSR 660010 cron jobs missing after rollback Added procedure: CQSR 914281 ssh configuration procedure Updated output: CQSR 810149 Check network interface gives error Further updates for 1900.24 OMCR load: CQSR836839 CQSR919623 CQSR922810 Updates for the following SRs: CQSR933603 CQSR933606 CQSR934086 Updates for the following SRs: CQSR950467 CQSR953928 CQSR971481 Updates for the following SRs (CR998072): CQSR990572 CQSR846442
1.4
25th July 2007
Sys Admin Development
1.5
3rd August 2007
1.6
18th October 2007 6th December 2007
1.7
3.0
References
[1] WSG Product Upgrade Strategy Template 001 [2] GSM OMC-R 18x0 and 19x0 Clean Install Manual [3] GSM OMC-R 18x0 and 19x0 System Admin Manual [4] NHA Software Release Notes [5] Hardware that will not be supported in GSR 9 OMCR and NHA [6] OMC-R Release Notes, GSR9 19x0 [7] Update DVD Drive Bulletin [8] NBI Release Notes [9] COP Software Release Notes, [10] DataGen Software Release Notes [11] OSI Software Release Notes WSG-PROC-SYSU-TMPLT68P02901W47 68P02901W19 68P0200W77 GSM_G_OMCR_079 68P02901W74-S GSM_G_OMCR_067 68P02901W73 68P02900W69 68P02900W76 68P02901W70
4.0
CDE
Glossary of Terms
Common Desktop Environment Compact Disk Read Only Memory Digital Versatile Disc Read Only Memory Installing GSM OMC-R on a network for the first time Procedure for changing from one GSM OMC-R release to another Digital Audio Tape Fibre Channel Arbitrated Loop. This is a disk drive technology Global System for Mobile Communications GSM OMC-R machine whose GUI display is being exported from a GUI Server GSM OMC-R machine which may export a GUI to another machine High-speed Serial Interface Installing a specific product with a specific software release Moving from an E3500 machine to a N20/N440/SF4800/4900 as part of an upgrade. This is a 1:1 migration. It does not involve the consolidation of databases. Network File System Network Health Analyst Network Information Service Operations and Maintenance Centre - Radio Open Systems Interconnect Model Procedure for restoring an earlier GSM OMC-R release A N20/Netra440/SunFire 4800/4900 GSM OMC-R combining System Processor and GUI Processor functionality. Traffic Channel Procedure for moving to a newer Major GSM OMC-R release A DVD is shared from the Single Platform Processor to two or more GUI Servers connected to the Single Platform Processor to facilitate upgrading the GUI Servers at the same time.
CD-ROM DVD-ROM Clean Install Cutover DAT FCAL GSM GUI Client GUI Server HSI Installation Migration
NFS NHA NIS OMC-R OSI Rollback Single Platform Processor TCH Upgrade Parallel GUI Server Upgrade
5.0
General Information
This manual is only to be used by System Administrators who have a good knowledge of UNIX and of how the GSM OMC-R functions. Read all the relevant sections of this upgrade/migration guide before proceeding so that tasks can be scheduled in the appropriate order. Read the latest Release Notes for GSR9 1.9.x.0 carefully before proceeding with the upgrade for installation/upgrade instructions specific to this release. The GSM OMC-R may not start if the workarounds specified in these Release Notes are not implemented. Customers with multiple OMC-Rs should note the instructions in Appendix I regarding the introduction of mandatory secure services in GSR9 1.9.x.0, to ensure that the mixed configurations of GSR8 and GSR9 OMC-Rs will function correctly during the upgrade procedure. It is recommended that the upgrade procedure be completed in a terminal type window and not the console window. It is also recommended that the upgrade procedure is completed by logging into the system directly as user root and not through the su command. When connecting to the Platform using the console connection with a PC/laptop. Make sure you have read and fully understand the appropriate PC/laptop documentation in association with the SUN documentation with specific reference to the sending of automatic break/cntrl sequences through the console connection. The consequences of not understanding what you are doing could cause the Platform to halt and return to the OBP prompt. Examples of automatic break/control sequences are, disconnecting the connection, closing a laptop screen, going to power save mode.
5.1 Summary Having completed reading this introduction chapter, refer to the following chapters relevant to the procedure being completed: Single Platform Processor UPGRADE: Follow chapters 6, 7 and 8. Single Platform Processor ROLLBACK after upgrade: Follow chapter 9. GUI Server Upgrade: Follow chapters 6, 7 and 12. GUI Server ROLLBACK after upgrade: Follow chapter 13. MIGRATION: Follow chapters 6, and10 [Chapter 7 can be completed optionally]. MIGRATION ROLLBACK: Follow chapter 11.
5.2
Overall Procedure Work Flow

Upgrade Preparation
Single Platform Processor Verification
Single Platform Processor Upgrade
GUI Server Upgrade
Commit the Single Platform Processor
Commit the GUI Server
5.3
Scope, Purpose and Audience This document is intended for customers and describes the procedure to upgrade a GSM OMC-R Single Platform Processor from GSR8 1.8.x.0 to GSR9 1.9.x.0 and the procedure to upgrade a GSM OMC-R GUI Server from GSR8 1.8.x.0 to GSR9 1.9.x.0. It also describes an upgrade migration from an E3500 to a N20/N440/SF4800/SF4900 where the retiring platform is on a GSR8, 1.8.x.0 release and the target will be on GSR9, 1.9.x.0. The upgrade procedures contained within this document cover the platforms: Single Platform Processor: SUN N20/N440/SunFire 4800/4900 Server GUI Server: Sunblade150, N210 NOTE: Flexible GUI Server platforms and Sunblade150 GUI Client platforms are clean install ONLY. No upgrade procedure is supported on these platforms. Wherever GUI Server is referred to in this guide, it applies to SUNBLADE 150 and N210 GUI Server platforms ONLY. Refer to [5] for more information on supported GSR9 platforms. NOTE: The E3500 Platform has been retired at GSR9 1.9.x.0. All existing E3500 platforms must be migrated to operate at GSR9 1.9.x.0. For details, refer to [5]. The following upgrades and migrations are supported on the Single Platform Processor and GUI Server platforms: N20, N440, Sunfire4800/4900 GSM OMC-R, GSR8 1.8.x.0 to GSR9 1.9.x.0 (Upgrade)
Sunblade 150/N210 GUI Server GSR8 1.8.x.0 to GSR9 1.9.x.0 (Upgrade) E3500 GSM OMC-R, GSR8 1.8.x.0 to N20/N440/SF4800/4900 GSR9 1.9.x.0 (Migration)
5.4
Document Format Conventions The following formatting conventions are used in this document. Table 1: Document Format Conventions
Format Meaning Disk device reference, for example, <c0t0d0s0> Command to be completed Tick box to be completed
<DISK Device_ID>
command
5.5
Adjunct products Where the OMCR has any adjunct product(s) attached please check the release notes for that product for any OMCR upgrade related impacts (see ref [4],[8],[9],[10],[11]). For personnel carrying out upgrades for OMC-R customers who have a Network Health Analyst (NHA) installed please note that the NHA platform will need to be on an NHA release that supports the OMC release. Refer to [4] for details of which NHA release is required with the GSR9 1.9.x.0 OMC-R. Execute the following command to view the current NHA software release:
ls l /usr/omc
If an NHA upgrade is necessary, then it should be upgraded prior to the Single Platform Processor. Refer to [4], Chapter 3: OMC Upgrades for details of this procedure. 5.6 Procedure Impacts This GSM OMC-R Single Platform Processor upgrade procedure will incur an OMC outage. During the upgrade the OMC processes will be stopped and the system reboots. The outage commences once the OMC processes are stopped and is concluded once the reboots associated with the upgrade are complete. Currently it is estimated that the outage time should be in the region of 30 minutes, but this can vary depending on the amount of data in the MIB database. NOTE: Time durations will not be given for individual steps as these will vary depending on the system being upgraded. 5.7 Logging and Tracking Convention For a detailed description of the logging and tracking convention utilised in the upgrade phases see Appendix B.
6.0
Preparation
This section will describe procedures to be completed in order to prepare the Single Platform Processor and GUI Servers for upgrade/migration. 6.1 6.1.1 System Stability Checks Hardware checks Before proceeding with the upgrade ensure that all system cables are secure and all peripheral devices (disk arrays, tape devices and so on) are correctly installed. Required Upgrade Information Ensure that all the tables below are completed before beginning the upgrade/migration procedure. Single Platform Processor Host name Internet Address Temporary Internet Address 1 (Needed for migration only) Netmask Aliases
(Defaults supplied)
6.1.2
omc_splat omc_4gl omc_pm <hostname.domainname>
GUI Server(s)
(Complete details for all relevant GUI server platforms)
Host name Internet Address Location (local/remote) Single Platform Processor hostname Single Platform Processor IP Address A GUI Server Processor is considered to be local if it is on the same sub-net as the Single Platform Processor. A remote machine resides on a separate sub-net to the Single Platform Processor.
The temporary IP address must be a spare unique address on the same subnet as the primary IP address _________________________________________________________________________________________________ Doc ID: OSS-GSR8-CUSTSUP-RLS-003 Doc Version: 3.0 10
6.2
Upgrade Prerequisites Ensure that each of the following prerequisites are available before commencing the upgrade. Software Motorola Patches and Jumpstart, Ultra Client GSR8 1.8.x.0 DVDROM Motorola GSR9 1.9.0.0.X inc OMC Software and Jumpstart DVDROM Motorola GSR9 1.9.0.0.X Additional OMC Software DVDROM StorEdge Enterprise Backup Software License [where applicable] NBI Corba Server [where applicable] NHA Server [where applicable] Available
Documentation
Part Number
Avai lable
OMC-R System Admin, GSR8 1.8.x.0 68P02901W19-R OMC-R System Admin, GSR9 1.9.x.0 68P02901W19-S OMC-R Clean Install, GSR8 1.8.x.0 OMC-R Clean Install, GSR9 1.9.x.0 NHA Release Notes OMC-R Release Notes GSR8 1.8.x.0 OMC-R Release Notes GSR9 1.9.x.0 68P02901W47-R 68P02901W47-S 68P02900W77-S 68P02901W74-R 68P02901W74-S
Hardware that will not be supported in GSM_G_OMCR_079 GSR9 NBI Release Notes [where applicable] 68P02901W73 COP Software Release Notes [where
applicable]
68P02900W69 68P02901W70
OSI Software Release Notes [where

applicable]
Datagen Software Release Notes [where 68P02900W76

applicable]
6.3
Migration Prerequisites Ensure that each of the following prerequisites are available before commencing the migration. Software Motorola Patches and Jumpstart, Ultra Client GSR8 1.8.x.0 Single Platform Processor DVDs Motorola GSR9 1.9.0.0.X inc OMC Software and Jumpstart Motorola GSR9 1.9.0.0.X Additional OMC Software DVDs X25 Licence for the target platform [ transferred from source platform ] RTF Licence for the target platform [ transferred from source platform ] StorEdge Enterprise Backup Software License for the target platform [where applicable] NBI Corba Server [where applicable] Hardware N20/N440/SF4800/4900 Platform Documentation OMC-R System Admin, GSR8 1.8.x.0 OMC-R System Admin, GSR9 1.9.x.0 OMC-R Clean Install, GSR8 1.8.x.0 OMC-R Clean Install, GSR9 1.9.x.0 NHA Release Notes OMC-R Release Notes GSR8 1.8.x.0 OMC-R Release Notes GSR9 1.9.x.0 Hardware that will not be supported in GSR9 NBI Release Notes [where applicable] COP Software Release Notes Part Number 68P02901W19-R 68P02901W19-S 68P02901W47-R 68P02901W47-S 68P02900W77-S 68P02901W74-R 68P02901W74-S GSM_G_OMCR_079 68P02901W73 68P02900W69 Available Available
Available
6.4
Systems Backup Task Description A full backup of all the file systems on the different processors MUST be performed BEFORE proceeding with the upgrade. This should include the Single Platform Processor and GUI Servers. A level-0 archive of the omc_db and mib_db databases on the Single Platform Processor MUST be performed - this is essential for rollback/recovery purposes. Refer to [3] for details of the backup procedures.
6.5
Verify the GSR9 DVD Media Task Description Validate the DVD media. Ensure that this task is completed on all GSR9 DVD media delivered. Pre-checks - Ensure that the task is completed as user root on the Single Platform Processor - Note that this script can take a number of hours to complete. Its advised to run a check on the DVD media well in advance of plans to start verification and/or upgrade. Task Steps OMC Software and Jumpstart DVD Insert the first DVD, GSR9 1.9.0.0.X OMC Software and Jumpstart DVD into the DVD drive, then execute the command:
/cdrom/cdrom0/s0/suninstall/check_dvd
If the command above returns anything other than No Errors were detected then DO NOT continue with the upgrade and contact the relevant support organisation. Additional OMC Software DVD Insert the second DVD, GSR9 1.9.0.0.X Additional OMC Software DVD into the DVD drive, then execute the command:
/cdrom/cdrom0/check_dvd
If the command above returns anything other than No Errors were detected then DO NOT continue with the upgrade and contact the relevant support organisation.
6.6 Create the Upgrade Directory 6.6.1 Single Platform Processor Upgrade Setup and Local GUI Server Upgrade Setup Task Description This task will install the necessary upgrade scripts, library files and configuration files to the /var/install/upgrade directory. Pre-checks - Ensure that the GSR9 OMC Software and Jumpstart DVD is in the media drive in the Single Platform Processor/GUI Server. - Ensure that the task is completed as user root on the Single Platform Processor and GUI Servers. Task Steps
/cdrom/cdrom0/s0/suninstall/upgrade/scripts/upgrade_setup
6.6.2
Remote/Parallel GUI Server Upgrade Setup Task Description This task will share the contents of the DVD on the Single Platform Processor to the GUI Server and install the necessary upgrade scripts, library files and configuration files to the /var/install/upgrade directory on the GUI Server. Pre-checks - Ensure that the GSR9 OMC Software and Jumpstart DVD is in the media drive in the Single Platform Processor. - Ensure that no media is present in the media drive of the GUI Server. - Ensure that /cdrom/cdrom0 is not already mounted on the GUI Server. - Ensure that ssh is configured between the GSR9 Single Platform Processor and GSR8 GUI Server. - Ensure that the Single Platform Processor tasks which are described below, are completed as user root on the Single Platform Processor. - Ensure that the GUI Server tasks which are described below, are completed as user root on the GUI Server. Task Steps GUI Server To enable the GUI server to access the DVD share from the Single Platform Processor, ssh must be setup correctly using the following commands: Edit the file /etc/ssh/sshd_config to allow: PermitRootLogin yes Re-start secure services using: /etc/init.d/sshd stop /etc/init.d/sshd start
Single Platform Processor To make the DVD media available complete the following to share the media from the Single Platform Processor:
/cdrom/cdrom0/s0/suninstall/upgrade/scripts/share_dvd share <GUI Server>
GUI Server Run the upgrade_setup script:

Ensure that where any procedures are being carried out remotely or in parallel on GUI Server(s) that the media has been shared from the Single Platform Processor. To unshare the media from the Single Platform Processor complete the following:
/cdrom/cdrom0/s0/suninstall/upgrade/scripts/share_dvd unshare <GUI Server>
6.7 6.7.1
General Preparation System Cleanup Single Platform Processor ONLY Task Description Refer to [3] for details on how to carry out the procedures below. This task will guide the user through some basic system cleanup. As a group of files are identified for deletion the user will be prompted to confirm that this deletion can take place. Pre-checks The following free space needs to be available on each machine before beginning the upgrade. / (root) 20% /usr/omc 20% /usr/omc/ne_data 30% Task Steps Execute the following script as user root to do some initial tidy up on the Single Platform Processor. This script will guide the user through some basic system cleanup. As a group of files are identified for deletion the user will be prompted to confirm that this deletion can take place. It is NOT the intention of this script to ensure that sufficient space is available on the system; it will only act as an aid to system cleanup. In the case where files are not deleted it is the responsibility of the user to ensure that sufficient space is made available to comply with the guidelines detailed above.
/var/install/upgrade/scripts/system_cleanup
Examine the contents of the system_cleanup logfile at: /usr/omc/logs/system_cleanup.log /usr/omc Files and Directories Ensure that 30% of /usr/omc/ne_data is free. This is to ensure that there is sufficient space if statistics are to be preserved through the upgrade. Likely places to save space are: Old log files in /usr/omc/ne_data/cell_analysis/log (If COP tools are installed) Old unloaded stats in /usr/omc/ne_data/unload_stats (Older than 3-4 days) Old loads in /usr/omc/ne_data/dbroot Old databases in /usr/omc/ne_data/dbroot
Check with Configuration Management personnel on databases that can be removed. Some systems have several N-1 and N-2 BSS point loads. The old loads can be removed through load management on the OMC_R GUI. If a load is in use on a BSC or RXCDR, then GUI code prevents removal of the load. 6.7.2 X.25 Configuration Single Platform Processor ONLY If the system is configured as a high-end system, but without the extra physical links configured the following lines must be added to the x25_config file in order to correspond to entries in the high-end STARTUP.LIST file. Using an editor of your choice append the entries shown below to the end of the /usr/omc/config/global/x25_config using the appropriate unique x25 address. In general the following rule can be applied for the x25 addresses of the extra Uploader processes: For Uploader process 3 use the x25 address of Uploader process 1 and port number <a> For Uploader process 4 use the x25 address of Uploader process 2 and port number <b> NOTE: the addresses used below are for example purposes only, substitute with addresses already in the x25_config file:
8 x25_chan8 <a> 2020130001299 H - OMC_PU X25 128 2 50 9 x25_chan9 <b> 2020130001299 H - OMC_PU X25 128 2 50
6.7.3
Other pre-upgrade checks Ensure that all users can create and write to the log files created during the upgrade procedure: Execute the following command as user root:
chmod 777 /var/install/logs
6.8
Configuring the Verify, Upgrade and Migration Phases for the Single Platform Processor Task Description Certain parts of verify and upgrade for the Single Platform Processor can be configured to maintain extra customer specific data. It should be noted that this procedure does not maintain symbolic links. NOTE: Only users with an entry in /etc/passwd will have their /home directories migrated over. Extra files and directories added to /home are not migrated over. NOTE2: The following list of directories/files are not currently maintained in the migration. If you wish to retain these directories/files when migrating, then please add them to the file /var/install/upgrade/config/altern_migrate_file_list.dat
/usr/omc/config/global/cellX/ExportNbr.CNFG /usr/omc/config/global/cellX/RF.CNFG /usr/omc/config/global/cellX/RF.CNFG.TEMPLATE /usr/omc/config/global/cellX/SWAPSITECELLS.CNFG /usr/omc/config/global/cellX /usr/omc/config/global/batch
Pre-checks Ensure that the task is completed as user root on the Single Platform Processor:
Task Steps These steps are optional and only need to be completed if the customer wishes to maintain extra information that is not part of the standard upgrade/migration. Configuring the upgrade to maintain extra files and directories As part of upgrade procedure certain files and directories are maintained. The file /var/install/upgrade/config/migrate_file_list.dat lists these files and directories. Should extra files and directories be required they can be added to this file in the following format:
<Full file/directory name, including full path>
An example from the migrate_file_list.dat for a file to maintain is as follows:

/usr/omc/config/global/SITE.MAP
An example from the migrate_file_list.dat for a directory to maintain is as follows:

/etc/opt/SUNWconn/x25/config
Add any extra files or directories to this file, in the format described above, as desired. Configuring the migration to maintain extra files and directories As part of the migration procedure certain files and directories are maintained. The file /var/install/upgrade/config/altern_migrate_file_list.dat lists these files and directories. Should extra files and directories be required they can be added to this file in the following format:
<Full file/directory name, including full path>
An example from the altern_migrate_file_list.dat for a file to maintain is as follows:

/usr/omc/config/global/SITE.MAP
An example from the altern_migrate_file_list.dat for a directory to maintain is as follows:

/etc/opt/SUNWconn/x25/config
Add any extra files or directories to this file, in the format described above, as desired. Maintain DNS configuration If DNS is being used, rename the /etc/resolv.conf file on the Single Platform Processor before starting the upgrade to GSR9. The file can be renamed to its original name after the upgrade has completed.
mv /etc/resolv.conf /etc/resolv.conf.GSR9
As user omcadmin append this line to the following files if not already present: /usr/omc/config/global/env/pmProcConfig.csh and /usr/omc/config/global/env/mibProcConfig.csh
unsetenv STATE_ON_AUDIT
7.0
7.1
Single Platform Processor and GUI Server - Verification Procedure Tasks

Verify the Single Platform Processor Task Description Verify that the system hardware, metadevice configurations are correct. There is a lengthy disk test carried out as part of this system verification. Each disk will be tested individually and it will therefore take a number of hours to complete depending on the number of disks in the system. For details, refer to Appendix C for typical script output. Pre-checks - Ensure that the GSR9 OMC Software and Jumpstart DVD is in the media drive in the Single Platform Processor. - Ensure that the task is completed as user root on the Single Platform Processor: Task Steps
/var/install/bin/verify_platform
7.2
Verify the GUI Server Task Description Verify the GSR8 1.8.x.0 system and that the system hardware is correct. Refer to Appendix D for typical script output. Pre-checks - Ensure that the GSR9 OMC Software and Jumpstart DVD is in the appropriate media drive. - Local Upgrade: media should be in GUI Server drive. - Remote/Parallel Upgrade: media should be in Single Platform Processor drive. If you are using the media drive on the Single Platform Processor then ensure that the GSR9 1.9.x.0 OMC-R Media is in the media drive in the Single Platform Processor and execute the following:
/cdrom/cdrom0/s0/suninstall/upgrade/scripts/share_dvd share <GUI
Server>
Steps
Ensure that the task is completed as user root on the GUI Server.
/var/install/bin/verify_platform
If the media drive on the Single Platform Processor was shared to the GUI Server, then execute the following commands to unshare the media from the Single Platform Processor:
/cdrom/cdrom0/s0/suninstall/upgrade/scripts/share_dvd unshare <GUI
Server>
7.3
Examine Verify Logfiles Task Description To examine the contents of the verify log files to ensure that any errors captured in the log files are analyzed on the Single Platform Processor and GUI sever platforms. Pre-checks Ensure that the task is completed as user root on the Single Platform Processor and the GUI Server.
Task Steps Examine the contents of the following log file: - /var/install/logs/verify_platform/verify_platform.log If any errors exist in this log file, contact the relevant support organisation.
8.0
8.1
Single Platform Processor - Upgrade Procedure Tasks

Upgrade Procedure Work Flow
Figure 1:
Single Platform Processor Upgrade Procedure
8.2
Tools and Adjunct Products Task Description This section will describe tasks that need to be completed in advance of the OMC Single Platform Processor upgrade for other tools and products connected to the OMC. In this section, actions are required for the NHA, NBI and COP tools. Pre-checks - Ensure that the tasks are completed as user root on the appropriate platform. Task Steps - An NHA stop is required before the OMC upgrade. Refer to [4] for details of this procedure.
Where COP is installed on a GUI Server then all of the cron jobs that are running on that GUI server must be stopped. Execute the following command on such systems:
/etc/init.d/cron stop
The NBI connection to this OMCR must be disabled before the OMC upgrade. Refer to [8] for details of this procedure.
8.3
Upgrade and Reboot the Single Platform Processor Task Description Upgrade the Single Platform Processor to a Solaris 10, GSR9 1.9.x.0 platform. Users should not be using areas temporarily mounted for the upgrade, as this could cause upgrade failure. The upgrade asks a number of questions which require response. In GSR9 the upgrade will prompt and gather responses to all these questions at the beginning. The following questions will be asked: 1. "Keep PM Data and delete old unl files (y/n): " This question refers to whether data from the PM database should be maintained. If a y response is given the upgrade will maintain PM data. If a n response is given, the upgrade will not maintain the data. 2. "Keep Custom Stats (y/n): " [NOTE: this question is ONLY asked when response for Q1 is n] This question refers to whether Custom Statistics data from the PM database should be maintained. If a y response is given the upgrade will maintain Custom Statistics data. If a n response is given, the upgrade will not maintain the Custom Statistics data. 3. "Cutover to latest release automatically (y/n): " This question refers to whether during the upgrade the cutover should proceed without need for further input. If a y response is given, the upgrade will automatically proceed with the cutover. If a n response is given, the upgrade script will pause during execution and wait for further user input before proceeding with the cutover. 4. "Stop the OMC (y/n): " This question refers to whether during the upgrade the OMC processes should be automatically stopped without need for further input. If a y response is given, the upgrade will automatically stop the OMC processes. If a n response is given, the upgrade script will pause during execution and wait for further user input before stopping the OMC processes. 5. "Reboot automatically (y/n): " This question refers to whether during the upgrade the system should automatically reboot without need for further input. If a y response is given, the upgrade will automatically proceed with the required system reboots. If a n response is given, the upgrade script will pause during execution and wait for further user input before proceeding with system reboots.
It is important to plan in advance how these questions should be responded to. It is also important to understand the implications of a y or n response to each individual question. For example, a n response to questions 3 will mean that the user will be asked the question again later the in upgrade. A n response to questions 1 or 2 will not involve user interaction again, and PM related data will not be maintained. The following details the steps taken by the upgrade script (this is not an exhaustive list but points out the highlights of the upgrade): (R) Below indicates that a response is required during this step. 1. Gather responses to upgrade questions(R) 2. Validate system hardware configuration 3. Stop the system cron 4. Re-verify hardware component operation and system mirroring 5. Update the savecore device 6. Stop PM Informix instance [ GSR8 side ] NOTE: The parser is disconnected from the PM database (omc_db) from this point in the upgrade. Stats outage commences at this point. 7. Detach and clear system mirrors 8. Upgrade eeprom bootdevice setting 9. Restart PM Informix instance [ GSR8 side ] 10. Configure disksuite metadevice configuration 11. Install Solaris 10 Operating System 12. Install GSR9 OMC Software and associated third party products 13. Unload PM database [NOTE: in the 1900.17 load, Q1 and Q2 described above will be repeated during this phase] (R) 14. Configure Informix [ GSR9 side ] 15. Configure CDE environment [ GSR9 side ] 16. Initialize Informix [ GSR9 side ] 17. Cutover to GSR9 load [ GSR9 side ] 18. Attach MIB database metadevices 19. Migrate users accounts and cronjobs 20. Migrate OMC files 21. Generate scripts to reboot system 22. Stop the OMC [outage commences at this point] 23. Stop all Informix instances 24. Detach MIB database metadevices 25. Tidy up upgrade related temporary file 26. Reboot the system 27. Migrate MIB database For more details, refer to Appendix C for typical script outputs. Pre-checks - Ensure that the GSR9 OMC Software and Jumpstart DVD is in the media drive in the Single Platform Processor. - Ensure that the task is completed as user root on the Single Platform Processor:
NOTE: As the Single Platform Processor does not have a graphics card, any steps in this chapter which are executed on the platform being upgraded will need to be completed using a direct terminal connection, until the system is available on the network.
Task Steps
/var/install/upgrade/scripts/upgrade
If messages regarding load_modules and open_modules appear on the console during the upgrade, they can safely be ignored. After the upgrade script has completed the system will be rebooted. Two complete reboots will occur for all Platforms. 1. During the first reboot, metadevice reconfiguration will be completed. 2. During the second reboot, the MIB database will be migrated to the GSR9 1.9.x.0 format. In some cases the system reboots will appear almost complete ensure that the system is not logged into until all the reboots described above have completed FULLY and the login prompt is available. SSH keys are automatically configured during the upgrade for all users in Unix groups omc and omcread. If the user already had a .ssh directory, this is moved to .ssh.orig.<PID>, where PID is the process ID of the script running during that part of the upgrade. Any keys that are required to be kept from the previous release need to be copied manually to the files in the new .ssh directory. See Appendix H for further details on SSH. To ensure that the CDE desktop environment is fully configured, run the following command:
/usr/omc/current/sbin/cde_install
Additional configuration if DNS is being used If DNS is used as a supplementary naming service to NIS, ensure that NFSMAPID_DOMAIN is set to the NIS domain in /etc/default/nfs. For example:
# Specifies to nfsmapid daemon that it is to override its default # behaviour of using the DNS domain, and that it is to use 'domain' as # the domain to append to outbound attribute strings, and that it is to # use 'domain' to compare against inbound attribute strings. NFSMAPID_DOMAIN=<domain>
Where <domain> is the NIS domainname used by the OMC-R, for example:
NFSMAPID_DOMAIN=omcadmin _________________________________________________________________________________________________ Doc ID: OSS-GSR8-CUSTSUP-RLS-003 Doc Version: 3.0 24
Restore the /etc/resolv.conf file:

mv /etc/resolv.conf.GSR9 /etc/resolv.conf
8.4
Examine Upgrade Logfiles Task Description To examine the contents of the upgrade log files to ensure that any errors captured in the log files are analyzed. Pre-checks Ensure that the task is completed as user root on the Single Platform Processor.
Task Steps Examine the contents of the following log files: - /var/install/logs/upgrade/upgrade.log - /usr/omc/logs/cutover.log - /usr/omc/logs/pm_db_unload.log* - /usr/omc/logs/SQLMibMigration.log If any errors exist in these log files, contact the relevant support organisation. NOTE: The following error can be ignored in the /var/install/logs/upgrade/upgrade.log file: autopush: ERROR: File /etc/opt/SUNWconn/x25/x25mod.autopush: could not configure autopush for line 2 autopush: ERROR: Major/minor already configured. GUI Server The Single Platform Processor upgrade procedure has progressed to a point where the GUI server platform upgrades can now commence, while the upgrade procedure is being completed on the Single Platform Processor. See Chapter 12.0 for details of the GUI server upgrade procedure. 8.5 Install additional software patches Task Description Additional software patches need to be manually installed from the second GSR9 OMCR DVD. Pre-checks Ensure that the tasks are completed as user root on the Single Platform Processor. Task Steps Ensure that the informix user owns the .cshrc file:
chown informix:informix /usr/informix/.cshrc
Reboot the OMCR to ensure that all processes are started correctly:
/usr/sbin/shutdown i6 g0 y
Insert the second GSR9 OMCR DVD Additional OMC Software into the DVD drive. If the drive already contains a DVD, eject it using the following command:
eject cdrom
Enter the following command as one command to install the patches from the DVD:
/cdrom/cdrom0/suninstall/bin/install_patches \ --patch_dir /cdrom/cdrom0/suninstall/Patches \ --patch_order /cdrom/cdrom0/suninstall/Patches/patch_order
Some error messages may be shown if the install_patches script attempts to install patches that are already installed on the system as shown below. These errors can be safely ignored.
# # /cdrom/cdrom0/suninstall/bin/install_patches --patch_dir /cdrom/cdrom0/suninstall/Patches --patch_order /cdrom/cdrom0/suninstall/Patches/patch_order Patches to be installed: 3 Now installing patches...please wait... Patches Patches Patches Patches installed: installed: installed: installed: 0/3 1/3 2/3 3/3 (0%) (33%) (66%) (100%)
Patch install complete. 3 patches failed to install. Please check logfile for details. 119059-20 121118-10 122660-07 Logfile is /var/install/logs/patch_install.log
Additional information is available in the patch_install.log file:

Patch install started on Wed Jul 25 17:20:18 BST 2007 Installing 119059-20 Validating patches... Loading patches installed on the system... Done! Loading patches requested to install. Done! _________________________________________________________________________________________________ Doc ID: OSS-GSR8-CUSTSUP-RLS-003 Doc Version: 3.0 26
2005, Motorola General Business Use The following requested patches are already installed on the system Requested to install patch 119059-20 is already installed on the system. No patches to check dependency. Installing 121118-10 Validating patches... Loading patches installed on the system... Done! Loading patches requested to install. Done! The following requested patches are already installed on the system Requested to install patch 121118-10 is already installed on the system. No patches to check dependency. Installing 122660-07 Validating patches... Loading patches installed on the system... Done! Loading patches requested to install. Done! The following requested patches are already installed on the system Requested to install patch 122660-07 is already installed on the system. No patches to check dependency. Patch install completed on Wed Jul 25 17:20:25 BST 2007
8.6
Install StorEdge Backup Software Task Description If the StorEdge Backup Software is required, it must be manually installed from the second GSR9 OMCR DVD. Pre-checks Ensure that the tasks are completed as user root on the Single Platform Processor. Task Steps Insert the second DVD Additional OMC Software into the DVD drive. If the drive already contains a DVD, eject it using the following command:
eject cdrom
Copy the StorEdge Enterprise Backup software packages from the DVD:
cp rp /cdrom/cdrom0/suninstall/backup /var/install cp /cdrom/cdrom0/suninstall/lib/backup.lib \ /var/install/lib cp /cdrom/cdrom0/suninstall/data/package_list \ /var/install/data cp /var/install/backup/tape-mgr /var/install/bin
Install the software:

/var/install/bin/tpp_installer Installing StorEdge Backup... Done Installing Solstice Backup Module for Informix... Done
For further information about licensing the StorEdge software, see the OMCR clean install guide [2]. 8.7 Network Performance Problem Refer to Appendix A.3 in cases where network performance is not as expected. Mandatory PM Database Tasks
8.8
ENSURE that ALL THESE MANDATORY TASKS ARE COMPLETED AFTER THE SYSTEM HAS COME UP
8.8.1 Update statistics within the PM database Task Description Update statistics within the PM database. Pre-checks Ensure that the tasks are completed as user omcadmin on the Single Platform Processor. Task Steps
/usr/omc/current/sbin/update_db_statistics
8.8.2
Complete a PM Resync Task Description Complete a PM Resync through the OMC-R GUI. Pre-checks Ensure that the tasks are completed as user omcadmin on the Single Platform Processor. Task Steps
Start up an OMC-R GUI session Once a GUI session has been started up successfully a PMResync should be performed.
NOTE: If the PM Resync appears to fail, then repeat the PM Resync task.
8.8.3 PM_HOURLY_STATS variable Task Description To examine the setting of the PM_HOURLY_STATS variable. Pre-checks Ensure that the tasks are completed as user omcadmin on the Single Platform Processor. Task Steps Check the latest parser file, for example fpomcaudit* in /usr/omc/logs/. Check if the following message appears after the OMC has restarted: "Invalid Duration, which will result in a .bad_header file." If this message does not appear in the fpomcaudit* log then skip to Section 8.6.5 If this message appears then the customer must set the PM_HOURLY_STATS variable to either ON or OFF in the OMC.CNFG file. This change can take place without the requirement of an OMC stop/start by following this procedure:
cd /usr/omc/config/global
Using an editor or choice, edit the OMC.CNFG file. Uncomment the setting for PM_HOURLY_STATS and alter the environment variable so it looks like either one of the following: PM_HOURLY_STATS=ON OR PM_HOURLY_STATS=OFF
Save and exit the file. Now execute the following

omctool -m PARSER_1 c
To make the change a permanent one, set the value of the variable in /usr/omc/config/global/env/pmProcConfig.csh: setenv PM_HOURLY_STATS ON
8.8.4
PM parsing of .bad_header Files Task Description To rename and parse any .bad_header files which exist in the BSS directories. Pre-checks Ensure that the task is completed as user root on the Single Platform Processor. Task Steps
/var/install/upgrade/scripts/badheader_tidyup
In the event of a file not parsing correctly, the extension .bad_header will automatically be re-added to the file. Check the current /usr/omc/logs/fpomcaudit log for more details. 8.8.5 PM Database Maintenance Setup Task Description Ensure that a new fragment exists in the PM database. Pre-checks Ensure that the task is completed as user root on the Single Platform Processor. Task Steps If the upgrade does not complete by 4:02am the default time for the omc_db_maint cron to execute OR if the upgrade does not complete before the customer configured start time for the omc_db_maint cron to run, then execute the following script as user root:
/usr/omc/sbin/omc_db_maint
Check the omc_db_maint logfile in /usr/omc/logs, to ensure that the script has completed successfully.
8.9
Check OMC audit log file for possible errors Task Description Check the Single Platform Processor OMC log file for a specific FM error. Pre-checks - Ensure that the tasks are completed as user root on the appropriate platform. Task Steps - Open the latest log file in /usr/omc/logs:
/usr/omc/logs/omcaudit<YYYYMMDD>
Check if the following error is present in the log:
2007-07-25 18:05:44 FM_AUDIT(1453) FM_get_line_status(): can't open /usr/omc/current/config/fm/disconnect, error is 2 2007-07-25 18:05:44 FM_AUDIT(1453) FM_get_line_status() failed.
If the error is present, run the following command as root:

devfsadm
Then perform an OMC stop/start as user omcadmin:

omc stop Stopping the OMC omc start Starting the OMC
8.10 Tools and Adjunct Products Task Description This section will describe tasks that need to be completed after the OMC Single Platform Processor upgrade for other tools and products connected to the OMC. In this section, actions are required for the NHA, NBI and COP tools. Pre-checks - Ensure that the tasks are completed as user root on the appropriate platform. Task Steps - If you have an NHA, run the script nha_omc_upgrade on the NHA and then start the NHA. Refer to [4] for details of this procedure. - If COP Tools are installed on this OMCR Single Platform Processor then refer to [9] for relevant administration details. - If there are any other tools or adjunct products related to the OMC they can be upgraded at this stage, or at the appropriate time, for example, OSI, Datagen. - If NBI is in use on this OMCR Single Platform Processor then refer to [8] for details of activities to be carried out to update NBI services.
8.11 Complete Filesystem Backup Task Description To complete a full backup of file systems and databases after the upgrade has completed. Pre-checks Ensure that the task is completed as user root on the Single Platform Processor, unless the backup procedure specifies otherwise.
Task Steps A full backup of all the file systems on the different processors can now be performed. For details of the backup procedures, refer to [3]. A level-0 archive of the omc_db and mib_db databases can also be performed at this stage. If Solstice backup has been configured to perform database backups on the system previously by running the configure_solstice script, then re-run this.
/usr/omc/sbin/configure_solstice
8.12 Re-Mirror the System Task Description When the GSM OMC-R Single Platform Processor has been deemed stable and the customer is satisfied with the functionality, it is advisable to complete the disk mirroring. It should be noted that there is no automatic rollback to GSR8 1.8.x.0 release after this procedure has been completed. The only possible method is by means of a Complete File System Recovery. Pre-checks - Ensure that the task is completed as user root on the Single Platform Processor - Ensure that a GSR9 DVD is in the Single Platform Processor. Task Steps
/var/install/upgrade/scripts/commit
8.13 Examine Commit Logfiles Task Description To examine the contents of the commit log files to ensure that any errors captured in the log files are analyzed.
Pre-checks Ensure that the task is completed as user root on the Single Platform Processor.
Task Steps Examine the contents of the following log file: - /var/install/logs/upgrade/commit.log If any errors exist in this log file, contact the relevant support organisation.
9.0
Single Platform Processor - Rollback Procedure Tasks
This rollback procedure is in effect undoing the operations performed during the upgrade. The rollback procedure supports the following scenarios: SCENARIO One: Either the upgrade script completed successfully and the system has rebooted or the upgrade script has not completed successfully but the system has rebooted. SCENARIO Two: The upgrade script has not completed successfully and the system has not rebooted. Based on the rollback scenario which has been encountered, the appropriate section below should be completed. 9.1 Tools and Adjunct Products Task Description This section will describe tasks that need to be completed before the OMC Single Platform Processor rollback for other tools and products connected to the OMC. In this section, actions are required for the NHA tool. Task Steps - You will need to do an NHA stop before the OMC rollback. Refer to [4] for details. 9.2 Back Out Procedure Scenario One Task Description Roll the system back to its original configuration. In this scenario one of the following has occurred: (i) the upgrade script has completed successfully and the system has rebooted. (ii) the upgrade script has not completed successfully but the system has rebooted. The following details the steps taken by the rollback script (this is not an exhaustive list but points out the highlights of the rollback): (R) Below indicates that a response is required during this step. 1. 2. 3. 4. 5. 6. 7. 8. 9. Cleanup any setup remaining from the previous upgrade Stop the Informix instances Stop the OMC (R) Clear system mirrors Re-initialize the GSR8 mirrors Attach mirrors Reset the savecore device Restart the Informix instances Restart the OMC
Refer to Appendix C for typical script output.

Pre-checks - Ensure that the task is completed as user root on the Single Platform Processor. - As the N20, Netra440 and Sunfire4800/4900 platforms do not have a graphics card, any steps in this chapter which are executed on the system being rolled back, will need to be completed through a direct terminal connection, until the system is available on the network. - Ensure that a GSR9 DVD is in the Single Platform Processor. Task Steps Collect the logfiles associated with the rollback before proceeding. Complete the following as user root
tar cvf /UPGRADE_LOGS.TAR /usr/omc/logs /var/install/logs . /var/install/upgrade/scripts/varinit.sh mount /dev/dsk/$MIRROR /mnt cp /UPGRADE_LOGS.TAR /mnt umount /mnt
Should these logfiles be required by any Motorola Support Organization they can be retrieved from the /(root) directory once the system is rolled back to GSR8.
/var/install/fallback_to_old_install
This will reboot the system. Once this reboot is complete continue with the following:
/var/install/upgrade/scripts/rollback
The cron tab files are copied back from the GSR9 side to GSR8. Therefore the following needs to be executed as root to ensure that the GSR8 crons are present once more:
cp -r /omcgen/1900_backup/root.backup /var/spool/cron/crontabs/root cp -r /omcgen/1900_backup/omcadmin.backup /var/spool/cron/crontabs/omcadmin
9.3
Back Out Procedure Scenario Two Task Description - Roll the system back to its original configuration. In this scenario the upgrade script has not completed successfully and the system has not rebooted. The following details the steps taken by the rollback script (this is not an exhaustive list but points out the highlights of the rollback): (R) Below indicates that a response is required during this step. 1. Cleanup any setup remaining from the previous upgrade 2. Stop the Informix instances
3. 4. 5. 6. 7. 8. 9.
Stop the OMC (R) Clear system mirrors Re-initialize the GSR8 1.8.x.0 mirrors Attach mirrors Reset the savecore device Restart the Informix instances Restart the OMC
Refer to Appendix C for typical script output. Pre-checks - Ensure that the task is completed as user root on the Single Platform Processor. - As the N20, Netra440 and Sunfire4800/4900 platforms do not have a graphics card, any steps in this chapter which are executed on the system being rolled back will need to be completed through a direct terminal connection, until the system is available on the network. - Ensure that a GSR9 DVD is in the Single Platform Processor. Task Steps
reboot -- mirrordisk
This will reboot the system. Once this reboot is complete continue with the following:
9.4
Examine Rollback Logfiles Task Description To examine the contents of the rollback log files to ensure that any errors captured in the log files are analyzed. Pre-checks Ensure that the task is completed as user root on the Single Platform Processor.
Task Steps Examine the contents of the following log file: - /var/install/logs/upgrade/rollback.log If any errors exist in this log file, contact the relevant support organisation. As part of the rollback procedure, the tracker files which were used in the upgrade are moved to /var/install/logs/upgrade/tracker.rolledback.<timestamp> 9.5 Retain Rollback Directory Task Description To maintain the rollback directory.
Pre-checks Ensure that the task is completed as user root on the Single Platform Processor
Task Steps
cd /var/install mv upgrade old_upgrade
NOTE: As the upgrade directory has now been renamed, when attempting the upgrade again, the procedure will have to be re-started from Chapter 6 - Preparation. 9.6 Tools and Adjunct Products Task Description This section will describe tasks that need to be completed after the OMC Single Platform Processor rollback for other tools and products connected to the OMC. In this section, actions are required for the NHA tool. Task Steps If you have an NHA, after you have completed the OMC rollback you will need to restart the NHA. Refer to [4] for details of this procedure. 9.7 Mandatory PM Database Tasks
ENSURE THAT ALL THESE MANDATORY TASKS ARE COMPLETED AFTER THE SYSTEM HAS COME UP
9.7.1 Update statistics within the PM database
Task Description Update statistics within the PM database. Pre-checks Ensure that the tasks are completed as user omcadmin on the Single Platform Processor. Task Steps
9.7.2
Complete a PM Resync
NOTE: This step involves launching a GUI on the OMC-R Single Platform Processor. If you are displaying this GUI to a GUI Server, its recommended to include a reboot on the GUI server to refresh stale NFS handles. Once the reboot is complete, ensure that an xhost + command has been executed locally.
Before launching the GUI ensure that your DISPLAY variable has also been set correctly. Task Description Complete a PM Resync through the OMC-R GUI. Pre-checks Ensure that the tasks are completed as user omcadmin on the Single Platform Processor. Task Steps
9.7.3
PM_HOURLY_STATS variable
Task Description To examine the setting of the PM_HOURLY_STATS variable. Pre-checks Ensure that the tasks are completed as user omcadmin on the Single Platform Processor. Task Steps Check the latest parser file, for example fpomcaudit* in /usr/omc/logs/. Check if the following message appears after the OMC has restarted: "Invalid Duration, which will result in a .bad_header file." If this message does not appear in the fpomcaudit* log then skip to Section 9.7.5 If this message appears then the customer must set the PM_HOURLY_STATS variable to either ON or OFF in the OMC.CNFG file. This change can take place without the requirement of an OMC stop/start by following this procedure:
Using the vi editor edit the OMC.CNFG file Uncomment the setting for PM_HOURLY_STATS and alter the environment variable so it looks like either one of the following: PM_HOURLY_STATS=ON OR PM_HOURLY_STATS=OFF Save and exit the file. Now execute the following
To make the change a permanent one, set the value of the variable in /usr/omc/config/global/env/pmProcConfig.csh: setenv PM_HOURLY_STATS ON PM parsing of .bad_header Files
9.7.4
Task Description To rename and parse any .bad_header files which exist in the BSS directories. Pre-checks Ensure that the task is completed as user root on the Single Platform Processor. Task Steps
/var/install/old_upgrade/scripts/badheader_tidyup
In the event of a file not parsing correctly, the extension .bad_header will automatically be re-added to the file. Check the current /usr/omc/logs/fpomcaudit log for more details. 9.7.5 PM Database Maintenance Setup
Task Description Ensure that a new fragment exists in the PM database. Pre-checks Ensure that the task is completed as user root on the Single Platform Processor. Task Steps If the rollback does not complete by 4:02am the default time for the omc_db_maint cron to execute OR if the rollback does not complete before the customer configured start time for the omc_db_maint cron to run, then execute the following script as user root:
10.0 Single Platform Processor Migration Procedure Tasks

The Single Platform Processor Migration Procedure involves the replacement of an existing E3500 platform with one of N20, N440 or Sunfire 4800/4900. For GSR9 this procedure applies to the migration of an E3500 platform ONLY. For the purposes of this document the existing platform will be referred to as the Source Platform and the replacement platform the Target Platform, and for illustrative purposes the example used in this section will refer to E3500 as the source platform, and SunFire 4900 as the target platform. 10.1 Single Platform Processor Migration Procedure Work Flow
Figure 2:
Single Platform Processor Migration Procedure
10.2 Clean Install the Target (SF4900) Platform Task Description The TARGET (SF4900) platform must be clean installed in advance of the remaining migration procedure. It is mandatory that the TARGET (SF4900) platform is clean installed with the same hostname, IP address and naming service domain name as the existing SOURCE (E3500) platform. (that is, the E3500 platform being replaced).
Complete the clean install procedure for the platform as described in [2], except DO NOT complete the sections entitled: The /etc/dfs/dfstab file Modifying the /etc/hosts file Creating the /etc/hosts.equiv file As the Single Platform Processor does not have a graphics card, any steps in this chapter which are executed on the TARGET (SF4900) platform will need to be completed through a direct terminal connection, until the system is available on the network (system will be available on the network once step 10.4 is completed). Task Steps - Refer to [2] for details of the clean install procedure and complete this procedure before continuing. The Ethernet cable should be disconnected for the duration of the clean install procedure. Instructions will be given later on connecting the Ethernet cable in the TARGET (SF4900) platform. - Before proceeding with the migration ensure that ssh is configured between the source and target platform. Refer to Appendix H for details on completing this setup. 10.3 Tools and Adjunct Products Task Description This section will describe tasks that need to be completed after the OMC Single Platform Processor upgrade for other tools and products connected to the OMC. In this section, actions are required for the OSI tool.
THIS SECTION APPLIES TO MIGRATIONS FROM A GSR8 SOURCE (E3500) PLATFORM ONLY.
Task Steps - If there are any other tools or adjunct products related to the OMC can they be upgraded at this stage, or at the appropriate time, for example. OSI, Datagen. 10.4 Update TARGET (SF4900) Platform IP Address and Domain Task Description Once the TARGET (SF4900) platform has been clean installed the IP address will need to be temporarily changed in order to allow the SOURCE (E3500) and TARGET (SF4900) platforms to coexist on the same network while the migration is taking place. The TARGET (SF4900) platform will automatically reboot during this step. Complete this section regardless of the naming service in use but, where NIS is the chosen Naming Service, the domain will be updated automatically during this
reboot. Where NIS is not the chosen Naming Service, ensure that any relevant updates needed are completed before proceeding with the migration. Pre-checks - Ensure that the GSR9 OMC Software and Jumpstart DVD is in the media drive of the TARGET (SF4900) platform. - Ensure that the temporary IP address chosen is unique on the network. - Ensure that the task is completed as user root on the TARGET (SF4900) platform. Task Steps
/cdrom/cdrom0/s0/suninstall/upgrade/scripts/prepare_platform setup
Enter the temporary IP address when prompted. The System will reboot automatically on completion of this script.
During this system reboot the Ethernet cable should be connected to the TARGET (SF4900) platform.
For details on the location of the Ethernet connection, refer to [2]. Login to the TARGET (SF4900) platform as user omcadmin and execute the following:
omc stop
This is the point where Appendix H implementation should be carried out. 10.5 Migrate the SOURCE (E3500) Platform Task Description The migration of the SOURCE (E3500) platform to the TARGET (SF4900) platform will be completed during this step. This involves the transfer of data from both the MIB and PM databases as well as predefined data which is desirable to maintain between the platforms. As this data migration process is completed over the network this may take some time depending on the amount of data to be copied and the speed of the network link available. See Chapter 6, section 6.8 for details of how to configure this step to maintain extra files and directories which may be required. The duration of the migration procedure is entirely dependant on the amount of data being migrated from the SOURCE (E3500) platform to the TARGET (SF4900). Database size will also impact migration duration. Refer to Appendix E for typical script output. The following details the steps taken by the migration script (this is not an exhaustive list but points out the highlights of the migration):
(R) Below indicates that a response is required during this step. 1. Gather responses to migration questions (R) 2. Validate system hardware configuration 3. Enter details of replacement server (R) 4. Sharing and mounting of remote filesystems 5. Migrate user accounts and cronjobs 6. Migrate OMC files 7. Upgrading PM database 8. Stop the OMC (R) [outage commences at this point] 9. Export MIB database 10. Import MIB database 11. Tidy up upgrade related temporary files Pre-checks - Ensure that the GSR9 OMC Software and Jumpstart DVD is in the media drive in the SOURCE (E3500) platform. - Ensure that the task is completed as user root on the SOURCE (E3500) platform. Task Steps - The NBI connection to this OMCR must be disabled before the OMC upgrade. Refer to [8] for details of this procedure. NOTE: Run the upgrade_setup script here ONLY if it has not already been executed in Section 6.6.
/cdrom/cdrom0/s0/suninstall/upgrade/scripts/upgrade_setup /var/install/upgrade/scripts/migrate
10.6 Examine Migration Logfiles Task Description To examine the contents of the migration log files to ensure that any errors captured in the log files are analysed. Any errors noted from the log files should be investigated before proceeding with the remainder of the migration. Where necessary the appropriate support organization should be contacted. Pre-checks Ensure that the task is completed as user root on the SOURCE (E3500) and TARGET (SF4900) platforms.
Task Steps Examine the contents of the following log files on the SOURCE (E3500) platform: - /var/install/logs/upgrade/migrate .log - /usr/omc/logs/pm_db_unload.log
Examine the contents of the following log files on the TARGET (SF4900) platform: - /usr/omc/logs/SQLMibMigration.log. 10.7 Update TARGET (SF4900) Platform IP Address Task Description The SOURCE (E3500) platform must also be removed from the network and the HSI cables must be switched from the SOURCE (E3500) platform to the TARGET (SF4900). Now that the log files have been examined and the TARGET (SF4900) platform is ready to function completely as the Single Platform Processor the temporary IP address must be removed and replaced with the IP address of the SOURCE (E3500) platform. The TARGET (SF4900) platform will automatically reboot during this step. Complete this section regardless of the naming service in use but, where NIS is the chosen Naming Service, the domain will be updated automatically during this reboot. Where NIS is not the chosen Naming Service, ensure that any relevant updates needed are completed before proceeding with the remainder migration. Pre-checks - Ensure that the GSR9 OMC Software and Jumpstart DVD is in the media drive in the TARGET (SF4900) platform. - Ensure that the tasks are completed as user root on the TARGET (SF4900) platform. Task Steps - Ensure that the Ethernet cable is unplugged from the SOURCE (E3500) platform. For details on the location of the Ethernet connection, refer to [2]. - Switch the HSI cables from the SOURCE (E3500) platform to the TARGET (SF4900) platform. It is recommended that before removing the cables from the SOURCE (E3500) platform they are labeled to ensure that they are connected to the TARGET (SF4900) platform correctly. Note that these scripts will initiate a system reboot automatically.
/cdrom/cdrom0/s0/suninstall/upgrade/scripts/ssh_setup.sh /cdrom/cdrom0/s0/suninstall/upgrade/scripts/prepare_platform complete
Complete the following command as user root:

svcadm enable informix/pm svcadm restart omc
10.8 Mandatory PM Database Tasks ENSURE THAT ALL THESE MANDATORY TASKS ARE COMPLETED DURING THE MIGRATION 10.8.1 Update statistics within the PM database Task Description Update statistics within the PM database. Pre-checks Ensure that the tasks are completed as user omcadmin on the TARGET (SF4900) Platform. Task Steps
10.8.2 Complete a PM Resync Task Description Complete a PM Resync through the OMC-R GUI. Pre-checks Ensure that the tasks are completed as user omcadmin on the TARGET (SF4900) Platform. Task Steps
10.8.3 PM_HOURLY_STATS variable Task Description To examine the setting of the PM_HOURLY_STATS variable. Pre-checks Ensure that the tasks are completed as user omcadmin on the TARGET (SF4900) Platform.
Task Steps Check the latest parser file, for example pomcaudit* in /usr/omc/logs/. Check if the following message appears after the OMC has restarted: "Invalid Duration, which will result in a .bad_header file." If this message does not appear in the fpomcaudit* log then skip to Section 10.9.5 If this message appears then the customer must set the PM_HOURLY_STATS variable to either ON or OFF in the OMC.CNFG file. This change can take place without the requirement of an OMC stop/start by following this procedure:
Using the vi editor edit the OMC.CNFG file. Uncomment the setting for PM_HOURLY_STATS and alter the environment variable so it looks like either one of the following: PM_HOURLY_STATS=ON OR PM_HOURLY_STATS=OFF Save and exit the file. Now execute the following:
To make the change a permanent one, set the value of the variable in /usr/omc/config/global/env/pmProcConfig.csh: setenv PM_HOURLY_STATS ON 10.8.4 Parsing of .bad_header Files Task Description To rename and parse any .bad_header files which exist in the BSS directories. Pre-checks Ensure that the tasks are completed as user root or omcadmin, as instructed below, on the TARGET (SF4900) Platform. Task Steps
In the event of a file not parsing correctly, the extension .bad_header will be re-added to the file. Check the current /usr/omc/logs/fpomcaudit log for more details. 10.8.5 PM Database Maintenance Setup Task Description Ensure that a new fragment exists in the PM database.
Pre-checks Ensure that the task is completed as user root on the Single Platform Processor. Task Steps If the migration does not complete by 4:02am the default time for the omc_db_maint cron to execute OR if the upgrade does not complete before the customer configured start time for the omc_db_maint cron to run, then execute the following script as user root:
Check the omc_db_maint logfile in /usr/omc/logs, to ensure that the script has completed successfully. 10.9 Check OMC audit log file for possible errors Task Description Check the Single Platform Processor OMC log file for a specific FM error. Pre-checks - Ensure that the tasks are completed as user root on the appropriate platform. Task Steps - Open the latest log file in /usr/omc/logs. - Check if the following error is present in the log:
2007-07-25 18:05:44 FM_AUDIT(1453) FM_get_line_status(): can't open /usr/omc/current/config/fm/disconnect, error is 2 2007-07-25 18:05:44 FM_AUDIT(1453) FM_get_line_status() failed.
If the error is present, run the following command as root:

devfsadm
Then perform an OMC stop/start as user omcadmin:

omc stop Stopping the OMC omc start Starting the OMC
10.10 Network Performance Problem

Refer to Appendix A.3 in cases where network performance is not as expected.
11.0 Single Platform Processor - Migration Rollback Procedure Tasks

If the OMC fails to start on the new server, or if for any other reason it is decided that a rollback to the original server is required, the procedure below needs to be followed. 11.1 Single Platform Processor Migration Rollback Task Description To return to the SOURCE (E3500) Single Platform Processor. Pre-checks Ensure that the task is completed as user root on the SOURCE (E3500) platform. Task Steps - Move the HSI cables back to the SOURCE (E3500) platform. - Unplug the Ethernet cable from the TARGET (SF4900) platform - Ensure that the original IP address is in the /etc/hosts file of the SOURCE (E3500) platform and plug an Ethernet cable into the SOURCE (E3500) platform. - Once the SOURCE (E3500) platform is back on the network it should be rebooted as follows:
/usr/sbin/shutdown -i6 -g0 y
.
Once the machine has booted up, the GUI servers/clients should also be rebooted To ensure that the logfiles from the migration are maintained, rename the migration directory as follows:
mv /var/install/upgrade /var/install/first_migration
11.2 Mandatory PM Database Tasks
ENSURE THAT ALL THESE MANDATORY TASKS ARE COMPLETED AFTER THE SYSTEM HAS COME UP
11.2.1 Update statistics within the PM database Task Description Update statistics within the PM database. Pre-checks Ensure that the tasks are completed as user omcadmin on the Single Platform Processor. Task Steps
11.2.2 Complete a PM Resync Task Description Complete a PM Resync through the OMC-R GUI. Pre-checks Ensure that the tasks are completed as user omcadmin on the Single Platform Processor Task Steps
11.2.3 PM_HOURLY_STATS variable Task Description To examine the setting of the PM_HOURLY_STATS variable. Pre-checks Ensure that the tasks are completed as user omcadmin on the Single Platform Processor Task Steps Check the latest parser file fpomcaudit* in /usr/omc/logs/. Check if the following message appears after the OMC has restarted: "Invalid Duration, which will result in a .bad_header file." If this message does not appear in the fpomcaudit* log then skip to Section 8.8.5 If this message appears then the customer must set the PM_HOURLY_STATS variable to either ON or OFF in the OMC.CNFG file. This change can take place without the requirement of an OMC stop/start by following this procedure:
Using the vi editor edit the OMC.CNFG file Uncomment the setting for PM_HOURLY_STATS and alter the environment variable so it looks like either one of the following: PM_HOURLY_STATS=ON OR
PM_HOURLY_STATS=OFF Save and exit the file. Now execute the following:
To make the change a permanent one, set the value of the variable in /usr/omc/config/global/env/pmProcConfig.csh: setenv PM_HOURLY_STATS ON 11.2.4 PM parsing of .bad_header Files Task Description To rename and parse any .bad_header files which exist in the BSS directories. Pre-checks Ensure that the task is completed as user root on the Single Platform Processor Task Steps
/var/install/first_migration/scripts/badheader_tidyup
In the event of a file not parsing correctly, the extension .bad_header will automatically be re-added to the file. Check the current /usr/omc/logs/fpomcaudit log for more details.
11.2.5 PM Database Maintenance Setup Task Description Ensure that a new fragment exists in the PM database. Pre-checks Ensure that the task is completed as user root on the Single Platform Processor. Task Steps If the upgrade does not complete by 4:02am the default time for the omc_db_maint cron to execute OR if the upgrade does not complete before the customer configured start time for the omc_db_maint cron to run, then execute the following script as user root:
12.0 GUI Server - Upgrade Procedure Tasks

The procedures detailed in this chapter apply only to the N210 and Sunblade 150 GUI Server platforms ONLY. Upgrades are not supported on flexible GUI Server platforms. Refer to [2] for details on how to clean install these platforms. 12.1 GUI Server Upgrade Procedure Work Flow
Figure 3:
GUI Server Upgrade Procedure
12.2 COP TOOLS/NHA pre-upgrade workarounds Task Description Various workarounds are required to ensure that the adjunct products function correctly after the upgrade. Pre-checks - This task only applies where the Customer is using COP Tools and/or NHA. Task Steps Refer to the appropriate sections of appendix F and G.
12.3 Reboot the GUI Server Task Description As part of the overall upgrade procedure, the Single Platform Processor has been rebooted. The GUI Server will need to be rebooted in order to eliminate any Stale NFS file handles which may exist. Pre-checks - Ensure that the task is completed as user root on the GUI Server. Task Steps
reboot
12.4 Upgrade and Reboot the GUI Server Task Description Upgrade the GUI Server to a Solaris 10, GSR9 1.9.x.0 platform. Users should not be using areas temporarily mounted for the upgrade, as this could cause upgrade failure. The upgrade asks a number of questions which require response. In GSR9 the upgrade will prompt and gather responses to all these questions at the beginning. The following questions will be asked: 1. "Cutover to latest release automatically (y/n): " This question refers to whether during the upgrade the cutover should proceed without need for further input. If a y response is given, the upgrade will automatically proceed with the cutover. If a n response is given, the upgrade script will pause during execution and wait for further user input before proceeding with the cutover. 2. "Reboot automatically (y/n): " This question refers to whether during the upgrade the system should automatically reboot without need for further input. If a y response is given, the upgrade will automatically proceed with the required system reboots. If a n response is given, the upgrade script will pause during execution and wait for further user input before proceeding with system reboots. It is important to plan in advance how these questions should be responded to. It is also important to understand the implications of a y or n response to each individual question. For example, a n response to questions 1 or 2 will mean that the user will be asked the question again later the in upgrade. The following details the steps taken by the upgrade script (this is not an exhaustive list but points out the highlights of the upgrade):
(R) Below indicates that a response is required during this step. 1. 2. 3. 4. 5. 6. 7. 8. 9. Gather responses to upgrade questions(R) Validate system hardware configuration. Re-verify hardware component operation and system mirroring. Detach mirrors. Install Solaris 10 Operating System. Install GSR9 1.9.x.0 OMC Software and associated third party products. Configure Informix. Cutover to GSR9 1.9.x.0 load. Reboot the system.
For more details, refer to Appendix D for typical script outputs. Pre-checks Ensure that the GSR9 OMC Software and Jumpstart DVD is in the appropriate media drive. Local Upgrade: media should be in GUI Server drive. Remote/Parallel Upgrade: media should be in Single Platform Processor drive.
GUI Server To enable the GUI server to access the DVD share from the Single Platform Processor, ssh must be setup correctly using the following commands: Edit the file /etc/ssh/sshd_config to allow: PermitRootLogin yes Re-start secure services using:
/etc/init.d/sshd stop /etc/init.d/sshd start
Single Platform Processor To make the DVD media available to one or more GUI Servers, complete the following for each GUI Server to share the media from the Single Platform Processor. This will allow one or more GUI Servers to be upgraded in parallel:
NOTE: Remote/parallel GUI server upgrades will have a longer duration than the standard local upgrades. Exact times will depend on LAN speed. Ensure that the task is completed as user root on the GUI Server.
Task Steps
/var/install/upgrade/scripts/upgrade
Please note the system will be rebooted as part of the upgrade script and the user will be prompted before the reboot takes place. After the upgrade script has completed the system will be rebooted. During the reboot Disksuite reconfiguration will be completed. In some cases the system reboot will appear almost complete ensure that the system is not logged into until the reboot described above has completed FULLY and the login prompt is available. To ensure that the CDE desktop environment is fully configured, run the following command:
If the media drive on the Single Platform Processor was shared to the GUI Server, then execute the following commands for each GUI server to unshare the media from the Single Platform Processor, once the system has completed its tasks:
12.5 Activate secure services on the GUI Server Task Description Secure services need to be enabled manually on the GUI Server. Pre-checks Ensure that the tasks are completed as user root on the GUI Server. Task Steps Ensure that the first GSR9 OMCR DVD OMC Software and Jumpstart is inserted in the DVD drive: Local Upgrade: media should be in GUI Server drive Remote/Parallel Upgrade: media should be in Single Platform Processor drive. GUI Server To enable the GUI server to access the DVD share from the Single Platform Processor, ssh must be setup correctly using the following commands: Edit the file /etc/ssh/sshd_config to allow: Permit RootLogin yes Re-start secure services using:
svcadm restart svc:/network/ssh:default
/cdrom/cdrom0/s0/suninstall/upgrade/scripts/share_dvd share <GUI Server> GUI Server Then enter the following commands:
/cdrom/cdrom0/s0/suninstall/bin/security/secure /var/install/security/os_harden high
Single Platform Processor If the media drive on the Single Platform Processor was shared to the GUI Server, then execute the following commands for each GUI server to unshared the media from the Single Platform Processor, once the system has completed its tasks: /cdrom/cdom0/s0/suninstall/upgrade/scripts/share_dvd unshare <GUI Server> 12.6 Examine Upgrade Logfiles Task Description To examine the contents of the upgrade logfiles to ensure that any errors captured in the log files are analyzed. Pre-checks Ensure that the task is completed as user root on the GUI Server. Task Steps Examine the contents of the following log files: - /var/install/logs/upgrade/upgrade.log - /var/install/logs/upgrade/cde_install.log - /var/install/logs/upgrade/link_current.log - /usr/omc/logs/cutover.log - /var/install/logs/disksuite_setup.log Any errors noted from the log files need to be investigated before proceeding with the remainder of the upgrade. Where necessary the appropriate support organization should be contacted.
12.7 Install additional software patches Task Description Additional software patches need to be manually installed from the second GSR9 OMCR DVD. Pre-checks Ensure that the tasks are completed as user root on the GUI Server.
Task Steps Insert the second GSR9 OMCR DVD Additional OMC Software into the DVD drive. Local Upgrade: media should be in the GUI Server drive Remote/Parallel Upgrade: media should be in the Single Platform Processor drive If the drive already contains a DVD, eject it using the following command:
eject cdrom
If the DVD is in the Single Platform Processor, share the DVD to the GUI server: On the Single Platform Processor: share /cdrom/cdrom0 On the GUI Server: mkdir /cdrom/cdrom0 mount omc_splat:/cdrom/omcr.<load> /cdrom/cdrom0 For example mount omc_splate:/cdrom/omcr.190028 /cdrom/cdrom0 for 1900.28 Enter the following command as one command to install the patches from the DVD:
/cdrom/cdrom0/suninstall/bin/install_patches \ --patch_dir /cdrom/cdrom0/suninstall/Patches \ --patch_order /cdrom/cdrom0/suninstall/Patches/patch_order
If the DVD was shared from the Single Platform Processor to the GUI server, enter the following commands: On the GUI Server: unmount /cdrom/cdrom0 rmdir /cdrom/cdrom0 On the Single Platform Processor: unshare /cdrom/cdrom0 Some error messages may be shown if the install_patches script attempts to install patches that are already installed on the system as shown below. These errors can be safely ignored.
# /cdrom/cdrom0/suninstall/bin/install_patches --patch_dir /cdrom/cdrom0/suninstall/Patches --patch_order /cdrom/cdrom0/suninstall/Patches/patch_order Patches to be installed: 3 Now installing patches...please wait... Patches Patches Patches Patches installed: installed: installed: installed: 0/3 1/3 2/3 3/3 (0%) (33%) (66%) (100%)
2005, Motorola General Business Use Patch install complete. 3 patches failed to install. Please check logfile for details. 119059-20 121118-10 122660-07 Logfile is /var/install/logs/patch_install.log

Patch install started on Wed Jul 25 17:20:18 BST 2007 Installing 119059-20 Validating patches... Loading patches installed on the system... Done! Loading patches requested to install. Done! The following requested patches are already installed on the system Requested to install patch 119059-20 is already installed on the system. No patches to check dependency. Installing 121118-10 Validating patches... Loading patches installed on the system... Done! Loading patches requested to install. Done! The following requested patches are already installed on the system Requested to install patch 121118-10 is already installed on the system. No patches to check dependency. Installing 122660-07 Validating patches... Loading patches installed on the system... Done! Loading patches requested to install. Done! The following requested patches are already installed on the system Requested to install patch 122660-07 is already installed on the system. No patches to check dependency. Patch install completed on Wed Jul 25 17:20:25 BST 2007 _________________________________________________________________________________________________ Doc ID: OSS-GSR8-CUSTSUP-RLS-003 Doc Version: 3.0 57
12.8 COP TOOLS/NHA post-upgrade workarounds Task Description Various workarounds are required to ensure that the adjunct products function correctly after the upgrade. Pre-checks - This task only applies where the Customer is using COP Tools and/or NHA. Task Steps Refer to the appropriate sections of appendix F and G. 12.9 Post-Upgrade Procedure for Netra 210 GUI Server The SunRay Server software needs to be re-installed on the Netra 210 when the GUI server upgrade has been completed. See the GSR9 OMCR Clean Install guide (refer to [2]) for details. 12.10 Complete Filesystem Backup Task Description To complete a full backup of the GUI Server file systems after the upgrade has completed. Pre-checks Ensure that the task is completed as user root on the GUI Server, unless the backup procedure specifies otherwise. Task Steps A full backup of all the file systems on the GUI Server can now be performed. Refer to [3] for details of the backup procedures. 12.11 Commit the System Task Description To commit the system. Refer to Appendix D for typical script outputs. Pre-checks Ensure that the task is completed as user root on the GUI Server. When the GSM OMC-R system has been deemed stable and the customer is satisfied with the functionality, it is advisable to complete the disk/data mirroring.
It should be noted that there is no automatic rollback to GSM OMC-R Release GSR9 1.8.x.0 after this procedure has been completed. The only possible method is by means of a Complete File System Recovery. Ensure that the GSR9 OMC Software and Jumpstart DVD is in the appropriate media drive. Local Upgrade: media should be in GUI Server drive. Remote/Parallel Upgrade: media should be in Single Platform Processor drive. GUI Server To enable the GUI server to access the DVD share from the Single Platform Processor, ssh must be setup correctly using the following commands: Edit the file /etc/ssh/sshd_config to allow: PermitRootLogin yes Re-start secure services using:
svcadm restart svc:/network/ssh:default
Steps GUI Server

/var/install/upgrade/scripts/commit
If the media drive on the Single Platform Processor was shared to the GUI Server, then execute the following commands to unshare the media from the Single Platform Processor, once the system has completed its tasks.
12.12 Examine Commit Logfiles Task Description To examine the contents of the commit log files to ensure that any errors captured in the log files are analyzed. Pre-checks Ensure that the task is completed as user root on the GUI Server.
Task Steps Examine the contents of the following log file: - /var/install/logs/upgrade/commit.log If any errors exist in this log file, contact the relevant support organisation.
13.0 GUI Server - Rollback Procedure Tasks

This rollback procedure is in effect undoing the operations performed during the upgrade. The rollback procedure supports the following scenarios: SCENARIO One: The upgrade script completed successfully and the system has rebooted. SCENARIO Two: The upgrade script has not completed successfully and the system has not rebooted. SCENARIO Three: The upgrade script has completed successfully and the system has rebooted. Its required that the GUI Server revert back to the GSR8 1.8.x.0 software, but a decision to fully rollback the system hasnt been made. This will allow the system to switch back to GSR8 1.8.x.0, without the need to upgrade again should this be required. Based on the rollback scenario, which has been encountered, the appropriate section below should be completed. 13.1 Rollback Procedure Scenario One Task Description To roll the system back to its original configuration. The following details the steps taken by the rollback script (this is not an exhaustive list but points out the highlights of the rollback): (R) Below indicates that a response is required during this step. 1. Cleanup any setup remaining from the previous upgrade 2. Re-initialize the GSR8 1.8.x.0 mirrors 3. Attach mirrors Refer to Appendix D for typical script output. Pre-checks Ensure that the task is completed as user root on the GUI Server. Ensure that the upgrade script completed successfully and the system has rebooted. Steps
This will reboot the system onto the mirrordisk. Once this reboot is complete continue with the following:
13.2 Rollback Procedure Scenario Two Task Description To roll the system back to its original configuration. The following details the steps taken by the rollback script (this is not an exhaustive list but points out the highlights of the rollback): (R) Below indicates that a response is required during this step. 1. Cleanup any setup remaining from the previous upgrade 2. Re-initialize the GSR8 1.8.x.0 mirrors 3. Attach mirrors Refer to Appendix D for typical script output. Pre-checks Ensure that the task is completed as user root on the GUI Server. Ensure that the upgrade script has not completed successfully and the system has not rebooted. Steps
13.3 Rollback Procedure Scenario Three Task Description If its required to switch a GUI Server back to its original GSR8 1.8.x.0 configuration, but not fully rollback at this stage then this step should be completed.. Should a full rollback be required at a later stage follow the steps described for Scenario 2, in section 13.2 above. The Steps section below also contains an instruction to switch back again to GSR9, should a full rollback not be required. Pre-checks Ensure that the task is completed as user root on the GUI Server. Ensure that the upgrade script completed successfully and the system has rebooted. Steps To switch back to the GSR8 configuration:
To switch forward to the GSR9 configuration:

/var/install/swap_to_new_install
13.4 Examine Rollback Logfiles Task Description To examine the contents of the rollback log files to ensure that any errors captured in the log files are analyzed on the Single Platform Processor. Pre-checks Ensure that the task is completed as user root on the Single Platform Processor.
Task Steps Examine the contents of the following log files: - /var/install/logs/upgrade/rollback/rollback.log If any errors exist in these log files, contact the relevant support organisation for clarification. 13.5 Retain Rollback Directory Task Description To maintain the rollback directory. Pre-checks Ensure that the task is completed as user root on the GUI Server.
Task Steps
cd /var/install mv upgrade old_upgrade
NOTE: As the upgrade directory has now been renamed, when attempting the upgrade again, the procedure will have to be re-started from Chapter 6 - Preparation.
A Trouble Shooting
A.1 Verify Disk Check If it is necessary to break from the system_verify script during the verify stage due to a SUNVTS disk test hanging, take note of the disk on which the VTS test has hung and complete the following to ensure that no hardware problems exist on that disk: As user root on the Single Platform Processor run: format Select the disk the VTS test has failed on. Select the analyse option from the menu, Select the read option from the menu. Allow the read to complete. If no errors are reported on the disk, restart the system_verify and complete the phase and answer Y when asked if you wish to skip the SUNVTS test on this disk. A.2 MIB Database Migration Should the MIB database migration procedure fail the system will be left in the following state: The OMC is not restarted The CDE desktop login will not be launched on the system console. This is designed to ensure that the failure of the MIB migration is addressed. Should this be the case it can be useful to retry the migration as follows: As user root on the Single Platform Processor:
/var/install/upgrade/scripts/S981mib_migration start
If this should not result in a successful database migration contact the relevant support organisation for assistance in resolving the MIB migration failure. Once the migration has been successfully completed the following should be implemented to bring the system into the correct state: As user omcadmin on the Single Platform Processor:
mib_env /usr/omc/sbin/create_sy
As user root on the Single Platform Processor to restart the login prompt and the OMC:
svcadm enable console-login svcadm enable omc
. A.3 How to correct a potential system performance problem
This troubleshooter will only be needed if the LAN is 100 Mbps full-duplex
If the LAN connecting the TARGET platform is a 100 Mbps full-duplex network (check this with the Network System Administrator), then the system may experience performance issues. It is recommended to run the commands in this section on the console of a system as changing the network link settings can cause existing network connections to close. Ensure that the task is completed as user root on the TARGET platform
/var/install/bin/check_link
If the output of this command shows nothing, then there is no performance problem and the rest of this section may be ignored. If the command detects a 100 Mbps half duplex link, then you have the option of forcing the link to 100 Mbps full duplex.
The network interface eri0 has negotiated a 100Mbps half-duplex link. If connected to a switch, this is often incorrect and may result in very slow network speeds. Do you wish to force a 100Mbps full-duplex link? (y/n)
If you answer y to this question, the link speed will be forced to 100 Mbps full duplex and will be configured to set this speed automatically on every boot.
B Upgrade Logging and Tracking Convention

This appendix describes the logging and tracking undertaken by the upgrade. During certain stages of an upgrade, the logs are located under /a/<dir>. B.1 Logging Each of the following scripts, involved in the upgrade, creates a log file in the /var/install/logs/upgrade/ directory: verify upgrade migrate commit rollback The following naming convention is used for all these log files: <PHASE>.log where <PHASE> is one of verify, upgrade, migrate, commit, rollback. upgrade.log The following types of error entries are also logged to the log files. Each type is of a different severity. Where ANY type of error is encountered it should be investigated and where appropriate resolved before continuing with ANY upgrade/migration related activities. Where necessary the appropriate support organisation should be called. Fatal Error where a phase of the upgrade/migration encounters a problem such that it is impossible to continue with the procedure it will exit and the operator will be informed that a FATAL ERROR has occurred. where a phase of the upgrade encounters a problem that is not deemed severe enough to cause a fatal error, but does indicate a problem with the system. where a phase of the upgrade encounters a situation what should be investigated to verify system integrity.
Error
Warning
B.2 Tracking As described above the upgrade consists of the following major phases: Verify Upgrade/Migration Rollback Commit (not applicable in migration scenario) Furthermore, these major phases of the upgrade are divided into sub-phases and the upgrade procedure is tracked at this sub-phase level.
Within the /var/install/logs/upgrade/tracker directory, there will be a subdirectory created for each of the sub-phases. Within these directories are empty files, which the sub-phase creates, once the particular stage in the sub-phase has completed. The filenames correspond to stages within the subphase. These may be useful in the event of problems with any of the sub-phases. B.2.1 SINGLE PLATFORM PROCESSOR The sub-phases for the VERIFY phase and the associated tracker files are as follows: 1. GEN_SC_CONF 2. SETUP 3. HARDWARE_VERIFY 4. PRE_VERIFY 5. UPDATE_MDTAB 6. DISKSUITE_VERIFY 7. POST_VERIFY 8. SYSTEM_VERIFY The sub-phases for the UPGRADE phase and the associated tracker files are as follows: 1. HARDWARE_VERIFY 2. SYSTEM_PROFILE 3. PRE_VERIFY 4. CHECK_DVD_CONF 5. META_VERIFY 6. DISKSUITE_VERIFY 7. POST_VERIFY 8. SYSTEM_VERIFY 9. CLEANUP 10. USER_INPUT 11. GEN_SC_CONF 12. SETUP 13. PRE_DISKSUITE_DETACH 14. DISKSUITE_DETACH 15. DISKSUITE_CLEAR 16. POST_DISKSUITE_CLEAR 17. PRE_JUMPSTART 18. JUMPSTART 19. POST_JUMPSTART 20. CONFIGURE_DISKSUITE 21. THIRD_PARTY_INSTALL 22. PRE_DATABASE_INSTANCE 23. DATABASE_INSTANCE 24. POST_DATABASE_INSTANCE25. MIGRATE_FILES 26. GENERATE_REBOOT_SCRIPTS 27. POST_GENERATE 28. CONFIGURE_NEW_LVM 29. POST_CLEANUP
_________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 67
The sub-phases for the ROLLBACK phase and the associated tracker files are as follows: 1. CLEANUP 2. POST_ROLLBACK_CLEANUP 3. ROLLBACK 4. POST_ROLLBACK The sub-phases for the COMMIT phase and the associated tracker files are as follows: 1. HARDWARE_VERIFY 2. SETUP 3. COMMIT 4. POST_COMMIT The sub-phases for the MIGRATION phase and the associated tracker files are as follows: 1. PRE_HARDWARE_VERIFY 2. MIGRATE_SETUP 3. MIGRATE_FILES 4. MIGRATE_DATABASE 5. CLEANUP 6. POST_CLEANUP B.2.2 GUI SERVER The sub-phases for the VERIFY phase and the associated tracker files are as follows: 1. PRE_GEN_SC_CONF 2. GEN_SC_CONF 3. HARDWARE_VERIFY 4. PREINSTALL_PLATFORM 5. DISKSUITE_VERIFY 6. POST_VERIFY 7. CLEANUP The sub-phases for the UPGRADE phase and the associated tracker files are as follows: 1. GEN_SC_CONF 2. USER_INPUT 3. PRE_HARDWARE_VERIFY 4. HARDWARE_VERIFY 5. DISKSUITE_DETACH 6. POST_DISKSUITE_DETACH 7. DISKSUITE_CLEAR 8. PREINSTALL_PLATFORM 9. PRE_JUMPSTART 10. JUMPSTART 11. POST_JUMPSTART
12. PRE_THIRD_PARTY_INSTALL 13. THIRD_PARTY_INSTALL 14. MIGRATE_FILES 15. POST_MIGRATE_FILES 16. GENERATE_REBOOT_SCRIPTS 17. CONFIGURE_NEW_LVM 18. CLEANUP 19. POST_CLEANUP 20. SWAP_TO_NEW The sub-phases for the ROLLBACK phase and the associated tracker files are as follows: 1. CLEANUP 2. ROLLBACK 3. POST_ROLLBACK The sub-phases for the COMMIT phase and the associated tracker files are as follows: 1. SETUP 2. PRE_HARDWARE_VERIFY 3. HARDWARE_VERIFY 4.PREINSTALL_PLATFORM 5. PRE_DISKSUITE_SETUP 6. DISKSUITE_SETUP 7. POST_DISKSUITE_SETUP
C Single Platform Processor - Typical Script Output

The output below is from a SF4900. Is should be viewed as an example. Other platforms will have slightly different output. C.1 Verify Script
# /var/install/bin/verify_platform 320 blocks Motorola Common Platform Verify_platform script has started Motorola Common Platform Verify_platform script This script will verify_platform your platform
Do you wish to proceed with the operation? (enter 'Y' or 'N'): [y,n,?,q] Y Reading verify_platform control file /var/install/bin/config/verify_platform_control.dat ################################################# ## Output from /var/install/bin/scripts/system_profile ## Run at 211106-17:48:17 ################################################# Release 1.9.0.0.21 Server_Type Sun Fire 4900 Processors 4 Capacity(tch) 60k HSI_cards 0 Memory_Size 8192 Megabytes Number of Disks 14 Total_Formatted_Space 207.7 GB Free_Formatted_Space 197.7 GB ****************************************************************************** * Preparing to detect the current software release * ****************************************************************************** Upgrading from a valid software release 1800 ****************************************************************************** * Checking General Hardware * ****************************************************************************** System Status Mode and LEDS ------------------------------Board Receptacle Occupant FRU Name Type Status Status Condition Info --------- ----------- ----------- ------------ --------- ---------------------------------------/N0/SB2 CPU_V2 connected configured ok powered-on, assigned /N0/SB4 CPU_V2 connected configured ok powered-on, assigned /N0/IB6 PCI_I/O_Boa connected configured ok powered-on, assigned /N0/IB8 PCI_I/O_Boa connected configured ok powered-on, assigned ****************************************************************************** * Checking network interface * ******************************************************************************
ERROR: The network interface has not been successfully tested (This can be safely ignored see SR 810149).
2007, Motorola General Business Use ****************************************************************************** * Checking Installed Processors * ****************************************************************************** Starting a SunVTS test on the installed Processor(s) 4 Processor(s) have been successfully tested ****************************************************************************** * Checking memory * ****************************************************************************** Memory passed SunVTS test
****************************************************************************** * Checking capacity of / filesystem * ****************************************************************************** INFO: 2% in / is sufficient space to proceed with upgrade ****************************************************************************** * Checking capacity of /usr/omc filesystem * ****************************************************************************** INFO: 10% in /usr/omc is sufficient space to proceed with upgrade ****************************************************************************** * Checking DVD drive * ****************************************************************************** Starting vtsk process. Started vtsk process. <DVD ROM TEST here ...> Stopped vtsk process. ****************************************************************************** * Preparing to detect the current software release * ****************************************************************************** Upgrading from a valid software release 1800 Metadevice layout OK ****************************************************************************** * Script for DISKSUITE_VERIFY started * ****************************************************************************** Checking metadatabases for c1... Done Checking metadatabases... Done
****************************************************************************** * Preparing to attach mirrors where required * ****************************************************************************** Attaching submirrors... Done ****************************************************************************** * Checking status of system mirrors * ****************************************************************************** _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 71
2007, Motorola General Business Use Checking metadevices... Done Updated eeprom boot-device variable to "bootdisk mirrordisk" ****************************************************************************** * Preparing to detect the current software release * ****************************************************************************** Upgrading from a valid software release 1800 No BSS needs to be upgraded. No RXCDR needs to be upgraded. Beginning disk checks - this phase of the verify will take some time <check_disk_conf check here> System Verification complete Starting postupgrade cleanup ... Common Platform Upgrade cleanup complete Motorola Common Platform Verify_platform script has completed
C.2 Upgrade Script

# /var/install/upgrade/scripts/upgrade Motorola Common Platform Upgrade script has started Motorola Common Platform Upgrade script This script will upgrade your platform
Do you wish to proceed with the operation? (enter 'Y' or 'N'): [y,n,?,q] Y Reading upgrade control file /var/install/upgrade/config/upgrade_control.dat Enter y or n for each of the following: Keep PM Data and delete old unl files (y/n): y Cutover to latest release automatically (y/n): y Stop the OMC (y/n): y Reboot automatically (y/n): y Interrupts have been disabled for phase HARDWARE_VERIFY ****************************************************************************** * Preparing to detect the current software release * ****************************************************************************** /var/install/upgrade/scripts/pre_verify.sh[31]: test: argument expected Upgrading from a valid software release 1800 ****************************************************************************** * Script for DISKSUITE_VERIFY started * ******************************************************************************
****************************************************************************** * Updating savecore device * ****************************************************************************** Dump content: kernel pages Dump device: /dev/dsk/c3t8d0s1 (dedicated) Savecore directory: /var/crash/somc211 Savecore enabled: yes ****************************************************************************** _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 72
2007, Motorola General Business Use * Preparing to stop INFORMIX processes * ****************************************************************************** Sun Microsystems Inc. SunOS 5.10 You have new mail. Generic January 2005
OMC Database disconnect utility invoked. Utility initialisation completed successfully Request sent successfully for parser application. Request sent successfully for em application. Request sent successfully for pmproxy application. Request sent successfully for csm application. Request sent successfully for loader application. Positive confirmation received from parser for a disconnect. Positive confirmation received from em for a disconnect. Positive confirmation received from pmproxy for a disconnect. Positive confirmation received from csm for a disconnect. Positive confirmation received from loader for a disconnect. Time taken for disconnect is 1.994 seconds OMC database utility completed successfully. Shutting down the PM Informix Instance Sun Microsystems Inc. SunOS 5.10 Generic January 2005 ****************************************************************************** * Preparing to detach mirrors * ****************************************************************************** Gathering LVM configuration information from System... Done Detaching mirrors... Done ****************************************************************************** * Clearing c1 soft partitions * ****************************************************************************** Clearing metadevices... Done ****************************************************************************** * Preparing to start INFORMIX processes * ****************************************************************************** Starting the PM Informix Instance Sun Microsystems Inc. SunOS 5.10 Generic January 2005 Informix instance successfully brought online Validating Hardware ... GSM OMCR Preparing for Upgrade ... Setting default PROM values... Done Starting Solaris Install Interrupts have been disabled for phase JUMPSTART Installing Live Upgrade Packages... Processing package instance <SUNWlur> from </cdrom/cdrom0/s0/suninstall/Packages/liveupgrade.pkgs> Live Upgrade (root) (sparc) 11.10,REV=2005.01.10.00.03 This appears to be an attempt to install the same architecture and version of a package which is already installed. This installation will attempt to overwrite this package. Using </> as the package base directory. _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 73
2007, Motorola General Business Use ## Processing package information. ## Processing system information. 33 package pathnames are already properly installed. ## Verifying package dependencies. ## Verifying disk space requirements. Installing Live Upgrade (root) as <SUNWlur.2> ## Executing preinstall script. ## Installing part 1 of 1. [ verifying class <AddNoUpdate> ] [ verifying class <EtcDefLu> ] ## Executing postinstall script. Installation of <SUNWlur.2> was successful. Processing package instance <SUNWluu> from </cdrom/cdrom0/s0/suninstall/Packages/liveupgrade.pkgs> Live Upgrade (usr) (sparc) 11.10,REV=2005.01.10.00.03 This appears to be an attempt to install the same architecture and version of a package which is already installed. This installation will attempt to overwrite this package. Using </> as the package base directory. ## Processing package information. ## Processing system information. 159 package pathnames are already properly installed. ## Verifying package dependencies. ## Verifying disk space requirements. Installing Live Upgrade (usr) as <SUNWluu.2> ## Installing part 1 of 1. ## Executing postinstall script. Installation of <SUNWluu.2> was successful. Updating /etc/lu/lu_transfer_list... Updating /etc/lu/synclist... Creating BOOT environments ... Discovering physical storage devices Discovering logical storage devices Cross referencing storage devices with boot environment configurations Determining types of file systems supported Validating file system requests Preparing logical storage devices Preparing physical storage devices Configuring physical storage devices Configuring logical storage devices Analyzing system configuration. Updating boot environment description database on all BEs. Searching /dev for possible boot environment filesystem devices Updating system configuration files. Creating <ufs> file system for </> on </dev/dsk/c1t8d0s0>. Creating <ufs> file system for </opt> on </dev/dsk/c1t8d0s4>. Creating <ufs> file system for </usr> on </dev/dsk/c1t8d0s5>. Creating <ufs> file system for </var> on </dev/dsk/c1t8d0s3>. Creation of boot environment <sol10> successful. Starting Solaris installation INFO: Live upgrade execution complete /a _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 74
2007, Motorola General Business Use Determining hostname... Done Creating default user profiles... Done Generating SSH key for informix ld.so.1: ssh-keygen: fatal: libcrypto.so.0.9.7: open failed: No such file or directory /cdrom/suninstall/postinstall[301]: 11979 Killed Changing home directory permissions for omcadmin Generating SSH key for omcadmin ld.so.1: ssh-keygen: fatal: libcrypto.so.0.9.7: open failed: No such file or directory /cdrom/suninstall/postinstall[301]: 12012 Killed Changing home directory permissions for omcread Generating SSH key for omcread ld.so.1: ssh-keygen: fatal: libcrypto.so.0.9.7: open failed: No such file or directory /cdrom/suninstall/postinstall[301]: 12045 Killed Generating SSH key for root ld.so.1: ssh-keygen: fatal: libcrypto.so.0.9.7: open failed: No such file or directory /cdrom/suninstall/postinstall[311]: 12049 Killed Creating /var/adm/loginlog... Done Creating default admin file for pkgadd... Done Updating sys crontab... Done Configuring Locale... Done Adjusting root's ULIMIT... Done Configuring /etc/auto_master... Done Configuring default network interface (ce0)... Done Turning off IP Forwarding... Done Configuring /etc/inet/netmasks... Done Updating /etc/inet/hosts... Done Setting /etc/defaultdomain to localdomain... Done Setting /etc/defaultrouter to 175.3.41.84... Done Setting up the timeserver... Done Locking system accounts... Done /cdrom/suninstall/postinstall[883]: /sbin/get_root: not found /cdrom/suninstall/postinstall[884]: /sbin/get_root: not found Saving mountroot information INFO: Logging unload to /usr/omc/logs/pm_db_unload.log WARNING: Keeping your PM data after the unload could fail unless the following WARNING: are checked: WARNING: (1) ULIMIT has been unset to enable very large files be created. WARNING: (2) Sufficient disk space is available on your filesystem. Do you want to keep your PM data after upgrade (yes/no) ? ye valid responses are yes/no ? yes INFO: User elected to keep their entire PM database. INFO: Database unload started. INFO: Attempting to unload current data... INFO: Checking subscriptions unl files... INFO: Checking subscriptions tables... Preparing new High Performance Loader database... Done Dropping old High Performance Loader database... Done Importing new High Performance Loader database... Done INFO: Please wait: determining amount of PM data (kbytes) in existing database... INFO: The current data size is 842Kb and you have 16326409Kb available INFO: in /a/usr/omc/ne_data. This is sufficient space to continue with the unload. INFO: Unloading table subscriptions. INFO: Table subscriptions unloaded successfully. INFO: Unloading table psp_statistics. INFO: Table psp_statistics unloaded successfully. INFO: Unloading table carrier_statistic2. INFO: Table carrier_statistic2 unloaded successfully. INFO: Unloading table carrier_statistic3. INFO: Table carrier_statistic3 unloaded successfully. INFO: Unloading table gproc_statistics. INFO: Table gproc_statistics unloaded successfully. INFO: Unloading table carrier_statistics. _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 75
2007, Motorola General Business Use INFO: Table carrier_statistics unloaded successfully. INFO: Unloading table pm_load_log. INFO: Table pm_load_log unloaded successfully. INFO: Unloading table nbr_statistics. INFO: Table nbr_statistics unloaded successfully. INFO: Unloading table dynetgp_statistics. INFO: Table dynetgp_statistics unloaded successfully. INFO: Unloading table axcdr_statistics. INFO: Table axcdr_statistics unloaded successfully. INFO: Unloading table vgcs_statistics. INFO: Table vgcs_statistics unloaded successfully. INFO: Unloading table entity. INFO: Table entity unloaded successfully. INFO: Unloading table stored_selections. INFO: Table stored_selections unloaded successfully. INFO: Unloading table bss_datetimes. INFO: Table bss_datetimes unloaded successfully. INFO: Unloading table oml_statistics. INFO: Table oml_statistics unloaded successfully. INFO: Unloading table cbl_statistics. INFO: Table cbl_statistics unloaded successfully. INFO: Unloading table pm_info. INFO: Table pm_info unloaded successfully. INFO: Unloading table pcu_statistics. INFO: Table pcu_statistics unloaded successfully. INFO: Unloading table bss_statistics. INFO: Table bss_statistics unloaded successfully. INFO: Unloading table mtl_statistics. INFO: Table mtl_statistics unloaded successfully. INFO: Unloading table gsl_statistics. INFO: Table gsl_statistics unloaded successfully. INFO: Unloading table custom_statistics. INFO: Table custom_statistics unloaded successfully. INFO: Unloading table cell_statistics. - Tue Nov 21 18:35:55 2006 18:35:55 Dynamically allocated new virtual shared memory segment (size 4096KB) INFO: Table cell_statistics unloaded successfully. INFO: Unloading table lmtl_statistics. _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 76
2007, Motorola General Business Use INFO: Table lmtl_statistics unloaded successfully. INFO: Unloading table carrier_statistic4. INFO: Table carrier_statistic4 unloaded successfully. INFO: Unloading table nbr_status. INFO: Table nbr_status unloaded successfully. INFO: Unloading table reset_site_table. INFO: Table reset_site_table unloaded successfully. INFO: Unloading table subscription_list. INFO: Table subscription_list unloaded successfully. INFO: Unloading table xbl_statistics. INFO: Table xbl_statistics unloaded successfully. INFO: Unloading table nbr_entity. INFO: Table nbr_entity unloaded successfully. INFO: Unloading table device_selection. INFO: Table device_selection unloaded successfully. INFO: Unloading table stat_selection. INFO: Table stat_selection unloaded successfully. INFO: Unloading table gbl_statistics. INFO: Table gbl_statistics unloaded successfully. INFO: Unloading table rsl_statistics. INFO: Table rsl_statistics unloaded successfully. INFO: Unloading table dproc_statistics. INFO: Table dproc_statistics unloaded successfully. INFO: Table unload completed. INFO: Database unload completed. INFO: IP address formatted. INFO: Please wait installing the ONCONFIG and SQLHOSTS for the OMC INFO: Relevant multiple connect entry written to /usr/informix/etc/onconfig_OMC INFO: Relevant multiple connect entry written to /usr/informix/etc/SF4800_sqlhosts_OMC INFO: Please wait installing the ONCONFIG and INFO: SQLHOSTS for the MIB.... INFO: Relevant multiple connect entry written to /usr/informix/etc/onconfig_MIB INFO: Relevant multiple connect entry written to /usr/informix/etc/SF4800_sqlhosts_MIB INFO: Please wait installing the TCP ports in INFO: /etc/services for both OMC and MIB.... INFO: Completed successfully. Modifying /a/usr/informix/etc/SF4800_sqlhosts_OMC Modifying /a/usr/informix/etc/SF4800_sqlhosts_OMC Modifying /a/usr/informix/etc/SF4800_sqlhosts_OMC Modifying /a/usr/informix/etc/SF4800_sqlhosts_OMC Modifying /a/usr/informix/etc/onconfig_OMC Modifying /a/usr/informix/etc/onconfig_OMC Modifying /a/usr/informix/etc/plconfig.std Modifying /a/usr/informix/etc/plconfig.std Modifying /a/usr/omc/config/global/pmAdminConfig.csh Modifying /a/usr/omc/config/global/pmAdminConfig.sh Modifying /a/usr/omc/config/global/pmInfxUserConfig.csh _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 77
2007, Motorola General Business Use Modifying /a/usr/omc/config/global/pmInfxUserConfig.sh Setup for additional database instance complete Invoking Initialize_Informix to create the PM database instance Initialize_Informix has completed Reconfiguring CDE settings... Done cde_install has completed Starting the third instance of Informix 1139824 blocks Cutting over to release 1.9.0.0.21... Relinking /usr/omc/current... Done Configuring file permissions... Done Creating startup files... Done Configuring SMF permissions... Done INFO: Checking for an existing database. INFO: No PM database currently present, exiting.... Updating PM environment files... Done Configuring Country/Network code... Done Copying release specific scripts... Done Cleaning up sec files... Done INFO: Checking PM DB configuration... INFO: Chunk /dev/omc_db_root already exists - continuing... INFO: Chunk /dev/omc_db_logs already exists - continuing... INFO: Chunk /dev/omc_db_logs already exists - continuing... INFO: Chunk /dev/omc_db1 already exists - continuing... INFO: Chunk /dev/omc_db2 already exists - continuing... INFO: Chunk /dev/omc_db3 already exists - continuing... INFO: Chunk /dev/omc_db4 already exists - continuing... INFO: Chunk /dev/omc_db5 already exists - continuing... INFO: Chunk /dev/omc_db6 already exists - continuing... INFO: Chunk /dev/omc_db7 already exists - continuing... INFO: Chunk /dev/omc_db8 already exists - continuing... INFO: Chunk /dev/omc_db9 already exists - continuing... INFO: Chunk /dev/omc_db10 already exists - continuing... INFO: Chunk /dev/omc_db11 already exists - continuing... INFO: Chunk /dev/omc_db12 already exists - continuing... INFO: Chunk /dev/omc_db_temp already exists - continuing... INFO: Done INFO: Checking for PM database changes... INFO: Relevant multiple connect entry written to /usr/informix/etc/onconfig_OMC INFO: Relevant multiple connect entry written to /usr/informix/etc/SF4800_sqlhosts_OMC INFO: Please wait installing the ONCONFIG and INFO: SQLHOSTS for the MIB.... INFO: Relevant multiple connect entry written to /usr/informix/etc/onconfig_MIB INFO: Relevant multiple connect entry written to /usr/informix/etc/SF4800_sqlhosts_MIB INFO: Please wait installing the TCP ports in INFO: /etc/services for both OMC and MIB.... INFO: Completed successfully. Modifying /a/usr/informix/etc/SF4800_sqlhosts_OMC Modifying /a/usr/informix/etc/SF4800_sqlhosts_OMC Modifying /a/usr/informix/etc/SF4800_sqlhosts_OMC Modifying /a/usr/informix/etc/SF4800_sqlhosts_OMC Modifying /a/usr/informix/etc/onconfig_OMC Modifying /a/usr/informix/etc/onconfig_OMC Modifying /a/usr/informix/etc/plconfig.std Modifying /a/usr/informix/etc/plconfig.std Modifying /a/usr/omc/config/global/pmAdminConfig.csh Modifying /a/usr/omc/config/global/pmAdminConfig.sh Modifying /a/usr/omc/config/global/pmInfxUserConfig.csh Modifying /a/usr/omc/config/global/pmInfxUserConfig.sh Setup for additional database instance complete Invoking Initialize_Informix to create the PM database instance Initialize_Informix has completed Reconfiguring CDE settings... Done cde_install has completed Starting the third instance of Informix 1139824 blocks Cutting over to release 1.9.0.0.21.. _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 78
2007, Motorola General Business Use Relinking /usr/omc/current... Done Configuring file permissions... Done Creating startup files... Done Configuring SMF permissions... Done INFO: Checking for an existing database. INFO: No PM database currently present, exiting.... Updating PM environment files... Done Configuring Country/Network code... Done Copying release specific scripts... Done Cleaning up sec files... Done INFO: Checking PM DB configuration... INFO: Chunk /dev/omc_db_root already exists - continuing... INFO: Chunk /dev/omc_db_logs already exists - continuing... INFO: Chunk /dev/omc_db_logs already exists - continuing... INFO: Chunk /dev/omc_db1 already exists - continuing... INFO: Chunk /dev/omc_db2 already exists - continuing... INFO: Chunk /dev/omc_db3 already exists - continuing... INFO: Chunk /dev/omc_db4 already exists - continuing... INFO: Chunk /dev/omc_db5 already exists - continuing... INFO: Chunk /dev/omc_db6 already exists - continuing... INFO: Chunk /dev/omc_db7 already exists - continuing... INFO: Chunk /dev/omc_db8 already exists - continuing... INFO: Chunk /dev/omc_db9 already exists - continuing... INFO: Chunk /dev/omc_db10 already exists - continuing... INFO: Chunk /dev/omc_db11 already exists - continuing... INFO: Chunk /dev/omc_db12 already exists - continuing... INFO: Chunk /dev/omc_db_temp already exists - continuing... INFO: Done INFO: Checking for PM database changes... INFO: Done INFO: Shutting down Informix Instance ./S51databaseUpgrade: svcadm: not found INFO: Updating the onconfig file INFO: Starting Informix instance INFO: Informix instance started successfully INFO: Database load commenced. INFO: Checking for an existing database. INFO: Attempting to create the OMC database... | Database selected.
1 row(s) retrieved.
Database closed. INFO: Sun Microsystems Inc. SunOS 5.10 Generic January 2005 INFO: You have new mail. INFO: INFO: CREATING DATABASE: omc_db... INFO: INFO: CREATING DATABASE SCHEMA... INFO: INFO: Making database schema using: /usr/omc/current/config/db_config.dat
INFO: Database selected.
INFO: Table created. INFO: Permission revoked. _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 79
2007, Motorola General Business Use INFO: Index created.
INFO: Index created.
INFO: Table created.
INFO: Permission revoked.
INFO: Index created. . . . INFO: Done INFO: Shutting down Informix Instance ./S51databaseUpgrade: svcadm: not found INFO: Updating the onconfig file INFO: Starting Informix instance INFO: Informix instance started successfully INFO: Database load commenced. INFO: Checking for an existing database. INFO: Attempting to create the OMC database... | Database selected.
1 row(s) retrieved.
Database closed. INFO: Sun Microsystems Inc. SunOS 5.10 Generic January 2005 INFO: You have new mail. INFO: INFO: CREATING DATABASE: omc_db... INFO: INFO: CREATING DATABASE SCHEMA... INFO: INFO: Making database schema using: /usr/omc/current/config/db_config.dat _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 80
2007, Motorola General Business Use INFO: Database selected.
INFO: Index created. . . . INFO: Permission granted.
INFO: Permission granted.
INFO: Permission granted. INFO: Permission granted.
INFO: Permission granted. _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 81
2007, Motorola General Business Use INFO: Permission granted.
INFO: Permission granted. . . . INFO: Permission granted.
INFO: Permission granted. INFO: Permission granted.
INFO: View created.
2007, Motorola General Business Use INFO: View created.
INFO: View created.
INFO: View created.
INFO: View created.
INFO: View created.
INFO: View created.
INFO: View created.
INFO: View created.
INFO: View created.
INFO: View created. . . . INFO: Permission granted.
INFO: Database closed. INFO: INFO: GRANTING DATABASE PRIVILEGES... INFO: Database selected.
INFO: Database closed. _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 83
2007, Motorola General Business Use INFO: INFO: INITIALIZING DATABASE... INFO: Database selected.
INFO: 1 row(s) loaded.
INFO: 2966 row(s) loaded. . . . INFO: 4 row(s) loaded.
INFO: Database closed. INFO: INFO: LOADING PM LOADER SPECIFIC OBJECTS... INFO: OMC database created successfully. INFO: Shutting down Informix... /usr/omc/1.9.0.0.21/install_splat/pm_db_load: svcadm: not found / INFO: Informix is off-line. INFO: Updating the onconfig file INFO: Starting Up Informix... /usr/omc/1.9.0.0.21/install_splat/pm_db_load: svcadm: not found | INFO: Informix is on-line. Preparing new High Performance Loader database... Done Dropping old High Performance Loader database... Done Importing new High Performance Loader database... Done INFO: Granting necessary permissions to root user. INFO: Sun Microsystems Inc. SunOS 5.10 Generic January 2005 _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 84
2007, Motorola General Business Use INFO: You have new mail. INFO: Loading Table subscriptions INFO: Creating columns lists for subscriptions. INFO: Searching for columns to delete from subscriptions. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table psp_statistics INFO: Creating columns lists for psp_statistics. INFO: Searching for columns to delete from psp_statistics. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table carrier_statistic2 INFO: Creating columns lists for carrier_statistic2. INFO: Searching for columns to delete from carrier_statistic2. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table carrier_statistic3 INFO: Creating columns lists for carrier_statistic3. INFO: Searching for columns to delete from carrier_statistic3. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table gproc_statistics INFO: Creating columns lists for gproc_statistics. INFO: Searching for columns to delete from gproc_statistics. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table carrier_statistics INFO: Creating columns lists for carrier_statistics. INFO: Searching for columns to delete from carrier_statistics. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table pm_load_log INFO: Creating columns lists for pm_load_log. INFO: Searching for columns to delete from pm_load_log. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table nbr_statistics INFO: Creating columns lists for nbr_statistics. INFO: Searching for columns to delete from nbr_statistics. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table dynetgp_statistics INFO: Creating columns lists for dynetgp_statistics. INFO: Searching for columns to delete from dynetgp_statistics. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table axcdr_statistics INFO: Creating columns lists for axcdr_statistics. INFO: Searching for columns to delete from axcdr_statistics. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table vgcs_statistics INFO: Creating columns lists for vgcs_statistics. INFO: Searching for columns to delete from vgcs_statistics. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table entity _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 85
2007, Motorola General Business Use INFO: Creating columns lists for entity. INFO: Searching for columns to delete from entity. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table stored_selections INFO: Creating columns lists for stored_selections. INFO: Searching for columns to delete from stored_selections. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table bss_datetimes INFO: Creating columns lists for bss_datetimes. INFO: Searching for columns to delete from bss_datetimes. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table oml_statistics INFO: Creating columns lists for oml_statistics. INFO: Searching for columns to delete from oml_statistics. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table cbl_statistics INFO: Creating columns lists for cbl_statistics. INFO: Searching for columns to delete from cbl_statistics. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table pm_info INFO: Creating columns lists for pm_info. INFO: Searching for columns to delete from pm_info. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table pcu_statistics INFO: Creating columns lists for pcu_statistics. INFO: Searching for columns to delete from pcu_statistics. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table bss_statistics INFO: Creating columns lists for bss_statistics. INFO: Searching for columns to delete from bss_statistics. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table mtl_statistics INFO: Creating columns lists for mtl_statistics. INFO: Searching for columns to delete from mtl_statistics. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table gsl_statistics INFO: Creating columns lists for gsl_statistics. INFO: Searching for columns to delete from gsl_statistics. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table custom_statistics INFO: Creating columns lists for custom_statistics. INFO: Searching for columns to delete from custom_statistics. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table cell_statistics INFO: Creating columns lists for cell_statistics. INFO: Searching for columns to delete from cell_statistics. _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 86
2007, Motorola General Business Use pm_db_load: Processing columns deleted from cell_statistics: pm_db_load: Dropping columns for table cell_statistics Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. Successfully modified object LOADMAP DL_38033_1 \ Tue Nov 21 18:47:50 2006 18:47:50 Dynamically allocated new virtual shared memory segment (size 4096KB) Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table lmtl_statistics INFO: Creating columns lists for lmtl_statistics. INFO: Searching for columns to delete from lmtl_statistics. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table carrier_statistic4 INFO: Creating columns lists for carrier_statistic4. INFO: Searching for columns to delete from carrier_statistic4. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table reset_site_table INFO: Creating columns lists for reset_site_table. INFO: Searching for columns to delete from reset_site_table. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table subscription_list INFO: Creating columns lists for subscription_list. INFO: Searching for columns to delete from subscription_list. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table xbl_statistics INFO: Creating columns lists for xbl_statistics. INFO: Searching for columns to delete from xbl_statistics. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table nbr_entity INFO: Creating columns lists for nbr_entity. INFO: Searching for columns to delete from nbr_entity. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table device_selection INFO: Creating columns lists for device_selection. INFO: Searching for columns to delete from device_selection. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table stat_selection INFO: Creating columns lists for stat_selection. INFO: Searching for columns to delete from stat_selection. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table gbl_statistics INFO: Creating columns lists for gbl_statistics. INFO: Searching for columns to delete from gbl_statistics. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 87
2007, Motorola General Business Use You have new mail. INFO: Loading Table rsl_statistics INFO: Creating columns lists for rsl_statistics. INFO: Searching for columns to delete from rsl_statistics. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Loading Table dproc_statistics INFO: Creating columns lists for dproc_statistics. INFO: Searching for columns to delete from dproc_statistics. Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have new mail. INFO: Running ontape to reset the archive level omc_env: Command not found WARNING: Cannot access configuration file $INFORMIXDIR/etc/$ONCONFIG. INFO: Sun Microsystems Inc. SunOS 5.10 Generic January 2005 INFO: Program over. WARNING: Unable to reset the database to read-write! WARNING: Database is in read-only mode INFO: Revoking permissions from root user. INFO: Sun Microsystems Inc. SunOS 5.10 Generic January 2005 INFO: You have new mail. INFO: Shutting down Informix... /usr/omc/1.9.0.0.21/install_splat/pm_db_load: svcadm: not found \ INFO: Informix is off-line. INFO: Starting Up Informix... /usr/omc/1.9.0.0.21/install_splat/pm_db_load: svcadm: not found \ INFO: Informix is on-line. INFO: Updating table statistics... INFO: Sun Microsystems Inc. SunOS 5.10 Generic January 2005 INFO: You have new mail. INFO: INFO: Completed successfully. Preparing new High Performance Loader database... Done Dropping old High Performance Loader database... Done Importing new High Performance Loader database... Done INFO: Data load completed. INFO: Updating High Performance Loader database. INFO: Checking for an existing database. INFO: Deleting PM Violations tables... ERROR: Unable to find the output file /tmp/S03PmVioStop.logtmp.10900 FATAL ERROR: Unsuccessful iteration of PM Violations tables deletion (see /usr/omc/logs/cutover.log for details) INFO: S03PmVioStop failed: this does not affect the upgrade. INFO: Shutting down Informix Instance ./S51databaseUpgrade: svcadm: not found INFO: Starting Informix instance INFO: Informix instance started successfully Copying empty map file... Done Copying printer definition file... Done Copying FM configuration files... Done Creating site map... Done Configuring cronjobs for root... Done Configuring cronjobs for omcadmin... Done Setting Up Modem... Done INFO: Configuring PM Loader... FATAL ERROR: Unsuccessful iteration of PM Loader DB Objects creation (see /usr/omc/logs/cutover.log for details) cutover has completed successfully Stopping the third instance of Informix Sun Microsystems Inc. SunOS 5.10 Generic January 2005 Processing configuration file /var/install/upgrade/config/migrate_file_list.dat Migrating files File migration complete ****************************************************************************** * Migrating user information * _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 88
2007, Motorola General Business Use ****************************************************************************** - Updating crontab file for root Copying mail file for root - Copying crontab file for sys - Copying crontab file for adm - Copying crontab file for lp - Copying crontab file for uucp - Copying crontab file for omcadmin - Copying home directory /home/omcadmin - Home directory exists on target system... - Renaming existing directory... Copying mail file for omcadmin - Copying home directory /home/omcread - Home directory exists on target system... - Renaming existing directory... INFO: No users to be migrated ****************************************************************************** * Migrating group information * ****************************************************************************** INFO: No Groups to be migrated Writing the swap-to-new script /var/install/swap_to_new_install Writing the rollback script /a/var/install/fallback_to_old_install ****************************************************************************** * Preparing to stop OMC * ****************************************************************************** OMC outage will begin at this point All GUIs will be shut down Sun Microsystems Inc. SunOS 5.10 Generic January 2005 You have mail. Terminating OMC applications OMC Shutdown Complete. Shutting down the PM database engine... Done Shutting down the MIB database engine... Done Copying MIB database partitions Copying data for mib_db 16377+0 records in 16377+0 records out Copying data for mib_db1 16377+0 records in 16377+0 records out Copying data for mib_db_logs 16377+0 records in 16377+0 records out Modifying /a/usr/informix/etc/sqlhosts_OMC Modifying /a/usr/informix/etc/sqlhosts_OMC Modifying /a/usr/informix/etc/sqlhosts_OMC Modifying /a/usr/informix/etc/sqlhosts_OMC Modifying /a/usr/informix/etc/onconfig_OMC Modifying /a/usr/informix/etc/onconfig_OMC Modifying /a/usr/informix/etc/plconfig.std Modifying /a/usr/informix/etc/plconfig.std Modifying /a/usr/omc/config/global/pmAdminConfig.csh Modifying /a/usr/omc/config/global/pmAdminConfig.sh Modifying /a/usr/omc/config/global/pmInfxUserConfig.csh Modifying /a/usr/omc/config/global/pmInfxUserConfig.sh Removing inf7_OMC_serv_new 5001/tcp /a/etc/services Removing mcOMC_new 15031/tcp /a/etc/services Configuring disksuite on new side... Done Starting postupgrade cleanup ... /b/var/svc: _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 89
2007, Motorola General Business Use /b/var/run: /b/usr/omc: /b/usr/lib/svc: /b/usr/informix: /b/home: /b/etc/pam.conf: /b/etc: /b/dev/fd: /b/dev: /b: /a/zones: /a/var/run: /a/var: /a/usr/omc/ne_data/raw_stats: /a/usr/omc/ne_data/e1mon: /a/usr/omc/ne_data: /a/usr/omc/logs/sleeping_cell: /a/usr/omc/logs/bss_sec: /a/usr/omc/logs: /a/usr/omc: /a/usr: cd /a/solbak: /a/proc: /a/opt: /a/omcgen: /a/home: /a/etc/mnttab: /a/devices: /a/dev/fd: /a/cdrom/suninstall: /a/cdrom/cdrom0: /a: Common Platform Upgrade cleanup complete Copying logfiles to new side /a Calling swap_to_new_install script Updating the boot-device and rebooting About to reboot the system to swap to new installation Shutdown started. Tue Nov 21 19:02:52 GMT 2006 Changing to init state 6 - please wait Broadcast Message from root (pts/1) on somc211 Tue Nov 21 19:02:52... THE SYSTEM somc211 IS BEING SHUT DOWN NOW ! ! ! Log off now or risk your files being damaged Motorola Common Platform Upgrade script has completed # Connection to somc211.cork.cig.mot.com closed by foreign host.
C.3 Commit/Mirror Script

#/var/install/upgrade/scripts/commit
Motorola Common Platform Commit script has started Motorola Common Platform Commit script This script will enable disk mirroring on the new platform and complete the upgrade Press y to confirm commit y reading commit control file /var/install/upgrade/config/upgrade_control.dat _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 90
2007, Motorola General Business Use Starting commit phase PRE_COMMIT Phase PRE_COMMIT has completed with exit status 0 Interrupts have been disabled for phase HARDWARE_VERIFY Starting commit phase HARDWARE_VERIFY Phase HARDWARE_VERIFY has completed with exit status 0 Starting commit phase SETUP Phase SETUP has completed with exit status 0 Starting commit phase COMMIT fmthard: New volume table of contents now in place. fmthard: New volume table of contents now in place. fmthard: New volume table of contents now in place. fmthard: New volume table of contents now in place. INFO : Metadatabase exists on disk c0t0d0 INFO : Metadatabase exists on disk c0t1d0 INFO : Metadatabase exists on disk c0t2d0 INFO : Metadatabase exists on disk c0t3d0 Creating metadatabase on c2t4d0 Creating metadatabase on c2t5d0 Creating metadatabase on c2t6d0 Creating metadatabase on c2t7d0 ****************************************************************************** * Clearing c2 soft partitions * ****************************************************************************** initializing metadevice d24 initializing metadevice d29 initializing metadevice d34 initializing metadevice d39 initializing metadevice d44 initializing metadevice d49 initializing metadevice d54 initializing metadevice d59 initializing metadevice d64 initializing metadevice d69 initializing metadevice d74 initializing metadevice d79 initializing metadevice d84 initializing metadevice d89 initializing metadevice d94 initializing metadevice d99 initializing metadevice d104 initializing metadevice d109 initializing metadevice d114 initializing metadevice d119 initializing metadevice d124 initializing metadevice d129 initializing metadevice d22 initializing metadevice d27 initializing metadevice d32 initializing metadevice d37 initializing metadevice d42 initializing metadevice d47 initializing metadevice d52 initializing metadevice d57 initializing metadevice d62 initializing metadevice d67 initializing metadevice d72 _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 91
2007, Motorola General Business Use initializing metadevice d77 initializing metadevice d82 initializing metadevice d87 initializing metadevice d92 initializing metadevice d97 initializing metadevice d102 initializing metadevice d107 initializing metadevice d112 initializing metadevice d117 initializing metadevice d122 initializing metadevice d127 initializing metadevice d2 initializing metadevice d7 initializing metadevice d12 initializing metadevice d17 ****************************************************************************** * Preparing to attach mirrors where required * ****************************************************************************** Sub-mirror d1 attached Sub-mirror d2 not attached Attaching mirror d2 to top level mirror d0 d0: submirror d2 is attached Sub-mirror d6 attached Sub-mirror d7 not attached Attaching mirror d7 to top level mirror d5 d5: submirror d7 is attached Sub-mirror d11 attached Sub-mirror d12 not attached Attaching mirror d12 to top level mirror d10 d10: submirror d12 is attached Sub-mirror d16 attached Sub-mirror d17 not attached Attaching mirror d17 to top level mirror d15 d15: submirror d17 is attached Sub-mirror d21 attached Sub-mirror d22 not attached Attaching mirror d22 to top level mirror d20 d20: submirror d22 is attached Sub-mirror d26 attached Sub-mirror d27 not attached Attaching mirror d27 to top level mirror d25 d25: submirror d27 is attached Sub-mirror d31 attached Sub-mirror d32 not attached Attaching mirror d32 to top level mirror d30 d30: submirror d32 is attached Sub-mirror d36 attached Sub-mirror d37 not attached Attaching mirror d37 to top level mirror d35 d35: submirror d37 is attached Sub-mirror d41 attached Sub-mirror d42 not attached Attaching mirror d42 to top level mirror d40 d40: submirror d42 is attached Sub-mirror d46 attached Sub-mirror d47 not attached Attaching mirror d47 to top level mirror d45 _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 92
2007, Motorola General Business Use d45: submirror d47 is attached Sub-mirror d51 attached Sub-mirror d52 not attached Attaching mirror d52 to top level mirror d50 d50: submirror d52 is attached Sub-mirror d56 attached Sub-mirror d57 not attached Attaching mirror d57 to top level mirror d55 d55: submirror d57 is attached Sub-mirror d61 attached Sub-mirror d62 not attached Attaching mirror d62 to top level mirror d60 d60: submirror d62 is attached Sub-mirror d66 attached Sub-mirror d67 not attached Attaching mirror d67 to top level mirror d65 d65: submirror d67 is attached Sub-mirror d71 attached Sub-mirror d72 not attached Attaching mirror d72 to top level mirror d70 d70: submirror d72 is attached Sub-mirror d76 attached Sub-mirror d77 not attached Attaching mirror d77 to top level mirror d75 d75: submirror d77 is attached Sub-mirror d81 attached Sub-mirror d82 not attached Attaching mirror d82 to top level mirror d80 d80: submirror d82 is attached Sub-mirror d86 attached Sub-mirror d87 not attached Attaching mirror d87 to top level mirror d85 d85: submirror d87 is attached Sub-mirror d91 attached Sub-mirror d92 not attached Attaching mirror d92 to top level mirror d90 d90: submirror d92 is attached Sub-mirror d96 attached Sub-mirror d97 not attached Attaching mirror d97 to top level mirror d95 d95: submirror d97 is attached Sub-mirror d101 attached Sub-mirror d102 not attached Attaching mirror d102 to top level mirror d100 d100: submirror d102 is attached Sub-mirror d106 attached Sub-mirror d107 not attached Attaching mirror d107 to top level mirror d105 d105: submirror d107 is attached Sub-mirror d111 attached Sub-mirror d112 not attached Attaching mirror d112 to top level mirror d110 d110: submirror d112 is attached Sub-mirror d116 attached Sub-mirror d117 not attached Attaching mirror d117 to top level mirror d115 d115: submirror d117 is attached _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 93
2007, Motorola General Business Use Sub-mirror d121 attached Sub-mirror d122 not attached Attaching mirror d122 to top level mirror d120 d120: submirror d122 is attached Sub-mirror d126 attached Sub-mirror d127 not attached Attaching mirror d127 to top level mirror d125 d125: submirror d127 is attached Updating eeprom boot-device value Phase COMMIT has completed with exit status 0 Motorola Common Platform Commit script has completed
C.4 Rollback Script

#/var/install/upgrade/scripts/rollback
Motorola Common Platform Rollback script has started Motorola Common Platform Rollback script This script will rollback your platform Do you wish to proceed with rollback? (enter 'Y' or 'N'): Y Reading rollback control file /var/install/upgrade/config/upgrade_control.dat Starting postupgrade cleanup ... Common Platform Upgrade cleanup complete Tue Mar 8 11:44:20 SGT 2005 Starting S95informix Please wait shutting down the PM/OMC database engine... PM/OMC database engine has been shutdown. Please wait shutting down the MIB database engine... MIB database engine has been shutdown. S95informix: Completed successfully. ****************************************************************************** * Preparing to stop OMC * ****************************************************************************** OMC outage will begin at this point All GUIs will be shut down Please enter "Yes" to continue : Yes Sun Microsystems Inc. SunOS 5.9 You have mail. Terminating OMC applications
Generic Patch January 2005
****************************************************************************** * Clearing c0 soft partitions * ****************************************************************************** Clearing metadevices... Done fmthard: New volume table of contents now in place. fmthard: New volume table of contents now in place. _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 94
2007, Motorola General Business Use fmthard: New volume table of contents now in place. fmthard: New volume table of contents now in place. Checking metadatabases for c0... Done ****************************************************************************** * Clearing c0 soft partitions * ****************************************************************************** Clearing metadevices... Done Initializing metadevices... Done ****************************************************************************** * Preparing to attach mirrors where required * ****************************************************************************** Attaching submirrors... d20 d21 d26 d22 d23 d27 d29 d30 d31 d50 d51 d52 d53 d54 d55 d56 d57 d58 d59 d60 d61 d62 d63 d64 d65 d66 d67 d68 d69 d70 d71 d72 d73 d74 d75 d76 d77 d78 d79 Done Updating eeprom boot-device value ****************************************************************************** * Updating savecore device * ****************************************************************************** Dump content: kernel pages Dump device: /dev/md/dsk/d21 (swap) Savecore directory: /var/crash/omcsys7 Savecore enabled: yes Tue Mar 8 11:53:29 SGT 2005 Starting S95informix Please wait starting up the PM/OMC database engine... PM/OMC database engine has been started. Please wait starting up the MIB database engine... MIB database engine has been started. S95informix: Completed successfully. Sun Microsystems Inc. SunOS 5.9 Generic Patch January 2005 You have new mail. Starting MIBs - expecting MIB InformixServer omc_mib1 online.. Starting OMC applications [OMCINIT] Startup Version GSR8-1.8.0.0 [OMCINIT] Starting EVTMGR [OMCINIT] Starting LMMGR Motorola Common Platform Rollback script has completed
D GUI Server - Typical Script Output

D.1 Mirror Script
# /var/install/upgrade/scripts/mirror
Motorola Common Platform Mirror script has started Motorola Common Platform Mirror script This script will mirror your platform Press y to confirm mirror y reading mirror control file /var/install/upgrade/config/mirror_control.dat Starting mirror phase SETUP Phase SETUP has completed with exit status 0 Starting mirror phase PRE_HW_VERIFY The contents of /data will not be preserved after this phase Do you wish to continue with the phase? Please enter y or n y Phase PRE_HW_VERIFY has completed with exit status 0 Interrupts have been disabled for phase HARDWARE_VERIFY Starting mirror phase HARDWARE_VERIFY Phase HARDWARE_VERIFY has completed with exit status 0 Starting mirror phase PREINSTALL_PLATFORM Phase PREINSTALL_PLATFORM has completed with exit status 0 Starting mirror phase PRE_DISKSUITE_SETUP Installation of <SUNWmdg> was successful. Installation of <SUNWmdja> was successful. Installation of <SUNWmdnr> was successful. Installation of <SUNWmdnu> was successful. Installation of <SUNWmdr> was successful. Installation of <SUNWmdu> was successful. Installation of <SUNWmdx> was successful. *** IMPORTANT NOTICE *** This machine must now be rebooted in order to ensure that sane operation. Execute shutdown -y -i6 -g0 and wait for the "Console Login:" prompt. Phase PRE_DISKSUITE_SETUP has completed with exit status 0 Starting mirror phase DISKSUITE_SETUP Configuring disksuite ... Done Phase DISKSUITE_SETUP has completed with exit status 0 Starting mirror phase POST_DISKSUITE_SETUP Phase POST_DISKSUITE_SETUP has completed with exit status 0 Starting mirror phase S97SDS Disksuite Configuration in progress. Please wait...
2007, Motorola General Business Use May 23 11:25:02 sunblade9 reboot: rebooted by root May 23 11:25:02 sunblade9 syslogd: going down on signal 15 May 23 11:25:02 rpcbind: rpcbind terminating on signal. syncing file systems... done rebooting... Resetting ... Sun Blade 150 (UltraSPARC-IIe 550MHz), No Keyboard Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.6, 1024 MB memory installed, Serial #53217047. Ethernet address 0:3:ba:2c:7:17, Host ID: 832c0717. Initializing Initializing Initializing Initializing Initializing Initializing 1MB of memory at addr 1MB of memory at addr 15MB of memory at addr 16MB of memory at addr 480MB of memory at addr 512MB of memory at addr 5ff3a000 5fe46000 5f002000 5e002000 40000000 0-
Rebooting with command: boot Boot device: bootdisk File and args: | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / SunOS Release 5.8 Version Generic_108528-13 64-bit Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved. \ | / - \ | / - \ | / WARNING: forceload of misc/md_trans failed WARNING: forceload of misc/md_raid failed WARNING: forceload of misc/md_hotspares failed WARNING: forceload of misc/md_sp failed configuring IPv4 interfaces: eri0. Hostname: sunblade9 Configuring /dev and /devices Configuring the /dev directory (compatibility devices) The system is coming up. Please wait. checking ufs filesystems /dev/md/rdsk/d10: is logging. /dev/md/rdsk/d15: is logging. NIS domainname is omcadmin starting rpc services: rpcbind keyserv ypbind done. Setting netmask of eri0 to 255.255.255.0 Setting default IPv4 interface for multicast: add net 224.0/4: gateway sunblade9 syslog service starting. Print services started. volume management starting. Admin server is not running... Starting admin server... AdminSuite server started! Server com.sun.admin.cis.server.AdminServer_3_0 bound in RMI registry at port 5981 d0: submirror d2 is attached d5: submirror d7 is attached d10: submirror d12 is attached d15: submirror d17 is attached The system is ready. sunblade9 console login:
D.2 Verify Script

# /var/install/bin/verify_platform 320 blocks Motorola Common Platform Verify_platform script has started _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 97
2007, Motorola General Business Use Motorola Common Platform Verify_platform script This script will verify_platform your platform
Do you wish to proceed with the operation? (enter 'Y' or 'N'): [y,n,?,q] y Reading verify_platform control file /var/install/bin/config/verify_platform_control.dat ################################################# ## Output from /var/install/bin/scripts/system_profile ## Run at 101207-14:48:41 ################################################# Release 1.8.0.0.56 Server_Type Sun Blade 150 Processors 1 Memory_Size 1024 Megabytes Number of Disks 2 Total_Formatted_Space 34.4 GB Free_Formatted_Space 30.8 GB ****************************************************************************** * Preparing to detect the current software release * ****************************************************************************** Upgrading from a valid software release 1800 ****************************************************************************** * Script for DISKSUITE_VERIFY started * ****************************************************************************** Checking metadatabases... Done Checking metadatabases... Done
****************************************************************************** * Preparing to attach mirrors where required * ****************************************************************************** Attaching submirrors... | Done ****************************************************************************** * Checking status of system mirrors * ****************************************************************************** Checking metadevices... | / - Done ****************************************************************************** * Checking status of system mirrors * ****************************************************************************** Checking metadevices... | / - Done Updating savecore device ... Dump content: kernel pages Dump device: /dev/md/dsk/d5 (swap) Savecore directory: /var/crash/zuk14omc41 Savecore enabled: yes unmounting /cdrom/suninstall ...
2007, Motorola General Business Use ****************************************************************************** * Preparing to detect the current software release * ****************************************************************************** Upgrading from a valid software release 1800 System Verification complete Starting postupgrade cleanup ... Common Platform Upgrade cleanup complete Motorola Common Platform Verify_platform script has completed
D.3 Upgrade Script

# /var/install/upgrade/scripts/upgrade
Motorola Common Platform Upgrade script has started Motorola Common Platform Upgrade script This script will upgrade your platform Do you wish to proceed with the operation? (enter 'Y' or 'N'): Y reading upgrade control file /var/install/upgrade/config/upgrade_control.dat *********************************************************************** * Preparing to detect the current software release * ********************************************************************** Upgrading from a valid software release 1800 Interrupts have been disabled for phase HARDWARE_VERIFY *********************************************************************** * Preparing to detach mirrors * *********************************************************************** Gathering DiskSuite configuration information from System... Done Detaching mirrors... Done Validating Hardware ... GSM OMCR Preparing for Upgrade ... Setting default PROM values... Done Starting Solaris Install The install profile passes sanity tests OK Starting Solaris installation INFO: pfinstall execution complete Determining hostname... Done Creating default user profiles... Done Creating /var/adm/loginlog... Done Setting up logging for / file system... Done Setting up logging for /omcgen file system... Done Setting up logging for /usr/omc file system... Done Creating default admin file for pkgadd... Done Updating sys crontab... Done Turning off Power Management... Done Configuring Locale... Done Adjusting root's ULIMIT... Done Configuring /etc/auto_master ... Done Configuring default network interface (eri0)... Done Turning off IP Forwarding... Done Configuring /etc/inet/netmasks ... Done Updating /etc/inet/hosts ... Done Setting /etc/defaultdomain to localdomain... Done Setting /etc/defaultrouter to 175.3.41.84 ... Done Modifying FTP user list ... Done _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 99
2007, Motorola General Business Use Setting up the timeserver ... Done Locking system accounts... Done Syncing user passwords INFO : Beginning install of third party products INFO : The log file for Third Party Product installation is /var/install/logs/packages.log Installing Applix... Done Installing Enscript... Done Installing LibGCC... Done Installing Informix 9... Done Installing Python/OSP... Done Installing StorEdge Backup Client... Done Installing TCL... Done Installing TK... Done Installing OMC-R 1800... Done Installing OMC-R 1800... Done Installing OMC-R 1800 Help... Done Migrating files File migration complete *********************************************************************** * Migrating user information * *********************************************************************** - Copying crontab file for root - Copying crontab file for adm - Copying crontab file for lp INFO: No users to be migrated *********************************************************************** * Migrating group information * *********************************************************************** INFO: No Groups to be migrated Sun Microsystems Inc. SunOS 5.10 Generic January 2005 link_current has completed Monday May 23 12:23:01 IST 2005 Starting Configure_Informix Please wait installing the SQLHOSTS for the MMI... Please wait installing the TCP ports in /etc/services for the MMI Configure_Informix: Completed successfully. Configure_Informix has completed Reconfiguring CDE settings... Done cde_install has completed Not updating contents of /var/install/lib Not updating contents of /var/install/bin ================================================================= OMC Generic Cutover ================================================================= There are 1 OMC releases available. 1. OMC Release 1.9.0.0.21 <<-- CURRENT 2. QUIT - do nothing _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 100
2007, Motorola General Business Use Enter Choice: 1 About to cutover to OMC Release 1.9.0.0.21 Are you sure (Type Yes to confirm) ? Yes Cutting over to release 1.9.0.0.21... Relinking /usr/omc/current... Done Configuring file permissions... Done Creating startup files... Done Copying release specific scripts... Done Configuring cronjobs for root... Done Configuring cronjobs for omcadmin... Done cutover has completed successfully Writing the swap-to-new script /var/install/swap_to_new_install Writing the rollback script /a/var/install/fallback_to_old_install Configuring disksuite on new side... Done Starting postupgrade cleanup ... /a/usr/omc/ne_data/raw_stats: /a/usr/omc/ne_data: /a/usr/omc/config/global: /a/usr/omc: /a/proc: /a/omcgen: /a/home: /a: Common Platform Upgrade cleanup complete Updating the boot-device and rebooting About to reboot the system to swap to new installation Are you sure you want to continue(Type Y/y to confirm) ? y Shutdown started. Monday May 23 12:24:57 IST 2007
Changing to init state 6 - please wait THE SYSTEM sunblade9 IS BEING SHUT DOWN NOW ! ! ! Log off now or risk your files being damaged Motorola Common Platform Upgrade script has completed As the system begins to reboot output will look as follows: INIT: New run level: 6 The system is coming down. Please wait. System services are now being stopped. Print services stopped. umount: /cdrom/jumpstart_gsm-omcr1800.22/s2 busy umount: /cdrom/jumpstart_gsm-omcr1800.22/s1 busy umount: /cdrom/jumpstart_gsm-omcr1800.22/s3 busy umount: /cdrom/jumpstart_gsm-omcr1800.22/s5 busy umount: /cdrom/jumpstart_gsm-omcr1800.22/s0 busy umount: /cdrom/jumpstart_gsm-omcr1800.22/s4 busy The system is down. syncing file systems... done rebooting... Resetting ... Sun Blade 150 (UltraSPARC-IIe 550MHz), No Keyboard Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.6, 1024 MB memory installed, Serial #53217047. Ethernet address 0:3:ba:2c:7:17, Host ID: 832c0717. _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 101
2007, Motorola General Business Use Initializing Initializing Initializing Initializing Initializing Initializing 1MB of memory at addr 1MB of memory at addr 15MB of memory at addr 16MB of memory at addr 480MB of memory at addr 512MB of memory at addr 5ff3a000 -_ 5fe46000 -_ 5f002000 -_ 5e002000 -_ 40000000 -_ 0 -_
Rebooting with command: boot Boot device: bootdisk File and args: SunOS Release 5.9 Version Generic_112233-12 64-bit Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. configuring IPv4 interfaces: eri0. Hostname: sunblade9 Configuring /dev and /devices Configuring the /dev directory (compatibility devices) The system is coming up. Please wait. checking ufs filesystems /dev/rdsk/c0t0d0s6: is clean. /dev/rdsk/c0t0d0s4: is clean. NIS domain name is omcadmin starting rpc services: rpcbind keyserv ypbind done. Setting netmask of eri0 to 255.255.255.0 Setting default IPv4 interface for multicast: add net 224.0/4: gateway sunblade9 syslog service starting. starting NetWorker daemons: nsrexecd volume management starting. Disksuite Configuration in progress. Please wait... Disksuite configuration complete. May 23 12:27:28 sunblade9 reboot: rebooted by root May 23 12:27:28 sunblade9 syslogd: going down on signal 15 May 23 12:27:28 stfontserverd[333]: Terminating on receiving signal 15. syncing file systems... done rebooting... Resetting ... Sun Blade 150 (UltraSPARC-IIe 550MHz), No Keyboard Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.6, 1024 MB memory installed, Serial #53217047. Ethernet address 0:3:ba:2c:7:17, Host ID: 832c0717. Initializing Initializing Initializing Initializing Initializing Initializing 1MB of memory at addr 1MB of memory at addr 15MB of memory at addr 16MB of memory at addr 480MB of memory at addr 512MB of memory at addr 5ff3a000 -_ 5fe46000 -_ 5f002000 -_ 5e002000 -_ 40000000 -_ 0 -_
Rebooting with command: boot Boot device: bootdisk File and args: SunOS Release 5.9 Version Generic_112233-12 64-bit Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. WARNING: forceload of misc/md_trans failed _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 102
2007, Motorola General Business Use WARNING: forceload of misc/md_raid failed WARNING: forceload of misc/md_hotspares failed WARNING: forceload of misc/md_sp failed configuring IPv4 interfaces: eri0. Hostname: sunblade9 The system is coming up. Please wait. checking ufs filesystems /dev/md/rdsk/d15: is logging. /dev/md/rdsk/d10: is logging. NIS domain name is omcadmin starting rpc services: rpcbind keyserv ypbind done. Setting netmask of eri0 to 255.255.255.0 Setting default IPv4 interface for multicast: add net 224.0/4: gateway sunblade9 syslog service starting. starting NetWorker daemons: nsrexecd volume management starting. The system is ready.
D.4 Rollback Scripts

# /var/install/fallback_to_old_install
Updating the boot-device and rebooting About to reboot the system to previous installation Are you sure you want to continue(Type Y/y to confirm) ? y Shutdown started. Fri Oct 15 00:49:39 IST 2004 Changing to init state 6 - please wait THE SYSTEM sunblade9 IS BEING SHUT DOWN NOW ! ! ! Log off now or risk your files being damaged # INIT: New run level: 6 The system is coming down. Please wait. System services are now being stopped. stopping NetWorker daemons: nsr_shutdown -a -q Print services already stopped. The system is down. syncing file systems... done rebooting... Resetting ...
Sun Blade 150 (UltraSPARC-IIe 550MHz), No Keyboard Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.6, 1024 MB memory installed, Serial #53217047. Ethernet address 0:3:ba:2c:7:17, Host ID: 832c0717.
Initializing 1MB of memory at addr Initializing 1MB of memory at addr Initializing 15MB of memory at addr Initializing 16MB of memory at addr Initializing 480MB of memory at addr
5ff3a000 -_ 5fe46000 -_ 5f002000 -_ 5e002000 -_ 40000000 -_
2007, Motorola General Business Use Initializing 512MB of memory at addr 0 -_
Rebooting with command: boot Boot device: mirrordisk File and args: SunOS Release 5.8 Version Generic_108528-13 64-bit Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved. WARNING: forceload of misc/md_trans failed WARNING: forceload of misc/md_raid failed WARNING: forceload of misc/md_hotspares failed WARNING: forceload of misc/md_sp failed configuring IPv4 interfaces: eri0. Hostname: sunblade9 The system is coming up. Please wait. checking ufs filesystems /dev/md/rdsk/d15: is logging. /dev/md/rdsk/d10: is logging. NIS domainname is omcadmin starting rpc services: rpcbind keyserv ypbind done. Setting netmask of eri0 to 255.255.255.0 Setting default IPv4 interface for multicast: add net 224.0/4: gateway sunblade9 syslog service starting. Print services started. volume management starting. Admin server is not running... Starting admin server... The system is ready.
# /var/install/upgrade/scripts/rollback Motorola Common Platform Rollback script has started Motorola Common Platform Rollback script This script will rollback your platform Do you wish to proceed with rollback? (enter 'Y' or 'N'): Y reading rollback control file /var/install/upgrade/config/upgrade_control.dat Starting postupgrade cleanup ... Common Platform Upgrade cleanup complete *********************************************************************** * Clearing c0t0 soft partitions * *********************************************************************** Clearing metadevices... Done fmthard: New volume table of contents now in place. Checking metadatabases for c0t0... Done *********************************************************************** * Clearing c0t0 soft partitions * *********************************************************************** Clearing metadevices... Done Initializing metadevices... Done
2007, Motorola General Business Use *********************************************************************** * Preparing to attach mirrors where required * *********************************************************************** Attaching submirrors... d0 d5 d10 d15 Done Updating eeprom boot-device value Updating the boot-device and rebooting May 23 12:39:16 sunblade9 reboot: rebooted by root May 23 12:39:16 sunblade9 rpcbind: rpcbind terminating on signal. May 23 12:39:16 sunblade9 syslogd: going down on signal 15 syncing file systems... done rebooting... Resetting ... Sun Blade 150 (UltraSPARC-IIe 550MHz), No Keyboard Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.6, 1024 MB memory installed, Serial #53217047. Ethernet address 0:3:ba:2c:7:17, Host ID: 832c0717. Initializing Initializing Initializing Initializing Initializing Initializing 1MB of memory at addr 1MB of memory at addr 15MB of memory at addr 16MB of memory at addr 480MB of memory at addr 512MB of memory at addr 5ff3a000 -_ 5fe46000 -_ 5f002000 -_ 5e002000 -_ 40000000 -_ 0 -_
Rebooting with command: boot mirrordisk Boot device: /pci@1f,0/ide@d/disk@2,0:a File and args: SunOS Release 5.8 Version Generic_108528-13 64-bit Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved. WARNING: forceload of misc/md_trans failed WARNING: forceload of misc/md_raid failed WARNING: forceload of misc/md_hotspares failed WARNING: forceload of misc/md_sp failed configuring IPv4 interfaces: eri0. Hostname: sunblade9 The system is coming up. Please wait. checking ufs filesystems /dev/md/rdsk/d15: is logging. /dev/md/rdsk/d10: is logging. NIS domainname is omcadmin starting rpc services: rpcbind keyserv ypbind done. Setting netmask of eri0 to 255.255.255.0 Setting default IPv4 interface for multicast: add net 224.0/4: gateway sunblade9 syslog service starting. Print services started. volume management starting. Admin server is not running... Starting admin server... The system is ready.
D.5 Commit Script

# /var/install/upgrade/scripts/commit Motorola Common Platform Commit script has started _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 105
2007, Motorola General Business Use Motorola Common Platform Commit script This script will enable disk mirroring on the new platform and complete the upgrade Press y to confirm commit y reading commit control file /var/install/upgrade/config/upgrade_control.dat Starting commit phase PRE_COMMIT Phase PRE_COMMIT has completed with exit status 0 Interrupts have been disabled for phase HARDWARE_VERIFY Starting commit phase HARDWARE_VERIFY Phase HARDWARE_VERIFY has completed with exit status 0 Starting commit phase SETUP Phase SETUP has completed with exit status 0 Starting commit phase COMMIT VTOC copied from c0t0d0 to c0t2d0 Creating metadatabase on c0t2d0 *********************************************************************** * Clearing c0t2 soft partitions * *********************************************************************** initializing metadevice d2 d2: Concat/Stripe is setup initializing metadevice d7 d7: Concat/Stripe is setup initializing metadevice d12 d12: Concat/Stripe is setup initializing metadevice d17 d17: Concat/Stripe is setup A Non-legacy mirroring configuration has been detected *********************************************************************** * Preparing to attach mirrors where required * *********************************************************************** Sub-mirror d1 attached Sub-mirror d2 not attached Attaching mirror d2 to top level mirror d0 Sub-mirror d6 attached Sub-mirror d7 not attached Attaching mirror d7 to top level mirror d5 Sub-mirror d11 attached Sub-mirror d12 not attached Attaching mirror d12 to top level mirror d10 Sub-mirror d16 attached Sub-mirror d17 not attached Attaching mirror d17 to top level mirror d15 Updating eeprom boot-device value Phase COMMIT has completed with exit status 0 Starting commit phase POST_COMMIT Phase POST_COMMIT has completed with exit status 0 Motorola Common Platform Commit script has completed
E Migration - Typical Script Output

E.1 migrate Script
Motorola Common Platform Migrate script has started Motorola Common Platform Migrate script This script will migrate your platform Press y to confirm migrate y reading migrate control file /var/install/upgrade/config/upgrade_control.dat Starting migrate phase PRE_HARDWARE_VERIFY Platform is valid for migration Phase PRE_HARDWARE_VERIFY has completed successfully Starting migrate phase MIGRATE_SETUP *********************************************************************** * Enter details of replacement server * *********************************************************************** Enter IP address of replacement server: 175.3.44.169
*********************************************************************** * Sharing and mounting remote filesystems * *********************************************************************** Adding share for / Mounting 175.3.44.169:/ Adding share for /usr Mounting 175.3.44.169:/usr Adding share for /var Mounting 175.3.44.169:/var Adding share for /opt Mounting 175.3.44.169:/opt Adding share for /omcgen Mounting 175.3.44.169:/omcgen Adding share for /home Mounting 175.3.44.169:/home Adding share for /solbak Mounting 175.3.44.169:/solbak Adding share for /usr/omc Mounting 175.3.44.169:/usr/omc Adding share for /usr/omc/ne_data Mounting 175.3.44.169:/usr/omc/ne_data Adding share for /usr/omc/ne_data/raw_stats Mounting 175.3.44.169:/usr/omc/ne_data/raw_stats Adding share for /cdrom/jumpstart_gsm-omcr1800.27/s5 Mounting 175.3.44.169:/cdrom/jumpstart_gsm-omcr1900.16/s5 Adding share for /cdrom/jumpstart_gsm-omcr1900.16/s4 Mounting 175.3.44.169:/cdrom/jumpstart_gsm-omcr1900.16/s4 Adding share for /cdrom/jumpstart_gsm-omcr1900.16/s3 Mounting 175.3.44.169:/cdrom/jumpstart_gsm-omcr1900.16/s3 _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 107
2007, Motorola General Business Use Adding share for /cdrom/jumpstart_gsm-omcr1900.16/s2 Mounting 175.3.44.169:/cdrom/jumpstart_gsm-omcr1900.16/s2 Adding share for /cdrom/jumpstart_gsm-omcr1900.16/s1 Mounting 175.3.44.169:/cdrom/jumpstart_gsm-omcr1900.16/s1 Phase MIGRATE_SETUP has completed successfully Starting migrate phase MIGRATE_FILES INFO: Migrating files listed in /var/install/upgrade/config/altern_migrate_file_list.dat Processing configuration file /var/install/upgrade/config/altern_migrate_file_list.dat Migrating files File migration complete *********************************************************************** * Migrating user information * *********************************************************************** - Updating crontab file for root Copying mail file for root - Copying crontab file for sys Copying mail file for sys - Copying crontab file for adm - Copying crontab file for lp - Copying crontab file for uucp - Copying crontab file for omcadmin - Copying home directory /home/omcadmin - Home directory exists on target system... - Renaming existing directory... Copying mail file for omcadmin - Copying home directory /home/omcread - Home directory exists on target system... - Renaming existing directory... INFO: No users to be migrated *********************************************************************** * Migrating group information * *********************************************************************** INFO: No Groups to be migrated Phase MIGRATE_FILES has completed successfully Starting migrate phase MIGRATE_DATABASE *********************************************************************** * Preparing to export the OMC database * *********************************************************************** Changing to user omcadmin to export the OMC database The logfile for the dbexport can be found in /usr/omc/logs Sun Microsystems Inc. SunOS 5.10 Generic May 2005 You have mail. [H [JLogging unload to /usr/omc/logs/pm_db_unload.log.26705
WARNING Keeping your PM data after the unload could fail unless the following are checked: (1) ULIMIT has been unset to enable very large files be created. _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 108
2007, Motorola General Business Use (2) Sufficient disk space is available on your filesystem. Do you want to keep your PM data after upgrade (yes/no) ? no Do you want to keep your custom data after upgrade (yes/no) ? Custom data includes subscriptions, custom statistics, network entities amongst others. no You have opted to retain neither the statistics nor the custom data. The following compressed unload files already exist in /usr/omc/ne_data: /usr/omc/ne_data/axcdr_statistics.unl.Z /usr/omc/ne_data/bss_datetimes.unl.Z /usr/omc/ne_data/bss_statistics.unl.Z /usr/omc/ne_data/carrier_statistic2.unl.Z /usr/omc/ne_data/carrier_statistic3.unl.Z /usr/omc/ne_data/carrier_statistic4.unl.Z /usr/omc/ne_data/carrier_statistics.unl.Z /usr/omc/ne_data/cbl_statistics.unl.Z /usr/omc/ne_data/cell_statistics.unl.Z /usr/omc/ne_data/custom_statistics.unl.Z /usr/omc/ne_data/device_selection.unl.Z /usr/omc/ne_data/dproc_statistics.unl.Z /usr/omc/ne_data/dynetgp_statistics.unl.Z /usr/omc/ne_data/entity.unl.Z /usr/omc/ne_data/gbl_statistics.unl.Z /usr/omc/ne_data/gproc_statistics.unl.Z /usr/omc/ne_data/gsl_statistics.unl.Z /usr/omc/ne_data/lmtl_statistics.unl.Z /usr/omc/ne_data/mtl_statistics.unl.Z /usr/omc/ne_data/nbr_entity.unl.Z /usr/omc/ne_data/nbr_statistics.unl.Z /usr/omc/ne_data/nbr_status.unl.Z /usr/omc/ne_data/oml_statistics.unl.Z /usr/omc/ne_data/pcu_statistics.unl.Z /usr/omc/ne_data/pm_info.unl.Z /usr/omc/ne_data/reset_site_table.unl.Z /usr/omc/ne_data/rsl_statistics.unl.Z /usr/omc/ne_data/stat_selection.unl.Z /usr/omc/ne_data/stored_selections.unl.Z /usr/omc/ne_data/subscription_list.unl.Z /usr/omc/ne_data/subscriptions.unl.Z /usr/omc/ne_data/xbl_statistics.unl.Z To continue with the upgrade these files will be deleted! Do you wish to continue with the upgrade (yes/no) ? yes Files successfully removed. pm_db_unload completed with no unload at Wed Aug 3 11:20:24 IST 2005 *********************************************************************** * Upgrading PM database * *********************************************************************** Upgrading PM database... |
2007, Motorola General Business Use *********************************************************************** * Preparing to stop OMC * *********************************************************************** OMC outage will begin at this point All GUIs will be shut down Please enter "Yes" to continue : Yes Sun Microsystems Inc. SunOS 5.10 Generic May 2005 You have new mail. Terminating OMC applications OMC Shutdown Complete. Shutting down the MIB database engine... Done Starting the MIB database engine... Done *********************************************************************** * Exporting MIB database * *********************************************************************** Exporting MIB database... this may take a while... *********************************************************************** * Importing MIB database on 175.3.44.169 * *********************************************************************** Dropping any existing MIB databases Importing MIB database... this may take a while... *********************************************************************** * Upgrading MIB database on 175.3.44.169 * *********************************************************************** Upgrading MIB database... this may take a while... Warning: no access to tty; thus no job control in this shell... Sun Microsystems Inc. SunOS 5.10 Generic May 2005 You have new mail. Synonym created.
Permission granted.
Phase MIGRATE_DATABASE has completed successfully Starting migrate phase CLEANUP Starting postupgrade cleanup ... /a/var: /a/usr/omc/ne_data/raw_stats: /a/usr/omc/ne_data: /a/usr/omc: /a/usr: /a/solbak: /a/opt: /a/omcgen: /a/home: /a/cdrom/jumpstart_gsm-omcr1800.27/s5: _________________________________________________________________________________________________ Doc ID: OSS-GSR9-CUSTSUP-UG-001 Doc Version: 1.7 110
2007, Motorola General Business Use /a/cdrom/jumpstart_gsm-omcr1800.27/s4: /a/cdrom/jumpstart_gsm-omcr1800.27/s3: /a/cdrom/jumpstart_gsm-omcr1800.27/s2: /a/cdrom/jumpstart_gsm-omcr1800.27/s1: /a: Common Platform Upgrade cleanup complete Phase CLEANUP has completed successfully Starting migrate phase POST_CLEANUP Updating shares on 175.3.44.169 share_nfs: /usr/omc/config/global: parent-directory (/usr/omc) already shared share_nfs: /usr/local: parent-directory (/usr) already shared share_nfs: /usr/omc/config/global: parent-directory (/usr/omc) already shared share_nfs: /usr/local: parent-directory (/usr) already shared Phase POST_CLEANUP has completed successfully NFS fsstat failed for server 175.3.44.169: error 7 (RPC: Authentication error) df: cannot statvfs /cdrom/jumpstart_gsm-omcr1900.16/s0: Permission denied NFS fsstat failed for server 175.3.44.169: error 7 (RPC: Authentication error) df: cannot statvfs /cdrom/jumpstart_gsm-omcr1900.16/s1: Permission denied Motorola Common Platform Migrate script has completed
F COP TOOLS Gui Server related workarounds Workaround to reinstall Tools during GSR9 Major upgrade on Gui Servers
BEFORE upgrading a GSR8 1.8.x.0 GUI Server to GSR9 1.9.x.0 1. Login in to the GUI Server as user asaadmin 2. Stop the ECT Server:
/usr/omc/ne_data/ECTv2/ectSer stop
3. Stop the postmaster:

/gen/tools/pgsql/bin/pg_ctl stop -m fast -D /gen/tools/pgsql/data
4. tar and zip the whole /gen/tools/pgsql directory,

cd /gen/tools/ tar -cvf pgsqlGSR8.tar pgsql gzip pgsqlGSR8.tar cp pgsqlGSR8.tar.gz /home/asaadmin
AFTER completing the upgrade of a GUI Server . 1. Login in to the GUI Server as user asaadmin 2. Configure the System Settings. Refer to [9] for the details of this procedure. "Shared memory configuration of GUI Server" under "Installing COP", and "General installation information" Chapter 6. The details of the guidance is shown in "GUI Server configuration for ECT" in Chapter 6, which provides the sample system file for Sunblade150 and Netra 210 machines. NOTE: root access is needed for changing /etc/system file.
3. If the GUI Server is Sunblade150, execute the following commands as user root
cd / ln -s /omcgen /gen exit
4. untar and unzip the whole /gen/tools/pgsql directory, execute the following commands as user root
cd /gen ls
(Note: If the /gen/tools/ directory does not exist, please create it by typing command mkdir /gen/tools)
chmod 777 tools
Execute the following commands as user asaadmin

cd /gen/tools/ cp /home/asaadmin/pgsqlGSR8.tar.gz . gunzip pgsqlGSR8.tar.gz tar -xvf pgsqlGSR8.tar chmod 700 /gen/tools/pgsql/data
5. start the ectSer

/usr/omc/ne_data/ECTv2/ectSer start
6. Upgrade the ECT software with the procedures in the "Upgrading" chapter in the COP Release Notes Reference [9].
G NHA GUI Server related workarounds Workaround to reinstall NHA GUI on OMC-R GUI server(s) after GSR8 1.8.x.0 to GSR9 1.9.x.0 Upgrade
Preconditions: OMC-R GUI Server is upgraded to GSR9 1.9.x.0. COPs workaround in Appendix F is applied. RSH connections between NHA and GUI Server(s) are available. 1900.1BA NHA CD is in the NHA Server.
Perform the following steps: 1. Login to NHA server as omcadmin. 2. Cleanup /usr/gsm/config/local/installed_software_listing
cd /usr/gsm/config/local/installed_software_listing rm server_<GUI_Server_hostname>_*
3. Repeat step #2 for every OMC-R GUI Server that has NHA GUI installed. 4. Login as root on the NHA Server and reinstall NHA GUI.
cd /usr/gsm/cdrom_install ./S31tw_mmi <GUI_Server_hostname>
5. Repeat step #4 for every OMC-R GUI Server for which NHA software is to be installed.
H Manual ssh Configuration

This appendix can be used when: - Running the migration it is necessary to set up SSH connections between the SOURCE and TARGET platforms. The two systems must be able to connect as user root without providing passwords. - Running a remote GUI Server upgrade, where the DVD media is in the Single Platform Processor. H.1 Migration Scenario For a migration scenario complete the following as user root on the SOURCE platform:
ssh-keygen -t rsa
Accept all the default answers for questions prompted. Add the contents of the file /.ssh/id_rsa.pub on the SOURCE platform to the file /.ssh/authorized_keys on the TARGET platform. An example follows: On the Source Platform
cd /.ssh scp id_rsa.pub <TARGET IP address>:/.ssh/id_rsa.pub.source ssh <TARGET IP address> cat /.ssh/id_rsa.pub.source >> /.ssh/authorized_keys
To validate that the ssh setup has completed successfully, as user root on the SOURCE platform complete the following:
ssh root@<TARGET_IP_ADDRESS>
Where <TARGET_IP_ADDRESS> is the temporary IP address of the Single Platform Processor chosen and recorded in the prerequisites section. H.2 GUI Server Scenario For a remote GUI Server Upgrade scenario complete the following as user root on the GUI Server platform:
ssh-keygen -t rsa
Accept all the default answers for questions prompted. Add the contents of the file /.ssh/id_rsa.pub on the Single Platform Processor to the file /.ssh/authorized_keys on the GUI Server. An example follows: On the Single Platform Processor:
cd /.ssh scp id_rsa.pub <TARGET IP address>:/.ssh/id_rsa.pub.source
ssh <TARGET IP address> cat /.ssh/id_rsa.pub.source >> /.ssh/authorized_keys
To validate that the ssh setup has completed successfully, as user root on the Single Platform Processor complete the following:
ssh root@<TARGET_IP_ADDRESS>
Where <TARGET_IP_ADDRESS> is the IP address of the GUI Server chosen and recorded in the prerequisites section.
Configuring secure services for multiple OMC-Rs
During the upgrade phase from GSR8 to GSR9, customers will have OMC-Rs on different releases, that is some on GSR9, and the remainder on GSR8 which are yet to be upgraded to GSR9. In this scenario, OMC-R functionality which spans across multiple OMC-Rs such as license audit (FMON) and pcellSync, will not work correctly. To correct this, the following procedure must be applied: 1. On the GSR9 OMC-R single platform processors, rsh must be temporarily enabled until all OMCRs are upgraded to GSR9. As user root on the GSR9 machine, run the command:
svcadm enable rexec
Check the service is enabled properly by running:

svcs -a | grep rexec online Feb_02 svc:/network/rexec:default
2. On the GSR8 OMC-R single platform processors, secure services (ssh) must be enabled. Check the correct packages are installed on GSR8 by running the following commands as user root:
pkginfo | egrep ssh
The following packages should be listed:

SUNWsshcu SUNWsshdr SUNWsshdu SUNWsshr SUNWsshu
Ensure that ssh is running, by running the following as root:

ls -l /var/run/sshd.pid
If this file does not exist, then need to enable ssh daemon by running as root:
/etc/init.d/sshd start
3. Ensure that password-less ssh connections are enabled between the remote OMCs. (see Appendix K). 4. Once all OMC-Rs are running on GSR9, rsh must be disabled. As user root on all GSR9 machines, run below command:
svcadm disable rexec
Check the service is properly disabled by running:

svcs -a | grep rexec disabled Feb_02 svc:/network/rexec:default
GSM OMC-R 1.9.0.0.X to 1.9.0.0.Y Point Release Upgrade Guide

OSS-GSR9-CUSTSUP-UG-004 Abstract
This document describes the procedure for a point release upgrade from 1.9.0.0.X to 1.9.0.0.Y
Audience: Customer Information Authoring Organization: System Administration Development, Swindon Version: 1.2 Status: Released 9 Nov 2007
1.0
1.0 2.0 3.0 4.0 5.0
5.1 5.2 5.3 5.4 5.5
Table of Contents
Table of Contents ...............................................................................................ii Revision History ................................................................................................iv References...........................................................................................................v Glossary of Terms .............................................................................................vi General Information..........................................................................................1
OVERALL PROCEDURE WORK FLOW ......................................................................................... 2 SCOPE, PURPOSE AND AUDIENCE .............................................................................................. 2 DOCUMENT FORMAT CONVENTIONS ......................................................................................... 2 PROCEDURE IMPACTS ................................................................................................................ 2 SUMMARY ................................................................................................................................. 3
6.0
6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8
Preparation.........................................................................................................4
REQUIRED INFORMATION .......................................................................................................... 4 UPGRADE PREREQUISITES ......................................................................................................... 4 SYSTEMS BACKUP ..................................................................................................................... 5 VERIFY THE GSR9 DVD MEDIA ............................................................................................... 6 SETUP UPGRADE LIBRARIES ....................................................................................................... 6 GENERAL PREPARATION ........................................................................................................... 7 UPDATE /VAR/INSTALL/SC_CONF.SH ......................................................................................... 8 UPDATE CM DATABASE CONFIGURATION ................................................................................ 9
7.0
7.1 7.2 7.3 7.4 7.5 7.6 7.7 7.8 7.9 7.10 7.11
Single Platform Processor - Point release upgrade Procedure Tasks.........10

POINT RELEASE UPGRADE PROCEDURE WORK FLOW .............................................................. 10 PATCH INSTALLATION ............................................................................................................. 10 TOOLS AND ADJUNCT PRODUCTS ............................................................................................ 12 UPGRADE THE SINGLE PLATFORM PROCESSOR ....................................................................... 12 PRE-CUTOVER PROCEDURES .................................................................................................... 14 POST-CUTOVER PROCEDURES .................................................................................................. 14 EXAMINE POINT RELEASE UPGRADE LOGFILES ....................................................................... 16 MANDATORY PM DATABASE TASKS ...................................................................................... 16 TOOLS AND ADJUNCT PRODUCTS ............................................................................................ 18 TURNING OFF WARNING ALARMS IN THE MAIN ALARM WINDOW ............................................. 19 COMPLETE FILESYSTEM BACKUP ............................................................................................ 19
8.0
8.1 8.2 8.3 8.4 8.5 8.6
Single Platform Processor - Rollback Procedure Tasks...............................20

TOOLS AND ADJUNCT PRODUCTS ............................................................................................ 20 ROLL BACK PROCEDURE ......................................................................................................... 20 PRE-CUTOVER PROCEDURES .................................................................................................... 21 POST-CUTOVER PROCEDURES .................................................................................................. 22 ROLLBACK LOGS ..................................................................................................................... 22 TOOLS AND ADJUNCT PRODUCTS ............................................................................................ 23
9.0
9.1 9.2 9.3 9.4 9.5 9.6 9.7 9.8
GUI Server - Point release upgrade Procedure Tasks .................................24

GUI SERVER POINT RELEASE UPGRADE PROCEDURE WORK FLOW ......................................... 24 REBOOT THE GUI SERVER....................................................................................................... 24 PATCH INSTALLATION ............................................................................................................. 24 UPGRADE THE GUI SERVER .................................................................................................... 26 PRE-CUTOVER WORKAROUNDS................................................................................................ 27 POST-CUTOVER WORKAROUNDS.............................................................................................. 28 EXAMINE POINT RELEASE UPGRADE LOGFILES ....................................................................... 28 COMPLETE FILESYSTEM BACKUP ............................................................................................ 29
10.0
10.1
GUI Server - Rollback Procedure Tasks....................................................30

ROLLBACK PROCEDURE .......................................................................................................... 30
A. Point Release Upgrade Typical Script Output for Single Platform Processor and GUI Server (all platforms) ...............................................................32
A.1 A.2 OUTPUT FOR OMC-R POINT RELEASE UPGRADE ..................................................................... 32 OUTPUT FOR GUI SERVER POINT RELEASE UPGRADE .............................................................. 60
Doc ID: OSS-GSR9-CUSTSUP-UG-004 Doc Version: 1.2
ii
B. C. D.
Using swtool to remove an old OMCR Software load ..................................64 OSI re-cutover after 1.9.0.0.X to 1.9.0.0.Y OMC-R Point release upgrade65 What to do if swtool fails to install your new packages................................70
iii
2.0
Revision History
Date
1 Oct 2007
st
Version
1.0
Author
Sys Admin Development Sys Admin Development Sys Admin Development
Description
Original Draft
Release
Initial version to support 1900.24 to 1900.27
1.1. 1.2
17 Oct 2007 9th Nov 2007
Updates to OSI procedures and Updates after review Updates to include NBI and OMC Utils
iv
3.0
References
[1] WSG Product Upgrade Strategy Template 001 [2] GSM OMC-R 1900 Clean Install Manual [3] GSM OMC-R 1900 System Admin Manual [4] NHA Software Release Notes [5] OMC-R Release Notes, GSR9 1900.x, 1900.y [6] NBI Release Notes [7] COP Software Release Notes [8] GSM Alert Bulletin - How to correct wrongly configured OMC-R MIB Informix instance after WSG-PROC-SYSU-TMPLT68P02901W47-S 68P02901W19-S 68P0200W77-S 68P02901W74-S 68P02901W73 68P02900W69 GSM_A_OMC_RCD_01
GSR9 upgrade
4.0
CDE
Glossary of Terms
Common Desktop Environment Compact Disk Read Only Memory Digital Versatile Disc Read Only Memory Installing GSM OMC-R on a network for the first Procedure for changing from one GSM OMC-R release to another Digital Audio Tape Fibre Channel Arbitrated Loop. This is a disk drive technology. Global System for Mobile Communications GSM OMC-R machine whose GUI display is being exported from a GUI Server GSM OMC-R machine which may export a GUI to another machine High-speed Serial Interface Installing a specific product with a specific software release North Bound Interface Network File System Network Health Analyst Network Information Service Operations and Maintenance Centre - Radio Open Systems Interconnect Model Procedure for restoring an earlier GSM OMC-R release A Netra20/Netra440/SunFire 4800/4900 GSM OMC-R Low-End or High-End system combining System Processor and GUI Processor functionality Traffic Channel Procedure for moving to a newer GSM OMC-R release
vi
CD-ROM DVD-ROM Clean Install time Cutover DAT FCAL GSM GUI Client GUI Server HSI Installation NBI NFS NHA NIS OMC-R OSI Rollback Single Platform Processor
TCH Upgrade
Upgrade time Outage time Remote Machine Remote Install
Total time for the complete upgrade of the OMCR Total time during which the OMC is non-functional Machine on a separate sub-net Where the Media is in a different machine to the one being installed
vii
5.0
General Information
This manual is only to be used by System Administrators who have a good knowledge of UNIX and of how the GSM OMC-R functions. This is a generic upgrade guide for point release upgrades within GSR9. For all commands replace X with the point release being upgraded from and replace Y with the point release being upgrade too. Read all the relevant sections of this point release upgrade guide before proceeding so that tasks can be scheduled in the appropriate order. Read the latest Release Notes for GSR9 1.9.0.0.Y carefully before proceeding with the point release upgrade for installation/upgrade instructions specific to this release. The GSM OMC-R may not start if the workarounds specified in these Release Notes are not implemented. It is recommended that the point release upgrade procedure be completed in a terminal type window and not the console window. It is also recommended that the point release upgrade procedure is completed by logging into the system directly as user root and not using the su command. When connecting to the Platform using the console connection with a PC/laptop. Make sure you have read and fully understand the appropriate PC/laptop documentation in association with the SUN documentation with specific reference to the sending of automatic break/cntrl sequences through the console connection. The consequences of not understanding what you are doing could cause the Platform to halt and return to the OBP prompt. Examples of automatic break/control sequences are, disconnecting the connection, closing a laptop screen, going to power save mode.
5.1
Overall Procedure Work Flow
5.2 Scope, Purpose and Audience This document is intended for customers and describes the procedure to upgrade a GSM OMC-R Single Platform Processor from GSR9 1.9.0.0.X to GSR9 1.9.0.0.Y and the procedure to upgrade a GSM OMC-R GUI Server from GSR9 1.9.0.0.X to GSR9 1.9.0.0.Y. The point release upgrade procedures contained within this document cover the platforms: Single Platform Processor: SUN Netra20/N440/SunFire 4800/4900 Server GUI Server: Sunblade150/Netra 210/Flexible platform NOTE: No action is required for GUI client platforms as they are supported.
5.3 Document Format Conventions The following formatting conventions are used in this document. Table 1: Document Format Conventions
Format Meaning Disk device reference, for example, <c0t0d0s0> Command to be completed Tick box to be completed
<DISK Device_ID>
command
5.4 Procedure Impacts This GSM OMC-R Single Platform Processor point release upgrade procedure will incur outage. Currently it is estimated that the outage time should be in the region of 15 minutes.
Doc ID: OSS-GSR9-CUSTSUP-UG-004 Doc Version: 1.2 2
Note: Time durations are not given for individual steps as the steps vary depending on the system being upgraded. 5.5 Summary Having completed reading this introduction chapter, refer to the following chapters relevant to the procedure being completed: Single Platform Processor Point Release UPGRADE: Follow chapters 6.0 and 7.0. Single Platform Processor Point Release ROLLBACK after upgrade: Follow chapter 8.0. GUI Server Point Release Upgrade: Follow chapter 6.0 and 9.0. GUI Server Point Release ROLLBACK after upgrade: Follow chapter 10.0.
6.0
Preparation
This section describes the procedures to be completed in order to prepare the Single Platform Processor and GUI Servers for point release upgrade. 6.1 Required Information
Ensure that all the tables below are completed before beginning the point release upgrade procedure. Single Platform Processor Host name Internet Address Netmask Aliases
(Defaults supplied)
omc_splat omc_4gl omc_pm <hostname.domainname>
GUI Server(s)
(Complete details for all relevant GUI server platforms)
Host name Internet Address Location (local/remote) A GUI Server Processor is considered to be local if it is on the same sub-net as the Single Platform Processor. A remote machine resides on a separate sub-net to the Single Platform Processor. 6.2 Upgrade Prerequisites Ensure that the following prerequisites are available before commencing the point release upgrade. Software Motorola GSR9 1.9.0.0.Y inc OMC Software and Jumpstart DVDROM Motorola GSR9 1.9.0.0.Y Additional OMC Software DVDROM StorEdge Enterprise Backup Software License [where applicable] NBI Corba Server [where applicable] NHA Server [where applicable]
Available
Documentation OMC-R System Admin GSR9 OMC-R Clean Install GSR9 NHA Release Notes OMC-R Release Notes GSR9 1.9.0.0.X, 1.9.0.0.Y NBI Release Notes [where applicable] COP Software Release Notes [where applicable] OSI Software Release Notes [where applicable] Datagen Software Release Notes [where
applicable]
Part Number 68P02901W19-S 68P02901W47-S 68P02900W77-S 68P02901W74-S 68P02901W73 68P02900W69 68P02901W70 68P02900W76
Available
6.3
Systems Backup
Task Description A full backup of all the file systems on the different processors MUST be performed BEFORE proceeding with the point release upgrade. This should include the Single Platform Processor and GUI Servers. A level-0 archive of the omc_db and mib_db databases on the Single Platform Processor MUST be performed. Refer to section [3] for details of the backup procedures.
6.4
Verify the GSR9 DVD Media Task Description Validate the DVD media. Ensure this task is completed on all GSR9 DVD media delivered. Pre-checks - Ensure that the task is completed as user root on the Single Platform Processor. Task Steps OMC Software and Jumpstart DVD Insert the first DVD, GSR9 1.9.0.0.Y OMC Software and Jumpstart DVD, into the DVD drive, and then execute the command:
/cdrom/cdrom0/s0/suninstall/check_dvd
If the command above returns anything other than the following message, No Errors were detected Then DO NOT continue with the upgrade and contact the relevant support organization. Additional OMC Software DVD Insert the second DVD, GSR9 1.9.0.0.Y Additional OMC Software DVD into the DVD drive, and then execute the command:
/cdrom/cdrom0/check_dvd
If the command above returns anything other than the following message, No Errors were detected Then DO NOT continue with the upgrade and contact the relevant support organization. 6.5 Setup upgrade libraries Task Description This task will install the necessary upgrade scripts, library files and configuration files to the /var/install/upgrade directory. Pre-checks - Ensure that the GSR9 1.9.0.0.Y OMC Software and Jumpstart DVD is in the media drive in the Single Platform Processor.
- Ensure that the task is completed as user root on the Single Platform Processor. Task Steps - Execute the following command:
6.6
General Preparation 6.6.1 System Cleanup Single Platform Processor ONLY Refer to section [3] for details on how to carry out the procedures. System Files and Directories Ensure that the following free space is available on each machine before beginning the point release upgrade. / (root) 20% /usr/omc 20% /usr/omc/ne_data 30% Execute the following script as user root to perform the initial cleanup on the Single Platform Processor. This script will guide the user through some basic system cleanup. As a group of files are identified for deletion, the user is prompted for confirmation. It is NOT the intention of this script to ensure that sufficient space is available on the system; it will only act as an aid to system cleanup. In the case where files are not deleted, it is the responsibility of the user to ensure sufficient space is made available to comply with the guidelines detailed above.
/var/install/upgrade/scripts/system_cleanup
/usr/omc/ne_data Files and Directories Ensure that 30% of /usr/omc/ne_data is free, so that there is sufficient space if statistics are to be preserved through the point release upgrade. Likely places to save space are: Old log files in /usr/omc/ne_data/cell_analysis/log (If COP tools are installed) Old unloaded stats in /usr/omc/ne_data/unload_stats (Older than 3-4 days) Old loads in /usr/omc/ne_data/dbroot Old databases in /usr/omc/ne_data/dbroot
(Check with Configuration Management personnel on databases that can be removed.) Some systems have several N-1 and N-2 BSS point loads. The old loads can be removed through load management on the OMC_R GUI. If a load is in use on a BSC or RXCDR, then GUI code prevents removal of the load.
6.6.2 X.25 Configuration Single Platform Processor ONLY If the system is configured as a high-end system, but without the extra physical links configured, the following lines must be added to the x25_config file in order to correspond to entries in the high-end STARTUP.LIST file. Using an editor of your choice, append the entries shown below to the end of the /usr/omc/config/global/x25_config using the appropriate unique x25 address. In general the following rule can be applied for the x25 addresses of the extra Uploader processes: For Uploader process 3 use the x25 address of Uploader process 1 and port number <a> For Uploader process 4 use the x25 address of Uploader process 2 and port number <b> NOTE: The addresses used below are for example purposes only, substitute with addresses already in the x25_config file:
8 x25_chan8 <a> 2020130001299 H - OMC_PU X25 128 2 50 9 x25_chan9 <b> 2020130001299 H - OMC_PU X25 128 2 50
6.7
Update /var/install/sc_conf.sh Task Description This task will ensure that the /var/install/sc_conf.sh file has a value set for the SWITCH_SPEED variable on platforms where a 254 NE license is in use. Pre-checks - Ensure that the task is completed as user root on the Single Platform Processor. - Verify that the number of NEs licensed is 254 by examining the value of the NE variable in the RTF license file /opt/omc/license_tools/license_file. Where fewer than 254 NEs are licensed, this step can be ignored. Task Steps - Complete the following command. Using a text editor of choice edit the following file: /var/install/sc_conf.sh If a CISCO router is in use, append the following entry to the end of the file:
SWITCH_SPEED=2Mbps
Or if any other router is in use, append the following entry to the end of the file:
SWITCH_SPEED=384Kbps
Save and exit the file.
6.8
Update CM Database Configuration Task Description After a major release upgrade from GSR8 to GSR9, the CM database is mis-configured and needs to be corrected by running a procedure documented in a customer bulletin. Task Steps Before attempting the cutover, ensure that the procedure described in section [8] is applied to the system.
7.0
Single Platform Processor - Point release upgrade Procedure Tasks

7.1 Point release upgrade Procedure Work Flow
Figure 1:
Single Platform Processor Point release upgrade Procedure
7.2
Patch Installation
Task Description Additional software patches need to be manually installed from the second GSR9 OMCR DVD. Pre-checks Ensure that the tasks are completed as user root on the Single Platform Processor. Task Steps Insert the second GSR9 OMCR DVD Additional OMC Software into the DVD drive. If the drive already contains a DVD, eject it using the following command:
eject cdrom
Enter the following command on a single line to install the patches from the DVD:
/cdrom/cdrom0/suninstall/bin/install_patches --patch_dir /cdrom/cdrom0/suninstall/Patches --patch_order /cdrom/cdrom0/suninstall/Patches/patch_order
10
# # /cdrom/cdrom0/suninstall/bin/install_patches --patch_dir /cdrom/cdrom0/suninstall/Patches --patch_order /cdrom/cdrom0/suninstall/Patches/patch_order Patches to be installed: 3 Now installing patches...please wait... Patches Patches Patches Patches installed: installed: installed: installed: 0/3 1/3 2/3 3/3 (0%) (33%) (66%) (100%)

Patch install started on Wed Jul 25 17:20:18 BST 2007 Installing 119059-20 Validating patches... Loading patches installed on the system... Done! Loading patches requested to install. Done! The following requested patches are already installed on the system Requested to install patch 119059-20 is already installed on the system. No patches to check dependency. Installing 121118-10 Validating patches... Loading patches installed on the system... Done! Loading patches requested to install. Done! The following requested patches are already installed on the system Requested to install patch 121118-10 is already installed on the system. No patches to check dependency. Installing 122660-07 Validating patches... Doc ID: OSS-GSR9-CUSTSUP-UG-004 Doc Version: 1.2
11
Loading patches installed on the system... Done! Loading patches requested to install. Done! The following requested patches are already installed on the system Requested to install patch 122660-07 is already installed on the system. No patches to check dependency. Patch install completed on Wed Jul 25 17:20:25 BST 2007
7.3
Tools and Adjunct Products
Task Description This section describes the tasks that need to be completed before performing the OMC Single Platform Processor upgrade for other tools and products connected to the OMC. In this section, actions are required for the NHA, NBI and COP tools. Pre-checks - Ensure that the tasks are completed as user root on the appropriate platform. Task Steps - An NHA stop is required before the OMC upgrade. Refer to section [4] for details of this procedure. - If COP is installed on the OMCR or any GUI Servers, then all of the cron jobs that are running on those systems must be stopped. Execute the following command on each system as root:
svcadm disable -t cron
If NBI is in use on this OMCR Single Platform Processor, the NBI connection to this OMCR must be disabled before the OMC upgrade. Refer to section [6] for details of this procedure.
7.4
Upgrade the Single Platform Processor
Task Description Upgrade the Single Platform Processor to GSR9 1.9.0.0.Y. The following list provides the steps taken by the point release upgrade (this is not an exhaustive list but points out the highlights of the point release upgrade): (R) Below indicates that a response is required during this step. 1. 2. 3. 4. Install GSR9 OMC Software Stop the OMC (R) [outage commences at this point] Shell for pre-cutover workarounds (R) Cutover to GSR9 load (R)
12
5. Shell for post-cutover workarounds (R) 6. Start the OMC 7. Start cron For more details, refer to Appendix A.1 for typical script outputs. Pre-checks - Ensure that the GSR9 1.9.0.0.Y OMC Software and Jumpstart DVD is in the media drive in the Single Platform Processor. - Ensure that the task is completed as user root on the Single Platform Processor. Task Steps - Execute the following commands as user root:
touch /tmp/cutover_workarounds /usr/omc/sbin/swtool
The following Menus are displayed. Make the selections as per the example provided:
----------------------------------------------------------------------------------Software tool 1. 2. 3. 4. Display software inventory Manage releases Manage test objects Quit
Your Choice: 2 -----------------------------------------------------------------------------------OMC Releases 1. Install a release 2. Remove a release 3. Done Your Choice: 1 ----------------------------------------------------------------------------------Install Release 1. 2. 3. 4. Install OMC Release and Cutover Machine Install OMC Release Only Cutover Done
Your Choice: 1 -----------------------------------------------------------------------------------
The cron will now be stopped, the new release will be installed and the OMC stopped. Run the pre-cutover workarounds as per Task 7.5. When the cutover menu appears, select the release being upgraded to. After the cutover is complete, you will be prompted for the post-cutover workarounds as per Task 7.6. When the OMC restarts, select Menu option 3 followed by 4 to exit the swtool.
13
7.5
Pre-cutover procedures
Note: All of these tasks should be completed when the Pre-Cutover-Workarounds> prompt appears before cutover during the completion of Task 7.4. Task Description This section will describe tasks that need to be completed during the point release upgrade of the OMC Single Platform Processor, for open issues related to the OMC. Pre-checks - Ensure that the tasks are completed on the Single Platform Processor. Task Steps Execute the following commands as user root:
mkdir p /omcgen/1900.X_backup_files cp /usr/omc/config/global/CustomWorksheet.as \ /omcgen/1900.X_backup_files/CustomWorksheet.as
Execute the following command as user root:

cp /usr/omc/config/global/RC.CNFG \ /omcgen/1900.X_backup_files/RC.CNFG

chown sys:sys /var/adm/sa/sa*

cp /cdrom/cdrom0/s0/suninstall/platform_files/usertool.conf \ /var/install/data/usertool.conf

chmod 777 /var/install/logs
If there is an OSI Processor connected to the OMC-R, then execute the following command as user root:
cp /usr/omc/config/global/ACCESS.CNFG \ /omcgen/1900.X_backup_files/ACCESS.CNFG
7.6
Execute the following command as user root.

exit
Post-cutover procedures
Note: All of these tasks should be completed when the Post-Cutover-Workarounds> prompt appears after the cutover during the completion of Task 7.4. Task Description This section will describe tasks that need to be completed during the OMC Single Platform Processor point release upgrade, for open issues related to the OMC.
14
Pre-checks - Ensure that the tasks are completed on the Single Platform Processor. Task Steps As user omcadmin append this line to the following files /usr/omc/config/global/env/pmProcConfig.csh and /usr/omc/config/global/env/mibProcConfig.csh:
unsetenv STATE_ON_AUDIT

cp /omcgen/1900.X_backup_files/CustomWorksheet.as \ /usr/omc/config/global/CustomWorksheet.as
Execute the following commands as user root:

rm -rf /tmp/pyOmcOsp99.watch unshareall shareall
If there is an OSI processor connected to the OMC-R please complete the steps outlined in Appendix C, then execute the following command as user root:
cp /omcgen/1900.X_backup_files/ACCESS.CNFG \ /usr/omc/config/global/ACCESS.CNFG

Check the values of environment variables in /usr/omc/config/global/RC.CNFG. If any previously customized values noted in section 7.5 (and saved in the backup file /omcgen/1900.X_backup_files/RC.CNFG) have been reset to default values, complete the following as user omcadmin: Edit /usr/omc/config/global/RC.CNFG and modify any environment variables, which had customized values in the backup file. Save and exit the file.

exit
When the OMC restarts, select Menu option 3 followed by 4 to exit the swtool.
15
7.7
Examine Point release upgrade Logfiles
Task Description To examine the contents of the point release upgrade log files to ensure any errors captured in the log files are analyzed. Pre-checks Ensure that the task is completed as user root on the Single Platform Processor.
Task Steps Examine the contents of the following log file. If any errors exist in the log file, contact the relevant support organisation.
/usr/omc/logs/cutover.log
7.8
Mandatory PM Database Tasks
ENSURE THAT THESE TASKS ARE COMPLETED AFTER THE OMC IS STARTED. 7.8.1 Update statistics within the PM database
Task Description Update statistics within the PM database. Pre-checks Ensure that the tasks are completed as user omcadmin on the Single Platform Processor.
Task Steps Execute the following command.

7.8.2
Complete a PM Resync
Task Description Complete a PM Resync through the OMC-R GUI. Pre-checks Ensure that the tasks are completed as user omcadmin on the Single Platform Processor.
Task Steps Execute the following instructions. Start up an OMC-R GUI session
Once a GUI session is started successfully, a PMResync should be performed. Note: If the PM Resync appears to fail, then repeat the PM Resync task. 7.8.3 PM_HOURLY_STATS variable
Task Description To examine the setting of the PM_HOURLY_STATS variable. Pre-checks Ensure that the tasks are completed as user omcadmin on the Single Platform Processor.
Task Steps Check the latest parser file, for example, fpomcaudit* in /usr/omc/logs/. Check if the following message appears after the OMC has restarted: "Invalid Duration, which will result in a .bad_header file." If this message does not appear in the fpomcaudit* log, then skip to Section 7.8.5 If this message appears, then set the PM_HOURLY_STATS variable to either ON or OFF in the OMC.CNFG file. This change can take place without the requirement of an OMC stop/start using following this procedure:
Edit the OMC.CNFG file using a suitable editor. Un-comment the setting for PM_HOURLY_STATS and alter the environment variable so it looks like one of the following: PM_HOURLY_STATS=ON OR PM_HOURLY_STATS=OFF
Save and exit the file. Now execute the following command
This workaround will only temporarily set the value of PM_HOURLY_STATS. If an omc stop and start is performed on the system this change will be overwritten. To make the change a permanent one set the value of the variable in /usr/omc/config/global/env/pmProcConfig.csh 7.8.4 PM parsing of .bad_header Files
Task Description To rename and parse any .bad_header files which exist in the BSS directories.
17
Pre-checks Ensure that the task is completed as user root on the Single Platform Processor.
Task Steps Execute the following command:

In the event of a file not parsing correctly, the extension .bad_header will automatically be re-added to the file. Check the current /usr/omc/logs/fpomcaudit log for more details.
7.8.5
omc_db_maint cron
Task Description Ensure that a new fragment exists in the PM database. Pre-checks Ensure that the task is completed as user root on the Single Platform Processor.
Task Steps If the upgrade does not complete by 4:02am the default time for the omc_db_maint cron to execute OR if the upgrade does not complete before the customer configured start time for the omc_db_maint cron to run, then execute the following script:
Check the omc_db_maint logfile in /usr/omc/logs, to ensure the script has completed successfully.
7.9
Task Description This section will describe tasks that need to be completed after the OMC Single Platform Processor point release upgrade for other tools and products connected to the OMC. In this section, actions are required for the NHA, NBI, OMC utilities and COP tools. Pre-checks - Ensure that the tasks are completed as user root on the appropriate platform. Task Steps - If you have an NHA, run the script nha_omc_upgrade on the NHA and then start the NHA. Refer to section [4] for details of this procedure. - If COP Tools are installed on this OMCR Single Platform Processor then refer to section [7] for relevant administration details.
18
If NBI is in use on this OMCR Single Platform Processor, then refer to section [6] for details of activities to be carried out to start NBI services. If OMC utilities are being used, then refer to section [3] for the installation procedure.
7.10
Turning off warning alarms in the main alarm window
Task Description The environment variable, MMI_DEFAULT_WARN_ON has been introduced. It is used for controlling, irrespective of the warning alarms displayed in the main alarm window along with other alarms. By default, it is set to 1, which means that it is enabled. This may result in a lot of warning alarms being displayed in the main alarm window along with other alarms. If this is not required, then the environment variable MMI_DEFAULT_WARN_ON should be set to 0 in the file mmiProcConfig.csh using the following procedure. Pre-checks Ensure that the task is completed as user omcadmin. Task Steps Edit the file /usr/omc/config/global/env/mmiProcConfig.csh Add the following line to the file
setenv MMI_DEFAULT_WARN_ON 0
Stop and restart all GUI sessions for the change to take effect. 7.11 Complete Filesystem Backup
Task Description To complete a full backup of file systems and databases after the point release upgrade is complete. Pre-checks Ensure that the task is completed as user root on the Single Platform Processor, unless the backup procedure specifies otherwise.
Task Steps A full backup of all the file systems on the different processors can now be performed. For details of the backup procedures, refer to section [3]. A level-0 archive of the omc_db and mib_db databases can also be performed at this stage.
19
8.0
Single Platform Processor - Rollback Procedure Tasks
This rollback procedure is in effect undoing the operations performed during the point release upgrade. 8.1 Tools and Adjunct Products
Task Description This section will describe tasks that need to be completed before the OMC Single Platform Processor rollback for other tools and products connected to the OMC. In this section, actions are required for the NHA, NBI and COP tools. Task Steps - If NBI is installed, refer to section [6] to stop the NBI before the OMC point release rollback. If COP is installed then all of the cron jobs that are running on any of the servers that are connected to the Single Platform Processor must be stopped. Execute the following command on those systems:
svcadm disable -t cron
8.2
You will need to do an NHA stop before the OMC rollback. Refer to section [4] for details.
Roll Back Procedure
Task Description - Roll the system back to its previous GSR9 OMC Release.
(R) Below indicates that a response is required during this step. 1. 2. 3. 4. 5. 6. Cleanup any setup remaining from the previous point release upgrade Stop the OMC (R) Shell for pre-cutover procedures (R) Cutover to previous release Shell for post-cutover procedures (R) Restart the OMC
For more details, reference Appendix A.1 for typical script outputs. Pre-checks - Ensure that the task is completed as user root on the Single Platform Processor.
20
Task Steps - Execute the following commands as user root selecting the indicated options:
The following Menus are displayed. Make the selections as per the provided example:
Your Choice: 3 -----------------------------------------------------------------------------------
The OMC and cron will now be stopped. Run the pre-cutover workarounds as per Task 8.3. Select the previous 1.9.0.0.X release to rollback. After the cutover has completed you will be prompted for the post-cutover workarounds as per Task 8.4 now. When the OMC has restarted you should select Menu option 3 followed by 4 to exit the swtool.
8.3 Pre-cutover procedures Note: All of these tasks should be completed when the Pre-Cutover-Workarounds> prompt appears during the completion of Task 8.2. Task Description This section will describe tasks that need to be completed during the OMC Single Platform Processor rollback for open issues related to the OMC. Pre-checks - Ensure that the tasks are completed on the Single Platform Processor.
21
Task Steps - Execute the following command as user root:

exit
8.4
Post-cutover procedures
Note: All of these tasks should be completed when the Post-Cutover-Workarounds> prompt appears after the cutover during the completion of Task 8.2. Task Description This section will describe tasks that need to be completed during the OMC Single Platform Processor rollback for open issues related to the OMC. Pre-checks - Ensure that the tasks are completed on the Single Platform Processor. Task Steps - Execute the following command as user root :
unshareall shareall
If there is an OSI processor connected to the OMC-R please complete the steps outlined in Appendix C, then execute the following command as user root:
cp /omcgen/1900.X_backup_files/ACCESS.CNFG \ /usr/omc/config/global/ACCESS.CNFG
8.5

exit
When the OMC has restarted you should select Menu option 3 followed by 4 to exit the swtool.
Rollback logs
Task Description To examine the contents of the rollback log file to ensure any errors captured in the log files are analyzed. Pre-checks Ensure that the task is completed as user root on the Single Platform Processor.
Task Steps Examine the contents of the following log file. If any errors exist in this log file, contact the relevant support organization.
/usr/omc/logs/cutover.log
22
8.6
Task Description This section will describe tasks that need to be completed after the OMC Single Platform Processor rollback for other tools and products connected to the OMC. In this section, actions are required for the NHA, NBI and COP tools. Task Steps If you have an NHA, after you have completed the OMC rollback you will need to restart the NHA. Refer to section [4] for details of this procedure. If COP Tools are installed on this OMCR Single Platform Processor then refer to section [7] for relevant administration details. If NBI is in use on this OMCR Single Platform Processor then refer to section [6] for details of activities to be carried out to start NBI services.
23
9.0
GUI Server - Point release upgrade Procedure Tasks
9.1
GUI Server Point release upgrade Procedure Work Flow
Figure 2:
GUI Server Point release upgrade Procedure
9.2
Reboot the GUI Server
Task Description As part of the overall upgrade procedure, the Single Platform Processor has been rebooted. The GUI Server will need to be rebooted in order to eliminate any Stale NFS file handles which may exist. Pre-checks - Ensure that the task is completed as user root on the GUI Server. Task Steps
/usr/sbin/shutdown -i6 -g0 -y
9.3
Patch Installation
Task Description Additional software patches need to be manually installed from the second GSR9 OMCR DVD. Pre-checks Ensure that the tasks are completed as user root on the GUI Server.
24
Task Steps Insert the second GSR9 OMCR DVD Additional OMC Software into the GUI server DVD drive. If the drive already contains a DVD, eject it using the following command:
eject cdrom
Enter the following command on a single line to install the patches from the DVD:
/cdrom/cdrom0/suninstall/bin/install_patches --patch_dir /cdrom/cdrom0/suninstall/Patches --patch_order /cdrom/cdrom0/suninstall/Patches/patch_order
# /cdrom/cdrom0/suninstall/bin/install_patches --patch_dir /cdrom/cdrom0/suninstall/Patches --patch_order /cdrom/cdrom0/suninstall/Patches/patch_order Patches to be installed: 3 Now installing patches...please wait... Patches Patches Patches Patches installed: installed: installed: installed: 0/3 1/3 2/3 3/3 (0%) (33%) (66%) (100%)

Patch install started on Wed Jul 25 17:20:18 BST 2007 Installing 119059-20 Validating patches... Loading patches installed on the system... Done! Loading patches requested to install. Done! The following requested patches are already installed on the system Requested to install patch 119059-20 is already installed on the system. No patches to check dependency. Installing 121118-10 Validating patches... Loading patches installed on the system... Doc ID: OSS-GSR9-CUSTSUP-UG-004 Doc Version: 1.2
25
Done! Loading patches requested to install. Done! The following requested patches are already installed on the system Requested to install patch 121118-10 is already installed on the system. No patches to check dependency. Installing 122660-07 Validating patches... Loading patches installed on the system... Done! Loading patches requested to install. Done! The following requested patches are already installed on the system Requested to install patch 122660-07 is already installed on the system. No patches to check dependency. Patch install completed on Wed Jul 25 17:20:25 BST 2007
9.4
Upgrade the GUI Server
Task Description Upgrade the GUI Server to OMCR load GSR9 1.9.0.0.Y. The following list provides the steps taken by the upgrade script (this is not an exhaustive list but points out the highlights of the point release upgrade): (R) Below indicates that a response is required during this step. 1. 2. 3. 4. Install GSR9 OMC Software. Shell for pre-cutover workarounds (R) Cutover to GSR9 load (R) Shell for post-cutover workarounds (R)
For more details, reference Appendix A.2 for typical script outputs. Pre-checks - Ensure that the GSR9 1.9.0.0.Y OMC-R Media is in the GUI Server drive. - Ensure that the task is completed as user root on the GUI Server.
26
Task Steps - Execute the following command as user root:

Your Choice: 1 -----------------------------------------------------------------------------------
9.5
Run the pre-cutover workarounds as per Task 9.5. After the cutover has completed you will be prompted for the post-cutover workarounds as per Task 9.6. When the Cutover has completed you should select Menu option 3 followed by 4 to exit the swtool.
Pre-cutover workarounds
Note: All of these tasks should be completed when the Pre-Cutover-Workarounds> prompt appears during the completion of Task 9.4. Task Description This section will describe tasks that need to be completed during the GUI Server point release upgrade. Pre-checks - Ensure that the tasks are completed on the GUI Server.
27
Task Steps Execute the following command as user root:

exit
9.6
Post-cutover workarounds
Note: All of these tasks should be completed when the Post-Cutover-Workarounds> prompt appears after the cutover during the completion of Task 9.4. Task Description This section will describe tasks that need to be completed during the GUI Server point release upgrade. Pre-checks - Ensure that the tasks are completed as the specified user on the GUI Server. Task Steps 9.7 Execute the following command as user root:
rm -rf /tmp/pyOmcOsp99.watch


exit
When the Cutover is complete, select Menu option 3 followed by 4 to exit the swtool.
Examine Point release upgrade Logfiles
Task Description To examine the contents of the point release upgrade logfiles to ensure any errors captured in the log files are analyzed. Pre-checks -
Ensure that the task is completed as user root on the GUI Server.
Task Steps - Examine the contents of the following log files: /usr/omc/logs/cutover.log Any errors noted from the log files need to be investigated before proceeding with the remainder of the point release upgrade. Where necessary the appropriate support organization should be contacted.
28
9.8
Complete Filesystem Backup
Task Description To complete a full backup of the GUI Server file systems after the point release upgrade has completed. Pre-checks - Ensure that the task is completed as user root on the GUI Server, unless the backup procedure specifies otherwise. Task Steps - A full backup of all the file systems on the GUI Server can now be performed. Refer to section [3] for details of the backup procedures.
29
10.0 GUI Server - Rollback Procedure Tasks

This rollback procedure is in effect undoing the operations performed during the point release upgrade. 10.1 Rollback Procedure
Task Description To roll the system back to previous release. (R) Below indicates that a response is required during this step. 1. Cleanup any setup remaining from the previous point release upgrade 2. Cutover to previous GSR9 load Refer Appendix A.2 for typical script output. Pre-checks - Ensure that the task is completed as user root on the GUI Server. Steps Execute the following command as user root selecting the indicated options:
/usr/omc/sbin/swtool
Your Choice: 2 -----------------------------------------------------------------------------------OMC Releases 1. Install a release 2. Remove a release 3. Done Your Choice: 1 -----------------------------------------------------------------------------------
30

Install Release 1. 2. 3. 4. Install OMC Release and Cutover Machine Install OMC Release Only Cutover Done
Your Choice: 3 -----------------------------------------------------------------------------------
Select the previous 1.9.0.0.X release to rollback.
When the Cutover is complete, select Menu option 3 followed by 4 to exit the swtool.
31
A. Point Release Upgrade Typical Script Output for Single Platform Processor and GUI Server (all platforms)
This appendix contains example script output for the single platform processor and the GUI server. A.1 Output for OMC-R point release upgrade
Note: Output supplied is for a SF4900 showing a cutover from 1900.24 to 1900.27 release. Output for other platforms may vary slightly.
# touch /tmp/cutover_workarounds # /usr/omc/sbin/swtool Motorola Software Tool 1. 2. 3. 4. Display software inventory Manage releases Manage test objects Quit
Your Choice: 2 OMC Releases 1. Install a release 2. Remove a release 3. Main menu Your Choice: 1 Install Release 1. 2. 3. 4. Install OMC Software Release and Cutover Machine Install OMC Software Release Only Cutover Release menu
Your Choice: 2 Install release from which directory? [/cdrom/cdrom0/s0/suninstall/Packages] OMC Releases 1. Install a release 2. Remove a release 3. Main menu Your Choice: Invalid choice Your Choice: 1 Install Release 1. 2. 3. 4. Install OMC Software Release and Cutover Machine Install OMC Software Release Only Cutover Release menu
Your Choice: 3 Doc ID: OSS-GSR9-CUSTSUP-UG-004 Doc Version: 1.2
32
2007, Motorola General Business Use Stopping Cron Cron has stopped successfully. Sun Microsystems Inc. You have new mail. Stopping the OMC... SunOS 5.10 Generic January 2005
Apply Pre-Cutover-Workarounds Now and type exit when completed Pre-Cutover-Workarounds> exit ================================================================= OMC Generic Cutover ================================================================= There are 3 OMC releases available. 1. 2. 3. 4. OMC Release 1.8.0.0.54 OMC Release 1.9.0.0.24 <<-- CURRENT OMC Release 1.9.0.0.27 QUIT - do nothing
Enter Choice: 3 About to cutover to OMC Release 1.9.0.0.27 Are you sure (Type Yes to confirm) ? Yes Cutting over to release 1.9.0.0.27... Relinking /usr/omc/current... Done Configuring file permissions... Done Creating startup files... Done Configuring SMF permissions... Done INFO: Checking for an existing database. INFO: Deleting PM Violations tables... INFO: Done Updating PM environment files... Done Configuring Country/Network code... Done Copying release specific scripts... Done Cleaning up sec files... Done INFO: Checking PM DB configuration... INFO: Chunk /dev/omc_db_root already exists - continuing... INFO: Chunk /dev/omc_db_logs already exists - continuing... INFO: Chunk /dev/omc_db_logs already exists - continuing... INFO: Chunk /dev/omc_db1 already exists - continuing... INFO: Chunk /dev/omc_db2 already exists - continuing... INFO: Chunk /dev/omc_db3 already exists - continuing... INFO: Chunk /dev/omc_db4 already exists - continuing... INFO: Chunk /dev/omc_db5 already exists - continuing... INFO: Chunk /dev/omc_db6 already exists - continuing... INFO: Chunk /dev/omc_db7 already exists - continuing... INFO: Chunk /dev/omc_db8 already exists - continuing... INFO: Chunk /dev/omc_db9 already exists - continuing... INFO: Chunk /dev/omc_db10 already exists - continuing... INFO: Chunk /dev/omc_db11 already exists - continuing... INFO: Chunk /dev/omc_db12 already exists - continuing... INFO: Chunk /dev/omc_db_temp already exists - continuing... INFO: Done INFO: Checking for PM database changes... INFO: Done INFO: Shutting down Informix Instance INFO: Updating the onconfig file Doc ID: OSS-GSR9-CUSTSUP-UG-004 Doc Version: 1.2 33
2007, Motorola General Business Use INFO: Starting Informix instance INFO: Informix instance started successfully INFO: Stopping and dropping _vio and _dia tables Database 'omc_db' - Logging status updated. Program over. INFO: Checking for required files... INFO: Required file check complete. INFO: Checking schema_version... INFO: Starting database modifications... INFO: Upgrading to system version: 1.9.0.0.27 INFO: Checking for required files... INFO: Required file check complete. INFO: Generating table lists INFO: Creating lists of schema tables INFO: Searching for tables added in this release INFO: Searching for tables deleted from this release INFO: Searching for tables not on static list INFO: Table list generation completed. INFO: Checking subscriptions unl files... INFO: Checking subscriptions tables... INFO: Creating new tables... INFO: No new tables in target release. INFO: Dropping tables not present in this release... INFO: No tables to be deleted in target release. INFO: Checking all tables are fully updated... INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: Creating columns lists for subscriptions. Searching for columns to delete from subscriptions. Searching for new columns to add to subscriptions. Checking the data type of columns in table subscriptions. Checking the extent sizes & placement of table subscriptions. Table update for subscriptions complete. Creating columns lists for subscription_list. Searching for columns to delete from subscription_list. Searching for new columns to add to subscription_list. Checking the data type of columns in table subscription_list. Checking the extent sizes & placement of table subscription_list. Table update for subscription_list complete. Creating columns lists for bss_datetimes. Searching for columns to delete from bss_datetimes. Searching for new columns to add to bss_datetimes. Checking the data type of columns in table bss_datetimes. Checking the extent sizes & placement of table bss_datetimes. Table update for bss_datetimes complete. Creating columns lists for mtl_statistics. Searching for columns to delete from mtl_statistics. Searching for new columns to add to mtl_statistics. Checking the data type of columns in table mtl_statistics. Checking the extent sizes & placement of table mtl_statistics. Table update for mtl_statistics complete. 34
INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO:
Creating columns lists for oml_statistics. Searching for columns to delete from oml_statistics. Searching for new columns to add to oml_statistics. Checking the data type of columns in table oml_statistics. Checking the extent sizes & placement of table oml_statistics. Table update for oml_statistics complete. Creating columns lists for cbl_statistics. Searching for columns to delete from cbl_statistics. Searching for new columns to add to cbl_statistics. Checking the data type of columns in table cbl_statistics. Checking the extent sizes & placement of table cbl_statistics. Table update for cbl_statistics complete. Creating columns lists for rsl_statistics. Searching for columns to delete from rsl_statistics. Searching for new columns to add to rsl_statistics. Checking the data type of columns in table rsl_statistics. Checking the extent sizes & placement of table rsl_statistics. Table update for rsl_statistics complete. Creating columns lists for gsl_statistics. Searching for columns to delete from gsl_statistics. Searching for new columns to add to gsl_statistics. Checking the data type of columns in table gsl_statistics. Checking the extent sizes & placement of table gsl_statistics. Table update for gsl_statistics complete. Creating columns lists for xbl_statistics. Searching for columns to delete from xbl_statistics. Searching for new columns to add to xbl_statistics. Checking the data type of columns in table xbl_statistics. Checking the extent sizes & placement of table xbl_statistics. Table update for xbl_statistics complete.
INFO: Creating columns lists for gproc_statistics. INFO: Searching for columns to delete from gproc_statistics. INFO: Searching for new columns to add to gproc_statistics. INFO: Checking the data type of columns in table gproc_statistics. INFO: Checking the extent sizes & placement of table gproc_statistics. INFO: Extent & placement check indicates table gproc_statistics INFO: must be moved or resized... INFO: Unloading original table gproc_statistics... ERROR: error unloading gproc_statistics. INFO: Dropping original gproc_statistics Database selected.
Table dropped.
Database closed.
Database selected. Doc ID: OSS-GSR9-CUSTSUP-UG-004 Doc Version: 1.2
35
Table created.
Index created.
Index created.
Permission revoked.
Permission granted.
Database closed. INFO: Successfully recreated gproc_statistics table INFO: Reloading data into gproc_statistics... ERROR: error loading gproc_statistics. INFO: Extent & placement resize for gproc_statistics complete. INFO: Table update for gproc_statistics complete. INFO: Creating columns lists for dproc_statistics. INFO: Searching for columns to delete from dproc_statistics. INFO: Searching for new columns to add to dproc_statistics. INFO: Checking the data type of columns in table dproc_statistics. INFO: Checking the extent sizes & placement of table dproc_statistics. INFO: Extent & placement check indicates table dproc_statistics INFO: must be moved or resized... INFO: Unloading original table dproc_statistics... ERROR: error unloading dproc_statistics. INFO: Dropping original dproc_statistics Database selected.
Table dropped.
Database closed.
Database selected.
Table created.
Index created.
Index created.
Permission revoked. Doc ID: OSS-GSR9-CUSTSUP-UG-004 Doc Version: 1.2
36
Permission granted.
Database closed. INFO: Successfully recreated dproc_statistics table INFO: Reloading data into dproc_statistics... ERROR: error loading dproc_statistics. INFO: Extent & placement resize for dproc_statistics complete. INFO: Table update for dproc_statistics complete. INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: Creating columns lists for psp_statistics. Searching for columns to delete from psp_statistics. Searching for new columns to add to psp_statistics. Checking the data type of columns in table psp_statistics. Checking the extent sizes & placement of table psp_statistics. Table update for psp_statistics complete. Creating columns lists for carrier_statistics. Searching for columns to delete from carrier_statistics. Searching for new columns to add to carrier_statistics. Altering table carrier_statistics - add(rf_losses_tch_sig7
integer)
Database selected.
Table altered.
Database closed. INFO: Altering table carrier_statistics - add(rf_losses_tch_sig6 Database selected. integer)
Table altered.
Table altered.
Table altered. Doc ID: OSS-GSR9-CUSTSUP-UG-004 Doc Version: 1.2
37
Table altered.
Table altered.
Table altered.
Table altered.
Database closed. INFO: Checking the data type of columns in table carrier_statistics. INFO: Checking the extent sizes & placement of table carrier_statistics. INFO: Table update for carrier_statistics complete. INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: Creating columns lists for nbr_statistics. Searching for columns to delete from nbr_statistics. Searching for new columns to add to nbr_statistics. Checking the data type of columns in table nbr_statistics. Checking the extent sizes & placement of table nbr_statistics. Table update for nbr_statistics complete. Creating columns lists for carrier_statistic2. Searching for columns to delete from carrier_statistic2. Searching for new columns to add to carrier_statistic2. Checking the data type of columns in table carrier_statistic2. Checking the extent sizes & placement of table carrier_statistic2. 38
2007, Motorola General Business Use INFO: Table update for carrier_statistic2 complete. INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: Creating columns lists for carrier_statistic3. Searching for columns to delete from carrier_statistic3. Searching for new columns to add to carrier_statistic3. Checking the data type of columns in table carrier_statistic3. Checking the extent sizes & placement of table carrier_statistic3. Table update for carrier_statistic3 complete. Creating columns lists for vgcs_statistics. Searching for columns to delete from vgcs_statistics. Searching for new columns to add to vgcs_statistics. Checking the data type of columns in table vgcs_statistics. Checking the extent sizes & placement of table vgcs_statistics. Table update for vgcs_statistics complete.
INFO: Creating columns lists for eth_statistics. INFO: Searching for columns to delete from eth_statistics. INFO: Searching for new columns to add to eth_statistics. INFO: Checking the data type of columns in table eth_statistics. INFO: Checking the extent sizes & placement of table eth_statistics. INFO: Extent & placement check indicates table eth_statistics INFO: must be moved or resized... INFO: Unloading original table eth_statistics... ERROR: error unloading eth_statistics. INFO: Dropping original eth_statistics Database selected.
Table dropped.
Database closed.
Database selected.
Table created.
Index created.
Index created.
Permission revoked.
Permission granted.
Database closed. INFO: Successfully recreated eth_statistics table INFO: Reloading data into eth_statistics... Doc ID: OSS-GSR9-CUSTSUP-UG-004 Doc Version: 1.2 39
2007, Motorola General Business Use ERROR: error loading eth_statistics. INFO: Extent & placement resize for eth_statistics complete. INFO: Table update for eth_statistics complete. INFO: Creating columns lists for pproc_statistics. INFO: Searching for columns to delete from pproc_statistics. INFO: Searching for new columns to add to pproc_statistics. INFO: Checking the data type of columns in table pproc_statistics. INFO: Checking the extent sizes & placement of table pproc_statistics. INFO: Extent & placement check indicates table pproc_statistics INFO: must be moved or resized... INFO: Unloading original table pproc_statistics... ERROR: error unloading pproc_statistics. INFO: Dropping original pproc_statistics Database selected.
Table dropped.
Database closed.
Database selected.
Table created.
Index created.
Index created.
Permission revoked.
Permission granted.
Database closed. INFO: Successfully recreated pproc_statistics table INFO: Reloading data into pproc_statistics... ERROR: error loading pproc_statistics. INFO: Extent & placement resize for pproc_statistics complete. INFO: Table update for pproc_statistics complete. INFO: INFO: INFO: INFO: INFO: INFO: Creating columns lists for entity. Searching for columns to delete from entity. Searching for new columns to add to entity. Checking the data type of columns in table entity. Checking the extent sizes & placement of table entity. Table update for entity complete.
INFO: Creating columns lists for nbr_entity. Doc ID: OSS-GSR9-CUSTSUP-UG-004 Doc Version: 1.2 40
2007, Motorola General Business Use INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: Searching for columns to delete from nbr_entity. Searching for new columns to add to nbr_entity. Checking the data type of columns in table nbr_entity. Checking the extent sizes & placement of table nbr_entity. Table update for nbr_entity complete. Creating columns lists for schema_version. Searching for columns to delete from schema_version. Searching for new columns to add to schema_version. Checking the data type of columns in table schema_version. Checking the extent sizes & placement of table schema_version. Table update for schema_version complete. Creating columns lists for network_classes. Searching for columns to delete from network_classes. Searching for new columns to add to network_classes. Checking the data type of columns in table network_classes. Checking the extent sizes & placement of table network_classes. Table update for network_classes complete. Creating columns lists for statistic_types. Searching for columns to delete from statistic_types. Searching for new columns to add to statistic_types. Checking the data type of columns in table statistic_types. Checking the extent sizes & placement of table statistic_types. Table update for statistic_types complete. Creating columns lists for statistic_groups. Searching for columns to delete from statistic_groups. Searching for new columns to add to statistic_groups. Checking the data type of columns in table statistic_groups. Checking the extent sizes & placement of table statistic_groups. Table update for statistic_groups complete. Creating columns lists for statistic_columns. Searching for columns to delete from statistic_columns. Searching for new columns to add to statistic_columns. Checking the data type of columns in table statistic_columns. Checking the extent sizes & placement of table statistic_columns. Table update for statistic_columns complete. Creating columns lists for pm_statistics. Searching for columns to delete from pm_statistics. Searching for new columns to add to pm_statistics. Checking the data type of columns in table pm_statistics. Checking the extent sizes & placement of table pm_statistics. Table update for pm_statistics complete. Creating columns lists for custom_statistics. Searching for columns to delete from custom_statistics. Searching for new columns to add to custom_statistics. Checking the data type of columns in table custom_statistics. Checking the extent sizes & placement of table custom_statistics. Table update for custom_statistics complete. Creating columns lists for stored_selections. Searching for columns to delete from stored_selections. Searching for new columns to add to stored_selections. Checking the data type of columns in table stored_selections. 41
2007, Motorola General Business Use INFO: Checking the extent sizes & placement of table stored_selections. INFO: Table update for stored_selections complete. INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: Creating columns lists for device_selection. Searching for columns to delete from device_selection. Searching for new columns to add to device_selection. Checking the data type of columns in table device_selection. Checking the extent sizes & placement of table device_selection. Table update for device_selection complete. Creating columns lists for reset_site_table. Searching for columns to delete from reset_site_table. Searching for new columns to add to reset_site_table. Checking the data type of columns in table reset_site_table. Checking the extent sizes & placement of table reset_site_table. Table update for reset_site_table complete. Creating columns lists for stat_selection. Searching for columns to delete from stat_selection. Searching for new columns to add to stat_selection. Checking the data type of columns in table stat_selection. Checking the extent sizes & placement of table stat_selection. Table update for stat_selection complete. Creating columns lists for pm_info. Searching for columns to delete from pm_info. Searching for new columns to add to pm_info. Checking the data type of columns in table pm_info. Checking the extent sizes & placement of table pm_info. Table update for pm_info complete. Creating columns lists for cell_statistics. Searching for columns to delete from cell_statistics. Searching for new columns to add to cell_statistics. Altering table cell_statistics - add(rf_los_tch_sig integer)
Database selected.
Table altered.
Database closed. INFO: Altering table cell_statistics - add(chanrqfailhr_rol Database selected. integer)
Table altered.
Database closed. INFO: Altering table cell_statistics - add(chanrqfailfr_rol Database selected. integer)
42
2007, Motorola General Business Use Table altered.
Database closed. INFO: Altering table cell_statistics - add(alloc_tch_sig Database selected. integer)
Table altered.
Database closed. INFO: Checking the data type of columns in table cell_statistics. INFO: Checking the extent sizes & placement of table cell_statistics. INFO: Table update for cell_statistics complete. INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: Creating columns lists for dynetgp_statistics. Searching for columns to delete from dynetgp_statistics. Searching for new columns to add to dynetgp_statistics. Checking the data type of columns in table dynetgp_statistics. Checking the extent sizes & placement of table dynetgp_statistics. Table update for dynetgp_statistics complete. Creating columns lists for gbl_statistics. Searching for columns to delete from gbl_statistics. Searching for new columns to add to gbl_statistics. Checking the data type of columns in table gbl_statistics. Checking the extent sizes & placement of table gbl_statistics. Table update for gbl_statistics complete. Creating columns lists for bss_statistics. Searching for columns to delete from bss_statistics. Searching for new columns to add to bss_statistics. Checking the data type of columns in table bss_statistics. Checking the extent sizes & placement of table bss_statistics. Table update for bss_statistics complete. Creating columns lists for axcdr_statistics. Searching for columns to delete from axcdr_statistics. Searching for new columns to add to axcdr_statistics. Checking the data type of columns in table axcdr_statistics. Checking the extent sizes & placement of table axcdr_statistics. Table update for axcdr_statistics complete. Creating columns lists for lmtl_statistics. Searching for columns to delete from lmtl_statistics. Searching for new columns to add to lmtl_statistics. Checking the data type of columns in table lmtl_statistics. Checking the extent sizes & placement of table lmtl_statistics. Table update for lmtl_statistics complete. Creating columns lists for carrier_statistic4. Searching for columns to delete from carrier_statistic4. Searching for new columns to add to carrier_statistic4. Checking the data type of columns in table carrier_statistic4. Checking the extent sizes & placement of table carrier_statistic4. 43
2007, Motorola General Business Use INFO: Table update for carrier_statistic4 complete. INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: INFO: Creating columns lists for nbr_status. Searching for columns to delete from nbr_status. Searching for new columns to add to nbr_status. Checking the data type of columns in table nbr_status. Checking the extent sizes & placement of table nbr_status. Table update for nbr_status complete. Creating columns lists for pcu_statistics. Searching for columns to delete from pcu_statistics. Searching for new columns to add to pcu_statistics. Checking the data type of columns in table pcu_statistics. Checking the extent sizes & placement of table pcu_statistics. Table update for pcu_statistics complete. Creating columns lists for pm_fragments. Searching for columns to delete from pm_fragments. Searching for new columns to add to pm_fragments. Checking the data type of columns in table pm_fragments. Checking the extent sizes & placement of table pm_fragments. Table update for pm_fragments complete. Creating columns lists for lockfiles. Searching for columns to delete from lockfiles. Searching for new columns to add to lockfiles. Checking the data type of columns in table lockfiles. Checking the extent sizes & placement of table lockfiles. Table update for lockfiles complete. Creating columns lists for pm_data_storage. Searching for columns to delete from pm_data_storage. Searching for new columns to add to pm_data_storage. Checking the data type of columns in table pm_data_storage. Checking the extent sizes & placement of table pm_data_storage. Table update for pm_data_storage complete.
INFO: Deleting Motorola static data for static list tables. INFO: Deleting Motorola static data for table subscription_list. INFO: Deleting old static data for table subscription_list Database selected.
18 row(s) deleted.
Database closed. INFO: Deleting Motorola static data for table subscriptions. INFO: Deleting old static data for table subscriptions Database selected.
102 row(s) deleted.
44
Database closed. INFO: Deleting Motorola static data for table stat_selection. INFO: Deleting old static data for table stat_selection Database selected.
16 row(s) deleted.
Database closed. INFO: Deleting Motorola static data for table stored_selections. INFO: Deleting old static data for table stored_selections Database selected.
4 row(s) deleted.
Database closed. INFO: Deleting Motorola static data for table custom_statistics. INFO: Deleting old static data for table custom_statistics Database selected.
21 row(s) deleted.
Database closed. INFO: Deleting Motorola static data for table statistic_types. INFO: Deleting old static data for table statistic_types Database selected.
6 row(s) deleted.
Database closed. INFO: Deleting Motorola static data for table statistic_groups. INFO: Deleting old static data for table statistic_groups Database selected.
7 row(s) deleted. Doc ID: OSS-GSR9-CUSTSUP-UG-004 Doc Version: 1.2
45
Database closed. INFO: Deleting Motorola static data for table statistic_columns. INFO: Deleting old static data for table statistic_columns Database selected.
3 row(s) deleted.
Database closed. INFO: Deleting Motorola static data for table pm_statistics. INFO: Deleting old static data for table pm_statistics Database selected.
3011 row(s) deleted.
Database closed. INFO: Deleting Motorola static data for table schema_version. INFO: Deleting old static data for table schema_version Database selected.
1 row(s) deleted.
Database closed. INFO: Deleting Motorola static data for table network_classes. INFO: Deleting old static data for table network_classes Database selected.
55 row(s) deleted.
Database closed. INFO: Deleting Motorola static data for table lockfiles. INFO: Deleting old static data for table lockfiles Database selected.
1 row(s) deleted. Doc ID: OSS-GSR9-CUSTSUP-UG-004 Doc Version: 1.2 46
Database closed. INFO: Loading Motorola static data for fixed list tables. Database selected.
1 row(s) loaded.
18 row(s) loaded.
102 row(s) loaded.
55 row(s) loaded.
6 row(s) loaded.
7 row(s) loaded.
3 row(s) loaded.
2985 row(s) loaded.
4 row(s) loaded.
16 row(s) loaded.
21 row(s) loaded.
1 row(s) loaded.
Database closed. INFO: Load of Motorola static data complete. INFO: Dropping old views.
Database selected.
40 row(s) retrieved.
47
2007, Motorola General Business Use Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped.
48
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped. Doc ID: OSS-GSR9-CUSTSUP-UG-004 Doc Version: 1.2
49
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped. Doc ID: OSS-GSR9-CUSTSUP-UG-004 Doc Version: 1.2 50
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
51
2007, Motorola General Business Use View dropped.
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped.
Database closed.
Database selected. Doc ID: OSS-GSR9-CUSTSUP-UG-004 Doc Version: 1.2
52
View dropped.
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped.
Database closed.
Database selected.
View dropped.
Database closed. INFO: Creating new views.
Database selected.
View created.
View created.
53
2007, Motorola General Business Use View created.
View created.
View created.
View created.
View created.
View created.
View created.
View created.
View created.
View created.
View created.
View created.
View created.
View created.
View created.
View created.
View created.
View created.
View created.
View created. Doc ID: OSS-GSR9-CUSTSUP-UG-004 Doc Version: 1.2
54
View created.
View created.
View created.
View created.
View created.
View created.
View created.
View created.
View created.
View created.
View created.
View created.
View created.
View created.
View created.
View created.
View created.
View created.
Permission granted.
Permission granted. Doc ID: OSS-GSR9-CUSTSUP-UG-004 Doc Version: 1.2 55
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
56
2007, Motorola General Business Use Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted.
Permission granted. Doc ID: OSS-GSR9-CUSTSUP-UG-004 Doc Version: 1.2
57
Database closed. INFO: Starting to update indexes INFO: Completed updating indexes INFO: The current state of the database omc_db is... Connecting to database omc_db Table Name (Number): systables (0x00100071): syscolumns (0x00100072): sysindices (0x00100073): systabauth (0x00100074): syscolauth (0x00100075): sysviews (0x00100076): sysusers (0x00100077): sysdepend (0x00100078): syssynonyms (0x00100079): syssyntable (0x0010007a): sysconstraints (0x0010007b): sysreferences (0x0010007c): syschecks (0x0010007d): sysdefaults (0x0010007e): syscoldepend (0x0010007f): sysprocedures (0x00100080): sysprocbody (0x00100081): sysprocplan (0x00100082): sysprocauth (0x00100083): sysblobs (0x00100084): sysopclstr (0x00100085): systriggers (0x00100086): systrigbody (0x00100087): sysdistrib (0x00100088): sysfragments (0x00100089): sysobjstate (0x0010009d): sysviolations (0x0010009e): sysfragauth (0x0010008a): sysroleauth (0x0010009c): sysxtdtypes (0x0010008b): sysattrtypes (0x0010008d): sysxtddesc (0x0010008c): sysinherits (0x0010008e): syscolattribs (0x0010008f): syslogmap (0x00100090): syscasts (0x00100091): sysxtdtypeauth (0x00100092): sysroutinelangs (0x00100099): syslangauth (0x0010009a): sysams (0x00100093): systabamdata (0x00100094): sysopclasses (0x00100095): syserrors (0x00100096): systraceclasses (0x00100097): systracemsgs (0x00100098): sysaggregates (0x0010009b): syssequences (0x0010009f): sysdirectives (0x001000a0): sysxasourcetypes (0x001000a1): sysxadatasources (0x001000a2): Doc ID: OSS-GSR9-CUSTSUP-UG-004 Doc Version: 1.2
Pages 24 208 48 40 8 24 8 8 8 8 32 8 8 8 16 64 208 40 32 8 8 8 8 32 360 32 8 8 8 8 8 8 8 8 8 24 8 8 8 8 8 8 8 8 8 8 8 8 8 8
Used 18 208 43 37 4 22 3 4 3 3 27 3 2 7 11 60 205 37 27 3 3 4 2 32 360 27 5 3 3 6 4 2 3 2 3 21 3 3 4 4 2 4 2 3 3 3 3 3 3 3
Free Extent DataPg 6 3 10 0 10 81 5 4 31 3 4 8 4 1 1 2 3 14 5 1 1 4 1 1 5 1 0 5 1 0 5 4 12 5 1 0 6 1 0 1 1 5 5 2 2 4 8 46 3 14 184 3 5 18 5 4 9 5 1 1 5 1 0 4 1 0 6 1 0 0 2 28 0 13 143 5 4 9 3 1 0 5 1 0 5 1 0 2 1 1 4 1 0 6 1 0 5 1 0 6 1 0 5 1 0 3 1 13 5 1 0 5 1 1 4 1 1 4 1 1 6 1 0 4 1 1 6 1 0 5 1 0 5 1 0 5 1 0 5 1 0 5 1 0 5 1 0 5 1 0
#Rows 141 3586 177 179 17 370 3 102 0 0 203 0 0 33 203 238 1283 120 223 6 0 0 0 163 836 288 0 0 0 17 0 0 0 0 0 280 0 5 4 4 0 2 0 0 0 0 0 0 0 0 58
2007, Motorola General Business Use subscriptions subscription_list bss_datetimes mtl_statistics oml_statistics cbl_statistics rsl_statistics gsl_statistics xbl_statistics psp_statistics carrier_statistics nbr_statistics carrier_statistic2 carrier_statistic3 vgcs_statistics entity nbr_entity schema_version network_classes statistic_types statistic_groups statistic_columns pm_statistics custom_statistics stored_selections device_selection reset_site_table stat_selection pm_info cell_statistics dynetgp_statistics gbl_statistics bss_statistics axcdr_statistics lmtl_statistics carrier_statistic4 nbr_status pcu_statistics pm_fragments lockfiles pm_data_storage pm_load_log gproc_statistics dproc_statistics eth_statistics pproc_statistics INFO: The database (0x00f00002): 256 (0x00f00006): 4 (0x00f00009): 4 (0x00000000): 102912 (0x00000000): 3072 (0x00000000): 32256 (0x00000000): 46080 (0x00000000): 7680 (0x00000000): 32256 (0x00000000): 3072 (0x00000000): 3201024 (0x00000000): 960000 (0x00000000): 448512 (0x00000000): 321024 (0x00000000): 84480 (0x00f00035): 2560 (0x00f0003c): 320 (0x00f0003f): 4 (0x00f00041): 4 (0x00f00044): 4 (0x00f00047): 4 (0x00f0004a): 4 (0x00f0004d): 256 (0x00f00053): 10 (0x00f00059): 70 (0x00f0005b): 256 (0x00000000): 19968 (0x00f00060): 4 (0x00f00062): 4 (0x00000000): 5760000 (0x00000000): 13824 (0x00000000): 12288 (0x00000000): 4608 (0x00000000): 7680 (0x00000000): 96768 (0x00000000): 576000 (0x00f00077): 256 (0x00000000): 1536 (0x00f0007f): 4 (0x00f00080): 4 (0x00f00081): 4 (0x00f00084): 11 (0x00000000): 256512 (0x00000000): 58368 (0x00000000): 64512 (0x00000000): 58368 upgrade has finished. 5 251 2 2 2 2 12 102900 12 3060 12 32244 12 46068 12 7668 12 32244 12 3060 14 3201010 14 959986 14 448498 14 321010 12 84468 1 2559 1 319 2 2 2 2 2 2 2 2 2 2 145 111 2 8 2 68 1 255 12 19956 2 2 1 3 16 5759984 12 13812 12 12276 14 4594 12 7668 12 96756 14 575986 1 255 12 1524 2 2 2 2 2 2 1 10 12 256500 12 58356 12 64500 12 58356 1 1 1 12 12 12 12 12 12 12 12 12 12 12 12 1 1 1 1 1 1 1 1 1 1 1 12 1 1 12 12 12 12 12 12 12 1 12 1 1 1 1 12 12 12 12 4 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 143 1 1 0 0 1 0 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 0 102 18 96 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 55 6 7 3 2985 21 4 0 0 16 0 0 0 0 0 0 0 0 0 0 12 1 1 0 0 0 0 0
INFO: Database schema modifications completed. INFO: Updating High Performance Loader database. INFO: Removing vio_ and dia_ tables with S03PmVioStop INFO: Shutting down Informix Instance INFO: Starting Informix instance INFO: Informix instance started successfully Copying empty map file... Done Reconfiguring printer definition file... Done Copying FM configuration files... Done Configuring cronjobs for root... Done Configuring cronjobs for omcadmin... Done Doc ID: OSS-GSR9-CUSTSUP-UG-004 Doc Version: 1.2 59
2007, Motorola General Business Use INFO: Configuring PM Loader... INFO: Done Apply Post-Cutover-Workarounds Now and type exit when completed Post-Cutover-Workarounds> exit Disabling NBI Elements Starting OMC Sun Microsystems Inc. SunOS 5.10 You have new mail. Starting the OMC... OMC has successfully restarted. Starting Cron Cron has successfully restarted. OMC Releases 1. Install a release 2. Remove a release 3. Main menu Your Choice: 3 Press ENTER to return to the main menu... Motorola Software Tool 1. 2. 3. 4. Display software inventory Manage releases Manage test objects Quit
Generic January 2005
Your Choice: 4
A.2
Output for GUI Server point release upgrade
Note: Output supplied is for a Sunblade. Output for other platforms may vary slightly. # touch /tmp/cutover_workarounds # /usr/omc/sbin/swtool Motorola Software Tool 1. 2. 3. 4. Display software inventory Manage releases Manage test objects Quit
Your Choice: 2 OMC Releases 1. Install a release 2. Remove a release 3. Main menu Your Choice: 1 Install Release Doc ID: OSS-GSR9-CUSTSUP-UG-004 Doc Version: 1.2 60
1. 2. 3. 4.
Install OMC Software Release and Cutover Machine Install OMC Software Release Only Cutover Release menu
Your Choice: 1 Install release from which directory? [/cdrom/cdrom0/s0/suninstall/Packages] Oct 9 16:51:11 zuk14omc40 hsfs: NOTICE: hsfs: Warning: file system mounted on /cdrom/jumpstart_omcr.190027/s0 Oct Oct 9 16:51:11 zuk14omc40 does not conform to the ISO-9660 specification: 9 16:51:11 zuk14omc40 hsfs: file len greater than max allowed
Oct 9 16:51:11 zuk14omc40 hsfs: Due to this error, the file system may not be correctly interpreted. Oct 9 16:51:11 zuk14omc40 hsfs: Other such errors in this file system will be silently ignored. Software releases 1. 1900.27 2. None Install which release? 1 Processing package instance <MOTc190027> from </cdrom/jumpstart_omcr.190027/s0/suninstall/Packages/MOTc1900x> Motorola GSM OMC-R 1.9.0.0.27 GUI Software(sparc) 1.9.0.0.27 Motorola Using </usr/omc> as the package base directory. ## Processing package information. ## Processing system information. ## Verifying disk space requirements. Installing Motorola GSM OMC-R 1.9.0.0.27 GUI Software as <MOTc190027> ## Installing part 1 of 1. 826073 blocks Installation of <MOTc190027> was successful. Removal of <MOTc1900> was successful. Processing package instance <MOTc1900> from </cdrom/jumpstart_omcr.190027/s0/suninstall/Packages/MOTc1900> Motorola GSM OMC-R 1.9.0.0 GUI Software(sparc) 1.9.0.0.27 Motorola Using </usr/omc> as the package base directory. ## Processing package information. ## Processing system information. 7 package pathnames are already properly installed. ## Verifying disk space requirements. Doc ID: OSS-GSR9-CUSTSUP-UG-004 Doc Version: 1.2 61
Installing Motorola GSM OMC-R 1.9.0.0 GUI Software as <MOTc1900> ## Installing part 1 of 1. 1231 blocks Installation of <MOTc1900> was successful. Processing package instance <MOTh190027> from </cdrom/jumpstart_omcr.190027/s0/suninstall/Packages/MOTh1900x> Motorola GSM OMC-R 1900.27 Help files(sparc) 1900.27 Motorola Using </usr/omc/1.9.0.0.27/config/help> as the package base directory. ## Processing package information. ## Processing system information. ## Verifying disk space requirements. Installing Motorola GSM OMC-R 1900.27 Help files as <MOTh190027> ## Installing part 1 of 1. 103437 blocks Installation of <MOTh190027> was successful. Stopping Cron Cron has stopped successfully. Apply Pre-Cutover-Workarounds Now and type exit when completed Pre-Cutover-Workarounds> exit ================================================================= OMC Generic Cutover ================================================================= There are 2 OMC releases available. 1. 2. 3. OMC Release 1.9.0.0.24 <<-- CURRENT OMC Release 1.9.0.0.27 QUIT - do nothing
Enter Choice: 2 About to cutover to OMC Release 1.9.0.0.27 Are you sure (Type Yes to confirm) ? Yes Cutting over to release 1.9.0.0.27... Relinking /usr/omc/current... Done Configuring file permissions... Done Creating startup files... Done Configuring SMF permissions... Done Copying release specific scripts... Done Configuring cronjobs for root... cron may not be running - call your system administrator Done Configuring cronjobs for omcadmin... cron may not be running - call your system administrator Done Apply Post-Cutover-Workarounds Now and type exit when completed Doc ID: OSS-GSR9-CUSTSUP-UG-004 Doc Version: 1.2 62
2007, Motorola General Business Use Post-Cutover-Workarounds> rm -rf /tmp/pyOmcOsp99.watch Post-Cutover-Workarounds> /usr/omc/current/sbin/cde_install Reconfiguring CDE settings... Done Post-Cutover-Workarounds> exit Starting Cron Cron has successfully restarted. OMC Releases 1. Install a release 2. Remove a release 3. Main menu Your Choice: 3 Press ENTER to return to the main menu... Motorola Software Tool 1. 2. 3. 4. Display software inventory Manage releases Manage test objects Quit
Your Choice: 4 # cat /usr/omc/logs/cutover.log 17:09:57 (6): -> [1] Procedure Logfile /usr/omc/logs/cutover.log.20071009_17:09:57 started has been called 17:10:29 (15): About to cutover to OMC Release 1.9.0.0.27 17:10:29 (15): Are you sure (Type Yes to confirm) ? 17:10:32 (15): 17:10:32 (10): User chose Yes 17:10:32 (15): Cutting over to release 1.9.0.0.27... 17:10:32 (15): Relinking /usr/omc/current... 17:10:33 (15): Done 17:10:33 (10): Now executing /usr/omc/current/install_mmi/S01chgFileAttr... Configuring file permissions... Done 17:10:34 (10): Now executing /usr/omc/current/install_mmi/S02SetupServices... Creating startup files... Done Configuring SMF permissions... Done 17:10:35 (10): Now executing /usr/omc/current/install_mmi/S20sbinFileCopy... Copying release specific scripts... Done 17:10:36 (10): Now executing /usr/omc/current/install_mmi/S90cronjob_mmi... Configuring cronjobs for root... cron may not be running - call your system administrator Done Configuring cronjobs for omcadmin... cron may not be running - call your system administrator Done 17:10:37 (6): -> [2] Procedure Logfile /usr/omc/logs/cutover.log.20071009_17:09:57 completed has been called
63
B.
Using swtool to remove an old OMCR Software load

/usr/omc/sbin/swtool
Execute the following command as user root to remove an OMCR software load: The following Menus are displayed. Make the selections as per the example provided:
Motorola Software Tool 1. 2. 3. 4. Display software inventory Manage releases Manage test objects Quit
Your Choice: 2 OMC Releases 1. Install a release 2. Remove a release 3. Main menu Your Choice: 2 Software releases 1. 1900.24 2. 1900.27 3. None Remove which release? 1 Sun Microsystems Inc. SunOS 5.10 You have new mail.
Generic January 2005
Removal of <NBIGSMRMI190024> was successful. Removal of <MOTs190024> was successful. Removal of <MOTh190024> was successful. OMC Releases 1. Install a release 2. Remove a release 3. Main menu Your Choice: 3 Press ENTER to return to the main menu... Motorola Software Tool 1. 2. 3. 4. Display software inventory Manage releases Manage test objects Quit
Your Choice: 4
64
C.
OSI re-cutover after 1.9.0.0.X to 1.9.0.0.Y OMC-R Point release upgrade
Re-cutover OSI Processor This is a re-cutover of the current OSI release in order to update the OMC configuration files. The OSI applications are installed using scripts provided with the software loaded from delivery media. The main script is /usr/omc/sbin/cutover. It is used to select the OSI release to be installed from a possible choice of releases, and to execute the other installation scripts. Note: The OSI OMC interface feature is automatically installed during this cutover procedure. The Motorola IPC configuration file is automatically updated if necessary on the Single Platform Processor in order to allow the OSI OMC interface to communicate with the rest of the OSI application. To execute the cutover script, carry out the following steps: 1. Login to the OSI Processor as root:
Note: Do not use the command su. 2. As a result of the OMC-R cutover the NFS share for the directory /usr/omc/current/config/env on the OSI system is changed. This may result in the OSI not initialising correctly. Execute the following command as root on the OSI processor: Using a text editor, edit the /etc/vfstab file and locate the following line: omc_splat:/usr/omc/omc/<omc current version>/config/env /usr/omc/current/config/env nfs - yes bg Note: Although the above line appears on two lines it is actually a single line. Update the vfstab entry and replace <omc current version> with the version number that the OMC-R is being cutover to. For example: omc_splat:/usr/omc/1.9.0.0.24/config/env /usr/omc/current/config/env nfs - yes bg Becomes omc_splat:/usr/omc/1.9.0.0.27/config/env /usr/omc/current/config/env nfs - yes bg
65
Or in the case of a rollback: omc_splat:/usr/omc/1.9.0.0.27/config/env /usr/omc/current/config/env nfs - yes bg Becomes: omc_splat:/usr/omc/1.9.0.0.24/config/env /usr/omc/current/config/env nfs - yes bg
/usr/sbin/umount /usr/omc/current/config/env /usr/sbin/mount -a
3. Execute the following as user root to back up the following configuration files:
mkdir /usr/omc/ne_data/osi_backup cd /usr/omc/ne_data/osi_backup cp p /usr/omc/current/config/md_nma.cfg . cp p /usr/omc/current/config/md_mds.cfg . cp p /usr/omc/current/config/access.data .
4.
Type the following command:

/usr/omc/sbin/cutover
The cutover is logged to the file /usr/omc/logs/cutover.<$$> where <$$> is the process identifier number of the cutover execution. A menu, similar to that shown below, is displayed:
================================================================ OMC Generic Cutover ================================================================ There are 1 OMC releases available. 1. 2. OMC Release 1.9.0.0.X.MD Quit do nothing
Enter choice : 1
The letter X in the release name designates the subrelease of the MD software. 5. Select the OSI release to be installed, in this example enter 1. A confirmation message similar to that shown is displayed. If the release chosen is correct enter Yes for confirmation as follows:
About to cutover to OMC Release 1.9.0.0.X.MD Are you sure (Type Yes to confirm) ? Yes
The following example shows a sample output of the cutover script:
66
2007, Motorola General Business Use Cutting over to OMC Release 1.9.0.0.X.MD .... Relinking /usr/omc/current Executing /usr/omc/current/install/S01chgFileAttr ... ....... Executing /usr/omc/current/install/S02timesynch Executing /usr/omc/current/install/S10CDE_setup ... Creating alternate CDE configuration path... Copying new CDE configuration Executing /usr/omc/current/install/S20sbinFileCopy Executing /usr/omc/current/install/S30md_nma_cfgConfig Executing /usr/omc/current/install/S35PreserveUserParam Executing /usr/omc/current/install/S70Clean_alarm.data 6. If the SA option has not been chosen, go directly to step 8 else if SA has been chosen, the cutover script displays the following message: Executing /usr/omc/current/install/S75installSA Enter an MMI Processors hostname [q to quit} :
6. Enter successively all the MMI Processor hostnames and enter q to quit after the last hostname. At this point, the cutover script performs some checks:
Checking Updating Checking Updating Checking Updating ... /usr/omc/current/env/.cshrc (omc_mib) /usr/omc/current/env/.cshrc (omc_mib) /etc/dt/config/C/sys.dtwmrc (omc_mib) /etc/dt/config/C/sys.dtwmrc (omc_mib) /usr/omc/config/local/sessionetc (omc_mib) /usr/omc/config/local/sessionetc (omc_mib)
Note: The following output lines specifying pluto and motoper are only given as examples: Actual output depends on the user's defined on the OMC Single Platform Processor.
Executing /usr/omc/current/install/S76upgradeUsers Configuring SA for users in the CDE environment for each OMC user... Checking /home/pluto/.dt/sessions/sessionetc for pluto Updating /home/pluto/.dt/sessions/sessionetc for pluto Checking /home/pluto/.dt/dtwmrc for pluto Updating /home/pluto/.dt/dtwmrc for pluto Checking /home/motoper/.dt/sessions/sessionetc for motoper ...
67
7.
The cutover script displays the following output:

/usr/omc/current/install/S80ipc /usr/omc/current/install/S85installConfig /usr/omc/current/install/S87exportFiles /usr/omc/current/install/S89importFiles /usr/omc/current/install/S90cronjob_osi /usr/omc/current/install/S91cron_md /usr/omc/current/install/S91cron_md_mib /usr/omc/current/install/S91cron_opt_osi
Executing Executing Executing Executing Executing Executing Executing Executing Done.
8.
Restore the configuration files as user root

cd cp cp cp /usr/omc/current/config p /usr/omc/ne_data/osi_backup/md_nma.cfg . p /usr/omc/ne_data/osi_backup/md_mds.cfg . p /usr/omc/ne_data/osi_backup/access.data .
9.
Logout from the OSI Processor. Operations to be carried out before restarting the OMC The file STARTUP.LIST must be updated to include the lines that will automatically start the OSI applications (SA and MD). Logon to the Single Platform Processor as user root to update the STARTUP.LIST
10.
MD is without SA option
Edit the file /usr/omc/current/config/STARTUP.LIST with a suitable editor. Add the following line at the end of the file :
1 MD_SUP /usr/omc/current/bin/md_omc_start 19 0 60 1 omc_osi
Note: The numbers after the filenames should be continuous from the numbers in the rest of the file and should follow on from the number of the monitor (normally 18). If MD without SA skip to step 13. 11.
MD is with SA option
Edit the file /usr/omc/current/config/STARTUP.LIST with a suitable editor. Add the following lines at the end of the file three lines for SA, one line for MD (if the monitor process is not number 18, read the note first):
1 SEC_DISPATCHER /usr/omc/current/bin/sec_dispatcher 19 1 SEC_ATP /usr/omc/current/bin/sec_atp 20 0 1 SEC_SFC /usr/omc/current/bin/sec_sfc 21 0 1 SEC_REP /usr/omc/current/bin/sec_rep 22 0 1 MD_SUP /usr/omc/current/bin/md_omc_start 23 0 60 1 omc_osi 0 60 60 60 60 1 1 1 1 omc_osi omc_osi omc_osi omc_osi
Note: The numbers after the filenames should be continuous from the numbers in the rest of the file and should follow on from the number of the monitor (normally 18).
12.
Now return to the Post-cutover workaround section. Steps 14 onwards can be used to check the MD/SA have started after the upgrade/rollback is complete.
Checking that MD and SA have started To check that the Mediation Device and the Security Application have started, carry out the following steps: 13. 14. Login to the OSI Processor as user omcadmin. Please make sure that the OMC has been started. To check that the MD application has started, type the following command:
md_ps
The following output is displayed:

MD PROCESS MD Supervisor Event Reporter Operation Performer MAP Object Manager LOG Object Manager Agent Input Output Processor IOP Write Process CM Event Reporter NB 1 1 1 1 1 1 2 1 1 PID(s) [9759] [9763] [9764] [9768] [9769] [9767] [21321] [21322] [21325] [21332]
where the numbers shown in the PID(s) column may vary. Note: When the NB column displays the value 0 (zero), the corresponding process is not running.
15. If MD without SA skip to step 17. MD is with SA option
16.
To check that the SA application has started, enter the following command:
sa_ps
The following is displayed:

SA PROCESS SA SA SA SA dispatcher authentication security control security reporter NB 1 1 1 1 PID(s) [14063] [14145] [13840] [14526]
where the values shown in the PIDs column may vary. Note: When the NB column displays the value 0 (zero), the corresponding process is not running. 17. Logout from the OSI Processor.
69
D.
What to do if swtool fails to install your new packages
Swtool uses pkgrm to remove the previous version of your software before using pkgadd to install the new version. In the case where swtool fails, you may be left with a system that has no software load. The following instructions detail how to install packages manually. To check the state of the installed package on the Single Platform Processor use the following command as user root
pkginfo l MOTs1900
If the output does not contain the status completely installed then we need to remove the package and re-install it. To remove a package use the following command as user root
pkgrm MOTs1900
To re-install the package install a working DVD and run the following command as user root
pkgadd d /cdrom/cdrom0/s0/suninstall/Packages/MOTs1900 all
For the Gui Server the same commands can be applied to the package MOTc1900
70
Standard Printing Instructions

Part Number Manual Title 68P02901W74-S Software Release Notes: OMC-R System
A5 Wire Bound (Word/PDF) - GSD (UK) Binder Printing None Cover / spine text printed in colour. Body- printed double sided onto white A5 size (148.5mm x 210mm) 80g paper. Photo-reduce to A5. Manuals containing multiple documents within the same cover require a pale yellow divider sheet to separate individual documents. The most common example being release notes containing additional upgrade guides A5 size (148.5mm x 210mm) clear PVC sheet front page for protection. Punched with 24 x 2mm holes or 16 x 3mm holes depending on thickness of manual and sealed with blue wire mechanism. Bag wrapped with clear polythene.
Finishing
If this is to be used by manufacturing as an Inbox document, then refer to appropriate Materials or Methods Specification.
OMC-R System
Software Release Notes
Including: GSM OMC-R 1.9.0.0 Upgrade/Migration Guide GSM OMC-R 1.9.0.0.X to 1.9.0.0.Y Point Release Upgrade Guide
1.9.0.0.29
68P02901W74-S
GSR9

Upgrade Guide For 1.9.0.0.29

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Upgrade Guide For 1.9.0.0.29

Uploaded by

Copyright:

Available Formats

Software Release Notes: OMC-R System

1994 - 2008 Motorola, Inc. All Rights Reserved

High Risk Materials

Chapter 1 About this release ................................................................................... 1-1

68P02901W74-S Mar 2008

Chapter 2 Open issues..............................................................................................2-1

Chapter 3 Resolved issues ....................................................................................... 3-1

Chapter 4 Compatibility ........................................................................................... 4-1

68P02901W74-S Mar 2008

Chapter 5 Hardware and firmware requirements .....................................................5-1

Chapter 6 Software management .............................................................................6-1

Chapter 7 MMI changes............................................................................................7-1

68P02901W74-S Mar 2008

About This Manual

Software Release Notes: OMC-R System

68P02901W74-S Mar 2008

Resolution of Service Requests

Incorporation of Change Notices

68P02901W74-S Mar 2008

Special key sequences

Questions and comments

68P02901W74-S Mar 2008

Warnings, cautions, and notes

Warnings, cautions, and notes

68P02901W74-S Mar 2008

Caring for the environment

Caring for the environment

Disposal of Motorola equipment

Disposal of surplus packaging

68P02901W74-S Mar 2008

CMM labeling and disclosure table

CMM labeling and disclosure table

Motorola document set

Motorola document set

Ordering documents and CD-ROMs

Document banner definitions

68P02901W74-S Mar 2008

Third Party computer software and trademarks

Third Party computer software and trademarks

Chapter 1 About this release

68P02901W74-S Mar 2008

General information about the release notes

Chapter 1: About this release

General information about the release notes

Information on OMC Utilities can be found in the Online Help.

Nomenclature, release load identification

Software Release Notes: OMC-R System

68P02901W74-S Mar 2008

New features in 1.9.0.0.29

Chapter 1: About this release

New features in 1.9.0.0.29

Table 1-1 New features in OMC-R 1.9.0.0.29 release

New features in OMC-R

Table 1-2 New features in OMC-R

Software Release Notes: OMC-R System

New features in 1.9.0.0.29

68P02901W74-S Mar 2008

New statistics in 1.9.0.0.29

Chapter 1: About this release

New statistics in 1.9.0.0.29

Software Release Notes: OMC-R System

New statistics in 1.9.0.0.29

UL_RLC_STALLED_BLKS_MCS_2 UL_RLC_STALLED_BLKS_MCS_3 UL_RLC_STALLED_BLKS_MCS_4 UL_RLC_STALLED_BLKS_MCS_5 UL_RLC_STALLED_BLKS_MCS_6 UL_RLC_STALLED_BLKS_MCS_7 UL_RLC_STALLED_BLKS_MCS_8 UL_RLC_STALLED_BLKS_MCS_9