Oracle® Auto Service Request

Exadata Database Machine Quick Installation Guide

Release 5.3

E23333-15

August 2015

This document describes how to install and configure Oracle Auto Service Request for the Exadata Database Machine.

The following topics are described:

1 About Oracle ASR

Oracle Auto Service Request (ASR) is a secure, scalable, customer-installable software feature of warranty and Oracle Support Services that provides auto-case generation when common hardware component faults occur. ASR is designed to enable faster problem resolution by eliminating the need to initiate contact with Oracle Support Services for common hardware component failures, reducing both the number of phone calls needed and overall phone time required.

ASR also simplifies support operations by using electronic diagnostic data. Easily installed and deployed, ASR is completely controlled by you, the customer, to ensure security.

ASR is applicable only for component faults. Not all component failures are covered, though the most common components (such as disk, fan, and power supplies) are covered. For example, Exadata systems do not support InfiniBand events; however, there are very specific images that must be used as well as a specific InfiniBand switch firmware. They cannot be upgraded independently.

Note:

ASR is not a system management or monitoring tool; it is designed to automatically open Oracle Service Requests when specific faults are detected on Oracle products that are qualified for ASR. Best practices include implementing a system management and monitoring solution along with ASR, such as Oracle Enterprise Manager Ops Center.

Caution:

The commands included in this document are provided for your convenience. However, the copy and paste functionality may not work as expected. To ensure the command text you copy is the same as the text you paste, make sure to have your console session set to receive data as UTF-8.

2 Recommended Configuration

The recommended configuration is to install the ASR Manager, which receives fault telemetry information from the servers in Oracle Exadata Database Machine, on an external standalone server. This server must run Solaris or Linux as the operating system.

Note:

While not recommended, you may install the ASR Manager on one of the database servers in the Oracle Exadata Database Machine.

3 Prerequisites

