| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2331.1 | | NETCAD::DOODY | Michael Doody | Wed May 31 1995 16:09 | 15 |
| What are you power-cycling? The DEChub 900 or the 900EF?
How long is the interval between the "put port #7 on the back" step and the
power-cycle step? And do you wait the same amount of time every one?
Do you do anything else (Like remove the 900EF from the hub)?
What else is in the Hub? (9 is not evenly divisible by 6) .
Were all the "bad" ones installed in the same Hub?
Any messages from Hubwatch when you configure the port #7 ? Do you just
configure it out the back, or is it also connected to an internal LAN?
Hubwatch, MAM and 900EF Fw revs might be helpful.
-Mike (many questions & no answers)
|
| 2331.2 | attempt at answers | HACMAN::HACK | Don Hack, Network Services | Wed May 31 1995 23:52 | 41 |
| >> What are you power-cycling? The DEChub 900 or the 900EF?
I tried both. toward the end, I just pulled the 900EF from the hub, waited 3-5
seconds and pushed it back in the hub.
>> How long is the interval between the "put port #7 on the back" step and the
>> power-cycle step?
During real life usage, the port would be turned around. maybe hours later I
would make some other changes and power cycle the hub. The 900EF would come up
not turned-around.
During testing, I often set it, due to slow PC, wait about 20 seconds, then
pull the 900EF from the hub, wait 5 seconds, put the 900EF back in and waitc it
come up.
>> And do you wait the same amount of time every one?
No. It varied a lot.
>> Do you do anything else (Like remove the 900EF from the hub)?
Sure, see above.
>> What else is in the Hub? (9 is not evenly divisible by 6) .
Typically,
8 - 900EF
7, 6, 5 900TM repeater
4 900TM DECserver, .... but it varied with hub.
>> Were all the "bad" ones installed in the same Hub?
No. Various hubs over several days.
>> Any messages from Hubwatch when you configure the port #7 ?
No. It looked successful.
>> Do you just configure it out the back, or is it also connected to an
>> internal LAN?
? I typically had A/B on a FO ring (but not always) and port 7 turned to an
internal HUB900 Ethernet LAN.
>> Hubwatch, MAM and 900EF Fw revs might be helpful.
Don't have that info today. Off to another client (another state) tomorrow.
HUBwatch was/is v3.1.0. All of the hardware shipped in May-1995.
-Don
|
| 2331.3 | | NETCAD::DOODY | Michael Doody | Thu Jun 01 1995 10:40 | 27 |
| The DEChub 900 stores the configuration in its non-volatile memory for
each module installed in the Hub. The module (in your case 900EF) does
not remember whether it had ports out the back or not - it is the Hub's
job to do that (fyi).
When you remove the 900EF from the Hub (with the Hub running, a
hot-swap) the configuration for that slot is deleted. This is expected.
That is why you see that port #7 is out the front again - the default.
It's not clear whether this explains what you saw when you first thought
you had a problem. The Hub remembers the configuration across power
failures - I do it all the time.
If you see cases where the 900EF has port #7 configured out the back,
and you never remove it from the Hub, and you wait, and then you power
cycle the Hub, and when the Hub comes up the 900EF port #7 is out the
front, then we have a problem. Maybe there is an Errorlog entry for the
Hub?
Also, whenever you make a configuration change, you should wait at
least 15 seconds after the operation is complete before removing power
from the Hub so that it has time to write the configuration to non-vol
memory. I know you said you waited 20 seconds but I want to make clear
it is indeed necessary.
-Mike
|
| 2331.4 | What about ... | HACMAN::HACK | Don Hack, Network Services | Thu Jun 01 1995 18:20 | 8 |
| Thanks for the help. One clarification ... The HUB900 remembers the
config for the "module". Does it remember for the slot or the specific
module (via Ethernet address?)? So if I move the 900EF, after powering
down the hub, from slot 7 to slot 1 will it remember?
Also, what is the best document to gain further insight on such topics?
Again, Thanks .. Don
|
| 2331.5 | | NETCAD::DOODY | Michael Doody | Thu Jun 01 1995 19:07 | 20 |
| The Hub remembers the configuration by slot & module type. If you moved
a module from slot 7 to 1, you'd lose the configuration for slot 7 and
slot 1 would still have no configuration.
If you had a 900EF in slot 7 configured, then with the hub powered down
you swapped the old 900EF for a new 900EF in the same slot, when the
hub was powered up it could not tell the difference.
If you had swapped a 900TX in slot 7 instead, you lose the configuration
because it is a different module type.
FDDI Auto Healing improves the rules a bit, but wait for the new FDDI
configuration note for more details on that. (RSN)
>>Also, what is the best document to gain further insight on such topics?
Anyone have a suggestion? The Owner's manual and release notes will
touch on bits and pieces for starters.
-Mike
|
| 2331.6 | see ch. 6 of HUBwatch Use Manual, v4.0 | NETCAD::MOWER | | Fri Jun 02 1995 17:49 | 9 |
|
>>Also, what is the best document to gain further insight on such topics?
The HUBwatch [4.0] Use Manual has a 47-page chapter dedicated to
LAN interconnect issues. I would recommend that you read the version
of the Use manual that goes with HUBwatch v4.0 since many changes have
been made to the chapter since the previous version.
Carl Mower.
|