Deployment Example 2: Federation Using SAML v2

ProcedureTo Configure Load Balancer 9 for the Federation Manager Servers

Before You Begin
  1. Create a Pool.

    A pool contains all the backend server instances.

    1. Go to URL for the Big IP load balancer login page.

    2. Open the Configuration Utility.

      Click “Configure your BIG-IP (R) using the Configuration Utility.”

    3. In the left pane, click Pools.

    4. On the Pools tab, click the Add button.

    5. In the Add Pool dialog, provide the following information:

      Pool Name

      Example: fm_server_pool

      Load Balancing Method

      Round Robin

      Resources

      Add the IP address of both Federation Manager hosts. In this example:

      192.18.72.89 (for Federation Manager 1)

      192.18.72.86 (for Federation Manager 2)

    6. Click the Done button.

  2. Add a Virtual Server.

    If you encounter Javascript errors or otherwise cannot proceed to create a virtual server, try using Microsoft Internet Explorer for this step.

    1. In the left frame, Click Virtual Servers.

    2. On the Virtual Servers tab, click the Add button.

    3. In the Add a Virtual Server dialog box, provide the following information:

      Address

      192.18.69.14 (for LoadBalancer-9.siroe.com )

      Service

      1080

    4. Continue to click Next until you reach the Select Physical Resources page.

      Select Pool, and then choose fm_server_pool from the drop-down list.

    5. On the same page, set the Cookie Name property to fmlbcookie.

    6. Click the Done button.

  3. Configure the load balancer for persistence.

    1. In the left frame, click Pools.

    2. Click the name of the pool you want to configure.

      In this example, fm_server_pool.

    3. Click the Persistence tab.

    4. On the Persistence tab, under Persistence Type, select Active HTTP Cookie and set the following:

      Method:

      Insert

      When the Insert method is specified, the first time a server receives a request, the load balancer inserts a cookie and cookie value. On subsequent requests, when the load balancer sees the same cookie name and value, it redirects the request to the same server that received the initial request.

    5. Click Apply.

  4. Create a new monitor.

    This monitor will simply indicate whether the Federation Manager servers are running or stopped.

    1. Click the Monitors tab.

    2. Click the Add.

    3. In the Name and Parent window, provide the following information, and then click Next.

      Name

      fm_servers_monitor

      Inherits From

      http

    4. In the Basic Properties window, accept the default values, and then click Next.

      Interval

      5

      Timeout

      16

    5. In the Configure Destination Address and Service window, accept the default values and then click Done.

      The new monitor is added to the list on the Monitors tab.

  5. Click the Basic Associations tab.

    1. Find the IP addresses for Federation Manager 1 and for Federation Manager 2

      In this example: 192.18.72.89 for Federation Manager 1, and 192.18.82.86 for Federation Manager 2.

    2. In the Node dropdown list, select fm_servers_monitor.

    3. Mark the ADD box for each IP address, and then click APPLY.

      When you click Nodes in the left frame of the console, you will be able to see if each server is running or stopped.