I've always avoided VLAN tagging unless the network administration tells me
I need it on the network. Internal networks that never leave the
backplane, I'll never tag them. Too much fuss for so little benefit.
I consider it best practice to have one adapter for each VLAN. Generally
I'll number the virtual adapters like xx1, xx3, xx3 for VLAN 1, 2, and 3.
That way when you look at the hardware location it will give a hint to the
VLAN. Assuming one Ethernet card, I'll create four SEAs and designate them
for specific types of traffic, DMZ, Inter-partition, DEV, and Production.
SR-IOV changes the whole thing since that adapter is very capable, but in
the absence of an SR-IOV adapter the old ways tend to work better.
Larry might opine differently on this but I've always thought with networks,
simple is better than complicated. Makes troubleshooting much easier.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steve
Pavlichek
Sent: Tuesday, May 29, 2018 8:50 AM
To: Midrange List <midrange-l@xxxxxxxxxxxx>
Subject: v7.3 VLAN tagging and VIOS configs
What are best practices for configuring VLANs to IBM I LPARs running under
VIOS? Prior to v7r2, we would configure the VLAN on the virtual ethernet
adapter on the LPAR profile. Now that v7r2/v7r3 support VLAN tagging at the
OS, which is preferred, on the Profile or in the OS?
Say I need to support 5 interfaces each on different VLANs. Should I define
5 virtual ethernet adapters on the Profile and then have ETHLIN01-05 or
should I define 1 virtual ethernet adapter on the Profile and add the VLAN
tag to the TCP/IP Interface and share ETHLIN01 between all 5? I would think
the second option sounds like a cleaner configuration, but networking has
never been my strongest area.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD
midrange.com
