Alan wrote: >Maybe, maybe not. Point me to the documentation. "This document is limited for use only at the GDPS site for which it is licensed Date: 28.03.2010 ZG24-1753-04"
(secret squirrel I guess so it's not on a publicly accessible ibm site). p.61 "To avoid page faults you must use a dedicated address in the OSA adapter for the proxy guest to allow TCP/IP communication independent from the VM TCP/IP machine." And no one uses only one OSA if you really care about SPOF... right? So channel bonding... and no default vlan provided by the network guys now ... so vlan tagging... And on the other... I'm trying...but they tell me we must change by next release... another frowny face... P.64 The following restrictions exist when you are setting up SA MP in conjunction with xDR: A maximum length of 32 characters each is supported for the cluster and node names. Cluster and node names are not allowed to contain periods (.), dashes (-) or underscores (_) and they must not be identical. New restriction in 3.7 (hence the little change bars next to it)... and enforced in 3.8 I'm told apparently. 3.6 didn't have the restriction. I'll send you the PDF off list. 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:[email protected]] On Behalf Of Alan Altmark Sent: Tuesday, March 29, 2011 9:12 PM To: [email protected] Subject: Re: [LINUX-390] VLAN tagging and Channel Bonding with Linux On Tuesday, 03/29/2011 at 11:09 EDT, Marcy Cortes <[email protected]> wrote: > Alan wrote: That's kind of odd. If the VSWITCH controllers have locked memory > I don't know why a VSWITCH wouldn't work. > > Well, I think you know more people that I do that can fix that problem, huh :) Maybe, maybe not. Point me to the documentation. > We like "lifting restrictions". But the adding restrictions is what's really > making us grouchy at the moment. Like, you can't any longer have a "-" sign in > your server names because that is used in Rexx as variable names and we might > need it in the future??!! Nice. (and god forbid they code something that uses > customer data in variable names?? - can you say hello hackers? ) > > 2 harrumphs and an eye roll.. I see your extra harrumph and raise you an eye roll. I have been finding and reporting cases where arbitrary customer-provided data is being used in (for example) a PIPE command string rather than proper use of the VAR stage. They are BUGS and no amount of hand waving will change that. IMO, go ahead, be grouchy. You don't have to put up with poorly-written code. IMNSHO. Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 [email protected] IBM Endicott ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
