Листовка для Cisco Cisco Secure User Registration Tool 2.0
Page
COMPANY CONFIDENTIAL --- FOR INTERNAL CISCO DISTRIBUTION ONLY
Cisco Secure User Registration Tool 2.5.x
Error Message Guide
1
Cisco Secure User Registration Tool 2.5.x
Error Message Guide
Error Message Guide
This guide describes the Cisco Secure User Registration Tool (URT) 2.5.x error messages, possible causes, and recovery
solutions. Use this Error Message Guide as your first resource in isolating and resolving URT problems.
solutions. Use this Error Message Guide as your first resource in isolating and resolving URT problems.
URT is a complex product to debug. It can be difficult to determine the cause of a problem by reviewing only a single error
message or by reviewing only the content of a single log file. Problems are typically revealed by reviewing a series of
messages or by reviewing several log files. If any URT components (such as switches, DHCP, PDC, BDCs, and so on) are
configured incorrectly, URT might not function properly.
message or by reviewing only the content of a single log file. Problems are typically revealed by reviewing a series of
messages or by reviewing several log files. If any URT components (such as switches, DHCP, PDC, BDCs, and so on) are
configured incorrectly, URT might not function properly.
If you are unable to resolve problems using the information in this Error Message Guide, open a support call with the Cisco
TAC.
TAC.
The following steps describe how to enable trace(when relevant) and gather the log files from all three URT components:
1. Client Logs
Traditional Client Logs
Enable the trace on the traditional client
Enable the trace on the traditional client
Start the URT Administrative GUI.
Click on the NT/NDS Domain name in the left frame where the clients trace has to be enabled.
Click Customize followed by Configure Domain Options.
Check the Enable trace check box. See Figure 1.
Figure 1 Enabling Trace on the Traditional Client
Now perform client log into and collect traditional client logs UrtService.log and OnOffHandler.log located in %windir% or
%temp% on the client machine.
%temp% on the client machine.