05-25-2016 11:42 AM
After installed REDHAT OS on a used to be ESX host, we still can see the old storage LUNs, in addtion to the new NetApp LUNs.
It could be caused by the same WWPN number on the same HBA card, and the old zone on SAN switch is till active. Please confirm if it could be the cause, or any other courses you can think of?
One way to resolve it is to remove WWPN from old zoning configuration on the switch. My question is, is there anything I can do on the host, to comopletely deconfigure these old LUNs without removing that zone?
Thank you for sharing!
Solved! Go to Solution.
06-01-2016 09:42 PM
Don't understand ? has your RedHat Lun a different LUN id ?
If your initator pwwn is the same, zoning the same, LUN id is the same and masking / mapping the same on the storage subsystem, then yes, this is expected !
You could erase the LUN, and/or create a new one, with the same masking / mapping on the storage array.
06-01-2016 09:42 PM
Don't understand ? has your RedHat Lun a different LUN id ?
If your initator pwwn is the same, zoning the same, LUN id is the same and masking / mapping the same on the storage subsystem, then yes, this is expected !
You could erase the LUN, and/or create a new one, with the same masking / mapping on the storage array.
06-02-2016 06:18 AM
clean up your zoning before someone fdisk your ESX LUNs from the Redhat server by mistake.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: