Migrating to Solaris 10 and Cisco PGW 2200 Softswitch Release 9.7

Transcription

1 CHAPTER 5 Migrating to Solaris 10 and Cisco PGW 2200 Softswitch Release 9.7 Revised: May 18, 2011, This chapter describes how to migrate your PGW 2200 to the Solaris 10 operating system and Cisco PGW 2200 Softswitch Release 9.7 software. This chapter contains the following information: Conditions for Migration, page 5-1 Cautions and s, page 5-2 Required Software, page 5-3 Recording System Data, page 5-3 Migration Overview, page 5-4 Migrating the Second PGW to Cisco PGW 2200 Softswitch Release 9.7, page 5-4 Migrating the First PGW to Cisco PGW 2200 Softswitch Release 9.7, page 5-14 Falling Back to Solaris 8, page 5-25 Replacing Hard Disks on an Existing Solaris 10 Platform, page 5-30 Upgrading Lively from Sparc-based Platforms to Opteron-based Platforms, page 5-32 Conditions for Migration Your hardware and software environment must meet the following conditions before you can use the procedures provided below to migrate your software to Solaris 10: Your system must have at least two disks. If you plan to replace the PGW hard disks during the upgrade, ensure that you have two replacement disks. The disks in the system must be at least 18 GB in size. You (or the person doing the upgrade) must be an experienced Solaris system administrator. You must be familiar with system administration tasks such as mounting file systems and running tar to save and restore files. Use Table 5-1 to determine the appropriate steps to upgrade your system. 5-1

2 Cautions and s Chapter 5 Migrating to Solaris 10 and Cisco PGW 2200 Softswitch Release 9.7 Table 5-1 Solaris 10 and Cisco PGW 2200 Softswitch Release 9.7 Migration Procedures Condition If you are upgrading the disk drive but not upgrading the software... Action Follow the procedure in the Replacing Hard Disks on an Existing Solaris 10 Platform section on page If you are migrating from Solaris 8 to Solaris You must install the Sun Solaris 10 Operating System and Cisco PGW 2200 Softswitch Release 9.7 software on your PGW 2200 platform. If you are migrating from the old Sparc-based platforms to the new Opteron-based platforms Follow the procedure in the Upgrading Lively from Sparc-based Platforms to Opteron-based Platforms section on page 5-32 Cautions and s Before starting the upgrade, consider the following cautions and notes: Caution Before starting the upgrade, make sure the Cisco PGW 2200 Softswitch software is shut down, and the system administrator is logged in as root. Caution Always start the migration or upgrade from the standby PGW host. Caution Resolve any major alarms on the PGW before proceeding with the upgrade or migration. Caution Do not make any provisioning changes to the PGW during the upgrade to the Cisco PGW 2200 Softswitch Release 9.7 software. Caution When upgrading a redundant system, verify that the pom.datasync parameter (located in /opt/ciscomgc/etc/xecfgparm.dat) is set to false on both PGW hosts in order to maintain calls and preserve your configuration. The Cisco PGW 2200 softswitch supports a live upgrade from the Sparc-based platforms to the Opteron-based platforms. There is no service outrage during the upgrade. For detailed procedure of this live upgrade, see the Upgrading Lively from Sparc-based Platforms to Opteron-based Platforms section on page

3 Required Software Required Software You must have the following software: Cisco Solaris 10 Operating System Jumpstart Disk. There are two versions of this disk, one for each of the supported platform types. If your host platform is a Sun Fire V40z, a Sun Fire X4600, or a Sun Netra X4200 M2, use the Cisco Solaris 10 Operating System Jumpstart Disk for Opteron-based Platforms. Otherwise, use the Cisco Solaris 10 Operating System Jumpstart Disk for Sparc-based Platforms. Cisco Solaris 10 Operating Environment CD. The latest version of the version is available at: (Sparc platform) (Opteron platform) Cisco Installation CD, which includes the new release of the Cisco PGW 2200 Softswitch software. For information on latest patches, see the Release s for the Cisco PGW 2200 Softswitch Release 9.7(3) at License Installation Before you begin installation, obtain and install an Cisco PGW 2200 Softswitch license file using the instructions provided in Installing the License File, page Recording System Data When you upgrade to Sun Solaris 10, you must reenter various elements of your system data, because the installation overwrites your existing system data. To ensure that you have all of your system data, record the contents of the following files: /etc/default /etc/defaultrouter Hostname files for each interface (such as /etc/hostname.hme0 or /etc/hostname.bge0) /etc/hosts.equiv /etc/group /etc/nsswitch.conf /etc/passwd /etc/resolv.conf /etc/shadow /etc/inet/hosts /etc/inet/netmasks /etc/inet/ntp.conf 5-3

4 Migration Overview Chapter 5 Migrating to Solaris 10 and Cisco PGW 2200 Softswitch Release 9.7 You may have already recorded some of this information based on the Required Site-Specific Information section on page 1-3 and the Required Machine-Specific Information section on page 1-3. Migration Overview In order to migrate to Release 9.7 of the Cisco PGW 2200 Softswitch software, you need to install the 9.7 software on both the active and standby PGW hosts. During the migration procedure, you must set each host to both active and standby. For clarity, the PGWs are labeled PGW 1 and PGW 2. PGW host 1 is the host that is active at the beginning of the procedure, and PGW host 2 is the host that is set to standby at the beginning of the procedure. Figure 5-1 PGW Host Labeling 1 Active PGW host Cisco ITP-L 2 Standby PGW host STP PSTN STP Bearer traffic V Voice Gateway QoS packet network Migrating the Second PGW to Cisco PGW 2200 Softswitch Release 9.7 Use the steps in the following sections to upgrade PGW 2 to Cisco PGW 2200 Softswitch Release 9.7. If you want to use two new disk drives to install the Cisco PGW 2200 Softswitch 9.7 software, complete the Installing Sun Solaris 10 and Loading the Sun Solaris 10 Operating Environment Packages sections before you begin this procedure. Backing Up the Cisco PGW 2200 Softswitch Configuration Files Before you begin the migration to the new version of the Cisco PGW 2200 Softswitch software, you need to back up your current system files. This section describes the following backup procedures: 5-4

5 Migrating the Second PGW to Cisco PGW 2200 Softswitch Release 9.7 Create a remote backup of the current Cisco PGW 2200 Softswitch configuration using the mgcbackup utility. These backup files are used to revert to the original version of the Cisco PGW 2200 Softswitch software if a problem occurs during migration. Create an MGC.tar archive file of the current Cisco PGW 2200 Softswitch settings. Follow these steps to back up the Cisco PGW 2200 Softswitch configuration files on PGW host 2: Step 1 Verify that the pom.datasync variable is set to False on the active and standby PGW hosts. To view or modify the pom.datasync variable, use an editor such as vi to edit /opt/ciscomgc/etc/xecfgparm.dat. Step 2 Step 3 Step 4 If you modify the pom.datasync variable, restart the active and standby PGW hosts sequentially to ensure that the changes take effect. Log in to the PGW host 2 as mgcusr. Enter the following command to stop the PGW. % sudo /etc/init.d/ciscomgc stop Follow these steps to back up the system: a. Local Tape Backup Using the mgcbackup utility, back up the system to the local tape drive. % /opt/ciscomgc/local/mgcbackup d /dev/rmt/0 b. Remote File Server Backup Type the following commands to use the mgcbackup utility to back up the system to local directory. % mkdir /var/tmp/upgrade % cd /var/tmp/upgrade % /opt/ciscomgc/local/mgcbackup d /var/tmp/upgrade The backup file is stored in the specified directory path in the following format: mgc_<hostname>_<yyyymmdd>_<hhmmss>_backup Where: hostname is the name of the Cisco PGW 2200 Softswitch host, such as MGC-01. yyyymmdd is the date the backup file is created, in a year-month-day format, such as hhmmss is the time the backup file is created, in an hour-minute-second format, such as c. Type the following command to list the files in your backup directory. Verify that the backup was successful. % /opt/ciscomgc/local/mgcbackup -l Caution You must now move the backup file to a remote file server using the ftp program so it can be recovered if you need to revert to the previous version of Solaris or PGW software. You are responsible for providing the mechanism and storage location. 5-5

6 Migrating the Second PGW to Cisco PGW 2200 Softswitch Release 9.7 Chapter 5 Migrating to Solaris 10 and Cisco PGW 2200 Softswitch Release 9.7 Step 5 Stop TimesTen database replication on PGW hosts 1 and 2: %./delete_replication.sh Step 6 Go to Step 7 if you are migrating to a Sparc platform. If you are migrating from Sparc to Opteron, use the following command to back up the Main Memory Database (MMDB) on the PGW host 2. % mgcttmigrate export ttbackup.tar Make sure there is no active provision on the PGW host 2 before you use mgcttmigrate to back up the MMDB. To make sure that you use the latest version of the mgcttmigrate script, download the mgcttmigrate script from Cisco.com every time before you use it. Step 7 Follow these steps to back up the MMDB on the PGW host 2: a. Log in to the PGW host 2 as mgcusr. b. Create the export.ttdb file: % /opt/ciscomgc/local/backupdb.sh /opt/ciscomgc/etc/export.ttdb c. Create the migrate.ttdb file: % ttmigrate -c DSN=howdydb /opt/ciscomgc/etc/migrate.ttdb d. Remove the existing version of the MMDB file: % rm -f /opt/ciscomgc/etc/version.ttdb e. Determine the version of the version.ttdb file: % /opt/timesten/32/bin/ttversion presenter The PGW displays output similar to the following example: [ output = "TimesTen Release x.y.z build time... ] f. Replace the TimesTen database Release x.y.z with the new version: % echo xyz >/opt/ciscomgc/etc/version.ttdb g. Ensure that the version.ttdb, migrate.ttdb, and export.ttdb files are present: % cd /opt/ciscomgc/etc % ls *.ttdb Step 8 Step 9 Log in to the PGW host 2 as root. Save the Cisco PGW 2200 Softswitch configuration data: % cp /opt/ciscomgc/snmp/snmpd.cnf /opt/ciscomgc/dialplan Step 10 If you are using Cisco MNM, save the snmpd.cnf file (located in /opt/ciscomgc/snmp) before the migration starts. Move to the Cisco MGC directory: % cd /opt/ciscomgc 5-6

7 Migrating the Second PGW to Cisco PGW 2200 Softswitch Release 9.7 Step 11 Step 12 Step 13 Back up the current MGC files: % tar cvf /var/tmp/upgrade/mgc.tar./etc./dialplan % cp./local/ttbackup.tar /var/tmp/upgrade/ttbackup.tar Verify that configuration files were successfully backed up. The mgc_<hostname>_<yyyymmdd>_<hhmmss>_backup file, ttbackup.tar, and MGC.tar files must be present. % cd /var/tmp/upgrade % ls At this point, you have saved all the required data in tar files in /var/tmp/upgrade. Follow these steps to move these files to a blank tape or remote machine so that you can recover them after installing Solaris 10. Caution You are responsible for providing the backup mechanism and storage location. a. Local tape drive Enter the following commands to store the files on a local tape drive: % cd /var/tmp/upgrade % tar cvf /dev/rmt/0 MGC.tar ttbackup.tar mgc_mgc-01_ _115923_backup.tar b. Remote file server Using the ftp utility, transfer the MGC.tar and ttbackup.tar files from the /var/tmp/upgrade directory to a remote file server. Use the binary mode of ftp to transfer the MGC.tar and ttbackup.tar files. Step 14 Verify that the files are successfully transferred to the remote file server before continuing. At this point, the Cisco PGW 2200 Softswitch configuration data has been saved in MGC.tar files on a tape or remote file server. The file backup is now complete. Proceed to Installing Sun Solaris 10. Installing Sun Solaris 10 Follow these steps to install Sun Solaris 10 on PGW host 2. If you want to use two new disk drives to install the Cisco PGW 2200 Softswitch Release 9.7 software, you can use the original disk drives to revert to the previous Cisco PGW 2200 Softswitch version if there is a problem during the upgrade procedure. For instructions on how to revert to the previous Cisco PGW 2200 Softswitch version, refer to Falling Back to Solaris 8. If you are upgrading from the primary disk, use Veritas Volume Manager to use the second disk for Solaris 8 fallback. For further information, refer to me_manager/index.html. 5-7

8 Migrating the Second PGW to Cisco PGW 2200 Softswitch Release 9.7 Chapter 5 Migrating to Solaris 10 and Cisco PGW 2200 Softswitch Release 9.7 Step 1 Shut down PGW host 2: init 0 Step 2 Wait for the system to return to the boot prompt and load the Cisco Solaris 10 Operating System Startup CD in the CD-ROM drive. If you are replacing the disk drives, power off the system and label, and remove the existing disks, using proper anti-static procedures. Install the new disk drives in the same slots the original disk drives were located. Finally, power up the system. For more information, see the Sun System Manual for your platform. Step 3 Install the Sun Solaris 10 operating system using the procedures in the Loading the Sun Solaris 10 Operating System section on page 2-3. Caution Do not format or modify the second disk drive. Unless you replaced the disk drives in Step 2, the second disk contains the original Solaris 8 system if you are using Veritas Volume Manager. The second disk is used as a fallback in case of a failure in the Solaris 10 upgrade. Loading the Sun Solaris 10 Operating Environment Packages Before you install the Cisco PGW 2200 Softswitch software, load the Sun Solaris 10 Operating Environment packages using the steps in the Loading the Sun Solaris 10 Operating Environment section. Caution Do not load Solstice DiskSuite (CSCOh023) if you are using Veritas Volume Manager to use the second disk for Solaris 8 fallback. For more information about Veritas Volume Manager, refer to me_manager/index.html. Restoring Data Files Follow these instructions to restore the Cisco PGW 2200 Softswitch configuration files (MGC.tar) on PGW host 2: Step 1 Step 2 Step 3 Log in as root and move the Cisco PGW 2200 Softswitch configuration files to the /tmp directory. # cd /var/tmp Create a mount point. # mkdir saved # cd /var/tmp/saved Store the data files: a. Local tape drive Store the files on a local tape drive. 5-8

9 Migrating the Second PGW to Cisco PGW 2200 Softswitch Release 9.7 # tar xvf /dev/rmt/0 b. Remote file server Using the ftp utility, transfer the MGC.tar and ttbackup.tar files from the remote file server to the /tmp/saved directory. Step 4 Step 5 Step 6 Step 7 Step 8 Use the binary mode of ftp to transfer the MGC.tar and ttbackup.tar files. Verify that the files successfully transfer to the remote file server before continuing. Create an MGC directory and extract Cisco MGC data files: # cd /opt # mkdir CiscoMGC # Create MGC directory # cd /opt/ciscomgc # mkdir snmp # Create snmp directory # cp /var/tmp/saved/mgc.tar MGC.tar # tar xvf MGC.tar # Extract MGC data files # mkdir local # Create snmp directory # cp /var/tmp/saved/ttbackup.tar./local/ttbackup.tar Verify that the etc and dialplan directories are present. If you saved the snmpd.cnf file, copy the file to the /opt/ciscomgc/snmp directory: # cp /opt/ciscomgc/dialplan/snmpd.cnf /opt/ciscomgc/snmp If you are migrating your PGW system from the Sparc platform to the Opteron platform, remove the.bin files from the /opt/ciscomgc/dialplan, /opt/ciscomgc/etc, and active_link directories: # rm /opt/ciscomgc/dialplan/*.bin # rm /opt/ciscomgc/etc/*.bin # rm /opt/ciscomgc/etc/active_link/*.bin # rm /opt/ciscomgc/etc/export.ttdb # If file exists # rm /opt/ciscomgc/etc/migrate.ttdb # If file exists # rm /opt/ciscomgc/etc/version.ttdb # If file exists Step 9 Complete this step only if you are migrating from the Sparc platform to the Opteron platform. Type the following command to reboot the PGW: # init 6 Installing and Verifying the Cisco PGW 2200 Softswitch Software Follow these steps to install the Cisco PGW 2200 Softswitch software on PGW host 2: Step 1 Install the Cisco PGW 2200 Softswitch software using the instructions in Installing the Cisco PGW 2200 Softswitch Software Release 9.7 and Higher. Step 2 When the installation is complete, perform the following steps on PGW host 2: Step 3 Step 4 Log into PGW host 2 as mgcusr. If you are migrating from the Sparc platform to the Opteron platform, complete the following steps: 5-9

10 Migrating the Second PGW to Cisco PGW 2200 Softswitch Release 9.7 Chapter 5 Migrating to Solaris 10 and Cisco PGW 2200 Softswitch Release 9.7 If you are migrating to a Sparc platform, skip to Step 5. a. Enter the following commands to start the TimesTen database. % cd /opt/ciscomgc/local % sudo /etc/init.d/tt start The tt60 daemon has started successfully. b. Run the db_count.sh script to verify that the TimesTen database is empty. % db_count.sh Counting the rows in each database table. CISCO.ANNOUNCEMENT < 0 > CISCO.A_CHARGE_ORIGIN < 0 > CISCO.A_NUMBERDIALPLANSELECTION < 0 > CISCO.BLACKLIST_A < 0 > CISCO.BLACKLIST_B < 0 > CISCO.CBBOOKINGINFO < 0 > CISCO.CBMONITORINGINFO < 0 > CISCO.CLIIPADDRESS < 0 > CISCO.CLIPREFIX < 0 > CISCO.FULLNUMBERTRANSLATION < 0 > CISCO.H323IDDIVFROM < 0 > CISCO.LIENTRIES < 0 > CISCO.NUMBERTERM < 0 > CISCO.PORTEDNUMBERS < 0 > CISCO.SCRIPT < 0 > CISCO.WHITELIST_A < 0 > CISCO.WHITELIST_B < 0 > c. Import the TimesTen database from the ttbackup.tar file. %./mgcttmigrate import ttbackup.tar #!/opt/ciscomgc/bin/perl #*************** CISCO Copyright Notice ********************^M CiscoMGC Timesten Database Migration Script. Checking System & Application information... Checking System & Application information...passed Start import Timesten Database... Uncompressing backup file... x /opt/ciscomgc/local/ttbulkbak, 0 bytes, 0 tape blocks x /opt/ciscomgc/local/ttbulkbak/export.ttdb, bytes, 78 tape blocks x /opt/ciscomgc/local/ttbulkbak/cisco.announcement.dat, 307 bytes, 1 tape blocks x /opt/ciscomgc/local/ttbulkbak/cisco.a_charge_origin.dat, 214 bytes, 1 tape blocks x /opt/ciscomgc/local/ttbulkbak/cisco.a_numberdialplanselection.dat, 228 bytes, 1 tape blocks x /opt/ciscomgc/local/ttbulkbak/cisco.blacklist_a.dat, 181 bytes, 1 tape blocks x /opt/ciscomgc/local/ttbulkbak/cisco.blacklist_b.dat, 213 bytes, 1 tape blocks x /opt/ciscomgc/local/ttbulkbak/cisco.cbbookinginfo.dat, 245 bytes, 1 tape blocks x /opt/ciscomgc/local/ttbulkbak/cisco.cbmonitoringinfo.dat, 281 bytes, 1 tape blocks x /opt/ciscomgc/local/ttbulkbak/cisco.cliipaddress.dat, 210 bytes, 1 tape blocks x /opt/ciscomgc/local/ttbulkbak/cisco.cliprefix.dat, 207 bytes, 1 tape blocks x /opt/ciscomgc/local/ttbulkbak/cisco.cmdgroup.dat, 2008 bytes, 4 tape blocks x /opt/ciscomgc/local/ttbulkbak/cisco.h323iddivfrom.dat, 211 bytes, 1 tape blocks x /opt/ciscomgc/local/ttbulkbak/cisco.lientries.dat, 303 bytes, 1 tape blocks x /opt/ciscomgc/local/ttbulkbak/cisco.namedinputparams.dat, 2514 bytes, 5 tape blocks 5-10

11 Migrating the Second PGW to Cisco PGW 2200 Softswitch Release 9.7 x /opt/ciscomgc/local/ttbulkbak/cisco.namedoutputparams.dat, 1521 bytes, 3 tape blocks x /opt/ciscomgc/local/ttbulkbak/cisco.namedsql.dat, 9350 bytes, 19 tape blocks x /opt/ciscomgc/local/ttbulkbak/cisco.numberterm.dat, 210 bytes, 1 tape blocks x /opt/ciscomgc/local/ttbulkbak/cisco.portednumbers.dat, 181 bytes, 1 tape blocks x /opt/ciscomgc/local/ttbulkbak/cisco.schema_version.dat, 286 bytes, 1 tape blocks x /opt/ciscomgc/local/ttbulkbak/cisco.script.dat, 277 bytes, 1 tape blocks x /opt/ciscomgc/local/ttbulkbak/cisco.whitelist_a.dat, 181 bytes, 1 tape blocks x /opt/ciscomgc/local/ttbulkbak/cisco.whitelist_b.dat, 213 bytes, 1 tape blocks x /opt/ciscomgc/local/ttbulkbak/dbversion.dat, 6 bytes, 1 tape blocks x /opt/ciscomgc/local/ttbulkbak/mgcversion.dat, 6 bytes, 1 tape blocks x /opt/ciscomgc/local/ttbulkbak/etcversion.dat, 7 bytes, 1 tape blocks x /opt/ciscomgc/local/ttbulkbak/platform.dat, 6 bytes, 1 tape blocks Uncompressing backup file finished. Checking System-information Prev Platform : sparc System Platform : i Prev DBversion : System DBversion : Prev ConfigVer : System ConfigVer : Prev MGC Ver : System MGC Ver : Warning:System-info check failed. if you just forget run this script before start CiscoMGC with Auto-migration press[y]. else press[n] exit Timesten Migration,And seek help to resolve the problem. y Import databse from 96001sparc to 97003i386 Starting backup exist-timesten Database... Backup Database completed... Destroy Prev-Timesten DataBase successed. Different Platform,Using blukcp import the database... Starting Create Timesten Structure... Create TimesTen Structure successed. /opt/ciscomgc/local/ttbulkbak/cisco.announcement.dat: 0 rows inserted 0 rows total /opt/ciscomgc/local/ttbulkbak/cisco.a_charge_origin.dat: 0 rows inserted 0 rows total /opt/ciscomgc/local/ttbulkbak/cisco.a_numberdialplanselection.dat: 0 rows inserted 0 rows total /opt/ciscomgc/local/ttbulkbak/cisco.blacklist_a.dat: 0 rows inserted 0 rows total /opt/ciscomgc/local/ttbulkbak/cisco.blacklist_b.dat: 0 rows inserted 0 rows total /opt/ciscomgc/local/ttbulkbak/cisco.cbbookinginfo.dat: 0 rows inserted 5-11

12 Migrating the Second PGW to Cisco PGW 2200 Softswitch Release 9.7 Chapter 5 Migrating to Solaris 10 and Cisco PGW 2200 Softswitch Release rows total /opt/ciscomgc/local/ttbulkbak/cisco.cbmonitoringinfo.dat: 0 rows inserted 0 rows total /opt/ciscomgc/local/ttbulkbak/cisco.cliipaddress.dat: 0 rows inserted 0 rows total /opt/ciscomgc/local/ttbulkbak/cisco.cliprefix.dat: 0 rows inserted 0 rows total /opt/ciscomgc/local/ttbulkbak/cisco.cmdgroup.dat: 115 rows inserted 115 rows total /opt/ciscomgc/local/ttbulkbak/cisco.h323iddivfrom.dat: 0 rows inserted 0 rows total /opt/ciscomgc/local/ttbulkbak/cisco.lientries.dat: 0 rows inserted 0 rows total /opt/ciscomgc/local/ttbulkbak/cisco.namedinputparams.dat: 194 rows inserted 194 rows total /opt/ciscomgc/local/ttbulkbak/cisco.namedoutputparams.dat: 109 rows inserted 109 rows total /opt/ciscomgc/local/ttbulkbak/cisco.namedsql.dat: 87 rows inserted 87 rows total /opt/ciscomgc/local/ttbulkbak/cisco.numberterm.dat: 0 rows inserted 0 rows total /opt/ciscomgc/local/ttbulkbak/cisco.portednumbers.dat: 0 rows inserted 0 rows total /opt/ciscomgc/local/ttbulkbak/cisco.schema_version.dat: 6 rows inserted 6 rows total /opt/ciscomgc/local/ttbulkbak/cisco.script.dat: 0 rows inserted 0 rows total /opt/ciscomgc/local/ttbulkbak/cisco.whitelist_a.dat: 0 rows inserted 0 rows total /opt/ciscomgc/local/ttbulkbak/cisco.whitelist_b.dat: 0 rows inserted 0 rows total Import the database successed. Import version:96001!= System version:97003 Starting Timesten Migration... Migrate /opt/ciscomgc/etc/migrate/migrate_9.7001_ sql successed. 5-12

13 Migrating the Second PGW to Cisco PGW 2200 Softswitch Release 9.7 Migrate /opt/ciscomgc/etc/migrate/migrate_9.7002_ sql successed. Timesten Migration successed. Timesten import completed successfully. d. Run the db_count.sh script to verify that the TimesTen database has been imported. % db_count.sh Counting the rows in each database table. CISCO.ANNOUNCEMENT < 1001 > CISCO.A_CHARGE_ORIGIN < 1001 > CISCO.A_NUMBERDIALPLANSELECTION < 6 > CISCO.BLACKLIST_A < 1001 > CISCO.BLACKLIST_B < 1002 > CISCO.CBBOOKINGINFO < 0 > CISCO.CBMONITORINGINFO < 0 > CISCO.CLIIPADDRESS < 1000 > CISCO.CLIPREFIX < 9 > CISCO.FULLNUMBERTRANSLATION < 0 > CISCO.H323IDDIVFROM < 1002 > CISCO.LIENTRIES < 0 > CISCO.NUMBERTERM < 0 > CISCO.PORTEDNUMBERS < > CISCO.SCRIPT < 1000 > CISCO.WHITELIST_A < 1001 > CISCO.WHITELIST_B < 1001 > Step 5 Enter the following command to start the Cisco PGW 2200 Softswitch software on PGW host 2: % sudo /etc/init.d/ciscomgc start Step 6 If you are migrating from the Sparc platform to the Opteron platform, start a provisioning session and regenerate the.bin files: # mml>prov-sta # mml>prov-cpy Caution Complete this step only if you are migrating from the Sparc platform to the Opteron platform. Step 7 Step 8 Step 9 Verify that the migration to the 9.7 software is complete and that all protocols are operational: % rtrv-ne % rtrv-tc:all % rtrv-dest:all % rtrv-c7lnk:all % rtrv-iplnk:all Enter the following command on the standby host to verify that call replication is occurring between PGW hosts 1 and 2: rtrv-tc:all rtrv-tt-database # numan-rtrv:cliprefix:clisetname="1111",cliprefix="1" # numan-rtrv:announcement:annid=1,gwtype="as5400" # numan-rtrv:porttbl:digitstring="100034" You have now upgraded the PGW host 2 to the Release 9.7 software. Promote PGW host 2 to active: 5-13

14 Migrating the First PGW to Cisco PGW 2200 Softswitch Release 9.7 Chapter 5 Migrating to Solaris 10 and Cisco PGW 2200 Softswitch Release 9.7 This step sets PGW host 1 to standby. sw-over::confirm Step 10 When the switchover is complete, verify that PGW host 2 is processing calls. rtrv-tc:all If the call replication fails, or if new active host is not processing calls, refer to the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide. Migrating the First PGW to Cisco PGW 2200 Softswitch Release 9.7 Use the steps in the following sections to upgrade PGW 1 to Cisco PGW 2200 Softswitch Release 9.7. If you want to use two new disks drives to install the Cisco PGW 2200 Softswitch Release 9.7 software, complete the Installing Sun Solaris 10 and Loading the Sun Solaris 10 Operating Environment Packages sections before you begin this procedure. Backing Up the Cisco PGW 2200 Softswitch Configuration Files Before you begin the migration to the new version of the Cisco PGW 2200 Softswitch software, you need to back up your current system files. This section describes the following backup procedures: Create a remote backup of the current Cisco PGW 2200 Softswitch configuration using the mgcbackup utility. You can use these backup files to revert to the original version of the Cisco PGW 2200 Softswitch software if there is a problem during migration. Create an MGC.tar archive of the current Cisco PGW 2200 Softswitch settings. Follow these steps to back up the configuration files on PGW host 1: Step 1 Verify that the pom.datasync variable is set to False on both PGW hosts. To edit the pom.datasync variable, use an editor such as vi to edit /opt/ciscomgc/etc/xecfgparm.dat. Step 2 Step 3 If you modify the pom.datasync variable, restart the active and standby PGW hosts sequentially to ensure that the changes take effect. Log in to the PGW host 1 as mgcusr. Enter the following command to stop the PGW. % sudo /etc/init.d/ciscomgc stop 5-14

15 Migrating the First PGW to Cisco PGW 2200 Softswitch Release 9.7 Step 4 Follow these steps to back up the system: a. Local Tape Backup Using the mgcbackup utility, back up the system to the local tape drive. % /opt/ciscomgc/local/mgcbackup d /dev/rmt/0 b. Remote File Server Backup Enter following commands to use the mgcbackup utility to back up the system to local directory. % mkdir /var/tmp/upgrade % cd /var/tmp/upgrade % /opt/ciscomgc/local/mgcbackup d /var/tmp/upgrade The backup file is stored in the specified directory path in the following format: mgc_<hostname>_<yyyymmdd>_<hhmmss>_backup Where: hostname is the name of the Cisco PGW 2200 Softswitch host, such as MGC-01. yyyymmdd is the date the backup file is created, in a year-month-day format, such as hhmmss is the time the backup file is created, in an hour-minute-second format, such as c. Verify that the backup was successful by listing the files in your backup directory: % /opt/ciscomgc/local/mgcbackup -l Caution You must now move the backup file to a remote file server using the ftp program so it can be recovered if you need to revert the PGW to the previous version of Solaris or PGW software. You are responsible for providing the mechanism and storage location. Step 5 Stop TimesTen database replication on PGW hosts 1 and 2: %./delete_replication.sh Step 6 Go to Step 7 if you are migrating to a Sparc platform. If you are migrating from Sparc to Opteron, use the following command to back up the Main Memory Database (MMDB) on the PGW host 1. % mgcttmigrate export ttbackup.tar To make sure that you use the latest version of the mgcttmigrate script, download the mgcttmigrate script from Cisco.com every time before you use it. Step 7 Follow these steps to back up the MMDB on the PGW host 1: a. Log in to the PGW host 1 as mgcusr. b. Create the export.ttdb file: % /opt/ciscomgc/local/backupdb.sh /opt/ciscomgc/etc/export.ttdb c. Create the migrate.ttdb file: % ttmigrate -c DSN=howdydb /opt/ciscomgc/etc/migrate.ttdb d. Remove the existing version of the MMDB file: 5-15

16 Migrating the First PGW to Cisco PGW 2200 Softswitch Release 9.7 Chapter 5 Migrating to Solaris 10 and Cisco PGW 2200 Softswitch Release 9.7 % rm -f /opt/ciscomgc/etc/version.ttdb e. Determine the version of the version.ttdb file: % /opt/timesten/32/bin/ttversion presenter The PGW displays output similar to the following example: [ output = "TimesTen Release x.y.z build time... ] f. Replace the TimesTen database Release x.y.z with the new version: % echo xyz >/opt/ciscomgc/etc/version.ttdb g. Ensure that the version.ttdb, migrate.ttdb, and export.ttdb files are present: % cd /opt/ciscomgc/etc % ls *.ttdb Step 8 Step 9 Log in to PGW 1 as root. Save the Cisco PGW 2200 Softswitch configuration data: # cp /opt/ciscomgc/snmp/snmpd.cnf /opt/ciscomgc/dialplan Step 10 Step 11 Step 12 Step 13 If you are using Cisco MNM, save the snmpd.cnf file (located in /opt/ciscomgc/snmp) before the migration starts. Move to the Cisco MGC directory: # cd /opt/ciscomgc Back up the current MGC files: # tar cvf /var/tmp/upgrade/mgc.tar./etc./dialplan # cp./local/ttbackup.tar /var/tmp/upgrade/ttbackup.tar Verify that configuration files were successfully backed up. The mgc_<hostname>_<yyyymmdd>_<hhmmss>_backup file and the MGC.tar file must be present. # cd /var/tmp/upgrade # ls At this point, you have saved all the required data in tar files in /var/tmp/upgrade. Follow these steps to move these files to a blank tape or remote machine so that you can recover them after installing Solaris 10. Caution You are responsible for providing the backup mechanism and storage location. a. Local tape drive Enter the following commands to store the files on a local tape drive: # cd /var/tmp/upgrade # tar cvf /dev/rmt/0 MGC.tar ttbackup.tar mgc_mgc-01_ _115923_backup.tar b. Remote file server Using the ftp utility, transfer the MGC.tar and ttbackup.tar files from the /var/tmp/upgrade directory to a remote file server. Use the binary mode of ftp to transfer the MGC.tar and ttbackup.tar files. 5-16

17 Migrating the First PGW to Cisco PGW 2200 Softswitch Release 9.7 Step 14 Verify that the files are successfully transferred to the remote file server before continuing. At this point, the Cisco PGW 2200 Softswitch configuration data have been saved in MGC.tar files on a tape or remote file server. The file backup is now complete. Proceed to Installing Sun Solaris 10. Installing Sun Solaris 10 Follow these steps to install Sun Solaris 10 on PGW host 1: If you want to use two new hard disks to install the Cisco PGW 2200 Softswitch Release 9.7 software, you can use the original hard disks to revert to the previous Cisco PGW 2200 Softswitch version if there is a problem during the upgrade procedure. For instructions on how to revert to the previous Cisco PGW 2200 Softswitch version, refer to Falling Back to Solaris 8. If you are upgrading from the primary disk, you need use Veritas Volume Manager to use the second disk for Solaris 8 fallback. For further information, refer to me_manager/index.html. Step 1 Shut down PGW host 1: # init 0 Step 2 Wait for the system to return to the boot prompt then load the Cisco Solaris 10 Operating System Startup CD in the CD-ROM drive. If you are replacing the hard disks, power off the system, label, and remove the existing disks using proper anti-static procedures. Install the new disk drives in the same slots the original disk drives were located. Finally, power up the system. See the Sun System Manual for your platform. Step 3 Install the Sun Solaris 10 operating system using the procedures in Loading the Sun Solaris 10 Operating System section on page 2-3. Caution Do not format or modify the second disk drive. Unless the disk drives were replaced in Step 2, the second disk contains the original Solaris 8 system if you are Veritas Volume Manager. The second disk is used as a fallback in case of a failure in the Solaris 10 upgrade. Loading the Sun Solaris 10 Operating Environment Packages Before you install the Cisco PGW 2200 Softswitch software, load the Sun Solaris 10 Operating Environment packages using the steps in the Loading the Sun Solaris 10 Operating Environment section on page

18 Migrating the First PGW to Cisco PGW 2200 Softswitch Release 9.7 Chapter 5 Migrating to Solaris 10 and Cisco PGW 2200 Softswitch Release 9.7 Caution Do not load Solstice DiskSuite (CSCOh023) if you are using Veritas Volume Manager to use the second disk for Solaris 8 fallback. For more information about Veritas Volume Manager, refer to me_manager/index.html. Restoring Data Files Follow these instructions to restore the Cisco PGW 2200 Softswitch configuration files (MGC.tar) on PGW host 1: Step 1 Step 2 Step 3 Log in as root and move the Cisco PGW 2200 Softswitch configuration files to the /tmp directory. # cd /var/tmp Create a mount point. # mkdir saved # cd /var/tmp/saved Store the data files: a. Local tape drive: Store the files on a local tape drive. # tar xvf /dev/rmt/0 b. Remote file server Using the ftp utility, transfer the MGC.tar and ttbackup.tar files from the remote file server to the /tmp/saved directory. Step 4 Step 5 Step 6 Step 7 Step 8 Use the binary mode of ftp to transfer the MGC.tar and ttbackup.tar files. Verify that the files successfully transfer to the remote file server before continuing. Create an MGC directory and extract Cisco MGC data files: # cd /opt # mkdir CiscoMGC # Create MGC directory # cd /opt/ciscomgc # mkdir snmp # Create snmp directory # cp /var/tmp/saved/mgc.tar MGC.tar # tar xvf MGC.tar # Extract MGC data files # mkdir local # Create snmp directory # cp /var/tmp/saved/ttbackup.tar./local/ttbackup.tar Verify that the etc and dialplan directories are present. If you saved the snmpd.cnf file, copy the file to the /opt/ciscomgc/snmp directory: # cp /opt/ciscomgc/dialplan/snmpd.cnf /opt/ciscomgc/snmp If you are migrating your PGW system from the Sparc platform to the Opteron platform, remove the.bin files in the /opt/ciscomgc/dialplan, /opt/ciscomgc/etc, and active_link directories: # rm /opt/ciscomgc/dialplan/*.bin # rm /opt/ciscomgc/etc/*.bin # rm /opt/ciscomgc/etc/active_link/*.bin # rm /opt/ciscomgc/etc/export.ttdb # rm /opt/ciscomgc/etc/migrate.ttdb # rm /opt/ciscomgc/etc/version.ttdb 5-18

19 Migrating the First PGW to Cisco PGW 2200 Softswitch Release 9.7 Complete this step only if you are migrating from the Sparc platform to the Opteron platform. Step 9 Type the following command to reboot the PGW: # init 6 Installing and Verifying the Cisco PGW 2200 Softswitch Software Follow these steps to install the Cisco PGW 2200 Softswitch software on PGW host 1: Step 1 Step 2 Step 3 Step 4 Install the Cisco PGW 2200 Softswitch software using the instructions in Installing the Cisco PGW 2200 Softswitch Software Release 9.7 and Higher. Set the value of pom.datasync to true on PGW hosts 1 and 2. To update the pom.datasync value, use an editor such as vi to edit the XECfgParm.dat in the /opt/ciscomgc/etc/ directory. Log in to PGW host 1 as mgcusr. If you are migrating from the Sparc platform to the Opteron platform, complete the following steps. If you are migrating to a Sparc platform, skip to. a. Enter the following commands to start the TimesTen database. % cd /opt/ciscomgc/local % sudo /etc/init.d/tt start The tt60 daemon has started successfully. b. Run the db_count.sh script to verify that the TimesTen database is empty. % db_count.sh Counting the rows in each database table. CISCO.ANNOUNCEMENT < 0 > CISCO.A_CHARGE_ORIGIN < 0 > CISCO.A_NUMBERDIALPLANSELECTION < 0 > CISCO.BLACKLIST_A < 0 > CISCO.BLACKLIST_B < 0 > CISCO.CBBOOKINGINFO < 0 > CISCO.CBMONITORINGINFO < 0 > CISCO.CLIIPADDRESS < 0 > CISCO.CLIPREFIX < 0 > CISCO.FULLNUMBERTRANSLATION < 0 > CISCO.H323IDDIVFROM < 0 > CISCO.LIENTRIES < 0 > CISCO.NUMBERTERM < 0 > CISCO.PORTEDNUMBERS < 0 > CISCO.SCRIPT < 0 > CISCO.WHITELIST_A < 0 > CISCO.WHITELIST_B < 0 > c. Import the TimesTen database from the ttbackup.tar file. %./mgcttmigrate import ttbackup.tar 5-19

20 Migrating the First PGW to Cisco PGW 2200 Softswitch Release 9.7 Chapter 5 Migrating to Solaris 10 and Cisco PGW 2200 Softswitch Release 9.7 d. Run the db_count.sh script to verify that the TimesTen database has been imported. % db_count.sh Counting the rows in each database table. CISCO.ANNOUNCEMENT < 1001 > CISCO.A_CHARGE_ORIGIN < 1001 > CISCO.A_NUMBERDIALPLANSELECTION < 6 > CISCO.BLACKLIST_A < 1001 > CISCO.BLACKLIST_B < 1002 > CISCO.CBBOOKINGINFO < 0 > CISCO.CBMONITORINGINFO < 0 > CISCO.CLIIPADDRESS < 1000 > CISCO.CLIPREFIX < 9 > CISCO.FULLNUMBERTRANSLATION < 0 > CISCO.H323IDDIVFROM < 1002 > CISCO.LIENTRIES < 0 > CISCO.NUMBERTERM < 0 > CISCO.PORTEDNUMBERS < > CISCO.SCRIPT < 1000 > CISCO.WHITELIST_A < 1001 > CISCO.WHITELIST_B < 1001 > Step 5 Enter the following command to start the Cisco PGW 2200 Softswitch software on PGW host 1: % sudo /etc/init.d/ciscomgc start Step 6 Step 7 Step 8 Step 9 Wait for PGW host 1 to come up fully as standby host. When the Cisco PGW 2200 Softswitch software starts, it updates the following files to function with the Cisco PGW 2200 Softswitch Release 9.7 software: Data files in the /opt/ciscomgc/etc directory Data files in the /opt/ciscomgc/etc/config_lib/cfg_config-name directory specified by the /opt/ciscomgc/etc/active_link file Enter the following command on PGW host 1 to restart TimesTen database replication: % /opt/ciscomgc/local/setup_replication.sh peerhost active Enter the following command on PGW host 2 to stop the Cisco PGW 2200 Softswitch software: % init 0 Step 10 Enter the following command on PGW host 2: % /opt/ciscomgc/local/setup_replication.sh peerhost standby Step 11 If you are upgrading from the Sparc platform to the Opteron platform, start a provisioning session and regenerate the MGC.bin files: # mml>prov-sta # mml>prov-cpy Caution Step 12 Complete this step only if you are migrating from the Sparc platform to the Opteron platform. Verify that the migration to the 9.7 software is complete and that all protocols are operational: % rtrv-ne % rtrv-tc:all % rtrv-dest:all % rtrv-c7lnk:all % rtrv-iplnk:all 5-20

21 Migrating the First PGW to Cisco PGW 2200 Softswitch Release 9.7 Step 13 Step 14 Step 15 Enter the following command on the standby host to verify that call replication is occurring between PGW hosts 1 and 2: rtrv-tc:all rtrv-tt-database # numan-rtrv:cliprefix:clisetname="1111",cliprefix="1" # numan-rtrv:announcement:annid=1,gwtype="as5400" # numan-rtrv:porttbl:digitstring="100034" You have now completed upgrading PGW host 1 to the Release 9.7 software. Enter the following command to promote PGW host 1 to active: sw-over::confirm When the switchover is complete, enter the following command to verify that PGW host 1 is processing calls. rtrv-tc:all Step 16 If the call replication fails, or if new Active Host is not processing calls, refer to the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide. Restart PGW host 2 in order to ensure that the changes to the pom.datasync variable take effect. Transferring Additional Configuration Files If you need to transfer additional configuration files, follow these steps, using the config-lib tool: Step 1 Step 2 Set the pom.datasync variable to False on both PGW hosts. To view or modify the pom.datasync variable, use an editor such as vi to edit /opt/ciscomgc/etc/xecfgparm.dat. Restart the active and standby PGW hosts sequentially to ensure that the changes to the pom.datasync variable take effect. Step 3 Complete the following steps to migrate the files to PGW host 2: a. Log in to PGW host 2 as root. b. Enter the following command to stop the Cisco PGW 2200 Softswitch software on PGW host 2: # /etc/init.d/ciscomgc stop c. Run the config-lib application: # config-lib d. At the configuration file library main menu, type 3 and press Enter. The Configuration File Library Main Menu 1. List Configuration Versions in Library 2. Save Production to a new Library Version 3. Copy Library Version to Production 4. Remove Configuration Library Version Enter Selection or 'q' to quit> 3 e. The menu lists available configuration files. 5-21

22 Migrating the First PGW to Cisco PGW 2200 Softswitch Release 9.7 Chapter 5 Migrating to Solaris 10 and Cisco PGW 2200 Softswitch Release 9.7 Configuration Versions 1. sip-upgrade sip-upgrade sip-upgrade sip-upgrade-0130 ***Current Production Version = sip-upgrade Enter Selection to Copy or 'q' to go back> f. Enter the number of the configuration you want to migrate. Command output is truncated. Enter Selection to Copy or 'q' to go back> 2 ***Start checking if migration is needed... starting migration... g. Config-lib lists the related files as they are migrated to Release 9.7. When the migration is complete, config-lib displays the following output: migration completed successfully ***finish checking migration... This operation will copy the selected version of each configuration file from the LIBRARY to the PRODUCTION area. Do you want to overwrite the production files (y/n)? h. At the prompt, type y and press Enter to copy the files to the production area. Do you want to overwrite the production files (y/n)? y removing data files in Production Area... Copying data files of selected version to the data Production Area... Completed copy i. Type q to exit config-lib. The Configuration File Library Main Menu 1. List Configuration Versions in Library 2. Save Production to a new Library Version 3. Copy Library Version to Production 4. Remove Configuration Library Version Enter Selection or 'q' to quit> q Quit Step 4 When the file transfer is complete, perform the following steps on PGW host 2: a. Enter the following command to start the Cisco PGW 2200 Softswitch software: # /etc/init.d/ciscomgc start b. Verify that all protocols are operational: # rtrv-ne # rtrv-tc:all # rtrv-dest:all # rtrv-c7lnk:all # rtrv-iplnk:all 5-22

23 Migrating the First PGW to Cisco PGW 2200 Softswitch Release 9.7 c. Type the following command on the standby host to verify that call replication is occurring between the active and standby PGW hosts: rtrv-tc:all Step 5 Step 6 Promote PGW host 2 to active: sw-over::confirm When the switchover is complete, verify that PGW host 2 is processing calls: rtrv-tc:all If the call replication fails, or if the new Active Host is not processing calls, refer to the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide. Step 7 Complete the following steps to migrate the files to PGW host 1: a. Log in to PGW host 1 as root. b. Enter the following command to stop the Cisco PGW 2200 Softswitch software on PGW host 1: # /etc/init.d/ciscomgc stop c. Enter the following command on PGW host 1: # config-lib d. At the configuration file library main menu, type 3. The Configuration File Library Main Menu 1. List Configuration Versions in Library 2. Save Production to a new Library Version 3. Copy Library Version to Production 4. Remove Configuration Library Version Enter Selection or 'q' to quit> 3 e. The menu lists available configuration files. Configuration Versions 1. sip-upgrade sip-upgrade sip-upgrade sip-upgrade-0130 ***Current Production Version = sip-upgrade Enter Selection to Copy or 'q' to go back> f. Enter the number of the configuration you want to migrate. Enter Selection to Copy or 'q' to go back> 2 ***Start checking if migration is needed... starting migration... Command output is truncated. g. Config-lib lists the related files as they are migrated to Release 9.7. When the migration is complete, config-lib displays the following output: migration completed successfully 5-23

24 Migrating the First PGW to Cisco PGW 2200 Softswitch Release 9.7 Chapter 5 Migrating to Solaris 10 and Cisco PGW 2200 Softswitch Release 9.7 ***finish checking migration... This operation will copy the selected version of each configuration file from the LIBRARY to the PRODUCTION area. Do you want to overwrite the production files (y/n)? h. Copy the files to the production area. Do you want to overwrite the production files (y/n)? y removing data files in Production Area... Copying data files of selected version to the data Production Area... Completed copy i. Type q to exit config-lib. The Configuration File Library Main Menu 1. List Configuration Versions in Library 2. Save Production to a new Library Version 3. Copy Library Version to Production 4. Remove Configuration Library Version Enter Selection or 'q' to quit> q Quit Step 8 When the file transfer is complete, perform the following steps: a. Set the value of pom.datasync to true on PGW hosts 1 and 2. To update the pom.datasync value, use an editor such as vi to edit the XECfgParm.dat in the /opt/ciscomgc/etc/ directory. b. Log in to PGW host 1 as root. a. Enter the following command to start the Cisco PGW 2200 Softswitch software on PGW host 1: # /etc/init.d/ciscomgc start b. Wait for PGW host 1 to come up fully as standby host. c. Stop the Cisco PGW 2200 Softswitch software on PGW host 2: # init 0 d. Set PGW host 2 to standby: # /opt/ciscomgc/local/setup_replication.sh peerhost standby Step 9 Step 10 Step 11 Step 12 Verify that all protocols are operational: # rtrv-ne # rtrv-tc:all # rtrv-dest:all # rtrv-c7lnk:all # rtrv-iplnk:all Type the following command on the standby host to verify that call replication is occurring between PGW hosts 1 and 2: rtrv-tc:all Promote PGW host 1 to active: sw-over::confirm When the switchover is complete, verify that PGW host 1 is processing calls. rtrv-tc:all 5-24

25 Falling Back to Solaris 8 Step 13 If the call replication fails, or if new Active Host is not processing calls, refer to the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide. Restart PGW host 2 in order to ensure that the changes to the pom.datasync variable take effect. Falling Back to Solaris 8 If you encounter problems during migration to Solaris 10, follow these steps to revert to Solaris 8: If you replaced disk drives during the migration to Solaris 10, refer to the Falling Back to Solaris 8 If Hard Drives Were Replaced During the Upgrade section on page If you did not replace disk drives during migration but used Veritas Volume Manager to mirror disk drives, refer to the Falling Back to Solaris 8 on the Second Disk Drive section on page If you cannot use the previous options to restore Solaris 8, you need to restore the original Cisco PGW 2200 Softswitch configuration. For further instructions, refer to the Restoring the Original Cisco PGW 2200 Softswitch Software section on page Falling Back to Solaris 8 If Hard Drives Were Replaced During the Upgrade If you replaced disk drives during the migration to Solaris 10 and need to revert to Solaris 8, perform the following procedure: Step 1 Step 2 Step 3 Stop the operating system and power down the platform: # /usr/sbin/shutdown g0 -i5 Remove the new disk drives and install the original disk drives in their original locations using proper anti-static procedures. See the Sun System manual for your platform. Power up the system. Falling Back to Solaris 8 on the Second Disk Drive If the upgrade is not successful, you can fall back to Solaris 8: Step 1 Step 2 Step 3 Stop the operating system. # init 0 From the ok prompt, boot the secondary boot disk. ok boot disk1 Log in as mgcusr and verify that the system boots Solaris 8 and the Cisco PGW 2200 Softswitch software starts properly. 5-25

26 Falling Back to Solaris 8 Chapter 5 Migrating to Solaris 10 and Cisco PGW 2200 Softswitch Release 9.7 % uname r indicates that the system is running the Solaris 8 operating system. % mml mml> rtrv-ne Step 4 Step 5 Verify that the correct version of the Cisco PGW 2200 Softswitch software is running. Log in again as root and start vxdiskadm. # vxdiskadm Text similar to the following is displayed: Volume Manager Support Operations Menu: VolumeManager/Disk 1 Add or initialize one or more disks 2 Encapsulate one or more disks 3 Remove a disk 4 Remove a disk for replacement 5 Replace a failed or removed disk 6 Mirror volumes on a disk 7 Move volumes from a disk 8 Enable access to (import) a disk group 9 Remove access to (deport) a disk group 10 Enable (online) a disk device 11 Disable (offline) a disk device 12 Mark a disk as a spare for a disk group 13 Turn off the spare flag on a disk list List disk information? Display help about menu?? Display help about the menuing system q Exit from menus Select an operation to perform Step 6 Type 4 to remove a disk for replacement. Remove a disk for replacement Menu: VolumeManager/Disk/RemoveForReplace Use this menu operation to remove a physical disk from a disk group, while retaining the disk name. This changes the state for the disk name to a "removed" disk. If there are any initialized disks that are not part of a disk group, you will be given the option of using one of these disks as a replacement. Step 7 Type list to list all disks: Enter disk name [<disk>,list,q,?] list Disk group: rootdg DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE dm rootdiska NODEVICE dm rootdiskb c0t1d0s2 sliced Step 8 Type rootdiska at the following prompt: 5-26