topic Re: EVA5000 cannot communicate with controller in HPE EVA Storage

EVA5000 cannot communicate with controller

jorgen325 — Fri, 06 Aug 2010 18:05:08 GMT

I have an EVA5000. Mirror broke so I had to start from scratch. Have Server 2003 and Command View, SSSU.
I am going nuts trying to troubleshoot the controller. I do not anything about how it is configured. I inherited this problem and the EVA itself hasn't been used in at least a year. What can I do to troubleshoot this?

Re: EVA5000 cannot communicate with controller

jorgen325 — Fri, 06 Aug 2010 18:08:22 GMT

SSSU: ls system "No Systems Found"
CV: Operation Failed! No controllers found

Re: EVA5000 cannot communicate with controller

Rob Leadbeater — Mon, 09 Aug 2010 10:38:38 GMT

Hi,

Do you know what state the EVA5000 is in itself ?

If it is working correctly, the two controllers should be diplaying the EVAs name and its World Wide number.

When you said that the "mirror broke" I assume you mean that you've had to rebuild the Management Server from scratch. The version of Command View has to be compatible with the version of VCS on the controllers...

Cheers,
Rob

Re: EVA5000 cannot communicate with controller

jorgen325 — Mon, 09 Aug 2010 14:32:09 GMT

Yes. Mirror broke on Management App.
They gave me the latest version before licensing. Version: 6.0.0.193

I have not set a name on the controller.
Storage system name:
I have entered the WWN manually on the controllers.

I have not plugged in the ethernet on the controllers. I don't know the IP but I suspect I can guess the Network address and then scan for IP's.
Do I even need ethernet on the controllers? Shouldn't the fibre be enough?

How can I find out what version is compatible with the controllers?

Is there a way to get into the Controllers and change settings?

Thank you for your help (points given!)

Re: EVA5000 cannot communicate with controller

Uwe Zessin — Mon, 09 Aug 2010 14:48:11 GMT

The EVA-5000 controllers do not have 'ethernet'-ports. If I remember correctly, there are two RJ45-ports:

- UPS, which is not used

- EAB (not sure what it is really labelled). It's been some time I've touched one and there have been two 'generations' of the EVA-5000 with different controller modules.

EAB is for the Enclosure Address Bus and used to assign a unique address to each enclosure. The controllers are linked by an Y-cable to the bus and any disk drive enclosure uses a simple RJ45/RJ45 cable.

> I have not set a name on the controller.

This is the 'cell' or 'system' named and assigned when 'initializing' the meta-data from Command View EVA.

> Shouldn't the fibre be enough?

The EVA-5000 and all others except the 4400 can _only_ be managed 'in-band' via Fibre Channel.

> How can I find out what version is compatible with the controllers?

You can use the up/down/left/right buttons on th controller O)perator C)ontrol P)anel to find out the firmware revision. The firmware is named V)irtual C)ontroller S)oftware (VCS) and the entry should be named similar. From there we can look into the compatibility tables.

Re: EVA5000 cannot communicate with controller

jorgen325 — Mon, 09 Aug 2010 14:55:18 GMT

Sorry, by ethernet, I meant RJ-45.

The controller displays WWN and Storage System Name,

CSV: HSV V3028

Again, Thank You!

Re: EVA5000 cannot communicate with controller

Uwe Zessin — Mon, 09 Aug 2010 15:12:45 GMT

OK. I've looked and VCS V3.028 is supported with CV-EVA V6.0, 6.0.1 + 6.0.2.

Let's go back and do some basic checks:

- the controllers have logged in on the Fibre Channel switch(es)? Which switch models are you using? Can you see their WWPNs?

- the server is logged in on the FC switch(es), too?

- any zoning on the switches that can prevent the management server from talking to the EVA?

Re: EVA5000 cannot communicate with controller

jorgen325 — Mon, 09 Aug 2010 15:46:49 GMT

Here's the thing. I don't know much about the fibre switches. I was able to get in using a null modem cable and the default login.

I have no idea how to configure them though I have been looking through a ton of documentation.

Can I plug the fibre into the controllers directly and bypass the switches just so I know that the controllers work properly?

If not, then I probably have a lot of reading to do on those switches...

Re: EVA5000 cannot communicate with controller

jorgen325 — Mon, 09 Aug 2010 15:51:40 GMT

Have two: HP StorageWorks SAN Switch 2/32

Everything is configured for redundancy.
Dual switches, dual controllers...

Re: EVA5000 cannot communicate with controller

Uwe Zessin — Mon, 09 Aug 2010 16:13:20 GMT

A 'direct connect' requires that the EVA and the server talk Fibre Channel Arbitrated Loop (FC_AL) protocol.

It must be changed via the controller OCP and on the driver configuration of the Windows server. How to make the change on the server depends on the type of FC adapter.

Re: EVA5000 cannot communicate with controller

jorgen325 — Mon, 09 Aug 2010 16:26:38 GMT

