SPECTRUM Software Release Notes (6.0.
Summary of Changes Summary of Changes SPECTRUM Software Release Notes Version Date Reason for Change 9030743-07 March, 2001 Update to Added Features and Functionality Description of Change Instructions on converting the Empire Application.
Notice Aprisma Management Technologies, Inc. (Aprisma) 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 Aprisma 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. Aprisma Management Technologies, Inc., 121 Technology Way, Durham, New Hampshire 03824. 2. (a) This computer software is submitted with restricted rights.
Contents Overview 12 Purpose of this Document ......................................................................................... 12 How This Manual Is Organized ................................................................................. 13 Version Control ......................................................................................................... 14 System Requirements 15 The SPECTRUM Online Sizing Tool .....................................................................
Contents Contents Installing SPECTRUM on Windows NT .................................................................... 36 BMC Patrol Integration .............................................................................................. 37 Corrected and Known Anomalies 38 Alarm Notification Manager (SANM) 39 Considerations .......................................................................................................... 39 Scheduler Requirements for Windows NT ............................
Contents Control Panel (CPanel) Contents 62 Known CPanel Anomalies in SPECTRUM 6.0.2 ....................................................... 62 Data Export 63 Corrected Data Export Anomalies in SPECTRUM 6.0.2 ........................................... 63 Known Data Export Anomalies in SPECTRUM 6.0.2 ............................................... 64 Event Configuration Editor(ECE) 67 Known ECE Anomalies in SPECTRUM 6.0.2 ...........................................................
Contents Search Manager (SM) Contents 83 Known SM Anomalies in SPECTRUM 6.0.2 ............................................................. 83 SpectroRX 85 SpectroRX Conversion Instructors ............................................................................ 85 Corrected SpectroRX Anomalies in SPECTRUM 6.0.2 ............................................ 87 Known SpectroRX Anomalies in SPECTRUM 6.0.2 .................................................
Contents Contents Corrected Anomalies in Level I Developer’s Toolkit ................................................113 Known Anomalies in Level I Developer’s Toolkit .....................................................113 MTE ......................................................................................................................113 Level II Developer’s Toolkit 114 Product Description .................................................................................................
Contents Contents EMME/EMM-E6 ................................................................................................... 147 Empire Agent ....................................................................................................... 148 Ethernet Hubs ...................................................................................................... 149 Extreme Devices ................................................................................................. 150 F5 Networks ....
Contents Contents Wellfleet Routers ................................................................................................. 195 SPMA (SPECTRUM Portable Management Applications) ..................................
Overview These SPECTRUM Software Release Notes (SSRN) accompanies each copy of the release package for version 6.0.2 of SPECTRUM. Purpose of this Document The SSRN is intended to accomplish the following: • • • • • alert the user to product enhancements or changes system and platform requirements corrected and known anomalies identify any updates or corrections to related documentation any other information useful for this release.
Overview How This Manual Is Organized How This Manual Is Organized The following outlines the organization of the SPECTRUM Software Release Notes for SPECTRUM 6.0.2. Section Description Overview The contents and purpose of the SSRN. System and Platform Requirements Describes operating system, hard disk, RAM, swap space and RAID requirements. New Features and Functionalities Describes the new features, supported versions, release advisories.
Overview Version Control Version Control SPECTRUM’s numbering scheme for version control consists of up to four numeric fields as well as an alphabetic descriptor as shown in the following diagram. 06.00.02.000 Major Release Minor Release Revision Patch Major Release - Increments to the number in this field represent major changes in the product’s design, functionality, or user interface. Major releases are planned well in advance and occur no more frequently than once per year.
System Requirements The following subsections list the hardware and software required for the basic SPECTRUM Network Management package on each of the supported platforms. SPECTRUM may be configured with more than one SpectroGRAPH. Suggested Minimum and Recommended RAM, Disk Space and Processor requirements are presented under Minimum Windows NT and Solaris Configurations section. Amounts shown are in both megabytes and gigabytes.
System Requirements 4 SPECTRUM requires 24-bit color or a workstation with a graphics card or controller that supports 24-bit color. The SPECTRUM Online Sizing Tool The SPECTRUM Online Sizer determines the number of SpectroSERVERS your enterprise needs to efficiently manage your distributed network. This is an especially useful tool if you are adding SPECTRUM to your enterprise for the first time or if you are creating a distributed SpectroSERVER environment for the first time.
System Requirements Determining RAM and Disk Space Requirements Aprisma proposes RAM and Disk Space Requirements for each of the platforms included in these Software Release Notes as being the minimum requirements. However, your enterprise environment may require more RAM and disk space that exceeds the minimum requirements.
System Requirements Sun SPARCstation/Solaris 7 and 8 Sun SPARCstation/Solaris 7 and 8 SPECTRUM supports the Solaris 7 and 8 operating systems running on at least an UltraSPARC I at 167MHz. SPECTRUM will install and run on Solaris 7 with CDE 1.3. SPECTRUM will install and run on Solaris 8 with CDE 1.4. SPECTRUM is compiled with C++ version 5.0 to run on Solaris 7 and Solaris 8, plus C++ patch.
System Requirements 4 Under CDE’s Color Style Manager, be sure to choose “More Colors for Applications” in order to permit SPECTRUM to display in all its colors. Note: Note: SPECTRUM links the X libraries (libX11, libXt, and libXm) dynamically. On most systems, soft links from /usr/lib to the appropriate directories are created as defaults.
System Requirements Note: Note: When installing on Solaris the user will need to include the following paths in their PATH variable: /usr/bin /usr/openwin/bin /usr/ccs/bin For C-Shell: setenv PATH /usr/bin:/usr/openwin/bin:/usr/ccs/bin: ${PATH} For K-Shell: export PATH =/usr/bin:/usr/openwin/bin:/usr/ccs/bin: $PATH For Bourne Shell: PATH=/usr/bin:/usr/openwin/bin:/usr/ccs/bin: $PATH export PATH SPECTRUM Software Release Notes Page 20
System Requirements Solaris 7 Patches Note: Note: Aprisma recommends the following patches from Sun Microsystems in order to run SPECTRUM efficiently. These patches are subject to change as Sun Microsystems adds new patches or makes changes to existing patches. The patches for Solaris 7 listed in this note are available from Sun Microsystems. Solaris 7 Patches 106144-20 SunOS 5.7: Elite3D AFB Graphics Patch 106145-17 SunOS 5.7: Creator 7 FFB Graphics Patch 106146-14 SunOS 5.
System Requirements Solaris 8 Patches Note: Note: Aprisma recommends the following patches from Sun Microsystems in order to run SPECTRUM efficiently. These patches are subject to change as Sun Microsystems adds new patches or makes changes to existing patches. The patches for Solaris 8 listed in this note are available from Sun Microsystems.
System Requirements Configuring a 24-bit Color Card Note: Note: A 24-bit color card is required for SPECTRUM. This allows more colors to be displayed. To allow your Sun workstation to display more colors with the windowing manager, be certain your 24-bit color card has been configured to do so. If you purchase a 24-bit color card, be certain to follow all installation instructions in the manual that comes with the card. You must first determine if your workstation has a 24-bit frame buffer.
System Requirements - As root, create an empty file named S99m64setup in the /etc/rc2.
System Requirements If a 24-bit color card is already installed but your workstation is not in 24-bit color mode, complete the following configuration instructions: 1 Become root 2 Create your own, user-defined config directory by typing at the command line: mkdir -p /etc/dt/config 3 Navigate to the new config directory by typing: cd /etc/dt/config 4 Create a file and name it Xservers by typing: vi Xservers 5 Enter the following one line string in the new Xservers file: Local local_uid@console roo
System Requirements Microsoft Windows NT (OS 4.0 and 2000) Microsoft Windows NT (OS 4.0 and 2000) SPECTRUM supports Microsoft’s Windows NT 4.0 and Windows 2000 on Intel-based systems with 500 MHz (or faster) Pentium III CPUs. To run SPECTRUM on a Windows NT 4.0 system, you must have Service Pack SP5 or Service Pack SP6a installed. SPECTRUM is compiled with Visual C++ version 6.0 with Service Pack 3. Service Packs are not required to run SPECTRUM on systems running Windows 2000.
System Requirements Note: Note: Note: Note: To ensure that SPECTRUM successfully installs, be sure Virtual Memory has been set appropriately. For a full explanation on Virtual Memory settings and procedure, refer to the SPECTRUM Installation Guide. The installation process creates a local user group called “SPECTRUM Users.” This group has Full Control permissions to the SPECTRUM directory tree.
System Requirements Minimum Windows NT and Solaris Configurations Note: Note: Note: Note: Tip: If you experience problems with window elements appearing incorrectly such as inverted or partially displayed text, make sure you are using the latest drivers for your video card. To successfully run a shell script from the Scheduler on Windows NT, the command must precede the name of the script. For example, to run a bash script named, “test.ksh”, you need to type, “bash test.ksh” (no quotes).
System Requirements would normally be considered a healthy maximum (~80%) thus underutilizing the workstation’s potential. Similarly, high-speed disk I/O is required to handle these loads. Due to the excessive memory utilization of Java processes on Solaris, more RAM is required to run SpectroGRAPH and its applications on Solaris. Therefore, all memory requirements associated with a SpectroGRAPH presented below includes this factor.
System Requirements Disk Platform SpectroServer Only SpectroGRAPH Only SpectroSERVER and SpectroGRAPH Windows NT 3 x 4.0 gig * 1 x 4.0 gig 3 x 4.0 gig * Solaris 3 x 4.0 gig ** 1 x 4.0 gig 3 x 4.
System Requirements Disk Platform SpectroServer Only SpectroGRAPH Only SpectroSERVER and SpectroGRAPH Windows NT 3 x 4.0 gig * 1 x 4.0 gig 3 x 4.0 gig * Solaris 3 x 4.0 gig ** 1 x 4.0 gig 3 x 4.
System Requirements Disk Requirements (Disk Striping) For optimum performance, Aprisma recommends running SPECTRUM on systems with multiple ultra-wide SCSI or EIDE drives using RAID disk striping technologies. SPECTRUM requires high-performance disk I/O optimized for small random writes. Please contact your hardware vendor for an appropriate RAID solution.
System Requirements 1 mv DDM to a temporary directory (DDM_TMP) 2 create an empty DDM directory in SS (mkdir DDM) 3 mount the new disk to $SPECROOT/SS/DDM 4 cp DDM_TMP/*DDM (remember to also get .configrc) WINDOWS NT (ONLY) Currently, it is not possible to separate the DDM from the rest of the SPECTRUM installation on Windows NT. Therefore, the required configuration is to install SPECTRUM (with DDM) on its own 3-disk stripe set which is separate from the disk holding the operating system.
New Features in SPECTRUM 6.0.2 This section lists the new features and functionalities plus other release advisories in SPECTRUM 6.0.2 SPECTRUM Web Operator Foundation (WOF) 2.5 The SPECTRUM Web Operator Foundation (WOF) is now available on the SPECTRUM 6.0.2 product CD. Included on the CD are the following two files related to WOF: Install.html and ReadMe.html. Please refer to these files on installation instructions and known anomalies. Improved Model Management Version 2.
New Features in SPECTRUM 6.0.2 BMC PEM Integration BMC PEM Integration BMC Patrol Enterprise Manager (PEM) Integration allows system administrators to analyze SPECTRUM alarms from a centralized console. This is accomplished through a PEM filter pathway setup to specifically receive alerts.
Release Advisories and Special Considerations This section provides any late-breaking information, or information that is mandatory or useful for the successful operation of SPECTRUM. Multiple SpectroGRAPHS on a Single Workstation SPECTRUM does not support running two or multiple SpectroGRAPHS on the same display from a single SpectroSERVER. SpectroGRAPH Connection to Older SpectroSERVERS SPECTRUM does not support new connections of SpectroGRAPH 6.0.0 clients to a SPECTRUM 5.0rev1 SpectroSERVER.
Release Advisories and Special Considerations BMC Patrol Integration BMC Patrol Integration Note: Note: Version 2.3.00 of Patrol Integration for SPECTRUM (the version which integrates SPECTRUM 6.0.1 and BMC’s Patrol 2000) may be delayed due to BMC’s Quality Assurance testing and BMC’s Beta Cycle.
Corrected and Known Anomalies This section lists the known irregularities or anomalies that have been corrected since the previous revision of SPECTRUM and current known anomalies. Corrected and known anomalies are listed under the particular core, application, management module or toolkit component with which the anomaly is associated.Miscellaneous issues may also be included.
Alarm Notification Manager (SANM) SPECTRUM Alarm Notification Manager (SANM) enhances the functionality of SANM-compatible, SPECTRUM-client applications that respond in various ways (email notifications, trouble tickets, etc.) to alarms generated by SPECTRUM. SANM’s Policy Administrator, an alarm filter configuration tool, enables you to specify and associate alarm notification policies with applications.
Alarm Notification Manager (SANM) Corrected SANM Anomalies in SPECTRUM 6.0.2 not specify the System Account — it cannot access the network.) Then make sure the user or user group assigned to the Schedule Service is also defined as a SPECTRUM user in SpectroGRAPH. If you find that the Scheduler is not performing SANM tasks as scheduled, check the NT Schedule Service Startup parameters. Even when these Schedule Service parameters are incorrect, you can schedule associations.
Alarm Notification Manager (SANM) Corrected SANM Anomalies in SPECTRUM 6.0.2 with the value f would correctly display in the Event View and Alarm View, but not in AlarmNotifier. This problem has been corrected. sanm566 5 Previously, when using SANM to filter alarm information from AlarmNotifier, multiple SETs and CLEARs for the same device(s) and alarm ID(s) could be seen in log files following communications interruptions, such as can occur during online backups, for example.
Alarm Notification Manager (SANM) Known SANM Anomalies in SPECTRUM 6.0.2 Known SANM Anomalies in SPECTRUM 6.0.2 Problem 1: When you run SANM-enabled AlarmNotifier on the Solaris platform with the option -ts set less than the number of models you are filtering (e.g.: if you have 1000 models, you should not set the option -ts to be 500), the swap space will eventually be used up causing SpectroSERVER to segmentation fault.
Alarm Notification Manager (SANM) Known SANM Anomalies in SPECTRUM 6.0.2 Problem 5: If you change a SANM policy association while AlarmNotifier is running, and the value for GET_EXISTING_ALARMS in the .alarmrc resource file is TRUE, then the states of all previously existing alarms are displayed as NEW, rather than EXISTING. Solution: To ensure that previously existing alarms are displayed as EXISTING, restart AlarmNotifier after the SANM policy association change takes place.
Enterprise Alarm Manager Alarm Manager and Enterprise Alarm Manager provide the user with a dynamic view of SpectroSERVER alarms. If your network is modeled using a distributed SpectroSERVER, you may have several landscape icons in SpectroGRAPH, each representing its own SpectroSERVER. You can opt to view all or some of these landscapes in EAM. Known Alarm Manager Anomalies in SPECTRUM 6.0.
Enterprise Alarm Manager Known Alarm Manager Anomalies in SPECTRUM 6.0.2 navigator menu off the alarm model, then select Device -> Chassis, you receive the message: SpectroSERVER Error: Cannot recover, must return to previous view. Solution: Return to the previous view. This does not have any adverse affects and seems to occur on the Olicom Wire Speed Bridge program Model type GNSNMPDev. This problem will be corrected in the next major release of SPECTRUM.
Enterprise Alarm Manager Known Alarm Manager Anomalies in SPECTRUM 6.0.2 Problem 7: Currently, alarm IDs may not be unique during a single runtime session of SpectroSERVER. One possible outcome could be when you attempt to clear one alarm, a different alarm is cleared instead. Solution: The chance that this problem will occur is very low. This problem will be corrected in a future release of SPECTRUM.
Enterprise Alarm Manager Known Alarm Manager Anomalies in SPECTRUM 6.0.2 Problem 11: The Enterprise Alarm Manager view resizes itself after you maximize the window, open the View menu, and select Show Toolbar. It will also resize itself after you open the View menu, and choose Show Filter/Search Panel. Solution: This problem will be corrected in a future release of SPECTRUM.
Enterprise Alarm Manager Known Alarm Manager Anomalies in SPECTRUM 6.0.2 Enter keys while entering a text string in the Alarm Status field, the data reflected in the Alarm Status field in the AlarmNotifier will be truncated or include garbage characters. In addition, the values for fields following Alarm Status in the AlarmNotifier will also contain garbage characters. This is a problem if you are using AlarmNotifier in conjunction with EAM.
AR System Gateway The AR System Gateway provides you with many tools for managing network problems. The timely resolution of problems and service requests is one of the fundamental requirements of a network management system. The AR System Gateway provides the tools to efficiently detect, track, and resolve these network problems and service requests.
AR System Gateway Considerations • While using the SPECTRUM Trouble Ticket Form, the active links (SimilarTickets and SpectrumView) may fail. This will happen if the AR System Gateway installation directory paths are different on the Remedy server and the Remedy client machines. This is because active links are executed on the client machine and the form on the server machine is using the AR System Gateway installation path on the server machine.
AR System Gateway Network Configuration Requirements This solution will not work on the NT platform, since there is no signalling in Windows NT. • If contact with the AR System Server is interrupted, an error is sent to the UNIX syslog file or the Windows NT Event Viewer. Any trouble tickets generated by the SPECTRUM AR System Gateway between the time contact is interrupted and then reestablished are lost. • Beginning with 6.0, the gateway will be started by processd.
AR System Gateway Order of Installation for Components Note: Note: If you are not interested in automatic trouble ticket generation and you want to use the AR System Gateway just to submit trouble tickets manually, you need to install only one AR System Gateway for one SpectroSERVER. When you use the SpectroGRAPH that is on the node with AR System Gateway, you can still submit trouble tickets for alarms from any landscape modeled on that node’s SpectroGRAPH.
AR System Gateway AR and AR System Gateway Compatibility are in the /usr/ar directory on UNIX systems (or in the c:\Program Files\Remedy folder on NT systems). These are the default locations set up by the AR System Gateway installation.
AR System Gateway Corrected ARS Gateway Anomalies in SPECTRUM 6.0.2 Corrected ARS Gateway Anomalies in SPECTRUM 6.0.2 1 After installing SPECTRUM on Windows NT, when you open the Remedy ->Admin Tool and you select Forms to import a definition, you can now import SpectrumForm.
AR System Gateway Known ARS Gateway Anomalies in SPECTRUM 6.0.2 Problem 2: When you run SANM-enabled AR System Gateway on the Solaris platform with the -ts option set less than the number of models you are filtering (e.g.: if you have 1000 models, you should not set the option -ts to be 500), the swap space will eventually be used up causing a SpectroSERVER segmentation fault.
AR System Gateway Known ARS Gateway Anomalies in SPECTRUM 6.0.2 Solution: Select Show Trouble Tickets from the SPECTRUM Alarm Manager to verify that trouble tickets are submitted. This will be corrected in a future release of SPECTRUM AR System Gateway.
Annotation Toolbox The Annotation Toolbox, allows you to edit SPECTRUM views by adding lines, circles, boxes, and text. The toolbox provides several graphic tools to enhance a view’s background by adding extra graphics or text. Known Toolbox Anomalies in SPECTRUM 6.0.
AutoDiscovery AutoDiscovery is SPECTRUM’s automatic topology mapping facility. AutoDiscovery offers three Discovery Methods: • IP List maps a discovered device's IP address to a physical (MAC) address.When this method is used, AutoDiscovery will attempt to contact and identify only those devices at the IP addresses you specify when you create the configuration. • Range uses ICMP echo requests (pings) to test each of the IP addresses within the range or ranges you specify in the IP Address Ranges panel.
AutoDiscovery Known AutoDiscovery Anomalies in SPECTRUM 6.0.2 Known AutoDiscovery Anomalies in SPECTRUM 6.0.2 Problem 1: AutoDiscovery may fail to discover a Token Ring the first time AutoDiscovery is run. It may find one ring while failing to find another ring. Solution: Run Ring Discovery, and the missing ring will be found. Problem 2: On Windows NT, if you search for IP an ATT1000 model, it is found as a pingable. If you destroy the device and model it by IP, it is discovered as an ATT_SmartHub.
BMC PEM Integration BMC Patrol Enterprise Manager (PEM) Integration allows system administrators to analyze SPECTRUM alarms from a centralized console. This is accomplished through a PEM filter pathway setup to specifically receive alerts. Known BMC PEM Integration Anomalies in SPECTRUM 6.0.2 Problem 1: When .pempiperc is run without the PEM_FILTER_NAME resource having a value or with an invalid value, no error messages are generated. Solution: Before running .
Command Line Interface (CLI) The Command Line Interface (CLI) provides access to the SpectroSERVER in situations where it is not possible or not desirable to use the SpectroGRAPH graphical user interface. One such situation is the use of a character-based terminal to remotely access the SpectroSERVER. Corrected CLI Anomalies in SPECTRUM 6.0.2 1 The syntax, create event -a as documented in the Command Line Interface User’s Guide now works correctly . Known CLI Anomalies in SPECTRUM 6.0.
Control Panel (CPanel) The SPECTRUM Control Panel is a convenient Point and Click interface that provides facilities that let you configure SPECTRUM resources, start and stop SpectroSERVER, start SpectroGRAPH, perform database administration and maintain your SPECTRUM installation. Known CPanel Anomalies in SPECTRUM 6.0.
Data Export Data Export extracts archived events and statistics data from SPECTRUM DDM (Distributed Data Manager) databases and current data for object entities stored in VNM databases. Data Export converts extracted data to the output format that you specify — either ASCII, SAS, or SQL. Data Export connects to a single SpectroSERVER in a distributed server environment and can extract data from any of the landscapes registered with that SpectroSERVER.
Data Export Known Data Export Anomalies in SPECTRUM 6.0.2 3 On the Windows NT platform, filter operations no longer produce inconsistent results. 4 Data from SAS exports now reports the time from different time zones correctly. 5 The Clear All Entries and Reset To Defaults options on the Edit menu now clear and reset all values for underlaying layers of events or statistics. 6 On the Windows NT platform, you can now schedule more than one definition file to run at a time.
Data Export Known Data Export Anomalies in SPECTRUM 6.0.2 Windows NT as the client the export completes but you are unable to view the table even though the table exists in the database. Since the Oracle server is on UNIX and the client is on NT, this becomes a heterogeneous environment when a homogenous environment is needed.
Data Export Known Data Export Anomalies in SPECTRUM 6.0.2 the SDE_OUTPUT_MODEL_LEN variable in the dtxscript) and the ensuing export contains models with names longer than the previous default, the export will likely fail with an Oracle error indicating that the insert value was too large for the column. Solution: Manually drop the existing table and then perform the export. This will establish the column width to the value specified in the dtxscript.
Event Configuration Editor(ECE) The Event Configuration Editor ECEditor) allows creation, deletion, modification, and browsing of the following information in SPECTRUM: Alert Map, Event Disposition, Event Format, and Alarm Probable Cause files. Known ECE Anomalies in SPECTRUM 6.0.2 Problem 1: Not all vendor event files that are shipped with SPECTRUM are read/writable.
Enterprise Configuration Manager (ECM) Enterprise Configuration Manager (ECM) is an application that enables customers to monitor, document, troubleshoot, and control the configuration of network devices. New Features • Runtime selection of models or model types. You no longer have to exit and restart ECM to work with different models or model types. • Selective writing to RAM or NVRAM on Cisco routers. You now can selectively copy the host configuration of Cisco routers to RAM, or commit it to NVRAM.
Enterprise Configuration Manager (ECM) Special Requirements for NT Users Host Configuration strings are now easily editable by using Cut/Copy/Paste operations along with the Find/Find Again tool. • Global editing of Host Configuration Mask strings. Mask strings can now be appended globally to selected configurations. • Latest configuration updates can now be overwritten.
Enterprise Configuration Manager (ECM) Special Requirements for NT Users Tip: When Microsoft Internet Explorer 5.0 is installed on your PC, the Windows NT 4.0 Schedule Service (Atsvc.exe) is upgraded to the Task Scheduler Service (mstask.exe), which enables you to assign different user accounts to run scheduled tasks. See About the SPECTRUM Control Panel for more information about configuring the Task Scheduler Service for scheduled SPECTRUM tasks.
Enterprise Configuration Manager (ECM) Special Requirements for NT Users Considerations You should be aware of the following considerations when using ECM: • ECM cannot successfully capture a device’s attributes unless the community string matches the community string in the SNMPmanaged device itself. Likewise, ECM cannot successfully load external attributes to a device unless the community string matches the community string that has write permission in the SNMP-managed device itself.
Enterprise Configuration Manager (ECM) Considerations for Running ECM from the Command Line Considerations for Running ECM from the Command Line Solaris Platform Only • Before you can run ECM manually from the command line, you must define the XUSERFILESEARCHPATH variable.
Enterprise Configuration Manager (ECM) Known ECM Anomalies in SPECTRUM 6.0.2 Known ECM Anomalies in SPECTRUM 6.0.2 Problem 1: The ECM cannot use External List-typed Attributes that have OID References within configurations. If you create or capture a configuration in ECM you receive the error message, “No instance exists.” for any External List-type Attributes that have an OID Reference.
Enterprise Configuration Manager (ECM) Known ECM Anomalies in SPECTRUM 6.0.2 Problem 5: Sometimes the keyboard focus is lost. For example, you may not be able to edit the value of a configuration in the Configurations window. Solution: Move the mouse outside of the window and then bring it back into the window. Problem 6: The X window manager may perform unpredictably when you select attributes from devices that display duplicate attributes.
Enterprise Configuration Manager (ECM) Known Scheduler Anomalies on the Solaris Platform Solution: If you have problems reading or writing to certain attributes, use the SPECTRUM MIB tools to see if the status is specified as “Deprecated.” If so, omit the attribute from the configuration or template. Problem 10: Background Host Configuration operations fail for Cisco Catalyst devices regardless of whether or not they are performed against the corresponding CatStack application.
EventLog The Event Log is a fault isolation tool that allows network administrators access to the historically archived database of all events associated with a single landscape. Event Log provides the following features: • Viewing of archived events by a user defined range, or by the most current range of events across a single landscape. • Three tier sorting of events. Sort fields include: model name, model type name, event code, user name, date and time, and event message.
Network Configuration Utilities (NCU) Network Configuration Utilities is a set of applications, accessible from SPECTRUM Search Manager, that enables you to perform the following device management tasks for Cabletron devices that are modeled in SPECTRUM: • Configure and execute TFTP firmware image downloads using the Firmware Download Tool. • Modify community strings using the Modify Community Strings Tool. Corrected NCU Anomalies in SPECTRUM 6.0.
Network Configuration Utilities (NCU) Known NCU Anomalies in SPECTRUM 6.0.2 Solution: Make certain that the SPECTRUM model community name matches any one of the valid community names on the device. Telnet to the device and change the community strings via local management. You can also change the SPECTRUM community string in the information GIB using the GIB Editor. See the GIB Editor User’s Guide for more information. This will be corrected in a future release of SPECTRUM. Problem 2: Offline downloads (*.
SPECTRUM Installation Program Information on installing SPECTRUM on Solaris, Windows NT and 2000, system requirements, RAM, and hard disk requirements plus any other information needed for a successful install of SPECTRUM may be found earlier in this documentation. Known Installation Anomalies in SPECTRUM 6.0.2 Problem 1: During an installation on a Windows NT workstation, you may receive the message, Ò! The Security log file is full.Ó Solution: You may safely ignore this message.
SPECTRUM Installation Program Known Installation Anomalies in SPECTRUM 6.0.2 Problem 3: When you run host_eval on Windows NT with a foreign operating system, you receive a message warning that you have a missing operating system patch and to contact your system administrator to correct the problem. This warning appears when host_eval fails to detect either Service Pack 5 or 6. Solution: Service Packs 5 or 6a are required to run SPECTRUM.
SPECTRUM Installation Program Known Installation Anomalies in SPECTRUM 6.0.2 ** Error during Creation of DDM database save file The ddm_save program fails to save a database which never had data archived to it. Users normally do not migrate empty databases. Solution: (1) If migration of the current DDM landscape handle is not possible, instead of initializing the DDM database prior to the migration installation, simply delete the whole DDM directory.
JMibTools JMibTools is a suite of applications that lets you access and manage any SNMPcompliant — device through its Management Information Bases (MIBs). A MIB is a database maintained by the device that stores all its known management information. Each individual element of information in the MIB is termed an Object. Known MIBTools Anomalies in SPECTRUM 6.0.2 Problem 1: When you try to run more than one session of MIBTools on the same workstation, you may receive a blank warning message.
Search Manager (SM) The Search Manager application allows you to search for specific models in the SPECTRUM database. You can either search for models using predefined criteria or create your own customized searches. Search Manager also provides access to attributes in the SPECTRUM database, allowing you to change attribute settings on individual models or globally for all models of a type. Known SM Anomalies in SPECTRUM 6.0.
Search Manager (SM) Known SM Anomalies in SPECTRUM 6.0.2 2../connect (to start the command line session) 3../show models | grep SwCat35xx (to display all the Cat 3500 models in the database. 4. Find the model handle of the Cat 3500 model in the left column of the list you wish to use. 5../update mh= attr-0x11a3d,val=2 This problem will be corrected in a future release of SPECTRUM.
SpectroRX SpectroRx uses a problem-solving technique called case-based reasoning to organize the knowledge about network problems. A case consists of the alarm resolution information that you enter and additional alarm information provided by SPECTRUM. As you enter information about new alarms, SpectroRx adds the case to its case library.
SpectroRX SpectroRX Conversion Instructors note that the quotation marks are provided simply to delimit the strings, and should not be considered part of the change): File To be Modified cbr.db, cbr_back.db. If the first line of this file starts with the word “begin” - delete the line. If the second line of this file starts with the string “cnum=0|”, change it to read “cnum=0\205” (note that the “\205” is the hex code for the ˆ character).
SpectroRX Corrected SpectroRX Anomalies in SPECTRUM 6.0.2 Delete any leading spaces on all lines. Verify that there are no duplicate lines in the file. Once you have done this, you will also have to update any backup copies of these files made by SpectroRx. The location of these files can be determined by checking the db_dir_backup variable (as documented in the “Customizing the Environment” section of the SpectroRx manual). Corrected SpectroRX Anomalies in SPECTRUM 6.0.
SpectroRX Known SpectroRX Anomalies in SPECTRUM 6.0.2 ÒUse of uninitialized value at line xxxÓ This problem concerns the use of the -w option when executing Perl (from within the cbr executable). These messages can be safely ignored. This will be corrected in a future release.
RingView for Token Ring RingView for Token Ring is a SPECTRUM application program that provides enhanced capabilities for modeling and displaying the ring of devices and connections that make up a Token Ring (802.5) LAN. An important feature of the RingView application is that it allows for several different ways of displaying a Token Ring LAN within a SPECTRUM Topology view.
SPECTRUM Reports SPECTRUM’s design is based on a client-server model where the SpectroSERVER (VNM) includes a database. This database provides storage for the specific device configurations and contains a modeling catalog (model types and relations) that is the structure for all your network information. By modeling devices in the database, SPECTRUM provides a wide range of information about network devices and network structure even when a device is powered-off or contact is lost.
SPECTRUM Reports Be aware of the following when you use SPECTRUM Reports: Note: Note: • Relational reports are no longer supported. • In the Report Formatter, if the expression exists within a report format that you want to modify, do not remove any attributes that are located in columns before the expression column. • If you are using top-n in the line data of a Statistical report, the summary portion, where the totals are displayed, is based on the entire report, not just the sorted data.
SPECTRUM Reports Corrected Reports Anomalies in SPECTRUM 6.0.2 2 The alarm number no longer is missing when you generate an event report in which two events of the same event type occur at the same time. In addition, none of the events will be missing when you filter on an alarm condition. 3 On the Windows NT platform, generating and scheduling .gif and .grf.ps output files now works correctly.
SPECTRUM Reports Known Reports Anomalies in SPECTRUM 6.0.2 15 When you run a report on a GnSNMPDev device, you now generate information. 16 SPECTRUM allowing reporting on secure models, even though user access to these models is denied in SpectroGRAPH is no longer a problem. 17 If a landscape in the preferred landscape list is shut down while you are in a Statistics or Events dialog box, a subsequent attempt to expand a model type no longer causes the user interface to freeze.
SPECTRUM Reports Known Reports Anomalies in SPECTRUM 6.0.2 Solution: Choose the Save As command and navigate to the appropriate model type directory to save your file. Problem 2: If a reports output directory specified in the Reports resource file does not exist and you try to bring up the Reports Display, you get a list of all files in the current directory. Solution: Make a backup copy of the Reports resource file.
SPECTRUM Reports Known Reports Anomalies in SPECTRUM 6.0.2 Problem 7: On the NT platform, colors on Alarm report pie graphs may not appear correctly or may be obscured. For example, pie pieces are colored over by other pie pieces when values are close to zero (0). Solution: This is not a problem with SPECTRUM Reports but rather a limitation of Neuron Data. Problem 8: The Rib Editor previewer goes blank after a few minutes.
SPECTRUM Reports Known Reports Anomalies in SPECTRUM 6.0.2 Problem 12: On Windows NT, when you print multiple pages, each page that gets printed has an NT print dialog displayed asking for the printer selection. Printing does take place, however, each page will have the Print dialog display asking for the printer to be selected. It occurs on Solaris if an invalid printer name is entered. Solution: This problem is under study and will be addressed in a future release of SPECTRUM.
SPECTRUM Reports Known Reports Anomalies in SPECTRUM 6.0.2 Solution: From the Specify Data window, choose OK instead of Cancel to exit without modification.
SpectroGRAPH (SG) (UI) SpectroGRAPH provides the graphical user interface that you will use to monitor your network and launch other client applications. SpectroGRAPH’s views contain a variety of icons that represent the different elements of your network, including devices, users, and “conceptual” elements such as LAN segments. Each icon presents status information and provides access to management facilities specific to the network element it represents.
SpectroGRAPH (SG) (UI) Known SpectroGRAPH Anomalies in SPECTRUM 6.0.2 Known SpectroGRAPH Anomalies in SPECTRUM 6.0.2 Problem 1: In the Stack Link View on the Windows NT platform, the pipe connecting the two model is split horizontally with black on top and green on the bottom. Solution: This is a visual problem only derived from a bug in Neuron Data’s toolkit (ND Defect #11069). This problem will be corrected in a future release of SPECTRUM.
SpectroGRAPH (SG) (UI) Known SpectroGRAPH Anomalies in SPECTRUM 6.0.2 grayscale images. This problem has been a known limitation of the Neuron Data toolkit on Windows NT. Problem 5: On the Windows NT platform, when you print a .GRF report on a Hewlett-Packard series 5 printer, the X and Y axis as well as part of the heading are missing. However, on screen they display correctly. Solution: This is a Neuron Data problem (Neuron Data bug problem ID #8843).
SpectroGRAPH (SG) (UI) Known SpectroGRAPH Anomalies in SPECTRUM 6.0.2 Problem 9: On Windows NT 4.0 Server with Service Pack 6a, when you double click a SPECTRUM .prf file, the operating system mistakenly launches Microsoft’s Content Advisor for Internet Explorer 5.0. There is a Registry entry under HKEY_CLASSES_ROOT that identifies .prf files as “PICSRules Files” (also a .prf) which conflicts with SPECTRUM’s .prf files. To edit a SPECTRUM .prf file, open it with a text editor. Selecting and opening the .
SpectroGRAPH (SG) (UI) Known SpectroGRAPH Anomalies in SPECTRUM 6.0.2 Problem 12: The multi-attribute line graph on a device’s Performance view does not represent accurate 10 minute blocks of time in the X-Axis labels when you scroll back in time for data. Solution: The documentation explaining how this graph displays and interprets data will be clarified. This problem will be corrected in a future release of SPECTRUM.
SpectroSERVER (VNM) SPECTRUM’s design is based on a client/server model. The server, SpectroSERVER (or VNM – Virtual Network Machine), includes the SPECTRUM database and provides security, modeling capabilities, and device management facilities. SpectroSERVER supports a suite of client applications through its Application Program Interface (SSAPI). The first client application you will see when you start SPECTRUM is SpectroGRAPH.
SpectroSERVER (VNM) Known SpectroSERVER Anomalies in SPECTRUM 6.0.2 Attribute that is a duplicate of the Attribute you intend to log, but not make it List-type. Then use this duplicate in place of the original Attribute. This problem will be corrected in a future release of SPECTRUM.
SpectroSERVER (VNM) Known SpectroSERVER Anomalies in SPECTRUM 6.0.2 Problem 6: When you attempt to stop the MySQL service on Windows 2000 the service will not stop. This problem is due to a bug in the current version of MySQL server. Solution: A fix is in progress and will be made available as soon as it is developed. As a workaround perform the following: 1. In a bash or DOS shell, navigate to the MySQL binary directory in $SPECROOT/SS/DDM/mysql/bin. 2.
SpectroSERVER (VNM) Known SpectroSERVER Anomalies in SPECTRUM 6.0.2 Solution: Avoid stopping processd without first stopping the SpectroSERVER. This is known problem with third party software from Visigenics and is not SPECTRUM problem. Visigenics has been apprised of the issue (their case #455220) and are examining the problem.
SpectroWATCH The Watch Manager and Watch Editor applications provide you with a mechanism for easily adding thresholds and logging historical data without having to program new modules or modify standard Generic Information Block (GIB) views. These applications allow selected elements to be monitored at a higher level of detail while providing data to be used with other tools used in network analysis.
SpectroWATCH Known SpectroWATCH Anomalies in SPECTRUM 6.0.2 Problem 3: When you create a watch, give it an attribute, and you do not set or change it to the appropriate Data Type (defaults to Boolean), after you create a Threshold violation that requires Integer as the Data Type, when you click OK to finally create the watch you receive an error message that indicates “Incompatible types.
User Editor The User Editor allows you to manage network security and simplify management of your network by providing you with the option of managing users as individuals or as groups of related users (User Groups). The User Editor lets you create, modify, delete, copy, find, move, and perform domain maintenance for User Groups and Users. Corrected User Editor Anomalies in SPECTRUM 6.0.
Level I Developer’s Toolkit The SPECTRUM Level I Developer’s Tools are designed to allow OEM developers to integrate their products into SPECTRUM, and to allow developers at customer sites to customize SPECTRUM to suit the site’s specific needs. Product Description Packaged as optionally-purchasable modules, the following Level I Developer’s Tools are available: • SPECTRUM Model Type Editor (MTE) - The primary tool used to create and modify SPECTRUM model types.
Level I Developer’s Toolkit Extensions Categories extension. The toolkit includes tools and information for integrating a customer-developed extension with the SPECTRUM CD formats and the SPECTRUM installation script. CDs created using the SEI Toolkit utilities will be installed at a customer’s site. Tools are also provided to export models from the SPECTRUM database, icons from SpectroGRAPH, and protocols from SPECTRUM.
Level I Developer’s Toolkit Corrected Level I Developer’s Toolkit Anomalies Also, simple views can be created by modifying a GIB information block. These extensions can be accomplished using the Basic Extensions Toolkit, and the GIB Editor. Extensions developed using the Level I or Level II Developer’s Tools can be packaged to distribution media for resale, and installed at a customer site using the standard SPECTRUM installation process.
Level I Developer’s Toolkit Corrected Anomalies in Level I Developer’s Toolkit Corrected Anomalies in Level I Developer’s Toolkit 1 In the GIB Editor, after changing an attribute value within a SPECTRUM view, clicking the keyboard’s Return button or clicking the Cancel button now will save or change the value. Known Anomalies in Level I Developer’s Toolkit MTE Problem 1: Attributes of an unsupported type must be created manually.
Level II Developer’s Toolkit This section provides a description of the SPECTRUM Level II Developer’s Tools for 6.0 rev1. This section also identifies operational constraints that pertain to the last major release, and any corrected and known anomalies. Product Description The SPECTRUM Level II Developer’s Tools provide C/C++ programming interfaces for developing advanced extensions to SPECTRUM.
Level II Developer’s Toolkit Product Description • SPECTRUM Virtual Network Machine Parameter Block API (VPAPI) - This toolkit includes the VnmParmBlock C++ Class Libraries, which are essential to the development of C++ objects and programs that integrate with SpectroSERVER. The VnmParmBlock classes are used to define objects that allow access to specific SPECTRUM model types, attributes, aspects, and processes. VPAPI is used with the Inference Handler API, View API, and SpectroSERVER APIs.
Level II Developer’s Toolkit Product Description • Global Classes - The Global C++ class library is used to create and manipulate buffers for the Inference Handler API, the View API, and SpectroSERVER API. Refer to the SPECTRUM Global Classes Reference for more information. With the SPECTRUM Level II Developer’s Tools, you can create advanced extensions by integrating new objects and programs into the SPECTRUM knowledge-base.
Level II Developer’s Toolkit Major Level II Toolkit Changes for 6.0 • Implementation of a gateway between SPECTRUM and another network management system using the Asynchronous SpectroSERVER API. A gateway allows the sharing of alarm information between network management systems and allows centralized management of a network whose subcomponents are managed by different network management systems.
Level II Developer’s Toolkit Known Level II Developer’s Toolkit Anomalies referencing system headers). For more information, review the readme file in the following SPECTRUM directory: /SDK/README CORBA CORBA is similar to the Level II toolkits (SS API, VP API, IH API, and the communications library). CORBA provides server infrastructure including connection management, security, and location services. The SPECTRUM CORBA API is used to write applications.
Level II Developer’s Toolkit Known Level II Developer’s Toolkit Anomalies SSAPI Problem 1: AsyncDemo on NT fails, and default landscape messages display. Solution: This problem will be fixed in a future release.
Management Module Software Management Module Software accompanies the release package for SPECTRUM version 6.0.2. This section of the SPECTRUM Software Release Notes is intended to alert you to product enhancements or changes, problem resolutions, and anomalies associated with SPECTRUM Management Modules. Updates to SPECTRUM Management Modules are issued and packaged with each release of SPECTRUM.
New Modules and Functionality This section identifies management modules that have been added since the last release as well as new functionality that has been added to existing modules. The information within each section listed below is organized numerically by management module number. • New Management Modules • Added Features, Changes and Functionality (Page 123) New Management Modules The following management modules have been added since the last release of SPECTRUM (revision 6.0).
New Modules and Functionality New Management Modules SM-CIS1013, Cisco Service Level Agreement Manager This management module allows users to acess services and features of the Cisco Service Level Agreement Manager (SLAM) through Cisco Extensible Markup Language interfaces. SM-CPQ1000, Host Compaq This management module provides device management support for Compaq devices that support Compaq Insight Manager.
New Modules and Functionality Added Features, Changes and Functionality services between telco central office or cable/wireless head-ends and service provider routers. SM-SFA1000, Scientific Atlanta Explorer HCT This management module supports the power TV operating system run by the Scientific Atlanta set top boxes and provides statistics about service and performance in a subscription area.
New Modules and Functionality Added Features, Changes and Functionality longer launched via the Utilities > Applications menu option from the SNMP2_Agent application. The Logical Device view has been removed for the ELS and FNET devices. SmartSwitch 6000 This management module has been enhanced to provide support for an intelligent chassis container model type. This container can be used to organize modules contained within the SmartSwitch 6000 chassis.
New Modules and Functionality Added Features, Changes and Functionality SM-KEN1001, Kentrox This management module was enhanced to include additional MIB support and traps. SM-LUC1001, Definity Switch DNM Integration This management module was updated to include DNM integration. SM-CSI1091, SSR Upgrades Enhancements to this management module included added support for the VRRP MIB and modifications to the Environmental and Chassis views.
Corrected & Current Anomalies This section identifies the anomalies that have been corrected since the last release and the anomalies that are known to exist in the current release. This information is presented alphabetically by device manufacturer name.
Corrected & Current Anomalies Multiple Management Modules Problem 1: The following devices and/or model types (and possibly more) are not clearing a link down alarm with a link up trap.
Corrected & Current Anomalies 3Com FMS/MSH SPECTRUM Part Name Device SM-3CM1004 10BTi FMS SuperStack II MSH Hubs Firmware 1.32 2.02 4.01 MM Version 6.0 Rev 0 Known Anomalies: Problem 1: If you select the icon in the Alarm view of a Hub3ComMSH and then open the Applications view, a small primary application button appears in the view’s banner. Solution: This problem will be addressed in a future release.
Corrected & Current Anomalies 3Com LinkSwitch 1100/3300 SPECTRUM Part Name Devices SM-3CM1011 LS1100, LS3300 Firmware 1.06 MM Version 6.0 Rev 0 Known Anomalies: Problem 1: In the Hub3ComLS3300’s Model Information view, changing the Community Name to something other than Public results in the view’s Description field becoming red-boxed. Solution: This device is operating with a non-compliant SNMP agent, which appears to be a firmware problem.
Corrected & Current Anomalies 3Com NetBuilder II SPECTRUM Part Name Device Firmware SM-3CM1001 3Com N/A NetBuilder MM Version 6.0 Rev 0 Known Anomalies: Problem 1: In the 3Com NetBuilder II’s IP Security Control Table, the columns Control, Packet Default Auth, and Packet System Auth show a value of “|” (pipe). Solution: This problem will be fixed in a future release.
Corrected & Current Anomalies 3Com PortSwitch Family SPECTRUM Part Name Device Firmware SM-3CM1008 3Com N/A PortSwitch Family Hub MM Version 6.0 Rev 0 Known Anomalies: Problem 1: In the 3ComRmonExtApp application, the print buttons located in the Configuration view’s rfc1516 Extensions, Host, and Alarm Event tables cause SpectroGRAPH to crash. Solution: This problem will be addressed in a future release.
Corrected & Current Anomalies Adtran DSU/CSU SPECTRUM Part Name Device SM-ADT1000 DSU/CSU Firmware 3.31 MM Version 6.0.2 Known Anomalies: Problem 1: Devices DSU IQ, TSU IQ, TSU IQ+, and IQ Probe display red boxes in the DLCI Port Configuration view. Solution: This is a firmware related problem.
Corrected & Current Anomalies AT & T StarLAN10 SmartHUB SPECTRUM Part Name Device Firmware SM-ATT1000 SmartHUB 10.0 MM Version 6.0 Rev 0 Known Anomalies: Problem 1: The SNMP Agent Detail view, accessed from the Application or Performance views, shows pie charts with missing data breakdown fields. Solution: The AT& T StarLAN10 SmartHUB does not fully support MIB I. Some views will not show any information.
Corrected & Current Anomalies Bay Centillion 100 SPECTRUM Part Name Device Firmware Version SM-BAN1001 Bay Centillion 100 2.2.4 MM Version 6.0 Rev 0 Known Anomalies: Problem 1: Interface icons in the Device Interface and Device Topology views display port and board labels with an incorrect value of “0.” Solution: This is a firmware problem.
Corrected & Current Anomalies BayStack Ethernet Hubs Part Number SM-BAY1000 Device HubBaySt10x/20x Firmware MM Version 6.0.2 Known Anomalies: Problem 1: Modeling by IP gives different results than AutoDiscovery. Modeling by IP results in a HubBayStxx/xxx model icon in the Topology view that has incorrect labeling and Icon Subviews menu options. AutoDiscovery correctly results in the creation of a BSEnetRptr model icon.
Corrected & Current Anomalies Cayman GatorStar Repeater/Router SPECTRUM Part Name Device MM Version Firmware SM-CAY1001 RtrCayGBox 3.0.3/2.2.0 RtrCayGMIM 3.0.3/2.2.0 RtrCayGStar 3.0.3/2.2.0 6.
Corrected & Current Anomalies Cisco Catalyst SPECTRUM Part Name Device Firmware MM Version SM-CAT1000 SwCat 1200 (Catalyst Workgroup Switch) 4.1, 4.21 6.0 Rev 0 6.0.2 SM-CAT1001 HubCat 1400 (Catalyst Workgroup Concentrator) 1.5 6.0 Rev 0 SM-CAT1002 HubCat 5xxx (Catalyst 5xxx) 2.1 6.0 Rev 0 Known Anomalies: Problem 1: The HubCat5000 and HubCat5500 Interface Translation table shows only Interface Index 1. Solution: This is a firmware problem; the management module functions as designed.
Corrected & Current Anomalies Problem 4: For SwCat1200 models, double-clicking any interface’s IF Status label displays the Interface Status view with a red-boxed Port Oper Status field. Solution: For switches with firmware versions not supporting the trunking status attribute, Port Oper Status will be red-boxed. Problem 5: In the Device Topology view of the SwCat5505, reconfigured (swapped) boards appear in incorrect numeric order. Solution: The port information is correct.
Corrected & Current Anomalies Cisco Access Server SPECTRUM Part Number SM-CIS1004 Device AS5x00 (Cisco Access Server) Firmware Version MM Version Experimental 6.0 Rev 0 Version 12.0 Known Anomalies: Problem 1: The AS5x00 T1 port interfaces 4 and 5 show red-boxed attributes in the Interface Configuration view. Interfaces 1-3 and 6-51 show correct values. Solution: This is a firmware problem with the Experimental Version 12.
Corrected & Current Anomalies Cisco Router SPECTRUM Part Name SM-CIS1001 Device Rtr_Cisco (Cisco Router 2) Firmware Version 11.1(8) MM Version 6.0 Rev 0 Rtr_CiscoIGS, 11.2 CGS, AGS, MGS, 2500, 3000, 4000, 7000 SM-CIS1002 Lightstream 10.10 (ATM Support) 11.2(5)/ wa3(2b) 6.0 Rev 0 Known Anomalies: Problem 1: The Cisco 3T MIM is not recognized in hub or MMAC chassis views. Solution: This is a Cisco 3T MIM firmware problem.
Corrected & Current Anomalies management module. Problem 4: Clicking the Ciscoview menu choice, or the CiscoView button in the Cisco Router MM, does not work. Solution: For the Ciscoview functionality, the user must first install the Ciscoview product. Additionally, the path to the executable must be located in the user path. If these two conditions are not met, the Ciscoview cannot be accessed. Problem 5: When the Cisco router is modeled with a Rtr_Cisco model type, some application models do not appear.
Corrected & Current Anomalies Cisco Works Integration Known Anomalies: Problem 1: For any Cisco and Cisco Catalyst models, if Ciscoworks is not correctly installed in your path, then the CiscoView selection on the Cisco model Icon Subviews menu will not work correctly and the following error message will appear: Stop Process Daemon:nmcview -host - No Such File or directory. (This affects Cisco model icons that appear in core application views if Ciscoworks is not installed).
Corrected & Current Anomalies Copper Mountain Networks Part Number Devices SM-CPM1000 CopperEdge 150/200 DSL Concentrators Firmware Version 2.20.61 MM Version 6.0.2 Corrected Anomalies: 1 The Device icon in the Model Events view now contains a device label, and all menu options are available.
Corrected & Current Anomalies CSX200/400 SPECTRUM Part Name Device SM-CSI1077 CSX200/400 SM-CSI1077 CSX5500, CSX7000 Firmware Version 1.03.13 2.01.10 MM Version 6.0 Rev 0 Known Anomalies: Problem 1: The fr1315App’s Frame Relay Data Link Connection Management table for the CSX200 and CSX400 may incorrectly show the State value as “6.” If you double-click on State, the Data Link Connection Management table view shows “???” for the State value. Solution: This is a firmware problem.
Corrected & Current Anomalies DBconv Tool ($SPECROOT/SS-Tools) Corrected Anomalies: 1 When running the DBconv tool to convert a GnSNMPDev to another model type, the device no longer disappears from the Location or OrgChart view and is no longer placed the Lost and Found after the conversion.
Corrected & Current Anomalies ELS100-24TXG SPECTRUM Part Name SM-CSI1064 Device Firmware Version ELS100-24TXG 2.01.07 MM Version 6.0 Rev 0 Known Anomalies: Problem 1: The Port Information view for the ELS100_TxG incorrectly displays the Port Speed for ports 25 and 26 as “3.” Solution: This is a firmware problem that was corrected with firmware version 2.02.01.
Corrected & Current Anomalies EMME/EMM-E6 SPECTRUM Part Name Device Firmware Version MM Version SM-CSI1004 EMME/EMME - 3.08.01 Routing 1.01.02 6.0 Rev 0 SM-CSI1004 EMM-E6 EMM-E6 ADV 6.0 Rev 0 3.22.01 4.01.
Corrected & Current Anomalies Empire Agent SPECTRUM Part Name SM-EMP1000 Device Firmware Version Empire Agent MM Version 6.0.2 Known Anomalies: Problem 1: The Empire_NT, Empire_Ext, and Empire_Unix applications contain views (configuration and/or performance) that show red boxes. Solution: This will be fixed in a future release.
Corrected & Current Anomalies Ethernet Hubs SPECTRUM Part Name Device Firmware Revision MM Version SM-CSI1000 IRBM, IRM-2, 1.07.02 IRM-3 6.0 Rev 0 SM-CSI1000 IRM-3 BP 2.00.01 6.0 Rev 0 SM-CSI1000 MINI-MMAC 2.03.04 6.0 Rev 0 SM-CSI1000 MRXI 22/24 1.11.09 6.0 Rev 0 SM-CSI1000 MRXI-2E 2.03.02 6.0 Rev 0 SM-CSI1000 MRXI-93 SNMP IRM 2.03.02 6.0 Rev 0 Known Anomalies: Problem 1: In the IRBM’s Device Topology view, the Edit menu’s New Model option does not list LAN802.3 or LAN802.
Corrected & Current Anomalies Extreme Devices Part Number SM-EXT1000 Devices Extreme Summit switches and BlackDiamond 6808 Core Switch Firmware Version MM Version For Summit: 6.0.2 ExtremeWare 2.1.7 For BlackDiamond: ExtremeWare 3.09b4 and Version 5.0 for policy management Corrected Anomalies: 1 In the DevTop > Interface view, the slot number and port number information is no longer incorrect.
Corrected & Current Anomalies F5 Networks Part Number SM-F5N1000 Device F5 BigIp Load Balancer family Firmware Version 3.1.1 MM Version 6.0.2 Corrected Anomalies: 1 Several views accessed from the BigIpApp icon no longer have the Description field red boxed. Known Anomalies: Problem 1: The Interface Configuration view displays fields that are red boxed. Solution: This is a firmware related problem.
Corrected & Current Anomalies FDM SPECTRUM Part Name Device SM-CSI1012 FDMMIM FDMMIM-04 Firmware Version 4.07.06 MM Version 6.0 Rev 0 Known Anomalies: Problem 1: There are no statistical reports being generated for the BdgCSIFDM icon. Solution: Run the reports on the applications for the HubCSIFDDI icon to review the statistical information; the statistical reports function as designed.
Corrected & Current Anomalies ForeRunner Series of ATM Switches SPECTRUM Part Name Firmware Version Device SM-FOR1000 ASX-100 ASX-200 9A000 ASX-1000 ASX-4000 5.3.1 MM Version 6.0 Rev 0 Known Anomalies: Problem 1: Some fields for ASX and OC3 models are red-boxed in the Application Port view (accessed from the Application Configuration view’s Port Table). Solution: The management module functions as designed. This is a firmware problem.
Corrected & Current Anomalies Problem 5: A yellow alarm occurs if multiple ForeWorkstations are modeled in SPECTRUM. The alarms only appear on ForeWorkstation models using an older (previous) version of the Fore adaptor card. Solution: Install FORE’s ATM adapter card software, the Solaris_5.0.0.5_28757.tar version or later.
Corrected & Current Anomalies Foundry Network Devices SPECTRUM Part Name SM-FDR1000 Device Firmware ServerIron, NetIron, 07.0.10T53 BigIron, FastIron, TurboIron MM Version 6.0.2 Known Anomalies: Problem 1: Red boxes appear in several fields in the Chassis General Information view. Solution: This is a firmware problem that will be fixed in a future version of SPECTRUM.
Corrected & Current Anomalies Generic SNMP Devices SPECTRUM Part Name SM-CSI1017 Device Firmware Version Generic SNMP N/A MM Version 6.0 Rev 0 Known Anomalies: Problem 1: When some devices are modeled as GnSNMPDev, the Topology view may show the GnSNMPDev models with incorrect name labels. Solution: Generally, this label on the GnSNMPDev model type denotes the name of the manufacturer that initially wrote the firmware. The management module functions as designed.
Corrected & Current Anomalies Host Compaq Module SPECTRUM Part Name Device SM-GHO1007 Host Compaq MM Version 6.0 Rev 0 Known Anomalies: Problem 1: The SNMP Agent Detail View is not showing statistical information. Also, the view’s Auth Trap field and the Detail 2 view’s Receive Breakdown and Transmit fields are red-boxed. Changing the Auth Traps from disabled to enabled causes an attribute error message to appear. Solution: This is a firmware problem.
Corrected & Current Anomalies Host HP SPECTRUM Part Name Device SM-GHO1003 HP_Host MM Version 6.0 Rev 0 Known Anomalies: Problem 1: For HP_Host, the MIB-II Detail 1 view’s Auth Traps button shows “???” instead of enabled or disabled. The device is not reading the proper value (enabled or disabled) from the MIB. Solution: This is a firmware problem.
Corrected & Current Anomalies Host NT Module SPECTRUM Part Name Device MM Version SM-GHO1004 Windows NT (pc) 6.0 Rev 0 Known Anomalies: Problem 1: For the IP2_App application of Host_NT models, the IP Routing view does not display all appropriate fields. Solution: The table is seeing a premature “end of table” being sent from the device. The table then continues to process errors. This is a firmware problem; the management module functions as designed.
Corrected & Current Anomalies Host Sun Part Number SM-GHO1001 Device Firmware Sun platforms MM Version 6.0.2 Known Anomalies: Problem 1: On some Sun platforms, modeling results in a GenSNMPDev model, which has no connectivity associated with it. Solution: This is a firmware related issue.
Corrected & Current Anomalies Juniper Networks Part Number SM-JPR1000 Device Firmware M20, M40, M160 JUNOS 4.0R1.2 Internet Backbone Routers MM Version 6.0.2 Known Anomalies: Problem 1: Juniper Internet JUNOS may send OSPF traps SNMP Version 1 with a non-standard specific trap number. Traps will be sent with a specific trap number of 9-24, which should be 1-16. As a result, SPECTRUM will show these traps as UNKNOWN to the Juniper Model or will display the wrong Event/Alarm.
Corrected & Current Anomalies Kentrox DataSMART SPECTRUM Part Name Device Firmware SM-KEN1001 Kentrox 1.43 DataSMART_680, DataSMART_688 MM Version 6.0 Rev 0 Known Anomalies: Problem 1: Several views for the Kentrox DataSMARTApp contain redboxed attributes. Solution: This problem occurs because the device is not returning any values for these attributes. The management module functions as designed; this is a firmware problem.
Corrected & Current Anomalies Motorola Vanguard SPECTRUM Part Name Device SM-MOT1000 6520, 6560, 320 Firmware Version MM Version 6.0.2 Known Anomalies: Problem 1: The Bridge Traffic view displays blank fields. Solution: This a firmware issue.
Corrected & Current Anomalies Nokia Firewall Part Number SM-NOK1000 Devices Nokia Firewall family Firmware Version 3.2.1 MM Version 6.01 Corrected Anomalies: 1 The Checkpoint App’s name no longer appears as “7” in the Application view when it is in the List mode.
Corrected & Current Anomalies Packeteer PacketShaper SPECTRUM Part Name SM-PKT1000 Device Packeteer Family Firmware Version 4.2.0 MM Version 6.0.2 Corrected Anomalies: 1 There are no longer red boxes around the Description field in the Partition table accessed from the PSCommonApp Performance view. The ninth variable in the AlertMap file no longer contains a typographical error (that is, 1.3.6.1.4.1.2334.2.1.8.1.8.9 (8,0) instead of 1.3.6.1.4.1.2334.2.1.8.1.8.9 (9,0).
Corrected & Current Anomalies Paradyne FrameSaver SPECTRUM Part Name SM-PRD1000 Device FrameSaver Firmware Version MM Version 6.0.2 Known Anomalies: Problem 1: The Alarm Relay Cutoff field in the Configuration view accessed from the PdnCommonApp Icon Subviews menu may be red boxed. Solution: This a firmware issue. The attribute value may not be present in the MIB. Use the SPECTRUM MIB Tool to see if it is.
Corrected & Current Anomalies RMON Application Known Anomalies: Problem 1: A search for RMONApp, RMONEthProbe, or RMONTRProbe results in icons with inconsistent menu picks as compared to the Topology menu picks. Solution: This will not be changed. Problem 2: There may be problems with window displays associated with RMON statistics errors. Multiple windows may appear and/or error messages may occur. Solution: This is an issue related to the firmware and MIB.
Corrected & Current Anomalies RMON Management Module SPECTRUM Part Name SM-CSI1014 Device Remote Monitoring Firmware Version N/A MM Version 6.0 Rev 0 Known Anomalies: Problem 1: After launching the RMON Suite from the command line of a Cisco Frontier Switch Probe modeled as GnSNMPDev, MAC addresses in the Host Matrix table appear incorrectly.
Corrected & Current Anomalies SEHI Hubs SPECTRUM Part Name SM-CSI1020 Device Firmware Version SEHI 1.10.04 (Stackable Hubs) SEHI-22 SEHI-24 SEHI-32 SEHI-34 MM Version 6.0 Rev 0 Known Anomalies: Problem 1: When you highlight a port in the Device view and choose Port Frame Size & Protocols from the Icon Subviews menu, the view that displays has Frame Size information only. Solution: Port protocols are not supported by the SEHI device and will, therefore, not show up in the view.
Corrected & Current Anomalies SFSmartCell Switch (9A656-04, 9A686-04) SPECTRUM Part Name SM-CSI1073 Devices SmartSwitch 9A656_04 SmartSwitch 9A686_04 Firmware MM Version Version 2.04.09 6.0 Rev 0 Known Anomalies: Problem 1: The SFCS device’s Interface Configuration Table view’s Clocking to Mother Board field is empty, and the same field in the SFCS Interface Configuration view is red boxed for devices using the 02.02.03 firmware. Solution: This is a firmware related issue.
Corrected & Current Anomalies SmartSwitch 2000 Family SPECTRUM Part Name Devices Firmware Version MM Version SM-CSI1068 2Exx-xx 4.09.08 6.0 Rev 0 SM-CSI1080 2H2x-xxx 2H3x-xxx 4.09.08 6.0 Rev 0 SM-CSI1087 2M46-04R 2M46-04RDC 4.09.08 6.
Corrected & Current Anomalies SmartSwitch 6000 Chassis SPECTRUM Part Name Devices Firmware Version MM Version SM-CSI1088 6C105 6C110 4.01.10 6.0 Rev 0 Known Anomalies: Problem 1: Duplicate models will cause erroneous yellow alarm conditions to appear in the 6C105 chassis. The duplicates are overwriting existing models; models are being shifted from correct slot positions and the duplicates are being incorrectly placed into empty chassis slots.
Corrected & Current Anomalies SmartSwitch 6000 Family SPECTRUM Part Name Devices Firmware Version MM Version SM-CSI1076 6E122-26, 6E128-26, 6E133-25, 6E138-25, 6E123-26, 6E123-50, 6E129-26, 6E132-25 6E133-37, 6E133-49, 6E139-25 6E233-49 4.01.10 6.0 Rev 0 SM-CSI1082 6H122-08, 6H122-16, 6H123-50, 6H128-08, 6H129-08, 6H133-37 6H202-24, 6H252-17 4.01.10 1.01.10 1.01.10 6.0 Rev 0 SM-CSI1088 6M146-04 4.01.10 6.
Corrected & Current Anomalies SmartSwitch 9000 Dual Backplane SPECTRUM Part Name Devices SM-CSI1098 9C114 9C106 Firmware Version MM Version 6.0 Rev 0 Known Anomalies: Problem 1: Duplicate models will cause erroneous yellow alarm conditions to appear in any SmartSwitch 9000 chassis. The duplicates are overwriting existing models; models are being shifted from correct slot positions and the duplicates are being incorrectly placed into empty chassis slots.
Corrected & Current Anomalies SmartSwitch 9000/9500 SPECTRUM Part Name Devices Firmware Version MM Version SM-CSI1030 9E13x-xx 2.06.10 6.0 Rev 0 SM-CSI1031 9F116-01 2.00.06 6.0 Rev 0 SM-CSI1032 9F1xx-xx 2.00.10 6.0 Rev 0 1.12.05, 6.0 Rev 0 9F2xx-xx SM-CSI1035 9F4xx-xx 9F31x-xx 6.00.15 1.00.30 SM-CSI1036 9E3xx-xx 9E4xx-xx 1.12.05 6.0 Rev 0 SM-CSI1038 9T122-xx 1.08.07, 6.0 Rev 0 1.02.17 9T125-xx SM-CSI1055 9E106-06 2.10.06 6.0 Rev 0 SM-CSI1059 9A128-01 9A426-xx 2.10.17 5.00.08 6.
Corrected & Current Anomalies SPECTRUM Part Name Devices SM-CSI1098 9E5xx-xx 9G5xx-xx 9H5xx-xx Firmware Version MM Version 1.02.09 6.0 Rev 0 Common Anomalies - SmartSwitch 9000/9500 The following affect two or more management modules and the associated devices.
Corrected & Current Anomalies entries within the Static Bridging application’s Static Bridging Table. This only happens with some SmartSwitch 9000 modules; for example; the 9E133-36, 9E138-36, 9E423-24, and 9F310-02 SmartSwitch models display the following: Update failed for the following attributes: Attribute 0x1194c - Attribute doesnÕt exist on device,0x200000a Solution: In order for the Static Bridging Table to work correctly, a “MacAddr.receiveport” entry must be provided.
Corrected & Current Anomalies ILMI parameters must be set. (Use local management to do this.) The following summarizes the creation procedure using a Zeitnet device. The procedure will be similar for the other devices. 1 In a Virtual Channel Link view, set the link information (IF Index, VPI, and VCI). For example, 20101.0.160. 2 Save the link by pressing and then clicking the Create Link button. The VCL Row Status view displays.
Corrected & Current Anomalies information incorrectly. For example, the Log and Lin graphs may appear to show 100 % of capacity when the cell rate exceeds a certain value. Solution: This problem comes about because the graph is used to show both percentages and rates and has a limitation as to the total cell rate that can be depicted in the graph. Percentages obviously do not exceed 100 % and the rates on the other hand have a multiplier associated with them (noted by an asterisk next to the attribute).
Corrected & Current Anomalies SmartSwitch ATM - Zeitnet Switch (2500, 6500, 6A000, 9A100) SPECTRUM Part Name SM-CSI1085 Switches Firmware MM Version Version 2.04.09 SmartSwitch 2500 (standalone ATM; the former Zeitnet ZX-250) SmartSwitch 6A000 (ATM module) SmartSwitch 9A100 (ATM module) SmartSwitch 6500 (ATM backbone) 6.0 Rev 0 Known Anomalies: Problem 1: In the Device Topology view for the ZX_250 model type, the Port Load Status field is blank. Solution: This is a firmware problem.
Corrected & Current Anomalies of Ports field as “7”, while the Port table displays eight rows of port data. Solution: This is a firmware problem. Problem 6: Modeled 6Exxx cards (with the ZX-250 SW_Link) do not provide Port Performance view statistics. The “Device not configured” error message appears instead, or the Performance view shows red-boxed attributes. Solution: This is a firmware problem. Upgrade to the SmartSwitch 6500 with 2.4 firmware, which provides the MIB-II performance parameters.
Corrected & Current Anomalies Interface view > IF Configuration view. An error message will be displayed. Solution: This is a firmware related problem. Problem 12: The 6A000 model may display “Failure” or no values in some of the fields in the Gen_IF_Port Performance view. Solution: This is a firmware related problem.
Corrected & Current Anomalies SmartSwitch FDDI (9F310-02, 9F426-02, 9F426-03) SPECTRUM Part Name SM-CSI1035 Devices Firmware MM Version Version SmartSwitch 9F426_02 1.06.09 SmartSwitch 9F426_03 SmartSwitch 9F310_02 6.0 Rev 0 Known Anomalies: Problem 1: In the Interface Device view of a 9F426-02, three possible interfaces can appear. One is the INB interface and the others are FDDI interfaces. The FDDI interfaces can be Front Panel 1 and Front Panel 2, Front Panel 1 and FNB, or Front Panel 2 and FNB.
Corrected & Current Anomalies SmartSwitch Router (SSR) 250/2000/8000/8600 SPECTRUM Part Name Device SM-CSI1092 SSR2000 Firmware Version 3.0.0b.14 MM Version 6.0 Rev 0 SM-CSI1092 SSR8000/8600 3.1.0.0 3.1.C.5 6.0 Rev 0 SM-CSI1096 SSR-250 6.0 Rev 0 SM-ENT 6-SSRM 3.0.8 6.0.2 Known Anomalies: Problem 1: For Generic_SSR_FP models, the Interface Device view’s Console Interface (#3) shows “???” on the Interface Type label. Solution: This firmware problem will be addressed in a future release.
Corrected & Current Anomalies Solution: This problem will be fixed in future release of SPECTRUM. Problem 6: Fast Ethernet ports are not being created in the Application view. Only the RMONEthProbe on the Ethernet ports appear. Solution: RMON probes are not created for Gigabit Ethernet ports. Gigabit interface types are currently not supported by Rmon code and therefore are not modeled as RMONEthProbes. Problem 7: Red boxes appear in the Configuration and Performance views of rfc2338App.
Corrected & Current Anomalies SmartSwitch FDDI MicroLAN Switches SPECTRUM Part Name SM-CSI1095 Device STS16 Token Ring (formerly Olicom TR16) Firmware Version 3.1.0 MM Version 6.0 Rev 0 Known Anomalies: Problem 1: When you have improper firmware, AutoDiscovery does not place the concentrator boards in the container view of the 9F12x-xx or 9F241-12. When you model the 9F12x-xx or 9F241-12 by IP address from the Device Topology view, that model is being placed correctly.
Corrected & Current Anomalies SynOptics 5000 Hubs SPECTRUM Part Name Device Firmware Version MM Version SM-SYN1003 53xx Enet 55xx TR 59xx FDDI 1.5.1 1.5.1 2.2.6 6.0 Rev 0 SM-SYN1007 SynOptics D5xxx 1.5.0 6.0 Rev 0 Corrected Anomalies: 1 In the Configuration view for the HubSyn5xxx model, Chassis Contact and Chassis Location MIB objects are read-write on the device and the device can now be set with SNMP.The SM-SYN1003 management module now supports the 5005 chassis.
Corrected & Current Anomalies Problem 2: Opening certain SPECTRUM views may cause link error messages to appear in the SpectroGRAPH window. These messages will not affect the operation of SPECTRUM. Solution: This problem will be addressed in a future release. Problem 3: Traps are only generated against the IP address of the first Data Collection Engine (DCE) on an Ethernet or Token Ring Network Management Module (NMM). If contact is lost with the first DCE, the user will not receive traps.
Corrected & Current Anomalies Problem 8: The HubSyn5DNxx does not appear in the Topology view when modeled by IP. Solution: Exit the Edit mode; the model will then appear in the Topology view. The recommended method is to model the HubSyn5DNxx using the “by Model Type” option. Problem 9: The Performance views accessed for the HubSyn5xxx may show red boxes. Solution: This may be fixed in a future release.
Corrected & Current Anomalies SynOptics Modules SPECTRUM Part Name Device Firmware Version MM Version SM-SYN1001 HubSyn3FDDI (SynOptics 3000) 5.1.0 6.0 Rev 0 SM-SYN1002 HubSynEnet28 5.3.1 xx(SynOptics 28xx) 6.0 Rev 0 SM-SYN1004 SynOptics 332xS (Enet Bridge) 6.0 Rev 0 SM-SYN1005 SynOptics 39xx 2.0.48 (FDDI) 6.0 Rev 0 SM-SYN1006 SynOptics 28xxx 2.0.3 6.0 Rev 0 SM-SYN1008 HubSyn27xx (SynOptics 27xx) 5.11 6.0 Rev 0 SM-SYN1009 HubSyn29xx (SynOptics 29xx) 2.2.4 6.0 Rev 0 1.0.
Corrected & Current Anomalies Solution: This problem will be addressed in a future release. Problem 2: The 3000 Series chassis has one Ethernet backplane, which can be broken into multiple segments so that more than one Network Management Module (NMM) can exist in the same chassis. HubSynSer3xxx Device views show all the Ethernet modules on the chassis instead of just the modules on the segment. Only the modules on the segment, however, have port information and configuration capability.
Corrected & Current Anomalies TRMM and TRMMIM Token Ring Modules SPECTRUM Part Name Device Firmware Version MM Version SM-CSI1023 TRMM 3.01.06 6.0 Rev 0 SM-CSI1025 TRMMIM TRMMIM-1 3.01.01 6.0 Rev 0 Known Anomalies: Problem 1: The TRMM does not recognize Router CRM-3T models; they appear as “unknown” in the TRMM’s Device Topology view and cannot be resolved. Solution: This is a firmware problem. The management module functions as designed.
Corrected & Current Anomalies TRMM-2 and TRMM-4 Token Ring Modules SPECTRUM Part Name Device Firmware MM Version SM-CSI1040 TRMM-2 2.00.03 6.0 Rev 0 SM-CSI1041 TRMM-4 2.00.03 6.0 Rev 0 Known Anomalies: Problem 1: If the HubCSITRMM2 is used as a monitor point for the 802.5 LAN, the SystemUpTime is 0, Ring Speed is 0, and no statistical data is calculated. Solution: A model representing the appropriate ring must be chosen; use the HubCSITR model as a monitor point.
Corrected & Current Anomalies Xylogics Terminal Server II SPECTRUM Part Name Device SM-XYL1001 Annex3 Annex3-UX Firmware MM Version 11.0 6.0 Rev 0 Known Anomalies: Problem 1: For Xyl_CSMIM and Xyl_AnnexII models of devices with firmware versions less than 9.0, the serial number fields in the Device and Application views remain empty. Solution: For versions 9.0 and greater, all views have been updated to support the serial number field.
Corrected & Current Anomalies Wellfleet Routers SPECTRUM Part Name Device Firmware MM Version SM-WEL1003 Rtr_Bay_Wflet 14.0 (Wellfleet Router 2) 6.0 Rev 0 5.77 6.0 Rev 0 SM-WEL1002 Rtr_Wfleet5xx (Wellfleet Series 5 Router) Known Anomalies: Problem 1: For Rtr_Wfleet models of devices with firmware 7.56 and 7.57, the Configuration view’s Console Configuration field is red-boxed. Solution: Firmware 7.80 replaces firmware 7.56 and 7.57; correct information displays with the newer firmware.
Corrected & Current Anomalies SPMA (SPECTRUM Portable Management Applications) Known Anomalies: Problem 1: Some of the SPMA applications create/use files to store userdefined information. These files are placed in the directory pointed to by the environment variable CTRONDB. By default, the script used to launch SPMA applications sets the CTRONDB variable to: {Install Directory}/SPMA/db directory The retrieved files are owned by the first person to use the SPMA applications.
Index Numerics B 10BTi MSH Hubs 128, 129 2E4x-xx 171 2H2x-xx 171 2M46-04R 171 3Com PortSwitch 130, 131, 132 53xx Enet 187 6E12x-xx 173 6H12x-xx 173 6M146-04 173 7CO3 SmartSwitch 170, 180, 183 9A128-01 180 9A656-04 170, 175 9A686-04 175 9E106-06 175 9E423-xx 175 9F12x-xx 175 9F310-02 183 9F426-02 175 9F426-02, 183 9F426-03 183 9M426-02 175 9T12x-xx 175 9T425-16 175 Banyan II File Server Agent 134 Basic Extensions Toolkit 110 BdgCSIFDM 152 A Annex3 194 API Asynchronous SpectroSERVER 116 ASX-100 153 ASX-20
Index Order of Installation for Components 52 AutoDiscovery 58 Corrected AutoDiscovery Anomalies 58 Known AutoDiscovery Anomalies 59 BMC PEM Integration Known BMC PEM Integration Anomalies 60 Command Line Interface (CLI) 61 Corrected CLI Anomalies 61 Known CLI Anomalies 61 Control Panel (CPanel) 62 Known CPanel Anomalies 62 Data Export 63 Corrected Data Export Anomalies 63 Known Data Export Anomalies 64 Enterprise Alarm Manager 44 Known Alarm Manager Anomalies 44 Enterprise Configuration Manager (ECM) 68 C
Index Known SpectroSERVER Anomalies 103 SpectroWATCH 107 Known SpectroWATCH Anomalies 107 SPECTRUM Installation Program 79 Known Installation Anomalies 79 SPECTRUM Reports 90 Corrected Reports Anomalies 91 Known Reports Anomalies 93 User Editor 109 Corrected User Editor Anomalies in SPECTRUM 6.0.
Index I IRBM 149 L Level I Developer's Tools ?? to 112 extensions categories 111 Level II Developer's Tools ?? to 117 Level II Developer’s Toolkit CORBA 118 Major Level II Toolkit Changes 117 Level II extensions, common types 116 Lightstream 140 M Major Release 14 Management Information Bases (MIBs) 82 Management Modules Added Management Module Features, Changes and Functionality 123 Empire Application 123 SM-APC1000 125 SmartSwitch 6000 124 SmartSwitch 9000 124 SM-CHT1000, Cheetah Gateway Integration 12
Index Microsoft’s End User License Agreement for NT Workstation 4.0 and 2000 27 Microsoft Windows NT (OS 4.0) 26 NT Server 4.
Index SM-ATT1000 133 SM-BAN1001 134, 144 SM-CAT1000 137 SM-CAT1001 137 SM-CAT1002 137 SM-CAY1001 136 SM-CIS1001 140 SM-CIS1002 139, 140 SM-CSI1000 149 SM-CSI1004 146, 147, 148 SM-CSI1012 152 SM-CSI1014 168 SM-CSI1017 156 SM-CSI1020 169 SM-CSI1023 192 SM-CSI1025 192 SM-CSI1030 175 SM-CSI1031 175 SM-CSI1032 175 SM-CSI1035 175 SM-CSI1036 175 SM-CSI1038 175 SM-CSI1040 193 SM-CSI1041 193 SM-CSI1055 175 SM-CSI1059 175 SM-CSI1062 170, 180, 183 SM-CSI1066 175 SM-CSI1068 171 SM-CSI1073 175 SM-CSI1074 175 SM-CSI1076
Index Swap Space 15 SwCat 1200 137 SynOptics 190 SynOptics 332xS 190 SynOptics 39xx 190 System Requirements Determining RAM and Disk Space Requirements 17 editing the file 17 Swap Space referred to Virtual Memory in Windows NT 15 The SPECTRUM Online Sizing Tool 16 Index X Xyl_AnnexII 194 T Topology view 89 TR NMM 188 trademarks 3 TRMM-2 193 TRMM-4 193 TRMMIM-1 192 V VNM – Virtual Network Machine 103 W Web Browser Recommendations 33 Wellfleet Router II 195 Wellfleet Series 5 195 Windows NT 157, 158, 15