PACKET LOSS MEASUREMENT AT SERVICE ENDPOINTS OF A VIRTUAL PRIVATE LAN SERVICE

• US 20120236734A1
• Filed: 03/16/2011
• Published: 09/20/2012
• Est. Priority Date: 03/16/2011
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Sampath, Prabakaran Thirumali, Goli, Sri
• Granted Patent: US 8,665,739 B2
• Time in Patent Office: Days
• US Class Current: 370/252
• CPC Class Codes: H04L 12/413 with random access, e.g. carrier-sense multiple-access with collision detection [CSMA-CD]
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 12/4641 Virtual LANs, VLANs, e.g. virtual private networks [VPN] LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272
• CPC Class Codes: H04L 43/0829 Packet loss

Abstract

In general, techniques are described for measuring packet data unit (PDU) loss in a L2 virtual private network (L2VPN) service, such as a VPLS instance. In one example of the techniques, provider edge (PE) routers that participate in the L2VPN measure known unicast and multicast PDU traffic at the service endpoints for the instance to determine unicast PDU loss within the service provider network. As the routers learn the outbound service (i.e., core-facing) interfaces and outbound local (i.e., customer-facing) interfaces for L2 addresses of customer devices that issue packets to the VPLS instance, the routers establish respective unicast transmit and receipt counters for the service endpoints that serve the customer devices. In another example, PE routers that participate in the L2VPN measure multicast PDU traffic at the service endpoints for the instance and account for internal replication by intermediate service nodes to determine multicast PDU loss within the service.

Claims

1. A method comprising:

switching layer two (L2) packet data units (PDUs) with a local network device between a local L2 network, coupled by an attachment circuit for a Virtual Private Local Area Network (LAN) Service (VPLS) instance to the local network device, and one or more remote L2 networks to provide the VPLS instance to the local and remote L2 networks, wherein the local network device terminates one or more pseudowires that operate over a layer three (L3) packet-switched network (PSN) to carry the PDUs in pseudowire packets to connect, for the VPLS instance, the local network device to one or more corresponding remote network devices that each serves a corresponding one of the remote L2 networks; and

incrementing, with the local network device, a respective unicast receipt counter for each of one or more remote service endpoints of the VPLS instance only for the PDUs that are known unicast PDUs within the respective remote network device of the corresponding remote service endpoint from which the PDU was received, wherein each of the known unicast PDUs received by the local network device is a unicast PDU that includes an indicator that the remote network device from which the unicast PDU was received currently maps the destination L2 address of the unicast PDU to a corresponding outbound interface of the remote network device.

2. The method of claim 1, further comprising:

incrementing, with the local network device, a respective unicast transmit counter for each of one or more remote service endpoints of the VPLS instance only for the PDUs that are known unicast PDUs that the local network device sends to the corresponding remote service endpoints, wherein the known unicast PDUs sent by the local network device are unicast PDUs having destination L2 addresses currently mapped to a corresponding outbound interfaces of the local network device;

determining, with the local network device, unicast PDU loss measurement data between a local service endpoint of the local network device for the VPLS instance and the one or more remote service endpoints based at least on the respective unicast transmit counter and unicast receipt counter values for the each of the one or more remote service endpoints; and

sending the unicast PDU loss measurement data from the local network device to a management entity.

3. The method of claim 2, further comprising:

receiving a first PDU with the local network device from the local L2 network;

determining whether the first PDU is a known unicast PDU within the local network device;

only when the first PDU is known unicast, attaching a shim header to the first PDU to mark the first PDU as known unicast and outputting the first PDU with the attached shim header over a core-facing pseudowire selected according to the VPLS instance.

4. The method of claim 3,

wherein determining whether the first PDU is a known unicast PDU within the local network device comprises determining whether a Media Access Control (MAC) table of the local network device maps a destination L2 address of the first PDU to an outbound interface of the local network device.

5. The method of claim 3,

wherein the shim header comprises a service endpoint identifier (SEID) that uniquely identifies the local service endpoint of the local network device.

6. The method of claim 5, further comprising:

incrementing, with the local network device, a unicast transmit counter for a remote SEID that uniquely identifies one of the remote service endpoints of the remote network device that serves the customer device having the destination L2 address of the first PDU only when the first PDU is known unicast.

7. The method of claim 3, further comprising:

receiving a second PDU with the local network device from a core-facing pseudowire; and

determining, with the local network device, the second PDU is known unicast within a remote network device that comprises an ingress one of the remote service endpoints for the second PDU.

8. The method of claim 7,

wherein determining, with the local network device, the second PDU is known unicast within the remote network device comprises determining the second PDU includes an attached shim header that marks the second PDU as known unicast within the remote network device.

9. The method of claim 8,

wherein the shim header comprises a remote service endpoint identifier (SEID) that uniquely identifies one of the remote service endpoints of the remote network device among a plurality of service endpoints for the VPLS instance, the method further comprising:

incrementing, with the local network device, a unicast receipt counter for the remote SEID only when the second PDU includes the shim header.

10. The method of claim 2, further comprising:

receiving, with the local network device, a remote unicast receipt counter value for the local service endpoint from a remote network device comprising a first one of the remote service endpoints, wherein the remote unicast receipt counter value is a number of known unicast PDUs received by the first one of the remote service endpoint from the local service endpoint; and

receiving, with the local network device, a remote unicast transmit counter value for the local service endpoint from the remote network device, wherein the remote unicast transmit counter value is a number of known unicast PDUs transmitted by the first one of the remote service endpoints to the local service endpoint,

wherein determining unicast PDU loss measurement data comprises computing a near-end unicast PDU loss between the local service endpoint and the first one of the remote service endpoints as a difference between the remote unicast transmit counter value and the unicast receipt counter value for the first one of the remote service endpoints,

wherein determining unicast PDU loss measurement data comprises computing a far-end unicast PDU loss between the local service endpoint and the remote service endpoint as a difference between the remote unicast receipt counter value and a respective transmit counter value for the first one of the remote service endpoints, and

wherein sending the unicast PDU loss measurement data from the local network device to the management entity comprises sending the near-end unicast PDU loss measurement data and the far-end unicast PDU loss measurement data.

11. The method of claim 10, further comprising:

receiving the remote unicast receipt counter value and the remote unicast transmit counter value with the local network device in a loss measurement reply (LMR) message generated in accordance with a Loss Measurement Message (LMM) protocol.

12. The method of claim 11, further comprising:

sending the unicast transmit counter value for the remote service endpoint from the local network device to the remote network device in a loss measurement message (LMM) generated in accordance with the LMM protocol.

13. A method comprising:

switching layer two (L2) packet data units (PDUs) with a local network device between a local L2 network, coupled by an attachment circuit for a Virtual Private Local Area Network (LAN) Service (VPLS) instance to the local network device, and one or more remote L2 networks to provide the VPLS instance to the local and remote L2 networks, wherein the local network device terminates one or more pseudowires that operate over a layer three (L3) packet-switched network (PSN) to carry the PDUs in pseudowire packets to connect, for the VPLS instance, the local network device to one or more corresponding remote network devices that each serves a corresponding one of the remote L2 networks;

incrementing, with the local network device, a multicast PDU transmit counter for each multicast PDU or broadcast PDU received from the attachment circuit and switched by the local network device to the one or more remote network devices;

receiving, with the local network device, a respective multicast PDU receipt return value from each of the one or more remote network devices;

determining, with the local network device, multicast PDU loss measurement data based at least on a multicast PDU transmit counter value and the multicast PDU receipt return values; and

sending the multicast PDU loss measurement data from the local network device to a management entity.

14. The method of claim 13, further comprising:

accumulating, with the local network device, the multicast PDU receipt return values to determine an accumulated value; and

determining, with the local network device, the multicast PDU loss measurement data as a difference between the multicast PDU transmit counter value and the accumulated value.

15. The method of claim 13, further comprising:

issuing a multicast loss measurement message from the local network device to the one or more remote network devices, wherein the multicast loss measurement message specifies a replication factor for the VPLS instance at the local network device that defines a number of the one or more pseudowires terminated by the local network device.

16. The method of claim 13,

wherein at least one of the remote network devices that participates in the VPLS instance is not a member of a loss measurement domain for the VPLS instance, the method further comprising:

issuing a multicast loss measurement message from the local network device to the one or more remote network devices, wherein the multicast loss measurement message specifies a loss measurement domain identifier for the loss measurement domain, and wherein the multicast loss measurement message specifies a replication factor for the VPLS instance at the local network device that defines a number of the one or more pseudowires terminated by the local network device and by one of the one or more remote network devices that is a member of the loss measurement domain.

17. The method of claim 13,

wherein the respective multicast PDU receipt return values from each of the one or more remote network devices define a number of multicast or broadcast PDUs transmitted by the local network device and received by the corresponding remote network device, the method further comprising:

accumulating, with the local network device, the respective multicast PDU receipt return values to determine an accumulated value;

dividing the accumulated value by a replication factor for the VPLS instance at the local network device that defines a number of the one or more pseudowires terminated by the local network device to determine a quotient value; and

determining, with the local network device, the multicast PDU loss measurement data as a difference between the multicast PDU transmit counter value and the quotient value.

18. A network device comprising:

a control unit having one or more processors;

one or more interface cards;

a Virtual Private Local Area Network (LAN) Service (VPLS) layer of the control unit that switches layer two (L2) packet data units (PDUs) between a local L2 network, coupled by an attachment circuit for a VPLS instance to one of the interface cards, and one or more remote L2 networks to provide the VPLS instance to the local and remote L2 networks, wherein the network device terminates one or more pseudowires that operate over a layer three (L3) packet-switched network (PSN) to carry the PDUs in pseudowire packets to connect, for the VPLS instance, the network device to one or more corresponding remote network devices that each serves a corresponding one of the remote L2 networks; and

an accounting module of the control unit that increments a respective unicast transmit counter for each of one or more remote service endpoints of the VPLS instance only for the PDUs that are known unicast PDUs within the VPLS layer that the network device sends to the corresponding remote service endpoints from which the PDU was received, wherein each of the known unicast PDUs received by the local network device is a unicast PDU that includes an indicator that the remote network device from which the unicast PDU was received currently maps the destination L2 address of the unicast PDU to a corresponding outbound interface of the remote network device.

19. The network device of claim 18,

wherein the accounting module increments a respective unicast receipt counter for each of one or more remote service endpoints of the VPLS instance only for the PDUs that are known unicast PDUs that the network device receives from the corresponding remote service endpoints that are known unicast PDUs within the respective remote network devices of the corresponding remote service endpoints, wherein the known unicast PDUs sent by the local network device are unicast PDUs having destination L2 addresses currently mapped to a corresponding outbound interfaces of the local network device, the network device further comprising:

a loss measurement module of the control unit that determines unicast PDU loss measurement data between a local service endpoint of the network device for the VPLS instance and the one or more remote service endpoints based at least on the respective unicast transmit counter and unicast receipt counter values for the each of the one or more remote service endpoints; and

a management interface of the control unit that sends the unicast PDU loss measurement data to a management entity.

20. The network device of claim 19,

wherein the interface cards receive a first PDU from the local L2 network on the attachment circuit, the network device further comprising:

a loss measurement PDU handler of the control unit that determines whether the first PDU is a known unicast PDU and, only when the first PDU is known unicast, attaches a shim header to the first PDU to mark the first PDU as known unicast,

wherein the VPLS layer switches the first PDU with the attached shim header over a core-facing pseudowire selected according to the VPLS instance.

21. The network device of claim 20, further comprising:

a MAC table for the VPLS instance that maps learned L2 addresses of customer devices of the customer networks to interfaces of the network device,

wherein the loss measurement PDU handler determines whether the MAC table of the network device maps a destination L2 address of the first PDU to one of the interfaces of the network device.

22. The network device of claim 20,

wherein the shim header comprises a service endpoint identifier (SEID) that uniquely identifies the local service endpoint of the network device.

23. The network device of claim 22,

wherein the accounting module increments a unicast transmit counter for a remote SEID that uniquely identifies one of the remote service endpoints of the remote network device that serves the customer device having the destination L2 address of the first PDU only when the first PDU is known unicast.

24. The network device of claim 20,

wherein the interface cards receive a second PDU from a core-facing pseudowire, and

wherein the loss measurement PDU handler determines whether the second PDU is known unicast within a remote network device that comprises an ingress remote service endpoint for the second PDU.

25. The network device of claim 24,

wherein the loss measurement PDU handler determines the second PDU is known unicast within a remote network device by determining the second PDU includes an attached shim header that marks the second PDU as known unicast within the remote network device.

26. The network device of claim 25,

wherein the shim header comprises a remote service endpoint identifier (SEID) that uniquely identifies the ingress service endpoint of the remote network device among a plurality of service endpoints for the VPLS instance, and

wherein the accounting module increments a unicast receipt counter for the remote SEID only when the second PDU includes the shim header.

27. The network device of claim 19, further comprising:

a loss measurement message handler of the control unit that receives a remote unicast receipt counter value for the local service endpoint from a remote network device, wherein the remote unicast receipt counter value is a number of known unicast PDU received by the remote network device from the local service endpoint,

wherein the loss measurement message handler receives a remote unicast transmit counter value for the local service endpoint from the remote network device, wherein the remote unicast transmit counter value is a number of known unicast PDUs transmitted by the first one of the remote service endpoints to the local service endpoint,

wherein the loss measurement module determines unicast PDU loss measurement data by computing a near-end unicast PDU loss between the local service endpoint and the first one of the remote service endpoints as a difference between the remote unicast transmit counter value and the unicast receipt counter value for the first one of the remote service endpoints,

wherein the loss measurement module determines unicast PDU loss measurement data by computing a far-end unicast PDU loss between the local service endpoint and the remote service endpoint as a difference between the remote unicast receipt counter value and a respective transmit counter value for the first one of the remote service endpoints, and

wherein the management interface sends the unicast PDU loss measurement data from the local network device to the management entity comprises sending the near-end unicast PDU loss measurement data and the far-end unicast PDU loss measurement data.

28. The network device of claim 27, further comprising:

a connectivity fault management module of the control unit that includes a maintenance entity endpoint (MEP),

wherein the MEP receives the remote unicast receipt counter value and the remote unicast transmit counter value in a loss measurement reply (LMR) message generated in accordance with a Loss Measurement Message (LMM) protocol.

29. The network device of claim 28,

wherein the MEP sends the transmit unicast counter value for the first one of the remote service endpoints to the remote network device in a loss measurement message (LMM) generated in accordance with the LMM protocol.

30. A network device comprising:

a control unit having one or more processors;

one or more interface cards;

a Virtual Private Local Area Network (LAN) Service (VPLS) layer of the control unit to switch layer two (L2) packet data units (PDUs) between a local L2 network, coupled by an attachment circuit for a VPLS instance to one of the interface cards, and one or more remote L2 networks to provide the VPLS instance to the local and remote L2 networks, wherein the network device terminates one or more pseudowires that operate over a layer three (L3) packet-switched network (PSN) to carry the PDUs in pseudowire packets to connect, for the VPLS instance, the network device to one or more corresponding remote network devices that each serves a corresponding one of the remote L2 networks;

an accounting module of the control unit that increments a multicast PDU transmit counter for each multicast PDU or broadcast PDU received from the attachment circuit and switched by the VPLS layer to the one or more remote network devices;

a loss measurement message handler that receives a multicast PDU receipt return value from each of the one or more remote network devices,

wherein the accounting module determines multicast PDU loss measurement data based at least on a multicast PDU transmit counter value and the respective multicast PDU receipt return values; and

a management interface that sends the multicast PDU loss measurement data to a management entity.

31. The network device of claim 30,

wherein the loss measurement module accumulates the multicast PDU receipt return values to determine an accumulated value and determines the multicast PDU loss measurement data as a difference between the multicast PDU transmit counter value and the accumulated value.

32. The network device of claim 30,

wherein the loss measurement message handler issues a multicast loss measurement message to the one or more remote network devices, wherein the multicast loss measurement message specifies a replication factor for the VPLS instance that defines the number of the one or more pseudowires terminated by the network device.

33. The network device of claim 30,

wherein at least one of the remote network devices that participates in the VPLS instance is not a member of a loss measurement domain for the VPLS instance, and

wherein the loss measurement message handler issues a multicast loss measurement message to the one or more remote network devices, wherein the multicast loss measurement message specifies a loss measurement domain identifier for the loss measurement domain, and wherein the multicast loss measurement message specifies a replication factor for the VPLS instance that defines the number of the one or more pseudowires terminated by the network device and by one of the one or more remote network devices that is a member of the loss measurement domain.

34. The network device of claim 30,

wherein the respective multicast PDU receipt return values from each of the one or more remote network devices define a number of multicast or broadcast PDUs transmitted by the network device and received by the corresponding remote network device,

wherein the loss measurement module accumulates the respective multicast PDU receipt return values to determine an accumulated value,

wherein the loss measurement module divides the accumulated value by a replication factor for the VPLS instance that defines a number of the one or more pseudowires terminated by the network device to determine a quotient value, and

wherein the loss measurement module determines the multicast PDU loss measurement data as a difference between the multicast PDU transmit counter value and the quotient value.

35. A system comprising:

a network management system;

a local network device and one or more remote network devices that participate in a Virtual Private Local Area Network (LAN) Service (VPLS) instance to switch layer two (L2) packet data units (PDUs) between a local L2 network, coupled by an attachment circuit for a VPLS instance to the local network device, and one or more remote L2 networks to provide the VPLS instance to the local and remote L2 networks, wherein the local network device terminates one or more pseudowires that operate over a layer three (L3) packet-switched network (PSN) to carry the PDUs in pseudowire packets to connect, for the VPLS instance, the local network device to the one or more corresponding remote network devices that each serves a corresponding one of the remote L2 networks,

wherein the local network device increments a multicast PDU transmit counter for each multicast PDU or broadcast PDU received from the attachment circuit and switched by the local network device to the one or more remote network devices,

wherein each of the one or more remote network devices increment a respective multicast PDU receipt counter for the local network device for each multicast PDU or broadcast PDU received from the local network device,

wherein the local network device issues a multicast loss measurement message from the local network device to the one or more remote network devices,

wherein each of the one or more remote network devices returns a respective return value based at least on a respective multicast PDU receive counter value for the local network device,

wherein the local network device receives the return values from the one or more remote network devices and computes multicast PDU loss measurement data based at least on the return values and a multicast PDU transmit counter value, and

wherein the local network device sends the multicast PDU loss measurement data to the network management system.

36. The system of claim 35,

wherein the multicast loss measurement message issued by the local network device specifies a replication factor for the VPLS instance that defines a number of the one or more pseudowires terminated by the local network device, and

wherein the one or more remote network devices compute respective return values based at least on the replication factor.

37. The system of claim 36, wherein the one or more remote network devices compute respective return values by computing a quotient of the respective multicast PDU receive counter value for the local network device and the replication factor.

38. The system of claim 35,

wherein the VPLS instance is a hierarchical VPLS (H-VPLS) instance, the system further comprising:

one or more hub routers interconnected by one or more hub links in a hub for the H-VPLS instance, wherein each of the one or more hub routers is connected to one or more of the remote network devices or the local network device with a respective spoke pseudowire,

wherein an entrance one of the hub routers receives the multicast loss measurement message issued by the local network device and adds an entrance replication factor to the multicast loss measurement message that specifies a number hub pseudowires for the H-VPLS instance terminated by the entrance one of the hub routers,

wherein one or more exit ones of the hub routers each receive a replicated, modified multicast loss measurement message from the entrance one of the hub routers and each add a respective exit replication factor to the multicast loss measurement message that specifies a respective number of spoke pseudowires for the H-VPLS terminated by the entrance one of the hub routers, and

wherein each of the one or more remote network devices receives a respective replicated, modified multicast loss measurement message via a spoke pseudowire from one of the exit one of the hub routers and computes a respective return value based at least on the entrance replication factor and exit replication factor included in the respective replicated, modified multicast loss measurement message.

39. The system of claim 38, wherein each of the one or more remote network devices computes a respective return value as a quotient of the respective multicast PDU receive counter value for the local network device and a product of the entrance replication factor and the exit replication factor included in the respective replicated, modified multicast loss measurement message.

40. The system of claim 38,

wherein each of the one or more hub routers includes a replication factor table that maps an exit replication factor and/or an entrance replication factor to a loss measurement domain identifier that identifies a loss measurement domain for the H-VPLS instance,

wherein the local network devices issues the multicast loss measurement message that specifies the loss measurement domain identifier,

wherein the entrance one of the hub routers adds the entrance replication factor mapped to the loss measurement domain identifier in the replication factor table, and

wherein the one or more exit ones of the hub routers add the exit replication factor mapped to the loss measurement domain identifier in the replication factor table.