Scalable connectivity fault management in a bridged/virtual private LAN service environment

• US 8,284,678 B2
• Filed: 03/17/2008
• Issued: 10/09/2012
• Est. Priority Date: 10/30/2007
• Status: Active Grant

• Current Assignee: Ericsson AB (Telefonaktiebolaget LM Ericsson)
• Original Assignee: Ericsson AB (Telefonaktiebolaget LM Ericsson)
• Inventors: Kini, Sriganesh, Mehta, Rishi
• Primary Examiner(s): Vu, Huy D
• Assistant Examiner(s): MIAN, OMER S
• Application Number:
  US12/050,121
• Publication Number:
  US 20090109861A1
• Time in Patent Office: 1,667 Days
• Field of Search: 370/241.1, 370/241, 370/242, 370/248, 370/231
• US Class Current: 370/241.1
• CPC Class Codes: H04L 41/06 Management of faults, events, alarms or notifications
• CPC Class Codes: H04L 41/0627 by acting on the notification or alarm source
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: H04L 61/2528 Translation at a proxy

Abstract

A method and apparatus that proxies connectivity check messages and sends fault state changes messages across an MPLS/VPLS network is described. A network element proxies connectivity check messages for remote maintenance endpoints based on a local database. The network element updates the database based on received fault state change message that identify a fault state change of a remote maintenance endpoint. The network element detects fault state changes of local maintenance endpoints and sends a fault state change message to other network elements that proxy connectivity check message for the local maintenance endpoints.

Claims

1. A computerized method performed by a first network element, the method comprising:

detecting, with the first network element according to a first protocol, a fault state change of a local maintenance endpoint, wherein a connectivity status of the local maintenance endpoint is active in response to the first network element periodically receiving connectivity check messages of the first protocol generated by the local maintenance endpoint, and is not active in response to a lack of connectivity check messages received from the local maintenance endpoint, and wherein detecting the fault state change includes detecting the connectivity status of the local maintenance endpoint changing between not active and active;

creating a fault state change message according to a second protocol based on the detected fault state change; and

sending the fault state change message according to the second protocol to a second network element that proxies connectivity check messages of the first protocol to remote maintenance endpoints and maintains a database that represents the connectivity status of the local maintenance endpoint, wherein the first and second protocols are different, and wherein sending the fault state change message includes sending the fault state change message in response to the connectivity status of the local maintenance end point changing from not active to active instead of forwarding the connectivity check messages periodically received by the first network element to the remote maintenance endpoints

wherein the first network element and the second network element are included in the same domain.

2. The method of claim 1, wherein the first protocol is Connectivity Fault Management protocol.

3. The method of claim 1, wherein the second protocol is Virtual Circuit Connectivity Verification protocol.

4. The method of claim 1, wherein information about the fault state change is stored in fields of a Virtual Circuit Connectivity Verification (VCCV) message.

5. The method of claim 1, wherein a maintenance endpoint is one of a personal computer, a server, a bridge, and a switch.

6. A non-transitory machine-readable medium that stores instructions, which when executed by a set of one or more processors, cause said set of processors to perform operations comprising:

detect, with a first network element according to a first protocol, a fault state change of a local maintenance endpoint, wherein a connectivity status of the local maintenance endpoint is active in response to the first network element periodically receiving connectivity check messages of the first protocol generated by the local maintenance endpoint, and is not active in response to a lack of connectivity check messages received from the local maintenance endpoint, and wherein detecting the fault state change includes detecting the connectivity status of the local maintenance endpoint changing between not active and active;

create a fault state change message according to a second protocol based on the detected fault state change; and

send the fault state change message according to the second protocol to a second network element that proxies connectivity check messages of the first protocol to remote maintenance endpoints and maintains a database that represents connectivity status of the local maintenance endpoint, wherein the first and second protocols are different, and wherein sending the fault state change message includes sending the fault state change message in response to the connectivity status of the local maintenance endpoint changing from not active to active instead of forwarding the connectivity check messages periodically received by the first network element to the remote maintenance endpoints

wherein the first network element and the second network element are included in the same domain.

7. The machine-readable medium of claim 6, wherein the first protocol is Connectivity Fault Management protocol.

8. The machine-readable medium of claim 6, wherein the second protocol is Virtual Circuit Connectivity Verification protocol.

9. The machine-readable medium of claim 6, wherein information about the fault state change is stored in fields of a Virtual Circuit Connectivity Verification (VCCV) message.

10. The machine-readable medium of claim 6, wherein a maintenance endpoint is one of a personal computer, a server, a bridge, and a switch.

11. An apparatus comprising:

a first network element to be coupled with a second network element that proxies connectivity check messages to remote maintenance endpoints, the first network element further to be coupled with a set of one or more third network elements, the first network element including;

a connectivity check detection module to detect, according to a first protocol, a fault state change of a local maintenance endpoint on the set of third network elements wherein a connectivity status of the local maintenance endpoint is active in response to the first network element periodically receiving connectivity check messages of the first protocol generated by the local maintenance endpoint, and is not active in response to a lack of connectivity check messages received from the local maintenance endpoint, and wherein detecting the fault state change includes detecting the connectivity status of the local maintenance endpoint changing between not active and active; and

a connectivity check fault state change module to create a fault state change message according to a second protocol based on the detected fault state change and send the fault state change message according to the second protocol to the second network element, and wherein sending the fault state change message includes sending the fault state change message in response to the connectivity status of the local maintenance endpoint changing from not active to active instead of forwarding the connectivity check messages periodically received by the first network element to the remote maintenance endpoints

wherein the first network element and the second network element are included in the same domain.

12. The apparatus of claim 11, wherein the first protocol is Connectivity Fault Management protocol.

13. The apparatus of claim 11, wherein the second protocol is Virtual Circuit Connectivity Verification protocol.

14. The apparatus of claim 11, wherein information about the fault state change is stored in fields of a VCCV message.

15. The apparatus of claim 11, wherein a maintenance endpoint is one of a personal computer, a server, a bridge, and a switch.

16. A network element comprising:

a controller card that controls functions of the network element;

a set of one or more line cards, wherein at least one of the line cards configured to detect, according to a first protocol, a fault state change of a local maintenance endpoint, wherein a connectivity status of the local maintenance endpoint is active in response to the line card periodically receiving connectivity check messages of the first protocol generated by the local maintenance endpoint, and is not active in response to a lack of connectivity check messages received from the local maintenance endpoint, and wherein detecting the fault state change includes detecting the connectivity status of the local maintenance endpoint changing between not active and active;

create a fault state change message according to a second protocol based on the detected fault state change, and

send the fault state change message according to the second protocol to a second network element that proxies messages of the first protocol to remote maintenance endpoints and maintains a database that represents connectivity status of the local maintenance endpoint, wherein the first and second protocols are different, and wherein sending the fault state change message includes sending the fault state change message in response to the connectivity status of the local maintenance endpoint changing from not active to active instead of forwarding the connectivity check messages periodically received by the line card to the remote maintenance endpoints

wherein the first network element and the second network element are included in the same domain.

17. The network element of claim 16, wherein the first protocol is Connectivity Fault Management protocol.

18. The network element of claim 16, wherein the second protocol is Virtual Circuit Connectivity Verification protocol.

19. The network element of claim 16, wherein information about the fault state change is stored in fields of a Virtual Circuit Connectivity Verification (VCCV) message.