I'm looking for some sort of explanation of the 3 interfaces in a vSZ-H deployment.
I'm assuming it basically boils down to the following:
Management: What you connect to to configure Cluster: cluster only traffic, can be an empty vlan with only the cluster interfaces in it Control: What the AP's connect and talk to for provisioning and management AP traffic
Is that correct? If so, why do the Management and Control interfaces share a routing table at all? You have to pick one to use as a gateway but I'm not clear which one to choose and what circumstances would make me pick one over the other.
In our setup we'll have central controllers with all our AP's out on sites in different subnets, but those that need to manage it will also be in different subnets.
In our case all our AP subnets can be included in a single /16 route statement so I'm guessing I should set the management interface as the default gateway and add a route to the control interface to include that single /16. Is that correct?
Before someone links the getting started guides I've gone through them, they don't explain the purpose of these interfaces, they just say to give them IP addresses, which isn't even remotely helpful sadly. When configuring interfaces giving them IP addresses seems obvious, it would be much better to explain their purpose of the interface and why it needs a separate IP address/interface in the first place.
Sorry, this is just very frustrating trying to find even basic architectural information about this product or some basic design guides for deployment seems impossible
So, an update. The 3.5 Getting Started Guide has some useful info but still lacks some basic details. I hadn't found the 3.5 one before only the quick start guide and an older Getting Started guide.
My description of the interfaces seems accurate, although I still haven't found any documentation that tells me which interface to point the actual AP's at for provisioning. I'm assuming it's the control interface but that's a guess
The other thing that's sadly lacking is a simple description of configuring it with a single interface only. The guides indicate you are prompted with a question during CLI setup of if you want a single interface or triple interface system but I never got that question. You appear to be able to force a single interface system by just deleting two of the interfaces installed as part of the virtual machine provisioning.
So far that's been my solution to all these problem. I've just created a single interface install as we wont' be tunneling any significant traffic anyway and even with three interfaces they would all be going out the same 10Gb trunk anyway.
Now I have to work out how a vSZ-D connects and works and how to configure that so what traffic we do tunnel I can route out the right gateway