SDM/SDC not reconnecting automatically through Virtual IP
Article ID: 128473
Updated On:
Products
Spectrum
Issue/Introduction
We have devices modeled through Secure Domain connectors using Virtual IP ports. There was an issue where the Virtual IP ports went down, and upon bringing the Virtual Ports back up, SDM/SDC did not automatically re-establish a connection. Why?
Environment
Release:
Component: SPCCSS
Component: SPCCSS
Resolution
The SDC debug is showing a failed connection on established socket reference:
WARNING: socket closed and invalid.
WARNING: Socket error: 111
When the Virtual IP port went down, the existing socket reference used by the SDC connection was lost. Upon bring the Virtual IP back up, it does not re-use the same socket reference.
A restart of SDC is required to re-establish a new socket reference and establish a connection back to Secure Domain Manager.
WARNING: socket closed and invalid.
WARNING: Socket error: 111
When the Virtual IP port went down, the existing socket reference used by the SDC connection was lost. Upon bring the Virtual IP back up, it does not re-use the same socket reference.
A restart of SDC is required to re-establish a new socket reference and establish a connection back to Secure Domain Manager.
Feedback
Yes
No
Powered by
