I just added a newly created LUN to my storage group and I rescanned the adapters, found the new LUN... named the vmfs volumes and it formatted it. Then when I go to the 2nd esx server in my DRS/HA cluster and try to add it... it sees it but wants to give the lun a name and format it again. It named the vmfs volume (volume1) where the first one would have been just (volume). Now I'm thinking this is not right. I removed it and went to rescan then re-add it, thinking it would simply list itself as the VMFS volume I created from the first server and just add it. It didn't do that. Does it sound like I am doing somthing wrong? I have reviewed the server config.pdf and it covers the steps for the first server but not adding the vmfs volume to a second server. Any assistance would be greatly appreciated.
Sounds like you are "Adding It" instead of rescanning and the 2nd host just seeing it. It should just be a rescan of the Adapter and the host see it. No need to add the LUN
I did do a rescan, in fact I did another one just now to make sure I wasn't mistaken. It still does not show up, but if I add the storage it sees the LUN. Kind of weird huh?
Does the LUN have the same "signature" on both the ESX hosts? If not, you might have to change a setting.
The setting would be in the Advanced Settings for the ESX host, under LVM.
LVM.DissalowSnapshotLUN = 0
Message was edited by:
waynegrow
I removed and recreated it again from the other host first this time. It rescanned again okay from the additional host. In the first scenari, on the second host I "added: storage and picked the LUN, it added the datastore name with a 1 on the end of it. I think I torqued it and it didn't want to play nicely after that. The newly created store works okay. Sometimes these things make you second guess yourself. Thanks for the insight.