If I recall, it requires a big chunk of memory in your virtual machine. Marcy Cortes "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:[EMAIL PROTECTED] On Behalf Of Ken Schweiker Sent: Wednesday, February 06, 2008 2:18 PM To: [email protected] Subject: Re: [LINUX-390] OSA portname I know a lot of folks are using vswitch. I just don't see a compelling reason to yet. The OSA's have been rock solid. There are plenty of ports to assign. It's a shorter pathlength. It's less complex, though vswitches are not that complex but they are another layer to set up. We do have vm guest lans for security reasons for certain servers. What am I missing? Redundancy. Anything else? Not being a LAN architect, all suggestions are welcome. We will need to address the redundancy issue in the future with some kind of OSA failover if workloads become more critical. About the portname, I finally found the location for that parameter. It wasn't my search string, just that some numskull (no names mentioned :) had set a different portname than I was looking for, on some of the servers. (I must not have noticed the portname mismatch message on startup). So then I think the answer is I would not have to use YaST to change them, just edit the hwcfg-qeth-bus-ccw-0.0.1d20? Mark Post <[EMAIL PROTECTED] > To Sent by: Linux on [email protected] 390 Port cc <[EMAIL PROTECTED] IST.EDU> Subject Re: OSA portname 02/06/2008 03:54 PM Please respond to Linux on 390 Port <[EMAIL PROTECTED] IST.EDU> >>> On Wed, Feb 6, 2008 at 10:14 AM, in message <[EMAIL PROTECTED]>, Ken Schweiker <[EMAIL PROTECTED]> wrote: > Re-defining osa addresses on zVM for a SuSE 9x server to another OSA > card (OSA Express Gb LX). This is the first time this card is being > used and the link does not come up. > (example > DEDICATE 1D00 1F20 > DEDICATE 1D01 1F21 > DEDICATE 1D02 1F22 ) >From later notes in this thread, I see you're onto the possible cause of your error. So, I'll ask the question no one else has. Why in the world are you DEDICATEing OSA ports to a guest? Why are you not using VSWITCH? (There are legitimate reasons to do this, but the question needs to be asked, just in case.) -snip- > I followed a Mark Post post to see/set portname using Yast. It was > already blank but I saved it anyway. So where is the below portname > coming from? -snip- > Setting up network interfaces: > qeth: Device 0.0.1d00/0.0.1d01/0.0.1d02 is a OSD Express card (level: 0635) > with link type OSD_1000 (portname: osacssd) -snip- The fact that it is lower case means that it is being set by a Linux system, somewhere. Any Linux system connected to the OSA could be doing it, not necessarily this particular one. (You say this is the first system to use the card, so it likely is the culprit.) So, on all the systems connected to this card, you could do this: find /etc -type f | xargs grep -il osacssd Mark Post ---------------------------------------------------------------------- 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 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 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
