Target Sets Configuration Elements
A Target Set associated with an IPFE maps a single externally available IP address to a set of IP addresses for application servers.
In general, it is inadvisable to reduce delete age value to less than the default. However, a TSA that has connections with longer SCTP heartbeat interval may require this value to be increased from default.
The Table 4-1 describes the fields on the page.
The Table 4-2 describes the fields on the view, insert, and edit pages.
Table 4-1 Target Sets configuration elements (View pages)
| Field | Description | Data Input Notes |
|---|---|---|
| Target Set Number | Unique ID identifying the target set. |
Format: Numeric Range: 1-32 |
| Target Set Address | Public IP address to present to the outside world. |
Format: IPv4 or IPv6 address The target set address must be on the XSI network |
| Target Set IP List | List of IP addresses of the associated application servers. | Format: IPv4 or IPv6 address
IP address type must match that of the target set Address. The IP addresses in target set IP list must be on the XSI network. A maximum of 16 application servers can be added in the target set IP list for each target set address. |
| Weighting | Weighting value is used to apportion load between application servers within the target set. |
Format: Numeric Range: 0-65535 Default: 100 |
| Supported Protocols | The protocols supported by this target set. |
Format: Options Range: TCP only, SCTP only, Both TCP and SCTP Default: Both TCP and SCTP |
| Preferred Active | The IPFE that primarily handles traffic for this target set. Disabled means that the target set is defined, but not currently in use by an IPFE. |
Format: Options Range: IPFE-A1, IPFE-A2, IPFE-B1, IPFE-B2 Default: IPFE-A1 If an option is not activate, you need configure the IPFE address under . |
| Preferred Standby | The mate of the Preferred Active IPFE. If the Preferred Active IPFE is unavailable, the Preferred Standby server takes over. | If the preferred standby IPFE has been configured, it is set when you select the preferred active IPFE. |
Table 4-2 Target Sets configuration elements (Insert and Edit pages)
| Field | Description | Data Input Notes |
|---|---|---|
| Target Set | ||
| * TS Number | Unique ID identifying the TSA. |
Format: List Range:1-32 Default: 1 |
| Protocols | A target set can support SCTP, TCP, or both. |
Format: Options Range: TCP only, SCTP only, Both TCP and SCTP Default: Both TCP and SCTP |
| Disable | Select to disable this target set, but preserve it in this configuration. |
Format: Checkbox Range: Disable |
| * Delete Age | Connections are dropped if idle for this time (seconds). When setting this value please take into account that TCP connections can sometimes be idle for long periods of time depending on the application protocol. |
Format: Text box, numeric Range: 10 - 3110400 Default: 600 |
| Load Balance Algorithm |
Algorithm used to determine where new connections should go. Hash: load balancing by sending the new connection to a server based on hashing the originating port and IP address. Least Load: load balancing by choosing the server with the least load as reported by the application server. (Requires Monitoring Protocol to be set to Heartbeat.) The load of an application server is calculated using the load equation: L(m,c) = (Fm * m/mtotal + Fc * c/ctotal) * Whigh/w where m and mtotal are the currently reserved and total capacity of ingress MPS (messages per second), respectively; c and ctotal are the number of current connections and total connection capacity, respectively; w and whigh are the application server weighing and the highest weighting in the Target IP List, respectively. The value c includes, as an added component, the rate of new connections, in order to smooth the distribution of a sudden flood of new connections. |
Format: Options Range: Hash, Least Load Default: Least Load |
| Least Load Parameters | ||
| * MPS Factor | Factor Fm in load equation. The total Fm + Fc is normalized to 100 on commit of this form. |
Format: Text field; numeric Range: 0 - 100 Default: 50 |
| * Connection Count Factor | Factor Fc in load equation. The total Fm + Fc is normalized to 100 on commit of this form. |
Format: Text field; numeric Range: 0 - 100 Default: 50 |
| * Allowed Deviation |
Percentage within which two application servers' L(m,c) results are considered to be equal, which is used to smooth out load distribution. If the difference in load between the lowest and next least-loaded application server is greater than or equal to this value, then the IPFE applies the Least Load algorithm and assigns new connections to the least loaded application server. If the difference in load between the lowest and next least-loaded application server is less than this value, then the IPFE distributes the connection in a weighted round-robin fashion between the application servers that are within the Allowed Deviation range. |
Format: Text field; numeric Range: 0 - 50 Default: 5 |
| Peer Node Aware Least Load |
Enable peer node group awareness when directing connections. When enabled, the IPFE distribute connections from the same peer node group across servers in the target set to provide server redundancy for that group of peers. The IPFE keeps a group count of the connections from a peer node group to each server in the target set. Servers with a group count difference that is equal to or greater than D from the lowest group count is generally not considered, such as, if D is 1, the effect is to send the connection to the server with the lowest group count. |
Format: Checkbox Default: Enable |
| Peer Node Group Distribution Threshold | The value D in Peer Node Aware |
Format: Text field; numeric Range: 1 - 10 Default: 1 |
| Public IP Address | ||
| * Address | Public IP address presented to the outside world. Do not edit if in use by a local node. | Format: IPv4 or IPv6 address |
| Active IPFE |
IPFE that primarily handles traffic for this TSA. If the active IPFE fails, then its mate takes over. IPFE-A1 and IPFE-A2 are mates. IPFE-B1 and IPFE-B2 are mates. If these options are disabled, IPFE Addresses under IPFE>Configuration>Options need to be configured. |
Format: Options |
| Alternate Public IP Address | ||
| Alternate Address |
Optional alternate public IP address presented to the outside world. For SCTP, this address serves as an non-primary protocol-linked failover address. For TCP, this address can serve as an independent address. If this field is populated, then the column alternate IP address target set IP List must be populated. Do not edit if in use by a local nodes. |
Format: IPv4 or IPv6 address |
| Active IPFE for Alternate address IPFE |
The IPFE that primarily handles traffic for this TSA's alternate address. If the active IPFE fails, then its mate takes over. IPFE-A1 and IPFE-A1 are mates. IPFE-B1 and IPFE-B2 are mates. The setting for this field should complement the setting of Active IPFE in order to provide and alternative path for SCTP dual-homed traffic. This allows SCTP connections with a very short heartbeat interval to transmit on the alternate path if the heartbeat timeout is short than the IPFE switchover delay. |
Format: Options |
| Target Set IP List | ||
| IP Address | Public IPv4 or IPv6 address for the application server. | Format: List |
| Alternate IP Address | Alternate IP address for the application server. | Format: List |
| Description | Free-form description for the application server. | Format: Text |
| * Weighting |
Weighting value used to apportion load between application servers within the target set. The following formula determines the selection of an application server: Application server's % chance of selection = (Application server weight / Sum of all weights in the target set ) * 100. If all application servers have an equal weight, they have an equal chance of being selected. If application servers have unequal capacities, give a higher weight to the servers with the greater capacity. |
Format: Text field; numeric Range: 0 - 65535 |