06-27-2013 12:27 PM - edited 07-04-2021 12:18 AM
I have a couple of questions surrounding the Office Extend 600 series access points.
Currently we have 2- WLC5508s.
1) In the Deployment guide it mentions turning off Aironet IE and Coverage Hole Detection. Is this required, or just highly recommended? What types of issues are we expected to encounter if we have Aironet IE and Coverage Hold Detection enabled with Office Extend AP's?
2) In a Primary, Secondary configuration of WLC controllers, I would need to setup another NAT configuration for the second controller int he event of a failover correct? Any alternatives?
Solved! Go to Solution.
06-29-2013 12:17 PM
If you mean the user end is the 192 it shouldn't matter because the oe ap nats this to the outside ip address of the oe ap.
Sent from Cisco Technical Support iPhone App
06-27-2013 12:35 PM
Hi
My install has been in production for over a year. Going off memory we had some issues with aironet extensions enabled. Some clients would connect at all. It also recommended to have all the encryption types selected. You may have seen this already as well.
Yes, each box have its own ip and own nat. In my install I have each box and outside IP address rather than deal with nat.
Hope some of this helps ..
Sent from Cisco Technical Support iPhone App
06-27-2013 12:48 PM
Ok. Problem is we have current Production WLANs setup on the same controller.
I would either have to change the SSID or change the config ont eh Production SSIDs. Same thing for WPA2 Encryption types. We have AES only enabled at this time.
Any problem with disabling Aironet IE on production networks? What is the expected issue with doing so?
Also. Any known problems with keeping coverage hole detection enabled?
06-27-2013 12:58 PM
Ok so I understand your oe will connect to inside controllers not a DMZ controller. Thats fine .. Here is another way to skin this cat ..
You can create the same ssid as production but name it differently under the profile name. So you can have the same WLAN ssid name.
Under the new WLAN number it above 16, same 100. Configure this one as spec'd in the oe manual.
Then create an ap group for your oe aps and include WLAN 100 in the group.
This way you can have the same ssid, different configs. Since the WLAN is above 16 they don't get broadcasted out unless you put the aps in the group.
Make sense ?
Sent from Cisco Technical Support iPhone App
06-27-2013 01:10 PM
I have tried that and it complains. It doesnt like Duplicate SSID and security settings.
Thoughts?
06-27-2013 01:13 PM
Yes, just want to make sure you did indeed make the profile name different than the already configured WLAN. It should work, that's how I have it here ..
Sent from Cisco Technical Support iPhone App
06-27-2013 01:20 PM
Yeah. I had different profile names but it didnt stick until i put the new WLAN with a index higher than 16.
06-27-2013 01:13 PM
Ok. Hold up.
I put it in an Index above 100 and BAM!
I'll try that. Thanks
06-27-2013 01:15 PM
Excellent .. Create an ap group an you will have the ability to have identical ssid names while keeping your corp as is and meeting the best practice of office extends.
If any of this is helpful. Support me we a few rates! Thanks
Sent from Cisco Technical Support iPhone App
06-27-2013 01:21 PM
Ok. So this entire time i thought the users(s) problem was related to Wireless but it was the "Remote LAN". The user needs to release DHCP before traffic begins flowing again. It keeps the IP configuration just stops communicating.
06-27-2013 01:34 PM
You just lost me .. We were discussing wlans .. What's the matter with rlans..
Sent from Cisco Technical Support iPad App
06-27-2013 01:40 PM
Yeah i lost myself as well.
No the issue that first sparked this thread i thoguht was related to WLANs. So looking through the deployment guide i noticed that Aironet IE and Coverage Hole Detection should not be enabled. Then I found out that the user was having a problem on the RLAN.
Every now and then the user has to release DHCP and renew to be able to use network. It works fine and then all the sudden they have to do renew DHCP, they dont get a different address and thier IP configuration is not lost when network communication seizes.
06-27-2013 01:57 PM
Did you mess with the phy rates ?
Read this https://supportforums.cisco.com/thread/2101846
Sent from Cisco Technical Support iPad App
06-28-2013 06:01 AM
I dont have any of the 802.11g rates set to Mandatory.
I did however notice that the users Office Extend AP address is 192.168.0.13. So this user has the Office Extend WAN port connected to a switch port on thier existing home network.
We also have a active IPSec tunnel to another location that matches traffic to (192.168.0.0 /24 - same as home users network). Is this causing the issue?
Remember we have the controller on the (inside) natting to a WWW address.
Is the issue the IPSec tunnel or is it recommended not to set the Office Extend behind an existing NAT\Firewall device?
06-29-2013 12:17 PM
If you mean the user end is the 192 it shouldn't matter because the oe ap nats this to the outside ip address of the oe ap.
Sent from Cisco Technical Support iPhone App
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide