550-00206 Version 4.1 System Upgrade 1

SONUS TECHNICAL PUBLICATION
SONUS Systems
System Software
Upgrade Guide
to Version 4.01
Sonus Part Number: 550-00206

Document Version: 1.0
Software Version: V04.01.00
Copyright
Copyright © 1999 - 2002 Sonus Networks, Inc. All rights reserved. Printed in the U.S.A.
This publication may be used, copied, or distributed only in accordance with the terms of the license agreement. Any other use,
reproduction or distribution may occur only upon Sonus’ prior written consent.
Disclaimer and Restrictions

The material in this publication is for information only and is subject to change without notice. This material does not constitute a
commitment on the part of Sonus Networks, Inc. This material is provided “AS IS,” with all faults, and without any warranties
whatsoever, express or implied, including, but not limited, warranties of merchantability, performance, or fitness for a particular
purpose. While reasonable efforts have been made in the preparation of this publication to assure its accuracy, Sonus Networks,
Inc. assumes no liability resulting from technical or editorial errors or omissions, or for any damages whatsoever (including, but not
limited to, incidental, special or consequential damages) resulting from the furnishing, performance, or use of the information
contained herein. Sonus Networks, Inc. reserves the right to revise this publication, and to make changes on the content hereof
without notice.
The information in this document may be used by customers solely for the use and understanding of Sonus Networks’ products and
solutions. This document is not meant to define an interface between Sonus products and any third party hardware or software.
Sonus reserves the right to change the design and implementation used for any of the tables, screens, field names, etc. to enhance
its products as it sees fit.
Trademarks
Sonus, Open Services Architecture, Insignus, SMARRT, Sonus Insight, and GSX9000 are trademarks of Sonus Networks, Inc. —
Open Services Partner Alliance and SonusCARE are service marks of Sonus Networks, Inc.
The Sonus Networks, Inc. trademarks may not be used in connection with any product or service that is not Sonus Networks’ in any
manner that is likely to cause confusion among customers or in any manner that disparages or discredits Sonus Networks, Inc.
Third-Party Trademarks
Apache is the http server, and Tomcat is the Servlet/JSP container developed by the Apache Software Foundation. — Rapid
Service Introduction (RSI) System is a trademark of BayPackets, Inc. — Borland is a registered trademark, and AppServer is a
trademark of Borland Software Corporation. — Dot Hill and SANnet are trademarks of Dot Hill Systems Corp. — IBM and
WebSphere are registered trademarks of IBM Corp. — Intel and Pentium are registered trademarks of Intel Corporation. —
Macromedia is a registered trademark, and JRun is a trademark of Macromedia, Inc. in the U.S. and/or other countries. —
MERANT is a trademark of MERANT Inc. — DataDirect is a registered trademark of DataDirect Technologies. — Micromuse and
Netcool are registered trademarks of Micromuse Ltd. in the United States and/or other countries. — Microsoft, Microsoft Internet
Explorer logo, Windows, Windows NT, and/or other Microsoft products referenced herein are either registered trademarks or
trademarks of Microsoft Corporation in the U.S. and/or other countries. — Netscape is a registered trademark of Netscape
Communications Corporation in the U.S. and other countries. — Nokia is a registered trademark of Nokia Corporation. — Oracle is
a registered trademark of Oracle Corporation. — Palm OS and Palm Powered are registered trademarks, and Palm is a trademark
of Palm, Inc. — Riverstone Networks is a trademark of Riverstone Networks, Inc. — Sage Instruments is a copyright of Sage
Instruments, Inc. — SnowShore, SnowShore Networks, and N20 are trademarks of SnowShore Networks, Inc. — SSH is an IETF
protocol and OpenSSH is a derivative of the original and free ssh 1.2.12 release by Tatu Ylonen. SSH Secure Shell is a trademark
of SSH Communications Security, Ind. — Sun, Sun Microsystems, Java, Netra, Solaris, Solstice DiskSuite, and all trademarks that
contain Sun, Solaris, or Java are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the United
States and other countries. — iPlanet is a division of Sun Microsystems, Inc. — All SPARC trademarks are used under license and
are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC
trademarks are based upon an architecture developed by Sun Microsystems, Inc. — Telcordia and LERG are trademarks of
Telcordia Technologies, Inc., an SAIC company. — Signalware is a registered trademark of Ulticom, Inc. — UNIX is a registered
trademark in the United States and other countries, exclusively licensed through X/Open Company, Ltd. — VeriSign is a registered
trademark, and Thawte Consulting is a wholly owned subsidiary of VeriSign, Inc. — VERITAS Volume Manager and VERITAS
Volume Replicator are trademarks of VERITAS Software Corporation. — WebLogic is a registered trademark of BEA Systems, Inc.
All other product names mentioned herein are trademarks of their respective owners.
FCC Compliance
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC
Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in
a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used
in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in
a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at the
user’s own expense.
TABLE OF CONTENTS
Chapter 1 Introduction
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Document Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Technical Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Technical Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Upgrade Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
System Software Upgrade Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Required Upgrade Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Upgrade a Solaris 2.6 Operating System to Solaris 8 . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Verify your Solaris OS System Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Upgrading the Solaris OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Necessary Solaris OS Patches and Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Solaris 8 Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Solaris 2.6 Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Disabling Daemons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Java Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Removing Previous JRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Installing the new JRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Sonus Products and Solaris LOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Chapter 2 Insight EMS Software Upgrade
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Hardware - Small Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Hardware - Large Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Installing Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
System Software Upgrade Guide - 550-00206 - 1.0 iii
© 2002 Sonus Networks, Inc. Confidential and Proprietary. All Rights Reserved. Do not distribute without permission.
Pre-Oracle Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Oracle Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Post-Oracle Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Upgrading an Existing Sonus Insight Database Instance . . . . . . . . . . . . . . . . . . . . . . 2-13
Manually Starting and Stopping the Intelligent Oracle Agent . . . . . . . . . . . . . . . . . . . . 2-18
Upgrading Sonus Insight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Scenario 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Scenario 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Scenario 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
Scenario 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
Creating the Database Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
Starting and Stopping the Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35
SSL Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
Upgrading the SSL Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
Configuring Sonus Insight V04.01.00 for SSL Support . . . . . . . . . . . . . . . . . . . . . 2-40
Installing OPENssh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41
Installing OPENssh 3.1p1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42
Enabling SSH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42
Synchronizing with the NTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
Installation Notes for NFS Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44
Initial Netcool Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
Starting Netcool Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
Starting the Sonus Insight Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47
Configuring the Primary and Standby Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48
Initializing and Starting the Standby Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49
Creating a Minimal Insight Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
Changing Default Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-51
Configuring Multiple User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-53
Solaris Freeware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54
Online Documentation Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55
Uninstalling Sonus Insight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56
Clearing Client Browser Cache After a Software Upgrade . . . . . . . . . . . . . . . . . . . . . 2-57
Internet Explorer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
Netscape Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
iv System Software Upgrade Guide - 550-00206 - 1.0
Chapter 3 PSX Software Upgrade
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
PSX Upgrade Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Prerequisites for the PSX Software Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Reconfiguring GSX Primary and Secondary PSXs . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Synchronize the Databases between Master and Replica PSX systems . . . . . . . . 3-6
Updating the PSX Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
PSX Software Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Upgrading the Database on the Master PSX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Update/Migrate the Master Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Update/Migrate the Slave (Replica) Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Upgrading the PSX Manager Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
PSX Database Upgrade and Numbering Plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Process Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Chapter 4 SGX SS7 Gateway Software Upgrade
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Chapter 5 GSX9000 Software Upgrade
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
GSX9000 Software Upgrade Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Firmware Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
GSX9000 Product Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
NFS Server Upgrade Solaris 2.6 to 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
GSX9000 Software Upgrade Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Installing the Software to the GSX System Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Installing New Firmware on Each Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Loading GSX9000 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Loading GSX9000 Software by Booting the System . . . . . . . . . . . . . . . . . . . . . . . 5-11
Loading GSX9000 Software with Live Software Upgrade . . . . . . . . . . . . . . . . . . . 5-12
Restoring the Previously Installed Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
System Software Upgrade Guide - 550-00206 - 1.0 v
Chapter 6 Upgrade Existing DataStream Integrator Software
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Preconditions for DataStream Integrator Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Rollback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
vi System Software Upgrade Guide - 550-00206 - 1.0
CHAPTER 1 Introduction
Overview
This chapter contains introductory information for the System Software Upgrade procedures
detailed in the following chapters of this guide.
This is the contents provided in the Introduction:
• "About this Document" on page 1-2

• "Contacts" on page 1-3
• "Upgrade Components" on page 1-4
• "Upgrade a Solaris 2.6 Operating System to Solaris 8" on page 1-6
• "Necessary Solaris OS Patches and Actions" on page 1-11
• "Disabling Daemons" on page 1-13
• "Java Runtime Environment" on page 1-14
• "Sonus Products and Solaris LOM" on page 1-15
System Software Upgrade Guide - 550-00206 - 1.0 1-1

Introduction About this Document
About this Document
Audience
This document is intended for the following audience:
• Customer Operation Teams

• Sonus Support
Document Purpose
This document is intended to provide detailed instructions on upgrade and other necessary
procedures to migrate existing Sonus products to a new software load.
Document Conventions
This document uses the following admonition conventions:
This is a Note or Attention indicator for additional information.
This is a Caution indicator, indicating the possibility of data loss or

corruption if instructions are not followed accurately.
This is a Warning indicator, indicating physical danger to the operator of

the equipment if directions are not followed accurately.
1-2 System Software Upgrade Guide - 550-00206 - 1.0
Contacts Introduction
Contacts
Technical Support
For problems or questions, contact the Sonus Technical Assistence Center (TAC).
TABLE 1-1. Sonus TAC contact information

Telephone (USA) +1 (888) 391-3434
International +1 (978) 589-8589
Facsimile +1 (978) 589-8320
Email support@sonusnet.com
The TAC is available 24 hours a day, 7 days a week.
Technical Publications
If you have questions or comments about this document, please address your feedback
• via e-mail to support@sonusnet.com or
• by mail to:
Sonus Networks, Inc.

Attn. Technical Publishing
5 Carlisle Road
Westford, MA 01886
USA
Introduction Upgrade Components
Upgrade Components
The following component upgrades are addressed in this document:
TABLE 1-2. Upgrade Components and Versions
Previous Software Upgraded

Element Version Software Version
Insight Element Management System V03.02.1 or higher V04.01.00
PSX Policy Server V03.02.1 or higher V04.01.00
SGX SS7 Gateway Any V6.02.2+SP6+S6H
GSX9000 Open Services Switch V03.02.1 or higher V04.01.00
Firmware:
V01.07.00R000
DSI - DataStream Integrator V3.3 or higher V04.01.00
System Software Upgrade Sequence
Use the following sequence to perform a system software upgrade:

1. Upgrade the Insight Element Management System server software.
2. Upgrade the PSX software. The PSX software is always compatible with the previous version
and new version of the GSX9000 software.
3. Upgrade the SGX software, please refer to the following document for further instructions:
• SGX SS7 Gateway Introduction and Installation Guide, as delivered on your
documentation CD. Also refer to the Sonus’ FTP site for downloads of the latest version of
the SGX documentation.
4. Upgrade the GSX9000 software.
5. Upgrade the DSI software.
Upgrade Components Introduction
Required Upgrade Materials
To perform a system software upgrade, you need the following materials:
• Telnet access to the management network

• Insight Software V04.01.00 CD
• PSX Policy Server System Software V04.01.00 CD
• SGX SS7 Gateway Software V6.02.2+SP6+S68 CD
• GSX9000 Open Service Switch System Software V04.01.00 CD
• DSI - DataStream Integrator V04.01.00 CD
Introduction Upgrade a Solaris 2.6 Operating System to Solaris 8
Upgrade a Solaris 2.6 Operating System to Solaris 8
When you are upgrading your System Software, make sure the right Solaris OS is applied. Please
refer to the following table for information on Sonus release versions and necessary Solaris OS
changes:
TABLE 1-3. Necessary Solaris OS Upgrades
Product The Solaris OS Upgrade to version 8 is necessary, if

Insight EMS you plan to upgrade from a version prior to V03.04.
PSX Policy Server you plan to upgrade from a version prior to V04.00.
NFS Server you plan to upgrade the GSX from a version prior to V04.00.
No Solaris OS Upgrade necessary

SGX SS7 Gateway Remains on Solaris OS 2.6.
Verify your Solaris OS System Version
Please verify that your dedicated product host has the right OS version installed.
1. At the command prompt type:

hostname> uname -rs
2. A response of
SunOS 5.8
hostname>
indicates your host is running Solaris 8. Where as SunOS 5.6 in the response indicates your
host is running Solaris 2.6.
Upgrade a Solaris 2.6 Operating System to Solaris 8 Introduction
Upgrading the Solaris OS
See the Sun Microsystems Solaris documentation for complete installation instructions. The
following information is a supplement to the Solaris installation instructions as documented in the
Solaris Installation Manual. All information regarding settings and selections in this procedure
might vary from settings and selections necessary for your location and system.
Before beginning the upgrade to Solaris 8, verify that you have a

minimum of 800 MB of free space in your root partition. Failure to have
adequate space available will result in either your manually halting the
installation process to free the necessary space, or your allowing Solaris
to backup and re-partition the drive, which could add several hours to
the upgrade process.
Procedure
Follow the procedure below to update your Solaris Operating System from version 2.6 to 8.
Upgrading the Solaris OS from version 2.6 to 8 (2.8):
Step Action
1. Obtain the following system information:
• Host name and IP address of the Primary Network Interface (PNI) of the system,
which can be obtained with the following command:
# /bin/grep loghost /etc/hosts
That command should return an output containing a line similar to this:
10.9.9.103 eee3 loghost
The host name in this case is eee3 and the IP address of the PNI is 10.9.9.103.
• Subnet mask of the system, which can be obtained with the following command:
# /bin/cat /etc/netmasks
That command should return a line similar to this:
10.0.0.0 255.255.0.0
The netmask value in this case is 255.255.0.0.
2. Place the Solaris installation CD into your CD drive.
3. If the system is currently booted, stop the operating system and go into firmware. To
do so type:
# init 0
The machine initializes and acknowledges with ok prompt.
Step Action
4. At the ok> prompt type:
ok> boot cdrom
The machine reboots using the CD drive for the boot sequence.
5. After displaying a number of status messages, you are asked to select a language. At
the prompt:
Select a language
For example, choose 0, for English.
6. Next you may be asked to
Select a Locale
For example, choose 0 from the options.
7. The next prompt is:
What type of terminal are you using?
Choose 3, for DEC VT100 (recommended).
8. The next set of prompts are used to identify the system. Continue by either pressing
the F2 control key or the keys ESC+2.
a. If the system is networked, confirm the setting, else change it for your specific
needs. It is mandatory that the system is networked.
b. Select No for DHCP setting.
c. If you have multiple network interfaces, you are queried for the Primary Network
Interface (PNI). Select 0 (hme) for PNI.
d. Type in the Hostname for your system.
e. Specify the IP Address for your system.
f. Select y/Y (yes) to specify that the system is part of a Subnet.
g. Specify the Netmask for your system.
h. Select No for IPv6 setting.
Confirm your settings.
9. Select No at the Configure Kerberose Security prompt. Confirm your setting.
10. Select the appropriate naming service and follow any additional prompts. If you select
None at the prompt it is possible to configure the naming service later. Confirm your
setting.
11. The next prompt asks you to specify your Time Zone by Region. Specify this
depending on your location. For example:
• for Region select United States,
• for Time Zone select Eastern.
The next prompt shows the system time based on the previous specifications.
Change the Date/Time if necessary.
Confirm your settings.
Upgrade a Solaris 2.6 Operating System to Solaris 8 Introduction
Step Action
12. The system identification sequence is now completed. The OS installation program
starts.
13. The next prompt asks you to select between F2_Upgrade and F4_Initial. Choose the
option for Upgrade.
14. The next prompt asks for profile information. Select your geographic region. The
system shows default settings. As a minimum, you must select the U.S.A.
(en_US.ISO8859-1) option under North America as shown below.
V [/] North America
[ ] Canada-English (ISO8859-1)
[ ] Canada-French (ISO8859-1)
[ ] French
[X] U.S.A. (en_US.ISO8859-1)
Change the other selections depending on your needs.
15. The systems enters an analysis sequence and may prompt you to customize the
software. Accept the 64-bit support as offered.
16. The upgrade process starts. Depending on your system performance and
specification the upgrade process might take 1 to 2 hours.
17. Once the upgrade is complete, you need to check for errors in the log files. Go to the
following file location:
/var/sadm/system/logs/upgrade_log
Scroll through the log file line by line and scan if there are any ERROR entries.
18. Next examine the upgrade_cleanup file. Go to the following file location:
/var/sadm/system/data/upgrade_cleanup
19. Also check the files begin_log and finish_log.
20. After addressing any errors discovered in the log files or if there were no errors, you
must reboot the system by entering
# init 0
21. At the ok> prompt type:
0> boot
22. The machine resets and enters a configuration sequence. The next prompt asks if you
want to configure a security policy. Select No. Confirm your settings.
Due to the OS upgrade, the SNMP Research software generates a

