Border Node Routing in Multi-Site Enterprise Fabric
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing LISP techniques are limited in multi-site enterprise fabrics as they cannot register border RLOCs with different path characteristics at the fabric control plane or reply to map requests with multiple border RLOCs in different virtual networks, restricting their use in directing external traffic effectively.
Innovation Solution
Deploying redundant/multiple borders (ingress/egress tunnel routers and RLOCs) in different virtual networks and using additional parameters to route external traffic through multiple RLOCs with varying path characteristics, allowing policy-based and load-balanced routing across RLOCs based on source parameters.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If LISP map server uses traditional single virtual network routing, then routing simplicity is maintained, but scalability and path diversity are limited
Solution Approach 1:
The patent segments the routing control by introducing separate control plane processes (e.g., Route Server, Map Server) that independently handle different aspects of routing decisions. This allows the system to manage multiple virtual networks and path characteristics without overwhelming complexity at any single decision point.
Solution Approach 2:
The patent adds new dimensions to the routing control plane by introducing attributes such as path characteristics, virtual network identifiers, and border node information. This dimensional expansion enables the system to handle diverse routing scenarios while maintaining manageable complexity through structured data organization.
2Productivity
If multiple border RLOCs in different virtual networks are registered, then path diversity and load balancing are improved, but map message handling complexity increases
Solution Approach 1:
The patent implements preliminary registration of border RLOCs with their associated path characteristics and virtual network identifiers in the control plane before actual traffic routing occurs. This pre-processing organizes routing information in advance, reducing the complexity of real-time map message handling while enabling efficient path diversity and load balancing.
Solution Approach 2:
The patent introduces intermediary control plane components (Route Server, Map Server) that mediate between border nodes and forwarding elements. These intermediaries centralize the complexity of managing multiple border RLOCs across different virtual networks, allowing simplified map message handling at the forwarding level while maintaining routing efficiency.
3Reliability
If border nodes are deployed in multiple virtual networks, then network resilience is improved, but registration and mapping operations become more complex
Solution Approach 1:
The patent segments the registration operation by separating border node registration within individual virtual networks from the global routing decision process. Each virtual network can register its border nodes independently with the control plane, and the system aggregates this information for resilient routing decisions without increasing operational complexity at any single level.
Data Source
AI summary
In one embodiment, a method is performed at a node in a multi-site enterprise fabric. The method includes obtaining map entries from a fabric control plane of the multi-site enterprise fabric, where the map entries are associated with identifiers of endpoints in external networks, site and virtual network identifiers of sites in the multi-site enterprise fabric, location identifiers of border nodes, and characteristics of the border nodes. The method further includes receiving a request from a source to connect to an external endpoint. After deriving an external endpoint identifier and source parameters, the method additionally includes establishing at least one connection between the source and the external endpoint via border node(s) that are selected from the map entries based at least in part on the source parameters, the external endpoint identifier, and characteristics of the border node(s) with their site and virtual network identifier(s) along the at least one connection.