If a network system communicates with more than one management system (it participates with multiple MIMIX installations), it must have a different port for each management system with which it communicates. Figure 7 shows an example of such an environment with two MIMIX installations. In the LIBA cluster, the port 50410 is used to communicate between LONDON (the management system) and HONGKONG and CHICAGO (network systems). In the LIBB cluster, the port 50411 is used to communicate between CHICAGO (the management system for this cluster) and MEXICITY and CAIRO. The CHICAGO system has two port numbers defined, one for each MIMIX installation in which it participates.
Figure 7. Creating Port Aliases. In this example, the system CHICAGO participates in two MIMIX installations and uses a separate port for each MIMIX installation.
If you need to use port aliases in an environment such as Figure 7, you need to have a service table entry on each system that equates the port number to the port alias. In this example, CHICAGO would require two port aliases and two service table entries. For example, you might use a port alias of LIBAMGT for port 50410 on LONDON and an alias of LIBANET for port 50410 on both HONKONG and CHICAGO. You might use an alias of LIBBMGT for port 50411 on CHICAGO and an alias of LIBBNET for port 50411 on both CAIRO and MEXICITY. You would use these port aliases in the PORT1 and PORT2 parameters on the transfer definitions.