If your LUN is showing up as a snapshot, then that means it looks like a LUN you already have existing. Most likely, the LUN ID is the same as an existing LUN. So, to not write to the same LUN using two different paths, the new path is disabled. You should first figure out if there is a LUN match with another, and update it so that it is unique. Second, the resignature is usually only required if the LUN had a pre-existing VMFS on it, and the LUN needs to be cleaned out and a new signature or ID written to it.
I tend to stay away from resignature, unless absolutely necessarry, as it can cause problems with naming of the datastore, especially if there are multiple hosts that access it.
The workaround will rename the datastore to something-snap001 or something like that. Then, you'll have to rename it to what you want, then rescan your hosts to pickup the new name. Assuming you've fixed the LUN ID issue, you won't have to do any of this, since your LUN will be seen as unique, and thus resignature will not be required.
-KjB
vExpert/VCP/VCAP
vmwise.com / @vmwise
-KjB
