HPE SimpliVity Virtual Controller having significant socket leak

[ErwinH]

Hi all,

After a long time I am posting again! We recently rolled out 3 new DL380GEN10+ servers with the latest version (5.1. 0U1) of Simplivity. The deployment went without any problems and there are now 70 VMs running globally. However, after migrating the VMs from the 'old' custer to the 'new' cluster we saw a day later the warning 'HPE SimpliVity Virtual Controller having significant socket leak'! In the 8 years we are using Simplivity i never seen this warning. We have of course already reported this to support (three weeks ago) but there is no solution yet! My question is, are there members who may also have (or had) this issue?

Kind regards,
Erwin

[NeetSat]

Hi ErwinH,
Good day. 
I was going through the details you mentioned and the information is actually mentioned on the 5.1.0U1 Events release section: 
https://support.hpe.com/hpesc/public/docDisplay?docId=sd00004301en_us&docLocale=en_US&page=GUID-AAB1A186-F3A2-4995-8B60-03D6057C3BF2.html

So in this section, it talks about the data where in one has to shutdown the OVC in a safe way and then proceed to reboot the host. You can clear the message as "Reset to Green" before rebooting the host and once the host is back up and running along with the OVC, monitor it for a day or couple of hours, you shall see if that resolves the issue or not. 

If that doesnt work, then basically we have to reach out to the support team for further investigation, since we need to see what may be causing the issue.

[ErwinH]

Hi Neetesh,

As I indicated earlier this issue is already known to support. A restart of the OVC solves the problem temporarily, but after about 7 hours the message appears again on all three hosts. What I have not tried yet is to also restart the host, but I also assume that I should also get this action from support?

Kind regards,

Erwin

[NeetSat]

Hi Erwin,

Usually is a thing where the task has been closed on the application (here OVC) but the host hasnt responded to it as a closure, so thats what in simple terms the issue would mean. 

Well rebooting the host is already mentioned on the link i provided above and i think it should be fine and you can reboot the host maybe during the production hours by migrating all VMs or maybe off-production hours. 
But we need to monitor it for a couple of hours or maybe a day max once the host is rebooted as well. 
https://support.hpe.com/hpesc/public/docDisplay?docId=sd00004301en_us&page=GUID-0C35A578-9E38-4932-BA2A-9DCDE96A6594.html

 
Since it requires some in-depth checks to see what maybe causing this issue, so we need support team to look into it. 
Btw, you can help me with the case number that you have with support team and I check on it to let you know as to whats happening on it. 

[ErwinH]

Hi Nateesh,

The case is 5386229710

Regards,
Erwin

[NeetSat]

Hi Erwin,
I did have a check on this case and also had a discussion with the engineer working on it. 
So as informed earlier, they are already discussing with the L3 team and shall get back to you soon with a POA.
Apologies for any delay, but rest assured, the team is working on it and shall let you know the next POA.

[NeetSat]

Hi Erwin,
Good day. 
I see there is progress on the existing case 5386229710. 
Since the support team is already working on it, I would suggest, that we proceed with closing this query here.

[ErwinH]

Hello neetesh,

Yes thats ok! Apparently we are the only ones experiencing this issue?

Kind regards,

Erwin

[NeetSat]

Hi Erwin,
Thank you for confirmation, we shall proceed to close the query.
Please note, the ticket with support team will be active and wouldn't be affected with us closing this query.
As for the issue, well, i would say, a couple of other users too have experienced it and since i see, the L3/ERT team is also involved and giving the suggestions/ troubleshooting, i am sure, it may have taken time, but the issue will be resolved. 

[support_s]

Hello,

Let us know if you were able to resolve the issue.

If you have no further query, and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[ErwinH · Accepted solution]

Yes, the problem has been solved since yesterday. In the end, an installed QNAP Vaai plugin turned out to be the culprit. We had installed this plugin right after the deployment, for a certain reason! In retrospect, this was not a smart move. A comment from L3 pointed us in the right direction, which made us realize that it could be that plugin. Fortunately, it is now solved!

[Sunitha_Mod]

Hello @ErwinH,

That's Excellent! 

We are extremely glad to know the issue has been resolved.