![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||
Solution Type Predictive Self-Healing Sure Solution 1571505.1 : Fujitsu M10-1/M10-4/M10-4S Servers: DraftSR: M10-upset_ppar.config
In this Document
Applies to:Fujitsu M10-1 - Version All Versions and laterFujitsu M10-4 - Version All Versions and later Fujitsu M10-4S - Version All Versions and later Fujitsu M10 PCI Expansion Unit - Version All Versions and later Information in this document applies to any platform. PurposeThis article describes activities required by a System Administrator to promote a DraftSR to a formal Service Request when an XSCF reports a M10-upset_ppar.config error. ScopeThis document is intended for System Administrators and support personnel. DetailsAuto Service Request (ASR) provides automatic failure detection and SR creation for Oracle SPARC systems. See http://www.oracle.com/us/asr/index.html for more information on ASR. This particular ASR event has created a Draft Service Request (DraftSR). DraftSRs require manual verification in order to determine whether further action by Oracle Service is required. Description of the ASR Event: Upset due to the fact that PPAR(s) cannot be configured successfully. Step 1: Please review and follow the steps recommended in document: PPAR(s) cannot be configured successfully (Doc ID 1537464.1) Step 2: If the error's root cause does not need to be investigated by Oracle, no further action is required. The DraftSR will automatically expire 30 days from the sending of the notification. If the failure has been verified as requiring an investigation by Oracle to determine and fix the root cause, please proceed with the steps to promote the DraftSR into an open Service Request:
Attachments This solution has no attachment |
||||||||||||||||||
|