Specifications

9032277-04 MMS3 Software Characteristics
4-13
Problems Resolved in MMS3
Other Problem Resolutions
SM-SYN1009, SynOptics Stackable Hubs 2900 Series
The HubSny29xx Large icon now shows the model name at the top.
Also, double-clicking it will bring up the SynOptics Chassis
Configuration view.
SM-WEL1003, Bay Networks Wellfleet Router
The Rtr_Bay_Wflet interface information is now read from the
proprietary interface tables as well as MIB II. In this way, all of the
interfaces should be created correctly. The problem was that there was
no support for ISDN for such devices as the Wellfleet Series 7 router.
Also, ports that were not active for the Rtr_Bay_Wlflet model were not
being displayed in various port views.
Other Problem Resolutions
1. Modifying a port's security string now works correctly, i.e., it
remains as changed. Previously, any change you made to the port's
security string was overwritten with the value of the device
model's security string. This was a problem on a variety of model
types (e.g., Rtr_Cisco, 2H258_17R, 2H28_08R, and EMME).
Security strings are now rolled down from the device to the port
level but they do not overwrite user entered values.
2. A problem in which frame relay modeling was destroyed has been
fixed. The problem occurred when a frame relay reconfiguration
event occurred during a time when there was no contact with the
device or the device did not respond in time.
3. Community Name changes now roll down correctly from
rfc1512App. If the Community Name is changed on a device that
supports rfc1512App, the name will roll down to that application
and to the GenFDDISmt_II and GenFDDIMac_II models.
Community Name changes no longer cause these models to go red.
4. The Detail button in the Performance view of the
ctATMConfigMib application no longer yields a Detail view of a
default GIB; it provides the appropriate view.
5. The WA_Link WA_Bandwidth attribute/gib field no longer has
Read-Write permissions; it has Read-Only permissions.