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.0000
        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     -     03    1    1
0.61   1     -     04    1    1
0.62   1     -     04    1    1
0.70   1     -     04    1    1
0.71   1     -     03    1    1
0.72   1     -     04    1    1

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 <[email protected]>:
> On Sunday, 05/09/2010 at 08:04 EST, Błażej Ślusarek <[email protected]>
> 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 [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

Reply via email to