We could see following error message appearing in the logs when any config changes were being done on the Primary through GUI or CLI.



Secondary NetScaler VPX was showing in the sync state : inprogress


Could also see following messages appearing just before the operation time-out message:

Reboot the secondary NetScaler VPX in order to take it out from the HUNG state.

---

Problem Cause

Secondary NetScaler VPX was found in the hung state and unreachable from the Primary instance of the NetScaler due to which the Primary NetScaler was not able to propagate the commands to the other pair in the HA. Hence it was showing the error message as Operation timed out when making any changes in the config of the Primary. At the same time we could see some  SNMP alert has been triggering  for  haPropFailure (This trap indicates that config propagation has failed on secondary) and Write failed because of broken pipe in nsnet_sendack; FD=20 errno=32 peerPort=-1 peerProcess=?? in the ns.log.