Device Driver Messages

Logging

The NTRACE.OS2 device driver participates in IBM's NDIS logging extensions. The Network Trace device driver uses the LANMSGDD/FFST interface for posting messages. This interface enables device drivers to log messages to a centrally managed log file. Although we refer to the LANTRAN.LOG file, the actual name and/or location of the log file may vary. The destination for these messages is usually the LANTRAN.LOG, which is located in the directory specified in the /I: parameter to the LANMSGDD.OS2 device driver in CONFIG.SYS. If the drive is not specified in the /I:, the boot drive is assumed. If there is no /I: keyword, the default path is \IBMCOM on the boot drive. In certain circumstances, the NDIS environment may log using the FFST subsystem.

Interpreting LANTRAN.LOG Entries

All LANTRAN entries from NTRACE.OS2 are prefixed with one of the following:

Prefix	Description
`[NTR----]`	This is a generic prefix that indicates the message is associated with driver initialization.
`[NTR%1]`	Where %1 is a "module ID" in hexidecimal format. This allows the origin of the message to be traced back to a specific NTRACE.OS2 instance (in CONFIG.SYS) and its associated configuration section in PROTOCOL.INI. Example: `[NTR0005]`

When an NTRACE.OS2 instance is loaded and initialized, it will write the 2 lines into LANTRAN.LOG.

Example:

[NTR0003] Registered with Protocol Manager as Service Module NTRACE_NIF ID 0003
[NTR0003] Network Trace Device Driver NTRACE$ loaded

These lines can be used to link a specific module ID back to the name of the specific driver instance which is being referenced. In this case, all LANTRAN entries which are prefaced [NTR0003] are known to be written from the driver named NTRACE$ with a configuration section in PROTOCOL.INI named NTRACE_NIF.

Interpreting the Severity Level

All device driver messages have a severity code appended to the end of the "message ID". The list of severity codes and their meanings follows:

Severity Code	Meaning
`I`	Informational
`W`	Warning
`E`	Error

Device Driver Messages - INIT Time

The following INIT Time Messages are posted to the LANTRAN.LOG and may occur during the IPL of the system:

Message ID	Prefix	Message Text	Description and Action
`NTR0001I`	`[NTR----]`	Network Trace Device Driver v%1.%2	Version number of the Network Trace device driver.
`NTR0002I`	`[NTR----]`	Copyright (c) Golden Code Development 1999, 2000	Displays copyright information.
`NTR0006I`	`[NTR----]`	Default device driver parameter are in effect	No DEVICE= statement parameters were detected.
`NTR0007I`	`[NTR----]`	The following device driver parameters are in effect:
`NTR0008I`	`[NTR----]`	%1	DEVICE= statement parameters are listed.
`NTR0009I`	`[NTR%1]`	Network Trace Device Driver %2 loaded	This indicates successful INIT time processing.
`NTR0010E`	`[NTR----]`	Internal error detected: Invalid DevHelp Entry Point	Operating system fault, please reboot the system.
`NTR0011E`	`[NTR----]`	Driver didn't install due to serious error(s) detected in DEVICE parameters	DEVICE= statement contains syntactically incorrect parameters.
`NTR0012E`	`[NTR----]`	A previously installed instance detected	Instance name specified with the DEVICE= Statement conflicts with a previous loaded instance.
`NTR0013E`	`[NTR----]`	High Resolution Timing can't be turned on (32 timers already installed)	Device Driver loads, but high resolution timing mode is disabled.
`NTR0020E`	`[NTR----]`	Cannot open NDIS Protocol Manager interface	Protocol Manager is not running. Check the CONFIG.SYS file to ensure the DEVICE=...PROTMAN.OS2 statement is above the NTRACE.OS2 statement.
`NTR0021E`	`[NTR----]`	Cannot get Protocol Manager Information	Internal error reported by the call to Protocol Manager. Contact technical support.
`NTR0022E`	`[NTR----]`	Cannot find itself in Protocol Manager Information	Network Trace device driver instance name does not match the a section in PROTOCOL.INI file.
`NTR0023E`	`[NTR----]`	Cannot construct bindings table. Check BINDINGS entry for NTRACE in PROTOCOL.INI	Check BINDINGS entry for NTRACE in PROTOCOL.INI file.
`NTR0024E`	`[NTR----]`	Cannot register with Protocol Manager. RC = %1 (hex)	Internal error reported by Protocol Manager. Contact technical support.
`NTR0025E`	`[NTR----]`	Cannot allocate GDT selectors	The system is constrained on the available number of GDT selectors. Try reducing the MaxBufSegments value.
`NTR0026I`	`[NTR----]`	Can't identify NDIS module type from MODULETYPE= statement in PROTOCOL.INI	Incorrect MODULETYPE= statement in PROTOCOL.INI.
`NTR0027I`	`[NTR%1]`	Registered with Protocol Manager as %2 Module %3 ID %4 (hex)	Reports the module ID assigned to the device driver by Protocol Manager. This can be used to identify all related instances of the driver.

Device Driver Messages - Run Time

The following Run Time Messages are posted to the LANTRAN.LOG and may occur during execution of Network Trace program:

Message ID	Prefix	Message Text	Description and Action
`NTR0100E`	`[NTR%1]`	NDIS violation, SystemRequest operation code %2 (hex) received	Possible misconfiguration of NDIS environment.
`NTR0101E`	`[NTR%1]`	NDIS Configuration error. Possible attempt to bind to a non-MAC module	Possible misconfiguration of NDIS environment.
`NTR0102E`	`[NTR%1]`	NDIS Bind failed. RC = %2 (hex)	Internal error reported by the Bind function.
`NTR0103E`	`[NTR%1]`	MAC ID %2 adapter check: %3 (hex), %4	Hardware fault as reported by the MAC driver. MAC driver will attempt a recovery.
`NTR0104E`	`[NTR%1]`	NDIS OpenAdapter failed. RC = %2 (hex)	Internal error reported by the OpenAdapter function.
`NTR0105W`	`[NTR%1]`	Warning. NDIS Open Adapter issued with OpenOptions = 0. Normally adapter should have been open yet	This is an unexpected but non-fatal condition.
`NTR0106E`	`[NTR%1]`	NDIS SetLookAhead failed. RC = %2 (hex)	Internal error reported by the SetLookAhead function.
`NTR0107E`	`[NTR%1]`	NDIS SetPacketFilter failed. RC = %2 (hex). RC = %3 (hex)	Internal error reported by the SetPacketFilter function. This indicates a possible problem with the calculated packet filter OR with the -pf option if the user override was used on the NTRACE.EXE command line.
`NTR0108I`	`[NTR%1]`	Bound to %2 with index %3, module ID %4 (hex), %5	This message reports successful binding.
`NTR0109E`	`[NTR%1]`	MAC ID %2 adapter reset failed. RC = %3 (hex)	Fatal hardware fault as reported by the MAC driver. Determine the status of the network adapter.
`NTR0110E`	`[NTR%1]`	NDIS TransferData failed. RC = %2 (hex)	Internal error reported by the TransferData function.
`NTR0111E`	`[NTR%1]`	VMAlloc for intermediate buffer failed. RC = %2 (hex)	More memory was requested from global system area than could be obtained through VMAlloc. Close down applications or reduce the number of segments requested in NTRACE.EXE parameter.
`NTR0112E`	`[NTR%1]`	LinToGDTSelector for intermediate buffer failed. RC = %2 (hex)	Operating system error, please reboot the system.
`NTR0113E`	`[NTR%1]`	VMFree for intermediate buffer failed. RC = %2 (hex)	Internal error in the driver. Possible data segment corruption.
`NTR0114E`	`[NTR%1]`	NDIS ReceiveRelease failed. RC = %2 (hex)	Internal error reported by the OpenAdapter function.
`NTR0115W`	`[NTR%1]`	Warning. Promiscuous mode not supported	This MAC Driver doesn't support promiscuous mode. Execution of the Network Trace program continues.
`NTR0116E`	`[NTR%1]`	Internal error ID %2, data %3, %4, %5	Contact technical support.
`NTR0117I`	`[NTR%1]`	MAC ID %2 unrecognized status change indication %3 (hex), data %4 (hex)	Status of the Token-Ring has changed. See NDIS references.
`NTR0118I`	`[NTR%1]`	Some frames will be rejected by mask %2 (hex)	Specified RejectFrames mask has been activated.
`NTR0119I`	`[NTR%1]`	Dedicated Trace mode entered	All networking is now disabled until tracing is closed.
`NTR0120I`	`[NTR%1]`	MAC ID %2 ring status change: %3 (hex)%4	Token-Ring status change has occurred.
`NTR0121I`	`[NTR%1]`	MAC ID %2 adapter reset in progress	MAC adapter reset has started but is not yet complete.
`NTR0122I`	`[NTR%1]`	MAC ID %2 adapter reset completed	The MAC adapter reset which was in progress is now complete.
`NTR0123I`	`[NTR%1]`	MAC ID %2 adapter presence change: %3 (hex)%4	A PCMCIA MAC adapter has either been inserted or removed.