Specifications

Patches Issued Since the CS2/MMS2 Release
Software Superseded by CS3/MMS3 Software Release Notice for 5.0rev1
5-108 CS3 and MMS3
The problem was that the SpectroSERVER was crashing with an mts
malloc out of memory error when the Asnd_MAX model was in the
database. When this model was not present, the SERVER would not
crash. The crash was caused by the negative value being returned by
the device for mdmNumber.
The resolution was to add a check to make sure the value returned for
mdmNumber was not negative. The SpectroSERVER should no longer
crash when the Asnd_MAXmodel is in the database.
--
The problem was that no pipe was being created between the two ATM
interfaces in the following scenario:
A WA_Link model was placed off at AAL5 (ATM Adoption Layer)
interface on non-core router, and a LAN model placed off at ATM
subinterface on core router. The two interfaces (AAL5 and ATM
subIF) were directly connected together. But no pipe was created
between the two interfaces.
The resolution was to change the way SPECTRUM resolves these
connections so that the pipe will be created.
--
The problem was that AutoDiscovery code placed a LAN model off an
interface that had a direct route. If a LAN was subneted by mask
255.255.255.252, only two IPs would be allowed for the subnet. These
two IPs would be used for the two interfaces from each side router. For
this case, no third device was allowed to connect/be within this subnet
LAN.
The resolution was to change AutoDiscovery so that the other router
would be placed off of the interface rather than the LAN model.
--
The problem was that several variables for determining whether a
model type was a valid subnet type were not initialized.This was
causing AutoDiscovery to work incorrectly.
The resolution was to initialize the variables and remove others that
were hindering AutoDiscovery.
--