CN116112335A - Network equipment management method and device - Google Patents

Abstract

The application provides a network equipment management method and device, wherein the method comprises the following steps of; receiving a first notification message sent by a second controller in the controller cluster, wherein the first notification message comprises a message type and a device identifier of network devices to be managed; establishing a switching distributed lock according to the message type; releasing the switching distributed lock after the network equipment indicated by the equipment identifier completes the establishment of the NETCONF session, and judging whether the connection distributed lock is acquired or not; if so, performing nano-tube on the network equipment; the first controller is a controller newly added into the controller cluster, or is a controller already in the controller cluster, and the second controller is a master controller in the controller cluster.

Description

Network equipment management method and device

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for managing network devices.

Background

With the rapid development of cloud computing, the traditional network adopts a manual deployment mode, so that the efficiency is low, the labor cost is high, and the current service increasing requirement cannot be met. The software defined network (English: software Defined Network, SDN for short) controller enables management personnel to rapidly realize automatic deployment of each network device service by using the SDN controller in a centralized controller mode, and service deployment period is greatly shortened; meanwhile, dynamic adjustment is realized to meet the change of the service.

In order to realize rapid forwarding of data, an SDN controller is usually a high-performance switch or firewall device, and performs automatic management and configuration on network devices of a nanotube through a network configuration protocol (english: network Configuration Protocol, abbreviated as netcon) protocol. With the increasing number of network devices in an SDN network, how to effectively and reliably manage the increasing number of network devices in the network presents greater challenges to an SDN controller.

As shown in fig. 1, fig. 1 is a schematic diagram of a conventional SDN controller cluster. In fig. 1, an SDN controller cluster adopts a main multi-standby mode to achieve high availability. The main controller provides the expression state transfer (English: representational State Transfer, REST for short) application programming interface (English: application Programming Interface, API for short) to the outside, and interfaces with the management platform or Openstack (cloud platform). The backup controller is used as a backup of the main controller, and is quickly switched to become the main controller when the main controller is abnormal, so that high service availability is realized.

As shown in fig. 2, fig. 2 is a schematic diagram of the main and standby of the conventional Openflow example. In fig. 2, an SDN controller implements reliability management of network devices based on the active-standby functions of Openflow instances. An Openflow instance is configured in the network device, and one Openflow instance can be connected to multiple controllers at the same time, wherein roles of the multiple controllers include two types, namely a Master (Master) controller and a standby (Slave) controller.

The role of the controller is to configure when the equipment is initialized, and when the main controller fails, the standby controller becomes the main controller in an election mode. The master controller may establish a netcon session with the network device, with subsequent service configurations all based on the established netcon session. And if the main controller fails, the role is switched, and the controller automatically switches the NETCONF session according to the role change.

However, the above manner of implementing the controller to manage the network device by using the active/standby function based on the Openflow instance also exposes the following drawbacks: 1) As the number of network devices increases, there is no guarantee that the network devices are evenly loaded to different controllers. In extreme cases, it may result in one controller becoming the master controller for all network devices. At this time, the resources of the main controller are rapidly exhausted, and the service abnormality is triggered, so that the availability and reliability of the whole controller cluster are affected; 2) When controllers are added in the controller cluster, the Openflow instance configuration of all network devices needs to be updated. If the added controller is designated as a standby controller of the network device, the existing roles are not changed at this time, and the operation is kept, but the problem of uneven resource distribution of the main controller possibly existing cannot be solved. If the added controller is the master controller of a part of the network devices, the problem of uneven resource distribution of the master controller can be solved, but the reestablishment of the existing netcon f session may be caused, and the availability of the service is affected.

Disclosure of Invention

In view of this, the present application provides a method and apparatus for managing network devices, which are used to solve the problem that when the number of network devices increases in the existing manner, it cannot be guaranteed that the network devices are uniformly loaded to different controllers, and when the number of controllers increases, the existing netcon session is rebuilt, which affects the usability of the service.

In a first aspect, the present application provides a network device management method, where the method is applied to a first controller, the method includes;

receiving a first notification message sent by a second controller in the controller cluster, wherein the first notification message comprises a message type and a device identifier of network devices to be managed;

establishing a switching distributed lock according to the message type;

releasing the switching distributed lock after the network equipment indicated by the equipment identifier completes the establishment of the NETCONF session, and judging whether the connection distributed lock is acquired or not;

if so, performing nano-tube on the network equipment;

the first controller is a controller newly added into the controller cluster, or is a controller already in the controller cluster, and the second controller is a master controller in the controller cluster.

In a second aspect, the present application provides a network device management method, the method being applied to a first controller, the method comprising;

when a second controller is newly added into the controller cluster, acquiring state attributes of other controllers except the second controller in the controller cluster;

determining whether to smoothly switch part of network equipment of the other controller nanotubes to the second controller nanotube according to the state attribute of the other controller;

if yes, selecting a third controller from the other controllers;

respectively sending different first notification messages to the second controller and the third controller, so that the second controller and the third controller perform NA Guan Qiehuan of the network device according to the received first notification messages;

the first controller is a master controller in the controller cluster.

In a third aspect, the present application provides a network device management apparatus, the apparatus being applied to a first controller, the apparatus comprising;

a receiving unit, configured to receive a first notification message sent by a second controller in the controller cluster, where the first notification message includes a message type and a device identifier of a network device to be managed;

The establishing unit is used for establishing a switching distributed lock according to the message type;

