This document provides a list of the alarms that may be raised by CGIN:
Core CGIN Alarms
Alarm | Instance ID | Level | Description |
---|---|---|---|
|
|
|
This alarm is raised when the CGIN RA entity cannot be activated. It is automatically cleared when the CGIN RA entity is deactivated. |
|
|
|
This alarm is raised when active reconfiguration fails. See the raised alarm for the reason why active reconfiguration failed. Once the reason for the reconfiguration failure is resolved the alarm will be automatically cleared. |
Stack Specific Alarms
OpenCloud OCSS7 Stack
Alarm | Instance ID | Level | Description |
---|---|---|---|
|
the resource adaptor entity name |
|
This alarm is raised when a TCAP stack configured via the legacy It is cleared when a connection is succesfully made to the cluster. |
|
the address of the affected connection |
|
This alarm is raised when a TCAP stack configured via It is cleared the connection has been successfully reestablished. |
|
|
|
This alarm is raised when the OCSS7 TCAP stack is unable to schedule an invoke timer.
This usually occurs when This alarm must be manually cleared as it indicates a configuration problem that must be resolved. |
|
|
|
This alarm is raised when the OCSS7 TCAP stack is unable to schedule an activity timer.
This usually occurs when This alarm must be manually cleared as it indicates a configuration problem that must be resolved. |
Mavenir Signalware Stack
Alarm | Instance ID | Level | Description |
---|---|---|---|
|
the address of the affected connection |
|
This alarm is raised when an existing connection to a backend is lost, or the initial connection cannot be established. It is automatically cleared when the connection is successfully established. |
|
the address of the affected connection |
|
This alarm is raised when a connection’s heartbeat is lost. This indicates that TCP/IP traffic is not flowing between CGIN and the backend. This can occur for multiple reasons, including network failure, stop-the-world activity in either CGIN or the backend, or CPU overload in either the CGIN or backend hosts. It is automatically cleared when the heartbeat is reestablished. |
Simulated TCAP Stack
Alarm | Instance ID | Level | Description |
---|---|---|---|
|
the address of the affected connection |
|
This alarm is raised when a TCAP stack configured via It is cleared the connection has been successfully reestablished. |