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 <[email protected]>: > On Saturday, 05/08/2010 at 09:58 EST, Błażej Ślusarek > <[email protected]> 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.0000-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=0000,PATH=((CSS(0),39),(CSS(1),39),(CSS(2),39), X > (CSS(3),39)), X > UNIT=OSA > IODEVICE ADDRESS=(0000,32),CUNUMBR=(0000),UNIT=OSA,UNITADD=00 > IODEVICE ADDRESS=(00FE),CUNUMBR=(0000),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 [email protected] 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 [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
