Re: [WIRELESS-LAN] Cisco AP 'flash' bug

2017-12-13 Thread Tristan Gulyas
t; Twente, Enschede, Netherlands > > Building Citadel room 219 | T: +31 53 489 4321 <tel:+31%2053%20489%204321> | > j.f.po...@utwente.nl <mailto:j.f.po...@utwente.nl> | www.utwente.nl > <http://www.utwente.nl/> > > > > > From: The EDUCAUSE Wireles

RE: [WIRELESS-LAN] Cisco AP 'flash' bug

2017-12-12 Thread j.f.popma
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Garret Peirce Sent: dinsdag 12 december 2017 14:29 To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Cisco AP 'flash' bug I should've circled back/followed up as we worked through this. We worked w/Cisco earlier this year

Re: [WIRELESS-LAN] Cisco AP 'flash' bug

2017-12-12 Thread Samuel Clements
ate to a different environment >> and of course it is not a fix. >> >> >> >> Regards, >> >> *Jan Freerk Popma* *|* *ICT Service Center, Networkmanagement **|** >> University of Twente, Enschede, Netherlands* >> >> Building Citadel room 219 | T: +31 53 489 43

Re: [WIRELESS-LAN] Cisco AP 'flash' bug

2017-12-12 Thread Garret Peirce
; > > On 20 Jan 2017, at 7:46 am, McClintic, Thomas < > thomas.mcclin...@uth.tmc.edu> wrote: > > > > Next time you have this issue, try connecting a console to the AP and run > the following: > > > > ap: *fsck flash:* > > Are you sure you want to fsck &qu

RE: [WIRELESS-LAN] Cisco AP 'flash' bug

2017-12-12 Thread j.f.popma
l> From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Tristan Gulyas Sent: dinsdag 12 december 2017 07:18 To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Cisco AP 'flash' bug Hi all, I was under the impres

Re: [WIRELESS-LAN] Cisco AP 'flash' bug

2017-12-11 Thread Tristan Gulyas
nstituent Group Listserv > [mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Garret Peirce > Sent: Thursday, January 19, 2017 10:44 AM > To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU > Subject: Re: [WIRELESS-LAN] Cisco AP 'flash' bug > > Ian, thanks for the response. > To comm

Re: [WIRELESS-LAN] Cisco AP 'flash' bug

2017-02-03 Thread Garret Peirce
Yes, we have re-flashed as well but we'd rather not use resources to keep going out to do so. We feel there may be a HW issue and are working w/Cisco EFA on further investigation. On Fri, Jan 20, 2017 at 1:07 PM, Joachim Tingvold wrote: > On 19 Jan 2017, at 21:46,

Re: [WIRELESS-LAN] Cisco AP 'flash' bug

2017-01-20 Thread Joachim Tingvold
On 19 Jan 2017, at 21:46, McClintic, Thomas wrote: Next time you have this issue, try connecting a console to the AP and run the following: ap: fsck flash: Are you sure you want to fsck "flash:" (could take some time) (y/n)?y flashfs[0]: … ap: boot This works for us on the failed to

RE: [WIRELESS-LAN] Cisco AP 'flash' bug

2017-01-19 Thread McClintic, Thomas
ess Issues Constituent Group Listserv [mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Garret Peirce Sent: Thursday, January 19, 2017 10:44 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Cisco AP 'flash' bug Ian, thanks for the response. To commiserate it does feel tha

Re: [WIRELESS-LAN] Cisco AP 'flash' bug

2017-01-19 Thread Garret Peirce
Ian, thanks for the response. To commiserate it does feel that wireless ecosystem has been affected by a larger bloom of bugs over the last year or so. Some of that may be due to enhanced vigilance and our tracking them down to root causes, but whatever the case, in aggregate it's a concern here

RE: [WIRELESS-LAN] Cisco AP 'flash' bug

2017-01-19 Thread Ian Lyons
Yes, we own that bug too. Pretty much we have every bug ..and have been patching like madmen since July. From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Garret Peirce Sent: Thursday, January 19, 2017 10:27 AM To: