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

E18475-27
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

4 ASR Environment Administration

This chapter contains all procedures and other information required to manage the ASR environment.

Note:

To enter the ASR prompt (asr>) as root, type asr on the command line. See "Install ASR" for instructions for setting the PATH environment variable.

The following topics are discussed.

4.1 Using Auto Update to Upgrade Oracle ASR

Beginning with ASR 4.3, Oracle ASR, by default, checks the ASR software update server for any software updates. If there is a newer version, it will:

  • Automatically download the latest Oracle ASR software bundle.

    See Network Connection Requirements for details on how to test your connection.

  • Install the new version of the software.

    Note:

    If you are running ASR Auto Update from a Linux server and there is no rpm-build package installed, then ASR Auto Update will not work. The following error message is displayed:
    Warning: rpm-build package is not installed on this server. ASR
    Manager Auto Update functionality will not work unless the
    rpm-build package is installed.
    
    Auto Update functionality will be disabled until rpm-build package
    is installed. Please install the rpm-build package and then enable
    Auto Update by running "asr enable_autoupdate".
    

    If an Auto Update fails because of a missing rpm-build package, then this error message is displayed in:

    /var/opt/SUNWsasm/log/sw-asr-autoupdate.log
    
  • Send an e-mail notification that installation is complete or if a problem was encountered.

  • Store the previous version of Oracle ASR to the /var/opt/SUNWsasm/backup directory.

The following topics are presented:

4.1.1 Disabling and Enabling ASR Auto Update

If necessary, you can disable the Auto Update feature:

asr> disable_autoupdate

To enable ASR Auto Update:

asr> enable_autoupdate

4.1.2 Using Auto Update to Manually Upgrade ASR Manager Software

If Auto Update is disabled, you will need to upgrade Oracle ASR manually. You can use the Auto Update feature to download and install future versions of Oracle ASR manually:

asr> autoupdate

Output of the autoupdate command will look like this:

asr> autoupdate

This command will update the ASR Manager software with the latest bundles
available on Oracle content server. Auto Update process will take up to 5 minutes
to complete. During this time, assets attached to ASR Manager will not be
monitored. Do you want to proceed with Auto Update? [y/n]:

Enter y to proceed. The upgrade continues with the following output:

New SWASR package 4.4.0 is available for update.
New Rules definitions bundle 4.4.1 is available for update.
 
Started ASR Manager software Auto Update.
ASR command line console will be locked until Auto Update is completed.

Note:

For Linux, the environment variable SELINUX can be set to Enforcing mode which will not allow the automatic update of RPM packages. If you try the Auto Update feature with this environment variable set to Enforcing, the following warning message will display:
Warning: SELINUX environment variable is set to "enforcing" mode on this server. ASR Manager Auto Update functionality will not work unless the SELINUX enviornment variable is set to "permissive"

4.1.3 Other ASR Auto Update Commands

Auto Update commands include:

  • show_version: Shows OASM, ASR Manager, and rules version information. See ASR Auto Update show_version Examples for sample output of the show_version command.

  • autoupdate: Executes the Auto Update feature to update the ASR Manager and rules bundle software.

  • enable_autoupdate: Enables the ASR Auto Update feature.

  • disable_autoupdate: Disables the ASR Auto Update feature.

4.1.4 ASR Auto Update show_version Examples

You can run the ASR show_version command any time. There are several possible output examples, depending on your configuration:

Auto Update Enabled

When the ASR Auto Update feature is enabled, the output of the show_version command includes information about the installed ASR software versions, Auto Update statistics and status, and a history of Auto Update activity (such as, ASR Manager updates and rules definitions updates).

When you run the show_version command, you should expect to see output like this:

asr> show_version

Software Versions
=====================
OASM version: 1.4.2

ASR Manager version: 4.4

Rules definitions version: 4.4.0

Auto Update Statistics
==========================
Last Run Time: 2013-04-02 14:59:55.15
Last Run Status: ASR Manager software has been updated successfully.
Next Run Time: 2013-04-03 14:59:55.15

Auto Update Status
==========================
Auto Update functionality is enabled.
 
Auto Update History
==========================
ASR Manager Auto Update history
-------------------------------------
ASR Manager Auto Update started at: 2013-04-02 14:31:30.229
ASR Manager Auto Update completed at: 2013-04-02 14:34:12.696
ASR Manager Auto Update result: COMPLETE_SUCCESS
ASR Manager updated from version: 4.3.2
ASR Manager updated to version: 4.4.0
 
Rules definitions Auto Update history
------------------------------------------
Rules definitions Auto Update started at: 2013-04-02 14:58:21.544
Rules definitions Auto Update completed at: 2013-04-02 14:59:54.96
Rules definitions Auto Update result: COMPLETE_SUCCESS
Rules definitions updated from version: 4.4.0
Rules definitions updated to version: 4.4.1

ASR Manager Services
--------------------
ASR Notification trap is enabled.
Remote Request feature is enabled.

Auto Update Disabled

Even though the ASR Auto Update feature is disabled, you can still use the show_version command for information about the installed ASR software, including statistics and status.

When you run the show_version command, you should expect output like this:

asr> show_version

OASM version: 1.4.2

ASR Manager version: 4.4

Rules definitions version: 4.4.0

Auto Update Statistics
==========================
Last Run Time: 2013-04-03 11:21:11.283
Last Run Status: Auto Update functionality is disabled.
Next Run Time: 2013-04-03 11:23:11.283

New Rules definitions bundle 4.4.2.0.0 is available for update.

Auto Update Status
==========================
Auto Update functionality is disabled.
Please refer to the My Oracle Support Doc Id: 1503107.1 for instructions on Auto Update of ASR Manager software.

ASR Manager Services
--------------------
ASR Notification trap is disabled.
Remote Request feature is disabled.

Auto Update Enabled, ASR Manager Unregistered

For ASR to function properly, the ASR Manager must be registered. See Register the ASR Manager for more information. You can still use the show_version command to view limited information about ASR software versions and Auto Update status.

If your ASR Manager is unregistered and you run the show_version command, the output should look like this:

asr> show_version

Software Versions
=================
OASM version: 1.4.2

ASR Manager version: 4.4

Rules definitions version: 4.4.0
 
Oracle ASR Infrastructure is not available.
 
Auto Update Status
==================
Auto Update functionality is enabled.

New Software Available

If a new software download is available (including any new rules definitions), you can use the show_version command to review the versions. Output should look like this:

asr> show_version

Software Versions
=================
OASM version: 1.4.2

ASR Manager version: 4.4

Rules definitions version: 4.4.0

New SWASR package 4.4.0.0.0 is available for update.
New Rules definitions bundle 4.4.2.0.0 is available for update.

Auto Update Status
==================
Auto Update functionality is enabled.

4.2 Manually Upgrading ASR Manager Software

Follow the steps below to upgrade the ASR Manager software manually:

  1. Make sure that OASM is running. To get the status of the OASM:

    • For Solaris, run: svcs sasm

    • For Linux, run: service sasm status

    If OASM is not running, then start it with these commands:

    • For Solaris, run:

      svcadm enable sasm (starts OASM)
      
    • For Linux, run:

      service sasm start
      
  2. Uninstall ASR. Refer to Uninstall ASR for details.

  3. Obtain the new ASR package. Refer to Software Requirements for download instructions. To install OASM, refer to Install OASM.

  4. Install the new ASR package. Refer to Install ASR. Be sure to register and activate the ASR Manager, as explained in the referenced instructions.

4.3 ASR Manager Registrations

Beginning with ASR 4.8, the list_registration command provides a list of all registered ASR Manager hosts. Use this command to verify that your installed ASR Manager is registered with Oracle ASR Infrastructure or ASR Manager relay. To generate the information, run:

asr> list_registration

The following examples show a sample output of the list_registration command:

Sample 1

This ASR Manager is registered with Oracle ASR Infrastructure.
The following ASR Manager(s) are registered with this ASR Manager Relay:
ASR Manager Host : 10.12.12.11
ASR Manager Host : 10.12.12.13

Sample 2

This ASR Manager is registered with Oracle ASR Infrastructure.

Sample 3

This ASR Manager is registered with ASR Manager relay http://host123.test.com:8928/asr

4.4 ASR Asset Management Overview

This section provides a variety of commands and procedures for managing ASR Assets. The following diagram shows the status transition of ASR Asset:

ASR Asset Transition Diagram

4.5 ASR E-mails

This section describes the types of e-mails generated by ASR. See Appendix A, "ASR E-mail Examples." E-mail generated by ASR is sent to:

  • The e-mail address of the My Oracle Support account associated with the ASR installation.

  • The contact assigned to the asset in My Oracle Support.

  • A distribution list assigned to the asset in My Oracle Support (optional)

