IP Library › Granted Patent US 12,192,086
Granted Patent B2
US 12,192,086 · App. 17/728,395 · Granted Jan 7, 2025

Validating reachability for liaison VRFs using OAM ping packets

Inventors: Saumya Dikshit (Bangalore, IN); Ashwini Dahiya (Bangalore, IN); Srinath Krishna Rao (Roseville, CA)
Assignee: Hewlett Packard Enterprise Development LP
H04L43/10H04L12/4633H04L12/4641H04L45/02
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 12,192,086
App. No.
17/728,395
Granted
Jan 7, 2025
Kind
B2
Abstract

Systems and methods provide a new type of time-length-value data stream (TLV) which can be encapsulated in an OAM ping packet. This “EVI TLV” encapsulating OAM ping packet can be sent to a network device (e.g., a border router) that a liaison VRF is provisioned on. Upon receipt, the encapsulated EVI TLV instructs the network device to determine whether the configuration of the liaison VRF is mapped to an EVI value specified by the EVI TLV. If the configuration of the liaison VRF is mapped to the specified EVI value, the network device returns an echo response indicating that the configuration of the liaison VRF is mapped onto the specified EVI value. Such a response may indicate that the liaison VRF is reachable for the EVPN.

Claims (42)

1. A method comprising:

sending, by a first device, to a second device in a Virtual Private Network (VPN), an Operations, Administration, and Maintenance (OAM) ping packet, wherein;

a liaison Virtual Routing and Forwarding instance (VRF) is provisioned on the second device,

the liaison VRF functions to publish learned external routes to other devices within the VPN,

the OAM ping packet encapsulates a VPN Instance Identifier (EVI) time-length-value data stream (TLV) (collectively an EVI TLV), and

the EVI TLV specifies an EVI value; and

receiving, by the first device, from the second device, a response to the OAM ping packet indicating that a configuration of the liaison VRF is mapped onto the specified EVI value.

2. The method of claim 1 , further comprising, determining, by the first device, that the liaison VRF is reachable within the VPN.

3. The method of claim 1 , wherein the liaison VRF has not published any learned external routes to the other devices within the VPN.

4. The method of claim 1 , wherein the VPN comprises an Ethernet VPN (EVPN).

5. The method of claim 4 , wherein the EVPN comprises a Vxlan data plane and the EVI value comprises a Virtual Network Identifier (VNI) associated with the Vxlan data plane.

6. The method of claim 4 , wherein the EVPN comprises an MPLS data plane and the EVI value comprises an identifying label associated with the MPLS data plane.

7. The method of claim 4 , wherein the second device comprises a border router of the EVPN.

8. The method of claim 1 , wherein the first device is a device within the VPN.

9. A first device in an EVPN, the first network device comprising:

a plurality of processing resources associated with the first device; and

a non-transitory computer-readable medium, coupled to the plurality of processing resources, having stored therein instructions that when executed by the processing resources cause the first device to:

receive, from a second device, an OAM ping packet, wherein;

a liaison VRF is provisioned on the first device,

the liaison VRF functions to publish learned external routes to other devices within the EVPN,

the OAM ping packet encapsulates an EVI TLV, and

the EVI TLV specifies an EVI value;

determine that a configuration of the liaison VRF is mapped onto the specified EVI value; and

send, to the second device, a response to the OAM ping packet indicating that the configuration of the liaison VRF is mapped onto the specified EVI value.

10. The first device of claim 9 , wherein the response to the OAM ping packet comprises an echo response.

11. The first device of claim 9 , wherein the response to the OAM ping packet also indicates that the liaison VRF is reachable within the EVPN.

12. The first device of claim 9 , wherein the first device comprises a border router of the EVPN.

13. The first device of claim 9 , wherein the liaison VRF has not published any learned external routes to the other devices within the EVPN.

14. The first device of claim 9 , wherein the EVPN comprises a Vxlan data plane and the EVI value comprises a VNI associated with the Vxlan data plane.

15. The first device of claim 9 , wherein the EVPN comprises an MPLS data plane and the EVI value comprises an identifying label associated with the MPLS data plane.

16. The first device of claim 9 , wherein the second device is a device within the EVPN.

17. A non-transitory computer-readable medium storing instructions, which when executed by a plurality of processing resources of a first device, cause the first device to:

send, to a second device in an EVPN, an OAM ping packet, wherein;

a liaison VRF is provisioned on the second device,

the liaison VRF functions to publish learned external routes to other devices within the EVPN,

the OAM ping packet encapsulates an EVI TLV, and

the EVI TLV specifies an EVI value;

receive, from the second device, a response to the OAM ping packet indicating that a configuration of the liaison VRF is mapped onto the specified EVI value; and

determining the liaison VRF is reachable within the EVPN.

18. The non-transitory computer-readable medium of claim 17 , wherein the liaison VRF has not published any learned external routes to other devices within the EVPN.

19. The non-transitory computer-readable medium of claim 17 , wherein EVPN comprises a Vxlan data plane and the EVI value comprises a VNI associated with the Vxlan data plane.

20. The non-transitory computer-readable medium of claim 17 , wherein the EVPN comprises an MPLS data plane and the EVI value comprises an identifying label associated with the MPLS data plane.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 25, 2022
From: DIKSHIT, SAUMYA; DAHIYA, ASHWINI; RAO, SRINATH KRISHNA
To: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
Reel/Frame 059700/0011 →
Continuity (1)
Related Publication 20230344736A1 · Oct 26, 2023
References Cited (15)
US 7623446B1 · Allan · 2009 [cited by examiner]
US 7983174B1 · Monaghan · 2011 [cited by examiner]
US 9071514B1 · Hegde · 2015 [cited by examiner]
US 11159389B1 · Miriyala · 2021 [cited by examiner]
US 20150029872A1 · Pignataro · 2015 [cited by examiner]
US 20210203585A1 · Takeshita · 2021 [cited by examiner]
“Layer-transcending traceroute for VXLAN”, available online at <https://datatracker.ietf.org/meeting/92/materials/slides-92-nvo3-5>, 12 pages. [cited by applicant]
Chen et al., “Revised Error Handling for BGP Update Messages”, Request for Comments: 7606, Aug. 2015, 19 pages. [cited by applicant]
Jain et al., “LSP-Ping Mechanisms for EVPN and PBB-EVPN draft-ietf-bess-evpn-lsp-ping-06”, Jan. 16, 2022, 16 pages. [cited by applicant]
Jain et al., “LSP-Ping Mechanisms for EVPN and PBB-EVPN draft-ietf-bess-evpn-lsp-ping-05”, BESS Workgroup, Jun. 14, 2021, 15 pages. [cited by applicant]
Juniper Networks, Inc., “MPLS OAM Configuration,” Feb. 22, 2021, 21 pages, <https://web.archive.org/web/20211028002751/https://www.juniper.net/documentation/us/en/software/junos/mpls/topics/topic-map/mpls-oam-configurat… [cited by applicant]
Kompella et al., “Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures”, Request for Comments: 4379, Feb. 2006, 50 pages. [cited by applicant]
Kompella et al., “Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures”, Request for Comments: 8029, Mar. 2017, 78 pages. [cited by applicant]
Lukas Krattiger, “Overlay Management and Visibility with VXLAN”, Cisco, 2019, 101 pages. [cited by applicant]
Salam et al., “NVO3 Fault Management draft-tissa-nvo3-oam-fm-04.txt”, NV03 Working Group , May 5, 2017, 39 pages. [cited by applicant]