Connection network configuration considerations

Following are two examples showing incorrect configuration of a connection network. The correct configuration of the same example follows:

Parallel TGs to the same connection network are not allowed. Only one LAN line description may be associated with a connection name.
Figure 1. Incorrect configuration showing parallel TGs to a connection network
There can be only one connection network name that is associated with a LAN line description at any given time.
One iSeries system (SYSA) has two LAN line descriptions (with a separate connection network that is defined on each), and another iSeries system (SYSB) has two connection network names defined on one LAN line. If SYSA were to request multiple sessions to SYSB, the first session may go over CN1. Another session initiation request might choose CN2. However, the destination address is the same, so the second controller description can not be varied on.

Figure 2. Incorrect configuration showing two connection networks on the same line
Multiple connection networks (that have different connection network names) may be defined on separate LAN lines.
Figure 3. Correct configuration showing two connection networks and two LAN lines

Note:

The name of a virtual node cannot be the same as the control-point name of any network node, or end node. That is, the CNNNETID and CNNCPNAME parameters cannot be the same as the RMTNETID and RMTCPNAME parameters in any controller descriptions in the entire APPN network.