# US 2019/0356581 A1 · Techniques for preferred path local switching in evpn-vpws > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2019/0356581 A1 - Document ID: US20190356581A1 - Status: Published application - Kind: A1 - Application number: 16/531,211 - Filed: 2019-08-05 - Published: 2019-11-21 - Earliest claimed: 2017-06-09 - Assignees: Cisco Technology, Inc. - Applicants: Cisco Technology, Inc. - Inventors: Patrice Brissette; Ali Sajassi - Web page: https://patentgrep.com/patent/US20190356581A1 ## CPC - H04L 45/28: using route fault recovery - H04L 12/413: with random access, e.g. carrier-sense multiple-access with collision detection [CSMA-CD] - 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)} - H04L 45/04: {Interdomain routing, e.g. hierarchical routing} - H04L 45/22: {Alternate routing} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract In one embodiment, a method includes, subsequent to receipt of a packet from a first customer network node destined for a second customer network node at a first provider network node, determining whether a local connection exists between the first provider network node and the second customer network node, the provider network node forming part of an Ethernet Virtual Private Network (“EVPN”)-Virtual Private Wire Service (“VPWS”) domain; if a local connection is determined to exist between the first provider network node and the second customer network node, determining whether the local connection has failed; if the local connection is determined not to have failed, switching the packet to the second customer network node via the local connection instead of via the EVPN-VPWS domain; and if the local connection is determined to have failed, switching the packet to the second customer network node via the EVPN-VPWS domain. ## Claims ### Claim 1 A method comprising: subsequent to receipt of a plurality of packets from a first customer network node destined for a second customer network node at a first provider network node, determining whether a local connection exists between the first provider network node and the second customer network node, wherein the first provider network node comprises part of an Ethernet Virtual Private Network (“EVPN”)-Virtual Private Wire Service (“VPWS”) domain, and wherein the first provider network node and a second provider network node provide all-active redundancy for a redundancy group; if a local connection is determined to exist between the first provider network node and the second customer network node, determining whether the local connection has failed; if the local connection is determined not to have failed, switching the plurality of packets to the second customer network node to provide preferred path local switching via the local connection instead of via the EVPN-VPWS domain; and if the local connection is determined to have failed, switching the plurality of packets to the second customer network node via the EVPN-VPWS domain. ### Claim 2 (depends on 1) The method of claim 1, wherein both of the first provider network node and the second provider network node of the redundancy group can forward traffic for both of the first customer network node and the second customer network node. ### Claim 3 (depends on 1) The method of claim 1, further comprising, if a local connection is determined not to exist between the first provider network node and the second customer network node, switching the plurality of packets to the second customer network node via the EVPN-VPWS domain. ### Claim 4 (depends on 1) The method of claim 1, wherein the first customer network node is locally connected to the first provider network node. ### Claim 5 (depends on 1) The method of claim 1, wherein the first and second customer network nodes comprise customer edge (“CE”) nodes. ### Claim 6 (depends on 1) The method of claim 1, wherein the first and second provider network nodes comprise provider edge (“PE”) nodes. ### Claim 7 (depends on 1) The method of claim 1, further comprising establishing a circuit between the first provider network node and the second provider network node via the EVPN-VPWS domain. ### Claim 8 (depends on 7) The method of claim 7, wherein the second customer network node is locally connected to the second provider network node. ### Claim 9 (depends on 1) The method of claim 1, wherein the first customer network node is associated with a first Ethernet segment identifier and the second customer network node is associated with a second Ethernet segment identifier that is different from the first Ethernet segment identifier. ### Claim 10 One or more non-transitory tangible media that includes code for execution and when executed by a processor is operable to perform operations comprising: subsequent to receipt of a plurality of packets from a first customer network node destined for a second customer network node at a first provider network node, determining whether a local connection exists between the first provider network node and the second customer network node, wherein the first provider network node comprises part of an Ethernet Virtual Private Network (“EVPN”)-Virtual Private Wire Service (“VPWS”) domain, and wherein the first provider network node and a second provider network node provide all-active redundancy for a redundancy group; if a local connection is determined to exist between the first provider network node and the second customer network node, determining whether the local connection has failed; if the local connection is determined not to have failed, switching the plurality of packets to the second customer network node to provide preferred path local switching via the local connection instead of via the EVPN-VPWS domain; and if the local connection is determined to have failed, switching the plurality of packets to the second customer network node via the EVPN-VPWS domain. ### Claim 11 (depends on 10) The media of claim 10, wherein both of the first provider network node and the second provider network node of the redundancy group can forward traffic for both of the first customer network node and the second customer network node. ### Claim 12 (depends on 10) The media of claim 10, wherein the operations further comprise, if a local connection is determined not to exist between the first provider network node and the second customer network node, switching the plurality of packets to the second customer network node via the EVPN-VPWS domain. ### Claim 13 (depends on 10) The media of claim 10, wherein the first customer network node is locally connected to the first provider network node. ### Claim 14 (depends on 10) The media of claim 10, wherein the first and second customer network nodes comprise customer edge (“CE”) nodes. ### Claim 15 (depends on 10) The media of claim 10, wherein the first and second provider network nodes comprise provider edge (“PE”) nodes. ### Claim 16 (depends on 10) The media of claim 10, wherein the operations further comprise establishing a circuit between the first provider network node and the second provider network node via the EVPN-VPWS domain. ### Claim 17 (depends on 16) The media of claim 16, wherein the second customer network node is locally connected to the second provider network node. ### Claim 18 An apparatus comprising: a memory element configured to store data; and a processor operable to execute instructions associated with the data, wherein executing the instructions causes the apparatus to perform operations, comprising: subsequent to receipt of a plurality of packets from a first customer network node destined for a second customer network node at a first provider network node, determining whether a local connection exists between the first provider network node and the second customer network node, wherein the first provider network node comprises part of an Ethernet Virtual Private Network (“EVPN”)-Virtual Private Wire Service (“VPWS”) domain, and wherein the first provider network node and a second provider network node provide all-active redundancy for a redundancy group; if a local connection is determined to exist between the first provider network node and the second customer network node, determining whether the local connection has failed; if the local connection is determined not to have failed, switching the plurality of packets to the second customer network node to provide preferred path local switching via the local connection instead of via the EVPN-VPWS domain; and if the local connection is determined to have failed, switching the plurality of packets to the second customer network node via the EVPN-VPWS domain. ### Claim 19 (depends on 18) The apparatus of claim 18, wherein both of the first provider network node and the second provider network node of the redundancy group can forward traffic for both of the first customer network node and the second customer network node. ### Claim 20 (depends on 18) The apparatus of claim 18, wherein executing the instructions causes the apparatus to perform further operations, comprising: if a local connection is determined not to exist between the first provider network node and the second customer network node, switching the plurality of packets to the second customer network node via the EVPN-VPWS domain.