History

byu343 9b2b8e3e86 Add gearbox taps to vs gearbox_config.json (#11480 ) Why I did it For the change to support gearbox taps by gearbox_config.json (sonic-net/sonic-swss#2158), I need to add tests to sonic-swss/tests/test_gearbox.py to satisfy the test coverage of the change. The existing code in test_gearbox.py has already used brcm_gearbox_vs and here is to add some gearbox tap value to its gearbox_config.json, for the added tests in sonic-swss/tests/test_gearbox.py. How I did it How to verify it This change itself will not affect existing code.		2022-10-10 13:35:06 -07:00
..
brcm_gearbox_vs	Add gearbox taps to vs gearbox_config.json (#11480 )	2022-10-10 13:35:06 -07:00
plugins	[sonic-utilities] Update submodule; Build and install as a Python 3 wheel (#5926 )	2020-11-25 10:28:36 -08:00
SONiC-VM	[devices]: Add new SKU for SONiC VM (#8971 )	2021-10-14 10:47:40 -07:00
asic.conf	[baseimage]: support building multi-asic component (#3856 )	2020-01-26 13:56:42 -08:00
default_sku	[vs]: build sonic vs kvm image (#2269 )	2018-11-20 22:32:40 -08:00
installer.conf	[vs]: Update swiotlb buffer size to support multi-asic VS platform. (#6674 )	2021-02-04 09:04:00 -08:00
platform_asic	Add platform_asic file to each platform folder in sonic-device-data based package (#8542 )	2021-10-08 19:27:48 -07:00
pmon_daemon_control.json	[y_cable] Support for initialization of new daemon ycable to support ycables (#9125 )	2022-01-25 11:10:25 -08:00
README.md	Revert "[gearbox] provide common gbsyncd.service.j2 to start for platform specific gbsyncd docker (#9286 )"	2021-11-19 10:10:55 -08:00

README.md

Changing the virtual device

You can control the hw sku and default factory configuration for the VS image by modifying the content of the file default_sku in this directory.

The format of default_sku is a single line:

<hw_key> <default_preset>

Allowable values for hw_key

hw_key	Device
Force10-S6000	Dell Force10 S6000
brcm_gearbox_vs	Similar to Force10-S6000, but implements a virtual BRCM81724 Gearbox Phy

Allowable values for default_preset

These include "t1", "l2", and "empty". See the file sonic-buildimage/src/sonic-config-engine/config_samples.py for details on how each default_preset value is interpreted.

Changing the hwsku of an existing VS switch

To change the default hwsku for a VS image that has already been built and installed, follow these steps:

Edit /usr/share/sonic/device/x86_64-kvm_x86_64-r0/default_sku. For details, see the section below (Device Specific Documentation)
Edit /etc/sonic/config_db.json, and change the "hwsku" key in DEVICE_METADATA:localhost to match the hw_key used in default_sku. Example:

"DEVICE_METADATA": { "localhost": { ... "hwsku": "brcm_gearbox_vs", ... } }, ...
Reboot the switch
Use "show platform summary" to verify, and follow any steps specific to the platform, as needed, such as those described below for the brcm_gearbox_vs hwsku.

Device Specific Documentation

For general info on building, see https://github.com/Azure/sonic-buildimage/blob/master/README.md

Force-10-S6000

This is the default VS for SONiC. To enable, set contents of default_sku to:

Force10-S6000 t1

To build:

make init
make configure PLATFORM=vs
make target/sonic-vs.img.gz

brcm_gearbox_vs

This sku simulates a device with a Broadcom BRCM81724 gearbox PHY. To enable, set default_sku to:

brcm_gearbox_vs t1

To build (same as Force-10-S6000):

make init
make configure PLATFORM=vs
make target/sonic-vs.img.gz

To verify, install and bring up SONiC. There will be a new gbsyncd docker which is designed to respond to configuration directed towards the gearbox phy "switch". swss will create that gearbox switch on startup after detecting the gearbox is present (this is done by a short lived gearsyncd that runs in the swss docker).

The commands "show gearbox interfaces status" and "show gearbox phys status" can be used to verify the virtual gearbox phy has been created. See https://github.com/Azure/sonic-utilities/blob/master/doc/Command-Reference.md#gearbox for details.