| HPE Storage Users Group https://3parug.com/ |
|
| 3PAR/Proliant Fileserver https://3parug.com/viewtopic.php?f=18&t=2625 |
Page 1 of 1 |
| Author: | rbird97 [ Mon Aug 21, 2017 11:20 am ] |
| Post subject: | 3PAR/Proliant Fileserver |
Hello, We have a proliant file server appliance and it uses 3PAR storage. We are having a unique problem with one of the hosts. The hosts are in a file cluster. One of the hosts LUNs become slow. 3000 to 4000 ms access times from the hosts not the arrays. If we move the LUNs to other side of the file cluster no problems speed is normal. If we create a new LUN and add it to the affected host, also no issues. We seem to only have issues when it is the affected host LUN to the affected host. Has anyone come across this issue before? Is there anyone I can test the LUN from the 3PAR side to see if there problems with it? |
|
| Author: | JohnMH [ Tue Aug 22, 2017 3:46 am ] |
| Post subject: | Re: 3PAR/Proliant Fileserver |
There's not much to go on but assuming connectivity is good then it sounds more like a windows problem, in effect you've proved the array is ok by moving the volumes to another cluster node. I'd start by looking in the Windows event log on that node and start troubleshooting this at the OS level. Assuming it's a StoreEasy worst case think about rebuilding the effected node via the recovery image. https://h20392.www2.hpe.com/portal/swdepot/displayProductsList.do?category=NAS |
|
| Author: | rbird97 [ Wed Aug 23, 2017 1:28 pm ] |
| Post subject: | Re: 3PAR/Proliant Fileserver |
We have come to the conclusion that there is something wrong with the one host in the file cluster. We are still waiting for HP to come back with some kind of idea of what is wrong. Has anyone used File Persona did NFS shares from the 3PAR? |
|
| Author: | aDelaloy [ Thu Aug 24, 2017 9:34 am ] |
| Post subject: | Re: 3PAR/Proliant Fileserver |
rbird97 wrote: We have come to the conclusion that there is something wrong with the one host in the file cluster. We are still waiting for HP to come back with some kind of idea of what is wrong. Hello, have you checked the Windows MPIO settings on the host for the affected LUN ? because we had a similar problem on a Windows 2012R2 hyper-V cluster and two replicated 3par arrays with Peer Persistence ,since the end of June ( some Microsoft securty patch bundle included a MPIO change?) : in our case, it turns out on some LUNs sometimes the Windows policy wrongly changed itself from RRSW (roundrobin with subset) to plain round robin : so it tried to use the passive path , with a ~3 000 ms timeout before going to the next path. the I/O doesnt truly fail , it is just slow... also, if your LUN is disk8 type the powershell command mpclaim -s -d 8 and check for any discerpancy bettwed the "actual" and "desired" state for each of its paths (sorry, my servers are in french) |
|
| Author: | rbird97 [ Wed Sep 06, 2017 1:07 pm ] |
| Post subject: | Re: 3PAR/Proliant Fileserver |
Just an update we think we found the solution thanks to the post above about looking at MPIO drivers. Found the following in an HPE document HPE 3PAR Peer Persistence HPE 3PAR Peer Persistence enables HPE 3PAR StoreServ Storage systems located at metropolitan distances to act as peers to each other, presenting a nearly continuous storage system to hosts and servers connected to them. This capability allows customers to configure a high-availability solution between two sites or data centers, where switchover and switchback remain transparent to the hosts and applications running on those hosts. CAUTION: Path Verify Enabled must be set in the MPIO settings on Windows Server 2016/2012/2008 hosts configured for an HPE 3PAR Peer Persistence implementation. To configure the Path Verify Enabled MPIO setting: • With Windows Server 2016/2012, the setting can be found at Device Manager > Disk Drives. Right-click any of the HPE 3PAR disks, select MPIO > MS DSM Details, and then select the Path Verify Enabled check box. • With Windows Server 2008, the setting can be found at Server Manager > Disk Management. Right-click any of the HPE 3PAR disks, select MPIO > MS DSM Details, and then select the check box. We checked off the box on the servers and rebooted. Problem went away no slowness at all |
|
| Author: | 3par3 [ Sat Nov 25, 2017 1:08 pm ] |
| Post subject: | Re: 3PAR/Proliant Fileserver |
aDelaloy wrote: rbird97 wrote: We have come to the conclusion that there is something wrong with the one host in the file cluster. We are still waiting for HP to come back with some kind of idea of what is wrong. Hello, have you checked the Windows MPIO settings on the host for the affected LUN ? because we had a similar problem on a Windows 2012R2 hyper-V cluster and two replicated 3par arrays with Peer Persistence ,since the end of June ( some Microsoft securty patch bundle included a MPIO change?) : in our case, it turns out on some LUNs sometimes the Windows policy wrongly changed itself from RRSW (roundrobin with subset) to plain round robin : so it tried to use the passive path , with a ~3 000 ms timeout before going to the next path. the I/O doesnt truly fail , it is just slow... also, if your LUN is disk8 type the powershell command mpclaim -s -d 8 and check for any discerpancy bettwed the "actual" and "desired" state for each of its paths (sorry, my servers are in french) Did you find a solution to the problem with the load balancing policy wrongly switching to Round Robin instead of Round Robind with Subset (RRWS) ? I have the same problem on some LUNs, and a reboot of the hosts is not fixing it. |
|
| Page 1 of 1 | All times are UTC - 5 hours |
| Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group http://www.phpbb.com/ |
|