Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-2363975.1
Update Date:2018-03-28
Keywords:

Solution Type  Technical Instruction Sure

Solution  2363975.1 :   Why didn't my DiagPack upload automatically?  


Related Items
  • Exadata X5-2 Hardware
  •  
  • Exadata X6-2 Hardware
  •  
  • Oracle Platinum Services
  •  
Related Categories
  • PLA-Support>Sun Systems>x86>x86-ASR>SN-x86: ASR Configuration
  •  




In this Document
Goal
Solution
References


Created from <SR 3-16899412211>

Applies to:

Exadata X5-2 Hardware - Version All Versions and later
Oracle Platinum Services - Version N/A and later
Exadata X6-2 Hardware - Version All Versions and later
Information in this document applies to any platform.

Goal

Determine why a DiagPack wouldn't upload automatically.

 

Example:
 

2018-02-08T16:01:08-06:00 Maintenance Configuration check discovered some problems

2018-02-08T22:03:03-06:00 Warning Diagnostic packages for Service Requests will not be automatically uploaded.


Software Alert 4_1 2018-02-08T22:03:03-06:00 Warning Diagnostic packages for Service Requests will not be automatically uploaded because ASR Manager xxxxxxx is not accessible or does not support automatic diagnostic package upload or does not have HTTP receiver enabled or SNMP subscribers on xxxxxxx are not configured properly.

Affected Server Name xxxxxxx
Server Model Oracle Corporation ORACLE SERVER XX-X

 

Solution

First verify that the ASR Manager is running;

 

#/opt/asrmanager/util/check_asr_status.sh
Checking ASR Manager status ..
PASS: ASR Manager bundles state is active.
PASS: ASR Manager SNMP listener is running (SNMP port 162).
PASS: ASR Manager database connectivity is working.
PASS: ASR Manager Registration SSO user name is set correctly.
PASS: ASR Manager Oracle transport connectivity is working.
PASS: ASR Manager Oracle transport endpoint is set correctly.
PASS: ASR Manager OSGI port is accessible.
PASS: ASR Manager process is running.

 
If the ASR manager is running properly, please execute the following command on the ASR Manager server:

# asr show_http_receiver

HTTP Receiver configuration:

HTTP Receiver configuration:

HTTP Receiver Status: Enabled
Host Name: 10.xxx.xxx.xxx
HTTP Port: 16161 

 Then, verify the HTTP Port is set to 16161. This value is now required for DiagPack to upload automatically.

 You should see output similar to what is above, if the http receiver is enabled. However, if not, you can enable it by typing the following in the ASR Manager:

# asr enable_http_receiver -p 16161

In addition, please verify the asrmPort is set to the same value as displayed for the "HTTP Port" in the show_http_receiver output.

To see more details about setting the asrmPort value, please see; 

Enabling, Activating and Testing X86 Oracle Assets for ASR. (Doc ID 2022483.1)

 

At this point, attempt to collect a DiagPack. If needed please see;

How To Collect Diagpack Diagnostic Package In Exadata (Doc ID 2226173.1)

 

Please refer to Document 2335926.1 DiagPack FAQs for ASR version and Exadata Image information regarding DiagPack.

 

 

References

<NOTE:2205946.1> - Auto Service Request (ASR) Manager Health Check
<NOTE:2335926.1> - DiagPack - Frequently Asked Questions (FAQ)
<NOTE:2022483.1> - Enabling, Activating and Testing X86 Oracle Assets for ASR.

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback