| Title: | FDDI - The Next Generation |
| Moderator: | NETCAD::STEFANI |
| Created: | Thu Apr 27 1989 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2259 |
| Total number of notes: | 8590 |
Configuration:-
---------------
Thinwire Ethernet "A"
|--------------------------------------------------|
Hub "A" | |
+-----------+ +----------------+
| D D D | +------| DECbrtidge 5xx |------+
| S E B | | +----| |----+ |
| 9 N 9 | | | +----------------+ | |
| 0 M 0 | | | | |
| T N | | |<------ FDDI ring ------>| |
| L A | | | | |
+-----------+ | | +----------------+ | |
| | | DECconcentrator| | | | |
| +-----| 5xx |---+ |
+-------| |-----+
+----------------+
| | |
FDDI-----> | | |
| | |
V V V
A A A
X X X
4 4 4
0 0 0
0 0 0
0 0 0
M M M
9 9 9
0 0 0
| | |
| | |
| | |
|--------------------------------|
|
Hub "B" | Thinwire Ethernet "B"
+-----------+
| D |
| B |
| 9 |
| 0 |
+-----------+
The VAXstation 4000 Model 90s are all Routing Nodes
---------------------------------------------------
Problem:-
---------
From any VAXstation 4000 when we connect to the DECbridge 90 in Hub "B"
via NCP via Ethernet we get the DECbridge prompt and we can do all the DECbridge
commands even "show bridge" and "show port" etc. No problem at all.
But from any VAXstation when we connect to the DECbridge in Hub "A" via
NCP via FDDI we get the DECbridge prompt. So far so good. But when we do a
command such as "show bridge" or "show port" (basically commands that produce
about a 1 page response, only about � page is displayed, the output hangs
for several seconds, then the TARGET DOES NOT RESPOND message is displayed and
the user is returned to the NCP> prompt. If we try to do another connect to the
bridge again via NCP via FDDI immediately we get the message "Console already in
use." If we try after a few minutes then again we get the DEcbridge prompt. Any
command that produces a short response works fine. The DECbridge from Hubs A
and B have been swapped and we get the same result. The DENMA (DECAgent 90) has
been removed from Hub "A" and we still get the same result. The interesting
fact is user traffic via FDDI has no problem according to the customer. Also
connecting via NCP via FDDI to the DS90TL in Hub "A" and typing DS90TL server
commands works fine as well. The version of the DEcbridge 90s FPROM is 3.0.
I am about to trace the Thinwire Ethernet "A" to narrow down the problem
while doing a "show bridge" when connected via FDDI and compare the trace on
Ethernet "B" when doing the same command when connected via Ethernet.
Has anyone else seen this symptom.
Alphonse
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 938.1 | set host? | BRAT::BUKOWSKI | Thu Apr 22 1993 11:19 | 5 | |
This probably isn't any help, but I seen similar results connecting to
terminal servers in the past. It only happened when we tried to
connect to the server from a system that we connect to via set host.
Mike
| |||||