Vmware Server rebuild effect in the existing SAN & LUN operations

Yes, the new name & IP must be synced with the initiator record on the clariion to reflect the server configuration change. Fortunately, ESX 4.1+ has built in navisphere agent that will sync the change to the clariion automatically. If you didn't see the change on the array, just restart the navisphere agent service on the ESX server.

Steve,

Thanks for the clarification, but I'll be upgrading to ESXi 5.1u1 not ESX anymore.

Does HBA rescan can help to re-discover all of the VM data store and the RDM presented to the ESXi host from the SAN array ?

Kind Regards,

Al

If you already have the host that you're rebuilding configured on the array (host assigned to a Storage Group and LUNs in the Storage group assigned to the host), you should remove the host from the storage group first, then de-register that host or the old host name and IP address will persist to the HBA's WWN and when the new host is brought online, it may register incorrectly.

glen

ESXi 5.1 should have navisphere agent built-in also. I believe re-scan the HBA bus can re-discover all the LUNs assigned to the host even the host information has not been synced to the array's initiator record because the rescan operates at the SCSI layer (over FC protocol), while the initiator record is only useful to the Unisphere management console to better understand the host configuration.

Cool, so on this case rebuilding the ESX server into ESXi 5.1u1 should be straight forward without having to worry about reconfiguring the Storage Setting from the Unisphere ?

Kind Regards,

Al

--

Thanks for the calrification Glen.

noted down

Cool,

Thanks Steve, that does make sense assuming the server hardware remains the same, then the HBA card WWN will also the same and should be registered already in the Unisphere.