Updating via the CLI

Because you log into the appliance to use the CLI, the upload as described earlier is actually a download. To download the media onto the appliance via the CLI, execute the download command in maintenance system updates:

dory:maintenance system updates> download
dory:maintenance system updates download (uncommitted)> get
                          url = (unset)
                         user = (unset)
                     password = (unset)

You must set the "url" property to be a valid URL for the download. This may be either local to your network or over the internet. The URL can be either HTTP (beginning with "http://") or FTP (beginning with "ftp://"). If user authentication is required, it may be a part of the URL (for example, "ftp://myusername:mypasswd@myserver/export/foo"), or you may leave the username and password out of the URL and instead set the user and password properties.

dory:maintenance system updates download (uncommitted)> set url=
   ftp://foo/update.pkg.gz
                          url = ftp://foo/update.pkg.gz
dory:maintenance system updates download (uncommitted)> set user=bmc
                         user = bmc
dory:maintenance system updates download (uncommitted)> set password
Enter password: 
                     password = ********
dory:maintenance system updates download (uncommitted)> commit
Transferred 157M of 484M (32.3%) ...      

Unpacking and Verifying Media

After the file has been transferred, it is automatically unpacked and verified:

dory:maintenance system updates download (uncommitted)> commit
Transferred 484M of 484M (100%) ... done 
Unpacking ... done
dory:maintenance system updates> list
UPDATE                           DATE                      STATUS
ak-nas@2009.10.14,1-0-nd         2009-10-14 08:45          AKUP_WAITING
...

Beginning an Upgrade

To begin an upgrade, select the update that constitutes the upgrade. During this process, an update health check is performed to verify that the appliance is ready to update.

From this context, you can set any properties specific to the update, including applying deferred updates. For more information on the set of properties available for the particular update, run the help properties command. User-controllable properties begin with the update_ prefix:

clownfish:maintenance system updates ak-nas@2009.04.03,1-0> help properties
Properties that are valid in this context:

   version              => Update media version

   date                 => Update release date

   status               => Update media status

   update_zfs_upgrade   => Apply incompatible storage pool update

clownfish:maintenance system updates ak-nas@2009.04.03,1-0> get
                       version = 2009.04.03,1-0
                          date = 2009-4-3 08:45:01
                        status = AKUP_WAITING
            update_zfs_upgrade = deferred
clownfish:maintenance system updates ak-nas@2009.04.03,1-0> set update_zfs_upgrade=onreboot
            update_zfs_upgrade = onreboot
clownfish:maintenance system updates ak-nas@2009.04.03,1-0> 

After you set any properties, execute the upgrade command. You are prompted for confirmation and (assuming an affirmative) the upgrade begins:

dory:maintenance system updates> select ak-nas@2009.10.14,1-0-nd 
dory:maintenance system updates ak-nas@2009.10.14,1-0-nd> upgrade
The selected software update requires a system reboot in order to take effect.
The system will automatically reboot at the end of the update process. The
update will take several minutes. At any time during this process, you can
cancel the update with [Control-C].

Are you sure? (Y/N) y
Updating from ... ak/nas@2009.10.11,1-0
Backing up smf(5) ... done.
Loading media metadata ... done.
Selecting alternate product ... SUNW,iwashi
Installing Sun Storage 7120 2009.10.14,1-0
pkg://sun.com/ak/SUNW,iwashi@2009.10.14,1-0:20091014T084500Z
Creating system/boot/ak-nas-2009.10.14_1-0 ... done.
Creating system/root/ak-nas-2009.10.14_1-0 ... done.
...

As the upgrade proceeds, the latest message is printed. You can cancel the upgrade at any time by pressing ^C, at which point you are prompted for confirmation:

Updating from ... ak/nas@2009.10.11,1-0
Backing up smf(5) ... done.
Loading media metadata ... ^C
This will cancel the current update. Are you sure? (Y/N) y
error: interrupted by user
dory:maintenance system updates ak-nas@2009.10.14,1-0-nd>

Rolling Back

To roll back to an earlier version, select the update that corresponds to that version and execute the rollback command. You are asked to confirm that you wish to execute a rollback, and then the system reboots and executes the rollback. Unlike fail-safe rollback, you are not asked for further confirmation when the system reboots. For information on the fail-safe rollback, see Fail-safe Rollback.

Removing Update Media

To remove update media, use the destroy command, specifying the update to be removed:

dory:maintenance system updates> destroy ak-nas@2009.10.14,1-0-nd
This will destroy the update "ak-nas@2009.10.14,1-0-nd". Are you sure? (Y/N) y 
dory:maintenance system updates>

Applying Deferred Updates (CLI)

To see if there are any available deferred updates, run the show command. If deferred updates are available, you can use the apply command:

clownfish:maintenance system updates> show
Updates:

UPDATE                                  DATE                      STATUS
ak-nas@2011.04.24.3.0,1-2.19.11.2       2012-6-24 17:14:19        current
ak-nas@2011.04.24.4.2,1-1.28            2012-11-5 03:11:34        waiting
ak-nas@2013.06.05.0.0,1-1.2             2013-6-19 12:58:18        unavailable

Waiting media is listed as unavailable if the currently active software is not sufficiently recent to be able to upgrade to that waiting media. In this example, media has been downloaded for both 2011.1.4.2 and 2013.1 but the 2013.1 upgrade is unavailable because you first need to upgrade to at least 2011.1.4.2.

Deferred updates:

The following incompatible updates are available. Applying these updates will
enable new software features as described below, but will prevent older
versions of the software from accessing the underlying resources. You should
apply deferred updates once you have verified that the current software update
is functioning and a rollback is not required. Applying deferred updates in a
cluster will also update any resources on the cluster peer.

1. Support for the "passthrough-x" aclinherit property for shares.
clownfish:maintenance system updates> apply
Applying deferred updates will prevent rolling back to previous versions of
software.

Are you sure? (Y/N) 
clownfish:maintenance system updates> apply