|
|
| (43 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| − | The '''AlphaCom system log''' provides technical events for monitoring the health of the AlphaCom system. The system log includes the following type of events:
| + | #REDIRECT [[System log]] |
| − | [[Image:AlphaPro System LogsAndErrors.jpg|thumb|right|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 ==
| |
| − | | |
| − | <pre>
| |
| − | 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
| |
| − |
| |
| − | | |
| − | </pre>
| |
| − | | |
| − | == Log events ==
| |
| − | === Station line error ===
| |
| − | ==== Traditional (analog) stations ====
| |
| − | '''Line Down''': 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 error is reported on station 102. The line board is located in positon 1, port 2:
| |
| − | Oct 11 14:06:21 src@Johnson AlphaLog: N001.D065:.Exch:@D65.B01-2 Line Down: CD Open St 2 "102 -"
| |
| − | | |
| − | ==== IP Stations ====
| |
| − | The IP substation is supervised in two different ways.
| |
| − | | |
| − | # Each IP-sub-stations have its own unique TCP socket for data communication. This socket send TCP-alive frames every 5 second, thus a broken socket is discovered within 10 seconds and reported as line error from AlphaCom.
| |
| − | # From the Application layer AlphaCom is sending a "PING" approximately every 90 second. The stations reply with a "PONG". If one PONG is missing the station is reported as line fault.
| |
| − | | |
| − | ===== IP station down=====
| |
| − | IP station down is reported on the log port in the two following ways (Data communication is lost, no PING reply or socket closed):
| |
| − | <pre>
| |
| − | 930: Feb 13 16:17:58 src@Node1 AlphaLog: N001.D065:.Exch:@D65.B25-1 Line Down: IP ST Data Com St 20 "1001 -"
| |
| − | </pre>
| |
| − | IP station down is also reported to the event handler "[[Faulty Station Line (Event Type)|faulty station line]]" ON/OFF.
| |
| − | | |
| − | ===== No license =====
| |
| − | If a new [[Licenses|license key]] is entered with no IP station licenses or not enough licenses, then some stations will be out of business:
| |
| − | 933: Feb 13 16:21:34 src@Node1 AlphaLog: N001.D065:.Exch:@D65.B25-1 Line Down: IP ST License St 20 "1001 -"
| |
| − | | |
| − | The system station will report like ordinary line faults with reference to master board and first port (B25-1) since the IP station is not related to any physical AMC board position.
| |
| − | | |
| − | === Board error ===
| |
| − | '''Board Down''' is reported when the AMC-board fail to communicate with a board inside the module. Board error is 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 ===
| |
| − | '''AlphaNet Line Down''' is reported if the [[AGA]] or [[AE1]] 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 tone 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
| |
| − |
| |
| − | '''AlphaNet Line Up''' is reported when the audio link becomes OK. Signal level is 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 ===
| |
| − | '''ALARM xx ON''': [[RCI]]'s are reported ON and OFF. The number indicate the logical RCI number.
| |
| − | 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 ===
| |
| − | ====AlphaPro log-in ====
| |
| − | [[AlphaPro]] is using port 60001. The system log will show the IP address of the PC that has logged on the the AlphaCom:
| |
| − | 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:
| |
| − | | |
| − | ==== TCP-IP connections ====
| |
| − | TCP-IP connections are logged. [[MultiModule]] over IP is using TCP port 50010 and shows connection between master and slave module. Here a device with IP address 10.5.101.42 has connected (and disconnected) to port 4001.
| |
| − | 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:
| |
| − | | |
| − | And this is...:
| |
| − | Oct 10 12:54:34 src@Johnson AlphaLog: N001.D065:.Exch:DP 39 CONN Uart /dev/tts/0
| |
| − | Oct 10 12:54:37 src@Johnson AlphaLog: N001.D065:.Exch:DP 04 CONN Uart /dev/tts/1
| |
| − |
| |
| − | Others:
| |
| − | 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
| |
| − |
| |
| − | | |
| − | [[Category:AlphaCom E Software]]
| |
