Table of Contents

Release Notes for
ViewRunner for HP OpenView Release 2.3.5

Release Notes for
ViewRunner for HP OpenView Release 2.3.5

April 6, 1999

These release notes describe features, resolved problem reports, and unresolved problem reports for the ViewRunner for HP OpenView Release 2.3.5.

For more detailed information about the features in these release notes, refer to the "" section. Information about electronic documentation can be found in the "Cisco Connection Online" section, and in the "Documentation CD-ROM" section.

1. Contents

These release notes discuss the following topics:

2. ViewRunner for HP OpenView

ViewRunner for HP OpenView Release 2.3.5 serves as the Carrier Class Element Management System (EMS) for the Cisco 6100.

The ViewRunner for HP OpenView Release 2.3.5 supports the following Cisco 6100 releases:

The following matrix more fully describes the compatibility among Cisco 6100 and ViewRunner for HP OpenView releases.

Table 1: ViewRunner for HP OpenView and Cisco 6100 Release Compatibility Matrix
Cisco 6100 Releases
Release 2.3.0 Releases 2.2.1/2.2.5 Release 2.2.0 Release 2.1.3 Release 2.1.2
ViewRunner for HP OpenView

Release 2.3.5






Release 2.3.0

6100 2.2.1

FCM update for 2.2.5




Release 2.2.0

6100 2.2.0

6100 2.2.0





X indicates that ViewRunner presents a feature set customized to this Cisco 6100 release's capabilities.

Cisco 6100 X.Y.Z -View Runner presents a feature set corresponding to the specified Cisco 6100 X.Y.Z release's capabilities. ViewRunner prompts the user when the Chassis View is opened that the feature set is not recognized and a default feature set is being used.

3. Primary Fixes for ViewRunner for HP OpenView Release 2.3.5

The primary fixes contained in this release are:

4. New Features for ViewRunner for HP OpenView Release 2.3.5

The new features in ViewRunner for HP OpenView Release 2.3.5 are as follows

4.1 Support for ATU-C Modules

Support for ATU-C modules in Direct Connect configurations only is included in this release. The Module Properties dialog displays the transceiver properties of the module, including the line coding method (CAP) for any ATU-C module.

The existing table that shows performance statistics, such as successful trains, failed trains, etc., has been modified to allow single lines of the table to be selected. Once you have selected a line of the table for an ATU-C module, a button on the performance dialog enabled to allow you to display a graphical representation of the Bit Allocation, SNR, and Receiver Gain for that module. The graph can be refreshed or closed using available buttons on the display. The range of the training statistics display is the same as that specified in the MIB.

In ViewRunner for HP OpenView, the user can open as many ATU-C graphs as are allowed by the windows system limit.

4.2 Per-subscriber Provisionable CPE Signature Detection

You can configure per-subscriber CPE signature detection for a LIM module (DOH) or an ATU-C module (Direct Connect) through the Subscriber Properties dialog. You can specify of the minimum CPE signature within a range of 0-127. The default is 0 which essentially disables CPE signature detection.

If the system controller (SC) revision supports per-subscriber provisionable CPE detection, then the performance dialog displays dashes in the "Non-Timer Failed Trains" column, and the total for that column is disabled. There is also a new column in the subscriber tab of the performance dialog called "CPE Rejects" which totals the number of CPE signature which were not detected by design.

In addition, the "Allow non-timer CPE trains" toggle on the Cisco 6100 Properties dialog is disabled unless the SC revision supports ATUCPARMS but does not support per-subscriber provisionable CPE.

4.3 Per-subscriber Provisionable 136K Baud Training Rates

Both CAP modules support 136 KBaud training rates, which can be allowed or disallowed when the feature is supported by the SC software revision and the subscriber is locked. If the SC supports per-subscriber provisionable 136 KBaud or does not support ATUCPARMS, then the "Allow 136 KBaud" toggle on the Cisco 6100 Properties dialog shall be disabled. If the SC supports ATUCPARMS but does not support per-subscriber 136 KBaud then the toggle is enabled.

4.4 Per-node Provisionable EPD Controls

If you have administrator level permissions, you can configure a per-node EPD threshold of between 0 and 60 cells through the Cisco 6100 Properties dialog. If you have guest level permissions, the Edit EPD... button is disabled, but operators may or may not be able to edit the EPD depending on the permissions granted by the administrator to that operator. The default is 0. The Properties dialog has a field showing the EPD value which is not editable, and it has a button to edit the value. When you bring up the edit EPD dialog, a warning alerting you that changing the EPD value will affect system performance appears and a field where you can set the EPD threshold.

4.5 Per-subscriber Session Timer with Configurable Lockout

The Subscriber Properties dialog has toggle buttons for both session and idle timer types with editable fields for connection timeout in minutes for each. There are two other editable fields for timers, PVC Idle and Lockout time. The Lockout time can be set for minutes. If the SC does not support timer settings, then all the fields will be disabled. Otherwise, the fields will be enabled or disabled depending on the administrative state of the subscriber (locked or unlocked). The default settings are session timeout at 100 minutes. The valid range for the session timer is 1 to 240 minutes.

4.6 Per-subscriber Idle Timer with Configurable PVC Low Tide Mark

The Subscriber Properties dialog has toggle buttons for both session and idle timer types with editable fields for connection timeout in minutes for each. There are two other editable fields for timers, PVC Idle and Lockout time. The PVC Idle time can be set for cell per minute. The per-subscriber idle timeout default is zero, or disabled. The subscriber can be disconnected if the PVC rate is below the specified threshold of the idle timer setting. The default value of the PVC threshold is zero, or disabled. The range for the PVC threshold is 1 to 2147483647 cells per minute.

The PVC threshold is used also for low tide monitoring. If the PVC traffic is less than the threshold for the duration of the timer, then the PVC is considered idle and the subscriber is disconnected. If the traffic is more than the threshold, the PVC is considered active.

A subscriber can have multiple PVCs. If at least one PVC is active, then the subscriber stays connected.

4.7 Inband Channel Software Download Capability

ViewRunner for HP OpenView supports software downloads and restores for Cisco 6100 nodes being managed via the inband management channel or the ethernet management channel. The menu option allowing this feature is active only if the SC supports the feature and the node is being managed through one of the management channels. Warnings will be issued if software download / restore is not supported by either the current or the target SC.

4.8 Support for DOH Pool Blocking Time Counter

In the DOH Performance dialog, two counters display the total time and block time in minutes experienced by the logical modem pool since its creation or since the last system reset. A blocked minute is any minute during which one or more subscribers is refused modem port assignments in response to DOH connection requests due to 100% modem utilization. The total time is the number of minutes that the logical modem pool has been in existence or since the last system reset. These counters are displayed on the Pool Performance dialog.

4.9 Removal of Unused User Interface Elements

User interface elements which are not being used have been removed from dialogs and displays. Specifically, the menu and button options for ViewRunner help and the maintenance state field have been removed from dialogs and displays.

4.10 Module Status Icons on Module Tabs

ViewRunner for HP OpenView Release 2.3.5 displays the Administrative and Operational states of the node as an icon on the module and port tabs of the Module Properties dialogs.

4.11 Cisco Identity Changes

With the exception of the MIB, all external references to NetSpeed have been removed and replaced by references to Cisco where applicable.

4.12 NI Module Type Determination

Since the MIB does not contain any information about the NI module type, the feature compatibility matrix (FCM) contains a table that includes this information. The type of NI is displayed in the Module Properties dialog, the face plate of the module on the Chassis View, and in the Inventory dialog.

4.13 Support for Additional Third Party Software Versions

ViewRunner for HP OpenView Release 2.3.5 supports additional versions of its primary third party software. The following table illustrates the current third party support:

Table 2: Third Party Software Support

Operating System

Solaris 2.5.1

Solaris 2.6

HPOV Version

HPOV 4.11

HPOV 5.0

Oracle 7.3.2



Oracle 7.3.3



Oracle 7.3.4



The Oracle database server can be distributed to an external workstation.

4.14 Map Synchronization Changes

ViewRunner for HP OpenView Release 2.3.5 allows the user to specify either automatic or manual layout of nodes within on a map. Using manual layout, the map synchronization process retains the manual layout of the nodes within a map. In automatic layout, map synchronization deletes the nodes and re-adds them to synchronize with the database.

4.15 Primary Administrative Login Changes

The primary administrative login has been changed from netspeed to vradmin. The default password for the login is cisco123. When upgrading and existing system, the netspeed login is replaced by vradmin with the existing password.

4.16 Double Clicking on Cisco 6100 Icon Opens Chassis View

ViewRunner for HP OpenView Release 2.3.5 allows the user to double click on a Cisco 6100 icon to open Chassis View for that node.

4.17 Software Upgrade Gets Defaults from vrconstants.conf

During software upgrade, when moving to a release which supports new subscriber data which is not supported in the release being upgraded from, defaults are taken from the vrconstants.conf file instead of relying on node defaults. This allows the user to upgrade software and get default subscriber values set to their site defaults. Otherwise, if the node default does not match what the customer wanted, they would have to modify each subscriber manually after the upgrade.

5. Important Caveats for ViewRunner for HP OpenView Release 2.3.5

The following are the important caveats for ViewRunner for HP OpenView Release 2.3.5.

5.1 XRT Motif SpinButton Widget

There is an issue with the XRT Motif SpinButton widge when ViewRunner is linked with Release 11 of the XRT libraries. The widget works fine on Solaris 2.5.1 but not on Solaris 2.6. If ViewRunner is linked with Release 12 of the XRT libraries, the widget works fine on Solaris 2.6, but not on 2.5.1. Therefore, you will have two separate executables for client programs viewLoopRunner and viewMap. The installation process will install the proper programs based on the version of Solaris currently running on your machine.

Note The fact that there are two separate executables becomes more important when running ViewRunner in a mixed Solaris version environment.

5.2 HP OpenView Network Node Manager

When running HP OpenView Network Node Manager version 5.01 with the latest consolidated patch PSOV_02243 and the ViewRunner viewMap client process, HP OpenView's ovw process core dumps. This does not happen when you are running the earlier PSOV_02091 patch. Unfortunately, the earlier PSOV_02091 patch is not available from HP any longer. Therefore, until HP can fix this problem with the new patch, PSOV_02091 will be available as part of the ViewRunner software distribution.

5.2.1 HP Installation Issue

Description: Alarms are seen in trapd.conf, but not in the HP OpenView Even browser. However, then the Event Browser is invoked form the command line, the events are displayed.

Impact: This condition is an HP OpenView site configuration issue. The Resource settings for the xnmevents application (the HP Event Browser) can keep ViewRunner event from being displayed in the event browser.

Workaround: For the event browser to show all events when invoked from the command line, the user must modify $APP_DEFS/XNmevents file. The user must also un-comment the "*.filterByMap: False" line in this file to show all events.

Note Cisco highly recommends that you install the earlier PSOV_02091 patch.

6. Resolved Problem Reports in Release 2.3.5

The problems listed in Table 3 are resolved in ViewRunner for HP OpenView Release 2.3.5.

Table 3: Resolved Problems in Release 2.3.5
PR Number Description



GUI flicker stopped


Download/restore to deal with subtend


View All Subscribers units not shown


View All Subscribers is blank in subtend scope


Pipe corruption problem


Download aborts after successful SC TFTP


Duplicate alarm displayed


Port totals are incorrect


Server to protect download during inband


ViewMap displays NetSpeed for symbols


Any user can stop VR processes


Nodes disappear from ViewMap and can't be re-added


Change ATUCPARMS restore for 2.2.5 node defaults


Map synchronization to support auto placement off


-53 PSD allowed in GUI but not node


Fix download wizard for multiples


ViewRunner does not restore subscribers if the subscriber's associated port is not assigned to a logical pool when the configuration is saved.

7. Open Problem Reports as of Release 2.3.5

The problems listed in Table 4 are open in ViewRunner for HP OpenView Release 2.3.5.

Table 4: Open Problems as of Release 2.3.5
PR Number Description


A Subscriber with a NULL ID may be configured regardless of user privilege level. (2.2.0)

Impact: Subscriber is added.

Workaround: N/A


Edit button enabled when no transit subscriber selected regardless of user privilege level. (2.2.0)

Impact: None

Workaround: None


Configuring subscriber does not update sorting of View All Subscriber window. (2.2.0)

Impact: None

Workaround: Manually sort the window.


Configuration changes allowed if permission are changed after the configuration dialog is opened. (2.2.0)

Impact: Configuration completes with the current changes

Workaround: None


During Software Download or Restore, if TFTP fails because the image file is not found, the Wizard warns the user that the file is not found. Then if the user chooses to continue, a generic "TFTP Failed" error message is displayed both in the wizard and in the Event Browser instead of a more descriptive "File not found" error. (2.2.0)

Impact: The Event Browser displays a vague error message.

Workaround: none


ViewMap shows wrong message: Subtending LoopRunner X to LoopRunner X. (2.2.0)

Impact: ViewMap Log message may be confusing.

Workaround: None.


Software Download (SWD) failures related to lost communication after SC Reset are not reported as errors in SWD Wizard. (2.2.0)

Impact: If communication to the SC is not restored after an SC Reset (e.g. - Ethernet connectivity is lost), the failure is not presented in SWD Wizard after the 15 minute SC Reset Timeout expires.

Workaround: NetMon log files may be viewed to see these detailed error messages.


Deleting a subtending Cisco 6100 (a Cisco 6100 whose STM ports are connected to NI's of other Cisco 6100's) without deleting the subtend connection objects first results in a difficult to remove inconsistent subtend relationship. (2.2.0)

Impact: After deleting the node, this node will not be able to participate in any subtend network maps until this inconsistency is cleared. (Note: this in no way affects the operation of Cisco 6100 subtending).

Workaround: Refrain from deleting node without first deleting any subtend connections to the node. If this condition arises the following will clear the condition: a) using HP OpenView's MIB browser, set the SpID's of the STM Ports to " " (a single space character). b) delete the node from the OpenView Maps. c) exit OpenView, restart OpenView and re-add the equipment.


Improper Pool dialog operation after configuration sync if the pool window is kept open during sync. a) Incorrect ports displayed for the current pool. b) Ports cannot be unassigned. c) Assign port works, but the port does not get displayed in the current logical pool panel. (1.0.1)

Impact: User workaround to re-enable capability.

Workaround: Either close/reopen the Pool window or tab to the next pool and back to re-enable capability to assign/unassign ports.


ViewLoopRunner occasionally dumps core while opening 6100 Properties window. (2.2.0)

Impact: 6100 Chassis view must be restarted.

Workaround: Right click on the Cisco 6100 map symbol and select View Cisco 6100 Chassis to restart


HP OpenView NNM 4.11 does not support setting variables defined as Read-Create using its graphical MIB Browser. (1.0.1)

Impact: Since the Cisco 6100 MIB uses SNMP V2 Read-Create syntax extensively, the NNM 4.11 MIB Browser can only be used to view Cisco 6100 configurations.

Workaround: If setting MIB variables using a Browser is desirable, use a MIB Browser other than HP's NNM browser.


When changing a users password, the old password is not rejected as an invalid password. (2.2.0)

Impact: If, when changing a users password the old password is correctly entered, and the old password is also entered into the new password and new password confirmation field, the password is accepted.

Workaround: None


AlarmFormatter does not work through in-band. AlarmFormatter communicates with the node during trap receipt and alarm sync. However it does not know to use the in-band IP address since the Trap PDUs from in-band use the Ethernet IP address, and not the current specified comm address. (2.2.0)

Impact: This means that traps received through in-band when ethernet is not active will not be processed.

Workaround: Keep ethernet active.


Subtend connections fail to be created when the IP address of the head node is greater than the IP address of the leaf node. (2.2.0)

Impact: If an attempt is made to make a subtend connection with nodes whose IP addresses fail this test, the subtend group will need to be deleted. It may also be necessary to delete and rediscover the Cisco 6100s in the subtend group that was being created. The user should also check the MIB on the two Cisco 6100s to ensure that the lrSpId and the sysContact fields have been reset to " ".

Workaround: Until this is fixed, the workaround is to ensure that the head node of a new subtend group always has the lowest IP address in the subtend group. The second tier Cisco 6100s must have lower IP addresses than their leaf nodes as well.


New Subtend groups are identified by the IP address of the head node as opposed to the CLLI code of the head node.

Impact: All subtend groups will be identified by the IP address of the head node Cisco 6100.

Workaround: None


Subscriber PVC Window: Sorting on port is not correct. (2.3.0)

Impact: Chassis, slot, port sorting would be more useful

Workaround: None


Add User dialog doesn't update when wire center/location deleted. (2.3.0)

Impact: User may attempt to make available a wire center which no longer exists.

Workaround: Close Add User dialog and re-open.


Deleting multiple Cisco 6100s from a subtend group does not work. (2.3.0)

Impact: Subtend map is out of sync if multiple Cisco 6100s are deleted from it in one operation.

Workaround: Manually synchronize map by selecting head node and Synchronize this subtend group from the ViewMap Configuration menu.


Deleting multiple Cisco 6100s from a subtend group does not work (2.3.0)

Impact: Subtend map is out of sync if multiple Cisco 6100s are deleted from it in one operation.

Workaround: Manually synchronize map by selecting head node and Synchronize this subtend group from the ViewMap Configuration menu.


Subtend group not deleted when head node in holding area deleted. (2.3.0)

Impact: User must manually delete the subtend group icon.

Workaround: None


ViewAllSubscribers displays blank window in subtend view. (2.3.0)

Impact: Local subscribers not displayed under this rare circumstance

Workaround: Change scope to local.


SWD aborts when SC succeeds and other images fail (2.3.0)

Impact: If this condition occurs, and SC is reset, the current node configuration will be lost.

Workaround: If this condition occurs, do not reset SC manually, determine reason for TFTP failure, resolve condition, and download software again.


Ports total incorrect on Port Service Configuration window (2.3.0)

Impact: Total may be incorrect if module deleted while viewing Port Service Configuration window.

Workaround: Close and re-open window.


Validate (SWD/Rest) not abort when inband detected (2.3.0)

Impact: Since HP OpenView can rediscover an interface at any time, software download should not be performed on a machine which has both ethernet and inband active at the same time.

Workaround: To perform a download or restore to a node which has both interfaces active, disable the inband channel by locking (this will cause the node to go into Loss of Communications with ViewRunner). Next switch the communications channel indicated on the Cisco 6100 configuration panel to the Ethernet interface (this will restore communications to the node). Then proceed with Software Download or Restore.


Service state not updated in Port Service Config and Pool window (2.3.0)

Impact: Service state in these windows will not be up-to-date.

Workaround: Close and re-open Window.


Save/Restore/Download wizard will not queue any jobs after failure (2.3.0)

Impact: If the first node in a series fails, the user will have to press the wizard cancel button and attempt to perform the operation on those nodes again. The user can verify that this condition occurred by looking at the status, the first node will say failed, all other nodes will say pending. The unsuccessful count will be 1.

Workaround: Cancel operation and try again, leaving out the failed node (or resolving the condition which caused the first node to fail).


Selecting blank item in combo boxes causes ViewRunner chassis view to exit.

Impact: User must restart chassis view.

Workaround: None.


If HP OpenView 5.01 consolidated patch PSOV_02243 is installed, ovw exits when opening a ViewRunner Map.

Impact: ViewRunner cannot start.

Workaround: Uninstall HP OpenView patch PSOV_02243. We recommend you install HP OpenView patch PSOV_02091, if it is not already installed. This patch is no longer available on the HP Web site. HP permitted us to distribute the patch PSOV_02091 on the ViewRunner CD-ROM.


Installing the ViewRunner Database package CSCOvrdb for the first time on a machine with an existing Oracle database will incorrectly install ViewRunner Oracle database. The init.ora file of the original database is removed when running a pkgrm to remove the ViewRunner package.

Impact: If the tablespace exists with the same name it will add the ViewRunner tables to that tablespace, otherwise it will create new tablespaces for the ViewRunner tables. The install package will then run the Oracle Catalog scripts (catalog.sql, catproc.sql, catblock.sql, catexp.sql, plustrce.sql, and pupbld.sql). This could invalidate any existing PL/SQL procedures and cause a recompile.

Workaround: Create a separate Oracle instance and database for ViewRunner.


Significant number of "Reconnecting to server" messages seen. For example, "CM_019 Reconnected to ViewRunner Server." displays every three minutes. When using the distributed client/server configuration, heavy network traffic can cause this message to be displayed.

Impact: This message interrupts the work of the operator and disrupts a healthy network connection between the client and server workstations. It should not be displayed. If a significant number of these events occur, the source of the network delays or errors warrents investigation.

Workaround: This condition (heavy network traffic between client and server) can be detected by examining the log files for constant user re-logins. Increase the CLIENT_HEARTBEAT_CHECK_TIMEOUT in the vrconstants.conf file to 360 seconds or larger if necessary.


ViewRunner log files grow without bound on Trace Level 4, irrespective of the maximumTraceFileSize setting. (1.0.1)

Impact: NetMon process executing Trace level 4 grows rapidly, consuming 100+ KB every minute. Trace level 4 should only be run for short periods of time or else it will consume all available disk space and crash ViewRunner.

Workaround: Trace level 1 should be the normal operational setting unless a problem is being diagnosed.


Adding location symbol into World or Location submaps sometimes results in IP Map warning message. (1.0.1)

Impact: None - warning is due to a ViewMap operation and does not apply IP Map.

Workaround: Dismiss warning dialog and continue.


The LoopRunner Chassis View occasionally gets blacked out areas when it is opened with a window on top of it. (1.0.1)

Impact: Chassis view does not fully display

Workaround: Close and Reopen the View Cisco 6100 window.


Initially opening a System Dialog or subsequently expanding the scope to Subtend or Wirecenter should automatically invoke an Intelligent Config Sync (ICS) prior to (re)displaying the window.

Impact: System dialogs such as View All Subscribers and View Equipment Inventory may display incorrect data when they are initially opened or when their scope is expanded if ViewRunner is out-of-sync with the Cisco 6100's configuration due to another management system modifying the Cisco 6100 directly. Note that an ICS is automatically invoked every time a View Cisco 6100 chassis window is opened, and that must be opened prior to invoking any locally scoped Summary Dialog, so this problem is minor for locally scoped views. (2.2.0)

Workaround: Manually initiating a Config Synchronization prior to opening a locally scoped Cisco 6100 Summary Dialog guarantees data integrity. Be aware that Subtend/Wirecenter scoped Summary Dialogs may display incorrect data if another management system has modified those Cisco 6100s directly since the last time they were configuration synced.


If a trapSequenceNumber is written to the database but the corresponding NetMon service fails or does not get completed, Intelligent Config Sync will not properly sync the alarm. (2.2.0)

Impact: Menu driven synchronizations would not be able to synchronize the database with the Cisco 6100 alarm. This problem would correct itself if an out-of-sequence trap was received.

Workaround: Use vrPerformConfigSync to force a full config sync.


Subscriber Admin Status is displayed as Locked when in Loss of Communication (LOC) to the Cisco 6100. (1.0.1)

Impact: ViewRunner displays the incorrect Admin Status when in LOC.

Workaround: Admin status displays correctly once communication is restored to the Cisco 6100.


Starting View LoopRunner in True Color mode takes 30M of memory on X server. Current chassis bitmaps use a significant amount of X server resources when viewed in true color mode. (1.0.1)

