Cisco Wireless :: 5500 / Dhcp Proxy Option In Controller?
Jul 2, 2012
While configuring a 5500 wireless controller, i came across this option of DHCP proxy under Advanced tab of Controller Option.It asks for the dhcp option 82 remote id format & the dhcp timeout.
1. What is the significance of this & when do we use it?
2. Also, under each wlan ssid that we create, there is an option of dhcp address required under the advanced tab. Do we need to use this option, if we are defining a normal dhcp pool in our controller for that ssid.
How to disable dhcp proxy on controller and what is the impact of doing it in the middle? We tried once by giving 'config dhcp proxy disable' command but seeing virtual ip again.(likely it gets back to proxy mode). We also have ip helper address on the L3 interface. We have only external dhcp servers configured..
We are trying to navigate the waters in choosing between a in-house, controller-based, wireless network solution or a cloud-based solution. We have been presented with the usual suspects in cloud-based (Aerohive, Meracki, etc) and with Cisco (5500) and Aruba on the other side. We are a multi-campus organization with approx. 200 APs.Any hard reasons why go with a controller-based vs. cloud-based solution? If we must keep the conversation limited to Cisco, why go Meracki over Cisco's WLC solutions or vise versa?
Have a client wanting to hand out public ip addresses to all clients from a PFSense Firewall terminating the internet connection.
How do I allow the Cisco Switches currently in place, configured with private ip addresses in the 10.10.x.x ranges and Vlans, where the main 3550 layer 3 has defined dhcp scopes for each vlan, to relay dhcp requests from all vlans to the PFSense firewall?
I assume I would take off the currently defined dhcp scopes for the vlans and configure each vlan/switch with the ip helper address and specify the PFSense firewall and that Nat would have to be disabled onthe firewall?
I have two 5500-controllers and one WCS-server. Now I will have to move the WCS-server to another subnet and change the IP, but it will keep the name.Will that effect the connection between the controllers and the WCS?Do I have the change anything in the configuration on the controllers or the WCS-server?
I am working on a project that will involve 5500 controllers managing 1260 series N rate A/Ps. There may be a requirement for MESH but my previous experience using Motorola 802.11a radios is that random, intermittent radio detections resulted in the MESH network having to keep re-forming resulting in less than 100% availability.
What's peoples experience in the UK is 802.11a outdoors?
Ideally i would prefer to use 2.4GHz and repeater access points for those areas not serviced with data connection but I cant find any info' so far on how whether the 5500 controller is able to manage repeater access points.
I have a Cisco ASA 5500 as the main router with a DIR-655 as a wireless access point behind it. DHCP is turned off on the 655 as the ASA is providing DHCP. This worked great for about a year and now suddenly, without any changes, I'm having problems. The only thing that connects without a problem is a laptop, which shows up on the device list with an IP. Other devices have problems. iPhones connect, show an IP on the device itself, but when listed in the connected list on the 655 show no IP. The connection is super slow. An Airport Express will connect, but again, shows no IP in the connected list on the 655. Using the ethernet cable from the Airport Express, nothing can get an IP. I can live with the iPhone not connecting, but the Airport Express not connecting is a major problem. Any reason why this would just stop working one day?
I am using a WLC 5508 and its internal DHCP server. I cant find anywhere I can setup option 43. However, the access points are connected in just fine. Do I need to worry about setting up a seperate DHCP server to get option 43 setup properly?
I have Cisco 1131 & 1300 Light Weight Acces Points and I have 5508 WLAN controller. If i enable the wlan controller internal DHCP Server can this access points will work with this internal DHCP server or do i need to configure DHCP option 43 for these access points? Can these access points works with LWAPP or do i need to configure CAPWAP?
I have 5500 controller with firmware 7.0 installed from the factory. Due to some reasons, I understood that other existing wireless infrastructure runs on firmware 6.0, and hance i need to downgrade the 5500 series to 6.0 . During the bootup, i could see there is another image called backup recovery image, which is running on version 6.0. How can i reboot controller to use the older image , which is from backup recovery image. I couldnt find it in the configuration guide.
Is it possible to regain the PSK from the security tab from a 5500 controller in clear text?I need to check the current used password without resetting it, but I fail to find the password in the configuration (CLI & web interface)Obviously I do have admin access to my controller.
The Release Notes for 7.0.116.0 of WLC 5500 has a table which title is "Client Type", and it shows wireless adapters. My question is, what kind of customer means? Wireless clients or clients for an specific application? If it was the first option, does it mean tha just this adapters could connect to my wireless network?
i have cisco CAP 3602e series access point to work with 5500 series controller with code 7.0i did not find VCI option 60 for this type of APs to configure DHCP. How I can let these APs will join the controller, i mean through which process DNS discovery methode and what about if i need to configure option 60 and 43 in dhcp for ap joining process to controllers.
I'm trying to configure my Cisco Router 2811 which is also acting as the DHCP server for my branch office for DHCP option 60 and 43 so Aruba AP's at my branch can discover it's master Controller? What is the command I need to enter in the Cisco router?
Is it possible to configure DHCP option 150 on the RV220? I have a Cisco 7940 IP phone that is trying to connect back to my office. The VPN is up and I can ping the relevant server but I can't see any way to configure the DHCP option.
I have a RV042 VPN Router with the latest firmware v4.2.1.02.This Router is connected to the main site by a VPN Tunnel.
Now, I like to configure some DHCP Option so I can put a IP Phone behind the RV042. The IP Phone should receive a IP by DHCP from the RV042 and of course, the IP of the Call Manager with the Option 150.
I can configure DHCP and it works fine but I can't find where I have or can configure Option 150.
I have sample lab dhcp-client ------- (vlan62) sg-300 switch (vlan62) ------ dhcp server
When I set on switch :
dhcp relay : enable option 82 : enable dhcp server address: ip of dhcp
When debug packets from client to server, there is no 82 option in dhcp discover packets. I mirror all traffic to mirror port with wireshark. I can see dhcp packets but without option 82.
with our WLC 5500 controller, once the clients get the DHCP address the page is not redirecting them to the guest portal.What is the best way to check as to why the redirection is failing.
I convert IOS Cisco AP 1130 LAP to 1130 Autonomous mode. Well, the periphericals - clients connect to SSID AP no recieved I.P Adress, I think that is not possible active option DHCP server in AP 1130 dispositive. In mode I.P static clients the connection is established successfully.
I have a very simple setup containing 3 C2960S switches:switch 1: central switch, acting as router between VLAN 1 en VLAN 2switch 2+3: edge switches, connected via 1 link to central switch, both on VLAN 2,Clients connect to switch 2 and 3 using dhcp, switch 1 uses dhcp relay to forward requests from VLAN 2 to the dhcp server on VLAN 1. So far so good.Now I want switch 1 to add option 82 to the dhcp requests so the dhcp server can see whether the request came through switch 2 or switch 3. I tried turning on dhcp option 82 support on switch 1 by doing.
In RFC 951, the format of BOOTP packet was legislated, but the vendor information was not legislated in this document, so the authors of this document had described that :"If the 'vend' field is used, it is recommended that a 4 byte 'magic number' be the first item within 'vend'. This lets a server determine what kind of information it is seeing in this field. "
I think it meant that the format of vendor information wasn't fixed in RFC 951, and any vendor can legislate a new format of vendor information by itself. And the value in "magic cookie" can be set by any vendor.But in RFC 2131, the format of DHCP packet was legislated, and the "magic cooke" was fixed to values 99, 130, 83 and 99, I think it meant that the format of option information in DHCP packet was fixed absolutely and any vendor can't legislate a new format by itself.
Since the format of option information in DHCP packet was fixed absolutely, why the network device needs "magic cookie" to identify the mode in which the succeeding data is to be interpreted ? I think the magic cookie is not useful in DHCP packet because the format of option information is fixed. In other words, there is only one format of option information forever.
in one of the sites, the client has an exisiting 4402 controller which he moved to the DMZ in order to set it as an anchor & he purchased two new 5508 controllers to control the corporate APs. I configured all the parameters needed for the guest anchoring & then I tested the connection but there was an issue. (all the controllers are running the same firmware version)after testing the setup, the guest users could get an IP from the internal DHCP of the anchor controller (in DMZ), but then they cannot reach the internet or anything outside the anchor controller.Cisco confirmed that the 4400 is fully compatible with the 5500 to work in an anchor-foreign secnario as long as they are running the same firmware version. yet, when I temporarily used one of the 5500 controller in the DMZ as an anchor & I applied the exact same configurations on it as the 4400, it worked perfectly without any issues.
note: on the anchor controller (4400), the management & AP-manager interfaces reside on the same subnet & the wireless guest SSID is also mapped to the management interface. (may be this setup is causing the issue) but on the 5500 it is working just fine?
Having an issue with my WLC 5500 and client connectivity. This just started today. Clients will connect for a short period of time and then drop off. WLC appears fine with the exception of a bunch of trap errors. I've rebooted the WLC but this did not clear the issue.
I have an ASA 5500 series and am looking to set up the AnyConnect VPN. Looking at this guide everything seems fairly straightforward. However, on the inside private network DHCP is setup and I was wondering if it was possible to just use DHCP instead of providing a static address pool? I did not see any option to do this.
I own a Nanostation5 Loco, and I have a router behind it.I would like to add a DHCP Lease to that router and do a port forward to the router.I can not find the DHCP Lease option in Nanostation settings, but if I choose to see DHCP Leases in "Extra info" on main page I can see some MAC and IP addresses there.When it comes to port forwarding, I fill the form slots with info, and when I press OK to save it a pop-up comes saying "Please fill out this field", a field for another forward rule.
I have a Cisco Wlan Controller 2504 with 1042N AP (3-nos) every thing was working fine from past 2 months. Now i am getting a issue with clients which are connected to the wireless AP, they are not able to get an dhcp IP address from the 2960 Switch (DHCP Server). The clients are getting IP address as 0.0.0.0. [code]
I have a 5508 WLC controller at the HQ with the employee ssid ,the dhcp scope on the ssid is 10.120.0.0/16 network.
However,I want this same ssid to be brodcasted to a remote site using HREAP access point but with different dhcp scope 10.102.0.0/16.
I have tried creating another interface for the remote site with a different dhcp scope(10.102.0.0) but the controller wont allow me create another wlan with same ssid that existed before to apply the new interface created for.
All controllers are in version 7.2.111.3.C1 is a 5508, it is ou anchor controller.C2 is a 5508, it is a big site controller.C3 is a 2504, it is a small site controller. C2 and C3 are in the same mobility group than C1 (and all is up up in mobilty managment). When "DHCP Addr. Assignment" is enable on C1 : Clients on C2 received their IP address by our external DHCP server via C1 and the guest tunneling betwenn C1 and C2 and all is working fine. Clients on C3 don't received their IP address by our external DHCP server via C1 and the guest tunneling betwenn C1 and C3, so nothing work.
I am trying to setup a guest vlan. I set up an interface for the guest vlan on my 4402 controller. I assigned the guest vlan interface an IP of 192.168.2.10 with a 24 bit subnet mask.
This vlan will go to my DMZ where there is no DHCP server so I need to setup the internal DHCP server. I created a new scope but I'm having trouble with what to put in the Network field for the DHCP scope. The pool addresses are 192.168.2.100-200. with a 24 bit subnet mask.
Every time I try to apply the configuration I get an "error in setting DHCP scope network and netmask".
I've tried using:
192.168.2.10 192.168.2.255 192.168.2.254
as entries for the Network setting but no go. The docs say to enter the IP address used by the management interface with subnet mask applied.
I was assuming they meant the interface for the guest vlan.
