Just managaed to read the other thread, but still need clarification on it please.
I see the following message posted:
2. You do not need to trunk up all VLANs to the MM, the MM only need to be routable from and to the controllers the MM is managing. So the MM in effect only needs one VLAN/network minimum. Now, you CAN trunk up multiple VLANs to the MM depending on your use case, etc. But otherwise, it only need one IP and one VLAN (or two IPs if you are doing VRRP).
I understand your point that in many installs we would only be using one interface, which is the management network and making the mgmt-VLAN available between the MC and the MM for communication.
What is the actual purpose of the data interfaces? what traffic uses this interface when both the MGMT interface and data interface is deployed? Just want to make sure I understand why two interfaces could be deployed if there ever is a need for it.
Looking at the below point is the data interface used depending on how the ESX hypervisor's is connected to the network?
4. LACP is never required for any Aruba product, but some people like to. For VMM, LACP is involved when your ESX hypervisor's vSwitch is connected to multiple NICs. VMWare tries to make it easy with NIC Teaming, however, virtual switches with firewalls won't just accept frames from one or the other, so you just have to specify that that vSwitch's multiple NICs be configured between the hypervisor and uplink switch with LACP (instead of NIC teaming with no config on the upstream switch). This is also common when carrying virtualized switching products across a vSwitch with multiple physical uplinks from the hypervisor, and is more efficient.