Specifications

9032277-04 Software Superseded by CS3/MMS3

5-69

Patches Issued Since the CS2/MMS2 Release

The resolution was to create an action object that can be added to an

iib ﬁle for an icon. The action will take name of menu, action code and

text that describes that action to be displayed along with the returned

error from the action.

The problem was that SpectroGRAPH was crashing (with a trace)

consistently in cases where a device was not initialized correctly, the

SpectroSERVER was down, etc. For example, a customer navigated to

a port on an EMME-6 and then tried to launch something from the

menu pick of the icon and the SpectroGRAPH crashed. The customer

launched it again and that time it didn't crash. The customer created

another device that had the CSIRptPort model for interfaces. When

an attempt to launch a program from the menu was made the

SpectroGRAPH crashed again.

The resolution was to prevent the SpectroGRAPH crashes by changing

the DeviceNode member to initialize to "unknown".

The problem was that RMON probes have to manually placed into

discreet LANs. It is necessary for them to be in discreet LANs to

collect statistical information (i.e. from SpectroWATCHes).

The resolution was to add functionality so that SPECTRUM would

automatically place RMON probes in discreet LANs.

The problem was that there was an inconsistency in the two methods

for creating new models. The community string ﬁeld in the Model by

IP GIB is limited to 16 characters. The community string ﬁeld in the

Model by Type GIB is not limited.

The resolution was to take away the 16 character limitation for the

community string ﬁeld in the Model by IP GIB.

The problem was AutoDiscovery of the 2H23_50R was failing to

resolve attached devices to a port in the CsRipEnetRptr model.

Attached devices were being placed in a fanout in the same LAN

container as the CsRipEnetRptr but no connections were resolved.

This is caused by the CsRipEnetRptr failing when attempting to