search cancel

unable to connect to SDN Gateway through webSocket error in logs

book

Article ID: 253167

calendar_today

Updated On:

Products

CA Spectrum

Issue/Introduction

After testing the connection and save the VNA Configuration in OneClick, the integration is not working, and next error is seen in logs:

Oct 14, 2022 16:12:32.060 (Thread-22) (SDIntegration) - Tomcat started. Starting NIM initilization
Oct 14, 2022 16:12:33.044 (PoolThread-2: GlobalPool => SDNIntegrationServlet) (SDNIntegrationServlet) - Number of inventory objects created: 1
Oct 14, 2022 16:12:33.107 (PoolThread-2: GlobalPool => SDNIntegrationServlet) (SDNIntegrationServlet) - Loading user domain mapping to inventory...
Oct 14, 2022 16:12:33.107 (PoolThread-2: GlobalPool => SDNIntegrationServlet) - Registering for Notification Updates ...
Oct 14, 2022 16:12:39.621 (PoolThread-2: GlobalPool => SDNIntegrationServlet) (SDNIntegrationServlet) -  unable to connect to SDN Gateway through webSocket
javax.websocket.DeploymentException: SSL handshake has failed
...
Caused by: javax.net.ssl.SSLHandshakeException: No subject alternative DNS name matching vnaserver.mydomain.com found.
...
Oct 14, 2022 16:13:40.617 (PoolThread-2: GlobalPool => SDNIntegrationServlet) (SDNIntegrationServlet) -  unable to connect to SDN Gateway through webSocket
out 14, 2022 4:14:40 PM org.glassfish.grizzly.nio.transport.TCPNIOTransport$DefaultChannelConfigurator postConfigure
WARNING: GRIZZLY0005: Can not set SO_KEEPALIVE to true
java.net.SocketException: Invalid argument: no further information
...
Oct 14, 2022 16:14:40.654 (PoolThread-2: GlobalPool => SDNIntegrationServlet) (SDNIntegrationServlet) -  unable to connect to SDN Gateway through webSocket
Oct 14, 2022 16:15:40.672 (PoolThread-2: GlobalPool => SDNIntegrationServlet) (SDNIntegrationServlet) -  unable to connect to SDN Gateway through webSocket
Oct 14, 2022 16:20:40.704 (PoolThread-2: GlobalPool => SDNIntegrationServlet) (SDNIntegrationServlet) -  unable to connect to SDN Gateway through webSocket

 

Environment

Release : 22.2

Cause

This issue occurs if the CN or the SAN on the VNA certificate does not contain the name set on the VNA Server Host  Name configured in VNA Configuration page in OneClick

Resolution

To correct the problem, one option is

- Make sure the VNA certificate has the VNA FQDN as CN or as SAN

Another option if the VNA certificate only includes the hostname as CN or SAN is

- Disable the integration 
   How to fully disable and reenable the VNA Integration in Spectrum
  https://knowledge.broadcom.com/external/article?articleId=190460

- Configure the integration using the VNA hostname

Attachments