Thanks, Alan. My notes said that I was able to do it. Obviously my notes are wrong. I connected a real OSA triplet to the guest and it works fine.
On Thu, Jan 22, 2009 at 8:55 AM, Alan Altmark <alan_altm...@us.ibm.com>wrote: > On Thursday, 01/22/2009 at 08:37 EST, Mark Pace <mpac...@gmail.com> wrote: > > I've got to learn to keep better notes. This worked once in my z/VM 5.4 > under > > z/VM 5.2 running in an LPAR with a GP engine. > > Now I'm trying to do the same thing, z/VM 5.4 as guest in z/VM 5.2 in > an LPAR > > with an IFL. I have defined a NIC for the 2nd level z/VM 5.4 guest, and > > > connected it to the layer 3 vswitch. Now in z/VM 5.4 when I try to > define a > > layer 2 vswitch with that NIC I get errors. > > > > define vswitch vswtch1 rdev 600 contr * > ethernet > > VSWITCH SYSTEM VSWTCH1 is > created > > HCPSWU2832E Connection 0600.P00 for VSWITCH SYSTEM VSWTCH1 is not > active. > > HCPSWU2832E A mismatch was found in the LAN transport > type. > > HCPSWU2830I VSWITCH SYSTEM VSWTCH1 status is disconnected following > error. > > > > I can not figure out what I'm doing differently this time. I'm certain, > mostly, > > that it is not the IFL. > > You cannot define a Layer 2 VSWITCH on a Layer 3 VSWITCH (or vice versa). > (It's the same reason you can't mixed Layer 2 and Layer 3 on the same > VSWITCH.) > > From HELP HCP2832E > -- Connection device for VSWITCH SYSTEM switchname is not active. > A mismatch was found in the LAN transport type > > Explanation: This error occurs in a second-level environment where there > is a > mismatch between the transport defined for the virtual switch and the > simulated OSA-Express device. > > System Action: Device is not an active connection for the virtual > switch. The > virtual switch connection to the network may be active if other devices > are > defined, either through the RDEV keyword on DEFINE VSWITCH or SET > VSWITCH, or > by way of SET PORT GROUP. > > User Response: Ensure the simulated OSA-Express device is coupled to the > > appropriate LAN or virtual switch on the first level system. For example, > if > your second level virtual switch is defined as ETHERNET, the first level > guest > LAN or virtual switch that the simulated OSA-Express is coupled to must > be > ETHERNET as well. > > > Alan Altmark > z/VM Development > IBM Endicott > -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317
