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 a customer did a Firmware Upgrade to V4.1.0 on Nine HUB900. All Hubs where updated using HUBLOADER on a PC running WINDOWS V3.11. All Hubs where factory reset and newly setup. The Lan/FDDI Segments where recreated from scratch. This was ok on eight Hubs. But one Hub gives the following problems. Before the Update was done, the Ethernet-LAN Segments (three) where named as follows: E_H1_11 E_H1_12 E_H1_13 after the Update was done and after a Factory Reset of the Hub was done there was a Ethernet LAN Segment called E_H1_121_11 This Segment is not removeable, it is not possible to connect any Lan Port to it, it even remains there after a Factory Reset. When trying to remove it the customer gets a "HUBWATCH Error delete failed" When trying to connect a LAN Port from a repeater to it the customer gets a "HUBWATCH Error Add failed" There is no Trace of Error in the Message Box from Hubwatch. The Hub is populated as follows: slot 1 DECConcentrator 900MX slot 2 DECSwitch900EF slot 3 DECSwitch900EF slot 4-7 DECreepeater900TM slot 8 DECserver900TM Can this be a Hardware Error in the Hub that only showed up due to the new Firmware ? What other posibilities do I have to get rid of this beside changing the agent/Backplane ? Thanks OTTO
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
3540.1 | Never heard of this one | NETCAD::DOODY | Michael Doody | Thu May 23 1996 14:46 | 13 |
The LAN segments are stored in non-volatile RAM in the hub's management module. When you do a "reset to factory defaults" all this non-vol memory is erased. Therefore you should not have any LAN segments left over. I can think of two possibilities: 1) There is a hardware problem in that non-volatile ram that causes it to malfunction and not be erased when you do a "factory reset". 2) You need to press the "refresh" button on the lan interconnect in hubwatch (or exit hubwatch and start from scratch). |