VMware Cloud Community
JF_ID
Enthusiast
Enthusiast
‎07-07-2010 01:04 PM

Only one HBA sees luns on 2 hba host configuration

I currently have HP EVA 4000 with 4 ESX Host with 2 HBA connect with 2 fabric and 2 controller. This should give me a total of 4 path to access each lun. I'm running Esx 4 U2.

Each Host have Vmhba1 & 2, all of my host use vmhba2 as you can see in my screenshots. If my memory is good, i remember that we should see e more path with standby status.

San zonning is Ok, what could it be ?

Preview file
35 KB
Preview file
71 KB
0 Kudos
13 Replies
a_p_
Leadership
Leadership
‎07-07-2010 03:37 PM

If SAN zoning is ok, the only other reason for not seeing LUN's is the presentation. Make sure you presented the LUN's to both HBA's/WWN's. Most likely you missed to add the second WWN to the ESX host in Command View.

André

0 Kudos
a_p_
Leadership
Leadership
‎07-07-2010 03:42 PM

BTW, did you already read HP's Configuration best practices for HP StorageWorks Enterprise Virtual Array (EVA) family and VMware vS... ?

André

0 Kudos
JF_ID
Enthusiast
Enthusiast
‎07-07-2010 05:03 PM

The host is configure with two port the lun is presented to that host.

For you second question, Yes i check the guide, i was checking configuration to apply some of these recommandation and this issue. I was searching for 2 active (i/o) in Round Robin in found that only one hba was used.

Thank for your help

0 Kudos
binoche
VMware Employee
VMware Employee
‎07-07-2010 06:19 PM

