Re: SLES10 LPAR clone - OSA interface not found

2011-02-10 Thread Mark Post
>>> 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 ---

Re: SLES10 LPAR clone - OSA interface not found

2011-02-10 Thread Lester, Doug
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: LIN

Re: vswitch routing

2011-02-10 Thread Alan Altmark
On Thursday, 02/10/2011 at 04:55 EST, Jose Correa Saldeño wrote: > For backup over the same network without affecting real time traffic, Is it > possible to establish routes to the media server over particular OSAs on the > same VLAN and VSwitch. We currently have two OSAs from the same VSw

Re: SLES10 LPAR clone - OSA interface not found

2011-02-10 Thread Mark Post
>>> 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 H

Re: vswitch routing

2011-02-10 Thread Mark Post
>>> On 2/10/2011 at 04:50 PM, Jose Correa Saldeño >>> wrote: > Hello, > > For backup over the same network without affecting real time traffic, Is it > possible to establish routes to the media server over particular OSAs on the > same VLAN and VSwitch. We currently have two OSAs from the sam

vswitch routing

2011-02-10 Thread Jose Correa Saldeño
Hello, For backup over the same network without affecting real time traffic, Is it possible to establish routes to the media server over particular OSAs on the same VLAN and VSwitch. We currently have two OSAs from the same VSwitch to two different Cisco switches with the same VLANs. For th

Re: SLES10 LPAR clone - OSA interface not found

2011-02-10 Thread Dave Jones
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

Re: one final observation on my piping to multiple processes.

2011-02-10 Thread Larry Ploetz
On 2/10/11 12:15 PM, Philip Rowlands wrote: > > > One final note; the pee utility included in the moreutils package does > exactly what you want without the funky shell syntax. > > Funky syntax?!? I take exception to that, sir. ;-) Larry "I *like* bash; I really do" Ploetz --

Re: SLES10 LPAR clone - OSA interface not found

2011-02-10 Thread Lester, Doug
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

Re: SLES10 LPAR clone - OSA interface not found

2011-02-10 Thread Lester, Doug
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: SLES1

Re: one final observation on my piping to multiple processes.

2011-02-10 Thread Philip Rowlands
On 10/02/2011 14:23, McKown, John wrote: The use of>(...) and tee seem to be what I need to pipe the output from bzcat to muliple perl scripts. But I found a "bug" in my original: bzcat data*bz2| tee>(perl script1.pl) | perl script2.pl The stdout from script1.pl is piped into script2.pl ater th

Feb 16/17 Webcast: Lessons learned from putting Linux on System z in Production

2011-02-10 Thread Pamela Christina in frozen Endicott NY
Cross-posted to IBMVM,LINUX390,IBMMAIN for those who are interested in webcasts/live virtual classes. The next webcast has three airings Feb 16/17, and will also be recorded for later replay. Link to Description and registration for choice of day/time. http://www.vm.ibm.com/education/lvc/ Title:

Re: SLES10 LPAR clone - OSA interface not found

2011-02-10 Thread Sam Bass
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

Re: SLES10 LPAR clone - OSA interface not found

2011-02-10 Thread Mark Post
>>> 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

one final observation on my piping to multiple processes.

2011-02-10 Thread McKown, John
The use of >(...) and tee seem to be what I need to pipe the output from bzcat to muliple perl scripts. But I found a "bug" in my original: bzcat data*bz2| tee >(perl script1.pl) | perl script2.pl The stdout from script1.pl is piped into script2.pl ater the bzcat'ed data. So I need to do someth

AUTO: Damian Osisek/Raleigh/IBM is out on personal business until Friday, February 11 (returning 02/11/2011)

2011-02-10 Thread Damian Osisek
I am out of the office until 02/11/2011. Note: This is an automated response to your message "LINUX-390 Digest - 8 Feb 2011 to 9 Feb 2011 (#2011-32)" sent on 2/10/2011 12:00:35 AM. This is the only notification you will receive while this person is away. --

Re: SLES10 LPAR clone - OSA interface not found

2011-02-10 Thread Helmut Grauer
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