Oracle Auto Service Request (ASR)

For ASR version 3.3 and later Quick-Installation Guide

About ASR
Configuration Requirements
Auto Service Request (ASR) is a secure, scalable, customer-installable software
feature of warranty and Oracle Support Services that provides auto-case generation Operating Systems (required for the ASR Manager)
when specific hardware faults occur. ASR is designed to enable faster problem
resolution by eliminating the need to initiate contact with Oracle Support Services for
Oracle Enterprise Linux (OEL) 5.3 and later
hardware failures, reducing both the number of phone calls needed and overall phone - or -
time required. Solaris 10, Update 6 (10u6) and later
Java Version: at least JRE/JDK 1.6.0_04
ASR also simplifies support operations by utilizing electronic diagnostic data. Easily
installed and deployed, ASR is completely controlled by you, the customer, to ensure Network connection: Connect to the Internet via HTTPS.
security. Other Software
Services Tools Bundle (STB) must be installed on all
Solaris ASR assets, including the ASR Manager
Need help? If you need assistance installing or configuring ASR, Service Tags must be installed on the OEL ASR Manager
then click the Contact Us link on My Oracle Support to open a Download the latest ASR and OASM packages (see doc
Service Request. 1185493.1 in from My Oracle Support)

Prerequisites Before You Start

Oracle Premier Support Contract Information
Make sure you have access to My Oracle Support and that
your contact information is correct and current.
If you will be approving assets for ASR, you will need to be
the Customer User Administrator (CUA) for the CSI(s)
associated with your assets.
Make sure your My Oracle Support account is associated
with a Customer Support Identifier (CSI) number.
All of your assets must have a Contact assigned to your
ASR hardware. Make sure the contact is correct and
current.
Hardware Information
Identify and designate a system to serve as ASR Manager.
Identify and verify ASR assets.
Identify telemetry sources.
Make sure your hardware qualifies for ASR (see
Sun Products Qualified for ASR).
Make sure your hardware is associated with a CSI number
in My Oracle Support.
For ASR Assets and ASR Manager Systems
Install Service Tags OEL
1. Service Tags 1.1.5 is required only on an OEL ASR
Manager that is also designated as an ASR Asset.
2. Download and unzip the latest Sun Service Tags zip file.
You can download Sun Service Tags 1.1.5 from here:
https://updates.oracle.com/download/12757884.html
3. Run the following commands to install the service tags:
rpm -i sun-servicetag-1.1.5-1.i386.rpm
rpm -i sun-hardware-reg-1.0.0-1.i386.rpm
Note: JRE/JDK 6 is required for Oracle Automated Service
Manager (OASM). You can download the latest version
from the Java SE Downloads page.
Resources
Oracle ASR Product Page
My Oracle Support
Sun Products Qualified for ASR
Oracle ASR Documentation
Install Service Tools Bundle (STB) Solaris
If your system is using only a service processor-
based telemetry source (ILOM, or XSCF on M-
Series), STB does not need to be installed. If this is
your configuration, then you can skip the STB install.
1. Download STB (see doc 1153444.1 in
My Oracle Support)
2. Untar the STB bundle and run the installation script
(install_stb.sh). STB version 6.0 and higher
defaults to installing all tools.
When prompted: Would you like to
(I)nstall, (X)tract component
selections, or (E)xit, press [Enter].
3. Confirm that SNEEP is installed correctly. Run:
sneep -a
4. Verify that Service Tags is reporting your system
attributes correctly. Run:
stclient -E
5. If stclient -E does not show the serial number,
register manually. Run:
sneep -s <serial number>

Copyright 2011, Oracle and/or its affiliates. All rights reserved. Page 1

For ASR version 3.3 and later
Part 1 Install ASR Manager for Solaris and OEL
Select a qualified Sun server running Solaris or Oracle Enterprise Linux to house the ASR Manager.
Install OASM Package
Oracle Automated Service Manager (OASM) is
only installed on the ASR Manager system. You
must login as root to install the ASR components.
1. From the directory where you unzipped the OASM
package, install the OASM package:
For Solaris:
pkgadd -d SUNWsasm.version_num.pkg
For OEL:
rpm -i SUNWsasm.version_num.rpm
2. As the installation progresses, you are prompted to
make several selections. Use the list below to
determine how to respond to the installation
prompts:
When prompted:
. . . install all packages, press [Return].
When prompted:
. . . install conflicting files, enter Y.
When prompted:
. . . scripts will be executed with
super-user permission during the
process of installing this package,
enter Y.
Need help? If you need assistance
installing or configuring ASR, then click the
Contact Us link on My Oracle Support to
open a Service Request.
Copyright 2011, Oracle and/or its affiliates. All rights reserved.
Oracle Auto Service Request (ASR)
Quick-Installation Guide
Install ASR Package
1. As root, install the ASR package:
For Solaris:
pkgadd -d SUNWswasr.version_num.pkg
For OEL:
rpm -i SUNWswasr.version_num.rpm
2. As the installation progresses, you are prompted
to make several selections. Use the list below to
determine how to respond to the installation
prompts:
When prompted:
. . . select all packages to process,
press [Return] to select all packages.
When prompted:
. . . install conflicting files, enter Y.
When prompted:
. . . scripts will be executed with
super-user permission during the
process of installing this package,
enter Y.
3. Add the asr command to the PATH (update to
the root's .profile, .cshrc, .kshrc. or .bashrc as
needed):
PATH=$PATH:/opt/SUNWswasr/bin/asr
export PATH
Learn More About ASR
For complete details, please see the
Oracle ASR product page
Register and Verify ASR Manager
1. As root on the ASR Manager system,
run 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
username and password. ASR will validate the
login. Once validated, the registration is
complete. Note: Passwords are not stored.
4. Check the registration status.
Run asr show_reg_status.
5. Test the connection to ensure that ASR can send
information to the transport server.
Run asr test_connection.
Note: An ASR Manager can be activated
as an ASR Asset, if it is qualified for ASR
and entitled to service. In this case, you
must select your ASR Manager from the
list of qualified hardware (see
http://www.oracle.com/asr).
Once you install and register the ASR
Manager as described here, go to Page 3
to complete the instructions for installing
ASR Assets.
Page 2

For ASR version 3.3 and later
Part 2 Install ASR and Configure ASR Assets
Select qualified ASR Assets running Solaris or Oracle Enterprise Linux
Install ASR Asset Bundle
If you are configuring an M-series system, X6270, or
X6275, skip this step and go to Enable M-Series XSCF
Telemetry.
1. Copy the ASRAssetBundle.tar to each asset requiring
SunMC and/or Sol 10 FMA fault telemetry.
2. As root on the ASR Manager system, go to the
/opt/SUNWswasr directory and make sure a copy of the
ASRAssetBundle.<version_num>.tar file is available on
each ASR asset system.
3. As root on the ASR Asset system, unzip and untar the file.
Activate ASR Assets
Active ASR Assets after the appropriate telemetry
sources have been set up.
The asr activate_asset command must be
run from the ASR Manager system.
All Systems (except Sun Blades)
For all systems (except for Sun Blades) using Solaris 10
FMA, SunMC, or XSCF as fault telemetry source, activate
with:
asr activate_asset -i <IP address>
or
asr activate_asset -h <hostname>
For All Blades
1. For the Sun Blade 6000 chassis (CMM), activate with:
asr activate_asset -i <Chassis_ILOM_IP>
2. For each Blade within the chassis using Solaris 10 FMA
as fault source, activate with:
asr activate_blade -i <Blade-NEMport-IP>
-c <Chassis_ILOM_IP>
3. For x6x70 Blades, activate with:
asr activate_blade -i <blade-ILOM-ip>
-c <Chassis_CMM_ip>
Complete Activation in My Oracle Support
For all assets, login to My Oracle Support to complete
activation. (See "Pending ASR Activations" and "Assets"
via "Settings".) Only a Customer User Administrator (CUA)
for the asset's CSI can approve an ASR activation.
Copyright 2011, Oracle and/or its affiliates. All rights reserved.
Oracle Auto Service Request (ASR)
Quick-Installation Guide
Set Up Telemetry Sources for ASR
The ASR Manager can receive telemetry from multiple
sources (SunMC, ILOM, FMA, XSCF). Check the list of
qualified hardware (see Sun Products Qualified for ASR) to
verify the fault telemetry source needed for each asset
identified.
These sources will need to be configured to provide
maximum fault coverage for your asset.
Enable Integrated Lights Out Manager
(ILOM) Telemetry (CLI)
1. Initiate an ssh connection to the IP address of the ILOM
network interface and login as root.
2. ILOM has up to 15 rules available. One of these rules will
be set for use with ASR. Select an available a rule, 1 15.
Confirm the rule is available (disabled) with:
For rackmount servers and qualified blades:
show /SP/alertmgmt/rules/x
For the Sun Blade 6000 Chassis:
show /CMM/alertmgmt/rules/x
3. Once you have an available rule, configure the following:
set destination=<IP address of ASR manager>
set destination_port=162
set type=snmptrap
set level=minor
set snmp_version=2c
set community_or_username=public
show /SP/alertmgmt/rules/x to confirm these
parameters
4. Confirm that SNMP services are enabled:
Run show /SP/services/snmp and verify that the port
is 161 and that v2c is enabled.
5. Repeat for each ASR asset using ILOM.
Learn More About ASR
For complete details, please see the
Oracle ASR product page
For any Solaris 11 asset activation,
please see the ASR Installation
and Operations Guide
Enable FMA/SunMC Telemetry
This step does not apply to M-series, X6270, or X6275
systems.
1. As root, launch the ASR Asset Menu:
/opt/SUNWswasr/asrassetbundle/asrassetmenu.sh
2. From the Asset Menu, select 3 to enable Solaris 10 SNMP
trap destination (management host). (If the asset requires
SunMC for ASR, select 2 to enable SunMC telemetry.)
For the prompt Please enter Hostname or IP Address of
OASM ASR plugin, enter the hostname or IP for the
installed ASR Manager system.
For the prompt Please enter SNMP port of SASM
ASR plugin (q to quit) [162], press [Return]
or enter another port if you have changed your port
settings for ASR.
For the prompt Do you want to set trap-
destination [y,n, q], enter Y and press [Return].
3. Repeat for each ASR asset.
Enable M-Series XSCF Telemetry
1. Initiate an ssh connection to the IP address of the XSCF
network interface and login to the XSCF console. Make sure
you have platadm privileges (showuser -p <login name>).
Run showuser -p to list users with this privilege.
2. Disable the SNMP agent. Run setsnmp disable
3. Add the ASR Manager system as the trap destination. Run
setsnmp addtraphost -t v2 -s public -p 162
xxx.xxx.xxx.xxx
-s = community string (default value is public)
-p = SNMP listener port (default value is 162)
xxx.xxx.xxx.xxx = ASR Manager IP address
4. Confirm the XSCF hostname is set as you would like.
Run showhostname -a
5. Enable the SNMP agent. Run setsnmp enable
6. Enable SNMP v1v2. Run setsnmp enablev1v2c public
7. Verify Service Tags are enabled. Run showservicetag
8. Verify SNMP settings to ensure the trap destination is set and
SNMP is enabled. Run showsnmp
9. Repeat for all M-Series ASR assets.
Page 3