On 25.01.2020 17:23, Andrew Lunn wrote:
EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safeLets say that the link between H1 and H2 goes down: +------------------------------------------+ | | +-->|H1|<--- / --->|H2|<---------->|H3|<--+ eth0 eth1 eth0 eth1 eth0 eth1 H1 will now observe that the test packets it sends on eth1, is not received in eth0, meaninf that the ring is openIs H1 the only device sending test packets? It is assumed that H2 and H3 will forward them?
Horatiu, please correct me if I'm wrong, you have been spending more time with the standard. It is only the manager/MRM (in this case H1) which sends test-frames. The other nodes (the MRC's) must forward the MRP-test frames, but only on the ports which is part of the ring.
Or does each device send test packets, and when it stops hearing these packets from a neighbour, it assumes the link is open?
No. This also means that most non-MRP aware switches can properly act as MRC with HW offload. It is good to have that in mind when reviewing the netlink interface. It is worth mentioning that the client shall send a frame if they see a link up/down on one of the ring ports. This is to allow the manager to react faster. Also, in this first patch we have only defined the MRM and MRC roles. In future version we would also like to support a MRA (auto manager), where the clients is monitoring the test frames, and if there are no manager (it disappear, or they are all MRA) then they can negotiate who should take the role as manager. /Allan
