Specifications

Software Superseded by CS2/MMS2 Software Release Notice for 5.0rev1
5-4 CS2 and MMS2
SPECTRUM_5.0rev1.P16
Error while retrieving the alarm history information. An error occurred while
retrieving the alarm history information for this model. Error: Error
0x6000020 (0x6000020)
Problem with canceling filter when in Modeltypes tab.
Get error message when starting AlarmManager as RO user.
5.0rev1 SANM can't handle distributed environments if one is 4.0rev3
SERVER.
The Alarm Manager does not handle a large number of events well in the
Events tabbed page of the information panel.
The History tabbed page should be rolled into 5.0rev1 since it provides
information the user really wants. The history page displays all events for a
specified model between creation of an alarm and clearing of the alarm.
ForeRunner ports create a red alarm when device attached to the port goes
down. These should be yellow alarms.
When changing the Model Name of a Model via the Model Information View
the new name does not get propagated to all of its child models.
A READ only user can change the Filter options in the Alarm View.
Filtering on multiple PCauses in the Alarm Manager is not saved to the user
model.
SpectroSERVER crashes with a mts:malloc: out of memory message.
FrameRelay is not suppressing the dlci alarm when the router goes down. Two
new attributes were added to support this functionality: AlarmLinkedPorts
and SuppressLinkedPortAlarms. These two attributes have been added to the
LivePipes Information GIB accessed from the VNMs Performance GIB
“Application” list. They toggle from TRUE to FALSE.
Live Pipes is not suppressing one of the port alarms when both linked ports
are bad and the “Suppress Linked Port Alarms” option is set to TRUE in the
Live Pipes GIB.
Watch Editor PGUI will not allow polling interval over 06:28:15.
SpectroSERVER crashes with mts.malloc error after upgrade to 5.0rev0.
SpectroWATCH does not work for calculations like: x=x+y.
When a WA_Link is determining its proper state during re-start, it asks both
routers if they are down. The GREEN router responds, “No, I'm up”. The
ORANGE router incorrectly responds “Yes, I'm down”. This causes the
WA_Link to go RED.
At times we lose contact with LandScapes models.