You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: doc/lag/Static Port Channel Design Document.md
+7-7
Original file line number
Diff line number
Diff line change
@@ -88,12 +88,12 @@ This document describes the high level design of Static Port Channel functionali
88
88
1. Support Port Channel in Static mode. Static Port Channel member ports are always available for traffic transmission and reception if the ports links are up. Port types and features are supported in the same way as SONiC LAGs today. MLAG should seamlessly work in Static Mode.
89
89
90
90
### 1.1.2 Configuration and Management Requirements
91
-
1. Provide configuration to set a Port Channel mode as Static with the click CLI.
92
-
2. Enhance show commands to display the Port Channel mode as Static when configured so with the click CLI.
91
+
1. Provide configuration to set a Port Channel mode as on with the click CLI.
92
+
2. Enhance show commands to display the Port Channel mode as STATIC when configured so with the click CLI.
93
93
94
94
### 1.1.3 Scalability Requirements
95
95
1. The maximum number of Port Channels configurable (Static and Dynamic put together) per system is 256.
96
-
2. The maximum number of member ports configurable per Port Channel are 32.
96
+
2. The maximum number of member ports configurable per Port Channel are 32. (Generally depends on ASIC)
97
97
98
98
### 1.1.4 Warm Boot Requirements
99
99
The traffic loss during a warm reboot should be within the prescribed limits of warm boot.
@@ -124,15 +124,15 @@ Static Port Channels can be deployed in both Enterprise and Data center networks
124
124
## 2.2 Functional Description
125
125
A Port Channel bundles individual ports into a group to provide increased bandwidth, load balancing and redundancy. A Port Channel can be either Static or Dynamic. A Dynamic Port Channel runs Link Aggregation Signaling protocols like LACP to mark the links active for traffic. A Static Port Channel has its member ports always available for traffic. Incoming LACPDUs are silently ignored.
126
126
127
-
Static Port Channel uses the loadbalance runner which hashes CPU sourced or CPU forwarded traffic among the member ports. Traffic forwarded in hardware on the Port Channel uses the silicon specific traffic hashing algorithm.
127
+
Static Port Channel uses the roundrobin runner which hashes CPU sourced or CPU forwarded traffic among the member ports. Traffic forwarded in hardware on the Port Channel uses the silicon specific traffic hashing algorithm.
128
128
129
129
# 3 Design
130
130
131
131
## 3.1 Overview
132
132
Upon creating a static Port Channel, the "Teamd" daemon corresponding to that Port Channel is instantiated in static mode.
133
133
134
134
### 3.1.1 Teamd configuration
135
-
A user should be able to create the Port Channel in static or dynamic mode. For static mode, the CONFIG_DB is updated with a flag.
135
+
A user should be able to create the Port Channel in static or dynamic mode. For static mode, the CONFIG_DB is updated with a "on": "true".
136
136
Note: Port Channels are dynamic by default in SONiC.
137
137
138
138
### 3.1.2 Team Manager
@@ -240,7 +240,7 @@ No new error handling support is added.
240
240
No new Serviceability or Debug support are added.
241
241
242
242
# 7 Warm Boot Support
243
-
Teamd supports warm boot. There is minimal traffic loss on the Port Channel during a system warm boot as the data plane is disrupted for less than 1 second.
243
+
Teamd supports warm boot. There is minimal traffic loss on the Port Channel during a system warm boot as the data plane is disrupted for less than 1 second. No new changes needed.
244
244
245
245
# 8 Scalability
246
246
Teamd will support the necessary scalability requirements.
@@ -253,7 +253,7 @@ Teamd will support the necessary scalability requirements.
253
253
- Verify that there is an entry in the PORTCHANNEL in STATE_DB for the Port Channel.
254
254
- Verify that there is an entry in the ASIC_DB for the Port Channel.
255
255
- Verify that there is an entry in the hardware for the Port Channel with no member ports.
256
-
- Dump Teamd instance config and Verify that the Port Channel is present and the runner is "loadbalance".
256
+
- Dump Teamd instance config and Verify that the Port Channel is present and the runner is "round-robin".
257
257
- Dump Teamd instance state and verify that the Port Channel is present.
0 commit comments