IW9165D initial configuration problem

[petrk9]

Hello,

I have an issue with my two new IW9165D. Both APs are in URWB mode out of the box and have IOS version 17.14.1. They are powered by POE switch which has trunk configured on that port.

Then I'm following this guide: https://www.cisco.com/c/en/us/td/docs/wireless/outdoor_industrial/iw9167/software/configuration/b-cisco-catalyst-iw9167e-iw9165e-and-iw9165dh-heavy-duty-access-point-cisco-ultra-reliable-wireless-backhaul-software-configuration-guide-17-14-1/m-initia...

When first powered up they get IP address from DHCP and I can login to the web interface. I can see that AP is in provisioning mode and I can turn off IOTOD IW cloud connection (set to offline) and under that I can set Fallback IP address. Once I enter all the information (IP, default gateway, dns), I hit reset to the provisioning and pop-up window asks me if I want to save IP and reload (image1). After reload the AP doesn't have the configured IP address so I can't get to web interface and have to connect to it via console port.

Then there is another problem. The command in the configuration guide for setting static IP adress (configure ip address ipv4 static) is not working. So I found another command after going through all the possible commands.

The command is: configure ap address ipv4 static

So I'm thinking if this command problem is causing the web interface to not setting the IP address and only reloading the AP and falling back to the default IP.

PS: The image attached is from the guide. When I was setting mine it was showing my configured IP address.

[Mark Elsen]

     - Check if this is related : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwj30243
       + Try using latest software version (if feasible)
       + Check console boot process (output) and or review logs just after the AP has booted to get info's on 
          the IP address  being allocated

 M.

[petrk9]

I think the bug you mentioned is not really my case. My AP is connected to IW services but in the end I don't want to be conected to the cloud anyways.

The problem is still present on newest version (17.15.1).

The AP is getting IP assigned with DHCP when in the provisioning mode (as it should) but when I set the IP in web interface it fallbacks to the default 192.168.0.10.

[Mark Elsen]

                     >... After reload the AP doesn't have the configured IP address
  - Make sure to always save the configuration , either to startup-config (when using the CLI) or just  saving changes when configuring the device through the GUI , 

 M.

[Rich R · Accepted solution]

I think you have found a bug. Open a TAC case, they will open a bug for it and eventually it will get fixed in a future release of software.
Meantime - you will have to use your own workaround <smile>

[clarkvyborg]

I used to see this fallback to 192.168.0.10 process when I worked with Volo/Endo units.  Our work around was to set the radio to offline mode and then after it cycled configure the radio the way we wanted.  We would weird interactions in the field when the radio received DHCP that we sometimes were able to resolve and sometimes we rolled a truck to fix.