A very useful function, that is provided by Abilis CPX, is the recording of all the events that are pertinent to the global working mode and other events of particular importance. These events are stored in textual format in a file called System Log.
The System Log file is a fixed length one (10 Kbytes) and it contains the 256 more recent events. The System Log is saved on the floppy disk and updated every time that an event to save occurs. New events are stored and the oldest ones are progressively deleted. Every event is saved with its date and time of occurrence.
Because System Log file is stored on the floppy disk, that contains the Abilis CPX software and that is inserted in floppy drive, the disk must be NOT WRITE PROTECTED, otherwise, the Abilis CPX keeps on working, but the System Log cannot be saved.
Using the command interpreter of the Control Port, it is possible to inspect the content of the System Log file. Events are displayed starting from the oldest one or from a certain date and time, that must be specified in the displaying command.
Here is an example of System Log content visualization:
[14:40:11] ABILIS_CPX: D L 01/03/2004 15:33:26 --- NEW RUN ---- 01/03/2004 15:33:26 I: SYSTEM RESET 01/03/2004 15:33:36 I: EB IDEC f01 01/03/2004 15:33:36 I: EB ESCC8 f01 01/03/2004 15:33:41 I: EB AC f04 r04 01/03/2004 15:33:47 W: C02 01/03/2004 15:33:47 TRACE ACTIVATED 01/03/2004 15:33:50 SYSTEM STARTED 01/03/2004 15:33:50 CONF:ACCEPTED 01/03/2004 15:33:50 CONF:BACKUP 01/03/2004 15:33:50 AUTO SAVE CONF 01/03/2004 15:33:50 I:p1 SYN:UP.01 01/03/2004 15:33:50 I:p2 SYN:UP.01 01/03/2004 15:33:50 I:p3 SYN:UP.11 01/03/2004 15:33:50 I:p4 SYN:UP.11 01/03/2004 15:33:50 I:p5 SYN:UP.01 01/03/2004 15:33:50 I:p6 SYN:UP.01 01/03/2004 15:33:50 I:p7 SYN:UP.01 01/03/2004 15:33:50 I:p8 SYN:UP.01 01/03/2004 15:33:50 I:p21 PAD:dn.01 01/03/2004 15:33:50 I:p196 EPL:dn.in 01/03/2004 15:33:50 I:p197 EPL:dn.in 01/03/2004 15:33:50 I:p201 LAPB:cg 01/03/2004 15:33:50 I:p202 LAPB:cg 01/03/2004 15:33:50 I:p203 LAPB:cg 01/03/2004 15:33:50 I:p204 LAPB:cg 01/03/2004 15:33:50 I:p301 X25:down 01/03/2004 15:33:50 I:p302 X25:down 01/03/2004 15:33:50 I:p303 X25:down 01/03/2004 15:33:50 W: EVENTS LOST 01/03/2004 15:33:51 AUTO SAVE OK 01/03/2004 15:33:58 CONN P:920 L:01 01/03/2004 15:33:58 CONN P:921 L:01 01/03/2004 15:34:16 I:p751 MLM:RD.ln
It is also possible to make System Log events to be simultaneously sent to the current Control Port session. Events are displayed in the same time that they occurs and that they are recorded into the file on the floppy disk.
Here is an example of System Log content real-time listing:
[14:09:03] ABILIS_CPX: START L Current Local Time: Wednesday 03/04/2002 14:12:37 (GMT+2.00) Start System Log content real-time logging (Type Ctrl+C to stop logging): 03/04/2002 14:16:00 I:p1 SYN:UP.00 03/04/2002 14:16:02 I:p1 SYN:UP.01 03/04/2002 14:22:30 System Alive 03/04/2002 14:23:12 I:p2 SYN:UP.11 03/04/2002 14:23:15 I:p201 LAPB:CONN 03/04/2002 14:23:15 I:p205 LAPB:CONN 03/04/2002 14:23:15 I:p301 X25:RDY 03/04/2002 14:23:15 I:p305 X25:RDY
The System Log content can also be cleared through an appropriate command.
The commands for managing the System Log are described in the section Logging Functionalities of the chapter General and system commands. They are:
C LAs it can be seen from the previous examples, System Log events can be grouped in four classes on the base of their meanings. Each class is easily identifiable because the text of the message starts with an opportune prefix:
| Event type | Prefix | Meaning |
|---|---|---|
| GENERAL | no prefix | Signaling of general events such as Abilis CPX start. |
| ERROR: | E: | Signaling errors that require Abilis CPX restart. All the sessions are closed and Abilis CPX restarts. |
| WARNING | W: | Warning signaling. The occurred event is not critic, so that Abilis keeps on working. |
| INFORMATION | I: | Informative signaling. Important events are saved. |
For the full list of all the messages saved in the System Log and a short description of their meaning, refer to the Messages in the System Log section.
Another useful function, that is provided by the Abilis CPX, is the recording of all the events that are pertinent to connection's opening/closing and to port's state changes. These feature is called Events Log (or Debug Log).
This kind of information is highly technical and for being able to use them, it is necessary a deepened knowledge of Abilis CPX and of the X.25/ISDN protocols.
Events that are registered in the Events Log are grouped in the following classes:
| Mnemonic | Events classes |
|---|---|
| DIAG | Events related to port diagnostic and status. |
| COR | Events related to the Connection Oriented Router. |
| MLM | Events related to the Multi Link Manager driver. |
| EIR | Events related to the Enhanced ISDN Router. |
| EIRE | Extension of the events class related to the Enhanced ISDN Router. |
| PPP | Events related to the Point-to-Point Protocol driver. |
| ML | Events related to the Multi Links driver. |
Events are recorded in a circular buffer of fixed length that is kept in memory. The buffer maintains the more recent events, progressively eliminating the oldest. Every event is saved with its date and time of occurrence.
Usually the Events Log can store events for few days; however this time interval depends, exclusively, on the number and the type of events to record, that can also change from customer to customer.
The Events Log content is transferred from the memory to a proper file of the floppy disk every time the Abilis CPX is restarted or in correspondence to the user request, without restarting the Abilis CPX.
The system restart can be performed by the user through the RESTART SYSTEM command, that is available from both the the command interpreter of the Control Port and from the UTILITY of the LCD display of the frontal panel.
The user can request Events Log to be saved through the SAVE DEBUG command, that is available from both the the command interpreter of the Control Port and from the UTILITY of the LCD display of the frontal panel.
For being able to transfer the Events Log to the floppy disk, it is essential that the floppy disk, that contains the Abilis CPX software and that is inserted in floppy drive, should be NOT WRITE PROTECTED, otherwise, the Abilis CPX keeps on working, but the Events Log cannot be saved.
Using the command interpreter of the Control Port, it is possible to inspect the content of both the Events Log that is currently saved in memory and of the Events Log file stored on the floppy disk.
In both cases, events are displayed starting from the oldest one or from a certain date and time, that must be specified in the displaying command. it is also possible to select the events to display by specifying their class.
Here is an example of visualization of the Events Log stored in memory:
[14:31:37] ABILIS_CPX: D LDM
Current Local Time: Wednesday 03/03/2004 15:20:42 (GMT+1.00)
Date Time Po Ses Event and Parameters
------ ------ --- ----- ------------------------------------------------------
020304 165053 1 0 PortDiag SYNC:UP DCD:dn DTR:UP
020304 165053 2 0 PortDiag SYNC:UP DCD:dn DTR:UP
020304 165053 21 0 PortDiag PAD:dn DCD:dn DTR:UP
020304 165053 196 0 PortDiag EPLAPD Q931:dn X25:in
020304 165053 197 0 PortDiag EPLAPD Q931:dn X25:in
020304 165053 201 0 PortDiag LAPB:cg
020304 165053 202 0 PortDiag LAPB:cg
020304 165053 301 0 PortDiag X25:down
020304 165053 302 0 PortDiag X25:down
020304 165053 503 0 PortDiag MLM PLink:ln SLink:ln ATN:
020304 165053 504 0 PortDiag MLM PLink:ln SLink:ln ATN:
020304 165053 521 0 PortDiag ML PLINKs:NO-LINKS CHANs:STOPPED1
020304 165053 541 0 PortDiag PPP:DOWN
020304 165053 997 0 PortDiag MLM PLink:ln SLink:RD ATN:
020304 165053 998 0 PortDiag LAPB:cg
020304 165053 999 0 PortDiag X25:down
030304 102314 905 6 CallRx CG: CD:00
PID:01000000 UD:CP FF:
030304 102314 905 6 Routing Match PR:1
030304 102314 0 1 CallTx CG: CD:00
PID:01000000 UD:CP FF:
030304 102314 0 1 CallConnRx LSN:01 CG: CD:00
PID:01000000 UD:CP FF:
030304 102314 905 6 CallConnTx LSN:01 CG: CD:
PID: UD: FF:
030304 102450 905 6 ClrRx F0:A3 LSN:01
030304 102450 905 6 ClrConfTx 00:00 LSN:01
030304 102450 0 1 ClrTx 00:00 LSN:01
030304 102450 0 1 ClrConfRx 00:00 LSN:01
It is also possible to make Events Log records to be simultaneously sent to the current Control Port session. Events are displayed in the same time that they occurs and that they are recorded into the buffer in memory.
Here is an example of Events Log content real-time listing:
[14:31:37] ABILIS_CPX: START LDM
Current Local Time: Wednesday 03/04/2002 14:36:41 (GMT+2.00)
Start Debug Log content real-time logging (Type Ctrl+C to stop logging):
030402 143712 p905 s5 CallRx CG: CD:00
PID:01000000 UD:CP FF:
030402 143712 p905 s5 Routing Match PR:0
030402 143712 p0 s2 CallTx CG: CD:00
PID:01000000 UD:CP FF:
030402 143712 p0 s2 CallConnRx LSN:02 CG: CD:00
PID:01000000 UD:CP FF:
030402 143712 p905 s5 CallConnTx LSN:02 CG: CD:
PID: UD: FF:
03/04/2002 14:42:10 System Alive
030402 144514 p905 s5 ClrRx F0:A3 LSN:02
030402 144514 p905 s5 ClrConfTx 00:00 LSN:02
030402 144514 p0 s2 ClrTx 00:00 LSN:02
030402 144514 p0 s2 ClrConfRx 00:00 LSN:02
The Events Log content can also be cleared through an appropriate command.
The commands for accessing the Events Log are described in the section Logging Functionalities of the chapter General and system commands. The available commands are:
C LDM
As it can be seen from the previous examples, the Events Log contains a lot of information that are meaningless for the user, but that are very useful for the Abilis CPX technicians for solving eventual problems.
For a list of all the messages saved in the Events Log and a short description of their meaning, refer to Messages in the Events Log section.
Another very useful function, that is provided by Abilis CPX for problem solving, is the recording of the Exceptions Log.
An exception is an event that cause the Abilis CPX restart. It is generated every time the system is in any particularly critical situation, to prevent the normal operation.
In correspondence of such event, detailed information and circumstances about it are saved in the Exceptions Log.
In correspondence of an exception a message is also stored in the System Log, in this way it is possible to identify the cause of the system restart.
It has to be noted that such events type are very uncommon.
As well as System and Events Logs, the Exceptions Log is saved on disk. Consequently, the floppy disk that contains the Abilis CPX software and that is inserted in floppy drive, must be NOT WRITE PROTECTED, otherwise, the Abilis CPX keeps on working, but the Exceptions Log cannot be saved.
The commands for accessing the Exceptions Log are described in the section Logging Functionalities of the chapter General and system commands. The available commands are:
C LE The Exceptions Log contains a lot of information that are meaningless for the user, but that are very useful for the Abilis CPX technicians for solving eventual problems.
Print this page