CN108259215B - Equipment management method and device - Google Patents
Equipment management method and device Download PDFInfo
- Publication number
- CN108259215B CN108259215B CN201710880571.2A CN201710880571A CN108259215B CN 108259215 B CN108259215 B CN 108259215B CN 201710880571 A CN201710880571 A CN 201710880571A CN 108259215 B CN108259215 B CN 108259215B
- Authority
- CN
- China
- Prior art keywords
- equipment
- network
- group
- management
- tlv
- 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
Images
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/0893—Assignment of logical groups to network elements
-
- 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/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
-
- 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/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- 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/0803—Configuration setting
- H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
- H04L41/0846—Configuration by using pre-existing information, e.g. using templates or copying from other elements based on copy from other elements
-
- 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/12—Discovery or management of network topologies
Abstract
The application provides a device management method and a device, wherein the method is applied to forwarding devices which are designated as network management servers in a network and can comprise the following steps: and broadcasting a member device discovery message in the network, and determining that the network device sending the response message is the member device managed by the device when receiving the response message of the member device discovery message. Sending topology searching messages to each member device, and receiving network topology information returned by each member device; and calculating the topological structure of the network based on the collected topological information of each member device, and displaying the topological structure through the management device. The method provided by the application can realize centralized management of a large number of scattered network devices in a small network and reduce the cost of network device management.
Description
Technical Field
The present application relates to the field of computer communications, and in particular, to a device management method and apparatus.
Background
As the network scale increases, more network devices are required to be used in the network, and thus, management of the network devices becomes critical.
The traditional network device management generally needs to deploy additional servers and network management software, thereby greatly increasing the overhead of network device management. In addition, it is also necessary to ensure that the external network management software is compatible with the version of the managed device. This is costly for small enterprises to simply manage a large number of dispersed network devices, and for simple operation and maintenance of network devices.
Disclosure of Invention
In view of this, the present application provides a device management method and apparatus, so as to reduce the cost of network device management while implementing centralized management of a large number of distributed network devices in a simple network.
Specifically, the method is realized through the following technical scheme:
according to a first aspect of the present application, there is provided a device management method applied to a forwarding device designated as a network management server in a network, the method including:
broadcasting member device discovery messages within the network;
when a response message of the member device discovery message is received, determining that the network device sending the response message is the member device managed by the device;
sending topology collection messages to each member device;
receiving network topology information returned by each member device;
and calculating the topological structure of the network based on the collected topological information of each member device, and displaying the topological structure through the management device.
Optionally, the Type field in the member device discovery message is a designated field, and the Type length value TLV in the Data field is a designated TLV; the Type field in the member device response message is the designated field, and the TLV in the Data field is the designated TLV;
the broadcasting a member device discovery packet within the network includes:
broadcasting a Type field in the network as the designated field, wherein TLV in a Data field is a member device discovery message of the designated TLV;
when receiving a response message of the member device discovery message, the determining that the network device sending the response message is the member device managed by the device includes:
when receiving messages of which the Type field is the designated field and the TLV in the Data field is the designated TLV, determining the received messages as response messages aiming at the discovery messages of the member equipment;
and determining the network equipment which sends the response message as member equipment managed by the equipment.
Optionally, after determining that the network device sending the response packet is a member device managed by the device, the method further includes: grouping the discovered member devices;
the method further comprises the following steps:
and after receiving the software upgrading instruction, upgrading the software of the member equipment in each group by using the software upgrading version corresponding to each group.
Optionally, the software upgrading of the member devices in each group by using the software upgrading version corresponding to each group includes:
aiming at each group, sending a software upgrading version downloading path corresponding to the group to the member equipment in the group so as to enable the member equipment in the group to download the software upgrading version corresponding to the group according to the software upgrading version downloading path;
and controlling the member equipment in the group to use the downloaded software upgrading version to carry out software upgrading when determining that the member equipment in the group finishes downloading the software upgrading version.
Optionally, the member devices discovered are grouped; the method comprises the following steps:
for each discovered member device, determining a device model corresponding to the device identifier of the member device based on a preset corresponding relationship between the device identifier and the device model;
searching a group corresponding to the determined equipment model;
if the member equipment is found, adding the member equipment into the found group;
and if the member equipment is not found, establishing a group corresponding to the determined equipment model, and adding the found member equipment to the newly established group.
Optionally, the method further includes:
when a member device fails, determining a newly accessed network device that replaces the failed member device;
and synchronizing the configuration information of the fault member equipment to the determined newly accessed network equipment so that the newly accessed network equipment replaces the fault member equipment to work.
Optionally, the determining a newly accessed network device to replace the failed member device includes:
detecting whether the newly accessed network equipment meets a replacement condition; the alternative conditions include: the newly accessed network equipment and the fault member equipment have the same equipment model, and the newly accessed network equipment and the fault member equipment have the same neighbor relation;
if so, the newly accessed network device is determined to be the newly accessed network device that replaces the failed member device.
According to a second aspect of the present application, there is provided a device management apparatus applied to a forwarding device designated as a network management server in a network, the apparatus comprising:
a discovery unit, configured to broadcast a member device discovery packet in the network, and determine, when receiving a response packet of the member device discovery packet, that a network device that sends the response packet is a member device managed by the device;
the collecting unit is used for sending topology collecting messages to each member device and receiving network topology information returned by each member device;
and the display unit is used for calculating the topological structure of the network based on the collected topological information of each member device and displaying the topological structure through the management device.
Optionally, the Type field in the member device discovery message is a designated field, and the Type length value TLV in the Data field is a designated TLV; the Type field in the member device response message is the designated field, and the TLV in the Data field is the designated TLV;
the discovery unit is specifically configured to broadcast a Type field as the designated field in the network, where TLV in a Data field is a member device discovery packet of the designated TLV; when receiving messages of which the Type field is the designated field and the TLV in the Data field is the designated TLV, determining the received messages as response messages aiming at the discovery messages of the member equipment; and determining the network equipment which sends the response message as member equipment managed by the equipment.
Optionally, the apparatus further comprises: the grouping unit is used for grouping the discovered member devices after the member devices managed by the management device are discovered;
the device further comprises: and the upgrading unit is used for upgrading the software of the member equipment in each group by using the software upgrading version corresponding to each group after receiving the software upgrading instruction.
Optionally, the upgrading unit is specifically configured to send, for each group, a software upgrade version download path corresponding to the group to the member device in the group, so that the member device in the group downloads the software upgrade version corresponding to the group according to the software upgrade version download path; and controlling the member equipment in the group to use the downloaded software upgrading version to carry out software upgrading when determining that the member equipment in the group finishes downloading the software upgrading version.
Optionally, the grouping unit is specifically configured to, for each discovered member device, determine, based on a preset correspondence between a device identifier and a device model, a device model corresponding to the device identifier of the member device; searching a group corresponding to the determined equipment model; if the member equipment is found, adding the member equipment into the found group; and if the member equipment is not found, establishing a group corresponding to the determined equipment model, and adding the found member equipment to the newly established group.
Optionally, the apparatus further comprises:
a determining unit, configured to determine, when a member device fails, a newly accessed network device that replaces the failed member device;
and the replacing unit is used for synchronizing the configuration information of the fault member equipment to the determined newly-accessed network equipment so as to enable the newly-accessed network equipment to replace the fault member equipment to work.
Optionally, the determining unit is specifically configured to detect whether a newly accessed network device meets a replacement condition; the alternative conditions include: the newly accessed network equipment and the fault member equipment have the same equipment model, and the newly accessed network equipment and the fault member equipment have the same neighbor relation; if so, the newly accessed network device is determined to be the newly accessed network device that replaces the failed member device.
The application aims to provide a device management method for solving the problem of centralized management of distributed network devices for small enterprises or small networks.
On one hand, the method adopts an embedded equipment management mode, and if the specified forwarding equipment in the network is adopted as the management server, the specified forwarding equipment performs self-management on the network, so that the cost for deploying additional management servers is effectively reduced.
On the other hand, the forwarding device serving as the management server can automatically discover the member devices, acquire the topology of the member devices and present the network topology in a graphical manner, and on the basis, grouping the member devices according to the models of the member devices and batch upgrading of software on the member devices based on the grouping are realized; and automatic replacement of the failed member device, thereby realizing management of the member devices in the network.
Drawings
FIG. 1 is a flow chart illustrating a method for device management according to an exemplary embodiment of the present application;
FIG. 2 is a schematic diagram of a network topology shown in an exemplary embodiment of the present application;
FIG. 3 is a flow chart illustrating a member device software upgrade according to an exemplary embodiment of the present application;
FIG. 4 is a flow chart illustrating automatic replacement of a malfunctioning device according to an exemplary embodiment of the present application;
fig. 5 is a hardware structure diagram of a forwarding device where a device management apparatus is located according to an exemplary embodiment of the present application;
fig. 6 is a block diagram of a device management apparatus according to an exemplary embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
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 appended 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 refers to and encompasses 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. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
With the increasing scale of networks, the network edge needs to use a large number of network devices, such as switches, routers, etc., so that the management of these network devices becomes very important.
However, in the conventional network device management technology, an external management server is usually required to be additionally configured to manage the network device, and network management software compatible with each managed device version is also required to be configured. However, this is too costly for small enterprises to manage and maintain network devices such as switches, routers, etc. or for small networks to manage.
In view of the above, the present application aims to provide a device management method for solving the problem of centralized management of distributed network devices for small enterprises or small networks.
On one hand, the method adopts an embedded equipment management mode, and if the specified forwarding equipment in the network is adopted as the management server, the specified forwarding equipment performs self-management on the network, so that the cost for deploying additional management servers is effectively reduced.
On the other hand, the forwarding device serving as the management server can automatically discover the member devices, acquire the topology of the member devices and present the network topology in a graphical manner, and on the basis, grouping the member devices according to the models of the member devices and batch upgrading of software on the member devices based on the grouping are realized; and automatic replacement of the failed member device, thereby realizing management of the member devices in the network.
The device management methods provided herein are described in detail below in terms of automated topology collection of management devices, software upgrades of member devices, and automated replacement of failed member devices. A
1) Automatic topology searching
To better describe the methods provided herein, some concepts used herein are first explained.
The forwarding device as the management server may include a switch, a router, and the like specified by a developer in the network. For convenience of description herein, the forwarding device as the management server is defined as a management device. The management device is mainly used for managing other network devices in the network, such as being responsible for collecting network topology, presenting collected network topology diagrams in visual graphical pages, being responsible for grouping management of member devices, and the like.
It should be noted that, different from the conventional network device management technology, the management device provided in the present application is a forwarding device specified in a managed network, rather than a preset network management tool outside the network, such as a management server, and this embedded network device management method can greatly reduce the cost of network device management.
The member devices, which may also be referred to as managed devices, may cooperate with the management device to gather the topology and complete the management task.
Next, the basic configuration of the member device is explained. The basic configuration may be understood as the minimum configuration for completing the network device management, and the member device can be discovered and managed by the management device after the basic configuration is performed. Network management personnel may manually perform basic configuration on each member device. The member equipment can also automatically acquire basic configuration information through the automatic configuration server to complete basic configuration.
The basic configuration described above may include the following:
LLDP (Link Layer Discovery Protocol) Global enabling, enabling LLDP Protocol, for generating a topological neighbor relation;
STP (Spanning Tree Protocol) Global enabling, enabling STP Protocol, and blocking when a loop is formed in the topology;
interface configuration, for example, creating vlan 1, configuring an ip address dhcp alloc under an interface of interface vlan 1, and using the ip address dhcp alloc to receive and transmit a layer 2,3 management message;
telnet (remote terminal protocol) server (service) enabling, which is used for managing member equipment by management equipment through Telnet, configuring and the like;
local user configuration, which is used for managing the logged member device by the management device, and the configuration information is as follows:
a line (subscriber line, also called user interface) configuration, configured to manage, by a management device, member devices logged in through Telnet, where configuration information is as follows:
NETCONF (Network Configuration) is enabled, and is used for a management device to obtain member device basic information, neighbor information, and the like, where Configuration information is as follows:
finally, automatic topology gathering is described in detail.
Referring to fig. 1, fig. 1 is a flowchart illustrating a network device management method according to an exemplary embodiment of the present application, where the method is applicable to a forwarding device (management device) designated as a network management server in a network, and the method may include the following steps.
Step 101: and the management equipment broadcasts member equipment discovery messages in the network.
Step 102: and when receiving a response message of the member device discovery message, the management device determines that the network device sending the response message is the member device managed by the management device.
In order to prevent other network devices in the network except the management device from being repeatedly discovered by the management device, a state identifier can be configured on the other network devices, and the state identifier can characterize the managed state of the other network devices. The status identifier may include a managed identifier to characterize that the network device has been discovered for management. The status identifier may also include an unmanaged identifier to characterize the network device as being unmanaged. The state identifier has aging time, and for the managed identifier on the network device, when the managed identifier does not receive the periodic heartbeat message sent by the management device in the aging time period, the managed identifier is modified into an unmanaged identifier.
The management device may periodically broadcast member discovery messages within the network. The member discovery message carries information of the management device.
After receiving the member discovery message broadcast by the management device, the other network devices may check their own status identifiers. If the status identifier of the network device is the managed identifier, the network device may not process the broadcast member discovery packet, for example, not record the information of the management device carried in the member discovery packet, or respond to the broadcast member discovery packet. If the status identifier of the network device is an unmanaged identifier, the network device may record the information of the management device carried in the member discovery message, and then send a unicast response message for the member discovery message to the management device, where the response message carries the information of the network device. Meanwhile, the network device can also update the unmanaged identification of the network device to the managed identification.
When the management device receives a response message for the member discovery message returned by the other network device, the management device may determine that the other network device is the member device managed by the management device. The management device may obtain the information of the other network device from the received scan response packet, and add the information of the other network device to the member device list in charge of the management device after the information of the other network device is given.
The information of the management device includes an IP address of the management device, a serial number of the management device, and the like. Here, the information of the management apparatus is merely exemplified and not particularly limited.
The information of the network device includes an IP address of the network device, a serial number of the network device, a system name of the network device, and the like. Here, the information of the network device is merely exemplified and not particularly limited.
In an example, the member discovery packet and the response packet to the member discovery packet may be private Protocol packets, for example, HSTP (H3C SmartMC Transport Protocol, hua san SmartMC Transport Protocol) Protocol. The Type field of the packet in the private protocol is a designated field, and the first TLV (Type-Length-Value) in the Data field is a designated TLV.
Referring to table 1, table 1 is a message format of the HSTP protocol.
| DA | SA | TAG | Type | Data | CRC |
TABLE 1
The specified field of the protocol Type field may be 0xabb0, and the Data field is composed of TLVs. The Length of the Type field in the TLV is 1 byte, the Length field is 2 bytes, and the Length of the Value field is equal to the Value of the Length field.
It should be noted that, in order to prevent the occurrence of the private messages of the same protocol type on the network device, the management device does not discover all the member devices. The HSTP management protocol specifies that TLV No. 1 of the above-mentioned Data field must be a designated TLV. The Type in the specified TLV is 1, the Length is 28 bytes, and the Length field is 28 bytes, which is defined as follows:
the member discovery message is a broadcast message, for example, the DA (destination address) field in table 1 is full f, and the Data field is shown in table 2.
| Sender Mac | Send IP |
| MAC_ADDR TLV | IPV4_ADDR TLV |
TABLE 2
The Sender Mac in table 2 indicates the bridge Mac address that sent the member discovery packet, such as the bridge Mac address of the management device. The Sender IP indicates an IP address, such as an IP address of the management device, to which the member discovery packet is sent.
The scan response packet is a unicast packet, and for example, the DA in table 1 is an SA (source address) in the member discovery packet, and the SA is an MAC address for sending the scan response packet. The Data field is shown in table 3.
TABLE 3
Wherein, the slave dev MAC indicates a bridge MAC address of the network device that sends the scan response packet; the SlaveDev IP indicates the IP address of the network equipment which sends the scanning response message; the SlaveDev MaskLen indicates the IP address mask of the network equipment which sends the scanning response message; the SlaveDev Model indicates the device type of the scanning response message; the slave dev SN indicates the device serial number that sent the scan response message.
Of course, the member discovery message and the response message for the member discovery message may also use other proprietary protocols, which are only exemplarily illustrated and are not specifically limited.
The management device may utilize the above-described private protocol to enable discovery of the member devices.
For example, the management device may broadcast the Type field as a specified field into the network, and the TLV in the Data field is a member device discovery packet of the specified TLV. When other devices in the network receive the message with the Type field as the designated field and the TLV in the Data field as the designated TLV, the received message can be determined to be the member device discovery message sent by the management device. Other devices in the network can return a Type field as a designated field to the management device in an unmanaged state, and the TLV in the Data field is a response message of the designated TLV for the member device discovery message.
When the management device receives a message with a Type field as a designated field and a TLV in a Data field as a designated TLV, the management device can determine that the received message is a response message aiming at the discovery message of the member device. The management device may determine that the network device that sends the response packet is a member device managed by the management device, and the management device may add the determined member device to the member device list.
Step 103: and the management equipment sends the topology collection messages to each member equipment.
Step 104: the management equipment receives network topology information returned by each member equipment;
in the embodiment of the present application, the management device sends the topology collection packet to all the member devices discovered in step 101. After receiving the topology collection message sent by the management device, the member device can send the network topology information of the member device to the management device through a NETCONF protocol.
The network topology information includes basic information, stacking information, interface information, LLDP neighbor information, STP information, etc. of the member devices. The LLDP neighbor information is the key information for the network topology calculation.
It should be noted that, the management device may send the topology collection message to all the discovered member devices after detecting the externally input topology collection specification. Of course, the management device may also periodically and automatically send topology collection messages to all the discovered member devices. Here, the timing of triggering the topology collection by the management device is merely exemplified and is not particularly limited.
Step 105: the management device calculates the topology of the network based on the collected topology information of each member device, and displays the topology through the management device.
After receiving the network topology information of each member device, the network device may calculate the network topology structure of the network based on the network topology information, then draw the network topology diagram of the preset network, and display the network topology diagram through the management device and a graphical page, for example, display the network topology diagram through a WEB page. The network topology shown may be as shown in fig. 2.
2) Software upgrade of member devices
Generally, devices of the same model use the same software version file, so in the present application, in order to implement software upgrade on batch member devices and improve software upgrade efficiency, the management device may group the member devices, and then use the software version file corresponding to the group to perform batch upgrade on the member devices in the group.
Referring to fig. 3, fig. 3 is a flow chart illustrating a member device software upgrade according to an exemplary embodiment of the present application. The process may include the steps described below.
Step 301: the management device groups the discovered member devices.
In this embodiment of the present application, after discovering the member devices of the management device, the management device may further group the discovered member devices.
In an alternative, since devices of the same model typically use the same software version file, the management device may group the member devices by their device models.
The grouping method is described in detail below by taking an example of grouping one member device, and the grouping method of other member devices is the same as that described above, and is not described again here.
In implementation, the Management device may obtain the device identifier of the member device by using an SNMP (Simple Network Management Protocol) Protocol packet.
Usually, the management device is preconfigured with a corresponding relationship between the device identifier and the device model, for example, the management device may maintain a table in which the corresponding relationship between the device identifier and the device model is recorded, and the table may support manual extension to increase the corresponding relationship between the device identifier and the device model.
After acquiring the device identifier of the member device, the management device may determine the device model corresponding to the device identifier of the member device based on the correspondence between the device identifier and the device model.
The management device may look up the grouping corresponding to the determined device model. If the member device is found, the management device can add the member device to the found group; if not, the management device may create a new group corresponding to the determined device model, and then add the discovered member device to the created group.
Step 302: and after receiving the software upgrading instruction, the management equipment uses the software upgrading version corresponding to each group to upgrade the software of the member equipment in each group.
The software upgrading method is described in detail below by taking the software upgrading of any one group of member devices as an example, and the software upgrading of the member devices of other groups is the same as that of the member devices of other groups, and is not described herein again.
In this embodiment, after the management device receives an externally input software upgrade instruction, the management device may issue a download path of a software upgrade version corresponding to the group to the member devices in the group.
After receiving the download path, the member devices of the group may download the software upgrade version corresponding to the group based on the download path.
And when the management equipment determines that the member equipment in the group finishes downloading the software upgrading version, the management equipment can control the member equipment in the group to use the downloaded software upgrading version for software upgrading.
In implementation, after the downloading is completed, the member device may return a downloading completion message to the management device. After receiving the download completion message returned by all the online member devices in the group, the management device can issue an upgrade instruction to each member device in the group, and after receiving the upgrade instruction, the member device can delay a preset time (such as 5 s) and then upgrade the software on the device by using the downloaded software upgrade version.
3) Automatic replacement of malfunctioning device
In the embodiment of the application, when a member device in the network fails, the failed member device can be replaced by a newly accessed network device meeting the condition.
Referring to fig. 4, fig. 4 is a flow chart illustrating automatic replacement of a malfunctioning device according to an exemplary embodiment of the present application. The process may include the steps described below.
Step 401: when a member device fails, the management device determines a newly accessed network device that replaces the failed member device.
In implementation, the management device may periodically send a heartbeat message to the member devices managed by the management device, and when the management device does not receive a response message, which is returned by a member device and is directed to the heartbeat message, in a preset period or in consecutive periods, it determines that the member device is faulty.
In addition, since the management device periodically broadcasts the member device discovery message in the network, the management device can detect the member device newly accessing the network.
When the management device confirms that a member device fails, the management device can detect whether a newly accessed network device can replace the failed member device.
In an alternative implementation, the management device may determine whether the newly accessed network device satisfies the replacement condition. If so, the newly accessed network device is indicated as the newly accessed network device replacing the failed member device. If not, continuing to judge whether the next newly accessed network meets the replacing condition.
Wherein the alternative conditions may include: the device models of the newly accessed network device and the failed member device are the same, and the neighbor relations of the newly accessed network device and the failed member device are the same.
Before the judgment, the management equipment can acquire the equipment identifier of the newly accessed network equipment through the SNMP message, and then determine the equipment model corresponding to the equipment identifier of the newly accessed network equipment according to the corresponding relation between the equipment identifier and the equipment model. In addition, the management device can also collect messages through the periodic topology to acquire the neighbor relation of the newly accessed network device.
It should be noted that, the neighbor relationship of the newly accessed network device needs to be stable for a period of time, so in order to obtain an accurate neighbor relationship, the management device may obtain the neighbor relationship of the newly accessed network device again when the neighbor information in the LLDP message returned by the newly accessed device is not empty and remains unchanged for a plurality of consecutive periods (e.g., 2 periods).
After acquiring the device signal and the neighbor relation of the new access device, the management device may determine whether the device signal and the neighbor relation of the new access device are the same as those of the failed member device, and if so, determine that the new access device is a network device that can replace the failed member device.
Step 402: and the management equipment synchronizes the configuration information of the fault member equipment to the determined newly-accessed network equipment so as to enable the newly-accessed network equipment to replace the fault member equipment to work.
In this embodiment of the present application, after determining the newly accessed network device that replaces the failed member device, the management device may synchronize the configuration information of the failed device to the determined newly accessed network device.
The configuration information may include a software version file, a configuration file, etc. of the failed member device, and is only exemplary and not limited to the configuration information.
The application provides a device management method which is used for solving the problem of centralized management of distributed network devices for small enterprises or small networks.
On one hand, the method adopts an embedded equipment management mode, and if the specified forwarding equipment in the network is adopted as the management server, the specified forwarding equipment performs self-management on the network, so that the cost for deploying additional management servers is effectively reduced.
On the other hand, the forwarding device serving as the management server can automatically discover the member devices, acquire the topology of the member devices and present the network topology in a graphical manner, and on the basis, grouping the member devices according to the models of the member devices and batch upgrading of software on the member devices based on the grouping are realized; and automatic replacement of the failed member device, thereby realizing management of the member devices in the network.
Corresponding to the embodiment of the device management method, the application also provides an embodiment of a device management apparatus.
The embodiment of the device management apparatus can be applied to forwarding devices. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. The software implementation is taken as an example, and is formed by reading corresponding computer program instructions in the nonvolatile memory into the memory for operation through the processor of the management device where the software implementation is located as a logical means. In terms of hardware, as shown in fig. 5, a hardware structure diagram of a management device in which the apparatus management apparatus of the present application is located is shown, except for the processor, the memory, the network output interface, and the nonvolatile memory shown in fig. 5, the management apparatus in which the apparatus is located in the embodiment may also include other hardware according to the actual function of the management apparatus, which is not described again.
Referring to fig. 6, fig. 6 is a block diagram of a device management apparatus according to an exemplary embodiment of the present application. The device is applied to forwarding equipment which is designated as a network management server in a network, and comprises the following components:
a discovery unit 601, configured to broadcast a member device discovery packet in the network, and when receiving a response packet of the member device discovery packet, determine that a network device that sends the response packet is a member device managed by the device;
a collecting unit 602, configured to send a topology collection packet to each member device, and receive network topology information returned by each member device;
a display unit 603, configured to calculate a topology structure of the network based on the collected topology information of each member device, and display the topology structure through the management device.
Optionally, the Type field in the member device discovery message is a designated field, and the Type length value TLV in the Data field is a designated TLV; the Type field in the member device response message is the designated field, and the TLV in the Data field is the designated TLV;
the discovery unit is specifically configured to broadcast a Type field as the designated field in the network, where TLV in a Data field is a member device discovery packet of the designated TLV; when receiving messages of which the Type field is the designated field and the TLV in the Data field is the designated TLV, determining the received messages as response messages aiming at the discovery messages of the member equipment; and determining the network equipment which sends the response message as member equipment managed by the equipment.
Optionally, the apparatus further comprises: a grouping unit 604, configured to, after discovering member devices managed by the management device, group the discovered member devices;
the device further comprises: and the upgrading unit 605 is configured to, after receiving the software upgrading instruction, upgrade the software of the member devices in each group by using the software upgrading version corresponding to each group.
Optionally, the upgrading unit 605 is specifically configured to, for each group, send a software upgrade version download path corresponding to the group to the member device in the group, so that the member device in the group downloads the software upgrade version corresponding to the group according to the software upgrade version download path; and controlling the member equipment in the group to use the downloaded software upgrading version to carry out software upgrading when determining that the member equipment in the group finishes downloading the software upgrading version.
Optionally, the grouping unit 604 is specifically configured to determine, for each discovered member device, a device model corresponding to a device identifier of the member device based on a preset correspondence between the device identifier and the device model; searching a group corresponding to the determined equipment model; if the member equipment is found, adding the member equipment into the found group; and if the member equipment is not found, establishing a group corresponding to the determined equipment model, and adding the found member equipment to the newly established group.
Optionally, the apparatus further comprises:
a determining unit 606, configured to determine, as a member device failure, a newly accessed network device that replaces the failed member device;
a replacing unit 607, configured to synchronize the configuration information of the failed member device to the determined newly accessed network device, so that the newly accessed network device works in place of the failed member device.
Optionally, the determining unit 606 is specifically configured to detect whether a newly accessed network device meets a replacement condition; the alternative conditions include: the newly accessed network equipment and the fault member equipment have the same equipment model, and the newly accessed network equipment and the fault member equipment have the same neighbor relation; if so, the newly accessed network device is determined to be the newly accessed network device that replaces the failed member device.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and 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 modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (12)
1. A device management method applied to a forwarding device designated as a network management server in a network, the method comprising:
broadcasting member device discovery messages within the network;
when a response message of the member device discovery message is received, determining that the network device sending the response message is the member device managed by the device;
sending topology collection messages to each member device;
receiving network topology information returned by each member device;
calculating the topological structure of the network based on the collected topological information of each member device, and displaying the topological structure through the management device;
the member device finds that a Type field in the message is a designated field, and a Type length value TLV in a Data field is a designated TLV; the Type field in the member device response message is the designated field, and the TLV in the Data field is the designated TLV;
the broadcasting a member device discovery packet within the network includes:
broadcasting a Type field in the network as the designated field, wherein TLV in a Data field is a member device discovery message of the designated TLV;
when receiving a response message of the member device discovery message, the determining that the network device sending the response message is the member device managed by the device includes:
when receiving messages of which the Type field is the designated field and the TLV in the Data field is the designated TLV, determining the received messages as response messages aiming at the discovery messages of the member equipment; and determining the network equipment which sends the response message as member equipment managed by the equipment.
2. The method according to claim 1, after determining that the network device that sends the response packet is a member device managed by the device, further comprising:
grouping the determined member devices;
the method further comprises the following steps:
and after receiving the software upgrading instruction, upgrading the software of the member equipment in each group by using the software upgrading version corresponding to each group.
3. The method of claim 2, wherein the software upgrade of the member devices in each group using the software upgrade version corresponding to each group comprises:
aiming at each group, sending a software upgrading version downloading path corresponding to the group to the member equipment in the group so as to enable the member equipment in the group to download the software upgrading version corresponding to the group according to the software upgrading version downloading path;
and controlling the member equipment in the group to use the downloaded software upgrading version to carry out software upgrading when determining that the member equipment in the group finishes downloading the software upgrading version.
4. The method of claim 2, wherein the grouping of discovered member devices; the method comprises the following steps:
for each discovered member device, determining a device model corresponding to the device identifier of the member device based on a preset corresponding relationship between the device identifier and the device model;
searching a group corresponding to the determined equipment model;
if the member equipment is found, adding the member equipment into the found group;
and if the member equipment is not found, establishing a group corresponding to the determined equipment model, and adding the found member equipment to the newly established group.
5. The method of claim 1, further comprising:
when a member device fails, determining a newly accessed network device that replaces the failed member device;
and synchronizing the configuration information of the fault member equipment to the determined newly accessed network equipment so that the newly accessed network equipment replaces the fault member equipment to work.
6. The method of claim 5, wherein determining a newly accessed network device to replace the failed member device comprises:
detecting whether the newly accessed network equipment meets a replacement condition; the alternative conditions include: the newly accessed network equipment and the fault member equipment have the same equipment model, and the newly accessed network equipment and the fault member equipment have the same neighbor relation;
if so, the newly accessed network device is determined to be the newly accessed network device that replaces the failed member device.
7. An apparatus for device management, the apparatus being applied to a forwarding device designated as a network management server in a network, the apparatus comprising:
a discovery unit, configured to broadcast a member device discovery packet in the network, and determine, when receiving a response packet of the member device discovery packet, that a network device that sends the response packet is a member device managed by the device;
the collecting unit is used for sending topology collecting messages to each member device and receiving network topology information returned by each member device;
the management equipment comprises a display unit, a management unit and a management unit, wherein the display unit is used for calculating the topological structure of the network based on the collected topological information of each member equipment and displaying the topological structure through the management equipment;
the member device finds that a Type field in the message is a designated field, and a Type length value TLV in a Data field is a designated TLV; the Type field in the member device response message is the designated field, and the TLV in the Data field is the designated TLV;
the discovery unit is specifically configured to broadcast a Type field as the designated field in the network, where TLV in a Data field is a member device discovery packet of the designated TLV; when receiving messages of which the Type field is the designated field and the TLV in the Data field is the designated TLV, determining the received messages as response messages aiming at the discovery messages of the member equipment; and determining the network equipment which sends the response message as member equipment managed by the equipment.
8. The apparatus of claim 7, further comprising: a grouping unit, configured to group the discovered member devices;
the device further comprises: and the upgrading unit is used for upgrading the software of the member equipment in each group by using the software upgrading version corresponding to each group after receiving the software upgrading instruction.
9. The apparatus according to claim 8, wherein the upgrade unit is specifically configured to, for each group, send a software upgrade version download path corresponding to the group to the member devices in the group, so that the member devices in the group download the software upgrade version corresponding to the group according to the software upgrade version download path; and controlling the member equipment in the group to use the downloaded software upgrading version to carry out software upgrading when determining that the member equipment in the group finishes downloading the software upgrading version.
10. The apparatus according to claim 8, wherein the grouping unit is specifically configured to determine, for each discovered member device, a device model corresponding to a device identifier of the member device based on a preset correspondence between the device identifier and the device model; searching a group corresponding to the determined equipment model; if the member equipment is found, adding the member equipment into the found group; and if the member equipment is not found, establishing a group corresponding to the determined equipment model, and adding the found member equipment to the newly established group.
11. The apparatus of claim 7, further comprising:
a determining unit, configured to determine, when a member device fails, a newly accessed network device that replaces the failed member device;
and the replacing unit is used for synchronizing the configuration information of the fault member equipment to the determined newly-accessed network equipment so as to enable the newly-accessed network equipment to replace the fault member equipment to work.
12. The apparatus according to claim 11, wherein the determining unit is specifically configured to detect whether a newly accessed network device satisfies a replacement condition; the alternative conditions include: the newly accessed network equipment and the fault member equipment have the same equipment model, and the newly accessed network equipment and the fault member equipment have the same neighbor relation; if so, the newly accessed network device is determined to be the newly accessed network device that replaces the failed member device.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710880571.2A CN108259215B (en) | 2017-09-26 | 2017-09-26 | Equipment management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710880571.2A CN108259215B (en) | 2017-09-26 | 2017-09-26 | Equipment management method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108259215A CN108259215A (en) | 2018-07-06 |
| CN108259215B true CN108259215B (en) | 2021-05-28 |
Family
ID=62722075
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710880571.2A Active CN108259215B (en) | 2017-09-26 | 2017-09-26 | Equipment management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108259215B (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109672571B (en) * | 2019-01-16 | 2022-04-08 | 新华三技术有限公司 | Stacking method, device and storage medium |
| CN111343237B (en) * | 2020-02-07 | 2022-11-29 | 广州亚美信息科技有限公司 | Server cluster communication method, communication device and computer storage medium |
| CN112015098A (en) * | 2020-08-14 | 2020-12-01 | 深圳市欧瑞博科技股份有限公司 | System upgrading method and device for intelligent household equipment and electronic equipment |
| CN115150280A (en) * | 2021-03-31 | 2022-10-04 | 华为技术有限公司 | Data packet sending method and equipment |
| CN115567380A (en) * | 2021-05-31 | 2023-01-03 | 浙江大华技术股份有限公司 | Device processing method and device, authentication method and device, and storage medium |
| CN113824584A (en) * | 2021-07-19 | 2021-12-21 | 上海瀚银信息技术有限公司 | Network equipment management method and device |
| CN114363293B (en) * | 2021-12-14 | 2024-04-12 | 南昌航天广信科技有限责任公司 | Device management method, system, readable storage medium and computer device |
| CN115001957A (en) * | 2022-05-26 | 2022-09-02 | 苏州思萃工业互联网技术研究所有限公司 | System and method for quickly and automatically upgrading software |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1917433A (en) * | 2005-08-19 | 2007-02-21 | 上海贝尔阿尔卡特股份有限公司 | System for collecting network topology, and network equipment |
| CN103873301A (en) * | 2014-03-20 | 2014-06-18 | 浙江宇视科技有限公司 | System and method for automatically finding and adding devices |
| CN105207853A (en) * | 2015-10-12 | 2015-12-30 | 深圳市万网博通科技有限公司 | Local area network monitoring management method |
| EP2988452A1 (en) * | 2011-08-30 | 2016-02-24 | Qualcomm Incorporated | Topology discovery in a hybrid network |
| CN105426193A (en) * | 2015-11-25 | 2016-03-23 | 努比亚技术有限公司 | Software service realization method and apparatus |
| CN106888132A (en) * | 2017-04-28 | 2017-06-23 | 杭州迪普科技股份有限公司 | The management method and device of a kind of configuration information |
| CN107040399A (en) * | 2016-02-04 | 2017-08-11 | 京东方科技集团股份有限公司 | A kind of upgrade file method for down loading, equipment and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105591932B (en) * | 2015-07-13 | 2019-03-15 | 新华三技术有限公司 | The recognition methods of neighbours and device |
-
2017
- 2017-09-26 CN CN201710880571.2A patent/CN108259215B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1917433A (en) * | 2005-08-19 | 2007-02-21 | 上海贝尔阿尔卡特股份有限公司 | System for collecting network topology, and network equipment |
| EP2988452A1 (en) * | 2011-08-30 | 2016-02-24 | Qualcomm Incorporated | Topology discovery in a hybrid network |
| CN103873301A (en) * | 2014-03-20 | 2014-06-18 | 浙江宇视科技有限公司 | System and method for automatically finding and adding devices |
| CN105207853A (en) * | 2015-10-12 | 2015-12-30 | 深圳市万网博通科技有限公司 | Local area network monitoring management method |
| CN105426193A (en) * | 2015-11-25 | 2016-03-23 | 努比亚技术有限公司 | Software service realization method and apparatus |
| CN107040399A (en) * | 2016-02-04 | 2017-08-11 | 京东方科技集团股份有限公司 | A kind of upgrade file method for down loading, equipment and system |
| CN106888132A (en) * | 2017-04-28 | 2017-06-23 | 杭州迪普科技股份有限公司 | The management method and device of a kind of configuration information |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108259215A (en) | 2018-07-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108259215B (en) | Equipment management method and device | |
| US9344333B2 (en) | Automating network build-out in self building networks | |
| CN101083557B (en) | SNMP based IP network cluster managerial approach | |
| US9088477B2 (en) | Distributed fabric management protocol | |
| JPWO2013115177A1 (en) | Network system and topology management method | |
| US20210028982A1 (en) | Method, device, and system for deploying static routes | |
| US10206092B1 (en) | Automatic discovery | |
| CN109660442A (en) | The method and device of multicast replication in Overlay network | |
| CN110351141B (en) | Flexe interface management method, device and network element | |
| US10404544B2 (en) | Network topology determining method and apparatus, and centralized network status information storage device | |
| CN104283802A (en) | Neighbor discovery method and device | |
| CN103036934A (en) | Wide area network clustered deployment system and method based on mirror image | |
| CN110391940A (en) | Response method, device, system, equipment and the storage medium of address of service | |
| CN109379239B (en) | Method and device for configuring access switch in OpenStack environment | |
| CN104219100A (en) | Information acquiring method and device | |
| WO2020010906A1 (en) | Method and device for operating system (os) batch installation, and network device | |
| CN101404594B (en) | Hot backup performance test method and apparatus, communication equipment | |
| CN111106970A (en) | Data monitoring method and device, electronic equipment and readable storage medium | |
| CN107465621A (en) | A kind of router finds method, SDN controllers, router and network system | |
| CN107733727B (en) | Zero configuration method, device and equipment | |
| JP2021191007A (en) | Network topology discovery method, network topology discovery device, and network topology discovery system | |
| CN104125079A (en) | Method and device for determining double-device hot-backup configuration information | |
| Cisco | Rel Notes for Catalyst 2900 Series XL Cisco IOS Rel 11.2(8)SA2 | |
| Cisco | Release Notes for Catalyst 5000 Family Software Release 4.x | |
| Cisco |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |