Scribd Logo
Upload

Welcome to Scribd!

  • 208 views

    1.azure Load Balancer PDF

    Uploaded by

    Sarath Kumar
    Azure Load Balancer provides load balancing capabilities for applications running on Azure. It uses a 5-tuple hash to map network flows to backend servers and can automatically reconfigure when servers are added or removed. Load Balancer supports health probes to monitor backend servers, frontend IP configurations, backend pools, load balancing rules, port forwarding using NAT rules, and pricing tiers including Basic and Standard.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    1.azure Load Balancer PDF

    Uploaded by

    Sarath Kumar
    208 views4 pages
    Azure Load Balancer provides load balancing capabilities for applications running on Azure. It uses a 5-tuple hash to map network flows to backend servers and can automatically reconfigure when servers are added or removed. Load Balancer supports health probes to monitor backend servers, frontend IP configurations, backend pools, load balancing rules, port forwarding using NAT rules, and pricing tiers including Basic and Standard.

    Original Title

    1.Azure-Load-Balancer.pdf

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Azure Load Balancer provides load balancing capabilities for applications running on Azure. It uses a 5-tuple hash to map network flows to backend servers and can automatically reconfigure when servers are added or removed. Load Balancer supports health probes to monitor backend servers, frontend IP configurations, backend pools, load balancing rules, port forwarding using NAT rules, and pricing tiers including Basic and Standard.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    208 views4 pages

    1.azure Load Balancer PDF

    Uploaded by

    Sarath Kumar
    Azure Load Balancer provides load balancing capabilities for applications running on Azure. It uses a 5-tuple hash to map network flows to backend servers and can automatically reconfigure when servers are added or removed. Load Balancer supports health probes to monitor backend servers, frontend IP configurations, backend pools, load balancing rules, port forwarding using NAT rules, and pricing tiers including Basic and Standard.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 4

    Azure Load Balancer Overview

    Azure Load Balancer Overview


    Load balancing
    By default, Load Balancer uses a 5-tuple hash composed of source
    IP address, source port, destination IP address, destination port, and
    IP protocol number to map flows to available servers

    Standard load balancer


    Port forwarding
    Standard Load Balancer has additional SKU-
    specific capabilities With Load Balancer, you can create an inbound NAT rule to
    port forward traffic from a specific port of a specific frontend
    IP address to a specific port of a specific backend instance
    inside the virtual network
    Azure Load
    balancer
    Using Azure load balancer, you
    can deliver highly available
    Outbound connection Application agnostic and transparent
    applications on Azure
    All outbound flows from private IP addresses inside Load Balancer does not directly interact with TCP or
    your virtual network to public IP addresses on the UDP or the application layer, and any TCP or UDP
    internet can be translated to a frontend IP address of application scenario can be supported.
    the Load Balancer.

    Automatic
    Health probes reconfiguration
    To determine the health of instances Load Balancer instantly
    in the backend pool, Load Balancer reconfigures itself when you
    uses health probes that you define. scale instances up or down.
    Azure Load Balancer components
    Internet

    Azure
    Infrastructure Front-end IP configuration
    A Load balancer can include one or more front end IP addresses, otherwise
    External load known as a virtual IPs (VIPs). These IP addresses serve as ingress for the
    balancer traffic.

    Frontend IP Configuration Back-end address pool


    These are IP addresses (DIPs) associated with the virtual machine Network
    LB & NAT rules Health probes
    Interface Card (NIC) to which load will be distributed.
    Backend Pool of VMs Finance - Production
    Virtual Network Load balancing rules
    99.0.0.0/16
    A rule property maps a given front end IP and port combination to a set of
    back end IP addresses and port combination. A single load balancer can have
    Internal; load multiple load balancing rules. Each rule is a combination of a front-end IP and
    balancer port and back-end IP and port associated with VMs.

    Probes
    Probes enable you to keep track of the health of VM instances. If a health
    AZ1 AZ2 AZ1 AZ2 probe fails, the VM instance will be taken out of rotation automatically.

    App server 1 App server 2


    Web server 1 Web server 2 (99.0.2.4) (99.0.2.5)
    Inbound & Outbound NAT rules
    (99.0.1.4) (99.0.1.5) NAT rules defining the inbound traffic flowing through the front end IP and
    distributed to the back end IP. Outbound rules will translate VM private IP to
    Web servers Subnet App servers Subnet
    (99.0.1.0/24) (99.0.2.0/24) load balancer public IP.
    Pricing tiers

    Category Basic Standard


    Any virtual machine in a single virtual
    Virtual machines in a single availability set network, including blend of virtual
    Backend pool or virtual machine scale set. machines, availability sets, virtual machine
    scale sets.

    Health probes TCP, HTTP TCP, HTTP, HTTPS


    Zone-redundant and zonal frontends for
    inbound and outbound, outbound flows
    Availability Zones Not Available
    mappings survive zone failure, cross-zone
    load balancing.
    Declarative outbound NAT configuration,
    using public IP addresses or public IP
    Outbound rules Not Available
    prefixes or both

    Multiple frontends Inbound and outbound Inbound only

    You might also like