Load Balancing based on IPv6 Anycast and pseudoMobility draftluov6ops6manshim6lbam01 - PowerPoint PPT Presentation

1 / 14
About This Presentation
Title:

Load Balancing based on IPv6 Anycast and pseudoMobility draftluov6ops6manshim6lbam01

Description:

Load balancing across multiple servers would enhance ... (9): Annunciate the Agent the Binding is invalid. (9)':Annunciate the CN the Binding is invalid. ... – PowerPoint PPT presentation

Number of Views:58
Avg rating:3.0/5.0
Slides: 15
Provided by: lwm
Category:

less

Transcript and Presenter's Notes

Title: Load Balancing based on IPv6 Anycast and pseudoMobility draftluov6ops6manshim6lbam01


1
Load Balancing based on IPv6 Anycast and
pseudo-Mobility(draft-luo-v6ops-6man-shim6-lbam-0
1)
  • Wanming Luo,Xiaodong Li
  • Wei Mao,Mei Wang
  • 2009-7-28

2
Outline
  • Introduction
  • Overview
  • Operation of LBAM
  • Conclusion

3
Introduction
  • Load balancing across multiple servers would
    enhance responsiveness and scale well with
    session load.
  • Both IPv4 to IPv6 transition mechanisms, e.g.
    NAT-PT, CGN (Carrier Grade NAT), NAT64 or Tunnel
    broker, and Multihoming require some kind of load
    balancing.

4
Overview
  • Anycast and pseudo-anycast
  • Anycast was adopted by IPv6 specification suite .
  • An IPv6 anycast address is an address that is
    assigned to more than one interface (typically
    belonging to different nodes)
  • When a unicast address is assigned to more than
    one interface, it turns into an anycast address
    consequently.
  • LBAM has two kinds of entity agent and the pool
    of servers, and all of those entities have a
    same anycast address.

5
Overview
  • Only the agent takes part in the routing system,
    and the other servers are "dumb" in routing
    system
  • As for the server, it is the server's unicast
    address who takes part in the routing system.
  • We call this kind of anycast "pseudo-anycast".
  • Use IPv6 Routing header, in which the server's
    unicast address is just a intermediate address to
    be "visited" on the way to a very server's
    pseudo-anycast address

6
Overview
  • Overview of Mobile IPv6 and pseudo-mobility
  • Each mobile node is always identified by its home
    address, a mobile node is also associated with a
    care-of address
  • LBAM Agent will tunnel a packets destined to the
    pseudo-anycast address to the care-of address of
    one selected server, as if the server changed its
    point, even through the server is stationary in
    the same link
  • In the extreme case, all the servers stationary
    at the same link permanently.
  • We call the false mobility as "pseudo-mobility"

7
Load Balancing based on IPv6 Anycast and
pseudo-Mobility(LBAM)
  • Except those modifications followed, the other
    parts of LBAM Agent and servers are same as
    Mobile IPv6. So, it is to easy to implement LBAM
    based on Mobile IPv6.
  • Modifying Binding Cache in LBAM Agent
  • Adding Load Balancing History Cache in LBAM Agent
  • Adding No Active Session Notice parameter

8
Operations of LBAM
9
Operations of LBAM
  • (1) Address Request (URL)
  • (2) Return the pseudo-anycast address
  • (3) Send initial packet to LBAM Agent
  • (4) Choose a "best" server by some load
    balancing algorithms, and log the Binding
  • (5) Tunnel the packet to the server using IPv6
    encapsulation
  • (6) Send Binding Update Message

10
Operations of LBAM
  • (7) Direct session between the server and the CN
  • (8) Detect the session over or timeout
  • (9) Annunciate the Agent the Binding is invalid.
  • (9)Annunciate the CN the Binding is invalid.
  • (10)Invalidate the corresponding Binding

11
Operations of LBAM
  • The other steps except (4)(8) and(10) are all
    ordinary operation in current IPv6 environment
    with mobile support
  • Step(4)implements two functions
  • to choose a "best" server by some load balancing
    algorithm,
  • to log the binding

12
Operations of LBAM
  • Step (8) and(10) are mainly responsible for
    deleting the binding history in LBAM Agent.
  • When a server detects an inactive session with a
    CN, it should send a message to alert the LBAM
    Agent for deleting.

13
Conclusion
  • The benefits of LBAM over other approaches are
    obvious
  • seamless compatibility with current protocol,
  • higher scalability,
  • short delay time
  • no topological constraint on Server pool,
  • protecting previous investment.
  • Easy deployment (only little patch at Server and
    LBAM Agent sides) Compared with other load
    balancing methods,
  • LBAM has better performance and fewest problems
    in IPv6 environment.

14
Conclusion
  • We believe that this technology will be used
    broadly in workload intensive IPv6 application
    including client/server application environment,
    such as IPv4/6 transition gateway, WWW, Email,
    and multimedia services, as well as
    high-performance parallel computing.
Write a Comment
User Comments (0)
About PowerShow.com