Method for Establishing High Resilient Active Recovery for BGP Route Reflectors
Abstract
A recovery route reflector with a monitoring module and a BGP state establishment module is peered with a plurality of primary route reflectors. Each of the plurality of primary route reflectors is peered with a set of provider edge devices. The BGP state between the recovery route reflector and the plurality of primary route reflectors is periodically monitored. When a primary route reflector fails the BGP state between the recovery route reflector and the failed primary route reflectors is idle, and the recovery route reflector establishes a peer session with the provider edge devices that had been peered with the failed route reflector.
Claims
exact text as granted — not AI-modifiedWhat is claimed:
1 . A method comprising:
establishing, by one or more processors, a first peer session between a recovery route reflector and a first route reflector; monitoring, by the one or more processors, a routing protocol state between the first route reflector and the recovery route reflector; based upon a determination that the routing protocol state is not active, establishing, by the one or more processors, a second peer session between the recovery route reflector and a first set of provider edge devices associated with the first route reflector; and establishing, by the one or more processors, a data artifact relating to the recovery route reflector and the first set of provider edge devices.
2 . The method of claim 1 , further comprising establishing, by the one or more processors, a third peer session between the recovery route reflector and a second route reflector, monitoring, by the one or more processors, a second routing protocol state between the second route reflector and the recovery route reflector, and based upon a determination that the second routing protocol state is not active, establishing, by the one or more processors, a fourth peer session between the recovery route reflector and a second set of provider edge devices associated with the second route reflector.
3 . The method of claim 1 , wherein the data artifact comprises neighbor configuration policies and parameters.
4 . The method of claim 1 , wherein the data artifact comprises a router ID.
5 . The method of claim 1 , wherein the data artifact comprises a loopback address.
6 . The method of claim 1 , wherein the recovery route reflector comprises a virtual route reflector.
7 . The method of claim 1 , wherein the first set of provider edge devices comprises routers.
8 . A system comprising:
one or more processors; and memory coupled with the one or more processors, the memory storing executable instructions that when executed by the one or more processors cause the one or more processors to effectuate operations comprising: establishing a first peer session between a recovery route reflector and a first route reflector; monitoring a routing protocol state between the first route reflector and the recovery route reflector; based upon a determination that the routing protocol state is idle, establishing a second peer session between the recovery route reflector and a first set of provider edge devices associated with the first route reflector; and establishing an artifact for the recovery route reflector and the first set of provider edge devices.
9 . The system of claim 8 , further comprising establishing a third peer session between the recovery route reflector and a second route reflector, monitoring a second routing protocol state between the second route reflector and the recovery route reflector, and based upon a determination that the second routing protocol state is idle, establishing a fourth peer session between the recovery route reflector and a second set of provider edge devices associated with the second route reflector.
10 . The system of claim 8 , wherein the artifact comprises neighbor configuration policies and parameters.
11 . The system of claim 8 , wherein the artifact comprises a router ID.
12 . The system of claim 8 , wherein the artifact comprises a loopback address.
13 . The system of claim 8 , wherein the recovery route reflector comprises a virtual route reflector.
14 . The system of claim 8 , wherein the first set of provider edge devices comprises routers.
15 . A non-transitory computer readable storage medium storing computer executable instructions that when executed by a computing device cause said computing device to effectuate operations comprising:
establishing a first peer session between a recovery route reflector and a first route reflector; monitoring a routing protocol state between the first route reflector and the recovery route reflector; when the routing protocol state is idle, establishing a second peer session between the recovery route reflector and a first set of provider edge devices; and establishing a data artifact for the recovery route reflector and the first set of provider edge devices.
16 . The non-transitory computer readable storage medium of claim 15 , further comprising establishing a third peer session between the recovery route reflector and a second route reflector, monitoring a second routing protocol state between the second route reflector and the recovery route reflector, and, when the second routing protocol state is idle, establishing a fourth peer session between the recovery route reflector and a second set of provider edge devices.
17 . The non-transitory computer readable storage medium of claim 15 , wherein the data artifact comprises neighbor configuration policies and parameters.
18 . The non-transitory computer readable storage medium of claim 15 , wherein the data artifact comprises a router ID.
19 . The non-transitory computer readable storage medium of claim 15 , wherein the data artifact comprises a loopback address.
20 . The non-transitory computer readable storage medium of claim 15 , wherein the recovery route reflector comprises a virtual route reflector.Join the waitlist — get patent alerts
Track US2022278890A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.