HPE EVA Storage

EVA4400 ignoring Emulex and Qlogic FC-HBAs from new 8/40 SAN switch1

 
Sean Paul
New Member

EVA4400 ignoring Emulex and Qlogic FC-HBAs from new 8/40 SAN switch1


I have an Eva4400 with the 2 port controllers in it, not the Brocade switches. Long story short, just connected a new 8/40 StorageWorks SAN switch with mixture of 14 Emulex & Qlogic FC-HBAs connected to it. EVA doesn't see the WWN's available via the new SAN to configure into hosts.

SAN Fabric is flat....that is none of the SAN switches are connected to one another. All SAN switches denoted below are HP StorageWorks:

On EVA:
In controller 1, port 1...I have a 4/16 connected. In Controller 1, port 2...I have a 8/40 connected. In Controller 2, port 1..I have an 4/24 connected. In Controller 2, port 2...I have the new 8/40 connected.

All other SAN switches are working and have vDisks presented to the FC-HBAs connected to them.

On the new 8/40 switch...I can see the WWNs of the Emulex and Qlogic cards, I can also see on Port 0 the WWN of the EVA4400 controller 2, port 2. Via Command View on the EVA, I can see that Controller 2, Port 2 is logged into Fabric and 'good'.

Any ideas why the FC-HBA WWNs from the new 8/40 SAN aren't showing up on the EVA? I've verified the new 8/40 is running the same f/w and zoning policy as the other switches.

Any suggestions would be welcomed....
9 REPLIES 9
Johan Guldmyr
Honored Contributor

Re: EVA4400 ignoring Emulex and Qlogic FC-HBAs from new 8/40 SAN switch1

Hi!

What is your zoning policy?

Unless you are using "DID, PID" zoning, you should not have the same zoning on this switch.

Or is the zoning policy referring to the "allow all" policy?
Sean Paul
New Member

Re: EVA4400 ignoring Emulex and Qlogic FC-HBAs from new 8/40 SAN switch1

Here is our Zoning policy that all the SAN switches follow (this one is specific to SAN69):

san69:FID128:admin> cfgshow
Defined configuration:
cfg: prime port01; port02; port03; port04; port05; port06; port07;
port08; port09; port10; port11; port12; port13; port14;
port15; port16; port17; port18; port19; port20; port21;
port22; port23; port24; port25; port26; port27; port28;
port29; port30; port31; port32; port33; port34; port35;
port36; port37; port38; port39
zone: port01 169,1; 169,0
zone: port02 169,2; 169,0
zone: port03 169,3; 169,0
zone: port04 169,4; 169,0
zone: port05 169,5; 169,0
zone: port06 169,6; 169,0
zone: port07 169,7; 169,0
zone: port08 169,8; 169,0
zone: port09 169,9; 169,0
zone: port10 169,10; 169,0
zone: port11 169,11; 169,0
zone: port12 169,12; 169,0
zone: port13 169,13; 169,0
zone: port14 169,14; 169,0
zone: port15 169,15; 169,0
zone: port16 169,16; 169,0
zone: port17 169,17; 169,0
zone: port18 169,18; 169,0
zone: port19 169,19; 169,0
zone: port20 169,20; 169,0
zone: port21 169,21; 169,0
zone: port22 169,22; 169,0
zone: port23 169,23; 169,0
zone: port24 169,24; 169,0
zone: port25 169,25; 169,0
zone: port26 169,26; 169,0
zone: port27 169,27; 169,0
zone: port28 169,28; 169,0
zone: port29 169,29; 169,0
zone: port30 169,30; 169,0
zone: port31 169,31; 169,0
zone: port32 169,32; 169,0
zone: port33 169,33; 169,0
zone: port34 169,34; 169,0
zone: port35 169,35; 169,0
zone: port36 169,36; 169,0
zone: port37 169,37; 169,0
zone: port38 169,38; 169,0
zone: port39 169,39; 169,0

Effective configuration:
cfg: prime
zone: port01 169,1
169,0
zone: port02 169,2
169,0
zone: port03 169,3
169,0
zone: port04 169,4
169,0
zone: port05 169,5
169,0
zone: port06 169,6
169,0
zone: port07 169,7
169,0
zone: port08 169,8
169,0
zone: port09 169,9
169,0
zone: port10 169,10
169,0
zone: port11 169,11
169,0
zone: port12 169,12
169,0
zone: port13 169,13
169,0
zone: port14 169,14
169,0
zone: port15 169,15
169,0
zone: port16 169,16
169,0
zone: port17 169,17
169,0
zone: port18 169,18
169,0
zone: port19 169,19
169,0
zone: port20 169,20
169,0
zone: port21 169,21
169,0
zone: port22 169,22
169,0
zone: port23 169,23
169,0
zone: port24 169,24
169,0
zone: port25 169,25
169,0
zone: port26 169,26
169,0
zone: port27 169,27
169,0
zone: port28 169,28
169,0
zone: port29 169,29
169,0
zone: port30 169,30
169,0
zone: port31 169,31
169,0
zone: port32 169,32
169,0
zone: port33 169,33
169,0
zone: port34 169,34
169,0
zone: port35 169,35
169,0
zone: port36 169,36
169,0
zone: port37 169,37
169,0
zone: port38 169,38
169,0
zone: port39 169,39
169,0
Johan Guldmyr
Honored Contributor

Re: EVA4400 ignoring Emulex and Qlogic FC-HBAs from new 8/40 SAN switch1

"On the new 8/40 switch...I can see the WWNs of the Emulex and Qlogic cards, I can also see on Port 0 the WWN of the EVA4400 controller 2, port 2. "

Does that say that the EVA Controller 2 Port 2 is connected to the new 8/40 on port 0?

In the zoning you pasted there is no port 0 mentioned. Well, it says "169,0". Maybe you need to set this to "69,0" for switch69 or whatever the new 8/40 is called?
Sean Paul
New Member

Re: EVA4400 ignoring Emulex and Qlogic FC-HBAs from new 8/40 SAN switch1

Does that say that the EVA Controller 2 Port 2 is connected to the new 8/40 on port 0?

In the zoning you pasted there is no port 0 mentioned. Well, it says "169,0". Maybe you need to set this to "69,0" for switch69 or whatever the new 8/40 is called?

Johan,

Correct....the EVA Controller 2 Port 2 is connected to the new 8/40 on port 0. On the SAN Port 0 via 'switchshow', I can see the WWN of the EVA Controller 2 Port 2.

The above zoning policy was created for us by a HP Customer System Architect. This SAN switch's id is '69'....hence the '169' that you are referring to in the zoning above.

As I understand it, the uplink port from the 8/40, in this case...port 0, does NOT get zoned.....hence, it's not zoned in the policy stated above.
Sean Paul
New Member

Re: EVA4400 ignoring Emulex and Qlogic FC-HBAs from new 8/40 SAN switch1


Interesting tidbit of info....I connected Port 0 of SAN69 to a different EVA4400. SAN69 Port 0 was connected to EVA2, now it's connected to EVA3.

EVA3 had Controller 1 Port 0 connected to another 8/40 SAN switch but the other 3 ports were open.....now all the WWNs of the FC-HBA cards connected to SAN69 show up on EVA3.

So, the question is....how many SAN switches can be connected to an EVA4400 that has the controllers with just 2 ports on them?
Johan Guldmyr
Honored Contributor

Re: EVA4400 ignoring Emulex and Qlogic FC-HBAs from new 8/40 SAN switch1

Hey,

if your SAN switch domain ID is 69, then I'm pretty sure you should have ID 69 in the zone config.
Johan Guldmyr
Honored Contributor

Re: EVA4400 ignoring Emulex and Qlogic FC-HBAs from new 8/40 SAN switch1

"169, 0" means "Domain ID, Port ID" or DID, PID.

You can find switch69's domain id by typing 'switchshow' in the CLI.
Sean Paul
New Member

Re: EVA4400 ignoring Emulex and Qlogic FC-HBAs from new 8/40 SAN switch1

The domain ID of all our SAN switches is preceded by a '1'.....so SAN69 is DID 169, SAN70 is DID 170, etc. All this was set up before I started working here....and I've been told "that's how it's done".
Johan Guldmyr
Honored Contributor

Re: EVA4400 ignoring Emulex and Qlogic FC-HBAs from new 8/40 SAN switch1

OK, then the zoning should be OK.

"Interesting tidbit of info....I connected Port 0 of SAN69 to a different EVA4400. SAN69 Port 0 was connected to EVA2, now it's connected to EVA3.

EVA3 had Controller 1 Port 0 connected to another 8/40 SAN switch but the other 3 ports were open.....now all the WWNs of the FC-HBA cards connected to SAN69 show up on EVA3."

Did you try to restart the controller in EVA2 when that was connected to switch69,port 0?
Maybe that port is not behaving very well, even though it is in a logged in state. Maybe the fabstateshow or fabriclog --show could tell you more about the port.

Does the EVA2 logs say anything when the port is connected to switch69,0?