BGP peering status-aware hitless reboot
AssigneeArista Networks, Inc.
InventorsAnand Narayanan, Akhil Shashidar, Pavan Narasimhaprasad, Thejesh Panchappa
Life of this patent
Estimating the term…
Abstract
Techniques for implementing Border Gateway Protocol (BGP) peering status-aware hitless reboot on a network device are provided. In one set of embodiments, at the time of shutting down for a hitless reboot, the network device can collect status information regarding its BGP peerings and can write this information to a file on non-volatile storage. Then, upon booting up after the hitless reboot, the network device can retrieve the file from the non-volatile storage and use the status information included therein to restore the BGP peerings as they existed prior to the hitless reboot.
Claims18
A method performed by a network device for implementing a hitless reboot, the method comprising:
- at a time of shutting down the network device:
- identifying one or more Border Gateway Protocol (BGP) static peers defined in a peer configuration of the network device;
- for each identified BGP static peer, writing a first entry to a peering status file maintained on a non-volatile storage of the network device, the first entry including an Internet Protocol (IP) address of the identified BGP static peer and a current peering status of the identified BGP static peer;
- identifying one or more BGP dynamic peers that have an established BGP session with the network device;
- and
- for each identified BGP dynamic peer, writing a second entry to the peering status file, the second entry including an IP address of the identified BGP dynamic peer and a current peering status of the identified BGP dynamic peer;
- and
- at a time of booting up the network device:
- retrieving the peering status file from the non-volatile storage;
- identifying one or more BGP peers of the network device listed in the peering status file;
- and
- for each identified BGP peer, sending a connection request to the identified BGP peer using the IP address specified for the identified BGP peer in the peering status file.
A network device comprising:
- a central processing unit (CPU);
- a non-volatile storage;
- and
- a main memory having stored thereon program code that, when executed by the CPU, causes the CPU to:
- at a time of shutting down the network device:
- identify one or more Border Gateway Protocol (BGP) static peers defined in a peer configuration of the network device;
- for each identified BGP static peer, write a first entry to a peering status file maintained on the non-volatile storage, the first entry including an Internet Protocol (IP) address of the identified BGP static peer and a current peering status of the identified BGP static peer;
- identify one or more BGP dynamic peers that have an established BGP session with the network device;
- and
- for each identified BGP dynamic peer, write a second entry to the peering status file, the second entry including an IP address of the identified BGP dynamic peer and a current peering status of the identified BGP dynamic peer;
- and
- at a time of booting up the network device:
- retrieve the peering status file from the non-volatile storage;
- identify one or more BGP peers of the network device listed in the peering status file;
- and
- for each identified BGP peer, send a connection request to the identified BGP peer using the IP address specified for the identified BGP peer in the peering status file.
A method performed by a network device for implementing a hitless reboot, the method comprising:
- at a time of shutting down the network device:
- identifying one or more Border Gateway Protocol (BGP) static peers defined in a peer configuration of the network device;
- and
- for each identified BGP static peer, writing a first entry to a peering status file maintained on a non-volatile storage of the network device, the first entry including an Internet Protocol (IP) address of the identified BGP static peer and a current peering status of the identified BGP static peer;
- and
- at a time of booting up the network device:
- retrieving the peering status file from the non-volatile storage;
- identifying one or more BGP peers of the network device listed in the peering status file;
- and
- for each identified BGP peer, sending a connection request to the identified BGP peer using the IP address specified for the identified BGP peer in the peering status file.
Dependencies are inferred from the claim text.