[wlc] secondary wlc in a 1:1, Ip dhcp pool redundancy

Hello

I will put up a high availability of 1:1 with 2 wlc 2504.

I need to enter the ip address primary and backup controller and name to each AP.
Unfortunately, we have a lot of AP and AP will more soon; it manually will take some time.

I wonder if there is a way to give the secondary ip address to the ip dhcp pool? or any other stand-alone solution.

Thank you very much

For any additional consultation
LINK: https://learningnetwork.cisco.com/thread/66301

To quote one of the answers:
The global primary and secondary come into play if there is no primary or secondary configured specifically in the AP. personally I've never used it however if you had only two controllers that would be ideal. I just see by specifying more granular level AP. personally I always use the HA tab for the ap as you never know how the deployment will evolve. You may fail aps to only one controller several controllers. You may need the HA failover priority. It is always useful to understand what will happen when your controllers fail and can become interesting if you have several controllers with several groups of AP and RF to profiles that you really need start controlling what ap's going where.

As you can see, most of the Admins do not configure the Global setting.
Just be patient in their configuration by AP XD

Tags: Cisco Support

Similar Questions

WLC Campus Design - 10 controllers etc.

Hi guys,.

If I have the following scenarios,

2 sites and each site will be broken up by 100km (just an example to show that wireless reached between them) and have 100 APs in each site.

Please see the attached diagram.

Both sites have two controllers on site or a domain controller centralized (if there is a preferred method)?

Anyway,.

Two controllers for site1 (1 on each DC for example) should be in the same group of mobility.

Site controllers 2 should be in a different group of mobility?

Also, if this design developed by a factor of 5, and we had now 20 + controllers, controllers each either on one VLAN separate in the domain controllers or could I create a controller wireless VLAN that has all the controllers connected to?

Please note that, on the previous point, the domain controllers have NO VLAN for layer 2 between them, so that each set of controllers (by site, one in each ms) are sensitive to the layer 3 wanders, but the basic principle, we will use is that each site will have a PDC and a BDC and all items should be on the same controller.

Also, for most small Wireless deployments, is better to have a set of controllers of nmanager small sites, say for APs 5 to 10 per site? BUT then, you can't have a group of mobility for the controller so would this cause a problem? Oh, now I'm confused?

Anyone can comment on the above drawings?

Thx a lot.

Ken

REAP H works well in the code of 4.2. I have about 30 sites with the up to 5 1252 mode operation REAP H return to the a single domain controller. The domain controller has 2 4404-100 and I divided the primary one and secondary to the other sites.

As for redundancy, should watch how you manage the clients ip address. N + N is the most popular because you always have 100% redundancy. It can either be on site or to the domain controller.

Now you can also make N + 1, one in the local site and the other in the domain controller. Now, you have to look at what ip address users will get when they are on the wlc primary and when the primary fails and AP, go to wlc backup. Now, you have clients getting and the ip address on the central site (DC) and the traffic here. So now, you have to watch the traffic flow and how you configure your acl, if necessary.

N + N + 1 can work for you if you have a WISN in the two DC. Then for the site 1:

Primary school DC1WISM1-WLC1

High school DC2WISM1-WLC1

Tertiary DC1WISM1-WLC2

Or you can have a 4404-100 on each site that primary and a 4404-100 on each secondary and tertiary domain controller. You will need one at each site and two on each controller domain just for two remote sites. Now, please understand what is needed for smaller remote sites.

It boils down to cost and is it better to keep the wlc on site since if the wan goes down, resources is not available on the domain controller. Also if you place the different primary and secondary or tertiary in ip subnets, how will you manage ip addressing customer will get from the wlc.

Also... Stick with the 4.2 If you need to deploy h - harvest. Do not go with the 5.0 or 5.1 again. %.0 is the worst and 5.1 is too new and could focus on the issues raised in the 5.0 and could introduce more.

AIR-LAP1242AG-A-K9 cannot adhere to WLC

Guys,

I have problem, I try to connect AIR-LAP1242AG-A-K9 AP WLC 4400 with the 7.0.98.218 software, but the HA indicator is blink and always request new IP address (based on console logg AP), this device can ping from LAN but unstable (based on logg, the always AP request new IP address).

Anyone have experience with this case?

It's newspaper when I try the console to AP.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

XMODEM file system is available.

flashfs [0]: 15 files, 4 folders

flashfs [0]: 0 orphaned files, orphaned directories 0

flashfs [0]: Total number of bytes: 15998976

flashfs [0]: bytes used: 10084864

flashfs [0]: available bytes: 5914112

flashfs [0]: flashfs fsck took 36 seconds.

Basic Ethernet MAC address: 00: 1 d: 45:36:86:ca

Initialization of the ethernet port 0...

Reset the ethernet port 0...

Reset done!

upward, 100 Mbps, full-duplex Ethernet link

Ethernet port initialized 0: connection is established

Loading "flash:/c1240-k9w8-mx.124-23c.JZ/c1240-k9w8-mx.124-23c.JZ"...########################################################################################################################################################################################################################################################################################################################################################################################################################################################

'Flash:/c1240-k9w8-mx.124-23c.JZ/c1240-k9w8-mx.124-23c.JZ' file, unzipped and installed, point of entry: 0 x 3000

execution of...

Legend restricted rights

Use, duplication, or disclosure by the Government is

subject to such restrictions as set out in paragraph

(c) Commercial - limited computer software

The rights to FAR clause 52.227 - 19 and subparagraph s

(c) (1) (ii) rights to technical and computer data

Clause of DFARS 252.227 - 7013 section software.

Cisco Systems, Inc.

170 West Tasman Drive

San Jose, California 95134-1706

Cisco IOS software, software of C1240 (C1240-K9W8-M), Version 12.4 (23 c) JZ, RELEASE SOFTWARE (fc1)

Technical support: http://www.cisco.com/techsupport

Copyright (c) 1986-2011 by Cisco Systems, Inc.

Updated Thursday, April 6, 11 15:01 by prod_rel_team

Proceed with the initialization of the system

Proceeding to unmask interrupts

Initialization of flashfs...

flashfs [1]: 15 files, 4 folders

flashfs [1]: 0 orphaned files, orphaned directories 0

flashfs [1]: Total number of bytes: 15740928

flashfs [1]: bytes used: 10084864

flashfs [1]: available bytes: 5656064

flashfs [1]: flashfs fsck took 5 seconds.

flashfs [1]: the complete initialization... done Initializing flashfs.

Radio0 present A506 7100 E8000000 A0000000 80000000 3

Radio1 present A506 6700 E8000100 A0040000 80010000 2

This product contains cryptographic features and is under the United States

States and local laws governing the import, export, transfer and

use. Delivery of Cisco cryptographic products does not imply

third party approval to import, export, distribute or use encryption.

Importers, exporters, distributors and users are responsible for

compliance with U.S. laws and local countries. By using this product you

agree to comply with the regulations and laws in force. If you are unable

to satisfy the United States and local laws, return the product.

A summary of U.S. laws governing Cisco cryptographic products to:

http://www.Cisco.com/WWL/export/crypto/tool/stqrg.html

If you need assistance please contact us by mail at

[email protected] / * /.

Cisco AIR-LAP1242AG-A-K9 (PowerPCElvis) Prozesseur (revision A0) 25590K / 7168K bytes of memory.

Card processor ID FTX1135B3ZF

PowerPCElvis CPU at 262 Mhz, revision number 0 x 0950

Last reset of tension

Image LWAPP 7.0.98.218 version

1 interface FastEthernet

2 802.11 radios

32K bytes memory simulated by flash not volatile configuration.

Basic Ethernet MAC address: xxxxxxxxxx

Part number: 73-9925-06

Kit numbered PCA: 800-26579-05

Revision number of PCA: xxxxx

Serial number of PCB: xxxxxxx

Top of page Assembly part number: xxxxxxx

Top of page the Assembly serial number: xxxxxxx

Top of page revision number: A0

Product/model number: AIR-LAP1242AG-A-K9

% Please first set a domain name.

Press RETURN to get started!

* 00:00:06.526 Mar 1: % SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: crypto IOS FIPS self-test passed

* 00:00:08.150 Mar 1: % SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: crypto RADIO FIPS self-test passed on Dot11Radio interface 0

* 00:00:09.747 Mar 1: % SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: crypto RADIO FIPS self-test passed on 1 Dot11Radio interface

* 00:00:09.863 Mar 1: % LWAPP-3-CLIENTEVENTLOG: reading and initialized AP event log (contains 1024 messages)

* 00:00:09.895 Mar 1: State of the voice_diag_test of WLC is false

* 00:00:12.004 Mar 1: % LINK-3-UPDOWN: Interface FastEthernet0, changed State to

* 00:00:12.072 Mar 1: % SYS-5-RESTART: System restarted.

Cisco IOS software, software of C1240 (C1240-K9W8-M), Version 12.4 (23 c) JZ, RELEASE SOFTWARE (fc1)

Technical support: http://www.cisco.com/techsupport

Copyright (c) 1986-2011 by Cisco Systems, Inc.

Updated Thursday, April 6, 11 15:01 by prod_rel_team

* 00:00:12.072 Mar 1: % SNMP-5-start COLD: SNMP agent on host AP001d.4536.86ca knows a cold start

* 00:00:12.154 Mar 1: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

* 00:00:12.161 Mar 1: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset

* 00:00:12.161 Mar 1: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset

* 00:00:12.369 Mar 1: % SSH-5-ACTIVATED: SSH 2.0 has been activated

* 00:00:13.016 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed State to

* 00:00:13.170 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down

* 00:00:13.170 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs

* 00:00:20.493 Mar 1: % ADDRESS_ASSIGN-6-DHCP: Interface FastEthernet0 assigned address DHCP 10.10.11.150, mask 255.255.255.0, hostname AP001d.xxxx.xxxx

* 00:00:30.976 Mar 1: State of the voice_diag_test of WLC is false

* 00:00:31.083 Mar 1: message logging LWAPP to 255.255.255.255.

* 00:00:34.263 Mar 1: % CDP_PD-4-POWER_OK: full power - supply NEGOTIATED online

* 00:00:34.304 Mar 1: % LINK-3-UPDOWN: Interface Dot11Radio1, changed State to

* 00:00:34.342 Mar 1: % LINK-3-UPDOWN: Interface Dot11Radio0, changed State to

* 00:00:35.265 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to

* 00:00:35.265 Mar 1: % SYS-6-LOGGINGHOST_STARTSTOP: logging to host started 255.255.255.255 - initiated CLI

* 00:00:35.304 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to

Translate "CISCO-CAPWAP - CONTROLLER.tester .net '... the domain server (10.10.10.40)

Translate "CISCO-LWAPP - CONTROLLER.tester .net '... the domain server (10.10.10.40)

* 00:00:42.131 Mar 1: % 3-CAPWAP-ERRORLOG: did not get the server DHCP server log settings.

* 00:00:42.135 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CAPWAP-CISCO - CONTROLLER.tester .net

* 00:00:42.139 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CISCO-LWAPP - CONTROLLER.tester .net

* 00:01:32.143 Mar 1: % CAPWAP-5-DHCP_RENEW: could not find WLC by using DHCP IP. Renew DHCP IP.

* 00:01:34.274 Mar 1: % CDP_PD-4-POWER_OK: full power - supply NEGOTIATED online

Not in a bound State.

* 00:01:40.659 Mar 1: % 3-CAPWAP-ERRORLOG: event white 38 & combination of State 2.

* 00:01:40.778 Mar 1: % ADDRESS_ASSIGN-6-DHCP: Interface FastEthernet0 assigned address DHCP 10.10.11.150, mask 255.255.255.0, hostname AP001d.xxxx.xxxx

Translate "CISCO-CAPWAP - CONTROLLER.tester .net '... the domain server (10.10.10.40)

Translate "CISCO-LWAPP - CONTROLLER.tester .net '... the domain server (10.10.10.40)

* 00:01:48.652 Mar 1: % 3-CAPWAP-ERRORLOG: did not get the server DHCP server log settings.

* 00:01:48.655 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CAPWAP-CISCO - CONTROLLER.tester .net

* 00:01:48.657 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CISCO-LWAPP - CONTROLLER.tester .net

* 00:02:28.661 Mar 1: % CAPWAP-5-DHCP_RENEW: could not find WLC by using DHCP IP. Renew DHCP IP.

Not in a bound State.

* 00:02:37.173 Mar 1: % 3-CAPWAP-ERRORLOG: event white 38 & combination of State 2.

* 00:02:37.290 Mar 1: % ADDRESS_ASSIGN-6-DHCP: Interface FastEthernet0 assigned address DHCP 10.10.11.150, mask 255.255.255.0, hostname AP001d.xxx.xxxx

