Enabling, Activating and Testing X86 Oracle Assets for ASR.

Asset ID:	1-71-2022483.1
Update Date:	2018-01-16
Keywords:

Solution Type Technical Instruction Sure

Solution 2022483.1 : Enabling, Activating and Testing X86 Oracle Assets for ASR.

Applies to:

Exadata Database Machine X2-2 Hardware - Version All Versions to All Versions [Release All Releases]
Auto Service Request (ASR) - Version All Versions to All Versions [Release All Releases]
Oracle Platinum Services - Version N/A to N/A
Exadata X3-2 Hardware - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

The goal of this Document is to provide the instructions on how to enable the components telemetry (ILOM/OS), for the ASR Manager activation of the assets components, and to test the end-to-end functionality of ASR by running tests in the Oracle assets.

Note: Please refer to the Products Qualified for ASR document to check the "Telemetry Source" components (ILOM/OS) that need to be enabled and ASR activated for a specific product.
For more details on the ASR Manager application, installation, registration, assets deactivation, etc. please refer to the Auto Service Request ASR Manager User's Guide

Solution

ASR Enabling Telemetry Sources, Activating and testing ASR in Oracle Assets.

Please click on the Product or Component you want to configure or test:

Solaris 10 ASR FMA

Solaris 11 ASR FMA

ILOM

Exadata OS/ILOM

Exalogic ILOM

Solaris 10 ASR FMA

A) Enabling FMA Telemetry for Solaris 10 ASR Assets

B) ASR Manager asset activation

C) Testing ASR

A) Enabling FMA Telemetry for Solaris 10 ASR Assets.

1) Make sure you are logged in as root on the system whose telemetry you wish to enable. This could be either an ASR Manager or an ASR asset system.

2) Go to the directory where you untarred the ASR asset bundle file, and then go to the specific ASR asset bundle directory. For example:

-On an ASR asset:

#cd /file_copy_location/asrassetbundle

-On an ASR Manager:

ASR versions 3.x or 4.x use:

#cd /opt/SUNWswasr/asrassetbundle

for version 5.x use:

#cd /opt/asrmanager/asrassetbundle

3) Launch the ASR asset menu. As root, run the following command to display the ASR asset menu:

#./asrassetmenu.sh

Welcome to the ASR asset menu

-------------------------------------------

1) Add a trap-destination to FMA agent

2) Remove a trap-destination from FMA agent

3) List FMA agent trap-destinations

4) Test event to verify ASR connectivity

5) Exit

Please enter your selection [1-5]

4) Select 3 to enable FMA telemetry. Respond to the script’s prompts as follows:

Please enter Hostname or IP address of ASR Manager (q to quit)

-Enter the information for the ASR Manager. Whether you are enabling telemetry on the ASR Manager system or on ASR asset systems, the host name or IP entered must be for the installed ASR Manager

Please enter SNMP port of ASR Manager (q to quit)

-Press [Return] or enter another port if you have changed your port settings for ASR.

Do you want to set trap-destination [y,n,q]

-Confirm the displayed information, enter Y, and press [Return]

5) The ASR asset menu then enables the telemetry and displays where the telemetry from this system will be sent (IP or host name of the ASR Manager).

6) Repeat for all ASR assets using Solaris 10 FMA telemetry

B) ASR Manager asset activation

asr>activate_asset –i [asset IP]

asr>activate_asset –h [asset Hostname]

C) Testing ASR

-From #./asrassetmenu.sh Select 4 to Test event to verify ASR connectivity with the ASR Manager and the Oracle Backend.

Note:Based on the Status, the email account registered to the ASR Manager, Technical contact and the Distribution list setup in MOS should receive 1 email. If the email has not been received, please work with the X86-ASR engineer for further troubleshooting of the issue.

Solaris 11 ASR FMA

A) Enabling FMA Telemetry for Solaris 11 ASR Assets

B) ASR Manager asset activation

C) Testing ASR

A) Enabling FMA Telemetry for Solaris 11 ASR Assets

-Follow the steps below to active ASR assets for Solaris 11 systems:

1) Log in to the ASR asset as the root user.

2) Run the following command to register the endpoint URL:

For the endpoint URL to be the ASR Manager:

#asradm register -e http://[asr_manager_host]:[port_number]/asr

-The[port_number] is the same port that was specified when enable HTTP receiver was done on the ASR Manager (See Enabling HTTP Receiver for ASR Manager Relay, Solaris 11, and VOP).

-For the endpoint URL to be a direct connect back to Oracle:

#asradm register

3) Enter your Oracle SSO user name and password.

4) Run the following command to view the status:

#asradm list

-The results should appear like this:

#asradm list

PROPERTY VALUE

Status Successfully Registered with ASR manager

System Id <system identification number>

Asset Id <asset identification number>

User MyUserName

Endpoint URL http://<asr_manager_host>:<port_number>/asr

B) ASR Manager asset activation

-Not necessary, the “#asradm register” from the asset activates the asset automatically.

C) Testing ASR

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

#asradm send test email.address@mycompany.com

ILOM

A) Enable ILOM (SNMP): Command Line Interface

B) ASR Manager asset activation

C) Testing ASR

A) Enable ILOM (SNMP): Command Line Interface

-Follow these ILOM command line procedures below to enable ILOM telemetry. If you used the GUI method, as described in the previous procedure, you do not need to complete these steps.

1) Open a terminal window and ssh to the IP address of the ILOM network interface:

ssh IP_address_of_ILOM_interface

2) Log in as root.

3) Before enabling ILOM telemetry, it is important to understand that ILOM supports up to 15 user-configurable alert rules. It is one of these rules you must set to enable ILOM telemetry. Therefore, you must first choose one of these rules (1 to 15) to set.

-Before choosing, however, you must determine that the rule you select is not currently being used. Please list and check the rules current configuration:

-Listing all ILOM SNMP Rules:

>show /SP/alertmgmt/rules -level all

-Once an alert rule slot is determined, run one of the following commands. Pay close attention to the following data entry points before running the command:

rules/x: For x, enter a number from 1 to 15, depending upon which alert rule slot you have determined is unoccupied using the previous step.

destination: Enter the IP address of the ASR Manager.

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

destination_port: Set to 162. For ILOM versions 2.0.4.2 or lower, the port cannot be changed from the default (162).

-For Rack Mount Servers and Blades:

-> set /SP/alertmgmt/rules/x type=snmptrap level=minor destination=[IP_of_ASR Manager] snmp_version=2c community_or_username=public destination_port=162

-For the Sun Blade 6000 Chassis:

-> set /CMM/alertmgmt/rules/x type=snmptrap level=minor destination=[IP_of_ASR Manager] snmp_version=2c community_or_username=public destination_port=162

Note:If you are using ILOM 3.0.16 or above and want to enable SNMP v3, refer to Optional ILOM Setup: SNMP v3 for ASR Assets

B) ASR Manager asset activation:

asr>activate_asset –i [asset IP]

asr>activate_asset –h [asset Hostname]

C) Testing ASR

-Send a test trap to verify end-to-end communications.

>show /SP/alertmgmt/rules -level all

- Once listed please identify the rule number for the "ASR" (ASR Manager IP)

>set /SP/alertmgmt/rules/X testrule=true

X= enter the "rule number" related to ASR to test.

Note:Based on the Status, the email account registered to the ASR Manager, Technical contact and the Distribution list setup in MOS should receive 1 email, which is from the ILOM component. If the email has not been received, please work with the X86-ASR engineer for further troubleshooting of the issue.

Exadata OS/ILOM

A) Exadata Enabling OS/ILOM Telemetry (SNMP)

B) ASR Manager asset activation

C) Testing ASR

A) Exadata Enabling OS/ILOM Telemetry (SNMP)

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 hostname or IP]is the ASR Manager hostname or IP address. The ASR Manager hostname can be used when DNS is enabled for the site. If DNS is not running, the IP address is preferred, but the ASR Manager

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

Add SNMP Trap Destinations for a Single Server:

Add the trap destinations to each node using the command line interface (CLI).

Note: Repeat for each Oracle Exadata Database and Storage nodes.

1) Data Base Nodes.

-If your Exadata Server Software is Release is earlier than 12.1.2.x, run;

#/opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -set_snmp_subscribers "(type=asr,host=[ASR Manager hostname or IP],fromip=[ETH0 NodeIP],port=162,community=public)"

-If your Exadata Server Software is Release 12.1.2.1.0 or later, run:

#dbmcli -e "alter dbserver snmpsubscriber=((host='ASR Manager host or IP',port=162,community=public,type=asr))"

-If your Exadata Server Software is Release 12.2.1.1.0 or later,run:

#dbmcli -e "alter dbserver snmpsubscriber=((host='ASR Manager host or IP',port=162,community=public,type=asr,fromIP=node eth0 ip,asrmPort=16161))"

Element Definitions

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

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

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

community=public is the required value of the community string. This value varies for each implementation because you can modify it to be a different string based on your network requirements.

port=162 is the SNMP port. This port value is customer-dependent. You can configure it as a different port based on your network requirements. Or, you may need to change the port value in order for Oracle ASR to work correctly in a managed environment.

asrmPort is an optional element that supports automatic diagnostic package uploads for Service Requests (SR). The default value is 16161. The value should be set to the same value as displayed for "HTTP Port" in the output of the command asr show_http_receiver on the ASR manager machine.

fromIP enables you to specify an IP address from which the trap is sent. If this field is not specified, then it defaults to the IP address associated with eth0. To support automatic diagnostic package uploads, you must set fromIP on the database nodes to the value of the IP address of the eth0 network interface.Otherwise, use this field if the default IP address is not registered with Oracle ASR Manager. Oracle ASR Manager only processes SNMP traps that are sent from IP addresses that Oracle ASR Manager recognizes.

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

For More information refer- Oracle® Auto Service Request Quick Installation Guide for Oracle Exadata Database Machine

2) Cell Nodes.

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 or IP',port=162,community=public,type=asr))"

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.

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

B) ASR Manager asset activation

-For the ILOM (Data Base and Cell nodes)

asr>activate_asset –i [asset IP]

asr>activate_asset –h [asset Hostname]

-For the OS (Data Base and Cell nodes)

asr>activate_exadata -i [Node IP address] -h [Node hostname] -l [Node ILOM IP]

asr>activate_exadata -i [Node IP address] -h [Node hostname] -n [Node ILOM hostname]

C) Testing ASR

a) asrexacheck 4.X in full rack mode (exachk –profile hardware)

Step 1: Run the following command to invoke the script on the first Database node:

[root@hostdb01 exachk]# /opt/oracle.SupportTools/exachk/exachk –profile hardware

Step 2: Use MOS to upload resulting zip to the SR

Be sure to upload the zip file to the SR related to your ASR issue or the Preventative Maintenance case that prompted you to launch this utility.

b) asrexacheck 4.X in stand-alone mode

Step 1: Running asrexacheck in standalone mode

# /opt/oracle.SupportTools/asrexacheck

Zipfile will be created in /var/log/asrexacheck/

Example; /var/log/asrexacheck/asrexacheck_hostdb01_20160205T153628.zip

Step 2: Use MOS to upload resulting zip to the SR

Be sure to upload the zip file to the SR related to your ASR issue or the Preventative Maintenance case that prompted you to launch this utility.

Note:Based on the Status, the email account registered to the ASR Manager, Technical contact and the Distribution list setup in MOS should receive 2 emails, One from the OS Hostname, and the second from the ILOM Hostname. If 2 emails has not been received, please work with the X86-ASR engineer for further troubleshooting of the issue.

Script Download and detailed instructions check the document below:

Engineered Systems ASR Configuration Check tool (asrexacheck version 4.x) (Doc ID 2103715.1)

Exalogic ILOM

A) Enabling ILOM Telemetry Exalogic

B) ASR Manager asset activation

C) Testing ASR

A) Enabling ILOM Telemetry Exalogic (SNMP)

-Please use the same steps described here: A) Enable ILOM (SNMP): Command Line Interface

B) ASR Manager asset activation

-For the ILOM

asr>activate_asset –i [asset IP]

asr>activate_asset –h [asset Hostname]

C) Testing ASR

Run the asrexacheck script to validate the ASR Configuration setup on the server.
- You may have it in the following path:

#/opt/exalogic.tools/asrexachk

- If not you can download it from the following My Oracle Support KB Document:
Engineered Systems ASR Configuration Check via ASREXACHECK (Doc ID 1450112.1)

You can validate ASR running the above script one by one on the nodes or you can run the following command ONLY on the First DB node:

#dcli -g /opt/ exalogic.tools/onecommand/all_group -l root -x "asrexachk" -d /opt/exalogic.tools

- Please capture the output into a text and upload it into the SR for review.

Attachments

This solution has no attachment