Alan, This was a layer 2 vswitch before and after the move. Also if I need to delete and re-define do I just do it in Linux or we also need to delete and re-define in z/VM guest ID( I do not see if this matters). I tried deleting and re-defining the network interface in the guest but with no success. I still get the same error:
qdio: loading QDIO base support version 2 qeth: loading qeth S/390 OSA-Express driver qeth: received an IDX TERMINATE with cause code 0xf6 qeth: The qeth device 0.0.0800 is not configured for the OSI layer required by z/VM qeth: sense data available on channel 0.0.0800. qeth: cstat 0x0 dstat 0xE qeth: irb: 00 c2 60 17 04 98 90 38 0e 00 10 00 00 80 00 00 qeth: irb: 01 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 qeth: sense data: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 qeth: sense data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 qeth: Initialization in hardsetup failed! rc=-5 qeth: received an IDX TERMINATE with cause code 0xf6 Regards, Ashwin -----Original Message----- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Alan Altmark Sent: Friday, October 02, 2009 12:17 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Linux vswitch layer2 OSA-Express2 (z9 ) to OSA-EXPRESS3 1000T (z10 ) migration issue On Thursday, 10/01/2009 at 07:31 EDT, "Bhemidhi, Ashwin" <ashw...@ti.com> wrote: > We recently moved our working z/VM Linux LPAR from z9 to z10. After the move > our Linux guest systems are unable to use a layer 2 VSWITCH device. Our Linux > guest has 2 layer2 NIC interface eth0 and eth1 defined. NIC eth0 is used for IP > and NIC eth1 only does LLC over Ethernet (no IP) and is used to communication > with Cisco SNA switch router. After the VM LPAR move IP NIC interface eth0 > works but not the LLC NIC interface eth1 work. I am confused why only the IP > interface is working and the LLC even though both of them were defined as > Layer2 VSWITCH. I do see a "qeth: received an IDX TERMINATE with cause code > 0xf6" error though. I know something is not right about the OSA but am unable > to determine what it is. 0xF6 indicates that the VSWITCH type does not match how the guest has *previously* initialized its NIC. That is, you have, say, a layer 3 (IP) VSWITCH and the guest initialized its virtual NIC to "layer 3". Then you uncouple the guest from the VSWITCH, delete and re-define the VSWITCH as "layer 2" (ETHERNET) and re-couple. When the guest re-initializes as "layer 2" you get the 0xF6. Once a vNIC has a "personality", you must delete and re-define it to change the personality. Alan Altmark z/VM Development IBM Endicott ---------------------------------------------------------------------- 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 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
