In addition to what Alan said about your config and maintenance, you might want to take the OSA chpid completely offline and back on to force it to reload its microcode. We had some OSA issues last week with a z9->z10 upgrade and the reload fixed them.
Marcy "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Alan Altmark Sent: Friday, October 02, 2009 10:12 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Linux vswitch layer2 OSA-Express2 (z9 ) to OSA-EXPRESS3 1000T (z10 ) migration issue On Friday, 10/02/2009 at 12:16 EDT, "Bhemidhi, Ashwin" <ashw...@ti.com> wrote: > 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 0xF6 is specifically issued when the VSWITCH type doesn't match the way the guest has previously configured the adapter. You could get this error if the guest tried to configure layer 3 on an layer 2 VSWITCH or the guest configured the vNIC prior to the COUPLE to the VSWITCH. All that would be required is to log the user off/on or detach the NIC and re-define it. If the ONLY thing you changed was z9->z10 and you have the support for OSA-Express3 (if that's what you're using) applied, then call it in. Just double-check that Linux is configured to do layer 2. I have seen systems do odd things after a h/w change because something was dependent on the system identifier or CPU serial number. 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
