Professional Documents
Culture Documents
Chen
Internet-Draft Futurewei
Intended status: Standards Track Y. Fan
Expires: September 16, 2021 Casa Systems
A. Wang
China Telecom
L. Liu
Fujitsu
X. Liu
Volta Networks
March 15, 2021
Abstract
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminologies . . . . . . . . . . . . . . . . . . . . . . . . 3
3. BGP for Controller Cluster Reliability . . . . . . . . . . . 3
3.1. Overview of Mechanism . . . . . . . . . . . . . . . . . . 3
3.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Extensions to BGP . . . . . . . . . . . . . . . . . . . . . . 6
4.1. Capability . . . . . . . . . . . . . . . . . . . . . . . 6
4.2. Controller NLRI . . . . . . . . . . . . . . . . . . . . . 7
5. Recovery Procedure . . . . . . . . . . . . . . . . . . . . . 9
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
7. Security Considerations . . . . . . . . . . . . . . . . . . . 11
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
9.1. Normative References . . . . . . . . . . . . . . . . . . 11
9.2. Informative References . . . . . . . . . . . . . . . . . 11
Authors’ Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction
the cluster may split the cluster into a few of separated controller
groups. These groups do not know each other and may be out of
synchronization. Two or more groups may be elected as primary groups
to control the network at the same time, which may cause some issues.
This document proposes some procedures and extensions to BGP for the
separated controllers or controller groups to know each other thus
elect one new primary controller or controller group correctly when
the cluster is split because of failures in the cluster.
2. Terminologies
Each controller has a BGP session with each of a give number of the
same NEs in the network and the session is established and maintained
over an IP path between the controller and the NE. The session is a
session of BGP with extensions.
3.2. Example
+---------------------------------------------------+
| Controller Cluster |
| |
| +------------+ +------------+ |
| |Controller A| Synchronize |Controller B| |
| |(Primary) +---------------+(Secondary) | |
| +------------+ +-----------++ |
| ^ | |
| |_______________ | |
| | | |
| v | |
+-----------------Channels to Network---------|-----+
/ \ |
Session ----> / \____ |
between / \ \____ | <--Session
A and NEi /\ .---. .---+ \ | between
(i=1,2,..) | \( ’ |’.---. | | B and NE4
|---\ Network | ’+. |
(o NE1\ | | ) /
( | | o) /
( | | ) NE4
( o NE2 o NE3.-’
’ )
’---._.-. )
’---’
The primary BGP controller (i.e., A) has a BGP session with each NE
in the network, including NE4. The secondary controller (i.e., B)
has a BGP session with the same NE4 in the network and the session is
established and maintained over an IP path between B and NE4.
For condition a, when the heartbeat from the primary stops, the
secondary knows that the connection between the primary and secondary
controller failed.
4. Extensions to BGP
4.1. Capability
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Cap Code (TBD1)| Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags |C|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Flag (32 bits): One flag bit, C-bit, is defined. When it is set to
one, it indicates that the BGP speaker supports the high
availability of controller cluster as a Controller. When it is
set to zero, it indicates that the BGP speaker supports the high
availability of controller cluster as a network element (NE).
When two BGP speakers establish a BGP session between them, each of
the speakers indicates its support for HAC by including a Controller
HA Support Capability Triple in the Capabilities Optional Parameter
in the OPEN message if it supports for HAC.
An NE running BGP with HAC support receives the information about the
controllers from the BGP as a controller supporting for HAC, and
sends the information to every BGP as a controller supporting for HAC
and having a BGP session with the NE except for the one from which
the information is received.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags |C| Position | OldPosition | Priority |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | NoControllers |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Connected Controller 1 ID |
: : |
| Connected Controller n ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5. Recovery Procedure
In the case of tie (i.e., two or more groups have the same maximum
number of controllers), the group with the highest old position
controller (e.g., the old primary controller) wins in one policy. In
another policy, the group with the highest priority controller wins.
One example is that failures split the cluster into two separated
groups: group 1 comprising A and C, group 2 consisting of B and N.
Each group elects its intent primary controller, secondary
controller, and so on. Suppose that controller A and C are elected
as the intent primary and secondary controller respectively in group
1; controller B and N are elected as the intent primary and secondary
controller respectively in group 2.
6. IANA Considerations
TBD
7. Security Considerations
TBD
8. Acknowledgements
TBD
9. References
[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
Border Gateway Protocol 4 (BGP-4)", RFC 4271,
DOI 10.17487/RFC4271, January 2006,
<https://www.rfc-editor.org/info/rfc4271>.
[RFC8283] Farrel, A., Ed., Zhao, Q., Ed., Li, Z., and C. Zhou, "An
Architecture for Use of PCE and the PCE Communication
Protocol (PCEP) in a Network with Central Control",
RFC 8283, DOI 10.17487/RFC8283, December 2017,
<https://www.rfc-editor.org/info/rfc8283>.
Authors’ Addresses
Huaimo Chen
Futurewei
Boston, MA
USA
Email: Huaimo.chen@futurewei.com
Yanhe Fan
Casa Systems
USA
Email: yfan@casa-systems.com
Aijun Wang
China Telecom
Beiqijia Town, Changping District
Beijing, 102209
China
Email: wangaj3@chinatelecom.cn
Lei Liu
Fujitsu
USA
Email: liulei.kddi@gmail.com
Xufeng Liu
Volta Networks
McLean, VA
USA
Email: xufeng.liu.ietf@gmail.com