Virtualized Workload Mobility

Virtualized Workload Mobility allows live migration between “Twin” data centers and presents several challenges. Firstly, it brings the challenge of route optimization once the workload has moved to the new location. When virtual machines are migrated between data centers, the traffic flow for client-server may become suboptimal, leading to application performance degradation.

How do existing and new connections get directed to the new location? Traditional methods, such as Route Health Injection ( RHI ) and DNS, are available but don’t suit all requirements. They can place unnecessary workloads over the data center interconnect link ( DCI ), creating a triangular routing effect discussed below.

Triangular Routing

With traditional IP routing, an IP address has two functions:

• Identity: To identify the device.
• Location: We use the device’s location in the network for routing.

LISP separates these two functions of an IP address into two separate tasks:

• Endpoint Identifier (EID): Assigned to hosts like computers, laptops, printers, etc.
• Routing Locators (RLOC): Assigned to routers. We use the RLOC address to reach EIDs.

Cisco created LISP. Originally, it was designed for the Internet, but nowadays, it is also used in other environments, such as data centers, IoT, WAN, and the campus (Cisco SD-Access).

IP Routing.

A router’s primary function is to move an IP packet from one network to a different network. Routers try to select the best loop-free path in a network that forwards a packet to its destination IP address. A router understands nonattached networks through static configuration or dynamic IP routing protocols. So, we have two routing protocols, static and dynamic.

Dynamic IP routing protocols distribute network topology information between routers and provide updates without intervention when a topology change occurs. On the other hand, IP routing with static routes only accommodates topology changes well and can burden network engineers depending on the network size.

A network routing technique

So, what is triangular routing? Triangular routing is a network routing technique that involves sending traffic through three or more points on the network. It is often used to increase the network’s reliability, security, or performance by reducing the load on any single point. In triangular routing, the data is sent from the source node to a middle node and then to the destination node. Depending on the network configuration, the central node may be a router, switch, or hub.

LISP is a map and encapsulation protocol. There are three essential environments in a LISP environment:

• LISP sites: This is the EID namespace where EIDs are.
• Non-LISP sites: This is the RLOC namespace where we find RLOCs. For example, the Internet.
• LISP mapping service: This infrastructure takes care of EID-to-RLOC mappings.

Avoid congestion

Triangular routing is a common technique on the Internet. It is used to avoid congestion and increase reliability. When a connection is established between two nodes, the traffic is sent from the source to the middle node via a shorter route. If the connection between the central node and the destination node is interrupted, the data can be re-routed through another node. This ensures the data is delivered to the destination without interruption.

Example Troubleshooting Technology: Traceroute

### The Mechanics of Traceroute

Traceroute operates by sending packets with incrementing Time-To-Live (TTL) values. Each router that handles the packet decreases the TTL by one until it reaches zero, prompting an ICMP “Time Exceeded” message sent back to the sender. By observing these messages, traceroute maps the journey of the packet, revealing the IP addresses of each hop and the time taken for each segment.

### Why Traceroute Matters

Understanding the route data takes is essential for diagnosing network issues. Traceroute helps identify where delays or failures occur, be it a congested router or a broken link. This insight is invaluable for network administrators seeking to ensure efficient and reliable data delivery, making traceroute a staple in the toolkit for troubleshooting.

### Traceroute in Action

Let’s consider an example: You’re experiencing slow internet speeds. Running a traceroute can reveal if there’s a particular hop causing the delay. By examining the response times and the number of hops, you can pinpoint bottlenecks or misconfigurations in the network. This practical application underscores traceroute’s importance in maintaining network health.

Triangular routing is also used in private networks, such as corporate networks. It reduces the load on a single point, reduces latency, and increases the network’s security. In addition, each node in the triangular routing is configured with different routing protocols, making it difficult for intruders to penetrate the network.

Triangular routing is a reliable and secure technique for improving network performance. Routing data through multiple points on the network can avoid congestion and increase reliability. The following figure shows an example of triangular routing.

Hair-pinning & Triangular routing – Ingress and Egress traffic flows.

1. The external client queries its configured DNS server. The Global Load Balancing ( GLB ) device receives the request, which is authoritative for the queried domain. The GLB responds with the VIP_1 address of the local Load Balancer ( LLB ) in DC1. The VIP_1 represents the application in DC1.
2. Traffic gets directed toward the active LLB in DC1.
3. The LLB performs a source-NAT translation. Source-NAT changes the source IP address to the LLB’s internal IP address. This enables return traffic to be routed through the correct Load balancer, which is necessary to retain existing established sessions.
4. The Virtual Machine ( VM ) receives the packet and replies with the destination address of the Local Load Balancer ( due to Source-NAT ).
5. The LLB performs reverse translation and returns the packet to the external client.

Let’s assume that DC1 is overutilized and the network administrator wants to move the VM from DC1 to DC2. This move will be a hot move, a “live migration,” so all established sessions must remain intact. This is mainly because of the presence of stateful devices and the fact that we are not stretching the state of these stateful devices between the two data centers.

There is also a requirement for a LAN extension, such as OTV or vPC, between the two data centers. The LAN extension stretches VLANs and the layer 2 traffic between the two data centers.

1. The client-server flows are still directed to VIP_1 from the global load balancers, as there have been no changes to site selection for existing connections. We are traversing the same stateful device as in the earlier example.
2. The local load balancer performs Source-NAT and changes the source IP address to its inside address.
3. The packet can reach the moved VM by leveraging the L2 LAN extension between both DCs.
4. Any existing or new sessions using DC1’s VIP_1 will follow the suboptimal path through DC1 to reach DC2.

You hope there will be immediate changes to DNS and any new sessions ingress to DC2. This would follow the optimum path to the VIP_2, and egress traffic would follow the local gateway in DC2.

Triangular routing: The challenge

The main problem with this approach is that it works for only name-based connections, and previously established connections are hairpinned. The hair-pinning effect implies that there have been active connections to the VIP_1 ( old address ) and some new connections to the VIP_2 in the second data center for some time. Hair-pinning can put an additional load on the DCI and create a triangular routing effect.

The Solution? Locator Identity Separation Protocol ( LISP )

A new routing architecture called the Locator Identity Separation Protocol ( LISP ) was developed to overcome the challenges of workload mobility and triangular routing that were previously discussed. LISP overcomes the problems faced with route optimization when workloads migrate. It creates a new paradigm by splitting the device identity, an Endpoint Identifier ( EID ), and its location, known as its Routing Locator ( RLOC ), into two different numbering spaces.

This means we have a separate protocol representing where and who you are. The existing number scheme based on IP does not offer this flexibility, and both roles ( who and where ) are represented by one address.

Additional information on the LISP protocol 

RFC 6830 describes LISP as an Internet Protocol routing and addressing architecture. The LISP routing architecture addresses scalability, multihoming, inter-site traffic engineering, and mobility.

Internet addresses today combine location (how a device is connected to the network) and identity semantics into a single 32-bit or 128-bit number. In LISP, the location is separated from the identity. LISP allows you to change your location in a network (your network layer locator), but your identity remains the same (your network layer identifier).

A LISP separates the identifiers of end users from the routing locators used to reach them. The LISP routing architecture design separates device identity – endpoint identification (EID) – from its location – routing locator (RLOC). To further understand how LISP does the locator/ID separation, it is essential to first learn about the architectural components of LISP. The following are some of the functions or features that form the LISP architecture:

LISP Host Mobility

LISP Host Mobility provides an automated solution that enables IP endpoints, such as Virtual Machines ( VM ), to change location while keeping their assigned IP address. As a result, the LISP detection and mapping system guarantees optimal routing between clients and the IP endpoints that moved. The critical point to note is that it’s an automated system.

Once the VM moves to the new location, there is no need to change DNS. The LISP control plane does not make any changes to DNS and does not require agents to be installed on the clients. It’s completely transparent.

LISP VM-mobility provides a transparent solution to end hosts and guarantees optimal path routing to the moving endpoints. It decouples the identity from the topology but creates two separate namespaces, RLOC and EID. 

The RLOCs remain associated with the topology and are reachable via traditional routing methods. The EID, which describes the end host, can dynamically change location and associate with different RLOCs. This allows the End-point Identifier space to be mobile without impacting the routing interconnecting the locator’s IP space.

LISP VM-Mobility solution:

• • VM migrations are automatically detected by the LISP Tunnel Router ( xTR ). This is accomplished by comparing the source in the IP header of traffic received from the hosts against a range of configured prefixes allowed to roam.
  • No changes are required to DNS or to install any agents. Transparent to end-users.
  • Once the move is detected, the mappings between EIDs and RLOCs are updated by the new xTR.
  • Updating the RLOC-to-EID mappings allows traffic to be redirected to the new locations without causing any updates or churn in the underlying routing. It is transparent to the core.

Load Balancing:

By distributing data packets across multiple paths, triangular routing helps balance the network load. This ensures that no single path becomes overwhelmed with traffic, preventing congestion and optimizing network performance. Load balancing improves network efficiency and minimizes latency, resulting in faster data transmission.

Fault Tolerance:

One critical advantage of triangular routing is its fault tolerance capabilities. In the event of a link failure or network congestion on one path, the other two paths can still carry the data packets to their destination. This redundancy ensures that the network remains operational despite adverse conditions, reducing the risk of data loss and maintaining uninterrupted connectivity.

Closing Points: Triangular Routing LISP 

The Locator/ID Separation Protocol (LISP) is a network architecture and protocol that separates the location and identity of network devices. This distinction allows for more scalable and efficient routing, particularly in large, complex networks. LISP addresses the limitations of traditional IP routing by decoupling the IP address into two distinct components: one for identifying the endpoint (the Identity) and one for determining the endpoint’s location (the Locator).

Triangular routing is a unique concept within the LISP protocol. It refers to a network routing scenario where data packets take a longer, indirect path between the source and destination. This can often occur in mobile networks or when dealing with certain types of address translation. While traditionally seen as a drawback due to increased latency, LISP’s innovative approach can leverage triangular routing to improve network flexibility and resilience. By strategically directing traffic through intermediary nodes, LISP can optimize routing paths and enhance performance.

One of the primary advantages of LISP’s approach to triangular routing is its ability to improve network efficiency and scalability. By dynamically managing routing paths, LISP can adapt to changes in network topology without the need for complex reconfigurations. This adaptability makes it easier to manage large-scale networks, accommodating rapid growth and changes in traffic patterns. Additionally, LISP’s triangular routing can provide better fault tolerance, ensuring continued service even when parts of the network are disrupted.

Implementing LISP within a network involves deploying LISP-capable routers and configuring them to support the protocol’s unique addressing and routing mechanisms. Network administrators can leverage LISP’s control plane to manage mappings between endpoint identifiers and locators, ensuring data packets are routed efficiently. As organizations increasingly migrate to cloud-based architectures and embrace IoT technologies, LISP offers a scalable solution to the challenges of modern networking.