Oracle Database Appliance
 

PLA-Support>Sun Systems>Sun_Other>Sun ASR>SN-OTH: ASR
 

Providing steps to configure ASR on the ODA Appliance using a standalone ASR Manager

In this Document

Goal

Fix

Applies to:

Goal

Providing steps to configure ASR on the ODA Appliance using a standalone ASR Manager

Based on the need of ASR and the function of a standalone ASR Manager, here are the steps to follow on the ODA and ASR Manager once installation of the ASR Manager is complete.

For ASR Manager Installation on a standalone server running the required OS Levels, see My Oracle Support ASR Documentation Link :  Oracle ASR Installation and Operations Guide (PDF)

Fix

The following set of steps are to be run on node 0 of the ODA Chassis.

Step 1: Check the validation of ODA to make sure ASR was not previously installed through the "onecommand step 23".

Run the following command to check for the following entries

grep -i "view systemview included .1.3.6.1.4." /etc/snmp/snmpd.conf

If the command returns a value proceed to Step 2, else if the command returns no value, skip to Step 3.

Step 2: Remove the two entries listed below from the file /etc/snmp/snmpd.conf that are a part of the automated configuration.

view systemview included .1.3.6.1.4.

trap2sink X.X.X.X (Note that the X.X.X.X is the ASR Manager IP)

Step 3: Setup the SNMPD.CONF file to have the values to show that we are using an external ASR Manager. Run the following commands to set up the entries for the ODA Node to be able to send SNMP Traps to the ASR Manager in the following listed order. Make sure to update the X.X.X.X to the ASR Managers IP before running the commands.

echo '# ASR Manager Trap Details' >> /etc/snmp/snmpd.conf

echo 'view systemview included .1.3.6.1.4.' >> /etc/snmp/snmpd.conf

echo 'trap2sink X.X.X.X' >> /etc/snmp/snmpd.conf

Step 4: Validate the ASR configuration file on the ODA

cat /opt/oracle/oak/conf/asr.conf

If the file returns a value, proceed to Step 5, else if the command returned an error value of “File not found”, skip to Step 6.

Step 5: Edit the file asr.conf file to have the ASR Manager IP. It is recommended to change the second value to an IP over the hostname. Please make sure to have the following format of the entry:

x.x.x.x ; x.x.x.x ; public

Save the file and exit. Once done, skip to Step 7.

Step 6: Enter in the ASR Manager IP Information, as well as the community string into the asr.conf file

echo "x.x.x.x ; x.x.x.x ; public" >  /opt/oracle/oak/conf/asr.conf

Step 7: The first portion of the setup has been configured, the next step will be to set up the SNMP Ports that ASR uses.

        * Please note that these default ports that are being set up based on normal ASR functionality (setting up port: 162). These ports can be updated per your site requirements.

        Run the three following command sets:

perl -pi -e 's/227/162/' /opt/oracle/oak/adapters/oakAsrTrap.pl

perl -pi -e 's/227/162/' /opt/oracle/oak/onecmd/asrIlom.pl

perl -pi -e 's/227/162/' /opt/oracle/oak/onecmd/GridSteps.pm

Step 8: Configure and setup the ILOM with the information for the ASR Manager.

        Run the following command (Please note that there will be errors, and takes time to finish):

/opt/oracle/oak/onecmd/asrIlom.pl

Once this command finishes, run the next command to check and make sure that the values are there: ipmitool sunoem cli "show /SP/alertmgmt/rules/1"

Step 9: Restart the SNMP Service to have it re-read the new configuration parameters that were just setup for the OS Side.

service snmpd restart

These next set of steps are to be run on the ASR Manager itself.

Step 10: Check the list of assets to see if the ILOM has activated itself within the ASR manager

/opt/SUNWswasr/bin/asr list_asset

If the ILOM hostname of this particular node shows up in the list, skip to Step 12, else if it does not show up, proceed to Step 11

Step 11: Activation of the ILOM for the node being currently setup. Please run the one of the following command sets as it can be dependent on DNS being setup or not:

/opt/SUNWswasr/bin/asr activate_asset -i <ILOM Node IP>

/opt/SUNWswasr/bin/asr activate_asset -h <ILOM Hostname>

Step 12: Activation of the OS side of the ODA Node. This will make sure we capture the Disk faults. Please run one of the following command sets as it can be dependent on DNS being setup or not:

/opt/SUNWswasr/bin/asr activate_asset -i < Node IP>

/opt/SUNWswasr/bin/asr activate_asset -h < Hostname>

NOTE: To get the IP of the ODA Node, run the command set on the ODA Node of:

ip route show | grep bond0 | grep -v default | /usr/bin/awk '{ print $9 }'

Step 13: Run the asset list again to make sure that there are two hostnames present for that current node. You should have one hostname for the ILOM, and than one for the OS. Once everything is done, a total of four Hostnames will be present for each node.

The following set of steps are to be run back on node 0 of the ODA Chassis.

The next set of commands will validate the configuration of the ODA, the ports defined for SNMP Traps on the ODA nodes and send a test trap to the ASR manager and pass it along to Oracle for processing.

Step 14: Run the following test command on the node:

/opt/oracle/oak/adapters/oakAsrTrap.pl asrTrap 1 ASRTest 2 HDD 7 1 DISKALRT-0TEST TEST_Alert pd_01

You should see the following output from the command:

/usr/bin/snmptrap -v 2c -L e -c public -m SUN-HW-TRAP-MIB X.X.X.X:162 "" SUN-HW-TRAP-MIB::sunHwTrapHardDriveFault sunHwTrapSystemIdentifier s "Oracle Database Appliance" sunHwTrapChassisId s "1234567890" sunHwTrapProductName s "SUN FIRE X4370 M2 SERVER" sunHwTrapSuspectComponentName s "ASRTest pd_01; Slot = HDD" sunHwTrapFaultClass s "NULL" sunHwTrapFaultCertainty i 0 sunHwTrapFaultMessageID s "1" sunHwTrapFaultUUID s "NULL" sunHwTrapAssocObjectId o 0.0 sunHwTrapAdditionalInfo s "SUN FIRE X4370 M2 SERVER; x4370m2-hostname-sc1-a Disk TEST_Alert problem: DISKALRT-0TEST."

If you do not see this, please remove the following file:

/opt/oracle/oak/adapters/ oakhwtraps.list

Step 15: Run the following command to run a test event from the ILOM: (Note that the email account used for the ASR Manager registration should receive an email from Oracle about the test event)

ipmitool sunoem cli "set /SP/alertmgmt/rules/1 testrule=true"

If no email is received, please create a Service Request and have it assigned to the ASR Backline team for further investigation.

Now that the first node has been completed, repeat for each additional node

This solution has no attachment