the release unit is used for releasing the switching distributed lock after the network equipment indicated by the equipment identifier completes the establishment of the NETCONF session, and judging whether the connection distributed lock is acquired or not;

the network equipment comprises a network equipment, a nanotube unit and a control unit, wherein the network equipment is used for acquiring network equipment;

the first controller is a controller newly added into the controller cluster, or is a controller already in the controller cluster, and the second controller is a master controller in the controller cluster.

In a fourth aspect, the present application provides a network device management apparatus, the apparatus being applied to a first controller, the apparatus comprising;

the system comprises an acquisition unit, a control unit and a control unit, wherein the acquisition unit is used for acquiring state attributes of other controllers except for a second controller in a controller cluster when the second controller is newly added in the controller cluster;

the determining unit is used for determining whether to smoothly switch part of network equipment of the other controller nanotubes to the second controller nanotube according to the state attribute of the other controller;

a selecting unit, configured to select a third controller from the other controllers if yes;

A sending unit, configured to send different first notification messages to the second controller and the third controller respectively, so that the second controller and the third controller perform a per Guan Qiehuan of the network device according to the received first notification messages;

the first controller is a master controller in the controller cluster.

In a fifth aspect, the present application provides a network device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor to cause the processor to perform the method provided in the first aspect of the present application.

In a sixth aspect, the present application provides a network device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor to cause the processor to perform the method provided in the second aspect of the present application.

Therefore, by applying the network equipment management method and device provided by the application, the first controller receives the first notification message sent by the second controller in the controller cluster, wherein the first notification message comprises the message type and the equipment identifier of the network equipment to be managed; according to the message type, the first controller establishes a switching distributed lock; after the network equipment indicated by the equipment identifier completes the establishment of the NETCONF session, the first controller releases the switching distributed lock and judges whether the connection distributed lock is acquired or not; if so, the first controller carries out nano-tube on the network equipment; the first controller is a controller newly added into the controller cluster, or is a controller already in the controller cluster, and the second controller is a master controller in the controller cluster.

Therefore, the reliability management capability of the controllers in the controller cluster to the network equipment is improved, the number of the controllers in the dynamic capacity-expansion controller cluster is supported, and meanwhile, the load adjustment can be realized on the premise of not affecting the service. The method solves the problems that when the number of network devices is increased in the existing mode, the network devices cannot be guaranteed to be uniformly loaded to different controllers, and when the number of the controllers is increased, the existing NETCONF session is rebuilt, and the service availability is affected.

Drawings

FIG. 1 is a schematic diagram of a conventional SDN controller cluster;

FIG. 2 is a schematic diagram of the active/standby of the conventional Openflow example;

fig. 3 is a flowchart of a network device management method provided in an embodiment of the present application;

fig. 4 is a flowchart of another network device management method according to an embodiment of the present application;

fig. 5 is a block diagram of a network device management apparatus according to an embodiment of the present application;

fig. 6 is a block diagram of another network device management apparatus according to an embodiment of the present application;

fig. 7 is a hardware structure of a network device according to an embodiment of the present application.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to 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 some aspects of the present application as detailed in the accompanying claims.

The terminology used in the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the present 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 will also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the corresponding listed items.

It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first message may also be referred to as a second message, and similarly, a second message may also be referred to as a first message, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.

The following describes a network device management method in detail. Referring to fig. 3, fig. 3 is a flowchart of a network device management method according to an embodiment of the present application. The method is applied to a first controller. The network device management method provided by the embodiment of the application can comprise the following steps.

Step 310, receiving a first notification message sent by a second controller in the controller cluster, where the first notification message includes a message type and a device identifier of a network device to be managed;

specifically, the first controller is located in a controller cluster, and the controller cluster comprises a plurality of controllers, wherein the second controller is a main controller in the controller cluster, and other controls except the second controller are standby controllers; the first controller may be a controller that is newly added to the controller cluster or a controller that is already within the controller cluster before.

When the second controller determines that the smooth switching of the nanotube right between the controllers is required, the second controller generates and sends a first notification message to the first controller. The first notification message includes a message type and a device identification of the network device to be managed.

Wherein the first controller may also be referred to as a nanotube authority recipient. The message type specifically means that the first notification message is a smooth handover notification. The device identification of the network device refers in particular to the unique ID of the network device.

The first controller receives the first notification message and obtains therefrom the message type and the device identification of the network device.

In the embodiment of the application, the nanotube right refers to actual control of the controller to manage the network device. The determination by the second controller that a smooth switching of nanotube rights between controllers is desired includes the following.

In one case, when the controller cluster expands the capacity of the controller, the second controller determines newly added control nano network equipment according to the state attribute of the controller in the current controller cluster so as to achieve load balancing. For example, the first controller is a newly added controller in the controller cluster, and the second controller may determine whether to smoothly switch the network device of the other controller nanotube to the nanotube by the first controller according to the state attribute of the other controllers except the first controller in the current controller cluster, so as to reduce the workload of the other controllers.

In another case, a certain controller automatically reports to a second controller to perform load balancing. For example, the number of network devices of a certain controller nanotube exceeds a number threshold (for example, the number threshold is 5000, which is half of the network devices in the SDN networking), or the current state of the certain controller does not meet the working state, and the certain controller reports to the second controller. The second controller may determine whether to smoothly switch the network device of the controller nanotube to be nanotube by another controller according to the state attributes of the other controllers except the controller in the current controller cluster, so as to reduce the workload of the controller.

Step 320, establishing a switching distributed lock according to the message type;

specifically, according to the description of step 310, after the first controller obtains the message type and the device identifier of the network device, the first controller determines that the first notification message is a smooth handover notification according to the message type; according to the device identification, it is also determined that the network device indicated by the device identification is not self-administered. Thus, the first controller determines that the second controller initiates a smooth handoff and wants the network device indicated by the device identification to be managed by the first controller.

According to the message type, the first controller establishes a switched distributed lock.

Further, an application module is included in the controller cluster, which can provide distributed lock functionality and access. The controller can acquire the distributed lock by calling an interface provided by the application module, or upload the created distributed lock and related data into the application module so as to facilitate the acquisition of other controllers. A distributed lock is a globally visible variable that is visible and acquired by all controllers within a controller cluster.

The first controller establishes a switch distributed lock and invokes an interface of the application module. The first controller uploads the switching distributed lock and related data into the application module. Meanwhile, the application module locally records the creation, occupation and release processes of the lock.

Step 330, releasing the switch distributed lock after the network device indicated by the device identifier completes the establishment of the netcon session, and judging whether a connection distributed lock is acquired;

specifically, after the first controller establishes the switch distributed lock, the first controller establishes a netcon f session with the network device indicated by the device identification, as described in step 320. And after the first controller and the network equipment complete the establishment of the NETCONF session, the first controller releases the switching distributed lock and judges whether the connection distributed lock is acquired or not.

It will be appreciated that the first controller again invokes the interface of the application module requesting release of the switch distributed lock. And the application module responds to the request and records the release process, and updates the occupation record of the switching distributed lock. At the same time, the first controller also requests to acquire a connection distributed lock. If the connection distributed lock is not occupied by other controllers at this time, the first controller can acquire the connection distributed lock, which means that the first controller can receive network equipment, and the application module records the acquisition process of the first controller and updates the occupation record of the connection distributed lock.

It should be noted that, in the embodiment of the present application, the first controller may periodically acquire the switching distributed lock. The switch distributed lock may also be used to indicate whether a netcon f session has been established normally. The controller can perform service configuration processing on the network device after successfully establishing the NETCONF session with the network device.

And 340, if the network equipment is obtained, performing nano-tube on the network equipment.

Specifically, according to the determination in step 330, if the first controller acquires the connection distributed lock and has completed the netcon session establishment with the network device, the first controller performs the nanotubes on the network device.

Optionally, if the first controller does not acquire the connection distributed lock, the first controller again attempts to acquire the connection distributed lock and continues to determine whether the connection distributed lock is acquired.

Therefore, by applying the network equipment management method and device provided by the application, the first controller receives the first notification message sent by the second controller in the controller cluster, wherein the first notification message comprises the message type and the equipment identifier of the network equipment to be managed; according to the message type, the first controller establishes a switching distributed lock; after the network equipment indicated by the equipment identifier completes the establishment of the NETCONF session, the first controller releases the switching distributed lock and judges whether the connection distributed lock is acquired or not; if so, the first controller carries out nano-tube on the network equipment; the first controller is a controller newly added into the controller cluster, or is a controller already in the controller cluster, and the second controller is a master controller in the controller cluster.

Therefore, the reliability management capability of the controllers in the controller cluster to the network equipment is improved, the number of the controllers in the dynamic capacity-expansion controller cluster is supported, and meanwhile, the load adjustment can be realized on the premise of not affecting the service. The method solves the problems that when the number of network devices is increased in the existing mode, the network devices cannot be guaranteed to be uniformly loaded to different controllers, and when the number of the controllers is increased, the existing NETCONF session is rebuilt, and the service availability is affected.

Alternatively, in the foregoing embodiment, the first controller is described as the right-to-nanotube acceptor. In the embodiment of the application, the first controller can also serve as a nanotube right output party to receive the process of the second notification message.

Specifically, when the second controller determines that the smooth switching of the nanotube right between the controllers is required, the second controller may first select a part of network devices from all network devices already nanotube by the first controller, and smoothly switch the na Guan Quan of the part of network devices to other controllers to balance the load between the controllers.

The second controller generates and transmits a second notification message to the first controller. The second notification message includes a message type and a device identification of the network device of the first controller nanotube.

Wherein the first controller may also be referred to as a nanotube right outputter. The message type specifically means that the second notification message is a smooth handover notification. The device identification of the network device refers in particular to the unique ID of the network device.

The first controller receives the second notification message and obtains therefrom the message type and the device identification of the network device.

According to the message type, the first controller determines that the second notification message is a smooth switching notification; according to the device identification, it is also determined that the network device indicated by the device identification has been managed by itself. Thus, the first controller determines that the second controller initiates a smooth handover and wants to transfer the nanotube right of the network device indicated by the device identification to the other controllers for the nanotubes.

And according to the message type, the first controller judges whether the switching distributed lock is acquired. The first controller invokes an interface of the application module and periodically requests to acquire the switching distributed lock. If the switching distributed lock is not occupied by other controllers at this time, the first controller may acquire the switching distributed lock, which also indicates that the receiving party of na Guan Quan has the nanotube capability, and the application module records the occupation process of the first controller.

And if the first controller acquires the switching distributed lock, the first controller calls an interface of the application module to request to release the connecting distributed lock. The application module responds to the request and records the release process, and updates the occupation record of the connection distributed lock. The first controller, upon releasing the connection distributed lock, indicates that the first controller released the per Guan Quan to the network device.

The first controller closes a netcon f session established with the network device indicated by the device identification. The first controller invokes an interface of the application module requesting release of the switch distributed lock. And the application module responds to the request and records the release process, and updates the occupation record of the switching distributed lock.

It should be noted that, before the first controller receives the second notification message, it still needs to continue to process the existing tasks of all network devices of the current nanotube or the newly added tasks in the smooth handover process.

If the first controller does not acquire the switching distributed lock, the first controller again tries to acquire the connecting distributed lock and continues to judge whether the connecting distributed lock is acquired.

Optionally, in the embodiment of the present application, a process that the first controller requests the second controller to balance the load is further included.

Specifically, in one case, the first controller identifies the number of network devices of its own nanotubes. If the number of network devices of the first controller nanotube exceeds a number threshold (e.g., 5000), the first controller determines that the self-load is excessive. The first controller generates and transmits a third notification message to the second controller.

In another case, the first controller detects that the first controller is not suitable for carrying out the nano tube on the network equipment any more due to abnormality, failure and the like, namely, when the current state of the first controller does not meet the working state, the first controller generates and sends a third notification message to the second controller.

The third notification message includes a message type and a device identification of the network device of the first controller nanotube. Wherein the message type specifically means that the third notification message is a transfer nanotube right notification. The device identification of the network device may be a device identification of a portion of the network device of the first controller nanotube.

It may be appreciated that, after the first controller determines that the load of the first controller is excessive, or the current state of the first controller does not satisfy the working state, the first controller may select a part of network devices from all network devices of the self-nanotubes and request the second controller to transfer the element Guan Quan of the selected part of network devices.

And after receiving the third notification message, the second controller acquires the message type and the equipment identifier of the network equipment from the third notification message. According to the message type, the second controller determines that the third notification message is a transfer nanotube right notification, and determines that the current load of the first controller is excessive or the current state does not meet the working state.

Depending on the message type, the second controller may obtain status attributes of the other controllers including, but not limited to, the number of network devices of the nanotube, CPU memory usage, and the like. By the status attribute, the second controller selects, as the third controller, a controller having a smaller number of nanotubes (for example, 100 nanotubes) and a lower CPU memory usage (for example, 20%) as the third controller.

After the second controller selects the third controller, two fourth known messages are generated and sent to the first controller and the third controller respectively. The fourth notification message sent by the second controller to the first controller may be the same as the second notification message, and the fourth notification message sent by the second controller to the third controller may be the same as the first notification message.

And the first controller and the third controller perform the nanotube switching of the network equipment indicated by the equipment identification according to the received fourth known message. The switching process performed by the third controller may specifically refer to the foregoing processes of steps 310-340, and the switching process performed by the first controller may specifically refer to the foregoing process of receiving the second notification message, which will not be repeated herein.

Optionally, in the embodiment of the present application, the method further includes a process that the second controller selects the nanotube controller for the newly added network device after the newly added network device in the SDN network.

Specifically, when network equipment is newly added in the SDN network, the second controller obtains the number of netcon sessions of each controller in the controller cluster. The second controller takes the first controller with the smallest number of NETCONF sessions as the controller of the nano-network equipment.

The second controller generates and sends a fourth notification message to the first controller, the fourth notification including the message type and a device identification of the newly added network device within the SDN network. The message type specifically means that the fourth known message is a notification of establishing a nanotube right.

According to the message type, the first controller determines that the fourth known message is a notification of establishing the nanotube right, and also determines that the network equipment indicated by the equipment identification is not received by the first controller according to the equipment identification. Thus, the first controller determines that the second controller initiates establishment of the nanotubes and intends to nanotube the network device indicated by the device identification by the first controller.

According to the message type, the first controller acquires the connection distributed lock. The first controller invokes an interface of the application module requesting acquisition of the connection distributed lock. If the connection distributed lock is not occupied by other controllers at this time, the first controller can acquire the connection distributed lock, and the application module records the occupation process of the first controller.

According to the device identification, the first controller establishes a netcon session with the network device. If the first controller acquires the connection distributed lock and establishes the NETCONF session with the network equipment, the first controller carries out nano-tube on the network equipment.

Another method for managing network devices provided in the embodiments of the present application is described in detail below. Referring to fig. 4, fig. 4 is a flowchart of another network device management method according to an embodiment of the present application. The method is applied to a first controller. The network device management method provided by the embodiment of the application can comprise the following steps.

Step 410, when a second controller is newly added into the controller cluster, acquiring state attributes of other controllers except the second controller in the controller cluster;

specifically, the first controller is located in a controller cluster, and the controller cluster includes a plurality of controllers, wherein the first controller is a master controller in the controller cluster, and other controls except the first controller are all standby controllers. The second controller may be a controller that is newly added to the controller cluster.

After the second controller is newly added into the controller cluster, since it is a controller newly added into the controller cluster, the load of the second controller is 0. At this time, the first controller may smoothly switch the network devices of the other controller nanotubes in the controller cluster to the second controller nanotubes to balance the load of each controller.

To perform smooth switching of the nanotube rights, a first controller first acquires state attributes of other controllers within the controller cluster than a second controller. The status attributes include, but are not limited to, the number of network devices of the nanotube, CPU memory usage, and the like.

