Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Installing and Configuring TLB Using the CLI Interface

 

Before you configure TLB, install the TLB application package.

To install the TLB application:

  1. Download the TLB package.
  2. Install the TLB package in the router.
  3. At the [edit chassis fpc slot-number pic pic-number adaptive-services service-package extension-provider] hierarchy level, configure the desired level of syslog information from the TLB daemon.
  4. Enable TLB network monitoring daemon on the PIC.

After you have installed the application package, you can configure or reconfigure TLB as needed. The following topics describe how to configure TLB. To create a complete application, you must also define interfaces and routing information. You can optionally define firewall filters and policy options in order to differentiate TLB traffic.

Configuring a TLB Instance

TLB configurations are saved in named instances.

Configuring Interface and Routing Information

To configure interface and routing information:

  1. At the [edit services traffic-load-balance instance instance-name] hierarchy level, identify the service interface associated with this instance.

    For example:

  2. Specify the client interface for which an implicit filter is defined to direct traffic in the forward direction. This is required only for translated mode.

    For example:

  3. Specify the virtual routing instance, server-vrf, used to route data traffic in the forward direction to servers. This is required for SLT and Layer 3 DSR; it is optional for Layer 2 DSR.

    For example:

  4. Specify the server interface for which implicit filters are defined to direct return traffic to the client. Note

    Implicit filters for return traffic are not used for DSR.

    For example:

  5. (Optional) Specify the filter used to bypass rephrase as health-check traffic from real servers.

    For example:

  6. Specify the virtual routing instance client-vrfi n which you want the data in the reverse direction to be routed to the clients.Note

    Virtual routing instances for routing data in the reverse direction are not used with DSR.

    For example:

Configuring Servers

To configure servers for the TLB instance:

  1. Go to the [edit services traffic-load-balance instance instance-name] hierarchy level.
  2. At the [edit services traffic-load-balance instance instance-name ] hierarchy level, configure a logical name and IP address for each server to be made available for next-hop distribution.

    For example:

Configuring Network Monitoring Profiles

A network monitoring profile configures a health check probe, which you assign to a server group to which session traffic is distributed. To configure a network monitoring profile:

  1. Configure the type of probe to use for health monitoring — icmp, tcp, http, or custom.
    • For an ICMP probe:

    • For a TCP probe:

    • For an HTTP probe:

    • For an SSL probe:

    • For a custom probe:

  2. Configure the interval for probe attempts, in seconds (1 through 180).

    For example:

    The default value is 5.

  3. Configure the number of failure retries, after which the real server is tagged as down.

    For example:

  4. Configure the number of recovery retries, which is the number of successful probe attempts after which the server is declared up.

    For example:

Configuring Server Groups

Server groups consist of servers to which traffic is distributed by means of stateless, hash-based session distribution and server health monitoring.

To configure a server group:

  1. At the [edit services traffic-load-balance instance instance-name] hierarchy level, specify the names of one or more configured real servers.

    For example:

  2. Configure the routing instance for the group when you do not want to use the default instance, inet.0.

    For example:

  3. (Optional) Disable the default option that allows a server to rejoin the group automatically when it comes up.
  4. Configure one or two network monitoring profiles to be used to monitor the health of servers in this group.

    For example:

Configuring Virtual Services

A virtual service provides an address that is associated with a group of servers to which traffic is directed as determined by hash-based or random session distribution and server health monitoring. You may optionally specify filters and routing instances to steer traffic for TLB.

To configure a virtual service:

  1. At the [edit services traffic-load-balance instance instance-name] hierarchy level, specify a non-zero address for the virtual service.

    For example:

  2. Specify the server group used for this virtual service.

    For example:

  3. Specify a routing instance for the virtual service. If you do not specify a routing instance, the default routing instance is used.

    For example:

  4. (Optional) Specify a routing metric for the virtual service.

    For example:

  5. Specify the method used for load balancing. You can specify a hash method, source-ip, destination-ip, or protocol, or specify random.

    For example:

    or

  6. For mode translated services, specify a service for translation, including a virtual-port, server-listening-port, and protocol.

    For example:

  7. Commit the configuration.
    Note

    In the absence of a client-interface configuration under the TLB instance, the implicit client filter (for VIP) is attached to the client-vrf configured under the TLB instance. In this case, the routing-instance under a translate mode virtual service cannot be the same as the client-vrf configured under the TLB instance. if it is, the commit fails.

Related Documentation