Thanks, I will probably do so when we get the firmware updated as that is tyicpally supports goto answer for everything, even if the notes don't mention the specific issue we are having at the time.
Yeah, thats the guide I used to check our settings. We are seeing this on the newer and older volumes, and after I last updated the MEM I went back and verified that all the older datastores had the proper configuration. However I will try removing the targets again on a few hosts and see if we notice any difference after adding it back in.
Most of our servers have the C:\ on one scsi controller and other disks on a different one or two depending on the server. Thank you for your reply.
The IO's seem to be fairly consistent. Even when I see an IO spike I don't always see a latency increase, or at least not much of one in either vmware or SANHQ.
So for the old iscsi settings in the DB, even if I changed those in the vsphere client are you saying they still might persist on the hosts?
Like I said, they are about normal. The IOP's on all our sans except one are "low" by SANHQ's measurements, and usually only a fraction of what the estimated overall total IOP count can max out at. The other ones has only gotten to about 50-60% of it's IOP max.
I guess I don't understand why it would still say those settings are configured properly after a reboot if it was populating that data from a database that had the old settings in it. I'm 99% sure we used a script after the last MEM upgrade to make sure all our older Datastores were given the new settings. But it won't cost us much to try it so I'll give it a go. And I believe that the MEM auto configures those settings for any equallogics no?
admlshake
1 Rookie
•
57 Posts
0
September 21st, 2017 08:00
Thanks, I will probably do so when we get the firmware updated as that is tyicpally supports goto answer for everything, even if the notes don't mention the specific issue we are having at the time.
Yeah, thats the guide I used to check our settings. We are seeing this on the newer and older volumes, and after I last updated the MEM I went back and verified that all the older datastores had the proper configuration. However I will try removing the targets again on a few hosts and see if we notice any difference after adding it back in.
Most of our servers have the C:\ on one scsi controller and other disks on a different one or two depending on the server. Thank you for your reply.
admlshake
1 Rookie
•
57 Posts
0
September 21st, 2017 09:00
The IO's seem to be fairly consistent. Even when I see an IO spike I don't always see a latency increase, or at least not much of one in either vmware or SANHQ.
So for the old iscsi settings in the DB, even if I changed those in the vsphere client are you saying they still might persist on the hosts?
admlshake
1 Rookie
•
57 Posts
0
September 21st, 2017 11:00
Like I said, they are about normal. The IOP's on all our sans except one are "low" by SANHQ's measurements, and usually only a fraction of what the estimated overall total IOP count can max out at. The other ones has only gotten to about 50-60% of it's IOP max.
I guess I don't understand why it would still say those settings are configured properly after a reboot if it was populating that data from a database that had the old settings in it. I'm 99% sure we used a script after the last MEM upgrade to make sure all our older Datastores were given the new settings. But it won't cost us much to try it so I'll give it a go. And I believe that the MEM auto configures those settings for any equallogics no?