Accessing the Switch
You can access the switch by sshing into it with its management IP located in "Servers and Switches" section in each of the Pods wiki pages. The login credentials will he located on the servers of the Pod located in /opt/server_info.txt.
Once you have logged in you can configure the entire switch from one file located in /etc/sonic/config_db.json. You can also you commands like a Cisco CLI like through the wiki here: https://github.com/Azure/sonic-utilities/blob/master/doc/Command-Reference.md
Currently the Broadcom platform is broken on the current builds of SONiC. So we have a couple of workarounds to get things working.
This is what a typical VLAN setup would look like, just add the interfaces and VLANs you wish to use.
Once you have finished editing the json file, run this command to reload the config:
Untagged VLAN Workaround
Currently untagged VLANs do not just work right out of the box, it will show that it is untagged and will seem like it is working but no traffic will be able to go through the port unless you do this work around.
Edit /etc/sonic/config_db.json and go to the top of the file and you should see something like this:
Then count down to which interface you are setuping up to be untagged (for example Ethernet0 lines up to 10.0.0.1 and Ethernet4 lines up to 10.0.0.3) and delete the entire section from the IP address down to is closing bracket.
Then scoll down till you find something like this:
And then just delete the line with the interface you are setting up for untagged VLANs.
Once all of this is done save the file and then reload the config:
Now traffic should be able to flow through that port.
Breakout cables are now working on all of our pods with edgecore switches.
If you require all or some SFP connections over breakouts on the servers from your Pod please email firstname.lastname@example.org.