Re: cio_ignore

2021-01-07 Thread Bill Head 
Thank you Viktor!!  

Right you are, I should have used chzdev instead of znetconf -a.  The devices 
are displaying as Pers YES with the lszdev command.  I removed the devices from 
the /etc/dasd.conf file (temporarily added them there so they wouldn't be 
ignored), rebooted and they are active.  




Thank you, 
Bill

Bill Head
Lead Systems Engineer
z/VM Mainframe Support
IBM Global Technology Services-Solutions

Humana: Contractor/Temporary Staff – IT Systems Technician

/Office:   (502) 262-7563
 Email:   bh...@humana.com
bEmail:   billh...@us.ibm.com






-Original Message-
From: Linux on 390 Port  On Behalf Of Viktor 
Mihajlovski
Sent: Thursday, January 7, 2021 4:02 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: cio_ignore

[External Email: Use caution with links and attachments]


On 1/7/21 4:41 AM, Bill Head wrote:
> On RHEL 8.2 I'm having a problem with cio_ignore.  I can remove devices from 
> the blacklist but when I reboot they are exluded again:
>
> cio_ignore -L
> Devices that are not ignored:
> =
> 0.0.0009
> 0.0.0150
> 0.0.0300-0.0.0301
> 0.0.0700-0.0.0702
> 0.0.1000-0.0.1002
> 0.0.2000-0.0.2002
>
> After the reboot:
>
> cio_ignore -L
> Devices that are not ignored:
> =
> 0.0.0009
> 0.0.0150
> 0.0.0300-0.0.0301
> 0.0.0700-0.0.0702
>
> It's ignoring 1000-1002, and 2000-2002.
>
> cio_ignore settings are supposed to survive a boot, correct?
>
>

[snip]

That's not the case. Upon reboot, the kernel command line determines the 
devices seen by the operating system. In a next step the configured devices are 
been freed from the ignore list. In your example the console (0009), the boot 
disk (0150) and two QETH devices (0300-0302, 0700-0702) are removed from the 
ignore list. If you want 1000-1002 and 2000-2002 to be persistently available 
you should configure them, e.g. using chzdev(8).

--
Kind Regards,
Viktor

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit 
https://urldefense.com/v3/__http://www2.marist.edu/htbin/wlvindex?LINUX-390__;!!IfVdvpvC!E5pGzxyHs8IlBGAvXegBzz1l_wiY6yiJRGV440a0u2bNoZlHzzmIOXihb-rW$

The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material.  If you receive this 
material/information in error,
please contact the sender and delete or destroy the material/information.

Humana Inc. and its subsidiaries comply with applicable Federal civil rights 
laws and
do not discriminate on the basis of race, color, national origin, ancestry, 
age, disability, sex,
marital status, gender, sexual orientation, gender identity, or religion. 
Humana Inc. and its subsidiaries do not
exclude people or treat them differently because of race, color, national 
origin, ancestry, age,
disability, sex, marital status, gender, sexual orientation, gender identity, 
or religion.

English: ATTENTION: If you do not speak English, language assistance services, 
free
of charge, are available to you. Call 1‐877‐320‐1235 (TTY: 711).

Español (Spanish): ATENCIÓN: Si habla español, tiene a su disposición servicios
gratuitos de asistencia lingüística. Llame al 1‐877‐320‐1235 (TTY: 711).

繁體中文(Chinese):注意:如果您使用繁體中文,您可以免費獲得語言援助
服務。請致電 1‐877‐320‐1235 (TTY: 711)。

Kreyòl Ayisyen (Haitian Creole): ATANSION: Si w pale Kreyòl Ayisyen, gen sèvis 
èd
pou lang ki disponib gratis pou ou. Rele 1‐877‐320‐1235 (TTY: 711).

Polski (Polish): UWAGA: Jeżeli mówisz po polsku, możesz skorzystać z bezpłatnej
pomocy językowej. Zadzwoń pod numer 1‐877‐320‐1235 (TTY: 711).

한국어 (Korean): 주의: 한국어를 사용하시는 경우, 언어 지원 서비스를 무료로
이용하실 수 있습니다. 1‐877‐320‐1235 (TTY: 711)번으로 전화해 주십시오.


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390

Re: cio_ignore

2021-01-07 Thread Bill Head 
 on a 3270 session:

   
 [1;31mlxgtmp21 root:~> [0;37m lszdev  
lszdev 
TYPE ID  ON   PERS  NAMES  
dasd-eckd0.0.0150yes  nodasda  
qeth 0.0.0700:0.0.0701:0.0.0702  yes  noenc700 
qeth 0.0.1000:0.0.1001:0.0.1002  no   no   
qeth 0.0.2000:0.0.2001:0.0.2002  no   no   
generic-ccw  0.0.0009yes  no   
 [1;31mlxgtmp21 root:~> [0;37m 

They don't show up in ifconfig, but bond0 and bond0.10 do, I can see the 
correct gateway in netstat -rn.  

Any ideas on how to get this up on the network?







-Original Message-
From: Linux on 390 Port  On Behalf Of Dan Horák
Sent: Thursday, January 7, 2021 7:03 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: cio_ignore

[External Email: Use caution with links and attachments]


On Thu, 7 Jan 2021 03:41:07 +
Bill Head  wrote:

> On RHEL 8.2 I'm having a problem with cio_ignore.  I can remove devices from 
> the blacklist but when I reboot they are exluded again:
>
> cio_ignore -L
> Devices that are not ignored:
> =
> 0.0.0009
> 0.0.0150
> 0.0.0300-0.0.0301
> 0.0.0700-0.0.0702
> 0.0.1000-0.0.1002
> 0.0.2000-0.0.2002
>
> After the reboot:
>
> cio_ignore -L
> Devices that are not ignored:
> =
> 0.0.0009
> 0.0.0150
> 0.0.0300-0.0.0301
> 0.0.0700-0.0.0702
>
> It's ignoring 1000-1002, and 2000-2002.
>
> cio_ignore settings are supposed to survive a boot, correct?

the device id list to "un-ignore" is created dynamicaly during the boot based 
on the content of /etc/dasd.conf, /etc/zfcp.conf and the network interface 
configuration.


Dan

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit 
https://urldefense.com/v3/__http://www2.marist.edu/htbin/wlvindex?LINUX-390__;!!IfVdvpvC!Df_0E0Mntwm8ffz9Gxz8-OFn9ZT2ZvTkGuRSyV6Sc-_kZoVfLFqu76LEkMhy$

The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material.  If you receive this 
material/information in error,
please contact the sender and delete or destroy the material/information.

Humana Inc. and its subsidiaries comply with applicable Federal civil rights 
laws and
do not discriminate on the basis of race, color, national origin, ancestry, 
age, disability, sex,
marital status, gender, sexual orientation, gender identity, or religion. 
Humana Inc. and its subsidiaries do not
exclude people or treat them differently because of race, color, national 
origin, ancestry, age,
disability, sex, marital status, gender, sexual orientation, gender identity, 
or religion.

English: ATTENTION: If you do not speak English, language assistance services, 
free
of charge, are available to you. Call 1‐877‐320‐1235 (TTY: 711).

Español (Spanish): ATENCIÓN: Si habla español, tiene a su disposición servicios
gratuitos de asistencia lingüística. Llame al 1‐877‐320‐1235 (TTY: 711).

繁體中文(Chinese):注意:如果您使用繁體中文,您可以免費獲得語言援助
服務。請致電 1‐877‐320‐1235 (TTY: 711)。

Kreyòl Ayisyen (Haitian Creole): ATANSION: Si w pale Kreyòl Ayisyen, gen sèvis 
èd
pou lang ki disponib gratis pou ou. Rele 1‐877‐320‐1235 (TTY: 711).

Polski (Polish): UWAGA: Jeżeli mówisz po polsku, możesz skorzystać z bezpłatnej
pomocy językowej. Zadzwoń pod numer 1‐877‐320‐1235 (TTY: 711).

한국어 (Korean): 주의: 한국어를 사용하시는 경우, 언어 지원 서비스를 무료로
이용하실 수 있습니다. 1‐877‐320‐1235 (TTY: 711)번으로 전화해 주십시오.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390

cio_ignore

2021-01-06 Thread Bill Head 
On RHEL 8.2 I'm having a problem with cio_ignore.  I can remove devices from 
the blacklist but when I reboot they are exluded again:

cio_ignore -L
Devices that are not ignored:
=
0.0.0009
0.0.0150
0.0.0300-0.0.0301
0.0.0700-0.0.0702
0.0.1000-0.0.1002
0.0.2000-0.0.2002

After the reboot:

cio_ignore -L
Devices that are not ignored:
=
0.0.0009
0.0.0150
0.0.0300-0.0.0301
0.0.0700-0.0.0702

It's ignoring 1000-1002, and 2000-2002.

cio_ignore settings are supposed to survive a boot, correct?







The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material.  If you receive this 
material/information in error,
please contact the sender and delete or destroy the material/information.

Humana Inc. and its subsidiaries comply with applicable Federal civil rights 
laws and
do not discriminate on the basis of race, color, national origin, ancestry, 
age, disability, sex,
marital status, gender, sexual orientation, gender identity, or religion. 
Humana Inc. and its subsidiaries do not
exclude people or treat them differently because of race, color, national 
origin, ancestry, age,
disability, sex, marital status, gender, sexual orientation, gender identity, 
or religion.

English: ATTENTION: If you do not speak English, language assistance services, 
free
of charge, are available to you. Call 1‐877‐320‐1235 (TTY: 711).

Español (Spanish): ATENCIÓN: Si habla español, tiene a su disposición servicios
gratuitos de asistencia lingüística. Llame al 1‐877‐320‐1235 (TTY: 711).

繁體中文(Chinese):注意:如果您使用繁體中文,您可以免費獲得語言援助
服務。請致電 1‐877‐320‐1235 (TTY: 711)。

Kreyòl Ayisyen (Haitian Creole): ATANSION: Si w pale Kreyòl Ayisyen, gen sèvis 
èd
pou lang ki disponib gratis pou ou. Rele 1‐877‐320‐1235 (TTY: 711).

Polski (Polish): UWAGA: Jeżeli mówisz po polsku, możesz skorzystać z bezpłatnej
pomocy językowej. Zadzwoń pod numer 1‐877‐320‐1235 (TTY: 711).

한국어 (Korean): 주의: 한국어를 사용하시는 경우, 언어 지원 서비스를 무료로
이용하실 수 있습니다. 1‐877‐320‐1235 (TTY: 711)번으로 전화해 주십시오.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390

Re: zLINUX end user provisioning

2019-12-12 Thread Bill Head 
> like, where and how to put an ISO

On LINUX or AIX you can use a "loopback" option to mount an ISO on a directory. 
 The command might differ depending on your distro.  I use an AIX server for 
staging install images, AIX has a command specifically for mounting an ISO as 
opposed to using the mount command with loopback option on LINUX:

AIX:
ISO image cdrom.iso, mount directory /mnt:
loopmount -i cdrom.iso -o "-V cdrfs -o ro" -m /mnt

On LINUX I think it looks something like this:

mount -t iso9660 -o loop /tmp/cdrom.iso /mnt

Then you can copy the files from the iso mount to a filesystem on your staging 
server. 






-Original Message-
From: Linux on 390 Port  On Behalf Of Hamilton, Robert
Sent: Wednesday, December 11, 2019 11:11 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: zLINUX end user provisioning

I'm interested in this too. I am following the read-only root documentation, 
which is starting to show its age a little (RedPaper redp4322 is good, but 
copyright 2008), but still has good stuff about gold instances, maintenance and 
cloning.
The other documents I have are the workbooks from some VM and Linux 
installation classes I've taken, but a lot of the preparation stuff is skipped 
over.

like, where and how to put an ISO. Nothing I've found in any cookbook says how 
it was done, or what tools I can use to manage or unpack an ISO. BFS? OMVS? RPI?

I'm just interested in the latest doc. I'm trying to install ClefOS and manage 
it as cleanly as possible.

R;


Rob Hamilton
Infrastructure Engineer
Chemical Abstracts Service


-Original Message-
From: Linux on 390 Port  On Behalf Of Michael MacIsaac
Sent: Wednesday, December 11, 2019 10:24 AM
To: LINUX-390@VM.MARIST.EDU
Subject: [EXT] Re: zLINUX end user provisioning

[Actual Sender is owner-linux-...@vm.marist.edu]

Jake,

Which cookbook are you using?

-Mike M

On Wed, Dec 11, 2019 at 10:20 AM Jake Anderson 
wrote:

> Hello
>
> I am pretty new to zLINUX provisioning.
>
> I have used cookbook to build Linux and if functional.
>
> From the provisioning part untill which chapter of cookbook i can follow ?
>
> Generally untill which chapter will be followed to provision the Linux 
> guest ?
>
> Jake
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions, send 
> email to lists...@vm.marist.edu with the message: INFO LINUX-390 or 
> visit
> https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.
> marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390data=02%7C01%7Cbhead%40h
> umana.com%7C3f0bc2bf3bc44883ef4108d77e56886a%7C56c62bbe85984b859e511ca
> 753fa50f2%7C1%7C0%7C637116782433649540sdata=qBYUTwyskOye5ijNdxJp9
> TgpjSmKLuI6tOqEORz1nPE%3Dreserved=0
>


--
 -Mike MacIsaac

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390data=02%7C01%7Cbhead%40humana.com%7C3f0bc2bf3bc44883ef4108d77e56886a%7C56c62bbe85984b859e511ca753fa50f2%7C1%7C0%7C637116782433649540sdata=qBYUTwyskOye5ijNdxJp9TgpjSmKLuI6tOqEORz1nPE%3Dreserved=0
Confidentiality Notice: This electronic message transmission, including any 
attachment(s), may contain confidential, proprietary, or privileged information 
from CAS, a division of the American Chemical Society ("ACS"). If you have 
received this transmission in error, be advised that any disclosure, copying, 
distribution, or use of the contents of this information is strictly 
prohibited. Please destroy all copies of the message and contact the sender 
immediately by either replying to this message or calling 614-447-3600.


--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390data=02%7C01%7Cbhead%40humana.com%7C3f0bc2bf3bc44883ef4108d77e56886a%7C56c62bbe85984b859e511ca753fa50f2%7C1%7C0%7C637116782433659535sdata=jGJVuwaoH4ON4rgEwY64LYR0HBkGu6zEYqfFy%2FUIgvc%3Dreserved=0

The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material.  If you receive this 
material/information in error,
please contact the sender and delete or destroy the material/information.

Humana Inc. and its subsidiaries comply with applicable Federal civil rights 
laws and
do not discriminate on the basis of race, color, national origin, age, 
disability, sex,
sexual orientation, gender identity, or religion. Humana Inc. and its 
subsidiaries do not
exclude people or treat them differently because of race, color, national 
origin, age,

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

2017-03-09 Thread Bill Head 
Got it, in bond0

NETWORK='162.101.1.0'  << removed address
BROADCAST='162.101.1.255'
STARTMODE='onboot'
VLAN='YES'   <<  removed
VLAN_ID=10  <<  added this parm

Actually YaST did it for me, when I changed the VLAN from 0 to 10 in the yast 
screen for bon0, then looked at it's ifcfg file:


ETHERDEVICE='bond0'
IPADDR='193.91.10.24/24'
NETMASK='255.255.255.0'
NAME='VLAN access'
NETWORK=''
BROADCAST=''
STARTMODE='auto'
VLAN='YES'
BOOTPROTO='static'
ETHTOOL_OPTIONS=''
MTU=''
REMOTE_IPADDR=''
USERCONTROL='no'
VLAN_ID='10'

Now when I remove eth0 and not sure if I will break the bonding, if the eth 
addresses change, we shall see. 



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Marcy 
Cortes
Sent: Thursday, March 09, 2017 1:56 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DEDICATED OSA, LINUX VLAN tagging and bonding

How about telling ping which interface to use? I think it's minus i parm but I 
am not by a computer at the moment



Marcy

-Original Message-----
From: Bill Head [bh...@humana.com<mailto:bh...@humana.com>]
Sent: Thursday, March 09, 2017 12:46 PM Central Standard Time
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] DEDICATED OSA, LINUX VLAN tagging and bonding


Yep, found that in the meantime.  I did this for both eth1 and eth2

qeth_configure -l -t qeth 0.0.1000 0.0.1001 0.0.1002# DEDICATE device to 
1000, 1001, and 1002
qeth_configure -l -t qeth 0.0.2001 0.0.2001 0.0.2002   # assigned the 2000's to 
the second OSA

set routes to the default router

ifup eth1
ifup eth2

lxgonep1:root:/etc/sysconfig/network> cat routes cat routes default 
193.91.10.254 - - lxgonep1:root:/etc/sysconfig/network> rcnetwork restart 
rcnetwork restart Shutting down network interfaces:
vlan10name: VLAN access
..donebond0
8021q: adding VLAN 0 to HW filter on device bond0
bonding: bond0: Removing slave eth1.
bonding: bond0: releasing active interface eth1
bonding: bond0: making interface eth2 the new active one.
bonding: bond0: Removing slave eth2.
bonding: bond0: releasing active interface eth2
bonding: bond0 is being deleted...
..doneeth0
..doneeth1  name: OSA Express Network card (0.0.1000)
..doneeth2  name: OSA Express Network card (0.0.2000)
..doneShutting down service network  .  .  .  .  .  .  .  .  ...done
Hint: you may set mandatory devices in /etc/sysconfig/network/config Setting up 
network interfaces:
Mar  9 13:40:20 lxgonep1 SuSEfirewall2: SuSEfirewall2 not active
eth0
8021q: adding VLAN 0 to HW filter on device eth0
eth0  IP address: 205.145.91.142/24
Mar  9 13:40:21 lxgonep1 SuSEfirewall2: SuSEfirewall2 not active
..doneeth1  name: OSA Express Network card (0.0.1000)
qeth.cc0c57: 0.0.1000: MAC address 02:00:00:00:01:ef successfully registered on 
device eth1
8021q: adding VLAN 0 to HW filter on device eth1
..doneeth2  name: OSA Express Network card (0.0.2000)
qeth.cc0c57: 0.0.2000: MAC address 02:00:00:00:01:fe successfully registered on 
device eth2
8021q: adding VLAN 0 to HW filter on device eth2
..donebond0
bonding: bond0 is being created...
bonding: bond0: setting mode to active-backup (1).
bonding: bond0: Setting fail_over_mac to active (1).
bonding: bond0: Setting MII monitoring interval to 100.
qeth.cc0c57: 0.0.1000: MAC address 02:00:00:00:01:ef successfully registered on 
device eth1
bonding: bond0: Adding slave eth1.
8021q: adding VLAN 0 to HW filter on device eth1
bonding: bond0: making interface eth1 the new active one.
bonding: bond0: first active interface up!
bonding: bond0: enslaving eth1 as an active interface with an up link.
bond0 enslaved interface: eth1
qeth.cc0c57: 0.0.2000: MAC address 02:00:00:00:01:fe successfully registered on 
device eth2
bonding: bond0: Adding slave eth2.
8021q: adding VLAN 0 to HW filter on device eth2
bonding: bond0: enslaving eth2 as a backup interface with an up link.
bond0 enslaved interface: eth2
8021q: adding VLAN 0 to HW filter on device bond0
..donevlan10name: VLAN access
vlan10IP address: 193.91.10.24/24
..doneSetting up service network  .  .  .  .  .  .  .  .  .  ...done

But can't ping the default gateway

lxgonep1:root:/etc/sysconfig/network> ping -c2 193.91.10.254 ping -c2 
193.91.10.254 PING 193.91.10.254 (193.91.10.254) 56(84) bytes of data.
From 193.91.10.24: icmp_seq=1 Destination Host Unreachable From 193.91.10.24 
icmp_seq=1 Destination Host Unreachable From 193.91.10.24 icmp_seq=2 
Destination Host Unreachable

--- 193.91.10.254 ping statistics ---
2 packets transmitted, 0 received, +3 errors, 100% packet loss, time 1008ms , 
pipe 2 lxgonep1:root:/etc/sysconfig/network>

I'm missing something here, but I'm getting closer..




-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Marcy 
Cortes
Sent: Thursday, March 09, 2017 1:13 PM
To:

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

2017-03-09 Thread Bill Head 
54) 56(84) bytes of data.   
From 193.91.10.24: icmp_seq=1 Destination Host Unreachable 
From 193.91.10.24 icmp_seq=1 Destination Host Unreachable  
From 193.91.10.24 icmp_seq=2 Destination Host Unreachable  
   
--- 193.91.10.254 ping statistics ---  
2 packets transmitted, 0 received, +3 errors, 100% packet loss, time 1008ms
, pipe 2   
lxgonep1:root:/etc/sysconfig/network>  
   
I'm missing something here, but I'm getting closer..
   




-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Marcy 
Cortes
Sent: Thursday, March 09, 2017 1:13 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DEDICATED OSA, LINUX VLAN tagging and bonding

What does lsqeth telll you? Are there files in /etc/udev/rules.d for them? If 
not qeth_configure might be needed



Marcy

-Original Message-
From: Bill Head [bh...@humana.com<mailto:bh...@humana.com>]
Sent: Thursday, March 09, 2017 11:02 AM Central Standard Time
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] DEDICATED OSA, LINUX VLAN tagging and bonding


I'm still using eth0 using a vswitch so I can putty in and make changes.  I 
created the ifcfg-eth1, ifcfg-eth2, ifcfg-bond0, and ifcfg-vlan10.   Made 
changes to bond0 to make eth1 and eth2 slaves.  When I boot it looks like it 
can't find eth1 and eth2.   Any ideas?

..doneWaiting for mandatory devices:  eth1 eth2
18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
bonding: Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
bonding: bond0 is being created...
bonding: bond0: setting mode to active-backup (1).
bonding: bond0: Setting fail_over_mac to active (1).
bonding: bond0: Setting MII monitoring interval to 100.
eth1No interface found
..failedeth2No interface found
..failedbond0
bond0 skipping interface: eth1 (missed)
bond0 skipping interface: eth2 (missed)
Removing bonding interface 'bond0'
bond0
Mar  9 11:11:09 lxgonep1 ifup-bonding: Removing bonding interface 'bond0'
ADDRCONF(NETDEV_UP): bond0: link is not ready
bonding: bond0 is being deleted...
..donevlan10name: VLAN access
Cannot find device "bond0"
interface 'bond0' is not up
Mar  9 11:11:10 lxgonep1 ifup-802.1q: interface 'bond0' is not up ..doneSetting 
up service (localfs) network  .  .  .  .  .  .  .  .  .  ...faile

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Marcy 
Cortes
Sent: Tuesday, March 07, 2017 6:44 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DEDICATED OSA, LINUX VLAN tagging and bonding

Yea, i didn't include the VLAN in the presentation.  You'd only need it if you 
didn't have a default vlan that worked for that interface with that IP.

You're welcome and good luck!


-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Bill Head
Sent: Tuesday, March 07, 2017 3:31 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] DEDICATED OSA, LINUX VLAN tagging and bonding

