Table Of Contents

Migrating to Solaris 10 and Cisco MGC 9.7

Conditions for Migration

Cautions and Notes

Required Software

Recording System Data

Backing Up the Cisco MGC Configuration Files

Installing Sun Solaris 10

Loading the Sun Solaris 10 Operating Environment Packages

Restoring Data Files

Restoring Data Files from Remote Server or Local Tape Drive

Restoring Data Files from the Log Partition of the Second Disk

Installing the Cisco MGC Software

Starting the Cisco MGC Software

Falling Back to Solaris 8

Falling Back to Solaris 8 If Hard Drives Were Replaced During the Upgrade

Falling Back to Solaris 8 on the Second Disk Drive

Restoring the Original Cisco MGC Software

Replacing Hard Disks on an Existing Solaris 10 Platform

Backup Procedure

Hard Disk Replacement Procedure

Loading the Solaris 10 Operating System

Installing the Cisco MGC Software

Restoring the System

Migrating to Solaris 10 and Cisco MGC 9.7

---

This chapter describes scenarios for migrating to the Solaris 10 operating system and Cisco MGC 9.7 software.

This chapter contains the following information:

•Conditions for Migration

•Cautions and Notes

•Required Software

•Recording System Data

•Backing Up the Cisco MGC Configuration Files

•Installing Sun Solaris 10

•Loading the Sun Solaris 10 Operating Environment Packages

•Restoring Data Files

•Installing the Cisco MGC Software

•Starting the Cisco MGC Software

•Falling Back to Solaris 8

•Replacing Hard Disks on an Existing Solaris 10 Platform

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:

1. Your system must have at least 2 disks.

2. The disks in the system must be at least 18 GB in size.

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

The following table lists the conditions and corresponding tasks you must know before the upgrade or migration:

Table 4-1 Conditions for Upgrading or Migrating to Solaris 10 and Cisco MGC 9.7

Condition	Action
If you are upgrading the disk drive but not upgrading the software...	Follow the procedure in the "Replacing Hard Disks on an Existing Solaris 10 Platform" section.
If the migration is from Solaris 8 to Solaris 10...	You are required to also migrate your Cisco MGC software from its current release up to Release 9.7.

Cautions and Notes

Before starting the upgrade, consider the following cautions and note:

---

Caution Before starting the upgrade, make sure the Cisco MGC software is shut down, and the system administrator is logged in as root.

---

---

Caution Always start the migration or upgrade from the standby box.

---

---

Caution Verify the existing system status and make sure there are no major alarms. You must first resolve alarms that are found before proceeding with the upgrade or migration.

---

---

Caution When upgrading a redundant system, verify that the pom.dataSync parameter (located in /opt/CiscoMGC/etc/XECfgParm.dat) is set to false to maintain calls and preserve your configuration.

---

---

Note The Cisco PGW 2200 PSTN Gateway (hereafter referred to as Cisco PGW 2200) is the new name for the Cisco VSC 3000 and Cisco SC 2200. Some parts of this document may use these older names.

---

Required Software

You must have the following software:

•Cisco Solaris 10 Operating System Startup CD. There are two versions of this disk, one for each of the supported platform types. If your host platform is a Sun Fire V40z or a Sun Fire X4600, you should be using the Cisco Solaris 10 Operating System Startup Disk for Opteron-based Platforms. Otherwise, you should be using the Cisco Solaris 10 Operating System Startup Disk for Sparc-based Platforms.

•Cisco Solaris 10 Operating Environment CD

•Cisco Installation CD, which includes the new release of the Cisco MGC software.

If Veritas Volume Manager is not running on the platform, the following software is also required for the backout procedure:

•Cisco Installation CD, which includes the version of the Cisco MGC software that was originally installed on your system.

•Operating Environment Installation CD, part number 704-6914-10

Recording System Data

When you upgrade to Sun Solaris 10, you must re-enter various elements of your system data, because the installation overwrites your existing system data. To ensure that you have all of your system data. We recommend that you 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

---

Note You may have already recorded some of this information based on the "Required Site-Specific Information" section and "Required Machine-Specific Information" section.

---

This completes the procedures for recording system data. Continue to the following section, Backing Up the Cisco MGC Configuration Files.

Backing Up the Cisco MGC Configuration Files

Before you begin the migration to the new version of the MGC software, you need to back up your current system files. This section describes the following backup procedures:

•Create a remote backup of the current MGC configuration using the mgcbackup utility. These backup files are used to revert to the original version of the MGC software in the event of a problem during migration.

•Create a .tar archive file to migrate to the new version of the MGC software.

Follow these steps to back up the MGC configuration files:

---

Step 1 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 and press Enter 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

---

Note 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 MGC host, such as MGC-01.
² yyyymmdd is the date the backup file is created, in a year-month-day format, such as 20011130.
² hhmmss is the time the backup file is created, in an hour-minute-second format, such as 115923.

---

Type the following command and press Enter to 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 in the case that 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 2 Enter the following command to stop TimesTen database replication between the active and standby PGW:

./delete_replication.sh

Step 3 Insert the Cisco MGC software CD in the CD-ROM drive.

Step 4 Before you install Solaris 10, you need to remove operating environment and security packages and from previous Solaris versions. Follow these steps to remove the packages:

a. Determine which operating environment or security packages you need to remove from your system. To display the current Solaris patch version, use the command showrev -p. This command displays both the old and new patch versions. The most common patches are:

–Solaris 2.6 Patch Cluster (CSCOh007)

–Solaris 2.5.1 Patch Cluster (CSCOh0008)

–Solaris 8 Operating System Patch Cluster (CSCOh015)

–Cisco Security Package (CSCOh013)

–Cisco Security Package (CSCOk9000)

---

Note If CSCOk9000 is installed, removed it before you remove CSCOh013.

---

---

Caution Remove the Cisco Security Packages only if you intend to perform tasks such as upgrading the Cisco MGC or upgrading to a new version of the security packages. Otherwise, the /etc/system files might be corrupted and the MGC's security might be compromised.

---

b. If you need to uninstall the CSCOk9000 security package, enter the following commands to run the uninstall security script:

cd /opt/sun_install

./CiscoSec.sh uninstall /tmp/<logfile>.log

c. Type the following command to remove an operating environment package press Enter:

# pkgrm <package_number>

Where:

–package_number is the patch number that you want to remove, such as CSCOh007.

d. The PGW displays a confirmation message. The PGW displays output similar to the following

The following package is currently installed:

   <CSCOh007  Solaris 2.6 Patch Cluster>

Do you want to remove this package? [y,n,?,q] 

e. Type y and press Enter to remove the package. The PGW displays output similar to the following:

Do you want to remove this package? [y,n,?,q] y

# Removing installed package instance <CSCOh007>

This package contains scripts which will be executed with super-user

permission during the process of removing this package.

Do you want to continue with the removal of this package [y,n,?,q] 

f. Type y and press Enter to continue uninstall the package. The PGW displays output similar to the following:

Do you want to continue with the removal of this package [y,n,?,q] y

## Verifying package <CSCOh007> dependencies in global zone

## Processing package information.

## Executing preremove script.

## Removing pathnames in class <none>

/var/tmp <shared pathname not removed>

/opt/sun_install/restore_lp.sh

/opt/sun_install/CiscoSec.sh

/opt/sun_install <shared pathname not removed>

## Updating system information.

Removal of <CSCOh007> was successful.

g. Repeat steps c through f for each additional package that you need to uninstall.

Step 5 Uninstall the current version of the Cisco MGC software by typing the following commands and pressing Enter:

cd /cdrom/

./uninstall.sh

---

Note When you enter the uninstall.sh command, the PGW saves a copy of the TimesTen database in the /opt/CiscoMGC/etc directory. The original TimesTen database is updated for release 9.7 after you restore the data files in Restoring Data Files.

---

Step 6 The MGC uninstall application displays the following output:

########################################################################################

# READ CAREFULLY BEFORE PROCEEDING!!!                                                  #

# This uninstall will allow the user to return to the last good installation by        #

# answering "NO" to the following question.  You MAY NOT install an arbitrary earlier  #

# version of the software without experiencing fatal install problems.  If you do      #

# return to the last good install prior to the current install, you will lose any      #

# provisioning work you may have performed on the current software install.            #

########################################################################################

Step 7 The uninstall application displays a prompt to verify if you are upgrading the MGC software. Type y and press Enter.

Is the uninstall being done in order to upgrade to a new version of the

software? [y] [y,n,?,q] y

Step 8 The uninstall application displays a prompt to verify whether to use the admin file for unattended removal. Type y and press Enter.

Use supplied admin file for unattended removal? [n] [y,n,?,q] y

Step 9 The uninstall application displays output similar to the following example:

Restoring saved /opt/CiscoMGC/bin/EISUP

Restoring saved /opt/CiscoMGC/bin/ISDNBRI

Restoring saved /opt/CiscoMGC/bin/ISDNIP

Restoring saved /opt/CiscoMGC/bin/ISDNL3

Restoring saved /opt/CiscoMGC/bin/IUA

Restoring saved /opt/CiscoMGC/bin/LI

Restoring saved /opt/CiscoMGC/bin/LMAgent

Step 10 When the uninstall is complete, enter the following command to save the MGC configuration data:

cp /opt/CiscoMGC/snmp/snmpd.cnf /opt/CiscoMGC/dialPlan

---

Note If you are using Cisco MNM, save the snmpd.cnf file (located in /opt/CiscoMGC/snmp) before the migration starts.

---

Step 11 Type the following command to move to the Cisco MGC directory and press Enter:

cd /opt/CiscoMGC 

Step 12 Type the following command to back up the current MGC files:

tar cvf /var/tmp/upgrade/MGC.tar ./etc ./dialPlan

Step 13 Use the following command to 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

Step 14 At this point, all the required data has been saved in tar files in /var/tmp/upgrade.

---

Caution These files must now be moved to a blank tape or remote machine so they can be recovered after Solaris 10 is installed. You are responsible for providing the mechanism and storage location.

---

a. Local tape drive: Use the following procedure to store the files on a local tape drive.

cd /var/tmp/upgrade

tar cvf /dev/rmt/0 MGC.tar

---

Note The name of the second file depends on the time that you used the mgcbackup program. For more information, see Step 3.

---

b. Remote file server: Using the ftp utility, transfer the MGC.tar file from the /var/tmp/upgrade directory to a remote file server. Make sure to use the binary mode of ftp and verify the files are successfully transfer to the remote file server before continuing.

The file backup is now complete. Proceed to Installing Sun Solaris 10.

---

Installing Sun Solaris 10

At this point, the Cisco MGC configuration data have been saved in .tar files on a tape or remote file server.

To install Sun Solaris 10, perform the following steps:

---

Step 1 Shut down the system, using the following command:

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.

---

Note If you are replacing the hard disks, you should 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 new origin 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.

---

Caution Do not format or modify the second disk drive. Unless the disk drives were replaced in Step 2 above, the second disk contains the original Solaris 8 system if Veritas Volume Manager is being used. 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 MGC software, you need to load the Sun Solaris 10 Operating Environment packages. To install the environment packages, complete the steps in the section Loading the Sun Solaris 10 Operating Environment.

Restoring Data Files

There are two methods to restore data that was saved in the section Backing Up the Cisco MGC Configuration Files.

The first method, described in the "Restoring Data Files from Remote Server or Local Tape Drive" section, retrieves the files from the tar file that was saved to the remote server or local tape drive.

The second method, described in the "Restoring Data Files from the Log Partition of the Second Disk" section, retrieves the files from the log partition on the second disk. This method can only be used if the second disk contains the log and spool partitions.

Restoring Data Files from Remote Server or Local Tape Drive

Follow these instructions to restore the MGC configuration files (MGC.tar) on the platform once Solaris 10 is up and running on the primary disk:

---

Step 1 Log in as root and type the following command to move the MGC configuration files to the /tmp directory. Press Enter.

# cd /tmp 

Step 2 Type the following commands to create a mount point. Press Enter.

# mkdir saved 

# cd /tmp/saved

Step 3 Store data files:

a. Local tape drive: Enter the following command to 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 sys.tar files from the remote file server to the /tmp/saved directory. Make sure to use the binary mode of ftp and verify the files are successfully transfer to the remote file server before continuing.

Step 4 Type the following commands and press Enter to 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 /tmp/saved/MGC.tar MGC.tar

# tar xvf MGC.tar               # Extract MGC data files

Step 5 Verify that the etc and dialPlan directories are present.

Step 6 If you saved the snmpd.cnf file, type the following command and press Enter to copy the file to its proper directory:

cp /opt/CiscoMGC/dialPlan/snmpd.cnf /opt/CiscoMGC/snmp

Step 7 Type the following command and press Enter to reboot the platform:

# init 6

---

Note If you have installed the Solaris DiskSuite package (CSCOh023) on your system, the messages below are displayed during system boot-up. They are normal Solaris DiskSuite start-up messages and do not indicate any problem with your system.

WARNING force load of misc /md-trans failed
WARNING force load of misc /md-raid failed
WARNING force load of misc /md-hotspares failed
WARNING force load of misc /md-sp failed

---

Restoring Data Files from the Log Partition of the Second Disk

The following procedure restores Cisco MGC configuration files from the log partition of the second disk when Solaris 10 is up and running on the primary disk. It can only be used if the second disk contains the Cisco MGC log and spool partitions (that is, /opt/CiscoMGC/var/log and /opt/CiscoMGC/var/spool):

---

Step 1 Log in as root and enter the following command to move to the /tmp directory:

# cd /tmp 

Step 2 Enter the following command to create a mount point:

# mkdir saved 

Step 3 Enter the following command to mount saved data on /tmp/saved:

# mount -F ufs /dev/dsk/c0t1d0s3 /tmp/saved

Step 4 Enter the following commands to create MGC directories:

# cd /opt

# mkdir CiscoMGC                # Create MGC directory

# cd /opt/CiscoMGC

# mkdir snmp                    # Create snmp directory

Step 5 Enter the following command to extract the MGC data files:

# tar xvf /tmp/saved/Solaris8/MGC.tar

Step 6 Verify that the etc and dialPlan directories aare present.

Step 7 If you saved the snmpd.cnf file, type the following command and press Enter to copy the file to its proper directory:

cp /opt/CiscoMGC/dialPlan/snmpd.cnf /opt/CiscoMGC/snmp

---

Note When you install the Cisco MGC software, the snmpd.cnf file is renamed smnpd.cnf.custorig.

---

Step 8 Unmount the /tmp/saved partition:

# umount /tmp/saved

Step 9 Type the following command and press Enter to reboot the platform:

# init 6

---

You have now completed restoring the MGC configuration files (MGC.tar).

Installing the Cisco MGC Software

Install the Cisco MGC software using the instructions in Installing the Cisco MGC Software Release 9.7 and Higher.

Starting the Cisco MGC Software

Follow these steps to start the Cisco MGC software:

---

Step 1 Obtain an MGC license file and install the license file in the /opt/CiscoMGC/license directory. For more information about licenses, refer to Installing the License File.

Step 2 Enter the following command to start the MGC software:

# /etc/init.d/CiscoMGC start

Step 3 Enter the following command to start TimesTen database replication between the active and standby PGW:

./setup_replication.sh

Step 4 When the MGC software starts, it updates the following files to function with the MGC version 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

Step 5 After the MGC software starts, you can use the config-lib tool to migrate other configuration data files to 9.7. Follow these steps to migrate additional files with the config-lib tool:

a. Type config-lib at the command prompt and press Enter.

> config-lib

b. 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 

c. The menu lists available configuration files.

Configuration Versions 
 
1. sip-upgrade-0131-3 
2. sip-upgrade-0131 
3. sip-upgrade-0131-2 
4. sip-upgrade-0130 
***Current Production Version = sip-upgrade-0131-3

Enter Selection to Copy or 'q' to go back>

d. Enter the number of the configuration you want to migrate and press Enter.

---

Note Command output is truncated.

---

Enter Selection to Copy or 'q' to go back> 2 
***Start checking if migration is needed...

starting migration ...

e. Config-lib lists the related files as they are migrated to 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)?

f. 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

g. Type q and press Enter 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

h. After you migrate any additional files using the config-lib tool, enter the following command to start the MGC software:

# /etc/init.d/CiscoMGC start

---

You have now completed the upgrade procedure to the Solaris 10 operating system and Cisco MGC 9.7 software.

Falling Back to Solaris 8

If the disk drives were replaced during the migration to Solaris 10, follow the procedures in the "Falling Back to Solaris 8 If Hard Drives Were Replaced During the Upgrade" section.

If the disk drives were not replaced during the migration to Solaris 10 and Veritas Volume Manager was used to mirror the disk drives, follow the procedures in the "Falling Back to Solaris 8 on the Second Disk Drive" section.

Otherwise, if neither of the above options can be used to back out to the Solaris 10 operating system and the original MGC software configuration has to be restored, follow the procedures in the "Restoring the Original Cisco MGC Software" section.

Falling Back to Solaris 8 If Hard Drives Were Replaced During the Upgrade

If you replaced the hard disks as part of the upgrade to the Solaris 10 operating system and now need to fall back to Solaris 8, perform the following procedure:

---

Step 1 Enter the following command to stop the operating system and power down the platform.

/usr/sbin/shutdown -g0 -i5 

Step 2 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.

Step 3 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 the original Solaris 8 environment:

---

Step 1 Stop the operating system.

# init 0 

Step 2 From the ok prompt, boot the secondary boot disk.

ok boot disk1

Step 3 Log in as mgcusr and verify that the system boots Solaris 8 and the MGC software starts properly.

% uname -r 
5.8

---

Note "5.8" indicates that the system is running the Solaris 8 operating system.

---

% mml

mml> rtrv-ne 

Verify that the correct version of the MGC software is running.

Step 4 Log in again as root and start vxdiskadm.

# vxdiskadm 

A screen 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 5 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 6 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   4711     35363560 -

Step 7 Type rootdiska at the following prompt:

Enter disk name [<disk>,list,q,?] rootdiska

  The following volumes will lose mirrors as a result of this

  operation:

        opt rootvol swapvol usr var

  No data on these volumes will be lost.

  The requested operation is to remove disk rootdiska from disk group

  rootdg.  The disk name will be kept, along with any volumes using

  the disk, allowing replacement of the disk.

  Select "Replace a failed or removed disk" from the main menu

  when you wish to replace the disk.

Step 8 Type Enter at the following prompt to continue:

Continue with operation? [y,n,q,?] (default: y) 

  Removal of disk rootdiska completed successfully.

Step 9 Type n at the following prompt and then q to quit vxdiskadm:

Remove another disk? [y,n,q,?] (default: n) n

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: q

Goodbye.

Step 10 Use the vxdisk command to verify that rootdiska is removed.

# vxdisk list 

Step 11 Shut down and boot from disk1.

# init 0

ok boot disk1

Step 12 Log in as root and run vxdiskadm.

# vxdiskadm

Step 13 Type 5 to replace a failed disk.

Replace a failed or removed disk

Menu: VolumeManager/Disk/ReplaceDisk

  Use this menu operation to specify a replacement disk for a disk

  that you removed with the "Remove a disk for replacement" menu

  operation, or that failed during use.  You will be prompted for

  a disk name to replace and a disk device to use as a replacement.

  You can choose an uninitialized disk, in which case the disk will

  be initialized, or you can choose a disk that you have already

  initialized using the Add or initialize a disk menu operation.

Step 14 Type list at the following prompt:

Select a removed or failed disk [<disk>,list,q,?] list

Disk group: rootdg

DM NAME         DEVICE       TYPE     PRIVLEN  PUBLEN   STATE

dm rootdiska    -            -        -        -        REMOVED

Step 15 Type rootdiska at the following prompt:

Select a removed or failed disk [<disk>,list,q,?] rootdiska

Step 16 Type list at the following prompt:

Select disk device to initialize [<address>,list,q,?] list

DEVICE       DISK         GROUP        STATUS

c0t0d0       -            -                            error

c0t1d0       rootdiskb    rootdg              online

Type c0t0d0 to select disk device to initialize

The following disk device has a valid VTOC, but does not appear to have

  been initialized for the Volume Manager.  If there is data on the disk

  that should NOT be destroyed you should encapsulate the existing disk

  partitions as volumes instead of adding the disk as a new disk.

  Output format: [Device_Name]

  c0t0d0

Step 17 Type n and Enter when asked to encapsulate the disk. Type y and Enter when asked if you wish to initialize the disk. Type y and Enter when asked to continue:

Instead of encapsulating, initialize? [y,n,q,?] (default: n) y

  The requested operation is to initialize disk device c0t0d0 and

  to then use that device to replace the removed or failed disk

  rootdiska in disk group rootdg.

Type Y at the following prompt:

Continue with operation? [y,n,q,?] (default: y) y

Replacement of disk rootdiska in group rootdg with disk device

  c0t0d0 completed successfully.

This will begin recovery of the disk and the mirrors will re-synchronize automatically. 

Step 18 Type n and Enter when asked to replace another disk the disk. Type q and Enter to quit:

Replace another disk? [y,n,q,?] (default: n) n

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: q

Goodbye.

---

Note Allow enough time to let both disks synchronize. Depending on the system, it may take 5 to 6 hours.

---

Step 19 Use the vxprint command to make sure disk0 is re-mirrored to disk1. When this is complete, shut down the platform and boot.

# vxprint -ht

# init 0

ok boot 

Step 20 Repeat Step 3 to verify that the correct software is running.

---

Restoring the Original Cisco MGC Software

If the neither of the previous two sections can be used to back out to the system, use the following procedure to restore the original MGC software configuration to the platform.

---

Step 1 Install Solaris 8 Operating System using the procedures in the Sun Solaris 8 Operating System Installation section.

Step 2 Install the original Cisco MGC Software using the procedures in the Cisco MGC Software Release 9.2 to Release 9.6 Installation section.

Step 3 Restore the data files using the procedures in "Restoring Data Files from Remote Server or Local Tape Drive" section.

---

Replacing Hard Disks on an Existing Solaris 10 Platform

This section describes the scenario for replacing the hard disks on an existing platform running the Solaris 10 operating system and Cisco MGC 9.7 software.

Backup Procedure

---

Caution Before restoring the mgcbackup file, you must first install the same Cisco MGC software release and the patch level that was originally on the platform.

---

To back up the system:

---

Step 1 Log in as root and stop the Cisco MGC application.

# /etc/init.d/CiscoMGC stop

Step 2 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: Using the mgcbackup utility, back up the system to local directory. Use the mgcbackup utility to list the filename of the last backup, then use ftp to transfer the file to a remote file system.

# /opt/CiscoMGC/local/mgcbackup -d /var/tmp/upgrade

---

Note The backup file is stored in the specified directory path in the following format:
mgc_<hostname>_<yyyymmdd>_<hhmmss>_backup.tar

Where:
² hostname is the name of the Cisco MGC host, such as MGC-01.
² yyyymmdd is the date the backup file is created, in a year-month-day format, such as 20011130.
² hhmmss is the time the backup file is created, in an hour-minute-second format, such as 115923.

---

# /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 in the case that 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 3 Stop the operating system and power down the platform.

# /usr/sbin/shutdown -g0 -i5

---

System backup is now complete.

Hard Disk Replacement Procedure

---

Caution Be sure to follow the appropriate anti-static procedures when performing this procedure.

---

To replace the hard disk:

---

Step 1 Label the hard disks with their current locations and remove them from the system. See your platform's Sun System manual for the proper procedure.

Step 2 Install the new hard disks in the same slots as the existing hard disks. See your platform's Sun System manual for the proper procedure.

---

Loading the Solaris 10 Operating System

Power on the platform and follow the procedures in the "Installing the Sun Solaris 10 Operating System," to install the Solaris 10 operating system.

Installing the Cisco MGC Software

Install the same release and patch level of Cisco MGC software that was originally on the box, using the procedures provided in the "Installing the Cisco MGC Software Release 9.7 and Higher."

Restoring the System

---

Step 1 To restore the system:

a. Local Tape Backup: Using the mgcrestore utility, enter the following command to restore the system from the local tape drive:

# /opt/CiscoMGC/local/mgcrestore -d /dev/rmt/0

b. Remote File Server Backup: Using the ftp program, retrieve the file created in Step 2b. of the Backup Procedure section, and place it in the /opt/CiscoMGC/var/log directory. Using the mgcrestore utility, restore the system.

# /opt/CiscoMGC/local/mgcrestore -d /var/tmp/upgrade -f filename

where filename is the filename created in Step 2b. of the section Backup Procedure.

Step 2 Start the Cisco MGC software.

# /etc/init.d/CiscoMGC start

---

The hard disk replacement on an existing platform running the Solaris 10 operating system and Cisco MGC 9.7 software is now complete.