1

Oracle Auto Service Request

Exadata Database Machine Quick Installation Guide
Release 3.9
E23333-04
June 2012
Oracle Auto Service Request (ASR) is a secure, scalable, customer-installable software
feature of warranty and Oracle Support Services that provides auto-case generation
when common hardware component faults occur. ASR is designed to enable faster
problem resolution by eliminating the need to initiate contact with Oracle Support
Services for common hardware component failures, reducing both the number of
phone calls needed and overall phone time required.
ASR also simplifies support operations by using electronic diagnostic data. Easily
installed and deployed, ASR is completely controlled by you, the customer, to ensure
security.
ASR is applicable only for component faults. Not all component failures are covered,
though the most common components (such as disk, fan, and power supplies) are
covered.
Recommended Configuration
The recommended configuration is to install the ASR Manager, which receives fault
telemetry information from the servers in Oracle Exadata Database Machine, on an
external standalone server. This server must run Solaris or Oracle Linux as the
operating system.
Note: ASR is not a replacement for other monitoring mechanisms,
such as SMTP and SNMP alerts, within your 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.
Caution: The commands included in this document are provided for
your convenience. However, the copy and paste functionality may not
work as expected. To ensure the command text you copy is the same
as the text you paste, make sure to have your console session set to
receive data as UTF-8.
Note: While not recommended, you may install the ASR Manager on
one of the database servers in the Oracle Exadata Database Machine.
2
Prerequisites
Before installing ASR, please ensure the following conditions are met:
Make sure you have access to My Oracle Support and that your contact
information is correct and current.
Make sure all of your assets have a Contact assigned and that the contact is correct
and current.
Identify and designate a system to serve as ASR Manager.
Identify and verify ASR assets.
Ensure connectivity to the Internet using HTTPS.
Hardware and Software Requirements
You will need root access to install the software to set up the ASR Manager.
Operating System: Oracle Linux 5.3 and later, or Solaris 10, Update 6 (10u6) and
later.
Java Version: at least JRE/JDK 1.6.0_04
Database Server: Exadata Software 11.2.1.3.1 and higher
Exadata Storage Server: Exadata Storage Server Software 11.2.1.3.1 and higher
For configuring trap destinations, you can save time and effort using one of the
following options:
- OneCommand: Running the setupASR step in OneCommand will configure
the traps and assist in activating Oracle ASR assets.
- dcli Utility: Refer to the Setting User Equivalence section in the Oracle
Exadata Database Machine Owner's Guide for instructions to enable SSH for
the dcli utility
Upgrade Database Servers (if needed)
On the database servers, check for the existence of the following script:
/opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl
If the script is there, then continue with Install ASR Manager on a Standalone Server.
If the script is missing, you will need to patch the database servers to the current patch
level. Refer to the "Database Machine and Exadata Storage Server 11g Release 2 (11.2)
Supported Versions" document (Doc ID 888828.1) for guidance on upgrading to the
current patch. You can access Doc ID 888828.1 from My Oracle Support:
https://support.oracle.com
Install ASR Manager on a Standalone Server
Provide a standalone server that is running either Oracle Linux or Solaris.
3
Install Oracle Automated Service Manager (OASM) Package
Complete the following instructions to install Oracle Automated Service Manager
(OASM) on a server running Oracle Solaris or Oracle Linux:
1. Verify you have version 1.3.1 or later (if needed, download OASM). As root:
Solaris: pkginfo -l SUNWsasm
Oracle Linux: rpm -q SUNWsasm
2. Install the OASM package. As root:
Solaris: pkgadd -d SUNWsasm.[version_num].pkg
Oracle Linux: rpm -i SUNWsasm.[version_num].rpm
Install Services Tools Bundle (STB) for Solaris
If you are installing ASR Manager on a server running Oracle Solaris, complete the
following instructions:
1. Download and unzip the STB bundle and run the installation script (install_
stb.sh). As part of the installation, be sure to select:
Enter I for install
Enter Y to replace existing SNEEP packages
Enter Y to replace existing Service Tags packages
2. Confirm that SNEEP is installed correctly. Run the following command:
sneep -a
3. Verify that Service Tags is reporting your system attributes correctly.
Run: stclient -E
If the serial number does not display, then register the serial number manually.
Run the following command:
sneep -s <serial number>
Note: You can download OASM 1.3.1 from My Oracle Support (log
in required):
https://updates.oracle.com/Orion/PatchDetails/process_form?patch_
num=12809941
Note: If your server is running Linux, then skip this step for
installing Services Tools Bundle (STB).
Note: See Doc ID 1153444.1 to download the latest STB bundle from
My Oracle Support (log in required):
https://support.oracle.com
4
Install Oracle Auto Service Request (ASR) Package
Complete the following instructions to install Oracle ASR on a server running Oracle
Solaris or Oracle Linux:
1. Download and unzip the ASR package. As root:
Solaris: pkgadd -d SUNWswasr.[version_num].pkg
Oracle Linux: rpm -i SUNWswasr.[version_num].rpm
2. Add the asr command to the PATH (update to the root's .profile, .cshrc,
.kshrc, or .bashrc files as needed):
PATH=$PATH:/opt/SUNWswasr/bin/asr
export PATH
Register the ASR Manager
Follow the instructions below to register the ASR Manager with Oracle:
1. As root on the ASR Manager system, run the following command:
asr register
2. 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 ( - ).
3. When prompted, enter your My Oracle Support user name and password. ASR
will validate the login. Once validated, the registration is complete.
4. Check the registration status. Run the following command:
asr show_reg_status
5. Test the connection to ensure that ASR can send information to the transport
server. Run the following command:
asr test_connection
Configure Fault Telemetry Destinations
Follow the instructions below to configure fault telemetry destinations on the Oracle
Exadata Storage Server and Database Server.
Note: An ASR Manager can be activated as an ASR Asset. If you
want to activate an ASR Manager as an ASR Asset. You must select
your ASR Manager from the list of qualified hardware.
Note: You can download the latest ASR package from My Oracle
Support (log in required):
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&docty
pe=SYSTEMDOC&id=1185493.1
Note: Passwords are not stored.
5
To configure fault telemetry, choose one of the following three options:
Add SNMP Trap Destinations Using OneCommand (recommended for new
installations)
Add SNMP Trap Destinations for Multiple Servers Using the dcli Utility
Add SNMP Trap Destinations for a Single Server
Add SNMP Trap Destinations Using OneCommand
If this is the initial deployment of the Exadata Database Machine, OneCommand will
automatically configure SNMP settings if run with the version released on April 26,
2012 (patch 14004092) or later. You can download the patch from My Oracle Support:
https://support.oracle.com
OneCommand performs the SNMP configuration to ASR when the SetupASR
command is executed.
To confirm that OneCommand has set up the trap destinations, run the following
command and verify that the host and ports point to the ASR server:
dcli -g dbs_group -l root "/opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -get_
snmp_subscribers -type asr"
dcli -g cell_group -l celladmin "cellcli -e list cell attributes snmpsubscriber"
You will need to run this command from an account that has equivalency with the
root user on the database nodes and celladmin equivalency on the cell nodes.
Add SNMP Trap Destinations for Multiple Servers Using the dcli Utility
If OneCommand did not already set up the trap destinations, then you can follow the
instructions outlined below to use the dcli utility to add trap destinations for multiple
servers.
When enabled, the dcli utility gives the ability to set up all servers at the same time
and also the storage servers. The dcli utility set definitions are:
dbs_group is the list of servers such as dm01db01, dm01db02
cell_group is the list of Exadata Cells such as dm01cel01, dm01cel02
Note: Oracle ASR can only use the management network. You must
make sure that the management network (ETH0 on the interfaces or
net0 on the back of the server) is set up to allow ASR to run.
Tip: You can find the current versions of OneCommand by using the
advanced patch search option in My Oracle Support. Search for the
patch description containing "onecommand."
Note: If your designated ASR Manager is not pingable by this step,
then the ASR Managers IP address was most likely not set correctly
in the configurator spreadsheet.
6
Refer to the Setting User Equivalence section in the Oracle Exadata Database
Machine Owner's Guide for instructions to enable SSH for the dcli utility. Depending
on your environment restrictions, the dcli utility may not be set up. The dcli utility is
not required for ASR. See Oracle Exadata Command and Configuration Reference for
more information about the dcli utility.
The dcli utility commands shown in this document will run commands expecting
equivalency with the root or celladmin user, depending on the command. You must
ensure the user who runs the dcli utility command has the proper equivalency set up.
For the Exadata Database Server, log in to the first database node as root. Run one of
the following commands, depending on your environment:
If your Exadata Server Software is earlier than Release 11.2.2.4.0, run:
dcli -g /opt/oracle.SupportTools/onecommand/dbs_group -l root
"/opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -set_snmp_subscribers
\"\(type=asr,host=[ASR Manager hostname or IP],port=162,community=public,\)\""
If your Exadata Server Software is Release 11.2.2.4.0 or later, run;
dcli -g /opt/oracle.SupportTools/onecommand/dbs_group -l root
"fromip=\$(ifconfig eth0 | awk '/inet addr/ {print \$2}' | cut -d:
-f2);/opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -set_snmp_subscribers
\"(type=asr,host=[ASR Manager hostname or
IP],fromip=\$fromip,port=162,community=public)\""
For the Exadata Storage Server, log in to the first database node as a user with
equivalency to the celladmin user (typically oracle). Run the following command:
Check check all cells for the snmpSubscriber attribute:
dcli -g /opt/oracle.SupportTools/onecommand/cell_group -l celladmin "cellcli -e
list cell attributes snmpSubscriber"
Run the following command (you will need to run this command from an account
that has equivalency with the celladmin user on the cells):
dcli -g /opt/oracle.SupportTools/onecommand/cell_group -l celladmin "cellcli -e
alter cell snmpsubscriber=\(\(host=\'[ASR Manager hostname or IP]\',port=162,
community=public,type=asr\)\)"
Note: If dcli is not or cannot be enabled, follow the steps in Add
SNMP Trap Destinations for a Single Server.
Note: ILOMs are set up via Exadata. Do not configure the ILOMs
manually.
Note: In some cases, SNMP entries may already be set up for
monitoring (such as, Enterprise Manager). See Doc ID 1110675.1 in My
Oracle Support for the appropriate links for that documentation:
https://support.oracle.com
7
Element Definitions:
host=[ASR Manager hostname or IP] is the ASR Manager
hostname or IP address. The ASR Manager hostname can be used
when DNS is enabled for the site. If DNS is not running, the IP
address is preferred, but the ASR Manager hostname can be used
if the entry is added to /etc/hosts file.
type=asr represents the ASR Manager being a special type of
SNMP subscriber.
community=public is the required value of the community string.
(This value is per customer as it can be modified to be a different
string based on customer network requirements.)
port=162 is the SNMP port. (This port value is customer
dependent. It can be configured as a different port based on
network requirements, or it may need to be changed for ASR to
work correctly in a managed environment.)
8
Add SNMP Trap Destinations for a Single Server
If OneCommand or the dcli utility is not available, then add the trap destinations to
each node using the command line interface (CLI).
For the Exadata Database Server, log in to the first server as root. Run the following
command:
If your Exadata Server Software is earlier than Release 11.2.2.4.0, run:
/opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -set_snmp_subscribers
"(type=asr,host=[ASR Manager hostname or IP],port=162,community=public)"
If your Exadata Server Software is Release 11.2.2.4.0 or later, run;
/opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -set_snmp_subscribers
"(type=asr,host=[ASR Manager hostname or IP],fromip=[ETH0 Node
IP],port=162,community=public)"
For the Exadata Storage Server, log in to each storage server as celladmin on the
storage node. Run the following command:
cellcli -e "alter cell snmpsubscriber=(host ='[ASR Manager hostname or
IP]',port=162,community=public,type=asr)"
Note: Repeat for each Oracle Exadata Database and Storage nodes.
Element Definitions:
host=[ASR Manager hostname or IP] is the ASR Manager
hostname or IP address. The ASR Manager hostname can be used
when DNS is enabled for the site. If DNS is not running, the IP
address is preferred, but the ASR Manager hostname can be used
if the entry is added to /etc/hosts file.
type=asr represents the ASR Manager being a special type of
SNMP subscriber.
community=public is the required value of the community string.
(This value is per customer as it can be modified to be a different
string based on customer network requirements.)
port=162 is the SNMP port. (This port value is customer
dependent. It can be configured as a different port based on
network requirements, or it may need to be changed for ASR to
work correctly in a managed environment.)
9
Activate Node on the ASR Manager
1. To validate if ILOM auto-activation occurred (if the network and ILOM are set up
correctly), run the following command:
asr list_asset
Output should looke like this:
If all ILOMs for Exadata nodes are in the list, skip to Step 3. If ILOMs are not in the
list, proceed with Step 2.
2. Activate ILOM. Run the following command:
asr activate_asset -i [Node ILOM IP]
or
asr activate_asset -h [Node ILOM hostname]
3. Activate the Exadata OS side of the ASR support. Run one of the following
commands:
asr activate_exadata -i [Node IP address] -h [Node hostname] -l [Node ILOM IP]
or
asr activate_exadata -i [Node IP address] -h [Node hostname] -n [Node ILOM
hostname]
Notes:
The commands listed below are to be run on the ASR Manager
host, not on Exadata hosts.
Repeat for each Oracle Exadata Database Machine being attached
for ASR.
Refer to ASR SNMP Trap Destination and Grid Control on Exadata
Cell Nodes (Doc ID 1451026.1). You must ensure that for any SNMP
addition, the ASR entry is last in the snmpsubscriber string. You
can access Doc ID 1451026.1 in My Oracle Support:
https://support.oracle.com
Note: Use the script file generated by OneCommand's setupASR
step, if available. The script, which includes the asr activate_asset
command, is located here:
/opt/oracle.SupportTools/onecommand/AsrActivationScript.txt
This script is valid as long as the IPs for all nodes have not changed
since initial deployment.
10
4. Verify all nodes are visible on the ASR Manager. Run the following command:
asr list_asset
5. Approve and assign contacts to nodes. For more information on the process, see
ASR MOS 5.3+ Activation Process (Doc ID 1329200.1).
Exadata Validation and SNMP Test Trap Commands
Run the following commands to validate SNMP trap configurations.
Database node configuration validation
To verify using the dcli utility, run the following command on an Exadata
Database Machine host (you will need to run this command from an account that
has equivalency with the root user on the database nodes):
dcli -g /opt/oracle.SupportTools/onecommand/dbs_group -l root n
"/opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -get_snmp_subscribers -type
asr"
To verify if the dcli utility is not available, run the following command on each
Exadata Database Machine host:
/opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -get_snmp_subscribers -type
asr
Storage node configuration validation
To verify using the dcli utility, run the following command on the first database
node host (you will need to run this command from an account that has
equivalency with the celladmin user on the cells):
dcli -g /opt/oracle.SupportTools/onecommand/cell_group -l celladmin "cellcli -e
list cell attributes snmpsubscriber"
To verify if the dcli utility is not available, log on as celladmin and run the
following command on each Exadata cell storage host:
cellcli -e "list cell attributes snmpsubscriber"
Database node SNMP validation
To verify using the dcli utility, run the following command on an Exadata
Database Machine host:
dcli -g /opt/oracle.SupportTools/onecommand/dbs_group -l root
"/opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -validate_snmp_
subscriber-type asr"
Note: Use the script file generated by OneCommand's setupASR
step, if available. The script, which includes the asr activate_
exadata command, is located here:
/opt/oracle.SupportTools/onecommand/AsrActivationScript.txt
This script is valid as long as the IPs for all nodes have not changed
since initial deployment.
11
To verify if the dcli utility is not available, run the following command on each
Exadata Database Machine host:
/opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -validate_snmp_subscriber
-type asr
Storage node SNMP validation
To verify using the dcli utility, run the following command on each Exadata cell
storage host:
dcli -g /opt/oracle.SupportTools/onecommand/cell_group -l celladmin "cellcli -e
alter cell validate snmp type=asr"
To verify if the dcli utility is not available, run the following command on each
Exadata cell storage host:
cellcli -e "alter cell validate snmp type=asr"
Once the Validate SNMP Trap step is done, you will receive a confirmation e-mail on
the MOS Registration ID user e-mail account. No actual Service Request will be
opened. If no e-mail is received, contact ASR support.
For the most up to date validations, please refer to MOS Note 1450112.1 (ASR Exadata
Configuration Check via ASREXACHECK). This note will be updated with the latest
checks available for ASR. The note is available in My Oracle Support:
https://support.oracle.com
Resources
Oracle ASR
Oracle ASR product page:
http://www.oracle.com/asr
Oracle Exadata products qualified for ASR:
http://www.oracle.com/technetwork/server-storage/asr/documentation/asr-
qualified-exadata-325098.html
Oracle ASR user documentation, including products qualified for ASR, fault
coverage, etc.:
http://www.oracle.com/technetwork/server-storage/asr/documentation/inde
x.html
Oracle ASR Installation and Operations Guide (pdf):
http://www.oracle.com/technetwork/server-storage/asr/documentation/asru
d-323492.pdf
Download Oracle ASR software (MOS log in required):
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=S
YSTEMDOC&id=1185493.1
ASR MOS 5.3+ Activation Process (Doc ID 1329200.1)
Oracle Exadata Database Machine Documentation
Oracle Exadata Command and Configuration Reference:
12
http://www.oracle.com/technetwork/articles/oem/exadata-commands-intro-4
02431.html
DCLI group definitions (Part 2):
http://www.oracle.com/technetwork/articles/oem/exadata-commands-part2-4
02442.html
DCLI Setup and Commands (Part 3):
http://www.oracle.com/technetwork/articles/oem/exadata-commands-part3-4
02445.html
My Oracle Support (MOS)
MOS log in (Flash required):
https://support.oracle.com
MOS log in (non-Flash):
https://supporthtml.oracle.com/ep/faces/index.jspx
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers have access to electronic support through My Oracle Support. For
information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or
visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing
impaired.
Oracle Auto Service Request Exadata Database Machine Quick Installation Guide, Release 3.9
E23333-04
Copyright 2012, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected
by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate,
broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering,
disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them
to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the
following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government
customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions
and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the
additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway,
Redwood City, CA 94065.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use
in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in
dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe
use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks
or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered
trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle
Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products,
and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of
third-party content, products, or services.
This product includes software developed by the JDOM Project.
Copyright 2000-2004 Jason Hunter & Brett McLaughlin. All rights reserved. Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
13
Redistributions of source code must retain the above copyright notice, this list of conditions, and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the disclaimer that follows these conditions in
the documentation and/or other materials provided with the distribution.
The name "JDOM" must not be used to endorse or promote products derived from this software without prior written permission. For written
permission, please contact.
Products derived from this software may not be called "JDOM", nor may "JDOM" appear in their name, without prior written permission from the
JDOM Project Management.
THIS SOFTWARE IS PROVIDED AS IS' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE JDOM AUTHORS OR THE PROJECT CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many individuals on behalf of the JDOM Project and was originally created by Jason
Hunter and Brett McLaughlin. For more information on the JDOM Project, please see http://www.jdom.org.
14