HPE EVA Storage
1748217 Members
4114 Online
108759 Solutions
New Discussion юеВ

Re: New EVA installation on existing SAN

 
SOLVED
Go to solution
Stuart Powell
Super Advisor

New EVA installation on existing SAN

Our K580 is one of many boxes that are seeing the same problem; we have two HBA's in this server, each one connecting to one of two duplicate SAN's. Each SAN consists of two EMC labled Brocade 3800 switches running firmware 3.2.0, one running in a local room (Domain 1 for SAN 1, and Domain 2 for SAN 2), and the second in a remote room on the same plant campus (Domain 3 for SAN 1, and Domain 4 for SAN 2). The switch pairs that make up a SAN have 2 port ISL connections. There are two EVA 4000 arrays; one connected to the local switch in both SANs. The zone on each SAN has as members; one HBA on the K580, and one controller on the local and remote EVA4000's.
When the LUNs on each array are created and presented to host specified, t9kkux in this case, then after an "ioscan" the LUNs on the array connected directly to each switch are seen, but not the LUNs through the ISL connection. Below is the output of "ioscan" that relates to this situation:
For th9kkux on Yertle:
disk 65 8/8/1/0.1.30.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
disk 66 8/8/1/0.1.30.0.0.0.2 sdisk CLAIMED DEVICE HP HSV200
disk 68 8/8/1/0.1.30.0.0.0.3 sdisk CLAIMED DEVICE HP HSV200
disk 61 8/8/1/0.2.19.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
disk 63 8/8/1/0.2.19.0.0.0.2 sdisk CLAIMED DEVICE HP HSV200
On Turtle:
disk 73 8/4/1/0.3.30.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
disk 75 8/4/1/0.3.30.0.0.0.2 sdisk CLAIMED DEVICE HP HSV200
disk 76 8/4/1/0.3.30.0.0.0.3 sdisk CLAIMED DEVICE HP HSV200
disk 58 8/4/1/0.4.30.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
disk 59 8/4/1/0.4.30.0.0.0.2 sdisk CLAIMED DEVICE HP HSV200

I'd like to be able to see the LUN's through the ISL connection.

Any ideas?

Stuart
Sometimes the best answer is another question
4 REPLIES 4
Steven Clementi
Honored Contributor

Re: New EVA installation on existing SAN

Stuart:

Can you attached to 1 of the switches in each SAN using the web gui and hit the admin page, download the Admin report and attach to a message? This will give us some more insight into how your SAN(s) is configured.



Steven
Steven Clementi
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
Stuart Powell
Super Advisor

Re: New EVA installation on existing SAN

Steven,

Here is the report. I haven't looked at it yet to see if there something that makes me go "Duh!"
List of Switches

Switch ID Worldwide Name Enet IP Addr FC IP Addr Name
-------------------------------------------------------------------------
1: fffc01 10:00:00:60:69:50:0e:7e 147.116.63.20 0.0.0.0 >"swemcm1"
2: fffc02 10:00:00:60:69:50:14:23 147.116.63.27 0.0.0.0 "swemcs1"

The Fabric has 2 switches

Ethernet IP Address: 147.116.63.20
Ethernet Subnet Mask: 255.255.255.0
Fibre Channel IP Address: none
Fibre Channel Subnet Mask: none
Gateway Address: 147.116.63.254

Kernel: 5.4
Fabric OS: v3.2.0
Made on: Thu Oct 21 12:17:19 PDT 2004
Flash: Thu Oct 21 12:17:58 PDT 2004
BootProm: Wed May 23 12:37:30 PDT 2001

List of Inter-Switch Links

Local Domain ID: 1

Local Port Domain Remote Port State
-------------------------------------------------------
9 2 9 NB_ST_FULL
13 2 13 NB_ST_FULL


List of Ports

switchName: swemcm1
switchType: 9.1
switchState: Online
switchMode: Native
switchRole: Principal
switchDomain: 1
switchId: fffc01
switchWwn: 10:00:00:60:69:50:0e:7e
switchBeacon: OFF
Zoning: ON (AET_Zone_Config_1)
port 0: id N1 Online F-Port 50:06:0b:00:00:13:57:58
port 1: id N2 Online F-Port 10:00:00:00:c9:36:4c:d5
port 2: id N2 No_Light
port 3: id N1 Online F-Port 50:00:1f:e1:50:06:a7:ad
port 4: id N1 Online F-Port 50:06:0b:00:00:13:57:b0
port 5: id N2 No_Light
port 6: id N2 No_Light
port 7: id N2 Online F-Port 50:06:0b:00:00:11:8d:c4
port 8: id N1 Online F-Port 50:06:0b:00:00:0b:35:e4
port 9: id N2 Online E-Port 10:00:00:60:69:50:14:23 "swemcs1" (downstream)
port 10: id N2 No_Light
port 11: id N2 Online F-Port 50:06:01:68:11:03:20:eb
port 12: id N2 No_Light
port 13: id N2 Online E-Port 10:00:00:60:69:50:14:23 "swemcs1"
port 14: id N1 Online F-Port 50:00:1f:e1:50:06:a7:a8
port 15: id N2 Online F-Port 50:06:01:69:11:03:20:eb

Name Server

{
011000 011100 011300 011400 011700 011800 011b00 011e00
011f00 021000 021100 021200 021300 021400 021700 021800
021b00 021e00 021f00
19 Nx_Ports in the Fabric }

{
Type Pid COS PortName NodeName TTL(sec)
N 011000; 3;50:06:0b:00:00:13:57:58;50:06:0b:00:00:13:57:59; na
FC4s: FCP
Fabric Port Name: 20:00:00:60:69:50:0e:7e
N 011100; 2,3;10:00:00:00:c9:36:4c:d5;20:00:00:00:c9:36:4c:d5; na
FC4s: FCIP FCP
NodeSymb: [35] "Emulex LP9002 FV3.90A7 DV5-1.10A4 "
Fabric Port Name: 20:01:00:60:69:50:0e:7e
N 011300; 3;50:00:1f:e1:50:06:a7:ad;50:00:1f:e1:50:06:a7:a0; na
FC4s: FCP
PortSymb: [26] "HSV200 - NO SCELL - CR0920"
Fabric Port Name: 20:03:00:60:69:50:0e:7e
N 011400; 3;50:06:0b:00:00:13:57:b0;50:06:0b:00:00:13:57:b1; na
FC4s: FCP
Fabric Port Name: 20:04:00:60:69:50:0e:7e
N 011700; 3;50:06:0b:00:00:11:8d:c4;50:06:0b:00:00:11:8d:c5; na
FC4s: FCP
Fabric Port Name: 20:07:00:60:69:50:0e:7e
N 011800; 3;50:06:0b:00:00:0b:35:e4;50:06:0b:00:00:0b:35:e5; na
FC4s: FCP
Fabric Port Name: 20:08:00:60:69:50:0e:7e
N 011b00; 3;50:06:01:68:11:03:20:eb;50:06:01:60:88:03:20:eb; na
FC4s: FCP [DGC 0851]
Fabric Port Name: 20:0b:00:60:69:50:0e:7e
N 011e00; 3;50:00:1f:e1:50:06:a7:a8;50:00:1f:e1:50:06:a7:a0; na
FC4s: FCP
PortSymb: [26] "HSV200 - NO SCELL - CR0920"
Fabric Port Name: 20:0e:00:60:69:50:0e:7e
N 011f00; 3;50:06:01:69:11:03:20:eb;50:06:01:60:88:03:20:eb; na
FC4s: FCP [DGC 0851]
Fabric Port Name: 20:0f:00:60:69:50:0e:7e

The Local Name Server has 9 entries }

Zoning Information

Defined configuration:
cfg: AET_Zone_Config_1
PLS3; PLS4; DEV2; DW2; DW4; ERP7; ERP5; DEV4; mail1; sthnt1_1;
EVA_Mgmt_Zone; DWPLSEVA; ERPEVA
zone: CIS2 sthcisha2; Lion_B0; Tiger_A0
zone: DEV2 th9kfux_8_4; Lion_B1; Tiger_A1
zone: DEV4 th9keux_8_4; Lion_B1; Tiger_A1
zone: DW2 th9klux_050; Lion_B1; Tiger_A1
zone: DW4 th9kmux_050; Lion_B1; Tiger_A1
zone: DWPLSEVA
th9klux_050; th9kmux_050; eva_main_top; eva_sat_bot;
th9kjux_8_8; th9kkux_8_8
zone: ERP5 th9kpux_0_0_12; Lion_B0; Tiger_A0
zone: ERP7 Lion_B0; Tiger_A0; th9koux_0_0_12
zone: ERPEVA eva_main_top; eva_sat_bot; th9koux_0_0_12; th9kpux_0_0_12
zone: EVA_Mgmt_Zone
eva_main_top; eva_sat_bot; stheva_2; th9kfux_8_4; sthcisha2
zone: PLS3 th9kjux_8_8; Lion_B0; Tiger_A0
zone: PLS4 th9kkux_8_8; Lion_B0; Tiger_A0
zone: mail1 sthmail_2; Tiger_A1; Lion_B0
zone: sthnt1_1
Lion_B1; Tiger_A0; sthnt1_7
alias: Lion_B0 50:06:01:68:11:03:20:eb
alias: Lion_B1 50:06:01:69:11:03:20:eb
alias: Tiger_A0
50:06:01:60:40:04:b2:5e
alias: Tiger_A1
50:06:01:61:40:04:b2:5e
alias: eva_main_bot
50:00:1f:e1:50:06:a7:ad
alias: eva_main_top
50:00:1f:e1:50:06:a7:a8
alias: eva_sat_bot
50:00:1f:e1:50:06:a7:bd
alias: eva_sat_top
50:00:1f:e1:50:06:a7:b8
alias: sthcisha2
10:00:00:00:c9:34:a1:1d
alias: stheva_2
21:00:00:e0:8b:14:f0:e4
alias: sthmail_2
10:00:00:00:c9:32:5d:bb
alias: sthnt1_7
10:00:00:00:c9:36:4c:d5
alias: th9keux_8_4
50:06:0b:00:00:13:57:b0
alias: th9kfux_8_4
50:06:0b:00:00:13:57:72
alias: th9kjux_8_8
50:06:0b:00:00:13:57:58
alias: th9kkux_8_8
50:06:0b:00:00:13:5a:4c
alias: th9klux_050
50:06:0b:00:00:0b:29:a0
alias: th9kmux_050
50:06:0b:00:00:0b:35:e4
alias: th9koux_0_0_12
50:06:0b:00:00:11:8d:9a
alias: th9kpux_0_0_12
50:06:0b:00:00:11:8d:c4

