That's why I asked "Why are you running 4.3.2 on just one station? Is it an AC station?"
I assumed that the one station you were having problems with, running 4.3.2 was an AC client and thus not compatible with a legacy AP running 3.5.6, as shown on that compatibility list.
So yeah... WHY again are you trying to get a legacy client running 4.3.2 to connect a a legacy AP running 3.5.6? I wouldn't not run this configuration if I were you. When running an all legacy network, it's advised that you just use 3.5.6 until 4.4 comes out.
I wanted to proceed by steps. Since the configuration, as shown in the diagram above, allows it, I started with supplying the force180/200 to installers with fw 4.3.2
Because among the several hundred bts present, we have made some new bts with only the 3000 series as AP.
Since the intent is to have a mixed (n/ac) network, I want to take out the old series antennas and buy only the 300. But the technician must be able to hook his force180/200, in the case of a bts 3000 is reacheble
The second step is to update all the APs of the network to 184.108.40.206, making it possible to connect the future 3000 stations
But, given the presence of the problem tonight we will start updating all the APs
The next step is to update all the stations. But here it will take months, because there will always be: - the customer with the antenna turned off during my pdate scheduler - the customer who uses it only during the holiday period, therefore off for months - all the various force200s in stock of the several dozen installers
- customers who have terminated contract and turned off antenna. So I wait to update until the technician does not go to uninstall it and reuse it
Therefore, the 4.3.x version must necessarily coexist with the 3.5.x version I don't have a magic wand to turn them all instantly to 4.3.x
I have an issue with the roll back FROM 4.3.2 BACK TO 3.5.6 One of my guys assuming that the new addition of 4.3.2 to our CnMaestro server meant fresh firmware pushed it out in one big update(added for future 3000 implimentation), problem being that ALL of our ePmP are legacy 1000/2000. I was able to roll MOST of the equipment back, but still have radios that say they need power cycled before the update can be done. some have been power cycled from the GUI but the message remains, other have been powered down at the source and left for 5-10 min and still the message remains. How do I fix this "Please perform device reboot before Upgrading software" error?