bsv

Broadcom SAI Version: show the SAI, OCP SAI, SDK and Cancun versions

bsv

Show the SAI and SDK versions of the running build.

bsv is handled by the SAI’s drivshell> front-end (see The drivshell> front-end), not by the SDK shell. It works only when it is the whole line, typed exactly in lower case. BSV, bsv with arguments or a trailing space, and 0:bsv all reach the SDK shell, which answers Unknown command. For the same reason bsv is not listed by help and cannot be used in rcload scripts. BCMSAI VERsion prints the same information and has none of these limits.

It prints one line with the four versions and, when the switch has a recorded cold-boot version, a second line with it:

BRCM SAI ver: [15.2.1.0.0.0.26.3], OCP SAI ver: [1.18.1], SDK ver: [sdk-6.5.35-SP1], CANCUN ver: [06.15.00]
BRCM SAI cold boot ver:[15.2.1.0.0.0.26.3]

A third line, BRCM FIPS ver: [<version>], appears only on builds with MACsec FIPS support.

BRCM SAI ver is fixed for a given SAI build. Chip families other than Trident 3 print an NPL, LT or EDK ISO FW field instead of CANCUN. The command is read-only.

Hardware-validated

drivshell> bsv
BRCM SAI ver: [15.2.1.0.0.0.26.3], OCP SAI ver: [1.18.1], SDK ver: [sdk-6.5.35-SP1], CANCUN ver: [06.15.00]
BRCM SAI cold boot ver:[15.2.1.0.0.0.26.3]

Further reading

bcmsh.md (published as https://kamelnetworks.github.io/sonic/bcmsh.html), led.md (SONiC on Broadcom: LED debugging), sonic-mgmt test suite files invoking bcmcmd (19 files).