® Software Release Notice for 5.0rev1 CS2 and MMS2 ! Caution The CS2 portion of the CD includes SPECTRUM core updates. The MMS2 portion includes new and updated versions of management modules. Once the CS2 software has been installed, you MUST install the MMS2 versions of any management modules previously installed in your database.
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 CS2 and MMS2 ................................................................................................ 1-2 New Feature, Solaris 2.7 Support...................................................................................... 1-3 Chapter 2 Installation Pre-Installation Instructions ...............................................
Contents vi Software Release Notice for 5.
Chapter 1 Introduction This chapter provides an overview of this document and the CS2and MMS2 software. Purpose of This Document This Software Release Notice (SRN) accompanies the CD containing the Core Supplement (CS2) and Management Module Supplement (MMS2) 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 CS2 and MMS2 The CS2 and MMS2 software portions of the CD perform the following functions for SPECTRUM 5.0rev1. • The CS2 software provides an interim solution to problems and anomalies associated with SPECTRUM 5.0rev1. It consolidates previous off-cycle releases (Patches) and provides solutions to some problems not previously addressed.
New Feature, Solaris 2.7 Support The CS2/MMS2 software provides SPECTRUM 5.0rev1 with support for the Solaris 2.7 operating system; however, you must install the appropriate SunOS patches for SPECTRUM to operate properly. A complete list of the patches is provided in Table 1-1. The specific patches to be applied depend upon your system configuration. For example, 106144-08, the Elite3D AFB Graphics Patch, only applies if your system contains an Elite3D graphics card. NOTE Table 1-1.
Introduction 1-4 Software Release Notice for 5.
Chapter 2 Installation This chapter describes how to install the CS2and MMS2 software. Although the installation process is identical to that used to install the previously released CS1 and MMS1 software, we urge you to completely read the instructions in this chapter before proceeding. NOTES 1. If you are going to run SPECTRUM 5.0rev1 on the Solaris 2.7 operating system, ensure that the appropriate SunOS patches are installed on your system . (See New Feature, Solaris 2.
ArchMgr, processd, and the Control Panel itself. (ArchMgr should be shut down using the Control Panel's Control menu.) NOTE On Windows NT, extraction of the files LocServer.exe and gzip.exe from the CS2 vtape will fail. This is a result of a problem with NT permissions. To ensure successful extraction of these files, proceed as follows: 1. Using Microsoft Explorer, navigate to the LS directory and rename the file LocServer.exe as LocServer_orig.exe. 2.
WARNING Do not manually deselect components via the Component Selection window. The Install program will automatically select and install those CS2 components that are applicable to your current SPECTRUM installation. Manual deselection of components may result in installation failure and/or incorrect product installation. You may, however, do SpectroSERVER-only or SpectroGRAPH-only installations. 6. Enter the user name of the person performing the installation in the Target Ownership field.
CS2 Post-Installation Instructions Once you have completed the CS2 installation, 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, 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.
Chapter 3 CS2 Software Characteristics This chapter describes the problem resolutions and known anomalies associated with the CS2 software. General Characteristics Listed below (in chronological order) are the categories of problem resolutions that are provided by the CS2 (and MMS2) software. • CS2/MMS2 supersedes all of the off-cycle releases originally superseded by the CS1/MMS1 software (i.e., Patches SPECTRUM_5.0rev1.P01 through SPECTRUM_5.0rev1.P16).
CS2 includes the deliverable files listed in the section titled Files Shipped With CS2, starting on Page 6-1. Problems Resolved in CS2 CS2 provides resolutions for the following problems, which have not been addressed in any previous off-cycle releases. 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.
. CLI no longer fails to connect from SpectroWatch script. 18. The printer dialog box for the Print-View on NT systems now displays, showing the default printer selected. 19. There is no longer a need to manually update the vendor ID list and vendor Name list before running the Event Configuration Editor. 20. Model types and models are now visible in the Reports UI Statistics and Events pick lists. 21. Components in SPECTRUM 5.
There are three valid values for the log state attribute, which are: 0 = NO_LOGGING 1 = LOG_ALL_CHANGES 2 = LOG_VALUE_CHANGES_ONLY When Log_State is 0, no logging is done when an unsolicited message is received. This is important, since the old behavior of logging all INT and REAL changes no longer occurs. When Log_State is 1, logging is done every time a CsEpiVerbAttrChng is received for a given attribute.
4. On Windows NT, extraction of the files LocServer.exe and gzip.exe from the CS2 vtape will fail. This is a result of a problem with NT permissions. To ensure successful extraction of these files, proceed as follows: a. Using Microsoft Explorer, navigate to the LS directory and rename the file LocServer.exe as LocServer_orig.exe. b. Also using Microsoft Explorer, navigate to the Install-Tools directory and rename the file gzip.exe as gzip_orig.exe. c. 5. On Solaris 2.
CS2 Software Characteristics 3-6 Software Release Notice for 5.
Chapter 4 MMS2 Software Characteristics This chapter describes the contents of the MMS2 software. MMS2 provides updated and additional management modules and support as described in this chapter. The following topics are covered: • New Support and Functionality in MMS2 (see below). • Problems Resolved in MMS2, starting on Page 4-2. • MMS2 Known Anomalies, starting on Page 4-4. • Management Modules Included in MMS2, starting on Page 4-8.
10. A new Beta management module (SM-CAT1005) supporting the Catalyst 2900 devices. 11. A new Beta management module (SM-CSI1095) supporting the Cabletron STS16 Token Ring Switch. 12. WS-X5225R EtherChannel Board for the Catalyst 5000 in SM-CAT1002. 13. Catalyst 5509 in SM-CAT1002. 14. CSX5500 in SM-CSI1077. 15. Cabletron TRMIM-62A in SM-CSI1025. 16. Management of the SmartSwitch 9000 EM module COM ports. 17. ELS100-24TXM and ELS100-24TXG in SM-CSI1064. 18. CoreBuilder 3500 in SM-3CM1006. 19.
10. ForeView now launches from NT. 11. Port resolution is now provided when manually modeling a connection between a ForeSwitchApp and an ATM client. 12. CoreWatch now launches from the SSR menu pick. 13. Reports can now be run for a Wellfleet Router's DLCI_Port. 14. A Reconfigure Applications button is provided for Rtr_Bay_Wflet. 15. A new script enables Site Manager to launch correctly. 16. RingDiscover no longer causes SpectroSERVER to crash. 17. 9F120-08 no longer causes SpectroSERVER to crash. 18.
27. AutoDiscovery no longer hangs if the address range includes Wellfleet BLN II routers. 28. Alarms are now supported for the Cisco Access Server, AS5x00. 29. The SmartSwitch Router physical and Logical Device views have been modified so that Quad Serial and Dual HSSI modules now show correctly. 30. The DevTop view now launches correctly for the Cabletron 9A686-04 model type. 31. Double-click zones for the Hub3ComLS3000 Topology view icon and Off Page Reference icon now both access the same DevTop view.
SM-CSI1030 SmartSwitch 9000 (9E132_15) When a SmartSwitch 9000 is modeled using a Gen9000 Model Type, the serial number for the device is not displayed in the Banner of the Configuration, Performance, and Model Information views. SmartSwitch 9000 (9E133_36) When a MMAC+ card is modeled, the serial number attribute (0x10030) is filled in with device data. When the card is replaced in the chassis, next time the view is brought up the serial number is the same.
6E132-25 (CtRemoteApp) 1. The ds1 Alarms Circuit Configuration view and the DS3 Extensions view contain ??? in some of the information fields. Solution: Change the read modes for the attributes to ReadInstance and ReadWriteInstance. 2. The CtRemoteApp name is not visible when the Application view is in List mode. Solution: Place the mouse pointer over the branch where the name should be located to view the pop-up description. Use the right mouse button to view and select the applications subview menu.
SM-3CM1004, SM-3CM1007, SM-3CM1008, SM-3CM1011 All Devices Device models go red rather than orange when the SNMP agent fails. SM-3CM1011 3Com LinkSwitch 1100/3300 When in the Device Chassis view, selecting Print from the File menu and then clicking Print View and OK results in a distortion of the images on the right side of the view. SM-BAY1000 HubBayStack 450 1.
2. The PNNI_App Information view Primary Application button displays "wait...". Solution: The Primary Application button will be removed in a future release. SM-CIS1004 Cisco Access Server CiscoView will not launch from the Access Server’s menu. SM-WEL1003 Rtr_Bay_Wellfleet 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 Information view's Banner.
Cabletron Management Modules Table 4-1 lists all of the Cabletron management modules included in the MMS2 software. NOTE In the table below, an asterisk (*) beside the Model Type name denotes a model type that has been added in MMS2. In any case, for proper operation of your SPECTRUM 5.0rev1 system, you must re-install from MMS2 all Cabletron management modules that are in your current SPECTRUM database. Table 4-1.
Table 4-1.
Table 4-1.
Table 4-1.
Third Party Management Modules Table 4-2 lists all of the third party management modules included in the MMS2 software. Some of these may have been updated in MMS2. NOTE In the table below, an asterisk (*) beside the Part Number denotes a management module that has been added in MMS2; an asterisk (*) beside the Model Type denotes a model type that has been added in MMS2; and a double asterisk (**) denotes a management module that was previously a Beta product and is now FCS.
Table 4-2.
Table 4-2.
MMS2 Software Characteristics 4-16 Software Release Notice for 5.
Chapter 5 Software Superseded by CS2/ MMS2 This chapter describes the patches and problem resolutions that were previously issued for SPECTRUM 5.0rev1 and are being superseded by the CS2/MMS2 software. CS2/MMS2 supersedes CS1/MMS1 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 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. SPECTRUM_5.0rev1.P01 Obsoleted by P16. SPECTRUM_5.0rev1.P02 AutoDiscovery is requesting process status every 2-5 seconds. AutoDiscovery is not reading all ranges in list.
In a summary report, either created through the report formatter or with the included UpDownExec.rib, a line break is included after each summary. Saving the print command in default.PRF for reports causes .gif creation failure. SPECTRUM_5.0rev1.P06 5.0rev1 SANM cannot handle distributed environments if one environment is a SpectroSERVER running SPECTRUM 4.0rev3. SPECTRUM_5.0rev1.P07 5.0rev1 ARS Gateway cannot handle distributed environments if one environment is a SpectroSERVER running SPECTRUM 4.0rev3.
SPECTRUM_5.0rev1.P16 Error while retrieving the alarm history information. An error occurred while retrieving the alarm history information for this model. Error: Error 0x6000020 (0x6000020) Problem with canceling filter when in Modeltypes tab. Get error message when starting AlarmManager as RO user. 5.0rev1 SANM can't handle distributed environments if one is 4.0rev3 SERVER. The Alarm Manager does not handle a large number of events well in the Events tabbed page of the information panel.
OnlineBackup fails on first try. 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. % .
SM-COMRPTR, SM-GENTR, SM-COMMAN, SM-GNBDG, SM-GNRTR1, SMMMSW, seh, SM-CSI1000 and SM-TRHUBSTK. Not all DLCI port models appearing on Rtr_Bay_Wflet DTE. The user is unable to edit a default SpectroWATCH off of the DLCI_Port model type. Destroying any model after performing a find_attr_by_oid crashes the SpectroSERVER. Purify reports leak in CsIHLostAndFoundDestroy::do_destroy. SpectroWATCH calculation causes erroneous overflow error. Cisco routers don't send link up event to clear link down alarm.
4. Assignment Filter Not Working in Enterprise Alarm Manager. The problem only occurs when saving the assignment filter with the "(Unassigned)" entry in the “Hide” list. 5. Corrupt schema files not handled well in Oracle exports 6. IP Address field was added to Event00010017 & Event0001030a. 7. VNM Polling-Related problems were fixed which increases the VNM performance. d. Web AlarmView not updating properly, reading cached pages. 8. Fixed coredump in new APIs. 9.
23. Add PCause information into Event Format files: Event00010701, Event00010702, and Event00010706 24. In a Fault Tolerant environment, the secondary SpectroSERVER may crash. 25. Install error for mtregupd.exe on NT. Unable to locate msjet35.dll. Patches Issued Since 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.
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.P28 Included in P34, P41, and P48.
Models will now reg_watch_change after the first successful read of the model's attributes. When a change does occur, the IH ensures that a write is necessary by checking the current value of the external attribute before writing. FrameRelay DTE models were disappearing. Added code to check that DLCIs are unique before attempting to shift the modeling. SPECTRUM_5.0rev1.P31 Included in P34, P41, and P48. SPECTRUM_5.0rev1.
SPECTRUM_5.0rev1.P35 Included in P50. SPECTRUM_5.0rev1.P36 Included in P47 and P48. SPECTRUM_5.0rev1.P37 Included in P49. SPECTRUM_5.0rev1.P38 The server is terminating when 45% of the models get activated. During startup of the SpectroSERVER, with ChipCom ONline/ONcore Models from the CSEU-CCOM product, when the device cannot be contacted, the logic in CsComMntrIH::trig_model_activate will sometimes cause uninitialized memory to be accessed. This, in turn, causes the server to terminate. SPECTRUM_5.0rev1.
NOTES 1. The following corrected anomaly was included in Patches P40, P41, P42, P43, P44, P45, P47, P48, P49, P50, and P51. When you run an Online Backup from the VNM icon, the status in the Online Backup window reports that the Backup failed. VLAN Manager 1.8 is also installed on the machine. This happens only during a very specific set of events that can come from a vpapi client (VNM, etc.) as follows: 1. Thread A sends a ticket request for the start of a process in the foreground. 2.
SPECTRUM_5.0rev1.P41 Included in P48. (Also refer to the Notes on corrected anomalies, on Page 5-12.) SPECTRUM_5.0rev1.P42 Creating a model by IP via CLI, creates the device as Pingable. This has been resolved by having it create a device with the correct model type. (Also refer to the Notes on corrected anomalies, on Page 5-12.) SPECTRUM_5.0rev1.P43 After installing P23 the following message is printed out in the VNM.OUT file: status=1 status=1, repeatedly. This was caused by debug output left in the code.
initiating the process to discover the RMON groups by creating the RMONCreate model and triggering the correct action. (Also refer to the Notes on corrected anomalies, on Page 5-12.) SPECTRUM_5.0rev1.P44 Capturing of host configs on SmartSwRtr fails with no explanation The error states “Capture Failed” with no details. To reproduce this, go to the configuration screen and perform a capture.
and some default values, for unsuccessful attributes. The result of such a capture operation is "NON_FATAL_ERROR". This does not prevent writing the configuration to database and also shows up as successful, but sends an event to the SS indicating capture “not successful.
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. A bad alarm node is in the table which causes the sorting code to compare bad data and therefore crash. The bad alarm node is in the table because an update occurred with both an ADD and a MODIFY. The same could occur if a REMOVE and a MODIFY came in on the same update.
The reason is because of spanning tree. There are two scenarios that exist that determine how spanning tree is implemented across the backplane. 1. The root bridge is one of the boards inside the chassis. Spanning tree sends BPDU's from the switches to the root bridge. If the root bridge resides inside the chassis, then the BPDU's travel from the other boards across the backplane to the root bridge and back.
The Chassis view for SS6000 devices has an area on the right side of the view for chassis power supply and fan information. Currently no information shows in these boxes. The appropriate methods need to be updated to include appropriate instance information during the reads. The view of the SmartSwitch 6000 backplane does not show the backplane ports (b1, b2, b3, b4, b5) correctly. The ports are not shown in numerical order; at times they show up in random order. The problem is an array indexing problem.
1. The 3ComTRChassisApp is placed in a Network container. There is no devtop for this model to show connections. 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.
about Bridge B and at least one of Bridge B's Ports hears the same devices that Bridge A's ports (other than Port 1) hear. Apparently, this second technique was added when technique 1 did not work with a certain Cisco device even though the Cisco device was connected. The resolution to the current MR is to NOT run the second technique if the bridge is in a SS6000 chassis. The problem of not being able to create a LAN model off a SONET interface (by manual configuration) has been corrected.
When modeling a cisco router with ISDN interfaces, the interfaces are constantly going up and down. This is resulting in the device sending a trap for each occurrence. When the trap is received, SPECTRUM generates a red alarm for each port that goes down. For the ISDN interfaces this is a normal state and the ports should not show an alarm status. The inference handler that is managing the incoming trap has been changed to create just an event, in addition to the all or nothing option now available.
Serial Interfaces. This has been resolved by creating the WA_Link regardless of whether the nexthop device was modeled or not. Annotated text moves across the SpectroGRAPH view to the right (approx 1 to 2 pixels) each time a model is created or destroyed. Zooming the annotations causes X,Y coordinates to be changed, which causes this problem. 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.
agent was capable of handling, the DCM did successfully process all of the data: 1. Through an arbitration type process the DCM removed attributes that were roughly equal to 25% of the total packet size during each iteration, until it finally sent a packet that was small enough to be processed by the Liebert Agent. 2. The remaining attributes were then packed into subsequent packets and sent to the agent for processing. 3.
In SPECTRUM 5.0 and beyond, we do not examine the state of the connected ports during a WA_Link's Fault Isolation process. We simply look at the status of the connected devices. If both devices are up, then the WA_Link will be GREEN. This causes problems when the VNM has a redundant connection to the remote device. When the wide area connection goes down, the VNM will have a second way to contact the remote device, thus we won't lose contact with it.
types were derived from the Composite model type. Unfortunately this resulted in some incorrect fault isolation behavior. After removing Composite as a base model type, it was found in several views that the PatrolView icons were not displayed correctly. By removing Composite, which does the arranging, CsIHVIB was no longer attached. Since PatrolView is a 3rd Party product, there is no access to this core IH. To resolve this, a new model type has been created from which 3rd Party model types can be derived.
Software Superseded by CS2/MMS2 5-26 Software Release Notice for 5.
Chapter 6 Files Shipped With CS2 This chapter lists the SPECTRUM files that are shipped with the CS2 software. The CS2 software includes the following deliverable files listed by Management Module. AutoDiscovery Support (adisc) SS/CsIHIfTypeL.o SS/CsIHBkgrdDis.o SS/CsIHTblDisc.o SS/CsIHRtrMap.o SS/CsIHRtrDisc.o SS/CsIHVerByIP.o SS/CsTVIBMI.o SS/ADIfType.o AutoDiscovery (adisc_opt) SG-Tools/ARTDISC SG-Tools/BRGMAP SG-Tools/HUBMAP SG-Tools/RTRDISC SG-Tools/autodisc adisc_opt.
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 Alarm Manager Application (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.
SG-Support/CsScript/ClientView Data Export (datex) SG-Tools/SDE SG-Tools/dataexp SG-Tools/SDEIngImport SG-Tools/SDESybImport SG-Tools/SDEOraImport SG-Tools/dtxscript.tpl datex.
SS/CsIHEpiPIf.o Event Log Application (event) SG-Support/CsExtProcess/EventLog SpectroGRAPH Support (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.
SG-Support/CsGib/Ds3App1407/CsDs3Curr.GTb 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 SS/SM-GEXT.e SS/CsEGP1AppMI.o SS/CsEGP2AppMI.o SS/CsICMPAppMI.o SS/CsIP1AppMI.o SS/CsSNMP1AgMI.o SS/CsSNMP2AgMI.o SS/CsTCP1AppMI.o SS/CsTCP2AppMI.o SS/CsUDP1AppMI.o SS/CsUDP2AppMI.o SS/CsTRAppMI.o SS/CsEthAppMI.o SS/CsEtIfAppMI.
SG/CsRdAttInNW.o SG-Support/Enumerations/iftype.txt SS/V3COREMM-CSI.e SS/CsColFddiMI.o SS/CsIHIfStat.o SS/CsIHColFddi.o SS/CsIHSyncRd.o Generic Routing Support (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.30 SG-Support/CsPCause/Prob00220006 SS/SMGRTR-CSI.e SS/CsIHDLnkTrp.
SS/CsIHChasCtl.o SS/CsIHChasSup.o SS/CsPortGroup.o Global Classes API (globl) SDK/lib/libGlobl.a Global Classess API (WIN32 / globl32 ) SDK/lib/lib/Globl.a Core Icon Objects (icon) SG/CsIAniMult.o SG/CsIAck.o SG/CsIDiag.o IcmpPif (Windows_NT only) SS/CsICMPServ.o Inference Handler API (ihapi) SDK/lib/libIHapi.a Extensions Integration Toolkit (insdk) INSDK/Install.tar INSDK/mkarea MAC Address Locator Tool (malt) SG-Tools/MALT SG-Tools/SSMALT Map View (mapv) SG/CsPLLServer.
Install-Tools/host_eval Install-Tools/host_eval.dat Install-Tools/locserv.cus Install-Tools/phaselist Install-Tools/processd.cus Install-Tools/release.dat Install-Tools/patch/tools/patch_inst Install-Tools/patch/tools/patch_prep Install-Tools/setup.ksh Install-Tools/MMD/Install.mmd SDPM/new/processd SDPM/new/.autostartrc LS/LocServer Portability Library (PortLib) SDK/lib/libPort.a Portability Library (WIN32 / PortLib32) WIN32SDK/lib/libPort.
SANMTK/lib/libGlobl.a SANMTK/lib/libPort.a SANMTK/lib/sanmtk.a Alarm Notification Manager (sanm) SANM/PolicyAdmin SANM/associate SANM/xcron AlarmNotifier (Notifier) Notifier/AlarmNotifier Notifier/AlarmAck Notifier/AlarmClear SNMP Device (SMSNP-CSI) SS/SMSNP-CSI.e SS/CsSV1Ident.o SS/CsSnmpV1PIf.o SpectroGRAPH (SG-Core) SG/SG.o SG/libUIapi.a SG/libVPapi.a SG/libGlobl.a SG/libPort.a SG-Tools/stdmenu/salt_stdmenu SG-Tools/SALT ndlib/salt.
SS/core.e SS/libEPI.a SS/libIHapi.a SS/libVPapi.a SS/libGlobl.a SS/libPort.a Remote Object Encapsulation (ssroe_core) SG-Tools/reconfig SG-Tools/hierarchy SG-Tools/reconfig.txt SG-Tools/hierarchy.txt SG-Support/CsResource/language/ssroe.default Event/Alarm Configuration Editor (steae) SG-Support/CsExtProcess/ECEditor SG-Support/CsResource/language/steae.default User Interface Common Objects (uiapi) SG/libUIapi.
SDK/include/VPAPI/CsEventTypes.h SDK/include/VPAPI/CsRelDef.h SDK/include/VPAPI/CsRHLst.h SDK/lib/libVPapi.a VnmParmBlock API (WIN32 / vpapi) WIN32SDK/include/VPAPI/CsActionCode.h WIN32SDK/include/VPAPI/CsAlarmCause.h WIN32SDK/include/VPAPI/CsAttrValDef.h WIN32SDK/include/VPAPI/CsEventTypes.h WIN32SDK/include/VPAPI/CsRelDef.h WIN32SDK/include/VPAPI/CsRHLst.h WIN32SDK/lib/libVPapi.a SpectroWATCH UI (watch) SG-Tools/WatchManager SG-Tools/WatchEditor SpectroWATCH IH (watch-ih) SS/SwLoopDetct.o SS/SwIHControl.
SS/CsIvnmops.o SS/SwYacc.o Files Shipped With CS2 6-12 Software Release Notice for 5.
