ITschak,
I can't seem to respond directly to you since our mail system thinks you are
suspicious :)
Command line you could do something like
qeth_configure -l -f 0.0.0402 0.0.0403 0.0.0404 1
I think that should do it, although haven't tried it myself.
I am assuming you are using a real OSA - I may have missed that part.
If a vswitch, you'd need to change it and your NIC card defs.
-----Original Message-----
From: Cortes, Marcy D.
Sent: Tuesday, February 07, 2017 12:42 PM
To: 'i_mugz...@securiteam.co.il'; LINUX-390@VM.MARIST.EDU
Subject: RE: [LINUX-390] SUSE under ZVM networking issues
You can go into /etc/udev/rules.d/
and edit the file associated with the address 402 and set it to layer2
Mine has a line like this
ACTION=="add", SUBSYSTEM=="ccwgroup", KERNEL=="0.0.3000", ATTR{layer2}="1"
Then reboot
-----Original Message-----
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Itschak
Mugzach
Sent: Tuesday, February 07, 2017 12:03 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] SUSE under ZVM networking issues
Mark,
I looked into the cookbook (Installing Linux for z Systems on zPDT: A Short
Cookbook) and it instruct not to install layer 2 support...
OPRMSG: Device address for data channel. (Enter '+++' to abort).
OPRMSG: 0.0.0402!>
+
(enter a null line)
OPRMSG: Portname to use. (Enter '+++' to abort).
+
(enter a null line)
OPRMSG: Enable OSI Layer 2 support?
OPRMSG: 0) <-- Back <--
OPRMSG: 1) Yes
OPRMSG: 2) No
+
2
(select option 2)
OPRMSG: Examples: 192.168.5.77/24 2001:db8:75:fff::3/64.
+ 10.1.1.2/24
(IP for target system
will it be easier to re-install the image? what about the second card?
should I configure it later after connecting to the guest?
Best,
ITschak
On Tue, Feb 7, 2017 at 9:43 PM, Itschak Mugzach <imugz...@gmail.com> wrote:
> lsqeth returns zero for layer2 on both NICs. using root to echo 1 >
> /sys/devices/qeth/0.0.0.0400/layer2 returns write error operation not
> permited... any alternative to this?
>
> ITschak
>
> On Tue, Feb 7, 2017 at 8:20 PM, Mark Post <mp...@suse.com> wrote:
>
>> >>> On 2/7/2017 at 08:30 AM, Itschak Mugzach <imugz...@gmail.com> wrote:
>> > I was able to change the network interfaces to dhcp using yast lan
>> > edit id=x bootproto=dhcp, and wicked ifup . Now eth0 and eth1 are
>> > stalled
>> (?) at
>> > setup in progress and both lease of ipv4 and ipv6 are ipvx dhcp
>> requesting
>> > status...
>>
>> Are these NICs in Layer 2 mode? They have to be, for dhcp to work.
>> The lsqeth command will show that information.
>>
>>
>> Mark Post
>>
>> ---------------------------------------------------------------------
>> - 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 more information on Linux on System z, visit
>> http://wiki.linuxvm.org/
>>
>
>
>
> --
> ITschak Mugzach
> *|** IronSphere Platform* *|** An IT GRC for Legacy systems* *|
> Automated Security Readiness Reviews (SRR) **|*
>
>
>
--
ITschak Mugzach
*|** IronSphere Platform* *|** An IT GRC for Legacy systems* *| Automated
Security Readiness Reviews (SRR) **|*
----------------------------------------------------------------------
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 more information on Linux on System z, visit http://wiki.linuxvm.org/
