Re: Hipersockets - What Kernal level is required to s upport/use?
> TO : > #include <<< #ifdef MVS /[EMAIL PROTECTED]/ > #pragma comment(copyright,"GFSCWLOUHDZ11TC ") > #pragma options(RENT) > #pragma strings(readonly) > #pragma csect(CODE,"GFSCWLOU") > > #include > /*#include */ << #include "gfscwmnt.h" > #else > #include > #include "gfsawmnt.h" > #endif > > Is this change advisable Yes. Be sure to report it to IBM officially, as this code is part of the NFS product and should work w/o having to hack it. -- db
Re: Hipersockets - What Kernal level is required to s upport/use?
No problem. It saves me from having the same thing happen. It's all good. |-+> | | "Kubannek, | | | Harold" | | | <[EMAIL PROTECTED]| | | ower.com>| | | Sent by: Linux on| | | 390 Port | | | <[EMAIL PROTECTED]| | | IST.EDU> | | || | || | | 02/06/2004 10:41 | | | AM | | | Please respond to| | | Linux on 390 Port| | || |-+> >--| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Re: Hipersockets - What Kernal level is required to s upport/use? | >--| Thanks Mark, Neale, mvslogin and mvslogout seem to be working as advertised, now. James, sorry to have side tracked the thread. Thanks --Harold -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Friday, February 06, 2004 09:35 To: [EMAIL PROTECTED] Subject: Re: Hipersockets - What Kernal level is required to s upport/use? I would say so. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Kubannek, Harold Sent: Friday, February 06, 2004 11:28 AM To: [EMAIL PROTECTED] Subject: Re: Hipersockets - What Kernal level is required to s upport/use? Making the following changes in gfsawlin.c and gfsawlou.c allowed the 'make' to work. CHANGING : #ifdef MVS /[EMAIL PROTECTED]/ #pragma comment(copyright,"GFSCWLOUHDZ11TC ") #pragma options(RENT) #pragma strings(readonly) #pragma csect(CODE,"GFSCWLOU") #include #include #include "gfscwmnt.h" #else #include #include "gfsawmnt.h" #endif TO : #include <<<<<<< /*#include */ <<<<<< #include "gfsawmnt.h" #endif Is this change advisable --Harold -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Friday, February 06, 2004 09:22 To: [EMAIL PROTECTED] Subject: Re: Hipersockets - What Kernal level is required to s upport/use? Most likely. That's a change that crept in with later versions of gcc/glibc, so I'm not surprised that IBM hasn't updated their code yet. I've run into it with a number of packages I've compiled myself. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Ferguson, Neale Sent: Friday, February 06, 2004 10:50 AM To: [EMAIL PROTECTED] Subject: Re: Hipersockets - What Kernal level is required to s upport/use? Is there a "#include " missing from gfsawlin.c perhaps? -Original Message- gfsawlin.o(.text+0x74): In function `main': : undefined reference to `errno' collect2: ld returned 1 exit status make: *** [mvslogin] Error 1 This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. A1. [INFO] -- Access Manager: This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. A2
Re: Hipersockets - What Kernal level is required to s upport/use?
Thanks Mark, Neale, mvslogin and mvslogout seem to be working as advertised, now. James, sorry to have side tracked the thread. Thanks --Harold -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Friday, February 06, 2004 09:35 To: [EMAIL PROTECTED] Subject: Re: Hipersockets - What Kernal level is required to s upport/use? I would say so. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Kubannek, Harold Sent: Friday, February 06, 2004 11:28 AM To: [EMAIL PROTECTED] Subject: Re: Hipersockets - What Kernal level is required to s upport/use? Making the following changes in gfsawlin.c and gfsawlou.c allowed the 'make' to work. CHANGING : #ifdef MVS /[EMAIL PROTECTED]/ #pragma comment(copyright,"GFSCWLOUHDZ11TC ") #pragma options(RENT) #pragma strings(readonly) #pragma csect(CODE,"GFSCWLOU") #include #include #include "gfscwmnt.h" #else #include #include "gfsawmnt.h" #endif TO : #include <<<<<<< /*#include */ <<<<<< #include "gfsawmnt.h" #endif Is this change advisable --Harold -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Friday, February 06, 2004 09:22 To: [EMAIL PROTECTED] Subject: Re: Hipersockets - What Kernal level is required to s upport/use? Most likely. That's a change that crept in with later versions of gcc/glibc, so I'm not surprised that IBM hasn't updated their code yet. I've run into it with a number of packages I've compiled myself. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Ferguson, Neale Sent: Friday, February 06, 2004 10:50 AM To: [EMAIL PROTECTED] Subject: Re: Hipersockets - What Kernal level is required to s upport/use? Is there a "#include " missing from gfsawlin.c perhaps? -Original Message- gfsawlin.o(.text+0x74): In function `main': : undefined reference to `errno' collect2: ld returned 1 exit status make: *** [mvslogin] Error 1 This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. A1. [INFO] -- Access Manager: This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. A2
Re: Hipersockets - What Kernal level is required to s upport/use?
I would say so. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Kubannek, Harold Sent: Friday, February 06, 2004 11:28 AM To: [EMAIL PROTECTED] Subject: Re: Hipersockets - What Kernal level is required to s upport/use? Making the following changes in gfsawlin.c and gfsawlou.c allowed the 'make' to work. CHANGING : #ifdef MVS /[EMAIL PROTECTED]/ #pragma comment(copyright,"GFSCWLOUHDZ11TC ") #pragma options(RENT) #pragma strings(readonly) #pragma csect(CODE,"GFSCWLOU") #include #include #include "gfscwmnt.h" #else #include #include "gfsawmnt.h" #endif TO : #include <<<<<<< /*#include */ <<<<<< #include "gfsawmnt.h" #endif Is this change advisable --Harold -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Friday, February 06, 2004 09:22 To: [EMAIL PROTECTED] Subject: Re: Hipersockets - What Kernal level is required to s upport/use? Most likely. That's a change that crept in with later versions of gcc/glibc, so I'm not surprised that IBM hasn't updated their code yet. I've run into it with a number of packages I've compiled myself. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Ferguson, Neale Sent: Friday, February 06, 2004 10:50 AM To: [EMAIL PROTECTED] Subject: Re: Hipersockets - What Kernal level is required to s upport/use? Is there a "#include " missing from gfsawlin.c perhaps? -Original Message- gfsawlin.o(.text+0x74): In function `main': : undefined reference to `errno' collect2: ld returned 1 exit status make: *** [mvslogin] Error 1 This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. A1.
Re: Hipersockets - What Kernal level is required to support/use?
Yes. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of James Melin Sent: Friday, February 06, 2004 11:02 AM To: [EMAIL PROTECTED] Subject: Re: Hipersockets - What Kernal level is required to support/use? Does that apply to Linux in LPAR mode? |-+> | | "Post, Mark K" | | | <[EMAIL PROTECTED]| | | m> | | | Sent by: Linux on| | | 390 Port | | | <[EMAIL PROTECTED]| | | IST.EDU> | | || | || | | 02/06/2004 09:30 | | | AM | | | Please respond to| | | Linux on 390 Port| | || |-+> >--- ---| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Re: Hipersockets - What Kernal level is required to support/use? | >--- ---| James, You would set it up just like you would a Guest LAN using virtual HiperSockets. Look at http://linuxvm.org/Info/HOWTOs/guestlan.html and ignore the Guest LAN pieces. Any 2.4 kernel should support this. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of James Melin Sent: Friday, February 06, 2004 9:42 AM To: [EMAIL PROTECTED] Subject: Hipersockets - What Kernal level is required to support/use? Who has experience with setting up Linux to use hipersockets for data transfer to z/OS? I am looking at the disk-tape ackup solution that David Boyes came up with, and I believe that hipersockets would be the best route to go. Just not sure if we can go there.
Re: Hipersockets - What Kernal level is required to support/use?
Does that apply to Linux in LPAR mode? |-+> | | "Post, Mark K" | | | <[EMAIL PROTECTED]| | | m> | | | Sent by: Linux on| | | 390 Port | | | <[EMAIL PROTECTED]| | | IST.EDU> | | || | || | | 02/06/2004 09:30 | | | AM | | | Please respond to| | | Linux on 390 Port| | || |-+> >--| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Re: Hipersockets - What Kernal level is required to support/use? | >--| James, You would set it up just like you would a Guest LAN using virtual HiperSockets. Look at http://linuxvm.org/Info/HOWTOs/guestlan.html and ignore the Guest LAN pieces. Any 2.4 kernel should support this. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of James Melin Sent: Friday, February 06, 2004 9:42 AM To: [EMAIL PROTECTED] Subject: Hipersockets - What Kernal level is required to support/use? Who has experience with setting up Linux to use hipersockets for data transfer to z/OS? I am looking at the disk-tape ackup solution that David Boyes came up with, and I believe that hipersockets would be the best route to go. Just not sure if we can go there.
Re: Hipersockets - What Kernal level is required to s upport/use?
Making the following changes in gfsawlin.c and gfsawlou.c allowed the 'make' to work. CHANGING : #ifdef MVS /[EMAIL PROTECTED]/ #pragma comment(copyright,"GFSCWLOUHDZ11TC ") #pragma options(RENT) #pragma strings(readonly) #pragma csect(CODE,"GFSCWLOU") #include #include #include "gfscwmnt.h" #else #include #include "gfsawmnt.h" #endif TO : #include <<<<<<< /*#include */ <<<<<< #include "gfsawmnt.h" #endif Is this change advisable --Harold -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Friday, February 06, 2004 09:22 To: [EMAIL PROTECTED] Subject: Re: Hipersockets - What Kernal level is required to s upport/use? Most likely. That's a change that crept in with later versions of gcc/glibc, so I'm not surprised that IBM hasn't updated their code yet. I've run into it with a number of packages I've compiled myself. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Ferguson, Neale Sent: Friday, February 06, 2004 10:50 AM To: [EMAIL PROTECTED] Subject: Re: Hipersockets - What Kernal level is required to s upport/use? Is there a "#include " missing from gfsawlin.c perhaps? -Original Message- gfsawlin.o(.text+0x74): In function `main': : undefined reference to `errno' collect2: ld returned 1 exit status make: *** [mvslogin] Error 1 This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. A1.
Re: Hipersockets - What Kernal level is required to s upport/use?
Most likely. That's a change that crept in with later versions of gcc/glibc, so I'm not surprised that IBM hasn't updated their code yet. I've run into it with a number of packages I've compiled myself. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Ferguson, Neale Sent: Friday, February 06, 2004 10:50 AM To: [EMAIL PROTECTED] Subject: Re: Hipersockets - What Kernal level is required to s upport/use? Is there a "#include " missing from gfsawlin.c perhaps? -Original Message- gfsawlin.o(.text+0x74): In function `main': : undefined reference to `errno' collect2: ld returned 1 exit status make: *** [mvslogin] Error 1
Re: Hipersockets - What Kernal level is required to s upport/use?
sorry. you can't use that. sco property. > -Original Message- > From: Ferguson, Neale [mailto:[EMAIL PROTECTED] > Sent: Friday, February 06, 2004 9:50 AM > To: [EMAIL PROTECTED] > Subject: Re: Hipersockets - What Kernal level is required to s > upport/use? > > > Is there a "#include " missing from gfsawlin.c perhaps? > > -Original Message- > gfsawlin.o(.text+0x74): In function `main': > : undefined reference to `errno' > collect2: ld returned 1 exit status > make: *** [mvslogin] Error 1 >
Re: Hipersockets - What Kernal level is required to s upport/use?
Is there a "#include " missing from gfsawlin.c perhaps? -Original Message- gfsawlin.o(.text+0x74): In function `main': : undefined reference to `errno' collect2: ld returned 1 exit status make: *** [mvslogin] Error 1
Re: Hipersockets - What Kernal level is required to support/use?
Mark, on the "make" I get the following output : [EMAIL PROTECTED] mvs-client]# make cc -c -I. gfsawsha.c gfsawsha.c: In function `getsite_1': gfsawsha.c:641: warning: passing arg 3 of pointer to function from incompatible pointer type gfsawsha.c:641: warning: passing arg 4 of pointer to function from incompatible pointer type gfsawsha.c:641: warning: passing arg 5 of pointer to function from incompatible pointer type gfsawsha.c:641: warning: passing arg 6 of pointer to function from incompatible pointer type cc -c -I. gfsawaxd.c gfsawaxd.c: In function `xdr_rtnattr': gfsawaxd.c:231: warning: passing arg 4 of `xdr_pointer' from incompatible pointer type cc -o showattr gfsawsha.o gfsawaxd.o cc -c -I. gfsawlin.c cc -c -I. gfsawclt.c gfsawclt.c: In function `mvsnfsproc_login_1': gfsawclt.c:164: warning: passing arg 3 of pointer to function from incompatible pointer type gfsawclt.c:164: warning: passing arg 4 of pointer to function from incompatible pointer type gfsawclt.c:164: warning: passing arg 5 of pointer to function from incompatible pointer type gfsawclt.c:164: warning: passing arg 6 of pointer to function from incompatible pointer type gfsawclt.c: In function `mvsnfsproc_logout_1': gfsawclt.c:207: warning: passing arg 3 of pointer to function from incompatible pointer type gfsawclt.c:207: warning: passing arg 4 of pointer to function from incompatible pointer type gfsawclt.c:207: warning: passing arg 5 of pointer to function from incompatible pointer type gfsawclt.c:207: warning: passing arg 6 of pointer to function from incompatible pointer type cc -c -I. gfsawmcl.c cc -c -I. gfsawmou.c cc -o mvslogin gfsawlin.o gfsawclt.o gfsawmcl.o gfsawmou.o gfsawlin.o(.text+0x74): In function `main': : undefined reference to `errno' collect2: ld returned 1 exit status make: *** [mvslogin] Error 1 --Harold -Original Message- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Friday, February 06, 2004 08:31 To: [EMAIL PROTECTED] Subject: Re: Hipersockets - What Kernal level is required to support/use? Harold, I got them to compile with no problem on an Intel Linux system. What problems are you having? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Kubannek, Harold Sent: Friday, February 06, 2004 10:26 AM To: [EMAIL PROTECTED] Subject: Re: Hipersockets - What Kernal level is required to support/use? We are running Red Hat 7.2 with the 2.4.21 kernel (with the patches from the June Stream 2003 applied) and have been able to implement hipersockets with no problems - in preparation to test David's backup solution. If I can just get the mvslogin/mvslogout to compile on Linux!! Anyone been able to do this? --Harold -Original Message- From: James Melin [mailto:[EMAIL PROTECTED] Sent: Friday, February 06, 2004 07:42 To: [EMAIL PROTECTED] Subject: Hipersockets - What Kernal level is required to support/use? Who has experience with setting up Linux to use hipersockets for data transfer to z/OS? I am looking at the disk-tape ackup solution that David Boyes came up with, and I believe that hipersockets would be the best route to go. Just not sure if we can go there. This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. A1. This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. A1.
Re: Hipersockets - What Kernal level is required to support/use?
Harold, I got them to compile with no problem on an Intel Linux system. What problems are you having? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Kubannek, Harold Sent: Friday, February 06, 2004 10:26 AM To: [EMAIL PROTECTED] Subject: Re: Hipersockets - What Kernal level is required to support/use? We are running Red Hat 7.2 with the 2.4.21 kernel (with the patches from the June Stream 2003 applied) and have been able to implement hipersockets with no problems - in preparation to test David's backup solution. If I can just get the mvslogin/mvslogout to compile on Linux!! Anyone been able to do this? --Harold -Original Message- From: James Melin [mailto:[EMAIL PROTECTED] Sent: Friday, February 06, 2004 07:42 To: [EMAIL PROTECTED] Subject: Hipersockets - What Kernal level is required to support/use? Who has experience with setting up Linux to use hipersockets for data transfer to z/OS? I am looking at the disk-tape ackup solution that David Boyes came up with, and I believe that hipersockets would be the best route to go. Just not sure if we can go there. This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. A1.
Re: Hipersockets - What Kernal level is required to support/use?
James, You would set it up just like you would a Guest LAN using virtual HiperSockets. Look at http://linuxvm.org/Info/HOWTOs/guestlan.html and ignore the Guest LAN pieces. Any 2.4 kernel should support this. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of James Melin Sent: Friday, February 06, 2004 9:42 AM To: [EMAIL PROTECTED] Subject: Hipersockets - What Kernal level is required to support/use? Who has experience with setting up Linux to use hipersockets for data transfer to z/OS? I am looking at the disk-tape ackup solution that David Boyes came up with, and I believe that hipersockets would be the best route to go. Just not sure if we can go there.
Re: Hipersockets - What Kernal level is required to support/use?
We are running Red Hat 7.2 with the 2.4.21 kernel (with the patches from the June Stream 2003 applied) and have been able to implement hipersockets with no problems - in preparation to test David's backup solution. If I can just get the mvslogin/mvslogout to compile on Linux!! Anyone been able to do this? --Harold -Original Message- From: James Melin [mailto:[EMAIL PROTECTED] Sent: Friday, February 06, 2004 07:42 To: [EMAIL PROTECTED] Subject: Hipersockets - What Kernal level is required to support/use? Who has experience with setting up Linux to use hipersockets for data transfer to z/OS? I am looking at the disk-tape ackup solution that David Boyes came up with, and I believe that hipersockets would be the best route to go. Just not sure if we can go there. This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. A1.
Hipersockets - What Kernal level is required to support/use?
Who has experience with setting up Linux to use hipersockets for data transfer to z/OS? I am looking at the disk-tape ackup solution that David Boyes came up with, and I believe that hipersockets would be the best route to go. Just not sure if we can go there.
Re: Guest LAN using Virtual Hipersockets...again
Did you apply the may-2002 patches form SuSE7 and update the /etc/modules ??? |+-> || "Ketchens, LeMarr T. | || (RyTull)" | || | || Sent by: Linux on 390 | || Port | || <[EMAIL PROTECTED]| || u> | || | || | || 02/03/2003 10:07 PM| || Please respond to Linux| || on 390 Port| || | |+-> >---| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Guest LAN using Virtual Hipersockets...again | >---| 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, but that won't do. I need to find a way to get the working without the VCTC. It seems that my primary problem is on the Linux side, but I can not figure out why this will not work. Do I need to have a physical Hipersocket or physical connection via OSA-E to point to as the gateway for the Linux machines? Sorry for constantly returning, but I think I'm getting close with the help I've received thus far. __ L. Ketchens Technical Services MVS Systems Programmer [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> *** PROFILE TCPIP BEGIN *** ; OSA-E GIGABIT ETHERNET CARD ON z/800 CHPID DEVICE <mailto:DEV@0074> DEV@0074 OSD 0074 PORTNAME ZVMHOST PRIROUTER LINK ETH0 QDIOETHERNET <mailto:DEV@0074> DEV@0074 ; VIRTUAL HIPERSOCKETS 2000-2002 VHIP1 DEVICE VHIP1 HIPERS 2000 PORTNAME VIRTHIP1 AUTORESTART LINK VHIP1 QDIOIP VHIP1 ; VIRTUAL CHAN 2 CHAN 3000-3001 FOR LNXMSTR DEVICE VCTC09 CTC 3000 LINK VCTC09 CTC 0 VCTC09 ; VIRTUAL CHAN 2 CHAN 3002-3003 FOR LINUX11 DEVICE VCTC11 CTC 3002 LINK VCTC11 CTC 0 VCTC11 HOME 10.22.22.213 ETH0 10.22.25.1 VHIP1 10.22.22.213 VCTC09 10.22.22.213 VCTC11 GATEWAY 10 = ETH0 1500 0.255.0.0 0.22.0.0 10 = VHIP1 1500 0.255.255.00.22.25.0 10.22.25.9 = VCTC099216 HOST 10.22.25.11= VCTC119216 HOST DEFAULTNET 10.22.11.110 ETH0 1500 0 (REAL ROUTER) START <mailto:DEV@0074> DEV@0074 START VHIP1 START VCTC09 START VCTC11 *** PROFILE TCPIP END *** *** SYSTEM CONFIG BEGIN *** DEFINE LAN VIRTHIP1 MAXCONN INF OWNERID SYSTEM TYPE HIPER *** SYSTEM CONFIG END *** *** USER DIRECT BEGIN *** PROFILE LINDFLT IPL CMS MACH ESA 4 IUCV ANY IUCV ALLOW CPU 00 NODEDICATE CPU 01 NODEDICATE CPU 02 NODEDICATE CPU 03 NODEDICATE SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A CONSOLE 009 3215 T SPECIAL 2000 HIPER 3 SYSTEM VIRTHIP1 LINK MAINT 0190 0190 RR LINK MAINT 019D 019D RR LINK MAINT 019E 019E RR LINK TCPMAINT 0592 0592 RR * USER TCPIP TCPIP 64M 128M ABG INCLUDE TCPCMSU OPTION QUICKDSP SVMSTAT MAXCONN 1024 DIAG98 APPLMON SHARE RELATIVE 3000 IUCV ALLOW IUCV ANY PRIORITY IUCV *CCS PRIORITY MSGLIMIT 255 SPECIAL 2000 HIPER 3 SYSTEM VIRTHIP1 SPECIAL 3000 CTCA LNXMSTR SPECIAL 3001 CTCA LNXMSTR SPECIAL 3002 CTCA LINUX11 SPECIAL 3003 CTCA LINUX11 LINK TCPMAINT 591 591 RR LINK TCPMAINT 592 592 RR LINK TCPMAINT 198 198 RR MDISK 191 3390 0486 005 430W01 MR RPASS WPASS MPASS * USER LNXMSTR LNXMSTR 128M 512M G INCLUDE LINDFLT SPECIAL 3000 CTCA TCPIP SPECIAL 3001 CTCA TCPIP MDISK 191 3390 0560 0050 430W02 MR RPASS WPASS MPASS MDISK 100 3390 0001 3338 LNX001 MR RPASS WPASS MPASS MDISK 101 3390 0001 1669 LNX002 MR RPASS WPASS MPASS * USER LINUX11 LINUX11 512M 512M G INCLUDE LINDFLT SHARE REL 2500 SPECIAL 3002 CTCA TCPIP SPECIAL 3003 CTCA TCPIP MDISK 100 3390 0001 3338 LNX003 MR RPASS WPASS MPASS MDISK 101 3390 1670 1669 LNX002 MR RPASS WPASS MPASS MDISK 200 3390 0001 3338 LNX004 MR RPASS WPASS MPASS LINK LNXMSTR 191 191 RR * *** USER DIRECT
Re: Guest LAN using Virtual Hipersockets...again
Print out the routing tables of VM and linux... "query lan detail" and "active" |+-> || "Ketchens, LeMarr T. | || (RyTull)" | || | || Sent by: Linux on 390 | || Port | || <[EMAIL PROTECTED]| || u> | || | || | || 02/05/2003 03:47 PM| || Please respond to Linux| || on 390 Port| || | |+-> >---| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Re: Guest LAN using Virtual Hipersockets...again | >---| ryn-zvmlnx:~ # uname -a uname -a Linux ryn-zvmlnx 2.4.7-timer-SMP #1 SMP Tue May 21 12:58:16 GMT 2002 s390 unknown -Original Message- From: Eddie Chen [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 04, 2003 12:57 PM To: [EMAIL PROTECTED] Subject: Re: Guest LAN using Virtual Hipersockets...again Did you apply the may-2002 patches form SuSE7 and update the /etc/modules ??? |+-> || "Ketchens, LeMarr T. | || (RyTull)" | || | || Sent by: Linux on 390 | || Port | || <[EMAIL PROTECTED]| || u> | || | || | || 02/03/2003 10:07 PM| || Please respond to Linux| || on 390 Port| || | |+-> > --- | | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Guest LAN using Virtual Hipersockets...again | > --- ----| 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, but that won't do. I need to find a way to get the working without the VCTC. It seems that my primary problem is on the Linux side, but I can not figure out why this will not work. Do I need to have a physical Hipersocket or physical connection via OSA-E to point to as the gateway for the Linux machines? Sorry for constantly returning, but I think I'm getting close with the help I've received thus far. __ L. Ketchens Technical Services MVS Systems Programmer [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> *** PROFILE TCPIP BEGIN *** ; OSA-E GIGABIT ETHERNET CARD ON z/800 CHPID DEVICE <mailto:DEV@0074> DEV@0074 OSD 0074 PORTNAME ZVMHOST PRIROUTER LINK ETH0 QDIOETHERNET <mailto:DEV@0074> DEV@0074 ; VIRTUAL HIPERSOCKETS 2000-2002 VHIP1 DEVICE VHIP1 HIPERS 2000 PORTNAME VIRTHIP1 AUTORESTART LINK VHIP1 QDIOIP VHIP1 ; VIRTUAL CHAN 2 CHAN 3000-3001 FOR LNXMSTR DEVICE VCTC09 CTC 3000 LINK VCTC09 CTC 0 VCTC09 ; VIRTUAL CHAN 2 CHAN 3002-3003 FOR LINUX11 DEVICE VCTC11 CTC 3002 LINK VCTC11 CTC 0 VCTC11 HOME 10.22.22.213 ETH0 10.22.25.1 VHIP1 10.22.22.213 VCTC09 10.22.22.213 VCTC11 GATEWAY 10 = ETH0 1500 0.255.0.0 0.22.0.0 10 = VHIP1 1500 0.255.255.00.22.25.0 10.22.25.9 = VCTC099216 HOST 10.22.25.11= VCTC119216 HOST DEFAULTNET 10.22.11.110 ETH0 1500 0 (REAL ROUTER) START <mailto:DEV@0074> DEV@0074 START VHIP1 START VCTC09 START VCTC11 *** PROFILE TCPIP END *** *** SYSTEM CONFIG BEGIN *** DEFINE LAN VIRTHIP1 MAXCONN INF OWNERID SYSTEM TYPE HIPER *** SYSTEM CONFIG END *** *** USER DIRECT BEGIN *** PROFILE LINDFLT IPL CMS MA
Re: Guest LAN using Virtual Hipersockets...again
ryn-zvmlnx:~ # uname -a uname -a Linux ryn-zvmlnx 2.4.7-timer-SMP #1 SMP Tue May 21 12:58:16 GMT 2002 s390 unknown -Original Message- From: Eddie Chen [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 04, 2003 12:57 PM To: [EMAIL PROTECTED] Subject: Re: Guest LAN using Virtual Hipersockets...again Did you apply the may-2002 patches form SuSE7 and update the /etc/modules ??? |+-> || "Ketchens, LeMarr T. | || (RyTull)" | || | || Sent by: Linux on 390 | || Port | || <[EMAIL PROTECTED]| || u> | || | || | || 02/03/2003 10:07 PM| || Please respond to Linux| || on 390 Port| || | |+-> >--- | | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Guest LAN using Virtual Hipersockets...again | >--- | 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, but that won't do. I need to find a way to get the working without the VCTC. It seems that my primary problem is on the Linux side, but I can not figure out why this will not work. Do I need to have a physical Hipersocket or physical connection via OSA-E to point to as the gateway for the Linux machines? Sorry for constantly returning, but I think I'm getting close with the help I've received thus far. __ L. Ketchens Technical Services MVS Systems Programmer [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> *** PROFILE TCPIP BEGIN *** ; OSA-E GIGABIT ETHERNET CARD ON z/800 CHPID DEVICE <mailto:DEV@0074> DEV@0074 OSD 0074 PORTNAME ZVMHOST PRIROUTER LINK ETH0 QDIOETHERNET <mailto:DEV@0074> DEV@0074 ; VIRTUAL HIPERSOCKETS 2000-2002 VHIP1 DEVICE VHIP1 HIPERS 2000 PORTNAME VIRTHIP1 AUTORESTART LINK VHIP1 QDIOIP VHIP1 ; VIRTUAL CHAN 2 CHAN 3000-3001 FOR LNXMSTR DEVICE VCTC09 CTC 3000 LINK VCTC09 CTC 0 VCTC09 ; VIRTUAL CHAN 2 CHAN 3002-3003 FOR LINUX11 DEVICE VCTC11 CTC 3002 LINK VCTC11 CTC 0 VCTC11 HOME 10.22.22.213 ETH0 10.22.25.1 VHIP1 10.22.22.213 VCTC09 10.22.22.213 VCTC11 GATEWAY 10 = ETH0 1500 0.255.0.0 0.22.0.0 10 = VHIP1 1500 0.255.255.00.22.25.0 10.22.25.9 = VCTC099216 HOST 10.22.25.11= VCTC119216 HOST DEFAULTNET 10.22.11.110 ETH0 1500 0 (REAL ROUTER) START <mailto:DEV@0074> DEV@0074 START VHIP1 START VCTC09 START VCTC11 *** PROFILE TCPIP END *** *** SYSTEM CONFIG BEGIN *** DEFINE LAN VIRTHIP1 MAXCONN INF OWNERID SYSTEM TYPE HIPER *** SYSTEM CONFIG END *** *** USER DIRECT BEGIN *** PROFILE LINDFLT IPL CMS MACH ESA 4 IUCV ANY IUCV ALLOW CPU 00 NODEDICATE CPU 01 NODEDICATE CPU 02 NODEDICATE CPU 03 NODEDICATE SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A CONSOLE 009 3215 T SPECIAL 2000 HIPER 3 SYSTEM VIRTHIP1 LINK MAINT 0190 0190 RR LINK MAINT 019D 019D RR LINK MAINT 019E 019E RR LINK TCPMAINT 0592 0592 RR * USER TCPIP TCPIP 64M 128M ABG INCLUDE TCPCMSU OPTION QUICKDSP SVMSTAT MAXCONN 1024 DIAG98 APPLMON SHARE RELATIVE 3000 IUCV ALLOW IUCV ANY PRIORITY IUCV *CCS PRIORITY MSGLIMIT 255 SPECIAL 2000 HIPER 3 SYSTEM VIRTHIP1 SPECIAL 3000 CTCA LNXMSTR SPECIAL 3001 CTCA LNXMSTR SPECIAL 3002 CTCA LINUX11 SPECIAL 3003 CTCA LINUX11 LINK TCPMAINT 591 591 RR LINK TCPMAINT 592 592 RR LINK TCPMAINT 198 198 RR MDISK 191 3390 0486 005 430W01 MR RPASS WPASS MPASS * USER LNXMSTR LNXMSTR 128M 512M G INCLUDE LINDFLT SPECIAL 3000 CTCA TCPIP SPECIAL 3001 CTCA TCPIP MDISK 191 3390 0560 0050 430W02 MR RPASS WPASS MPASS MDISK 100 3390 0001 3338 LNX001 MR RPASS WPASS MPASS MDISK 101 3390 0001 1669 LNX002 MR RPASS WPASS MPASS * USER LINUX11 LINUX11 512M 512M G INCLUDE LINDFLT SHARE REL 2500 SPECIAL 3002 CTCA TCPIP SPECIAL 3003 CTCA TCPIP MDISK 100 3390 0001 3338 LNX003 MR RPASS WPASS MPASS MDISK 101 3390 1670 1669 LNX002 MR RPASS WPASS MPASS MDISK 200 3390 0001 3338 LNX004 MR RPASS WPASS MPASS LINK LNXMSTR 191 191 RR * *** USER DIRECT END *** *** chan
Guest LAN using Virtual Hipersockets...again
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, but that won't do. I need to find a way to get the working without the VCTC. It seems that my primary problem is on the Linux side, but I can not figure out why this will not work. Do I need to have a physical Hipersocket or physical connection via OSA-E to point to as the gateway for the Linux machines? Sorry for constantly returning, but I think I'm getting close with the help I've received thus far. __ L. Ketchens Technical Services MVS Systems Programmer [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> *** PROFILE TCPIP BEGIN *** ; OSA-E GIGABIT ETHERNET CARD ON z/800 CHPID DEVICE <mailto:DEV@0074> DEV@0074 OSD 0074 PORTNAME ZVMHOST PRIROUTER LINK ETH0 QDIOETHERNET <mailto:DEV@0074> DEV@0074 ; VIRTUAL HIPERSOCKETS 2000-2002 VHIP1 DEVICE VHIP1 HIPERS 2000 PORTNAME VIRTHIP1 AUTORESTART LINK VHIP1 QDIOIP VHIP1 ; VIRTUAL CHAN 2 CHAN 3000-3001 FOR LNXMSTR DEVICE VCTC09 CTC 3000 LINK VCTC09 CTC 0 VCTC09 ; VIRTUAL CHAN 2 CHAN 3002-3003 FOR LINUX11 DEVICE VCTC11 CTC 3002 LINK VCTC11 CTC 0 VCTC11 HOME 10.22.22.213 ETH0 10.22.25.1 VHIP1 10.22.22.213 VCTC09 10.22.22.213 VCTC11 GATEWAY 10 = ETH0 1500 0.255.0.0 0.22.0.0 10 = VHIP1 1500 0.255.255.00.22.25.0 10.22.25.9 = VCTC099216 HOST 10.22.25.11= VCTC119216 HOST DEFAULTNET 10.22.11.110 ETH0 1500 0 (REAL ROUTER) START <mailto:DEV@0074> DEV@0074 START VHIP1 START VCTC09 START VCTC11 *** PROFILE TCPIP END *** *** SYSTEM CONFIG BEGIN *** DEFINE LAN VIRTHIP1 MAXCONN INF OWNERID SYSTEM TYPE HIPER *** SYSTEM CONFIG END *** *** USER DIRECT BEGIN *** PROFILE LINDFLT IPL CMS MACH ESA 4 IUCV ANY IUCV ALLOW CPU 00 NODEDICATE CPU 01 NODEDICATE CPU 02 NODEDICATE CPU 03 NODEDICATE SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A CONSOLE 009 3215 T SPECIAL 2000 HIPER 3 SYSTEM VIRTHIP1 LINK MAINT 0190 0190 RR LINK MAINT 019D 019D RR LINK MAINT 019E 019E RR LINK TCPMAINT 0592 0592 RR * USER TCPIP TCPIP 64M 128M ABG INCLUDE TCPCMSU OPTION QUICKDSP SVMSTAT MAXCONN 1024 DIAG98 APPLMON SHARE RELATIVE 3000 IUCV ALLOW IUCV ANY PRIORITY IUCV *CCS PRIORITY MSGLIMIT 255 SPECIAL 2000 HIPER 3 SYSTEM VIRTHIP1 SPECIAL 3000 CTCA LNXMSTR SPECIAL 3001 CTCA LNXMSTR SPECIAL 3002 CTCA LINUX11 SPECIAL 3003 CTCA LINUX11 LINK TCPMAINT 591 591 RR LINK TCPMAINT 592 592 RR LINK TCPMAINT 198 198 RR MDISK 191 3390 0486 005 430W01 MR RPASS WPASS MPASS * USER LNXMSTR LNXMSTR 128M 512M G INCLUDE LINDFLT SPECIAL 3000 CTCA TCPIP SPECIAL 3001 CTCA TCPIP MDISK 191 3390 0560 0050 430W02 MR RPASS WPASS MPASS MDISK 100 3390 0001 3338 LNX001 MR RPASS WPASS MPASS MDISK 101 3390 0001 1669 LNX002 MR RPASS WPASS MPASS * USER LINUX11 LINUX11 512M 512M G INCLUDE LINDFLT SHARE REL 2500 SPECIAL 3002 CTCA TCPIP SPECIAL 3003 CTCA TCPIP MDISK 100 3390 0001 3338 LNX003 MR RPASS WPASS MPASS MDISK 101 3390 1670 1669 LNX002 MR RPASS WPASS MPASS MDISK 200 3390 0001 3338 LNX004 MR RPASS WPASS MPASS LINK LNXMSTR 191 191 RR * *** USER DIRECT END *** *** chandev.conf begin ***LNXMSTR add_parms,0x10,0x2000,0x2002,portname:VIRTHIP1 ctc0,0x3000,0x3001,0,0 qeth0,0x2000,0x2001,0x2002,0,0,0 *** chandev.conf end *** *** rc.config begin ***LNXMSTR NETCONFIG="_0 _1" IPADDR_0="10.22.25.10" IPADDR_1="10.22.25.9" NETDEV_0="hsi0" NETDEV_1="ctc0" IFCONFIG_0="10.22.25.10 broadcast 10.22.25.255 netmask 255.255.255.0 mtu 1500 up" IFCONFIG_1="10.22.25.9 pointopoint 10.22.22.213 mtu 32760 up" *** rc.config end *** *** route.conf begin ***LNXMSTR 10.22.22.213 0.0.0.0 255.255.255.255 ctc0 10.22.25.00.0.0.0 255.255.255.0 hsi0 default 10.22.25.10.0.0.0 hsi0 *** route.conf end *** --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. ---
Re: z/VM Guest LAN using HiperSockets
On Friday, 01/31/2003 at 04:45 CST, "Ketchens, LeMarr T. (RyTull)" <[EMAIL PROTECTED]> wrote: > Now, all is in virtual connectivity. I have an hsi0 defined on both Linux > Guests, but I think I have it pointing to the wrong broadcast address. Can > I make up a broadcast address (10.22.25.1). or should I select the VMTCPIP > Router eth0 (10.25.25.155) or to the Cisco Router (10.25.1.1). and do change > the default of the guest to point to (10.22.25.1)? Don't mess with the Linux broadcast address. It is selected automatically (and correctly) based on the subnet mask you provided to it. You *do* need to add a default route to the Linuxen pointing to VM TCP/IP. VM's default route is the Cisco router. You know the following information: - z/VM TCPIP on ethernet LAN => 10.25.25.155 - Linux01 on guest LAN => 10.22.25.10 - Linux02 on guest LAN => 10.22.25.11 - Cisco Router => 10.25.1.1 I extracted the following information from your PROFILE TCPIP, but I have no way of knowing if these are the values you intended (only you know the answer to that): - Subnet mask of ethernet LAN: 255.255.0.0 - Subnet mask of guest LAN: 255.255.255.0 There is one missing piece of information: - z/VM TCPIP on guest LAN I'm going to make up an address: 10.22.25.1 Given all of the above, you would code: HOME 10.25.25.155 ETH0 10.22.25.1VHIP1 GATEWAY 10 = ETH0 1500 0.255.0.00.25.0.0 10 = VHIP1 1500 0.255.255.0 0.22.25.0 default 10.25.1.1 ETH0 1500 0 In each Linux, specify a default gateway of 10.22.25.1. The Cisco router will have to be told to route 10.22.25.0/24 through 10.25.25.155. Alan Altmark Sr. Software Engineer IBM z/VM Development
Re: z/VM Guest LAN using HiperSockets
LeMarr, Two things. Guest LANs using Hipersockets don't support broadcast. Guest LANs using QDIO do support it. You have to be at z/VM 4.3 to be able to define a QDIO Guest LAN. Mark Post -Original Message- From: Ketchens, LeMarr T. (RyTull) [mailto:[EMAIL PROTECTED]] Sent: Friday, January 31, 2003 5:45 PM To: [EMAIL PROTECTED] Subject: Re: z/VM Guest LAN using HiperSockets Now, all is in virtual connectivity. I have an hsi0 defined on both Linux Guests, but I think I have it pointing to the wrong broadcast address. Can I make up a broadcast address (10.22.25.1). or should I select the VMTCPIP Router eth0 (10.25.25.155) or to the Cisco Router (10.25.1.1). and do change the default of the guest to point to (10.22.25.1)? -Original Message- From: Dennis Musselwhite [mailto:[EMAIL PROTECTED]] Sent: Friday, January 31, 2003 3:26 PM To: [EMAIL PROTECTED] Subject: Re: z/VM Guest LAN using HiperSockets Hi, It looks like you are dedicating a LAN segment to each Linux guest. With Guest LAN you are no longer restricted to the point-to-point model. Define just one Guest LAN (VHIP1) for this segment and one virtual HiperSockets adapter for each guest (TCPIP, LINUX01, and LINUX02). Each guest connects (via the CP COUPLE command) to the same Guest LAN. You can eliminate DEVICE VHIP2 and LINK VHIP2 statements... The HOME list can include both IP addresses, but both should name the same link (VHIP1). You can drop the VHIP2 entry from the GATEWAY list. And... the START VHIP2 can be eliminated. To "wire" your virtual network, somebody has to "own" the LAN segment (ownership of the LAN makes it easier to manage it). For example, if you want TCPIP to own it, you have to issue (from the TCPIP userid): CP DEFINE LAN VHIP1 This is the simplest form to create a HiperSockets LAN segment. For each guest (TCPIP, LINUX01, and LINUX02) you need to define a NIC (instead of a CTCA) and couple to the LAN (instead of a specific peer). For example: CP DEFINE NIC 2000 CP COUPLE 2000 TO TCPIP VHIP1 After you DEFINE LAN and couple from all three guests, you should be able to confirm those connections with the command: CP QUERY LAN VHIP1 DETAILS Regards, Dennis Musselwhite ([EMAIL PROTECTED]) IBM Corporation -- z/VM Development -- CP Network Simulation "Ketchens, LeMarr T. (RyTull)" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 01/31/2003 02:33:49 PM Please respond to Linux on 390 Port <[EMAIL PROTECTED]> Sent by:Linux on 390 Port <[EMAIL PROTECTED]> To:[EMAIL PROTECTED] cc: Subject:[LINUX-390] z/VM Guest LAN using HiperSockets Okay, I've figured out how to run a Linux Guest as vctc and connect with no problem. Right now, I need to know how to get this running with Guest LAN using virtual Hipersockets. I think I can figure the issues on the Linux Guest side, but I need to know what to use in the PROFILE TCPIP. I need to know based on the following: OSA-E 0090-0092 => z/VM TCPIP => 10.25.25.155 Virtual HIPER 2000-2002 => Portname:VIRTHIP1 Virtual HiperLan 2100-2102 => Portname:VIRTHIP2 Projected Linux Guest IP Addresses: Linux01 => 10.22.25.10 Linux02 => 10.22.25.11 We do have a Cisco Router => 10.25.1.1 ; OSA-E GIGABIT ETHERNET CARD ON Z/800 CHPID =>00 DEVICE DEV@0090 OSD 0090 PORTNAME VMHOST PRIROUTER LINK ETH0 QDIOETHERNET DEV@0090 ; VIRTUAL HIPERSOCKETS 2000-2002 VHIP1 DEVICE VHIP1 HIPERS 2000 PORTNAME VIRTHIP1 AUTORESTART LINK VHIP1 QDIOIP VHIP1 ; VIRTUAL HIPERSOCKETS 2100-2102 VHIP2 (Guest LAN) DEVICE VHIP2 HIPERS 2100 PORTNAME VIRTHIP2 AUTORESTART LINK VHIP2 QDIOIP VHIP2 HOME 10.25.25.155 ETH0 10.22.25.10 VHIP1 10.22.25.11 VHIP2 ; (End HOME Address information) ; -- GATEWAY ; -- 10 = ETH0 1500 0.255.0.00.25.0.0 10 = VHIP1 1500 0.255.255.00.22.25.0 10 = VHIP2 1500 0.255.255.00.22.25.0 DEFAULTNET 10.25.25.155 ETH0 1500 0 ; (End GATEWAY Static Routing information) START DEV@0090 START VHIP1 START VHIP2 ; (End START statements) With these as the statements, I want to know if I'm going down the wrong path trying to utilize Guest LAN with virtual Hipersockets. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your
Re: z/VM Guest LAN using HiperSockets
Now, all is in virtual connectivity. I have an hsi0 defined on both Linux Guests, but I think I have it pointing to the wrong broadcast address. Can I make up a broadcast address (10.22.25.1). or should I select the VMTCPIP Router eth0 (10.25.25.155) or to the Cisco Router (10.25.1.1). and do change the default of the guest to point to (10.22.25.1)? -Original Message- From: Dennis Musselwhite [mailto:[EMAIL PROTECTED]] Sent: Friday, January 31, 2003 3:26 PM To: [EMAIL PROTECTED] Subject: Re: z/VM Guest LAN using HiperSockets Hi, It looks like you are dedicating a LAN segment to each Linux guest. With Guest LAN you are no longer restricted to the point-to-point model. Define just one Guest LAN (VHIP1) for this segment and one virtual HiperSockets adapter for each guest (TCPIP, LINUX01, and LINUX02). Each guest connects (via the CP COUPLE command) to the same Guest LAN. You can eliminate DEVICE VHIP2 and LINK VHIP2 statements... The HOME list can include both IP addresses, but both should name the same link (VHIP1). You can drop the VHIP2 entry from the GATEWAY list. And... the START VHIP2 can be eliminated. To "wire" your virtual network, somebody has to "own" the LAN segment (ownership of the LAN makes it easier to manage it). For example, if you want TCPIP to own it, you have to issue (from the TCPIP userid): CP DEFINE LAN VHIP1 This is the simplest form to create a HiperSockets LAN segment. For each guest (TCPIP, LINUX01, and LINUX02) you need to define a NIC (instead of a CTCA) and couple to the LAN (instead of a specific peer). For example: CP DEFINE NIC 2000 CP COUPLE 2000 TO TCPIP VHIP1 After you DEFINE LAN and couple from all three guests, you should be able to confirm those connections with the command: CP QUERY LAN VHIP1 DETAILS Regards, Dennis Musselwhite ([EMAIL PROTECTED]) IBM Corporation -- z/VM Development -- CP Network Simulation "Ketchens, LeMarr T. (RyTull)" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 01/31/2003 02:33:49 PM Please respond to Linux on 390 Port <[EMAIL PROTECTED]> Sent by:Linux on 390 Port <[EMAIL PROTECTED]> To:[EMAIL PROTECTED] cc: Subject:[LINUX-390] z/VM Guest LAN using HiperSockets Okay, I've figured out how to run a Linux Guest as vctc and connect with no problem. Right now, I need to know how to get this running with Guest LAN using virtual Hipersockets. I think I can figure the issues on the Linux Guest side, but I need to know what to use in the PROFILE TCPIP. I need to know based on the following: OSA-E 0090-0092 => z/VM TCPIP => 10.25.25.155 Virtual HIPER 2000-2002 => Portname:VIRTHIP1 Virtual HiperLan 2100-2102 => Portname:VIRTHIP2 Projected Linux Guest IP Addresses: Linux01 => 10.22.25.10 Linux02 => 10.22.25.11 We do have a Cisco Router => 10.25.1.1 ; OSA-E GIGABIT ETHERNET CARD ON Z/800 CHPID =>00 DEVICE DEV@0090 OSD 0090 PORTNAME VMHOST PRIROUTER LINK ETH0 QDIOETHERNET DEV@0090 ; VIRTUAL HIPERSOCKETS 2000-2002 VHIP1 DEVICE VHIP1 HIPERS 2000 PORTNAME VIRTHIP1 AUTORESTART LINK VHIP1 QDIOIP VHIP1 ; VIRTUAL HIPERSOCKETS 2100-2102 VHIP2 (Guest LAN) DEVICE VHIP2 HIPERS 2100 PORTNAME VIRTHIP2 AUTORESTART LINK VHIP2 QDIOIP VHIP2 HOME 10.25.25.155 ETH0 10.22.25.10 VHIP1 10.22.25.11 VHIP2 ; (End HOME Address information) ; -- GATEWAY ; -- 10 = ETH0 1500 0.255.0.00.25.0.0 10 = VHIP1 1500 0.255.255.00.22.25.0 10 = VHIP2 1500 0.255.255.00.22.25.0 DEFAULTNET 10.25.25.155 ETH0 1500 0 ; (End GATEWAY Static Routing information) START DEV@0090 START VHIP1 START VHIP2 ; (End START statements) With these as the statements, I want to know if I'm going down the wrong path trying to utilize Guest LAN with virtual Hipersockets. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strict
Re: z/VM Guest LAN using HiperSockets
Hi, It looks like you are dedicating a LAN segment to each Linux guest. With Guest LAN you are no longer restricted to the point-to-point model. Define just one Guest LAN (VHIP1) for this segment and one virtual HiperSockets adapter for each guest (TCPIP, LINUX01, and LINUX02). Each guest connects (via the CP COUPLE command) to the same Guest LAN. You can eliminate DEVICE VHIP2 and LINK VHIP2 statements... The HOME list can include both IP addresses, but both should name the same link (VHIP1). You can drop the VHIP2 entry from the GATEWAY list. And... the START VHIP2 can be eliminated. To "wire" your virtual network, somebody has to "own" the LAN segment (ownership of the LAN makes it easier to manage it). For example, if you want TCPIP to own it, you have to issue (from the TCPIP userid): CP DEFINE LAN VHIP1 This is the simplest form to create a HiperSockets LAN segment. For each guest (TCPIP, LINUX01, and LINUX02) you need to define a NIC (instead of a CTCA) and couple to the LAN (instead of a specific peer). For example: CP DEFINE NIC 2000 CP COUPLE 2000 TO TCPIP VHIP1 After you DEFINE LAN and couple from all three guests, you should be able to confirm those connections with the command: CP QUERY LAN VHIP1 DETAILS Regards, Dennis Musselwhite ([EMAIL PROTECTED]) IBM Corporation -- z/VM Development -- CP Network Simulation "Ketchens, LeMarr T. (RyTull)" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 01/31/2003 02:33:49 PM Please respond to Linux on 390 Port <[EMAIL PROTECTED]> Sent by:Linux on 390 Port <[EMAIL PROTECTED]> To:[EMAIL PROTECTED] cc: Subject:[LINUX-390] z/VM Guest LAN using HiperSockets Okay, I've figured out how to run a Linux Guest as vctc and connect with no problem. Right now, I need to know how to get this running with Guest LAN using virtual Hipersockets. I think I can figure the issues on the Linux Guest side, but I need to know what to use in the PROFILE TCPIP. I need to know based on the following: OSA-E 0090-0092 => z/VM TCPIP => 10.25.25.155 Virtual HIPER 2000-2002 => Portname:VIRTHIP1 Virtual HiperLan 2100-2102 => Portname:VIRTHIP2 Projected Linux Guest IP Addresses: Linux01 => 10.22.25.10 Linux02 => 10.22.25.11 We do have a Cisco Router => 10.25.1.1 ; OSA-E GIGABIT ETHERNET CARD ON Z/800 CHPID =>00 DEVICE DEV@0090 OSD 0090 PORTNAME VMHOST PRIROUTER LINK ETH0 QDIOETHERNET DEV@0090 ; VIRTUAL HIPERSOCKETS 2000-2002 VHIP1 DEVICE VHIP1 HIPERS 2000 PORTNAME VIRTHIP1 AUTORESTART LINK VHIP1 QDIOIP VHIP1 ; VIRTUAL HIPERSOCKETS 2100-2102 VHIP2 (Guest LAN) DEVICE VHIP2 HIPERS 2100 PORTNAME VIRTHIP2 AUTORESTART LINK VHIP2 QDIOIP VHIP2 HOME 10.25.25.155 ETH0 10.22.25.10 VHIP1 10.22.25.11 VHIP2 ; (End HOME Address information) ; -- GATEWAY ; -- 10 = ETH0 1500 0.255.0.00.25.0.0 10 = VHIP1 1500 0.255.255.00.22.25.0 10 = VHIP2 1500 0.255.255.00.22.25.0 DEFAULTNET 10.25.25.155 ETH0 1500 0 ; (End GATEWAY Static Routing information) START DEV@0090 START VHIP1 START VHIP2 ; (End START statements) With these as the statements, I want to know if I'm going down the wrong path trying to utilize Guest LAN with virtual Hipersockets. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. ---
Re: z/VM Guest LAN using HiperSockets
Just by looking at the two addresses for VHIP1 and VHIP2 you will have a problem. 1 - the HOME/GATEWAY address for VHIP1 should be 10.21.25.10 /0.21.25.0 2 - I'm assuming that you have done the CP related commands for GuestLAN support, and you are running SuSE 7.0 with the latest patches. - /etc/chandev.conf and /etc/module.conf |+-> || "Ketchens, LeMarr T. | || (RyTull)" | || | || Sent by: Linux on 390 | || Port | || <[EMAIL PROTECTED]| || U> | || | || | || 01/31/2003 07:33 PM| || Please respond to Linux| || on 390 Port| || | |+-> >---| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: z/VM Guest LAN using HiperSockets | >---| Okay, I've figured out how to run a Linux Guest as vctc and connect with no problem. Right now, I need to know how to get this running with Guest LAN using virtual Hipersockets. I think I can figure the issues on the Linux Guest side, but I need to know what to use in the PROFILE TCPIP. I need to know based on the following: OSA-E 0090-0092 => z/VM TCPIP => 10.25.25.155 Virtual HIPER 2000-2002 => Portname:VIRTHIP1 Virtual HiperLan 2100-2102 => Portname:VIRTHIP2 Projected Linux Guest IP Addresses: Linux01 => 10.22.25.10 Linux02 => 10.22.25.11 We do have a Cisco Router => 10.25.1.1 ; OSA-E GIGABIT ETHERNET CARD ON Z/800 CHPID =>00 DEVICE DEV@0090 OSD 0090 PORTNAME VMHOST PRIROUTER LINK ETH0 QDIOETHERNET DEV@0090 ; VIRTUAL HIPERSOCKETS 2000-2002 VHIP1 DEVICE VHIP1 HIPERS 2000 PORTNAME VIRTHIP1 AUTORESTART LINK VHIP1 QDIOIP VHIP1 ; VIRTUAL HIPERSOCKETS 2100-2102 VHIP2 (Guest LAN) DEVICE VHIP2 HIPERS 2100 PORTNAME VIRTHIP2 AUTORESTART LINK VHIP2 QDIOIP VHIP2 HOME 10.25.25.155 ETH0 10.22.25.10 VHIP1 10.22.25.11 VHIP2 ; (End HOME Address information) ; -- GATEWAY ; -- 10 = ETH0 1500 0.255.0.00.25.0.0 10 = VHIP1 1500 0.255.255.00.22.25.0 10 = VHIP2 1500 0.255.255.00.22.25.0 DEFAULTNET 10.25.25.155 ETH0 1500 0 ; (End GATEWAY Static Routing information) START DEV@0090 START VHIP1 START VHIP2 ; (End START statements) With these as the statements, I want to know if I'm going down the wrong path trying to utilize Guest LAN with virtual Hipersockets. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. ---
z/VM Guest LAN using HiperSockets
Okay, I've figured out how to run a Linux Guest as vctc and connect with no problem. Right now, I need to know how to get this running with Guest LAN using virtual Hipersockets. I think I can figure the issues on the Linux Guest side, but I need to know what to use in the PROFILE TCPIP. I need to know based on the following: OSA-E 0090-0092 => z/VM TCPIP => 10.25.25.155 Virtual HIPER 2000-2002 => Portname:VIRTHIP1 Virtual HiperLan 2100-2102 => Portname:VIRTHIP2 Projected Linux Guest IP Addresses: Linux01 => 10.22.25.10 Linux02 => 10.22.25.11 We do have a Cisco Router => 10.25.1.1 ; OSA-E GIGABIT ETHERNET CARD ON Z/800 CHPID =>00 DEVICE DEV@0090 OSD 0090 PORTNAME VMHOST PRIROUTER LINK ETH0 QDIOETHERNET DEV@0090 ; VIRTUAL HIPERSOCKETS 2000-2002 VHIP1 DEVICE VHIP1 HIPERS 2000 PORTNAME VIRTHIP1 AUTORESTART LINK VHIP1 QDIOIP VHIP1 ; VIRTUAL HIPERSOCKETS 2100-2102 VHIP2 (Guest LAN) DEVICE VHIP2 HIPERS 2100 PORTNAME VIRTHIP2 AUTORESTART LINK VHIP2 QDIOIP VHIP2 HOME 10.25.25.155 ETH0 10.22.25.10 VHIP1 10.22.25.11 VHIP2 ; (End HOME Address information) ; -- GATEWAY ; -- 10 = ETH0 1500 0.255.0.00.25.0.0 10 = VHIP1 1500 0.255.255.00.22.25.0 10 = VHIP2 1500 0.255.255.00.22.25.0 DEFAULTNET 10.25.25.155 ETH0 1500 0 ; (End GATEWAY Static Routing information) START DEV@0090 START VHIP1 START VHIP2 ; (End START statements) With these as the statements, I want to know if I'm going down the wrong path trying to utilize Guest LAN with virtual Hipersockets. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. ---
Re: Another z/VM Linux Guests using Hipersockets Question
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 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 HiperSockets. I really need some help. From > > examples within the PROFILE TCPIP (DEVICE & LINK, HOME and GATEWAY) to > > the IFCONFIGs used to define the hipersockets to z/VM and to the Linux > > Guest. Here's how we are setup. We are running z/VM 4.3.0 in an IFL on a > > z/800 box. We have OSA-E Gigabit Ethernet at our disposal. We have z/VM > > up and running with with 2 Linux Guests (SuSE 2.4.7). The two guests are > > ip connected via virtual CTCs. We would like to get the HiperSockets > > working (virtual or physical). To get to the outside world we also have > > a Cisco Router, if that matters. At this point, I would appreciate any > > insight into correcting this problem. Thanks > > Apply all the service from SuSE. The initial SLES 7 didn't work with > virtual HiperSockets, but after enough patches you get both a kernel and > drivers that will drive them just fine. > > Adam 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) to read up on? Thanks in advance folks, Steve
Re: Another z/VM Linux Guests using Hipersockets Question
>From Steven Adams: > 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) to read up on? HiperSockets (the hardware feature) and HiperSockets (as simulated by z/VM CP) are implementations of QDIO architecture which include ARP offload capability. The adapter does the ARP for you. The guest software just has to tell the adapter about each IP Address to associate with this particular interface. The OSA-Express in QDIO mode (the hardware) and QDIO (as simulated by z/VM 4.3.0 CP) include the ARP offload capability, but they also support broadcast. Note that you will need z/VM 4.3.0 APAR VM63172 to exploit QDIO Guest LAN broadcast for DHCP under Linux. My point is that these adapters are capable of networking without exposing the ARP traffic to the guest. Regards, Dennis Musselwhite ([EMAIL PROTECTED]) IBM Corporation -- z/VM Development -- CP Network Simulation
Re: z/VM Linux Guests using Hipersockets....
I am under the impression that all maintenance needed has been applied (z/VM & SuSE). I needed some examples to cross check with those who actually have a working model. Maybe we have a misconfigured subnet. I'm just trying to rule out as much as possible. -Original Message- From: Adam 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 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 > used to define the hipersockets to z/VM and to the Linux Guest. Here's how > we are setup. We are running z/VM 4.3.0 in an IFL on a z/800 box. We have > OSA-E Gigabit Ethernet at our disposal. We have z/VM up and running with > with 2 Linux Guests (SuSE 2.4.7). The two guests are ip connected via > virtual CTCs. We would like to get the HiperSockets working (virtual or > physical). To get to the outside world we also have a Cisco Router, if that > matters. At this point, I would appreciate any insight into correcting this > problem. Thanks Apply all the service from SuSE. The initial SLES 7 didn't work with virtual HiperSockets, but after enough patches you get both a kernel and drivers that will drive them just fine. Adam --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. ---
Re: Another z/VM Linux Guests using Hipersockets Question
> 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) to read > up on? If you need broadcast, you should go with virtual OSAs rather than Virtual HiperSockets. Both are supported in z/VM 4.3. The only difference is whether you CP DEFINE LAN OWNER LANID TYPE HIPER or CP DEFINE LAN OWNER LANID TYPE QDIO Adam
Another z/VM Linux Guests using Hipersockets Question
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 HiperSockets. I really need some help. From > > examples within the PROFILE TCPIP (DEVICE & LINK, HOME and GATEWAY) to > > the IFCONFIGs used to define the hipersockets to z/VM and to the Linux > > Guest. Here's how we are setup. We are running z/VM 4.3.0 in an IFL on a > > z/800 box. We have OSA-E Gigabit Ethernet at our disposal. We have z/VM > > up and running with with 2 Linux Guests (SuSE 2.4.7). The two guests are > > ip connected via virtual CTCs. We would like to get the HiperSockets > > working (virtual or physical). To get to the outside world we also have > > a Cisco Router, if that matters. At this point, I would appreciate any > > insight into correcting this problem. Thanks > > Apply all the service from SuSE. The initial SLES 7 didn't work with > virtual HiperSockets, but after enough patches you get both a kernel and > drivers that will drive them just fine. > > Adam 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) to read up on? Thanks in advance folks, Steve
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 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 > used to define the hipersockets to z/VM and to the Linux Guest. Here's how > we are setup. We are running z/VM 4.3.0 in an IFL on a z/800 box. We have > OSA-E Gigabit Ethernet at our disposal. We have z/VM up and running with > with 2 Linux Guests (SuSE 2.4.7). The two guests are ip connected via > virtual CTCs. We would like to get the HiperSockets working (virtual or > physical). To get to the outside world we also have a Cisco Router, if that > matters. At this point, I would appreciate any insight into correcting this > problem. Thanks Apply all the service from SuSE. The initial SLES 7 didn't work with virtual HiperSockets, but after enough patches you get both a kernel and drivers that will drive them just fine. Adam
z/VM Linux Guests using Hipersockets....
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 used to define the hipersockets to z/VM and to the Linux Guest. Here's how we are setup. We are running z/VM 4.3.0 in an IFL on a z/800 box. We have OSA-E Gigabit Ethernet at our disposal. We have z/VM up and running with with 2 Linux Guests (SuSE 2.4.7). The two guests are ip connected via virtual CTCs. We would like to get the HiperSockets working (virtual or physical). To get to the outside world we also have a Cisco Router, if that matters. At this point, I would appreciate any insight into correcting this problem. Thanks Also, when coding the "DEFAULTNET", should that be the VHIP or the Cisco Router or the VM Host? Lemarr Ketchens --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. ---
Re: Hipersockets SLES8
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 (your QUERY LAN command shows that it is associated with your Linux user's connection). > LAN SYSTEM VMSNAPV Type: HIPERS Active: 2 MAXCONN: INFINITE > PERSISTENT UNRESTRICTED MFS: 16384 > Adapter Owner: TCPIPNIC: 0D20 Name: VMPORT3 > 129.80.16.54129.80.45.128 129.80.45.193 > 129.80.45.225 > Adapter Owner: TMP04LNX NIC: 7000 Name: UNASSIGNED > 129.80.45.226 It appears that you have sent 9 packets from 129.80.45.226 (with 0 responses). > 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 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:0 (0.0 b) TX bytes:792 (792.0 b) > Interrupt:25 I don't know why TCPIP is not responding, but both interfaces look valid, so if you 'ping 129.45.225 -c 1' from your linux user, it should be delivered to the TCPIP user. I know of two easy ways this can fail on the way back: (1) TCPIP has another gateway definition that sends this IP address out a different interface. (2) TCPIP thinks this datagram has to go through an intermediate node with a different IP address (this may send it into the right LAN segment but with the wrong next-hop address which makes it invisible to your Linux connection). Regards, Dennis Musselwhite ([EMAIL PROTECTED]) IBM Corporation -- z/VM Development -- CP Network Simulation "Jones, Brian P" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 01/15/2003 06:20:25 PM 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 SLES8 > 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 an installed system. Is there any known problems with the > hipersockets support? > You will see that I did not have a portname defined on the Linux side, but > I have tried adding a portname on a (non-starter) system, also to no avail. > > 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 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:0 (0.0 b) TX bytes:792 (792.0 b) > Interrupt:25 > #*#: route > route > Kernel IP routing table > Destination Gateway Genmask Flags Metric RefUse > Iface > 129.80.45.224 * 255.255.255.224 U 0 00 > hsi0 > default 129.80.45.225 0.0.0.0 UG0 00 > hsi0 > #*#: > > Here is my VM config: > LAN SYSTEM VMSNAPV Type: HIPERS Active: 2 MAXCONN: INFINITE > PERSISTENT UNRESTRICTED MFS: 16384 > Adapter Owner: TCPIPNIC: 0D20 Name: VMPORT3 > 129.80.16.54129.80.45.128 129.80.45.193 > 129.80.45.225 > Adapter Owner: TMP04LNX NIC: 7000 Name: UNASSIGNED > 129.80.45.226 > > CP Q NIC DETAILS > Adapter 7000 Type: HIPER Name: UNASSIGNED Devices: 3 > Port 0 MAC: 00-04-AC-00-00-11 LAN: SYSTEM VMSNAPV MFS: 16384 > Connection Name: HALLOLE State: Session Established > Device: 7000 Unit: 000 Role: CTL-READ > Device: 7001 Unit: 001 Role: CTL-WRITE > Device: 7002 Unit: 002 Role: DATA > Unicast IP Addresses: > 129.80.45.226 > > NETSTAT HOME: > 129.80.45.225 VM1VLAN3 > > > NETSTAT GATE: > 129.80.0.0 US 1500 0.0.255.224 0.0.45.224 > VM1VLAN3 > > > > Thanks, > Brian Jones > (303) 661-4626 phone > StorageTek > INFORMATION made POWERFUL >
Re: Hipersockets SLES8
Brian,
I'll pass on this feedback from Vic Cross from a question I posted in
December:
+++
Dave, if your z/VM is 4.3 and you are using the so-called QDIO Guest LAN
(DEFINE LAN xxx QDIO), you will define your connection to the LAN as if it
was an OSA-Express. If your using z/VM 4.2, or you have 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 of VC's comments)
I think for this to work, you'd have to configure VM's MPROUTE ahead
of time to provide the proper routing to whatever lan subnet you'll be
running the putty/yast portion of the install from?? Is that true route
gurus out there?
If you're using OSA you could also share the OSA port between VM and the
linux ram system.
I did this with OSA/EXPRESS today for an SLES8 install under zVM 4.3 and it
came up fine.
Just use 3 other device numbers for the OSA and same portname as the one
defined in VM's IP stack.
Feel free to email me if you run into quirks with the SLES8 install.
The SLES8 doc didn't exactly match the process :o)
Make sure to read the readme file on CD1.
Dave Myers
Denver Solutions Group
Senior Systems Engineer
Office Phone: (303) 996-7112
Cellular Phone: (303) 619-0782
Fax: (303) 706.1713
e-mail: [EMAIL PROTECTED]
"Jones, Brian P"
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
ORTEK.COM> cc:
Sent by: Linux on 390Subject: Hipersockets SLES8
Port
<[EMAIL PROTECTED]
DU>
01/15/2003 04:20 PM
Please respond to
Linux on 390 Port
> 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 an installed system. Is there any known problems with the
> hipersockets support?
> You will see that I did not have a portname defined on the Linux side,
but
> I have tried adding a portname on a (non-starter) system, also to no
avail.
>
> 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 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:0 (0.0 b) TX bytes:792 (792.0 b)
> Interrupt:25
> #*#: route
> route
> Kernel IP routing table
> De
Re: Hipersockets SLES8
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 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:100 > > RX bytes:0 (0.0 b) TX bytes:792 (792.0 b) > > Interrupt:25 > > #*#: route > > route > > Kernel IP routing table > > Destination Gateway Genmask Flags Metric RefUse > > Iface > > 129.80.45.224 * 255.255.255.224 U 0 00 > > hsi0 > > default 129.80.45.225 0.0.0.0 UG0 00 > > hsi0 > > #*#: > > > > Here is my VM config: > > LAN SYSTEM VMSNAPV Type: HIPERS Active: 2 MAXCONN: INFINITE > > PERSISTENT UNRESTRICTED MFS: 16384 > > Adapter Owner: TCPIPNIC: 0D20 Name: VMPORT3 > > 129.80.16.54129.80.45.128 129.80.45.193 > > 129.80.45.225 > > Adapter Owner: TMP04LNX NIC: 7000 Name: UNASSIGNED > > 129.80.45.226 > > > > CP Q NIC DETAILS > > Adapter 7000 Type: HIPER Name: UNASSIGNED Devices: 3 > > Port 0 MAC: 00-04-AC-00-00-11 LAN: SYSTEM VMSNAPV MFS: 16384 > > Connection Name: HALLOLE State: Session Established > > Device: 7000 Unit: 000 Role: CTL-READ > > Device: 7001 Unit: 001 Role: CTL-WRITE > > Device: 7002 Unit: 002 Role: DATA > > Unicast IP Addresses: > > 129.80.45.226 > > > > NETSTAT HOME: > > 129.80.45.225 VM1VLAN3 > > > > > > NETSTAT GATE: > > 129.80.0.0 US 1500 0.0.255.224 0.0.45.224 > > VM1VLAN3 > > > > > > > > Thanks, > > Brian Jones > > (303) 661-4626 phone > > StorageTek > > INFORMATION made POWERFUL Being sort of a VM newbi but an IP vet of many years, it appears that you have the Hipersocket LANs network set to 16 bits where it should be 27. I could be wrong here but the NETSTAT GATE: results should look something like "129.80.45.0US 15000.0.0.224 ..." I do know that VM requires the mask entries to be configured in reverse of what one expects in the *nix world (that really crossed me up the first time I dealt with it). In short, and please correct me if I am wrong here, Linux is configured for a 27 bit subnet and VM is configured for 16 bit (old class "B") subnet making the gateway unreachable because it is on a different network. Steve
Hipersockets SLES8
> 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 an installed system. Is there any known problems with the > hipersockets support? > You will see that I did not have a portname defined on the Linux side, but > I have tried adding a portname on a (non-starter) system, also to no avail. > > 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 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:0 (0.0 b) TX bytes:792 (792.0 b) > Interrupt:25 > #*#: route > route > Kernel IP routing table > Destination Gateway Genmask Flags Metric RefUse > Iface > 129.80.45.224 * 255.255.255.224 U 0 00 > hsi0 > default 129.80.45.225 0.0.0.0 UG0 00 > hsi0 > #*#: > > Here is my VM config: > LAN SYSTEM VMSNAPV Type: HIPERS Active: 2 MAXCONN: INFINITE > PERSISTENT UNRESTRICTED MFS: 16384 > Adapter Owner: TCPIPNIC: 0D20 Name: VMPORT3 > 129.80.16.54129.80.45.128 129.80.45.193 > 129.80.45.225 > Adapter Owner: TMP04LNX NIC: 7000 Name: UNASSIGNED > 129.80.45.226 > > CP Q NIC DETAILS > Adapter 7000 Type: HIPER Name: UNASSIGNED Devices: 3 > Port 0 MAC: 00-04-AC-00-00-11 LAN: SYSTEM VMSNAPV MFS: 16384 > Connection Name: HALLOLE State: Session Established > Device: 7000 Unit: 000 Role: CTL-READ > Device: 7001 Unit: 001 Role: CTL-WRITE > Device: 7002 Unit: 002 Role: DATA > Unicast IP Addresses: > 129.80.45.226 > > NETSTAT HOME: > 129.80.45.225 VM1VLAN3 > > > NETSTAT GATE: > 129.80.0.0 US 1500 0.0.255.224 0.0.45.224 > VM1VLAN3 > > > > Thanks, > Brian Jones > (303) 661-4626 phone > StorageTek > INFORMATION made POWERFUL >
Re: HiperSockets and Guest LAN
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 the May 2002 stream; not SuSe. -- Jxrgen Quoting Malcolm Beattie <[EMAIL PROTECTED]>: > > OK, let's keep going at it. What's the output of > # cat /proc/chandev > on the Linux side (1) when you've freshly rebooted it, (2) after > you've caused the chandev settings to take effect (whether you > use SuSE's rcchandev, echo a read_conf to /proc/chandev or > whatever) and also (3) after you do the "modprobe qeth"? > > --Malcolm > <...>
Re: HiperSockets and Guest LAN
Thanks a lot for your comments Dennis. I will forward your comments regarding the APARs to the z/VM owners first thing tomorrow. Hopefully this will resolve the problem. Strangely, I have not seen this requirement mentioned in any of the (red)papers regarding *linux* and hipersockets. Maybe it's contained in the actual VM docs? -- Jxrgen Quoting Dennis Musselwhite <[EMAIL PROTECTED]>: <...> > > I believe your CP system has been installed with only the z/VM 4.2.0 base > tapes, and > no service. After the suggested APARs (VM62958 or VM62938) are applied > your current > configuration should work properly. > > > Regards, > Dennis Musselwhite ([EMAIL PROTECTED]) > IBM Corporation -- z/VM Development -- CP Network Simulation
Re: HiperSockets and Guest LAN
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 way, but why tempt fate? Cornelia is correct in pointing out that the portname does not matter here. HiperSockets does not require a portname, and if your configured portname does not match that of other interfaces using the same network, that is OK. If you were using dedicated OSA-Express devices with this interface, you would have to specify the portname and it would have to match the portname configured by the other users of that OSA port. Most users of Guest LAN are not affected by this because each DEFINE NIC creates an "adapter" in your virtual machine, so portnames only have to match within the devices that are part of that adapter range. Most users create the default adapter (three devices) and there is no risk of portname conflict. If you defined a TYPE QDIO NIC with six or more devices, all interfaces using that NIC would have to agree on a portname. That is NOT a problem on z/VM 4.2.0 because the OSA-Express simulation is not available at that level. You were concerned about the partial results in Q NIC DETAILS: > Q NIC DETAILS > Adapter 0960 Type: HIPER Name: UNASSIGNED Devices: 3 > Port 0 MAC: 00-04-AC-00-00-0E LAN: SYSTEM LNXLAN02 MFS: 16384 > Connection Name: HALLOLE State: Startup >Device: 0960 Unit: 000 Role: CTL-READ > Unassigned Devices: >Device: 0961 Unit: 001 Role: Unassigned >Device: 0962 Unit: 002 Role: Unassigned > > > The dev numbers do match with the contents of /proc/subchannels. I'm > slightly perplexed as to why the nic is in "State: Startup" and why 0961 > and 0962 are "Unassigned". That just means the driver started by initializing 0x960 as the Control-Read device, and encountered the IDX failure that you reported. We were still in "Startup" state and no attempt was made to initialize 0x961 or 0x962 so they are still reported as "Unassigned" devices. I believe your CP system has been installed with only the z/VM 4.2.0 base tapes, and no service. After the suggested APARs (VM62958 or VM62938) are applied your current configuration should work properly. Regards, Dennis Musselwhite ([EMAIL PROTECTED]) IBM Corporation -- z/VM Development -- CP Network Simulation
Re: HiperSockets and Guest LAN
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 LAN: SYSTEM LNXLAN02 MFS: 16384 > Connection Name: HALLOLE State: Startup >Device: 0960 Unit: 000 Role: CTL-READ > Unassigned Devices: >Device: 0961 Unit: 001 Role: Unassigned >Device: 0962 Unit: 002 Role: Unassigned > > > The dev numbers do match with the contents of /proc/subchannels. I'm > slightly perplexed as to why the nic is in "State: Startup" and why 0961 > and 0962 are "Unassigned". > > Linux, on the other hand, reports: > > > qeth: Trying to use card with devnos 0x960/0x961/0x962 > qeth: received an IDX TERMINATE on irq 0x11/0x12 with cause code 0x17 > qeth: IDX_ACTIVATE on read channel irq 0x11: negative reply > qeth: There were problems in hard-setting up the card. > > > Back to scratch. OK, let's keep going at it. What's the output of # cat /proc/chandev on the Linux side (1) when you've freshly rebooted it, (2) after you've caused the chandev settings to take effect (whether you use SuSE's rcchandev, echo a read_conf to /proc/chandev or whatever) and also (3) after you do the "modprobe qeth"? --Malcolm -- Malcolm Beattie <[EMAIL PROTECTED]> Linux Technical Consultant IBM EMEA Enterprise Server Group... ...from home, speaking only for myself
Re: HiperSockets and Guest LAN
Hi Cornelia qdio: loading QDIO base support version 2 ($Revision: 1.120.2.1 $/$Revision: 1.56.2.2 $) qeth: loading qeth S/390 OSA-Express driver ($Revision: 1.260.2.13 $/$Revision: 1.86.2.2 $/$Revision: 1.31 $:IPv6:VLAN) >From the May 2002 stream. Please note that we are no longer running 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. > <...>
Re: HiperSockets and Guest LAN
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 MFS: 16384 Connection Name: HALLOLE State: Startup Device: 0960 Unit: 000 Role: CTL-READ Unassigned Devices: Device: 0961 Unit: 001 Role: Unassigned Device: 0962 Unit: 002 Role: Unassigned The dev numbers do match with the contents of /proc/subchannels. I'm slightly perplexed as to why the nic is in "State: Startup" and why 0961 and 0962 are "Unassigned". Linux, on the other hand, reports: qeth: Trying to use card with devnos 0x960/0x961/0x962 qeth: received an IDX TERMINATE on irq 0x11/0x12 with cause code 0x17 qeth: IDX_ACTIVATE on read channel irq 0x11: negative reply qeth: There were problems in hard-setting up the card. Back to scratch. -- Hilsen/regards Jxrgen Birkhaug Quoting Malcolm Beattie <[EMAIL PROTECTED]>: <...> 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. > <...>
Re: HiperSockets and Guest LAN
Hi, > Notice that VM shows that the triple of device numbers 963,964,965 > have been switched around to the order 964,965,963 in order for the > first even number to become the CTL-READ device. The error message > from your Linux guest was > > qeth: Trying to use card with devnos 0x963/0x964/0x965 > > qeth: received an IDX TERMINATE on irq 0x14/0x15 with cause code 0x08 > > qeth: IDX_ACTIVATE on read channel irq 0x14: negative reply > > qeth: There were problems in hard-setting up the card. > and it may be worth checking whether Linux has decided to switch > around the device numbers in the same way, perhaps by checking in > /proc/subchannels or /proc/chandev whether subchannel 0x14 really > is the control 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. qeth tries to re-order 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 they seem to be fine for odd addresses. > 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 a different portname and so on (which is case sensitive and so > may be worth checking too: even if your OS/390 people see/quote it > in upper case it's possible that the underlying portname could be > lower case). Afaik HiperSockets don't require a portname (not sure about GuestLan, though) - but it shouldn't hurt to specify one. Portnames are always upper case. Mit freundlichen Grüßen/Regards Cornelia Huck Linux for zSeries Development IBM Deutschland Entwicklung GmbH Email: [EMAIL PROTECTED] Phone: ext. +49(0)7031/16-4837, int. *120-4837
Re: HiperSockets and Guest LAN
Jxrgen Birkhaug writes: > > Quoting Malcolm Beattie <[EMAIL PROTECTED]>: > > > > > > > > > > Better make that triple of device numbers start on an even boundary. > > > > > > --Malcolm > > Why? I'm sure I've seen somewhere that it's a requirement but I can't remember exactly which part of the system requires it and the only reference I can find at the moment is one which only mentions the requirement for OSE and not OSD (i.e. for non-QDIO). However, something does look a bit odd about your new try: > Adapter 0963 Type: HIPER Name: UNASSIGNED Devices: 3 > Port 0 MAC: 00-04-AC-00-00-0C LAN: SYSTEM LNXLAN02MFS: 16384 > Connection Name: HALLOLE State: Session Established > Device: 0964 Unit: 001 Role: CTL-READ > Device: 0965 Unit: 002 Role: CTL-WRITE > Device: 0963 Unit: 000 Role: DATA Notice that VM shows that the triple of device numbers 963,964,965 have been switched around to the order 964,965,963 in order for the first even number to become the CTL-READ device. The error message from your Linux guest was > qeth: Trying to use card with devnos 0x963/0x964/0x965 > qeth: received an IDX TERMINATE on irq 0x14/0x15 with cause code 0x08 > qeth: IDX_ACTIVATE on read channel irq 0x14: negative reply > qeth: There were problems in hard-setting up the card. and it may be worth checking whether Linux has decided to switch around the device numbers in the same way, perhaps by checking in /proc/subchannels or /proc/chandev whether subchannel 0x14 really is the control 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 a different portname and so on (which is case sensitive and so may be worth checking too: even if your OS/390 people see/quote it in upper case it's possible that the underlying portname could be lower case). Setting up QDIO/Hipersockets connections have quite a few little subtle requirements and getting any of them wrong can lead to the sort of errors you're seeing. It's a bit of nuisance but usually it's just a question of checking every little thing one more time to find the one that you're running into. --Malcolm -- Malcolm Beattie <[EMAIL PROTECTED]> Linux Technical Consultant IBM EMEA Enterprise Server Group... ...from home, speaking only for myself
Re: HiperSockets and Guest LAN
Why? -- Jxrgen Quoting Malcolm Beattie <[EMAIL PROTECTED]>: > > Better make that triple of device numbers start on an even boundary. >
Re: HiperSockets and Guest LAN
Why? -- Hilsen/regards Jxrgen Birkhaug Quoting Malcolm Beattie <[EMAIL PROTECTED]>: > > Better make that triple of device numbers start on an even boundary. > > --Malcolm
Re: HiperSockets and Guest LAN
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 were developing the CP simulation code at the same time the hardware group was developing the HiperSockets millicode. Our final adjustments were too late to make the GA tape. CP APAR VM62958 PTF UM30140 which includes the fix for (probably) this same problem Device indexing was one of the last-minute changes and the device index passed to the driver via the CCW interface was incorrect in most cases. When this service has been applied, you should be able to issue CP QUERY VMLAN and see "VM62938" listed as the latest service. Also, Malcolm is correct in pointing out that "addparms" should be "add_parms" (I should remember this by now). That could also cause an initialization failure. Regards, Dennis Musselwhite ([EMAIL PROTECTED]) IBM Corporation -- z/VM Development -- CP Network Simulation
Re: HiperSockets and Guest LAN
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: received an IDX TERMINATE on irq 0x14/0x15 with cause code 0x08 > qeth: IDX_ACTIVATE on read channel irq 0x14: negative reply > qeth: There were problems in hard-setting up the card. > - > > At least it is a different cause code. Better make that triple of device numbers start on an even boundary. --Malcolm -- Malcolm Beattie <[EMAIL PROTECTED]> Linux Technical Consultant IBM EMEA Enterprise Server Group... ...from home, speaking only for myself
Re: HiperSockets and Guest LAN
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: received an IDX TERMINATE on irq 0x14/0x15 with cause code 0x08 qeth: IDX_ACTIVATE on read channel irq 0x14: negative reply qeth: There were problems in hard-setting up the card. - At least it is a different cause code. As I have mentioned earlier I have little or no knowledge of z/VM, but I have been given access. Here's how it looks from the z/VM end: - Adapter 0963 Type: HIPER Name: UNASSIGNED Devices: 3 Port 0 MAC: 00-04-AC-00-00-0B LAN: SYSTEM LNXLAN02 MFS: 16384 Connection Name: HALLOLE State: Startup Device: 0963 Unit: 000 Role: CTL-READ Unassigned Devices: Device: 0964 Unit: 001 Role: Unassigned Device: 0965 Unit: 002 Role: Unassigned - Any ideas on how to troubleshoot this problem? -- Best regards/hilsen Jxrgen Birkhaug Quoting Malcolm Beattie <[EMAIL PROTECTED]>: > > > That "addparms" needs to be "add_parms" instead (i.e. with an underscore). > > --Malcolm > > -- > Malcolm Beattie <[EMAIL PROTECTED]> > Linux Technical Consultant > IBM EMEA Enterprise Server Group... > ...from home, speaking only for myself > >
Re: HiperSockets and Guest LAN
Jxrgen Birkhaug writes: > 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: > [...] > /etc/chandev.conf contains: > > noauto;qeth0,0x0960,0x0961,0x0962;addparms,0x10,0x0960,0x0962,portname:LNXLAN02 That "addparms" needs to be "add_parms" instead (i.e. with an underscore). --Malcolm -- Malcolm Beattie <[EMAIL PROTECTED]> Linux Technical Consultant IBM EMEA Enterprise Server Group... ...from home, speaking only for myself
Re: HiperSockets and Guest LAN
Hi Dennis Thanks for your reply. Below are details of the different cp commands that you requested: CP QUERY CPLEVEL z/VM Version 4 Release 2.0, service level (64-bit) Generated at 08/29/01 18:40:17 EST IPL at 11/20/02 10:42:05 EST CP QUERY VMLAN VMLAN general activity: PERSISTENT Limit: INFINITE Current: 1 TRANSIENT Limit: INFINITE Current: 1 CP QUERY NIC DETAIL Adapter 0960 Type: QDIO Name: UNASSIGNED Devices: 3 Port 0 MAC: 00-04-AC-00-00-0A LAN: SYSTEM LNXLAN02MFS: 16384 Connection Name: HALLOLE State: Startup Device: 0960 Unit: 000 Role: CTL-READ Unassigned Devices: Device: 0961 Unit: 001 Role: Unassigned Device: 0962 Unit: 002 Role: Unassigned Adapter 0963 Type: HIPER Name: UNASSIGNED Devices: 3 Port 0 MAC: 00-04-AC-00-00-0C LAN: SYSTEM LNXLAN02MFS: 16384 Connection Name: HALLOLE State: Session Established Device: 0964 Unit: 001 Role: CTL-READ Device: 0965 Unit: 002 Role: CTL-WRITE Device: 0963 Unit: 000 Role: DATA CP QUERY LAN LNXLAN02 OWNER SYSTEM DETAIL LAN SYSTEM LNXLAN02Type: QDIO Active: 4 MAXCONN: INFINITE PERSISTENT UNRESTRICTED MFS: 16384 Adapter Owner: RATATOSK NIC: 0960 Name: UNASSIGNED Adapter Owner: TCPIPNIC: 0960 Name: LNXLAN02 Adapter Owner: URD NIC: 0960 Name: UNASSIGNED Adapter Owner: URD NIC: 0963 Name: UNASSIGNED The guest linux that I am currently working with is named "URD". -- Best regards, Jxrgen Birkhaug Quoting Dennis Musselwhite <[EMAIL PROTECTED]>: > Hi... > > I think your chandev.conf file is OK (but I am no expert on driver > configuration). > > The IDX Termination code 0x17 usually means that the data device could not > be found, > or it belongs to a different adapter. > > If you can access the primary 3270 virtual console where you logon and IPL > your Linux > system, there are some CP commands that might provide more insight: > > (1) What version of CP are you running? Enter: > > CP QUERY CPLEVEL > > I would expect to see something like this: > > z/VM Version 4 Release 2.0, service level (64-bit) > Generated at 10/28/02 14:32:45 EST > IPL at 10/30/02 12:04:46 EST > > If you get an error message instead, then you may need to use a different > method to > enter CP commands. CP is the layer that runs between your Linux system and > the > real machine. One way to enter a CP command is: > Signal PA1 (Programmed Attention 1) from your telnet-3270 client. > This > should put your session in CP READ status (displayed in the lower > right corner of the 3270 session). The command that you enter > in CP READ status goes directly to CP. Depending on your virtual > machine settings, you may go back to a VM status after each command. > If that is the case, you will need to signal PA1 before each command. > If you STAY in CP READ after each command, enter "CP BEGIN" after > the last command to get your virtual machine running again. > > (2) What level of VM Guest LAN service has been installed? Enter: > > CP QUERY VMLAN > > (3) How is your adapter defined? Enter: > > CP QUERY NIC DETAIL > > (4) How is the LAN defined? Not relevent to this problem, but for future > reference, > your adapter at 0960 may indicate it is connected to a LAN identified by > two tokens. > The first is the ownerid, the second is the lanname. If (for example) > ownerid = SYSTEM > and lanname = LNXLAN02 then you could find out who is currently connected > to that > LAN with the command: > > CP QUERY LAN LNXLAN02 OWNER SYSTEM DETAIL > > (4) Don't forget to enter CP BEGIN if you are still in CP READ status. > > > Please post the results. > > Regards, > Dennis Musselwhite ([EMAIL PROTECTED]) > IBM Corporation -- z/VM Development -- CP Network Simulation > > > Jxrgen Birkhaug <[EMAIL PROTECTED]>@VM.MARIST.EDU> 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 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: > > -- > IPv6 v0.8 for NET4.0 > IPv6 over IPv4 tunneling driver > 802.1Q VLAN Support v1.7 Ben Greear <[EMAIL PROTECTED]&g
Re: HiperSockets and Guest LAN
Hi... I think your chandev.conf file is OK (but I am no expert on driver configuration). The IDX Termination code 0x17 usually means that the data device could not be found, or it belongs to a different adapter. If you can access the primary 3270 virtual console where you logon and IPL your Linux system, there are some CP commands that might provide more insight: (1) What version of CP are you running? Enter: CP QUERY CPLEVEL I would expect to see something like this: z/VM Version 4 Release 2.0, service level (64-bit) Generated at 10/28/02 14:32:45 EST IPL at 10/30/02 12:04:46 EST If you get an error message instead, then you may need to use a different method to enter CP commands. CP is the layer that runs between your Linux system and the real machine. One way to enter a CP command is: Signal PA1 (Programmed Attention 1) from your telnet-3270 client. This should put your session in CP READ status (displayed in the lower right corner of the 3270 session). The command that you enter in CP READ status goes directly to CP. Depending on your virtual machine settings, you may go back to a VM status after each command. If that is the case, you will need to signal PA1 before each command. If you STAY in CP READ after each command, enter "CP BEGIN" after the last command to get your virtual machine running again. (2) What level of VM Guest LAN service has been installed? Enter: CP QUERY VMLAN (3) How is your adapter defined? Enter: CP QUERY NIC DETAIL (4) How is the LAN defined? Not relevent to this problem, but for future reference, your adapter at 0960 may indicate it is connected to a LAN identified by two tokens. The first is the ownerid, the second is the lanname. If (for example) ownerid = SYSTEM and lanname = LNXLAN02 then you could find out who is currently connected to that LAN with the command: CP QUERY LAN LNXLAN02 OWNER SYSTEM DETAIL (4) Don't forget to enter CP BEGIN if you are still in CP READ status. Please post the results. Regards, Dennis Musselwhite ([EMAIL PROTECTED]) IBM Corporation -- z/VM Development -- CP Network Simulation Jørgen Birkhaug <[EMAIL PROTECTED]>@VM.MARIST.EDU> 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 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: -- IPv6 v0.8 for NET4.0 IPv6 over IPv4 tunneling driver 802.1Q VLAN Support v1.7 Ben Greear <[EMAIL PROTECTED]> All bugs added by David S. Miller <[EMAIL PROTECTED]> qdio: loading QDIO base support version 2 ($Revision: 1.120.2.1 $/$Revision: 1.56.2.2 $) debug: qdio_setup: new level 2 debug: qdio_labs: new level 2 debug: qdio_sense: new level 2 debug: qdio_trace: new level 2 qeth: loading qeth S/390 OSA-Express driver ($Revision: 1.260.2.13 $/$Revision: 1.86.2.2 $/$Revision: 1.31 $:IPv6:VLAN) qeth: allocated 0 spare buffers debug: qeth_setup: new level 3 debug: qeth_misc: new level 2 debug: qeth_data: new level 2 debug: qeth_control: new level 2 debug: qeth_sense: new level 2 debug: qeth_qerr: new level 2 debug: qeth_trace: new level 2 qeth: Trying to use card with devnos 0x960/0x961/0x962 qeth: received an IDX TERMINATE on irq 0x11/0x12 with cause code 0x17 qeth: IDX_ACTIVATE on read channel irq 0x11: negative reply qeth: There were problems in hard-setting up the card. -- /etc/chandev.conf contains: noauto;qeth0,0x0960,0x0961,0x0962;addparms,0x10,0x0960,0x0962,portname:LNXLAN02 I have been given these paramaters by the kind people in charge of our z/VM (ie. i know linux, not so much mainframes and z/VM), and if needed I could probably provide more details of the hardware and how things are "coupled". -- Best regards/hilsen Jxrgen Birkhaug
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 with chandev for some time but to no avail. insmod qeth returns: -- IPv6 v0.8 for NET4.0 IPv6 over IPv4 tunneling driver 802.1Q VLAN Support v1.7 Ben Greear <[EMAIL PROTECTED]> All bugs added by David S. Miller <[EMAIL PROTECTED]> qdio: loading QDIO base support version 2 ($Revision: 1.120.2.1 $/$Revision: 1.56.2.2 $) debug: qdio_setup: new level 2 debug: qdio_labs: new level 2 debug: qdio_sense: new level 2 debug: qdio_trace: new level 2 qeth: loading qeth S/390 OSA-Express driver ($Revision: 1.260.2.13 $/$Revision: 1.86.2.2 $/$Revision: 1.31 $:IPv6:VLAN) qeth: allocated 0 spare buffers debug: qeth_setup: new level 3 debug: qeth_misc: new level 2 debug: qeth_data: new level 2 debug: qeth_control: new level 2 debug: qeth_sense: new level 2 debug: qeth_qerr: new level 2 debug: qeth_trace: new level 2 qeth: Trying to use card with devnos 0x960/0x961/0x962 qeth: received an IDX TERMINATE on irq 0x11/0x12 with cause code 0x17 qeth: IDX_ACTIVATE on read channel irq 0x11: negative reply qeth: There were problems in hard-setting up the card. -- /etc/chandev.conf contains: noauto;qeth0,0x0960,0x0961,0x0962;addparms,0x10,0x0960,0x0962,portname:LNXLAN02 I have been given these paramaters by the kind people in charge of our z/VM (ie. i know linux, not so much mainframes and z/VM), and if needed I could probably provide more details of the hardware and how things are "coupled". -- Best regards/hilsen Jxrgen Birkhaug
Re: HiperSockets
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 or you have the option of defining a QDIO adapter which supports multicast and broadcast within the QDIO Guest LAN. If you were depending on routed to install the SUSE7 IP Address in your TCPIP routing table, that might cause ping to fail. I am not skilled with the configuration options, but if you describe the way you have configured the HiperSockets DEVICE/LINK on the TCPIP side, perhaps other readers can offer suggestions that will help. Regards, Dennis Musselwhite ([EMAIL PROTECTED]) IBM Corporation -- z/VM Development -- CP Network Simulation
Re: HiperSockets
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 world
Re: HiperSockets
Hi, In the past (prior to z/VM 4.2.0) the CP COUPLE command was only used to connect simulated CTCA adapters. For example: cp define ctca 500 cp couple 500 to othervm 500 This "connects the wires" between your virtual 500 and the other user's virtual 500. With z/VM 4.2.0 we also use the CP COUPLE command to connect your simulated network adapter to the VM Guest LAN. For example, let us assume somebody (USERX) has defined a Guest LAN: cp define lan sample Now your CP system has a Guest LAN named "sample" owned by "USERX", and you could use the COUPLE command to connect a virtual NIC to that Guest LAN: cp define nic 800 cp couple 800 to userx sample This "connects the wires" between your virtual adapter and the simulated LAN segment. You should define and couple before the CP IPL command that starts the guest operating system. Regards, Dennis Musselwhite ([EMAIL PROTECTED]) IBM Corporation -- z/VM Development -- CP Network Simulation Eddie Chen <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 08/26/2002 12:01:46 PM Please respond to Linux on 390 Port <[EMAIL PROTECTED]> Sent by:Linux on 390 Port <[EMAIL PROTECTED]> To:[EMAIL PROTECTED] cc: Subject:Re: [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 are not talking to each other. on the LINUX userid: -cp define nic a004 -cp couple a004 system
Re: HiperSockets
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 system (e.g. TCPIP), any Class B userid can modify the LAN, but your TCPIP user WITHOUT CLASS B priviliges can also modify that LAN. If, for example, this is a restricted LAN, your TCPIP user can grant or revoke users with the CP SET LAN command. One potential disadvantage of a user-owned LAN in a production environment is that the user-owned LAN is considered transient. If the owner signs off, AND all members sign off or uncouple, the LAN will be detached by the system. You can circumvent this by adding the DEFINE LAN for a user-owned LAN to the SYSTEM CONFIG file. When the LAN is created from the SYSTEM CONFIG file it is considered persistent (even if it is not owned by SYSTEM). This is probably more than you wanted to know about SYSTEM-owned verses user-owned Guest LAN. In an earlier note, you show the following response from QUERY LAN DETAILS: cp q lan detail LAN SYSTEM HSI1Type: HIPERS Active: 2 MAXCONN: INFINITE PERSISTENT UNRESTRICTED MFS: 16384 Adapter Owner: SUSE7NIC: A004 Name: HSIPORT 192.168.138.207 Adapter Owner: TCPIPNIC: A000 Name: HIPERPEC 192.168.138.201 192.168.254.194 This indicates that both users SUSE7 and TCPIP have properly initialized their virtual adapters. All three IP Addresses are visible on the Guest LAN. I do not recall if you mentioned what you are doing to check for connectivity between SUSE7 and TCPIP. Your routing table from SUSE7 should show 192.168.138.201 as the default gateway for hsi0. The gateway table from TCPIP should show that an address of 192.168.138.207 should go to the LINK name that you've assigned to the A000 device in your TCPIP profile. This sounds like the sort of problem you could have if (for example) that other address (192.168.254.194) happened to be your CTCA link address, and if your CTCA link happened to be the DEFAULT NET for the TCPIP stack. There are probably other ways that a configuration error could account for this (I'm familiar with this one because something similar happened to me on a test system recently). Regards, Dennis Musselwhite ([EMAIL PROTECTED]) IBM Corporation -- z/VM Development -- CP Network Simulation
Re: HiperSockets
Then I stand corrected. This is what not actively supporting VM gets me. Sigh. Still, I learned something new today. Thanks. Mark Post -Original Message- From: Adam Thornton [mailto:[EMAIL PROTECTED]] Sent: Monday, August 26, 2002 12:35 PM To: [EMAIL PROTECTED] Subject: Re: 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 COUPLE ADDR OWNER LANNAME Adam
Re: HiperSockets
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 (TCP/IP) 192.159.81.14 ===Other System(network) linux05192.168.138.209 =| linux08 192.168.138.220 | TCP/IP linux02 192.168.138.203 | on linux: side I added route add default gw 192.168.134.201/24
Re: 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 COUPLE ADDR OWNER LANNAME Adam
Re: HiperSockets
Can I assume it's the "couple" command that bind/joint the guest LAN???
Re: 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 are not talking to each other. on the LINUX userid: -cp define nic a004 -cp couple a004 system
Re: HiperSockets
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). Mark Post -Original Message- From: Eddie Chen [mailto:[EMAIL PROTECTED]] Sent: Monday, August 26, 2002 9:51 AM To: [EMAIL PROTECTED] Subject: Re: HiperSockets Can I assume it's the "couple" command that bind/joint the guest LAN???
Re: HiperSockets
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 be specified as primary router. Alan Altmark Sr. Software Engineer IBM z/VM Development
HiperSockets
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 Enabled for QDIO data transfers >17:25:11 DTCOSD246I HIPERS device HIPERDEC: Assigned IP address >192.168.138.201 >17:25:11 DTCOSD234I ToOsd: TCPIP host is not set as a router for port >HIPERPEC >17:25:11 DTCOSD246I HIPERS device HIPERDEC: Assigned IP address >192.168.254.194 >17:25:11 DTCSTM213I Telnet server: Global connection to *CCS CP System >Service e >stablished >17:25:11 DTCSTM216I Telnet server: First line of *CCS logo is: z/VM ONLI > --ZVMV4R20--PRESS BREAK KEY TO BEGIN SESSION > > the query LAN > > cp q lan detail >LAN SYSTEM HSI1Type: HIPERS Active: 2 MAXCONN: INFINITE > PERSISTENT UNRESTRICTED MFS: 16384 >Adapter Owner: SUSE7NIC: A004 Name: HSIPORT > 192.168.138.207 >Adapter Owner: TCPIPNIC: A000 Name: HIPERPEC > 192.168.138.201 192.168.254.194 > > I still having problem connecting SUSE7 to TCPIP stack > __ Marcy Cortes, VM Systems Programming, 415-243-6343
HiperSockets
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 192.168.138.201 17:25:11 DTCOSD234I ToOsd: TCPIP host is not set as a router for port HIPERPEC 17:25:11 DTCOSD246I HIPERS device HIPERDEC: Assigned IP address 192.168.254.194 17:25:11 DTCSTM213I Telnet server: Global connection to *CCS CP System Service e stablished 17:25:11 DTCSTM216I Telnet server: First line of *CCS logo is: z/VM ONLINE --ZVMV4R20--PRESS BREAK KEY TO BEGIN SESSION the query LAN cp q lan detail LAN SYSTEM HSI1Type: HIPERS Active: 2 MAXCONN: INFINITE PERSISTENT UNRESTRICTED MFS: 16384 Adapter Owner: SUSE7NIC: A004 Name: HSIPORT 192.168.138.207 Adapter Owner: TCPIPNIC: A000 Name: HIPERPEC 192.168.138.201 192.168.254.194 I still having problem connecting SUSE7 to TCPIP stack
Re: Strange TCP (?) behavior with OSA-GigE/HiperSockets
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 added to /proc/qeth_ipa_takeover ? Are you using dynamic routing at all (Zebra / gated)? What about MTU sizes and/or are you using Path MTU discovery on all stacks involved? Ciao Mark -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Adam Thornton Sent: 01 July 2002 16:25 To: [EMAIL PROTECTED] Subject: Strange TCP (?) behavior with OSA-GigE/HiperSockets 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 is instantaneous. But if I SSH directly to the guests on the HiperSockets, it works but the connection is unresponsive and jerky; it feels like I'm typing over a transatlantic line. Everything gets there eventually but it sometimes takes a few tenths of a second. I'm guessing that this is something to do with TCP buffering packets as they pass from one interface to another, since the problem doesn't exist with ICMP packets. Further I suspect that--since I'm running the SuSE 2.4.7-timer kernel--it may have something to do with TCP not flushing its buffers on each timer tick, since there are no timer ticks. This, however, is a guess which I have not yet attempted to construct a test case for. Has anyone else seen this behavior? Adam
Strange TCP (?) behavior with OSA-GigE/HiperSockets
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 is instantaneous. But if I SSH directly to the guests on the HiperSockets, it works but the connection is unresponsive and jerky; it feels like I'm typing over a transatlantic line. Everything gets there eventually but it sometimes takes a few tenths of a second. I'm guessing that this is something to do with TCP buffering packets as they pass from one interface to another, since the problem doesn't exist with ICMP packets. Further I suspect that--since I'm running the SuSE 2.4.7-timer kernel--it may have something to do with TCP not flushing its buffers on each timer tick, since there are no timer ticks. This, however, is a guess which I have not yet attempted to construct a test case for. Has anyone else seen this behavior? Adam
coding hipersockets and OSA cards in a single LPAR
FYI,as I know it will come up eventually in this forum, so I've included an example: The system is 2.4.7, SuSE GA (10/30/01 kernel) I have a hipersocket connection, 2 OSA GB express, and 1 OSA FEX installed on my zSeries in 3 LPARS. To get them all working at the same time, I coded the following (example from 1 LPAR): In /etc/chandev.conf noauto add_parms,0x10,0x7e00,0x7e02,portname:HIPR7E00 # portnames for all entries must agree between hosts add_parms,0x10,0x4000,0x4002,portname:QDIO4000 # I happen in insert the device address for clarity add_parms,0x10,0x4300,0x4302,portname:QDIO4300 add_parms,0x10,0x4d00,0x4d02,portname:QDIO4D00 qeth0,0x7e00,0x7e01,0x7e02,4096 #Hipersocket - genned to a free channel qeth1,0x4000,0x4001,0x4002,0,0,polltime:0 #Gigabit Express - genned OSD qeth2,0x4300,0x4301,0x4302,0,0,polltime:0 #Gibabit Express - genned OSD qeth3,0x4d00,0x4d01,0x4d02,0,0,polltime:0 #FE Express - genned OSD in /etc/modulles.conf alias hsi0 qeth alias eth1 qeth alias eth2 qeth alias eth3 qeth in /etc/rc.config # # networking # # number of network cards: "_0" for one, "_0 _1 _2 _3" for four cards # # _0 - hsi0 - hipersocket 7E00 # _1 - eth1 - VLAN1 # _2 - eth2 - VLAN3 # _3 - eth3 - VLAND # NETCONFIG="_0 _1 _2 _3" # # IP Adresses # IPADDR_0="10.32.254.11" IPADDR_1="10.32.81.10" IPADDR_2="10.32.82.10" IPADDR_3="10.32.90.140" # # network device names (e.g. "eth0") # NETDEV_0="hsi0" NETDEV_1="eth1" NETDEV_2="eth2" NETDEV_3="eth3" # IFCONFIG_0="10.32.254.11 broadcast 10.32.254.255 netmask 255.255.255.0 up" IFCONFIG_1="10.32.81.10 broadcast 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. Regards, Jim Linux S/390-zSeries Support, SEEL, IBM Silicon Valley Labs t/l 543-4021, 408-463-4021, [EMAIL PROTECTED] *** Grace Happens ***
ip route command with HiperSockets
So I want to use my 2.4.7 system to have a default default route and a backup default route, but to route statically rather than using OSPF or similar. I think this should be ip route add default via 10.90.2.1 nexthop via 10.90.2.2 But I get RTNETLINK answeres: Invalid argument. What is the right incantation for this guy? The host is at 10.90.2.119. He's on a HiperSockets interface, which is his only network interface. 10.90.2.1 and 10.90.2.2 should be his routers, in that order--only if 10.90.2.1 does not work should he go to 10.90.2.2 to get out. All of 10.90.2.0 is on the same guest LAN and is directly accessible. Adam
Code Drop - glibc 2.2.5, glibc 2.2.4/5 + binutils bug-fixes, Kernel 2.4.7 qdio/qeth OCOs with HiperSockets bug-fix
Linux for S/390 & zSeries: Please check out the DeveloperWorks page at: http://www10.software.ibm.com/developerworks/opensource/linux390/whatsnew.shtml On the Recommended level 2.4.7 page at: http://www10.software.ibm.com/developerworks/opensource/linux390/current2_4.shtml you will find: - 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 _ IBM Deutschland Entwicklung GmbH, Schönaicher Str. 220 D-71032 Böblingen eServer Software Management, D4357, Intern: 71032-06, Tel. 902-2088 Tel. ++49-(0)7031-16-2088, Fax. 07031-16-3456, OV/VM: IBMDE(WIRBSER) Internet: [EMAIL PROTECTED]
Re: SLES Beta and Hipersockets ?
Regards, Dennis Musselwhite ([EMAIL PROTECTED]) IBM Corporation -- z/VM Development -- CP Network Simulation "Philip J. Tully" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 02/13/2002 09:53:40 AM Please respond to Linux on 390 Port <[EMAIL PROTECTED]> Sent by:Linux on 390 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 >fixes to z/VM CP and z/VM TCPIP. There *was* a recent change to the qdio/qeth drivers which had to be coordinated with CP APAR VM62938 and TCPIP APAR PQ51738 but if the qdio/qeth driver had been the problem I would have expected it to fail before it had the chance to send an IP Address to the adapter. I would be surprised if either of those RPM packages included a new qdio.o or qeth.o executable... but then I've been surprised before :-} Regards, Dennis Musselwhite ([EMAIL PROTECTED]) IBM Corporation -- z/VM Development -- CP Network Simulation
Re: SLES Beta and Hipersockets ?
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/psdb/ sends users over to sdb.suse.de/en/psdb/... so these are probably equivalent. (3) I don't have the support package, but I want to point people in this direction if *they* are authorized for this service. I wouldn't worry about k_deflt.rpm and k_deflt-20011210.rpm being the same... k_deflt.rpm is probably intended to be a symlink of whatever is the most recent k_deflt-*.rpm. Thank You, Dennis Musselwhite ([EMAIL PROTECTED]) IBM Corporation -- z/VM Development -- CP Network Simulation
Re: SLES Beta and Hipersockets ?
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 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 problem as well. > > I have a couple of questions (I'm trying to compile a list > of known problems and solutions for Guest LAN). > > (1) Would it be safe to say this was a bug in the kernel > verses a bug in the qdio or qeth drivers? > > (2) Is http://support.suse.de/psdb/ the SuSE Maintenance site > that you (Jeremy) are talking about? > > (3) Would the URL and the list of RPMs (k_deflt.rpm and > kernel-source.rpm) be sufficient to direct somebody else > to the right service? (I would go looking around in > there, but I don't have a copy of SLES7 so I have no > product registration code to gain entry) > > Thanks, > Dennis Musselwhite ([EMAIL PROTECTED]) > z/VM CP Development
Re: SLES Beta and Hipersockets ?
(1) Would it be safe to say this was a bug in the kernel verses a bug in the qdio or qeth drivers? - SUSE words it as a kernel fix. But it addresses numerous issues not just the hipersocket/guest LAN issues. " Title: Bugfix update of Linux kernel 2.4.7 for S/390 " Our specific interest 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 SUSE to access this DL area. the links are below to obtain the files. After much debate we determined that the k_deflt.rpm and k_deflt-20011210.rpm files are identical. Not sure why they give links to both. Here is the text of the document Title: Bugfix update of Linux kernel 2.4.7 for S/390 ___ Applies to Product(s): SuSE Linux Enterprise Server 7 for S/390 and zSeries Package: images/k_deflt,d2/kernel-source Architecture: S/390 Release: 20011210 Obsoletes: none Indications This update should be installed. Contraindications None. Problem description The new kernel image fixes the following problems: * Kernel crash (with kernel message 'kernel BUG at fcntl.c:417') due to missing bits in the kernel header file asm/siginfo.h * Kernel crash with a NULL pointer dereference after formatting a device due to a race condition. * The device interrupt handler of a terminated CCW does not get called under certain circumstances (for example the halt of a long running tape rewind). The process accessing the device will subsequently 'hang' within a system call. * The system locks up in the partition detection on some configurations. The skip of format 4/5/7 labels does not increase the block number of the label block, subsequently the same block gets read over and over again. * Hipersockets do not work under VM. * Poor network throughput on high CPU load. The wake up of a of a process does not cause a preemptive reschedule of the CPU intensive process due to a comparison problem between unsigned integers of different size. * No proper padding of short blocks on Common Disk Layout (CDL) formatted DASDs. * Additional parameters after an add_params statement on Channel Device Layer configurations get ignored. * Insufficient handling of hardware reset events during startup sequence of a new LCS or OSA port. * Missing reset of files in the VM reader on a P/390 system due to a wrong test criterion. * The PFAULT interrupt handler does not check the sub code correctly and terminates without doing anything. * Missing export of symbol dasd_device_from_kdev. * A kernel built without /proc filesystem support panics on boot. (This affects self-compiled kernels only, SuSE kernels have /proc support compiled in.) Solution Please install the updates provided at the location noted below. Installation notes This update is provided as an RPM package that can be installed by using these commands as user root: rpm -Uvh k_deflt.rpm zipl Now shut down the Linux system with: shutdown -h now (substitute 'now' with an appropriate amount of time if you want to give local users a chance to log out before the Linux system goes down.) After the system has been shut down, re-IPL. ___ Please use the following links to download the packages: SuSE Linux Enterprise Server 7 for S/390 and zSeries (s390): http://sdb.suse.de/download/s390/update/SuSE-SLES/7/images/k_deflt-20011210.rpm SuSE Linux Enterprise Server 7 for S/390 and zSeries (s390) (most recent package): http://sdb.suse.de/download/s390/update/SuSE-SLES/7/images/k_deflt.rpm SuSE Linux Enterprise Server 7 for S/390 and zSeries (s390): http://sdb.suse.de/download/s390/update/SuSE-SLES/7/d2/kernel-source-20011210.rpm SuSE Linux Enterprise Server 7 for S/390 and zSeries (s390) (most recent package): http://sdb.suse.de/download/s390/update/SuSE-SLES/7/d2/kernel-source.rpm If you do not have access to above URLs yet please go to http://support.suse.de/psdb/ and follow the directions to get your password mailed to you. You can then access the Maintenance Web with your registration code and the password. Dennis Musselwhite <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 02/13/2002 09:14:15 Please respond to Linux 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 h
Re: SLES Beta and Hipersockets ?
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 problem as well. I have a couple of questions (I'm trying to compile a list of known problems and solutions for Guest LAN). (1) Would it be safe to say this was a bug in the kernel verses a bug in the qdio or qeth drivers? (2) Is http://support.suse.de/psdb/ the SuSE Maintenance site that you (Jeremy) are talking about? (3) Would the URL and the list of RPMs (k_deflt.rpm and kernel-source.rpm) be sufficient to direct somebody else to the right service? (I would go looking around in there, but I don't have a copy of SLES7 so I have no product registration code to gain entry) Thanks, Dennis Musselwhite ([EMAIL PROTECTED]) z/VM CP Development
Re: SLES Beta and HiperSockets ? - now MTU size question
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 <[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 webserving). > >For guests that communicate with *each other* on the guest LAN, a large >MTU is best. When routing traffic to a real LAN, use the MTU of the real >LAN. Otherwise you get packet fragmentation which just steals cycles from >the machine. > >Linux had "dynamic path MTU discovery" so the apache server will >automatically discover the best MTU to use. With this model, feel free to >use a larger MTU on the guest LAN. Fragmentation will occur initially, >but will disappear as Linux reduces the MTU automatically. Just make sure >the initial MTU size specified on the apache server matches the MTU >specified on VM TCP/IP. > >Regards, >Alan > >IBM Senior Software Engineer >z/VM Development, Endicott, NY >Phone 607.752.6027fax 607.752.1497 t/l 852
Re: SLES Beta and HiperSockets ? - now MTU size question
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 webserving). For guests that communicate with *each other* on the guest LAN, a large MTU is best. When routing traffic to a real LAN, use the MTU of the real LAN. Otherwise you get packet fragmentation which just steals cycles from the machine. Linux had "dynamic path MTU discovery" so the apache server will automatically discover the best MTU to use. With this model, feel free to use a larger MTU on the guest LAN. Fragmentation will occur initially, but will disappear as Linux reduces the MTU automatically. Just make sure the initial MTU size specified on the apache server matches the MTU specified on VM TCP/IP. Regards, Alan IBM Senior Software Engineer z/VM Development, Endicott, NY Phone 607.752.6027fax 607.752.1497 t/l 852
Re: SLES Beta and HiperSockets ? - now MTU size question
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
Re: SLES Beta and HiperSockets ? - now MTU size question
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. > >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
Re: SLES Beta and HiperSockets ? - now MTU size quest ion
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 /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
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
Re: SLES Beta and HiperSockets ?
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 >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. This is why I think the drivers are working. The device driver has to jump through numerous initialization hoops to get to the point of registering an IP Address. If there is a mismatch between the adapter support (real or simulated) and the driver, you would normally see it before this point. >hsi0 came up fine and can ping itself, but no one else. The netmask and >MTU are correct. My experience has been that the adapter does not see that ping. Something within the Linux stack recognizes that you are pinging the interface IP Address... and the response is generated without causing any activity for the adapter. >I'm wondering if SuSE shipped a working QDIO driver, because all my >parameters are as far as I can tell correct, and everything works except >actually passing packets, which is the problem we had before we got the >right level of hipersockets on the machine. I have limited experience with Linux. I have seen some failures where the ifup command concludes with "delaying initialization" but in those cases the IP Addresses are not successfully registered with the adapter... but in those cases the QUERY NIC DETAIL did not show IP Addresses. I hope the same was true for you... otherwise it is going to make it very difficult to distinguish between configuration errors and simulation errors :-( >So: has anyone successfully set up SLES beta with the hsi interface? Sorry... I have not used the SLES beta, but I hope somebody on the list will confirm that the HiperSockets drivers work with that distribution. Regards, Dennis Musselwhite ([EMAIL PROTECTED]) z/VM CP Development
Re: SLES Beta and HiperSockets ?
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.255.255.0; broadcast 10.90.3.255. RH and the router agree that they're happy. SLES can't see either of 'em. Adam -- [EMAIL PROTECTED] "My eyes say their prayers to her / Sailors ring her bell / Like a moth mistakes a light bulb / For the moon and goes to hell." -- Tom Waits
Re: SLES Beta and HiperSockets ?
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: SLES Beta 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. hsi0 came up fine and can ping itself, but no one else. The netmask and MTU are correct. I'm wondering if SuSE shipped a working QDIO driver, because all my parameters are as far as I can tell correct, and everything works except actually passing packets, which is the problem we had before we got the right level of hipersockets on the machine. So: has anyone successfully set up SLES beta with the hsi interface? Adam
SLES Beta 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. hsi0 came up fine and can ping itself, but no one else. The netmask and MTU are correct. I'm wondering if SuSE shipped a working QDIO driver, because all my parameters are as far as I can tell correct, and everything works except actually passing packets, which is the problem we had before we got the right level of hipersockets on the machine. So: has anyone successfully set up SLES beta with the hsi interface? Adam
Re: QETH/HiperSockets/Guest Lan.Save me from jumping off a bridge
Thanks Dennis... >> Your PING results indicate that this is NOT happening, so I have to believe >> one of the following: >> (1) linux0 ping to 10.105.1.254 does not go to the hsi0 interface. >> The hsi0 interface address is 10.105.1.250 / 255.255.255.0. >> Is /etc/sysconfig/network script configured with: >> GATEWAYDEV=hsi0 >> GATEWAY=10.105.1.254 >> ?? (1) I can't think of a way to get a sniffer onto this segment to verify this. And I cannot find an /etc/sysconfig/network script. But correct me if I am wrong, even if my default gw is not configured correctly, I in theory from 10.105.1.250/24 should be able to ping 10.105.1.1/24 they are on the same segment and don't need a router. And that doesn't work either. OR: >> (2) tcpip ping response to 10.105.1.250 does not go to the VLAN1 interface. >> If the ping reaches TCPIP but the stack sends the response back out >> the wrong interface (maybe out the 10.100.1.2 interface?) this would >> also result in a ping failure. Are you sure the TCPIP configuration >> is set to direct all 10.105.1.* traffic through 10.105.1.254 ? >> ?? (2) I am reasonably certain that routing at the VM level is correct. We tried to eliminate the VM side of the configuration by bringing up a second VM IP stack. This second stack happily communicated with the 10.105.1.254 address and vice versa. So the primary stack can route to the 10.105.1 network. Also a netstat gate from the primary stack shows: netstat gate VM TCP/IP Netstat Level 420 Known gateways: NetAddress FirstHopFlgs PktSz Subnet Mask Subnet Value Link -- - --- -- Default 10.100.0.254UGS Def OSA2 10.0.0.0US 1500 0.255.0.0 0.100.0.0 OSA2 10.100.7.1 HS 1500 HOSTC701 10.100.7.2 HS 1500 HOSTD702 10.100.7.3 HS 1500 HOSTC703 10.100.7.4 HS 1500 HOSTD704 10.100.7.5 HS 1500 HOSTC705 10.100.7.6 HS 1500 HOSTD706 10.100.7.7 HS 1500 HOSTC707 10.100.7.8 HS 1500 HOSTD708 10.100.7.9 HS 1500 HOSTC709 10.100.7.10 HS 1500 HOSTD70A 10.100.7.250HS 1500 HOSTC000 10.0.0.0US 1500 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 off a bridge Hi, Jeremy Warren wrote: > I'm at my wits end... > The water below looks cool and refreshing. I wish I could solve this for you (that water is a lot harder than it looks). Perhaps I can fill in some of the blanks based on your observations of the Guest LAN operation... then maybe the networking experts can figure out the rest. >From either Linux instance it can ping its own interface but no-one else on >the 10.105.1.0 network. I'm reasonably sure these pings to the interface IP Address do not actually go through the adapter, so they don't really count. >So from linux0 >ping 10.105.1.250 - works (but does not really exercise the adapter) >ping 10.105.1.254 - fails >ping 10.105.1.1 - fails >From linux1 >ping 10.105.1.1 - works (but does not really exercise the adapter) >ping 10.105.1.254 - fails >ping 10.105.1.250 - fails >ifconfig for hsi0 shows: >hsi0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > inet addr:10.105.1.250 Mask:255.255.255.0 > inet6 addr: fe80::200:ff:fe00:0/10 Scope:Link > UP RUNNING NOARP MTU:8192 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:0 (0.0 b) TX bytes:728 (728.0 b) > Interrupt:10 >Note that the HW Address is all 00. This seems wrong to me but since I >can't get it to work who knows This should not affect the operation. I agree that it looks odd, 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.c
Re: QETH/HiperSockets/Guest Lan.Save me from jumping off a bridge
Hi, Jeremy Warren wrote: > I'm at my wits end... > The water below looks cool and refreshing. I wish I could solve this for you (that water is a lot harder than it looks). Perhaps I can fill in some of the blanks based on your observations of the Guest LAN operation... then maybe the networking experts can figure out the rest. >From either Linux instance it can ping its own interface but no-one else on >the 10.105.1.0 network. I'm reasonably sure these pings to the interface IP Address do not actually go through the adapter, so they don't really count. >So from linux0 >ping 10.105.1.250 - works (but does not really exercise the adapter) >ping 10.105.1.254 - fails >ping 10.105.1.1 - fails >From linux1 >ping 10.105.1.1 - works (but does not really exercise the adapter) >ping 10.105.1.254 - fails >ping 10.105.1.250 - fails >ifconfig for hsi0 shows: >hsi0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > inet addr:10.105.1.250 Mask:255.255.255.0 > inet6 addr: fe80::200:ff:fe00:0/10 Scope:Link > UP RUNNING NOARP MTU:8192 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:0 (0.0 b) TX bytes:728 (728.0 b) > Interrupt:10 >Note that the HW Address is all 00. This seems wrong to me but since I >can't get it to work who knows This should not affect the operation. I agree that it looks odd, 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: >noauto >ctc0,0xc000,0xc001,0,0 >qeth0,0x0500,0x0501,0x0502,4096 >add_parms,0x10,0x0500,0x0502,portname:VLAN1 >(We tried hsi0 instead of qeth0 and get unknown verb or something similar). This configuration looks OK. I have not tried overriding the memory allocation myself, so you might want to try the default (put "0" instead of "4096" on the qeth0 line. If the channel layer finds HiperSockets devices at these addresses, it will use the "hsi" interface name. >A Q NIC DETAILS from linux0 shows: >CP Q NIC DETAILS >Adapter 0500 Type: HIPER Name: VLAN1 Devices: 3 > Port 0 MAC: 00-04-AC-00-00-11 LAN: SYSTEM VLAN1 MFS: 16384 > Connection Name: HALLOLE State: Session Established >Device: 0500 Unit: 000 Role: CTL-READ >Device: 0501 Unit: 001 Role: CTL-WRITE >Device: 0502 Unit: 002 Role: DATA > Unicast IP Addresses: >10.105.1.250 >Note that I DO have a mac address and the 0500-0502 devices are indeed >connected. >(For folks who have been helping offline the NIC Address changed from 0510 >to 0500 on a SWAG) This looks right... and confirms that /etc/chandev.conf is OK. The fact that you have an IP Address here, and on the QUERY LAN DETAILS is evidence that (1) your /etc/chandev.conf is ok, and (2) the qdio and qeth drivers are working with the simulated NIC devices. >A Q LAN DETAILS from linux0 shows: (At the time this was taken linux1 was >down). >CP Q LAN DETAILS >LAN SYSTEM VLAN1 Type: HIPERS Active: 2 MAXCONN: INFINITE > PERSISTENT UNRESTRICTED MFS: 16384 >Adapter Owner: LINUX0 NIC: 0500 Name: VLAN1 > 10.105.1.250 >Adapter Owner: TCPIPNIC: 0510 Name: VLAN1 > 10.105.1.254 >It appears to me anyway that both linux0 and tcpip are properly into the >guest lan they just wont talk to each other. Which to me points to a linux >config error but I can't figure it out. I agree that the drivers are talking to the Guest LAN. I'm not convinced that the linux configuration is the problem. Given the Q LAN DETAILS above, I can just about guarantee that IF the linux0 stack sent a packet on the LINUX0 500 NIC with a next-hop 10.105.1.254 it would certainly be delivered to the TCPIP 510 NIC. Furthermore... IF the tcpip stack sent a response on this NIC with a next-hop 10.105.1.250 it would be delivered to the LINUX0 500 NIC. Your PING results indicate that this is NOT happening, so I have to believe one of the following: (1) linux0 ping to 10.105.1.254 does not go to the hsi0 interface. The hsi0 interface address is 10.105.1.250 / 255.255.255.0. Is /etc/sysconfig/network script configured with: GATEWAYDEV=hsi0 GATEWAY=10.105.1.254 ?? OR: (2) tcpip ping response to 10.105.1.250 does not go to the VLAN1 interface. If the ping reaches TCPIP but the stack sends the response back out the wrong interface (maybe out the 10.100.1.2 interface?) this would also result in a ping fa
Re: Installing RH 7.2 with Hipersockets
> When I try using the qdio driver, I get a bunch of "attempt to access > beyond end of device" errors. Help? Welcome! Adding the OCO modules grew the (unzipped) initrd beyond the 9216 blocks that apparently is the default with RedHat (the mkocord specifically extends the initrd.img for that). I had more succcess when I specified 'ramdisk_size=10240' in the RedHat parm file. Rob
Installing RH 7.2 with Hipersockets
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 alias hsi0 qeth like I have in my other machines' /etc/modules.conf. How do I do this? My HiperSockets interface is at 0x340-342, and it's on LNXLAN3, if that makes a difference to how I specify the parameters. When I try using the qdio driver, I get a bunch of "attempt to access beyond end of device" errors. Help? Adam
z/VM 4.2 Hipersockets PTFs
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
Hipersockets Red Paper Avialable
IBM's red paper on hipersockets is available at: http://www.redbooks.ibm.com/redpapers/pdfs/redp0160.pdf Regards, Jim Linux S/390-zSeries Support, SEEL, IBM Silicon Valley Labs t/l 543-4021, 408-463-4021, [EMAIL PROTECTED] ** Grace Happens **
