Storage Area Network Transaction Management via Inverted Firewall Connections

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional storage area network management applications face inefficiencies in managing and processing large volumes of management data, particularly due to the need for special accommodations when agents need to transmit data through firewalls, and the complexity of handling resource changes or additions, which can impact external networks.

Innovation Solution

A method where a management server initiates a request for agent information, providing a ticket that allows communication with the storage component to receive data from the agent without requiring special firewall accommodations, enabling seamless data transmission and processing within the storage area network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If agents transmit data through firewalls, then data collection functionality is maintained, but special firewall accommodations are required which increase system complexity

Engineering Contradiction:

Improvedata transmission capabilityVSAvoidfirewall configuration complexity

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

Instead of having agents initiate connections to storage components through firewalls (outbound traffic), the storage components initiate connections to agents (inbound traffic). This inversion allows data transmission through firewalls without requiring special outbound firewall rules, as inbound connections are typically permitted or can be more easily configured.

Inventive Principle:

Principle #13The other way round (Inversion)

Solution Approach 2:

The management server acts as an intermediary that receives data requests from consoles, assigns tickets, and routes them to appropriate storage components. This intermediary layer simplifies the firewall interaction by centralizing the connection management and allowing storage components to initiate connections through the firewall to agents rather than requiring complex outbound rules from agents.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Ease of operation

If storage component addresses are exposed publicly for agent communication, then data transmission is enabled, but security is compromised

Engineering Contradiction:

Improvecommunication capabilityVSAvoidsecurity vulnerability

Core Design Contradiction:

Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The communication initiation direction is inverted: storage components initiate connections to agents rather than agents connecting to storage components. This allows the storage component addresses to remain private and not exposed publicly, as the initiation comes from the storage component side through the firewall, maintaining security while enabling communication.

Inventive Principle:

Principle #13The other way round (Inversion)

Solution Approach 2:

The management server serves as a mediator that handles the communication routing. Consoles send requests to the management server, which then routes them to storage components without exposing storage component addresses to external systems. This intermediary layer maintains the security barrier while enabling necessary data transmission.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Ease of manufacture

If conventional agent-initiated communication is used, then data collection is straightforward, but resource changes or additions impact external networks

Engineering Contradiction:

Improveimplementation simplicityVSAvoidresource change adaptability

Core Design Contradiction:

Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

By inverting the communication initiation direction to storage component-initiated connections, the system becomes more adaptable to resource changes. When resources are added or moved, the storage component can initiate connections to the appropriate agents without requiring changes to external network configurations or firewall rules, as the initiation comes from within the secure internal network.

Inventive Principle:

Principle #13The other way round (Inversion)

Solution Approach 2:

The management server as an intermediary provides a stable internal routing mechanism that is insulated from external network changes. Resource additions or reconfigurations are handled through the internal management server routing rather than requiring external network adaptation, improving the system's adaptability to changing resources.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS8209354B1Transaction lifecycle management in distributed management systems

Publication Date: 2012.06.26 EMC IP HLDG CO LLC

AI summary

A method and apparatus for managing a transaction in a storage area network is presented. A request is received from an agent process at a management server. The management server provides a ticket relating to the request. The ticket is sent to the agent process. The management server identifies a storage process related to the ticket. The storage process contacts the agent process and receives the information from the agent process.