IKVM Network Management via Multi-Control Center Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional IP-based KVM systems restrict client access to IKVM switches and remote computers, requiring clients to log on to specific control centers connected to the same router, limiting access to devices across different subnets.
Innovation Solution
Implementing a network structure with multiple control center servers that allow clients to access all IKVM switches within the system by storing and sharing system configuration information, enabling communication between clients and IKVM switches managed by different control centers, and establishing a master-slave structure for redundancy and configuration management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If clients log on to specific control centers connected to the same router, then access to local IKVM switches is enabled, but access to IKVM switches on different subnets is restricted
Solution Approach 1:
The patent introduces a gateway server as an intermediary component that mediates between clients on different subnets and IKVM switches. The gateway server receives access requests from clients, forwards them to the appropriate control centers, and relays responses back, enabling cross-subnet access without requiring direct connectivity between clients and all control centers
Solution Approach 2:
The gateway server is designed with multi-functionality to handle various operations including receiving access requests, identifying target IKVM switches, communicating with multiple control centers, and managing sessions across different subnets. This universal component enables the system to access IKVM switches regardless of which subnet they are located on
2Speed
If multiple control centers manage different subnets, then local access is efficient, but centralized management of all IKVM switches becomes complex
Solution Approach 1:
The system is segmented into multiple control centers, each managing a specific subnet or group of IKVM switches locally. This segmentation allows fast local access while the gateway server provides a unified access point. The segmentation is further applied to the gateway server's operation, which segments the access management by routing requests to appropriate control centers based on target device location
Solution Approach 2:
The gateway server acts as an intermediary layer between clients and multiple control centers, simplifying the management architecture. Instead of clients needing to know which control center manages which devices, the gateway server automatically routes requests, reducing the complexity of centralized management while preserving local access efficiency
3Ease of operation
If a single control center manages all IKVM switches, then centralized control is achieved, but network performance and reliability decrease
Solution Approach 1:
The control function is segmented across multiple control centers, each responsible for managing specific IKVM switches or subnets. This distribution of control responsibilities maintains centralized management through the gateway server while improving reliability by eliminating single points of failure. If one control center fails, others continue to operate independently
Solution Approach 2:
The system changes the architectural parameter from a single control center to multiple control centers, fundamentally altering the system's reliability characteristics. This parameter change transforms the system from having a single point of failure to having redundant control nodes, thereby improving overall reliability while maintaining centralized coordination through the gateway server
Data Source
AI summary
An IP-based KVM (IKVM) switch system includes a plurality of control centers connected by a network via respective routers. A group of IKVM switches is connected to each router. Each IKVM switch is connected to a plurality of remote computers. Each control center stores system configuration information regarding all other control centers, including their IP addresses, port information, information about the IKVM switches managed by them, and (optionally) the remote computers connected to each IKVM switch. The control centers use a master-slave scheme to share the configuration information among them. When a client logs on to any control center, all IKVM in the system are displayed on a UI so that the client can select any IKVM or (optionally) remote computer for access. The control centers perform necessary functions to facilitate the access to the select IKVM or remote computer by the client.