Table 4-1 shows the various recipients of the typical ASR e-mail, depending on the reason for sending it, where:

  • Registration user: The e-mail address used to register the asset. For the ASR Manager, this is the e-mail address entered for the asr register command.

  • My Oracle Support Contact: The My Oracle Support (MOS) user assigned to the asset as the contact.

  • MOS Dist List: a comma-separated distribution list of e-mail addresses in My Oracle Support.

  • Support Identifier Administrators: The My Oracle Support users who are administrators of the Support Identifier associated with the asset.

Table 4-1 ASR E-mail Types and Recipients

Notification Type ASR E-mail Recipient
Registration User Contact MOS Dist List Support Identifier Admins Other

Auto Update

Yes

Yes

   

Auto Update user SSO (typically the same as activation SSO)

Heartbeat failure

Yes

Yes

Yes

 

Registration SSO (if applicable)

ASR rules out of date

Yes

       

ASR Manager out of date

Yes

       

SR create delayed

Yes

Yes

Yes

   

SR create

Yes

Yes

Yes

   

SR create (partner)

No

Yes

Yes

No

 

SR failed

Yes

Yes

Yes

Yes

 

SR test (non-Pillar)

Yes

Yes

Yes

   

SR test (Pillar)

Yes

Yes

Yes

Yes

 

SR update

Yes

Yes

Yes

   

Status Pending MOS

Yes

   

Yes

 

Status Change

Yes

       

Activation failed

Yes

       

The types of e-mail generated by ASR include:

  • ASR Activation E-mail and Status of ASR Assets

    An e-mail indicating success or failure of ASR activation is sent. Instructions for any user action is included as needed. ASR Asset status is available in My Oracle Support.

  • ASR Service Request E-mail

    Service Request e-mails are generated whenever a Service Request is created at Oracle that results from a hardware fault detection on any of your ASR-enabled systems. Failure e-mails indicate what issues may have prevented a Service Request from being created upon receipt of a hardware fault from ASR.

    All Service Request e-mails are sent to the Primary and Preferred Technical Contact associated with the system reporting a potential fault. For more on how this contact is established or changed, refer to View Status from My Oracle Support.

    Note:

    Any e-mail sent from Blade ASR Assets have a different e-mail format.
  • Heartbeat Failure Notification

    If the ASR Heartbeat detects a communications error to Oracle, an e-mail is sent.

  • Fault Rules Out of Date E-mail

    This e-mail is sent if ASR detects that its fault rules are out of date.

4.5.1 Create Test Alert

You can test the end-to-end functionality of ASR by simulating a hardware fault. The end result is an e-mail sent to the e-mail address of the My Oracle Support account associated with the ASR installation.

Note:

A test alert should be run only after the asset has been enabled in My Oracle Support. See "Approve ASR Assets in My Oracle Support" for more information.

4.5.1.1 Create Test Alert - ILOM

Note:

Only valid for ILOM 3.0 or later.

To generate a test alert from ILOM:

  • From the ILOM GUI: In the Alert Settings page, select the alert you want to test and then click the Send Test Alert button. ILOM generates a test event for the selected alert. If configured properly, you will receive a test Service Request e-mail.

  • From the ILOM CLI: Type one of the following command paths to set the working directory:

    • For a rack-mounted server SP, type: cd /SP/alertmgmt/rules

    • For a Blade server SP, type: cd /CH/BLn/SP/alertmgmt/rules

    • For a chassis CMM, type: cd /CMM/alertmgmt/CMM/rules

    Type the following command to generate a test alert:

    ->set testalert=true

4.5.1.2 Create Test Alert - Solaris 11

To send a test e-mail on an ASR Asset for Solaris 11, run the following command:

asradm send test email.address@mycompany.com

Note:

The ASR Asset Menu (asrassetmenu.sh) is not available on ASR Assets running Solaris 11.

4.5.1.3 Create Test Alert - Solaris 10

To send a test e-mail on an ASR Asset for Solaris 10:

  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 "Install ASR Asset Bundle" 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.

  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 e-mail contact of the My Oracle Support account associated with the ASR installation.

Note:

If this test fails on Solaris 10, be sure that the /usr/sfw/bin/snmptrap exists and Solaris netsnmp library is installed on the asset.

4.6 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:

4.6.1 Add/Remove Telemetry Traps from Solaris 10 FMA Systems

Follow the procedure below to add or remove a trap destination for systems using Solaris 10 FMA telemetry.

  1. To add a Solaris FMA telemetry trap, go to "Enable FMA Telemetry for Solaris 10 ASR Assets".

  2. To remove a trap destination, make sure you are logged in as root on the system whose telemetry trap you wish to remove. This could be either an ASR Manager or an ASR Asset system. Keep in mind that this process stops telemetry from being sent to the ASR Manager. It does not remove the telemetry software itself nor disables its operation (for example, FMA).

  3. Go to the directory where you previously untarred the ASR Asset Bundle file, and then go to the specific ASR Asset Bundle directory, if needed. For example:

    • If on an ASR Asset:

      cd /file_copy_location/asrassetbundle

    • If on the ASR Manager system:

      cd /opt/SUNWswasr/asrassetbundle

    Note:

    Refer to "Install ASR Asset Bundle" if you have issues locating the asrassetbundle directory and/or asrassetmenu.sh script (below).
  4. Launch the ASR Asset Menu:

    ./asrassetmenu.sh
    
    Welcome to the ASR asset menu
    ----------------------------------------------
    1) Check system for ASR qualifications
    2) Add a trap-destination to SunMC agent
    3) Add a trap-destination to FMA agent
    4) Remove a trap-destination from SunMC agent
    5) Remove a trap-destination from FMA agent
    6) List SunMC agent trap-destinations
    7) List FMA agent trap-destinations
    8) Test event to verify ASR connectivity
    9) Exit
    
  5. Select 5 to remove the FMA trap destination.

  6. When prompted, ”. . . enter the number of the trap-destination to remove,” enter the list number of the IP address of the ASR Manager.

    Note:

    If you are removing an FMA trap, enter the listed IP address with the port number (for example, 192.20.77.192:162).
  7. The trap is then removed from the system and all telemetry sent from Solaris FMA to the ASR Manager is stopped.

4.6.2 Add/Remove Telemetry from Solaris 11 FMA Systems

Follow the procedure below to add or remove registration for systems using Solaris 11 FMA telemetry.

  1. To add Solaris FMA telemetry, see "Enable FMA Telemetry for Solaris 11 ASR Assets".

  2. To delete the ASR Manager registration, run:

    asradm unregister
    

4.6.3 Add/Remove Telemetry Traps from ILOM Systems

To add or remove an ILOM trap, refer to "Enable ILOM Telemetry". This referenced procedure can be used to add or remove traps. If removing a trap, use the following parameters:

  • If using the ILOM GUI interface, either remove the entire alert rule destination or set the Level parameter to Disable.

  • If using the command line interface, set the Level parameter to Disable. Also, be sure to specify the correct alert rule (1 to 15) to disable.

4.6.4 Add/Remove Telemetry Traps from M-Series Systems (XSCF)

To add or remove telemetry traps on systems that have XSCF telemetry (Sun M-Series), refer to "Enable M-Series XSCF Telemetry". This referenced procedure can be used to add or remove traps.

4.7 ASR Backup and Restore

ASR Backup

  1. Verify all information is in the database that is activated:

    asr> list_asset
    
  2. Stop OASM so that data does not change in middle of backup:

    • For Solaris, run: svcadm disable sasm

    • For Linux, run: service sasm stop

  3. Back up the database directory. Run:

    tar -cvf db.tar.bz /var/opt/SUNWsasm/db

  4. Create a backup of the ASR configuration. Run:

    tar -cvf configuration.tar.bz /var/opt/SUNWsasm/configuration

  5. Copy both db.tar.bz and configuration.tar.bz files to their proper backup destination.

  6. Restart OASM. Run:

    • For Solaris, run: svcadm enable sasm

    • For Linux, run: service sasm start

ASR Restore

  1. Install the ASR plug-in and OASM:

    • For Solaris, run:

      pkgadd -d SUNWsasm-version-timestamp.pkg
      pkgadd -d SUNWswasr-version-timestamp.pkg
      
    • For Linux, run:

      rmp -i SUNWsasm-version-timestamp.rpm
      rpm -i SUNWswasr-version-timestamp.rpm
      

    Note:

    Download and install the latest packages to upgrade to the latest version of the ASR Manager. See Software Requirements for more information.
  2. Stop OASM to restore files:

    • For Solaris, run: svcadm disable sasm

    • For Linux, run: service sasm stop

  3. Restore the files from backup:

    1. Remove files /var/opt/SUNWsasm/configuration and /var/opt/SUNWsasm/db

    2. Copy backup data to /var/opt/SUNWsasm/

    3. Extract the tar files (both Solaris and Linux):

      tar -xvf configuration.tar.bz
      tar -xvf db.tar.bz
      
  4. Verify the files have been correctly extracted. Run:

    ls /var/opt/SUNWsasm/

  5. Restart OASM. Run:

    • For Solaris, run: svcadm enable sasm

    • For Linux, run: service sasm start

  6. Register the backup configuration:

    asr> register
    

    Note:

    If you are running the latest version of ASR and if host name of the restored ASR Manager and My Oracle Support account) login have not changed, then you can stop here. Steps 7 and 8 are not required.
  7. Remove old entries from the My Oracle Support backend to associate correctly:

    asr> send_deactivations -a
    
  8. Add new entries to the My Oracle Support backend:

    asr> send_activations -a
    
  9. List ASR Assets. Run:

    asr> list_asset
    

4.8 Unregister ASR

When you installed ASR, you registered it with the transport server (transport.oracle.com) using your My Oracle Support username. 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 My Oracle Support account is no longer valid, as in a case when the e-mail contact is no longer associated with the company. The e-mail address associated with the My Oracle Support 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 account information.

  • If the server and ASR handshake becomes corrupted.

To unregister ASR:

  1. From the ASR Manager system, run:

    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.

4.9 Starting and Stopping ASR and OASM

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 OASM config.ini file:

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

Note:

On Solaris, OASM startup/restart is done via SMF service.

4.9.1 Stop ASR and OASM

Follow the procedure below to stop ASR and OASM.

Note:

Stopping OASM is optional, depending upon what your purpose is. If changes are made to the OASM config.ini file, for example, you must stop and restart OASM. In conformance with best practices, OASM should be stopped whenever ASR is stopped, and started whenever ASR is started.
  1. Open a terminal window and log in as root on the ASR Manager system.

  2. Run the following commands:

    • For Solaris:

      asr> stop (stops ASR)
      svcadm disable sasm (stops OASM)
      
    • For Linux:

      asr> stop (stops ASR)
      service sasm stop
      
  3. Once ASR is stopped, you can perform the desired maintenance tasks. Once complete, continue to the next section to restart ASR.

4.9.2 Start ASR and OASM

Follow the procedure below to restart ASR and OASM:

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

  2. Run the following commands:

    • For Solaris:

      svcadm enable sasm (starts OASM)
      asr> start (starts ASR)
      
    • For Linux:

      service sasm start (starts OASM)
      asr> start (starts ASR)
      
  3. Be sure that ASR can send information to the transport.oracle.com servers by running the following command:

    asr> test_connection
    

4.10 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 the ASR Manager from sending fault telemetry to Oracle for that asset.

4.10.1 Disable ASR Assets

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

  2. Run any one of the following commands depending on your circumstance. Use the IP address or the hostname of the asset you wish to disable. If you disable the ASR Manager itself, only its telemetry will be stopped. All enabled ASR Asset(s) that send telemetry to this ASR Manager will continue, and the ASR Manager will continue to forward fault telemetry to Oracle's backend systems.

    • asr> disable_asset -i IP_address

    • asr> disable_asset -h hostname

    • asr> disable_asset -s subnet(used to disable a group of assets within the subnet)

4.10.2 Enable ASR Assets

After you have disabled an ASR asset, you can re-enable it when you are ready for ASR to begin transmitting telemetry data.

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

  2. Run any one of the following commands depending on your circumstance. Use the IP address or the hostname of the asset you wish to enable. Once enabled, the asset will send hardware telemetry data to the ASR Manager and faults will be sent to Oracle's backend systems.

    • asr> enable_asset -i IP_address

    • asr> enable_asset -h hostname

    • asr> enable_asset -s subnet(used to enable a group of assets within the subnet)

  3. Once complete, a successfully enabled message is displayed.

  4. To confirm the asset is enabled, you can generate a test event using either one of the following command options:

    • asr> send_test -i IP_address

    • asr> send_test -h hostname

    Note:

    The send_test command validates the ASR Manager connection to Oracle and the ASR activation status of the asset.

    It does not validate the network connection from the asset to the ASR Manager.

  5. The status of the test event is sent to the e-mail address of the My Oracle Support account associated with the ASR installation.

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

