We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I tried to config LAG interface in virtual switch by adding fllowing to the config_db.json and then restart the vs container.
"PORTCHANNEL_INTERFACE": { "PortChannel0001|10.0.0.56/31": {}, "PortChannel0001|FC00::71/126": {} }, "PORTCHANNEL": { "PortChannel0001": { "members": [ "Ethernet112" ] } },
But seems the LAG was not created and can only find it's configuration in CONFIG_DB, guess this is due to lack of teamd support in the virtual switch?
kebol@arc-host74-006 ~]$sudo docker exec -it vs ifconfig PortChannel0001 PortChannel0001: error fetching interface information: Device not found [kebol@arc-host74-006 ~]$sudo docker exec -it vs redis-cli -n 4 keys \*PORTCHANNEL* 1) "PORTCHANNEL|PortChannel0001" 2) "PORTCHANNEL_INTERFACE|PortChannel0001|FC00::71/126" 3) "PORTCHANNEL_INTERFACE|PortChannel0001|10.0.0.56/31" [kebol@arc-host74-006 ~]$sudo docker exec -it vs redis-cli -n 6 keys \*LAG* (empty list or set)
The text was updated successfully, but these errors were encountered:
for how to add LAG config in VS, refer to #1720 #sonic-net/sonic-swss#507 and #sonic-net/sonic-swss#494
Sorry, something went wrong.
No branches or pull requests
I tried to config LAG interface in virtual switch by adding fllowing to the config_db.json and then restart the vs container.
But seems the LAG was not created and can only find it's configuration in CONFIG_DB, guess this is due to lack of teamd support in the virtual switch?
The text was updated successfully, but these errors were encountered: