Specifications

Patches Issued Since the CS2/MMS2 Release

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

5-42 CS3 and MMS3

SPECTRUM_5.0rev1.P71

Included in SPECTRUM_5.0rev1.P101

SPECTRUM_5.0rev1.P72

The problem was that AutoDiscovery and Modeling by IP allowed

duplicate models without warning for the following model types:

2E43_51 and 2H23_50R or any other device covered under SM-

CSI1068 or SM-CSI1080. As it turned out AutoDiscovery WAS

ﬁnding the already created model, but then it checked to if the model

had the Dev_Model_Handle attribute (meaning the model was a

component of some other model). If it has the attribute, it reads the

attribute and assumes that model is the already existing model. For

some reason many of the model types exhibiting this problem HAVE

the Dev_Model_Handle attribute. They shouldn't. It's value was 0x0

for these models, thus when AutoDiscovery read it, it gets 0x0 back,

and model appears not to be found.

The resolution was setting the Dev_Model_Handle for the 2H23_50R

and 2H33_37R model types to be themselves. This caused

AutoDiscovery to not allow multiple modeling of the same device.

The problem was that the Device Chassis View of the 2E253-49 was

not comprehensible. All the ports were squeezed together making all

the information in them useless. The 2E253_29R was using the wrong

iib ﬁle, making it look like a 6000 series management module for the

Device Chassis View.

The resolution was to correct the Iib ﬁle so that the Device Chassis

View is understandable and uncrowded.

The problem was that a "Device Not Conﬁgured" error message

appears when attempting to get to the DevTop View of a FddiMAC

model of model type's 2E42-27 or 2E42-27R with HSIM-F6's installed.

This problem was found particularly with the following install

conﬁguration: 4.0rev3, MS1, RS3, MS2 and MS3, CS1/MMS1. Also,

no FDDIPort's (A-Type and B-Type) were showing in the DevTop View

of the FddiMAC models. Only Rptr Port models were present.