In a high-availability (HA) socket deployment, we may observe instances where both the primary and secondary sockets undergo reconnection, as depicted in the following events:
This article will discuss the possible reasons.
Following are some of the possibilities that the tunnels from both sockets will reconnect at the same time:
- Both sockets are connected to the same upstream device and it's possible that this common device experienced a glitch, impacting the connectivity from both sockets
- This situation is somewhat similar to point 1, wherein both sockets connect to the same Internet Service Provider (ISP), and there may be an issue with a shared component within the ISP infrastructure, leading to the reconnection of both sockets.
- The PoP becomes unavailable for some reasons and both sockets will reconnect to another PoP.
- The primary socket experienced a connection problem, which could have arisen from various factors such as ISP link issues, hardware problems, and more. Once the primary socket successfully reconnected, it directed the secondary socket to follow suit. Consequently, both sockets show a "Reconnected" status in the event. This is the expected behavior.