|Oracle® Big Data Appliance Owner's Guide
Release 1 (1.1)
Part Number E36161-06
|PDF · Mobi · ePub|
This chapter explains how to install and configure Auto Service Request for Oracle Big Data Appliance. It contains these sections:
Auto Service Request (ASR) is designed to automatically open service requests when specific Oracle Big Data Appliance hardware faults occur. To enable this feature, the Oracle Big Data Appliance components must be configured to send hardware fault telemetry to the ASR Manager software. ASR Manager must be installed on a server that has connectivity to Oracle Big Data Appliance and an outbound Internet connection using HTTPS or an HTTPS proxy.
Note:Set up ASR Manager before you configure Oracle Big Data Appliance. Ensure that Auto Service Request is selected in the Oracle Big Data Appliance Configuration Worksheets, so that ASR components are installed and configured on the appliance. See "Software Configuration".
When a hardware problem is detected, ASR Manager submits a service request to Oracle Support Services. In many cases, Oracle Support Services can begin work on resolving the issue before the database administrator is even aware the problem exists.
ASR detects faults in the most common server components, such as disks, fans, and power supplies, and automatically opens a service request when a fault occurs. ASR monitors only server components and does not detect all possible faults.
ASR is not a replacement for other monitoring mechanisms, such as SMTP and SNMP alerts, within the customer data center. It is a complementary mechanism that expedites and simplifies the delivery of replacement hardware. ASR should not be used for downtime events in high-priority systems. For high-priority events, contact Oracle Support Services directly.
A service request may not be filed automatically on some occasions. This can happen because of the unreliable nature of the SNMP protocol or a loss of connectivity to ASR Manager. Oracle recommends that customers continue to monitor their systems for faults and call Oracle Support Services if they do not receive notice that a service request has been filed automatically.
Oracle Auto Service Request web page at
Oracle Auto Service Request user documentation at
Before installing ASR, complete these prerequisites:
Create a My Oracle Support account at
Ensure that the following are set up correctly:
Oracle Premier Support for Systems, Oracle Premier Support for Operating Systems, or Oracle Limited Warranty
The technical contact person at the customer site who is responsible for Oracle Big Data Appliance
A valid shipping address at the customer site for Oracle Big Data Appliance parts
Identify and designate a system to serve as ASR Manager.
ASR Manager must be installed on a server that has connectivity to Oracle Big Data Appliance and an outbound Internet connection using HTTPS or an HTTPS proxy. To submit a service request (SR), the server must be able to access the Internet.
Ensure that the designated system conforms to the "Hardware and Network Configuration Recommendations for ASR." See the Oracle ASR website:
Confirm that Java Development Kit 6 (JDK 1.6.0_04 or later) is running on the designated ASR Manager system:
If necessary, download and install the latest version of JDK from the Java SE Downloads website:
root access to the designated ASR Manager system.
Identify and verify connectivity to Oracle Big Data Appliance.
Verify connectivity to the Internet using HTTPS.
See Also:Oracle Auto Service Request Installation and Operations Guide at
This section contains these topics:
ASR Manager requires installation of these components:
ASR Manager Version 3.6 or later
Oracle Service Tags
For links to the ASR software, go to the Oracle Auto Service Request Downloads website:
Refer to My Oracle Support Note 1185493.1 for the most recent software releases.
To download the Oracle Service Tags bundle, go to this site:
Connect to the ASR Manager system.
Check whether OASM version 1.3.1 or later is already installed:
rpm -q SUNWsasm
If it is not installed, then download the latest version as described in "Downloading the Software".
root user, install the OASM package:
rpm -i SUNWsasm.version_number.rpm
Verify the installation:
rpm -Vv SUNWsasm-version_number
Connect to the ASR Manager system.
Download and unzip the
root user, install the package:
rpm -i SUNWswasr.version_number.rpm
Update the root login file, such as
.bashrc, to add the
asr software to the
PATH variable. These commands are for the Bash shell:
PATH=$PATH:/opt/SUNWawasr/bin/asr EXPORT PATH
Verify the installation:
rpm -Vv SUNWswasr
If the installation failed, then remove it, restart the system, and reinstall the package.
Verify that ASR is running before entering any other ASR commands:
root user on the ASR Manager server, enter this command:
2, depending on your location:
Americas or Asia Pacific regions:
Europe, Middle East, or Africa regions:
If you are using a proxy server to access the Internet, then enter the proxy server information. If you are not using a proxy server, then enter a hyphen (-).
Enter your My Oracle Support user name and password when prompted. ASR validates the login. After validation, the registration is complete. Passwords are not stored.
Your My Oracle Support email address receives output from ASR reports, notification of ASR problems, and notice when a service request (SR) has been generated.
Perform these checks on ASR Manager to ensure that it is installed properly:
root user, verify that the ASR installer created three CRON jobs:
The following are the recommended settings:
asr report: Set once a month on Sunday
asr heartbeat: Set twice daily or at least once daily
asr update_rules.sh: Set once daily by default
Verify that ASR Manager 3.5 or later is running:
Check the registration status:
Test the connection by sending a test message to the transport server.
The Oracle Big Data Appliance Mammoth Utility configures the servers automatically to trap component fault indicators. See "Mammoth Utility Steps".
On ASR Manager, verify that ASR is activated:
asr list_asset -i asset_ip
In the preceding command, asset_ip is the IP address of a server or an Oracle ILOM. To list all assets, enter this command:
The following is an example of the output. You should see a host name and an Oracle ILOM name for each of the 18 servers, for a total of 36 activations. If you see fewer than 36, then identify the missing ones and activate them. An example of a server name is bda1node15 and an Oracle ILOM name is bda1node15-c.
ADDRESS HOST_NAME SERIAL_NUMBER ASR PRODUCT_NAME ------------- ------------- ----------- -------- -------------------------- 184.108.40.206 bda1node15 1143FMM023 Enabled SUN FIRE X4270 M2 SERVER... 220.127.116.11 bda1node15-c 1143FMM073 Enabled SUN FIRE X4270 M2 SERVER 18.104.22.168 bda1node16 1143FMM021 Enabled SUN FIRE X4270 M2 SERVER... 22.214.171.124 bda1node16-c 1143FMM063 Enabled SUN FIRE X4270 M2 SERVER 126.96.36.199 bda1node17 1143FMM021 Enabled SUN FIRE X4270 M2 SERVER... 188.8.131.52 bda1node17-c 1143FMM46B Enabled SUN FIRE X4270 M2 SERVER
If no assets are listed, then verify that all steps of the Mammoth Utility have run successfully. See Chapter 11.
Confirm end-to-end ASR functionality:
This is an example of the output:
Successfully submitted request for activation status report. Activation status report will be sent to email address associated with MOS Account:firstname.lastname@example.org
The report is sent to My Oracle Support.
Activate the assets in My Oracle Support. Only a customer user administrator can perform this step.
Log in to My Oracle Support.
Click the More tab.
Click Pending ASR Activations.
Select the asset to activate, and review the information in the ASR Activation - Asset window. Update any information as needed.
Click Approve to complete activation. The assets should be
Confirm that the assets are listed as
Active in My Oracle Support:
Note:If an IP address or host name changes, then you must deactivate and reactivate the asset.
If no assets are discovered, then take these steps:
Log in to the first server.
(Optional) Activate the ASR Manager host using the following command:
asr activate_asset -i host_ip
In this command, host_ip is the host IP address. If the server is qualified for ASR and entitled to service, then it can be activated.
Activate Oracle ILOM:
asr activate_asset -i ilom_ip
In this command, ilom_ip is the Oracle ILOM IP address.
Activate the servers:
asr activate_asset –i host_eth0_ip
In this command, host_eth0_ip is the IP address of the first server on the administrative network.
activate_asset commands on each server.
To set up a test event on Oracle ILOM:
Log in to the Oracle ILOM of any server in Oracle Big Data Appliance.
Change to the following directory:
The following information is displayed:
/SP/alertmgmt/rules/3 Targets: Properties: type = snmptrap level = minor destination = 10.10.10.255 (Use the IP of your own ASR manager!) destination_port = 162 community_or_username = public snmp_version = 2c testrule = (Cannot show property) Commands: cd set show
Ensure that the properties have valid values as shown in Step 3, not blank or set to zeros. Use the appropriate IP address and port for your site.
Set the test trap:
You should receive an email about the event. Verify that an email was also sent to the address listed in your customer support identifier (CSI) for Oracle Big Data Appliance.
To set up a test in the operating system environment:
Enter this command to validate the operating system. The sample output shows 10.10.10.123:162 as the ASR Manager address.
# /opt/oracle/bda/compmon**/bda_mon_hw_asr.pl -validate_snmp_subscribers -type asr Sending test trap to destination - 10.10.10.123:162
Verify that an email about the event was sent to you and to the address listed in your customer support identifier (CSI) for Oracle Big Data Appliance.
This test event does not open a case, but it makes a verifiable entry in the ASR back end.
You received the emails from both of the previous tests (Oracle ILOM and operating system environment), then your validation is complete. If not, then proceed to "Troubleshooting ASR".
If the emails state that there are contract issues, contact your installation coordinator for further assistance.
If you continue to have issues, contact ASR support. See My Oracle Support Note 1352349.1).