Release Notes for ViewRunner for
HP OpenView Release 2.4.0

2.4.0

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

2.3.5

No

No

Yes

Yes

Yes

Yes

Yes

Yes

2.3.0

No

No

Yes³

Yes³

Yes⁴

Yes

Yes

Yes

2.2.0

No

No

Yes⁵

Yes⁵

Yes⁵

Yes

Yes

Yes

CAP ATU-C, DMT-2 ATU-C

Circuit ID Field Activation

Provides more line and location detail for a particular subscriber. You can configure and display circuit ID for each subscriber. The circuit field accepts up to 20 characters. Valid characters include
A to Z, a to z, 0 to 9, {.,-=;:'#!$%&*()<>_+/\}.

DMT-2 ATU-C

ViewRunner for HP OpenView Support

Transmission rates:

• Downstream range from 32k to 8032k.
  
  
• Upstream range from 32k to 864k.
  
  
• Bit rates are determined by the number of carriers and the number of bits per carrier.
  
  

CAP ATU-C

DMT-2 ATU-C

Per-Subscriber Power Setting Transmittal

You can refine signal attenuation by setting power transmittal in DBm/Hz per-subscriber.

Configure transmit power attribute using the Subscriber Properties dialog box in the PSD Transmit Power field. Default values are

• Upstream: -38
  
  
• Downstream: -40
  
  

DMT-2 ATU-C

Interleaved Path Support¹

Default value is set to 16000 and the unit is microsecond.

Although you can configure interleaved values on the DMT-2 Subscriber Properties dialog box, the Interleaved latency option is the read-only default per subscriber on the Service Provisioning dialog box. The Interleaved setting cannot be changed. Delay options include: 0, 500, 1000, 2000, 4000, 8000, 16000, 32000, 64000. Delay settings 16000 to 64000 result in a maximum setting.

DMT-2 ATU-C

Training Mode

The read-only default is set to Standard Train.

CAP ATU-C

DMT-2 ATU-C

Priority Queue Support

You can configure the priority queue for each subscriber PVC through the Service Provisioning dialog box. The default Priority Queue setting is 3. You can also configure the priority queue for each transit subscriber PVC through the Transit Subscriber dialog box. A new header field labeled Priority displays priority in a list-box.

Values 1 through 3 represent queues. Queue usage follows these rules:

• Queue 1—Voice transfer
  
  
• Queue 2—Signalling
  
  
• Queue 3—Data Transfer
  
  

DMT-2 ATU-C

Performance Monitoring: Parameter and value

You can access the Parameter field in the DMT-2 Port Status dialog box to view performance counters such as HecVioll and FarCvflfe. Performance counters measure the DMT-2 port performance according to the following factors:

• Attenuation equations
  
  
• Signal-to-noise ratios
  
  
• Number of anomalies per interval
  
  
• Types of defects such as SEF or LPR
  
  
• Number of cells used
  
  

The Value field contains the value of the performance counter.

DMT-2 ATU-C

Forward Error Correction (FEC)

You can configure the number of redundancy bytes in both upstream and downstream. The default value is 16. The unit is bytes. Redundancy byte amount options range in multiples of two from 2 to 16.

DMT-2 ATU-C

Overhead Framing Structure

The default overhead framing structure value is 3. You can configure overhead framing according to the structure definitions and values below.

• Full asynchronous—Full overhead framing with asynchronous bit-to-modem timing (enabled synchronization control mechanism). Value = 0.
  
  
• Full synchronous—Full overhead framing with synchronous bit-to-modem timing (disabled synchronization control mechanism) Value=1
  
  
• Reduced separate fast—Reduced overhead framing with separate fast and sync bytes in fast and interleaved latency buffer respectively (64 kbits/s framing overhead) Value = 2
  
  
• Reduced merged fast—Reduced overhead framing with merged fast and dsync byte, using either the fast or interleaved latency buffer (32kbit/s framing overhead). Value=3
  
  

CAP ATU_C

DMT-2 ATU-C

Network Interface Module Information

You can determine the physical layer and the number of ports from the NI Module Port Configuration dialog box.

DMT-2 ATU-C

ATM virtual circuit support

Support for the ATM PVC is similar to the existing CAP ATU-C module. Subscriber provisioning is similar to the CAP ATU-C module, except for training rates.

Module and port tab icons

Module and port tab icon support is provided on the following modules:

• CAP ATU-C
  
  
• DMT-2 ATU-C
  
  

Persistent System Name/System Location

The 6100 Properties dialog box provides two new fields where you can enter the name and location of the system you are using.

Rules:

1. When the system is set up for the first time, the System Name and System Location fields are empty strings.

2. Field length for both fields is 255 characters.

3. To save the system name and system location variables, click Apply.

4. The system name and system location variables are restored each time you select the 6100 Properties dialog box.

6130 Chassis Fan Tray Present toggle

The 6100 Properties dialog box now allows you to indicate whether or not a chassis fan tray is present on a 6130 chassis by clicking a toggle.

Rules:

1. If you check the chassis Fan Tray Present toggle, the operational status of the fan tray will display on the 6130 Event History View as an event such as, "Fan tray detected."

2. Keywords in the FCM governing fan tray support and chassis revision are: CHASSISREV and FANTRAY.

Fan Tray Alarms

Two critical severity fan tray alarms now display.

MC Fan Failure—When you have checked the Fan Tray Present toggle on the 6100 Properties dialog box but a fan tray is not present, a critial alarm will display on the Current Alarms View dialog box.

MC Fan Required—When you have configured a module requiring a fan tray, such as the DMT-2 ATU-C module, and no fan tray can be detected, a critical alarm will display on the Current Alarms View dialog box.

Chassis operational state indicator

The operational state of the chassis is displayed in the upper right corner of the chassis in the Chassis View. The color used to indicate the chassis state conforms to the standard ViewRunner use of color.

Administrative state icons on 6100 Chassis View

The Cisco 6100 Chassis View supports administrative state icons that indicate module lock/unlock and port lock/unlock. The three different type icons are a lock shown in locked position, a lock shown unlocked, and a key. The module ejector tab color now indicates operation and preprovision status as follows:

• White—ViewRunner loss of communication with the Cisco 6100 node, but this module is present in the ViewRunner database.
  
  
• Blue—Module has been preprovisioned in the chassis.
  
  
• Green—The module and all of its ports ar in normal operational state.
  
  
• Yellow—Outstanding alarm (minor) on the module or any of its ports.
  
  
• Orange—Outstanding alarm (major) on the module or any of its ports.
  
  
• Red—Outstanding alarm (critical) on the module or any of its ports.
  
  

Scoped Subtend Hierarchy Enhancements

Out of the three subtend modes of operation: local, wire center, and subtend group, the subtend group is now called scoped subtend. The scoped subtend provides a new subtend view from the current node selection and down.

Save summary dialog to file

The summary dialogs boxes, View All Subscribers and View All Subscriber PVCs can be saved to a file.

Configuration restore enhancements

This feature allows separation of configuration restore and image restore and supports configuration-only restore. A wizard screen has two new check boxes and a new save as default button. One check box is for configuration restore and the other is for image restore to allow you to restore either or both. The check box option is configurable with the vrconstant file.

HPOV 4.11

HPOV 5.x

Oracle 7.3.2

yes

no

Oracle 7.3.3

yes

no

Oracle 7.3.4

yes

yes

CSCne02427

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.

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.

CSCdm53158

Errors in Restore are not always reported in wizard.

Impact: Under extremely rare circumstances, the software download may encounter unexpected SNMP errors, even though the software download wizard may report a successful software download. The SNMP errors are reported in the vrNetMon.log file found in the $VRS_HOME/log directory.

Workaround: If errors are suspected, examine the vrNetMon.log files for more detail.

CSCdm47116

ViewRunner package removal didn't remove all files from OpenView

Impact: Not all of the ViewRunner OpenView files and entries are removed when the ViewRunner for OpenView packages are removed under Solaris 2.6. The following list contains the files and entries which may be left behind.

1. /var/opt/OV/share/snmp_mibs/Vendor/NetSpeed/looprunr.mib
/var/opt/OV/share/snmp_mibs/Vendor/NetSpeed/lrtraps.mib
/var/opt/OV/share/snmp_mibs/Vendor/NetSpeed/netspeed.mib.ov
and directory /var/opt/OV/share/snmp_mibs/Vendor/NetSpeed

2. The entry below is still in /etc/opt/OV/share/conf/oid_to_sym

#CiscoDSL Equipments BEGIN CONFIG
1.3.6.1.4.1.1871.2.1.1.1.1:CiscoDSLAM:Cisco6100
# Cisco 6100 DSLAM
#CiscoDSL Equipments END CONFIG

3. /opt/OV/share/symbols/C/vr_symbols
/opt/OV/share/symbols/C/vr_types
/opt/OV/share/registration/C/viewrunner.reg
/opt/OV/share/fields/C/vr_fields
/opt/OV/share/bitmaps/C/NetSpeed
/opt/OV/share/bitmaps/C/LoopRunner

Workaround: Manually remove the remaining files and entries.

CSCdm46175

Core file created in $VRS_HOME/log when vrStop is used.

Impact: Under rare circumstances, a core file may be generated when using vrStop to stop the ViewRunner for HP OpenView servers.

Workaround: None. The behavior has no negative impact on the system configuration or performance.

CSCdm45510

CSCOvrovs installed on multi-homed box causes environment error.

Impact: The installation of CSCOvrovs on a workstation with multiple network interface cards will by default assign the first IP address to the TFTP_IP_ADDRESS and cause the generated vrs.cshrc and vrs.ksh files to have an invalid file format.

Workaround: Change option A in the installation menu to the single IP address for the environment variable.

CSCdm31092

Locked inband management PVC prevents reuse of the PVC.

Impact: If an inband management PVC is locked, the same PVC cannot be used for subscribers. Currently there is no way to delete an inband management PVC. ViewRunner for HP OpenView allows the same PVC to be reused for subscribers. Therefore, if ViewRunner for HP OpenView assigns the inband PVC to a subscriber, ViewRunner for HP OpenView still shows the PVC as being used by both inband management and the subscriber.

Workaround: None.

CSCdm24448

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.

CSCdm14374

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.

CSCdm08635

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.

CSCdk72349

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

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).

CSCdk71267

Validate (SWD/Rest) not abort when inband detected

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.

CSCdk71198

Ports total incorrect on Port Service Configuration window

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

Workaround: Close and re-open window.

CSCdk68697

SWD aborts when SC succeeds and other images fail

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.

CSCdk65379

ViewAllSubscribers displays blank window in subtend view.

Impact: Local subscribers not displayed under this rare circumstance

Workaround: Change scope to local.

CSCdk65378

Subtend group not deleted when head node in holding area deleted.

Impact: User must manually delete the subtend group icon.

Workaround: None

CSCdk65277

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

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.

CSCdk64818

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

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

Workaround: Close Add User dialog and re-open.

CSCdk64405

Subscriber PVC Window: Sorting on port is not correct.

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

Workaround: None

CSCdk45259

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

CSCdk43961

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

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.

CSCdk42961

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.

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

Workaround: Keep ethernet active.

CSCdk42799

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

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

CSCdk42798

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

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.

CSCdk42678

ViewLoopRunner occasionally dumps core while opening 6100 Properties window.

Impact: 6100 Chassis view must be restarted.

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

CSCdk42366

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.

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.

CSCdk42107

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.

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.

CSCdk42081

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

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.

CSCdk41837

ViewMap shows wrong message: Subtending LoopRunner X to LoopRunner X.

Impact: ViewMap Log message may be confusing.

Workaround: None.

CSCdk41773

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.

Impact: The Event Browser displays a vague error message.

Workaround: none

CSCdk40704

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

Impact: Configuration completes with the current changes

Workaround: None

CSCdk40690

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

Impact: None

Workaround: Manually sort the window.

CSCdk40676

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

Impact: None

Workaround: None

CSCdk39777

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

Impact: Subscriber is added.

Workaround: N/A

CSCne02435

Invalid NSS file not deleted when Save Configuration fails.

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.

CSCne02425

Restore system with pre-provisioned LCC fails in some cases

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.

CSCne02315

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

Impact: None.

Workaround: Delete incorrect *** password manually.

CSCne02230

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

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.

CSCne02138

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.

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.

CSCne01802

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

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

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

CSCne01801

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.

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.

CSCne01735

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

Impact: Chassis view does not fully display

Workaround: Close and Reopen the View Cisco 6100 window.

CSCne01597

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

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

Workaround: Dismiss warning dialog and continue.

CSCne00984

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

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.