Storage Network Local Identifiers for Fast Zoning Decisions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing storage network systems face inefficiencies in data communication due to the need for deep packet inspection to obtain global device identifiers for zoning, which consumes significant processing bandwidth and memory resources.
Innovation Solution
Assigning local identifiers within the storage network system, unique to each device, allows for embedding these identifiers in a shallow location within packets, enabling switch devices to evaluate zone rules without deep packet inspection, thus reducing memory requirements and improving performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If deep packet inspection is performed to obtain global device identifiers for zoning, then accurate device identification and zone rule evaluation are achieved, but processing bandwidth and memory resources are significantly consumed
Solution Approach 1:
The device identifier is segmented into two parts: a compact local identifier (e.g., 4 bytes) embedded in the packet header for quick switch device evaluation, and a full global identifier (e.g., 224 bytes) stored in packet payload for verification. This segmentation allows switch devices to perform zoning decisions using only the small local identifier without deep packet inspection, while still maintaining accurate device identification through the global identifier when needed.
Solution Approach 2:
A central controller acts as an intermediary between device identification and zone rule evaluation. The central controller generates local identifiers for devices and distributes zone rules to switch devices. This intermediary structure enables switch devices to make zoning decisions based on local identifiers without needing to perform deep packet inspection to extract global identifiers, thereby reducing processing overhead while maintaining identification accuracy.
2Reliability
If deep packet inspection is performed to obtain global device identifiers, then zone rules can be accurately evaluated, but switch device performance deteriorates due to high processing load
Solution Approach 1:
The identifier system is segmented into local identifiers for rapid switch device processing and global identifiers for accurate device identification. Switch devices only need to read the small local identifier from the packet header to evaluate zone rules, avoiding the need for deep packet inspection. This segmentation maintains zone rule evaluation accuracy while dramatically improving switch device performance by reducing processing load.
Solution Approach 2:
Local identifiers are pre-assigned to devices and pre-configured in zone rules before actual data transmission occurs. This preliminary action enables switch devices to perform fast zone rule evaluation using only the local identifier without needing to perform deep packet inspection to extract global identifiers during data transmission, thereby maintaining evaluation accuracy while improving processing speed.
3Measurement precision
If global device identifiers are used in packets, then unique device identification is ensured, but memory requirements increase due to the large size of global identifiers
Solution Approach 1:
The device identification system is segmented into a compact local identifier (e.g., 4 bytes) and a full global identifier (e.g., 224 bytes). The local identifier is embedded in the packet header for switch device processing, while the global identifier is stored in the packet payload. This segmentation ensures unique device identification through the global identifier while reducing memory requirements for packet header processing and switch device memory usage.
Solution Approach 2:
A simplified copy of the global identifier, called the local identifier, is created and embedded in the packet header. This local identifier copy contains sufficient information for switch devices to perform zone rule evaluation without needing to store or process the full global identifier in packet headers. This copying approach maintains device identification uniqueness while significantly reducing memory requirements.
Data Source
AI summary
Example implementations relate to storage networks. In some examples, a controller receives a packet sent from a source device to a destination device. The controller reads a local identifier of the source device at a first offset in the packet, where a global identifier of the source device is located at a second offset that is larger than the first offset. The controller also reads a local identifier of the destination device at a third offset in the packet, where a global identifier of the destination device is located at a fourth offset that is larger than the third offset. In response to a determination that the combination of the local identifiers of the source and destination devices matches a predefined zone rule, the controller causes a delivery of the packet to the destination device.