User error: The portname does matter! I thought IBM previously relieved this requirement. I guess I'm wrong. When I change the portname in the "prm" file to "INTRANET" my RH 6 server will connect to the OSA device.
-----Original Message----- From: Scully, William P Sent: Wednesday, December 15, 2010 10:55 AM To: [email protected] Subject: RE: Red Hat 6 qeth device driver failed to recover So far none of the suggestions have helped. Although I appreciate the advice. This problem with the virtual OSA is only with RH. If I reboot (without logging off) SLES 11.1 the OSA adapter does work. (It doesn't matter if I boot SLES or RH first, RH always fails and SLES always works.) I've tested RH 6.0 and 5.5 and both fail in a similar fashion. The failure occurs with the second-level VM node running either CP 5.3.0 or 5.4.0. Base-level z/VM is 5.4.0. The third-level TCP/IP can use the OSA's created by the second-level z/VM CP. The OSA adapters are DEDICATEd devices to the third-level guest. The second-level z/VM sees the OSA via a NICDEF. Is there a document which describes the OSA sense bits? I'm guessing I'll need to decode the sense information to understand why this is failing. Here's some additional sample responses: cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.0 (Santiago) /sbin/qeth_configure 0.0.0c00 0.0.0c01 0.0.0c02 1 -bash: /sbin/qeth_configure: No such file or directory lsqeth Device name : --------------------------------------------- card_type : GuestLAN QDIO cdev0 : 0.0.0c00 cdev1 : 0.0.0c01 cdev2 : 0.0.0c02 chpid : 0E online : 0 portname : OSD02 portno : 0 route4 : no route6 : no checksumming : sw checksumming state : DOWN priority_queueing : always queue 2 fake_broadcast : 0 buffer_count : 16 layer2 : 0 large_send : no isolation : none sniffer : 0 echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.0c00/online qeth 0.0.0c00: The qeth device driver failed to recover an error on the device qeth: irb 00000000: 00 c2 60 17 1f 3e 60 38 0e 00 10 00 00 80 00 00 ..`..>`8........ qeth: irb 00000010: 01 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ qeth: sense data 00000000: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ qeth: sense data 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ qeth 0.0.0c00: The qeth device driver failed to recover an error on the device -bash: echo: write error: No such device echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.0c00/layer2 qeth: register layer 2 discipline echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.0c00/online qeth 0.0.0c00: The qeth device is not configured for the OSI layer required by z/VM qeth 0.0.0c00: The qeth device driver failed to recover an error on the device qeth: irb 00000000: 00 c2 60 17 1f 3e 60 38 0e 00 10 00 00 80 00 00 ..`..>`8........ qeth: irb 00000010: 01 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ qeth: sense data 00000000: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ qeth: sense data 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ qeth 0.0.0c00: The qeth device driver failed to recover an error on the device -bash: echo: write error: No such device -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Sebastian Ott Sent: Wednesday, December 15, 2010 4:44 AM To: [email protected] Subject: Re: Red Hat 6 qeth device driver failed to recover On Tue, 14 Dec 2010, Mark Post wrote: > >>> On 12/14/2010 at 04:13 PM, Marcy Cortes <[email protected]> wrote: > > > Don't you have to bring online the c01 and c02 devices too > > chccwdev -e 0.0.0c00-0.0.0c02 > > No, you can only bring the lowest address of the three devices that have been grouped together online. So, the manual process would be > echo 0.0.0c00,0.0.0c01,0.0.0c02 > /sys/bus/ccwgroup/drivers/qeth/group > echo 0 > /sys/bus/ccwgroup/drivers/qeth/0.0.0c00/layer2 > echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.0c00/online yes. > -- or -- > chccwdev -e 0.0.0c00 The last one is not right - it would change an attribute of the ccw device, not one of the ccwgroup device. (I know its hard to distinguish, since they have the same name...) > > If it's a Layer 2 NIC, then you would have to change the second echo command to "echo 1". > > > Mark Post > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] 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/ > regards Sebastian ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] 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 [email protected] 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/