Note:

If you need to unregister your ASR Asset for Solaris 11, run:
asradm unregister

This command unregisters and disables your ASR Asset.

The following topics are described:

4.11.1 Deactivate/Activate ASR Assets from My Oracle Support

  1. In the "Assets" dashboard, click on the serial number of the asset you wish to deactivate/activate. The last column (ASR Status) will show the status of the asset (Active, Inactive, or Pending).

    Note:

    You must have either CUA or Asset Admin roles to update/approve ASR activation requests.
    Surrounding text describes assets.gif.
  2. In the Asset's Details pane, click the "Deactive" button to deactivate the asset. If the asset is already deactivated, click the "Activate" button to activate it.

  3. If necessary, you can update details about the asset (for example, change the Contact Name).

4.11.2 Deactivate/Activate ASR Assets from the ASR Manager

Follow these instructions to deactivate/activate an ASR Asset from the ASR Manager:

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

  2. Run any one of the following commands depending on your circumstance. Use the IP address or the hostname of the asset you wish to deactivate.

    • asr> deactivate_asset -i IP_address

    • asr> deactivate_asset -h hostname

    • asr> deactivate_asset -s subnet(used to enable a group of assets within the subnet)

    Note:

    When you deactivate an ASR Asset, you cannot re-enable it. If you want to enable it again for ASR, you must re-activate it. Refer to "Activate ASR Assets".
  3. Once an asset is deactivated, you should also stop the hardware telemetry from being sent from the asset (even though the telemetry data is ignored by ASR once sent).

4.11.3 Reactivate/Deactivate All ASR Assets Associated with an ASR Manager

If you have multiple ASR Assets reporting to an ASR Manager, you can activate them all with one command:

asr> send_activations -a

Note:

Activations are resent for all the previously activated assets only.

Likewise, if you need to deactivate all of the ASR Assets associated with an ASR Manager, you can deactivate them all with one command:

asr> send_deactivations -a

4.12 Uninstall ASR

The following procedure explains how to remove ASR completely or partially for the purpose of an upgrade.

Remove ASR as Part of an Upgrade

  1. Remove the ASR package from the ASR Manager system:

    • For Solaris: pkgrm SUNWswasr

      Note:

      To remove the ASR package from a Solaris machine in "silent" mode, run:
      /opt/SUNWswasr/pkg/uninstall_silent_mode.sh
      
    • For Linux: rpm -e SUNWswasr

    As part of the uninstall process, you will be asked the following question:

    Will you be upgrading to a newer version of ASR Manager [y,n,q]:
    

    Enter y to continue the process.

  2. Remove the OASM package from the ASR Manager system. Removing this package is optional and is often done to reduce system overhead. If you have other applications running under OASM, do not remove it. Refer to Oracle Automated Service Manager (OASM) Requirements - ASR Manager Only for more information on OASM.

    • For Solaris: pkgrm SUNWsasm

    • For Linux with OASM 1.5 or later: rpm -e SUNWsasm

    • For Linux with OASM 1.4.2 or earlier: rpm -e --noscripts SUNWsasm

      Note:

      There is a known issue when uninstalling OASM 1.4.2 (or earlier) on Linux using the rpm -e SUNWsasm command. Using this command to remove OASM 1.4.2 (or earlier) completely removes the crontab entries for OASM.

      This uninstallation issue has been resolved with OASM 1.5. To prevent losing any crontab entries, you can uninstall OASM 1.4.2 (or earlier) with the following command:

      rpm -e --noscripts SUNWsasm
      

Remove ASR Completely

  1. For all ASR Asset systems, remove telemetry traps that send hardware telemetry to the ASR Manager. Follow these steps:

  2. Deactivate all ASR Asset(s). Refer to Deactivate/Activate ASR Assets.

  3. Unregister ASR. Refer to Unregister ASR.

    Important:

    If you are using other OASM plug-ins (for example SFT), the OASM transport service used by these plug-ins will be unregistered as part of this process. Consult your plug-in documentation to re-register the OASM transport service, if needed.
  4. Remove the ASR package from the ASR Manager system:

    • For Solaris: pkgrm SUNWswasr

    • For Linux with OASM 1.5 or later: rpm -e SUNWsasm

    • For Linux with OASM 1.4.2 or earlier: rpm -e --noscripts SUNWsasm

      Note:

      There is a known issue when uninstalling OASM 1.4.2 (or earlier) on Linux using the rpm -e SUNWsasm command. Using this command to remove OASM 1.4.2 (or earlier) completely removes the crontab entries for OASM.

      This uninstallation issue has been resolved with OASM 1.5. To prevent losing any crontab entries, you can uninstall OASM 1.4.2 (or earlier) with the following command:

      rpm -e --noscripts SUNWsasm
      

    As part of the uninstall process, you will be asked the following questions:

    1. The first question is whether or not you are upgrading the ASR Manager:

      Will you be upgrading to a newer version of ASR Manager [y,n,q]:
      

      Enter n to continue the process.

    2. The next question is to initiates the removal of ASR Manager and the deactivation of ASR Assets:

      Do you want to uninstall ASR Manager completely and deactivate all assets [y,n,q]:
      

      Enter y to continue the process. Because the removal is for a complete uninstall, you will be asked to confirm the removal:

      You are going to deactivate all assets. Please confirm [y,n,q]
      

      Enter y to continue the process.

  5. Remove the OASM package from the ASR Manager system. Removing this package is optional and is often done to reduce system overhead. If you have other applications running under OASM, do not remove it. Refer to Oracle Automated Service Manager (OASM) Requirements - ASR Manager Only for more information on OASM.

    • For Solaris: pkgrm SUNWsasm

    • For Linux: rpm -e SUNWsasm

  6. If you never intend to use ASR and OASM again, run the following command to remove leftover artifacts (OASM log files, ASR asset database, configuration files, etc.):

    Warning:

    This command will remove all asset activation, configuration, and ASR log file data. Only remove these files if you want to permanently remove ASR from the system or node.

    rm -r /var/opt/SUNWsasm

  7. After completing the steps above, the uninstall of ASR is complete.

4.13 ASR Network Parameters Management

This section provides the instructions for networking-related tasks for ASR operations.

4.13.1 ASR Port Usage

The following table explains the network ports used by ASR:

Source Destination Protocol Port Description
ASR Asset ASR Manager http/https user defined For sending Solaris 11 ASR telemetry to the ASR Manager.
ASR Manager ASR Backend (Oracle)

transport.oracle.com

https 443 For sending telemetry messages to the transport.oracle.com ASR backend system at Oracle.
ASR Manager ASR Asset http 6481 Service Tags listener for Asset activation
ASR Asset ASR Manager snmp

udp

162 For sending telemetry messages to the ASR Manager.
ASR Manager ASR Asset snmp (get)

udp

161 FMA enrichment for getting additional diagnostics information (Solaris 10 only).

4.13.2 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 OASM:

    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.

4.13.2.1 Known Issue: Change ASR SNMP Port (ASR 4.1 Only)

A known issue with the SNMP port update in the config.ini file from the default 162 port is not working in ASR 4.1. The following workaround is required only when you need to change the ASR SNMP port from the default port (162) in ASR 4.1:

  1. Set the SNMP port:

    asr>  set_property snmp.receiver.port <port_number>
    

    For example:

    asr>  set_property snmp.receiver.port 1162
    

    Edit the /var/opt/SUNWsasm/configuration/config.ini file and update com.sun.svc.container.snmp.port to the desired port number. This step is required to prevent any issues during future ASR Manager upgrades.

  2. Verify that the SNMP port is set correctly:

    asr>  get_property snmp.receiver.port
    
  3. Restart OASM:

    • For Solaris: svcadm restart sasm

    • For Linux: service sasm restart

4.13.3 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 Linux, run: service sasm restart

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

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

4.13.4 Configure OASM Network Settings

The following command can be used to confirm that the network parameters used by OASM 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.oracle.com

4.13.5 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:

    • Using telnet:

      telnet transport.oracle.com 443
      
    • Using a web browser:

      https://transport.oracle.com/v1/
      

      The web page should indicate that the Data Transport Service is operating.

    • Using the wget utility:

      • For Solaris:

         /usr/sfw/bin/wget https://transport.oracle.com/v1/
        
      • For Linux:

        wget https://transport.oracle.com/v1/
        

      Note:

      "Unable to locally verify the issuer's authority" is an expected error.
  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:

    • Determine if your network's DNS configuration is able to resolve transport.oracle.com. You may need to configure your firewall to enable outbound Internet access to transport.oracle.com.

      If DNS is not available on the ASR Manager host, you may need to manually add an entry for transport.oracle.com and its IP address to the /etc/hosts file. Use any DNS lookup service on the Internet to determine the IP address for transport.oracle.com.

    • You may need to contact your network administrator for assistance. Refer to "Network Connection 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 OASM. This is done by registering ASR, as discussed in the following procedure.