Yep, that's what I need.  I didn't see where you had examples of VLAN tagging 
in your presentation, also didn't want to keep bugging you about this.   I 
really do appreciate the help!

FYI: you are right about not having to specify the module, support got back to 
me and said it was included in the kernel and no longer necessary.  Got my 
hands on dated "how to" links on the interweb.

Many thanks!


-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Marcy 
Cortes
Sent: Tuesday, March 07, 2017 5:30 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DEDICATED OSA, LINUX VLAN tagging and bonding

Hi,

I have vlan tagged channel bonded interfaces on xDR proxies.  Maybe it will 
help just to show you.
In my case VLAN number is 71 and the IP address used here is 162.101.1.129.   
You need to make up unique LLADDR's.   Generally i think it's start them with 
02:00:00 to indicate user made up (Alan can correct me there if I misremembered 
that :)

rename off your vswitch configs so in case you need to get back its easy :)


xdr91:/etc/sysconfig/network # cat ifcfg-bond0 BOOTPROTO='static'
STARTMODE='onboot'
BONDING_MASTER='yes'
BONDING_MODULE_OPTS='mode=active-backup fail_over_mac=active miimon=100'
BONDING_SLAVE0='eth0'
BONDING_SLAVE1='eth1'


xdr91:/etc/sysconfig/network # cat ifcfg-vlan71 ETHERDEVICE='bond0'
IPADDR='162.101.1.129'
NETMASK='255.255.255.0'
NAME='VLAN access'
NETWORK='162.101.1.0'
BROADCAST='162.1

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

2017-03-09 Thread Bill Head 
I'm still using eth0 using a vswitch so I can putty in and make changes.  I 
created the ifcfg-eth1, ifcfg-eth2, ifcfg-bond0, and ifcfg-vlan10.   Made 
changes to bond0 to make eth1 and eth2 slaves.  When I boot it looks like it 
can't find eth1 and eth2.   Any ideas?

..doneWaiting for mandatory devices:  eth1 eth2 
18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0  
bonding: Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)   
bonding: bond0 is being created...  
bonding: bond0: setting mode to active-backup (1).  
bonding: bond0: Setting fail_over_mac to active (1).
bonding: bond0: Setting MII monitoring interval to 100. 
eth1No interface found  
..failedeth2No interface found  
..failedbond0   
bond0 skipping interface: eth1 (missed) 
bond0 skipping interface: eth2 (missed) 
Removing bonding interface 'bond0'  
bond0   
Mar  9 11:11:09 lxgonep1 ifup-bonding: Removing bonding interface 'bond0'   
ADDRCONF(NETDEV_UP): bond0: link is not ready   
bonding: bond0 is being deleted...  
..donevlan10name: VLAN access   
Cannot find device "bond0"  
interface 'bond0' is not up 
Mar  9 11:11:10 lxgonep1 ifup-802.1q: interface 'bond0' is not up   
..doneSetting up service (localfs) network  .  .  .  .  .  .  .  .  .  ...faile

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Marcy 
Cortes
Sent: Tuesday, March 07, 2017 6:44 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DEDICATED OSA, LINUX VLAN tagging and bonding

Yea, i didn't include the VLAN in the presentation.  You'd only need it if you 
didn't have a default vlan that worked for that interface with that IP.

You're welcome and good luck!


-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Bill Head
Sent: Tuesday, March 07, 2017 3:31 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] DEDICATED OSA, LINUX VLAN tagging and bonding

Yep, that's what I need.  I didn't see where you had examples of VLAN tagging 
in your presentation, also didn't want to keep bugging you about this.   I 
really do appreciate the help!  

FYI: you are right about not having to specify the module, support got back to 
me and said it was included in the kernel and no longer necessary.  Got my 
hands on dated "how to" links on the interweb.  

Many thanks! 


-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Marcy 
Cortes
Sent: Tuesday, March 07, 2017 5:30 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DEDICATED OSA, LINUX VLAN tagging and bonding

Hi,

I have vlan tagged channel bonded interfaces on xDR proxies.  Maybe it will 
help just to show you.
In my case VLAN number is 71 and the IP address used here is 162.101.1.129.   
You need to make up unique LLADDR's.   Generally i think it's start them with 
02:00:00 to indicate user made up (Alan can correct me there if I misremembered 
that :) 

rename off your vswitch configs so in case you need to get back its easy :)


xdr91:/etc/sysconfig/network # cat ifcfg-bond0 BOOTPROTO='static'
STARTMODE='onboot'
BONDING_MASTER='yes'
BONDING_MODULE_OPTS='mode=active-backup fail_over_mac=active miimon=100'
BONDING_SLAVE0='eth0'
BONDING_SLAVE1='eth1'


xdr91:/etc/sysconfig/network # cat ifcfg-vlan71 ETHERDEVICE='bond0'
IPADDR='162.101.1.129'
NETMASK='255.255.255.0'
NAME='VLAN access'
NETWORK='162.101.1.0'
BROADCAST='162.101.1.255'
STARTMODE='onboot'
VLAN='YES'


xdr91:/etc/sysconfig/network # cat ifcfg-eth0 BOOTPROTO='static'
IPADDR=''
BROADCAST=''
STARTMODE='auto'
LLADDR=''
NAME='OSA Express Network card (0.0.3000)'
ETHTOOL_OPTIONS=''
MTU=''
NETWORK=''
REMOTE_IPADDR=''
USERCONTROL='no'
SLAVE='yes'
LLADDR='02:00:00:00:91:EF'


xdr91:/etc/sysconfig/network # cat ifcfg-eth1 BOOTPROTO='static'
IPADDR=''
BROADCAST=''
STARTMODE='auto'
LLADDR=''
NAME='OSA Express Network card (0.0.4000)'
ETHTOOL_OPTIONS=''
MTU=''
NETWORK=''
REMOTE_IPADDR=''
USERCONTROL='no'
SLAVE='yes'
LLADDR='02:00:00:00:91:EE'

