The switch's frame limit set by the network agent on the XGS 136, measured, 2026-10-24
Issue 706: after a reboot of the XGS 136
the network agent reported Port3 and F1 down while frames still came in through Port3, and no
connection through Port3 went into hardware that boot. The boot hook switch-jumbo.sh had just
read and written Port Control 2 of the ten switch ports over the MDIO bus - the bus the coprocessor's
network agent follows the links on. The switch is in multi-chip mode, where a read is a command to
one register and its answer in another, and the agent took an answer of ours for a port's status.
On the XGS 136 it follows links by interrupt, so a state it takes wrongly stays until the link
changes.
The whole page, with how it was taken and what it does not show: The switch's frame limit set by the network agent on the XGS 136, measured, 2026-10-24.
The discussion of this page is held in the project's GitHub Discussions. Showing it here loads giscus from giscus.app and GitHub, and writing in it needs a GitHub account - what that means.