4.14 ASR Integration with Enterprise Monitoring Systems

Other environments are set up to use different enterprise monitoring systems (e.g., IBM Tivoli, HP OpenView, etc.). Beginning with ASR 3.0, integration with My Oracle Support allows sending ASR service-request information to these systems. Once installed and properly configured, ASR provides the following integration features with enterprise monitoring systems:

  • Ability to configure SNMP trap destination from OASM ASR to enterprise monitoring systems.

  • Send case creation and test alert messages to enterprise monitoring systems.

  • New ASR MIB that provides the data model of ASR case creation notification.

Examples of enterprise-monitoring systems include:

  • IBM Tivoli

  • HP OpenView

  • BMC Patrol

  • Unicenter

  • xVM Ops Center

  • Any monitoring tool that can receive an SNMP v2c trap

During installation of the ASR software package, the SNMP trap destination can be configured from the OASM host to monitoring systems. Once the ASR-capable assets are activated, ASR is designed to generate a service request after specific faults are detected. Once the service request is opened, the Oracle Support coverage and response times are delivered in accordance with your Oracle Premier Support or Warranty Contract.

Note:

Because of ASR 3.0 integration with My Oracle Support, there are changes in the Service Request format. The service request number format in the notification trap is not correct if you are using any version older than ASR 3.0 manager. See "Using Auto Update to Manually Upgrade ASR Manager Software" for instructions on upgrading to the latest version of ASR.

The OASM ASR Plug-in polls the ASR backend whenever a fault event or test alert occurred and updates its local database with service request or test alert information. Once the service request/test alert information is available to the OASM ASR Plugin, it sends an SNMP v2c trap to the enterprise monitoring systems and include the following service request/test alert data defined in the ASR MIB:

  • Hostname
  • IP address

  • Serial number

  • Platform type

  • Fault information (one line description)

  • Fault information knowledge link

  • Service Request number

  • Link to Service Request number
  • Service Request status information (for "unable to create SR" problems)

  • Severity of Service Request

  • SR creation time

  • Fault detection time

  • Customer Contact information


4.14.1 Managing SNMP Trap Destinations for Service Request Notifications

Follow the procedure below to configure SNMP trap destinations for ASR Service Request notifications. You can create up to 10 notification trap destinations.

  1. Set ASR notification trap destination:

    asr> set_notification_trap [-i ipAddress -p port -c community] [-h hostname -p port -c community]
    

    For example:

    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 -i 127.0.0.1

4.14.2 MIB Location and Data Elements

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

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

Data Element Description
sunAsrSrHostname Hostname of the system for which the Service Request was created.
sunAsrSrIpAddress IP address of the system for which the Service Request was created.
sunAsrSrSerialNumber Product serial number of the system for which the Service Request was created. For chassis and blade systems, chassis serial number is used.
sunAsrSrPlatformType Product Type of the system for which the Service Request was created.
sunAsrSrCreationDateTime Date and time when the Service Request was created.
sunAsrSrFaultDetectionDateTime Date and time when the fault was generated.
sunAsrSrCreationStatus Status indicating the processing of Service Request creation.
sunAsrSrAdditionalInfo Additional information associated with the fault can be added as name/value pairs. For example:

<additional-information name=chassis_host_name>chassisHostName</additional-information>

<additional-information name=chassis_serial_number>chassisSerial</additional-information>

sunAsrSrFaultSummary Brief summary of the fault for which the Service Request was created.
sunAsrSrKnowledgeLink Link to a knowledge article for the fault that was reported.
sunAsrSrNumber Service request number
sunAsrSrLink URL for accessing the Service Request information.
sunAsrSrSeverity Severity of the Service Request opened for the reported fault.
sunAsrSrName
  • Customer contact information associated with the device reporting the fault.
  • Name of Customer Contact associated with the Serial Number of the Device for which the Service Request was created.

sunAsrSrTelephone Telephone number of Customer Contact associated with the Serial Number of the Device for which the Service Request was created.
sunAsrSrEmail E-mail address of Customer Contact associated with the Serial Number of the Device for which the Service Request was created.