Specifications

SPECTRUM Software Release Notice (SSRN)
For SPECTRUM 6.6 with Service Pack 2 CD release
Page 19
Document 5135
SPECTRUM Configuration Manager
• SPECTRUM Configuration Manager “save as” capabilities have been
enhanced to allow the current configuration to be written to a file with
the name devicename_config name.txt. This translates to easier
archival of configurations.
• The risk of a customer router staying in an infinite “wait” state and
SPECTRUM Configuration Manager hanging has been removed. By
leveraging a timer to give the device time to respond, reducing the
server load, and adding a counter for “wait” messages, the load will
automatically be stopped when necessary and the error “Router did not
initiate tftp transfer in time” will be presented to the user.
• The performance of SPECTRUM Configuration Manager has been
enhanced when displaying large amounts of data from Host Configs
comparisons.
Trap Handling
• For unmanaged and unmapped traps, the user will now have access to
all trap information. When a trap is received by SPECTRUM for which
there is no trap mapping or the element is not modeled in the
SPECTRUM object database, all varbind data will be captured and
presented to the user in a SPECTRUM event associated with the trap.
• Customers who add SNMP trap mappings through AlertMaps can use a
new global scope alert mapping by creating a new subdirectory in the
CsVendor area and placing an AlertMap file there. Previously, AlertMap
trap mapping entries were required for every model type that needed
to support the trap. Now only one “global scope” AlertMap entry is
required for a trap to be supported/mapped across all modeled devices.
These files will be preserved on upgrades.
• The trap mapping functionality is no longer available in the Event
Configuration Editor. However, it is still possible to map traps by
directly editing the appropriate AlertMap file. Instructions for doing this
can be found in the Event Configuration Files Guide (5070).