Storage Area Network Zone Configuration Checksum Conflict Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional storage area network management applications face inefficiencies, particularly in managing zones, as multiple users can modify zone configuration settings simultaneously, leading to overwrites and performance issues due to the need for frequent synchronization of large zoneset data, which consumes bandwidth and time.

Innovation Solution

Generating checksum values for zone configuration information allows for efficient detection of changes by comparing unique identifiers rather than entire configuration sets, reducing memory requirements and avoiding unnecessary data imports, thus ensuring synchronization and minimizing conflicts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multiple users modify zone configuration settings simultaneously, then user productivity is improved, but configuration reliability deteriorates due to overwrites and conflicts

Engineering Contradiction:
Improveuser productivityVSAvoidconfiguration reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system implements a feedback mechanism where the management application continuously monitors zone configuration changes and notifies users of conflicts. When a user attempts to apply configuration changes, the system checks for conflicts with other pending changes and provides feedback about the conflict status, allowing users to decide whether to proceed, wait, or modify their changes.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The management application acts as an intermediary between multiple users and the zone configuration system. It maintains a queue of pending configuration changes, mediates conflicts between simultaneous modifications, and coordinates the application of changes to ensure reliability while allowing multiple users to work concurrently.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If large zoneset data is frequently synchronized, then configuration reliability is improved, but network bandwidth consumption increases

Engineering Contradiction:
Improveconfiguration reliabilityVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system extracts only the essential synchronization information (change indicators and conflict status) from the complete zoneset data, transmitting only this minimal necessary information over the network rather than the entire large zoneset dataset, thereby reducing bandwidth consumption while maintaining reliability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of performing complete zoneset synchronization, the system performs partial synchronization by transmitting only the portions of configuration data that have changed or are relevant to conflict detection, reducing network bandwidth consumption while achieving the necessary reliability.

Inventive Principle:
Principle #16Partial or excessive action

3Measurement precision

If complete zoneset data is imported and stored, then measurement precision is improved for conflict detection, but memory consumption increases

Engineering Contradiction:
Improveconflict detection precisionVSAvoidmemory consumption
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The system extracts only the critical elements needed for conflict detection (such as change indicators, configuration identifiers, and hash values) from the complete zoneset data, storing only these extracted elements in memory rather than the entire datasets, thereby reducing memory consumption while maintaining sufficient precision for conflict detection.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system transforms the complete zoneset data into condensed parameter representations (such as hash values, change indicators, and configuration identifiers) that occupy less memory space but retain the essential information needed for accurate conflict detection and comparison.

Inventive Principle:
Principle #35Parameter changes

4Reliability

If frequent synchronization is performed, then configuration reliability is improved, but time consumption increases

Engineering Contradiction:
Improveconfiguration reliabilityVSAvoidtime consumption
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs partial synchronization operations, transmitting and processing only the changes and conflict-relevant information rather than complete zoneset data, thereby reducing the time required for each synchronization operation while maintaining configuration reliability through frequent operations.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system implements periodic synchronization with optimized intervals, using change detection mechanisms to trigger synchronization only when necessary rather than at fixed frequent intervals, reducing time consumption while maintaining reliability through timely updates.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS7653712B1Methods and apparatus for processing configuration data
Publication Date: 2010.01.26 EMC IP HLDG CO LLC
  • US7653712B1 patent drawing
  • US7653712B1 patent drawing
  • US7653712B1 patent drawing

AI summary

An agent of a storage area network generates a first checksum value for a first set of zone configuration data used to at least initially configure the storage area network. At a later time, after a potential change to the first zone configuration data of the storage area network, the agent generates a checksum value based on current zone configuration data presently used to configure the zone in the storage area network. The agent then compares the first checksum value and the second checksum value to identify whether there has been a change to the first zone configuration data. That is, if the first checksum value does not equal the second checksum value, the agent flags that there has been a change to zone configuration data of the storage area network. Users can control behavior of zoning importation and activation depending on whether current zone configuration data has been changed.