Actually, if by "native vlan" you mean what is set by
Virtual Ethernet Adapter Properties - vios21
Port Virtual Ethernet (VLAN ID)
they used 3999 (after getting permission from our lan guy) not 1.
But, our lan guy really wants us out of 10.10.1 and on to 10.10.6 anyway
so I will probably end up changing a bunch of IP addresses into that vlan
anyway. Why fight a battle for a short term solution when we should move
to something else anyway?
Now, on to the 252 issue...
Assuming that the Virtual Ethernet for VIOS includes 252 and that it's a
valid VLAN in yours switches AND that it's not restricted on the trunk
AND that there is another port on that VLAN with a device to talk too?
Yes, the virtual ethernet for VIOS includes 4, 6, 209 and 252.
Yes, these are valid and have all been blessed by our network guy.
Addresses such as 10.10.4.x, 10.10.6.x, 10.17.4,x, 10.17.6.x, 209 is dmz,
252 is Mimix; like 10.10.252.x matches 10.17.252.x. Second octet
indicates city (usually), third octet normally matches vlan.
Didn't quite grasp "AND that there is another port on that VLAN with a
device to talk too?" Like is this some switch setting, a hmc setting,
On our old box we had two line descriptions, to two different physical
ports. One ran 10.10.1.x and the other ran Mimix 10.10.252.x. And the
other city was 10.17.6.x and 10.17.252.x for matching stuff.
Does, when I get this working right, this create two 'resources' that I
then associate with two different line descriptions and associate the
interface to the right line description?
Or is it done some how differently? Like multiple vlans on the same