01-14-2022 03:26 PM
vwlc does not ping the ap or gateway in my lab
I downloaded the AIR 9.8.2.170 ova, and I'm trying to associate an AIR AP CAP3502P-N-K9. However, I got lost in concepts:
1st - I can only access the GUI of my lab network if I add its IP in the service port, and not in the management.
When I added it to the service port, I accessed the box, configured it, but the AP did not join due to dhcp/subnet conflict.
When I returned to the configuration in the manager, I can see the ap with the command "show ap summary", but I can't ping the ap or my gateway from within the CLI/VM, what's missing?
My default lab network (gateway + dhcp on native vlan = 1): 172.16.1.1
Modem >> RV42 >> SW + AP >> PC with VM in bridge mode (receiving ip from dhcp)
NOTE: I can ping to vwlc, but I can no longer access it via GUI/https or via ssh. How do I solve this problem?
01-15-2022 11:38 AM
Hi
Try to enable LAG on the WLC side our disable it in case is enable. You can also add an addicional virtual interface on the VMware side and then use one for Management e one for Service port.
01-29-2022 12:43 PM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide