CN104079494B - A kind of transmission method and equipment of Echo Request messages - Google Patents
A kind of transmission method and equipment of Echo Request messages Download PDFInfo
- Publication number
- CN104079494B CN104079494B CN201410331649.1A CN201410331649A CN104079494B CN 104079494 B CN104079494 B CN 104079494B CN 201410331649 A CN201410331649 A CN 201410331649A CN 104079494 B CN104079494 B CN 104079494B
- Authority
- CN
- China
- Prior art keywords
- controller
- keep
- alive
- network equipment
- chained list
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Abstract
The invention discloses a kind of transmission method and equipment of Echo Request messages, this method includes：The network equipment is that each controller generates a keep-alive chained list；The network equipment determines keep-alive chained list corresponding to the example when needing to send Echo Request messages for example, and judges whether the example is given instance on the keep-alive chained list；If it is not, then the network equipment is refused to send Echo Request messages to controller；If it is, the network equipment sends Echo Request messages to controller, and the Echo Reply messages for waiting controller to be received to return.In the embodiment of the present invention, it is possible to reduce the quantity for the Echo Request messages that the network equipment is sent, save the process resource of the network equipment, and the quantity of the Echo Reply messages of controller transmission can be reduced, save the process resource of controller.
Description
Technical field
The present invention relates to the communications field, the especially a kind of transmission method and equipment of Echo Request messages.
Background technology
OpenFlow is one defined in SDN (Software Defined Network, software defined network) framework
Communication interface standard between controller and forwarding.OpenFlow thought is to separate control plane and datum plane, the two
Between use standard protocol communication.In OpenFlow networks, including the network equipment is (such as：OpenFlow interchangers) and control
Device is (such as：OpenFlow controllers), and pass through OpenFlow tunneling traffics between the network equipment and controller.Wherein, controller
For the protocol generation flow table of the configuration according to user or dynamic operation (Flow Table), and flow table is sent to network and set
It is standby.The network equipment is used to receive the flow table from controller, and matches and handle message according to flow table.
In the prior art, the network equipment is established after connection with controller, it is necessary to periodically send Echo to controller
Request messages, Echo Reply messages are returned to the network equipment after Echo Request messages are received from controller.Enter one
Step, example is divided usually using VLAN (Virtual Local Area Network, VLAN) on the network equipment,
Each example is individually and controller establishes connection, because the VLAN number that the network equipment is supported at present is 4094, because
This network equipment can support 4094 examples.If each example and controller establish connection (different instances can and phase
Same controller establishes connection, can also establish connection with different controllers), then the network equipment can establish 4094 connections.
On this basis, it is assumed that 4094 examples all establish connection with same controller, then the network equipment is in each hair
Send in the cycle (default value 5 seconds), be required to send 4094 Echo Request messages to controller, and controller is needed to net
Network equipment returns to 4094 Echo Reply messages.Obviously, sending in the cycle, the network equipment needs to send substantial amounts of Echo
Request messages, so as to waste the process resource of the network equipment, and influence the normal use of the network equipment；Further, control
Device is also required to send substantial amounts of Echo Reply messages, so as to waste the process resource of controller, and influences the normal of controller
Use.
The content of the invention
The embodiment of the present invention provides a kind of transmission method of loopback request Echo Request messages, applied to including network
In the OpenFlow networks of equipment and controller, it the described method comprises the following steps：
The network equipment is that each controller generates a keep-alive chained list, is remembered in keep-alive chained list corresponding to the controller
The example for establishing connection on the network equipment with the controller is recorded；
The network equipment determines keep-alive corresponding to the example when needing to send Echo Request messages for example
Chained list, and judge whether the example is given instance on the keep-alive chained list；
If it is not, then the network equipment is refused to send Echo Request to the controller for establishing connection with the example
Message；If it is, the network equipment sends Echo Request messages to the controller that connection is established with the example, and
The loopback response Echo Reply messages returned etc. controller to be received.
The network equipment is the process that each controller generates a keep-alive chained list, is specifically included：
For each example on the network equipment, after example and controller establish connection, the network equipment judges to work as
It is preceding to whether there is keep-alive chained list corresponding to the controller；Protected if not, the network equipment creates corresponding to the controller
Chained list living, and the example is added in keep-alive chained list corresponding to the controller；If it is, the network equipment is in the control
The example is added in keep-alive chained list corresponding to device processed.
The network equipment judge the example whether be given instance on the keep-alive chained list process, specific bag
Include：The network equipment judges whether the example is first example recorded in the keep-alive chained list；It is if it is, described
The network equipment determines that the example is the given instance on the keep-alive chained list；If it is not, then described in the network equipment determination
Example is not the given instance on the keep-alive chained list.
After the network equipment sends Echo Request messages to the controller that connection is established with the example, bag
Include：If the network equipment receives the Echo Reply messages of controller return in preset time, the control is kept
The connection of each example recorded in keep-alive chained list corresponding to device and the controller；If the network equipment is in preset time
The Echo Reply messages of controller return, the then each example that will be recorded in keep-alive chained list corresponding to the controller are not received
Connection with the controller disconnects.
Methods described further comprises：
If example is the given instance on keep-alive chained list, as the Echo that controller return is received in preset time
During Reply messages, the network equipment resets keepalive timer corresponding to the example；When not receiving control in preset time
During the Echo Reply messages that device processed returns, after keepalive timer corresponding to the example reaches time-out time, the network
Equipment disconnects the connection of the example and the controller；
If example is not the given instance on keep-alive chained list, the network equipment utilizes the finger on the keep-alive chained list
Determine the value of keepalive timer corresponding to example, update the value of keepalive timer corresponding to the example；When corresponding to the example
When keepalive timer does not reach time-out time, the network equipment keeps the connection of the example and the controller；When described
After keepalive timer corresponding to example reaches time-out time, the network equipment is by the connection of the example and the controller
Disconnect.
Methods described further comprises：When the network equipment deletes the example in present networks equipment, the network is set
It is standby to delete the example from corresponding keep-alive chained list；And/or when the connection of example and controller disconnects, the network is set
It is standby that the example is deleted from keep-alive chained list corresponding to the controller.
The embodiment of the present invention provides a kind of network equipment, applied to the OpenFlow for including the network equipment and controller
In network, the network equipment specifically includes：
Generation module, for generating a keep-alive chained list for each controller, in keep-alive chained list corresponding to the controller
It has recorded the example for establishing connection on the network equipment with the controller；
Judge module, for when needing to send Echo Request messages for example, determining to protect corresponding to the example
Chained list living, and judge whether the example is given instance on the keep-alive chained list；
Processing module, for when judged result is is not the given instance on the keep-alive chained list, refuse to it is described
The controller that example establishes connection sends loopback request Echo Request messages；It is on the keep-alive chained list to be in judged result
Given instance when, send Echo Request messages to the controller that connection is established with the example, and wait control to be received
The loopback response Echo Reply messages that device returns.
The generation module, specifically for for each example on the network equipment, being established in example and controller
After connection, judgement currently whether there is keep-alive chained list corresponding to the controller；If it is not, then it is corresponding to create the controller
Keep-alive chained list, and the example is added in keep-alive chained list corresponding to the controller；If it is, in the controller pair
The example is added in the keep-alive chained list answered.
The judge module, specifically for judging whether the example is first reality being recorded in the keep-alive chained list
Example；If it is, determine that the example is the given instance on the keep-alive chained list；If it is not, then determine that the example is not
Given instance on the keep-alive chained list.
The processing module, it is additionally operable to sending Echo Request messages to the controller for establishing connection with the example
Afterwards, if receiving the Echo Reply messages that the controller returns in preset time, keep the controller corresponding
Keep-alive chained list in each example for recording and the controller connection；If do not receive the controller in preset time to return
The Echo Reply messages returned, then by the company of each example recorded in keep-alive chained list corresponding to the controller and the controller
Connect disconnection.
The processing module, if it is the given instance on keep-alive chained list to be further used for example, when in preset time
When receiving the Echo Reply messages of controller return, keepalive timer corresponding to the example is reset；When in preset time
When not receiving the Echo Reply messages of controller return inside, when keepalive timer corresponding to the example reaches time-out time
Afterwards, the connection of the example and controller is disconnected；If example is not the given instance on keep-alive chained list, the keep-alive is utilized
The value of keepalive timer corresponding to given instance on chained list, update the value of keepalive timer corresponding to the example；When described
When keepalive timer corresponding to example does not reach time-out time, the connection of the example and the controller is kept；When the reality
After keepalive timer reaches time-out time corresponding to example, the connection of the example and controller is disconnected.
The processing module, it is additionally operable to when deleting the example on the network equipment, from keep-alive corresponding to the example
The example is deleted in chained list；And/or when the connection of example and controller disconnects, from keep-alive chain corresponding to the controller
The example is deleted in table.
Based on above-mentioned technical proposal, in the embodiment of the present invention, by sending Echo for the given instance on keep-alive chained list
Request messages, and refuse to send Echo Request messages for the non-designated example on keep-alive chained list, set so as to reduce network
The quantity for the Echo Request messages that preparation is sent, saves the process resource of the network equipment, and can reduce controller transmission
Echo Reply messages quantity, save the process resource of controller.Further, aforesaid way can reduce the network equipment
With the loss of the processing keep Alive Packet ability of controller, the performance impact to E-Packet is reduced, enhancing OpenFlow functions
Stability.
Brief description of the drawings
Fig. 1 is the application scenarios schematic diagram of the embodiment of the present invention；
Fig. 2 is a kind of transmission method flow chart of Echo Request messages provided in an embodiment of the present invention；
Fig. 3 is a kind of structural representation of network equipment provided in an embodiment of the present invention.
Embodiment
For problems of the prior art, the embodiment of the present invention provides a kind of transmission side of Echo Request messages
Method, this method can apply to including the network equipment (such as OpenFlow interchangers) and controller (such as OpenFlow controllers)
In OpenFlow networks.Application scenarios schematic diagram using Fig. 1 as the embodiment of the present invention, on network devices by using 4000
VLAN, to divide 4000 examples on network devices, wherein, example 1- examples 1000 are established with controller 1 and connected, example
1001- examples 2000 are established with controller 2 and connected, and example 2001- examples 4000 are established with controller 3 and connected.
Under above-mentioned application scenarios, as shown in Fig. 2 this method may comprise steps of：
Step 201, the network equipment is that each controller generates a keep-alive chained list；Wherein, keep-alive corresponding to the controller
The example for establishing connection in present networks equipment with the controller is have recorded in chained list.
For example, the network equipment, which is controller 1, generates a keep-alive chained list 1, and the network equipment is have recorded in the keep-alive chained list 1
Upper and controller 1 establishes the example 1- examples 1000 of connection.The network equipment is that controller 2 generates a keep-alive chained list 2, and the guarantor
The example 1001- examples 2000 for establishing connection on the network equipment with controller 2 are have recorded in chained list 2 living.The network equipment is control
Device 3 generates a keep-alive chained list 3, and the example for establishing connection on the network equipment with controller 3 is have recorded in the keep-alive chained list 3
2001- examples 4000.
In the embodiment of the present invention, the network equipment be each controller generate a keep-alive chained list process, specifically include but
It is not limited to following manner：For each example on the network equipment, after example and controller establish connection, the network equipment
Judgement currently whether there is keep-alive chained list corresponding to the controller；Protected if it is not, then the network equipment creates corresponding to the controller
Chained list living, and the example is added in keep-alive chained list corresponding to the controller；If it is, the network equipment is corresponding in the controller
Keep-alive chained list in add example.
For example, after example 1 and controller 1 establish connection, it is assumed that there is currently no keep-alive chain corresponding to controller 1
Table, then the network equipment is needed to create keep-alive chained list 1 corresponding to controller 1, and example 1 is added in keep-alive chained list 1.In example 2
After establishing connection with controller 1, due to being presently in existence keep-alive chained list 1 corresponding to controller 1, therefore the network equipment can be with
Example 2 is added directly in keep-alive chained list 1.By that analogy, for the processing of other examples, in the embodiment of the present invention no longer in detail
Repeat.
Step 202, the network equipment determines to protect corresponding to the example when needing to send Echo Request messages for example
Chained list living, and judge whether the example is given instance on the keep-alive chained list.If it is not, then the network equipment performs step 203,
If it is, the network equipment performs step 204.
, it is necessary to periodically send Echo Request messages to controller after the network equipment connects with controller foundation,
By controller after Echo Request messages are received, Echo Reply messages are returned to the network equipment.On network devices
Example and controller are established after connection, the network equipment in each transmission cycle (default value 5 seconds), be required to for example to
Controller sends Echo Request messages.Based on this, in the embodiment of the present invention, for each example, the network equipment is needing
When sending Echo Request messages for example, keep-alive chained list corresponding to the example is determined, and judge whether the example is the guarantor
Given instance on chained list living.If it is not, then step 203 is performed, if it is, performing step 204.
In the embodiment of the present invention, given instance can be first example recorded on keep-alive chained list.Based on this, network is set
It is standby judge example whether be given instance on keep-alive chained list process, be specifically including but not limited to：Needing to send for example
During Echo Request messages, the network equipment judges whether the example is first example recorded in keep-alive chained list；If it is,
Then the network equipment determines that the example is the given instance on keep-alive chained list；If it is not, then the network equipment determines that the example is not to protect
Given instance on chained list living.
As shown in figure 1, have recorded example 1- examples 1000 in keep-alive chained list 1, example 1 is the recorded in keep-alive chained list 1
One example, example 1001- examples 2000 are have recorded in keep-alive chained list 2, and example 1001 is first recorded in keep-alive chained list 2
Individual example, example 2001- examples 4000 are have recorded in keep-alive chained list 3, and example 2001 is first reality recorded in keep-alive chained list 3
Example.On this basis, the network equipment determines keep-alive corresponding to example 1 when needing to send Echo Request messages for example 1
Chained list is keep-alive chained list 1, and example 1 is first example recorded in keep-alive chained list 1, performs step 204；The network equipment is needing
When being that example 2 sends Echo Request messages, it is keep-alive chained list 1 to determine keep-alive chained list corresponding to example 2, and example 2 is not
It is first example recorded in keep-alive chained list 1, performs step 203.By that analogy, for the processing of other examples, with example 1
Or the processing of example 2 is similar, no longer repeats in detail herein.
Step 203, the network equipment is refused to send Echo Request messages to the controller for establishing connection with example.Example
Such as, the network equipment is not after it is determined that example 2 is first example recorded in keep-alive chained list 1, refuses to connect to establishing with example 2
The controller 1 connect sends Echo Request messages.
Step 204, the network equipment sends Echo Request messages to the controller that connection is established with example, and waits waiting
The Echo Reply messages that admission controller returns.For example, the network equipment it is determined that example 1 be record in keep-alive chained list 1 first
After individual example, Echo Request messages are sent to the controller 1 that connection is established with example 1, and wait controller 1 to be received to return
The Echo Reply messages returned.
In the embodiment of the present invention, for the example 1- examples 1000 recorded in keep-alive chained list 1, for example 1, the network equipment
Echo Request messages are sent to the controller 1 that connection is established with example 1, for example 2- examples 1000, the network equipment is refused
Absolutely Echo Request messages are sent to the controller 1 that connection is established with example 2- examples 1000.For being recorded in keep-alive chained list 2
Example 1001- examples 2000, for example 1001, the network equipment to example 1001 establish connection controller 2 send
Echo Request messages, for example 1002- examples 2000, the network equipment is refused to establish to example 1002- examples 2000
The controller 2 of connection sends Echo Request messages.For the example 2001- examples 4000 recorded in keep-alive chained list 3, for
Example 2001, the network equipment sends Echo Request messages to the controller 3 that connection is established with example 2001, for example
2002- examples 4000, the network equipment are refused to send Echo to the controller 3 for establishing connection with example 2002- examples 4000
Request messages.Based on above-mentioned technical proposal, it is possible to reduce the quantity for the Echo Request messages that the network equipment is sent, section
The about process resource of the network equipment, and the quantity of the Echo Reply messages of controller transmission can be reduced, save controller
Process resource.Further, aforesaid way can reduce the loss of the processing keep Alive Packet ability of the network equipment and controller,
The performance impact to E-Packet is reduced, strengthens the stability of OpenFlow functions.
In the embodiment of the present invention, the transmission cycle of each example is subjected to unification on the network equipment, in each transmission cycle
In (default value 5 seconds), the network equipment needs to be directed to each Query By Example keep-alive chained list, to judge whether the example is keep-alive chained list
On given instance, i.e., it is each transmission the cycle in, the network equipment need for each example send Echo Request messages, after
And need to judge whether each example is given instance on keep-alive chained list.Further, if it is, the network equipment confirms in fact
Example is given instance, if it is not, then the network equipment confirms that example is non-given instance.Further, if example is given instance,
Then the network equipment needs to send Echo Request messages to the controller for establishing connection with the given instance, and waits control to be received
The Echo Reply messages that device processed returns.If example is non-designated example, the network equipment is refused to build to the non-designated example
The controller of vertical connection sends Echo Request messages.
In the embodiment of the present invention, the network equipment sends Echo Request messages to the controller that connection is established with example,
And after waiting the Echo Reply messages that controller to be received returns, it can also comprise the following steps：
Step 205, if the network equipment have received the Echo Reply messages of controller return in preset time, need
Keep the connection of each example and controller recorded in keep-alive chained list corresponding to the controller；If the network equipment is default
The Echo Reply messages of controller return are not received in time, then need to record in keep-alive chained list corresponding to the controller
The connection of each example and the controller disconnects.
As shown in figure 1, the network equipment to the controller 1 that connection is established with example 1 send Echo Request messages it
Afterwards, if the network equipment have received the Echo Reply messages of the return of controller 1 in preset time, the network equipment needs to protect
The connection of each example (i.e. example 1- examples 1000) recorded in keep-alive chained list 1 corresponding to held controller 1 and controller 1；In addition,
If the network equipment does not receive the Echo Reply messages of the return of controller 1 in preset time, the network equipment needs will control
The connection of each example (i.e. example 1- examples 1000) recorded in keep-alive chained list 1 corresponding to device 1 processed and controller 1 disconnects.
In the embodiment of the present invention, for each example：If example is the given instance on keep-alive chained list, when
When the Echo Reply messages of controller return are received in preset time (such as 3* send cycle=15s), the network equipment is by the reality
Keepalive timer corresponding to example (its time-out time such as 3* sends cycle=15s) is reset；When not receiving control in preset time
During the Echo Reply messages that device returns, after keepalive timer corresponding to example reaches time-out time, the network equipment is by example
Connection with controller disconnects.If example is not the given instance on keep-alive chained list, the network equipment is using on keep-alive chained list
Given instance corresponding to keepalive timer value, update the value of keepalive timer corresponding to the example；As guarantor corresponding to example
When active timer does not reach time-out time, the network equipment keeps the connection of example and controller；When keep-alive timing corresponding to example
After device reaches time-out time, the network equipment disconnects the connection of example and controller.
In the embodiment of the present invention, when the network equipment delete present networks equipment on example when, the network equipment also need to from
The example is deleted in corresponding keep-alive chained list.For example, when the network equipment deletes the example 1 in present networks equipment, the network is set
Standby to also need to delete the example 1 from keep-alive chained list 1 corresponding to example 1, first example now recorded in keep-alive chained list 1 is more
New is example 2；In another example when the network equipment deletes the example 5 in present networks equipment, the network equipment is also needed to from example 5
The example 5 is deleted in corresponding keep-alive chained list 1, first example now recorded in keep-alive chained list 1 remains as example 1.
In the embodiment of the present invention, when the connection of example and controller disconnects, the network equipment is also needed to from the controller pair
The example is deleted in the keep-alive chained list answered.For example, when the connection of example 1- examples 1000 and controller 1 disconnects, the network equipment
Need to delete example 1- examples 1000 from keep-alive chained list 1 corresponding to controller 1, i.e., all examples deleted from keep-alive chained list 1,
And it can further delete keep-alive chained list 1.
Example and controller connection disconnect after, when example and controller connection recover, i.e., example again with control
Device processed is established after connection, then re-executes above-mentioned steps 201- steps 205.I.e.：The network equipment is again controller generation one
Individual keep-alive chained list, when needing to send Echo Request messages for example, keep-alive chained list corresponding to the example is determined, and judge
Whether the example is given instance on the keep-alive chained list.If not, the network equipment is refused to the control that connection is established with example
Device sends Echo Request messages；If it is, the network equipment sends Echo to the controller that connection is established with example
Request messages, and the Echo Reply messages for waiting controller to be received to return.If controller is have received in preset time
The Echo Reply messages of return, then need to keep each example and the control recorded in keep-alive chained list corresponding to the controller
The connection of device；If not receiving the Echo Reply messages of controller return in preset time, need the controller pair
The connection of each example recorded in the keep-alive chained list answered and the controller disconnects.
Based on the inventive concept same with the above method, a kind of network equipment is additionally provided in the embodiment of the present invention, is applied
In the OpenFlow networks including the network equipment and controller, as shown in figure 3, the network equipment specifically includes：
Generation module 11, for generating a keep-alive chained list, keep-alive chained list corresponding to the controller for each controller
In have recorded on the network equipment with the controller establish connection example；
Judge module 12, for when needing to send Echo Request messages for example, determining corresponding to the example
Keep-alive chained list, and judge whether the example is given instance on the keep-alive chained list；
Processing module 13, for when judged result is is not the given instance on the keep-alive chained list, refuse to institute
State the controller transmission loopback request Echo Request messages that example establishes connection；It is the keep-alive chained list to be in judged result
On given instance when, send Echo Request messages to the controller that connection is established with the example, and wait control to be received
The loopback response Echo Reply messages that device processed returns.
The generation module 11, specifically for for each example on the network equipment, being built in example and controller
After vertical connection, judgement currently whether there is keep-alive chained list corresponding to the controller；If it is not, then create the controller pair
The keep-alive chained list answered, and the example is added in keep-alive chained list corresponding to the controller；If it is, in the controller
The example is added in corresponding keep-alive chained list.
The judge module 12, specifically for judging whether the example is first reality being recorded in the keep-alive chained list
Example；If it is, determine that the example is the given instance on the keep-alive chained list；If it is not, then determine that the example is not
Given instance on the keep-alive chained list.
The processing module 13, it is additionally operable to sending Echo Request reports to the controller for establishing connection with the example
After text, if receiving the Echo Reply messages that the controller returns in preset time, the controller pair is kept
The connection of each example recorded in the keep-alive chained list answered and the controller；If the controller is not received in preset time
The Echo Reply messages of return, then by each example recorded in keep-alive chained list corresponding to the controller and the controller
Connection disconnect.
The processing module 13, if it is the given instance on keep-alive chained list to be further used for example, when in preset time
When inside receiving the Echo Reply messages of controller return, keepalive timer corresponding to the example is reset；When default
In do not receive controller return Echo Reply messages when, when corresponding to the example keepalive timer reach time-out time
Afterwards, the connection of the example and controller is disconnected；If example is not the given instance on keep-alive chained list, the keep-alive is utilized
The value of keepalive timer corresponding to given instance on chained list, update the value of keepalive timer corresponding to the example；When described
When keepalive timer corresponding to example does not reach time-out time, the connection of the example and the controller is kept；When the reality
After keepalive timer reaches time-out time corresponding to example, the connection of the example and controller is disconnected.
The processing module 13, it is additionally operable to when deleting the example on the network equipment, from guarantor corresponding to the example
The example is deleted in chained list living；And/or when the connection of example and controller disconnects, from keep-alive corresponding to the controller
The example is deleted in chained list.
Wherein, the modules of apparatus of the present invention can be integrated in one, and can also be deployed separately.Above-mentioned module can close
And be a module, multiple submodule can also be further split into.
Through the above description of the embodiments, those skilled in the art can be understood that the present invention can be by
Software adds the mode of required general hardware platform to realize, naturally it is also possible to which by hardware, but the former is more in many cases
Good embodiment.Based on such understanding, what technical scheme substantially contributed to prior art in other words
Part can be embodied in the form of software product, and the computer software product is stored in a storage medium, if including
It is dry to instruct to cause a computer equipment (be personal computer, server, or network equipment etc.) to perform this hair
Method described in bright each embodiment.It will be appreciated by those skilled in the art that accompanying drawing is the schematic diagram of a preferred embodiment,
Module or flow in accompanying drawing are not necessarily implemented necessary to the present invention.It will be appreciated by those skilled in the art that in embodiment
Device in module can according to embodiment describe be distributed in the device of embodiment, respective change position can also be carried out
In one or more devices different from the present embodiment.The module of above-described embodiment can be merged into a module, can also
It is further split into multiple submodule.The embodiments of the present invention are for illustration only, do not represent the quality of embodiment.
Disclosed above is only several specific embodiments of the present invention, and still, the present invention is not limited to this, the technology of any this area
What personnel can think change should all fall into protection scope of the present invention.
Claims (10)
1. a kind of transmission method of loopback request Echo Request messages, applied to including the network equipment and controller
In OpenFlow networks, it is characterised in that the described method comprises the following steps：
The network equipment is that each controller generates a keep-alive chained list, be have recorded in keep-alive chained list corresponding to the controller
The example of connection is established on the network equipment with the controller；
The network equipment determines keep-alive chain corresponding to the example when needing to send Echo Request messages for example
Table, and judge whether the example is given instance on the keep-alive chained list；
If it is not, then the network equipment is refused to send Echo Request reports to the controller for establishing connection with the example
Text；If it is, the network equipment sends Echo Request messages to the controller that connection is established with the example, and wait
The loopback response Echo Reply messages that admission controller waiting returns；
If the network equipment receives the Echo Reply messages of controller return in preset time, the control is kept
The connection of each example recorded in keep-alive chained list corresponding to device and the controller；If the network equipment is in preset time
Do not receive controller return Echo Reply messages, then by each example recorded in keep-alive chained list corresponding to the controller with
The connection of the controller disconnects.
2. the method as described in claim 1, it is characterised in that the network equipment is that each controller generates a keep-alive chain
The process of table, is specifically included：
For each example on the network equipment, after example and controller establish connection, the network equipment judgement is currently
It is no keep-alive chained list corresponding to the controller to be present；If not, the network equipment creates keep-alive chain corresponding to the controller
Table, and the example is added in keep-alive chained list corresponding to the controller；If it is, the network equipment is in the controller
The example is added in corresponding keep-alive chained list.
3. the method as described in claim 1, it is characterised in that the network equipment judges whether the example is the keep-alive
The process of given instance on chained list, is specifically included：
The network equipment judges whether the example is first example recorded in the keep-alive chained list；If it is, institute
State the network equipment and determine that the example is the given instance on the keep-alive chained list；If it is not, then the network equipment determines institute
It is not the given instance on the keep-alive chained list to state example.
4. the method as described in claim 1, it is characterised in that methods described further comprises：
If example is the given instance on keep-alive chained list, when the Echo Reply reports that controller return is received in preset time
Wen Shi, the network equipment reset keepalive timer corresponding to the example；Returned when not receiving controller in preset time
During the Echo Reply messages returned, after keepalive timer corresponding to the example reaches time-out time, the network equipment will
The connection of the example and the controller disconnects；
If example is not the given instance on keep-alive chained list, the network equipment utilizes the specified reality on the keep-alive chained list
The value of keepalive timer corresponding to example, update the value of keepalive timer corresponding to the example；When keep-alive corresponding to the example
When timer does not reach time-out time, the network equipment keeps the connection of the example and the controller；When the example
After corresponding keepalive timer reaches time-out time, the network equipment breaks the connection of the example and the controller
Open.
5. the method as described in claim 1, it is characterised in that methods described further comprises：
When the network equipment deletes the example in present networks equipment, the network equipment is deleted from corresponding keep-alive chained list
The example；And/or when the connection of example and controller disconnects, keep-alive corresponding to the network equipment from the controller
The example is deleted in chained list.
A kind of 6. network equipment, applied in the OpenFlow networks including the network equipment and controller, it is characterised in that
The network equipment specifically includes：
Generation module, for generating a keep-alive chained list for each controller, recorded in keep-alive chained list corresponding to the controller
The example of connection is established on the network equipment with the controller；
Judge module, for when needing to send Echo Request messages for example, determining keep-alive chain corresponding to the example
Table, and judge whether the example is given instance on the keep-alive chained list；
Processing module, for when judged result is is not the given instance on the keep-alive chained list, refuse to the example
The controller for establishing connection sends loopback request Echo Request messages；It is finger on the keep-alive chained list to be in judged result
When determining example, Echo Request messages are sent to the controller that connection is established with the example, and wait controller to be received to return
The loopback response Echo Reply messages returned；
The processing module, be additionally operable to the controller that connection is established with the example send Echo Request messages it
Afterwards, if receiving the Echo Reply messages that the controller returns in preset time, keep corresponding to the controller
The connection of each example recorded in keep-alive chained list and the controller；If do not receive the controller in preset time to return
Echo Reply messages, then by the connection of each example recorded in keep-alive chained list corresponding to the controller and the controller
Disconnect.
7. the network equipment as claimed in claim 6, it is characterised in that
The generation module, specifically for for each example on the network equipment, establishing and connecting in example and controller
Afterwards, judge currently to whether there is keep-alive chained list corresponding to the controller；Protected if it is not, then creating corresponding to the controller
Chained list living, and the example is added in keep-alive chained list corresponding to the controller；If it is, corresponding to the controller
The example is added in keep-alive chained list.
8. the network equipment as claimed in claim 6, it is characterised in that
The judge module, specifically for judging whether the example is first example being recorded in the keep-alive chained list；Such as
Fruit is, it is determined that the example is the given instance on the keep-alive chained list；If it is not, then determine that the example is not the guarantor
Given instance on chained list living.
9. the network equipment as claimed in claim 6, it is characterised in that
The processing module, if it is the given instance on keep-alive chained list to be further used for example, when being received in preset time
During the Echo Reply messages that controller returns, keepalive timer corresponding to the example is reset；When in preset time not
, will after keepalive timer corresponding to the example reaches time-out time when receiving the Echo Reply messages of controller return
The connection of the example and controller disconnects；If example is not the given instance on keep-alive chained list, the keep-alive chained list is utilized
On given instance corresponding to keepalive timer value, update the value of keepalive timer corresponding to the example；When the example
When corresponding keepalive timer does not reach time-out time, the connection of the example and the controller is kept；When the example pair
After the keepalive timer answered reaches time-out time, the connection of the example and controller is disconnected.
10. the network equipment as claimed in claim 6, it is characterised in that
The processing module, it is additionally operable to when deleting the example on the network equipment, from keep-alive chained list corresponding to the example
It is middle to delete the example；And/or when the connection of example and controller disconnects, from keep-alive chained list corresponding to the controller
Delete the example.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410331649.1A CN104079494B (en) | 2014-07-11 | 2014-07-11 | A kind of transmission method and equipment of Echo Request messages |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410331649.1A CN104079494B (en) | 2014-07-11 | 2014-07-11 | A kind of transmission method and equipment of Echo Request messages |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104079494A CN104079494A (en) | 2014-10-01 |
| CN104079494B true CN104079494B (en) | 2018-01-16 |
Family
ID=51600546
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410331649.1A Active CN104079494B (en) | 2014-07-11 | 2014-07-11 | A kind of transmission method and equipment of Echo Request messages |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104079494B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5870540A (en) * | 1995-11-20 | 1999-02-09 | Ncr Corporation | Low overhead method for detecting communication failures on a network |
| US6446144B1 (en) * | 1998-04-01 | 2002-09-03 | Microsoft Corporation | Method and system for message transfer session management |
| CN101753597A (en) * | 2008-12-09 | 2010-06-23 | 华为技术有限公司 | Keeping alive method between peer node and client under peer node-client architecture |
| CN102347855A (en) * | 2011-07-21 | 2012-02-08 | 福建星网锐捷网络有限公司 | Method, device and network equipment for realizing bidirectional forwarding detection |
| CN102547939A (en) * | 2010-12-30 | 2012-07-04 | 三星电子株式会社 | Keep-alive packet transmission method and apparatus of mobile terminal |
-
2014
- 2014-07-11 CN CN201410331649.1A patent/CN104079494B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5870540A (en) * | 1995-11-20 | 1999-02-09 | Ncr Corporation | Low overhead method for detecting communication failures on a network |
| US6446144B1 (en) * | 1998-04-01 | 2002-09-03 | Microsoft Corporation | Method and system for message transfer session management |
| CN101753597A (en) * | 2008-12-09 | 2010-06-23 | 华为技术有限公司 | Keeping alive method between peer node and client under peer node-client architecture |
| CN102547939A (en) * | 2010-12-30 | 2012-07-04 | 三星电子株式会社 | Keep-alive packet transmission method and apparatus of mobile terminal |
| CN102347855A (en) * | 2011-07-21 | 2012-02-08 | 福建星网锐捷网络有限公司 | Method, device and network equipment for realizing bidirectional forwarding detection |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104079494A (en) | 2014-10-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101764751B (en) | Method, system and equipment for forwarding roaming messages for wireless user terminal travelling across VLAN | |
| CN105591912B (en) | A kind of selection method and device of forward-path | |
| CN106687974B (en) | Attack observation device and attack observation method | |
| CN106533845A (en) | Long-connection state monitoring method and device | |
| CN104038447B (en) | A kind of message transmitting method and equipment | |
| CN104283785A (en) | Method and device for processing flow table rapidly | |
| CN105264918A (en) | System and method for distributed evolved packet core architecture | |
| CN104283791A (en) | Three-layer topology determining method and device in SDN network | |
| CN103718532A (en) | Data transmission method, apparatus and terminal device | |
| CN104601742B (en) | A kind of method and apparatus of message transmissions | |
| CN105871977A (en) | Long connection establishment method and system, and devices | |
| CN104253711B (en) | The management method and equipment of the Group tables of Openflow in a kind of SDN network | |
| CN105281942A (en) | Network equipment sending BGP information and methods for sending BGP information | |
| CN104518936B (en) | Link dynamic aggregation method and apparatus | |
| CN103188171B (en) | A kind of method for dispatching message and equipment | |
| CN109561164A (en) | Management method, device and the NAT device of NAT table item | |
| CN106716975A (en) | A transmission link resume method, device and system | |
| CN206313803U (en) | A kind of router for realizing network game acceleration | |
| CN109150766A (en) | The method and apparatus of dynamic addressing server in local area network based on UDP multicast | |
| CN102158422B (en) | Message forwarding method and equipment for layer 2 ring network | |
| CN104038424B (en) | A kind of processing method and equipment of offline message | |
| CN103825839A (en) | Message transmission method and equipment based on aggregated link | |
| CN104486217A (en) | Cross network message transmitting method and equipment | |
| CN108650337B (en) | Server detection method, system and storage medium | |
| CN105681266B (en) | A kind of communication cluster method and device of mediaphone MMTel |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant after: Xinhua three Technology Co., Ltd. Address before: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant before: Huasan Communication Technology Co., Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |