Any entity including groups, nodes, endpoints/interfaces and links can have alarms. Furthermore, some entities have their alarms propagated to their higher-level counterparts. For example, a Node's alarms are propagated, and thus become visible, on the Group that encloses that Node.

Here we can see the ‘Network’ group has been selected and the user has selected the Alarms tab on its dashboard, which lists all the alarms in the group. The alarms might belong to the selected entity, or to entities related to it. In the example below they belong to the Nodes that comprise the group. Any alarm can be selected, and if done so the alarms's dashboard for that individual alarm will then shown. 

A user can also disable any and all alarms in any specific entity, for a given and predefined amount of time. This will result in the Entity not displaying any alarming related information in the 3D topology. Nevertheless, alarms can still be viewed upon selecting the entity and visiting the alarms tab (as displayed below). This functionality is particularly useful for disabling alarms during maintenance periods or on entities whose alarms are not relevant for any specific reason.

Instead disabling any and all alarms, one can instead mute specific alarm types that have happened at least once.

Once muted the alarms will still remain visible in the alarms tab, but will be flagged as muted. Muted alarms, however, do not get propagated to higher-level entities.