Aironet 1850 configuration loss

[ExailAero]

When stopping power supply during the starting phase on Aironet 1850 (between 190 and 210 sec after start) the AP loose is configuration and returns to factory settings. The prompt is "Enter Administrative User Name (24 characters max):".

The Ethernet link is not activated and whole configuration have to be done through the RS232 maintenance interface.

Does someone encouter this problem and have an idea how to prevent it (except without cutting the power of course) ?

Thanks

[Flavio Miranda]

Hi @ExailAero 

  Considering that you are saving the config,  this is a very unusual problem for AP, actually first time I heard.  This problem is not unsual for switches, for example.  I would try to change the AP IOS and hopefully this is not a hardware problem.

[ExailAero]

Hi,

Unfortunately I tried with several version of IOS (8.10.162.0, 8.10.171.0 and the last one 8.10.185.0) and had the same results. When I stop the power supply before 190s the AP restart well with his config but somewhere between 190 and 210s the configuration is lost. This is very unconvenient because the RS232 maintenance interface is not cabled on the final environment of the AP Aironet, so it have to be unmount for reconfiguration.

[Flavio Miranda]

 I am afraid this is a hardware problem as AP, as far as I know, does not have a boot system to configure like we do with other devices. So, the configation should be kept after saved.

 If you can replace it, it is recommended to do so.

[ExailAero]

Hi,

I was able to reproduce the problem on two different AP Aironet 1850, so I'm afraid replace it will not solve our problem.

[jamesbos96602]

i ran like prob with other ap now i got wounder if related. what i found no matter what u did u cant save config file on 4 ap's they all do same u have del the startup-config and then resave it now, let me state i not played around with 1850 . but i just help cisco to fix wism2 card,  and cisco wants be find out why a router is pulling data from there servers .  so i might just have get one off ebay. and get with cisco to fix this , even if i wrong in what i first said there is reason this going on and that reason needs be discover and work out with cisco so main quistion has any one ever del the starup-config and then save the new config in its place and then unplug the unit ? that is where i would start . if this happens work please post it here . other whys i get one and figger out why not working  i find most all of probems i run in to and cant fix is becuase there codeding probems and only the builders can fix it

to say hardware  unless some one had del all save config files and resave them i would say startup-config is lock cant be change so has be del this how i got around the probems on my ap as it did same thing is same probem i cant say u all can test my idea and see if it works  then we move back to cisco to fix the firmware