On Wednesday, 11/02/2005 at 10:27 CST, Adam Thornton <[EMAIL PROTECTED]> wrote:
> Am I confused? I thought the VSWITCH controller required a dedicated > OSA port. Controllers don't have ports. They're just "CP helper" virtual machines. > I guess it doesn't have to be a different physical port, but wouldn't > that be wise in case you lose a port or a cable? Ideally, ports on > entirely different cards, going to different physical switches, right? It depends on what you want to do. If you want a Linux guest to have access to VLAN A and VLAN B, but didn't want to give him a virtual trunk port, then you would create two VSWITCHes, both using the same OSA port (different subchannels, of course) but with different VLAN numbers. The controllers being used are irrelevant. > Then, if those switches are trunked, no need for host-level VIPA, in > that incoming packets will still be able to get to the host no matter > which physical switch they're hanging off of. If they aren't, > though, you *do* need host-level VIPA providing dummy addresses so > that packets can get down the right wire to the right VSWITCH to the > right guest. Recipe. You need: - Two controllers - Two OSA chpids - Two switches - One VSWITCH 1. Create two controllers. Start them and ignore. 2. Trunk the two switches together 3. Locate two ports, one on each switch, that are defined to be in the same LAN (VLAN) 4. Plug each OSA into one of the two ports 5. Define the VSWITCH and specify rdevs of the OSAs If the switches are not trunked, then you have separate networks. All OSAs defined to a VSWITCH *must* be in the same network. You can use two ports on the SAME switch, and you will still be protected from a port or OSA failure. You will not be protected from a switch failure. 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
