Snmp Event Generation - Novell NETWARE 6-DOCUMENTATION Manual

SNMP Event Generation

Clients that are on the same subnet as the DHCP server do not have to be
configured for the subnet pool if the server is bound to all local subnet
addresses, or if the server has an address on each local subnet.
You can use the DNS/DHCP Management Utility to set up SNMP event
generation in the case of critical, major, warning, or minor events. The default
setting is Major, which causes the server to log all major and critical events.
Critical events are those that cannot or should not be ignored by the network
administrator. Major events denote a significant change in the state of the
server processing. Warning and Minor events are logged for maintenance and
diagnosis only. Warning and Minor events should not be turned on unless a
problem has developed.
All Critical and some Major events are logged on the local server console.
The following warning events can be logged or trapped for SNMP event
generation:
An eDirectory update to the subnet failed, causing degraded operation
(incomplete transactions are logged to a local file named
DHCPLOG.LOG).
SNMP recovered from an internal fault and the error code was logged.
A subnet was not configured and addresses are not available, causing
degraded operation.
The following minor events are logged and/or trapped for SNMP event
generation:
A Decline was generated against an IP address.
All logged file transactions have been reprocessed (operational).
Major events are logged or trapped for SNMP event generation. For example,
when the DHCPSRVR NLM is loaded and the server is operational and ready
for LAN-based clients.
The following events are logged or trapped for SNMP event generation:
The logger cannot open the recovery log file or is having difficulty
opening it. (The server is inoperative.)
The main thread cannot process lease expiration. (The server is
inoperative.)
49
Understanding