I’ve seen 2702’s doing this as well. Was amazed when I looked in the log of my 
switch when I couldn’t figure out why the ports got disabled. Wrong MAC address 
is also one of the problems we’re having with the 2702’s. Don’t know what they 
have been doing with these pre-loaded images on them. These images should have 
been tested better at Cisco…

Van: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[mailto:[email protected]] Namens Lee H Badman
Verzonden: dinsdag 11 augustus 2015 14:36
Aan: [email protected]
Onderwerp: Re: [WIRELESS-LAN] New 3702 APs not playing well with Spanning-Tree 
Portfast Out-of-Box

Thanks, Oliver- so this is known… good to know. So far I’m not finding a 
specific bug ID doing searches. Would you have any link, by chance?

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]<mailto:[email protected]> w 
its.syr.edu
SYRACUSE UNIVERSITY
syr.edu

From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[mailto:[email protected]] On Behalf Of Oliver Elliott
Sent: Tuesday, August 11, 2015 8:27 AM
To: 
[email protected]<mailto:[email protected]>
Subject: Re: [WIRELESS-LAN] New 3702 APs not playing well with Spanning-Tree 
Portfast Out-of-Box

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]<mailto:[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]<mailto:[email protected]> w 
its.syr.edu<http://its.syr.edu>
SYRACUSE UNIVERSITY
syr.edu<http://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]<mailto:[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/.
********** Participation and subscription information for this EDUCAUSE 
Constituent Group discussion list can be found at 
http://www.educause.edu/groups/.

**********
Participation and subscription information for this EDUCAUSE Constituent Group 
discussion list can be found at http://www.educause.edu/groups/.

Reply via email to