Audit and Error Logging
Log messages provide diagnostics information for SNA protocol problems, user errors, or system problems. The types of events logged can be specified using the administration tools, to record more or less detailed information as required.
In a client-server system, log messages can be written to a single central log file, or to a separate file on each computer.
Log files are ASCII text and can be viewed by a standard text editor such as vi. The following is an example of an error log.
----------------------- 10:56:51 GMT 31 Oct 2002 --------------------- SNAPLLC2 Message 1024 - 71, Subcode: 1 - 3 Log category: EXCEPTION Cause Type: Config / External System: doodles Link activation failed - adjacent link station ETHL0 is not responding. Adjacent station: MAC address = 440039003900 ( 22009C009C00), SAP address = 04 Local station: MAC address = 080020C139B7 ( 100004839CED), SAP address = 04 Cause: The link activation request has failed because the adjacent link station is not responding to TEST frames. Action: Check the configuration; check the link hardware.
API Tracing
API Tracing allows individual programmers to trace the calls they make across the SNAP-IX APIs. This is controlled by environment variables and is very useful when developing and debugging SNAP-IX applications. This is an example from a CPI-C API trace.
-------------------------------- 11:00:02.13 GMT 31 Oct 2002
CMSTPN request
Conversation ID = 01000001
Partner TP name =
4150494E 47440000 20202020 20202020 .&.+............ APINGD..
20202020 20202020 20202020 20202020 ................
20202020 20202020 20202020 20202020 ................
20202020 20202020 20202020 20202020 ................
TP name length = 6
Conversation characteristics
Partner TP name =
40404040 40404040 40404040 40404040 @@@@@@@@@@@@@@@@
40404040 40404040 40404040 40404040 @@@@@@@@@@@@@@@@
40404040 40404040 40404040 40404040 @@@@@@@@@@@@@@@@
40404040 40404040 40404040 40404040 @@@@@@@@@@@@@@@@
-------------------------------- 11:00:02.14 GMT 31 Oct 2002
CMSTPN response, result = CM_OK
Conversation characteristics
Partner TP name =
C1D7C9D5 C7C44040 40404040 40404040 APINGD ......@@@@@@@@@@
40404040 40404040 40404040 40404040 @@@@@@@@@@@@@@@@
40404040 40404040 40404040 40404040 @@@@@@@@@@@@@@@@
40404040 40404040 40404040 40404040 @@@@@@@@@@@@@@@@
Link / Node Tracing
Tracing can be activated as required to help with diagnosis of specific problems. It can be used to trace
- links between SNAP-IX and attached system
- data flowing to all applications
- flows between the SNAP-IX node and the remote system.
This is an example from a line trace.
------------------------------------------------ 17:21:04.040 PDT 22 Oct 1997
SND>> ACTPU +RSP LFSID:00000 SDLC0.SDLCP1.SDLCL1
TH: 2D000000BC9B BBIU EBIU EFI OAF:00 DAF:00 SNF:BC9B
RH: EB8000 SC FI
RU: 11124040 40404040 40400000 07010000 .. ...... ..@@@@@@@@......
00000000 .... ....
------------------------------------------------ 17:21:04.230 PDT 22 Oct 1997
SND>> ACTLU +RSP LFSID:02000 SDLC0.SDLCP1.SDLCL1
TH: 2D000002BC9C BBIU EBIU EFI OAF:02 DAF:00 SNF:BC9C
RH: EB8000 SC FI
RU: 0D020100 85800000 0C060100 01000000 ....e........... ................
------------------------------------------------ 17:21:04.240 PDT 22 Oct 1997
SND>> NOTIFY RQD1 LFSID:02000 SDLC0.SDLCP1.SDLCL1
TH: 2C0000020000 BBIU EBIU OAF:02 DAF:00 SNF:0000
RH: 0B8000 FMD FI BC EC
RU: 8106200C 06030001 000000 a.......... .. ........
------------------------------------------------ 17:21:04.460 PDT 22 Oct 1997
>>RCV FMD +RSP LFSID:02000 SDLC0.SDLCP1.SDLCL1
TH: 2C0000020001 BBIU EBIU OAF:02 DAF:00 SNF:0001
RH: 838000 FMD
------------------------------------------------ 17:21:04.550 PDT 22 Oct 1997