We've got a test Force 180 antenna configured as a NAT, with a cnPilot R190W connected to it. In cnMaestro, the cnPilot appears under the corresponding SM.
We have another Force 180 configured in bridge mode, with VLAN for management. The same VLAN is added as a member, and is accessible from the management inteface configure on a R190W. They are on the same VLAN, and same subnet. Both are accessible. But in this scenario, we are unable to get the R190W to appear under the SM in the tree... Also tried to make the management interface on the SM accessible via Ethernet + Wireless, to no avail. Anyone knows what is the configuration required to associate a cnPilot to an SM in the device tree, so that we can configure this properly?
I believe this problem stems from the network layout, rather than a configuration issue, but either way, finding a solution would simplify the CSR's work. Plus, if our RGs (R190s) don't show up under the SM in the three and in cnMaestro diagrams, we could instead use someone else's WiFi/RG. The benefit of having the SM and R190s grouped together and displayed together is what brought us to your solution.
We expect this network to grow to ~100 subs, and wanted to keep things lined up, so we decided to have all our IPs statically assigned, for management and internet. We NAT management traffic only, Internet addresses are public. A client (client 100 for example) will have the same .100 appended to all addresses, be it SM management, RG management, and Internet. We segregate management VLANs based on the type of devices, and route all management VLANs through a software-based router on a VM for traffic management, NATting, and remote VPN access.