01-02-2012 06:04 AM
I have little experience setting Controller (Aruba 620 with 6.0.1 firmware) but I could get VIA client authenticate with the controller. However I had an issue where the LAN subnet is not advertise and not reachable from VIA. Attached is the simple network sketch showing you that the controller is placed in DMZ network.
Once VIA authenticated with controller, it received 172.16.100.50 from the DHCP pool. It can never reach the web server in LAN port 4 subnet (which is 172.16.1.50). When I check VIA client route table, the subnet 172.16.1.0/24 is not injected into OS so I manually add it myself but not working either.
Does anyone have clue with this issue?
Thanks in advance.
Solved! Go to Solution.
01-02-2012 06:25 AM
Your infrastructure would need a route for 172.16.100.0 pointing to the management interface of the controller. Optionally, the controller would need a VLAN interface in the 172.16.100.0 subnet, as well.
*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.4 User Guide
InstantOS 8.3 User Guide
Airheads Learning Videos
Aruba Central Documentation
Sign up for Security Alerts
Aruba Technical Webinars