Steps for partitioning a set of TCP/IP stacks in a sysplex into a subplex

You can partition a set of TCP/IP stacks in a sysplex into a subplex that is functionally isolated from the other TCP/IP stacks in the sysplex.

Procedure

Perform the following steps to partition a set of TCP/IP stacks in a sysplex into a subplex:

  1. If TCP/IP coupling facility structures for SYSPLEXPORTS or sysplex-wide security associations (SWSA) are to be used, ensure that all the structures are defined to MVS™ and are specified in the active CFRM policy using their fully suffixed names. For example, if SYSPLEXPORTS is to be used with the base structure name of EZBEPORT, two VTAM® subplexes are to be configured (11 and 12), and within each VTAM subplex, two TCP/IP subplexes are defined (21 and 22), ensure that the EZBEPORT1121, EZBEPORT1122, EZBEPORT1221, and EZBEPORT1222 structures are defined to MVS and specified in the active CFRM policy.
  2. If the VTAM nodes are to be partitioned into subplexes, reconfigure each VTAM node in the VTAM subplex that will support the new TCP/IP subplex. For a description of how to set up VTAM subplexing, see z/OS Communications Server: SNA Network Implementation Guide.
  3. As each VTAM is being reconfigured, for each TCP/IP stack that you want to place in a new subplex, perform the following steps:
    1. Stop the stack.
    2. Change the GLOBALCONFIG statement in the TCP/IP profile to include the XCFGRPID parameter with the group ID for the new subplex.
    3. If HiperSockets™ is enabled and there are TCP/IP stacks that are on the same CPC as this stack and that use the same HiperSockets CHPID, change the GLOBALCONFIG statement in the TCP/IP profile to include the IQDVLANID parameter with the selected VLAN ID for the new subplex.
      Tip: This step depends on the level of isolation you require for your subplexes within the sysplex. If you do not need to isolate the subplexes for HiperSockets connectivity (if, for example, you need only to restrict sysplex distributor distribution between subplexes), you do not need to perform this step.
    4. Start the TCP/IP stack, specifying the updated TCP/IP profile.
    5. Continue until all the TCP/IP stacks in the new subplex have been reconfigured.
Parent topic: Setting up a subplex