Before You Begin
Complete Preparing for a Software Upgrade.
controller-a:> maintenance system updates hostname:maintenance system updates> show Updates: UPDATE RELEASE DATE STATUS ak-nas@2013.06.05.6.2,1-1.1 2016-7-26 15:20:06 current ak-nas@2013.06.05.6.3,1-2.1.7.1 2016-8-24 14:10:02 waiting ak-nas@2013.06.05.6.1,1-1.1 2016-6-24 23:37:50 previous
controller-a:maintenance system updates> select ak-nas@2013.06.05.6.3,1-2.1.7.1
controller-a:maintenance system updates ak-nas@2013.06.05.6.3,1-2.1.7.1> check You have requested to run checks associated with waiting upgrade media. This will execute the same set of checks as will be performed as part of any upgrade attempt to this media, and will highlight conditions that would prevent successful upgrade. No actual upgrade will be attempted, and the checks performed are of static system state and non-invasive. Do you wish to continue? Are you sure? (Y/N) y
As part of the update, controller A automatically reboots.
controller-a:maintenance system updates ak-nas@2013.06.05.6.3,1-2.1.7.1> upgrade This procedure will consume several minutes and requires a system reboot upon successful update, but can be aborted with [Control-C] at any time prior to reboot. A health check will validate system readiness before an update is attempted, and may also be executed independently using the check command. Are you sure? (Y/N) y
In the following example, the state of controller A is AKCS_STRIPPED, with a description of "Ready (waiting for failback)."
controller-a:> configuration cluster show state = AKCS_STRIPPED description = Ready (waiting for failback) ... peer_state = AKCS_OWNER peer_description = Active (takeover completed)
For information about the cluster states, see Cluster Takeover and Failback in Oracle ZFS Storage Appliance Administration Guide, Release OS8.7.0.
controller-a:> maintenance system updates firmware show Pending No Pending Updates Failed No Failed Updates In Progress No Updates in Progress
For information about the cluster states, see Cluster Takeover and Failback in Oracle ZFS Storage Appliance Administration Guide, Release OS8.7.0.
In the following example, the state of controller B is AKCS_OWNER, with a description of "Active (takeover completed)."
controller-b:> configuration cluster show state = AKCS_OWNER description = Active (takeover completed) ... peer_state = AKCS_STRIPPED peer_description = Ready (waiting for failback)
controller-b:> configuration cluster failback Continuing will immediately fail back the resources assigned to the cluster peer. This may result in clients experiencing a slight delay in service. Are you sure? (Y/N) y
controller-b:> maintenance system updates hostname:maintenance system updates> show Updates: UPDATE RELEASE DATE STATUS ak-nas@2013.06.05.6.2,1-1.1 2016-7-26 15:20:06 current ak-nas@2013.06.05.6.3,1-2.1.7.1 2016-8-24 14:10:02 waiting ak-nas@2013.06.05.6.1,1-1.1 2016-6-24 23:37:50 previous
controller-b:maintenance system updates> select ak-nas@2013.06.05.6.3,1-2.1.7.1
controller-b:maintenance system updates ak-nas@2013.06.05.6.3,1-2.1.7.1> check You have requested to run checks associated with waiting upgrade media. This will execute the same set of checks as will be performed as part of any upgrade attempt to this media, and will highlight conditions that would prevent successful upgrade. No actual upgrade will be attempted, and the checks performed are of static system state and non-invasive. Do you wish to continue? Are you sure? (Y/N) y
As part of the update, controller B automatically reboots.
controller-b:maintenance system updates ak-nas@2013.06.05.6.3,1-2.1.7.1> upgrade This procedure will consume several minutes and requires a system reboot upon successful update, but can be aborted with [Control-C] at any time prior to reboot. A health check will validate system readiness before an update is attempted, and may also be executed independently using the check command. Are you sure? (Y/N) y
For information about the cluster states, see Cluster Takeover and Failback in Oracle ZFS Storage Appliance Administration Guide, Release OS8.7.0.
In the following example, the state of controller B is AKCS_STRIPPED, with a description of "Ready (waiting for failback)."
controller-b:> configuration cluster show state = AKCS_STRIPPED description = Ready (waiting for failback) ... peer_state = AKCS_OWNER peer_description = Active (takeover completed)
controller-b:> maintenance system updates firmware show Pending No Pending Updates Failed No Failed Updates In Progress No Updates in Progress
In the following example, the state of controller A is AKCS_OWNER, with a description of "Active (takeover completed)."
controller-a:> configuration cluster show state = AKCS_OWNER description = Active (takeover completed) ... peer_state = AKCS_STRIPPED peer_description = Ready (waiting for failback)
For information about the cluster states, see Cluster Takeover and Failback in Oracle ZFS Storage Appliance Administration Guide, Release OS8.7.0.
controller-a:> maintenance system updates firmware show Pending No Pending Updates Failed No Failed Updates In Progress No Updates in Progress
controller-a:> configuration cluster failback Continuing will immediately fail back the resources assigned to the cluster peer. This may result in clients experiencing a slight delay in service. Are you sure? (Y/N) y
Both controllers are now upgraded.
controller-a:> maintenance hardware show Chassis: NAME STATE MANUFACTURER MODEL SERIAL RPM ... disk-000 HDD 0 ok SEAGATE ST330057SSUN300G 001117G1G929 6SJ1G929 15000 disk-001 HDD 1 ok SEAGATE ST330057SSUN300G 001117G1GA8Y 6SJ1GA8Y 15000 disk-002 HDD 2 ok SEAGATE ST330057SSUN300G 001117G1KDPZ 6SJ1KDPZ 15000 ...
Pools should be online and have no errors.
controller-a:> configuration storage show Pools: POOL OWNER DATA PROFILE LOG PROFILE STATUS ERRORS -> pool25 controller-a - - online 0 pool26 controller-b - - online 0