Effective configuration:
cfg: AET_Zone_Config_1
zone: DEV2 50:06:0b:00:00:13:57:72
50:06:01:69:11:03:20:eb
50:06:01:61:40:04:b2:5e
zone: DEV4 50:06:0b:00:00:13:57:b0
50:06:01:69:11:03:20:eb
50:06:01:61:40:04:b2:5e
zone: DW2 50:06:0b:00:00:0b:29:a0
50:06:01:69:11:03:20:eb
50:06:01:61:40:04:b2:5e
zone: DW4 50:06:0b:00:00:0b:35:e4
50:06:01:69:11:03:20:eb
50:06:01:61:40:04:b2:5e
zone: DWPLSEVA
50:06:0b:00:00:0b:29:a0
50:06:0b:00:00:0b:35:e4
50:00:1f:e1:50:06:a7:a8
50:00:1f:e1:50:06:a7:bd
50:06:0b:00:00:13:57:58
50:06:0b:00:00:13:5a:4c
zone: ERP5 50:06:0b:00:00:11:8d:c4
50:06:01:68:11:03:20:eb
50:06:01:60:40:04:b2:5e
zone: ERP7 50:06:01:68:11:03:20:eb
50:06:01:60:40:04:b2:5e
50:06:0b:00:00:11:8d:9a
zone: ERPEVA 50:00:1f:e1:50:06:a7:a8
50:00:1f:e1:50:06:a7:bd
50:06:0b:00:00:11:8d:9a
50:06:0b:00:00:11:8d:c4
zone: EVA_Mgmt_Zone
50:00:1f:e1:50:06:a7:a8
50:00:1f:e1:50:06:a7:bd
21:00:00:e0:8b:14:f0:e4
50:06:0b:00:00:13:57:72
10:00:00:00:c9:34:a1:1d
zone: PLS3 50:06:0b:00:00:13:57:58
50:06:01:68:11:03:20:eb
50:06:01:60:40:04:b2:5e
zone: PLS4 50:06:0b:00:00:13:5a:4c
50:06:01:68:11:03:20:eb
50:06:01:60:40:04:b2:5e
zone: mail1 10:00:00:00:c9:32:5d:bb
50:06:01:61:40:04:b2:5e
50:06:01:68:11:03:20:eb
zone: sthnt1_1
50:06:01:69:11:03:20:eb
50:06:01:60:40:04:b2:5e
10:00:00:00:c9:36:4c:d5


SFP Serial ID Information

port 0: id (sw) Vendor: IBM Serial No: 21P7053001GR4
port 1: id (sw) Vendor: IBM Serial No: 21P7053001JRP
port 2: id (sw) Vendor: IBM Serial No: 21P7053001BGW
port 3: id (sw) Vendor: IBM Serial No: 21P7053001BRH
port 4: id (sw) Vendor: IBM Serial No: 21P7053001A9B
port 5: id (sw) Vendor: IBM Serial No: 21P70530019SX
port 6: id (sw) Vendor: IBM Serial No: 21P7053001BQG
port 7: id (sw) Vendor: IBM Serial No: 21P7053001F5Q
port 8: id (sw) Vendor: IBM Serial No: 21P7053001JTU
port 9: id (sw) Vendor: IBM Serial No: 21P7053001BKT
port 10: id (sw) Vendor: IBM Serial No: 21P70530019SR
port 11: id (sw) Vendor: IBM Serial No: 21P7053001AEW
port 12: id (sw) Vendor: IBM Serial No: 21P7053001A09
port 13: id (sw) Vendor: IBM Serial No: 21P70530019Z6
port 14: id (sw) Vendor: IBM Serial No: 21P70530019GR
port 15: id (sw) Vendor: IBM Serial No: 21P70530019G8


Sometimes the best answer is another question
Uwe Zessin
Honored Contributor
Solution

Re: New EVA installation on existing SAN

This is a fabric of domains 1+2, not 1+3.
.
Stuart Powell
Super Advisor

Re: New EVA installation on existing SAN

I hate it when I do that. I got my domain numbers all confused. Now I've got to apologies to the SAN Admin.

Thanks for the extra set of eyes.
Sometimes the best answer is another question