RE: [WIRELESS-LAN] Client DHCP issues after WLC upgrade
Thanks Mike and Loc, The more TAC cases opened for this the better. It's getting the WNBUs attention, and needs to be checked in for resolution in the next release (so far looks like they're still trying to isolate the issue -- don't be surprised if they ask you to actively monitor). The bug as described is exactly what I'm seeing. I see the Decrypt errors in the sh controller d0 | beg --Clients output, and there's no issues with Open authentication WLAN clients. 5.2.193 appears immune to this. Reference CSCtf34858 when opening the case. Call early and often. --Bruce Johnson -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Schomer, Michael J. Sent: Wednesday, March 31, 2010 2:45 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade No, we didn't get a fix for it yet, although Cisco says they're working on it. At this point we are pretty sure we are running into bugID CSCtf34858. -Mike -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Pham, Loc Sent: Tuesday, March 30, 2010 11:57 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Mike, do you get the fix for it ? I am ready to call TAC now Running to exactly the same issue. Loc -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Schomer, Michael J. Sent: Tuesday, March 23, 2010 6:28 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Disabling dhcp-proxy didn't work for us. After chatting with Cisco I think we are running into BugID CSCte08161 or CSCtf34858. We upgraded to 6.0.196 this morning, which should rule out CSCte08161. Since all the access points rebooted in the process, we probably won't know if it fixed it for a day or so. If not, our solution will probably be to reset the radios every morning, at least until Cisco develops a more permanent solution... and probably a new bug in the process! -Mike -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Charles Spurgeon Sent: Friday, March 19, 2010 5:06 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Although the AssureWave doc lists the CSCtd84852 bugID as a caveat in 6.0.196.0 code, that bugID it is superseded by CSCte08161. The new bugID says the issue is fixed in AP code 12.4(21a)JHA. We just upgraded our system to 6.0.196.0 and the APs are now running 12.4(21a)JHA code. The latest v6.0 release notes also state that bugID CSCte08161 is resolved in v6.0.196.0. We've asked our Cisco support channel to confirm, but going by the evidence of the new bugID and the release notes, it looks like this issue is resolved in the latest 6.0 MR2 code. -Charles Charles E. Spurgeon / UTnet UT Austin ITS / Networking c.spurg...@its.utexas.edu / 512.475.9265 On Thu, Mar 18, 2010 at 01:17:11PM -0500, Schomer, Michael J. wrote: I know 6.0.196 is AssurWave, but it also lists the issue we might be having as a caveat. We did test 6.0.188 on one of our WLCs for a few months and decided to go with the known quantity. From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Lee H Badman Sent: Thursday, March 18, 2010 12:15 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade If I'm not mistaken- and I'm not trying to be snarky- 5.2.178 was also AssureWave. Am pretty sure of that. __ From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Mike King Sent: Thursday, March 18, 2010 1:00 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Hey Mike, I didn't know 6.0.196 was released. I just checked it out, and 6.0.196 is AssureWave. This is one of the point releases that Cisco releases that has had extensive testing with multiple devices / vendors / software products. It's similar to the old Safe Harbor release. Here's the doc to it: [1]http://www.cisco.com/en/US/netsol/ns779/networking_solutions_progra m_category_home.html The test results actually show the test methodolgy, and it's pretty extensive. [2]http://www.cisco.com/en/US/solutions/collateral/n s340/ns414/ns779/AssureWave-WLC-Release-6.0.196.0-Results.pdf It also gives a list
RE: [WIRELESS-LAN] Client DHCP issues after WLC upgrade
No, we didn't get a fix for it yet, although Cisco says they're working on it. At this point we are pretty sure we are running into bugID CSCtf34858. -Mike -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Pham, Loc Sent: Tuesday, March 30, 2010 11:57 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Mike, do you get the fix for it ? I am ready to call TAC now Running to exactly the same issue. Loc -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Schomer, Michael J. Sent: Tuesday, March 23, 2010 6:28 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Disabling dhcp-proxy didn't work for us. After chatting with Cisco I think we are running into BugID CSCte08161 or CSCtf34858. We upgraded to 6.0.196 this morning, which should rule out CSCte08161. Since all the access points rebooted in the process, we probably won't know if it fixed it for a day or so. If not, our solution will probably be to reset the radios every morning, at least until Cisco develops a more permanent solution... and probably a new bug in the process! -Mike -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Charles Spurgeon Sent: Friday, March 19, 2010 5:06 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Although the AssureWave doc lists the CSCtd84852 bugID as a caveat in 6.0.196.0 code, that bugID it is superseded by CSCte08161. The new bugID says the issue is fixed in AP code 12.4(21a)JHA. We just upgraded our system to 6.0.196.0 and the APs are now running 12.4(21a)JHA code. The latest v6.0 release notes also state that bugID CSCte08161 is resolved in v6.0.196.0. We've asked our Cisco support channel to confirm, but going by the evidence of the new bugID and the release notes, it looks like this issue is resolved in the latest 6.0 MR2 code. -Charles Charles E. Spurgeon / UTnet UT Austin ITS / Networking c.spurg...@its.utexas.edu / 512.475.9265 On Thu, Mar 18, 2010 at 01:17:11PM -0500, Schomer, Michael J. wrote: I know 6.0.196 is AssurWave, but it also lists the issue we might be having as a caveat. We did test 6.0.188 on one of our WLCs for a few months and decided to go with the known quantity. From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Lee H Badman Sent: Thursday, March 18, 2010 12:15 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade If I'm not mistaken- and I'm not trying to be snarky- 5.2.178 was also AssureWave. Am pretty sure of that. __ From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Mike King Sent: Thursday, March 18, 2010 1:00 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Hey Mike, I didn't know 6.0.196 was released. I just checked it out, and 6.0.196 is AssureWave. This is one of the point releases that Cisco releases that has had extensive testing with multiple devices / vendors / software products. It's similar to the old Safe Harbor release. Here's the doc to it: [1]http://www.cisco.com/en/US/netsol/ns779/networking_solutions_progra m_category_home.html The test results actually show the test methodolgy, and it's pretty extensive. [2]http://www.cisco.com/en/US/solutions/collateral/n s340/ns414/ns779/AssureWave-WLC-Release-6.0.196.0-Results.pdf It also gives a list of Bugs (at the end) that the testers felt should be considered before upgrading On Thu, Mar 18, 2010 at 11:40 AM, Schomer, Michael J. [3]mjscho...@stcloudstate.edu wrote: Hello, We are noticing a problem on our WPA/802.1x SSID with some of our clients after a recent Cisco WLC upgrade from 5.2.178 to 6.0.188. The clients are able to connect and authenticate to the SSID; however, they aren't receiving an IP address. We have ruled out the DHCP server as the problem. This doesn't affect all clients, and the problem seems to come and go. We haven't seen a common OS or chipset among the clients that are having problems. We currently are running four WLCs in production, and all of them received the upgrade at the same time. The only thing that most of these clients have in common is that they are associated
RE: [WIRELESS-LAN] Client DHCP issues after WLC upgrade
Mike, do you get the fix for it ? I am ready to call TAC now Running to exactly the same issue. Loc -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Schomer, Michael J. Sent: Tuesday, March 23, 2010 6:28 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Disabling dhcp-proxy didn't work for us. After chatting with Cisco I think we are running into BugID CSCte08161 or CSCtf34858. We upgraded to 6.0.196 this morning, which should rule out CSCte08161. Since all the access points rebooted in the process, we probably won't know if it fixed it for a day or so. If not, our solution will probably be to reset the radios every morning, at least until Cisco develops a more permanent solution... and probably a new bug in the process! -Mike -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Charles Spurgeon Sent: Friday, March 19, 2010 5:06 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Although the AssureWave doc lists the CSCtd84852 bugID as a caveat in 6.0.196.0 code, that bugID it is superseded by CSCte08161. The new bugID says the issue is fixed in AP code 12.4(21a)JHA. We just upgraded our system to 6.0.196.0 and the APs are now running 12.4(21a)JHA code. The latest v6.0 release notes also state that bugID CSCte08161 is resolved in v6.0.196.0. We've asked our Cisco support channel to confirm, but going by the evidence of the new bugID and the release notes, it looks like this issue is resolved in the latest 6.0 MR2 code. -Charles Charles E. Spurgeon / UTnet UT Austin ITS / Networking c.spurg...@its.utexas.edu / 512.475.9265 On Thu, Mar 18, 2010 at 01:17:11PM -0500, Schomer, Michael J. wrote: I know 6.0.196 is AssurWave, but it also lists the issue we might be having as a caveat. We did test 6.0.188 on one of our WLCs for a few months and decided to go with the known quantity. From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Lee H Badman Sent: Thursday, March 18, 2010 12:15 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade If I'm not mistaken- and I'm not trying to be snarky- 5.2.178 was also AssureWave. Am pretty sure of that. __ From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Mike King Sent: Thursday, March 18, 2010 1:00 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Hey Mike, I didn't know 6.0.196 was released. I just checked it out, and 6.0.196 is AssureWave. This is one of the point releases that Cisco releases that has had extensive testing with multiple devices / vendors / software products. It's similar to the old Safe Harbor release. Here's the doc to it: [1]http://www.cisco.com/en/US/netsol/ns779/networking_solutions_progra m_category_home.html The test results actually show the test methodolgy, and it's pretty extensive. [2]http://www.cisco.com/en/US/solutions/collateral/n s340/ns414/ns779/AssureWave-WLC-Release-6.0.196.0-Results.pdf It also gives a list of Bugs (at the end) that the testers felt should be considered before upgrading On Thu, Mar 18, 2010 at 11:40 AM, Schomer, Michael J. [3]mjscho...@stcloudstate.edu wrote: Hello, We are noticing a problem on our WPA/802.1x SSID with some of our clients after a recent Cisco WLC upgrade from 5.2.178 to 6.0.188. The clients are able to connect and authenticate to the SSID; however, they aren't receiving an IP address. We have ruled out the DHCP server as the problem. This doesn't affect all clients, and the problem seems to come and go. We haven't seen a common OS or chipset among the clients that are having problems. We currently are running four WLCs in production, and all of them received the upgrade at the same time. The only thing that most of these clients have in common is that they are associated to APs on two particular controllers. The only thing unique about those two controllers is that they have mostly 1131 APs. When the clients roam to a different WLC, they can usually connect just fine. I'm at a loss right now. We did test the 6.0.188 code in one building (with 1250 APs) for several months before deploying it, without any notable issues. We are now potentially looking at downgrading back to 5.2 code, but aren't
RE: [WIRELESS-LAN] Client DHCP issues after WLC upgrade
Disabling dhcp-proxy didn't work for us. After chatting with Cisco I think we are running into BugID CSCte08161 or CSCtf34858. We upgraded to 6.0.196 this morning, which should rule out CSCte08161. Since all the access points rebooted in the process, we probably won't know if it fixed it for a day or so. If not, our solution will probably be to reset the radios every morning, at least until Cisco develops a more permanent solution... and probably a new bug in the process! -Mike -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Charles Spurgeon Sent: Friday, March 19, 2010 5:06 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Although the AssureWave doc lists the CSCtd84852 bugID as a caveat in 6.0.196.0 code, that bugID it is superseded by CSCte08161. The new bugID says the issue is fixed in AP code 12.4(21a)JHA. We just upgraded our system to 6.0.196.0 and the APs are now running 12.4(21a)JHA code. The latest v6.0 release notes also state that bugID CSCte08161 is resolved in v6.0.196.0. We've asked our Cisco support channel to confirm, but going by the evidence of the new bugID and the release notes, it looks like this issue is resolved in the latest 6.0 MR2 code. -Charles Charles E. Spurgeon / UTnet UT Austin ITS / Networking c.spurg...@its.utexas.edu / 512.475.9265 On Thu, Mar 18, 2010 at 01:17:11PM -0500, Schomer, Michael J. wrote: I know 6.0.196 is AssurWave, but it also lists the issue we might be having as a caveat. We did test 6.0.188 on one of our WLCs for a few months and decided to go with the known quantity. From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Lee H Badman Sent: Thursday, March 18, 2010 12:15 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade If I'm not mistaken- and I'm not trying to be snarky- 5.2.178 was also AssureWave. Am pretty sure of that. __ From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Mike King Sent: Thursday, March 18, 2010 1:00 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Hey Mike, I didn't know 6.0.196 was released. I just checked it out, and 6.0.196 is AssureWave. This is one of the point releases that Cisco releases that has had extensive testing with multiple devices / vendors / software products. It's similar to the old Safe Harbor release. Here's the doc to it: [1]http://www.cisco.com/en/US/netsol/ns779/networking_solutions_progra m_category_home.html The test results actually show the test methodolgy, and it's pretty extensive. [2]http://www.cisco.com/en/US/solutions/collateral/n s340/ns414/ns779/AssureWave-WLC-Release-6.0.196.0-Results.pdf It also gives a list of Bugs (at the end) that the testers felt should be considered before upgrading On Thu, Mar 18, 2010 at 11:40 AM, Schomer, Michael J. [3]mjscho...@stcloudstate.edu wrote: Hello, We are noticing a problem on our WPA/802.1x SSID with some of our clients after a recent Cisco WLC upgrade from 5.2.178 to 6.0.188. The clients are able to connect and authenticate to the SSID; however, they aren't receiving an IP address. We have ruled out the DHCP server as the problem. This doesn't affect all clients, and the problem seems to come and go. We haven't seen a common OS or chipset among the clients that are having problems. We currently are running four WLCs in production, and all of them received the upgrade at the same time. The only thing that most of these clients have in common is that they are associated to APs on two particular controllers. The only thing unique about those two controllers is that they have mostly 1131 APs. When the clients roam to a different WLC, they can usually connect just fine. I'm at a loss right now. We did test the 6.0.188 code in one building (with 1250 APs) for several months before deploying it, without any notable issues. We are now potentially looking at downgrading back to 5.2 code, but aren't thrilled about it. Another option would be to upgrade to 6.0.196, but we haven't done any testing of that code revision. Has anyone seen a similar issue? Does anyone know of any issues with 6.0.188 code and 1131 APs? Any thoughts or advice would be appreciated. Thanks for your help. -Mike Schomer -St. Cloud State University ** Participation and subscription
RE: [WIRELESS-LAN] Client DHCP issues after WLC upgrade
Charles, thanks for the tips. FYI, we just stuck with 6.0.182 by default when we purchase an 5508... Seem that 6.0.196 is better AssureWave ?!! I will check the bug-list and choose my poison ;-] Rest of my LWAPP farm (85%) still at 4.2.207. Loc -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Charles Spurgeon Sent: Friday, March 19, 2010 3:06 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Although the AssureWave doc lists the CSCtd84852 bugID as a caveat in 6.0.196.0 code, that bugID it is superseded by CSCte08161. The new bugID says the issue is fixed in AP code 12.4(21a)JHA. We just upgraded our system to 6.0.196.0 and the APs are now running 12.4(21a)JHA code. The latest v6.0 release notes also state that bugID CSCte08161 is resolved in v6.0.196.0. We've asked our Cisco support channel to confirm, but going by the evidence of the new bugID and the release notes, it looks like this issue is resolved in the latest 6.0 MR2 code. -Charles Charles E. Spurgeon / UTnet UT Austin ITS / Networking c.spurg...@its.utexas.edu / 512.475.9265 On Thu, Mar 18, 2010 at 01:17:11PM -0500, Schomer, Michael J. wrote: I know 6.0.196 is AssurWave, but it also lists the issue we might be having as a caveat. We did test 6.0.188 on one of our WLCs for a few months and decided to go with the known quantity. From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Lee H Badman Sent: Thursday, March 18, 2010 12:15 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade If I'm not mistaken- and I'm not trying to be snarky- 5.2.178 was also AssureWave. Am pretty sure of that. __ From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Mike King Sent: Thursday, March 18, 2010 1:00 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Hey Mike, I didn't know 6.0.196 was released. I just checked it out, and 6.0.196 is AssureWave. This is one of the point releases that Cisco releases that has had extensive testing with multiple devices / vendors / software products. It's similar to the old Safe Harbor release. Here's the doc to it: [1]http://www.cisco.com/en/US/netsol/ns779/networking_solutions_progra m_category_home.html The test results actually show the test methodolgy, and it's pretty extensive. [2]http://www.cisco.com/en/US/solutions/collateral/n s340/ns414/ns779/AssureWave-WLC-Release-6.0.196.0-Results.pdf It also gives a list of Bugs (at the end) that the testers felt should be considered before upgrading On Thu, Mar 18, 2010 at 11:40 AM, Schomer, Michael J. [3]mjscho...@stcloudstate.edu wrote: Hello, We are noticing a problem on our WPA/802.1x SSID with some of our clients after a recent Cisco WLC upgrade from 5.2.178 to 6.0.188. The clients are able to connect and authenticate to the SSID; however, they aren't receiving an IP address. We have ruled out the DHCP server as the problem. This doesn't affect all clients, and the problem seems to come and go. We haven't seen a common OS or chipset among the clients that are having problems. We currently are running four WLCs in production, and all of them received the upgrade at the same time. The only thing that most of these clients have in common is that they are associated to APs on two particular controllers. The only thing unique about those two controllers is that they have mostly 1131 APs. When the clients roam to a different WLC, they can usually connect just fine. I'm at a loss right now. We did test the 6.0.188 code in one building (with 1250 APs) for several months before deploying it, without any notable issues. We are now potentially looking at downgrading back to 5.2 code, but aren't thrilled about it. Another option would be to upgrade to 6.0.196, but we haven't done any testing of that code revision. Has anyone seen a similar issue? Does anyone know of any issues with 6.0.188 code and 1131 APs? Any thoughts or advice would be appreciated. Thanks for your help. -Mike Schomer -St. Cloud State University ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at [4]http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list
RE: [WIRELESS-LAN] Client DHCP issues after WLC upgrade
This morning we disabled DHCP Proxy and reset all the radios. I'll keep the list posted. Thanks for all the suggestions! -Mike From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Jason Cook Sent: Thursday, March 18, 2010 5:49 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade We've had some varying dhcp issues over various releases since 2007, we've generally found a way to resolve. Upgrading drivers has helped, but that's more been with individual client issues, not when you have a number of clients on various OS's having similar issues. We have had similar issues in the past where clients roam between AP's on different controllers and changed the design of our network to reduce roaming between controllers. So rather than having a building with 10 AP's where they are alternately connected to different controllers, the whole building is connected to one. Due to the closeness of buildings we've generally allocated buildings in close proximity to each other to go to the same controller as well as neighboring buildings. Since then (2 years ago) we've had only 3-5 reports a year on this issue, and mostly due to someone mis-configuring primary's for access points. If it's not mis-config then normally it's a neighboring building on seperate controllers so we investigate AP locations, primary controllers and radio power levels and modify the config as seems best. We also had one controller playing up that would simply not provide dhcp to about 90% of clients. After amount of un-successful troubleshooting with TAC we decided (not their suggestion) to set the controller to default and re-config it from scratch. It's been great ever since, we hadn't just upgraded, and it was somewhere in 5.2. Disabling dhcp proxy has also helped resolve a number of issues. Perhaps not ideal solutions for everyone, but certainly has worked well for us. We run 4404-100's and a mixture of 1131, 1231, 1250 and 1142 and noticed no difference to clients on different AP types it's all referred to controllers and roaming. Jason On 19/03/2010 5:18 AM, Lee Weers wrote: No we are not running dhcp proxy. Thank you, Lee Weers Central College Assistant Director for Network Services 641-628-7675 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Lee H Badman Sent: Thursday, March 18, 2010 11:16 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDUmailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Mike, and Lee- are you guys running DHCP proxy on your controllers? -Lee Lee H. Badman Wireless/Network Engineer Information Technology and Services Adjunct Instructor, iSchool Syracuse University 315 443-3003 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Schomer, Michael J. Sent: Thursday, March 18, 2010 11:40 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDUmailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Hello, We are noticing a problem on our WPA/802.1x SSID with some of our clients after a recent Cisco WLC upgrade from 5.2.178 to 6.0.188. The clients are able to connect and authenticate to the SSID; however, they aren't receiving an IP address. We have ruled out the DHCP server as the problem. This doesn't affect all clients, and the problem seems to come and go. We haven't seen a common OS or chipset among the clients that are having problems. We currently are running four WLCs in production, and all of them received the upgrade at the same time. The only thing that most of these clients have in common is that they are associated to APs on two particular controllers. The only thing unique about those two controllers is that they have mostly 1131 APs. When the clients roam to a different WLC, they can usually connect just fine. I'm at a loss right now. We did test the 6.0.188 code in one building (with 1250 APs) for several months before deploying it, without any notable issues. We are now potentially looking at downgrading back to 5.2 code, but aren't thrilled about it. Another option would be to upgrade to 6.0.196, but we haven't done any testing of that code revision. Has anyone seen a similar issue? Does anyone know of any issues with 6.0.188 code and 1131 APs? Any thoughts or advice would be appreciated. Thanks for your help. -Mike Schomer -St. Cloud State University ** 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] Client DHCP issues after WLC upgrade
Although the AssureWave doc lists the CSCtd84852 bugID as a caveat in 6.0.196.0 code, that bugID it is superseded by CSCte08161. The new bugID says the issue is fixed in AP code 12.4(21a)JHA. We just upgraded our system to 6.0.196.0 and the APs are now running 12.4(21a)JHA code. The latest v6.0 release notes also state that bugID CSCte08161 is resolved in v6.0.196.0. We've asked our Cisco support channel to confirm, but going by the evidence of the new bugID and the release notes, it looks like this issue is resolved in the latest 6.0 MR2 code. -Charles Charles E. Spurgeon / UTnet UT Austin ITS / Networking c.spurg...@its.utexas.edu / 512.475.9265 On Thu, Mar 18, 2010 at 01:17:11PM -0500, Schomer, Michael J. wrote: I know 6.0.196 is AssurWave, but it also lists the issue we might be having as a caveat. We did test 6.0.188 on one of our WLCs for a few months and decided to go with the known quantity. From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Lee H Badman Sent: Thursday, March 18, 2010 12:15 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade If I'm not mistaken- and I'm not trying to be snarky- 5.2.178 was also AssureWave. Am pretty sure of that. __ From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Mike King Sent: Thursday, March 18, 2010 1:00 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Hey Mike, I didn't know 6.0.196 was released. I just checked it out, and 6.0.196 is AssureWave. This is one of the point releases that Cisco releases that has had extensive testing with multiple devices / vendors / software products. It's similar to the old Safe Harbor release. Here's the doc to it: [1]http://www.cisco.com/en/US/netsol/ns779/networking_solutions_progra m_category_home.html The test results actually show the test methodolgy, and it's pretty extensive. [2]http://www.cisco.com/en/US/solutions/collateral/n s340/ns414/ns779/AssureWave-WLC-Release-6.0.196.0-Results.pdf It also gives a list of Bugs (at the end) that the testers felt should be considered before upgrading On Thu, Mar 18, 2010 at 11:40 AM, Schomer, Michael J. [3]mjscho...@stcloudstate.edu wrote: Hello, We are noticing a problem on our WPA/802.1x SSID with some of our clients after a recent Cisco WLC upgrade from 5.2.178 to 6.0.188. The clients are able to connect and authenticate to the SSID; however, they aren't receiving an IP address. We have ruled out the DHCP server as the problem. This doesn't affect all clients, and the problem seems to come and go. We haven't seen a common OS or chipset among the clients that are having problems. We currently are running four WLCs in production, and all of them received the upgrade at the same time. The only thing that most of these clients have in common is that they are associated to APs on two particular controllers. The only thing unique about those two controllers is that they have mostly 1131 APs. When the clients roam to a different WLC, they can usually connect just fine. I'm at a loss right now. We did test the 6.0.188 code in one building (with 1250 APs) for several months before deploying it, without any notable issues. We are now potentially looking at downgrading back to 5.2 code, but aren't thrilled about it. Another option would be to upgrade to 6.0.196, but we haven't done any testing of that code revision. Has anyone seen a similar issue? Does anyone know of any issues with 6.0.188 code and 1131 APs? Any thoughts or advice would be appreciated. Thanks for your help. -Mike Schomer -St. Cloud State University ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at [4]http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at [5]http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at [6]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/. References 1. http://www.cisco.com/en/US/netsol/ns779/networking_solutions_program_category_home.html 2. http://www.cisco.com/en/US/solutions/collateral
RE: [WIRELESS-LAN] Client DHCP issues after WLC upgrade
We have been experiencing the same problem as well with 6.0.188. What we see is mostly with 1252's. It is almost like a client can't decide between 2 ap's on different controllers. We have controllers 1, 3, 4, 5, 6, and 7. We experience the problem the most when an ap is on controller4 and another ap on controller6. Both controllers show the client connected to them, but the client doesn't get an ip address. When we shutdown one of the ap's then the client is happy, or they roam to an ap on another controller. We keep suspecting something wrong with controller6, but I have compared the configs of all the controllers and the only difference between the controllers are the wlan id numbers. Thank you, Lee Weers Central College Assistant Director for Network Services 641-628-7675 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Schomer, Michael J. Sent: Thursday, March 18, 2010 10:40 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Hello, We are noticing a problem on our WPA/802.1x SSID with some of our clients after a recent Cisco WLC upgrade from 5.2.178 to 6.0.188. The clients are able to connect and authenticate to the SSID; however, they aren't receiving an IP address. We have ruled out the DHCP server as the problem. This doesn't affect all clients, and the problem seems to come and go. We haven't seen a common OS or chipset among the clients that are having problems. We currently are running four WLCs in production, and all of them received the upgrade at the same time. The only thing that most of these clients have in common is that they are associated to APs on two particular controllers. The only thing unique about those two controllers is that they have mostly 1131 APs. When the clients roam to a different WLC, they can usually connect just fine. I'm at a loss right now. We did test the 6.0.188 code in one building (with 1250 APs) for several months before deploying it, without any notable issues. We are now potentially looking at downgrading back to 5.2 code, but aren't thrilled about it. Another option would be to upgrade to 6.0.196, but we haven't done any testing of that code revision. Has anyone seen a similar issue? Does anyone know of any issues with 6.0.188 code and 1131 APs? Any thoughts or advice would be appreciated. Thanks for your help. -Mike Schomer -St. Cloud State University ** 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] Client DHCP issues after WLC upgrade
In doing debug info with cisco tac just resulted in a It is a client driver issue. Thank you, Lee Weers Central College Assistant Director for Network Services 641-628-7675 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Schomer, Michael J. Sent: Thursday, March 18, 2010 10:40 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Hello, We are noticing a problem on our WPA/802.1x SSID with some of our clients after a recent Cisco WLC upgrade from 5.2.178 to 6.0.188. The clients are able to connect and authenticate to the SSID; however, they aren't receiving an IP address. We have ruled out the DHCP server as the problem. This doesn't affect all clients, and the problem seems to come and go. We haven't seen a common OS or chipset among the clients that are having problems. We currently are running four WLCs in production, and all of them received the upgrade at the same time. The only thing that most of these clients have in common is that they are associated to APs on two particular controllers. The only thing unique about those two controllers is that they have mostly 1131 APs. When the clients roam to a different WLC, they can usually connect just fine. I'm at a loss right now. We did test the 6.0.188 code in one building (with 1250 APs) for several months before deploying it, without any notable issues. We are now potentially looking at downgrading back to 5.2 code, but aren't thrilled about it. Another option would be to upgrade to 6.0.196, but we haven't done any testing of that code revision. Has anyone seen a similar issue? Does anyone know of any issues with 6.0.188 code and 1131 APs? Any thoughts or advice would be appreciated. Thanks for your help. -Mike Schomer -St. Cloud State University ** 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] Client DHCP issues after WLC upgrade
Hi, This sounds very much like an issue that we had, Cisco got involved, told us repeatedly that it was a client issue, then finally accepted it was a Cisco issue. The bug is CSCtd84852, although it doesn't read like the problem I describe above, I'm assured by our Cisco partner that it's the same bug. I was also told that V7 would address the bug, and that V7 would be released in March, this was in January this year. We rolled back to v4 (despite Cisco telling us it would make no difference) and the problem went away. If you debug a failing client, what do you see? There were a couple of different failing scenarios, but primarily we saw a repeated retransmission of M5 to the client then failure. The controller saw no reply from the client, but it would seem from the air captures we did and supplied to Cisco that the client did respond. Debug client client MAC We found that resetting the dot11 interface on the AP cleared the fault for some time, so we implemented a script to detect failed clients on a controller and reset the respective APs. Very messy though. I'll tentatively try v7 on one or two controllers when it's released. Aruba looks very appealing at the minute for our imminent re-procurement, but it could be a case of grass is greener... Cheers, Jezz. From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Lee Weers Sent: 18 March 2010 16:03 To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade In doing debug info with cisco tac just resulted in a It is a client driver issue. Thank you, Lee Weers Central College Assistant Director for Network Services 641-628-7675 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Schomer, Michael J. Sent: Thursday, March 18, 2010 10:40 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Hello, We are noticing a problem on our WPA/802.1x SSID with some of our clients after a recent Cisco WLC upgrade from 5.2.178 to 6.0.188. The clients are able to connect and authenticate to the SSID; however, they aren't receiving an IP address. We have ruled out the DHCP server as the problem. This doesn't affect all clients, and the problem seems to come and go. We haven't seen a common OS or chipset among the clients that are having problems. We currently are running four WLCs in production, and all of them received the upgrade at the same time. The only thing that most of these clients have in common is that they are associated to APs on two particular controllers. The only thing unique about those two controllers is that they have mostly 1131 APs. When the clients roam to a different WLC, they can usually connect just fine. I'm at a loss right now. We did test the 6.0.188 code in one building (with 1250 APs) for several months before deploying it, without any notable issues. We are now potentially looking at downgrading back to 5.2 code, but aren't thrilled about it. Another option would be to upgrade to 6.0.196, but we haven't done any testing of that code revision. Has anyone seen a similar issue? Does anyone know of any issues with 6.0.188 code and 1131 APs? Any thoughts or advice would be appreciated. Thanks for your help. -Mike Schomer -St. Cloud State University ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade
Hey Mike, I didn't know 6.0.196 was released. I just checked it out, and 6.0.196 is AssureWave. This is one of the point releases that Cisco releases that has had extensive testing with multiple devices / vendors / software products. It's similar to the old Safe Harbor release. Here's the doc to it: http://www.cisco.com/en/US/netsol/ns779/networking_solutions_program_category_home.html The test results actually show the test methodolgy, and it's pretty extensive. http://www.cisco.com/en/US/solutions/collateral/ns340/ns414/ns779/AssureWave-WLC-Release-6.0.196.0-Results.pdf It also gives a list of Bugs (at the end) that the testers felt should be considered before upgrading http://www.cisco.com/en/US/netsol/ns779/networking_solutions_program_category_home.html On Thu, Mar 18, 2010 at 11:40 AM, Schomer, Michael J. mjscho...@stcloudstate.edu wrote: Hello, We are noticing a problem on our WPA/802.1x SSID with some of our clients after a recent Cisco WLC upgrade from 5.2.178 to 6.0.188. The clients are able to connect and authenticate to the SSID; however, they aren’t receiving an IP address. We have ruled out the DHCP server as the problem. This doesn’t affect all clients, and the problem seems to come and go. We haven’t seen a common OS or chipset among the clients that are having problems. We currently are running four WLCs in production, and all of them received the upgrade at the same time. The only thing that most of these clients have in common is that they are associated to APs on two particular controllers. The only thing unique about those two controllers is that they have mostly 1131 APs. When the clients roam to a different WLC, they can usually connect just fine. I’m at a loss right now. We did test the 6.0.188 code in one building (with 1250 APs) for several months before deploying it, without any notable issues. We are now potentially looking at downgrading back to 5.2 code, but aren’t thrilled about it. Another option would be to upgrade to 6.0.196, but we haven’t done any testing of that code revision. Has anyone seen a similar issue? Does anyone know of any issues with 6.0.188 code and 1131 APs? Any thoughts or advice would be appreciated. Thanks for your help. -Mike Schomer -St. Cloud State University ** 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] Client DHCP issues after WLC upgrade
I know 6.0.196 is AssurWave, but it also lists the issue we might be having as a caveat. We did test 6.0.188 on one of our WLCs for a few months and decided to go with the known quantity. From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Lee H Badman Sent: Thursday, March 18, 2010 12:15 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade If I'm not mistaken- and I'm not trying to be snarky- 5.2.178 was also AssureWave. Am pretty sure of that. From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Mike King Sent: Thursday, March 18, 2010 1:00 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Hey Mike, I didn't know 6.0.196 was released. I just checked it out, and 6.0.196 is AssureWave. This is one of the point releases that Cisco releases that has had extensive testing with multiple devices / vendors / software products. It's similar to the old Safe Harbor release. Here's the doc to it: http://www.cisco.com/en/US/netsol/ns779/networking_solutions_program_category_home.html The test results actually show the test methodolgy, and it's pretty extensive. http://www.cisco.com/en/US/solutions/collateral/ns340/ns414/ns779/AssureWave-WLC-Release-6.0.196.0-Results.pdf It also gives a list of Bugs (at the end) that the testers felt should be considered before upgrading On Thu, Mar 18, 2010 at 11:40 AM, Schomer, Michael J. mjscho...@stcloudstate.edumailto:mjscho...@stcloudstate.edu wrote: Hello, We are noticing a problem on our WPA/802.1x SSID with some of our clients after a recent Cisco WLC upgrade from 5.2.178 to 6.0.188. The clients are able to connect and authenticate to the SSID; however, they aren't receiving an IP address. We have ruled out the DHCP server as the problem. This doesn't affect all clients, and the problem seems to come and go. We haven't seen a common OS or chipset among the clients that are having problems. We currently are running four WLCs in production, and all of them received the upgrade at the same time. The only thing that most of these clients have in common is that they are associated to APs on two particular controllers. The only thing unique about those two controllers is that they have mostly 1131 APs. When the clients roam to a different WLC, they can usually connect just fine. I'm at a loss right now. We did test the 6.0.188 code in one building (with 1250 APs) for several months before deploying it, without any notable issues. We are now potentially looking at downgrading back to 5.2 code, but aren't thrilled about it. Another option would be to upgrade to 6.0.196, but we haven't done any testing of that code revision. Has anyone seen a similar issue? Does anyone know of any issues with 6.0.188 code and 1131 APs? Any thoughts or advice would be appreciated. Thanks for your help. -Mike Schomer -St. Cloud State University ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade
I don't think so. But I can't confirm nor deny it, because Cisco isn't archiving the releases that were AssureWave. My disbelief is because I sent an email to the AssureWave alias dated Januray 6th 2010, asking when / if there would be a 5.x or a 6.x AssureWave release, since we were about to purchase 1142N access Points, and I wanted to be on a stable release. There was talk on the mailing list last year that 5.2 something was an AssureWave Candidate, but nothing came of it. I never got anything but a bounce message from the email alias. Mike On Thu, Mar 18, 2010 at 1:14 PM, Lee H Badman lhbad...@syr.edu wrote: If I’m not mistaken- and I’m not trying to be snarky- 5.2.178 was also AssureWave. Am pretty sure of that. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
RE: [WIRELESS-LAN] Client DHCP issues after WLC upgrade
No we are not running dhcp proxy. Thank you, Lee Weers Central College Assistant Director for Network Services 641-628-7675 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Lee H Badman Sent: Thursday, March 18, 2010 11:16 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Mike, and Lee- are you guys running DHCP proxy on your controllers? -Lee Lee H. Badman Wireless/Network Engineer Information Technology and Services Adjunct Instructor, iSchool Syracuse University 315 443-3003 From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Schomer, Michael J. Sent: Thursday, March 18, 2010 11:40 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Hello, We are noticing a problem on our WPA/802.1x SSID with some of our clients after a recent Cisco WLC upgrade from 5.2.178 to 6.0.188. The clients are able to connect and authenticate to the SSID; however, they aren't receiving an IP address. We have ruled out the DHCP server as the problem. This doesn't affect all clients, and the problem seems to come and go. We haven't seen a common OS or chipset among the clients that are having problems. We currently are running four WLCs in production, and all of them received the upgrade at the same time. The only thing that most of these clients have in common is that they are associated to APs on two particular controllers. The only thing unique about those two controllers is that they have mostly 1131 APs. When the clients roam to a different WLC, they can usually connect just fine. I'm at a loss right now. We did test the 6.0.188 code in one building (with 1250 APs) for several months before deploying it, without any notable issues. We are now potentially looking at downgrading back to 5.2 code, but aren't thrilled about it. Another option would be to upgrade to 6.0.196, but we haven't done any testing of that code revision. Has anyone seen a similar issue? Does anyone know of any issues with 6.0.188 code and 1131 APs? Any thoughts or advice would be appreciated. Thanks for your help. -Mike Schomer -St. Cloud State University ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade
We've had some varying dhcp issues over various releases since 2007, we've generally found a way to resolve. Upgrading drivers has helped, but that's more been with individual client issues, not when you have a number of clients on various OS's having similar issues. We have had similar issues in the past where clients roam between AP's on different controllers and changed the design of our network to reduce roaming between controllers. So rather than having a building with 10 AP's where they are alternately connected to different controllers, the whole building is connected to one. Due to the closeness of buildings we've generally allocated buildings in close proximity to each other to go to the same controller as well as neighboring buildings. Since then (2 years ago) we've had only 3-5 reports a year on this issue, and mostly due to someone mis-configuring primary's for access points. If it's not mis-config then normally it's a neighboring building on seperate controllers so we investigate AP locations, primary controllers and radio power levels and modify the config as seems best. We also had one controller playing up that would simply not provide dhcp to about 90% of clients. After amount of un-successful troubleshooting with TAC we decided (not their suggestion) to set the controller to default and re-config it from scratch. It's been great ever since, we hadn't just upgraded, and it was somewhere in 5.2. Disabling dhcp proxy has also helped resolve a number of issues. Perhaps not ideal solutions for everyone, but certainly has worked well for us. We run 4404-100's and a mixture of 1131, 1231, 1250 and 1142 and noticed no difference to clients on different AP types it's all referred to controllers and roaming. Jason On 19/03/2010 5:18 AM, Lee Weers wrote: No we are not running dhcp proxy. Thank you, Lee Weers Central College Assistant Director for Network Services 641-628-7675 *From:* The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] *On Behalf Of *Lee H Badman *Sent:* Thursday, March 18, 2010 11:16 AM *To:* WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU *Subject:* Re: [WIRELESS-LAN] Client DHCP issues after WLC upgrade Mike, and Lee- are you guys running DHCP proxy on your controllers? -Lee Lee H. Badman Wireless/Network Engineer Information Technology and Services Adjunct Instructor, iSchool Syracuse University 315 443-3003 *From:* The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] *On Behalf Of *Schomer, Michael J. *Sent:* Thursday, March 18, 2010 11:40 AM *To:* WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU *Subject:* [WIRELESS-LAN] Client DHCP issues after WLC upgrade Hello, We are noticing a problem on our WPA/802.1x SSID with some of our clients after a recent Cisco WLC upgrade from 5.2.178 to 6.0.188. The clients are able to connect and authenticate to the SSID; however, they aren't receiving an IP address. We have ruled out the DHCP server as the problem. This doesn't affect all clients, and the problem seems to come and go. We haven't seen a common OS or chipset among the clients that are having problems. We currently are running four WLCs in production, and all of them received the upgrade at the same time. The only thing that most of these clients have in common is that they are associated to APs on two particular controllers. The only thing unique about those two controllers is that they have mostly 1131 APs. When the clients roam to a different WLC, they can usually connect just fine. I'm at a loss right now. We did test the 6.0.188 code in one building (with 1250 APs) for several months before deploying it, without any notable issues. We are now potentially looking at downgrading back to 5.2 code, but aren't thrilled about it. Another option would be to upgrade to 6.0.196, but we haven't done any testing of that code revision. Has anyone seen a similar issue? Does anyone know of any issues with 6.0.188 code and 1131 APs? Any thoughts or advice would be appreciated. Thanks for your help. -Mike Schomer -St. Cloud State University ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. -- Jason Cook Technology Services The University of Adelaide, AUSTRALIA 5005 Ph: +61 8 8313 4800 e-mail: jason.c...@adelaide.edu.au CRICOS Provider Number 00123M --- This email message