Translate "CISCO-CAPWAP - CONTROLLER.tester .net '... the domain server (10.10.10.40)

Translate "CISCO-LWAPP - CONTROLLER.tester .net '... the domain server (10.10.10.40)

* 00:02:45.164 Mar 1: % 3-CAPWAP-ERRORLOG: did not get the server DHCP server log settings.

* 00:02:45.167 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CAPWAP-CISCO - CONTROLLER.tester .net

* 00:02:45.169 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CISCO-LWAPP - CONTROLLER.tester .net

* 00:03:25.170 Mar 1: % CAPWAP-5-DHCP_RENEW: could not find WLC by using DHCP IP. Renew DHCP IP.

Not in a bound State.

* 00:03:33.681 Mar 1: % 3-CAPWAP-ERRORLOG: event white 38 & combination of State 2.

* 00:03:33.798 Mar 1: % ADDRESS_ASSIGN-6-DHCP: Interface FastEthernet0 assigned address DHCP 10.10.11.150, mask 255.255.255.0, hostname AP001d.xxxx.xxxx

Translate "CISCO-CAPWAP - CONTROLLER.tester .net '... the domain server (10.10.10.40)

Translate "CISCO-LWAPP - CONTROLLER.tester .net '... the domain server (10.10.10.40)

* 00:03:41.673 Mar 1: % 3-CAPWAP-ERRORLOG: did not get the server DHCP server log settings.

* 00:03:41.676 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CAPWAP-CISCO - CONTROLLER.tester .net

* 00:03:41.678 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CISCO-LWAPP - CONTROLLER.tester .net

* 00:04:21.679 Mar 1: % CAPWAP-5-DHCP_RENEW: could not find WLC by using DHCP IP. Renew DHCP IP.

Not in a bound State.

* 00:04:30.191 Mar 1: % 3-CAPWAP-ERRORLOG: event white 38 & combination of State 2.

* 00:04:30.308 Mar 1: % ADDRESS_ASSIGN-6-DHCP: Interface FastEthernet0 assigned address DHCP 10.10.11.150, mask 255.255.255.0, hostname AP001d.xxxx.xxxx

Translate "CISCO-CAPWAP - CONTROLLER.tester .net '... the domain server (10.10.10.40)

Translate "CISCO-LWAPP - CONTROLLER.tester .net '... the domain server (10.10.10.40)

* 00:04:38.181 Mar 1: % 3-CAPWAP-ERRORLOG: did not get the server DHCP server log settings.

* 00:04:38.184 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CAPWAP-CISCO - CONTROLLER.tester .net

* 00:04:38.187 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CISCO-LWAPP - CONTROLLER.tester .net

* 00:05:18.191 Mar 1: % CAPWAP-5-DHCP_RENEW: could not find WLC by using DHCP IP. Renew DHCP IP.

Not in a bound State.

* 00:05:26.703 Mar 1: % 3-CAPWAP-ERRORLOG: event white 38 & combination of State 2.

* 00:05:26.820 Mar 1: % ADDRESS_ASSIGN-6-DHCP: Interface FastEthernet0 assigned address DHCP 10.10.11.150, mask 255.255.255.0, hostname AP001d.xxxx.xxxx

Translate "CISCO-CAPWAP - CONTROLLER.tester .net '... the domain server (10.10.10.40)

Translate "CISCO-LWAPP - CONTROLLER.tester .net '... the domain server (10.10.10.40)

* 00:05:34.694 Mar 1: % 3-CAPWAP-ERRORLOG: did not get the server DHCP server log settings.

* 00:05:34.696 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CAPWAP-CISCO - CONTROLLER.tester .net

* 00:05:34.699 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CISCO-LWAPP-CONTROL

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Thank you!!!

Hi John,.

If your WLC mgt vlan does not enable DHCP, yes you can try to manually configure an IP address like below (IP & Gateway and WLC mgt IP info that you need to change to according to your intellectual property regime). If the keyword CAPWAP does not use LWAPP keyword in the syntax of the command

LWAP #debug capwap console cli

LWAP #capwap ap 10.10.110.5 ip address 255.255.255.0

LWAP #capwap ap ip default gateway - 10.10.110.1

IP LWAP ap controller 10.10.110.10 #capwap

LWAP #debug lwapp console cli

LWAP #lwapp ap 10.10.110.5 ip address 255.255.255.0

LWAP #lwapp ap ip default gateway - 10.10.110.1

IP LWAP ap controller 10.10.110.10 #lwapp

This refer for details

http://mrncciew.com/2013/03/17/AP-registration/

Position the console AP output this time if it does not work

HTH

Rasika

Pls note all useful responses *.

Two WLC 5508 anchor high availability

Hello.

It is possible use 2 WLC 5508 EN HOW to ANCHOR in an active scenario?.

For example, if a WLC down the service, another Dungeon provide service to customers of anchor?

At the moment we have just a WLC 5508 anchor mode. What do I have to configure high availability of the ANCHOR.

Thank you very much!!!

You have redundant WLC as anchor points, but if an anchor fails, the user must reconnect.

There is a feature on the WLC HA, but it is mainly for foreigners redundancy WLC anchor no redundancy. With guest several anchors overseas WLC balance the load between the two. You will not be able to put a primary or backup.

Sent by Cisco Support technique iPhone App

WLC management port is another trunk that vlan native

Hello

I installed my first WLC 5508 with this topology:

WLC connected trought distribution SFP 1 GB port to the port of switch configured as a Trunk port cut 3 Wireless VLAN:

-Management WLC, wireless and wireless voice data Vlan (Vlan native is WLAN Management).

-J' created 2 dynamic interface on WLC on my VLAN Wireless:

10.7.1.0/24: default management Virtual Interface installing WLC +.

10.7.6.0/24: Virtual Interface of voice and

10.7.2.0/24: Wireless Data Interface virtual trought GUI.

DHCP configured on each dynamic interface is the interface vlan L3 subent for SWITCH main technical IP DHCP Pool equal VLAN.

WLC management interface IP address is: 10.7.1.10/24

I create 2 WLAN SSID name with given ID 1, and ID2 voice.

I create and AP group named APGRP1 that contains the AP recorded about WLC and using the two WLAN SSID.

The two AP are connected to the switch acess port configured as native management WLC VLAN access port.

I have to create 3 IP DHCP pool on main switch with the related L3 Interfaces for Inter VLAN routing.

Problem: when I try to connect from mobile data SSID I get IP address of management WLC VLAN a VLAN data no.

the same case of Wireless IP Phone configured with voice SSID.

What I can likely that allows two devices to get the address IP of the correct VLAN?

Thnks

Hi Adil,

T1 > coelio AP on the switch must be configured on a mode of access to the port or trunk mode?

YEARS - the LWAPP / CAPWAP APs connected to the switchport should be an access port not trunk.

Q2 > if the first case, the configuration of the port, on the same VLAN as WLC management VLAN support Vlans other WLANS (voice and data)?

YEARS - Yes it supports, since traffic that involes the WLAN will be inside the tunnel of logic LWAPP/CAPWAP.

Q3 > I will check the interface between WLAN and dynamic Interfaces map and I'll tell you.

YEARS - I will wait for your answer!

Let me know if that answers your question...

Concerning
Surendra
====
Please do not forget to note positions that answered your question and mark as answer or was useful

Connection to a wlc on subnets

I recently bought a 4402 wireless controller to manage our access points. When I put the APs on the same subnet as the subnet ap-Manager, I get the access point you want to connect. When I put on the subnet wireless access point, it does not connect. Does not record again.

I read that I have to layer 3 routing on the 4502 to work. I'm doing now. Do I need to configure anything on my switches to ensure that packets are by (a bit like defining where the DHCP server) or should it just work? Do I need to set up a WLAN ID that corresponds to the ID of the WLAN using the switches? I thought I tried that first and not had much luck. Any ideas on this vague question?

I'm trying to dig into the documentation to see if I can find the answer, but so far I have found nothing.

Sent by Cisco Support technique iPhone App

You will want to ensure that your APs can route where that you install to the WLC management address.

How APs find the controller may occur a few different ways:

(1) A DNS record

(2) layer 2 broadcast (that you've already seen)

(3) IP Route forward

(4) DHCP Option 43

(5) manual to initiate the PA

Most people lead with option 43.

http://www.my80211.com/Cisco-WLC-Labs/2009/7/4/Cisco-DHCP-option-43-configuration-nugget.html

If you see the configuration guide will explain the other process.

WLC 2112 stopped giving ip addresses

My wlc has stopped giving the ip address on a wlan. My guest access

WLAN works well.

In WLC message log shows:

* 12:09:19.105 14 April: DHCP-3-SEND_OFFER_FAIL %: dhcpd.c:276 unable to send DHCP offers. A could not allocate appropriate ip address

the scope of application
* 12:08:48.348 14 April: % DHCP-3-ADDR_NOTIN_POOL: pools.c:158 error: 0.0.0.0 Ip address is not in the pool (192.168.196.10-> 192.168.196.39)
* 12:08:48.348 14 April: DHCP-3-SEND_OFFER_FAIL %: dhcpd.c:276 unable to send DHCP offers. A could not allocate appropriate ip address

the scope of application

I use the wlc to give to two wlan ip addresses.

I have the active proxy DHCP and the dhcp server defined as the address of the WLC management.

I enclose a bedug client log

Any ideas?

Thanks in advance

Richard

Hello

We have a bug known on the version that you use... the internal DHCP pool will break... Here is the bug ID. the latest version 6.0 the CCEL has the fix... Please update the WLC to that or use the outdoor pool to DHCP from the server...

http://Tools.Cisco.com/support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCth68708

Let me know if that answers your question and please do not forget to note the useful messages!

Concerning

Surendra

WLC problem!

Hello, Cisco Support Comunnity

I have a problem that I hope you and you can help me

We have a WLC 4402 in our network, we have 12 AP and we have three SSID that is assignment of IP addresses of three different DHCP pools configured in router base, the situation is that we want one of the SSID is not to assign the IP addresses of the router base, to do this, we have set up a new pool VLAN and DHCP in a layer switch in the other segment 3 When I assign the SSID to the new VIRTUAL local network with the IP address cannot be conmunicate with the VLAN, I mean the SSID that is attributed to the new VLAN cannot speak with the WLC.

Concerning

[email protected] / * /.

Hi Elvin,.

are you able to ping wlc L3 switch? and also please check if this vlan individual is allowed on the trunk of the WLC port or not.

Thank you

SG300 DHCP DNS server secondary Allocation

I'm not sure that this is possible, but is the DHCP server to assign a secondary DNS server.

It seems to be an option to place a single DNS entry in.

I have DHCP configuration to allocate an internet base DNS (DNS Google on 8.8.8.8) so my workstations can access the internet, but I want to allocate a secondary dns for my workstations are aware able to connect to my internal servers through host names.

Is it possible on the SG300-20 for this

Thank you

Paul

Weird, I'm trying to remember what I did today. Here is my order show proving that it worked:

switch706852(config-DHCP) #do sh ip dhcp pool network test

Address name mask rental range.

------------------- --------------------------- ------------- -----------

test 10.10.10.1 - 10.10.10.6 255.255.255.2 1 d: 0 h: 0 m

48

Statistics:

All-range available free prealloue allocated expired declined

----------- ----------- ------ --------------- ----------- ---------- ----------

6 6 6 0 0 0 0

DNS server: 4.2.2.2; 8.8.8.8

Ah ha, history buffer shows no comma, but the space!

switch706852(config-DHCP) # 4.2.2.2 dns server 8.8.8.8

-Please do not forget to rate and Marc answered useful posts.

Problems of Tunneling comments

Hello

I was wondering if someone could help me out here. I followed the guidelines in accordance with the configuration guide estim├⌐ WLC regarding the configuration of the internal controller that is simple enough. Mobility anchor is in place with the controller of the DMZ however I do not know what configuration is required on the controller of DMZ itself regarding the DHCP and the WLAN comments himself. To be honest, the documentation is a bit narrow to say the least.

Any help would be greatly appreciated

See you soon,.

Martin

Martin,

I share your frustrations with the documentation to access as a guest. Of what you have said that you are having problems with the way in which mobility guest access is configured regarding DHCP. I hope this helps.

The first part is well documented. Set up a group of mobility between the remote control and the controller of the DMZ. Make sure it is pointing upwards. Now we'll move DHCP configuration.

(1) on the controller of the DMZ, set up a DHCP pool for invited guests. Make sure that you generate a WLAN and link to the appropriate interface

(2) on the remote control, your 'management' interface, set the DHCP server or the ip address of the management on the controller of the DMZ interface. Very important!

(3) build the WLAN prompt on the remote with the same configuration and link its interface to the management interface of the remote control.

Voila... now, all DHCP requests will be forwarded to the anchoring of the DMZ.

Thing I can help with made me know.

-Mike

http://CS-Mars.blogspot.com

SG500 layer 3 - VLAN can see each other devices Vlan9 <>- Vlan13

Hi all!

I guess I'm missing something simple here:

Basic configuration: two SG500 stacked switches in layer mode 3 who should do the routing. LANCOM WLC with access Internet COOL tied up in the trunk.

As for my understanding, I wouldn't be able to see Vlan13 of Vlan9 devices. But unfortunately, I don't have.

Any help is appreciated. Thank you!!!

config-file-header
switch0908fa
v1.3.7.18 / R750_NIK_1_35_647_358
CLI v1.0
define the system mode router queues-mode 4

SSD of encrypted file indicator
@
SSD-control-start
config of SSD
control of password file unrestricted SSD
no control of the integrity of the file ssd
SSD-control-end cb0a3fdb1f3a1af4e4430033719968c0
!
database of VLAN
VLAN 46, 91-9-99
output
Add a voice vlan Yes-table 0001e3 Siemens_AG_phone___
Add a voice vlan Yes-table 00036 b Cisco_phone___
Add a voice vlan Yes-table 00096e Avaya___
Add a voice vlan Yes-table 000fe2 H3C_Aolynk___
Add a voice vlan Yes-table 0060 b 9 Philips_and_NEC_AG_phone
Add a voice vlan Yes-table 00d01e Pingtel_phone___
VLAN voice Yes-table add Polycom/Veritel_phone___ 00e075
Add a voice vlan Yes-table 00e0bb 3Com_phone___
The dhcp server IP
network IP dhcp pool P_1
address 192.168.0.10 low high 192.168.0.254 255.255.255.0
Infinite rental
94.200.200.200 DNS server
output
network IP dhcp pool P_9
address 192.168.9.10 low high 192.168.9.254 255.255.255.0
Infinite rental
94.200.200.200 DNS server
output
network IP dhcp pool P_13
address 192.168.13.20 low high 192.168.13.254 255.255.255.0
Infinite rental
94.200.200.200 DNS server
output
no host start auto-config
Hello interface range vlan 1
hostname switch0908fa
No complexity of passwords allow
username privilege 15 7af78c911d5b48bea1dc2449d9d89513abeb4be5 encrypted password cisco
name-server IP 192.168.0.5
querying domain IP 18
no service-CPU usage
!
interface vlan 1
the IP 192.168.0.1 255.255.255.0
no ip address dhcp
!
interface vlan 9
name V_9
IP 192.168.9.1 255.255.255.0
!
interface vlan 10
name V_10
!
interface vlan 11
name V_11
!
interface vlan 12
name V_12
!
interface vlan 13
name V_13
192.168.13.1 IP address 255.255.255.0
!
interface vlan 14
name V_14
!
interface vlan 15
name V_15
!
interface vlan 16
name V_16
!
interface vlan 17
name V_17
!
interface vlan 18
name V_18
!
interface vlan 19
name V_19
!
interface vlan 20
name V_20
!
interface vlan 21
name V_21
!
interface vlan 22
name V_22
!
interface vlan 23
name V_23
!
interface vlan 24
name V_24
!
interface vlan 25
name V_25
!
interface vlan 26
name V_26
!
interface vlan 27
name V_27
!
interface vlan 28
name V_28
!
interface vlan 29
name V_29
!
interface vlan 30
name V_30
!
interface vlan 31
name V_31
!
interface vlan 32
name V_32
!
interface vlan 33
name V_33
!
interface vlan 34
name V_34
!
interface vlan 35
name V_35
!
interface vlan 36
name V_36
!
interface vlan 37
name V_37
!
interface vlan 38
name V_38
!
interface vlan 39
name V_39
!
interface vlan 40
name V_40
!
interface vlan 41
name V_41
IP 192.168.41.1 255.255.255.0
!
interface vlan 42
name V_42
!
interface vlan 43
name V_43
!
interface vlan 44
name V_44
!
interface vlan 45
name V_45
!
interface vlan 46
name V_46
!
interface vlan 91
name V_91
!
interface vlan 92
name V_92
!
interface vlan 93
name V_93
!
interface vlan 94
name V_94
!
interface vlan 95
name V_95
!
interface vlan 96
name V_96
!
interface vlan 97
name V_97
!
interface vlan 98
name V_98
!
interface vlan 99
name V_99
!
interface gigabitethernet1/1/1
switchport mode access
!
interface gigabitethernet1/1/2
switchport mode access
!
interface gigabitethernet1/1/3
switchport mode access
!
interface gigabitethernet1/1/4
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/5
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/6
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/7
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/8
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/9
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/10
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/11
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/12
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/13
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/14
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/15
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/16
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/17
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/18
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/19
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/20
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/21
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/22
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/23
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/24
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/25
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/26
switchport mode access
switchport access vlan 9
!
interface/gigabitethernet1/1/27
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/28
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/29
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/30
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/31
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/32
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/33
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/34
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/35
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/36
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/37
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/38
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/39
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/40
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/41
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/42
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/43
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/44
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/45
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/46
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/47
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/48
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/49
switchport mode access
!
interface gigabitethernet1/1/50
switchport mode access
!
interface gigabitethernet1/1/51
switchport mode access
switchport access vlan 9
!
interface gigabitethernet1/1/52
switchport mode access
switchport access vlan 9
!
interface gigabitethernet2/1/1
switchport mode access
!
interface gigabitethernet2/1/2
switchport mode access
switchport access vlan 13
!
interface gigabitethernet2/1/3
switchport mode access
switchport access vlan 13
!
interface gigabitethernet2/1/4
switchport mode access
switchport access vlan 13
!
interface gigabitethernet2/1/5
switchport mode access
switchport access vlan 13
!
interface gigabitethernet2/1/6
switchport mode access
switchport access vlan 13
!
interface gigabitethernet2/1/7
switchport mode access
switchport access vlan 13
!
interface gigabitethernet2/1/8
switchport mode access
!
interface gigabitethernet2/1/9
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/10
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/11
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/12
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/13
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/14
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/15
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/16
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/17
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/18
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/19
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/20
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/21
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/22
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/23
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/24
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/25
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/26
switchport mode access
switchport access vlan 41
!
interface/gigabitethernet2/1/27
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/28
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/29
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/30
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/31
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/32
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/33
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/34
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/35
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/36
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/37
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/38
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/39
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/40
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/41
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/42
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/43
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/44
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/45
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/46
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/47
switchport mode access
switchport access vlan 41
!
interface gigabitethernet2/1/48
switchport mode access
!
interface gigabitethernet2/1/51
switchport mode access
!
interface gigabitethernet2/1/52
switchport mode access
!
output
IP route 0.0.0.0/0 192.168.0.5 metrics 2
encryption ip key-pair of keys rsa ssh-client
.

The VLAN intercommunicates is because you have an IP address on the interface VLAN that will dynamically build a route on the switch.

As noted below, if you want to VLAN 9 to not see 13 or vice versa and ACL will be needed on the interface VLAN.

REAP: quick question

Hi team

On the WLC 7.0, page 15-2, configuration guide under the REAP H authentication process it is mentioned option DHCP 43 can be used to discover APs.

However, page 15-4 H - HARVEST guidelines, it is mentioned that you need a local DHCP of IPss of APs.

As this is a bit confusing, can someone confirm that we could use option 43 with a DHCP server located at Headquarters via links WAN of IPs for the APs Office remotely in a configuration REAP: pls?

Thank you

Andrée

Hi Jean Miche,.

Yes I agree with you... It's confusing... Let me help you...

There are many ways to tell the AP to enter the IP address... the two methods you mentioned is correct. It's... option 43 works for HREAP APs and the server is the central site... we prefer the local DHCP pool... but local pool is another option.

The method above should boot the PA... which... is the need to ship H-Reap twice: once for a central site for commissioning and a second time at the remote site for installation...

To overcome this static addressing started after version 4.0 of the WLC software... that will overcome the provision to the AP once on the central and others on the remote...

But all 3 methods are valid and can be used...

Concerning

Surendra

Multiple SSIDs\VLANs, DHCP and wireless

Hello

Check out my last post in a different discussion. I reported it as answered, my first question has been answered, but I am still confused of DHCP is working. I work with a config along the lines of:

I work with a WLC 5508.

He'll be there 2 separate WLAN on their own VIRTUAL local area network.

The WLC connects to the Southwest over a trunk link, which seems logical.

However, my question is in connection with the TOUR to the switch... should be a trunk as well? (one answer, needs to be an access port)

So my next question is:

How clients in their ssid / VLAN respective will receive an IP via DHCP to it to the switch port that connects the TOWER on a VLAN?

Here are the basics of my config.

Hatch 192.168.1.55 Mgmt iface and 56

VLAN 9 is going to be for tours only (network 192.168.9.0/24)

VLAN 6 is for example personal WLAN SSID is CORP-WLAN (network 192.168.6.0/24)

8 VLAN for the guests, example SSID is GUEST-WLAN (network 192.168.8.0/24)

I have DHCP pools configured for each network, and 43 is set for the APs over the nearest SW to the WLC (the SW there rising directly)

I have a dynamic port configured on the WLC, and two wireless LANs are associated with the port and have received their VLAN respective.

Allows to say that I am an AP, I have tension, and given that my SW port is VLAN 9, my broadcasts DHCP is heard by the SW, and he assigned me an IP of the 192.168.9.0 pool. It's all great. Now, I have a client that tries to associate to my Guest-WLAN SSID, and is now applying an IP address... How can I assign an IP address from the correct pool?

Maybe I'm too complicate it a bit...?

In addition, lets say I have 3 pools DHCP configured network 192.168.6.0 24, 8.0, 9.0 on my way... How will the switch knows what pool to match with and VLAN individual? I should know this, but I feel forgetful... SW needs to have an interface vlan is configured with an IP address that falls within a configured pool?

Give me a sense, that is a good question?

Bill

There are several ways to solve your problem, it depends on your expectations. I guess that you will travel with the value default Local AP Mode.

By default, it is important to note that customer traffic to a point of integrated access to the WLC, and then it comes out of the WLC on the VIRTUAL LAN that you specified. This is why the AP can be a switchport Mode access and could reside in a vlan / entirely different subnet of your wireless users.

So assuming that it is the model that you want to track, a high level overview of the configuration would be as follows:

Suppose you want client WLAN 1 VLAN 11 and WLAN 2 VLAN 12. Assuming that the WLC management interface is VLAN 1.

You simply need to create a dynamic Interface in vlan 11 and vlan 12 with the appropriate addresses. Then you would set up WLAN 1 out Interface VLAN 11 and 2 WLAN as output interface 12 VLANS.

Now when a customer joins 1 WLAN, its traffic will be the tunnel from AP to the WLC via CAPWAP and going to the controller on VLAN 11. The client will now effectively be in VLAN 11.

Who is?

Help to set up a WLC2100

Hello!

I'm new to a wirelless world and my manager give me work to set up a wlc2100 and join an air lap1242g to the controller, so the problem is that I have configured the wlc connectivity and one have access to the browser web wlc... Next I configure a dhcp pool in my dhcp server and the lap1242 to connect to the network find the wlc but cannot join the wlc get ip.

Please can someone help me?

NEWSPAPERS

LAP1242:****************************************************************************

* 12:20:35.839 Feb 23: level 0 adjusted on the slot 1 to 140 power chan

* 12:20:48.841 Feb 23: % 3-CAPWAP-ERRORLOG: go join a capwap controller

* 12:20:49.000 Feb 23: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.10.50.51 peer_port: 5246

* 12:20:50.688 Feb 23: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 10.10.50.51 peer_port: 5246

* 12:20:50.690 Feb 23: % CAPWAP-5-SENDJOIN: send request to join 10.10.50.51

* 12:20:50.690 Feb 23: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE

* 12:20:50.773 Feb 23: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

* 12:20:50.775 Feb 23: % DTLS-5-ALERT: WARNING received: close notify alert from 10.10.50.51

* 12:20:50.775 Feb 23: % DTLS-5-PEER_DISCONNECT: Peer 10.10.50.51 has closed the connection.

* 12:20:50.775 Feb 23: % DTLS-5-SEND_ALERT: send WARNING: close notify alert at 10.10.50.51

* 12:20:50.820 Feb 23: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

* 12:20:50.820 Feb 23: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

* 12:20:50.830 Feb 23: level 0 adjusted on slot 0 for 13 power chan

* 12:20:50.830 Feb 23: level 0 adjusted on the slot 1 to 140 power chan

* 12:21:03.831 Feb 23: % 3-CAPWAP-ERRORLOG: go join a capwap controller

* 12:21:03.000 Feb 23: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.10.50.51 peer_port: 5246

* 12:21:04.692 Feb 23: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 10.10.50.51 peer_port: 5246

* 12:21:04.693 Feb 23: % CAPWAP-5-SENDJOIN: send request to join 10.10.50.51

* 12:21:04.693 Feb 23: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE

* 12:21:04.777 Feb 23: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

* 12:21:04.779 Feb 23: % DTLS-5-ALERT: WARNING received: close notify alert from 10.10.50.51

* 12:21:04.779 Feb 23: % DTLS-5-PEER_DISCONNECT: Peer 10.10.50.51 has closed the connection.

* 12:21:04.780 Feb 23: % DTLS-5-SEND_ALERT: send WARNING: close notify alert at 10.10.50.51

* 12:21:04.823 Feb 23: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

* 12:21:04.824 Feb 23: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

* 12:21:04.833 Feb 23: level 0 adjusted on slot 0 for 13 power chan

* 12:21:04.833 Feb 23: level 0 adjusted on the slot 1 to 140 power chan

* 12:21:17.835 Feb 23: % 3-CAPWAP-ERRORLOG: go join a capwap controller

* 12:21:18.000 Feb 23: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.10.50.51 peer_port: 5246

===========================================================================================

See the (cisco Controller) > logging

Logging to the buffer:

-Buffer system message logging:

-Logging filter level... Errors

-Number of logged system messages... 137805

-Number of messages fell system... 42720

-Saving debugging messages for stamp... People with disabilities

-Number of connected debug messages... 0

-Number of debugging messages dropped... 0

By connecting to the console:

-Registration system to the console messages:

-Logging filter level... Errors

-Number of logged system messages... 0

-Number of messages fell system... 180525

-Saving debugging messages to console... Activated

-Number of connected debug messages... 0

-Number of debugging messages dropped... 0

Logging into syslog:

-Installation of Syslog... local0

-Logging system in syslog messages:

-Logging filter level... Errors

-Number of logged system messages... 137805

-Other - or ITU (q)

-Number of messages fell system... 42720

-Saving debugging in syslog messages... People with disabilities

-Number of connected debug messages... 0

-Number of debugging messages dropped... 0

-Number of remote syslog hosts... 0

- Host 0....................................... Not configured

- Host 1....................................... Not configured

- Host 2....................................... Not configured

Logging tracing... Activated

-Record tracing level... Errors

Saving process information... Activated

Save the file to the source of information... Activated

Timestamp of messages...

-Timestamp of the system messages... Activated

-Timestamp format... Date and time

-Timestamp of the debug messages... Activated

-Timestamp format... Date and time

Logging buffer (137805 connected, 42720 abandoned)

* 13:22:00.769 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

* 13:22:00.767 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

Previous message occurred 3 times.

-Other - or ITU (q)

* 13:22:00.767 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

* 13:22:00.686 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

* 13:21:45.319 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

* 13:21:45.318 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

* 13:21:45.318 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

Previous message has happened 2 times.

* 13:21:45.317 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

* 13:21:45.236 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

* 13:21:30.492 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

* 13:21:30.490 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

Previous message occurred 3 times.

* 13:21:30.490 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

* 13:21:30.409 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

* 13:21:15.669 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

* 13:21:15.668 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

Previous message occurred 3 times.

* 13:21:15.668 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

* 13:21:15.586 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

* 13:21:00.838 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

* 13:21:00.837 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

Previous message occurred 3 times.

* 13:21:00.836 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

* 13:21:00.756 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

-Other - or ITU (q)

* 13:20:46.012 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

* 13:20:46.010 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

Previous message occurred 3 times.

* 13:20:46.010 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

* 13:20:45.928 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

* 13:20:31.175 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

* 13:20:31.173 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

Previous message occurred 3 times.

* 13:20:31.173 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

* 13:20:31.092 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

* 13:20:16.346 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

* 13:20:16.345 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

Previous message occurred 3 times.

* 13:20:16.344 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

* 13:20:16.262 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

* 13:20:01.519 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

* 13:20:01.518 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

Previous message occurred 3 times.

* 13:20:01.517 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

* 13:20:00.811 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

* 13:19:46.063 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

* 13:19:46.062 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

Previous message occurred 3 times.

-Other - or ITU (q)

* 13:19:46.061 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

* 13:19:45.979 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

* 13:19:31.236 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

* 13:19:31.235 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

Previous message occurred 3 times.

* 13:19:31.234 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

* 13:19:31.154 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

* 13:19:16.407 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

* 13:19:16.406 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

Previous message has happened 2 times.

* 13:19:16.406 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

* 13:19:16.405 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

* 13:19:16.324 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

* 13:19:01.582 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

* 13:19:01.580 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

Previous message occurred 3 times.

* 13:19:01.580 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

* 13:19:01.499 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

* 13:18:46.748 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

* 13:18:46.746 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

Previous message occurred 3 times.

* 13:18:46.746 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

* 13:18:46.664 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

-Other - or ITU (q)

* 13:18:31.923 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

* 13:18:31.922 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

* 13:18:31.922 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

Previous message has happened 2 times.

* 13:18:31.921 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

* 13:18:31.841 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

* 13:18:17.087 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

* 13:18:17.086 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

Previous message occurred 3 times.

* 13:18:17.085 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

* 13:18:16.379 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

* 13:18:01.636 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

* 13:18:01.634 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

Previous message occurred 3 times.

* 13:18:01.634 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

* 13:18:01.554 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

* 13:17:46.814 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

* 13:17:46.813 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

* 13:17:46.813 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

Previous message has happened 2 times.

* 13:17:46.812 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

* 13:17:46.731 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

* 13:17:31.989 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

-Other - or ITU (q)

* 13:17:31.987 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

Previous message occurred 3 times.

* 13:17:31.987 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

* 13:17:31.906 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

* 13:17:17.151 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

* 13:17:17.149 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

Previous message occurred 3 times.

* 13:17:17.149 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

* 13:17:17.067 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

* 13:17:02.320 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

* 13:17:02.319 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

Previous message occurred 3 times.

* 13:17:02.319 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

* 13:17:02.238 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

* 13:16:47.495 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

* 13:16:47.493 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

Previous message occurred 3 times.

* 13:16:47.493 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

* 13:16:47.411 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

* 13:16:32.664 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

* 13:16:32.662 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

Try this... go wireless-> country-> select the country for your AP and reboot... see if it works...

DHCP wireless

I have just taken the reins of a new wireless solution. Currently, they have only a WLAN and implement the second for customers only, so they have access to the internet and no device internal.

The controller is an AIR-WLC52 4.2.61.8 running.

All DHCP info points to a router on the site, but when I check the DHCP of the router links, they are not the DHCP pool that the WLC is distributing...

The config on the WLC:

192.168.144.250 ap-handler interface addresses 255.255.255.0 192.168.144.254

interface of management to address 192.168.144.249 255.255.255.0 192.168.144.254

address of the virtual interface 1.1.1.1

AP-handler interface dhcp 192.168.144.254 elementary school

management of dhcp primary interface 192.168.144.254

WLAN create 1 ReduserReduser

WLAN create 2 RedGuest RedGuest

Global custom web WLAN turn 2

WLAN qos 1 Platinum

Disable session-timeout 1 WLAN

Disable session-timeout 2 WLAN

WLAN wmm let 1

WLAN wmm let 2

WiFi wpa security disable 1

WiFi wpa security disable 2

ACCT Serveur_RADIUS WLAN disable 1

ACCT Serveur_RADIUS WLAN disable 2

WiFi security wep key-static enable 1

WiFi security wep key-static turn 2

-Other - or ITU (q)
static-key wep security WLAN 1 shared key authentication

wep authentication static-key WLAN security shared key 2

WiFi security static wep - the encryption key 40 1

WiFi security static wep - the encryption key 40 2

turn off the WiFi security wpa 802 akm. 1 x 1

WiFi wpa psk akm security enable 1

WLAN dhcp_server 2 required 192.168.144.254 required

The setup of the router:

interface GigabitEthernet0/0
Description * off management *.
IP 194.105.164.249 255.255.255.248
IP access-group FIREWALL_IN in
NAT outside IP
IP virtual-reassembly
automatic duplex
automatic speed
card crypto IPSec_vpn
!
interface GigabitEthernet0/1
Description * physical connection to 3560-SW1 *.
no ip address
automatic duplex
automatic speed
!
interface GigabitEthernet0/1.2
Description * DATA *.
encapsulation dot1Q 2 native
IP 192.168.144.254 255.255.255.0
IP nat inside
IP virtual-reassembly
!
interface GigabitEthernet0/1.100
Description * VOICE *.
encapsulation dot1Q 100
IP 192.168.244.254 255.255.255.0
IP nat inside
IP virtual-reassembly
H323-gateway voip bind port 192.168.244.254

IP VOICE dhcp pool
network 192.168.244.0 255.255.255.0
router by default - 192.168.244.254
option 150 ip 192.168.244.254
!
IP dhcp pool B 88, 6
the host 192.168.144.3 255.255.255.0
0100.1ef7.2788.b6 client identifier
router by default - 192.168.144.254
option 150 ip 192.168.244.254

!

dhcp WLAN IP pool

network 192.168.250.0 255.255.255.0

router by default - 192.168.144.249

!

The connections on the router only show links for equipmen 192.168.244 voice and one for the host 192.168.144.3:

IP address customer_id / expiration Type of rental
Hardware address.
Username
192.168.144.3 infinite manual 0100.1ef7.2788.b6
192.168.244.1 0100.1ef7.278f.0c May 13, 2011 04:27 auto
192.168.244.2 0100.1ebe.921c.f6 May 13, 2011 03:31 automatic
192.168.244.3 0100.1ef7.2788.bd May 13, 2011 03:31 automatic
192.168.244.4 0100.1ef7.278f.80 May 13, 2011 03:31 automatic
192.168.244.5 0100.1ebe.921e.19 May 13, 2011 03:41 automatic
192.168.244.6 0100.1ebe.921f.b0 May 13, 2011 03:31 automatic
192.168.244.7 0100.1ef7.2788.b6 May 13, 2011 03:31 automatic
192.168.244.8 0100.1ef7.278f.54 may 13, 2011 03:32 automatic
192.168.244.9 0100.1ebe.921d.e6 May 13, 2011 11:02 auto

There are an average of 50 clients who use wireless right now for the 192.168.144.x address. So I guess it will be on a different server on the site?

How is the controller knows how to get to this unknown DHCP server?

How can I get my new WLAN comments to point correctly to the router to 192.168.144.254?

When you run a debugging dhcp, I see DHCP messages do not:

14:08:24.589 12 may: DHCPD: no subnet configured for 192.168.144.63.
14:08:24.589 12 may: DHCPD: see if there is a specified internal pool class:
14:08:24.589 12 may: DHCPD: htype 1 CHADRR 40a6.d9c7.437a
14:08:24.593 12 may: DHCPD: id remote 020a0000c0a890fe01000002
14:08:24.593 12 may: DHCPD: id circuit 00000000
14:08:24.593 12 may: DHCPD: there is no pool for 192.168.144.254.
14:08:26.633 12 may: DHCPD: see if there is a specified internal pool class:
14:08:26.633 12 may: DHCPD: htype 1 CHADRR 0017.427a.c75f
14:08:26.637 12 may: DHCPD: id remote 020a0000c0a890fe01000002
14:08:26.637 12 may: DHCPD: id circuit 00000000
14:08:26.637 12 may: DHCPD: there is no pool for 192.168.144.254.
14:08:36.529 12 may: DHCPD: no subnet configured for 192.168.144.63.
14:08:36.529 12 may: DHCPD: see if there is a specified internal pool class:
14:08:36.529 12 may: DHCPD: htype 1 CHADRR 40a6.d9c7.437a
14:08:36.529 12 may: DHCPD: id remote 020a0000c0a890fe01000002
14:08:36.529 12 may: DHCPD: id circuit 00000000
14:08:36.529 12 may: DHCPD: there is no pool for 192.168.144.254

Thought maybe better to assign pools on the WLC herself, she can't see how to do this. I can't on the version of the software that I use?

Any help would be greatly appreciated

.

lol Option 43 is for Access Points know ip address WLC in case they don't sit in the WLC subnet. Customers don't care about dhcp options.

[wlc] secondary wlc in a 1:1, Ip dhcp pool redundancy

Similar Questions

Maybe you are looking for