Specifications

Software Superseded by CS2/MMS2 Software Release Notice for 5.0rev1
5-24 CS2 and MMS2
In SPECTRUM 5.0 and beyond, we do not examine the state of the connected
ports during a WA_Link's Fault Isolation process. We simply look at the status
of the connected devices. If both devices are up, then the WA_Link will be
GREEN. This causes problems when the VNM has a redundant connection to
the remote device. When the wide area connection goes down, the VNM will
have a second way to contact the remote device, thus we won't lose contact
with it. This results in no alarms even though the WA_Link went down. In
4.0rev3, WA_Links used to monitor the status of the connected ports and
generate an ORANGE "Probable Link Failure" alarm when one of the ports
went down. This patch adds this type of functionality back in for WA_Links.
When modeling a HubCat 5500 device, the SpectoGRAPH crashes when
opening the Configuration View. This was resolved by modifying the GIB view
to prevent the crash.
On startup, the SpectroSERVER randomizes the first poll for all devices over
a fixed ten minute period. While this works well to distribute the load when
polling and logging are at the Spectrum defaults, it does not work well on very
large databases where the polling interval has been extended beyond ten
minutes. This results in a very cyclic SpectroSERVER workload, and
decreases overall capacity and response time. A .vnmrc entry can be added to
allow the randomization period to be set. This entry is: mdl_act_dist_factor.
The Archive Manager is crashing and producing a core file. This is caused by a
double-delete occurring when running a Data Export when the user no longer
has permission to access a model. This has been resolved by deleting the
memory correctly.
ArchMgr uses up to 100% of the CPU and will continue to do so until the
process is killed. It appears that we have found a hole in the 5.0rev1
CsMgrClientList, where the client_list member can schedule during list
manipulation, which can allow the list to become corrupt. This can then cause
core dumps or 100% CPU usage due to an infinite loop. This has been resolved
by preventing the client_list member from scheduling during list
manipulation.
Going into the devtop of a BRtrCSIEMM_E6 causes the SpectroGRAPH to
core dump. This was caused when changes were made to correct
swbug011329; not all files needed to fully complete this change were included
in P34.
An EPI agent can send an unsolicited message to Spectrum in the form of an
attribute change. There is currently no means for logging when these
attribute changes occur. A new attribute called Log_Attr_Changes of type
Integer has been added to the EpiPif model type. This attribute will maintain
3 valid values. 0 = no logging, 1 = log all changes, and 2 = log only when the
value of the attribute changes.
Purify reports a memory leak in adisc. The memory allocated for conn_DTEs
should be freed.
Recently while working on the PatrolView integration, a problem was
discovered relating to icon arrangement. Several of the PatrolView model