topic Re: EVA - New Configuration in HPE EVA Storage

EVA - New Configuration

Karthik S S — Tue, 17 Feb 2004 09:32:09 GMT

Hi,

We received a new EVA and are trying to configure the same. As per the document we have input the WWN number through the OCP. After entering we are getting a Flashing message on the OCP saying,

WWN: xyz zyz ..

The connectivity between the HSV100s and the Disk enclosure seems to be OK ( it came pre wired).

As per the doc. we are supposed get some Storage System name once we enter the WWN.

How do I proceed?? Pl. help.

Thanks,
-Karthik S S

Re: EVA - New Configuration

Andrew_168 — Tue, 17 Feb 2004 09:45:23 GMT

Hi,
You have completed the first step, all further configuration takes place using the Management Appliance. Connect this to the fabric, login and start Command View EVA, just bear in mind if the EVA is running VCS 3.010 you may need to update command view EVA on the appliance to 3.1.

Re: EVA - New Configuration

Karthik S S — Tue, 17 Feb 2004 11:02:49 GMT

Hi,

Thanks for those inputs.

The VCS version I have is 3.010. And the CV EVA version is 2.1. When I tried doing a discovery of devices it gave me a error message saying that No controllers could be found. Is it due to the version problem?? Is it must to have CV EVA 3.1 to configure EVA3000/VCS 3.010??

Pl. Clarify,

Thanks
Karthik S S

Re: EVA - New Configuration

Karthik S S — Wed, 18 Feb 2004 00:10:22 GMT

Any update??

-Karthik S S

Re: EVA - New Configuration

Uwe Zessin — Wed, 18 Feb 2004 00:48:06 GMT

OK, here are some tips to manage the discovery:

- wenn CV-EVA doesn't see any EVAs it shows a [discovery] button as you have already seen, right? Pressing it does sometimes work...

- If not, there is another [discovery] button that you can reach through "agent option". And then [Discover storage systems]. I don't know if they are the same or not, but I found out that it is worth a try.

- As the next option you can try to restart CV-EVA. From the entry screen select "Settings" and (Manage Tools). You see a list of applications. Mark the radio button on the left side of 'command view eva' and you should see that the 'Tasks' column allows you to enter the 'Stop' task. Press it, then the green 'Next' button on he bottom of the screen. Wait until it is stopped which can take some time and the press 'Finish'. Now select 'command view eva' again, but now choose 'Start' task. After the restart, please wait some time (I'd say a minute) so that the task can settle and then go back to "Devices"->"command view eva".

Re: EVA - New Configuration

Orrin — Wed, 18 Feb 2004 00:48:57 GMT

Hi Karthik,

This is normal, when you enter the WWN number on the HSV110's you then have to enter the checksum.

Assuming you have done that, you then have to assign a storage name through the SMA.
Only then is the configuration saved. Until then if you power off the HSV110 and power Up , you have to enter the WWN and Checksum again.

On the SMA click on the discover devices, then through the Command view EVA V3.0 ( If you are not at this version upgrade to this version before you continue). Select Uninitialised storage System from the HSV Storage Network Folder in the left Pane.
Click on Initialise on the properties page.
( At thi spoint if the SMA does not have a liscence loaded for the EVA you are prompted to enter a liscence key)

The enter a name in the text box to identify the storage system sontroller.

Enter the number of disk to include in the default disk group ( All is good )

Select data protection level and then Finish. At this point configuration is saved and you are good to go.

The next steps will be to get the WWN of the HBA's on the hosts and use them to configure the hosy connections. After that you should create your Vraid's and you're good to go.

Hope this helps.
Regards,
Orrin.

Re: EVA - New Configuration

Karthik S S — Wed, 18 Feb 2004 00:56:30 GMT

Uwe/Orrin,

I think the problem is due to the CV EVA version. I am in touch with our storage team to get the appliance installed with CV EVA 3.1.

As you suggested I tried doing a manual discover but still it couldn't find the controller.

Thanks,
Karthik S S

Re: EVA - New Configuration

Karthik S S — Wed, 18 Feb 2004 00:59:54 GMT

All the connections from the EVA and EMA appear to be proper. Infact we have only one SAN switch [It is not connected to any exisiting SAN but a standalone(?) switch] to which all the 4 ports of the EVA and 1 port of the SMA are connected. I have not configured any zoning yet. Is it required to configure zoning also?? I thought it comes into picture only when you need to secure the storage/LUNs across different server but not for the initial setup.

-Karthik S S

Re: EVA - New Configuration

Uwe Zessin — Wed, 18 Feb 2004 01:54:06 GMT

Karthik,
is that a new switch with zoning cleared? What model?

LUN masking can (and I think should) be done completely on the EVA.

You use zoning to prevent too much/ the wrong ports from 'talking to each other'.

For filtering LUNs a switch needs the ability to look up the SCSI commands in the payload of the frame. Most switches simply cannot do that, but that's not a problem as the EVA has built-in LUN masking.

Re: EVA - New Configuration

Karthik S S — Wed, 18 Feb 2004 02:03:20 GMT

Yes that is a brand new switch. All I have done with that switch is to assign a IP to it.

-Karthik S S

Re: EVA - New Configuration

Karthik S S — Thu, 19 Feb 2004 06:56:32 GMT

Hi,

Finally it turned out to be a FC cable issue. We had to replace the LC-SC cable that was connected from SMA to the FC Switch. CV EVA was able to discover the EVA and I created Diskgroups/Vdisks all is fine :-)

Now I need to connect host machines and try presenting the vdisks to the hosts.

Thanks,
Karthik S S

Re: EVA - New Configuration

Uwe Zessin — Thu, 19 Feb 2004 07:14:18 GMT

Congratulations on your progress! Sometimes it is a simple problem that makes us stumble.

How did you diagnose the problem? Didn't the switch show a link?

Re: EVA - New Configuration

Karthik S S — Thu, 19 Feb 2004 07:25:31 GMT

Yeah .. intermittantly the link was going off. And also the cable what we had was locally purchased and was not a branded one ..!!

Thanks for your help ... keep watching this space .. I will be back to bug you again :-)

I have posted this success at,
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=427387

-Karthik S S

Re: EVA - New Configuration

Mike Naime — Thu, 19 Feb 2004 23:11:07 GMT

That sounds like a corporate penny pincher to me. Spend 1/2 million on the hardware, and then try to save 5$ by purchasing cheap cables.

I keep fighting my network folks over the 50 Micron VS 62.5 Micron fibre cables.

Fibre channel wants 50 Micron. Network wants 62.5

Re: EVA - New Configuration

Orrin — Thu, 19 Feb 2004 23:41:33 GMT

COngratulations!! Karthik...

Good going.

Sorry, I couldn't follow the forum due to work.

Best of Luck.. see you online again sometime.

Regards,
Orrin.

Re: EVA - New Configuration

Karthik S S — Fri, 20 Feb 2004 00:23:05 GMT

Hi Mike,

It was definitely not a cost cutting measure from the corporate .... but since the shipment of the FC cables got delayed by a week and we wanted to have the EVA up and running we had to settle for that second quality cable .... :-( ...

Thank you Orrin ...

-Karthik S S

Re: EVA - New Configuration

Uwe Zessin — Fri, 20 Feb 2004 15:30:37 GMT

Mike, I'm curious:
which network installations require 62.5 today? Or is that some, well, 'backward' people?

During one of my EVA installs last year I stumbled over such an electrician. I did call the european connectors 'american trash'. When we sent them the required couplings (they are 32 ampere single phase, which is not that common here in Germany) he refused to install them because they were missing the 'VDE' sign. VDE was a german authority, whose standards were replaced by european regulations just, gasp, 2 years ago!

Re: EVA - New Configuration

Uwe Zessin — Fri, 20 Feb 2004 15:57:09 GMT

Oops. Of course it wasn't me, who said bad things about the connectors - it was the electrician...

Re: EVA - New Configuration

Karthik S S — Fri, 20 Feb 2004 16:05:38 GMT

Hi Guys,

I even created a vDisk and presented it to a host. But still facing lots of problem with securepath/vdisk presentation. We have a RP8400 with 4 cell single hard partition that is configured with 4 virtual partitions. I am facing a strange problem that with some vPars the EVA vdisks are not getting recognized (even after presenting them to that particular host). FC link from the vPar to the switch are proper. Even a "ioscan -f" shows a list of HSV devices but when you do a "ioscan -fnC disk" it does not show the vDisk. Also "spmgr display -u" reports that no vDisks are presented to the host. I tested the follwoing things,

1. vDisk presentation on EVA.
2. Associated host WWN to the vDisk
3. FC cable and Link

all these are proper.

Have any of you configured EVAs with vPars?? Are there any known issues?? (I have installed Jun 2003 App. Pack and Dec 2003 HW enablement pack along with the patches that are required for the secure path 3.0)

Thanks,
Karthik S S

Re: EVA - New Configuration

Mike Naime — Sat, 21 Feb 2004 00:49:23 GMT

Well, in this area. (Kansas City) the local contractor that does our patch panel installation (Watcher Electric) says that they are using 62.5 fibre for network patch panels all over the city. I could care less what they are using at other sites, I care about my site.

We are adding a new 6000+ square foot data center that I am supposed to be able to put 2 new EVA's into on April 2nd (If they keep to the schedule). Before we had several meeting about the subject, our Network manager wanted to install 62.5 all over the place. We finally got our Network manager to agree that we needed 50 Micron Fibre after we got supporting documentation from both HP/Compaq, Hitachi, and Brocade stating that we needed 50. He still contends that we could function on the 62.5 stuff, but finally agreed that they would install 50 for our SAN patch panels, and use 62.5 for the network gear.