Specifications

Patches Issued Since the CS2/MMS2 Release

Software Superseded by CS3/MMS3 Software Release Notice for 5.0rev1

5-82 CS3 and MMS3

(0x10c48) is read for each ATM Network model found. In case the

AutoDiscovery is launched from AtmNetwork model itself then it

will be added to the network_list.

The problem was a multiple memory leaks were found while

Spectrum_5.0rev1, Spectrum_CS2/MMS2, Spectrum_5.0rev1.P54 and

Spectrum_5.0rev1.SLAM-P54 were installed. Purify had been

installed and a trace was made available.

The resolution was to remove the memory leaks from the code

pinpointedby the Purify traces.

The problem was SpectroWATCH watches will not stop polling or

logging until the watches are destroyed.

The resolution was change how the values were being propagated in

SwIHEval.

The problem was modeling a SS6000 in distributed environment

resulted in an error for the 6C105 and no blades were placed in the

Topology View. The error was as follows:

Error: Model Type of Device XXX.XXX.XXX.XXX Already

exists and cannot be related to this viewed model.

Existing Model: 6C105 of Type 6C105

The modeling was occurring properly, but the blades were not getting

placed into the Topology. This was because the AutoDiscovery code

was discovering the chassis as it pinged the IP and then created it.

Then the Management Module got triggered and created the blades

themselves. But AutoDiscovery only knew about the chassis, so it

attempted to place it in the Topology, which results in the error

window, as the chassis is not topologically signiﬁcant.

The resolution was to change AutoDiscovery so that during the Model

by IP process it will ﬁre off a new action containing the model handle

of the view which should be Collecting the model(s). The action will

fail for MMs that don't implement it, in which case AutoDiscovery will

behave as usual by setting up the Collects relationship with the

proper Topology. For Management Modules that do implement the