On Monday, 04/16/2007 at 06:56 GMT, "Dusha, Cecelia CIV WHS/ITMD" <[EMAIL PROTECTED]> wrote: > I have a requirement to implement a VLAN aware tcpip.
1. The VLAN parameter on DEFINE VSWITCH must match the "native" VLAN of the switch. For every switch I have encountered, the default is VLAN 1. If this parameter is wrong, things won't work. (In z/VM 5.3 we have fixed this - see below.) 2. Are you sure you want TCP/IP stacks to be VLAN-aware? Or do you just want to assign them to VLAN 545? Unless the guest is acting as a VLAN router, I don't recommend giving the guest a virtual trunk port. In this case, must SET VSWITCH GRANT VLAN 545 and DON'T specify "PORTTYPE TRUNK" on DEFINE VSWITCH. 3. If you give them all virtual trunk ports, then each *IP stack* must ALSO be explicitly configured to use VLAN 545 (e.g. in DEVICE/LINK). > I thought the following was sufficient to implement this: > > 'CP DEFINE VSWITCH VSW1 RDEV 500 600 CONNECT QUEUESTORAGE 8M CONTROLLER * IP > IPTIMEOUT 5 NONROUTER VLAN 545 PortType TRUNK' I suggest CP DEFINE VSWITCH VSW1 RDEV 500 600 VLAN 1 (leave other options off) CP SET VSWITCH VSW1 GRANT userid1 VLAN 545 CP SET VSWITCH VSW1 GRANT userid2 VLAN 545 etc. If you have RACF, it can hold the VSWITCH authorizations (incl. VLAN id) if you activate the VMLAN class. In z/VM 5.3 this can alternatively appear as: CP DEFINE VSWITCH VSW1 RDEV 500 600 VLAN 565 NATIVE 1 CP SET VSWITCH VSW1 GRANT userid1 CP SET VSWITCH VSW1 GRANT userid2 Alan Altmark z/VM Development IBM Endicott
