Child pages
    • Radware AppDirector load balancer
    Skip to end of metadata
    Go to start of metadata

    The Radware AppDirector load balancer pattern builds the BMC Atrium Discovery load balancer model based on Radware AppDirector details obtained via SNMP for the L4Policies, Farms and Application Servers. 

    Additional SNMP requests are used in order to get redundancy configuration. Any configuration no longer reported is removed from the model.

    Load Balancer Model

    Radware AppDirector uses the following conceptual model: L4 Policy (1) - (1) Farm (n) - (1) Application Server

    A L4 Policy is modeled as a Load Balancer Service.

    A Farm is modeled as a Load Balancer Pool.

    A Application Server is modeled as a Load Balancer Member.

    If application servers assigned to different farms have the same name, ip address, and port, they are treated as one Load Balancer Member.

    Supported virtual server types

    • poolbased - The virtual server is based on a pool.

    • ipforward - The virtual server only supports IP forwarding. There is no load balancing on this type of virtual server.

    • l2forward - The virtual server only supports L2 forwarding. There is no load balancing on this type of virtual server.

    • reject - All connections going to this virtual server will be rejected, and resets will be sent.

    Supported L4 applications

    • Any

    • HTTP

    • FTP Control

    • FTP Data

    • HTTPS

    • RTSP

    • RSH

    • REXEC

    • TFTP

    • SIP

    • tsCookie

    • RADIUS

    • FIX

    • VIPI

    • Ping

    Supported L4 protocols

    • TCP

    • UDP

    • ICMP

    • Any - Any IP protocol, including TCP, UDP and ICMP.

    • Other - Any IP traffic different from TCP, UDP or ICMP.

    • SCTP

    Supported algorithms

    • cyclic

    • leastTraffic

    • leastUsersNumber

    • leastTrafficLocal

    • leastUsersNumberLocal

    • nt-1

    • nt-2

    • private-1

    • private-2

    • weightedCyclic

    • static

    • cck-stats

    Supported server operation status

    • Active
    • NotInService
    • NoNewSessions

    Modeled Load Balancer Components

    Load Balancer Instance

    The pattern creates a Load Balancer Instance with the following attributes:

    AttributesValue
    keyA hash of the device key and load balancer type.
    typeA load balancer type (F5 BIG-IP).
    nameA %LB_TYPE% on %device.name%.
    versionA version of the device OS.
    hardware_versionNo sample.
    failover_typeA failover type used on the device.
    failover_stateA failover state reported by the device.

    The pattern models a network service relationship between the device and the Load Balancer Instance.

    Load Balancer Member

    The pattern creates a Load Balancer Member with the following attributes:

    AttributesValue
    key

    A hash of the instance key, IP address and port of the real server.

    ip_addrA server IP address.
    portA server port.
    nameA pair of server IP address and port.
    stateA server state.
    _config_hashContains a hash of the server ip address, port, name, and type.

    The pattern models a containment relationship between the Load Balancer Pool and a Load Balancer Member.

    Load Balancer Service

    The pattern creates a Load Balancer Service with the following attributes:

    AttributesValue
    key

    A hash of the instance key, service name, ip address, and port.

    nameA service name.
    ip_addrA service IP address.
    portA service port.
    typeA service type.
    protocolA service state.
    dns_namesA dns name of a service IP address.
    _config_hashContains a hash of the service name, IP address, port, type,protocol, and state.

    The pattern models a containment relationship between the Load Balancer Instance and a Load Balancer Service.

    The pattern also models a containment relationship between the Load Balancer Service and a Load Balancer Pool.

    Load Balancer Pool

    The pattern creates a Load Balancer Pool with the following attributes:

    AttributesValue
    keyA hash of the instance key and pool name.
    nameA pool name.
    algorithmAn algorithm used by the device.
    _config_hashContains a hash of the pool name, and protocol.

    The pattern models a containment relationship between the Load Balancer Pool and Load Balancer Member.