Hipersockets...again
Did you apply the may-2002 patches form SuSE7 and update the
/etc/modules ???
|+-
|| Ketchens, LeMarr T. |
|| (RyTull) |
|| LeMarr.Ketchens@ryerso
:
|
| Subject: Guest LAN using Virtual Hipersockets...again
|
---|
Okay, I'm still having issues
Okay, I'm still having issues with the Guest LAN using Virtual Hipersockets.
Below is what I have coded for the Linux Master. I can get to the machine
using the VCTC, but I can not get to the machine via Virtual Hipersockets.
I can get to the 10.22.25 subnet from the VCTC connection
Thornton [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 28, 2003 7:53 PM
To: [EMAIL PROTECTED]
Subject: Re: z/VM Linux Guests using Hipersockets
On Tue, Jan 28, 2003 at 05:37:08PM -0600, Ketchens, LeMarr T. (RyTull)
wrote:
For some reason, we can not get our HiperSockets to work. We
ARP uses an Ethernet broadcast. This is very different from an IP broadcast.
-Original Message-
From: Steven Adams [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 28, 2003 5:37 PM
To: [EMAIL PROTECTED]
Subject: Another z/VM Linux Guests using Hipersockets Question
On Tuesday 28
For some reason, we can not get our HiperSockets to work. We are trying to
use virtual hipersockets, but I was wondering if it would be better to use
actual Physical HiperSockets. I really need some help. From examples
within the PROFILE TCPIP (DEVICE LINK, HOME and GATEWAY) to the IFCONFIGs
On Tue, Jan 28, 2003 at 05:37:08PM -0600, Ketchens, LeMarr T. (RyTull)
wrote:
For some reason, we can not get our HiperSockets to work. We are trying to
use virtual hipersockets, but I was wondering if it would be better to use
actual Physical HiperSockets. I really need some help. From
On Tuesday 28 January 2003 17:52, you wrote:
On Tue, Jan 28, 2003 at 05:37:08PM -0600, Ketchens, LeMarr T. (RyTull)
wrote:
For some reason, we can not get our HiperSockets to work. We are trying
to use virtual hipersockets, but I was wondering if it would be better to
use actual Physical
We have not gotten to the point of implementing Hipersockets yet but we are
planning to. In reading about them, I ran into a list of will not do's. In
that list was IP broadcast traffic, an ARP requirement. Is this still the
case? If not, can someone please tell me the appropriate redbook(s
Hi Brian,
I think your interface drivers are configured properly. You have defined a
HiperSockets NIC and you are using the hsi0 interface. HiperSockets does
not require a portname, and does not care if you provide one, so don't
worry
about that part.
Your IP address is visible on the LAN
Hi
I have been attempting to install SLES8, for s/390 using hipersockets
support to a guest LAN and can't get the network to work. I have tried
beta-6 and rc-6. I can never get the gateway address to ping, resulting
in an install failure. I have the same problem when I try and
ifconfig
On Wednesday 15 January 2003 15:20, you wrote:
Here is my Linux config:
ifconfig
hsi0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:129.80.45.226 Mask:255.255.255.224
inet6 addr: fe80::200:ff:fe00:0/10 Scope:Link
UP RUNNING NOARP MTU:8192
defined a
HiperSockets Guest LAN on z/VM 4.3 (DEFINE LAN xxx HIPER), the option you
will use is the one James mentioned.
Regardless, the installation system contains the required drivers. It is
when installing Red Hat that special action needs to be taken to include
the qeth.o driver.
+++ (end
PROTECTED]
cc:
Subject:[LINUX-390] HiperSockets and Guest LAN
Hi
I'm having problems setting getting my qeth interface to work running on a
virgin 2.4.19 kernel patched with the may 2002 stream.
I suspect that it might be a problem with chandev and syntax, and I have
been screwing around
on 11/29/2002 08:31:00
AM
Please respond to Linux on 390 Port [EMAIL PROTECTED]
Sent by:Linux on 390 Port [EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc:
Subject:[LINUX-390] HiperSockets and Guest LAN
Hi
I'm having problems setting getting my qeth interface to work running
Jxrgen Birkhaug writes:
Thanks Malcolm. I checked my chandev.conf and it did contain the
underscore. I probably messed up my orginal post.
I have now defined a new hipersocket and when trying to initialize it I get:
-
qeth: Trying to use card with devnos 0x963/0x964/0x965
qeth:
Hi...
It appears that your adapters (NIC) are defined properly and coupled to the
LAN that you want. I would suggest, however, that you ask the owner of
your
CP system to install the following service to z/VM 4.2.0 :
CP APAR VM62938 PTF UM30225 which includes HiperSockets enablement
We
Why?
--
Hilsen/regards
Jxrgen Birkhaug
Quoting Malcolm Beattie [EMAIL PROTECTED]:
s
Better make that triple of device numbers start on an even boundary.
--Malcolm
s
read device. On the other hand, it may be simpler
just to enforce the even boundary constraint, if only to avoid
having those permuted device numbers appearing.
I guess that there may even be other differences since this time
you're using a hipersockets device instead of a qdio one and it'll
have
the devices presented by chandev so that they match
the odd-even restriction
(just juggling the devices around until we have something reasonable).
Maybe we should adapt the
messages...
Btw.: Which oco-Level is this? (dmesg | grep Revis) We don't do the
reordering for HiperSockets in
recent levels since
Malcolm
Ok - I've ditched the uneven device and reverted back to an even boundary.
z/VM now sees the following *after* trying to initialize the qeth module:
Q NIC DETAILS
Adapter 0960 Type: HIPER Name: UNASSIGNED Devices: 3
Port 0 MAC: 00-04-AC-00-00-0E LAN: SYSTEM LNXLAN02
with odd addresses. See my reply
to Malcolm for more details.
--
Hilsen/regards
Jxrgen Birkhaug
Quoting Cornelia Huck [EMAIL PROTECTED]:
...
Btw.: Which oco-Level is this? (dmesg | grep Revis) We don't do the
reordering for HiperSockets in
recent levels since they seem to be fine for odd addresses.
...
Jxrgen Birkhaug writes:
Ok - I've ditched the uneven device and reverted back to an even boundary.
z/VM now sees the following *after* trying to initialize the qeth module:
Q NIC DETAILS
Adapter 0960 Type: HIPER Name: UNASSIGNED Devices: 3
Port 0 MAC: 00-04-AC-00-00-0E
Hi...
The even/odd starting address may cause you some problems depending
on the combination of CP HiperSockets and device driver support. It is
safer
to stick with an even-numbered starting address when you define the NIC.
With the latest CP and the latest device drivers this should work either
Malcolm - I'm currently offline from the linux site, but I will post the
information tomorrow morning. Also, Dennis' last post does suggest that I am
missing some software at the z/VM level.
BTW: the linux guests are set up with RedHat 7.2 with a virgin 2.4.19 kernel
from kernel.org patched with
Hi
I'm having problems setting getting my qeth interface to work running on a
virgin 2.4.19 kernel patched with the may 2002 stream.
I suspect that it might be a problem with chandev and syntax, and I have
been screwing around with chandev for some time but to no avail.
insmod qeth returns:
Hi...
You mention 'routed' in your network, but I believe the routed application
uses multicast or broadcast to exchange routing information. If you are
running z/VM 4.2.0 HiperSockets it will not support multicast.
If you are using z/VM 4.3.0 the HiperSockets simulation supports multicast
]
Subject: Re: HiperSockets
Can I assume it's the couple command that bind/joint the guest
LAN???
I started define the GuestLAN (virtual HiperSockets) by:
- cp define lan ownerid system
on the TCPIP userid:
- cp define nic a000 - - cp couple a000 system
The TCPIP is the router. My problem is that the LINUX and TCPIP are
not talking to each
Can I assume it's the couple command that bind/joint the guest
LAN???
On Mon, Aug 26, 2002 at 11:44:41AM -0400, Post, Mark K wrote:
I would say no. The CP COUPLE command is used to connect a virtual CTC to
another VM guest. It has nothing to do with guest LANs (that I'm aware of).
It's also how you couple virtual NICs to guest lans.
CP DEF NIC ADDR
CP COUPLE
Then, what is the difference between coupling to a ownerid
is SYSTEM -vs- VMuserid.
Should I have my Owneridto TCPIP
(GuestLAN) Stack
CTC
Host(linux01) 192.168.138.202
|192.168.138.201
: HiperSockets
On Mon, Aug 26, 2002 at 11:44:41AM -0400, Post, Mark K wrote:
I would say no. The CP COUPLE command is used to connect a virtual CTC to
another VM guest. It has nothing to do with guest LANs (that I'm aware
of).
It's also how you couple virtual NICs to guest lans.
CP DEF NIC ADDR
CP
Hi...
SYSTEM-owned LAN verses user-owned LAN --
When the LAN owner is defined as SYSTEM, you have to
have a Class B userid to modify the LAN or DETACH it.
A Guest LAN owned by SYSTEM will persist even if all
members have signed off or uncoupled from the LAN.
When the LAN owner is a user on the
: [LINUX-390] HiperSockets
I started define the GuestLAN (virtual HiperSockets) by:
- cp define lan ownerid system
on the TCPIP userid:
- cp define nic a000 - - cp couple a000 system
The TCPIP is the router. My problem is that the LINUX and TCPIP
I use the Ping command from VM and LINUX. I am running ROUTED with ETC
GATEWAYS.
NET 192.168.138.0 Gateway 192.168.138.201 Metric 1 permanent mask
255.255.255.0
Two Home address:
192.168.138.201(GuestLAN side) and
192.159.81.14(CTC) to the outside
On Wednesday, 08/21/2002 at 08:41 PDT, Marcy Cortes [EMAIL PROTECTED]
wrote:
Uh, you'd better make those Name:'s match.
Marcy, the names only have to match when using a virtual (or real) NIC
which is shared by multiple hosts. In this case, each guest has its own
dedicated NIC, all of which can
Uh, you'd better make those Name:'s match.
Marcy Cortes
Wells Fargo Services Co
Eddie wrote:
I am getting folling message when I started TCPIP:
AUTO LOGON *** ROUTED USERS = 17
17:25:11 DTCQDI001I QDIO device HIPERDEC device number A002:
17:25:11 DTCQDI007I
I am getting folling message when I started TCPIP:
AUTO LOGON *** ROUTED USERS = 17
17:25:11 DTCQDI001I QDIO device HIPERDEC device number A002:
17:25:11 DTCQDI007I Enabled for QDIO data transfers
17:25:11 DTCOSD246I HIPERS device HIPERDEC: Assigned IP address
I've got a situation where I've got a Linux guest owning an OSA-GigE,
with (virtual) HiperSockets networks routed behind him.
Ping times to the HiperSockets guests are effectively instantaneous.
If I ssh to the guest with the Gig-E and then SSH to the guests behind
him, *that* interaction
Adam,
Don't see your problem but we use a mix of z/OS and Linux (SuSE 2.4.17) so
can't exactly match your config.
A few basic questions:
The Linux guest that owns the OSA - does this mean the OSA is not shared
at all, and/or have you defined it as PRI router?
Are the Hipersockets addresses
10.32.81.255 netmask 255.255.255.0 up
IFCONFIG_2=10.32.82.10 broadcast 10.32.82.255 netmask 255.255.255.0 mtu 8992 up
IFCONFIG_3=10.32.90.140 broadcast 10.32.90.255 netmask 255.255.255.0 up
To find IBM's redbook on hipersockets, go to http://www.ibm/com and search for
redbooks
:
- Recommended OCO-modules (qdio and qeth) with HiperSockets bug-fix.
- Important tool-chain fixes for the 64-bit undefined weak external bug
affecting glibc and binutils.
- Bug-fixes for glibc 2.2.4 and 2.2.5.
Happy downloading !
Mit freundlichen Gruessen / Kind regards,
Axel Wirbser
was:
* Hipersockets do not work under VM.
(2) Is http://support.suse.de/psdb/ the SuSE Maintenance site
that you (Jeremy) are talking about?
- We obtained it from:
http://sdb.suse.de/en/psdb/html/8152e93d07ceccd026588a64d988a0f1.html
(3)
You need to have purchased support from
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
]
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
fixes to z/VM CP and z/VM TCPIP.
There *was* a recent
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
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
On Tuesday, 02/12/2002 at 01:42 PST, Marcy Cortes [EMAIL PROTECTED]
wrote:
Now, one more question! In the TCP/IP PC 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:
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
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
and HiperSockets ?
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
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:
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
0.255.255.0 0.105.1.0
QDIO1
Dennis Musselwhite [EMAIL PROTECTED]@VM.MARIST.EDU on 01/31/2002
00:19:51
Please respond to Linux on 390 Port [EMAIL PROTECTED]
Sent by: Linux on 390 Port [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: QETH/HiperSockets/Guest Lan.Save me from jumping
, but
the MACADDR is not very meaningful to real HiperSockets. All of the
LPARs communicating on a HiperSockets CHPID are (sort of) on the same
adapter. The HiperSockets adapter uses the Destination IP Address to
deliver packets.
We are manually configuring the device in chandev.
Our chandev.conf
Has anyone done this?
I have an initrd built with the OCO modules and z/VM at the appropriate
level to use HiperSockets (many of my other Linux guests are doing so).
I think I must modify the /linuxrc to get it to believe that
HiperSockets are the right thing, and additionally do something like
Both z/VM 4.2 Hipersockets PTFs (UM30225 for CP and UQ61461 for TCP/IP) are COR
closed and available for ordering.
Best Regards,
Les Geer
IBM z/VM and Linux Development
401 - 458 of 458 matches
Mail list logo
