HPE EVA Storage
1753789 Members
7622 Online
108799 Solutions
New Discussion юеВ

EVA5000 cannot communicate with controller

 
SOLVED
Go to solution
jorgen325
Frequent Advisor

Re: EVA5000 cannot communicate with controller

Emulex. Wonder if I can use HBAnywhere for that..
Rob Leadbeater
Honored Contributor

Re: EVA5000 cannot communicate with controller

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
jorgen325
Frequent Advisor

Re: EVA5000 cannot communicate with controller

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)
jorgen325
Frequent Advisor

Re: EVA5000 cannot communicate with controller

switch2 cfgshow attached.

So it looks heavily zoned.
Uwe Zessin
Honored Contributor

Re: EVA5000 cannot communicate with controller

> 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
.
Rob Leadbeater
Honored Contributor

Re: EVA5000 cannot communicate with controller


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

jorgen325
Frequent Advisor

Re: EVA5000 cannot communicate with controller

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!
jorgen325
Frequent Advisor

Re: EVA5000 cannot communicate with controller

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 }
jorgen325
Frequent Advisor

Re: EVA5000 cannot communicate with controller

I believe that did it!

Now I have to learn how to use the damn thing...
jorgen325
Frequent Advisor

Re: EVA5000 cannot communicate with controller

Clear Zoning.