Before installing ASR, you must ensure that the following conditions are met:

  • Make sure you have access to My Oracle Support (https://support.oracle.com) and that your contact information is correct and current.

  • Make sure all of your assets have a contact assigned and that the contact is correct and current.

  • Identify and designate a system to serve as ASR Manager.

  • Identify and verify ASR assets.

  • Ensure connectivity to the Internet using HTTPS.

  • Ensure network connectivity to Exadata assets, ILOM, and eth0 of the operating system to the designated ASR Manager.

  • Make sure all Hardware and Software Requirements are met.

Note:

Currently, Exadata IPv6 is not supported in Oracle Auto Service Request (ASR).

3.1 Hardware and Software Requirements

You will need root access to install the software to set up the ASR Manager.

  • ASR Manager: See the "Installing and Registering ASR Manager Software" in the Oracle® Auto Service Request (ASR) Manager User's Guide to install ASR manager on a standalone server that is running either Linux or Solaris.

    http://docs.oracle.com/cd/E37710_01/install.41/e18475/ch2_asr_manager.htm#ASRUD128
    
  • Database Server: Exadata Software 11.2.1.3.1 or later.

  • Exadata Storage Server Software:

    • Release 12.1.2.1.1 and later.

    • Release 11.2.1.3.1 and later.

  • For configuring trap destinations, you can save time and effort using one of the following options:

    • OneCommand: Running the setupASR step in OneCommand will configure the traps and assist in activating Oracle ASR assets.

    • dcli Utility: Refer to the dcli chapter in the Oracle Exadata Storage Server Software User's Guide for instructions to enable SSH for the dcli utility.

  • Port 162 Availability: Port 162 is the SNMP port and is used to Configure Fault Telemetry Destinations. This port value can be configured as a different port based on your network requirements, or it may need to be changed for ASR to work correctly in a managed environment.

  • The dcli Utility: While not required for ASR, the dcli utility gives the ability to set up all servers at the same time and also the storage servers at the same time. The dcli utility set definitions are:

    • dbs_group is a file that would contain the database nodes such as dm01db01, dm01db02, and so forth, and may be found at:

      /opt/oracle.SupportTools/onecommand/dbs_group
      
    • cell_group is a file that would contain the Exadata Cells such as dm01cel01, dm01cel02, and so forth, and may be found at:

      /opt/oracle.SupportTools/onecommand/cell_group
      

    Refer to the ”Setting User Equivalence” section in the Oracle Exadata Database Machine Extending and Multi-Rack Cabling Guide for instructions to enable SSH for the dcli utility. Depending on your environment restrictions, the dcli utility may not be set up. See Oracle Exadata Command and Configuration Reference for more information about the dcli utility.

    The dcli utility commands shown in this document will run commands expecting equivalency with the root or celladmin user, depending on the command. You must ensure the user who runs the dcli utility command has the proper equivalency set up.

4 Configure Fault Telemetry Destinations

Follow the instructions below to configure fault telemetry destinations on the Oracle Exadata Storage Server and Database Server.

To configure fault telemetry, choose one of the following three options:

Note:

Oracle ASR can only use the management network. You must make sure that the management network (ETH0 on the interfaces or net0 on the back of the server) is set up to allow ASR to run.

Element Definitions

The sections below include command examples that may use the following elements:

  • host=[ASR Manager host name or IP] is the ASR Manager host name or IP address. The ASR Manager host name can be used when DNS is enabled for the site. If DNS is not running, the IP address is preferred, but the ASR Manager host name can be used if the entry is added to /etc/hosts file.

  • type=asr represents the ASR Manager being a special type of SNMP subscriber.

  • community=public is the required value of the community string. (This value is per customer as it can be modified to be a different string based on customer network requirements.)

  • port=162 is the SNMP port. (This port value is customer dependent. It can be configured as a different port based on network requirements, or it may need to be changed for ASR to work correctly in a managed environment.)

  • fromIP enables you to specify an IP address from which the trap is sent. If this field is not specified, it defaults to the IP address associated with eth0. Use this field if the default IP address is not registered with ASR Manager. ASR Manager only processes SNMP traps that are sent from IP addresses that it recognizes.

    The fromIP field is allowed only for snmpSubscribers whose type is either ASR or v3ASR.

Note:

To enable and activate InfiniBand Switches, refer to How to configure Datacenter InfiniBand Switch 36 & QDR InfiniBand Gateway Switches for ASR (Doc ID 1902710.1) in My Oracle Support:
https://support.oracle.com/rs?type=doc&id=1902710.1

4.1 Add SNMP Trap Destinations Using OneCommand

If this is the initial deployment of the Exadata Database Machine, OneCommand will automatically configure SNMP settings if run with the version released on April 26, 2012 (patch 14004092) or later. You can download the patch from My Oracle Support:

https://support.oracle.com

Tip:

See the "OneCommand" section of Exadata Database Machine and Exadata Storage Server Supported Versions (Doc ID 888828.1) for a complete list of patches available for download in My Oracle Support.
https://support.oracle.com/rs?type=doc&id=888828.1

Select the patch for your supported version.

OneCommand performs the SNMP configuration to ASR when the SetupASR command is executed.

Note:

If your designated ASR Manager is not pingable by this step, then the ASR Manager's IP address was most likely not set correctly in the configurator spreadsheet.

To confirm that OneCommand has set up the trap destinations, run the following command and verify that the host and ports point to the ASR server:

  • For a system with Exadata Storage Server Software 12.1.2.x or later:

    # dbmcli -e list dbserver attributes snmpSubscriber
    
  • For a system with Exadata Storage Server Software earlier than 12.1.2.x:

    # dcli -g dbs_group -l root "/opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -get_snmp_subscribers -type asr"
    
    # dcli -g cell_group -l celladmin "cellcli -e list cell attributes snmpsubscriber"
    

You will need to run this command from an account that has equivalency with the root user on the database nodes and celladmin equivalency on the cell nodes.

4.2 Add SNMP Trap Destinations for a Single Server

If OneCommand or the dcli utility is not available, then add the trap destinations to each node using the command line interface (CLI).

Caution:

Refer to ASR SNMP Trap Destination and Enterprise Manager on Exadata Cell Nodes (Doc ID 1451026.1). You must ensure that for any SNMP addition, the ASR entry is last in the snmpsubscriber string. You can access this document in My Oracle Support:
https://support.oracle.com/rs?type=doc&id=1451026.1

Note:

Repeat for each Oracle Exadata Database and Storage nodes.

For the Exadata Database Server, log in to the first server as root. Run the following command:

  • If your Exadata Server Software is release 12.1.2.x or later, run:

    # dbmcli -e alter dbserver snmpSubcriber=((host='<ASR Manager host name or IP>',port=162,community=public,type=asr))
    
  • If your Exadata Server Software is release earlier than 12.1.2.x, run;

    # /opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -set_snmp_subscribers "(type=asr,host=<ASR Manager host name or IP>,fromip=<ETH0 Node IP>,port=162,community=public)"
    

For the Exadata Storage Server, log in to each storage server as celladmin on the storage node.

  • Run the following command:

    # cellcli -e alter cell snmpsubscriber=((host ='<ASR Manager host name or IP>',port=162,community=public,type=asr))
    

4.3 Add SNMP Trap Destinations for Multiple Servers Using the dcli Utility

If OneCommand did not already set up the trap destinations, then you can follow the instructions outlined below to use the dcli utility to add trap destinations for multiple servers:

Caution:

Refer to ASR SNMP Trap Destination and Enterprise Manager on Exadata Cell Nodes (Doc ID 1451026.1). You must ensure that for any SNMP addition, the ASR entry is last in the snmpsubscriber string. You can access this document in My Oracle Support:
https://support.oracle.com/rs?type=doc&id=1451026.1

Note:

If dcli is not or cannot be enabled, follow the steps in Add SNMP Trap Destinations for a Single Server.

4.3.1 Exadata Database Server with Server Software Release 12.x (dbmcli command)

For the Exadata Database Server, log in to the first database node as root. Run the dbmcli command:

  • Retrieve the server details:

    # dbmcli -e list dbserver detail
    

    Output will look like this:

    name: host01
    bbuStatus: normal
    coreCount: 12
    cpuCount: 24
    diagHistoryDays: 7
    fanCount: 16/16
    fanStatus: normal
    id: 1117FMM0NE
    interconnectCount: 2
    ipaddress1: 111.222.33.44/55
    kernelVersion: 2.6.39-400.248.3.el6uek.x86_64
    locatorLEDStatus: off
    makeModel: Oracle Corporation SUN FIRE X4170 M2 SERVER
    metricHistoryDays: 7
    msVersion: OSS_12.1.2.1.1_LINUX.X64_150316.2
    notificationMethod: snmp
    powerCount: 2/2
    powerStatus: normal
    releaseImageStatus: success
    releaseVersion: 12.1.2.1.1.150316.2
    releaseTrackingBug: 20240049
    status: online
    temperatureReading: 21.0
    temperatureStatus: normal
    upTime: 0 days, 0:49
    msStatus: running
    rsStatus: running
    
  • Set the first SNMP subscriber:

    # dbmcli -e alter dbserver snmpSubcriber=((host='host01.mycompany.com',port=162,community=public,type=asr))
    
    # dbmcli -e list dbserver detail
    

    Notice the snmpSubscriber entry as shown in this example:

    name: host01
    bbuStatus: normal
    coreCount: 12
    cpuCount: 24
    diagHistoryDays: 7
    fanCount: 16/16
    fanStatus: normal
    id: 1117FMM0NE
    interconnectCount: 2
    ipaddress1: 111.222.33.44/55
    kernelVersion: 2.6.39-400.248.3.el6uek.x86_64
    locatorLEDStatus: off
    makeModel: Oracle Corporation SUN FIRE X4170 M2 SERVER
    metricHistoryDays: 7
    msVersion: OSS_12.1.2.1.1_LINUX.X64_150316.2
    notificationMethod: snmp
    powerCount: 2/2
    powerStatus: normal
    releaseImageStatus: success
    releaseVersion: 12.1.2.1.1.150316.2
    releaseTrackingBug: 20240049
    snmpSubscriber: host=host01.mycompany.com,port=162,community=public,type=asr
    status: online
    temperatureReading: 21.0
    temperatureStatus: normal
    upTime: 0 days, 0:49
    msStatus: running
    rsStatus: running
    
  • Set the second SNMP subscriber:

    # dbmcli -e alter dbserver snmpSubcriber=((host='host01.mycompany.com',port=162,community=public,type=asr),(host='host02.mycompany.com',port=162,community=public,type=asr))
    
    # dbmcli -e list dbserver detail
    

    Notice the snmpSubscriber entry as shown in this example:

    name: host01
    bbuStatus: normal
    coreCount: 12
    cpuCount: 24
    diagHistoryDays: 7
    fanCount: 16/16
    fanStatus: normal
    id: 1117FMM0NE
    interconnectCount: 2
    ipaddress1: 111.222.33.44/55
    kernelVersion: 2.6.39-400.248.3.el6uek.x86_64
    locatorLEDStatus: off
    makeModel: Oracle Corporation SUN FIRE X4170 M2 SERVER
    metricHistoryDays: 7
    msVersion: OSS_12.1.2.1.1_LINUX.X64_150316.2
    notificationMethod: snmp
    powerCount: 2/2
    powerStatus: normal
    releaseImageStatus: success
    releaseVersion: 12.1.2.1.1.150316.2
    releaseTrackingBug: 20240049
    snmpSubscriber: host=Host01.mycompany.com,port=162,community=public,type=asr host=host02.mycompany.com,port=162,community=public,type=asr
    status: online
    temperatureReading: 21.0
    temperatureStatus: normal
    upTime: 0 days, 0:49
    msStatus: running
    rsStatus: running
    

Note:

ILOMs are set up via Exadata. Do not configure the ILOMs manually.

4.3.2 Exadata Database Server with Server Software Release 11.x (dcli command)

For the Exadata Database Server, log in to the first database node as root. Run one of the following commands, depending on your environment:

  • If your Exadata Server Software is earlier than Release 11.2.2.4.0, run:

    # dcli -g dbs_group -l root "/opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -set_snmp_subscribers \"\(type=asr,host=[ASR Manager host name or IP],port=162,community=public,\)\""
    
  • If your Exadata Server Software is Release 11.2.2.4.0 or later, run;

    # dcli -g dbs_group -l root "fromip=\$(ifconfig eth0 | awk '/inet addr/ {print \$2}' | cut -d: -f2);/opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -set_snmp_subscribers \"(type=asr,host=[ASR Manager host name or IP],fromip=\$fromip,port=162,community=public)\""
    

Note:

ILOMs are set up via Exadata. Do not configure the ILOMs manually.

4.3.3 Exadata Storage Server

For the Exadata Storage Server, log in to the first storage server as a user with equivalency to the celladmin user (typically oracle). Run the following command:

  • Check check all cells for the snmpSubscriber attribute:

    # dcli -g cell_group -l celladmin "cellcli -e list cell attributes snmpSubscriber"
    

    Note:

    In some cases, SNMP entries may already be set up for monitoring (such as, Enterprise Manager). See Oracle Database Machine Monitoring Best Practices (Doc ID 1110675.1) in My Oracle Support for the appropriate links for that documentation:
    https://support.oracle.com/rs?type=doc&id=1110675.1
    
  • Run the following command (you will need to run this command from an account that has equivalency with the celladmin user on the cells):

    # dcli -g cell_group -l celladmin "cellcli -e alter cell snmpsubscriber=\(\(host=\'<ASR Manager host name or IP>\',port=162, community=public,type=asr\)\)"
    

4.4 Activate Node on the ASR Manager

Notes:

  • The commands listed below are to be run on the ASR Manager host, not on Exadata hosts.

  • Repeat for each Oracle Exadata Database Machine being attached for ASR.

  1. To validate if ILOM auto-activation occurred (if the network and ILOM are set up correctly), run the following command:

    # asr list_asset
    

    Output should look like this:

    Surrounding text describes asr_list_asset_example.gif.

    If all ILOMs for Exadata nodes are in the list, skip to Step 3. If ILOMs are not in the list, proceed with Step 2.

  2. Activate ILOM. Run the following command:

    # asr activate_asset -i [Node ILOM IP]
    

    or

    # asr activate_asset -h [Node ILOM host name]
    

    Note:

    Use the script file generated by OneCommand's setupASR step, if available. The script, which includes the asr activate_asset command, is located here:
    /opt/oracle.SupportTools/onecommand/AsrActivationScript.txt
    

    This script is valid as long as the IPs for all nodes have not changed since initial deployment.

  3. Activate the Exadata OS side of the ASR support. Run one of the following commands:

    # asr activate_exadata -i [Node IP address] -h [Node host name] -l [Node ILOM IP]
    

    or

    # asr activate_exadata -i [Node IP address] -h [Node host name] -n [Node ILOM host name]
    

    Note:

    Use the script file generated by OneCommand's setupASR step, if available. The script, which includes the asr activate_exadata command, is located here:
    /opt/oracle.SupportTools/onecommand/AsrActivationScript.txt
    

    This script is valid as long as the IPs for all nodes have not changed since initial deployment.

  4. Verify all nodes are visible on the ASR Manager. Run the following command:

    # asr list_asset
    
  5. Approve and assign contacts to nodes. For more information on the process, see How To Manage and Approve Pending ASR Assets In My Oracle Support (Doc ID 1329200.1):

    https://support.oracle.com/rs?type=doc&id=1329200.1
    

5 Exadata Validation and SNMP Test Trap Commands

Run the following commands to validate SNMP trap configurations.

Database node configuration validation

  • To verify using the dcli utility, run the following command on an Exadata Database Machine host (you will need to run this command from an account that has equivalency with the root user on the database nodes):

    • If your Exadata Server Software is release 12.1.2.x or later:

      # dcli -g dbs_group -l root -n "dbmcli -e list dbserver attributes snmpSubscriber"
      
    • If your Exadata Server Software release is earlier than 12.1.2.x:

      # dcli -g dbs_group -l root –n "/opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -get_snmp_subscribers -type asr"
      
  • To verify the configuration when the dcli utility is not available, run the following command on each Exadata Database Machine host:

    • If your Exadata Server Software is release 12.1.2.x or later:

      # dbmcli -e list dbserver attributes snmpSubscriber
      
    • If your Exadata Server Software release is earlier than 12.1.2.x:

      # /opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -get_snmp_subscribers -type asr
      

Storage node configuration validation

  • To verify using the dcli utility, run the following command on the first database node host (you will need to run this command from an account that has equivalency with the celladmin user on the cells):

    # dcli -g cell_group -l celladmin "cellcli -e list cell attributes snmpsubscriber"
    
  • To verify when the dcli utility is not available, log on as celladmin and run the following command on each Exadata cell storage host:

    # cellcli -e "list cell attributes snmpsubscriber"
    

Database node SNMP validation

  • For a system with Exadata Storage Server Software 12.1.2.x or later:

    # dbmcli -e alter dbserver validate snmp type=asr
    
  • For a system with Exadata Storage Server Software earlier than 12.1.2.x:

    • To verify using the dcli utility, run the following command on an Exadata Database Machine host:

      # dcli -g dbs_group -l root "/opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -validate_snmp_subscriber-type asr"
      
    • To verify when the dcli utility is not available, run the following command on each Exadata Database Machine host:

      # /opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -validate_snmp_subscriber -type asr
      

Storage node SNMP validation

  • To verify using the dcli utility, run the following command on each Exadata cell storage host:

    # dcli -g cell_group -l celladmin "cellcli -e alter cell validate snmp type=asr"
    
  • To verify when the dcli utility is not available, run the following command on each Exadata cell storage host:

    # cellcli -e "alter cell validate snmp type=asr"
    

After the Validate SNMP Trap step is done, Oracle will send e-mail notifications for each of the nodes to:

  • ASR Manager registration user specified in the ASR Manager asr register command.

  • Asset Contact assigned in My Oracle Support.

  • Distribution e-mail list assigned in My Oracle Support (optional).

When deploying Oracle ASR, you must run the asrexachck script as described in Engineered Systems ASR Configuration Check via ASREXACHK (Doc ID 1450112.1) to verify the ASR deployment.

For more details, this document is available in My Oracle Support:

https://support.oracle.com/rs?type=doc&id=1450112.1

An Oracle Service Request (SR) must be filed to validate that the ASR installation is correct end-to-end. Include the output of the asrexachck script when you file the SR.

6 Configure and Activate Switches

To configure Datacenter InfiniBand Switch 36 and QDR InfiniBand Gateway Switches for Oracle ASR, follow the instructions outline in Oracle Support Document 1902710.1 available in My Oracle Support (https://support.oracle.com):

https://support.oracle.com/rs?type=doc&id=1902710.1

7 Additional Resources

Oracle ASR

Oracle Exadata Database Machine Documentation

My Oracle Support (MOS)

8 Third-Party Licenses

Oracle Auto Service Request (ASR) includes third-party products. For a complete list of the licensed third-party products, see Appendix C, "Third-Party Licenses," of the Oracle® Auto Service Request (ASR) Manager User's Guide:

http://docs.oracle.com/cd/E37710_01/install.41/e18475/app_3rd_party.htm#ASRUD366

9 Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.


Oracle Auto Service Request Exadata Database Machine Quick Installation Guide, Release 5.3

E23333-15

Copyright © 2015, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.