July 8, 2014

Solaris 11.1 and SAN zoning issue

Posted in Solaris tagged , , , , , , at 2:00 pm by alessiodini

Scenario:
– Solaris 11.1
– OSC 4.1 ( two nodes cluster )
– LDOM with I/O domain configuration
– Brocade Switches
– EMC VNX 5200 storage

Recently I faced an issue where rebooting one cluster node, I lost LUN access from the other node.
For example, rebooting node “1” I saw on both nodes:

Jun 21 13:36:02 xxx fctl: [ID 517869 kern.warning] WARNING: fp(5)::GPN_ID for D_ID=a0300 failed
Jun 21 13:36:02 xxx fctl: [ID 517869 kern.warning] WARNING: fp(5)::N_x Port with D_ID=a0300, PWWN=21000024ff470d9e disappeared from fabric
Jun 21 13:36:02 xxx fctl: [ID 517869 kern.warning] WARNING: fp(8)::GPN_ID for D_ID=140300 failed
Jun 21 13:36:02 xxx fctl: [ID 517869 kern.warning] WARNING: fp(8)::N_x Port with D_ID=140300, PWWN=21000024ff470cb8 disappeared from fabric
Jun 21 13:36:44 xxx fctl: [ID 517869 kern.warning] WARNING: fp(5)::N_x Port with D_ID=a0300, PWWN=21000024ff470d9e reappeared in fabric
Jun 21 13:36:44 xxx fctl: [ID 517869 kern.warning] WARNING: fp(8)::N_x Port with D_ID=140300, PWWN=21000024ff470cb8 reappeared in fabric

As the messages said , both nodes got a PWWN disappear/reappear for 40 seconds.
We opened a case to EMC where they said us that our zoning configuration was not supported because there was a multiple initiators configured, instead of a single initiator.
After the new zoning configuration from storage administrator , everything was fine Solaris side 🙂

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: