Controller Based WLANs

 View Only
last person joined: one year ago 

APs, Controllers, VIA

A branch office controller fails to connect to the master via DHCP provisioning 

Apr 21, 2015 02:43 PM

Problem:

A branch office controller is provisioned with Master controller IP and country code via an DHCP server, but it seems the information responded from the DHCP Offer packet is not correct or not enough, it fails to connect to the master.



Diagnostics:

To troubleshoot this problem, please check out a few things:​

  1. Is the uplink port in a VLAN which has DHCP client enabled?
  2. Can the controller get an IP address from the DHCP server?
  3. Does the DHCP offer packet have DHCP option 43 & option 60 included?
 


Solution
  1. By default, only the last copper port of a brand new branch controller is in the default VLAN 4094 with DHCP client enabled, such as port 0/0/3 in a A7005, 0/0/15 in a A7010, 0/0/23 in a A7024. To get an IP address and provisioning infovia DHCP, make sure the last copper port is used to reach the DHCP server.
  2. To get provisioning info from an DHCP server, the server has to have DHCP option 43 and option 60 configured.
            •Option 60 needs to be configured as Text “ArubaMC”
            •Option 43 needs to be configured as Text “<IP>,<country code>” of master, such as “10.163.188.38,US”.
 
For example:  Master IP is 10.163.188.38, Country Code is US

#show ip dhcp database

# vlan20

subnet 20.1.1.0 netmask 255.255.255.0 {

        default-lease-time 43200;

        max-lease-time 43200;

        option routers 20.1.1.1;

        option user-option-43 code 43 = text;

        option user-option-43 "10.163.188.38,US";

        option user-option-60 code 60 = text;

        option user-option-60 "ArubaMC";

        range 20.1.1.2 20.1.1.254;

        authoritative;

Statistics
0 Favorited
0 Views
0 Files
0 Shares
0 Downloads

Related Entries and Links

No Related Resource entered.