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-72-2186681.1
Update Date:2017-07-17
Keywords:

Solution Type  Problem Resolution Sure

Solution  2186681.1 :   FS System: Controller Target Ports Disconnect and Reconnect within a SAN Fabric During a Non-Disruptive Upgrade (NDU)  


Related Items
  • Oracle FS1-2 Flash Storage System
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Flash Storage>SN-EStor: FSx
  •  




In this Document
Symptoms
Changes
Cause
Solution
References


Created from <SR 3-13349822781>

Applies to:

Oracle FS1-2 Flash Storage System - Version All Versions and later
Information in this document applies to any platform.

Symptoms

During a Non Disruptive Upgrade (NDU) of the Oracle Flash Storage FS1-2, the SAN hosts accessing I/O on the the array may report the following events:

Note: The PWWN below have been sanitized with XXXXXXXXXXX.

   

Sep 18 18:20:32 hostname fctl: [ID 517869 kern.warning] WARNING: fp(4)::GPN_ID for D_ID=10000 failed
Sep 18 18:20:32 hostname fctl: [ID 517869 kern.warning] WARNING: fp(4)::N_x Port with D_ID=10000, PWWN=XXXXXXXXXXX730c0 disappeared from fabric
Sep 18 18:20:32 hostname fctl: [ID 517869 kern.warning] WARNING: fp(4)::GPN_ID for D_ID=10100 failed
Sep 18 18:20:32 hostname fctl: [ID 517869 kern.warning] WARNING: fp(4)::N_x Port with D_ID=10100, PWWN=XXXXXXXXXXX73260 disappeared from fabric
Sep 18 18:20:32 hostname fctl: [ID 517869 kern.warning] WARNING: fp(4)::GPN_ID for D_ID=10200 failed
Sep 18 18:20:32 hostname fctl: [ID 517869 kern.warning] WARNING: fp(4)::N_x Port with D_ID=10200, PWWN=XXXXXXXXXXX73130 disappeared from fabric
Sep 18 18:20:32 hostname fctl: [ID 517869 kern.warning] WARNING: fp(8)::GPN_ID for D_ID=10000 failed
Sep 18 18:20:32 hostname fctl: [ID 517869 kern.warning] WARNING: fp(8)::N_x Port with D_ID=10000, PWWN=XXXXXXXXXXX73330 disappeared from fabric
Sep 18 18:20:32 hostname fctl: [ID 517869 kern.warning] WARNING: fp(8)::GPN_ID for D_ID=10100 failed
Sep 18 18:20:32 hostname fctl: [ID 517869 kern.warning] WARNING: fp(8)::N_x Port with D_ID=10100, PWWN=XXXXXXXXXXX736c0 disappeared from fabric
Sep 18 18:20:32 hostname fctl: [ID 517869 kern.warning] WARNING: fp(8)::GPN_ID for D_ID=10200 failed
Sep 18 18:20:32 hostname fctl: [ID 517869 kern.warning] WARNING: fp(8)::N_x Port with D_ID=10200, PWWN=XXXXXXXXXXX73570 disappeared from fabric
Sep 18 18:20:38 hostname fctl: [ID 517869 kern.warning] WARNING: fp(4)::N_x Port with D_ID=10000, PWWN=XXXXXXXXXXX730c0 reappeared in fabric
Sep 18 18:20:38 hostname fctl: [ID 517869 kern.warning] WARNING: fp(4)::N_x Port with D_ID=10100, PWWN=XXXXXXXXXXX73260 reappeared in fabric
Sep 18 18:20:38 hostname fctl: [ID 517869 kern.warning] WARNING: fp(4)::N_x Port with D_ID=10200, PWWN=XXXXXXXXXXX73130 reappeared in fabric
Sep 18 18:20:38 hostname fctl: [ID 517869 kern.warning] WARNING: fp(8)::N_x Port with D_ID=10000, PWWN=XXXXXXXXXXX73330 reappeared in fabric
Sep 18 18:20:38 hostname fctl: [ID 517869 kern.warning] WARNING: fp(8)::N_x Port with D_ID=10100, PWWN=XXXXXXXXXXX736c0 reappeared in fabric
Sep 18 18:20:38 hostname fctl: [ID 517869 kern.warning] WARNING: fp(8)::N_x Port with D_ID=10200, PWWN=XXXXXXXXXXX73570 reappeared in fabric


The Port WWN (PWWN) reported in the above SAN events are related to the FS1-2 Controller host port.

Changes

A FS1-2 NDU takes place at the time these SAN events are reported. 

Cause

During a FS1-2 NDU, the array needs to warmstart both Controllers in order to activate the new code. The warmstart is an activity which lasts about 5-8 seconds for each Controller and this leads each Controller host port (aka target ports) to disappear and then reappear in the SAN fabric. These events are absolutely normal during a NDU and the I/O retries (if any) take place right after the target ports are back.
 

Solution

You can safely ignore these events if they occur during the FS1-2 NDU.

The <Bug 24696509> (type Enhancement Request) has been logged to request the engineering to eventually warmstart the Controllers in a stagged manner.

References

<BUG:24696509> - NDU SHOULD WARMSTART THE CONTROLLERS ONE AFTER THE OTHER

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