Re: Defining a vipa
lsmod|grep dummy returns: dummy 16384 0 But there is no dummy0 device defined. Gadi -Original Message- From: Linux on 390 Port On Behalf Of Lee B Sent: Tuesday, May 21, 2019 9:31 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Defining a vipa The 'modprobe dummy' from step 2? It should appear in the output of 'lsmod'. When I load it on a system here, I see a 'dummy0' device in the output from 'ip link': root@mgmt:~# modprobe dummy root@mgmt:~# lsmod | grep dummy dummy 16384 0 root@mgmt:~# ip link ... 4: dummy0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether a6:d2:eb:af:82:64 brd ff:ff:ff:ff:ff:ff root@mgmt:~# Lee. On Tue, May 21 2019, Gadi Ben-Avi wrote: > Hi, > I am trying to define a VIPA on my Ubuntu v18.04.1 LTS system. > The system is running on a z13s in an LPAR. > I found instructions at > https://www.ibm.com/support/knowledgecenter/en/linuxonibm/com.ibm.linu > x.z.ludd/ludd_t_stdvipa_xmp.html > > The command: > sudo ip addr add 10.205.1.100/24 dev dummy0 fails with: > Cannot find device "dummy0" > > Am I missing something? > > Thanks > Gadi > > > > -- > 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 -- 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: Defining a vipa
Hmmm. OK then, what happens when you: ip link add dummy0 type dummy ? Lee. On Tue, May 21 2019, Gadi Ben-Avi wrote: > lsmod|grep dummy returns: > dummy 16384 0 > > But there is no dummy0 device defined. > > Gadi > > -Original Message- > From: Linux on 390 Port On Behalf Of Lee B > Sent: Tuesday, May 21, 2019 9:31 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Defining a vipa > > The 'modprobe dummy' from step 2? > > It should appear in the output of 'lsmod'. When I load it on a system here, I > see a 'dummy0' device in the output from 'ip link': > > root@mgmt:~# modprobe dummy > root@mgmt:~# lsmod | grep dummy > dummy 16384 0 > root@mgmt:~# ip link > ... > 4: dummy0: mtu 1500 qdisc noop state DOWN mode DEFAULT > group default qlen 1000 > link/ether a6:d2:eb:af:82:64 brd ff:ff:ff:ff:ff:ff root@mgmt:~# > > Lee. > > On Tue, May 21 2019, Gadi Ben-Avi wrote: > >> Hi, >> I am trying to define a VIPA on my Ubuntu v18.04.1 LTS system. >> The system is running on a z13s in an LPAR. >> I found instructions at >> https://www.ibm.com/support/knowledgecenter/en/linuxonibm/com.ibm.linu >> x.z.ludd/ludd_t_stdvipa_xmp.html >> >> The command: >> sudo ip addr add 10.205.1.100/24 dev dummy0 fails with: >> Cannot find device "dummy0" >> >> Am I missing something? >> >> Thanks >> Gadi >> >> >> >> -- >> 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 > > -- > 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: Defining a vipa
Thanks Lee. The ip link add dummy0 type dummy command worked and then I could assign it the address. Thanks for your help Gadi -Original Message- From: Linux on 390 Port On Behalf Of Lee B Sent: Tuesday, May 21, 2019 10:24 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Defining a vipa Hmmm. OK then, what happens when you: ip link add dummy0 type dummy ? Lee. On Tue, May 21 2019, Gadi Ben-Avi wrote: > lsmod|grep dummy returns: > dummy 16384 0 > > But there is no dummy0 device defined. > > Gadi > > -Original Message- > From: Linux on 390 Port On Behalf Of Lee B > Sent: Tuesday, May 21, 2019 9:31 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Defining a vipa > > The 'modprobe dummy' from step 2? > > It should appear in the output of 'lsmod'. When I load it on a system here, I > see a 'dummy0' device in the output from 'ip link': > > root@mgmt:~# modprobe dummy > root@mgmt:~# lsmod | grep dummy > dummy 16384 0 > root@mgmt:~# ip link > ... > 4: dummy0: mtu 1500 qdisc noop state DOWN mode DEFAULT > group default qlen 1000 > link/ether a6:d2:eb:af:82:64 brd ff:ff:ff:ff:ff:ff root@mgmt:~# > > Lee. > > On Tue, May 21 2019, Gadi Ben-Avi wrote: > >> Hi, >> I am trying to define a VIPA on my Ubuntu v18.04.1 LTS system. >> The system is running on a z13s in an LPAR. >> I found instructions at >> https://www.ibm.com/support/knowledgecenter/en/linuxonibm/com.ibm.lin >> u >> x.z.ludd/ludd_t_stdvipa_xmp.html >> >> The command: >> sudo ip addr add 10.205.1.100/24 dev dummy0 fails with: >> Cannot find device "dummy0" >> >> Am I missing something? >> >> Thanks >> Gadi >> >> >> >> - >> - 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 > > -- > 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 -- 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: Defining a vipa
No problem - glad it worked :) (I'm assuming you're OK with adding to the network config so it persists across reboots...) Lee. On Tue, May 21 2019, Gadi Ben-Avi wrote: > Thanks Lee. > The ip link add dummy0 type dummy command worked and then I could assign it > the address. > > Thanks for your help > > Gadi > > -Original Message- > From: Linux on 390 Port On Behalf Of Lee B > Sent: Tuesday, May 21, 2019 10:24 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Defining a vipa > > Hmmm. OK then, what happens when you: > > ip link add dummy0 type dummy > > ? > > Lee. > > > On Tue, May 21 2019, Gadi Ben-Avi wrote: > >> lsmod|grep dummy returns: >> dummy 16384 0 >> >> But there is no dummy0 device defined. >> >> Gadi >> >> -Original Message- >> From: Linux on 390 Port On Behalf Of Lee B >> Sent: Tuesday, May 21, 2019 9:31 AM >> To: LINUX-390@VM.MARIST.EDU >> Subject: Re: Defining a vipa >> >> The 'modprobe dummy' from step 2? >> >> It should appear in the output of 'lsmod'. When I load it on a system here, >> I see a 'dummy0' device in the output from 'ip link': >> >> root@mgmt:~# modprobe dummy >> root@mgmt:~# lsmod | grep dummy >> dummy 16384 0 >> root@mgmt:~# ip link >> ... >> 4: dummy0: mtu 1500 qdisc noop state DOWN mode DEFAULT >> group default qlen 1000 >> link/ether a6:d2:eb:af:82:64 brd ff:ff:ff:ff:ff:ff root@mgmt:~# >> >> Lee. >> >> On Tue, May 21 2019, Gadi Ben-Avi wrote: >> >>> Hi, >>> I am trying to define a VIPA on my Ubuntu v18.04.1 LTS system. >>> The system is running on a z13s in an LPAR. >>> I found instructions at >>> https://www.ibm.com/support/knowledgecenter/en/linuxonibm/com.ibm.lin >>> u >>> x.z.ludd/ludd_t_stdvipa_xmp.html >>> >>> The command: >>> sudo ip addr add 10.205.1.100/24 dev dummy0 fails with: >>> Cannot find device "dummy0" >>> >>> Am I missing something? >>> >>> Thanks >>> Gadi >>> >>> >>> >>> - >>> - 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 >> >> -- >> 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 > > -- > 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: Defining a vipa
That will come later. I have a problem with the next step I ran the command: sudo qethconf vipa add 10.205.1.100 enc1440 and got: qethconf: OSA layer 2 enabled for device enc1440 ! IPA, VIPA, PARP not supported. Any ideas? Gadi -Original Message- From: Linux on 390 Port On Behalf Of Lee B Sent: Tuesday, May 21, 2019 10:53 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Defining a vipa No problem - glad it worked :) (I'm assuming you're OK with adding to the network config so it persists across reboots...) Lee. On Tue, May 21 2019, Gadi Ben-Avi wrote: > Thanks Lee. > The ip link add dummy0 type dummy command worked and then I could assign it > the address. > > Thanks for your help > > Gadi > > -Original Message- > From: Linux on 390 Port On Behalf Of Lee B > Sent: Tuesday, May 21, 2019 10:24 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Defining a vipa > > Hmmm. OK then, what happens when you: > > ip link add dummy0 type dummy > > ? > > Lee. > > > On Tue, May 21 2019, Gadi Ben-Avi wrote: > >> lsmod|grep dummy returns: >> dummy 16384 0 >> >> But there is no dummy0 device defined. >> >> Gadi >> >> -Original Message- >> From: Linux on 390 Port On Behalf Of Lee B >> Sent: Tuesday, May 21, 2019 9:31 AM >> To: LINUX-390@VM.MARIST.EDU >> Subject: Re: Defining a vipa >> >> The 'modprobe dummy' from step 2? >> >> It should appear in the output of 'lsmod'. When I load it on a system here, >> I see a 'dummy0' device in the output from 'ip link': >> >> root@mgmt:~# modprobe dummy >> root@mgmt:~# lsmod | grep dummy >> dummy 16384 0 >> root@mgmt:~# ip link >> ... >> 4: dummy0: mtu 1500 qdisc noop state DOWN mode DEFAULT >> group default qlen 1000 >> link/ether a6:d2:eb:af:82:64 brd ff:ff:ff:ff:ff:ff root@mgmt:~# >> >> Lee. >> >> On Tue, May 21 2019, Gadi Ben-Avi wrote: >> >>> Hi, >>> I am trying to define a VIPA on my Ubuntu v18.04.1 LTS system. >>> The system is running on a z13s in an LPAR. >>> I found instructions at >>> https://www.ibm.com/support/knowledgecenter/en/linuxonibm/com.ibm.li >>> n >>> u >>> x.z.ludd/ludd_t_stdvipa_xmp.html >>> >>> The command: >>> sudo ip addr add 10.205.1.100/24 dev dummy0 fails with: >>> Cannot find device "dummy0" >>> >>> Am I missing something? >>> >>> Thanks >>> Gadi >>> >>> >>> >>> >>> - >>> - 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 >> >> - >> - 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 > > -- > 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 -- 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: Defining a vipa
How about: https://www.ibm.com/support/knowledgecenter/en/linuxonibm/com.ibm.linux.z.lhdd/lhdd_t_qeth_wrk_layer2.html That's for SuSE, but I guess there's something similar lurking in /proc for Ubuntu somewhere? Lee. On Tue, May 21 2019, Gadi Ben-Avi wrote: > That will come later. > I have a problem with the next step > I ran the command: > sudo qethconf vipa add 10.205.1.100 enc1440 > and got: > qethconf: OSA layer 2 enabled for device enc1440 ! > IPA, VIPA, PARP not supported. > > Any ideas? > > Gadi > > -Original Message- > From: Linux on 390 Port On Behalf Of Lee B > Sent: Tuesday, May 21, 2019 10:53 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Defining a vipa > > No problem - glad it worked :) > > (I'm assuming you're OK with adding to the network config so it persists > across reboots...) > > Lee. > > On Tue, May 21 2019, Gadi Ben-Avi wrote: > >> Thanks Lee. >> The ip link add dummy0 type dummy command worked and then I could assign it >> the address. >> >> Thanks for your help >> >> Gadi >> >> -Original Message- >> From: Linux on 390 Port On Behalf Of Lee B >> Sent: Tuesday, May 21, 2019 10:24 AM >> To: LINUX-390@VM.MARIST.EDU >> Subject: Re: Defining a vipa >> >> Hmmm. OK then, what happens when you: >> >> ip link add dummy0 type dummy >> >> ? >> >> Lee. >> >> >> On Tue, May 21 2019, Gadi Ben-Avi wrote: >> >>> lsmod|grep dummy returns: >>> dummy 16384 0 >>> >>> But there is no dummy0 device defined. >>> >>> Gadi >>> >>> -Original Message- >>> From: Linux on 390 Port On Behalf Of Lee B >>> Sent: Tuesday, May 21, 2019 9:31 AM >>> To: LINUX-390@VM.MARIST.EDU >>> Subject: Re: Defining a vipa >>> >>> The 'modprobe dummy' from step 2? >>> >>> It should appear in the output of 'lsmod'. When I load it on a system here, >>> I see a 'dummy0' device in the output from 'ip link': >>> >>> root@mgmt:~# modprobe dummy >>> root@mgmt:~# lsmod | grep dummy >>> dummy 16384 0 >>> root@mgmt:~# ip link >>> ... >>> 4: dummy0: mtu 1500 qdisc noop state DOWN mode DEFAULT >>> group default qlen 1000 >>> link/ether a6:d2:eb:af:82:64 brd ff:ff:ff:ff:ff:ff root@mgmt:~# >>> >>> Lee. >>> >>> On Tue, May 21 2019, Gadi Ben-Avi wrote: >>> Hi, I am trying to define a VIPA on my Ubuntu v18.04.1 LTS system. The system is running on a z13s in an LPAR. I found instructions at https://www.ibm.com/support/knowledgecenter/en/linuxonibm/com.ibm.li n u x.z.ludd/ludd_t_stdvipa_xmp.html The command: sudo ip addr add 10.205.1.100/24 dev dummy0 fails with: Cannot find device "dummy0" Am I missing something? Thanks Gadi - - 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 >>> >>> - >>> - 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 >> >> -- >> 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 > > -- > 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: Defining a vipa
Sorry, I meant /sys not /proc... Lee. On Tue, May 21 2019, Gadi Ben-Avi wrote: > That will come later. > I have a problem with the next step > I ran the command: > sudo qethconf vipa add 10.205.1.100 enc1440 > and got: > qethconf: OSA layer 2 enabled for device enc1440 ! > IPA, VIPA, PARP not supported. > > Any ideas? > > Gadi > > -Original Message- > From: Linux on 390 Port On Behalf Of Lee B > Sent: Tuesday, May 21, 2019 10:53 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Defining a vipa > > No problem - glad it worked :) > > (I'm assuming you're OK with adding to the network config so it persists > across reboots...) > > Lee. > > On Tue, May 21 2019, Gadi Ben-Avi wrote: > >> Thanks Lee. >> The ip link add dummy0 type dummy command worked and then I could assign it >> the address. >> >> Thanks for your help >> >> Gadi >> >> -Original Message- >> From: Linux on 390 Port On Behalf Of Lee B >> Sent: Tuesday, May 21, 2019 10:24 AM >> To: LINUX-390@VM.MARIST.EDU >> Subject: Re: Defining a vipa >> >> Hmmm. OK then, what happens when you: >> >> ip link add dummy0 type dummy >> >> ? >> >> Lee. >> >> >> On Tue, May 21 2019, Gadi Ben-Avi wrote: >> >>> lsmod|grep dummy returns: >>> dummy 16384 0 >>> >>> But there is no dummy0 device defined. >>> >>> Gadi >>> >>> -Original Message- >>> From: Linux on 390 Port On Behalf Of Lee B >>> Sent: Tuesday, May 21, 2019 9:31 AM >>> To: LINUX-390@VM.MARIST.EDU >>> Subject: Re: Defining a vipa >>> >>> The 'modprobe dummy' from step 2? >>> >>> It should appear in the output of 'lsmod'. When I load it on a system here, >>> I see a 'dummy0' device in the output from 'ip link': >>> >>> root@mgmt:~# modprobe dummy >>> root@mgmt:~# lsmod | grep dummy >>> dummy 16384 0 >>> root@mgmt:~# ip link >>> ... >>> 4: dummy0: mtu 1500 qdisc noop state DOWN mode DEFAULT >>> group default qlen 1000 >>> link/ether a6:d2:eb:af:82:64 brd ff:ff:ff:ff:ff:ff root@mgmt:~# >>> >>> Lee. >>> >>> On Tue, May 21 2019, Gadi Ben-Avi wrote: >>> Hi, I am trying to define a VIPA on my Ubuntu v18.04.1 LTS system. The system is running on a z13s in an LPAR. I found instructions at https://www.ibm.com/support/knowledgecenter/en/linuxonibm/com.ibm.li n u x.z.ludd/ludd_t_stdvipa_xmp.html The command: sudo ip addr add 10.205.1.100/24 dev dummy0 fails with: Cannot find device "dummy0" Am I missing something? Thanks Gadi - - 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 >>> >>> - >>> - 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 >> >> -- >> 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 > > -- > 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: Defining a vipa
On Tue, May 21, 2019 at 10:47 AM Lee B wrote:
>
> How about:
>
> https://www.ibm.com/support/knowledgecenter/en/linuxonibm/com.ibm.linux.z.lhdd/lhdd_t_qeth_wrk_layer2.html
>
> That's for SuSE, but I guess there's something similar lurking in /proc
> for Ubuntu somewhere?
$ cat /sys/devices/qeth/0.0.c000/layer2
1
The same on Ubuntu as we all have the same s390x kernel code exposing that path.
IMHO the difference starts when you think about tooling as the network
config differs and for both depends on versions.
E.g. for my interface above you'd have
/etc/sysconfig/hardware.back/config-ccw-0.0.c000:2:QETH_OPTIONS=(layer2)
/etc/udev/rules.d/41-qeth-0.0.c003.rules:18:ATTR{[ccwgroup/0.0.c003]layer2}="1"
But nobody wants to mess with all those files manually.
And in fact this is generated by IBMs lszdev/chzdev tooling.
Take a look at the man page and maybe:
$ chzdev qeth --help-attribute layer2
I think from here things are rather clear.
With that in mind looking at one of my devices that I can spare.
$ lszdev 0.0.c003 --columns TYPE,ID,ON,PERS,NAMES,ATTR:layer2
TYPE ID ON PERS NAMESATTR:layer2
qeth 0.0.c003:0.0.c004:0.0.c005 yes yes encc003 1/1
The following could be simplified, but for illustration disabling layer2:
$ sudo chzdev -d qeth 0.0.c003
QETH device 0.0.c003:0.0.c004:0.0.c005 deconfigured
$ sudo chzdev qeth c003 layer2=0
QETH device 0.0.c003:0.0.c004:0.0.c005 configured
$ sudo chzdev -e qeth 0.0.c003
QETH device 0.0.c003:0.0.c004:0.0.c005 configured
$ lszdev 0.0.c003 --columns TYPE,ID,ON,PERS,NAMES,ATTR:layer2
TYPE ID ON PERS NAMESATTR:layer2
qeth 0.0.c003:0.0.c004:0.0.c005 yes yes encc003 0/0
And then you can enable vipa:
$ sudo qethconf vipa add 10.205.1.100 encc003
qethconf: Added 10.205.1.100 to sysfs entry
/sys/class/net/encc003/device/vipa/add4.
qethconf: For verification please use "qethconf vipa list"
$ sudo qethconf vipa list
vipa add 10.205.1.100 encc003
--
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: Defining a vipa
Thanks! (yes, I *meant* /sys :)
I did a bit of googling trying to help Gadi out - I've no experience of
setting up VIPA etc. under linux myself yet. However, I can see it might be
required in future on one of the systems I work on so the below is very helpful.
Lee.
On Tue, May 21 2019, Christian Ehrhardt wrote:
> On Tue, May 21, 2019 at 10:47 AM Lee B wrote:
>>
>> How about:
>>
>> https://www.ibm.com/support/knowledgecenter/en/linuxonibm/com.ibm.linux.z.lhdd/lhdd_t_qeth_wrk_layer2.html
>>
>> That's for SuSE, but I guess there's something similar lurking in /proc
>> for Ubuntu somewhere?
>
> $ cat /sys/devices/qeth/0.0.c000/layer2
> 1
>
> The same on Ubuntu as we all have the same s390x kernel code exposing that
> path.
>
> IMHO the difference starts when you think about tooling as the network
> config differs and for both depends on versions.
>
> E.g. for my interface above you'd have
> /etc/sysconfig/hardware.back/config-ccw-0.0.c000:2:QETH_OPTIONS=(layer2)
> /etc/udev/rules.d/41-qeth-0.0.c003.rules:18:ATTR{[ccwgroup/0.0.c003]layer2}="1"
>
> But nobody wants to mess with all those files manually.
> And in fact this is generated by IBMs lszdev/chzdev tooling.
> Take a look at the man page and maybe:
> $ chzdev qeth --help-attribute layer2
> I think from here things are rather clear.
>
> With that in mind looking at one of my devices that I can spare.
>
> $ lszdev 0.0.c003 --columns TYPE,ID,ON,PERS,NAMES,ATTR:layer2
> TYPE ID ON PERS NAMESATTR:layer2
> qeth 0.0.c003:0.0.c004:0.0.c005 yes yes encc003 1/1
>
> The following could be simplified, but for illustration disabling layer2:
>
> $ sudo chzdev -d qeth 0.0.c003
> QETH device 0.0.c003:0.0.c004:0.0.c005 deconfigured
> $ sudo chzdev qeth c003 layer2=0
> QETH device 0.0.c003:0.0.c004:0.0.c005 configured
> $ sudo chzdev -e qeth 0.0.c003
> QETH device 0.0.c003:0.0.c004:0.0.c005 configured
> $ lszdev 0.0.c003 --columns TYPE,ID,ON,PERS,NAMES,ATTR:layer2
> TYPE ID ON PERS NAMESATTR:layer2
> qeth 0.0.c003:0.0.c004:0.0.c005 yes yes encc003 0/0
>
> And then you can enable vipa:
>
> $ sudo qethconf vipa add 10.205.1.100 encc003
> qethconf: Added 10.205.1.100 to sysfs entry
> /sys/class/net/encc003/device/vipa/add4.
> qethconf: For verification please use "qethconf vipa list"
> $ sudo qethconf vipa list
> vipa add 10.205.1.100 encc003
>
> --
> 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
2FA in the Linux Terminal Server
Hi All, In our Linux machines 2 Factor Authentication is required. So we use a PKI card and the putty agent to connect to the Linux machines. We also have a Linux Terminal Server and we can login to that with PKI as well. When I use ssh within the terminal server to connect to another Linux guest it too uses the PKI based login, but obviously that is limited to guests in specific (IP) networks only. Through iucvconn we would be able to connect to all Linux machines in our VM cluster. But with iucvconn an userid/password authentication is used. Is there a way to use the PKI login in the iucvconn as well just like the ssh login does? Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen, Berry van Sleeuwen Flight Forum 3000 5657 EW Eindhoven • +31 (0)6 22564276 [cid:image001.jpg@01CE3508.E10AE080] [cid:image002.jpg@01CE3508.E10AE080] This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, Atos’ liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. On all offers and agreements under which Atos Nederland B.V. supplies goods and/or services of whatever nature, the Terms of Delivery from Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly submitted to you on your request. -- 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
NEW: Linux on Z and LinuxONE videos for Pervasive Encryption
Linux on Z and LinuxONE Setting up Data Volumes for Pervasive Encryption - in less than ten minutes A new Linux security video illlustrates the ease of setting up data volumes for pervasive encryption. See: https://youtu.be/t2Ph_h0LcsQ Watch also the conceptual video to pervasive encryption for Linux on Z and LinuxONE: Pervasive Encryption for Data Volumes This Linux video illlustrates how pervasive encryption for data volumes makes full data volume encryption fast and affordable. See: https://youtu.be/jDK3ZwEdX4I Dorothea Matthaeus Linux on Z and LinuxONE Information Development IBM Deutschland Research and Development GmbH -- 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: 2FA in the Linux Terminal Server
Hi Berry, On Tue, May 21, 2019 at 10:01:24AM +, van Sleeuwen, Berry wrote: > In our Linux machines 2 Factor Authentication is required. So we use a PKI > card and the putty agent to connect to the Linux machines. > > We also have a Linux Terminal Server and we can login to that with PKI as > well. When I use ssh within the terminal server to connect to another Linux > guest it too uses the PKI based login, but obviously that is limited to > guests in specific (IP) networks only. Through iucvconn we would be able to > connect to all Linux machines in our VM cluster. But with iucvconn an > userid/password authentication is used. Is there a way to use the PKI login > in the iucvconn as well just like the ssh login does? Iucvconn presents you the login prompt from the getty that runs on the HVC console devices of target systems. If the PKI 2FA is configured for SSH through a PAM plugin, you might change the respective configuration for terminal logins as well. Kind regards, Hendrik -- Hendrik Brueckner brueck...@linux.ibm.com | IBM Deutschland Research & Development GmbH Linux on z Systems Development| Schoenaicher Str. 220, 71032 Boeblingen IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Matthias Hartmann Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 -- 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
Martin Schwidefsky
To all, Today I learned that Martin Schwidefsky has died in a parachute accident.(see attached url for translated news story). Martin was a deeply technical person, with Linux kernel expertise. He presented at many technical conferences and was always willing to discuss and dig into the Linux puzzles. I have worked on multiple technical issues with Martin, and while he could overwhelm my linux technical knowledge easily, he was always willing to help me learn. Martin’s intelligence, wit and good nature will be missed. Regards Phil Tully https://translate.google.com/translate?hl=&sl=de&tl=en&u=https%3A%2F%2Fwww.focus.de%2Fpanorama%2Fwelt%2Fdrama-in-baden-wuerttemberg-fallschirmspringer-schlagen-auf-boden-auf-und-sterben-ursache-ist-klar_id_10728579.html -- 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: Martin Schwidefsky
This is a painful loss. I met Martin on several occasions. He was bright and articulate and eminently approachable. -- R; <>< On Tue, May 21, 2019, 8:47 AM PHILIP TULLY wrote: > To all, > > Today I learned that Martin Schwidefsky has died in a parachute > accident.(see attached url for translated news story). > > Martin was a deeply technical person, with Linux kernel expertise. He > presented at many technical conferences and was always willing to > discuss and dig into the Linux puzzles. > > I have worked on multiple technical issues with Martin, and while he > could overwhelm my linux technical knowledge easily, he was always > willing to help me learn. > > Martin’s intelligence, wit and good nature will be missed. > > Regards > Phil Tully > > > > > https://translate.google.com/translate?hl=&sl=de&tl=en&u=https%3A%2F%2Fwww.focus.de%2Fpanorama%2Fwelt%2Fdrama-in-baden-wuerttemberg-fallschirmspringer-schlagen-auf-boden-auf-und-sterben-ursache-ist-klar_id_10728579.html > > -- > 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: Martin Schwidefsky
That is sad news indeed. Like Rick, I had met him a few times and found him friendly and approachable. A great loss. DJ --- DAVID JONES | MANAGING DIRECTOR FOR ZSYSTEMS SERVICES | z/VM, Linux, and Cloud 703.237.7370 (Office) | 281.578.7544 (CELL) INFORMATION TECHNOLOGY COMPANY On 05.21.2019 8:20 AM, Rick Troth wrote: This is a painful loss. I met Martin on several occasions. He was bright and articulate and eminently approachable. -- R; <>< On Tue, May 21, 2019, 8:47 AM PHILIP TULLY wrote: To all, Today I learned that Martin Schwidefsky has died in a parachute accident.(see attached url for translated news story). Martin was a deeply technical person, with Linux kernel expertise. He presented at many technical conferences and was always willing to discuss and dig into the Linux puzzles. I have worked on multiple technical issues with Martin, and while he could overwhelm my linux technical knowledge easily, he was always willing to help me learn. Martin’s intelligence, wit and good nature will be missed. Regards Phil Tully https://translate.google.com/translate?hl=&sl=de&tl=en&u=https%3A%2F%2Fwww.focus.de%2Fpanorama%2Fwelt%2Fdrama-in-baden-wuerttemberg-fallschirmspringer-schlagen-auf-boden-auf-und-sterben-ursache-ist-klar_id_10728579.html -- 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 -- 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: Martin Schwidefsky
I too am saddened by this news. I enjoyed attending Martin's presentations at SHARE and other events learning about s390x enablement in the Linux kernel. I always said hello to Martin when in Boblingen. Even though he was very busy he would always stop to chat. Martin will be missed! Mike On 5/21/19 7:46 AM, PHILIP TULLY wrote: > To all, > > Today I learned that Martin Schwidefsky has died in a parachute > accident.(see attached url for translated news story). > > Martin was a deeply technical person, with Linux kernel expertise. He > presented at many technical conferences and was always willing to > discuss and dig into the Linux puzzles. > > I have worked on multiple technical issues with Martin, and while he > could overwhelm my linux technical knowledge easily, he was always > willing to help me learn. > > Martin’s intelligence, wit and good nature will be missed. > > Regards > Phil Tully > > > > https://translate.google.com/translate?hl=&sl=de&tl=en&u=https%3A%2F%2Fwww.focus.de%2Fpanorama%2Fwelt%2Fdrama-in-baden-wuerttemberg-fallschirmspringer-schlagen-auf-boden-auf-und-sterben-ursache-ist-klar_id_10728579.html > > > > -- > 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
