You get unexpected errors and disconnects in the App Layering Management Console.  While logged in, you may see "Connectivity Failure" or a status of the ELM saying "No connection to Layering Service".

Reboot the ELM.  This is specifically an internal problem communicating between different services inside the ELM.  There is no external network connectivity problem.  The first, most likely solution is to just reboot the ELM and allow the services to reconnect to each other.

Note that the Layering Service status may not update itself to show Running for up to three hours after you actually fix the problem.  The Layering Service status goes to Connectivity Failure after a few hours of sustained internal ping failures.  In order to keep the status from flapping on and off (and sending a storm of notifications), it does not clear until the average over time gets back below the warning threshold.  So after rebooting the ELM, test normal functionality.  Do not rely on the  status indicator.