The arrays were bought after market, I just checked and the support expired 4 years ago. I suppose this means that updates are not an option. The clients are running Debian Linux 8. I am seeing internally what is required to take it off the internet. One option seems to be to disable the default gateway, but I can see how to confirm the current setting before doing a "def-gateway none"
I'm curious as to how often these events occur for you. I had similar issues with my PS6510/6500 arrays. Same deal; had them in different locations, saw similar behavior. For me it was 20-30s of random pauses a couple times a day. The duration of the hang/pause was directly related to how much free space there was on the array. At times we saw hangs upwards of 25-30s; then as we were in the process of vacating it, the hang times would gradually go down to 10-15s as the "in-use" space decreased. I also noticed active page movement (replication, balancing) between arrays caused the frequency of these "hangs" to go up. Say from 1/day to 1/hour. I had a case open a LONG time; we got sidetracked due to other issues, but still they could never get to the bottom of it. The issue was observed with all OS's- ESXi, RHEL, Windows, etc which all had best practices set. Our other PS6210 arrays never did this and they used all the same switches, were even in the same group. My belief is there is some fundamental issue with the PS6500/6510 series array controllers. Maybe the 6000's have the same thing.
Maybe I can add a few details. I realize you said that it can't be a network issue, but check these just in case:
1. Check the PS6000 system event log in the GUI. See what is happening at the time of the long delays
2. Are there iSCSI connection drops?
3. When the delays occur, have the hosts ping the PS6000 active eth interfaces to see if a response comes back. Just checking to see if the interfaces are still operational during the long pauses.
4. On the EQL GUI Network Tab, check the error counter for each eth interface and make sure it is not incrementing.
timdau1
4 Posts
0
October 3rd, 2017 09:00
timdau1
4 Posts
0
October 3rd, 2017 15:00
Any suggestions for troubleshooting beyond buying a support contract?
bealdrid2
1 Rookie
•
117 Posts
0
October 3rd, 2017 17:00
I'm curious as to how often these events occur for you. I had similar issues with my PS6510/6500 arrays. Same deal; had them in different locations, saw similar behavior. For me it was 20-30s of random pauses a couple times a day. The duration of the hang/pause was directly related to how much free space there was on the array. At times we saw hangs upwards of 25-30s; then as we were in the process of vacating it, the hang times would gradually go down to 10-15s as the "in-use" space decreased. I also noticed active page movement (replication, balancing) between arrays caused the frequency of these "hangs" to go up. Say from 1/day to 1/hour. I had a case open a LONG time; we got sidetracked due to other issues, but still they could never get to the bottom of it. The issue was observed with all OS's- ESXi, RHEL, Windows, etc which all had best practices set. Our other PS6210 arrays never did this and they used all the same switches, were even in the same group. My belief is there is some fundamental issue with the PS6500/6510 series array controllers. Maybe the 6000's have the same thing.
timdau1
4 Posts
0
October 3rd, 2017 18:00
I think we have sufficient space, more than 1TB free at least. How much do you recommend?
TotalSpace: 5.1TB
UsedSpace: 3.08TB
SnapSpace: 603.63GB
dell-richard g
605 Posts
0
October 3rd, 2017 18:00
Maybe I can add a few details. I realize you said that it can't be a network issue, but check these just in case:
1. Check the PS6000 system event log in the GUI. See what is happening at the time of the long delays
2. Are there iSCSI connection drops?
3. When the delays occur, have the hosts ping the PS6000 active eth interfaces to see if a response comes back. Just checking to see if the interfaces are still operational during the long pauses.
4. On the EQL GUI Network Tab, check the error counter for each eth interface and make sure it is not incrementing.
5. Have the PS6000 been rebooted recently?