Cisco CRS-1 Series User manual

Quick Start Guide
Cisco CRS-1 Series Carrier Routing System Craft Works Interface
Quick Start Guide
Cisco IOS-XR Software Release 2.0
1Introduction
2About the CWI
3Getting Started
4Setting Up the Router and CWI Client
5Getting Started with the CWI
6CWI Overview
7CWI Desktop Window
8Configuration Desktop Window
9Obtaining Documentation
10 Documentation Feedback
11 Obtaining Technical Assistance
12 Obtaining Additional Publications and Information

2
1 Introduction
This document introduces the Craft Works Interface (CWI) that supports Cisco IOS-XR Software Release 2.0. The following
sections are provided:
•About the CWI, page 2
•Getting Started, page 3
•Setting Up the Router and CWI Client, page 6
•Getting Started with the CWI, page 11
•CWI Overview, page 18
•CWI Desktop Window, page 18
•Configuration Desktop Window, page 20
•Obtaining Documentation, page 22
•Documentation Feedback, page 23
•Obtaining Technical Assistance, page 23
•Obtaining Additional Publications and Information, page 24
Related Documentation
Refer to the following list for related documents that may be useful:
•Cisco CRS-1 Series Carrier Routing System Getting Started Guide
•Cisco CRS-1 Series Carrier Routing System Craft Works Interface User Interface Guide
•Cisco CRS-1 Series Carrier Routing System Craft Works Interface Configuration Applications Reference Guide
•Cisco CRS-1 Series Carrier Routing System Craft Works Interface Configuration Guide
Intended Audience
This document is intended for experienced service provider administrators, Cisco telecommunication management engineers,
and third-party field service technicians that have completed the required Cisco router training sessions.
2 About the CWI
The CWI is a client-side application used to configure and manage routers. The management and configuration features include
fault, configuration, security, and inventory, with an emphasis on speed and efficiency.
The CWI provides a context-sensitive graphical representation of the objects in a router, simplifying the process of configuring
and managing the router. The CWI allows you to log in to multiple routers and perform the following management tasks:
•View, filter, sort, search, correlate, purge, and monitor real-time alarms.
•View, filter, export, and search real-time inventory and interface object attribute information.
•Display a dynamic graphical representations of routers.
•Telnet/Secure Shell (SSH) to the router for command-line interaction.
•Troubleshoot management connectivity problems.

3
The CWI provides three ways to configure and manage a router:
•Using a Telnet or SSH session launched from the CWI, which allows you to configure and manage the router using
command-line interface (CLI) commands.
•Using the Configuration Editor or Replace Configuration Editor, which allows you to view and edit the running
configuration in CLI format. The configuration editors provide common text editing functionality as well as traditional CLI
features. See the “Configuration Editor” section on page 22 and the “Replace Configuration Editor” section on page 22.
•Using the graphical configuration applications. See the “Configuration Desktop Window” section on page 20.
Support is provided to manage a two-stage commit functionality, which includes locking and rollback control.
3 Getting Started
This section provides information you need to know before you can start setting up a router and CWI client. The following
information is provided:
•Network Considerations, page 3
•Prerequisites, page 4
Network Considerations
The following network information must be taken into consideration before starting the minimum router and CWI client
configuration.
Basic Configuration
The basic configuration is not secure. See the “Setting Up the Required Management Services Without a Secure Connection”
section on page 8 for procedures.
Secure Socket Layer Encryption Configuration
The secure configuration has Secure Socket Layer (SSL) encryption. If you use the SSL protocol on your network, use the SSL
configuration. See the “Setting Up the Required Management Services with a Secure Connection” section on page 8 for
procedures.
IP Security
IP security (IPSec) does not require any special configuration for CWI on the router or client. See the “Setting Up the Required
Management Services Without a Secure Connection” section on page 8 for procedures.
Firewall
If you have a firewall in your network, you can use the basic or SSL encryption configurations. See the “Setting Up the Required
Management Services with a Secure Connection” section on page 8 and “Setting Up the Required Management Services Without
a Secure Connection” section on page 8 for procedures.
The ports listed in Table 1 must be opened when configuring the firewall. Refer to the firewall documentation for information
on opening the ports.
Table 1 Firewall Ports
Component Port Direction
HTTP/HTTPS 80/443 Inbound
IIOP/IIOPSSL 10001/10002 Inbound

4
Virtual Private Network
When setting the minimum router configuration you must use the client Virtual Private Network (VPN) IP address and Domain
Name Server (DNS) name instead of the client IP address and DNS name when configuring the IP hostname for the CWI client.
This mapping is required for the client to receive notifications from the router. See Step 3 in the “Setting the Minimum Router
Configuration” section on page 7.
If you have a VPN, you can use the basic or SSL encryption configurations. See the “Setting Up the Required Management
Services with a Secure Connection” section on page 8 and “Setting Up the Required Management Services Without a Secure
Connection” section on page 8 for procedures.
Dual-Homed
Dual-homed devices are used to bridge two networks. You can run an instance of CWI on the dual-homed device so that you
can access the secondary network. You will require terminal services or X-client software to run the CWI graphical application
from the client PC. A dual-homed device contains a client-side interface (IP address) and router-side interface (IP address). The
client-side is the primary interface, and the router-side is the secondary interface. (See Figure 1.)
Figure 1 Dual-Homed Device Configuration
When setting the minimum router configuration you must use the dual-homed device router-side (secondary) IP address and
DNS name when configuring the IP hostname for the CWI client. This mapping is required for the client to view the notifications
from the router received by the dual-home instance of CWI. See Step 3 in the “Setting the Minimum Router Configuration”
section on page 7.
If you have a dual-homed device in your network, you can use the standard or SSL encryption configurations. See the “Setting
Up the Required Management Services with a Secure Connection” section on page 8 and “Setting Up the Required Management
Services Without a Secure Connection” section on page 8 for procedures.
Prerequisites
Prerequisites ensure that the CWI client and router are correctly set up to allow them to communicate. Meeting all prerequisites
before starting any of the procedures in this guide is recommended to ensure successful communication between the CWI client
and router.
The following prerequisites are provided:
•CWI Client System Prerequisites, page 5
•Router Prerequisites, page 6
•CWI Client Prerequisites, page 6
Notifications 49901 to 49950 Outbound
Telnet/SSH 23/22 Inbound
Table 1 Firewall Ports (continued)
Component Port Direction
P
R
I
M
A
R
Y
S
E
C
O
N
D
A
R
Y
Dual-homed device
Client PC Router
111615

5
Note The managed router must be configured to send notifications to a specified client. These notifications include real-time
inventory updates (for example online insertion and removal [OIR]), alarms, and change of configuration events. See
the “Setting the Minimum Router Configuration” section on page 7 for information on configuring the router to send
notifications to a specified client.
CWI Client System Prerequisites
The CWI client hardware requirements ensure that the CWI client has the proper verified system requirements for the chosen
platform.
The following system requirements for a CWI client are provided in the following hardware platform tables:
•Windows-based PC (See Table 2.)
•UNIX (See Table 3.)
•Linux (See Table 4.)
Table 2 Windows-Based PC Minimum System Requirements
Requirement Type Minimum Requirements
System hardware IBM PC-compatible 500 MHz PentiumIII minimum, 1.20 GHz Pentium IV recommended.
System software Windows NT, Windows 98, Windows 2000, or Windows XP.
Memory (RAM) 256 MB minimum, 512 MB recommended.
Available drive space CWI=5MB, JRE=48MB.
Additional software One of these browsers:
•Microsoft Internet Explorer 5.0 or higher.
•Netscape Navigator 4.77 or higher.
•Netscape Navigator 7.0 or higher.
Java Runtime environment (JRE) version 1.4.2.
Monitor display settings Minimum recommended screen resolution=1024 by 768 pixels.
Table 3 UNIX Minimum System Requirements
Requirement Type Minimum Requirements
System hardware Solaris 550 MHz minimum, 1.2GHz recommended.
Operating System Solaris 7, 8, 9 (each with a full set of required Solaris patches).
Memory (RAM) 256 MB minimum, 512 MB recommended.
Available drive space CWI=5MB, JRE=48MB.
Additional software One of these browsers:
•Netscape Navigator 4.77 or higher.
•Netscape Navigator 7.0 or higher.
JRE version 1.4.2.
Refer to the Sun website for latest minimum system requirements for the JRE on Solaris.
Monitor display settings Minimum recommended screen resolution=1024 by 768 pixels.

6
Router Prerequisites
The router prerequisites ensure that the router is correctly set up.
The following router prerequisites must be met before logging in to a router using the CWI:
•Ensure that the base image and Manageability pie have been installed and booted up on the router that you will be
connecting to using the CWI client. Optionally, install and boot up the Crypto pie to enable SSH and SSL functionality, and
the MPLS pie to enable a Multiprotocol Label Switching (MPLS) configuration. Refer to the Cisco CRS-1 Series Carrier
Routing System Getting Started Guide for information on booting up the base image.
•Ensure that connectivity is established between the router management Ethernet interface and the CWI client. Refer to the
Cisco CRS-1 Series Carrier Routing System Getting Started Guide for information on connecting an Ethernet interface from
the CWI client to the router.
•At least one username and password must be configured on the router. A valid authentication, authorization, and
accounting (AAA) username and password for accessing the router must be configured. Refer to the Cisco CRS-1 Series
Carrier Routing System Getting Started Guide for information on configuring usernames and passwords on the router.
CWI Client Prerequisites
Ensure that the CWI client is correctly set up to communicate with the router. No special configuration is required on the CWI
client.
4 Setting Up the Router and CWI Client
This section provides the procedures that must be completed, in sequence, before you can start using the CWI. The procedures
include setting the minimum router configuration that will allow the router to communicate with the CWI client, configuring
the required Management Services, and configuring the CWI client.
The following two procedures are provided:
•Setting the Minimum Router Configuration, page 7
•Setting Up the Required Management Services, page 7
Refer to the Cisco CRS-1 Series Carrier Routing System Getting Started Guide for information on the capabilities of the router,
installing IOS-XR software packages on the router, and booting up the router.
Table 4 Linux-Based PC Minimum System Requirements
Requirement Type Minimum Requirements
System hardware IBM PC-compatible 500 MHz PentiumIII minimum, 1.20 GHz Pentium IV recommended.
Operating System Red Hat Linux release 7.1 (Seawolf) or any Linux operating system on which Java
Development Kit (JDK) 1.4.2 runs.
Memory (RAM) 256 MB minimum, 512 MB recommended.
Available drive space CWI=5MB, JRE=48MB.
Additional software One of these browsers:
•Netscape Navigator 4.77 or higher.
•Netscape Navigator 7.0 or higher.
JRE version 1.4.2.
Refer to the Sun website for latest minimum system requirements for the JRE on Linux.
Monitor display settings Minimum recommended screen resolution=1024 by 768 pixels.

7
Setting the Minimum Router Configuration
The minimum router configuration must be set before configuring the CWI client and required Management Services.
The “Router Information Requirements” section on page 7 provides a list of information you require to complete the procedures
in this section.
Router Information Requirements
Contact your system administrator to obtain the following information required to configure the router for use with the CWI:
•Router hostname.
•CWI client DNS name.
•CWI client IP address if the client DNS name is not registered in a DNS server accessible by the router.
Note Before starting the procedures in this section, you must determine if the router will be running under Secure Socket
Layer (SSL).
To set the minimum router configuration, perform the following steps:
Step 1 Establish a Telnet/SSH session with the router.
Step 2 Enter configuration mode.
RP/0/RP0/CPU0:router# configure terminal
Step 3 Configure the IP host DNS name to IP address mapping for the CWI client.
Note If you are using a VPN or a dual-homed device in your network, the client IP address and DNS name are not
used when configuring the IP hostname for the CWI client. For a VPN, use the VPN IP address and DNS name.
For a network with a dual-homed device, use the dual-homed device router-side (secondary) IP address and
DNS name. See the “Network Considerations” section on page 3 for information on VPN and dual-homes
devices in a network.
RP/0/RP0/CPU0:router(config)# domain ipv4 host client-DNS-name client-IP-address
Step 4 Configure the hostname for the router.
RP/0/RP0/CPU0:router(config)# hostname router-hostname
Step 5 Exit configuration mode.
RP/0/RP0/CPU0:router(config)# commit
Setting Up the Required Management Services
When setting up the required Management Services, you have the option of communicating between the CWI client and required
Management Services using SSL (secure connection) or no SSL (nonsecure encryption).
The following two sections provide procedures for setting up the required Management Services with or without a secure
connection:
•Setting Up the Required Management Services Without a Secure Connection, page 8
•Setting Up the Required Management Services with a Secure Connection, page 8
The “Setting Up the CWI Client” section on page 10 provides information on setting up the CWI client after the required
Management Services are set up. The “Troubleshooting CWI Client Connectivity” section on page 10 provides information on
resolving connectivity problems.

8
Setting Up the Required Management Services Without a Secure Connection
This section provides the procedures required to set up the required Management Services without SSL.
Note The Telnet server must be enabled before you can manage a router using certain CWI features. These features include
the Telnet application, setting character displays in the Rack View application, and viewing committed configuration
changes using the Configuration Change dialog box. Refer to Chapter 4, “Bring Up a New Cisco CRS-1 Series Router,”
in the Cisco CRS-1 Series Carrier Routing System Getting Started Guide for information on enabling the Telnet server.
Note If you are connecting through a firewall in your network, the ports listed in Table 1 must be open before setting up the
required Management Services. Refer to your firewall documentation for information on opening the ports. See the
“Network Considerations” section on page 3 for information on firewalls in a network.
To start the required Management Services on the router, perform the following steps:
Step 1 Establish a Telnet/SSH session with the router.
Step 2 Enter configuration mode.
RP/0/RP0/CPU0:router# configure terminal
Step 3 Enable the HTTP server on the router.
RP/0/RP0/CPU0:router(config)# http server
Step 4 Enable the XML agent on the router.
RP/0/RP0/CPU0:router(config)# xml agent corba
Step 5 Exit configuration mode.
RP/0/RP0/CPU0:router(config)# commit
Setting Up the Required Management Services with a Secure Connection
This section provides the procedures required to set up the Management Services with SSL encryption. When setting up the
required Management Services and the CWI client with a secure connection, the certification authority (CA) and router
certificates must be set up before enabling the HTTP server and CORBA agent.
The following procedures are provided:
•Setting Up the Certificates, page 9
•Enabling the Secure HTTP Server and CORBA Agent, page 10
Note The SSH server must be enabled before you can manage a router using certain CWI features. These features include the
SSH application, setting character displays in the Rack View application, and viewing committed configuration changes
using the Configuration Change dialog box. Refer to Chapter 4, “Bring Up a New Cisco CRS-1 Series Router,” in the
Cisco CRS-1 Series Carrier Routing System Getting Started Guide for information on enabling the SSH server.
Note If you are connecting through a firewall in your network, the ports listed in Table 1 must be open before setting up the
required Management Services. Refer to your firewall documentation for information on opening the ports. See the
“Network Considerations” section on page 3 for information on firewalls in a network.

9
Note You must have the Crypto pie installed before attempting to complete the steps in this section. See the “Router
Prerequisites” section on page 6.
Setting Up the Certificates
Note The CA and router certificates have to be set up only once on a router. If the certificates have been set up, proceed to
the “Enabling the Secure HTTP Server and CORBA Agent” section on page 10.
To set up the certificates, perform the following steps:
Step 1 Establish a Telnet/SSH session with the router.
Step 2 Generate a Rivest, Shamir, and Adelman (RSA) key pair. Accept all prompted defaults.
RP/0/RP0/CPU0:router# crypto key generate rsa keypair-label
Note If the key pair label is not specified, “the_default” will be used.
Example:
RP/0/RP0/CPU0:router# crypto key generate rsa key1
Step 3 Enter configuration mode.
RP/0/RP0/CPU0:router# configure terminal
Step 4 Configure the CA trustpoint.
RP/0/RP0/CPU0:router(config)# crypto ca trustpoint ca-name
RP/0/RP0/CPU0:router(config-trustp)# enrollment url ca-URL
RP/0/RP0/CPU0:router(config-trustp)# rsakeypair keypair-label (This command must be completed if a
keypair label is specified in Step 2.)
RP/0/RP0/CPU0:router(config-trustp)# exit
RP/0/RP0/CPU0:router(config)# commit
Example:
RP/0/RP0/CPU0:router(config)# crypto ca trustpoint myca
RP/0/RP0/CPU0:router(config-trustp)# enrollment url http://myca/mydomain.com
RP/0/RP0/CPU0:router(config-trustp)# rsakeypair keypair-label
RP/0/RP0/CPU0:router(config-trustp)# exit
RP/0/RP0/CPU0:router(config)# commit
Step 5 Exit configuration mode.
RP/0/RP0/CPU0:router(config)# commit
Step 6 Authenticate the CA by getting the certificate for the CA.
RP/0/RP0/CPU0:router# crypto ca authentication ca-name
Step 7 Obtain a router certificate from the CA.
RP/0/RP0/CPU0:router# crypto ca enroll ca-name
Step 8 Verify that the router was granted a certificate. This command displays information about the router certificate and the
CA certificate.
RP/0/RP0/CPU0:router# show crypto ca certificate

10
Enabling the Secure HTTP Server and CORBA Agent
To enable the secure HTTP server and CORBA agent, perform the following steps:
Step 1 Establish a Telnet/SSH session with the router.
Step 2 Enter configuration mode.
RP/0/RP0/CPU0:router# configure terminal
Step 3 Enable the HTTPS server on the router.
RP/0/RP0/CPU0:router(config)# http server ssl
Step 4 Enable the XML agent with SSL.
RP/0/RP0/CPU0:router(config)# xml agent corba ssl
Step 5 Exit configuration mode.
RP/0/RP0/CPU0:router(config)# commit
Setting Up the CWI Client
Verify that you can connect to the router by logging in to the router. See the “Starting the CWI” section on page 11 for
procedures. If you are unable to log in to the router, see the “Troubleshooting CWI Client Connectivity” section on page 10.
Troubleshooting CWI Client Connectivity
This section provides information on troubleshooting connectivity problems when attempting to log in to a router using the
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/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 or IP address of the router.
If this step fails, the problem is an incorrect hostname to IP address mapping. See Step 3 in the “Setting the Minimum
Router Configuration” section on page 7.
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 Step 3 in the “Setting Up the Required Management Services Without a
Secure Connection” section on page 8 or Step 3 in the “Setting Up the Required Management Services with a Secure
Connection” section on page 8.
If you are unable to log into the router from the CWI login screen run the Troubleshooter application at the prompt. Refer to
the Cisco CRS-1 Series Carrier Routing System Craft Works Interface User Interface Guide for information on using the
Troubleshooter application.

11
5 Getting Started with the CWI
This section describes the procedures for establishing a connection between the CWI and a router. The procedures are described
in the following sections:
•CWI Login Information Requirements, page 11
•Starting the CWI, page 11
•Logging In to Multiple Logical Routers, page 16
•Logging Out of a Logical Router, page 17
•Closing the CWI, page 18
When starting the CWI and logging in to a router, you always log in to a single router. After you have logged in to a single router,
you can log in to and manage multiple routers, but you must log in to each one separately. Each router appears in the CWI
Desktop Inventory Tree. See the “Inventory Tree” section on page 20.
CWI Login Information Requirements
Contact your system administrator to obtain the following information required to complete the procedures in this section:
•The hostnames (DNS names) or IP addresses of any routers you want to log in to.
•Valid username and password for each router you want to log in to using the CWI. The username and password for each
router is your AAA username and password for that router. Therefore, each router may have a different username and
password.
Note The Telnet/SSH server must be enabled before you can manage a router using certain CWI features. These features
include the Telnet/SSH application, the Troubleshooter application, setting character displays in the Rack View
application, and viewing committed configuration changes using the Configuration Change dialog box. Refer to
Chapter 4, “Bring Up a New Cisco CRS-1 Series Router”, in the Cisco CRS-1 Series Carrier Routing System Getting
Started Guide for information on enabling the Telnet/SSH server.
Note The managed router must be configured to send notifications to a specified client. These notifications include real-time
inventory updates (for example online insertion and removal [OIR]), alarms, and change of configuration events. See
the “Setting the Minimum Router Configuration” section on page 7 for information on configuring the router to send
notifications to a specified client.
Starting the CWI
The following two sections provide procedures for starting the CWI and logging in to a router:
•Starting the CWI When SSL Is not Enabled, page 11
•Starting the CWI When SSL Is Enabled, page 13
Starting the CWI When SSL Is not Enabled
Use this procedure to start the CWI and log in to a router when SSL is not enabled on the required Management Services. See
the “Setting Up the Required Management Services Without a Secure Connection” section on page 8.
To start the CWI when SSL is not enabled, perform the following steps.
Step 1 Start a supported web browser. See the “CWI Client System Prerequisites” section on page 5 for information on web
browsers.
The web browser window appears.

12
Step 2 In the Address field located near the top of the web browser window, enter the DNS name or IP address of the router
to be accessed.
You must enter the DNS name or IP address in Address field using the following format:
http://router-dns-name or http://ip-address
Step 3 Press Enter.
Step 4 A router HTTP authentication dialog box appears.
You require your AAA username and password. See the “Router Prerequisites” section on page 6 for information on
the AAA username and password.
a. Type your AAA username and password in the User Name and Password fields.
b. Click Yes.
The Cisco Systems router homepage appears.
Step 5 Click the Craft Works Interface link in the web browser.
Step 6 A router HTTP authentication dialog box appears.
Your AAA username and password must be provided for the Craft Works Interface Launcher to start. See the “Router
Prerequisites” section on page 6 for information on the AAA username and password.
a. Type your AAA username and password in the User Name and Password fields.
b. Click Yes.
Step 7 If this is the first time the CWI client has started the CWI, the Java Plug-in must be installed and the CWI Cisco security
certificate must be accepted.
a. If the Java Plug-in installation is completed, a dialog box appears asking you to trust the security certificate distributed
by Cisco Systems, Inc. This dialog box will differ depending on the client platform.
b. The security certificate must be accepted to run CWI. You have the following options:
– Click Yes to trust and accept the security certificate for this router session only. If this option is chosen, the
certificate is accepted and the login process continues. Proceed to Step 9. If you choose Yes, the security
certificate must be accepted next time you log in to the router.
– Click No to deny the security certificate. If this option is chosen, the login process is canceled.
– Click Always to automatically trust and accept the security certificate in this section and all subsequent CWI
sessions. If this option is chosen, the certificate is accepted and the login process continues. Proceed to Step 8.
If you choose Always, the security certificate does not have to be accepted again when logging in to a router
from the CWI client.
– Click More Details to view the security certificate. A dialog box appears with detailed certificate information.
The certificate information includes the version, serial number, insurer, and start and end date validity of the
certificate.
The Craft Works Interface Launcher appears.
Step 8 If this is the first time you have started the CWI or if you have installed a new version of the CWI, the CWI components
will start downloading. Otherwise, a cached version of the CWI components are used, reducing the CWI start time.
After the CWI component download is complete, the Start CWI, Delete Cache, and About buttons become available.
Step 9 Log in to the router when the CWI - Login dialog box appears. (See Figure 2.)
Note A valid AAA username and password for accessing the router must be configured. See the “Router
Prerequisites” section on page 6.
a. Enter a username in the User Name field. See the “CWI Login Information Requirements” section on page 11 for
information on obtaining your username.
b. Enter a password in the Password field. See the “CWI Login Information Requirements” section on page 11 for
information on obtaining your password.
c. (Optional) In the Node Name list, click the drop-down arrow and choose a node name (DNS name or IP address of the
router).

13
d. Click Login.
Figure 2 CWI - Login Dialog Box
Step 10 Observe the dynamic display that shows each initialization step and indicates whether each step is successful.
After the CWI initialization is complete, the CWI Desktop window appears. See the “CWI Overview” section on
page 18 for information on the CWI Desktop window.
Note The CWI is automatically locked when there is no activity in the CWI session for 15 minutes. To unlock the
CWI you must provide the username and password used when logging in to the router. Refer to the
Cisco CRS-1 Series Carrier Routing System Craft Works Interface User Interface Guide for CWI unlocking
procedures.
If any of the minimum requirements of the initialization steps fail, a CWI dialog box appears allowing you to Abort,
Troubleshoot, or Continue the initialization process. Proceed to Step 11.
Step 11 Complete the following steps to troubleshoot the initialization process.
a. To stop the initialization process, click Abort.
b. To troubleshoot the process, click Troubleshoot. The Troubleshooter application is started, and a Troubleshoot New LR
Launch problems dialog box appears. The Troubleshooter application allows you to run fault isolation tests on the
client/server communication path between the CWI and the router management agent. The Troubleshooter application
provides a window that describes the reason for the failure, possible cause, and recommended repair action. An
automatic repair option is provided in many instances. Refer to the Cisco CRS-1 Series Carrier Routing System Craft
Works Interface User Interface Guide for information on using the Troubleshooter feature.
c. To continue the initialization, process click Continue.
Starting the CWI When SSL Is Enabled
Use this procedure to start the CWI and log in to a router when SSL is enabled on the required Management Services. See the
“Setting Up the Required Management Services with a Secure Connection” section on page 8 for information on enabling SSL.
Note All steps associated with accepting a certificate are not required after the first time you have started the CWI client and
logged in to a router if you choose the certificate option Always. See the “Starting the CWI When SSL Is not Enabled”
section on page 11 for procedures to start the CWI and log in to a router for a subsequent log in.
To start the CWI when SSL is enabled, perform the following steps.
Step 1 Start a supported web browser. See the “CWI Client System Prerequisites” section on page 5 for information on web
browsers.
The web browser window appears.
Step 2 In the Address field located near the top of the web browser window, enter the DNS name or IP address of the router
to be accessed.

14
You must enter the DNS name or IP address in Address field using the following format:
https://router-dns-name or https://ip-address
Step 3 Press Enter.
Step 4 The router SSL certificate must be accepted. You have the following options:
•Click Yes to trust and accept the SSL certificate for this router session only. If this option is chosen, the certificate
is accepted and the login process continues. Proceed to Step 5. If you choose Yes, the SSL certificate must be accepted
next time you log in to the router.
•Click No to deny the SSL certificate. If this option is chosen, the login process is canceled.
•Click Always to automatically trust and accept the SSL certificate in this session and all subsequent CWI sessions.
If this option is chosen, the certificate is accepted and the login process continues. Proceed to Step 5. If you choose
Always, the SSL certificate does not have to be accepted again when logging in to a router from the CWI client.
•Click More Details to view the SSL certificate. A dialog box appears with detailed certificate information. The
certificate information includes the version, serial number, insurer, and start and end date validity of the certificate.
Step 5 A router HTTP authentication dialog box appears.
You require your AAA username and password. See the “Router Prerequisites” section on page 6 for information on
the AAA username and password.
a. Type your AAA username and password in the User Name and Password fields.
b. Click Yes.
The Cisco Systems router homepage appears.
Step 6 Click the Craft Works Interface link in the web browser.
Step 7 A router HTTP authentication dialog box appears.
Your AAA username and password must be provided for the Craft Works Interface Launcher to start. See the “Router
Prerequisites” section on page 6 for information on the AAA username and password.
a. Type your AAA username and password in the User Name and Password fields.
b. Click Yes.
Step 8 If this is the first time the CWI client has started the CWI, the Java Plug-in must be installed and the CWI Cisco security
certificate must be accepted.
a. If the Java Plug-in installation is completed, a dialog box appears asking you to trust the security certificate distributed
by Cisco Systems, Inc.
b. The security certificate must be accepted to run CWI. You have the following options:
– Click Yes to trust and accept the security certificate for this router session only. If this option is chosen, the
certificate is accepted and the login process continues. Proceed to Step 9. If you choose Yes, the security
certificate must be accepted next time you log in to the router.
– Click No to deny the security certificate. If this option is chosen, the login process is canceled.
– Click Always to automatically trust and accept the security certificate in this section and all subsequent CWI
sessions. If this option is chosen, the certificate is accepted and the login process continues. Proceed to Step 9.
If you choose Always, the security certificate does not have to be accepted again when logging in to a router
from the CWI client.
– Click More Details to view the security certificate. A dialog box appears with detailed certificate information.
The certificate information includes the version, serial number, insurer, and start and end date validity of the
certificate.
Step 9 The router SSL certificate must be accepted. You have the following options:
•Click Yes to trust and accept the SSL certificate for this router session only. If this option is chosen, the certificate
is accepted and the login process continues. Proceed to Step 10. If you choose Yes, the SSL certificate must be
accepted next time you log in to the router.
•Click No to deny the SSL certificate. If this option is chosen, the login process is canceled.

15
•Click Always to automatically trust and accept the SSL certificate in this session and all subsequent CWI sessions.
If this option is chosen, the certificate is accepted and the login process continues. Proceed to Step 10. If you choose
Always, the SSL certificate does not have to be accepted again when logging in to a router from the CWI client.
•Click More Details to view the SSL certificate. A dialog box appears with detailed certificate information. The
certificate information includes the version, serial number, insurer, and start and end date validity of the certificate.
The Craft Works Interface Launcher appears.
Step 10 If this is the first time you have started the CWI or if you have installed a new version of the CWI, the CWI components
will start downloading. Otherwise, a cached version of the CWI components are used, reducing the CWI start time.
After the CWI component download is complete, the Start CWI, Delete Cache, and About buttons become available.
Step 11 Log in to the router when the CWI - Login dialog box appears. (See Figure 3.)
Note A valid AAA username and password for accessing the router must be configured. See the “Router
Prerequisites” section on page 6.
a. Enter a username in the User Name field. See the “CWI Login Information Requirements” section on page 11 for
information on obtaining your username.
b. Enter a password in the Password field. See the “CWI Login Information Requirements” section on page 11 for
information on obtaining your password.
c. (Optional) In the Node Name list, click the drop-down arrow and choose a node name (DNS name or IP address of the
router).
d. Click Login.
Figure 3 CWI - Login Dialog Box
Step 12 If you did not choose Always in Step 9, you must accept the SSL certificate. You have the following options:
•Click Yes to trust and accept the SSL certificate for this router session only. If this option is chosen, the certificate
is accepted and the login process continues. Proceed to Step 13. If you choose Yes, the SSL certificate must be
accepted next time you log in to the router.
•Click No to deny the SSL certificate. If this option is chosen, the login process is canceled.
•Click Always to automatically trust and accept the SSL certificate in this session and all subsequent CWI sessions.
If this option is chosen, the certificate is accepted and the login process continues. Proceed to Step 13. If you choose
Always, the SSL certificate does not have to be accepted again when logging in to a router from the CWI client.
•Click More Details to view the SSL certificate. A dialog box appears with detailed certificate information. The
certificate information includes the version, serial number, insurer, and start and end date validity of the certificate.
The Initializing CWI dialog box appears.
Step 13 Observe the dynamic display that shows each initialization step and indicates whether each step is successful.
Once the CWI initialization is complete, the CWI Desktop window appears. See the “CWI Overview” section on
page 18 for information on the CWI Desktop window.

16
Note The CWI is automatically locked when there is no activity in the CWI session for 15 minutes. To unlock the
CWI you must provide the username and password used when logging in to the router. Refer to the
Cisco CRS-1 Series Carrier Routing System Craft Works Interface User Interface Guide for CWI unlocking
procedures.
If any of the minimum requirements of the initialization steps fail, a CWI dialog box appears allowing you to Abort,
Troubleshoot, or Continue the initialization process. Proceed to Step 14.
Step 14 Complete the following steps to troubleshoot the initialization process.
a. To stop the initialization process, click Abort.
b. To troubleshoot the process, click Troubleshoot. The Troubleshooter application is started, and a Troubleshoot New LR
Launch problems dialog box appears. The Troubleshooter application allows you to run fault isolation tests on the
client/server communication path between the CWI and the router management agent. The Troubleshooter application
provides a window that describes the reason for the failure, possible cause, and recommended repair action. An
automatic repair option is provided in many instances. Refer to the Cisco CRS-1 Series Carrier Routing System
Craft Works Interface User Interface Guide for information on using the Troubleshooter feature.
c. To continue the initialization process, click Continue.
Logging In to Multiple Logical Routers
The CWI can manage multiple routers. You can log in to multiple routers when the CWI Desktop is open and currently logged
in to at least one router.
To log in to a router from the CWI Desktop, perform the following steps:
Step 1 From the File menu, choose Login.
The CWI - Login dialog box appears. (See Figure 4.)
Figure 4 CWI - Login Dialog Box
Step 2 In the User Name field, enter a valid username. See the “CWI Login Information Requirements” section on page 11 for
information on obtaining your username.
Step 3 In the Password field, enter a valid password. See the “CWI Login Information Requirements” section on page 11 for
information on obtaining your password.
Note A valid AAA username and password for accessing the router must be configured. See the “Router
Prerequisites” section on page 6.
Step 4 In the Node Name field, enter a valid node name (DNS name or IP address of the router) or click the drop-down arrow
and choose a valid node name.
Step 5 Click Login.

17
Step 6 If this is the first time the router has started from the CWI client and the required Management Services are running
SSL, a certificate dialog box appears. The Cisco security certificate must be accepted to log in to the router. You have
the following options:
a. Click Yes to trust and accept the security certificate for this router session only. If this option is chosen, the certificate is
accepted and the login process continues. If you choose Yes, the security certificate must be accepted next time you
log in to the router.
b. Click No to deny the security certificate. If this option is chosen, the login process is canceled.
c. Click Always to automatically trust and accept the security certificate in this section and all subsequent sessions with
this specific router from the CWI client. If this option is chosen, the certificate is accepted and the login process
continues. If you choose Always, the security certificate does not have to be accepted again when logging in to a
router from the CWI client.
d. Click More Details to view the security certificate. A dialog box appears with detailed certificate information. The
certificate information includes the version, serial number, insurer, and start and end date validity of the certificate.
The Initializing CWI dialog box appears.
After the router initialization is successfully completed, a new router appears in the Inventory Tree in the CWI Desktop.
See the “Inventory Tree” section on page 20 for information on the Inventory Tree.
Logging Out of a Logical Router
You can log out of a router when there is more than one router open in the CWI Desktop.
To log out of a router, perform the following steps:
Step 1 Choose a router in the Inventory Tree.
Step 2 From the File menu, choose Logout.
A Logout dialog box appears. (See Figure 5.)
Figure 5 Logout Dialog Box
Step 3 From the NE Name list, choose a router.
Step 4 Click OK.
A second Logout dialog box appears to confirm that you want to log out of the router. (See Figure 6.)
Figure 6 Logout Dialog Box
Step 5 Click Yes.
All applications opened from the selected router are closed, the session with the router is ended, and the router
disappears from the Inventory Tree. See the “Inventory Tree” section on page 20 for information on the Inventory Tree.

18
Closing the CWI
To close the CWI, perform the following steps:
Step 1 From the File menu, choose Exit or click Close on the CWI Desktop title bar.
A Craft Works Interface dialog box appears.
Step 2 Click Yes to exit the application.
The CWI Desktop window closes. The Configuration Desktop is also closed (if it was open when the close command
was executed).
6 CWI Overview
The CWI is an application used to manage Cisco routers. CWI provides the following features:
•A user-friendly context-sensitive interface that is used for fault, configuration, inventory, and security management of a
router.
•A combination of both graphical and text-based interfaces that allow the user to select the best interface for the task at hand.
•A powerful CWI feature set used to simplify managing the router scale and complexity.
•Access to the powerful manageability features of the router.
The CWI provides three ways to configure and manage a router:
•Using a Telnet/SSH session launched from the CWI, which allows you to configure and manage the router using CLI
commands.
•Using the Configuration Editor or Replace Configuration Editor, which allows you to view and edit the running
configuration in CLI format. These editors provide common text editing functionality as well as traditional CLI features
such as help and command-completion. See the “Configuration Editor” section on page 22 and the “Replace Configuration
Editor” section on page 22.
•Using the graphical configuration applications. See the “Configuration Desktop Window” section on page 20.
7 CWI Desktop Window
The CWI Desktop is the main point of access to all CWI applications and tools, allowing you to configure, monitor, and manage
routers. (See Figure 7.)
Common Elements in the CWI Desktop
The CWI Desktop is designed with common elements that provide an easy to use and consistent user interface.
The following features are common among the CWI applications:
•Printing, exporting, and searching data.
•Sorting and moving columns.
•Filtering records.
•Setting preferences.
•Cascading applications.
•Minimizing and maximizing applications.
•Maximizing applications.
•Choosing applications in the Application pane.
Refer to the Cisco CRS-1 Series Carrier Routing System Craft Works Interface User Interface Guide for details on common
elements and procedures for common activities in the CWI Desktop.

19
Figure 7 CWI Desktop
The CWI Desktop allows you to communicate with the router using the following applications:
•Alarm Viewer—Provides an interface between the CWI and the alarm management functions of the router controller,
allowing you to dynamically view alarm records with powerful filtering capabilities. The Alarm Viewer also provides a
launch point to view correlated alarms.
•Inventory Viewer—Displays the attribute values of selected objects.
•Rack View—Displays a graphical representation of the physical equipment including racks, cards, slots, power supplies,
and fan trays. The router can be viewed from the front or the back. The Rack View displays active alarms on the associated
object and provides context-sensitive launch points for other CWI applications in the same way as the Inventory Tree. The
card character displays are user configurable and are displayed on the card faceplate.
•Interface Quick Viewer—Provides a view of interface attributes for selected cards.
•Configuration Desktop—Provides an interface tailored to managing configuration applications.
•Telnet/SSH—Provides the capability to issue CLI commands and view session information within the CWI. Telnet/SSH
includes additional CWI features for creating command lists and executing commands from the command list, saving and
loading command lists from a file, and running in batch mode. Additionally, console text can be displayed in a separate
window. The SSH application allows you to connect to the router with a secure connection.
•Troubleshooter—Provides fault isolation and repair of connectivity problems between the CWI and router.

20
Menu Bar
The CWI Desktop menu bar provides a list of options available on the basis of the selected object and active application. The
options include administrative, editing, and viewing tasks, starting applications, and arranging windows.
Toolbar
The CWI Desktop toolbar contains icons, referred to as tools, that provide direct access to context-sensitive functions. Clicking
a tool selects a task.
Inventory Tree
The Inventory Tree displays all components of each router that the CWI can access and is the primary interface to these
components. The Inventory Tree dynamically shows current alarms and events, connectivity status, and physical and logical tree
views. The Inventory Tree provides context-sensitive launching of applications by selecting an object, a group of objects, or an
entire router in the Inventory Tree and then choosing an available application.
CWI Status Bar
The CWI status bar contains three icons that show the status of the CWI including communication security and NE connectivity
and allows you to open the Alarm Dashboard. The left side of the status bar may contain a progress message.
Dashboard
The Dashboard provides a summary of the alarm status information for all routers in the CWI Desktop. Color coding is used
to indicate active alarm counts by severity. A resettable running count of new alarm arrivals is provided.
CWI Application Pane
The CWI Application pane is the area of the CWI Desktop that contains the active CWI applications used to manage the router.
Multiple applications can be open concurrently in the CWI Application pane.
8 Configuration Desktop Window
The Configuration Desktop is the main point of access to all configuration applications. (See Figure 8.) These applications allow
you to configure and manage routers within your network.
The Configuration Desktop is opened for one router chosen in the CWI Desktop. If there are multiple routers in the
CWI Desktop, you can open one Configuration Desktop for each router.
There are four ways to configure a router using the CWI:
•Telnet/SSH application from the CWI Desktop.
•Configuration Editor from the Configuration Desktop.
•Replace Configuration Editor from the Configuration Desktop.
•Graphical user interface (GUI) applications from the Configuration Desktop.
The Configuration Applications Tree uses icons for each configuration application to dynamically display the state of each
application. The icon states include the unchanged, not permitted, incompatible version, uncommitted, and disabled.
The Configuration Desktop allows you to view the configuration changes made using the configuration applications or the
Configuration Editor using the Show Uncommitted Config tool. The tool is launched by right-clicking the Configuration
Applications icon in the Configuration Applications Tree. The uncommitted configuration (also known as the target
configuration) is displayed in a window in CLI format.