Re: How to tell how many linux running on z/VM?
Since all my Linux guests IPL 02xx, I run pipe lnxusers | count lines | cons where LNXUSERS REXX looks like: /* LNXUSERS REXX Return list of logged on Linux users. */ 'CALLPIPE(name LNXUSERS endchar ?)|', 'CP Q N |', 'SPLIT , |', 'STRIP |', 'CHOP 8 |', 'SORT 1.8 |', 'SPECS /IND USER/ 1 1.8 NW |', 'CP |', 'F: FIND USERID=|', 'J: JUXTAPOSE |', 'SPECS 8.8 1 |', '*:', '?', 'F: |', 'FIND IPLSYS=DEV_02|', 'J:' exit 0 Mark Wheeler http://www.linkedin.com/in/marklwheeler _ Get your vacation photos on your phone! http://windowsliveformobile.com/en-us/photos/default.aspx?&OCID=0809TL-HM -- 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
Re: Dynamically Changing Linux Guest Network
Folks, Don't forget to also change the host name in /etc/postfix/main.cf David Kelly Marcy Cortes To Sent by: Linux on LINUX-390@VM.MARIST.EDU 390 Port cc Subject Re: Dynamicallhy Changing Linux Guest Network 08/14/2009 11:48 AM Please respond to Linux on 390 Port DHCP is not an option here. In the event of a real disaster, we use the production IP s and hostnames, full replication, all is easy peasy. But for a disaster test, we can't - have to change IPs and hostnames. This can be problematic, but after a while, you make a list and figure it out - not everything uses DNS (think firewall, perhaps load balancers, some stupid sw :). In SuSE 9 and 10, the files that are going to perhaps need attention are /etc/HOSTNAME /etc/hosts /etc/sysconfig/hwcfg-qeth-bus* /etc/sysconfig/network/ifcfg-qeth-bus-ccw-x.x. /etc/sysconfig/network/routes /etc/resolv.conf We also regenerate server SSH keys on a change of the HOSTNAME. Marcy "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Lionel Dyck Sent: Friday, August 14, 2009 8:01 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Dynamicallhy Changing Linux Guest Network Does anyone have a z/vm and/or linux script that they could share that can be used to dynamically change the linux servers network when the server is brought up at a dr site and/or when the network addressing is changed? I've tried playing with it without success - keep missing a piece here or there. thx Lionel B. Dyck, z/Linux Virtualization Specialist IBM Global Services - Kaiser Permanente Team Linux on System z Service Delivery Team 925-926-5332 (8-473-5332) | E-Mail: ld...@us.ibm.com AIM: lbdyck | Yahoo IM: lbdyck I never guess. It is a capital mistake to theorize before one has data. Insensibly one begins to twist facts to suit theories, instead of theories to suit facts. - Sir Arthur Conan Doyle -- 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 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 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
An informal survey.
- What applications / types of applications (databases, web servers, etc...) are you running? - Do you typically have specialized guests running one "primary" application each, or sets/stacks of applications running on the same guest? - Do the majority of your Linux guests house long-term persistent data, or is there some significant number of guests which primarily operate on data from an external source (like a database on a different guest/machine)? - Are your Linux guests individually customized for specific uses, or do you have a handful of configurations that you apply to most or all of your Linux-on-z/VM systems? - What tasks consume the majority of your system-administration time and effort? Thank you. ~ Chris -- 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
Re: vmpoff=LOGOFF not working in RHEL 5.3?
Oliver and Brad, Yes, "vmhalt" works much better than "vmphalt". Thanks. Ken, You are right - not having a 3270 session going causes SIGNAL SHUTDOWN to behave as I expected: ==> signal shutdown rh5rwmnt ... HCPSIG2113I User RH5RWMNT has reported successful termination ==> q rh5rwmnt HCPCQU045E RH5RWMNT not logged on I was keeping a 3270 session running to observe the system logging off. But the act of observing changed the outcome - Hmmm - the Heisenberg uncertainty principle at work? ... So now when I set up zipl.conf, I will specify both "vmpoff=LOGOFF" and "vmhalt=LOGOFF". Thanks all. "Mike MacIsaac"(845) 433-7061 -- 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
Re: Dynamicallhy Changing Linux Guest Network
Yeah, you are right and we know. The effort and cost to duplicate the active directory environment likely won't fly for just Linux on z servers testing. And the AD servers are not in the mainframe datacenter so unlikely that they would suffer the same disaster. In our case though, the real event doesn't have any configuration changes necessary other than the network routers. The best "test" though is just to go run in the other place for a week or whatever. We'll be doing that too. Marcy "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Richard Troth Sent: Friday, August 14, 2009 9:52 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Dynamicallhy Changing Linux Guest Network Forgive me ... you realize, of course, that you're not getting a true "exercise". Touching prod stuff means there's yet another point that's not getting exercised. (Not to mention the exposure ... "test" things with access to your prod network.) I have fought the same fight where I work (about changing IP addresses). Others have already acquiesced. (Gotta pick yer battles, I guess, but this hostname and IP addr shuffle drives me nuts.) I'm probably telling you something you already know. -- R; <>< On Fri, Aug 14, 2009 at 12:18, Marcy Cortes wrote: > It's because of the software we use to interface to Active Directory for > single signon. It doesn't want 2 systems coming in with the same hostname. > If we do that, we can't login to the prod systems :( > > > > Marcy > "This message may contain confidential and/or privileged information. If you > are not the addressee or authorized to receive this for the addressee, you > must not use, copy, disclose, or take any action based on this message or any > information herein. If you have received this message in error, please advise > the sender immediately by reply e-mail and delete this message. Thank you for > your cooperation." > > > -Original Message- > From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Michael > MacIsaac > Sent: Friday, August 14, 2009 9:02 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Dynamicallhy Changing Linux Guest Network > > Marcy, > >> have to change IPs and hostnames > I can understand that you have to change IP addresses. But do you have to > change hostnames? Maybe have a DNS system that maps the same hosts to new > i...@s? ... just a thought ... > > "Mike MacIsaac" (845) 433-7061 > > -- > 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 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 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 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
Re: Dynamicallhy Changing Linux Guest Network
Forgive me ... you realize, of course, that you're not getting a true "exercise". Touching prod stuff means there's yet another point that's not getting exercised. (Not to mention the exposure ... "test" things with access to your prod network.) I have fought the same fight where I work (about changing IP addresses). Others have already acquiesced. (Gotta pick yer battles, I guess, but this hostname and IP addr shuffle drives me nuts.) I'm probably telling you something you already know. -- R; <>< On Fri, Aug 14, 2009 at 12:18, Marcy Cortes wrote: > It's because of the software we use to interface to Active Directory for > single signon. It doesn't want 2 systems coming in with the same hostname. > If we do that, we can't login to the prod systems :( > > > > Marcy > "This message may contain confidential and/or privileged information. If you > are not the addressee or authorized to receive this for the addressee, you > must not use, copy, disclose, or take any action based on this message or any > information herein. If you have received this message in error, please advise > the sender immediately by reply e-mail and delete this message. Thank you for > your cooperation." > > > -Original Message- > From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Michael > MacIsaac > Sent: Friday, August 14, 2009 9:02 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Dynamicallhy Changing Linux Guest Network > > Marcy, > >> have to change IPs and hostnames > I can understand that you have to change IP addresses. But do you have to > change hostnames? Maybe have a DNS system that maps the same hosts to new > i...@s? ... just a thought ... > > "Mike MacIsaac" (845) 433-7061 > > -- > 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 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 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
Re: vmpoff=LOGOFF not working in RHEL 5.3?
The message below indicates the guest is still logged onto a terminal. I was told early on that the guest will ONLY logoff if it's running disconnected, no matter what parms you pass. It (signal shut) works fine for us with all our disconnected machines, but if I shut down from the 3270 console, I always get the disabled wait, like you show below. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Brad Hinson Sent: Friday, August 14, 2009 12:34 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] vmpoff=LOGOFF not working in RHEL 5.3? Michael MacIsaac wrote: > Clovis, > >> Please, try with vmphalt too. >> >> root=LABEL=/ vmpoff=LOGOFF vmphalt=LOGOFF BOOT_IMAGE=0 > > Thanks for the suggestion. I tried that and there was no difference: > > # cat /proc/cmdline > cat /proc/cmdline > root=LABEL=/ vmpoff=LOGOFF vmphalt=LOGOFF BOOT_IMAGE=0 > # halt > halt > That should be vmhalt, not vmphalt. The reason vmpoff didn't work the first time is that '/sbin/halt' halts the system without doing a true poweroff instruction (thus leaving the system halted but on), whereas '/sbin/poweroff' does a halt+poweroff. 'shutdown -h now' does a poweroff also, which is why that worked the 2nd time. If you have vmpoff=LOGOFF vmhalt=LOGOFF, you have all your bases covered. Any time the system halts, it'll logoff, regardless of whether you run the command to perform an actual poweroff. -Brad > Broadcast message from root (console) (Fri Aug 14 12:01:52 2009): > > The system is going down for system halt NOW! > ... > 00: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP > stop from > CPU 01. > 01: HCPGSP2630I The virtual machine is placed in CP mode due to a SIGP > stop and > store status from CPU 01. > > The user ID remains logged on. Then I reboot and try a "shutdown -h now" > and the behavior is different (I naively thought that "halt" and "shutdown > -h now" were the same): > # shutdown -h now > ... > And in fact the system does get logged off > > Then I reboot again and go to MAINT and do a: > ==> signal shutdown rh5rwmnt > > And I see the system go down on the 3270 session, however it does not > logoff, it goes to disabled wait: > 01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP > stop from > CPU 01. > 00: HCPGIR450W CP entered; disabled wait PSW 00020001 8000 > 0FFF > > Back on MAINT I see: > > HCPSIG2113I User RH5RWMNT has reported successful termination > > However, the user ID remains running: > q rh5rwmnt > RH5RWMNT -L0006 > > So now I'm even more confused. But something does not seem to be working > correctly. > > "Mike MacIsaac"(845) 433-7061 > > -- > 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 -- Brad Hinson Sr. Support Engineer Lead, System z Red Hat, Inc. (919) 754-4198 www.redhat.com/z -- 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 -- This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. --
Re: vmpoff=LOGOFF not working in RHEL 5.3?
Michael MacIsaac wrote: Clovis, Please, try with vmphalt too. root=LABEL=/ vmpoff=LOGOFF vmphalt=LOGOFF BOOT_IMAGE=0 Thanks for the suggestion. I tried that and there was no difference: # cat /proc/cmdline cat /proc/cmdline root=LABEL=/ vmpoff=LOGOFF vmphalt=LOGOFF BOOT_IMAGE=0 # halt halt That should be vmhalt, not vmphalt. The reason vmpoff didn't work the first time is that '/sbin/halt' halts the system without doing a true poweroff instruction (thus leaving the system halted but on), whereas '/sbin/poweroff' does a halt+poweroff. 'shutdown -h now' does a poweroff also, which is why that worked the 2nd time. If you have vmpoff=LOGOFF vmhalt=LOGOFF, you have all your bases covered. Any time the system halts, it'll logoff, regardless of whether you run the command to perform an actual poweroff. -Brad Broadcast message from root (console) (Fri Aug 14 12:01:52 2009): The system is going down for system halt NOW! ... 00: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop from CPU 01. 01: HCPGSP2630I The virtual machine is placed in CP mode due to a SIGP stop and store status from CPU 01. The user ID remains logged on. Then I reboot and try a "shutdown -h now" and the behavior is different (I naively thought that "halt" and "shutdown -h now" were the same): # shutdown -h now ... And in fact the system does get logged off Then I reboot again and go to MAINT and do a: ==> signal shutdown rh5rwmnt And I see the system go down on the 3270 session, however it does not logoff, it goes to disabled wait: 01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop from CPU 01. 00: HCPGIR450W CP entered; disabled wait PSW 00020001 8000 0FFF Back on MAINT I see: HCPSIG2113I User RH5RWMNT has reported successful termination However, the user ID remains running: q rh5rwmnt RH5RWMNT -L0006 So now I'm even more confused. But something does not seem to be working correctly. "Mike MacIsaac"(845) 433-7061 -- 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 -- Brad Hinson Sr. Support Engineer Lead, System z Red Hat, Inc. (919) 754-4198 www.redhat.com/z -- 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
Re: vmpoff=LOGOFF not working in RHEL 5.3?
On Fri, 2009-08-14 at 11:07 -0400, Michael MacIsaac wrote: > Hi, > > Is anyone seeing the vmpoff=LOGOFF *not* working on RHEL 5.3? > > I add this parm to zipl.conf, run zipl and reboot. Then I do a shutdown > (halt) from a 3270 session: > > # cat /proc/cmdline > root=LABEL=/ vmpoff=LOGOFF BOOT_IMAGE=0 > # halt > halt > vmpoff requires halt -p vmhalt is for plain halt Check the generic settings in /sys/firmware, they should reflect the old-style bootparms. grep -r . /sys/firmware/ And rhel 5.3 supports dumpconf, maybe there is a /etc/sysconfig/dumpconf defining something different. Details about dumpconf should be described in Device Drivers Book. Regards Oliver Paukstadt -- Oliver Paukstadt -- 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
Re: Dynamicallhy Changing Linux Guest Network
It's because of the software we use to interface to Active Directory for single signon. It doesn't want 2 systems coming in with the same hostname. If we do that, we can't login to the prod systems :( Marcy "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Michael MacIsaac Sent: Friday, August 14, 2009 9:02 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Dynamicallhy Changing Linux Guest Network Marcy, > have to change IPs and hostnames I can understand that you have to change IP addresses. But do you have to change hostnames? Maybe have a DNS system that maps the same hosts to new i...@s? ... just a thought ... "Mike MacIsaac"(845) 433-7061 -- 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 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
Re: vmpoff=LOGOFF not working in RHEL 5.3?
Clovis, > Please, try with vmphalt too. > > root=LABEL=/ vmpoff=LOGOFF vmphalt=LOGOFF BOOT_IMAGE=0 Thanks for the suggestion. I tried that and there was no difference: # cat /proc/cmdline cat /proc/cmdline root=LABEL=/ vmpoff=LOGOFF vmphalt=LOGOFF BOOT_IMAGE=0 # halt halt Broadcast message from root (console) (Fri Aug 14 12:01:52 2009): The system is going down for system halt NOW! ... 00: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop from CPU 01. 01: HCPGSP2630I The virtual machine is placed in CP mode due to a SIGP stop and store status from CPU 01. The user ID remains logged on. Then I reboot and try a "shutdown -h now" and the behavior is different (I naively thought that "halt" and "shutdown -h now" were the same): # shutdown -h now ... And in fact the system does get logged off Then I reboot again and go to MAINT and do a: ==> signal shutdown rh5rwmnt And I see the system go down on the 3270 session, however it does not logoff, it goes to disabled wait: 01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop from CPU 01. 00: HCPGIR450W CP entered; disabled wait PSW 00020001 8000 0FFF Back on MAINT I see: HCPSIG2113I User RH5RWMNT has reported successful termination However, the user ID remains running: q rh5rwmnt RH5RWMNT -L0006 So now I'm even more confused. But something does not seem to be working correctly. "Mike MacIsaac"(845) 433-7061 -- 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
Re: Dynamicallhy Changing Linux Guest Network
Marcy, > have to change IPs and hostnames I can understand that you have to change IP addresses. But do you have to change hostnames? Maybe have a DNS system that maps the same hosts to new i...@s? ... just a thought ... "Mike MacIsaac"(845) 433-7061 -- 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
Re: Dynamicallhy Changing Linux Guest Network
DHCP is not an option here. In the event of a real disaster, we use the production IP s and hostnames, full replication, all is easy peasy. But for a disaster test, we can't - have to change IPs and hostnames. This can be problematic, but after a while, you make a list and figure it out - not everything uses DNS (think firewall, perhaps load balancers, some stupid sw :). In SuSE 9 and 10, the files that are going to perhaps need attention are /etc/HOSTNAME /etc/hosts /etc/sysconfig/hwcfg-qeth-bus* /etc/sysconfig/network/ifcfg-qeth-bus-ccw-x.x. /etc/sysconfig/network/routes /etc/resolv.conf We also regenerate server SSH keys on a change of the HOSTNAME. Marcy "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Lionel Dyck Sent: Friday, August 14, 2009 8:01 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Dynamicallhy Changing Linux Guest Network Does anyone have a z/vm and/or linux script that they could share that can be used to dynamically change the linux servers network when the server is brought up at a dr site and/or when the network addressing is changed? I've tried playing with it without success - keep missing a piece here or there. thx Lionel B. Dyck, z/Linux Virtualization Specialist IBM Global Services - Kaiser Permanente Team Linux on System z Service Delivery Team 925-926-5332 (8-473-5332) | E-Mail: ld...@us.ibm.com AIM: lbdyck | Yahoo IM: lbdyck I never guess. It is a capital mistake to theorize before one has data. Insensibly one begins to twist facts to suit theories, instead of theories to suit facts. - Sir Arthur Conan Doyle -- 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 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
Re: Dynamically Changing Linux Guest Network
On Aug 14, 2009, at 10:33 AM, David Boyes wrote: Actually, you could trivially construct a Linux NAT appliance that would translate between the DR external addresses and the "normal" ones. It would simply substitute for the default route in the normal network, and NAT appropriately. You just don't bring it up in the normal configuration. In fact iptables provides a netmap function so, as long as you keep the networks the same size and put the guests at the same host-part-of- the-addresses, you can do it in a single line rather than having to do a map per host. Adam -- 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
Re: Dynamicallhy Changing Linux Guest Network
Actually, you could trivially construct a Linux NAT appliance that would translate between the DR external addresses and the "normal" ones. It would simply substitute for the default route in the normal network, and NAT appropriately. You just don't bring it up in the normal configuration. On 8/14/09 11:14 AM, "Richard Troth" wrote: My eyes have seen the glory ... er, uh ... the elegance of an isolated network where this is not needed and not even desirable. Nice when DR looks 100% like your real data center (just virtualized). But that probably doesn't help you in this context. -- 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
Re: vmpoff=LOGOFF not working in RHEL 5.3?
Hi, Please, try with vmphalt too. root=LABEL=/ vmpoff=LOGOFF vmphalt=LOGOFF BOOT_IMAGE=0 Regards, __ Clovis Pereira zVM & zOS Support - SWS Maintenance and Technical Support Services MTS Brazil phone: 55-11-2132-3399 gclo...@br.ibm.com From: Michael MacIsaac To: LINUX-390@VM.MARIST.EDU Date: 14/08/2009 12:07 Subject:vmpoff=LOGOFF not working in RHEL 5.3? Sent by:Linux on 390 Port Hi, Is anyone seeing the vmpoff=LOGOFF *not* working on RHEL 5.3? I add this parm to zipl.conf, run zipl and reboot. Then I do a shutdown (halt) from a 3270 session: # cat /proc/cmdline root=LABEL=/ vmpoff=LOGOFF BOOT_IMAGE=0 # halt halt Broadcast message from root (console) (Fri Aug 14 10:56:58 2009): The system is going down for system halt NOW! INIT: Switching to runlevel: 0 ... 01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop from CPU 00. 00: HCPGSP2630I The virtual machine is placed in CP mode due to a SIGP stop and store status from CPU 00. And the session stops here - it is not logged off as with other distos. Similarly, if I do a halt from an SSH session with no 3270 session active, the user ID remains in a disconnected (DSC) state. Thanks. "Mike MacIsaac"(845) 433-7061 -- 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 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 <><>
Re: Dynamicallhy Changing Linux Guest Network
Use an internal DHCP server configured with specific MAC addresses for each server. Change /etc/dhcp3/dhcpd.conf when you go to DR. That's what it's for. On 8/14/09 11:01 AM, "Lionel Dyck" wrote: Does anyone have a z/vm and/or linux script that they could share that can be used to dynamically change the linux servers network when the server is brought up at a dr site and/or when the network addressing is changed? -- 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
Re: Dynamicallhy Changing Linux Guest Network
On Aug 14, 2009, at 10:01 AM, Lionel Dyck wrote: Does anyone have a z/vm and/or linux script that they could share that can be used to dynamically change the linux servers network when the server is brought up at a dr site and/or when the network addressing is changed? I've tried playing with it without success - keep missing a piece here or there. This is inherently a network-specific question, and I don't think there is a one-size-fits-all approach. A DHCP server that, before starting, does a Q CPUID and swaps the appropriate lease-granting file in is probably the most straightforward approach, but how to do this and do it right is going to be extremely dependent on the specifics of what changes between the DR network and the normal network, or the original network and the changed network. Adam -- 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
Re: Dynamicallhy Changing Linux Guest Network
My eyes have seen the glory ... er, uh ... the elegance of an isolated network where this is not needed and not even desirable. Nice when DR looks 100% like your real data center (just virtualized). But that probably doesn't help you in this context. You can get VM ID and z/VM host node ID from /proc/sysinfo. It's architected. No need for 'hcp' or 'vmcp', just 'grep' for the strings of interest and 'awk' to parse them. You then would want to have some home-grown script (in Linux space) which wraps it all up and automagically sets your DR networking. Not difficult at all, just time consuming. You could also employ (physical) DHCP in your DR network, but your z/VM VSWITCHes would all have to be layer 2. -- R; <>< On Fri, Aug 14, 2009 at 11:01, Lionel Dyck wrote: > Does anyone have a z/vm and/or linux script that they could share that can > be used to dynamically change the linux servers network when the server is > brought up at a dr site and/or when the network addressing is changed? > > I've tried playing with it without success - keep missing a piece here or > there. > > thx > > > > Lionel B. Dyck, z/Linux Virtualization Specialist > IBM Global Services - Kaiser Permanente Team > Linux on System z Service Delivery Team > 925-926-5332 (8-473-5332) | E-Mail: ld...@us.ibm.com > AIM: lbdyck | Yahoo IM: lbdyck > > > I never guess. It is a capital mistake to theorize before one has data. > Insensibly one > begins to twist facts to suit theories, instead of theories to suit facts. > - Sir Arthur Conan Doyle > -- > 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 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
vmpoff=LOGOFF not working in RHEL 5.3?
Hi, Is anyone seeing the vmpoff=LOGOFF *not* working on RHEL 5.3? I add this parm to zipl.conf, run zipl and reboot. Then I do a shutdown (halt) from a 3270 session: # cat /proc/cmdline root=LABEL=/ vmpoff=LOGOFF BOOT_IMAGE=0 # halt halt Broadcast message from root (console) (Fri Aug 14 10:56:58 2009): The system is going down for system halt NOW! INIT: Switching to runlevel: 0 ... 01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop from CPU 00. 00: HCPGSP2630I The virtual machine is placed in CP mode due to a SIGP stop and store status from CPU 00. And the session stops here - it is not logged off as with other distos. Similarly, if I do a halt from an SSH session with no 3270 session active, the user ID remains in a disconnected (DSC) state. Thanks. "Mike MacIsaac"(845) 433-7061 -- 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
Dynamicallhy Changing Linux Guest Network
Does anyone have a z/vm and/or linux script that they could share that can be used to dynamically change the linux servers network when the server is brought up at a dr site and/or when the network addressing is changed? I've tried playing with it without success - keep missing a piece here or there. thx Lionel B. Dyck, z/Linux Virtualization Specialist IBM Global Services - Kaiser Permanente Team Linux on System z Service Delivery Team 925-926-5332 (8-473-5332) | E-Mail: ld...@us.ibm.com AIM: lbdyck | Yahoo IM: lbdyck I never guess. It is a capital mistake to theorize before one has data. Insensibly one begins to twist facts to suit theories, instead of theories to suit facts. - Sir Arthur Conan Doyle -- 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
