JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle® ZFS Storage Appliance Customer Service Manual

For ZS3-x, 7x20 Controllers, and DE2-24, Sun Disk Shelves

Oracle Technology Network
Library
PDF
Print View
Feedback
search filter icon
search icon

Document Information

Using This Documentation

Chapter 1 Introduction

Chapter 2 Hardware Maintenance

Chapter 3 System Maintenance

System

Introduction

System Disks

Support Bundles

Managing Support Bundles Using the BUI

Generating and Uploading a Support Bundle Using the BUI

Support Bundle Options

Managing Support Bundles Using the CLI

Initial Setup

Factory Reset

Updates

System Updates

Software Update Notification

Scheduling Software Notification Using the BUI

Scheduling Software Notification Using the CLI

Checking for Updates Using the BUI

Checking for Updates Using the CLI

System Update Overview

Preconditions

Update Health Checks

BUI

CLI

Troubleshooting Update Health Check Failures

Actions to Take to Resolve Health Check Alerts

Resolution Steps

Steps for Resolving Health Check Alerts

Deferred Updates

Reboot After an Update

Hardware Firmware Updates

Rollback

Fail-safe Rollback

Cluster Upgrade

Performing the Cluster Upgrade

Cluster States During Upgrade

Updating via the BUI

Unpacking and Verifying Media

Beginning the Upgrade

Rolling Back

Removing Update Media

Applying Deferred Updates

Updating via the CLI

Unpacking and Verifying Media

Beginning an Upgrade

Rolling Back

Removing Update Media

Applying Deferred Updates (CLI)

Passthrough x

Passthrough-x Deferred Update

User Quotas

User Quotas Deferred Update

COMSTAR

COMSTAR Deferred Update

Triple Parity RAID

Triple-Parity RAID Deferred Update

Dedup

Data Deduplication Deferred Update

Replication

Replication Deferred Update

Received Properties

Received Properties Deferred Update

Slim ZIL

Introduction

Snapshot Deletion

Snapshot Deletion Deferred Update

Recursive Snapshots

Recursive Snapshots Deferred Update

Multi Replace

Multi Replace Deferred Update

RAIDZ Mirror

RAIDZ/Mirror Deferred Update

Optional Child Dir

Introduction

Multiple Initiator Groups per LUN

Introduction

Support for Large Block Sizes

Support for Large Block Sizes

Sequential Resilvering

Sequential Resilvering

ConfigurationBackup

Configuration Backup

Backup Contents

Restore Impact

Security Considerations

Managing Configuration Backups Using the BUI

Create a Configuration Backup

Restore from a Saved Configuration

Delete a Saved Configuration

Export a Saved Configuration

Import a Saved Configuration

Managing Configuration Backups Using the CLI

Listing Configurations

Create a Configuration Backup

Restore from a Saved Configuration

Delete a Saved Configuration

Export a Saved Configuration

Import a Saved Configuration

Problems

Problems

Active Problems Display

Repairing problems

Related features

Logs

Logs

Alerts

Faults

System

Audit

Phone Home

BUI

Viewing Logs

Exporting Logs

CLI

Listing Logs

Viewing a Log

Viewing All Log Entries

Viewing Groups of Log Entries

Viewing Entry Details

Exporting Logs

Maintenance Workflows

Using Workflows

Workflow Execution Context

Workflow Parameters

Constrained Parameters

Optional Parameters

Workflow Error Handling

Workflow Input Validation

Workflow Execution Auditing

Workflow Execution Reporting

Versioning

Appliance Versioning

Workflow Versioning

Workflows as Alert Actions

Alert Action Execution Context

Auditing Alert Actions

Using Scheduled Workflows

Using the CLI

Coding the Schedule

Example: Device Type Selection

BUI

CLI

Downloading Workflows

Viewing Workflows

Executing Workflows

System Updates

The system update feature provides customers, developers, and field personnel with the ability to update a system's software after the system is installed. You can be notified when new software updates are available on My Oracle Support (MOS) or you can perform an immediate check for updates, using the BUI or CLI.

Software Update Notification

You can set up periodic checks for software updates, or you can check for updates at any time. When an updated software package is available, you are directed to download the latest package from MOS. To use the update notification feature, the Phone Home service must be enabled, as described in Phone Home Service in Oracle ZFS Storage Appliance Administration Guide .

Scheduling Software Notification Using the BUI

  1. Be sure the Phone Home service is enabled.
  2. Go to Maintenance > System > Software Updates.
  3. Click the Check box, and select the frequency: daily, weekly, or monthly. When a software update is available on MOS, you will receive an alert notification similar to the following:

    An update is available on My Oracle Support version 2013.1.0.1.

  4. Go to Maintenance > System > Software Updates, and click the download icon image: at the far right.
  5. Click the download link shown in the popup window, and save the zip file.

Scheduling Software Notification Using the CLI

  1. Be sure the Phone Home service is enabled.
  2. At the command line, enter configuration services scrk. The following example checks for new software versions every 30 days:
    zfs-appliance:configuration services scrk> ls
    ...
    updatecheck_on = false
    time_updatecheck = 7d
    ...
    zfs-appliance:configuration services scrk> set updatecheck_on=true
    updatecheck_on = true (uncommitted)
    zfs-appliance:configuration services scrk> set time_updatecheck=30d
    time_updatecheck = 30d (uncommitted)
  3. When you are notified of an update, go to MOS and download the package.

Checking for Updates Using the BUI

  1. Be sure the Phone Home service is enabled.
  2. Go to Maintenance > System > Software Updates.
  3. Notice the date of the last software check, displayed next to the Check now link.
  4. Click the Check now link.
  5. When an update is available on MOS, you see the following under STATUS:

    Update available for download

  6. Click the download icon image: , at the far right.
  7. Click the download link shown in the popup window, and save the zip file.

Checking for Updates Using the CLI

  1. Be sure the Phone Home service is enabled.
  2. At the command line, enter the following in the maintenance system updates context:
     zfs-appliance:maintenance system updates> show
     Updates:
     UPDATE                          DATE                      STATUS
     2013.1.1.5                      2014-2-18 08:00           downloadable
     ak-nas@2014.01.15,1-0           2014-1-15 14:38:53        previous
     ak-nas@2014.02.01,1-0           2014-2-1 19:38:55         previous
     ak-nas@2014.02.08,1-0           2014-2-8 08:59:04         current
     zfs-appliance:maintenance system updates>
    
     zfs-appliance:maintenance system updates> select status=downloadable
     zfs-appliance:maintenance system 2013.1.1.5> show
     Properties:
    
                           version = 2013.1.1.5
                               date = 2014-2-18 08:00
                           status = downloadable
                                url = https://updates.oracle.com/Orion/Services/download
    /p18269573_20131_Generic.zip?aru=17312483&patch_file=p18269573_20131_Generic.zip
    
                          checkdate = 2014-3-4
      zfs-appliance:maintenance system 2013.1.1.5> 
    

System Update Overview

Software updates are delivered as opaque binary downloads that contain some or all of:

The updated release notes describe what is in the update, and the update process automates all of the steps of activating the delivered components. The procedure for updating the system is as follows:

For details on the update process using the BUI or CLI, review the following sections.

Preconditions

Best practices include verifying several preconditions prior to applying an update. Whenever possible, administrators should ensure that these preconditions are satisfied immediately prior to applying an update on the storage controller. In a clustered environment, these should be verified on both storage controllers before applying the update to either one.

Update Health Checks

System-level health checks are provided to help ensure that no pathologies interfere with the software update. If a problem is encountered, it is noted in the Alert Log and the update process is aborted. System software updates do not proceed until all problems have been corrected.

You can manually run the same health checks in advance of any planned update. This allows you to check the state of the system prior to scheduling an update maintenance window so you can correct any problems that could interfere with the update process. Any problem report that is issued by a manual health check is identical to that issued by the health checks integrated in the update process. As with the integrated health checks, you are presented with a link to the Alert Log, as described in Alerts , when problems are found. If no problems are found, the System Ready state transitions to Yes to indicate that the system is ready for software updates.


Note -  Running an update health check does not replace meeting required preconditions. Precondition checks, described in Preconditions, must also be executed and problems resolved prior to updating the system software.
BUI

After you select and start an update, update health checks may be issued from the software update dialog box in the BUI by clicking Check.

Figure 3-1  Starting the Update Health Checks in the BUI

image:graphic showing how to start the Update Health Checks in 									the BUI

The system remains in the Unchecked state until the Check button is clicked. During the health check operation, an indicator shows its progress.

Figure 3-2  Update Health Checks in Progress in the BUI

image:graphic showing the Update Health Checks in progress in the 									BUI

After completion, the System Ready state changes to Yes or No with a link to the Alert Log.

Figure 3-3  Completed Update Health Checks in the BUI

image:graphic showing completed Update Health Checks in the 									BUI
CLI

To execute the update health checks via the CLI, execute the upgrade command in the maintenance system updates context after selecting the update media:

zfs-appliance:maintenance system updates:ak-nas@2013.06.05.0.0,1-1.6> 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)
 Healthcheck running ... /
 Healthcheck completed.  There are no issues at this time which
 would cause an upgrade to this media to be aborted.
Troubleshooting Update Health Check Failures

Prior to the actual update, health checks are performed automatically when an update is started. If an update health check fails, it can cause an update to abort (see following example). Update health checks only validate issues that can impact updates.

Figure 3-4  Example BUI and CLI Update Health Checks Failures

image:graphic showing example BUI and CLI Update Health Checks 									failures
zfs-appliance:maintenance system updates ak-nas@2013.06.05.0.0,1-1.6> 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)
error: System is not in an upgradeable state: prerequisite healthcheck reports problems. 
See alert log for more.
Actions to Take to Resolve Health Check Alerts

After an update health check failure, you can review the Alert Log and take action to resolve each failure based on the message in the log. The following table lists the update health check failures that can block an update, and describes the associated Alert Log message and recommended order of steps you can take to resolve the issue. For component faults, follow the instructions for removal and installation found in the maintenance procedures for your controller.

Table 3-2  Resolving Health Check Alerts
ID and Alert Log Message
Failure
Resolution Steps
B1 "System software update cannot proceed: Slot <label> in disk shelf <name> is reported as absent."
SIM cannot be detected.
1, 2, 4
B2 "System software update cannot proceed: Slot <label> in disk shelf <name> is faulted."
SIM is faulted.
1, 2, 4
C1 "System software update cannot proceed: Some slots of disk shelf <name> have no firmware revision information."
SIM is missing firmware revision information.
1, 4
C2 "System software update cannot proceed: The slots of disk shelf <name> have non-uniform part numbers."
SIMs report different part numbers.
2, 4
C5 "System software update cannot proceed: The slots of disk shelf <name> have mixed firmware revisions <rev1> and <rev2>."
SIMs report different firmware revisions.
4
E1 "System software update cannot proceed: Disk shelf <name> has <just one path or zero paths>."
Disk shelf does not have two paths.
1, 2, 4
E2 "System software update cannot proceed: Disk shelf <name> path <pathname> is <state>."
Disk shelf path is not online.
1, 2, 4
E3 "System software update cannot proceed: Pool <data or log> disk <label> in disk shelf <name> has <just one path or zero paths>."
Disk or log device that is configured in a pool does not have two paths.
3, 4
PAN1 "Slot <slot> has a Revision B3 SAS HBA; Revision C0 (or later) required."
A revision B3 SAS HBA is present.
4
PAN2 "J4400 and J4500 disk shelves are not supported in this release."
Disk shelf/shelves are present that are not supported for this software release.
V1 "<product> is not supported in this release."
Controller (product) is not supported for this software release.
Resolution Steps

Take the following steps in the order listed above to resolve the issue detected during the upgrade health check.

Steps for Resolving Health Check Alerts

  1. If a SAS port LED is unlit, check all connections and replace cables as needed.
  2. Identify affected chassis, then disconnect and remove faulted SIM. After two minutes, re-seat SIM and wait for steady Power LED before reconnecting cables.
  3. Identify affected chassis, and remove faulted disk. After 30 seconds, re-seat disk and wait for steady or flashing LED.
  4. Contact Oracle Support for component service or replacement.

Deferred Updates

Each update may come with new firmware or updates to external resources. In general, these updates are backwards-compatible and applied automatically without user intervention. There are exceptions, however, for non-reversible updates. These updates involve updating a resource external to the system software in a way that is incompatible with older software releases. After the update is applied, rolling back to previous versions results in undefined behavior. For these updates, you are always given an explicit option of applying them automatically during upgrade or applying them after the fact. They are, therefore, referred to as "deferred updates."

When applying an update to a version with incompatible version changes, you are given an option to apply these version changes as part of the upgrade. For each version change, the benefits of applying the change are presented to you. The default is to not apply them, requiring you to return to the updates view and apply them once the system has rebooted after the upgrade is applied. This allows you to verify that the rest of the software is functional and a rollback is not required before applying the update.

If you elect to not apply deferred updates during an upgrade, you can return to the updates view at any point to apply the update. If deferred updates are available for the current software version, they appear as a list below the current set of available updates, with an "Apply" button to apply the updates. Deferred updates in a cluster take effect on both storage controllers simultaneously, and can only be applied while both controllers are operational. Because deferred updates are listed only for resources present on the local storage controller, in a cluster it may be the case that deferred updates are available only for resources active on the peer controller. In a cluster, it is therefore necessary to check both storage controllers to determine the availability of deferred updates.


