Configuring static IP on Cisco AIR-CAP2702I-E-K9.

[n ochieng]

I need to configure static IP on the BVI1 interface but the interface keeps resetting. I get the notification  %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP. 

[Flavio Miranda]

@n ochieng 

 This is a capwap AP as per the logs. You need to use capwap command

capwap ap ip <ip address> <mask>  <default gateway>

[n ochieng]

@Flavio Miranda , Thank you for the feedback. I tried but none of the interface has the ip I configured. 

[Flavio Miranda]

Do you know the IP address of the WLC ?

You can use

capwap ap primary-base   <WLC IP address>

And, if the AP is not on the same network as the WLC, you need to use gateway on the first command  I sent

[n ochieng]

I don't have a WLC, i intend to convert it to autonomous. 

[Flavio Miranda]

OK.

 Try to use the commando

debug capwap console cli

[n ochieng]

I tried that too. I keep getting "  %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP." 

[Flavio Miranda]

Do you have the IOS for autonomous AP?

Try to transfer the IOS to the AP 

archive download-sw /force-reload /overwrite tftp://

[n ochieng]

I do have the IOS, the main issue is the AP loses the IP hence cannot transfer any file. 

[marce1000 · Accepted solution]

  - @n ochieng wrote : >...I do have the IOS, the main issue is the AP loses the IP hence cannot transfer any file. 
                                   Then factory reset the AP by pressing the mode button for longer then 20secs ; and follow this procedure afterwards : https://community.cisco.com/t5/wireless-mobility-knowledge-base/access-point-rommon-recovery-ap-prompt-recovery-example/ta-p/3119495

  M.

[n ochieng]

@marce1000 , thank you for your feedback. configured the AP as indicated. I got the notification below: " Connection timeout" . I believe I'm supposed to be able to ping the device after set IP_ADDR 192.168.40.20 , set NETMASK 55.255.255.0  and set DEFAULT_ROUTER 192.168.40.254, but I cannot ping it. 

[marce1000 · Accepted solution]

  @n ochieng wrote :                                       > ....but I cannot ping it. 
                               The only thing I can suggest is to verify the network parameters being set on the AP , and also check the logs on the tftp server to check if there is a connection attempt from the AP ; you can also set the tftp server in debugging mode , if available. The above is useful in the sense that I think , that the network stack on the AP is only being made active when the tftp server is being accessed from the AP. Hence checking the connection logs on the tftp server is strongly advised , 

 M.

 M.

[Rich R]

>  I believe I'm supposed to be able to ping the device after set IP_ADDR 192.168.40.20 , set NETMASK 55.255.255.0  and set DEFAULT_ROUTER 192.168.40.254, but I cannot ping it.
Maybe it's just a typo but your netmask is missing a leading "2"?

If your TFTP server is on Windows did you disable Windows Firewall or allow the TFTP through the firewall.  You should still be able to ping the AP though.  Did you initialise the ethernet?  Is the port up?  You keep showing little pieces of screenshot - never a complete log of your console.  Copy the complete output of the console from the time the AP is powered on including every command you typed and every response you got back from the AP.  Paste the output into a text file (.txt) and attach the text file to your reply here so we can take a good look at exactly what is happening on the AP.

Do the TFTP server logs show any attempt to download a file?

[Flavio Miranda]

debug capwap console cli should work for you but dont run conf  t first.

[Flavio Miranda]

Dont mind, this will not work until you fix the DHCP renew behavior.

 The command debug capwap console cli should fix it.

One last attempt is to put the AP in rommon mode and do the IOS transfer from there.