xdr91:/etc/sysconfig/network # cat routes default 162.101.1.1 - -


The bonding and 8021q modules seem to have loaded themselves - I couldn’t find 
anything specific to them in /etc/modprobe.d

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

2017-03-07 Thread Bill Head 
Yep, that's what I need.  I didn't see where you had examples of VLAN tagging 
in your presentation, also didn't want to keep bugging you about this.   I 
really do appreciate the help!  

FYI: you are right about not having to specify the module, support got back to 
me and said it was included in the kernel and no longer necessary.  Got my 
hands on dated "how to" links on the interweb.  

Many thanks! 


-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Marcy 
Cortes
Sent: Tuesday, March 07, 2017 5:30 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DEDICATED OSA, LINUX VLAN tagging and bonding

Hi,

I have vlan tagged channel bonded interfaces on xDR proxies.  Maybe it will 
help just to show you.
In my case VLAN number is 71 and the IP address used here is 162.101.1.129.   
You need to make up unique LLADDR's.   Generally i think it's start them with 
02:00:00 to indicate user made up (Alan can correct me there if I misremembered 
that :) 

rename off your vswitch configs so in case you need to get back its easy :)


xdr91:/etc/sysconfig/network # cat ifcfg-bond0 BOOTPROTO='static'
STARTMODE='onboot'
BONDING_MASTER='yes'
BONDING_MODULE_OPTS='mode=active-backup fail_over_mac=active miimon=100'
BONDING_SLAVE0='eth0'
BONDING_SLAVE1='eth1'


xdr91:/etc/sysconfig/network # cat ifcfg-vlan71 ETHERDEVICE='bond0'
IPADDR='162.101.1.129'
NETMASK='255.255.255.0'
NAME='VLAN access'
NETWORK='162.101.1.0'
BROADCAST='162.101.1.255'
STARTMODE='onboot'
VLAN='YES'


xdr91:/etc/sysconfig/network # cat ifcfg-eth0 BOOTPROTO='static'
IPADDR=''
BROADCAST=''
STARTMODE='auto'
LLADDR=''
NAME='OSA Express Network card (0.0.3000)'
ETHTOOL_OPTIONS=''
MTU=''
NETWORK=''
REMOTE_IPADDR=''
USERCONTROL='no'
SLAVE='yes'
LLADDR='02:00:00:00:91:EF'


xdr91:/etc/sysconfig/network # cat ifcfg-eth1 BOOTPROTO='static'
IPADDR=''
BROADCAST=''
STARTMODE='auto'
LLADDR=''
NAME='OSA Express Network card (0.0.4000)'
ETHTOOL_OPTIONS=''
MTU=''
NETWORK=''
REMOTE_IPADDR=''
USERCONTROL='no'
SLAVE='yes'
LLADDR='02:00:00:00:91:EE'

xdr91:/etc/sysconfig/network # cat routes default 162.101.1.1 - -


The bonding and 8021q modules seem to have loaded themselves - I couldn’t find 
anything specific to them in /etc/modprobe.d

Marcy

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Bill Head
Sent: Tuesday, March 07, 2017 2:07 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] DEDICATED OSA, LINUX VLAN tagging and bonding

And Alan is correct about VLAN tagging in LINUX (much easier to configure 
VSWITCH's, www), not to mention trying to do it with bonding two dedicated 
OSA's.  I opened up a ticket with SuSE for some guidance on that.   I may have 
to trudge on with just a VSWITCH connection until I get that figured out, at 
least I can get all the proxy guests built, get DNS changes in, etc.   GDPS is 
a different animal, miles to go before I sleep.



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Alan 
Altmark
Sent: Tuesday, March 07, 2017 4:26 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DEDICATED OSA, LINUX VLAN tagging and bonding

The VSWITCH depends on the controller virtual machines.  It and some related CP 
control blocks may be swapped out.

In a hyperswap, you can't do I/O to bring them back in.

Bill is correct regarding the requirements for the GDPS proxy servers.

Regards,
  Alan



The information transmitted is intended only for the person or entity to which 
it is addressed and may contain CONFIDENTIAL material.  If you receive this 
material/information in error, please contact the sender and delete or destroy 
the material/information.

The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material.  If you receive this 
material/information in error,
please contact the sender and delete or destroy the material/information.

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

2017-03-07 Thread Bill Head 
Dedicated network interfaces and channel bonding for Proxy Guests

Loss of communications between the Master Controlling system and a master proxy 
node during a HyperSwap could result in the failure of the z/VM system to 
complete the swap. In this case, GDPS would reset the z/VM system. Also, 
because I/O for z/VM service machines like TCP/IP and/or VSWITCH is quiesced 
during HyperSwap, proxy nodes should not use these services to provide network 
connectivity. This means that the network interfaces for proxy nodes need to be 
directly attached (dedicated) to the proxy guest machine instead of virtual 
devices connected through z/VM. We recommend you use two sets of directly 
attached (dedicated) OSA devices for each proxy node and set up channel bonding 
to provide network interface redundancy and avoid actions that can result in a 
complete loss of communication.



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Scott 
Rohling
Sent: Tuesday, March 07, 2017 3:34 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DEDICATED OSA, LINUX VLAN tagging and bonding

Are you sure you are interpreting the requirement correctly?   'Everything
gets quiesced during hyperswap' ...   how does this relate to z/VM and
VSWITCH?

Scott Rohling

On Tue, Mar 7, 2017 at 12:23 PM, Bill Head <bh...@humana.com> wrote:

> One requirement with building proxy guests for GDPS/xDR is that you do 
> not use virtual switches (since everything gets quiesed during a hyperswap).
>  So in order to setup DEDICATED OSA adapters I think I'm forced to use VLAN
> tagging in LINUX.  They also recommend using bonding.   Which goes back to
> my original question.   When I clone a guest I'm coming up on a VSWITCH
> connected via eth0, on VLAN 14.
>
> So I putty in at that point and try to configure  ifcfg-eth1 and
> ifcfg-eth2, then ifcfg-bond0, then ifcfg-vlan10.   The free IP addresses I
> have are on VLAN10.
>
> I found  something on the net about loading a module (8021q) so I did 
> that and rebooted, when it comes up I'm getting the following
>
> Mar  7 14:44:29 lxqmq001 kernel: 8021q: adding VLAN 0 to HW filter on 
> device eth0 Mar  7 14:44:29 lxqmq001 kernel: eth0: no IPv6 routers 
> present Mar  7 14:44:29 lxqmq001 kernel: bonding: Ethernet Channel 
> Bonding Driver:
> v3.7.1 (April 27, 2011)
> Mar  7 14:44:29 lxqmq001 kernel: bonding: bond0 is being created...
> Mar  7 14:44:29 lxqmq001 kernel: bonding: bond0: setting mode to 
> active-backup (1).
> Mar  7 14:44:29 lxqmq001 kernel: bonding: bond0: Setting fail_over_mac 
> to active (1).
> Mar  7 14:44:29 lxqmq001 kernel: bonding: bond0: Setting MII 
> monitoring interval to 100.
> Mar  7 14:44:29 lxqmq001 kernel: bonding: bond0: Adding slave eth1.
> Mar  7 14:44:29 lxqmq001 kernel: bonding: bond0: Adding slave eth2.
> Mar  7 14:44:29 lxqmq001 kernel: ADDRCONF(NETDEV_UP): bond0: link is 
> not ready Mar  7 14:44:29 lxqmq001 kernel: 8021q: adding VLAN 0 to HW 
> filter on device bond0 Mar  7 14:44:29 lxqmq001 kernel: bonding: bond0 
> is being deleted..
>
> I am unable to ping the 193.91.10.113 address from another server.
>
> I tried changing /etc/sysconfig/network/routes from this:
>
> default 205.145.91.254 - -
>
> to this:
>
> default 193.91.10.254 - -
>
> But I lose my connection on eth0 as well as the new vlan10 bonded address.
>
>
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of 
> Alan Altmark
> Sent: Tuesday, March 07, 2017 1:37 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: DEDICATED OSA, LINUX VLAN tagging and bonding
>
> On Tuesday, 03/07/2017 at 06:18 GMT, "Vitale, Joseph"
> <joseph.vit...@bnymellon.com> wrote:
> > Hello,
> >
> > Interested to know if  VLAN Tagging can be done via zLinux if  zVM
> currently adding VLAN Tag.  OSA
> > set up for Port access. Using Red Hat 7.  Please see below:
> >
> > CP SET VSWITCH VSWITCH2 GRANT R00022N1 VLAN 2419 2439 HCPSWS2847E 
> > PORTTYPE ACCESS is not allowed when the user is authorized 
> > HCPSWS2847E for more than one VLAN
>
> That's because you didn't include PORTTYPE TRUNK on the GRANT.  If you 
> do that, you can use vconfig on Linux to let it do the tagging 
> (eee!)
>
> Alternatively, you can use a PORTBASED VSWITCH and assign a VLAN to a 
> virtual NIC, so that Linux can remain VLAN unaware.  In this mode, you:
> a) Add the PORTBASED option to DEFINE  VSWITCH
> b) Use the SET VSWITCH PORTNUMBER command to assign guests to a port 
> number.
> c) Use the SET VSWITCH VLANID command to assign a port number to a 
> VLAN
> d) Remove the VSWITCH name from the NICDEF in the directory
> e) Add COMMAND COUPLE to the directory to connect a vdev to a port.
>

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

2017-03-07 Thread Bill Head 
One requirement with building proxy guests for GDPS/xDR is that you do not use 
virtual switches (since everything gets quiesed during a hyperswap).   So in 
order to setup DEDICATED OSA adapters I think I'm forced to use VLAN tagging in 
LINUX.  They also recommend using bonding.   Which goes back to my original 
question.   When I clone a guest I'm coming up on a VSWITCH connected via eth0, 
on VLAN 14.  

So I putty in at that point and try to configure  ifcfg-eth1 and ifcfg-eth2, 
then ifcfg-bond0, then ifcfg-vlan10.   The free IP addresses I have are on 
VLAN10.   

I found  something on the net about loading a module (8021q) so I did that and 
rebooted, when it comes up I'm getting the following

Mar  7 14:44:29 lxqmq001 kernel: 8021q: adding VLAN 0 to HW filter on device 
eth0
Mar  7 14:44:29 lxqmq001 kernel: eth0: no IPv6 routers present
Mar  7 14:44:29 lxqmq001 kernel: bonding: Ethernet Channel Bonding Driver: 
v3.7.1 (April 27, 2011)
Mar  7 14:44:29 lxqmq001 kernel: bonding: bond0 is being created...
Mar  7 14:44:29 lxqmq001 kernel: bonding: bond0: setting mode to active-backup 
(1).
Mar  7 14:44:29 lxqmq001 kernel: bonding: bond0: Setting fail_over_mac to 
active (1).
Mar  7 14:44:29 lxqmq001 kernel: bonding: bond0: Setting MII monitoring 
interval to 100.
Mar  7 14:44:29 lxqmq001 kernel: bonding: bond0: Adding slave eth1.
Mar  7 14:44:29 lxqmq001 kernel: bonding: bond0: Adding slave eth2.
Mar  7 14:44:29 lxqmq001 kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready
Mar  7 14:44:29 lxqmq001 kernel: 8021q: adding VLAN 0 to HW filter on device 
bond0
Mar  7 14:44:29 lxqmq001 kernel: bonding: bond0 is being deleted..

I am unable to ping the 193.91.10.113 address from another server.  

I tried changing /etc/sysconfig/network/routes from this:

default 205.145.91.254 - -

to this:

default 193.91.10.254 - -

But I lose my connection on eth0 as well as the new vlan10 bonded address.


-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Alan 
Altmark
Sent: Tuesday, March 07, 2017 1:37 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DEDICATED OSA, LINUX VLAN tagging and bonding

On Tuesday, 03/07/2017 at 06:18 GMT, "Vitale, Joseph" 
 wrote:
> Hello,
>
> Interested to know if  VLAN Tagging can be done via zLinux if  zVM
currently adding VLAN Tag.  OSA
> set up for Port access. Using Red Hat 7.  Please see below:
>
> CP SET VSWITCH VSWITCH2 GRANT R00022N1 VLAN 2419 2439 HCPSWS2847E 
> PORTTYPE ACCESS is not allowed when the user is authorized HCPSWS2847E 
> for more than one VLAN

That's because you didn't include PORTTYPE TRUNK on the GRANT.  If you do that, 
you can use vconfig on Linux to let it do the tagging (eee!)

Alternatively, you can use a PORTBASED VSWITCH and assign a VLAN to a virtual 
NIC, so that Linux can remain VLAN unaware.  In this mode, you:
a) Add the PORTBASED option to DEFINE  VSWITCH
b) Use the SET VSWITCH PORTNUMBER command to assign guests to a port number.
c) Use the SET VSWITCH VLANID command to assign a port number to a VLAN
d) Remove the VSWITCH name from the NICDEF in the directory
e) Add COMMAND COUPLE to the directory to connect a vdev to a port.

Folks at SHARE in San Jose this week can see my presentation on this Wednesday, 
along with a preview of the PORTBASED/USERBASED VSWITCH unification and 
simplification that will be coming soon to a z/VM system near you.

Alan Altmark

Senior Managing z/VM and Linux Consultant Lab Services System z Delivery 
Practice IBM Systems & Technology Group ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
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 more information on Linux on System z, visit http://wiki.linuxvm.org/

The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material.  If you receive this 
material/information in error,
please contact the sender and delete or destroy the material/information.

--
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/

DEDICATED OSA, LINUX VLAN tagging and bonding

2017-03-06 Thread Bill Head 
Howdy folks,

Up until now I've been using VSWITCHes for new SuSE guests (SLES 11 SP4).  I'm 
in the process of trying to build out a guest with two dedicated OSA adapters, 
set up VLAN tagging and bonding in LINUX.

The z/VM LPAR default vlan is 3
VSWITCH setup for the GOLD image is VLAN 14 (using a GRANT)
The new setup will be on VLAN 10

So when I bring up the new guest I can putty into it on VLAN 14, set up on eth0
I've added the DEDICATE triplets for the two OSA adapters.  And I can see those 
in YaST.
Eventually, once I get the bonded dedicated adapters set up on VLAN 10 I can 
remove the setup for vlan 14 on eth0.

I'm guessing this is all possible, to have eth0 using a vswitch, eth1 and eth2 
as dedicated, setting up VLAN tagging in LINUX and eventually setting up 
bonding between the two OSA's.  With eth0 using one VLAN and the bonded adapter 
using a different one, albeit temporarily.  Does that sound correct?

If so, I haven't found a way to do this using YaST, does all this have to be 
setup by editing files, or some other method?




The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material.  If you receive this 
material/information in error,
please contact the sender and delete or destroy the material/information.

--
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/

Re: YaST Missing network settings

2017-03-06 Thread Bill Head 
Good call Mark, good memory as well.I was headed down a (support initiated) 
rabbit hole, should have posted here first.  

Thank you Sir, much appreciated.  



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Vandale, 
Mark D
Sent: Monday, March 06, 2017 4:32 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: YaST Missing network settings

I believe the response I received was that Yast no longer supported (tolerated) 
the INTERFACEDEVICETYPE="qeth" record  in the ifcfg-eth0 file.  Delete that and 
your network settings will appear with Yast.

Thanks,
Mark Vandale


Sr. System Engineer Lead, MCS-MF z/VM & z/VSE and z/Linux
Office: 860-705-1657
Mobile  : 860-705-1657
Textmsg   : 8607051...@txt.att.net

CSC


-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Bill Head
Sent: Monday, March 6, 2017 4:26 PM
To: LINUX-390@VM.MARIST.EDU
Subject: YaST Missing network settings

Running SLES 11 SP4 on z/VM 6.3.   I'm noticing on some of the guests, yast, 
network devices, network settings, all of the settings are blank.  IP address 
is missing, when I select the QDIO adapter into Network Card Setup everything 
is blank.

>From the command line "ifconfig" shows all the correct settings.  I can reboot 
>and it comes up on the network just fine.

Anyone run into this, ideas?






The information transmitted is intended only for the person or entity to which 
it is addressed and may contain CONFIDENTIAL material.  If you receive this 
material/information in error, please contact the sender and delete or destroy 
the material/information.

--
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/

  CSC - This is a PRIVATE message - If you are not the intended recipient, 
please delete without copying and kindly advise us by e-mail of the mistake in 
delivery.  NOTE: Regardless of content, this e-mail shall not operate to bind 
the Company to any order or other contract unless pursuant to explicit written 
agreement or government initiative expressly permitting the use of e-mail for 
such purpose.

--
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/

The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material.  If you receive this 
material/information in error,
please contact the sender and delete or destroy the material/information.

--
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/

YaST Missing network settings

2017-03-06 Thread Bill Head 
Running SLES 11 SP4 on z/VM 6.3.   I'm noticing on some of the guests, yast, 
network devices, network settings, all of the settings are blank.  IP address 
is missing, when I select the QDIO adapter into Network Card Setup everything 
is blank.

>From the command line "ifconfig" shows all the correct settings.  I can reboot 
>and it comes up on the network just fine.

Anyone run into this, ideas?






The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material.  If you receive this 
material/information in error,
please contact the sender and delete or destroy the material/information.

--
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/