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:[email protected]] On Behalf Of Scott Rohling Sent: Tuesday, March 07, 2017 3:34 PM To: [email protected] 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 <[email protected]> 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:[email protected]] On Behalf Of > Alan Altmark > Sent: Tuesday, March 07, 2017 1:37 PM > To: [email protected] > Subject: Re: DEDICATED OSA, LINUX VLAN tagging and bonding > > On Tuesday, 03/07/2017 at 06:18 GMT, "Vitale, Joseph" > <[email protected]> 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 > (eeewwww!) > > 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 > [email protected] > IBM Endicott > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For 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 [email protected] 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/ > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For 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.
