Dialogic IMG - How to read the Alarm and Socket Logs on GCEMS
Table of Contents
Introduction
In order to troubleshoot an issue, Dialogic IMG 1010 Integrated Media Gateway users may be requested to collect Dialogic Gate Control Element Management System (GCEMS) logs. All log files are stored on the GCEMS server and are located at /opt/dialogic/common/log directory.
Each day at approximately 1:30 am the complete log file directory is zipped up and moved into a directory named 'zipfiles' which is also located in the /opt/dialogic/common directory.
The GCEMS automatically creates the logs; the alarm and socket logs are two important logs:
- Alarm.log: alarm.PID.log: (PID is the process ID of the GateManager)
The alarm.log file logs all the actions taken by GateManager during the configuration of the IMG and the text of any alarm conditions that occur on the IMG.
- Socket log: socket.PID.log (PID is the process ID of the CommManager)
This file logs all the API messages going between the IMG and the GCEMS.
This article describes how to read the alarm and socket logs
Procedure
Below is an example with the following assumption:
- span is up and in service
- an SS7 link is configured on this span
- this is the only SS7 link to SS7 APC/DPC 0x111
After this span is down, the SS7 link configured on this E1 span will be failed and SS7 Remote ISUP to DPC 0x111 will become Unavailable.
EventView from the GCEMS server shows:
- PPL Event Indication from MTP3 LSAC (signalling link activity control): SS7 Link id 1 is failed with reason "Excessive error rate"
- General major alarm: SS7 remote ISUP to DPC0x111 becomes unavailable
- Span major alarm: span id 28 is dead with status: receiving Red/AIS alarm, sending Yellow alarm
- PPL Event Indication from L3P Link: SS7 link id 1 is out of service with reason L1_dead
GCEMS EventView screenshot
Please click the following image to display it full-size:
alarm.13464.log shows similar information to the GCEMS EventView:
Jun 07 2010 12:07:54 Minor: PPLEventIndication Evt=0x02: LinkID = 1, StackID=1, Comp=0x2E MTP3 LSAC (Link Failed)
Jun 07 2010 12:07:54 **Major: CCS :Node 0: General Alarm: SS7 Remote ISUP Unavailable, Stack:0x01, DPC:0x111
Jun 07 2010 12:07:56 **Major: Circuit :Node 0: Span Alarm: On Span 28(0x1c), Carrier Group Alarm or span dead - network status: Rcvng Red; Sndng Yellow; Rcvng AIS;
Jun 07 2010 12:07:56 Minor: PPLEventIndication Evt=0x0B: LinkID = 1, StackID=1, Comp=0x10 L3P Link (Link Out of Service, L1_DEAD)
socket.13193.log shows inbound and outbound API messages. The first line is the API message from X0->H which is from the IMG Node 0 to the Host. The second line is a message from H -> X0 which is a host acknowledgement
Jun 07 2010 12:07:54.104 X0[10.129.51.9]->H : 00 43 02 23 00 00 01 09 02 01 01 00 2e 00 02 01 03 00 2d 00 18 00 00 00 04 00 08 a6 c4 00 01 00 04 00 00 00 00 00 1d 00
04 00 00 00 03
Jun 07 2010 12:07:54.104 H->X0[10.129.51.9] : 00 43 02 23 00
Jun 07 2010 12:07:54.919 X0[10.129.51.9]->H : 00 43 02 24 00 00 01 1c 03 01 00 01 00 3f 00 01 01 03 00 2d 00 10 00 00 00 04 00 08 a9 f8 00 01 00 04 00 00 00 00
Jun 07 2010 12:07:54.920 H->X0[10.129.51.9] : 00 43 02 24 00
Jun 07 2010 12:07:54.921 X0[10.129.51.9]->H : 00 b9 00 58 00 03 01 0f 05 01 00 00 01 11
Jun 07 2010 12:07:54.921 H->X0[10.129.51.9] : 00 b9 00 58 00
Jun 07 2010 12:07:56.520 X0[10.129.51.9]->H : 00 b9 00 59 00 03 03 01 07 00 01 0c 02 00 1c 61
Jun 07 2010 12:07:56.520 H->X0[10.129.51.9] : 00 b9 00 59 00
Jun 07 2010 12:07:56.520 X0[10.129.51.9]->H : 00 43 02 25 00 00 01 09 02 01 01 00 10 00 0b 01 02 14 01 03
Jun 07 2010 12:07:56.520 H->X0[10.129.51.9] : 00 43 02 25 00
PPL Event Indication (API id 0x0043) decode example:
Jun 07 2010 12:07:54.104 X0[10.129.51.9]->H : 00 43 02 23 00 00 01 09 02 01 01 00 2e 00 02 01 03 00 2d 00 18 00 00 00 04 00 08 a6 c4 00 01 00 04 00 00 00 00 00 1d 00
04 00 00 00 03
Byte Description Values
0, 1 Message Type 0x0043 - PPL Event Indication
2, 3 Sequence Number 0x0223
4 Logical Node ID 0x00
5-10 AIB (SS7 Link AIB) 00 01 09 02 01 01 - ss7 stack id 1, ss7 link id 1
11,12 PPL Component ID 0x002e - MTP3 LSAC (signalling link activity control)
13,14 PPL Event 0x0002 - Signaling link failure
15 Number of ICBs 0x01
16 ICB Type 0x03 (Extended Data)
17,18 ICB ID 0x002D (Q.752 parameters)
19,20 ICB Length (2 Bytes) 0x0018
21,22 Parameter 1 Type 0x0000 (MTP3 Timestamp)
23,24 Parameter 1 Length 0x0004
25-28 Parameter 1 Value 00 08 a6 c4
29,30 Parameter 2 Type 0x0001 (Interval sequence number)
31,32 Parameter 2 Length 0x0004
33-36 Parameter 2 Value 00 00 00 00
37,38 Parameter 3 Type 0x001d (Link failure reason code)
39,40 Parameter 3 Length 0x0004
41-44 Parameter 3 Value 00 00 00 03 - Excessive error rate
Note (Link failure reason code):
0x0001 Abnormal FIBR/BSNR
0x0002 Excessive delayed ACK (T7)
0x0003 Excessive error rate
0x0004 Excessive duration of congestion (T6)
0x0005 LSSU received (SIOS, SIO, SIN, SIE)
0x0006 Changeover MSU received
0x0007 Other
Alarm (API id 0x00B9) decode example:
Jun 07 2010 12:07:54.921 X0[10.129.51.9]->H : 00 b9 00 58 00 03 01 0f 05 01 00 00 01 11
Byte Description Values
0, 1 Message Type 0x00b9 - Alarm
2 Reserved 0x00
3 Sequence Number 0x33
4 Logical Node ID 0x00
5 Severity 0x03 (Major)
Note (alarm severity):
0x01 Informative
0x02 Minor
0x03 Major
6 Alarm Type 0x01 (General Alarms)
Note (alarm type):
0x01 - General Alarms
0x02 - Card Alarms
0x03 - Span Alarms
0x04 - Channel Alarms
0x05 - DSP SIMM Alarms
0x06 - DSP Alarms
0x07 - Node Alarms
0x08 - DS3 Alarms
0x09 - VoIP Module Alarms
0x0B – M3UA Alarms
7 Alarm Number 0x0f (SS7 Remote ISUP Unavailable)
8 Data Length 0x05
9 Data[0] SS7 Stack ID 0x01
10-13 Data[1-4] DPC 0x00000111
Product List
Dialogic IMG 1010 Integrated Media Gateway
Glossary of Acronyms / Terms
API - Application Programming Interface
AIB - Address Information Blocks
ICB - Information Control Blocks