Re: [WIRELESS-LAN] Problems in the Dorms

2011-11-01 Thread James J J Hooper

On 01/11/2011 17:56, Jeffrey Sessler wrote:

How was your multicast configured? Past the controller-multicast, the
important piece is the AP Multicast mode set on the general page. If it's
set to Unicast, pain and suffering can occur. Also, have you enabled any
of the Media Stream features?
Are you still working with Cisco TAC, or have you engaged the wireless
business unit?
Jeff

  On Thursday, October 27, 2011 at 6:31 PM, in message
700d77bb392ae543b5b4455c8db89e3a09cc7...@mbox1.ad.bradley.edu, Ghere,
Shayne sgh...@bumail.bradley.edu wrote:

One thing we did find is that by turning Multicast off
(Controller-Multicast) it dropped the UDP traffic from 40-60Mb/sec down to
1-2Mb/sec on all Trunk Ports across campus. This was something even Cisco
was surprised by, so maybe it’s something with the 7.0.116 code. ??? It
was on by default after the upgrade because I don’t remember ever enabling
it since we don’t use Multicast over wireless, just on the wired network.

All our AP’s and controllers are on the same Vlan, so we’ve ruled out the
router/firewall, and none of the Gig trunk ports are even near capacity.

We are starting to make progress, but the biggest thing we’re seeing now
is the massive interference which we’re working on.



+1 on multicast enabled in unicast mode breaks everything in special 
ways (including our WISM2s *generating* ~200Mbps traffic) with 7.0.116.0 
and Cisco haven't yet been able to explain why.


-James

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


RE: [WIRELESS-LAN] Problems in the Dorms

2011-10-27 Thread Ghere, Shayne
Thank you for the input.   This is how we have the ports setup
currently.

We're to the point of experimenting with certain buildings in the dorms
and turning all rogue wireless devices off (including wireless
printers) to see if that helps.

I'll let you know what we find, and hopefully this will be resolved
before I retire in 22 years.;)

 

Thanks again everyone!
Shayne

 

From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Lee H Badman
Sent: Wednesday, October 26, 2011 5:05 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

 

Ditto that.

 

Lee H. Badman
Wireless/Network Engineer, ITS
Adjunct Instructor, iSchool
Syracuse University
315.443.3003



From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] on behalf of Jeffrey Sessler
[j...@scrippscollege.edu]
Sent: Wednesday, October 26, 2011 5:48 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

As Lee mentions, the communication between the AP and the controller is
via a standard access port. There should be no need to have trunking or
and other configuration on the port for the AP. Even if the AP has
multiple SSIDs and VLANs, all of that traffic is encapsulated within
CAPWAP.

 

Every port an AP connects to on my campus looks something like this:

interface GigabitEthernet1/0/1
 description Cisco AP
 switchport access vlan 111
 switchport mode access
 spanning-tree portfast

 On Wednesday, October 26, 2011 at 7:02 AM, in message
700d77bb392ae543b5b4455c8db89e3a09cc7...@mbox1.ad.bradley.edu, Ghere,
Shayne sgh...@bumail.bradley.edu wrote:

Lee,

I've read multiple documents and all say different things on setup.   We
have an internal registration system that we register each AP's mac
address and it's updated (yes we're still using VMPS) in the vmps.cfg
file.  So currently we have each port setup like this:

interface GigabitEthernet0/48
description GPB-AIR2-2 2-16
switchport access vlan dynamic
no logging event link-status
no snmp trap link-status
spanning-tree portfast


We have turned off Spanning-tree, hardcoded it to VLAN 5, hard set it to
1000/Full and even had them setup as trunks to allow ONLY the vlans we
are passing for wireless, but to no avail.

If you have any ideas, please let me know.

Thanks
Shayne

P.S.  Sorry, our e-mail was out yesterday so I couldn't log in to read
or respond.



-Original Message-
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Lee H Badman
Sent: Monday, October 24, 2011 6:08 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

Shayne, please post what your switchport configs look like for the APs.
Also, are you managing the APs on a single network?

Lee H. Badman
Wireless/Network Engineer, ITS
Adjunct Instructor, iSchool
Syracuse University
315.443.3003

From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] on behalf of Jeffrey Sessler
[j...@scrippscollege.edu]
Sent: Monday, October 24, 2011 6:10 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

This sounds/looks a lot more like a network issue then an AP/rogue
problem. The logs suggest the AP's are having problems staying in
contact with the controllers. Everything gigabit from end to end?

What does WCS indicate as the number of channel changes per hour?
As a test, on each 5508, under Wireless, 802.11b/g/n and 802.11a/n, DCA,
change the interval to 6 hours, and the DCA Channel Sensitivity to low.

Do this - contact your Cisco team and ask them to put you in contact
with the Wireless Business unit. They have a team that can assist if you
feel it's a show-stopper problem.

Jeff

 On Monday, October 24, 2011 at 7:30 AM, in message
700d77bb392ae543b5b4455c8db89e3a09cc7...@mbox1.ad.bradley.edu, Ghere,
Shayne sgh...@bumail.bradley.edu wrote:
Hello Craig,

The upgrades were done independently as was the WCS upgrade.   I have
the WLC's setup with an equal number of AP's on each with Primary,
Secondary and Tertiary controllers configured so I can upgrade one with
them fail over to the others.

I have spent the past 3 weeks pouring over the configurations on each
WLC...even doing print screens of each to compare and they are
completely identical.

The WCS (running 7.0.172.0) has settings that the WLC's don't like
(7.0.116.0) or are mismatched such as power level settings etc.So
for those I just set on the WLC's and don't push out the templates on
the WCS with the odd values.

Here's our history:

May 2010 we started with the 3 WS-C5508 and 1 WCS to handle all the
dorms/academic/non academic buildings.  We are a single campus (so no
wan).  We were running 6.0.199.0 on the WLC's (I believe

RE: [WIRELESS-LAN] Problems in the Dorms

2011-10-27 Thread Peter P Morrissey
That can only help. I couldn't imagine trying to run a wireless network and 
allowing that many rogue devices. One thing we do is give out USB cables to 
incoming freshmen if we see they have a printer (which is almost always 
wireless nowadays). I found you could get 15' USB cables for close to 2.00 a 
piece. It is worth the price to be able to say, you can't do that, but here's a 
cable on us.
Pete M.

From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Ghere, Shayne
Sent: Thursday, October 27, 2011 12:53 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

Thank you for the input.   This is how we have the ports setup currently.
We're to the point of experimenting with certain buildings in the dorms and 
turning all rogue wireless devices off (including wireless printers) to see 
if that helps.
I'll let you know what we find, and hopefully this will be resolved before I 
retire in 22 years.;)

Thanks again everyone!
Shayne

From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Lee H Badman
Sent: Wednesday, October 26, 2011 5:05 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms


Ditto that.


Lee H. Badman
Wireless/Network Engineer, ITS
Adjunct Instructor, iSchool
Syracuse University
315.443.3003

From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] on behalf of Jeffrey Sessler 
[j...@scrippscollege.edu]
Sent: Wednesday, October 26, 2011 5:48 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms
As Lee mentions, the communication between the AP and the controller is via a 
standard access port. There should be no need to have trunking or and other 
configuration on the port for the AP. Even if the AP has multiple SSIDs and 
VLANs, all of that traffic is encapsulated within CAPWAP.

Every port an AP connects to on my campus looks something like this:
interface GigabitEthernet1/0/1
 description Cisco AP
 switchport access vlan 111
 switchport mode access
 spanning-tree portfast

 On Wednesday, October 26, 2011 at 7:02 AM, in message 
 700d77bb392ae543b5b4455c8db89e3a09cc7...@mbox1.ad.bradley.edu, Ghere, 
 Shayne sgh...@bumail.bradley.edu wrote:
Lee,

I've read multiple documents and all say different things on setup.   We
have an internal registration system that we register each AP's mac
address and it's updated (yes we're still using VMPS) in the vmps.cfg
file.  So currently we have each port setup like this:

interface GigabitEthernet0/48
description GPB-AIR2-2 2-16
switchport access vlan dynamic
no logging event link-status
no snmp trap link-status
spanning-tree portfast


We have turned off Spanning-tree, hardcoded it to VLAN 5, hard set it to
1000/Full and even had them setup as trunks to allow ONLY the vlans we
are passing for wireless, but to no avail.

If you have any ideas, please let me know.

Thanks
Shayne

P.S.  Sorry, our e-mail was out yesterday so I couldn't log in to read
or respond.



-Original Message-
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Lee H Badman
Sent: Monday, October 24, 2011 6:08 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

Shayne, please post what your switchport configs look like for the APs.
Also, are you managing the APs on a single network?

Lee H. Badman
Wireless/Network Engineer, ITS
Adjunct Instructor, iSchool
Syracuse University
315.443.3003

From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] on behalf of Jeffrey Sessler
[j...@scrippscollege.edu]
Sent: Monday, October 24, 2011 6:10 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

This sounds/looks a lot more like a network issue then an AP/rogue
problem. The logs suggest the AP's are having problems staying in
contact with the controllers. Everything gigabit from end to end?

What does WCS indicate as the number of channel changes per hour?
As a test, on each 5508, under Wireless, 802.11b/g/n and 802.11a/n, DCA,
change the interval to 6 hours, and the DCA Channel Sensitivity to low.

Do this - contact your Cisco team and ask them to put you in contact
with the Wireless Business unit. They have a team that can assist if you
feel it's a show-stopper problem.

Jeff

 On Monday, October 24, 2011 at 7:30 AM, in message
700d77bb392ae543b5b4455c8db89e3a09cc7...@mbox1.ad.bradley.edu, Ghere,
Shayne sgh...@bumail.bradley.edu wrote:
Hello Craig,

The upgrades were done independently as was the WCS upgrade.   I have
the WLC's setup with an equal number of AP's on each with Primary,
Secondary and Tertiary controllers configured so I can

Re: [WIRELESS-LAN] Problems in the Dorms

2011-10-27 Thread Jeffrey Sessler
Getting rid of the rogues can't hurt, but this smells like a network
issue. The communication between the AP and controller are such that it
wouldn't take much to cause the AP's to see a problem and try to fix it.
Even an etherchannel flapping, say on a trunk heading to those
buildings, would be enough to cause the APs to go back into CAPWAP
discovery.
 
Oh, and if you've not yet escalated this to your Cisco team, you
should. Once the wireless business unit is involved, they tend to
resolve problems nearly at the speed of light... well... except if it
involves Lee. ;)
 
