COMMMON AGENT FRAMEWORK FOR NETWORK DEVICES

• US 20140269762A1
• Filed: 03/15/2013
• Published: 09/18/2014
• Est. Priority Date: 03/15/2013
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: VOIT, Eric A., PRUSS, Richard M., MCDOWALL, John E.
• Granted Patent: US 9,100,346 B2
• Time in Patent Office: Days
• US Class Current: 370/466
• CPC Class Codes: H04L 41/022 Multivendor or multi-standard integration
• CPC Class Codes: H04L 41/0816 the condition being an adaptation, e.g. in response to network events
• CPC Class Codes: H04L 43/028 by filtering
• CPC Class Codes: H04L 45/52 Multiprotocol routers
• CPC Class Codes: H04L 49/602 Multilayer or multiprotocol switching, e.g. IP switching
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols

Abstract

Techniques are provided for automating a common framework for network devices. In one example, a network device (e.g., switch, router, etc.) is configured to resolve the handling unknown packets automatically. The network device can detect whether or not a protocol is unknown to the network device, perform a lookup, determine if a matching protocol is available for the network device, and dynamically load an appropriate protocol handler into a memory of the network device. Advantageously, the present technology provides a mechanism for flexible on-demand push of protocol information. If a new protocol is noted on the network, the network device can look up the type of packet and can use a single platform kit to dynamically load drivers and control logic for that protocol onto the network device. Likewise, other network devices in the packet'"'"'s path or in the network generally can load the drivers and control logic, as needed.

Claims

1. A computer-implemented method for automating packet handling on a network device, the method comprising:

receiving a packet;

detecting for the packet a protocol that is unknown to the network device;

performing a lookup of the protocol to identify a matching protocol handler for the unknown protocol; and

upon determining a matching protocol is available, dynamically loading a protocol handler corresponding to the matching protocol into memory of the network device.

2. The method of claim 1, further comprising, communicating with one or more other network devices to provide an opportunity for the one or more other network devices to load the protocol handler corresponding to the matching protocol into memory of the one or more other network devices.

3. The method of claim 1, further comprising:

determining that a matching protocol handler is available at the network device; and

determining that the matching protocol handler is not loaded on the network device.

4. The method of claim 1, further comprising, parsing the packet to extract fields used to handle the packet, wherein an extracted field includes a header identifies a protocol for handling the packet.

5. The method of claim 1, wherein performing the lookup comprises at least one of:

reading Multiprotocol Label Switching (MPLS) tags;

reading Virtual Extensible Local Area Network (VxLAN) identifiers;

performing Deep Packet Inspection (DPI);

or

performing pattern matching on the packet header.

6. The method of claim 1, wherein performing the lookup comprises sending the packet to an external lookup device to perform a lookup for an appropriate protocol handler for the packet.

7. The method of claim 1, further comprising, passing to the protocol handler at least one of:

the packet;

a pointer to the packet;

or

a packet flow.

8. The method of claim 1, further comprising dynamically registering one or more applicable routes in a component of the network device that is configured to perform switching operations.

9. The method of claim 1, further comprising registering the appropriate protocol handler in memory for use on other data packets that match particular criteria of the network device.

10. The method of claim 1, wherein dynamically loading the appropriate protocol handler comprises using an application programming interface (API) of a single platform kit, wherein the single platform kit includes a toolkit for development, automation, and rapid service generation on a data center to which the network device is connected.

11. The method of claim 1, wherein dynamically loading means loading the appropriate protocol handler into the memory after the network device receives the packet and during processing operations for the packet.

12. A network device configured for automating packet handling on a network device, the network device comprising:

a protocol identifier component configured to receive a packet, detect for the packet a protocol that is unknown to the network device, perform a lookup of the protocol that is unknown in order to find a matching protocol handler, and determine if a matching protocol is available for the network device; and

a default handler component configured to dynamically load an appropriate protocol handler into a memory of the network device.

13. The network device of claim 12, further comprising a loaded handler component configured to determine if a matching protocol handler is not loaded on the network device.

14. The network device of claim 13, wherein the default protocol handler comprises an application configured to run on at least one of:

the network device;

a blade server that is accessible to the network device;

or

another network device that is completely separate from the network device.

15. The network device of claim 13, wherein the default handler component includes a chain of default handlers such that each default handler in the chain of default handlers can potentially provide the appropriate protocol handler for a particular packet.

16. The network device of claim 15, wherein the default handler component is configured to register a custom protocol from a third party and to place the custom protocol in high priority in the chain of default handlers.

17. The network device of claim 13, wherein the appropriate protocol handler is located on a virtual machine that is dynamically instatiated after the packet is detected.

18. The network device of claim 13, wherein the network device is linked to a softwared defined network.

19. The network device of claim 13, wherein the network device is configured to communicate with one or more other network devices to provide an opportunity for the one or more other network devices to load the appropriate protocol handler into memory of the one or more other network devices.

20. One or more computer-readable storage media storing instructions for automating packet handling on a network device, wherein the instructions, when executed, direct the one or more processors to perform steps comprising:

receiving a packet;

detecting for the packet a protocol that is unknown to the network device;

performing a lookup of the protocol that is unknown in order to find a matching protocol handler;

determining if a matching protocol is available for the network device; and

dynamically loading an appropriate protocol handler into a memory of the network device.