|
|
The 8.4.11 Cisco StrataView Plus for Solaris software release supports the existing Cisco WAN Switching switch family (including the Cisco WAN Switching IGX and Cisco WAN Switching 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.
The Equipment Management application is enhanced to support real time counter feature for AXIS release 4 AUSM4, AUSM8 and IMATM cards.
Network Browser is a new application that summarizes and displays the status of all nodes in a tabular form for both SWSW 8.4 based and SWSW 8.2.5x based releases.
SV+ Administration application is added to SV+ desktop. 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 and ESP (Extended Services Processor) nodes for SWSW 8.2.5x based releases.
SV+ 8.4.07 and later versions of SV+ will support networks with 200,000 end-to-end user connections, and will synchronize with these networks within 2 hours on a recommended high end machine configuration for both SWSW 8.4 based and SWSW 8.2.5x based releases.
Connection Manager in SV+ 8.4.07 and later versions of SV+ 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.
Connection Manager in SV+ 8.4.07 and later versions of SV+ 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 3801 and ESP (Extended Services Processor) nodes for SWSW 8.2.5x based release.
SV+ 8.4.11 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.11 supports the image download feature for ESP nodes via TFTP protocol for SWSW 8.2.5x based release.
SV+ 8.4.11 is extended to support the configuration save and restore feature for ESP nodes for SWSW 8.2.5x based release.
SV+ 8.4.11 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.11 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.11 SCM is enhanced to support Cisco 3801 statistics, UVM and UFM-U statistics for SWSW 8.2.5x based release.
SV+ 8.4.11 does not support Wingz report generator feature for Cisco 3801 nodes. However, the Cisco 3801 statistics are collected and saved in the SV+ database.
SV+ 8.4.11 does not support the ALM-A cards for IGX. As a result, the connections terminated at ALM-A cards will not shown in the Connection Manager GUI.
SV+ 8.4.11 does not support voice connections. As a result, the connections terminated at UVM cards or FTM cards will not be shown in the Connection Manager GUI.
SV+ 8.4.11 does not support ELMI on UFM cards.
The upgrade from SV+ release 8.1.4x (Solaris based), SV+ release 8.1.16 family (SunOS based) or SV+ release 8.2 (SunOS based) to release 8.4.11 (Solaris based) is supported.
Please refer to the "Cisco StrataView Plus 8.4 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 the /usr/users/svplus/tools directory.
Three types of machines are supported for SV+ 8.4.11 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:
For Stand-alone SCM, the following minimal CPU configuration is required:
128 MB memory, Solaris 2.5.1, 2GB total disk space. The user should install Solaris, and provide at least 300 MBytes for the /usr/users/svplus partition. This will provide adequate storage for the SCM files and some local stats files. For larger stats file depository, the user can add more disks and store the stats files on the larger partition.
The SV+ 8.4.11 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+ 8.4.11 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+ 8.4.11 release. Pkgchk checks the accuracy of installed files or displays information about package files.
The user should install Wingz software from the Wingz tape. Then he should contact Wingz for a runtime license and blend it with SV+ 8.4.11. 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.
For SCM stand-alone package, user svplus and group svplus needs to be created before installation of the package. Otherwise, the pkgadd of this package on Solaris systems fail with 'user svplus not known' type of message.
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.
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/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 Cisco WAN Switching virtual trunk cloud when the connection originates from an MGX 8220 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.
The maximum VCI that can be used for connections is 32767.
The Connection Manager GUI provides the default values of 5100 bytes for BC (Burst Committed) and BE (Burst Excess). These values are suitable for all cases of CIR (Committed Information Rate) up to 2048 Kbps. If the CIR is changed to some value higher than 2048 Kbps, 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).
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. Upgrading from an 8.1 release prior to 8.1.16 is not supported.
The SCM supports 3100 nodes maximum in stand-alone mode.
For CISCO 3801 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, following rules are used when the user configures peak interval through SV+. Violating the rule will cause TFTP error 22 displayed in the SCM.
SV+ must not be started from the OpenWindow's Cmdtool Window. If SV+ is started from Cmdtool, the Cmdtool may freeze the screen if Cmdtool window's log buffer is full.
While SV+ is running, if the X server crashes for any reason, then login as svplus and stop core processes. Then SV+ can be restarted.
While SV+ is running, if remote display is killed without properly shutting down the SV+ Desktop, then reopening it remotely may not succeed.
A VNS node is not to be attached to feeder nodes.
A VNS node may be added to a node isolated from the network.
The Wingz "Add Comment" option is not supported for virtual trunk and ATM connections. Wingz sometimes does not scroll up the list box properly.
Sometimes it may take 2-3 minutes to display new nodes after addition of virtual trunks. This is due to the time required to setup link0 and link1 subscriptions.
Although SV+ 8.4.11 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.
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.
The following two new traps have been added to Axis mib ( axis.mib file in mibs subdirectory of svplus home directory).
50022 - shelfLossLmiAlarmTrap
Indicates the Loss of LMI Alarm for AXIS BNM trunk.
(ANNEX G signalling failure)
50023 - shelfLossLmiAlarmClearTrap
Indicates the Clear of Loss of LMI Alarm for AXIS BNM trunk.
(ANNEX G signalling failure has cleared)
The above traps also have been added to StrataCom_trapd.conf, the HPOV-SV+ interface file.
The following changes are done in axis.mib (changes from axis.mib release 4.0.03 to 4.0.06).
1. Additional enumerations have been added for the following objects due to introduction of new card types.
shelfFunctionModuleType redPrimaryType redSecondaryType functionModuleType
2. The object dsx3LineType has been changed.
a. Added enumeration dsx3M23(3).
b. Changed access from read-only to read-write.
3. The default value of chanOvrSubOvrRide has been changed from disable to enable.
4. Changed varbinds in traps.
a. Varbind #4 has been changed from shelfSlotNum to moduleSlotNumber for all traps.
b. Varbinds #6 and #7 have been changed for the traps 50000, 50002-50009
shelfFunctionModuleState to functionModuleState
shelfFunctionModuleType to functionModuleType
5. Varbinds #6 and #7 have been changed in the following traps
a. bnmNolinealarmTrapnum (50100)
b. bnmlinealarmTrapnum (50101)
c. bnmLineLpbkEnableTrapnum (50102)
d. bnmLineLpbkDisableTrapnum (50103)
6. Varbind #6 has been changed from dsx3LineNum to lineNum.
7. Varbind #7 has been changed from dsx3LineType to lineType.
8. Changes in Descriptions have been done for some MIB objects.
The following changes are done in axis.mib (changes from axis.mib release 4.0.06 to 4.0.07).
1. Modify(3) enumeration has been deleted from SRM3T3 object.
2. Additional enumerations have been added for portState object. These are done as part of BERT related changes.
latchDS0DropFeLoop(9)
latchDS0LineFeLoop(10)
latchOcuFeLoop(11)
latchCsuFeLoop(12)
latchDsuFeLoop(13)
latchHL96FeLoop(14)
v54PolynomialFeLoop(15)
The following changes are done between release 4.0.07 and 4.0.08 versions of axis.mib.
1. The stratacom definition was removed from the MIB. This can be imported from the RTM-MIB instead.
2. NetPrefix definition has been changed. Instead of SIZE(8|13), now it is SIZE(8..13). This clears errors from the smic compiler.
3. Changed bertDDSCode enumerations from HEX to decimal equivalents. This clears errors from the smic compiler.
4. NsapAddress definition has been changed. Instead of SIZE(1 | 4..21), now it is SIZE(1..21). This clears errors from the smic compiler.
5. Trap definitions have been modiefied for the traps 50040, 50041, 50060, 50061 and 50062. In the previous release, the varbind moduleSlotNumber appeared twice in the trap definition, resulting in smic compiler errors. So, to avoid the problem of duplicate moduleSlotNumber varbinds, now the second moduleSlotNumber has been changed to shelfSlotNum.
Step 1 Enter following commands on your SV+ station as super user.
# /opt/OV/bin/xnmevents -delete trapCesmChanOverflow trapCesmChanCellLoss
Step 2 The HP OpenView user has to load the SV+ RTM mib first then load the axis mib version 4.0.08. The SV+ RTM mib is located in /usr/users/svplus/mibs/rtm.mib.
The HP OpenView mib loader is in the OpenView "Options" menu. Some notification messages will be shown after the RTM and axis mibs are loaded.
If StrataView plus 8.4.11 is installed on the system running HP OpenView, StrataView installation procedure will take care of the above steps.
The following changes are done between release 4.0.08 and 4.0.09 versions of axis.mib.
1. The traps 50120-50123 have been added.
2. The traps 50100-50103 have been obsoleted from Axis release 4.0.
The following changes have been done to switch mib (/usr/users/svplus/mibs/strata.mib) and SV+Service.mib.
1. The range of atmEndptMinAdjustICA object has been changed from 1..100 to 3..255.
2. The description of atmEndptMinAdjustICA object has been updated. Following is the new description.
DESCRIPTION
"ForeSight minimum adjustment period. Also known as TRM, which provides an upper bound on the time between forward RM-cells for an active source.
. Units: milliseconds.
. Applicable connection types:
standard ABR, ABR FST, ATFST: VSVD = enable(1)
. Default: 100 "
1. The range of atmEndPointMinAdjustPeriod object has been changed from 1..100 to 3..255.
2. The description of atmEndPointMinAdjustPeriod object has been updated. Following is the new description.
DESCRIPTION
"ForeSight minimum adjustment period. Also known as TRM, which provides an upper bound on the time between forward RM-cells for an active source.
. Units: milliseconds.
. Applicable connection types:
. ABR.1, ABR.FS: VSVD = enable(1)
. Range:
. ASI/BNI T3/E3: 20-250 msec
. BXM: 3-255 msec
. Applicable cards: BXM, BNI, ASI-T3/E3
. Not supported for AXIS."
The following changes are done between release 4.0.09 and 4.0.10 versions of axis.mib.
1. Added text "The moduleSlotNumber is the slot number of the Active ASC card." to the description field of traps 50022 to 50023.
1. The following interface types have been removed from the svAtmPortIfType and svPortIfType mib objects:
t3-smf (27)
t3-mmf (28)
t3-smflr (29)
t3-snm (30)
e3-smf (31)
e3-mmf (32)
e3-smflr (33)
e3-snm (34)
The smf, mmf, smflr and snm are fiber interfaces and are not applicable to t3 and e3 interfaces.
2. Updated the description of svAtmPortIfType object to reflect smf, mmf, smflr and snm related updates to t3 and e3 interfaces.
Updated description: "For BPX-BXM, lm-bxm, t3, e3, oc3-smf/mmf/smflr/snm, oc12-smf/mmf/smflr/snm"
The following changes are done between release 4.0.10 and 4.0.11 versions of axis.mib.
1. Syntax for the following bnmCounters has been changed from INTEGER to Counter.
bnmPortRcvCells
bnmPortXmtCells
bnmCellbusXmtCellCount
bnmCellbusNoAckCellCount
bnmCellbusGrantCount
bnmEgressXmtCellCountDuringAlarm
bnmEgressInvalidCellCount
bnmIngressInvalidCellCount
2. Syntax for the following sarChannelCounters has been changed from INTEGER to Counter.
xmtCells
xmtCellsCLP
xmtCellsAIS
xmtCellsFERF
xmtCellsBCM
xmtCellsEnd2EndLpBk
xmtCellsSegmentLpBk
xmtCellsDiscShelfAlarm
rcvCells
rcvCellsCLP
rcvCellsAIS
rcvCellsFERF
rcvCellsBCM
rcvCellsEnd2EndLpBk
rcvCellsSegmentLpBk
rcvCellsDiscOAM
The following changes are done between release 4.0.11 and 4.0.13 versions of axis.mib.
1. Added default values for all the objects under the ausmChanCnfGrp.
2. Added the following BNM Port Counters.
bnmPortRcvCellRate,
bnmPortRcvUtilization,
bnmPortXmtCellRate,
bnmPortXmtUtilization
3. Added the following AUSM Port Counters.
ingrRcvClpSetCells,
ingrXmtCells,
egrRcvCells,
ingrRcvCellRate,
ingrRcvUtilization,
egrXmtCellRate,
egrXmtUtilization,
egrRcvCellRate,
egrRcvUtilization,
totalIngrQfulldiscardCells,
txFifoFullCnt,
totalIngrClpSetDiscardCells.
4. Added the following AUSM Channel Counters.
chanIngrRcvCellRate,
chanIngrRcvUtilization,
chanIngrXmtCellRate,
chanIngrXmtUtilization,
chanEgrRcvCellRate,
chanEgrRcvUtilization,
chanIngrXmtAAL5Frames,
chanIngrEfciSetXmtCells,
chanEgrPortQfullDiscardCells,
chanEgrPortQClpThresDiscardCells,
chanTxFifoFullCnt.
5. The bit postion 8 in dsx3LineAlarmState has been changed from "Receiving test pattern" to "Receiving remote payload loopback".
1. The range for atmEndPointCDVTZeroPlus1 changed from 1-250000 to 0-5000000 microseconds.
2. The description for atmEndPointCDVTZeroPlus1 has been updated.
". Ranges:
BXM : 0 - 5000000
Other : 1 - 250000"
StrataView Plus 8.4 is certified on Solaris version 2.5.1. Certification for 2.6 Solaris has not been performed. Preliminary testing shows that SV+ does not operate on release 2.6 of Solaris. Do not use Solaris 2.6 to run StrataView Plus 8.4.
StrataView Plus 8.4 works with Informix 5.XX, where XX is greater than or equal to 06. However, Informix 5.07.UC2 is now being shipped with StrataView Plus 8.4.11 for Solaris platform.
SV+ GA releases are recommended for production use of SV+ and production
versions of switch software. Operating SV+ with releases that were Pre-
Release software created risks that can be alleviated using GA software. SV+
8.4.06 and greater are GA releases and are supported.
This version of StrataView Plus will operate with IPX/BPX/IGX releases
8.4.0, 8.1 and 8.2, Axis release 3.x (AUSM4, CESM4, FRSM4, ASC and IMATM)
and Axis release 4.0.02 or greater (CESM4, FRSM4, AUSM4, BNM T3/E3, BNM 155,
SRM T1/E1, SRM 3T3, IMATM and FRSM8) for all supported features.
AXIS Release 2.X and Switch Release 8.4.X is not supported for AUSM. This
configuration has not been fully tested.
StrataView Plus 8.4.XX has been tested with IPX/BPX/IGX release 8.4.X and AXIS
release 4.0.02.
StrataView Plus is backward compatible with AXIS release 3. In the case
of IMATM, StrataView Plus 8.4 will fully support IMATM starting on IMATM
release 3.0.03 onwards. The support for any previous releases of IMATM is
limited to display on Equipment Manager. No other support is available from
SV+.
Although SV+ 8.4 Equipment Manager shelf view displays AUSM release 2 cards,
the user needs to enable the line and ports from AUSM CLI. The Equipment
Manager line configuration window and port configuration windows will not be fully functional for AUSM R2 cards. As stated earlier, release 2.X and 8.4.x switch software is NOT recommended for production deployment.
StrataView Plus 8.4 Connection Manager does not support AUSM R2 due to the
lack of port speed information in the SV+ database. This limitation will not
allow the user to specify the PCR(0+1) parameter related to AXIS.
StrataView Plus 8.4 does not support the BERT feature of AXIS/SRM R4. The user
has to use CLI interface to configure the BERT functions.
The following is the list of known anomalies in this Cisco StrataView Plus software release.
| Bug ID | Descriptions |
|---|---|
CSCst97513 | DNS trap number 7012, 7014, 7015 are shown in the rtm.log but not in HP Openview event log. There is no workaround. |
CSCdj24615 | SV+ should use higher time out value for BRAM save/restore application. Current application level time out value is 1 minute which is the same as the robust protocol level time out value. The workaround is the user has to restart the BRAM save/restore process when the protocol transmission is not reliable. |
CSCdj38135 | On any AXIS card, upon bringing up the line menu, if any of the lines are disabled then the "operational state" displays "disabl" and not "disabled". There is no workaround. |
CSCdj40594 | The ConnProxy can not be used to "unset" a preferred route. This is typically done by setting the preferred route to NULL. The workaround is using CLI interface instead. |
CSCdj69154 | The Frame Viewer program which pops up when SV+ desktop is launched remains on after SV+ core processes have been stopped and desktop has exited. The impact is some amount of memory is occupied by the Frame Viewer process. The workaround is the user manually kills the Frame Viewer process after SV+ core processes have been stopped. |
CSCdj72731 | Wrong err msg shown (End Pt. does not exist), if out of range parameters are given for FR-ATM PVC on BXM card, while setting the PVC using SNMP proxy agent. |
CSCdj73647 | When SV+ Desktop fails to start, the error message given is not clear. The message includes two possibile reasons for the failure. |
CSCdj76510 | Real Time Counters not accessible from the StrataView proxy agents, but the proxy documentation says that they are accessible. |
CSCdj79083 | After TestCon if a SNMP GET operation is done on svConnLocalStr and svConnRemoteStr objects ConnProxy returns NULL. |
CSCdj83866 | NWTopology process exits intermittently in an unexpected way. |
CSCdj81530 | Specifying a value more than 255 for atmEndPointVpi for BXM card as part of the ConnProxy script results in an error. |
CSCdj88137 | TestCon returns erroneous data in SNMP for FR-ATM PVC. The returned values do not match with the values described in SV+Service.mib file. |
CSCdj88286 | TestCon on FR-ATM PVC is available through SNMP Proxy agent, but Connection Manager GUI does not allow. |
CSCdj88324 | If time Sync to a node times out the next node from the node table in the same subnet is tried as alternate time sync host. While trying this the type of the node is not checked (routing/feeder). |
CSCdj83876 | The Connection Manager GUI does not allow the CDVT(0+1) parameter to have a value larger that 250,000 micro seconds for BXM ports. The maximum value supported by the BXM cards is 5,000,000 micro seconds. As a work-around for the above problem BPX CLI can be used to adjust the CDVT(0+1) parameter if the value > 250,000 usecs is desired. |
CSCdj84198 | The treatments of failed connection in the case of Testcon and TestDelay by Connection Manager GUI and Connection Proxy Agent are not consistent. When the connection is in the "Failed" state, the GUI still allows the Testcon and TestDelay operations to be performed on the connection. However, the proxy agent would not attempt the operations, but instead, generate an general error. |
CSCdj85527 | SV+ install script overwrites the perl executable in /usr/local/bin with the version bundled StrataView media. |
CSCdj88210 | SNMP Proxy Agent dose not send cardAlarmTrap, when a BXM front card is removed. |
CSCdj88215 | Incorrect trapReason#3025 (card inserted) will be sent when BXM back card is removed. |
CSCdj88443 | Equip Management GUI and SNMP Proxy agent return wrong value for chanSecUpTime counter. |
CSCdj89302 | SCM doesn't give any warning message while exiting, that the stats collection will be stopped. |
The following conditions have been corrected with the 8.4.10 version of the software release. In addition, all corrections applied to previous 8.4 releases are included in this release.
| Bug ID | Descriptions |
|---|---|
CSCdj68473 | Statistics for FRM/CVM T1 circuit line can not be collected. This problem has been fixed in statsparser. |
CSCdj69022 | The mib object svFrPortStartingCh in the svFrPortTable is listed as "Read/Write" for FRSM-4, FRSM-8 and FRSM-HS1 card. However, no matter what value you set on svFrPortStartingCh, the value you get back on snmp get is always the same as that of svFrPortPort. Similar problem exists for svFrPortLine. In this case, the value returned is that of svFrPortLineIndex. The above problem happens when attempting to set the mib objects svFrPortStartingCh and svFrPortTable on AXIS FRSM-4, FRSM-8 and FRSM-HS1 card using PortProxy process. These problems have been fixed in PortProxy process and SV+Service.mib. |
CSCdj69146 | An intermittent problem in cmgrd and databroker processes which blocks PVC provisioning. The problem only occurs when PVC provisioning is happening non-stop while the databroker process is busy processing topology messages or alarm messages. As a work-around, warm start of the SV+ core will gracefully cause the back-end to recover. |
CSCdj70786 | The snmpcomm process might exhaust its resources intermittently and blocking the user to perform test con/test delay thru Connection Manager GUI. This problem only occurs when a relatively large no. of Connection Manager GUI's were restarted after running test con/test delay operation. The work-around for this problem is stop and start SV+. |
CSCdj72187 | An intermittent exit problem in configSave process has been fixed. This problem happens only if configSave receives a SIGTERM signal. This could be caused by exiting HP-OV ovw while configSave is still running. |
CSCdj72188 | An intermittent abnormal exit problem in Equipment Manager GUI process has been fixed. This problem has been observed to be happening usually after using real time counter screen for long time, to view counters on Axis AUSM and FRSM cards. |
CSCdj72753 | The documentation error regarding atmEndPointMinAdjustPeriod object in SV+Service.mib has been fixed. The range now has been changed to 3 to 255. |
CSCdj72953 | When the selected/highlighted connection on the Connection Manager GUI main window has a change of state event, the PVC would become deselected/un-highlighted. This problem has been fixed in Connection Manager GUI. The work-around for the above problem is to select/highlight the connection. |
CSCdj73570 | Setting up or updating a ATM-ATM/ATM-FR connection using ConnProxy process fails, if atmEndPointMBS parameter given is more than 24000. |
CSCdj75824 | Enumeration for 4001 was missing from trapReason field in SV+Network.mib. So when "Power supply clear" (defined as 4001) TRAP was sent to user from SV+ with 4001 reason field value, he/she could not map it to any value. This has been fixed in SV+Network.mib file by defining 4001 as "Power supply clear" reason field. |
CSCdj77436 | SCM may not collect statistics files 12 collection cycles back if the history files are set to >= 12. This problem has been fixed in statsmain process.This problem only occurs if the number of history files to collect is set to >= 12. |
CSCdj78846 | Unable to collect the following statistics via TFTP from BXM trunk lines when selected from SV+ stats manager: T3 Trunk 41) BIP-8 Errors 98) Frame Sync Errors 197) Tx NTS Cells Discarded 198) Tx Hi-Pri Cells Discarded 199) Tx Voice Cells Discarded 200) Tx TS Cells Discarded 201) Tx BData A Cells Discarded 202) Tx BData B Cells Discarded 203) Tx CBR Cells Discarded 204) Tx ABR Cells Discarded 205) Tx VBR Cells Discarded E3 Trunk 41) BIP-8 Errors 197) Tx NTS Cells Discarded 198) Tx Hi-Pri Cells Discarded 199) Tx Voice Cells Discarded 200) Tx TS Cells Discarded 201) Tx BData A Cells Discarded 202) Tx BData B Cells Discarded 203) Tx CBR Cells Discarded 204) Tx ABR Cells Discarded 205) Tx VBR Cells Discarded (98) Frame Sync Errors and (141) FEBE Counts can be configured for a T3 trunk but don't appear for an E3 trunk. (170) Loss of Cell Delineation can be configured for an E3 trunk but doesn't appear for a T3 trunk.. Further explanation of the problem: Frame Sync Errors As of today, On E3 trunks only Direct Map mode OR HEC framing is supported. With this type of Line Framing "Frame Sync Errors" are NOT supported. Loss of cell deliniation If the Line Framing was SET to HEC framing by doing cnftrk, ONLY then this stat is valid. When it is configured in the PLCP mode, this count is not valid. FEBE Count This fix is done in Switch Software. The rest of the missing counters counters are fixed in StrataView Plus SCM. |
CSCdj82171 | The percent utilization value reported by the Connection Manager GUI/Conn Proxy Agent might be reported as -1 occasionally. This problem has been fixed in databroker process. This problem only occurs when the 8.4 SV+ is managing an 8.2 network. |
CSCdj82198 | An intermittent problem in the cmgrd and databroker processes which blocks the PVC provisioning process. This problem only occurs after the Connection Manager GUI was exited and restarted more than 200 times. As a work-around for the above problem, a warm start of the SV+ core will gracefully cause the back-end to recover. |
CSCdj82416 | An intermittent abnormal exit problem in ConnProxy process has been fixed. This problem is experienced when the SNMP Agent gets detached from ConnProxy, and subsequent reconnection fails during SV+ shutdown. |
CSCdj82504 | The time stamp of traps from RtmProxy is different when its first received as compared to the recovered trap. This problem has been fixed in RtmProxy process. |
CSCdj84308 | Wingz Raw Data Report shows multiple "line 255" entries for T1 service line. This happens only if the node has multiple FRP-T1 cards. This problem has been fixed in util_ext process and Wingz command files. |
CSCdj84552 | An intermittent problem in Connection Manager GUI where complete connections will be shown as incomplete, has been fixed. The above situation occurs when the ILOG connection between emd and databroker gets into an invalid state which makes emd think that it is not connected to databroker. As a work-around for this, emd process can be killed, which will eventually be started by watchdog process. |
CSCdj84905 | Documentation problem related to stats "Total Cells Tx to Line" in and "ATM Cell Header HEC Errors" StrataView database schema documentation has been fixed. The "Total Cells Tx to Line" stat is not supported in AXIS shelf for trunk/line. AXIS shelf only supports this stat for port. The "ATM Cell Header HEC Errors" stat is supported in SCM as well as in the AXIS shelf. |
CSCdj85874 | BXM port status will not get updated in the asi_port table for BXM cards except for BXM having card type 117. Also, there won't be any BXM port alarm generated by SV+. This problem has been fixed in emsc process. |
CSCdj87239 | Trunk comments get truncated periodically. This problem has been fixed in NWTopology process. |
| Bug ID | Descriptions |
|---|---|
CSCdj42728: | 'status' field in 'packet_line' table is being populated with'0' value. The status field will now be correct. This effected the topology packet_line table and had no visual effect on the SV+ GUI or topology maps. |
CSCdj42760: | Cannot add cons with ICRTO > 8000. The range has been updated to be up to 250 seconds or 250000. This effects the Connection Proxy subsystem and the MIB comment. |
CSCdj42722: | Cannot get Physical to Logical map on FRSM connections. This problem effects the Port Proxy Subsystem only. |
CSCDj42895: | PortProxy exits under heavy system loads. This problem correction only effects the Port Proxy subsystem only. |
CSCdj40772: | CLP Hi/CLP Lo range incorrect. The Connection Proxy needs to support 1 as a valid value for CLP high and CLP low. The range of CLP-Hi, and CLP-Lo has been changed from 0-100 to 1-100. Accordingly, changes have been made to ConnProxy and the ConnProxy Service MIB. |
CSCdj43616: | Memory config of greater than 256 but less than 512 Megs memory get "Out of Shared Mem" error. |
| Bug ID | Descriptions |
|---|---|
CSCdj42987: | Cannot add FR-FR cons from SV+ 8.4 managing 8.2 network, using ConnProxy. |
CSCdj45010: | Cannot modify connection on a FRP card in 8.2 network, when the modify command is given using ConnProxy from a SV+ 8.4 station, other than the one from where the connection has been created. |
| Bug ID | Descriptions |
|---|---|
CSCdj45001: | "maintlog messages not converted to traps". |
| The maintlog messages are sent directly to eventd, who converts them to traps and sends them ONLY to HOPV (trapd). The robust object alarms, are processed by emsc, sent to eventd, who converts them to traps and sends them ONLY to RtmProxy. |
| The problem was that the process emsc was checking the status of the robust object alarm with the current status for that object. If they were the same, a duplicate alarm was assumed - even though they could have different "reason" codes. The change/fix is to not do this checking. |
| Bug ID | Descriptions |
|---|---|
CSCdj52243: | "packet_line table has corrupted entries". |
| The packet_line (trunk) information is reported to SV+ in two ways. First, topology messages contain packet_line information and are processed by the topod process. Second, there are robust object/alarm messages that are processed by the emsc process. The problem was that the emsc process was sending updates to the topod process, which was causing the topod process to corrupt it's cache and the database. The fix is to stop the emsc process from sending packet_line updates to the topod process. |
CSCdj47926: | "database current and preferred route strings missing nodenames" |
| The problem was that the emsd process was corrupting it's cache and the database due to a problem reading large topology messages from the topod process. |
The following conditions have been corrected with the 8.4.09 version of the software release. In addition, all corrections applied to previous 8.4 releases are included in this release.
| Bug ID | Descriptions |
|---|---|
CSCdj32955 & CSCdj61939: | An intermittent occurrence of un-readable events showing up in the HP Openview eventlog. However, the Openview trapd.log (the log file for Openview events) does not contain such an event. |
| The workaround for this is to apply HPOV 4.11 patch PSOV_01782 and run SV+_HPOV.install script in /usr/users/svplus directory as user root. |
| The patch PSOV_01782 can be applied by following the procedure given below. |
| Patch can be downloaded from http://ovweb.external.hp.com/cpe/patches and the consolidated patch number for HPOV 4.11 for Solaris 2.x platforms is PSOV_01782. |
| Before executing this procedure, make sure that SV+ and HPOV are not running. |
| Once this patch is downloaded, let us say to /tmp directory |
| 1. cd /tmp |
| 2. Become root user |
| su root |
| 3. sh PSOV_01782 |
| - creates two files PSOV_01782.text and PSOV_01782.tar |
| 4. Extract the contents of PSOV_01782.tar using tar command |
| tar xovf PSOV_01782.tar |
| 5. Above command creates PSOV_01782.install sub-directory in user's current directory. |
| 6. cd PSOV_01782.install |
| 7. ./install_patch |
| 8. cd /usr/users/svplus |
| 9. /opt/OV/bin/ovstart |
| - The above command starts OV processes |
| 10. ./SV+_HPOV.install |
| - The above steps makes sure that SV+ extensions OV are copied properly, after the patch installation |
| 11. Login as user 'svplus', start running SV+, ovw and check that the above error no more exists. |
|
|
CSCdj53355: | The Test Delay operation is not available from Connection Manager GUI on a connection with both end points on the same switch (DAX connection). |
| The workaround for this is to run tstdelay command on switch. |
| As a result of the fix for above problem user will be able to click on 'Test Delay' button in Connection Manager GUI, after selecting a DAX connection. However, the 'Test Delay' may or may not be successful depends on the support by switch for that type of connections. Currently 'Test Delay' on DAX conns is supported by BPX, but not by IPX or IGX. |
CSCdj53956: | EMGUI doesn't show SRM in slot 16 until a node resync. This happens in networks with SV+ 8.4.xx where xx < 09 and Axis FW release 4.0.0x where x < 4. StrataView portion of fix has been done in Equipment Manager GUI and AXIS fw release 4.0.04 has AXIS fix. |
CSCdj53960: | After core card switch SRM card can not be configured from Equipment Manager GUI. |
| The work-around for this is to remove the card entry for that slot from SV+ database and do a node resync from Equipment Manager GUI. |
CSCdj54384: | Modifying PIR parameter value of FR-FR PVC fails as RIF parameter of the connection is not adjustable. The problem is fixed in cmgrd process. |
| The workaround for this is to use the CLI on switch to lower the RIF value. |
CSCdj55784: | When a tftpchild process is killed tftpMgr process kills all the remaining tftpchild process, and restarts them. This problem has been fixed in tftpMgr process. |
CSCdj55790: | The rtm process is taking longer time to inform topology applications of the DAS/INS station status update (UP/DOWN). |
CSCdj57299: | Inconsistent display between AXIS CLI and Equipment Manager GUI clock config screen. This problem only occurs with release 3 BNM card. |
CSCdj59417: | An intermittent exit problem in statsparser has been fixed. This happens due to some internal memory corruption. |
CSCdj59754: | Modification of atmEndPointPolicing for ATM endpoints using SNMP Proxy fails. The following variables also have similar problems: |
| atmEndPointNRM |
| atmEndPointTBE |
| atmEndPointFRTT |
| atmEndPointVSVD |
| This has been fixed in in ConnProxy process. |
CSCdj60485: | An unexpected exit problem in emsc process has been fixed. This can happen if SV+ station is attached to IPX/IGX network with FTM/FTC cards. |
CSCdj60520: | NWTopology process exits in an unexpected manner. This can happen when user clicks on trunk 2 in the topology map, after double clicking on the same trunk and then clicking on Cancel when 'Trunk Description' window shows up. |
CSCdj60587: | strata.mib doesn't get loaded into OpenView by StrataView install program. |
| The workaround for this is to load strata.mib using options from OpenView menu. |
CSCdj62505, CSCdj63377: | SV+ processes gets unregistered intermittently with all the AXIS shelves. This happens only in the networks having large number of AXIS shelves with lots of activity. This problem has been fixed in rtm and databroker process. With this fix databroker directly sends the user connection traps to trapd and RTMProxy, instead of routing them through rtm. This will reduce the load on rtm and will avoid above problem occurrences. |
| The workaround for the above problem is to kill snmpcomm process or to stop and start StrataView Plus. |
CSCdj63341: | After SV+ warmstart, when Connection Manager GUI is started it pops up a message that shared memory is not accessible and the customary node list is not shown. This problem has been fixed in topod process. |
| This can happen on systems where several Network Topology (NWTopology) processes are running and being stopped and restarted. |
| The workaround for the above problem is to kill all the Desktop processes, bring up one, wait until the node list is seen in Connection Manager GUI, and bring up other Desktops. |
CSCdj63598: | Setting peak interval same as the bucket interval to collect statistics as mentioned in StrataView release notes, will result in Cell Tx and Rx stats collected with wrong value. The documentation problem has been fixed in StrataView release notes. |
| The workaround for this is to restart collecting stats with a peak value less than the bucket interval. |
CSCdj63905: | Equipment Manager GUI does not reflect the correct color for administrative state on SRM3T3 in release 4 AXIS shelves. This problem happens because of improper handling of the related trap by emc process. |
| The workaround for this is to do a node resync from Equipment Manager GUI after disabling the line. |
CSCdj64646: | Display of the real time counters from EMGUI does not get updated if the port/channel number is changed in the input window. The counters shown are still related to the port/channel previously entered. This problem has been fixed in Equipment Manager GUI. |
| The work-around for the above problem is to stop and start Equipment Manager GUI. |
CSCdj65376: | EMGUI real time counter do not match the counter on Axis shelf. This problem has been fixed in Equipment Manager GUI. |
CSCdj66681: | On certain systems after auto installing StrataView, an attempt to start SV+ fails with message "error - unable to initialize shared memory". |
| The workaround for this to run INSTALL program in StrataView home directory as user root after editing the /etc/system file to delete the duplicate entries, leading white spaces and rebooting the system with 'reboot -- -r' command as user root. |
CSCdj65933: | EMGUI does not show alarms on SRM card in Axis shelf running 4.0.04. This problem has been fixed in Equipment Manager GUI. |
| The workaround for the above problem is to look at the line alarm, and then go to individual line screen and look at the alarm state. |
The following conditions have been corrected with the 8.4.08 version of the software release. In addition, all corrections applied to previous 8.4 releases are included in this release.
| Bug ID | Descriptions |
|---|---|
CSCdj24454: | downld program rejects requests even if it doesn't have any active download sessions. This could happen when there is lot of network traffic generated due to multiple download sessions, and some of the sessions may end up in above state. |
CSCdj28230: | Shared memory values for feeder node ids are wrong and also some of the SV+ processes like databroker etc. would suddenly exit with an error. This can happen if Desktop is started before all the links are up or having ESP and/or ACCESS nodes in the network. |
| The workaround for the wrong feeder ids in the Network with no ESP or Access nodes is to start the SV+ Desktop after all the links have come up. However, there is no workaround if the Network has ESP or Access nodes, and SV+ process like databroker etc. start exiting. |
CSCdj39053: | Using dbexport tool of Infomix to export StrataView Plus DB stratacom, results in a failure with 'Illegal Stored Procedure Entry'. All the stored procedures used by StrataView Plus have been updated with the fix. |
| There is no workaround for the above problem. However, this message can be ignored as it doesn't seem to have any adverse effect on SV+ DB creation. User needs to run /usr/users/svplus/bin/create_sp program manually after importing the DB, if manual DB export and import operations are being done using Informix DBATools. |
CSCdj40746: | statsmain and statschild processes have been enhanced to validate stats file checksum and re-get file if validation fails. |
| This problem only happens on BPG/IPX/IGX running software version 8.4 or later. |
CSCdj41663: | For SCM, statsenablelist.stats & enable.master.81.stats files are changed to use defaults and enable.master.81.stats has been fixed to match with statsenablelist.stats file. |
CSCdj41747: | A problem in RtmProxy that walking the lineGroup object in StrataView Plus Service MIB results in "General Failure Error", has been fixed. |
| This problem happens only, if there is more than one circuit line on the IPX/IGX. |
CSCdj41775: | The 500 trap, which is sent for connection alarms from BPX/IPX/IGX, has a new value '5' defined for svConnType in StrataView Plus Service MIB and related changes in emsc. The same is done for trap 20000 also. |
CSCdj41906 | Unable to disable VS/VD feature for BXM-BXM ABR.1 connection by using Connection Manager GUI nor SV+ SNMP proxy agent. This problem only occurs on BXM-BXM ABR.1 connections. Once such a connection is added through the GUI/Proxy agent, the VS/VD feature of the connection cannot be turned off. The workaround is delete the connection and then create it again with the desirable VS/VD turned off. |
CSCdj45470: | A problem in statsparser, where it aborts parsing stats file when there is more than 127 stat types enabled for one object instance, has been fixed. |
CSCdj47539: | Multiple statsparser processes are running at a given instance on a StrataView Plus station. There are now two differently named processes - statsparser and statsager which are both independently started/stopped by the watchdog process. |
CSCdj49165: | When adding a intra-switch frame relay connection on an IPX/IGX routing node using ConnMgr or ConnProxy, the switch will reject the request if the percent utilization parameter is set to any value other than 100. This problem now has been fixed in cmgrd. |
| Workaround for this problem is not to set the percent utilization parameter when adding such connection using ConnProxy. If ConnMgr GUI is used, not to change the percent utilization parameter from its default value of 100. |
CSCdj49244: | The log files of SV+ processes in /usr/users/svplus/log directory show year portion as 100 and ImageDownLoad window from HPOV menu also shows 100 in date stamp of images, when system's date is changed to year 2000. |
CSCdj49457: | When INS station icon is dragged into HP OpenView map, the following error message appears on SV+ terminal. |
| "Ilb Error: Function void::msgPort(InsMsgHeader*) not exported by SVOV949.pid949@daslab8. |
| Ilb Fatal Error: Mismatch between versions of ILB generated protocol. |
| NSD process gets restarted due to the above error. |
CSCdj49468: | Clicking the "Refresh" button on the Connection Manager GUI main window after the transition between "Normal" and "ANI/Dial up" modes may cause the GUI process to exit occasionally. |
| The workaround for this is to first click the "Apply" button to enforce the filter setup before using the "Refresh" button. |
CSCdj49612: | cmgrd process may get disconnected from databroker process for long time and gets reconnected on its own after sometime. |
| This can happen on networks with more number of feeder nodes. |
| The above problem happened because databroker process is busy reading its messages in the memory sent by topod process, to respond to cmgrd process when cmgrd tried to check its connection with databroker. |
CSCdj50252: | When a MOD(ify) operation is performed on ICRTO value of an existing connection using Connection Proxy the following error is generated |
| "Invalid Value[value] for atmEndPtICRTO" |
| The only workaround for the above problem is to delete the connection and add it again with desired value of ICRTO. |
CSCdj50369: | INS ANI Configuration window does not come up when it is started from SV+ menu (option 8), even when INS is installed. |
| The workaround for this is to open an 'xterm' and run insAniConfig. |
CSCdj50377: | Scroll bar in connection list window of Connection Manager GUI disappears, when an ANI is selected in Dial Up window and Apply button is clicked. |
| The workaround for the above problem to exit Connection Manager GUI and restart it. |
CSCdj50479: | An intermittent problem in tftpchild process, where uploaded config files in current session are corrupted, if the previous tftp session had error timedout. |
CSCdj50752: | Network Topology application shows only the configuration saved date of the saved configuration ID, when it is selected from "Images->Config ..." screen. It doesn't show the BRAM ID and Node name information of the saved configuration. |
CSCdj50938: | Changing severity of a event twice from Normal - Minor - Normal, in HPOV 4.11 Event Browser using "Actions->Assign Severity" menu options pops out an "Error Exit" window with the following message. |
| " INTERNAL ERROR at: xnmeventCB.C:639. |
| Contact your HP Support representative." |
| and Event Browser exits. |
| The workaround for this is to apply HPOV 4.11 patch PSOV_01670 and run SV+_HPOV.install script in /usr/users/svplus directory as user root. |
| The patch PSOV_01670 can be applied by following the procedure given below. |
| Patch can be downloaded from http://ovweb.external.hp.com/cpe/patches and the consolidated patch number for HPOV 4.11 for Solaris 2.x platforms is PSOV_01670. |
| Before executing this procedure, make sure that SV+ and HPOV are not running. |
| Once this patch is downloaded, let us say to /tmp directory |
| 1. cd /tmp |
| 2. Become root user |
| su root |
| 3. sh PSOV_01670 |
| - creates two files PSOV_01670.text and PSOV_01670.tar |
| 4. Extract the contents of PSOV_01670.tar using tar command |
| tar xovf PSOV_01670.tar |
| 5. Above command creates PSOV_01670.install sub-directory in user's current directory. |
| 6. cd PSOV_01670.install |
| 7. ./install_patch |
| 8. cd /usr/users/svplus |
| 9. /opt/OV/bin/ovstart |
| - The above command starts OV processes |
| 10. ./SV+_HPOV.install |
| - The above steps makes sure that SV+ extensions OV are copied properly, after the patch installation |
| 11. Login as user 'svplus', start running SV+, ovw and check that the above error no more exists. |
|
|
CSCdj51047: | Can not add 1-1 redundancy to FRSM-HSI cards on Axis shelf, using SV+ Equipment Manager GUI. |
| The workaround for this is to use addred command from Axis CLI. |
CSCdj51831: | When clicking on the NWTopology map on a multiple trunk line to open up a multiple trunks window the following message is displayed on SV+ start-up terminal. |
| "Warning: |
| Name: popup |
| Class: XmForm |
| Top attachment widget for widget named 'list_label' (class XmLabelGadget) must not be null." |
| However, this warning message doesn't effect any functionality of the Network Topology map. |
CSCdj52061: T | he configuration file for watchdog process, watchdog.conf becomes empty or is completely removed when the SV+ Proxy processes are killed at the same time. |
| The above problem happens only when the proxy processes are killed manually in one kill command or SNMPAgent process is killed before the proxy process. |
| The workaround for the above problem is not to manually kill these SV+ Proxy processes. Stopping SV+ will terminate these processes without this problem. Another alternative is kill the proxy processes one by one and kill SNMPAgent last. |
CSCdj54165: | Modifying or deleting a PVC might fail with an error message "No SUCH NAME" for certain configured node names. The problem only occurs in cmgrd process, if the node name is configured as "D" or "Dx" where x is any alphanumeric character. |
| The workaround for this is to change the node name to a string at least 3 characters long or use any character other than 'D' as the starting character. |
The following conditions have been corrected with the 8.4.07 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. |
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. |
| When performing mib walk on svNodeGroup for an IPX/IGX/BPX node, only trunkGroup and lineGroup mib values are returned and the walk stopped. |
| No values returned for the rest in svNodeGroup: |
| svNodeGrpName |
| svNodeGrpNetName |
| svNodeGrpAlarmState |
| svNodeGrpGateway |
| svNodeGrpActive |
| Only when querying these mib objects individually, user can get their values. This is not happening for AXIS nodes. However there are no values for trunkGroup and lineGroup for AXIS nodes so values returned starting from svNodeGrpName. Is this the right behavior when querying an AXIS node? |
| This problem does not impact SV+ management applications. The workaround is querying these MIB objects individually from HP Openview. |
| Problems is in Agent when it verify the getnext response from RtmProxy, it cannot identify that the scalar after the lineGroup is also belong to the same subtree. |
| This is a generic problem but its not happening in pre-8.4 SV+ version because the mib was not arranged to have sub-groups and scalar mixed in one group. |
| A new function parent_oid_is_subset() is added to perform oid checking and nex_oidtree() is modified to call this new function to handle the checking properly. When 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. |
CSCdj36017 | Sometime cmgrd process core dumps at deleting one segment incomplete AXIS connections. |
| Incomplete connections usually happens after the connection has been built. If the card of one end-segment is removed from the chassis, the end-to-end connection becomes incomplete. Using ConnMgr GUI to add the connection will avoid incomplete connections at build time but not when the connection is in operation. |
| Sometime cmgrd process core dumps at deleting one segment incomplete AXIS connections. There is no workaround. |
CSCdj37361 | SV+ does not process traps sent from Axis Shelves with IP Addresses defined as X.0.X.X format where X is a non zero number. The impact is the user can't assign X.0.X.X format for AXIS IP address. |
CSCdj39399 | The back card type was recorded incorrectly in the SV+ database card table. This problem exists for all back card types. |
CSCdj33142 | Following alarms were not available from SV+: BCC restarted due to system reset, BCC restarted due to a power failure, CC redundancy, Y redundancy and communication break for a node. |
CSCdj39189 | The SV+ Solaris installation script specifies incorrect device name for CD device and it asks the user to rewind CD device. |
CSCdj37451 | The Connection Proxy is not able to read the current route information correctly from the logical connection table. As a result, the SNMP get response returns a null string for the current route. |
| Bug ID | Descriptions |
|---|---|
CSCdj42728: | 'status' field in 'packet_line' table is being populated with'0' value. The status field will now be correct. This effected the topology packet_line table and had no visual effect on the SV+ GUI or topology maps. |
CSCdj42760: | Cannot add cons with ICRTO > 8000. The range has been updated to be up to 250 seconds or 250000. This effects the Connection Proxy subsystem and the MIB comment. |
CSCdj42722: | Cannot get Physical to Logical map on FRSM connections. This problem effects the Port Proxy Subsystem only. |
CSCDj42895: | PortProxy exits under heavy system loads. This problem correction only effects the Port Proxy subsystem only. |
CSCdj40772: | CLP Hi/CLP Lo range incorrect. The Connection Proxy needs to support 1 as a valid value for CLP high and CLP low. The range of CLP-Hi, and CLP-Lo has been changed from 0-100 to 1-100. Accordingly, changes have been made to ConnProxy and the ConnProxy Service MIB. |
CSCdj43616: | Memory config of greater than 256 but less than 512 Megs memory get "Out of Shared Mem" error. |
| Bug ID | Descriptions |
|---|---|
CSCdj42987: | Cannot add FR-FR cons from SV+ 8.4 managing 8.2 network, using ConnProxy. |
CSCdj45010: | Cannot modify connection on a FRP card in 8.2 network, when the modify command is given using ConnProxy from a SV+ 8.4 station, other than the one from where the connection has been created. |
| Bug ID | Descriptions |
|---|---|
CSCdj45001: | "maintlog messages not converted to traps". |
| The maintlog messages are sent directly to eventd, who converts them to traps and sends them ONLY to HOPV (trapd). The robust object alarms, are processed by emsc, sent to eventd, who converts them to traps and sends them ONLY to RtmProxy. |
| The problem was that the process emsc was checking the status of the robust object alarm with the current status for that object. If they were the same, a duplicate alarm was assumed - even though they could have different "reason" codes. The change/fix is to not do this checking. |
| Bug ID | Descriptions |
|---|---|
CSCdj52243: | "packet_line table has corrupted entries". |
| The packet_line (trunk) information is reported to SV+ in two ways. First, topology messages contain packet_line information and are processed by the topod process. Second, there are robust object/alarm messages that are processed by the emsc process. The problem was that the emsc process was sending updates to the topod process, which was causing the topod process to corrupt it's cache and the database. The fix is to stop the emsc process from sending packet_line updates to the topod process. |
CSCdj47926: | "database current and preferred route strings missing nodenames" |
| The problem was that the emsd process was corrupting it's cache and the database due to a problem reading large topology messages from the topod process. |
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. |
One of the problems in the field is the quick dissemination of patches and release notes to ISC support and internal distribution. To standardize on a solution for this problem, the following process is adopted for the interface between TAC and internal distribution, and Strataview Plus 3rd Level support team.
SV+ Development has added patches and release notes to CCO for additional references to the patches. Once this is done, one should be able to find the links to the StrataView patches at the CCO site.
http://www.cisco.com
The field software support engineers can contact The Cisco TAC support center for information on the latest patch for a given version of StrataView, or browse the directory specified above for the release notes. All patches are described in the latest version of the release notes. You may find you do not need any of the patches available for a specific release of StrataView Plus.
All patches are "Inclusive" patches. Each subsequent SV+ patch includes the previous patch. This makes patch installation a single step. You MUST have previously installed SV+ or the SV+ Service Agents BEFORE applying the patches. The patch ASSUMES this has been done.
To install a patch a user would do the following:
Step 1 Get the patch tar file on to the SV+ machine.
Step 2 If the tar file name does NOT end in "Z", the file is uncompressed. These instructions are for compressed files. If your patch is not compressed, as user 'root', use the command "compress <tarfilename>" and go to step 3.
Step 3 Stop Strataview Plus.
Step 4 As user 'root' do the following on the patch level you have decided to install:
zcat <patchfilename> | tar xvf -Step 5 Start SV+.
The files on the patch have already been setup for the correct execution privileges, and are ready to use.
The Serial Configuration Upload Download (SCUD) product, as the name says, supports IPX/BPX/IGX configuration save and restore functionality over a serial interface.
The current available is 2.0. This tool is used for disaster recovery and is available free of cost to Cisco SV+ users having support contract.
SV+ Development is actively attempting to add this tool to CCO. Once this is done, one should be able to find the links to the SCUD patches at the CCO site.
http://www.cisco.com
1. Supports configuration save and restore for a single node network.
2. SCUD uses serial line interface on 'Control Port' of switch.
3. Following baud rates are supported:
2400, 4800, 9600, 19200 and 38400
4. The "Node Administration" window is used for user logins.No topology map will be shown.
5. SCUD supports IPX, BPX and IGX switches.
6. SCUD can be launched by any user and does not need special privileges.
7. SCUD uses the same directory structure used by SV+ to save/restore configurations.
The SCUD software will run on any Sun workstation running SunOS 4.1.x operating system. It can also be run on Sun workstation running Solaris 2.5 or 2.6 with binary compatibility support. The minimum memory requirement is 64MB. There are no special hardware requirements.
SCUD software is available on quarter inch tape in UNIX tar format. This procedure needs to be followed for installation.
Step 1 Login on Sun workstation.
Step 2 Change directory to where you need to install SCUD (SCUD home directory). It is advisable to install SCUD in the /usr/users/svplus directory. For this you have to move any existing SV+ installation in /usr/users/svplus to some other place before installing SCUD.
Step 3 Insert tape in the tape drive.
Step 4 Use tar command as shown below to get software loaded.
$ tar xvf /dev/<driveid> where <dirveid> indicates the tape drive identifier
e.g. rst0, rmt0 etc.
There is no install script to be run. The software is ready for use.
This version of SCUD is compatible with Switch Software release 8.1, 8.2 and 8.4 only.
SCUD software uses two configuration files. Configuration file 'cnfnodes' is used to specify the switch identification. Second file 'config.sv' is similar to one used by SV+ product and contains the serial line configurations.
'cnfnodes' file can have only one line with format shown below:
<nodename>|<switch_node_id>|<switch_net_id>|<SV+_netid>|
e.g.
nmsipx02|2|1|1|
'switch_node_id' is node id of a switch.
'switch_net_id' is network (also called as domain) is of a switch.
'SV+_netid' is SV+ network id (from config.sv file)
'config.sv' can have only one line with following fields and '|' as delimiter:
SV+_netid NO NEED TO CHANGE
networkname NO NEED TO CHANGE
serialport Specify the device file name for the serial port used
Baudrate Set serial port speed, must match speed of control port at the node
autodial Phone # to dial out including any prefix needed, 0 for not dialing
SV_Timeout NOT ALLOWED TO CHANGE
Retransmit NOT ALLOWED TO CHANGE
DL_Thresh_TO NOT ALLOWED TO CHANGE
DL_Ack_TO Set application level time-out value in seconds as appropriate
DL_Blk_Size Set transmission block size in bytes, no greater than 1024
Release Specify switch software release as appropriate
e.g.
1|Network1|/dev/ttya|19200|0|7|3|0|30|256|8.1
If SCUD is running with SunOS system, no configuration is needed for the serial port. User only need to identify which tty (/dev/ttya or /dev/ttyb) is for SCUD to use.
If SCUD is running with Solaris system, user need to run the system administration tool "admintool" to configure the serial port as "Modem - Dial-Out Only". This tool can only be run by super user (root). The serial port device name to use in the "config.sv" file should be "/dev/cua/a" for ttya and "/dev/cua/b" for ttyb.
Configure the control port of the remote node to be connected as follows:
Step 1 Run "cnftermfunc c 1" command to set control port function as VT100/StrataView.
nmsipx06 TN SuperUser IPX 8 8.1.50 Sep. 18 1997 19:16 PST
Control port Auxiliary port
1. VT100/StrataView 1. Okidata 182 Printer
2. VT1002. Okidata 18 2 Printer with LOG
3. VT100
4. Alarm Message Collector
5. External Device Window
6. Autodial Modem
Last Command: cnftermfunc c 1
Next Command:
Step 2 Run "cnfterm c 19200 n 8 1 x x y n" command, replacing the port speed parameter (19200) to match the setting in 'config.sv' file, to configure the control port to this settings:
nmsipx06 TN SuperUser IPX 8 8.1.50 Sep. 18 1997 19:29 PST
Control port Auxiliary port
Baud Rate: 19200 Baud Rate: 9600
Parity: None Parity: None
Number of Data Bits: 8 Number of Data Bits: 8
Number of Stop Bits: 1 Number of Stop Bits: 1
Output flow control: XON/XOFF Output flow control: XON/XOFF
Input flow control: XON/XOFF Input flow control: XON/XOFF
CTS flow control: Yes CTS flow control: Yes
Use DTR signal: No Use DTR signal: Yes
Last Command: cnfterm c 19200 n 8 1 x x y n
Next Command:
Modem settings we use in this recommendation is for Motorola Codex 3220+ model. If you are not using this model, use the corresponding commands for your modem to configure same settings.
1. Modem attached to the remote node:
AT&F Reset to factory default
ATS0=1 Enable auto-answer on first ring
ATL1 Modem speaker at low volume
AT*SM3 Enable automatic MNP error correction
AT*DC0 Disable data compression
AT*FL0 Disable XON/XOFF flow control
AT&S1 Sets DSR to "normal"
ATE0 Disable local character echo
ATQ1 Disable result codes (modem will appear dead)
AT&W Save current configuration settings
2. Modem attached to SCUD workstation:
AT&F Reset to factory default
ATL0 Modem speaker at minimum volume
AT*SM3 Enable automatic MNP error correction
AT*DC0 Disable data compression
AT*SC1 Enable DTE speed conversion
AT*FL0 Disable XON/XOFF flow control
AT&C1 DCD controlled by modem
AT&D2 Modem disconnects when SCUD toggles DTR
AT&W Save current configuration settings
SCUD allows user to save and restore configuration from/to IPX/BPX/IGX switches. The configuration saved using StrataView Plus product is stored under /usr/users/svplus directory using <saveid>_Cfgdir as directory name. When user needs to restore the saved configuration he has to copy this directory under SCUD home directory.
e.g.
If SCUD is installed under /usr/SCUD directory and the current saved configuration has saveid of 'SV72' then user will copy the 'SV72_Cfgdir' directory from /usr/users/svplus/ (or from other directory where files are manually copied) to /usr/SCUD directory.
Step 1 Change the 'cnfnodes' and 'config.sv' files to the required configurations.
Step 2 Change directory to where SCUD is installed.
Step 3 Set DISPLAY environment variable to your workstation display.
e.g. B shell --> $ set DISPLAY :0.0
$ export DISPLAY (for local display)
--> $ set DISPLAY mach1:0.0
$ export DISPLAY (for remote machine name mach1)
C shell --> % setenv DISPLAY :0.0 (for local display)
--> % setenv DISPLAY mach1:0.0 (for remote machine name mach1)
Make sure the SCUD configuration files, the remote node's control port and the modems on both sides are configured properly before launching SCUD.
Follow these steps to launch or stop SCUD:
Step 1 Type 'SCUD' on command line and hit <RETURN>
Step 2 Select option 1 to launch SCUD or select 2 to stop SCUD.
When SCUD is launched user will see "Node Administration" window on screen. User can logon to switch and use 'loadcnf' command to restore the configuration. The configuration to be restored must have already been copied to the SCUD home directory.
There are two ways to make the modem connection:
1. Use SCUD to dial out
This is enabled by putting the phone number in the "config.sv" file. The phone number can be prefixed by 'P' or 'T' for pulse or tone dialing. Comma, ',' is also allowed in this field for additional pause time. When SCUD starts, it will dial out from the modem and wait for it to connect before the actual applications are started. Messages are displayed at the start-up window to show the progression.
If SCUD fails to make the connection, it will retry indefinitely. If retries continue to fail, user should correct the failing condition and restart SCUD.
After the connection is established, the "Node Administration" window will appear. However, it may take a couple minutes before the node's login prompt is displayed in the "Node Administration" window. This is because the node may send a lot of data out once the connection is established and SCUD has to filter them out. At this time, the "RD" light on the modem is almost solid on. Wait until this "RD" light is off, you should be able to get the node's login prompt by hitting <RETURN> on the "Node Administration" window.
2. Use other communication tools, e.g. tip
In some cases, user cannot establish the modem connection by simply dialing a phone number. For example, if the remote end modem connects to a terminal server, some commands have to be issued after the modems are connected to route the connection to the port that the remote node is on. SCUD is capable of establishing this kind of connection. Hence, user has to establish the connection manually before launching SCUD.
The modem should be setup in a way that it would not drop the line even when DTR is dropped. After user has establish the connection using tools like tip, the remote node will start sending the command line interface screen data to user's screen. These data include VT100 terminal escape sequence that looks like garbage. User should wait until these are cleared and the node's login prompt appears, then exit the tip session. Make sure the line is still up by checking the "CD" light on the modem.
Before launching SCUD, verify that in SCUD's configuration file "config.sv", the autodial (phone number) field is set to 0. If this field is set to any valid phone number, SCUD will drop the line and redial that number. After SCUD is launched with the no dial out setting, the "Node Administration" window will appear right away and the node's login prompt will show up in seconds' time.
If network id in 'config.sv' does not match with one from 'cnfnodes' SCUD does not detect it.
SCUD may not be launched if SV+ software is running on the same workstation.
The protocol between SCUD and the remote node during a configuration save or restore session enforced a simple handshaking protocol that the sending side after sending a data packet, will wait for an acknowledgment (ACK) from the remote side before sending the next data packet. An application level time-out is imposed. When time-out on waiting the ACK, the sending side will send an ABORT message to the remote end and the operation is aborted completely. At the application layer, there is no retry capability. However, at the link layer, each packet will retransmit 3 times before giving up. Depending on the modem line quality, it could be so worse that the session keep aborting and never get completed.
In SCUD release 2.0, some enhancements are added to address this issue:
1. SCUD will perform retry on a configuration restore session (loadcnf). Configuration data is sent from SCUD to the remote node. When SCUD time-out on receiving the ACK, it will re-send the last data packet. By default, SCUD will try totally 3 times on the same packet before it gives up and abort the session. A "-r <num>" command line option can be given to configd in the "start_SCUD" script to specify the number of retries SCUD use.
Please note that the retry is only performed by SCUD and it works only for a configuration restore session. For configuration save, there is no retry feature at all.
2. The Baudrate (port speed), DL_Ack_TO time-out value and the DL_Blk_Size values in SCUD's configuration file "config.sv" can be tuned to optimize performance and cope with line quality. For example, if the line quality is good, port speed and block size could be set to a higher value. On the other hand, when line quality is not so good, these 2 fields should be set to a smaller value while DL_Ack_TO should be set to a larger value to give sufficient time for link layer retransmission.
One can check the quality of the serial communication between SCUD and the remote node by running "dspsv1" command at the node. This command will show any errors on the serial communication to and from the node. Time-out values at the remote node can also be configured by the "cnfdlparm" command and setting parameters #7 (Session Timeout) and #14 (Rmt Response TO).
Log files are stored in the log directory under SCUD home directory. Messages are appended to these log files continuously even when SCUD is restarted. When they grow to certain size, they are moved to *.old and new log files are used. When the new log files are full again, the *.old will be overwritten. In other words, only one backup is kept to prevent using up all disk space.
These log files are there to help debugging in case problems occur. User should saved these files when there is problem. Otherwise, there is no need to backup these files.
There are some debugging capabilities built into SCUD as highlighted here:
1. Higher levels (L3 and L4) of verbose messages for log/svmain.log can be enabled at SCUD start-up time and toggled on/off during run time. To enable these levels of verbose messages at start-up time, modify the "start_SCUD" script to include "-w" command line option for socketd as follows:
#!/bin/sh # # $RCSfile: start_SCUD,v $ $Revision: 1.1.4.1 $ # # -f option for topod and configd need to point # the same file. # If there is a port conflict then change base # 4000 to some other number. socketd -b 4000 -c config.sv -g 560x342+1+90 -w << ! topod -e topo.err -f cnfnodes downld configd -C cnfnodes
L3 and L4 verbose messages for log/svmain.log can also be toggled on/off by sending SIGUSR2 signal to svmain process. The command is: kill -USR2 <pid> where <pid> is the process id of svmain.
2. Verbose mode can also be turned on for configd process which is responsible for the configuration save and restore operation in SCUD. Modify the "start_SCUD" script to give the "-v" command line option to configd:
#!/bin/sh # # $RCSfile: start_SCUD,v $ $Revision: 1.1.4.1 $ # # -f option for topod and configd need to point # the same file. # If there is a port conflict then change base # 4000 to some other number. socketd -b 4000 -c config.sv -g 560x342+1+90 << ! topod -e topo.err -f cnfnodes downld configd -C cnfnodes -v
The output for the verbose message from configd is stored in "configd.verbose" in SCUD home directory. This file is overwritten every time SCUD is started.
1. At times, user may see the following messages:
ipc.c:598:IPC Connect Failed, Address(4001) PID(25409):: Connection refused topod: send_packet_2_IPX failed, retrying ... ipc.c:598:IPC Connect Failed, Address(4001) PID(25408):: Connection refused topod: send_packet_2_IPX retry succeeded.
This is generated by topod process when it could not communicate with another process due to the start-up time difference. This problem is fixed in SCUD 2.0 that topod will now wait for 1 second and retry until successful. Normally, it takes only one retry to succeed. As long as the "retry succeeded" message is shown, there is no problem and user does not need to restart SCUD. If the "topod: send_packet_2_IPX failed, retrying ..." message keep showing, it usually indicates a serious system problem. User may need to reboot the workstation to clear the problem.
2. If in the middle of a SCUD session, the phone line dropped or hung, user has to restart SCUD to re-establish the connection.
In the case that modem connection is made by tip or other communication tools, the re-established connection may appear to be "dead" (no prompt or any data), or showing some garbage. This is because at the remote node, it is still in StrataView mode so it would not send the VT100 screen data. User can launch SCUD as usual and SCUD would be able to communicate with the node in StrataView mode. However, if user wants to make sure the connection is working, user can send the DEL character to the remote node by pressing the "Del" key on the workstation. This will toggle the node's control port function back to VT100 mode. User would be able to see the node's login prompt.
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.
Posted: Mon Dec 20 14:18:19 PST 1999
Copyright 1989-1999©Cisco Systems Inc.