Adding a Target Set

Before you can add a Target Set, you must configure at least one IPFE in IPFE > Configuration > Options.

Use this task to add a Target Set to the IPFE configuration. Define the list of application server IP addresses for the Target Set and associate the Target Set with an IPFE.

Target Sets associated with an IPFE may be completely overlapping, but may not be partially overlapping. A warning will appear if overlapping Target Sets are associated with an IPFE.

  1. Select IPFE > Configuration > Target Sets.

    The IPFE Configuration Target Sets page appears. Field descriptions are provided by Table 2

  2. Click either the Insert IPv4 or Insert IPv6 button.

    The Target Sets [Forminsert] page appears.

    If no IPFE has been configured, an error message is displayed.

  3. Under the Target Set section complete the following entries:
    1. Select the TS Number for the Target Set.
    2. Select the Protocols this Target Set will support.
    3. If you want to configure the Target Set, but not enable its use, select Disable.
    4. Check the box Initiator Connection Support to support the connections initiated from the Target Set Address, with incoming packets routed through the IPFE to the originating server.
    5. Set the Delete Age timer. The timer must be greater than Diameter Watchdog timer.
    6. Select Hash or Least Load in the Load Balance Algorithm field.
  4. Under the Least Load Parameters section complete the following entries:
    1. Set the MPS Factor.
    2. Set the Connection Count Factor.
    3. Set the deviation percentage of MPS Factor and Connection Count Factor in the Allowed Deviation field.
    4. If you want to Enable Peer Node Group awareness when directing connections, check the box in the Peer Node Aware Least Load field.

      When enabled, the IPFE will 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 will generally not be considered. eg. If D is 1, the effect is to send the connection to the server with the lowest group count.

    5. Set the D value as describe in step 4d (Peer Node Aware Least Load) in the Peer Node Group Distribution Threshold field.
  5. Under the Primary Public IP Address section complete the following entries:
    1. Provide an IP Address to represent this Target Set to the outside world.

      The IP address format will be either IPv4 or IPv6 depending on which button you selected in step 2. This IP address must reside on the XSI network.

    2. Select the Active IPFE that will primarily handle traffic for this TSA.

      If an IPFE is unavailable for selection, that IPFE has not been configured.

      If the Active IPFE fails then its mate will take over.

      If configured, the partner of the active IPFE will be the standby IPFE.

  6. Under the Secondary Public IP Address section complete the following entries:
    1. Provide an optional Secondary Address that is a public IPv4 IP address to represent this Target Set to the outside world.

      For SCTP this address will serve as a non-primary protocol-linked failover address.

      For TCP, this address can serve as an independent address.

      If this field is populated then the column Secondary IP Address under Target Set IP List must be populated. Do not edit if in use by a local node.

    2. Select the Active IPFE for secondary address that will handle traffic for this TSA's secondary address.

      If the Active IPFE fails then its mate will take over.

  7. Under the Target Set IP List section complete the following entries:
    1. Select an IP address in the IP Address field.

      This IP address must reside on the XSI network.

    2. Optionally, select a secondary IP address in the Secondary IP Address field.
    3. Enter a textual description for the application server in the Description field.
    4. Provide a weighting value in the Weighting field.

      The weighting value is used to control the traffic distribution among the application servers.
      Note: Initiator Port Range is managed by OAM and Application.

    5. Click Add to add another IP address to the list.

      You may add up to 16 IP addresses per Target Set.

  8. Click:
    • OK to save the data and return to the IPFE Configuration page.
    • Apply to save the data and remain on this page.
    • Cancel to return to the IPFE Configuration page without saving any changes.

    If OK or Apply is clicked and any of the following conditions exist, an error message appears:
    • Any required field is empty (no entry was made)
    • Any field is not valid or is out of range
    • The maximum number of Target Sets (32) already exists in the system
    • The Target Set Address is already assigned to an IPFE
    • The Target Set Address is already assigned another Target Set
    • The Target Set Address is already used as the address of an application server
    • An IP address appears more than once in the Target Set IP List
    • The Initiator Connection Support is enabled and any listen ports for any local node in the target set is out of responder port range.

    If OK or Applyis clicked and any of the following conditions exist, a warning message appears:
    • Partially overlapping Target Sets are associated with an IPFE.

After application servers have been added to a Target Set, the IPFE will distribute traffic across them.

Parent topic: IPFE Target Sets Configuration