Unsolved
117 Posts
0
2267
Any known issues with ESXi 6.5U3 and MEM 1.5?
I just updated one of our hosts to 6.5U3. I have a mix of EqualLogic and Compellent iSCSI datastores. Exiting maintenance mode resulted in a hang, and the process never finished. There are several errors in the vmkernel/hostd logs that point to the EqualLogic datastores, and specifically the MEM module:
2019-07-25T20:04:00.468Z info hostd[104C2B70] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 201 : Path redundancy to storage device naa.60fff18a0e80b172c3be25cfdd6eedb8 degraded. Path vmhba64:C0:T17:L0 is down. Affected datastores: eql-ssd-03.
2019-07-25T20:04:00.755Z info hostd[104C2B70] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 202 : Path redundancy to storage device naa.6090a0c840d7b406555315b4900520de degraded. Path vmhba64:C0:T3:L0 is down. Affected datastores: prod-r10-esxi-02.
---
2019-07-25T20:04:00.211Z cpu0:66640)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Sess [ISID: 00023d000001 TARGET: iqn.2001-05.com.equallogic:0-af1ff6-72b1800e8-b8ed6eddcf25bec3-eql-ssd-03 TPGT: 1 TSIH: 0]
2019-07-25T20:04:00.211Z cpu16:66103)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: 00023d000001 TARGET: iqn.2001-05.com.equallogic:0-af1ff6-72b1800e8-b8ed6eddcf25bec3-eql-ssd-03 TPGT: 1 TSIH: 0]
2019-07-25T20:04:00.466Z cpu15:65642)WARNING: dell_psp_eql_routed: psp_eqlUpdatePathSelection:1293: Path is reported as inactive (0x50475304)
2019-07-25T20:04:00.753Z cpu0:65641)WARNING: dell_psp_eql_routed: psp_eqlUpdatePathSelection:1293: Path is reported as inactive (0x50475304)
I just wanted to reach out to see if there were any known issues before I troubleshoot this further on my own.
dwilliam62
1 Rookie
1 Rookie
•
1.5K Posts
0
July 25th, 2019 19:00
bealdrid2
117 Posts
0
July 26th, 2019 06:00
Hi Don.
I have two groups. One is single-member, the other has 5 members with 3 pools. The SC array is setup with two fault domains, but only one subnet, and that /24 subnet is shared with the EqualLogic arrays as well. (this config was required for PS coexistance). I wasn't aware that we should not be using MEM. I did reboot that host and seems like things have started functioning, but if I should not use MEM along with the SC arrays in the picture, I will remove it and use native MPIO similar to compellent. At this point I don't trust the host to let it run like this.
bealdrid2
117 Posts
0
July 26th, 2019 07:00
Also just FYI, the doc at https://downloads.dell.com/solutions/storage-solution-resources/BPforPS_SC_CoexistenceESXiHostAndiSCSI_SAN(2015-A-BP-INF)v4.pdf suggests that MEM is supported for use when sharing PS and SC series SANs. See section 4.
ChadCorkrum
24 Posts
0
July 27th, 2019 09:00
I'm curious, is not using MEM recommended if you're not running in mixed mode with PS and SC? Reading the manual they go over a new command:
setup.pl --configure –-disable --RR
Does DELL_PSP_EQL_ROUTED auto-configure IOPS?
I was looking at the result of running the following and DELL_PSP_EQL_ROUTED looks to not show or have any configuration.
Device Display Name: EQLOGIC iSCSI Disk (naa.6019cb5170e35b4aafbbe50a000060cc)
Storage Array Type: VMW_SATP_EQL
Storage Array Type Device Config: {action_OnRetryErrors=off}
Path Selection Policy: DELL_PSP_EQL_ROUTED
Path Selection Policy Device Config: PSP DELL_PSP_EQL_ROUTED does not support device configuration.
Path Selection Policy Device Custom Config:
Working Paths: vmhba68:C1:T2:L0, vmhba68:C0:T2:L0
Is USB: false
Device Display Name: EQLOGIC iSCSI Disk (naa.6019cb5170e35b4aafbbe50a000060cc)
Storage Array Type: VMW_SATP_EQL
Storage Array Type Device Config: {action_OnRetryErrors=off}
Path Selection Policy: VMW_PSP_RR
Path Selection Policy Device Config: {policy=iops,iops=3,bytes=10485760,useANO=0; lastPathIndex=1: NumIOsPending=0,numBytesPending=0}
Path Selection Policy Device Custom Config:
Working Paths: vmhba68:C1:T2:L0, vmhba68:C0:T2:L0
Is USB: false
dwilliam62
1 Rookie
1 Rookie
•
1.5K Posts
0
July 27th, 2019 14:00
Hello,
Yes MEM sets a lower IOs per path value. It's based on a much different algorithm than simply switching paths every so often. It uses the paths to send or receive data from the member having that data when you have multimember pools. But even single member pools are optimized automatically with MEM
Regards,
Don
ChadCorkrum
24 Posts
0
July 27th, 2019 19:00
Do you have to do anything after just installing MEM?
Build wise I usually install ESXi, create the vSwitch and PortGroups and configure jumbo frames, assign the PortGroups to the iSCSI software initiator and then join vCenter, update the host, install MEM and iSM and migrate to a dvSwitch and join a cluster.
I've never done anything more than install MEM and noticed it changes to the DELL_PSP_EQL_ROUTED policy and I call the job complete.
Using VMW_PSP_RR with the recommended configuration the VMs actually feel faster, now I feel like I might have been missing a step.
dwilliam62
1 Rookie
1 Rookie
•
1.5K Posts
0
July 28th, 2019 01:00
Hello,
No further configuration is required after install MEM. It optimizes on the fly based on storage configuration.
Regards,
Don