IP Library Granted Patent US 7,978,614
Granted Patent B2
US 7,978,614 · App. 11/953,743 · Granted Jul 12, 2011

Techniques for detecting non-receipt of fault detection protocol packets

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,978,614
App. No.
11/953,743
Granted
Jul 12, 2011
Kind
B2
Abstract

Techniques that assist in processing of failure detection protocol (FDP) packets. Techniques are provided that assist a CPU of a network device in processing incoming FDP packets. In one embodiment, a module is provided in a network device for detecting and flagging the non-receipt of FDP packets by the network device for one or more FDP sessions. In this manner, the task of detecting non-receipt of FDP packets is offloaded from the CPU of the network device. This enables the network device to support newer FDPs with shorter periodic interval requirements.

Claims (27)

1. A method performed by a network device of detecting non-receipt of failure detection protocol packets, the method comprising:

storing, at the network device, timer information for each session in a plurality of failure detection protocol sessions, the timer information for each session comprising a first timer specifying a time value indicative of a periodic time interval for receiving a failure detection protocol packet for the session and a second timer specifying a time value indicative of an amount of time since a failure detection protocol packet was last received for the session;

determining, based upon the first timer values specified for the plurality of failure detection protocol sessions, a time period for comparing the timers for the plurality of failure detection protocol sessions;

based upon the determined time period, periodically comparing, for each session in the plurality of failure detection protocol sessions, the first timer value specified in the timer information for the session with the second timer value specified in the timer information for the session; and

determining, based upon the comparing for a first session in the plurality of failure detection protocol sessions, that a failure detection protocol packet for the session is not received by the network device within the periodic time interval specified by the timer information for the first session;

wherein determining the time period comprises setting the time period to a least common denominator of the first timer values specified for the plurality of failure detection protocol sessions;

wherein determining that a failure detection packet is not received is performed by a module of the network device other than a processor of the network device, the processor configured to execute software for processing failure detection protocol packets.

2. The method of claim 1 wherein determining that a failure detection protocol packet is not received for the first failure detection protocol session comprises:

indicating that a failure detection protocol packet is not received within the periodic time interval for the first session when the second timer value for the first session equals or exceeds the first timer value for the first session.

3. The method of claim 1 further comprising, for each session in the plurality of failure detection protocol sessions, resetting the second timer value for the session upon receiving a failure detection protocol packet for that session.

4. The method of claim 1 wherein the first timer value for each session in the plurality of failure detection protocol sessions is set by the software executed by the processor of the network device.

5. The method of claim 1 wherein the first failure detection protocol session is a Bidirectional Forwarding (BFD) protocol session.

6. The method of claim 1 wherein the first failure detection protocol session is an 802.1ag protocol session.

7. A system for detecting non-receipt of failure detection protocol packets, the system comprising:

a processor configured to execute software for processing failure detection protocol packets;

a memory configured to store timer information for each session in a plurality of failure detection protocol sessions, the timer information for each session comprising a first timer specifying a time value indicative of a periodic time interval for receiving a failure detection protocol packet for the session and a second timer specifying a time value indicative of an amount of time since a failure detection protocol packet was last received for the session; and

a module configured to:

determine, based upon the first timer values specified for the plurality of failure detection protocol sessions, a time period for comparing the timers for the plurality of failure detection protocol sessions;

based upon the determined time period, periodically compare, for each session in the plurality of failure detection protocol sessions, the first timer value specified in the timer information for the session with the second timer value specified in the timer information for the session; and

wherein the time period for the comparing is set to a least common denominator of the first timer values specified for the plurality of failure detection protocol sessions;

determine, based upon the comparison for a first session in the plurality of failure detection protocol sessions, that a failure detection protocol packet for the session is not received by the system within the periodic time interval specified by the timer information for the first session.

8. The system of claim 7 wherein the module is configured to indicate that a failure detection protocol packet is not received within the periodic time interval for the first session when the second timer value for the first session equals or exceeds the first timer value for the first session.

9. The system of claim 7 wherein the module is configured to, for each session in the plurality of failure detection protocol sessions, reset the second timer value for the session upon receiving a failure detection protocol packet for that session.

10. The system of claim 7 wherein the first timer value for each session in the plurality of failure detection protocol sessions is set by the software executed by the processor.

11. The system of claim 7 wherein the first failure detection protocol session is a Bidirectional Forwarding (BFD) protocol session.

12. The system of claim 7 wherein the first failure detection protocol session is an 802.1ag protocol session.

13. The system of claim 7 wherein the module is a field-programmable logic device.

Assignments (13)
AMENDED SECURITY AGREEMENT Recorded Aug 18, 2023
From: EXTREME NETWORKS, INC.; AEROHIVE NETWORKS, INC.
To: BANK OF MONTREAL
Reel/Frame 064782/0971 →
SECURITY INTEREST Recorded May 1, 2018
From: EXTREME NETWORKS, INC.
To: BANK OF MONTREAL
Reel/Frame 046050/0546 →
RELEASE OF SECURITY INTEREST Recorded May 1, 2018
From: SILICON VALLEY BANK
To: EXTREME NETWORKS, INC.
Reel/Frame 046051/0775 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 7, 2017
From: BROCADE COMMUNICATIONS SYSTEMS, INC.; FOUNDRY NETWORKS, LLC
To: EXTREME NETWORKS, INC.
Reel/Frame 044054/0678 →
THIRD AMENDED AND RESTATED PATENT AND TRADEMARK SECURITY AGREEMENT Recorded Oct 31, 2017
From: EXTREME NETWORKS, INC.
To: SILICON VALLEY BANK
Reel/Frame 044639/0300 →
RELEASE OF SECURITY INTEREST Recorded Jan 22, 2015
From: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
To: BROCADE COMMUNICATIONS SYSTEMS, INC.; FOUNDRY NETWORKS, LLC
Reel/Frame 034804/0793 →
RELEASE OF SECURITY INTEREST Recorded Jan 21, 2015
From: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
To: BROCADE COMMUNICATIONS SYSTEMS, INC.; INRANGE TECHNOLOGIES CORPORATION; FOUNDRY NETWORKS, LLC
Reel/Frame 034792/0540 →
RELEASE OF SECURITY INTEREST Recorded Jan 21, 2015
From: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
To: BROCADE COMMUNICATIONS SYSTEMS, INC.; FOUNDRY NETWORKS, LLC
Reel/Frame 034784/0609 →
SUPPLEMENTAL PATENT SECURITY AGREEMENT Recorded Sep 26, 2011
From: BROCADE COMMUNICATIONS SYSTEMS, INC.; FOUNDRY NETWORKS, LLC; INRANGE TECHNOLOGIES CORPORATION; MCDATA CORPORATION; MCDATA SERVICES CORPORATION
To: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 026971/0042 →
SUPPLEMENTAL PATENT SECURITY AGREEMENT Recorded Sep 20, 2011
From: BROCADE COMMUNICATIONS SYSTEMS, INC.; FOUNDRY NETWORKS, LLC; MCDATA CORPORATION
To: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 026938/0922 →
CHANGE OF NAME Recorded Jul 21, 2010
From: FOUNDRY NETWORKS, INC.
To: FOUNDRY NETWORKS, LLC
Reel/Frame 024733/0739 →
SECURITY AGREEMENT Recorded Jan 20, 2010
From: BROCADE COMMUNICATIONS SYSTEMS, INC.; FOUNDRY NETWORKS, LLC; INRANGE TECHNOLOGIES CORPORATION; MCDATA CORPORATION; MCDATA SERVICES CORPORATION
To: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 023814/0587 →
SECURITY AGREEMENT Recorded Dec 22, 2008
From: BROCADE COMMUNICATIONS SYSTEMS, INC.; FOUNDRY NETWORKS, INC.; INRANGE TECHNOLOGIES CORPORATION; MCDATA CORPORATION
To: BANK OF AMERICA, N.A. AS ADMINISTRATIVE AGENT
Reel/Frame 022012/0204 →