Network traffic redirection in bi-planar networks

• US 9,338,021 B2
• Filed: 12/21/2006
• Issued: 05/10/2016
• Est. Priority Date: 05/03/2005
• Status: Active Grant

• Current Assignee: Trend Micro Inc.
• Original Assignee: Trend Micro Inc.
• Inventors: Sarin, Alexander, Kabbara, Hazem, Tiew, Chin Yaw
• Primary Examiner(s): ANWAR, MOHAMMAD S
• Application Number:
  US11/643,553
• Publication Number:
  US 20080151754A1
• Time in Patent Office: 3,428 Days
• Field of Search: 370/235, 370/229, 370/230
• US Class Current: 1/1
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management
• CPC Class Codes: H04L 43/028 by filtering

Abstract

An electronic communication network includes a connectivity subsystem. The connectivity subsystem registers a control subsystem with the connectivity subsystem. The control subsystem requests that network traffic be redirected from the connectivity subsystem to the control subsystem. In response to the request, the connectivity subsystem redirects network traffic from the connectivity subsystem to the control subsystem.

Claims

1. A method comprising:

receiving, in a connectivity subsystem, a registration request from a control subsystem;

sending, by the connectivity subsystem, a registration confirmation message to the control subsystem, wherein the registration confirmation message includes information related to capabilities of the connectivity subsystem;

receiving a redirection request requesting that network traffic be redirected from the connectivity subsystem to the control subsystem; and

redirecting network traffic from the connectivity subsystem to the control subsystem in response to the redirection request.

2. The method of claim 1, further comprising:

assigning a registration identifier to the control subsystem.

3. The method of claim 1, further comprising:

confirming the network traffic redirection request.

4. The method of claim 3, wherein confirming the network traffic redirection request comprises sending a redirection confirmation message from the connectivity subsystem to the control subsystem.

5. The method of claim 1, wherein redirecting network traffic from the connectivity subsystem to the control subsystem comprises:

receiving the network traffic; and

sending the network traffic to the control subsystem.

6. The method of claim 5, wherein redirecting network traffic from the connectivity subsystem to the control subsystem further comprises:

adding to the received network traffic an identifier that identifies the traffic redirection request.

7. The method of claim 1, wherein receiving the redirection request comprises receiving a redirection request requesting that network traffic satisfying redirection criteria be redirected to the control subsystem;

and

wherein redirecting network traffic from the connectivity subsystem to the control subsystem comprises;

determining whether the network traffic satisfies the redirection criteria; and

redirecting the network traffic to the control subsystem if the network traffic is determined to satisfy the redirection criteria.

8. The method of claim 7, wherein receiving the redirection request comprises receiving the redirection request requesting that the network traffic be redirected in one of an IP address mode, a copy and forward mode, and a redirect mode.

9. The method of claim 1, further comprising:

storing registration information about the control subsystem in a Management Information Base (MIB).

10. The method of claim 9, further comprising:

determining that the control subsystem has become inoperable;

discontinuing redirection of the network traffic to the control subsystem; and

de-registering the control subsystem.

11. The method of claim 1, further comprising:

receiving a registration request message from the control subsystem using a protocol which operates between the control subsystem and the connectivity subsystem;

receive the redirection request using the protocol; and

redirecting the network traffic to the control subsystem over a data path.

12. The method of claim 1, wherein the control subsystem is part of a control plane.

13. The method of claim 12, wherein the control plane comprises a plurality of control subsystems.

14. An electronic communication network comprising:

a connectivity subsystem,

wherein the connectivity subsystem is to;

receive a registration request from a control subsystem,

send a registration confirmation message to the control subsystem, wherein the registration confirmation message includes information related to capabilities of the connectivity subsystem,

receive a redirection request from the control subsystem,

confirm the redirection request, and

redirect network traffic to the control subsystem in response to the redirection request.

15. The electronic communication network of claim 14, wherein the connectivity subsystem is further to register the control subsystem with the connectivity subsystem in response to the registration request.

16. The electronic communication network of claim 15, wherein the connectivity subsystem is further to store registration information about the control subsystem in a data store.

17. The electronic communication network of claim 14, wherein the connectivity subsystem is to receive the network traffic and send the network traffic to the control subsystem.

18. The electronic communication network of claim 14, wherein the connectivity subsystem is to add to the network traffic an identifier that identifies the redirection request.

19. The electronic communication network of claim 14, wherein the redirection request requests that network traffic satisfying redirection criteria be redirected to the control subsystem;

and

wherein the connectivity subsystem is to determine whether the network traffic satisfies the redirection criteria and to redirect the network traffic to the control subsystem if the network traffic is determined to satisfy the redirection criteria.

20. The electronic communication network of claim 14, wherein the redirection request requests that the network traffic be redirected in one of an IP address mode, a copy and forward mode, and a redirect mode.

21. The electronic communication network of claim 14, wherein the connectivity subsystem is to:

receive the registration request using a protocol which operates between the control subsystem and the connectivity subsystem,

receive the redirection request using the protocol, and

redirect the network traffic to the control subsystem over a data path.

22. The electronic communication network of claim 14, wherein the connectivity subsystem is to assign a registration identifier to the control subsystem.

23. The electronic communication network of claim 14, wherein the connectivity subsystem is to send a redirection confirmation message to the control subsystem.

24. The electronic communication network of claim 14, wherein the connectivity subsystem is to receive the registration request using SNMP, and receive the redirection request using SNMP.

25. The electronic communication network of claim 14, wherein the electronic communication network comprises a control plane including the control subsystem.

26. The electronic communication network of claim 25, wherein the control plane comprises a plurality of control subsystems.

27. The network of claim 14, wherein the connectivity subsystem operates on a first hardware module of a chassis device, and wherein the control subsystem operates on a second hardware module of the chassis device.

28. The network of claim 14, wherein the connectivity subsystem operates on one stackable module in a plurality of stackable devices, and wherein the control subsystem operates on another stackable module of the plurality of stackable devices.

29. The network of claim 14, wherein the connectivity subsystem operates on one standalone hardware device, and wherein the control subsystem operates on another standalone hardware device.

30. The network of claim 14, wherein both the connectivity subsystem and the control subsystem operate on a single hardware device.

31. The network of claim 30, wherein the connectivity subsystem operates on one CPU core of the single hardware device and wherein the control subsystem operates on another CPU core of the hardware device.

32. The network of claim 30, wherein both the connectivity subsystem and the control subsystem operate on a single CPU core of the hardware device.

33. A connectivity subsystem for use with an electronic communication network, the electronic communication network including a control subsystem, the connectivity subsystem comprising:

a memory storing machine readable instructions to;

receive a registration request from the control subsystem to register the control subsystem with the connectivity subsystem;

register the control subsystem with the connectivity subsystem in response to the registration request;

send a registration confirmation message to the control subsystem, wherein the registration confirmation message includes information related to capabilities of the connectivity subsystem;

receive a redirection request from the control subsystem to redirect network traffic from the connectivity subsystem to the control subsystem; and

redirect the network traffic to the control subsystem in response to the redirection request; and

a processor to implement the machine readable instructions.

34. The connectivity subsystem of claim 33, the machine readable instructions are further to store registration information about the control subsystem in a data store.

35. The connectivity subsystem of claim 33, wherein the machine readable instructions are further to receive the network traffic and send the network traffic to the control subsystem.

36. The connectivity subsystem of claim 35, wherein the the machine readable instructions are further to add to the network traffic an identifier that identifies the redirection request.

37. The connectivity subsystem of claim 35, wherein the redirection request includes redirection criteria;

and

wherein the machine readable instructions are further to determine whether the network traffic satisfies the redirection criteria and send the network traffic to the control subsystem if the network traffic is determined to satisfy the redirection criteria.

38. The connectivity subsystem of claim 37, wherein the redirection request requests that the network traffic be redirected in one of an IP address mode, a copy and forward mode, and a redirect mode.

39. The connectivity subsystem of claim 33, wherein the machine readable instructions are to receive the registration request using a protocol which operates between the control subsystem and the connectivity subsystem, receive the redirection request using the protocol, and redirect the network traffic to the control subsystem over a data path.

40. The connectivity subsystem of claim 33, wherein the machine readable instructions are further to assign a registration identifier to the control subsystem.

41. The connectivity subsystem of claim 33, wherein the machine readable instructions are further to send a redirection confirmation message to the control subsystem.

42. The connectivity subsystem of claim 33, wherein the machine readable instructions are to receive the registration request using SNMP, and receive the redirection request using SNMP.

43. The connectivity subsystem of claim 33, wherein the connectivity subsystem operates on a first hardware module of a chassis device, and wherein the control subsystem operates on a second hardware module of the chassis device.

44. The connectivity subsystem of claim 33, wherein the connectivity subsystem operates on one stackable module in a plurality of stackable devices, and wherein the control subsystem operates on another stackable module of the plurality of stackable devices.

45. The connectivity subsystem of claim 33, wherein the connectivity subsystem operates on one standalone hardware device, and wherein the control subsystem operates on another standalone hardware device.

46. The connectivity subsystem of claim 33, wherein both the connectivity subsystem and the control subsystem operate on a single hardware device.

47. The connectivity subsystem of claim 46, wherein the connectivity subsystem operates on one CPU core of the single hardware device and wherein the control subsystem operates on another CPU core of the hardware device.

48. The connectivity subsystem of claim 46, wherein both the connectivity subsystem and the control subsystem operate on a single CPU core of the hardware device.

49. A control subsystem for use with an electronic communication network, the electronic communication network including a connectivity subsystem, the control subsystem comprising:

a memory storing machine readable instructions to;

send a registration request to the connectivity subsystem to request that the control subsystem be registered with the connectivity subsystem;

receive a registration confirmation message from the connectivity subsystem, wherein the registration confirmation message includes information related to capabilities of the connectivity subsystem; and

send a redirection request requesting that network traffic be redirected from the connectivity subsystem to the control subsystem; and

a processor to implement the machine readable instructions.

50. The control subsystem of claim 49, wherein the machine readable instructions are further to:

receive the redirected network traffic from the connectivity subsystem.

51. The control subsystem of claim 49, wherein the machine readable instructions are to request that network traffic satisfying redirection criteria be redirected to the control subsystem.

52. The control subsystem of claim 49, wherein the machine readable instructions are to request that the network traffic be redirected in one of an IP address mode, a copy and forward mode, and a redirect mode.

53. The control subsystem of claim 49, wherein the machine readable instructions are to send the registration request using a protocol which operates between the control subsystem and the connectivity subsystem;

and wherein the machine readable instructions are to send the redirection request using the protocol.

54. The control subsystem of claim 53, wherein the protocol comprises SNMP.

55. The control subsystem of claim 49, wherein the connectivity subsystem operates on a first hardware module of a chassis device, and wherein the control subsystem operates on a second hardware module of the chassis device.

56. The control subsystem of claim 49, wherein the connectivity subsystem operates on one stackable module in a plurality of stackable devices, and wherein the control subsystem operates on another stackable module of the plurality of stackable devices.

57. The control subsystem of claim 49, wherein the connectivity subsystem operates on one standalone hardware device, and wherein the control subsystem operates on another standalone hardware device.

58. The control subsystem of claim 49, wherein both the connectivity subsystem and the control subsystem operate on a single hardware device.

59. The control subsystem of claim 58, wherein the connectivity subsystem operates on one microprocessor core of the single hardware device and wherein the control subsystem operates on another microprocessor core of the hardware device.

60. The control subsystem of claim 58, wherein the single hardware device comprises a microprocessor core, wherein the connectivity subsystem operates on the microprocessor core, and wherein the control subsystem operates on the microprocessor core.

61. A non-transitory computer-readable medium tangibly embodying processor-executable computer program code, which when executed causes a connectivity subsystem to:

register a control subsystem the connectivity subsystem in an electronic communication network;

send a registration confirmation message to the control subsystem, wherein the registration confirmation message includes information related to capabilities of the connectivity subsystem;

redirect network traffic from the connectivity subsystem to the control subsystem in response to a redirection request from the control subsystem; and

determine which network traffic to redirect to the control subsystem.

62. The non-transitory computer-readable medium of claim 61, wherein the registration confirmation message further comprises a registration identifier associated with the control subsystem.

63. The non-transitory computer-readable medium of claim 61, wherein the computer program code further causes the connectivity subsystem to redirect the network traffic from the connectivity subsystem to the control subsystem in a redirection mode, wherein the redirect mode is one of an IP address mode, a copy and forward mode, and a redirect mode.

64. A non-transitory computer-readable medium storing computer program instructions to:

carry a registration request from a control subsystem to a connectivity subsystem;

carry a registration confirmation message from the connectivity subsystem to the control subsystem, wherein the registration confirmation message includes information related to capabilities of the connectivity subsystem;

carry a traffic redirection request from the control subsystem to the connectivity subsystem; and

carry redirected traffic from the connectivity subsystem to the control subsystem.