Thank you for the quick response
.
Yes they did work on 6.1.3.1, but are stuck at "Upgrading" after the updated to 6.1.4.1
The affected RAPs stil have 6.1.3.1 as "running" and "production" images but their "(Provisioning/Backup)" Image Version is not just 3.3.2.11-rn-3.0.1 but also 5.0.4.4 and some even show their "Production Image" as empty!! (so my initial analysis might be wrong after all!). I saw port 21 was open to master and jumped to conclusion.
Yes it was for RAP3 support. I needed to test the RAP3s on a pre-production controller (3200) first, it didn't have enough memory to take 6.2 as it hung that controller. So I got 6.1.4.1 released and did all the pre-production tests which was successful so I upgraded our production units to 6.1.4 . Since 6.1.4 seemed okay I thought I will wait for the 6.2.01 to bed in a bit longer before taking the leap mid year.
I am reluctant to down graded as a few RAPs have presisted and upgraded after many may hours, one has just come up an hour ago! Would it involve these RAPs reflashing, trigging reboots en masse?
Should I just attempt to go 6.2.0.1 anyway, which I prefer?
I will log a support call also.
One question I like answer to is what command will let me know the current usage of the RAP IP address pool? I am sure this is not the case, but didn't know how to check for sure. Also I am wondering if our firewall is restricting the upgrade process somehow, unlikely as I had successly reflashed already upgraded unit without any big delay. Any idea how to check this on the controller end?
Kind Regards,
RK