ASR Environment Administration

View Status of ASR Asset(s)

The status of any ASR Asset can be obtained by running any one of the following command options from the ASR Manager system:

• asr list_asset - lists all assets associated with this ASR Manager

• asr list_asset -i IP_Address_of_ASR Asset

• asr list_asset -h Hostname_of_ASR Asset

• asr list_asset -s Subnet_IP_Address_of_ASR Asset(s)

The results will be similar to the following example:

Review Status of ASR Assets

To view the status of all ASR Assets, login to My Oracle Support (https://support.oracle.com). In the My Oracle Support Dashboard, click the “More...” tab. Then select “Settings” from the menu.

In the “Settings” pane on the left of the window, select “Assets” (located under the Administrative submenu). A complete list of all ASR Assets is displayed:

Create Test Alert

The following command allows you to test the end-to-end functionality of ASR by simulating a hardware fault. The end result is an email sent to the email address of the Sun Online Account associated with the ASR installation.

1. Execute the asrassetbundle shell script:

   • If on an ASR Asset:

     cd /untar_location_of_assetbundle/asrassetbundle

     ./asrassetmenu.sh

     Note:

     If you have issues finding the asrassetbundle directory, go to "Obtain the ASR Asset Bundle for non-ILOM Telemetry Sources" for more information.

   • If on the ASR Manager system:

     cd /opt/SUNWswasr/asrassetbundle ./asrassetmenu.sh

2. From the ASR Asset Menu, type 8.

3. Whether you are on an ASR Asset or the ASR Manager, enter the IP address of the ASR Manager.

   Note:

   Test Alerts can only be generated from a host. Test Alerts are not supported on service processors.

4. Enter the SNMP port used to send hardware telemetry to the ASR Manager. The default port is 162.

5. When the test alert is sent, check the email account of the Sun Online Account associated with the ASR installation.

Enable/Disable ASR Assets

Follow the procedures below to enable or disable ASR Asset(s). Regardless of which asset you wish to enable or disable, this action is always performed on the ASR Manager system. The most common reasons to disable ASR Asset(s) are for system maintenance or if an asset is “noisy” in terms of sending an excess of telemetry data. Disabling an ASR Asset stops it from sending hardware telemetry.

Deactivate/Activate ASR Assets

Deactivating an ASR Asset is done when you are replacing the asset or removing it entirely from the ASR system. When you deactivate an ASR Asset, ASR can no longer transmit telemetry data from this asset to Oracle.

Add/Remove Telemetry Traps from ASR Asset(s)

The procedures in this section explain how to enable or disable telemetry trap destinations on ASR Asset(s). A trap destination is where the telemetry data is sent. During ASR installation, each asset is configured by setting trap destinations from the asset system. In all cases, the trap destination specified is the ASR Manager system, which centrally collects the telemetry data sent from ASR Asset(s). Even if the ASR Manager itself is configured to send telemetry data, its trap destination must be this same ASR Manager.

Reasons for enabling traps include:

• Traps were not enabled during installation.

• Traps need to be enabled as part of troubleshooting tasks.

Reasons for disabling traps include:

• IP address of ASR Manager changed. If this situation occurs, you need to disable the traps, then re-enable the traps with the new IP information.

• Stopping the use of ASR and/or you want to minimize telemetry traffic.

Before continuing, be mindful of the following:

• You should know what telemetry sources exist on any particular ASR system. Refer to "Confirm Existing Telemetry Sources".

• An active ASR Manager should already be fully installed. Refer to "Install the ASR Manager" on page 3-1.

• Ideally, but not required, at least one ASR Asset should already be fully installed. Refer to "Configure and Manage ASR Assets" on page 4-1.

Unregister ASR

When you installed ASR, you registered it with the transport server (transport.sun.com) using your Sun Online Account. The registration is performed on the ASR Manager system, as is an unregister if required. Reasons for unregistering ASR can include the following:

• If your current Sun Online Account (SOA) is no longer valid, as in a case when the email contact is no longer associated with the company. The email address associated with the SOA login is used by ASR to send a variety of ASR notifications, such as status reports. In this case, ASR should be unregistered and then re-registered with the new Sun Online account information.

• If the server and ASR handshake becomes corrupted.

To unregister ASR:

1. From the ASR Manager system, run:

   /opt/SUNWswasr/bin/asr unregister

2. Once unregistered, ASR cannot send hardware fault telemetry to Oracle's backend systems.

To register ASR, refer to "Register the ASR Manager" for instructions.

Starting and Stopping ASR and SASM

This section explains how to stop and start your complete ASR environment. There are several reasons why you may want to do this, as listed below:

• Telemetry rules or other image upgrade to ASR.

• If you change network and port settings used by ASR. These changes are typically made in the SASM config.ini file:

  /var/opt/SUNWsasm/configuration/config.ini

ASR Port Usage

The following table explains the network ports used by ASR:

Changing the Default SNMP Port for ASR

You can change the default SNMP port on the ASR Manager by editing the /var/opt/SUNWsasm/configuration/config.ini file as follows:

1. Change com.sun.svc.container.snmp.port=162 to listen on whatever port is appropriate. 162 is the default.

2. Restart SASM:

   svcadm restart sasm

3. Verify the change:

   /opt/SUNWsasm/bin/sasm getprop | grep com.sun.svc.container.snmp.port
   

This command will return the new port value that you entered.

Configure ASR to Send HTTPS Traffic Through a Proxy Server

This procedure should be used to enable network communications in cases where you have a SOCKS proxy server mediating network traffic between the ASR Manager and the internet. For other proxy server types, you need to re-register ASR to set-up the proxy server information, as discussed in "Register the ASR Manager".

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

2. Using an editor of your choice (such as vi), edit the following file by changing the SOCKS proxy information as needed:

   /var/opt/SUNWsasm/configuration/config.ini

3. The following entries must be made within the file. Contact a Network Administrator if needed.

   socksProxyHost=
   socksProxyPort=
   java.net.socks.username=
   java.net.socks.password=
   

4. Restart ASR using the following command:

   • For Solaris: svcadm restart sasm

   • For OEL, run:

     /opt/SUNWsasm/bin/sasm stop-instance
     /opt/SUNWsasm/bin/sasm start-instance
     

5. To verify the changes, run the following command:

   cat /var/opt/SUNWsasm/configuration/config.ini | grep socks
   

Configure SASM Network Settings

The following command can be used to confirm that the network parameters used by SASM to connect to Oracle's ASR backend systems are properly set:

grep transport.root
/var/opt/SUNWsasm/configuration/config.ini

The ASR transport hostname is displayed and will be similar to the results shown below:

com.sun.svc.container.transport.root=
https://transport.sun.com

Test Connectivity from the ASR Manager to Oracle

The following procedure can be used to confirm proper communication between the ASR Manager and Oracle's ASR backend systems.

1. Complete one of the following steps from the ASR Manager to verify connectivity to Oracle's ASR backend systems:

   • telnet transport.sun.com 443

   • If you have a web browser, go to https://transport.sun.com. The web page should indicate that the Data Transport Service is operating.

   • If a web browser is unavailable, or you are in Europe, the Middle East, or Africa regions, run one the following commands from a terminal window:

     wget https://transport.sun.comor wget https://transport.sun.co.uk (for Europe, Middle East, or Africa Regions)

2. If the results of the above commands do not indicate the Data Transport Service is operating, you must resolve your network connection issue. Listed below are possible resolutions:

   • The issue could be a DNS problem, or you might need to add transport.sun.com to the /etc/hosts file.

   • You may need to contact your network administrator for assistance. Refer to "Oracle Auto Service Request Configuration Requirements" for the specific ASR network requirements.

   • If you use a proxy server, the issue could be that the proxy information has not yet been configured to ASR and SASM. This is done by registering ASR, as discussed in the following procedure.

Configuring Trap Files

Follow the procedure below to configure trap files for ASR:

1. Set ASR notification trap destination:

   /opt/SUNWswasr/bin/asr set_notification_trap -i <ip_address>-p <portNumber> -c <community string>

   For example:

   /opt/SUNWswasr/bin/asr set_notification_trap -i 127.0.0.1 -p 162 -c public
   

   Note:

   Port “162” in the example is the destination port on your monitoring system. The notification trap will be sent only when a new service request (SR) is created successfully, and also when the test SR (test SNMP alert from the ASR asset menu) is successful

2. Show ASR notification trap destination:

   asr show_notification_trap

3. Delete ASR notification trap destination:

   asr delete_notification_trap

MIB Location and Data Elements

The SUN-ASR-NOTIFICATION-MIB file is located at:

/var/opt/SUNWsasm/configuration/SUN-ASR-NOTIFICATION-MIB.mib