Jump to: navigation, search

GMS Alarms

The following alarms can be raised by Genesys Mobile Services based on system status/configuration:

Resources Configuration Alarm (EventId 2000) This alarm is raised by GMS when the server detects a problem on resources configuration (Duplicated DN on same/different Groups)
No more resources Alarm (EventId 2001) This alarm is raised by GMS when no more resources are available in GMS (LOCAL or CLUSTER strategy).
web_port option Alarm (EventId 2002) This alarm is raised by GMS when at startup, a GMS is not available on web_port.
NO_JDK Alarm (EventId 2003)
Introduced in 8.5.006.09
This alarm is raised when GMS is not started using a JDK (used to compile DFM files).)
Config Server: Handle Connection Failure Alarm (EventId 2004)
Introduced in 8.5.114.09
GMS raises this alarm when it fails to connect the Configuration Server. In this scenario, the GMS alarm displays at which time GMS will try to connect again.
Config Server: Handle Registration Failure Alarm (EventId 2005)
Introduced in 8.5.114.09
GMS raises this alarm when it fails to register on the Configuration Server. In this scenario, the GMS alarm displays at which time GMS will try to register again.

To create Alarms, refer to Creating the SCS Alarm Conditions.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on 11 April 2018, at 12:03.