Enclosure Management Controller Drive Mapping Architecture
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing computing systems require multiple motherboards to manage a large number of drive slots in mass storage devices, limiting flexibility and efficiency in enclosure management, as all enclosure management controllers (EMCs) need to be connected to motherboards to receive data.
Innovation Solution
A highly configurable architecture allows multiple EMCs to communicate with each other, with one EMC functioning as a master to collect and map enclosure management data from others, enabling the operation of drive slot status indicators without direct connection to motherboards, using SPI, SGPIO, or SMBus for communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If multiple EMCs are connected to multiple motherboards to manage large number of drive slots, then the number of controlled drive slots increases, but the system complexity and hardware requirements increase
Solution Approach 1:
Multiple EMCs are merged into a coordinated system where one master EMC consolidates enclosure management data from multiple slave EMCs, allowing them to function as a unified control unit. This merging approach enables management of large numbers of drive slots without proportionally increasing motherboard connections or system complexity.
Solution Approach 2:
The master EMC performs multiple functions: it collects enclosure management data from multiple slave EMCs, maps drive slot status indicators across all connected EMCs, and coordinates LED status indications for the entire drive array. This multi-functionality reduces the need for separate control paths for each EMC.
2Reliability
If all EMCs are connected to motherboards to receive enclosure management data, then data reception capability is ensured, but the flexibility and configurability of the system decreases
Solution Approach 1:
The master EMC acts as an intermediary between the slave EMCs and the motherboard. Instead of requiring each EMC to connect directly to a motherboard, the master EMC receives enclosure management data and redistributes it to appropriate slave EMCs, providing flexibility in system configuration while ensuring reliable data reception.
Solution Approach 2:
The system is segmented into master and slave EMC roles, allowing flexible configuration where only the master EMC requires direct motherboard connection. Slave EMCs can be distributed across multiple backplanes without requiring individual motherboard connections, enhancing system adaptability.
3Speed
If each EMC independently controls drive slot status indicators, then control responsiveness is improved, but the coordination and data mapping complexity increases
Solution Approach 1:
Slave EMCs provide feedback to the master EMC about their drive slot status and LED states. The master EMC uses this feedback to coordinate the overall drive slot status indication across all EMCs, ensuring consistent and accurate status representation without requiring complex direct coordination between all EMC pairs.
Data Source
AI summary
According to one aspect, a computing system having a plurality of enclosure management controllers (EMCs) is disclosed. In one embodiment, the EMCs are communicatively coupled to each other and each EMC is operatively connected to a corresponding plurality of drive slots and at least one of a plurality of drive slot status indicators. Each EMC is operative to receive enclosure management data, detect an operational status of the drive slots, and generate drive slot status data. One of the EMCs is configured to function at least partly as a master EMC to receive drive slot status data and, based on received enclosure management data and received drive slot status data, generate mapped data for each one of the EMCs for selectively activating at least one of the drive slot status indicators to indicate corresponding operational status.