Table of Contents
TrafficDirector Release 5.5.1
Upgrade Installation and Release Notes for Windows NT and Solaris
TrafficDirector Release 5.5.1
Upgrade Installation and Release Notes for Windows NT and Solaris
June 1, 1999
This document describes:
- How to install the Year 2000 compliant TrafficDirector Release 5.5.1 software in an existing CiscoWorks 2000 (CW2000) Release 2.2 environment.
- New features in Release 5.5.1.
- Known caveats and limitations in Release 5.5.1.
Note This product can be used only on those Microsoft Windows NT and Solaris systems already running CW2000 with TrafficDirector Release 5.3.
Note The information in this document applies only to TrafficDirector applications running in Microsoft Windows NT and Solaris environments.
Note When you upgrade to TrafficDirector Release 5.5.1 from Release 5.3, the databases and all existing configuration files are automatically preserved.
This document contains the following sections:
Note To use the full functionality of TrafficDirector Release 5.5.1, you must upgrade your SwitchProbe agent firmware to Release 4.5.
When you upgrade to TrafficDirector Release 5.5.1, you can use SwitchProbe devices running the older agent firmware Release 4.2 with the following exceptions:
- Error messages are displayed when you try to use the following new TrafficDirector applications:
- ATM Monitor
- Custom History
- VLAN Monitor
- TopN Conversations
- ART Monitor
- Logging for TopN Conversations fails.
- The tilde domains install but do not work with SwitchProbe devices running Release 4.2 unless you enable the enable_other_domains flag in the device.
- High-Capacity RMON (HCRMON) is not supported.
- All SwitchProbe devices continue to communicate with SNMPv1-type messages and fast upload technology.
- When working with WAN SwitchProbe devices, the Traffic Monitor, Segment Zoom, and Segment Details applications do not reflect utilization above 50% for WAN trunk interfaces.
- NFS_T and NFS_U domains do not install on a SwitchProbe device running Release 4.2.
The files listed in Table 1 have been renamed or made obsolete in Release 5.5.1.
Note If you have scripts that call any of these files, you must edit the scripts to reflect the changes.
Table 1: File Name Changes in Release 5.5.1
| Old File Name
| New File Name
| Description
|
|---|
nsman
| tdir
| TrafficDirector executable
|
nscons
| console
| Console window
|
nstosnif
| cvtosnif
| Command line Sniffer conversion utility
|
nsreport
| report
| Command line report generation utility
|
nstrend
| txtrend
| Trend Reporter
|
nsrpted
| txrpted
| Report Editor
|
nsdomed
| txdomed
| Domain Editor
|
nsqled
| txsqled
| Config Server
|
nssz
| txsz
| Segment Details
|
nshl
| txhl
| All Talkers
|
nscl
| txcl
| All Conversations
|
nsdommon
| txdommon
| Domain Discovery
|
nxhz
| txhz
| Host Zoom
|
nspdec
| txpdec
| Protocol Decode
|
nsrepted
| txrpted
| Report Editor
|
nsdcap
| txdcap
| Data Capture
|
nstrsr
| txtrsr
| Source Routing Monitor
|
nstrrsl
| txtrrsl
| Ring Station List (Token Ring)
|
nsfdrsl
| txfdrsl
| Ring Station List (FDDI)
|
nsresmgr
| txresmgr
| Resource Monitor (Round Trip Delay and Proxy SNMP)
|
nsaltmon
| txaltmon
| Alert Monitor
|
nsfilted
| txfilted
| Filter Editor
|
nslogin
| txlogin
| Remote Login
|
nsshell
| ---
| Obsolete in this release
|
The following sections describe how to install the TrafficDirector Release 5.5.1 software in an existing CiscoWorks 2000 (CW2000) Release 2.2 environment:
This section contains instructions for installing the software from these media types:
- Cisco Connection Online (CCO)
- CD-ROM
To obtain and install the TrafficDirector upgrade from the CCO website, follow these steps:
Step 1 Quit the TrafficDirector application.
Step 2 Close all other applications.
Step 3 From the DOS window, run dbshutdn -all from the %NSHOME%\bin directory.
Note Cisco Systems recommends that you start the Windows Task Manager to verify that the trap daemon (dvtrapd) and all perl scripts have stopped running. If they have not stopped, highlight the task(s) and click End Task.
If you do not stop these processes, the installation will fail when it tries to replace the files that are currently open and being used by those processes.
Step 4 Start your web browser.
Step 5 Log in to the CCO website at http://www.cisco.com.
Step 6 Click Software Support.
Step 7 Under the category Software Center, click Cisco Software Products.
Step 8 Under the category Cisco Software Products, click Network Mgmt Products.
Step 9 Under the category Network Management Products, subcategory Cisco Works for Switched Internetworks, click TrafficDirector.
Step 10 Click TD5.5-nt-smu-.readme.
Step 11 From the Software Download page, you can:
- FTP the readme file directly to your location.
- HTTP the readme file directly to your location.
- E-mail the readme file to a specified location.
Make the appropriate selection and save the file to a local disk.
Note Cisco Systems strongly recommends that you review the information in the readme file before you continue with the upgrade.
Step 12 Click Back to return to the TrafficDirector upgrade selection page.
Step 13 Click TD5.5-nt-smu.zip.
Step 14 From the Software Download page, you can:
- FTP the software directly to your location.
- HTTP the software directly to your location.
- E-mail the software to a specified location.
Make the appropriate selection and save the file to a local disk.
Step 15 Create a temporary location into which to unzip the zip archive.
Step 16 Change directory to that temporary location.
Step 17 Unzip the TD5.5-nt-smu.zip archive.
Step 18 Run setup.exe.
A dialog box will display the following message and prompt:
Setup detected a previously installed version of TrafficDirector. Please make sure all TrafficDirector application windows are closed and log files are not open.
Do you want to continue with the upgrade/reinstall of TrafficDirector?
Step 19 Enter Y and press Enter.
A dialog box will display the following information:
You can select one of the following databases for data logging.
Step 20 Depending on the type of database you wish to use, click the Microsoft SQL (the default) or Embedded SQL radio button.
Step 21 Click Finish.
Step 22 After setup has finished, you must restart your system now so that the TrafficDirector application will run properly; click Restart Now.
To install the TrafficDirector upgrade from CD-ROM, follow these steps:
Step 1 Quit the TrafficDirector application, and close all other applications.
Step 2 From the DOS window, run dbshutdn -all from the %NSHOME%/bin directory.
Note Cisco Systems recommends that you start the Windows Task Manager to verify that the trap daemon (dvtrapd) and all perl scripts have stopped running. If they have not stopped, highlight the task(s) and click End Task.
If you do not stop these processes, the installation will fail when it tries to replace the files that are currently open and being used by those processes.
Step 3 Insert the CD-ROM into the CD-ROM drive.
Step 4 Run setup.exe.
A dialog box will display the following message and prompt:
Setup detected a previously installed version of TrafficDirector. Please make sure all TrafficDirector application windows are closed and log files are not open.
Do you want to continue with the upgrade/reinstall of TrafficDirector?
Step 5 Enter Y and press Enter.
A dialog box will display the following information:
You can select one of the following databases for data logging.
Step 6 Depending on the type of database software you wish to use, click the Microsoft SQL (the default) or Embedded SQL radio button.
Step 7 Click Finish.
Step 8 After setup has finished, you must restart your system now so that the TrafficDirector application will run properly; click Restart Now.
This section contains instructions for installing the software from these locations:
- Cisco Connection Online (CCO)
- CD-ROM
To obtain and install the TrafficDirector upgrade from the CCO website, follow these steps:
Step 1 Quit the TrafficDirector application, and close all other applications.
Step 2 Log in as the root user.
Step 3 Shut down all the TrafficDirector daemons running on your system by entering the dbshutdn -all command from the $NSHOME\bin directory.
Note To confirm that the daemons are shut down, check the dbshutdn.log file.
Step 4 Start your web browser.
Step 5 Log in to the CCO website at http://www.cisco.com.
Step 6 Click Software Support.
Step 7 Under the category Software Center, click Cisco Software Products.
Step 8 Under the category Cisco Software Products, click Network Mgmt Products.
Step 9 Under the category Network Management Products, subcategory Cisco Works for Switched Internetworks, click TrafficDirector.
Step 10 Click TD5.5-sol-smu-.readme.
Step 11 From the Software Download page, you can:
- FTP the readme file directly to your location.
- HTTP the readme file directly to your location.
- E-mail the readme file to a specified location.
Make the appropriate selection and save the file to a local disk.
Note Cisco Systems strongly recommends that you review the information in the readme file before you continue with the upgrade.
Step 12 Click Back to return to the TrafficDirector upgrade selection page.
Step 13 Download the following files:
- TD5.5-sol-smu-01
- TD5.5-sol-smu-02
- TD5.5-sol.map
- TD5.5-sol_install.sh
Step 14 From the Software Download page, you can:
- FTP the software directly to your location.
- HTTP the software directly to your location.
- E-mail the software to a specified location.
Make the appropriate selection and save the file to a local disk.
Note Verify that the NSHOME variable points to the location of the TrafficDirector 5.3 software.
Step 15 Change directory to the save location.
Step 16 Change the permission on the TD5.5-sol_install.sh file by entering the following command:
chmod 777 TD5.5-sol_install.sh
Step 17 Run the install program as root by entering the following command:
./TD5.5-sol_install.sh
After the install program finishes verifying, rebuilding, decompressing, and untarring the tar file, the following message is displayed:
TrafficDirector 5.3 detected in [5.3 location]
Continue with upgrading TrafficDirector to version 5.5 (y/n)? [y]
Step 18 Enter Y and press Enter.
A long series of messages is displayed.
The final message tells you that the installation was successful.
Note Because a number of tasks are executing in the background, you must wait for the UNIX shell prompt to display on your monitor before you do anything else.
To install the TrafficDirector upgrade from CD-ROM, follow these steps:
Step 1 Quit the TrafficDirector application, and close all other applications.
Step 2 Log in as the root user.
Step 3 Shut down all TrafficDirector daemons running on your system by entering the dbshutdn -all command from the $NSHOME\bin directory.
Note To confirm that the daemons are shut down, check the dbshutdn.log file.
Note Verify that the NSHOME variable points to the location of the TrafficDirector 5.3 software.
Step 4 Insert the CD-ROM into the CD-ROM drive.
Step 5 Change directory to the location where the upgrade software is located by entering the following command:
cd install.td5
Step 6 Run the setup program by entering the following command:
./setup.sh
The following message is displayed:
TrafficDirector 5.3 detected in [5.3 location]
Continue with upgrading TrafficDirector to version 5.5 (y/n)? [y]
Step 7 Enter Y and press Enter.
A long series of messages is displayed.
The final message tells you that the installation was successful.
Note Because a number of tasks are executing in the background, you must wait for the UNIX shell prompt to display on your monitor before you do anything else.
Release 5.5.1 includes the major new features and enhancements described in the following sections:
To support the widest range of topologies and standards possible, Release 5.5.1 provides a variety of features for the new MIB definitions and other important standards, as follows:
- ATM RMON MIB---This release fully supports the ATM RMON MIB as implemented in Cisco ATM SwitchProbe devices. You can collect native ATM statistics for specific port groups.
- Switch Monitoring (SMON) standard---This release supports the emerging SMON standard (RMON MIB extensions for switched networks) so you can view switch traffic by VLANs or priorities as discovered by an agent or switches that embed SMON reporting. Both ISL and Token Ring-ISL protocols and the 802.1Q standard (Ethernet Tag---ETPID without RIF support) are supported to monitor communications between switches. Snap tag and Null tagging under the 802.1Q standard are not supported.
- Application Response Time (ART) MIB---This release introduces extensions to RMON to track application response time for the ART MIB. You can examine statistics for application retries, traffic load, and response time to receive an up-to-date picture of application load on the network.
- High-Capacity RMON (HCRMON)---To provide added support for data captured from high-speed SwitchProbe devices, applications can now graphically display 64-bit counters as implemented in the HCRMON draft standard. This reduces the chance for losing data if a counter wraps between polling intervals. The overall polling frequency is also minimized.
- Extensions for RMON2 groups---All RMON2 groups (including User History, Probe Config, and TopN Conversations) are fully supported on selected SwitchProbe devices. Third-party applications can also use the Probe Config features for help with configuration.
- Extended NetFlow Support---Up to eight Cisco routers or interfaces on multi-interface routers can be accommodated on Fast Ethernet SwitchProbe devices to track router statistics using NetFlow conventions (in addition to the single aggregate NetFlow interface). The device can receive IP address and interface port number group information when the NetFlow option is enabled on the device and configured in the hardware.
- SNMPv2 Bulk Retrieval---Third-party applications can now take advantage of improved performance when using SNMPv2 messaging for communication with a SwitchProbe device. The following applications now display switch ports, hosts, conversations, and logging more quickly:
- TrafficMonitor
- Protocol Monitor
- Application Monitor
- Protocol Zoom
- All host- and conversation based applications, domain discovery, and logging daemons.
Table 2 lists the new monitoring applications that provide support for the extended RMON standard:
Table 2: New Monitoring Applications That Support Extended RMON Standards
| This New Application...
| Supports
|
|---|
Custom History
| RMON2 User History group
|
ATM Monitor
| ATM RMON MIB
|
ART Monitor
| ART MIB
|
VLAN Monitor
| SMON draft standard
|
TopN Conversations
| Viewing of statistics for the most active conversation pairs for a single RMON2 or ATM RMON agent.
|
The following usability and functional improvements have been made to the Trend Reporter subsystem:
- GUI enhancements
- Improved ASCII report viewing
- Configurable daily reports
- Easy navigation of multisegment reports
- New reports---The following reports provide reporting capabilities for the new applications and expand features to supply data aggregation and baseline capabilities:
- Baselines
- Proxy SNMP
- Application Response Time
- TopN AL/NL Hosts and Conversations
- Network Volume Summary
The following new extensions are provided for monitoring switches, Frame Relay agents, and ATM virtual channels (VCs):
- Switch Monitoring---The following enhancements have been made to switch monitoring:
- Fast EtherChannel/multiport roving.
Added to Catalyst 5000-series switches, you can view traffic from several ports simultaneously.
- VLAN interface monitoring.
With the new VLAN agent options, you can monitor Cisco ISL and 802.1Q VLANs on full-duplex links as though they were individual links.
- Enhanced switch configuration.
To ease the switch configuration process, you can create a master switch properties file that you can apply to identical switches. Using the switching file, the TrafficDirector application can automatically assign port files to specific port numbers. You can create port properties files for user, server, and trunk ports, so different properties can be applied per port.
- ATM Monitoring---The following enhancements have been made to ATM monitoring:
- ATM RMON MIB support.
Native ATM evaluation can now be achieved in various applications so you can monitor using the ATM NSAP address.
- ATM data captures.
Now supports raw mode for examining ATM headers in addition to WAN headers. This feature helps you troubleshoot complex ATM problems at their source.
- ATM virtual channel as an interface.
With the new ATM RMON support, you can monitor each VPI/VCI pair from ATM SwitchProbe devices in TrafficDirector applications.
- Generic domains for LAN Emulation (LANE) types.
With ATM RMON support, you can monitor by ATM LAN emulation type, including LANE, and Multiprotocol over ATM/Classical IP (MPOA/CIP).
The following configuration enhancements have been made:
- Embedded SQL database on NT---This release supports an embedded version of a SQL database on Windows NT, in addition to Microsoft SQL Server support. This option saves time and money in deploying a SQL database for reporting; the embedded SQL databases on UNIX platforms can receive data from the Windows embedded version, and vice versa.
- Autodiscovery of multiport SwitchProbe interfaces---To ease the agent configuration process, the configuration subsystem can extract the names of monitoring interfaces and their topology from the SwitchProbe device automatically.
Several existing real-time monitoring applications have been improved to increase ease of use and provide extensions for other new features:
- Data Capture---Allows you to save Ethernet, Token Ring, and FDDI packets in Sniffer 5.0 format. You can also filter traffic based on protocol definitions and those filters defined with the Filter Editor.
- New Protocol Decodes---To support a greater number of industry-standard, and most widely used protocols, definitions for the following decodes have been added:
- HTTP, for greater insight into web traffic.
- SNMP enhancements to support SNMP v2, extensions for the RMON2 groups, HCRMON, ATM RMON, and SMON.
- Traffic Monitor---Increased ease of use in viewing data can now be achieved through:
- Paging (with stepping arrows) to show more ports (maximum of 32 simultaneously).
- Port speed display for 10/100 switches and CIR on DLCIs.
- Alarm Discovery---You can view all currently configured domains and existing alarms in the enhanced Domain/Alarm Discovery application.
Table 3 describes notes and caveats about TrafficDirector Release 5.5.1.
Table 3: TrafficDirector Release 5.5.1 Notes and Caveats
| Functional Area
| Description
|
|---|
Upgrade issues
| The following issues apply to upgrading the TrafficDirector software:
- When upgrading from TrafficDirector Release 5.3, all switch roving information is lost.
- After upgrading, you must change the description in the Roving Agent field to "Internal" for any switches in which the Network Analysis Module is installed. If you do not do this:
- Roving operations with the Network Analysis Module will fail.
- Installation of properties files on the switch might not work.
- This happens because the TrafficDirector Release 5.3 software uses the name of the switch to define the roving agent; the TrafficDirector Release 5.5.1 software uses the name "Internal" for the Roving Agent field.
- The upgrade does not delete the external agent for the Network Analysis Module that was created with TrafficDirector Release 5.3.
- The port properties file name is truncated in the display after the upgrade on Microsoft NT platforms. To see the complete file name, click the port; the file name is displayed in the right-hand corner.
|
Interpreting some reports
| For some reports, the Utilization% displayed may differ from that shown on Segment Details. [CSCdk57767] [CSCdk55659]
|
Network Analysis Module
Release 4.3(1a)
| The following caveats are known to exist in the Network Analysis Module:
- The Network Analysis Module supports the roving of only one port; therefore, adding a port to a list of roved ports is not supported.
- Running Domain Discovery against a switch port, VLAN, or FEC that is roved to a Network Analysis Module results in an error retrieving alarm entries.
- Running Data Capture against a switch port, VLAN, or FEC that is roved to a Network Analysis Module may result in the Running For field showing an incorrect value. [CSCdk87967]
- You can enable and install logging for ports that are roved to the Network Analysis Module. However, the logging daemons are not started, and therefore no actual data is logged to the database. Generating a report against this data results in an error stating that there is no data available for that report. [CSCdk84504]
|
ping
| The TrafficDirector application ships with the default pingoff file. This file is required for successful pings on selected agents if you are running either the HP-UX or TCP/Pro TCP/IP stacks. For pings to be performed successfully when you are running any other TCP/IP stack, delete the $NSHOME/usr/pingoff file.
|
Support for switch roving
| The following caveats exist for switch roving:
- Before roving multiple ports, verify that the ports are all in the same VLAN and that one of the ports is not a trunk or FEC port. [CSCdk49058]
- If you make any changes to a roved port, FEC, or VLAN without using the TrafficDirector application (for example, using the switch command-line interface), the TrafficDirector application will not reflect these changes. [CSCdk44815]
- An error message is displayed when you attempt to rove a port or a group of ports that contains a port that has already been roved. [CSCdk60830]
- TopN Conversations is not supported for the ALLAL and ALLNL domains.
|
NMS integration
| The following NMS integration caveats are known in this release:
- The TrafficDirector application does not integrate with CastleRock SNMPc.
- The TrafficDirector application does not integrate with SunNet Manager at installation time. To perform this integration, refer to the Using the Campus TrafficDirector Application publication. [CSCdk70759]
|
Disabling host-conv-getbulk
| Disabling the host-conv-getbulk option in the default.dvp configuration file results in duplicate entries appearing in the ATALK All Talkers display. [CSCdj89834]
|
Known limitations
| The following limitations are known to exist in this release:
- VLANs are only learned on Catalyst 5000-series devices. [CSCdk29981]
- To log data and run Trend Reports on an individual VLAN, you must enable logging on the specific interface for that VLAN.
- The RMON II probeConfig group is supported only on a limited number of SwitchProbe devices. [CSCdk47296]
- The maximum number of History buckets supported on a Catalyst 1900 series or Catalyst 2820 series device running release 8.X is 20.
- Mini-RMON is not supported for VLANs and FECs on the Catalyst 5xxx family of switches. Trying to use a mini-RMON application (such as Traffic Monitor, Short- and Long-Term History, Segment Details, Segment Zoom, and so on) against a roved VLAN with the Network Analysis Module produces an error.
- On the Catalyst 19xx and 28xx families of switches, the TrafficDirector IP address or host name must be defined as one of the four WRITE Managers in the Network Management (SNMP) Configuration. If it is not defined, the roving and installation of properties files will fail.
- The TrafficDirector application does not recognize gigabit modules in the Catalyst 8510 switch.
|
Viewing managed interfaces
| In the Add Agent window, if you select View, the managed interface of the SwitchProbe device is displayed. You must deselect this agent before saving any of the entries as agents. [CSCdk40368]
|
Running All Talkers
| Running the All Talkers application for the ATALK domain may result in duplicate entries being displayed. [CSCdj89834]
|
Shutting down the
TrafficDirector application
| Shutting down the TrafficDirector application does not always shut down all of the daemons. [CSCdk50319]
|
The following updates apply to the Using the Campus TrafficDirector Application publication.
The following information was inadvertently omitted from the sections "Enabling Domains for Monitoring" on page 6-8, and "Defining Individual Properties" on page 6-23:
If, when adding or editing a domain in a properties file with Property Editor, you cannot see all domains defined in that properties file, follow these steps:
Step 1 Shut down the TrafficDirector application.
Step 2 Restart the TrafficDirector application.
Step 3 Restart Property Editor.
You will then be able to see all domains in the properties file.
The following information was inadvertently omitted from the subsection "Creating .udh Files" on page 19-15, Step 4:
To identify the OID string, refer to the appropriate MIB document or a MIB browser that shows both the OID name and value.
For example, to indicate ifInOctets, you would specify 1.3.6.1.2.1.2.2.1.10.
To identify which variable instance to use, you must specify the interface on the SwitchProbe device for which you want to track the OID you specified. You can identify this using either the IFINDEX, DLCI #, or CONTROL INDEX of that interface.
For example, to track ifInOctets for interface 3, you would specify 1.3.6.1.2.1.2.2.1.10@IFN.3; to track ifInOctets for DLCI 57, you would specify 1.3.6.1.2.1.2.2.1.10@DLCI.57.
The following note was inadvertently omitted from the description of the Buffer Size parameters in the section "Establishing Data Capture Parameters," Table 28-1, on page 26-5:
Note On Windows NT platforms, the Buffer Size field only accepts a value with a maximum of four digits. Click the Mb radio button to specify a value larger than 9999 Kb.
The following note was inadvertently omitted from the section "Testing Agents, Switches, and Frame Relay Agents" on page A-4:
Note The Test Agent feature does not update the SPAN port information under the Roving Information when the SPAN port is set on the switch through the command line. It will always reflect the information about the port that was roved from the TrafficDirector application and is not updated.
The HP OpenView-related information in the subsection, "Integrating with HP OpenView or IBM NetView/6000," should be replaced with the information in this section:
To integrate the TrafficDirector application with HP OpenView, follow these steps:
Step 1 Stop all open ovw sessions.
Step 2 Enter the following command:
cd $NSHOME/ums/fsd_ov/bin ./install.ovfiles.ovw
Step 3 Edit the OpenView files as follows:
- For each agent (SwitchProbe device or embedded RMON agent) on your network, add that device's system object identifier (sysoid) to the file /etc/opt/OV/share/conf/oid_to_sym, followed by :Net Device:SwitchProbe.
- A list of entries reflecting various IOS-embedded RMON agents is located in the $NSHOME/ums/fsd_ov/config/oid_to_sym_TrafficDir file.
- For each agent on your network, add a similar line to the /etc/opt/OV/share/conf/oid_to_type file, followed by :Cisco Systems:SwitchProbe Agent.
- You can find a list of example entries for this file in the file $NSHOME/ums/fsd_ov/config/oid_to_type_TrafficDir.
Note These files reflect SwitchProbe device firmware revision 2.2.0 or later. For older firmware revisions, you can learn the object identifier by selecting the device and querying its SNMP MIB. To do this, select Monitor>MIB Values.
Step 4 Query the setting for the sysoid from the Systems Group.
Step 5 Edit the file /etc/opt/OV/share/fields/C/snmp_fields by adding the line RMON Agent to the SNMP Agent fields enumeration.
Step 6 Run the OpenView program to add the symbol and fields to the OpenView database.
To do so, enter the following command:
ovstart
Step 7 Enter the following command to create a new symbol under an existing symbol class Net Device:
/opt/OV/bin/ovw -fields
A new enumerated value is assigned to the Vendor field. A new enumerated value---RMON Agent---is assigned to the SNMP Agent field. You can use these field values and symbol types to locate SwitchProbe devices or embedded RMON agents in OpenView network maps.
Step 8 Start an OpenView windows session by entering the following command:
/opt/OV/bin/ovw
Note You must set the NSHOME environment variable before you start an OpenView session.
Step 9 Several applications, when started from an OpenView session, require an Xterm window. You can find the Xterm executable in the /usr/x11/bin directory. For Sun systems, the path is /usr/openwin/bin. You must add this directory to your execution path.
- In the csh shell, enter the following command:
setenv PATH /usr/X11/bin:$PATH
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.
Posted: Tue Jun 1 12:22:41 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.
