MRU policy showing up for EVA6000

[njd62495]

I have installed vSphere Update 1 onto a couple of new hosts.

When I attach them to my EVA6000 the policy of the path is defaulting to Most Recently Used and it's confusing to me a little because when I connected my ESX 3.5 servers to the same EVA6000 the policy defaulted to Fixed as I understand it should on an active/active array.

I got nervous so I set them all to Fixed.

The Storage Adapter Type that I see is VMW_SATP_ALUA. Should I be concerned about this?

Also would there be any benefit to running the paths under Round Robin now that it is fully supported under vSphere?

Will my EVA freak out if I set the vSphere host paths to round robin while the ESX3.5 hosts are still set to fixed?

[jpdicicco]

See my post here: http://communities.vmware.com/message/1452783

These documents are pretty much the only docs you need to setup an EVA for VMware.

You should try to get to RR for all of your LUNs in vSphere. You will see better load balancing on your EVA host ports, and you should also see your HBAs balanced, if you split their zoning across the controllers.

Happy virtualizing!

JP

Please consider awarding points for correct and/or helpful answers

[binoche]

VMW_SATP_ALUA added since vShpere, and the default PSP for ALUA is MRU, so your results on vSphere Update 1 expected;

VMW_SATP_ALUA MRU usually will select Active Optimized path, but Fixed on ESX 3.5 maybe select Active Non-Optimized path

binoche, VMware VCP, Cisco CCNA

[jpdicicco · Accepted solution]

VMW_SATP_ALUA is expected and desirable. The VMW_SATP_EVA is deprecated (see doc referenced in earlier post).

You can use MRU or Fixed from 3.5 hosts and RR from vSphere hosts with no issues. You will want to verify your active controller in CommandView, and make sure that your 3.5 hosts are using a front-end port on that controller so as to not cause controller flapping.

If you haven't, you should read the docs referenced in my previous post.

Happy virtualizing!

JP

Please consider awarding points for correct and/or helpful answers

[njd62495]

I'm going through the docs now.

Thanks for the responses, they've been very helpful.

[INSPSC]

Hello

I am a bit confused to about the SATP with two HP EVAs. One 8000 and one 6400.

All the LUNs have for Storage Array Type VMW_SATP_ALUA - which should be right. I read the HP DOC

But the EVA Array Controllers for the 8000 shows VMW_SATP_EVA – this isn’t right I think because of the HP DOC which says:

VMW_SATP_DEFAULT_AP is the SATP that active/passive EVAs will use. However, active/passive EVAs are not supported with ESX 4.0 thus using this plugin to enable ESX 4.0 connection to an active/passive EVA for production is not recommended. VMW_SATP_EVA has no useful application. It is an SATP for active/active EVA models, which have the TPGS (ALUA compliance) option turned off. By default, all active/active EVAs have the TPGS option turned on and this option is not user configurable. Thus no EVA arrays currently use this specific SATP (VMW_SATP_EVA).

Shouldn’t this also be VMW_SATP_ALUA?

The EVA 6400 shows VMW_SATP_DEFAULT_AA.

So do I have to change the SATP for the EVA Array Controllers?

Regards,

Peter

[binoche]

the expected satp for EVA 6400 is VMW_SATP_ALUA, isn't it?

could you please post the results of esxcli nmp satp listrules and the oldest vmkernel messages /var/log/vmkernel.*? thanks

binoche, VMware VCP, Cisco CCNA

[INSPSC]

Hi

here is the output:

esxcli nmp satp listrules

Name Vendor Model Driver Transport Options Claim Options Description

VMW_SATP_ALUA_CX DGC tpgs_on CLARiiON array in ALUA mode

VMW_SATP_SVC IBM 2145

VMW_SATP_MSA MSA1000 VOLUME

VMW_SATP_EQL EQLOGIC All EqualLogic Arrays

VMW_SATP_INV EMC Invista

VMW_SATP_INV EMC LUNZ Invista LUNZ

VMW_SATP_SYMM EMC SYMMETRIX EMC Symmetrix

VMW_SATP_LSI IBM ^1742* FAStT 700/900

VMW_SATP_LSI IBM ^3542* FAStT 200

VMW_SATP_LSI IBM ^3552* FAStT 500

VMW_SATP_LSI IBM ^1722* FAStT 600/DS4300

VMW_SATP_LSI IBM ^1815* FAStT DS4800

VMW_SATP_LSI IBM ^1724* FAStT 100

VMW_SATP_LSI IBM ^1726-* DS3X00

VMW_SATP_LSI IBM ^1814* DS4000

VMW_SATP_LSI IBM ^1818* DS5100/DS5300

VMW_SATP_LSI Universal Xport FAStT

VMW_SATP_LSI DELL MD3000 Dell MD3000

VMW_SATP_LSI DELL MD3000i Dell MD3000i

VMW_SATP_LSI STK OPENstorage 9176

VMW_SATP_LSI STK OPENstorage D173

VMW_SATP_LSI STK OPENstorage D178

VMW_SATP_LSI STK OPENstorage D210

VMW_SATP_LSI STK OPENstorage D220

VMW_SATP_LSI STK OPENstorage D240

VMW_SATP_LSI STK OPENstorage D280

VMW_SATP_LSI STK BladeCtlr BC82

VMW_SATP_LSI STK BladeCtlr BC84

VMW_SATP_LSI STK BladeCtlr BC88

VMW_SATP_LSI STK BladeCtlr B210

VMW_SATP_LSI STK BladeCtlr B220

VMW_SATP_LSI STK BladeCtlr B240

VMW_SATP_LSI STK BladeCtlr B280

VMW_SATP_LSI STK INF-01-00

VMW_SATP_LSI STK FLEXLINE 380

VMW_SATP_LSI LSI OPENstorage 9176

VMW_SATP_LSI LSI OPENstorage D173

VMW_SATP_LSI LSI OPENstorage D178

VMW_SATP_LSI LSI OPENstorage D210

VMW_SATP_LSI LSI OPENstorage D220

VMW_SATP_LSI LSI OPENstorage D240

VMW_SATP_LSI LSI OPENstorage D280

VMW_SATP_LSI LSI BladeCtlr BC82

VMW_SATP_LSI LSI BladeCtlr BC84

VMW_SATP_LSI LSI BladeCtlr BC88

VMW_SATP_LSI LSI BladeCtlr B210

VMW_SATP_LSI LSI BladeCtlr B220

VMW_SATP_LSI LSI BladeCtlr B240

VMW_SATP_LSI LSI BladeCtlr B280

VMW_SATP_LSI LSI INF-01-00

VMW_SATP_LSI LSI FLEXLINE 380

VMW_SATP_LSI SUN CSM100_R_FC

VMW_SATP_LSI SUN FLEXLINE 380

VMW_SATP_LSI SUN CSM200_R

VMW_SATP_LSI SUN LCSM100_F

VMW_SATP_LSI SUN LCSM100_I

VMW_SATP_LSI SUN LCSM100_S

VMW_SATP_LSI SUN STK6580_6780 Sun StorageTek 6580/6780

VMW_SATP_LSI ENGENIO INF-01-00

VMW_SATP_EVA HSV101 tpgs_off active/active EVA 3000 GL

VMW_SATP_EVA HSV111 tpgs_off active/active EVA 5000 GL

VMW_SATP_EVA HSV200 tpgs_off active/active EVA 4000/6000 XL

VMW_SATP_EVA HSV210 tpgs_off active/active EVA 8000/8100 XL

VMW_SATP_EVA HSVX740 tpgs_off active/active HP StorageWorks SVSP

VMW_SATP_DEFAULT_AP DEC HSG80

VMW_SATP_DEFAULT_AP HSV100 active/passive EVA 3000 GL

VMW_SATP_DEFAULT_AP HSV110 active/passive EVA 5000 GL

VMW_SATP_DEFAULT_AP HSVX700 tpgs_off active/passive HP StorageWorks SVSP

VMW_SATP_CX DGC tpgs_off All non-ALUA Clariion Arrays

VMW_SATP_ALUA HSV101 tpgs_on EVA 3000 GL with ALUA

VMW_SATP_ALUA HSV111 tpgs_on EVA 5000 GL with ALUA

VMW_SATP_ALUA HSV200 tpgs_on EVA 4000/6000 XL with ALUA

VMW_SATP_ALUA HSV210 tpgs_on EVA 8000/8100 XL with ALUA

VMW_SATP_ALUA HSV300 tpgs_on EVA 4100/4400 with ALUA

VMW_SATP_ALUA HSV400 tpgs_on EVA 6400 with ALUA

VMW_SATP_ALUA HSV450 tpgs_on EVA 8400 with ALUA

