IP Library Granted Patent US 7,500,014
Granted Patent B1
US 7,500,014 · App. 10/431,010 · Granted Mar 3, 2009

Network link state mirroring

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,500,014
App. No.
10/431,010
Granted
Mar 3, 2009
Kind
B1
Abstract

Methods, apparatuses and systems allowing for network link state mirroring in intermediate network devices. A variety of intermediate network devices disposed between two network devices are operationally transparent to the two network devices. For example, a bandwidth management device disposed between a gateway router and a LAN hub or switch, is operationally transparent, to both network devices since the bandwidth management device, pacing or otherwise controlling packet flows, does not alter the essential routing or switching functions of the devices. The present invention promotes or enhances this operational transparency by mirroring the link state detected at a first network interface on other network interfaces. This functionality is highly useful in today's network topologies where information regarding failure of a link can be used to re-route traffic, alert a network administrator, and the like.

Claims (46)

1. An apparatus comprising

a first network interface for communication with a first network device;

a second network interface for communication with a second network device; and

a control module operative to

detect, at the first network interface, a link failure corresponding to a link between the first network interface and a first network device; and

responsive to the detected link failure, functionally disable the second network interface to simulate to the second network device the link failure between the first network interface and the first network device.

2. The apparatus of claim 1 wherein the first network interface is a wired network interface.

3. The apparatus of claim 1 wherein the first network interface is a wireless network interface.

4. The apparatus of claim 1 wherein the control module comprises a link state demon operative to

detect a link failure at the first or second network interface, and

in response to a detected link failure at the first network interface, change the configuration of the second network interface to functionally disable the second network interface.

5. The apparatus of claim 1 wherein the control module is operative to physically bring down the second network interface in response to a detected link failure on the first network interface.

6. The apparatus of claim 1 wherein the control module is operative to ignore packets received at the second network interface in response to a detected link failure on the first network interface.

7. The apparatus of claim 1 wherein the first network device is a router.

8. The apparatus of claim 7 wherein the second network device is a switch.

9. In an intermediate network device comprising a first network interface connected to a first remote system, and a second network interface connected to a second remote system, a method comprising

detecting, at the first network interface of the intermediate network device, a link failure to the first remote system; and

responsive to the detected link failure, functionally disabling the second network interface of the intermediate network device, to simulate the link failure to the second remote system operably connected to the second network interface.

10. The method of claim 9 wherein the first network interface is a wired network interface.

11. The method of claim 9 wherein the first network interface is a wireless network interface.

12. The method of claim 9 wherein the functionally disabling step comprises bringing down the second network interface in response to a detected failure of the link to the first remote system.

13. The method of claim 9 wherein the functionally disabling step comprises ignoring messages received at the second network interface in response to a detected failure of the link to the first remote system.

14. A bandwidth management device operative to serve as an intermediate network device, comprising

a first network interface for communication with a first network device;

a second network interface for communication of data with a second network device;

a bandwidth management module operably connected to the first and second network interfaces, wherein the bandwidth management module is operative to

receive data flows at the first and second network interfaces,

associate traffic types to the data flows, and

enforce bandwidth utilization controls on the data flows associated with corresponding traffic types; and

a link state demon operative to

detect, at the first network interface, an intercommunication failure between the first network interface and a first network device; and

change the configuration of the bandwidth management module to functionally disable the second network interface, to simulate the failure of the link between the first network interface and the first network device.

15. The bandwidth management device of claim 14 wherein the bandwidth management module is operative to maintain an interface status attribute for each of the first and second network interfaces, and wherein the link failure demon is operative to change the interface status attributes associated with the first and second network interfaces in response to detected intercommunication failures in the first interface.

16. The bandwidth management device of claim 15 wherein the bandwidth management module is responsive to changes in the interface status attributes.

17. The bandwidth management device of claim 14 wherein the link state demon is operative to bring down the second network interface in response to a detected failure of the link associated with the first network interface.

18. The bandwidth management device of claim 14 wherein the link state demon is operative to change the configuration of the bandwidth management module to ignore packets received at the second network interface in response to a detected link failure on the first network interface.

19. An intermediate network device operative to initiate a response to communication failures detected on a network interface, comprising

an inside network interface for communication with a network device,

at least two outside network interfaces, each for communication with the network device,

a control module operative to:

receive data flows at the inside interface,

associate a traffic type to the data flows,

distribute the data flows to one of the at least two outside network interfaces based on the associated traffic type,

detect failures of the at least two outside interfaces, and

functionally disable the inside network interface relative to a select outside interface by ignoring data flows received at the inside interface corresponding to the select outside network interface in response to a intercommunication failure detected at the select outside network interface of the at least two outside interfaces.

20. The apparatus of claim 5 wherein the control module is operative to physically shut down the hardware of the second network interface in response to the detected link failure at the first network interface.

Assignments (8)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 21, 2019
From: SYMANTEC CORPORATION
To: CA, INC.
Reel/Frame 051144/0918 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 27, 2016
From: BLUE COAT SYSTEMS, INC.
To: SYMANTEC CORPORATION
Reel/Frame 039851/0044 →
RELEASE OF SECURITY INTEREST Recorded Aug 1, 2016
From: JEFFERIES FINANCE LLC
To: BLUE COAT SYSTEMS, INC.
Reel/Frame 039516/0929 →
RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL AT REEL/FRAME NO. 30740/0181 Recorded May 29, 2015
From: JEFFERIES FINANCE LLC
To: BLUE COAT SYSTEMS, INC.
Reel/Frame 035797/0280 →
RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL AT REEL/FRAME NO. 27727/0144 Recorded May 29, 2015
From: JEFFERIES FINANCE LLC
To: BLUE COAT SYSTEMS, INC.
Reel/Frame 035798/0006 →
SECURITY INTEREST Recorded May 22, 2015
From: BLUE COAT SYSTEMS, INC.
To: JEFFERIES FINANCE LLC, AS THE COLLATERAL AGENT
Reel/Frame 035751/0348 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Jul 3, 2013
From: BLUE COAT SYSTEMS, INC.
To: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 030740/0181 →
RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL RECORDED AT R/F 027727/0178 Recorded Oct 16, 2012
From: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT
To: BLUE COAT SYSTEMS, INC.
Reel/Frame 029140/0170 →