Cisco Transport Manager User's Guide, 7.2 - Appendix J: Using CiscoView to Configure and Monitor ONS 15501, ONS 15530, and ONS 15540 NEs [Cisco Transport Manager]

Table Of Contents

Using CiscoView to Configure and Monitor ONS 15501, ONS 15530, and ONS 15540 NEs

J.1  Starting CiscoView

J.2  Displaying and Using Context Menus

J.3  Understanding the Color Coding Scheme

J.4  Understanding the Status Bar and Buttons

J.5  Using the Main Menu Buttons

J.6  Frequently Asked Questions

J.7  Troubleshooting

J.7.1  Testing the Basic Connectivity of CiscoView

J.7.2  Common CiscoView Problems

Using CiscoView to Configure and Monitor ONS 15501, ONS 15530, and ONS 15540 NEs

This appendix describes CiscoView, the device management tool for configuring and monitoring ONS 15501, ONS 15530, and ONS 15540 NEs.

This appendix contains the following sections:

•Starting CiscoView

•Displaying and Using Context Menus

•Understanding the Color Coding Scheme

•Understanding the Status Bar and Buttons

•Using the Main Menu Buttons

•Frequently Asked Questions

•Troubleshooting

J.1  Starting CiscoView

Note Before attempting to launch server-based CiscoView, make sure that CiscoView is installed and that the server and clients are properly configured. For more information, see the Cisco Transport Manager Release 7.2 Installation Guide.

Step 1 Log into the CTM client with the appropriate user profile. See the Cisco Transport Manager Release 7.2 Installation Guide for instructions on how to log into the CTM client.

Step 2 Launch CiscoView from the Domain Explorer, Network Map, or Subnetwork Explorer.

a. Use one of the following options:

•Double-click the NE

•Select the NE and choose Configuration > ONS 155XX > Launch CiscoView

•Right-click the NE and choose Launch CiscoView

One of the following occurs:

•Server-based CiscoView is launched in the CTM default browser. Login to CiscoWorks is required, using the following username and password:

–Username: admin

–Password: admin

Then, you must specify SNMP community strings for the selected NE.

•If server-based CiscoView is not available, CTM launches embedded CiscoView for the ONS 15530 and ONS 15540. Go to step b.

•For the ONS 15501, embedded CiscoView is not available and an error message is displayed.

b. After the CiscoView splash screen appears, log in using the NE enable password and click OK in the community string dialog boxes.

If neither server-based nor embedded CiscoView is available, an error message is displayed.

The CiscoView window (Figure J-1) contains the following elements:

•Graphical representation of the chassis—This display shows all configurable components, color-coded according to their current status. The display is refreshed according to the polling frequency. Right-click the device or a component to display the context menus. See Displaying and Using Context Menus and Understanding the Color Coding Scheme.

•Select Device list—Allows you to select and display a device. Enter a device name or IP address, or select from a list of recently displayed devices.

•Status bar and buttons. See Understanding the Color Coding Scheme.

•Main menu buttons. See Using the Main Menu Buttons.

Figure J-1 Sample CiscoView Window

J.2  Displaying and Using Context Menus

Step 1 Use one of the following methods to select the entire device or a component:

Note To select the entire device, point to an area that does not contain a component before clicking.

•Double-click the device or a component to display the default menu option (usually Configure).

•Right-click the device or a component to display a popup context menu that contains options specific to the selection. The default menu option (usually Configure) appears in bold type. See the following sections for information about using the context menu, dialog boxes, and command buttons and understanding the status bar and color legends.

Step 2 If you select the device, the context menu contains the following options:

•Configure—Opens the Configure menu.

•Monitor—Displays dynamic charts.

•Copy Config Files—Copies the running or startup configuration file.

•Front—Displays the front of the chassis.

•Rear—Displays the back of the chassis.

•Resize—Resizes the graphical display. The display can be reduced to 50%.

•Refresh—Triggers component polling and updates the display.

•System Info—Displays the general system MIB information (device name, description, location, contact information, and up time).

Note If you select a component, the context menu displayed depends on the type of component selected.

Step 3 After you select an option from a context menu, either a drop-down list box or a dialog box appears. After you select a category from a drop-down list box, a dialog box appears. Dialog boxes contain some or all of the following buttons:

•Apply—Applies changes. The dialog box remains open. Select more categories to view or configure.

•OK—Applies changes and closes the dialog box.

•Print—Prints the current category.

•Cancel—Cancels changes and closes the dialog box.

•Refresh—Refreshes the dialog box.

•Help—Launches dialog box-specific help.

•Create—Launches a dialog box for creating a table row.

•Delete—Deletes the selected table row.

•Start/Stop—Starts or stops the monitoring of device information.

J.3  Understanding the Color Coding Scheme

The color of the border surrounding a component indicates the operational status of the component. When the status changes, the border surrounding the component changes as indicated in the following table.

