Specifications

9032277-04 Software Superseded by CS3/MMS3

5-65

Patches Issued Since the CS2/MMS2 Release

The resolution was to add a check in the View Information Block to

prevent any further SpectroGRAPH crashes while Editing and Save &

Closing while new models are being created.

The problem was Range Router AutoDiscovery was not discovering

second tier routers. An example of a scenario where this would occur

is as follows:

The customer had 16 backbone routers. They also had 400~900 second

tier routers in a few hundreds ClassB networks. They wanted to use

the 16 backbone routers as seed routers and then run IP Range Router

Discovery to discover all the second tier routers. However, IP Range

Router discovery failed to ﬁnd the routers.

The reason that no router found was that the code only checked the

seed routers nextHop addresses to see if the remote side router was

within the IP range. If it was, the NextHop address gets added to the

discovery list. If it was not, then the remote router gets ignored.

The resolution to this problem is to also check the backbone router's

Destination Address. If the Destination Address or the NextHop

Address is within the discovery IP range, then the NextHop Address is

added to the router discovery list.

The problem was a memory leak was found in association with the

creation of SynOptics 3000 devices. Purify had been installed and a

trace was made available.

The resolution was to remove the memory leaks from the code

pinpointed by the Purify traces.

The problem was the SpectroGRAPH was producing a segmentation

violation when the user exited SpectroGRAPH after a Distributed

Find Search. A core trace was made available.

The resolution was to correct code so that no segmentation violation

would occur if the user exits SpectroGRAPH after a Distributed Find

Search.