Method and device for managing out-of-band equipment, electronic device, storage medium

Abstract

The application discloses a kind of management method and management device of out-of-band equipment, electronic equipment, storage medium, it is related to big data technical field, the method includes: receiving the account management instruction transmitted by network server, at least carry with in account management instruction: equipment identification and account operation instruction, account operation instruction at least includes: user account information and account management operation;Response account management instruction, inquires target out-of-band equipment indicated by equipment identification;Account operation instruction is sent to target out-of-band equipment, wherein, target out-of-band equipment executes account management operation to the user account indicated by user account information, obtains account management result and account update information;Account management result returned by target out-of-band equipment is transmitted to network server, and account update information is transmitted to database.The application solves the technical problem that a large number of physical machines in computer room are managed by equipment management personnel in the related art, and the management difficulty is great.

Description

Technical Field

[0001] This invention relates to the field of big data technology, and more specifically, to a management method and device for out-of-band devices, an electronic device, and a storage medium. Background Technology

[0002] Currently, massive amounts of data require storage through numerous servers / physical machines. As data volumes increase, servers often need to be placed separately in different data center rooms. However, managing the large number and diverse types of physical machines in data centers is inconvenient. Existing management methods require designated personnel to manage the equipment using user accounts and passwords. This manual management approach is not only difficult to control but also tedious and prone to oversights, potentially leading to machine damage.

[0003] There is currently no effective solution to the above problems. Summary of the Invention

[0004] This invention provides a method, device, electronic equipment, and storage medium for managing out-of-band devices, thereby addressing the technical problem in related technologies where managing a large number of physical machines in a computer room by device management personnel is difficult.

[0005] According to one aspect of the present invention, a method for managing out-of-band devices is provided, applied to an out-of-band proxy server, wherein the out-of-band proxy server has a pre-established connection with a network server, comprising: receiving an account management instruction transmitted by the network server, wherein the account management instruction carries at least: a device identifier and an account operation instruction, wherein the account operation instruction includes at least: user account information and an account management operation; responding to the account management instruction, querying a target out-of-band device indicated by the device identifier; sending the account operation instruction to the target out-of-band device, wherein the target out-of-band device performs the account management operation on the user account indicated by the user account information to obtain an account management result and account update information; transmitting the account management result returned by the target out-of-band device to the network server, and transmitting the account update information to a database, wherein the database has a pre-established network connection with the network server.

[0006] Optionally, before receiving the account management instruction transmitted by the network server, the method further includes: the network server receiving account management operations, device information, and user information sent by the front end; the network server determining the device identifier and device address of the target out-of-band device to be managed based on the device information; the network server determining the user account information based on the user information, wherein the user account information includes at least: the user account's operation permissions; and the network server generating the account management instruction based on the account management operation, the user account information, the device identifier, and the device address, provided that the user account's operation permissions indicate that the operator has the operation permission to perform the account management operation.

[0007] Optionally, before the network server receives the management operation, device information, and user information sent by the front end, the method further includes: the front end displaying a user login page; the front end receiving the user information entered through the user login page; the front end receiving a device management instruction; the front end responding to the device management instruction and displaying a device management page, wherein the device management page includes a virtual box associated with device management and account management; and the front end receiving operation information from an external device on the device management page to obtain the account management operation and the device information.

[0008] Optionally, before receiving the account management instruction transmitted by the network server, the method further includes: the network server receiving a device management policy input from the front end, wherein the device management policy is one of the following: a partial takeover policy, a full takeover policy, and a non-takeover policy; the partial takeover policy indicates that the user account's password is randomly generated and can be controlled by the operation and maintenance user; the full takeover policy indicates that the user account's password is randomly generated and cannot be controlled by the operation and maintenance user; the non-takeover policy indicates that the user account's password is controlled by the operation and maintenance user and cannot be modified; and based on the device management policy, determining the user account's operation permissions, wherein the operation permissions are used to determine whether the account management operation can be performed.

[0009] Optionally, before receiving the account management instruction transmitted by the network server, the method further includes: the network server receiving a list management instruction input by the front end; the network server responding to the list management instruction retrieving device information and historical operation information of all out-of-band devices from the database to obtain a device operation list; and transmitting the device operation list to the front end.

[0010] Optionally, the out-of-band proxy server, the network server, and the database are deployed in the target open platform, and multiple application systems of the target open platform share user accounts.

