Service Chain Debugging via Logical-Physical Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current debugging tools for network connectivity in data center networks implementing service chains lack the ability to effectively test and identify faults within service chains, as they often focus solely on physical connectivity without considering the mapping between logical and physical networks.
Innovation Solution
A system and method that uses a controller to generate customized echo test packets and receive echo reply packets to test end-to-end connectivity and identify fault locations within service chains by mapping logical service chains to physical routing paths, employing virtual routing and forwarding (VRF) configurations and timestamps to determine connectivity issues.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If traditional debugging tools are used for network connectivity, then physical connectivity can be tested, but service chain connectivity and fault localization cannot be effectively identified
Solution Approach 1:
The patent introduces an intermediary mapping relationship between service chains and physical routing paths. The controller maintains a mapping table that correlates logical service chain identifiers with physical routing path identifiers, enabling the debugging tool to translate service chain testing requirements into physical network testing actions and back, thus resolving the inability of traditional tools to handle service chain-specific debugging
Solution Approach 2:
The patent creates a virtual copy of the service chain topology in the controller's mapping table. This copy includes service chain identifiers, routing path identifiers, and node information that mirrors the physical network structure. By working with this copied representation, the debugging tool can perform service chain connectivity testing without directly manipulating the physical network, improving both precision and adaptability
2Adaptability or versatility
If service chain mapping information is integrated into debugging tools, then service chain connectivity can be tested, but tool complexity increases
Solution Approach 1:
The patent extracts the complex mapping management functionality into a separate controller component that maintains the service chain to physical routing path mapping table. The debugging tool itself remains relatively simple, issuing test packets and receiving results, while the controller handles the complexity of mapping translation. This separation reduces the debugging tool's structural complexity while maintaining service chain testing capability
Solution Approach 2:
The controller automatically maintains and updates the mapping table between service chains and physical routing paths without requiring manual configuration in the debugging tool. The system performs self-service by automatically translating service chain identifiers to physical routing path identifiers and back, reducing the complexity burden on the debugging tool while enabling service chain adaptability
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The devices, systems, and methods test network connectivity, where the physical network is used to provide one or more service chains connecting service appliances, including firewalls, intrusion detection systems, load balancers, network address translators, web servers, and so on. A service chain may involve multiple routing paths. The devices, systems, and methods test network connectivity test network connectivity by injecting customized echo request packets on each routing path and collecting customized echo reply packets in response. The customized echo reply packets are processed and aggregated to isolate network connectivity problems.