Storage Network set up f

[Abdelhadi Nassif]

I am looking for a document to show me a step by step configuration of an HP EVA 4400 storage network.
The environment consists of an C7000 enclosure with half and full length blades, two interconnect switches connecting to two brocade switches. I am having problems figuring out how to connect it all together to have evrything redundant (multipathing).

Thanks

[Torsten.]

You basically have 2 SANs. Each server blade connects to both SANs via the 2 brocade switches. Same for the EVA. First you show create a zone on the switch to make the EVA visible to the server, then let the server scan the SAN in order to make the server WWN visible to the EVA. Now create a vdisk and present it to the server.

[Abdelhadi Nassif]

Hi;
It all sounds good, but I need to start at the beginning.
1: The interconnect on the backplane need to connect to the brocades for redundancy. Say interconnect port 1 connecting to a port on the brocade switch 1 and the interconnect port 2 connecting to the second brocade switch for redundancy, The same applied to the other interconnect.
I read that this set up is not supported.

2: I am a kind of the deep end here and need some step by step guidance to zone and present LUNs to the blades

I can go to the other stuff once I can understand the physical and logical connections.

Tx

[Johan Guldmyr]

OK.

Please clarify which switches you have in the c-class and the two standalone switches. Or do you have pass-through modules?
Do you have virtual connect?

Do you have embedded switches in the EVA4400 too?

Before you start connecting things: Have you checked firmware levels??

[Abdelhadi Nassif]

Hi;
There is a connect through on the baclplane (interconnect) each containing 4 port each which according to the documentation aggregate the traffic from the blade servers.

Then there are two external brocade switches. There are two connection from the brocades going to the SAN (EVA) one from each switch.

[Johan Guldmyr]

So in the back of the c7000 you have two brocade SAN-switches. These two should then be connected to the EVA? Correct? The EVA4400 is sometimes shipped with embedded SAN switches.

Switch A Port 17 -> CTRL A FP1
Switch B Port 17 -> CTRL A FP1

Switch A Port 18 -> CTRL B FP2
Switch B Port 18 -> CTRL B FP2

Should do it.

Then I guess you need to set up the port mapping in the c-class as well.

[Abdelhadi Nassif]

The brocades are not actually in the C7000. The enclosure ships with Interconnect switches. The brocades sit between the interconnect and the EVA. So I need to create zones (redundant) and map the LUNs to be seen by the appropriate servers.

When I create a zone, do I need to give it teh Interconnect switch port WWN or the EVA controller WWN ?
I am sure this is simple for someone who does this day in day out. I might not be desribing it in an easy way

[Johan Guldmyr]

The brocades are not actually in the C7000. The enclosure ships with Interconnect switches.

"Interconnect switches". So it is not a brocade? Ar they pass-through modules?

Same principle anyway.

In each zone you put the target and the initiator.

So the HBA port wwn and the EVA port wwn.

Brocade recommends 1 target and 1 initiator per zone.

[Torsten.]

>> The enclosure ships with Interconnect switches.


Any model or product name or number?

[Abdelhadi Nassif]

Just to understand the target is the SP WWN i.e the controller in the EVA and the initiator. What would the initiator be ? I don't want to make any assumption.

[Abdelhadi Nassif]

Not sure which type as I did not look for that information specifically.
I attach an artistic diagram of the current environment which may make things easier of what is to be achieved.

As for creating the zone, there is a gap in my knowledge.
I create an Alias
Create a zone and give it a SP1 WWN
Add any hosts that need to see the LUNs connected to SP1
Associate the zone with a port in the brocade

What I need to do is make sure that server only see the LUN associated with them.

[Abdelhadi Nassif]

Hi Guys, I am still waiting for suggestions. I am under pressure to get this sorted asap.

Thanks

[Johan Guldmyr]

Hi,

please log on to the OA and tell us what these "interconnect" devices are called.
It is relevant..

"Create a zone and give it a SP1 WWN"
What is SP1??? One of the host ports on one of the EVA controllers - FP1?

Target: EVA
Initiator: one wwpn on the server/hba

In a zone you put only the HBA port wwn and one of the port wwn of the EVA. Each FP/host port/front port on the EVA has a wwpn. Each controller has at least two host ports (but your drawing only shows 1 - why?).

If you zone it this way it will help you out with troubleshooting if you ever need that in the future.

Don't forget that you need to create zoning on both switches and that after you have created the zones, you need to save and enable the config.

[Abdelhadi Nassif]

Hi;

The SP is (service processor) the controller on the EVA. You are right, the controller has a PWWN and two WWNs and there are two controllers.

The switch on the back of the enclosure is an Virtual interconnect (VC) that HP uses to define profiles. It has a WWN per port and currently, there is only one por connected on each side as per the diagram.
My thinking is that the zonning will be as such:
On Brocade SW1

Zone_Server1(target Controller 1 PWWN, WWN1 for Server1 ) and add the VC1 port1 WWN as member to the zone. This will be path 1 to the target LUN1

On Brocade SW2
Zone_Server1 (Target Controller 1 PWWWN, WWN2 for Server1) and add VC2 port 1 WWN as member to the zone. This will be path 2 to LUN1

Finally, I need to chech how to spread the load between the prots in the VC.

I attach the current config for both switches

[Johan Guldmyr]

Hi!

The VC is an 'invisible step' between the blades and the SAN.
I do not think you need to define the wwpn of the VC uplink in the zones.

Only one .txt file attached.
I presume in the other config/fabric/san switch you have these EVA aliases:
EVA01_CLFP1
EVA01_CRFP1

[Abdelhadi Nassif]

Here is the second one. Yes, They are the controllers in teh EVA. The naming convention is not really great which has been an issue here as well.

Brocade Switch 2 config

COMFSWT02 172.xx.xx.xx

Defined configuration:
cfg: Fabric_B_cfg
BLADE01_EVA_B; BLADE02_EVA_B; B
BLADE05_EVA_B; BLADE13_EVA_B; C
COMVIRT01_EVA_B; COMVIRT02_EVA_
COMVIRT04_EVA_B; COMVIRT05_EVA_
zone: BLADE01_EVA_B
BLADE01_2; EVA01_CLFP2; EVA01_C
zone: BLADE02_EVA_B
BLADE02_2; EVA01_CLFP2; EVA01_C
zone: BLADE03_EVA_B
BLADE03_2; EVA01_CLFP2; EVA01_C
zone: BLADE04_EVA_B
BLADE04_2; EVA01_CLFP2; EVA01_C
zone: BLADE05_EVA_B
BLADE05_2; EVA01_CLFP2; EVA01_C
zone: BLADE13_EVA_B
BLADE13_2; EVA01_CLFP2; EVA01_C
zone: COMBACK04_EVA_B
comback04_2; EVA01_CLFP2; EVA01
zone: COMBACK04_MSA_B
comback04_2; msa_2
zone: COMVIRT01_EVA_B
comvirt01_2; EVA01_CLFP2; EVA01
zone: COMVIRT01_MSA_B
comvirt01_2; msa_2
zone: COMVIRT02_EVA_B
comvirt02_2; EVA01_CLFP2; EVA01
zone: COMVIRT02_MSA_B
comvirt02_2; msa_2
zone: COMVIRT03_EVA_B
comvirt03_2; EVA01_CLFP2; EVA01
zone: COMVIRT03_MSA_B
comvirt03_2; msa_2
zone: COMVIRT04_EVA_B
comvirt04_2; EVA01_CLFP2; EVA01
zone: COMVIRT05_EVA_B
comvirt05_2; EVA01_CLFP2; EVA01
alias: BLADE01_2
50:06:0b:00:00:c2:62:22
alias: BLADE02_2
50:06:0b:00:00:c2:62:2a
alias: BLADE03_2
50:06:0b:00:00:c2:62:2e
alias: BLADE04_2
50:06:0b:00:00:c2:62:32
alias: BLADE05_2
50:06:0b:00:00:c2:62:36
alias: BLADE13_2
50:06:0b:00:00:c2:62:26
alias: EVA01_CLFP2
50:01:43:80:02:5c:0d:e9
alias: EVA01_CRFP2
50:01:43:80:02:5c:0d:ed
alias: comback04_2
H{10:00:00:00:c9:59:41:50}
alias: comvirt01_2
50:01:43:80:05:66:51:02
alias: comvirt02_2
50:01:43:80:03:b0:19:3e
alias: comvirt03_2
H{50:01:10:a0:00:18:68:36}
alias: comvirt04_2
50:01:43:80:03:af:63:38
alias: comvirt05_2
50:01:43:80:02:51:c5:b6
alias: msa_2 50:05:08:b3:00:93:43:61

Effective configuration:
cfg: Fabric_B_cfg
zone: BLADE01_EVA_B
50:06:0b:00:00:c2:62:22
50:01:43:80:02:5c:0d:e9
50:01:43:80:02:5c:0d:ed
zone: BLADE02_EVA_B
50:06:0b:00:00:c2:62:2a
50:01:43:80:02:5c:0d:e9
50:01:43:80:02:5c:0d:ed
zone: BLADE03_EVA_B
50:06:0b:00:00:c2:62:2e
50:01:43:80:02:5c:0d:e9
50:01:43:80:02:5c:0d:ed
zone: BLADE04_EVA_B
50:06:0b:00:00:c2:62:32
50:01:43:80:02:5c:0d:e9
50:01:43:80:02:5c:0d:ed
zone: BLADE05_EVA_B
50:06:0b:00:00:c2:62:36
50:01:43:80:02:5c:0d:e9
50:01:43:80:02:5c:0d:ed
zone: BLADE13_EVA_B
50:06:0b:00:00:c2:62:26
50:01:43:80:02:5c:0d:e9
50:01:43:80:02:5c:0d:ed
zone: COMBACK04_EVA_B
10:00:00:00:c9:59:41:50
50:01:43:80:02:5c:0d:e9
50:01:43:80:02:5c:0d:ed
zone: COMVIRT01_EVA_B
50:01:43:80:05:66:51:02
50:01:43:80:02:5c:0d:e9
50:01:43:80:02:5c:0d:ed
zone: COMVIRT02_EVA_B
50:01:43:80:03:b0:19:3e
50:01:43:80:02:5c:0d:e9
50:01:43:80:02:5c:0d:ed
zone: COMVIRT03_EVA_B
50:01:10:a0:00:18:68:36
50:01:43:80:02:5c:0d:e9
50:01:43:80:02:5c:0d:ed
zone: COMVIRT04_EVA_B
50:01:43:80:03:af:63:38
50:01:43:80:02:5c:0d:e9
50:01:43:80:02:5c:0d:ed
zone: COMVIRT05_EVA_B
50:01:43:80:02:51:c5:b6
50:01:43:80:02:5c:0d:e9
50:01:43:80:02:5c:0d:ed

Brocade switch 2 config

172.xx.xx.xx

Defined configuration:
cfg: Fabric_A_cfg
BLADE01_EVA_A; BLADE02_EVA_A; BLADE0
BLADE05_EVA_A; BLADE13_EVA_A; COMVIR
COMVIRT02_EVA_A; COMVIRT03_EVA_A; CO
COMVIRT05_EVA_A; comvirt06; VConnect
zone: BLADE01_EVA_A
BLADE01_1; Comvirt06; EVA01_CLFP1; E
zone: BLADE02_EVA_A
BLADE02_1; EVA01_CLFP1; EVA01_CRFP1
zone: BLADE03_EVA_A
BLADE03_1; EVA01_CLFP1; EVA01_CRFP1
zone: BLADE04_EVA_A
BLADE04_1; EVA01_CLFP1; EVA01_CRFP1
zone: BLADE05_EVA_A
BLADE05_1; EVA01_CLFP1; EVA01_CRFP1
zone: BLADE13_EVA_A
BLADE13_1; EVA01_CLFP1; EVA01_CRFP1
zone: COMVIRT01_EVA_A
comvirt01_1; EVA01_CLFP1; EVA01_CRFP
zone: COMVIRT01_MSA_A
msa_1; comvirt01_1
zone: COMVIRT02_EVA_A
comvirt02_1; EVA01_CLFP1; EVA01_CRFP
zone: COMVIRT02_MSA_A
msa_1; comvirt02_1
zone: COMVIRT03_EVA_A
comvirt03_1; EVA01_CLFP1; EVA01_CRFP
zone: COMVIRT03_MSA_A
msa_1; comvirt03_1
zone: COMVIRT04_EVA_A
comvirt04_1; EVA01_CLFP1; EVA01_CRFP
zone: COMVIRT04_MSA_A
comvirt04_1; msa_1
zone: COMVIRT05_EVA_A
comvirt05_1; EVA01_CLFP1; EVA01_CRFP
zone: COMVIRT05_MSA_A
comvirt05_1; msa_1
zone: VConnect_Bay01_EVA_A
EVA01_CLFP1; EVA01_CRFP1; VConnect_B
zone: comvirt06
50:06:0b:00:00:c2:62:18; 50:06:0b:00
alias: BLADE01_1
50:06:0b:00:00:c2:62:18; 50:06:0b:00
alias: BLADE02_1
50:06:0b:00:00:c2:62:28
alias: BLADE03_1
50:06:0b:00:00:c2:62:2c
alias: BLADE04_1
50:06:0b:00:00:c2:62:30
alias: BLADE05_1
50:06:0b:00:00:c2:62:34
alias: BLADE13_1
50:06:0b:00:00:c2:62:24
alias: Comvirt06
50:06:0b:00:00:c2:62:18
alias: EVA01_CLFP1
50:01:43:80:02:5c:0d:e8
alias: EVA01_CRFP1
50:01:43:80:02:5c:0d:ec
alias: VConnect_Bay01_1
20:00:00:21:5a:2f:b4:01
alias: comvirt01_1
50:01:43:80:05:66:51:00
alias: comvirt02_1
50:01:43:80:03:b0:19:3c
alias: comvirt03_1
H{50:01:10:a0:00:18:68:34}
alias: comvirt04_1
50:01:43:80:03:af:63:3a
alias: comvirt05_1
50:01:43:80:02:51:c5:b4
alias: msa_1 50:05:08:b3:00:93:43:69

