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

Hardware Firmware Updates

Following the application of a software upgrade, any hardware for which the upgrade includes newer versions of firmware is upgraded. There are several types of devices for which firmware upgrades may be made available; each has distinct characteristics.

Disks, storage enclosures, and certain internal SAS devices are upgraded in the background. When this is occurring, the firmware upgrade progress is displayed in the left panel of the Maintenance > System BUI view, or in the maintenance system updates CLI context. These firmware updates are almost always hardware related, though it may briefly show some number of outstanding updates when applying certain deferred updates to components other than hardware.

As of 2010Q3.4, when there are outstanding updates, an informational or warning icon appears next to the number of updates remaining. Clicking the icon brings up the Firmware Updates dialog, which lists the current remaining updates. For each update we also show the current version of the component, the time of the last attempted update, as well as the reason why the last attempt did not succeed.

We consider any outstanding updates to be in one of 3 states: Pending, In Progress and Failed. An update begins in the Pending state, and is periodically retried, at which time it moves into the In Progress state. If we fail to upgrade, due to a transient condition, the upgrade is moved back to the Pending state, and otherwise to the Failed state.

In general, it is only an indication of a problem if:

The following conditions do not indicate a problem:

Note that currently the Firmware Updates dialog does not automatically refresh, so you would have to close it and re-open it to get an updated view.

Applying hardware updates is always done in a completely safe manner. This means that the system may be in a state where hardware updates cannot be applied. This is particularly important in the context of clustered configurations. During takeover and failback operations, any in-progress firmware upgrade is completed; pending firmware upgrades are suspended until the takeover or failback has completed, at which time the restrictions described below are reevaluated in the context of the new cluster state and, if possible, firmware upgrades resume.


Caution

Caution  -  Unless absolutely necessary, takeover and failback operations should not be performed while firmware upgrades are in progress.


The rolling upgrade procedure documented later meets all of these best practices and addresses the per-device-class restrictions described later. It should always be followed when performing upgrades in a clustered environment. In both clustered and standalone environments, these criteria are also reevaluated upon any reboot or diagnostic system software restart, which may cause previously suspended or incomplete firmware upgrades to resume.

During the firmware upgrade process, hardware may appear to be removed and inserted, or offlined and onlined. While alerts attributed to these actions are suppressed, if you are viewing the Maintenance > Hardware screen or the Configuration > Storage screen, you may see the effects of these upgrades in the UI in the form of missing or offline devices. This is not a cause for concern; however, if a device remains offline or missing for an extended period of time (several minutes or more) even after refreshing the hardware view, this may be an indication of a problem with the device. Check the Maintenance > Problems view for any relevant faults that may have been identified. Additionally, in some cases, the controllers in the disk shelves may remain offline during firmware upgrade. If this occurs, no other controllers are updated until this condition is fixed. If an enclosure is listed as only having a single path for an extended period of time, check the physical enclosure to determine whether the green link lights on the back of the SIM are active. If not, remove and re-insert the SIM to re-establish the connection. Verify that all enclosures are reachable by two paths.