Cisco VXC desktop—click the System Settings icon on the Cisco VXC toolbar (administrators can also click the Admin Mode button on the Login dialog box).
Figure 1. System Settings menu
Classic Desktop—click User Name (User Name is the user who is logged-on and is located at the bottom-left side of the task bar), and select either Network Test (for network tools Ping and Trace Route) or System Tools(for system tools to configure Trace and Event log settings, and to view INI files)
Figure 2. Desktop menu
Additional system tool features such as Write Event Log to USB, Network Capture to USB, Trace Action, Delay on Trace, and Trace to/from USB, can be found in the Shortcut Menu (right-click on the Classic Desktop) as described in Shortcut menu.
Use the System Tools dialog box (System Settings icon > System Tools) to configure Trace and Event log settings, and for CMOS management (extract and restore cmos settings as described in Extract CMOS Settings to a USB key for distribution). It also allows you to view wnos.ini and user.ini cached information for troubleshooting purposes.
Figure 3. System Tools dialog box
Use the Trace and Write Event log options on the General tab to configure the settings you want (be sure to enable the EnableTrace option of the Privilege parameter in a wnos.ini file - see INI Files Reference Guide for Cisco Virtual Experience Client 2112/2212 ).
Use the Network capture to USB option on the General tab to enable the capture of network information (a network trace of all traffic coming in and out of the zero client) to a USB drive that is inserted into the zero client (after logon and use of the XenDesktop server or network, you will see a WTOS_WS.pcap file in the USB drive which you can analyze using software such as a packet analyzer used for network troubleshooting, analysis, and so on).
Be sure to insert the USB drive into the zero client before selecting the Network Capture to USB option. Note that the Network Capture to USB option is automatically cleared if there is no USB drive inserted and you exit the dialog box, or after restarting the zero client (if needed, you must select the option again).
Figure 4. Global INI tab
If you are using global INI files, use the Global INI tab to view wnos.ini information.
If you are using username INI files, use the user.ini tab to view user.ini information.
Figure 5. Mirror File Server tab
Use the Mirror File Server tab to view, format, and delete locally stored files that are designated within the wnos.ini as backup (the locally saved files will be used when the file server is not accessible). The files that are saved locally are copies of files within the wnos folder on the file server. For MirrorFileServer parameter details, see
INI Files Reference Guide for Cisco Virtual Experience Client 2112/2212 .
Collect Troubleshooting Information
Use the following procedure to copy Cisco VXC 2112/2212 event logs, network traces, and a coredump to a USB key for troubleshooting purposes.
Include the following INI parameters in the INI file for the device:
Reboot the device to allow the Cisco VXC 2112/2212 to load the updated INI file.
Connect a USB key to the Cisco VXC 2112/2212.
Enable the trace and capture options on the Cisco VXC 2112/2212 (the required steps differ depending on whether the device is running the Cisco VXC Desktop or the Classic Desktop):
Cisco VXC Desktop
Enter Admin mode.
Choose System Tools.
Under Trace Action, choose Capture (to capture ICA and RDP traces to the device).
Check the Trace to/from USB box (to capture ICA and RDP traces to the USB key).
Under Write Event Log to USB, choose Persistent (to capture the event log to the USB key).
Under Network Capture to USB, choose Persistent (to capture Wireshark network traces to the USB key).
Right click on the Cisco VXC 2112/2212 desktop.
Choose Trace to/from USB (to capture ICA and RDP traces to the USB key). A check mark appears to indicate that this option is enabled.
Choose Network capture to USB > Persistent (to capture the event log to the USB key). A check mark appears to indicate that the Persistent option is selected.
Choose Write Event Log to USB > Persistent (to capture Wireshark network traces to the USB key). A check mark appears to indicate that the Persistent option is selected.
Perform the steps to duplicate the issue that requires troubleshooting.
If you need to reboot the Cisco VXC 2112/2212, recheck to be sure that the desired options in step 4 are still selected after the reboot.
After a coredump is complete, the USB key should contain the following files:
WTOS_log.txt: Event log file
WTOS_WS.pcap: Network trace file
WTOS_coredump: Coredump file
Use the Network Tools dialog box (System Settings icon > Network Tools) to access Ping (Packet InterNet Groper) and Trace Route tools for checking the integrity of the network connection (ping also checks the usability of the network configuration and the availability of all equipment required to communicate between the zero client and the ping destination). Generally, Ping and Trace Route are used for system diagnostics by, or under the direction of, a network administrator.
Use the Ping dialog box to execute the ping diagnostic utility and display response messages. Ping sends an echo request to a network host. The host parameter is either a valid host name or an IP address. If the host is operational and on the network, it responds to the echo request. By default, echo requests are sent until interrupted (by clicking Stop). Ping sends one echo request per second and calculates round trip times and packet loss statistics. It displays a brief summary upon completion of the calculation.
The ping utility can be used to:
Determine the status of the network and various foreign hosts
Track and isolate hardware and software problems
Test, measure, and manage networks
Determine the IP address of a host if only the host name is known
Not all network equipment will respond to ping packets, because this is a common mechanism used in denial-of-service attacks. Lack of response does not necessarily indicate that the target of the ping is unusable for other purposes. However, a response provides a definite indication that connectivity from the Cisco VXC client to the remote endpoint exists.
Figure 6. Ping tab
Use the following guidelines:
Enter Hostname or IP—Enter the IP address, DNS-registered host name, or WINS-registered host name of the target to be pinged.
Data area—Displays ping response messages. The ping command sends one echo request per second, calculates round trip times and packet loss statistics, and displays a brief summary upon completing the calculation.
Start—Executes the ping command. If the host is operational and on the network, it responds to the echo request. By default, echo requests are sent until interrupted by clicking Stop.
Stop—Terminates the ping request and leaves the Ping dialog box open (so you can read the summary posted in the data area).
Trace Route tab
Use the Trace Route dialog box to execute the tracert diagnostic utility and display response messages. The tracert utility traces the path from your zero client to a network host. The host parameter is either a valid host name or an IP address. The tracert utility sends out a packet of information three times to each device (routers and computers) in the path and displays the round trip response times and identifying information in the message box.
Figure 7. Trace Route tab
Use the following guidelines:
Enter Hostname or IP—Enter the IP address, DNS-registered host name, or WINS-registered host name of the target to be traced.
Data area—Displays round-trip response time and identifying information for each device in the path.
Start—Executes the tracert command.
Stop—Terminates the tracert command and leaves the Trace Route dialog box open (so you can read the information posted in the data area).