MaxRep: FS1-2 detects new MaxRep host NPIV ports as Not Connected

Asset ID:	1-72-2152531.1
Update Date:	2016-09-28
Keywords:

Solution Type Problem Resolution Sure

Solution 2152531.1 : MaxRep: FS1-2 detects new MaxRep host NPIV ports as Not Connected

Applies to:

Pillar Axiom Replication Engine (MaxRep) - Version 3.0 to 3.0 [Release 3.0]
Oracle FS1-2 Flash Storage System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

After re-installing the MaxRep software or anytime re-configuring the HBA N_Port ID Virtualization (NPIV) initiator ports without first making sure all of the MaxRep host's initiators are detected as "Not Connected" by the FS1-2, the old HBA WWPN/NPIV initiator ports will continue to display as "Connected" and new HBA WWPN/NPIV initiator ports will be displayed as "Not Connected" by the FS1-2.

This may result in the inability to access the existing mapped LUNs.

Cause

The cause is due to the FS1-2 not receiving two RSCNs when this change occurs.

Solution

This is a software issue that is fixed in release 6.2.4 and higher. Please make sure to upgrade the FS1-2 to 6.2.4 or higher to obtain the fix (this is the preferred option).

If upgrading to 6.2.4 or higher is not an option the workaround is to force a FC link down of all the FC ports on the FS1-2 or a FC link down on all the MaxRep Engine's FC ports with NPIV ports.

Any one of these actions will work:

Disable and re-enable the FS1-2 FC ports using the switch's UI, this forces an implicit logout that will flush the port's database.
Disable and re-enable the MaxRep Engine's FC ports that have NPIV ports using the switch's UI, this will trigger the 2 sets of RSCN to the FS1-2.
Physically disconnect and re-connect the FS1-2 side FC ports, this forces an implicit logout that will flush the port's database.
Physically disconnect and re-connect the MaxRep Engine's ports that have NPIV ports, this will trigger the 2 sets of RSCN to the FS1-2.

NOTE: Please take necessary caution when disabling/enabling ports or disconnecting/reconnecting cables from the FS1-2 as this might cause disruption accessing data on the FS1-2 and may cause data corruption. Before doing any of the recommended actions make sure the SAN hosts have multiple paths to each LUN, and we recommend doing the actions mentioned one port at a time.

References

<BUG:23528333> - FAIL,ERROR WHILE DISCOVERING THE LUN

Attachments

This solution has no attachment