|
|
This release note describes Cisco StrataView Plus Release 8.4.13 for Solaris.
This sections describes the new features in Cisco StrataView Plus Release 8.4.13. The main features in this release are:
| Software | Release | Patch | Y2K compliance Certified By | Remarks |
|---|---|---|---|---|
StrataView Plus | 8.4.13 | N/A | Cisco Systems 29 Test Case suite |
|
HP OpenView | 4.11 | PSOV-02123 PSOV_01782 | HP |
|
WINGZ | 2.5 | N/A | IISC |
|
Informix | 5.07 UC2 | N/A | Informix |
|
Solaris OS
| 2.5.1 | Solaris 2.5.1 Recommended Patch Cluster Dated Feb/12/1999 And Solaris 2.5.1 Y2000 Patch Cluster Dated Jan/20/1999 | Sun MicroSystems
| These patch clusters can be downloaded (as of Feb/24/1999) from http://sunsolve.sun.com/pub-cgi/us/pubpatchpage.pl |
Following table has the changes to WAN device names. This document has reference to the old names only.
Old Name | New Name |
|---|---|
BPX | BPX 8600 |
IGX | IGX 8400 |
AXIS | MGX 8220 |
The Connection Service Agent is enhanced to support management of ATM-ATM and ATM-FR types of connections for both SWSW 8.4 based and SWSW 8.2.5x based releases.
The Port Service Agent is enhanced to support ASI ports and BXM (Monarch) OC3 and OC12 ports for both SWSW 8.4 based and SWSW 8.2.5x based releases.
The Connection Service Agent and Port Service Agent are enhanced to support AXIS release 4.0.02 cards including CESM4, FRSM4, AUSM4, BNM T3/E3, BNM 155, SRM T1/E1, SRM 3T3, IMATM, FRSM8, FRSM-HS1/X21 and AUSM8.
The Port Service Agent is enhanced to support ELMI feature for AXIS release 4.0.02 FRSM4, FRSM8 and FRSM-HS1/X21 cards.
The Connection Service Agent is enhanced to support SWSW 8.2.5x release Service Interworking feature and UFM-U cards for IGX.
The Equipment Management application is enhanced to support management of SRM 1:1, 1:N redundancy and IMATM cards for AXIS release 3.
The statd process is replaced by emsd/emsc (parent/child processes) to enhance the sync up performance for both SWSW 8.4 based and SWSW 8.2.5x based releases.
The Equipment Management application is enhanced to support AXIS release 4.0.02 cards including CESM4, FRSM4, AUSM4, BNM T3/E3, BNM 155, SRM T1/E1, SRM 3T3, IMATM, FRSM8, FRSM-HS1/X21 and AUSM8.
The Equipment Management application is enhanced to support ELMI feature for AXIS release 4.0.02 FRSM4, FRSM8 and FRSM-HS1/X21 cards.
The Equipment Management application is enhanced to support real time counter feature for AXIS release 4 AUSM4, AUSM8 and IMATM cards.
Network Browser is a new application that summarizes and displays the status of all nodes in a tabular form for both SWSW 8.4 based and SWSW 8.2.5x based releases.
SV+ Administration application is added to SV+ desktop. You are able to view system error log and SV+ process status.
NwTopology and HPOvTopology map are enhanced to discover and display Cisco 3800 nodes and ESP (Extended Services Processor) nodes for SWSW 8.2.5x based release.
SV+ 8.4.07 and later versions of SV+ will support networks with 200,000 end-to-end user connections, and will synchronize with these networks within 2 hours on a recommended high end machine configuration for both SWSW 8.4 based and SWSW 8.2.5x based releases.
Connection Manager in SV+ 8.4.07 and later versions is enhanced to support new ATM connection types1, such as UBR and standard ABR connections for both SWSW 8.4 based and SWSW 8.2.5x based releases.
SV+ 8.4 doesn't support ATM-SVC or FR-SVCs. As a result, they are not shown in Connection Manager GUI.
Connection Manager in SV+ 8.4.07 and later versions is enhanced to support SWSW 8.2.5x release SIW feature and UFM-U cards for IGX.
The Fault management and Statistics Collection Manager are enhanced to support BXM and AXIS release 4.0.02 cards including CESM4, FRSM4, AUSM4, BNM T3/E3, BNM 155, SRM T1/E1, SRM 3T3, IMATM, FRSM8, FRSM-HS1/X21 and AUSM8.
The Fault management is enhanced to support traps sent by the Cisco 3800 nodes for SWSW 8.2.5x based release and ESP (Extended Services Processor) nodes for SWSW 8.4 based release.
SV+ 8.4.07 and later versions will support image download feature for routing nodes via TFTP protocol for SWSW 8.4 based release.
SV+ 8.4.07 and later versions will support the image download feature for ESP nodes via TFTP protocol for SWSW 8.4 based release.
SV+ 8.4.07 and later versions are extended to support the configuration save and restore feature for ESP nodes for SWSW 8.4 based release.
SV+ will support 40 simultaneous SV+ desktops with proper hardware configuration for both SWSW 8.4 based and SWSW 8.2.5x based releases.
SV+ 8.4.07 and later versions will support physical port scheme for FRSM and logical port scheme for all other cards. The physical port support is implemented on EM, CM and service proxies. For CESM and FRP, logical port scheme and physical port scheme are the same.
SCM in SV+ 8.4.07 and later versions is enhanced to support Cisco 3800 statistics, UVM and UFM-U statistics for SWSW 8.2.5x based release.
SV+ 8.4.13 does not support Wingz report generator feature for Cisco 3800 nodes. However, the Cisco 3800 statistics are collected and saved in the SV+ database.
SV+ 8.4.13 does not support the ALM-A cards for IGX. As a result, the connections terminated at ALMA cards will not shown in the Connection Manager GUI.
SV+ 8.4.13 does not support voice connections. As a result, the connections terminated at UVM cards or FTM cards will not be shown in the Connection Manager GUI.
SV+ 8.4.13 does not support ELMI on UFM cards.
The upgrade from SV+ release 8.1.4x (Solaris based), SV+ release 8.1.16 family (SunOS based) or SV+ release 8.2 (SunOS based) to release 8.4.13 (Solaris based) is supported.
Please refer to the "StrataView Plus 8.4 Installation Guide" for detailed information.
The typical SV+ upgrade procedures include importing the Informix database from previous SV+ release. You must check the data integrity of existing SV+ 8.1 or 8.2 database prior to executing the SV+ 8.4 database upgrade procedures. The recommended tool for this purpose is the connmiss program located in /usr/users/svplus/tools directory.
<Required section for Cisco IOS release notes.>
Three types of machines are supported for SV+ 8.4 as standard platforms. They are low-end, mid-range and high-end platforms. The configuration of each platform type is listed in table 2.
| Platform Type | Machine Type | Number of CPU | Size of RAM | Graphic Card Type | Hard Disk Drive | Size of Swap Space | Number of SV+ Desktops (n) | Number of Connections (m) |
|---|---|---|---|---|---|---|---|---|
Low End | Sun Ultra Enterprise 1 Model 170E or Sparc 20 Model 151 or Ultra 10 with SCSI controller | 1 | 256 MBytes | 24 bits | Two 2 GByte drives OR one 4 GByte drive | 512 MBytes | n < 5 | m < 5,000 |
Mid Range option 1 | Sun Ultra 2 with 300 MHz or Ultra 30 model 300 and 1MB cache
| 1 (300 MHz processor) | 512 MBytes | 24 bits | Two 4 GByte drives | 1 GByte | 5 =< n < 10 | 5,000 =< m < 25,000 |
Mid Range option 2 | Sun Ultra Enterprise 2 Model 2300 or Ultra 60 | 2 (300 MHZ processors) | 512 MBytes | 24 bits | Two 4 GByte drives | 1 GByte | 5 =< n < 10 | 25,000 =< m < 50,000 |
Mid Range option 3 | Sun Ultra Enterprise 2 Model 2300 or Ultra 60 | 2 (300 MHZ processors) | 1 GByte | 24 bits | Two 4 GByte drives | 2 GByte | 5 =< n < 10
| 50,000 =< m < 100,000 |
High End | Sun Enterprise 4000 or Enterprise 450 | at least 4 | 1 GByte | 24 bits | Two 4 GByte drives and disk array | 2 GByte | n >= 10 | m >= 100,000 |
The selection of a proper SV+ platform depends on a number of factors, such as number of SV+ desktops, number of managed connections and number of statistics collected and stored. The above table also lists recommended SV+ platforms based on the size of network.
Following are additional notes for SV+ platform requirements:
1. For every additional SV+ desktop, there is a need for additional 8 Mbytes of RAM beyond the standard platform configuration.
2. Users may upgrade the standard configuration such as CPU speed, RAM size and disk space for future expansion.
3. The default disk size for the Informix database is 800 MBytes. However, it is highly recommended to size the disk space needed for the statistics collection process.
For Stand-alone SCM, a minimal CPU configuration is required:
128 MB memory, Solaris 2.5.1, 2GB total disk space. You should install Solaris, and provide at least 300 MBytes for the /usr/users/svplus partition. This will provide adequate storage for the SCM files and some local stats files. For larger stats file depository, you can add more disks and store the stats files on the larger partition.
The SV+ 8.4.13 release works with HP Openview Release 4.11 for Solaris 2.5.1.
For HP OpenView installation requirements and procedures, please refer to "HP OpenView Network Node Manager Products, Installation Guide" (part # J1172-90001 from HP).
StrataView Plus 8.4 is certified on Solaris version 2.5.1. Certification for 2.6 Solaris has not been performed. Preliminary testing shows that SV+ does not operate on release 2.6 of Solaris. Do not use Solaris 2.6 to run StrataView Plus 8.4.
StrataView Plus 8.4 works with Informix 5.XX, where XX is greater than or equal to 06. However, Informix 5.07.UC2 is now being shipped with StrataView Plus 8.4.09 for Solaris platform.
SV+ GA releases are recommended for production use of SV+ and production versions of switch software. Operating SV+ with releases that were Pre-Release software created risks that can be alleviated using GA software. SV+ 8.4.06 and greater are GA releases and are supported.
This version of StrataView Plus will operate with IPX/BPX/IGX releases 8.4.0, 8.1 and 8.2, Axis release 3.x (AUSM4, CESM4, FRSM4, ASC and IMATM) and Axis release 4.0.02 or greater (CESM4, FRSM4, AUSM4, BNM T3/E3, BNM 155, SRM T1/E1, SRM 3T3, IMATM and FRSM8) for all supported features.
Axis Release 2.X and Switch Release 8.4.X is not supported for AUSM. This configuration has not been fully tested.
StrataView Plus 8.4.XX has been tested with IPX/BPX/IGX release 8.4.X and Axis release 4.0.02.
StrataView Plus is backward compatible with AXIS release 3. In the case of IMATM, StrataView Plus 8.4 will fully support IMATM starting on IMATM release 3.0.03 onwards. The support for any previous releases of IMATM is limited to display on Equipment Manager. No other support is available from SV+.
Although SV+ 8.4 Equipment Manager shelf view displays AUSM release 2 cards, you must enable the line and ports from AUSM CLI. The Equipment Manager line configuration window and port configuration windows will not be fully functional for AUSM R2 cards. As stated earlier, release 2.X and 8.4.x switch software is NOT recommended for production deployment.
StrataView Plus 8.4 Connection Manager does not support AUSM R2 due to the lack of port speed information in the SV+ database. This limitation will not allow you to specify the PCR(0+1) parameter related to AXIS.
StrataView Plus 8.4 does not support the BERT feature of AXIS/SRM R4. You must use CLI interface to configure the BERT functions.
All event messages are now displayed in HPOV's Event Browser window. There is a limit of 2000 pending messages on HPOV's Event Browser. If there are more than 2000 messages to be processed and displayed by Event Browser it may exit.
There is a known problem with the malloc() function on Solaris version 2.5.1. Sometimes this problem will cause SV+ applications to core dump in the malloc() function call. The following Solaris patch is required to fix the problem.
Patch-ID# 103640-06 or later Keywords: SIGSEGV kernel mutex_enter lwplock lm_get_sysid klmmod lm_sysid Synopsis: SunOS 5.5.1: kernel patch Date: Mar/13/97All patches are Inclusive patches. Each subsequent SV+ patch includes the previous patch. This makes patch installation a single step. You must have previously installed SV+ or the SV+ Service Agents before applying the patches. The patch assumes this has been done.
To install a patch a user would do the following:
Step 1 Get the patch tar file on to the SV+ machine.
Step 2 If the tar file name does NOT end in "Z", the file is uncompressed. These instructions are for compressed files. If your patch is not compressed, as user 'root', use the command "compress <tarfilename>" and go to step 3.
Step 3 Stop Strataview Plus.
Step 4 As user 'root' do the following on the patch level you have decided to install:
zcat <patchfilename> | tar xvf -
Step 5 Start SV+.
The files on the patch have already been setup for the correct execution privileges, and are ready to use.
The field software support engineers can contact The Cisco TAC support center for information on the latest patch for a given version of StrataView, or browse the directory specified above for the release notes. All patches are described in the latest version of the release notes. You may find you do not need any of the patches available for a specific release of StrataView Plus.
Make sure at least 750 MBytes of disk space in /usr/users/svplus area can be allocated for SV+ 8.4.09 installation. In the case of upgrade, disk space used by existing SV+ software plus free disk space should exceed 750 MBytes.
You should install Wingz software from the Wingz CD, then contact Wingz for a runtime license and blend it with SV+ 8.4.09. Failing to do so will result in following error messages when you click on the SV+ Report icon: "There is a problem with the registration information for this machine. Contact your system administrator".
If the SV+ station is a Sun Enterprise 4000 and the Informix is installed on a disk array (typically the device name is /dev/vx/rdsk/rootdg/vol03) then the ownership of the device and the group ownership of the device should be set to informix. The mode of the device should be 770. Otherwise, after reboot the machine, following error message will be shown in the console, "Shared memory is not initialized".
If you are installing OpenView 4.x over an existing version make sure that the /etc/snmpd and /etc/snmpd.conf are removed or re-named before carrying out the upgrade. It is likely that you will see the following message when trying to re-start OV:
object manager name: netmonbehavior: OVs_WELL_BEHAVEDstate: NOT_RUNNINGPID: -last message: Can't talk to snmpd; see /usr/OV/log/netmon.trace forinfoexit status: exit(1)Information left in these files causes problems for the new version of OV.
These files are not removed by the ovremove program.
If smux entry exists in /etc/services file, SV+ SNMP Agent process try to use that port and may have problem opening. For SV+ SNMP Agent processes to function properly this entry in /etc/services should be commented out, if it is not using default tcp port of 199.
The SV+ upgrade is not supported across different platforms, for example the upgrade from a AIX-based SV+ release can't be upgraded to a Solaris based SV+ release or vice versa.
After creating a new database by executing SV+CreateDb command, if StrataView Plus is restarted before it is synched up with the network, it will result in a database inconsistency. In this case, perform SV+CreateDb before restarting SV+ to avoid database inconsistency.
The logical_connection table count for a node in SV+ database may not match the master lcon counts in that node. This will happen if it contains fastpad connections, or if it has slave lcons with no connections.
Any node with IP address 192.0.0.0 or 0.0.0.0 will not be displayed or stored in SV+ database.
Each IPX/BPX/IGX/Axis node to be managed by StrataView Plus must be configured with IP Relay IP Address (cnfnwip). The gateway node must be configured with both LAN and IP Relay IP Addresses.
The IPX/BPX routing and IPX/AF feeder modes must be configured with read and write SNMP community names. The SNMP community names "public" and "private" are configured in SV+ for GET and SET respectively as defaults.
The directly attached node (Gateway node) must be configured with IP Relay IP address before starting StrataView Plus.
For adding a connection the connectionIndex must be 0(i.e., there is no need to do a GET on connAvailIndex). The actual index is internally generated by the connection service agent itself.
For the sake of backward compatibility, the 500 series traps are generated for 8.1 or 8.2 nodes, while the 20000 series traps are generated for 8.4 nodes.
For DAS connections, deleting an end point from a segment and later adding it to another segment at a very fast rate may result in a database inconsistency.
Test Connection and Test Delay do not work for connections routed through a StrataCom virtual trunk cloud when the connection originates from an Axis or BPX.
Connection Manager GUI for preferred route displays ALL available trunks without considering the traffic class. As a result, it is possible to set a preferred route for a CBR connection traversing trunks that do not support CBR traffic.
SV+ shows the status of a connection based only on the routing segment status.
In the Connection Manager GUI, you must enter both the end points (i.e. node, shelf, slot, port) in the Add Connection window before entering any connection or midpoint parameters.
For an FRSM - ASI PVC connection, the error message "Remote SCR value out of range" generated by the remote BPX, indicates that the CIR value of the Frame Relay side is below the acceptable limit (cell rate) of the trunk between the AXIS shelf and its routing node. To correct the problem, one can increase the value of CIR. E.g., if the trunk between the AXIS shelf and the routing node is a BXM trunk, the CIR value should be at least 19.2 kbps (= 50 cell/sec).
ABR.FS connections cannot be added with default values for ATM-FR SIW connection. The 'ICR TO' value has to be changed.
Certain types of connections, such as VBR.1 or CBR, with policing parameters can't be modified by SV+ if the default was changed using the switch command line interface.
The maximum VCI that can be used for connections is 32767.
The Connection Manager GUI provides the default values of 5100 bytes for BC (Burst Committed) and BE (Burst Excess). These values are suitable for all cases of CIR (Committed Information Rate) up to 2048 Kbps. If the CIR is changed to some value higher than 2048 Kbps, you should adjust the BC and BE accordingly, otherwise, frames might be "detagged" due to the inappropriate values of BC and BE. The following formula can be used as a guideline for these two parameters: BC = BE = 5100 * (CIR / 2048000).
When you start a stand-alone SCM, the following message is not an error message: Cannot communicate with SV+, either SV+ is not active or another GUI is running presently.
You should select a routing node for the SCM time sync node.
For a group of selected nodes from which stats files are to be collected by a stand-alone SCM, the collection period should be set to the same value for all nodes.
If stats files are being saved, the SCM does not purge these files even if the disk is full.
The format of "statsgen.stats" binary file, which is used to store all SCM collection related parameters, has been changed in release 8.1.16. So, upgrading from 8.1.16 will have no impact on this file. Upgrading from 8.1 release prior to 8.1.16 is not supported.
The SCM supports 3100 nodes maximum in stand-alone mode.
For CISCO 3800 nodes, the network parameter 'Time-out period' has to be 5 seconds.
Prior to SWSW release 8.1, you could specify any time period for a peak interval from SV+. In SWSW 8.4, following rules are used when you configure peak interval through SV+. Violating the rule will cause TFTP error 22 displayed in the SCM.
SV+ must not be started from the OpenWindow's Cmdtool Window. If SV+ is started from Cmdtool, the Cmdtool may freeze the screen if Cmdtool window's log buffer is full.
While SV+ is running, if the X server crashes for any reason, then login as svplus and stop core processes. Then SV+ can be restarted.
While SV+ is running, if remote display is killed without properly shutting down the SV+ Desktop, then reopening it remotely may not succeed.
A VNS node is not to be attached to feeder nodes.
A VNS node may be added to a node isolated from the network.
The Wingz "Add Comment" option is not supported for virtual trunk and ATM connections. Wingz sometimes does not scroll up the list box properly.
Sometimes it may take 2-3 minutes to display new nodes after addition of virtual trunks. This is due to the time required to setup link0 and link1 subscriptions.
Although SV+ 8.4.09 is designed to be backward compatible with pure 8.1 and pure 8.2 networks, the SIT testing was done only on a pure 8.4 network.
The basic SNMP Agent functionality is unchanged from release 8.2. ATM-ATM and ATM-FR cross connections are supported through the Connection Service Agent.The Port Service Agent will support a physical port addressing for FRSM and a logical port addressing for the rest of the cards. In the case of CESM and FRP, the logical port addressing is identical to physical port addressing. The structure of the SV+ 8.4 service MIB has been re-organized.
The SNMP master agent is configured to use 8161 as a default port id for agent communication. The configuration file SNMPAgent.conf for the master agent is located in /usr/users/svplus/config. If user is running another Network Manager which uses port number 8161, this UDP port can be configured to some other port number in this file as follows:
Syntax:Explanation TRANSPORT special SNMP
OVER UDP SOCKET AT PORT 8161The Service MIB (Connection Service MIB and Port Service MIB) uses community strings for authentication. The Connection Service Agent and Port Service Agent processes use /usr/users/svplus/config/SNMPProxy.conf file as a configuration file. The SNMP community name strings can be configured in this file as follows:
Syntax: GET_COMMUNITY public SET_COMMUNITY privateThe SNMP community names "public" and "private" are configured in this file for GET and SET respectively as defaults.
The following two new traps have been added to Axis mib (axis.mib file in mibs subdirectory of svplus home directory).
Indicates the Loss of LMI Alarm for AXIS BNM trunk.
(ANNEX G signalling failure)
Indicates the Clear of Loss of LMI Alarm for AXIS BNM trunk.
(ANNEX G signalling failure has cleared)
The above traps also have been added to StrataCom_trapd.conf, the HPOV-SV+ interface file.
The following changes are done in axis.mib (changes from axis.mib release 4.0.03 to 4.0.06).
Additional enumerations have been added for the following objects due to introduction of new card types.
shelfFunctionModuleTypeThe object dsx3LineType has been changed.
Added enumeration dsx3M23(3).
Changed access from read-only to read-write.
The default value of chanOvrSubOvrRide has been changed from disable to enable.
Varbind #4 has been changed from shelfSlotNum to moduleSlotNumber for all traps.
Varbinds #6 and #7 have been changed for the traps 50000, 50002-50009
shelfFunctionModuleState to functionModuleState
shelfFunctionModuleType to functionModuleType
Varbinds #6 and #7 have been changed in the following traps
1. bnmNolinealarmTrapnum (50100)
2. bnmlinealarmTrapnum (50101)
3. bnmLineLpbkEnableTrapnum (50102)
4. bnmLineLpbkDisableTrapnum (50103)
Varbind #6 has been changed from dsx3LineNum to lineNum.
Varbind #7 has been changed from dsx3LineType to lineType.
Changes in Descriptions have been done for some MIB objects.
The following changes are done in axis.mib (changes from axis.mib release 4.0.06 to 4.0.07).
Modify(3) enumeration has been deleted from SRM3T3 object.
Additional enumerations have been added for portState object. These are done as part of BERT related changes.
latchDS0DropFeLoop(9)The following changes are done between release 4.0.07 and 4.0.08 versions of axis.mib.
1. The stratacom definition was removed from the MIB. This can be imported from the RTM-MIB instead.
2. NetPrefix definition has been changed. Instead of SIZE(8|13), now it is SIZE(8..13). This clears errors from the smic compiler.
3. Changed bertDDSCode enumerations from HEX to decimal equivalents. This clears errors from the smic compiler.
4. NsapAddress definition has been changed. Instead of SIZE(1 | 4..21), now it is SIZE(1..21). This clears errors from the smic compiler.
5. Trap definitions have been modified for the traps 50040, 50041, 50060, 50061 and 50062. In the previous release, the varbind moduleSlotNumber appeared twice in the trap definition, resulting in smic compiler errors. So, to avoid the problem of duplicate moduleSlotNumber varbinds, now the second moduleSlotNumber has been changed to shelfSlotNum.
Because of the changes to axis mib version 4.0.08, the HP OpenView users need to delete some events. The following steps can be followed to achieve this
Enter following commands on your SV+ station as super user.
# /opt/OV/bin/xnmevents -delete trapCesmChanOverflow trapCesmChanCellLossThe HP OpenView user has to load the SV+ RTM mib first then load the axis mib version 4.0.08. The SV+ RTM mib is located in /usr/users/svplus/mibs/rtm.mib.
The HP OpenView mib loader is in the OpenView "Options" menu. Some notification messages will be shown after the RTM and axis mibs are loaded.
If StrataView plus 8.4.10 is installed on the system running HP OpenView, StrataView installation procedure will take care off the above steps.
The following changes are done between release 4.0.08 and 4.0.09 versions of axis.mib.
The traps 50120-50123 have been added.
The traps 50100-50103 have been obsoleted from Axis release 4.0.
The following changes have been done to switch mib (/usr/users/svplus/mibs/strata.mib) and SV+Service.mib.
The range of atmEndptMinAdjustICA object has been changed from 1..100 to 3..255.
The description of atmEndptMinAdjustICA object has been updated. Following is the new description.
"ForeSight minimum adjustment period. Also known as TRM, which provides an upper bound on the time between forward RM-cells for an active source.
The range of atmEndPointMinAdjustPeriod object has been changed from 1..100 to 3..255. The description of atmEndPointMinAdjustPeriod object has been updated. Following is the new description.
ForeSight minimum adjustment period. Also known as TRM, which provides an upper bound on the time between forward RM-cells for an active source.
The following changes are done between release 4.0.09 and 4.0.10 versions of axis.mib.
Added text "The moduleSlotNumber is the slot number of the Active ASC card." to the description field of traps 50022 to 50023.
The following interface types have been removed from the svAtmPortIfType and svPortIfType mib objects:
t3-smf (27)The smf, mmf, smflr and snm are fiber interfaces and are not applicable to t3 and e3 interfaces.
Updated the description of svAtmPortIfType object to reflect smf, mmf, smflr and snm related updates to t3 and e3 interfaces.
Updated description: "For BPX-BXM, lm-bxm, t3, e3, oc3-smf/mmf/smflr/snm, oc12-smf/mmf/smflr/snm"
The following changes are done between release 4.0.10 and 4.0.11 versions of axis.mib.
Syntax for the following bnmCounters has been changed from INTEGER to Counter.
bnmPortRcvCellsSyntax for the following sarChannelCounters has been changed from INTEGER to Counter.
xmtCellsThe following changes are done between release 4.0.11 and 4.0.13 versions of axis.mib.
Added default values for all the objects under the ausmChanCnfGrp.
Added the following BNM Port Counters.
bnmPortRcvCellRate,Added the following AUSM Port Counters.
ingrRcvClpSetCells,Added the following AUSM Channel Counters.
chanIngrRcvCellRate,The bit postion 8 in dsx3LineAlarmState has been changed from "Receiving test pattern" to "Receiving remote payload loopback".
The range for atmEndPointCDVTZeroPlus1 changed from 1-250000 to 0-5000000 microseconds.
The description for atmEndPointCDVTZeroPlus1 has been updated.
". Ranges:The following changes are done between release 4.0.15 and 4.0.16 versions of axis.mib.A new enumeration reserved (12) has been added to the following objects.
shelfFunctionModuleState
redPrimaryState
redSecondaryState
functionModuleState
A new enumeration not-testable(169) has been added to svCmpaErrorEcode and svCmpaErrorLastEcode object.
The following changes are done between release 4.0.17 and 4.0.18 versions of axis.mib.
A new counter dsx3LCVCount has been added under the dsx3CounterTable. This counter is used for counter LCV errors on DS3 line on a BNM card.
The description for atmEndPointRateDown has been updated to state that the range for abr-fs service on BPX is 1%-100%.
The range for atmEndPointVpi mib object has been changed from 0..255 to 0..4095. The description for this object also has been updated to state that the range for AUSM card is 0 to 255, for UNI port on ASI/BXM cards is 0 to 255 and for NNI port on ASI/BXM cards, it is 0 to 4095.
The description for atmEndPointPCRZeroPlus1 object has been updated with the following range details.
The description for atmEndPointMCR object has been updated with the following range details for BXM and AUSM cards.
The description for atmEndPointSCRZeroPlus1 object has been updated with the following range details for ASI/BNI cards.
The mib object atmEndPointFGCRA has been updated to have no default value.
The description for mib objects atmEndPointHiCLP, atmEndPointLoCLP, atmEndPointVcQSize, atmEndPointEfciQSize, atmEndPointIBS has been updated to state that these objects are not supported for AXIS shelves.
The Serial Configuration Upload Download (SCUD) product, as the name says, supports IPX/BPX/IGX configuration save and restore functionality over a serial interface.
The current version available is 2.0. This is currently available for SunOS 4.1.x platform. This tool is used for disaster recovery and is available free of cost to Cisco SV+ users having support contract.
SV+ Development is actively attempting to add this tool to CCO. Once this is done, one should be able to find the links to the SCUD patches at the CCO site.
Supports configuration save and restore for a single node network. SCUD uses serial line interface on 'Control Port' of switch. Following baud rates are supported:2400, 4800, 9600, 19200 and 38400. The "Node Administration" window is used for user logins.No topology map will be shown.
SCUD supports IPX, BPX and IGX switches and can be launched by any user and does not need special privileges. SCUD uses the same directory structure used by SV+ to save/restore configurations.
The SCUD software will run on any Sun workstation running SunOS 4.1.x operating system. It can also be run on Sun workstation running Solaris 2.5 or 2.6 with binary compatibility support. The minimum memory requirement is 64MB. There is no special hardware requirement.
SCUD software is available on quarter inch tape in UNIX tar format. Following procedure needs to be followed for installation.
Step 1 Login on Sun workstation.
Step 2 Change directory to where you need to install SCUD (SCUD home directory). It is advisable to install SCUD in the /usr/users/svplus directory. For this you have to move any existing SV+ installation in /usr/users/svplus to some other place before installing SCUD.
Step 3 Insert tape in the tape drive.
Step 4 Use tar command as shown below to get software loaded.
$ tar xvf /dev/<driveid>
where <driveid> indicates the tape drive identifier, such as rst0 or rmt0.
Step 5 There is no install script to be run. The software is ready for use.
This version of SCUD is compatible with Switch Software release 8.1, 8.2 and 8.4 only.
SCUD software uses two configuration files. Configuration file 'cnfnodes' is used to specify the switch identification. Second file 'config.sv' is similar to one used by SV+ product and contains the serial line configurations.
'cnfnodes' file can have only one line with format shown below:
<nodename>|<switch_node_id>|<switch_net_id>|<SV+_netid>|
for example:
nmsipx02|2|1|1|
switch_node_id is node id of a switch.
switch_net_id is network (also called as domain) is of a switch.
SV+_netid' is SV+ network id (from config.sv file)
config.sv can have only one line with following fields and '|' as delimiter:
SV+_netid | no need to change |
networkname | no need to change |
serialport | Specify the device file name for the serial port used |
Baudrate | Set serial port speed, must match speed of control port at the node |
autodial | Phone # to dial out including any prefix needed, 0 for not dialing |
SV_Timeout | Not allowed to change |
Retransmit | Not allowed to change |
DL_Thresh_TO | Not allowed to change |
DL_Ack_TO | Set application level time-out value in seconds as appropriate |
DL_Blk_Size | Set transmission block size in bytes, no greater than 1024 |
Release | Specify switch software release as appropriate |
For example: 1|Network1|/dev/ttya|19200|0|7|3|0|30|256|8.1
If SCUD is running with SunOS system, no configuration is needed for the serial port. User only need to identify which tty (/dev/ttya or /dev/ttyb) is for SCUD to use.
If SCUD is running with Solaris system, user need to run the system administration tool "admintool" to configure the serial port as "Modem - Dial-Out Only". This tool can only be run by super user (root). The serial port device name to use in the config.sv file should be "/dev/cua/a" for ttya and "/dev/cua/b" for ttyb.
Configure the control port of the remote node to be connected as follows:
Step 1 Run "cnftermfunc c 1" command to set control port function as VT100/StrataView.
nmsipx06 TN StrataCom IPX 8 8.1.50 Sep. 18 1997 19:16 PSTStep 2 Run "cnfterm c 19200 n 8 1 x x y n" command, replacing the port speed parameter (19200) to match the setting in 'config.sv' file, to configure the control port to this settings:
nmsipx06 TN StrataCom IPX 8 8.1.50 Sep. 18 1997 19:29 PSTModem settings we use in this recommendation is for Motorola Codex 3220+ model. If you are not using this model, use the corresponding commands for your modem to configure same settings.
AT&F | Reset to factory default |
ATS0=1 | Enable auto-answer on first ring |
ATL1 | Modem speaker at low volume |
AT*SM3 | Enable automatic MNP error correction |
AT*DC0 | Disable data compression |
AT*FL0 | Disable XON/XOFF flow control |
AT&S1 | Sets DSR to "normal" |
ATE0 | Disable local character echo |
ATQ1 | Disable result codes (modem will appear dead) |
AT&W | Save current configuration settings |
AT&F | Reset to factory default |
ATL0 | Modem speaker at minimum volume |
AT*SM3 | Enable automatic MNP error correction |
AT*DC0 | Disable data compression |
AT*SC1 | Enable DTE speed conversion |
AT*FL0 | Disable XON/XOFF flow control |
AT&C1 | DCD controlled by modem |
AT&D2 | Modem disconnects when SCUD toggles DTR |
AT&W | Save current configuration settings |
SCUD allows user to save and restore configuration from/to IPX/BPX/IGX switches. The configuration saved using StrataView Plus product is stored under /usr/users/svplus directory using <saveid>_Cfgdir as directory name. When user needs to restore the saved configuration he has to copy this directory under SCUD home directory.
e.g.
If SCUD is installed under /usr/SCUD directory and the current saved configuration has saveid of 'SV72' then user will copy the 'SV72_Cfgdir' directory from /usr/users/svplus/ (or from other directory where files are manually copied) to /usr/SCUD directory.
Change the cnfnodes and config.sv files to the required configurations. Refer to SCUD Software Configuration later in this document.
Change directory to where SCUD is installed.
Set DISPLAY environment variable to your workstation display.
Make sure the SCUD configuration files, the remote node's control port and the modems on both sides are configured properly before launching SCUD.
Follow these steps to launch or stop SCUD:
Step 1 Type 'SCUD' on command line and hit <RETURN>
Step 2 Select option 1 to launch SCUD or select 2 to stop SCUD.
When SCUD is launched user will see "Node Administration" window on screen. User can logon to switch and use 'loadcnf' command to restore the configuration. The configuration to be restored must have already been copied to the SCUD home directory.
There are two ways to make the modem connection:
This is enabled by putting the phone number in the config.sv file. The phone number can be prefixed by 'P' or 'T' for pulse or tone dialing. Comma, ',' is also allowed in this field for additional pause time. When SCUD starts, it will dial out from the modem and wait for it to connect before the actual applications are started. Messages are displayed at the start-up window to show the progression.
If SCUD fails to make the connection, it will retry indefinitely. If retries continue to fail, user should correct the failing condition and restart SCUD.
After the connection is established, the "Node Administration" window will appear. However, it may take a couple minutes before the node's login prompt is displayed in the "Node Administration" window. This is because the node may send a lot of data out once the connection is established and SCUD has to filter them out. At this time, the "RD" light on the modem is almost solid on. Wait until this "RD" light is off, you should be able to get the node's login prompt by hitting <RETURN> on the "Node Administration" window.
1. Use other communication tools, e.g. tip
In some cases, user cannot establish the modem connection by simply dialing a phone number. For example, if the remote end modem connects to a terminal server, some commands have to be issued after the modems are connected to route the connection to the port that the remote node is on. SCUD is capable of establishing this kind of connection. Hence, user has to establish the connection manually before launching SCUD.
The modem should be setup in a way that it would not drop the line even when DTR is dropped. After user has establish the connection using tools like tip, the remote node will start sending the command line interface screen data to user's screen. These data include VT100 terminal escape sequence that looks like garbage. User should wait until these are cleared and the node's login prompt appears, then exit the tip session. Make sure the line is still up by checking the "CD" light on the modem.
Before launching SCUD, verify that in SCUD's configuration file config.sv, the autodial (phone number) field is set to 0. If this field is set to any valid phone number, SCUD will drop the line and redial that number. After SCUD is launched with the no dial out setting, the "Node Administration" window will appear right away and the node's login prompt will show up in seconds' time.
If network id in config.sv does not match with one from cnfnodes SCUD does not detect it.
SCUD may not be launched if SV+ software is running on the same workstation.
The protocol between SCUD and the remote node during a configuration save or restore session enforced a simple handshaking protocol that the sending side after sending a data packet, will wait for an acknowledgment (ACK) from the remote side before sending the next data packet. An application level time-out is imposed. When time-out on waiting the ACK, the sending side will send an ABORT message to the remote end and the operation is aborted completely. At the application layer, there is no retry capability. However, at the link layer, each packet will retransmit 3 times before giving up. Depending on the modem line quality, it could be so worse that the session keep aborting and never get completed.
In SCUD release 2.0, some enhancements are added to address this issue:
Log files are stored in the log directory under SCUD home directory. Messages are appended to these log files continuously even when SCUD is restarted. When they grow to certain size, they are moved to *.old and new log files are used. When the new log files are full again, the *.old will be overwritten. In other words, only one backup is kept to prevent using up all disk space.
These log files are there to help debugging in case problems occur. User should saved these files when there is problem. Otherwise, there is no need to backup these files.
There are some debugging capabilities built into SCUD as highlighted here:
Higher levels (L3 and L4) of verbose messages for log/svmain.log can be enabled at SCUD start-up time and toggled on/off during run time. To enable these levels of verbose messages at start-up time, modify the "start_SCUD" script to include "-w" command line option for socketd as follows:
#!/bin/shL3 and L4 verbose messages for log/svmain.log can also be toggled on/off by sending SIGUSR2 signal to svmain process. The command is: kill -USR2 <pid> where <pid> is the process id of svmain.
Verbose mode can also be turned on for configd process which is responsible for the configuration save and restore operation in SCUD. Modify the "start_SCUD" script to give the "-v" command line option to configd:
#!/bin/shThe output for the verbose message from configd is stored in "configd.verbose" in SCUD home directory. This file is overwritten every time SCUD is started.
At times, user may see the following messages:
ipc.c:598:IPC Connect Failed, Address(4001) PID(25409):: Connection refusedThis is generated by topod process when it could not communicate with another process due to the start-up time difference. This problem is fixed in SCUD 2.0 that topod will now wait for 1 second and retry until successful. Normally, it takes only one retry to succeed. As long as the "retry succeeded" message is shown, there is no problem and user does not need to restart SCUD. If the "topod: send_packet_2_IPX failed, retrying ..." message keep showing, it usually indicates a serious system problem. User may need to reboot the workstation to clear the problem.
If in the middle of a SCUD session, the phone line dropped or hung, user has to restart SCUD to re-establish the connection.
In the case that modem connection is made by tip or other communication tools, the re-established connection may appear to be "dead" (no prompt or any data), or showing some garbage. This is because at the remote node, it is still in StrataView mode so it would not send the VT100 screen data. User can launch SCUD as usual and SCUD would be able to communicate with the node in StrataView mode. However, if user wants to make sure the connection is working, user can send the DEL character to the remote node by pressing the "Del" key on the workstation. This will toggle the node's control port function back to VT100 mode. User would be able to see the node's login prompt.
This section describes known anomalies in the StrataView Plus releases and anomalies fixed in SV+_ releases.
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCst97513 | DNS trap number 7012, 7014, 7015 are shown in the rtm.log but not in HP Openview event log. | There is no workaround. |
CSCdj24615 | SV+ should use higher time out value for BRAM save/restore application. Current application level time out value is 1 minute which is the same as the robust protocol level time out value. | Restart the BRAM save/restore process when the protocol transmission is not reliable. |
CSCdj38135 | On any AXIS card, upon bringing up the line menu, if any of the lines are disabled then the "operational state" displays "disabl" and not "disabled". | There is no workaround. |
CSCdj40594 | The ConnProxy can not be used to "unset" a preferred route. This is typically done by setting the preferred route to NULL. | The workaround is using CLI interface instead. |
CSCdj68477 | The value of svPortAlarmTable from Service MIB and port status on switch do not match for BXM cards. | There is no workaround. |
CSCdj69154 | The Frame Viewer program which pops up when SV+ desktop is launched remains on after SV+ core processes have been stopped and desktop has exited. The impact is some amount of memory is occupied by the Frame Viewer process. | Manually kill the Frame Viewer process after SV+ core processes have been stopped. |
CSCdj72233 | EM GUI shows blank for the line that BERT test is being run. | There is no workaround. |
CSCdj76510 | Real Time Counters not accessible from the StrataView proxy agents, but the proxy documentation says that they are accessible. |
|
CSCdj79083 | After TestCon if a SNMP GET operation is done on svConnLocalStr and svConnRemoteStr objects ConnProxy returns NULL. |
|
CSCdj80823 | ICON state on HP does not track switch over of esp |
|
CSCdj83866 | NWTopology process exits intermittently in an unexpected way. This happens very intermittently. |
|
CSCdj84298 | Wingz does not display object for selected line statistics for E1 line type. |
|
CSCdj85040 | Wingz Raw Data Report shows only slot number for UFM card service lines. |
|
CSCdj88443 | Equip Management GUI and SNMP Proxy agent return wrong value for chanSecUpTime counter. | This is a problem in Axis firmware and has been fixed in 4.0.11 version of Axis firmware. |
CSCdj90924 | SV+ database shows connections with no routes after warm start. |
|
CSCdk02142 | ESP ICON on HP OV does not change color (state) on clearing failure. |
|
CSCdk19781 | UserConnection Fail event is logged without any error on the connection alarms. | This has been observed in SV+ 8.4.10 managing AXIS 2.1.25 shelves. |
CSCdk24060 | ConMgr GUI doesn't show current route for a PVC, intermittently. |
|
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdj68372 | Stat types "Packets Received" and "Receive Packets Discarded" are missing in Data Connection section of Statistics Collection Manager.. | These statistic types have been added Statistics Collection Manager and the reports tool |
CSCdj81530 | Connection Proxy and Connection Management GUI can't setup ATM connections if the VPI value given is in the range of 256-4096 for connections involving BXM/ASI NNI port. | It has been fixed to take the values for atmEndPointVpi in the range of 0 to 4095 for BXM/ASI NNI port. For UNI port the range is 0-255 .For AUSM NNI VPI range is 0-255. |
CSCdk02834 | Frame Forward and FUNI enums are missing from SV+ Service mib for frEndPointchanType mib object. Enumerations frFUNI(4), frForward(5) have been added to this mib variable. Defaults for this attribute:
frFUNI is applicable for FUNI ports only. frForward is applicable for FrameForwarding ports only. |
|
CSCdk04116 | Database inconsistency between two SV+ stations managing same network, after the cold start (after creating SV+ DB) has been fixed in SV+CreateDB process. |
|
CSCdk23634 | When executing pkgadd -d CSCOsv error message "please create group users" is shown. | For this group users has to be created before running pkgadd command. |
CSCdk26786 | SV+ SNMP Proxy can not set atmEndPointMCR to any value less than 50 for PVCs on BXM/UXM cards. | The lower limit for atmEndPointMCR should be 6. |
CSCdk34622 | Values for the column protocol_type in SV+ database table - frp for certain rows, do not match with the enumerations specified in the SV+ Database Interface Manual. This happens for protocol types -'none' and 'LMI with Async Updates. | This has been fixed by updating SV+ Database Interface Manual. |
CSCdk37713 | SV+ install overrides root users PATH environment variable. | This has been fixed in SV+ install procedure. |
CSCdk45518 | After a FRP port is deleted, it takes sometimes before it can be added back, even though SNMP get on the port confirms that the port is deleted. The wait is usually more than 30 seconds. Further problem description: This is a timing issue. After the port is deleted, if an attempt to add back that port is done immediately, ConnProxy may not allow user to do so. The reason is ConnProxy goes to the DB to check for port existence. And if it happens that the robust message has not come from the network to update the FRP table, ConnProxy thinks the port still exists and hence reject the add operation. | This has been fixed in ConnProxy process. (The fix is to remove the DB port existence check, and forward the add request to the switch to let it determine if the port exists or not.) |
CSCdk53210 | SV+ Topology map doesn't reflect the correct status of ESP nodes. | This problem has been fixed in topod process. |
CSCdk60151 | A problem in rtm process, where keep alive messages to AXIS shelves are not sent, has been fixed. | This problem has been fixed. |
CSCdk60249 | An unexpected exit problem in Connection Manager GUI has been fixed. This happens when `.' (dot) is entered as port number in Port # field and when Apply button is pressed. | Fix has been put in to flag an error message if there is any illegal character entered in this field. |
CSCdk66993 | An intermittent exit problem in Equipment Manager GUI has been fixed. This problem occurs when a DISPLAY SHELF button is clicked, after changing the node selection from the one that is being displayed to a different shelf. |
|
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdj11154 | SV+ core dumped when a Wingz program - the SV+ report generator was invoked. The problem has been reported to Wingz for investigation. | The workaround is to restart the Report Application. |
CSCdj12670 | User is not able to plot SRM T3 statistics from Wingz. |
|
CSCdj12734 | Sometimes EMSD core dumps in ILOG R2.1 software. This problem has been reported to ILOG for investigation. The watchdog program will automatically restart the EMSD process. No service impact was found except the core file takes some disk space. | This problem is intermittent and happened to other SV+ processes as well, such as CMGRD and DATA BROKER. (CSCdj12899, CSCdj14467) |
CSCdj15835 | Sometimes the following message appears in the dbroker.log file: "SQLAccess.ec:14145:insert to user connection table failed (-1214)". The root cause of this problem is SWSW sends an incorrect con_obj_id to SV+ (CSCdj15083). | This problem only occurs on adding 2 segment connections. |
CSCdj16290 | Percentage utilization at the remote end point is incorrectly displayed as 0 (zero) in the "Terminating->originating" field in the connection manager modify connection window. | This problem only occurs on two segment connections. You can see the correct % utilization value through the CLI. It is a duplication of CSCdj15564 |
CSCdj08660 | For a UVM connections, Wingz does not show the line number of the connection. |
|
CSCdj15302 | UVM connections are not seen in raw data report's "Object Available" field. |
|
CSCdj09509 | There is a problem of adding FRSM to ASI VBR3 connections. | You will see the value of -1 for %util field on the second SV+ station. (MR972084) |
CSCdj11457 | The ABR.Foresight "rate up" calculation is based on "% to PCR" in SV+ 8.4. However, it is based on "cells per second" in SWSW 8.4. | The decision to use the absolute value for ABR. Foresight "rate up" in SV+ 8.4. (MR972086) |
CSCdj18572 | cmgrd core dumped on hosts scmg2 and sview100 | (MR972279) |
CSCdj10618 | Compiled mibs are not supplied with 8.4.0c | (MR972050) |
CSCdj11735, CSCdj14090 | Can not add connections back after deletion them form some ports. | (MR972093) |
CSCdj10483 | When a FRSM port fails, wrong PVCs fail in eventlog/CMGUI/EMGUI. This problem is due to the SWSW sends incorrect object identifiers. | (MR972052) |
CSCdj08401 | SNMP parameters to be added in service mib for atm support. | (MR971956, MR971870) |
CSCdj08450, CSCdj10723 | Sometimes there was an inconsistency between atm_connection and user_connection tables. | This problem was due to a SWSW problem that failed sending robust messages to SV+ for feeder nodes. (MR971975) |
CSCdj08376 | Unable to change frEndPtchanDEtoCLPmap to ignoreCLP. | (MR971928) |
CSCdj08378 | The slot information were missing from lineAlarm traps in the SV+ Network MIB. | (MR971944) |
CSCdj08387 | The svCmpaErrorTable were not updated for invalid connSubType. | (MR971942) |
CSCdj00196 | There was problem in EMGUI that preventing you from changing frame relay signalling from Annex DNNI to No signal. | (MR971858) |
CSCdj00835 | After adding an ASI to FRSM VBR.3 connection with FGCRA enabled, the u_fgcra field in atm_connection table was disabled. | (MR971866) |
CSCdj09523 | Need to document on how to generate the oid_inf file. | (MR971859) |
CSCdj08398 | There were problems on compiling network.mib, service.mib using MOSY compiler. | (MR971904) |
CSCdj08389 | SV+ database Card table fc_state value is incorrect | (MR971908) |
CSCdj07741 | SV+ database bc_state is not accurate in SV+ database. | (MR971913) |
CSCdj15683 | SV+ database fc_state is not accurate in SV+ database. | (MR972211) |
CSCdj16622 | There was a problem of adding ATM-FR connection using CMGUI to 8.1 nodes. The error message reads "agent reported no such name". | (MR972230) |
CSCdj11865 | The fc_state field in SV+ Card table shows 8 which is missing from SV+ DB schema. | (MR972100) |
CSCdj12254 | SV+ desktop aborts itself when the NWTopology window is closed. | (MR972115) |
CSCdj13313 | The connectionRemOSpaceCells object has value (-1) for all connections. | (MR972149) |
CSCdj13317 | The svConnLocOSpaceCells object in the svConnTable of SV+Servicemib has value (-1) for all the connections. | (MR972150) |
CSCdj10103 | The fc_fw_rev is blank in SV+ database. | (MR971915) |
CSCdj10367 | When starting stand-alone SCM, following error message is shown in the console: "cd /opt/OV/bin/ov.envvars.csh: No such file or directory". ) | (MR971932 |
CSCdj09567 | The column upgrade_status in SV+ network table is blank. | (MR971984) |
CSCdj10189 | The SCM can handle only 2000 /etc/hosts entries. | (MR972028) |
CSCdj14090 | Cannot add or delete PVCs for some ports. | (MR972185) |
CSCdj14231 | The SV+ database says subtype while in manual it is sub_type. | (MR972164) |
CSCdj14089 | SV+ does not show preferred routes at all. | (MR972182) |
CSCdj12802 | Other SV+ will not update % utilization for the IPX connections. | (MR972134) |
CSCdj15595 | The getfwrev function does not work with 8.4.0m (SW) and 8.4.0H SV+ build. | (MR972218) |
CSCsi92972 | The SCM stopped collecting statistics after running more than a day. | (MR971860) |
CSCdj10091 | No line numbers for traps generated from IPX. | (MR972022) |
CSCdj10098 | The trunk status values contained in the SV+ traps look like they are off by one. | (MR972024) |
CSCdj17225 | Line trap(501), slot, idstring, status, severity wrong values (MR972248). The trap (501) involved in this bug is used for the circuit line on IPX/IGX and ASI line on BPX running software version 8.1 or 8.2. In this particular incident, the trap is for an IPX's circuit line, i.e. the T1/E1 line for the frp card. | If user does not have these two objects, this problem won't be seen. Also this trap is sent via RtmProxy so if the system did not register as manager to RtmProxy, it won't see this traps in the HPOV event browser. |
CSCdj17240 | The port alarm (503) has incorrect status/severity values. (MR972249) The trap (503) involved in this bug is used for the frp and ftc ports on IPX/IGX and ASI port on BPX running software version 8.1 or 8.2. | If user does not have these objects, this problem won't be seen. Also this trap is sent via RtmProxy so if the system did not register as manager to RtmProxy, it won't see this traps in the HPOV event browser. |
CSCdj17251 | The trunk trap (502) status and severity has incorrect values. (MR972251) The trap (502) involved in this bug is used for the trunk on IPX/IGX/BPX running software version 8.1 or 8.2. | This trap is sent via RtmProxy so if the system did not register as manager to RtmProxy, it won't see this traps in the HPOV event browser.
|
CSCdj05789 | The SV+ install adds bogus svplus and informix group and user identifiers. | (MR971792) |
CSCdj05991 | Sometimes SvOvTopology dumping cores.
| (MR971834) |
CSCdj15391 | EMGUI does not show line info for ports and PVCs. (MR971849) In SV+ 8.4 EMGUI, the port is displayed as <slot>.<logical_port> and PVC is displayed as <slot>.<port>.<dlci> The port is displayed in the "Configure->Port" screen and the "View->Card/Line Alarm ..." screen. With the fix for CSCdj15391, port is now displayed in this way: <slot>.<logical_port> <slot>.(<line>.<physical_port>) The PCV is displayed in the "View->Card/Line Alarm ..." screen, and with the fix, its now displayed as: <slot>.<line>.<physical_port>.<dlci> |
|
CSCdj19368 | TRAPS in 20k series have wrong values in STATUS field. | If SWSW running is 8.2, it will not generate this trap at all. (MR972290) |
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdj01722 | SV+ database counts and alarm states were not consistent between two SV+ stations. This problem was found once during stress test in the large network. However, follow up tests could not reproduce similar problems. | The inconsistency was in the LCON and routes tables. |
CSCdj01109 | SV+ statsparser core dumped when reading Unix password file (/etc/passwd). | This problem has been reported to Sun Microsystems for investigation. |
CSCdj21534 | The CMGUI takes a long time (about 25 minutes) to show a large number of connections (about 7000 connections) in the connection list. | This problem was found once in SIT. |
CSCdj21366 | Sometimes SV+ port proxy core dumped on handling a nonexistent IPX X.21 backyard. | (MR972342) |
CSCdj17225 | There is a problem of displaying correct Line trap information (501). The information in slot, idstring, status, severity fields are incorrect. trapSeverity is warning(2) when it should be Major (when card is pulled out) trapLineIdString is 255.255 when it should be slot.line No slot number provided. lineStatus is clear (2) when it should be failed (3) | (MR972248) No Workaround is known. |
CSCdj17240 | There is a problem of displaying correct Port alarm information (503). The information in status and severity fields are incorrect. (MR972249) There was no mapping done from value received from switch to value defined in SV+Network mib. There is no Workaround |
|
CSCdj17251 | There is a problem of displaying correct Trunk trap information (502). The information in status and severity fields are incorrect. When trunk (t3) was disconnected from switch, SV+ displayed trunk alarm with status cleared and severity was minor when it was actually failed and major. There is no workaround. | (MR972251) |
CSCdj15683 | The fc_state field is not correct in the SV+ database. | (MR972211)
|
CSCdj15391 | The line information is missing from EMGUI for those cards support physical port scheme. (MR971849)8.4 EMGUI design is different When it shows logical port info. The problem is due to the logical/physical port scheme. In SV+ 82 we were using logical port for both frsm and ausm, so the line info is not needed for any of the channels, since logical port number is unique on a given slot. Now in 8.4 we have changed it back to use physical port ==> line info is needed in this case. | No Workaround. Expect Physical port display like 8.1. |
CSCdj15564 | Sometimes the remote per_util of a connection is stored as 0 in the user_connection table when it should be non zero. | (MR972262) |
CSCdj19368 | There is problem of displaying correct status field information for 20k series traps. (MR972290) In trap 20002 here "Fail OK" is showing as trunkstatus it should be "clear OK". SOme are showing "down" when should be fail. | No Workaround. |
CSCdj19371 | There is problem of displaying correct status and severity fields information for 25k series traps. (MR972290) An AXIS line or port failure, we get the incorrect PVC trap sent (trap # 25000) which indicates a clear PVC. Trap 25001 should have been sent instead. Also, svConnOpStatus and svConnAbitStatus are set to clear in this trap when both should have been failed. Somehow SV+ thinks the PVC is in a clear state when it shouldn't be. | No Workaround. |
CSCdj00196 | You are not able to change the frame relay signalling from Annex DNNI to no signalling through EMGUI. | (MR971858) |
CSCdj11457 | The rate up (RIF) parameter of a ABR foresight connection is not calculated correctly. | (MR972086) |
CSCdj15678 | The nwip_on option for savecnf command does not work with 8.4.01 IPX feeders. | (MR972220) |
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdj25530 | Equipment Manager core dump Code was not checking for ILOG connection existence. Added code to check for the ilog connection.Happens during busy system loads. | No Workaround, but subsystem restarts. |
CSCdj30269 | atmsvc.mib file not current. Some ESP trap related |
|
CSCdj24356 | ATM-FR connection contains different CMAX values. There are multiple problems with ESP traps: atmsvc.mib file is not current. There are some traps which are missing from this file. Old APS traps are not getting deleted from trapd.log due to case difference between trap definition in trapd.log and SV+HPOV.install Four traps defined in trapd.log (StrataCom_trapd.conf) do not match with the trap definitions in atmsvc.mib file. 8029 and 8030 traps were not defined in StrataCom_trapd.conf file. |
|
CSCdj24571 | Testcon fails for atfr connections. Testcon from Connection Manager GUI of SV+ consistently fails. It was found that when configured remote loopback for that connection from CLI Test con always succeeded from SV+. Note that tstcon always succeeded from CLI. | The problem is only in SNMP interface. |
CSCdj27485 | Connection Manager core dumps during multiple requests. cmgrd abnormally exits when multiple requests (add/delete) come in from Connection Manager GUI or ConnProxy simultaneously on one SV+ system. Happens on multiple users/desktops. No workaround, subsystem restarts, can leave database in inconsistent state. |
|
CSCdj29220 | CMgrD should block the addition/modification.CMgrD does not block the requests from its clients and tries to add/mod 8.1 ATM-ATM PVC through SNMP |
|
CSCdj26815 | Cannot drag objects in NWTopology launched from ov. The NWTopology main window does not work properly when launched from a Desktop which is launched from OpenView's StrataCom menu. The following problems were found: 1. No Default Background map. 2. Unable to drag objects in the map. |
|
CSCdj26825 | StrataView Network map background image does not come up. |
|
SV+ 8.4 05 Fixed Bugs
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdj20689 | Sometimes databroker restarted without sending a notification. The databroker will create a file when the "Incomplete" cache has data which have not been written database. The file will be removed whenever the "Incomplete" cache is all written to DB. At databroker start up time, it checks the existence of the file. If the indicator file exists, databroker will generate L1 messages and exit. | You are asked to run the tools/connmiss program to correct any database inconsistencies. No Workaround. |
CSCdj19360 | Sometimes there is a problem of showing correct PVC status in CMGUI and EMGUI/alarm view. The CMGUI failed to show an A-bit problem. There are three root problems. The EMC does not forward AXIS channel alarms to dbroker. The EMSC does not forward the switch conn alarms to databroker if the conn alarm object is originated from the slave side. The databroker does not save the remote conn object id in its cache nor update the user_connection table when the conn update from EMSC is processed. | There is no workaround. |
CSCdj25970 | The SNMP object svFrPortSpeed in 8.4 is not matching with 8.1 for set/get results. One uses units of kbps, the other uses 100 bps. |
|
CSCdj19575 | The trapCardType for BXM-12T3 is not supported in SV+MIB and schema. |
|
CSCdj20902 | Sometimes CMGUI does not show connections of a failed IPX port. ( |
|
CSCdj22291 | Sometimes incomplete connection not showing on CMGUI. This problem is intermittent. The performance enhancement of databroker introduced a mechanism to not immediately write the just arrived incomplete segments to the database but to keep them in an internal cache. Either the connections are completed or the incomplete segments have been aged long enough, they will be written out to DB. However, in the case of a complete connection becomes incomplete (one of the segments was deleted for whatever reason), the incomplete segments should be flushed out to DB immediately. | Note that this problem was fixed together with the DDTS CSCdj20689. There is no Workaround. |
CSCdj38666 | The SV+ Service mib variable nodeGrpPlatform does not support igx-platform. The required changes have been done to RtmProxy process. | There is no workaround. |
1. SV+ 8.4.06 Fixed Bugs
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdj08401 | The SV+ Service MIB should be enhanced to support following ATM parameters: CLPHighThresh, CLPLowThresh, EFCIThresh, IBS and VCQ size. |
|
CSCdj29021 | Sometime the number of user connections between two SV+ stations managing the same network do not match. This problem observed on a 8.2.50 based network only. There were 3 problems identified as part of this bug: Switch was reporting ALMA lines as trunks. There was a separate bug opened against switch software and was fixed. If IGX is a gateway IGX use to send some junk trunk messages. This problem was not there if BPX is a gateway node. bamboo1 was connected to BPX and panda1 was connected to IGX. Because of the junk messages from IGX packet line table was inconsistent between bamboo1 and panda1 SV+ was calculating termination flag for 8.2.5 release which was not correct. | There is no workaround.
|
CSCdj33564 | Sometime the connection states for AXIS connections are showing up as "OK/Abit failed" when they are actually "FAILED/Abit failed". The line on the axis shelf is in alarm state. |
|
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdj01722 | SV+ database counts and alarm states were not consistent between two SV+ stations. This problem was found once during stress test in the large network. However, follow up tests could not reproduce similar problems. |
|
CSCdj01109 | SV+ statsparser core dumped when reading Unix password file (/etc/passwd). This problem has been reported to Sun Microsystems for investigation. This problem was found once in SIT. |
|
CSCdj21534 | The CMGUI takes a long time (about 25 minutes) to show a large number of connections (about 7000 connections) in the connection list. |
|
CSCdj21366 | Sometimes SV+ port proxy core dumped on handling a nonexistent IPX X.21 backyard. |
|
CSCdj17225 | There is a problem of displaying correct Line trap information (501). The information in slot, idstring, status, severity fields are incorrect. |
|
CSCdj17240 | There is a problem of displaying correct Port alarm information (503). The information in status and severity fields are incorrect. |
|
CSCdj17251 | There is a problem of displaying correct Trunk trap information (502). The information in status and severity fields are incorrect. |
|
CSCdj15683 | The fc_state field is not correct in the SV+ database. |
|
CSCdj15391 | The line information is missing from EMGUI for those cards support physical port scheme. |
|
CSCdj15564 | Sometimes the remote per_util of a connection is stored as 0 in the user_connection table when it should be non zero. |
|
CSCdj19368 | There is problem of displaying correct status field information for 20k series traps. |
|
CSCdj19371 | There is problem of displaying correct status and severity fields information for 25k series traps. |
|
CSCdj00196 | You are unable to change the frame relay signalling from Annex DNNI to no signalling through EMGUI. |
|
CSCdj11457 | The rate up (RIF) parameter of a ABR foresight connection is not calculated correctly. |
|
CSCdj15678 | The nwip_on option for savecnf command does not work with 8.4.01 IPX feeders. |
|
CSCdj20689 | Sometimes databroker restarted without sending a trap. |
|
CSCdj19360 | Sometimes there is a problem of showing correct PVC status in CMGUI and EMGUI/alarm view. The CMGUI failed to show an A-bit problem. |
|
CSCdj25970 | The SNMP object svFrPortSpeed in 8.4 is not matching with 8.1 for set/get results. One uses units of kbps, the other uses 100 bps. |
|
CSCdj19575 | The trapCardType for BXM-12T3 is not supported in SV+MIB and schema. |
|
CSCdj20902 | Sometimes CMGUI does not show connections of a failed IPX port. ( |
|
CSCdj22291 | Sometimes incomplete connection not showing on CMGUI. This problem is intermittent. |
|
CSCdj08401 | The SV+ Service MIB should be enhanced to support following ATM parameters: CLPHighThresh, CLPLowThresh, EFCIThresh, IBS and VCQ size. |
|
CSCdj29021 | Sometime the number of user connections between two SV+ stations managing the same network do not match. This problem observed on a 8.2.50 based network only. |
|
CSCdj33564 | Sometime the connection states for AXIS connections are showing up as "OK/Abit failed" when they are actually "FAILED/Abit failed". The line on the axis shelf is in alarm state. |
|
CSCdj33872 | When you perform a MIB walk (a HP OpenView tool) on the svNodeGroup of SV+ Service MIB for an IPX/IGX/BPX node, the process stops at MIB object svNodeGrpName. When performing mib walk on svNodeGroup for an IPX/IGX/BPX node, only trunkGroup and lineGroup mib values are returned and the walk stopped. No values returned for the rest in svNodeGroup: svNodeGrpName svNodeGrpNetName svNodeGrpAlarmState svNodeGrpGateway svNodeGrpActive . . . Only when querying these mib objects individually, user can get their values. This is not happening for AXIS nodes. However there are no values for trunkGroup and lineGroup for AXIS nodes so values returned starting from svNodeGrpName. Is this the right behavior when querying an AXIS node? This problem does not impact SV+ management applications. The workaround is querying these MIB objects individually from HP Openview. Problems is in Agent when it verify the getnext response from RtmProxy, it cannot identify that the scalar after the lineGroup is also belong to the same subtree. This is a generic problem but its not happening in pre-8.4 SV+ version because the mib was not arranged to have sub-groups and scalar mixed in one group. A new function parent_oid_is_subset() is added to perform oid checking and nex_oidtree() is modified to call this new function to handle the checking properly. When you perform MIB walk (a HP OpenView tool) on the svNodeGroup of SV+ Service MIB for an IPX/IGX/BPX node, the process stops at MIB object svNodeGrpName. This problem does not impact SV+ management applications. The workaround is querying these MIB objects individually from HP Openview. CSCdj36017 Sometime cmgrd process core dumps at deleting one segment incomplete AXIS connections. Incomplete connections usually happens after the connection has been built. If the card of one end-segment is removed from the chassis, the end-to-end connection becomes incomplete. Using ConnMgr GUI to add the connection will avoid incomplete connections at build time but not when the connection is in operation.
Sometime cmgrd process core dumps at deleting one segment incomplete AXIS connections. There is no workaround. CSCdj37361 SV+ does not process traps sent from Axis Shelves with IP Addresses defined as X.0.X.X format where X is a non zero number. The impact is you can't assign X.0.X.X format for AXIS IP address.
|
|
CSCdj39399 | The back card type was recorded incorrectly in the SV+ database card table. This problem exists for all back card types. |
|
CSCdj33142 | Following alarms were not available from SV+: BCC restarted due to system reset, BCC restarted due to a power failure, CC redundancy, Y redundancy and communication break for a node. |
|
CSCdj39189 | The SV+ Solaris installation script specifies incorrect device name for CD device and it asks you to rewind CD device. |
|
CSCdj37451 | The Connection Proxy is not able to read the current route information correctly from the logical connection table. As a result, the SNMP get response returns a null string for the current route. |
|
Only those users that are users of SV+ Proxy subsystem should use patch 1.
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdj42728 | 'status' field in 'packet_line' table is being populated with'0' value. The status field will now be correct. | This affected the topology packet_line table and had no visual effect on the SV+ GUI or topology maps. |
CSCdj42760 | Cannot add cons with ICRTO > 8000. The range has been updated to be up to 250 seconds or 250000.
| This affects the Connection Proxy subsystem and the MIB comment. |
CSCdj42722 | Cannot get Physical to Logical map on FRSM connections.
| This problem effects the Port Proxy Subsystem only. |
CSCDj42895 | PortProxy exits under heavy system Loads. | This problem correction only effects the Port Proxy subsystem only. |
CSCdj40772 | CLP Hi/CLP Lo range incorrect. The Connection Proxy needs to support 1 as a valid value for CLP high and CLP low. | The range of CLP-Hi, and CLP-Lo has been changed from 0-100 to 1-100. Accordingly, changes have been made to ConnProxy and the ConnProxy Service MIB. |
CSCdj43616 | Memory config of greater than 256 but less than 512 Megs memory get "Out of Shared Mem" error. |
|
2. SV+ 8.4.07 Patch 2 Fixed Bugs
Only those users that are users of SV+ Proxy subsystem should use patch 2.
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdj42987 | Cannot add FR-FR cons from SV+ 8.4 managing 8.2 network, using ConnProxy. |
|
CSCdj45010 | Cannot modify connection on a FRP card in 8.2 network, when the modify command is given using ConnProxy from a SV+ 8.4 station, other than the one from where the connection has been created. |
|
3. SV+ 8.4.07 Patch 3 Fixed Bugs
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdj45001 | maintlog messages not converted to traps.The maintlog messages are sent directly to eventd, who converts them to traps and sends them ONLY to HOPV (trapd). The robust object alarms, are processed by emsc, sent to eventd, who converts them to traps and sends them ONLY to RtmProxy. | The problem was that the process emsc was checking the status of the robust object alarm with the current status for that object. If they were the same, a duplicate alarm was assumed - even though they could have different "reason" codes. The change/fix is to not do this checking. |
4. SV+ 8.4.07 Patch 4 Fixed Bugs
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdj52243 | packet_line table has corrupted entries. The packet_line (trunk) information is reported to SV+ in two ways. First, topology messages contain packet_line information and are processed by the topod process. Second, there are robust object/alarm messages that are processed by the emsc process. The problem was that the emsc process was sending updates to the topod process, which was causing the topod process to corrupt it's cache and the database.. | The fix is to stop the emsc process from sending packet_line updates to the topod process. |
CSCdj47926 | Database current and preferred route strings missing nodenames | The problem was that the emsd process was corrupting it's cache and the database due to a problem reading large topology messages from the topod process. |
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdj24454 | downld program rejects requests even if it doesn't have any active download sessions. This could happen when there is lot of network traffic generated due to multiple download sessions, and some of the sessions may end up in above state. |
|
CSCdj28230 | Shared memory values for feeder node ids are wrong and also some of the SV+ processes like databroker etc. would suddenly exit with an error. This can happen if Desktop is started before all the links are up or having ESP and/or ACCESS nodes in the network. | The workaround for the wrong feeder ids in the Network with no ESP or Access nodes is to start the SV+ Desktop after all the links have come up. However, there is no workaround if the Network has ESP or Access nodes, and SV+ process like databroker etc. start exiting. |
CSCdj39053 | Using dbexport tool of Informix to export StrataView Plus DB stratacom, results in a failure with 'Illegal Stored Procedure Entry'. All the stored procedures used by StrataView Plus have been updated with the fix. | There is no workaround for the above problem. However, this message can be ignored as it doesn't seem to have any adverse effect on SV+ DB creation. User needs to run /usr/users/svplus/bin/create_sp program manually after importing the DB, if manual DB export and import operations are being done using Informix DBATools.
|
CSCdj40746 | statsmain and statschild processes have been enhanced to validate stats file checksum and re-get file if validation fails. | This problem only happens on BPG/IPX/IGX running software version 8.4 or later.
|
CSCdj41663 | For SCM, statsenablelist.stats & enable.master.81.stats files are changed to use defaults and enable.master.81.stats has been fixed to match with statsenablelist.stats file. |
|
CSCdj41747 | A problem in RtmProxy that walking the lineGroup object in StrataView Plus Service MIB results in "General Failure Error", has been fixed. | This problem happens only, if there is more than one circuit line on the IPX/IGX.
|
CSCdj41775 | The 500 trap, which is sent for connection alarms from BPX/IPX/IGX, has a new value '5' defined for svConnType in StrataView Plus Service MIB and related changes in emsc. The same is done for trap 20000 also. |
|
CSCdj41906 | Unable to disable VS/VD feature for BXM-BXM ABR.1 connection by using Connection Manager GUI nor SV+ SNMP proxy agent. This problem only occurs on BXM-BXM ABR.1 connections. Once such a connection is added through the GUI/Proxy agent, the VS/VD feature of the connection cannot be turned off. The workaround is delete the connection and then create it again with the desirable VS/VD turned off. | INSD process gets restarted due to the above error.
|
CSCdj45470 | A problem in statsparser, where it aborts parsing stats file when there is more than 127 stat types enabled for one object instance, has been fixed. | Workaround for this problem is not to set the percent utilization parameter when adding such connection using ConnProxy. If ConnMgr GUI is used, not to change the percent utilization parameter from its default value of 100. |
CSCdj47539 | Multiple statsparser processes are running at a given instance on a StrataView Plus station. | There are now two differently named processes - statsparser and statsager which are both independently started/stopped by the watchdog process. |
CSCdj49165 | When adding a intra-switch frame relay connection on an IPX/IGX routing node using ConnMgr or ConnProxy, the switch will reject the request if the percent utilization parameter is set to any value other than 100. | This problem now has been fixed in cmgrd. |
CSCdj49244 | The log files of SV+ processes in /usr/users/svplus/log directory show year portion as 100 and ImageDownLoad window from HPOV menu also shows 100 in date stamp of images, when system's date is changed to year 2000. |
|
CSCdj49457 | When INS station icon is dragged into HP OpenView map, the following error message appears on SV+ terminal. "Ilb Error: Function void ::msgPort(InsMsgHeader*) not exported by SVOV949.pid949@daslab8. Ilb Fatal Error: Mismatch between versions of ILB generated protocol. |
|
CSCdj49468 | Clicking the "Refresh" button on the Connection Manager GUI main window after the transition between "Normal" and "ANI/Dial up" modes may cause the GUI process to exit occasionally. | The workaround for this is to first click the "Apply" button to enforce the filter setup before using the "Refresh" button.
|
CSCdj49612 | cmgrd process may get disconnected from databroker process for long time and gets reconnected on its own after sometime. This can happen on networks with more number of feeder nodes. | This problem happened because databroker process is busy reading its messages in the memory sent by topod process, to respond to cmgrd process when cmgrd tried to check its connection with databroker. |
CSCdj50252 | When a MOD(ify) operation is performed on ICRTO value of an existing connection using Connection Proxy the following error is generated "Invalid Value[value] for atmEndPtICRTO" | The only workaround for the above problem is to delete the connection and add it again with desired value of ICRTO.
|
CSCdj50369 | INS ANI Configuration window does not come up when it is started from SV+ menu (option 8), even when INS is installed. | The workaround for this is to open an 'xterm' and run insAniConfig.
|
CSCdj50479 | An intermittent problem in tftpchild process, where uploaded config files in current session are corrupted, if the previous tftp session had error timedout. |
|
CSCdj50752 | Network Topology application shows only the configuration saved date of the saved configuration ID, when it is selected from "Images->Config..." screen. It doesn't show the BRAM ID and Node name information of the saved configuration. |
|
CSCdj50938 | Changing severity of a event twice from Normal - Minor - Normal, in HPOV 4.11 Event Browser using "Actions->Assign Severity" menu options pops out an "Error Exit" window with the following message. " INTERNAL ERROR at: xnmeventCB.C:639. Contact your HP Support representative." and Event Browser exits.
| The workaround for this is to apply HPOV 4.11 patch PSOV_01670 and run SV+_HPOV.install script in /usr/users/svplus directory as user root. The patch PSOV_01670 can be applied by following the procedure given below. Patch can be downloaded from http://ovweb.external.hp.com/cpe/patches and the consolidated patch number for HPOV 4.11 for Solaris 2.x platforms is PSOV_01670. Before executing this procedure, make sure that SV+ and HPOV are not running. Once this patch is downloaded, let us say to /tmp directory Step 1 cd /tmp Step 2 Become root user Step 3 su root Step 4 sh PSOV_01670 Step 5 creates two files PSOV_01670.text and PSOV_01670.tar Step 6 Extract the contents of PSOV_01670.tar using tar command tar xovf PSOV_01670.tar Step 7 Above command creates PSOV_01670.install sub-directory in user's current directory. Step 8 cd PSOV_01670.install Step 9 ./install_patch Step 10 cd /usr/users/svplus Step 11 /opt/OV/bin/ovstart The above command starts OV processes Step 12 ./SV+_HPOV.install The above steps makes sure that SV+ extensions OV are copied properly after the patch installation Step 13 Login as user 'svplus', start running SV+, ovw and check that the above error no more exists. |
CSCdj51047 | Can not add 1-1 redundancy to FRSM-HSI cards on Axis shelf, using SV+ Equipment Manager GUI. | The workaround for this is to use addred command from Axis CLI.
|
CSCdj51831 | When clicking on the NWTopology map on a multiple trunk line to open up a multiple trunks window the following message is displayed on SV+ start-up terminal. "Warning: Name: popup Class: XmForm Top attachment widget for widget named 'list_label' (class XmLabelGadget) must not be null." However, this warning message doesn't effect any functionality of the Network Topology map. |
|
CSCdj52061 | The configuration file for watchdog process, watchdog.conf becomes empty or is completely removed when the SV+ Proxy processes are killed at the same time. The above problem happens only when the proxy processes are killed manually in one kill command or SNMPAgent process is killed before the proxy process. | The workaround for the above problem is not to manually kill these SV+ Proxy processes. Stopping SV+ will terminate these processes without this problem. Another alternative is kill the proxy processes one by one and kill SNMPAgent last. |
CSCdj54165 | Modifying or deleting a PVC might fail with an error message "No SUCH NAME" for certain configured node names. The problem only occurs in cmgrd process, if the node name is configured as "D" or "Dx" where x is any alphanumeric character. | The workaround for this is to change the node name to a string at least 3 characters long or use any character other than 'D' as the starting character. |
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdj32955, CSCdj61939 | An intermittent occurrence of un-readable events showing up in the HP Openview eventlog. However, the Openview trapd.log file does not contain such an event. The workaround for this is to apply HPOV 4.11 patch PSOV_01782 and run SV+_HPOV.install script in /usr/users/svplus directory as user root. Note This patch must be applied if SV+ DB configuration includes multiple disk partitions. | Before executing this procedure, make sure that SV+ and HPOV are not running. Apply Patch PSOV_01782 (after downloading to /tmp) using the following the procedure: Step 1 cd /tmp Step 2 Become root user Step 3 sh PSOV_01782 creates two files PSOV_01782.text and PSOV_01782.tar. Step 4 Extract the contents of PSOV_01782.tar tar xovf PSOV_01782.tar Step 5 Above command creates PSOV_01782.install sub-directory in user's current directory. Step 6 cd PSOV_01782.install Step 7 ./install_patch Step 8 cd /usr/users/svplus Step 9 ./opt/OV/bin/ovstart The above command starts OV processes Step 10 ./SV+_HPOV.install This makes sure that SV+ extensions OV are copied properly, after the patch installation Step 11 Login as user 'svplus', start running SV+, ovw and check that the above error no more exists. |
CSCdj53355 | The Test Delay operation is not available from Connection Manager GUI on a connection with both end points on the same switch (DAX connection). | The workaround for this is to run tstdelay command on switch. As a result of the fix for above problem user will be able to click on 'Test Delay' button in Connection Manager GUI, after selecting a DAX connection. However, the 'Test Delay' may or may not be successful depending on the support by switch for that type of connection. Currently 'Test Delay' on DAX conns is supported by BPX, but not by IPX or IGX. |
CSCdj53956 | EMGUI doesn't show SRM in slot 16 until a node resync. This happens in networks with SV+ 8.4.xx where xx < 09 and Axis FW release 4.0.0x where x < 4. | StrataView portion of fix has been done in Equipment Manager GUI and AXIS firmware release 4.0.04 has AXIS fix. |
CSCdj53960 | After core card switch SRM card can not be configured from Equipment Manager GUI. | The work-around for this is to remove the card entry for that slot from SV+ database and do a node resync from Equipment Manager GUI. |
CSCdj54384 | Modifying PIR parameter value of FR-FR PVC fails as RIF parameter of the connection is not adjustable. The problem is fixed in cmgrd process.
| The workaround for this is to use the CLI on switch to lower the RIF value.
|
CSCdj55784 | When a tftpchild process is killed tftpMgr process kills all the remaining tftpchild process, and restarts them. | This problem has been fixed in tftpMgr process. |
CSCdj55790 | The rtm process is taking longer time to inform topology applications of the DAS/INS station status update (UP/DOWN). |
|
CSCdj57299 | Inconsistent display between AXIS CLI and Equipment Manager GUI clock config screen. | This problem only occurs with release 3 BNM card. |
CSCdj59417 | An intermittent exit problem in statsparser has been fixed. | This happens due to some internal memory corruption. |
CSCdj59754 | Modification of atmEndPointPolicing for ATM endpoints using SNMP Proxy fails. The following variables also have similar problems: atmEndPointNRM atmEndPointTBE atmEndPointFRTT atmEndPointVSVD | This has been fixed in ConnProxy process. |
CSCdj60485 | An unexpected exit problem in emsc process has been fixed. | This can happen if SV+ station is attached to IPX/IGX network with FTM/FTC cards. |
CSCdj60520 | NWTopology process exits in an unexpected manner. | This can happen when user clicks on trunk 2 in the topology map, after double clicking on the same trunk and then clicking on Cancel when 'Trunk Description' window shows up. |
CSCdj60587 | strata.mib doesn't get loaded into OpenView by StrataView install program. | The workaround for this is to load strata.mib using options from OpenView menu. |
CSCdj62505, CSCdj63377 | SV+ processes gets unregistered intermittently with all the AXIS shelves. This happens only in the networks having large number of AXIS shelves with lots of activity. This problem has been fixed in rtm and databroker process. With this fix databroker directly sends you connection traps to trapd and RTMProxy, instead of routing them through rtm. This will reduce the load on rtm and will avoid above problem occurrences. | The workaround for the above problem is to kill snmpcomm process or to stop and start StrataView Plus.The workaround for this is to do a node resync from Equipment Manager GUI after disabling the line. |
CSCdj63341 | After SV+ warmstart, when Connection Manager GUI is started it pops up a message that shared memory is not accessible and the customary node list is not shown. This problem has been fixed in topod process. This can happen on systems where several Network Topology (NWTopology) processes are running and being stopped and restarted. | The workaround for the above problem is to kill all the Desktop processes, bring up one, wait until the node list is seen in Connection Manager GUI, and bring up other Desktops. |
CSCdj63598 | Setting peak interval same as the bucket interval to collect statistics as mentioned in StrataView release notes, will result in Cell Tx and Rx stats collected with wrong value. The documentation problem has been fixed in StrataView release notes. | The workaround for this is to restart collecting stats with a peak value less than the bucket interval. |
CSCdj63905 | Equipment Manager GUI does not reflect the correct color for administrative state on SRM3T3 in release 4 AXIS shelves. | This problem happens because of improper handling of the related trap by emc process. |
CSCdj64646 | Display of the real time counters from EMGUI does not get updated if the port/channel number is changed in the input window. The counters shown are still related to the port/channel previously entered. This problem has been fixed in Equipment Manager GUI. | The work-around for the above problem is to stop and start Equipment Manager GUI.
|
CSCdj65376 | EMGUI real time counter do not match the counter on Axis shelf. | This problem has been fixed in Equipment Manager GUI. |
CSCdj66681 | On certain systems after auto installing StrataView, an attempt to start SV+ fails with message "error - unable to initialize shared memory". | Run the INSTALL program in StrataView home directory as user root after editing the /etc/system file to delete the duplicate entries, leading white spaces, then reboot the system using reboot -- -r |
CSCdj65933 | EMGUI does not show alarms on SRM card in Axis shelf running 4.0.04. This problem has been fixed in Equipment Manager GUI. | The workaround for the above problem is to look at the line alarm, and then go to individual line screen and look at the alarm state. |
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdj70378 | Selecting real time counters display make Equipment Manager GUI to terminate in an unexpected manner. This problem has been fixed in Equipment Manager GUI. This happens only if the channel counts are selected before the port counters. | The workaround for the above problem is to select and display port counters before the channel counters. |
CSCdj70855 | An intermittent and unexpected exit problem has been fixed in emc process. |
|
CSCdj69756 | PortProxy process intermittently returns wrong value for the variable svPortCardType, for the GET requests. | This problem only happens if the GET request contains variables from multiple tables. |
CSCdj67625 | PortProxy process returns incorrect results for svPortAlarmTable variable, if a get next query is done for ports on AXIS FRSM-8 and FRSM-HS1 cards.\ |
|
CSCdj68460 | PortProxy process doesn't show status of AUSM-8 ports, if a snmpwalk is done on svPhysicalToLogicalMapTable. | This problem has been fixed in PortProxy |
CSCdj71053 | SV+ INSTALL gives error messages like 'grep: cannot open /tmp/swap.*' etc. This happens only in SV+ DB configurations where there is more than one disk involved. | To create a dummy file (0 byte) with the same name as it is shown in the error message, without interrupting the INSTALL. This can be done from a different terminal and it has to be done whenever the error message is shown in the INSTALL window. |
CSCdj71731 | A problem with Connection Manager GUI where it shows incorrect user connection status and also fails to show some of the connections has been fixed. This happens when you delete a channel on AXIS shelf where there are some more channels on the same slot with the same physical port number and DLCI. | The workaround for the above problem is to do a node resync operation on the AXIS shelf from Equipment Manager GUI.
|
5. SV+ 8.4.09 Patch2 Fixed Bugs
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdj62427 | Connection status and Abit status shown in Connection GUI, doesn't match with their status on the switch or axis shelf. | This happens usually if the connections are added when the axis shelf is under LMI failure. |
CSCdj66288 | A problem in topod process, which causes SV+ database inconsistency by leaving some of the deleted trunks in the database has been fixed. This happens only if trunks are deleted using 'deltrk' command on CLI, when SV+ is down and not using 'dntrk' command after 'deltrk' command. | Workaround for this problem is to do 'dntrk' command on the spurious trunks using CLI.
|
CSCdj66348 | A problem in ConnectionManager GUI, where it incorrectly shows ICR TO ADTF unit in seconds, has been fixed. | This is shown in both ATM-ATM ABR.FS and ATM-FR ABR.FS provision windows. |
CSCdj69172 | A problem in topod process, where it leaves some entries in the trunk table of SV+ database with no endpoints or wrong endpoints. | This only happens if trunks are moved on the network (by holding one endpoint constant and changing other), while SV+ is not running. |
CSCdj71795 | Functional inconsistencies between some of the objects in SV+Service MIB and EquipmentManager GUI have been fixed. | The fixes have been done SV+Service.MIB and PortProxy process. The updated MIB objects are svFrPortCLLMEnable, svFrPortCLLMTimer, svFrPortAsyncUpd, svFrPortPollVerTimer, svFrPortErrThresh, svFrPortMonEveCnt, svFrPortLinkTimer, svFrPortPollCycle. After these modifications the above attributes on a port are no longer modifiable through PortProxy, if the signaling protocol on the port is disabled. |
CSCdj72220 | Inability to change CLLM transmit status timer alone for FRSM cards using EquipmentManager GUI. This problem has been fixed in EquipmentManager GUI. | Disable CLLM first using AXIS CLI and then enable it and change the Xmt status timer at the same time. |
CSCdj72989 | An attempt start SNMPAgent from SV+ menu results in the following error messages. " Unable to start SNMPAgent Unable to start ConnProxy Unable to start PortProxy Unable to start DasProxy Unable to start RtmProxy" | This happens only if SV+ INSTALL programming has been run after installing SNMPAgent software. The workaround for this is to run INSTALL_AGENT program in /usr/users/svplus directory as user root. |
CSCdj73910 | Inability to delete INS node from a HPOV map. This problem has been fixed in topod process. | This problem happens only if INS and INSD nodes are added in one session of HPOV, and trial to delete INS node made after stopping and starting SV+. This results in "No active INSD present. Can't delete INS node" error message. |
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdj64669 | smic compiler complains about some syntax errors with axis.mib file in /usr/users/svplus/mibs directory. SV+ now ships smicng, necessary RFCs and scripts to compile mibs. Files and directories included in this patch are: /usr/users/svplus/bin/compile_mibs_with_mosy /usr/users/svplus/bin/compile_mibs_with_smicng /usr/users/svplus/tools/smicng /usr/users/svplus/tools/mosy /usr/users/svplus/mibs/rfcs/ /usr/users/svplus/mibs/*.MIB | To compile SV+ mibs using smicng compiler follow these steps: . login as svplus . cd /usr/users/svplus/mibs . run compile_mibs_with_smicng Output files generated under /usr/users/svplus/mibs/ with suffix .smicng |
CSCdj70381 | Connection Manager GUI does not reflect correct connection status of AUSM 8T1. This problem has been fixed in emc. | The connection manager shows either a "OK" or "OK/A-Bit Alarm" status on the connections instead of "Fail/A-bit" status. if a LOS is caused on a port on 8T1 AUSM.
|
CSCdj76442 | SV+ INSTALL gives error messages like "'/usr/sbin/prtvtoc -h $i | awk '{print $5}': Ambiguous input" etc. | This happens only in SV+ Patch1 or Patch2 configurations and only if non meta devices (no /dev/md/* /dev/vx/*) are used to configure DB partitions. |
CSCdj77420 | An enhancement has been done to Connection Manager GUI to include logical and the corresponding physical port information for the all the port types, in SlotPortHelp list. Prior to this enhancement, the SlotPortHelp list used to display all the FRSM ports in physical notation i.e., <physical line no.>.<Starting DS0 channel no.>, and all the other ATM/FR/CE ports in logical notation. | The work-around for the above exists only for Axis shelves. For Axis shelves one can always invoke Equipment Manager GUI to display the port list of a selected slot. The port list includes both the logical and physical notation.
|
6. SV+ 8.4.09 Patch4 Fixed Bugs
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdj72186 | An intermittent unexpected exit problem with tftpmgr process has been fixed. | As a result of this problem, the tftpmgr will be seen restarting in watchdog.log file. |
CSCdj79397 | A problem in emc process, which causes DB inconsistency has been fixed. The above problem causes SV+ DB to have multiple entries in connection table with same node.slot.port.dlce and when only one of them actually exists on the node. This problem happens only if connections are added or deleted when SV+ is down. | Stop SV+, recreate SV+ DB, then restart SV+. |
CSCdj80656 | An intermittent and unexpected exit problem with emc process has been fixed. | The above problem has been observed with SV+ 8.4.09 Patch2 software. |
CSCdj80718 | A problem in emc process, which causes SV+ DB inconsistency by showing some of the deleted connections in user_connection table but not in connection table. The above problem has been observed with connections on Axis FRSM cards. | To correct this problem: Step 1 Stop SV+ core, run conmiss program in /usr/users/svplus/tools directory, and re-start SV+ core Step 2 Stop SV+ core, re-create the database, and re-start SV+ core. |
CSCdj81657 | A problem in emsc process, where it updates card table in the SV+ DB with a erroneous value '0' for the card state value. | This has been observed with BNI/BXM cards only. |
CSCdj81658 | An internal problem in Connection Manager GUI process has been fixed for it not to depend on the line values from the frp table for error checking of FRP/FRM/UFM ports. | As a result of this problem FRP ports are not shown in SlotPortHelp screen. |
CSCdj81728 | The real time counters screen in Equipment Manager GUI gives incorrect value for AIR in frsm port counter. | This problem has been fixed in Equipment Manager GUI. |
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdj59952 | When using the MIB browser in HP OpenView for BPX node in the StrataView map, the nodename is postfixed -bpx. As a result, MIB browser doesn't understand if this name is given. In release SV+ 8.4.10 in the routing level map, all bpx nodes label and selection names are constructed from node names suffixed with "-hub". In the feeder level map, the label and selection name of the core shelf are the same as the node name. User has to select the core shelf for the bpx node in the feeder level map to launch Mib Browser. For IPX, IGX and AXIS, user can select the respective node and launch Mib Browser. The name/ip address displayed in the MIB Browser will be correct. | As a work-around for the above problem the core shelf for the bpx node can be selected from the feeder level map. Then from the Misc menu, if SNMP Mib Browser is selected, the name/ip address displayed in the MIB Browser will be correct. |
CSCdj68473 | Statistics for FRM/CVM T1 circuit line can not be collected. | This problem has been fixed in statsparser. |
CSCdj69022 | The mib object svFrPortStartingCh in the svFrPortTable is listed as "Read/Write" for FRSM-4, FRSM-8 and FRSM-HS1 card. However, no matter what value you set on svFrPortStartingCh, the value you get back on snmp get is always the same as that of svFrPortPort. Similar problem exists for svFrPortLine. In this case, the value returned is that of svFrPortLineIndex. | This problem occurs when attempting to set the mib objects svFrPortStartingCh and svFrPortTable on AXIS FRSM-4, FRSM-8 and FRSM-HS1 card using PortProxy process. These problems have been fixed in PortProxy process and SV+Service.mib. |
CSCdj69146 | An intermittent problem in cmgrd and databroker processes which blocks PVC provisioning. The problem only occurs when PVC provisioning is happening non-stop while the databroker process is busy processing topology messages or alarm messages. | Warm start of the SV+ core will gracefully cause the back-end to recover. |
CSCdj70786 | The snmpcomm process might exhaust its resources intermittently and block you from performing test con/test delay through Connection Manager GUI. This problem only occurs when a relatively large no. of Connection Manager GUI's were restarted after running test con/test delay operation. | The work-around for this problem is stop and start SV+.
|
CSCdj72187 | An intermittent exit problem in configSave process has been fixed. | This problem happens only if configSave receives a SIGTERM signal. This could be caused by exiting HP-OV ovw while configSave is still running. |
CSCdj72188 | An intermittent abnormal exit problem in Equipment Manager GUI process has been fixed. | This problem has been observed to be happening usually after using real time counter screen for long time, to view counters on Axis AUSM and FRSM cards. |
CSCdj72753 | The documentation error regarding atmEndPointMinAdjustPeriod object in SV+Service.mib has been fixed. | The range now has been changed to 3 to 255. |
CSCdj72953 | When the selected/highlighted connection on the Connection Manager GUI main window has a change of state event, the PVC would become deselected/un-highlighted. This problem has been fixed in Connection Manager GUI. | Select/highlight the connection.
|
CSCdj73570 | Setting up or updating a ATM-ATM/ATM-FR connection using ConnProxy process fails, if atmEndPointMBS parameter given is more than 24000. |
|
CSCdj75824 | Enumeration for 4001 was missing from trapReason field in SV+Network.mib. So when "Power supply clear" (defined as 4001) TRAP was sent to user from SV+ with 4001 reason field value, he/she could not map it to any value. | This has been fixed in SV+Network.mib file by defining 4001 as "Power supply clear" reason field.
|
CSCdj77436 | SCM may not collect statistics files 12 collection cycles back if the history files are set to >= 12. | This problem has been fixed in statsmain process.This problem only occurs if the number of history files to collect is set to >= 12. |
CSCdj78846 | Unable to collect the several groups of statistics via TFTP from BXM trunk lines when selected from SV+ stats manager. Further explanation of the problem:
|
|
CSCdj82171 | The percent utilization value reported by the Connection Manager GUI/Conn Proxy Agent might be reported as -1 occasionally. This problem has been fixed in databroker process. | This problem only occurs when the 8.4 SV+ is managing an 8.2 network.
|
CSCdj82198 | An intermittent problem in the cmgrd and databroker processes which blocks the PVC provisioning process. This problem only occurs after the Connection Manager GUI was exited and restarted more than 200 times. | As a work-around for the above problem, a warm start of the SV+ core will gracefully cause the back-end to recover.
|
CSCdj82416 | An intermittent abnormal exit problem in ConnProxy process has been fixed. | This problem is experienced when the SNMP Agent gets detached from ConnProxy, and subsequent reconnection fails during SV+ shutdown. |
CSCdj82504 | The time stamp of traps from RtmProxy is different when its first received as compared to the recovered trap. | This problem has been fixed in RtmProxy process. |
CSCdj84308 | Wingz Raw Data Report shows multiple "line 255" entries for T1 service line. | This happens only if the node has multiple FRP-T1 cards. This problem has been fixed in util_ext process and Wingz command files. |
CSCdj84552 | An intermittent problem in Connection Manager GUI where complete connections will be shown as incomplete, has been fixed. The above situation occurs when the ILOG connection between emd and databroker gets into an invalid state which makes emd think that it is not connected to databroker. As a work-around for this, emd process can be killed, which will eventually be started by watchdog process.
|
|
CSCdj84905 | The "Total Cells Tx to Line" stat is not supported in AXIS shelf for trunk/line. AXIS shelf only supports this stat for port. The "ATM Cell Header HEC Errors" stat is supported in SCM as well as in the AXIS shelf. |
|
CSCdj85874 | BXM port status will not get updated in the asi_port table for BXM cards except for BXM having card type 117. Also, there won't be any BXM port alarm generated by SV+. | This problem has been fixed in emsc process. |
CSCdj87239 | Trunk comments get truncated periodically. | This problem has been fixed in NWTopology process |
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdj89037 | statsparser process fails to parse stat files collected from AXIS shelves with the following error message in /usr/users/svplus/statsmgrdir/statsparser.err file. "Mar 17 17:17:00 ERROR:0 statsparser.c@668: FILE ABORTED: File:/usr/users/svplus/incoming/<axisnodename>.0317981700 Mar 17 17:17:00 ERROR:0 BinaryProcessor.c@258: Parser Template Node Not Found for Binary Statistics File Record Entry" | This problem happens only with release 4.0.09x Axis shelves. |
CSCdj83305 | A DB inconsistency problem in user_connection table related to ungroup connections has been fixed. | This problem can happen if connection un-grouping activity involving CLI and SV+ Proxy agent for same set of connections is done simultaneously. |
CSCdj89395 | In Equipment Manager GUI view counter screen, the last Unknown DLCI for frport counter is shown incorrectly. | This problem has been observed with Axis FR cards in StrataView 8.4.10 Equipment Manager GUI. |
CSCdj89609 | Strata View Plus Equipment Manager GUI shows BNM Clock Source as AUM Inband instead of BNM Inband. | This problem has been observed with Strata View 8.4.10 manager Axis shelves with release 4 or higher BNM cards. |
CSCdj89825 | When a SNMP GET operation is done on the ServiceMib object svPortIfType and svAtmPortIfType for a port on a BXM-12T3 or BXM-8T3 card, the Port Proxy Agent returns the wrong value of 16 which is oc12-smf. The correct value should be 4 for t3. | Similar problem happens to BXM-8E3 and BXM-12E3 cards also, for which the correct value is 5 for e3 |
CSCdj91893 | OpenView trapd.log file shows some Axis traps in no defined format. This could happen if traps from axis.mib are loaded (using OpenView menu options etc.), prior to StrataView installation. This has been observed in StrataView 8.4.10. | The work-around for the above problem is available only for Axis traps 50120-50123. Login as root and run following commands from /usr/users/svplus directory # /opt/OV/bin/xnmevents -delete dsx1LineNoAlarmTrap dsx1LineInAlarmTrap\ dsx1LineLpbkEnableTr dsx1LineLpbkDisableT # cd /usr/users/svplus # ./SV+_HPOV.install |
CSCdj92179 | The operation for modification of preferred route only through SV+ connection proxy agent is deemed not efficient. | A performance enhancement targeted to this specific operation has been done in topod, ConnProxy and cmgrd processes. |
CSCdj94084 | The cmgrd process exits intermittently at the time of processing the PVC deletion request. | The problem only occurs when the databroker process is busy processing connection or alarm messages from the network. |
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdj52072 | Connection Manager GUI does not allow value=0 for %util parameter on BXM card with serviceType=UBR. The problem exists for connections UBR.1 and UBR.2 service types involving BXM cards. | A work-around for this is to use CLI to modify the %util value to zero. |
CSCdj81917 | A problem in Connection Manager GUI where the range check done for TRM parameter is wrong. The correct range for TRM parameter for BXM card is 3 to 255. | A work-around for this is to use CLI to modify TRM parameter if a value more than 100 needs to be set. |
CSCdj83876 | The Connection Manager GUI does not allow the CDVT(0+1) parameter to have a value larger that 250,000 micro seconds for BXM ports. The maximum value supported by the BXM cards is 5,000,000 micro seconds. | As a work-around for the above problem BPX CLI can be used to adjust the CDVT(0+1) parameter if the value > 250,000 usecs is desired.
|
CSCdj88856 | A problem in configSave which causes Configuration Save operation on a Axis shelf to never complete, if a card is in failed state has been fixed. | A work-around for this is to abort the operation using Abort button on Configuration Save window. |
CSCdj89426 | A StrataView DB inconsistency problem in user_connection table has been fixed. These inconsistent connection records do not get updated or deleted. This problem happens if the card on which connections are being set, using Connection Proxy agent, gets reset. If this reset causes the agent to fail the addition of one of the connection segments, then StrataView back-end can leave this connection in a pending state. | This happens when StrataView back-end tries to back off already added segments. This problem has been fixed in databroker, cmgrd, Connection Manager GUI and Connection Proxy processes. |
CSCdj80624 | The status of a trunk in the packet_line table of SV+ DB is inconsistent with the status displayed in the CLI of the switch. The packet_line table is written to by both topod and emsd although to update different sets of attributes. But this may at times create the scenario that when either of them is writing the other also tries to write which fails and as a result the database may not get update with the correct values for some of the attributes (trunk status in this case). This gives rise to database inconsistency. | This problem has been fixed in topod and emsd processes by introducing retry mechanism for DB writes. |
CSCdj85527 | SV+ install script overwrites the perl executable in /usr/local/bin with the version bundled with StrataView media. This problem has been fixed SV+ INSTALL procedure. | A work-around for this problem is to save the existing copy of perl before the install and restore it back in /usr/local/bin after StrataView installation. |
CSCdj88324 | If time Sync to a node times out the next node from the node table in the same subnet is tried as alternate time sync host. While trying this the type of the node is not checked (routing/feeder). | This problem has been fixed in statsmgr process. This problem happens only when there are ESP nodes in the network. |
CSCdj89302 | When statistics collection is in progress SCM does not warn you while exiting that statistics collection will be stopped upon exit. |
|
CSCdj93368 | A problem in emc process which causes SV+ database inconsistency, where complete connections are shown as incomplete. This problem happens in the following scenario: After setting up the 1-N redundancy, if the primary card has failed, and the secondary is actively protecting the primary card, and if you remove the primary card from the shelf, then the primary card configuration will be missing from SV+ database, which causes database inconsistency. However, if the card is still in the shelf, in whatever state, the configuration will remain there, since logically the card is still in active state. | The work-around for the above problem is to put the primary card back in the slot and to do a node resync from Equipment Manager GUI. This problem has been observed in SV+ 8.4.10 with AXIS Service Module Release 4 or later. |
CSCdk01192 | When adding a BXM or ASI port that is already existing, the error message in the error table is incorrect. The error message reported the wrong port with a bogus shelfName, in the format "Port routingNodeName.shelfName.slot.port already exists". The correct error message should not have the shelfName. | This problem has been fixed in PortProxy process. |
CSCdk011943 | For RedundancyActivated trap (50045) and RedundancyReverted trap (50046) from AXIS, OpenView event browser shows incorrect primary and secondary slot numbers. Same problem appears in trapd.log file. Trap 50045 is generated when primary slot fails and secondary becomes active. Trap 50046 is generated when primary slot is active and secondary goes to standby. | To work-around this problem, complete the following steps: login as root Stop OpenView by typing /opt/OV/bin/ovstop and hit return Type /opt/OV/bin/xnmevents -delete RedundancyActivated and hit return Type /opt/OV/bin/xnmevents -delete RedundancyReverted and hit return Type /opt/OV/bin/xnmevents -load /usr/users/svplus/OV/conf/C/StrataCom_trapd.conf and hit return Start OpenView by typing /opt/OV/bin/ovstart and hit return logout as root Run ovw as svplus user |
CSCdk02141 | In Connection Manager GUI the default value (disable) shown for FBTC for UBR and ABR service types is wrong. This problem has been fixed in ConnMgr process. |
|
CSCdk05539 | A problem in PortProxy which makes ASI port provisioning with OC3-SMFLR backcard not possible, has been fixed. |
|
CSCdk07105 | When trap 50045 is received, the HPOV event browser dumps the varbind list instead of trap description string. | This trap is generated when secondary card becomes active as the primary card fails. |
CSCdk07451 | For userLogoutTrap (55021) from axis, OpenView event browser shows incorrect value in user field. |
|
CSCdk09192 | A problem in configd process which makes the loadcnf command given from BPX/IPX/IGX CLI abort has been fixed. This could happen if IP network is prone to drop packets. When configuration packets going from SV+ to a switch get dropped, the retry (retransmission) mechanism in SV+ does not work & loadcnf aborts. | The work-around for this to use loadcnf command on the switch when the network is less used.
|
CSCdk09486 | A database inconsistency problem related to user_connection table has been fixed in emsc process. Because of this problem entries in user_connection table do not match with status on network and atm_connection table. This problem could happen if addition and deletion of connections on the same switch are done at a rapid rate or when SV+ is down. | As a work-around for this problem SV+ database can be re-created and SV+ can be started.
|
CSCdk10508 | A database inconsistency issue related to logical connections has been fixed in emsc process. SV+ database table logical_conn contains rows that do not correspond to any existing connection. These rows are leftovers from connections that have been deleted. This problem can happen if connection addition & deletion is performed while SV+ is down or if SV+ is up but the network is busy. | As a work-around for this problem SV+ database can be re-created and SV+ can be started.
|
CSCdk11108 | SV+ SNMP proxy returns no variable found, when a query is made on mib variable svMapLogicalPort for non-channelize frsm-8 card. | This problem has been fixed in PortProxy process. |
CSCdk12069 | Node resync operation in Equipment Manager GUI fails with Axis shelves running release 4.0.13 software. | This problem has been fixed in emc process. |
CSCdk14426 | An occasional abnormal exit problem in cmgrd process has been fixed. |
|
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdj63905 | Equipment Manager GUI does not reflect the correct color for administrative state on SRM3T3 in release 4 AXIS shelves. This problem happens because of improper handling of the related trap by emc process. | The problem has been fixed in both Axis firm-ware and Strataview releases. Axis fix is release 4.0.13 or later. The workaround for this is to do a node resync from Equipment Manager GUI after disabling the line. |
CSCdj84198 | The treatments of failed connection in the case of TestConn and TestDelay by Connection Manager GUI and Connection Proxy Agent are not consistent. When the connection is in the "Failed" state, the GUI still allows the Testcon and TestDelay operations to be performed on the connection. However, the proxy agent would not attempt the operations, but instead, generate an general error. | To resolve the inconsistency, the ConnProxy has been changed to allow the TestConn and TestDelay buttons when the PVC is in the failed state.
|
CSCdj88137 | TestConn returns erroneous data in SNMP for FR-ATM PVC. The returned values do not match with the values described in SV+Service.mib file. This problem has been fixed in ConnProxy process. | This problem occurs if a TestConn is executed for a FR-ATM connection from the ATM end and if the test is successful, the test result returned actually contains the delay, a positive integer value, rather than the expected 0. As a work-around for this any positive value returned can be considered as success. |
CSCdj88286 | ConMgrGUI does not allow TestConn for ATM-FR 2 segment connection when ATM side is chosen as the local end, whereas ConnProxy always allows TestConn for this type of connection. This is not a problem and this is a implementation issue. The implementation details are given below. ConMgrGui and ConnProxy has different implementation of Test Connection and Test Delay for ATM-FR 2 segment connection. In case of ConMgrGUI, it initiates the test con or test delay from the local end of the connection displayed in the main window. If the local end is chosen at the ATM side, it does not allow Test Conn. It only allows Test Delay. If the local end is FR, it supports both TestConn and Test Delay. However, ConnProxy initiates the test con or test delay from the master end of the connection. For ATM-FR 2 segment connection, the master end is at the ATM side. Though the ATM side does not support Test Conn, ConnProxy initiates Test Delay and reports that Test Conn has been performed and maps the result accordingly. To do TestConn for this type of connections from ConMgrGui, user needs to make FR end as the local end using the filter. |
|
CSCdk11895 | Equipment Manager GUI displays incorrect values for rcv/xmt AIR counter values for FR-channels, in the view counter screen. | This problem happens if the network has Axis 4 shelves with FRSM-4 cards and SV+ is 8.4.09, 8.4.10 or 8.4.11.
|
CSCdk13155 | In a redundancy card setup, when a secondary card takes over in primary card failure situation, no new ports or PVCs can be added to the primary card, if the primary card is pulled out. This problem has been fixed in emc process. | This problem has been observed with SV+ 8.4.11 and prior releases managing release 4.0.12 or later Axis shelves. |
CSCdk13162 | StrataView node resync with axis shelves fails. This problem happens only when any redundancy action occurred like softswitch, primary card failed or pulled out. | In such cases the SV+ database will be out of sync with axis shelves. This has been observed with StrataView 8.4.11 managing Axis 4.0.13 shelves. This problem has been fixed in emc process. |
CSCdk14193 | When line distribution is added or deleted using SNMP Agent or from Axis CLI, the change is not updated in Equipment Manager GUI. | As a work-around to this problem, node resync can be opted from Equipment Manger GUI. This will update the GUI with line distribution status. |
CSCdk14782 | An intermittent exit problem in Desktop process has been fixed. | This problem has been observed when SV+ processes are stopped while Desktop is running. |
CSCdk14790 | Intermittently ILOG error message is displayed on the SV+ terminal mentioning that ConnMgrGUI can not communicate with the databroker process. This happens when the databroker is busy processing messages and the ConnMgrGUI is trying to send a request to the databroker during this period. | This is not an error and user can make ConnMgrGUI to retry communicating with databroker by clicking on Apply button. |
CSCdk21314 | The equipment management subsystem (emd, emc processes) and DataBase schema have been updated to support the new card state reserved in Axis releases 4.0.16 onwards. Axis send this reserved state if a card is pulled out from its slot. In Equipment Manager GUI a card in this state will be shown as empty slot. |
|
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdk10837 | Equipment Manager GUI shows the secondary slot as empty after the cold start even though the primary card is covered by the secondary card. It should show the secondary as activated. This problem has been fixed in emc process. When primary and secondary cards are setup and then primary card is removed and secondary is activated while SV+ is running, Equipment Manager GUI shows the secondary card as empty and the primary card as covered slot. If SV+ is stopped and cold started, Equipment Manager GUI still shows the secondary slot as empty. This happens for secondary FRSM8 cards with no back card only. Further Problem Description:While investigating this problem, a problem similar to this and applies to all types of cards was found. In this case Equipment Manager GUI shows the primary slot as empty after the cold start even though the primary card is covered by the secondary card. It should show the primary card as covered slot. | This problem can happen in the following scenario. When primary and secondary cards are setup and then primary card is removed while SV+ is running, Equipment Manager GUI shows the secondary card as active and the primary card as covered slot. If SV+ is then stopped and restarted after creating SV+ database, Equipment Manager GUI shows the primary slot as empty. As a work-around for this the primary card can be inserted back into the slot. |
CSCdk15349 | StrataView topology shows virtual trunks/or broken lines (...) when no such trunks exist. | This has been fixed in topod process. |
CSCdk18847 | validate_image tool does not detect corrupted bpx/ipx/igx firmware or software images. | This problem happens only in Rel 8.4 onwards if the image files are corrupted by some appended data. In this case validate_image does not compare the actual file size with recorded file size but switch will fail as the files are corrupted. |
CSCdk19688 | In Equipment Manager GUI When SRM 3 T3 line is enabled from disabled state, Equipment Manager GUI doesn't show the update. This problem occurs very intermittently. | As a work-around for this problem 'Display Shelf View' button can be clicked to see the updated status of the line. |
CSCdk22603 | SCM appears to get stuck when it is trying to reach timesync host. This problem could happen in either of these conditions. Time Sync host is not reachable Network responds after a period close to the (sync with timesync host) retry time. This problem has been fixed in statsmain process. With this fix the default retry time to sync with timesync host is 5 minutes and this can be set to anywhere from 4 to 14 minutes by a environment variable TIMESYNCPERIOD. Further Problem Description There was a problem in the way the time sync host was contacted by SCM. If the time sync host was unreachable then a particular host may kept on gutting retried. | When this problem happens one can exit SCM and set this TIMESYNCPERIOD to a value more than network response time for timesync host status and then start SCM. This time if timesync host is not reachable, you will be able to change the timesync host from SCM in NodeConfig parameters.
|
CSCdk24102 | Maintenance logs (event logs) on switches are logged but do not immediately appear in HPOV event browser. Sometimes the delay is very significant, i.e.,in hours. Traps may seem to be bursted into HPOV event browser every 2 to 3 minutes. This has been fixed in eventd process. The problem occurs when a new switch is added to the network, but not yet added to SV+ workstation(s) local /etc/hosts file or on the DNS server. The problem also occurs whenever the entire network status changes. | An entry with node name "NETWORK" (all capital letters) and a dummy IP address can be added to SV+ workstation(s) local /etc/hosts file (or to SV+ system(s) hosts database if /etc/hosts is not consulted by system running SV+). Prior to introducing a new switch to the network, the node name and its IP address should be added to the SV+ workstation(s) local /etc/hosts file( or to SV+ system(s) host database if /etc/hosts is not consulted by system running SV+). If for whatever reason, the symptoms occur, try to "ping" all the nodes and node "NETWORK" from the SV+ workstation(s). If any node is unreachable, add the node name to local /etc/hosts file ( or to SV+ system(s) hosts database if /etc/hosts is not consulted by system running SV+). |
CSCdk24394 | If softswitch command is executed on CLI to switch primary card to secondary card in redundant card setup, the PVCs on primary card are stayed in failed state on SV+ CMGUI. even though the PVCs on AXIS shelves and switches are in clear state. This problem has been fixed in emc process. | As a work-around for this problem, StrataView can be cold started (clearing the DB and restarting SV+).
|
CSCdk28135 | Checksum error is shown in statsmain error log even though the collected stats file is not corrupted. This problem has been fixed in statschild and statsparser processes. Further Problem Description The child process on getting the stats file validates it using the checksum at the end of the file. When this checksum straddles two blocks of size 4096, StrataView checksum computation procedure breaks down and flags the file as corrupt.
| This problem occurs when the collected stats file is of such a size such that the checksum straddles two blocks. Each block is assumed to be of size 4096. |
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdk33001 | StrataView SCM or stand-alone SCM fails to complete statistics collection from switches running 8.4.X SWSW. This problem has been observed only on system with StrataView 8.4.11 Patch 2 stand-alone SCM 8.4.11 Patch 2 installed and when SCM is enabled to collect statistics from switches running 8.4.X SWSW. | As a work-around to this problem, user can reinstall StrataView 8.4.11. |
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdj73647 | When SV+ Desktop fails to start, the error message given is not clear. The message includes two possible reasons for the failure. SV+ can't determine the actual cause of the problem. It could be one of the two reasons shown. Hence, that message. | The misspelled words have been corrected. |
CSCdk12201 | User connection is not reset back to OK state when connection is re-established. This problem has objserved on CESM-CESM connections in SV+ 8.4. | This problem has been fixed in Connection Manager GUI process. |
CSCdk12929 | StrataView Plus Connection Manager GUI only allows the range 1..24,000 cells for the parameter MBS of the BXM cards. BXM cards support the range 1..5,000,000 cells for MBS. | This problem has been fixed Connection Manager GUI process. |
CSCdk13002 | Equipment Manager GUI doesn't allow to filter on line 4 of FRSM-HS1 card, even it has 4 lines. It comes up with a error message "Field:line number: The filed you entered has a range of 1 to 3. Please re-enter the field". The FRSM-HS1 supports two different types of back cards. This problem is only applicable to the situation where the back card is X.21(i.e. 4-lines). | This problem has been fixed ConnProxy process. |
CSCdk21635 | Non existing trunk appear intermittently on SV+ Topology and HPOV Topology maps. This problem has been observed in SV+ 8.4 usually after swithcc operation is done on 8.4 SWSW network. T | he problem has been fixed in topod process. |
CSCdk30217 | Different SNMP community strings other than the default settings are not supported for VNS. VNS is shown as unreachable on SV+ if the SNMP community strings on VNS are changed from default. | This problem has been fixed in rtm process. |
CSCdk30572 | When a VPC is created through ConnProxy it fails with error message "Invalid variable type,length or value". Since the VPC does not have a specific vci, it is stored in the SV+ DB with vci=65537. Hence, this error. This problem can also be seen whenever a SNMP get operation is done on the endpoints of the VPC connection, or when a SNMP next or SNMP walk kind of operations are done. |
|
CSCdk33893 | Port speed can't be set for X.21 type ports on frp/frm card on IGX/IPX switches, when the port is brought up for the first time. This problem has been fixed in PortProxy process. With this fix user will be able to specify the port speed for X21 type port, when it is brought up for the first time. However, you must not try to modify the portspeed after that. Note For V35 ports, user can modify the port speed later also |
|
CSCdk36034 | Unknown line interface is reported by SV+ whenever trap 20001 is received. This trap is received whenever a line cable is pulled out and line alarm is generated. When a line alarm occurs, SWSW sends SV+ robust alarm message. The interface varbind in 20001 trap sent out by SV+ contains a value "Unknown" (1). This is because the message sent to SV+ from SWSW is as below:
| This problem has been fixed in eventd process. |
CSCdk36049 | SV+ database table 'circuit_line' shows wrong information in column 'l_line'; the l_line field has value 255. | This problem applies to circuit lines on IPX, IGX and BPX only. This problem has been fixed in emsc process. |
This patch is required for the SV+ SNMP Agent 8.4.12 users who is Connection Proxy agent for provisioning on the network. The problem fixed in this patch appears only in SV+ 8.4.12.
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdk44308 | Connection provisioning using ConnProxy agent software fails with internal error message, if the connection includes an IPX node as one of the endpoints. The connection will be with no error, if it is made using Connection Manager GUI. |
|
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdk48257 | SV+ topology window gets very frequent updates. This happens usually in a large network environment and/or with a high node/trunk alarm frequency. This has been fixed in NWTopology process by introducing an environment variable REDRAW_TIME. The details of the fix are as follows: | A NWTopology application keeps its topology maps and its shared memory in sync with the network in the following manner: Redraw maps & refill shared memory every REDRAW_TIME seconds (this is a environment variable, default 5seconds, max allowed value 300seconds, min allowed value 1 second.). After each topod msg input, the need to redraw maps, shared memory is determined and 2 flags are set. If the flag indicates that no redraws are required, the above logic for redraw is not exercised. Same for shared memory. Redrawing maps (as above) is suppressed if both windows (overview & NWTopology) are unmapped (iconised).However, updates to shared memory continue inspect of the application window being unmapped. This is required since the shared memory may be used by the applications ConMgrGUI and Equipment Manager GUI to obtain routing and feeder nodes information within the network. |
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdk67023 | SV+ does not get registered to the AXIS nodes for a long time. This problem happens if the first attempt to register to the AXIS fails due to AXIS agent time-out or other SNMP error and the short time-out (in secs) given by command line option (-s) to rtm process is set to a high value. | This problem is fixed by de-coupling the use of the short time-out value in the error retry delay scenario. Now, the short time-out value is used only for time-out getting response from snmpcomm. This short time-out can be set to a higher value to avoid too many repeated requests sent to snmpcomm while its busy and end up flooding its message queue. A new command line option "-d" is introduced to set the error retry delay time in seconds.This error retry delay time is used if response is received from snmpcomm but the request was failed. In this case, rtm will retry (resend the request) after the error retry delay time. The default for this retry delay is 60s if its not set. |
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdk60860 | Support for following BXN trunk stats has been added in SCM. BIP-8 Errors (stat id on switch 40) BIP-8 Errored Seconds (stat id on switch 41) BIP-8 Severely Err Secs (stat id on switch 42) |
|
CSCdk67145 | SCM will skip sending request to tftp GET the stats file for some nodes in a random pattern. This results in missing stats in the database. | This problem has been fixed in statsmain process. |
Bug ID | Description | Workaround or Resolution |
|---|---|---|
CSCdk45631 | When user tries to add INS/DAS dial-up connection with value of CIR/QIR/MIR/PIR set to 32 kbytes/sec, SV+ puts invalid (negative) value in ins_dialup_conn database table. This problem has been fixed in Connection Manager GUI. | The valid range for atmEndPointMCR should be (0..353208) instead of (0..240000). |
CSCdk45646 | The modify function of Conn Manager GUI for INS dial-up connections does not work and gives an error: failure to Modify connection: connection not found in database. This problem happens when an attempt is made to modify an existing INS dial-up connection. | As a work-around to the problem, connection can deleted and re-added with the new values. This problem requires fixes in SV+ Connection Manager as well as in INS/DAS software. SV+ Connection Manager has been updated to fix SV+ side of this problem. To have a complete fix user needs to have this patch as well as INS/DAS version with it's side of fix included. |
CSCdk58273 | SV+ SNMP Proxy does invalid range checking for the mib objects atmEndPoitnPCRZeroPlus1, atmEndPointSCRZeroPlus1 and atmEndPointMCR on ASI/BXM card. Because of this attempts to add/modify connections on these cards by modifying the above mentioned mib objects, with the values in the valid range, fail. | For BXM card:
|
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
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.
SV+ 8.4 does not support ATM-SVC or FR-SVCs. As a result, they are not shown in the Connection Manager GUI.
Posted: Fri Mar 5 11:21:02 PST 1999
Copyright 1989-1999©Cisco Systems Inc.