Repository navigation
v2.207.0
A polarity or Tx disable change no longer restarts every Data Path
CMIS Table 8-77 lists 10h:129-142 as Lane-Specific Control, "independent of the Data Path State machine or control sets". Polarity and Tx disable take effect when written and need no Apply. The DataPath panel writes them through its Apply button, which always asks for an Apply. The server treated "no staged configuration changed" as a request to re-commission. So flipping one lane's polarity restarted every Data Path on the module; on a 2×400G module both 400G ports dropped. The manual has claimed otherwise since v2.10.1.
Now
- A request whose only change is a lane control (polarity or Tx disable) is written without an ApplyDPInit trigger. It answers
applied_lanes: [], and the page says no Data Path was restarted. - Pressing Apply with nothing changed still re-commissions every Data Path.
- A change to the staged configuration applies only the Data Paths it touches.
- DP Deinit changes keep the order introduced in v2.200.0.
- The manual's three passages saying Apply writes 0xFF and restarts every lane are rewritten.
2967 end-to-end tests. 32-bit build, as CH341 requires.