asrexachk Reports ASR Setup Failures and ASR Alerts Are Not Picked Up on BDA V4.0

Asset ID:	1-72-1956717.1
Update Date:	2018-01-17
Keywords:

Solution Type Problem Resolution Sure

Solution 1956717.1 : asrexachk Reports ASR Setup Failures and ASR Alerts Are Not Picked Up on BDA V4.0

Applies to:

Big Data Appliance X4-2 Hardware - Version All Versions and later
x86_64

Symptoms

1. After making the changes in the MOS document: Running asrexachk on BDA V3.*/V4.* Raises, "/opt/oracle/bda/install/state/mammoth-saved.params: No such file or directory" (Doc ID 1956738.1), allowing 'asrexachk' to run on BDA V4, that utility is reporting that ASR setup is incorrect and that the ASR Manager SNMP port is not correct. Output may look like:

# ./asrexachk

Oracle Big Data Appliance X4-2 AK*
ASRExachk 2.7
Fri Oct 31 14:56:19 CET 2014
Hostname: <host_name>
Device Type: Oracle Big Data Appliance X4-2 AK*
Serial Number: 1*
ASR Manager IP:
        #########Warning#########
        Unable to determine configuration status of the DB node.
        Please check to make sure the ASR Manager SNMP Port is
        setup through the command to include the port of 162 or 1162
        Please reference the Oracle Exadata Administration guide for more
        details on DB commands for ASR

Checking for ASR Process Running
        BDA Monitoring Script running as expected

        #########Warning#########
        ASR Is not configured on Node
        Please setup ASR per process from ASR BDA Installation Guide
        http://www.oracle.com/technetwork/server-storage/engineered-systems/bigdata-appliance/documentation/index.html

2. /opt/oracle/bda/compmon/asrs.state is found to have an incorrect port and incorrect host IP even though "mammoth-reconfig add asr" was
run with the correct values and completed successfully.

For example asrs.state looks like:

# cat asrs.state

<incorrect host ip>:<incorrect port> ; <incorrect host>.example.com ; public ;

3. ASR alerts are not picked up.

Cause

/opt/oracle/bda/compmon/asrs.state, the ASR configuration file containing the list of ASR destinations is not correct. This file is the result of the configuration of the ASR asset on any node. It can be changed/updated with /opt/oracle/bda/compmon/bda_mon_hw_asr.pl.

The ASR server reads from this file to to know the set of destinations when it needs to send traps. The server uses snmptrap to send traps. asrexachk reads from this file when validating ASR configurations.

For a valid setup asrs.state must contain the following:
1. The asset must point to an ASM manager
2. The default port for communication between assets and the ASR manager 162.

A correctly configured asrs.state looks like:

# cat asrs.state

<ASR manager host IP>:162 ; <ASR manager host IP> ; public ;

Solution

Use /opt/oracle/bda/compmon/bda_mon_hw_asr.pl to validate and then correctly set ASR subscribers for a BDA node. /opt/oracle/bda/compmon/bda_mon_hw_asr.pl will configure the local node and the ILOM to send traps to the ASR destination.

Perform all steps from Node 1 of the cluster as 'root'.

1. Verify the current configuration from assets: