|
|
The 8.4.06 Cisco StrataView Plus for AIX software release supports the existing Cisco StrataCom switch family (including the Cisco StrataCom IGX and Cisco StrataCom BPX) running either Switch software version 8.2.5x or 8.4 based releases, and introduces the following features:
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.
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. The user is 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.06 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.
SV+ 8.4.06 Connection Manager is enhanced to support new ATM connection types, such as UBR and standard ABR connections for both SWSW 8.4 based and SWSW 8.2.5x based releases.
SV+ 8.4.06 Connection Manager 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 and ESP (Extended Services Processor) nodes for SWSW 8.2.5x based release.
SV+ 8.4.06 supports image download feature for routing nodes via TFTP protocol for both SWSW 8.4 based and SWSW 8.2.5x based releases.
SV+ 8.4.06 supports the image download feature for ESP nodes via TFTP protocol for SWSW 8.2.5x based release.
SV+ 8.4.06 is extended to support the configuration save and restore feature for ESP nodes for SWSW 8.2.5x based release.
SV+ 8.4.06 supports 40 simultaneous SV+ desktops with proper hardware configuration for both SWSW 8.4 based and SWSW 8.2.5x based releases.
SV+ 8.4.06 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+ 8.4.06 SCM is enhanced to support Cisco 3800 statistics, UVM and UFM-U statistics for SWSW 8.2.5x based release.
SV+ 8.4.06 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.06 does not support the ALM-A cards for IGX. As a result, the connections terminated at ALM-A cards will not be shown in the Connection Manager GUI.
SV+ 8.4.06 does not support voice connections. As a result, the connections terminated at UVM cards or FTM cards will not shown in the Connection Manager GUI.
SV+ 8.4.06 does not support ELMI on UFM cards.
The upgrade from SV+ release 8.1.4x (AIX 4.1.4 based) or SV+ release 8.2 (AIX 3.2.5 based) to release 8.4.06 (AIX 4.1.4 based) is supported.
Please refer to the "StrataView Plus 8.4 AIX Installation Guide" for detailed information.
The typical SV+ upgrade procedures include importing the Informix database from previous SV+ release. The user has to 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.
StrataView Plus 8.4.06 supports AIX 4.1.4/4.1.5 on IBM Power PC model 42T or E30.
The recommended system configuration for SV+ 8.4.06 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+ 8.4.06 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+ 8.4.06 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+ 8.4.06. Please refer to the "StrataView Plus 8.4 AIX Installation Guide" for detailed information.
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 SV+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.
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 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 P2, the user is able to specify any time period for a peak interval from SV+. In SWSW 8.4, following rules are used when the user configures peak interval through SV+. Violating the rule will cause TFTP error 22 displayed in the SCM.
While SV+ Desktop is running, if the X server crashes for any reason then SV+ desktop 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.
Whenever SV+ core processes are stopped, NetView for AIX also need to be stopped, if it is running. To get the proper updates, NetView for AIX should be restarted after the SV+ core processes have been restarted.
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.06 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:
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.
In order to run Wingz2.5 successfully on AIX 4.1.4/4.1.5 user needs to do the following:
Step 1 User should extract Wingz2.5 to /usr/users/Wingz directory. If it is extracted to any other directory, then user has to create a link /usr/users/Wingz pointing to the extracted directory.
Step 2 The extracted Wingz2.5 directory should be owned by user svplus, and group users.
Step 3 User needs to create a link DBLink in /usr/users/Wingz directory which points to /usr/users/Wingz/DataLink/DBLink.(Assuming the Wingz2.5 is extracted in /usr/users/Wingz directory)
StrataView Plus 8.4.06 will operate with IPX/BPX/IGX releases 8.4.0, 8.1 and 8.2, Axis release 2.x, 3.x (AUSM4, CESM4, FRSM4, ASC and IMATM) and Axis release 4.0.02 (CESM4, FRSM4, AUSM4, BNM T3/E3, BNM 155, SRM T1/E1, SRM 3T3, IMATM and FRSM8) for all supported features.
StrataView Plus 8.4.06 has been tested with IPX/BPX/IGX release 8.4.0 and Axis release 4.0.02.
StrataView Plus 8.4.06 will be backward compatible with AXIS release 3. In the case of IMATM, StrataView Plus 8.4.06 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.06 equipment manager shelf view displays AUSM release 2 cards, the user needs to enable the line and ports from AUSM CLI. The Equipment Manager line configuration window and port configuration windows will not fully functional for AUSM R2 cards.
The following is the list of known anomalies in this Cisco StrataView Plus software release.
Bug ID Descriptions
CSCdj34167 There is a problem of displaying incorrect paths for some PVCs in the CMGUI. It does not happen on all PVCs.
CSCdj33872 When the user performs 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.
CSCdj33443 The length of curr_route and pref_route strings in the logical_conn table (255 bytes) may support up to 7 hops (with virtual trunks information included). The switch is designed to support up to 10 hops.After a Node-by-Node upgrade, a node may become unreachable, and software error 1406 is logged, indicating that network messages about the network topology were not correctly sent/received.
CSCdj36017 Sometime cmgrd process core dumps at deleting one segment of incomplete AXIS connections.
CSCdj36936 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 the user can't assign X.0.X.X format for AXIS IP address.
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. The impact is the user has to restart the BRAM save/restore process when the protocol transmission is not reliable.
CSCdj31076 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 platform resources are wasted.
CSCdj23550 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, the user 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)
CSCdj32955 There is one time occurrence that an un-readable event was shown in the HP Openview event log. However, the Openview trapd.log (the database for Openview events) does not contain such an event.
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.
The 'telnet' command in AIX 4.x(x>= 1) has the following problem. If it is used to logon to any of the StrataView nodes (BPX/IPX/IGX), the login user name and password are not taken properly and the login always fails.
The workaround for this is to set the 'telnet' mode to character mode. For this enter the telnet escape character (usually combination of Control key and ']' - left square bracket -keys), which is shown on the screen as soon as the telnet command is given at 'Enter User ID:' prompt.
telnet > mode character <ENTER> <ENTER>
NetView-Network Topology-Objects can be placed out of the screen. But, no way to get them back in the screen. Work-around: Turn the Auto Layout "ON" on all the submaps. This will re-layout the map using NetView for AIX layout algorithms and bring the out of screen objects on this screen.
NetView for AIX refresh map does not work occasionally for READ-ONLY map.
NetView for AIX displays blanks in the filter window occasionally.
ovw binary goes to loop sometimes.
While using Reports feature of StrataView Plus (using Wingz 2.5), 'Window not found' messages appear on screen. These are harmless messages (press OK for the window).
While using Wingz2.5 the Config.wkz or ConfigRep.wkz, worksheets flicker when any of the list box items are selected. This is not a problem.
Sometimes, SV+ desktop does not start giving the Bad Font error. This is a problem with MWM on AIX 4.1.4. When this happens exit the MWM and restart it again, then desktop comes up ok. If the problem is still exists perform the following steps:
Step 1 On the machine where you want the desktop to be up, do a xlsfonts and redirect the output to a file.
$ xlsfonts > xx
Step 2 Set the environment variable 'FONT_FILE' to xx.
$ setenv FONT_FILE xx.
This will take care of the font problem.
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.
|
|