Notifying a controller of a change to a packet forwarding configuration of a network element over a communication channel

• US 8,897,134 B2
• Filed: 12/17/2010
• Issued: 11/25/2014
• Est. Priority Date: 06/25/2010
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Kern, Andrs, Jocha, Dvid
• Primary Examiner(s): Masur, Paul H.
• Assistant Examiner(s): PHILLIPS, MICHAEL K
• Application Number:
  US12/971,647
• Publication Number:
  US 20110317559A1
• Time in Patent Office: 1,439 Days
• Field of Search: 370/356, 370/373, 370/377, 370/384, 370/385, 370/410, 370/426, 370/229, 370/237, 370/395.32, 370/220, 370/422, 370/235, 370/2, 370/54
• US Class Current: 370/235
• CPC Class Codes: H04L 41/0816 the condition being an adaptation, e.g. in response to network events
• CPC Class Codes: H04L 41/342 between virtual entities, e.g. orchestrators, SDN or NFV entities
• CPC Class Codes: H04L 45/02 Topology update or discovery

Abstract

A method performed by a network element, for notifying a controller of a change to a packet forwarding configuration of the network element. The network element is separated from the controller by a communication channel. The method includes determining the change to the packet forwarding configuration of the network element. The packet forwarding configuration specifies how packets are to be forwarded by the network element. The method also includes actively notifying the controller of the change to the packet forwarding configuration by sending a message to the controller over the communication channel. The message, in addition to indicating the change, also indicates at least one detail about the packet forwarding configuration after the change.

Claims

1. A method performed by a network element, for notifying a controller of a change to a packet forwarding configuration of the network element, where the network element is separated from the controller by a communication channel, the method comprising:

receiving packet forwarding configuration modification messages from the controller over the communication channel that are operable to control the network element to modify the packet forwarding configuration;

determining the change to the packet forwarding configuration of the network element, wherein the packet forwarding configuration specifies how packets are to be forwarded by the network element and specifies to which ports of the network element the packets are to be forwarded; and

actively notifying the controller of the change to the packet forwarding configuration by sending a message to the controller over the communication channel, the message in addition to indicating the change also indicating at least one detail about a portion of the packet forwarding configuration after the change, wherein the at least one detail comprises a detail of a flow entry in the flow table after the change, wherein each flow entry includes header fields, counters, and zero or more data forwarding actions to apply to a packet that matches the header fields, and wherein the message containing the detail of the flow entry after the change is sent to the controller without explicit instruction from the controller.

2. The method of claim 1, further comprising:

receiving a packet forwarding configuration modification message from the controller over the communication channel, the packet forwarding configuration modification message specifying a modification to the packet forwarding configuration of the network element, and

wherein determining the change to the packet forwarding configuration comprises determining the change to the packet forwarding configuration that is different than the modification specified by the message.

3. The method of claim 2, wherein actively notifying the controller which is an OpenFlow controller comprises sending the message that includes:

one of;

(a) an identification of the packet forwarding configuration modification message; and

(b) the modification specified by the packet forwarding configuration modification message; and

a second packet forwarding configuration modification message, the second packet forwarding configuration modification message specifying the change to the packet forwarding configuration.

4. The method of claim 2, wherein actively notifying the controller which is an OpenFlow controller comprises sending the message indicating a reason for the change, the reason selected from a group consisting of:

(a) the packet forwarding configuration modification message was invalid;

(b) the packet forwarding configuration modification message was changed to improve performance of the network element; and

(c) the packet forwarding configuration modification message was translated by a virtualization entity.

5. The method of claim 1, further comprising:

detecting a flow changing event within the network element by the network element, and

wherein determining the change includes the network element determining to change the packet forwarding configuration, without explicit instruction from the controller, based on the detection of the flow changing event.

6. The method of claim 5, wherein detecting the flow changing event comprises detecting that a port associated with a flow is unavailable, wherein determining the change includes determining a replacement port for the port that is unavailable, and wherein sending the message indicating the at least one detail includes sending the message indicating the replacement port for the flow.

7. The method of claim 1, wherein determining the change comprises determining the change based on information internal to the network element that is not available to the controller, and further comprising adding a flow entry to a flow table based on a message received from the controller, the flow entry indicating a port to which a packet associated with the flow entry is to be forwarded.

8. The method of claim 1, wherein determining the change to the packet forwarding configuration comprises determining the change to a flow table that includes flow entries, each flow entry including header fields, counters, and zero or more data forwarding actions to apply to a packet that matches the header fields, and wherein the at least one detail comprises a detail of a flow entry in the flow table after the change.

9. The method of claim 1, wherein the method is performed within the network element which is OpenFlow enabled, wherein actively notifying the controller is not in response to a query from the controller, wherein detecting the change comprises detecting the change that is not merely a deletion of a portion of the packet forwarding configuration, and wherein the detail comprises the detail of an entry of a flow table after the change that is one of a changed header field that packets are to be compared against, a changed packet forwarding action that is to be applied to matching packets, and a changed output port to be used for forwarding.

10. A network element, the network element operable to be coupled with a controller by a communication channel, the network element operable to notify the controller of a change to a packet forwarding configuration of the network element, the network element comprising:

an interface to the communication channel;

the packet forwarding configuration, wherein the packet forwarding configuration specifies how packets are to be forwarded by the network element and specifies to which ports of the network element the packets are to be forwarded;

a configuration change determination module coupled with the packet forwarding configuration, the configuration change determination module operable to determine the change to the packet forwarding configuration of the network element; and

a notification module coupled with the configuration change determination module, the notification module operable to notify the controller of the change to the packet forwarding configuration by sending a message to the controller over the communication channel through the interface, the message in addition to indicating the change also indicating at least one detail about a portion of the packet forwarding configuration after the change, wherein the at least one detail comprises a detail of a flow entry in the flow table after the change, wherein each flow entry includes header fields, counters, and zero or more data forwarding actions to apply to a packet that matches the header fields, and wherein the message containing the detail of the flow entry after the change is sent to the controller without explicit instruction from the controller.

11. The network element of claim 10,

wherein the interface is operable to receive a packet forwarding configuration modification message from the controller over the communication channel, the packet forwarding configuration modification message operable to specify a modification to the packet forwarding configuration, and

wherein the configuration change determination module is operable to determine the change to the packet forwarding configuration that is different than the modification specified by the packet forwarding configuration modification message.

12. The network element of claim 11, wherein the notification module comprises a message generation module, the message generation module operable to generate the message to be sent that includes:

one of;

(a) an identification of the packet forwarding configuration modification message; and

(b) the modification specified by the packet forwarding configuration modification message; and

a second packet forwarding configuration modification message, the second packet forwarding configuration modification message specifying the change to the packet forwarding configuration.

13. The network element of claim 10, wherein the network element is OpenFlow enabled and is operable to detect a flow changing event within the network element, and wherein the configuration change determination module is operable to determine to change the packet forwarding configuration, without explicit instruction from the controller, based on the detection of the flow changing event.

14. The network element of claim 13, wherein the network element is operable to detect that a port associated with a flow is unavailable as the flow changing event, wherein the configuration change determination module is operable to determine a replacement port for the port that is unavailable, and wherein the notification module is operable to indicate the replacement port in the message sent to the controller.

15. The network element of claim 10, wherein the packet forwarding configuration comprises a flow table that includes flow entries, each flow entry including header fields, counters, and zero or more data forwarding actions to apply to a packet that matches the header fields, and wherein the network element is to add a flow entry to the flow table in response to a message from the controller which includes a header field and an indication of a port where a packet that matches the header field is to be forwarded, and wherein the detail comprises a detail of a flow entry of the flow table after the change.

20. The network element of claim 10, wherein the network element is OpenFlow enabled and wherein the controller comprises an OpenFlow controller, wherein the configuration change determination module is to determine the change which is not merely a deletion of a flow entry, and wherein the notification module is operable to notify the controller of the change not in response to a read-state message from the controller requesting information.

21. The network element of claim 10, wherein the configuration change determination module and the notification module comprise an OpenFlow agent, and wherein the configuration change determination module and the notification module each comprise at least one of hardware, software, and firmware.

16. A method performed by a controller of a network element, for updating a record of a packet forwarding configuration of the network element that is maintained by the controller, where the controller is separated from the network element by a communication channel, the method comprising:

receiving a notification of a change to the packet forwarding configuration of the network element over the communication channel, wherein the packet forwarding configuration specifies how packets are to be forwarded by the network element, and wherein the notification, in addition to indicating the change, also indicates at least one detail about a portion of the packet forwarding configuration of the network element after the change, wherein the at least one detail comprises a detail of a flow entry in the flow table after the change, wherein each flow entry includes header fields, counters, and zero or more data forwarding actions to apply to a packet that matches the header fields, and wherein the message containing the detail of the flow entry after the change is sent to the controller without explicit instruction from the controller; and

updating the record of the packet forwarding configuration to reflect the change, wherein the controller is to maintain the record of the packet forwarding configuration of the network element including to which ports of the network elements the packets are to be forwarded.

22. The method of claim 16, further comprising the controller sending a message, which is an OpenFlow protocol message, to the network element to one of allow and deny changes to a packet forwarding configuration modification message sent from the controller to the network element.

23. The method of claim 16, wherein receiving the notification comprises receiving an OpenFlow protocol message, and further comprising the controller sending a message to the network element to request that the network element provide notification of changes to multiple packet forwarding configuration modification messages sent by the controller to the network element.

17. An OpenFlow controller of a network element, the OpenFlow controller operable to be coupled with the network element by a communication channel, the OpenFlow controller operable to update a record of a packet forwarding configuration of the network element that is maintained by the OpenFlow controller, the OpenFlow controller comprising:

an interface to the communication channel, the interface operable to receive a notification of a change to the packet forwarding configuration of the network element from the communication channel, wherein the notification, in addition to indicating the change, also indicates at least one detail about a portion of the packet forwarding configuration of the network element after the change, wherein the at least one detail comprises a detail of a flow entry in the flow table after the change, wherein each flow entry includes header fields, counters, and zero or more data forwarding actions to apply to a packet that matches the header fields, and wherein the message containing the detail of the flow entry after the change is sent to the controller without explicit instruction from the controller;

the record of the packet forwarding configuration of the network element, wherein the packet forwarding configuration specifies how packets are to be forwarded by the network element; and

an update module coupled with the record of the packet forwarding configuration to update the record of the packet forwarding configuration to reflect the change indicated by the notification.

18. The OpenFlow controller of claim 17, further comprising a change authorization module that is operable to in one instance send a first message to the network element to allow changes to a packet forwarding configuration modification message sent from the OpenFlow controller to the network element, and in another instance send a second message to the network element to deny changes to the packet forwarding configuration modification message sent from the OpenFlow controller to the network element.

19. The OpenFlow controller of claim 17, further comprising a change notification request module that is operable to send a message to the network element to request that the network element provide notification of changes to multiple packet forwarding configuration modification messages sent by the OpenFlow controller to the network element.

24. The OpenFlow controller of claim 17, wherein the update module comprises at least one of hardware, software, and firmware.