Persistent Static LUN mappings

[wade001]

I have an EqualLogic SAN attached to my Vsphere cluster via qlogic 4062c ISCSI HBA's. We frequently create and remove LUNs to support our VM environment. Currently every time a LUN is removed the static discovery target information remains, this information does not get removed with an HBA rescan. The entries must be manually removed or we received error notifications from our EqualLogic concerning attempts to access the removed LUNs from the HBAs connecting to the SAN.

This manual process must be performed over several HBA ports and is tedious and time consuming. Is there an automated approach to cleaning up these entries? A HOST reboot does remove the static entries however this seems to be an unreasonable approach to this issue. We have talked to VMsupport , EqualLogic and Qlogic and this seems to be the consensus approach for resolving the issue. If there is a more graceful approach to cleaning these entries it would be greatly appreciated.

[steffan]

We have the exact same issue. We installed ESX 4 Update 1 and that solved the issue. Can you agree with that?

But the must annoying is, that volumes has to be removed seperately. We normally remove the ISCSI connection on the ESX to the LUN on every Qlogic HBA, before removing the volume on the Equallogic Array. It takes severel minutes, hours to remove volumes from esx servers....

Why is it not possible to mark more than one volume at a time? And why is it not possible to do that global for a amount of ESX servers?

Kind regards,

Steffan