Re: SUSE12 Gold image on VM
On Tuesday, 06/16/2015 at 12:50 EDT, Mark Post mp...@suse.com wrote: On 6/15/2015 at 11:54 PM, Alan Altmark alan_altm...@us.ibm.com wrote: Neither z/VM nor Linux have to specify a portname (real or virtual). I recommend that you do NOT specify the portname. I don't understand why the distros still worry about the portname. We got rid of the requirement for z/VM and Linux on the z900 and z800 back in 2003. Just issue a msg that it's obsolete and ignore it. Even for Linux in an LPAR sharing an OSA with a z/OS system that is specifying (their equivalent of) a portname? Yes, even then. You can google OSA portname relief. I've posted this a few times, from October 2003: An OSA-Express microcode update for the IBM zSeries z800 and z900 machines became available today that makes the portname optional for the OSA-Express in QDIO mode. The update is Driver 3G - EC stream J11204, MCL032 (OSA level 3.33). This is a functional change that has already been made for the z990 and is now backfitted to earlier hardware levels. z/VM has released two APARs in support of these changes at the z/VM 4.3.0 level (these were already included in the z/VM 4.4.0 base): VM63308 - PORTNAME relief for z/VM Guest LAN PQ73878 - VM TCP/IP exploitation of PORTNAME relief If you are using real OSA-Express devices in QDIO mode and have the hardware update applied, the PORTNAME is no longer required when configuring OSD devices. For compatibility, OSA-Express will permit activation with or without a PORTNAME. For the z/VM Guest LAN environment with VM63308 applied, the portname specification is also optional. Prior to this change, if you were sharing an OSA-Express, you needed to configure matching names for all shared devices. If a mismatch occurred, activation would fail. Now you can omit the portname. The June 2003 Linux distribution also contains support for portname relief. The portname is still required for z/OS. 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: SUSE12 Gold image on VM
On 6/16/2015 at 09:55 AM, Alan Altmark alan_altm...@us.ibm.com wrote: On Tuesday, 06/16/2015 at 12:50 EDT, Mark Post mp...@suse.com wrote: On 6/15/2015 at 11:54 PM, Alan Altmark alan_altm...@us.ibm.com wrote: Neither z/VM nor Linux have to specify a portname (real or virtual). I recommend that you do NOT specify the portname. I don't understand why the distros still worry about the portname. We got rid of the requirement for z/VM and Linux on the z900 and z800 back in 2003. Just issue a msg that it's obsolete and ignore it. Even for Linux in an LPAR sharing an OSA with a z/OS system that is specifying (their equivalent of) a portname? Yes, even then. You can google OSA portname relief. OK then. I'm going to open up a bug with IBM to either remove that attribute from the driver, or make it read-only in sysfs. Preferably removing it altogether since it can only cause problems by being present. Looking at the results of my Google searches, I can see why I never made the complete connection. There were always statements made about z/OS requiring the parameter, and if you specify it in Linux it has to match. Looking at it now, I understand what was meant. Back then it meant (to me and apparently others) if you're sharing an OSA you need to specify the same portname as z/OS is using. 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: SUSE12 Gold image on VM
Or make the driver ignore anything specified and set it to null/blank ... ? Scott Rohling On Tue, Jun 16, 2015 at 7:53 AM, Mark Post mp...@suse.com wrote: On 6/16/2015 at 09:55 AM, Alan Altmark alan_altm...@us.ibm.com wrote: On Tuesday, 06/16/2015 at 12:50 EDT, Mark Post mp...@suse.com wrote: On 6/15/2015 at 11:54 PM, Alan Altmark alan_altm...@us.ibm.com wrote: Neither z/VM nor Linux have to specify a portname (real or virtual). I recommend that you do NOT specify the portname. I don't understand why the distros still worry about the portname. We got rid of the requirement for z/VM and Linux on the z900 and z800 back in 2003. Just issue a msg that it's obsolete and ignore it. Even for Linux in an LPAR sharing an OSA with a z/OS system that is specifying (their equivalent of) a portname? Yes, even then. You can google OSA portname relief. OK then. I'm going to open up a bug with IBM to either remove that attribute from the driver, or make it read-only in sysfs. Preferably removing it altogether since it can only cause problems by being present. Looking at the results of my Google searches, I can see why I never made the complete connection. There were always statements made about z/OS requiring the parameter, and if you specify it in Linux it has to match. Looking at it now, I understand what was meant. Back then it meant (to me and apparently others) if you're sharing an OSA you need to specify the same portname as z/OS is using. 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/ -- 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: SUSE12 Gold image on VM
On Tuesday, 06/16/2015 at 11:41 EDT, Duerbusch, Tom duerbus...@stlouis-mo.gov wrote: Back in the old days, SLES 7, the statement about portname was, it is not required, but if you do use it, you must use it every where (or something to that effect). So, as I never when back to the older running images to delete the portname, I still continue to specify the portname on all new images. So, the question is, can I have a mixture of images that specify a portname with images that do not specify a portname? Also, I have running images that goes back to SLES9 running. Does your answer go all the way back to SLES9? (I'm on a z/890almost everything I run is currently unsupported G) I can't speak to SLES requirements, but as far as the OSAs go, the portname is optional. IF it is specified, then it must match anyone else who also specified the portname, be they z/OS, Linux, VM, or VSE. So, yes, you can mix specify/unspecified on the port. All the 'specified' hosts must use the same value. 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: SUSE12 Gold image on VM
Thanks Alan I'll drop portname from my install documentation and, eventually, when we get a new processor, we can go to SLES 12 and beyond, and portnames will eventually die out (no zOS here...for bettor or worse). Tom Duerbusch THD Consulting On Tue, Jun 16, 2015 at 11:00 AM, Alan Altmark alan_altm...@us.ibm.com wrote: On Tuesday, 06/16/2015 at 11:41 EDT, Duerbusch, Tom duerbus...@stlouis-mo.gov wrote: Back in the old days, SLES 7, the statement about portname was, it is not required, but if you do use it, you must use it every where (or something to that effect). So, as I never when back to the older running images to delete the portname, I still continue to specify the portname on all new images. So, the question is, can I have a mixture of images that specify a portname with images that do not specify a portname? Also, I have running images that goes back to SLES9 running. Does your answer go all the way back to SLES9? (I'm on a z/890almost everything I run is currently unsupported G) I can't speak to SLES requirements, but as far as the OSAs go, the portname is optional. IF it is specified, then it must match anyone else who also specified the portname, be they z/OS, Linux, VM, or VSE. So, yes, you can mix specify/unspecified on the port. All the 'specified' hosts must use the same value. 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/
WWPN changes
Hello Group, We are using SUSE 11.2 z/Linux system with FCP channels. There are issues with one host that WWPN being dropped . So, now we want to use different WWPN number for this host and bring up again. For doing this, as per my knowledge we have to change entries in two places 1) z/VM text file, which is used while z/Linux comes up and have network related information etc. 2) Somewhere in z/Linux kernel. I am not sure the exact location Can anybody help me making this WWPN changes in z/Linux kernel . -- 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/
