Problem with Vdisk Presentation

[Miguel Ustariz]

We have an EVA3000 with HSV100 VCS 3.020,a HP Storageworks switch 2/8V with firmware 4.2.0b, a DL380G3 with Win2003 SP1 and FC2214 with windows drives 9.1.3

We installed CV 4.0 and we can define vdisks without problem. Also, we can present to the machine in CM and all OK.

BUT, when we rescan in disk management in the Win2003 machine (that is the same where CM was installed), we can not see the vdisk!!!

Thanks for your help

[Uwe Zessin]

What does CM stand for?

[Ivan Ferreira]

I think that CM is CV. Ensure that your OS type in the host definition is set to windows. What if you reboot the server?

[Miguel Ustariz]

You ara wright! Its CV, no CM. I put the OS to Windows and reboot the server and the same problem exist!!!

[NathanK]

Same thing happens to me. I was going to run some IOMeter stuff, but I couldn't present a lun from the EVA to my storage management appliance.

[Uwe Zessin]

Not surprising, as the true SMA (Storage Management Appliance) uses a 'non-standard' device driver and the configuration is set so that no LUNs > 0 are passed to the upper layers, if I remember correctly.

In this thread we are talking about a GPS (General Purpose Server) that uses a plain driver (9.1.0.13, I'd say although Miguel wrote 9.1.3).

[Mark Poeschl_2]

Miguel - do you have zoning configured in your switch? That could prevent communication.

[Uwe Zessin]

Didn't he write that he can manage the EVA? Zoning usually disrupts _all_ comunication - can you even set LUN filters in the 2/8V?

[Mark Poeschl_2]

Not if the zoning was such that SMA could see the EVA, but not the server.

[Miguel Ustariz]

No zone, no LUN filter. The only change in the 2/8v was IP Address

[Ivan Ferreira]

This may sound stupid but, are you sure that the HBAs that you selected in CV when creating the host are the right HBAs for that server?

[Miguel Ustariz]

Yes, the same HBA wwn in CV is the same that we see in the machine

[Matt Tourney]

Miguel, do the HSV100 controllers show up in your server's Device Manager under the SCSI devices section? If everything is zoned correctly, I believe you should see 4 instances of the HSV100 controllers (Command Console LUN over all 4 ports) even before you actually present a vdisk. If you don't see that in Device manager, then you are having a problem with basic FC connectivity.

Double-check your WWNs and zoning configuration on the switches. Then double-check the WWNs in the host port configuration in CommandView.

By the way, you also need to consider upgrading your VCS code. 3020 is old and is known to have some problems if I recall. New version is 4.001 and just came out, although I recommend you go to 3.028 first.

[Sheldon Smith]

If the Windows system is running 2003 and not 2000, then it is definitely NOT a Storage Management Appliance.
The SMA *only* runs a stripped-down version of Windows 2000.

[Miguel Ustariz]

Hi:

Is necessary to connect all 4 FP ports to the switch? We have only one switch (now with 5.xxx firmware). We tested with an emulex HBA (FCA 2101) and not work!!!. The same problem again!!!

[Matt Tourney]

Miguel

Yes, you absolutely have to connect all of the EVA 3000 host side ports to your SAN switch. It is possible that you cannot access the port through which your vdisk is currently presented.

Matt

[Miguel Ustariz]

OK Mat,

How I can make the zoninig in my swicht with 4 connection fron the EVA, 1 connection fron the machine with CV and 3 conection from 3 windows host (all single path)?

[Matt Tourney]

Create a zone for each server that includes that server's HBA and all 4 of the ports of the EVA 3000.

If you are unsure of how to do that, check the Administrator's guide for your SAN switch.

[Miguel Ustariz]

HELP!!!!!!!
when we try to connect all the 4 ports, one of the controllers can not boot!!!!!!!!!!!!!
It stop in "boot config Ram test passed"
HELP!!!!!!! URGENT!!!!!! Some solution???????

[Miguel Ustariz]

False alarm. I recover the lost controller