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.
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 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:
Note:Beginning with ASR 5.0, Oracle Automated Service Manager (OASM) is no longer required.
Note:As part of the ASR 5.0 release, the following directories have changed:
/opt/SUNWswasr directory is replaced by the
/var/opt/SUNWsasm directory is replaced by the
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 Installing Services Tools Bundle (STB) - Solaris 10 Only for more information.
If your ASR Manager system is running Solaris 11, the installation of STB is not required. See Enabling HTTP Receiver for ASR Manager Relay, Solaris 11, and VOP.
If your system is using only a service processor-based telemetry source (ILOM, or XSCF on M-Series), STB does not need to be installed.
Note: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.
Download and unzip the ASR software package from My Oracle Support:
Open a terminal window and make sure you are logged in to the ASR Manager system as
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
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.
PATH=$PATH:/opt/asrmanager/bin export PATH
Note:The instructions provided in this document assume that the
PATHvariable has been set.
Note:If you are upgrading your ASR Manager installation, then you do not need to re-register.
Log in to the ASR console:
If you have not set your
PATH environment variable, run:
Note:See Installing ASR Manager Software for instructions for setting the
If you have set your
PATH environment variable, run:
To register the ASR Manager:
Note:If you are registering the system with an ASR Manager Relay, see Enabling HTTP Receiver for ASR Manager Relay, Solaris 11, and VOP.
Enter proxy server details:
If you are using a proxy server to access the internet, see the instructions in Configuring ASR Manager to Use a Proxy Server.
If you are not using a proxy server, enter a hyphen:
Enter the username and password of your My Oracle Support (MOS) account when prompted.
Upon entry of your MOS credentials, ASR will validate the login. Once validated, the registration is complete.
Check the registration status of ASR:
A message is displayed on the screen indicating whether ASR is registered with the transport server.
To be sure that ASR can send information to the transport server:
This command sends a test message (ping) to the transport server.
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.
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.
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.
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:
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
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:
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.
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. 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.
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 disable the HTTP receiver, run:
If you need to use HTTPS for security purposes, you can set up HTTPS/SSL for the ASR Manager HTTP receiver:
The detailed steps for enabling https/SSL for Jetty are documented at
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
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 the above commands..
Restart ASR Manager:
svcadm restart asrm
service asrm restart
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:
Verify the HTTP receiver is enabled:
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.
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
Test the 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.
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:
Note:If you are using a SOCKS proxy, enter the hyphen - for no proxy. When completed with the steps in this procedure, 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 ASR Manager server. NTLM Host: [?] <NTLM host name> NTLM support is not bundled with ASR Manager 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>
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).
Note: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:
Create an SNMP v3 user:
asr> add_snmpv3_user -u userName -e engineId[,engineId2, ...] -pp privacyProtocol
Note: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:
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.
Show the SNMP v3 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 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 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:
You will be prompted to enter both authentication and privacy passwords.
Delete the SNMP v3 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
Appendix B, "Other ASR Manager Administration" describes how to set up the ASR Manager in a high availability environment.