AIA enhancements to support lag networks

1. A method for maintaining packet's source network identification information while aggregating packets from a plurality of networks, the method comprising:

processing an ingress packet to extract a plurality of packet header fields and port identifier;

generating a first hash index by hashing information associated with the plurality of packet header fields from the ingress packet;

storing the port identifier in a hash table using the generated first hash index;

forwarding the ingress packet to one or more inline tool devices configured to monitor and analyze a flow of Multi Link Aggregation Group (MC-LAG) traffic configured such that one or more links comprising one LAG terminate at ports on a first device and one or more links comprising the same LAG terminate on a second device;

processing an egress packet received from the one or more inline tools to extract the plurality of packet header fields from the egress packet;

generating a second hash index by hashing information associated with the plurality of packet header fields from the egress packet;

retrieving the port identifier from the hash table based on the generated second hash index; and

transmitting the egress packet to a switching device based on the retrieved port identifier.

2. The method of claim 1 , wherein the plurality of packet header fields comprises Layer 2 (L2) source and destination addresses.

3. The method of claim 2 , wherein the processing an ingress packet received from an inline network port comprises determining whether the received ingress packet comprises an IP packet.

4. The method of claim 3 , wherein the plurality of packet fields further comprises at least one of Layer 3 (L3) source and destination addresses, Layer 4 (L4) source and destination ports and L3 protocol field.

5. The method of claim 4 , wherein the first and second hash indices are generated by a cyclic redundancy check 32 (CRC 32) function.

6. The method of claim 5 , wherein the first and second hash indices are generated by the CRC 32 function using the L2 source and destination addresses as hashing keys, responsive to a determination that the ingress packet comprises an IP packet.

7. The method of claim 1 , wherein processing an ingress packet received from an inline network port and processing an egress packet received from the one or more inline tool devices comprises parsing MAC and IP header fields of the corresponding packets.

8. The method of claim 1 , wherein a plurality of ingress packets comprises aggregate packets from a plurality of networks comprising a Link Aggregation Group (LAG).

9. A system comprising:

a plurality of networks comprising a Link Aggregation Group (LAG);

one or more inline tool devices configured to monitor and analyze a flow of LAG network traffic; and

an Advanced Inline Aggregation (AIA) device connected to each of the plurality of networks and connected to the one or more inline tool devices, the AIA device having stored therein a plurality of programming instructions, which when executed on the AIA device cause the AIA device to:

process an ingress packet to extract a plurality of packet header fields and port identifier;

generate a first hash index by hashing information associated with the plurality of packet header fields from the ingress packet;

store the port identifier in a hash table using the generated first hash index;

forward the ingress packet to one or more inline tool devices configured to monitor and analyze a flow of Multi Link Aggregation Group (MC-LAG) traffic configured such that one or more links comprising one LAG terminate at ports on a first device and one or more links comprising the same LAG terminate on a second device;

process an egress packet received from the one or more inline tools to extract the plurality of packet header fields from the egress packet;

generate a second hash index by hashing information associated with the plurality of packet header fields from the egress packet;

retrieve the port identifier from the hash table based on the generated second hash index; and

transmit the egress packet to a switching device based on the retrieved port identifier.

10. The system of claim 9 , wherein the plurality of packet header fields comprises Layer 2 (L2) source and destination addresses.

11. The system of claim 10 , wherein the processing an ingress packet received from an inline network port comprises determining whether the received ingress packet comprises an IP packet.

12. The system of claim 11 , wherein the plurality of packet fields further comprises at least one of Layer 3 (L3) source and destination addresses, Layer 4 (L4) source and destination ports and L3 protocol field.

13. The system of claim 12 , wherein the first and second hash indices are generated by a cyclic redundancy check 32 (CRC 32) function.

14. The system of claim 13 , wherein the first and second hash indices are generated by the CRC 32 function using the L2 source and destination addresses as hashing keys, responsive to a determination that the ingress packet comprises an IP packet.

15. The system of claim 9 , wherein processing an ingress packet received from an inline network port and processing an egress packet received from the one or more inline tool devices comprises parsing MAC and IP header fields of the corresponding packets.

16. The system of claim 9 , wherein the hash table contains a plurality of associations between the generated indices and corresponding port identifier information.

17. The system of claim 9 , wherein the AIA device comprises a Field Programmable Gate Array (FPGA).

18. The system of claim 9 , wherein entries exceeding a predetermined age interval are aged out from the hash table.