Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have 3 esx 4.1 hosts connected to HP EVA 4400 StorageWork. All host can see 6 datastore, LUN1 to LUN6, 1TB for each datastore. Recently I add another esx 4.1 host but unfortunately this now host cant see the existing datastore. I try to rescan the datastore many times but still failed to see the datastore.

FYI I've already created new host using HP Command view for the new esx host and present all 6 vdisk/LUN to the new host. I've also install vmware-esx-drivers-scsi-bfa-400. driver for FC adapter (dual port), the same driver for another 3 esx hosts, but still failed to see the datastore. What most probably the problem?

Does anybody face the same problem like this before? Please advice..

share|improve this question
Do you have the right WWN configured for the newly added host? – Shane Madden Dec 19 '11 at 5:30
Yup. I just choose the Port WWN from the drop down box then I add additional port for redundancy to the host. The FC adapter Port WWN for the host is 4. Then I present the Vdsik to the host (6 Vdisk) and then when I rescan for datastore at ESX node it still failed to see the datastore. By right if there's no issue related to connectivity the ESX node will automatically detect all current datastore unless if we want to add new datastore. – Syairus Dec 19 '11 at 5:48
How is your FC switching setup/configured? – Chopper3 Dec 19 '11 at 14:41
up vote 5 down vote accepted

Start off by triple checking your zoning and LUN masking. I know you did it already, but if you made a typo or something, that would do this.

  • You need to ensure that your switch has a zone containing all the front end ports for your EVA as well as the HBA for your new VMWare server. Most FC places have two switches, so you'll want to see that zone on each switch.
  • Once that's done, go back into the EVA and triple check that the vdisks are being allocated to the new server and that the new server has the right WWNs in it.

Once this has been checked, reboot your VMWare server, and press ctrl-q during the boot up to access the qlogic HBA directly. From this interface, you can see on each card and each port on that card what devices are visible. If you can't see the HP EVA, it's a FC switch, card, or cable problem. If you can see it, but can't see the LUNs when you go "into" it, then it's an EVA problem. If you can see them but you can't see the datastore, then it's a VMWare problem.

If it's a switch problem, start off by ensuring the ports your server is plugged into are on. If they're on, ensure they're not in the wrong mode. You want an F port, not an E port or FL port. Make sure that the port your new ESX server is plugged into is blinking, and then go check the WWN logged into that port. You can validate this against the zoning on the switch, as well as the LUN masking on the EVA.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.