[0011] Optionally, the account management operation includes at least one of the following: modifying the account password, extracting the account information of the user account, and extracting the device information of the out-of-band device to which the user account belongs.

[0012] According to another aspect of the present invention, an out-of-band device management apparatus is also provided, applied to an out-of-band proxy server, wherein the out-of-band proxy server has a pre-established connection with a network server, comprising: a receiving unit, configured to receive an account management instruction transmitted by the network server, wherein the account management instruction carries at least: a device identifier and an account operation instruction, wherein the account operation instruction includes at least: user account information and an account management operation; a querying unit, configured to respond to the account management instruction and query a target out-of-band device indicated by the device identifier; a sending unit, configured to send the account operation instruction to the target out-of-band device, wherein the target out-of-band device performs the account management operation on the user account indicated by the user account information to obtain an account management result and account update information; and a transmission unit, configured to transmit the account management result returned by the target out-of-band device to the network server and transmit the account update information to a database, wherein the database has a pre-established network connection with the network server.

[0013] Optionally, the out-of-band device management device further includes: a first receiving module, used for the network server to receive account management operations, device information, and user information sent by the front end before receiving the account management instruction transmitted by the network server; a first determining module, used for the network server to determine the device identifier and device address of the target out-of-band device to be managed based on the device information; a second determining module, used for the network server to determine the user account information based on the user information, wherein the user account information includes at least: the user account's operation permissions; and a first generating module, used for the network server to generate the account management instruction based on the account management operation, the user account information, the device identifier, and the device address when the user account's operation permissions indicate that the operator has the operation permission to perform the account management operation.

[0014] Optionally, the management device for out-of-band devices further includes: a first display module, used to display a user login page on the front end before the network server receives the management operation, device information, and user information sent by the front end; a second receiving module, used to receive the user information entered through the user login page on the front end; a third receiving module, used to receive device management instructions on the front end; a second display module, used to display a device management page on the front end in response to the device management instructions, wherein the device management page includes a virtual frame associated with device management and account management; and a third receiving module, used to receive operation information from external devices on the device management page on the front end, thereby obtaining the account management operation and the device information.

[0015] Optionally, the out-of-band device management device further includes: a fourth receiving module, configured to receive a device management policy input by the front end before receiving the account management instruction transmitted by the network server, wherein the device management policy is one of the following: a partial takeover policy, a full takeover policy, and a non-takeover policy, wherein the partial takeover policy indicates that the user account's password is randomly generated and can be controlled by the operation and maintenance user; the full takeover policy indicates that the user account's password is randomly generated and cannot be controlled by the operation and maintenance user; and the non-takeover policy indicates that the user account's password is controlled by the operation and maintenance user and cannot be modified; and a third determining module, configured to determine the user account's operation permissions based on the device management policy, wherein the operation permissions are used to determine whether the account management operation can be performed.

[0016] Optionally, the out-of-band device management device further includes: a fifth receiving module, used for the network server to receive a list management instruction input by the front end before receiving the account management instruction transmitted by the network server; a retrieval module, used for the network server to retrieve device information and historical operation information of all out-of-band devices from the database in response to the list management instruction, and obtain a device operation list; and a transmission module, used to transmit the device operation list to the front end.

[0017] Optionally, the out-of-band proxy server, the network server, and the database are deployed in the target open platform, and multiple application systems of the target open platform share user accounts.

[0018] Optionally, the account management operation includes at least one of the following: modifying the account password, extracting the account information of the user account, and extracting the device information of the out-of-band device to which the user account belongs.

[0019] According to another aspect of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored computer program, wherein, when the computer program is executed, it controls the device where the computer-readable storage medium is located to perform the out-of-band device management method described in any one of the above embodiments.

[0020] According to another aspect of the present invention, an electronic device is also provided, including one or more processors and a memory, the memory being used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors cause the one or more processors to implement the out-of-band device management method described in any of the preceding embodiments.

[0021] In this invention, an account management instruction transmitted from a network server is received. The account management instruction carries at least a device identifier and an account operation instruction. The account operation instruction includes at least user account information and an account management operation. In response to the account management instruction, a target out-of-band device indicated by the device identifier is queried, and the account operation instruction is sent to the target out-of-band device. The target out-of-band device performs an account management operation on the user account indicated by the user account information, obtains an account management result and account update information, transmits the account management result returned by the target out-of-band device to the network server, and transmits the account update information to the database.

[0022] This invention can manage various out-of-band devices through an out-of-band proxy server, automatically complete the account management of out-of-band devices, avoid the uncontrollable impact caused by bypassing the login operation device server, reduce the management difficulty, and thus solve the technical problem of the high management difficulty of managing a large number of physical machines in the data center by device management personnel in related technologies.

[0023] This invention provides a management scheme and login process for out-of-band devices, enabling account management for all out-of-band devices. From device management and security policy configuration to single sign-on and access control, it can be extended to various compatible out-of-band devices.

[0024] This invention manages out-of-band devices through front-end automation, ensuring the high efficiency of out-of-band device management. Attached Figure Description

[0025] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:

[0026] Figure 1 This is a flowchart of an optional out-of-band device management method according to an embodiment of the present invention;

[0027] Figure 2This is a schematic diagram of an optional out-of-band device management system according to an embodiment of the present invention;

[0028] Figure 3 This is a schematic diagram of an optional out-of-band device management device according to an embodiment of the present invention;

[0029] Figure 4 This is a hardware structure block diagram of an electronic device (or mobile device) according to an embodiment of the present invention, which describes a method for managing out-of-band devices. Detailed Implementation

[0030] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0031] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0032] To facilitate understanding of the present invention by those skilled in the art, some terms or nouns involved in the various embodiments are explained below:

[0033] A Configuration Management Database (CMDB) is a logical database that contains information about the entire lifecycle of configuration items and the relationships between them, as well as various configuration information stored on the device.

[0034] J2EE, short for Java 2 Platform Enterprise Edition, is an enterprise-level distributed application development specification.

[0035] It should be noted that the management method and apparatus for out-of-band devices in this disclosure can be used in the big data field when out-of-band devices are managed through an open platform, and can also be used in any field other than the big data field when out-of-band devices are managed through an open platform. This disclosure does not limit the application field of the management method and apparatus for out-of-band devices.

[0036] It should be noted that all information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for display, data used for analysis, etc.) involved in this disclosure are information and data authorized by the user or fully authorized by all parties. For example, this system has an interface with relevant users or organizations. Before obtaining relevant information, it is necessary to send an acquisition request to the aforementioned user or organization through the interface, and obtain the relevant information after receiving consent information from the aforementioned user or organization.

[0037] The following embodiments of this application can be applied to various systems / software / platforms that manage out-of-band devices, enabling the management of all device users in the management center and avoiding uncontrollable impacts caused by bypassing the login operation device server.

[0038] This application proposes a scheme for managing out-of-band devices. Device address, account, IP, and user information are parameterized and configured through a front-end page. The front-end sends management commands to the out-of-band device (or an out-of-band server) to extract and change accounts. The out-of-band device manages the corresponding account configured on the front-end, transmitting information to an out-of-band proxy server (or an out-of-band management server). The out-of-band proxy server pushes the information to the front-end page, where the front-end records and stores user passwords and other information in the application database. After management, the user has no control over the out-of-band device password and must log in to the application's front-end for single sign-on.

[0039] The proposed out-of-band device management solution allows users to periodically or manually change their original passwords according to the password rules configured in the security policy. User management can be based on three strategies: partial control (passwords are randomly generated, and the user's password is controlled by the maintenance user), full control (passwords are randomly generated, and the user's password is not controlled by the maintenance user), and no control (the user's password is controlled by the maintenance user, and no password change is performed). Maintenance users log in to the out-of-band device via a front-end page by entering their IP address and user information. The front-end allows configuration of security management policies to control and audit user commands. For example, low-privilege users can only perform read operations and cannot perform write operations. If a user performs an abnormal operation, the access control module will intervene, promptly alert the user to the risk, and stop the dangerous behavior. All operations are recorded in the database and can be viewed in audit reports.

[0040] This application supports out-of-band device management protocols and is applicable to various mainstream central devices.

[0041] This application enables the management of out-of-band devices on the open platform, filling the long-standing gap in data center device management.

[0042] This application provides a complete set of out-of-band device management and login processes, from out-of-band device management and security policy configuration to single sign-on and access control, which can be extended to various compatible out-of-band devices / out-of-band servers.

[0043] This application manages out-of-band devices through front-end automation, ensuring the high efficiency of out-of-band device management.

[0044] The present application will now be described in detail with reference to various embodiments.

[0045] Example 1

[0046] According to an embodiment of the present invention, an embodiment of a management method for out-of-band devices is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0047] In one aspect, the present invention provides a method for managing out-of-band devices, applied to an out-of-band proxy server, wherein the out-of-band proxy server and a network server have a pre-established connection relationship.

[0048] Figure 1 This is a flowchart of an optional out-of-band device management method according to an embodiment of the present invention, such as... Figure 1 As shown, the method includes the following steps:

[0049] Step S101: Receive account management instructions transmitted from the network server. The account management instructions carry at least: device identifier and account operation instructions. The account operation instructions include at least: user account information and account management operations.

[0050] Step S102: Respond to the account management command and query the target out-of-band device indicated by the device identifier;

[0051] Step S103: Send the account operation instruction to the target out-of-band device, wherein the target out-of-band device performs account management operation on the user account indicated by the user account information and obtains the account management result and account update information;

[0052] Step S104: The account management results returned by the target out-of-band device are transmitted to the network server, and the account update information is transmitted to the database. The database and the network server have a pre-established network connection.

[0053] Through the above steps, account management instructions transmitted from the network server can be received. These instructions carry at least a device identifier and account operation instructions. The account operation instructions include at least user account information and account management operations. Responding to the account management instructions, the system queries the target out-of-band device indicated by the device identifier and sends the account operation instructions to the target out-of-band device. The target out-of-band device performs account management operations on the user account indicated by the user account information, obtaining account management results and account update information. The system then transmits the account management results returned by the target out-of-band device to the network server and the account update information to the database. In this embodiment, an out-of-band proxy server can be used to manage various out-of-band devices, automating account management and avoiding uncontrollable impacts caused by bypassing the login operation device server. This reduces management difficulty and solves the technical problem in related technologies where managing a large number of physical machines in a data center by device administrators is very difficult.

[0054] It should be noted that the out-of-band device in this embodiment, also known as an out-of-band server, is a physical machine deployed in a data center. This embodiment does not limit the type of out-of-band device; the actual usage shall prevail.

[0055] This embodiment manages N out-of-band devices through an out-of-band proxy server (or out-of-band management server). Management primarily involves account management, such as account extraction and password modification. The out-of-band proxy server pre-establishes wired / wireless connections with the N out-of-band devices. Upon receiving an account management command, it accurately locates each out-of-band device requiring control, thus implementing account / user management. Here, N is a positive integer greater than or equal to 1.

[0056] In order to facilitate the management of a large number of out-of-band devices by the out-of-band proxy server, this embodiment constructs a database. The type of database may include, but is not limited to, an application database, through which account information can be recorded / updated.

[0057] Furthermore, in this embodiment, the out-of-band proxy server, network server, and database are all deployed on the target open platform, and multiple application systems on the target open platform share user accounts. By sharing user accounts, single sign-on (SSO) is achieved, meaning that in multiple application systems under the same account platform, a user only needs to log in once to access all mutually trusted application systems.

[0058] This embodiment provides single sign-on functionality, allowing users to log in to all out-of-band devices through an out-of-band server via a front-end page. For example, if an out-of-band device has the IP address 192.168.1.0 and the initial password for the root user is "root," this embodiment uses an out-of-band proxy server to log in to that out-of-band device as the root user and changes the password according to a predetermined password policy to achieve user password management. Users cannot log in to 192.168.1.0 via root / root and must log in through the front-end page for single sign-on.

[0059] In this embodiment, the front-end manages devices through an out-of-band proxy server and configures security policies for user control. Specific development languages ​​include, but are not limited to, J2EE.

[0060] Figure 2 This is a schematic diagram of an optional out-of-band device in-line system according to an embodiment of the present invention, such as... Figure 2 As shown, the management system includes: a front-end, a network server, an out-of-band proxy server, N out-of-band devices, and a database. The network server and the out-of-band proxy server are pre-connected, the out-of-band proxy server and the N out-of-band devices are pre-connected, and the network server and the database are pre-connected.

[0061] The types of network servers can include, but are not limited to: web servers, through which management operations initiated by the front end can be received (corresponding to...). Figure 2 Step 1 in the process (initiating the management operation), then the web server performs account management (corresponding to...). Figure 2 Step 2 in the process (initiating an account management command) allows the out-of-band proxy server to respond to the account management command and initiate account management (corresponding to...). Figure 2 Step 3 (Initiating Account Management) involves the managed out-of-band device responding to the account management request, performing operations such as account extraction and password modification, and sending the account management result (corresponding to...) to the out-of-band proxy server. Figure 2 Step 4. Account Management Result: The out-of-band proxy server forwards this result to the web server (corresponding to...). Figure 2 Step 5. Account Management Results: Finally, the web server will update the account information to the database based on the account management results (corresponding to...). Figure 2 Step 6. Update account information.