Note -  Replication does not work across deferred updates. After deferred updates are applied that increment the stream format version, it is no longer possible to replicate to an older system. See the "Incompatible Target" failure in section Replication Failures in Oracle ZFS Storage Appliance Administration Guide .

Table 3-3  Deferred Updates
Feature
Version introduced
2009.Q2.0.0
2009.Q3.0.0
2009.Q3.0.0
2009.Q3.0.0
2010.Q1.0.0
2010.Q1.0.0
2010.Q1.0.0
2010.Q3.1.0
2010.Q3.1.0
2010.Q3.1.0
2010.Q3.1.0
2011.1.0.0
2011.1.0.0
2011.1.8.0
2013.1.1.0
2013.1.2.0

Reboot After an Update

Following the completion of the update process, the system reboots automatically. If you have the serial console open, you will notice during this reboot that multiple GRUB menu entries are available, ordered from the newest software (at the top) to the oldest software (at the bottom). The default menu entry is at the top -- the new software to which you just updated. If you do nothing, this entry boots by default, completing the update. The previous entries are rollback targets that can be used to initiate a rollback to previous versions of the system software. Rollback is discussed later.

  GNU GRUB  version 0.97  (612K lower / 2087424K upper memory)
 +-------------------------------------------------------------------------+
 | Sun ZFS Storage 7120 2013.06.05.0.0,1-1.6                               |  
 | Sun ZFS Storage 7120 2011.04.24.4.2,1-1.28                              |
 |                                                                         |  
 +-------------------------------------------------------------------------+
     Use the ^ and v keys to select which entry is highlighted.
     Press enter to boot the selected OS, 'e' to edit the
     commands before booting, or 'c' for a command-line.

As the system boots up using the new system software, you will see some special messages on the first boot indicating that an update is completing and noting the previous and new versions of the system software:

SunOS Release 5.11 Version ak/generic@2013.06.05.0.0,1-1.6 64-bit
Copyright (c) 1983, 2013, Oracle and/or its affiliates. All rights reserved.

System update in progress.
Updating from: ak/nas@2011.04.24.4.2,1-1.28
Updating to:   ak/nas@2013.06.05.0.0,1-1.6

Cloning active datasets ...... done.
Upgrading /var/ak/home ... 16 blocks
Upgrading /etc/svc/profile ... 176 blocks
Upgrading /var/apache2 ... 4432 blocks
Upgrading /var/sadm ... 5040 blocks
Upgrading /var/svc ... 0 blocks
Upgrading /var/dhcp/duid ... done.
Upgrading /var/pkg ... 208800 blocks
Upgrading /var/ak/logadm.conf ... done.
Adjusting system/dump and system/cores ... done.
Upgrading /var/crypto/pkcs11.conf ... done.
Updating system logs ... done.
Starting primordial svc.configd
Upgrading SMF repository.  This may take several minutes.
   Upgrading from Version 5 to Version 6 :   
     11570 of 11570 rows upgraded  
                   
   Upgrading from Version 6 to Version 7 :  
     6305 of 6305 rows upgraded  
                   
   Upgrading from Version 7 to Version 8 :

SMF repository upgrade complete
SMF online in 180 seconds
Sanitizing manifestfiles properties ... done.
Loading smf(5) service descriptions: 162/162
svccfg: Loaded 162 smf(5) service descriptions
Transitioning NFS server properties ... done.
Re-enabling auditing of Solaris commands ... done.
Transitioning network/initial IPMP properties to network/ipmp ... done.
Transitioning name service properties ... done.
Transitioning CIFS server properties ... done.
Preparing for service import ... done.
Importing adconf.xml ... done.
...
Configuring appliance/kit/identity:default ... done.
Applying service layer ak_generic ... done.
Refreshing services: done.
Applying service layer ak_nas ... done.
Refreshing services: done.
Applying service layer ak_SUNW,iwashi_plus ... done.
Refreshing services: done.
Applying service profile ak_generic ... done.
Applying profile upgrade/akinstall.xml ... done.
Applying layer upgrade/composite.svc ... done.
Cleaning up services ... done.
Shutting down svc.configd ... done.
Configuring devices.
Configuring network devices.

Sun ZFS Storage 7120 Version ak/SUNW,iwashi_plus@2013.06.05.0.0,1-1.6
Copyright (c) 2008, 2013, Oracle and/or its affiliates. All rights reserved.

dorab console login: