|
|
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, select Documentation, and click Enter the feedback form. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
The 9.0.03 Cisco StrataView Plus for AIX software release supports the existing Cisco WAN switching products (including the Cisco IGX 8400 series and the Cisco BPX 8600 series) running the Switch software version 8.5 based release, and introduces the following features:
The StrataView Plus Release 9.0 Connection Manager 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 will support management of voice and synchronous data connections on a tiered network architecture, where the switch software is running 8.5 software. Please note that 3 segment voice/data connections with the middle segment terminated in BPX nodes are not supported. Also, the user needs to preconfigure the remote endpoint channel before setting up 1 segment data connection between two IPX/IGX routing nodes. For more information, please see CSCdk021115 bug description
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.03 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.03 has been tested to manage up to eight disjoint networks.
Users currently using SV+ 9.0.00 release, should install SV+ 9.0.03 and choose the installation New option to initialize the database tables. See next section, Installation Notes for details.
For users moving from release 8.2 or 8.4.xx, upgrading the software while keeping data in the Informix database intact is possible. See next section, Installation Notes for more details.
The upgrade from SV+ releases 8.2 (AIX 3.2.5) or 8.4.xx (AIX 4.1.4) is supported in this release. Users using SV+ 9.0.00 should perform a full install, which recreates the database. Thus graceful upgrade from SV+ 9.0.00 is not supported.
The following sub-sections detail procedures to prepare for SV+ 9.0.03 installation, to upgrade from SV+ 8.2 (AIX 3.2.5) or 8.4.xx (AIX 4.1.4), and to install SV+ 9.0.03.
AIX SMIT Install is used for SV+ 9.0.03. Please refer to the "StrataView Plus 9.0 AIX Installation Guide" for detailed information. After loading the svplus from the CD-ROM, user can either do new install or upgrade from previous release. The user is required to have AIX system level experience.
User is required to perform the following steps for installation:
1. Load Informix 5.10 from the CD-ROM (If not already installed)
2. Load StrataView Plus from the CD-ROM
3. Install SV+ 9.0.03
Login as root user and enter the following command:
/usr/users/svplus/INSTALL
Answer the following prompts accordingly:
This upgrade path will allow users to preserve the content of the database from releases 8.2 or 8.4.xx,. The following steps are involved with the upgrade. User should backup the existing database in case if he/she desires to fallback to the existing SV+ release.
Login as root user and enter the following command:
/usr/users/svplus/INSTALL
Answer the following prompts accordingly:
Enter "2"
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.
This section describes how to save a copy of the current database using Informix dbexport
1 ) Stop SV+ core processes
2 ) As user svplus, make a directory 'dbdump' under /user/users/svplus and change permission.
do "mkdir /user/users/svplus/dbdump"3 ) 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.
4 ) Save the content to a directory outside of /user/users/svplus, that is not easily being overwritten. Make sure that directory has enough space.
do "cp -r /user/users/svplus/dbdump <some directory>"Or one can save the database residing in user/users/svplus/dbdump onto a tape mounted on the /dev/rmt/0 drive:
5 ) If SV+ 8.2 is running, one should copy the exported database to a remote machine, so that the database will not be overwritten in some directory of machine B:
do "rcp -rp /user/users/svplus/dbdump < machine B>: <some directory>"or to a tape mounted on /dev/rmt/0:
The StrataView Plus 9.0.03 shall support AIX 4.1.4/4.1.5 on IBM Power PC model 42T or E30.
The recommended system configuration for SV+ 9.0.03 is, any one of the above mentioned workstations, with greater than or equal to 256 megabytes of RAM, two 2 Gigabytes of hard disks, CD-ROM drive, 8mm tape drive, 3 and 1/2 inch floppy drive running AIX 4.1.4/4.1.5, and NetView for AIX Version 4 Server. It is recommended that the system be configured with at least 400 megabytes of swap(paging) space(Paging space should be roughly two to three times of the RAM). The default disk space for the Informix database is 800 megabytes.
The SV+ 9.0.03 release works with IBM NetView Release 4.1 Server for AIX 4.1.4/4.1.5.
For IBM NetView installation requirements and procedures, please refer to "IBM NetView for AIX Installation Guide - Version 4".
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.
AIX SMIT Install is used for SV+ 9.0.03. Please refer to the "StrataView Plus 9.0 AIX Installation Guide" for detailed information.
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".
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.
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. In order to configure the correct network ip address use cnfnwip command on the switch.
Each IPX/BPX/IGX/MGX 8220 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 SCM supports 3100 nodes maximum in stand-alone mode.
For "CISCO 3800" node types, 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 ELMI feature on IGX and ALM-A card is not supported from SV+ 9.0.03.
SNMP Agent functionality is unchanged from release 8.4 of SV+. Refer to release 8.4.09 release notes for SNMP Agent Notes. Relevant part of 8.4.09 release notes is reproduced here for completeness.
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:
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.
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, FRSM8, AUSM8, and FRSM-HS1) 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 StrataView Plus.
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 |
|---|---|
| CSCdk02115 | Roll down CSCdj92497, no data continuity for 1 segment data connection. When user uses SV+ to setup 1 segment data connection, though connection add is successful, there is no data continuity. The reason is SV+ presets only the local line/port parameters but not the remote one. For data continuity both sides should have same values for these parameters.
User needs to preconfigure channel for remote endpoint for dfm enable, dfm length and eia update from the remote node's CLI before adding 1 segment data connection. |
| CSCdj47443 | One occurrence 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 through IP-relay. The delay could be due to the heavy traffic over the ip-relay network. This delay can be minimized if IP subnets are properly planned and out-of-band management is already in place. Make sure that all the swiches have read snmp community string set to public and write snmp community string set to private. |
| 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. |
| CSCdj31976 | Test Delay from Conn GUI has misspelled error message If test delay times out then the error message has few characters wrongly spelled. Known problem as of now, but this message conveys the time-out message. The same is true if test delay is aborted by switch. 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 analyzing 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 behavior is observed. a. Until the nwip addresses are configured correctly the nodes do not appear on the topology.
This is correct behavior.
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. |
| 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. |
| 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. |
| CSCdj74802 | Voice ports are shown as port number 0 in the conn If SV+ 9.0.03 is attached to a swsw 8.4 or earlier, all CDP/CVM cards are being reported as port number 0 in ConnMgr Gui. There is no workaround. However, it should be noted that since voice/data connections on CDP/CVM cards were not supported by SV+ before swsw 8.5, this does not block any functionality. The port 0 in the list can be safely ignored. |
| CSCdj75650 | After runcnf the SV+ does not update the connection database accordingly After performing "runcnf" for the entire switch, it was found that in some cases there were pending robust messages in the switch either due to one of the nodes becoming unreachable or multiple trunk failure. As a result, SV+ did not get all the connections. Currently, the way to get around the missing connections problem on SV+ is to do a cold start after a "runcnf". |
| CSCdj75650 | cmgrd - Failed to configure preferred route for UVM-CVM connection This happens when preferred route is applied for a UVM-CVM connection. There is no workaround. |
The following conditions have been corrected with the 9.0.03 version of the software release.
| Bug ID | Descriptions |
|---|---|
| CSCdj84455 | emd core dump |
| Symptom | Emd exits when fails to register with the topod process. This happens when topod is not running. |
| Workaround | Restart SV+. |
| CSCdj83361 | Roll down CSCdj72384 - statsmain has incorrect node version info in cache |
| Symptom | If the incorrect node release is lower than the actual one, some stats which are supported for the actual release of node cannot be enabled. This incorrect node version occurs if SCM has connected to a different network from the previous network. |
| Workaround | Delete stathistory.stats file under /usr/users/svplus/statsmgrdir and restart SCM. |
| CSCdj84298 | Wingz does not display object for selected line statistics |
| Symptom | No E1 line objects are listed in the Object Available window |
| Workaround | None |
| CSCdj85870 | EMSC will not update port status for BXM ports |
| Symptom | Port alarm status for some BXM cards are not updated. |
| Workaround | None |
| CSCdj86766 | Internal Error: Failed to modify connection. Cannot get selected connection. When a connection is in selected state in the main window, and an event(DBKR_ALARM_EVENT) comes for that connection, user will get the above error message if an attempt is made to modify that connection. Wait for a few seconds and try to modify again. |
| Symptom | |
| Workaround | |
CSCdj87117 Symptom Workaround | Make pkgchk work for 9.0.03 When run "pkgchk" on CSCOsv, CSCOinf and CSCOscm packages, there are error messages on all the files in the package. Thus, it is very difficult to pinpoint which file got modified inadvertently in the file audit process. None |
The following conditions have been corrected with the 9.0.02 version of the software release.
| Bug ID | Description |
|---|---|
| CSCdj35673 | IGX feeder not seen by cmgrd nor NWTopology after being deleted and re-added |
| CSCdj63233 | Wingz: Save/Retrieve template does not work |
| CSCdj65482 | SV+ 9.0 Wingz2.5 Wingz will not launch from GUI |
| CSCdj65804 | /usr/users/svplus/config/svplus.conf has wrong ownership, SV+ will not s |
| CSCdj65837 | Problems when running Wingz, multiple error messages |
| CSCdj27687 | Baseline : Wingz error message loops forever |
| CSCdj43801 | Eventd/RtmProxy: incorrect trktype in trktrap, incorrect contype in cont |
| CSCdj56495 | SV+ 9.0 : spelling mistake in data conn error message |
| CSCdj63230 | Wingz: cleanup some of the pop up and flashing of Config.wkz |
| CSCdj65404 | CSCOsv pkg states that CSCO Wingz is a pre-requisite. This is incorrect |
| CSCdj65427 | Incorrect permissions/ownerships of traceroute and top in tools directory |
| CSCdj69945 | Voice and data channels entries will not be removed when node is deleted |
| CSCdj71987 | (Rollup CSCdj68473 from 8.4) cannot parse stats for FRM/CVM T1 circuit line |
| CSCdj80628 | SV+ does not show a-bit failures for 2 segment FR conns |
| CSCdj74473 | Conn mgr shows OK data/voice connections as in OK/A-bit alarm |
| CSCdj62532 | PortProxy does not support UFM port |
| CSCdj82123 | Wingz does not support Add Comment feature |
The following bugs were fixed in 8.4 and rolled up into release 9.0.02:
| Bug ID | Description |
|---|---|
| CSCdj52243 | packet_line table has corrupted entries |
| CSCdj09378 | SV+ : 8.4.0B (AIX) : Unable to add foresight connection |
| CSCdj40746 | When a statistic file is found bad, the SCM will not re-get the f |
| CSCdj41747 | RtmProxy return gen err when walking the lineGroup mib for an IPX |
| CSCdj41775 | specific 500 trap gives svConnType value of 5 which is undefined |
| CSCdj45001 | comm failure messages in maintlog are not converted to traps |
| CSCdj47539 | Multiple Stats Ager processes in SV+ |
| CSCdj49013 | Preferred routes via SNMP off by one on trunk info |
| CSCdj49468 | Connection Mgr Gui crashed after certain input sequence involving |
| CSCdj49612 | cmgrd disconnected from databroker for 2 hours ICORE (ispan976468 |
| CSCdj50252 | Modification of PVC with icrto > 8000ms problem via snmp mib |
| CSCdj50479 | tftpchild may store data from previous session to current file |
| CSCdj51047 | EM GUI - cannot configure redundant card for HSSI. |
| CSCdj52053 | Modifying a Fr-ATM connection changes some values to defaults |
| CSCdj52061 | watchdog.conf can get removed when the SNMPAgent/Proxies are kill |
| CSCdj53960 | EMGUI cannot configure SRMs intermittently. |
| CSCdj54165 | Connection manager fails to delete/modify cons. |
| CSCdj55784 | tftpmgr starts one child less, whenever a child is manually killed |
| CSCdj55790 | Enhance RTM to poll INS faster than an AXIS node. |
| CSCdj57299 | AXIS clock source configuration is not displayed accurately in EM |
| CSCdj59754 | snmp error 152 while trying to increase cir on fr-atm com |
| CSCdj60562 | Customer needs information about Informix Database tables and Ob |
| CSCdj63341 | After SV warmstart, Shared Mem failure prevents GUI node list pop |
| CSCdj63377 | SV+ became unsubscribed to all AXIS shelves. |
| CSCdj63440 | No ports seen thru ConnManager. |
| CSCdj63905 | EMGUI does not properly display admin/loop status for SRM |
| CSCdj64646 | EMGUI view counters does not reflect input parameters |
| CSCdj65376 | EMGUI view counters does not reflect value on switch. |
| CSCdj24454: | downld lcbs not getting freed up. |
| CSCdj39053 | Dbexport illegal stored procedure failure |
| CSCdj48237 | create a read only Connection Manager GUI |
| CSCdj49244 | SV+ log files and ImagDownLoad program shows 100 for Year 2000 |
| CSCdj49998 | ConnProxy: ServiceMib definition of pref Route lacks trunk remote |
| CSCdj50369 | SV+ startup script option 8 is not functioning. INS ANI Configurable |
| CSCdj50377 | Scroll bar in NORMAL congui window disappear after coming back from |
| CSCdj50752 | Configs saved using savecnf do not show BRAM or node ids in the S |
| CSCdj50938 | Changing assign severity twice causes INTERNAL ERROR 639 on HPOV4 |
| CSCdj52643 | No HPOV format for trap 20007 sent by RtmProxy |
| CSCdj52856 | Topod doesnt update the debug level passed thru command line |
| CSCdj53355 | tstdelay doesnt work for local connection on ConnMgr |
| CSCdj54427 | emd: dberr 100 and 239 when deleting a link of an IMATM port |
| CSCdj56246 | Makefiles generated for SV+ processes do not include all the flag |
| CSCdj61406 | UMR and UMW problems in emsc as shown by Purify |
| CSCdj63598 | wrong stats if peak interval = bucket interval |
| CSCdj51831 | NWTopology gives warning msg at console when listing multiple tru |
The following conditions have been corrected with the 9.0.01 version of the software release.Bug ID
| Bug ID | Description |
|---|---|
| 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 be 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. |
All anomalies corrected between version 8.4.06 and version 8.4.09 are included in this release. Please see the Cisco StrataView Plus Software release notes for version 8.4.09.
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.
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.
|
|