Re: OSA Card Sharing on Linux
Thanks again for Your help, and at the same time I have to apologize for not making myself clear. I forgot to mention I'm not using z/VM for the installation (don't ask why... just following orders:), just Linux on plain LPAR. So I suppose that if something's wrong with mainframe configuration, it's in the HMC; but I'm not even sure that I can share the OSA this way. Some people I asked before said yes. Regards, Blazej 2010/5/9 Alan Altmark alan_altm...@us.ibm.com: On Saturday, 05/08/2010 at 09:58 EST, Błażej Ślusarek blazej...@gmail.com wrote: Thanks for a quick reply and clarification of the portname setting. a Well, the error I get is, hmm, timeout? Any form of network connection I'm trying to initiate just hangs for some time, then it spits out a Connection Error or something similar (depends on application). I doubt it's a configuration error, I've checked it with the same Linux distribution and network settings as I used on the first LPAR (which was inactive during the check). Since you didn't get an OSA activation error, I suspect that you're connected to the wrong OSA. See below. I'm pretty sure the chpid is 0 on both LPARs - I'll check it again on Monday, but if not - what does it mean and eventually where can I change it? Oh, and is it correct that the two LPARs have different OSA addresss (0.0.-0001-0002 and 0.0.1000-1001-1002) ? It is indeed possible to create different device numbers on different LPARs for the same chpid, but it takes extra effort and it's unusual to do so. Since you ask how to change it, I assume that you're not the person in charge of the I/O configuration of the box. Only they can change it. An OSA on chpid 0 at device number 0 would appear in the I/O configuration as something like CHPID PCHID=170,PATH=(CSS(0,1,2,3),00),TYPE=OSD,SHARED,CHPARM=02 CNTLUNIT CUNUMBR=,PATH=((CSS(0),39),(CSS(1),39),(CSS(2),39), X (CSS(3),39)), X UNIT=OSA IODEVICE ADDRESS=(,32),CUNUMBR=(),UNIT=OSA,UNITADD=00 IODEVICE ADDRESS=(00FE),CUNUMBR=(),UNIT=OSAD,UNITADD=FE To make it device 0 on LPAR 1 and device 1000 on LPAR 2 requires a bunch of extra coding that few people bother with. The QUERY PATHS command will tell you the chpid. If QUERY PATHS 000 on LPAR 1 and QUERY PATHS 1000 on LPAR 2 show the same chpid, you're on the right track. Here's what my OSA looks like. It has the same addresses on all LPARs. CHPID PCHID=291,PATH=(CSS(0,1,2,3),53),TYPE=OSD,SHARED,CHPARM=02 CNTLUNIT CUNUMBR=6640,PATH=((CSS(0),53),(CSS(1),53),(CSS(2),53), X (CSS(3),53)), X UNIT=OSA IODEVICE ADDRESS=(6640,32),CUNUMBR=(6640),UNIT=OSA IODEVICE ADDRESS=(67E1),CUNUMBR=(6640),UNIT=OSAD,UNITADD=FE q 6646 OSA 6646 FREE Ready; T=0.01/0.01 23:19:53 q paths 6646 Device 6646, Status ONLINE CHPIDs to Device 6646 (PIM) : 53 Physically Available (PAM) : + Online (LPM) : + Legend + Yes - No Ready; T=0.01/0.01 23:19:58 q chpid 53 Path 53 online to devices 6640 6641 6642 6643 6644 6645 6646 6647 Path 53 online to devices 6648 6649 664A 664B 664C 664D 664E 664F Path 53 online to devices 6650 6651 6652 6653 6654 6655 6656 6657 Path 53 online to devices 6658 6659 665A 665B 665C 665D 665E 665F Path 53 online to devices 67E1 Ready; T=0.01/0.01 23:20:08 q chpid 53 type Path 53 is an Open Systems Adapter Direct Express (OSD) channel Ready; T=0.01/0.01 23:20:16 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
Re: Linux boot image for s390
On Sunday 09 May 2010, Błażej Ślusarek wrote: Hello, First of all, thanks for quick reply and explanation of some basics. Well, the distribution I'm trying to install (gentoo) doesn't provide the installation image, however the s390 architecture is supported. So I'm forced to create the image by myself. I'll try to cross-compile the kernel and see if it will work. Gentoo already supplied a complete s390 distro in 2007. I fixed it up a bit and documented a boot-strap technique using Red Hat images. You can find the results in http://www.binro.org/gentoo-2008.6-s390x-unofficial.tar.bz2. It's a long time since I played with this though, so good luck! Incidentally I did it on Hercules but I guess it's much the same with real iron, you just have to burn a CD? HTH -Robin -- -- Robin Atwood. Ship me somewheres east of Suez, where the best is like the worst, Where there ain't no Ten Commandments an' a man can raise a thirst from Mandalay by Rudyard Kipling -- -- 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
Re: OSA Card Sharing on Linux
On Sunday, 05/09/2010 at 08:04 EST, Błażej Ślusarek blazej...@gmail.com wrote: Thanks again for Your help, and at the same time I have to apologize for not making myself clear. I forgot to mention I'm not using z/VM for the installation (don't ask why... just following orders:), just Linux on plain LPAR. So I suppose that if something's wrong with mainframe configuration, it's in the HMC; but I'm not even sure that I can share the OSA this way. Some people I asked before said yes. Sorry; you did say you were in an LPAR. Use 'lsqeth eth0' to get the chpid number on the working LPAR. Then you can use 'lschp' to ensure that the chpid is shared. On the failing LPAR, use lsqeth again to ensure you have the same chpid. 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
Re: OSA Card Sharing on Linux
Thanks, I'll try that. On my working LPAR I'm getting something like this: lsqeth eth0 Device name : eth0 - card_type : OSD_100 cdev0 : 0.0. cdev1 : 0.0.0001 cdev2 : 0.0.0002 chpid : 00 online : 1 portno : 0 route4 : no route6 : no checksumming: sw checksumming state : UP (LAN ONLINE) priority_queueing : always queue 2 fake_ll : 0 fake_broadcast : 0 buffer_count: 16 add_hhlen : 0 layer2 : 0 large_send : no lschp CHPID Vary Cfg. Type Cmg Shared 0.60 1 - 0311 0.61 1 - 0411 0.62 1 - 0411 0.70 1 - 0411 0.71 1 - 0311 0.72 1 - 0411 Seems strange to me that chpid from lsqeth is not present in lschp (or I don't understand the output). Regards, Blazej 2010/5/9 Alan Altmark alan_altm...@us.ibm.com: On Sunday, 05/09/2010 at 08:04 EST, Błażej Ślusarek blazej...@gmail.com wrote: Thanks again for Your help, and at the same time I have to apologize for not making myself clear. I forgot to mention I'm not using z/VM for the installation (don't ask why... just following orders:), just Linux on plain LPAR. So I suppose that if something's wrong with mainframe configuration, it's in the HMC; but I'm not even sure that I can share the OSA this way. Some people I asked before said yes. Sorry; you did say you were in an LPAR. Use 'lsqeth eth0' to get the chpid number on the working LPAR. Then you can use 'lschp' to ensure that the chpid is shared. On the failing LPAR, use lsqeth again to ensure you have the same chpid. 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
