Hi all,
Hoping you can save me some legwork -
We've upgraded our 270c to a 2050ha - data looks good. We did run into the lun signaturing issue with VMWare but forewarned we were able to place the old sigs back onto the luns.
My biggest hassle is that the Windows boxes with iSCSI attached LUN's appear to have lost their luns (ie SQL & Exchange). So the IQN string changed - we set it back to what it should be - but SnapDrive appears to have lost its drive mappings and the SAN lost its iSCSI initiator groups (luckily we can put them back manually from previous autosupports).
So wondering a couple of things
1. whats the fastest way to get SnapDrive to remember its luns (even the MS iSCSI initiator seems to know what it thinks it should be seeing but SD 6 has lost all its config) ? I know I can manually re-connect them all but with DBA's and Exchange Admins having weird and wonderful drive mappings this is going to be time-consuming.
2. why did the SAN lose its initiator group config (across all luns and including chap security for our dmz esx servers) and why did SnapDrive lose its config (ie the SAN it connects to, the luns, igroup and drive mappings) as a result of a controller and ontap upgrade ?
Next time I'll be sure to screenshot every lun mapping in Windows but surely I shouldn't need to do this ?
Any post-upgrade tips to make my Sunday reconnecting systems a little more pleasant will be gratefully received.
Cheers, Raj.