in the SM (NAT mode), when I try to set the VLAN ID of Separate management interface, it return the error:"Current parameter value should be not equals to "Management VLAN ID" value"
I have the necessity to set the same VLAN on both interfaces (WLAN Data and Separate Wireless Management Interface) , how I can do this?
If you want to use the same VLAN for management as well as data, then DON'T Enable Separate Management Wireless Interface. This way the VLAN you configure under Configuration->Virtual Local Area Network (VLAN) -> VLAN (Management + Data) will be used for both Management and Data.
Yes, but I have the necessity to have 2 ip: one for management (static), and one for data (in dhcp from pppoe concentrator) both on the same VLAN. In this case, I have the ability to reach the SM (from wireless interface) even if the pppoe connection is down.
This is an older post, but I have the same question. Is this possible to accomplish with ePMP 1000 set as SMs? I.E. - WAN IP config and Separate Management IP config both using the same VLAN? Or is this not possible?
If VLAN(Data + Management) is set to -enabled-, and if 'Separate Management IP' is configured, but you were to leave the 'Separate Management VLAN' setting as -disabled-, does the SM then apply the VLAN tag that you defined under 'VLAN(Data + Management), or does it apply -no- tag at all?
We've tried this type of config on one SM today, and from how our cut-over attempt went, it looks like the ePMP SM does not seem to have the ability to configure both the WAN IP settings and Separate Managment IP settings while also tagging these IPs on the same tagged VLAN.
If you leave the 'Separate Management VLAN' setting disabled, that separate private IP appeared to come back untagged and we lost remote access, but if you try to enable the setting and use the same tag on both the Public and Private, the SM does not accept the setting.
Its usually best to have a seperate management vlan away from customer traffic. This allows you to prioritize your access to the device in a situation where customer flooded traffic causes issues accessing the radio. It also thins your broadcast domain which can be problematic for performance.