US 12,106,160 B2
First hop gateway redundancy in a network computing environment
Neeraj Malhotra, Los Gatos, CA (US); Keyur Patel, San Jose, CA (US); Derek Man-Kit Yeung, Fremont, CA (US); Lawrence Rolfe Kreeger, Fremont, CA (US); Shitanshu Shah, Cupertino, CA (US); Lalit Kumar, Milpitas, CA (US); Kalyani Rajaraman, San Jose, CA (US); Vikram Ragukumar, Pleasanton, CA (US); and Nalinaksh Pai, San Ramon, CA (US)
Assigned to Arrcus Inc., San Jose, CA (US)
Filed by Arrcus Inc., San Jose, CA (US)
Filed on Aug. 23, 2019, as Appl. No. 16/549,852.
Claims priority of provisional application 62/722,003, filed on Aug. 23, 2018.
Prior Publication US 2020/0067812 A1, Feb. 27, 2020
Int. Cl. G06F 9/54 (2006.01); G06F 9/455 (2018.01); G06F 9/48 (2006.01); G06F 16/22 (2019.01); G06F 16/23 (2019.01); G06F 16/27 (2019.01); H04L 9/40 (2022.01); H04L 12/28 (2006.01); H04L 12/44 (2006.01); H04L 12/46 (2006.01); H04L 12/66 (2006.01); H04L 45/00 (2022.01); H04L 45/02 (2022.01); H04L 45/24 (2022.01); H04L 45/28 (2022.01); H04L 45/48 (2022.01); H04L 45/50 (2022.01); H04L 45/586 (2022.01); H04L 45/745 (2022.01); H04L 47/125 (2022.01); H04L 67/1097 (2022.01); H04L 67/55 (2022.01); H04L 49/25 (2022.01)
CPC G06F 9/542 (2013.01) [G06F 9/45558 (2013.01); G06F 9/4881 (2013.01); G06F 9/54 (2013.01); G06F 16/2272 (2019.01); G06F 16/2379 (2019.01); G06F 16/27 (2019.01); G06F 16/278 (2019.01); H04L 12/2881 (2013.01); H04L 12/44 (2013.01); H04L 12/462 (2013.01); H04L 12/4633 (2013.01); H04L 12/4641 (2013.01); H04L 12/66 (2013.01); H04L 45/02 (2013.01); H04L 45/08 (2013.01); H04L 45/22 (2013.01); H04L 45/24 (2013.01); H04L 45/26 (2013.01); H04L 45/28 (2013.01); H04L 45/48 (2013.01); H04L 45/50 (2013.01); H04L 45/586 (2013.01); H04L 45/66 (2013.01); H04L 45/745 (2013.01); H04L 47/125 (2013.01); H04L 63/0272 (2013.01); H04L 67/1097 (2013.01); H04L 67/55 (2022.05); G06F 2009/45595 (2013.01); H04L 2012/4629 (2013.01); H04L 49/25 (2013.01)] 17 Claims
OG exemplary drawing
 
1. A system comprising:
a first switch in a network topology and a second switch in the network topology, wherein each of the first switch and the second switch comprises one or more processors, a memory, and a switch virtual interface for communicating with a virtual Layer3 interface to route traffic to other Layer3 interfaces;
a host virtual machine comprising a communication link with each of the first switch and the second switch; and
a routed peer link connecting the first switch to the second switch;
wherein the first switch and the second switch have a same gateway Internet protocol (IP) address and gateway media access control (MAC) address such that a single virtual interface including the gateway IP address and gateway MAC address is spread across both the first switch and the second switch;
wherein the first switch further has a first IP address and a first MAC address and the second switch further has a second IP address and a second MAC address, the first IP address being different from the second IP address and the first MAC address being different from the second MAC address; and
wherein the first switch and the second switch are configured to:
signal, to one another, a repair path for redirecting traffic when the communication link between the host virtual machine and either of the first switch or the second switch experiences a failure;
sync ARP tables through border gateway protocol (BGP) ethernet virtual private network (EVPN) messages;
generate the BGP EVPN messages in response to binding of the host virtual machine to a switch virtual interface (SVI) interface of the first and second switches.