Oracle FS1-2 Flash Storage System
 

PLA-Support>Sun Systems>DISK>Flash Storage>SN-EStor: FSx
 

In this Document

Symptoms

Changes

Cause

Solution

References

Created from <SR 3-13341320745>

Applies to:

Symptoms

The Oracle FS1-2 Flash Storage System raised the event "PCP_EVT_SYSTEM_STATE_CHANGED" which triggered an Oracle Service Request.

Changes

A Non Disruptive Upgrade (NDU) was performed. 

Cause

Although we can have different triggers for this event "PCP_EVT_SYSTEM_STATE_CHANGED", the trigger covered in this document is the NDU.

During a NDU, the Pilot 1 and 2 reboot, which triggers a failover and therefore a system state change.

Solution

If you proceeded with a NDU and you confirm that your FS1-2 is in a state optimal after the upgrade, you can safely ignore this event "PCP_EVT_SYSTEM_STATE_CHANGED". If however this event was raised outside of an upgrade activity, this will require further investigation with the assistance from the Oracle Support.

As an Oracle support engineer, you can proceed with the following steps to confirm whether this event "PCP_EVT_SYSTEM_STATE_CHANGED" was related to a NDU.

1. Ask the customer to collect a manual log bundle. Refer to <Document 1943289.1> FS System: How to Attach a Manual Log Bundle to an Existing MOS Service Request.
   
   
2. Run "scanlog6" against the log bundle "XXXXXXXXXX-XXXXXXXXXXXX-XXXXXXXXXXXX-MANUAL_COLLECTION-m-01-01.tar". Refer to <Document 1902160.1> FS System: How to Process Flash Storage and Axiom Logs on Cores3/ISDE.
   
   
3. Go into the directory "XXXXXXXXXX-XXXXXXXXXXXX-XXXXXXXXXXXX-PCP_EVT_SYSTEM_STATE_CHANGED-e-02-02" and execute the egrep command in the following example:
   
   
   # egrep "SOFTWARE_UPDATE_STARTED |PCP_EVT_CONTROLLER_WARMSTART|PCP_EVT_SYSTEM_STATE_CHANGED |SOFTWARE_UPDATE_SUCCEEDED |SYSTEM_STARTUP_SUCCEEDED " events_summary.txt
     
4. If you find events like the following, this means that the "PCP_EVT_SYSTEM_STATE_CHANGED" was triggered due to a NDU:
   
   The upgrade started:
   
   2016-09-16T04:57:48.562 SOFTWARE_UPDATE_STARTED INFORMATIONAL ComponentName=/INTERNAL_OP/5272413/administrator, SoftwareUpdate_ignoreBadState=0
     
   
   The Controllers performed their warmstarts:
   
   2016-09-16T04:58:55.793 PCP_EVT_CONTROLLER_WARMSTART_BEGIN INFORMATIONAL ComponentName=/CONTROLLER-01, Source=/PILOT-1
   2016-09-16T04:58:55.794 PCP_EVT_CONTROLLER_WARMSTART_BEGIN INFORMATIONAL ComponentName=/CONTROLLER-02, Source=/PILOT-1
   2016-09-16T04:58:59.795 PCP_EVT_CONTROLLER_WARMSTART_COMPLETE INFORMATIONAL ComponentName=/CONTROLLER-01, Source=/PILOT-1
   2016-09-16T04:59:02.797 PCP_EVT_CONTROLLER_WARMSTART_COMPLETE INFORMATIONAL ComponentName=/CONTROLLER-02, Source=/PILOT-1
     
   
   The Pilots rebooted and triggered their failover:
   
   2016-09-16T05:16:59.151 PCP_EVT_SYSTEM_STATE_CHANGED INFORMATIONAL Source=/PILOT-1, currentSystemState=NORMAL, previousSystemState=PILOT_FAILBACK_IN_PROGRESS
     
   
   The upgrade succeeded and the FS1-2 is back in an optimal status:
   2016-09-16T05:19:50.873 SOFTWARE_UPDATE_SUCCEEDED INFORMATIONAL ComponentName=/UpdateAndRsyncSoftwareUpdateOperationStatus/183/INTERNAL_OP, SoftwareUpdate_ignoreBadState=0
   2016-09-16T05:20:55.358 SYSTEM_STARTUP_SUCCEEDED INFORMATIONAL

     

References

This solution has no attachment