How to Handle Storage Reconfiguration During an Upgrade
Any changes to the storage topology, including running Sun Cluster commands, should be completed before you upgrade the cluster to Solaris 9 software. If, however, changes were made to the storage topology during the upgrade, perform the following procedure. This procedure ensures that the new storage configuration is correct and that existing storage that was not reconfigured is not mistakenly altered.
Ensure that the storage topology is correct.
Check whether the devices that were flagged as possibly being replaced map to devices that actually were replaced. If the devices were not replaced, check for and correct possible accidental configuration changes, such as incorrect cabling.
Become superuser on a node that is attached to the unverified device.
Manually update the unverified device.
# scdidadm -R device
-R device Performs repair procedures on the specified device
See the scdidadm(1M) man page for more information.
Update the DID driver.
# scdidadm -ui # scdidadm -r
-u Loads the device ID configuration table into the kernel
-i Initializes the DID driver
-r Reconfigures the database
Repeat Step 2 through Step 4 on all other nodes that are attached to the unverified device.
Return to the remaining upgrade tasks.
For nonrolling upgrade, go to Step 11 in How to Upgrade to Sun Cluster 3.1 10/03 Software (Nonrolling).
For rolling upgrade, go to Step 4 in How to Prepare the Cluster for Upgrade (Rolling).
How to Resolve Mistaken Storage Changes During an Upgrade
If accidental changes are made to the storage cabling during the upgrade, perform the following procedure to change the storage configuration back to the correct state.
Note - This procedure assumes that no physical storage was actually changed. If physical or logical storage devices were changed or replaced, instead follow procedures in How to Handle Storage Reconfiguration During an Upgrade.
Change the storage topology back to its original configuration.
Check the configuration of the devices that were flagged as possibly being replaced, including the cabling.
As superuser, update the DID driver on each node of the cluster.
# scdidadm -ui # scdidadm -r
-u Loads the device-ID configuration table into the kernel
-i Initializes the DID driver
-r Reconfigures the database
See the scdidadm(1M) man page for more information.
Did the scdidadm command return any error messages in Step 2?
Return to the remaining upgrade tasks.
For nonrolling upgrade, go to Step 11 in How to Upgrade to Sun Cluster 3.1 10/03 Software (Nonrolling).
For rolling upgrade, go to Step 4 in How to Prepare the Cluster for Upgrade (Rolling).
Sun Management Center Software Upgrade
This section describes how to upgrade from Sun Management Center 2.1.1 to either Sun Management Center 3.0 software or Sun Management Center 3.5 software on a Sun Cluster 3.1 10/03 configuration.
How to Upgrade Sun Management Center Software
Have available the following items:
Sun Cluster 3.1 10/03 CD-ROM or the path to the CD-ROM image. You use the CD-ROM to reinstall the Sun Cluster 3.1 10/03 version of the Sun Cluster-module packages after you upgrade Sun Management Center software.
Sun Management Center documentation.
Sun Management Center patches and Sun Cluster-module patches, if any.
See "Patches and Required Firmware Levels" in Sun Cluster 3.1 Release Notes for the location of patches and installation instructions.
Stop any Sun Management Center processes.
If the Sun Management Center console is running, exit the console.
In the console window, select File>Exit from the menu bar.
On each Sun Management Center agent machine (cluster node), stop the Sun Management Center agent process.
# /opt/SUNWsymon/sbin/es-stop -a
On the Sun Management Center server machine, stop the Sun Management Center server process.
# /opt/SUNWsymon/sbin/es-stop -S
As superuser, remove Sun Cluster-module packages.
Use the pkgrm(1M) command to remove all Sun Cluster-module packages from all locations listed in the following table.
Location
Package to Remove
Each cluster node
SUNWscsam, SUNWscsal
Sun Management Center console machine
SUNWscscn
Sun Management Center server machine
SUNWscssv
Sun Management Center help-server machine
SUNWscshl
If you do not remove the listed packages, the Sun Management Center software upgrade might fail because of package dependency problems. You reinstall these packages in Step 5, after you upgrade Sun Management Center software.
Upgrade the Sun Management Center software.
Follow the upgrade procedures in your Sun Management Center documentation.
As superuser, reinstall Sun Cluster-module packages to the locations listed in the table below.
# cd /cdrom/suncluster_3_1_u1/SunCluster_3.1/Packages/ # pkgadd module-package
Location
Package to Install
Each cluster node
SUNWscsam, SUNWscsal
Sun Management Center server machine
SUNWscssv
Sun Management Center console machine
SUNWscshl
Sun Management Center help-server machine
SUNWscshl
You install the help-server package SUNWscshl on both the console machine and the help-server machine.
Apply any Sun Management Center patches and any Sun Cluster-module patches to each node of the cluster.
Restart Sun Management Center agent, server, and console processes.
Follow procedures in How to Start Sun Management Center.
Load the Sun Cluster module.
Follow procedures in How to Load the Sun Cluster Module.
If the Sun Cluster module was previously loaded, unload the module and then reload it to clear all cached alarm definitions on the server. To unload the module, select Module=>Unload Module from the console's Details window.