Skip to content

Commit a2a742c

Browse files
Update Static Port Channel Design Document.md
1 parent f99d5d5 commit a2a742c

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

doc/lag/Static Port Channel Design Document.md

+7-7
Original file line numberDiff line numberDiff line change
@@ -88,12 +88,12 @@ This document describes the high level design of Static Port Channel functionali
8888
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.
8989

9090
### 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.
9393

9494
### 1.1.3 Scalability Requirements
9595
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)
9797

9898
### 1.1.4 Warm Boot Requirements
9999
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
124124
## 2.2 Functional Description
125125
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.
126126

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.
128128

129129
# 3 Design
130130

131131
## 3.1 Overview
132132
Upon creating a static Port Channel, the "Teamd" daemon corresponding to that Port Channel is instantiated in static mode.
133133

134134
### 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".
136136
Note: Port Channels are dynamic by default in SONiC.
137137

138138
### 3.1.2 Team Manager
@@ -240,7 +240,7 @@ No new error handling support is added.
240240
No new Serviceability or Debug support are added.
241241

242242
# 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.
244244

245245
# 8 Scalability
246246
Teamd will support the necessary scalability requirements.
@@ -253,7 +253,7 @@ Teamd will support the necessary scalability requirements.
253253
- Verify that there is an entry in the PORTCHANNEL in STATE_DB for the Port Channel.
254254
- Verify that there is an entry in the ASIC_DB for the Port Channel.
255255
- 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".
257257
- Dump Teamd instance state and verify that the Port Channel is present.
258258

259259
2. Add a member to the Static Port Channel.

0 commit comments

Comments
 (0)