Table J-1 CiscoView Color Legend

Color

Meaning

Description

Cyan (blue-green)

Interface is dormant.

The interface cannot pass packets, but is in a pending state waiting for some external event to place it in the up state. The interface might have packets to transmit before establishing a connection to a remote system, or a remote system might be establishing a connection to the interface.

When the pending event occurs, the interface changes to the up state.

Orange

Component is down.

The administrative status is up and the operational value is down.

Red

Component failed.

Physical hardware failure.

Yellow

Minor failure.

The component is down; both administrative and operational values are down. This does not necessarily indicate a fault condition; the component might be disabled.

Purple

Component is being tested.

The administrative status is Up, but tests need to be performed. After the tests are completed, the component status changes to Up, Dormant, or Down as appropriate.

Green

Component is active.

The component is operating normally.

J.4  Understanding the Status Bar and Buttons

The status bar at the bottom of the display shows the progress of device polling, refreshes, and other operations. If a command fails, the status bar displays an error message. Error messages are explained in Troubleshooting.

The three command buttons next to the status bar have the following functions:

•The System Info button displays system information (device name, description, location, contact, and up time).

•The Print button prints the current display.

•The Color Legend button displays the color-coding scheme. (See Understanding the Color Coding Scheme.)

J.5  Using the Main Menu Buttons

The following table describes the functions of the menu buttons on the left side of the CiscoView window.

Table J-2 CiscoView Main Menu Buttons

Button Name

Function

Telnet

Launches a Telnet command-line session on the device.

CCO

Launches the Cisco.com web page in a separate window.

Cisco Support

Opens the TAC mailer dialog box for sending reports to the Cisco Technical Assistance Center (TAC).

Preferences

Opens the Preferences dialog box. The preferences settings are preserved for all new CiscoView sessions.

If community strings for an NE are not already defined within CiscoView, you can add them with the CiscoView Community Strings tab. Otherwise, you can enter the community strings when accessing the device. If you do not enter community strings when accessing the NE, CiscoView uses the default read and write community strings as defined in the SNMP tab.

You can use the SNMP tab to set polling frequency, SNMP timeout and retries, and default read and write community strings.

About

Displays the CiscoView release version and copyrights, the active device package (if applicable), and all installed device package information.

Help

Opens CiscoView help if no device is selected. Opens context-sensitive help if a device or component is selected.

J.6  Frequently Asked Questions

The following are frequently asked questions (FAQs) about CiscoView.

Q. How do I know which version of CiscoView is required to support my devices?

A. Refer to the Cisco IOS readme file, which lists all of the supported new devices. Refer to the following URL to find out which version of CiscoView is appropriate to support those new devices:

http://www.cisco.com/public/sw-center/netmgmt/ciscoview/cvcww-download.shtml

Q. How do I set the default community strings in CiscoView?

A. Click Preferences from the CiscoView Main menu and click the Community tab. Modify the community strings as necessary.

Q. How do I know which device packages to download for my version of the devices?

A. Refer to the Cisco IOS readme file for a list of the latest device packages, or go to the following URL to find out which device packages to download:

http://www.cisco.com/public/sw-center/netmgmt/ciscoview/cvcww-download.shtml

Q. How do I add device support to CiscoView?

A. CiscoView device support can be updated by downloading device-specific files from Cisco.com. To do this, go to the following URL:

http://www.cisco.com/pcgi-bin/Software/CiscoView/cvplanner.cgi

For detailed information about downloading and installing new device packages, refer to the "Installing and Setting Up CiscoView" chapter in the Cisco Transport Manager Release 7.2 Installation Guide.

Q. How do I find out which version of the Java Plug-in I am currently using?

A. Bring up the Java Plug-in control panel:

–On a Windows client, click the Java Plug-in icon in the Windows Control Panel.

–On a Solaris client, enter the /usr/j2se/jre/bin/ControlPanel command.

Then, click the About tab.

J.7  Troubleshooting

When troubleshooting CiscoView, first test basic connectivity. See Testing the Basic Connectivity of CiscoView. Then, proceed to the troubleshooting tips in Common CiscoView Problems.

J.7.1  Testing the Basic Connectivity of CiscoView

Step 1 Test the IP connectivity:

a. Try to ping the IP address of the NE by using the ping <IP_address> command. If the ping is unsuccessful, make sure that IP routing is properly enabled and is functioning normally.

b. Ping the NE by its name as well as by its IP address.

c. If you can ping the NE by its IP address but not its resolved name, there is a name resolution problem. Consult your system administrator for assistance in resolving this problem.

Step 2 Open a Telnet session to the NE and enter the show running-config privileged EXEC command to view the NE configuration. Verify that there is an snmp-server community string rw command entry in the configuration.

•If the command is not present, configure the router with the snmp-server community command.

•If the command is present, make sure that the rw (read-write) keyword is specified, not the ro (read only) keyword.

J.7.2  Common CiscoView Problems

The following table provides possible solutions for common problems you might experience.
Table J-3 Troubleshooting CiscoView
Symptom

Probable Cause(s)

Possible Solution(s)

Received CiscoView timeout error messages.

There is a problem with the basic connectivity or setup.

Perform the steps in Testing the Basic Connectivity of CiscoView, and verify that the NE is running.

The polling interval is too low.

Verify that SNMP is active. If SNMP is inactive, activate it by using the device command-line interface (CLI).

There might be a problem with the community string, name resolution, or timeout value.

Increase the timeout if the device is remote, and reduce timeout errors if the problem is on the network.

Unable to modify or configure devices.

•The write community string might be invalid.

•The Modify button is disabled.

Click Preferences to modify the write community string. The write community string set in CiscoView should match what is set on the NE for any modification or configuration to work.

A card is missing for a particular device.

The latest device package might not be installed.

Upgrade the device package from the following URL:

http://www.cisco.com/public/sw-center/netmgmt/ciscoview/cvcww-download.shtml

Web server is down and unable to connect.

The package installer might be shutting down the server to install a device package. This could last for 2 minutes.

1. Try to reconnect in a few minutes. If it still fails, go to the server machine and run pdshow Web Server from the CSCOpx/bin directory to verify if the web server is running.

On Solaris: opt/cscopx/bin

On Windows: programfiles/pdshow

2. If it still fails, run pdexec JRunProxyServer to try to start the web server.

No device package exists for a device after using the Package Support Updater to download it.

During the installation, the web server stopped.

Reinstall the device package and start the web server.

Select Abort from the CiscoView main menu to manually stop the installation process and restart the server.

CiscoView fails to launch.

For an ONS 15501, server-based CiscoView is not installed.

ONS 15501 NEs do not have embedded CiscoView. Make sure server-based CiscoView is installed.

The client is not configured properly.

See Cisco Transport Manager Release 7.2 Installation Guide for client configuration instructions.
There are too many active Telnet sessions on the NE.
If there are already five active sessions (the limit on ONS 15501, ONS 15530, and ONS 15540 NEs), the following error message is displayed on the browser:

A network error occurred while Netscape was receiving data.
Terminate one of the Telnet sessions; then, launch CiscoView.
CiscoView launches but the device is not displayed.

If you can ping the device, SNMP might not be enabled on the device, or the community string might be configured incorrectly on the device.

Enable SNMP on the device and verify that the community string is correct.

If you cannot ping the device, there might be a network problem.

Correct the network problem.

The timeout value might be too low.

Click Preferences to change the timeout value. Doubling the existing value is a good starting point.

The device package is not current.

Click About to check the device package. Compare the date of the package to the latest version on Cisco.com. Upgrade your device package to the latest version.

Received noSuchName message.

A request was made for a variable that is not accessible.

Enter the correct community string for the device.

Received badValue message.

The SNMP agent in the NE did not respond within the time interval specified by the timeout and retries values. This can also indicate an incorrect community string.

Use the Preferences SNMP tab to enter new timeout and retry values.

Enter the correct community string for the device.

Browser prompts for Java Plug-in every time CiscoView is launched (on a Solaris client).

The environment variables are not set.

Make sure you source the /jpi.cshrc or /jpi.profile file before launching the browser. This sets the correct environment variable.

CiscoView runs slowly with Java Plug-in installed.

The Java console is enabled.

Make sure the Java console is disabled:

•On a Windows client—To bring up the Java Plug-in control panel, click the Java Plug-in icon in the Windows Control Panel. Uncheck the Show Java Console check box.

•On a Solaris client—To bring up the Java Plug-in control panel, enter the command /usr/j2se/jre/bin/ControlPanel. Uncheck the Show Java Console check box.

Browser hangs when trying to launch CiscoView

There is an incompatibility between CiscoView and the Java Plug-in version currently installed on the client workstation.

CiscoView works only with Java Plug-in 1.3.1-b24. If the CTM client workstation is using a different plug-in version, CiscoView does not launch.

To ensure that your system has the correct plug-in version, you must uninstall any 1.3.1 JDK or JRE version that is currently installed. After uninstalling, launch CiscoView for an ONS 155xx NE from CTM. CiscoView automatically installs the correct Java Plug-in version and launches correctly.

Netscape freezes right after you install the Java Plug-in on a Windows client.

—

Restart the client system.

In CiscoView, after selecting an NE, the browser URL points to the NE IP address instead of the CTM server IP address.

CiscoView is installed incorrectly.

Complete the following steps:

1. Enter the ctms-stop command to stop the CTM server.

2. Enter the ctms-start command to restart the CTM server.

3. Close CTM.

4. Uninstall CiscoView.

5. Run cleanview.sh (located in the UninstallerData directory) to further clean up the CiscoView uninstall process. Make sure that the dmgtd is not running.

6. Install CiscoView.

7. Start CTM.