IBM does provide some LACP examples - so you don't have to say "I don't know" :), but you can say it's supposed to look something like this:
http://www.vm.ibm.com/virtualnetwork/cis6509.html I can send you a working LACP cisco 6509 config if you'd like too. We have not yet implemented the VSS 1440 yet - that will happen after the network guys certify. 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: Thursday, February 19, 2009 7:00 AM To: [email protected] Subject: Re: [LINUX-390] VSWITCH - OSA-Ports connected different physical switches On Thursday, 02/19/2009 at 08:33 EST, Hürlimann Heinz (KIUT 33) <[email protected]> wrote: > Hello, > according to the documentation, a z/VM virtual switch controlled link > aggregation (IEEE 802.3ad) allows you to combine multiple physical OSA-Express > ports into a single logical link for increased throughput and for nondisruptive > failover in the event that a port becomes unavailable. But the OSA-Express > adapters that comprise the link aggregation group must be connected to the same > physical switch and LAN segment. > > We have 2 OSA-Ports on different OSA-Adapters which connect to > different > physical switches. We would like to have a load balancing between the two > OSA-Interfaces and also a transparent recovery of a failed > link/switch/OSA-Port. Is there any way to accomplish that with VSWITCH? The 6500s have a feature called "Virtual Switching System (VSS) 1440" that allows multiple switches to appear as one. (Btw, IEEE 802.3ad requires awareness of what's going on on all the links. This isn't a limitation of the VSWITCH.) > Another problem is, that I have to specify how our (outsourced) networker-staff > have to configure the physical switches (Cisco Catalyst 6500) that we can > fullfill our requirements. Can you assist me in this task, to have no inkling > of physical switches. Just say "I don't know.". Switch configuration is a skill like any other. If your network hardware team doesn't know how to configure a switch, there is a light at the end of the tunnel and it isn't the exit. Don't go into the light! (What *is* that rumbling noise anyway?) You should, indeed, be specifying the Requirement, but not the Solution. The networkers need to acquire that on their own. If you don't know and they don't know, then someone has to learn and it might as well be them since it's their job. By all means, educate yourself (if you hire a housekeeper, you should know something about keeping house), but don't let yourself be suckered into doing their job. Of course, if your role as Lead Switch Deployment Architect is spelled out in your outsource contract, then it's time to go to Switch Training, which I'm sure Cisco would be happy to provide. Oh, and time to fire a few lawyers or IT managers. Alan Altmark z/VM Development 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 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
