Network Management
Connection attempt failed! Unknown error during F5 iControl test
Connection attempt failed! Unknown error during F5 iControl test. When trying to add F5 credentials in the Orion web console you get the following error Connection attempt failed! Unknown error during F5 iControl test.
First published date
Last published date
Overview
Connection attempt failed! Unknown error during F5 iControl test
Errors
WARN SolarWinds.F5.Pollers.API.F5ApiClient -
Test connection failed for https://"F5 IP Address"
Error: Solarwinds.F5.Common.Models.API.F5ApiException: Unknown error during F5 iControl
request.
at SolarWinds.F5.Pollers.API.F5ApiClient.Execute(RestApiRequest request)
at SolarWinds.F5.Pollers.API.F5ApiClient.GetData(String path)
at SolarWinds.F5.Pollers.API.F5ApiClient.TestConnection().
ERROR SolarWinds.F5.Pollers.API.F5ApiClient - Invalid response from https://"F5 IP Address"/:
Status=0, Content=, ErrorMessage=Error executing HTTP Web Request.
URL: https://"F5 IP Address"/mgmt/tm/ltm/, ErrorException=System.Net.WebException:
The request was aborted: Could not create SSL/TLS secure channel.
Product section
Cause
- The F5 SSL certificate is an MD5 certificate, and the Microsoft .NET version on the Orion Server is 4.6 or later.
- Microsoft .NET Framework 4.6 adds TLS 1.2, and TLS 1.2 does not support MD5 certificate authentication.
- The .NET Framework 4.6 adds TLS 1.1 and TLS 1.2 to the WCF SSL protocol default list.
- There is no TLS configured on the Polling Engine
For more info please see this Microsoft Post (©03/30/2017 Microsoft, available at https://docs.microsoft.com, obtained on 22/09/2017).
Resolution
- Use RESTWalker to verify the connection and collect other information to the target F5, below is a KB article taht may use:
How to use SolarWinds REST Walker - In an event that RestWalker does not able to connect or collect information, make sure there is a TLS configured on the Polling Engine
- From the Orion Server, browse to the F5 API using Internet Explorer.
- When the page loads, select the padlock icon from the browser address bar and select view certificate.
- Go to the details tab.
- Check the signature hash algorithm.
- If it is MD5, then the issue is that the certificate is not supported by .NET 4.6.
- To check the .NET version, please see the following Microsoft support doc (©08/09/2017 Microsoft, available at https://docs.microsoft.com, obtained on 22/09/2017).
- If the certificate is MD5, please contact F5 to have this upgraded to a supported certificate or revert to .NET 4.5