Emulex. Wonder if I can use HBAnywhere for that..

Re: EVA5000 cannot communicate with controller

Rob Leadbeater — Tue, 10 Aug 2010 06:37:06 GMT

Hi,

If you can log on to each of the switches and issue these two commands:

switchShow
cfgShow

and post the output here, that should allow us to see enough of the configuration to work out what needs to be connected where...

Cheers,
Rob

Re: EVA5000 cannot communicate with controller

jorgen325 — Wed, 11 Aug 2010 18:04:57 GMT

switch config (on switch 2)
atlsanswitch02:admin> switchshow
switchName: switch02
switchType: 12.4
switchState: Online
switchMode: Native
switchRole: Principal
switchDomain: 1
switchId: fffc01
switchWwn: 10:00:00:60:69:90:8e:4f
zoning: ON (eva_san_20050608)
switchBeacon: OFF

Area Port Media Speed State
==============================
0 0 id N2 Online F-Port 50:00:1f:e1:50:05:8b:4d
1 1 id N2 Online L-Port 1 public
2 2 id N2 No_Light
(no light 3- 14)
15 15 id N2 No_Light
16 16 id N2 Online F-Port 50:00:1f:e1:50:05:8b:48
17 17 id N2 No_Light
18 18 id N2 Online G-Port
19 19 id N2 No_Light
(20-31)

Re: EVA5000 cannot communicate with controller

jorgen325 — Wed, 11 Aug 2010 18:08:54 GMT

switch2 cfgshow attached.

So it looks heavily zoned.

Re: EVA5000 cannot communicate with controller

Uwe Zessin — Wed, 11 Aug 2010 18:12:33 GMT

> zoning: ON (eva_san_20050608)

Zoning is enabled. To turn it off:
: cfdisable
: cfgclear
: cfgsave

:0 0 id N2 Online F-Port 50:00:1f:e1:50:05:8b:4d

Second EVA controller.

> 1 1 id N2 Online L-Port 1 public

A server whose port is runnig public FC_AL protocol.

The "nsShow" command will give us a better clue what is connected.

> 16 16 id N2 Online F-Port 50:00:1f:e1:50:05:8b:48

First EVA controller

> 18 18 id N2 Online G-Port

A port that has not logged in properly.
Maybe this helps:
: portdisable 18
wait a minute
: portenable 18

Re: EVA5000 cannot communicate with controller

Rob Leadbeater — Wed, 11 Aug 2010 18:17:50 GMT

Do you need to keep the zoning ?

I'm guessing probably not, however if you do, then the EVA controllers look to be plugged into the wrong switch.

Also, the switchShow output shows that the management server isn't logging into the SAN.

Cheers,

Rob

Re: EVA5000 cannot communicate with controller

jorgen325 — Wed, 11 Aug 2010 19:03:26 GMT

No, do not need to keep, looks like it was from the last company. I will probably be configuring a new zone, but would be thrilled just to get it communicating first.
Will go try this now.

Thanks again!

Re: EVA5000 cannot communicate with controller

jorgen325 — Wed, 11 Aug 2010 19:07:54 GMT

atlsanswitch02:admin> nsshow
{
Type Pid COS PortName NodeName TTL(sec)
N 010000; 3;50:00:1f:e1:50:05:8b:4d;50:00:1f:e1:50:05:8b:40; na
FC4s: FCP
PortSymb: [36] "HSV110 (C)COMPAQ - NO SCELL - CR0A3E"
Fabric Port Name: 20:00:00:60:69:90:8e:4f
Permanent Port Name: 50:00:1f:e1:50:05:8b:4d
NL 010101; 2,3;10:00:00:00:c9:41:df:24;20:00:00:00:c9:41:df:24; na
FC4s: FCP
PortSymb: [40] "Emulex LP9002 FV3.82A1 Dv5-2.30a2 KTPEVA"
NodeSymb: [40] "Emulex LP9002 FV3.82A1 Dv5-2.30a2 KTPEVA"
Fabric Port Name: 20:01:00:60:69:90:8e:4f
Permanent Port Name: 10:00:00:00:c9:41:df:24
N 011000; 3;50:00:1f:e1:50:05:8b:48;50:00:1f:e1:50:05:8b:40; na
FC4s: FCP
PortSymb: [36] "HSV110 (C)COMPAQ - NO SCELL - CR0A3E"
Fabric Port Name: 20:10:00:60:69:90:8e:4f
Permanent Port Name: 50:00:1f:e1:50:05:8b:48
The Local Name Server has 3 entries }

Re: EVA5000 cannot communicate with controller

jorgen325 — Wed, 11 Aug 2010 19:45:18 GMT

I believe that did it!

Now I have to learn how to use the damn thing...

Re: EVA5000 cannot communicate with controller

jorgen325 — Wed, 11 Aug 2010 20:34:42 GMT

Clear Zoning.