Table 15 | Connection Methods and Applications |
|
| |
|
|
|
|
|
|
| Console Port (Serial Cable or |
| Telnet/SSH, or CORBA |
CWI Application | Through a Terminal Server) | Telnet (No XML) | Connection (XML) | |
|
|
|
| |
Launch and Login | Yes. Enter the serial port or | Yes. Enter the DNS name or IP | Yes. Enter the DNS name or IP | |
|
| terminal server and port name. | address. | address. |
|
|
|
| |
Main Desktop | Yes, but no notifications or | Yes, but no notifications or | Yes | |
|
| associated alarms are | associated alarms are |
|
|
| displayed. | displayed. |
|
|
|
|
| |
Alarm Viewer | Yes, but no alerts are | Yes, but no alerts are | Yes | |
|
| displayed. | displayed. |
|
|
|
|
| |
Alarm Dashboard | — | — | Yes | |
|
|
|
| |
Inventory Viewer | Yes | Yes | Yes | |
|
|
|
| |
Interface Viewer | Yes | Yes | Yes | |
|
|
|
| |
Telnet Plus/SSH Plus | — | Yes | Yes | |
|
|
|
| |
Terminal Plus | Yes, but are mutually exclusive | — | — | |
|
| other applications1. |
|
|
Troubleshooter | — | — | Yes | |
|
|
|
| |
Configuration Editor | Yes | Yes | Yes | |
|
|
|
|
|
1.When connecting through the serial port or terminal server, the Terminal Plus application requires exclusive access to the connection, so no other applications can be launched or refreshed while it is open.
Testing the CWI Client
Verify that you can connect to the router by logging in to the router. See the “Installing CWI” section on page 7 for procedures. If you are unable to log in to the router, see the “Troubleshooting Basic IP Connectivity” section on page 24.
Troubleshooting Basic IP Connectivity
This section provides information on troubleshooting basic IP connectivity problems when attempting to log in to a router using CWI.
If you are unable to connect to the router HTTP server using the browser, follow these steps in sequence, exiting the test steps when a failure is encountered.
Step 1 Ping the IP address of the router management Ethernet interface from the client PC or workstation.
If this step fails, the problem can be an incorrect IP address, incorrect management Ethernet interface configuration, or a network connectivity problem.
Step 2 (Optional) Ping the DNS name of the router.
If this step fails, the problem is an incorrect
Step 3 Check that the HTTP server is running on the router using the following command:
RP/0/RP0/CPU0:router# show process emweb
If this step fails, start the HTTP server. See the “Setting Up the Common Configuration for IP Connection Methods” section on page 5.
If you are unable to log in to the router from the CWI login screen, run the Troubleshooter application at the prompt. See Cisco Craft Works Interface User Guide for information on using the Troubleshooter application.
24
