Specifications
Table Of Contents
- Titlepage
- Notice
- Contents
- Preface
- Overview
- Product Description
- New Features in SPECTRUM 6.0
- AutoDiscovery
- Sub-Interface Support
- Monitor/Manage ATM Circuits Through SPECTRUM
- NuTCRACKER No Longer Required for SPECTRUM on Windows NT
- Serial Interface Reconfiguration Improvements
- Enumerated Value Text Support
- OSPF Protocol Support
- New Cabletron-Ethernet-Parameters MIB Support
- Increased Model Capacity
- Performance Increased on Database Tools
- Reduce Unnecessary Gen_IF_Ports Link-Down Traps
- EtherMap Moved To New Enumerated Attribute
- User Interface Help
- VLAN Fault Isolation
- Throttling
- Top 10 CPU and Memory Users
- Toolbar Added to SpectroGRAPH
- Bookmarks Menu Added To the Menubar
- “Options” Menu in SpectroGRAPH Changed to “Tools”
- “Show Toolbar Labels” Menu Item Added
- Preference System for Many Applications Have Been Enhanced
- Right Mouse Edit Menu PopUp Using While Editing
- “Grab and Scroll” Function
- Lost Server Connection Disables Buttons
- Views Now Contain a "Save All Changes" Toolbar Icon
- Icon Subviews Menu Items For Which The User Does Not Have Access Permissions Grayed Out
- Tools Menu In GRAPH Contain SpectroSERVER Tools
- Applications Have Disconnection Dialog
- Easier To Select Multiple Items
- SPECTRUM Launchable Applications Improvements
- Remove User Preference File While Clearing Preferences
- Create Event/Alarm When Interface's IP Changes
- User Model Security Strings Now Updated During Runtime
- Foreign Operating Systems
- Language Translation: Foreign Character Support
- Search Manager
- Java MibTools for SPECTRUM
- Filtering By Event Message Is Now Allowed
- Creation of Duplicate Alarms Now Allowed
- Event Log
- Defining 24 hour range for Data Exports
- Host List Editing
- Location Server Configuration
- Detection Of Other Archive Manager/SpectroSERVER Processes
- Run A Post Online Backup User-defined Script
- FrameRelay / DLCI Alarms Enhancements
- Converter
- New Utility On Windows NT To Uninstall NutCracker
- Command Line Interface (CLI)
- SpectroWATCH
- Report Column Headers Are Now More Flexible
- Run A Report On Entire Database For Given Range
- Report Values Greater Than 3 Decimal Places
- Desktop Integration
- Enterprise Alarm Manager (EAM)
- Alarm/Event Usability
- Persistent Alarms
- Filter Dialog Enhancements
- User-defined Columns
- New View For Alarm Management
- Primary/Secondary Alarms Clarified
- Topological Location Button
- Event Counter Added
- New Trouble Ticket Id Information In Alarm Manager
- Alarm Manager-Usability Improvement For Single
- Alarm Manager-New Column Indicates "stale" Alarms
- Upgrade Warning
- SPECTRUM Environment Resources
- System Requirements
- Sun SPARCstation/Solaris 7 and 8
- Microsoft Windows NT (OS 4.0 and 2000)
- Minimum Windows NT and Solaris Configurations
- Corrected and Known Anomalies
- Alarm Notification Manager (SANM)
- Enterprise Alarm Manager
- AR System Gateway
- Annotation Toolbox
- Archive Manager
- AutoDiscovery
- Command Line Interface (CLI)
- Client View
- Control Panel (CPanel)
- Converter
- Data Export
- Distributed Data Manager (DDM)
- Event Configuration Editor (ECE)
- Event Configuration Manager (ECM)
- Network Configuration Utilities (NCU)
- SPECTRUM Installation Program
- MAC Address Locator Tool (MALT)
- MIBTools
- Search Manager
- SpectroRX
- SPECTRUM Online Backup
- Online Documentation
- RingView for Token Ring
- SPECTRUM Reports
- SPECTRUM Security
- SpectroGRAPH (UI)
- SpectroSERVER (VNM)
- SpectroWATCH
- User Editor
- Model Conversion
- Index
Corrected and Known Anomalies
Converter
Software Release Notes Page 80
Converter
Known Converter Anomalies in SPECTRUM 6.0
Problem 1: If you migrate a SPECTRUM 4.0 Rev 3 UNIX database to
version 6.0 on a Windows NT workstation and then attempt to change the
landscape handle using the Converter, the conversion may fail.
Solution: Before attempting to change the landscape handle using the
Converter on an Windows NT database that was migrated from UNIX,
please call SPECTRUM Technical Support or contact your Field Support
Representative.
Problem 2: After a migration and database conversion, you see Converter
error messages that say:
Converter has not been found: <model type>
Solution: You may safely ignore these messages. These messages occur
because certain model types that have been obsoleted leave behind
remnants of the models. The Converter attempts to process those
remnants and when it does not find all the pieces of information it
generates the messages. The remnants are permanently removed from the
database whenever a SSdbsave database restoration is performed.