CN110572365A - multi-protocol server management method, system, terminal device and storage medium - Google Patents
multi-protocol server management method, system, terminal device and storage medium Download PDFInfo
- Publication number
- CN110572365A CN110572365A CN201910728752.2A CN201910728752A CN110572365A CN 110572365 A CN110572365 A CN 110572365A CN 201910728752 A CN201910728752 A CN 201910728752A CN 110572365 A CN110572365 A CN 110572365A
- Authority
- CN
- China
- Prior art keywords
- protocol
- server
- address
- management
- managed server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/255—Maintenance or indexing of mapping tables
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/08—Protocols for interworking; Protocol conversion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
Abstract
The embodiment of the application records mapping relations corresponding to all managed servers in a data recording layer, then sets a management instruction and carries IP addresses in a protocol abstraction layer, searches a protocol supported by the corresponding managed server according to the IP addresses, and sends the management instruction through a corresponding protocol adaptation layer, so that the problem that a plurality of sets of management systems are needed to manage the servers simultaneously under the condition that a server cluster contains the servers supporting multiple protocols is solved, and the server management is more convenient.
Description
Technical Field
The present application relates to the field of server management technologies, and in particular, to a method, a system, a terminal device, and a storage medium for managing a multi-protocol server.
Background
Currently, server products are continuously developed, server management technologies are diversified, traditional servers generally support an ipmi protocol (intelligent platform management interface is used for performing hardware management) for management, and some emerging servers are managed by supporting a redfish protocol (restful api interface is used for performing remote management on the servers). The current server management system can only manage a server of one protocol type singly, for example, the server can only manage a server supporting an ipmi protocol, or can only manage a server supporting a redfish protocol, and a server cluster often includes a large number of servers, some of which only support ipmi and some of which only support redfish protocol, so that two sets of management systems are required to manage the servers at the same time, and the server management is inconvenient.
Content of application
in view of this, embodiments of the present application provide a method, a system, a terminal device, and a storage medium for managing a multi-protocol server, so as to solve the problem in the prior art that management of a multi-protocol server in a server cluster is inconvenient.
A first aspect of an embodiment of the present application provides a multi-protocol server management method, which is applied to a server management system, and the multi-protocol server management method includes:
acquiring a management instruction, wherein the management instruction carries an IP address of a managed server; wherein the management instruction is used for managing a server;
acquiring a protocol supported by the managed server according to the IP address;
and sending a management instruction to a managed server supporting the protocol in the server cluster.
a second aspect of an embodiment of the present application provides a multi-protocol server management system, including:
the first acquisition module is used for acquiring a management instruction, wherein the management instruction carries an IP address of a managed server, and the management instruction is used for managing the server;
A second obtaining module, configured to obtain, according to the IP address, a protocol supported by the managed server;
And the sending module is used for sending a management instruction to the managed server supporting the protocol in the server cluster.
A third aspect of embodiments of the present application provides a terminal device, comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the method according to any one of the preceding claims when executing the computer program.
A fourth aspect of embodiments of the present application provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the method of any one of the preceding claims.
the beneficial effect of this application lies in: according to the method and the system, the mapping relation corresponding to each managed server is recorded in the data recording layer, then the management instruction and the IP address are set in the protocol abstraction layer, the protocol supported by the corresponding managed server is searched according to the IP address, and the management instruction is sent through the corresponding protocol adaptation layer, so that the problem that a plurality of sets of management systems are needed to manage the servers simultaneously under the condition that a server cluster comprises the servers supporting multiple protocols is solved, and the server management is more convenient.
Drawings
in order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
fig. 1 is a schematic flowchart of an implementation of a multi-protocol server management method according to an embodiment of the present application;
Fig. 2 is a schematic flowchart of another implementation of a multi-protocol server management method according to an embodiment of the present application;
fig. 3 is a schematic flowchart of another implementation of a multi-protocol server management method according to an embodiment of the present application;
Fig. 4 is a schematic flowchart of another implementation of a multi-protocol server management method according to an embodiment of the present application;
Fig. 5 is a schematic structural diagram of a multi-protocol server management system provided in an embodiment of the present application;
fig. 6 is a schematic structural diagram of a multi-protocol server management system according to an embodiment of the present application;
Fig. 7 is a schematic structural diagram of a terminal device according to an embodiment of the present application.
Detailed Description
in order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms "comprises" and "comprising," and any variations thereof, in the description and claims of this application and the drawings described above, are intended to cover non-exclusive inclusions. For example, a process, method, or system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus. Furthermore, the terms "first," "second," and "third," etc. are used to distinguish between different objects and are not used to describe a particular order.
Example one
The present application provides a multi-protocol server management method, which is applied to a multi-protocol server management system 100, wherein the multi-protocol server management system 100 is used for managing all servers in a server cluster 5, and the multi-protocol server management system 100 includes, but is not limited to, a Linux server management system, a wdcp management system, a virtual host management system, and the like, which is not limited thereto.
As shown in fig. 1, the present embodiment provides a multi-protocol server management method, including:
S101, acquiring a management instruction, wherein the management instruction carries an IP address of a managed server; wherein the management instruction is used for managing a server;
In the application, the management instruction includes, but is not limited to, controlling the managed server to power on, power off, checking the server status, and configuring a site on the management server, and the management instruction is set by a manager for input, or may be an instruction preset in the multi-protocol server management system 100, where the instruction sets a corresponding trigger condition, such as 8: 00, sending a management instruction to the server, which is not limited in this respect; the IP address is a protocol address designed for the servers to communicate with each other, the IP address is used to number the servers, and the number is unique, the managed server is provided in a server cluster, and the server cluster is provided with a plurality of servers supporting different protocols, which is not limited thereto.
As shown in fig. 2, in one embodiment, the managed server includes a MAC address; before step S101, the method includes:
S201, acquiring an association relation between the IP address and the MAC address uploaded by the managed server;
s202, determining the IP address of the managed server according to the MAC address.
In the application, the MAC address of the managed server is a physical address of the managed server, which is also called a hardware address or a link address, and is written inside hardware when produced by a network equipment manufacturer. The MAC address is independent of the network, i.e. the MAC address is not available for communication, i.e. wherever the hardware with this address (e.g. network card, hub, router, etc.) is connected to the network, it has the same MAC address, which is written by the manufacturer in the BIOS of the network card. The MAC address may take any one of 6 bytes (48 bits) or 2 bytes (16 bits). In addition, the network card of the MAC address has unique identification, namely the MAC address also has uniqueness.
the association relationship may be a mapping relationship, a binding relationship, or the like, and is not limited thereto. The IP address is only identified logically, and can be modified freely by anyone, so that the IP address cannot be used for identifying the user and is used for communication; the MAC address is solidified in the network card, so that the MAC address cannot be impersonated and stolen, and based on the characteristic of the MAC address, the MAC address and the IP address are in one-to-one correspondence in the server.
in a specific application, the association relationship may be a one-to-one bidirectional mapping relationship, and may query the associated IP address according to the MAC address, or query the corresponding MAC address according to the IP address, which is not limited herein. In the application, the IP address can be changed, the MAC address cannot be changed, one server can be configured with one MAC address, and can also be configured with a plurality of IP addresses, and when one IP address is stolen, other IP addresses can be used for communication.
As shown in FIG. 3, in one embodiment, the protocol comprises a redfish protocol, and the server cluster comprises a first managed server; before step S101, the method includes:
S301, sending a redfish protocol instruction to the server cluster;
S302, acquiring a first request packet of the server cluster responding to the redfish protocol instruction; the first request packet carries a first IP address and a first protocol tag of the first managed server, and the first protocol tag is used for indicating that the first managed server supports a redifish protocol.
in application, the first IP address is specifically an IP address of a first managed server, and the server cluster 5 is a first managed server that supports a redfish protocol and is included therein; the redfish is used for creating, updating and reading server internal information by using HTTP, and a corresponding data interface, such as a restful interface, is used for managing the server by matching with an HTTP protocol; the redfish protocol instruction is sent to the first managed server by a redfish adaptation layer in the multi-protocol server management system 100, where the redfish adaptation layer is a device dedicated to sending the redfish protocol instruction, and the purpose of sending the redfish protocol instruction is to obtain the first managed server supporting the redifish protocol and to be marked by the first protocol, which is specifically shown in fig. 6.
In a specific application, the redfish protocol instruction may be understood as an 'rmcp ping message of the redfish protocol, and the first managed server may respond to the' rmcp ping message, that is, after receiving the rmcp ping message, the first managed server returns an rmcp pong message and indicates that the redfish protocol is supported.
in an embodiment, after step S302, the method includes:
and establishing a first mapping relation between the first IP address and the first protocol label.
in an application, the first mapping relationship may be a single-to-single mapping relationship, and may be a single-to-single mapping relationship, where the first protocol flag (the first managed server) may be queried only according to the first IP address, or may be a single-to-single bidirectional mapping relationship, or may be queried according to the first protocol flag (the first managed server), which is not limited to this.
in an embodiment, the above protocol further includes an ipmi protocol, and the server cluster further includes a second managed server; step S101 is preceded by:
Sending an ipmi protocol command to the server cluster;
Acquiring a second request packet of the server cluster 5 according to the ipmi protocol instruction; the second request packet carries a second IP address and a second protocol label of the second managed server, and the second protocol label is used for indicating that the second managed server supports the ipmi protocol.
in application, the second IP address is specifically an IP address of a second managed server, and the server cluster 5 further includes a second managed server supporting an ipmi protocol therein; the ipmi also creates, updates and reads the server internal information by using HTTP, and manages the server by using a corresponding data interface, such as an ipmi interface, in cooperation with the HTTP protocol; the ipmi protocol command is sent to the second managed server by the ipmi adaptation layer in the multi-protocol server management system 100, as shown in fig. 6. Wherein, the ipmi adaptation layer is a device specially sending an ipmi protocol command, which aims to acquire a second managed server supporting the ipmi protocol and is marked by the second protocol.
In a specific application, the ipmi protocol command may be understood as an' rmcp ping message of the ipmi protocol, and the second managed server responding thereto may be understood as returning an rmcppang message after the second managed server receives the rmcp ping message, and indicating that the ipmi protocol is supported.
in an embodiment, after obtaining the second request packet of the server cluster responding to the ipmi protocol instruction, the method includes:
and establishing a second mapping relation between the second IP address and the second protocol label.
In an application, the second mapping relationship may be a single-to-single mapping relationship, and may be a single-to-single mapping relationship, where the second protocol label (the first managed server) may be queried only according to the second IP address, or may be a single-to-single bidirectional mapping relationship, or may be queried according to the second protocol label (the second managed server), which is not limited in this respect.
as shown in fig. 4, in an embodiment, before step S101, the method includes:
s401, recording and storing the first mapping relation and the second mapping relation;
s402, acquiring and updating the first IP address and the second IP address according to the first MAC address and the second MAC address;
s403, updating and storing the first mapping relation and the second mapping relation according to the updated first IP address and the second IP address.
in an application, the first mapping relationship and the second mapping relationship are both stored in the data recording layer 3 in the multi-protocol server management system 100, in a specific embodiment, the data recording layer 3 may record the relationship between the mapping relationship and the IP address in a form of a "table," for example, the table entry is a first IP address and a first MAC address, and supports redfish protocol, where the rmcppng packet has the first IP address and the first MAC address, so that the corresponding IP address and MAC address can be recorded. If the first IP address is replaced, the multi-protocol server management system 100 may obtain, from the server cluster 5, a first request packet and/or a second request packet of the ipmi protocol instruction, where the first request packet and/or the second request packet each carries a corresponding updated first IP address and second IP address, and the data recording layer 3 updates and records a new mapping relationship in real time, and obtains the new mapping relationship and the new association relationship, updates the old mapping relationship and the old association relationship, which is not limited to the above, as shown in fig. 6.
in other embodiments, a managed server may have one or more IP addresses, and an IP address may be changed at any time, and each MAC address is fixed and unchanged, so obtaining the association relationship between the IP address and the MAC address uploaded by the managed server further includes: establishing an incidence relation between a plurality of IP addresses and MAC addresses; and respectively establishing and recording mapping relations between a plurality of IP addresses and protocol marks. Specifically, in a certain managed server supporting the protocol, the entry of the managed server may be a second MAC address, a second IP address a, a second IP address B, and a second protocol label, so that one server may be connected to different network devices, which is not limited herein.
as shown in fig. 1, step 102, acquiring the protocol supported by the managed server according to the IP address.
In application, the management instruction carries an IP address of a managed server, the management instruction is input to the protocol abstraction layer 1 in the multiprotocol server management system 100 by a manager, and then a corresponding table entry is searched in the data recording layer 3, where the table entry records a specific protocol supported by the IP address, such as a first IP address a, a supported redfish protocol, and a first MAC address B, and the supported redfish protocol of the managed server can be obtained, as shown in fig. 6.
As shown in fig. 1, step S103 sends a management instruction to a managed server in the server cluster 5 that supports the protocol;
In application, after acquiring the protocol supported by the managed server, the multi-protocol server management system 100 sends a management instruction to the server cluster 5 according to the internal protocol adaptation layer, for example, sending the management instruction to the first managed server supporting the redfish protocol through the redfish protocol adaptation layer 4, and sending the management instruction to the second managed server supporting the ipmi protocol through the ipmi protocol adaptation layer 2. The redfish protocol adaptation layer 4 is in bidirectional communication with the first managed server, the ipmi protocol adaptation layer 2 and the second managed server, as shown in fig. 6.
the beneficial effect of this application lies in: according to the method and the system, the mapping relation corresponding to each managed server is recorded in the data recording layer, then the management instruction and the IP address are set in the protocol abstraction layer, the protocol supported by the corresponding managed server is searched according to the IP address, and the management instruction is sent through the corresponding protocol adaptation layer, so that the problem that a plurality of sets of management systems are needed to manage the servers simultaneously under the condition that a server cluster comprises the servers supporting multiple protocols is solved, and the server management is more convenient.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
Example two
As shown in fig. 5, the present embodiment provides a multi-protocol server management system 100, including:
A first obtaining module 10, configured to obtain a management instruction, where the management instruction carries an IP address of a managed server, and the management instruction is used for managing the server;
a second obtaining module 20, configured to obtain, according to the IP address, a protocol supported by the managed server;
A sending module 30, configured to send a management instruction to a managed server in the server cluster that supports the protocol.
In one embodiment, the managed server includes a MAC address; a multi-protocol server management system 100 comprising:
a third obtaining module, configured to obtain an association relationship between the IP address and the MAC address uploaded by the managed server;
a first determining module, configured to determine an IP address of the managed server according to the MAC address.
in one embodiment, the protocol comprises a redfish protocol, and the server cluster comprises a first managed server; acquiring a management instruction, the multi-protocol server management system 100 further includes:
The first sending module is used for sending a redfish protocol instruction to the server cluster;
A fourth obtaining module, configured to obtain a first request packet of the server cluster responding to the redfish protocol instruction; the first request packet carries a first IP address and a first protocol tag of the first managed server, and the first protocol tag is used for indicating that the first managed server supports a redifish protocol.
In one embodiment, the multi-protocol server management system 100 further comprises:
a first establishing module, configured to establish a first mapping relationship between the first IP address and the first protocol label.
In an embodiment, the protocol further comprises an ipmi protocol, and the server cluster further comprises a second managed server; the multi-protocol server management system 100 further includes:
the second sending module is used for sending an ipmi protocol instruction to the server cluster;
a fifth obtaining module, configured to obtain a second request packet of the server cluster responding to the ipmi protocol instruction; the second request packet carries a second IP address and a second protocol label of the second managed server, and the second protocol label is used for indicating that the second managed server supports the ipmi protocol.
in one embodiment, the multi-protocol server management system 100 further comprises:
and the second establishing module is used for establishing a second mapping relation between the second IP address and the second protocol label.
In one embodiment, the multi-protocol server management system 100 further comprises:
The recording module is used for recording and storing the first mapping relation and the second mapping relation;
A sixth obtaining module, configured to obtain and update the first IP address and the second IP address according to the first MAC address and the second MAC address;
And the updating module is used for updating and storing the first mapping relation and the second mapping relation according to the updated first IP address and the second IP address.
in another embodiment, the third obtaining module is further configured to establish an association relationship between a plurality of IP addresses and MAC addresses; and respectively establishing and recording mapping relations between a plurality of IP addresses and protocol marks.
the beneficial effect of this application lies in: according to the method and the system, the mapping relation corresponding to each managed server is recorded in the data recording layer, then the management instruction and the IP address are set in the protocol abstraction layer, the protocol supported by the corresponding managed server is searched according to the IP address, and the management instruction is sent through the corresponding protocol adaptation layer, so that the problem that a plurality of sets of management systems are needed to manage the servers simultaneously under the condition that a server cluster comprises the servers supporting multiple protocols is solved, and the server management is more convenient.
EXAMPLE III
fig. 7 is a schematic diagram of a terminal device 80 according to an embodiment of the present application. As shown in fig. 7, the terminal device 80 of this embodiment includes: a processor 803, a memory 801 and a computer program 802 stored in the memory 801 and executable on the processor 803. The processor 803 implements the steps in the various method embodiments described above, such as the steps S101 to S103 shown in fig. 1, when executing the computer program 802. Alternatively, the processor 803 realizes the functions of the modules/units in the above-described device embodiments when executing the computer program 802.
Illustratively, the computer program 802 may be partitioned into one or more modules/units that are stored in the memory 801 and executed by the processor 803 to accomplish the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution process of the computer program 802 in the terminal device 80. For example, the computer program 802 may be divided into a first obtaining module, a second obtaining module, and a sending module, and each module specifically functions as follows:
the first acquisition module is used for acquiring a management instruction, wherein the management instruction carries an IP address of a managed server, and the management instruction is used for managing the server;
A second obtaining module, configured to obtain, according to the IP address, a protocol supported by the managed server;
And the sending module is used for sending a management instruction to the managed server supporting the protocol in the server cluster.
the terminal device 80 may be a desktop computer, a notebook, a palm computer, a cloud server, or other computing devices. The terminal device may include, but is not limited to, a processor 803 and a memory 801. Those skilled in the art will appreciate that fig. 7 is merely an example of a terminal device 80, and does not constitute a limitation of terminal device 80, and may include more or fewer components than shown, or some components in combination, or different components, e.g., the terminal device may also include input-output devices, network access devices, buses, etc.
The Processor 803 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The storage 801 may be an internal storage unit of the terminal device 80, such as a hard disk or a memory of the terminal device 80. The memory 801 may also be an external storage device of the terminal device 80, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, provided on the terminal device 80. In one embodiment, the memory 801 may also include both internal and external memory units of the terminal device 80. The memory 801 is used to store the computer programs and other programs and data required by the terminal device. The memory 801 may also be used to temporarily store data that has been output or is to be output.
it will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
in the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/communication terminal and method may be implemented in other ways. For example, the above-described embodiments of the apparatus/communication terminal are merely illustrative, and for example, the division of the modules or units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
the integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow in the method of the embodiments described above can be realized by a computer program, which can be stored in a computer-readable storage medium and can realize the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
the above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (10)
1. A multi-protocol server management method is applied to a server management system, and comprises the following steps:
acquiring a management instruction, wherein the management instruction carries an IP address of a managed server; wherein the management instruction is used for managing a server;
acquiring a protocol supported by the managed server according to the IP address;
And sending a management instruction to a managed server supporting the protocol in the server cluster.
2. the multi-protocol server management method of claim 1, wherein the managed server includes a MAC address;
acquiring a management instruction, wherein the management instruction carries the IP address of a managed server, and the method comprises the following steps:
Acquiring the association relation between the IP address and the MAC address uploaded by the managed server;
and determining the IP address of the managed server according to the MAC address.
3. The multi-protocol server management method of claim 1 wherein the protocol comprises a redfish protocol, the cluster of servers comprises a first managed server;
Acquiring a management instruction, wherein the management instruction carries the IP address of a managed server, and the method comprises the following steps:
sending a redfish protocol instruction to the server cluster;
Acquiring a first request packet of the server cluster responding to the redfish protocol instruction; the first request packet carries a first IP address and a first protocol tag of the first managed server, and the first protocol tag is used for indicating that the first managed server supports a redifish protocol.
4. The multi-protocol server management method according to claim 3, wherein after obtaining the first request packet of the server cluster responding to the redfish protocol command, the method comprises:
And establishing a first mapping relation between the first IP address and the first protocol label.
5. The multi-protocol server management method of claim 4 wherein the protocols further comprise an ipmi protocol, the server cluster further comprising a second managed server;
Acquiring a management instruction, wherein the management instruction carries the IP address of a managed server, and the method comprises the following steps:
Sending an ipmi protocol command to the server cluster;
acquiring a second request packet of the server cluster responding to the ipmi protocol instruction; the second request packet carries a second IP address and a second protocol label of the second managed server, and the second protocol label is used for indicating that the second managed server supports the ipmi protocol.
6. The multi-protocol server management method of claim 5, wherein after obtaining the second request packet of the server cluster responding to the ipmi protocol command, comprising:
And establishing a second mapping relation between the second IP address and the second protocol label.
7. The multiprotocol server management method according to claim 6, wherein obtaining a management instruction, the management instruction carrying the IP address of the managed server, comprises:
Recording and storing the first mapping relation and the second mapping relation;
Acquiring and updating the first IP address and the second IP address according to the first MAC address and the second MAC address;
and updating and storing the first mapping relation and the second mapping relation according to the updated first IP address and the second IP address.
8. a multi-protocol server management system, comprising:
The first acquisition module is used for acquiring a management instruction, wherein the management instruction carries an IP address of a managed server, and the management instruction is used for managing the server;
a second obtaining module, configured to obtain, according to the IP address, a protocol supported by the managed server;
And the sending module is used for sending a management instruction to the managed server supporting the protocol in the server cluster.
9. a terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any of claims 1 to 7 when executing the computer program.
10. a computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910728752.2A CN110572365A (en) | 2019-08-08 | 2019-08-08 | multi-protocol server management method, system, terminal device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910728752.2A CN110572365A (en) | 2019-08-08 | 2019-08-08 | multi-protocol server management method, system, terminal device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110572365A true CN110572365A (en) | 2019-12-13 |
Family
ID=68774761
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910728752.2A Pending CN110572365A (en) | 2019-08-08 | 2019-08-08 | multi-protocol server management method, system, terminal device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110572365A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111130891A (en) * | 2019-12-26 | 2020-05-08 | 北京浪潮数据技术有限公司 | Server management device and method, electronic equipment and storage medium |
| CN111881139A (en) * | 2020-07-29 | 2020-11-03 | 北京浪潮数据技术有限公司 | Data acquisition method, system, equipment and readable storage medium |
| CN112183690A (en) * | 2020-09-30 | 2021-01-05 | 深圳市快易典教育科技有限公司 | Integrated learning management method and system for teaching and electronic equipment |
| CN113359642A (en) * | 2021-06-28 | 2021-09-07 | 上海致景信息科技有限公司 | Multi-brand fusion dyeing and finishing control method, device, system and processor |
| CN113810210A (en) * | 2020-06-15 | 2021-12-17 | 戴尔产品有限公司 | IPMI on REDFISH |
| CN113810210B (en) * | 2020-06-15 | 2024-05-03 | 戴尔产品有限公司 | IPMI on REDFISH |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102957568A (en) * | 2012-11-21 | 2013-03-06 | 浪潮电子信息产业股份有限公司 | Monitoring management method of multi-node server |
| CN103716188A (en) * | 2013-12-20 | 2014-04-09 | 上海网达软件股份有限公司 | Management and maintenance method for Linux server cluster management |
| CN106354610A (en) * | 2015-07-16 | 2017-01-25 | 广达电脑股份有限公司 | Server system and operation method thereof |
| CN107229492A (en) * | 2017-05-17 | 2017-10-03 | 东软集团股份有限公司 | Installation method, device, system, storage medium and the equipment of server system |
| CN107360042A (en) * | 2017-08-22 | 2017-11-17 | 郑州云海信息技术有限公司 | A kind of server management method and device |
| CN108920103A (en) * | 2018-06-29 | 2018-11-30 | 平安科技（深圳）有限公司 | Management method, device, computer equipment and the storage medium of server |
| US20190050351A1 (en) * | 2017-08-10 | 2019-02-14 | Seagate Technology Llc | Enabling out-of-band hardware management via an in-band communications channel |
| CN109710346A (en) * | 2018-08-20 | 2019-05-03 | 平安普惠企业管理有限公司 | Server management method, device, equipment and computer readable storage medium |
-
2019
- 2019-08-08 CN CN201910728752.2A patent/CN110572365A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102957568A (en) * | 2012-11-21 | 2013-03-06 | 浪潮电子信息产业股份有限公司 | Monitoring management method of multi-node server |
| CN103716188A (en) * | 2013-12-20 | 2014-04-09 | 上海网达软件股份有限公司 | Management and maintenance method for Linux server cluster management |
| CN106354610A (en) * | 2015-07-16 | 2017-01-25 | 广达电脑股份有限公司 | Server system and operation method thereof |
| CN107229492A (en) * | 2017-05-17 | 2017-10-03 | 东软集团股份有限公司 | Installation method, device, system, storage medium and the equipment of server system |
| US20190050351A1 (en) * | 2017-08-10 | 2019-02-14 | Seagate Technology Llc | Enabling out-of-band hardware management via an in-band communications channel |
| CN107360042A (en) * | 2017-08-22 | 2017-11-17 | 郑州云海信息技术有限公司 | A kind of server management method and device |
| CN108920103A (en) * | 2018-06-29 | 2018-11-30 | 平安科技（深圳）有限公司 | Management method, device, computer equipment and the storage medium of server |
| CN109710346A (en) * | 2018-08-20 | 2019-05-03 | 平安普惠企业管理有限公司 | Server management method, device, equipment and computer readable storage medium |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111130891A (en) * | 2019-12-26 | 2020-05-08 | 北京浪潮数据技术有限公司 | Server management device and method, electronic equipment and storage medium |
| CN113810210A (en) * | 2020-06-15 | 2021-12-17 | 戴尔产品有限公司 | IPMI on REDFISH |
| CN113810210B (en) * | 2020-06-15 | 2024-05-03 | 戴尔产品有限公司 | IPMI on REDFISH |
| CN111881139A (en) * | 2020-07-29 | 2020-11-03 | 北京浪潮数据技术有限公司 | Data acquisition method, system, equipment and readable storage medium |
| CN111881139B (en) * | 2020-07-29 | 2022-07-08 | 北京浪潮数据技术有限公司 | Data acquisition method, system, equipment and readable storage medium |
| CN112183690A (en) * | 2020-09-30 | 2021-01-05 | 深圳市快易典教育科技有限公司 | Integrated learning management method and system for teaching and electronic equipment |
| CN113359642A (en) * | 2021-06-28 | 2021-09-07 | 上海致景信息科技有限公司 | Multi-brand fusion dyeing and finishing control method, device, system and processor |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110572365A (en) | multi-protocol server management method, system, terminal device and storage medium | |
| CN110677405B (en) | Data processing method and device, electronic equipment and storage medium | |
| CN105049502B (en) | The method and apparatus that device software updates in a kind of cloud network management system | |
| CN108243407B (en) | Method for managing network interfaces of multiple wireless module devices and terminal device | |
| CN105577420A (en) | Method and system for automatic generation of server network topology | |
| CN114338594B (en) | ARP (Address resolution protocol) response-substituting method, device, equipment and storage medium in Kubernetes environment | |
| US10015650B2 (en) | Dynamic branding based on baseboard management controller | |
| CN105516386B (en) | A kind of server management system MAC Address collision detection and processing method and system | |
| CN110688146A (en) | Method, device and storage medium for dynamically configuring monitoring system | |
| CN110825772A (en) | Method and device for synchronizing memory data of multiple service instances and storage medium | |
| CN110928681A (en) | Data processing method and device, storage medium and electronic device | |
| CN111542035A (en) | Cloud service connection method, system and related equipment | |
| CN112954088A (en) | Equipment address allocation method and equipment of CAN network and electronic equipment | |
| CN109933595B (en) | Internet of things equipment information sharing system and device and terminal equipment | |
| CN107086937A (en) | A kind of monitoring method and equipment | |
| CN110851334A (en) | Flow statistical method, electronic device, system and medium | |
| CN114844833A (en) | Message processing method and system, storage medium and computer terminal | |
| WO2016202016A1 (en) | Device management method, apparatus and system | |
| WO2020000657A1 (en) | Method and apparatus for establishing operation and maintenance monitoring connection, terminal device, and medium | |
| CN114070755B (en) | Virtual machine network flow determination method and device, electronic equipment and storage medium | |
| CN105281944B (en) | Method for setting network protocol address and service management system | |
| CN101656722B (en) | Method for generating dynamic host configuration protocol (DHCP) snooping binding information, and device thereof | |
| CN110505075B (en) | Device management method and related device | |
| CN112804276A (en) | Virtualization broadband remote access server, control method thereof and communication system | |
| CN108282374B (en) | Method, system and readable storage medium for configuring NCSI network card |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20191213 |