×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Best practise is for virtual adapters on client logical partitions (LPARs), use Port VLAN IDs. For simplification of the installation, do not configure multiple VLANs on one adapter. Also VLAN tagging enables Load Sharing between the SEA in dual VIOS config.
Sent from Mail for Windows 10
From: Steve Pavlichek
Sent: 29 May 2018 14:50
To: Midrange List
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