Effective configuration:
cfg: Fabric_A_cfg
zone: BLADE01_EVA_A
50:06:0b:00:00:c2:62:18
50:06:0b:00:00:c2:62:20
50:01:43:80:02:5c:0d:e8
50:01:43:80:02:5c:0d:ec
zone: BLADE02_EVA_A
50:06:0b:00:00:c2:62:28
50:01:43:80:02:5c:0d:e8
50:01:43:80:02:5c:0d:ec
zone: BLADE03_EVA_A
50:06:0b:00:00:c2:62:2c
50:01:43:80:02:5c:0d:e8
50:01:43:80:02:5c:0d:ec
zone: BLADE04_EVA_A
50:06:0b:00:00:c2:62:30
50:01:43:80:02:5c:0d:e8
50:01:43:80:02:5c:0d:ec
zone: BLADE05_EVA_A
50:06:0b:00:00:c2:62:34
50:01:43:80:02:5c:0d:e8
50:01:43:80:02:5c:0d:ec
zone: BLADE13_EVA_A
50:06:0b:00:00:c2:62:24
50:01:43:80:02:5c:0d:e8
50:01:43:80:02:5c:0d:ec
zone: COMVIRT01_EVA_A
50:01:43:80:05:66:51:00
50:01:43:80:02:5c:0d:e8
50:01:43:80:02:5c:0d:ec
zone: COMVIRT02_EVA_A
50:01:43:80:03:b0:19:3c
50:01:43:80:02:5c:0d:e8
50:01:43:80:02:5c:0d:ec
zone: COMVIRT03_EVA_A
50:01:10:a0:00:18:68:34
50:01:43:80:02:5c:0d:e8
50:01:43:80:02:5c:0d:ec
zone: COMVIRT04_EVA_A
50:01:43:80:03:af:63:3a
50:01:43:80:02:5c:0d:e8
50:01:43:80:02:5c:0d:ec
zone: COMVIRT05_EVA_A
50:01:43:80:02:51:c5:b4
50:01:43:80:02:5c:0d:e8
50:01:43:80:02:5c:0d:ec
zone: VConnect_Bay01_EVA_A
50:01:43:80:02:5c:0d:e8
50:01:43:80:02:5c:0d:ec
20:00:00:21:5a:2f:b4:01
zone: comvirt06
50:06:0b:00:00:c2:62:18
50:06:0b:00:00:c2:62:1a


I pasted both.

Thanks

[Johan Guldmyr]

Hi, should work.

But again I do not think you need the zones with the VC uplink port and the EVA ports.

[Abdelhadi Nassif]

The problem is this. Someone came in to the environment, pulled a cable from one of the VCs thinking it to be redundant. You can guess the rest. The whole thing came down and lost service. This is a live environment so my plan is to create new meaningful named zones, and test them before removing the old ones.

[Johan Guldmyr]

OK.

Well I don't think it will cause any problems ahving them there.

[Abdelhadi Nassif]

Unfortunately, it did and I know now why. Failover is not supported across VCs.I Need to set up another port and add it to the same fabric and setup failover. However, there is a still a SPOF as if the VC goes down you lose the path.

Any thoughts ?

Next,I can set up the zoning but I have to see what server is accessing which target to get a full map of the current.

[Johan Guldmyr]

If you cannot fail over a server's path between vc modules then you cannot protect against one vc going down. Sounds like a pretty severe limitation to me. Are you 100% on that?

On the eva you can control which controller owns the vdisk.

[Uwe Zessin]

Sure you can - route alternate paths through the second VC module. A blade FC mezz card has two ports.

[Abdelhadi Nassif]

I looked at the FC cookbook uses only one VC for fail over in all given scenarios

http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c01702940/c01702940.pdf

I hunted as much as I could on the web and seems to had a hunt on the net and everyone seems to agree this seems to be a severe limitation.

Can you please tell me or point me to a document on how I can set up a second VC and map the second HBA to use it.
Plus, do I have to create a second zone for VC2 or just add it to the same zone.

[Abdelhadi Nassif]

Thank you guys for your help.
We finally figured out the issue. It was down to the way we cabled up the bays. HP seems does not support a mesh type connection. Once we connected it according to the Cookbook, bingo!!! We now have redundant path. Still seems to be odd not to be able to have a mesh connection.

Now I am posting another similar question on the Ethernet side as I have a weird issue.

[Abdelhadi Nassif]

Cabling the bays according to the VC-FC cookbook and adding the second bay on the OA config solved the problem.