| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1646.1 | Protocol mismatch? | NETCAD::B_CRONIN | | Tue Nov 01 1994 18:24 | 14 |
|
The Raw 802.3 switch will only apply to transfers to/from the FDDI,
so it won't affect this problem (unfortunately!)
If the systems are placed on the same wire will they communicate?
That might rule the bridge in/out.
If that can't be done, what are the default protocol types being used
on each system? There are usually two choices - Raw 802.3 and Ethernet.
If one is Raw 802.3, and the other is Ethernet, they won't talk to each
other until one of them is changed. We always suggest that the
change be made so that both use Ethernet format (type will be 81-37).
|
| 1646.2 | More info and firmware questions | CUJO::HILL | Dan Hill-NetConsultant-Denver-553-3624 | Tue Nov 01 1994 20:43 | 22 |
| Thanks for the quick response.
It seems that the customer was indeed trying to go from FDDI to
Ethernet. HUBwatch management station was plugged into DECconcentrator
900MX, across the backplane to DECswitch 900EF (DEFBA), out Ethernet to
server.
They have also tried FDDI-to-FDDI on DC900MX and Ethernet-to-Ethernet
thru the DECswitch 900EF. Neither works.
The customer is in the process of putting the NT system and the Novell
server on the same Ethernet segment to test.
By the way, firmware is as follows:
HW ROM SW
DECswitch 900EF 0/2 0.2 1.2.4
DECconc 900MX 1 1.0 2.8.0
Is there anything in these revs that may cause a problem?
Thanks,
Dan
|
| 1646.3 | 3 problems in one | NETCAD::B_CRONIN | | Wed Nov 02 1994 09:23 | 16 |
| It looks like there are three different problems here.
1) Enet to Enet doesn't work
2) FDDI to FDDI doesn't work
3) FDDI to Enet doesn't work
Checking out enet to enet without the bridge in the middle is the correct
first step. Assuming that works, then enet to enet bridging is the next
thing to look at. But, they probably want to fix it, not study it(!),
so my next question is "what is the final config or configs supposed to
look like?
Do you know whose FDDI adapter are being used - that may have a bearing
once we get to testing the FDDI.
|
| 1646.4 | Upgrade the DECswitch 900EF to 1.4.0 | NETCAD::BATTERSBY | | Wed Nov 02 1994 10:07 | 11 |
| HW ROM SW
>> DECswitch 900EF 0/2 0.2 1.2.4
Dan, I'd like to see the DECswitch 900EF upgraded to 1.4.0 SW
This would allow taking advantage of the features in the latest
release of the 9000EF SW (of course this ideally should be coupled
with the latest Multiswitch backplane SW rev release & HUBwatch
SW release). There were a bunch of things fixed (reading from the
1.4.0 release notes), which exist as bugs in the 1.2.4 rev.
Bob
|
| 1646.5 | Here is the configuration. | CUJO::HILL | Dan Hill-NetConsultant-Denver-553-3624 | Wed Nov 02 1994 10:58 | 51 |
| The configuration looks like this:
DEChub900
+-----+-----+-----+ +-------------+
NovServ3====|1 D | D | D A|===========|B |
| C | R | Sw | | Wellfleet +----WAN-->
| 9 | 9 | 9 B|===========|A |
NovServ4====|2 0 | 0 | 0 | +-------------+
NovServ5====|3 0 | C+ | 0 |
|4 M +---|-+ E | +----------+ Alpha w/ Turbo EISA
|5 X | | | F | UTP | | This system is
| | | | 5--------| W-NTSys | Running Beam &
HUBwMGR=====|6 | | | | | IP,IPX, | Whiteside Multi-
+-----+ | +-----+ | No NWLink| Connect supporting
| +----------+ Novell 3.11, 3.12,
+NovServ1 and 3.4?
| Note: This system
+NovClient1 serves Vice
| Presidents of
+NovClient2 MCI & it
| -PCs with 3COM doesn't work.
+ EtherLink III
NICs
Additional Info:
Customer has verified that the configuration works just fine when
not going through DECswitch 900EF, that is, when nodes are on same
Ethernet.
HUBwatch configuration summaries for modules:
Module CF-State LAN/FDDI Ligo Type
-------- ---------- ---------- -----------
DC900MX Thru FDDI_LAN1 Trunk-A
DSw900EF Thru FDDI_LAN1 Trunk-B (See NOTE)
DR90C n/a ThinWire
NOTE:
*Don't center too much on the FDDI configuration since the problem is
with Ethernet-to-Ethernet, but I am curious about the CF-state.
-Port 7 on backplane of DC900MX (Trunk-A)
-Port B on DSw900EF is on Backplane, so front panel connection to port-B
is not active, therefore, ring is wrapped.
-Port 6 on DC900MX is effectively a Master port.
CF-state = Thru is supposed to indicate a fully self-contained
ring, but it doesn't appear that way.
|
| 1646.6 | | NETCAD::ANIL | | Wed Nov 02 1994 18:40 | 19 |
| > Note: This system
> serves Vice
> Presidents of
> MCI & it
> doesn't work.
In that case you're all set.. they'd probably never know the difference.
(sorry, couldn't resist :-)
In going from one Ethernet to another, the switch will do
nothing to prevent a packet from going through unless there was a
physical level error, or there was a protocol or address filter.
Your initial note mentions the address filters, you might also check
the protocol window. (There's no default filter for IPX, but just in
case someone was experimenting with the filters.) If this is not
the case, I would put an Ethernet analyzer on both the input and
output LAN, and find out exactly which packets were getting dropped.
Anil
|
| 1646.7 | Windows-NT, Beam&Whiteside Multiconnect, & FDDI setup. | CUJO::HILL | Dan Hill-NetConsultant-Denver-553-3624 | Fri Nov 04 1994 10:10 | 33 |
| This problem is still being worked; however, the customer discovered a
problem in starting up B&W Multiconnect using an FDDI adapter. These
steps should be followed when moving from Ethernet to FDDI in order to
get FDDI to work:
NOTE: The same procedure would be
followed if you had a Token
Ring adapter instead of
Ethernet NIC.
1. UNBIND the B&W Multiconnect driver in W-NT from the Ethernet NIC.
2. DISABLE the Ethernet NIC.
3. Shutdown the W-NT system and remove the Ethernet NIC.
4. Install the FDDI adapter.
5. In EISA CONFIG (CF on the Boot Disk), load the FDDI drivers into
memory to control the FDDI adapter.
6. Reboot the machine and bring up W-NT.
7. Load Beam & Whiteside and BIND the driver to get FDDI to work.
***Another helpful hint involves setting the VIDEO CARD to NOWAIT.
If you don't, and it is on the same bus as the FDDI adapter,
the system will crash.
((More info to follow regarding the continuing saga of IPX over the
DEFBA.))
-Dan
|