Actions

Difference between revisions of "AlphaCom system log"

From Zenitel Wiki

(Device error)
(Device error)
Line 42: Line 42:
  
 
=== Device error ===
 
=== Device error ===
Error on communication with [[Device]] #1 (Device is normally a [[RIO]] unit):
+
'''Device Error''' is reported if the communication between the AlphaCom and the device fails. A "[[device]]" is normally a [[RIO]] unit). Here there is an error communicating with device #1:
 
  Oct 10 17:51:36 src@Johnson AlphaLog: N001.D065:.Exch:@D01        Device Error
 
  Oct 10 17:51:36 src@Johnson AlphaLog: N001.D065:.Exch:@D01        Device Error
  
Device OK is reported when the communication becomes OK, and also after restart of the AlphaCom exchange:
+
'''Device OK''' is reported when the communication becomes OK, and also after restart of the AlphaCom exchange:
 
  Oct 10 17:51:37 src@Johnson AlphaLog: N001.D065:.Exch:@D01        Device OK
 
  Oct 10 17:51:37 src@Johnson AlphaLog: N001.D065:.Exch:@D01        Device OK
  
  
Device Missing is reported if the device is not responding after AlphaCom startup:
+
'''Device Missing''' is reported if the device is not responding after AlphaCom startup:
 
  Oct 11 16:16:54 src@Johnson AlphaLog: N001.D065:.Exch:@D02        Device Missing
 
  Oct 11 16:16:54 src@Johnson AlphaLog: N001.D065:.Exch:@D02        Device Missing
  

Revision as of 15:38, 12 October 2007

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

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

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 the event handler by using the LOG command.

Description of log string

                  Common part                                    Log event
----------------------------------------------------- ------------------------------------------
Oct 11 14:06:21 src@Johnson AlphaLog: N001.D065:.Exch:@D65.B01-2 Line Down: CD Open St 2 "102 -"
--------------- ----------- --------  ---- ----- ---- ------------------------------------------
      |             |            |      |    |     |      |
      |             |            |      |    |     |      +- Log event
      |             |            |      |    |     +-------- Mandatory text
      |             |            |      |    +-------------- Source: Module number (65 is master module, 66-68 are slave modules)
      |             |            |      +------------------- Source: Node number (Here: node 1)    
      |             |            +-------------------------- Mandatory text
      |             +--------------------------------------- Source: Exchange name
      +----------------------------------------------------- Date and time of log event
 

Log events

Station line error

The line monitoring feature of the AlphaCom will detect when there is a station line error. Stations are reported down only (not UP). Here line eroor is reported on station 102, board positon 1, line 2:

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

Board error

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

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

Device error

Device Error is reported if the communication between the AlphaCom and the device fails. A "device" is normally a RIO unit). Here there is an error communicating with device #1:

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

Device OK is reported when the communication becomes OK, and also after restart of the AlphaCom exchange:

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


Device Missing is reported if the device is not responding after AlphaCom startup:

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

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

AGA error

An AGA error is reported if the audio link between two nodes in AlphaNet becomes faulty. Here the first line on board position 23 (B23-1) is reported faulty. The audio links are supervised by a test tones issued at regular intervals. Signal Level (SL) is the level measured when there is supposed to be a tone, Noise Level (NL) is the measured level when there is no tone (silence). Signal level is normally in the range 80 - 90. If the signal level is below 40, the AGA error is reported.

Oct 13 14:23:28 src@AlphaComE AlphaLog: N001.D065:.Exch:@D65.B23-1  AlphaNet Line Down:SL=  8 NL=  8

When the audio link becomes OK, the line is reported UP. Signal level 86 in this example:

Oct 13 14:23:59 src@AlphaComE AlphaLog: N001.D065:.Exch:@D65.B23-1  AlphaNet Line Up:SL=86 NL=  8



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: