Blade Server Network Traffic Validation via Session ID Matching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network traffic routing and classification systems in blade chassis face challenges during system resets, where session identifiers become inactive, leading to difficulties in validating packet routing and classification.
Innovation Solution
A system and method that generates test packets with session identifiers, sends them through the network, and uses expect queues to validate packet routing by comparing session identifiers and payloads, ensuring accurate routing and classification even after system resets.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If system reset is performed to restore network components, then system reliability is improved, but session identifiers become inactive making packet routing validation difficult
Solution Approach 1:
The system generates test packets with embedded session identifiers before system reset occurs, and creates corresponding expect packets with expected routing information. These preliminary preparations enable validation to proceed successfully even after the reset invalidates actual session identifiers.
Solution Approach 2:
The system creates expect packets as copies of what the test packets should become after proper routing and classification. These expect packets contain duplicate session identifiers and payload data that serve as reference for validating the actual routed packets, bypassing the issue of session identifier invalidation.
2Manufacturing precision
If session identifiers are used to track packets, then packet routing accuracy is improved, but session identifiers become invalid after system reset
Solution Approach 1:
The expect packets contain copied session identifiers from the original test packets. These copied identifiers remain valid for comparison purposes even after system reset, allowing the validation system to verify routing accuracy without relying on the original session identifiers that became invalid.
Solution Approach 2:
The system captures and stores the session identifier information in the expect packets before the system reset occurs. This preliminary capture preserves the routing reference information needed for later validation, preventing loss of routing accuracy data.
3Ease of operation
If test packets are sent through classification engine, then routing validation is enabled, but complex comparison logic is required to handle session identifier extraction and matching
Solution Approach 1:
By embedding duplicate session identifiers and payload data directly in the expect packets, the system creates a simplified comparison mechanism. The validation logic only needs to compare corresponding fields between test and expect packets, rather than implementing complex session identifier extraction, reconstruction, and matching algorithms.
Data Source
AI summary
A system and method for validating network traffic routing within a blade chassis, involving generating a first packet for sending to a first packet receiver by a first route; inserting a first session identifier into a payload of the first packet, where the first session identifier identifies a first session of the first packet receiver; sending the first packet to a packet classifier; sending a first copy packet to a first expect queue, where the first copy packet is a duplicate of the first packet; receiving the first packet by the packet classifier; classifying the first packet by the packet classifier to obtain a first classified packet; extracting the first session identifier from the first classified packet to obtain a first extracted session identifier; and determining whether the first extracted session identifier matches the first session identifier.