Specifications
Patches Issued Since the CS2/MMS2 Release
Software Superseded by CS3/MMS3 Software Release Notice for 5.0rev1
5-84 CS3 and MMS3
--
The problem was that SpectroSERVER was core dumping several
times over a period of three days. All the SPECTRUM systems were
in a distributed environment using a MOM SpectroSERVER as the
main location server and for modeling remote landscapes. Of the 12
SpectroSERVERs in the environment, two have experienced this
SERVER core dump and three (the previous two systems included)
have been experiencing a problem with the SpectroSERVER growing
in memory use while the DDM database grows in size.
The resolution was to add code fixes to the connection layer to prevent
the SpectroSERVER core dumping and growth in memory use.
--
The problem when attempting to set the "Desired Operational Mode"
in the Fast Ethernet Configuration window for a Cabletron Fast
Ethernet port the only set that works is "Auto-Negotiation". Sets to
other menu options 10Base-T, 10Base-T Full Duplex, 100Base-TX,
100Base-TX Full Duplex fail. When the Apply button was clicked on
SPECTRUM went out and made sets to both the Desired Operational
Mode and the Advertised Ability. If only the Advertised Ability was
changed the set worked fine. A
The resolution was to add a menu option for the port models of
Cabletron Fast Ethernet devices called "Enet Based Config". This
view is accessible from the Device Chassis view of the parent device
This view will launch the correct SPMA for the device, which in turn
allows all available Desired Operational Mode's to be set. These are:
Auto-Negotiation, 10Base-T, 10Base-T Full Duplex, 100Base-TX, and
100Base-TX Full Duplex.
--
The problem was Frame Relay port and connections were
"disappearing" after SPECTRUM lost contact with devices that were
connected by Frame Relay. This problem was not easily reproducible,
but was found to occur frequently when Frame Relay reconfiguration
event happened during the time when there was no contact to the
device. In the event of a reconfiguration, the frame relay modeling
was updated when the logical (internal) modeling was compared to the
physical (external) representation. This was done by reading the
device's frCircuitIfIndex=1.3.6.1.2.1.10.32.2.1.1 table. If during the
reconfiguration the MIB was not read successfully, the reconfiguration