90 Port <[EMAIL PROTECTED]>
To:[EMAIL PROTECTED]
cc:
Subject: Re: [LINUX-390] SLES Beta and Hipersockets ?
Philip J. Tully wrote:
>1. As I understand it the changes were made to the drivers. These
>drivers worked in an LPAR but not under VM, that's why there were also
>
Thanks Jeremy,
(1) Since SuSE mentioned HiperSockets in the write-up, this would probably
show up in a search of their support database. I could not find it
earlier,
but maybe that's because I don't have access to the official product
support
site.
(2) I'm going to guess that support.suse.de/ps
1. As I understand it the changes were made to the drivers. These
drivers worked in an LPAR but not under VM, that's why there were also
fixes to z/VM CP and z/VM TCPIP.
regards
Phil Tully
Dennis Musselwhite wrote:
>
> Hi...
>
> Jeremy wrote:
> >We had the EXACT same problem. SUSE has maintena
nux on 390 Port <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: SLES Beta and Hipersockets ?
Hi...
Jeremy wrote:
>We had the EXACT same problem. SUSE has maintenace for SLES7
>
>Applied RPM's to fix problem
Hi...
Jeremy wrote:
>We had the EXACT same problem. SUSE has maintenace for SLES7
>
>Applied RPM's to fix problems with Guest LAN k_deflt.rpm &
>kernel-source.rpm obtained from SUSE maintenance site.
>
>And this fixed all of our guest lan issues.
and later Marcy wrote that this resolved her pro
Marcy:
I would add the word "enough" after "large" in Alan's first comment. It
makes no difference if your MTU is 1500 bytes or 56K bytes if the longest
packet you send is 500 bytes.
Romney
On Tue, 12 Feb 2002 17:29:48 -0500 Alan Altmark said:
>On Tuesday, 02/12/2002 at 01:42 PST, Marcy Cortes
On Tuesday, 02/12/2002 at 01:42 PST, Marcy Cortes <[EMAIL PROTECTED]>
wrote:
> 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 webservi
MAIL 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 co
Marcy:
The MTU size allowed is limited by the large envelope size. Try changing
your LargeEnvelopePoolSize specification.
Romney
On Tue, 12 Feb 2002 11:33:39 PST Marcy Cortes said:
>Thanks everyone for you help, esp. Jeremy. I got a fix from
>Suse and now VM Guest LAN is working just fine.
>
>
Don't mix up framesize with MTU. For 16K framesize MTU is 8K. For 24K MTU is
16K etc.
> -Original Message-
> 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 /et
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
Hi,
I would guess that your qdio and qeth drivers are working OK, but the stack
does not recognize
that it should use this particular interface to reach the RedHat systems
you are trying to ping.
Adam Thornton wrote:
>I'm trying to load the SLES beta on a virtual machine on a HiperSockets
>netwo
On Sat, Feb 09, 2002 at 06:13:41PM -0500, Post, Mark K wrote:
> I haven't tried yet, but one thing you didn't mention is what your routing
> table looks like. Does that look OK also?
Looks fine. 10.90.3.5 is the SLES machine. 10.90.3.4 is RH. 10.90.3.1
is default router. 24-bit netmask: 255.
Adam,
I haven't tried yet, but one thing you didn't mention is what your routing
table looks like. Does that look OK also?
Mark Post
-Original Message-
From: Adam Thornton [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 6:15 PM
To: [EMAIL PROTECTED]
Subject: SLE
I'm trying to load the SLES beta on a virtual machine on a HiperSockets
network.
It's working fine for the RH beta on the same subnet--both my router
machine and the red hat machine can see each other fine.
Q NIC DETAILS shows all three machines, with their proper IP addresses.
hsi0 came up fin
15 matches
Mail list logo
