Methods and arrangements to detect a failure in a communication network
First Claim
1. An apparatus configured to detect failures, the apparatus comprising:
- a traffic generator adapted to generate at least one packet to initiate a data transmission to a communication component of a bundle of communication components, wherein the bundle of communication components is configured to transmit and receive data in parallel via a load-sharing arrangement for a communication device, wherein further communication components of the bundle share at least one network address;
an activity monitor to detect a monitored activity level of the communication component responsive to the at least one packet; and
an activity comparator to compare the monitored activity level against a predetermined activity level and identify the communication component as a failed component if the monitored activity level is below the predetermined level.
0 Assignments
0 Petitions
Accused Products
Abstract
Methods and arrangements to monitor communication components such as a network adapters for activity, and identify components that have lower than normal levels of activity are provided. An identified communication component can become suspect component and a candidate for further testing, including different forms of interrogation. Process for interrogating candidates can include generating and sending test packets having the media access control (MAC) address of the candidate to the candidate and if activity is not detected subsequent to the interrogation, the candidate can be flagged as a failed component. Correspondingly, the component can be deactivated and removed from service. In a further embodiment, a backup component can be activated and assume the role previously held by the failed component.
39 Citations
29 Claims
-
1. An apparatus configured to detect failures, the apparatus comprising:
-
a traffic generator adapted to generate at least one packet to initiate a data transmission to a communication component of a bundle of communication components, wherein the bundle of communication components is configured to transmit and receive data in parallel via a load-sharing arrangement for a communication device, wherein further communication components of the bundle share at least one network address; an activity monitor to detect a monitored activity level of the communication component responsive to the at least one packet; and an activity comparator to compare the monitored activity level against a predetermined activity level and identify the communication component as a failed component if the monitored activity level is below the predetermined level. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A computer program product comprising a computer useable medium having a computer readable program, wherein the computer readable program when executed on a computer causes the computer to:
-
route data to a communication component that shares one Internet protocol address with a plurality of communication components of a bundle, wherein routing the data activates at least a portion of the communication component, wherein further the plurality of communication components of a bundle is configured to transmit and receive data in parallel via a load-sharing arrangement for a communication device; monitor at least the portion of the communication component to determine a monitored activity level responsive to the routed data; compare the monitored activity level to a predetermined activity level; and
identify the communication component as a failed component if the monitored activity level is less than the predetermined activity level. - View Dependent Claims (10)
-
-
11. A method, comprising:
-
monitoring a component of a bundle of components for an aspect of data transmission for the component, wherein the bundle of components is configured to transmit and receive data in parallel via a load-sharing arrangement for a communication device; determining, via the monitored aspect of data transmission, the component is suspect; monitoring the operation of the component based on attempted reception or attempted transmission of a test packet via the component in response to the suspect determination; and flagging the component as a failed component based on the monitored operation. - View Dependent Claims (12, 13, 14, 15, 16, 17, 18, 19, 20, 21)
-
-
22. An apparatus, comprising:
-
an activity monitor configured to determine an activity level of a network adapter during a time interval and configured to monitor activity of the network adapter responsive to at least one test packet, wherein the network adapter is one of a plurality of network adapters in a bundle, wherein further the network adapters of the bundle are configured to operate in parallel via a load-sharing arrangement; an activity comparator to compare the determined activity level to a predetermined activity level, to identify the network adapter as a suspect adapter if the determined activity is less than the predetermined activity level; a traffic generator to transmit the at least one test packet to the suspect adapter; and a flagger to flag the suspect adapter as a failed adapter if the monitored activity is less than a projected activity associated with the at least one test packet. - View Dependent Claims (23, 24, 25)
-
-
26. A system comprising:
-
a plurality of network adapters in a bundle configured to share a data transmission load, wherein the network adapters of the bundle are configured to transmit and receive data in parallel via a load-sharing arrangement for a single network address; a failure detection logic coupled to the plurality of network adapters to measure a number of unsuccessful data transmissions associated with a network adapter in the bundle, to identify the network adapter as a suspect adapter based upon the number, to attempt transmission of a test packet via the suspect adapter or attempt reception of the test packet via the suspect adapter, and to determine whether to mark the suspect adapter as a failed adapter based upon the attempted transmission or attempted reception. - View Dependent Claims (27, 28, 29)
-
Specification