This chapter describes the Oracle ASR service and provides the prerequisites you will need to use it with Oracle Enterprise Manager.
The following sections are described:
Oracle Auto Service Request (ASR) is a feature of Oracle Premier Support for Systems and Oracle/Sun Limited Warranty support that provides auto-case generation when specific hardware faults occur. The ASR Manager software and system, which is an implementation of ASR for Oracle, accepts fault telemetry data sent from one or more assets.
Review the list of prerequisites below and verify your ASR assets and Enterprise Manager environments:
Enterprise Manager Cloud Control 13c (13.1.0.1.0) or later is installed.
My Oracle Support (MOS) details:
Provide contact information for your assets.
Enable ASR assets and associate them with a valid Customer Service Identifier (CSI) with rights over the asset.
Provide valid MOS credentials.
The provided MOS user must have administrator or asset administrator privileges.
Hardware requirements:
Since ASR is included as part of Enterprise Manager Cloud Control 13c, any ASR hardware requirements are part of the Enterprise Manager requirements. See the Preinstallation Requirements for Enterprise Manager Cloud Control section of the Enterprise Manager Cloud Control Basic Installation Guide:
http://docs.oracle.com/cd/E24628_01/install.121/e22624/part_preinstall_reqs.htm#sthref50
The hardware targets (Exadata and Solaris host) must be discovered by Enterprise Manager.
Root privilege is required in order to configure FMA on Solaris to send traps to the Enterprise Manager agent.
This must be done by the administrator as part of agent deployment as a one time configuration step.
Verify that the asset is qualified for ASR, which are configured to report its hardware telemetry to an ASR Manager. For a complete list of hardware qualified for ASR, see:
http://docs.oracle.com/cd/E37710_01/nav/products.htm
For ASR activation to complete, the asset has to be Inactive or not monitored by ASR or any other client. For example, if the ASR Manager or another instance of Enterprise Manager is monitoring the asset, then this instance of Enterprise Manager will not be able to activate it.
Software requirements:
Since ASR is included as part of Enterprise Manager Cloud Control 13c, any ASR software requirements are part of the Enterprise Manager requirements. See the Preinstallation Requirements for Enterprise Manager Cloud Control section of the Enterprise Manager Cloud Control Basic Installation Guide:
http://docs.oracle.com/cd/E24628_01/install.121/e22624/part_preinstall_reqs.htm#sthref50
Oracle Java 8 (1.8.0_25) or later.
Exadata Storage Server software Release 12.1.2 or higher.
Enable Solaris FMA.
Table 1-1 shows the typical life cycle for ASR and describes the different phases:
Table 1-1 ASR Asset Life Cycle
| ASR Action | What It Means... |
|---|---|
|
Ensures that:
|
|
|
Checks connectivity daily to the ASR client and/or asset still in place. A warning e-mail is sent to you if the heartbeat is not received. |
|
|
Auto Create Service Requests (SRs) |
Creates SRs automatically for hardware faults known to require Oracle Service action. |
|
Enables you to refine which assets are auto creating SRs. |
|
|
Removes ASR status and disables ASR heartbeat monitoring. |
Serial Information From a Solaris Host
Problem: If the Enterprise Manager monitoring agent user does not have the required privileges to get the serial number information from a Solaris host, then ASR is not able to get it from the Enterprise Manager repository.
As a result, Oracle ASR will not be supported for that host.
Resolution: In Enterprise Manager Cloud Control 13c, if you encounter this error, then add the required privilege on the Solaris host to the agent user.