Cisco BTS 10200 Softswitch Solaris OS Install/Upgrade Procedure

Cisco BTS 10200 Softswitch

Solaris OS Install/Upgrade Procedure for Solaris 10 Version 0606

Install-Core CD Version #: Solaris!Sun!sparc!10!0!0606!V02

Install-Finish CD Version #: Solaris!Sun!sparc!10!0!0606!BTS02

EDCS-562654

July 27, 2007

Corporate Headquarters

Cisco Systems, Inc.

170 West Tasman Drive

San Jose, CA 95134-1706

USA

http://www.cisco.com

Tel: 408 526-4000

800 553-NETS (6387)

Fax: 408 526-4100

Cisco BTS 10200 Softswitch CD Install/Upgrade for Solaris 10 Version 0606

Page 1 of 51

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE

WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED

TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST

TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE

INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE.

IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO

REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley

(UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the

University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE

SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL

WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY,

FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE,

OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR

INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA

ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN

ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco

Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the

Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, MGX, MICA, the Networkers logo, Network Registrar, Packet, PIX, Post-

Routing, Pre-Routing, RateMUX, Registrar, ScriptShare, SlideCast, SmartNet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, The

Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.

All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0304R)

Cisco BTS 10200 Softswitch CD Jumpstart Procedure for Duplex Systems

Copyright © 2005-2007, Cisco Systems, Inc.

All rights reserved.


Page 2 of 51

Revision History

Date

12/12/06

Version Description

1.0

Initial version

01/18/2007 1.1

Changes suggested by SysTest and Integration

02/16/2007 1.2

Changes to V02 and suggestions from SysTest.

03/19/2007 1.3

03/29/2007 1.4

04/09/2007 1.5

05/03/2007 1.6

05/31/2007 1.7

06/18/2007 1.8

07/16/2007 1.9

07/27/2007 1.10

Added a check on BTSjava in the upgrade procedure. Added checkmarks to all procedural steps.

Added reference to the Oracle relink procedure. A few minor touches suggested by the last round of tests.

Clarified that the OS-upgrade is intended to be run on a system with BTS installed.

Added a clarification about a possible warning appearing on the console when rebooting from OS upgrade.

For the backup before OS upgrade referring to two approaches:

a) the Cisco BTS 10200 Backup and Restore procedure using

the mirrored disk approach . b) the flash archive described in Cisco BTS 10200 Softswitch

Operations Manual (Performing Full System Backup).

Added a short Appendix to handle the case where the CD cannot be mounted on the suggested device. Used a better example on step 6 of the upgrade. Added a step 9 on the BTS finish procedure. Added a step for T2000 only in the Install procedure.

Changed the name of the document for the backup mirroring procedure

Requested a manual check on the link of /etc/hosts to

/etc/inet/hosts for the OS upgrade.

Added a restoration step for ‘date’ and ‘rdate’ in the OS upgrade.


Page 3 of 51

Table of Contents

Preface.............................................................................................................................. 5

1. Overview .................................................................................................................... 9

Supported Hardware and Firmware ..................................................................... 9

2. Precautions ............................................................................................................... 11

3. Prerequisite Checklist .............................................................................................. 12

4. New OS Install ......................................................................................................... 14

OS Core Installation Procedure ......................................................................... 14

BTS-Finish Procedure ........................................................................................ 16

Setting Up the Network Configuration Files ..................................................... 19

Configuring the Element Management System ................................................. 20

Configuring the Call Agent and Feature Server Installation ............................. 21

5. OS Upgrade .............................................................................................................. 23

OS Core Upgrade Procedure .............................................................................. 23

BTS Finish Upgrade Procedure ......................................................................... 46

6. Appendix A: Mirroring the Disks ........................................................................... 48

7. Appendix B: Setting the Time Zone ....................................................................... 50

8. Appendix C: Where to mount a CD ........................................................................ 51


Page 4 of 51

Preface

Obtaining Documentation

These sections explain how to obtain documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at this URL: http://www.cisco.com/

Translated documentation is available at this URL: http://www.cisco.com/public/countries_languages.shtml

Documentation CD-ROM

Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.

Ordering Documentation

You can order Cisco documentation in these ways:

Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the

Networking Products MarketPlace: http://www.cisco.com/cgi-bin/order/order_root.pl

Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription

Store: http://www.cisco.com/pcgi-bin/marketplace/welcome.pl

Non registered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in

North America, by calling 800 553-NETS (6387).

Documentation Feedback

You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.

You can e-mail your comments to [email protected].


Page 5 of 51

You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:

Cisco Systems

Attn: Document Resource Connection

170 West Tasman Drive

San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you with these tasks:

Streamline business processes and improve productivity

Resolve technical issues with online support

Download and test software packages

Order Cisco learning materials and merchandise

Register for online skill assessment, training, and certification programs

If you want to obtain customized information and service, you can self-register on Cisco.com. To access

Cisco.com, go to this URL: http://www.cisco.com/

Technical Assistance Center

The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC

Web Site and the Cisco TAC Escalation Center.

Cisco TAC inquiries are categorized according to the urgency of the issue:

Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.

Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.

Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.

The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.

Cisco TAC Web Site


Page 6 of 51

You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time.

The site provides around-the-clock access to online tools, knowledge bases, and software. To access the

Cisco TAC Web Site, go to this URL: http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a

Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register: http://tools.cisco.com/RPF/register/register.do

If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco

TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL: http://www.cisco.com/tac/caseopen

If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC

Web Site.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations.

When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network

Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.


Page 7 of 51

<<This page left intentionally blank>>


Page 8 of 51

1. Overview

A BTS10200 host machine must have the BTS version of the Solaris image installed on it prior to installing BTS10200 software. Also, when upgrading the BTS10200 software, it may be necessary to first upgrade the Solaris OS image on the machine. This document describes the procedures used to a) install the Solaris 10 (0606) image on a BTS10200 host machine, and b) upgrade the Solaris 10 image on a BTS host machine to the (0606) version.

This document is intended for those responsible for installing the Cisco BTS 10200

Softswitch.

This procedure uses a two CD set – the Install-Core CD and the Install-Finish CD. Their versions are:

Install-Core CD Version #: Solaris!Sun!sparc!10!0!0606!V02

Install-Finish CD Version #: Solaris!Sun!sparc!10!0!0606!BTS02

Supported Hardware and Firmware

The following host machines are supported by this Solaris OS image (please note that all

of these may not be supported by specific BTS releases). The minimum disk size required for an installation is 36 gig. Each supported hardware type has a minimum firmware version level required for correct performance. The operator must check for the correct firmware version and perform a firmware upgrade if necessary prior to OS installation/upgrade. The firmware version can be obtained by executing the following

Solaris command.

# prtconf -V

Hardware Compatibility and Recommended Firmware Version

• Sun Fire T2000 requires Firmware 6.2.4

• Sun Fire V1280 requires Firmware 5.19.2



• Sun Netra 440 Same as V440


Page 9 of 51

• Sun Netra 240 Same as V240

• Sun Netra 120

• Sun Netra 1405

• Sun Netra 105

Note that on the 1280, the system components must have a firmware version which matches the monitor prom. On bootup, a console message is displayed for each system component version. Verify each component version with the monitor prom version.


Page 10 of 51

2. Precautions

CAUTION: These procedures should not be performed while the host machine is handling live traffic. All BTS networks elements (CA, FS, EMS, BDMS) must be brought down on the host machine prior to executing this procedure for both new OS installs or for OS upgrades. A new OS install will also delete all existing software and data from the machine. Do not run these procedures on an active system that is carrying live traffic. If you have questions, contact Cisco TAC.

There is no backing out once these procedures are started.

Data backup before OS Install.

If data is present, perform a data backup using the applicable procedure in the Cisco BTS

10200 Softswitch Operations Manual before you start this procedure. If you are reinstalling an existing Cisco BTS 10200 Softswitch software version following this jumpstart, you can restore the Cisco BTS 10200 Softswitch data that was previously backed up. Follow the procedure in the Cisco BTS 10200 Softswitch Operations

Manual. If you are installing a new software version following this jumpstart, data previously backed up will become obsolete and cannot be restored on the new software.

Data must be re-provisioned. You can restore data backups performed after the software installation in the usual manner.

Full system backup before OS Upgrade

Perform a full system backup using one of the following two options.

a) A disk mirroring approach as described in the Backup and Restore

procedure using the mirrored disk approach-Option2 document. b) A flash archive approach as outlined in the Cisco BTS 10200 Softswitch

Operations Manual (Performing Full System Backup).

We recommend that you back up data that has been restored or re-provisioned following software installation.

A user experienced in basic UNIX commands should perform this procedure.

The prerequisite checklist should be completed prior to starting the procedure.


Page 11 of 51

3. Prerequisite Checklist

1. Ensure that the Cisco BTS 10200 Softswitch hardware components are set up and turned on in accordance with manufacturer recommendation.

Done

2. Verify hardware and firmware compatibility (see Chapter 1 for details)

Done

3. Verify that you have the correct CDs (see Chapter 1 for details)

Done

4. Perform data backup as necessary if the machine was running BTS10200 software prior to OS install/upgrade (see Chapter 2 , Data backup before OS Install or

Full system backup before OS Upgrade section for details)

Done

5. The following tasks need to be performed for a new OS install only (i.e. not for an

OS upgrade) a) Ensure that you have a Network Installation Data Sheet (NIDS) provided by Cisco. This will contain the following information necessary to place the jumpstarted node on the network after the

CD installation.

 nodename

 hosts

 netmasks

 hostname.<primary interface>.

Done

6. The following tasks need to be performed for an OS upgrade only a) Verify that you have the “

BTS Oracle Engine Binaries

Relink”

document (EMS nodes specific).

Done b) Verify that /etc/hosts is a link to /etc/inet/hosts. If this is not the case, make sure that /etc/inet/hosts has the right configuration

(the OS upgrade will take care of linking /etc/hosts to

/etc/inet/hosts)

.

Done


Page 12 of 51

c) Verify that the BTS load is installed. The OS upgrade is not intended to be a preliminary step to the BTS installation. The OS upgrade is intended for a system performing the complete BTS services.

Done d) Verify that the system is based on the following Install version:

"Solaris!Sun!sparc!10!0!0503!V02”. Type the following command:

# cat /etc/jcoreversion

Done e) BTS specific: Verify that the system is based on the following

Finish version: "Solaris!Sun!sparc!10!0!0503!BTS02". Type the following command:

# cat /etc/jbtsversion

Done f) BTS specific: Verify that the disk is mirrored. See Appendix A.

Done g) BTS specific: BTS has been installed in this system.

Done

7. Ensure that a console port is available to carry on the jumpstart/upgrade procedure.

Done


Page 13 of 51

4. New OS Install

Use the following procedure only if you are performing a fresh OS install. If you are performing an upgrade of an existing Solaris 10 image on a BTS host, go to Chapter 5.

OS Core Installation Procedure

Step 1 Power on the system and bring the ok> prompt to the console.

NOTE: If Solaris is already installed, to get to the ok prompt login as root on the console and then run:

# shutdown –i0 –g0 -y

Done

Step 2 Type the following commands to restart the system and bring it to a known state: ok> setenv auto-boot? false ok> reset-all

Done

Step 3 Insert the CISCO Solaris 10 Install - Core CD into the CD-ROM drive

Done

Step 4 Type the following commands: ok>setenv auto-boot? true ok>boot cdrom – install (NOTE: there is a space between ‘-‘ and ‘install’)

Done

The process will take approximately 10 to 20 minutes.

Notes:

1. If you encounter the following Error: “ERROR Disk is Invalid” Please check to make sure your Hardware configuration match exactly with the list of supported Hardwares.

2. The system will prompt for an NFS domain name near the end of this step. Enter

“carriage return”.


Page 14 of 51

3. By default, the steps above will assign the system the host name vtghost and the IP address 192.168.123.1 and the default root password vtghost.

Step 5 Login using user name root and password vtghost.

Done

Step 6 (T2000 only)

Add an entry to /etc/system:

# echo “set pcie:pcie_aer_ce_mask=0x1” >> /etc/system

Done N/A

Step 7 Continue with the same CD that is in the CD-ROM drive. Mount the CD using the following command:

# mount –F hsfs –o ro /dev/dsk/c0t0d0s0 /cdrom

NOTE: if the above command fails go to Appendix C to find the proper

/dev/dsk device.

Done

Step 8 Execute the following command

#

cd /

# /cdrom/core_finish/core_finish.sh

This procedure will be aborted if the working directory is not root (‘/’). If this happens it will be possible to redo this procedure from the root directory.

NOTE: a question will be posted asking for the local host name, be ready to answer.

Wait for this procedure to finish: at the end the CD will be ejected and the system might reboot automatically depending on the type of Solaris patches installed. There will be no other request.

Done


Page 15 of 51

BTS-Finish Procedure

Note: Enter all commands as shown; some commands are case sensitive. Press Enter at the end of each command.

This section describes how to finish jumpstarting the Solaris 10 operating system on the

Cisco BTS 10200 Softswitch platforms for both the EMS and CA node types. You must execute the following procedure for each of the four nodes in the BTS10200 Softswitch.

Start on the primary EMS. To perform the BTS-finish follow these steps:

Step 1 Login using user name root and password vtghost.

Done

Step 2 Insert the Cisco Solaris 10 Install - Finish CD into the CD-ROM drive

Done

Step 3 Mount the CD using the following command:


NOTE: if the above command fails go to Appendix C to find the proper /dev/dsk device.

Done

Step 4

Execute the following two commands for an EMS node

#

cd /cdrom/EMS

# ./EMS_finish.sh

Execute the following two commands for a CA node,

# cd /cdrom/CA

# ./CA_finish.sh

Done

Note: To have the vi editor work correctly on the console terminal, you may first need to type the following commands for all shells except C-Shell.


Page 16 of 51

# TERM=vt100

# export TERM

For C-Shell, use

# setenv TERM vt100

Step 5 Edit the /etc/TIMEZONE file and change the TZ setting to the correct setting for your locale. Reference Appendix B for additional information on how to do this.

Done

Step 6 Create and/or edit the following files to allow Ethernet communication via the first management interface port.

The purpose is to provide the minimal network capability to later transfer the entire set of configuration files as defined in the NIDS. The changes operated during this step will use the host name and the first management IP address as provided by the Network Information Data Sheet (NIDS).

 For EMS nodes, the first management IP address is applied to the first working Ethernet interface, such as eri0 or ce0.



For CA nodes, the first management IP address is applied to the third working

Ethernet interface (starting with the onboard ports and continuing with a 4 port network interface card if necessary).

NOTE: For CA nodes based on 1280 and 440 and using a quad CE Ethernet card for the management networks, the name of the first Management interface might not be ‘ce2’ as expected. To determine the actual name of the first Management CE interface run the following script (CA nodes only):

#

cd /opt/setup

#

./getFirstManCE.sh

The example illustrated below indicates changes for a node named prica23 on the management IP address 10.89.183.112 which uses the Ethernet interface qfe0 and a netmask of 255.255.255.0

/etc/hosts

Add the entry for the network IP address and this node name. Like

# echo “10.89.183.112 prica23” >> /etc/hosts

(Note the double ‘>>’ to ‘append’ to the end of a file)

/etc/netmasks


Page 17 of 51

Enter the subnet and netmask for the IP address placed in hostname.<working

network interface> . For example

# echo “10.89.183.0 255.255.255.0” >> /etc/netmasks


/etc/hostname.<working network interface>

This file always contains the name of this node. For our example, the file hostname.qfe0 will contain prica23 on a single line.

# echo prica23 > /etc/hostname.qfe0

(Note the single ‘>’ to over-write a file)

/etc/rc3.d/S96StaticRoutes

This file should be edited to include the subnet default route to enable communication between the EMS and CA nodes on the subnet. Note that all NTP,

DNS traffic and traffic from other machines to BTS system (eg. login), should all go through management networks for security reasons, shielding as much as possible the signaling traffic. Static routes are particularly important in the CA system because CA has both management and signaling networks. If the user does not specify explicitly a route through the management networks in this file, the traffic will be directed to the signaling networks.

For example purposes, the following line should be added to this file since

10.89.183.254 is the IP address of the router for the 183 subnet.

# echo “route add -net 10.89.0.0 10.89.183.254” >> /etc/rc3.d/S96StaticRoutes


/etc/resolv.conf

Edit this file with the appropriate values for your network. Change the domain, search, and nameserver entries for your network.

NOTE: Once you have customized the files above, “cat” each one in turn to verify the changes were made correctly.

Done

Step 7 Reboot the system with the following command

# shutdown –i6 –g0 –y


Page 18 of 51

Done

Step 8 Log in as root using password opticall.

Done

Setting Up the Network Configuration Files

To set up files needed to configure each BTS10200 node, verify that both EMS and both

CA machines are properly configured for a network connection to each other. Then complete the following steps:

Step 1 Login as root on EMS side A.

Done

Step 2 Navigate to the /setup directory by entering the following command:

# cd /opt/setup

Done

Step 3 Edit the ‘hostconfig’ file by entering the following command:

# vi hostconfig

Edit the ‘hostconfig’ file as appropriate with the information found in the NIDS.

The references to ENDFIX are the last octet of the particular computing element

IP address found in the first Management Network section of the NIDS. If you have any questions, contact Cisco TAC.

Done

Step 4 Save the edited hostconfig file

Done

Step 5 Generate the ‘host’ and ‘netmasks’ files in /tmp by entering the following command:

#./hostgen.sh

Done

Step 6 Change directory by entering the following command:

# cd /tmp

Done


Page 19 of 51

Step 7 Verify that the entries in /tmp/host have the correct values by comparing them to the values in the NIDS.

Done

Step 8 Manual intervention is needed if one of the following cases applies:

 The host address of the IPs used on the physical/logical interfaces (last

‘octet’) is not the same on a given host. In this case a manual intervention is expected in order to update the entries in /etc/hosts that do not comply with the values created by the jumpstart procedure.

 The netmasks are different from 255.255.255.0. In this case the

/etc/netmasks will need some manual correction.

The /etc/hosts and /etc/netmasks files are rebuilt, as part of the jumpstart procedure in two steps. First two files are generated in /tmp, ‘host’ and

‘netmasks’, by running ‘hostgen.sh’. Later on, ‘setlogic_EMS.sh’ (or

‘setlogic_CA.sh’ in the CallAgent) will make the final changes in the /etc directory. The two files /tmp/host and /tmp/netmasks, produced by hostgen.sh, must be modified as needed.

Done

Step 9 This procedure will not be repeated on the other nodes. Just use the sftp command to transfer the /tmp/host and /tmp/netmask files to the secondary EMS.

sftp <secems IP address>

cd /tmp

put host

put netmasks

quit

Done

Step 10 Next, repeat step 9 for to transfer the same files to the primary call agent.

Done

Step 11 Next, repeat step 9 to transfer the same files to the secondary call agent

Done

Configuring the Element Management System

To configure the primary and secondary EMS nodes, complete the following steps on both primary and secondary EMS nodes.

Step 1 Login as root.

Done


Page 20 of 51

Step 2 Change directory by entering the following command:

# cd /opt/setup

Done

Step 3 Run the setlogic_EMS.sh script to set up the interfaces by entering the following command:

# ./setlogic_EMS.sh

Done

Step 4 Verify that the /etc/netmasks and /etc/hosts files have the correct values by comparing them to the values in the NIDS.

Done

Step 5 Shutdown and reboot the system using the following command:


Done

Step 6 For Field Installations and Lab installations which require mirrored disks, execute the procedure in Appendix A

Done N/A

Configuring the Call Agent and Feature Server Installation

To configure the primary and secondary CA and FS, complete the following steps on both primary and secondary call agent nodes.

Step 1 Login as root.

Done

Step 2 Change directories by entering the following command:

# cd /opt/setup

Done

Step 3 Run the ./setlogic_CA.sh script to set up the interfaces.

# ./setlogic_CA.sh

Done


Page 21 of 51

Step 4 Verify that the /etc/netmasks, and /etc/hosts files have the correct values by comparing them to the values in the NIDS. Make sure both match the NIDS.

Done

Step 5 Shutdown and reboot the system using the following command


Done

Step 6 For Field Installations and Lab installations which require mirrored disks, execute the procedure in Appendix A

Done


Page 22 of 51

5. OS Upgrade

Use the following procedure only if you are upgrading an existing Solaris 10 image on a

BTS host. If you are performing a fresh OS install, go to Chapter 4.

OS Core Upgrade Procedure

Step 1. Complete the prerequisite checklist in Chapter 3.

Done

Step 2 Verify that /opt/BTSjava has just one directory and nothing else. a. Determine the directory that /usr/java points to:

# ls –l /usr/java

Example output: lrwxrwxrwx 1 root other 24 Mar 6 16:55 /usr/java -> /opt/BTSjava/jdk1.5.0_07

/

Done b. Ensure that only one Java directory exists under /opt/BTSjava and nothing else:

# ls –l /opt/BTSjava

Done c. If only one directory exists, go to step e.

Done N/A d. If there is any other directory or file beside the directory pointed to by

/usr/java (refer to step a), delete every directory/file leaving only the

Java directory used by /usr/java:

# \rm –rf <unwanted directory/file>

Done N/A e. Continue to step 3.

Done


Page 23 of 51

Step 3 Insert the Cisco Solaris 10 Install - Core CD into the CD-ROM drive.

Done

Step 4. Login as root on the console and execute:

# platform stop all

# mv /etc/rc3.d/S99platform /etc/rc3.d/saved.S99platform

Done

Step 5. Halt the system using the shutdown command:

# shutdown –i0 –g0 -y

The ok monitor “ok” prompt will appear.

Done

Step 6. Execute the following command:

ok >

boot cdrom – upgrade

NOTE: ‘-‘ and ‘upgrade’ must be separate by at least one space

NOTE: typing ‘install’ instead of ‘upgrade’ will generate a fresh jumpstart

Done

The output on the console will be similar to this (some differences in output will be hardware dependent):

SC Alert: Host System has Reset

SC Alert: Host system has shut down.

-

Sun Fire T200, No Keyboard

Copyright 2006 Sun Microsystems, Inc. All rights reserved.

OpenBoot 4.20.4, 8184 MB memory available, Serial #70061496.

Ethernet address 0:14:4f:2d:d:b8, Host ID: 842d0db8.

Rebooting with command: boot cdrom - upgrade

Boot device: /pci@7c0/pci@0/pci@1/pci@0/ide@8/cdrom@0,0:f File and args: - upgrade

SunOS Release 5.10 Version Generic_118833-17 64-bit

Copyright 1983-2005 Sun Microsystems, Inc. All rights reserved.

Use is subject to license terms.

Configuring devices.

Using RPC Bootparams for network configuration information.

Attempting to configure interface ipge3...

Skipped interface ipge3







-

Beginning system identification...

Searching for configuration file(s)...


Page 24 of 51

It will take about 10 minutes for the first graphical interface to appear. This is the average case. However in some instances this period might go over the 30 minutes (we have seen this on a 1280).

NOTE: It is only after entering step 22 that the actual upgrade takes effect.

The following steps can be safely aborted up to step 21 by selecting the <Exit> option (see the boxed note below).

This graphical interface will appear:

- The Solaris Installation Program ---------------------------------------------

The Solaris installation program is divided into a series of short sections

where you'll be prompted to provide information for the installation. At the

end of each section, you can change the selections you've made before

continuing.

About navigation...

- The mouse cannot be used

- If your keyboard does not have function keys, or they do not

respond, press ESC; the legend at the bottom of the screen

will change to show the ESC keys to use for navigation.

--------------------------------------------------------------------------------

F2_Continue F5_Exit F6_Help

Step 5. Type <ESC 2>

Done

To navigate the screen use:

> Arrow keys

Or:

> Control-N...to move down

> Control-P...to move up

> Enter … to select the choice where the cursor is positioned

In general, any menu choice can be selected by typing <ESC> followed by the number corresponding to the proper function key. For instance <F5> becomes <ESC 5>.

NOTE: In case the <Exit> choice is selected, the prompt becomes “#” and Solaris can be restarted by simply typing:

# reboot


Page 25 of 51


- Solaris Interactive Installation ---------------------------------------------

On the following screens, you can accept the defaults or you can customize

how Solaris software will be installed by:

- Selecting the type of Solaris software to install

- Selecting disks to hold software you've selected

- Selecting unbundled products to be installed with Solaris

- Specifying how file systems are laid out on the disks

After completing these tasks, a summary of your selections (called a

profile) will be displayed.

There are two ways to install your Solaris software:

- "Standard" installs your system from a standard Solaris Distribution.

Selecting "Standard" allows you to choose between initial install

and upgrade, if your system is upgradable.

- "Flash" installs your system from one or more Flash Archives.

--------------------------------------------------------------------------------

Esc-2_Standard F3_Go Back Esc-4_Flash F5_Exit F6_Help

Step 6. Type <ESC 2>

Done


Page 26 of 51


- Eject a CD/DVD Automatically? ------------------------------------------------

During the installation of Solaris software, you may be using one or more

CDs/DVDs. You can choose to have the system eject each CD/DVD automatically

after it is installed or you can choose to manually eject each CD/DVD.

[X] Automatically eject CD/DVD

[ ] Manually eject CD/DVD

--------------------------------------------------------------------------------

F2_Continue F3_Go Back F5_Exit

Step 7. Move the cursor down to <Manually eject CD/CVD> and press <Enter>.

Done


Page 27 of 51

The screen will change:

- Eject a CD/DVD Automatically? ------------------------------------------------

During the installation of Solaris software, you may be using one or more

CDs/DVDs. You can choose to have the system eject each CD/DVD automatically

after it is installed or you can choose to manually eject each CD/DVD.

[ ] Automatically eject CD/DVD

[X] Manually eject CD/DVD

--------------------------------------------------------------------------------


Step 8. Press <Esc 2>

Done


Page 28 of 51


- Reboot After Installation? ---------------------------------------------------

After Solaris software is installed, the system must be rebooted. You can

choose to have the system automatically reboot, or you can choose to

manually reboot the system if you want to run scripts or do other

customizations before the reboot. You can manually reboot a system by using

the reboot(1M) command.

[X] Auto Reboot

[ ] Manual Reboot

--------------------------------------------------------------------------------



Done


Page 29 of 51


- Solaris Interactive Installation ---------------------------------------------

This system is upgradable, so there are two ways to install the Solaris

software.

The Upgrade option updates the Solaris software to the new release, saving

as many modifications to the previous version of Solaris software as

possible. Back up the system before using the Upgrade option.

The Initial option overwrites the system disks with the new version of

Solaris software. This option allows you to preserve any existing file

systems. Back up any modifications made to the previous version of Solaris

software before starting the Initial option.

After you select an option and complete the tasks that follow, a summary of

your actions will be displayed.

--------------------------------------------------------------------------------

F2_Upgrade F3_Go Back F4_Initial F5_Exit F6_Help


Done


Page 30 of 51


- Initializing -----------------------------------------------------------------

The system is being initialized.

Loading install media, please wait ..

Step 11. Just wait ..

Done


Page 31 of 51

NOTE: This request is not expected; in a normal configuration this screen will not show up.

If there are two disks with a Solaris image, this graphical interface will appear:

- Select Version to Upgrade ----------------------------------------------------

More than one version of Solaris has been found on the system. Select the

version of Solaris to upgrade from.

Solaris Version Slice

----------------------------------

[X] Solaris 10 c1t0d0s0

[ ] Solaris 10 c1t1d0s0

--------------------------------------------------------------------------------

F2_Continue F3_Go Back F5_Exit F6_Help

Step 12. BTS specific: type <Esc 2> to select disk0.

General case: select the proper slice and then type <Esc 2>.

Done N/A

This could be the case of a system that used to have disk mirroring. Now the two disks are independent and both disks have a Solaris image.

(BTS specific: This should not happen. Disk mirroring is the default).


Page 32 of 51


- License ----------------------------------------------------------------------

- Sun Microsystems, Inc. ("Sun")

| SOFTWARE LICENSE AGREEMENT

|

| READ THE TERMS OF THIS AGREEMENT ("AGREEMENT") CAREFULLY BEFORE

| OPENING SOFTWARE MEDIA PACKAGE. BY OPENING SOFTWARE MEDIA

| PACKAGE, YOU AGREE TO THE TERMS OF THIS AGREEMENT. IF YOU ARE

| ACCESSING SOFTWARE ELECTRONICALLY, INDICATE YOUR ACCEPTANCE OF

| THESE TERMS BY SELECTING THE "ACCEPT"(OR EQUIVALENT) BUTTON AT

| THE END OF THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE

| TERMS, PROMPTLY RETURN THE UNUSED SOFTWARE TO YOUR PLACE OF

| PURCHASE FOR A REFUND OR, IF SOFTWARE IS ACCESSED ELECTRONICALLY,

| SELECT THE "DECLINE" (OR EQUIVALENT) BUTTON AT THE END OF THIS

| AGREEMENT. IF YOU HAVE SEPARATELY AGREED TO LICENSE TERMS

| ("MASTER TERMS") FOR YOUR LICENSE TO THIS SOFTWARE, THEN SECTIONS

| 1-6 OF THIS AGREEMENT ("SUPPLEMENTAL LICENSE TERMS") SHALL

| SUPPLEMENT AND SUPERSEDE THE MASTER TERMS IN RELATION TO THIS

| SOFTWARE.

|

v 1. Definitions.

--------------------------------------------------------------------------------

Esc-2_Accept License F5_Exit


Done


Page 33 of 51


- Select Geographic Regions ----------------------------------------------------

Select the geographic regions for which support should be installed.

> [ ] Australasia

> [ ] Asia

> [ ] Eastern Europe

> [ ] Northern Europe

> [ ] Northern Africa

> [ ] Middle East

> [ ] Southern Europe

> [ ] South America

> [ ] Central America

> [ ] Central Europe

> [ ] North America

> [ ] Western Europe

Move left, right, up, down using the arrow keys

--------------------------------------------------------------------------------

Esc-2_Continue F3_Go Back F5_Exit F6_Help

Step 14. Move the cursor down to the proper region and press <Enter>.

Done


Page 34 of 51

For North America the screen will change like this:

- Select Geographic Regions ----------------------------------------------------

Select the geographic regions for which support should be installed.

> [ ] Australasia

> [ ] Asia

> [ ] Eastern Europe

> [ ] Northern Europe

> [ ] Northern Africa

> [ ] Middle East

> [ ] Southern Europe

> [ ] South America

> [ ] Central America

> [ ] Central Europe

V [ ] North America

[ ] Canada-English (ISO8859-1)

[ ] Canada-French (ISO8859-1)

[ ] French

[ ] Mexico (ISO8859-1)

[ ] Spanish

Press Return to hide components

--------------------------------------------------------------------------------



Done


Page 35 of 51


- Select System Locale ---------------------------------------------------------

Select the initial locale to be used after the system has been installed.

[X] POSIX C ( C )

--------------------------------------------------------------------------------


Step 16 Press <Esc 2>

Done


Page 36 of 51


- Select Products --------------------------------------------------------------

Select the products you would like to install.

> [ ] Solaris 10 Extra Value Software................. 0.00 MB

> [ ] Java Enterprise System.......................... 0.00 MB

Move left, right, up, down using the arrow keys

--------------------------------------------------------------------------------

Esc-2_Continue F3_Go Back Esc-4_Product Info F5_Exit F6_Help


Done


Page 37 of 51


- Additional Products ----------------------------------------------------------

To scan for additional products, select the location you wish to scan.

Products found at the selected location that are in a Web Start Ready

install form will be added to the Products list.

Web Start Ready product scan location:

[X] None

[ ] CD/DVD

[ ] Network File System

--------------------------------------------------------------------------------

Esc-2_Continue F3_Go Back F5_Exit


Done


Page 38 of 51


- Analyzing System -------------------------------------------------------------

The Solaris software on the system is being analyzed for the upgrade.

Analyzing System...

|

0 100

Please wait ...

Step 19. Just wait.

Done


Page 39 of 51


- Customize Software? ----------------------------------------------------------

Do you want to customize (add or delete) software for the upgrade? By

default, the existing software on the system will be upgraded.

--------------------------------------------------------------------------------

Esc-2_Continue F3_Go Back F4_Customize F5_Exit


Done


Page 40 of 51


- Profile ----------------------------------------------------------------------

The information below is your profile which shows how Solaris software will

be installed. It is a summary of the choices you've made on previous

screens.

============================================================================

Installation Option: Upgrade

Boot Device: Boot Device:

Upgrade Target: Solaris 10 c1t0d0s0

System Locale: C ( C )

Software: Solaris 10, Core System Support

--------------------------------------------------------------------------------

F2_Upgrade F4_Change F5_Exit F6_Help


Done


Page 41 of 51


- Upgrading Solaris Software - Progress ----------------------------------------

The Solaris software is now being upgraded on the system using the profile

you created. Upgrading Solaris software can take several hours depending on

the software configuration, the reallocation of any space if needed, and the

speed of the installation media.

When Solaris software is completely upgraded, the message `Upgrade complete'

will be displayed.

Upgrading...

|

100

Step 22. Just wait.

Done

Now the upgrade is in progress.

When the percentage of completion will reach 100 a set of log files will be presented.


Page 42 of 51

This list will appear:

Preparing system for Solaris upgrade

- Environment variables (/etc/default/init)

Installation log location

- /a/var/sadm/system/logs/upgrade_log (before reboot)

- /var/sadm/system/logs/upgrade_log (after reboot)

Please examine the file:

- /a/var/sadm/system/data/upgrade_cleanup

It contains a list of actions that may need to be performed to complete the upgrade. After this system is rebooted, this file can be found at:

- /var/sadm/system/data/upgrade_cleanup

Upgrade complete

Executing SolStart postinstall phase...

Executing finish script "patch_finish"...

Finish script patch_finish execution completed.

Executing JumpStart postinstall phase...

The begin script log 'begin.log' is located in /var/sadm/system/logs after reboot.

The finish script log 'finish.log' is located in /var/sadm/system/logs after reboot.

Step 23 No action needed.

Done


Page 43 of 51

The following information will appear:

Launching installer. Please Wait...

Installing Additional Software

|-1%--------------25%-----------------50%-----------------75%--------------100%|

Pausing for 30 seconds at the "Summary" screen. The wizard will continue to

the next step unless you select "Pause". Enter 'p' to pause. Enter 'c' to

continue. [c]

Step 24 Hit <Enter> (or wait 30 seconds)

Done

The following information will appear:

Pausing for 90 seconds at the "Reboot" screen. The wizard will continue to

the next step unless you select "Pause". Enter 'p' to pause. Enter 'c' to

continue. [c]

Step 25. Hit <Enter> (or wait 90 seconds)

Done

NOTE: The two steps above might be disregarded because the default action in case of no-answer corresponds to what is needed, ending with a reboot. The procedure will continue, if no answer is given, in 30 seconds for the first request, 90 seconds for the second one.

The rebooting procedure is reported:

syncing file systems... done rebooting...


Page 44 of 51

Step 26 Log into the node as root using the console

Done

Step 27 If a warning about the ‘network/ssh:default’ service appears on the console:

Feb 6 14:13:30 svc.startd[7]: svc:/network/ssh:default: Method "/lib/svc/method/sshd start" failed with exit status 1.

This can be safely disregarded. The BTS uses its own ssh package. To avoid seen this report just execute:

# svcadm disable /network/ssh:default

Done N/A

Step 28 Continue with the Install Core CD. Mount the CD using the following command:


NOTE: if /cdrom does not exist (this directory was created at jumpstart) it must be created by executing the following command:

# mkdir /cdrom


Done

Step 29 Execute the following command

#

cd /

# /cdrom/core_finish/upgrade_finish.sh

This procedure will be aborted if the working directory is not root (‘/’). If this happens it will be possible to redo this procedure from the root directory.

Wait for this procedure to finish: at the end the CD will be ejected and the system will reboot automatically. There will be no request.

Done

After the system reboots the following BTS Finish upgrade procedure must be executed.


Page 45 of 51

BTS Finish Upgrade Procedure

This section describes how to finish upgrading Solaris 10 operating system on the Cisco

BTS 10200 Softswitch platforms for both the EMS and CA node types. You must execute the following procedure for each of the four nodes in the BTS10200 Softswitch.

After the execution of the OS Core Upgrade procedure follow these steps:

Step 1 Login on console using user name root and password the BTS root password.

Done

Step 2 Insert the Cisco Solaris 10 Install - Finish CD into the CD-ROM drive

Done

Step 3 Mount the CD using the following command:



Done

Step 4 Execute the following two commands

#

cd /cdrom/bts_common

# ./bts_upgrade.sh

Done

Step 5 Execute the following commands (notice the tilde ‘~ ‘ character)

#

cd /usr/bin

# mv date~10 date

# mv rdate~10 rdate

Done

Step 6 Undo the change made in /etc/rc3.d at the beginning of the upgrade procedure.

#

mv /etc/rc3.d/saved.S99platform /etc/rc3.d/S99platform

Done

Step 7 If this is a CallAgent node go to step 8.

Done N/A

Step 8 On the EMS nodes execute the Oracle relink procedure as described in the:

“BTS Oracle Engine Binaries Relink”

document.

Done N/A


Page 46 of 51

Step 9 Reboot the node:


Done

Step 10 Remove the Cisco Solaris 10 Install - Finish CD from the CD-ROM

Done


Page 47 of 51

6. Appendix A: Mirroring the Disks

NOTE: The following procedure for mirroring disks is necessary for field installations.

The same is true for lab systems which require mirrored disks. This procedure must then be executed on both EMS nodes and both CA nodes.

In case of an OS upgrade, to determine if disk-mirroring is configured, use:

# metastat

If the command reports “there are no existing databases” no disk mirroring is in place.

Step 1 Change directory to /opt/setup

# cd /opt/setup

Done

Step 2 Set up the mirror for each EMS by entering the following command on the EMS node

#./setup_mirror_ems

Set up the mirror for each CA by entering the following command on the CA node.

#./setup_mirror_ca

Done

Note: Do not reboot your system if an error occurs. You must fix the error before moving to the next step.

Step 3 Reboot by entering the following command:

# reboot -- -r

Note: Wait for the boot before continuing. Then log in to the node which you are working.

Done


Page 48 of 51

Step 4 Log in as root.

Done

Step 5 Change directory to /opt/setup

# cd /opt/setup

Done

Step 6 Synchronize the disk by entering the following command: (using nohup is an option and since the operation could take 2 to 3 hours, is recommended)

# nohup ./sync_mirror &

Note: Wait for the disks to synchronize before continuing. It takes 2 to 2.5 hours to complete the disk mirroring process on each machine.

Please run

“/opt/utils/Resync_status

” to check for the disk mirroring status

.

The display will show the resyncing in progress and report resync completion.

Done

Step 7 Exit the primary EMS or CA node.

Done


Page 49 of 51

7. Appendix B: Setting the

Time Zone

The /etc/TIMEZONE file contains the entry for the time zone used in determining the local time. The system must be rebooted for a time zone change to take effect.

By default, the TZ variable is set as follows

TZ=US/Central

Valid values for TZ can be found in the directory structure under

/usr/share/lib/zoneinfo

. The following values are valid for the US:

ls /usr/share/lib/zoneinfo/US

Alaska Central Hawaii Mountain Samoa

Aleutian East-Indiana Indiana-Starke Pacific

Arizona Eastern Michigan Pacific-New

The following values are valid for Europe.

ls /usr/share/lib/zoneinfo/Europe

Amsterdam Brussels Helsinki Luxembourg Nicosia San_Marino Tirane

Warsaw

Andorra Bucharest Istanbul Madrid Oslo Sarajevo Tiraspol Zagreb

Athens Budapest Kaliningrad Malta Paris Simferopol Uzhgorod

Zaporozhye

Belfast Chisinau Kiev Mariehamn Prague Skopje Vaduz Zurich

Belgrade Copenhagen Lisbon Minsk Riga Sofia Vatican

Berlin Dublin Ljubljana Monaco Rome Stockholm Vienna

Bratislava Gibraltar London Moscow Samara Tallinn Vilnius

To change the time zone to US Pacific time change

TZ=US/Pacific

To change the time zone to Europe London time change

TZ=Europe/London


Page 50 of 51

8. Appendix C: Where to mount a CD

If the following command fails:

# mount –F hsfs –o ro /dev/dsk/c0t0d0s0 /cdrom it is very likely the case of a device sequencing arranged in an unusual order.

To determine what device to use, run this command as root:

# ls –l /dev/dsk | grep ide

An example of the output: lrwxrwxrwx 1 root root 45 Apr 20 11:32 c2t0d0s0 -> ../../devices/pci@1f,0/pci@1,1/ide@d/sd@0,0:a lrwxrwxrwx 1 root root 45 Apr 20 11:32 c2t0d0s1 -> ../../devices/pci@1f,0/pci@1,1/ide@d/sd@0,0:b lrwxrwxrwx 1 root root 45 Apr 20 11:32 c2t0d0s2 -> ../../devices/pci@1f,0/pci@1,1/ide@d/sd@0,0:c lrwxrwxrwx 1 root root 45 Apr 20 11:32 c2t0d0s3 -> ../../devices/pci@1f,0/pci@1,1/ide@d/sd@0,0:d lrwxrwxrwx 1 root root 45 Apr 20 11:32 c2t0d0s4 -> ../../devices/pci@1f,0/pci@1,1/ide@d/sd@0,0:e lrwxrwxrwx 1 root root 45 Apr 20 11:32 c2t0d0s5 -> ../../devices/pci@1f,0/pci@1,1/ide@d/sd@0,0:f lrwxrwxrwx 1 root root 45 Apr 20 11:32 c2t0d0s6 -> ../../devices/pci@1f,0/pci@1,1/ide@d/sd@0,0:g lrwxrwxrwx 1 root root 45 Apr 20 11:32 c2t0d0s7 -> ../../devices/pci@1f,0/pci@1,1/ide@d/sd@0,0:h

The device to use will be the first one, the one ending with ‘s0’.

In the example above the mount command would change this way:



Page 51 of 51

Cisco BTS 10200 Softswitch Solaris OS Install/Upgrade Procedure

Cisco BTS 10200 Softswitch

Solaris OS Install/Upgrade Procedure for Solaris 10 Version 0606

Revision History

Table of Contents

Preface

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Web Site

Cisco TAC Escalation Center

1. Overview

Supported Hardware and Firmware

2. Precautions

3. Prerequisite Checklist

BTS Oracle Engine Binaries

Relink”

4. New OS Install

OS Core Installation Procedure

BTS-Finish Procedure

Setting Up the Network Configuration Files

Configuring the Element Management System

Configuring the Call Agent and Feature Server Installation

5. OS Upgrade

OS Core Upgrade Procedure

BTS Finish Upgrade Procedure

“BTS Oracle Engine Binaries Relink”

6. Appendix A: Mirroring the Disks

7. Appendix B: Setting the

Time Zone

8. Appendix C: Where to mount a CD

Related manuals

Cisco BTS 10200 Softswitch Solaris OS Install/Upgrade Procedure