core dump at this point. This is expected behavior. After
completing the OS and the Insight upgrade, the SNMP Research
kit is also updated. It is safe to continue with the Solaris upgrade.
Step Action
23. The system asks for further upgrade files. Select CD as the media selection and swap
the CDs at the hardware.
The installation of the second CD takes about 20 minutes, depending on your system
performance. After completing the installation of the second CD, the system asks you
if you want to install more software.
Select 2 to complete the installation process.
24. Reboot the system and continue the upgrade process by installing the Sonus
recommended Solaris patches and disabling the appropriate daemons. To reboot
type:
# init 6
Necessary Solaris OS Patches and Actions Introduction
Necessary Solaris OS Patches and Actions
Please download the necessary Solaris OS cluster patches from Sonus’ FTP site.
Solaris 8 Operating System
Sonus tested its products running on Solaris 8 operating systems, using a particular cluster of
Solaris patches from Sun Microsystems. For proper operation and functionality, you must install
the same patch cluster. Sonus has posted the cluster for download on Sonus' FTP site at:
sonus/release/V04.01.xx/patches
Installing the Cluster:
Step Action
1. Move the cluster to a temporary directory, type:
mv Solaris8_Recommended_20020415.tar.Z /tmp
2. Change to the temporary directory, type:
cd /tmp
3. Revert the file compression, type:
uncompress Solaris8_Recommended_20020415.tar.Z
4. Extract the cluster from the tar file, type:
/bin/tar -xvf Solaris8_Recommended_20020415.tar
5. Change to the directory containing the extracted cluster, type:
cd Solaris8_Recommended_20020415
6. Install the cluster, type:
./install_cluster
7. Restart the system with the following command:
shutdown -i6 -g0 -y
If you encounter Error Code 2 during the patch installation process, you
may ignore it. Error Code 2 simply indicates that the patch already
exists on the system.
An Error Code 8 during the patch installation process, indicates that you
attempt to apply a patch to a package that is not installed. In that case
please verify your Solaris OS installation.
Introduction Necessary Solaris OS Patches and Actions
Solaris 2.6 Operating System
Sonus tested its products running on Solaris 2.6 operating systems, using a particular cluster of
Solaris patches from Sun Microsystems. For proper operation and functionality, you must install
the same patch cluster. Sonus has posted the cluster for download on Sonus' FTP site at:
sonus/release/V04.01.xx/patches
Installing the Cluster:
Step Action
1. Move the cluster to a temporary directory, type:
mv Solaris2.6_Recommended_20020415.tar.Z /tmp
2. Change to the temporary directory, type:
cd /tmp
3. Revert the file compression, type:
uncompress Solaris2.6_Recommended_20020415.tar.Z
4. Extract the cluster from the tar file, type:
/bin/tar -xvf Solaris2.6_Recommended_20020415.tar
5. Change to the directory containing the extracted cluster, type:
cd Solaris2.6_Recommended_20020415
6. Install the cluster, type:
./install_cluster
7. Restart the system with the following command:
shutdown -i6 -g0 -y
If you encounter Error Code 2 during the patch installation process, you
may ignore it. Error Code 2 simply indicates that the patch already
exists on the system.
An Error Code 8 during the patch installation process, indicates that you
attempt to apply a patch to a package that is not installed. In that case
please verify your Solaris OS installation.
Disabling Daemons Introduction
Disabling Daemons
The table below lists the daemons that Sonus recommends you disable for security reasons after
installing Solaris and the recommended patches.
To disable the daemons use the command /bin/mv Daemonname daemonname, changing
the first character to lowercase.
For example:
/bin/mv S72autoinstall s72autoinstall
TABLE 1-1. List of Daemons ought to be disabled on Solaris OSs

S72autoinstall S47asppp
S80lp S92rtvc-config
S80spc S91leoconfig
S85power S77dmi
S88sendmail S76snmpdx
S89bdconfig S72slpd
S21perf S71ldap.client
S50rwho S70uucp
S76nscd (Solaris OS 2.6 only!)
Introduction Java Runtime Environment
Java Runtime Environment
With release V04.01 a new version of the Java Runtime Environment (JRE) is required.
To prevent problems with the new version, we recommend removing of the previously loaded Java
2 Runtime Environment.
Removing Previous JRE
Removing Previous JRE
Step Action
1. Select Start | Settings | Control Panel | Add/Remove Programs. This opens the
Add/Remove Programs dialog box.
2. Remove all instances of the Java 2 Runtime Environment Standard Edition.
3. Once all previous JRE instances are removed, close the dialog box and the Control
Panel. You can now resume with the system software upgrades.
Installing the new JRE
When you start up either Insight EMS or the PSX Manager and there is no JRE installed on your
system, the installation of the new JRE version (j2re1_3_1_03-win.exe) is automatically initiated.
Sonus Products and Solaris LOM Introduction
Sonus Products and Solaris LOM
Solaris Light Out Management is a feature that allows server administrators to monitor server
environments, set alarms, and to automatically reboot Netra servers remotely. The LOM feature
requires both, hardware and software. The hardware is already installed on shipments from Sonus
Manufacturing.
Based on the Solaris OS version 2.6 or 8 different software packages are required. The proper
software to utilize this Solaris feature, is provided on the Solaris disks shipped with each product’s
release software. Sonus software supports the alarms generated by LOM only. The fault
notification happens via Insight EMS.
Introduction Sonus Products and Solaris LOM
CHAPTER 2 Insight EMS Software Upgrade
Overview
This section provides upgrade instructions for installing and configuring the required software on
the Sonus Insight server.For instructions on initial configuration you perform after completing the
upgrade, see the Sonus Insight Web-Based Element Management System Installation and User
Guide. The only client-side installation is the Sun Java Plug-in, required to run Java applets
embedded throughout the application.
The following topics are covered in this chapter:
• "Prerequisites" on page 2-3

• "Requirements" on page 2-6
• "Installing Oracle" on page 2-8
• "Oracle Installation" on page 2-10
• "Upgrading an Existing Sonus Insight Database Instance" on page 2-13
• "Manually Starting and Stopping the Intelligent Oracle Agent" on page 2-18
• "Upgrading Sonus Insight" on page 2-19
• "SSL Certificates" on page 2-39
• "Installing OPENssh 3.1p1" on page 2-42
• "Synchronizing with the NTP Server" on page 2-43
• "Installation Notes for NFS Servers" on page 2-44
• "Initial Netcool Configuration" on page 2-45
• "Starting the Sonus Insight Server" on page 2-47
• "Configuring the Primary and Standby Servers" on page 2-48
• "Creating a Minimal Insight Server" on page 2-50
• "Solaris Freeware" on page 2-54
• "Online Documentation Update" on page 2-55
• "Uninstalling Sonus Insight" on page 2-56

Insight EMS Software Upgrade
• "Clearing Client Browser Cache After a Software Upgrade" on page 2-57
Sonus strongly recommends that you back up the Insight EMS before
starting the software upgrade. The recommended method of backing up
your system varies depending upon your current software version. (See
bullets below and/or Figure 2-1.)
The term <BASE_DIR> used throughout this chapter, represents the
base directory of Sonus Insight. The default is /export/home/ems.
Prerequisites Insight EMS Software Upgrade
Prerequisites
You should consider the following items prior to beginning any system upgrade:
• If you are using Insight V3.03.xx or above, prior to performing any system upgrade, run the
manualBackup.sh script (located in <BASE_DIR>/conf directory). This script creates a
tar file that you can use for system recovery. Sonus recommends that you save this tar file to a
safe location external to the system you are upgrading.
The manualBackup.sh script does not create a backup of the

Performance csv files and the system does not carry these files forward
during an upgrade. If you wish to retain these files, you must save them
manually to a safe location prior to upgrading the system.
• If your Insight server is running V3.03.xx or above and you wish to maintain management
capabilities of your network while upgrading your Insight server, follow the procedure
detailed in “Creating a Minimal Insight Server” on page 2-48.
• If your Insight server is running V3.02.xx and you wish to maintain management capabilities
of your network while upgrading your Insight server, Sonus recommends that you follow the
procedure detailed in “Configuring the Primary and Standby Servers” on page 2-46. This
creates a Standby Insight server you can switch to prior to beginning the upgrade process on
your Primary Insight server. The Standby server acts to maintain management capabilities and
simultaneously serves to backup the system. (Backup scripts do not exist for V3.02.xx.)
• If you use the International version of Windows NT and you are upgrading from a release prior
to V03.02.01, you must install the International version of the Sun Java Plug-In v1.3.1_03 on
each client computer. You can obtain this version at the java.sun.com web site.
• Refer to the latest Sonus Insight release notes for important information.
• The Insight server runs as the super user (root) on a Solaris system. If users who do not
typically have root access needs to perform Insight server administration tasks (e.g., starting
and stopping the server), Sonus suggests that the system administrator investigate, install and
appropriately configure the sudo utility (see The Insight Installation and User Guide,
Installation chapter, Solaris Freeware section), designed to solve this type of issue. You can
obtain the sudo utility at http://www.courtesan.com/sudo/.
• If you are planning on running fault management and do not have the Netcool license
information, contact your Sonus representative prior to performing an Insight software
installation or upgrade.
Insight EMS Software Upgrade Prerequisites
The following flowchart provides an overview of the EMS software upgrade process.
FIGURE 2-1. Upgrade Flowchart (Part 1)
S ta rt
W h ic h V e rs io n o f
In s ig h t a re y o u
ru n n in g ?
V 3 .0 3 .x x
V 3 .0 2 .x x
o r h ig h e r
D o y o u w is h to
m a in ta in No No
m anagem ent
c a p a b ility d u rin g D o y o u w is h to m a in ta in
u p g ra d e ? m a n a g e m e n t c a p a b ility d u rin g
u p g ra d e a n d /o r b a c k u p y o u r
s y s te m ?
Yes Yes
C re a te a n d s w itc h to a
M in im a l In s ig h t s e rv e r
(C re a tin g a M in im a l In s ig h t
S e rv e rs )
* C re a te a n d s w itc h to
S ta n d b y In s ig h t s e rv e r o r
P e rfo rm S y s te m B a c k u p c re a te o n ly fo r u s e a s
(V 3 .0 3 .x x o r h ig h e r) backup
(m a n u a lB a c k u p .s h ) (C o n fig u rin g th e P rim a ry a n d
N o te : B a c k u p P e rfo rm a n c e S ta n d b y S e rv e rs )
(c s v ) file s m a n u a lly .
A * C re a tin g a S ta n d b y s e rv e r is
th e re c o m m e n d e d m e th o d o f o f
b a c k in g u p y o u r s y s te m fo r
V 3 .0 2 .x x .
Prerequisites Insight EMS Software Upgrade
FIGURE 2-2. Upgrade Flowchart (Part 2)
If upgrading from Insight

V3.3.X or less, Install
Solaris 8
Install Solaris 8 Patches

and Disable Daemons
If upgrading from Insight

V3.3.X or less, Upgrade
to Oracle 8.1.7
Upgrade the Insight

Database Instance
(upgradeInsightOra.sh)
Note: You may perform
this step after upgrading
Insight. You must perform
it prior to starting Insight
OPTIONAL: Install
OPENssh
Upgrade Insight
(emsInstall.sh)
Complete
Insight EMS Software Upgrade Requirements
Requirements
Refer to the following information on the minimum requirements for operating Sonus Insight.
Hardware - Small Configuration
A small configuration is defined as supporting up to 25 Sonus Insight users and 100 to 200
GSX9000s.
• Sun Enterprise 420R with CD-ROM
• 2 UltraSparc II 450 MHz CPUs
• 1 GB of Memory
• 1 GB of Swap Space (set swap space = physical memory)
• 18.2 GB free disk space in a single partition. A second 18.2 GB drive is optional for disaster
recovery or disk mirroring.
• 1 PCI 10/100 Ethernet interface card (optional). Comes equipped with 1 onboard 10/100
Ethernet interface.
For better performance, Oracle recommends installing their software on

one disk and creating the data store on a second disk.
Hardware - Large Configuration
A large configuration is defined as supporting 50 to 100 Sonus Insight users and 200+ GSX9000s.
• Sun Enterprise 420R with CD-ROM
• 4 UltraSparc II 450 MHz CPUs
• 2 GB Memory
• 2 GB of Swap Space (set swap space = physical memory)
• 18.2 GB free disk space in a single partition. A second 18.2 GB drive is optional for disaster
recovery or disk mirroring.
• 1 PCI 10/100 Ethernet interface card (optional). Comes equipped with 1 onboard 10/100
Ethernet interface.
Requirements Insight EMS Software Upgrade
Software Requirements
Your system must meet the following software requirements prior to installing Insight.
• Solaris 8 operating system and Sonus recommended OS patches

• Enable 64-bit OS support
• Oracle 8.1.7
Sonus recommends that you do not use the Insight server system for
software other than Sonus Insight and related items documented here.
Insight EMS Software Upgrade Installing Oracle
Installing Oracle
This section provides information pertaining to the installation and configuration of the Oracle
8.1.7, required for Insight V4.0 and above. The following process assumes that you previously set
all necessary Oracle users, groups, kernel, and environment variables and that your system meets
the necessary hardware and software requirements.
If your current Insight software is version V4.0, you already have

Oracle 8.1.7 and should skip this section. Continue to "Upgrading an
Existing Sonus Insight Database Instance" on page 2-13
Installing and configuring Oracle for the Sonus Insight Server consists of the following steps:
• Pre-Oracle Installation
• Oracle Installation
• Post-Oracle Installation
• Creating the Database Instance
• Starting and Stopping the Oracle Database
• Starting and Stopping the Database Listener
To successfully install Oracle and the Insight server, follow the instructions in the order
documented. You must have the ability to log in as a root user to modify various system files and
have the fully qualified hostname of the server on which you are installing Oracle. You must also
have X-windows installed on the system running the Oracle Installer (Use any Sun-supported X-
windows server (for example, dtwm, twm, olwm) that supports Motif. Character mode
installations are not supported for Oracle Version 8.1.7.)
Installing the PSX Oracle database on the same server as the Insight
database is not supported.
Installing Oracle Insight EMS Software Upgrade
Pre-Oracle Installation
Prior to installing Oracle 8.1.7, you must perform several preparatory tasks, as follows:
Preparing for the Oracle Installation
Step Action
1. If you have not already done so and you are running V3.03.xx or higher, prior to
performing any system upgrade, run the manualBackup.sh script. This script,
located in the /export/home/ems/conf directory, creates a tar file that you can
use for system recovery, if needed. Sonus recommends that you save this tar file to a
safe location external to the system you are upgrading.
2. Stop the Insight server as follows:
# cd <BASE_DIR>
# ./sonusEms stop
Leave the database instance running during the upgrade process.
3. Edit the initSIDB.ora file located in the <ORACLE_HOME>/product/
8.1.6/dbs directory and set the job_queue_processes parameter to 0.
4. Login as oracle and shut down and re-start the database instance using the svrmgrl
utility as follows:
$ svrmgrl
SVRMGR> connect internal
SVRMGR> shutdown
The shutdown command, without any options, tries to stop the
database normally. If anyone is using the database, shutdown
waits indefinitely for them to either end their session or
disconnect. Prior to issuing this command, you should shutdown
the GUI, Sonus Insight server, and any other connections you may
have to the database. To force disconnections, issue a shutdown
immediate or shutdown abort command.
5. Restart the database instance using the startup command.
SVRMGR> startup
Exit the svrmgrl utility.
6. Shutdown the database Listener using the command:
lsnrctl stop
7. Edit the user's .profile logon file, found in the Oracle user's home directory, changing
all occurrences of 8.1.6 to 8.1.7.
8. Log out and log back in for the changes to take effect. Verify the changes.
Refer to the Pre-Oracle installation section in the Oracle installation manual for any other pre-
installation steps that may be required for your system.
Insight EMS Software Upgrade Oracle Installation
Oracle Installation
Installing the PSX Oracle database on the same server as the Insight
database is not supported. Installing this new instance of Oracle will
stop any other previously installed and running instances of Oracle.
See the Oracle documentation for complete installation instructions.