VMW_SATP_ALUA NETAPP tpgs_on NetApp with ALUA

VMW_SATP_ALUA HP ^MSA2* tpgs_on HP MSA A/A with ALUA

VMW_SATP_ALUA HP MSA 3G SAS Cntlr tpgs_on HP MSA A/A with ALUA

VMW_SATP_ALUA HSVX700 tpgs_on active/passive HP StorageWorks SVSP with ALUA

VMW_SATP_ALUA HSVX740 tpgs_on active/active HP StorageWorks SVSP with ALUA

VMW_SATP_ALUA Intel Multi-Flex tpgs_on Intel Promise

VMW_SATP_ALUA FUJITSU tpgs_on ETERNUS with ALUA

VMW_SATP_ALUA HSV340 tpgs_on EVA 4600 with ALUA

VMW_SATP_ALUA HSV360 tpgs_on EVA 6600 with ALUA

VMW_SATP_DEFAULT_AA fc Default for Fibre Channel

VMW_SATP_DEFAULT_AA iscsi Default for iSCSI

VMW_SATP_DEFAULT_AA IBM SAS SES-2 DEVICE IBM SAS SES-2

VMW_SATP_DEFAULT_AA IBM 1820N00 IBM BCS RSSM

VMW_SATP_DEFAULT_AA HITACHI

VMW_SATP_LOCAL usb USB Devices

VMW_SATP_LOCAL ide IDE Devices

VMW_SATP_LOCAL block RAID Block Devices

VMW_SATP_LOCAL parallel Parallel SCSI Devices

VMW_SATP_LOCAL sas Serial Attached SCSI Devices

VMW_SATP_LOCAL sata Serial ATA Devices

VMW_SATP_LOCAL unknown Unknown Devices

[binoche]

VMW_SATP_ALUA HSV400 tpgs_on EVA 6400 with ALUA

this claimrule looks like correct;

could you please post the oldest vmkernel messages /var/log/vmkernel.*? thanks

[INSPSC]

the oldest kernel log is attatched

[binoche]

thanks;

here is part of vmkernel,

...

Nov 23 18:25:31 hzvm0006 vmkernel: 0:00:00:33.565 cpu1:4211)ScsiScan: 843: Path 'vmhba2:C0:T0:L0': Vendor: 'HP ' Model: 'HSV210 ' Rev: '6110'

Nov 23 18:25:31 hzvm0006 vmkernel: 0:00:00:33.565 cpu1:4211)ScsiScan: 846: Path 'vmhba2:C0:T0:L0': Type: 0xc, ANSI rev: 5, TPGS: 0 (none)

Nov 23 18:25:31 hzvm0006 vmkernel: 0:00:00:33.566 cpu1:4211)ScsiScan: 843: Path 'vmhba2:C0:T0:L1': Vendor: 'HP ' Model: 'HSV210 ' Rev: '6110'

Nov 23 18:25:31 hzvm0006 vmkernel: 0:00:00:33.566 cpu1:4211)ScsiScan: 846: Path 'vmhba2:C0:T0:L1': Type: 0x0, ANSI rev: 5, TPGS: 3 (implicit and explicit)

...

Nov 23 18:25:32 hzvm0006 vmkernel: 0:00:00:37.801 cpu4:4110)VMW_SATP_EVA: satp_eva_alloc_path: Path vmhba2:C0:T0:L0 has devclass 0xc; marking device as management lun

...

no lun 0 looks like been assigned to this esx, could you please recheck what are the result when real lun 0 assigned? thanks

binoche, VMware VCP, Cisco CCNA

[INSPSC]

Hi

don't know what you mean.The Array Controller itself is LUN0

[binoche]

does it mean no real lun 0 can be assigned from EVA?

could you please run vm-support and upload its .tgz? thanks

binoche, VMware VCP, Cisco CCNA

[binoche]

also this vmkernel has the below message,

Nov 23 18:25:33 hzvm0006 vmkernel: 0:00:00:37.855 cpu5:4110)vmw_psp_mru: psp_mruSelectPathToActivateInt: Changing active path from NONE to vmhba1:C0:T1:L8 for device "Unregistered Device".

VMW_SATP_DEFAULT_AA its default psp is Fixed, why mru here? did you change some configurations?

binoche, VMware VCP, Cisco CCNA

[binoche]

vSphere Update 2 maybe fix this issue, thanks

binoche, VMware VCP, Cisco CCNA