Controller Based WLANs

Why shouldn't we connect a brand new / factory reset controller to the network before initial config?

by on ‎06-29-2014 11:41 AM

Environment : This article applies to all Aruba controllers and code versions.

 

A controller can have default config under one of the following cases:

1. It is a brand new, out of the box controller.
2. Controller was write erased and rebooted.
3. It is a replacement unit from Aruba after the RMA.

In all of the above configs, the controller has an active DHCP server scope for subnet 172.16.0.0 /24.

This is to facilitate the initial configuration via web user interface. Desktop or laptop connected to any of the controller wired ports will get DHCP lease from 172.16.0.0/24 scope. After this, the user can launch a browser session to 172.16.0.254 for the initial configuration wizard.

This DHCP server is active on the controller until the controller is configured and rebooted.

If we connect the controller to the network before reboot, it will start replying to DHCP discover messages and give out leases in that subnet which can cause duplicate IP addressing and connectivity issues.

 

It is safe to connect the controller only after doing initial config and rebooting the controller.

 

http://www.arubanetworks.com/controller_setup_video.html

Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.