Specifications

Problems Resolved in MMS3
Third Party Management Module Problem Resolutions
MMS3 Software Characteristics Software Release Notice for 5.0rev1
4-10 CS3 and MMS3
SM-BAY1000, BayStack Ethernet Hubs
1. The Baystack 350-24T now models as the HubBatSt350 model. It
no longer comes up as GnSnmpDev.
2. The HubBaySt450 Large icon and Application Device icon now
display in the Device Configuration and Chassis Group views.
SM-CAT1002, Catalyst 5000/5500/5509
1. The Device and DevTop views of the HubCat5000 and
HubCat5500 now work correctly. A Port Configuration view with
correct fields is accessible by bringing up the Icon Subviews menu
on a port in the Device Logical and Device Chassis views.
2. It no longer takes an unusually long time to bring up the
Application view of the Catalyst 5000. Polling has been reduced.
3. Bringing up the Configuration view on a HubCat5500 or
HubCat5000 no longer causes SpectroGRAPH to terminate.
SM-CAT1002
The Catalyst 1900, 2820, and 3200 devices now AutoDiscover and
model correctly. The problem was that a Catalyst 1900, 2820, and 3200
device would be AutoDiscovered and Modeled by IP as a Rtr_Cisco
when the Catalyst Management Module was not installed. This was
because there was nothing in the system descriptor for these devices
that would disqualify them from being modeled as a Rtr_Cisco. The
resolution was to give the Rtr_Cisco model type the ability to
disqualify all Catalyst devices (including the Catalyst 1900, Catalyst
2820 and Catalyst 3200). The term "atalyst" was added as a
disqualification criterion to the CsCisRtrMI.cc is_it_a_10_Rtr_Cisco
function.
SM-CAT1003, Catalyst 1900/2820
Catalyst 1900 devices now model correctly as SwCat1900 models and
not Rtr_Cisco models.
SM-CAT1004, Catalyst 3200
The SwCat3x00 devices now correctly discover as SwCat3200 models
and not Rtr_Cisco models.