Local KVM Module for Blade Server CMC Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In blade server configurations, users face difficulties in accessing and managing chassis management controllers (CMCs) due to limited I/O device connections and dynamic IP address assignment, making it hard to provide keyboard input and locate CMCs, especially when only network or serial access is available.
Innovation Solution
A local KVM module with an on-screen display interface that presents the CMC as a blade server, allowing users to establish a virtual terminal via LAN or a tiny Telnet client, enabling keyboard input and redirection to IO modules, even with DHCP-assigned IP addresses.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If remote KVM access is used to manage blade servers, then user accessibility is improved, but the ability to provide keyboard input to CMC becomes limited
Solution Approach 1:
The LKVM module acts as an intermediary device between the user and the CMC. It captures keyboard input locally and transmits it to the CMC through the existing KVM infrastructure, enabling keyboard input capability to be added without requiring direct physical connection to the CMC.
Solution Approach 2:
The LKVM module is designed to work with multiple CMCs and blade servers simultaneously. It can redirect keyboard input to different targets and supports both local and remote access modes, making it a universal solution for various management scenarios.
2Adaptability or versatility
If CMC uses DHCP-assigned IP addresses for network access, then network configuration flexibility is improved, but the ability to locate and access CMC becomes difficult
Solution Approach 1:
The LKVM module serves as a mediator that provides an alternative access path to the CMC. Instead of requiring users to locate and connect to the CMC's dynamic IP address, the LKVM module intercepts and redirects access requests, making the CMC accessible through a stable, known interface.
Solution Approach 2:
The LKVM module creates a virtual representation or copy of the CMC interface that can be accessed independently of the CMC's actual network location. This virtual interface maintains the functionality needed for management tasks while bypassing the IP address discovery issue.
3Extent of automation
If local video output is disabled for blade servers, then remote management capability is improved, but the ability to access blade for local operations becomes difficult
Solution Approach 1:
The LKVM module acts as an intermediary that captures and redirects video output from blades to the CMC interface. This allows local video display functionality to be restored through the LKVM module even when the blade's local video output is disabled, enabling hybrid remote/local management scenarios.
Data Source
AI summary
A local KVM module with an on-screen display interface in which a chassis management controller is included within a list of servers which may be accessed by the local KVM module. The local KVM module includes keyboard, mouse and video connectors as well as a tiering network connector. When accessing the local KVM module, the CMC is presented as any other blade server, but with the name Chassis Management Controller (CMC). When a user selects the CMC module from the onscreen display, the user is presented with a text console, where the user can login to a text terminal interface of the CMC module. The text interface can be implemented as for example, a serial connection via a local area network (LAN) or through a tiny telnet client via a chassis private network.