Sysplex distributor policy example

The goal of this sysplex distributor policy is to limit the number of SD target stacks for inbound Telnet traffic. The policies are identified as SD policies by the ForLoadDistribution TRUE attribute on the PolicyRule statement. The corresponding policy on the target is also shown.

The following statements apply to the example in this topic:

Separate policies are defined on the sysplex distributor distributing and target stacks.
The policy rules select incoming Telnet connection requests.
The selected target stack will be based on WLM information and QoS information if activated at the target stacks.
The rule (disttelnet) is coded on the distributing stack to select inbound traffic destined to the Telnet server.
The rule (targtelnet) is coded on the target stack to select outbound data from the Telnet server.
If none of the specified target stacks is available to service incoming requests (either the node is down or the Telnet server is not active), then sysplex distributor will distribute the requests to any available target stack.
Result: If the OutboundInterface 0.0.0.0 statement (for IPv4) and the OutboundInterface :: statement (for IPv6) are not present, and the defined target stacks are not available, sysplex distributor rejects the request.

policyAction        telnetGold
    {
        MinRate        500       # Provide minimum rate of 500 Kbps.
        OutgoingTOS    10100000  # the TOS value of outgoing telnet packets.
        outboundinterface  129.100.11.1
        outboundinterface  129.100.21.1
        outboundinterface  129.200.12.1
        outboundinterface  129::1B0D:13F0
        outboundinterface  0.0.0.0
        outboundinterface  ::
    }
     
    policyRule           disttelnet
    {
        ProtocolNumberRange     6
        DestinationPortRange    23
        PolicyRulePriority      20
        policyactionreference   telnetGold
        ForLoadDistribution     TRUE
    }
     
    policyRule           targtelnet
    {
        ProtocolNumberRange     6
        SourcePortRange         23
        PolicyRulePriority      20
        policyactionreference   telnetGold
        ForLoadDistribution     FALSE
    }

Notes:

The ApplicationName attribute is valid only for a target rule and should not be coded on a distributor rule because the application name determined for inbound traffic (which is always the case on a distributor) will always be the stack's TCP jobname.
If you are using Telnet with multiple stacks in conjunction with the sysplex distributor, see Accessing remote hosts using Telnet for more information.