parnassus wrote: If so, it would also be interesting to know if - actually (latest Firmware) - a little HPE 1920 series switch (Comware 5) could act as MAD "assist" device.
After digging a little bit I found that it looks like the HPE OfficeConnect 1920 Switch series doesn't support MAD passhthrough...
Edit: finally found an interesting Configuration Guide recently published about VSF. Details here.
On page 19 there is a nice "VSF HA topology with LLDP-MAD" configuration example (an Aruba 2920 is used as MAD).
Two statements I didn't understood very well when reading the paragraph "Best practices and configuration notes" on Page 23, it's written:
- For High Availability applications, it is recommended to trunk ports across VSF members on different modules (so the guide suggests to terminate each incoming Trunk - here I mean BAGG - within the same unit - no matter if it is Commander or Standby - but do so using ports located on different unit's modules <- this is to prevent disruption on module fault).
- VSF is not compatible with Distributed Trunking and Meshing (so the guide states that an incoming Trunk - again here I mean BAGG - can't be splitted between two units, so between Commander and Standby).
Does this really mean that an access Switch connected to the VSF through a BAGG (made of two or more aggregated ports) must terminate all its BAGG members' links on one and only one VSF member without the chance of distributing/sharing BAGG's member links to both VSF members?
The only permitted scenario is when a BAGG terminates inside the same VSF member (eventually on different Modules, as suggested).