The Dashboard tab displays the total number of alarms triggered. It also displays the number of alarms according to their severity.

VNF Alarms

VNF alarms are triggered when VMware Telco Cloud Automation identifies anomalies in the network connection status or when the power state changes. VMware Telco Cloud Automation also triggers VNF alarms that are predefined and user-defined in VMware vSphere.

CNF Alarms

CNF triggers alarms for system level and service level anomalies. For example, system level alarms are triggered when an image or resource is not available, or when a pod becomes unavailable. Service level alarms are triggered when the number of replicas that you have specified is not identical to the number of nodes that get created, and so on. Here are some possible anomalies when VMware Telco Cloud Automation displays an error message and triggers an alarm. These alarms are in the Critical state:
  • Image pull error - The URL to the Helm Chart image is incorrect or the image cannot be accessed due to network issues.
  • Crash loop backoff - The application fails to load.
  • Progress deadline exceeded - Kubernetes controller exceeds the maximum number of tries to recover a crashed application.
  • Failed create - Kubernetes controller fails to create or schedule a Kubernetes Pod.
  • Resource failed - Kubernetes controller fails to create the resources.

VIM Alarms

VIM alarms are triggered at the VIM level for CNF infrastructure anomalies. For example, when a Kubernetes cluster reaches its memory or CPU resource limit, its corresponding VIM triggers an alarm. Here are some possible CNF infrastructure anomalies for which alarms are triggered. These alarms are in the Warning state:
  • Network unavailable - Worker node is unable to reach the network.
  • PID pressure - Worker node encounters Process ID (PID) limitations.
  • Disk pressure - Worker node is running out of disk space.
  • Memory pressure - Worker node is running out of memory.

Viewing and Acknowledging Alarms

Alarms are triggered at four levels:
  • CNF/VNF level - To view the alarms of individual CNFs and VNF instances, go to the Inventory tab, click a VNF or CNF instance, and click Alarms.
  • Network Service level - VNF and CNF alarms are listed at the corresponding Network Service level.
  • VDU level - For a VNF, the alarms are also listed at the corresponding VDU level.
  • Global level - You can view the global alarms for all entities and users from the Administration > Alarms tab.
To view and acknowledge alarms, perform the following steps:
  1. Go to Administration > Alarms. Details of the alarm such as the alarm name, its associated entity, its associated managed object, alarm severity, alarm triggered time, description, and state are displayed.
  2. To acknowledge a triggered alarm, select the alarm and click Acknowledge. When the acknowledgment is successful, the state of the alarm changes to Acknowledged. To acknowledge multiple alarms together, select the alarms that you want to acknowledge and click Acknowledge.

By default, the list refreshes every 120 seconds. To get the current state of the alarms, click Refresh.