Oracle Exadata Hardware
 
Exalogic Elastic Cloud X5-2 Hardware
 
Big Data Appliance Hardware
 

PLA-Support>Sun Systems>x86>x86-ASR>SN-x86: ASR Configuration
 

Fault codes produced by asrexack and/or asrexacheck utilities - see MOS Doc ID 1450112.1 and Doc ID 2103715.1

Applies to:

Goal

Explanation of Error Messages and needed actions when running asrexacheck

The following documents all of the error messages you may receive as a result of running the asrexacheck application.
Along with an explanation of the messages, there are instructions as to what should be done to resolve the issues.

Asrexacheck may be run in 2 different manners but the messages, and their resolutions, are the same.

As part of exachk; ./exachk -profile hardware
Standalone mode; ./asrexacheck

For Exalogic OS validation is skipped.

For ASR to be valid on ILOM the following properties must be enabled;

-> show /SP/alertmgmt/rules/X
Targets:

Properties:
type = snmptrap
level = minor
destination = x.x.x.x
destination_port = 162
community_or_username = public
snmp_version = 2c

Solution

Error Messages

Both of these messages mean that the named file or the directory in which it is located does not have the correct permissions to allow you to either read or write to it.

Please verify that the permissions are correctly set. If you utilized the –L option, you should re-verify that the directory named allows read/write permissions.

The asrexacheck script verifies that you are logged in as the ‘root’ user.

Log in as the ‘root’ user to run this script.

The ipmitool was not found in the known directories for Linux 5.x and Linux 6.x

Ipmitool package should be installed as part of a normal part of an Engineered System.
If it has been moved, please restore it to the appropriate directory.

Linux 5.x - /usr/bin

Linux 6.x - /usr/sbin

Earlier Engineered Systems with certain image versions can occasionally hang the BMC controller.

Seek guidance on how to correct this issue from EEST team.

Earlier Engineered Systems with earlier images could occasionally hang the BMC controller. You may see this in conjunction with the BMC message above.

Seek guidance on how to correct this issue from EEST team.

The asrexacheck script was ran on an unsupported system.

Run it only on products documented as supported in MOS doc 2103715.1.

The asrexacheck script was ran on an unsupported system.

Run it only on products documented as supported in MOS doc 2103715.1.

The asrexacheck script was unable to determine correct ILOM configuration.

Open an SR with ASR Support team to investigate the issue, attach generate zip file to the SR.

Warning Messages

This script has found multiple ASR managers to which events are being sent. No test will be performed.

Each platform should only be pointing to one ASR Manager so that multiple service requests are not opened when a fault event occurs.

Determine which ASR Manager is the appropriate to send events to and remove the others, then re-run the script.

There was an error creating the zip file. Possible reasons are permission issue or lack of disk space where the zip file was being created.

Validate permission or disk space issues in the targeted directory.

Change to the named directory and manually zip the files to be sent back to Oracle.

Informational Messages

The IP of the ASRM designated by your system is not reachable due to firewalls or filtering or may not exist.

Check with your network team if PING is allowed between asset IP and ASRM IP. This may not need fixing if assets are able to send events to the ASRM even though it is not pingable.

Configuration is missing notification method.

Run the following to add snmp as a notification method;

Cell# cellcli -e "alter cell notificationMethod='mail,snmp'"

DB# dbmcli -e "alter dbserver notificationMethod='mail,snmp'"

The asrexacheck script has noted that for value type=asr the pointer in ILOM is setup to use the V1 protocol, which is not correct.

To fix the snmp_version perform the following based on the rule value of 'X' reflected as belonging to ASR;

# ipmitool sunoem cli "set /SP/alertmgmt/rules/X snmp_version=2c"

The asrexacheck script was not able to find an instance of type=asr or an ILOM rule matching all criteria for ASR.

Enable ASR for this node, if appropriate.

See Chapter 4 Configure Fault Telemetry Destinations of the Oracle Auto Service Request Exadata Database Machine Quick Installation Guide.

The asrexacheck script was not able to find a rule in ILOM  that matched all criteria for ASR.

If no rule exists one needsa to be established as follows

Enable ASR for this node by selecting an open rule or make corrections to an existing rule, if appropriate.

-> set /SP/alertmgmt/rules/X level=minor destination=X.X.X.X destination_port=162 community_or_username=public snmp_version=2c

Optionally this can also be done in the OS as such;

# ipmitool sunoem cli "set /SP/alertmgmt/rules/X level=minor destination=X.X.X.X destination_port=162 community_or_username=public snmp_version=2c"

If you do not have a rule in which level=minor, version=2c.

A rule needs to be established containing these values (see above) or corrected to contain these values. These parameters are fixed for ASR.

-> set /SP/alertmgmt/rules/X level=minor

-> set /SP/alertmgmt/rules/X snmp_version=2c

If you are using a different port or community then use external file /var/tmp/asrexacheck.conf.

Specify port as "port=number" or community as "community=notpublic"

Example file would look like;

port=1162

community=chicago

The OS image and the ILOM are not directing events to the same end-point. This could mean that some events are not being captured by Oracle Support.

Ensure that the OS and the ILOM point to the same ASR Manager.

See Chapter 4 Configure Fault Telemetry Destinations of the Oracle Auto Service Request Exadata Database Machine Quick Installation Guide.

References

This solution has no attachment