![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||
Solution Type Problem Resolution Sure Solution 2148437.1 : FS System: "HTTPS_UNKNOWN_HOST_FAILURE" event may be recorded during a callhome failure
In this Document
Created from <SR 3-12818589511> Applies to:Oracle FS1-2 Flash Storage System - Version All Versions to All Versions [Release All Releases]Information in this document applies to any platform. Symptoms"HTTPS_UNKNOWN_HOST_FAILURE" event is recorded during failed callhome test. Changes
CauseA transient Linux operating system condition exists within the pilot. SolutionFailover to the 'standby' pilot using the FSCLI management software and the repeat the callhome test. NOTE: Confirm FS1-2 status is 'NORMAL' status. If the system status is warning (yellow) or critical (red), resolve those conditions before proceeding.
1. Disable Call-Home to prevent spurious alerts (see Document 1942676.1 FS System: How to Disable Call-Home to Prevent Automatic Service Request (ASR) Generation). 2. Login as support account 'pillar' using fscli: # fscli login -u pillar -oracleFS <FQDN or IP address of FS1-2>
NOTE: The default password as per FS System: Passwords Associated with the Oracle FS1-2 Flash Storage System (Doc ID 2046703.1) 3. Failover to the standby pilot. # fscli pilot -forceFailover
4. Repeat callhome test. NOTE: When a successful callhome is achieved, failover (back) to the original pilot and retest callhome again for completion.
References<NOTE:1988591.1> - FS System: How to Configure and Test Call-Home<NOTE:2046703.1> - FS System: Passwords Associated with the Oracle FS1-2 Flash Storage System <NOTE:1496027.1> - Pillar Axiom: How to manually test Callhome Transfers from the pilot in SSH <NOTE:1570356.1> - Pillar Axiom: Troubleshooting callhome issues with network traces Attachments This solution has no attachment |
||||||||||||||||||||
|