2 Installing and Registering ASR Manager Software

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. Installing ASR Manager Software

  2. Registering the 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 the ASR backend infrastructure.


Once you have registered the ASR Manager, many ASR features are enabled by default (such as, ASR Manager Auto Update). See Managing Your Oracle ASR Environment 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 Installing ASR Manager Software

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


Beginning with ASR 5.0, Oracle Automated Service Manager (OASM) is no longer required.


As part of the ASR 5.0 release, the following directories have changed:
  • The /opt/SUNWswasr directory is replaced by the /opt/asrmanager directory.

  • The /var/opt/SUNWsasm directory is replaced by the /var/opt/asrmanager directory.


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 Installing Services Tools Bundle (STB) - Solaris 10 Only for more information.

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

Follow the procedure below to install the ASR package for the first time on the ASR Manager system:


To upgrade an installed version of ASR Manager, see Manually Upgrading ASR Manager Software for details. The instructions outlined below are for new installations only.
  1. Download and unzip the ASR software package from My Oracle Support:

  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 ASR package, install the ASR package using the following command:

    • For Solaris, run: pkgadd -d <asrmanager-version_num-time_stamp>.pkg

    • For Linux, run: rpm -i <asrmanager-version_num-time_stamp>.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. To avoid need to type the full path name the ASR Manager asr command, you can apply one of the following options:

    • 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):

      export PATH
    • Create a symbolic link to the asr command in the /usr/bin directory:

      ln -s /opt/asrmanager/bin/asr /usr/bin


    The instructions assume that you are able to run the ASR Manager command by typing asr.
  6. Confirm proper network connectivity between the ASR Manager and Oracle, as described in Test Connectivity from the ASR Manager to Oracle. When complete, continue to Registering the ASR Manager.

2.2 Registering 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.


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:



      See Installing ASR Manager Software 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

    Enter 1 to select:

    1) transport.oracle.com


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

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

  5. Upon entry of your MOS 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.


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. Once you install and register the ASR Manager as described in this chapter, complete the instructions in the Configuring and Activating 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


    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)


    Linux runs on x86 servers, and logical domains are specific to Solaris SPARC servers.
  • Virtual environments: ASR Manager is supported in virtual environments (such as Oracle VirtualBox, VMWare, and others) that meet the operating system, software, and network requirements.

  • 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 Enabling HTTP Receiver for ASR Manager Relay, Solaris 11, and SDP2

The ASR Manager can be configured as a relay for other ASR Managers, Solaris 11 servers, and Service Delivery Platform 2 (SDP2) for tape library products (Figure 2-1):

Figure 2-1 ASR Manager Relay

Surrounding text describes Figure 2-1 .


Beginning with ASR 5.4, the Auto Update feature has been enabled for those ASR Managers behind the relay. However, any ASR Manager behind the relay and facing DTS must be manually updated to ASR 5.4 or later before the Auto Update feature can take effect.

See Manually Upgrading ASR Manager Software for details.

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>


    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. Run the following commands:

    /opt/asrmanager/bin/asr set_property org.osgi.service.http.host <IP_address_of_ASR_manager>
    /opt/asrmanager/bin/asr set_property org.osgi.service.http.port <http_port>
    /opt/asrmanager/bin/asr set_property org.apache.felix.http.enable true

    Restart the ASR Manager and test the HTTP receiver as described in step 2.

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


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.

Generate and install the SSL Certificate into the Key Store specific to the Java/JDK that the ASR Manager is pointing to:

  1. Generate the Certificate Signing Request:

    1. Enter the following command:

      # keytool -genkey -alias <aliasName> -keyalg <keyAlgorithm> -keysize <keySize> -sigalg <signatureAlgorithm> -keystore <keyStoreFile.jks>

      Enter the valid key store password and specify the key password. Enter the Country, Locality, Organization and Common Name.

    2. Enter the following command:

      # keytool -certreq -alias <aliasName> -keystore <keyStoreFile.jks> -sigalg <signatureAlgorithm> -file <certRequestFile.cer>

      Enter the valid key store password and specify the key password.

    Submit the Certificate Signing Request <certRequestFile.cer> to the Certificate Authority, and request a Certificate.

  2. Install that Certificate once you receive it from Certificate Authority:

    # keytool -import -trustcacerts -alias <aliasName> -file <certFileFromCA> -keystore <keyStoreFile.jks>

    Enter the valid key store password and specify the key password.

  3. Once the SSL certificate from a trusted authority is loaded into keystore, run the following commands:

    # asr
    asr> set_property org.osgi.service.http.host <IP_address_of_ASR_manager>
    asr> set_property org.osgi.service.http.port.secure <https_port>
    asr> set_property org.apache.felix.https.keystore <https_keystore>
    asr> set_property org.apache.felix.https.keystore.password <https_keystore_password>
    asr> set_property org.apache.felix.https.keystore.key.password <https_keystore_key_password>
    asr> set_property org.apache.felix.https.truststore <https_truststore>
    asr> set_property org.apache.felix.https.truststore.password <https_truststore_password>
    asr> set_property org.apache.felix.https.enable true

    Trust Store information is same as the Key Store information.

    Passwords above can be plain text or obfuscated as follows:

    jar -xvf /opt/asrmanager/lib/com.oracle.asr.http.receiver.jar
    java -classpath org.apache.felix.http.bundle-2.2.0.jar  org.mortbay.jetty.security.Password <plain-text-password>

    Then copy/paste the output line starting with OBF: (including the OBF: part) into the above commands..

  4. Restart ASR Manager:

    • Solaris: svcadm restart asrm

    • Linux: service asrm restart

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


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.


The following layering scenarios for ASR Managers (ASRMs) are supported (all ASR Managers must be at ASR 5.3 or later):
  • Any http/s client --> ASRM --> Oracle Transport

  • Any http/s client --> ASRM --> ASRM Relay --> Oracle Transport

AND within a given customer network:

  • Any http/s ASR client --> ASRMa --> ASRM Relay --> Oracle Transport

  • Any http/s ASR client --> ASRMb --> ASRM Relay --> Oracle Transport

  • Any http/s ASR client --> ASRM[n] --> ASRM Relay --> Oracle Transport

2.4 Configuring 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 Verifying Your Network Connection. If you are not using a proxy server, enter: - (hyphen).

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>
Is this SOCKS proxy [y,n] 
Is this SOCKS proxy [y,n] - enter "y" if proxy used is SOCKS otherwise enter "n"


If you are using an NTLM-type proxy, enter the information below; otherwise, enter a hyphen ( - ).

Screen output should look like this:

NTLM Domain: ? <NTLM domain name>
NTLM Host: ? <hostname of the ASR Manager server>

2.5 Configuring ASR Manager for SNMP v3

ASR Manager supports two SNMP v3 telemetry sources: ILOM 3.0.16 and later (see Enabling ILOM Telemetry for details to enable ILOM telemetry for your ASR assets) and M-Series XSCF (see Enabling M-Series XSCF Telemetry for details to enable XSCF telemetry for your ASR assets).


If ILOM or M-Series XSCF is not your telemetry source, then skip this section.

SNMP v3 provides security (encryption and authentication) for any communication between an ASR asset.

To configure your designated ASR Manager to allow ASR assets to use SNMP v3 through ILOM or M-Series XSCF, you must create an SNMP v3 user:

  1. Create an SNMP v3 user:

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


    • ASR Manager only supports the SHA protocol for authentication. It supports AES (ILOM) and DES (M-Series XSCF) for privacy and encryption.

    • The authentication password is case-sensitive and must contain 8 to 16 characters, with no colons or space characters.

    • ASR Manager supports only two SNMP v3 users at this time.

    • To enable the proper telemetry for your ASR assets, see:


    ILOM only: 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 Optional ILOM Setup: SNMP v3 for ASR Assets 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.


    • ASR Manager only supports the SHA protocol for authentication and the AES (ILOM) and DES (M-Series XSCF) protocols for privacy and encryption.

    • ASR Manager supports only two SNMP v3 users at this time.

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 Optional ILOM Setup: SNMP v3 for ASR Assets 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 A, "Other ASR Manager Administration" describes how to set up the ASR Manager in a high availability environment.

2.7 ASR Manager on IPv6

For IPv6, the ASR Manager server needs to be enabled for dual stack IPv6/IPv4. ASR Manager supports IPv6 to and from assets configured for ASR. The traffic outbound from the ASR Manager to transport.oracle.com currently only supports IPv4 traffic.