This section discusses the objectives, audience, organization, and conventions of the Cisco Hub/Ring Manager for Windows Getting Started Guide.
All Cisco technical documentation and additional literature are available on UniverCD, Cisco's online library of product information. UniverCD is updated and shipped monthly, so it might be more up to date than printed documentation. UniverCD is available both as a single CD and as an annual subscription. To order UniverCD, contact your local sales representative or call Customer Service.
This publication will step you through initial site preparation, installation, configuration and operation of Cisco Hub/Ring Manager for Windows. The appendices provide additional details on supporting components of network management software.
This publication is designed for the person managing the Token Ring network, including the network-management PC that is running Cisco Hub/Ring Manager for Windows. This guide assumes that you are familiar with the basic concepts and terminology used in internetworking, and that you understand your network topology and the protocols you will route. This guide also assumes that you have a working knowledge of the Microsoft Windows environment and HP OpenView.
This guide does not contain information on HP OpenView, nor does it contain information about setting up or configuring your Cisco 2517. For information on the Cisco 2517, refer to the Cisco 2517 Router/Hub User Guide.
This guide is also useful for data communications specialists, who are responsible for performing network management and troubleshooting, and for distributed systems operators, who are responsible for monitoring the network.
For additional information, refer to the following Cisco Systems publications:
- CiscoWorks for Windows Getting Started Guide
- Cisco 2517 Router/Hub User Guide
- Router Products Getting Started Guide
- Router Products Command Reference
- Router Products Configuration Guide
- Access and Communication Servers Configuration Guide
- Access and Communication Servers Command Reference
- Router Products Command Summary
- System Error Messages
- Cisco MIB User Quick Reference
- Cisco Products Catalogue
- Internetworking Terms and Acronyms
- Hardware installation and maintenance publication for your product
- Configuration notes for your product, if applicable
Note Document titles might vary slightly depending on the software release.
All of these documents are available on UniverCD, Cisco's interactive online library of product information. To order UniverCD or paper documentation, refer to "Ordering Cisco Documentation," which was shipped with your product.
See also your HP OpenView for Windows user guide.
The Cisco Hub/Ring Manager for Windows Getting Started Guide is organized as follows.
- Chapter 1, "Overview," lists Cisco Hub/Ring Manager LAN management station hardware and software and presents an overview of Cisco Hub/Ring Manager for Windows and its applications.
- Chapter 2, "Installing Cisco Hub/Ring Manager for Windows," presents detailed instructions for installing the Cisco Hub/Ring Manager on a network management station.A tutorial section is included to help you perform some of the basic tasks of adding device symbols to your network map and configuring the devices for management by Cisco Hub/Ring Manager for Windows.
- Chapter 3, "Reference to Operations," describes menus and dialog boxes related to Cisco Hub/Ring Manager, specifically for hub management and ring management.
- Appendix A, "TCP/IP Overview and Utilities," provides internet addresses and subnets, TCP/IP system files and utilities, and references.
- Appendix B, "Terminal Emulation," describes terminal emulation programs that are used for modifying the parameters on a remote NMS module. Upon installation of Cisco Hub/Ring Manager, a terminal-emulation program called, TTT.EXE, automatically copied to the /boot directory of your PC. Cisco Hub/Ring Manager provides TTT.EXE as a convenience in case you do not have a suitable "ANSI terminal emulator" program on your PC.
- If you directly connect your network-management PC over the RS-232 serial link, you can use the TTT.EXE program to perform your initial configuration including the SPSET function that is described in your Cisco 2517 Router/Hub User Guide. TTT.EXE provides the required ANSI terminal emulation that makes SPSET look correct and work properly on your console.
- In addition, TTT.EXE is present on the NMS firmware agent. However, within the NMS, TTT.EXE is used for a different purpose. The ROUTER command on the NMS card is actually a batch file (like a macro) that uses the TTT.EXE program in its firmware to establish a terminal emulation session to the router console port of your Cisco 2517. The terminal emulation session, in turn, enables you to configure the router portion of your Cisco 2517.
This document is written under the assumption that HP OpenView is installed in the C:\OV directory.
This section discusses some of the terms commonly used in this document:
- Hub--For the purpose of simplicity, the term hub is used to refer to the Cisco 2517.
- System Initialization File--The C:\OV\OVWIN.INI file is referred to as the System Initialization file.
- System Log File--The C:\OV\OVWIN.LOG file or C:\OV\OVWI2.LOG file is referred to as the System Log file.
- Alarm Log Files--The C:\OV\OVALINS files are referred to as the Alarm Log files.
- Alarm Dialog Box--The HP OpenView Alarm dialog box is referred to as the Alarm dialog box because it contains all the Cisco Hub/Ring Manager alarms.
After you complete the hardware and software setup, you will use the network maps that are part of HP OpenView to help you gather immediate visual reporting of all device status. You can also use audible alarms as well as textual reports to track network activity.
This publication uses the following conventions to convey instructions and information:
Command descriptions use these conventions:
- Commands and keywords are in boldface font.
- Variables for which you supply values are in italic font.
- Elements in square brackets ([ ]) are optional.
- Alternative but required keywords are grouped in braces ({ }) and are separated by a vertical bar ( | ).
Examples use these conventions:
- Terminal sessions are in
screen
font.
- Information you enter is in
boldface screen
font.
- Nonprinting characters are shown in angle brackets (< >).
- Information the system displays is in
screen
font, with default responses in square brackets ([ ]).
Note Means
reader take note. Notes contain helpful suggestions or references to materials not contained in this guide.