EGC_01

Database query error alarm

EGC_02

Socket error alarm

EGC_03

Thread error alarm

EGC_04

XML message error alarm

ITG003

Input \ output file error alarm

ITG020

Configuration error alarm

ITG002

Memory allocation error alarm

ITG004

Network input \ output error alarm

ITG005

Message queue error alarm

ITG012

Module initialization failure alarm

ITG014

Network interface failure alarm

ITG020

Configuration error alarm

ITG030

Media engine error alarm

ITG031

Certificate error alarm

ITG001

Task spawn failure

ITG002

Memory allocation error alarm

ITG003

Input \ output file error alarm

ITG004

Network input \ output error alarm

ITG005

Message queue error alarm

ITG012

Module initialization failure alarm

ITG014

Network interface failure alarm

ITG020

Configuration error alarm

ITG036

TPS/DSA communication link alarm

ITG001 

 Task spawn failure: <taskName>. 

Creation of a Device Adapter task or process failed for some reason.

 Critical 

No

 Yes 

  Yes

ITG002 

 Memory allocation failure. 

Memory allocation failed. Probable cause is memory leakage.

 Major 

No

 Yes 

  Yes

ITG003 

 File IO error: <fileName> <opName> <fd> <errno> <errtext>. 

Some file related input/output operation (<opName>) for the file (<fileName >) has failed. The operation can be: - file open  (<opName> = fopen or <opName> = open) - file read  (<opName> = fread) - get file status (<opName> = stat) - ini file open (<opName> = iniFileOpen) - ini section get (<opName> = iniSectionGet) May be the file does not exist or has incorrect access permissions.

 Major 

No

 Yes 

  Yes

TPS

ITG004 

 Network IO error: <opName> <fd> <errno> <errtext>. 

Some network related operation (<opName>) has failed. The operation can be: - socket creation (<opName> = socket) - socket bind (<opName> = bind) - set socket options (<opName> = setsocketopt) - socket sending (<opName> = sendto)

 Major

No

 Yes 

  Yes

ITG005 

 Message queue error: <opName> <fd> <errno> <errtext>. 

Some message queue related operation (<opName>) has failed. The operation can be: - queue open (<opName> = mq_open) - queue send (<opName> = mq_send) - queue receive (<opName> = mq_receive)

 Major 

No

 Yes 

  Yes

ITG012 

Module initialization failure: <moduleName>. 

Failed to initialize and start some programm module. Possible values for moduleName are: - "pbxLinkStartActive - TCP" - failed to start the PBX TCP link to the DSA - "pbxLinkStartPort failed" - PBX link port is not configured - "Problems in ES module" - Echo Server task configuration and initializatin failed

 Major 

No

 Yes 

  Yes

ITG014 

Network interface carrier: <ifName> <carrierState>. 

Carrier state for the specified network interface <ifName> changed. Possible values for network interface name (<ifName>) are: - eth0 (Management interface) - eth1 (Security Module interface) Carrier state can be "LOST" if carrier is lost or "OK" when carrier is restored. The "LOST" state alarms are cleared automatically when carrier state becomes "OK". In addition, this alarm can be raised for some internal issues in the Carrier Detection tool. In such case <carrierState> field can be: - "NetLink socket open failed" - failed to open NETLINK socket - "NetLink socket bind failed" - failed to bind NETLINK socket - "EthTool request failed" - failed to check link beating by direct request - "EthTool socket open failed" - failed to open a socket for direct carrier beating requests

 Critical 

Yes

 Yes 

  Yes

Carrier Detection

ITG020 

Configuration error.

Some configuration error has been detected. Additional data is printed out for the error : - <configFile> - configuration file name, e.g. config.ini; <configVar> - field in the config file that has invalid value; <configValue> - invalid value. Alternatively, the <configFile> <configVar> <configValue> fields can contain just some text information to provide more details about the issue, e.g. "ES2 is assigned the same IP address as default ES1 ( TLAN 192.168.96.115 ). This can cause NAT type detection failure."

Major

Yes (For some cases)

 Yes 

  Yes

ITG036 

TPS/DSA communication link: <up/down>.

State of the TPS/DSA PBX link changed. Possible status is "up" or "down". The alarm is cleared automatically when the state becomes "up".

 Critical

Yes

Yes

Yes

Intercommunication issue may have caused this alarm. Further analysis is required as described below.

PBX

EGC_01

Database query error

Failed to execute database query. The alarm is cleared automatically when subsequent query operations become successful.

Critical

Yes

Yes

Yes

Snap-in (Java)

EGC_02

Failed to bind socket

Socket bind network operation failed. Possible reason - network port 15557 is already in use by some other process or service.

Critical

No

Yes

Yes

Snap-in (Java)

EGC_03

Unable to shutdown ada snap-in threads

Failed to shut down some Device Adapter snap-in threads.

Critical

No

Yes

Yes

Snap-in (Java)