|
December 9, 1998
These release notes discuss features, resolved problem reports, and unresolved problem reports for the ViewRunner for HP OpenView 2.3.0 release.
For more detailed information about the features in these release notes, refer to the "Related Documentation" section. Information about electronic documentation can be found in the "Cisco Connection Online" section, and in the "Documentation CD-ROM" section.
These release notes discuss the following topics:
ViewRunner for HP OpenView 2.3.0 serves as the Carrier Class Element Management System (EMS) for the Cisco 6100. ViewRunner for HP OpenView 2.3.0 and ViewRunner for Windows 2.3.0 support roughly equivalent 6100 capability.
The ViewRunner for HP OpenView 2.3.0 release supports the following Cisco 6100 releases:
The primary fixes contained in this release are:
The new feature in ViewRunner for HP OpenView 2.3.0 are as follows
The CPE detection feature is used to discover CPE gear that is not capable of performing Idle or Session timeouts when CPE Detection is enabled. During training, the CPE detection feature determines whether or not the CPE equipment can be timer enabled. If the equipment can be timer enabled, then training continues. If the equipment cannot be timer enabled, an alarm is generated in the ViewRunner. The subscriber line port will be Out of Service while the alarm is asserted. After an hour, the alarm will clear allowing the CPE equipment to attempt to train again.
The 136K Baud training rates now can be enabled or disabled through a system wide MIB object. If the 136K Baud training rates are disabled, then those selections will be grayed out in ViewRunner and thus not selectable by the user.
The user can configure various subscriber defaults in this release. The user can set the following:
The parameters for setting these are in the vrconstants.conf file.
The following is an important caveat for ViewRunner for HP OpenView 2.3.0.
The problems listed in Table 1 are resolved in ViewRunner for HP OpenView 2.3.0.
PR Number | Description |
---|---|
CSCdk40747 | View Map log window for read only map not updating. (Beta 1) |
CSCdk41743 | Image associations and swRelease not updated (Beta 1) |
CSCdk41745 | ViewRunner does not detect that images are deleted using a MIB Browser. (Beta 1) |
CSCdk41747 | ViewRunner Software Download (SWD) pauses after "Validate was successful" message. This occurs very infrequently. (Beta 1) |
CSCdk41769 | Subscribers configured with one of the 136 KBaud rates will be lost during Software Download (SWD) from 6100 2.2.0 to 2.1.2. (Beta 1) |
CSCdk42223 | Sync Subtend Group doesn't discover 2 level deep LoopRunners. This condition only occurs when the 6100's which are participating in the subtend group have not been added to the system prior to selecting the Synchronize This Subtend Group command. (Beta 1) |
CSCdk42261 | When VR4OV receives a duplicate alarm that is already asserted, the alarm gets added to the database. The old alarm should be moved to the alarm history table and the new alarm added to the alarm table. (Beta 1) |
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. (Beta 1) |
CSCdk42626 | ViewMap log window not displaying Loss of Communication messages. (Beta 1) |
CSCdk42628 | Cut/Paste a subtended or subtending LoopRunner from one Subtend Group into another is denied but the LoopRunner which is cut is moved into the new object holding area. The expected behavior is the LoopRunner should be placed in the main area of the submap showing the actual subtend relationship. This problem is occurring in only the OVW session where actual cut/paste is done. The another Read-Write session continue to show the subtend relation. Database has the subtend relation. (Beta 1) |
CSCdk42754 | SNMP error reported when pre-provisioning an ATU-C in a direct connect system. (Beta 1) |
CSCdk42783 | View 6100 chassis and Property Dialogs do not always get focus and open to the front of other windows. Sometimes another window pops up in front of the window that is opening. The chassis view does not always get focus. (Beta 1) |
CSCdk45108 | When logged in as guest, deleting a subtend connection gives an error message saying that the operation is not allowed, however the object is removed from the screen anyway. (Beta 1) |
CSCdk45184 | Guest user is allowed to perform several subtend related operations: Remove 6100 from subtend group, Create Subtend connection, and Add 6100 to Subtend Group (Beta 1) |
CSCdk45321 | Image alarms not cleared after alarm synch (Beta 1) |
CSCdk45398 | Cutting and Pasting 6100's from a wirecenter into a subtend group removes the 6100 from the wirecenter. (Beta 1) |
CSCdk45403 | When making a subtend connection which causes the subtend tree to be more than 3 levels deep, the connection is made but not displayed in the subtend group map. (Beta 1) |
CSCdk45404 | Performing subtend operation when logged in as an operator does not work as expected. Gives "Permission Denied" error even when the operator has access to the wirecenter. (Beta 1) |
CSCdk45960 | Chassis View disappears occasionally when viewing 6100 properties window. (Beta 1) |
CSCdk48316 | Inband node discovered by HP Openview does not get added to ViewRunner New Equipment Window. (Beta 1) |
CSCdk48634 | Subtend group icon is not removed when all the 6100 nodes have been removed from the subtend group. (Beta 1) |
CSCdk48639 | Trying to copy/cut & paste subtended looprunners from a subtend group into a subtend location gives an error (correct behavior), but removes the connections and moves the looprunners to the holding area in its subtend group. On performing a subtend synch, the looprunners are put back in the subtend group. * Create a subtend group with n equipments in connection. * Copy/Cut and paste the subtend looprunners from the subtend group into a subtend location. * Error dialog is displayed which says "Object cannot be moved here". However all the looprunners in subtend group are moved to the holding area. [The connections are still present in the database and on the node]. (Beta 1) |
CSCdk48844 | If a user tries to make second subtend connection between two subtend connected 6100s using Edit -> Add Connection menu, he will get an error message "Object cannot be added here" and the earlier subtend connection on the map is removed. If a user tries to make second subtend connection between two subtend connected 6100s using Edit -> Add Connection menu, he will get an error message "Object cannot be added here" and the earlier subtend connection on the map is removed. (Beta 1) |
CSCdk48853 | Test Case VMap-1470 section 19.9.13 (ViewMapDVT_ver1.12) Making subtend connections across submaps fails under the following conditions: 1. Subtend an LR (LR1) in the holding area and to another LR (LR2) which is already subtended. The connection is made but LR1's group is not changed. Subtend sync does not help. 2. Subtend headnode (LR1) of one group to another LR (LR2) in new equipment window. New subtend group with LR2 is not created. LR2 is not added to any subtend group. Database is updated with subtend connection details only. After subtend sync of LR1, LR2 are moved to LR1's subtend group. No new group is created with LR2 as group name. (Beta 1) |
CSCdk48861 | When multiple subtend connections are selected on the subtend group submap and then they are deleted using Edit -> Delete menu, only the first the connection selected will be deleted and the user gets an error dialog "Service failed at Server PM_030 Another subtend service is in progress". (Beta 1) |
CSCdk50065 | Synchronization of subtend connections which are cyclic are not determined to be cyclic if there is no subtend connection on port 1 of the 6100s Subtend module. (Beta 1) |
CSCdk50067 | 6100s which are currently connected in a subtend group can not be removed from the subtend group without first deleting the subtend connection. (Beta 1) |
CSCdk50088 | After syncing a subtend group with stray LoopRunners, if the current subtend group is destroyed all the stray LoopRunners should be removed from their subtend group and they SHOULD not be moved into any subtend group. (Beta 1) The possible cases: 1. Deleting a head node. 2. Subtending head node to another node. (?) |
CSCdk50091 | ViewRunner did not display the correct subtend relationships after connecting a 6100 which was already a head node of a subtend group, as the child node of another 6100. (Beta 1) |
CSCdk50096 | ProcessMon sometimes dumps core when subtend operation times out and while sending error message to client, the client structure contains invalid data. (Beta 1) |
CSCdk52113 | The Actual Upstream Rate and Actual Upstream Margin values are displayed incorrectly as 12 kbps and 0 dB respectively. (Beta 1) |
CSCdk55404 | After deleting the head node of a subtend group, an attempt to create a new subtend group with the node fails, saying that the 6100 is already subtended. (Beta 1) |
CSCdk57080 | ChassisView continues to display ejector tabs in LOC colors even when ViewRunner is able to communicate with the 6100. (Beta 1) |
CSCdk57083 | LoopRunner Config Panel does not grey the ServiceType button and allows mode change even when unlocked modules are present in the 6100. The 6100 is in Direct Connect Mode. (Beta 1) |
CSCdk57099 | Restoring the configuration of a 6100 in Direct Mode fails. Gives the following error "Invalid NSS File format" (Beta 1) |
CSCdk57662 | When a configuration sync is performed on a 6100 that has a minimal configuration, but the database configuration is a fully equipped 6100, the netmon process will get a "too many open cursors" Oracle error when trying to update the database. As far as I know this does not leave the database in a corrupted state. The problem may be rectified by adding the following line to the initvrunner.ora file:
|
CSCdk58414 | Software download clears traps are sent when netmon starts, the download wizard should process these, and for any download operation that is in progress, it should mark ar errored (generally this will indicate that Netmon restarted while the download was in progress. (Beta 1) |
CSCdk58663 | Netmon core dumps during software download. This occurs when software download (with no save/restore) is performed repeatedly. Looks like some memory corruption. (Beta 1) |
CSCdk58676 | View Hardware Revisions/Image Revisions window displays some junk value for image date when the image date is NULL in the database. This occurs when the window is opened after software download in which save/restore is not performed i.e. various images other than SC is downloaded. This condition will show up only if a config sync is not performed during/after software download. This is because image information is not being retrieved after images are tftp'd. Component: Dbinterface (Beta 1) |
CSCdk59108 | Image information in the database is incorrect when config sync is not performed as a part of SWD. This occurs when SC image is not downloaded as a part of SWD. (Beta 1) Conditions: 1. Image date does not get updated in the db for the images tftp'd. 2. Image index in the node and the db vary. Reason: 1. Condition 1 occurs because read only image information i.e. image date is not retrieved after the image is added. 2. Condition 2 occurs because config sync is not done when SC is reset during SWD. Because of reset the image index in the node gets changed but database still has the index with which the image was added to the node. |
CSCdk59162 | There have been isolated reports of software download failures when the /tftpboot directory is not linked to itself when a Solaris 2.5.1 system is being used as the TFTP server. (Beta 1) |
CSCdk59990 | Route window does not display agent reported errors. (Beta 1) |
CSCdk60958 | DataCollector uses the systemID and not commAddress for communication with the node. (Beta 1) |
CSCdk60972 | Save service is not performed when save is invoked after software download is started. Software download is completed successfully. Services performed after this are done. However the Save wizard still shows "In progress". (Beta 1) |
CSCdk63269 | Service State for an STM port is not displayed in the port status panel of STM module. (Beta 1) |
CSCdk63397 | In 6100 Properties Window, "6100 Date" Label is shown as "6100 Time" and "6100 Time" Label is shown as Time. Also, in the window title, 6100 is read as LoopRunner. (Beta 1) |
CSCdk63407 | In the 6100 Properties window, after changing the fields in Configuration panel if the tab is changed to Status panel and back to Configuration Panel, all the fields are refreshed except the Date and Time fields. Either refreshing the fields or not should be consistent across all fields. (Beta 1) |
CSCdk63649 | Line Port AID is not displayed fully for some line ports. LCC15 Slot19 Port1 is displayed as LCC15 Slot19 Port etc. (Beta 1) |
CSCdk63753 | In trap recipients window, if system wide authentication traps is disabled, the error message displayed is incorrect. 1. there should space between "any" and "trap". 2. there should a question mark at the end of the message. For reference, the current message shown is "Disabling system wide authentication traps will prevent any trap recipients from receiving authentication traps. Are you sure you want to disable system wide authentication traps." (Beta 1) |
CSCdk64086 | Open any system dialog and set the scope to Subtend Group. Change the 6100 subtend group form one to another, after two or three subtend group changes for the system dialog doesn't refresh automatically. (Beta 1) |
CSCdk64093 | Deleting the head node in a subtend group does not create 2 new subtend groups with the other 6100's in the group. This works when the 6100 is removed using 'Configuration -> Remove from subtend group' menu. (Beta 1) |
CSCdk64105 | Other read-write maps not refreshed when 6100 deleted. (Beta 2) |
CSCdk64417 | Subtend Sync LoopRunner creating a new subtend group. (Beta 2) |
CSCdk64595 | Setting lrSpId to an equipment that is not a 6100 does not work. (Beta 2) |
CSCdk64830 | On deleting user account, sessions are not closed for that user. (Beta 2) |
CSCdk65121 | Default inband channel and route cause message in Restore Wizard. (Beta 2) |
CSCdk65228 | Admin State for transit subscribers not displayed. (Beta 2) |
CSCdk65262 | PVC total not updated when the PVC for Inband is added. (Beta 2) |
CSCdk65268 | PVC Window: For VPC type PVCs, VCI part is shown as 0. (Beta 2) |
CSCdk65276 | Subscriber Property: Margin set to 0 is reset to default value. (Beta 2) |
CSCdk65351 | Unable to configure inband after setting a value which already exist. (Beta 2) |
CSCdk65690 | ViewRunner reports incorrect node name in alarm window after change. (Beta 2) |
CSCdk65695 | Adding PSC chassis causes general SNMP error & config sync. (Beta 2) |
CSCdk65760 | Validate Failure messages not appearing. (Beta 2) |
CSCdk65777 | PKG - VRSERVER installation can fail. (Beta 2) |
CSCdk65789 | Restore with different chassis IDs from installed equip. can fail. (Beta 2) |
CSCdk66143 | More than 1 hwRev missing from NSS not reported. (Beta 2) |
CSCdk66211 | NetMon core dumps in ValidateSWDownloadService sometimes. (Beta 2) |
CSCdk66779 | ProcessMon dumps core when there is cyclic subtend connection. (Beta 2) |
CSCne00984 | ViewRunner log files grow without bound on Trace Level 4, irrespective of the maximumTraceFileSize setting. (Beta 1) |
CSCne01800 | 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. (Beta 1) |
CSCne02240 | Summary Views (e.g. View Equipment Inventory) scoped to 'WireCenter' do not get dynamically updated when the wirecenter or location is deleted. (Beta 1) |
CSCne02251 | Subscriber PVC scope combo selection does not set busy cursor quick enough. (Beta 1) |
CSCne02283 | Config Sync status message sometimes not cleared when a manual (Intelligent) Config Sync is invoked prior to the current one completing. (Beta 1) |
The problems listed in Table 2 are open in ViewRunner for HP OpenView 2.3.0.
PR Number | Description |
---|---|
CSCdk64405 | Subscriber PVC Window: Sorting on port is not correct. (Beta 2) Impact: Chassis, slot, port sorting would be more useful Workaround: None |
CSCdk64818 | Add User dialog doesn't update when wire center/location deleted. (Beta 2) Impact: User may attempt to make available a wire center which no longer exists. Workaround: Close Add User dialog and re-open. |
CSCdk65277 | Deleting multiple 6100s from a subtend group does not work. (Beta 2) Impact: Subtend map is out of sync if multiple 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. |
CSCdk65378 | Subtend group not deleted when head node in holding area deleted. (Beta 2) Impact: User must manually delete the subtend group icon. Workaround: None |
CSCdk65379 | ViewAllSubscribers displays blank window in subtend view. (Beta 2) Impact: Local subscribers not displayed under this rare circumstance Workaround: Change scope to local. |
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. (Beta 1) 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 6100 configuration restore. |
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. |
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. |
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 6100 configuration panel to the Ethernet interface (this will restore communications to the node). Then proceed with Software Download or Restore. |
CSCdk71347 | Service state not updated in Port Service Config and Pool window Impact: Service state in these windows will not be up-to-date. Workaround: Close and re-open Window. |
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 occured 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). |
CSCdk65277 | Deleting multiple 6100s from a subtend group does not work Impact: Subtend map is out of sync if multiple 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. |
The problems listed in Table 3 are resolved in ViewRunner for HP OpenView Release 2.2.0.
PR Number | Description |
---|---|
CSCdk38470 | AlarmFormatter cant write DB when alarm ID too large |
CSCdk42678 | ViewLoopRunner occasionally dumps core while opening 6100 Properties window. |
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. |
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. |
CSCne00681 | View LoopRunner should use a single window per LoopRunner chassis |
CSCne00927 | ipmap failure |
CSCne00938 | Opening/closing Subscriber Provisioning window needs busy mouse icon |
CSCne01310 | Pool Configuration dialog - multi-selection using CTRL or SHIFT no longer works |
CSCne01396 | Set Initial Password button is active with out having a user. |
CSCne01410 | LoopRunner Properties - Need a new method for setting the Date/Time |
CSCne01426 | CLLI Code updates not being broadcast |
CSCne01476 | Stopping Oracle database causes critical problems |
CSCne01479 | Data not displayed after mult. refreshes. |
CSCne01489 | Subscriber ID not in Subscriber Window title bar |
CSCne01490 | The performance window is blank |
CSCne01491 | Get No Response From Server on ViewAllSubscribers window |
CSCne01495 | No Response from Server error message received while deleting a logical pool |
CSCne01496 | No Response from Server error message received while deleting an LCC |
CSCne01498 | Equipment Inventory not updated when status is refreshed |
CSCne01499 | Add new user window opens very slowly. |
CSCne01500 | Wrong dialog window opened for right mouse click on Active Connections. |
CSCne01501 | Wrong dialog msg. displayed for assigning a PVC a second time. |
CSCne01502 | Subscriber Preprovison allow user to try and add a fifth PVC. |
CSCne01504 | Logging in as a disabled user without a password should not prompt for a new password |
CSCne01507 | Administrators are able to add equipment to restricted wire centers |
CSCne01516 | Cursor should change to an hourglass during manual LoopRunner addition |
CSCne01520 | Login screen should have initial focus set to User ID text edit field |
CSCne01522 | Password fields should be reset on entry |
CSCne01523 | Error dialog for insecure passwords should be given when password dialog is closed |
CSCne01525 | Add password warning dialog should include the password confirmation screen |
CSCne01526 | Multiple cursors showing up on dialogs |
CSCne01527 | Double-clicking a user in the user admin list should open the modify user dialog |
CSCne01530 | VrProcessMon should restart OpenView if it dies |
CSCne01531 | VrProcessMon should restart the Oracle database if it dies |
CSCne01532 | Deleting LoopRunner from ViewRunner did not remove it from the database |
CSCne01533 | LoopRunner not being added to View Map upon discovery |
CSCne01534 | Active Connections Window - Top section should list LPOOLS in sorted order |
CSCne01538 | Subscriber Configuration window should set focus to Subscriber Id edit field |
CSCne01539 | No feedback that subscriber has been added |
CSCne01543 | PVC delete button should be dimmed if no PVC selected in list |
CSCne01550 | Got Blank Error Window on Exiting viewLoopRunner application |
CSCne01560 | All Subscribers dialog column label should be "Admin State" not "Admin Port" |
CSCne01564 | Options grayed out in menu should also be grayed out in Mouse right click. |
CSCne01566 | Security menu lists both login and logout options |
CSCne01568 | Noise Margin should display +6 dB. |
CSCne01570 | Drilling down through dialogs causes previous dialog to reposition |
CSCne01577 | Attempting to delete a module from LCC 5 Slot 22 resulted in a loss of comm error |
CSCne01580 | Received multiple "Request Timed Out" errors while trying to delete chassis |
CSCne01581 | after auto config sync, All Subscr dialog not updated correctly |
CSCne01589 | Non-functional LoopRunner may be added to a domain if non-unique IP addr is used and a warning ignored. |
CSCne01603 | Add/Modify User screen exhibits redraw flicker when displayed. |
CSCne01606 | Performance dialog not getting all data from node |
CSCne01610 | Warning messages in console window |
CSCne01614 | Can not delete a Location from the World Map. |
CSCne01620 | LCC1 chassis was deleted message incorrect |
CSCne01627 | View Alarm Formatter dumped core in TraceObject::TraceLevel3 |
CSCne01628 | ovtopmd repeatedly dumps core |
CSCne01630 | IP Map displaying wrong icon for LOC |
CSCne01631 | LOC listed 2 times in Module Status dialog |
CSCne01632 | config sync never executed when NetMon killed |
CSCne01633 | Object gets deleted, but symbols do not. |
CSCne01634 | Operator inherits Admin user profile. |
CSCne01635 | User with no privileges able to create new symbol on root map. |
CSCne01676 | IP Address and subnet mask are not displayed on SC Configuration Panel |
CSCne01725 | Delete Module should be dimmed if module is unlocked |
CSCne01727 | User should not be able to leave CLLI code blank |
CSCne01867 | Initial focus not on login ID field when ovw is started |
CSCne01875 | Busy cursor is not displayed until the endo of the operation |
CSCne01877 | Locking NI/LCM module does not display second confirmation dialog |
CSCne01888 | Loss of Communication alarm not cleared from the database |
CSCne01999 | View LoopRunner takes more than 10 minutes to start on client workstation |
CSCne02008 | Loss of Comm handling is inconsistent |
CSCne02050 | vrNetMon Core Dumps |
CSCne02061 | ViewRunner Table Indexes are in System Tablespace |
CSCne02082 | viewMap Crashes |
CSCne02107 | Adding an non-looprunner as looprunner |
CSCne02152 | Alarms are not shown in module window until refresh is done. |
CSCne02154 | ViewAdmin displaying unnecessary error dialogs |
CSCne02157 | Loss of Communication message is not shown when config sync is done |
CSCne02179 | Subscriber admin status is not set correctly. |
CSCne02190 | Config Sync not performed when a pvc of a deleted subscriber is deleted. |
CSCne02206 | Subscriber PVC list updates slowly |
CSCne02226 | ViewMap dumped core when moving WC to World |
CSCne02272 | ViewMap doesnt verify lengths of LR string attributes. |
CSCne02309 | Deleting the #2 logical pool of 3 pools, leaves 1 & 3 displayed and not 1 & 2 |
CSCne02410 | Need 6100 IP address added to information on 6100 Prop Config Panel |
CSCne02418 | Deleting last PVC from subscriber dose not remove View Subscriber PVC window entry |
CSCne02441 | Detecting LOC due to 6100 CV SNMP messages doesnt update module ejector tabs White. |
The problems listed in Table 4 are open in ViewRunner for HP OpenView Release 2.2.0.
PR Number | Description |
---|---|
CSCdk39777 | A Subscriber with a NULL ID may be configured regardless of user privilege level. Impact: Subscriber is added. Workaround: N/A |
CSCdk40676 | Edit button enabled when no transit subscriber selected regardless of user privilege level. Impact: None Workaround: None |
CSCdk40690 | Configuring subscriber does not update sorting of View All Subscriber window. Impact: None Workaround: Manually sort the window. |
CSCdk40704 | Configuration changes allowed if permission are changed after the configuration dialog is opened. Impact: Configuration completes with the current changes Workaround: None |
CSCdk40747 | View Map log window for read only map not updating. Impact: Popup messages are notifying Read-only map users of map Location changes. However, Read only map users cannot look at the ViewMap Log to determine adds/deletes/moves of map locations, wirecenters, and 6100 symbols. Workaround: Use Map->Refresh Map menu option to manually update Read only maps when suspected of being out of sync. |
CSCdk41743 | Image associations and swRelease not updated Impact: System Software Revisions dialog not correct after Software Download if the RDF being applied does not change the SC image. Workaround: If the SC image is not changed, then follow Software Download with manually initiated config sync. The window will display correct Image associations and swRelease after the Config Sync. |
CSCdk41745 | ViewRunner does not detect that images are deleted using a MIB Browser. Impact: Images deleted using MIB browser causes problems with Software Download Workaround: The ViewRunner Software Download process automatically handles image deletion as needed. ViewRunner is the only tool that should be used to Upgrade Software in the 6100. |
CSCdk41747 | ViewRunner Software Download (SWD) pauses after "Validate was successful" message. This occurs very infrequently. Impact: The 6100 is not affected - no Set messages get sent to the node. Software Download stops and must be restarted. Workaround: Cancel SWD and Restart SWD. This typically clears up the problem. Occasionally, however, the ViewRunner servers must be stopped and restarted to get past this situation. |
CSCdk41769 | Subscribers configured with one of the 136 KBaud rates will be lost during Software Download (SWD) from 6100 2.2.0 to 2.1.2. Impact: Subscriber configuration and service provisioning information gets lost during Software Downgrade. Workaround: Configure subscribers with a bit rate that is valid for 2.1.2 before the SWD. |
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 |
CSCdk41837 | ViewMap shows wrong message: Subtending LoopRunner X to LoopRunner X. Impact: ViewMap Log message may be confusing. Workaround: None. |
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 logfiles may be viewed to see these detailed error messages. |
CSCdk42107 | Deleting a subtending 6100 (a 6100 whose STM ports are connected to NI's of other 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 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 OpenViews 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. |
CSCdk42223 | Sync Subtend Group doesnt discover 2 level deep looprunners. This condition only occurs when the 6100's which are participating in the subtend group have not been added to the system prior to selecting the Synchronize This Subtend Group command. Impact: Synchronize this Subtend Group will fail if more than half of the nodes have not already been added to the system, synchronizing a second time (after the failure message is displayed) will work correctly. Workaround: 1) Make sure all nodes have been added to ViewRunner before synchronizing subtend groups, or 2) Issue Synchronize command a second time when this failure occurs (if the failure occurs a second time it may indicate the inability to communicate with one or more of the subtended nodes, this should be investigated and resolved before trying to subtend synchronize a third time. |
CSCdk42261 | When VR4OV receives a duplicate alarm that is already asserted, the alarm gets added to the database. The old alarm should be moved to the alarm history table and the new alarm added to the alarm table. Impact: Multiple instances of the same alarm may be displayed on alarm windows. This situation results in the number of outstanding critical/major/minor alarms displayed being different Than is actually asserted against the 6100 Workaround: When the alarm clears, all instances of the alarm get cleared. |
CSCdk42626 | ViewMap log window not displaying Loss of Communication messages Impact: Read only map users cannot look at the ViewMap Log to determine 6100 LOC conditions. Workaround: Use Map->Refresh Map menu option to manually update Read only maps to get an up-to-date snapshot of 6100 communication status. |
CSCdk42678 | ViewLoopRunner occasionally dumps core while opening 6100 Properties window. Impact: 6100 Chassis view must be restarted. Workaround: Right click on the 6100 map symbol and select View 6100 Chassis to restart |
CSCdk42783 | View 6100 chassis and Property Dialogs do not always get focus and open to the front of other windows. Sometimes another window pops up in front of the window that is opening. The chassis view does not always get focus. Impact: Annoyance since it may seem like the window doesn't open or the window is difficult to find. Workaround: None. |
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 |
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. |
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 6100s in the subtend group that was being created. The user should also check the MIB on the two 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 6100s must have lower IP addresses than their leaf nodes as well. |
CSCdk45108 | When logged in as guest, deleting a subtend connection gives an error message saying that the operation is not allowed, however the object is removed from the screen anyway. Impact: Subtend map operations (such as deleting subtend connections) which are not allowed by the users permissions do not automatically refresh the maps after the error message is displayed. So even though the objects still exist they are not displayed until the user forces the map to refresh. Workaround: There are 2 ways to force the subtend group map to refresh: 1. Select the head node and then select synchronize this subtend group. 2. Logout of ViewRunner and log back in. (But you do not have to exit OpenView) |
CSCdk45184 | Guest user is allowed to perform several subtend related operations: Remove 6100 from subtend group, Create Subtend connection, and Add 6100 to Subtend Group Impact: This only occurs when logged in as a guest user, and performing subtend addition type operations. Any destructive operations (such as delete) will not be allowed. 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 6100. Workaround: None |
CSCdk45321 | Image alarms not cleared after alarm synch Impact: AlarmFormatter does not reflect the correct image alarm status even after an alarm sync is performed. Workaround: All the alarms will be cleared on cold trap. Image alarms not cleared after alarm synch |
CSCdk45398 | Cutting and Pasting 6100's from a wirecenter into a subtend group removes the 6100 from the wirecenter. Impact: HP OpenView considers all cut operations a delete. This work well when cutting 6100s from wire centers and pasting into wire centers. However when pasting 6100s into subtend groups, the original 6100 symbol needs to stay in the wirecenter map (as well as being added to the subtend map) Workaround: Only use copy and paste when adding 6100s to subtend group maps. |
CSCdk45403 | When making a subtend connection which causes the subtend tree to be more than 3 levels deep, the connection is made but not displayed in the subtend group map. Impact: Subtend connections are only supported to a level of 3 deep. When making a connection that is greater than 3 levels no warning message is displayed, and the operation is performed even though it is not supported. Workaround: Do not connect 6100s deeper than 3 levels. |
CSCdk45960 | Chassis View disappears occasionally when viewing 6100 properties window. Impact: When 6100 properties window is opened multiple times while 6100 properties requests are still outstanding, the outstanding request timer is overwritten and the application may abort. Workaround: When opening 6100 properties window, wait for busy cursor to return to normal before dismissing the window or changing which tab is displayed. |
CSCdk48316 | Inband node discovered by HP Openview does not get added to ViewRunner New Equipment Window. Impact: ViewRunner relies on the HP topology database for adding nodes which have been discovered by HP OpenView. When a node is discovered by OpenView which has an inband interface configured, it's topology database may have inconsistent information which will cause ViewRunner not to add the equipment to the New Equipment Window. Workaround: Delete the node from HP OpenView and manually add the node to ViewRunner. |
CSCdk48634 | Subtend group icon is not removed when all the 6100 nodes have been removed from the subtend group. Impact: Subtend groups are created by ViewRunner (as opposed to being directly created by the user) based on finding a head subtending node. When the head node is removed from the Subtend group, the group should be deleted. Workaround: Manually delete the subtend group object after removing the head node from it. |
CSCdk48844 | If a user tries to make second subtend connection between two subtend connected 6100s using Edit -> Add Connection menu, he will get an error message "Object cannot be added here" and the earlier subtend connection on the map is removed. If a user tries to make second subtend connection between two subtend connected 6100s using Edit -> Add Connection menu, he will get an error message "Object cannot be added here" and the earlier subtend connection on the map is removed. Impact: Users are not allowed to make more than one subtend connection between two 6100s and when he makes a second connection the map is not refreshed correctly and the connection is removed from the submap even though the actual connection is not removed between the 6100s. Workaround: There are 2 ways to force the subtend group map to refresh: 1. Select the head node / subtend group icon and then select synchronize this subtend group. 2. Logout of ViewRunner and log back in. (But you do not have to exit Open View) |
CSCdk48861 | When multiple subtend connections are selected on the subtend group submap and then they are deleted using Edit -> Delete menu, only the first the connection selected will be deleted and the user gets an error dialog "Service failed at Server PM_030 Another subtend service is in progress". Impact: Multiple subtend connections cannot be deleted simultaneously. Workaround: Delete subtend connections one at a time. |
CSCdk50065 | Synchronization of subtend connections which are cyclic are not determined to be cyclic if there is no subtend connection on port 1 of the 6100s Subtend module. Impact: When a cyclic subtend connection exists on port 2 of a subtend module, but no subtend connection of any kind exists for port1, the cyclic relationship will not be discovered, and ViewRunner will incorrectly show the connection. Workaround: None |
CSCdk50067 | 6100s which are currently connected in a subtend group can not be removed from the subtend group without first deleting the subtend connection. Impact: This occurs only when using the Remove from Subtend Group command on a 6100 which still has subtend connections. Workaround: Remove all subtend connections from 6100 before using the Remove from Subtend Group command. |
CSCdk50091 | ViewRunner did not display the correct subtend relationships after connecting a 6100 which was already a head node of a subtend group, as the child node of another 6100. Impact: Only occurs when connecting an existing head node as a child node of another 6100 Workaround: remove the existing subtend group before trying to create a new group when trying to use a head node as a child of another 6100. |
CSCdk52113 | The Actual Upstream Rate and Actual Upstream Margin values are displayed incorrectly as 12 kbps and 0 dB respectively. Impact: When the user sorts the information in the ActiveConnections Window by clicking on any of the column headings. Workaround: Refresh the display by clicking on 'Refresh' button. |
CSCdk55404 | After deleting the head node of a subtend group, an attempt to create a new subtend group with the node fails, saying that the 6100 is already subtended. Impact: When a subtend group is deleted by deleting the head node, while it is still connected to other 6100s, ViewRunner does not remove the subtend information from the node which was deleted. Workaround: Remove all subtend connections from a node before deleting a node. |
CSCdk57080 | ChassisView continues to display ejector tabs in LOC colors even when ViewRunner is able to communicate with the 6100. Impact: When chassis View Opens after timing out on LoopRunnerCommunication State message when opening the window. Workaround: Reopen ChassisView. |
CSCdk57083 | LoopRunner Config Panel does not grey the ServiceType button and allows mode change even when unlocked modules are present in the 6100. The 6100 is in Direct Connect Mode. Impact: When Config sync is performed as a result of a change in the configuration or when any service which results in an Equipment Configured Message is performed viz Software Download or Save & Restore etc. Workaround: Open PortConfiguration Window (results in a retrieve status of all modules) and reopen/change tabs in LR Properties Window or Reopen ChassisView. |
CSCdk57099 | Restoring the configuration of a 6100 in Direct Mode fails. Gives the following error "Invalid NSS File format" Impact: When configuration is restored from an NSS file that was stored from a 6100 in Direct Connect Mode. Workaround: Edit the NSS file delete all entries in the Modem Section i.e. all the lrMpLPoolId entries. |
CSCne01800 | 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 6100's configuration due to another management system modifying the 6100 directly. Note that an ICS is automatically invoked every time a View 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. Workaround: Manually initiating a Config Synchronization prior to opening a locally scoped 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 6100s directly since the last time they were configuration synced. |
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 6100 alarm. This problem would correct itself if an out-of-sequence trap was received. Workaround: Use vrPerformConfigSync to force a full config sync. |
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. |
CSCne02240 | Summary Views (e.g. View Equipment Inventory) scoped to 'WireCenter' do not get dynamically updated when the wirecenter or location is deleted. Impact: Information on summary views is not dynamically updated when a wirecenter is deleted. Workaround: Clicking the Refresh button on the Summary View dialog updates the window. |
CSCne02251 | Subscriber PVC scope combo selection does not set busy cursor quick enough. Impact: User does not get visual feedback on the state of the GUI. Workaround: None. |
CSCne02252 | Subscriber PVC scope combo selection resizes dialog. Impact: Aesthetic. Workaround: None. |
CSCne02255 | Changing scope of View All Subscribers dialog resizes window. Impact: Aesthetic. Workaround: None. |
CSCne02283 | Config Sync status message sometimes not cleared when a manual (Intelligent) Config Sync is invoked prior to the current one completing. Impact: Incorrect state displayed. Workaround: Reopen View 6100 window. Also, the next Config Sync that occurs (manually or automatically initiated) will clear up the status message on any open 6100 Views. |
CSCne02315 | After getting wrong password msg., dialog for change password does not clear out wrong password. Impact: None. Workaround: Delete incorrect *** password 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 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. |
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. |
The problems listed in Table 5 are resolved in ViewRunner for HP OpenView Release 1.0.1.
PR Number | Description |
---|---|
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. |
CSCdk42798 | HP OpenView NNM 4.11 does not support setting variables defined as Read-Create using its graphical MIB Browser. Impact: Since the 6100 MIB uses SNMP V2 Read-Create syntax extensively, the NNM 4.11 MIB Browser can only be used to view 6100 configurations. Workaround: If setting MIB variables using a Browser is desirable, use a MIB Browser other than HP's NNM browser. |
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. |
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. |
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 6100 window. |
CSCne01802 | Subscriber Admin Status is displayed as Locked when in Loss of Communication (LOC) to the 6100. Impact: ViewRunner displays the incorrect Admin Status when in LOC. Workaround: Admin status displays correctly once communication is restored to the 6100. |
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. |
CSCne02247 | Active Connections totals area flickers badly when displaying Pool Window. Impact: Aesthetic. Workaround: None. |
CSCne02248 | Active Connections window sort slow and flickery. Impact: Aesthetic. Workaround: None. |
Use these release notes in conjunction with the documents listed in this section.
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.
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.
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 HelpHow to Use the Bug Toolkit.
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.
Posted: Sun Sep 29 00:33:49 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.