ARBITRATING MASTERSHIP BETWEEN REDUNDANT CONTROL PLANES OF A VIRTUAL NODE

• US 20190230031A1
• Filed: 01/19/2018
• Published: 07/25/2019
• Est. Priority Date: 01/19/2018
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Mahishi, Shrish
• Granted Patent: US 10,680,944 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 9/455 Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
• CPC Class Codes: G06F 9/545 where tasks reside in different layers, e.g. user- and kernel-space
• CPC Class Codes: H04L 41/0668 by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
• CPC Class Codes: H04L 45/586 of virtual routers
• CPC Class Codes: H04L 45/64 using an overlay routing layer

Abstract

In one example, a management component executes on a network device, a first routing component executing on a first server device physically separate from the network device to provide control plane routing functionality for a virtual node on the network device, and a second routing component executing on a second server device physically separate from the network device to provide control plane routing functionality for the virtual node, wherein the first routing component and the second routing component operate as a redundant master-backup pair for the virtual node. The management component is configured to detect first reachability of the network device with a first routing component and second reachability of the network device with a second routing component, and send a control message to each of the first routing component and the second routing component, the control message specifying reachability information indicating the first reachability and the second reachability.

Claims

1. A system comprising:

a management component executing on a network device;

a first routing component executing on a first server device physically separate from the network device and configured to provide control plane routing functionality for a virtual node of a plurality of virtual nodes configured on the network device; and

a second routing component executing on a second server device physically separate from the network device and configured to provide control plane routing functionality for the virtual node, wherein the first routing component and the second routing component operate as a master-backup pair for the virtual node such that, at a given time, one of the first routing component and the second routing component is a master routing component of the master-backup pair and the other of the first routing component and the second routing component is a backup routing component of the master-backup pair,

wherein the management component is configured to detect first reachability of the network device with the first routing component and second reachability of the network device with the second routing component, and send a control message to each of the first routing component and the second routing component, the control message specifying reachability information indicating the first reachability and the second reachability, and

wherein one or more of the first routing component and the second routing component are configured to determine, in response to receiving the control message and based on the reachability information, whether to operate as the master routing component for the virtual node.

2. The system of claim 1, further comprising:

a first physical link providing connectivity between the first routing component and the management component; and

second physical link providing connectivity between the second routing component and the management component.

3. The system of claim 2, wherein to detect reachability with the first routing component, the management component is configured to determine whether a keepalive message is received on the first physical link.

4. The system of claim 1,

wherein the first reachability comprises reachability of a first interface of the network device with the first routing component, wherein the second reachability comprises reachability of the first interface of the network device with the second routing component,

wherein the management component is configured to detect third reachability of a second interface of the network device with the first routing component, and fourth reachability of the second interface of the network device with the second routing component, and

wherein in sending the control message the management component sends a control message specifying reachability information indicating the first reachability, second reachability, third reachability, and fourth reachability.

5. The system of claim 1, wherein the control message specifies the reachability information by a set of bits each indicating one of the first reachability, the second reachability, the third reachability, and the fourth reachability, wherein two bits of the set of bits are master reachability bits indicating reachability of a master routing component.

6. The system of claim 5, wherein the first routing component is configured to determine whether to operate as the master routing component by:

if the first routing component is currently a backup, and both master reachability bits are not set, acquiring mastership to operate as the master routing component,

if the first routing component is currently the backup routing component, and at least one master reachability bit is set, continuing to remain as the backup routing component;

if the first routing component is currently the backup routing component, and no subsequent control message is received within a configurable time period, continuing to remain as the backup routing component;

if the first routing component is currently the master routing component, and at least one master reachability bit is set, continuing to remain as the master routing component;

if the first routing component is currently the master routing component, and both master reachability bits are not set, relinquishing mastership to operate as the backup routing component; and

if the first routing component is currently the master routing component, and no subsequent control message is received within a configurable time period, relinquishing mastership to operate as the backup routing component.

7. The system of claim 1, wherein the first routing component and the second routing component are configured to manage, in a line card of the network device, forwarding state for forwarding packets for the virtual node.

8. The system of claim 1, wherein the virtual node comprises a first virtual node, and wherein the single-chassis network device further comprises:

a plurality of packet processors, the first virtual node configured to forward packets using a first subset of the plurality of packet processors; and

a second virtual node of the plurality of virtual nodes, the second virtual node configured to forward packets using a second subset of the plurality of packet processors, the second subset being distinct from the first subset.

9. The system of claim 8, further comprising:

a third routing component executing on the first server device, the third routing component configured to provide control plane routing functionality for the second virtual node; and

a fourth routing component executing on the second server device, the fourth routing component configured to provide control plane routing functionality for the second virtual node, wherein the third routing component and the fourth routing component operate as a master-backup pair for the second virtual node.

10. The system of claim 1, wherein the first routing component and the second routing component each comprises a virtual machine.

11. A method comprising:

