Identifying- Client connecting slowly

Prasan Venky · ‎09-29-2014

Dear All,

Sudden observation in my network is that client is taking time longer than usual to connect to wireless. It shows identifying for more than 3 mins before connecting. Why it is like that? what is happening during the state of 'Identifying'.? How to resolve that..?

WLC Model- 5508

AP's Model-3702E

Rasika Nayanajith · ‎09-29-2014

While client trying to connect take the "debug client <Client_MAC>" output from your WLC. That will tells us what's happening. Attach it to next response

HTH

Rasika

**** Pls rate all useful responses ****

Prasan Venky · ‎09-30-2014

Please find the debug output. Thanks

Rasika Nayanajith · ‎09-30-2014

Hi

As per the provided debug output I cannot see client took that long to get the connectivity. Altogether it took less than 1s (step 1 - 7). Value shown below is normal.

EAP Authentication- 558ms ( step 2 - 3)

4-Way Handshake - 31ms (Step 4-5)

1. *apfMsConnTask_1 : Sep 30 12:07:02.608: e8:2a:ea:0c:2e:7a Sending Assoc Response to station on BSSID d0:72:dc:5c:0b:1f (status 0) ApVapId 1 Slot 1

2. *Dot1x_NW_MsgTask_2: Sep 30 12:07:02.612: e8:2a:ea:0c:2e:7a Sending EAP-Request/Identity to mobile e8:2a:ea:0c:2e:7a (EAP Id 1)

3. *Dot1x_NW_MsgTask_2: Sep 30 12:07:03.266: e8:2a:ea:0c:2e:7a Processing Access-Accept for mobile e8:2a:ea:0c:2e:7a

4. *Dot1x_NW_MsgTask_2: Sep 30 12:07:03.269: e8:2a:ea:0c:2e:7a Sending EAPOL-Key Message to mobile e8:2a:ea:0c:2e:7a state INITPMK (message 1), replay counter 00.00.00.00.00.00.00.00 5. *Dot1x_NW_MsgTask_2: Sep 30 12:07:03.300: e8:2a:ea:0c:2e:7a Received EAPOL-key in PTKINITNEGOTIATING state (message 4) from mobile e8:2a:ea:0c:2e:7a

6. *Dot1x_NW_MsgTask_2: Sep 30 12:07:03.300: e8:2a:ea:0c:2e:7a 10.208.88.180 8021X_REQD (3) Change state to L2AUTHCOMPLETE (4) last state 8021X_REQD (3)

7. *Dot1x_NW_MsgTask_2: Sep 30 12:07:03.301: e8:2a:ea:0c:2e:7a 10.208.88.180 L2AUTHCOMPLETE (4) Change state to RUN (20) last state L2AUTHCOMPLETE (4)

you need to take a debug for a client that take longer time to see which part of connection takes time.

HTH

Rasika

**** Pls rate all useful responses ****

Prasan Venky · ‎10-06-2014

Hi,

I am facing a strange issues.

Type 1: I am getting ip assignments from DHCP server but still showing 'Identifying'. Takes minutes to get into domain. xxx.com

Type 2: 'Limited connectivity & No internet access' error while connecting.

Type 3: Not getting the gateway ip address in the DHCP assignment.

Could you explain me how to troubleshoot this to fix whether the issue is from Wireless side or Wired side or AD or DHCP ..?

Thanks in advance.

Rasika Nayanajith · ‎10-06-2014

What is the WLC software version you are running ? Attach "show wlan <WLAN_ID>" output for the WLAN you are having issue.

Looks like a bug, but first need to make sure configuration is correct.

Pls do not forget to rate all useful responses

HTH

Rasika

Prasan Venky · ‎10-06-2014

WLC Version is 7.6.120.0.

We are facing this issue only with corporate ssid.

Quick help is highly appreciated.

Rasika Nayanajith · ‎10-06-2014

First of all upgrade your code to 7.6.130.0 (7.6MR3), Also make sure your WLC FUS also upgrade to 1.9.0.0. Refer below release notes for those upgrade.

http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn76mr03.html

http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/fus_rn_OL-31390-01.html

The code you are in is not recommended & had many instabilities.

Let's do this first & see how it goes.

HTH

Rasika

**** Pls rate all useful responses ****