Actions

Difference between revisions of "Syslog (AlphaCom)"

From Zenitel Wiki

Line 9: Line 9:
 
The Debug log contains the same information as transmitted on the [[TST console]], and was on older systems  retrieved by the "[[TST_console#Read_Error_Buffer|err]]" command from the TST console.
 
The Debug log contains the same information as transmitted on the [[TST console]], and was on older systems  retrieved by the "[[TST_console#Read_Error_Buffer|err]]" command from the TST console.
  
The Debug Log has three levels:  
+
The Debug Log reports on three levels:  
- Disaster Exchange reset. The state of the exchange is so bad that the software does a controlled reset to restore normal operation.
+
Local0:Warning- Warning Information to the user. Often identical to texts sent to the log port
- Error – The software handles a problem by e.g. aborting an operation and returning to idle, but logs a message  
+
Local0:Error- Error – The software handles a problem by e.g. aborting an operation and returning to idle, but logs a message  
- Warning Information to the user. Often identical to texts sent to the log port
+
 
 +
Local0:???    - Disaster Exchange reset. The state of the exchange is so bad that the software does a controlled reset to restore normal operation.  
  
 
[[Category:AlphaCom E Software]]
 
[[Category:AlphaCom E Software]]

Revision as of 16:13, 31 August 2007

The Facility value is a way of determining which process of the AlphaCom created the message. Since the Syslog protocol was originally written on BSD Unix, the Facilities reflect the names of Unix processes and Daemons:

  • Local0: Debug log
  • Local1: System log
  • Local2: Statistics log

The Debug log contains the same information as transmitted on the TST console, and was on older systems retrieved by the "err" command from the TST console.

The Debug Log reports on three levels: Local0:Warning- Warning – Information to the user. Often identical to texts sent to the log port Local0:Error- Error – The software handles a problem by e.g. aborting an operation and returning to idle, but logs a message

Local0:??? - Disaster – Exchange reset. The state of the exchange is so bad that the software does a controlled reset to restore normal operation.