Specifications

9032277-04 Software Superseded by CS3/MMS3
5-21
Patches Issued After the CS1/MMS1 Release
The solution is to write a new inference handler and attach it to the
SS6000 module. It will be responsible for gathering the MAC
addresses heard off the SS6000 module's interfaces, as well as the
MAC addresses of the modules connected to it via its backplane
interfaces. The model state algorithm will also be modified so that a
SS6000 module will only go active after it's properly associated with a
chassis. However, if a chassis cannot be determined within 2 minutes,
then the model state will be forced active, and a yellow alarm will be
generated to alert the user. In order for all this to work, all modules
that reside in the chassis must be modeled, and their model states
must all be ACTIVE, before the GET_ADDRESS_LIST action is sent
by Adisc. This will be the case if all the SS6000 modules reside in a
single subnet. However, if they don't, then Adisc may have to be run a
second time in order for the SS6000 modules to have access to their
neighbor's MAC addresses.
NOTE: Connections will only be established between modules if
the module's backplane interface has a MIB II ifOperStatus of up,
and a dot1dStpPortState status of learning, forwarding or
listening.
NOTE: If the customer has done manual modeling and placed
S6000 boards from the same chassis into different IPClass, LAN
or Network containers then the modeling will still be
unpredictable.
The problem is that the serial number for SS 2200's cannot be read
from the GIB views. The resolution is to attach an inference handler
that copies the serial number from the device to the internal serial
number attribute to the hub model.
The Chassis view for SS6000 devices has an area on the right side of
the view for chassis power supply and fan information. Currently no
information shows in these boxes. The appropriate methods need to be
updated to include appropriate instance information during the reads.
The view of the SmartSwitch 6000 backplane does not show the
backplane ports (b1, b2, b3, b4, b5) correctly. The ports are not shown
in numerical order; at times they show up in random order. The
problem is an array indexing problem. A new default type was created,
and all interfaces read from the OID table are automatically added to
the list, effectively putting the HostPort interface at the end of the list.
This takes care of the array indexing issue for the SS6000 devices.