hex0101 no loss of modem sync, same goes for the maintenance that was on 5/15 @ 12:30 am.
Gateway Restarted 2-3 hours after hitting 30 days of uptime on 5/14. So after 720-722 hours of uptime. No change in firmware version. Rebooted though. Loss of sync also doesn’t cause a reboot on the XB gateway’s in my experience, and neither do the codewords reset. A restart will reset the codewords though.
Gateway Restarted on 5/15 at 3:58 am for firmware update, moved from CGM4331COM_8.3p1s1_PROD_sey (If I recall) to CGM4331COM_8.3p12s1_PROD_sey. Minor bump, but still on 8.3p.
Not sure if they have begun FDX deployments on N+X architecture, especially at scale. (probably not) Still some firmware bugs with the FDX amps that are apparently happening. Heck, the SoC (system on a chip, processor) on the FDX amps are more like the RPD itself due to how FDX works. A lot of software magic is needed to make these work no doubt, especially at peak performance. For now, they can run in Mid-Split mode!
Even during normal FDX operation, traditional 3.1 channels will continue to behave as they always have. If the FDX channels mess up, the modem simply goes into partial service mode and uses 3.1 on the downstream and the sub-split and mid-split upstream from 5-85 MHz. Comcast documentation mentions this as “partial service”. May even require a modem power cycle to get the modem to re-bond to the FDX channels currently, but with time that will likely get optimized more if it hasn’t been already.