could you please post the results of cat /proc/scsi/qla2xxx/* or cat /proc/scsi/lpfc820/* and vmkernel.log? thanks

binoche, VMware VCP, Cisco CCNA

0 Kudos
JF_ID
Enthusiast
Enthusiast
‎07-08-2010 05:44 AM

Here the lpfc820:

Emulex LightPulse Fibre Channel SCSI driver 8.2.0.30.52vmw-4

HP FC2142SR 4Gb PCI-e, SC, Fibre Channel Adapter on PCI bus 13 device 00 irq 137

BoardNum: 0

Firmware Version: 2.72A2 (W3F2.72A2)

Portname: 10:00:00:00:c9:81:88:73 Nodename: 20:00:00:00:c9:81:88:73

SLI Rev: 3

NPIV Supported: VPIs max 16 VPIs used 0

RPIs max 512 RPIs used 6

Vport List:

Link Up - Ready:

PortID 0x20600

Fabric

Current speed 4G

Physical Port Discovered Nodes: Count 0

Emulex LightPulse Fibre Channel SCSI driver 8.2.0.30.52vmw-4

HP FC2142SR 4Gb PCI-e, SC, Fibre Channel Adapter on PCI bus 17 device 00 irq 145

BoardNum: 1

Firmware Version: 2.72A2 (W3F2.72A2)

Portname: 10:00:00:00:c9:81:90:e6 Nodename: 20:00:00:00:c9:81:90:e6

SLI Rev: 3

NPIV Supported: VPIs max 16 VPIs used 0

RPIs max 512 RPIs used 6

Vport List:

Link Up - Ready:

PortID 0x10600

Fabric

Current speed 4G

Physical Port Discovered Nodes: Count 2

t01 DID 010000 State 06 WWPN 50:00:1f:e1:50:0c:60:b8 WWNN 50:00:1f:e1:50:0c:60:b0

t00 DID 010100 State 06 WWPN 50:00:1f:e1:50:0c:60:bc WWNN 50:00:1f:e1:50:0c:60:b0

VKERNEL :attached file

vkernel.log
0 Kudos
RParker
Immortal
Immortal
‎07-08-2010 06:06 AM

San zonning is Ok, what could it be ?

There is only one reason that HBA's don't show up. The Zoning is incorrect. If one HBA is visible and the other is not, the only thing it could be is the zone is mistyped or you can try adding the WW Port AND Node name to the zone.

Then after make sure you rescan BOTH HBA.

If there are luns visible on BOTH HBA, then something is wrong with the zone. It must be the zone. Maybe the Fiber Switch is blocking this HBA from an earlier setting, did you try checking the Fiber Switch logs?

Zoning includes the SAN and the Fiber Switch, both must be thoroughly checked for accuracy.

0 Kudos
a_p_
Leadership
Leadership
‎07-08-2010 11:02 AM

I agree with RParker, at least the controller ports should show up correctly when zoning is in place.

Log on to the switch 2 and check the ports where the EVA is attached. If you cabled like I assume, you should see "WWPN 50:00:1f:e1:50:0c:60:b9" on port 0 and "WWPN 50:00:1f:e1:50:0c:60:bd" on port 1.

Please check the zoning on the FC switches once more and make sure the zones are not just configured, but also added to the active configuration.

André

JF_ID
Enthusiast
Enthusiast
‎07-08-2010 12:09 PM

Here some screen shot of Switch #2 zoning,alias... I take for example one of my server Vm04

You right for B9 port 0 and BD on port 1 (screenshot)

Preview file
58 KB
Preview file
86 KB
Preview file
53 KB
0 Kudos
JF_ID
Enthusiast
Enthusiast
‎07-08-2010 12:12 PM

I fix the problem for one of my server... it weird ...

I unplug the hba who cannot see lun, reboot the server, plug it back it Boom everything work fine... the lun are visible though both HBA...

I'm gonna make a test with a second server just by unplug hba cable to see if he wakeup ; )

I'll let you know!

0 Kudos
JF_ID
Enthusiast
Enthusiast
‎07-08-2010 12:55 PM

AFTER UNPLUG AND PLUG BACK IN ! It work

Jul 8 15:46:51 Vm03 vmkernel: 16:02:49:03.311 cpu7:4226)<3>lpfc820 0000:13:00.0: 0:1305 Link Down Event x2 received Data: x2 x20 x110 x0 x0
Jul 8 15:46:57 Vm03 vmkernel: 16:02:49:09.844 cpu7:4226)<3>lpfc820 0000:13:00.0: 0:1303 Link Up Event x3 received Data: x3 x0 x10 x6f x0 x0 0

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.927 cpu3:4213)ScsiScan: 844: Path 'vmhba1:C0:T0:L0': Vendor: 'HP ' Model: 'HSV200 ' Rev: '6220'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.927 cpu3:4213)ScsiScan: 847: Path 'vmhba1:C0:T0:L0': Type: 0xc, ANSI rev: 5, TPGS: 0 (none)

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.927 cpu3:4213)ScsiScan: 844: Path 'vmhba1:C0:T0:L1': Vendor: 'HP ' Model: 'HSV200 ' Rev: '6220'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.927 cpu3:4213)ScsiScan: 847: Path 'vmhba1:C0:T0:L1': Type: 0x0, ANSI rev: 5, TPGS: 3 (implicit and explicit)

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.928 cpu3:4213)ScsiScan: 844: Path 'vmhba1:C0:T0:L2': Vendor: 'HP ' Model: 'HSV200 ' Rev: '6220'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.928 cpu3:4213)ScsiScan: 847: Path 'vmhba1:C0:T0:L2': Type: 0x0, ANSI rev: 5, TPGS: 3 (implicit and explicit)

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.928 cpu3:4213)ScsiScan: 844: Path 'vmhba1:C0:T0:L3': Vendor: 'HP ' Model: 'HSV200 ' Rev: '6220'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.928 cpu3:4213)ScsiScan: 847: Path 'vmhba1:C0:T0:L3': Type: 0x0, ANSI rev: 5, TPGS: 3 (implicit and explicit)

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.929 cpu3:4213)ScsiScan: 844: Path 'vmhba1:C0:T0:L11': Vendor: 'HP ' Model: 'HSV200 ' Rev: '6220'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.929 cpu3:4213)ScsiScan: 847: Path 'vmhba1:C0:T0:L11': Type: 0x0, ANSI rev: 5, TPGS: 3 (implicit and explicit)

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.929 cpu3:4213)ScsiScan: 844: Path 'vmhba1:C0:T0:L13': Vendor: 'HP ' Model: 'HSV200 ' Rev: '6220'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.929 cpu3:4213)ScsiScan: 847: Path 'vmhba1:C0:T0:L13': Type: 0x0, ANSI rev: 5, TPGS: 3 (implicit and explicit)

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.930 cpu3:4213)ScsiScan: 844: Path 'vmhba1:C0:T0:L14': Vendor: 'HP ' Model: 'HSV200 ' Rev: '6220'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.930 cpu3:4213)ScsiScan: 847: Path 'vmhba1:C0:T0:L14': Type: 0x0, ANSI rev: 5, TPGS: 3 (implicit and explicit)

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.930 cpu3:4213)ScsiScan: 844: Path 'vmhba1:C0:T0:L15': Vendor: 'HP ' Model: 'HSV200 ' Rev: '6220'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.930 cpu3:4213)ScsiScan: 847: Path 'vmhba1:C0:T0:L15': Type: 0x0, ANSI rev: 5, TPGS: 3 (implicit and explicit)

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.930 cpu3:4213)ScsiScan: 844: Path 'vmhba1:C0:T0:L16': Vendor: 'HP ' Model: 'HSV200 ' Rev: '6220'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.930 cpu3:4213)ScsiScan: 847: Path 'vmhba1:C0:T0:L16': Type: 0x0, ANSI rev: 5, TPGS: 3 (implicit and explicit)

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.931 cpu3:4213)ScsiScan: 844: Path 'vmhba1:C0:T0:L17': Vendor: 'HP ' Model: 'HSV200 ' Rev: '6220'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.931 cpu3:4213)ScsiScan: 847: Path 'vmhba1:C0:T0:L17': Type: 0x0, ANSI rev: 5, TPGS: 3 (implicit and explicit)

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.931 cpu3:4213)ScsiPath: 3715: Plugin 'NMP' claimed path 'vmhba1:C0:T0:L11'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.931 cpu3:4213)ScsiPath: 3715: Plugin 'NMP' claimed path 'vmhba1:C0:T0:L13'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.931 cpu3:4213)ScsiPath: 3715: Plugin 'NMP' claimed path 'vmhba1:C0:T0:L14'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.931 cpu3:4213)ScsiPath: 3715: Plugin 'NMP' claimed path 'vmhba1:C0:T0:L15'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.931 cpu3:4213)ScsiPath: 3715: Plugin 'NMP' claimed path 'vmhba1:C0:T0:L16'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.931 cpu3:4213)ScsiPath: 3715: Plugin 'NMP' claimed path 'vmhba1:C0:T0:L17'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.931 cpu3:4213)VMW_SATP_EVA: satp_eva_alloc_path: Path vmhba1:C0:T0:L0 has devclass 0xc; marking device as management lun

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.931 cpu3:4213)ScsiPath: 3715: Plugin 'NMP' claimed path 'vmhba1:C0:T0:L0'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.931 cpu3:4213)ScsiPath: 3715: Plugin 'NMP' claimed path 'vmhba1:C0:T0:L1'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.931 cpu3:4213)ScsiPath: 3715: Plugin 'NMP' claimed path 'vmhba1:C0:T0:L2'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.931 cpu3:4213)ScsiPath: 3715: Plugin 'NMP' claimed path 'vmhba1:C0:T0:L3'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.945 cpu3:4213)ScsiScan: 844: Path 'vmhba1:C0:T1:L0': Vendor: 'HP ' Model: 'HSV200 ' Rev: '6220'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.945 cpu3:4213)ScsiScan: 847: Path 'vmhba1:C0:T1:L0': Type: 0xc, ANSI rev: 5, TPGS: 0 (none)

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.945 cpu3:4213)ScsiScan: 844: Path 'vmhba1:C0:T1:L1': Vendor: 'HP ' Model: 'HSV200 ' Rev: '6220'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.945 cpu3:4213)ScsiScan: 847: Path 'vmhba1:C0:T1:L1': Type: 0x0, ANSI rev: 5, TPGS: 3 (implicit and explicit)

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.946 cpu3:4213)ScsiScan: 844: Path 'vmhba1:C0:T1:L2': Vendor: 'HP ' Model: 'HSV200 ' Rev: '6220'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.946 cpu3:4213)ScsiScan: 847: Path 'vmhba1:C0:T1:L2': Type: 0x0, ANSI rev: 5, TPGS: 3 (implicit and explicit)

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.946 cpu3:4213)ScsiScan: 844: Path 'vmhba1:C0:T1:L3': Vendor: 'HP ' Model: 'HSV200 ' Rev: '6220'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.946 cpu3:4213)ScsiScan: 847: Path 'vmhba1:C0:T1:L3': Type: 0x0, ANSI rev: 5, TPGS: 3 (implicit and explicit)

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.946 cpu3:4213)ScsiScan: 844: Path 'vmhba1:C0:T1:L11': Vendor: 'HP ' Model: 'HSV200 ' Rev: '6220'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.946 cpu3:4213)ScsiScan: 847: Path 'vmhba1:C0:T1:L11': Type: 0x0, ANSI rev: 5, TPGS: 3 (implicit and explicit)

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.947 cpu3:4213)ScsiScan: 844: Path 'vmhba1:C0:T1:L13': Vendor: 'HP ' Model: 'HSV200 ' Rev: '6220'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.947 cpu3:4213)ScsiScan: 847: Path 'vmhba1:C0:T1:L13': Type: 0x0, ANSI rev: 5, TPGS: 3 (implicit and explicit)

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.947 cpu3:4213)ScsiScan: 844: Path 'vmhba1:C0:T1:L14': Vendor: 'HP ' Model: 'HSV200 ' Rev: '6220'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.947 cpu3:4213)ScsiScan: 847: Path 'vmhba1:C0:T1:L14': Type: 0x0, ANSI rev: 5, TPGS: 3 (implicit and explicit)

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.950 cpu3:4213)ScsiScan: 844: Path 'vmhba1:C0:T1:L15': Vendor: 'HP ' Model: 'HSV200 ' Rev: '6220'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.950 cpu3:4213)ScsiScan: 847: Path 'vmhba1:C0:T1:L15': Type: 0x0, ANSI rev: 5, TPGS: 3 (implicit and explicit)

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.950 cpu3:4213)ScsiScan: 844: Path 'vmhba1:C0:T1:L16': Vendor: 'HP ' Model: 'HSV200 ' Rev: '6220'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.950 cpu3:4213)ScsiScan: 847: Path 'vmhba1:C0:T1:L16': Type: 0x0, ANSI rev: 5, TPGS: 3 (implicit and explicit)

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.950 cpu3:4213)ScsiScan: 844: Path 'vmhba1:C0:T1:L17': Vendor: 'HP ' Model: 'HSV200 ' Rev: '6220'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.950 cpu3:4213)ScsiScan: 847: Path 'vmhba1:C0:T1:L17': Type: 0x0, ANSI rev: 5, TPGS: 3 (implicit and explicit)

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.951 cpu3:4213)VMW_SATP_EVA: satp_eva_alloc_path: Path vmhba1:C0:T1:L0 has devclass 0xc; marking device as management lun

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.951 cpu3:4213)ScsiPath: 3715: Plugin 'NMP' claimed path 'vmhba1:C0:T1:L0'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.951 cpu3:4213)ScsiPath: 3715: Plugin 'NMP' claimed path 'vmhba1:C0:T1:L1'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.951 cpu3:4213)ScsiPath: 3715: Plugin 'NMP' claimed path 'vmhba1:C0:T1:L2'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.951 cpu3:4213)ScsiPath: 3715: Plugin 'NMP' claimed path 'vmhba1:C0:T1:L3'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.951 cpu3:4213)ScsiPath: 3715: Plugin 'NMP' claimed path 'vmhba1:C0:T1:L11'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.951 cpu3:4213)ScsiPath: 3715: Plugin 'NMP' claimed path 'vmhba1:C0:T1:L13'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.951 cpu3:4213)ScsiPath: 3715: Plugin 'NMP' claimed path 'vmhba1:C0:T1:L14'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.951 cpu3:4213)ScsiPath: 3715: Plugin 'NMP' claimed path 'vmhba1:C0:T1:L15'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.951 cpu3:4213)ScsiPath: 3715: Plugin 'NMP' claimed path 'vmhba1:C0:T1:L16'

Jul 8 15:46:58 Vm03 vmkernel: 16:02:49:09.951 cpu3:4213)ScsiPath: 3715: Plugin 'NMP' claimed path 'vmhba1:C0:T1:L17'

0 Kudos
binoche
VMware Employee
VMware Employee
‎07-08-2010 05:17 PM

I guess this is only vmhba2, where is lpfc820 entry for vmhba1, it is not found?

I also do not find vmhba1 from vmkernel.log, maybe you can have a recheck what is wrong for vmhba1 when the driver lpfc820 loading? then we can have more understanding why vmhba1 can not find luns at the beginning

binoche, VMware VCP, Cisco CCNA

JF_ID
Enthusiast
Enthusiast
‎07-09-2010 07:46 AM

I didn't copy all the vmkernel log, but just what happen after i unplug the Vmhba1...

In conclusion, we have a bug with the fabric 2, because all server connect to that switch got the same issue (including Esx, Windows ...).

After disable and enable the port for each host, everything was Ok

Thank for you help Guys,

0 Kudos
JF_ID
Enthusiast
Enthusiast
‎07-09-2010 07:49 AM

The problem was a Fabric problem, after disable and enable ports for each host, everything back to normal

0 Kudos