Specifications

Patches Issued After the CS1/MMS1 Release

Software Superseded by CS3/MMS3 Software Release Notice for 5.0rev1

5-22 CS3 and MMS3

After moving a card in the 9000 chassis to another chassis the new inb

and chassis are not being created.

When a 9000 (MMACPlus) board is removed from the chassis and

then reinserted, its System Up Time is reset to zero. Spectrum detects

this and attempts to reconﬁgure. If the board was moved from one slot

in a chassis to a different slot in the same chassis, this is correctly

identiﬁed, and the DevTop and Chassis Device views etc. are

repainted with the board in the new slot location.

However, if a board is moved from one chassis to a different chassis,

Spectrum is not detecting this. If a board is moved from slot 5 in

chassis 1 to slot 10 in chassis 2, Spectrum incorrectly thinks the board

is now in slot 10 (good) of chassis 1. It doesn't create a model for

chassis 2, or the INB of chassis 2, etc.

(Also refer to the Notes on corrected anomalies, on Page 5-14.)

SPECTRUM_5.0rev1.P50

The 3Com SuperStack II FMS Token Ring Hub has extra ports

supported in its MIB called the Router, RingIn, RingOut and Cascade

ports. These are in a different table from the standard ports. Support

is required for these extra ports so that they can be displayed properly

in the Device and DevTop Chassis Views. The resolution was to add

the GIB ﬁles and database changes that were required.

AutoDiscovery is not fully supported in the current module. The 3Com

FMS Token Ring Hub has extra ports in addition to its normal

repeater ports. There are 4 types of ports of which there can normally

be up to one of each on a stackable hub unit. These are the Router,

RingIn, RingOut and Cascade ports. Currently the Router port is the

only one which can contain MAC Address information. This port is

currently unsupported in AutoDiscovery. The resolution was to create

the necessary inference handler to support the Router port.

When AutoDiscovery runs on the 3Com SuperStack II from the

Universe view a Hub3ComSSTR_A is properly created. There are a

few evident problems that occur.

1. The 3ComTRChassisApp is placed in a Network container. There

is no devtop for this model to show connections.