Configure inter-partition virtual Ethernet networks
Inter-partition networks with the Hardware Management
Console
If you want an integrated server to communicate with other logical partitions,
or with integrated servers controlled by other i5/OS partitions, you need
to configure one or more inter-partition networks. Inter-partition networks
are configured differently on iSeries™ systems with the Hardware Management
Console (HMC) than on other systems. In an iSeries HMC system, inter-partition connections
exist between partitions or integrated servers using the same VLAN ID. Participating
integrated servers do not support VLAN IDs directly. Instead, each participating
integrated server needs an Ethernet line description that associates a virtual
Ethernet port value with a virtual adapter having a VLAN ID. The configuration
procedure consists of the following steps:
- Use the Hardware Management Console (HMC) to create a virtual
Ethernet adapter for each partition and each integrated server that will participate
in the inter-partition network. See Partitioning
with an eServer i5 and Configure Inter-partition
virtual Ethernet networks for more information. For each virtual adapter
that will connect an integrated server or i5/OS partition to the inter-partition
network, specify a consistent Port virtual LAN ID and uncheck IEEE 802.1Q compatible adapter.
- Configure a virtual Ethernet port and line description as described
in step 1 of the Configure virtual Ethernet networks article
if one has not already been created for the port of interest (0 through 9).
Select an associated port name (Cmnxx) for the appropriate 268C resource.
- Continue with step 2 of the Configure virtual Ethernet networks article
(in all i5/OS partitions that control a participating integrated server),
and step 3 of Configure virtual Ethernet networks.
- For a partition to fully participate, you will need to appropriately configure
the protocol(s) within the partition. In each i5/OS partition, create an Ethernet
line description on the appropriate dedicated 268C port resource. Configure
an appropriate unique IP address in each partition that will participate in
TCP/IP communications.
- Test to see if the inter-partition network is functioning, for example
by pinging between connected integrated servers and partitions.
Inter-partition networks without the Hardware Management
Console
In a system other than an iSeries HMC system, inter-partition connections
exist between partitions using the same network number, and integrated servers
are connected only if their controlling i5/OS partitions are connected. Network
numbers 0-9 are pertinent to integrated servers. For example, if an i5/OS
partition is configured for inter-partition communication on networks 1 and
5, then integrated servers controlled by that partition can participate in
inter-partition communication on virtual Ethernet ports 1 and 5. The configuration
procedure consists of the following steps:
- Configure the network number that you want each partition to connect to.
Refer to Logical Partition concepts and iSeries Navigator
online help information. Keep in mind that integrated servers are connected
only if their controlling i5/OS partitions are connected.
- Configure a virtual Ethernet port and line description as described
if one has not already been created for the port you want to use (0 through
9). See Step 1 of Configure virtual Ethernet networks. Leave the
associated port name set to None.
- Continue with step 2 in Configure virtual Ethernet networks (in
all i5/OS partitions that control a participating integrated server), and
step 3 in Configure virtual Ethernet networks.
- If you want a partition to fully participate, you will need to appropriately
configure the protocol(s) within the partition. In each i5/OS partition that
you want to participate, use the WRKHDWRSC *CMN command to find the name of
the appropriate port of hardware type 268C, which was automatically created.
See Step 1 in Configure virtual Ethernet networks. Then create an
Ethernet line description on the 268C port resource. Configure an appropriate
unique IP address in each partition that will participate in TCP/IP communications.
- Test to see if the inter-partition network is functioning, for example
by pinging between connected integrated servers and partitions.