Table Of Contents

Troubleshooting CWI Connectivity

Running Fault Isolation Tests

Understanding the Test Types for the Troubleshooter

Using the Troubleshooter

Troubleshooting CWI Connectivity

---

This chapter describes how to run fault isolation tests with the Troubleshooter application. These sections are provided:

•Running Fault Isolation Tests

•Understanding the Test Types for the Troubleshooter

•Using the Troubleshooter

Running Fault Isolation Tests

You can run fault isolation tests on the client/server communications path between the CWI and the device through the Troubleshooter application.

---

Note The Telnet/SSH server must be enabled before you can manage a device using certain CWI features. These features include the Telnet/SSH application, the Troubleshooter application, and viewing committed configuration changes using the Configuration Change dialog box. See Cisco IOS XR Getting Started Guide for information on enabling the Telnet/SSH server.

---

If a failure is encountered, you can click the Failure button next to the corresponding test. The Failure button opens a window that describes the reason for the failure, possible cause, and recommended repair action. If CWI can perform a repair action, the Repair button is enabled.

Understanding the Test Types for the Troubleshooter

Table 5-1 describes the test types for the Troubleshooter application.

Table 5-1 Test Types for the Troubleshooter 

Name	Description
Device DNS Name Test	Checks the Java DNS1 resolution from the client (proper DNS name support for the device). When this test fails, a list of possible causes and suggested repair actions is provided. No automatic repair is provided.
Client to Device Connectivity Test	Checks for proper end-to-end network connectivity between the device and the client. When this test fails, a list of possible causes and suggested repair actions is provided. No automatic repair is provided.
CORBA Services and CORBA Agent Test (CORBA connection only)	Checks whether the CORBA2 Agent can service XML requests. When this test fails, a list of possible causes and suggested repair actions is provided. An automatic repair is provided in some instances of this test failure.
CORBA Services and TTY Agent Test (TTY connection only)	Checks whether the TTY Agent can service XML requests. When this test fails, a list of possible causes and suggested repair actions is provided. An automatic repair is provided in some instances of this test failure.

1 DNS = Domain Name System 2 CORBA = Common Object Request Broker Architecture

Using the Troubleshooter

The Troubleshooter can be started when a problem is detected logging in to the device. It can also be started from a device object in the Inventory Tree.

To use the Troubleshooter, perform the following steps:

---

Step 1 To open the Troubleshooter, choose one of the following options:

•Right-click a device from the Inventory Tree and choose Troubleshooter.

•Choose an object in the Inventory Tree. Choose Tools > Troubleshooter.

The CWI Troubleshooter dialog box is displayed (see Figure 5-1).

Figure 5-1 CWI Troubleshooter

Step 2 Click Run to start the communications test.

The Troubleshooter runs the communications test. Results are displayed in the CWI Troubleshooter results pane (see Figure 5-2). Failed tests are indicated by a red Failed button.

Figure 5-2 CWI Troubleshooter Results

Step 3 Click Failed to open a Test Failure dialog box (see Figure 5-3) if a test fails.

Figure 5-3 Notification Test Failure Dialog Box

The dialog box displays the following information:

•Description of the error

•List of possible causes

•Repair action

The Repair button is enabled if the CWI can attempt to fix the problem. In some cases, you must perform the suggested actions in the Repair Actions field in addition to clicking the Repair button to fix the problem.

Step 4 If the Repair button is available and you want the CWI to attempt to fix the problem, click Repair.

The Troubleshooter attempts to fix the problem. If the repair is successful, a Successful Repair dialog box (see Figure 5-4) appears.

Step 5 Click OK.

Figure 5-4 Successful Repair Dialog Box

If the Repair button is not available or you want to manually fix the problem, follow the suggested repair actions provided in the Repair Action field.

Step 6 After the problem is repaired by using the Repair button or following the suggested repair actions, click Close.

---

Note If the Notification Test was repaired using the Troubleshooter, you must reload the node. See the "Reloading Device Information" section for information on using the Reload feature.

---

The Troubleshooter is closed.

---