Using event logging

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

Using event logging

Routing and Remote Access logs routing events extensively in the system event log. You can use information in the event logs to troubleshoot routing processes.

Four levels of logging are available:

• Log errors only

• Log errors and warnings (the default)

• Log the maximum amount of information

• Disable event logging

For example, if an OSPF router is unable to establish an adjacency on an interface, you can:

1. Disable OSPF on the interface.

2. Change the level of logging for OSPF to log the maximum amount of information.

3. Enable OSPF on the interface.

4. Examine the system event log for information on the OSPF adjacency process.

5. Change the level of logging for OSPF to log error information only.

You can further troubleshoot the adjacency problem by analyzing the OSPF entries in the system event log.

Logging is available in the following dialog boxes:

• General tab of the properties of IP Routing\General

• General tab of the properties of IP Routing\Network Address Translation (NAT)

• General tab of the properties of IP Routing\RIP

• General tab of the properties of IP Routing\OSPF

• General tab of the properties of IP Routing\IGMP

Notes

• Logging consumes system resources and should be used sparingly to help identify network problems. After the event has been logged or the problem is identified, you should immediately reset logging to its default value (log errors and warnings).

• When logging the maximum amount of information, the logging information can be complex and very detailed. Some of this information is useful only to Microsoft Product Support Services engineers or to network administrators who are very experienced with Routing and Remote Access.

• Open Shortest Path First (OSPF) is not available on Windows XP 64-bit Edition (Itanium) and the 64-bit versions of the Windows Server 2003 family.