I/O Engine Synchronizes Management Domains in MCM Groups
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In information handling systems, the formation of Multi-Chassis Management (MCM) groups results in different network management domains for each modular computing system, leading to separate management access points within the system management domain, which complicates management and scaling.
Innovation Solution
An Information Handling System (IHS) with a processing system and memory that provides an I/O engine to synchronize system management domains and network management domains by joining a network management domain based on an MCM group identifier, allowing I/O modules to switch between network management domains within a system management domain.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If modular computing systems form MCM groups with separate network management domains, then each system maintains independent network management control, but multiple separate management access points are created within the system management domain
Solution Approach 1:
The patent merges multiple separate network management domains into a single unified network management domain. When an MCM group is formed, I/O modules from member computing systems join the network management domain of the lead computing system, consolidating multiple management access points into one unified access point while maintaining independent control capabilities.
Solution Approach 2:
The patent enables I/O modules to function in multiple contexts - they can operate within their native computing system's network management domain or join the lead computing system's network management domain. This multi-functionality allows the same I/O module to participate in different network management domains as needed, providing universal management access.
2Reliability
If each modular computing system maintains its own network management domain, then network management independence is preserved, but scalability of the system management domain is limited
Solution Approach 1:
The patent introduces dynamic behavior where I/O modules can transition between different network management domains based on MCM group formation. When a computing system joins an MCM group, its I/O modules dynamically join the lead system's network management domain, enabling the system to scale while maintaining management independence through optional participation.
Solution Approach 2:
The patent segments the network management domain participation into optional components - I/O modules can choose to join the lead system's domain or remain in their native domain. This segmentation allows selective integration that preserves independence while enabling scalability through gradual incorporation of modules into the unified domain.
3Adaptability or versatility
If separate network management domains are maintained for each computing system, then individual system autonomy is preserved, but unified management of physical resources becomes complex
Solution Approach 1:
The patent introduces the lead computing system's network management domain as an intermediary that facilitates unified management. I/O modules from member systems join this intermediary domain, which provides a common management interface while maintaining connections to individual system autonomies, thereby simplifying unified resource management without sacrificing individual autonomy.
Solution Approach 2:
The patent merges multiple autonomous network management domains into a single unified domain accessible through one management access point. This consolidation maintains individual system autonomy through logical separation while providing unified management capabilities through physical consolidation, making resource management easier without sacrificing adaptability.
Data Source
AI summary
A system/network management domain synchronization system includes a first computing system that belongs to a first MCM group and that includes a first computing system I/O module that belongs to a first network management domain, and a second computing system that is coupled to the first computing system. The second computing system includes a second computing system management module that joins the first MCM group and, in response, broadcasts a first announcement that includes a first MCM group identifier for the first MCM group. The second computing system also includes a second computing system I/O module that receives the first announcement, determines that the second computing system management module is included in the second computing system with the second computing system I/O module and, n response, joins the first network management domain.


