Apparently, I got lost in the weeds due to the acronym 'VLAN'. I got
some offline help (thanks Pete!) as well as an explanation. It really
isn't a VLAN as much as it is a bridge, so I should have approached it
as such from the get go. I was tripping myself by starting with the
idea of 'internal cross-LPAR network' first.
On the HMC, create a virtual Ethernet adapter for the host, and check
the 'bridging' box. Create a virtual Ethernet adapter for the guest and
don't check that box. Make sure they both have the same VLAN number.
On the host, create 2 Ethernet line descriptions. One will be connected
to a physical Ethernet port; the other will be connected to the virtual
Ethernet adapter created earlier. Make sure they both have the same
name on the BRIDGE() parameter. Plug in your Ethernet cable and vary
them both on. On CFGTCP, there is nothing at all. No interface, no route.
On the guest, create one line description. This is connected to the
virtual Ethernet adapter created earlier. No BRIDGE(). Create an
interface that specifies the external IP address you will be using.
Don't specify a VLAN ID on the LIND() parameter. Create a *DFTROUTE
that has the next hop as the host, with the interface being the one just
created for the line. Vary it on, start the interface and wham, it
works like a charm.
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: Virtual Ethernet between IBM i LPARs, (continued)
This mailing list archive is Copyright 1997-2021 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.