After Turning a hub to Secure, When logging in into the IM on that Secure hub, if "alarm Window" is requested in IM, the hubs stop responding.
This only happens when logged on the secure hub from the secure hub local IM. When logging in to the secure hub from other non-secure hub the issue does not happen.
Re-log in to the secure hub (127.0.0.1) fixes the issue. As soon as Alarm window is requested via IM GUI the issue reocurrs.
Known Design Limitation of IM
This is a known behavior, documented as well in the hub release notes for Secure Hub and Robot
To open the alarm console on Secure hub and robot either of the following options are available: