Addr DHCP. Disposal - WLC required

Similar Questions

• Can built-in DHCP of WLC provide IP addresses for the wired client?

  Hello

  We have a WLC running on 7.0.98.0. It provides IP addresses for users without comment thread. Now, we would like to put a couple of wired posts for customers who do not bring mobile no. I wonder if I put these workstations on the same vlan without comment thread, they can always get IPs of the WLC. If this isn't the case, I put the static IP on these workstations.

  Thanks in advance.

  Robert

  Rob:
  The answer is simply "no". WLC cannot provide clients wired on the same VLAN wireless whose IP address if DHCP is configured on WLC.

  Fbarboza above metnioned is a 'very' special configuraiton on wireless LANs where the WLC is configured to support some wireline customers and he needs to have two WLCs (the show is called Wired comments). This particular case does not apply to your situation.

  With your situation, my answer above apply.

  Note 
  A internal DHCP server pool will only serve the wireless clients of that controller, not clients of other controllers. Also, internal DHCP server can only serve wireless clients and not wired clients.
  

  Reference: http://www.cisco.com/en/US/docs/wireless/controller/7.0/configuration/guide/c70wlan.html

  HTH

  Amjad

• External DHCP and WLC 2106

  Hello

  I built a WLC 2106 and 5 LIghweight AP 1121 G-based wireless network. Each AP have multiple ssid in VLANS separated.

  I managed to combine 5 AP to the controller and I have it configured with multiple SSID in different VLANS (each WLAN is associated with the virtual interfaces in the appropriate VLAN).

  The problem is that a wireless client cannot get its IP address from the DHCP externel which is in the same VLAN of the WLAN. And when configured with a static IP address, it works perfectly.

  Can you help please and thank you very much.

  Hi Nizar,

  The controller intercepts all broadcast traffic, so you must configure your DHCP server in your controller to allow your clients to receive DHCP.

  Using the graphical interface, go to the controller-> Interfaces. Click the interface that you use for your SSID. Enter your server DHCP here.

  I would like to know if your problem persists and we can find out what else could be wrong.

• Virtual WLC, customers of fall.

  Hello.

  I have a few clients who obtain a pa ignored AP. I used the debug customer's order, can anyone tell what to change on the WLC to make the erros stop.

  The vWLC is running the most recent version, and the AP is 1602i.

  * apfMsConnTask_6: 16:01:16.954 Oct 07: 68:b5:99:45:44:8e suppRates statusCode is 0 and gotSuppRatesElement is 1

  * apfMsConnTask_6: 16:01:16.954 Oct 07: 68:b5:99:45:44:8e STA - rates (12): 130 132 139 150 12 18 24 36 48 72 96 108 0 0 0 0

  * apfMsConnTask_6: 16:01:16.954 Oct 07: 68:b5:99:45:44:8e extSuppRates statusCode is 0 and gotExtSuppRatesElement is 1

  * apfMsConnTask_6: 16:01:16.954 Oct 07: 68:b5:99:45:44:8e treatment WPA IE type 221, length 22 for mobile 68:b5:99:45:44:8e

  * apfMsConnTask_6: 16:01:16.954 Oct 07: policy of STARTING (0) initialization 68:b5:99:45:44:8e 0.0.0.0

  * apfMsConnTask_6: 16:01:16.954 Oct 07: 68:b5:99:45:44:8e 0.0.0.0 START (0) change the State of the last START (0) AUTHCHECK (2)

  * apfMsConnTask_6: 16:01:16.954 Oct 07: 68:b5:99:45:44:8e 0.0.0.0 AUTHCHECK (2) change the State of 8021X_REQD (3) last State AUTHCHECK (2)

  * apfMsConnTask_6: 16:01:16.954 Oct 07: 68:b5:99:45:44:8e 0.0.0.0 DHCP 8021X_REQD (3) required on AP 68:86:a7:ca:bd:40 5 tasteless 5To apVapId this client

  * apfMsConnTask_6: 16:01:16.954 Oct 07: 68:b5:99:45:44:8e not use WMM compliance code qosCap 00

  * apfMsConnTask_6: 16:01:16.954 Oct 07: 68:b5:99:45:44:8e 0.0.0.0 8021X_REQD (3) mobile devices rule LWAPP AP tasteless 68:86:a7:ca:bd:40 5 apVapId 5 flex-acl-name:

  * apfMsConnTask_6: 16:01:16.954 Oct 07: 68:b5:99:45:44:8e apfMsAssoStateInc

  * apfMsConnTask_6: 16:01:16.954 Oct 07: 68:b5:99:45:44:8e apfPemAddUser2 (apf_policy.c:276) state change for mobile 68:b5:99:45:44:8e on Idle to Associated 68:86:a7:ca:bd:40 AP

  * apfMsConnTask_6: 16:01:16.954 Oct 07: 68:b5:99:45:44:8e apfPemAddUser2:session forstation 68:b5:99:45:44:8e - all Session timeout 0, apfMsTimeOut ' 0' and sessionTimerRunning flag is 0

  * apfMsConnTask_6: 16:01:16.954 Oct 07: 68:b5:99:45:44:8e stop deletion of Station Mobile: (callerId: 48)

  * apfMsConnTask_6: 16:01:16.954 Oct 07: 68:b5:99:45:44:8e Func: apfPemAddUser2, Ms Timeout = 0, Session Timeout = 0

  * apfMsConnTask_6: 16:01:16.954 Oct 07: 68:b5:99:45:44:8e send Assoc response to station 68:86:a7:ca:bd:44 BSSID (State 0) location ApVapId 5 0

  * apfMsConnTask_6: 16:01:16.954 Oct 07: 68:b5:99:45:44:8e apfProcessAssocReq (apf_80211.c:7399) State of change for mobile 68:b5:99:45:44:8e on AP 68:86:a7:ca:bd:40 of associated partners

  * apfMsConnTask_6: 16:01:16.961 Oct 07: 68:b5:99:45:44:8e update AID to RAISE the Client AP 68:86:a7:ca:bd:40 - AID of ===> 3

  * dot1xMsgTask: 16:01:16.963 Oct 07: 68:b5:99:45:44:8e creating a Cache PMKID PKC entry for station 68:b5:99:45:44:8e (ARS 0)

  * dot1xMsgTask: 16:01:16.963 Oct 07: 68:b5:99:45:44:8e index cache of active adjustment 8---> 8 key

  * dot1xMsgTask: 16:01:16.963 Oct 07: 68:b5:99:45:44:8e index cache of active adjustment 8---> 0 key

  * dot1xMsgTask: 16:01:16.963 Oct 07: 68:b5:99:45:44:8e Initiating WPA PSK for mobile 68:b5:99:45:44:8e

  * dot1xMsgTask: 16:01:16.963 Oct 07: 68:b5:99:45:44:8e dot1x - mobile 68:b5:99:45:44:8e Force penetrating Auth State

  * dot1xMsgTask: 16:01:16.963 Oct 07: 68:b5:99:45:44:8e exchange of departure for 68:b5:99:45:44:8e mobile key, data packages will be removed

  * dot1xMsgTask: 16:01:16.963 Oct 07: 68:b5:99:45:44:8e transmission of EAPOL-Key Message for mobile 68:b5:99:45:44:8e

  INITPMK (message 1) State, counter replay 00.00.00.00.00.00.00.00

  * Dot1x_NW_MsgTask_6: 16:01:16.972 Oct 07: 68:b5:99:45:44:8e received EAPOL-Key of mobile 68:b5:99:45:44:8e

  * Dot1x_NW_MsgTask_6: 16:01:16.972 Oct 07: 68:b5:99:45:44:8e key EAPOL received in State PTK_START (message 2) of 68:b5:99:45:44:8e mobile

  * Dot1x_NW_MsgTask_6: 16:01:16.972 Oct 07: 68:b5:99:45:44:8e for mobile 68:b5:99:45:44:8e retransmission timer stop

  * Dot1x_NW_MsgTask_6: 16:01:16.972 Oct 07: 68:b5:99:45:44:8e transmission of EAPOL-Key Message for mobile 68:b5:99:45:44:8e

  PTKINITNEGOTIATING (message 3) State, counter replay 00.00.00.00.00.00.00.01

  * Dot1x_NW_MsgTask_6: 16:01:16.981 Oct 07: 68:b5:99:45:44:8e received EAPOL-Key of mobile 68:b5:99:45:44:8e

  * Dot1x_NW_MsgTask_6: 16:01:16.981 Oct 07: 68:b5:99:45:44:8e key EAPOL received in State PTKINITNEGOTIATING (message 4) of mobile 68:b5:99:45:44:8e

  * Dot1x_NW_MsgTask_6: 16:01:16.981 Oct 07: 68:b5:99:45:44:8e for mobile 68:b5:99:45:44:8e retransmission timer stop

  * Dot1x_NW_MsgTask_6: 16:01:16.981 Oct 07: 68:b5:99:45:44:8e apfMs1xStateInc

  * Dot1x_NW_MsgTask_6: 16:01:16.981 Oct 07: 68:b5:99:45:44:8e 0.0.0.0 8021X_REQD (3) change the State of L2AUTHCOMPLETE (4) the last State 8021X_REQD (3)

  * Dot1x_NW_MsgTask_6: 16:01:16.981 Oct 07: 68:b5:99:45:44:8e 0.0.0.0 L2AUTHCOMPLETE DHCP (4) required on AP 68:86:a7:ca:bd:40 5 tasteless 5To apVapId this client

  * Dot1x_NW_MsgTask_6: 16:01:16.981 Oct 07: 68:b5:99:45:44:8e not use WMM compliance code qosCap 00

  * Dot1x_NW_MsgTask_6: 16:01:16.981 Oct 07: 68:b5:99:45:44:8e 0.0.0.0 L2AUTHCOMPLETE (4) mobile devices rule LWAPP AP tasteless 68:86:a7:ca:bd:40 5 apVapId 5 flex-acl-name:

  * Dot1x_NW_MsgTask_6: 16:01:16.981 Oct 07: 68:b5:99:45:44:8e 0.0.0.0 L2AUTHCOMPLETE (4) change the State of the last State DHCP_REQD (7) L2AUTHCOMPLETE (4)

  * Dot1x_NW_MsgTask_6: 16:01:16.981 Oct 07: rule of TMP adding 5952, 68:b5:99:45:44:8e 0.0.0.0 DHCP_REQD (7) pemAdvanceState2

  * Dot1x_NW_MsgTask_6: 16:01:16.982 Oct 07: rule DHCP_REQD (7) add Fast Path 68:b5:99:45:44:8e 0.0.0.0

  type = Airespace AP - IP address learn

  about AP 68:86:a7:ca:bd:40, location 0, interface = 1, QOS = 0

  ACL ID = 255, VPI IPv4

  * Dot1x_NW_MsgTask_6: 16:01:16.982 Oct 07: rule DHCP_REQD (7) Fast Path 68:b5:99:45:44:8e 0.0.0.0 (more...) 802.1 P = 0, DSCP = 0, = 64206 TokenID Vlan bridging Local = 1, bypass Local intf id = 6

  * Dot1x_NW_MsgTask_6: 16:01:16.982 Oct 07: 68:b5:99:45:44:8e 0.0.0.0 DHCP_REQD (7) successfully mounted a mobile rule (255 ID ACL IPv4, IPv6 ACL ID 255)

  * Dot1x_NW_MsgTask_6: 16:01:16.982 Oct 07: 68:b5:99:45:44:8e Key exchange done, mobile 68:b5:99:45:44:8e data packets to be sent shortly

  * Dot1x_NW_MsgTask_6: 16:01:16.982 Oct 07: 68:b5:99:45:44:8e transmission of EAPOL-Key Message for mobile 68:b5:99:45:44:8e

  State PTKINITDONE (message 5 - group), read the meter 00.00.00.00.00.00.00.02

  * apfReceiveTask: 16:01:16.982 Oct 07: 68:b5:99:45:44:8e 0.0.0.0 DHCP_REQD State (7) set a day of mobility-incomplete for complete mobility, mobility role = Local, client state = APF_MS_STATE_ASSOCIATED

  * apfReceiveTask: 16:01:16.982 Oct 07: rule of TMP adding 5576, 68:b5:99:45:44:8e 0.0.0.0 DHCP_REQD (7) pemAdvanceState2

  * apfReceiveTask: 16:01:16.982 Oct 07: rule DHCP_REQD (7) replacing Fast Path 68:b5:99:45:44:8e 0.0.0.0

  type = Airespace AP - IP address learn

  about AP 68:86:a7:ca:bd:40, location 0, interface = 1, QOS = 0

  IPv4 ACL ID = 255,

  * apfReceiveTask: 16:01:16.982 Oct 07: rule DHCP_REQD (7) Fast Path 68:b5:99:45:44:8e 0.0.0.0 (more...) 802.1 P = 0, DSCP = 0, = 64206 TokenID Vlan bridging Local = 1, bypass Local intf id = 6

  * apfReceiveTask: 16:01:16.982 Oct 07: 68:b5:99:45:44:8e 0.0.0.0 DHCP_REQD (7) successfully mounted a mobile rule (255 ID ACL IPv4, IPv6 ACL ID 255)

  * pemReceiveTask: 16:01:16.982 Oct 07: added entry NPU 68:b5:99:45:44:8e 9, dtlFlags 0x0 type 0.0.0.0

  * pemReceiveTask: 16:01:16.982 Oct 07: added entry NPU 68:b5:99:45:44:8e 9, dtlFlags 0x0 type 0.0.0.0

  * spamApTask1: 16:01:16.990 Oct 07: 68:b5:99:45:44:8e sent EAPOL M5 key for mobile 68:b5:99:45:44:8e

  * Dot1x_NW_MsgTask_6: 16:01:17.001 Oct 07: 68:b5:99:45:44:8e received EAPOL-Key of mobile 68:b5:99:45:44:8e

  * Dot1x_NW_MsgTask_6: 16:01:17.001 Oct 07: 68:b5:99:45:44:8e key EAPOL received in the State REKEYNEGOTIATING (message 6) of 68:b5:99:45:44:8e mobile

  * Dot1x_NW_MsgTask_6: 16:01:17.001 Oct 07: 68:b5:99:45:44:8e for mobile 68:b5:99:45:44:8e retransmission timer stop

  * DHCP special socket: 16:01:28.373 Oct 07: 68:b5:99:45:44:8e DHCP received op BOOTREPLY (2) (len 333, vlan 0, port 1, encap 0xec03)

  * DHCP special socket: 16:01:28.373 Oct 07: 68:b5:99:45:44:8e DHCP server OFFER (10.21.1.254, yiaddr 10.21.1.96 server) configuration

  * DHCP special socket: 16:01:28.376 Oct 07: 68:b5:99:45:44:8e DHCP received op BOOTREPLY (2) (len 333, vlan 0, port 1, encap 0xec03)

  * DHCP special socket: Oct 07 16:01:28.376: 68:b5:99:45:44:8e apfMsRunStateInc

  * DHCP special socket: Oct 07 16:01:28.376: 68:b5:99:45:44:8e 10.21.1.96 DHCP_REQD (7) change the State final State of RUN (20), DHCP_REQD (7)

  * DHCP special socket: 16:01:28.376 Oct 07: 68:b5:99:45:44:8e address assignment 10.21.1.96 on mobile

  * DHCP special socket: 16:01:28.376 Oct 07: customer success 68:b5:99:45:44:8e DHCP event. County of default dhcp for the interface of compensation data.

  * DHCP special socket: 16:01:28.376 Oct 07: customer success 68:b5:99:45:44:8e DHCP event. County of default dhcp for the interface of compensation data.

  * pemReceiveTask: 16:01:28.376 Oct 07: deleted entry NPU 68:b5:99:45:44:8e 10.21.1.96.

  * Dot1x_NW_MsgTask_6: 16:01:34.017 Oct 07: 68:b5:99:45:44:8e received EAPOL-Key of mobile 68:b5:99:45:44:8e

  * Dot1x_NW_MsgTask_6: 16:01:34.017 Oct 07: 68:b5:99:45:44:8e received EAPOL-Key to launch the new Exchange of keys to mobile 68:b5:99:45:44:8e

  * Dot1x_NW_MsgTask_6: 16:01:34.017 Oct 07: 68:b5:99:45:44:8e initialization key EAPOL request replay to 00 00 00 00 00 00 00 a0 for customer 68:b5:99:45:44:8e

  * Dot1x_NW_MsgTask_6: 16:01:34.017 Oct 07: 68:b5:99:45:44:8e exchange of departure for 68:b5:99:45:44:8e mobile key, data packages will be removed

  * Dot1x_NW_MsgTask_6: 16:01:34.017 Oct 07: 68:b5:99:45:44:8e transmission of EAPOL-Key Message for mobile 68:b5:99:45:44:8e

  INITPMK (message 1) State, counter replay 00.00.00.00.00.00.00.03

  * Dot1x_NW_MsgTask_6: 16:01:34.017 Oct 07: 68:b5:99:45:44:8e Received key EAPOL MIC err message of mobile 68:b5:99:45:44:8e

  * Dot1x_NW_MsgTask_6: 16:01:34.018 Oct 07: 68:b5:99:45:44:8e received EAPOL-Key of mobile 68:b5:99:45:44:8e

  * Dot1x_NW_MsgTask_6: 16:01:34.018 Oct 07: 68:b5:99:45:44:8e received EAPOL-Key to launch the new Exchange of keys to mobile 68:b5:99:45:44:8e

  * Dot1x_NW_MsgTask_6: 16:01:34.018 Oct 07: 68:b5:99:45:44:8e exchange of departure for 68:b5:99:45:44:8e mobile key, data packages will be removed

  * Dot1x_NW_MsgTask_6: 16:01:34.018 Oct 07: 68:b5:99:45:44:8e transmission of EAPOL-Key Message for mobile 68:b5:99:45:44:8e

  INITPMK (message 1) State, counter replay 00.00.00.00.00.00.00.03

  * Dot1x_NW_MsgTask_6: 16:01:34.018 Oct 07: 68:b5:99:45:44:8e Received key EAPOL MIC err message of mobile 68:b5:99:45:44:8e

  * dot1xMsgTask: 16:01:34.997 Oct 07: 68:b5:99:45:44:8e failure sending WPA EAPOL-Key due to invalid state 2 to 68:b5:99:45:44:8e mobile

  * dot1xMsgTask: 16:01:34.997 Oct 07: 68:b5:99:45:44:8e unable to send the WPA key for mobile 68:b5:99:45:44:8e

  * dot1xMsgTask: 16:01:34.997 Oct 07: impossible to update 68:b5:99:45:44:8e released 68:B5:99:45:44:8E key for mobile

  * osapiBsnTimer: 16:01:35.201 Oct 07: 68:b5:99:45:44:8e 802. 1 x "timeoutEvt" Timer expired for station 68:b5:99:45:44:8e and message = M2

  * dot1xMsgTask: 16:01:35.201 Oct 07: 68:b5:99:45:44:8e 1 retransmit of EAPOL M1 (length 99) key for mobile 68:b5:99:45:44:8e

  * osapiBsnTimer: 16:01:36.221 Oct 07: 68:b5:99:45:44:8e 802. 1 x "timeoutEvt" Timer expired for station 68:b5:99:45:44:8e and message = M2

  * dot1xMsgTask: 16:01:36.221 Oct 07: 68:b5:99:45:44:8e 2 retransmit EAPOL M1 (length 99) key for mobile 68:b5:99:45:44:8e

  * osapiBsnTimer: 16:01:37.241 Oct 07: 68:b5:99:45:44:8e 802. 1 x "timeoutEvt" Timer expired for station 68:b5:99:45:44:8e and message = M2

  * dot1xMsgTask: 16:01:37.241 Oct 07: 68:b5:99:45:44:8e failure of retransmission for EAPOL M1 key to 68:b5:99:45:44:8e mobile, retransmit count 3, CMO deauth count 0

  * dot1xMsgTask: 16:01:37.241 Oct 07: 68:b5:99:45:44:8e reset CMOS PMK Cache entry 0 for station 68:b5:99:45:44:8e

  * dot1xMsgTask: 16:01:37.241 Oct 07: 68:b5:99:45:44:8e cache of active adjustment key index 0---> 8

  * dot1xMsgTask: 16:01:37.241 Oct 07: 68:b5:99:45:44:8e Deauthenticate sent mobile site 68:86:a7:ca:bd:40 BSSID 0 (calling 1x_ptsm.c:546)

  * dot1xMsgTask: 16:01:37.241 Oct 07: 68:b5:99:45:44:8e removal of Scheduling of Station Mobile: (callerId: 57) in 10 seconds

  (Cisco Controller) > * osapiBsnTimer: 16:01:47.442 Oct 07: 68:b5:99:45:44:8e apfMsExpireCallback (apf_ms.c:615) expires Mobile!

  * apfReceiveTask: 16:01:47.442 Oct 07: 68:b5:99:45:44:8e apfMsExpireMobileStation (apf_ms.c:5827) state change for mobile 68:b5:99:45:44:8e on AP 68:86:a7:ca:bd:40 of Disassociated Associates

  The error:

  Receipt key EAPOL MIC err message from mobile

  suggests that the (computer) STA sends an invalid nonce value. The MIC stands for verifying the integrity of messages

  I've seen generally this when customers use TKIP, try to change your WLAN to use only the AES. Also if you can send the output of: show wlan ID, this will help clarify how your WLAN is configured.

  * Please Note If this post was helpful, thank you *.

• WLC5508 problem with dhcp and flexconnect local switching

  Hello
  I have a new WLC 5508 with firmware 8.0.133.0 (suggested one right now) and I'm trying to set up a WLAN with flexconnect and local switching, but when I try to connect a client it is not getting an IP address.

  Here's what I did:
  -put the AP mode flexconnect
  -support vlan in the AP has allowed
  -local switching license and only in wlan
  -spread the vlan from AP to the local gateway
  -put the IP helper on local and pointed the wlc management ip gateway
  -set up a scope for the vlan Server dhcp internal WLC
  -set up a working group with the vlan-wlan association flexconnect

  Here is what I checked:
  -l'AP obtains an IP address in dhcp in the vlan, and a lease for that appear in the DHCP Server internal to the WLC
  -If I put the interface vlan on a switch in DHCP it gets the ip address of the same way
  -If I set the static IP address in the wireless client it ping the local gateway and navigate normally
  -J' tried the deactivation/activation proxy DHCP in the management connected to the WLAN interface, but nothing happened
  -J' tried Central DHCP activation of treatment with no luck

  It seems a dhcpdump on the wireless client client ask for an IP address, but get no response, as if it were the DHCP request is be filtered or diverted somehow.

  All you other ideas?

  DHCP on the controller is not a real dhcp server, see it that way. The management interface is used when defining aid ip and proxy dhcp must be enabled for internal dhcp. In your configuration, dhcp only works for the AP and should not work for any cable customer. You should be able to use the IP helper pointing to your WLC management interface but also make sure that you create an interface on the WLC for the local subnet and assign the interface to a correct address, even if it is not actually using it. Then in the new dynamic interface of this local subnet, you create, make sure that the primary dhcp is the ip address of the controller management. I think it works.

  I would really use a true if possible dhcp server or even put a dhcp scope on the interface of L3 on the production site.

  -Scott

  Please evaluate the useful messages *.

• How to add the new AP on WLC

  Hello

  I currently have a WLC 4402 and 18 AP 1131. Everything works fine.
  I would add 2 AP to expand coverage. I have 2 1042 AP I want to add. How?
  I plugged my wifi vlan AP, and it gets its IP address given by the WLC (which is DHCP). I see it next to another AP on the WLC controller > internal DHCP server > allocated DHCP leases
  But all this after I don't know where to go...
  Can you help me?
  Thank you.

  Just for info... We have a bug in show stopper on the version of the software that you are running DHCP on WLC-related...

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

  Please move the DHCP server as any layer 3 device... and I see that you plan to use APs 1040,

  1040 series APs needs the minimum WLC software to 7.0. and more... Please update the WLC to 7.0.116 and this will solve the DHCP bug as the PA joining the WLC...

  Let me know how it works for you and don't forget to evaluate the useful post!

  Concerning

  Surendra

• Internet connection lost when power is removed Probook s 4330

  HP probook 4330 s

  Windows 7 Ultimate + service pack 1 64-bit

  Driver: Microsoft 3.0.0.41 RALINK driver (up to date when I do a search)

  When I remove its internet external power is lost.  The wireless connection always seems to be in place, but there is no traffic.  I can't ping anything in this case.

  The only way to get this up and running again is to

  1. Insert the AC power

  2. restart the service dhcp client (sometimes required to conduct more than once).  The service has not stopped, but for some reason, it becomes it running.

  I also tried to disable the 'allow the computer to turn off this device to save power ".  But that did not help.

  Have spent a long period of problems, have almost tried everything and am at the point where I am considering the purchase of a new laptop computer.

  Kind regards

  Paul

  fixed by updating with the latest wifi driver

• Already registered on the portal OnPlus - cannot add a device already enabled/customer

  Hello

  I am registered on OnPlus.

  Then my colleague registered and activated a device.

  I could not activate the device - even if my PC is on the same subnet and can connect to it very well (with the password provided by my colleague).

  When he sends me an invitation for the device - it takes me to the registration page.

  If I get my information from record (again) - I get (not surprisingly)...

  "We had a problem with your submission. Please correct the following errors. This user ID is already registered. »

  Still-, there is no choice because "I am already registered.

  When I connect OnPlus and try to "Add Customer" - I put in the details, then it goes to the activation screen with

  "CustomerX / status".

  To activate this client:

  Install the Agent network OnPlus on the premises of the customer and connect it to the LAN client.

  Turn the Network Agent OnPlus the switch zipper on the back panel of the Network Agent OnPlus.

  If your computer is connected to the same network as the network OnPlus Agent, click on the button activate now below.

  Otherwise, follow the instructions for activation in the guide getting started for the Cisco OnPlus Network Agent.

  Activation for this customer information are:

  Activation ID:... »

  If I click on activate it says

  "Unable to determine a local IP address for all Agent OnPlus of network into your current network.

  Check that the Network Agent OnPlus is connected to the same local network as this browser. OnPlus Network Agent must be on the same public WAN IP address (203.25.x.x) in your web browser block current.

  Not enabled OnPlus network Agents will attempt to disseminate their IP up to 30 minutes and if successful will appear here for 4 hours. Try to stop power OnPlus Network Agent if it has been online for more than 30 minutes.

  Verify that the DHCP service is running on the local network so that network OnPlus Agent is able to acquire an IP via DHCP. You will be able to change Agent of the OnPlus network to use a static IP address if you choose to (recommended), but the DHCP service is required to access the Network Agent OnPlus start.

  Ensure that DHCP clients can route to the Internet.

  If the Network Agent OnPlus hosting site has multiple WAN paths to the Internet, try refreshing this page. Your browser must Access this page from the IP WAN as the Agent of OnPlus network address. »

  We even tried power cycling it, and I'm definitely on the same subnet.

  There was no possibility of entering an IP address no matter where manually - process regarding the "Impossible to determine an IP address local for all Agent OnPlus network on your current network."

  I ping the device and even connect to its graphical interface. It simply does not appear as any way to add this unit to my own account on the portal OnPlus.

  That please?

  Hello Brett.

  The On100 device can be associated with a single customer and a customer cannot exist in more than one Agent account. From your description, I understand that your colleague registered as a OnPlus Agent, created an account customer, and then active the On100 device under this new client.

  However, it is possible for you to have access to the customer site by becoming a sub-agent under account OnPlus Agent of your colleague.  And according to the description above, it seems that your colleague has already sent you an invitation to become a subagent.  The problem now is that you have previously registered your EAC as OnPlus Agent id.  It is not possible for a single CCE id or an Agent and a secondary agent in the OnPlus portal.

  To allow your registration as sub-agent, we remove your EAC to your portal id.  It is a manual step that I am happy to help you.  Simply unicast your Agent account information to [email protected] / * / .  Once I take off your CEC id you will be OK to complete the registration of subagent.

  Here's some more information about the creation of the sub-agents in the portal OnPlus.  A previous post jamwyatt courtesy of response:

  In the account that contains the Agent network ON100, you can add other agents, on invitation. On the overview page, there is a menu agent at the top that will allow you to invite the officers. Once you invite an agent, and they sign up, they will be able to see the same view you see. The design intent is that you set up a master account for your business, then you invite other employees and contractors to adhere as agents of this account. Each guest will need a Cisco ID and once that they sign up, they will have to be approved by the owner of the main account (same menu agent, selection "of Agents in waiting"). Using this approach, the owner of the company retains the main account and allows you to manage completely all agents.

  Kind regards

  -r.

