Conflict avoidant traffic routing in a network environment

Patent metadata

Field	Value
Publication number	US-9787572-B2
Application number	US-201414508680-A
Country	US
Kind code	B2
Filing date	Oct 7, 2014
Priority date	Oct 7, 2014
Publication date	Oct 10, 2017
Grant date	Oct 10, 2017

Abstract

An example method for facilitating conflict avoidant traffic routing in a network environment is provided and includes detecting, at a network element, an intent conflict at a peer network element in a network, and changing a forwarding decision at the network element to steer traffic around the conflicted peer network element. The intent conflict refers to an incompatibility between an asserted intent associated with the traffic and an implemented intent associated with the traffic. In specific embodiments, the detecting includes mounting rules from the peer network element into the network element, and analyzing the mounted rules to determine intent conflict. In some embodiments, a central controller in the network deploys one or more intentlets on a plurality of network elements in the network according to corresponding intent deployment parameters.

First claim

What is claimed is:

1. A method executed at a network element in a network environment, comprising:
receiving, at the network element, traffic between two endpoints, wherein the traffic is to be forwarded from the network element to a peer network element in the network according to a forwarding decision at the network element, the peer network element being coupled to the network element over a network interface of the network element, wherein the network element and the peer network element are intermediary nodes in the network for the traffic;
detecting, at the network element, an intent conflict for forwarding the traffic at the peer network element, wherein the intent conflict exists at the peer network element, wherein the intent conflict comprises an incompatibility between an asserted intent for forwarding the traffic and an implemented intent for forwarding the traffic, wherein the peer network element cannot forward the traffic until the intent conflict is resolved, wherein the detecting comprises mounting rules from the peer network element into the network element over the network interface, wherein the mounted rules are acquired from a locally addressable data store, and analyzing the mounted rules for inconsistency to determine the intent conflict;
changing the forwarding decision at the network element to steer traffic around the conflicted peer network element; and
forwarding the traffic away from the conflicted peer network element, wherein a central controller in the network deploys one or more intentlets on a plurality of network elements in the network according to corresponding intent deployment parameters, wherein the intentlets are deployed according to pre-configured accuracy and convergence bounds.

2. The method of claim 1 , further comprising:
identifying another peer network element that does not have the intent conflict; and
changing the forwarding decision to steer traffic to the another peer network element.

3. The method of claim 1 , further comprising automatically generating a list of network elements that are conflicted.

4. The method of claim 1 , wherein the central controller maintains status information connected with the intentlet deployment on each of the plurality of network elements.

5. The method of claim 1 , wherein the controller monitors the intentlets deployed on the plurality of network elements, wherein if the intentlet is not implemented on any particular network element, the intentlet is reapplied on the particular network element.

6. The method of claim 5 , wherein the controller queries the network elements for a cause of the intentlet not being implemented and determines whether corrective action should be taken before reapplying the intentlet.

7. The method of claim 1 , further comprising:
receiving an intentlet from the controller;
comparing the received intentlet with existing intents implemented on the network element;
re-ordering the existing intents and the received intentlet based on respective pre-assigned priorities when a conflict is detected between the received intentlet and one of the existing intents;
deciding to deploy the received intentlet if the received intentlet is of higher priority than the conflicting existing intent; and
deciding not to deploy the received intentlet if the received intentlet is not of higher priority than the conflicting existing intent.

8. The method of claim 7 , further comprising periodically comparing the received intentlet with the existing intents, if the received intentlet is not deployed.

9. Non-transitory tangible media that includes instructions for execution, which when executed by a processor of a network element located in a network, is operable to perform operations comprising:
receiving, at the network element, traffic between two endpoints, wherein the traffic is to be forwarded from the network element to a peer network element in the network according to a forwarding decision at the network element, the peer network element being coupled to the network element over a network interface of the network element, wherein the network element and the peer network element are intermediary nodes in the network for the traffic;
detecting, at the network element, an intent conflict for forwarding the traffic at the peer network element, wherein the intent conflict exists at the peer network element, wherein the intent conflict comprises an incompatibility between an asserted intent for forwarding the traffic and an implemented intent for forwarding the traffic, wherein the peer network element cannot forward the traffic until the intent conflict is resolved, wherein the detecting comprises mounting rules from the peer network element into the network element over the network interface, wherein the mounted rules are acquired from a locally addressable data store, and analyzing the mounted rules for inconsistency to determine the intent conflict;
changing the forwarding decision at the network element to steer traffic around the conflicted peer network element; and
forwarding the traffic away from the conflicted peer network element, wherein a central controller in the network deploys one or more intentlets on a plurality of network elements in the network according to corresponding intent deployment parameters, wherein the intentlets are deployed according to pre-configured accuracy and convergence bounds.

10. The media of claim 9 , wherein the operations further comprise:
identifying another peer network element that does not have the intent conflict; and
changing the forwarding decision to steer traffic to the another peer network element.

11. The media of claim 9 , wherein the controller monitors the intentlets deployed on the plurality of network elements, wherein if any of the intentlets is not implemented on any particular network element, the intentlet is reapplied on the particular network element.

12. The media of claim 11 , wherein the central controller queries the network elements for a cause of the intentlet not being implemented and determines whether corrective action should be taken before reapplying the intentlet.

13. The media of claim 9 , wherein the operations further comprise automatically generating a list of network elements that are conflicted.

14. The media of claim 9 , wherein the central controller maintains status information connected with the intentlet deployment on the plurality of network elements.

15. An apparatus located in a network, comprising:
a network interface;
a memory element for storing data; and
a processor, wherein the processor executes instructions associated with the data, wherein the processor and the memory element cooperate, such that the apparatus is configured for:
receiving, at the apparatus, traffic between two endpoints, wherein the traffic is to be forwarded from the apparatus to a peer apparatus in the network according to a forwarding decision at the apparatus, the peer apparatus being coupled to the apparatus over the network interface, wherein the apparatus and the peer apparatus are intermediary nodes in the network for the traffic;
detecting, at the apparatus, an intent conflict for forwarding the traffic at the peer apparatus, wherein the intent conflict exists at the peer apparatus, wherein the intent conflict comprises an incompatibility between an asserted intent for forwarding the traffic and an implemented intent for forwarding the traffic, wherein the peer apparatus cannot forward the traffic until the intent conflict is resolved, wherein the detecting comprises mounting rules from the peer apparatus into the apparatus over the network

Assignees

• Cisco Tech Inc

Inventors

• Voit Eric A
• Salam Samer
• Clemm Ludwig Alexander
• Chandramouli Yegnanarayanan Gargya

Classifications

• H04L41/0873

  Checking configuration conflicts between network elements · CPC title

• H04L45/28

  using route fault recovery · CPC title

• H04L47/122

  by diverting traffic away from congested entities · CPC title

• H04L45/22 Primary

  Alternate routing · CPC title

• H04L41/0672

  Electricity · mapped topic