server_upgrade(1M)
NAME | SYNOPSIS | DESCRIPTION | OPTIONS | EXAMPLES
NAME
- server_upgrade- upgrade clients of a heterogeneous OS server
SYNOPSIS
-
server_upgrade -d <install_image_dir> [-p<profile>]
DESCRIPTION
- 1.
-
Using the Solaris CD that matches the platform of the OS server, boot the OS server and perform a standard upgrade. Only clients that have the same platform and platform group supported on the installation image are upgraded. For example, when you boot a SPARC based server using a Solaris SPARC CD; all clients that are SPARC based and share the same platform group are upgraded.
- 2.
-
Reboot the OS server.
- 3.
-
Insert a platform-specific CD into the CD-ROM drive. For example, if the OS server is a SPARC based system, which shares services for both SPARC and IA based clients, you would load the IA Solaris CD at this point.
- 4.
-
server_upgrade -d <install_image_dir> [-p <profile>]
The command upgrades the platform-specific services for clients on the OS server from the installation image.
- 5.
-
Reboot the OS server.
- 6.
-
Repeat steps 3-5 to upgrade platforms or platform groups of other clients.
Use this command to upgrade clients of a heterogeneous OS server that have different platforms (for example, SPARC or IA) or platform groups (for example, sun4d, sun4L) from the OS server. This command is necessary because clients of an OS server are not upgraded during a standard upgrade if the installation image does not support their platform or platform group.
Following are the steps for performing a standard upgrade of an OS server and upgrading clients, followed by the steps for upgrading clients with different platforms and platform groups using the server_upgrade command. The steps assume you are mounting the Solaris CD locally, remotely, or otherwise making it available.
OPTIONS
- -p <profile>
-
Specify the full path to a custom JumpStart profile (a text file that defines how to install Solaris software on a system). For information on setting up a profile, see Installing Solaris Software. NOTE: The profile must have the keyword set to upgrade.
- -d <install_image_dir>
-
Specify the path to the installation image. For example, /cdrom/cdrom0.
EXAMPLES
Example 1 Sample states of output of the server_upgrade command.
The following example shows the states of a SPARC based OS server and its clients each time the server_upgrade command is used to upgrade clients. The scenario uses the server_upgrade command once to upgrade a client with an IA platform, and once to upgrade a client with a different platform group (sun4L).
Initial State of Solaris
The OS server is a sparc.sun4d, running Solaris 2.4, sharing the following services:
> Solaris 2.4 for sparc.{sun4c, sun4d, sun4e, sun4m, and sun4L}
> Solaris 2.4 for i386.i86pc
> Solaris 2.3 for sparc.{sun4c, sun4d, sun4e, sun4m}
|
Initial client states are:
| Host name | Is A ... | Running ... |
| red | sparc.sun4c | Solaris 2.4 |
| blue | sparc.sun4e | Solaris 2.4 |
| yellow | sparc.sun4L | Solaris 2.4 |
| green | i386.i86pc | Solaris 2.4 |
| purple | sparc.sun4c | Solaris 2.3 |
| brown | sparc.sun4e | Solaris 2.3 |
Upgrade the 2.4 OS server to 2.5
Use the SPARC Solaris 2.5 CD to upgrade the Solaris 2.4 OS server, then reboot the OS server.
After rebooting the OS server, it is running Solaris 2.5 and sharing the following services:
> Solaris 2.5 for sparc.{sun4c, sun4d, sun4m}
> Solaris 2.3 for sparc.{sun4c, sun4d, sun4e, sun4m}
|
Client states are:
| Host name | Is A ... | Running ... | And is Now... |
| * red | sparc.sun4c | Solaris 2.5 | bootable |
| blue | sparc.sun4e | Solaris 2.4 | not bootable |
| yellow | sparc.sun4L | Solaris 2.4 | not bootable |
| green | i386.i86pc | Solaris 2.4 | not bootable |
| * purple | sparc.sun4c | Solaris 2.5 | bootable |
| * brown | sparc.sun4e | Solaris 2.3 | bootable |
NOTE: Client brown can still be booted because it is running Solaris 2.3, which is supported by the OS server, and because Solaris 2.3 supports sun4e.
Upgrade the IA clients and services
Insert the IA Solaris 2.5 CD and type:
server_upgrade -d /cdrom/cdrom0
After rebooting the OS server, it is running Solaris 2.5 and sharing the following services:
> Solaris 2.5 for sparc.{sun4c, sun4d, sun4m} > Solaris 2.5 for i386.i86pc > Solaris 2.3 for sparc.{sun4c, sun4d, sun4e, sun4m}
Client states are:
| Host name | Is A ... | Running ... | And is Now... |
| red | sparc.sun4c | Solaris 2.5 | bootable |
| blue | sparc.sun4e | Solaris 2.4 | not bootable |
| yellow | sparc.sun4L | Solaris 2.4 | not bootable |
| * green | i386.i86pc | Solaris 2.5 | bootable |
| purple | sparc.sun4c | Solaris 2.5 | bootable |
| brown | sparc.sun4e | Solaris 2.3 | bootable |
Upgrade the sun4L (Hardware Partner) client
Insert the Hardware Edition Solaris 2.5 CD and type:
server_upgrade -d /cdrom/cdrom0
After rebooting the OS server, it is running Solaris 2.5 and sharing the following services:
> Solaris 2.5 for sparc.{sun4c, sun4d, sun4m, sun4L}
> Solaris 2.5 for i386.i86pc
> Solaris 2.3 for sparc.{sun4c, sun4d, sun4e, sun4m}
|
Client states are:
| Host name | Is A ... | Running ... | And is Now... |
| red | sparc.sun4c | Solaris 2.5 | bootable |
| blue | sparc.sun4e | Solaris 2.4 | not bootable |
| * yellow | sparc.sun4L | Solaris 2.5 | bootable |
| green | i386.i86pc | Solaris 2.5 | bootable |
| purple | sparc.sun4c | Solaris 2.5 | bootable |
| brown | sparc.sun4e | Solaris 2.3 | bootable |
State of sun4e clients
Client blue is not bootable because sun4e systems are not supported by Solaris 2.5. However, it can be made bootable again by using the Solstice Host Manager and adding the Solaris 2.4 services to the OS server.
Client states are:
| Host name | Is A ... | Running ... | And is Now... |
| red | sparc.sun4c | Solaris 2.5 | bootable |
| * blue | sparc.sun4e | Solaris 2.4 | not bootable |
| yellow | sparc.sun4L | Solaris 2.5 | bootable |
| green | i386.i86pc | Solaris 2.5 | bootable |
| purple | sparc.sun4c | Solaris 2.5 | bootable |
| brown | sparc.sun4e | Solaris 2.3 | bootable |
NAME | SYNOPSIS | DESCRIPTION | OPTIONS | EXAMPLES
- © 2010, Oracle Corporation and/or its affiliates