Actions

AlphaCom system log

From Zenitel Wiki

Revision as of 14:36, 12 October 2007 by Asle (talk)

The system log provides technical events for monitoring the health of the AlphaCom system. The system log includes the following type of events:

  • Board down
  • Line error
  • Device/card cage error
  • AGA line error
  • Software error
  • Remote input on/off
  • Customized event logging
AlphaPro log configuration

In AlphaPro (Exchange & System > System > Logs and Errors) it is possible to configure what events to include in the system log. By default all events are included.

It is also possible to configure customized events in the system log. This is done in AlphaPro by using Event programming.

General

Message: 014101FF2118410015003632018002=54 

   Network      Application  Application
 layer header      header    message param.
--------------- ------------ --------
Oct 11 14:06:21 src@Johnson AlphaLog: N001.D065:.Exch:@D65.B01-2 Line Down: CD Open St 2 "102 -"
---- ---- -- -- -- ---- ---- -------- - --
 |    |   |  |  |   |    |       |    | |
 |    |   |  |  |   |    |       |    | +- Checksum. Bytewise XOR
 |    |   |  |  |   |    |       |    +--- Checksum next
 |    |   |  |  |   |    |       +-------- Station in NET_OBJ_REF format: dir no 8002, node 01
 |    |   |  |  |   |    +---------------- Message id: 0x0036 = Station is busy
 |    |   |  |  |   +--------------------- Reference: Value identifying receivers’ reference
 |    |   |  |  +------------------------- Message class: 65 (0x41) ‘A’ = AlphaCom
 |    |   |  +---------------------------- Options: Message sequence number. 
 |    |   |                                The number option bytes is given by the 3 most significant bits of <hop­count­byte> 
 |    |   |                                (In this case: Hex:21 = Bin:00100001 > 1 byte option)
 |    |   +------------------------------- Hopcount byte
 |    +----------------------------------- Destination: Node 01, broadcast (0xFF)
 +---------------------------------------- Source: Node 01, module 65 (0x41)


Oct 11 14:06:21 src@Johnson AlphaLog: N001.D065:.Exch:@D65.B01-2 Line Down: CD Open St 2 "102 -"

Description of log

Station line error

Oct 11 14:06:21 src@Johnson AlphaLog: N001.D065:.Exch:@D65.B01-2 Line Down: CD Open St 2 "102 -"

Device error

Error on communication with Device #1 (Device is normally a RIO unit):

Oct 10 17:51:36 src@Johnson AlphaLog: N001.D065:.Exch:@D01        Device Error

Reported after restart if device is defined and OK

Oct 10 17:51:37 src@Johnson AlphaLog: N001.D065:.Exch:@D01        Device OK


Device not responding when AlphaCom starts:

Oct 11 16:16:54 src@Johnson AlphaLog: N001.D065:.Exch:@D02        Device Missing


Board error

Boards are reported down only (not up). Here board in position 9 is reported down:

Oct 11 16:15:15 src@Johnson AlphaLog: N001.D065:.Exch:@D65.B09 Board Down


Card Cage

Reported OK when all boards in the module are up and running (the module is operational)

Oct 10 12:54:45 src@Johnson AlphaLog: N001.D065:.Exch:@D65        Card Cage OK

Remote Control Input RCI

RCI's are reported....

Oct 13 14:22:41 src@Johnson AlphaLog: N001.D065:.Exch:ALARM 1 ON.
Oct 13 14:22:39 src@Johnson AlphaLog: N001.D065:.Exch:ALARM 1 OFF.

System reports

Oct 10 12:46:20 src@Johnson AlphaLog: N001.D065:.Exch:DP 33 CONN TCP-IP Server Port: 60001 IP:10.5.101.111
Oct 10 12:53:42 src@Johnson AlphaLog: N001.D065:.Exch:DP 33 DISC TCP-IP Server Port: 60001 IP:
Oct 10 12:54:34 src@Johnson AlphaLog: N001.D065:.Exch:DP 39 CONN Uart /dev/tts/0      
Oct 10 12:54:35 src@Johnson AlphaLog: N001.D065:.Exch:ALARM 8 ON.
Oct 10 12:54:35 src@Johnson AlphaLog: N001.D065:.Exch:Temperature Alarm
Oct 10 12:54:37 src@Johnson AlphaLog: N001.D065:.Exch:DP 04 CONN Uart /dev/tts/1      
Oct  8 15:50:02 src@Johnson AlphaLog: N001.D065:.Exch:DP 03 CONN TCP-IP Client Port: 4001 IP: 10.5.101.42
Oct  8 15:49:48 src@Johnson AlphaLog: N001.D065:.Exch:DP 03 DISC TCP-IP Client Port: 4001 IP: