
Dialogic® SS7G2x Signaling Server SGW Mode User Manual Issue 4
Table 9. Alarm Fault Codes (Continued)
Severity | CODE | Name | Event Description | CATEGORY | ID | Class † | DIAG | |
(LED) |
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
| |
|
|
| The Signaling Gateway is unable to |
|
|
|
| |
|
|
| transfer information to an RDC for |
|
|
|
| |
|
|
| a Continuous Record. Possible |
|
|
|
| |
|
|
| problems include: no RDCs |
|
|
|
| |
Major |
|
| available, directory does not exist |
|
|
| Diagnostic | |
44 | CR send fail | on RDC for this CR, write failure on | NONE | RECORD | 2 | |||
(MJR) | code | |||||||
|
| RDC. If the problem clears, this |
|
|
| |||
|
|
|
|
|
|
| ||
|
|
| alarm will persist until any records |
|
|
|
| |
|
|
| saved on the hard disk during the |
|
|
|
| |
|
|
| failure have been successfully |
|
|
|
| |
|
|
| transferred to an RDC. |
|
|
|
| |
|
|
|
|
|
|
|
| |
|
|
| The Signaling Gateway is unable to |
|
|
|
| |
|
|
| transfer information to an RDC for |
|
|
|
| |
|
|
| a Periodic Report. Possible |
|
|
|
| |
Major |
|
| problems include: no RDCs |
|
|
| Diagnostic | |
45 | PR send fail | available, directory does not exist | NONE | REPORT | 2 | |||
(MJR) | on RDC for this PR, write failure on | code | ||||||
|
|
|
|
| ||||
|
|
| RDC. If the problem clears, then |
|
|
|
| |
|
|
| the alarm will clear at the next |
|
|
|
| |
|
|
| successful transfer of data for the |
|
|
|
| |
|
|
| Periodic Report. |
|
|
|
| |
|
|
|
|
|
|
|
| |
|
|
| The hard disk drive capacity for a |
|
|
|
| |
|
|
| Continuous Record has reached its |
|
|
|
| |
|
|
| limit. Either there is no more space |
|
|
|
| |
|
|
| on the hard disk drive to store |
|
|
|
| |
Major |
|
| data, or this continuous record has |
|
|
|
| |
47 | Hard disk full | the maximum amount of data |
| RECORD | 2 |
| ||
(MJR) | stored for it on the hard drive. In |
|
| |||||
|
|
|
|
|
| |||
|
|
| both cases, records is discarded |
|
|
|
| |
|
|
| until an RDC recovers and all |
|
|
|
| |
|
|
| stored records are transferred from |
|
|
|
| |
|
|
| the Signaling Gateway. The alarm |
|
|
|
| |
|
|
| will then clear. |
|
|
|
| |
|
|
|
|
|
|
|
| |
|
|
| A board has reached a congestion |
|
|
|
| |
Major | 50 | Board cong | threshold. Boards repeatedly | SYS | BPOS | 2 |
| |
entering congestion indicate a need |
| |||||||
(MJR) |
| |||||||
|
| to increase the dimensioning of the |
|
|
|
| ||
|
|
|
|
|
|
| ||
|
|
| switch. |
|
|
|
| |
|
|
|
|
|
|
|
| |
Major |
|
| The PCMTYPE setting is |
|
|
|
| |
53 | PCM mismatch | inconsistent with the hardware | SYS | PCM | 2 | 0 | ||
(MJR) | ||||||||
|
| settings on the board. |
|
|
|
| ||
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
| |
|
|
| The system has only partially been |
|
|
|
| |
|
|
| upgraded and a full software |
|
|
|
| |
Major | 61 | Software | update is required. The system is | SYS | 0 | 2 | 0 | |
running in ‘safe’ mode running | ||||||||
(MJR) | mismatch | |||||||
|
|
| limited management software. No |
|
|
|
| |
|
|
| circuits have been brought into |
|
|
|
| |
|
|
| service. |
|
|
|
| |
|
|
|
|
|
|
|
| |
Major | 62 | C7 link Cong | A SS7 signaling link is encountering | SIG | C7LINK | 2 | 0 | |
(MJR) | congestion. | |||||||
|
|
|
|
|
| |||
|
|
|
|
|
|
|
| |
|
|
| The system has detected that the |
|
|
|
| |
Major |
|
| voltage on one or more power rails |
|
|
|
| |
64 | Power warning | is out of range. This is usually due | SYS | 0 | 2 | 0 | ||
(MJR) | to either a faulty power supply | |||||||
|
|
|
|
|
| |||
|
|
| module or a faulty board causing |
|
|
|
| |
|
|
| excessive current consumption. |
|
|
|
| |
|
|
|
|
|
|
|
| |
|
|
| A SIGTRAN signaling link has |
|
|
|
| |
Major | 65 | Assoc fail | failed. Usually due to incorrect |
|
|
|
| |
configuration (connectivity fault or | SIG | SNLINK | 2 | 0 | ||||
(MJR) | ||||||||
|
| inactive signaling at the remote |
|
|
|
| ||
|
|
|
|
|
|
| ||
|
|
| end. |
|
|
|
| |
|
|
|
|
|
|
|
| |
|
|
| Diagnostic event relating to the |
|
|
|
| |
Major | 66 | NIF event ind | Nodal Interworking Function. | NONE |
| 2 |
| |
Persistent events of this type |
|
| ||||||
(MJR) |
|
| ||||||
|
| should be reported to your support |
|
|
|
| ||
|
|
|
|
|
|
| ||
|
|
| representative. |
|
|
|
| |
|
|
|
|
|
|
|
|
†The “Class” column provides the initial default setting of the alarm class for each fault code. The alarm class for any particular alarm code is configurable using the ALCLS command and can be viewed using the ALCLP command. Changing the alarm class for an event type changes the Severity indicated by the LEDs and/or relays.
149