F5 load balancer sample configuration

Use the F5 load balancer to ensure seamless failover when TrueSight Operations Management is configured for high availability. The following topic provides information on how to prepare and configure F5 load balancer.

Note

This topic provides only a sample configuration of the F5 load balancer. BMC Quality Assurance department used this configuration for TrueSight Operations Management in high availability mode.
Your F5 configuration can vary depending on your requirements. For more information about F5 documentation, see https://support.f5.com/csp/knowledge-center/software

Terms used in this document

  • A node is a logical object on the BIG-IP system that identifies the IP address of a physical resource on the network. You can explicitly create a node, or you can instruct Local Traffic Manager to automatically create one when you add a pool member to a load balancing pool.
  • A load balancing pool is a logical set of devices, such as web servers, that you group together to receive and process traffic. Instead of sending client traffic to the destination IP address specified in the client request, Local Traffic Manager sends the request to any/available servers that are members of that pool.
  • Purpose of health monitors is check the health, performance and load. If a monitored device, link, or service does not respond within a specified timeout period, or the status indicates that service is down or performance is degraded or that the load is excessive, the BIG-IP system can redirect the traffic to another resource.
  • A virtual server is a traffic-management object on the BIG-IP system that is represented by an IP address and a service. Clients on an external network can send application traffic to a virtual server, which then directs the traffic according to your configuration instructions. The main purpose of a virtual server is often to balance traffic load across a pool of servers on an internal network.


To configure F5 load balancer, perform the following:

Note

The F5 version used for testing and the illustrations in this topic: BIG-IP 13.0.0 Build 2.0.1671 Hotfix HF2

TrueSight Presentation server configuration

Create Nodes

  1. From the F5 home page, click Local Traffic > Nodes > Node List.
  2. Click Create.
  3. In the New Node page, enter the following information:
    1. In the Name field, enter a name for the node. For example, add a node named TSPS_node1.
    2. In the Address/FQDN field, enter the IP address of the node or FQDN.
    3. Optionally, in the Description field, enter a brief description for the node.
  4. In the Configuration area, keep the default configurations.
  5. Click Finished. The new node is created.
  6. Repeat the same step to add second node, Standby_node.

Create health monitor

  1. From the F5 home page, click Local Traffic > Monitors.
  2. Click Create.
  3. In the Name field, enter a name for the health monitor.
  4. In the Description field, enter a brief description for the health monitor.
  5. In the Type field, select HTTPS.
  6. In the Send String field:
    • (TrueSight Presentation server 11.0 and later) Enter the following string:
      GET /LogoutUser.jsp HTTP/1.1\r\nHost: <vip_name>\r\nConnection: Close\r\n\r\n
      For example:
      GET /LogoutUser.jsp HTTP/1.1\r\nHost: tsps-vip01.bmc.com\r\nConnection: Close\r\n\r\n
    • (TrueSight Presentation server 10.7 and earlier) Enter the following string:
      GET / HTTP/1.1\r\nHost: <vip_name>\r\nConnection: Close\r\n\r\n
      For example:
      GET / HTTP/1.1\r\nHost: tsps-vip01.bmc.com\r\nConnection: Close\r\n\r\n
  7. In the Receive String field, enter the following string:
    HTTP/1.1 200 
  8. In the Configuration area, retain the default configuration for the rest of the options.
  9. Click Finished.

Create Pool

  1. From the F5 home page, click Local Traffic > Pools > Pool list.
  2. Click Create.
  3. In the Name field, enter a name for the pool.
  4. Select the Health Monitor created in the previous step (TSPS_Health_Monitor).
  5. In the New Members field:
    1. Click Node List.
    2. From the Address drop-down list, click to select the two Presentation Server nodes that you added in the previous step. (Primary_node and Standby_node).
    3. Enter the service port number (the Presentation server Windows default port is 443 and for Linux it is 8043).
    4. Click Add.
  6. Click Finished.

