@NightShade1 wrote:
Hello i got this odd issue
This client is using the DHCP server of the Controller to give the APs an ip address.
Whenever they use the DHCP server of the controller to give IP addreses to the APs
The APs takes up to 3 minutes to show in the console which is really odd.
If i do the same with another controller it takes up to 36 seconds to show int he console.
If on the non working controller i put the AP with static ip address it takes up to 36 secs which is normal
If i put it to use a DHCP server a windows one for example it takes up to 1 minute.
If i put it to use the DHCP server of the controller it takes up to 3 minutes
If i try the same on another controller with the same code in all the options the AP takes up to 36 seconds to show in the console!
The AP is connected directly to the controller(there are no swithces or anything between them.
Its a new controller
I tried many differnet APS so its not the APS.
Anyone have seen this happening???
It just not make sense...
Cheers
Carlos
Carlos,
The controller DHCP automatically puts in a DHCP Option of 43 for access points which it assumes is the controller's switch-ip. As you can see below: I did not put in 192.168.1.3; it put it in automatically. Make sure that is the ip address that you want your access points to connect to, or if it is even accessible, otherwise, change the switchip..:
(192.168.1.3) #show ip dhcp database
DHCP enabled
# a
subnet 1.1.1.0 netmask 255.255.255.0 {
default-lease-time 15;
max-lease-time 15;
option domain-name "selabs.com";
option vendor-class-identifier "ArubaAP";
option vendor-encapsulated-options "192.168.1.3";
option domain-name-servers 192.168.1.25, 8.8.8.8;
option routers 1.1.1.1;
range 1.1.1.2 1.1.1.254;
authoritative;
}
That may not be the root of your issue, but it could contribute to the issue you are seeing. That is the main initial difference between using the controller vs. another DHCP server.