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