|
|
The 9.0 Cisco StrataView Plus for Solaris software release supports the existing Cisco StrataCom switch family (including the Cisco StrataCom IGX and Cisco StrataCom BPX) running the Switch software version 8.5 based release, and introduces the following features:
The Connection Service Agent is enhanced to support management of ATM-ATM and ATM-FR types of connections for the SWSW 8.5 based release.
The Port Service Agent is enhanced to support ASI ports and BXM (Monarch) OC3 and OC12 ports for the SWSW 8.5 based release.
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.5 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 the SWSW 8.5 based release.
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.
Network Browser is a new application that summarizes and displays the status of all nodes in a tabular form for the SWSW 8.5 based releases.
SV+ Administration application is added to SV+ desktop. The user is able to view system error log and SV+ process status.
NwTopology and HPOvTopology map are enhanced to discover and display Cisco 3801 nodes for the SWSW 8.5 based release.
The StrataView Plus Release 9.0 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 the SWSW 8.5 based release.
The StrataView Plus Release 9.0 Connection Manager is enhanced to support new ATM connection types, such as UBR and standard ABR connections for the SWSW 8.5 based release.
The StrataView Plus Release 9.0 Connection Manager is enhanced to support the SWSW 8.5 release SIW feature and UFM-U cards for IGX.
The StrataView Plus Release 9.0 Connection Manager will support management of voice and synchronous data connections on a tiered network architecture, where the switch software is running 8.5 software.
The network will allow up to 12 SV+ stations to be connected into it. There is no change in StrataView Plus Release 9.0 software for this feature, the switch software and AXIS (4.04 onwards) have increased their limits to support this.
StrataView Plus Release 9.0.01 will be able to manage different disjoint networks running switch software releases 8.2, 8.4 or 8.5 provided all the networks elements have unique network ip addresses and unique names across all the networks managed by StrataView Plus. Different networks may run different versions of switch software as long as the releases are those listed above.
StrataView Plus 9.0.01 has been tested to manage up to eight disjoint networks. It may be possible to manage more then eight networks, but it is not tested.
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 3801 nodes for SWSW 8.5 based release.
StrataView Plus Release 9.0 supports image download feature for routing nodes via TFTP protocol for the SWSW 8.5 based release.
StrataView Plus Release 9.0 supports 40 simultaneous SV+ desktops with proper hardware configuration for SWSW 8.5 based releases.
SV+ 9.0 supports 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.
SV+ 9.0 SCM is enhanced to support Cisco 3801 statistics and UVM and UFM-U statistics for the SWSW 8.5 based release.
As of release 9.0.00, upgrades for SV+ are not supported.
The upgrade from SV+ release 8.4 (Solaris based, GA version of 8.4), SV+ release 8.2 (SunOS based) to release 9.0(Solaris based) will be supported in the first maintenance release.
Please refer to the "Cisco StrataView Plus 9.0 Installation Guide for Solaris" for detailed information on disk partition requirements.
In this release, Informix version 7.22 is used. Users must first upgrade Informix to version 7.2 before upgrading SV+. For the Informix upgrade, database export and import is not necessary.
There is an important change in the Informix version for SV+ 9.0.00 release. Currently we are shipping Informix version 7.22. However, as of first maintenance release of SV+ 9.0, and onwards, we will ship Informix version 5.10 with this product. The reasons as are follows.
Customers should see minimal to no impact because of this change. The following points should be noted:
If SV+ 8.4.xx is running on your current SV+ workstation, you need to stop SV+
Next,save a copy of the database using Informix dbexport:
Stop SV+ core processes
As user svplus, make a directory 'dbdump' under /user/users/svplus and change permission.
do "midair /user/users/svplus/dbdump"
do "chmod 777 /user/users/svplus/dbdump"
As user informix, do "dbexport -o /user/users/svplus/dbdump stratacom". Hint: In order to find out disk space requirements, use command "tbstat -d" and ensure that at least that much disk space is available.
Save the content to a directory outside of /user/users/svplus, that is not easily overwritten. Make sure that directory has enough space.
do "cp -r /user/users/svplus/dbdump <some directory>"
If SV+ 8.2 is running, one should copy the database to a remote machine, so that the database will not be overwritten, say in /usr/users/svplus/dbdump of machine B:
do "rcp -rp /user/users/svplus/dbdump < machine B>: <some directory>"
Shutdown informix by doing "su root", and "./usr/users/svplus/kill_db"
At this point, it is recommended to note down the disk partition where the database resides, so that one may enter the same path at the SV+ installation prompt for database raw partition name.
The second column of the output is the disk partition where the database resides. It will be something like /dev/rdsk/c0t1d0s7.
Remove the older informix under /usr/users/informix
If the existing SV+ was installed through the "pkgadd" command, remove it.
The SV+ 9.0.01 CD contains SV+ 9.0.01 software and Informix version 5.10.
First install Informix and SV+ from the /cdrom/cdrom0 by doing the following:
Enter "pkgadd -d /cdrom/cdrom0 CSCOinf" and answer the prompts as follows:
< Informix installation related information displayed>
< ...... >
Do you want this directory created now [y,n,?,q]
Enter "y"
< Informix installation related information displayed>
< ..... >
[ Hit <RETURN> to continue display ]
Enter "<RETURN>"
Do you want to install these as setuid/setgid files [y,n,?,q]
Enter "y"
Do you want to continue with the installation of <CSCOinf> [y,n,?]
Enter "y"
< Informix installation related information displayed>
< ..... >
( wait for the following message )
Installation of <CSCOinf> was successful.
At this point, ensure that WingZ is loaded properly. If not, then load WingZ version 2.55 before proceeding.
Enter "pkgadd -d /cdrom/cdrom0 CSCOsv" and answer the prompts as follows:
< CSCOsv installation related information displayed>
< ...... >
Do you want this directory created now [y,n,?,q]
Enter "y"
Do you want to continue with the installation of <CSCOsv> [y,n,?]
Enter "y"
Do you want to install these as setuid/setgid files [y,n,?,q]
Enter "y"
Do you want to continue with the installation of <CSCOsv> [y,n,?]
< Informix installation related information displayed>
< ..... >
(wait for the following message)
Installation of <CSCOsv> was successful.
3. If 9.0.00 was running, logout of the current environment from the SV+ root menu, then login as svplus again.
4. Install SV+ 9.0.01. Enter the following:
Enter "su root"
Enter "./INSTALL"
The procedure is pretty much similar to the previous release. Pick 1) at the following prompt and answer the questions accordingly.
Enter number corresponding to installation type of x to exit:
Enter "1"
WARNING: In the following output, the installation script provides uses with available partitions. It also picks up the swap partition as available raw partition. DO NOT use swap partition.
Checking existing partition....................... Successful
Available partitions (Solaris):
================================
/dev/rdsk/c0t0d0s1
/dev/rdsk/c0t1d0s1
< Could be some more disk partition information displayed>
< ...... >
Checking Hard Disk count.......................... Successful
Disk Configuration Migration to SV+ 9.0
1) Single Raw Database Disk
2) Multiple Raw Database Disk
Enter number corresponding to disk configuration or x to exit:
Enter "1"
The following steps are involved with the upgrade. If upgrade from 8.2, make sure the exported database is in the local machine now, so that one can enter the path of the database at the prompt for importing database.
Answer the following prompts accordingly:
(1) NEW (Release 9.0 of SV+)
(2) UPGRADE (From previous release of SV+)
Enter number corresponding to installation type of x to exit:
Enter "2"
Supported Upgrade Path for SV+ Release 9.0
-------------------------------------------------------
(1) From 8.2 (SUN OS)
(2) From 8.4.xx (Solaris)
Enter number corresponding to upgrade path or x to exit:
Enter "1", if upgrade from 8.2. Enter "2", if upgrade from 8.4.xx.
WARNING: In the following output, the installation script provides uses with available partitions. It also picks up the swap partition as available raw partition. DO NOT use swap partition.
Checking existing partition....................... Successful
Available partitions (Solaris):
================================
/dev/rdsk/c0t0d0s1
/dev/rdsk/c0t1d0s1
< Could be some more disk partition information displayed>
< ...... >
Checking Hard Disk count.......................... Successful
Disk Configuration Migration to SV+ 9.0
1) Single Raw Database Disk
2) Multiple Raw Database Disk
Enter number corresponding to disk configuration or x to exit:
Enter "1"
Enter Raw Partition Name for rootdb (default: not configured):
Three types of machines are supported for StrataView Plus 9.0 as standard platforms. They are low-end, mid-range and high-end platforms. The configuration of each platform type is listed in Table 1.
| Platform Type | Machine Type | Number of CPU | Size of RAM | Graphic Card Type | Hard Disk Drive | Size of Swap Space |
|---|---|---|---|---|---|---|
| Low End | Sun Ultra 1 Model 170E or Sparc 20 Model 151 | 1 | 256 MBytes | 24 bits | Two 2 GByte drives | 300 MBytes |
| Mid Range option 1 | Sun Ultra 2 with 300 MHz and 1MB cache | 1 | 512 MBytes | 24 bits | Two 4 GByte drives | 1 GByte |
| Mid Range option 2 | Same as above | 2 | 1 GByte | 24 bits | Two 4 GByte drives | 2 GByte |
| High End | Sun Enterprise 4000 | at least 4 | 1 GByte | 24 bits | Two 4 GByte drives and disk array | 2 GByte |
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. Table 2 lists recommended SV+ platforms based on the size of network.
| Platform Type | Machine Type | Number of SV+ Desktops (n) | Number of Connections (m) |
|---|---|---|---|
| Low End | Sun Ultra 1 Model 170E or Sparc 20 Model 151 | n < 5 | m < 5,000 |
| Mid Range option 1 | Sun Ultra 2 with 300 MHz and 1MB cache | 5 =< n < 10 | 5,000 =< m < 25,000 |
| Mid Range option 2 | Same as above | 5 =< n < 10
| 25,000 =< m < 100,000 |
| High End | Sun Enterprise 4000 | n >= 10 | m >= 100,000 |
Following are additional notes for SV+ platform requirements:
The SV+ 9.0 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).
The user needs to make sure at least 750 MBytes of disk space in /usr/users/svplus area can be allocated for SV+ 9.0 installation. In the case of upgrade, disk space used by existing SV+ software plus free disk space should exceed 750 MBytes.
The Solaris Package Check program (pkgchk) may not work with the SV+ 9.0 release. Pkgchk checks the accuracy of installed files or displays information about package files. This feature will be fully tested and supported in future release.
Install Wingz software from the Wingz tape or CD. Note that WingZ version 2.5 should be installed for SV+ release 9.0. Contact Wingz for a runtime license and blend it with SV+ 9.0. Failing to do so will result in following error messages when the user clicks 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 the user is 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 the user will see the following message when trying to re-start OV:
object manager name: netmon behavior: OVs_WELL_BEHAVED state: NOT_RUNNING PID: - last message: Can't talk to snmpd; see /usr/OV/log/netmon.trace for info exit 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.
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 performing the creation of a new database, i.e. executing createDb command, if StrataView Plus is restarted before it is synchronized with the network, it will result in a database inconsistency. In this case, perform SV+CreateDb before restarting SV+ to avoid database inconsistency.
After SV+ is shut down, the user must wait for at least 10 minutes before restarting it again.
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 an 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 midpoint.
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, the user 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.
While adding three segment connections where one routing node is IGX and another is BPX, connections must be mastered on feeders connected to BPX. Attempting to master connections on feeders attached to IGX hub will generate "Internal error" error message, and the connection will not be added.
Three segment voice and data connections can only be added when both routing nodes are IGXs.This is due to a switch software limitation.
While adding connections originating and terminating on same feeder nodes, SV+ will treat these connections as three segment connections and will add three segments (two on the same feeder node, one on the routing node) to realize this connection.
When the user starts 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.
The user 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, but upgrading from any 8.1 release prior to 8.1.16 will cause collection parameters to have default values.
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, the user is able to specify any time period for a peak interval from SV+. In SWSW 8.4 and above, the following rules are used when the user configures peak interval through SV+. Violating the rule will cause TFTP error 22 displayed in the SCM.
Switch needs some processing time to parse the stats.enable file. Depending on the number of stats and the number of objects this time can be very large. Currently SCM has a finite value for time-out (maximum 420 seconds) to wait for the switch response. Hence there might be cases where SCM will time-out waiting for switch to finish parsing the stats.enable file.If there are excessive time-outs then users should:
(1) cut down on number of stats enabled and be able to get the status of stats-enabling from SCM or
(2) keep the number of stats but losing the status of stats-enabling from the SCM. Users can use CLI commands such as dspstatparms, dspchstatcnf, dsptrkstatcnf, dspportstatcnf and dsplnstatcnf to make sure their desired stats are enabled. Note that there can be occasional time-outs if a node is busy for that period of time, but this case at the best is intermittent and should go away once loading on the node stabilizes Following is the formula to calculate the time to enable statistics on the switch:
time = (stats / cnt) * delay
where
stats = (conns * stats_per_con) +
(CLNs * stats_per_cln) +
(trks * stats_per_trk) +
(ports * stats_per_port)
cnt = number of stats configured in one group before giving up CPU, a configurable parameter on the switch.
delay = a delay time between each group of stats get enabled, this is also a configurable parameter on switch.
This is captured in CR CSCdj39737.
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 SV+ should 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.
Always use the SV+ ImageDownload program to do a SW/FW download. Since SV+ does not make any assumptions on the filename, it requires the user to tell the SW the filename and the path to download, avoiding any inconsistencies resulting from the file naming assumptions made by the getfwrev and loadfwrev commands. If the SV+ ImageDownload program does not work, then there is some problem with the file transfer or the image.
The basic SNMP Agent functionality is unchanged from release 8.4. 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+ Service MIB was re-organized for Release 8.4. See the StrataView Plus Release 9.0 Service Agent document.
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:
The 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:
The SNMP community names "public" and "private" are configured in this file for GET and SET respectively as defaults.
A branded (does not need a key) version of FrameViewer software is bundled along with SV+ software tape. If a user has an un-branded version of another frame product (for example FrameMaker) there may be conflicts between the two licensing systems. If there is a conflict in license usage, then SV+ FrameViewer help will not work. It is recommended that the user not run both products at the same time on an SV+ workstation.
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.
StrataView Plus 9.0 will operate with IPX/BPX/IGX Releases 8.5, 8.4.0, and 8.2 (8.2.0x, 8.2.3x and 8.2.5x), AXIS Release 2.x, 3.x (AUSM4, CESM4, FRSM4, ASC and IMATM) and AXIS Release 4.0.0x (CESM4, FRSM4, AUSM4, BNM T3/E3, BNM 155, SRM T1/E1, SRM 3T3, IMATM and FRSM8) for all supported features.
StrataView Plus 9.0 will be backward compatible with AXIS Release 3. In the case of IMATM, StrataView Plus 9.0 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 the StrataView Plus 9.0 Equipment Manager shelf view displays AUSM Release 2 cards, the user needs to enable the line and ports from the AUSM Command Line Interface. The Equipment Manager line configuration window and port configuration windows will not be fully functional for AUSM Release 2 cards.
StrataView Plus 9.0 Connection Manager does not support AUSM Release 2 due to the lack of port speed information in the SV+ database. This limitation will not allow the user to specify the PCR(0+1) parameter related to AXIS.
StrataView Plus9.0 does not support the BERT feature of AXIS/SRM Release 4. The user has to use the SRM Command Line Interface to configure the BERT functions.
The following is the list of known anomalies in this Cisco StrataView Plus software release.
Bug ID Descriptions
CSCdj47443: One occurance of CM GUI core dump if exited in a certain way.
This core dump happens if users are trying to close the CM GUI by using Alt-F4 key AND CM GUI is trying to update the screen at the same time. Under such condition, a core dump is generated. It is possible that users may not be able to invoke CM GUI from Desktop.
There are two precautions.
First, users are recommended to use the File-Exit menu to exit the CM GUI. If this is observed then there is no impact on the functionality and no issues.
If however, users do use Alt-F4 by mistake and if they cannot subsequently restart CM GUI, then the desktop must be exited and restarted by invoking option "3" from SV+ script.
CSCdj47891: SV+ Stats GUI is slow first time after install
When statsmain is brought up first time after the install, by default, it goes to each node to get their statsmaster using SNMP Get and then collect stats using TFTP. Both operations go throught IP-relay. The delay could be due to the heavy traffic over the ip-relay network. By adding few more IP-relay gateway to SV+, the delay could be shortened.
CSCdj45264: RtmProxy: SV+Network.mib missing card reason, wrong port state for ASI
RtmProxy: SV+Network.mib missing card reason, wrong port state for ASI svPortState MIB object reports down state when it should report inactive state.
CSCdj50873: AIX installation hangs or fails intermittently during informix database setup
SV+ installtion on AIX machines hangs (sometimes). This happens during informix database setup.Installation goes thru fine, when machine is rebooted and rerun ths INSTALL script. Seen less that 25% of times as of now.
CSCdj31976: Test Delay from Conn GUI has misspelt error message
If test delay times out then the error message has few characters wrongly spelt. Known problem as of now, but this message conveys the timeout message. The same is true if test delay is aborted by swith. The messages displayed are as follows.
" ) Test endpoint operation aborte" for aborted operation and
" ) Test delay timed ou " for timed out operation.
CSCdj35196: Preferred route limit of 255 bytes may be inadequate in certain (very unlikely) network configurations
The preferred route limitation of 255 bytes is not enough if a connection routes over all 10 hops and more then 3 of them are over virtual trunks. If this happens and users need to configure preferred route then cli commands must be used. This problem has never been reported from field but was found by engineering while analysing some other limits.
CSCdj42660: Upgrade Status Window has duplicate entries if nodes have invalid ip addresses
When managing a network where some nwip addresses are not configured correctly following behaviour is observed.
a. Untill the nwip addresses are configured correctly the nodes do not appear on the topology.
This is correct behaviour.
b. However after all the nwip addresses are configured correctly the display upgrade status window still has the invalid ip address nodes appended at the end of the list.
CSCdj42991: SCM request stats file early resulting File not ready error, file is obtained in subsequent retry.
SCM request stats file early resulting File not ready error. Fudge factor is SCM needs to tune a bit such that the file will be ready on the switch when SCM tries to upload. Anyway, SCM will retry the not-ready file and no loss of stats should be seen.
CSCdj43801: Incorrect trktype in trktrap, incorrect contype in contrap, for swsw 8.2 release
When Switch is running 8.2, trunk type and conn type values are wrong in trunk and conn traps. This bug has no workaround.
CSCdj44061: PortProxy: intermittent gen err when walking the svPortNode
Walking the svPortNode Entry using BPX hub as index and then walking the same table using BPX.axis as index will give gen error. But, subsequent walk on the table using BPX.axis as index works correctly.
CSCdj51194: Need to inform the user when using incorrect password to restore configuration
Need to inform user when using an incorrect password to restore configuration Instead only a access violation message is displayed.
CSCdj54722: SV+ installation script did not inform about minimum version required for WingZ
The installation script should check all the minimum version that is required in the system and inform the user about an outdated version during the installation. SV+ release 9.0 requires version 2.55 of WingZ.
CSCdj27687: WingZ error message may enter into a loop
When plotting using Wingz 2.5 in SV+ 9.0, user has to close the current plot before going back to the raw data report to generate a new plot. Otherwise multiple error message will appear (not loops forever as described) and then Wingz exited. Still under investigation on whether this is Wingz 2.5 problem or Hyperscript/util_ext problem.
CSCdj41484: Two garbage lines seen at the end of SV+ Admin Process Log
Some garbage output has been seen on SV+ Admin window on two last lines.
CSCdj54740: Statictics Collection Period 5 minutes should not offered in the SCM
Users should not use the 5 minute or 10 minute collection intervals even though they are available for selection. These two collection intervals used to be disabled in previous releases and will be disabled in Release 9.0 as well.
The following conditions have been corrected with the 9.0.01 version of the software release. In addition, all corrections applied to previous 8.4 releases are included in this release.
CSCdj57155: Process emsc may core dump if there are FTM or FTC cards in the network.
CSCdj54776: A-bit alarms seen on 1 segment voice and data conns for IPX to IGX conns only
CSCdj43801: Incorrect trktype in trktrap, incorrect contype in contrap, for swsw 8.2 release
CSCdj54722: SV+ installation script did not inform about minimum version required for WingZ
CSCdj54740: Statistics Collection Period 5 minutes should not offered in the SCM
The following conditions have been corrected with the 8.4.06 version of the software release. In addition, all corrections applied to previous 8.4 releases are included in this release.
Bug ID Descriptions
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 The user is not able 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 to the user.
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.
For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the information packet that shipped with your chassis.
For service and support for a product purchased directly from Cisco, use CCO.
CCO is Cisco Systems' primary, real-time support channel. SMARTnet customers and partners can self-register on CCO to obtain additional content 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, 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 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.
Please use CCO to obtain general information about Cisco Systems, Cisco products, or upgrades. If CCO is not accessible, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.
|
|