Re: Problem adding a zfcp disk
On Wed, Jul 1, 2015 at 5:44 PM, Mark Post mp...@suse.com wrote: Did you select the Add function and get luns ? Yeah, nothing shows up. But I don't recall that has ever worked either on our setup. -- 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: Problem adding a zfcp disk
Did you happen to add the lun before it was available via zoning and masking? If so, you have to first remove it and add it again... On Jul 1, 2015 9:09 PM, Christer Solskogen christer.solsko...@gmail.com wrote: On Wed, Jul 1, 2015 at 5:44 PM, Mark Post mp...@suse.com wrote: Did you select the Add function and get luns ? Yeah, nothing shows up. But I don't recall that has ever worked either on our setup. -- 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/ -- 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: Migrate zLinux off zVM into standalone LPARs?
On Wed, 1 Jul 2015 02:18:45 + Morris, Kevin J. (RET-DAY) kevin.mor...@reedelsevier.com wrote: Given our static environment, can anyone provide any glaringly obvious caveats/downfalls to migrating from zVM to standalone zLinux LPARs that we might be missing? This is not that easy to answer. Things that I would consider are: - what disk type do you use (minidisks and EDEV might be interesting to migrate, new installations are of course always possible) - what bonding mode do you want to use on linux? With z/VM on z13 you will be able to use LACP shared over different z/VM systems. On Linux LPAR, if you want to use LACP, the ports must be reserved for the LPAR. - are your DR and backup procedures relying on z/VM? - Do you use OSA with multiple ports, and do you have requirements that a system should not see the other port of the same adapter? On z/VM, this can be done, on LPAR it will probably be difficult. I don't know the details about cost etc. but I personally would keep at least one z/VM system to be more flexible with upcoming demands. Berthold -- -- Berthold Gunreben Build Service Team http://www.suse.de/ Maxfeldstr. 5 SUSE Linux GmbHD-90409 Nuernberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton HRB 21284 (AG Nürnberg) -- 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: Where should we have been watching to find out about the leap second problem?
On Wednesday, 07/01/2015 at 09:57 EDT, Ron Foster ron.fos...@baldor.abb.com wrote: Everyone, Where should we have been watching so the we would not let the leap second problem sneak up on us? If you read the article I posted a couple of days ago (and posted about here and in IBMVM), it has the information on how you find out when leap seconds will be added. 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: Migrate zLinux off zVM into standalone LPARs?
On Wednesday, 07/01/2015 at 07:56 EDT, Morris, Kevin J. (RET-DAY) kevin.mor...@reedelsevier.com wrote: I know that we will lose the capability to overcommit/share memory between zLinux systems, but the application running in this environment is very response-time critical/sensitive so we actually dedicated memory resources to our production zLinux systems anyways. Additionally, after retiring the ~12 servers, we now have a memory excess on all of our zVM LPARs. VSWITCH is nice with its automatic failover, etc; however, we have tested the linux bonding driver and feel it is an adequate replacement. We are not a zVM SSI user. The VSWITCH also provides the security controls to keep a guest from VLAN hopping. (Assume Linux has been hacked.) As long as you have compensating controls, removing the VSWITCH shouldn't pose any obstacle. Given our static environment, can anyone provide any glaringly obvious caveats/downfalls to migrating from zVM to standalone zLinux LPARs that we might be missing? As long as you remove all z/VM dependencies from the guests (mindisks, VDISKS, DIAG250 driver, EDEVs, DR, etc.) before you migrate them to their own LPARs, then you should be fine. For example, minidisks allowed the virtual machines to share an I/O configuration. Your IOCDS will need to be changed to create limited I/O configurations for each LPAR. Speaking of IOCDS, how do you plan to manage it? Standalone IOCP? Or is z/OS on these boxes, too? 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: Migrate zLinux off zVM into standalone LPARs?
Hello, Kevin. That's an interesting direction for your company to take. Can you elaborate a bit on what drove the decision to not exploit virtualization? As far as the move from z/VM to bare metal LPARs, I don't see any potential problems, as long as the LPARs are defined with enough physical resources to support the zLinux workloads. Good luck. DJ On 06/30/2015 09:18 PM, Morris, Kevin J. (RET-DAY) wrote: We currently have 22 zLinux guests (all running RHEL 6.4) on 7 zVM (v6.2) LPARs spread across 6 CECs (29 IFLs in total) all to support numerous environments for a single application. Here is our current zVM LPAR / zLinux guest configuration: 1. Sandbox zVM LPAR - 3 zLinux systems only for Systems Programming use/testing. 2. Test/Dev zVM LPAR - 2 zLinux systems for application development and testing. 3. Prod#1 zVM LPAR - 5 zLinux systems for cert/prod 4. Prod#2 zVM LPAR - 4 zLinux systems for cert/prod 5. Prod#3 zVM LPAR - 1 zLinux system for prod 6. Prod#4 zVM LPAR - 1 zLinux system for prod 7. DR zVM LPAR - 6 zLinux systems for prod DR. At one point we had an additional ~12 zLinux systems throughout these zVM LPARs, but they have since been retired. As a sizeable software cost-savings effort (zVM, RACF, Perfkit, Operations Manager), we are planning to migrate these 22 zLinux systems into standalone LPARs and eliminate zVM altogether. I know that we will lose the capability to overcommit/share memory between zLinux systems, but the application running in this environment is very response-time critical/sensitive so we actually dedicated memory resources to our production zLinux systems anyways. Additionally, after retiring the ~12 servers, we now have a memory excess on all of our zVM LPARs. VSWITCH is nice with its automatic failover, etc; however, we have tested the linux bonding driver and feel it is an adequate replacement. We are not a zVM SSI user. Also, let me state that the business has no future plans to grow/expand the zVM/zLinux environment (including as a virtualization platform for traditional x86 workloads). Given our static environment, can anyone provide any glaringly obvious caveats/downfalls to migrating from zVM to standalone zLinux LPARs that we might be missing? Thanks! Kevin Morris Reed Elsevier - Technology Services zOS Systems Engineering -- 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/ -- Dave Jones Houston, TX 281.578.7544 -- 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/
Where should we have been watching to find out about the leap second problem?
Everyone, Where should we have been watching so the we would not let the leap second problem sneak up on us? Ron Foster Baldor Electric Company 5711 R S Boreham Jr Street Fort Smith, AR 72901 Phone:479-648-5865 Fax:479-646-5440 Email: ron.fos...@baldor.abb.commailto:ron.fos...@baldor.abb.com IM Address:ron.fos...@baldor.abb.com www.baldor.comhttp://www.baldor.com/ -- 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: Migrate zLinux off zVM into standalone LPARs?
Just one tongue in cheek comment. Given our static environment... Has anyone ever known a static environment that has remained static? Mike Wawiorko Please consider the environment before printing this e-mail -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Morris, Kevin J. (RET-DAY) Sent: 01 July 2015 03:19 To: LINUX-390@VM.MARIST.EDU Subject: Migrate zLinux off zVM into standalone LPARs? We currently have 22 zLinux guests (all running RHEL 6.4) on 7 zVM (v6.2) LPARs spread across 6 CECs (29 IFLs in total) all to support numerous environments for a single application. Here is our current zVM LPAR / zLinux guest configuration: 1. Sandbox zVM LPAR - 3 zLinux systems only for Systems Programming use/testing. 2. Test/Dev zVM LPAR - 2 zLinux systems for application development and testing. 3. Prod#1 zVM LPAR - 5 zLinux systems for cert/prod 4. Prod#2 zVM LPAR - 4 zLinux systems for cert/prod 5. Prod#3 zVM LPAR - 1 zLinux system for prod 6. Prod#4 zVM LPAR - 1 zLinux system for prod 7. DR zVM LPAR - 6 zLinux systems for prod DR. At one point we had an additional ~12 zLinux systems throughout these zVM LPARs, but they have since been retired. As a sizeable software cost-savings effort (zVM, RACF, Perfkit, Operations Manager), we are planning to migrate these 22 zLinux systems into standalone LPARs and eliminate zVM altogether. I know that we will lose the capability to overcommit/share memory between zLinux systems, but the application running in this environment is very response-time critical/sensitive so we actually dedicated memory resources to our production zLinux systems anyways. Additionally, after retiring the ~12 servers, we now have a memory excess on all of our zVM LPARs. VSWITCH is nice with its automatic failover, etc; however, we have tested the linux bonding driver and feel it is an adequate replacement. We are not a zVM SSI user. Also, let me state that the business has no future plans to grow/expand the zVM/zLinux environment (including as a virtualization platform for traditional x86 workloads). Given our static environment, can anyone provide any glaringly obvious caveats/downfalls to migrating from zVM to standalone zLinux LPARs that we might be missing? Thanks! Kevin Morris Reed Elsevier - Technology Services zOS Systems Engineering -- 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/ This e-mail and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this e-mail in error, please notify the sender immediately, delete it from your system and do not copy, disclose or otherwise act upon any part of this e-mail or its attachments. Internet communications are not guaranteed to be secure or virus-free. The Barclays Group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any Internet communications by any third party, or from the transmission of any viruses. Replies to this e-mail may be monitored by the Barclays Group for operational or business reasons. Any opinion or other information in this e-mail or its attachments that does not relate to the business of the Barclays Group is personal to the sender and is not given or endorsed by the Barclays Group. Barclays Bank PLC. Registered in England and Wales (registered no. 1026167). Registered Office: 1 Churchill Place, London, E14 5HP, United Kingdom. Barclays Bank PLC is authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority (Financial Services Register No. 122702).
Migrate zLinux off zVM into standalone LPARs?
We currently have 22 zLinux guests (all running RHEL 6.4) on 7 zVM (v6.2) LPARs spread across 6 CECs (29 IFLs in total) all to support numerous environments for a single application. Here is our current zVM LPAR / zLinux guest configuration: 1. Sandbox zVM LPAR - 3 zLinux systems only for Systems Programming use/testing. 2. Test/Dev zVM LPAR - 2 zLinux systems for application development and testing. 3. Prod#1 zVM LPAR - 5 zLinux systems for cert/prod 4. Prod#2 zVM LPAR - 4 zLinux systems for cert/prod 5. Prod#3 zVM LPAR - 1 zLinux system for prod 6. Prod#4 zVM LPAR - 1 zLinux system for prod 7. DR zVM LPAR - 6 zLinux systems for prod DR. At one point we had an additional ~12 zLinux systems throughout these zVM LPARs, but they have since been retired. As a sizeable software cost-savings effort (zVM, RACF, Perfkit, Operations Manager), we are planning to migrate these 22 zLinux systems into standalone LPARs and eliminate zVM altogether. I know that we will lose the capability to overcommit/share memory between zLinux systems, but the application running in this environment is very response-time critical/sensitive so we actually dedicated memory resources to our production zLinux systems anyways. Additionally, after retiring the ~12 servers, we now have a memory excess on all of our zVM LPARs. VSWITCH is nice with its automatic failover, etc; however, we have tested the linux bonding driver and feel it is an adequate replacement. We are not a zVM SSI user. Also, let me state that the business has no future plans to grow/expand the zVM/zLinux environment (including as a virtualization platform for traditional x86 workloads). Given our static environment, can anyone provide any glaringly obvious caveats/downfalls to migrating from zVM to standalone zLinux LPARs that we might be missing? Thanks! Kevin Morris Reed Elsevier - Technology Services zOS Systems Engineering -- 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/
Problem adding a zfcp disk
Hi! I have trouble adding a lun to a SuSE machine. I've tried adding the disk with channel, wwpn and lun in YaST. No error, but the lun does not show in the list Yast - Hardware - Zfcp. But the lun does show here: /sys/bus/ccw/drivers/zfcp/0.0.8030/0x5974082a4120/0x002f But I don't get a linux device! There are many other lun's activated there (same channel and wwpn) - which works perfectly. But /dev/sdm (which this lun should be) does not show. Any pointers? -- chs -- 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: Problem adding a zfcp disk
On 7/1/2015 at 11:24 AM, Christer Solskogen christer.solsko...@gmail.com wrote: Hi! I have trouble adding a lun to a SuSE machine. I've tried adding the disk with channel, wwpn and lun in YaST. No error, but the lun does not show in the list Yast - Hardware - Zfcp. Did you select the Add function and get luns ? 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/
Re: Migrate zLinux off zVM into standalone LPARs?
As usually LPARs have a lot of devices connected to them you might want to start using cio_ignore if you are not already using it. Not using cio_ignore can really slow down linux startup when the LPAR has a lot of devices connected to it. On Jul 1, 2015 5:32 PM, Alan Altmark alan_altm...@us.ibm.com wrote: On Wednesday, 07/01/2015 at 07:56 EDT, Morris, Kevin J. (RET-DAY) kevin.mor...@reedelsevier.com wrote: I know that we will lose the capability to overcommit/share memory between zLinux systems, but the application running in this environment is very response-time critical/sensitive so we actually dedicated memory resources to our production zLinux systems anyways. Additionally, after retiring the ~12 servers, we now have a memory excess on all of our zVM LPARs. VSWITCH is nice with its automatic failover, etc; however, we have tested the linux bonding driver and feel it is an adequate replacement. We are not a zVM SSI user. The VSWITCH also provides the security controls to keep a guest from VLAN hopping. (Assume Linux has been hacked.) As long as you have compensating controls, removing the VSWITCH shouldn't pose any obstacle. Given our static environment, can anyone provide any glaringly obvious caveats/downfalls to migrating from zVM to standalone zLinux LPARs that we might be missing? As long as you remove all z/VM dependencies from the guests (mindisks, VDISKS, DIAG250 driver, EDEVs, DR, etc.) before you migrate them to their own LPARs, then you should be fine. For example, minidisks allowed the virtual machines to share an I/O configuration. Your IOCDS will need to be changed to create limited I/O configurations for each LPAR. Speaking of IOCDS, how do you plan to manage it? Standalone IOCP? Or is z/OS on these boxes, too? 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/ -- 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: Migrate zLinux off zVM into standalone LPARs?
Since you won't have VM to limit which and how many devices each of the Linuxes sees, you may want to consider isolating them from each other via the IOCP. Also keep in mind that all your addresses will probably change as you move from virtual addresses to real addresses. And what the Linuxes have created for volsers is probably not unique, and if your DASD is shared with an MVS image, those duplicates will show up there... Lee Stewart ● VM System Support ● Visa ● Phone: 6(750)4601 - +1-303-389-4601 ● lstew...@visa.com -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Morris, Kevin J. (RET-DAY) Sent: Tuesday, June 30, 2015 8:19 PM To: LINUX-390@VM.MARIST.EDU Subject: Migrate zLinux off zVM into standalone LPARs? We currently have 22 zLinux guests (all running RHEL 6.4) on 7 zVM (v6.2) LPARs spread across 6 CECs (29 IFLs in total) all to support numerous environments for a single application. Here is our current zVM LPAR / zLinux guest configuration: 1. Sandbox zVM LPAR - 3 zLinux systems only for Systems Programming use/testing. 2. Test/Dev zVM LPAR - 2 zLinux systems for application development and testing. 3. Prod#1 zVM LPAR - 5 zLinux systems for cert/prod 4. Prod#2 zVM LPAR - 4 zLinux systems for cert/prod 5. Prod#3 zVM LPAR - 1 zLinux system for prod 6. Prod#4 zVM LPAR - 1 zLinux system for prod 7. DR zVM LPAR - 6 zLinux systems for prod DR. At one point we had an additional ~12 zLinux systems throughout these zVM LPARs, but they have since been retired. As a sizeable software cost-savings effort (zVM, RACF, Perfkit, Operations Manager), we are planning to migrate these 22 zLinux systems into standalone LPARs and eliminate zVM altogether. I know that we will lose the capability to overcommit/share memory between zLinux systems, but the application running in this environment is very response-time critical/sensitive so we actually dedicated memory resources to our production zLinux systems anyways. Additionally, after retiring the ~12 servers, we now have a memory excess on all of our zVM LPARs. VSWITCH is nice with its automatic failover, etc; however, we have tested the linux bonding driver and feel it is an adequate replacement. We are not a zVM SSI user. Also, let me state that the business has no future plans to grow/expand the zVM/zLinux environment (including as a virtualization platform for traditional x86 workloads). Given our static environment, can anyone provide any glaringly obvious caveats/downfalls to migrating from zVM to standalone zLinux LPARs that we might be missing? Thanks! Kevin Morris Reed Elsevier - Technology Services zOS Systems Engineering -- 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/ -- 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: Problem adding a zfcp disk
On 7/1/2015 at 02:07 PM, Christer Solskogen christer.solsko...@gmail.com wrote: On Wed, Jul 1, 2015 at 5:44 PM, Mark Post mp...@suse.com wrote: Did you select the Add function and get luns ? Yeah, nothing shows up. But I don't recall that has ever worked either on our setup. Then I would suggest trying this: zfcp_disk_configure 0.0.8030 0x5974082a4120 0x002f 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/
Re: Problem adding a zfcp disk
On Wed, Jul 1, 2015 at 10:41 PM, Mark Post mp...@suse.com wrote: Then I would suggest trying this: zfcp_disk_configure 0.0.8030 0x5974082a4120 0x002f Problem found. The LUN was activate on another server. But thanks anyways :-) -- chs -- 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/
VM Workshop tools tape collection complete (1985-2015)
I finally got a few minutes to complete the VM Workshop tools tapes collection. All the still-readable VM Workshop tapes from 1985 to current are now online (note the gap from 1998 to 2012 - no VM Workshops were held from 1998 to 2011, and the 2011 VM Workshop at Ohio State did not produce a tape). http://www.vmworkshop.org/tools Browse and enjoy. == db -- 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: VM Workshop tools tape collection complete (1985-2015)
image/gif: EXCLUDED
Re: Migrate zLinux off zVM into standalone LPARs?
Has anyone ever known a static environment that has remained static? We have had zVM for 10 years, and in the last 8 years we have only retired zLinux systems. Also, our largest zVM LPAR only has 6 zLinux guests with two zVM LPARs only having 1 zLinux guest -- almost no point in running zVM in those cases. - what disk type do you use (minidisks and EDEV might be interesting to migrate, new installations are of course always possible) Under zVM we use full-volume ECKD minidisks for zLinux storage. We will simply use full-volume ECKD for the LPARs as well. - what bonding mode do you want to use on linux? With z/VM on z13 you will be able to use LACP shared over different z/VM systems. On Linux LPAR, if you want to use LACP, the ports must be reserved for the LPAR. We are planning to use bonding mode 0 (active-backup) with primary reselect. Can you recommend a preferred mode for load balancing and failover? - are your DR and backup procedures relying on z/VM? Nope. We use Netbackup and a nightly rsync for DR (both at the Linux level). - Do you use OSA with multiple ports, and do you have requirements that a system should not see the other port of the same adapter? On z/VM, this can be done, on LPAR it will probably be difficult. Yes, we use OSA w/multiple ports but we do not have the visibility requirement. That's an interesting direction for your company to take. Can you elaborate a bit on what drove the decision to not exploit virtualization? Yes, we realize that this direction is generally against the normal flow. However, the overall business direction is to migrate off of the mainframe entirely, and we are under constant pressure to reduce costs in the meantime. Numerous years ago when the architects were looking at virtualization platforms for x86 workloads, the Z solution had a higher TCO, and several of our staple products did not have a s390 binary and refused to work with us or IBM to release one. As long as you remove all z/VM dependencies from the guests (mindisks, VDISKS, DIAG250 driver, EDEVs, DR, etc.) before you migrate them to their own LPARs, then you should be fine. For example, minidisks allowed the virtual machines to share an I/O configuration. Your IOCDS will need to be changed to create limited I/O configurations for each LPAR. We set aside a pool of DASD/UCBs for the zVM environment and only gen that range to the zVM LPARs. We will give that same pool to the zLinux LPARs and carefully manage access via cio_ignore and /etc/dasd.conf. Speaking of IOCDS, how do you plan to manage it? Standalone IOCP? Or is z/OS on these boxes, too? Yes, we are primarily a zOS shop (so HCD). Actually, the application that we run on zLinux is CPU-intense assembly code that we cross-assemble with Tachyon390 to run in zLinux. We greatly reduced our zOS software costs by moving this CPU-expensive workload onto IFLs. As usually LPARs have a lot of devices connected to them you might want to start using cio_ignore if you are not already using it. Not using cio_ignore can really slow down linux startup when the LPAR has a lot of devices connected to it. We have cio_ignore=all specified in zipl.conf. We add all system-specific non-root DASD devices and HyperPAV aliases to /etc/dasd.conf We have already migrated our Sandbox, DR, and test zLinux systems into standalone LPARs. So far we haven't seen any technical limitations or really any negatives to this setup. Actually, our list of pros is much longer than the cons. I appreciate everyone's responses so far. -- 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: Where should we have been watching to find out about the leap second problem?
On 7/1/2015 at 09:56 AM, Ron Foster ron.fos...@baldor.abb.com wrote: Everyone, Where should we have been watching so the we would not let the leap second problem sneak up on us? One place would be the patch notifications we send out via email. Go to https://www.novell.com/email/notification/ctrl and sign up. Note that the window that comes up is scrollable. I wouldn't recommend the - All SUSE Products - selection unless you really want that. SUSE Linux Enterprise Server is further down. 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/
