Traverse: Frequent 'DGE Communication Lost' events/alerts

An offset between the clock on a DGE/DGE extension with the clock on the BVE can lead to spurious 'DGE Communication Lost' events and optionally email alerts.  To determine if this is the case, as a 'superuser' navigate to 'Superuser->Health' and review the 'Time Offset' column for the DGE or DGE extension.  The value is expressed as hours:minutes, so +00:01 means 1 minute ahead of the BVE clock.

If there is an offset, it should be corrected by ensuring that the clocks on both the BVE and DGE/DGEx are synchronized with accurate sources to achieve zero offset.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


  • 0

    Hi Team,

    We are getting continuous alerts for DGE flapping as below, Kindly check and do the needful.


    Traverse BVE has not received a periodic heartbeat message from the following server for more than the configured amount of time

    DGE/DGEx Name  : dgex-nesa
    Severity       : warning
    Last Timestamp : Wed 2017.02.01 at 03:34:48 PM GST
    Elapsed Time   : 334 seconds

    Please verify that the DGE or DGE extension component is running on the remote server and there is no network communication problem.


  • 0
    Piyush Mehta

    Hello CNOC - If this article did not resolve the issue, kindly open a ticket with Kaseys Support. Regards.

Article is closed for comments.