Skip Headers
Oracle® Auto Service Request Installation and Operations Guide
Release 4.9 for Linux and Solaris

E18475-28
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

2 Oracle ASR Manager

The ASR Manager is a system that centrally accepts hardware telemetry data sent from a group of ASR Assets. The ASR Manager filters the incoming data and forwards potential fault telemetry to Oracle/ASR Backend systems.

This chapter explains how to install the software necessary for an ASR Manager, which must be installed first before ASR Assets. Installing the ASR Manager consists of the following tasks:

  1. Install Software

  2. Register the ASR Manager

Note:

Once you have registered the ASR Manager, many ASR features are enabled by default (such as, Using Auto Update to Upgrade Oracle ASR). See ASR Environment Administration for information on customizing your ASR environment.

Depending on your hardware and network configuration, you may be required to complete the following optional tasks to complete your ASR Manager installation:

2.1 Install Software

This section provides instructions for installing the appropriate software for the ASR Manager:

Note:

You can specify an ASR Manager to be monitored as an ASR Asset. If the ASR Manager that you want to monitor as an ASR Asset is running Solaris 10, then Services Tools Bundle must be installed. See Install Services Tools Bundle (STB) for more information.

STB is not a requirement for all systems. For example:

2.1.1 Install OASM

Follow the procedure below to install OASM.

Note:

OASM is installed on the ASR Manager system only, not ASR Assets.

See Oracle Automated Service Manager (OASM) Requirements - ASR Manager Only for information on the supported versions of OASM.

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

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

  3. From the directory where you unzipped the OASM package, install the OASM package using the following command:

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

    • For Linux, run: rpm -i SUNWsasm.version_timestamp.rpm

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

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

Run the following command to get the status of the OASM process ID (PID):

  • For Solaris: svcs sasm

  • For Linux: service sasm status

Note:

OASM requires Java 7 or later. If you have an incorrect or older version of Java, you will receive an error message when you try to run the ASR Manager. See Resolve ASR Manager Java Path Location in config.ini File for instructions to correct this issue.

2.1.2 Install ASR

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. Verify that OASM is running. To get the status of the OASM process ID (PID):

    • For Solaris, run: svcs sasm

    • For Linux, run: service sasm status

    If OASM is not running, then start it with:

    • For Solaris, run: svcadm enable sasm

    • For Linux, run: service sasm start

  3. 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 Linux, run: rpm -i SUNWswasr.version_num.rpm

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

  5. Add the asr command to the PATH environment variable. This update would be made to the root user's .profile, .cshrc, .kshrc, or .bashrc files as needed (for both Solaris and Linux):

    PATH=$PATH:/opt/SUNWswasr/bin
    export PATH
    
  6. 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 Register the ASR Manager.

2.2 Register the ASR Manager

Follow the procedure below to register the ASR Manager (for both Solaris 10u6, Solaris 11, and Linux systems). Make sure you are logged in to the ASR Manager system as root.

Note:

If you are upgrading your ASR Manager installation, then you do not need to re-register.
  1. Log in to the ASR console:

    • If you have not set your PATH environment variable, run:

      /opt/SUNWswasr/bin/asr
      

      Note:

      See Install ASR for instructions for setting the PATH environment variable.
    • If you have set your PATH environment variable, run:

      # asr
      
  2. To register the ASR Manager:

    asr> register
    

    Note:

    If you are registering the system with an ASR Manager Relay, see Enable HTTP Receiver for ASR Manager Relay, Solaris 11, and VOP.
  3. Enter proxy server details:

  4. Enter the username and password of your My Oracle Support account when prompted.

  5. Upon entry of your My Oracle Support credentials, ASR will validate the login. Once validated, the registration is complete.

  6. Check the registration status of ASR:

    asr> show_reg_status
    

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

  7. To be sure that ASR can send information to the transport server:

    asr> test_connection
    

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

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

Note:

ASR Audit Logging is enabled by default, regardless if your ASR Manager is disabled or unregistered. See ASR Audit Logging for more details.

2.2.1 ASR Manager as an ASR Asset (Solaris Only)

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 in this chapter, complete the instructions in the Oracle ASR Assets chapter.

2.2.2 ASR Manager Support for Other Platforms

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:

  • Local zone: for SPARC or x86 server running Solaris 10u6 or later

    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 returned:
    Asset cannot be activated due to unknown product name or serial number.
    

    Instead, activate the global zone of the asset, for example:

    asr> activate_asset -i <IP_address_of_the_global_zone>
    
  • Logical domains: for SPARC servers running Solaris 10u6 or later

  • x86 Server running Linux (see Linux (ASR Manager Only) for Linux versions supported)

    Note:

    Linux runs on x86 servers, and logical domains are specific to Solaris SPARC servers.
  • Windows 7/Windows XP:

    • VirtualBox running Solaris 10u6 or later

    • VirtualBox running Linux

  • Installation on blade servers:

    Before installing ASR Manager on a blade system, make sure the service svc:/milestone/multi-user-server status is online.

    • To check the status of this service, run:

      svcs svc:/milestone/multi-user-server
      
    • If the state indicates maintenance, run:

      svcadm clear svc:/milestone/multi-user-server
      svcadm enable svc:/milestone/multi-user-server
      
    • If the state indicates disabled, run:

      svcadm enable svc:/milestone/multi-user-server
      

2.3 Enable HTTP Receiver for ASR Manager Relay, Solaris 11, and VOP

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:

ASR Manager Relay

Solaris 11 includes the ability to send ASR fault events and telemetry to Oracle using xml over HTTP to the ASR Manager.

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:

asr> show_http_receiver

Follow the procedure below to configure the ASR Manager as a relay for other ASR Managers and Solaris 11 ASR Assets. Make sure you are logged in to the ASR Manager system as root.

  1. After installing the ASR Manager, enable the HTTP receiver:

    asr> enable_http_receiver -p <port_number>
    

    Note:

    If the following error message appears:
    Unable to determine the fully qualified domain name for this ASR Manager via DNS. Please refer to the Oracle ASR Installation and Operations Guide for troubleshooting information.
    

    If DNS is not available, then set up the HTTP receiver manually. Edit the /var/opt/SUNWsasm/configuration/config.ini file with the following properties:

    jetty.enable=true
    jetty.host=<IP_address_of_ASR_manager>
    jetty.http.port=<http_port>
    

    After updating the file, restart OASM and test the HTTP receiver as described in step 2.

  2. Verify the HTTP receiver is up and running. In a browser, go to:

    http://<asr_manager_host>:<port_number>/asr
    

    A message will display indicating that the HTTP receiver is up and running.

Note:

If you need to disable the HTTP receiver, run:
asr> disable_http_receiver

If you need to use HTTPS for security purposes, you can set up HTTPS/SSL for the ASR Manager HTTP receiver:

  1. The detailed steps for enabling https/SSL for Jetty are documented at http://docs.codehaus.org/display/JETTY/How+to+configure+SSL

  2. Once the SSL certificate from a trusted authority is loaded into keystore, then add the following SSL connector in /var/opt/SUNWsasm/configuration/jetty/jetty.xml below the <Call name="addConnector"> sections:

    <Call name="addConnector">
        <Arg>
          <New class="org.mortbay.jetty.security.SslSocketConnector">
            <Set name="Port">443</Set>
            <Set name="maxIdleTime">30000</Set>
            <Set name="keystore">/path/to/keystore</Set>
            <Set name="password">....</Set>
            <Set name="keyPassword">....</Set>
            <Set name="truststore">/path/to/keystore</Set>
            <Set name="trustPassword">....</Set>
          </New>
        </Arg>
      </Call>
    

    Passwords above can be plain text or obfuscated as follows:

    java -classpath lib/jetty-6.1.7.jar:lib/jetty-util-6.1.7.jar
    org.mortbay.jetty.security.Password <plaintext-password>
    

    Then copy/paste the output line starting with OBF: (including the OBF: part) into this jetty.xml config file.

  3. Restart OASM:

    • Solaris: svcadm restart sasm

    • Linux: service sasm restart

  4. Verify the SSL setup by accessing the following URL from a browser:

    https://<asr_manager_host>/asr
    

Even though an ASR Asset communicates its telemetry to one ASR Manager only, you can set up an ASR Manager to serve as a relay for other ASR Managers by sharing a common network connection to Oracle Support:

  1. Verify the HTTP receiver is enabled:

    asr> show_http_receiver
    

    Output should look like this:

    HTTP Receiver configuration:
    
    HTTP Receiver Status: Enabled
    Host Name: asrmanager1.mycompany.com
    HTTP Port: 8777
    HTTPS/SSL configuration is not enabled.
    
  2. To register an ASR Manager or Solaris 11 server with ASR Manager Relay:

    • On the ASR Manager machine, run:

      asr> register -e http://asrmanager1.mycompany.com:8777/asr
      
    • On a Solaris 11 server, run:

      asradm register -e http://asrmanager1.mycompany.com:8777/asr
      
  3. Test the connection:

    asr> test_connection
    

    Output should look like this:

    Connecting to ASR manager relay URL http://asrmanager1.mycompany.com:8777/asr
    Connectivity test to ASR manager relay completed successfully.
    

2.4 Configure ASR Manager to Use a Proxy Server

As part of the registration process for ASR Manager, you can optionally set the ASR Manager to access the internet through a proxy server.

In the step for proxy server settings, enter the proxy server information as you determined in 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 OASM 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.

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.

2.5 Configure ASR Manager for SNMP v3

The minimum required ILOM version for SNMP v3 support is ILOM 3.0.16 and later.

Note:

If ILOM is not your telemetry source, then skip this section.

Beginning with ASR 4.1, ILOM telemetry supports the SNMP v3 security protocol. SNMP v3 provides security (encryption and authentication) for any communication between an ASR Asset and OASM.

To configure your designated ASR Manager to allow ASR Assets to use SNMP v3 through ILOM, you must create an SNMP v3 user:

  1. Create an SNMP v3 user:

    asr> add_snmpv3_user -u userName -e engineId[,engineId2, ...] -pp privacyProtocol
    

    Note:

    ASR Manager supports adding multiple engine IDs (separated by comma) to the SNMP v3 user. The engine ID must match with the ILOM engine ID from ILOM Service processor. To view the ILOM engine id, run the following command from the ILOM Service Processor:
    show /SP/services/snmp
    

    For more information, see the Set Up SNMP v3 for ASR Assets (Optional) section.

    You will be prompted to create both authentication and privacy passwords.

  2. Show the SNMP v3 user:

    asr> show_snmpv3_user
    

    Running this command displays the SNMP v3 user name, engine IDs, and authentication and privacy protocols (algorithms). Passwords are not displayed.

    Notes:

    • ASR Manager only supports the SHA protocol for authentication and the AES protocol for privacy and encryption.

    • ASR Manager supports only one SNMP v3 user at this time. Multiple SNMP v3 users are not currently supported.

Once you have created the SNMP v3 user, you must configure the ASR Assets that use ILOM for a telemetry source to use SNMP v3. See Set Up SNMP v3 for ASR Assets (Optional) for more information.

Other options for managing the SNMP v3 user on the ASR Manager include:

  • Validate the authentication and privacy passwords of the SNMP v3 user:

    asr> validate_snmpv3_user
    

    You will be prompted to enter both authentication and privacy passwords.

  • Delete the SNMP v3 user:

    asr> delete_snmpv3_user
    

    You will be prompted to continue with the deletion. Enter Y to delete.

  • Add/delete the engine ID:

    asr> add_engine_id -e engineId[,engineId2, ...]
    asr> delete_engine_id -e engineId[,engineId2, ...]
    
  • Enable/disable SNMP v1 and v2c:

    asr> enable_snmpv1v2c : enable SNMPv1/v2c
    asr> disable_snmpv1v2c : disable SNMPv1/v2c
    

2.6 ASR Manager and High Availability

Appendix B, "Other ASR Manager Administration" describes how to set up the ASR Manager in a high availability environment.