Hi everyone!
The current infrastructure has a following build-up (R80.40): two management servers in the HA pair, two clustered gateways (6000 appliances; active & standby), and a standalone gateway. Previously, the HQ SMS suffered a failover to the DR SMS. We had to create a fresh instance of the HQ SMS, enable the HA pair again (sync was made from the DR to the new HQ), and switch back the places of the primary and secondary SMS (HQ -> to primary; DR -> to secondary).
As of now, HQ SMS tries to communicate with the cluster through the direct IP of the cluster member and has the following issue:
![Screenshot_5.png Screenshot_5.png](https://community.checkpoint.com/t5/image/serverpage/image-id/20943i021096FDA0F686BD/image-size/large?v=v2&px=999)
DR SMS (secondary) does not have any connectivity issues and speaks to the cluster member through a management IP (e.g, 192.168.2.1) configured under the Network Management tab:
![photo_2023-05-16_11-57-55.jpg photo_2023-05-16_11-57-55.jpg](https://community.checkpoint.com/t5/image/serverpage/image-id/20944i34CE75922FE3DB20/image-size/medium?v=v2&px=400)
SIC is working properly (Trust Established for the HQ SMS). The logs keep coming from the cluster to the HQ SMS on port 257. Whenever the SIC status is tested, policy is being pushed or interfaces are being fetched, the SmartConsole goes idle and throws errors, specifying that there is no connection between the SMS and the cluster (e.g., on port 18191).
Taking into consideration that the Network Management is identical between the HQ and DR, is there a way to specify from the HQ SMS side the management IP (same as on DR side) as the proper IP address to establish the communication with the cluster?