Specifications

SPECTRUM Software Release Notice (SSRN)
For SPECTRUM 6.6 with Service Pack 5 CD release
Page 40
Document 5156
Management Modules
Corrected Issues: Management Modules
Item Problem Resolution
1 ADC Cuda: The ADC_Cuda is a Chassis
based device. Each card in the Chassis
has its own CPU and thus its own
discreet
SystemUpTime. The system
was displaying the Chassis
SystemUpTime for the boards rather
than the correct board
SystemUpTime.
This was resolved by importing the mib
that supports
basSysUpTime into a
model type
adc_alias_mib that is
derived off of the ADC model type. This
was added to the base model type of
ADC_Cuda and the database to allow
customers to create the view(s) they
wish to implement using attributes from
the database.
2 Spectrum was not able to detect variable
varbinds associated with ADC Cuda
traps. Extra spaces in the Event files and
missing enumerations in the
EventTables were causing the
problems that were being seen.
This was resolved by adjusting the
formatting in the Event files and adding
entries for the new enumerations in the
EventTables.
3ATM Circuit Manager:
AlertMap file
name for
Nortel_PP/pp_3_slot had
a lower case “m” in
AlertMap rather
than an upper case “M”.
This was resolved by changing the “m” to
“M”.
4 Some ports were not displaying in the
DevTop view of the HubBaySt450 model.
This was resolved by adjusting the code
that determines duplicate board/port
associations on the HubBaySt450. This
prevents valid ports from being
eliminated and not displayed in the
DevTop view.
5 Cabletron: When a 2H252_25R with
SecureFast loaded was modeled, it
showed a switch sticky label in the center
of the device icon on the topology view.
When bringing up the DevTop view, the
device icon showed a bridge sticky label.
This also happened in the Device-
>Interface view. When bringing up the
Application view there were no bridging
application models shown. Instead there
was an SFVlanApp.
This was resolved by modifying the file to
correctly show a switch label rather than
a bridge label.