ASR (Auto Service Request) Exadata Validate SNMP Type ASR Fails using DCLI with (1). count

Asset ID:	1-75-1390977.1
Update Date:	2012-01-09
Keywords:

Solution Type Troubleshooting Sure

Solution 1390977.1 : ASR (Auto Service Request) Exadata Validate SNMP Type ASR Fails using DCLI with (1). count - 50 Failed to run

Applies to:

Exadata Database Machine X2-2 Hardware - Version: Not Applicable to Not Applicable - Release: N/A to N/A
Exadata Database Machine X2-2 Full Rack - Version: Not Applicable to Not Applicable   [Release: N/A to N/A]
Exadata Database Machine X2-2 Half Rack - Version: Not Applicable to Not Applicable   [Release: N/A to N/A]
Exadata Database Machine X2-2 Qtr Rack - Version: Not Applicable to Not Applicable   [Release: N/A to N/A]
Exadata Database Machine V2 - Version: Not Applicable to Not Applicable   [Release: N/A to N/A]
Linux x86-64

Purpose

Validating and correcting SNMP Trap sending issues on the Exadata Database nodes when the command using dcli, /opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -validate_snmp_subscriber -type asr fails to run and returns an error: (1). count - 50 Failed to run

Last Review Date

January 3, 2012

Instructions for the Reader

A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting Details

Configuration Script Issue

When setting up Exadata and ASR and using the dcli utility, dcli -g dbs_group -l root -n "/opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -set_snmp_subscribers\"\(type=asr,host=[ASR Manager Name or IP],port=162,community=public\)\"" returns a fail code, it will not be able to communicate to the ASR Manager when there is a fault. This will need to be corrected before ASR can be correctly communicated to with a SNMP Trap.
To start, you will need to take a look at the syntax provided after to see the error based on the -set option of the SNMP subscribers which is located in the first few after the error code seen here (1). count - 50 Failed to run "/usr/bin/snmptrap -v 2c -c public\ -M "

Based on this error message, during the command:

Image version 11.2.2.4.0 +

dcli -c examdb01 -l root "/opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -set_snmp_subscribers \"\(type=asr,host=ASR_Manager,fromip=10.10.10.1,port=162,community=public\)\""
returns
examdb01: Try to add ASR destination Host - ASR_Mamager IP - 10.10.10.100 Port - 162 Community - public\ From IP - 10.10.10.1

Image version 11.2.2.2.0 to 11.2.2.3.X

dcli -c examdb01 -l root "/opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -set_snmp_subscribers \"\(type=asr,host=ASR_Manager,port=162,community=public\)\""
returns
examdb01: Try to add ASR destination Host - ASR_Mamager IP - 10.10.10.100 Port - 162 Community - public\

From this, you can see that right after the community string is given in the return code, there is a backslash added onto the string public\. Because of this extra character, the shell script that SNMP uses, sees this as an exit character so that it will not perform the next options ofter it is given and will fail out with given exit code.

Configuration Script Fix

To fix this issue, rerun the commands to add a comma after the string of public, and before the backslash.
dcli -g dbs_group -l root -n "/opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -set_snmp_subscribers\"\(type=asr,host=[ASR Manager Name or IP],port=162,community=public,\)\""

Image version 11.2.2.4.0 +

dcli -c examdb01 -l root "/opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -set_snmp_subscribers \"\(type=asr,host=ASR_Manager,fromip=10.10.10.1,port=162,community=public,\)\""
returns
examdb01: Try to add ASR destination Host - ASR_Mamager IP - 10.10.10.100 Port - 162 Community - public From IP - 10.10.10.1

Image version 11.2.2.2.0 to 11.2.2.3.X

dcli -c examdb01 -l root "/opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -set_snmp_subscribers \"\(type=asr,host=ASR_Manager,port=162,community=public,\)\""
returns
examdb01: Try to add ASR destination Host - ASR_Mamager IP - 10.10.10.100 Port - 162 Community - public

Attachments

This solution has no attachment