There ought to be nothing special. Examine carefully the place where TR
"has a crossing" to Eth. TR is using larger MTU (4200 bytes by default,
max 17000+something).
- IP packet reassembly might have problems on TSM server side (IP packets
on 4200-byte TR frames will be fragmented to 1500-byte Eth frames).
- Some of TR hosts might have larger (max) MTU than others. Try to isolate
are errors originating from specific hosts.
What is the device for "crossing" TR to Eth?

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To:     ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:        Token Ring Network

Hi Everybody,

I experience a lot of TCPIP Errors while backups and archives are in
progress. Most of the clients (os/2, 3.7.2.26) are connected via a token
ring network which has a crossing to ethernet. The TSM Server has only an
ethernet interface. Does anyone has experience with such an environment?
Are there special values for the tcpip options using token ring (e.g
tcpwindowsize, tcpbuffsize).

Hints are welcome!

Sincerly

Dr. Ulrich May
GE CompuNet Hamburg
Enterprise Computing Solutions
Ost- West Strasse 49, 20457 Hamburg, Germany
Phone: +49 (0)40-30053-0, Fax: +49 (0)40-30053-330,
E-Mail : Ulrich.May AT gecits-eu DOT com
Visit us on the Internet: http://www.gecits-eu.com


This email is confidential. If you are not the intended recipient,
you must not disclose or use the information contained in it.
If you have received this mail in error, please tell us
immediately by return email and delete the document.