Example validation

Each example carries a label saying where it has been run. The label tells you how far you can trust the output shown with it.

Hardware-validated

Run on: a real Trident 3 switch with this release.

Output: captured from that switch, unchanged except that outputs longer than 40 lines are cut and end in ....

Keep in mind: port names, counters and table contents are that switch’s, not yours. The switch is a Seastone2 with a small SONiC configuration:

• ports ce0–ce30 and xe0–xe4;

• VLANs 902 and 3999;

• PortChannel2 on xe0–xe2;

• an IPv4 address on Vlan902.

Examples that need a link partner, such as PRBS or FEC changes, also show output from a second Trident 3 switch, a Dell S5232F-ON with the same software, at the other end of a 100G link. Some how-to examples change ports, VLANs and tables on the lab switch; the state was put back afterwards.

VMM-validated

Run on: a Trident 3 simulator running the same SONiC software.

Output: captured from the simulator. The syntax and the shape of the output are real.

Keep in mind: commands that read hardware state, such as link status, SerDes diagnostics, temperatures or counters, show the simulator’s values, not a real switch’s.

Unvalidated

Run on: nothing yet with this release.

Output: usually only the command line is shown. Where output is shown, it comes from another system or release.

Keep in mind: the syntax is believed correct, but check the output on your own switch before relying on it.