| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| Created: | Wed Nov 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4455 |
| Total number of notes: | 16761 |
Hello,
I have a customer who has the following problem after upgrading
the DEChub 900 MultiSwitch from V4.0.0 to V4.1.0.
After the upgrade to V4.1.0 the connections from the PORTswitch 900FP
v2.0.0 to the Flex-Channels where all disconnected. Also the connection
from a DECrepeater 90FS v2.0.0 to thinwire was made! This was very
strange because there was no connection to thinwire before the upgrade
only a connection to 1 flexchannel was made! Because of this there was
created a loop in the network. (the DECrepeater 90FS has a connection
with a CISCO4000 with port was going in standby mode and therefor this
was no problem). Other modules in this HUB 2x DECswitch 900EE (v1.1.1)
and 3x PORTswitch 900TP (v2.1.0 ) has no problems with connections
after the firmware upgrade.
Customer has 2 HUB900 both with the same configuration and both gives
the same problem after upgrading the MultiSwitch firmware!
Also the customer has read the important note,
The DEChub 900 MultiSwitch Hub Manager should be upgraded before upgrading
other modules in the hub, but the DECrepeater 90FS v2.0.0 was also the
version with V4.0.0.
Quistions,
1. Is this a known problem?
2. Is possible disconnecting and connecting to flex and thinwire channels
something for the important notes of the next firmware releases?
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3537.1 | 900FP Cannot disconnect from ThinWire backplane with current F/W. | MSDOA::REED | John Reed @CBO = Network Services | Fri May 17 1996 09:50 | 7 |
This is a known issue with the DECrepetaer 900FP. See other entries in
this conference. I am still waiting for a released version that fixes
this problem.
JR
| |||||
| 3537.2 | from V4.1.0 to 4.1.1 | UTRTSC::GROOT_R | Ronald de Groot | Fri May 17 1996 11:38 | 7 |
I make a small mistake in .0 the upgrade from V4.0.0 to V4.1.0 was o.k.
but from V4.1.0 to 4.1.1 was going wrong. Customer has used the
firmware from the www.networks.digital.com/npb/dr/hubs/firmware etc.
On gatekeeper there is only the V4.1.0 version and on the network home
page you find the 4.1.1 version!
Ronald
| |||||
| 3537.3 | you're not crazy | NETCAD::MILLBRANDT | answer mam | Tue May 21 1996 11:38 | 12 |
Hi Ronald - In testing for a planned DMHUB V4.2, we have found some hub configurations that behave in the manner you described when upgrading from V4.1.0 to V4.1.1. This is a hub firmware problem independent of the PORTswitch connection problem referred to in .1. V4.2, when released, will contain a fix that will restore flex channel corrections correctly. Meanwhile, resetting the hub to current settings will clean up the connections. Dotsie | |||||