Network Feature Trace Capability for Auto QoS and PoE Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current debugging and feature tracing tools are cumbersome and time-consuming, especially in complex networks, as they rely on outdated methods like 'ping' and 'trace route,' which fail to efficiently verify network device capabilities for features like auto QoS and power over Ethernet (PoE).
Innovation Solution
Implementing a feature trace capability that allows network administrators to query and validate features across a network path or the entire network, using feature trace query and response packets that traverse the network hop-by-hop, with a maximum hop count limit to prevent flooding, and provide detailed information on supported features and necessary upgrades.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional tools like ping and trace route are used for feature tracing, then basic network path detection is achieved, but the capability to verify network device features and capabilities is insufficient
Solution Approach 1:
The feature trace packet is designed to serve multiple functions: it traces the network path like traditional tools while simultaneously querying feature capabilities of each device. The packet contains feature type identifiers and version information fields, enabling it to verify auto QoS, PoE, and other network features along the path, combining path tracing and feature verification into a single universal tool.
Solution Approach 2:
The feature trace capability is segmented into discrete query packets that can be independently configured for different feature types. Each packet targets specific features (auto QoS, PoE, etc.) and can be processed independently by network devices, allowing flexible combination of multiple feature queries without requiring a completely new monolithic tool.
2Measurement precision
If show version commands are used to map results back to feature support versions, then feature capability information is obtained, but the process becomes extremely time consuming
Solution Approach 1:
The feature trace packet is prepared in advance with specific feature type identifiers and version information field configurations. Instead of executing multiple sequential show version commands and manually mapping results, the packet is pre-configured to query specific features directly, obtaining capability information in a single traversal pass through the network path.
Solution Approach 2:
The feature trace packet continuously queries feature capabilities as it traverses each network device along the path, without interruption or need to return to the source for additional commands. Each device responds in-line with its feature support status, maintaining continuous information gathering throughout the network traversal, eliminating the stop-start nature of traditional show version approaches.
3Loss of information
If feature trace packets are sent across the entire network without limits, then comprehensive feature information is collected, but network flooding occurs
Solution Approach 1:
The feature trace packet includes a configurable hop count limit parameter that controls the maximum number of network devices the packet will traverse. This parameter can be adjusted based on network size and scope of inquiry, allowing comprehensive feature information collection within safe boundaries. The packet also includes feature type identifiers that can be used to filter and limit queries to only relevant features, reducing unnecessary network traffic.
4Measurement precision
If detailed feature information is collected from every network device, then comprehensive upgrade requirements are identified, but the data processing burden increases
Solution Approach 1:
The feature trace packet extracts only the specific feature capability information needed for upgrade determination, rather than collecting all possible device data. The packet includes targeted feature type identifiers (auto QoS, PoE, etc.) and extracts only the relevant version support information from each device, filtering out unnecessary data and focusing on critical upgrade requirements.
Data Source
AI summary
A feature trace capability may be provided for features including, but not limited to, automatic quality of service (auto QoS), power over Ethernet (PoE), and fabric compatibility. A network command may be implemented with the capability to validate features across a network path or the network as a whole. The output of this network command may result in the display of details about supported features. Such a command may also result in a listing of what devices require upgrades to support any number of features of interest. Embodiments of the feature trace capability may be configured such that the query gets terminated once a final subnet (or endpoint) is reached. Alternatively, the feature trace capability may be configured such that the query gets terminated after a maximum hop count, or trace total (trace_ttl) is reached. Such a limit may prevent the continuous flooding of the network.