etwenandClaude Opus 5
b4148c9571
bcm_dsc_scan.sh runs
bcmcmd -n <unit> -c "dsh -c 'phydiag <port> dsc'"
over the whole port list (one 100G port plus the 200G ranges, ~445 in
total) on both units, writes the raw log under <script_dir>/log, and
copies it to /host/hw-eval/jobs. -f names the log (%u -> u0/u1, %t ->
timestamp), -F overwrites, -u picks one unit, -n dry runs, -C skips the
copy.
Two things it deliberately does not do:
- judge success by bcmcmd's exit code. The diag shell rejects commands
and bcmcmd still exits 0, so the script counts
"SERDES DISPLAY DIAG DATA END" markers instead. Same trap
blanton_traffic_linespeed.sh hit.
- resolve ~. Script A calls it after sudo -i, so paths are derived
from $0 rather than $HOME.
Output is one line per port when stdout is not a tty, so it does not
flood the Tera Term log, and it ends with "### DSC_SCAN_DONE rc=<n>" for
a TTL wait to key on.
bcm_dsc_parse.sh is the host-side half: raw log -> <prefix>_lane.csv
(TXEQ / RXFFE / DFE / EYE / SNR per lane) and <prefix>_pm.csv (per
pm_id). POSIX sh + awk, no Python. Lane rows are read by the order of
their bracket groups rather than by fixed columns, so the SDK re-spacing
its output does not break parsing; a row whose group count is not 9 is
reported as UNPARSED on stderr instead of being parsed wrongly.
A full scan is about 10 minutes.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014RetWKFZFG1ZHcitQAyhwM