Reverse Order Rebooting for Chained I/O Module Firmware Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing method of updating firmware in daisy-chained input/output modules (IOMs) is time-consuming due to the serial rebooting process, which causes delays as each IOM is rebooted in a specific order, leading to increased processing time as the number of storage drives and IOMs increases.
Innovation Solution
The firmware flashing process is optimized by loading the updated firmware image into all IOMs before rebooting, and then rebooting them in reverse order, starting from the last IOM in the chain, allowing upstream IOMs to send commands while downstream IOMs are rebooting, thus reducing overall update time.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If IOMs are rebooted in serial order according to the daisy chain processing order, then firmware updates are applied systematically, but the total update time increases significantly with more IOMs
Solution Approach 1:
The patent inverts the traditional serial rebooting order by implementing parallel rebooting of multiple IOMs simultaneously. Instead of rebooting IOMs one by one in chain order (IOM1, then IOM2, then IOM3), the system reboots multiple IOMs in parallel after loading firmware, reducing total update time while maintaining update reliability through controlled parallel execution.
Solution Approach 2:
The patent applies preliminary action by loading firmware images into all target IOMs before initiating any reboots. The firmware is pre-loaded into memory of each IOM while they remain operational, so that when reboots occur in parallel, each IOM immediately executes the new firmware without additional delays for firmware transfer during the reboot process.
2Productivity
If multiple IOMs are updated simultaneously, then update time is reduced, but system complexity and coordination overhead increase
Solution Approach 1:
The patent segments the firmware update process into distinct phases: firmware selection and validation, parallel firmware loading into target IOMs, coordinated parallel rebooting, and post-update verification. This segmentation allows simultaneous execution of independent loading operations while maintaining controlled coordination through defined phase transitions, reducing overall complexity despite parallel operations.
Solution Approach 2:
The host system acts as an intermediary that coordinates the parallel firmware updates. The host manages firmware image distribution to multiple IOMs, triggers synchronized reboots, and verifies update completion. This central intermediary simplifies coordination complexity by providing a single point of control rather than requiring complex peer-to-peer coordination between IOMs.
3Loss of time
If IOMs are rebooted in reverse order from the daisy chain, then upstream IOMs can continue sending commands during downstream IOM reboots, but the processing order constraint is violated
Solution Approach 1:
The patent introduces dynamics by allowing the IOM chain to operate in two distinct states: during firmware loading, IOMs remain operational in their original processing order; during the update phase, the chain transitions to a parallel reboot state where order constraints are temporarily suspended. This dynamic state transition enables time optimization without permanently violating the stable processing order required for normal operations.
Data Source
AI summary
A technique includes communicating with a plurality of input/output (I/O) modules to cause a firmware image to be transferred to the I/O modules. The I/O modules are each associated with the plurality of storage device enclosures, and the I/O modules are serially coupled together in a chain establishing a processing order among the I/O modules. The technique includes rebooting the I/O modules to cause the I/O modules to use the communicated firmware images, where the rebooting includes rebooting the I/O modules in a second order counter to the processing order.