Specifications

Patches Issued Since the CS2/MMS2 Release
Software Superseded by CS3/MMS3 Software Release Notice for 5.0rev1
5-98 CS3 and MMS3
The resolution was to make the appropriate database change so that
the CTM_Switch_MTH / 0xd80084 attribute of the 9A686_04 model
could be read by the SFSmartCell model.
--
The problem was the DevTop View was not launching off of the
SFSmartCell model.
The resolution was to correct code so that the DevTop View
successfully off of the SFSmartCell model wherever it is an option.
--
The problem was that a 6H252 with an HSIM-F6 installed did not
create the FddiMAC model in the DevTop or Application view when
modeled. AutoDiscovery did create a pipe to an FDDI container but
placed it as a GenFDDIMac_NM that remained blue. The source of
the problem was an attribute in the database that was used to point to
a fddiCreator model type handled all the fddi creation issues
(including fddiMACs). For many SS6000 devices, and a handful of
SS9000 devices, this attribute was not correctly set, so the creation
intelligence didn't know how to create the proper FDDI Applications.
The resolution was to change the attribute in the database to point the
creation process to the correct OID string in order to create the
fddiMAC application.
NOTE: Depending on what patches/maintenance versions of
SPECTRUM are installed, a "Device Not Configured" message may
appear when a user tries to drill into the DevTop of the fddiMAC
application. This is a separate known issue with all major
SmartSwitch devices (2000, 6000, 9000).
--
The problem was the value (Index List of 36 OIDs) of DisSysOIDList
(Attribute 0x00011fae) seems to be erased. The reason was because
DisSysOIDList 0x11fae attr does not have the Preserve Value Flag
set. The problem appeared after a customer installed SPECTRUM
5.0r1/CS2/MMS2 CD & P54, SLAM-P54 Patches over an existing
SPECTRUM area, but has existed since the DisSysOIDList was first
introduced.
The resolution was to set the Preserve Value Flag for DisSysOIDList
0x11fae.