When they log-in to UMA from UMC, WAA under the UMA disconnected. What is this cause? Does UMA reconnect to WAA?

When they log-in to UMA from UMC, WAA under the UMA disconnected. What is this cause? Does UMA reconnect to WAA?

Question:

When they log-in to UMA from UMC, WAA under the UMA disconnected. What is this cause? Does UMA reconnect to WAA?

 

Answer:

When UMA is disconnected from WAA unexpectedly, by default UMA would retry the connection for up to 5 times with a 1 second interval between each retry. Once all the retries have been attempted, UMA would stop the connection. 

 

To ensure a higher chance of re-connectivity, please increase the number of times and the interval to maybe 1 minute.

 

More information:

N/A

    • Related Articles

    • UMA / UMC Compatibility between v4.1 and v4.3

      Questions & Answers: 1. Does UMA ver4.3(.1) compatible with UMC v4.1?      No. The UMC has to be upgraded to v4.2 or v4.3 to ensure compatibility.  2. Does UMC ver4.3(.1) compatible with UMA v4.1?     No. The UMA has to be upgraded to v4.3 to ensure ...
    • Does UMA 4.3.x able to publish data into WAA 4.2.x ?

      Question: Does UMA 4.3.x able to publish data into WAA 4.2.x ? Answer: No, UMA 4.3.x can't connect to WAA 4.2.x. UMA and its target WAA needs to be same version to use whole function of the product. More Information: N/A
    • What is the recommended sequence to restart WAA and UMA processes?

      Question: What is the recommended sequence to restart WAA and UMA processes?   Answer: On systems with both WAA and UMA installed, please follow the recommended sequence below:  1. Restart WAA process  2. Restart UMA process Abbreviation: WebALARM ...
    • If WebALARM Console is closed forcefully, is there any impact to WAA & UMA?

      Question: If WebALARM Console is closed forcefully, is there any impact to WAA & UMA? Answer: There is no adverse impact to WAA & UMA. The Console connection does not affect connection between WAA & UMA. Abbreviation: WebALARM Agent (WAA) Update ...
    • Update Management Agent (UMA) failed to connect to WebALARM Agent (WAA)

      Symptom: Update Management Agent (UMA) failed to connect to WebALARM Agent (WAA) Possible Root cause:  1. UMA settings in WAA server settings tab configured incorrectly and not connected. 2. The default Command TCP port (5013) and Data TCP port ...