Re: SLES 10 SP2 and Layer 2 support on VMSWITCH
We have tested layer2 and we had to 'set a bit on somewhere' to be able to not define mac, that is possibly in the yast panels as well, but we didn't do it that way. As we can recall, the default for layer2 was that you need to give MAC but changing that bit, made z/VM to generate one unique. So No, you don't have to fill in MAC, but in that case you have to 'set a bit on'. Cordialement / Vriendelijke Groeten / Best Regards / Med Vänliga Hälsningar Tore Agblad Volvo Information Technology Infrastructure Mainframe Design Development SE-405 08, Gothenburg Sweden E-mail: tore.agb...@volvo.com http://www.volvo.com/volvoit/global/en-gb/ From: Linux on 390 Port [linux-...@vm.marist.edu] On Behalf Of Florian Bilek [florian.bi...@gmail.com] Sent: Thursday, September 03, 2009 19:52 To: LINUX-390@VM.MARIST.EDU Subject: SLES 10 SP2 and Layer 2 support on VMSWITCH Dear all, I would like to know if I have to fill in the mac address when defining a layer 2 interface in YAST. Because when I do this, it is not possible to start that VM on another z/VM image as the MAC Prefix of that image is different. So is there a way to avoid the coding of the MAC Address and use the value comming from the NIC? Could not really find more information to this issue. Thank you very much in advance. Best regards, Florian -- 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: SLES 10 SP2 and Layer 2 support on VMSWITCH
Tore, Takk! You have only to enable the layer 2 support and leave the MAC field empty in YAST. After a restart it is still working! I have checked, the fiel LLADDR in ifcfg-qeth-bus-ccw-0.0. is empty. Thank you for that info. Kind regards, Florian On Fri, Sep 4, 2009 at 10:01 AM, Agblad Tore tore.agb...@volvo.com wrote: We have tested layer2 and we had to 'set a bit on somewhere' to be able to not define mac, that is possibly in the yast panels as well, but we didn't do it that way. As we can recall, the default for layer2 was that you need to give MAC but changing that bit, made z/VM to generate one unique. So No, you don't have to fill in MAC, but in that case you have to 'set a bit on'. Cordialement / Vriendelijke Groeten / Best Regards / Med Vänliga Hälsningar Tore Agblad Volvo Information Technology Infrastructure Mainframe Design Development SE-405 08, Gothenburg Sweden E-mail: tore.agb...@volvo.com http://www.volvo.com/volvoit/global/en-gb/ From: Linux on 390 Port [linux-...@vm.marist.edu] On Behalf Of Florian Bilek [florian.bi...@gmail.com] Sent: Thursday, September 03, 2009 19:52 To: LINUX-390@VM.MARIST.EDU Subject: SLES 10 SP2 and Layer 2 support on VMSWITCH Dear all, I would like to know if I have to fill in the mac address when defining a layer 2 interface in YAST. Because when I do this, it is not possible to start that VM on another z/VM image as the MAC Prefix of that image is different. So is there a way to avoid the coding of the MAC Address and use the value comming from the NIC? Could not really find more information to this issue. Thank you very much in advance. Best regards, Florian -- 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
Kickstart Question RHEL5
Getting Kickstart setup for Z Linux guests and am wanting to keep the number ks files to a minimum and not edit them every time a hosts is built, so I noticed during a manual install the IP information gets passed over during the X Install and all you need to do is confirm it so my question is can this be passed over in some way to ks as well so it doesn't need to be specified in the file? - The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you -- 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
I think that I may have joined after the original message for this thread so I am not sure of the use case. Sounds like you may have a disjoint namespace meaning that you use a different DNS than Active Directory for your non-windows systems (like Linux). Our DirectControl product seamlessly works in this type environment such that you can join AD with a different alias than the hostname. Single sign on with AD still works, you don't need to change the hostname and we have a raft of other features as well. Just an FYI. Best regards, Corey Corey Williams Director of Product Management Centrify Corporation 408.542.7508 office 650.520.8450 mobile corey.willi...@centrify.com www.centrify.com Control. Authorize. Audit. Centralized identity management leveraging Microsoft Active Directory. On 8/14/09 10:01 AM, Marcy Cortes marcy.d.cor...@wellsfargo.com wrote: 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 Cortesmarcy.d.cor...@wellsfargo.com 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 mike...@us.ibm.com (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 -- For LINUX-390
Re: Active Directory integration for zLinux (SLES and RHEL)?
Just an FYI that we have shipped the Centrify Suite on RHEL for IBM Series z now. Let me know if you want free access to try it out, still looking for early adopters on the z platform for RHEL or SLES. Quick link to a chalktalk about securing users and access to linux on z in case you don¹t know what I am referring to: http://www.centrify.com/resources/securing-linux-on-ibm-series-z-using-activ e-directory.asp Best regards, Corey On 7/15/09 8:53 PM, C Williams cwilli...@centrify.com wrote: Curious if this is a requirement for folks out there and how they might be addressing it, what their experience has been, etc. Also, we shipped this product for SLES on 390x, we are looking for beta sites for RHEL, please contact me if you are interested in either. Best regards, Corey Williams Director of Product Management Centrify Corporation corey d o t williams a t centrify d o t 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
