Maintaining load balancing after service application with a network device

• US 9,036,476 B2
• Filed: 09/28/2012
• Issued: 05/19/2015
• Est. Priority Date: 09/28/2012
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Krishna, Gopi, Sathyanarayana, Ananda, Balasubramanian, Arun, Vandalore, Bobby, Grandhi, Jagadish
• Primary Examiner(s): Alia, Curtis A
• Application Number:
  US13/630,458
• Publication Number:
  US 20140092738A1
• Time in Patent Office: 963 Days
• Field of Search: 370/216, 370/217, 370/218, 370/221, 370/229, 370/235, 370/237, 370/351, 370/389, 370/392, 370/395.3, 370/395.31, 370/395.32, 370/400, 370/408
• US Class Current: 370/235
• CPC Class Codes: H04L 45/22 Alternate routing
• CPC Class Codes: H04L 45/24 Multipath
• CPC Class Codes: H04L 45/50 using label swapping, e.g. multi-protocol label switch [MPLS]
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 47/52 by attributing bandwidth to queues
• CPC Class Codes: H04L 47/724 at intermediate nodes, e.g. resource reservation protocol [RSVP]
• CPC Class Codes: H04L 47/824 Applicable to portable or mobile terminals
• CPC Class Codes: H04W 28/02 Traffic management, e.g. flow control or congestion control
• CPC Class Codes: H04W 8/04 Registration at HLR or HSS [Home Subscriber Server]

Abstract

In general, techniques are described for maintaining load balancing after service application. A network device comprising ingress and egress forwarding components and a service card may implement the techniques. An ingress forwarding component receives a packet and, in response to a determination that the service is to be applied to the packet, updates the packet to include an ingress identifier that identifies the ingress forwarding component, thereafter transmitting the updated packet to the service card. The service card applies the service to the updated packet to generate a serviced packet and transmits the serviced packet to the ingress forwarding component identified by the ingress identifier so as to maintain load balancing of packet flows across the plurality of forwarding components. The ingress forwarding component determines a next hop to which to forward the serviced packet and the egress forwarding component forwards the serviced packet to the determined next hop.

Claims

1. A method comprising:

receiving a packet with a first one of a plurality of forwarding components included within a network device, wherein the first one of the plurality of forwarding components acts as an ingress forwarding component for a packet flow to which the received packet corresponds;

determining, with the ingress forwarding component, that a service is to be applied to the packet;

updating, with the ingress forwarding component, the packet to include an ingress identifier that identifies the ingress forwarding component in response to the determination that a service is to be applied to the packet;

transmitting, with the ingress forwarding component, the updated packet to a service card that applies the service;

applying, with the service card, the service to the updated packet to generate a serviced packet;

transmitting, with the service card, the serviced packet to the ingress forwarding component identified by the ingress identifier so as to maintain load balancing of packet flows across the plurality of forwarding components;

determining, with the ingress forwarding component, a next hop of a plurality of next hops to which to forward the serviced packet; and

forwarding, with a second one of the plurality of forwarding components, the serviced packet to the determined next hop, wherein the second one of the plurality of forwarding components acts as an egress forwarding component for a packet flow to which the serviced packet corresponds.

2. The method of claim 1,

wherein the packet flow to which the received packet corresponds is identified by a first five tuple that includes a source address, a source port, a destination address, a destination port and a protocol,

wherein the packet flow to which the serviced packet corresponds is identified by a second five tuple that includes a source address, a source port, a destination address, a destination port and a protocol,

wherein applying the service to the updated packet comprises applying, with the service card, the service to the updated packet to generate the serviced packet such that second five tuple is different from the first five-tuple, and

wherein determining the next hop of the plurality of next hops comprises determining the next hop of a plurality of next hops to which to forward the serviced packet based on the second five-tuple so as to distribute packet flows across the plurality of next hops.

3. The method of claim 1, wherein transmitting the serviced packet to the ingress forwarding component comprises transmitting, with the service card, the serviced packet to the ingress forwarding component identified by the ingress identifier without applying a hash function to at least a portion of the serviced packet to identify the ingress forwarding component.

4. The method of claim 1, wherein transmitting the serviced packet to the ingress forwarding component comprises transmitting, with the service card, the serviced packet to the ingress forwarding component identified by the ingress identifier without determining, with the service card, the next hop of the plurality of next hops to which to forward the serviced packet.

5. The method of claim 1, wherein transmitting the serviced packet to the ingress forwarding component comprises transmitting, with the service card, the serviced packet to the ingress forwarding component such that the ingress forwarding component receives the packet as if the packet had been received by the ingress forwarding component via an interface associated with the ingress forwarding component that couples to another network device rather than via a switch fabric coupling the service card to the ingress forwarding component.

6. The method of claim 1, wherein the ingress forwarding component and an additional one of the plurality of forwarding components receive packet flows, including the packet flow to which the packet corresponds, from an adjacent network device having been sent by the adjacent network device in accordance with an equal cost multi-path (ECMP) algorithm or a weighted ECMP (WECMP) algorithm that load balances packet the flows across two or more links coupling the network device to the adjacent network device.

7. The method of claim 1, wherein the ingress forwarding component and an additional one of the plurality of forwarding components receive packet flows, including the packet flow to which the packet corresponds, from an adjacent network device having been sent by the adjacent network device in accordance with a link aggregation algorithm that aggregates two or more links to form a single virtual link and that load balances the packet flows across the two or more links coupling the network device to the adjacent network device.

8. The method of claim 1, wherein updating the packet to include the ingress identifier comprises appending the ingress identifier to the packet.

9. The method of claim 1,

wherein updating the packet to include the ingress identifier comprises appending an internal service packet header to the packet that includes a field specifying the ingress identifier, and

wherein the method further comprises removing the internal service packet header prior to forwarding the serviced packet to the determined next hop.

10. The method of claim 1, wherein applying the service to the updated packet comprises applying one or more of a deep packet inspection service, a network address translation (NAT) service, a firewall service, a tunneling service, an anti-malware service, an anti-virus service, and an encryption service to the updated packet to generate a serviced packet.

11. A network device comprising:

a plurality of forwarding components, wherein a first one of the plurality of forwarding components receives a packet and, acting as an ingress forwarding component for a packet flow to which the received packet corresponds, determines that a service is to be applied to the packet, updates the packet to include an ingress identifier that identifies the ingress forwarding component in response to the determination that the service is to be applied to the packet and transmits the updated packet to a service card that applies the service; and

a service card that applies the service to the updated packet to generate a serviced packet and transmits the serviced packet to the ingress forwarding component identified by the ingress identifier so as to maintain load balancing of packet flows across the plurality of forwarding components,

wherein the ingress forwarding component determines a next hop of a plurality of next hops to which to forward the serviced packet, and

wherein a second one of the plurality of forwarding components acts an egress forwarding component for a packet flow to which the service packet corresponds and forwards the serviced packet to the determined next hop.

12. The network device of claim 11,

wherein the packet flow to which the received packet corresponds is identified by a first five tuple that includes a source address, a source port, a destination address, a destination port and a protocol,

wherein the packet flow to which the serviced packet corresponds is identified by a second five tuple that includes a source address, a source port, a destination address, a destination port and a protocol,

wherein the service card, in applying the service to the updated packet, applies the service to the updated packet to generate the serviced packet such that second five tuple is different from the first five-tuple, and

wherein the ingress forwarding component, when determining the next hop of the plurality of next hops, determines the next hop of a plurality of next hops to which to forward the serviced packet based on the second five-tuple.

13. The network device of claim 11, wherein the service card, when transmitting the serviced packet to the ingress forwarding component, transmits the serviced packet to the ingress forwarding component identified by the ingress identifier without applying a hash function to at least a portion of the serviced packet to identify the ingress forwarding component.

14. The network device of claim 11, wherein the service card, when transmitting the serviced packet to the ingress forwarding component, transmits the serviced packet to the ingress forwarding component identified by the ingress identifier without determining the next hop of the plurality of next hops to which to forward the serviced packet.

15. The network device of claim 11, wherein the service card, when transmitting the serviced packet to the ingress forwarding component, transmits the serviced packet to the ingress forwarding component such that the ingress forwarding component receives the packet as if the packet had been received by the ingress forwarding component via an interface associated with the ingress forwarding component that couples to another network device rather than via a switch fabric coupling the service card to the ingress forwarding component.

16. The network device of claim 11, wherein the ingress forwarding component and an additional one of the plurality of forwarding components receive packet flows, including the packet flow to which the packet corresponds, from an adjacent network device having been sent by the adjacent network device in accordance with an equal cost multi-path (ECMP) algorithm or a weighted ECMP (WECMP) algorithm that load balances packet the flows across two or more links coupling the network device to the adjacent network device.

17. The network device of claim 11, wherein the ingress forwarding component and an additional one of the plurality of forwarding components receive packet flows, including the packet flow to which the packet corresponds, from an adjacent network device having been sent by the adjacent network device in accordance with a link aggregation algorithm that aggregates two or more links to form a single virtual link and that load balances the packet flows across the two or more links coupling the network device to the adjacent network device.

18. The network device of claim 11, wherein the ingress forwarding component, when updating the packet to include the ingress identifier, appends the ingress identifier to the packet.

19. The network device of claim 11,

wherein the ingress forwarding component, when updating the packet to include the ingress identifier, appends an internal service packet header to the packet that includes a field specifying the ingress identifier, and

wherein either the ingress forwarding component further removes the internal service packet header prior to forwarding the serviced packet to the determined next hop.

20. The network device of claim 11, wherein the service card, when applying the service to the updated packet, applies one or more of a deep packet inspection service, a network address translation (NAT) service, a firewall service, a tunneling service, an anti-malware service, an anti-virus service, and an encryption service to the updated packet to generate a serviced packet.

21. A service card configured to be inserted into a network device and couple to a plurality of forwarding components of the network device, the service card comprising:

a control unit that receives a packet from a first one of the plurality of forwarding components acting as an ingress forwarding component for a packet flow to which the packet corresponds, wherein the packet includes an internal service packet header that includes a field specifying an ingress identifier that identifies the ingress forwarding component, and

wherein the control unit executes a service engine that applies a service to the updated packet to generate a serviced packet,

wherein the control unit further transmits the serviced packet to the ingress forwarding component identified by the ingress identifier so as to maintain load balancing of packet flows across the plurality of forwarding components.

22. The service card of claim 21,

wherein the packet flow to which the received packet corresponds is identified by a first five tuple that includes a source address, a source port, a destination address, a destination port and a protocol,

wherein the packet flow to which the serviced packet corresponds is identified by a second five tuple that includes a source address, a source port, a destination address, a destination port and a protocol, and

wherein, when applying the service to the updated packet, the service engine applies the service to the updated packet to generate the serviced packet such that second five tuple is different from the first five-tuple.

23. The service card of claim 21, wherein the control unit transmits the serviced packet to the ingress forwarding component identified by the ingress identifier without applying a hash function to at least a portion of the packet to identify the ingress forwarding component.

24. The service card of claim 21, wherein the control unit transmits the serviced packet to the ingress forwarding component identified by the ingress identifier without determining, with the service card, the next hop of the plurality of next hops to which to forward the serviced packet.

25. The service card of claim 21, wherein the control unit transmits the service packet to the ingress forwarding component such that the ingress forwarding component receives the packet as if the packet had been received by the ingress forwarding component via an interface associated with the ingress forwarding component that couples to another network device rather than via a switch fabric coupling the service card to the ingress forwarding component.