| 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 |
I've found an interesting problem with the DR 900FP and was wondering if
anyone had any suggestions.
The hub consists of:
Slot 1 DECagent 90
Slot 2 " "
Slot 3 " "
Slot 4 Empty
Slot 5 DECrepeater 900FP
Slot 6 DECrepeater 900FP
Slot 7 DECbridge 900 FDDI & all 6 Ethernets to backplane
Slot 8 DECbridge 900 FDDI to backplane, all 6 Ethernet to front panel
Slot 5 DR 900FP
Ports IMB Floor
1-2 1 23
3-4 1 24
5-6 6 25
7-8 2 26
9-10 2 27
11-12 3 28
Thinwire to IMB 1.
Slot 6 DR 900FP
Ports IMB Floor
1-2 3 29
3-4 4 30
5-6 5 31
7-8 4 32
9-10
11-12
The DR 900FP's are at HW 1, RO 1, SW 1.0.1
I put a DECserver 90M into slot 4 and was attempting to upgrade the
flash ram. After 15 minutes of watching the LED blink I killed the load.
I restarted the server and did a SHOW SERVICE. About a dozen systems
showed up. I tried connecting to many and sometimes got a connection but it
was slow to print the ACCOUNCE.TXT on the screen. When entering the
username it was slow to echo what I typed and many times just lost the
connection. Going into the counters both in the server and LATCP showed a
high percentage of duplicate messages.
I tried using the repeater in slot 6 to repeat an IMB to the thinwire.
Same results.
Next I removed a DECagent and put a DEFAR into the hub. I fiber patched
the DEFAR to port 11 in slot 6. Port 11-12 was then connected to any IMB
and the server performed properly. The upgrade took less that a minute and
there weren't any duplicate messages.
Why doesn't the 900FP appear to be connecting (repeating) the thinwire to an
IBM properly? IMB 1 is lightly loaded although the other IMB's can get busy
from time to time, ie. orange LED on DB 900 will light solid for up to 30
seconds at a time.
dave
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1174.1 | More info please. | LEVERS::PAGLIARO | Rich Pagliaro, Hub Products Group | Wed Jun 29 1994 14:12 | 5 |
When you were having difficulty loading, what was the state of the #
LED on both of your DR 900FPs (i.e., solid on, solid off, blinking at
regular intervals, flashing erratically)?
-Rich
| |||||
| 1174.2 | LED status | CGOS01::DMARLOWE | Have you been HUBbed lately? | Wed Jun 29 1994 15:12 | 24 |
Slot 5 providing the thinwire connection
Slot 5
The # LED was on solid and the -> LED was flashing randomly with
traffic.
Slot 6
The # LED was slow flashing to indicate disabled.
Slot 6 providing the thinwire connection
Slot 5
The # LED was slow flashing to indicate disabled.
Slot 6
The # LED was on solid and the -> LED was flashing randomly with
traffic.
I spoke to Scott L. and will try other config testing and post results.
These repeaters were close to being first from manufacturing.
dave
| |||||
| 1174.3 | So confused | CGOS01::DMARLOWE | Have you been HUBbed lately? | Thu Jul 07 1994 11:37 | 77 |
More info.
Slot 5 DR 900FP leg 7 to Thinwire (DR 900FP in slot 6 disconnected, no
repeater loop). Thinwire grouped to Group 1 which was connected to Ports
1-2 and then to IMB 1.
When connecting to a host, CONNECT XXX, you would get the ANNOUNCE.txt and
the USERNAME prompt. Anything you typed would be echoed sporatically and
in bursts. You could type in your entire username and it would echo back
2-3 characters at a time. You could login completely and run various
applications. Within a minute or so you would get dropped with a LAT
timeout error.
LATCP counters
Messages retransmitted (45)
Duplicates (9)
LATCP errors
Invalid sequence number received (1)
Virtual circuit timeouts (4)
Slot 6 DR 900FP leg 7 to Thinwire (DR 900FP in slot 5 disconnected, no
repeater loop) Thinwire grouped to Group 1 which was connected to Ports
1-2 and then to IMB 1.
When connecting to a host, CONNECT XXX, the first message from the terminal
server would be "No response within timeout" followed by "Attempting
failover" and then "XXX not currently available". If you did a SHOW
SERVICE at this point in time you would not see host XXX. Within 1 minute
it would show up as part of the host service broadcast. Sometimes you would
receive part or all of the ANNOUNCE.TXT.
LATCP counters
Messages retransmitted (38)
Duplicates (1)
LATCP errors
Invalid sequence number received (1)
Circuit was forced to halt (1)
Node circuit invalid (1)
Virtual circuit timeouts (9)
DEFAR. A DEFAR was added to slot 4 in the hub. Both DR 900FP's had then
thinwire legs disconnected from the thinwire. The DEFAR fiber port was
used to connect to the DR 900FP in slot 5 port 2 (port 1 went to a floor).
Port pair 1-2 went to IMB 1, the same as going through the DR 900FP in the
above testing. The terminal server responded properly with no LATCP errors
and there were no echo delays.
Pings to one of the DECagent 90's on the thinwire had the following
results (UCX used, all values in millisec, min/avg/max):
Thru slot 5 10/12/50
Thru slot 6 10/11/60
Thru a DEFAR 10/10/30
However, when trying to use HUBWATCH to get to a DECagent 90 (through a DR
900FP, slot 5 or slot 6) I kept receiving SNMP timeouts saying unable to
get to agent.
It seems that each DR 900FP repeater engine between the thinwire and an IMB
responds differently but incorrectly. A DEFAR, which bypasses this
repeater engine does work properly.
dave
| |||||
| 1174.4 | it's works for me.. | PADNOM::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Tue Jul 12 1994 14:02 | 28 |
Hi Dave,
i tried unsucessfully to reproduced your problem in my lab
with configuration here under
======================== main LAN
| |
Bunch of VAX's DECBRIDGE90FL
/
/
/ Fo
/
slot 8 DECREPEATER900FP port 12 internal Chanel 5 imb 7 attached to
HUB900 slot 4 Decserver90l thinwire
V3.0 slot 2 Decserver900TM
From Decserver90l i can connect to any Vax on the main LAN without problem
of Deconnection or Delay during the display.
i can load my Decserver900TM from The main LAN without problem (3 min)
as this configuration reflect your customer problem ??
as have omitted something
Jean-Yves
| |||||