On Thursday, 03/26/2009 at 10:47 EDT, Craig Dudley
<[email protected]> wrote:
> Hi,
> Is there a way to tell if a VSWITCH, defined as PORTT TRUNK, has
> successfully completed VLAN trunk negotiations?
> A Q VSWITCH W2HVSW02 DETAILS doesn't show any state of status
> information related to the state of VLAN trunk negotiations.
>
> This question is from our network people.
I deeply regret the confusion caused by putting the PORTTYPE option on
DEFINE VSWITCH. It is the VLAN option that triggers the tagging of
frames. There is no negotiation.
The PORTTYPE option defines the default for the *guests*. IMO, you should
always define a VSWITCH with PORTTYPE ACCESS. If there is a guest who
needs access to more than one VLAN, then you can SET VSWITCH GRANT
PORTTYPE TRUNK.
My personal Best Practice to define a VSWITCH is
DEFINE VSWITCH ... RDEV dev1 RDEV dev2 PORTTYPE ACCESS VLAN <badVLANid>
NATIVE 1
Assumptions:
1. You don't want to configure the guests to be VLAN-aware. If you want a
guest to have a virtual trunk port, you will explicitly give it one.
2. Your network folks have reserved VLAN <badVLANid> to go nowhere and
have authorized the OSA to get to it (if desired)
3. The native VLAN of the physical switch is VLAN 1 ("native" VLAN is the
VLAN used when the switch receives an untagged frame on the trunk. Sort
of like a global "port VLAN id" for trunks.)
Alan Altmark
z/VM Development
IBM Endicott