• Reset a TOWER 1242 Ethernet interface

  Is there a way to reset a 1242 IP and gateway (both are configured under the same IP address because a Cut ' paste error in the WCS... so the AP is not accessible and the DHCP failover will not work, because the AP can reach his false gateway...)

  The AP is on a remote location, I can only ask the user to support onside. Is there an easy way to retrieve the AP do DHCP?

  Hello

  Restart the AP several times... It worked for me while troubleshooting at several customers... However when ever it does not... We need to get the console access to the AP and then issue the command below...

  en

  Debug lwapp console cli or debug console cli capwap

  Claire lwapp private-config or claire capwap private-config

  end

  LWAPP ap ip

  LWAPP ap controller ip

  or

  Debug lwapp console cli or debug console cli capwap

  int fa 0

  IP addr dhcp

  end

  This will do...

  Let me know if that answers your question

  Concerning

  Surendra

  ====

  Please do not forget to note the useful messages that answered your question or was useful

• Port of the switch for LAP

  Hello

  I have a potentially ridiculous question.

  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, ym question lies in the connection with the TOWER to the switch... should be a trunk as well?  If each SSID is on a VLAN respective, then TURN to pass wouldn't be a trunk as well?  Example: I have my tricks on vlan 9 (192.168.9.0/24) and I want my personal WLAN on VLAN 6 (192.168.6.0/24) and I want that my guest WLAN on vVLAN 8 (can you guess the IP address?)

  I read that the link between the KNEES and the SW needs to be an access port (so it would ' Switchport access vlan 9 "on the port which connects the LAP... but how would the traffic / VLAN 6 and 8, considered then?)

  FYI - DHCP for all devices (APs and hosts for each WLAN) is going to be the closest crossing the WLC, the DHCP for the APs will opt 43 defined pool so that APs can find the WLC...

  I'm getting confused about how the traffic is separated, can someone enlighten me?

  I still have to set up the JUMP with IAS and other, buit I must get DHCP and WLC communications up to b4, I even worry about security...

  However, ym question lies in the connection to the LAP to the switch...does that need to be a trunk as well?
  

  No. an access port.

• WLC - server DHCP (Override) and

  Hi guys,.

  A little confused. If I want my wireless clients to a DHCP address on my business DHCP servers, I need to click the Overrides button, for the WLC to act as a relay agent or the docs say that this happens by default?

  Can someone pls confirm, because it is a little confusing. The files help mentioned below also?

  Thx a lot indeed.

  Ken

  Server DHCP (Override)

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

  When the substitution is selected, you can enter the IP address of your DHCP server. It is a required field for some configurations of WLAN. There are three valid configurations:

  -DHCP Server override on a valid DHCP and DHCP address assignment requested server IP address: requires that all WLAN clients obtain an IP address from the DHCP server.

  -DHCP Server override on a valid DHCP and DHCP address unnecessary assignment server IP address: allows all clients WLAN get an IP address from the DHCP server or use a static IP address.

  -DHCP Server OFF Overrides: guests WLAN using the DHCP setting in the Management Interface, not the static address of the Forces.

  Hi Ken,

  Your WLC default is DHCP relay, you do not need to override.

  The WLAN configuration, put you in an interface. If you check this configuration of the interface, you will see that it points to a DHCP server. This is where your WLC relays to wireless clients.

  If you wish to override this setting and to send your customers to a different DHCP server instead, you then click DHCP replace in the WIFI config and enter another IP DHCP address.

  HTH

  Jerome

• WLC DHCP Proxy - to do or not to do?

  What is on the rise / decline of gyration of the DHCP Proxy of the WLC setting?  I know the option is there now, but it always by default the proxy mode, so what's the question?  I ask, because I could make an issue of a wlan comments becomes a dhcp server much easier, if requested by the customer. Then I can relay dhcp off a pix and my company dhcp/dns server. But I'm worried what effect it may have on my other local wireless networks.

  Proxy DHCP is required if the WLC is the dhcp server, if you disable it don't forget to add the ip helper address to your L3 interfaces.

  The part of the config is a relic of a time Airespace who helped the WLC learn the customers ip access. This problem has been fixed, updated in subsequent versions of the code. So the proxy or the proxy is really up to if the WLC is dhcp or not. Unless yopu run 6.0.196.0 or 7.0.980. Where you could hit CSCth68708

  Sent by Cisco Support technique iPad App

• unloading of feature to make dhcp off the WLC and put it on Active Directory.

  I need to use the feature of unloading to dhcp off the WLC and put it on Active Directory.  Someone at - it a walkthrough or a page for this?  I know it's just a checkbox and a redirect to the new dhcp server, but where the hell is the configuration on the WLC?

  Thank you!

  -anne

  You can go there.

  http://www.Cisco.com/c/en/us/TD/docs/wireless/controller/7-4/configuration/guides/consolidated/b_cg74_CONSOLIDATED/b_cg74_CONSOLIDATED_chapter_01001001.html

  Point to your existing ad integrated DHCP server.

• WLC and DHCP

  We've got a supernet wherein the WLC is distributing addresses dhcp for wireless clients... radios motorola to be more precise.  My question is the WLC allow dhcp for clients wired on that subnet as well?

  Any Yes or no supporting documentation would be greatly appreciated.

  Thank you!

  -anne

  http://www.Cisco.com/c/en/us/support/docs/wireless-mobility/wireless-LAN-WLAN/99470-config-wiredguest-00.html

  After a successful transfer from the client to the DMZ anchor controller, an IP DHCP, authentication of the client address assignment, and so on are handled in the DMZ WLC.

• WLC primary and secondary - Config DHCP Scope

  Hi all

  WLCs: AIR-CT2504-K9

  We have therefore two 2504 s each in separate locations. Inside of each of the Access Points, we have configured one of the controllers of the WLC primary and the other as the secondary WLC tab HA. So my question has to do with the internal DHCP configured in each of the controllers scope.

  We only use the internal DHCP server of the WLCs for our Public Wi - Fi network. And I was wondering if I should configure the DHCP scope even in two controllers, or if they are supposed to be different?

  For example:

  Elementary WLC - extended DHCP: 10.12.202.110 - 10.12.202.200
  Secondary WLC - extended DHCP: 10.12.202.xxx - 10.12.202.xxx?

  The way in which access points are configured, they should only be attached to a controller or another. So that the way its set up it shouldn't be some APs on a single controller and some of the other. They should all be attached to the WLC even at any time. So, given that I can configure the same scope on both controllers?

  Any ideas or suggestions would be greatly appreciated!

  Thanks in advance,
  Matt

  Yes, you can set up this way, as long as you don't expect not so much operational WLC & customer service at the same time.

  If you think to expand this network of comments, I suggest you stay away from using DHCP internal like these WLCs has ever made to use as complete apart from entire DHCP servers in large scale networks.

  HTH

  Rasika

  Pls note all useful responses *.