Compartir a través de


Event logging

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Event logging

Network Load Balancing uses Windows event logging to record information about important events. You can view the event log using Event Viewer.

Network Load Balancing classifies logged events into the following categories:

Event category Description

Information events

Records normal state transitions, such as driver startup, the completion of convergence, and the completion of cluster-control actions. These events are recorded for informational purposes only.

Warning events

Records abnormal occurrences that do not impede cluster operations. These events can indicate a configuration problem, such as an invalid dedicated IP address or other parameter. They can also indicate a temporary condition, such as limited driver resources. Cluster operations are not disrupted when warning events occur, and are not considered errors.

Error events

Records major problems or errors that might require immediate attention, such as significant cluster configuration parameter problems, detected inconsistencies, or unexpected execution errors. Error events usually disrupt cluster operations and might require individual hosts to be stopped and reconfigured. Note that errors can occur under normal operations when you update the cluster by adding or modifying port rules. For more information, see Error detection and handling.

Event log records provide crucial information when you are analyzing and solving problems. Use the nlb.exe display command to display the most recent event log records produced by Network Load Balancing. This information should be copied into the text of any e-mail message sent to Microsoft requesting technical support. For more information, see Nlb.

Network Load Balancing Manager logging

Network Load Balancing Manager does not use Windows event logging and therefore you can not use Event Viewer to review messages from Network Load Balancing Manager. You instead must explicitly enable Network Load Balancing Manager logging and define a specific log file. Enable Network Load Balancing Manager logging by clicking Log Settings in the Network Load Balancing Manager Options menu. Check the Enable logging box and specify a name and location for the log file.

You should always manage a Network Load Balancing cluster from a trusted and secure computer, particularly when logging is enabled. The Network Load Balancing Manager log file contains potentially sensitive information about the Network Load Balancing cluster and hosts, so it must be properly secured. By default, the log file inherits the security settings of the directory in which it is created, so you might have to change the explicit permissions on the file to restrict read and write access to those individuals who don't need full control of the file. Be aware that the individual using Network Load Balancing Manager does require full control of the log file. For more information, see Access Control How To....

Notes

  • WLBS stands for Windows NT Load Balancing Service, the former name of Network Load Balancing in Windows NT 4.0. For reasons of backward compatibility, WLBS continues to be used in certain instances.

  • For information on how to interpret messages, refer to the Microsoft Windows Resource Kits Web site.