detecting, by a management component executing on a network device, first reachability of the network device with a first routing component and second reachability of the network device with a second routing component, wherein the first routing component executes on a first server device physically separate from the network device and is configured to provide control plane routing functionality for a virtual node of a plurality of virtual nodes configured on the network device, and wherein the second routing component executes on a second server device physically separate from the network device and is configured to provide control plane routing functionality for the virtual node, wherein the first routing component and the second routing component operate as a master-backup pair for the virtual node such that one of the first routing component and the second routing component is a master routing component of the master-backup pair and the other of the first routing component and the second routing component is a backup routing component of the master-backup pair; and

sending, by the management component, a control message to each of the first routing component and the second routing component, the control message specifying reachability information indicating the first reachability and the second reachability, wherein the reachability information determines a mastership arbitration by which one or more of the first routing component and the second routing component determine whether to operate as the master routing component for the virtual node.

12. The method of claim 11, wherein the first reachability comprises reachability of a first interface of the network device with the first routing component, wherein the second reachability comprises reachability of the first interface of the network device with the second routing component,

the method further comprising:

detecting, by the management component, third reachability of a second interface of the network device with the first routing component; and

detecting, by the management component, fourth reachability of the second interface of the network device with the second routing component, and

wherein sending the control message comprises sending a control message specifying reachability information indicating the first reachability, second reachability, third reachability, and fourth reachability.

13. The method of claim 11, further comprising:

determining, by one or more of the first routing component and the second routing component in response to receiving the control message and based on the reachability information, whether to operate as the master routing component for the virtual node.

14. The method of claim 11,

wherein the control message causes the first routing component and second routing component to swap master and backup roles for providing control plane routing functionality for the virtual node.

15. A method comprising:

receiving, by a first routing component executing on a first server device physically separate from a network device and configured to provide control plane routing functionality for a virtual node of a plurality of virtual nodes configured on the network device, a control message specifying reachability information, the reachability information comprising first reachability of the network device with the first routing component and second reachability of the network device with a second routing component, wherein the second routing component executes on a second server device physically separate from the network device and is configured to provide control plane routing functionality for the virtual node, wherein the first routing component and the second routing component operate as a master-backup pair for the virtual node such that one of the first routing component and the second routing component is a master routing component of the master-backup pair and the other of the first routing component and the second routing component is a backup routing component of the master-backup pair; and

determining, by the first routing component, whether to operate as the master routing component for the virtual node.

16. The method of claim 15, wherein determining whether to operate as the master routing component for the virtual node comprises one of the group consisting of:

determining to acquire mastership to operate as the master routing component, and continuing to remain as the master routing component.

17. The method of claim 16, wherein determining whether to operate as the master routing component for the virtual node comprises one of the group consisting of:

determining to relinquish mastership, and continuing to remain as the backup routing component.

18. The method of claim 15, wherein the first reachability comprises reachability of a first interface of the network device with the first routing component, wherein the second reachability comprises reachability of the first interface of the network device with the second routing component, the reachability information further comprising third reachability of a second interface of the network device with the first routing component, and fourth reachability of the second interface of the network device with the second routing component, and

wherein receiving the control message comprises receiving a control message specifying the reachability information by a set of bits each indicating one of the first reachability, the second reachability, the third reachability, and the fourth reachability, wherein two bits of the set of bits are master reachability bits indicating reachability of a master routing component.

19. The method of claim 18, wherein determining, by the first routing component, whether to operate as the master routing component for the virtual node comprises:

if the first routing component is currently a backup, and both master reachability bits are not set, acquiring mastership to operate as the master routing component,

if the first routing component is currently the backup routing component, and at least one master reachability bit is set, continuing to remain as the backup routing component;

if the first routing component is currently the backup routing component, and no subsequent control message is received within a configurable time period, continuing to remain as the backup routing component;

if the first routing component is currently the master routing component, and at least one master reachability bit is set, continuing to remain as the master routing component;

if the first routing component is currently the master routing component, and both master reachability bits are not set, relinquishing mastership to operate as the backup routing component; and

if the first routing component is currently the master routing component, and no subsequent control message is received within a configurable time period, relinquishing mastership to operate as the backup routing component.

20. A non-transitory computer-readable storage medium comprising instructions for causing one or more programmable processors of a first server device to:

receive, by a first routing component executing on the first server device and configured to provide control plane routing functionality for a virtual node of a plurality of virtual nodes configured on a network device, a control message specifying reachability information, the reachability information including first reachability of the network device with the first routing component and second reachability of the network device with a second routing component, wherein the first server device is physically separate from the network device, and wherein the second routing component executes on a second server device physically separate from the network device and is configured to provide control plane routing functionality for the virtual node, wherein the first routing component and the second routing component operate as a master-backup pair for the virtual node such that one of the first routing component and the second routing component is a master routing component of the master-backup pair and the other of the first routing component and the second routing component is a backup routing component of the master-backup pair; and

determine whether the first routing component is to operate as the master routing component for the virtual node.