Equipment management method and device and related equipment
By implementing the device management method on the server side, and using the branch's agent to actively register and device discovery tasks, the problems of complexity and high cost of cross-Internet management in the operation and maintenance of ICT equipment on multiple branches are solved, and low-cost and simple device management and monitoring effects are achieved.
Patent Information
- Application Number
- CN202510361050.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-03-25
- Publication Date
- 2025-05-23
AI Technical Summary
In the ICT equipment operation and maintenance scenario of multi-branch sites, the operation and maintenance administrators at the headquarters need to manage and monitor the equipment of each branch site across the Internet. The existing technology mainly relies on public network IP addresses or VPN/dedicated lines, resulting in high cost, complexity and difficulty in achieving low-cost and simple equipment management.
By implementing the device management method on the server side, using the branch agency's agent to actively register and establish communication connections, assign area identification, issue device discovery tasks, receive and manage device information, and implement equipment monitoring, management, backup and recovery functions, supporting multiple manufacturers and different models of equipment.
It realizes the unified monitoring and management of ICT devices from multiple vendors across the Internet at a low cost and simplified manner without the need for public IP addresses and VPNs/dedicated lines, supports the device management of multiple branches, and reduces hardware resource consumption.
Smart Images
Figure CN120034419A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of network operation and maintenance technology, and in particular to a device management method, apparatus and related equipment. Background Art
[0002] Some enterprises and institutions (such as supermarket chains, restaurants, and education bureaus) have many branch sites. Each site has a small number of ICT devices, and there is no administrator to manage and operate the devices of each branch. The headquarters needs to manage and operate them in a unified manner. The sites and the headquarters are connected by the Internet. The operation and maintenance administrator of the headquarters needs operation and maintenance software to manage, monitor, and operate the devices of each branch site across the Internet. Summary of the invention
[0003] The present application provides a device management method, apparatus and related equipment.
[0004] In a first aspect, the present application provides a device management method, which is applied to a server, and the method includes:
[0005] Based on the registration request sent by the agent of each branch, establish a communication connection with the agent of each branch respectively, complete the registration of the agent of each branch, and allocate a regional identifier for uniquely identifying the branch to the agent of each branch;
[0006] Sending a device discovery task carrying a region identifier corresponding to the agent of the target branch to an agent of the target branch, so that the agent of the target branch discovers a device based on the device discovery task and sends the discovered device information to the server;
[0007] The device information sent by the agent of the target branch is received, and the device is managed based on the area identifier corresponding to the agent of the target branch and the device information.
[0008] Optionally, the step of managing the device based on the area identifier corresponding to the agent of the target branch and the device information includes:
[0009] Determine a first device that needs to be monitored by the target branch;
[0010] Configuration includes a device access mode of each first device and a monitoring configuration of a monitoring item required for each first device to establish a monitoring task;
[0011] Based on the regional identifier corresponding to the agent of the target branch, the monitoring task is issued to the agent of the target branch, so that the agent of the target branch collects monitoring information of the monitoring items required for each first device based on the monitoring task, and sends it to the server, wherein the monitoring information of a first device carries the regional identifier corresponding to the agent of the target branch and the device identifier of the first device.
[0012] Optionally, the step of managing the device based on the area identifier corresponding to the agent of the target branch and the device information includes:
[0013] Determine a second device that needs to be managed and controlled by the target branch;
[0014] Configuration includes device management and control methods of each second device, management and control configuration of management and control items required for each second device, so as to establish management tasks;
[0015] Based on the regional identifier corresponding to the agent of the target branch, the management task is issued to the agent of the target branch, so that the agent of the target branch manages and controls each second device based on the management task, and sends the management and control results to the server, wherein the management and control results of a second device carry the regional identifier corresponding to the agent of the target branch and the device identifier of the second device.
[0016] Optionally, the step of managing the device based on the area identifier corresponding to the agent of the target branch and the device information includes:
[0017] Determine a third device that the target branch needs to back up configuration;
[0018] Establish configuration backup tasks for each third device;
[0019] Based on the regional identifier corresponding to the agent of the target branch, the configuration backup task is issued to the agent of the target branch, so that the agent of the target branch obtains the device configuration of each third device based on the configuration backup task, and sends the device configuration of each third device to the server, wherein the configuration backup of a third device carries the regional identifier corresponding to the agent of the target branch and the device identifier of the third device.
[0020] Optionally, the step of managing the device based on the area identifier corresponding to the agent of the target branch and the device information includes:
[0021] Determining a fourth device that needs to be configured and restored at the target branch;
[0022] Establishing a configuration recovery task for each fourth device, wherein a configuration recovery task for a fourth device carries a region identifier corresponding to the agent of the target branch and a device identifier of the fourth device;
[0023] Based on the area identifier corresponding to the agent of the target branch, the configuration recovery task is issued to the agent of the target branch, so that the agent of the target branch issues the configuration of each fourth device to each fourth device based on the configuration recovery task.
[0024] Optionally, the method further comprises:
[0025] Receiving device Trap / syslog information sent by the agent of the target branch, wherein the agent of the target branch sends the device Trap / syslog information to the server when receiving the device Trap / syslog information reported by the fifth device;
[0026] The device Trap / syslog information of each fifth device is maintained based on the area identifier of the agent of the target branch office and the device identifier of the fifth device.
[0027] In a second aspect, the present application provides a device management apparatus, applied to a server, the apparatus comprising:
[0028] A registration unit, configured to establish communication connections with agents of each branch based on registration requests sent by agents of each branch, complete registration of agents of each branch, and allocate a regional identifier for uniquely identifying the branch to the agent of each branch;
[0029] A sending unit, used for sending a device discovery task carrying a region identifier corresponding to the agent of the target branch to the agent of the target branch, so that the agent of the target branch discovers a device based on the device discovery task and sends the discovered device information to the server;
[0030] The management unit is used to receive the device information sent by the agent of the target branch, and manage the device based on the area identifier corresponding to the agent of the target branch and the device information.
[0031] Optionally, when managing the device based on the area identifier corresponding to the agent of the target branch and the device information, the management unit is specifically configured to:
[0032] Determine a first device that needs to be monitored by the target branch;
[0033] Configuration includes a device access mode of each first device and a monitoring configuration of a monitoring item required for each first device to establish a monitoring task;
[0034] Based on the regional identifier corresponding to the agent of the target branch, the monitoring task is issued to the agent of the target branch, so that the agent of the target branch collects monitoring information of the monitoring items required for each first device based on the monitoring task, and sends it to the server, wherein the monitoring information of a first device carries the regional identifier corresponding to the agent of the target branch and the device identifier of the first device.
[0035] Optionally, when managing the device based on the area identifier corresponding to the agent of the target branch and the device information, the management unit is specifically configured to:
[0036] Determine a second device that needs to be managed and controlled by the target branch;
[0037] Configuration includes device management and control methods of each second device, management and control configuration of management and control items required for each second device, so as to establish management tasks;
[0038] Based on the regional identifier corresponding to the agent of the target branch, the management task is issued to the agent of the target branch, so that the agent of the target branch manages and controls each second device based on the management task, and sends the management and control results to the server, wherein the management and control results of a second device carry the regional identifier corresponding to the agent of the target branch and the device identifier of the second device.
[0039] Optionally, when managing the device based on the area identifier corresponding to the agent of the target branch and the device information, the management unit is specifically configured to:
[0040] Determine a third device that the target branch needs to back up configuration;
[0041] Establish configuration backup tasks for each third device;
[0042] Based on the regional identifier corresponding to the agent of the target branch, the configuration backup task is issued to the agent of the target branch, so that the agent of the target branch obtains the device configuration of each third device based on the configuration backup task, and sends the device configuration of each third device to the server, wherein the configuration backup of a third device carries the regional identifier corresponding to the agent of the target branch and the device identifier of the third device.
[0043] Optionally, the management unit is further used for:
[0044] Determining a fourth device that needs to be configured and restored at the target branch;
[0045] Establishing a configuration recovery task for each fourth device, wherein a configuration recovery task for a fourth device carries a region identifier corresponding to the agent of the target branch and a device identifier of the fourth device;
[0046] Based on the area identifier corresponding to the agent of the target branch, the configuration recovery task is issued to the agent of the target branch, so that the agent of the target branch issues the configuration of each fourth device to each fourth device based on the configuration recovery task.
[0047] Optionally, the management unit is further used for:
[0048] Receiving device Trap / syslog information sent by the agent of the target branch, wherein the agent of the target branch sends the device Trap / syslog information to the server when receiving the device Trap / syslog information reported by the fifth device;
[0049] The device Trap / syslog information of each fifth device is maintained based on the area identifier of the agent of the target branch office and the device identifier of the fifth device.
[0050] In a third aspect, an embodiment of the present application provides a device management apparatus, the device management apparatus comprising:
[0051] A memory for storing program instructions;
[0052] The processor is used to call the program instructions stored in the memory, and execute the steps of the method as described in any one of the first aspects above according to the obtained program instructions.
[0053] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to enable the computer to execute the steps of the method described in any one of the first aspects above.
[0054] In summary, the device management method provided in the embodiment of the present application is applied to the server, and the method includes: based on the registration request sent by the agent of each branch, establishing a communication connection with the agent of each branch respectively, and completing the registration of the agent of each branch, and for each branch agent, allocating a regional identifier for uniquely identifying the branch; issuing a device discovery task carrying the regional identifier corresponding to the agent of the target branch to the agent of the target branch, so that the agent of the target branch discovers the device based on the device discovery task, and sends the discovered device information to the server; receiving the device information sent by the agent of the target branch, and managing the device based on the regional identifier corresponding to the agent of the target branch and the device information.
[0055] By adopting the device management method provided in the embodiment of the present application, ICT equipment and software (such as routers, switches, security devices, wireless controllers, wireless controllers, wireless access points, servers, storage, virtualization, containers, operating systems, databases, middleware, etc.) can be monitored and managed with only extremely low hardware resource consumption, and support multiple brands, different models, and multiple communication protocols. It supports monitoring and management of devices in different branches across the Internet without using private networks or VPN scenarios. The device IP addresses between branch sites can be repeated. BRIEF DESCRIPTION OF THE DRAWINGS
[0056] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments of the present application or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For ordinary technicians in this field, other drawings can also be obtained based on these drawings of the embodiments of the present application.
[0057] Figure 1 This is a schematic diagram of an operation and maintenance network for related technologies;
[0058] Figure 2 A detailed flow chart of a device management method provided in an embodiment of the present application;
[0059] Figure 3 A schematic diagram of an operation and maintenance network provided in an embodiment of the present application;
[0060] Figure 4 A schematic diagram of a registration agent and device discovery process provided in the implementation of this application;
[0061] Figure 5 A schematic diagram of a device monitoring process provided in an embodiment of the present application;
[0062] Figure 6 A schematic diagram of a device management and control process provided in an embodiment of the present application;
[0063] Figure 7 A device configuration backup flow chart provided in an embodiment of the present application;
[0064] Figure 8 A schematic diagram of the device configuration recovery and issuance process provided in the embodiment of the present application;
[0065] Fig. 9 A schematic diagram of a trap or syslog process of a receiving device provided in an embodiment of the present application;
[0066] Fig.10A schematic diagram of the structure of a device management device provided in an embodiment of the present application;
[0067] Fig.11 A schematic diagram of the hardware architecture of a device management apparatus provided in an embodiment of the present application. DETAILED DESCRIPTION
[0068] The terms used in the embodiments of the present application are only for the purpose of describing specific embodiments, rather than limiting the present application. The singular forms of "a", "said" and "the" used in the present application and claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used herein refers to any or all possible combinations of one or more associated listed items.
[0069] It should be understood that, although the terms first, second, third, etc. may be used to describe various information in the embodiments of the present application, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the present application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, in addition, the word "if" used may be interpreted as "at..." or "when..." or "in response to determination".
[0070] Currently, in the multi-branch site ICT equipment operation and maintenance scenario, when the headquarters operation and maintenance administrator needs operation and maintenance software to manage, monitor, and operate the branch site equipment across the Internet, the following methods are mainly used for equipment management:
[0071] For example, see Figure 1 The figure shows a schematic diagram of an operation and maintenance network of related technologies. A set of operation and maintenance software is deployed at the headquarters, and agent software is deployed at the branch site. The operation and maintenance software and the agent communicate through the Internet using public network IP or using dedicated lines and VPNs. The operation and maintenance software sends monitoring and management instructions to the agent through the Internet, and the agent sends them to specific devices. The device information monitored by the agent is sent back to the operation and maintenance software, and the operation and maintenance software displays it uniformly.
[0072] However, the lower-level operation and maintenance software deployed in the branch needs a public IP address to communicate with the upper-level operation and maintenance software. When there are many branch sites, a large number of public IP addresses need to be applied for, which is difficult to implement and costly. If public IP addresses are not used, VPN or dedicated lines need to be established between the branch and the headquarters for communication, which is complex to implement and costly. In addition, IP addresses between different branches cannot be repeated, and NAT technology needs to be used to convert the private IP addresses of all sites into unified managed whole-network IP addresses.
[0073] The embodiment of the present application proposes a low-cost and simple method for enterprises and institutions with multiple branch sites to uniformly monitor and manage ICT equipment from multiple manufacturers through the Internet without occupying a large number of public IP addresses when there is no VPN or dedicated line between the branch sites and the headquarters.
[0074] For example, see Figure 2 FIG. 1 is a detailed flow chart of a device management method provided in an embodiment of the present application, and the method includes the following steps:
[0075] Step 200: Based on the registration request sent by the agent of each branch, establish a communication connection with the agent of each branch, complete the registration of the agent of each branch, and allocate a regional identifier for uniquely identifying the branch to the agent of each branch.
[0076] In the embodiment of the present application, the agent (e.g., Agent) of each branch actively registers with the server of the headquarters to establish a communication link with the server and store the relevant agent information on the server. Each agent actively establishes communication with the server, and the server completes the registration of each agent based on the registration request sent by each agent, and configures a regional identifier (e.g., ID) for each agent to uniquely identify the corresponding branch.
[0077] Step 210: issuing a device discovery task carrying the area identifier corresponding to the agent of the target branch to the agent of the target branch, so that the agent of the target branch discovers devices based on the device discovery task and sends the discovered device information to the server.
[0078] It should be noted that the target branch office may be any branch office that has completed registration. In the embodiment of the present application, the device management of the target branch office is taken as an example for description.
[0079] Specifically, after completing the registration of the agent of the target branch and assigning the corresponding regional identifier to the agent of the target branch, the device type required to be managed and monitored in the target branch is configured, that is, the server can issue device discovery tasks to the agents of each branch respectively, so that the agents of each branch can discover the devices required to be managed and monitored in the branch network according to the device discovery tasks. The agents of each branch record the discovered device information and send the discovered device information to the server through the link with the server.
[0080] Step 220: receiving the device information sent by the agent of the target branch, and managing the device based on the area identifier corresponding to the agent of the target branch and the device information.
[0081] The server receives and records the device information discovered by each branch, and associates it with each branch. Specifically, the device information may include device name, device type, device address, and other information.
[0082] Furthermore, the server can distinguish the agents of each branch according to their regional identifiers. Preferably, the discovered device information of each branch can be displayed on a web page.
[0083] For example, see Figure 4 As shown, it is a schematic diagram of a registration agent and device discovery process provided in the implementation of this application; on the agent side, configure the server IP address or domain name, start the service, and the agent actively initiates a link establishment and registration request to the server through the network according to the configuration; the server receives the link and registration request sent by the agent, confirms the use of this agent, registers this agent to assign an ID, establishes a link, and associates it with the site (branch); the server configures the type of equipment to be managed and monitored, and issues a device discovery task to the agent; the agent discovers devices in the network according to the discovery task, records the discovered device information, and sends the discovered device information to the server through an existing link or a new link; the server receives and records the discovered device information and associates it with the site, distinguishes it according to the agent ID, and displays the discovered device information on the web page.
[0084] In the embodiment of the present application, the server can manage each device of each branch based on the discovered device information sent by the agent of each branch.
[0085] In the embodiment of the present application, based on the regional identifier corresponding to the agent of the target branch and the device information management device, a preferred implementation method is:
[0086] Determine the first device that needs to be monitored by the target branch; configure the device access method of each first device and the monitoring configuration of the monitoring items required for each first device to establish a monitoring task; based on the area identifier corresponding to the agent of the target branch, issue the monitoring task to the agent of the target branch, so that the agent of the target branch collects the monitoring information of the monitoring items required for each first device based on the monitoring task, and sends it to the server, wherein the monitoring information of a first device carries the area identifier corresponding to the agent of the target branch and the device identifier of the first device.
[0087] For example, see Figure 5As shown, it is a schematic diagram of a device monitoring process provided by an embodiment of the present application; the server configures the device access mode, monitoring configuration and establishes a monitoring task; the agent periodically initiates a link establishment request, and actively initiates a link establishment to the server through the network; the server receives the link request sent by the agent and establishes a link; the server uses the link established by the agent to send a monitoring task to the agent; the agent receives the monitoring task and records it; the agent periodically collects information from the device according to the monitoring task and records it; the agent sends monitoring information to the server according to the existing link or the newly created link; the server receives and records the device monitoring information, and distinguishes it according to the agent ID, and displays the device monitoring information on the web page.
[0088] In the embodiment of the present application, based on the regional identifier corresponding to the agent of the target branch and the device information management device, a preferred implementation method is:
[0089] Determine the second devices that need to be managed and controlled by the target branch; configure the device management and control methods of each second device, and the management and control configuration of the management and control items required for each second device to establish a management task; based on the area identifier corresponding to the agent of the target branch, issue the management task to the agent of the target branch, so that the agent of the target branch manages and controls each second device based on the management task, and sends the management and control results to the server, wherein the management and control results of a second device carry the area identifier corresponding to the agent of the target branch and the device identifier of the second device.
[0090] For example, see Figure 6 As shown, it is a schematic diagram of a device management and control process provided by an embodiment of the present application; the server configures the device management information and establishes a management task; the agent periodically initiates a link establishment request, and actively initiates a link establishment to the server through the network; the server receives the link request sent by the agent and establishes a link; the server uses the link established by the agent to issue a management task to the agent according to the agent ID; the agent receives the management task and records it, and issues the management and control configuration to the device according to the management task and records the result; the agent sends the management result information to the server through an existing link or a new link; the server receives and records the device management and control result information, distinguishes it according to the agent ID, and displays the device management and control results on the web page.
[0091] In the embodiment of the present application, based on the regional identifier corresponding to the agent of the target branch and the device information management device, a preferred implementation method is:
[0092] Determine the third devices that need to be backed up for configuration at the target branch; establish a configuration backup task for each third device; and based on the area identifier corresponding to the agent of the target branch, issue the configuration backup task to the agent of the target branch, so that the agent of the target branch obtains the device configuration of each third device based on the configuration backup task, and sends the device configuration of each third device to the server, wherein the configuration backup of a third device carries the area identifier corresponding to the agent of the target branch and the device identifier of the third device.
[0093] For example, see Figure 7 As shown, it is a device configuration backup flow chart provided by an embodiment of the present application; the server configures the device configuration backup information to establish a configuration backup task; the agent periodically initiates a link establishment request, and actively initiates a link establishment to the server through the network; the server receives the link request sent by the agent and establishes a link; the server uses the link established by the agent to send the configuration backup task to the agent according to the agent ID; the agent receives the configuration backup task and records it; the agent obtains the configuration file from the device according to the configuration backup task; the agent sends the converted device configuration file data stream to the server through an existing link or a newly created link; the server receives the device configuration file data stream and converts it into a configuration file; the server distinguishes according to the agent ID, and displays the device configuration results and configuration information on the web page.
[0094] In the embodiment of the present application, based on the regional identifier corresponding to the agent of the target branch and the device information management device, a preferred implementation method is:
[0095] Determine the fourth device that needs to be configured and restored at the target branch; establish a configuration recovery task for each fourth device, wherein a configuration recovery task for a fourth device carries the area identifier corresponding to the agent of the target branch and the device identifier of the fourth device; based on the area identifier corresponding to the agent of the target branch, issue the configuration recovery task to the agent of the target branch, so that the agent of the target branch issues the configuration of each fourth device to each fourth device based on the configuration recovery task.
[0096] For example, see Figure 8As shown, it is a schematic diagram of the device configuration recovery and issuance process provided in an embodiment of the present application; the server configures the device recovery and issuance information, and establishes the configuration recovery and issuance tasks; the agent periodically initiates a link establishment request, and actively initiates a link establishment to the server through the network; the server receives the link request sent by the agent and establishes a link; the server converts the device configuration file into a data stream, and uses the link established by the agent to issue the configuration issuance, recovery task and configuration file data stream to the agent according to the agent ID; the agent receives the configuration issuance, recovery task and configuration file data stream and converts it into a configuration file; the agent passes the configuration file to the device according to the configuration issuance and recovery tasks.
[0097] Furthermore, in the embodiment of the present application, the above method may also include the following steps:
[0098] Receive device Trap / syslog information sent by the agent of the target branch, wherein the agent of the target branch sends the device Trap / syslog information to the server when receiving the device Trap / syslog information reported by the fifth device; maintain the device Trap / syslog information of each fifth device based on the area identifier of the agent of the target branch and the device identifier of the fifth device.
[0099] For example, see Fig. 9 As shown, it is a schematic diagram of a process of receiving a device trap or syslog provided in an embodiment of the present application; the agent periodically initiates a request to establish a link, and actively initiates a link establishment to the server through the network; the server receives the link request sent by the agent and establishes a link; the agent receives the device trap or syslog and records it; the device trap or syslog is converted into a data stream, and the converted device trap or syslog data stream is sent to the server through the existing link; the server receives the device trap or syslog data stream and converts and decrypts it; the server distinguishes according to the agent ID, and displays the device trap or syslog information on the web page.
[0100] In the embodiment of the present application, the agent of each branch actively registers with the server to store the relevant agent information on the server. The agent actively establishes communication with the server, and the server sends monitoring and management tasks to the agent according to the configuration. After the task is completed, the agent returns the task execution results and the information exchanged with the device to the server.
[0101] The server distinguishes duplicate private IP addresses between different sites based on the proxy ID plus the device IP address.
[0102] Register agents and automatically discover devices in the network; obtain device status information through relevant protocols for monitoring; manage and control devices through relevant protocols; obtain device configuration files through relevant protocols for configuration backup; pass configuration files to devices through relevant protocols for configuration recovery and configuration changes; obtain syslog and trap reported by devices. Relevant protocols include SNMP, SSH, Netconf, websocket, SFTP, TFTP, FTP, S-MIS, iLO, Rest, Redfish, IPMI, HTTP, HTTPS, etc.
[0103] The agent actively registers with the server, and the agent and server can communicate across the Internet. The agent does not need to configure a public IP address, and the agent and server do not need a VPN or dedicated line. The agent actively initiates communication with the server, and after the communication link is established, the server issues monitoring and collection tasks. Supports a variety of monitoring and management services, including monitoring, management, control, configuration backup, recovery, and device syslog and trap reception. Supports multi-vendor, multi-type IT and CT equipment.
[0104] Based on the same inventive concept as the above-mentioned embodiment of the invention, for example, refer to Fig.10 FIG. 1 is a schematic diagram of a device management apparatus provided in an embodiment of the present application, the device comprising:
[0105] The registration unit 100 is used to establish a communication connection with the agent of each branch based on the registration request sent by the agent of each branch, complete the registration of the agent of each branch, and allocate a regional identifier for uniquely identifying the branch to the agent of each branch;
[0106] The issuing unit 101 is used to issue a device discovery task carrying a region identifier corresponding to the agent of the target branch to the agent of the target branch, so that the agent of the target branch discovers a device based on the device discovery task and sends the discovered device information to the server;
[0107] The management unit 102 is configured to receive the device information sent by the agent of the target branch, and manage the device based on the area identifier corresponding to the agent of the target branch and the device information.
[0108] Optionally, when managing devices based on the area identifier corresponding to the agent of the target branch and the device information, the management unit 102 is specifically configured to:
[0109] Determine a first device that needs to be monitored by the target branch;
[0110] Configuration includes a device access mode of each first device and a monitoring configuration of a monitoring item required for each first device to establish a monitoring task;
[0111] Based on the regional identifier corresponding to the agent of the target branch, the monitoring task is issued to the agent of the target branch, so that the agent of the target branch collects monitoring information of the monitoring items required for each first device based on the monitoring task, and sends it to the server, wherein the monitoring information of a first device carries the regional identifier corresponding to the agent of the target branch and the device identifier of the first device.
[0112] Optionally, when managing devices based on the area identifier corresponding to the agent of the target branch and the device information, the management unit 102 is specifically configured to:
[0113] Determine a second device that needs to be managed and controlled by the target branch;
[0114] Configuration includes device management and control methods of each second device, management and control configuration of management and control items required for each second device, so as to establish management tasks;
[0115] Based on the regional identifier corresponding to the agent of the target branch, the management task is issued to the agent of the target branch, so that the agent of the target branch manages and controls each second device based on the management task, and sends the management and control results to the server, wherein the management and control results of a second device carry the regional identifier corresponding to the agent of the target branch and the device identifier of the second device.
[0116] Optionally, when managing devices based on the area identifier corresponding to the agent of the target branch and the device information, the management unit 102 is specifically configured to:
[0117] Determine a third device that the target branch needs to back up configuration;
[0118] Establish configuration backup tasks for each third device;
[0119] Based on the regional identifier corresponding to the agent of the target branch, the configuration backup task is issued to the agent of the target branch, so that the agent of the target branch obtains the device configuration of each third device based on the configuration backup task, and sends the device configuration of each third device to the server, wherein the configuration backup of a third device carries the regional identifier corresponding to the agent of the target branch and the device identifier of the third device.
[0120] Optionally, the management unit 102 is further configured to:
[0121] Determining a fourth device that needs to be configured and restored at the target branch;
[0122] Establishing configuration recovery tasks for each fourth device, wherein a configuration recovery task for a fourth device carries a region identifier corresponding to the agent of the target branch and a device identifier of the fourth device;
[0123] Based on the area identifier corresponding to the agent of the target branch, the configuration recovery task is issued to the agent of the target branch, so that the agent of the target branch issues the configuration of each fourth device to each fourth device based on the configuration recovery task.
[0124] Optionally, the management unit 102 is further configured to:
[0125] Receiving device Trap / syslog information sent by the agent of the target branch, wherein the agent of the target branch sends the device Trap / syslog information to the server when receiving the device Trap / syslog information reported by the fifth device;
[0126] The device Trap / syslog information of each fifth device is maintained based on the area identifier of the agent of the target branch office and the device identifier of the fifth device.
[0127] The above units may be one or more integrated circuits configured to implement the above methods, such as one or more application specific integrated circuits (ASIC), or one or more digital signal processors (DSP), or one or more field programmable gate arrays (FPGA). For another example, when a certain unit is implemented in the form of a processing element scheduling program code, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call program code. For another example, these units may be integrated together and implemented in the form of a system-on-a-chip (SOC).
[0128] Furthermore, the device management device provided in the embodiment of the present application, from the hardware level, the hardware architecture diagram of the device management device can be seen in Fig.11 As shown, the device management apparatus may include: a memory 110 and a processor 111,
[0129] The memory 110 is used to store program instructions; the processor 111 calls the program instructions stored in the memory 110 and executes the above method embodiment according to the obtained program instructions. The specific implementation method and technical effect are similar and will not be repeated here.
[0130] Optionally, the present application also provides a device management server, comprising at least one processing element (or chip) for executing the above method embodiment.
[0131] Optionally, the present application also provides a program product, such as a computer-readable storage medium, which stores computer-executable instructions, and the computer-executable instructions are used to enable the computer to execute the above method embodiments.
[0132] Here, the machine-readable storage medium may be any electronic, magnetic, optical or other physical storage device that may contain or store information, such as executable instructions, data, etc. For example, the machine-readable storage medium may be: RAM (RadomAccess Memory), volatile memory, non-volatile memory, flash memory, storage drive (such as hard disk drive), solid state drive, any type of storage disk (such as CD, DVD, etc.), or similar storage medium, or a combination thereof.
[0133] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which may be in the form of a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver, a game console, a tablet computer, a wearable device or a combination of any of these devices.
[0134] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.
[0135] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the embodiments of the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.
[0136] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0137] Moreover, these computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.
[0138] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0139] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.
Claims
1. A device management method, characterized in that: Applied to the server, the method includes: Based on the registration request sent by the agent of each branch, establish a communication connection with the agent of each branch respectively, complete the registration of the agent of each branch, and allocate a regional identifier for uniquely identifying the branch to the agent of each branch; Sending a device discovery task carrying a region identifier corresponding to the agent of the target branch to an agent of the target branch, so that the agent of the target branch discovers a device based on the device discovery task and sends the discovered device information to the server; The device information sent by the agent of the target branch is received, and the device is managed based on the area identifier corresponding to the agent of the target branch and the device information.
2. The method according to claim 1, characterized in that The steps of managing the device based on the regional identifier corresponding to the agent of the target branch and the device information include: Determine a first device that needs to be monitored by the target branch; Configuration includes a device access mode of each first device and a monitoring configuration of a monitoring item required for each first device to establish a monitoring task; Based on the regional identifier corresponding to the agent of the target branch, the monitoring task is issued to the agent of the target branch, so that the agent of the target branch collects monitoring information of the monitoring items required for each first device based on the monitoring task, and sends it to the server, wherein the monitoring information of a first device carries the regional identifier corresponding to the agent of the target branch and the device identifier of the first device.
3. The method according to claim 2, characterized in that The steps of managing the device based on the regional identifier corresponding to the agent of the target branch and the device information include: Determine a second device that needs to be managed and controlled by the target branch; Configuration includes device management and control methods of each second device, management and control configuration of management and control items required for each second device, so as to establish management tasks; Based on the regional identifier corresponding to the agent of the target branch, the management task is issued to the agent of the target branch, so that the agent of the target branch manages and controls each second device based on the management task, and sends the management and control results to the server, wherein the management and control results of a second device carry the regional identifier corresponding to the agent of the target branch and the device identifier of the second device.
4. The method according to claim 1, characterized in that The steps of managing the device based on the regional identifier corresponding to the agent of the target branch and the device information include: Determine a third device that the target branch needs to back up configuration; Establish configuration backup tasks for each third device; Based on the regional identifier corresponding to the agent of the target branch, the configuration backup task is issued to the agent of the target branch, so that the agent of the target branch obtains the device configuration of each third device based on the configuration backup task, and sends the device configuration of each third device to the server, wherein the configuration backup of a third device carries the regional identifier corresponding to the agent of the target branch and the device identifier of the third device.
5. The method according to claim 4, characterized in that The steps of managing the device based on the regional identifier corresponding to the agent of the target branch and the device information include: Determining a fourth device that needs to be configured and restored at the target branch; Establishing a configuration recovery task for each fourth device, wherein a configuration recovery task for a fourth device carries a region identifier corresponding to the agent of the target branch and a device identifier of the fourth device; Based on the area identifier corresponding to the agent of the target branch, the configuration recovery task is issued to the agent of the target branch, so that the agent of the target branch issues the configuration of each fourth device to each fourth device based on the configuration recovery task.
6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: Receiving device Trap / syslog information sent by the agent of the target branch, wherein the agent of the target branch sends the device Trap / syslog information to the server when receiving the device Trap / syslog information reported by the fifth device; The device Trap / syslog information of each fifth device is maintained based on the area identifier of the agent of the target branch office and the device identifier of the fifth device.
7. A device management device, characterized in that: Applied to the server, the device comprises: A registration unit, configured to establish communication connections with agents of each branch based on registration requests sent by agents of each branch, complete registration of agents of each branch, and allocate a regional identifier for uniquely identifying the branch to the agent of each branch; A sending unit, used for sending a device discovery task carrying a region identifier corresponding to the agent of the target branch to the agent of the target branch, so that the agent of the target branch discovers a device based on the device discovery task and sends the discovered device information to the server; The management unit is used to receive the device information sent by the agent of the target branch, and manage the device based on the area identifier corresponding to the agent of the target branch and the device information.
8. The device according to claim 7, characterized in that When managing the device based on the area identifier corresponding to the agent of the target branch and the device information, the management unit is specifically used to: Determine a first device that needs to be monitored by the target branch; Configuration includes a device access mode of each first device and a monitoring configuration of a monitoring item required for each first device to establish a monitoring task; Based on the regional identifier corresponding to the agent of the target branch, the monitoring task is issued to the agent of the target branch, so that the agent of the target branch collects monitoring information of the monitoring items required for each first device based on the monitoring task, and sends it to the server, wherein the monitoring information of a first device carries the regional identifier corresponding to the agent of the target branch and the device identifier of the first device.
9. The device according to claim 7, characterized in that When managing the device based on the area identifier corresponding to the agent of the target branch and the device information, the management unit is specifically used to: Determine a second device that needs to be managed and controlled by the target branch; Configuration includes device management and control methods of each second device, management and control configuration of management and control items required for each second device, so as to establish management tasks; Based on the regional identifier corresponding to the agent of the target branch, the management task is issued to the agent of the target branch, so that the agent of the target branch manages and controls each second device based on the management task, and sends the management and control results to the server, wherein the management and control results of a second device carry the regional identifier corresponding to the agent of the target branch and the device identifier of the second device.
10. The device according to claim 7, characterized in that When managing the device based on the area identifier corresponding to the agent of the target branch and the device information, the management unit is specifically used to: Determine a third device that the target branch needs to back up configuration; Establish configuration backup tasks for each third device; Based on the regional identifier corresponding to the agent of the target branch, the configuration backup task is issued to the agent of the target branch, so that the agent of the target branch obtains the device configuration of each third device based on the configuration backup task, and sends the device configuration of each third device to the server, wherein the configuration backup of a third device carries the regional identifier corresponding to the agent of the target branch and the device identifier of the third device.
11. The device according to claim 10, characterized in that The management unit is also used to: Determining a fourth device that needs to be configured and restored at the target branch; Establishing a configuration recovery task for each fourth device, wherein a configuration recovery task for a fourth device carries a region identifier corresponding to the agent of the target branch and a device identifier of the fourth device; Based on the area identifier corresponding to the agent of the target branch, the configuration recovery task is issued to the agent of the target branch, so that the agent of the target branch issues the configuration of each fourth device to each fourth device based on the configuration recovery task.
12. The device according to any one of claims 7 to 11, characterized in that: The management unit is also used to: Receiving device Trap / syslog information sent by the agent of the target branch, wherein the agent of the target branch sends the device Trap / syslog information to the server when receiving the device Trap / syslog information reported by the fifth device; The device Trap / syslog information of each fifth device is maintained based on the area identifier of the agent of the target branch office and the device identifier of the fifth device.