Auto Service Request (ASR)
 
Big Data Appliance Integrated Software
 
Automatic Service Request (ASR)
 

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

In this Document

Symptoms

Cause

Solution

References

Created from <SR 3-11914179861>

Applies to:

Symptoms

The symptoms are that "bdacli enable asr" fails with: "Could not activate all ASR assets".  The output shows: 

The file: /opt/oracle/BDAMammoth/bdaconfig/tmp/Expect-stdout-20151224095311-3.out, shows that while running, asractivate.sh, there is a problem with activiating assets on
the Admin network for each node in the cluster: <Adm-IP1> through <Adm-IPn>.

Output looks like.

Note that the step here do not  apply for a service tag issue.    These type of messages:

are raised when the ASR manager having problems contacting the servicetag of an asset, either due to network problems (6481 TCP is closed) or due to a service that is not running and not allowing to contact the servicetag.

Cause

This could be due to the port 6481 TCP being closed.

Or

This could be bug: Bug 23483593 - BDACLI ENABLE ASR FAILS WITH ERROR "COULD NOT ACTIVATE ALL ASSET", which is due to "xinetd service" problems.

Solution

To resolve:

1. Check the status of the xinetd service on all nodes of the cluster. 

On the BDA the xinetd service does not run by default, nor should that be the case. But the xinetd service should be running during ASR configuration.

a) Verify the status of the xinetd service on all nodes of the cluster:

b) If the xinetd service is stopped on all nodes of the cluster, start the service for the duration of the ASR configuration.

Note: After ASR configuration, restore the xinetd service to the same state is was before ASR configuration.  Hence, stop the xinetd service after configuring ASR if it was initially stopped.

2. File an SR with BDA Support. In this case an internal case needs to be created by BDA Support to add the assets. 

From BUG 17178749 - ORACLE DATABASE APPLIANCE (ODA) PRODUCT NOT BRIDGING CORRECT ENTITLEMENT TO MOS
Resolve by following the instructions in the internal pdf: HowtosubmitSRforserial_update.pdf

3. Once the assets are activated test that ASR is working properly by following the steps in: Enabling, Activating and Testing X86 Oracle Assets for ASR. (Doc ID 2022483.1)  Section: C) Testing ASR.  From those instructions log into each ILOM via the CLI and run tests against the ASR Manager server.

From the section: C) Testing ASR, send a test trap to verify end-to-end communications, from the ILOM CLI:

a) Log in the ILOM CLI and run the below command to list all SNMP Rules:

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

c) Then replace the X with the Rule Number and test it:

For example using ASR rule #1 the test will be:

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

An email with something like the following should be received:

Note: If the email has not been received, please work via the SR with BDA Support to troubleshoot further.

4. When ASR is configured, restore the xinetd service to the same state is was before ASR configuration i.e. stop the xinetd service it was initially stopped.

This solution has no attachment