Networking on z/OS
|
Previous topic |
Next topic |
Contents |
Glossary |
Contact z/OS |
PDF
Sysplex distributor roles Networking on z/OS |
||
|
With sysplex distributor, the LPARs in the sysplex are assigned roles. A TCP/IP stack in one LPAR is given the role of being a front-end host. It receives inbound connection requests and redirects them to a specific target back-end TCP/IP stack. Other LPARs run target TCP/IP stacks that ultimately function as the real endpoint of communication.
Sysplex distributor requires that a choice be made as to whether a host is to function as a distributor, a target, a backup distributor, or some combination. Things are about to get a little bit more complicated. So let's define
some simple terminology.
Sysplex distributor in action With these options and flexibility, there are a considerable number of configurations possible. The layout in Figure 1 is just one simple possible scenario. For example, the only application shown as being available on all target hosts is FTP. Such a sysplex might be functioning as a very busy FTP server farm, but it presents a single IP address to all incoming FTP clients. Many other applications could be added to these hosts as target applications. In Figure 1, there are four LPARs being used for sysplex distributor. LPAR 1 is a distributing host, and LPAR 2 is its backup. All LPARs are configured as targets for connections. The target application, of course, is the z/OS FTP server. |
Copyright IBM Corporation 1990, 2010 |