2504 autoinstall fails with code 7.4.100.60 and 7.5.102

Question

                   I am running into an autoinstall issue with our 2504 WLCs. Up to code version 7.2 I was able to use autoinstall to prime the WLCs by downloading the config from a TFTP server.
After upgrading to 7.4.100.60 the autoinstall fails because the WLC becomes unreachable after it received a DHCP address, gateway, option 150 and the bootfile. If I configure the controller manually, all is working as intended. Before upgrading to code version 7.4, we installed the FUS update 1.8 as described in the release notes.
The DHCP parameters are correctly handed out and I see the IP in the DHCP bindings with the management interface MAC. The WLC accepted all the parameters and in the console output the autoinstall is attempted as intended.
Pinging the DHCP - IP of the WLC is unsuccessful and thus the WLC cannot reach the TFTP server. A ping to a local broadcast shows 2 other clients (APs) on this segement but not the controller. The switch the WLC is connected to is a 3750 with IOS 12.2(58)SE2.
SW2#sho ip dh bin
Bindings from all pools not associated with VRF:
IP address          Client-ID/              Lease expiration        Type
                    Hardware address/
                    User name
10.80.1.57          f47f.35b6.9080          Mar 01 1993 04:40 AM    Automatic
10.80.1.126         0150.3de5.d9d4.e1       Mar 01 1993 04:58 AM    Automatic
10.80.1.127         01c8.9c1d.af2c.97       Mar 01 1993 04:59 AM    Automatic
SW2#sho arp | i 9080
Internet  10.80.1.57              0   f47f.35b6.9080  ARPA   Vlan8
SW2#sho run int g1/0/16
Building configuration...
Current configuration : 179 bytes
interface GigabitEthernet1/0/16
description WLC8-2504
switchport trunk encapsulation dot1q
switchport trunk native vlan 8
switchport mode trunk
spanning-tree portfast
end
I did not find anything in the bug navigator but this might be due to the fact that hardly anybody uses autoinstall.
Best
   Patrick

Answer 1

Hello Mario,
As per your query i can suggest you the following solution-
Please check the powering options-
• 802.3af Ethernet Switch
• Cisco AP2600 Power Injectors (AIR-PWRINJ4=)
• Cisco AP2600 Local Power Supply (AIR-PWR-B=)
and Power Draw
AP2600: 12.95W
Note: When deployed using Power over Ethernet (PoE), the power drawn from the power sourcing equipment will be higher by some amount depending on the length of the interconnecting cable. This additional power may be as high as 2.45W, bringing the total system power draw (access point + cabling) to 15.4W.
Hope this will help you.