Preparing to Upgrade Clustered Controllers (CLI)

Language:

Use the following procedure to prepare to upgrade clustered controllers.

Before You Begin

Complete Preparing for a Software Upgrade.

Note - For the purpose of this procedure, the first controller to be upgraded is referred to as controller A and its peer is controller B. If one of the controllers is in a Stripped state (it has no active resources), upgrade that controller first to avoid availability delays. If both controllers in a cluster have active resources, choose either controller to upgrade first.

On your local system, download the software update as described in Checking for and Downloading Software Updates (CLI).
The update package is a single compressed file named with the version number, such as ak-nas-2013-06-05-0-0.0.pkg.gz. You can rename the file if needed; the version number is recorded within the image. The updates can vary in size, but are typically several hundred megabytes in size.
Perform the following steps to verify that each controller has a dedicated management interface listed as a private resource:
The following examples show the cluster in Active/Active mode, with example output if the management interface is listed as a private resource.
1. On controller A, go to configuration cluster resources show.
```
controller-a:> configuration cluster resources show
Resources:

RESOURCE        OWNER           TYPE       LABEL         CHANGES  DETAILS
net/igb0        controller-a     private   management... no       10.80.2xx.112
```
2. On controller B, go to configuration cluster resources show.
```
controller-b:> configuration cluster resources show
Resources:

RESOURCE        OWNER           TYPE       LABEL         CHANGES  DETAILS
net/igb1        controller-b    private    management... no       10.80.2xx.114
```

If the management interface for controller A does not show type private, lock the management interface, as shown in the following example:

    
    controller-a:> configuration cluster resources select net/igb0
    configuration cluster resources (uncommitted)> set owner=controller-a
    configuration cluster resources (uncommitted)> set type=private
    configuration cluster resources (uncommitted)> commit

Note that each controller must be the current owner of the management interface.

On controller B, lock the management interface on controller B, as in step 3.

Download the update to both controllers.

On controller A, go to maintenance system updates download and enter the following example commands:

 controller-a:maintenance system updates download (uncommitted)> set url=
   ftp://mydirectory/update.pkg.gz
                          url = ftp://mydirectory/update.pkg.gz
 controller-a:maintenance system updates download (uncommitted)> set user=bmc
                         user = bmc
 controller-a:maintenance system updates download (uncommitted)> set password
 Enter password: 
                     password = ********
 controller-a:maintenance system updates download (uncommitted)> commit

 Transferred 157M of 484M (32.3%) ...

On controller B, go to maintenance system updates download and enter the following example commands:

 controller-b:maintenance system updates download (uncommitted)> set url=
   ftp://mydirectory/update.pkg.gz
                          url = ftp://mydirectory/update.pkg.gz
 controller-b:maintenance system updates download (uncommitted)> set user=bmc
                          user = bmc
  controller-b:maintenance system updates download (uncommitted)> set password
  Enter password: 
                      password = ********
  controller-b:maintenance system updates download (uncommitted)> commit
  Transferred 157M of 484M (52.1%) ...

Wait for the package to fully download and unpack before proceeding.

Next Steps

Upgrading Clustered Controllers (CLI)