SNMP Event Generation

You can use the DNS/DHCP Management Console to set up SNMP event generation in the case of critical, major, warning, or minor events. The default setting is major and 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 NDS update to the subnet failed, causing degraded operation (incomplete transactions are logged to a local file named DHCPLOG.LOG).
• An internal fault recovered 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, if when the DHCPSRVR NLM is loaded; 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.)