From eaba250df6a61d58c658d23492e98f3c4ce057da Mon Sep 17 00:00:00 2001 From: Jing Zhang Date: Tue, 31 May 2022 13:50:05 -0700 Subject: [PATCH] adjust decision table; remove bandwidth calculation as 2 member lags are not hard requirement --- doc/dualtor/active_active_hld.md | 13 ++++--------- 1 file changed, 4 insertions(+), 9 deletions(-) diff --git a/doc/dualtor/active_active_hld.md b/doc/dualtor/active_active_hld.md index c3c9ed7314..a7f5cee3fa 100644 --- a/doc/dualtor/active_active_hld.md +++ b/doc/dualtor/active_active_hld.md @@ -55,11 +55,6 @@ In this design: ![image info](./image/cluster_topology.png) -__Bandwidth__ -Each ToR will have single port-channel to each T1. The port-channel will have 2 members of 100Gbps. Therefore, each T0 will have total of 8\*2\*100 Gbps = 1.6 Tbps to all T1s. - -T1s will have 8 uplinks to T2s. Therefore, total T1s uplink will be 64. Total uplink bandwidth is 6.4Tbps. - ## 2 Requrement Overview ### 2.1 Server Requirements In our cluster setup, as smart y-cable is replaced, some complexity shall be transferred to server NIC. @@ -324,8 +319,8 @@ Linkmgrd will provide the determination of a ToR / link's readiness for use. Default Route to T1 - Link Prober Link State + Link Prober Link Manager State gRPC Action to Update Server-Side Admin Forwarding State @@ -339,9 +334,9 @@ Linkmgrd will provide the determination of a ToR / link's readiness for use. Available + Up Active Active - Up Active Set to Active No-op @@ -354,18 +349,18 @@ Linkmgrd will provide the determination of a ToR / link's readiness for use. Available + Up Unknown * - Up Standby Set to standby No-op Available + Down * * - Down Standby Set to standby No-op