|
Well, until we can verify that the customer is using the latest version
of HUBwatch & firmware for all modules, all we can do is speculate.
I've done this many times and it works fine. In order for this to work,
it only works if the hub is powered down and up, not if the customer
removes and inserts modules (even if into the same slots). In the next
version of the hub firmware, you should be able to remove a module and
if you replace the it with the same type of module, all connections
will be restored. This will be controlled by a setting which allows you
to enable/disable this feature.
Yes, I've encountered "the loop" also...
|
| Make sure you wait at least 15 seconds after any changes to the hub
before the power is removed. It takes that long for the hub's
configuration to be written to non-volatile memory.
There were fixes included in MAM v4.1.0 that involved losing the
configuration after power loss. Make sure they're up to at least that
rev.
>removes and inserts modules (even if into the same slots). In the next
>version of the hub firmware, you should be able to remove a module and
>if you replace the it with the same type of module, all connections
>will be restored. This will be controlled by a setting which allows you
>to enable/disable this feature.
That works today for FDDI modules that are connected to the backplane.
At this time, I'm not sure if we'll be able to fit it in for all other
modules in next release.
-Mike
|