Jeff

 On Thursday, October 27, 2011 at 9:53 AM, in message
700d77bb392ae543b5b4455c8db89e3a09cc7...@mbox1.ad.bradley.edu, Ghere,
Shayne sgh...@bumail.bradley.edu wrote:


Thank you for the input.   This is how we have the ports setup
currently.
We’re to the point of experimenting with certain buildings in the dorms
and turning all “rogue” wireless devices off (including wireless
printers) to see if that helps.
I’ll let you know what we find, and hopefully this will be resolved
before I retire in 22 years.;)
 
Thanks again everyone!
Shayne
 

From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Lee H Badman
Sent: Wednesday, October 26, 2011 5:05 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

 

Ditto that.

 

Lee H. Badman
Wireless/Network Engineer, ITS
Adjunct Instructor, iSchool
Syracuse University
315.443.3003


From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] on behalf of Jeffrey Sessler
[j...@scrippscollege.edu]
Sent: Wednesday, October 26, 2011 5:48 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

As Lee mentions, the communication between the AP and the controller is
via a standard access port. There should be no need to have trunking or
and other configuration on the port for the AP. Even if the AP has
multiple SSIDs and VLANs, all of that traffic is encapsulated within
CAPWAP.

 

Every port an AP connects to on my campus looks something like this:

interface GigabitEthernet1/0/1
 description Cisco AP
 switchport access vlan 111
 switchport mode access
 spanning-tree portfast

 On Wednesday, October 26, 2011 at 7:02 AM, in message
700d77bb392ae543b5b4455c8db89e3a09cc7...@mbox1.ad.bradley.edu, Ghere,
Shayne sgh...@bumail.bradley.edu wrote:


Lee,

I've read multiple documents and all say different things on setup.  
We
have an internal registration system that we register each AP's mac
address and it's updated (yes we're still using VMPS) in the vmps.cfg
file.  So currently we have each port setup like this:

interface GigabitEthernet0/48
description GPB-AIR2-2 2-16
switchport access vlan dynamic
no logging event link-status
no snmp trap link-status
spanning-tree portfast


We have turned off Spanning-tree, hardcoded it to VLAN 5, hard set it
to
1000/Full and even had them setup as trunks to allow ONLY the vlans we
are passing for wireless, but to no avail.

If you have any ideas, please let me know.

Thanks
Shayne

P.S.  Sorry, our e-mail was out yesterday so I couldn't log in to read
or respond.



-Original Message-
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Lee H Badman
Sent: Monday, October 24, 2011 6:08 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

Shayne, please post what your switchport configs look like for the
APs.
Also, are you managing the APs on a single network?

Lee H. Badman
Wireless/Network Engineer, ITS
Adjunct Instructor, iSchool
Syracuse University
315.443.3003

From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] on behalf of Jeffrey Sessler
[j...@scrippscollege.edu]
Sent: Monday, October 24, 2011 6:10 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

This sounds/looks a lot more like a network issue then an AP/rogue
problem. The logs suggest the AP's are having problems staying in
contact with the controllers. Everything gigabit from end to end?

What does WCS indicate as the number of channel changes per hour?
As a test, on each 5508, under Wireless, 802.11b/g/n and 802.11a/n,
DCA,
change the interval to 6 hours, and the DCA Channel Sensitivity to
low.

Do this - contact your Cisco team and ask them to put you in contact
with the Wireless Business unit. They have a team that can assist if
you
feel it's a show-stopper problem.

Jeff

 On Monday, October 24, 2011 at 7:30 AM, in message
700d77bb392ae543b5b4455c8db89e3a09cc7...@mbox1.ad.bradley.edu,
Ghere,
Shayne sgh...@bumail.bradley.edu wrote:
Hello Craig,

The upgrades were done independently as was the WCS upgrade.   I have
the WLC's setup with an equal number of AP's on each with Primary

RE: [WIRELESS-LAN] Problems in the Dorms

2011-10-27 Thread Ghere, Shayne
One thing we did find is that by turning Multicast off (Controller-Multicast) 
it dropped the UDP traffic from 40-60Mb/sec down to 1-2Mb/sec on all Trunk 
Ports across campus.  This was something even Cisco was surprised by, so maybe 
it’s something with the 7.0.116 code.  ???   It was on by default after the 
upgrade because I don’t remember ever enabling it since we don’t use Multicast 
over wireless, just on the wired network.

All our AP’s and controllers are on the same Vlan, so we’ve ruled out the 
router/firewall, and none of the Gig trunk ports are even near capacity.

We are starting to make progress, but the biggest thing we’re seeing now is the 
massive interference which we’re working on.

 

Thanks
Shayne

 

From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Jeffrey Sessler
Sent: Thursday, October 27, 2011 7:44 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

 

Getting rid of the rogues can't hurt, but this smells like a network issue. The 
communication between the AP and controller are such that it wouldn't take much 
to cause the AP's to see a problem and try to fix it. Even an etherchannel 
flapping, say on a trunk heading to those buildings, would be enough to cause 
the APs to go back into CAPWAP discovery.

 

Oh, and if you've not yet escalated this to your Cisco team, you should. Once 
the wireless business unit is involved, they tend to resolve problems nearly at 
the speed of light... well... except if it involves Lee. ;)

 

Jeff


 On Thursday, October 27, 2011 at 9:53 AM, in message 
 700d77bb392ae543b5b4455c8db89e3a09cc7...@mbox1.ad.bradley.edu, Ghere, 
 Shayne sgh...@bumail.bradley.edu wrote:

Thank you for the input.   This is how we have the ports setup currently.

We’re to the point of experimenting with certain buildings in the dorms and 
turning all “rogue” wireless devices off (including wireless printers) to see 
if that helps.

I’ll let you know what we find, and hopefully this will be resolved before I 
retire in 22 years.;)

 

Thanks again everyone!
Shayne

 

From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Lee H Badman
Sent: Wednesday, October 26, 2011 5:05 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

 

Ditto that.

 

Lee H. Badman
Wireless/Network Engineer, ITS
Adjunct Instructor, iSchool
Syracuse University
315.443.3003



From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] on behalf of Jeffrey Sessler 
[j...@scrippscollege.edu]
Sent: Wednesday, October 26, 2011 5:48 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

As Lee mentions, the communication between the AP and the controller is via a 
standard access port. There should be no need to have trunking or and other 
configuration on the port for the AP. Even if the AP has multiple SSIDs and 
VLANs, all of that traffic is encapsulated within CAPWAP.

 

Every port an AP connects to on my campus looks something like this:

interface GigabitEthernet1/0/1
 description Cisco AP
 switchport access vlan 111
 switchport mode access
 spanning-tree portfast

 On Wednesday, October 26, 2011 at 7:02 AM, in message 
 700d77bb392ae543b5b4455c8db89e3a09cc7...@mbox1.ad.bradley.edu, Ghere, 
 Shayne sgh...@bumail.bradley.edu wrote:

Lee,

I've read multiple documents and all say different things on setup.   We
have an internal registration system that we register each AP's mac
address and it's updated (yes we're still using VMPS) in the vmps.cfg
file.  So currently we have each port setup like this:

interface GigabitEthernet0/48
description GPB-AIR2-2 2-16
switchport access vlan dynamic
no logging event link-status
no snmp trap link-status
spanning-tree portfast


We have turned off Spanning-tree, hardcoded it to VLAN 5, hard set it to
1000/Full and even had them setup as trunks to allow ONLY the vlans we
are passing for wireless, but to no avail.

If you have any ideas, please let me know.

Thanks
Shayne

P.S.  Sorry, our e-mail was out yesterday so I couldn't log in to read
or respond.



-Original Message-
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Lee H Badman
Sent: Monday, October 24, 2011 6:08 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

Shayne, please post what your switchport configs look like for the APs.
Also, are you managing the APs on a single network?

Lee H. Badman
Wireless/Network Engineer, ITS
Adjunct Instructor, iSchool
Syracuse University
315.443.3003

From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] on behalf of Jeffrey Sessler
[j

Re: [WIRELESS-LAN] Problems in the Dorms

2011-10-27 Thread Mike King
Not exactly too surprising.  I've have a few enterprising students
broadcasting some stuff from there dorm rooms via multicast (Wired for us).
 I can imagine if it worked, they'd use it.

Mike

On Thu, Oct 27, 2011 at 9:31 PM, Ghere, Shayne sgh...@bumail.bradley.eduwrote:

 

 One thing we did find is that by turning Multicast off
 (Controller-Multicast) it dropped the UDP traffic from 40-60Mb/sec down to
 1-2Mb/sec on all Trunk Ports across campus.  This was something even Cisco
 was surprised by, so maybe it’s something with the 7.0.116 code.  ???   It
 was on by default after the upgrade because I don’t remember ever enabling
 it since we don’t use Multicast over wireless, just on the wired network.*
 ***

 All our AP’s and controllers are on the same Vlan, so we’ve ruled out the
 router/firewall, and none of the Gig trunk ports are even near capacity.**
 **

 We are starting to make progress, but the biggest thing we’re seeing now is
 the massive interference which we’re working on.

 ** **

 Thanks
 Shayne

 ** **

 *From:* The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:
 WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] *On Behalf Of *Jeffrey Sessler
 *Sent:* Thursday, October 27, 2011 7:44 PM

 *To:* WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
 *Subject:* Re: [WIRELESS-LAN] Problems in the Dorms

 ** **

 Getting rid of the rogues can't hurt, but this smells like a network issue.
 The communication between the AP and controller are such that it wouldn't
 take much to cause the AP's to see a problem and try to fix it. Even an
 etherchannel flapping, say on a trunk heading to those buildings, would be
 enough to cause the APs to go back into CAPWAP discovery.

  

 Oh, and if you've not yet escalated this to your Cisco team, you should.
 Once the wireless business unit is involved, they tend to resolve problems
 nearly at the speed of light... well... except if it involves Lee. ;)

  

 Jeff


  On Thursday, October 27, 2011 at 9:53 AM, in message 
 700d77bb392ae543b5b4455c8db89e3a09cc7...@mbox1.ad.bradley.edu, Ghere,
 Shayne sgh...@bumail.bradley.edu wrote:

 Thank you for the input.   This is how we have the ports setup currently.*
 ***

 We’re to the point of experimenting with certain buildings in the dorms and
 turning all “rogue” wireless devices off (including wireless printers) to
 see if that helps.

 I’ll let you know what we find, and hopefully this will be resolved before
 I retire in 22 years.;)

 ** **

 Thanks again everyone!
 Shayne

 ** **

 *From:* The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:
 WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] *On Behalf Of *Lee H Badman
 *Sent:* Wednesday, October 26, 2011 5:05 PM
 *To:* WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
 *Subject:* Re: [WIRELESS-LAN] Problems in the Dorms

 ** **

 Ditto that.

  

 Lee H. Badman
 Wireless/Network Engineer, ITS
 Adjunct Instructor, iSchool
 Syracuse University
 315.443.3003
 --

 *From:* The EDUCAUSE Wireless Issues Constituent Group Listserv [
 WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] on behalf of Jeffrey Sessler [
 j...@scrippscollege.edu]
 *Sent:* Wednesday, October 26, 2011 5:48 PM
 *To:* WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
 *Subject:* Re: [WIRELESS-LAN] Problems in the Dorms

 As Lee mentions, the communication between the AP and the controller is via
 a standard access port. There should be no need to have trunking or and
 other configuration on the port for the AP. Even if the AP has multiple
 SSIDs and VLANs, all of that traffic is encapsulated within CAPWAP.

  

 Every port an AP connects to on my campus looks something like this:

 interface GigabitEthernet1/0/1
  description Cisco AP
  switchport access vlan 111
  switchport mode access
  spanning-tree portfast

  On Wednesday, October 26, 2011 at 7:02 AM, in message 
 700d77bb392ae543b5b4455c8db89e3a09cc7...@mbox1.ad.bradley.edu, Ghere,
 Shayne sgh...@bumail.bradley.edu wrote:

 Lee,

 I've read multiple documents and all say different things on setup.   We
 have an internal registration system that we register each AP's mac
 address and it's updated (yes we're still using VMPS) in the vmps.cfg
 file.  So currently we have each port setup like this:

 interface GigabitEthernet0/48
 description GPB-AIR2-2 2-16
 switchport access vlan dynamic
 no logging event link-status
 no snmp trap link-status
 spanning-tree portfast


 We have turned off Spanning-tree, hardcoded it to VLAN 5, hard set it to
 1000/Full and even had them setup as trunks to allow ONLY the vlans we
 are passing for wireless, but to no avail.

 If you have any ideas, please let me know.

 Thanks
 Shayne

 P.S.  Sorry, our e-mail was out yesterday so I couldn't log in to read
 or respond.



 -Original Message-
 From: The EDUCAUSE Wireless Issues Constituent Group Listserv
 [mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Lee H Badman
 Sent: Monday, October 24

Re: [WIRELESS-LAN] Problems in the Dorms

2011-10-27 Thread Jeff Kell
On 10/27/2011 9:49 PM, Mike King wrote:
 Not exactly too surprising.  I've have a few enterprising students
 broadcasting some stuff from there dorm rooms via multicast (Wired for
 us).  I can imagine if it worked, they'd use it.

Yes, then there is that wonderful Dropbox LAN Sync broadcast nonsense...

And did anyone drop a Drobo server nearby?

How fat is your wireless subnet (how many printer management utilities
are looking for printers to manage)?

Rendezvous/Bonjour conferencing traffic?  

Display projection?   Slingbox?

IPv6?  MacOS DNS Multicast/Anycast traffic?

Jeff

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



RE: [WIRELESS-LAN] Problems in the Dorms

2011-10-26 Thread Ghere, Shayne
Lee,

I've read multiple documents and all say different things on setup.   We
have an internal registration system that we register each AP's mac
address and it's updated (yes we're still using VMPS) in the vmps.cfg
file.  So currently we have each port setup like this:

interface GigabitEthernet0/48
 description GPB-AIR2-2 2-16
 switchport access vlan dynamic
 no logging event link-status
 no snmp trap link-status
 spanning-tree portfast


We have turned off Spanning-tree, hardcoded it to VLAN 5, hard set it to
1000/Full and even had them setup as trunks to allow ONLY the vlans we
are passing for wireless, but to no avail.

If you have any ideas, please let me know.

Thanks
Shayne

P.S.  Sorry, our e-mail was out yesterday so I couldn't log in to read
or respond.



-Original Message-
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Lee H Badman
Sent: Monday, October 24, 2011 6:08 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

Shayne, please post what your switchport configs look like for the APs.
Also, are you managing the APs on a single network?

Lee H. Badman
Wireless/Network Engineer, ITS
Adjunct Instructor, iSchool
Syracuse University
315.443.3003

From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] on behalf of Jeffrey Sessler
[j...@scrippscollege.edu]
Sent: Monday, October 24, 2011 6:10 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

This sounds/looks a lot more like a network issue then an AP/rogue
problem. The logs suggest the AP's are having problems staying in
contact with the controllers. Everything gigabit from end to end?

What does WCS indicate as the number of channel changes per hour?
As a test, on each 5508, under Wireless, 802.11b/g/n and 802.11a/n, DCA,
change the interval to 6 hours, and the DCA Channel Sensitivity to low.

Do this - contact your Cisco team and ask them to put you in contact
with the Wireless Business unit. They have a team that can assist if you
feel it's a show-stopper problem.

Jeff

 On Monday, October 24, 2011 at 7:30 AM, in message
700d77bb392ae543b5b4455c8db89e3a09cc7...@mbox1.ad.bradley.edu, Ghere,
Shayne sgh...@bumail.bradley.edu wrote:
Hello Craig,

The upgrades were done independently as was the WCS upgrade.   I have
the WLC's setup with an equal number of AP's on each with Primary,
Secondary and Tertiary controllers configured so I can upgrade one with
them fail over to the others.

I have spent the past 3 weeks pouring over the configurations on each
WLC...even doing print screens of each to compare and they are
completely identical.

The WCS (running 7.0.172.0) has settings that the WLC's don't like
(7.0.116.0) or are mismatched such as power level settings etc.So
for those I just set on the WLC's and don't push out the templates on
the WCS with the odd values.

Here's our history:

May 2010 we started with the 3 WS-C5508 and 1 WCS to handle all the
dorms/academic/non academic buildings.  We are a single campus (so no
wan).  We were running 6.0.199.0 on the WLC's (I believe) and there were
a few problems.   Cisco advised us to upgrade to 6.0.299.0 (maintenance
release) to fix another issue, then 4 weeks ago upgraded to 7.0.116.0 to
fix another problem.

The WCS needed to be upgraded to 7.0.172.0 since the code we were
running before wouldn't work with the 116.0 on the WLC's.   /ugh

Since the students moved back to campus we've had nothing but radios
shutting off, AP's completely rebooting, AP's moving to
secondary/tertiary controllers then back to the primary etc.It has
been a NIGHTMARE.

What I'm seeing is that our B/G channels 1,6,11 are also being used by
the 450+ rogue AP's in the dorms.   We can't shut off the B/G due to
older machines, but the interference causes the A/N radios to drop as
well.

When we were running Autonomous AP's we didn't have this problem, but
since moving to LWAPP we've had problems.


Thanks
Shayne

From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Craig Eyre
Sent: Monday, October 24, 2011 9:02 AM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

Shayne,

Nothing jumps out at me, but I do have a couple questions.

1. What version were you running previously?
2. Did you deploy the upgrade with your WCS?

The reason I ask about the where you upgraded it from, is because a
colleague I know just upgraded 2 WLC's from his WCS and the settings
were different for each wlc.


Regards,

Craig Eyre
Network Analyst
IT Services Department
Mount Royal University
4825 Mount Royal Gate SW
Calgary AB T2P 3T5

P. 403.440.5199
E. ce...@mtroyal.ca

The difference between a successful person and others is not a lack of
strength, not a lack of knowledge, but rather in a lack

RE: [WIRELESS-LAN] Problems in the Dorms

2011-10-26 Thread Lee H Badman
I would suggest further reducing switch concerns out by fixing a test port or 
two to switchport mode access and switchport access vlan  (whatever 
appropriate) for a couple of APs that are acting up, along with making sure 
your switch uplinks are clearly set up with proper trunking and no overlap with 
access commands, and that all DHCP snooping (if used) is what it should be 
especially on the uplinks. 

I would imagine TAC touched on most of this, but fixing the access port ( if 
you can to) single VLAN and switchport mode access is easy and takes away one 
point of potential variability. 

-Lee



From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] on behalf of Ghere, Shayne 
[sgh...@bumail.bradley.edu]
Sent: Wednesday, October 26, 2011 10:02 AM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

Lee,

I've read multiple documents and all say different things on setup.   We
have an internal registration system that we register each AP's mac
address and it's updated (yes we're still using VMPS) in the vmps.cfg
file.  So currently we have each port setup like this:

interface GigabitEthernet0/48
 description GPB-AIR2-2 2-16
 switchport access vlan dynamic
 no logging event link-status
 no snmp trap link-status
 spanning-tree portfast


We have turned off Spanning-tree, hardcoded it to VLAN 5, hard set it to
1000/Full and even had them setup as trunks to allow ONLY the vlans we
are passing for wireless, but to no avail.

If you have any ideas, please let me know.

Thanks
Shayne

P.S.  Sorry, our e-mail was out yesterday so I couldn't log in to read
or respond.



-Original Message-
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Lee H Badman
Sent: Monday, October 24, 2011 6:08 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

Shayne, please post what your switchport configs look like for the APs.
Also, are you managing the APs on a single network?

Lee H. Badman
Wireless/Network Engineer, ITS
Adjunct Instructor, iSchool
Syracuse University
315.443.3003

From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] on behalf of Jeffrey Sessler
[j...@scrippscollege.edu]
Sent: Monday, October 24, 2011 6:10 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

This sounds/looks a lot more like a network issue then an AP/rogue
problem. The logs suggest the AP's are having problems staying in
contact with the controllers. Everything gigabit from end to end?

What does WCS indicate as the number of channel changes per hour?
As a test, on each 5508, under Wireless, 802.11b/g/n and 802.11a/n, DCA,
change the interval to 6 hours, and the DCA Channel Sensitivity to low.

Do this - contact your Cisco team and ask them to put you in contact
with the Wireless Business unit. They have a team that can assist if you
feel it's a show-stopper problem.

Jeff

 On Monday, October 24, 2011 at 7:30 AM, in message
700d77bb392ae543b5b4455c8db89e3a09cc7...@mbox1.ad.bradley.edu, Ghere,
Shayne sgh...@bumail.bradley.edu wrote:
Hello Craig,

The upgrades were done independently as was the WCS upgrade.   I have
the WLC's setup with an equal number of AP's on each with Primary,
Secondary and Tertiary controllers configured so I can upgrade one with
them fail over to the others.

I have spent the past 3 weeks pouring over the configurations on each
WLC...even doing print screens of each to compare and they are
completely identical.

The WCS (running 7.0.172.0) has settings that the WLC's don't like
(7.0.116.0) or are mismatched such as power level settings etc.So
for those I just set on the WLC's and don't push out the templates on
the WCS with the odd values.

Here's our history:

May 2010 we started with the 3 WS-C5508 and 1 WCS to handle all the
dorms/academic/non academic buildings.  We are a single campus (so no
wan).  We were running 6.0.199.0 on the WLC's (I believe) and there were
a few problems.   Cisco advised us to upgrade to 6.0.299.0 (maintenance
release) to fix another issue, then 4 weeks ago upgraded to 7.0.116.0 to
fix another problem.

The WCS needed to be upgraded to 7.0.172.0 since the code we were
running before wouldn't work with the 116.0 on the WLC's.   /ugh

Since the students moved back to campus we've had nothing but radios
shutting off, AP's completely rebooting, AP's moving to
secondary/tertiary controllers then back to the primary etc.It has
been a NIGHTMARE.

What I'm seeing is that our B/G channels 1,6,11 are also being used by
the 450+ rogue AP's in the dorms.   We can't shut off the B/G due to
older machines, but the interference causes the A/N radios to drop as
well.

When we were running Autonomous AP's we didn't have this problem

RE: [WIRELESS-LAN] Problems in the Dorms

2011-10-26 Thread Stephen G. Lotho

Hi Shayne,

I would agree with Mike King.  I would call your local rep or Cisco Team to 
resolve this issue quickly.  Thanks for sharing just in case we run into a 
similar issue.

Thanks,

Steve

Stephen G. Lotho | Roosevelt University | Director, Network Services | 
312-341-6996 | 430 S. Michigan, Rm. 264, Chicago, IL 60605| 
slo...@roosevelt.edumailto:slo...@roosevelt.edu



From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU]mailto:[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU]
 On Behalf Of Mike King
Sent: Monday, October 24, 2011 7:57 PM
To: 
WIRELESS-LAN@LISTSERV.EDUCAUSE.EDUmailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

I agree with contacting your Cisco Team.

Back 2005 we opened with a showshopper.  We had a bug that basically caused an 
Access Point to reboot when more than 20 users were associated.  Caused a 
cascade failure, as each access point was knocked down, it caused more users to 
associated to others, knocking them down.

We ran a 24 hour TAC call, running the whole follow the sun gamut.  The 
Business Unit was involved at some point during the night.

We eventually downgraded at some point to get stable, but the information we 
gathered allowed the bug to be identified and a resolved.
On Mon, Oct 24, 2011 at 6:10 PM, Jeffrey Sessler 
j...@scrippscollege.edumailto:j...@scrippscollege.edu wrote:
This sounds/looks a lot more like a network issue then an AP/rogue problem. The 
logs suggest the AP's are having problems staying in contact with the 
controllers. Everything gigabit from end to end?

What does WCS indicate as the number of channel changes per hour?
As a test, on each 5508, under Wireless, 802.11b/g/n and 802.11a/n, DCA, change 
the interval to 6 hours, and the DCA Channel Sensitivity to low.

Do this - contact your Cisco team and ask them to put you in contact with the 
Wireless Business unit. They have a team that can assist if you feel it's a 
show-stopper problem.

Jeff


 On Monday, October 24, 2011 at 7:30 AM, in message 
 700d77bb392ae543b5b4455c8db89e3a09cc7...@mbox1.ad.bradley.edumailto:700d77bb392ae543b5b4455c8db89e3a09cc7...@mbox1.ad.bradley.edu,
  Ghere, Shayne 
 sgh...@bumail.bradley.edumailto:sgh...@bumail.bradley.edu wrote:
Hello Craig,

The upgrades were done independently as was the WCS upgrade.   I have the WLC's 
setup with an equal number of AP's on each with Primary, Secondary and Tertiary 
controllers configured so I can upgrade one with them fail over to the others.

I have spent the past 3 weeks pouring over the configurations on each 
WLC...even doing print screens of each to compare and they are completely 
identical.

The WCS (running 7.0.172.0) has settings that the WLC's don't like (7.0.116.0) 
or are mismatched such as power level settings etc.So for those I just set 
on the WLC's and don't push out the templates on the WCS with the odd values.

Here's our history:

May 2010 we started with the 3 WS-C5508 and 1 WCS to handle all the 
dorms/academic/non academic buildings.  We are a single campus (so no wan).  We 
were running 6.0.199.0 on the WLC's (I believe) and there were a few problems.  
 Cisco advised us to upgrade to 6.0.299.0 (maintenance release) to fix another 
issue, then 4 weeks ago upgraded to 7.0.116.0 to fix another problem.

The WCS needed to be upgraded to 7.0.172.0 since the code we were running 
before wouldn't work with the 116.0 on the WLC's.   /ugh

Since the students moved back to campus we've had nothing but radios shutting 
off, AP's completely rebooting, AP's moving to secondary/tertiary controllers 
then back to the primary etc.It has been a NIGHTMARE.

What I'm seeing is that our B/G channels 1,6,11 are also being used by the 450+ 
rogue AP's in the dorms.   We can't shut off the B/G due to older machines, but 
the interference causes the A/N radios to drop as well.

When we were running Autonomous AP's we didn't have this problem, but since 
moving to LWAPP we've had problems.


Thanks
Shayne

From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDUmailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU]
 On Behalf Of Craig Eyre
Sent: Monday, October 24, 2011 9:02 AM
To: 
WIRELESS-LAN@LISTSERV.EDUCAUSE.EDUmailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

Shayne,

Nothing jumps out at me, but I do have a couple questions.

1. What version were you running previously?
2. Did you deploy the upgrade with your WCS?

The reason I ask about the where you upgraded it from, is because a colleague I 
know just upgraded 2 WLC's from his WCS and the settings were different for 
each wlc.


Regards,

Craig Eyre
Network Analyst
IT Services Department
Mount Royal University
4825 Mount Royal Gate SW
Calgary AB T2P 3T5

P. 403.440.5199tel:403.440.5199
E. ce...@mtroyal.camailto:ce...@mtroyal.ca

The difference between a successful person and others

Re: [WIRELESS-LAN] Problems in the Dorms

2011-10-26 Thread Jeffrey Sessler
As Lee mentions, the communication between the AP and the controller is via a 
standard access port. There should be no need to have trunking or and other 
configuration on the port for the AP. Even if the AP has multiple SSIDs and 
VLANs, all of that traffic is encapsulated within CAPWAP.
 
Every port an AP connects to on my campus looks something like this:
interface GigabitEthernet1/0/1
 description Cisco AP
 switchport access vlan 111
 switchport mode access
 spanning-tree portfast

 On Wednesday, October 26, 2011 at 7:02 AM, in message 
 700d77bb392ae543b5b4455c8db89e3a09cc7...@mbox1.ad.bradley.edu, Ghere, 
 Shayne sgh...@bumail.bradley.edu wrote:

Lee,

I've read multiple documents and all say different things on setup.   We
have an internal registration system that we register each AP's mac
address and it's updated (yes we're still using VMPS) in the vmps.cfg
file.  So currently we have each port setup like this:

interface GigabitEthernet0/48
description GPB-AIR2-2 2-16
switchport access vlan dynamic
no logging event link-status
no snmp trap link-status
spanning-tree portfast


We have turned off Spanning-tree, hardcoded it to VLAN 5, hard set it to
1000/Full and even had them setup as trunks to allow ONLY the vlans we
are passing for wireless, but to no avail.

If you have any ideas, please let me know.

Thanks
Shayne

P.S.  Sorry, our e-mail was out yesterday so I couldn't log in to read
or respond.



-Original Message-
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Lee H Badman
Sent: Monday, October 24, 2011 6:08 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

Shayne, please post what your switchport configs look like for the APs.
Also, are you managing the APs on a single network?

Lee H. Badman
Wireless/Network Engineer, ITS
Adjunct Instructor, iSchool
Syracuse University
315.443.3003

From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] on behalf of Jeffrey Sessler
[j...@scrippscollege.edu]
Sent: Monday, October 24, 2011 6:10 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

This sounds/looks a lot more like a network issue then an AP/rogue
problem. The logs suggest the AP's are having problems staying in
contact with the controllers. Everything gigabit from end to end?

What does WCS indicate as the number of channel changes per hour?
As a test, on each 5508, under Wireless, 802.11b/g/n and 802.11a/n, DCA,
change the interval to 6 hours, and the DCA Channel Sensitivity to low.

Do this - contact your Cisco team and ask them to put you in contact
with the Wireless Business unit. They have a team that can assist if you
feel it's a show-stopper problem.

Jeff

 On Monday, October 24, 2011 at 7:30 AM, in message
700d77bb392ae543b5b4455c8db89e3a09cc7...@mbox1.ad.bradley.edu, Ghere,
Shayne sgh...@bumail.bradley.edu wrote:
Hello Craig,

The upgrades were done independently as was the WCS upgrade.   I have
the WLC's setup with an equal number of AP's on each with Primary,
Secondary and Tertiary controllers configured so I can upgrade one with
them fail over to the others.

I have spent the past 3 weeks pouring over the configurations on each
WLC...even doing print screens of each to compare and they are
completely identical.

The WCS (running 7.0.172.0) has settings that the WLC's don't like
(7.0.116.0) or are mismatched such as power level settings etc.So
for those I just set on the WLC's and don't push out the templates on
the WCS with the odd values.

Here's our history:

May 2010 we started with the 3 WS-C5508 and 1 WCS to handle all the
dorms/academic/non academic buildings.  We are a single campus (so no
wan).  We were running 6.0.199.0 on the WLC's (I believe) and there were
a few problems.   Cisco advised us to upgrade to 6.0.299.0 (maintenance
release) to fix another issue, then 4 weeks ago upgraded to 7.0.116.0 to
fix another problem.

The WCS needed to be upgraded to 7.0.172.0 since the code we were
running before wouldn't work with the 116.0 on the WLC's.   /ugh

Since the students moved back to campus we've had nothing but radios
shutting off, AP's completely rebooting, AP's moving to
secondary/tertiary controllers then back to the primary etc.It has
been a NIGHTMARE.

What I'm seeing is that our B/G channels 1,6,11 are also being used by
the 450+ rogue AP's in the dorms.   We can't shut off the B/G due to
older machines, but the interference causes the A/N radios to drop as
well.

When we were running Autonomous AP's we didn't have this problem, but
since moving to LWAPP we've had problems.


Thanks
Shayne

From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Craig Eyre
Sent: Monday, October 24, 2011 9:02 AM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re

RE: [WIRELESS-LAN] Problems in the Dorms

2011-10-26 Thread Lee H Badman
Ditto that.



Lee H. Badman
Wireless/Network Engineer, ITS
Adjunct Instructor, iSchool
Syracuse University
315.443.3003

From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] on behalf of Jeffrey Sessler 
[j...@scrippscollege.edu]
Sent: Wednesday, October 26, 2011 5:48 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

As Lee mentions, the communication between the AP and the controller is via a 
standard access port. There should be no need to have trunking or and other 
configuration on the port for the AP. Even if the AP has multiple SSIDs and 
VLANs, all of that traffic is encapsulated within CAPWAP.

Every port an AP connects to on my campus looks something like this:
interface GigabitEthernet1/0/1
 description Cisco AP
 switchport access vlan 111
 switchport mode access
 spanning-tree portfast

 On Wednesday, October 26, 2011 at 7:02 AM, in message 
 700d77bb392ae543b5b4455c8db89e3a09cc7...@mbox1.ad.bradley.edu, Ghere, 
 Shayne sgh...@bumail.bradley.edu wrote:
Lee,

I've read multiple documents and all say different things on setup.   We
have an internal registration system that we register each AP's mac
address and it's updated (yes we're still using VMPS) in the vmps.cfg
file.  So currently we have each port setup like this:

interface GigabitEthernet0/48
description GPB-AIR2-2 2-16
switchport access vlan dynamic
no logging event link-status
no snmp trap link-status
spanning-tree portfast


We have turned off Spanning-tree, hardcoded it to VLAN 5, hard set it to
1000/Full and even had them setup as trunks to allow ONLY the vlans we
are passing for wireless, but to no avail.

If you have any ideas, please let me know.

Thanks
Shayne

P.S.  Sorry, our e-mail was out yesterday so I couldn't log in to read
or respond.



-Original Message-
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Lee H Badman
Sent: Monday, October 24, 2011 6:08 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

Shayne, please post what your switchport configs look like for the APs.
Also, are you managing the APs on a single network?

Lee H. Badman
Wireless/Network Engineer, ITS
Adjunct Instructor, iSchool
Syracuse University
315.443.3003

From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] on behalf of Jeffrey Sessler
[j...@scrippscollege.edu]
Sent: Monday, October 24, 2011 6:10 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

This sounds/looks a lot more like a network issue then an AP/rogue
problem. The logs suggest the AP's are having problems staying in
contact with the controllers. Everything gigabit from end to end?

What does WCS indicate as the number of channel changes per hour?
As a test, on each 5508, under Wireless, 802.11b/g/n and 802.11a/n, DCA,
change the interval to 6 hours, and the DCA Channel Sensitivity to low.

Do this - contact your Cisco team and ask them to put you in contact
with the Wireless Business unit. They have a team that can assist if you
feel it's a show-stopper problem.

Jeff

 On Monday, October 24, 2011 at 7:30 AM, in message
700d77bb392ae543b5b4455c8db89e3a09cc7...@mbox1.ad.bradley.edu, Ghere,
Shayne sgh...@bumail.bradley.edu wrote:
Hello Craig,

The upgrades were done independently as was the WCS upgrade.   I have
the WLC's setup with an equal number of AP's on each with Primary,
Secondary and Tertiary controllers configured so I can upgrade one with
them fail over to the others.

I have spent the past 3 weeks pouring over the configurations on each
WLC...even doing print screens of each to compare and they are
completely identical.

The WCS (running 7.0.172.0) has settings that the WLC's don't like
(7.0.116.0) or are mismatched such as power level settings etc.So
for those I just set on the WLC's and don't push out the templates on
the WCS with the odd values.

Here's our history:

May 2010 we started with the 3 WS-C5508 and 1 WCS to handle all the
dorms/academic/non academic buildings.  We are a single campus (so no
wan).  We were running 6.0.199.0 on the WLC's (I believe) and there were
a few problems.   Cisco advised us to upgrade to 6.0.299.0 (maintenance
release) to fix another issue, then 4 weeks ago upgraded to 7.0.116.0 to
fix another problem.

The WCS needed to be upgraded to 7.0.172.0 since the code we were
running before wouldn't work with the 116.0 on the WLC's.   /ugh

Since the students moved back to campus we've had nothing but radios
shutting off, AP's completely rebooting, AP's moving to
secondary/tertiary controllers then back to the primary etc.It has
been a NIGHTMARE.

What I'm seeing is that our B/G channels 1,6,11 are also being used by
the 450+ rogue AP's in the dorms.   We can't shut off

Re: [WIRELESS-LAN] Problems in the Dorms

2011-10-24 Thread Harry Rauch
We have seen this on a much smaller scale with some Cisco wireless APs. 
The general repair for us was two-fold: some older APs had capacitors 
starting to swell and new devices had trouble with newer firmware 
upgrades. We backed out the firmware upgrades and these seem to have 
settled down.


We have gone to Ruckus in our dorms due the way the APs handle rogue 
devices and other interferences (wireless controllers, remote controls 
for tvs, microwaves, wireless printers, etc.) The switch seems to have 
dramatically stopped most of our complaints in the dorms.



Harry Rauch Sr. Network Analyst Eckerd College 4200 - 54th Ave S St. 
Petersburg, FL 33711


On 10/22/11 6:52 PM, Ghere, Shayne wrote:


Hello,

We currently provide wireless for all our Dorms using Cisco 1142N 
AP's, 1 WCS and 3 WLC5508's.  We have roughly 375 AP's in the dorms 
but more than 450 rogue AP's that the students brought with them. 
  Since we have no policy to disallow them bringing their own devices, 
we now have a mess.


What we're seeing are the AP's either completely rebooting, radios 
shutting down then coming back up, or if the students are able to 
connect they get dropped after a few minutes.


On the Academic side of the University we don't see this problem, 
however all the AP's are disassociating with the controllers every 
hour, then reassociating again.


The WLC's are running 7.0.116.0 and the WCS is running 7.0.172.0.   It 
appears that since upgrading the controllers to 7.0.116.0 the problems 
started with the disassociating/reassociating with no explanation.


We are using WS-C2960S-PoE switches fibered to the core (6509) and 
have spent almost 28 hours on the phone with Cisco Tac looking at 
logs/packet captures and configuration review.   Nothing is 
misconfigured and the packet captures show the following from one of 
the AP's:


Oct 19 20:55:54.918: %CAPWAP-3-EVENTLOG: Retransmission Count= 3 Max 
Re-Transmission Value=3


*Oct 19 20:55:54.918: %CAPWAP-3-EVENTLOG: Max retransmission count 
exceeded going back to DISCOVER mode.


*Oct 19 20:55:54.918: %CAPWAP-3-EVENTLOG: The function which Posted 
the message to send out of the box is wtpSendEchoReques and of Type=1


., 1)19 20:55:54.918: %CAPWAP-3-EVENTLOG: Retransmission count for 
packet exceeded max(CAPWAP_ECHO_REQUEST


*Oct 19 20:55:54.918: %CAPWAP-3-EVENTLOG: GOING BACK TO DISCOVER MODE

*Oct 19 20:55:54.962: %DTLS-5-SEND_ALERT: Send FATAL : Close notify 
Alert to 136.176.x.x:5246


*Oct 19 20:55:54.962: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.

*Oct 19 20:55:54.963: %CAPWAP-3-EVENTLOG: DTLS session cleanup 
completed. Restarting capwap state machine.


*Oct 19 20:55:55.006: %WIDS-5-DISABLED: IDS Signature is removed and 
disabled.


*Oct 19 20:55:55.008: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Oct 19 20:55:55.008: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Oct 19 20:55:55.063: %LINK-5-CHANGED: Interface Dot11Radio0, changed 
state to administratively down


*Oct 19 20:55:55.063: %LINK-5-CHANGED: Interface Dot11Radio1, changed 
state to administratively down


*Oct 19 20:55:55.065: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort 
sending channel and power levels info.136:176:x.x


*Oct 19 20:55:55.074: %LINK-5-CHANGED: Interface Dot11Radio0, changed 
state to reset


*Oct 19 20:55:55.075: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort 
sending channel and power levels info.136:176:x.x


We're completely at a loss since none of the switch ports, trunk ports 
or the WLC's are showing dropped packets.


Has anyone run into this problem and found a work around?

I would greatly appreciate any help in this matter!

Thanks

Shayne

-

*/Bradley University/*

T. Shayne Ghere, CCNA

Network Engineer

1501 W. Bradley Ave.

Morgan Hall, Suite 205

Peoria, IL  61625

sgh...@bradley.edu

(309) 677-3094  ofc.

(309) 677-3460 fax

*/Class 2011 FBI CA Graduate/*

** 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/.



Re: [WIRELESS-LAN] Problems in the Dorms

2011-10-24 Thread Craig Eyre
Shayne,

Nothing jumps out at me, but I do have a couple questions.

1. What version were you running previously?
2. Did you deploy the upgrade with your WCS?

The reason I ask about the where you upgraded it from, is because a 
colleague I know just upgraded 2 WLC's from his WCS and the settings were 
different for each wlc.


Regards,
 
Craig Eyre 
Network Analyst
IT Services Department
Mount Royal University
4825 Mount Royal Gate SW
Calgary AB T2P 3T5

P. 403.440.5199
E. ce...@mtroyal.ca

The difference between a successful person and others is not a lack of 
strength, not a lack of knowledge, but rather in a lack of will.  Vincent 
T. Lombardi




From:   Ghere, Shayne sgh...@bumail.bradley.edu
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Date:   10/22/2011 04:53 PM
Subject:[WIRELESS-LAN] Problems in the Dorms
Sent by:The EDUCAUSE Wireless Issues Constituent Group Listserv 
WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU



Hello,
 
We currently provide wireless for all our Dorms using Cisco 1142N AP’s, 1 
WCS and 3 WLC5508’s.  We have roughly 375 AP’s in the dorms but more than 
450 rogue AP’s that the students brought with them.   Since we have no 
policy to disallow them bringing their own devices, we now have a mess.
 
What we’re seeing are the AP’s either completely rebooting, radios 
shutting down then coming back up, or if the students are able to connect 
they get dropped after a few minutes.
 
On the Academic side of the University we don’t see this problem, however 
all the AP’s are disassociating with the controllers every hour, then 
reassociating again.
 
The WLC’s are running 7.0.116.0 and the WCS is running 7.0.172.0.   It 
appears that since upgrading the controllers to 7.0.116.0 the problems 
started with the disassociating/reassociating with no explanation.
 
We are using WS-C2960S-PoE switches fibered to the core (6509) and have 
spent almost 28 hours on the phone with Cisco Tac looking at logs/packet 
captures and configuration review.   Nothing is misconfigured and the 
packet captures show the following from one of the AP’s:
 
Oct 19 20:55:54.918: %CAPWAP-3-EVENTLOG: Retransmission Count= 3 Max 
Re-Transmission Value=3
 
*Oct 19 20:55:54.918: %CAPWAP-3-EVENTLOG: Max retransmission count 
exceeded going back to DISCOVER mode.
*Oct 19 20:55:54.918: %CAPWAP-3-EVENTLOG: The function which Posted the 
message to send out of the box is wtpSendEchoReques and of Type=1
 
., 1)19 20:55:54.918: %CAPWAP-3-EVENTLOG: Retransmission count for packet 
exceeded max(CAPWAP_ECHO_REQUEST
*Oct 19 20:55:54.918: %CAPWAP-3-EVENTLOG: GOING BACK TO DISCOVER MODE
*Oct 19 20:55:54.962: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert 
to 136.176.x.x:5246
*Oct 19 20:55:54.962: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.
*Oct 19 20:55:54.963: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. 
Restarting capwap state machine.
*Oct 19 20:55:55.006: %WIDS-5-DISABLED: IDS Signature is removed and 
disabled.
*Oct 19 20:55:55.008: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Oct 19 20:55:55.008: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Oct 19 20:55:55.063: %LINK-5-CHANGED: Interface Dot11Radio0, changed 
state to administratively down
*Oct 19 20:55:55.063: %LINK-5-CHANGED: Interface Dot11Radio1, changed 
state to administratively down
*Oct 19 20:55:55.065: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort 
sending channel and power levels info.136:176:x.x
 
*Oct 19 20:55:55.074: %LINK-5-CHANGED: Interface Dot11Radio0, changed 
state to reset
*Oct 19 20:55:55.075: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort 
sending channel and power levels info.136:176:x.x
 
 
We’re completely at a loss since none of the switch ports, trunk ports or 
the WLC’s are showing dropped packets.
 
Has anyone run into this problem and found a work around?
 
I would greatly appreciate any help in this matter!
 
Thanks
Shayne
 
-
Bradley University
T. Shayne Ghere, CCNA
Network Engineer
1501 W. Bradley Ave.
Morgan Hall, Suite 205
Peoria, IL  61625
sgh...@bradley.edu
(309) 677-3094  ofc.
(309) 677-3460 fax
 
Class 2011 FBI CA Graduate
 
** Participation and subscription information for this EDUCAUSE 
Constituent Group discussion list can be found at 
http://www.educause.edu/groups/. 



RE: [WIRELESS-LAN] Problems in the Dorms

2011-10-24 Thread Helzerman, James
Hi.  In the dorm areas with all the rogue APs do you leave RRM on?  Have you 
tried freezing the configuration or setting channels manually for an area to 
see if the APs continue to reboot?  Just out of curiosity how are you finding 
out you have 450+ rogue APs?  Area any of the dorms next to residential 
non-campus areas?

-Jimmy


James Helzerman
Wireless Network Engineer
University of Michigan
ITS Communications Systems and Data Centers
4251 Plymouth Road,
Building 2, #2224
Ann Arbor, Michigan 48105
Phone: 734-615-9541
Cell: 734-972-5095




From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Ghere, Shayne
Sent: Monday, October 24, 2011 10:31 AM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

Hello Craig,

The upgrades were done independently as was the WCS upgrade.   I have the WLC's 
setup with an equal number of AP's on each with Primary, Secondary and Tertiary 
controllers configured so I can upgrade one with them fail over to the others.

I have spent the past 3 weeks pouring over the configurations on each 
WLC...even doing print screens of each to compare and they are completely 
identical.

The WCS (running 7.0.172.0) has settings that the WLC's don't like (7.0.116.0) 
or are mismatched such as power level settings etc.So for those I just set 
on the WLC's and don't push out the templates on the WCS with the odd values.

Here's our history:

May 2010 we started with the 3 WS-C5508 and 1 WCS to handle all the 
dorms/academic/non academic buildings.  We are a single campus (so no wan).  We 
were running 6.0.199.0 on the WLC's (I believe) and there were a few problems.  
 Cisco advised us to upgrade to 6.0.299.0 (maintenance release) to fix another 
issue, then 4 weeks ago upgraded to 7.0.116.0 to fix another problem.

The WCS needed to be upgraded to 7.0.172.0 since the code we were running 
before wouldn't work with the 116.0 on the WLC's.   /ugh

Since the students moved back to campus we've had nothing but radios shutting 
off, AP's completely rebooting, AP's moving to secondary/tertiary controllers 
then back to the primary etc.It has been a NIGHTMARE.

What I'm seeing is that our B/G channels 1,6,11 are also being used by the 450+ 
rogue AP's in the dorms.   We can't shut off the B/G due to older machines, but 
the interference causes the A/N radios to drop as well.

When we were running Autonomous AP's we didn't have this problem, but since 
moving to LWAPP we've had problems.


Thanks
Shayne

From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Craig Eyre
Sent: Monday, October 24, 2011 9:02 AM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

Shayne,

Nothing jumps out at me, but I do have a couple questions.

1. What version were you running previously?
2. Did you deploy the upgrade with your WCS?

The reason I ask about the where you upgraded it from, is because a colleague I 
know just upgraded 2 WLC's from his WCS and the settings were different for 
each wlc.


Regards,

Craig Eyre
Network Analyst
IT Services Department
Mount Royal University
4825 Mount Royal Gate SW
Calgary AB T2P 3T5

P. 403.440.5199
E. ce...@mtroyal.ca

The difference between a successful person and others is not a lack of 
strength, not a lack of knowledge, but rather in a lack of will.  Vincent T. 
Lombardi




From:Ghere, Shayne sgh...@bumail.bradley.edu
To:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Date:10/22/2011 04:53 PM
Subject:[WIRELESS-LAN] Problems in the Dorms
Sent by:The EDUCAUSE Wireless Issues Constituent Group Listserv 
WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU




Hello,

We currently provide wireless for all our Dorms using Cisco 1142N AP's, 1 WCS 
and 3 WLC5508's.  We have roughly 375 AP's in the dorms but more than 450 rogue 
AP's that the students brought with them.   Since we have no policy to disallow 
them bringing their own devices, we now have a mess.

What we're seeing are the AP's either completely rebooting, radios shutting 
down then coming back up, or if the students are able to connect they get 
dropped after a few minutes.

On the Academic side of the University we don't see this problem, however all 
the AP's are disassociating with the controllers every hour, then reassociating 
again.

The WLC's are running 7.0.116.0 and the WCS is running 7.0.172.0.   It appears 
that since upgrading the controllers to 7.0.116.0 the problems started with the 
disassociating/reassociating with no explanation.

We are using WS-C2960S-PoE switches fibered to the core (6509) and have spent 
almost 28 hours on the phone with Cisco Tac looking at logs/packet captures and 
configuration review.   Nothing is misconfigured and the packet captures show 
the following from one of the AP's:

Oct 19

Re: [WIRELESS-LAN] Problems in the Dorms

2011-10-24 Thread Heath Barnhart
450 sounds like a lot. I've never used Cisco's controllers, but are 
these actually rouge APs or devices with AP behaviors (Ad-hoc, 
smartphone teether, wifi printer, etc)? If they are actual rogue devices 
I would go with what Harry suggested as a way of enforcing policy (if 
you have clause similar to that).


We are in the same boat policy wise, and we require interfering device 
to be removed. I've only got one or two actual rogue APs at the moment, 
the rest are Ad-Hocs.


--

Heath Barnhart, CCNA
Information Systems Services
Washburn Univeristy
Topeka, KS 66621

On 10/24/2011 9:30 AM, Ghere, Shayne wrote:


Hello Craig,

The upgrades were done independently as was the WCS upgrade.   I have 
the WLC’s setup with an equal number of AP’s on each with Primary, 
Secondary and Tertiary controllers configured so I can upgrade one 
with them fail over to the others.


I have spent the past 3 weeks pouring over the configurations on each 
WLC…even doing print screens of each to compare and they are 
completely identical.


The WCS (running 7.0.172.0) has settings that the WLC’s don’t like 
(7.0.116.0) or are mismatched such as power level settings etc.So 
for those I just set on the WLC’s and don’t push out the templates on 
the WCS with the odd values.


Here’s our history:

May 2010 we started with the 3 WS-C5508 and 1 WCS to handle all the 
dorms/academic/non academic buildings.  We are a single campus (so no 
wan).  We were running 6.0.199.0 on the WLC’s (I believe) and there 
were a few problems.   Cisco advised us to upgrade to 6.0.299.0 
(maintenance release) to fix another issue, then 4 weeks ago upgraded 
to 7.0.116.0 to fix another problem.


The WCS needed to be upgraded to 7.0.172.0 since the code we were 
running before wouldn’t work with the 116.0 on the WLC’s.   /ugh


Since the students moved back to campus we’ve had nothing but radios 
shutting off, AP’s completely rebooting, AP’s moving to 
secondary/tertiary controllers then back to the primary etc.It has 
been a NIGHTMARE.


What I’m seeing is that our B/G channels 1,6,11 are also being used by 
the 450+ rogue AP’s in the dorms.   We can’t shut off the B/G due to 
older machines, but the interference causes the A/N radios to drop as 
well.


When we were running Autonomous AP’s we didn’t have this problem, but 
since moving to LWAPP we’ve had problems.


Thanks

Shayne

*From:*The EDUCAUSE Wireless Issues Constituent Group Listserv 
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] *On Behalf Of *Craig Eyre

*Sent:* Monday, October 24, 2011 9:02 AM
*To:* WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
*Subject:* Re: [WIRELESS-LAN] Problems in the Dorms

Shayne,

Nothing jumps out at me, but I do have a couple questions.

1. What version were you running previously?
2. Did you deploy the upgrade with your WCS?

The reason I ask about the where you upgraded it from, is because a 
colleague I know just upgraded 2 WLC's from his WCS and the settings 
were different for each wlc.



Regards,

Craig Eyre
Network Analyst
IT Services Department
Mount Royal University
4825 Mount Royal Gate SW
Calgary AB T2P 3T5

P. 403.440.5199
E. ce...@mtroyal.ca

The difference between a successful person and others is not a lack 
of strength, not a lack of knowledge, but rather in a lack of will. 
 Vincent T. Lombardi





From: Ghere, Shayne sgh...@bumail.bradley.edu
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Date: 10/22/2011 04:53 PM
Subject: [WIRELESS-LAN] Problems in the Dorms
Sent by: The EDUCAUSE Wireless Issues Constituent Group Listserv 
WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU







Hello,

We currently provide wireless for all our Dorms using Cisco 1142N 
AP’s, 1 WCS and 3 WLC5508’s.  We have roughly 375 AP’s in the dorms 
but more than 450 rogue AP’s that the students brought with them.   
Since we have no policy to disallow them bringing their own devices, 
we now have a mess.


What we’re seeing are the AP’s either completely rebooting, radios 
shutting down then coming back up, or if the students are able to 
connect they get dropped after a few minutes.


On the Academic side of the University we don’t see this problem, 
however all the AP’s are disassociating with the controllers every 
hour, then reassociating again.


The WLC’s are running 7.0.116.0 and the WCS is running 7.0.172.0.   It 
appears that since upgrading the controllers to 7.0.116.0 the problems 
started with the disassociating/reassociating with no explanation.


We are using WS-C2960S-PoE switches fibered to the core (6509) and 
have spent almost 28 hours on the phone with Cisco Tac looking at 
logs/packet captures and configuration review.   Nothing is 
misconfigured and the packet captures show the following from one of 
the AP’s:


Oct 19 20:55:54.918: %CAPWAP-3-EVENTLOG: Retransmission Count= 3 Max 
Re-Transmission Value=3


*Oct 19 20:55:54.918

Re: [WIRELESS-LAN] Problems in the Dorms

2011-10-24 Thread Joe Roth
This is reach back a long way (4.x.x maybe?), but at one point we did have
trouble with our WiSMs detecting Cisco LWAPP APs attached to them as rogues,
and actually running mitigation against them. We have since shut down the
auto contain for rogues and this has helped. It's under Security--Wireless
Protection Policies--Rogue Policies. We only have it reporting now.

You may also want to check your mobility configuration and make sure that
mobility is functioning, as I believe this is how the controllers exchange
information about what APs are connected to them so that they do not detect
each other's APs as rogues.

On Mon, Oct 24, 2011 at 11:34 AM, Heath Barnhart 
heath.barnh...@washburn.edu wrote:

  450 sounds like a lot. I've never used Cisco's controllers, but are these
 actually rouge APs or devices with AP behaviors (Ad-hoc, smartphone teether,
 wifi printer, etc)? If they are actual rogue devices I would go with what
 Harry suggested as a way of enforcing policy (if you have clause similar to
 that).

 We are in the same boat policy wise, and we require interfering device to
 be removed. I've only got one or two actual rogue APs at the moment, the
 rest are Ad-Hocs.

 --
 --
 Heath Barnhart, CCNA
 Information Systems Services
 Washburn Univeristy
 Topeka, KS 66621


 On 10/24/2011 9:30 AM, Ghere, Shayne wrote:

  Hello Craig,

 ** **

 The upgrades were done independently as was the WCS upgrade.   I have the
 WLC’s setup with an equal number of AP’s on each with Primary, Secondary and
 Tertiary controllers configured so I can upgrade one with them fail over to
 the others.

 ** **

 I have spent the past 3 weeks pouring over the configurations on each
 WLC…even doing print screens of each to compare and they are completely
 identical.

 ** **

 The WCS (running 7.0.172.0) has settings that the WLC’s don’t like
 (7.0.116.0) or are mismatched such as power level settings etc.So for
 those I just set on the WLC’s and don’t push out the templates on the WCS
 with the odd values.

 ** **

 Here’s our history:

 ** **

 May 2010 we started with the 3 WS-C5508 and 1 WCS to handle all the
 dorms/academic/non academic buildings.  We are a single campus (so no wan).
 We were running 6.0.199.0 on the WLC’s (I believe) and there were a few
 problems.   Cisco advised us to upgrade to 6.0.299.0 (maintenance release)
 to fix another issue, then 4 weeks ago upgraded to 7.0.116.0 to fix another
 problem.

 ** **

 The WCS needed to be upgraded to 7.0.172.0 since the code we were running
 before wouldn’t work with the 116.0 on the WLC’s.   /ugh

 ** **

 Since the students moved back to campus we’ve had nothing but radios
 shutting off, AP’s completely rebooting, AP’s moving to secondary/tertiary
 controllers then back to the primary etc.It has been a NIGHTMARE.

 ** **

 What I’m seeing is that our B/G channels 1,6,11 are also being used by the
 450+ rogue AP’s in the dorms.   We can’t shut off the B/G due to older
 machines, but the interference causes the A/N radios to drop as well. 

 ** **

 When we were running Autonomous AP’s we didn’t have this problem, but since
 moving to LWAPP we’ve had problems.

 ** **

 ** **

 Thanks

 Shayne

 ** **

 *From:* The EDUCAUSE Wireless Issues Constituent Group Listserv [
 mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDUWIRELESS-LAN@LISTSERV.EDUCAUSE.EDU]
 *On Behalf Of *Craig Eyre
 *Sent:* Monday, October 24, 2011 9:02 AM
 *To:* WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
 *Subject:* Re: [WIRELESS-LAN] Problems in the Dorms

 ** **

 Shayne,

 Nothing jumps out at me, but I do have a couple questions.

 1. What version were you running previously?
 2. Did you deploy the upgrade with your WCS?

 The reason I ask about the where you upgraded it from, is because a
 colleague I know just upgraded 2 WLC's from his WCS and the settings were
 different for each wlc.


 Regards,

 Craig Eyre
 Network Analyst
 IT Services Department
 Mount Royal University
 4825 Mount Royal Gate SW
 Calgary AB T2P 3T5

 P. 403.440.5199
 E. ce...@mtroyal.ca

 The difference between a successful person and others is not a lack of
 strength, not a lack of knowledge, but rather in a lack of will.  Vincent
 T. Lombardi




 From:Ghere, Shayne 
 sgh...@bumail.bradley.edusgh...@bumail.bradley.edu
 To:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
 Date:10/22/2011 04:53 PM
 Subject:[WIRELESS-LAN] Problems in the Dorms
 Sent by:The EDUCAUSE Wireless Issues Constituent Group Listserv
 WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
 
  --




 Hello,

 We currently provide wireless for all our Dorms using Cisco 1142N AP’s, 1
 WCS and 3 WLC5508’s.  We have roughly 375 AP’s in the dorms but more than
 450 rogue AP’s that the students brought with them.   Since we have no
 policy to disallow them bringing their own devices, we now have a mess.

 What we’re

RE: [WIRELESS-LAN] Problems in the Dorms

2011-10-24 Thread Lee H Badman
Shayne, please post what your switchport configs look like for the APs. Also, 
are you managing the APs on a single network?

Lee H. Badman
Wireless/Network Engineer, ITS
Adjunct Instructor, iSchool
Syracuse University
315.443.3003

From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] on behalf of Jeffrey Sessler 
[j...@scrippscollege.edu]
Sent: Monday, October 24, 2011 6:10 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

This sounds/looks a lot more like a network issue then an AP/rogue problem. The 
logs suggest the AP's are having problems staying in contact with the 
controllers. Everything gigabit from end to end?

What does WCS indicate as the number of channel changes per hour?
As a test, on each 5508, under Wireless, 802.11b/g/n and 802.11a/n, DCA, change 
the interval to 6 hours, and the DCA Channel Sensitivity to low.

Do this - contact your Cisco team and ask them to put you in contact with the 
Wireless Business unit. They have a team that can assist if you feel it's a 
show-stopper problem.

Jeff

 On Monday, October 24, 2011 at 7:30 AM, in message 
 700d77bb392ae543b5b4455c8db89e3a09cc7...@mbox1.ad.bradley.edu, Ghere, 
 Shayne sgh...@bumail.bradley.edu wrote:
Hello Craig,

The upgrades were done independently as was the WCS upgrade.   I have the WLC’s 
setup with an equal number of AP’s on each with Primary, Secondary and Tertiary 
controllers configured so I can upgrade one with them fail over to the others.

I have spent the past 3 weeks pouring over the configurations on each WLC…even 
doing print screens of each to compare and they are completely identical.

The WCS (running 7.0.172.0) has settings that the WLC’s don’t like (7.0.116.0) 
or are mismatched such as power level settings etc.So for those I just set 
on the WLC’s and don’t push out the templates on the WCS with the odd values.

Here’s our history:

May 2010 we started with the 3 WS-C5508 and 1 WCS to handle all the 
dorms/academic/non academic buildings.  We are a single campus (so no wan).  We 
were running 6.0.199.0 on the WLC’s (I believe) and there were a few problems.  
 Cisco advised us to upgrade to 6.0.299.0 (maintenance release) to fix another 
issue, then 4 weeks ago upgraded to 7.0.116.0 to fix another problem.

The WCS needed to be upgraded to 7.0.172.0 since the code we were running 
before wouldn’t work with the 116.0 on the WLC’s.   /ugh

Since the students moved back to campus we’ve had nothing but radios shutting 
off, AP’s completely rebooting, AP’s moving to secondary/tertiary controllers 
then back to the primary etc.It has been a NIGHTMARE.

What I’m seeing is that our B/G channels 1,6,11 are also being used by the 450+ 
rogue AP’s in the dorms.   We can’t shut off the B/G due to older machines, but 
the interference causes the A/N radios to drop as well.

When we were running Autonomous AP’s we didn’t have this problem, but since 
moving to LWAPP we’ve had problems.


Thanks
Shayne

From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Craig Eyre
Sent: Monday, October 24, 2011 9:02 AM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Problems in the Dorms

Shayne,

Nothing jumps out at me, but I do have a couple questions.

1. What version were you running previously?
2. Did you deploy the upgrade with your WCS?

The reason I ask about the where you upgraded it from, is because a colleague I 
know just upgraded 2 WLC's from his WCS and the settings were different for 
each wlc.


Regards,

Craig Eyre
Network Analyst
IT Services Department
Mount Royal University
4825 Mount Royal Gate SW
Calgary AB T2P 3T5

P. 403.440.5199
E. ce...@mtroyal.ca

The difference between a successful person and others is not a lack of 
strength, not a lack of knowledge, but rather in a lack of will.  Vincent T. 
Lombardi




From:Ghere, Shayne sgh...@bumail.bradley.edu
To:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Date:10/22/2011 04:53 PM
Subject:[WIRELESS-LAN] Problems in the Dorms
Sent by:The EDUCAUSE Wireless Issues Constituent Group Listserv 
WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU




Hello,

We currently provide wireless for all our Dorms using Cisco 1142N AP’s, 1 WCS 
and 3 WLC5508’s.  We have roughly 375 AP’s in the dorms but more than 450 rogue 
AP’s that the students brought with them.   Since we have no policy to disallow 
them bringing their own devices, we now have a mess.

What we’re seeing are the AP’s either completely rebooting, radios shutting 
down then coming back up, or if the students are able to connect they get 
dropped after a few minutes.

On the Academic side of the University we don’t see this problem, however all 
the AP’s are disassociating with the controllers every hour, then reassociating 
again.

The WLC’s are running

Re: [WIRELESS-LAN] Problems in the Dorms

2011-10-24 Thread Mike King
I agree with contacting your Cisco Team.

Back 2005 we opened with a showshopper.  We had a bug that basically caused
an Access Point to reboot when more than 20 users were associated.  Caused a
cascade failure, as each access point was knocked down, it caused more users
to associated to others, knocking them down.

We ran a 24 hour TAC call, running the whole follow the sun gamut.  The
Business Unit was involved at some point during the night.

We eventually downgraded at some point to get stable, but the information we
gathered allowed the bug to be identified and a resolved.

On Mon, Oct 24, 2011 at 6:10 PM, Jeffrey Sessler j...@scrippscollege.eduwrote:

  This sounds/looks a lot more like a network issue then an AP/rogue
 problem. The logs suggest the AP's are having problems staying in contact
 with the controllers. Everything gigabit from end to end?

 What does WCS indicate as the number of channel changes per hour?
 As a test, on each 5508, under Wireless, 802.11b/g/n and 802.11a/n, DCA,
 change the interval to 6 hours, and the DCA Channel Sensitivity to low.

 Do this - contact your Cisco team and ask them to put you in contact with
 the Wireless Business unit. They have a team that can assist if you feel
 it's a show-stopper problem.

 Jeff


  On Monday, October 24, 2011 at 7:30 AM, in message 
 700d77bb392ae543b5b4455c8db89e3a09cc7...@mbox1.ad.bradley.edu, Ghere,
 Shayne sgh...@bumail.bradley.edu wrote:

 Hello Craig,

 ** **

 The upgrades were done independently as was the WCS upgrade.   I have the
 WLC’s setup with an equal number of AP’s on each with Primary, Secondary and
 Tertiary controllers configured so I can upgrade one with them fail over to
 the others.

 ** **

 I have spent the past 3 weeks pouring over the configurations on each
 WLC…even doing print screens of each to compare and they are completely
 identical.

 ** **

 The WCS (running 7.0.172.0) has settings that the WLC’s don’t like
 (7.0.116.0) or are mismatched such as power level settings etc.So for
 those I just set on the WLC’s and don’t push out the templates on the WCS
 with the odd values.

 ** **

 Here’s our history:

 ** **

 May 2010 we started with the 3 WS-C5508 and 1 WCS to handle all the
 dorms/academic/non academic buildings.  We are a single campus (so no wan).
 We were running 6.0.199.0 on the WLC’s (I believe) and there were a few
 problems.   Cisco advised us to upgrade to 6.0.299.0 (maintenance release)
 to fix another issue, then 4 weeks ago upgraded to 7.0.116.0 to fix another
 problem.

 ** **

 The WCS needed to be upgraded to 7.0.172.0 since the code we were running
 before wouldn’t work with the 116.0 on the WLC’s.   /ugh

 ** **

 Since the students moved back to campus we’ve had nothing but radios
 shutting off, AP’s completely rebooting, AP’s moving to secondary/tertiary
 controllers then back to the primary etc.It has been a NIGHTMARE.

 ** **

 What I’m seeing is that our B/G channels 1,6,11 are also being used by the
 450+ rogue AP’s in the dorms.   We can’t shut off the B/G due to older
 machines, but the interference causes the A/N radios to drop as well. 

 ** **

 When we were running Autonomous AP’s we didn’t have this problem, but since
 moving to LWAPP we’ve had problems.

 ** **

 ** **

 Thanks

 Shayne

 ** **

 *From:* The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:
 WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] *On Behalf Of *Craig Eyre
 *Sent:* Monday, October 24, 2011 9:02 AM
 *To:* WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
 *Subject:* Re: [WIRELESS-LAN] Problems in the Dorms

 ** **

 Shayne,

 Nothing jumps out at me, but I do have a couple questions.

 1. What version were you running previously?
 2. Did you deploy the upgrade with your WCS?

 The reason I ask about the where you upgraded it from, is because a
 colleague I know just upgraded 2 WLC's from his WCS and the settings were
 different for each wlc.


 Regards,

 Craig Eyre
 Network Analyst
 IT Services Department
 Mount Royal University
 4825 Mount Royal Gate SW
 Calgary AB T2P 3T5

 P. 403.440.5199
 E. ce...@mtroyal.ca

 The difference between a successful person and others is not a lack of
 strength, not a lack of knowledge, but rather in a lack of will.  Vincent
 T. Lombardi




 From:Ghere, Shayne sgh...@bumail.bradley.edu
 To:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
 Date:10/22/2011 04:53 PM
 Subject:[WIRELESS-LAN] Problems in the Dorms
 Sent by:The EDUCAUSE Wireless Issues Constituent Group Listserv 
 WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU 
  --




 Hello,

 We currently provide wireless for all our Dorms using Cisco 1142N AP’s, 1
 WCS and 3 WLC5508’s.  We have roughly 375 AP’s in the dorms but more than
 450 rogue AP’s that the students brought with them.   Since we have no
 policy to disallow them bringing their own devices, we now have a mess.

 What we’re seeing are the AP’s either

Re: [WIRELESS-LAN] Problems in the Dorms

2011-10-22 Thread Foerst, Daniel P.
Hi Shayne,

That sounds like quite the pickle you are in and I'm sorry I don't have much of 
a technical resolution.

However let me ask this:

You do not have a policy disallowing them bringing their own devices, but do 
you have a policy disallowing anyone using your network from connecting 
equipment that will interfere with the University network?
If so, you have the ability to envoke the clause by completely disconnecting 
(if it needs to go that far) the residential space and mandate that all 
equipment be shutdown, after which you can bring a one building up at a time 
and search for rogue devices, note their MAC addresses and disallow those 
devices to the network. Then, perhaps through NAC, allow each student only one 
device on the network until the situation is better resolved.

Second question: Have you tried going back a code version or more to see if the 
issue resolves?

Obviously you will want to rewrite your policies after the trouble is resolved 
and I know what I suggest is difficult to do, but if you are essentially 
offering little to no service, then my draconian steps are not much worse to 
help resolve the situation. Sadly you sometimes need to amputate if normal 
methods of treatment are not bringing results, but only if it is absolutely 
necessary.

-dan



From: Ghere, Shayne 
sgh...@bumail.bradley.edumailto:sgh...@bumail.bradley.edu
Reply-To: WIRELESS-LAN@LISTSERV. EDU 
WIRELESS-LAN@LISTSERV.EDUCAUSE.EDUmailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Date: Sat, 22 Oct 2011 17:52:40 -0500
To: WIRELESS-LAN@LISTSERV. EDU 
WIRELESS-LAN@LISTSERV.EDUCAUSE.EDUmailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: [WIRELESS-LAN] Problems in the Dorms

Hello,

We currently provide wireless for all our Dorms using Cisco 1142N AP’s, 1 WCS 
and 3 WLC5508’s.  We have roughly 375 AP’s in the dorms but more than 450 rogue 
AP’s that the students brought with them.   Since we have no policy to disallow 
them bringing their own devices, we now have a mess.

What we’re seeing are the AP’s either completely rebooting, radios shutting 
down then coming back up, or if the students are able to connect they get 
dropped after a few minutes.

On the Academic side of the University we don’t see this problem, however all 
the AP’s are disassociating with the controllers every hour, then reassociating 
again.

The WLC’s are running 7.0.116.0 and the WCS is running 7.0.172.0.   It appears 
that since upgrading the controllers to 7.0.116.0 the problems started with the 
disassociating/reassociating with no explanation.

We are using WS-C2960S-PoE switches fibered to the core (6509) and have spent 
almost 28 hours on the phone with Cisco Tac looking at logs/packet captures and 
configuration review.   Nothing is misconfigured and the packet captures show 
the following from one of the AP’s:

Oct 19 20:55:54.918: %CAPWAP-3-EVENTLOG: Retransmission Count= 3 Max 
Re-Transmission Value=3

*Oct 19 20:55:54.918: %CAPWAP-3-EVENTLOG: Max retransmission count exceeded 
going back to DISCOVER mode.
*Oct 19 20:55:54.918: %CAPWAP-3-EVENTLOG: The function which Posted the message 
to send out of the box is wtpSendEchoReques and of Type=1

., 1)19 20:55:54.918: %CAPWAP-3-EVENTLOG: Retransmission count for packet 
exceeded max(CAPWAP_ECHO_REQUEST
*Oct 19 20:55:54.918: %CAPWAP-3-EVENTLOG: GOING BACK TO DISCOVER MODE
*Oct 19 20:55:54.962: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 
136.176.x.x:5246
*Oct 19 20:55:54.962: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.
*Oct 19 20:55:54.963: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. 
Restarting capwap state machine.
*Oct 19 20:55:55.006: %WIDS-5-DISABLED: IDS Signature is removed and disabled.
*Oct 19 20:55:55.008: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Oct 19 20:55:55.008: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Oct 19 20:55:55.063: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to 
administratively down
*Oct 19 20:55:55.063: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to 
administratively down
*Oct 19 20:55:55.065: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending 
channel and power levels info.136:176:x.x

*Oct 19 20:55:55.074: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to 
reset
*Oct 19 20:55:55.075: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending 
channel and power levels info.136:176:x.x


We’re completely at a loss since none of the switch ports, trunk ports or the 
WLC’s are showing dropped packets.

Has anyone run into this problem and found a work around?

I would greatly appreciate any help in this matter!

Thanks
Shayne

-
Bradley University
T. Shayne Ghere, CCNA
Network Engineer
1501 W. Bradley Ave.
Morgan Hall, Suite 205
Peoria, IL  61625
sgh...@bradley.edumailto:sgh...@bradley.edu
(309) 677-3094  ofc.
(309) 677-3460 fax

Class 2011 FBI CA Graduate

** Participation and subscription information for this EDUCAUSE 
Constituent Group discussion