System, device and method for limiting tunnel traffic in an information communication network
View Patent ↗There is disclosed an apparatus and method for limiting tunnel traffic in a network. Traffic engineering tunnels are used to direct traffic along a predefined path, which may differ from the path that internet protocol (IP) routing would determine. Interior gateway protocol (IGP) cut through will allow the forwarding of all destinations downstream of a tunnel through the tunnel, without the operator needing to specify a forwarding equivalence class (FEC). But congestion in the tunnel and network instability may result from this approach. A solution to these problems is disclosed which limits the traffic in the tunnel to only that with destination addresses of the tunnel's egress router or nodes directly supported thereby. Other solutions are disclosed which allow tunnel traffic to nodes having destination addresses other than those being directly supported by the tunnel's egress router. All of these solutions are achieved in both pre-determined forwarding entry and dynamic packet-by packet embodiments.
1. In an information communication network comprising a head-end device in communication with a tail-end device via a number of routes for routing information to various destinations, a method for limiting traffic volume in a tunnel by said head-end device, the method comprising:
establishing said tunnel to said tail-end device as one of said number of routes;
determining a number of said destinations within a predetermined number of hops of said tail-end device to identify serviced destinations, wherein the predetermined number is at least one; and
selectively routing only information destined for said serviced destinations through said tunnel.
2. The method of claim 1 , wherein said serviced destinations comprise directly-connected hosts/subnets of said tail-end device.
3. The method of claim 1 , further comprising monitoring tunnel utilization, wherein said determining further comprises dynamically increasing said predetermined number of router hops if said tunnel is under-utilized and decreasing said predetermined number of router hops if said tunnel is over-utilized.
4. The method of claim 1 , wherein said serviced destinations comprise said tail-end device.
5. The method of claim 1 , wherein said serviced destinations comprise a destination for which said tunnel is a better route to said destination than a predetermined shortest path route to said destination.
6. The method of claim 5 , wherein said determining comprises:
calculating said shortest path route to said destination;
determining a shortest path route metric associate with said shortest path route;
determining a tunnel metric associated with said tunnel; and
determining from said shortest path route metric and said tunnel metric that said tunnel is a better route to said destination than said shortest path route.
7. The method of claim 1 , wherein said head-end device comprises a link state database, and wherein said determining comprises examining said link state database to determine which of said destinations are serviced by said tail-end device.
8. The method of claim 1 , wherein said tunnel comprises a label switched path from said head-end device to said tail-end device, and wherein said routing comprises affixing to said information a predetermined label associated with said label switched path for label switching of said information from said head-end device to said tail-end device by a number of intermediate devices.
9. The method of claim 1 , wherein said head-end device comprises a forwarding table indicating one of said number of routes for each of said number of destinations, and wherein said determining further comprises indicating said tunnel for each of said serviced destinations in said forwarding table.
10. The method of claim 9 , wherein said routing comprises determining from said forwarding table that said information is associated with said tunnel.
11. The method of claim 1 , further comprising routing information destined for other than said serviced destinations over one of said number of routes other than said tunnel.
12. An apparatus for limiting traffic volume in a tunnel between said apparatus and a tail-end device, said apparatus having a number of routes to said tail-end for routing information to various destinations, the apparatus comprising:
tunnel establishment logic operably coupled to establish said tunnel to said tail-end device as one of said number of routes;
determination logic operably coupled to determine a number of said destinations that are within a predetermined number of hops of said tail-end device to identify serviced destinations, wherein the predetermined number is at least one; and
routing logic operably coupled to selectively route information destined only for said serviced destinations to said tail-end device through said tunnel.
13. The apparatus of claim 12 , wherein said serviced destinations comprise directly-connected hosts/subnets of said tail-end device.
14. The apparatus of claim 12 , further comprising monitoring tunnel utilization, wherein said determination logic is operably coupled to dynamically increase said predetermined number of router hops if said tunnel is under-utilized and decrease said predetermined number of router hops if said tunnel is over-utilized.
15. The apparatus of claim 12 , wherein said serviced destinations comprise said tail-end device.
16. The apparatus of claim 12 , wherein said serviced destinations comprise a destination for which said tunnel is a better route to said destination than a predetermined shortest path route to said destination.
17. The apparatus of claim 16 , wherein said determination logic is operably coupled to calculate said shortest path route to said destination;
determine a shortest path route metric associate with said shortest path route;
determine a tunnel metric associated with said tunnel; and
determine from said shortest path route metric and said tunnel metric that said tunnel is a better route to said destination than said shortest path route.
18. The apparatus of claim 12 , further comprising a link state database, and wherein said determination logic is operably coupled to examine said link state database to determine which of said destinations are serviced by said tail-end device.
19. The apparatus of claim 12 , wherein said tunnel comprises a label switched path from said head-end device to said tail-end device, and wherein said routing logic is operably coupled to affix to said information a predetermined label associated with said label switched path for label switching of said information from said head-end device to said tail-end device by a number of intermediate devices.
20. The apparatus of claim 12 , further comprising a forwarding table indicating one of said number of routes for each of said number of destinations, and wherein said determination logic is operably coupled to indicate said tunnel for each of said serviced destinations in said forwarding table.
21. The apparatus of claim 20 , wherein said routing logic is operably coupled to determine from said forwarding table that said information is associated with said tunnel.
22. The apparatus of claim 12 , wherein said routing logic is operably coupled to route information destined for other than said serviced destinations over one of said number of routes other than said tunnel.
23. A computer-readable medium containing program for controlling a head-end device to limit traffic volume in a tunnel between said apparatus and a tail-end device, said apparatus having a number of routes to said tail-end for routing information to various destinations, the computer program comprising:
tunnel establishment logic programmed to establish said tunnel to said tail-end device as one of said number of routes;
determination logic programmed to determine a number of said destinations that are within a predetermined number of hops of said tail-end device to identify serviced destinations, wherein the predetermined number is at least one; and
routing logic programmed to selectively route only information destined for said serviced destinations to said tail-end device through said tunnel.
24. The computer program of claim 23 , wherein said serviced destinations comprise directly-connected hosts/subnets of said tail-end device.
25. The computer program of claim 23 , further comprising monitoring logic programmed to monitor tunnel utilization, wherein said determination logic is further programmed to dynamically increase said predetermined number of router hops if said tunnel is under-utilized and decrease said predetermined number of router hops if said tunnel is over-utilized.
26. The computer program of claim 23 , wherein said serviced destinations comprise said tail-end device.
27. The computer program of claim 23 , wherein said serviced destinations comprise a destination for which said tunnel is a better route to said destination than a predetermined shortest path route to said destination.
28. The computer program of claim 27 , wherein said determination logic is programmed to calculate said shortest path route to said destination;
determine a shortest path route metric associate with said shortest path route;
determine a tunnel metric associated with said tunnel; and
determine from said shortest path route metric and said tunnel metric that said tunnel is a better route to said destination than said shortest path route.
29. The computer program of claim 28 , wherein said determination logic is programmed to examine a link state database to determine which of said destinations are serviced by said tail-end device.
30. The computer program of claim 23 , wherein said tunnel comprises a label switched path from said head-end device to said tail-end device, and wherein said routing logic is programmed to affix to said information a predetermined label associated with said label switched path for label switching of said information from said head-end device to said tail-end device by a number of intermediate devices.
31. The computer program of claim 23 , further comprising a forwarding table indicating one of said number of routes for each of said number of destinations, and wherein said determination logic is programmed to indicate said tunnel for each of said serviced destinations in said forwarding table.
32. The computer program of claim 31 , wherein said routing logic is programmed to determine from said forwarding table that said information is associated with said tunnel.
33. The computer program of claim 23 , wherein said routing logic is programmed to route information destined for other than said serviced destinations over one of said number of routes other than said tunnel.
34. The computer program of claim 23 embodied in a computer readable medium.
35. The computer program of claim 23 embodied as a data signal.
36. In an information communication network comprising a head-end device in communication with a tail-end device via a number of routes for routing information to various destinations, a method for limiting traffic volume in a tunnel, the method comprising:
establishing said tunnel between said head-end device and said tail-end device as one of said number of routes;
receiving information for a destination by said head-end device;
determining whether said destination is within a predetermined number of hops of said tail-end device to determine whether the destination is a serviced destination, wherein the predetermined number is greater than or equal to one; and
selectively routing said information by said head-end device to said tail-end device over said tunnel, if and only if said destination is a serviced destination.
37. The method of claim 36 , wherein determining whether said destination is serviced by said tail-end device comprises determining whether said destination is a directly-connected host/subnet of said tail-end device.
38. The method of claim 36 , further comprising monitoring tunnel utilization, wherein said determining further comprises dynamically increasing said predetermined number of router hops if said tunnel is under-utilized and decreasing said predetermined number of router hops if said tunnel is over-utilized.
39. The method of claim 36 , wherein said destination is serviced by said tail-end device comprises determining whether said destination is said tail-end device.
40. The method of claim 36 , wherein determining whether said destination is serviced by said tail-end device comprises:
calculating a shortest path route to said destination;
determining a shortest path route metric associate with said shortest path route;
determining a tunnel metric associated with said tunnel; and
determining from said shortest path route metric and said tunnel metric that said tunnel is a better route to said destination than said shortest path route;
said serviced destinations comprise a destination for which said tunnel is a better route to said destination than a predetermined shortest path route to said destination.
41. The method of claim 36 , wherein said head-end device comprises a link state database, and wherein said determining comprises examining said link state database to determine which of said destinations are serviced by said tail-end device.
42. The method of claim 36 , wherein said tunnel comprises a label switched path from said head-end device to said tail-end device, and wherein said routing comprises affixing to said information a predetermined label associated with said label switched path for label switching of said information from said head-end device to said tail-end device by a number of intermediate devices.
43. The method of claim 42 , wherein said routing further comprises said tail-end device removing said label from said information and forwarding said information to said destinations based upon destination address information in said information.
44. The method of claim 36 , further comprising routing said information by said head-end device to said tail-end device over one of said routes other than said tunnel, if and only if said destination is not serviced by said tail-end device.
45. An apparatus for limiting traffic volume in a tunnel between said apparatus and a tail-end device, said apparatus having a number of routes to said tail-end for routing information to various destinations, the apparatus comprising:
tunnel establishment logic operably coupled to establish said tunnel to said tail-end device as one of said number of routes;
receiving logic operably coupled to receive information for a destination;
determination logic operably coupled to determine whether said destination is serviced by said tail-end device responsive to said destination being within a predetermined number of hops of said tail-end device, wherein the predetermined number is at least one; and
routing logic operably coupled to selectively route said information to said tail-end device through said tunnel if and only if said destination is service by said tail-end device.
46. The apparatus of claim 45 , wherein said determination logic is operably coupled to determine whether said destination is a directly-connected host/subnet of said tail-end device.
47. The apparatus of claim 45 , further comprising monitoring logic operably coupled to monitor tunnel utilization, wherein said determination logic is operably coupled to dynamically increase said predetermined number of router hops if said tunnel is under-utilized and decrease said predetermined number of router hops if said tunnel is over-utilized.
48. The apparatus of claim 45 , wherein said determination logic is operably coupled to determine whether said destination is said tail-end device.
49. The apparatus of claim 45 , wherein said determination logic is operably coupled to calculate said shortest path route to said destination, determine a shortest path route metric associate with said shortest path route, determine a tunnel metric associated with said tunnel, and determine from said shortest path route metric and said tunnel metric that said tunnel is a better route to said destination than said shortest path route.
50. The apparatus of claim 45 , further comprising a link state database, wherein said determination logic is operably coupled to examine said link state database to determine which of said destinations are serviced by said tail-end device.
51. The apparatus of claim 45 , wherein said tunnel comprises a label switched path to said tail-end device, and wherein said routing logic is operably coupled to affix to said information a predetermined label associated with said label switched path for label switching of said information from said head-end device to said tail-end device by a number of intermediate devices.
52. The apparatus of claim 45 , wherein said routing logic is operably coupled to route said information to said tail-end device over one of said routes other than said tunnel, if and only if said destination is not serviced by said tail end device.
53. A computer-readable medium containing program for controlling a head-end device to limit traffic volume in a tunnel between said head-end device and a tail-end device, said head-end device having a number of routes to said tail-end for routing information to various destination, the computer program comprising:
tunnel establishment logic programmed to establish said tunnel to said tail-end device as one of said number of routes;
receiving logic programmed to receive information for a destination;
determination logic programmed to determine whether said destination is serviced by said tail-end device responsive to the destination being within a predetermined number of hops of the tail-end device, wherein the predetermined number is at least one; and
routing logic programmed to selectively route said information to said tail-end device through said tunnel if and only if said destination is serviced by said tail-end device.
54. The apparatus of claim 53 , wherein said determination logic is programmed to determine whether said destination is a directly-connected host/subnet of said tail-end device.
55. The computer program of claim 53 , further comprising monitoring logic programmed to monitor tunnel utilization, wherein said determination logic is programmed to dynamically increase said predetermined number of router hops if said tunnel is under-utilized and decrease said predetermined number of router hops if said tunnel is over-utilized.
56. The computer program of claim 54 , wherein said determination logic is programmed to determine whether said destination is said tail-end device.
57. The computer program of claim 54 , wherein said determination logic is programmed to calculate said shortest path route to said destination;
determine a shortest path route metric associate with said shortest path route;
determine a tunnel metric associated with said tunnel; and
determine from said shortest path route metric and said tunnel metric that said tunnel is a better route to said destination than said shortest path route.
58. The computer program of claim 54 , wherein said determination logic is programmed to examine a link state database to determine which of said destinations are serviced by said tail-end device.
59. The computer program of claim 54 , wherein said tunnel comprises a label switched path from said head-end device to said tail-end device, and wherein said routing logic is programmed to affix to said information a predetermined label associated with said label switched path for label switching of said information from said head-end device to said tail-end device by a number of intermediate devices.
60. The computer program of claim 54 , wherein said routing logic is programmed to route said information to said tail-end device over one of said routes other than said tunnel, if and only if said destination is not serviced by said tail end device.
61. The computer program of claim 54 embodied in a computer readable medium.
62. The computer program of claim 54 embodied as a data signal.
63. A communication system comprising a head-end device in communication with a tail-end device via a number of routes including a tunnel for routing information to various destinations, wherein said head-end device is operably coupled to determine a number of said destinations that are serviced by said tail-end device and route information to said serviced destinations over said tunnel, wherein destinations are determined to be serviced by said tail-end device responsive to the destinations being within a predetermined number of hops of the tail-end device, wherein the predetermined number is at least one.
64. The communication system of claim 63 , wherein said serviced destinations comprise directly-connected hosts/subnets of said tail-end device.
65. The communication system of claim 63 , wherein said serviced destinations comprise said tail-end device.
66. The communication system of claim 63 , wherein said serviced destinations comprise a destination for which said tunnel is a better route to said destination than a predetermined shortest path route to said destination.
67. The communication system of claim 63 , wherein said tunnel comprises a label switched path from said head-end device to said tail-end device.
68. The communication system of claim 67 , wherein said head-end device is operably coupled to affix to said information a predetermined label associated with said label switched path for label switching of said information from said head-end device to said tail-end device by a number of intermediate devices, and wherein said tail-end device is operably coupled to remove said label from said information and forward said information to said destinations based upon destination address information in said information.
69. The communication system of claim 63 , wherein said head-end device is operably coupled to route information destined for other than said serviced destinations over one of said number of routes other than said tunnel.