Redirecting data units to service modules based on service tags and a redirection table

• US 8,284,664 B1
• Filed: 09/28/2007
• Issued: 10/09/2012
• Est. Priority Date: 09/28/2007
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Aybay, Gunes, Nakil, Harshad, Shi, Fuguang, Kohn, Jack, Rowell, David
• Primary Examiner(s): Blanton, John
• Assistant Examiner(s): Patel, Jay P
• Application Number:
  US11/863,480
• Time in Patent Office: 1,838 Days
• Field of Search: 370/235, 370/236, 370/389, 370/412
• US Class Current: 370/235
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 49/3009 Header conversion, routing tables or routing tags
• CPC Class Codes: H04L 49/355 Application aware switches, e.g. for HTTP
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers

Abstract

A device may receive a data unit and identify a class of the received data unit. The device may further obtain a service tag based on the class of the data unit and send the service tag and the data unit to a service module in the network device. The service module may perform a service for the data unit.

Claims

1. A method comprising:

receiving a data unit at an ingress line interface of a network device;

at the ingress line interface, performing a lookup into a classification table, associated with the ingress line interface, based on header information of the data unit;

identifying a class of the received data unit based on the performed lookup;

at the ingress line interface, obtaining a service tag based on the class of the data unit, where the service tag includes a redirect subcommand field, the redirect subcommand field including a subcommand, used by a service module of the network device, to specify further processing required by the data unit, or provide an indication for assigning the data unit to at least one of a component or a service sub-module of the network device;

identifying at the ingress line interface, based on information included in the obtained service tag, the service module of the network device;

sending, based on identifying the service module, the service tag and the data unit, across a switch fabric of the network device from the ingress line interface to the service module in the network device;

performing a service for the data unit at the service module of the network device based on the subcommand;

determining whether the data unit requires further processing; and

upon determining the data unit requires no further processing, clearing fields of the service tag, and sending the data unit to a network address originally included in a data unit descriptor.

2. The method of claim 1, further comprising:

sending the data unit from the service module to an egress line interface.

3. The method of claim 1, further comprising:

upon determining the data unit requires further processing, sending the data unit from the service module to another service module based on a value of a destination field, corresponding to the other service module, that is indicated in a redirection table.

4. The method of claim 1, further comprising:

upon determining the data unit requires further processing, sending the data unit from the service module to another service module by rewriting the service tag and by following a new value of a destination field that is indicated in a redirection table.

5. The method of claim 1, where sending the service tag and the data unit includes:

sending the service tag and the data unit to a fabric interface; and

providing the fabric interface with a fabric port number.

6. The method of claim 1, where obtaining a service tag includes:

performing an access control list (ACL) lookup based on the class to find information that is needed to create the service tag.

7. The method of claim 1, further comprising:

obtaining a data unit descriptor that includes a destination network port number and a destination switch fabric port number.

8. The method of claim 1, where obtaining a service tag further includes:

creating the service tag with a redirection index that references a row in a redirection table, the row including information in a destination field indicative of the service module.

9. The method of claim 8, where sending the service tag and the data unit to the service module includes:

looking up the row using the redirection index in the service tag and the redirection table;

obtaining a target destination within the row; and

sending the service tag and the received data unit to the target destination.

10. The method of claim 1, where sending the service tag and the data unit to the service module includes:

copying the data unit and sending the copy of the data unit to a target destination of the data unit.

11. A device comprising:

a first line interface to;

receive a data unit,

identify a class of the received data unit,

obtain a data unit descriptor and a service tag using the data unit,

where the service tag is obtained by an access control list (ACL) lookup, the ACL including a plurality of rules that detail one or more services that are available on the device,

where the service tag includes a redirect subcommand field, the redirect subcommand field including;

a subcommand, used by a service module of the network device, to;

specify further processing required by the data unit, or

provide an indication for assigning the data unit to at least one of a component or a service sub-module of the network device,

augment the data unit by appending the data unit descriptor and the service tag to the data unit, and

send the augmented data unit from the first line interface to the service module;

and

the service module to;

receive the augmented data unit from the first line interface,

render a service for the augmented data unit, and

perform, based on the subcommand, one of;

sending the augmented data unit to another service module,

sending the augmented data unit to a second line interface,

dropping the augmented data unit, or

clearing fields of the service tag and sending the augmented data unit to a network address originally included in the data unit descriptor, if the subcommand does not specify further processing is required.

12. The device of claim 11, where the first line interface includes:

a redirection table that includes information about the service module and that may be searched based on a redirection index in the service tag.

13. The device of claim 11, where the first line interface includes:

a forwarding table that provides information needed to create the data unit descriptor.

14. The device of claim 11, further comprising:

a switch fabric that can convey the data unit from the first line interface to the service module, from the first line interface to a second line interface, or from the service module to another service module.

15. The device of claim 11, where the service tag includes:

a redirect subcommand and a redirection index that references service module target destination information in a redirection table.

16. A device comprising:

means for receiving a data unit at an ingress line interface of a network device;

means for obtaining a data unit descriptor based on a forwarding table and the received data unit;

means for identifying a class of the received data unit at the ingress line interface based on a classification table lookup using header information of the data unit, where the classification table includes one or more rules for performing an access control list (ACL) lookup or rendering differentiated quality of service;

means for obtaining a service tag at an ingress line interface based on the class of the received data unit, where the service tag includes a redirect subcommand field, the redirect subcommand field including a subcommand, used by a service module of the network device, to specify further processing required by the data unit, or provide an indication for assigning the data unit to at least one of a component or a service sub-module of the network device;

means for augmenting the data unit by attaching the service tag and the data unit descriptor to the data unit;

means for retrieving a target destination of the data unit from a redirection table by using a redirection index in the service tag;

means for sending the data unit from the ingress line interface to the service module of the network device based on the retrieved target destination;

means for determining whether the augmented data unit requires further processing; and

means for clearing fields of the service tag and means for sending the augmented data unit to a network address originally included in the data unit descriptor, upon determining the data unit requires no further processing.

18. The device of claim 16, further comprising:

means for sending the data unit from the service module to another service module by rewriting the service tag and by following a new value of a destination field that is indicated in the redirection table, upon determining the data unit requires further processing.

17. The device of 11, where the redirection table includes at least one row, the row including a destination field specifying two or more service modules.