Oracle ZFS Storage Appliance: How to (and why) enable the Automated Service Request (ASR) Feature
Last updated on APRIL 11, 2018
Applies to:Sun Storage 7720 Unified Storage System - Version All Versions and later
Oracle ZFS Storage ZS3-2 - Version All Versions and later
Sun Storage 7210 Unified Storage System - Version All Versions and later
Sun Storage 7110 Unified Storage System - Version All Versions and later
Oracle ZFS Storage ZS3-4 - Version All Versions and later
7000 Appliance OS (Fishworks)
The content of this document is specific to the Automated Service Request (ASR) feature of the ZFS Storage Appliance, although the ASR feature is now also available for Sun Systems, in addition to certain other Sun Storage models.
After reading this document, the storage user/administrator will be able to
- (i) understand the key benefits of the ASR feature,
- (ii) understand requirements for configuring ASR on the ZFS Storage Appliance,
- (iii) understand where to find instructions which explain how specifically to enable the feature on a ZFS Storage Appliance.
The Automated Service Request (ASR) feature of the ZFS Storage Appliance (formerly Sun S7000 Series NAS Appliance) is designed to automatically create an Oracle service request in response to a number of pre-defined Fault Management triggers (e.g. imminent or actual hardware component failure), helping to reduce the need for manual service request creation by the storage administrator.
Key customer benefits resulting from the use of ASR are faster problem reporting, fault diagnosis and resolution - resulting from automated fault detection and notification - and leading to improved system availability and reduced down-time.
Enabling the ASR feature on the ZFS Storage Appliance results in the following outcomes:
1. Fault reporting - the system reports active problems to Oracle for automated service response. Depending on the nature of the fault, a support case may be opened. If a service request is opened, then a limited SupportBundle will be automatically created by the appliance and transmitted to Oracle to assist with diagnosis of the open Service Request.
2. System heartbeat - daily heartbeat messages are sent to Oracle to indicate that the system is up and running. Oracle support may notify the technical contact for an account when one of the activated systems fails to send a heartbeat for too long.
3. System configuration (optional) - periodic messages are sent to Oracle describing current software and hardware versions and configuration, as well as storage configuration. No user data or metadata is transmitted in these messages.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms