Specifications

9032277-04 Software Superseded by CS3/MMS3
5-27
Patches Issued After the CS1/MMS1 Release
Open the Device Chassis View of a 6E122-26, then select the field
"Physical" of a board and open the Icon Subview Port Display Form.
You are able to switch from Operational Status to Duplex Mode but
you cannot switch back to Operational Mode again. The same behavior
exists when you switch to Speed and then back to Operational Mode.
This has been resolved by allowing the user to switch back to
Operational Mode.
After deriving a model type from Rtr_Cisco, adding some attributes,
and creating an instance of the new model type, it was found that the
intelligence attached to the Rtr_Cisco model (e.g. Action Buttons in
the Configuration-> Net/Host Configuration View) were non-
functional (returning the error Error = Not Implemented,0x2). This
has been resolved by fixing the if conditions in the MI file for all the
intel on Cisco Routers.
After doing an in-place migration of 4.0rev3 to 5.0rev0, you are unable
to see statistics dating prior to the 5.0rev0 installation. The events
converted fine and they could be seen dating prior to the 5.0rev0
installation. This is caused by an error in the Statistics migration
component of ddm_load. Because of the format of the old 4.0rev3
saves, we must use heuristics to try to match the data from the
various save files. In particular, we read through the
DDMSAVE_stat_attr_data file to get model/attr handle combinations
and their associated data, then we read in the
DDMSAVE_stat_time_data file, looking for a match on the model/attr
handle to read the compressed time nodes that correspond to the data.
The error lies the fact that if for some reason there are no compressed
time nodes for a model/attr, then we read past all of the time nodes
looking for a match, and we never reset the file pointer. Also, we never
read another time node to try to match it with the subsequent model/
attr handle data nodes. This has been resolved by changing ddm_load
to allow for loading of the rest of the time nodes.
SpectroSERVER cores after the copyright screen appears. This was
caused when the VGE interface was installed; the Solaris kernel stat
structure added 64 other interfaces. There is a hard-coded limit of 16
interfaces in SPECTRUM. This has been resolved by implementing a
check in the code that determines how many interfaces there are so it
won't exceed the limit.
After starting the SpectroSERVER and SpectroGRAPH and setting up
a Background Discovery, if you restart the SERVER for any reason,
the Background Discovery will no longer run at the previously