Alive_Time in CM_COMPUTER_SYSTEM and CM_NIMBUS_ROBOT not in sync

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

We are using the alive_time information from the UIM DB discovery tables in our dashboards and have found a discrepancy where the CM_COMPUTER_SYSTEM alive_time is different to the CM_NIMBUS_ROBOT alive_time.

Should these 2 always be in sync?

When are those values in Alive_Time updated? 

Environment

Release : UIM 20.4

Cause

Guidance

Resolution

The Alive_time from the 2 tables are not meant to be in sync. 

 Alive_time in cm_computer_system updates every time the discovery_server sees a robot. 

alive_time for the CM_NIMBUS_ROBOT is updated every time a robot is restarted (eg. hard restart) or soft-restarted (eg. log change) 

 

Some practical examples from Testing: 

The below test is done using a robot under the primary hub. (Tests done with robots under a remote hub can be different as the procedure can take longer to register so there might be a delay with the time)

15.13 Manual robot  Restart
Cm_Computer_system alive_time updated:  15.13.37.380
CM_Nimbus_robot alive_time is updated: 15.13.36.530 

(The same time reflect in the controller) 

 

Updated alias in OC for a certain robot: 
Here the alive_time in cm_computer_system for all systems are updated at the time the update was done. 
CM_Nimbus_robot remain unchanged

Update log level at robot lvel > soft Restart: 
alive_time cm_computer_system is unchanged
CM_Nimbus_robot alive_time is updated

Discovery_server is restarted: 
alive_time cm_computer_system is updated for all systems
CM_Nimbus_robot alive_time is unchanged

 

Additional Information

The KB below shows some additional definitions for the other attributes in the CM_computer_system: 

CM_COMPUTER_SYSTEM table attributes (broadcom.com)