On Tuesday, 02/15/2011 at 12:45 EST, Juha Vuori <[email protected]> wrote:
> Define vswitch vsw1 rdev 200.p1 250.p1 ETHERNET > Define vswitch vsw2 rdev 204.p1 254.p1 IP vlan 58 porttype access nogvrp That's not how I recommend defining VLAN-aware VSWITCHes. See my previous posts. DEFINE VSWITCH VSW1 RDEV 204.p1 254.p1 IP VLAN 666 NATIVE 1 Where '666' is an unused VLAN and '1' is the native VLAN id of the physical switch. Why NOGVRP? That prevents CP from telling the switch about the VLANs in use. > One port of two OSA cards (OSA-Express3 dual-port cards) are connected to trunk > ports of physical > switches 1 and 2. > So, actually, all the guests are connected to the external LAN via one OSA port > and one physical switch. I think what you're saying is that 200 and 204 are on port 1 of OSA#1 (primary), and that 250 and 254 are on port 1 of OSA#2 (backup)? "And the quarterback is toast!". The traffic on VSW1 will be untagged. Untagged traffic on a trunk port will be assigned the native VLAN id of the physical switch. You can bet it isn't VLAN 58 or 46 (probably VLAN 1). But you can certainly get your switch techs to look at the traffic and see what's happening. 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 [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/
