Specifications

Patches Issued Since the CS2/MMS2 Release
Software Superseded by CS3/MMS3 Software Release Notice for 5.0rev1
5-66 CS3 and MMS3
The problem was the Annotation Toolbox did not use the same grid as
the SpectroGRAPH did, regardless if *snapGrid: was set to True or
False. This was resulting in some movement of text and graphics
when views were cloned and/or zoomed to lesser or greater sizes.
The resolution was to correct the zoomed and unzoomed coordinate
calculation so that they did only assume the view was at 100%.
--
Memory leak found in CsRMNSetup.cc
This was corrected by restructuring the code so that deletes are done
only once at the end of scope.
--
The problem was that SpectroSERVER was core dumping while
running Purify. As Purify had been installed a trace was made
available.
The resolution was to correct the code pinpointed by the Purify traces
causing the core dump.
--
The problem was the SpectroSERVER was core dumping on a regular
basis when modeling Rtr_Cisco models that were undergoing frequent
physical configuration changes (frame relay interfaces were being
changed to sonet interfaces). The devices were undergoing frequent
physical reconfiguration.
The cause for the core dump was that at time T1 (action
AD_ROUTE_TABLE_DISCOVERY), IF 129 was physical interface, or
not a FrameRelay sub-interface, then later at time T2 (action
AD_ROUTER_MAP), IF 129 was configured as a FrameRelay sub-
interface. Since the devices were reconfigured very frequently and
dynamically mapped their network with Spectrum, above problem
could happen.
The resolution was to change the code in
CsIHRouterMap::get_subnet_list() not to call get_spectrum_if().
Although the device configuration may change from T1(action
AD_ROUTE_TABLE_DISCOVERY) to T2 (action
AD_ROUTER_MAP), we should always use the same information
gathered in AD_ROUTE_TABLE_DISCOVERY to map the device.