|
|
Cisco Works 2000 Resource Manager Essentials (CW2000 RME) is an element manager used to routinely manage Cisco equipment.
In this case study, CW2000 RME is used for the following tasks:
The following installation assumptions are made in this case study:
Reference | URL |
|---|---|
CiscoWorks 2000 TAC Support Page—Provides links to technical information for implementing, operating, and troubleshooting Cisco Works 2000. |
|
CiscoWorks 2000 Documentation Set—A collection of configuration guides and reference manuals. |
|
In this case study, CW2000 RME relies on the automatic-discovery mechanism in HPOV to discover devices in the network. CW2000 RME extracts the following information from the HPOV database after HPOV discovers the devices:
Device information is stored in the following database locations:
 |
Note Alternatively, you can use Cisco Works for Switched Internetworking (CWSI) to discover devices instead of using HPOV. |
To import the list of devices and SNMP community strings from HPOV into CW2000 RME, follow these steps:
Incorrect SNMP community strings prevent polling cycles. For basic verification steps, see the
"Task 7Using HP OpenView to Create the SNMP Framework" section.
Step 2 From the root directory, verify that the HPOV database daemon is running in the background by entering the ovstatus ovwdb command:
aurora:/ ->ovstatus ovwdb object manager name: ovwdb state: RUNNING PID: 442 last message: Initialization complete. exit status: - aurora:/ ->
|
Note If a daemon is not running, try restarting it by using the commands ovstop daemon-name and ovstart daemon-name. If a daemon is still not running, an HPOV license issue may exist. For more information, go to http://www.openview.hp.com |
Step 3 From a web browser, log in to CW2000 RME.
Step 4 Click on the Admin menu on the left toolbar.
Step 5 Select Inventory: Import from Local NMS.
Step 6 In the Import from Local NMS screen:
The SNMP community strings are automatically set during the import operation.
Devices Imported from HP OpenView
Step 7 Click Next.
The devices are imported and a status summary appears.
Step 8 Click Update until you see all the devices classified as managed devices.
A constant pending or conflicting state indicates a problem that requires resolution:
To verify that polling is enabled or to alter any polling settings, follow these steps.
Step 2 In the Select Polled Views screen, select All Views and All Polled Views.
Polling Setup
Step 3 Click Next.
Step 4 To accept the default settings, click Finish.
To inspect the status and availability of the devices, follow these steps.
The Status of the Devices
Step 2 Click a device to become familiar with the different management elements. Green arrows indicate devices that are up. Red arrows indicate devices that are down.
Step 3 To turn on continuous availability monitoring and reporting, go to the Tasks menu. Click on Availability: Availability Monitor.
Step 4 Select All in the Views window.
Devices Listed in the Availability Monitor
Step 5 Select one or more devices.
Step 6 Click Finish.
Step 7 Inspect the available elements for the devices.
Having quick access to archived configuration files reduces network downtime when problems occur.
|
Note You can only back up managed devices. |
To back up the Cisco IOS start-up configuration files for devices within the network, follow these steps:
The Update Archive Screen
Step 2 Select All Devices.
Step 3 Select one or more devices from the list that appears.
Step 4 Click Finish.
The Cisco IOS start-up configuration file is copied from the router to the Unix workstation.
CiscoView is a GUI-based device management software application that lets you access dynamic status, statistics, and comprehensive configuration information for Cisco products.
To inspect device-specific characteristics on different Cisco devices, follow these steps:
Step 2 Go to Monitor: CiscoView.
Step 3 Select and view different system components.
Card Positions in the Cisco AS5800 Dial Shelf
Available Modems in the Cisco AS5800 Dial Shelf
Posted: Fri Sep 29 08:21:39 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.