Find answers to your technical questions and learn how to use our products
Search suggestions:
Find answers to your technical questions and learn how to use our products
Search suggestions:
The following table includes the Avaya Hybrid Cloud Gateway alarm types, event codes, and alarm descriptions:
Alarm type |
Event code |
Alarm description |
|---|---|---|
Common alarms |
24 |
Cassandra is not running. |
76 |
Expired or license error and is within the grace period of 30 days. |
|
78 |
Expired or license error and the grace period has expired. |
|
90 |
CPU usage has exceeded the threshold by X percentage. 70% and above indicates warning severity. |
|
92 94 |
CPU usage has exceeded threshold by Y percentage. 80% and above indicates major severity whereas 90% and above indicates critical severity. |
|
242 |
Avaya Hybrid Cloud Gateway backup has failed. |
|
244 |
Certificate is about to expire. |
|
246 |
Certificate has expired. |
|
250 |
New Avaya Hybrid Cloud Gateway software load is available for upgrade. |
|
252 |
Low available disk space. Application partition has occupied X percentage space. 70% and above indicates warning severity. |
|
252 |
Low available disk space. Log Partition has occupied X percentage space. 70% and above indicates warning severity. |
|
254 |
Low available disk space. Application partition has occupied Y percentage of space. 90% and above indicates critical severity. |
|
254 |
Low available disk space. Log partition has occupied Y percentage of space. 90% and above indicates critical severity. |
|
256 |
Directory space is not sufficient for downloading upgrades. |
|
260 |
Nginx is not running. |
|
264 |
Connection of Avaya Hybrid Cloud Gateway to Avaya Aura® System Manager is lost. |
|
Signaling connector alarms |
28 |
Session Manager connection is down because it failed to connect to at least one Session Manager. |
30 |
Session Manager connection is down because it failed to connect to more than one Session Manager. |
|
34 |
Avaya Aura® Device Services connection is down. |
|
34 |
Avaya Aura® Device Services connection is down due to misconfiguration. Avaya Hybrid Cloud Gateway is not added as a trusted host on Avaya Aura® Device Services. |
|
102 104 |
Session Manager has requested high latency with at least one Session Manager. |
|
240 |
Session Manager connection is down due to misconfiguration. Missing trusted Session Initiation Protocol (SIP) entity link. Session Manager FQDN is not provisioned in the SIP entity of Session Manager. |
|
248 |
Websocket connection of Gateway Connection Manager of UC3 is down. |
|
262 |
Gateway Connection Manager of UC3 has high ping latency. |
|
266 |
Avaya Aura® Device Services has high request latency. |
|
268 |
Critical Threshold of JVM Memory is Y percent. 95% and above indicates critical severity. |
|
270 |
Java Heap usage of the signaling connector has exceeded the critical threshold. |
|
274 |
User session capacity. Warning threshold of Y (100%) number of users session is active. |
|
276 |
User session capacity. Warning threshold of X (70%) number of users session is active. |
|
286 |
Admin connector is down on all the nodes. Admin connector is up now. |
|
288 |
Admin connector Master instance is down. Admin connector Master instance is up now. |
|
Admin service alarms |
258 |
Signaling connector is not running except for manual stop or restart. |
278 |
Hybrid Cloud Manager (HCM) connection is down for other reasons. |
|
280 |
Admin services standby instance is not running. |
|
284 |
HCM connection is down due to misconfiguration. |
|
Admin connector alarms |
1 |
Admin connector fails to establish a connection to the Avaya Experience Platform™ Public Cloud Cloud. |
2 |
Admin connector can establish a successful connection to the Avaya Experience Platform™ Public Cloud Cloud. |
|
3 |
Admin connector fails to establish a connection to the Avaya Experience Platform™ Public Cloud Cloud due to incomplete configuration. |
|
4 |
Admin connector can attempt connection after getting the required configuration. |
|
5 |
Admin connector cannot successfully connect with Communication Manager or System Manager. |
|
6 |
Admin connector can successfully connect to Communication Manager or System Manager. |
|
7 |
Admin connector standby instance fails unexpectedly. |
|
8 |
Admin connector standby instance starts successfully. |
|
9 |
Admin connector fails to connect to the Avaya Hybrid Cloud Gateway database. |
|
10 |
Admin connector connects successfully to the Avaya Hybrid Cloud Gateway database. |