CN109450709A - Asynchronous message configuration method, upper delivery method, controller and the network equipment - Google Patents

Asynchronous message configuration method, upper delivery method, controller and the network equipment Download PDF

Info

Publication number
CN109450709A
CN109450709A CN201811562607.3A CN201811562607A CN109450709A CN 109450709 A CN109450709 A CN 109450709A CN 201811562607 A CN201811562607 A CN 201811562607A CN 109450709 A CN109450709 A CN 109450709A
Authority
CN
China
Prior art keywords
controller
message
asynchronous message
network equipment
asynchronous
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.)
Granted
Application number
CN201811562607.3A
Other languages
Chinese (zh)
Other versions
CN109450709B (en
Inventor
宋小恒
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
New H3C Information Technologies Co Ltd
Original Assignee
New H3C Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by New H3C Technologies Co Ltd filed Critical New H3C Technologies Co Ltd
Priority to CN201811562607.3A priority Critical patent/CN109450709B/en
Publication of CN109450709A publication Critical patent/CN109450709A/en
Application granted granted Critical
Publication of CN109450709B publication Critical patent/CN109450709B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • H04L41/0654Management of faults, events, alarms or notifications using network fault recovery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1001Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1034Reaction to server failures by a load balancer

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The application provides a kind of asynchronous message configuration method, upper delivery method, controller and the network equipment, issued from controller to the network equipment carry type of message, controller mark and share weight asynchronous message configuration, the network equipment is shared according to the asynchronous message configuration received to be sent, so as to realize that sharing for same type asynchronous message is sent.

Description

Asynchronous message configuration method, upper delivery method, controller and the network equipment
Technical field
This application involves network communication technology field, in particular to a kind of asynchronous message configuration method, on the side of sending Method, controller and the network equipment.
Background technique
SDN (Software Defined Network, software defined network) is a kind of novel network architecture, pass through by Network-based control level and forwarding plane separate, and are managed by control plane of the controller to each network equipment, realization pair The routing of the network equipment and being uniformly controlled for transmission rule strategy etc., so that can be cleverer to the flow control of network It is living.It, in some embodiments, can be using including more in order to improve the processing capacity and redundancy ability of controller in SDN framework The controller cluster of a controller controls SDN network equipment.
Summary of the invention
In a first aspect, the application provides a kind of asynchronous message configuration method, applied to the master in SDN framework controller cluster Controller;The described method includes:
Obtain the asynchronous message configuration of the network equipment, asynchronous message configuration includes type of message, described at least one The mark for the controller for including in controller cluster and corresponding with the mark of controller share weight;
The asynchronous message configuration is sent to the network equipment, so that the network equipment is configured according to the asynchronous message, Asynchronous message corresponding with the type of message in the network equipment corresponding is shared into weight according to the mark of each controller Corresponding controller included in the asynchronous message configuration is given on respectively.
Optionally, in the above-mentioned methods, the step of asynchronous message configuration for obtaining the network equipment, comprising:
Obtain the corresponding different asynchronous message configuration of the different network equipments, wherein in the different asynchronous message Controller mark or share weighted.
Optionally, in the above-mentioned methods, further includes:
Detect the working condition in the controller cluster from controller;
When detecting the failure from controller, for the network for sending asynchronous message on the slave controller to failure Equipment issues new asynchronous message configuration, so as to receive the network equipment of the new asynchronous message configuration according to described new Asynchronous message configuration will be sent on asynchronous message to the controller to normal work.
Optionally, in the above-mentioned methods, the asynchronous message configuration further includes in message corresponding with the type of message Mode is sent, it includes sending on sending or broadcast in unicast that mode is sent in the message;
It is then, described to send the step of asynchronous message configures to the network equipment, comprising:
It carries the asynchronous message of mode is sent to configure in the message to network equipment transmission, make to receive described asynchronous disappear The type of message of breath configuration is the network equipment that send in unicast, is configured according to the asynchronous message, by the network equipment with institute State the corresponding asynchronous message of type of message according to each controller mark it is corresponding share weight give in unicast respectively it is described Included corresponding controller in asynchronous message configuration;Or make the type of message broadcast for receiving the asynchronous message configuration On the network equipment that send, configured according to the asynchronous message, asynchronous disappeared corresponding with the type of message in the network equipment Breath is broadcasted in the controller cluster.
Second aspect, the application provide delivery method on a kind of asynchronous message, set applied to the network used in SDN framework It is standby, which comprises
The asynchronous message configuration that controller cluster issues is received, the asynchronous message configuration includes type of message, at least one The mark for the controller for including in a controller cluster and corresponding with the mark of controller share weight;
It is configured according to the asynchronous message, by asynchronous message corresponding with the type of message in the network equipment according to every The mark of a controller is corresponding share weight respectively on give corresponding controller included in asynchronous message configuration.
Optionally, in the above-mentioned methods, the asynchronous message configuration further includes in message corresponding with the type of message Mode is sent, it includes sending on sending or broadcast in unicast that mode is sent in the message;
It is described by asynchronous message corresponding with the type of message in the network equipment according to the mark pair of each controller Answer share weight respectively on the step of giving corresponding controller in the controller cluster, comprising:
Correspond to the asynchronous message sent in unicast for the type of message, is configured according to the asynchronous message, by the net Asynchronous message corresponding with the type of message distinguishes list according to the corresponding weight of sharing of mark of each controller in network equipment It broadcasts and gives corresponding controller included in the asynchronous message configuration;The method also includes:
Correspond to the asynchronous message sent in broadcast for the type of message, by the asynchronous message of the type of message described It is broadcasted in controller cluster.
Optionally, in the above-mentioned methods, described to press asynchronous message corresponding with the type of message in the network equipment According to each controller mark it is corresponding share weight respectively on give corresponding controller in the controller cluster the step of, Include:
The mark for calculating separately each controller in asynchronous message configuration corresponding shares weight and controller cluster In the ratio for sharing the sum of weight of each controller corresponding share ratio as the mark of the controller;
By asynchronous message corresponding with the type of message in the network equipment according to corresponding point of mark of each controller Load ratio, which is shared, gives corresponding controller in the controller cluster.
Optionally, in the above-mentioned methods, in the controller cluster include master controller and from controller, the reception The step of asynchronous message configuration that controller cluster issues, comprising:
The asynchronous message configuration is obtained from the master controller;
The method also includes:
When receiving the configuration acquisition request arbitrarily sent from controller, the asynchronous message of the network equipment is configured and is sent To described from controller.
The third aspect, the application provide a kind of controller, including machine readable storage medium and processor, and the machine can It reads storage medium and is stored with machine-executable instruction, machine-executable instruction rush when being called or being executed by the processor The controller is set to realize asynchronous message configuration method provided by the present application.
Fourth aspect, the application provide a kind of network equipment, including machine readable storage medium and processor, the machine Readable storage medium storing program for executing is stored with machine-executable instruction, and the machine-executable instruction is when being called or being executed by the processor The network equipment is promoted to realize a message above method provided by the present application.
In terms of existing technologies, the application has the advantages that
Asynchronous message configuration method, upper delivery method, controller and the network equipment provided in this embodiment, from controller to net Network equipment issue carry type of message, controller mark and share the asynchronous message configuration of weight, the network equipment is according to connecing The asynchronous message configuration received, which is shared, to be sent, so as to realize that sharing for same type asynchronous message is sent.
Detailed description of the invention
Technical solution in ord to more clearly illustrate embodiments of the present application, below will be to needed in the embodiment attached Figure is briefly described, it should be understood that the following drawings illustrates only some embodiments of the application, therefore is not construed as pair The restriction of range for those of ordinary skill in the art without creative efforts, can also be according to this A little attached drawings obtain other relevant attached drawings.
Fig. 1 is the interaction schematic diagram of SDN network provided by the embodiments of the present application;
Fig. 2 is the flow diagram of asynchronous message configuration method provided by the embodiments of the present application;
Fig. 3 is the structural schematic diagram of asynchronous message provided by the embodiments of the present application setting notice;
Fig. 4 is one of the flow diagram of delivery method on asynchronous message provided by the embodiments of the present application;
Fig. 5 is two of the flow diagram of delivery method on asynchronous message provided by the embodiments of the present application;
Fig. 6 is the correspondence diagram of asynchronous message type and mask field as defined in Openflow agreement;
Fig. 7 is the structural schematic diagram of the network equipment provided by the embodiments of the present application;
Fig. 8 is to send one of the functional block diagram of device on asynchronous message provided by the embodiments of the present application;
Fig. 9 be asynchronous message provided by the embodiments of the present application on send device the functional block diagram two;
Figure 10 is the structural schematic diagram of controller provided by the embodiments of the present application;
Figure 11 is the functional block diagram of asynchronous message configuration device provided by the embodiments of the present application.
Icon: 100A, 100B, 100C, 100D- network equipment;Device is sent on 110- asynchronous message;111- configuration receives mould Block;112-, which shares, send module;Module is sent in 113- broadcast;Module is sent in 114- configuration;The first machine readable storage of 120- is situated between Matter;130- first processor;140- the first system bus;20- controller cluster;200A, 200B, 200C- controller;210- is different Walk message arrangement device;211- configuration distributing module;The second machine readable storage medium of 220-;230- second processor;240- Second system bus;300- virtual machine.
Specific embodiment
To keep the purposes, technical schemes and advantages of the embodiment of the present application clearer, below in conjunction with the embodiment of the present application In attached drawing, the technical scheme in the embodiment of the application is clearly and completely described, it is clear that described embodiment is Some embodiments of the present application, instead of all the embodiments.The application being usually described and illustrated herein in the accompanying drawings is implemented The component of example can be arranged and be designed with a variety of different configurations.
Therefore, the detailed description of the embodiments herein provided in the accompanying drawings is not intended to limit below claimed Scope of the present application, but be merely representative of the selected embodiment of the application.Based on the embodiment in the application, this field is common Technical staff's every other embodiment obtained without creative efforts belongs to the model of the application protection It encloses.
It should also be noted that similar label and letter indicate similar terms in following attached drawing, therefore, once a certain Xiang Yi It is defined in a attached drawing, does not then need that it is further defined and explained in subsequent attached drawing.
In the SDN framework using Openflow agreement, the network equipment is needed to the various types of message of controller report, These message are referred to as asynchronous message (Asynchronous).Asynchronous message may include for informing the controller network equipment The Port-Status of the Packet-in message of the data packet received, port status for informing the controller network equipment Message, for informing deleted Flow-Removed message of the flow table on the controller network equipment etc..
In some embodiments, the controller cluster of SDN framework generally includes master controller and multiple from control Device, each controller can establish Openflow with the network equipment of each Self management respectively and connect to control to the network equipment System.Different controllers can independently control whether the network equipment send certain type of message on the controller, for example, control (OFPT_SET_ASYNC) informing network equipment can be arranged to the control in device processed by the asynchronous message in Openflow agreement Certain type of asynchronous message is sent on device.In this way, it can make the network equipment will be on the asynchronous message of different types Different controllers are given, realizes that the asynchronous message based on type of message is shared to a certain extent and send.
But the amount of sending has very big difference on different types of asynchronous message, for example, Packet-in message on the amount of sending it is logical It often can be used to carry out the message of network device state notice much larger than other, and Packet-in message only needs in cluster One controller is handled, this makes the controller for handling such asynchronous message assume responsibility for very big processing pressure.This Multiple controller collaborations may be just needed to handle same type of asynchronous message in the case of kind.But in above-mentioned embodiment party In formula, each controller can only independently control whether the network equipment gives certain class message on oneself, and the network equipment can not use Share the mode sent by same type of a plurality of asynchronous message respectively on give different controllers.
In view of this, the present embodiment provides the asynchronous message configurations that a kind of network equipment is issued according to controller to disappear to asynchronous Breath is shared the scheme sent, and scheme provided in this embodiment is described in detail below.
Fig. 1 is please referred to, Fig. 1 is a kind of network of SDN framework provided in this embodiment, including by multiple controllers (such as controller 200A, 200B and 200C shown in FIG. 1) composition controller cluster 20 and can be with controller cluster 20 In each controller communication the network equipment (such as the network equipment 100A, 100B, 100C and 100D shown in FIG. 1).It is multiple Virtual machine 300 can be respectively connected to these network equipments.The network equipment needs the asynchronous message for generating itself to be sent to control Device cluster 20 is handled.
Openflow agreement is used in SDN framework provided in this embodiment, the network equipment shown in Fig. 1 can be Openflow interchanger, each network equipment can establish Openlow with each controller respectively and connect to carry out control information Interaction.In controller cluster 20, may include master controller (Master Controller) and at least one from control Device (Slave Controller) processed.
Referring to figure 2., Fig. 2 matches for a kind of asynchronous message applied to master controller in controller cluster shown in Fig. 1 20 The flow chart of method is set, it below will be to the method includes each steps to be described in detail.
Step S110 obtains the asynchronous message configuration (asynchronous of the network equipment Messageconfiguration), the asynchronous message configuration including including in type of message, at least one controller cluster The mark of controller and corresponding with the mark of controller share weight.
Step S120 sends asynchronous message configuration to the network equipment, so that the network equipment is configured according to asynchronous message, by this In the network equipment asynchronous message corresponding with type of message according to each controller mark it is corresponding share weight respectively on give To corresponding controller included in asynchronous message configuration.
It optionally, can be each on a master controller by administrator in an embodiment of the present embodiment The network equipment is arranged asynchronous message and configures, and master controller is configured according to asynchronous message generates asynchronous message setting notice (OFPT_ SET_ASYNC) message and it is sent to the network equipment.
In the another embodiment of the present embodiment, it is also possible to by master controller according to current network condition or net The operating condition etc. of network equipment is automatically generated asynchronous message configuration and is sent to the network equipment.
It in the present embodiment, can in asynchronous message configuration in order to which informing network device-dependent shares the necessary information sent To include the mark of type of message, the controller for including at least one controller cluster and corresponding with the mark of each controller Share weight.
Wherein, type of message is used to indicate the type that the network equipment is shared the asynchronous message sent;Controller Mark be used to indicate the controller for needing to receive the asynchronous message of the type.For example, the mark of controller can be controller ID in controller cluster 20;It shares weight and is used to indicate and asynchronous message is being shared to share ratio when giving controller Example.
Referring to figure 3., Fig. 3 shows a kind of example for carrying the asynchronous message setting notice of asynchronous message configuration information Property structure, wherein OFP_ASYNC_CONFIG_PROP_REASONS attribute for record it is relevant to being sent on asynchronous message various Characteristic.
As shown in figure 3, in the present embodiment, the type of message in asynchronous message configuration can recorde in OFP_ASYNC_ Type of message in CONFIG_PROP_REASONS attribute, i.e., in type field, the mark of controller can be sequentially recorded in control The identification field of device processed, i.e., in controller_id field, the corresponding weight of sharing of the mark of each controller be can recorde Controller weight field, i.e., in controller_weight field, wherein the mark of the controller in controller_id field Knowledge is corresponded with the weight of sharing in controller_weight field according to sequence order.
Optionally, in an embodiment of the present embodiment, master controller can issue phase for heterogeneous networks equipment Same asynchronous message configuration.
In the another embodiment of the present embodiment, the available different network of master controller is set in step s 110 Standby corresponding different asynchronous message configuration, and in the step s 120, it will asynchronous message configuration point corresponding with each network equipment It is not sent to each network equipment.Wherein, the mark of the controller in different asynchronous messages or weighted is shared
It is issued from controller to the network equipment in scheme provided in this embodiment based on above-mentioned design and carries message Type, the mark of controller and share weight asynchronous message configuration, the network equipment according to the asynchronous message received configure into Row, which is shared, to be sent, so as to realize that sharing for same type asynchronous message is sent.
Optionally, in the present embodiment, master controller can detecte the working condition in controller cluster 20 from controller, It is new for sending the network equipment of asynchronous message to issue on the slave controller to failure when detecting from controller failure Asynchronous message configuration, so that the network equipment for receiving new asynchronous message configuration will be different according to the new asynchronous message configuration It send in step message to the controller to normal work.In this way, master controller can be in other member conditions of controller cluster 20 It adjusts to provide and deliver on the asynchronous message of corresponding network equipment in time when changing and set, enable the asynchronous message quilt sent on the network equipment The controller of normal work is handled.
Optionally, in the present embodiment, master controller can different concrete scenes match using not ipsilateral strategy generating is new Set message, for example, master controller it is available respectively from the loading condition of controller (e.g., obtain sent from controller to respectively it is asynchronous The quantity of the network equipment of message), and when issuing new asynchronous message configuration to the network equipment, feelings are loaded according to from controller Condition generates new asynchronous message configuration, make the network equipment to light load and normal work controller on send asynchronous message.
Optionally, different controller receptions may be needed to handle different asynchronous messages, for example, for Packet-in message may only need the network equipment to be sent to a controller and be handled;And for port status Port- Status message, it may be necessary to which the network equipment is notified to each controller in controller cluster 20.
Therefore, optionally, in the present embodiment, the configuration of main control issues asynchronous message can also include and type of message Mode is sent in corresponding message, it may include sending on sending or broadcast in unicast that mode is sent in message.
Master controller is carried to network equipment transmission send the asynchronous message of mode to configure in message, make to receive asynchronous disappear The type of message of breath configuration is the network equipment that send in unicast, is configured according to asynchronous message, by the network equipment with message class The corresponding asynchronous message of type gives asynchronous message configuration in unicast according to the corresponding weight of sharing of mark of each controller respectively In included corresponding controller;Or make the network equipment sent in the type of message broadcast for receiving asynchronous message configuration, It is configured according to asynchronous message, asynchronous message corresponding with type of message in the network equipment is carried out extensively in controller cluster It broadcasts.
In an embodiment of the present embodiment, the network equipment can be asynchronous corresponding to sending in broadcast by type of message Message is broadcast to each controller in controller cluster 20.
In the another embodiment of the present embodiment, the network equipment, which can also correspond to type of message in broadcast, to be sent Asynchronous message broadcast (or multicast) gives the corresponding multiple controllers of mark of the controller recorded in asynchronous message configuration.
Referring to figure 4., Fig. 4 is the flow chart applied to delivery method on a kind of asynchronous message of the network equipment shown in FIG. 1, It below will be to the method includes each steps to be described in detail.
Step S210 obtains asynchronous message configuration from controller cluster 20, and asynchronous message is configured including type of message, at least The mark of one controller and corresponding with the mark of each controller share weight.
Step S220, configures according to asynchronous message, by asynchronous message corresponding with type of message in the network equipment according to Each controller identifier is corresponding share weight respectively on give corresponding controller included in asynchronous message configuration.
In the present embodiment, the network equipment can receive different when sending on executing asynchronous message according to step S210 Message arrangement is walked, gives the asynchronous message of same type of message to corresponding controller in weight according to sharing.
For example, the multiple Packet-in message sent on needs can be buffered in by the network equipment for Packet-in message In the network equipment, and it will regularly be sent in the Packet-in message of caching.In the present embodiment, it can execute every time When being sent in Packet-in message, multiple Packet-in message in caching are distinguished according to corresponding ratio according to weight is shared Controller different in cluster is sent to be handled.
Optionally, in step S220, the network equipment can calculate separately the mark of each controller in asynchronous message configuration Know mark of the corresponding ratio for sharing the sum of weight for sharing each controller in weight and controller cluster 20 as the controller Know and corresponding shares ratio.For example, controller 200B is corresponding to share weight if the corresponding weight of sharing of controller 200A is 2 It is 1, then the corresponding ratio of sharing of controller 200A is 2/3, and the corresponding ratio of sharing of controller 200B is 1/3.Then by network In equipment asynchronous message corresponding with the type of message according to each controller mark it is corresponding share ratio and share give To corresponding controller in the controller cluster 20.
In the present embodiment, if further including sending mode in message in asynchronous message configuration, referring to figure 5., asynchronous message Upper delivery method can also include step S220 and step S230.
In step S220, the network equipment corresponds to the asynchronous message sent in unicast for type of message, disappears according to asynchronous Indicated in breath configuration share weight by the asynchronous message of the type of message respectively on give corresponding control in controller cluster 20 Device processed.
In step S230, the network equipment corresponds to the asynchronous message sent in broadcast for type of message, by the message class The asynchronous message of type is broadcasted in controller cluster 20.
Optionally, in the present embodiment, configuration acquisition request message (OFPT_ can be sent to the network equipment from controller GET_ASYNC_REQUEST).The network equipment is when receiving the configuration acquisition request that any one sends from controller, by this The asynchronous message configuration of the network equipment obtains back message (OFPT_GET_ASYNC_REPLY) by asynchronous message and is sent to this From controller.
Wherein, referring once again to Fig. 3, in the present embodiment, asynchronous message obtains back message (OFPT_GET_ASYNC_ REPLY) notice (OFPT_SET_ASYNC) can be arranged with asynchronous message has the same or similar structure, in this way, from control Device can obtain the relevant complete information for responding and obtaining and sending on the network equipment and asynchronous message by asynchronous message.
In this way, being configured from the controller also available asynchronous message to each network equipment, to occur in master controller When failure, it can continue to be sent into row pipe on the asynchronous message to the network equipment according to the asynchronous message configuration got from controller Reason.In addition, being from the asynchronous message that controller can also be sent on the asynchronous message configuration determination network equipment according to the network equipment It is no normal.
For convenience of skilled in the art realises that scheme provided in this embodiment, explains this implementation below by an example The scheme that example provides.
Referring once again to Fig. 1, in the network of SDN framework shown in Fig. 1, in controller cluster 20 include controller 200A, 200B and 200C, wherein controller 200A is master controller, and controller 200B and 200C are from controller.
The network equipment (including the network equipment 100A, 100B, 100C and 100D) is Openflow interchanger, and multiple users are empty Quasi- machine 300 is respectively connected to these network equipments, each controller in controller cluster 20 respectively with network equipment 100A, 100B, 100C establish Openflow with 100D and connect.
The network equipment can generate a large amount of message up sending controller clusters 20, such as Packet-in message at regular intervals. In order to reduce impact of the Packet-in message to single controller, it is desirable that the Packet-in information reporting of network equipment 100A arrives The Packet-in information reporting of controller 200A and controller 200B, network equipment 100B are to controller 200B and controller The Packet-in information reporting of 200C, network equipment 100C and network equipment 100D are to controller 200A and controller 200C.
Administrator is that each network equipment setting asynchronous message configures on the controller 200A as master controller, control Device 200A issues the asynchronous message for carrying corresponding asynchronous message configuration to the network equipment 100A, 100B, 100C and 100D respectively Setting notice (OFPT_SET_ASYNC) message.
Referring once again to Fig. 3, the structure of asynchronous message setting notice (OFPT_SET_ASYNC) message can be such as Fig. 3 institute Show, defines a kind of OFP_ASYNC_CONFIG_PROP_REASONS attribute structure in asynchronous message setting notice message, use In the relevant parameter of record asynchronous message configuration.Disappear in OFP_ASYNC_CONFIG_PROP_REASONS attribute structure with asynchronous Breath configures relevant primary fields and includes type of message (type), mask (mask), send mode (method), controller in message Mark (controller_id) and share weight (controller_weight) field, in which:
The parameter that type of message (type) is used to indicate in OFP_ASYNC_CONFIG_PROP_REASONS attribute structure is For the configuration of what type of asynchronous message.Fig. 6 is please referred to, Fig. 6 is type of message defined in Openflow agreement (type) corresponding relationship of the numerical value of field and asynchronous message type.For example, if OFP_ASYNC_CONFIG_PROP_REASONS The value of type of message (type) field is 0 in attribute structure, then corresponding asynchronous message type is " OFPACPT_PACKET_IN_ SLAV " indicates that the parameter recorded in the OFP_ASYNC_CONFIG_PROP_REASONS attribute structure is for providing Packet-in message how on send from controller.If the value of type of message (type) field is 1, corresponding asynchronous message class Type is " OFPACPT_PACKET_IN_MASTER " type, indicates the OFP_ASYNC_CONFIG_PROP_REASONS attribute knot The parameter recorded in structure be for regulation Packet-in message how on send master controller.
Mask (mask) field is used to indicate whether to send type of message (type) asynchronous message of field meaning type. It is provided in Openflow agreement, the type of every kind of asynchronous message shown in Fig. 6 can be corresponding in turn to the mask that overall length is 32 (mask) bit (that is, one in the 0th to the 31st) in.For example, " OFPACPT_PACKET_IN_SLAV " Type corresponds to the 0th of mask (mask), and " OFPACPT_PACKET_IN_MASTER " type is corresponding to mask (mask) 1st.In mask (mask) when position 1 corresponding with type of message (type) field, type of message (type) field institute is indicated Refer to that the asynchronous message of type needs to send;In mask (mask) when position 0 corresponding with type of message (type) field, indicate to disappear The asynchronous message of breath type (type) field meaning type does not need to send on again.For example, when type of message (type) field be 0 and When 0 position 1 mask (mask), indicate that the asynchronous message of " OFPACPT_PACKET_IN_SLAV " type needs to send;When disappearing When breath type (type) field is 0 and 0 position 0 mask (mask), " OFPACPT_PACKET_IN_SLAV " type is indicated Asynchronous message does not need to send.
It is the field that the present embodiment increases newly that mode (method) field is sent in message, is used to indicate asynchronous message using broadcast Or it is sent in unicast.
Mark (controller_id) field of controller is the field that the present embodiment increases newly, is used for recording controller collection The ID of one or more controllers in group sends asynchronous message to these controllers with instruction.
Sharing weight (controller_weight) field is the field that the present embodiment increases newly, shares weight (controller_weight) each controller in the value in field and mark (controller_id) field of controller Mark correspond, be used to indicate that each controller is corresponding to share weight.
Specifically, in the above example, for network equipment 100A, Packet-in message needs to be reported to master controller 200A and from controller 200B, due to providing in Openflow agreement, an OFP_ASYNC_CONFIG_PROP_REASONS belongs to Property structure can only record the parameter of a type of asynchronous message, therefore, the asynchronous message setting that network equipment 100A is received It may include the attribute of two OFP_ASYNC_CONFIG_PROP_REASONS structures in notice message, alternatively, setting to network When standby 100A issues asynchronous message notice message, two asynchronous message setting messages are issued, an asynchronous message setting message is used Asynchronous message is sent on master controller in instruction network equipment 100A, another asynchronous message setting message is used to indicate network and sets Standby 100A from controller to sending asynchronous message.
One corresponds to " OFPACPT_PACKET_IN_MASTER " type, another corresponds to " OFPACPT_PACKET_ IN_SLAVE " type.
Corresponding to " OFPACPT_PACKET_IN_MASTER " type OFP_ASYNC_CONFIG_PROP_REASONS attribute In, type of message (type) field value is 1, and the value of mask field (mask) is 0x2 (that is, the 1st position 1), indicates the network equipment 100A needs to send the asynchronous message of Packet-in type on master controller.Mark (controller_id) field of controller Value be controller 200A ID;It send the value of mode (method) field to correspond in message to be sent in weight unicast according to sharing; The value for sharing weight (controller_weight) field is, to indicate to send sharing for asynchronous message on master controller 200A Weight is 2.
Corresponding to " OFPACPT_PACKET_IN_SLAVE " type OFP_ASYNC_CONFIG_PROP_REASONS attribute In, type of message (type) field value is 0, and the value of mask (mask) field is 0x1 (that is, the 0th position 1), indicates the network equipment 100A is needed to the asynchronous message for sending Packet-in type from controller;Mark (controller_id) field of controller Value be controller 200B ID;It send the value of mode (method) field to correspond in message to be sent in weight unicast according to sharing; The value for sharing weight (controller_weight) field is 1, shares power with indicate to send asynchronous message on controller 200B Weight is 1.
It is configured according to above-mentioned asynchronous message, the ratio of controller 200A is sent in the Packet-in message of network equipment 100A It is 2/3, above sending the ratio of controller 200B is 1/3.
For network equipment 100B, Packet-in message needs to be reported to controller 200A and controller 200C.Therefore, It also include two OFP_ASYNC_CONFIG_PROP_ in the asynchronous message setting notice message that network equipment 100B is received The attribute of REASONS structure.
Corresponding to " OFPACPT_PACKET_IN_MASTER " type OFP_ASYNC_CONFIG_PROP_REASONS attribute It is received with network equipment 100A similar.
Unlike, correspond to " OFPACPT_PACKET_IN_SLAVE " type OFP_ASYNC_CONFIG_PROP_ In REASONS attribute, the value of type of message (type) field is 0, and the value of mask (mask) field is 0x1, indicates the network equipment 100B is needed to the asynchronous message for sending Packet-in type from controller;Mark (controller_id) field of controller Value be controller 200C ID;It send the value of mode (method) field to correspond in message to be sent in weight unicast according to sharing; The value for sharing weight (controller_weight) field is 1, shares weight with indicate asynchronous message on controller 200C It is 1.
It is configured according to above-mentioned asynchronous message, the ratio of controller 200A is sent in the Packet-in message of network equipment 100B It is 2/3, above sending the ratio of controller 200C is 1/3.
For the network equipment 100C and 100D, Packet-in message needs to be reported to controller 200B and controller 200C, So value includes an OFP_ASYNC_CONFIG_ in the asynchronous message setting notice that the network equipment 100C and 100D are received PROP_REASONS attribute.Wherein, the value of type of message (type) field is 0, and the value of mask (mask) field is 0x1, is indicated The network equipment 100C and 100D are needed to the asynchronous message for sending Packet-in type from controller;The mark of controller (controller_id) value of field is the ID of controller 200B and 200C;Mode (method) value pair of field is sent in message Ying Yu is sent in weight unicast according to sharing;Share weight (controller_weight) field value be (1,1), with indicate to The weight of sharing that asynchronous message is sent on controller 200B is 1, and it is 1 that the weight of sharing of asynchronous message is sent on controller 200C.
It is configured according to above-mentioned asynchronous message, send controller 200B in the Packet-in message of the network equipment 100C and 100D Ratio be 1/2, above send controller 200C ratio be 1/2.
After the setting mentioned above, controller 200A has received network equipment 100A's and network equipment 100B upper 2/3 Packet-in message, controller 200B have received the Packet-in message of network equipment 100A and network equipment 100B upper 1/3 And the Packet-in message of network equipment 100C and network equipment 100D upper 1/2, controller 200C have received network equipment 100C With the Packet-in message of network equipment 100D upper 1/2.
When member changes in controller cluster 20, such as controller 200C offline, at this time as the control of master controller Device 200A processed can timely respond to this offline event, issue new asynchronous message to network equipment 100C, network equipment 100D and set Notice is set, is adjusted to send 1/2 Packet-in to disappear on controller 200A with informing network equipment 100C, network equipment 100D Breath, 1/2 Packet-in message is sent on controller 200B.
Configuration acquisition request can also be sent to each network equipment 100 as the controller 200B or 200C from controller Message (OFPT_GET_ASYNC_REQUEST), the network equipment 100 is after receiving configuration acquisition request, according to the asynchronous of itself Message arrangement generates asynchronous message acquisition back message (OFPT_GET_ASYNC_REPLY) and is sent to controller 200B or 200C. Controller 200B or 200C can be according to sending on each network equipment 100 of the asynchronous message of each network equipment 100 configuration detection It is no correct, and asynchronous message configuration is backed up, to cope with the catastrophic failure of controller 200A.
Fig. 7 is please referred to, Fig. 7 is a kind of hardware structural diagram of the network equipment 100 provided in this embodiment.The network is set Standby 100 may include first processor 130 and the first machine readable storage medium 120.First processor 130 and first machine readable Storage medium 120 can be communicated via the first system bus 140.Also, the first machine readable storage medium 120 is stored with machine can It executes instruction, by reading and executing machine corresponding with logic is sent on asynchronous message in the first machine readable storage medium 120 Delivery method on above-described asynchronous message can be performed in executable instruction, first processor 130.
First machine readable storage medium 120 referred to herein can be any electronics, magnetism, optics or other physics Storage device may include or store information, such as executable instruction, data, etc..For example, machine readable storage medium can be with It is: RAM (Radom Access Memory, random access memory), volatile memory, nonvolatile memory, flash memory, deposits Store up driver (such as hard disk drive), solid state hard disk, any kind of storage dish (such as CD, dvd) or similar storage Medium or their combination.
Please refer to Fig. 8, the present embodiment also provides and send device 110 on a kind of asynchronous message, and device 110 is sent to wrap on asynchronous message Include at least one functional module that can be stored in a software form in the first machine readable storage medium 120.Functionally divide, It may include configuring receiving module 111 and sharing to send module 112 that device 110 is sent on asynchronous message.
Configuration receiving module 111 is used to receive the asynchronous message configuration that controller cluster 20 issues, asynchronous message configuration packet Include type of message, the mark for the controller for including at least one described controller cluster and corresponding with the mark of controller point Carry on a shoulder pole weight.
In the present embodiment, configuration receiving module 111 can be used for executing step S110 shown in Fig. 2, receive mould about configuration The specific descriptions of block 111 can join the description to step S110.
It shares and send module 112, it, will be corresponding with type of message different in the network equipment for being configured according to asynchronous message Step message according to each controller mark it is corresponding share weight respectively on give corresponding controller in controller cluster 20.
It in the present embodiment, shares and module 112 is sent to can be used for executing step S120 shown in Fig. 2, about sending mould on sharing The specific descriptions of block 112 can join the description to step S120.
Optionally, in the present embodiment, asynchronous message configuration further includes sending mode in message corresponding with type of message, is disappeared It includes sending on sending or broadcast in unicast that mode is sent on breath.
Share send module 112 be specifically used for sent in message mode be unicast on send when, will by the network equipment with disappear The corresponding asynchronous message of breath type according to share weight respectively on give corresponding controllers in controller cluster 20.
Fig. 9 is please referred to, it further includes sending module 113 in broadcast that device 110 is sent on asynchronous message.
Send module 113 for corresponding to and broadcasting the asynchronous message that send for type of message in broadcast, by the type of message Asynchronous message broadcasted in controller cluster 20.
In the present embodiment, request receiving module can be used for executing step S130 shown in Fig. 4, about request receiving module Specifically describe the description that can join to step S130.
Optionally, in the present embodiment, it shares and module 112 is sent to calculate separately each controller in asynchronous message configuration The corresponding ratio for sharing the sum of weight for sharing each controller in weight and controller cluster 20 is identified as the controller Identify it is corresponding share ratio, and by asynchronous message corresponding with type of message in the network equipment according to the mark of each controller It is corresponding share ratio and share give corresponding controller in controller cluster 20.
Optionally, in the present embodiment, including master controller and from controller in controller cluster 20, configuration receives mould Block 111, for obtaining asynchronous message configuration from master controller.
Referring once again to Fig. 9, it can also include sending module 114 in configuration that device 110 is sent on asynchronous message.
Send module 114 for when receiving the configuration acquisition request arbitrarily sent from controller, which to be set in configuration Standby asynchronous message configuration is sent to from controller.
Figure 10 is please referred to, Figure 10 is a kind of hardware structural diagram of controller provided in this embodiment.The controller can Including second processor 230 and the second machine readable storage medium 220.Second processor 230 and the second machine readable storage are situated between Matter 220 can be communicated via second system bus 240.Also, the second machine readable storage medium 220 is stored with the executable finger of machine It enables, it is executable by reading and executing machine corresponding with logic is sent on asynchronous message in the second machine readable storage medium 220 Delivery method on above-described asynchronous message can be performed in instruction, second processor 230.
Second machine readable storage medium 220 referred to herein can be any electronics, magnetism, optics or other physics Storage device may include or store information, such as executable instruction, data, etc..For example, machine readable storage medium can be with It is: RAM (Radom Access Memory, random access memory), volatile memory, nonvolatile memory, flash memory, deposits Store up driver (such as hard disk drive), solid state hard disk, any kind of storage dish (such as CD, dvd) or similar storage Medium or their combination.
Figure 11 is please referred to, the present embodiment also provides a kind of asynchronous message configuration device 210, asynchronous message configuration device 210 It can be stored in the functional module in the second machine readable storage medium 220 in a software form including at least one.Functionally draw Point, asynchronous message configuration device 210 may include configuration distributing module 211.
Configuration distributing module 211 is used to send asynchronous message configuration to the network equipment, and asynchronous message configuration includes message class Type, the mark of at least one controller and it is corresponding with the mark of each controller share weight so that the network equipment is according to different Message arrangement is walked, asynchronous message corresponding with type of message in the network equipment corresponding is shared according to the mark of each controller Weight respectively on give corresponding controller in controller cluster 20.
In conclusion the application asynchronous message configuration method provided in this embodiment, upper delivery method, controller and network are set It is standby, issued from controller to the network equipment carry type of message, controller mark and share weight asynchronous message configuration, The network equipment is shared according to the asynchronous message configuration received to be sent, so as to realize point of same type asynchronous message It is sent in load.
In embodiment provided herein, it should be understood that disclosed device and method, it can also be by other Mode realize.The apparatus embodiments described above are merely exemplary, for example, the flow chart and block diagram in attached drawing are shown According to device, the architectural framework in the cards of method and computer program product, function of multiple embodiments of the application And operation.In this regard, each box in flowchart or block diagram can represent one of a module, section or code Point, a part of the module, section or code includes one or more for implementing the specified logical function executable Instruction.It should also be noted that function marked in the box can also be attached to be different from some implementations as replacement The sequence marked in figure occurs.For example, two continuous boxes can actually be basically executed in parallel, they sometimes may be used To execute in the opposite order, this depends on the function involved.It is also noted that each of block diagram and or flow chart The combination of box in box and block diagram and or flow chart can be based on the defined function of execution or the dedicated of movement The system of hardware is realized, or can be realized using a combination of dedicated hardware and computer instructions.
In addition, each functional module in each embodiment of the application can integrate one independent portion of formation together Point, it is also possible to modules individualism, an independent part can also be integrated to form with two or more modules.
It, can be with if the function is realized and when sold or used as an independent product in the form of software function module It is stored in a computer readable storage medium.Based on this understanding, the technical solution of the application is substantially in other words The part of the part that contributes to existing technology or the technical solution can be embodied in the form of software products, the meter Calculation machine software product is stored in a storage medium, including some instructions are used so that a computer equipment (can be a People's computer, server or network equipment etc.) execute each embodiment the method for the application all or part of the steps. And storage medium above-mentioned includes: that USB flash disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), arbitrary access are deposited The various media that can store program code such as reservoir (RAM, Random Access Memory), magnetic or disk.
It should be noted that, in this document, relational terms such as first and second and the like are used merely to a reality Body or operation are distinguished with another entity or operation, are deposited without necessarily requiring or implying between these entities or operation In any actual relationship or order or sequence.Moreover, the terms "include", "comprise" or its any other variant are intended to Non-exclusive inclusion, so that the process, method, article or equipment including a series of elements is not only wanted including those Element, but also including other elements that are not explicitly listed, or further include for this process, method, article or equipment Intrinsic element.In the absence of more restrictions, the element limited by sentence "including a ...", it is not excluded that There is also other identical elements in process, method, article or equipment including the element.
The above, the only various embodiments of the application, but the protection scope of the application is not limited thereto, it is any Those familiar with the art within the technical scope of the present application, can easily think of the change or the replacement, and should all contain Lid is within the scope of protection of this application.Therefore, the protection scope of the application shall be subject to the protection scope of the claim.

Claims (10)

1. a kind of asynchronous message configuration method, which is characterized in that applied to the master controller in SDN framework controller cluster;Institute The method of stating includes:
The asynchronous message configuration of the network equipment is obtained, the asynchronous message configuration includes type of message, at least one described control The mark for the controller for including in device cluster and corresponding with the mark of controller share weight;
The asynchronous message configuration is sent to the network equipment, so that the network equipment is configured according to the asynchronous message, by this Asynchronous message corresponding with the type of message is distinguished according to the corresponding weight of sharing of mark of each controller in the network equipment On give corresponding controller included in asynchronous message configuration.
2. the method according to claim 1, wherein the step of the asynchronous message configuration for obtaining the network equipment Suddenly, comprising:
Obtain the corresponding different asynchronous message configuration of the different network equipments, wherein the control in the different asynchronous message The mark of device processed shares weighted.
3. the method according to claim 1, wherein the method also includes:
Detect the working condition in the controller cluster from controller;
When detecting the failure from controller, for the network equipment for sending asynchronous message on the slave controller to failure New asynchronous message configuration is issued, so as to receive the network equipment of the new asynchronous message configuration according to described new asynchronous Message arrangement will be sent on asynchronous message to the controller to normal work.
4. method according to claim 1-3, which is characterized in that asynchronous message configuration further include with it is described Mode is sent in the corresponding message of type of message, it includes sending on sending or broadcast in unicast that mode is sent in the message;
It is then, described to send the step of asynchronous message configures to the network equipment, comprising:
It carries the asynchronous message of mode is sent to configure in the message to network equipment transmission, make to receive the asynchronous message and match The type of message set is the network equipment sent in unicast, is configured, will be disappeared with described in the network equipment according to the asynchronous message The corresponding asynchronous message of breath type according to each controller mark it is corresponding share weight give in unicast respectively it is described asynchronous Included corresponding controller in message arrangement;Or make to send in the type of message broadcast for receiving the asynchronous message configuration The network equipment, according to the asynchronous message configure, asynchronous message corresponding with the type of message in the network equipment is existed It is broadcasted in the controller cluster.
5. delivery method on a kind of asynchronous message, which is characterized in that applied to the network equipment used in SDN framework, the method Include:
The asynchronous message configuration that controller cluster issues is received, the asynchronous message configuration includes type of message, at least one institute It states the mark for the controller for including in controller cluster and corresponding with the mark of controller shares weight;
It is configured according to the asynchronous message, by asynchronous message corresponding with the type of message in the network equipment according to each control Device processed identify it is corresponding share weight respectively on give corresponding controller included in asynchronous message configuration.
6. according to the method described in claim 5, it is characterized in that, asynchronous message configuration further includes and the type of message Mode is sent in corresponding message, it includes sending on sending or broadcast in unicast that mode is sent in the message;
It is described that asynchronous message corresponding with the type of message in the network equipment is corresponding according to the mark of each controller Share weight respectively on the step of giving corresponding controller in the controller cluster, comprising:
Correspond to the asynchronous message sent in unicast for the type of message, is configured according to the asynchronous message, which is set Asynchronous message corresponding with the type of message is distinguished in unicast according to the corresponding weight of sharing of mark of each controller in standby Give corresponding controller included in the asynchronous message configuration;
The method also includes:
Correspond to the asynchronous message sent in broadcast for the type of message, by the asynchronous message of the type of message in the control It is broadcasted in device cluster.
7. according to the method described in claim 5, it is characterized in that, described will be corresponding with the type of message in the network equipment Asynchronous message according to each controller mark it is corresponding share weight respectively on give in the controller cluster it is corresponding The step of controller, comprising:
Calculate separately each controller in asynchronous message configuration mark it is corresponding share it is each in weight and controller cluster The ratio for sharing the sum of weight of controller corresponding shares ratio as the mark of the controller;
By asynchronous message corresponding with the type of message in the network equipment according to the corresponding share ratio of mark of each controller Example, which is shared, gives corresponding controller in the controller cluster.
8. according to the described in any item methods of claim 5-7, which is characterized in that include master controller in the controller cluster It is described to receive the step of asynchronous message configuration that controller cluster issues and from controller, comprising:
The asynchronous message configuration is obtained from the master controller;
The method also includes:
When receiving the configuration acquisition request arbitrarily sent from controller, the asynchronous message configuration of the network equipment is sent to institute It states from controller.
9. a kind of controller, which is characterized in that including machine readable storage medium and processor, the machine readable storage medium It is stored with machine-executable instruction, the machine-executable instruction promotes the control when being called or being executed by the processor Device realizes method described in claim 1-4 any one.
10. a kind of network equipment, which is characterized in that including machine readable storage medium and processor, the machine readable storage Media storage has machine-executable instruction, and the machine-executable instruction promotes described when being called or being executed by the processor The network equipment realizes method described in claim 5-8 any one.
CN201811562607.3A 2018-12-20 2018-12-20 Asynchronous message configuration method, uploading method, controller and network equipment Active CN109450709B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201811562607.3A CN109450709B (en) 2018-12-20 2018-12-20 Asynchronous message configuration method, uploading method, controller and network equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201811562607.3A CN109450709B (en) 2018-12-20 2018-12-20 Asynchronous message configuration method, uploading method, controller and network equipment

Publications (2)

Publication Number Publication Date
CN109450709A true CN109450709A (en) 2019-03-08
CN109450709B CN109450709B (en) 2022-02-11

Family

ID=65560206

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201811562607.3A Active CN109450709B (en) 2018-12-20 2018-12-20 Asynchronous message configuration method, uploading method, controller and network equipment

Country Status (1)

Country Link
CN (1) CN109450709B (en)

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103873361A (en) * 2014-03-04 2014-06-18 杭州华三通信技术有限公司 Packet transmitting device and method
CN104734957A (en) * 2013-12-24 2015-06-24 中国移动通信集团公司 Service transmission method and device in software defined network (SDN)
WO2015187119A1 (en) * 2014-06-02 2015-12-10 Hewlett-Packard Development Company, L.P. Delivering messages according to a desired delivery order in a software defined network
CN105591963A (en) * 2015-08-27 2016-05-18 杭州华三通信技术有限公司 Message forwarding method and equipment in SDN
CN105763606A (en) * 2016-02-04 2016-07-13 杭州华三通信技术有限公司 Service chain agent aggregation method and system
US20160294682A1 (en) * 2013-11-14 2016-10-06 Zte Corporation Data flow Distribution Method and Controller
CN106656846A (en) * 2017-01-17 2017-05-10 大连理工大学 Construction method of coordination layer in software defined network (SDN) architecture
CN107070714A (en) * 2017-04-10 2017-08-18 中国人民解放军国防科学技术大学 A kind of SDN abnormality monitoring method
CN104429028B (en) * 2013-05-06 2018-01-12 华为技术有限公司 Network collocating method, apparatus and system based on SDN

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104429028B (en) * 2013-05-06 2018-01-12 华为技术有限公司 Network collocating method, apparatus and system based on SDN
US20160294682A1 (en) * 2013-11-14 2016-10-06 Zte Corporation Data flow Distribution Method and Controller
CN104734957A (en) * 2013-12-24 2015-06-24 中国移动通信集团公司 Service transmission method and device in software defined network (SDN)
CN103873361A (en) * 2014-03-04 2014-06-18 杭州华三通信技术有限公司 Packet transmitting device and method
WO2015187119A1 (en) * 2014-06-02 2015-12-10 Hewlett-Packard Development Company, L.P. Delivering messages according to a desired delivery order in a software defined network
CN105591963A (en) * 2015-08-27 2016-05-18 杭州华三通信技术有限公司 Message forwarding method and equipment in SDN
CN105763606A (en) * 2016-02-04 2016-07-13 杭州华三通信技术有限公司 Service chain agent aggregation method and system
CN106656846A (en) * 2017-01-17 2017-05-10 大连理工大学 Construction method of coordination layer in software defined network (SDN) architecture
CN107070714A (en) * 2017-04-10 2017-08-18 中国人民解放军国防科学技术大学 A kind of SDN abnormality monitoring method

Also Published As

Publication number Publication date
CN109450709B (en) 2022-02-11

Similar Documents

Publication Publication Date Title
CN105376083B (en) Energy-saving control method, management server and the network equipment
EP2493118B1 (en) Information processing system
US7594007B2 (en) Distributed service management for distributed networks
CN103053146B (en) Data migration method and device
CN103403683A (en) Capabilities based routing of virtual data center service request
CN103475722A (en) Implement system for business collaboration platform
US20190205145A1 (en) Robot task management method, robot using the same and computer readable storage medium
CN103929368A (en) Load balance method and device for multiple service units
CN1929494B (en) Distributed electronic program guidance system
CN105900068B (en) The systems, devices and methods of path management
WO2015105502A1 (en) Call home cluster
CN104660689B (en) Distributed computing system
CN110198346A (en) Method for reading data, device, electronic equipment and readable storage medium storing program for executing
CN107682411A (en) A kind of extensive SDN controllers cluster and network system
CN116016584A (en) Equipment data transfer method, equipment and medium based on Internet of things platform
CN1330124C (en) Method and apparatus for virtualizing network resources
CN107229425A (en) A kind of date storage method and device
CN109542627A (en) Node switching method, device, supervisor, node device and distributed system
CN114827171B (en) Information synchronization method, apparatus, computer device and storage medium
CN109733444B (en) Database system and train monitoring management equipment
CN105429823B (en) Flux of multicast detection method and device in distributed communication equipment
US20090259740A1 (en) Managing overlapping address spaces
CN109450709A (en) Asynchronous message configuration method, upper delivery method, controller and the network equipment
CN106330492A (en) Method, device and system of configuring user equipment forwarding table
CN104349172B (en) The cluster management method and its device of Internet video storage device

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
TR01 Transfer of patent right

Effective date of registration: 20230629

Address after: 310052 11th Floor, 466 Changhe Road, Binjiang District, Hangzhou City, Zhejiang Province

Patentee after: H3C INFORMATION TECHNOLOGY Co.,Ltd.

Address before: 310052 Changhe Road, Binjiang District, Hangzhou, Zhejiang Province, No. 466

Patentee before: NEW H3C TECHNOLOGIES Co.,Ltd.

TR01 Transfer of patent right