We had this behaviour on a batch of 2702s, the firmware that was preloaded had this bug that went away once the associated and upgraded. It's a right pita changing the port config to get them to connect, then reverting it later, but not as bad as the other firmware bug causing APs to use the wrong MAC address until they upgraded.
On 11 August 2015 at 13:21, Lee H Badman <[email protected]> wrote: > Wondering if anyone has seen similar with Cisco APs: On switchports that > have been fine for other Cisco APs, a run of new 3702s are going into error > disable. If you turn on the ability to see why in the switch, the APs – > only when new out of box—are sending BPDUs to ports that have Spanning-Tree > Portfast on as a rule. > > If you remove portfast, the new 3702s go off to the WLC just fine, get > updated for code, and then work as expected. You can restore spanning-tree > portfast, reboot the APs (that are no longer “out of box”) and they behave > fine on the portfast-enabled ports. > > I’ve not seen this behavior with any other Cisco AP, and I don’t think it > happened with our earliest 3700s, either. > > Does this oddity ring familiar with anyone? > > Thanks- > > Lee > > *Lee Badman* | Network Architect > Information Technology Services > 206 Machinery Hall > 120 Smith Drive > Syracuse, New York 13244 > *t* 315.443.3003 * f* 315.443.4325 *e* *[email protected]* > <[email protected]> *w* its.syr.edu > > *SYRACUSE UNIVERSITY *syr.edu > > > > ********** Participation and subscription information for this EDUCAUSE > Constituent Group discussion list can be found at > http://www.educause.edu/groups/. > > -- Oliver Elliott Senior Network Specialist IT Services University of Bristol e: [email protected] t: 0117 39 (41131) ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
