Install the ASR Manager

Prerequisite Tasks

The following tasks should already be complete before the ASR Manager is installed:

• Create a Sun Online Account (SOA) (see "Create a Sun Online Account").

• Assess ASR Systems (see "Oracle Auto Service Request Configuration Requirements" and "Telemetry Sources: Overview and Check") (OS version check, network validation, JDK version check, verify existing telemetry sources).

Because the ASR Manager no longer requires being installed on a device that is currently under an Oracle Service Contract and that the server has been qualified for ASR, you now have more flexibility regarding how you can install ASR. Some of the possibilities include:

• x86 or SPARC Server running Solaris 10u6 or later

  • local zone

    Note:

    If the ASR Manager is installed on a local zone, it is not possible to activate the ASR Manager as an ASR asset. If this is attempted, an error will be received: Asset cannot be activated due to unknown product name or serial number. This is a known issue expected to be corrected in a future version of Oracle ASR.

• SPARC Server running Solaris 10u6 or later

  • logical domains

• x86 Server running Oracle Enterprise Linux (OEL) 5.3 or later

• Windows 7/Windows XP

  • VirtualBox running Solaris 10u6 or later

  • VirtualBox running OEL 5.3 or later

• Installation on M-Series domains and blade servers

The ASR Manger still has to be registered but no longer has to be activated as an ASR Asset. The requirement that the ASR Manager has to be activated for ASR before activating other ASR Assets has also been lifted.

An ASR Manager can still be activated as an ASR Asset, if it is qualified for ASR and entitled to service.

Install Service Tags

This section provides instructions for downloading the appropriate software to enable service tags for Solaris and Oracle Enterprise Linux (OEL) systems.

Check for SASM Installation and Version

Follow the procedure below to determine if you already have SASM. For more information on the relationship between SASM and ASR, refer to "Close-Up of the ASR Manager".

1. Open a terminal window to the system where the ASR Manager is to be installed and log in as root.

2. Run the following command to determine the existence and version of SASM:

   • For Solaris, run: pkginfo -l SUNWsasm

   • For OEL, run: rpm -q SUNWsasm

3. Make note of the results and continue to the next section.

   Note:

   SASM on Linux (including OEL) will add a crontab on install to check that sasm is running. The default values are to check every 12 minutes.

Download the SASM and ASR Packages

If you do not have Sun Automated Service Manager (SASM) installed, follow the procedure below to download both the SASM and ASR packages.

1. From the machine where the ASR Manager is to be installed, open a terminal window and make sure you are logged in as root.

2. In a browser, click the following links to download SASM and ASR packages. You must login to My Oracle Support (https://support.oracle.com). See Document ID 1185493.1 for the software download links for SASM and ASR.

   Note:

   If a browser is not available, download the files to another machine and copy them to the machine where the ASR Manager is to be installed.

3. Once the file(s) are downloaded, go to the download directory, or other directory where you copied the .zip file(s), and unzip the file(s). Be certain that the file(s) are copied to an installation directory on the system where the ASR Manager is to be installed before unzipping them.

   • For Solaris: gunzip SUNWsasm.version_num.pkg.gz (if downloaded) gunzip SUNWswasr.version_num.pkg.gz

4. If you do not need to install SASM, skip the following procedure and go to "Install the ASR Package". Otherwise, continue to the following procedure.

Install the SASM Package

Follow the procedure below to install SASM.

1. Open a terminal window and make sure you are logged in to the ASR Manager system as root.

2. From the directory where you unzipped the SASM package, install the SASM package using the following command:

   • For Solaris, run: pkgadd -d SUNWsasm.version_num.pkg

   • For OEL, run: rpm -i SUNWsasm.version_num.rpm

   Note:

   See "Installing ASR Manager on Blade Systems" for additional information on installing the ASR Manager on a blade system.

3. 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.

4. Once the installation completes successfully, continue to "Install the ASR Package".

You can run sasm status to get the status of the SASM process. Running this command will return the process ID (PID) of SASM.

Install the ASR Package

Follow the procedure below to install the ASR package on the ASR Manager system.

1. Open a terminal window and make sure you are logged in to the ASR Manager system as root.

2. From the directory where you unzipped the ASR package, install the ASR package using the following command:

   • For Solaris, run: pkgadd -d SUNWswasr.version_num.pkg

   • For OEL, run: rpm -i SUNWswasr.version_num.rpm

3. 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.

4. Add the asr command to the PATH (update to the root's .profile, .cshrc, .kshrc, or .bashrc files as needed) (for both Solaris and OEL):

   • PATH=$PATH:/opt/SUNWswasr/bin export PATH

5. To confirm proper network connectivity between the ASR Manager and Oracle, go to"Test Connectivity from the ASR Manager to Oracle". When complete, continue to the next procedure "Register the ASR Manager".

Register the ASR Manager

Follow the procedure below to register the ASR Manager (for both Solaris and Oracle Enterprise Linux machines). Make sure you are logged in to the ASR Manager system as root.

1. To register the ASR Manager, run: asr register

2. Enter 1 or 2 depending on your geographic location: 1) transport.sun.com (Americas or Asia Pacific regions) 2) transport.sun.co.uk (Europe, Middle East, or Africa regions)

3. If you are using a proxy server for access to the internet, enter the proxy server information as you determined in "ASR Manager Network Connection Requirements". If you are not using a proxy server, enter: - (hyphen).

   Note:

   If you are using a SOCKS proxy, enter the hyphen - for no proxy. When completed with the steps in this procedure, manually edit the SASM config.ini file with your SOCKS proxy server information. For instructions, refer to "Configure ASR to Send HTTPS Traffic Through a Proxy Server". If you are using an NTLM proxy, pay close attention to the requirements as shown in the installation prompts (shown below). You may have to contact a network administrator for assistance.

4. Screen output should look like this:

   Proxy server name: ? <proxy server name>
   Proxy port number: ? <proxy port number>
   Proxy authentication; if authentication is not required, enter -.
   Proxy user: <proxy user name>
   Proxy password: <proxy password>
   If this is an NTLM type proxy, enter the information below.
   Otherwise, enter -
   NTLM Domain: [?] <NTLM domain name>
   Enter the host the NTLM authentication request is originating
   from. Usually this is the hostname of the SASM server.
   NTLM Host: [?] <NTLM host name>
   NTLM support is not bundled with SASM but may be added now.
    
   1) Download jCIFS from http://jcifs.samba.org/
   2) Extract contents and locate the jcifs-*.jar file
   3) Enter full path to this file below
    
   jCIFS jar file: [?] <full path of jCIFS jar file>
   Note: These properties are stored in the /var/opt/SUNWsasm/configuration/config.ini file. You can update these properties if needed and then restart the SASM.
   

5. Enter the username and password of your Sun Online Account (SOA) when prompted.

6. Upon entry of your SOA credentials, ASR will validate the login. Once validated, the registration is complete.

7. Check the registration status of ASR. Run: asr show_reg_status

   A message is displayed on the screen indicating whether ASR is registered with the transport server.

8. To be sure that ASR can send information to the transport server, run:

   asr test_connection
   

   This command sends a test message (ping) to the transport server.

9. Upon successful results of the above commands, the registration of the ASR Manager is complete.

Set Up Crontab

Crontab entries are automatically created when the ASR Manager is installed. These crontab entries perform the following tasks:

• asr heartbeat: This task sends a message to the Oracle backend server every 12 hours. If the Oracle/ASR back-end systems do not receive the heartbeat in 48 hours, they send an email to the Sun Online Account (SOA) technical contact used to install/register the ASR Manager. Refer to "ASR Emails" for more information.

  Note:

  The ASR Manager must be configured correctly to send the daily cron job for asr heartbeat. Failure to do so will result in the unit being marked a 'Heartbeat Failure' unit

  If a SASM Manager is in Heartbeat Failure mode for 90 days, it will be automatically deactivated at the ASR backend and in My Oracle Support. Also, any assets that are configured via that ASR Manager will also be marked deactivated. This will prevent any future events creating automatic Service Requests.

  You check to see if any ASR Manager or ASR Asset are in 'Heartbeat Failure' by reviewing the ASR status in My Oracle Support.

• asr update_rules: ASR uses fault rules to filter the telemetry data sent from ASR Assets. This filtering is done to remove telemetry that contains no real fault data and general telemetry “noise.” The filtering process also ensures that telemetry that contains faults is reported. These fault rules can change as ASR improves its filtering and as new platforms and telemetry sources are supported by ASR. ASR installs a cron job on the ASR Manager system to periodically check Oracle's autoupdate server for any new rules updates. When there are new rules, the ASR Manager automatically downloads and installs the latest rules bundle. If the cron job is not set to download the fault rules automatically, an email is sent to the SOA login name used to install and register ASR. For more information on fault rules, refer to "ASR Emails".

  Note:

  If the asr heartbeat is disabled in crontab, you will not be notified, via email, if your ASR fault rules are out of date with the most current release. To be sure your fault rules are current, you can run the asr update_rules command from the ASR Manager system.

The crontab entries are set-up as follows and can be changed by the ASR installer as needed:

asr heartbeat: 0 0,12 * * * /opt/SUNWswasr/bin/asr heartbeat

asr report: 0 6 1 * * /opt/SUNWswasr/bin/asr report

update rules: 0 <random number between 1-59> 0 <random number between 1-23> * * * /opt/SUNWswasr/bin/update_rules.sh