[0062] The following is combined Figure 2 The embodiments of the present invention will be described in detail below with reference to the above-described implementation steps.

[0063] Optionally, before the network server receives the management operations, device information, and user information sent by the front end, the following steps are also included: the front end displays a user login page; the front end receives user information entered through the user login page; the front end receives device management instructions; the front end responds to the device management instructions and displays a device management page, wherein the device management page contains virtual boxes associated with device management and account management; the front end receives operation information from external devices on the device management page, and obtains account management operations and device information.

[0064] It should be noted that the front-end in this embodiment can refer to the terminal platform used by maintenance users or business personnel of financial institutions. The type of front-end includes, but is not limited to, PCs, tablets, iPads, and mobile terminals. Through this front-end, users can log in to the device management front-end page to achieve unified management of out-of-band devices.

[0065] In this embodiment, the front-end receives user information and device management commands entered on the login page, then responds to the device management commands and displays the device management page. Subsequently, it receives operation information from external devices on the device management page to obtain account management operations and device information. Account management operations include, but are not limited to: device account information extraction, password modification, account deletion, and account addition. Device information includes, but is not limited to: the device ID, device name, device location, device attribute information (size, dimensions, weight), and usage status of the out-of-band device to be managed.

[0066] Optionally, before receiving the account management instructions transmitted by the network server, the process includes: the network server receiving the account management operation, device information, and user information sent by the front end; the network server determining the device identifier and device address of the target out-of-band device to be managed based on the device information; the network server determining the user account information based on the user information, wherein the user account information includes at least the user account's operation permissions; and the network server generating an account management instruction based on the account management operation, user account information, device identifier, and device address, provided that the user account's operation permissions indicate that the operator has the operation permission to perform the account management operation.

[0067] It should be noted that, in this embodiment, the network server receives a resource management request from the front end, obtains account management operations, device information, and user information (login user information), and then determines the operation permissions of the logged-in user account. Through the front end, users enter their IP address and user information to log in via an out-of-band device interface. The system manages and audits user operation commands based on their operation permissions. For example, low-privilege users can only perform read operations and cannot perform write operations. If a user performs an abnormal operation, the access control module will intervene, promptly alerting the user to the risk and preventing dangerous behavior. All operations are recorded in the database, and the relevant operations can be viewed in the audit report.

[0068] Alternatively, before receiving the account management instructions transmitted by the network server, the method further includes: the network server receiving a device management policy input from the front end, wherein the device management policy is one of the following: a partial takeover policy, a full takeover policy, and a non-takeover policy. Based on the device management policy, the operation permissions of the user account are determined, wherein the operation permissions are used to determine whether account management operations can be performed. In this embodiment, the partial takeover policy indicates that the user account's password is randomly generated and can be controlled by the operation and maintenance user; the full takeover policy indicates that the user account's password is randomly generated and cannot be controlled by the operation and maintenance user; the non-takeover policy indicates that the user account's password is controlled by the operation and maintenance user and cannot be modified.

[0069] Users can change their original passwords periodically or manually according to the password rules configured in the security policy, and can manage accounts and passwords according to the device management policy.

[0070] Optionally, before receiving the account management instruction transmitted by the network server, the process further includes: the network server receiving the list management instruction input by the front end; the network server responding to the list management instruction by retrieving the device information and historical operation information of all out-of-band devices from the database to obtain the device operation list; and transmitting the device operation list to the front end.

[0071] By configuring policies on the front end, the network server can obtain inventory management policies, which include, but are not limited to: inventory management extracted by device users to ensure the security of out-of-band devices.

[0072] Step S101: Receive account management instructions transmitted from the network server. The account management instructions carry at least: device identifier and account operation instructions. The account operation instructions include at least: user account information and account management operations.

[0073] In this embodiment, the device identifier includes, but is not limited to, device IP, physical address, device serial number, etc.

[0074] User account information can refer to the information of the login account, such as the login user's username, user account, and password. This user account information is used to confirm the operation permissions of the login user / business personnel.

[0075] Step S102: Respond to the account management command and query the target out-of-band device indicated by the device identifier.

[0076] Optionally, account management operations include at least one of the following: changing the account password, retrieving the account information of the user account, and retrieving the device information of the out-of-band device to which the user account belongs.

[0077] Step S103: Send the account operation instruction to the target out-of-band device, wherein the target out-of-band device performs account management operation on the user account indicated by the user account information, and obtains the account management result and account update information.

[0078] Users can change their original passwords periodically or manually according to the password rules configured in the security policy. Users can be managed according to the following strategies: semi-takeover (passwords are randomly generated and can be controlled by the operation and maintenance personnel), full takeover (passwords are randomly generated and the operation and maintenance personnel have no control over the user's password), and no takeover (the user's password is controlled by the operation and maintenance personnel and no password change is performed).

[0079] Step S104: The account management results returned by the target out-of-band device are transmitted to the network server, and the account update information is transmitted to the database. The database and the network server have a pre-established network connection.

[0080] In this embodiment, the out-of-band device manages the corresponding account configured on the front end and transmits the information to the out-of-band management server. The out-of-band management server then pushes the information to the front end page, and the front end records and stores user passwords and other information in the database. After being managed, the user has no knowledge of the password of the out-of-band device server and needs to log in to the front end of this application for single sign-on.

[0081] Alternatively, this embodiment can also implement the function of obtaining CMDB data to enrich the application node information of the server.

[0082] In addition, the target open platform in this embodiment can also be connected to a monitoring system, which will issue an alarm in a timely manner if the platform node is abnormal.

[0083] Furthermore, the target open platform provided in this embodiment can also interface with a designated email system to provide equipment maintenance personnel with a complete single sign-on and user management view, which has good universality and scalability.

[0084] The invention will now be described in detail with reference to another alternative embodiment.

[0085] Example 2

[0086] This embodiment provides a management device for out-of-band devices, wherein the multiple implementation units included in the management device correspond to the various implementation steps in the above embodiment one.

[0087] This invention provides an out-of-band device management apparatus applied to an out-of-band proxy server, wherein the out-of-band proxy server and the network server have a pre-established connection relationship.

[0088] Figure 3 This is a schematic diagram of an optional out-of-band device management device according to an embodiment of the present invention, such as... Figure 3As shown, the management device may include: a receiving unit 31, a querying unit 32, a sending unit 33, and a transmission unit 34, wherein,

[0089] The receiving unit 31 is used to receive account management instructions transmitted by the network server. The account management instructions carry at least: device identifier and account operation instructions. The account operation instructions include at least: user account information and account management operations.

[0090] Query unit 32 is used to respond to account management commands and query the target out-of-band device indicated by the device identifier;

[0091] The sending unit 33 is used to send the account operation instruction to the target out-of-band device, wherein the target out-of-band device performs account management operation on the user account indicated by the user account information and obtains the account management result and account update information;

[0092] The transmission unit 34 is used to transmit the account management results returned by the target out-of-band device to the network server and transmit the account update information to the database, wherein the database and the network server have a pre-established network connection.

[0093] The aforementioned out-of-band device management device can receive account management instructions transmitted from the network server via receiving unit 31. These instructions include at least a device identifier and account operation instructions, which in turn include at least user account information and account management operations. Responding to the account management instructions via query unit 32, the device queries the target out-of-band device indicated by the device identifier. Sending unit 33 then sends the account operation instructions to the target out-of-band device. The target out-of-band device performs account management operations on the user account indicated by the user account information, obtaining account management results and account update information. Transmitting unit 34 then transmits the account management results returned by the target out-of-band device to the network server and the account update information to the database. In this embodiment, an out-of-band proxy server can be used to manage various out-of-band devices, automating account management and avoiding uncontrollable impacts caused by bypassing the login operation device server. This reduces management difficulty and solves the technical problem in related technologies where managing a large number of physical machines in a computer room by device administrators is extremely difficult.

[0094] Optionally, the out-of-band device management device further includes: a first receiving module, used for the network server to receive account management operations, device information, and user information sent by the front end before receiving account management instructions transmitted by the network server; a first determining module, used for the network server to determine the device identifier and device address of the target out-of-band device to be managed based on the device information; a second determining module, used for the network server to determine user account information based on the user information, wherein the user account information includes at least: the user account's operation permissions; and a first generating module, used for the network server to generate account management instructions based on the account management operations, user account information, device identifier, and device address when the user account's operation permissions indicate that the operator has the operation permissions to perform account management operations.

[0095] Optionally, the management device for out-of-band devices further includes: a first display module, used to display a user login page on the front end before the network server receives the management operation, device information, and user information sent by the front end; a second receiving module, used to receive user information entered through the user login page on the front end; a third receiving module, used to receive device management instructions on the front end; a second display module, used to display a device management page on the front end in response to the device management instructions, wherein the device management page includes virtual boxes associated with device management and account management; and a third receiving module, used to receive operation information from external devices on the device management page on the front end, thereby obtaining account management operations and device information.

[0096] Optionally, the management device for out-of-band devices further includes: a fourth receiving module, used for the network server to receive a device management policy input from the front end before receiving the account management instruction transmitted by the network server, wherein the device management policy is one of the following: a partial takeover policy, a full takeover policy, and a non-takeover policy, wherein the partial takeover policy indicates that the user account's password is randomly generated and can be controlled by the operation and maintenance user; the full takeover policy indicates that the user account's password is randomly generated and cannot be controlled by the operation and maintenance user; and the non-takeover policy indicates that the user account's password is controlled by the operation and maintenance user and cannot be modified; and a third determining module, used to determine the user account's operation permissions based on the device management policy, wherein the operation permissions are used to determine whether account management operations can be performed.

[0097] Optionally, the management device for out-of-band devices further includes: a fifth receiving module, used for the network server to receive a list management instruction input by the front end before receiving the account management instruction transmitted by the network server; a retrieval module, used for the network server to respond to the list management instruction and retrieve the device information and historical operation information of all out-of-band devices from the database to obtain a device operation list; and a transmission module, used to transmit the device operation list to the front end.

[0098] Optionally, the out-of-band proxy server, web server, and database are all deployed on the target open platform, and multiple application systems on the target open platform share user accounts.

[0099] Optionally, account management operations include at least one of the following: changing the account password, retrieving the account information of the user account, and retrieving the device information of the out-of-band device to which the user account belongs.

[0100] The aforementioned management device for out-of-band devices may also include a processor and a memory. The aforementioned receiving unit 31, query unit 32, sending unit 33, transmission unit 34, etc., are all stored in the memory as program units, and the processor executes the aforementioned program units stored in the memory to realize the corresponding functions.

[0101] The aforementioned processor contains a kernel, which retrieves the corresponding program units from memory. One or more kernels can be configured; by adjusting kernel parameters, the account management results returned by the target out-of-band device are transmitted to the network server, and account update information is transmitted to the database.

[0102] The aforementioned memory may include non-permanent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0103] According to another aspect of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored computer program, wherein, when the computer program is running, it controls the device where the computer-readable storage medium is located to perform any of the above-described out-of-band device management methods.

[0104] According to another aspect of the present invention, an electronic device is also provided, including one or more processors and a memory, the memory being used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors cause the one or more processors to implement the out-of-band device management method of any of the above.

[0105] This application also provides a computer program product, which, when executed on a data processing device, is suitable for executing an initialization program comprising the following steps: receiving an account management instruction transmitted from a network server, wherein the account management instruction carries at least: a device identifier and an account operation instruction, and the account operation instruction includes at least: user account information and an account management operation; responding to the account management instruction and querying a target out-of-band device indicated by the device identifier; sending the account operation instruction to the target out-of-band device, wherein the target out-of-band device performs an account management operation on the user account indicated by the user account information, and obtains an account management result and account update information; transmitting the account management result returned by the target out-of-band device to the network server, and transmitting the account update information to a database, wherein the database and the network server have a pre-established network connection.

[0106] Figure 4 This is a hardware structure block diagram of an electronic device (or mobile device) according to an embodiment of the present invention for managing out-of-band devices. Figure 4 As shown, the electronic device may include one or more processors 402 (shown as 402a, 402b, ..., 402n in the figure) 402 (processor 402 may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 404 for storing data. In addition, it may include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, a keyboard, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 4 The structure shown is for illustrative purposes only and does not limit the structure of the electronic device described above. For example, the electronic device may also include components that are more... Figure 4 The more or fewer components shown, or having the same Figure 4 The different configurations shown are illustrated. The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0107] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0108] In the above embodiments of the present invention, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0109] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0110] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0111] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0112] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0113] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method for managing external devices, characterized in that, This is applied to out-of-band proxy servers, where the out-of-band proxy server has a pre-established connection with the network server, including: The system receives an account management instruction transmitted from the network server, wherein the account management instruction carries at least: a device identifier and an account operation instruction, and the account operation instruction includes at least: user account information and account management operation. In response to the account management command, query the target out-of-band device indicated by the device identifier; The account operation instruction is sent to the target out-of-band device, wherein the target out-of-band device performs the account management operation on the user account indicated by the user account information, and obtains the account management result and account update information; The account management results returned by the target out-of-band device are transmitted to the network server, and the account update information is transmitted to the database, wherein the database and the network server have a pre-established network connection; Prior to receiving the account management instructions transmitted by the network server, the process also includes: The network server receives device management policies input from the front end, wherein the device management policy is one of the following: a partial takeover policy, a full takeover policy, and a non-takeover policy. The partial takeover policy indicates that the user account's password is randomly generated and can be controlled by the operation and maintenance user. The full takeover policy indicates that the user account's password is randomly generated and cannot be controlled by the operation and maintenance user. The non-takeover policy indicates that the user account's password is controlled by the operation and maintenance user and cannot be modified. Based on the device management policy, the operation permissions of the user account are determined, wherein the operation permissions are used to determine whether the account management operation can be performed, and the account management operation includes at least one of the following: modifying the account password, retrieving the account information of the user account, and retrieving the device information of the out-of-band device to which the user account belongs.

2. The management method according to claim 1, characterized in that, Before receiving the account management instructions transmitted by the network server, the process also includes: The network server receives account management operations, device information, and user information sent from the front end; Based on the device information, the network server determines the device identifier and device address of the target out-of-band device to be managed; The network server determines the user account information based on the user information, wherein the user account information includes at least: the user account's operating permissions; When the user account's operation permissions indicate that the operator has the operation permissions to perform the account management operation, the network server generates the account management instruction based on the account management operation, the user account information, the device identifier, and the device address.

3. The management method according to claim 2, characterized in that, Before the network server receives the management operation, device information, and user information sent from the front end, it also includes: The front end displays the user login page; The front end receives the user information entered through the user login page; The front end receives device management commands; The front end responds to the device management command and displays a device management page, wherein the device management page includes a virtual box associated with device management and account management; The front end receives operation information from external devices on the device management page, and obtains the account management operation and the device information.

4. The management method according to claim 2, characterized in that, Before receiving the account management instructions transmitted by the network server, the process also includes: The network server receives the list management instructions input from the front end; The network server responds to the list management command and retrieves the device information and historical operation information of all out-of-band devices from the database to obtain a device operation list. The device operation list is transmitted to the front end.

5. The management method according to claim 1, characterized in that, The out-of-band proxy server, the network server, and the database are deployed in the target open platform, and multiple application systems of the target open platform share user accounts.

6. A management device for external equipment, characterized in that, This is applied to out-of-band proxy servers, where the out-of-band proxy server has a pre-established connection with the network server, including: The receiving unit is configured to receive the account management instruction transmitted by the network server, wherein the account management instruction carries at least: a device identifier and an account operation instruction, and the account operation instruction includes at least: user account information and account management operation; The query unit is used to respond to the account management instruction and query the target out-of-band device indicated by the device identifier; The sending unit is used to send the account operation instruction to the target out-of-band device, wherein the target out-of-band device performs the account management operation on the user account indicated by the user account information to obtain the account management result and account update information; A transmission unit is used to transmit the account management result returned by the target out-of-band device to the network server and transmit the account update information to the database, wherein the database and the network server have a pre-established network connection; The device further includes a fourth receiving module, used to receive a device management policy input from the front end before receiving the account management instruction transmitted by the network server. The device management policy is one of the following: a partial takeover policy, a full takeover policy, and a non-takeover policy. The partial takeover policy indicates that the user account's password is randomly generated and can be controlled by the operation and maintenance user. The full takeover policy indicates that the user account's password is randomly generated and cannot be controlled by the operation and maintenance user. The non-takeover policy indicates that the user account's password is controlled by the operation and maintenance user and cannot be modified. The third determining module is used to determine the operation permissions of the user account based on the device management policy. The operation permissions are used to determine whether the account management operation can be performed. The account management operation includes at least one of the following: modifying the account password, extracting the account information of the user account, and extracting the device information of the out-of-band device to which the user account belongs.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored computer program, wherein, when the computer program is executed, it controls the device on which the computer-readable storage medium is located to perform the out-of-band device management method according to any one of claims 1 to 5.

8. An electronic device, characterized in that, It includes one or more processors and a memory, the memory being used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors cause the one or more processors to implement the out-of-band device management method according to any one of claims 1 to 5.

Images