Please note after we create the Pool , primary node should show as Active (green) and secondary node as Standby (red). This is shown below from our in-house setup. Under any circumstance of whatever type of monitoring we are using Primary and Secondary node should be depicted as below.

Create Virtual Server

  1. From the F5 home page, click Local Traffic > Virtual Servers > Virtual Server List.
  2. Click Create.
  3. Under General Properties:
    1. In the Name field, enter a name for the Virtual server.
    2. Optionally, in the Description field, enter a brief description for the Virtual server.
    3. In the Type field, select Standard.
    4. In the Source Address field, 0.0.0.0/0
    5. In the Destination Address/Mask field, IP address of the Virtual server.
    6. Select Service Port as HTTPS with 443 Port.
  4. Under Configuration:
    1. In the HTTP Profile field, choose http
    2. In the SSL Profile (Client) field, select clientssl
    3. In the SSL Profile (Server) field, select serverssl
    4. In the Source Address Translation field, select Auto Map
  5. Click Finished.
  6. Select the saved Virtual Server and click on Edit in the Resource column.
  7. In the Default Pool field, select the pool that you created in the previous step (TSPS_HA_pool).

Install Presentation Server in HA mode

For more information, see:

Installing the Presentation Server in the high-availability mode using the wizard Open link

Installing the Presentation Server in the high-availability mode silently Open link

Add ‘F5 Virtual server’ referrer host to the Presentation Server:

Run the following commands from the Presentation Sever command prompt (installationDirectory\truesightpserver\bin) to add/append the F5 Virtual server as referrer host name:

  1. tssh properties list
    Check tspsProxyHosts if any host(s) listed
  2. Add F5_VIP_FQDN_host_name to the existing value
    tssh properties set tspsProxyHosts
    <F5_VIP_FQDN_host_name>,<host(s) listed from previous command, if any>
    For example: 
    tssh properties set tspsProxyHosts tsps-vip10.bmc.com,rsso-vip01.bmc.com 
  3. tssh properties reload

TrueSight Infrastructure Management server configuration

Create Nodes

  1. From the F5 home page, click Local Traffic > Nodes > Node List.
  2. Click Create.
  3. In the New Node page, enter the following information:
    1. In the Name field, enter a name for the node. For example, add a node named TSIM_node1.
    2. In the Address field, enter the IP address of the node.
    3. Optionally, in the Description field, enter a brief description for the node.
    4. In the Configuration area, retain the default configurations for the rest of the options.
  4. Click Finished. The new node is created.
  5. Repeat the same step to add second node, Standby_node.

Create health monitor

  1. From the F5 home page, click Local Traffic > Monitors.
  2. Click Create.
  3. In the Name field, enter a name for the health monitor.
  4. In the Description field, enter a brief description for health monitor.
  5. In the Type field, select HTTPS.
  6. In the Send String field:
    • (TrueSight Infrastructure Management 11.0 and later) Enter the following string:
      HEAD /jsp/ShowError.jsp HTTP/1.1\r\nHost: <vip_name>\r\nConnection: Close\r\n\r\n
      For example:
      HEAD /jsp/ShowError.jsp HTTP/1.1\r\nHost: tsim-vip01.bmc.com\r\nConnection: Close\r\n\r\n
    • (TrueSight Infrastructure Management 10.7 and earlier) Enter the following string: 
      GET /jsp/Login.jsp HTTP/1.1\r\nHost: <vip_name>\r\nConnection: Close\r\n\r\n
      For example:
      GET /jsp/Login.jsp HTTP/1.1\r\nHost: tsim-vip01.bmc.com\r\nConnection: Close\r\n\r\n
  7. In the Receive String field, enter the following string:
    HTTP/1.1 200
  8. In the Configuration area, retain the default configuration for the rest of the options.

Create Pool

  1. From the F5 home page, click Local Traffic > Pools > Pool list.
  2. Click Create.
  3. In the Name field, enter a name for the pool.
  4. Select the Health Monitor created in the previous step (TSIM_Health_Monitor).
  5. In the New Members field:
    1. Click the Node List.
    2. From the Address drop-down list, click to select the two Infrastructure Management nodes that you added in the previous step (Primary_node and Standby_node).
    3. Enter the service port number (the TrueSight Infrastructure Management server default port is 443).
    4. Click Add.
  6. Click Finished.

Create Virtual Server

  1. From the F5 home page, click Local Traffic > Virtual Servers > Virtual Server List.
  2. Click Create.
  3. Under General Properties:
    1. In the Name field, enter a name for the Virtual server.
    2. Optionally, in the Description field, enter a brief description for the Virtual server.
    3. In the Type field, select Performance (Layer 4).
    4. In the Source Address field, 0.0.0.0/0
    5. In the Destination Address/Mask field, IP address of the Virtual server.
    6. Select Service Port as * All Ports with 0 Port.
  4. Under Configuration:
    1. In the Protocol Profile (Client) field, choose fastL4
    2. In the Source Address Translation field, select Auto Map.
  5. Click Finished.
  6. Select the saved Virtual Server and click on Edit in the Resource column.
  7. In the Default Pool field, select the pool that you created in the previous step (TSIM_HA_pool).

Install/Configure Infrastructure Server in HA mode

For more information, see:

Installing and configuring the Infrastructure Management server for application high-availability using the wizard Open link

Installing and configuring the Infrastructure Management server for application high-availability silently Open link

Add ‘F5 Virtual server’ referrer host to both the primary and secondary Infrastructure Management Server

  1. Open the pronet.conf file located at the installationDirectory\pw\custom\conf directory.
  2. Add or append the F5 Virtual server name (FQDN format) to the pronet.conf property:
    pronet.tsim.proxy.hosts=<existing host(s), if any>,<F5_VIP_FQDN_host_name>. Ensure that there are no spaces between characters.
    Example: pronet.tsim.proxy.hosts=abc.bmc.com,f5_LB.bmc.com
  3. Save the file changes.
  4. Run the following command to reload the properties:
    pw jproperties reload

To configure a TrueSight Infrastructure Management installation with custom ports

If your Infrastructure Management installation is running with a custom port (For example, 8443), you can do one of the following:

  • Access the Infrastructure Management UI using the custom port. For example, https://tsim-vip01.bmc.com:8443/
  • To access the Infrastructure Management UI without specifying the custom port, do the following:
    1. Configure the load balancer by following the steps listed under TrueSight Infrastructure Management server configuration.
    2. Create another VIP for the end user only. Follow all steps listed under  TrueSight Infrastructure Management server configuration with the following changes:
      1. For virtual server, use these settings:


      2. Add the ‘F5 Virtual server’ referrer host to the Infrastructure Management Server:
        1. Open the pronet.conf file located at the installationDirectory\pw\custom\conf directory.
        2. Add or append the F5 Virtual server names (FQDN format) to the pronet.conf property:
          pronet.tsim.proxy.hosts=<existing host(s), if any>,<F5_VIP_FQDN_host_name>,<F5_user_VIP_FQDN_host_name>. Ensure that there are no spaces between characters.
          Example: pronet.tsim.proxy.hosts=abc.bmc.com,f5_LB.bmc.com,f5_user_LB.bmc.com
        3. Save the file changes.
        4. Run the following command to reload the properties:
          pw jproperties reload

TrueSight App Visibility Portal and App Visibility Collector load balancer configuration in HA mode

In TrueSight Operations Management, the App Visibility Portal and App Visibility Collector components can be installed and configured in a High-Availability mode.  However, to manage the connection between the active and standby nodes, the App Visibility Portal and Collector components require a load balancer.  For more information, see App Visibility Manager high-availability deployment

Note

There is no specific load balancer requirement for the App Visibility Portal and App Visibility Collector components.  This document discusses the usage of the F5 load balancer.

Configuring an F5 load balancer is users responsibility, and the information in this document uses as a sample F5 load balancer configuration with App Visibility Portal and App Visibility Collector.  In addition, these steps and screen shots could vary depending on the version of the F5 load balancer.

To install App Visibility Portal in HA mode

  1. Install the F5 load balancer.
  2. Install the App Visibility Portal in HA mode.  For more information, see one of the following topics:

To configure App Visibility Portal load balancer

Create Nodes

A node represents an App Visibility Portal instance in the cluster. For example, if you have a cluster of two App Visibility Portal instances, you will have to create two nodes in F5.

  1. From the F5 home page, click Local Traffic > Nodes > Node List.
  2. Click Create.
  3. In the New Node page, enter the following information:
    1. In the Name field, enter a name for the Primary App Visibility Portal node. For example, add a node named Primary_node.
    2. In the Address field, enter the IP address of the active App Visibility Portal node.
    3. Optionally, in the Description field, enter a brief description for the node.
    4. In the Configuration area, retain the default configurations for the rest of the options.
  4. Click Finished. The new node is created.
  5. Repeat the same step to add second (Standby) App Visibility Portal node (Standby_node).

Create health monitor

You need health monitors to check the nodes at a defined interval to ensure they are alive.

  1. From the F5 home page, click Local Traffic > Monitors.
  2. Click Create.
  3. In the Name field, enter a name for the health monitor. For example, add a health monitor named AVP_health_monitor.
  4. In the Description field, enter a brief description for health monitor.
  5. Select tcp from the Available list, and move it to the Active list.
  6. In the Configuration area, retain the default configuration for the rest of the options.

  7. Click Finished.

Create Pool

You need to create a pool to which nodes can be added.

  1. From the F5 home page, click Local Traffic > Pools > Pool list.
  2. Click Create.
  3. In the Name field, enter a name for the pool. For example, add a pool named pool_aj-tsps_8100
  4.  (Optional) In the Description field, enter a brief description for your pool.
  5. Select the Health Monitor created in the Create health monitor procedure (AVP_health_monitor).
  6.  From the Configuration drop-down list, select Basic.

  7. In the Resources area Load Balancing Method drop-down list, select Round Robin.

  8. In the New Members field:
    1. Click the Node List.
    2. From the Address drop-down list, click to select the two App Visibility Portal nodes (PrimaryAppVisPortal _node and StandbyAppVisPortal_node) that were added in the Create Nodes procedure.
    3. Enter the service port number (for example, port 8100 for App Visibility Portal).
    4. Click Add.
  9. Click Finished.
    A new pool with the specified name is created.
    Note: After creating the pool, the Status of the primary node must be Active (green) and standby node must be standby (red).  

 Create Virtual Server

  1. From the F5 home page, click Local Traffic > Virtual Servers > Virtual Server List.
  2. Click Create.
  3. Under General Properties:
    1. In the Name field, enter a name for the Virtual server. For example, add a virtual server named vs_AppVis_Portal.
    2. (Optional) In the Description field, enter a brief description for the Virtual server.
    3. In the Type field, select Standard.
    4. In the Destination Address field, enter the IP address of the Virtual server.
    5. Select Service Port (for example, port 8200 for App Visibility Collector).
    6. Select the saved Virtual Server and click on Edit in the Resource column.
    7. In the Default Pool field, select the pool that you created in the Create Pool procedure (pool_aj-tsps_8200).
  4. Click Finished.

To install App Visibility Collector in HA mode

  1. Install the F5 load balancer.
  2. Install the App Visibility Portal in HA mode.  For more information, see one of the following topics:

Note

Some of these steps in these procedures and the corresponding screenshots may vary based on the F5 Load Balancer version that you are using.


To configure App Visibility Collector load balancer

Create Nodes

