Re: [WIRELESS-LAN] spurious cpi report of mass AP disassociation

2017-09-15 Thread Yahya M. Jaber
17 8:19 PM, Earl Barfield <earl.barfi...@oit.gatech.edu> wrote: > Date:Mon, 11 Sep 2017 17:48:58 -0700 > From:Mark Duling <mark.dul...@biola.edu> > Subject: Re: spurious cpi report of mass AP disassociation > > Thanks for all the replies everyone. Well

Re: spurious cpi report of mass AP disassociation

2017-09-15 Thread Earl Barfield
> Date:Mon, 11 Sep 2017 17:48:58 -0700 > From:Mark Duling <mark.dul...@biola.edu> > Subject: Re: spurious cpi report of mass AP disassociation > > Thanks for all the replies everyone. Well I'm not used to looking at AP > logs, but ... After such an event, log int

RE: [WIRELESS-LAN] spurious cpi report of mass AP disassociation

2017-09-12 Thread Hector J Rios
"wireless-lan@listserv.educause.edu<mailto:wireless-lan@listserv.educause.edu>" <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU<mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>> Subject: [WIRELESS-LAN] spurious cpi report of mass AP disassociation We're using Cisco 8540 on code 8.2.151.0. Las

Re: [WIRELESS-LAN] spurious cpi report of mass AP disassociation

2017-09-11 Thread Mark Duling
ISTSERV. > EDUCAUSE.EDU> > *Date: *Monday, September 11, 2017 at 11:48 AM > *To: *"wireless-lan@listserv.educause.edu" <WIRELESS-LAN@LISTSERV. > EDUCAUSE.EDU> > *Subject: *[WIRELESS-LAN] spurious cpi report of mass AP disassociation > > > > We're using Cisco 8540

Re: [WIRELESS-LAN] spurious cpi report of mass AP disassociation

2017-09-11 Thread Jeffrey D. Sessler
ay, September 11, 2017 at 11:48 AM To: "wireless-lan@listserv.educause.edu" <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> Subject: [WIRELESS-LAN] spurious cpi report of mass AP disassociation We're using Cisco 8540 on code 8.2.151.0. Last week CPI reported a great number of simultaneous AP d

RE: [WIRELESS-LAN] spurious cpi report of mass AP disassociation

2017-09-11 Thread Lee H Badman
g Sent: Monday, September 11, 2017 4:02 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] spurious cpi report of mass AP disassociation >> Out of curiosity- how many APs, clients (in general) and are you doing >> 802.1X? It's roughly 250 APs out of approximately 1k

Re: [WIRELESS-LAN] spurious cpi report of mass AP disassociation

2017-09-11 Thread Mark Duling
ssues Constituent Group Listserv [mailto: > WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] *On Behalf Of *Mark Duling > *Sent:* Monday, September 11, 2017 2:48 PM > *To:* WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU > *Subject:* [WIRELESS-LAN] spurious cpi report of mass AP disassociation > &

RE: [WIRELESS-LAN] spurious cpi report of mass AP disassociation

2017-09-11 Thread Manon Lessard
eless Issues Constituent Group Listserv [mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Lee H Badman Sent: 11 septembre 2017 15:04 To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] spurious cpi report of mass AP disassociation Out of curiosity- how many APs, clients (in ge

RE: [WIRELESS-LAN] spurious cpi report of mass AP disassociation

2017-09-11 Thread Lee H Badman
RELESS-LAN] spurious cpi report of mass AP disassociation We're using Cisco 8540 on code 8.2.151.0. Last week CPI reported a great number of simultaneous AP disassociations and then reassociation. CPI shows all the events had the exact same timestamp right down to the hundredth second. It was

spurious cpi report of mass AP disassociation

2017-09-11 Thread Mark Duling
We're using Cisco 8540 on code 8.2.151.0. Last week CPI reported a great number of simultaneous AP disassociations and then reassociation. CPI shows all the events had the exact same timestamp right down to the hundredth second. It was just a single event. But I can find no event preceding it