Automated Inter-Tenant Service Chaining via SDN Controller
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In cloud-based data centers, configuring physical network functions (PNFs) for inter-tenant communication is typically done manually, which is cumbersome and lacks automation, especially when using standards like EVPN VxLAN.
Innovation Solution
The techniques described automate the configuration and architecture of network devices in data centers to provide PNFs in the forwarding path across tenants, leveraging existing constructs and standards like EVPN VxLAN, and allowing a software-defined network (SDN) controller to manage inter-tenant service chaining without manual intervention.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If manual configuration procedures are used for PNFs, then device-specific customization is possible, but configuration complexity and time consumption increase
Solution Approach 1:
The system enables self-service configuration where the network devices automatically configure themselves for PNF service chaining. The SDN controller orchestrates the configuration process, and devices autonomously apply service VRF tables and establish forwarding paths without manual CLI intervention, significantly reducing configuration time while maintaining device-specific requirements
Solution Approach 2:
Service VRF tables are pre-configured and stored in the network devices before actual PNF service chaining is needed. The SDN controller pre-establishes the forwarding paths and service policies, so when PNF services are activated, the configuration is already in place and devices can immediately begin service chaining operations
2Extent of automation
If manual configuration is used, then detailed control over device settings is achievable, but automation extent is reduced
Solution Approach 1:
An SDN controller acts as an intermediary between network administrators and the physical network functions. The controller translates high-level service chaining requirements into device-specific configuration commands, automatically managing VRF table applications and forwarding path establishment, thereby achieving full automation while maintaining detailed control over device settings
Solution Approach 2:
The configuration process is segmented into distinct automated components: service VRF table management, forwarding path establishment, and PNF integration. Each segment is handled by specific system components working in coordination, allowing comprehensive automation of the overall configuration process while maintaining granular control at each stage
3Adaptability or versatility
If generic PNF configuration is implemented, then adaptability to different PNF types is improved, but configuration standardization may reduce device-specific optimization
Solution Approach 1:
The service VRF table mechanism provides a universal configuration approach that works across different PNF types and vendor-specific devices. The same service VRF table structure and application process can be used for firewalls, load balancers, and other PNFs from different vendors, achieving broad adaptability while maintaining device-specific optimization through the standardized interface
Data Source
AI summary
An example data center system includes server devices hosting data of a first tenant and a second tenant of the data center, network devices of an interconnected topology coupling the server devices including respective service virtual routing and forwarding (VRF) tables, and one or more service devices that communicatively couple the network devices, wherein the service devices include respective service VRF tables for the first set of server devices and the second set of server devices, and wherein the service devices apply services to network traffic flowing between the first set of server devices and the second set of server devices using the first service VRF table and the second service VRF table.