Step 420, determining whether to smoothly switch part of the network devices of the other controller nanotubes to the second controller nanotube according to the state attribute of the other controller;

specifically, according to the description of step 410, after the first controller acquires the state attribute of the other controller, the first controller determines whether to smoothly switch the part of the network devices of the other controller nanotubes to the second controller nanotube according to the state attribute.

For example, the number of network devices currently loaded by the other controller exceeds a number threshold (e.g., 5000 number threshold), or the current CPU memory usage of the other controller exceeds a usage threshold (e.g., 70% usage threshold), the first controller determines to smoothly switch portions of the network devices of the other controller's nanotubes to the second controller's nanotubes and performs step 430.

Optionally, if the number of other network devices controlling the current load does not exceed the number threshold, or the current CPU memory usage rate of the other controllers does not exceed the usage threshold, the first controller may not perform the smooth handover. However, since the number of network devices currently loaded by the second controller is 0, the first controller may also select several network devices from other controllers respectively for smooth switching, so as to further balance the load.

Step 430, if yes, selecting a third controller from the other controllers;

specifically, if the first controller determines to smoothly switch the portion of the network devices of the other controller nanotubes to the second controller nanotube, the first controller selects the third controller from the other controllers according to the description of step 420. The number of third controllers selected may be one or more.

In one example, the first controller selects a controller that is the maximum of the number of nanotube network devices (e.g., 9000) or the maximum of CPU memory usage (e.g., 90%) as the third controller. That is, the third controller is the controller with the largest number of nanotubes or the highest utilization rate of the CPU memory.

In another example, the first controller selects a plurality of controllers whose number of nanotube network devices exceeds a number threshold or whose CPU memory usage exceeds a usage threshold as the third controller.

Step 440, sending different first notification messages to the second controller and the third controller respectively, so that the second controller and the third controller perform nanotube switching of the network device according to the received first notification messages.

Specifically, after the first controller selects the third controller, a plurality of first notification messages are generated according to the description of step 430. The first controller sends different first notification messages to the second controller and the third controller respectively. Wherein the first notification message sent by the first controller to the second controller may be the same as the first notification message referred to in step 310 of the previous embodiment, and the first notification message sent by the first controller to the third controller may be the same as the second notification message of the previous embodiment.

And the second controller and the third controller respectively switch the nanotubes of the network equipment according to the first notification messages received by the second controller and the third controller. And the second controller and the third controller switch the nanotubes of the network equipment according to the received first notification message. The switching process performed by the second controller may refer specifically to the processes from step 310 to step 340 in the previous embodiment, and the switching process performed by the third controller may refer specifically to the process that the first controller receives the second notification message in the previous embodiment, which will not be described again.

Therefore, when a second controller is newly added into the controller cluster, the first controller acquires the state attribute of other controllers except the second controller in the controller cluster by applying the network equipment management method; according to the state attribute of other controllers, the first controller determines whether to smoothly switch part of network equipment of the other controller nanotubes to the second controller nanotube; if yes, the first controller selects a third controller from the other controllers; the first controller respectively sends different first notification messages to the second controller and the third controller so that the second controller and the third controller can carry out the NA Guan Qiehuan of the network device according to the received first notification messages; the first controller is a master controller in the controller cluster.

Therefore, the reliability management capability of the controllers in the controller cluster to the network equipment is improved, the number of the controllers in the dynamic capacity-expansion controller cluster is supported, and meanwhile, the load adjustment can be realized on the premise of not affecting the service. The method solves the problems that when the number of network devices is increased in the existing mode, the network devices cannot be guaranteed to be uniformly loaded to different controllers, and when the number of the controllers is increased, the existing NETCONF session is rebuilt, and the service availability is affected.

Optionally, in the embodiment of the present application, the method further includes a process that, after the network device newly joins in the SDN network, the first controller selects the nanotube controller for the newly joining network device.

Specifically, when network equipment is newly added in the SDN network, the first controller obtains the number of netcon sessions of each controller in the controller cluster. The first controller takes a fourth controller with the smallest number of NETCONF sessions as a controller of the nano-network equipment.

The first controller generates and sends a second notification message to the fourth controller, the second notification including a message type and a device identification of a newly joined network device within the SDN network. Wherein the message type specifically means that the second notification message is a notification of establishing a nanotube right.

According to the message type, the fourth controller determines that the second notification message is a nanotube right notification establishment, and also determines that the network device indicated by the device identifier is not received by the network device according to the device identifier. Thus, the fourth controller determines that the first controller initiates establishment of the nanotubes and that the network device to be indicated by the device identification is to be nanotubes by the fourth controller.

According to the message type, the fourth controller acquires the connection distributed lock. The fourth controller invokes an interface of the application module requesting acquisition of the connection distributed lock. If the connection distributed lock is not occupied by other controllers at this time, the fourth controller can acquire the connection distributed lock, and the application module records the occupation process of the fourth controller.

And according to the equipment identification, the fourth controller establishes a NETCONF session with the network equipment. If the fourth controller acquires the connection distributed lock and the NETCONF session is established with the network equipment, the fourth controller carries out nano-tube on the network equipment.

Optionally, in the embodiment of the present application, the method further includes the step that the fifth controller sends a third notification message to the first controller to automatically request to implement a load balancing process.

Specifically, in one case, the fifth controller identifies the number of network devices of its own nanotubes. If the number of network devices of the fifth controller nanotube exceeds the number threshold, the fifth controller determines that the self load is too large. The fifth controller generates and transmits a third notification message to the first controller.

In another case, when the fifth controller detects that the abnormality, the fault and the like of the fifth controller are not suitable for carrying out the nano-tube on the network equipment, that is, the current state of the fifth controller does not meet the working state, the fifth controller generates and sends a third notification message to the first controller.

The third notification message includes a message type and a device identification of the network device of the fifth controller nanotube. Wherein the message type specifically means that the third notification message is a transfer nanotube right notification. The device identification of the network device may be a device identification of a portion of the network devices of the fifth controller nanotube.

It may be appreciated that, after the fifth controller determines that the load of the fifth controller is excessive, or the current state of the fifth controller does not satisfy the working state, the fifth controller may select a part of network devices from all network devices of the self-nanotubes and request the first controller to transfer the sodium Guan Quan of the selected part of network devices.

After receiving the third notification message, the first controller obtains the message type and the device identifier of the network device from the third notification message. According to the message type, the first controller determines that the third notification message is a transfer nanotube right notification, and determines that the current load of the fifth controller is excessive or the current state does not meet the working state.

Depending on the message type, the first controller may obtain status attributes of the other controllers including, but not limited to, the number of network devices of the nanotube, CPU memory usage, and the like. And through the state attribute, the first controller selects a controller with smaller number of nanotubes and lower CPU memory utilization rate as a sixth controller.

After the first controller selects the sixth controller, two fourth known messages are generated and sent to the fifth controller and the sixth controller respectively. The fourth notification message sent by the first controller to the fifth controller may be the same as the second notification message in the previous embodiment, and the fourth notification message sent by the first controller to the sixth controller may be the same as the first notification message related to step 310 in the previous embodiment.

And the fifth controller and the sixth controller perform the nanotube switching of the network equipment indicated by the equipment identification according to the received fourth known message. The handover procedure performed by the sixth controller may specifically refer to the procedures of steps 310 to 340, and the handover procedure performed by the fifth controller may specifically refer to the procedure of receiving the second notification message, which will not be described herein.

Based on the same inventive concept, the embodiment of the application also provides a network equipment management device corresponding to the network equipment management method. Referring to fig. 5, fig. 5 is a network device management apparatus provided in an embodiment of the present application, where the apparatus is applied to a first controller, and the apparatus includes;

A receiving unit 510, configured to receive a first notification message sent by a second controller in the controller cluster, where the first notification message includes a message type and a device identifier of a network device to be managed;

an establishing unit 520, configured to establish a switch distributed lock according to the message type;

a releasing unit 530, configured to release the switched distributed lock after the network device indicated by the device identifier completes the establishment of the netcon session, and determine whether a connected distributed lock is acquired;

a nanotube unit 540, configured to perform a nanotube on the network device if the nanotube unit is acquired;

the first controller is a controller newly added into the controller cluster, or is a controller already in the controller cluster, and the second controller is a master controller in the controller cluster.

Optionally, the releasing unit 530 is further configured to continuously determine whether the connection distributed lock is acquired if the connection distributed lock is not acquired.

Optionally, the receiving unit 510 is further configured to receive a second notification message sent by the second controller, where the second notification message includes a message type and a device identifier of a network device of the first controller nanotube;

The apparatus further comprises: a judging unit (not shown) for judging whether the switching distributed lock is acquired according to the message type;

the releasing unit 530 is further configured to, if the connection distributed lock is acquired, release the connection distributed lock, and close a netcon f session established with the network device indicated by the device identifier;

the releasing unit 530 is further configured to release the switching distributed lock.

Optionally, the apparatus further comprises: a sending unit (not shown in the figure) configured to send a third notification message to the second controller when the number of network devices of the first controller nanotube exceeds a number threshold or the current state of the first controller does not satisfy the working state, where the third notification message includes a message type and a device identifier of the network device of the first controller nanotube, so that the second controller selects a third controller from other controllers in the controller cluster except for the first controller according to the message type, and sends different fourth notification messages to the first controller and the third controller respectively, where the first controller and the third controller perform nanotube switching of the network device indicated by the device identifier according to the received fourth notification message.

Optionally, the receiving unit 510 is further configured to, when the first controller is a controller already in the controller cluster, receive a fourth notification message sent by the second controller, where the fourth notification includes a message type and a device identifier of a newly added network device in the SDN network;

the apparatus further comprises: an acquisition unit (not shown in the figure) for acquiring the connection distributed lock according to the message type;

an establishing unit (not shown in the figure) is configured to establish a netcon f session with the network device according to the device identifier.

Therefore, by applying the network device management apparatus provided by the application, the first controller receives the first notification message sent by the second controller in the controller cluster, where the first notification message includes a message type and a device identifier of the network device to be managed; according to the message type, the first controller establishes a switching distributed lock; after the network equipment indicated by the equipment identifier completes the establishment of the NETCONF session, the first controller releases the switching distributed lock and judges whether the connection distributed lock is acquired or not; if so, the first controller carries out nano-tube on the network equipment; the first controller is a controller newly added into the controller cluster, or is a controller already in the controller cluster, and the second controller is a master controller in the controller cluster.

Therefore, the reliability management capability of the controllers in the controller cluster to the network equipment is improved, the number of the controllers in the dynamic capacity-expansion controller cluster is supported, and meanwhile, the load adjustment can be realized on the premise of not affecting the service. The method solves the problems that when the number of network devices is increased in the existing mode, the network devices cannot be guaranteed to be uniformly loaded to different controllers, and when the number of the controllers is increased, the existing NETCONF session is rebuilt, and the service availability is affected.

Based on the same inventive concept, the embodiment of the application also provides a network equipment management device corresponding to the network equipment management method. Referring to fig. 6, fig. 6 is another network device management apparatus provided in an embodiment of the present application, where the apparatus is applied to a first controller, and the apparatus includes;

an obtaining unit 610, configured to obtain a state attribute of a controller in the controller cluster except for a second controller when the second controller is newly added in the controller cluster;

a determining unit 620, configured to determine whether to smoothly switch a part of network devices of the other controller nanotubes to the second controller nanotube according to the state attribute of the other controller;

A selecting unit 630, configured to select a third controller from the other controllers if yes;

a sending unit 640, configured to send different first notification messages to the second controller and the third controller, respectively, so that the second controller and the third controller perform a per Guan Qiehuan of the network device according to the received first notification messages;

the first controller is a master controller in the controller cluster.

Optionally, the obtaining unit 610 is further configured to obtain, when a network device is newly added in the SDN network, a number of netcon f sessions of each controller in the controller cluster;

the apparatus further comprises: an execution unit (not shown in the figure) configured to take the fourth controller with the smallest number of netcon f sessions as a controller of the network device;

the sending unit 640 is further configured to send a second notification message to the fourth controller, where the second notification message includes a message type and a device identifier of a network device newly added in the SDN network, so that the fourth controller obtains a connection distributed lock according to the message type, and establishes a netcon session with the network device according to the device identifier.

Optionally, the apparatus further comprises: a receiving unit (not shown in the figure) configured to receive a third notification message sent by a fifth controller in the controller cluster, where the third notification message includes a message type and a device identifier of a network device of the fifth controller nanotube;

the obtaining unit 610 is further configured to obtain, according to the message type, a state attribute of a controller other than the fifth controller in the controller cluster;

the apparatus further comprises: a selecting unit (not shown) for selecting a sixth controller from the other controllers according to the state attribute of the other controllers;

the sending unit 640 is further configured to send different fourth notification messages to the fifth controller and the sixth controller, respectively, so that the fifth controller and the sixth controller perform nanotube switching of the network device according to the received fourth notification messages.

Therefore, when the second controller is newly added into the controller cluster, the first controller acquires the state attribute of other controllers except the second controller in the controller cluster by using the network equipment management device provided by the application; according to the state attribute of other controllers, the first controller determines whether to smoothly switch part of network equipment of the other controller nanotubes to the second controller nanotube; if yes, the first controller selects a third controller from the other controllers; the first controller respectively sends different first notification messages to the second controller and the third controller so that the second controller and the third controller can carry out the NA Guan Qiehuan of the network device according to the received first notification messages; the first controller is a master controller in the controller cluster.

Therefore, the reliability management capability of the controllers in the controller cluster to the network equipment is improved, the number of the controllers in the dynamic capacity-expansion controller cluster is supported, and meanwhile, the load adjustment can be realized on the premise of not affecting the service. The method solves the problems that when the number of network devices is increased in the existing mode, the network devices cannot be guaranteed to be uniformly loaded to different controllers, and when the number of the controllers is increased, the existing NETCONF session is rebuilt, and the service availability is affected.

Based on the same inventive concept, the present embodiment also provides a network device, as shown in fig. 7, including a processor 710, a transceiver 720, and a machine-readable storage medium 730, where the machine-readable storage medium 730 stores machine executable instructions capable of being executed by the processor 710, and the processor 710 is caused by the machine executable instructions to perform the network device management method provided by the present embodiment. The network device management apparatus shown in fig. 5 and 6 may be implemented by using the hardware configuration of the network device shown in fig. 7.

The computer readable storage medium 730 may include a random access Memory (e.g., random Access Memory, or simply, RAM) or a nonvolatile Memory (e.g., NVM), such as at least one magnetic disk Memory. Optionally, the computer readable storage medium 730 may also be at least one storage device located remotely from the processor 710.

The processor 710 may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; it may also be a digital signal processor (English: digital Signal Processor; DSP; for short), an application specific integrated circuit (English: application Specific Integrated Circuit; ASIC; for short), a Field programmable gate array (English: field-Programmable Gate Array; FPGA; for short), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components.

In this embodiment, processor 710, by reading machine-executable instructions stored in machine-readable storage medium 730, is caused by the machine-executable instructions to implement processor 710 itself and invoke transceiver 720 to perform the network device management methods described in the embodiments of the present application previously.

In addition, the present embodiments provide a machine-readable storage medium 730, the machine-readable storage medium 730 storing machine-executable instructions that, when invoked and executed by the processor 710, cause the processor 710 itself and the invoking transceiver 720 to perform the network device management methods described in the previous embodiments of the present application.

The implementation process of the functions and roles of each unit in the above device is specifically shown in the implementation process of the corresponding steps in the above method, and will not be described herein again.

For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments. The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purposes of the present application. Those of ordinary skill in the art will understand and implement the present invention without undue burden.

For the network device management apparatus and the machine-readable storage medium embodiments, since the method content involved is substantially similar to the method embodiments described above, the description is relatively simple, and the relevant points are referred to in the description of the method embodiments.

The foregoing description of the preferred embodiments of the present invention is not intended to limit the invention to the precise form disclosed, and any modifications, equivalents, improvements and alternatives falling within the spirit and principles of the present invention are intended to be included within the scope of the present invention.

Claims (10)

1. A network device management method, wherein the method is applied to a first controller, the method comprising;

receiving a first notification message sent by a second controller in the controller cluster, wherein the first notification message comprises a message type and a device identifier of network devices to be managed;

establishing a switching distributed lock according to the message type;

releasing the switching distributed lock after the network equipment indicated by the equipment identifier completes the establishment of the NETCONF session, and judging whether the connection distributed lock is acquired or not;

if so, performing nano-tube on the network equipment;

the first controller is a controller newly added into the controller cluster, or is a controller already in the controller cluster, and the second controller is a master controller in the controller cluster.

2. The method according to claim 1, wherein the method further comprises:

receiving a second notification message sent by the second controller, wherein the second notification message comprises a message type and a device identifier of a network device of the first controller nanotube;

judging whether the switching distributed lock is acquired or not according to the message type;

If the network equipment is acquired, releasing the connection distributed lock, and closing a NETCONF session established with the network equipment indicated by the equipment identifier;

releasing the switching distributed lock.

3. The method according to any one of claims 1 or 2, further comprising:

if the connection distributed lock is not obtained, continuing to judge whether the connection distributed lock is obtained or not;

if the switching distributed lock is not acquired, continuing to judge whether the switching distributed lock is acquired or not.

4. The method according to claim 1, wherein the method further comprises:

when the number of network devices of the first controller nanotube exceeds a number threshold or the current state of the first controller does not meet the working state, a third notification message is sent to the second controller, wherein the third notification message comprises a message type and a device identifier of the network device of the first controller nanotube, so that the second controller selects a third controller from other controllers except the first controller in the controller cluster according to the message type, and sends different fourth notification messages to the first controller and the third controller respectively, and the first controller and the third controller switch the nanotubes of the network device indicated by the device identifier according to the received fourth notification message.

5. The method according to claim 1, wherein the method further comprises:

when the first controller is a controller in the controller cluster, receiving a fourth notification message sent by the second controller, wherein the fourth notification message comprises a message type and a device identifier of newly added network devices in an SDN network;

acquiring the connection distributed lock according to the message type;

and establishing NETCONF session with the network equipment according to the equipment identifier.

6. A network device management method, wherein the method is applied to a first controller, the method comprising;

when a second controller is newly added into the controller cluster, acquiring state attributes of other controllers except the second controller in the controller cluster;

determining whether to smoothly switch part of network equipment of the other controller nanotubes to the second controller nanotube according to the state attribute of the other controller;

if yes, selecting a third controller from the other controllers;

respectively sending different first notification messages to the second controller and the third controller, so that the second controller and the third controller perform NA Guan Qiehuan of the network device according to the received first notification messages;

The first controller is a master controller in the controller cluster.

7. The method of claim 6, wherein the method further comprises:

when network equipment is newly added in an SDN network, acquiring the NETCONF session number of each controller in the controller cluster;

taking the fourth controller with the smallest number of NETCONF sessions as a controller of the network equipment;

and sending a second notification message to the fourth controller, wherein the second notification message comprises a message type and a device identifier of a newly added network device in the SDN network, so that the fourth controller acquires a connection distributed lock according to the message type, and establishes a NETCONF session with the network device according to the device identifier.

8. The method of claim 6, wherein the method further comprises:

receiving a third notification message sent by a fifth controller in the controller cluster, wherein the third notification message comprises a message type and a device identifier of a network device of the fifth controller nanotube;

acquiring state attributes of other controllers except the fifth controller in the controller cluster according to the message type;

Selecting a sixth controller from the other controllers according to the state attribute of the other controllers;

and respectively sending different fourth known messages to the fifth controller and the sixth controller so that the fifth controller and the sixth controller can switch the nanotubes of the network equipment according to the received fourth known messages.

9. A network device management apparatus, the apparatus being applied to a first controller, the apparatus comprising;

a receiving unit, configured to receive a first notification message sent by a second controller in the controller cluster, where the first notification message includes a message type and a device identifier of a network device to be managed;

the establishing unit is used for establishing a switching distributed lock according to the message type;

the release unit is used for releasing the switching distributed lock after the network equipment indicated by the equipment identifier completes the establishment of the NETCONF session, and judging whether the connection distributed lock is acquired or not;

the network equipment comprises a network equipment, a nanotube unit and a control unit, wherein the network equipment is used for acquiring network equipment;

the first controller is a controller newly added into the controller cluster, or is a controller already in the controller cluster, and the second controller is a master controller in the controller cluster.

10. A network device management apparatus, the apparatus being applied to a first controller, the apparatus comprising;

the system comprises an acquisition unit, a control unit and a control unit, wherein the acquisition unit is used for acquiring state attributes of other controllers except for a second controller in a controller cluster when the second controller is newly added in the controller cluster;

the determining unit is used for determining whether to smoothly switch part of network equipment of the other controller nanotubes to the second controller nanotube according to the state attribute of the other controller;

a selecting unit, configured to select a third controller from the other controllers if yes;

a sending unit, configured to send different first notification messages to the second controller and the third controller respectively, so that the second controller and the third controller perform a per Guan Qiehuan of the network device according to the received first notification messages;

the first controller is a master controller in the controller cluster.

Images