Auditing can be used to perform an analysis of historical data and to help diagnose operational difficulties. Auditing uses a Btrieve database to store and manage data enabling meaningful trend analysis.
When auditing is enabled, every incidence of address deletion, addition, and rejection is recorded in the audit log. The beginning and end of each session is marked to help make sense of the audit log. The beginning session contains records defining the session in terms of addresses already assigned.
Additionally, other major events or alert situations that cause SNMP traps are also audited. Other incoming DHCP requests are also logged, including honored renewal requests and those rejected or dropped.
The following types of console log entries are generated by both DNS and DHCP:
For each NetWareAlert message generated, an entry is provided in the /SYSTEM/SYS$LOG file.
The DHCP server provides a foreground screen log of every packet received and each reply generated to maintain continuity with the DHCP 2.0 server. The screen provides a useful real-time indication of DHCP 3.0 server operations.
The DHCP server has a debug log feature (primarily used by Novell technical support and engineering groups) that records the exchange of DHCP messages to a screen log or the DHCPSRVR.LOG file (in ASCII text) in the server's \ETC\DHCP directory. When loading the DHCPSRVR, the administrator can use one of three flags to activate the debug log feature. The following table explains the use of the flags.