How to configure monitoring on multiple EtherChannel or LACP links?

There may be some environments where the best place to deploy a Sinefa probe is across multiple links that are part of an EtherChannel or LACP configuration.

Sinefa probes are able to monitor multiple links, using multiple bridges on the probe, as a single entity. We call this interface grouping.

The following example CLI configuration creates a group called 'gr_0', adds bridges 'br1' and 'br2' to it and enables monitoring on the group (monitoring on the individual bridges is disabled automatically). Only a single, combined source is shown in all reporting (not the individual links).

  cmd> interface add group gr_0
  (unsaved) cmd> interface.gr_0.interfaces add br1
  (unsaved) cmd> interface.gr_0.interfaces add br2
  (unsaved) cmd> interface.gr_0.monitor enable
  (unsaved) cmd> config save

In many EtherChannel or LACP deployments, it is recommended that Sinefa's carrier state mirroring feature be enabled. Carrier state mirroring will replicate the link/carrier state from one interface in a bridge to the other interface in the same bridge. For example, if the LAN interface of a bridge goes down, the Sinefa probe will automatically bring down the corresponding WAN interface.

This is important in EtherChannel or LACP environments so that neighbouring equipment can correctly add or remove links from the EtherChannel or LACP group based on if the link is up or down.

The following example CLI configuration enables carrier state mirroring on bridges 'br1' and 'br2'.

  cmd> interface.br1 carrier_state_mirror enable
  (unsaved) cmd> interface.br2 carrier_state_mirror enable
  (unsaved) cmd> config save