Ok so catching up on the convo line. Yeah you can't have both controlers on the EVA pointing to the Netapp Filer. It will only allow one path. You will notice this once you get connectivity because when you present the luns to the Itiator ports on the filer they will have the switch name. Well with Brocade thats what happens and so it should because that way you know that the disks are presented luns.
here is an example below. aunssdcfsw01 is my fabric switch. 126L8 ect are the lun numbers L8 ect.....
As you can see i have two initiators 0a and 0c from VFilerB and 2 target ports from EVA connected to
ports 17-18 (eva) and 20-21 (vfiler) on my san switch...
this are the wwn's
17 17 id 4G Online F-Port 50:01:43:80:02:5d:fa:29
18 18 id 4G Online F-Port 50:01:43:80:02:5d:fa:2d
19 19 id 4G Online F-Port 50:01:10:a0:00:93:9e:88
20 20 id 4G Online F-Port 50:0a:09:82:00:03:52:df
21 21 id 4G Online F-Port 50:0a:09:80:00:03:52:df
I have try to setup port zoning with no luck to show disks and there is no information from San switch present on fcadmin channels output. With port zoning also, WWNs for N ports on VFiler found as 0000000000000 and there is no other information present for additional ports on my san switch..
i have also try to mix wwn and port zoning....
20:14:00:05:1e:ae:cd:52 (portname for initiator port 0a vfilerB))
20:11:00:05:1e:ae:cd:52 (portname for target port on eva Controller 1 (fp2)
20:12:00:05:1e:ae:cd:52 (portname for target port on eva Controller 2 (fp2)
50:0a:09:82:00:03:52:df (wwn of initiator port 0a on VfilerB)
50:01:43:80:02:5d:fa:29 (wwn of target port on eva controller1 (fp2)
20:15:00:05:1e:ae:cd:52 (portname for initiator port 0c)
20:11:00:05:1e:ae:cd:52 (portname for target port on eva Controller1 (fp2)
20:12:00:05:1e:ae:cd:52 (portname for target port on eva Controller2 (fp2)
50:0a:09:80:00:03:52:df (wwn of initiator port 0c on VfilerB)
50:01:43:80:02:5d:fa:2d (wwn of target port on EVA (fp2)
with this configuration i can view some information for san switch:
ok, but then we have 2 initiators and 3 targets, which is not supported either. V-Series requires single initiator multiple target zoning for a supported configuration. There is a huge load of documentation in the NOW support database about proper cabeling and zoning btw.