Impact: True Color X Servers with limited memory may respond slowly due to operating system virtual memory swapping.

Workaround: Increase available memory in X Servers or run X Server in 256 color mode.


Guest Privilege 'Delete->From All Submaps' displays error "Permission Denied" but does not redisplay map symbols properly. (2.2.0)

Impact: A Guest user can delete a map symbol from his map, although the symbol is not deleted from the database. Note that no other User Maps are affected.

Workaround: Guest user should use 'Delete->From This Submap', which works properly. Exiting the map and re-open it will bring the symbol back into the Guest's map.


Active Connections totals area flickers badly when displaying Pool Window. (1.0.1)

Impact: Aesthetic.

Workaround: None.


Active Connections window sort slow and flickery. (1.0.1)

Impact: Aesthetic.

Workaround: None.


Subscriber PVC scope combo selection resizes dialog. (2.2.0)

Impact: Aesthetic.

Workaround: None.


Changing scope of View All Subscribers dialog resizes window. (2.2.0)

Impact: Aesthetic.

Workaround: None.


After getting wrong password msg., dialog for change password does not clear out wrong password. (2.2.0)

Impact: None.

Workaround: Delete incorrect *** password manually.


Restore system with pre-provisioned LCC fails in some cases (2.2.0)

Impact: If restoring an NSS file that contains an LCC and there is already a PRE-PROVISIONED LCC in the target Cisco 6100 with the same ID, then the LCC (modules, subscribers, and service provisioning) will not be restored. This is also a problem for SWD.

Workaround: For restore, run Restore 2 times with the same NSS file. No workaround for SWD.


The process seems to hang when an executable file is used instead of a valid NSS file. Status displayed as pending. No error displayed in Netmon log. Netmon executable was used. (2.3.0)

Impact: Servers may exit if a binary executable file is used as the NSS file instead of a valid NSS file.

Workaround: Only use valid NSS files for Cisco 6100 configuration restore.


Invalid NSS file not deleted when Save Configuration fails. (2.2.0)

Impact: Each time a Save is done, the oldest file is deleted. If Save configuration fails, eventually the only files remaining will be invalid (# of saved files is configurable)

Workaround: if Save Config fails delete the bad file manually.

8. Information from Previous Releases

The following are the new features introduced in previous releases of ViewRunner for HP OpenView.

8.1 New Features in Release 2.3.0

The new features supported in the 2.3.0 release of ViewRunner for HP OpenView are as follows

8.2 New Features in Release 2.2.0

The new features supported in the 2.2.0 release of ViewRunner for HP OpenView are as follows

9. Related Documentation

Use these release notes in conjunction with the following documents:

Note You can find the legacy Cisco 6100 documents at Click Technical Support.

10. Cisco Connection Online

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, description of service offerings, and download access to public and authorized files.

Note The current ViewRunner for HP OpenView documentation can be found on CCO. The legacy documents can be found at Click Technical Support.

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 For additional information, contact

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 To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or

For the latest information on caveats and known problems, follow these steps to consult CCO:

Step 1   Connect to CCO as directed in the section above.

Step 2   On the CCO home page, click LOGIN, which appears in green in the menu bar at the top of the page, and log into CCO. (If you are not a registered CCO user, follow the instructions to register so that you can log in.)

Step 3   After you log in, click Software & Support on the CCO home page.

Step 4   On the Software & Support page, click Technical Tools.

Step 5   On the Technical Tools page, click Bug Toolkit II. (Bug Toolkit II is not visible on the Technical Tools page unless you log in to CCO as directed in Step 2.)

Step 6   Use one of the tools to get up-to-date bug information. For example, click Search for Bug by ID Number, then enter a bug ID, such as CSCdk09616, when prompted. For instructions on using the bug tools, go to the bottom of the Bug Toolkit II page and click Help—How to Use the Bug Toolkit.

11. Documentation CD-ROM

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,, or

Note The current ViewRunner for HP OpenView documentation can be found on CCO. The legacy documents can be found at Click Technical Support.

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.

Posted: Sun Sep 29 00:34:19 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.