5.3 Configure IP Front End

This procedure configures IP Front End (IPFE) and optimizes performance.

1. Log in to the SOAM VIP GUI as the guiadmin user.
2. In SOAM VIP, configuration of replication IPFE association data.
   1. Navigate to IPFE, and then Configuration, and then Options.
   2. Type the IP address of the 1st IPFE in the IPFE-A1 IP Address field and the IP address of the 2nd IPFE in the IPFE-A2 IP Address field.
   3. If applicable, type the address of the 3rd and 4th IPFE servers in IPFE-B1 IP Address and IPFE-B2 IP Address fields.
      
      
      
      

   Note:

   • It is recommended that the address resides on the IMI (Internal Management Interface) network.
   • IPFE-A1 and IPFE-A2 must have connectivity between each other using these addresses. The same applies to IPFE-B1 and IPFE-B2.
3. In SOAM VIP, configuration of IPFE target sets (Part 1).
   1. Log into the SOAM VIP GUI as the guiadmin user.
   2. Navigate to IPFE, and then Configuration, and then Target Sets.
   3. Click either Insert IPv4 or Insert IPv6 depending on the IP version of the target set you plan to use.

      This screen displays the following configurable settings:

      Protocols: Protocols the target set supports.

      Delete Age: Specifies when the IPFE should remove its association data for a connection. Any packets presenting a source IP address/port combination that had been previously stored as association state but have been idle longer than the Delete Age configuration are treated as a new connection and does not automatically go to the same application server.

      Load Balance Algorithm: Hash or Least Load options.

   Note:

   • For the IPFE to provide Least Load distribution, navigate to IPFE, and then Configuration, and then Options. Monitoring Protocol must be set to Heartbeat so the application servers can provide the load information the IPFE uses to select the least-loaded server for connections.
   • The Least Load option is the default setting, and is the recommended option with exception of unique backward compatibility scenarios.
4. In SOAM VIP, configuration of IPFE target sets (Part 2).
   1. Navigate to IPFE, and then Configuration, and then Target Sets.

      (Optional): If you have selected the Least Load algorithm, then you may configure the following fields to adjust the algorithm’s behavior:

      MPS Factor: Messages per Second (MPS) is one component of the least load algorithm. This field allows you to set it from 0 (not used in load calculations) to 100 (the only component used for load calculations). It is recommended that IPFE connections have Reserved Ingress MPS set to something other than the default, which is 0. To configure Reserved Ingress MPS, navigate to Main Menu, and then Diameter, and then Configuration, and then Configuration Sets, and then Capacity Configuration. If you choose not to use Reserved Ingress MPS, set MPS Factor to 0, and Connection Count Factor, described below, to 100.

      Connection Count Factor: This is the other component of the least load algorithm. This field allows you to set it from 0 (not used in load calculations) to 100 (the only component used for load calculations). Increase this setting if connection storms (the arrival of many connections at a very rapid rate) are a concern.

      Allowed Deviation: Percentage within which two application server's load calculation results are considered to be equal. If very short, intense connection bursts are expected to occur, increase the value to smooth out the distribution.

      Primary Public IP Address: IP address for the target set.

      Note:

      This address must reside on the XSI (External Signaling Interface) network because it is used by the application clients to reach the application servers. This address must not be a real interface address (that is, must not be associated with a network interface card).

      Active IPFE: IPFE to handle the traffic for the target set address.

      Secondary Public IP Address: If this target set supports either multi-homed SCTP or Both TCP and SCTP, provide a Secondary IP Address.

      Note:

      • A secondary address is required to support SCTP multi-homing. A secondary address can support TCP, but the TCP connections are not multi-homed.
      • If SCTP multi-homing is to be supported, select the mate IPFE of the Active IPFE for the Active IPFE for secondary address to ensure SCTP failover functions as designed.

      Target Set IP List: Select an IP address, a secondary IP address if supporting SCTP multi-homing, a description, and a weight for the application server.

      Note:

      • • The IP address must be on the XSI network since they must be on the same network as the target set address. This address must also match the IP version of the target set address (IPv4 or IPv6). If the Secondary Public IP Address is configured, it must reside on the same application server as the first IP address.
        • A port must be created to associate the IP that needs to be used as TSA IP in cloud. Create a port using the following command:

          neutron port-create <xsi network-id>

          The command results in an IP that can be used as TSA IP.

        • If all application servers have an equal weight (for example, 100, which is the default), they have an equal chance of being selected. Application servers with larger weights have a greater chance of being selected.
   2. Click Add to add more application servers (up to 16).
   3. Click Apply.
5. In SOAM VIP, repeat for additional configuration of IPFE target sets.
   Repeat steps 3 and 4 for each target set (up to 16).

   At least one target set must be configured.