NSa4700 Active/Active HA and LACP / LLDP capabilities
I've become somewhat confused by a certain number of discrepancies between the various pieces of documentation that I've found, relating to a pair of NSa4700's I'm trying to configure/integrate.
states on Page 40:
"The dynamic Link Aggregation Control Protocol (LACP) is currently not supported. Dynamic, through a protocol to bundle Ethernet ports such as IEEE LACP or Cisco's PAGP,is another way of configuring Ethernet port channels. In this method, LACP or PAGP packets are sent out on the port."
and yet in this document apparently published on the same day:
has an entire section dedicated to LACP configuration.
In addition, the Switching document also has an entire section dedicated to LLDP and its various TLVs.
Meanwhile in this document:
there's a discussion of the various HA modes, but it's unclear which platforms support which modes. In particular, I've found other documents which indicate that the NSa4700 supports Active/Standby, but seemingly not any of the Active/Active HA modes.
To try and de-confuse me therefore, could I ask the following:
* Is there an up-to-date table on the website somewhere which details all the hardware models, and which HA modes are supported by each under which Licences?
* Does the NSa4700 support Active/Active Clustering at all, and does this need some form of extended Licence?
* Does the NSa4700 support Active/Active DPI at all, and does this need some form of extended Licence?
* Does the NSa4700 support LACP on any or all of its interfaces?
I've seen various documentation which implies that it is available on 1G interfaces, but not 10G, but this may be historical.
* On an Aggregated interface which doesn't use LACP, does traffic originate from the same Source MAC address on both legs, or from per-leg MACs, and does the answer to this change if HA is set to use a Virtual MAC?
* As above, but what happens with Source MAC's if LACP is available, and in use?
* Is there any Link-Local traffic on an Aggregated interface?
The implication from the Switching document is that there will be per-leg Link Local LLDP traffic, but I'm not sure. There might even be LLDP traffic associated with the logical aggregated Interface, but I would have thought that this goes against the spirit of LLDP being entirely Link-Local.