Hi, i did all different tests from linux- to linux-system (iperf(3)) and with the internal tool.torch and tool.ping between the interfaces between the 2 routers (both SFP+4= Port5) to the other side of the canyon.
The interfaces itself said, that they are at 10G-Speed.
Signal level, power, snr, etc is okay according the modules? They report similar values or different? Try to replace the modules if you have spare ones.
Uuuh, I’d made an Update to 6.49.19 long-term and have to learn more about it. on one side there is an additional “bridge” at the interfaces-page. I will be back, after i checked what is going on. Thanx
CPU should be a couple of percent maximum when just being used as a switch. Do the bridge ports have hardware offloading enabled (Hardware Offload ticked under General tab for each interface under Bridge>Ports, or yes in HW column from /interface bridge port print) and active (H flag in column before interface name under Bridge>Ports, or from /interface bridge port print)
L3 HW offloading is only available in ROS v7. But it doesn't apply if the use case is using CRS devices as switches (which are L2 entities). It is important, though, to configure bridge and ports in the way it allows switch chip to do the work.
If, OTOH, devices are used as routers (i.e. physical interfaces, involved in data transfer, are not members of same bridge), then ... CRS are routers with shitty performance unless they are properly configured for L3 HW offload (and then you're back to the beginning of my post).
Yes, used as switch (L2 entity, bridge functions offloaded to ahrdware as indicated by "H" flags). And it's unclear from information, provided by @DirkK , how he is using the two devices (as switches or as routers).
If just switched, you likely don't need the CRS305 at all.
So perhaps upgrade to 7.20.8 and rejig with hardware L3 offload.
I would be hesitant doing this cold without prior testing on a non-live/test system though.
On thinking about it some more (it takes a while )
You can probably just upgrade the near end,
and making it fast is possibly as simple as then enabling l3 hw offload on it.
Make sure you have your configs backed up somewhere (not only on router)
before doing the upgrade.
When that end is working ok, visit the other end and do the same.