SAS Expander Autonomous Domain Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Serial Attached SCSI (SAS) domain discovery processes do not ensure that detected devices are fully functional, leading to resource-intensive testing by host systems to verify operational status, which is not triggered by all relevant events in the domain.
Innovation Solution
A SAS expander is enhanced to sense changes in the SAS domain topology and configuration, initiating testing of SAS components to determine their operational status, using non-destructive commands like Test Unit Ready, Inquiry, and Read, and notifying the SAS initiator device of component functionality without relying on the host system for testing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the host system performs testing to verify operational status of SAS components, then reliability of device detection is improved, but productivity of the host system deteriorates due to resource-intensive testing
Solution Approach 1:
The patent extracts the testing function from the host system and relocates it to the SAS expander. The expander independently performs operational status verification of SAS components through non-destructive commands, separating this resource-intensive task from the host system while maintaining verification reliability.
Solution Approach 2:
The SAS expander serves itself by autonomously monitoring and testing SAS components without requiring host system intervention. The expander detects changes in the SAS domain, initiates appropriate testing sequences, and manages component verification independently, making the system self-sufficient for operational status monitoring.
2Loss of information
If the discovery process detects all SAS components, then completeness of domain mapping is improved, but reliability of functional verification deteriorates because presence detection does not ensure proper functioning
Solution Approach 1:
The patent applies preliminary action by performing operational status testing immediately when changes are detected in the SAS domain. Rather than waiting for host system intervention, the expander proactively tests components upon discovering changes, ensuring functional verification is performed before the components are fully utilized.
Solution Approach 2:
The expander implements feedback by continuously monitoring the SAS domain for changes and responding with appropriate testing actions. When a component is detected or a change occurs, the expander feeds back operational status information to the host system, creating a closed-loop verification system that ensures both completeness and reliability.
3Use of energy by moving object
If testing is performed only when host system launches a process, then device resource consumption is reduced, but speed of response to domain changes deteriorates because testing is not triggered by all relevant events
Solution Approach 1:
The expander implements feedback by continuously monitoring the SAS domain for changes and responding with appropriate testing actions. When a component is detected or a change occurs, the expander feeds back operational status information to the host system, creating a closed-loop verification system that ensures both completeness and reliability.
Solution Approach 2:
The SAS expander serves itself by autonomously monitoring and testing SAS components without requiring host system intervention. The expander detects changes in the SAS domain, initiates appropriate testing sequences, and manages component verification independently, making the system self-sufficient for operational status monitoring.
Data Source
AI summary
Methods and structures within a SAS expander for testing SAS devices and other SAS expanders in the SAS domain. Testing devices and expanders in the domain by operations performed within a SAS expander in the domain relieves the burden of such processing in attached host systems and adds flexibility for scheduling processing for test operation of devices and expanders in the domain. In one aspect hereof, the testing may be performed by a master SAS expander configured in the domain. The SAS expander may initiate testing of devices following completion of the SAS discovery process. Testing may also be initiated in response to events in the SAS domain not typically detected by attached host systems.