A node represents an App Visibility Collector instance in the cluster. For example, if you have a cluster of two App Visibility Collector instances, you will have to create two nodes in F5.

  1. From the F5 home page, click Local Traffic > Nodes > Node List.
  2. Click Create.
  3. In the New Node page, enter the following information:
    1. In the Name field, enter a name for the Primary App Visibility Collector node. For example, add a node named Primary_node.
    2. In the Address field, enter the IP address of the active App Visibility Collector node.
    3. Optionally, in the Description field, enter a brief description for the node.
    4. In the Configuration area, retain the default configurations for the rest of the options.
  4. Click Finished. The new node is created.
  5. Repeat the same step to add second (Standby) App Visibility Collector node (Standby_node).

Create health monitor

You need health monitors to check the nodes at a defined interval to ensure they are alive.

  1. From the F5 home page, click Local Traffic > Monitors.
  2. Click Create.
  3. In the Name field, enter a name for the health monitor. For example, add a health monitor named AVC_health_monitor.
  4. In the Description field, enter a brief description for health monitor.
  5. Select tcp from the Available list, and move it to the Active list.
  6. In the Configuration area, retain the default configuration for the rest of the options.

  7. Click Finished.

Create Pool

You need to create a pool to which nodes can be added.

  1. From the F5 home page, click Local Traffic > Pools > Pool list.
  2. Click Create.
  3. In the Name field, enter a name for the pool. For example, add a pool named pool_aj-tsps_8100
  4.  (Optional) In the Description field, enter a brief description for your pool.
  5. Select the Health Monitor created in the Create health monitor procedure (AVC_health_monitor).
  6.  From the Configuration drop-down list, select Basic.

  7. In the Resources area Load Balancing Method drop-down list, select Round Robin.

  8. In the New Members field:
    1. Click the Node List.
    2. From the Address drop-down list, click to select the two App Visibility Collector nodes (PrimaryAppVisCollector_node and StandbyAppVisCollector_node) that were added in the Create Nodes procedure.
    3. Enter the service port number (for example, port 8100 for App Visibility Collector).
    4. Click Add.
  9. Click Finished.
    A new pool with the specified name is created.
    Note: After creating the pool, the Status of the primary node must be Active (green) and standby node must be standby (red).  

 Create Virtual Server

  1. From the F5 home page, click Local Traffic > Virtual Servers > Virtual Server List.
  2. Click Create.
  3. Under General Properties:
    1. In the Name field, enter a name for the Virtual server. For example, add a virtual server named vs_AppVis_Collector.
    2. (Optional) In the Description field, enter a brief description for the Virtual server.
    3. In the Type field, select Standard.
    4. In the Destination Address field, enter the IP address of the Virtual server.
    5. Select Service Port (for example, port 8200 for App Visibility Collector).
    6. Click Update at the bottom of the screen.
  4. Select the saved Virtual Server and click the Resource tab.

    1. In the Default Pool field, select the pool that you created in the Create Pool procedure (pool_aj-tsps_8200).
    2. Click Update.
  5. Click Finished.
Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Cassie Derrick

    For 'Add ‘F5 Virtual server’ referrer host to the Infrastructure Management Server' - does this step need to be done on both the primary and secondary?

    Oct 01, 2019 05:58
  2. Cassie Derrick

    Example for TrueSight Application Management would be very helpful here. App management documentation is not nearly as clear.

    Oct 01, 2019 05:59
    1. Harihara Subramanian

      Hi Cassie Derrick,

      I am working with Lisa Jahrsdoerfer (AVM Support person) to get this updated.

      May 07, 2020 08:56
      1. Harihara Subramanian

        Closing this comment as per the following response from Winsor Lim.

        Yes, that web page is the link to the sample configuration for F5 load balancer for App Visibility.  However, the App Visibility does not have a specific web page like the TSOM page in your original email because the load balancer guideline setup is on the customer end and App Visibility does not provide any specific setup for load balancer or what type of load balancer to use.  If Cassie wants some like the TSOM page then you can give her the following link:

         

        https://docs.bmc.com/docs/TSOperations/113/app-visibility-manager-high-availability-deployment-843619753.html

         

        Thanks,

        Winsor

        May 26, 2020 03:11