SAS Controller Port Configuration Persistence
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
SAS controllers require manual configuration of PHYs, which is time-consuming and prone to human error, and existing automatic configuration solutions disrupt connections when SAS devices reconnect, leading to inconsistent port configurations and potential conflicts.
Innovation Solution
An SAS controller with a processing unit and non-volatile memory that retains PHY configuration information, automatically reconfigures ports upon device reconnection, and compares configuration data to prevent conflicts, ensuring consistent port settings across reboots and power cycles.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If automatic configuration functionality is implemented in SAS controllers, then the time and labor required for manual configuration is eliminated, but port configurations are disrupted when SAS devices reconnect after power cycles or reboots
Solution Approach 1:
The SAS controller performs preliminary actions by detecting device disconnection events (power cycles, reboots, resets) and proactively preserving the port configuration data in non-volatile memory before the device reconnects. This preliminary preservation action ensures that when the device reconnects, the configuration data is already available and intact, eliminating the need to re-establish connections or reconfigure ports, thus maintaining both high productivity and configuration consistency.
2Reliability
If port configurations are deactivated when SAS devices disconnect, then error conditions from attempting to access disconnected devices are prevented, but the SAS device cannot be reconnected to the same port after reboots or power cycles
Solution Approach 1:
The patent extracts the port configuration data (SAS addresses, port associations, PHY mappings) from volatile memory and stores it separately in non-volatile memory when a device disconnects. This extraction separates the configuration data from the active connection state, allowing the controller to clear volatile memory to prevent error conditions while preserving the extracted configuration data for future reconnection, thus achieving both error prevention and reconnection capability.
Solution Approach 2:
Non-volatile memory serves as an intermediary between the disconnected device state and the reconnection state. It holds the configuration data during the disconnection period, acting as a mediator that preserves the logical connection information even when the physical connection is broken. This intermediary storage allows the system to prevent errors from accessing disconnected devices while maintaining the ability to restore connections through the preserved configuration data.
3Manufacturing precision
If manual configuration of PHYs is performed, then precise control over port settings is achieved, but the setup process becomes time-consuming and laborious
Solution Approach 1:
The SAS controller implements self-service functionality by automatically detecting device disconnections, preserving configuration data in non-volatile memory, and restoring configurations upon reconnection without requiring human intervention. The system serves itself by monitoring its own state changes and autonomously managing the configuration persistence, eliminating the time-consuming manual reconfiguration process while maintaining precise configuration control through the preserved data.
Data Source
AI summary
An apparatus and method are disclosed for maintaining consistent port and PHY configuration information in an SAS controller when connected SAS devices are rebooted, reset or otherwise temporarily disconnected. Configuration information is stored in non-volatile memory, and restored by a methodology to prevent port conflicts.