- List of Tables
- Revision
- About This Manual
- Scope
- Definition/Abbreviation
- 1 Feature Overview
- 2 Functionality
- 3 Design
- 4 Flow Diagrams
- 5 Error Handling
- 6 Serviceability and Debug
- 7 Warm Boot Support
- 8 Scalability
- 10 Unit Test
- 11 References
| Rev | Date | Author | Change Description |
|---|---|---|---|
| 0.1 | 10/31/2019 | Amitabha Sen | Initial version |
| 0.2 | 06/20/2022 | Kannan Selvaraj | Updated load-balance round-robin |
| show command display as NONE |
This document provides details on achieving Static Port Channel functionality in SONiC.
This document describes the high level design of Static Port Channel functionality.
| Term | Meaning |
|---|---|
| LAG | Link Aggregation Group |
| LACP | Link Aggregation Control Protocol |
- 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.
- Provide configuration to set a Port Channel mode as on with the click CLI.
- Enhance show commands to display the Port Channel mode as STATIC when configured so with the click CLI.
- The maximum number of Port Channels configurable (Static and Dynamic put together) per system is 256.
- The maximum number of member ports configurable per Port Channel are 32. (Generally depends on ASIC)
The traffic loss during a warm reboot should be within the prescribed limits of warm boot.
A Static Port Channel has its member ports always available for traffic as long the links are up. All ports are mandated to have the same speed to become members of a Port Channel. Teamd uses round-robin for a Static Port Channel.
An instance of Teamd process is created when a Port Channel (Static or Dynamic) is created. Teamd process runs as part of the Teamd docker.
There are no changes to SAI headers/implementation to support this feature.
Static Port Channels can be deployed in both Enterprise and Data center networks. Example usage scenarios for Static Port Channels are:
- To attach legacy equipment that does not support LACP.
- To handle warm boot cases where the control plane outage can exceed 3 * long timeout.
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.
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.
Upon creating a static Port Channel, the "Teamd" daemon corresponding to that Port Channel is instantiated in static mode.
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". Note: Port Channels are dynamic by default in SONiC.
Team Manager listens to Port Channel update events from the PORTCHANNEL and PORTCHANNEL_MEMBER table in CONFIG_DB. For the Static Port Channel add event it starts Teamd with load-balance as the runner; whereas for the dynamic Port Channel Teammgr starts Teamd with lacp as the runner.
When static port-channel is configured then teammgr invokes teamd instance as follows root 27 1 0 Jun17 ? 00:01:10 /usr/bin/teamd -r -t PortChannel0001 -c {"device":"PortChannel0001","hwaddr":"00:e0:ec:7a:88:11","runner":{"name":"loadbalance","min_ports":1}} -L /var/warmboot/teamd/ -g -d
round-robin load-balancing is configured for the kernel interface port-channel.
To support the static mode for a Port Channel, the PORTCHANNEL table is modified to add a new key-value pair where the value is a "true" or a "false".
"PORTCHANNEL|PortChannel0001": {
"type": "hash",
"value": {
"on": "true"
}
}
127.0.0.1:6379[4]> hgetall "PORTCHANNEL|PortChannel0001"
9) "on"
10) "true"
No new tables are needed.
No new tables are needed.
No new tables are needed.
No new tables are needed.
No changes are needed.
No changes are needed.
No changes are needed.
No changes are needed.
Please refer Openconfig support for Port Channel for details on the Data Model.
Please refer Openconfig support for Port Channel for details on KLISH CLI.
click CLI
1. config portchannel add PortChannel<number> --on=true
Create a Static Port Channel.
Please refer Openconfig support for Port Channel for details on KLISH CLI.
click CLI
1. show interfaces portchannel
This command is modified to show the Port Channel Protocol as None for a Static Port Channel.
Flags: A - active, I - inactive, Up - up, Dw - Down, N/A - not available,
S - selected, D - deselected, * - not synced
No. Team Dev Protocol Ports
----- --------------- ------------- --------------
0001 PortChannel0001 NONE(A)(Up) Ethernet112(S)
0002 PortChannel0002 NONE(A)(Up) Ethernet116(S)
0003 PortChannel0003 NONE(A)(Up) Ethernet120(S)
No new debug commands are added.
Please refer Openconfig support for Port Channel for details on Rest API support.
The below flow diagrams illustrate the interactions of TeamD with rest of the components in SONiC.
No new error handling support is added.
No new Serviceability or Debug support are added.
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.
Teamd will support the necessary scalability requirements.
- Create a Static Port Channel.
- Verify that there is an entry in the PORTCHANNEL table in CONFIG_DB for the Port Channel and it is marked Static.
- Verify that there is an entry in the kernel for the Port Channel and its state is Down.
- Verify that there is an entry in the LAG_TABLE in APPL_DB for the Port Channel and the operational status is Down.
- Verify that there is an entry in the PORTCHANNEL in STATE_DB for the Port Channel.
- Verify that there is an entry in the ASIC_DB for the Port Channel.
- Verify that there is an entry in the hardware for the Port Channel with no member ports.
- Dump Teamd instance config and Verify that the Port Channel is present and the runner is "round-robin".
- Dump Teamd instance state and verify that the Port Channel is present.
- Add a member to the Static Port Channel.
- Verify that there is an entry in the PORTCHANNEL_MEMBER table in CONFIG_DB for the Port Channel with its member port.
- Verify that there is an entry in the kernel for the Port Channel and its state is Up.
- Verify that there is an entry in the LAG_TABLE in APPL_DB for the Port Channel and the operational status is Up.
- Verify that there is an entry in the LAG_MEMBER_TABLE in APPL_DB for the Port Channel and its member.
- Verify that there is an entry in the PORTCHANNEL in STATE_DB for the Port Channel.
- Verify that there is an entry in the ASIC_DB for the Port Channel with its member port.
- Verify that there is an entry in the hardware for the Port Channel with its member port.
- Dump Teamd instance config and Verify that the Port Channel is present with its member port.
- Dump Teamd instance state and verify that the Port Channel is present with its member port.
-
Delete the member from the Static Port Channel and verify that the system is restored to the state as after test case 1.
-
Delete the Static Port Channel and verify that the Redis database, kernel, hardware and Teamd instance have deleted all information about the Port Channel.