Customer Service Center

Objective/Summary Lost manchester lock The Manchester time is the timestamp received from another chassis using chassis-chassis chaining. Environment/Versions Synching chassis with ETR as well as Daisy chain Procedure   Before 5.00 release (07/26/2019), try the following: enableusb = off this USB admin command was added to controller 3 ​It was put into play due to something interfering with chassis sync using anything other than Internal. Such as any External Time Reference, including daisy chaining chassis. It was interfering with delorean (sync chain) functioning. When daisy chain two chassis, both chasses need to have the PCIe endpoint passed through.  There are significant performance issues when USB is passed through.   Starting 5.00 release the enableusb command seems to be discontinued (as per CIPNCD-20960), so this "workaround" won't work on these release, instead you may need to check: Check the setup just to validate there is NO extra sync cable dangling off any of the chassis on the chain, basically there should be NO cable connected to the IN interface of the Master chassis, and also no cable on the OUT interface of the last chassis. Make sure all the timing interconnect cables are the same length please. We have seen some issues when having a mix of 1 meter and 2 meter. Ended up with 1 meter, just make sure all cables are same length. Notes logfile_syncd.log you will see "Manchester vs. Internal Timestamp failure" GUI Logs 7/1/2020 06:00:33 .1 Warning Other chassis 10.108.8.20 event: out-of-sync: Lost manchester lock Refer to KNI16705 - Spirent TestCenter: 5.19 - 400G Appliances go Out Of Sync in daisy chain setup when running rfc2544 (Lost manchester clock message)