date:20170307

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

2017-03-07 Thread Marcy Cortes

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

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

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 Alan Altmark

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


   Scott Rohling --- Re: [LINUX-390] DEDICATED OSA, LINUX VLAN tagging and 
bonding --- 
From:"Scott Rohling" 
To:LINUX-390@VM.MARIST.EDUDate:Tue, Mar 7, 2017 12:34 
PMSubject:Re: [LINUX-390] DEDICATED OSA, LINUX VLAN tagging and bonding
  
Are you sure you are interpreting the requirement correctly?   
'Everythinggets quiesced during hyperswap' ...   how does this relate to z/VM 
andVSWITCH?Scott RohlingOn Tue, Mar 7, 2017 at 12:23 PM, Bill Head 
 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"> 
 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

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

2017-03-07 Thread Vitale, Joseph

Hello,

I later added  PORTTYPE TRUNK   , unaware of   "vconfig".  Thanks very much.

Thanks
 Joe

Technology Services Group
Mainframe Operating Systems

Pershing Plaza
95 Christopher Columbus Drive
Floor 14   
Jersey City,  N.J.  07302
Work  201-395-1509
Cell917-903-0102

-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 contained in this e-mail, and any attachment, is confidential 
and is intended solely for the use of the intended recipient. Access, copying 
or re-use of the e-mail or any attachment, or any information contained 
therein, by any other person is not authorized. If you are not the intended 
recipient please return the e-mail to the sender and delete it from your 
computer. Although we attempt to sweep e-mail and attachments for viruses, we 
do not guarantee that either are virus-free and accept no liability for any 
damage sustained as a result of viruses. 

Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures 
relating to European legal entities.

--
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: 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  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"
>  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

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

2017-03-07 Thread Scott Rohling

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

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/

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

2017-03-07 Thread Alan Altmark

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/

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

2017-03-07 Thread Vitale, Joseph

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


HCP2847E
PORTTYPE ACCESS is not allowed when the user is authorized for more than one 
VLAN.
Explanation:
If the user is given PORTTYPE ACCESS or if the PORTTYPE defaults to ACCESS, the 
user can
be authorized for only one VLAN ID.
System action:
The SET VSWITCH GRANT command fails.
User response:
Issue the SET VSWITCH GRANT command to use PORTTYPE TRUNK with a list of
VLAN IDs, or issue SET VSWITCH GRANT with PORTTYPE ACCESS and a single VLAN ID. 



Thanks
 Joe

Technology Services Group
Mainframe Operating Systems

Pershing Plaza
95 Christopher Columbus Drive
Floor 14   
Jersey City,  N.J.  07302
Work  201-395-1509
Cell917-903-0102


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

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/

The information contained in this e-mail, and any attachment, is confidential 
and is intended solely for the use of the intended recipient. Access, copying 
or re-use of the e-mail or any attachment, or any information contained 
therein, by any other person is not authorized. If you are not the intended 
recipient please return the e-mail to the sender and delete it from your 
computer. Although we attempt to sweep e-mail and attachments for viruses, we 
do not guarantee that either are virus-free and accept no liability for any 
damage sustained as a result of viruses. 

Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures 
relating to European legal entities.

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

Hillgang - 22 March

2017-03-07 Thread Neale Ferguson

Well things came together faster than I thought so we have the full agenda
and registration details available at
http://www.vm.ibm.com/events/HILL0317.PDF

Neale

--
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: Unable to get ipv4 dhcp addr (new OSA)

2017-03-07 Thread IronSphere by SecuriTeam Software

I revised the ip status and decided to reinstall the image directly under
zPDT. I now have access using the virtual tap device on 10.1.1.x network. I
also has a static (can be dynamic) configured NIC on the driving system.
The manuals are quit clear on how to configure z/os TCPIP to use the second
OSA. THe real NIC has an IP address, but it is known to the Centos os and
it doesn;t forward it any any way to the SESE image. What I need is a clear
explanation how to define a NAT (or any other routing) from the driving
system (Centos 7) to the SLES 12 image running under zPDT. the real OSA
card acts like a router, so there is no problem, but I can't understand how
it work with zPDT.

Can someone shed some light on this?

ITschak

On Wed, Mar 1, 2017 at 10:45 PM, Mark Post  wrote:

> >>> On 2/28/2017 at 02:04 AM, Itschak Mugzach  wrote:
> > Hi Mark. Tcpdump taken on the virtual machine guest. Dhcp has no evidence
> > in log. Firewalla aee down both sides aa well aa iptables on centoa side.
>
> If you're not able to see any traffic on the host that is coming from the
> guest, then it sounds like something is wrong with the bridging of the
> network between the host and the guest.  That sounds more like a zPDT
> setup/configuration problem than anything.
>
> The last thing I would try is to manually configure the IP address and
> default route that the DHCP server would normally hand out, and see if you
> can ping the default gateway from the guest.  If that doesn't work, then
> the problem isn't in the Linux guest.
>
>
> 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) **|*

--
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: DEDICATED OSA, LINUX VLAN tagging and bonding

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

Re: DEDICATED OSA, LINUX VLAN tagging and bonding

Hillgang - 22 March

Re: Unable to get ipv4 dhcp addr (new OSA)

11 matches

Site Navigation

Mail list logo

Footer information