The XGS 136's switch chip mirrors a port, limits a port and switches two ports, with no link changed, 2026-11-11
The XGS 136 has the same switch chip in front of its coprocessor as the XGS 3300, an 88E6193X (queue scheduling). The same day, on the second XGS 3300, that chip was made to copy one port's frames to another, to hold a port's egress to a rate, and to switch two ports to each other without the host. On the XGS 136 the host has kept off the chip's bus since 2026-10-24: the coprocessor's network agent follows the links on that bus, and the host's reads and writes there have made it report ports down that were up (639, 706). The question here: can the host do the same three things on the XGS 136's switch without a port going down, on an appliance whose own way in, F1, is a port of that chip? It matters to anyone who wants a port copied for a capture, a port held to a rate, or two ports switched in hardware on this model.
The whole page, with how it was taken and what it does not show: The XGS 136's switch chip mirrors a port, limits a port and switches two ports, with no link changed, 2026-11-11.
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.