Patent Application
20160057008
1. Field of the Invention
This invention relates to a remote management system for servers, and in particular, it relates to auto re-pairing and use of virtual port number in a remote management system for servers.
2. Description of the Related Art
In a distributed computing or cloud computing system, a plurality of computers (e.g. servers or PCs) are located at one location and connected to one or more KVM (keyboard, video, mouse) switches. Remote client computers located at other locations can access the computers via the KVM switch, through a network (such as a WAN, LAN, the Internet, Intranet, Ethernet, wireless network, etc.). A local user console (monitor, keyboard and mouse) can also be connected to a console port of the KVM switch via cables. A remote client can logon to the KVM switch via the network, for example by using a web browser, and can exchange keyboard, video and mouse data with one or more of the computers connected to the KVM switch. The KVM switch has a controller connected to a network interface circuit (NIC) for handling packets containing keyboard and mouse signals received from a remote client on a network, and transmits packets containing video signals and other signals to the network via the NIC. The KVM switch implements an on-screen display (OSD) system to assist the client in communicating with the KVM switch and perform various functions such as logging on, selecting a computer to be connected to, etc.
As schematically illustrated in
On the OSD display on the client computer, the physical port numbers are used to display a list of servers available to be accessed by the client. In the example schematically shown in
The present invention is directed to a remote server management method and related apparatus that substantially obviates one or more of the problems due to limitations and disadvantages of the related art.
An object of the present invention is to provide an auto re-pairing function in the remote server management system.
Another object of the present invention is to make the user interface (OSD) more user-friendly by using virtual port number.
Additional features and advantages of the invention will be set forth in the descriptions that follow and in part will be apparent from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims thereof as well as the appended drawings.
To achieve these and other advantages and in accordance with the purpose of the present invention, as embodied and broadly described, the present invention provides a remote server management method, implemented on a remote management device, the remote management device including: a plurality of computer ports for connecting to server computers, including at least a first computer port and a second computer port; a user port for connecting to a user device; a switching circuit for selectively connecting the user port to the first or the second computer port; and a control module; where the method includes: (a) detecting a connection of a target server computer to the first computer port; (b) transmitting video data representing a desktop image of the target server computer at the first computer port to a user device via the user port; (c) automatically detecting a move of the target server from the first computer port to the second computer port; and (d) upon the detection in step (c), transmitting video data representing a desktop image of the target server computer at the second computer port to the user port, based on a correspondence between the user port and the target server computer, without receiving any request from the user device via the user port to change computer ports.
In another aspect, the invention provides a remote management device, which includes: a plurality of computer ports for connecting to server computers, including at least a first computer port and a second computer port; a user port for connecting to a user device; a switching circuit for selectively connecting the user port to the first or the second computer port; a control module; and a memory having a computer readable program code embedded therein, the program code being configured to cause the remote management device to execute a process which includes: (a) detecting a connection of a target server computer to the first computer port; (b) transmitting video data representing a desktop image of the target server computer at the first computer port to the user device via the user port; (c) automatically detecting a move of the target server computer from the first computer port to the second computer port; and (d) upon the detection in step (c), transmitting video data representing a desktop image of the target server computer at the second computer port to the user port, based on a correspondence between the user port and the target server computer, without receiving any request from the user device via the user port to change computer ports.
In another aspect, the invention provides a remote server management method, implemented on a remote management device, the remote management device including: a plurality of physical computer ports for connecting to server computers; a user port for connecting to a user device; a switching circuit for selectively connecting the user port to one of the physical computer ports; and a control module; the method including: (a) storing a system configuration table which indicates a correspondence between physical computer ports of the remote management device and server computers connected to the physical computer ports; (b) storing a correspondence between each of a plurality of server computers connected to the remote management device and a unique virtual computer port number, the virtual computer port numbers being independent of the physical computer ports that the server computers are connected to; (c) based on the correspondence between the server computers and the virtual computer port numbers, transmitting port names corresponding to the plurality of server computers and the corresponding virtual computer port numbers to a user device via the user port to be displayed to a user; (d) receiving a connection request from the user device which identifies a target virtual computer port number to be connected to; (e) determining a target server computer corresponding to the virtual computer port number using the correspondence between the server computers and the virtual computer port numbers; (f) determining a physical port which the target server computer is connected to using the system configuration table; and (g) transmitting video data representing a desktop image of the target server computer at the physical computer port determined in step (f) to the user device via the user port.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are intended to provide further explanation of the invention as claimed.
Embodiments of the present invention are designed to solve the following problems.
Sometimes, a maintenance worker in the server room where the KVM switch is located may need to change the physical computer port of a server, i.e., move the server form one port of the KVM switch to another, by unplugging the cable for the server from one port and plugging it into another port. In a normal operation the unplugging and plugging actions are done in quick successions, e.g. within a few seconds. Such operations often occur without the remote client's knowledge. In conventional KVM systems, such a port change will break the connection between the client and the server being moved, including video, keyboard, mouse and virtual media connections between the client and the server. Moreover, after such a port change, the port number of the server is changed to the new port number on the client's OSD display. For example, if the server named PC_ABC is unplugged from port 02 and plugged into port 32 (as schematically illustrated by the dashed line in
In addition, in some conventional KVM systems, the OSD provides a “my favorites” function to allow the user to selectively display some servers together in a designated area, e.g. a “favorites” folder, so that the user can more easily select them for access. In conventional systems, the “my favorites” display uses physical port numbers to identify and organize the servers. Thus, when a server is changed from one port to another port, the server may disappear from the “my favorites” list. For example, in the above example, if the server PC_ABC at port [02] was in the favorites folder, and it is changed to port [32] which was not in the favorites folder, then its name will disappear from the favorites folder after the change, even though the port [02] may still be in the favorites folder.
These problems become more difficult when multiple KVMs, often rack-mounted, are connected together, for example in a daisy-chain and/or cascading manner. In a daisy-chain connection, two KVM switches are connected to each other by a cable plugged into dedicated daisy-chain ports of the KVM switches. In a cascading connection, one KVM switch is connected to a server port of another KVM switch. Such multiple connected KVM switches for a system where each computer port of each KVM switch has a unique port number or ID within the system. Sometimes there is a need to move a server from a port of one KVM switch to a port of another KVM switch within the system, by unplugging it from one port and plugging it into the other port. For example, if one KVM switch needs to be removed or replaced, there will be a need to move the servers connected to that KVM switch to one or multiple other KVM switches, either temporarily or permanently. On the client computer's OSD display, multiple KVM switches of the system and their connected servers may be listed in a collapsible tree structure, an example of which is shown in
Moving servers to different computer ports can be a complicated operation for the maintenance workers as well. For example, when replacing a KVM switch, one or more servers may need to be moved from ports of the old KVM switch to other KVM switches temporarily, and then moved back to the replacement KVM switch once that KVM switch is installed. In conventional KVM systems, the maintenance worker needs to record both the old port numbers and the temporary port numbers, so that the cables can be re-plugged into the correct ports on the replacement KVM switch. Sometimes the maintenance worker needs to attach physical tags to the server cables to identify them.
Embodiments of the present invention provide methods and apparatus that solve the above problems.
As required, a detailed illustrative embodiment of the present invention is disclosed herein. However, techniques, systems, operating structures and methods in accordance with the present invention may be embodied in a wide variety of forms and modes, some of which may be quite different from those in the disclosed embodiment. Consequently, the specific structural and functional details disclosed herein are merely representative, yet in that regard, they are deemed to afford the best embodiment for purposes of disclosure and to provide a basis for the claims herein, which define the scope of the present invention. The following presents a detailed description of the preferred embodiment (as well as some alternative embodiments) of the present invention.
According to an embodiment of the present invention, schematically illustrated in
Each dongle 30 contains a circuit and memory. Within the KVM switch system, each dongle 30 has a unique dongle ID (also referred to as adapter ID or computer interface module ID) stored in its circuit or memory, and each dongle is always connected to the same server computer 20 during normal operation and maintenance. This way, the dongle IDs are uniquely correlated with the respective server computers and can be used to uniquely identify the server computers. A reason that dongle IDs are used to identify the servers, rather than directly using an inherent unique ID of the server to identify the servers, is that the dongle IDs can be assigned by system administrators of the KVM switch system. The KVM switch 10 maintains a dongle-to-server correspondence table that indicates the one-to-one fixed correspondence between the dongle IDs and the server names or IDs. Of course, the dongles for the servers can be changed by the system administrator, in which case the dongle-to-server correspondence table will be updated, e.g. manually by the system administrator.
The KVM switch 10 also stores a system configuration table that records the current connection of dingle IDs to the computer ports, i.e., which dongle ID is connected to which computer port. This system configuration table is automatically updated by the KVM switch as will be described in more detail later.
The KVM switch 10 is connected to a network via a network interface circuit (NIC), and one or more client computers 40 can communicate with the KVM switch via the network, for example by using a browser program. Each client is assigned a network (LAN) port number by the KVM switch 10, and the switching circuit 11 of the KVM switch transmits signals between each network port and a selected computer port. The network ports are virtual ports by which client computers communicate with the KVM switch.
A local user console (monitor, keyboard and mouse) can also be connected to one or more console ports 15 of the KVM switch 10 via cables. Each console port is assigned a console port number. The embodiments described below focus on the communication between the KVM switch and a client computer located at a network port, but the methods applies equally to communications between the KVM switch 10 and a user console located a console port. More generally, as used in the appended claims, the term “user port” generally refers to either a network ports or a console port, and the term “user device” generally refers to either a client computer or a user console, as the case may be.
In a conventional KVM switch system, the KVM switch maintains a connection table which indicates a correspondence between the network ports and the computer ports, i.e., which network port is communicating with which computer port. This correspondence is established when a client computer, at the beginning of a connection session, selects a server (located at a particular computer port number) to be connected to. Thus, when the server is unplugged from the computer port, the connection between the client and the server is broken because the server is no longer present at that computer port.
In embodiments of the present invention, the KVM switch 10 maintains a network port connection table which indicates a correspondence between the network ports and the dongle IDs for the corresponding servers that the network ports are currently connected to, as well as the computer ports for the corresponding servers, as schematically illustrated in
A method executed by the KVM switch 10 according to embodiments of the present invention is described with reference to
The KVM switch 10 then transmits data between the network port of the client and the currently selected computer port, so that the client is connected to and exchanges data with the selected server (step S53). This may include, for example, transmitting video data representing a desktop image of the selected server to the client, and transmitting keyboard and/or mouse data from the client to the selected server. In the instant embodiments, the video data representing the desktop images originate from the servers and are processed by the KVM switch, such as A-to-D conversion, encoding and/or compression, before being transmitted to the client. Audio data and other data may also be transmitted between the server and the client and they may be processed by the KVM switch as well.
The KVM switch 10 continuously monitors the presence of the dongles (which indicates the presence of the server computers) on the various computer ports (step S54). For example, this can be done by polling the dongles periodically (e.g. every few seconds), and obtaining the dongle IDs in response. Steps S55 to S58 occur when a server (e.g. server “PC_ABC” depicted in the example shown in
When the selected server along with its dongle is unplugged from the currently selected computer port, the KVM switch 10 detects the absence of the selected dongle ID from the currently selected computer port (step S55). At this time, the KVM switch 10 continues to monitor all computer ports to detect whether the selected dongle ID is subsequently connected to another computer port (step S56). This is done by detecting a connection event at another computer port, and obtaining the dongle ID of the connected dongle to determine whether it matches the selected dongle ID (D02 in this example) that was previously unplugged from the currently selected computer port (port 02 in this example). When the KVM switch 10 detects that the selected dongle ID is now connected to the new computer port, the KVM switch updates the system configuration table to indicate the dongle ID is now connected to the new computer port (step S57). If the network port connection table has a column for the computer port numbers, the KVM switch also updates the network port connection table to indicate that for this network port, the currently selected computer port is replaced by the new computer port number (32 in this example) (step S57). This is schematically illustrated in
From this point on, the KVM switch will transmit data between the network port (C02 in this example) and the new computer port (port 32 in this example) (step S58), so that the client continues to be connected to and exchanges data with the selected server (PC_ABC in this example), now via the new computer port (32 in this example). Thus, by steps S55 to S58, the KVM switch 10 automatically re-pairs the client computer (at the network port) with the selected server via the new computer port, without requiring the client computer to look up the new computer port for the selected server and perform another connection request.
If the selected server is unplugged from the currently selected computer port without being subsequently plugged into another computer port with the predetermined time period, the server is considered to have been disconnected, and the KVM switch 10 will update the network port connection table to remove the currently selected computer port number from the entry of the network port without replacing it with another computer port number. The KVM switch will also update the system configuration table to indicate that the server (identified by the dongle ID) is no longer connected to the system. The predetermined time period may be set by the system administrator.
It should be noted that the re-paring steps S55 to S58 are performed only when a dongle ID that has disappeared form a computer port is one that is currently connected to a network port and being accessed by a client.
When the client switches connection to a different server, steps S51 to S53 are performed to connect the client to the new server, so that the network port connection table is updated.
When the client logs out of the KVM switch, the network port connection table is updated to indicate that the network port in question is no longer associated with any dongle ID.
In the process shown in
In some KVM switch systems, different media channels of the same client computer, such as video (desktop image), audio, virtual media (e.g., a USB storage devices connected to the client computer), can be connected to different servers at the same time and can be independently switched. For example, the client may transfer data between a USB storage device connected to the client and a first server, while at the same time exchanging video, keyboard and mouse data with a second server. Methods of implementing such connections are known in the art and are not described in detail here. The above-described auto re-paring method can be applied in such systems, by treating each media channel of the client as an independent network port.
As mentioned earlier, in some KVM switch systems, multiple KVM switches are connected together in a daisy-chain and/or cascading manner. Each computer port of the KVM switch system has a unique port number or ID. The client computer logs on to one of the KVM switches, sometimes referred to as the master, and can be connected to any computer port of the KVM switch system. Methods of implementing such a KVM system are known in the art and are not described in detail here. The above-described auto re-paring method can be applied in such systems, using the unique computer port numbers. The steps in the method of
In the KVM system of
The above described auto re-paring processes can also be applied to the communication between the KVM switch and a video session recording (VSR) device. In some KVM switch systems, the KVM switch transmits a copy of the video data (desktop images) associated with each server to the VSR device to be recorded. The VSR may be connected to the KVM switch via the network. When applying the auto re-paring method, the VSR device can be treated in a similar way as a client on a network port (in fact it may be referred to as a client). As a result, when a server is moved from one physical computer port to another, the video data from that server can continue to be recorded by the VSR as the same connection session between the client and the server.
An advantage of the auto re-paring method described above is that when a maintenance worker moves a server computer from one computer port to another within the KVM system, by unplugging the cable of the server from one computer port and then quickly re-plugging it into another computer port, the KVM switch keeps track of the computer port number of the server, and automatically re-establish connection between the network port and the same server now located at the new computer port. The client does not need to search for the new computer port number and re-request connection with it. This method is also advantageous when a maintenance worker accidentally unplugs a server cable, but quickly realizes the mistake and plugs it back into the same computer port.
According to another embodiment of the present invention, virtual computer port numbers are used to facilitate easier navigation for users.
As described earlier, in a conventional KVM system, on the OSD displayed on the client computer, the server computers are organized by the computer port numbers, as shown in
Based on the received server name and (virtual) computer port numbers, the client displays a list of servers on its OSD (step S62). In this OSD display, the servers are ordered by the computer port numbers as in conventional OSDs, so the appearance of the OSD display may be similar to that shown in
Based on the receive connection request, the KVM switch obtains the physical computer port number for the selected server (step S74). This is done by referring to the user's server-to-virtual-computer-port-number association table (if the connection request only specifies the virtual computer port number), as well as the system configuration table maintained by the KVM switch that indicates which server (by dongle ID) is connected to which physical computer port. The KVM switch can now establish a connection between the client (the network port of the client) and the physical computer port that the selected server is plugged into. Step S74 also includes updating the network port connection table (
The client can now exchange data with the selected server via the KVM switch (steps S64, S75). This may include, for example, transmitting video data representing a desktop image from the selected server to the client, and transmitting keyboard and/or mouse data from the client to the selected server. Audio data and other data may also be transmitted. During the connected session, the KVM switch monitors the presence of dongle IDs on the physical computer ports. If the selected server is moved from one physical computer port to another, the KVM server performs the auto re-paring steps (i.e. steps S55 to S58 in
In the process shown in
Because the server-to-virtual-computer-port-number association does not change when the servers are moved on the physical computer ports, the OSD display on the client are always the same for the same user, unless the user or the system administrator changes the user's customized server-to-virtual-computer-port-number association table. Thus, for example, if some servers are moved around on the KVM switch system when the user is logged off, when he logs back on, the list of servers and their (virtual) computer port numbers will appear on the OSD the same way as before. This OSD display method is more user-friendly because the order of servers, and therefore the visual appearance of the OSD page that list the servers, will remain constant for each user. Further, when the user makes a “favorites” folder, the servers listed in the favorite folder, along with their (virtual) computer port numbers, will not change when a server is moved from one physical computer port to another.
Optionally, the OSD may provide an option for the user to choose to use either the virtual computer port number of the physical computer port number in the OSD display.
In summary, in embodiments of the present invention, by using the automatic re-paring process and the virtual computer port numbers, when a server is moved from one physical computer port to another with the KVM switch system, the connection between the moved server and the client it was connected will be automatically re-established, and the list of servers on the client's OSD including the favorite folder remains unchanged. As a result, the maintenance operation performed at the server room will be transparent to the client.
The above-described process steps of the KVM switch 10 may be implemented by computer programs (software or firmware) stored in a memory 13 of the KVM switch and executed by a control module 12 such as a microprocessor. The control module 12 also controls the switching circuit 11 for switching the data between network ports and server ports. The process steps may also be implemented in logic circuits of the KVM switch. More generally, the KVM switch may be any suitable remote management device.
It will be apparent to those skilled in the art that various modification and variations can be made in the remote server management method and related apparatus of the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention cover modifications and variations that come within the scope of the appended claims and their equivalents.
