The Alarming service uses alarm definitions defined by other individual services to determine when to raise alarms upon reception of alarm events generated by the individual service. The alarms generated are expected to be received by the Network Management System (NMS).
Cause
The NMS might not have received the alarms because:
The Alarming or Prometheus pods are not in a running state.
The Alarming service is not properly configured.
Solution if Alarming or Prometheus pods are not in running state
Procedure
Run the command ccm status --pod-details.
If the command shows the Alarming or Prometheus pod in a non-running state, contact Avaya support.
Solution if the Alarming service is not properly configured
Procedure
Verify that the Alarming service has generated alarms by running the command ccm release common-services alarmctl -l alarmEvents.
Verify that the Alarming service destination is not empty by running the command ccm release common-services alarmctl -l destinations.
If the listing of the alarm request and alarm destination succeeds, but the alarm destination list is empty, you must configure the alarm destination. Run the command ccm release common-services alarmctl -a destinations --address <ip-address> --type <TRAP|KAFKA> --port <port-num> [--username <string>] [--password <string>] [--auth <SHA>] [--priv <AES>] [--authPwd <string>] [--privPwd <string>] [ --url <url-string> ]
Refer to your solution documentation for additional information about using this command and setting the alarm destination.
