Forgive me for not quoting exactly, but I'm on digest and the listserv
archives at marist.edu seem unavailable right now.
Neale pointed out that MFS is not the same as MTU. That is in fact
what was causing linux to refuse my MTU of 16k and use 8k. Thanks Neale!
And, Romney pointed out that LARGEENVELOPEPOOLSIZE needed to be
increased from the default of 8192. Although this didn't appear
to be affecting the response from NETSTAT GATE, it was what was
keeping FTP between VM and Linux from working. Thanks Romney!
Now, one more question! In the TCP/IP P&C manual, p.508 lists
some recommended MTU sizes for various types of interfaces. What's
a good MTU size for guest lan? (our primary app at this point
is apache webserving).
Marcy Cortes
Wells Fargo Services Company
*** Forwarding note from MARCY --EMINFO 02/12/02 11:33 ***
To: Linux 390 List <[EMAIL PROTECTED]>
FROM: Marcy Cortes
Subject: Re: SLES Beta and HiperSockets ? - now MTU size question
Thanks everyone for you help, esp. Jeremy. I got a fix from
Suse and now VM Guest LAN is working just fine.
Question about MTU sizes, though. I let MFS default to 16k
on the CP DEFINE LAN command. And so, in z/VM's MPROUTE CONFIG
I specified an MTU size of 16384 and in Linux's /etc/rc.config
I specified an MTU of 16384 as well. When I issue an
ifconfig from linux, I see the MTU size is 8192. Is that the max?
Should I go back and change the DEFINE LAN command and
the MPROUTE config to match?
ifconfig
hsi0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:10.12.7.2 Mask:255.255.255.128
inet6 addr: fe80::200:ff:fe00:0/10 Scope:Link
UP RUNNING NOARP MTU:8192 Metric:1
RX packets:219 errors:0 dropped:0 overruns:0 frame:0
TX packets:217 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:9969 (9.7 Kb) TX bytes:27025 (26.3 Kb)
Interrupt:11
Marcy Cortes
Wells Fargo Services Company
VM Systems Programming
