[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 797
  • Last Modified:

SAN volume offline until change in storage processor

We have a customer who is using an EMC AX100i SAN that has two storage processors on it. This same SAN also has two volumes defined. Typicaly, we have one volume on one SP and the other volume on the other SP. Recently, after a reboot the volume on the server will be listed as "Unrecognizable" and won't become active until we move the volume on the SAN from one SP to the other. We will do nothing with the iSCSI initiator and the volume will appear on the server shortly after the storage processor change. There is no support agreement on the SAN and nobody, prior to our involvement, ever set up an account with EMC for support. So, going to EMC is not an option. I am curious if anyone has ever seen this before and, if they have, what did they do to correct it?
0
DavidBCS
Asked:
DavidBCS
  • 4
  • 4
1 Solution
 
Duncan MeyersCommented:
The reason this is happening is that there is nothing telling the AX100 to fail the LUN over. That would be handled either by PowerPath (PowerPath is free for path failover only. You pay for path balancing), or by other software such as Symantec Storage Foindations (also a freebie for no more than two processors and four volumes. Alternatively, you can open the LUN properties and set the failover policy to "automatic".
0
 
DavidBCSAuthor Commented:
Would enabling Multi-path on the iSCSI initiator help in this situation? It is not currently set. Also, since each volume is only bound to one storage processor on the SAN and since there is no auto-failover value to be set on the SAN, could I accomplish the same thing by telling the iSCSI initiator to only attach to the SP hosting the volume instead of looking for both?
0
 
Duncan MeyersCommented:
>Would enabling Multi-path on the iSCSI initiator help in this situation? It is not currently set.
Yes, as part of the fix - but unless the LUN is explicitly told to fail over, it won't. You also need to set teh LUN failover policy to automatic as described above. Th estorage processors won't fail over the LUN unless it's told, or if it doesn't detect I/O on the other storage processor.

>Also, since each volume is only bound to one storage processor on the SAN and since there is no auto-failover value to be set on the SAN, could I accomplish the same thing by telling the iSCSI initiator to only attach to the SP hosting the volume instead of looking for both?
My apologies - got the name wrong. The setting is for auto trespass - trespass is failover in CLARiiON-speak.
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
DavidBCSAuthor Commented:
Is the auto-trespass feature something that is licensed? I don't have that option on the SAN under the WebUI. I think this particular SAN may be a Dell re-brand. Could it be possible that it is lacking some features as a result? Pardon my ignornace as I am not familiar with this product since I mainly work with HP SANs and we inherited this when we took over this account.
0
 
Duncan MeyersCommented:
Sorry - having one of those weeks. Look at the LUN properties dialogue box and check the "Enable Auto Assign" box. The LUN will automatically trespass when:
SP reboot or failure
Storage-system reboot or power failure
Server I/O trespassing to the peer SP

With auto assign enabled, if the SP that owns the LUN fails and the server tries to access that LUN through the second SP, the second SP assumes ownership of the LUN to enable access. The second SP continues to own the LUN until the failed SP is replaced and the storage system is powered up. Then, ownership of the LUN returns to its default owner. If auto assign is disabled in this situation, the second SP does not assume ownership of the LUN, and access to the LUN does not occur.


0
 
DavidBCSAuthor Commented:
OK... It must be a licensing issue or something because I have none of those features on the SAN WebUI for auto-trespass or anything to that effect.. Perhaps it's because it is running Navisphere Express and this is a dumbed-down version... I guess I'll live with it... The customer does not want to pour anymore money into this product platform.

Thanks for your assistance. You've given me some good things to look at.
0
 
DavidBCSAuthor Commented:
I have all the information I need at this point.
0
 
Duncan MeyersCommented:
Thanks! Glad I could help.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now