CN107070719B - Equipment management method and device - Google Patents
Equipment management method and device Download PDFInfo
- Publication number
- CN107070719B CN107070719B CN201710271574.6A CN201710271574A CN107070719B CN 107070719 B CN107070719 B CN 107070719B CN 201710271574 A CN201710271574 A CN 201710271574A CN 107070719 B CN107070719 B CN 107070719B
- Authority
- CN
- China
- Prior art keywords
- management
- local link
- specified type
- managed
- link address
- 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.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/085—Retrieval of network configuration; Tracking network configuration history
- H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
Abstract
the application provides a device management method and a device, and the method comprises the following steps: acquiring a local link address of a managed device and an output interface corresponding to the managed device on a management device; generating a specified type message for requesting management information according to the local link address; sending the specified type message through the output interface; receiving a response message which is returned by the managed equipment and aims at the specified type message, and analyzing the management information of the managed equipment from the response message; and managing the managed equipment according to the management information. By the technical scheme, bandwidth overhead caused by broadcast messages can be effectively avoided, bandwidth resources are saved, and management information of each managed device can be accurately collected.
Description
Technical Field
The present application relates to the field of network management technologies, and in particular, to a device management method and apparatus.
Background
in a traditional cloud computing platform, computing resources, storage resources, network resources and the like are respectively managed by using different management platforms, so that management is complex. Based on this, a Unified management matrix of UIS (Unified Infrastructure System) is proposed, which can integrate computing resources, storage resources, network resources, etc., and manage all resources in a Unified manner.
The UIS unified management matrix can provide a graphical user interface and a simplified operation mode, so that the connection and management of the network are more intuitive and clear. When the UIS unified management matrix is used for carrying out unified management on computing resources, storage resources and network resources, the network topology among the devices can be obtained and displayed, so that a user can know the connection relation among the devices according to the network topology, and the user management is facilitated.
Disclosure of Invention
the application provides a device management method, which is applied to management devices and comprises the following steps:
Acquiring a local link address of a managed device and an output interface corresponding to the managed device on a management device;
generating a specified type message for requesting management information according to the local link address;
sending the specified type message through the output interface;
Receiving a response message which is returned by the managed equipment and aims at the specified type message, and analyzing the management information of the managed equipment from the response message;
And managing the managed equipment according to the management information.
The application provides a device management method, which is applied to managed devices and comprises the following steps:
receiving a specified type message which is sent by a management device and used for requesting management information, wherein the specified type message is generated by the management device according to a local link address of the managed device;
Generating a response message carrying the management information of the managed device for the specified type message;
and sending the response message to the management equipment, so that the management equipment analyzes the management information from the response message and manages the managed equipment according to the management information.
the application provides a device management apparatus, is applied to the management equipment, the device includes:
The management device comprises an acquisition module, a management module and a management module, wherein the acquisition module is used for acquiring a local link address of a managed device and an output interface corresponding to the managed device on the management device;
A generating module, configured to generate a specified type message for requesting management information according to the local link address;
The sending module is used for sending the specified type message through the outgoing interface;
a receiving module, configured to receive a response message for the specified type of message returned by the managed device, and parse management information of the managed device from the response message;
and the management module is used for managing the managed equipment according to the management information.
The application provides a device management apparatus, is applied to by managed equipment, the device includes:
A receiving module, configured to receive a specified type message sent by a management device and used for requesting management information, where the specified type message is generated by the management device according to a local link address of the managed device;
A generating module, configured to generate a response message for the specified type of message; wherein the response message carries management information of the managed device;
And the sending module is used for sending the response message to the management equipment so that the management equipment can analyze the management information from the response message and manage the managed equipment according to the management information.
Based on the above technical solution, in the embodiment of the present application, the management device may send a specified type message to the managed device based on the local link address of the managed device, where the specified type message is a unicast message, rather than a broadcast message, so as to effectively avoid bandwidth overhead caused by the broadcast message and save bandwidth resources. Moreover, the management device can conveniently collect the management information of the managed devices, manage the managed devices according to the management information, accurately collect the management information of each managed device, and the collection mode is simple and effective.
Drawings
in order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments of the present application or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art according to the drawings of the embodiments of the present application.
FIG. 1 is a schematic diagram of an application scenario in an embodiment of the present application;
FIG. 2 is a flow chart of a device management method in one embodiment of the present application;
FIGS. 3A and 3B are schematic diagrams of a format of a specified type of message in one embodiment of the present application;
FIG. 4 is a flow chart of a device management method in another embodiment of the present application;
fig. 5 is a block diagram of a device management apparatus according to an embodiment of the present application;
FIG. 6 is a hardware block diagram of a management device in one embodiment of the present application;
Fig. 7 is a block diagram of a device management apparatus according to an embodiment of the present application;
Fig. 8 is a hardware configuration diagram of a managed device according to an embodiment of the present application.
Detailed Description
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein is meant to encompass any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. Depending on the context, moreover, the word "if" as used may be interpreted as "at … …" or "when … …" or "in response to a determination".
In an actual network environment, different manufacturers and different types of devices are often connected together, and in order to effectively manage the devices, the UIS Unified management matrix may use a UTP (Unified Infrastructure System Manager, Unified Infrastructure System management) Transport Protocol, that is, a UISM Transport Protocol), and the UTP generally uses broadcast messages to discover and manage the devices. Moreover, the UIS uniform management matrix may bring a relatively large bandwidth overhead when transmitting the broadcast message.
in view of the above discovery, an embodiment of the present application provides a device management method, which may be applied to a management device (e.g., UIS unified management matrix), where the management device may manage multiple types of devices, and for convenience of description, the multiple types of devices are referred to as managed devices, and the managed devices may include, but are not limited to, one or any combination of the following: routers, switches, firewall devices, load balancing devices, servers (e.g., rack servers or blade servers located within a chassis, etc.), virtual switches, and so forth.
referring to fig. 1, which is a schematic view of an application scenario of the embodiment of the present application, a management device, a managed device 1, a managed device 2, a managed device 3, and a managed device 4 are located in the same subnet. In the application scenario, referring to fig. 2, a flowchart of the device management method is shown, and the method may be applied to a management device.
Step 201, obtaining a local link address (i.e. link-local address) of the managed device, and an outgoing interface on the management device corresponding to the managed device. Specifically, the management device may select a local link address of the managed device from the local link address table, and an egress interface of the management device corresponding to the managed device.
Before step 201, a generation process of the local link address table may be further included, and the generation process of the local link address table may include, but is not limited to: and acquiring the local link address of the managed device and the output interface corresponding to the managed device on the management device from the neighbor information table, and recording the corresponding relation between the acquired local link address and the acquired output interface in the local link address table.
the neighbor information table may be used to record a local link address of a managed device located in the same subnet as the management device and an outgoing interface on the management device corresponding to the managed device.
the maintenance process of the above-mentioned neighbor information table and local link address table will be described in detail below.
Case one, maintenance process of neighbor information table.
As shown in fig. 1, the management device, the managed device 1, the managed device 2, the managed device 3, and the managed device 4 are located in the same subnet, and all these devices run a Neighbor Discovery Protocol (NDP) of IPv 6. Based on the neighbor discovery protocol, the devices can discover each other's existence, determine each other's local link address, and record the corresponding relationship between the local link address and the outgoing interface in the neighbor information table.
For example, the managed device 1 sends an IPv6 control information packet carrying the local link address 1 in a broadcast manner, and after receiving the IPv6 control information packet through the interface 1, the management device may record the correspondence between the local link address 1 and the interface 1 in the neighbor information table. Similarly, the management device may record, in the neighbor information table, a correspondence between the local link address 3 of the managed device 3 and the interface 1, a correspondence between the local link address 2 of the managed device 2 and the interface 2, and a correspondence between the local link address 4 of the managed device 4 and the interface 2, and finally, an example of the neighbor information table maintained by the management device may be as shown in table 1. Of course, the neighbor information table may also include other contents, and the maintenance process of the neighbor information table is not described in detail.
TABLE 1
| Local link address | Outlet interface |
| Local link address 1 | Interface 1 |
| Local link address 2 | Interface 2 |
| Local link address 3 | Interface 1 |
| Local link address 4 | Interface 2 |
Case two, a maintenance process of a local link address table (link-local address table).
In one example, the management device may create and maintain a local link address table that records the correspondence of local link addresses to outbound interfaces (i.e., outbound interfaces on the management device that correspond to the local link addresses). Specifically, the management device may obtain a local link address (i.e., a local link address of the managed device) and an outbound interface corresponding to the local link address from the neighbor information table, and may record a corresponding relationship between the obtained local link address and the obtained outbound interface in the local link address table.
In the maintenance process of the local link address table, the management device does not need to interact with the managed device, and can directly acquire the local link address and the corresponding output interface from the neighbor information table. In practical application, the management device may obtain all local link addresses and corresponding outgoing interfaces from the neighbor information table, or may obtain part of the local link addresses and corresponding outgoing interfaces from the neighbor information table, which is not limited herein.
In one example, each device running the neighbor discovery protocol may start an NDP timer, the timeout time of which is M seconds (e.g., 10 seconds), based on which each device periodically sends IPv6 control information messages, and the management device may periodically (e.g., every 10 seconds) receive IPv6 control information messages and update the neighbor information table. In addition, the management device may also start a link timer for the local link address table, where the timeout time of the link timer is N seconds (e.g., 1 second), based on the link timer, the management device may periodically obtain the local link address and the corresponding outgoing interface from the neighbor information table, and update the local link address table according to the obtained local link address and the obtained outgoing interface.
The timeout time M of the NDP timer and the timeout time N of the link timer may be configured empirically, which is not limited. During the configuration process, the timeout time N may be less than the timeout time M, for example, the timeout time N is one tenth of the timeout time M. Because the timeout time N is less than the timeout time M, when the neighbor information table changes, the changed content can be updated to the local link address table in time, so that the updating speed of the local link address table is increased, and the content of the local link address table is guaranteed to have timeliness.
When managed equipment located in the same subnet as the management equipment is increased and the NDP timer is overtime, the management equipment can update a neighbor information table, wherein the updated neighbor information table comprises the local link address of the newly increased managed equipment; when the link timer is overtime, the management equipment can update the local link address table according to the neighbor information table, and the overtime N is far shorter than the overtime M, so that the local link address table is updated in time, and the timeliness of the local link address table is ensured. When the managed device located in the same subnet as the management device is reduced and the NDP timer is timed out, the management device can update the neighbor information table, wherein the updated neighbor information table does not include the local link address of the managed device which leaves; when the link timer is overtime, the management equipment can update the local link address table according to the neighbor information table, and the overtime N is far shorter than the overtime M, so that the local link address table is updated in time, and the timeliness of the local link address table is ensured.
Step 202, a specified type message for requesting management information is generated based on the local link address.
In one example, after the local link address and the corresponding egress interface are selected from the local link address table, a specified type message for requesting the management information may be generated according to the local link address. Specifically, a Media Access Control (MAC) address corresponding to the local link address may be determined, and the MAC address is added to a destination MAC field of the specified type message, and the local link address is added to a destination IP field of the specified type message; or determining the MAC address corresponding to the local link address and adding the MAC address to the destination MAC field of the specified type of message.
for example, if the specified type message is in IPv6 format, the MAC address corresponding to the local link address may be determined, and the MAC address may be added to the destination MAC field of the specified type message, and the local link address may be added to the destination IPv6 field of the specified type message. Alternatively, if the specified type message is not in IPv6 format, the MAC address corresponding to the local link address may be determined and added to the destination MAC field of the specified type message.
in one example, the specified type of message may include, but is not limited to: messages based on link layer management protocols, such as unified infrastructure system management type messages, i.e. UISM type messages, such as UTP messages. The specified type message may or may not be in the IPv6 format, and the specified type message in the IPv6 format and the specified type message in the IPv6 format will be described below.
case one, as shown in fig. 3A, is a schematic diagram of a specified type message that is not in IPv6 format.
In one example, the following fields may be included in the specified type of message, but are not limited to: a destination MAC field, a source MAC field, a message type field, a data content field, an FCS (Frame Check Sequence) field. The destination MAC field is the MAC address corresponding to the local link address, but not the broadcast MAC address; the source MAC field is the MAC address of the management equipment; the message type field is a preset value (such as 0xAAB0) to indicate that the current message is a specified type message; the FCS field is check data used for checking a specific type of message, and a specific check method is not limited.
Further, the data content field may include a Head TLV, one or more optional TLVs, and a padding TLV in sequence. In each TLV, a Type field, a Length field, and a Value field are included, the Length of the Type field is 1 byte, the Length of the Length field is 2 bytes, and the Length of the Value field is determined by the Length. Moreover, the content of the optional TLV can be configured according to actual needs, and the optional TLV is explained in the following process. Moreover, when the total length of the specified type message is smaller than a preset value (e.g. 64 bytes), a padding TLV may be added so that the total length of the specified type message is not smaller than the preset value; when the total length of the specified type message is not less than the preset value, the padding TLV may not be added.
Further, the Head TLV may further include, but is not limited to, the following fields: a Magic (type) field, a Module field, an OpCode field, a FeedBack field, and a Reserve field. The Magic field takes a value of a predetermined value (e.g., 0xFF02CAFE) to indicate that the current message is a specified type message, for example, a message that is considered to be a specified type message only if the message type field is a predetermined value of 0xAAB0 and the Magic field is a predetermined value of 0xFF02 CAFE. The value range of the Module field is 0x0000-FFFF, which is used for indicating the Module to which the specified type message belongs. The OpCode field ranges from 0x0000-FFFF to indicate the OpCode specifying the type of message. The FeedBack field is a backfill field, and requires the receiver to return the value of the FeedBack field to the sender without changing. The value of the Reserve field is 0, which is a reserved field reserved for subsequent extensions.
case two, as shown in fig. 3B, is a schematic diagram of a specified type message in IPv6 format.
In one example, the following fields may be included in the specified type of message, but are not limited to: destination MAC field, source MAC field, message type field, IPv6 header field, option field, data content field, FCS field. The destination MAC field is the MAC address corresponding to the local link address, but not the broadcast MAC address; the source MAC field is the MAC address of the management equipment; the message type field is a preset first value (such as 0x86DD) to indicate that the current message carries an IPv6 header field; the optional field is a preset second value (e.g., 0xAAB0) to indicate that the current message is a specified type message; the FCS field is check data used for checking a specific type of message, and a specific checking method is not limited.
In addition, the IPv6 header fields may include, but are not limited to: a version field, a traffic type field, a flow label field, a source IPv6 field, a destination IPv6 field, and the like, the source IPv6 field and the destination IPv6 field are described below, and the other fields are not limited. Wherein the source IPv6 field is the local link address of the managing device and the destination IPv6 field is the local link address of the managed device (i.e., selected in step 101).
Further, the data content field may in turn include a Head TLV, one or more optional TLVs, a padding TLV. Each TLV includes a Type field having a Length of 1 byte, a Length field having a Length of 2 bytes, and a Value field having a Length determined by the Length. The content of the optional TLV can be configured according to actual needs, and the optional TLV is explained in the following process. When the total length of the specified type message is smaller than a preset value (such as 64 bytes), a padding TLV can be added, so that the total length of the specified type message is not smaller than the preset value; when the total length of the specified type message is not less than the preset value, the padding TLV may not be added. The Head TLV described above may also include, but is not limited to: a Magic field, a Module field, an OpCode field, a FeedBack field, and a Reserve field. The Magic field takes a value of a predetermined value (e.g., 0xFF02CAFE) to indicate that the current message is a specified type message, for example, a message that is considered to be a specified type message only if the optional field is a predetermined value of 0xAAB0 and the Magic field is a predetermined value of 0xFF02 CAFE. The value range of the Module field is 0x0000-FFFF, which is used for indicating the Module to which the specified type message belongs. The OpCode field ranges from 0x0000-FFFF to indicate the OpCode specifying the type of message. The feed back field is a backfill field, and the receiver is required to return the value of the feed back field to the sender without changing the value. The value of the Reserve field is 0, which is a reserved field reserved for subsequent extensions.
For the above first and second cases, the destination MAC field is the MAC address corresponding to the local link address, and for the process of "determining the MAC address corresponding to the local link address", then: in practical applications, after the device enables IPv6, each interface of the device may automatically generate a local link address, where the last 64 bits of the local link address are an interface identifier, and the interface identifier is generated based on a 48-bit MAC address, so that after the management device obtains the local link address, the management device may first resolve the last 64 bits of the local link address, that is, the interface identifier, and then convert the last 64-bit interface identifier into the 48-bit MAC address, where the 48-bit MAC address is the MAC address corresponding to the local link address.
for example, one example of a policy for generating a 64-bit interface identifier using a 48-bit MAC address may be: the hexadecimal number 0xFF-FE is inserted between the third and fourth bytes of the MAC address and the "global/local" bit (the second lowest bit of the starting byte of the MAC address) is negated and set to 0 if it is 1 and to 1 if it is 0. For example, for MAC address 00-60-08-52-F9-D8, the hexadecimal number 0xFF-FE is inserted between 0x08 (the third byte) and 0x52 (the fourth byte), forming 64-bit address 00-60-08-FF-FE-52-F9-D8; then, the "global/local" bit (i.e., the second least significant bit of 0x00 (the first byte)) is negated, which is 1 since the second least significant bit of 0x00 is 0, i.e., the first byte, 0x00, is changed to 0x02, and in summary, the interface identifier corresponding to MAC address 00-60-08-52-F9-D8 is 02-60-08-FF-FE-52-F9-D8. Based on the inverse operation of the above strategy, the 64-bit interface identifier can be converted into a 48-bit MAC address, and the conversion process is not described in detail.
For the above cases one and two, for the optional TLV in the data content field, the optional TLV may include, but is not limited to, the following types of TLVs: and the IP TLV is used for carrying a management address (such as a management IP address) of the management equipment, so that the managed equipment receiving the specified type message determines whether the specified type message is legal or not according to the management address, and the subsequent process introduces a process for determining the legality.
Wherein, for the management device, each interface of the management device has a local link address (i.e. IPv6 address), and the source IPv6 field of the IPv6 header carries the local link address of the management device, such as when a specified type message is sent through interface 1, the source IPv6 field carries the local link address of interface 1. In contrast, the management device further has a management IP address, which is specific to the management device and not specific to the interface of the management device, and the function of the management IP address may be: the managed device recognizes that the specified type of message is from the managing device based on this management IP address. Specifically, since the management device includes many interfaces, if it is identified whether the specified type message is from the management device based on the local link address carried in the field of the source IPv6, the local link address of each interface of the management device needs to be configured on the managed device, and the configuration workload is large. Therefore, in the embodiment of the application, the management IP address of the management device can be configured on the managed device, so that the managed device can identify that the specified type of message comes from the management device based on the management IP address only by configuring one management IP address on the managed device.
Moreover, if the management IP address (carried in the data content field) carried by the specified type message matches (if the management IP address and the management IP address are the same) with the management IP address of the management device configured on the managed device, the managed device may determine that the specified type message is legal; otherwise, the managed device may determine that the specified type of message is not legitimate.
and step 203, sending the specified type message through the obtained outgoing interface.
In one example, after the local link address and the outbound interface are selected from the local link address table and the specified type message is generated, the specified type message may be sent through the outbound interface.
furthermore, since the destination MAC address of the specified type message is a MAC address corresponding to the local link address, not a broadcast MAC address, the specified type message is transmitted in a unicast manner.
And step 204, receiving a response message for the specified type message returned by the managed device, and analyzing the management information of the managed device from the response message. The management information may include, but is not limited to, one or any combination of the following: management address, device type, device serial number of managed device.
in one example, after receiving the specified type of message sent by the management device, the managed device may generate a response message carrying management information of the managed device, and send the response message to the management device.
for example, the management apparatus may set an OpCode field of the specified type message to a preset flag (e.g., 01) to indicate that the specified type message is used to request management information. After the managed device receives the specified type message, if the OpCode field of the specified type message is analyzed to be the preset identifier, the management information of the managed device can be obtained, a response message carrying the management information is generated, and the response message is sent to the management device.
In an example, the specified type message may further include a management address (e.g., a management IP address) of the management device, and after receiving the specified type message, the managed device may determine that the specified type message is legal if the management address (carried in the data content field) carried in the specified type message matches (e.g., is the same as) the management address of the locally preset management device; otherwise, the specified type of message is determined to be illegal.
In one example, the format of the response message is similar to the format of the specified type message, e.g., if the specified type message is not in IPv6 format, the response message is not in IPv6 format, and if the specified type message is in IPv6 format, the response message is in IPv6 format. The specified type of message and the response message differ in that: the optional TLVs of the data content fields are different, for example, the optional TLVs of the specified type message include an IP TLV for carrying the management address of the management device. And the optional TLV of the response message may include: the Device management system comprises an IP TLV, a Device Type TLV and a Device SN TLV, wherein the IP TLV is used for carrying a management address (such as a management IP address) of a managed Device, the Device Type TLV is used for carrying a Device Type of the managed Device, and the Device SN TLV is used for carrying a Device serial number of the managed Device.
in the response message, the destination MAC field is the MAC address of the managing device, the source MAC field is the MAC address of the managed device, the destination IPv6 field is the local link address of the managing device, and the source IPv6 field is the local link address of the managed device. Furthermore, the local link address of the managed device is not the same as the management address of the managed device, the local link address of the managed device is for the interface of the managed device, and the management address of the managed device is for the managed device, not for the interface of the managed device.
The function of the managed address of this managed device may be: the management device recognizes that the response message is from the managed device based on the management address, and manages the managed device based on the management address.
Step 205, managing the managed device according to the management information of the managed device.
For example, the management device may implement a management process for the managed device according to management information such as a management address, a device type, and a device serial number of the managed device, and the management process is not limited.
Based on the above technical solution, in the embodiment of the present application, the management device may send a specified type message to the managed device based on the local link address of the managed device, where the specified type message is a unicast message, rather than a broadcast message, so that bandwidth overhead caused by the broadcast message may be effectively avoided, and bandwidth resources are saved. Moreover, the management device can conveniently collect the management information of the managed devices, manage the managed devices according to the management information, accurately collect the management information of each managed device, and the collection mode is simple and effective.
Moreover, in an actual network, the management IP addresses of different managed devices may be the same, but the local link addresses of different managed devices are different, so in the embodiment of the present application, when the management device sends a specified type message, the destination IPv6 field of the specified type message is the local link address of the managed device, but not the management IP address of the managed device, and therefore the risk caused by IP address collision can be effectively avoided.
based on the same application concept as the method, an apparatus management method is also proposed in the embodiment of the present application, and as shown in fig. 4, the method is a flowchart of the apparatus management method, and the method can be applied to managed apparatuses.
Step 401, receiving a specified type message sent by a management device for requesting management information, where the specified type message may be generated by the management device according to a local link address of the managed device.
Step 402, generating a response message carrying management information of the managed device for the specified type of message.
Step 403, sending the response message to the management device, so that the management device parses the management information of the managed device from the response message, and manages the managed device according to the management information.
In one example, the management information may include, but is not limited to, one or any combination of the following: management address, device type, device serial number of managed device. The specified type of message may include, but is not limited to: messages based on a link layer management protocol. In addition, the specified type message may further include a management address of the management device, and after the managed device receives the specified type message, if the management address carried in the specified type message matches with a locally preset management address, it determines that the specified type message is legal, and performs step 402 and step 403; otherwise, it is determined that the specified type of message is not legitimate, step 402 and step 403 are not performed.
Based on the same application concept as the method described above, an embodiment of the present application further provides an apparatus management device, which is applied to manage devices, and as shown in fig. 5, is a structural diagram of the apparatus management device, and includes:
An obtaining module 11, configured to obtain a local link address of a managed device and an output interface on a management device, where the output interface corresponds to the managed device;
a generating module 12, configured to generate a specified type message for requesting management information according to the local link address;
A sending module 13, configured to send the specified type message through the outgoing interface;
a receiving module 14, configured to receive a response message, which is returned by the managed device and is for the specified type of message, and parse the management information of the managed device from the response message;
and the management module 15 is configured to manage the managed device according to the management information.
The obtaining module 11 is specifically configured to, in a process of obtaining a local link address of a managed device and an egress interface corresponding to the managed device on a management device, select a local link address of the managed device and an egress interface corresponding to the managed device on the management device from a local link address table;
The obtaining module 11 is further configured to, in a generation process of the local link address table, obtain a local link address of a managed device and an outgoing interface, corresponding to the managed device, on the management device from a neighbor information table, and record a corresponding relationship between the obtained local link address and the obtained outgoing interface in the local link address table; the neighbor information table is used for recording the local link address of the managed device located in the same subnet as the management device and the output interface corresponding to the managed device on the management device.
the generating module 12 is specifically configured to, in a process of generating a specified type message for requesting management information according to the local link address, determine a MAC address corresponding to the local link address, add the MAC address to a destination MAC field of the specified type message, and add the local link address to a destination IP field of the specified type message; or determining the MAC address corresponding to the local link address, and adding the MAC address to the destination MAC field of the specified type message.
For the management device provided in the embodiment of the present application, a schematic diagram of a hardware architecture may be shown in fig. 6. Fig. 6 is a schematic diagram of a hardware configuration of the management apparatus. The method comprises the following steps: a machine-readable storage medium and a processor, wherein:
a machine-readable storage medium: the instruction code is stored.
a processor: the device management operations disclosed in the above examples of the present application are implemented by communicating with a machine-readable storage medium, reading and executing the instruction codes stored in the machine-readable storage medium.
here, a machine-readable storage medium may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and so forth. For example, the machine-readable storage medium may be: a RAM (random Access Memory), a volatile Memory, a non-volatile Memory, a flash Memory, a storage drive (e.g., a hard drive), a solid state drive, any type of storage disk (e.g., an optical disk, a dvd, etc.), or similar storage medium, or a combination thereof.
Based on the same application concept as the method, an embodiment of the present application further provides an apparatus management device, which is applied to a managed apparatus, and as shown in fig. 7, is a structural diagram of the apparatus management device, and includes:
a receiving module 21, configured to receive a specified type message sent by a management device and used for requesting management information, where the specified type message is generated by the management device according to a local link address of a managed device;
A generating module 22, configured to generate a response message for the specified type of message; wherein the response message carries management information of the managed device;
the sending module 23 is configured to send the response message to the management device, so that the management device analyzes management information from the response message, and manages the managed device according to the management information.
Fig. 8 may be referred to as a hardware architecture diagram of the managed device provided in the embodiment of the present application. FIG. 8 is a diagram of the hardware architecture of a managed device. The method comprises the following steps: a machine-readable storage medium and a processor, wherein:
A machine-readable storage medium: the instruction code is stored.
a processor: the device management operations disclosed in the above examples of the present application are implemented by communicating with a machine-readable storage medium, reading and executing the instruction codes stored in the machine-readable storage medium.
Here, a machine-readable storage medium may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and so forth. For example, the machine-readable storage medium may be: a RAM (random Access Memory), a volatile Memory, a non-volatile Memory, a flash Memory, a storage drive (e.g., a hard drive), a solid state drive, any type of storage disk (e.g., an optical disk, a dvd, etc.), or similar storage medium, or a combination thereof.
the systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.
as will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
furthermore, these computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (which may include, but is not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (11)
1. A device management method is applied to a management device, and comprises the following steps:
acquiring a local link address of a managed device and an output interface corresponding to the managed device on a management device;
Generating a specified type message for requesting management information according to the local link address;
Sending the specified type message through the output interface;
Receiving a response message which is returned by the managed equipment and aims at the specified type message, and analyzing the management information of the managed equipment from the response message;
and managing the managed equipment according to the management information.
2. the method according to claim 1, wherein the process of acquiring the local link address of the managed device and managing the outgoing interface corresponding to the managed device on the device specifically includes:
Selecting a local link address of a managed device and an output interface corresponding to the managed device on the management device from a local link address table; wherein, the generation process of the local link address table comprises:
Acquiring a local link address of a managed device and an outgoing interface corresponding to the managed device on the management device from a neighbor information table, and recording a corresponding relation between the acquired local link address and the acquired outgoing interface in the local link address table;
the neighbor information table is used for recording the local link address of the managed device located in the same subnet as the management device and the outgoing interface corresponding to the managed device on the management device.
3. the method according to claim 1, wherein the process of generating a specified type of message for requesting management information according to the local link address specifically includes:
Determining a MAC address corresponding to the local link address, adding the MAC address to a destination MAC field of the specified type message, and adding the local link address to a destination IP field of the specified type message; alternatively, the first and second electrodes may be,
and determining a MAC address corresponding to the local link address, and adding the MAC address to a destination MAC field of the specified type message.
4. the method of claim 1,
the specified type message also comprises a management address of the management device, so that the managed device receiving the specified type message determines whether the specified type message is legal or not according to the management address.
5. The method of claim 1, wherein the management information of the managed device comprises one or any combination of the following: the management address, the device type and the device serial number of the managed device.
6. a device management method is applied to managed devices, and comprises the following steps:
Receiving a specified type message which is sent by a management device and used for requesting management information, wherein the specified type message is generated by the management device according to a local link address of the managed device;
Generating a response message carrying the management information of the managed device for the specified type message;
and sending the response message to the management equipment, so that the management equipment analyzes the management information from the response message and manages the managed equipment according to the management information.
7. The method of claim 6, wherein the management information comprises one or any combination of the following: the management address, the equipment type and the equipment serial number of the managed equipment;
the specified type message also comprises a management address of the management equipment, and after the specified type message is received, if the management address carried by the specified type message is matched with a locally preset management address, the specified type message is determined to be legal; otherwise, determining that the specified type of message is illegal.
8. An apparatus for managing devices, the apparatus comprising:
The management device comprises an acquisition module, a management module and a management module, wherein the acquisition module is used for acquiring a local link address of a managed device and an output interface corresponding to the managed device on the management device;
a generating module, configured to generate a specified type message for requesting management information according to the local link address;
The sending module is used for sending the specified type message through the outgoing interface;
A receiving module, configured to receive a response message for the specified type of message returned by the managed device, and parse management information of the managed device from the response message;
and the management module is used for managing the managed equipment according to the management information.
9. The apparatus of claim 8,
The acquiring module is specifically configured to, in a process of acquiring a local link address of a managed device and an egress interface corresponding to the managed device on a management device, select the local link address of the managed device and the egress interface corresponding to the managed device on the management device from a local link address table;
the acquiring module is further configured to acquire a local link address of the managed device and an outgoing interface, corresponding to the managed device, on the management device from a neighbor information table in a generation process of the local link address table, and record a corresponding relationship between the acquired local link address and the acquired outgoing interface in the local link address table; the neighbor information table is used for recording the local link address of the managed device located in the same subnet as the management device and the output interface corresponding to the managed device on the management device.
10. the apparatus of claim 8,
The generating module is specifically configured to, in a process of generating a specified type message for requesting management information according to the local link address, determine a MAC address corresponding to the local link address, add the MAC address to a destination MAC field of the specified type message, and add the local link address to a destination IP field of the specified type message; or determining the MAC address corresponding to the local link address, and adding the MAC address to the destination MAC field of the specified type message.
11. An apparatus for managing a device, the apparatus being adapted for use with a managed device, the apparatus comprising:
A receiving module, configured to receive a specified type message sent by a management device and used for requesting management information, where the specified type message is generated by the management device according to a local link address of the managed device;
A generating module, configured to generate a response message for the specified type of message; wherein the response message carries management information of the managed device;
and the sending module is used for sending the response message to the management equipment so that the management equipment can analyze the management information from the response message and manage the managed equipment according to the management information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710271574.6A CN107070719B (en) | 2017-04-24 | 2017-04-24 | Equipment management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710271574.6A CN107070719B (en) | 2017-04-24 | 2017-04-24 | Equipment management method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107070719A CN107070719A (en) | 2017-08-18 |
| CN107070719B true CN107070719B (en) | 2019-12-06 |
Family
ID=59603985
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710271574.6A Active CN107070719B (en) | 2017-04-24 | 2017-04-24 | Equipment management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107070719B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111511041B (en) * | 2019-01-31 | 2022-03-29 | 大唐移动通信设备有限公司 | Remote connection method and device |
| CN110808950B (en) * | 2019-09-25 | 2022-06-28 | 西安广和通无线软件有限公司 | Message processing method, device, computer equipment and storage medium |
| CN112631786A (en) * | 2020-12-30 | 2021-04-09 | 上海玖道信息科技股份有限公司 | Unified management automatic processing system of heterogeneous load balancing equipment |
| CN113076263A (en) * | 2021-05-06 | 2021-07-06 | 北京字节跳动网络技术有限公司 | Process running method and device, computer equipment and storage medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1411214A (en) * | 2002-11-15 | 2003-04-16 | 烽火通信科技股份有限公司 | Network equipment management method based on ethernet technology |
| JP2006173673A (en) * | 2004-12-10 | 2006-06-29 | Canon Inc | Communication apparatus and control method thereof |
| CN1859304A (en) * | 2006-02-13 | 2006-11-08 | 华为技术有限公司 | Method for realizing neighbour discovery |
| CN101018146A (en) * | 2006-02-10 | 2007-08-15 | 北京航空航天大学 | A local management unit for hierarchical mobile IPv6 |
| CN101212773A (en) * | 2006-12-31 | 2008-07-02 | 华为技术有限公司 | Method and system supporting movement of mobile network |
| CN101304368A (en) * | 2004-06-03 | 2008-11-12 | 华为技术有限公司 | Method for conveying tactics information between network equipments |
| CN102377835A (en) * | 2010-08-20 | 2012-03-14 | 杭州华三通信技术有限公司 | Communication method and device for network element group network |
| CN102629915A (en) * | 2012-04-28 | 2012-08-08 | 杭州华三通信技术有限公司 | Method and device for improving rate of utilization of hardware entry |
| CN104113463A (en) * | 2014-07-24 | 2014-10-22 | 深圳市共进电子股份有限公司 | Network bridge based data message processing method, device and network bridge |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9148845B2 (en) * | 2013-09-23 | 2015-09-29 | Mitsubishi Electric Research Laboratories, Inc. | Method for discovering neighboring nodes in wireless networks |
-
2017
- 2017-04-24 CN CN201710271574.6A patent/CN107070719B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1411214A (en) * | 2002-11-15 | 2003-04-16 | 烽火通信科技股份有限公司 | Network equipment management method based on ethernet technology |
| CN101304368A (en) * | 2004-06-03 | 2008-11-12 | 华为技术有限公司 | Method for conveying tactics information between network equipments |
| JP2006173673A (en) * | 2004-12-10 | 2006-06-29 | Canon Inc | Communication apparatus and control method thereof |
| CN101018146A (en) * | 2006-02-10 | 2007-08-15 | 北京航空航天大学 | A local management unit for hierarchical mobile IPv6 |
| CN1859304A (en) * | 2006-02-13 | 2006-11-08 | 华为技术有限公司 | Method for realizing neighbour discovery |
| CN101212773A (en) * | 2006-12-31 | 2008-07-02 | 华为技术有限公司 | Method and system supporting movement of mobile network |
| CN102377835A (en) * | 2010-08-20 | 2012-03-14 | 杭州华三通信技术有限公司 | Communication method and device for network element group network |
| CN102629915A (en) * | 2012-04-28 | 2012-08-08 | 杭州华三通信技术有限公司 | Method and device for improving rate of utilization of hardware entry |
| CN104113463A (en) * | 2014-07-24 | 2014-10-22 | 深圳市共进电子股份有限公司 | Network bridge based data message processing method, device and network bridge |
Non-Patent Citations (2)
| Title |
|---|
| "IPv6 链路本地地址安全技术研究";孙文歌等;《计算机技术与发展》;20111031;第 21 卷(第 10 期);全文 * |
| "IPv6单播数据转发技术分析与研究";方诗虹;《万方数据》;20061117;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107070719A (en) | 2017-08-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112422393B (en) | Method for transmitting message of extensible virtual local area network, computer equipment and readable medium | |
| CN106412142B (en) | Resource equipment address obtaining method and device | |
| CN110635987B (en) | Message transmission method, device, equipment and machine readable storage medium | |
| CN107070719B (en) | Equipment management method and device | |
| CN107580079B (en) | Message transmission method and device | |
| CN108259347B (en) | Message transmission method and device | |
| CN106878194B (en) | Message processing method and device | |
| US20120131225A1 (en) | Data center network system and packet forwarding method thereof | |
| CN106878199B (en) | Configuration method and device of access information | |
| CN106921578B (en) | Method and device for generating forwarding table item | |
| CN108965092B (en) | Data message transmission method and device | |
| CN107770072B (en) | Method and equipment for sending and receiving message | |
| CN110580256A (en) | Method, device and system for identifying application identifier | |
| CN106453681B (en) | IP address allocation method and device | |
| CN108667888B (en) | Load balancing method and device | |
| CN107547346B (en) | Message transmission method and device | |
| WO2012146120A1 (en) | Method for forwarding response packet from dhcp server, forwarding device and system | |
| CN112887229B (en) | Session information synchronization method and device | |
| US20220393908A1 (en) | Message Encapsulation Method and Apparatus, and Message Decapsulation Method and Apparatus | |
| US20150256459A1 (en) | Packet processing method and apparatus | |
| US20160028628A1 (en) | Communication system, control apparatus, address allocation method, and program | |
| EP3503484B1 (en) | Message transmission methods and devices | |
| EP2951979B1 (en) | A method of and a unit handling a protocol address in a network | |
| CN103746768A (en) | Data packet identification method and equipment thereof | |
| CN102833287B (en) | The method of visit data resource in distributed file system and distributed file system |
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 | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 310052 11th Floor, 466 Changhe Road, Binjiang District, Hangzhou City, Zhejiang Province Applicant after: Xinhua Sanxin Information Technology Co., Ltd. Address before: 310052 11th Floor, 466 Changhe Road, Binjiang District, Hangzhou City, Zhejiang Province Applicant before: Huashan Information Technology Co., Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |