Clients stuck at 8021X_REQD
I have a CISCO 5508 WLC and 2602 WAP's. Some clients fail to connect while others connect without issue. I am broadcasting 2 SSID's a WPA2 ssid and a 802.1x ssid. The client fails on both.
I debugged the client and i see the client is stuck in 8021X_REQD. It never progresses past that. BUT....I can physically take the WLC to the campus and put them on the same subnet as the clients and they will connect. So I am leaning on a Routing issue, but what layer 3 issue would only effect SOME clients?
I am at a loss
(do1113cisco5508-02) >show interface detailed management
Interface Name................................... management
MAC Address...................................... 78:da:6e:da:a0:20
IP Address....................................... 10.32.0.112
IP Netmask....................................... 255.255.252.0
IP Gateway....................................... 10.32.0.1
External NAT IP State............................ Disabled
External NAT IP Address.......................... 0.0.0.0
VLAN............................................. untagged
Quarantine-vlan.................................. 0
Active Physical Port............................. 1
Primary Physical Port............................ 1
Backup Physical Port............................. Unconfigured
DHCP Proxy Mode.................................. Global
Primary DHCP Server.............................. 10.32.0.1
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
IPv4 ACL......................................... Unconfigured
mDNS Profile Name................................ Unconfigured
AP Manager....................................... Yes
Guest Interface.................................. No
L2 Multicast..................................... Enabled
--More-- or (q)uit
Similar Messages
-
PEAP clients stuck in the 8021X_REQD state
Hi,
I've got complaining for lots of PEAP clients not connecting to wireless network. Everything was working fine before. I logged into WLC and found out these clients are associated but stuck in the 8021X_REQD state. I checked our Radius server and couldn't find the failed log. The below message shows the debug for a client 00:0b:6b:24:66:55 and the attachment is the client info shown on the WLC. Please help. Thanks.
(vau-cr-wlc4402-1) >debug client 00:0b:6b:24:66:55
(vau-cr-wlc4402-1) >Mon Aug 8 15:40:53 2011: 00:0b:6b:24:66:55 802.1x 'timeoutEvt' Timer expired for station 00:0b:6b:24:66:55
Mon Aug 8 15:40:53 2011: 00:0b:6b:24:66:55 Retransmit 1 of EAP-Request (length 127) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 Association received from mobile on AP 00:1c:57:8b:34:e0
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 STA - rates (8): 130 132 139 150 140 18 152 36 176 72 96 108 0 0 0 0
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 STA - rates (12): 130 132 139 150 140 18 152 36 176 72 96 108 0 0 0 0
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 Processing RSN IE type 48, length 20 for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 Received RSN IE with 0 PMKIDs from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Initializing policy
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Change state to AUTHCHECK (2) last state 8021X_REQD (3)
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 10.115.148.80 AUTHCHECK (2) Change state to 8021X_REQD (3) last state 8021X_REQD (3)
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Plumbed mobile LWAPP rule on AP 00:1c:57:8b:34:e0
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 apfPemAddUser2 (apf_policy.c:209) Changing state for mobile 00:0b:6b:24:66:55 on AP 00:1c:57:8b:34:e0 from Associated to Associated
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 Stopping deletion of Mobile Station: (callerId: 48)
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 Sending Assoc Response to station on BSSID 00:1c:57:8b:34:e0 (status 0)
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 apfProcessAssocReq (apf_80211.c:3838) Changing state for mobile 00:0b:6b:24:66:55 on AP 00:1c:57:8b:34:e0 from Associated to Associated
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 dot1x - moving mobile 00:0b:6b:24:66:55 into Connecting state
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 Sending EAP-Request/Identity to mobile 00:0b:6b:24:66:55 (EAP Id 1)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL START from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 dot1x - moving mobile 00:0b:6b:24:66:55 into Connecting state
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP-Request/Identity to mobile 00:0b:6b:24:66:55 (EAP Id 2)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received Identity Response (count=2) from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 EAP State update from Connecting to Authenticating for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 dot1x - moving mobile 00:0b:6b:24:66:55 into Authenticating state
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=204) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 WARNING: updated EAP-Identifer 2 ===> 204 for STA 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 204)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 204, EAP Type 25)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=205) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 205)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 205, EAP Type 25)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=206) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 206)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 206, EAP Type 25)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=207) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 207)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 207, EAP Type 25)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=208) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 208)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 208, EAP Type 25)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=209) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 209)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 209, EAP Type 25)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=210) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 210)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 210, EAP Type 25)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=211) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 211)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 211, EAP Type 25)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=212) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 212)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 212, EAP Type 25)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=213) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 213)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 213, EAP Type 25)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=214) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 214)
Mon Aug 8 15:42:04 2011: 00:0b:6b:24:66:55 802.1x 'timeoutEvt' Timer expired for station 00:0b:6b:24:66:55
Mon Aug 8 15:42:04 2011: 00:0b:6b:24:66:55 Retransmit 1 of EAP-Request (length 127) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Association received from mobile on AP 00:1c:57:8b:0d:40
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 STA - rates (8): 130 132 139 150 140 18 152 36 176 72 96 108 0 0 0 0
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 STA - rates (12): 130 132 139 150 140 18 152 36 176 72 96 108 0 0 0 0
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Processing RSN IE type 48, length 20 for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received RSN IE with 0 PMKIDs from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Deleted mobile LWAPP rule on AP [00:1c:57:8b:34:e0]
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Updated location for station old AP 00:00:00:00:00:00-0, new AP 00:1c:57:8b:0d:40-0
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Initializing policy
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Change state to AUTHCHECK (2) last state 8021X_REQD (3)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 10.115.148.80 AUTHCHECK (2) Change state to 8021X_REQD (3) last state 8021X_REQD (3)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Plumbed mobile LWAPP rule on AP 00:1c:57:8b:0d:40
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 apfPemAddUser2 (apf_policy.c:209) Changing state for mobile 00:0b:6b:24:66:55 on AP 00:1c:57:8b:0d:40 from Associated to Associated
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Stopping deletion of Mobile Station: (callerId: 48)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending Assoc Response to station on BSSID 00:1c:57:8b:0d:40 (status 0)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 apfProcessAssocReq (apf_80211.c:3838) Changing state for mobile 00:0b:6b:24:66:55 on AP 00:1c:57:8b:0d:40 from Associated to Associated
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 dot1x - moving mobile 00:0b:6b:24:66:55 into Connecting state
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP-Request/Identity to mobile 00:0b:6b:24:66:55 (EAP Id 1)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received Identity Response (count=1) from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 EAP State update from Connecting to Authenticating for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 dot1x - moving mobile 00:0b:6b:24:66:55 into Authenticating state
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=153) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 WARNING: updated EAP-Identifer 1 ===> 153 for STA 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 153)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 153, EAP Type 25)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=154) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 154)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response packet with mismatching id (currentid=154, eapid=153) from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 154, EAP Type 25)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=155) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 155)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 155, EAP Type 25)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=156) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 156)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 156, EAP Type 25)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=157) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 157)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 157, EAP Type 25)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=158) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 158)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 158, EAP Type 25)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=159) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 159)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 159, EAP Type 25)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=160) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 160)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 160, EAP Type 25)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=161) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 161)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 161, EAP Type 25)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=162) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 162)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 162, EAP Type 25)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=163) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 163)
Mon Aug 8 15:43:03 2011: 00:0b:6b:24:66:55 802.1x 'timeoutEvt' Timer expired for station 00:0b:6b:24:66:55
Mon Aug 8 15:43:03 2011: 00:0b:6b:24:66:55 Retransmit 1 of EAP-Request (length 127) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:33 2011: 00:0b:6b:24:66:55 802.1x 'timeoutEvt' Timer expired for station 00:0b:6b:24:66:55
Mon Aug 8 15:43:33 2011: 00:0b:6b:24:66:55 Retransmit 2 of EAP-Request (length 127) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Association received from mobile on AP 00:1c:57:8b:0d:40
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 STA - rates (8): 130 132 139 150 140 18 152 36 176 72 96 108 0 0 0 0
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 STA - rates (12): 130 132 139 150 140 18 152 36 176 72 96 108 0 0 0 0
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Processing RSN IE type 48, length 20 for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received RSN IE with 0 PMKIDs from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Initializing policy
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Change state to AUTHCHECK (2) last state 8021X_REQD (3)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 10.115.148.80 AUTHCHECK (2) Change state to 8021X_REQD (3) last state 8021X_REQD (3)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Plumbed mobile LWAPP rule on AP 00:1c:57:8b:0d:40
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 apfPemAddUser2 (apf_policy.c:209) Changing state for mobile 00:0b:6b:24:66:55 on AP 00:1c:57:8b:0d:40 from Associated to Associated
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Stopping deletion of Mobile Station: (callerId: 48)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending Assoc Response to station on BSSID 00:1c:57:8b:0d:40 (status 0)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 apfProcessAssocReq (apf_80211.c:3838) Changing state for mobile 00:0b:6b:24:66:55 on AP 00:1c:57:8b:0d:40 from Associated to Associated
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 dot1x - moving mobile 00:0b:6b:24:66:55 into Connecting state
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP-Request/Identity to mobile 00:0b:6b:24:66:55 (EAP Id 1)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received Identity Response (count=1) from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 EAP State update from Connecting to Authenticating for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 dot1x - moving mobile 00:0b:6b:24:66:55 into Authenticating state
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=174) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 WARNING: updated EAP-Identifer 1 ===> 174 for STA 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 174)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 174, EAP Type 25)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=175) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 175)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 175, EAP Type 25)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=176) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 176)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 176, EAP Type 25)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=177) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 177)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 177, EAP Type 25)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=178) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 178)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 178, EAP Type 25)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=179) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 179)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 179, EAP Type 25)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=180) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 180)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 180, EAP Type 25)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=181) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 181)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 181, EAP Type 25)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=182) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 182)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 182, EAP Type 25)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=183) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 183)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 183, EAP Type 25)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=184) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 184)
Mon Aug 8 15:44:07 2011: 00:0b:6b:24:66:55 802.1x 'timeoutEvt' Timer expired for station 00:0b:6b:24:66:55
Mon Aug 8 15:44:07 2011: 00:0b:6b:24:66:55 Retransmit 1 of EAP-Request (length 127) for mobile 00:0b:6b:24:66:55
(vau-cr-wlc4402-1) >debug disable-allHi,
Check the username/password database on the AD if ur using one or check if the AD is integrated correctly with the IAS or the ACS.
Issue either on the IAS or ACS (RADIUS server) , the WLC is waiting for the response from the RADIUS.
Regards
Surendra -
Static IP clients stuck on dhcp_reqd after upgrade to LAP
I have wireless thermal printers that have static IP addresses. They are on an open wlan and the dhcp required box is not checked.
The client gets hung at DHCP_REQD even though the client has a static address.
Controllers are standalone wlc4402(x2) running 41.1.185.0. Access-points are a mix of 1510, 1231 and 1242. Clients running 802.1x PEAP and DHCP are ok (different SSID).
This is the log from the WCS troubleshooting window:
09/17/2007 06:57:49 EDT INFO 42.201.0.40 Controller association request message received.
09/17/2007 06:57:49 EDT INFO 42.201.0.40 Received reassociation request from client.
09/17/2007 06:57:49 EDT INFO 42.201.0.40 The wlan to which client is connecting does not require 802 1x authentication.
09/17/2007 06:57:49 EDT INFO 42.201.0.40 Client does not have an IP address yet.
09/17/2007 06:57:49 EDT INFO 42.201.0.40 Client Moved to DHCP Required State.
09/17/2007 06:57:49 EDT INFO 42.201.0.40 Client moved to associated state successfully.
09/17/2007 07:00:00 EDT INFO 42.201.0.40 Controller association request message received.
09/17/2007 07:00:00 EDT INFO 42.201.0.40 Received reassociation request from client.
09/17/2007 07:00:00 EDT INFO 42.201.0.40 The wlan to which client is connecting does not require 802 1x authentication.
09/17/2007 07:00:00 EDT INFO 42.201.0.40 Client does not have an IP address yet.
09/17/2007 07:00:00 EDT INFO 42.201.0.40 Client Moved to DHCP Required State.
09/17/2007 07:00:00 EDT INFO 42.201.0.40 Client moved to associated state successfully.
09/17/2007 07:00:05 EDT INFO 42.201.0.40 Controller association request message received.
09/17/2007 07:00:05 EDT INFO 42.201.0.40 Received reassociation request from client.
09/17/2007 07:00:05 EDT INFO 42.201.0.40 The wlan to which client is connecting does not require 802 1x authentication.
09/17/2007 07:00:05 EDT INFO 42.201.0.40 Client does not have an IP address yet.
09/17/2007 07:00:05 EDT INFO 42.201.0.40 Client Moved to DHCP Required State.
09/17/2007 07:00:05 EDT INFO 42.201.0.40 Client moved to associated state successfully.We got wireless network cameras (Axis 207W) that only connects when they are configured with DHCP, If they are configured with IP-addresses they get stuck at DHCP_REQ.
Our Laptops connects with both DHCP or IP configured, on the same WLAN as the cameras.
The cameras has no sleep mode. -
SAP Business One Client Stuck While upgrading
Hi Experts,
I have successfully run the upgrade 8.8 patch leve 8 on the server(windows 2003). The server also had the client installed.
As usually we opened up the client for autoupgrade, it seems like it was taking too much time to upgrade and it looked like the client upgrade got stuck.
So we ended the task(The client icon on the desktop disappeared the next moment. ) and tried to upgrade the client using the B1share folder.
We get the messages like Error 1605: This action is valid only for currently installed products . when i say okay
Error:Number:0*80040702
Description: Failed to load Dll; Creator dll
Next i have also tried to uninstall from add\remove programs, then it says
error 1628: failed to complete installation.
Please let me know how to solve this problem.
Regards,
Chidamber.Hi!
Im having the same problem after i tried to upgrade my version to SBO 8.8 PL 08. Ive also tried to run the fix mentioned in sap notes 1408662. To no luck, i still cant access my SBO client. Whenever I try to access the client I get this message - "The B1 upgrade failed to locate the setup file needed for the upgrade".
Help please
Camille -
OSD - client stuck in ProvisioningMode - help
Guys,
CM newbie here.. I am attempting a very simple OSD via TS, and like many of the post related to (provisioing mode = true) I am stuck.
I read atleast 40 post on various sites that mentions this issue, with the work around being to modify registry keys after the task "Setup Windows and ConfigMgr" (as mentioned
Here and in many places on this forum). I understand that this is a "work-around" and doesnt address the issue, but this never works for me as the machine reboot directly after "Setup Windows
and ConfigMgr" (and reg keys never get applies and neither does anything after this step).
I've also read the multiple reboots after Software Update can cause this, which i do not have. Also, I dont have a single reboot task in the TS and I still get the same results. My Setup is CM2012r2-cu1 and i just added the CU1 patch to the "Setup Windows
and ConfigMgr" task using steps similar to this.
I though the issue was solved once I added the patch as I could have swore my first deployment works successfully (provisioning mode=false), but I have re-ran the same TS several times and Im still stuck in provisioning mode.
During the installation of "Setup Windows and ConfigMgr" when booted to the OS, if I bring up the console and change these reg values before the machine reboots (about a 10 second window), the TS run as expect and my packages in the TS are deployed.
I have attached a screenshot of the the most basic TS that I have and the issue of being stuck in provisioning mode still persist. I removed the "Run Commandline" task of modifing the registry keys after the "Setup Windows and ConfigMgr"
task as it wasn't setting the value anyways. Any idea where am I going wrong?Hi Torsten,
Thanks for the reply. The client appears to install successfully. Below are the
all of the fails that are in the ccmsetup.log file, as well as the success return code at the end. Also, the machine is in a Workgroup at the time of Client installation.
Failers:
1) Unexpected row count (0) retrieved from AD.
ccmsetup 9/9/2014 9:25:56 PM
1892 (0x0764)
2) Failed to get site version from AD with error 0x80004005
ccmsetup 9/9/2014 9:25:56 PM
1892 (0x0764)
3) File 'C:\WINDOWS\system32\msrdc.dll' does not exist. Discovery failed.
ccmsetup 9/9/2014 9:25:57 PM
1892 (0x0764)
4) File 'C:\WINDOWS\ccmsetup\WindowsFirewallConfigurationProvider.msi' does not exist. Discovery failed.
ccmsetup 9/9/2014 9:25:57 PM
1892 (0x0764)
5) Failed to load mdmregistration.dll with error 0x8007007e
ccmsetup 9/9/2014 9:25:58 PM
1892 (0x0764)
6) Failed to load mdmregistration.dll. Continue deployment.
ccmsetup 9/9/2014 9:25:58 PM
1892 (0x0764)
7) MSI: Action 21:26:31: SmsGenerateFailureMIF. ccmsetup
9/9/2014 9:26:31 PM 1892 (0x0764)
8) MSI: Action 21:26:34: CcmRegisterEndpointRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterEndpoint.
ccmsetup 9/9/2014 9:26:34 PM
1892 (0x0764)
9) MSI: Action 21:26:36: CcmRegisterComponentsRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterComponents.
ccmsetup 9/9/2014 9:26:36 PM
1892 (0x0764)
10) MSI: Warning 25702. Failed to uninstall PrepDrvr.Sys for Software Metering Agent.
ccmsetup 9/9/2014 9:26:37 PM
1892 (0x0764)
11) MSI: Action 21:26:57: CcmRegisterEndpointRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterEndpoint.
ccmsetup 9/9/2014 9:26:57 PM
1892 (0x0764)
Success
1) File C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi installation succeeded.
ccmsetup 9/9/2014 9:27:17 PM
1892 (0x0764)
2) CcmSetup is exiting with return code 0 ccmsetup
9/9/2014 9:27:17 PM 1892 (0x0764) -
SCCM Clients stuck downloaded Windows Updates(Need Help)
I am using SCCM 2007 software update for my site. I created a deployment for windows XP patches and it applied successfully on the collection. But now i am seeing in Enforcement states for a deployment, Clients are stuck "downloaded Update(s)" stage,
I have check client logs also but does not find any error.
Can any one help me out over this
Regad
SachinKindly stop trying to bump your post by entering information that doesn't help anyone. On the client side what does it look like. Does the patch say failed when it installs? Do the client even see anything. You can stop the Windows
Update service. Delete the software distribution folder and restart it and it should recreate the folder and attempt to download the patches again and install. Remember the community is here to help when possible. By your posts I assume this
is an emergency so you might want to contact CSS, searching the internet or find a private consultant that could help you faster than we could. Sometimes there just isn't enough information for us to fix a problem. I have seen this problem
every month and every month a machine has a different problem as to why the error occurs. It could be
Previous required patch is broken
Windows update is messed up
WMI issue
Patch downloaded is corrupt. Delete the cache folder and see if the client will retry
Machine simply needs a reboot and it will complete whatever it is doing, retry and install
Client needs to be repair
Take a step back from the problem and write down some problems/solutions so you can track what you are doing and so you can find a direction.
http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com -
Hello. I've come across an oddity and I'm a bit stuck. I was reviewing some application deployments and noted that in one particular room, after a month half of the PCs were still reporting an "In Progress" state. I remoted on to one of these PCs
and found that there was about a dozen apps waiting to install. Two were listed as "downloading", the rest were waiting.
I had a flick through the logs and found that the CAS log was filling every 5-9seconds with the same line:
<![LOG[IsCacheCopyNeeded returned 'true' by {5777363A-FB22-4a42-ABB0-522DD42711DC}]LOG]!><time="10:29:04.624+00" date="11-27-2013" component="ContentAccess" context="" type="1" thread="260"
file="cachemanager.cpp:344">
...it's the same reference on every PC stuck in this "in progress" state.
I have also noted the CCMEXEC log is spamming the following line every ten minutes:
<![LOG[No logged on cached user during monitor task, trying to select.]LOG]!><time="20:20:57.378+00" date="11-21-2013" component="CcmExec" context="" type="1" thread="1660" file="senslog.cpp:1570">
...even if someone *is* logged on.
I have noticed this in the LocationServices log:
<![LOG[The number of discovered DPs(including Branch DP and Multicast) is 0]LOG]!><time="14:32:37.783+00" date="11-21-2013" component="LocationServices" context="" type="1" thread="1672"
file="lsutils.cpp:872">
Also, the SMS service will not stop cleanly. It hangs when attempting to stop.
What I've tried:
Attempting a client repair doesn't work.
Purging the download catalogue/Software Distribution/Catroot2 folder doesn't work.
I have tried uninstalling the client, purging the above folders and then reinstalling. The CAS is now behaving but the machine seems dead in the water in terms of the missing osftware updates, AppV 4.6 apps, AppV 5 apps and the physical installs.
I don't really want to ask that half a teaching space is taken out for a rebuild, do does anyone have any ideas? I am at a loss to understand why twenty PCs out of eight thousand have just suddenly all started showing the exact same error in the same room.
My gut is pointing at the network or boundaries?
Cheers.Rashmika, do you remember the log file that ultimately told you about the faulty app? We *are* using App-V and I'm seeing this problem on a number of machines.
Hi there, sorry for the delay, but I had to dig through two eyars of email archive to find the info xD
In order to track this down, I enabled logging on the client by doing the following:
1. Open regedit and navigate to following location
HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ CCM \ Logging \ @ GLOBAL
Set LogLevel to 0
1. Create the following KEY under HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ CCM \ Logging\DebugLogging Name: Enabled DataType: REG_SZ Value : True
...and then CAS.log started showing more information about the issue. Originally it was just spamming:
<![LOG[IsCacheCopyNeeded returned 'true' by {5777363A-FB22-4a42-ABB0-522DD42711DC}]LOG]
However with the above keys set, I could now see:
<![LOG[IsCacheCopyNeeded returned 'true' by {5777363A-FB22-4a42-ABB0-522DD42711DC}]LOG]!>
<![LOG[Found the AppV package [{B866BAFB-8F26-4C87-9169-3B6269EED5A1}] uses ConfigMgr content ID [Content_74376190-0a4e-4c73-a4d0-955b1bb76961] version 1, and it is configured as download and execute]LOG]!>
<![LOG[The AppV package {B866BAFB-8F26-4C87-9169-3B6269EED5A1} is not fully loaded into AppV cache, so we cannot delete the ConfigMgr cache copy(content ID Content_74376190-0a4e-4c73-a4d0-955b1bb76961 Version 1)]LOG]!>
<![LOG[The content Content_74376190-0a4e-4c73-a4d0-955b1bb76961 version 1 is needed]LOG]!>
...so now I had something concrete, and perhaps a reasonable explanation towards what was happening. If I recall, it wasn't so much package/reference 5777363A-FB22-4a42-ABB0-522DD42711DC, this was a bit misleading. I now had the actual content ID and a package
reference that led somewhere!
Hope it helps! Please post back if the root cause of this was some kind of DSC linked App-V 4 package :)
Rash. -
UDP client stuck in infinite loop
public static void main(String args[]) throws Exception
BufferedReader inFromUser= new BufferedReader(new InputStreamReader(System.in));
DatagramSocket clientSocket= new DatagramSocket();
InetAddress IPAddress = InetAddress.getLocalHost();
byte[] sendData = new byte[1024];
byte[] receiveData = new byte[1024];
String sentence = "";
boolean quit = true;
while(quit == true);
String initiateConntact = "hi there";
sendData= initiateConntact.getBytes();
DatagramPacket sendPacket= new DatagramPacket(sendData, sendData.length, IPAddress, 9876);
clientSocket.send(sendPacket);
DatagramPacket receivePacket= new DatagramPacket(receiveData, receiveData.length);
clientSocket.receive(receivePacket);
String modifiedSentence= new String(receivePacket.getData());
InetAddress getIPFromServer = receivePacket.getAddress();
System.out.println("The server is located at : " + getIPFromServer);
sentence = inFromUser.readLine();
System.out.println("From Server:" + modifiedSentence);
if(sentence.equals("bye"));
quit = false;
clientSocket.close();
}I am just courious why this pice of code gets stuck in an infinite loop.
(it seems anyway). It doesnt even make it into the while statement. If i replace the while with an if statement, everything works smoothly. Does anyone know what is actually happening here and why?
Thanks for your time.Why didnt the java compiler report the ;? or the
missing =?Because they're both syntactically valid.
You might want to code a loop with no body:
while ((ch = readChar()) != 0);
(same as)
while ((ch = readChar()) != 0)
// do nothing
And you might want to assign a boolean variable and compare it at the same time:
while (flag = callSomeMethod())
(as opposed to)
while ((flag = callSomeMethod()) == true)
Although in both cases I'd write them differently rather than making a statement which has 'side-effects' and makes for slightly less-readable code. -
Some guest clients stuck in DHCP_REQD state
Hi everyone,
We are regularly having issues with some (random) wireless guest users not being able to connect to our guest SSID while others are able to connect just fine. They get stuck in the DHCP_REQD state so do not even make it to the web authentication screen. We are running WLC 4404 code 7.0.98 and using the WLC (two of them) as internal DHCP servers with a /23 scope divided between the two of them. I have checked the lease allocations and there are plenty of ip addresses spare.
A couple of days ago, all the users connecting via APs associated via one of the WLCs were unable to get an ip address and were stuck in the DHCP_REQD state all day and we ended up rebooting the controller which seemed to fix the problem temporarily but today some users have again been unable to connect. The users connected to the second controller all apppeared to be working just fine. The config on both WLCs appears to be identical.
I have seen some previous discussion about this being a known Cisco bug and which have recommended a code upgrade to v7.0.116 and v7.0.220 and I just really wanted to know your thoughts about whether a code upgrade is really necessary or a misconfiguration is the more likely issue.
Just to complicate matters we are in the process of tunnelling all our guest users to anchor controllers in the DMZ but at present this issue seems to affect both users who are connecting to local WLCs and those that are being tunnelled to the DMZ controllers.
Fianlly, I just want to add that we are also looking into installing external DHCP servers in the DMZ to cater to the guest users instead of using the internal DHCP server on the WLCs. I just wanted to know of your own experiences ie whether a code upgrade will resolve the issue for now.Thanks, Viten. We are looking at upgrading the WLC code to v7.0.220 asap. Meanwhile, the DHCP_REQD issue occurred again with all users connecting to one of our WLCs and I ended up disabling/re-enabling the guest SSID on that WLC a couple of times and that seemed to do the trick for now. Longer term, I think we may need to move to external DHCP servers in the DMZ.
-
SCCM Windows Updates - Client stuck on Downloading but never finishes
I am running SCCM 2007 with 200 clients. I have been sucessfully performing windows updates through SCCM without an issue for about 6 months. Recently I approved updates released in March and most of the updates installed ok, but there are two, KB938464 and KB958690, which sit on status Downloading for hours until the desktop is switched off at night. The times reach 14 hours on some machines.
I have tried to cancel the updates by removing them from the Advertisements and from the Deployment packages but they still try to run everyday on 167 of 200 desktops. If I manually go to Windows Update and install the updates the issue goes away, however, you can imagine my unwillingness to do this across 167 stations if I can avoid it.
How can I do one or both of the following:
A) Cancel the updates so they no longer want to run on the clients
B) Fix the issue so the updates download properly.
The process that I use to approve and deploy updates:
Under Site Database -> Computer Management -> Software Updates
I select the updates I want to deploy and add them to a new update list. I place a check into the box to download the files associated to the updates.
Once the update list is built I select to deploy the updates, give it a name that represents the update period
I select a template that deploys but suppresses restart in the updates.
I select a deployment package, the same one I used for all my past updates
Download from the Internet
English
Schedule
Finish.
This has worked sucessfully for months.
Thank you for any help that can be offered.I think you can use powershell command to modify the cache size
Here is the link: http://thephuck.com/scripts/use-powershell-to-change-sccm-cache-directory-cache-size/
$ColQuery = "select * from sms_cm_res_coll_SMS0005E"
$CollectionMembers = gwmi -computername SCCM_Server -namespace root\sms\site_SMS -Query $ColQuery |sort Name
foreach($comp in $collectionmembers){
$server = $comp.name
write-host -fore green `n`t "working on " $server
$ccmcfg = gwmi -computer $server -Namespace root\ccm\SoftMgmtAgent -Class CacheConfig
$ccmcfg.Location = "d:\path\to\cache"
$ccmcfg.Size = "2048"
$ccmcfg.Put()
#stop service, sleep for 10s, start the service
Get-Service -computer $server ccmexec | Stop-Service
Start-Sleep 10
Get-Service -computer $server ccmexec | Start-Service
write-host -fore green `n`t "finished" $server -
Software updates - Clients stuck in passed/Inactive, passed/Active
I've deployed some software updates (an update group that has a deployment package of Windows Software Updates) to a small collection, but for the past couple days since I kicked off the deployment, all the assets in the collection are just
sitting with either of these two statuses.
There's no maintenance window on this collection, and deployment schedule was set to "As Soon As Possible".
I've tried running Software Updates Deployment Evaluation and Software Updates Scan Cycles multiple times thoughout the day but the clients do not appear to be pulling down any updates yet.
What should I be checking for at this point? Or just wait a couple days?When it comes to maintenance windows, they just dont affect the clients that reside in the collection where the maintenance window is configured. If you have configured Coll1 to include all of your clients, and configured a maintenance window on
that collection, if you then created Coll2 and added some of your clients to that, those clients would still get the configured maintenance window from Coll1. So check if you don't have any maintenance windows configured on another collection where you clients
are members of.
Nickolaj Andersen | www.scconfigmgr.com |
@NickolajA
To respond to this, I can say that I do not have any maintenance windows applied to this sub-collection, nor any other collections that the clients would be direct or indirect members of. -
Win8.1 Direct Access Client Stuck at "Connecting"
I'm experimenting with Direct Access in a lab setting with 1 client and 3 2012 R2 servers. The client is running Windows 8.1 Enterprise.
The client is always able to connect to the Direct Access server but is unable to ping or connect to the 2 servers that don't have RAS installed. Moreover, this behavior migrates to whichever server is running Remote Access Server: So, if I remove the role
and install on another server, the client is able to communicate with the new server, but not the old.
The connection from the client to the server is via IP-HTTPS (only option available to me in this environment). The client is able to reliably determine when it's on the Internet versus the intranet. However, when on the Internet, it stays in a "Connecting"
state and never connects, but I'm still able to access the DA server.
Does anyone have any ideas on how to resolve this?I managed to resolve the issue. I'm posting here in the hope that this may help another newbie to DA.
Here's what caused my issue: As I mentioned, this was a lab environment where the limited number of machines were fulfilling multiple roles. In particular, the DA Server was also a backup domain controller running DNS. In my research, I came across a comment
on http://directaccessguide.com that mentioned that the DA Server runs DNS64 to support clients; that made me suspicious that the regular DNS server was in some way conflicting. And, in fact, before this server was
made a backup DC, DA was functioning just fine. Removing the backup DC role resolved the issue.
So the takeaway is this: Don't run the regular DNS service on the DA Server; if you do, you will get DA client connectivity only to the DA Server. -
the following method sends a file to the server...
/* Sends the file to the server.
private void sendFile() {
try {
BufferedOutputStream bos = new BufferedOutputStream(clientSock.getOutputStream());
FileInputStream fis = new FileInputStream(f);
byte[] buffer = new byte[1024];
int i = 0;
int p = 0;
while ((i = fis.read(buffer)) != -1) {
bos.write(buffer, 0, i); //*
p += i;
updateProgress(p);
if (p == FileSize) //file is fully sent
isComplete = true;
fis.close();
bos.close();
catch (IOException e) { new HermesDialog(frame).showMessageDialog("Unknown Error 8159", "If you see this again, please contact the author."); }
}when i terminate the connection on the server side, the client stops at the line marked with the commented * and stays there. is there some way to know that the connection has been terminated and break out of the loop? i have already tried...
Socket.isConnected()
Socket.isClosed()
Socket.isInputShutdown()
Socket.isOutputShutdown()That's odd, you should get an exception for attempting to write to a closed socket. Are you sure the server didn't just stop reading? If that happens your writes will eventually block.
The correct way to handle this is to read from the socket, you will get an empty read when the socket closes. -
WLC 5508, SW 6.0.199.4, 1142 AP: Clients getting dropped intermittently
We have deployed a WLC 5508 w/ SW version 6.0.199.4, 1142 AP's & open authentication w/ MAC filtering. Clients are randomly getting dropped with "Limited Access" shown in Win 7. In this state, the client machine is unable to ping the gateway and sometimes lose their DHCP assigned IP as well. A manual disconnect/re-connect to the SSID is required everytime.
I ran a debug on one the clients stuck in the "Limited Access" state (debug client xx:xx:xx:xx):
*Apr 15 16:59:23.205: e0:91:53:60:1f:e4 Adding mobile on LWAPP AP 3c:ce:73:c5:1e:b0(0)
*Apr 15 16:59:23.205: e0:91:53:60:1f:e4 Scheduling deletion of Mobile Station: (callerId: 23) in 5 seconds
*Apr 15 16:59:23.205: e0:91:53:60:1f:e4 apfProcessProbeReq (apf_80211.c:4722) Changing state for mobile e0:91:53:60:1f:e4 on AP 3c:ce:73:c5:1e:b0 from Idle to Probe
*Apr 15 16:59:23.205: e0:91:53:60:1f:e4 Scheduling deletion of Mobile Station: (callerId: 24) in 5 seconds
*Apr 15 16:59:23.225: e0:91:53:60:1f:e4 Scheduling deletion of Mobile Station: (callerId: 24) in 5 seconds
*Apr 15 16:59:23.225: e0:91:53:60:1f:e4 Scheduling deletion of Mobile Station: (callerId: 24) in 5 seconds
*Apr 15 16:59:23.646: e0:91:53:60:1f:e4 Scheduling deletion of Mobile Station: (callerId: 24) in 5 seconds
*Apr 15 16:59:23.646: e0:91:53:60:1f:e4 Scheduling deletion of Mobile Station: (callerId: 24) in 5 seconds
*Apr 15 16:59:23.666: e0:91:53:60:1f:e4 Scheduling deletion of Mobile Station: (callerId: 24) in 5 seconds
*Apr 15 16:59:23.666: e0:91:53:60:1f:e4 Scheduling deletion of Mobile Station: (callerId: 24) in 5 seconds
*Apr 15 16:59:28.553: e0:91:53:60:1f:e4 apfMsExpireCallback (apf_ms.c:418) Expiring Mobile!
*Apr 15 16:59:28.554: e0:91:53:60:1f:e4 0.0.0.0 START (0) Deleted mobile LWAPP rule on AP [3c:ce:73:c5:1e:b0]
*Apr 15 16:59:28.554: e0:91:53:60:1f:e4 Deleting mobile on AP 3c:ce:73:c5:1e:b0(0)
On doing a manual re-connect, got the following logs:
*Apr 15 17:01:38.143: e0:91:53:60:1f:e4 Association received from mobile on AP b8:62:1f:e9:9f:30
*Apr 15 17:01:38.143: e0:91:53:60:1f:e4 Applying site-specific IPv6 override for station e0:91:53:60:1f:e4 - vapId 7, site 'Academy', interface 'students'
*Apr 15 17:01:38.143: e0:91:53:60:1f:e4 Applying IPv6 Interface Policy for station e0:91:53:60:1f:e4 - vlan 15, interface id 14, interface 'students'
*Apr 15 17:01:38.143: e0:91:53:60:1f:e4 Applying site-specific override for station e0:91:53:60:1f:e4 - vapId 7, site 'Academy', interface 'students'
*Apr 15 17:01:38.143: e0:91:53:60:1f:e4 0.0.0.0 START (0) Changing ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1276)
*Apr 15 17:01:38.143: e0:91:53:60:1f:e4 STA - rates (8): 130 132 139 150 12 18 24 36 0 0 0 0 0 0 0 0
*Apr 15 17:01:38.143: e0:91:53:60:1f:e4 STA - rates (12): 130 132 139 150 12 18 24 36 48 72 96 108 0 0 0 0
*Apr 15 17:01:38.143: e0:91:53:60:1f:e4 0.0.0.0 START (0) Deleted mobile LWAPP rule on AP [b8:62:1f:e5:6a:90]
*Apr 15 17:01:38.144: e0:91:53:60:1f:e4 Updated location for station old AP b8:62:1f:e5:6a:90-0, new AP b8:62:1f:e9:9f:30-0
*Apr 15 17:01:38.144: e0:91:53:60:1f:e4 apfProcessAssocReq (apf_80211.c:4268) Changing state for mobile e0:91:53:60:1f:e4 on AP b8:62:1f:e9:9f:30 from Probe to AAA Pending
*Apr 15 17:01:38.144: e0:91:53:60:1f:e4 Scheduling deletion of Mobile Station: (callerId: 20) in 10 seconds
*Apr 15 17:01:38.144: e0:91:53:60:1f:e4 0.0.0.0 START (0) Initializing policy
*Apr 15 17:01:38.144: e0:91:53:60:1f:e4 0.0.0.0 START (0) Change state to AUTHCHECK (2) last state AUTHCHECK (2)
*Apr 15 17:01:38.144: e0:91:53:60:1f:e4 0.0.0.0 AUTHCHECK (2) Change state to L2AUTHCOMPLETE (4) last state L2AUTHCOMPLETE (4)
*Apr 15 17:01:38.144: e0:91:53:60:1f:e4 0.0.0.0 L2AUTHCOMPLETE (4) Plumbed mobile LWAPP rule on AP b8:62:1f:e9:9f:30 vapId 7 apVapId 2
*Apr 15 17:01:38.144: e0:91:53:60:1f:e4 0.0.0.0 L2AUTHCOMPLETE (4) Change state to DHCP_REQD (7) last state DHCP_REQD (7)
*Apr 15 17:01:38.144: e0:91:53:60:1f:e4 apfPemAddUser2 (apf_policy.c:213) Changing state for mobile e0:91:53:60:1f:e4 on AP b8:62:1f:e9:9f:30 from AAA Pending to Associated
*Apr 15 17:01:38.145: e0:91:53:60:1f:e4 Scheduling deletion of Mobile Station: (callerId: 49) in 65535 seconds
*Apr 15 17:01:38.145: e0:91:53:60:1f:e4 Including FT Mobility Domain IE (length 5) in Initial assoc Resp to mobile
*Apr 15 17:01:38.145: e0:91:53:60:1f:e4 Sending Assoc Response to station on BSSID b8:62:1f:e9:9f:30 (status 0) Vap Id 2 Slot 0
*Apr 15 17:01:38.145: e0:91:53:60:1f:e4 apfProcessRadiusAssocResp (apf_80211.c:1957) Changing state for mobile e0:91:53:60:1f:e4 on AP b8:62:1f:e9:9f:30 from Associated to Associated
*Apr 15 17:01:38.189: e0:91:53:60:1f:e4 DHCP received op BOOTREQUEST (1) (len 308, port 13, encap 0xec03)
*Apr 15 17:01:38.189: e0:91:53:60:1f:e4 DHCP dropping packet due to ongoing mobility handshake exchange, (siaddr 0.0.0.0, mobility state = 'apfMsMmQueryRequested'
*Apr 15 17:01:39.953: e0:91:53:60:1f:e4 0.0.0.0 DHCP_REQD (7) State Update from Mobility-Incomplete to Mobility-Complete, mobility role=Local, client state=APF_MS_STATE_ASSOCIATED
*Apr 15 17:01:39.954: e0:91:53:60:1f:e4 0.0.0.0 DHCP_REQD (7) pemAdvanceState2 4166, Adding TMP rule
*Apr 15 17:01:39.954: e0:91:53:60:1f:e4 0.0.0.0 DHCP_REQD (7) Adding Fast Path rule
type = Airespace AP - Learn IP address
on AP b8:62:1f:e9:9f:30, slot 0, interface = 13, QOS = 0
ACL Id = 255, Jumbo F
*Apr 15 17:01:39.954: e0:91:53:60:1f:e4 0.0.0.0 DHCP_REQD (7) Successfully plumbed mobile rule (ACL ID 255)
*Apr 15 17:01:39.954: e0:91:53:60:1f:e4 0.0.0.0 Added NPU entry of type 9, dtlFlags 0x0
*Apr 15 17:01:39.954: e0:91:53:60:1f:e4 Sent an XID frame
*Apr 15 17:01:40.807: e0:91:53:60:1f:e4 Orphan Packet from STA - IP 169.254.201.128
*Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP received op BOOTREQUEST (1) (len 308, port 13, encap 0xec03)
*Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP processing DHCP DISCOVER (1)
*Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP xid: 0x9b24c896 (2602879126), secs: 1280, flags: 0
*Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP chaddr: e0:91:53:60:1f:e4
*Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP successfully bridged packet to DS
*Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP received op BOOTREPLY (2) (len 308, port 13, encap 0xec00)
*Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP processing DHCP OFFER (2)
*Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP xid: 0x9b24c896 (2602879126), secs: 0, flags: 0
*Apr 15 17:01:43.234: e0:91:53:60:1f:e4 DHCP chaddr: e0:91:53:60:1f:e4
*Apr 15 17:01:43.235: e0:91:53:60:1f:e4 DHCP ciaddr: 0.0.0.0, yiaddr: 10.6.2.160
*Apr 15 17:01:43.235: e0:91:53:60:1f:e4 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*Apr 15 17:01:43.235: e0:91:53:60:1f:e4 DHCP server id: 10.6.15.254 rcvd server id: 10.6.15.254
*Apr 15 17:01:43.235: e0:91:53:60:1f:e4 DHCP successfully bridged packet to STA
*Apr 15 17:01:43.240: e0:91:53:60:1f:e4 DHCP received op BOOTREQUEST (1) (len 316, port 13, encap 0xec03)
*Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP processing DHCP REQUEST (3)
*Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP xid: 0x9b24c896 (2602879126), secs: 1280, flags: 0
*Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP chaddr: e0:91:53:60:1f:e4
*Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP requested ip: 10.6.2.160
*Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP server id: 10.6.15.254 rcvd server id: 10.6.15.254
*Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP successfully bridged packet to DS
*Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP received op BOOTREPLY (2) (len 308, port 13, encap 0xec00)
*Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP processing DHCP ACK (5)
*Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP xid: 0x9b24c896 (2602879126), secs: 0, flags: 0
*Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP chaddr: e0:91:53:60:1f:e4
*Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP ciaddr: 0.0.0.0, yiaddr: 10.6.2.160
*Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*Apr 15 17:01:43.241: e0:91:53:60:1f:e4 DHCP server id: 10.6.15.254 rcvd server id: 10.6.15.254
*Apr 15 17:01:43.242: e0:91:53:60:1f:e4 10.6.2.160 DHCP_REQD (7) Change state to RUN (20) last state RUN (20)
*Apr 15 17:01:43.242: e0:91:53:60:1f:e4 10.6.2.160 RUN (20) Reached PLUMBFASTPATH: from line 4972
*Apr 15 17:01:43.242: e0:91:53:60:1f:e4 10.6.2.160 RUN (20) Replacing Fast Path rule
type = Airespace AP Client
on AP b8:62:1f:e9:9f:30, slot 0, interface = 13, QOS = 0
ACL Id = 255, Jumbo Frames = NO,
*Apr 15 17:01:43.242: e0:91:53:60:1f:e4 10.6.2.160 RUN (20) Successfully plumbed mobile rule (ACL ID 255)
*Apr 15 17:01:43.242: e0:91:53:60:1f:e4 Assigning Address 10.6.2.160 to mobile
*Apr 15 17:01:43.242: e0:91:53:60:1f:e4 DHCP successfully bridged packet to STA
*Apr 15 17:01:43.242: e0:91:53:60:1f:e4 10.6.2.160 Added NPU entry of type 1, dtlFlags 0x0
*Apr 15 17:01:43.242: e0:91:53:60:1f:e4 Sending a gratuitous ARP for 10.6.2.160, VLAN Id 15
*Apr 15 17:01:46.428: e0:91:53:60:1f:e4 DHCP received op BOOTREQUEST (1) (len 308, port 13, encap 0xec03)
*Apr 15 17:01:46.428: e0:91:53:60:1f:e4 DHCP processing DHCP INFORM (8)
*Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP xid: 0xbb0d5d87 (3138215303), secs: 0, flags: 0
*Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP chaddr: e0:91:53:60:1f:e4
*Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP ciaddr: 10.6.2.160, yiaddr: 0.0.0.0
*Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP successfully bridged packet to DS
*Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP received op BOOTREPLY (2) (len 308, port 13, encap 0xec00)
*Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP processing DHCP ACK (5)
*Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP xid: 0xbb0d5d87 (3138215303), secs: 0, flags: 0
*Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP chaddr: e0:91:53:60:1f:e4
*Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP ciaddr: 10.6.2.160, yiaddr: 0.0.0.0
*Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*Apr 15 17:01:46.429: e0:91:53:60:1f:e4 DHCP server id: 10.6.15.254 rcvd server id: 10.6.15.254
show client e0:91:53:60:1f:e4 (after re-connect)
(Cisco Controller) >show client detail e0:91:53:60:1f:e4
Client MAC Address............................... e0:91:53:60:1f:e4
Client Username ................................. N/A
AP MAC Address................................... b8:62:1f:e9:9f:30
Client State..................................... Associated
Client NAC OOB State............................. Access
Wireless LAN Id.................................. 7
BSSID............................................ b8:62:1f:e9:9f:31
Connected For ................................... 105 secs
Channel.......................................... 11
IP Address....................................... 10.6.2.160
Association Id................................... 8
Authentication Algorithm......................... Open System
Reason Code...................................... 1
Status Code...................................... 0
Session Timeout.................................. 65535
Client CCX version............................... No CCX support
QoS Level........................................ Silver
Diff Serv Code Point (DSCP)...................... disabled
802.1P Priority Tag.............................. disabled
WMM Support...................................... Enabled
U-APSD Support................................... Disabled
Power Save....................................... OFF
Current Rate..................................... m7
Supported Rates.................................. 1.0,2.0,5.5,11.0,6.0,9.0,
............................................. 12.0,18.0,24.0,36.0,48.0,
............................................. 54.0
Mobility State................................... Local
Mobility Move Count.............................. 0
Security Policy Completed........................ Yes
Policy Manager State............................. RUN
Policy Manager Rule Created...................... Yes
ACL Name......................................... none
ACL Applied Status............................... Unavailable
Policy Type...................................... N/A
Encryption Cipher................................ None
Management Frame Protection...................... No
EAP Type......................................... Unknown
Interface........................................ students
VLAN............................................. 15
Quarantine VLAN.................................. 0
Access VLAN...................................... 15
Client Capabilities:
CF Pollable................................ Not implemented
CF Poll Request............................ Not implemented
Short Preamble............................. Implemented
PBCC....................................... Not implemented
Channel Agility............................ Not implemented
Listen Interval............................ 1
Fast BSS Transition........................ Not implemented
Fast BSS Transition Details:
Client Statistics:
Number of Bytes Received................... 36509
Number of Bytes Sent....................... 32902
Number of Packets Received................. 300
Number of Packets Sent..................... 66
Number of EAP Id Request Msg Timeouts...... 0
Number of EAP Request Msg Timeouts......... 0
Number of EAP Key Msg Timeouts............. 0
Number of Data Retries..................... 95
Number of RTS Retries...................... 0
Number of Duplicate Received Packets....... 1
Number of Decrypt Failed Packets........... 0
Number of Mic Failured Packets............. 0
Number of Mic Missing Packets.............. 0
Number of Policy Errors.................... 0
Radio Signal Strength Indicator............ -66 dBm
Signal to Noise Ratio...................... 29 dB
Nearby AP Statistics:
APSOEBFF_COR3(slot 0) .....................
antenna0: 50 seconds ago -91 dBm................. antenna1: 50 seconds ago -76 dBm
APSOEAFF_FAC(slot 0) ......................
antenna0: 108 seconds ago -89 dBm................ antenna1: 108 seconds ago -87 dBm
APSOEBGF_FAC(slot 0) ......................
antenna0: 50 seconds ago -82 dBm................. antenna1: 50 seconds ago -71 dBm
APSOEBGF_STAFF(slot 0) ....................
antenna0: 49 seconds ago -74 dBm................. antenna1: 49 seconds ago -58 dBm
WLAN config
WLAN Identifier.................................. 9
Profile Name..................................... STAFF
Network Name (SSID).............................. STAFF
Status........................................... Enabled
MAC Filtering.................................... Enabled
Broadcast SSID................................... Enabled
AAA Policy Override.............................. Disabled
Network Admission Control
NAC-State...................................... Disabled
Quarantine VLAN................................ 0
Number of Active Clients......................... 32
Exclusionlist.................................... Disabled
Session Timeout.................................. Infinity
CHD per WLAN..................................... Disabled
Webauth DHCP exclusion........................... Disabled
Interface........................................ staff
WLAN ACL......................................... unconfigured
DHCP Server...................................... Default
DHCP Address Assignment Required................. Disabled
Quality of Service............................... Silver (best effort)
Scan Defer Priority.............................. 5,6
Scan Defer Time.................................. 100 milliseconds
WMM.............................................. Allowed
Media Stream Multicast-direct.................... Disabled
CCX - AironetIe Support.......................... Enabled
CCX - Gratuitous ProbeResponse (GPR)............. Disabled
CCX - Diagnostics Channel Capability............. Disabled
Dot11-Phone Mode (7920).......................... Disabled
Wired Protocol................................... None
IPv6 Support..................................... Disabled
Peer-to-Peer Blocking Action..................... Disabled
Radio Policy..................................... All
DTIM period for 802.11a radio.................... 1
DTIM period for 802.11b radio.................... 1
Radius Servers
Authentication................................ Disabled
Accounting.................................... Disabled
Dynamic Interface............................. Disabled
Local EAP Authentication......................... Disabled
Security
802.11 Authentication:........................ Open System
Static WEP Keys............................... Disabled
802.1X........................................ Disabled
Wi-Fi Protected Access (WPA/WPA2)............. Disabled
CKIP ......................................... Disabled
Web Based Authentication...................... Disabled
Web-Passthrough............................... Disabled
Conditional Web Redirect...................... Disabled
Splash-Page Web Redirect...................... Disabled
Auto Anchor................................... Disabled
H-REAP Local Switching........................ Disabled
H-REAP Learn IP Address....................... Enabled
Infrastructure MFP protection................. Enabled (Global Infrastructure MFP Disabled)
Client MFP.................................... Optional but inactive (WPA2 not configured)
Tkip MIC Countermeasure Hold-down Timer....... 60
Call Snooping.................................... Disabled
Band Select...................................... Disabled
Load Balancing................................... Disabled
HELPPPP!We have 75 evenly distributed AP's servicing the 500 odd users. Found the below traps on WLC. I was making some changes in the WLAN settings at the time:
Tue Apr 16 00:03:45 2013 Client Excluded: MACAddress:8c:a9:82:5d:d2:dc Base Radio MAC :3c:ce:73:c6:fe:00 Slot: 0 User Name: unknown Ip Address: unknown Reason:802.11 Association failed repeatedly. ReasonCode: 2
106 Tue Apr 16 00:03:45 2013 Client Excluded: MACAddress:58:94:6b:f2:24:c8 Base Radio MAC :c8:f9:f9:4c:01:30 Slot: 1 User Name: unknown Ip Address: unknown Reason:802.11 Association failed repeatedly. ReasonCode: 2
107 Tue Apr 16 00:03:45 2013 Client Excluded: MACAddress:bc:77:37:72:dc:0b Base Radio MAC :3c:ce:73:c6:53:10 Slot: 0 User Name: unknown Ip Address: unknown Reason:802.11 Association failed repeatedly. ReasonCode: 2
108 Tue Apr 16 00:03:45 2013 Client Excluded: MACAddress:00:26:c7:7d:12:76 Base Radio MAC :3c:ce:73:c4:79:80 Slot: 0 User Name: unknown Ip Address: unknown Reason:802.11 Association failed repeatedly. ReasonCode: 2
109 Tue Apr 16 00:03:45 2013 Client Excluded: MACAddress:bc:77:37:75:1f:93 Base Radio MAC :c8:f9:f9:2b:85:30 Slot: 0 User Name: unknown Ip Address: unknown Reason:802.11 Association failed repeatedly. ReasonCode: 2
110 Tue Apr 16 00:03:45 2013 Client Excluded: MACAddress:ac:72:89:58:8e:b9 Base Radio MAC :3c:ce:73:c6:53:10 Slot: 0 User Name: unknown Ip Address: unknown Reason:802.11 Association failed repeatedly. ReasonCode: 2
111 Tue Apr 16 00:03:44 2013 Client Excluded: MACAddress:bc:77:37:26:cd:e3 Base Radio MAC :3c:ce:73:c5:1f:10 Slot: 0 User Name: unknown Ip Address: unknown Reason:802.11 Association failed repeatedly. ReasonCode: 2
112 Tue Apr 16 00:03:44 2013 Client Excluded: MACAddress:ac:72:89:25:ea:e0 Base Radio MAC :3c:ce:73:c6:77:70 Slot: 0 User Name: unknown Ip Address: unknown Reason:802.11 Association failed repeatedly. ReasonCode: 2
113 Tue Apr 16 00:03:44 2013 Client Excluded: MACAddress:00:24:2c:6a:85:3d Base Radio MAC :3c:ce:73:c6:6a:50 Slot: 0 User Name: unknown Ip Address: unknown Reason:802.11 Association failed repeatedly. ReasonCode: 2
114 Tue Apr 16 00:03:44 2013 Client Excluded: MACAddress:68:5d:43:61:16:51 Base Radio MAC :3c:ce:73:f6:0c:20 Slot: 0 User Name: unknown Ip Address: unknown Reason:802.11 Association failed repeatedly. ReasonCode: 2
115 Tue Apr 16 00:03:44 2013 Client Excluded: MACAddress:7c:d1:c3:8a:64:f6 Base Radio MAC :3c:ce:73:c4:74:20 Slot: 1 User Name: unknown Ip Address: unknown Reason:802.11 Association failed repeatedly. ReasonCode: 2 -
SINGLE SCCM UPDATE STUCK AT DOWNLOADING 0% COMPLETE
I'm posting this because while there are multiple threads on the Internet about all patches on a client stuck at "downloading 0% complete", there's very little on when only one patch is stuck there network-wide. This was the "Windows Malicious
Software Removal Tool for Windows 8, 8.1 and Windows Server 2013, 2012 R2 x64 Edition - September 2014 (KB890830)". On this network it would not download on any machine. Other versions of the Sept 2014 version of 890830 did install, so it was clearly
something specific to this version of that update. After awhile, I decided to try something that worked for me: Delete the deployment that applies to the machine in question, update distribution points from the package in question, run Machine Policy on the
box in question, wait til the update clears off the Software Center screen, and then run Machine Policy and Software Updates Deployment on the Actions tab. Then the patch installed fine. Hope this helps someone else!
Ben JohnsonWYI just figured this out while typing this. One of the suggested threads that appeared when I was typing lead me to the answer for my case. The IIS App Pool for DPs was using an account that did not have rights to particular folder. Some security setting
pushed by the security server changed something. I changed to App Pool to an account that had the needed rights, restarted IIS, and the downloads started working. Maybe this will fix my secondary DP problem too.
Ben JohnsonWY
Maybe you are looking for
-
How to pass a variable value to an inner class?
Hi there, Please have a look of the code below. It's a bit long, but my concern is I did have to declare the int "i" variable as static because it is used by an inner class (if "i" is not declare as static, the code cannot be compiled). Is there a mo
-
Adobe Media Encoder CS5.5 (5.5.1) update available
The Adobe Media Encoder CS5.5 (5.5.1) update is available. This update fixes a few major bugs. After you've installed the update, let us know how it works for you.
-
RE: Firefox search box -> manage search engines -> get more search engines.. IT DOESN'T WORK I just want to add youtube + some others to the list of sites in the Firefox search box, I now get 1000's of useless irrelevant results, PLEASE FIX THE SITES
-
Problems replacing email-subject with SAPConnect
Hi there, I'm sending an order confirmation via SAPConnect as email. The order confirmation attaches the email as a *.PDF file. Now i'd like to replace the standard subject, that consists in the spool-number and some text from the message i use. So,
-
I'm trying to get to the Ultra Search home page, however the following link: http://otn.oracle.com/products/ultrasearch/index.html brings up Oracle Warehouse Builder 10g.