| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2508.1 | Your question has been forwarded...stay tuned | NETCAD::BATTERSBY | | Thu Jul 13 1995 13:39 | 4 |
| I've extracted and have forwarded your note to someone who
may be able to provide an answer....stay tuned.
Bob
|
| 2508.2 | Having Problem with AppleTalk as well.... | GIDDAY::CHONG | Andrew Chong - Sydney CSC | Thu Jul 13 1995 19:29 | 25 |
| thanks Bob, the same site is having problem passing AppleTalk through the
DECswitch900EF as well. IP seens to have no problems.
Configuration:
DECswitch900EF (standalone unit) , FDDI port A connected to S port
on the Ultrix Server.
All the ethernet ports are utilized ( 2 AUI, 4 10baseT).
Appletalk PahseII.
Apple talk Traversed ethernet segments fine but Ultrix server on FDDI cannot
see any appleTalk traffic or RARP tarffic. When the Ultix was on the ethernet
it all worked fine.
This is a new DECswitch and there are no filters.
Any ideas ?
andrew
|
| 2508.3 | Non-transparent translation for Appletalk ? | GIDDAY::CHONG | Andrew Chong - Sydney CSC | Tue Jul 18 1995 02:38 | 13 |
|
Someone suggested that there could be a problem with translation of
Appletalk ARP packets (protocol id 80-F3) if it was in the ethernet
format to FDDI SNAP format with protocol id 00-00-F8-80-F3.
I am not sure what version firmware is on the DECswitch 900EF but
I would like to ask if this is a potential problem with the DECswitch ?
If so, is there a firmware version that fixes it ?
Would RARP packet translation fall into the same caegorary ?
andrew
|
| 2508.4 | RARP - Interoperability Problem ? | NETCAD::KRISHNA | | Tue Jul 18 1995 17:03 | 25 |
| Andrew,
Regarding both the problems - RARP and AppleTalk, has anybody
monitored the FDDI ring to see if these packets have been forwarded by
the bridge ?
In the case of RARP if the packets are making it through on FDDI, there
is a possibility that there is an interoperability problem. The RARP
packet has a Hardware Type field which is 1 for Ethernet and 6 for IEEE
802 Networks. Translation bridges do not change the hardware type when
they translate RARP or ARP packets to FDDI format. Because of the
problem of interoperabilty in a bridged environment, there is a RFC
(RFC1390) which specifies that stations on FDDI should use 1 as the
Hardware Type in ARP/RARP packets. If the Ultrix station is expecting a
6 then the packets could be dropped because of invalid information.
As far as AppleTalk goes, I have not heard of any problems in
translating AppleTalk I & II in all our released firmware versions.
RARP does not fall into the category of AppleTalk translation.
If the RARP/AppleTalk packets are not making it to FDDI, then there is
a problem with the bridge and we can try and isolate it.
Hope this helps,
Krishna
|
| 2508.5 | type field is "probably" correct | GIDDAY::CHONG | Andrew Chong - Sydney CSC | Tue Jul 18 1995 19:43 | 17 |
|
Krishna,
We do not have the tools to monitor the FDDI ring.
In the case of RARP, how can I find out if the the type field is 1 or
6 as I don't have any means of tracing the FDDI ? In any case this is
not a user controllable parameter. AS IP is working, I would expect
that ARP packets are getting through and therefore (by logical
deduction) I assume the type field should be correct.
I am organising a DECbridge600 to replace the DECswitch900EF just
to see if the Switch has a problem.
Thanks for your reply.
andrew
|