12-03-2018 03:42 AM
I'm trying to get our AirCubes configured so that we can access them via management VLAN. For example, our core network is on 10.100.200.x and the management VLAN for a particular mast is on 10.100.300.x with the core router being 10.100.300.1.
On our customers with Edgerouters, we simply add a static route to 10.100.200.0/24 via 10.100.300.1 and that works fine. However if I try and add a similar static route to the Aircubes, it tells me that the gateway must be within the LAN range of the router.
Is there any way to set this sort of static route up on the AirCubes?
12-10-2018 07:02 AM
If your management network is 10.100.300.x then add management VLAN from this pool to airCube and you will access airCube on mgmt vlan from WAN side.
Data traffic can be configured different (DHCP ?)
12-10-2018 01:57 PM
So the 10.100.300.x management VLAN is for that particular mast so the Aircube is reachable by that mast's router but as the cube doesn't have a gateway on that VLAN it can't reach the management VLAN in our core (10.100.200.x). With the Edgerouters I simply add a static route to tell traffic for 10.100.200.x to use gateway 10.100.300.1 which does the job but I can't seem to do that with the Aircube.
12-11-2018 07:33 AM - edited 12-11-2018 07:48 AM
This works for us at the moment -- purely because EdgeOS doesn't have proper separation of routing for management and data planes. At some point, airCubes will need to get smarter about handling double DHCP assignments.