The Dual-Port feature supports two physical ports per CHPID. Each port is independent and can be independently configured as an OSA-ICC. The server definition for each physical port is restricted to a unique TCP port number and subnet. These server restrictions allow isolated Local Area Networks (LAN) to be created for each physical port. The OSA-ICC dual-port function supports 120 sessions which can be randomly distributed between the two LANs. Any external network traffic will only be routed through a common default gateway defined for both ports. An example illustrating an OSA-ICC dual-port connection is given in the network topology diagram in Figure 1.

In addition to the new port a new client connection option has also been introduced. The single client IP per session definition has been expanded to include a range of IP addresses specified by a user defined IP filter.

This document describes the new panels, tag identifiers and how to perform specific tasks using these components to configure OSA-ICC dual-port.

Figure 1 shows connectivity with OSA-ICC dual-port support where each physical port (P0, P1) is configured on a different broadcast domain (LAN). Both P0 and P1 clients communicate with OSA through the defined TCP port. The remote clients are only allowed to connect through P0 since the default gateway is associated with this port. The local clients connected to P1 are restricted to communicate only with the clients of that subnet. For more examples of different OSA-ICC dual-port network topologies, see Network topology diagrams.

Figure 1. Network topology diagram