Page Comparison

Index Number

State Number

Alarm Description

Data / Troubleshooting

1

3

Ethernet Link Failure

Alarm is sent if any ethernet port loses connection and alarm is cleared when connection is re-established.

Trace the network cable between the port and the remote ethernet switch. Replace ethernet cable or connector as necessary.

2

3

System Busy Condition

The system ignores any incoming calls until the alarm is cleared. By Ignoring incoming calls the traffic load decreases and eventually the alarm will clear.

Ensure that System Busy Warning messages are no longer seen. Return traffic to normal levels and resume normal operation.

3

3

System Busy Warning

This notification indicates that the traffic volume is approaching its capacity. This message is only a warning. It does not mean a System Busy condition will occur. The System Busy Warning does not have a clearing Alarm. It continues to occur every few seconds, until the CPU utilization reduces. The System Busy Warning messages can be between 2 and 20 seconds apart, depending on system load.

The CPU has exceeded the "System Busy Warning" threshold. This condition can happen due to traffic congestion or by having Debug printing enabled.

When a System Busy Warning is generated, the user should reduce the number of new calls until the System Busy Warning messages cease. Whenever possible, ramp call rates up slowly and evenly to prevent an initial System Busy. Do not re-configure, and do not enable additional diagnostics.

4

3

System Memory Low

System memory has dropped below the minimum level of performance. When the system is in this condition, it is also in a System Busy condition and will send a System Busy Alarm to the host.

Check for other error messages that would indicate a network or system condition leading to this problem.

5

3

NFS Minor traffic

NFS Traffic Minor Threshold Alarm

6

3

NFS Major traffic

NFS Traffic Threshold Major Alarm

7

3

SS7 Remote ISUP

The address information represents the SS7 stack and Destination Point Code (DPC).

Check the status of the Links and see if they are 'in service'. If they are not 'in service', attempt to determine why the links are Out Of Service. Verify they are marked 'in service' from a host perspective.

Check the status of layer 1, the T1/E1 span. On the span also check for any slips or framing errors.

8

3

SS7 Signaling Stack Busy Congestion

Decrease the ISDN/SS7 load.  Consult Sangoma Customer Technical Support.

9

3

SS7 Signaling Link Congestion

When a link is congested, the IMG sends this alarm to the host.

If the system has not decreased a call to this DPC and this symptom persists, check the network engineering plan to possibly create another link in the link set.

10

3

Radius Server No Access

This alarm is sent when the IMG is not able to access the radius server.

Check that the IP address of the Radius server is correct.

Check that the Radius server is accessible and the service is running.

11

3

Card Approaching Busy

This alarm is sent when the IMG E1/T1, SS7, ISDN, SIP, or H.323 systems start to become busy.

No action required at this time. If load continues, subsequent alarms and recovery action will be initiated.

12

3

Card Busy

This alarm is sent when the IMG E1/T1, SS7, ISDN, SIP, or H.323 systems become busy.

If the system has not decreased call load and this symptom persists, check network engineering for proper load balancing.

13

3

Span Dead

This alarm is generated when the IMG detects a carrier group alarm for more than the allowed time. Either the clock source was lost or the physical connection to the network was broken.

Check that the physical connection has not been compromised.

Check that a loop timing source has been configured.

14

3

VMOD OOS

This alarm is sent when a VoIP module becomes inaccessible. Contact Sangoma support for assistance.

15

3

VMOD Dead

This alarm is sent when a VoIP module becomes inaccessible. Contact Sangoma support for assistance.