IP Library Granted Patent US 9,692,677
Granted Patent B2
US 9,692,677 · App. 13/916,257 · Granted Jun 27, 2017

Implementing multicast link trace connectivity fault management in an Ethernet network

Inventors: Srikanth Keesara (Tewksbury, MA); Deborah Ellen Fitzgerald (Acton, MA)
Assignee: Avaya Inc.
H04L43/10H04L43/0811
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 9,692,677
App. No.
13/916,257
Granted
Jun 27, 2017
Kind
B2
Abstract

Multicast link trace Connectivity Fault Management (CFM) is implemented in an Ethernet network by causing nodes on the network which perform Reverse Path Forwarding Check (RPFC) based on packet Source Address (SA) to not update the packet SA when updating the content of the CFM message. Alternatively multicast CFM is implemented by causing nodes on the network to update the packet SA when the content of the CFM message is updated, but cause a secondary RPFC process to be implemented by a control process in connection with processing the CFM message. The secondary RPFC process is based on a combination of source and content contained in the payload of the CFM message.

Claims (33)

1. A method of implementing multicast link trace connectivity fault management in an Ethernet network, the method comprising:

receiving, at a first node, a connectivity fault management link trace message sent by a second node;

updating a payload portion of the connectivity fault management link trace message with an identifier of the first node to create an updated connectivity fault management link trace message; and

forwarding, by the first node, the updated connectivity fault management link trace message to a third node without updating a source address of the updated connectivity fault management link trace message.

2. The method of claim 1 , wherein the step of receiving the connectivity fault management link trace message by the first node comprises performing a reverse path forwarding check to determine whether the connectivity fault management link trace message arrived on an expected port for the source address of the connectivity fault management link trace message.

3. The method of claim 2 , wherein the step of performing a reverse path forwarding check is implemented in a forwarding plane by comparing a port on which the connectivity fault management link trace message was received with the expected port;

the method further comprising the steps of:

passing the connectivity fault management link trace message and information about the port on which the connectivity fault management link trace message was received to a control process; and

performing a secondary reverse path forwarding check in the control process by determining a source of the connectivity fault management link trace message and comparing the information about the port on which the connectivity fault management link trace message was received with expected port information for the source of the connectivity fault management link trace message.

4. The method of claim 3 , wherein the source information of the connectivity fault management link trace message is determined by reading source information contained in the payload portion of the connectivity fault management link trace message.

5. The method of claim 4 , wherein the source information is an originator ID response address.

6. The method of claim 3 , wherein the source information of the connectivity fault management link trace message is determined by reading a multicast destination address encoding information about the source of the connectivity fault management link trace message.

7. The method of claim 3 , wherein the connectivity fault management link trace message includes a time to live field, the method further including decrementing the time to live field prior to forwarding the updated connectivity fault management link trace message.

8. The method of claim 3 , wherein forwarding occurs before performing the secondary reverse path forwarding check in the control process.

9. The method of claim 3 , wherein forwarding occurs after performing the secondary reverse path forwarding check in the control process.

10. The method of claim 9 , forwarding occurs only if the connectivity fault management link trace message passes the secondary reverse path forwarding check in the control process.

11. The method of claim 1 , wherein the source address is a field of a header of the connectivity fault management link trace message identifying a source MAC address of a node that originated the connectivity fault management link trace message.

12. The method of claim 1 , wherein the payload portion of the connectivity fault management link trace message includes information identifying a node that originated the connectivity fault management link trace message, the method further comprising generating and transmitting a Link Trace Response (CFR) message to the node that originated the connectivity fault management link trace message.

13. The method of claim 1 ,

wherein the payload portion of the connectivity fault management link trace message includes a set of relayed by information elements, and

wherein the step of updating the payload portion of the connectivity fault management link trace message comprises adding a relayed by information element identifying the first node.

14. The method of claim 13 , wherein the relayed by information elements enables a set of nodes that have relayed the connectivity fault management link trace message to be determined.

15. The method of claim 1 , wherein the connectivity fault management link trace message includes a time to live field, the method further including decrementing the time to live field prior to forwarding the updated connectivity fault management link trace message.

16. A network element, comprising:

a memory device storing executable instructions; and

a processor in communication with the memory device, wherein executing the executable instruction by the processor causes the processor to:

provide a forwarding plane configured to implement a Reverse Path Forwarding Check (RPFC) on multicast packets based on a corresponding source address of each of the multicast packets;

wherein each of the multicast packets comprises a respective connectivity fault management link trace message; and

update connectivity fault management link trace messages by adding network element identification information to each of the respective connectivity fault management link trace messages;

wherein the forwarding plane is further configured to forward the updated connectivity fault management link trace messages without changing the source addresses of the updated connectivity fault management link trace messages.

17. The network element of claim 16 , wherein the RPFC enables the network element to determine whether the multicast packets arrived on respective expected ports.

18. The network element of claim 16 , wherein executing the executable instructions by the processor causes the processor to:

decrement time to live fields of the connectivity fault management link trace messages prior to forwarding the updated connectivity fault management link trace messages.

Assignments (13)
AMENDED SECURITY AGREEMENT Recorded Aug 18, 2023
From: EXTREME NETWORKS, INC.; AEROHIVE NETWORKS, INC.
To: BANK OF MONTREAL
Reel/Frame 064782/0971 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001) Recorded May 18, 2023
From: GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT
To: AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC. (FORMER NAME OF AVAYA CLOUD INC.); HYPERQUALITY, INC.; HYPERQUALITY II, LLC; CAAS TECHNOLOGIES, LLC; AVAYA MANAGEMENT L.P.
Reel/Frame 063779/0622 →
RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026 Recorded Apr 26, 2023
From: CITIBANK, N.A., AS COLLATERAL AGENT
To: AVAYA HOLDINGS CORP.; AVAYA INC.; AVAYA MANAGEMENT L.P.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063457/0001 →
RELEASE OF SECURITY INTEREST Recorded May 1, 2018
From: SILICON VALLEY BANK
To: EXTREME NETWORKS, INC.
Reel/Frame 046051/0775 →
SECURITY INTEREST Recorded May 1, 2018
From: EXTREME NETWORKS, INC.
To: BANK OF MONTREAL
Reel/Frame 046050/0546 →
SECURITY INTEREST Recorded Jan 23, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 045124/0026 →
SECURITY INTEREST Recorded Jan 10, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 045034/0001 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001 Recorded Dec 15, 2017
From: CITIBANK, N.A.
To: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS LLC (FORMERLY KNOWN AS OCTEL COMMUNICATIONS CORPORATION); VPNET TECHNOLOGIES, INC.
Reel/Frame 044893/0531 →
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 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 15, 2017
From: AVAYA INC.; AVAYA COMMUNICATION ISRAEL LTD; AVAYA HOLDINGS LIMITED
To: EXTREME NETWORKS, INC.
Reel/Frame 043569/0047 →
SECOND AMENDED AND RESTATED PATENT AND TRADEMARK SECURITY AGREEMENT Recorded Jul 14, 2017
From: EXTREME NETWORKS, INC.
To: SILICON VALLEY BANK
Reel/Frame 043200/0614 →
SECURITY INTEREST Recorded Jan 27, 2017
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS CORPORATION; VPNET TECHNOLOGIES, INC.
To: CITIBANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 041576/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 27, 2013
From: KEESARA, SRIKANTH; FITZGERALD, DEBORAH ELLEN
To: AVAYA, INC.
Reel/Frame 030695/0637 →
Continuity (1)
Related Publication 20140369177A1 · Dec 18, 2014