Re: SLES10 LPAR clone - OSA interface not found
<4D5693D 7026D000 cd...@novprvlin0050.provo.novell.com> <4d5a8092026d000ce...@novprvlin0050.provo.novell.com> From: "Lester, Doug" To: Linux on 390 Port X-OriginalArrivalTime: 16 Feb 2011 02:27:56.0040 (UTC) FILETIME=[1EBD7880:01CBCD81] X-OriginatorOrg: harryanddavid.com X-Barracuda-Connect: ch1outboundpool.messaging.microsoft.com[216.32.181.182] X-Barracuda-Start-Time: 1297823279 X-Barracuda-Encrypted: AES128-SHA X-Barracuda-Bayes: INNOCENT GLOBAL 0. 1. -2.0210 X-Barracuda-Virus-Scanned: by Barracuda Spam & Virus Firewall at marist.edu X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using global scores of TAG_LEVEL=3.5 QUARANTINE_LEVEL00.0 KILL_LEVEL=5.5 testsX-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.55457 Rule breakdown below pts rule name description -- -- Hi Mark, I appreciate your advice. It came in handy. Thanks again, Doug -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: Tuesday, February 15, 2011 10:33 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES10 LPAR clone - OSA interface not found >>> On 2/14/2011 at 09:18 PM, Undetermined origin c/o LISTSERV administrator wrote: > I re-did the configuration files for qeth and entered the > following commands to get it working. > > echo 0.0.3200,0.0.3201,0.0.3202 > /sys/bus/ccwgroup/drivers/qeth/group > echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.3200/online > > Many thanks to everyone for their help, Please double-check to make sure your hardware configuration file (/etc/sysconfig/hardware/hwcfg-??) reflects this change. That will make sure the correct definitions are built so that the next time you reboot the system, the NIC will still come up. The simplest method will likely be to use YaST to do this. (Delete and reconfigure.) The number of individual changes to the file make it likely a mistake will be made. You can see what I mean by doing a diff -u /etc/sysconfig/hardware/skel/hwcfg-lcs /etc/sysconfig/hardware/skel/hwcfg-qeth Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SLES10 LPAR clone - OSA interface not found
>>> On 2/14/2011 at 09:18 PM, Undetermined origin c/o LISTSERV administrator wrote: > I re-did the configuration files for qeth and entered the > following commands to get it working. > > echo 0.0.3200,0.0.3201,0.0.3202 > /sys/bus/ccwgroup/drivers/qeth/group > echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.3200/online > > Many thanks to everyone for their help, Please double-check to make sure your hardware configuration file (/etc/sysconfig/hardware/hwcfg-??) reflects this change. That will make sure the correct definitions are built so that the next time you reboot the system, the NIC will still come up. The simplest method will likely be to use YaST to do this. (Delete and reconfigure.) The number of individual changes to the file make it likely a mistake will be made. You can see what I mean by doing a diff -u /etc/sysconfig/hardware/skel/hwcfg-lcs /etc/sysconfig/hardware/skel/hwcfg-qeth Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SLES10 LPAR clone - OSA interface not found
in0050.p rov<4D5582BE 026d000cd...@novprvlin0050.provo.novell.com> <4d5693d7026d000cd...@novprvlin0050.provo.novell.com> From: "Lester, Doug" To: Linux on 390 Port X-OriginalArrivalTime: 15 Feb 2011 02:18:24.0478 (UTC) FILETIME=[9FA647E0:01CBCCB6] X-OriginatorOrg: harryanddavid.com X-Barracuda-Connect: ch1outboundpool.messaging.microsoft.com[216.32.181.185] X-Barracuda-Start-Time: 1297736366 X-Barracuda-Encrypted: AES128-SHA X-Barracuda-Bayes: INNOCENT GLOBAL 0. 1. -2.0210 X-Barracuda-Virus-Scanned: by Barracuda Spam & Virus Firewall at marist.edu X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using global scores of TAG_LEVEL=3.5 QUARANTINE_LEVEL00.0 KILL_LEVEL=5.5 testsX-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.55361 Rule breakdown below pts rule name description -- -- Hi Mark, Helmut, Ursula, Dave, and Sam, I was under the incorrect assumption that all 3 of our LPARS had been configured the same. I checked the guy that does the IO gens and found that of our 3 Linux LPARS, 2 were configured as OSE and the one I was having a problem with was OSD. I re-did the configuration files for qeth and entered the following commands to get it working. echo 0.0.3200,0.0.3201,0.0.3202 > /sys/bus/ccwgroup/drivers/qeth/group echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.3200/online Many thanks to everyone for their help, Doug -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: Saturday, February 12, 2011 11:06 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES10 LPAR clone - OSA interface not found >>> On 2/11/2011 at 06:46 PM, Undetermined origin c/o LISTSERV administrator wrote: > The system I did the initial install is good. See below. I'm not sure > why the CU is different. > > Thanks, > > Doug > > Device Subchan. DevType CU Type Use PIM PAM POM CHPIDs > -- > 0.0.3600 0.0.11C5 /00 3088/60 yes 80 80 FF 0600 > 0.0.3601 0.0.11C6 /00 3088/60 yes 80 80 FF 0600 I'm guessing that your I/O definition for those is different. Check from the z/OS side to see how they're defined. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SLES10 LPAR clone - OSA interface not found
Doug, an OSA-card can be used in non-QDIO mode (OSE) or in QDIO-mode (OSD). Your IOCDS-definition defines the type of your OSA-Express channel to be OSE or OSD. If lscss displays a CU-Type 1731/01, your OSA-Express channel is defined as OSD. In Linux the lcs-driver is responsible for OSE-type channels and the qeth-driver is responsible for OSD-type channels. For OSD-type devices a subchannel-triple is necessary to create a qeth-device, for instance echo 0.0.3200,0.0.3201,0.0.3202 > /sys/bus/ccwgroup/drivers/qeth/group Regards, Ursula Braun, IBM Germany On Fri, 2011-02-11 at 14:57 -0800, Lester, Doug wrote: > Mark, > > This is the lscss output. How do I tell if it is in LCS mode? > > Device Subchan. DevType CU Type Use PIM PAM POM CHPIDs > -- > 0.0.3200 0.0.1103 1732/01 1731/01 80 80 FF 0200 > 0.0.3201 0.0.1104 1732/01 1731/01 80 80 FF 0200 > > Thanks, > > Doug -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SLES10 LPAR clone - OSA interface not found
>>> On 2/11/2011 at 06:46 PM, Undetermined origin c/o LISTSERV administrator wrote: > The system I did the initial install is good. See below. I'm not sure > why the CU is different. > > Thanks, > > Doug > > Device Subchan. DevType CU Type Use PIM PAM POM CHPIDs > -- > 0.0.3600 0.0.11C5 /00 3088/60 yes 80 80 FF 0600 > 0.0.3601 0.0.11C6 /00 3088/60 yes 80 80 FF 0600 I'm guessing that your I/O definition for those is different. Check from the z/OS side to see how they're defined. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SLES10 LPAR clone - OSA interface not found
o.novell .com> From: "Lester, Doug" To: Linux on 390 Port X-OriginalArrivalTime: 11 Feb 2011 23:46:53.0866 (UTC) FILETIME=[F5FBB8A0:01CBCA45] X-OriginatorOrg: harryanddavid.com X-Barracuda-Connect: ch1outboundpool.messaging.microsoft.com[216.32.181.181] X-Barracuda-Start-Time: 1297468016 X-Barracuda-Encrypted: AES128-SHA X-Barracuda-Bayes: INNOCENT GLOBAL 0. 1. -2.0210 X-Barracuda-Virus-Scanned: by Barracuda Spam & Virus Firewall at marist.edu X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using global scores of TAG_LEVEL=3.5 QUARANTINE_LEVEL00.0 KILL_LEVEL=5.5 testsX-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.55066 Rule breakdown below pts rule name description -- -- Mark, The system I did the initial install is good. See below. I'm not sure why the CU is different. Thanks, Doug Device Subchan. DevType CU Type Use PIM PAM POM CHPIDs -- 0.0.3600 0.0.11C5 /00 3088/60 yes 80 80 FF 0600 0.0.3601 0.0.11C6 /00 3088/60 yes 80 80 FF 0600 techlnux:~ # l /sys/bus/ccwgroup/drivers/lcs/ total 0 drwxr-xr-x 2 root root0 Feb 10 12:45 ./ drwxr-xr-x 4 root root0 Feb 10 12:43 ../ lrwxrwxrwx 1 root root0 Feb 11 15:45 0.0.3600 -> ../../../../devices/cu3088/0.0.3600/ --w--- 1 root root 4096 Feb 11 15:45 bind --w--- 1 root root 4096 Feb 10 12:43 group --w--- 1 root root 4096 Feb 11 15:45 unbind -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: Friday, February 11, 2011 3:41 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES10 LPAR clone - OSA interface not found >>> On 2/11/2011 at 05:57 PM, "Lester, Doug" wrote: > This is the lscss output. How do I tell if it is in LCS mode? I don't know yet, or even if it's possible from this display. > Device Subchan. DevType CU Type Use PIM PAM POM CHPIDs > -- > 0.0.3200 0.0.1103 1732/01 1731/01 80 80 FF 0200 > 0.0.3201 0.0.1104 1732/01 1731/01 80 80 FF 0200 Assuming you have a working system, what does /sys/bus/ccwgroup/drivers/lcs/ and lscss look like on that system? Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SLES10 LPAR clone - OSA interface not found
>>> On 2/11/2011 at 05:57 PM, "Lester, Doug" wrote: > This is the lscss output. How do I tell if it is in LCS mode? I don't know yet, or even if it's possible from this display. > Device Subchan. DevType CU Type Use PIM PAM POM CHPIDs > -- > 0.0.3200 0.0.1103 1732/01 1731/01 80 80 FF 0200 > 0.0.3201 0.0.1104 1732/01 1731/01 80 80 FF 0200 Assuming you have a working system, what does /sys/bus/ccwgroup/drivers/lcs/ and lscss look like on that system? Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SLES10 LPAR clone - OSA interface not found
Mark, This is the lscss output. How do I tell if it is in LCS mode? Device Subchan. DevType CU Type Use PIM PAM POM CHPIDs -- 0.0.3200 0.0.1103 1732/01 1731/01 80 80 FF 0200 0.0.3201 0.0.1104 1732/01 1731/01 80 80 FF 0200 Thanks, Doug -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: Friday, February 11, 2011 2:44 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES10 LPAR clone - OSA interface not found >>> On 2/11/2011 at 05:29 PM, "Lester, Doug" wrote: > Thanks, but I get the following error: > > #echo 0.0.3200,0.0.3201 > /sys/bus/ccwgroup/drivers/lcs/group > > echo 0.0.3200,0.0.3201 > > /sys/bus/ccwgroup/drivers/lcs/g<.0.3200,0.0.3201 > > /sys/bus/ccwgroup/drivers/lcs/group > -bash: echo: write error: Invalid argument That's pretty odd. I guess the "lscss" output might tell us something. Perhaps this new interface isn't in LCS mode. > I also tried with the '"' at the end as in your example, but it leaves > me hanging wanting some input and I'm not sure what it needs. That was a cut and paste error on my part. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SLES10 LPAR clone - OSA interface not found
>>> On 2/11/2011 at 05:29 PM, "Lester, Doug" wrote: > Thanks, but I get the following error: > > #echo 0.0.3200,0.0.3201 > /sys/bus/ccwgroup/drivers/lcs/group > > echo 0.0.3200,0.0.3201 > > /sys/bus/ccwgroup/drivers/lcs/g<.0.3200,0.0.3201 > > /sys/bus/ccwgroup/drivers/lcs/group > -bash: echo: write error: Invalid argument That's pretty odd. I guess the "lscss" output might tell us something. Perhaps this new interface isn't in LCS mode. > I also tried with the '"' at the end as in your example, but it leaves > me hanging wanting some input and I'm not sure what it needs. That was a cut and paste error on my part. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SLES10 LPAR clone - OSA interface not found
Mark, Thanks, but I get the following error: #echo 0.0.3200,0.0.3201 > /sys/bus/ccwgroup/drivers/lcs/group echo 0.0.3200,0.0.3201 > /sys/bus/ccwgroup/drivers/lcs/g<.0.3200,0.0.3201 > /sys/bus/ccwgroup/drivers/lcs/group -bash: echo: write error: Invalid argument I also tried with the '"' at the end as in your example, but it leaves me hanging wanting some input and I'm not sure what it needs. Thanks, Doug -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: Friday, February 11, 2011 1:30 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES10 LPAR clone - OSA interface not found >>> On 2/11/2011 at 04:17 PM, "Lester, Doug" wrote: > Helmut, > > I think you are on to something. I didn't find anything of much help > using "dmesg". "lscss |grep -i 3200 " and "lscss |grep -i 3201" show the > devices, but "ls -la /sys/bus/ccwgroup/drivers/lcs/" does not. > > > How do I get the devices to group? echo 0.0.3200,0.0.3201 > /sys/bus/ccwgroup/drivers/lcs/group" echo 1 > /sys/bus/ccwgroup/drivers/lcs/0.0.3200/online Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SLES10 LPAR clone - OSA interface not found
>>> On 2/11/2011 at 04:17 PM, "Lester, Doug" wrote: > Helmut, > > I think you are on to something. I didn't find anything of much help > using "dmesg". "lscss |grep -i 3200 " and "lscss |grep -i 3201" show the > devices, but "ls -la /sys/bus/ccwgroup/drivers/lcs/" does not. > > > How do I get the devices to group? echo 0.0.3200,0.0.3201 > /sys/bus/ccwgroup/drivers/lcs/group" echo 1 > /sys/bus/ccwgroup/drivers/lcs/0.0.3200/online Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SLES10 LPAR clone - OSA interface not found
Mark, Thanks for mentioning Helmut again. It didn't register the first time that I never saw his response. My apologies to Helmut and Dave. For some reason, I never received your emails. I just found them by looking at http://www2.marist.edu/htbin/wlvgl?L=LINUX-VM&LOG=LOG1102. Dave, During the initial install on the LPAR that I cloned, the only choices for the CCW bus interface were QDIO and LCS. QETH wasn't an option. But, I did modify the configuration files for qeth to give it a try. Unfortunately, I got the same results. Helmut, I think you are on to something. I didn't find anything of much help using "dmesg". "lscss |grep -i 3200 " and "lscss |grep -i 3201" show the devices, but "ls -la /sys/bus/ccwgroup/drivers/lcs/" does not. How do I get the devices to group? Thanks everyone, Doug -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: Friday, February 11, 2011 11:28 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES10 LPAR clone - OSA interface not found >>> On 2/11/2011 at 01:14 PM, "Lester, Doug" wrote: > sysconfig-0.50.9-13.60.1 > yast2-sysconfig-2.13.9-0.3 > kernel-default-2.6.16.60-0.74.7 Those are pretty current levels, so the fix for the bug is already on your system. This brings us back to what Helmut suggested: ls -la /sys/bus/ccwgroup/drivers/lcs/ lscss Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SLES10 LPAR clone - OSA interface not found
>>> On 2/11/2011 at 01:14 PM, "Lester, Doug" wrote: > sysconfig-0.50.9-13.60.1 > yast2-sysconfig-2.13.9-0.3 > kernel-default-2.6.16.60-0.74.7 Those are pretty current levels, so the fix for the bug is already on your system. This brings us back to what Helmut suggested: ls -la /sys/bus/ccwgroup/drivers/lcs/ lscss Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SLES10 LPAR clone - OSA interface not found
Hi Mark, It returns the following: sysconfig-0.50.9-13.60.1 yast2-sysconfig-2.13.9-0.3 kernel-default-2.6.16.60-0.74.7 Thanks, Doug -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: Thursday, February 10, 2011 9:53 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES10 LPAR clone - OSA interface not found >>> On 2/10/2011 at 07:48 PM, "Lester, Doug" wrote: > The version is: > > techlnux:~ # cat /etc/SuSE-release > SUSE Linux Enterprise Server 10 (s390x) > VERSION = 10 > PATCHLEVEL = 3 What do you get from this command? rpm -qa | grep -E "kernel|sysconfig" Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SLES10 LPAR clone - OSA interface not found
>>> On 2/10/2011 at 07:48 PM, "Lester, Doug" wrote: > The version is: > > techlnux:~ # cat /etc/SuSE-release > SUSE Linux Enterprise Server 10 (s390x) > VERSION = 10 > PATCHLEVEL = 3 What do you get from this command? rpm -qa | grep -E "kernel|sysconfig" Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SLES10 LPAR clone - OSA interface not found
Mark, The version is: techlnux:~ # cat /etc/SuSE-release SUSE Linux Enterprise Server 10 (s390x) VERSION = 10 PATCHLEVEL = 3 Thanks, Doug -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: Thursday, February 10, 2011 2:19 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES10 LPAR clone - OSA interface not found >>> On 2/10/2011 at 03:32 PM, "Lester, Doug" wrote: > The machine is a zSeries 2086-A04 and the OSA is an OSA-Express Fast > FC2366. OK, so exactly what version of SLES10 are you running? Based on the messages, it doesn't look like the device numbers are being grouped (as first suggested by Helmut). There was a bug in SLES10 that caused such a symptom, but it was fixed in a kernel and udev update. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SLES10 LPAR clone - OSA interface not found
>>> On 2/10/2011 at 03:32 PM, "Lester, Doug" wrote: > The machine is a zSeries 2086-A04 and the OSA is an OSA-Express Fast > FC2366. OK, so exactly what version of SLES10 are you running? Based on the messages, it doesn't look like the device numbers are being grouped (as first suggested by Helmut). There was a bug in SLES10 that caused such a symptom, but it was fixed in a kernel and udev update. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SLES10 LPAR clone - OSA interface not found
Should the device driver be "qeth" and not "lcs"? DJ On 02/10/2011 03:25 PM, Lester, Doug wrote: > Mark, > > I left the additional startup messages out of my previous reply: > > [1A..doneStarting udevd > qdio: loading QDIO base support version2 > NET: Registered protocol family 10 > lo: Disabled Privacy Extensions > IPv6 over IPv4 tunneling driver > qeth: loading qeth S/390 OSA-Express driver > lcs: Loading LCS driver > ..done > Loading required kernel modules > > > The machine is a zSeries 2086-A04 and the OSA is an OSA-Express Fast > FC2366. > > Thanks, > > Doug > > > -Original Message- > From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of > Mark Post > Sent: Thursday, February 10, 2011 11:13 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: SLES10 LPAR clone - OSA interface not found > >>>> On 2/9/2011 at 07:55 PM, "Lester, Doug" > wrote: >> Unfortunately, we do not have z/VM and I am stuck with LPAR >> installations. I am trying to develop a process for cloning from one >> LPAR and installing the clone in another LPAR. >> >> Everything works according to plan except the OSA network card is not >> found. This is where I need help. > > What machine type and OSA type do you have? > > -snip- >> During boot, I get the following messages. >> >> Setting up network interfaces: >> lo >> lo >> IP address: 127.0.0.1/8 >> IP address: 127.0.0.2/8 >> Checking for network time protocol daemon (NTPD): ..unused >> lo >> [1A..done >> Waiting for mandatory devices: lcs-bus-ccw-0.0.3200 __NSC__ >> 17 >> 16 >> 15 >> 14 >> 13 >> 12 >> 11 >> 10 >> 9 >> 8 >> 7 >> 6 >> 5 >> 4 >> 3 >> 2 >> 1 >> 0 >> lcs-bus-ccw-0.0.3200No interface found >> [1A..failedSetting up service network . . . . . . . . . . . . . . >> . ...failed > > The messages that would tell us something would have come before this, > when the kernel is trying to activate the NIC. > > > Mark Post > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SLES10 LPAR clone - OSA interface not found
Mark, I left the additional startup messages out of my previous reply: [1A..doneStarting udevd qdio: loading QDIO base support version2 NET: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver qeth: loading qeth S/390 OSA-Express driver lcs: Loading LCS driver ..done Loading required kernel modules The machine is a zSeries 2086-A04 and the OSA is an OSA-Express Fast FC2366. Thanks, Doug -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: Thursday, February 10, 2011 11:13 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES10 LPAR clone - OSA interface not found >>> On 2/9/2011 at 07:55 PM, "Lester, Doug" wrote: > Unfortunately, we do not have z/VM and I am stuck with LPAR > installations. I am trying to develop a process for cloning from one > LPAR and installing the clone in another LPAR. > > Everything works according to plan except the OSA network card is not > found. This is where I need help. What machine type and OSA type do you have? -snip- > During boot, I get the following messages. > > Setting up network interfaces: > lo > lo > IP address: 127.0.0.1/8 > IP address: 127.0.0.2/8 > Checking for network time protocol daemon (NTPD): ..unused > lo > [1A..done > Waiting for mandatory devices: lcs-bus-ccw-0.0.3200 __NSC__ > 17 > 16 > 15 > 14 > 13 > 12 > 11 > 10 > 9 > 8 > 7 > 6 > 5 > 4 > 3 > 2 > 1 > 0 > lcs-bus-ccw-0.0.3200No interface found > [1A..failedSetting up service network . . . . . . . . . . . . . . > . ...failed The messages that would tell us something would have come before this, when the kernel is trying to activate the NIC. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SLES10 LPAR clone - OSA interface not found
Hi Mark, The machine is a zSeries 2086-A04 and the OSA is an OSA-Express Fast FC2366. Thanks, Doug -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: Thursday, February 10, 2011 11:13 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES10 LPAR clone - OSA interface not found >>> On 2/9/2011 at 07:55 PM, "Lester, Doug" wrote: > Unfortunately, we do not have z/VM and I am stuck with LPAR > installations. I am trying to develop a process for cloning from one > LPAR and installing the clone in another LPAR. > > Everything works according to plan except the OSA network card is not > found. This is where I need help. What machine type and OSA type do you have? -snip- > During boot, I get the following messages. > > Setting up network interfaces: > lo > lo > IP address: 127.0.0.1/8 > IP address: 127.0.0.2/8 > Checking for network time protocol daemon (NTPD): ..unused > lo > [1A..done > Waiting for mandatory devices: lcs-bus-ccw-0.0.3200 __NSC__ > 17 > 16 > 15 > 14 > 13 > 12 > 11 > 10 > 9 > 8 > 7 > 6 > 5 > 4 > 3 > 2 > 1 > 0 > lcs-bus-ccw-0.0.3200No interface found > [1A..failedSetting up service network . . . . . . . . . . . . . . > . ...failed The messages that would tell us something would have come before this, when the kernel is trying to activate the NIC. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SLES10 LPAR clone - OSA interface not found
If that is a normal Ethernet OSA shouldn't it be defined as qeth instead of lcs? Sam Bass -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: Thursday, February 10, 2011 1:13 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES10 LPAR clone - OSA interface not found >>> On 2/9/2011 at 07:55 PM, "Lester, Doug" wrote: > Unfortunately, we do not have z/VM and I am stuck with LPAR > installations. I am trying to develop a process for cloning from one > LPAR and installing the clone in another LPAR. > > Everything works according to plan except the OSA network card is not > found. This is where I need help. What machine type and OSA type do you have? -snip- > During boot, I get the following messages. > > Setting up network interfaces: > lo > lo > IP address: 127.0.0.1/8 > IP address: 127.0.0.2/8 > Checking for network time protocol daemon (NTPD): ..unused > lo > [1A..done > Waiting for mandatory devices: lcs-bus-ccw-0.0.3200 __NSC__ > 17 > 16 > 15 > 14 > 13 > 12 > 11 > 10 > 9 > 8 > 7 > 6 > 5 > 4 > 3 > 2 > 1 > 0 > lcs-bus-ccw-0.0.3200No interface found > [1A..failedSetting up service network . . . . . . . . . . . . . . > . ...failed The messages that would tell us something would have come before this, when the kernel is trying to activate the NIC. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SLES10 LPAR clone - OSA interface not found
>>> On 2/9/2011 at 07:55 PM, "Lester, Doug" wrote: > Unfortunately, we do not have z/VM and I am stuck with LPAR > installations. I am trying to develop a process for cloning from one > LPAR and installing the clone in another LPAR. > > Everything works according to plan except the OSA network card is not > found. This is where I need help. What machine type and OSA type do you have? -snip- > During boot, I get the following messages. > > Setting up network interfaces: > lo > lo > IP address: 127.0.0.1/8 > IP address: 127.0.0.2/8 > Checking for network time protocol daemon (NTPD): ..unused > lo > [1A..done > Waiting for mandatory devices: lcs-bus-ccw-0.0.3200 __NSC__ > 17 > 16 > 15 > 14 > 13 > 12 > 11 > 10 > 9 > 8 > 7 > 6 > 5 > 4 > 3 > 2 > 1 > 0 > lcs-bus-ccw-0.0.3200No interface found > [1A..failedSetting up service network . . . . . . . . . . . . . . > . ...failed The messages that would tell us something would have come before this, when the kernel is trying to activate the NIC. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SLES10 LPAR clone - OSA interface not found
Hi Doug,
I think the configuration files looks good
I would check first command " dmesg" to see all messages which are
available from the operating system
Then I would check if the devices could be sensed from the system with "
lscss |grep -i 3200 " and "lscss |grep -i 3201"
If this is Ok i would check if devices was grouped
"ls -la /sys/bus/ccwgroup/drivers/lcs/"
Then you know a little bit more what's going on.
Mit freundlichen Grüßen / Kind regards
Helmut Grauer
Linux on System z System & Performance Evaluation
IBM Systems &Technology Group, Systems Software Development
SW Linux on System z Syst&Perform Evaluation
Phone:
+49-7031-16-2938
IBM Deutschland
E-Mail:
helmut.gra...@de.ibm.com
Schoenaicher Str. 220
71032 Boeblingen
Germany
IBM Deutschland Research & Development GmbH / Vorsitzender des
Aufsichtsrats: Martin Jetter
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart,
HRB 243294
From: "Lester, Doug"
To: LINUX-390@vm.marist.edu
Date: 10.02.2011 01:56
Subject:SLES10 LPAR clone - OSA interface not found
Sent by:Linux on 390 Port
Unfortunately, we do not have z/VM and I am stuck with LPAR
installations. I am trying to develop a process for cloning from one
LPAR and installing the clone in another LPAR.
Everything works according to plan except the OSA network card is not
found. This is where I need help.
General steps:
*DFSS backup
*DFSS restore to different volumes
*Mount boot volume to /mnt on existing LPAR
*Update config files in /mnt/etc
*chroot /mnt
*mkinitrd
*zipl
*exit chroot
*umount /mnt and deactivate volume
*Update HMC with new boot volume in new LPAR and
Activate(start)
During boot, I get the following messages.
Setting up network interfaces:
lo
lo
IP address: 127.0.0.1/8
IP address: 127.0.0.2/8
Checking for network time protocol daemon (NTPD): ..unused
lo
[1A..done
Waiting for mandatory devices: lcs-bus-ccw-0.0.3200 __NSC__
17
16
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
lcs-bus-ccw-0.0.3200No interface found
[1A..failedSetting up service network . . . . . . . . . . . . . .
. ...failed
The configuration files that I modified for the new LPAR follow:
(The OSA channel ids need to change from 3600,3601 to 3200,3201 for the
new LPAR. I modified the channel ids and IP address to reflect the new
LPAR)
techlnux:/mnt/etc/sysconfig/hardware # cat hwcfg-lcs-bus-ccw-0.0.3200
STARTMODE='auto'
MODULE='lcs'
MODULE_OPTIONS=''
MODULE_UNLOAD='yes'
SCRIPTUP='hwup-ccw'
SCRIPTUP_ccw='hwup-ccw'
SCRIPTUP_ccwgroup='hwup-lcs'
SCRIPTDOWN='hwdown-ccw'
CCW_CHAN_IDS='0.0.3200 0.0.3201'
CCW_CHAN_NUM='2'
CCW_CHAN_MODE='0'
techlnux:/mnt/etc/sysconfig/network # cat ifcfg-lcs-bus-ccw-0.0.3200
BOOTPROTO='static'
UNIQUE=''
STARTMODE='auto'
IPADDR='10.128.160.2/24'
NETMASK='255.255.255.0'
NETWORK='10.128.160.0'
BROADCAST='10.128.160.255'
_nm_name='lcs-bus-ccw-0.0.3200'
PREFIXLEN='24'
techlnux:/mnt/etc/sysconfig/network # cat routes
default 10.128.160.1 - -
techlnux:/mnt/etc/udev/rules.d # cat 30-net_persistent_names.rules
SUBSYSTEM=="net", ACTION=="add", ENV{PHYSDEVPATH}=="*0.0.3200",
IMPORT="/lib/udev/rename_netiface %k eth0"
Is there a configuration file that I have left out? A command that I
need to run? Any help would be appreciated.
Thanks
Doug Lester
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
<><><><><><><>
SLES10 LPAR clone - OSA interface not found
Unfortunately, we do not have z/VM and I am stuck with LPAR
installations. I am trying to develop a process for cloning from one
LPAR and installing the clone in another LPAR.
Everything works according to plan except the OSA network card is not
found. This is where I need help.
General steps:
* DFSS backup
* DFSS restore to different volumes
* Mount boot volume to /mnt on existing LPAR
* Update config files in /mnt/etc
* chroot /mnt
* mkinitrd
* zipl
* exit chroot
* umount /mnt and deactivate volume
* Update HMC with new boot volume in new LPAR and Activate(start)
During boot, I get the following messages.
Setting up network interfaces:
lo
lo
IP address: 127.0.0.1/8
IP address: 127.0.0.2/8
Checking for network time protocol daemon (NTPD): ..unused
lo
[1A..done
Waiting for mandatory devices: lcs-bus-ccw-0.0.3200 __NSC__
17
16
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
lcs-bus-ccw-0.0.3200No interface found
[1A..failedSetting up service network . . . . . . . . . . . . . .
. ...failed
The configuration files that I modified for the new LPAR follow:
(The OSA channel ids need to change from 3600,3601 to 3200,3201 for the
new LPAR. I modified the channel ids and IP address to reflect the new
LPAR)
techlnux:/mnt/etc/sysconfig/hardware # cat hwcfg-lcs-bus-ccw-0.0.3200
STARTMODE='auto'
MODULE='lcs'
MODULE_OPTIONS=''
MODULE_UNLOAD='yes'
SCRIPTUP='hwup-ccw'
SCRIPTUP_ccw='hwup-ccw'
SCRIPTUP_ccwgroup='hwup-lcs'
SCRIPTDOWN='hwdown-ccw'
CCW_CHAN_IDS='0.0.3200 0.0.3201'
CCW_CHAN_NUM='2'
CCW_CHAN_MODE='0'
techlnux:/mnt/etc/sysconfig/network # cat ifcfg-lcs-bus-ccw-0.0.3200
BOOTPROTO='static'
UNIQUE=''
STARTMODE='auto'
IPADDR='10.128.160.2/24'
NETMASK='255.255.255.0'
NETWORK='10.128.160.0'
BROADCAST='10.128.160.255'
_nm_name='lcs-bus-ccw-0.0.3200'
PREFIXLEN='24'
techlnux:/mnt/etc/sysconfig/network # cat routes
default 10.128.160.1 - -
techlnux:/mnt/etc/udev/rules.d # cat 30-net_persistent_names.rules
SUBSYSTEM=="net", ACTION=="add", ENV{PHYSDEVPATH}=="*0.0.3200",
IMPORT="/lib/udev/rename_netiface %k eth0"
Is there a configuration file that I have left out? A command that I
need to run? Any help would be appreciated.
Thanks
Doug Lester
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
