test

N1 Provisioning Server 3.1, Blades Edition, Control Center Management Guide

ProcedureHow To Configure a Load Balancer in Path Failover Mode

This procedure describes configuration of three separate VLAN subnets to enable Path Failover. These subnets are used for data, service, and management path failover.

Before You Begin

Servers running the Solaris Operating System require that the clbmod package is installed to enable load balancing. During the farm activation process, the interface will be plumbed for the clbmod module. If the module is not present the activation will fail.

Path Failover mode requires that the Load Balancer be able to change the interface on which traffic flows from the VIP to the Load Balancer. This is accomplished by placing both management interfaces on the same subnet. When the Load Balancer determines that it no longer has a path to the target IP via the interface on which it was configured, it will then restore those paths on the other, live, interface. See Load Balancer Best Practices for additional information and illustrations.

Note –

Path failover is automatically configured when both management interfaces are placed on a single subnet. In this configuration, the VIPs will be configured on the primary port that the user selects, but when that primary port fails, they will be failed over to the other port.

This procedure assumes the following connections and naming conventions for farm components.

Steps

  1. Configure the management VLAN.

    Servers are load balanced on the management VLAN.

    1. Drag a Load Balancer, two Servers, an External Subnet and a Internal Subnet onto the Editor screen.

    2. Connect the Load Balancer management interfaces to the Internal Management Subnet.

      This automatically configures the Load Balancer in Path failover mode.

    3. Connect a VIP from the Load Balancer to Internal Management Subnet.

    4. Connect both primary interfaces on both physical ports of the Server to the Management Subnet.

    5. Connect Server1 service interfaces to Service Subnet.

    6. Place the data interface from the Server on the Data Subnet that will have the same VLAN as the VIPs.

  2. Choose Save from the File menu.

    The farm configuration is saved.

  3. Double click the Load Balancer element.

    The Configure Load Balancer dialog box appears.

  4. Select the type of Load Balancer from the Type drop-down list.

  5. Select the Policy type for the Load Balancer from the Policy drop-down list.

    The following choices appear.

    • Round Robin (default)—New connections are routed sequentially to servers in the Load Balancer group, thereby spreading new sessions equally across all servers.

    • Least Connected—New connections are sent to the server with the least number of active sessions.

    • Weighted—New connections are sent to servers according to weight assignments. Servers with a higher weight value receive a larger percentage of connections. You can assign a weight to each real server, and that weight determines the percentage of the current connections given to each server. The default weight is one. You must set the load balancer weights manually.

    Note –

    You may modify the Load Balancer policy in the Design and Active states.

  6. Click the + button to add a binding to the eth0:vip0 interface.

    The eth0:1 interface binding appears.

  7. Type the appropriate port number in the virtual and real port edit fields, for example 50.

  8. Select Server1-eth0:1 as the Real interface from the Real Interface drop-down list.

  9. Click the + button under virtual interface to add an interface.

    The eth0:2 interface appears.

  10. Type the appropriate port number in the virtual and real port edit fields, for example 50.

  11. Select Server2-eth0:2 as the Real interface from the Real Interface drop-down list.

  12. Click the OK button to close the Configure Load Balancer dialog box.

  13. Configure Servers. See How To Configure Servers for Load Balancing.

    You must configure Servers to enable load balancing.

  14. Connect the service and management VLANs.

    1. Connect the Load Balancer VIPs to the External Subnet and to the Management Subnet.

    2. Connect the service and data virtual interfaces from Server2 to the Service Subnet and the Data Subnet.

  15. Configure VLANs. See How To Modify a VLAN Configuration for Load Balancing.

  16. Choose Save from the File menu.

    The farm configuration is saved.

See Also