® Software Release Notice for 5.0rev1 CS3 and MMS3 ! CAUTION The CS3 portion of the CD includes SPECTRUM core updates. The MMS3 portion includes new and updated versions of management modules. Once the CS3 software has been installed, you MUST install the MMS3 versions of any management modules previously installed in your database.
Software Release Notice for 5.
Notice Cabletron Systems reserves the right to make changes in specifications and other information contained in this document without prior notice. The reader should in all cases consult Cabletron Systems to determine whether any such changes have been made. The hardware, firmware, or software described in this manual is subject to change without notice.
Restricted Rights Notice (Applicable to licenses to the United States Government only.) 1. Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. Cabletron Systems, Inc., 35 Industrial Way, Rochester, New Hampshire 03866-5005. 2. (a) This computer software is submitted with restricted rights.
Contents Chapter 1 Introduction Purpose of This Document..................................................................................... 1-1 Purpose of CS3 and MMS3.................................................................................... 1-2 New Features and Support.................................................................................... 1-3 Chapter 2 Installation Overview.........................................................................................................
Other Problem Resolutions ........................................................................... 4-13 MMS3 Known Anomalies .................................................................................... 4-14 Management Modules Included in MMS3.......................................................... 4-18 Cabletron Management Modules in MMS3 ................................................. 4-18 Third Party Management Modules in MMS3 ..............................................
Chapter 1 Introduction This chapter provides an overview of this document and the CS3 and MMS3 software. Purpose of This Document This Software Release Notice (SRN) accompanies the CD containing the Core Supplement (CS3) and Management Module Supplement (MMS3) software for SPECTRUM Enterprise Manager 5.0rev1. The SRN is also available on Cabletron’s Web site at: http:// www.cabletron.com/support/. This SRN performs the following functions: • Describes the purpose of this software release.
Purpose of CS3 and MMS3 • Describes anomalies (with solutions or workarounds when available) that have not been previously documented. See CS3 Known Anomalies on Page 3-7 and MMS3 Known Anomalies on Page 4-14. • Describes new problem resolutions incorporated in CS3 and MMS3. See Problems Resolved in CS3 on Page 3-2 and Problems Resolved in MMS3 on Page 4-5. Purpose of CS3 and MMS3 The CS3 and MMS3 software portions of the CD perform the following functions for SPECTRUM 5.0rev1.
New Features and Support management modules included in MMS3 that you have purchased. See Chapter 4, MMS3 Software Characteristics, for details on the MMS3 software and listings of the management modules included in MMS3. NOTE As a minimum, all of the management modules in your current SPECTRUM database must be re-installed from the MMS3 software in order for your SPECTRUM 5.0rev1 system to operate properly. Installation of MMS3 requires a Key provided with the CD.
New Features and Support Introduction 1-4 Software Release Notice for 5.
Chapter 2 Installation This chapter describes how to install the CS3and MMS3 software. Overview The installation procedures described in this chapter include four basic steps that must be performed in the following order: 1. Save the files indicated and then shut down all SPECTRUM processes. See Pre-Installation Instructions on Page 2-2. 2. Insert the CS3/MMS3 CD and run the CS3 installation program. See Installing CS3 on Page 2-5. 3.
Pre-Installation Instructions NOTE CS3 must be installed in its entirety (prior to installing the MMS3 software) on all systems containing a SpectroSERVER or SpectroGRAPH. It is not necessary for CS2, MMS2, or any of the patches listed in Chapter 5, Software Superseded by CS3/MMS3, to have been installed on your SPECTRUM 5.0rev1 system prior to installing CS3. Pre-Installation Instructions Perform the steps described below before invoking the CS3 Install program.
Pre-Installation Instructions NOTE Attempting to apply an unnecessary patch will do no harm since the Sun patch installation software detects whether a particular patch is needed by verifying that the package it pertains to is currently installed on your system. 2. Save your current CsStdMenu file by changing directory to /app-defaults and copying CsStdMenu to CsStdMenu.ori at the command line.
Pre-Installation Instructions Users who are unfamiliar with the SPECTRUM installation process should refer to the SPECTRUM Installation Guide before proceeding with the CS3 and MMS3 installations. You must install CS3 before installing MMS3. NOTE Table 2-1. SunOS Patches for Solaris 2.7 (Minimum Revision Level) Patch-rev Installation 2-4 Description 106144-08 SunOS 5.7: Elite3D AFB Graphics Patch 106145-07 SunOS 5.7: Creator 7 FFB Graphics Patch 106146-07 SunOS 5.
Installing CS3 Table 2-1. SunOS Patches for Solaris 2.7 (Minimum Revision Level) Patch-rev Description 107709-02 SunOS 5.7: libssasnmp/libssagent/snmpdx/mibiisa Patch 107716-02 SunOS 5.7: PGX32 Graphics Patch Installing CS3 Install the CS3 software as described below. NOTES 1. Refer to the SPECTRUM Installation Guide for instructions on installing from a local or remote CD-ROM drive. 2. For Windows NT, use the SpectroSHELL by selecting it from the SPECTRUM Programs folder. 1.
Installing CS3 a. On Solaris: /newtar xvudf /vtape.0 b. On Windows NT: /newtar xvpdf /vtape.0 4. Bring up the Install GUI by typing: ./Install NOTE If the custom installation mode was used to install the 5.0rev1 release, then it is necessary to install CS3 in the custom installation mode.
Installing CS3 Solaris Link Errors for CS3 Please wait! Installation is now building SpectroSERVER This may take several minutes... Undefined first referenced symbol in file __0oKCsIHRtrSumctR6NCsMTypeHandleP6NCsAttrValListTCRC6L CsRel HandleUl Cs8021QMI.o __0fMCsIHIfConfigQinterface_changeRC6NCsModelHandleih.a(CsIH NbldrIf.o) __0fTCsIHDeviceIsolationQassert_conditionRC6NCsModelHandleUl NCC ih.a(CsIHChsIsol.o) __0fMCsIHRPAMaintQcheck_against_PARC6NCsModelHandleP6ICs IPAddr ih.a(LbIHMPPALMn.
Installing CS3 CsATMIfPtMI.o: error LNK2001: unresolved external symbol "public: __thiscall CsIHIfStat::CsIHIfStat(class CsMTypeHandle &,unsigned long,unsigned long,unsigned long,unsigned long,class admin_op *)" (??0CsIHIfStat@@QAE@AAVCsMTypeHandle@@KKKKPAVadmin_op @@@Z) CsCSIIfPtMI.
Installing CS3 unsigned long)" (?assert_condition@CsIHDeviceIsolation@@MAEXABVCsModelHandl e@@KKK@Z) LbModuleMI.o: error LNK2001: unresolved external symbol "protected: virtual enum CsIHIfConfig::CsInterface_e __thiscall CsIHIfConfig::interface_change(class CsModelHandle const &)" (?interface_change@CsIHIfConfig@@MAE?AW4CsInterface_e@1@AB V CsModelHandle@@@Z) ih.a(CsIHNbldrIf.
CS3 Post-Installation Instructions CS3 Post-Installation Instructions Perform the following steps to verify and modify your files, as necessary. 1. Change directory to /app-defaults and compare the file CsStdMenu with CsStdMenu.ori, which is the file you saved prior to this installation. Edit CsStdMenu to restore any customized settings you may have had in CsStdMenu.ori. 2. Change directory to /SG-Tools and compare the file dtxscript with dtxscript.
Installing MMS3 Installing MMS3 This section describes how to start the MMS3 installation on the Solaris and Windows NT systems. These instructions are intended for users who are familiar with SPECTRUM installation. Management module installation from the CS3/MMS3 CD proceeds in the same manner as the installation from a SPECTRUM distribution CD. If you are unfamiliar with this process, we recommend that you refer to the SPECTRUM Installation Guide to get complete installation information.
Installing MMS3 Starting the MMS3 Install on Windows NT Systems Starting the MMS3 Install on Windows NT Systems 1. Open the Start menu and select the Run option. The Run dialog box displays. 2. In the Open field, enter the letter designation for your CD-ROM drive followed by the directory and application name as in the following example using the E drive: E:\mms3\setup.exe 3. Click OK in the Run dialog box to bring up the SPECTRUM Installation screen. 4.
Chapter 3 CS3 Software Characteristics This chapter describes the contents of the CS3 software. MMS3 is described in Chapter 4. The following subsections are included in this chapter. • Previous Releases Included In CS3/MMS3 (see below) describes what previous SPECTRUM 5.0rev1 software is being superseded by virtue of its incorporation into CS3/MMS3. • Problems Resolved in CS3 on Page 3-2 describes problem resolutions that have not been addressed in any previous off-cycle release.
Problems Resolved in CS3 • CS3/MMS3 supersedes all of the problem resolutions originally incorporated in the CS1/MMS1 software for the first time. See the Section titled Other Resolutions Included in CS1/MMS1 on Page 5-7 for descriptions of these items. • CS3/MMS3 supersedes all of the off-cycle releases since CS1/ MMS1 was released (i.e., Patches SPECTRUM_5.0rev1.P17 through SPECTRUM_5.0rev1.P51).
Problems Resolved in CS3 The resolution was to add a default value for Model_Name so that the application name could be displayed properly. GIB enumerations were added to the Model Information view GIB file so that the correct values would be displayed for Model State, Condition, and Contact Status.
Problems Resolved in CS3 case, the "No User Model" error should always be the one to be displayed. The resolution was to add a special case to the code to handle the scenario when the Unknown Landscape error is received after a previous error when the service is unusable. Now, the error with the most useful information will always be displayed. 5.
Problems Resolved in CS3 8. The problem was that the RFC1516 applications and the ones like it have their own reconfiguration time interval and no event was being created when the applications were reconfigured. The CONFIGINTERVAL attribute is set to 60 seconds by default. Pipes between devices were being lost as a result of these unmonitored reconfigurations because the configuration interval of the applications did not match that of the parent device.
Problems Resolved in CS3 The resolution was to change the MAPAPI object, CsPackedVib, so that pipes would not be lost in the above scenario. 13. The problem was that duplicate events were being created when a primary and secondary SpectroSERVER were using the same Archive Manager. The secondary server was configured with the secondary_polling flag set to TRUE so that the secondary server was ready when the switchover to the secondary server occurred.
CS3 Known Anomalies CS3 Known Anomalies The following SPECTRUM 5.0rev1 anomalies are associated with this release of CS3/MMS3. 1. SNMP agents on certain devices will report back inconsistent chassis configuration information, causing pipes to disappear between board models in the Topology view. This will occur when the SNMP agent reports a configuration omitting one or two boards on one read and then includes the boards on the next read.
CS3 Known Anomalies 6. The ability of a FanOut and/or Unplaced model to provide alarms on their connected port's status was removed from SPECTRUM 5.0rev1. The present workarounds for this problem are: a. Create SpectroWatches that would generate an alarm if either the ifOper or ifAdmin status of the port was other than 1. b. Turn Live Pipes on for the links of the monitored interfaces and change the filter in the Alarm Manager to show Maintenance alarms.
CS3 Known Anomalies releases of SPECTRUM will be built with the Solaris 5.0 C++ compiler. 11. On Windows NT systems, the TFTP Download view in NetWideApp does not list multiple 6H202-24s when selected for download. Selecting a single device does work.
CS3 Known Anomalies CS3 Software Characteristics 3-10 Software Release Notice for 5.
Chapter 4 MMS3 Software Characteristics This chapter describes the contents of the MMS3 software. MMS3 provides updated and additional management modules and support as described in this chapter. The following topics are covered: • New Support and Functionality in MMS3 (see below). • Problems Resolved in MMS3, starting on Page 4-5. • MMS3 Known Anomalies, starting on Page 4-14. • Management Modules Included in MMS3, starting on Page 4-18.
New Support and Functionality in MMS3 New Support and Functionality in MMS3 The MMS3 software provides SPECTRUM 5.0rev1 with support for the items described below. Cabletron Management Modules SM-CSI1077, CyberSwitch IP Routers Added support for SSA_7xx. Also, support for HSIM_SSA7xx added to management modules supporting this HSIM. SM-CSI1082, SmartSwitch 6000 Fast Ethernet Switches Added support for the 6H262-18 module. SM-CSI1085, Cabletron ATM - Zeitnet 1. Management module updated from Beta to FCS.
New Support and Functionality in MMS3 Third Party Management Modules Third Party Management Modules SM-3CM1009, 3Com SuperStackII/FMS TR Hub Added traps. SM-3CM1010, 3Com US Robotics Modem New Beta management module supports US Robotics modem pool. SM-3CM1011, 3Com Linkswitch 1100/3300/3400 1. Management module updated from Beta to FCS. 2. Added support for firmware 2.21. SM-CAT1005, Catalyst 29xx Management module updated from Beta to FCS.
New Support and Functionality in MMS3 Other Added Support and Functionality SM-WEL1003, Bay Networks Wellfleet Router 1. Added wf03ISDN_App, wf03DLS_App, and wf03WCP_App for the ISDN, DLS, and WCP MIBs. 2. Device Chassis view now provided. Device > Chassis selection now available from the Icon Subviews menu of wf01FDDI_App and wf03FDDI_App. 3. Management module now supports 13.X firmware. Other Added Support and Functionality Cisco Routers 1. New application, CiscoCSNA_App, supports CISCO-CIPCSNAMIB. 2.
Problems Resolved in MMS3 Problems Resolved in MMS3 The following problem resolutions have not been addressed in any previous off-cycle releases. Cabletron Management Module Problem Resolutions SM-CSI1012, FDMMIM For the FDDI and Ethernet ports, the Port Configuration view no longer generates the error message: Model to read from is Null. SM-CSI1022, Cabletron MicroMMAC-E 1. Condition colors for CSIIfPorts now display correctly. 2. The NetWideApp utility now successfully launches for the MicroMMAC device.
Problems Resolved in MMS3 Cabletron Management Module Problem Resolutions SM-CSI1066, SmartSwitch 9000 (9H421_12) The Port Bridging Status no longer displays UNK (unknown) in the Device Chassis and Device Interface (Bridging mode) views. SM-CSI1068/1080, SmartSwitch 2000 Ethernet and Fast Ethernet AutoDiscovery and Model by IP now detect duplicate models for all model types. If a duplicate model is detected, an error message appears and the model is not created a second time.
Problems Resolved in MMS3 Cabletron Management Module Problem Resolutions SM-CSI1076, 6E132-25 (CtRemoteApp) 1. The ds1 Alarms Circuit Configuration view and the DS3 Extensions view no longer contain ??? in some of the information fields. 2. The CtRemoteApp name is now visible when the Application view is in List mode. SM-CSI1076/1082/1088, SmartSwitch 6000 1. Devices that support distributed mode functionality now model correctly. This includes the SFSmartCell and SmartSwitch 6000 DMF mode devices.
Problems Resolved in MMS3 Cabletron Management Module Problem Resolutions SM-CSI1085, Cabletron ATM - Zeitnet 1. Multiple interfaces are no longer mistakenly created if the connection is lost to a device supported by SM-CSI1085 (for example, when the device is rebooted). 2. There are now menu options for Device view and Configuration view when right-clicking on the Device icon. 3. A Duplicate IP alarm notification now occurs when a second ZX250 is modeled with an IP address used by another ZX-250. 4. The .
Problems Resolved in MMS3 Third Party Management Module Problem Resolutions 2. The Special Database option is no longer present in the Device Chassis view. For bridging devices supporting the Special Database, the option is available in the respective CT_BdgTR_App and CT_BdgEnet_App applications. HSIM-W6 High Speed Interface Module 1. The DevTop view now displays without an error message being generated. 2. The Device Interface view now displays interfaces.
Problems Resolved in MMS3 Third Party Management Module Problem Resolutions SM-BAY1000, BayStack Ethernet Hubs 1. The Baystack 350-24T now models as the HubBatSt350 model. It no longer comes up as GnSnmpDev. 2. The HubBaySt450 Large icon and Application Device icon now display in the Device Configuration and Chassis Group views. SM-CAT1002, Catalyst 5000/5500/5509 1. The Device and DevTop views of the HubCat5000 and HubCat5500 now work correctly.
Problems Resolved in MMS3 Third Party Management Module Problem Resolutions SM-CAT1005, Catalyst 29xx 1. A Cisco Catalyst C2924M-XL now models as a HubCat29xx with a device type of Cat_2924MXL. It had been modeling incorrectly with a device type of Cat_2926R. 2. The Off Page Reference Iib for the HubCAT29xx no longer has an extra "(" in one of the entries for OPRYArw.Loc (down arrow). Therefore, SpectroGRAPH no longer crashes when navigating into the DevTop view of a newly connected device.
Problems Resolved in MMS3 Third Party Management Module Problem Resolutions SM-FOR1000, ForeRunner ATM Switch Modules The Inload and OutLoad watches no longer show a status of Failed in the Watch Editor off of a ForeSwitchApp model type, which had occurred due to an overflow in the binary operator. SM-GHOXXXX, Host Devices On systems with a Host management module, the following message no longer appears in the VNM.OUT file and Control Panel: failure to read attribute: 0x1161009.
Problems Resolved in MMS3 Other Problem Resolutions SM-SYN1009, SynOptics Stackable Hubs 2900 Series The HubSny29xx Large icon now shows the model name at the top. Also, double-clicking it will bring up the SynOptics Chassis Configuration view. SM-WEL1003, Bay Networks Wellfleet Router The Rtr_Bay_Wflet interface information is now read from the proprietary interface tables as well as MIB II. In this way, all of the interfaces should be created correctly.
MMS3 Known Anomalies MMS3 Known Anomalies Following are the known anomalies in MMS3, listed as they apply (i.e., by device type, management module number, application, or model type). SM-CSI1014, Standard RMON App 1. The performance information is red boxed in the Token Ring Promiscuous Segment Performance view. 2. The RMON Suite SPMA will remain blank indefinitely under certain conditions of OID comparison for particular model types. This will be addressed in a future release of SPECTRUM.
MMS3 Known Anomalies 2. The Switching Application Interface Configuration view is missing the IfIndex and Max VPCs columns. This is a firmware related issue. 3. When you double-click one of the rows in the Switching Application AAL5 VCC Performance view, the Detail view displays with red boxes around VPI and VCI. This is a firmware related issue. 4. There may be red boxes in the CAC Stats view of the Switching Application for all model types. This is a firmware issue that is fixed with firmware 2.2.
MMS3 Known Anomalies Interface view and the Chassis or Device Interface views display incorrect information. This problem will be addressed in a future release of SPECTRUM. 2. The SSR_PortIf icons are missing information, particularly VLAN information. This will be addressed in a future release of SPECTRUM. SM-CSI1095, STS16 Token Ring Switch 1.
MMS3 Known Anomalies 2. When the HubBaySt450 is connected to a LAN or Universe container, the Off-Page Reference is a Large Device icon instead of the triangular OPR icon. SM-CAT1005, Catalyst 2900 Red boxes display around the information area of the Port Configuration view accessed off of Port 1 in the Device view of the HubCat29xx, while other ports appear OK. SM-CAT1006, Catalyst 4xxx There is no Alert Map for the SwCat4xxx. SM-CIS1002, LightStream 1010 1.
Management Modules Included in MMS3 SM-WEL1003, Rtr_Bay_Wellfleet 1. In the wf03ATM_App Information view, the primary application is displaying "wait..." Also, there are red boxes around the Primary Address and User-Defined Type fields in the Banner of the Information view. 2. The views of the wf04FDDI_App application do not show correctly. The Chassis view does not appear correctly and the Icon Subviews menu show as default GIBs. 3.
Management Modules Included in MMS3 Cabletron Management Modules in MMS3 NOTE Table 4-1. In the table below, an asterisk (*) beside the Part Number denotes a management module that has been incorporated in a maintenance release for the first time. An asterisk (*) beside the Model Type name denotes a new model type that has been added by MMS3. A double asterisk (**) beside the part number denotes a management module that was a Beta product and is now FCS.
Management Modules Included in MMS3 Cabletron Management Modules in MMS3 Table 4-1.
Management Modules Included in MMS3 Cabletron Management Modules in MMS3 Table 4-1.
Management Modules Included in MMS3 Cabletron Management Modules in MMS3 Table 4-1.
Management Modules Included in MMS3 Cabletron Management Modules in MMS3 Table 4-1.
Management Modules Included in MMS3 Third Party Management Modules in MMS3 Table 4-1. Cabletron Management Modules Included in MMS3 (Continued) Part Number Model Type Management Module SM-CSI1091 SmartSwRtr SmartSwitch Router SM-CSI1092 9M426_02 SmartSwitch 9000 Dual Slot Carrier Module Third Party Management Modules in MMS3 Table 4-2 lists all of the third party management modules included in the MMS3 software. Some of these may have been updated in MMS3. NOTE Table 4-2.
Management Modules Included in MMS3 Third Party Management Modules in MMS3 Table 4-2.
Management Modules Included in MMS3 Third Party Management Modules in MMS3 Table 4-2.
Management Modules Included in MMS3 Third Party Management Modules in MMS3 Table 4-2.
Management Modules Included in MMS3 Beta Management Modules in MMS3 Table 4-2. Third-Party Management Modules Included in MMS3 (Continued) Part Number Model Type Management Module SM-SYN1008 HubSyn27xx SynOptics Stackable Hubs 2700 Series SM-SYN1009 HubSyn29xx SynOptics Stackable Hubs 2900 Series SM-UNB1001 HubUB7xx....
Management Modules Included in MMS3 Beta Management Modules in MMS3 Table 4-3.
Management Modules Included in MMS3 Beta Management Modules in MMS3 MMS3 Software Characteristics 4-30 Software Release Notice for 5.
Chapter 5 Software Superseded by CS3/ MMS3 This chapter describes the patches and problem resolutions that were previously issued for SPECTRUM 5.0rev1 and are being superseded by the CS3/MMS3 software. CS3/MMS3 supersedes CS1/MMS1, CS/MMS2, and the following previously issued SPECTRUM 5.0rev1 off-cycle releases (Patches) and other problem resolutions. • The off-cycle releases (Patches) that were originally superseded by CS1/MMS1.
Patches Originally Superseded by CS1/MMS1 See the Section titled Problems Resolutions Included in CS2/ MMS2, starting on Page 5-32. • The off-cycle releases (Patches) issued since the CS2/MMS2 release. See the Section titled Patches Issued Since the CS2/MMS2 Release, starting on Page 5-34. Patches Originally Superseded by CS1/ MMS1 The following SPECTRUM 5.0rev1 off-cycle releases (Patches) were originally superseded by the CS1/MMS1 software and are now being superseded by the CS2/MMS2 software.
Patches Originally Superseded by CS1/MMS1 SPECTRUM_5.0rev1.P04 A request has been made to add a "flagable" option so that child attribute information is not gathered. Without it, the Server pegs at 98% for the time (3+minutes) it takes to gather attributes. The mask strings stored in the description field for a 4.0rev3 configuration are not shown in the Mask window when that configuration is imported into 5.0.
Patches Originally Superseded by CS1/MMS1 SPECTRUM_5.0rev1.P09 SAS export gives incomplete results for some model entries. SPECTRUM_5.0rev1.P10 Obsoleted by P16. SPECTRUM_5.0rev1.P11 Destroying a model in CLI that does not have a model name fails. Allow the user to configure the timeout value in the configuration file (.vnmshrc). SPECTRUM_5.0rev1.P12 Obsoleted by P16. SPECTRUM_5.0rev1.P13 coreBuilder5000 fails to get correct bridge MIB information. SPECTRUM_5.0rev1.P14 Obsoleted by P16. SPECTRUM_5.0rev1.
Patches Originally Superseded by CS1/MMS1 The Alarm Manager does not handle a large number of events well in the Events tabbed page of the information panel. The History tabbed page should be rolled into 5.0rev1 since it provides information the user really wants. The history page displays all events for a specified model between creation of an alarm and clearing of the alarm. ForeRunner ports create a red alarm when device attached to the port goes down. These should be yellow alarms.
Patches Originally Superseded by CS1/MMS1 SEHi's are being modeled as GnSNMPDevs. Change the event generated at VNM shutdown so that it gets sent to the VNM model. Add CsIHEpiPoll functionality to improve fault isolation for EPI models. The type fields for some EPI requests are not being set correctly. If the user model has a Community String other than ADMIN, when they try to connect to the 5.0rev1 SERVER from a 4.0rev3 GRAPH, from the command line, the following error appears and no GRAPH appears. % .
Other Resolutions Included in CS1/MMS1 AutoDiscovery causes IH Timer Threads to max out and never decrease. Adisc finishes ok but the server seems to get bogged down and performance suffers. Network load on CsiRptr model is incorrect. EMM-E6 with two WAN Brims will not configure. In the IRM2/IRM3 Performance View, the Load is always zero.
Other Resolutions Included in CS1/MMS1 does not support a standard table of Board.Ports. The instance IDs of the ports are generated randomly by the device and it is up to the MM developer to translate them into standard Board.Port (e.g. 1.1 1.2 1.3 etc...) mappings. This value is stored in a separate attribute created by the MM developer to be displayed on icons for numbering boards and ports in the UI.
Other Resolutions Included in CS1/MMS1 11. The Host Configuration Window during the Verify Operation shows Security Tokens. 12. SpectroGRAPH crashes when a Port Performance View of a device modeled in a remote landscape is scrolled while loading. 13. Running Online Manuals from the SpectroGRAPH, instead of from the Control Panel, can cause an error of “This document could not be found:” when doing a search. 14. ArchMgr very infrequently produces strange output & will not start from CPANEL. 15.
Patches Issued After the CS1/MMS1 Release Patches Issued After the CS1/MMS1 Release The following SPECTRUM 5.0rev1 patches are superseded by CS2/ MMS2. SPECTRUM_5.0rev1.P17 Obsoleted by installing CS1/MMS1, P20, and P22. SPECTRUM_5.0rev1.P18 Running adisc in a LAN with Centillion devices causes the server to core dump. SPECTRUM_5.0rev1.P19 Obsoleted by the installation of CS1/MMS1 and P21. SPECTRUM_5.0rev1.P20 Included in P31, P34, P37, P41, and P48. SPECTRUM_5.0rev1.P21 Included in P33. SPECTRUM_5.0rev1.
Patches Issued After the CS1/MMS1 Release 2. The maximum number of requests that MALT can send to a server has been increased from 1000 to 8000. 3. Requests are no longer sent all at once. They are broken up into chunks of 100 and sent at 5 millisecond intervals. This allows MALT to read in some responses that may back up to the point of causing MALT to freeze. SPECTRUM_5.0rev1.P25 Included in P34, P41, and P48. SPECTRUM_5.0rev1.P26 Included in P45. SPECTRUM_5.0rev1.P27 Included in P44. SPECTRUM_5.0rev1.
Patches Issued After the CS1/MMS1 Release This has been resolved by building up the event filter object so that the model handle filter node is at the base of the filter hierarchy with the date/time filter nodes. SPECTRUM_5.0rev1.P30 Unable to assert ORANGE alarm on DLCI_Port w/watcheditor A threshold watch on a DLCI_port model type will not assert an Orange alarm. It will assert a Yellow or Red but not an Orange.
Patches Issued After the CS1/MMS1 Release SPECTRUM_5.0rev1.P33 Host_Compaq does not work well with Insight Mgr 4.11. Compaq has two sets of error logs. One for Insight Manager 4.11 and the other for Insight Manager 3.11. Compaq introduced a new object (attribute) that indicates which set of attributes is being used. The cause of the problem is that two Event Log Views are being displayed in SPECTRUM. Only one of them is supported by Insight Manager, which is determined by the version you are running.
Patches Issued After the CS1/MMS1 Release SPECTRUM_5.0rev1.P39 On Windows_NT, the SpectroSERVER is crashing after a couple of minutes. This is caused by the fact that we don't properly handle changing the icmp packet size on NT. We change the send size, but we don't account for the larger packet on the return. This has been resolved by changing the code to account for the larger packet size. NOTES 1.
Patches Issued After the CS1/MMS1 Release SPECTRUM_5.0rev1.P40 While running SpectroSERVER, when SpectroWATCH executes a script, a small memory leak occurs. This has been resolved by deleting the memory appropriately. While running SpectroSERVER, a small memory leak occurs in SpectroWATCH. This has been resolved by deleting the memory appropriately. (Also refer to the Notes on corrected anomalies, above.) SPECTRUM_5.0rev1.P41 Included in P48. (Also refer to the Notes on corrected anomalies, on Page 5-14.
Patches Issued After the CS1/MMS1 Release for devices with more than 50 instances in the etherstats table. The solution is to increase the number of slots. Token Ring Probes are failing as Monitor Points. This is being resolved by adding the correct attributes to allow this to work correctly. The TR_Mon_Ring_Speed watch is set to read the ifSpeed from the MIB-II Interface Table. The problem occurs in that the OID suffix is set to use the value of the attribute, mp_intefaceOIDref.
Patches Issued After the CS1/MMS1 Release This has been resolved by optimizing the code to read the template and store it rather than repeatedly reading it for each device. In ECM, create a new configuration in the configuration window by adding attributes from the list of attributes shown. Now Undo this insert operation by invoking Edit->Undo Insert from the Menu. The attribute(s) inserted are not shown (refreshed) in the list of insertable attributes window after the Undo Insert operation is performed.
Patches Issued After the CS1/MMS1 Release In all cases, the capture detail window shows the result of each attribute captured, and the configuration is written to the server. In the event of partial success, an additional event is posted to the SS. A new CsEvFormat file (Event00820012) has been added for this purpose. However no alarm is generated. A few non-critical problems that show up: a.
Patches Issued After the CS1/MMS1 Release If a customer has added notes or status to and existing alarm in Alarm Manager, the new changes are not reflected in AlarmWeb view when they happen, although the html files are being updated when the changes happen. The problem is that the pages are being cached in Netscape. This has been resolved by changing the pages so that they are not cached. Alarm Manager is crashing intermittently and no core file is being generated.
Patches Issued After the CS1/MMS1 Release (Also refer to the Notes on corrected anomalies, on Page 5-14.) SPECTRUM_5.0rev1.P49 After running Distributed Find across SpectroSERVER landscapes, the chassis view of the SS6000 and SS9000 boards will not launch in the landscape to which the user is connected. The problem is that when the Distributed Find View is launched, it uses the landscape of the server where the find is being done, instead of the landscape where the SS9000/SS6000 device is actually modeled.
Patches Issued After the CS1/MMS1 Release The solution is to write a new inference handler and attach it to the SS6000 module. It will be responsible for gathering the MAC addresses heard off the SS6000 module's interfaces, as well as the MAC addresses of the modules connected to it via its backplane interfaces. The model state algorithm will also be modified so that a SS6000 module will only go active after it's properly associated with a chassis.
Patches Issued After the CS1/MMS1 Release After moving a card in the 9000 chassis to another chassis the new inb and chassis are not being created. When a 9000 (MMACPlus) board is removed from the chassis and then reinserted, its System Up Time is reset to zero. Spectrum detects this and attempts to reconfigure. If the board was moved from one slot in a chassis to a different slot in the same chassis, this is correctly identified, and the DevTop and Chassis Device views etc.
Patches Issued After the CS1/MMS1 Release 2. Also during the discovery MAC addresses are found and connected to the device. These are incorrectly modeled as Physical_Addr. The Hub3ComSSTR_A should get placed in an 802_5 LAN container. The resolution is that a new inference handler has been written to handle the AutoDiscovery issue and the database attributes have been modified so that the device will be placed in the correct container. (Also refer to the Notes on corrected anomalies, on Page 5-14.
Patches Issued After the CS1/MMS1 Release BRGMAP hangs and is using 95%+ cpu. For each port on each bridge in the LAN, there is a method that determines potential connections to other ports on other bridges in the LAN using two techniques. The first technique creates a "potential" connection if both ports’ SAT tables know about each other.
Patches Issued After the CS1/MMS1 Release The Interface Description Map on the HubCat models cannot be resized. This has been resolved by increasing the size of the GIB when it is displayed. The values in SW_Link performance view all say "failed." The performance view for the monitor point, which is an ATMIfPort, has values of "failed" as well. The attributes being used for those fields -InLoad, OutLoad, InCellRate, OutCellRate, and ErrorCellRate, are all red-boxed in the attribute browser.
Patches Issued After the CS1/MMS1 Release from false to true and then reconfigure. This has been resolved by changing the default value for Create_Sub_Interfaces to TRUE. WA_Link monitor points are lost if one of the routers on either side is rebooted. The problem is that the intelligence which finds and maintains the monitor point for the container (in this case a WA_Link) has not been designed to handle the case where all potential monitor points which the container could use go down, i.
Patches Issued After the CS1/MMS1 Release Open the Device Chassis View of a 6E122-26, then select the field "Physical" of a board and open the Icon Subview Port Display Form. You are able to switch from Operational Status to Duplex Mode but you cannot switch back to Operational Mode again. The same behavior exists when you switch to Speed and then back to Operational Mode. This has been resolved by allowing the user to switch back to Operational Mode.
Patches Issued After the CS1/MMS1 Release scheduled intervals. You have to reset the Background Discovery in order for it to start running again. This has been resolved by changing Background Discovery to only reset every time the SpectroSERVER is shut down. Customer states that, under 4.0Rev3, although the SNMP get packet that was issued on behalf of an active GIB view did exceed the max length that his agent was capable of handling, the DCM did successfully process all of the data: 1.
Patches Issued After the CS1/MMS1 Release Cs_get_diskio: kstat_read: No such device or address Solaris 2.6 and beyond allows finer granularity of performance statistics on disks. Two things can happen, both of which are unnecessary. Items can be subdivided into partitions, and the software can try to collect information on NFS mounted directories. This does not stop the information from being collected; it just places a message into the VNM.OUT every 10 seconds while the I/O Statistics GIB is open.
Patches Issued After the CS1/MMS1 Release capacity and response time. A .vnmrc entry can be added to allow the randomization period to be set. This entry is: mdl_act_dist_factor. The Archive Manager is crashing and producing a core file. This is caused by a double-delete occurring when running a Data Export when the user no longer has permission to access a model. This has been resolved by deleting the memory correctly.
Patches Issued After the CS1/MMS1 Release For epapi, the port to NT introduced the "sigaction_thread()" function, which runs on its own native NT thread upon call to EPI_fcntl(). This function is implemented to always synchronize with the Cs_EPI_pause() method, to be called from the application thread. Unfortunately, this implementation changes the EPI interface, now requiring that Cs_EPI_pause() be called in order for ANY IO notification to occur.
Problems Resolutions Included in CS2/MMS2 (Also refer to the Notes on corrected anomalies, on Page 5-14.) Problems Resolutions Included in CS2/ MMS2 CS2/MMS2 provided resolutions for the following problems. 1. The UpTime attribute in SpectroWATCH formulas has been changed to type TimeTicks to avoid wrap-around errors and ensure the accuracy of certain load computations. 2. A new relation now exists for FddiConcentrators to prevent model destruction in the Lost & Found view. 3.
Problems Resolutions Included in CS2/MMS2 13. Pingable models now receive Alerts generated from SNMP Traps. 14. Final changes have been made to allow printing of more than one model per page. 15. SPECTRUM Data Export scheduling no longer fails with the message: Not authorized to use cron. 16. Cisco 2501s and 7500s modeled as Rtr_Cisco are no longer missing applications and lacking necessary containers. 17. CLI no longer fails to connect from SpectroWatch script. 18.
Patches Issued Since the CS2/MMS2 Release Patches Issued Since the CS2/MMS2 Release SPECTRUM_5.0rev1.P52 The problem was that a pointer in the SM-3CM1006 product was not being checked and therefore was being dereferenced. If this occurred during an AutoDiscovery the SpectroSERVER would core dump. The resolution was to put a check on attrval lists that were not being verified before they were being used.
Patches Issued Since the CS2/MMS2 Release SPECTRUM_5.0rev1.P53 Included in SPECTRUM_5.0rev1.P101 -SPECTRUM_5.0rev1.P54 Included in SPECTRUM_5.0rev1.P101 -The problem is with the DLCI_port model type. In SPECTRUM, the port would toggle between GREEN and RED (up and down) after a DLCI connection was made then broken on a router supporting DLCI. There is an attribute called "dlcistate" which is one of 11 internal/ external attributes for the DLCI_port model type.
Patches Issued Since the CS2/MMS2 Release SPECTRUM_5.0rev1.P57 Included in SPECTRUM_5.0rev1.P101 -SPECTRUM_5.0rev1.P58 The problem was that the Enterprise Configuration Manager needed long model name support for both configurations and templates in ECM. The maximum length for configurations or templates was 16 characters. Currently, the only long model name support was for devices that were created in SPECTRUM (modeled) and viewing them through ECM.
Patches Issued Since the CS2/MMS2 Release way as the c1400/c1100 and therefore you are also unable to store configs via the current version of ECM." The resolution was to incorporate a check to find out if the model type against which ECM was run was HubCat1400 or SwCat1200. If it was then the module value setting in CAT_TFTP_MODULE is set to 3 else the module setting remains at 1. For HubCat1400/SwCat1200 devices, host configuration operations can only be performed using ECM. Scmbg cannot be used.
Patches Issued Since the CS2/MMS2 Release SPECTRUM_5.0rev1.P59 Included in SPECTRUM_5.0rev1.P101 -SPECTRUM_5.0rev1.P60 The problem is when using DLS1000 and modeling Rtr_Cisco the AppnSessApp has a view called APPN Session Information View. This view has a number of columns. There are 2 problems with it. a. The rows of columns are not separated enough. This causes the top of the titles in 2nd and 3rd rows to be cut off. b. The ProCorrID is should be displayed as hex instead of text.
Patches Issued Since the CS2/MMS2 Release -SPECTRUM_5.0rev1.P66 The problem was that two icons for the 3Com Link Switch 3000 (Hub3ComLS3000) model type were showing different looking DevTop views. The Topology View icon and the Off Page Reference (OPR) icons were the two icons in question. The resolution was to have the OPR icon DevTop view match that of the Topology View icon. -SPECTRUM_5.0rev1.P67 The problem was there was no support for traps of the 3Com FMS Token Ring device Management Module.
Patches Issued Since the CS2/MMS2 Release Spectrum_5.0rev1.P46 against CS1/MMS1. There is no problem with printing to a printer that does not support color printing. The resolution was to write a script which installs gs5.50 (an executable called ghostscript). It takes the GRF filename, device type, gs5.50 install location as settable parameters and generates the appropriate print files using ghostscript.
Patches Issued Since the CS2/MMS2 Release (2) labels on both the axis (3) header section of the html files generated along with the gif files. Corresponding to each of these the new variables the file and valid values are given below. (1) in $SPECROOT/report.config/default.
Patches Issued Since the CS2/MMS2 Release SPECTRUM_5.0rev1.P71 Included in SPECTRUM_5.0rev1.P101 -SPECTRUM_5.0rev1.P72 The problem was that AutoDiscovery and Modeling by IP allowed duplicate models without warning for the following model types: 2E43_51 and 2H23_50R or any other device covered under SMCSI1068 or SM-CSI1080.
Patches Issued Since the CS2/MMS2 Release This problem was two-fold: There was an attribute, PORTS_STATE that did not exist for any SS2000 model type that was NOT derived from MicroLANModule (most 2000 devices). The intelligence tried to read this attribute before it got through any of the application association processes. When the attribute read failed (on a device that didn't have the attribute), the association process was bypassed altogether, and the model state never reached the active state.
Patches Issued Since the CS2/MMS2 Release -The problem is when Cabletron EMME, MicroMMAC and SEHi devices reboot the security configuration is deleted and must be manually reconfigured on the box. The customer would like the ability to use ECM to save and restore port locking information on these devices. These devices use RptrRev4Mib and they do not include the security attributes available in the RptrRev4SecMib.
Patches Issued Since the CS2/MMS2 Release rptrPortGrpSASecurityLearnMode rptrPortSecurityPortGrpId rptrPortSecurityPortId rptrPortSecurityLockStatus rptrPortSecurityLockAddAddress rptrPortSecurityLockDelAddress rptrPortSecurityDisableOnViolation rptrPortSecurityFullSecEnabled rptrPortSecuritySecureState rptrPortSecurityForceNonSecure rptrPortSecurityLearnState rptrPortSecurityLearnMode rptrPortSecurityListPortGrpId rptrPortSecurityListPortId rptrPortSecurityListIndex rptrPortSecurityListAddress -SPECTRUM_5
Patches Issued Since the CS2/MMS2 Release server to gather all alarms and distribute them to the trouble ticketing software from there. The resolution was to identify and correct the code that was causing the violation. The fix was tested at the customer site and the Segmentation Fault did not occur anymore. -SPECTRUM_5.0rev1.P76 The problem was that SPECTRUM was not processing traps correctly for UpsApc92xx. The Event were being documented as "Unknown alerts received from device".
Patches Issued Since the CS2/MMS2 Release SPECTRUM_5.0rev1.P80 The problem was there was some difficulty running AR System Gateway 5.0rev1 with Remedy's new 4.0 version. Several issues were addressed and the particulars are written below. For NT Only. The version of runmacro.exe and rcmn40.dll shipped with this product is 4.0. For Solaris only. The automatic Trouble Ticket Generator (arsgated) is linked with AR System 3.2 APIs. This patch was developed and tested with NT and Solaris AR System 4.0.2.
Patches Issued Since the CS2/MMS2 Release Trouble Tickets will display ARERR[1200]. The solution is to do the following steps after modifying the SPECTRUM password. NT -1) Verify the SPECTRUM user's home folder is $SPECROOT/ ars_gateway. 2) From the start menu run Action Request System @4.0/Remedy User. Login using the SPECTRUM user and new password. 3) $SPECROOT/ars_gateway/ar.ini has now been updated with the new password. Solaris ----1) Open a term window.
Patches Issued Since the CS2/MMS2 Release because the long cause text causes the runmacro command line arguments to get truncated. 9) Not Importing Active Links When importing the SPECTRUM Trouble Ticket Form you may choose not to import the SpectrumView and SimilarTickets active links. In this case when you display the SPECTRUM Trouble Ticket the buttons for these active links are displayed but when you try to execute them nothing happens. This is a Remedy issue.
Patches Issued Since the CS2/MMS2 Release SpectroSERVERs as well. To test the the primary/backup switchover they did the following: a. brought down the MOM SpectroSERVER b. watched as the secondary SpectroSERVER took over c. brought back the MOM SpectroSERVER and saw the map storm d. If the mapstorm in the previous step occurred - the e. If the mapstorm in the previous step occurred - the AlarmNotifier did not connect successfully.
Patches Issued Since the CS2/MMS2 Release It was found that running both AlarmNotifierA and AlarmNotifierB on serverA, and doing the same changes, both AlarmNotifiers are updated correctly with a new alarm coming through.
Patches Issued Since the CS2/MMS2 Release were selected. Also, filter changes are not alway saved although the "Make Permanent" button is selected. The resolution was to change the condition and state preferences so that they are *NOW* manually written out instead of relying on the preference binders. -SPECTRUM_5.0rev1.P85 The problem was when SPECTRUM lost SNMP contact (i.e. via incorrect community name) with a 3Com FMS the model turned RED instead of ORANGE.
Patches Issued Since the CS2/MMS2 Release for table STAT_ROUT Oracle sends out a message that the index does not exist, and an "insufficient privileges" message when it tries to create the index. These messages obviously occur because the actual table that is being loaded is STAT_ROUT_new. Also, when SPECTRUM models are exported daily the SDEOraImport script automatically assumes that an overwrite is in order. The actual table name is SPECTRUM.MODELS.
Patches Issued Since the CS2/MMS2 Release -SPECTRUM_5.0rev1.P90 Obsoleted by SPECTRUM_5.0rev1.P100 -SPECTRUM_5.0rev1.P91 Obsoleted by SPECTRUM_5.0rev1.P100 -SPECTRUM_5.0rev1.P92 Included in SPECTRUM_5.0rev1.P101 -SPECTRUM_5.0rev1.P93 Obsoleted by SPECTRUM_5.0rev1.P100 -SPECTRUM_5.0rev1.P94 Obsoleted by SPECTRUM_5.0rev1.P100 -SPECTRUM_5.0rev1.P95 Obsoleted by SPECTRUM_5.0rev1.P100 -SPECTRUM_5.0rev1.P96 Obsoleted by SPECTRUM_5.0rev1.P100 -SPECTRUM_5.0rev1.P97 Obsoleted by SPECTRUM_5.0rev1.
Patches Issued Since the CS2/MMS2 Release SPECTRUM_5.0rev1.P98 Obsoleted by SPECTRUM_5.0rev1.P100 -SPECTRUM_5.0rev1.P99 Obsoleted by SPECTRUM_5.0rev1.P100 -SPECTRUM_5.0rev1.P100 Included in SPECTRUM_5.0rev1.P101 -SPECTRUM_5.0rev1.P101 The problem was after modeling a TRMM with a TRMIM-62A, the Chassis Logical View doesn't appear correctly. In the devtop view, the TRMIM-62A is labeled "unknown" in the chassis in the center top window. This occurs with 3.01.01 and 3.02.00 firmware.
Patches Issued Since the CS2/MMS2 Release The resolution was to modify SPECTRUM so that GREY devices will be continually pinged. -The problem was the connection between the Frame Relay subinterface and ATM subinterface was not resolved. Some background information that will make the resolution more understandable is as follows: In 5.0rev1, we use FR DTE to resolve the conductivity of FR interfaces down to the DLCI ports.
Patches Issued Since the CS2/MMS2 Release Cases to be considered: (1) One side is a FR sub-interface; other side is not and has not been modeled yet. Skip resolving the FR sub-interface. Only do the normal FR DTE map on the FR physical interface. We may also place a LAN/WA_Link off the FR sub-interface.
Patches Issued Since the CS2/MMS2 Release The problem was a SpectroGRAPH core dump was occurring when the cacheZoomedImages from False to True and the defaultZoomLevel was set to 50%. A core trace was made available. Further, if the resource "*shadow" in the spectrum file is set to "false" setting *cacheZoomedImages to true dumps SpectroGRAPH.
Patches Issued Since the CS2/MMS2 Release The resolution was to reduce the size of the external attribute request list to the device by half and making two request lists instead of one. This was necessary because the the list of requests being sent to the device was too large for the device to handle. -The problem was SpectroSERVERs participating in a virtual landscape map were not sending updates when they updated their own copy of the map. Therefore, servers in the map ended up with dissimilar maps.
Patches Issued Since the CS2/MMS2 Release -The problem is WA_Links are not clearing alarms when WA_Segment is replaced or moved to a different port with a good condition. The problem presents itself because alarms are not disasserted before a model is destroyed. This has been resolved by disasserting the alarm before the model is destroyed. -The problem is Gen_IF_Port model names do not show up correctly in PGUI applications. This is caused because watches don't work properly when the db flag is not set.
Patches Issued Since the CS2/MMS2 Release a reconfigure of the Management Module the Preferred Addresses table still contains the IP's that were removed. The resolution was to add functionality that will allow the Redundancy Preferred Address list to be flushed when performing a reconfiguration of the device. A new Boolean attribute has been added to model type RedundancyMF. It is called flush_RPA, and it's default value is TRUE.
Patches Issued Since the CS2/MMS2 Release The problem is trying to capture a host config with an ECM template containing only the host config for a HubCAT1400 fails. The error message received is: "Capture Failed" and clicking on the Details button shows the message, "Cannot find error code in ECM_ERROR file: 0x200000c". Also, closing the Details button and then clicking on it again produces a core dump of the ECM.
Patches Issued Since the CS2/MMS2 Release -The customer needs to have more flexibility with the Event Configuration Manager for assigning levels of access for users in different managed subnets, i.e. user "A" can use CM in subnet "A" but not in subnet "B". -The ECM has been altered so that ECM will not read the community string of the user.
Patches Issued Since the CS2/MMS2 Release 9A128_01. All these devices are used to connect Ethernet, token ring and FDDI (conventional networks) to ATM Networks. This was happening because the GET_ATM_PORT_LIST action was not able to respond to devices using the CtATMConfigMib model type versus the ATMClientApp model type. The resolution was to attach an inference handler to the CtATMConfigMib modeltype so that devices using it will respond to the GET_ATM_PORT_LIST action.
Patches Issued Since the CS2/MMS2 Release The resolution was to add a check in the View Information Block to prevent any further SpectroGRAPH crashes while Editing and Save & Closing while new models are being created. -The problem was Range Router AutoDiscovery was not discovering second tier routers. An example of a scenario where this would occur is as follows: The customer had 16 backbone routers. They also had 400~900 second tier routers in a few hundreds ClassB networks.
Patches Issued Since the CS2/MMS2 Release The problem was the Annotation Toolbox did not use the same grid as the SpectroGRAPH did, regardless if *snapGrid: was set to True or False. This was resulting in some movement of text and graphics when views were cloned and/or zoomed to lesser or greater sizes. The resolution was to correct the zoomed and unzoomed coordinate calculation so that they did only assume the view was at 100%. -Memory leak found in CsRMNSetup.
Patches Issued Since the CS2/MMS2 Release Thus, CsIHRouterMap::get_subnet_list() should never return a NULL pointer, unless the scratchpad is not able to read. In this case, the caller of get_subnet_list() should check the returned pointer before dereferencing it. Another problem was Fanouts were being placed onto FrameRelay Port interface models in the DevTop View of a device supporting FrameRelay. At times, DLCI port were being connected to the Fanouts (which should not be possible) and/or LAN models.
Patches Issued Since the CS2/MMS2 Release This problem was also found with the following iibs files: HubCat1400/ CatDev.GSISd, HPAdvStkHub/HPAdvStkHub.GSISd, and HubSyn27xx/Syn27xx.GSISd -When viewing the device chassis view for any SS2000/SS6000, the ports display as UNK....(blue). They do not go into an active (green) state. This has been resolved by installing the missing core components. -The problem was during AutoDiscovery the SpectroSERVER would core dump.
Patches Issued Since the CS2/MMS2 Release The resolution was to create an action object that can be added to an iib file for an icon. The action will take name of menu, action code and text that describes that action to be displayed along with the returned error from the action. -The problem was that SpectroGRAPH was crashing (with a trace) consistently in cases where a device was not initialized correctly, the SpectroSERVER was down, etc.
Patches Issued Since the CS2/MMS2 Release respond to the Get_Address_List action. The GmIHRptrSrcAddr inference handler is getting "no such attr" errors when attempting to read attributes that do not exist in the CsRipEnetRptr. The resolution was to add a new method which can be called by an MI Node if desired to change which attribute ids are used for reads. -The problem was that sometimes the CsIGModel icon in the QuickFind view (custom view) appeared unselected and could not be selected manually.
Patches Issued Since the CS2/MMS2 Release -The problem was multiple memory leaks were found due to the creation of HubBaySt450. Purify had been installed and a trace was made available. The resolution was to remove the memory leaks from the code pinpointed by the Purify traces. -The problem was a memory leak was found due to the creation of a 6E233_49. Purify had been installed and a trace was made available. The resolution was to remove the memory leaks from the code pinpointed by the Purify traces.
Patches Issued Since the CS2/MMS2 Release The problem is that the CsGib/HubCat5000/CsConfg.GTb table has incorrect column heights which causes the listbox to create a horizontal scroll bar outside the viewing area. This causes the SpectroGRAPH to core dump when viewed if the text exceeds the specified length. The resolution was to change the column heights to fit inside the viewable area. -The problem was that the Device Chassis View of the 2E253-49 was not comprehensible.
Patches Issued Since the CS2/MMS2 Release before it got through any of the application association processes. When the attribute read failed (on a device that didn't have the attribute), the association process was bypassed altogether, and the model state never reached the active state. The second issue was similar. The SS2000 devices in question did not have a DEVICE_MDL_HANDLE attribute (again, because they were not derived from MicroLanModule).
Patches Issued Since the CS2/MMS2 Release board and concentrator level. The user should be able to modify certain attributes of the concentrator, board, and port as needed. -The problem was the ctUPSApp model was not appearing in the MicroMMAC's Application View even though a UPS was physically connected to the com 1 port of a MicroMMAC. The ctUpsID oid had to be set through mibtools before the model would appear.
Patches Issued Since the CS2/MMS2 Release rptrSrcAddrMgmtHashType rptrSecurityLockState rptrSecuritySecureState rptrSecurityLearnState rptrSecurityLearnMode rptrPortGrpSrcAddrLockGrpId rptrPortGrpSrcAddrLock rptrPortGrpSASecuritySecureState rptrPortGrpSASecurityLearnState rptrPortGrpSASecurityLearnMode rptrPortSecurityPortGrpId rptrPortSecurityPortId rptrPortSecurityLockStatus rptrPortSecurityLockAddAddress rptrPortSecurityLockDelAddress rptrPortSecurityDisableOnViolation rptrPortSecurityFullSecEnabled rpt
Patches Issued Since the CS2/MMS2 Release The problem was that the RMONFilter and RMONPacketCapt had an OID set by sys_oid_verify when the did not need one. Further, the OID was identical to the one set for a HubSynTR3xxx model. This was causing problems when modeling a HubSynTR3xxx with Model by IP. Upon modeling a HubSynTR3xxx with model by IP the device would get a yellow alarm and model mismatch error. The resolution was to remove the sys_oid_verify value for the RMONFilter and RMONPktCapt model types.
Patches Issued Since the CS2/MMS2 Release to: TR_Mon_Util=((MonBitsUsedPerSecs*100)/TR_Mon_Ring_Speed) b. WatchBitprsec - which calculates the load for Token Ring. The formula was changed from: MonBitsUsedPerSec=TR_Mon_Bytes_Per_Second*8 to: MonBitsUsedPerSec=INTEGER((COUNTER_DELTA (mp_mlayStsOctest)*8 + COUNTER_DELTA (mp_mlayStsPkts)*8*21)/COUNTER_DELTA(TIME)) ** NOTE: A factor of "21" was used to account for framing bytes vs. 17.
Patches Issued Since the CS2/MMS2 Release For example: If port 1A1 of switch A is connected to 1D4 of switch B , the ATM discovery establishes the Link connection between two ports as 1A1 -- CONNECTS_TO -> Fanout <- CONNECTS_TO -- 1D4 The fanout will be collected by SW_LINK model .
Patches Issued Since the CS2/MMS2 Release whether it is an ATM port. If it is an ATM port it will remove any connects_to relation that this port has. Since for GenSwitchPort the value returned by is_port_ATM is FALSE, the connection will not be removed. The resolution was to add a check in the is_port_ATM() function to return a value of TRUE if the IFTYPE is GenSwitchPort.
Patches Issued Since the CS2/MMS2 Release -The problem was ATM discovery was not resolving any connections other than those between ForeSwitches. When ATMDISC was run against an ATM network none of the LaneClient (9A128/9A426/ SS2200), ZX250 (6ATSM, 9A100), or Predator connections are resolved, and an error message was produced: *** Error: Cannot obtain ATM neighboring devices for ATM switch 0x5700016 The resolution was in several parts: 1.
Patches Issued Since the CS2/MMS2 Release The problem was ATM Discovery ran it tried to resolve all the ATM models in the database. This should only occur when you run AutoDiscovery from the Universe view. If AutoDiscovery is run from a IPClassX, Network or LAN container it should only look at the ATM switches contained within it and those that are connected to them. The resolution was in several parts: 1.
Patches Issued Since the CS2/MMS2 Release (0x10c48) is read for each ATM Network model found. In case the AutoDiscovery is launched from AtmNetwork model itself then it will be added to the network_list. -The problem was a multiple memory leaks were found while Spectrum_5.0rev1, Spectrum_CS2/MMS2, Spectrum_5.0rev1.P54 and Spectrum_5.0rev1.SLAM-P54 were installed. Purify had been installed and a trace was made available.
Patches Issued Since the CS2/MMS2 Release action, i.e. anything that's capable of DMF, AutoDiscovery will do nothing, and the Management Module will set up the Collects relationship with their topologically significant models. For the SS6000, this will be all the blades, for the 9AXXXX-XX boards, this will be the SFSmartCell. -The problem was when a socket to a SpectroSERVER was blocked, new alarms from that server stop showing up in clients which show alarms. Cleared alarms persist.
Patches Issued Since the CS2/MMS2 Release -The problem was that SpectroSERVER was core dumping several times over a period of three days. All the SPECTRUM systems were in a distributed environment using a MOM SpectroSERVER as the main location server and for modeling remote landscapes.
Patches Issued Since the CS2/MMS2 Release would occur anyway. All the DLCI OIDs which were not read successfully from the device would then be then destroyed from the Frame Relay Modeling. The resolution was to add a check called DCM_END_OF_TABLE. This check will make sure that only the whole table was read before the reconfiguration could occur. If the whole table is not read, the reconfiguration will not occur.
Patches Issued Since the CS2/MMS2 Release The problem was that an error shows up in the SPECTRUM Control Panel when the Event Configuration Editor is launched from it. This occurs on the Windows_NT platform only and the error message is: errorCsTSsteae_VendorError: The directory cannot be found. Configure trap mappings will not be available This occurred even though the user had full permissions to the entire CsVendor directory, and the $SPECROOT, $SG_INSTALL_ROOT.
Patches Issued Since the CS2/MMS2 Release Router. When the Bridge went physically down both the bridge and the router went GRAY. The Bridge should have gone RED and the Router GRAY but that did not happen since the Bridge was connected to the FDDIMac_NM. The resolution was to add functionality so that if contact to a device is lost and that device has a non-manageable neighbor upstream, that upstream device will now go RED instead of GRAY.
Patches Issued Since the CS2/MMS2 Release The problem was modeling 9A656_04's or 9A686_04's as SFSmartCell Models with other 9000 boards also created causes the incorrect DevTop View to be displayed. The resolution was to correct the display action of the DevTop for the SFSmartCell and now the correct DevTop view will come up for every 9000 board that is modeled. -The problem was GIB views displaying a SPECTRUM view Banner from the 6H133_37 Management Module showed no value for the Manufacturer attribute.
Patches Issued Since the CS2/MMS2 Release CsIHRollPL will transmit the SPECTRUM event from the router device model to the appropriate port instance if the information is contained in the trap. This inference handler is attached at the GenSnmpRouter model type. Therefore, it only seems to be running for router model types at the moment.
Patches Issued Since the CS2/MMS2 Release set of ifType ports throughout the enterprise, these traps are simply the result of a transient remote connection, which is being deliberately disconnected by the remote user. Alarm generation is unwanted in these cases, and currently imposes a real burden on the alarm management process.
Patches Issued Since the CS2/MMS2 Release The problem is there is excessive polling with SPECTRUM 5.0rev1, which results in a "sluggish" system. The resolution is to correct two aspects of performance and polling in SPECTRUM. First, a new method was created to make performing external reads more efficient by treating each each list attribute to be read as a separate entity. Second, a a new gather_ext_list method in CsModel will cause an additional get_next request to go to the device.
Patches Issued Since the CS2/MMS2 Release The problem is that there is now way for SPECTRUM to integrate devices or find a particular interface by using Secondary IP address. Since SPECTRUM does not store secondary ip addresses in the database, there's no way of being able to do a find on them. SPECTRUM only puts one of possibly many IP Addresses in the "ip_address" attribute of an interface model. SPECTRUM uses the term "secondary ip address" to indicate the other ip addresses of the interface.
Patches Issued Since the CS2/MMS2 Release for the connected devices. When the device is shut off the contact closure is noted by the Sentinel and a trap is sent. The trap is mapped to an event that creates an alarm. The trap represents a Telcom device being turned on. Before the alarm is cleared, the Telcom device unexpectedly switches off which sends another trap to Spectrum.
Patches Issued Since the CS2/MMS2 Release The problem is that IfDescr and IfName need to be displayed on all Gen_IF_Ports icons. The resolution was to update the Iib so that IfDescr/IfName could be user configurable. IfDescr is displayed by default. If the user wishes to display ifName instead, comment out the first line and uncomment the second line in the Gen_IF_Port/IFacePrt.IFCE and Gen_IF_Port/ IFaceTwo.IFCE Iib files. PrtLabel.
Patches Issued Since the CS2/MMS2 Release intel will set the AlarmOnLinkDown attribute to "Never" to suppress the critical alarms which are otherwise asserted. b. New NPC scenarios involve a variable, router and router port on the host side of the connection, the answering side. The current modeling only works with the specification of a specific single port. With the exception of accurate fault isolation, the entire Dial Backup management can be obtained by monitoring the remote router.
Patches Issued Since the CS2/MMS2 Release The problem was the customer was continuing to have problems viewing data and statistics after migrating their database from SPECTRUM 4.0rev3 to SPECTRUM 5.0rev1. Some of these problems were originally fixed with Spectrum_5.0rev1.P36. Apparently SPECTRUM was continuing to cut off the range if it rolled over a year.
Patches Issued Since the CS2/MMS2 Release The resolution was to add inferencing to alarm/disalarm ports upon receiving a LINK UP or LINK DOWN trap. -The problem was ISDN interfaces were receiving constant LinkDown alarms, despite Disable Trap Event being set to "TRUE" and Alarm on Link Down Trap being set to "NEVER" in the Model Information View of the interfaces.
Patches Issued Since the CS2/MMS2 Release The resolution was to make the appropriate database change so that the CTM_Switch_MTH / 0xd80084 attribute of the 9A686_04 model could be read by the SFSmartCell model. -The problem was the DevTop View was not launching off of the SFSmartCell model. The resolution was to correct code so that the DevTop View successfully off of the SFSmartCell model wherever it is an option.
Patches Issued Since the CS2/MMS2 Release -The problem was that LAN models were not getting created correctly (or at all in some cases) when modeled through AutoDiscovery. In one case, a customer used AutoDiscovery to model a SmartSwitch router 8000 as a seed router. The router had 45 ports, six of which had direct routes in the ipRouteTable. After the discovery, the only pipes to the router were from a fanout and a 9H421_12.
Patches Issued Since the CS2/MMS2 Release an off-page reference icon of the router in the switch's devtop. Each time the customer drew a pipe, he did a tcpdump between the VNM and the switch to which he is drawing a pipe. Each of the tcpdumps shows that the VNM only queries the dot1dTpFdbTable for MAC address X, and ignores Y and Z.
Patches Issued Since the CS2/MMS2 Release The problem is with the DLCI_port model type. In SPECTRUM, the port would toggle between GREEN and RED (up and down) after a DLCI connection was made then broken on a router supporting DLCI. There is an attribute called "dlcistate" which is one of 11 internal/ external attributes for the DLCI_port model type.
Patches Issued Since the CS2/MMS2 Release -The problem was that while running a "Reconfigure Model" on an rtr_cisco (Cisco 2501) it was found that the SPECTRUM AutoDiscovery would dead-lock at a router model which originally had a data relay class of 0. When the data relay class was changed from 0 to 3 the AutoDiscovery would still dead-lock. Presently, only one scratchpad is shared by all router actions.
Patches Issued Since the CS2/MMS2 Release WatchEditor was shut down then restarted that the truncating problem occurred. The resolution was to increase the formula size limit to 2K for the saved format of the expression. This allows for larger expressions to be saved without incident. If an expression still exceed the formula limit in its saved format (vs. original format) then a error dialog box will appear suggesting that the watch be broken up into two or more smaller watches.
Patches Issued Since the CS2/MMS2 Release The resolution was to make the alarm clearable through SPECTRUM AlarmNotifier. The alarm will generated when the device is modeled and upon device reconfiguration. -The problem was a memory leak was found due to the creation of a HubSyn5xxx. Purify had been installed and a trace was made available. The resolution was to remove the memory leaks from the code pinpointed by the Purify traces.
Patches Issued Since the CS2/MMS2 Release The resolution was to add the ability to use a Gen_IF_port as a monitor point for the sw_link. This will allow Performance View statistics to appear. -The problem was when a model was created of type Gen9000 or Gen6000, the ports in the Device->Chassis view were displayed with an icon similar to what would normally be seen in the DevTop view, instead of the way ports were normally displayed in the chassis view.
Patches Issued Since the CS2/MMS2 Release During router mapping process (AD_ROUTER_MAP action), we read each entry from the router's scratchpad and map the interface in the scratchpad entry. Since FR sub-interfaces were not scratched by their own IF index(all info was scratched under the FR physical IF), we don't actually resolve each individual FR sub-interface. When mapping the FR physical interface, we are actually dealing with the map of this side DTE to the other side DTE.
Patches Issued Since the CS2/MMS2 Release (4) One side is not a FR sub-interface; but other side is FR subinterface and has already been modeled. Using other side FR sub-IF scratchpad to do the normal mapping. -The problem was a sw_link that was attached to a Zeitnet switch was showing a value of "FAILURE" in it's Performance View statistic fields. The resolution was to add the ability to use a Gen_IF_port as a monitor point for the sw_link. This will allow Performance View statistics to appear.
Patches Issued Since the CS2/MMS2 Release The problem was that the SpectroSERVER was crashing with an mts malloc out of memory error when the Asnd_MAX model was in the database. When this model was not present, the SERVER would not crash. The crash was caused by the negative value being returned by the device for mdmNumber. The resolution was to add a check to make sure the value returned for mdmNumber was not negative. The SpectroSERVER should no longer crash when the Asnd_MAXmodel is in the database.
Patches Issued Since the CS2/MMS2 Release The problem was certain error messages (ie. failure to read attribute: 0x1161009) were being displayed in the VNM.OUT that should have been hidden from the user. The resolution was to suppress the error message.
Patches Issued Since the CS2/MMS2 Release Software Superseded by CS3/MMS3 5-110 Software Release Notice for 5.
Chapter 6 Files Shipped With CS3 This chapter lists the SPECTRUM files that are shipped with the CS3 software. The CS3 software includes the following deliverable files listed by product name. CORE SS/SS.o SS/core.e SS/.vnmrc SS/libEPI.a SS/libIHapi.a SS/libVPapi.a SS/libGlobl.a SG/CsGoSPMA.o SG/CsUserDefAct.o Ibm6611 SG-Support/CsGib/AppnSessApp/SessGenTab.GTS SG-Core SG/SG.
SG/libUIapi.a SG/libVPapi.a SG/libGlobl.a SG/libPort.a SG-Tools/stdmenu/salt_stdmenu SG-Tools/SALT ndlib/salt.dat SG-Tools/appdef/spectrum SG-Tools/appdef/spectrum.ENG SG-Support SG-Support/CsGib/LostFound/CsStandard.30 SG-Support/CsGib/FaultIsolation/CsPerform.30 SG-Support/CsGib/LivePipes/CsPerform.30 SG-Support/CsGib/LivePipes/CsStandard.
MF SS/a1count.o SS/a1guage.o SS/a1uint.o SS-Tools/dbpart1/a1count.o SS-Tools/dbpart1/a1guage.o SS-Tools/dbpart1/a1uint.o SM-COMMAN SG/CsSbMnuIcon.o SG/CsDevIcon.o SG/CsDISwGag.o SG/CsDISPARel.o SG/CsDIPtFmSta.o SG/CsGoInsNW.o SG/CsRdAttInNW.o SG/CsZAppView.o SG-Support/Enumerations/iftype.txt SS/CsIHSyncRd.o SS/CsSbMnuIcon.o SS/V3COREMM-CSI.e SS/V3COREIM-CSI.e SS/CsColFddiMI.o SS/CsIHUPSInit.o SS/CsIHIfStat.o SS/CsIHColFddi.o SS/CsPAppLst.
SS/CsIHSyncRd.o SS-Tools/dbpart1/V3COREIM-CSI.v SM-CSI1017 SG-Support/CsGib/GnSNMPDev/CsFIConfig.30 SG-Support/CsGib/GnSNMPDev/CsRdndOpt.30 SG-Support/CsIib/GnSNMPDev/Large.Bas SG-Support/CsIib/GnSNMPDev/Small.Bas SG/CsDynImage.o SG-Support/CsEvFormat/Event003d0001 SS/CsGnSNMP2MI.o SS/CsVendor/Ctron_SNMP/GnSNMPDev/AlertMap SS/CsVendor/Ctron_SNMP/EventDisp SS/CsIHChasCtl.o SS/CsIHChasMgr.o SS/CsIHChasSup.o SS/CsPortGroup.o SS/CsIHRlayFnc.o SM-DBCONV SS-Tools/DBconv SM-GEXT SG-Support/CsIib/Ds3App1407/Ds3App.
SG-Support/CsGib/Ds3App1407/CsDs3Intv.30 SG-Support/CsGib/Ds3App1407/CsDs3Intv.GTb SG-Support/CsGib/Ds3App1407/CsDs3Totl.30 SG-Support/CsGib/Ds3App1407/CsDs3Totl.GTb SG-Support/CsGib/Ds3App1407/CsStandard.30 SG-Tools/pib/SM-GEXT.p SG-Support/CsGib/CmUPSApp/CsPerform.30 SG-Support/CsGib/CtUPSApp/CsPerform.30 SS/SM-GEXT.e SS/CsEGP1AppMI.o SS/CsEGP2AppMI.o SS/CsICsMPAppMI.o SS/CsIP1AppMI.o SS/CsSNMP1AgMI.o SS/CsSNMP2AgMI.o SS/CsTCP1AppMI.o SS/CsTCP2AppMI.o SS/CsUDP1AppMI.o SS/CsUDP2AppMI.o SS/Cs1512MI.
SS/CsDTRIfApMI.o SM-GMMADISC SS/GmIHRpSrAdr.o SS/GmIHdot1Bdg.o SM-GNBDG SS/CsGBdgAppMI.o SS/CsStaAppMI.o SS/CsIHSpanCtl.o SS/CsIHPtStAct.o SG-Support/CsGib/GenBridgePort/CsStandard.30 SG-Support/CsGib/GenBridgePort/CsTrapConf.30 SM-GNRTR1 SG-Support/CsGib/FrameRelayPort/CsStandard.30 SG-Support/CsGib/FrameRelayPort/CsTrapConf.30 SG-Support/CsGib/Gen_IF_Port/CsStandard.30 SG-Support/CsGib/Gen_IF_Port/CsTrapConf.30 SG-Support/CsGib/Serial_IF_Port/CsStandard.30 SG-Support/CsGib/Serial_IF_Port/CsTrapConf.
SS/CsIHDLnkTrp.o SS/CsIHRtrSum.o SS/CsIHIpRoute.o SS/CsGSnmpRMI.o SS/CsIHSnmpRRoll.o SS/CsATAppMI.o SS/CsGenIFMI.o SS/CsIPAppMI.o SS/CsRtrAppMI.o SM-GNSW SG/CsGoGnInDMH.o SS/CsIHWSSet.o SS/CsIHSwLkMP.o SS/CsIHSwMPAp.o SS/CsIHPStAct.o SS/CsIHGIfDesc.o SS/CsIHSwPtEv.o SS/CsIHSwRdIn.o SS/CsGnSwPrtMI.o SS/CsSWLinkMI.o SS/CsSwPrtTyMI.o SNSMP-CSI SS/CsIHSnmpPIf.o SS/SMSNP-CSI.e SS/CsDcmBlkLst.o SS/CsSnmpIf.
SS/CsSV1Ident.o SS/CsSV1PIfUniq.o SS/CsSnmpV1PIf.o SS-Tools/dbpart1/SMSNP-CSI.v actn SG/CsGoSPMA.o SG/CsUserDefAct.o adisc SS/CsIHIfTypeL.o SS/CsIHBkgrdDis.o SS/CsIHSNMPRtr.o SS/CsIHTblDisc.o SS/CsIHRtrMap.o SS/CsIHRtrDisc.o SS/CsIHVerByIP.o SS/CsIHDevDis.o SS/CsTVIBMI.o SS/ADIfType.o adisc_opt SG-Tools/RTRDISC SG-Tools/ARTDISC SG-Tools/BRGMAP SG-Tools/HUBMAP SG-Tools/autodisc alarm SG-Support/CsExtProcess/AlarmView Files Shipped With CS3 6-8 Software Release Notice for 5.
SG-Support/CsResource/language/alarm.default SG-Support/CsHelp/AlarmView/default/findinfo/info.htm SG-Support/CsHelp/AlarmView/default/images/infopanl.gif SG-Support/CsHelp/AlarmView/default/images/prefer3.gif SG-Support/CsHelp/AlarmView/default/settings/pref.htm cview SG-Support/CsScript/ClientView event SG-Support/CsExtProcess/EventLog findv SG/CsFCCreate.o SG/CsFCView.o SG/CsFInit.o SG/CsFView.o genv SG/CsAppBtn.o SG/CsIGModel.o SG/CsIGSecTxt.o SG/CsMltGphAbs.o SG/CsIGMngNbor.o icon SG/CsIAniMult.
malt SG-Tools/MALT SG-Tools/SSMALT mapv SG/CsTAddIP.o SG/CsTNormal.o SG/CsPLLServer.o SG/CsTView.o net_dev SG-Support/CsGib/WA_Link/CsStandard.30 npc SS/CsDialupLinkMI.o SS/CsIHDialCond.o SS/CsDBLData.o SS/CsIHDialTrap.o SS/CsIHDialConn.o SS/CsIHDlUnreach.o SG-Support/CsExtProcess/PrimIFConfig ssroe_core SG-Tools/reconfig SG-Tools/hierarchy SG-Tools/reconfig.txt SG-Tools/hierarchy.txt SG-Support/CsResource/language/ssroe.
steae SG-Support/CsExtProcess/ECEditor SG-Support/CsResource/language/steae.default uiapi SG/libUIapi.a SG-Support/CsScript/CsPrint SG-Support/CsScript/CsXwdPrint SG-Support/CsScript/CsXwdToPcl SG-Support/CsScript/CsXwdToPs SG-Support/CsScript/CsXwdToXwd usred SG-Support/CsScript/UserEditor vnm SS/vnm.e watch-ih SS/SwReader.o SS/SwLoopDetct.o SS/SwIHControl.o SS/SwIHEval.o SS/SwIHEval2.o SS/SwIHAlarmEd.o SS/SwCallComp.o SS/SwDescBase.o SS/SwError.o SS/SwGenPurp.o SS/SwInstInfo.
SS/SwInstInfoL.o SS/SwIntDesc.o SS/SwIntThold.o SS/SwMdlOvride.o SS/SwPCause.o SS/SwTholdBase.o SS/SwThreshld.o SS/SwUIDesc.o SS/SwUIThold.o SS/SwValList.o SS/SwWInfRepN.o SS/SwWatchInf.o SS/SwString.o SS/CsInterp.o SS/CsIobject.o SS/CsIobjectL.o SS/CsIops.o SS/CsIstack.o SS/CsStrstack.o SS/CsIvnmops.o SS/SwLex.o SS/SwYacc.o watch SG-Tools/WatchManager SG-Tools/WatchEditor SG-Support/CsResource/language/watch.default Files Shipped With CS3 6-12 Software Release Notice for 5.
SMEPI-CSI SS/SMEPI-CSI.e SS/CsIHEpiPIf.o datex SG-Tools/SDE SG-Tools/dataexp SG-Tools/SDEIngImport SG-Tools/SDESybImport SG-Tools/SDEOraImport SG-Tools/dtxscript.tpl ddm SS/DDM/ddm_load SS/DDM/ddm_save SS/DDM/ddm_AttrDict SS/DDM/ArchMgr ecmsprm SS-Tools/dbpart1/CsvScmAtrVL.
rprts SG/Graphrpt SG/Alarms SG/BGArcRpt SG/EventAR SG/Inventory SG/UpDownAR SG/ReportsUI SG/lprps SG/RepGRFtogif SG/rptscript SG-Tools/RibE report.config/default.PRF sanm SANM/PolicyAdmin SANM/associate SANM/xcron sanmtk .SANMTK/lib/libGlobl.a .SANMTK/lib/libPort.a .SANMTK/lib/sanmtk.a spars ars_gateway/SpectrumSchema ars_gateway/Schema.adv ars_gateway/showTT.arq ars_gateway/submitTT.arq Files Shipped With CS3 6-14 Software Release Notice for 5.
ars_gateway/reconfig SG-Support/CsScript/ShowTroubleTickets SG-Support/CsScript/SubmitTroubleTicket ars_gateway/arsgated Notifier Notifier/AlarmNotifier Notifier/AlarmAck Notifier/AlarmClear SA-CSI1011 SG-Support/CsExtProcess/AlarmViewSL SG-Support/CsResource/alarm.default SG-Support/CsHelp/AlarmViewSL/default/findinfo/info.htm SG-Support/CsHelp/AlarmViewSL/default/images/infopanl.gif SG-Support/CsHelp/AlarmViewSL/default/images/prefer3.gif SG-Support/CsHelp/AlarmViewSL/default/settings/pref.
epapi SDK/lib/libEPapi.a globl SDK/lib/libGlobl.a ihapi SDK/include/IHAPI/CsIHThrshld.h SDK/lib/libIHapi.a insdk INSDK/buildfiles/Install.tar INSDK/mkarea vpapi SDK/include/VPAPI/CsActionCode.h SDK/include/VPAPI/CsAlarmCause.h SDK/include/VPAPI/CsAttrValDef.h SDK/include/VPAPI/CsEventTypes.h SDK/include/VPAPI/CsRelDef.h SDK/include/VPAPI/CsRHLst.h SDK/lib/libVPapi.a cmdproc vnmsh/VnmShd vnmsh/.vnmshrc vnmsh/connect vnmsh/create vnmsh/destroy Files Shipped With CS3 6-16 Software Release Notice for 5.