The following info is a supplement to the Oracle installation instructions
as documented in the Oracle installation manual.
To eliminate problems you may encounter ejecting disk #1, Oracle
recommends copying the contents of the two CDs to directories on your
harddrive (Recommended structure: Disk1/<Contents of CD #1> and
Disk2/<Contents of CD #2> ) and launching the installation from that
location. If the contents of each CD are copied into this structure on the
hard drive, Oracle Universal Installer automatically finds the contents of
each CD and does not prompt for the location of either CD during the
course of installation.
During the Oracle installation, you will be asked to log in as root on another Xterm and run several
scripts. Follow the on-screen instructions for each of these procedures.
Installing Oracle
Step Action
1. Insert the Oracle CD, Disk 1 of 2, in the CD-ROM drive.
2. Log in as oracle.
3. Go to the CD-ROM mount-point directory:
$ cd /cdrom/oracle8i_se
4. Set the DISPLAY variable by issuing the command:
$ DISPLAY=<Your IP Address>:0
$ export DISPLAY
5. Start the Oracle Universal Installer by entering:
$ ./runInstaller
The system displays the Oracle Installation Welcome screen. Click NEXT.
6. The File Locations window should display the default destination of /export/
home/oracle/product/8.1.7. Click NEXT to accept the default destination.
7. In the Available Products Window, select Oracle 8i 8.1.7.0.0. Click NEXT.
8. In the Installation Types Window, select Custom. Click NEXT.
Oracle Installation Insight EMS Software Upgrade
Installing Oracle
Step Action
9. On the Component screen, select/deselect the following items:
a. Select Oracle 8i Server 8.1.7.0.0
b. Deselect Oracle HTTP Server 1.3.12.0.1a
c. Select Oracle Product Option (Deselect the following two item located under this
category.)
Deselect Oracle Intermedia 8.1.7.0.0
Deselect Legato Storage Manager 8.1.7.0.0
d. Select Net8 Products 8.1.7.0.0 (Deselect the following four item located under this
category.)
Deselect Oracle Names 8.1.7.0.0
Deselect Oracle Connection Manager 8.1.7.0.0
Deselect External Naming NIS 8.1.7.0.0
Deselect Oracle Protocol Support 8.1.7.0.0
e. Select Oracle Utilities 8.1.7.0.0
f. Select Oracle Configuration Assistants 8.1.7.0.0
g. Deselect Development Tools 8.1.7.0.0
h. Select Oracle Java Products 8.1.7.0.0
i. Deselect Oracle Enterprise Manager Products 8.1.7.0.0
j. Select Oracle Installation Products 8.1.7.0.0
Click NEXT.
10. On the Privilege Operating System Group screen, enter dba in the OSDBA and
OSOPER fields. Click NEXT.
11. In the Update/Migrate Window, to update and migrate the old database, check the
Migrate Database checkbox and select the database instance from the list. Click
NEXT.
12. On the Summary screen, click the Install button to proceed with the installation.
13. When prompted, insert the second Oracle CD in the CD-ROM drive and change the
path in the Disk Location dialog box to /cdrom/oracle8i_se#1.
To eject the first CD, you should go to the session window you used
to start the install script. Press the enter key to get a normal
prompt. Then cd out of the cdrom directory and issue an eject
command.
14. When prompted, open a second X-term window, login as root, and run the designated
script. After running the script, return to the Oracle Installation window and click OK.
Insight EMS Software Upgrade Oracle Installation
Installing Oracle
Step Action
After running the root.sh script in the X-term window, the script
displays the following message:
IMPORTANT NOTE: Please delete any log and trace files previously created by the
Oracle Enterprise Manager Intelligent Agent. These files may be found in the directories
you use for storing other Net8 log and trace files. If such files exist, the OEM IA may not
restart.
You may ignore this message.
15. In the Net8 Configuration Assistant Window, select Perform Typical Configuration
and click NEXT.
16. In the first Oracle Data Migration Assistant window, verify the path information and
click NEXT.
17. In the second Oracle Data Migration Assistant window, select the default option and
click NEXT.
18. In the third Oracle Data Migration Assistant window, the installer allows you to backup
your database. You have already performed this as part of the pre-installation process
(If you did not back up your database, allow Oracle to do so now.). Select I have
already backed up my database and click NEXT.
19. In the fourth Oracle Data Migration Assistant window, verify the information and click
NEXT. Then click Yes to start the migration.
20. When prompted to migrate the Listener.ora entry, Click Yes.
21. Upon completion of the database migration, you are prompted to check the log files
and verify that the migration was successful. After doing so, assuming a successful
migration, click Finish.
22. When the End of Install window appears, exit the installer.
23. Start the Oracle database (See “Starting and Stopping the Oracle Database” on
page 35.)
Post-Oracle Installation
Refer to the Post-Oracle installation section in the Oracle installation manual for any post-
installation steps that may be required for your system.
Do not attempt to start the Insight server until you have updated the
database instance. Attempting to do so results in an error message.
Upgrading an Existing Sonus Insight Database Instance Insight EMS Software Upgrade
Upgrading an Existing Sonus Insight Database Instance
The following procedure upgrades an existing Sonus Insight database instance from any previous
version to version V04.01.00. You can upgrade the database Instance at this time, or wait for the
Insight Upgrade script to do so (see Step 7 in Scenarios 1, 2, or 3 of Upgrading Sonus Insight.).
You must update the database instance prior to starting Insight.
Although the software upgrade process retains all data, it is good

practice to back up the database prior to any software upgrade.
Your UNIX administrator should verify that the file permissions on your
Insight server allow proper file transfer and execution.
Upgrading the Insight Database Instance
Step Action
1. Shut down any running Insight server that uses the database instance you wish to
upgrade.
2. Log on to the database instance's system as user oracle.
3. Verify that your ORACLE_SID environment variable is set to the proper value that
represents the database instance you wish to upgrade. Use the following command to
verify the current setting of your ORACLE_SID environment variable.
$ set | grep ORACLE_SID
4. The default value is "SIDB" and should be used unless a different value was specified
during the original creation of the database instance. If the value is incorrect, set the
value of the ORACLE_SID environment variable to the proper value using the
following command, where SIDB is the value the environment variable is being set to
in this example.
$ ORACLE_SID=SIDB
5. Do one of the following:
• If you have extracted the contents of the Insight tar file (during the procedure for
upgrading to Insight Version V04.01.00), cd to the extracted oracle directory, and
then run the "upgradeInsightOra.sh" upgrade script from the oracle directory by
entering the following command:
sh upgradeInsightOra.sh
• If you are using the Insight CD, place the CD in the CD-ROM drive and run the
"upgradeInsightOra.sh" upgrade script from the oracle directory of the CD by
entering the following command:
sh upgradeInsightOra.sh
Insight EMS Software Upgrade Upgrading an Existing Sonus Insight Database Instance
Step Action
6. The script asks you to confirm that you have the correct SIDB database instance:
Is SIDB the correct database instance that you wish to
upgrade? (default: N) [y|Y,n|N] ?
Type: y
If you are upgrading from V03.02.xx, you must answer the following questions:
Do you want to AutoStart and AutoStop the Oracle
Intelligent Agent (HIGHLY RECOMMENDED) (default: N)
[y|Y,n|N] ?
Answer y
To configure AutoStart and AutoStop the following
file will be changed... /etc/init.d/oracle
This requires root access. Please provide the root
password:
Enter the password.
The upgrade script updates the contents of your database instance's orasql directory
with the latest files from the insightOraFiles.tar file, and the script will report any errors
should they occur. The tar file is located in the same directory on the CD as the
upgrade script. Steps 7 through 13 (inclusive) only appear if you are upgrading from
versions prior to V03.03.00.
The following messages appear:
Verified that the directory /export/home/oracle/orasql/
SIDB already exists.
Starting the Upgrade Process.
Certain aspects of this process may take a while.
About to make recommended changes to the database
instance SIDB initSonusEms.ora file which may overwrite
any custom settings. Refer to the upgrade documentation
in the Insight User Guide for more information on the
specific changes that will be performed.
If you skip this step you must manually verify that the
compatibility setting in your database instance's ora
file is set to 8.1.6.0.0 before proceeding. You must
restart your database instance manually after you have
made any changes to your database instance's ora file.
Portions of the upgrade will fail along with other
required run time operations if your database instance's
ora file compatibility setting is not set to 8.1.6.0.0.
Step Action
7. The script will ask you if you want to upgrade the following parameters in your
database instance's parameter file:
compatible = 8.1.6.0.0
java_pool_size = 0
db_block_buffers = 102400
shared_pool_size = 32M
log_checkpoint_interval = 10000000
log_buffer = 163840
processes = 100
max_dump_file_size = 10M
Confirm that you wish to have your database instances ora
file upgraded? (default:N) [y|Y,n|N] ?
Sonus recommends that you respond with a y and have the upgrade script make the
suggested changes. Only advanced users who want to preserve custom changes to
their database instance's parameter file should skip this step. One of the required
changes in this step is changing the instance's compatibility setting, which should be
set to "8.1.6.0.0". If you skip this step, you have to manually make the change and
restart the database instance for the change to take affect prior to proceeding with the
database upgrade. If you choose to skip this step, the upgrade script gives you the
option of exiting the upgrade to allow you to manually upgrade your parameter file and
your compatibility setting before proceeding.
Type: y
8. The upgrade script stops and restarts the database instance to read in any changes
made to the parameter file. This will happen even if you have chosen not to upgrade
the parameter file.
If your database instance does not restart successfully, error messages appear
describing the problem. You must correct any problems before you run the upgrade
script again.
You are asked if you want to upgrade your temporary table space. In this release, the
script creates a new temporary table space for your instance to use.
Confirm that you wish to have your temporary table space
and rollback segments upgraded? (default:N) [y|Y,n|N]
Type: y
9. The following prompt appears:
Under what directory location should the files for the
new temporary tablespace be located? (default: /export/
home/oracle/oradata/SIDB)
Either press Enter to accept the default value, or type in another value.
Insight EMS Software Upgrade Upgrading an Existing Sonus Insight Database Instance
Step Action
10. The following prompt appears (displaying the default value or the value you entered):
Database Instance Location:"/export/home/oracle/oradata/
SIDB"
Is the value correct (default:N) [y|Y,n|N] ?
Type: y
To perform the changes to the temporary table space and
rollback segments the password for the Oracle System
account is required.
Input the value of the Oracle System password. (default:
Manager)
Either press Enter to accept the default value, or type in another value.
12. The following prompt appears (displaying the default value or the value you entered):
Oracle System Password: "Manager"
Is the value correct (default:N) [y|Y,n|N] ?
Type: y
13. The following messages appear:
Attempting to run the upgrade script DbStructsUpgrade.sql
via sqlplus using the Oracle System account using the
supplied password Manager. If you have supplied the
incorrect password for the Oracle System account you will
be prompted by sqlplus to supply a valid username and
password.
SQL*Plus:Release 8.1.7.0.0 - Production on Wed Jul 18
11:49:41 2001
© Copyright 1999 Oracle Corporation. All rights reserved.
Connected to:
Oracle8i Release 8.1.7.0.0 - Production
Jserver Release 8.1.7.0.0 - Production
Disconnected from Oracle8i Release 8.1.7.0.0 -Production
Jserver Release 8.1.7.0.0 -Production
Done Updating the temporary table space and rollback
segments
Step Action
14. The upgrade script makes required schema changes to the database. This step
applies to all database upgrades. The length of time required by this process depends
on the size of your Performance Monitoring tables.
The following is an example of messages that appear during the upgrade process.
The actual messages you receive may differ depending upon the software version
from which you are upgrading.
Starting the Upgrade Process.
Upgrading Tables
Upgrading Meta Data
Adding new Tables
Loading new Stored Procedures
Done Upgrading database instance SIDB
Refer to the log file .//export/home/oracle/
SIDB_upgradeTo40.log for information on any errors.
The script has completed upgrading the database instance. Sonus recommends that
you check the log file (mentioned in the above message) for errors. You may ignore
any errors regarding certain tables or resources not existing as the upgrade script
attempts to drop them (for example, DROP TABLE Node_DSM * ERROR at line 1:
ORA-00942: table or view does not exist). Also, if for any reason you run the upgrade
script more than once (not recommended), the log file may contain a number of
additional errors. In most cases, you can ignore these errors as well, but if in doubt,
consult your Sonus Customer representative.
15. Proceed to Upgrading Sonus Insight to upgrade the server that uses the new
database instance.
Insight EMS Software Upgrade Manually Starting and Stopping the Intelligent Oracle Agent
Manually Starting and Stopping the Intelligent Oracle Agent
You must have the Oracle SNMP components and the Database Subagent running for the Oracle
Intelligent Agent to function properly. These components should automatically startup and
shutdown with the oracle database. Manual processes for starting and stopping these components
are described below.
Manually Starting the Intelligent Oracle Agent
Step Action
1. Verify that the SNMP components, master_peer, encap_peer, and snmpd, are not
running by issuing the following commands:
$ ps -aef | grep peer
$ ps -aef | grep snmp
2. If any of the components are running, log in as the root user and use the kill command
to terminate the processes before proceeding.
3. As the root user, run the start_peer script to start the PEER master agent, PEER
encapsulator, and native Sun SPARC Solaris SNMP agent:
# cd $ORACLE_HOME/network/snmp/peer
# ./start_peer -a
4. Verify that the SNMP components are running by issuing the command:
5. Use the following command for the Database Subagent startup.
lsnrctl dbsnmp_start
To shutdown the Oracle Subagent process log in as the root user and issue the following command:
lsnrctl dbsnmp_stop
Upgrading Sonus Insight Insight EMS Software Upgrade
Upgrading Sonus Insight
If you have not already done so and you are running V3.03.xx or higher, prior to performing any
system upgrade, run the manualBackup.sh script. This script, located in the <BASE_DIR>/
conf directory, creates a tar file that you can use for system recovery. Sonus recommends that you
save this tar file to a safe location external to the system you are upgrading.
The manualBackup.sh script does not create a backup of the

Performance csv files and the system does not carry these files forward
during an upgrade. If you wish to retain these files, you must save them
manually to a safe location prior to upgrading the system.
Please note that you should not uninstall your old version of Sonus Insight before installing or
upgrading to the new version. When upgrading, install Oracle first if not already installed.
With Sonus Insight Version V04.00, upgrades from versions prior to V03.02.00 are no longer
supported.
Carefully review each of the four scenarios documented in the following table, and choose the one
that applies to your situation and follow the instructions for that specific scenario.
If you plan to use OPENssh for security, you must install that software
prior to installing Sonus Insight (see “Installing OPENssh” on page 2-
40.)
If you are upgrading from V03.02.xx or V03.03.xx , before running the
upgrade script, save any installed keystore files to a temporary
directory. Typically, this is a single file located in the <BASE_DIR>/
tomcat/webapps/sonusEms/data/sys directory.
Because CIAgent contains an SNMP Master Agent, if you are running a
non-standard SNMP Master agent (other than the default Solaris agent),
it is important that you disable it before attempting this installation.
TABLE 2-1. Installation/Upgrade Scenarios

Scenario 1 I have an older version of Sonus Insight on the system and I want
to install a newer version. I would like to maintain the previous
configuration information including Netcool licensing information
(for example, upgrading from Version V03.02.01 to V04.01.00).
See “Scenario 1” on page 23.
Scenario 2 I have an older version of Sonus Insight on the system and I want
to install a newer version. I do not want to maintain the previous
configuration information including Netcool licensing information
(for example, upgrading from Version V03.02.01 to V04.01.00).
See “Scenario 2” on page 26.
Insight EMS Software Upgrade Upgrading Sonus Insight
TABLE 2-1. Installation/Upgrade Scenarios

Scenario 3 I have already uninstalled Sonus Insight from the system and I
want to install a newer version. I have the file named
<BASE_DIR>/configFiles.tar that was generated by the
uninstall procedure which will be used to maintain all
configuration information except the Netcool licensing. See
“Scenario 3” on page 28.
Scenario 4 I have already uninstalled Sonus Insight from the system and
want to install a newer version. I do not have the file named
<BASE_DIR>/configFiles.tar that was generated by the
uninstall procedure. See “Scenario 4” on page 30.
Scenario 1
If you follow the instructions in this section, all of the previously configured information will be
upgraded to a format compatible with the new version of Sonus Insight. Additionally, the Netcool
licensing information that you configured for the previous version will be maintained.
If you use a tar file to upgrade Sonus Insight EMS on your system, start with Step 1, if you use a
CD, start with Step 2.
Upgrading Insight - Scenario 1
Step Action
1. If you are upgrading using the Insight tar file, as super user, create a directory with the
proper permissions and with enough space for extracting the upgrade files from the
tar file.
a. Change directory to the directory where the tar file exists.
b. Enter the following command:
# /bin/uncompress -c <PATHNAME>/filename.tar.Z | /bin/tar
xvf -
Where filename is the name of the Insight release.
c. Continue to Step 3
To ensure that the above command works correctly, you need to

run the Sun Solaris version of tar (/bin/tar).
2. If you are using the Sonus Insight CD, place the CD in the CD-ROM drive and make
sure it is mounted. If the CD-ROM drive is not already mounted, rebooting will
automatically mount it. Change to the CD-ROM using the command:
# cd /cdrom/cdrom0
Step Action
3. In order to produce a log of the installation, use the /usr/bin/script command
to create a record of the terminal session. This command creates a sub-shell where
you run the installation. When the installation completes, type exit to terminate the
script command. As super user, enter the commands as follows:
# /usr/bin/script -a /emsInstall.log
Script started, file is /emsInstall.log
# ./emsInstall.sh
If the script detects that your system booted with only 32 bit
support, it informs you that the server must be running with 64 bit
support. The system administrator should use the following
command to change to the 64 bit kernel on the next reboot:
eeprom boot-file=/platform/sun4u/kernel/sparcv9/unix
and reboot the system.
4. The software examines your system, if the BEAweb package has not been installed, it
informs you that the BEAweb package must be installed first and asks:
Do you wish to continue [y|Y,n|N] ?
Answer y to this question. The system next asks:
What is the absolute path to package base directory?
(default: /export/home/bea):
Press Enter to accept the default directory.
Step Action
5. Read and answer the questions as follows:
a. You are asked if you would like to upgrade or perform a fresh installation. Answer
a to perform an upgrade.
b. You are asked if you would like to reuse your previous base directory, crontab, and
database values. To reuse your previous values select yes by entering y and
continue with step 5. The script proceeds to uninstall the previous version of
Insight, retaining the necessary information. Depending upon the amount of data
upgraded, this process may take an extended period of time.
To change any of the previously listed values, select no by entering n, continue with
step 4c.
c. If Netcool licensing was configured you will get a message saying that this
information is being copied for use later. If the licensing information is not
configured, you will be informed of this and given an opportunity to quit the
installation. If you continue with the installation at this point you will have to
configure Netcool licensing after this installation is complete.
d. The next step will remove all existing Insight software. If asked to remove a
package, answer y.
e. You are then asked to identify a base directory for the CIAgent installation. A top-
level directory called “ciagent” will be created underneath the base directory you
choose. You can select the default (/export/home) or enter a different location.
Do not install CIAgent underneath the base directory of Sonus Insight or any
other Sonus platform.
f. You are asked to restore your CIAgent configuration from a previous CIAgent
installation. Answer y only if you are upgrading from version V4.00 or later;
otherwise, answer n.
If you answer y, the following prompt appears:
/export/home/ciagent_configFiles.tar exists in the base
directory you selected.
Would you like to use this file to restore your
configuration? (default:Y) [y|Y,n|N]:
Answer y.
g. You must identify a base directory for the Insight installation. A top-level directory
called “ems” will be created underneath the base directory you choose. You can
select the default (/export/home) or enter a different location.
h. Next, you are asked to enter information regarding a cron job that the root user
runs weekly to clean out archive files containing Performance Management
statistics. See "Performance Data Collection" in the Insight Installation and
User Guide for details concerning these archive files. If you are not sure how
changing the settings affect the system, simply choose the default values.
i. Next, enter the fully qualified name or IP address of the server on which the Oracle
installation resides (typically the same host).
j. You will be asked to supply the database instance name for the Insight server.
Accept the default value of SIDB.
Step Action
If your Insight server is currently a registered node within Insight,
you will need to select "Enable Monitoring" from the Insight Node
Administration page for this node in order to ensure it is being fully
monitored.
6. If the installation explicitly stops and tells you that you must run netcoolsetup.ksh after
the installation completes (because the Netcool license information did not exist), you
will have to configure the licensing information. Press Return at the prompt to
acknowledge the message (see the section “Initial Netcool Configuration” on page 2-
44).
7. The script asks if you wish to upgrade the Database Instance. If you answer Yes, the
script proceeds to update the instance. If you answered No, then you must upgrade
the Insight Database Instance before starting Insight. Proceed to “Upgrading an
Existing Sonus Insight Database Instance” on page 2-16 to upgrade a database
instance for use by this Sonus Insight server.
8. At this point, the system has created a log file, emsInstall.log, containing output
from the installation process. If Step 5 told you to run netcoolsetup.ksh, do so now.
You can allow the sub-shell to continue running to record the netcoolsetup script
output. After exiting the sub-shell, you should inspect the file for any installation
errors. To terminate the sub-shell type:
# exit
Do not create a new database instance if you wish to retain the
data in your existing database. See “Creating the Database
Instance” on page 2-32 and “Upgrading an Existing Sonus Insight
Database Instance” on page 2-16 for more information on creating
and upgrading a database instance.
Scenario 2
If you follow the instructions in this section, no information from the existing installation will be
maintained. You will be required to obtain Netcool license key information after the product is
installed.
Step Action
tar file.
xvf -

# cd /cdrom/cdrom0
# ./emsInstall.sh
Step Action
a. The script asks if you would like to upgrade or perform a fresh installation. Answer
b to perform the upgrade.
b. The next step will remove all existing Insight software. If asked to remove a
package, answer y.
c. You must identify a base directory for the CIAgent installation. A top-level directory
called “ciagent” will be created underneath the base directory you choose. You can
select the default (/export/home) or enter a different location. Do not install
CIAgent underneath the base directory of Sonus Insight or any other Sonus
platform.
d. You are asked to restore your CIAgent configuration from a previous CIAgent
installation, answer no to this question, type n.
e. You must identify a base directory for the Insight installation. The script creates a
top-level directory called “ems” beneath the base directory you choose. You can
f. Next, you are asked to enter information regarding a cron job that the root user
g. Next, enter the fully qualified name or IP address of the server on which the Oracle
installation resides.
h. Next, supply the database instance for the Insight server. Accept the default value
of SIDB.
6. The script asks if you wish to upgrade the Database Instance. Answer No and
proceed to “Upgrading an Existing Sonus Insight Database Instance” on page 2-16 to
upgrade a database instance for use by this Sonus Insight server.
from the installation process. After exiting the sub-shell, you should inspect the file for
any installation errors. To terminate the sub-shell type:
# exit
8. See the section “Initial Netcool Configuration” on page 2-44.
data in your existing database. See “Creating the Database
Instance” on page 2-32 and “Upgrading an Existing Sonus Insight
Database Instance” on page 2-16 for more information on creating
and upgrading a database instance.
Scenario 3
In this scenario, you can maintain all of your previous configuration information except for the
Netcool licensing information. The file <BASE_DIR>/configFiles.tar contains the
reusable information. You must obtain Netcool license key information after the product
installation. If you do not want to maintain previous configuration information, follow the
instructions in “Scenario 4” on page 2-30.
Step Action
tar file.
xvf -

# cd /cdrom/cdrom0
# ./emsInstall.sh
Step Action
a. The scripts asks if you have an old archive file from a previous installation. Answer
y to this question.
b. The script looks for a configuration file. If it finds a configuration file, it asks if you
want to use it. If the script does not find the file or if you choose not to use the
indicated file, you are asked to identify the path to the file you wish to use. For
example, if the full path to the file is /home1/ems/configFiles.tar, the answer to this
question would be /home1/ems.
c. The script prompts you to identify a base directory for the CIAgent installation. A
top-level directory called “ciagent” will be created underneath the base directory
you choose. You can select the default (/export/home) or enter a different
location. Do not install CIAgent underneath the base directory of Sonus
Insight or any other Sonus platform.
d. You are asked to restore your CIAgent configuration from a previous CIAgent
installation. Answer y only if you are upgrading from version V4.00 or later;
otherwise, answer n.
If you answer y, the following prompt appears:
/export/home/ciagent_configFiles.tar exists in the base
directory you selected.
configuration? (default:Y) [y|Y,n|N]:
Answer y.
e. You must identify a base directory for the Insight installation. The script creates a
top-level directory called “ems” beneath the base directory you choose. You can
f. Next, you are asked to enter information regarding a cron job that the root user
g. Next, enter the fully qualified name or IP Address of the database server on which
the Oracle installation resides.
h. Next, supply the database instance for the Insight server. Accept the default value
of SIDB.
Step Action
44).
7. Perform one of the following steps:
a. The script asks if you wish to upgrade the Database Instance. If you answer Yes
the script proceeds to update the instance. If you answered No, then you must
upgrade the Insight Database Instance before starting Insight. Proceed to
“Upgrading an Existing Sonus Insight Database Instance” on page 2-16 to upgrade
a database instance for use by this Sonus Insight server.
b. If you have removed your existing Insight database instance, proceed to “Creating
the Database Instance” on page 2-32 to create a new database instance for use
by this Sonus Insight server.
errors. To terminate the sue-shell type:
# exit

data in your existing database.
Scenario 4
If you use a tar file to install Sonus Insight EMS on your system, start with Step 1, if you use a CD
as the installation media, start with Step 2.
Step Action
tar file.
xvf -
Step Action

# cd /cdrom/cdrom0
# ./emsInstall.sh
Step Action
a. You are asked if you have an old archive file from a previous installation. Answer
n to this question.
b. You are then asked to identify a base directory for the CIAgent installation. A top-
level directory called “ciagent” will be created underneath the base directory you
Do not install CIAgent underneath the base directory of Sonus Insight or any
other Sonus platform.
c. You are asked to restore your CIAgent configuration from a previous CIAgent
installation, answer no to this question, type n.
d. You are then asked to identify a base directory for the Insight installation. A top-
level directory called “ems” will be created underneath the base directory you
e. Next, you are asked to enter information regarding a cron job that the root user
f. Next, you are asked to enter the fully qualified name or IP address of the server on
which the Oracle installation resides.
g. You will be asked to supply the database instance for the Insight server. Accept the
default value of SIDB.
6. The script asks if you wish to upgrade the Database Instance. Answer No and
proceed to “Upgrading an Existing Sonus Insight Database Instance” on page 2-16 to
upgrade a database instance for use by this Sonus Insight server.
44).
errors. To terminate the sue-shell type:
# exit
9. Proceed to “Creating the Database Instance” on page 2-32 for instructions on creating
a new database instance for use by this Sonus Insight server.
Creating the Database Instance
Creating a new database using the same database instance name will
delete all existing data for that database instance. Only create a new
database instance if you do not already have an existing database
instance name. To upgrade a pre-existing Insight database instance to
the new version, refer to “Upgrading an Existing Sonus Insight
Database Instance” on page 2-16.
Creating the database Instance
Step Action
1. Log in as oracle.
2. Verify that the oracle user environment variable ORACLE_SID is equal to SIDB.
$ set | grep ORACLE_SID
3. Log out as oracle.
4. Log in as root.
5. On the Insight Install CD you find a shell script and a tar file in the oracle directory.
6. cd to that directory and run the shell script as follows:
# sh ./configureInsightOra.sh
7. You are asked to supply the database instance for the Insight server. Accept the
default value of SIDB.
8. As the various shell scripts proceed, they will echo progress information to the screen,
ask you to confirm several operations, and ask you for input as required. You see
output similar to the following:
ORA_USER = oracle
ORA_GROUP = dba
ORACLE_BASE = /export/home/oracle
ORACLE_HOME = /export/home/oracle/product/8.1.7
ORACLE_SID = SIDB
PATH=/export/home/oracle/product/8.1.7/bin:/usr/bin:/
usr/local/bin:.:/usr/sbin:/usr/bin
LD_LIBRARY_PATH=:/export/home/oracle/product/8.1.7/lib:
/usr/openwin/lib:/usr/dt/lib:/usr/dt
CWD = /export/home/test2
chmod 777 /export/home/oracle/SQL/InstallDb.log
Step Action
9. If this is not the first time you have run the configureInsightOra.sh script, you are
notified that several directories already exist. Answer y to modify the directory
attributes as necessary:
Directory "/export/home/oracle/orasql" already exists.
Modify its attributes as necessary and continue
(default:N) [y|Y,n|N] ? y
chown oracle:dba /export/home/oracle/orasql
chmod 775 /export/home/oracle/orasql
mkdir /export/home/oracle/orasql/SIDB
chown oracle:dba /export/home/oracle/orasql/SIDB
chmod 775 /export/home/oracle/orasql/SIDB
cp /export/home/oracle/SQL/*/export/home/oracle/orasql/
SIDB
chown oracle:dba /export/home/oracle/orasql/dba/*
chmod 770 /export/home/oracle/orasql/dba/*
10. You are notified that several more directories already exist. Answer y to modify the
directory attributes as necessary:
Directory "/export/home/oracle/oradata" already exists.
Modify its attributes as necessary and continue
(default:N) [y|Y,n|N] ? y
chown oracle:dba /export/home/oracle/oradata
chmod 775 /export/home/oracle/oradata
mkdir /export/home/oracle/oradata/SIDB
chown oracle:dba /export/home/oracle/oradata/SIDB
chmod 775 /export/home/oracle/oradata/SIDB
Step Action
11. You are asked if you wish to have the system files in the /etc directories modified to
automatically start and stop the Oracle database on system startup and shutdown
respectively. Answer y to AutoStart and AutoStop Oracle.
Do you want to AutoStart and AutoStop the database
(HIGHLY RECOMMENDED) (default:Y) [y|Y,n|N] ? y
To configure AutoStart and AutoStop the following files
will be changed...
/etc/init.d/oracle
/etc/rc2.d/S79oracle
/etc/rc0.d/K05oracle
Do you want to continue with the AutoStart and AutoStop
setup (default:Y) [y|Y,n|N] ? y
rm -f /etc/init.d/oracle /etc/rc2.d/S79oracle /etc/rc0.d/
K05oracle
cp /export/home/oracle/SQL/oracle /etc/init.d
chmod 755 /etc/init.d/oracle
ln -s /etc/init.d/oracle /etc/rc2.d/S79oracle
ln -s /etc/init.d/oracle /etc/rc0.d/K05oracle
Starting the Perl script CreateDb to create the
database....
su - oracle -c "cd /export/home/oracle/orasql/SIDB; perl
./CreateDb -l1 -d/export/home/oracle/oradata/SIDB"
Sun Microsystems Inc. SunOS 5.6 Generic August 1997
Database Install Start. Start time Tue Dec 5 09:35:05
EST 2000
$oraBase=|/export/home/oracle| $oraHome=|/export/home/
oracle/product/8.1.7| $oraSid=|SIDB|
12. If it is already running, the Perl script asks you to stop the oracle client listener.
Answer y to stop the Oracle client listener.
The Listener is running. Shut it down (default:Y)
[y|Y,n|N] ? y
Stopping Listener.......Done
Step Action
13. The Perl script asks you for the fully qualified host name of the system you are
installing Oracle on. Be sure to enter the fully qualified host name of your system. For
example: yourhostname.yourdomain.com
Please enter the following information for this database:
The directory for the database files set in the command\
line is "/export/home/oracle/oradata/SIDB"
What is the fully qualified name or IP address of
the Database server?
(e.g. hostname.domain.com, or 10.1.1.1):
14. You should see output similar to the following, indicating that the creation of the
Oracle instance for the Insight server is proceeding successfully:
Starting Oracle Instance.......Done
Creating Database.......Done
15. After appproximately one hour, you should see output similar to the following,
indicating the successful creation of the Insight database instance.
Creating Database Data Dictionary.......
Creating Product and User Profile tables.......Done
Creating Database Structures.......Done
Creating Tables.......Done
Stopping Oracle Instance Normally.......Done
Starting Normal Oracle Instance.......Done
Database Install Complete. End time Mon Apr 23 16:55:39
EST 2001
The CreateDb script has completed successfully. The
database install is complete.
Starting and Stopping the Oracle Database
The Oracle Database should automatically start and stop at system startup and shutdown time
respectively if you have chosen to enable that feature during the creation of the Insight database
instance. If you wish to manually start or stop the Oracle database, follow the procedures below.
Manually Starting an Oracle Instance
Step Action
1. Login as the user oracle.
2. Start the Oracle Server Manager utility svrmgrl.
3. Type connect internal and press Return.
4. Type startup and press Return.
Manually Starting an Oracle Instance
Step Action
5. 1. Once the database starts, type exit to exit out of the utility. A typical
session is shown below. All data entered by the user is shown in bold
type.
$ su - oracle
Password:
Sun Microsystems Inc. SunOS 5.6 Generic Apr 2001
$ svrmgrl
Oracle Server Manager Release 3.1.6.0.0 - Production
Copyright (c) 1997, 1999, Oracle Corporation. All Rights
Reserved.
JServer Release 8.1.7.0.0 - Production
Connected.
SVRMGR> startup
ORA-25138: SEQUENCE_CACHE_ENTRIES initialization
parameter has been made obsolete
ORA-25138: SEQUENCE_CACHE_HASH_BUCKETS initialization
ORA-25138: DISTRIBUTED_LOCK_TIMEOUT initialization
ORACLE instance started.
Total System Global Area
26038256 bytes
Fixed Size 69616
bytes
Variable Size 24752128
bytes
Database Buffers 1126400
bytes
Redo Buffers 90112
bytes
Database mounted.
Database opened.
SVRMGR> exit
Server Manager complete.
Manually Shutting Down an Oracle Instance
Step Action
1. Shut down the Sonus Insight server using the following command:
<BASE_DIR>/sonusEms stop
2. Shut down any SQLPLUS or SVRMGRL sessions that are connected to the
database.
3. Log in as the user oracle.
4. Start the Oracle Server Manager utility svrmgrl.
5. Enter the following command:
connect internal
6. Shut down the database with the following command. This command will wait for any
existing connections to the database to disconnect before shutting down the
database.
Shutdown
The shutdown command, without any options, tries to stop the
database normally. If anyone is using the database, shutdown
awaits indefinitely for them to end their session or disconnect, so
you should shut down the GUI, Sonus Insight server, and any other
connections you may have to the database. To force
disconnections, issue a shutdown immediate or shutdown abort
command.
Manually Shutting Down an Oracle Instance
Step Action
7. Once the database has been shut down, exit out of the Oracle Server Manager utility
using the following command:
exit
A typical session is shown below. All data that is entered by the user is shown
boldfaced.
$ su - oracle
Password:
Sun Microsystems Inc. SunOS 5.6 Generic August
1997
$ svrmgrl
Oracle Server Manager Release 3.1.6.0.0 - Production
Copyright (c) 1997, 1999, Oracle Corporation. All Rights
Reserved.
JServer Release 8.1.7.0.0 - Production
Connected.
SVRMGR> shutdown
Database closed.
Database dismounted.
ORACLE instance shut down.
SVRMGR> exit
Server Manager complete.
Starting and Stopping the Database Listener
The Oracle client listener should automatically start up and shut down with the Oracle database.
• To manually start the Oracle Listener, login as oracle and use the following command:
lsnrctl start
• To manually stop the Oracle Listener, login as oracle and use the following command:
lsnrctl stop
SSL Certificates Insight EMS Software Upgrade
SSL Certificates
Sonus Insight V04.01.00 can be configured to support HTTPS. The following instruction details
one way to set up SSL support for Sonus Insight V04.01.00. For detailed description about SSL
certificate under Java platform please refer to, http://java.sun.com/products//jdk/1.2/docs/guide/
security/cert3.html.
Upgrading the SSL Certificate
Sonus Insight V04.01.00 supports server side HTTPS using the X.509 (RSA) certificate. The
Sonus Insight V04.01.00 installation contains all necessary tools for SSL certificate generation. If
you are upgrading from V03.02.xx or V03.03.xx, follow this procedure to upgrade your SSL
Certificate. If you are upgrading from V03.04.xx, the upgrade script handles this automatically.
Upgrading the SSL Certificate (Insight V03.03 and below only)
Step Action
1. Create a copy of the original keystore file used by TOMCAT that you stored into a
temporary location.
2. Change the copied file to ems.keystore.
3. Use keytool to change the passwords of the keystore and all keys to sonusems.
You find keytool in <BASE_DIR>/jre/bin.
4. Clone the site certificate and the CA certificates using keytool. Make sure that the
aliases are insight and insight_ca respectively.
5. Export the private key from the keystore by using the following command:
<BASE_DIR>/jre/bin/java com.sonus.ems.proxy.server.
ExportPrivateKey <KEYSTORE_PATH> <KEYSTORE_PASSWD>
insight <KEYSTONE_PASSWD> insightSitePrivateKey.der
6. Convert the private key to *.pem file format:
<BASE_DIR>/conf/openssl pkcs8 -inform DER -nocrypt -in
insightSitePrivateKey.der -out insightSitePrivateKey.pem
7. Use keytool to export the site certificate and CA certificate from keystore. Make
sure the certificate files have the right names:
• Site certificate name: insightSiteCert.pem
• CA certificate name: insightCaCert.pem
8. Copy the keystore file, the private key file, and the certificate files to the following
directory:
<BASE_DIR>/weblogic/sonusEms/data/sys
Insight EMS Software Upgrade SSL Certificates
Upgrading the SSL Certificate (Insight V03.03 and below only)
Step Action
9. Add following lines to <BASE_DIR>/ems/weblogic/
weblogic.properties:
weblogic.security.certificate.server=sonusEms/data/sys/
insightSiteCert.pem
weblogic.security.key.server=sonusEms/data/sys/
insightPrivateKey.pem
weblogic.security.certificate.authority=sonusEms/data/
sys/insightCaCert.pem
# <BASE_DIR>/jre/bin/keytool -import -alias tomcat -file
# <BASE_DIR>/conf/thawte.cert -keystore
# <BASE_DIR>/conf/.keystore
Configuring Sonus Insight V04.01.00 for SSL Support
Please make sure that the SSL configuration in <BASE_DIR>/weblogic/weblogic-

properties.xml contains the following line:
weblogic.system.SSLListenPort=443
The aim of the previous sections is to provide help with a real example in installing an SSL
certificate in Sonus Insight V04.01.00. System administrators are advised to coordinate closely
with their chosen CA. Useful information can be found at: http://java.sun.com/products//jdk/1.2/
docs/guide/security/cert3.html.
Installing OPENssh Insight EMS Software Upgrade
Installing OPENssh
The SSH Secure Shell is a third-party software suite used to provide secure network
communications between Sonus Insight EMS and other network elements. Insight supports the use
of OPENssh version 3.1p1. The Open SSH binary is bundled into a standard Solaris package,
which you can install and manage using standard pkg commands (for example, pkgadd, pkginfo,
etc).
In order for SSH to operate, you must first install the Sonus SSH package on the Insight server and
on each managed device (for example, the PSX Policy Server, the NFS server, etc.) as well as the
Solaris systems acting as SSH proxies for the GSX9000 and the SGX SS7 Signaling Gateway,
Riverstone devices, and any other devices that can not run SSH directly.
The platform configuration for all Sonus servers includes Secure Shell protocol facilitated by
OPENssh open source code.
The OPENssh package includes the following components:
• SSH Server
• SSH Client
• Secure FTP (SFTP)
• Secure File Copy
• Startup and stop scripts for SSH server
Insight EMS Software Upgrade Installing OPENssh
Installing OPENssh 3.1p1
The following procedure details the steps necessary for the installation of the OPENssh 3.1p1
package.
Installing OPENssh 3.1p1
Step Action
1. Copy the OPENssh.3.1.p1_Secureid_sol8.pkg package to a temporary directory,
and then unzip the file.
2. To begin the installation type:
pkgadd -d OPENssh.3.1p1_Securid_sol8.pkg
3. The system displays the available packages. Enter 1 at the prompt for the OPENssh
3.1p1 package.
4. The system asks if you wish to create the directory /opt/OPENssh. Enter y.
5. The system processes the package and informs you that script with super user
permissions run during the installation. You are asked if you want to continue. Enter y.
The installation completes and the SSH daemon starts. Follow any additional instructions
generated by the scripts.
Enabling SSH
After installation, you must do the following to enable SSH:
Enabling SSH
Step Action
1. Stop the Insight server.
2. In the Insight SystemConfig.txt file, locate the parameters sshPath=SSH-
COOKIE/bin and scpCmd=SSH-COOKIE/bin/scp and replace SSH-COOKIE
with the base directory of the installed SSH package.
3. Restart Insight server.
With SSH enabled, you can select the use of SSH when registering the various devices (See
“Registering Nodes with the Insight Server”.)
Synchronizing with the NTP Server Insight EMS Software Upgrade
Synchronizing with the NTP Server
To ensure correct operation of the Performance Management Component, the Insight server, the
GSX9000s, and the SGX2000s must be synchronized with the same NTP server. This applies only
to Sonus Insight installations that are using the Performance Management Component.
Synchronizing ensures that the timestamps in the collected data are consistent with the GSX9000s,
the SGX2000s, and the Insight server's notion of time. Failure to do so could also introduce error
into certain statistics, notably the trunk group performance statistics.
Insight EMS Software Upgrade Installation Notes for NFS Servers
Installation Notes for NFS Servers
In order to access GSX9000 call trace files, enable the CDR viewer and reporting functions, the
Insight (EMS) host requires access permission to the NFS servers that store them. The exports file
of all NFS servers that the Insight server is expected to mount must be updated to permit Insight
mount privileges and (minimally) read-only file access for the user that started the Insight server.
For example:
/vol/vol0/GsxNFS -root=myemshost,ro
When Sonus Insight is installed, a process is started to collect PSX6000 events. It does so by
listening on a UDP port for events transmitted by one or more PSX6000 servers. The default port
on which these events are received is 9004. Each PSX6000 must be instructed to send its events to
the Insight host and to this port by updating the pes.config file to add the Insight server as the local
host.
When configuring call trace destination in the pes.config file, use the IP address of the Insight
server through which the PSX6000 is reachable instead of the host name in case the host name
cannot be resolved.
See the PSX6000 Sonus SoftSwitch Installation Guide for more information.
When setting up a system, it must be properly configured to handle automounting. If NIS is not
configured for the system, ensure that the automount entry in /etc/nsswitch.conf does not
reference nis. If NIS is configured, issue the /bin/ypwhich command to confirm that the NIS
server is reachable.
It should return the name of the current NIS server. If not, the system may not be correctly
configured (see related Solaris system administration guides) and/or ypbind may not be running. If
the later case is true, simply issue ypbind. For example:
...more...
publickey: nis [NOTFOUND=return] files
netgroup: nis
automount: files nis
aliases: files nis
...more...
may need to change to:

...more...
publickey: nis [NOTFOUND=return] files
netgroup: nis
automount: files
aliases: files nis
...more...
Initial Netcool Configuration Insight EMS Software Upgrade
Initial Netcool Configuration
This procedure assumes that you have the Netcool license key information from Sonus Networks.
If you don't, contact your Sonus representative before you begin this procedure. Instructions for
installing Netcool and performing the initial configuration are as follows:
Configuring Netcool
Step Action
1. Log in as root.
2. Create the directory <BASE_DIR>/conf/license.
3. Create the file <BASE_DIR>/conf/license/licenseInfo and copy the text
of the Netcool license keys that you received from Sonus to the file.
4. Run the setup script to configure Netcool-related components.
# cd <BASE_DIR>/conf/
# ./netcoolsetup.ksh
This script sets up licensing, and modifies configuration files and database tables for
Netcool.
5. During execution of this script, you will be prompted for the user name and password
under which the PA process will run. Enter a valid user name and password.
You do not have to use the root user name and password. The
password cannot contain special characters such as #,{, or }.
6. Start the Netcool processes.
Starting Netcool Processes
Start the Netcool processes using the following commands:

# cd <BASE_DIR>
# ./sonusNco start
To verify the status of Netcool processes, type:
Insight EMS Software Upgrade Initial Netcool Configuration
# ./sonusNco status or # ./showStatus fault
Several Netcool components have a delayed startup due to their

dependence on the Netcool database. These processes will show a state
of "PENDING." If processes remain in a "PENDING" state longer than
two minutes after startup, there is a configuration problem.
If you need to Stop the Netcool processes, do so as follows:

# cd <BASE_DIR>
# ./sonusNco stop
Starting the Sonus Insight Server Insight EMS Software Upgrade
Starting the Sonus Insight Server
Start the Insight server as follows:

# cd <BASE_DIR>
# ./sonusEms start
sonusEms start can also be called with arguments that control memory
size allocations. To get help with this command, enter: # sonusEms
help
To verify the status of the Insight server, enter:

# ./sonusEMS status
Stop the Insight server as follows:

# cd <BASE_DIR>
# ./sonusEms stop
To obtain a status for most Insight processes, enter:

# ./showStatus
Insight EMS Software Upgrade Configuring the Primary and Standby Servers
Configuring the Primary and Standby Servers
Use this procedure only if your system is running V3.02.XX.
The Standby system simply exports a file system to the Primary system. Once this export is
performed, the Primary system is configured to mount this file system and then run a cron job that
will copy data to the Standby file system.
Only one instance of the two Insight instances should be running at one
time.
Configuring the Primary and Standby Servers
Step Action
1. First configure the Standby server.
You need the fully qualified name of the Primary server that this system backs up. To
perform this step, execute the following command:
# <BASE_DIR>/ems/conf/makeStandby.sh
2. Next configure the Primary server.
You need the fully qualified name of the Standby server. This script adds a line to the
crontab, which copies the backup data to the Standby server. Backups can be
configured to happen between one and four times an hour. If you choose once an
hour, the files will be backed up at the beginning of every hour; twice an hour, and the
files will be backed up at the beginning and half past each hour; three times, and the
files will be backed up at the beginning, twenty minutes past and forty minutes past
each hour; four times an hour, and the files will be backed up at the beginning, fifteen
minutes past, thirty minutes past, and forty-five minutes past each hour. To perform
this step, execute the following command:
# <BASE_DIR>/ems/conf/makePrimary.sh
A system can be both a Primary and a Standby server at the same

time. However, you should remember that only one Insight server
should manage any given node at one time.
At this point you have configured both a Primary and a Standby server. The next step is to bring up
the Standby server with the configuration of the Primary server. Perform this procedure only when
the Primary server has failed or has been intentially removed from service.
Configuring the Primary and Standby Servers Insight EMS Software Upgrade
If the cronjob that copies the files fails, the system sends a mail
message to the root user account detailing the problem.
Initializing and Starting the Standby Server
In this example, ems1 is a Primary server and ems2 is a Standby server.
Example: ems1 has been running for a long time, and it has been configured with users and nodes,
has had Task Configurator tasks created, and has been gathering performance statistics. For some
reason, the server stops working. ems2 will now be started with the configuration information of
ems1. The user logs into ems2 and runs the installBackupFiles.sh script to load the configuration
information. Once this is completed, the user starts the fault and Insight processes. When the
server has been confirmed to be running with the configuration information from ems1, the user
will then load the statistics data. After this step has been completed (performance statistics could
take several hours to load), the failover is complete.
The commands shown below are the commands that would be executed by the user on ems2 to
perform the failover.
# cd <BASE_DIR>/conf
# ./installBackupFiles.sh
# cd <BASE_DIR>
# ./sonusNco start
# ./sonusEms start
# ./installStats.sh
Now that ems2 is running, the user can take the time to repair ems1 or replace it with a new
instance of Insight altogether. In effect, ems2 is now the Primary server and ems1, once repaired,
will become the Standby server. Once ems1 is ready for service, the user would execute the
makeStandby.sh and makePrimary.sh scripts as described above except they would be run on
opposite machines.
Insight EMS Software Upgrade Creating a Minimal Insight Server
Creating a Minimal Insight Server
Use this procedure only if your system is running V3.03.XX or higher.
If you do not have a redundant Insight server, in order to maintain management capabilities while
upgrading your system, Sonus recommends that you create a temporary, minimal Insight
management platform. The minimal server has the capability to manage registered nodes, role/user
information, and receive traps.
To create the minimal insight platform do the following:
If your system is V3.04 or higher substitute weblogic for tomcat/

webapps in the path statements detailed in Steps 2a and 3a.
Step Action
1. Install the same version of Insight running on your primary server to a backup system
(see The Insight Installation and User Guide).
2. On the primary Insight sever do the following:
a. cd <BASE_DIR>/tomcat/webapps/sonusEms/data/sys
b. /bin/tar cf /tmp/nodesUsers.tar Managed*.txt
c. Record the value generated by the following command:
/bin/grep tfNotifyRatio SystemConfig.txt
d. ftp yourBackupSystem and put /tmp/nodesUser.tar in /tmp
3. On the backup system do the following:
a. cd /<BASE_DIR>/tomcat/webapps/sonusEms/data/sys
b. /bin/tar xf /tmp/nodesUsers.tar
Creating a Minimal Insight Server Insight EMS Software Upgrade
Step Action
4. Replace all occurrences of the Primary Server IP address with the Secondary Server
IP address by entering the following script:
for i in `/bin/ls Managed*.txt`
do
/bin/sed ‘s/OldIpAddress/NewIpAddress/g’ $i>$i.new
/bin/mv $i.new $i
done
/bin/egrep -v ‘tfNotifyRatio|upgradeNode|upgradeUser’
SystemConfig.txt>afile.txt
/bin/echo “tfNotifyRatio=TheValueFromStep2c”>>afile.txt
/bin/echo “upgradeNodeEncryption=true”>>afile.txt
/bin/echo “upgradeUserEncryption=true”>>afile.txt
/bin/echo “upgradeNodes=true”>>afile.txt
/bin/echo “upgradeUsers=true”>>afile.txt
/bin/mv afile.txt SystemConfig.txt
5. After running the script, start the system. All users and nodes that existed on the
Primary system now exist on the Backup system.
6. Log into the system (you must have Administrator privileges) and access the Insight
Administrator.
7. Select the General tab and the Managed Device Association category.
8. Enter the IP Address of the newly created Minimal Insight Sever and click the
Associate button. This enables the Minimal Insight Server to receive trap information
from the registered nodes.
Changing Default Ports
You can configure Insight to run on ports other than the default 80/443 for http/https protocol. To
configure the http protocol and port number for Sonus Insight, the System Administrator must do
the following:
Step Action
1. Determine the protocol (http or https) and port number (defaults are 80 and 443
respectively) to use.
The system requires an SSL certificate to support the https

protocol.
Insight EMS Software Upgrade Creating a Minimal Insight Server
Step Action
2. Issue the following command:
# cd <BASE_DIR>/conf
3. Execute the following command with the proper arguments for your configuration.
(For example, to configure Insight to run on http port 8080, the System Administrator
enters the following: <BASE_DIR>/conf/configHttp http 8080):
# <BASE_DIR>/conf/configHttp http <port>
4. Edit <BASE_DIR>/weblogic/weblogic-properties.xml to reflect the changes.
Continuing with the example in step 3, the System Administrator must make changes
as follows:
a. To change the default port to 8080, search for the following comment line in the
weblogic-properties.xml file:
## TCP/IP port number at which the WebLogic Server
listens for connections
Change the entry below that comment, by default:
weblogic.system.listenPort=80
as follows:
weblogic.system.listenPort=8080
b. To change the default port 443, search for the following comment line in the
weblogic-properties.xml file:
## SSL listen port
Change the entry below that comment, by default:
weblogic.system.SSLListenPort=443
5. Stop and restart Netcool using the commands:
<BASE_DIR>/sonusNCO stop
<BASE_DIR>/sonusNCO start
6. Stop and restart Sonus Insight using the commands:
<BASE_DIR>/sonusEms stop
<BASE_DIR>/sonusEms start
Creating a Minimal Insight Server Insight EMS Software Upgrade
Configuring Multiple User Interfaces
When a server has multiple network interfaces, Sonus Insight requires the proper configuration of
the /etc/hosts file, allowing the user the option of selecting which network interface to connect a
node (e.g., GSX9000). During the Node Registration process, the user selects the desired IP
address from the Mgmt Client IP Address pull-down menu. The following is an example of an
entry in an /etc/hosts file. In the example, the server named samplehost has two network
interfaces with IP addresses of 38.45.67.123 and 38.33.54.26.
#
# Internet host table
#
127.0.0.1 localhost
38.45.67.123 samplehost samplehost.yourcom.com loghost
38.33.54.26 samplehost
38.45.67.33 otherhost
Insight EMS Software Upgrade Solaris Freeware
Solaris Freeware
The following Solaris freeware tools are available for installation:
• gzip
• lsof
• top
• sudo
• traceroute
Each of these will be installed in /usr/local/bin.
To install:
pkgadd -d gzip-1.2.4-sol8-sparc-local
gunzip lsof-4.33-sol8-sparc-local.gz
pkgadd -d lsof-4.33-sol8-sparc-local
gunzip top-3.5beta8-sol8-sparc-local.gz
pkgadd -d top-3.5beta8-sol8-sparc-local
gunzip sudo-1.5.4-sol8-sparc-local.gz
pkadd -d sudo-1.5.4-sol8-sparc-local
gunzip traceroute-1.4a5-sol8-sparc-local.gz
pkgadd -d traceroute-1.4a5-sol8-sparc-local
If you don't already have gunzip, you'll need to install the gzip package. If you already have it, then
you won't need to install it.
For usage instructions of the above tools, see the man pages for lsof, traceroute, sudo or the
documentation in /usr/local/doc* after the packages are installed. The above tools are all courtesy
of http://www.sunfreeware.com.
Online Documentation Update Insight EMS Software Upgrade
Online Documentation Update
Sonus online documentation included with the installation may become out of date. Updates will
be made available for installation on the Insight server.
Update the online documentation using the SONSdoc package and docsInstall.sh script from the
Sonus Insight Documentation CD as follows:
Updating the Online Documetation
Step Action
1. Insert the Sonus Insight Documentation CD into the Insight server CD-ROM drive.
2. Copy the SONSdoc_xxxxxx.tar.Z file to a temp directory.
3. Decompress the file then untar it using the following command:
# zcat <filename> | tar xvf -
4. Install the SONSdoc package by executing the following command:
# ./docsInstall.sh
Once the script completes, you can access the files through the Online Library section of Insight.
Insight EMS Software Upgrade Uninstalling Sonus Insight
Uninstalling Sonus Insight
Sonus Insight should not be uninstalled using the commands below unless you intend to
permanently remove Insight from your system.
Uninstall the Sonus Insight using the following commands:
# cd <BASE_DIR>/conf/
# ./emsUnInstall.sh
When executed, emsUnInstall.sh creates a tar file, <BASE_DIR>/configFiles.tar. You

should save this file in case you need to revert to the previous installation.
Clearing Client Browser Cache After a Software Upgrade Insight EMS Software Upgrade
Clearing Client Browser Cache After a Software Upgrade
After you perform an upgrade to a new version of Insight software, have each user who is running
an Insight client clear their Web browser's cache to prevent cached pages from the previous
version from being temporarily displayed.
Internet Explorer
Clearing Internat Explorer Cache
Step Action
1. Select the Tools menu from the Internet Explorer toolbar.
2. Select Internet Options.
3. From the Temporary Internet Files box, click Delete Files.
4. In the Delete Files dialog box, select the Delete all offline content check box, and
then click OK.
5. Click Settings, and set "Check for newer versions of stored pages:" to Every Visit
to the Page.
Netscape Navigator
Clearing Netscape Navigator 4.72 Cache
Step Action
1. Select Preferences… from the Edit menu in the Netscape toolbar.
2. Select Advanced, Cache.
3. Click Clear Disk Cache.
4. Set the "Document in cache is compared to document on network" setting to
Every time.
5. Click OK.
Insight EMS Software Upgrade Clearing Client Browser Cache After a Software Upgrade
CHAPTER 3 PSX Software Upgrade
Overview
This section provides information about upgrading PSX installations in both standalone and
redundant environments. In a standalone environment, you must halt call processing during the
software upgrade process. A redundant environment allows for uninterrupted call processing
during the software upgrade.
• "PSX Upgrade Overview" on page 3-2

• "Prerequisites for the PSX Software Upgrade" on page 3-5
• "Updating the PSX Software" on page 3-7
• "Upgrading the Database on the Master PSX" on page 3-11
• "Update/Migrate the Slave (Replica) Database" on page 3-16
• "Upgrading the PSX Manager Software" on page 3-20
• "PSX Database Upgrade and Numbering Plans" on page 3-21
• "Process Management" on page 3-22
Sonus strongly recommends that you back up the PSX Policy Server
before starting the software upgrade.
In a master/slave setup, force a database replication prior to the
upgrade and stop any configured automatic replication intervals.

PSX Software Upgrade PSX Upgrade Overview
PSX Upgrade Overview
In a network with multiple PSX systems, one PSX needs to host the Master Database. The other
PSXs each host a replicated database. A replica database is updated using a database replication
mechanism, based on a user configurable replication interval.
In a redundant network setup you need to dedicate one PSX as a primary and one PSX as the
secondary policy server for each GSX. The primary and secondary PSX are configured using the
GSX CLI or Insight GUI.
The two concepts Master/Replica (Slave) and Primary/Secondary are independent of each other.
Master/Replica (Slave) concept pertains to database replication and Primary/Secondary pertains to
PSX redundancy for a GSX.
FIGURE 3-1. Possible Network Setup (Master/Replica)
Customer Sonus
OSS Insight PSX with
Master Database
PSXs with Replica

(Slave) Databases GSX
GSX
...
GSX
GSX GSX Primary
GSX Secondary
To upgrade the PSX Software, you need to take the PSX out of service. In a redundant setup with
multiple PSXs you first need to upgrade the PSX hosting the master database. We recommend to
force a database replication prior to an upgrade, but during an upgrade replication must be
disabled.
PSX Upgrade Overview PSX Software Upgrade
Because PSX servers must be taken out of service to upgrade the software, it is necessary to
reconfigure the primary and secondary PSXs for the GSXs to retain PSX/GSX redundancy. This
configuration is done on the GSX.
FIGURE 3-2. Redundant Network set up, normal operation
Primary
Secondary
PSX A PSX B PSX n
...
GSX4
GSX1 GSX2
The 5 top rows of the table below indicate the primary/secondary specifications during normal
network operations. The following rows indicate the necessary changes to particular GSXs if
either the PSX server A or B is taken out of service for an upgrade. The bold typeface primary or
secondary indicate the new GSX configuration.
TABLE 3-1. GSX—PSX: Primary/Secondary switch over
Primary/Secondary PSX A PSX B PSX n

GSX1 primary seconday —
GSX2 secondary primary —
GSX3 — primary secondary
GSX4 — secondary primary
Upgrade PSX A
GSX1 — secondary primary
GSX2 — primary secondary
Upgrade PSX B
GSX1 primary — secondary
GSX2 secondary — primary
GSX3 primary — secondary
GSX4 secondary — primary
PSX Software Upgrade PSX Upgrade Overview
FIGURE 3-3. PSX Software Upgrade Overview Chart
START with Master PSX
Make sure all replicated PSX

databases are current and then You need to stop the automated
stop the replication for all replica database replication on the
PSXs. replica (slave) PSXs.
If a GSX is using this policy

server as either a primary or
secondary PSX, change the data
to point to another policy server.
If you are performing a software

upgrade from a version prior to
V04.00 you need to also upgrade
your Solaris OS to release 8.
Apply latest Solaris OS cluster With release V04.01 the Process
patch Management feature has changed. The
process management and device
configuration data, previously prompted for
during an installation or provisioned by
Upgrade PSX Software editing ASCII text files, is now provisioned
using the GUI and stored in database
tables. Once you have provisioned the
data based on this new design, the data
Upgrade PSX Database will be migrated in future releases.
Refer to the "Process Management"
chapters in the PSX Product Description
and in the PSX Provisioning Guide.
OPTIONAL STEP
SNMP Notification for Oracle DB
Installing the necessary packages
Restart PSX and Test
If you use the Service Profile

On the GSX change the Editor (SPE) you also need to
configuration to point back to this update the SPE Application on
policy server as either a primary your Windows PC to be able to
or secondary PSX. use the latest script features.
YES Are there any

other PSXs that need an
upgrade?
NO
END
Prerequisites for the PSX Software Upgrade PSX Software Upgrade
Prerequisites for the PSX Software Upgrade
The following procedures detail the prerequisite steps for the PSX software upgrade.
Reconfiguring GSX Primary and Secondary PSXs
Because PSX servers must be taken out of service to upgrade the software, it is necessary to
reconfigure the primary and secondary PSXs for the GSXs to retain PSX/GSX redundancy. As this
is done, make sure that the PSXs have enough capacity to handle the additional GSXs and balance
the load. See Table 3-1 on page 3-3 for an example.
Procedure
Perform the following procedure on each GSX that is connected to the PSX. We are using PSX A
and GSX 1 as an example for the configuration.
Switching GSX1 to other policy server, example upgrading PSX A:
Step Action
1. Log on to the GSX 1.
2. To switch GSX 1 back automatically after PSX A is upgraded, enter the following
command:
% CONFIGURE SONUS SOFTSWITCH SWITCHOVER AUTOMATIC.
3. If you want to verify that the automatic switchover is configured, enter the following
command:
% SHOW SONUS SOFTSWITCH SWITCHOVER
4. To upgrade PSX A you need to make it a standby policy server and take it out of
service, enter the following command lines:
% CONFIGURE SONUS SOFTSWITCH <PSX A> MODE STANDBY
% CONFIGURE SONUS SOFTSWITCH <PSX A> MODE OUTOFSERVICE
Substitute PSX A with the real name of your policy server.
5. Verify that the GSX is switched over to another PSX, type:
% SHOW SONUS SOFTSWITCH ALL STATUS
6. Log off from the GSX, type:
exit
After the PSX upgrade is complete and the PSX is restarted, the original state is restored
automatically.
PSX Software Upgrade Prerequisites for the PSX Software Upgrade
Synchronize the Databases between Master and Replica PSX systems
Before updating the software on the Master PSX, execute a forced data replication and then stop
the automatic replication intervals at the replica database, if configured.
Procedure
Synchronizing Master and Replica PSX Databases
Step Action
1. Log on to the PSX hosting the replicated database as ssuser.
2. Force a replication:
sqlplus dbimpl/dbimpl
exec dbms_refresh.refresh (‘REFGRP1’);
This command causes a replication of all the data changes that have occurred since
the last replication. The replication can take up to 30 minutes. Please wait for the
replication to finish.
3. Disable any automatic replication setup to prevent replication attempts during the
software update:
sqlplus dpimpl/dpimpl
select job from user_refresh where rname=’REFGRP1’;
exec dbms_job.remove(number);
For number substitute the return value from the select job entry.
Updating the PSX Software PSX Software Upgrade
Updating the PSX Software
The following procedure details the steps for the PSX software upgrade.
PSX Software Upgrade Procedure
Step Action
1. Log on to the PSX hosting the master database as ssuser.
2. Perform a database backup, type:
cd SOFTSWITCH/SQL
export filename.ext
For filename.ext substitute a real name and do not forget the extension. If you
do not specify an extension, the script will add .dmp as a default extension. If you
need to restore the database from the backup, use the import command and
provide the complete file name including extension.
3. Save the backup file to a directory other than SOFTSWITCH, use the cp or mv
command to do so.
4. To log the upgrade procedure to a file, type:
script filename
Substitute filename with a name for the script. To stop logging at any time, press
Ctrl-D.
5. Copy the following PSX files from the distribution CD to the /export/home/
ssuser directory:
• SONScia.pkg
• psxInstall.sh
• ss-V04.01.00Rxxx.pkg
Where the xs are placeholders for the actual release version number.
6. Stop the PSX, type:
stop.ssoftswitch
7. Change your log on to root to continue the software update.
8. Remove earlier PSX versions. Execute the following commands based on your
currently loaded software:
• V03.02.xx or earlier: pkgrm SONSss and enter y to confirm the system message.
• V03.03.xx or later: ./psxUninstall.sh (located in SOFTSWITCH/BIN).
The command removes all files and directories created when the PSX was installed,
but does not delete files created by the user. Sonus recommends that you check the
PSX install base directory and manually delete any remaining files and directories.
PSX Software Upgrade Updating the PSX Software
Step Action
9. Install the PSX package, enter
./psxInstall.sh
and press Return.
10. At the prompt
(default: /export/home)
Enter the default and press Return.
Would you like to restore your CIAgent configuration from a
previous CIAgent install? (default: Y) [y|Y,n|N]:
If your previous version was less than 4.0, type n and press Return.
If your PSX Policy Server is currently a registered node within Insight, you will need
to select "Enable Monitoring" from the Insight Node Administration page for this
node in order to ensure it is being fully monitored.
If your previous version was 4.0 or greater, type y and press Return.
• If you are installing in the same directory as your previous install the following
prompt should appear:
/export/home/ciagent/ciagent_configFiles.tar exists in the
base directory you selected.
configuration? (default:Y) [y|Y,n|N]
Type y and press Return.
• If you are installing in a different directory as your previous install the following
prompt should appear:
Please enter the path to the directory that contains
ciagent_configFiles.tar you wish to use to restore from:
Enter the path (i.e. /export/home/ciagent ) and press Return.
This package contains scripts which will be executed with
super-user permissions during the process of installing this
package.
Do you want to continue with the installation of <SONScia>
[y,n,?]
The PSX installation setup script installs the CIAgent software. When completed, the
following message appears:
Installation of <SONScia> was successful.
Updating the PSX Software PSX Software Upgrade
Step Action
13. The PSX installation setup script confirms the default directory location and then
displays the following text:
Please enter the information to identify the Sonus SoftSwitch
User/Installer:
User Name (default:ssuser)...
Group Name (default: ssgroup)...
If the values are correct, type y and press Return. If the values are not correct, type n
and press Return to correct the values.
14. The system displays the following prompt:
Do you want to automatically start the Sonus SoftSwitch on
system startup [y|Y,n|N]?
Sonus recommends that you type y and press Return.
This creates a startup script file in the /etc/rc2.d directory. The startup script is
executed when the system starts. It will start the PSX Process Manager, which in turn
starts up the other programs. Because the PSX programs use the Oracle Database,
the Oracle instance must be running before the PSX programs can successfully run.
Typing y to this prompt ensures that the right start up sequence is followed.
If you type n to this prompt, you must manually start the PSX programs after the sys-
tem has been restarted.
Do you want to automatically stop the Sonus SoftSwitch on
system shutdown?
Sonus recommends that you type y and press Return.
This creates a shutdown script file in the /etc/rc0.d directory. This file is executed
when the system shuts down and it stops the PSX Process Manager, which will in turn
shutdown the other programs. Typing y to the prompt ensures that the right shut down
sequence is followed.
If you type n in response to this prompt, Sonus strongly recommends that you manu-
ally shutdown the PSX programs before you shutdown the system.
Please enter the information to configure some Sonus
SoftSwitch processes:
Name of the host where the PES will be run...
Type the host name of the machine on which you are installing this package.
The host name does not need to be fully qualified, but it must be a valid network name
for the system. Meaning, if you type ss1host, you must be able to use the following
commands successfully from other machines on this network, i.e. telnet
ss1host or ping ss1host.
PSX Software Upgrade Updating the PSX Software
Step Action
You entered...
PES Host Name: “ss1host”
• If the name is correct, type y and press Return.
• If the name is not correct, type n and press Return. The system prompts you to
enter the host name again.
18. The system starts processing and displays pes related status messages. The
following is a excerpt of what to expect at the monitor:
Auto-computing PES parameters, number of threads & database
connections.
Default number of threads is 2.
...
...
Enter path to package base directory [?,q]
Enter the directory path (default):
/export/home/ssuser
The following files are already installed on the system and
are being used by another package:
* /export/home/ssuser/SOFTSWITCH/BIN <attribute change only>
* /export/home/ssuser/SOFTSWITCH/LIB <attribute change only>
* - conflict with a file which does not belong to any package.
Do you want to install these conflicting files [y,n,?,q]
##Checking for setuid/setgid programs.
This package contains scripts which will be executed with
super-user permission during the process of installing this
package.
Do you want to continue with the installation of <SONSss>
[y,n,?]
The directories and files are created in the SOFTSWITCH directory under /
export/home/ssuser (the path name of package base directory). In the
SOFTSWITCH directory, other directories and files are created and some permissions
are set.
22. When the upgrade is complete, the system displays the following:
Installation of <SONSss> was successful.
Upgrading the Database on the Master PSX PSX Software Upgrade
Upgrading the Database on the Master PSX
This topic provides instructions on upgrading the database on the master PSX.
For instruction on installing the Oracle8 Server see the PSX Policy
Server Installation Guide.
During the following procedure, you have to run the UpdateDb script. The UpdateDb script
prompts you for information and eventually migrates the database. It does that in three main steps,
as follows:
1. You execute the UpdateDb script as root user. The UpdateDb script collects information from
you, backs up directories, etc. It then starts the MigrateDb script, providing it with the correct
arguments.
2. You execute the MigrateDb script as oracle user. MigrateDb is a Perl script. It will also prompt
you for some information and will then migrate the database.
3. After the MigrateDb script has completed successfully, the UpdateDb script will update the
pes.config file with the correct database passwords.
Update/Migrate the Master Database
The following procedure details the steps of a database upgrade/migration.
Procedure
Performing an Upgrade on a PSX Master Database:
Step Action
1. Log in as root.
2. To log the database creation enter the following:
script UpdateDb
To stop the logging press Ctrl-D.
3. Enter the following command to start the UpdateDb script. The command syntax
below assumes that the PSX package is installed at /export/home/ssuser/
SOFTSWITCH.
# cd /export/home/ssuser/SOFTSWITCH/SQL
# sh ./UpdateDb
PSX Software Upgrade Upgrading the Database on the Master PSX
Step Action
4. The system displays the following:
chmod 777 /export/home/ssuser/SOFTSWITCH/SQL/UpdateDb.log
Enter the requested information for the Oracle User/
Installer....
User Name (default: oracle)...
Type the User Name and press Return
Group Name (default: dba)...
Type the Group Name and press Return.
You entered...
User Name: “oracle”
Group Name: “dba”
Are the values correct (default:N) [y|Y,n|N] ?
If the SSDB Oracle instance is running, it is announced at this time and this script will
be terminated. You must stop the SSDB instance and start over again with ./InstallDb.
Enter the Sonus SoftSwitch’s config file name (default:
pes.config)...
Press Return to accept the default file name.
Enter the fully-qualified path where the “orasql” directory
was created...
(default: /export/home)...
Press Return to accept the default path.
This directory, along with the oradata directory, is created when the database is first
created. Make sure that you enter the same path that you entered when you initially
installed the software. By default /export/home.
8. The system displays processing and status messages. The following is just an
excerpt:
Creating a tar file of the "/export/home/orasql/SSDB"
directory.....
tar cvf /export/home/orasql/SSDB020426155141.tar -C /export/
home/orasql SSDB
a SSDB/ 0K
...
...
A tar file named "SSDB020426155141.tar" has been created.
IF the database upgrade FAILS, use the file to recreate
the "/export/home/orasql/SSDB" directory.
Step Action
rm -r -f /export/home/orasql/SSDB/*
cp /export/home/ssuser/SOFTSWITCH/SQL/* /export/home/orasql/
SSDB
chown oracle:dba /export/home/orasql/SSDB/*
chmod 770 /export/home/orasql/SSDB/*
Enter the requested information to upgrade the database...
Migration until schema version 41A009
Master or Snapshot database (default:M) [m|M,s|S]...
Enter m and press Return to specify this as an upgrade to a master database.
Debug Level (default:1) [0|1|2]...
Enter the value for the debug level you want to apply.
A debug level of 0 produces a minimum amount of information in the log files. Debug
level 1 has more information and is the recommended value to use. Debug level 2
preserves temporary files created by the MigrateDb script. You should specify level
2 only if the database creation repeatedly fails.
The debug level applies only to the MigrateDb script. When the MigrateDb script
runs, it produces two log files, MigPrlLogFile and MigSqlLogFile. The
MigPrlLogFile holds the overall run status of the MigrateDb script. The
MigSqlLogFile holds the responses from the SQL commands used to create the
databases. These log files are in the directory /export/home/orasql/SSDB.
You entered...
Migrating to schema version: 41A009
Migration script: migrate.sql
Master or Snapshot database: "M"
Debug Level: "1"
Are the values correct (default:N) [y|Y,n|N] ?
The displayed Migration schema version 41A009 is for information only and is not the
build (package) version. Respond with y and press Return to accept the displayed
values.
12. At this point the UpdateDb script starts the MigrateDb script. The MigrateDb
proceeds with the database update/migration.
su - oracle -c "cd /export/home/orasql/SSDB; perl ./MigrateDb
-n -l1 -m41A009"
Sun Microsystems Inc. SunOS 5.8 Generic February 2000
A couple more status messages are displayed.
PSX Software Upgrade Upgrading the Database on the Master PSX
Step Action
Enter Country ID (default: 1 for US)
Press Return to accept the default or enter the appropriate value for you installation.
For user "Dbimpl", UserId = "dbimpl" & Password = "dbimpl".
Change ? ( default:N)
• Enter n if the database password for user Dbimpl has not changed from its
default value, as listed above.
• Enter y if the database password of user Dbimpl has changed from its default
value. This response allows you to add the changes to the MigrateDb script, so
that it can use them when connecting to the database to do the migration.
If your response was y, the following prompt appears:
Enter password
For user "Sys", UserId = "sys" & Password =
"change_on_install". Change ? ( default:N)
• Enter n if the database password for user Sys has not changed from its default
value, as listed above.
• Enter y if the database password of user Sys has changed from its default value.
This response allows you to add the changes to the MigrateDb script, so that it
can use them when connecting to the database to do the migration.
Enter password
For user "System", UserId = "system" & Password = "manager".
• Enter n if the database password for user System has not changed from its
• Enter y if the database password of user System has changed from its default
Enter password
Step Action
17. On master databases only, following the password change prompt, you are asked, if
you want to perform a database back up.
Perform a database backup? (Default: Y) [y|Y,n|N]
To perform a backup, accept the default by pressing Return. The system confirms
with the following output:
Backing up database to /export/home/orasql/SSDB/DbBackup.dmp
If you do not want to perform a backup, press n and Return.
A couple of status messages are displayed.
18. The upgrade starts automatically. The upgrade checks the database and installs
whatever schema version has not been installed. Any errors in the log file that specify
that version has already been installed can be ignored. If no errors occur, the following
message appears:
The MigrateDb script has completed successfully. the database
upgrade is complete.
If an error occurs, the MigrateDb script stops. The errors can be seen in the log
files. To fix any errors, you will need the help of Sonus’ Customer Support Center.
PSX Software Upgrade Update/Migrate the Slave (Replica) Database
Update/Migrate the Slave (Replica) Database
The following procedure details the steps of a replica database upgrade/migration.
Procedure
Performing an Upgrade on a PSX Replica Database:
Step Action
1. Log in as root.
2. Assuming that the PSX package base directory is /export/home/ssuser, type
the following:
sh /export/home/ssuser/SOFTSWITCH/SQL/UpdateDb
Enter the requested information for the Oracle User/
Installer...
User Name (default: oracle)...
Press Return to accept the default (oracle).
Group Name (default: dba)...
Press Return to accept the default (dba).
5. The system displays the entered values again and prompts for confirmation. Respond
with y and Return to accept the displayed values. If you want or need to correct the
values respond with n and Return.
Enter the Sonus SoftSwitch’s config file name (default:
pes.config)...
Press Return to accept the default file name.
Enter the fully-qualified path where the “orasql” directory
was created...
(default: /export/home)...
Press Return to accept the default path.
This directory, along with the oradata directory, is created when the database is first
created. Make sure that you enter the same path that you entered when you initially
installed the software. By default /export/home.
Enter the requested information to upgrade the database...
Master or Snapshot database (default: M) [m|M, s|S]....
Type s and press Return to specify the snapshot (slave db) upgrade.
Update/Migrate the Slave (Replica) Database PSX Software Upgrade
Step Action
Debug Level (default: 1) [0|1|2]....
Enter the value for the debug level you want to apply.
A debug level of 0 produces a minimum amount of information in the log files. Debug
level 1 has more information and is the recommended value to use. Debug level 2
preserves temporary files created by the MigrateDb script. You should specify level
2 only if the database creation repeatedly fails.
The debug level applies only to the MigrateDb script. When the MigrateDb script
runs, it produces two log files, MigPrlLogFile and MigSqlLogFile. The
MigPrlLogFile holds the overall run status of the MigrateDb script. The
MigSqlLogFile holds the responses from the SQL commands used to create the
databases. These log files are in the directory /export/home/orasql/SSDB.
You entered...
Migrating to schema version 41A009
Debug Level: “1”
Are these values correct? (default: N) [y|Y,n|N]
The displayed Migration schema version 41A009 is for information only and is not the
build (package) version. Respond with y and press Return to accept the displayed
values.
At this point the UpdateDb script spawns the MigrateDb script. The MigrateDb
proceeds with the database update/migration.
Enter Country ID (default: 1 for US)
Press Return to accept the default or enter the appropriate value for you installation.
For user "Dbimpl", UserId = "dbimpl" & Password = "dbimpl".
• Enter n if the database password for user Dbimpl has not changed from its
• Enter y if the database password of user Dbimpl has changed from its default
Enter password
PSX Software Upgrade Update/Migrate the Slave (Replica) Database
Step Action
For user "Sys", UserId = "sys" & Password =
"change_on_install". Change ? ( default:N)
• Enter n if the database password for user Sys has not changed from its default
value, as listed above.
• Enter y if the database password of user Sys has changed from its default value.
This response allows you to add the changes to the MigrateDb script, so that it
can use them when connecting to the database to do the migration.
Enter password
For user "System", UserId = "system" & Password = "manager".
• Enter n if the database password for user System has not changed from its
• Enter y if the database password of user System has changed from its default
Enter password
Please enter the following information for this database:
Fully qualified name of Master db system...
Type the fully qualified name of the Master system.
Service name for the master system (default: masterdb)
To accept the default press Return, or enter another name and press Return.
Update/Migrate the Slave (Replica) Database PSX Software Upgrade
Step Action
Replication Interval?
Specify the replication interval and press Return. The replication interval determines
the frequency at which the slave database enters a data replication with the master
database.
The divisor represents the number of times per day to perform the replication.
• 1/288 data replication every 5 minutes (used in this example)
• 1/96 data replication every 15 minutes
• 1/48 data replication every 30 minutes
• 1/24 data replication every hour
Setting the replication interval to short could result in the PSXs continually attempting
to update themselves, which could cause management problems. Please consult
Sonus’ Customer Support Center, if you are not sure about the right interval
specification for your network setup.
Enter dbimpl user password on master db.
Enter the password and press Return. The password is not displayed back.
19. The system asks you to confirm the values you entered:
You entered...
Fully qualified name of the master db system:
“host.domain.com”
Service name for the Master system: “masterdb”
Replication interval: “1/288”
Are the values correct (default N) [y|Y, n|N]
Enter y to accept the values or n to go back and correct them.
20. The upgrade starts automatically. The upgrade checks the database and installs
whatever schema version has not been installed. Any errors in the log file that specify
that version has already been installed can be ignored. If no errors occur, the following
message appears:
The MigrateDb script has completed successfully. the database
upgrade is complete.
If an error occurs, the MigrateDb script stops. The errors can be seen in the log
files. To fix any errors, you will need the help of Sonus’ Customer Support Center.
PSX Software Upgrade Upgrading the PSX Manager Software
Upgrading the PSX Manager Software
Usually the PSX Manager is upgraded automatically when you perform the Insight software
upgrade. However, under certain circumstances you might want to upgrade to a newer version of
the PSX Manager without upgrading Insight. In that case, you can perform a PSX Manager
upgrade independently.
An upgrade of the PSX software always requires an updated PSX Manager version, to be able to
utilize all feature additions and changes. If you did not update Insight to the new software version,
follow the procedure below to update the PSX Manager independently.
Procedure
Upgrading the PSX Manager independent from Insight:
Step Action
1. Place the PSX Policy Software CD in the DC-ROM drive.
2. As super user, enter the commands as follows:
cd /cdrom/cdrom0
version_number/SSGUI/GuiClient.sh
Substitute version_number in above’s commandline with the new PSX version
you installed.
For example: V04.01.00R000/SSGUI/GuiClient.sh
PSX Database Upgrade and Numbering Plans PSX Software Upgrade
PSX Database Upgrade and Numbering Plans
This topic only applies to systems that are updated from a PSX release version prior to V04.00.
Prefix profiles is a highly flexible method for provisioning both National/International dial plans
and private dial plans. Although provisioning numbering plans using regular expressions
continues to be supported, it is suggested that you migrate existing numbering plans to be based on
prefix profiles.
When you update the PSX database from a release prior to V04.00, numbering plans containing
regular expressions are automatically converted to numbering plans that use prefix profiles
following the process explained below. With release V04.00, Sonus changed the
NUMBERING_PLAN table to use the PREFIX_TRANSLATION table for a number of entries.
Please check /export/home/orasql/SSDB/MigSqlLogFile for accuracy.
The following logic has been used in the numbering plan migration. Sonus seeds the following
numbering plans as part of the package:
• NANP_ACCESS
• NANP_IXC
During the database migration, for each row in the NUMBERING_PLAN table, the value of
NUMBERING_PLAN_ID and the values in the Regular Expression (RE) columns are examined to
do the migration as follows:
1. If the NUMBERING_PLAN_ID is either NANP_ACCESS or NANP_IXC and the data in the

RE columns is the same as what Sonus had seeded, the row is changed to use
PREFIX_TRANSLATION. The following message appears in the log file:
Numbering plan ID 'NANP_IXC' is being migrated.
2. If the NUMBERING_PLAN_ID is either NANP_ACCESS or NANP_IXC and the data in the

RE columns is not the same as what was seeded, the row is changed to use
PREFIX_TRANSLATION. The following message appears in the log file:
Numbering plan ID 'NANP_IXC' was seeded, but the data has been changed.
Please note that numbering_plan_id 'NANP_IXC' is being migrated to use prefix
translation.
3. If the NUMBERING_PLAN_ID is neither NANP_ACCESS nor NANP_IXC , but the data in the
RE columns is the same as what was seeded for NANP_ACCESS or NANP_IXC , the row is
changed to use PREFIX_TRANSLATION. The following message appears in the log file:
Numbering plan ID 'NANP_IXC_BAK' is being migrated.
4. If the NUMBERING_PLAN_ID is neither NANP_ACCESS nor NANP_IXC, and the data in the
RE columns is not the same as what was seeded for NANP_ACCESS or NANP_IXC, then the
row is not changed to use PREFIX_TRANSLATION. The following message appears in the
log file:
Numbering plan ID 'test_plan' Was not seeded, and will not be changed. Please
contact Sonus personnel to have this changed to use prefix translation.
PSX Software Upgrade Process Management
Process Management
In release V04.01 the Process Management feature is redesigned. The process management
implementation changed from using the process manager file to a database and GUI based
provisioning for the information.
If you had SCPA, PGK, or SIPE process data provisioned via the “procfile”, you need to enter
that data through the GUI to manage the processes. Please refer to the “Process Management”
chapter in the PSX Product Description and in the PSX Provisioning Guide.
CHAPTER 4 SGX SS7 Gateway Software
Upgrade
Overview
If you are upgrading your system software, it is very important to upgrade the different Sonus
components in the following order:
• Sonus Insight EMS,

• Sonus PSX Policy Server,
• Sonus SGX SS7 Gateway, and
• Sonus GSX9000 Media Gateway.
Although the SGX upgrade instructions are not part of this System Software Upgrade Guide, it is
mandatory to first attend to the SGX software upgrade before you advance to the GSX9000
upgrade.
For SGX upgrade instructions, please refer to the following document:
• SGX SS7 Gateway Introduction and Installation Guide, which is included on your
documentation CD. Also visit the Sonus FTP site for a download of the latest version of the
SGX documents.

SGX SS7 Gateway Software Upgrade
CHAPTER 5 GSX9000 Software Upgrade
Overview
This section provides information about upgrading GSX system software.

• "GSX9000 Software Upgrade Overview" on page 5-2
• "NFS Server Upgrade Solaris 2.6 to 8" on page 5-5
• "GSX9000 Software Upgrade Procedures" on page 5-6
• "Installing New Firmware on Each Module" on page 5-9
• "Loading GSX9000 Software" on page 5-11

GSX9000 Software Upgrade GSX9000 Software Upgrade Overview
GSX9000 Software Upgrade Overview
The GSX9000 software is installed on the NFS servers into the GSX system tree for each
GSX9000. The layout of the GSX system tree is shown in Figure 5-1. One of these file hierachies
must be present on an NFS server for each GSX in the network.
Beginning with software version V04.00, you must upgrade the NFS server to Solaris 8 prior to
upgrading the GSX software.
Beginning with GSX9000 software Version V04.00.02, you may perform a Live Software
Upgrade (LSWU). The LSWU allows you to upgrade the GSX software without dropping active
calls. A complete description of the LSWU procedure is presented in the GSX Operations
Guide, Version 4.01, Document Version 1, Chapter 4. The requirements and restrictions
pertaining to LSWU are detailed in that Sonus reference. The LSWU decision point, in the context
of this document, occurs in "Loading GSX9000 Software" on page 5-11.
/export/SonusNFS mount-point
/<BASEDIR> boot path

GSX9000 Software Upgrade Overview
FIGURE 5-1. GSX System Tree

/evlog /announcements /<SOFTWPTH> /<-----> /<----->
software release directory
System Software Upgrade Guide - 550-00206 - 1.0

/<NODEID> /preload /ondemand /coredump /cli /param /images
*.wav *.wav core.* *.prm mns10.bin
*.bck cns10.bin
pns10.bin
cns30.bin
.
.
/DBG /SYS /TRC /ACT /sys /scripts /logs

*.DBG *.SYS *.TRC *.ACT commands.def *.tcl sysinit.tcl.out
showscreens.sda sysinit.tcl.out.last
sysinit.tcl
sessinit.tcl
alarmUtils.tcl
.
.
GSX9000 Software Upgrade
5-3
GSX9000 Software Upgrade GSX9000 Software Upgrade Overview
Firmware Versions
To run GSX9000 Version V04.01.00R000 software, GSX9000 boot PROMs on all server modules
must be at Version V01.08.00R001. To determine the boot PROM Firmware Version of a server
module residing in slot n, type the command:
SHOW SERVER SHELF 1 SLOT n STATUS
If your PROMs are earlier than V01.08.00R001, you must upgrade your firmware. See "Installing
New Firmware on Each Module" on page 5-9.
GSX9000 Product Compatibility
TABLE 5-1. Product Compatibility
Version(s) of PSX
Policy Server Version(s) of Insight Version(s) of SGX
software that may software that may software that may
Version of GSX9000 execute compatibly execute compatibly execute compatibly
software that is with the GSX9000 with the GSX9000 with the GSX9000
executing software1 software1 software
V04.00.00 V04.00.00 V04.00.00 For information on
compatible SGX
V03.04.xx V03.04.xx or higher V03.04.xx or higher2 software, please refer
to the Introduction
V03.03.xx V03.03.xx or higher V03.03.xx or higher2 chapter in the SGX
Installation, Upgrade
V03.02.xx V03.02.xx or higher V03.02.xx or higher2 & Operations Guide.
1
Backward compatibility allows for the older release features to continue working with the newer product. However,
the newer release’s features will not be available until all the products that are part of providing the feature are upgraded.
2
The version of the Insight software needs to be the same as or higher than the version of the PSX software.
NFS Server Upgrade Solaris 2.6 to 8 GSX9000 Software Upgrade
NFS Server Upgrade Solaris 2.6 to 8
Beginning with software version V04.00, you must upgrade the NFS server to Solaris 8 prior to
upgrading the GSX software.
See the Sun Microsystems Solaris documentation for complete installation instructions. The
information in the Introduction chapter of this guide is a supplement to the Solaris installation
instructions as documented in the Solaris Installation Manual. All information regarding settings
and selections in this procedure might vary from settings and selections necessary for your
location and system.
Refer to "Upgrade a Solaris 2.6 Operating System to Solaris 8" on page 1-6 for detailed
complimentary instructions on updating your Solaris Operating System from version 2.6 to 8.
GSX9000 Software Upgrade GSX9000 Software Upgrade Procedures
GSX9000 Software Upgrade Procedures
Perform the following procedures for all software upgrades of the GSX9000 software. These
procedures assume that your current GSX9000 software is Version 3.02.xx or higher.
This procedure also requires that your NFS file server have a UNIX account ID of gsx (integer ID
= 1036) with a group ID of gsx (integer ID = 101) already installed. Typically, this account is
factory installed by Sonus before the NFS server is shipped.
In the following procedures, for commands that continue on more than one line, the ^ character
appears at the end of the line to represent a space between the characters before it and the
characters after it.
The procedures in this section are prerequisites for loading and executing the GSX software.
Those procedures and considerations, including use of LSWU, are presented in "Loading
GSX9000 Software" on page 5-11.
Installing the Software to the GSX System Tree
Perform these steps regardless of whether or not you will use LSWU to load and execute this new
GSX software. (The example commands use Version V04.00.02R001 as the release that you are
upgrading from. Substitute your actual current release whenever you see that string in the example
commands.)
1. Log on to a system that has access to your primary NFS file server and gain super-user
privileges.
> su
Password:
2. Change directory to your GSX9000 mount point directory. The example mount point /export/
home/SonusNFS, below, is used throughout this procedure.
# cd /export/home/SonusNFS
3. Insert the GSX9000 software CD into the CD-ROM drive of your NFS system, and verify its
contents:
# ls /cdrom/cdrom0
announcements
FLASH
GSX.V04.01.00R000.tar.Z
V04.01.00R000
GSX.V04.01.00R000.readme
4. Create a tmp directory under your mount point directory:
# mkdir tmp
GSX9000 Software Upgrade Procedures GSX9000 Software Upgrade
5. Change directory to the tmp directory:

# cd tmp
6. Do one of the following:
a. If you are performing the upgrade using the GSX9000 software CD, copy the file
GSX.V04.01.00R000.tar.Z from the CD to the tmp directory:
# cp /cdrom/cdrom0/GSX.V04.01.00R000.tar.Z ./
b. If you are performing the upgrade using the GSX9000 software *.tar file, obtain the
compressed *.tar file and copy it to the tmp directory. For more information, contact Sonus
Customer Support.
7. Uncompress and untar the GSX9000 distribution software:
# zcat GSX.V04.01.00R000.tar.Z | tar xvf -
8. Change directory to the distribution base directory (below your temporary directory):
# cd GSX9000
9. Copy the new GSX9000 software into each GSX Software Release directory, identified below
by GSXn/V04.01.00R000, and repeat this step as many times as necessary:
# cp -pR V04.01.00R000 /export/home/SonusNFS/GSXn
10. Copy the new boot PROM program images to the images subdirectory in the new GSX system
tree (in case they are needed in the future):
# cp -p FLASH/V01.08.00R001/*.bin^
/export/home/SonusNFS/GSXn/V04.01.00R000/images
11. Copy the new boot PROM program images to the images subdirectory in the current GSX
system tree (to be used to install new firmware as described in the next section).
# cp -p FLASH/V01.08.00R001/*.bin^
/export/home/SonusNFS/GSXn/V04.00.02R001/images
12. Copy any parameter and script files that you need from the current GSX system tree to the new
GSX system tree in the GSX Software Release directory.
Enter the following commands:

# mkdir -p /export/home/SonusNFS/GSXn/V04.01.00R000/param
# mkdir -p /export/home/SonusNFS/GSXn/V04.01.00R000/cli/scripts
# cp -p /export/home/SonusNFS/GSXn/V04.00.02R001/param/*.prm^
/export/home/SonusNFS/GSXn/V04.01.00R000/param
# cp -p /export/home/SonusNFS/GSXn/V04.00.02R001/cli/scripts/*.tcl^
/export/home/SonusNFS/GSXn/V04.01.00R000/cli/scripts
#cp-p/export/home/SonusNFS/GSXn/V04.00.02R001/cli/sys/sysinit.tcl^
/export/home/SonusNFS/GSXn/V04.01.00R000/cli/sys
# cp -p /export/home/SonusNFS/GSXn/V04.00.02R001/cli/sys/sessinit.tcl^
/export/home/SonusNFS/GSXn/V04.01.00R000/cli/sys
13. Verify that the images subdirectory in the GSX system tree has the new files with the current
date, and repeat this step for other directories as necessary:
GSX9000 Software Upgrade GSX9000 Software Upgrade Procedures
# ls -lu /export/home/SonusNFS/GSXn/V04.01.00R000/images
-rw-rw-r-- 1 1036 101 4793748 May 11 16:43 cns10.bin
-rw-rw-r-- 1 1036 101 2083232 May 11 16:43 cns10b.bin
-rw-rw-r-- 1 1036 101 4717060 May 11 16:43 cns20.bin
.
.
14. Repeat Steps 10-13 for each GSX9000 that you are upgrading.
15. Remove the tmp directory from your NFS server:
# cd /export/home/SonusNFS
# rm -fr tmp
16. Remove the CD from the CD-ROM drive.
# eject
17. Repeat the previous steps for the secondary NFS, if applicable.
You can find the latest sample announcement files on the GSX9000
distribution CD in the /announcements directory, which is at the same
level in the directory structure as the Software Path directory. If
needed, copy these files into the directories under the /announcements
directory in the GSX system tree (for example, GSXn/announcements/
ondemand or GSXn/announcements/preload).
If a firmware upgrade is necessary (see "Firmware Versions" on page 5-4), proceed to the next
section.
Installing New Firmware on Each Module GSX9000 Software Upgrade
Installing New Firmware on Each Module
Before you perform the following procedure, you must perform the
procedure in the previous section, "Installing the Software to the GSX
System Tree."
You are now ready to upgrade each module's boot PROM to Version V01.08.00R001. This
procedure must be performed on each server module in each GSX9000. Ensure that every server
module in the GSX9000 is enabled. Place the GSX9000 in a quiescent state to carry out this
procedure. The GSX9000 must not be reset or switched over at any time during this procedure
(except as intended in Step 4 below). If a reset does occur while upgrading boot PROMs, contact
Sonus Customer Support for further instructions.
1. Telnet to the first GSX9000, log on, and verify that the current firmware is V01.02.00R002 (or
later):
# telnet 128.22.1.162
2. The following messages appear:
Trying 128.22.1.162...
Connected to 128.22.1.162.
Escape character is '^]'.
GSX9000 (128.22.1.162)
V0X.XX.X R00X
At the following prompts, enter the login name and password:
Login: admin
Password: *******
Log on to the GSX as shown above.
3. Determine whether the V01.08.00R001 firmware is now resident on the next server module by
entering the following show command:
% SHOW SERVER SHELF 1 SLOT n STATUS
where n is the slot number, beginning with 1 (or the MNS10/MNS11 server module in slot 1).
The following is sample output for this command:
Node: TPUBS Date: 2000/11/28 05:52:47 GMT
Zone: GMTMINUS05-EASTERN-US
Shelf: 1
Slot: 1
GSX9000 Software Upgrade Installing New Firmware on Each Module
Hardware Type: MNS10

Hardware Type Rev: 0
EPLD Rev: 0
Part Number: 810-00120
Part Number Rev: 12
Manufacture Date: 3/22/2001
Serial Number: 0211018004
Software Version: V04.01.00 R000
Firmware Version: V01.08.00 R001
Redundancy Mode: ACTIVE
Temperature: 25C
Memory Utilization: 40%
Total Memory Size: 0x3400000
Total Shared Memory Size: 0x2000000
Total Available Memory Size: 0x1ed0910
Total Available Shared Memory Size: 0x25bea0
CPU Utilization: 2%
If the Firmware Version is V01.08.00 R001, the firmware is current and you should
skip ahead to Step 5. If Firmware Version is less than V01.08.00 R001, execute
Step 4 to update the firmware on this module.
4. Type the following command,

% CONFIGURE SERVER FLASH SHELF 1 SLOT n UPDATE NOW
where n is the slot number used in the show command in Step 3. You will be immediately
prompted to confirm your intent to rewrite this device:
Erase and Program Boot PROM FLASH Device - Confirm (Y/N): Y

Confirm the command as shown and then await the completion of the update by monitoring
the progress of the command:
% MONITOR SERVER FLASH SHELF 1 SLOT n STATUS
This causes the status display to be continuously refreshed. When the State becomes IDLE,
type CTRL-C to terminate this command. Repeat the show command from Step 3 to confirm
that the Firmware Version is now V01.08.00 R001.
5. Repeat Step 3 using an incremented slot number until all 16 slots have been examined and
updated as necessary.
6. Repeat Steps 1-5 for each GSX9000 you are upgrading.
Loading GSX9000 Software GSX9000 Software Upgrade
Loading GSX9000 Software
You are ready to load and execute the software that is now properly installed on the NFS server
and in the GSX server module PROMs.
If your current software predates GSX9000 Version V04.00.02, you must load the GSX9000
Version V04.01 software by booting the system, as described in the next section.
If your current software is GSX9000 Version V04.00.02 or Version V04.00.03, then you may
qualify for loading the Version V04.01 software via LSWU. If you wish to use this Sonus facility,
see "Loading GSX9000 Software with Live Software Upgrade" on page 5-12. If you do not wish
to use the LSWU facility, you may load the new software by booting the system, as described in
the next section.
Loading GSX9000 Software by Booting the System
To load the GSX9000 software by booting the system:
1. Telnet back to the GSX9000, log on, and configure the SOFTWARE PATH appropriately for
this Version V04.01.00 software:
# telnet 128.22.1.162

Trying 128.22.1.162...
GSX9000 (128.22.1.162)
V04.01.00 R000
At the following prompts, enter the login name and password:

Login: admin
Password: *******
• Enter the following command:
% CONFIGURE NFS SHELF 1 SOFTWARE PATH V04.01.00R000
2. Reboot the GSX9000 to ensure that this new NFS parameter is used immediately:
% CONFIGURE NODE RESTART
Restart - Confirm (Y/N): Y
.
.
GSX9000 Software Upgrade Loading GSX9000 Software
3. Telnet once more to the GSX9000, log in, and configure your environment:
# telnet 128.22.1.162
If NODE NVS PARAMETER MODE is binaryFile (parameter loading

enabled), then the parameter file that was copied from the old software
path directory is loaded by the new software. Additional configuration
may be needed to make use of the new features offered by this version
of the software.

Trying 128.22.1.162...
GSX9000 (128.22.1.162)
V04.01.00 R000
At the following prompts, log on by entering the login name and password:
Login: admin
Password: *******
Then, continue to configure your environment:

% CONFIGURE …
4. Repeat the previous steps for each GSX9000 you are upgrading.
Loading GSX9000 Software with Live Software Upgrade
If your current software is GSX9000 Version V04.00.02 or Version V04.00.03, you may use the
LSWU procedure to load and execute the new software, subject to certain hardware and software
prerequisites. This procedure is documented in the GSX Operations Guide, Version 4.01,
Document Version 1. See Chapter 4, Managing the GSX, Performing Live Software
Upgrades. This section provides a comprehensive overview of this procedure, including hardware
and software requirements, background detail about the individual steps, suggestions for preparing
for an LSWU, and suggestions for performing an LSWU to a GSX that contains unprotected
SPS30 server modules. Follow the procedures in that document, omitting:
• installing software into the GSX system tree

• upgrading firmware.
You have already completed those two procedures.
Loading GSX9000 Software GSX9000 Software Upgrade
Restoring the Previously Installed Software
If it is necessary for any reason to return to the previous version of software after you have loaded
the GSX9000 software by booting the system, you do not need to replace the old firmware. The
V01.08.00R001 firmware will support the previous software as well as Version V04.01.00
software.
This procedure does require that you reboot the GSX9000. You will lose any active calls at the
time of the reboot.
1. Configure the NFS Software Path to V04.00.02R001 and reboot the GSX9000:
% CONFIGURE NFS SHELF 1 SOFTWARE PATH^ "V04.00.02R001"
% CONFIGURE NODE RESTART
Restart - Confirm (Y/N): Y
2. The GSX9000 will reboot the previous software that continues to exist under the old (and
new) NFS Boot Path. This software was never removed or overwritten by the new Version
V04.01.00 software. The Version V04.01.00 software was written to a new subdirectory under
the NFS Boot Path that will be forever ignored by the previous software.
The V01.08.00R001 boot PROM program images were written into the
original /SOFTWPTH/images subdirectory. Because V01.08.00R001
firmware supports all previous releases of the GSX9000 software, there
is no consequence to this change in configuration. The older boot PROM
program images were backed up in the same procedure. You may
choose to retrieve them from their saved repository and reinstall them.
GSX9000 Software Upgrade Loading GSX9000 Software
CHAPTER 6 Upgrade Existing DataStream
Integrator Software
Overview
The DataStream Integrator installation utility dsi_install will automatically invoke the
upgrade utility if it detects a previous installation of DataStream Integrator on the platform to
which it is being installed. Upgrades are only supported for up to two previous major releases.
If you are upgrading from this ...this menu will open when you run setup:
version to version 4.1...
3.3 Upgrade
4.0.1 Upgrade
4.0.2 Upgrade
An older patch level of 4.1 Uninstall
If the installation utility determines that the installed DataStream Integrator is older than the last
two major releases it will abort the upgrade. You will be informed of this action and instructed to
uninstall the older version of DataStream Integrator and install a new version.
If the installation utility determines that the installed DataStream Integrator is at the current major
revision level (in this case, 4.1), the Uninstall menu will open. You will need to uninstall the
existing version and reinstall the new version.
After an upgrade to DataStream Integrator 4.1 has been completed, all

adaptors (generic or custom) from the old release must be manually
removed and 4.1 adaptors installed for correct operation. After DSI
upgrade installation, and prior to adaptor installation, the
RouteDefinition and ConnectorDefinition configuration files should have
no entries.
System Software Upgrade Guide — 550-00206 — 1.0 6-1

Upgrade Existing DataStream Integrator Software Preconditions for DataStream Integrator Upgrade
Preconditions for DataStream Integrator Upgrade
• There must be a DataStream Integrator "maintainer" entry in /etc/services. If there is

not a "maintainer" entry, the following message will be displayed:
Because the current DSI installation is missing a DSI maintainer entry in
/etc/services, the installation script is unable to perform either an
install, uninstall, or upgrade. You must either correct this error or
perform a manual uninstall to address this problem.
Exiting from script...
• The /etc/init.d/lte_init script must exist. If the init script is missing, the following
message will be displayed:
Because /etc/services indicates that DSI is installed but the init script
in /etc/init.d is missing, the installation script is unable to perform
either an install, uninstall, or upgrade. You must either correct this
error or perform a manual uninstall to address this problem.
• The DataStream Integrator software must be located in the directory that is specified by the
install script. If it does not exist in the specified location with the specified directory name, the
following message will be displayed:
/etc/init.d/lte_install indicates that the installation location is /
dsm. However, /dsm does not exist. The installation script is therefore
unable to perform either an install, uninstall, or upgrade. You must
either correct this error or perform a manual uninstall to address this
problem.
• The install.log in the /export/home/dsi/files directory must exist. If the install log is missing,
the following message will be displayed:
Because the current DSI installation is missing /dsi/files/install, the
installation script is unable to perform either an install, uninstall, or
upgrade. You must either correct this error or perform a manual uninstall
to address this problem.
In Release 4.1 a system name change was made from DataStream Manager to DataStream
Integrator; and from lte, ltq, and dsm to dsi. As a consequence, the upgrade installation must
also accommodate these name changes. The upgrade installation with a name change will occur
only for those pre-4.1 releases capable of being upgraded (3.3 build 55, and 4.0.2 build 57). The
name changes will include the following:
• The installation directory will be changed from /dsm to /dsi

• The DataStream Integrator user will be changed from ltq to dsi
• The DataStream Integrator group will be changed from ltq to sonus
6-2 System Software Upgrade Guide — 550-00206 — 1.0
Upgrade Upgrade Existing DataStream Integrator Software
Upgrade
Upgrading to a Newer Version of DataStream Integrator
Step Action
1. Make sure that:
• All users named dsi are logged off.
• The DSI CLI is not running. For instructions on stopping DSI CLI, refer to the
DataStream Integrator Administration and Maintenance Guide.
• All DSI processes are stopped.
2. Log on to the DataStream Integrator server as user root. Insert the DataStream
Integrator Installation CD into the CD-ROM drive.
3. Change to the prod directory by typing:
cd /cdrom/cdrom0/prod
4. Type the following command:
./setup
A prompt will report on the amount of space available in your /tmp directory and the size
of the DataStream Integrator installation files, then ask if you want to proceed.
Type Y at the prompt. The following installation files will be copied to the /tmp directory:
• adaptor_install
• dsi.tar
• dsi_install
• DSIAgent.tar
• dsiadaptors.tar
• upgrade
• patching.tar
• setup
Although you can invoke the setup script from anywhere on the host system, all files
will be copied to the /tmp directory.
Upgrade Existing DataStream Integrator Software Upgrade
Upgrading to a Newer Version of DataStream Integrator (Continued)
Step Action
5. If the setup utility determines that conditions are correct, the Upgrade menu will open.
An example is shown here, release numbers may differ on your system:
DataStream Integrator Installation

Upgrade Menu
________________________________________________________
You currently have DSI Release 4.0.2 Build 57 installed at

/dsm.
1. Upgrade to DSI Release 4.1 b 035

2. Save DSI Release 4.0.2 b 57 to a tar file
3. Uninstall DSI Release 4.0.2 b57
4. View Install Log for DSI 4.0.2 b 57
5. Exit
________________________________________________________
Enter your choice [5]

6. If you want to save your current DataStream Integrator release to a tar file, type 2 and
answer the prompts.
7. Type 1 at the prompt to begin the upgrade.
8. At the prompt:
Begin Upgrade to DSI 4.1 Now? (Y/N) [N]
...type Y.
9. At the prompt:
DSI 4.0.2 at /export/home/dsm will be saved to /var/log/
lte/DSI_TAR_(4.0.2_57)_04-23-02:10:21:45.
You will need 16772 kbytes of space in /var/log/lte to
store it.
You currently have 225015 kbytes of space in /var/log/lte.
Do you wish to continue? (Y/N) [N]
...type Y.
Upgrade Upgrade Existing DataStream Integrator Software
Step Action
10. At the prompt:
Tar file DSI_TAR_(4.0.2_57)_04-23-02:10:21:45 has been
created in /var/log/lte.
[Press Enter to Continue]
...press Enter.
11. At the prompt:
Would you like to delete the group "ltq"? (Y/N) [N]
...type Y. The following message will be displayed:
Group ltq has been deleted.
12. At the prompt:
Would you like to delete the user "ltq"? (Y/N) [N]
...type Y. The following message will be displayed:
Deleting ltq user account and /export/home/dsm directory.
This may take a few minutes...
User ltq has been deleted.
Backing up /etc/services before updating ...
Backing up /etc/inetd.conf before updating ...
Deleted file /etc/rc3.d/S99dsm
Deleted file /etc/rc2.d/K99dsm
Deleted link /dsm
13. After a series of DataStream Integrator uninstall messages is displayed, you will be
prompted for new group and user IDs. Accept the default values by pressing Enter at
each prompt:
Creating home directories for user dsi ...
Creating group sonus
Default GroupID = 101.
Change GroupID ? (Y/N) [N]
GroupID = 101
Creating user dsi
Default UserID = 1036.
Change UserID ? (Y/N) [N]
UserID = 1036
Upgrade Existing DataStream Integrator Software Upgrade
Step Action
14. Create and verify a dsi user password at the prompts:
You must now change the password for dsi
New password:
Re-enter new password:
passwd (SYSTEM): passwd successfully changed for dsi
15. The following messages will be displayed after the Upgrade has been successfully
completed:
Old 4.0.2 and default 4.1 configuration files have been
saved in /export/home/dsi/files.
These files have version and date/timestamp file extensions
and are not needed to run DSI.
These files may be reviewed, if you wish, or they may be
removed.
16. At the prompt:
Do you wish to view the install log now? (Y/N) [N]
...type Y to view the log, or N to continue.
17. At the prompt:
Do you wish to run the adaptor script? (Y/N) [N]
...press Enter. You will then be instructed to exit the Upgrade script:
[Press Enter to Exit]
Press Enter at the prompt.
Rollback Upgrade Existing DataStream Integrator Software
Rollback
During the upgrade, a copy of the dsi directory is created using the UNIX tar command and
placed in the /var/log/dsi directory. It is meant solely as a source of reference.
After installing or upgrading, you can manually roll back to a previous version of DataStream
Integrator by uninstalling the new version and reinstalling the older version.
Upgrade Existing DataStream Integrator Software Rollback

550-00206 Version 4.1 System Upgrade 1

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

550-00206 Version 4.1 System Upgrade 1

Caricato da

Copyright:

Formati disponibili

SONUS TECHNICAL PUBLICATION

Sonus Part Number: 550-00206

Disclaimer and Restrictions

Chapter 2 Insight EMS Software Upgrade

System Software Upgrade Guide - 550-00206 - 1.0 iii

iv System Software Upgrade Guide - 550-00206 - 1.0

Chapter 4 SGX SS7 Gateway Software Upgrade

Chapter 5 GSX9000 Software Upgrade

System Software Upgrade Guide - 550-00206 - 1.0 v

vi System Software Upgrade Guide - 550-00206 - 1.0

This is the contents provided in the Introduction:

• "About this Document" on page 1-2

System Software Upgrade Guide - 550-00206 - 1.0 1-1

About this Document

This document is intended for the following audience:

• Customer Operation Teams

This document uses the following admonition conventions:

This is a Note or Attention indicator for additional information.

This is a Caution indicator, indicating the possibility of data loss or

This is a Warning indicator, indicating physical danger to the operator of

1-2 System Software Upgrade Guide - 550-00206 - 1.0

TABLE 1-1. Sonus TAC contact information

The TAC is available 24 hours a day, 7 days a week.

Sonus Networks, Inc.

System Software Upgrade Guide - 550-00206 - 1.0 1-3

The following component upgrades are addressed in this document:

TABLE 1-2. Upgrade Components and Versions

Previous Software Upgraded

System Software Upgrade Sequence

Use the following sequence to perform a system software upgrade:

1-4 System Software Upgrade Guide - 550-00206 - 1.0

Required Upgrade Materials

To perform a system software upgrade, you need the following materials:

• Telnet access to the management network

System Software Upgrade Guide - 550-00206 - 1.0 1-5

Upgrade a Solaris 2.6 Operating System to Solaris 8

TABLE 1-3. Necessary Solaris OS Upgrades

Product The Solaris OS Upgrade to version 8 is necessary, if

No Solaris OS Upgrade necessary

Verify your Solaris OS System Version

1. At the command prompt type:

1-6 System Software Upgrade Guide - 550-00206 - 1.0

Upgrading the Solaris OS

Before beginning the upgrade to Solaris 8, verify that you have a

Upgrading the Solaris OS from version 2.6 to 8 (2.8):

System Software Upgrade Guide - 550-00206 - 1.0 1-7

Upgrading the Solaris OS from version 2.6 to 8 (2.8):

1-8 System Software Upgrade Guide - 550-00206 - 1.0

Upgrading the Solaris OS from version 2.6 to 8 (2.8):

Due to the OS upgrade, the SNMP Research software generates a

System Software Upgrade Guide - 550-00206 - 1.0 1-9

Upgrading the Solaris OS from version 2.6 to 8 (2.8):

1-10 System Software Upgrade Guide - 550-00206 - 1.0

Necessary Solaris OS Patches and Actions

Solaris 8 Operating System

Installing the Cluster:

System Software Upgrade Guide - 550-00206 - 1.0 1-11

Solaris 2.6 Operating System

Installing the Cluster:

1-12 System Software Upgrade Guide - 550-00206 - 1.0

TABLE 1-1. List of Daemons ought to be disabled on Solaris OSs

System Software Upgrade Guide - 550-00206 - 1.0 1-13

Java Runtime Environment