So in case you didn't notice if you are monitoring netapp's or anything else that uses a SSL/TLS connection to the API of the device you might have noticed they stopped polling.
Here is the error in the SRM Logs
2016-11-21 06:15:36,416 [STP SmartThreadPool Thread #2] ERROR SolarWinds.SRM.NetAPP.NetAppServerBase - Failed invoking API
NetApp.Manage.NaException: Failed invoking API ---> System.Net.WebException: The request was aborted: Could not create SSL/TLS secure channel.
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
--- End of inner exception stack trace ---
at NetApp.Manage.NaServer.InvokeElem(NaElement element)
at SolarWinds.SRM.NetAPP.NetAppServerBase.InvokeCommand(String apiName, IList`1 outputAttributes, IList`1 parameters)
This is mainly due to a security update in Windows for longer certs to be required below are the updates that are applicable and the document about the update.
2012 R2 and Windows 8
2008 R2 and Windows 7
To fix this instead of uninstalling some critical updates that provide stronger security all you need to do is update the certs to 2048 bytes and at least SHA-2. I hope this helps some people as it drove me crazy for a while.
Here is the doc to update the NetApp certs http://www.regmen.com/upload-ssh-keys-netapp-7-mode/
Nope just had to update the certs on the client devices, its better that way to stay security compliant. A lot of people have just been uninstalling the updates which is a bad practice.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.