|Oracle® Auto Service Request Quick Installation Guide
Quick Installation Guide
Oracle Auto Service Request (ASR) is is designed to automatically open Oracle Service Requests when specific faults are detected on Oracle products that are qualified for ASR. This document provides quick installation instructions for setting up the ASR Manager and for configuring ASR Assets:
Note:Refer to the Oracle Auto Service Request Installation and Operations Guide for a complete list of prerequisites and requirements:
Examples presented in this document of ASR commands assumes you have updated the
PATH=$PATH:/opt/SUNWswasr/bin export PATH
You must first set up the ASR Manager before you set up and configure ASR Assets.
Note:You must log in as
Oracle Automated Service Manager (OASM) is only installed on the ASR Manager system. To verify you have OASM version 1.4.1 or later:
pkginfo -l SUNWsasm
rpm -q SUNWsasm
If OASM is already installed on the ASR Manager, then proceed to Install Oracle ASR Package. If it is not installed, then refer to the Oracle Auto Service Request Installation and Operations Guide for instructions to download and install OASM.
To install Oracle ASR on a server running Oracle Solaris or Linux:
Download and unzip the ASR package (see Doc ID 1185493.1 on My Oracle Support). As root:
pkgadd -d SUNWswasr.[version_num].pkg
rpm -i SUNWswasr.[version_num].rpm
As the installation progresses, you are prompted to make several selections, including:
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.
To register the ASR Manager with Oracle:
As root on the ASR Manager system, run:
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 ( - ).
When prompted, enter your My Oracle Support user name and password. ASR will validate the login. Once validated, the registration is complete.
Note:Passwords are not stored.
Once installed and registered, Oracle ASR provides the functionality to check the ASR software update server for any software updates. If there is a newer version, it will (by default):
Automatically download and install the latest Oracle ASR software bundle.
Send an e-mail notification that installation is complete or if there was any problem encountered.
Store the previous version of Oracle ASR to the
If necessary, you can disable the Auto Update feature:
The ASR Manager can be configured as a relay for other ASR Managers, Solaris 11 servers, and Virtual Operator Panel (VOP) for tape library products.
To enable this capability, use the
asr enable_http_receiver command. Select a port for the HTTP receiver that is appropriate for your network environment and does not conflict with other network services. To show the current HTTP receiver configuration port and status, run:
Follow the procedure below to enable the HTTP receiver for Solaris 11 ASR Assets. Make sure you are logged in to the ASR Manager system as root.
After installing Oracle ASR on the ASR Manager, enable the HTTP receiver:
asr> enable_http_receiver -p <port_number>
Note:If you need to disable the HTTP receiver, run:
Verify the HTTP receiver is up and running. In a browser, go to:
A message will display indicating that the HTTP receiver is up and running.
Note:If you need to use HTTPS, see the Oracle Auto Service Request Installation and Operations Guide for instructions.
Once you have set up the ASR Manager, follow the instructions below to install, configure, register and activate your qualified ASR Assets.
Note:An ASR Manager can also be activated as an ASR Asset. See the Oracle Auto Service Request Installation and Operations Guide for more information and special considerations:
ASRAssetBundle.tar to each asset requiring OHMP and/or Solaris 10 FMA fault telemetry.
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.
root on the ASR Asset system, unzip and untar the file.
The ASR Manager can receive telemetry from multiple sources (such as ILOM and FMA). Check the list of qualified hardware to verify the fault telemetry source needed for each asset identified.
For instructions for configuring all supported types of fault telemetry, see the Oracle Auto Service Request Installation and Operations Guide
Follow the procedures below to enable ILOM telemetry. It is assumed that a network connection to the platform's dedicated service processor (SP) is connected and configured. Do not continue with the installation unless you have confirmed the initial ILOM setup.
Note:Some platforms support Sideband Management, which enables support for ILOM telemetry through a host network port.
Open a terminal window and ssh to the IP address of the ILOM network interface:
Log in as
Because ILOM supports up to 15 user-configurable alert rules, run the following command to determine an available alert rule slot.
For Rack Mount Servers and Blades:
-> show /SP/alertmgmt/rules/x
For the Sun Blade 6000 Chassis:
-> show /CMM/alertmgmt/rules/x
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
Confirm that SNMP services are enabled:
Verify that the "port" is 161 and that "v2c" is enabled.
Repeat for each ASR Asset using ILOM.
root, launch the ASR Asset Menu:
From the Asset Menu, select 3 to enable Solaris 10 SNMP trap destination (management host).
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) ," press [Return] or enter another port if you have changed your port settings for ASR.
For the prompt
"Do you want to set trapdestination [y,n, q]," enter Y and press [Return].
Repeat for each ASR Asset.
Note:This step does not apply to M-series, X6270, or X6275 systems.
Open a terminal window and log in as
root on the ASR Manager system. Important: Activating ASR Assets is not done on the assets themselves but on the ASR Manager system only.
Run the following activate command for each ASR Asset. Be sure to use the IP or hostname of the ASR Asset system.
asr> activate_asset -i [IP_Address]
asr> activate_asset -i [hostname]
Note:To activate Sun Blade Systems and Chassis ASR Assets (for both Solaris 10 and Solaris 11), see the Oracle Auto Service Request Installation and Operations Guide:
Follow the steps below to active ASR Assets for Solaris 11 systems:
Log in to the ASR Asset as the
Run the following command to register the endpoint URL:
asradm register -e http://[asr_manager_host]:[port_number]/asr
Enter your Oracle SSO user name and password.
asradm list command to view the status.
Log in to My Oracle support to complete the activation. See Enable ASR Assets in My Oracle Support.
To send a test e-mail:
asradm send test [email@example.com]
Note:If you need to unregister and deactivate your ASR asset, run:
To complete the installation of Oracle ASR:
Log in to My Oracle Support (
In the My Oracle Support Dashboard, click the More... tab. Then select Settings from the menu.
In the Settings pane on the left of the window, select Assets (located under the Administrative submenu). For your Support Identifier, select ASR Status from the sort filter, then select Pending from the All Statuses drop-down menu:
Note:By default, all support identifiers that you are associated with are displayed. If this list of assets is long, you can limit the display to show only assets associated to one support identifier.
You can filter and sort on asset columns to find the assets you are interested in.
You can approve a Pending asset two ways:
Activate via Asset Toolbar. Click the asset's serial number to display a toolbar, which includes an option to Approve. Click Approve to enable ASR for the asset.
Note:You can use the Asset Toolbar to update multiple assets:
Activate via Asset Details
At the bottom of the Asset pane, there is a "Show Asset Details" option. Click an asset's serial number and then Show Asset Details to update information about the asset.
Required fields for ASR Asset activation are indicated by an asterisk (*). You should update and verify all required fields.
Oracle ASR product page:
Oracle ASR user documentation:
Oracle Technology Network:
ASR Documentation Library
My Oracle Support:
Download Oracle ASR software (including OASM) from My Oracle Support. See Doc ID 1185493.1.
How to activate ASR within My Oracle Support (Doc ID 1329200.1)
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at
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 4.4
Copyright © 2013, 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:
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.