Max EAPOL-key M1 retransmissions exceeded for client
WISMS on ver 6.0.196
Receiving several hundred messages:
*Jul 06 16:51:58.943: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:407 Max EAPOL-key M1 retransmissions exceeded for client 00:19:88:05:2d:53
*Jul 06 16:51:57.792: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:407 Max EAPOL-key M5 retransmissions exceeded for client 00:40:9d:3a:c9:8f
*Jul 06 16:51:56.991: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:407 Max EAPOL-key M1 retransmissions exceeded for client 00:19:88:06:64:82
Any thoughts? Wireless users are experiencing random disconnects.
In looking at the radius configuration again I notice that we have two servers defined. I looked through the logs and didn't see anything alarming, until I checked the secondary radius server. I was just told that the second radius server has been shutdown without notice.
I will remove that from the WLAN config later tonight.
Obvious question, but will ask it anyway, will this cause these errors?
Similar Messages
-
FT akm with 802.1x authentication failed at eapol key 2(invalid MIC)
My testing controller s/w version is 7.0.250.0, and testing clients were iphone5, iphone6 and macbook pro13, all debug inform showed failed because of invalid MIC, is this a bug or other reason ?
WLAN configuration:
(Cisco Controller) >show wlan 100
WLAN Identifier.................................. 100
Profile Name..................................... test-qh
Network Name (SSID).............................. test-qh
Status........................................... Enabled
MAC Filtering.................................... Disabled
Broadcast SSID................................... Enabled
AAA Policy Override.............................. Disabled
Network Admission Control
Radius-NAC State............................... Disabled
SNMP-NAC State................................. Disabled
Quarantine VLAN................................ 0
Maximum number of Associated Clients............. 10
Number of Active Clients......................... 0
Exclusionlist Timeout............................ 60 seconds
Session Timeout.................................. 1800 seconds
CHD per WLAN..................................... Enabled
Webauth DHCP exclusion........................... Disabled
Interface........................................ management
Multicast Interface.............................. Not Configured
--More-- or (q)uit
WLAN ACL......................................... unconfigured
DHCP Server...................................... Default
DHCP Address Assignment Required................. Disabled
Static IP client tunneling....................... Disabled
Quality of Service............................... Silver (best effort)
Scan Defer Priority.............................. 4,5,6
Scan Defer Time.................................. 100 milliseconds
WMM.............................................. Allowed
WMM UAPSD Compliant Client Support............... Disabled
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.................................... Global Servers
--More-- or (q)uit
Dynamic Interface............................. Disabled
Local EAP Authentication......................... Enabled (Profile 'test')
Security
802.11 Authentication:........................ Open System
Static WEP Keys............................... Disabled
802.1X........................................ Disabled
Wi-Fi Protected Access (WPA/WPA2)............. Enabled
WPA (SSN IE)............................... Disabled
WPA2 (RSN IE).............................. Enabled
TKIP Cipher............................. Disabled
AES Cipher.............................. Enabled
Auth Key Management
802.1x.................................. Disabled
PSK..................................... Disabled
CCKM.................................... Disabled
FT(802.11r)............................. Enabled
FT-PSK(802.11r)......................... Disabled
FT Reassociation Timeout......................... 20
FT Over-The-Air mode............................. Enabled
FT Over-The-Ds mode.............................. Disabled
CCKM tsf Tolerance............................... 1000
CKIP ......................................... Disabled
--More-- or (q)uit
IP Security................................... Disabled
IP Security Passthru.......................... 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 Local Authentication................... Disabled
H-REAP Learn IP Address....................... Enabled
Client MFP.................................... Optional
Tkip MIC Countermeasure Hold-down Timer....... 60
Call Snooping.................................... Disabled
Roamed Call Re-Anchor Policy..................... Disabled
SIP CAC Fail Send-486-Busy Policy................ Enabled
SIP CAC Fail Send Dis-Association Policy......... Disabled
Band Select...................................... Disabled
Load Balancing................................... Disabled
Mobility Anchor List
WLAN ID IP Address Status
debug info:
Cisco Controller) >*apfMsConnTask_0: Apr 27 21:46:09.971: Processing assoc-req station:68:96:7b:cd:89:1b AP:00:27:0d:2e:d0:50-01 thread:333140024
*apfMsConnTask_0: Apr 27 21:46:09.971: 68:96:7b:cd:89:1b Marking this mobile as TGr capable.
*apfMsConnTask_0: Apr 27 21:46:09.971: 68:96:7b:cd:89:1b Processing RSN IE type 48, length 20 for mobile 68:96:7b:cd:89:1b
*apfMsConnTask_0: Apr 27 21:46:09.971: 68:96:7b:cd:89:1b apfMsAssoStateInc
*apfMsConnTask_0: Apr 27 21:46:09.971: Sending assoc-resp station:68:96:7b:cd:89:1b AP:00:27:0d:2e:d0:50-01 thread:333140024
*apfMsConnTask_0: Apr 27 21:46:09.971: Adding MDIE, ID is:0x4e57
*apfMsConnTask_0: Apr 27 21:46:09.971: 68:96:7b:cd:89:1b Including FT Mobility Domain IE (length 5) in Initial assoc Resp to mobile
*apfMsConnTask_0: Apr 27 21:46:09.971: 68:96:7b:cd:89:1b Sending R0KH-ID as:192.168.20.244
*apfMsConnTask_0: Apr 27 21:46:09.971: 68:96:7b:cd:89:1b Sending R1KH-ID as 00:24:14:7e:74:c0
*apfMsConnTask_0: Apr 27 21:46:09.971: 68:96:7b:cd:89:1b Including FT IE (length 98) in Initial Assoc Resp to mobile
*spamReceiveTask: Apr 27 21:46:09.973: 68:96:7b:cd:89:1b Sent 1x initiate message to multi thread task for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:09.974: 68:96:7b:cd:89:1b Station 68:96:7b:cd:89:1b setting dot1x reauth timeout = 1800
*Dot1x_NW_MsgTask_0: Apr 27 21:46:09.974: 68:96:7b:cd:89:1b Sending EAP-Request/Identity to mobile 68:96:7b:cd:89:1b (EAP Id 1)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.037: 68:96:7b:cd:89:1b Received EAPOL EAPPKT from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.037: 68:96:7b:cd:89:1b Received Identity Response (count=1) from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.117: 68:96:7b:cd:89:1b Processing Access-Challenge for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.117: 68:96:7b:cd:89:1b Sending EAP Request from AAA to mobile 68:96:7b:cd:89:1b (EAP Id 2)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.133: 68:96:7b:cd:89:1b Received EAPOL EAPPKT from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.133: 68:96:7b:cd:89:1b Received EAP Response from mobile 68:96:7b:cd:89:1b (EAP Id 2, EAP Type 25)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.135: 68:96:7b:cd:89:1b Processing Access-Challenge for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.135: 68:96:7b:cd:89:1b Sending EAP Request from AAA to mobile 68:96:7b:cd:89:1b (EAP Id 3)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.139: 68:96:7b:cd:89:1b Received EAPOL EAPPKT from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.139: 68:96:7b:cd:89:1b Received EAP Response from mobile 68:96:7b:cd:89:1b (EAP Id 3, EAP Type 25)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.140: 68:96:7b:cd:89:1b Processing Access-Challenge for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.140: 68:96:7b:cd:89:1b Sending EAP Request from AAA to mobile 68:96:7b:cd:89:1b (EAP Id 4)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.200: 68:96:7b:cd:89:1b Received EAPOL EAPPKT from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.201: 68:96:7b:cd:89:1b Received EAP Response from mobile 68:96:7b:cd:89:1b (EAP Id 4, EAP Type 25)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.309: 68:96:7b:cd:89:1b Processing Access-Challenge for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.309: 68:96:7b:cd:89:1b Sending EAP Request from AAA to mobile 68:96:7b:cd:89:1b (EAP Id 5)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.312: 68:96:7b:cd:89:1b Received EAPOL EAPPKT from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.313: 68:96:7b:cd:89:1b Received EAP Response from mobile 68:96:7b:cd:89:1b (EAP Id 5, EAP Type 25)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.314: 68:96:7b:cd:89:1b Processing Access-Challenge for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.314: 68:96:7b:cd:89:1b Sending EAP Request from AAA to mobile 68:96:7b:cd:89:1b (EAP Id 6)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.321: 68:96:7b:cd:89:1b Received EAPOL EAPPKT from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.321: 68:96:7b:cd:89:1b Received EAP Response from mobile 68:96:7b:cd:89:1b (EAP Id 6, EAP Type 25)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.322: 68:96:7b:cd:89:1b Processing Access-Challenge for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.322: 68:96:7b:cd:89:1b Sending EAP Request from AAA to mobile 68:96:7b:cd:89:1b (EAP Id 7)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.325: 68:96:7b:cd:89:1b Received EAPOL EAPPKT from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.325: 68:96:7b:cd:89:1b Received EAP Response from mobile 68:96:7b:cd:89:1b (EAP Id 7, EAP Type 25)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.326: 68:96:7b:cd:89:1b Processing Access-Challenge for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.326: 68:96:7b:cd:89:1b Sending EAP Request from AAA to mobile 68:96:7b:cd:89:1b (EAP Id 8)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.329: 68:96:7b:cd:89:1b Received EAPOL EAPPKT from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.329: 68:96:7b:cd:89:1b Received EAP Response from mobile 68:96:7b:cd:89:1b (EAP Id 8, EAP Type 25)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.331: 68:96:7b:cd:89:1b Processing Access-Accept for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.331: 68:96:7b:cd:89:1b Setting re-auth timeout to 1800 seconds, got from WLAN config.
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.332: 68:96:7b:cd:89:1b Station 68:96:7b:cd:89:1b setting dot1x reauth timeout = 1800
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.332: 68:96:7b:cd:89:1b Creating a PKC PMKID Cache entry for station 68:96:7b:cd:89:1b (RSN 2)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.332: 68:96:7b:cd:89:1b Adding BSSID 00:27:0d:2e:d0:5e to PMKID cache for station 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.332: New PMKID: (16)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.332: [0000] 80 a9 e3 16 d9 c8 28 9a 37 11 bd 56 ca 01 d5 ce
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.332: 68:96:7b:cd:89:1b Disabling re-auth since PMK lifetime can take care of same.
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.332: 68:96:7b:cd:89:1b Created PMK Cache Entry for TGr AKM:802.1x 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.332: 68:96:7b:cd:89:1b R0KH-ID:192.168.20.244 R1KH-ID:00:24:14:7e:74:c0 MSK Len:48
pmkValidTime:1772
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.333: 68:96:7b:cd:89:1b PMK sent to mobility group
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.333: 68:96:7b:cd:89:1b Sending EAP-Success to mobile 68:96:7b:cd:89:1b (EAP Id 8)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.333: Including PMKID in M1 (16)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.333: [0000] 80 a9 e3 16 d9 c8 28 9a 37 11 bd 56 ca 01 d5 ce
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.333: 68:96:7b:cd:89:1b Starting key exchange to mobile 68:96:7b:cd:89:1b, data packets will be dropped
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.333: 68:96:7b:cd:89:1b Sending EAPOL-Key Message to mobile 68:96:7b:cd:89:1b
state INITPMK (message 1), replay counter 00.00.00.00.00.00.00.00
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.333: 68:96:7b:cd:89:1b Received Auth Success while in Authenticating state for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.336: 68:96:7b:cd:89:1b Received EAPOL-Key from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.336: 68:96:7b:cd:89:1b Received EAPOL-key in PTK_START state (message 2) from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.337: 68:96:7b:cd:89:1b Received EAPOL-key M2 with invalid MIC from mobile 68:96:7b:cd:89:1b
*osapiBsnTimer: Apr 27 21:46:10.560: 68:96:7b:cd:89:1b 802.1x 'timeoutEvt' Timer expired for station 68:96:7b:cd:89:1b and for message = M2
*dot1xMsgTask: Apr 27 21:46:10.562: 68:96:7b:cd:89:1b Retransmit 1 of EAPOL-Key M1 (length 121) for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.565: 68:96:7b:cd:89:1b Received EAPOL-Key from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.565: 68:96:7b:cd:89:1b Received EAPOL-key in PTK_START state (message 2) from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:10.566: 68:96:7b:cd:89:1b Received EAPOL-key M2 with invalid MIC from mobile 68:96:7b:cd:89:1b
*osapiBsnTimer: Apr 27 21:46:10.960: 68:96:7b:cd:89:1b 802.1x 'timeoutEvt' Timer expired for station 68:96:7b:cd:89:1b and for message = M2
*dot1xMsgTask: Apr 27 21:46:10.960: 68:96:7b:cd:89:1b Retransmit 2 of EAPOL-Key M1 (length 121) for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:11.048: 68:96:7b:cd:89:1b Received EAPOL-Key from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:11.048: 68:96:7b:cd:89:1b Received EAPOL-key in PTK_START state (message 2) from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:11.048: 68:96:7b:cd:89:1b Received EAPOL-key M2 with invalid MIC from mobile 68:96:7b:cd:89:1b
*osapiBsnTimer: Apr 27 21:46:11.360: 68:96:7b:cd:89:1b 802.1x 'timeoutEvt' Timer expired for station 68:96:7b:cd:89:1b and for message = M2
*dot1xMsgTask: Apr 27 21:46:11.360: 68:96:7b:cd:89:1b Retransmit 3 of EAPOL-Key M1 (length 121) for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:11.364: 68:96:7b:cd:89:1b Received EAPOL-Key from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:11.364: 68:96:7b:cd:89:1b Received EAPOL-key in PTK_START state (message 2) from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:11.364: 68:96:7b:cd:89:1b Received EAPOL-key M2 with invalid MIC from mobile 68:96:7b:cd:89:1b
*osapiBsnTimer: Apr 27 21:46:11.760: 68:96:7b:cd:89:1b 802.1x 'timeoutEvt' Timer expired for station 68:96:7b:cd:89:1b and for message = M2
*dot1xMsgTask: Apr 27 21:46:11.760: 68:96:7b:cd:89:1b Retransmit 4 of EAPOL-Key M1 (length 121) for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:11.763: 68:96:7b:cd:89:1b Received EAPOL-Key from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:11.764: 68:96:7b:cd:89:1b Received EAPOL-key in PTK_START state (message 2) from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:11.764: 68:96:7b:cd:89:1b Received EAPOL-key M2 with invalid MIC from mobile 68:96:7b:cd:89:1b
*osapiBsnTimer: Apr 27 21:46:12.160: 68:96:7b:cd:89:1b 802.1x 'timeoutEvt' Timer expired for station 68:96:7b:cd:89:1b and for message = M2
*dot1xMsgTask: Apr 27 21:46:12.161: 68:96:7b:cd:89:1b Retransmit failure for EAPOL-Key M1 to mobile 68:96:7b:cd:89:1b, retransmit count 5, mscb deauth count 0
*dot1xMsgTask: Apr 27 21:46:12.162: 68:96:7b:cd:89:1b Removing PMK cache entry for station 68:96:7b:cd:89:1b
*apfMsConnTask_0: Apr 27 21:46:12.185: Processing assoc-req station:68:96:7b:cd:89:1b AP:00:27:0d:2e:d0:50-01 thread:333140024
*apfMsConnTask_0: Apr 27 21:46:12.185: 68:96:7b:cd:89:1b Marking this mobile as TGr capable.
*apfMsConnTask_0: Apr 27 21:46:12.185: 68:96:7b:cd:89:1b Processing RSN IE type 48, length 20 for mobile 68:96:7b:cd:89:1b
*apfMsConnTask_0: Apr 27 21:46:12.185: Sending assoc-resp station:68:96:7b:cd:89:1b AP:00:27:0d:2e:d0:50-01 thread:333140024
*apfMsConnTask_0: Apr 27 21:46:12.185: Adding MDIE, ID is:0x4e57
*apfMsConnTask_0: Apr 27 21:46:12.185: 68:96:7b:cd:89:1b Including FT Mobility Domain IE (length 5) in Initial assoc Resp to mobile
*apfMsConnTask_0: Apr 27 21:46:12.185: 68:96:7b:cd:89:1b Sending R0KH-ID as:192.168.20.244
*apfMsConnTask_0: Apr 27 21:46:12.185: 68:96:7b:cd:89:1b Sending R1KH-ID as 00:24:14:7e:74:c0
*apfMsConnTask_0: Apr 27 21:46:12.185: 68:96:7b:cd:89:1b Including FT IE (length 98) in Initial Assoc Resp to mobile
*spamReceiveTask: Apr 27 21:46:12.187: 68:96:7b:cd:89:1b Sent 1x initiate message to multi thread task for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:12.188: 68:96:7b:cd:89:1b Station 68:96:7b:cd:89:1b setting dot1x reauth timeout = 1800
*Dot1x_NW_MsgTask_0: Apr 27 21:46:12.188: 68:96:7b:cd:89:1b Sending EAP-Request/Identity to mobile 68:96:7b:cd:89:1b (EAP Id 1)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:12.191: 68:96:7b:cd:89:1b Received EAPOL EAPPKT from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:12.191: 68:96:7b:cd:89:1b Received Identity Response (count=1) from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:12.271: 68:96:7b:cd:89:1b Processing Access-Challenge for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:12.271: 68:96:7b:cd:89:1b Sending EAP Request from AAA to mobile 68:96:7b:cd:89:1b (EAP Id 2)
*apfMsConnTask_0: Apr 27 21:46:12.563: Processing assoc-req station:68:96:7b:cd:89:1b AP:00:27:0d:2e:d0:50-01 thread:333140024
*apfMsConnTask_0: Apr 27 21:46:12.563: 68:96:7b:cd:89:1b Marking this mobile as TGr capable.
*apfMsConnTask_0: Apr 27 21:46:12.563: 68:96:7b:cd:89:1b Processing RSN IE type 48, length 20 for mobile 68:96:7b:cd:89:1b
*apfMsConnTask_0: Apr 27 21:46:12.563: Sending assoc-resp station:68:96:7b:cd:89:1b AP:00:27:0d:2e:d0:50-01 thread:333140024
*apfMsConnTask_0: Apr 27 21:46:12.563: Adding MDIE, ID is:0x4e57
*apfMsConnTask_0: Apr 27 21:46:12.563: 68:96:7b:cd:89:1b Including FT Mobility Domain IE (length 5) in Initial assoc Resp to mobile
*apfMsConnTask_0: Apr 27 21:46:12.563: 68:96:7b:cd:89:1b Sending R0KH-ID as:192.168.20.244
*apfMsConnTask_0: Apr 27 21:46:12.563: 68:96:7b:cd:89:1b Sending R1KH-ID as 00:24:14:7e:74:c0
*apfMsConnTask_0: Apr 27 21:46:12.563: 68:96:7b:cd:89:1b Including FT IE (length 98) in Initial Assoc Resp to mobile
*spamReceiveTask: Apr 27 21:46:12.565: 68:96:7b:cd:89:1b Sent 1x initiate message to multi thread task for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:12.566: 68:96:7b:cd:89:1b Sending EAP-Request/Identity to mobile 68:96:7b:cd:89:1b (EAP Id 1)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:12.571: 68:96:7b:cd:89:1b Received EAPOL EAPPKT from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:12.571: 68:96:7b:cd:89:1b Received Identity Response (count=1) from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:12.572: 68:96:7b:cd:89:1b Processing Access-Reject for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:12.573: 68:96:7b:cd:89:1b Removing PMK cache due to EAP-Failure for mobile 68:96:7b:cd:89:1b (EAP Id -1)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:12.573: 68:96:7b:cd:89:1b Sending EAP-Failure to mobile 68:96:7b:cd:89:1b (EAP Id -1)
(Cisco Controller) >*Dot1x_NW_MsgTask_0: Apr 27 21:46:12.573: 68:96:7b:cd:89:1b Setting quiet timer for 5 seconds for mobile 68:96:7b:cd:89:1b
*osapiBsnTimer: Apr 27 21:46:17.560: 68:96:7b:cd:89:1b 802.1x 'quiteWhile' Timer expired for station 68:96:7b:cd:89:1b and for message = M0
*dot1xMsgTask: Apr 27 21:46:17.561: 68:96:7b:cd:89:1b quiet timer completed for mobile 68:96:7b:cd:89:1b
*dot1xMsgTask: Apr 27 21:46:17.561: 68:96:7b:cd:89:1b Sending EAP-Request/Identity to mobile 68:96:7b:cd:89:1b (EAP Id 1)
(Cisco Controller) >*apfMsConnTask_0: Apr 27 21:46:19.793: Processing assoc-req station:68:96:7b:cd:89:1b AP:00:27:0d:2e:d0:50-01 thread:333140024
*apfMsConnTask_0: Apr 27 21:46:19.793: 68:96:7b:cd:89:1b Marking this mobile as TGr capable.
*apfMsConnTask_0: Apr 27 21:46:19.793: 68:96:7b:cd:89:1b Processing RSN IE type 48, length 20 for mobile 68:96:7b:cd:89:1b
*apfMsConnTask_0: Apr 27 21:46:19.793: Sending assoc-resp station:68:96:7b:cd:89:1b AP:00:27:0d:2e:d0:50-01 thread:333140024
*apfMsConnTask_0: Apr 27 21:46:19.793: Adding MDIE, ID is:0x4e57
*apfMsConnTask_0: Apr 27 21:46:19.793: 68:96:7b:cd:89:1b Including FT Mobility Domain IE (length 5) in Initial assoc Resp to mobile
*apfMsConnTask_0: Apr 27 21:46:19.793: 68:96:7b:cd:89:1b Sending R0KH-ID as:192.168.20.244
*apfMsConnTask_0: Apr 27 21:46:19.793: 68:96:7b:cd:89:1b Sending R1KH-ID as 00:24:14:7e:74:c0
*apfMsConnTask_0: Apr 27 21:46:19.793: 68:96:7b:cd:89:1b Including FT IE (length 98) in Initial Assoc Resp to mobile
*spamReceiveTask: Apr 27 21:46:19.796: 68:96:7b:cd:89:1b Sent 1x initiate message to multi thread task for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:19.798: 68:96:7b:cd:89:1b Sending EAP-Request/Identity to mobile 68:96:7b:cd:89:1b (EAP Id 1)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:19.825: 68:96:7b:cd:89:1b Received EAPOL EAPPKT from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:19.826: 68:96:7b:cd:89:1b Received Identity Response (count=1) from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:19.905: 68:96:7b:cd:89:1b Processing Access-Challenge for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:19.905: 68:96:7b:cd:89:1b Sending EAP Request from AAA to mobile 68:96:7b:cd:89:1b (EAP Id 2)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:19.918: 68:96:7b:cd:89:1b Received EAPOL EAPPKT from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:19.918: 68:96:7b:cd:89:1b Received EAP Response from mobile 68:96:7b:cd:89:1b (EAP Id 2, EAP Type 25)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:19.920: 68:96:7b:cd:89:1b Processing Access-Challenge for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:19.920: 68:96:7b:cd:89:1b Sending EAP Request from AAA to mobile 68:96:7b:cd:89:1b (EAP Id 3)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:19.923: 68:96:7b:cd:89:1b Received EAPOL EAPPKT from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:19.924: 68:96:7b:cd:89:1b Received EAP Response from mobile 68:96:7b:cd:89:1b (EAP Id 3, EAP Type 25)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:19.924: 68:96:7b:cd:89:1b Processing Access-Challenge for mobile 68:96:7b:cd:89:1b
d*Dot1x_NW_MsgTask_0: Apr 27 21:46:19.925: 68:96:7b:cd:89:1b Sending EAP Request from AAA to mobile 68:96:7b:cd:89:1b (EAP Id 4)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:19.964: 68:96:7b:cd:89:1b Received EAPOL EAPPKT from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:19.964: 68:96:7b:cd:89:1b Received EAP Response from mobile 68:96:7b:cd:89:1b (EAP Id 4, EAP Type 25)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.073: 68:96:7b:cd:89:1b Processing Access-Challenge for mobile 68:96:7b:cd:89:1b
e*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.073: 68:96:7b:cd:89:1b Sending EAP Request from AAA to mobile 68:96:7b:cd:89:1b (EAP Id 5)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.076: 68:96:7b:cd:89:1b Received EAPOL EAPPKT from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.076: 68:96:7b:cd:89:1b Received EAP Response from mobile 68:96:7b:cd:89:1b (EAP Id 5, EAP Type 25)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.077: 68:96:7b:cd:89:1b Processing Access-Challenge for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.077: 68:96:7b:cd:89:1b Sending EAP Request from AAA to mobile 68:96:7b:cd:89:1b (EAP Id 6)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.083: 68:96:7b:cd:89:1b Received EAPOL EAPPKT from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.083: 68:96:7b:cd:89:1b Received EAP Response from mobile 68:96:7b:cd:89:1b (EAP Id 6, EAP Type 25)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.084: 68:96:7b:cd:89:1b Processing Access-Challenge for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.084: 68:96:7b:cd:89:1b Sending EAP Request from AAA to mobile 68:96:7b:cd:89:1b (EAP Id 7)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.087: 68:96:7b:cd:89:1b Received EAPOL EAPPKT from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.087: 68:96:7b:cd:89:1b Received EAP Response from mobile 68:96:7b:cd:89:1b (EAP Id 7, EAP Type 25)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.088: 68:96:7b:cd:89:1b Processing Access-Challenge for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.088: 68:96:7b:cd:89:1b Sending EAP Request from AAA to mobile 68:96:7b:cd:89:1b (EAP Id 8)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.090: 68:96:7b:cd:89:1b Received EAPOL EAPPKT from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.090: 68:96:7b:cd:89:1b Received EAP Response from mobile 68:96:7b:cd:89:1b (EAP Id 8, EAP Type 25)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.091: 68:96:7b:cd:89:1b Processing Access-Accept for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.091: 68:96:7b:cd:89:1b Setting re-auth timeout to 1800 seconds, got from WLAN config.
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.091: 68:96:7b:cd:89:1b Station 68:96:7b:cd:89:1b setting dot1x reauth timeout = 1800
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.091: 68:96:7b:cd:89:1b Creating a PKC PMKID Cache entry for station 68:96:7b:cd:89:1b (RSN 2)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.091: 68:96:7b:cd:89:1b Adding BSSID 00:27:0d:2e:d0:5e to PMKID cache for station 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.092: New PMKID: (16)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.092: [0000] 16 3d 85 48 73 81 21 c9 dc 14 19 2e 40 65 7c 74
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.092: 68:96:7b:cd:89:1b Disabling re-auth since PMK lifetime can take care of same.
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.092: 68:96:7b:cd:89:1b Created PMK Cache Entry for TGr AKM:802.1x 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.092: 68:96:7b:cd:89:1b R0KH-ID:192.168.20.244 R1KH-ID:00:24:14:7e:74:c0 MSK Len:48
pmkValidTime:1813
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.092: 68:96:7b:cd:89:1b PMK sent to mobility group
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.092: 68:96:7b:cd:89:1b Sending EAP-Success to mobile 68:96:7b:cd:89:1b (EAP Id 8)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.093: Including PMKID in M1 (16)
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.093: [0000] 16 3d 85 48 73 81 21 c9 dc 14 19 2e 40 65 7c 74
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.093: 68:96:7b:cd:89:1b Starting key exchange to mobile 68:96:7b:cd:89:1b, data packets will be dropped
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.093: 68:96:7b:cd:89:1b Sending EAPOL-Key Message to mobile 68:96:7b:cd:89:1b
state INITPMK (message 1), replay counter 00.00.00.00.00.00.00.00
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.093: 68:96:7b:cd:89:1b Received Auth Success while in Authenticating state for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.096: 68:96:7b:cd:89:1b Received EAPOL-Key from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.096: 68:96:7b:cd:89:1b Received EAPOL-key in PTK_START state (message 2) from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.096: 68:96:7b:cd:89:1b Received EAPOL-key M2 with invalid MIC from mobile 68:96:7b:cd:89:1b
*osapiBsnTimer: Apr 27 21:46:20.360: 68:96:7b:cd:89:1b 802.1x 'timeoutEvt' Timer expired for station 68:96:7b:cd:89:1b and for message = M2
*dot1xMsgTask: Apr 27 21:46:20.361: 68:96:7b:cd:89:1b Retransmit 1 of EAPOL-Key M1 (length 121) for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.364: 68:96:7b:cd:89:1b Received EAPOL-Key from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.364: 68:96:7b:cd:89:1b Received EAPOL-key in PTK_START state (message 2) from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.364: 68:96:7b:cd:89:1b Received EAPOL-key M2 with invalid MIC from mobile 68:96:7b:cd:89:1b
bug *osapiBsnTimer: Apr 27 21:46:20.760: 68:96:7b:cd:89:1b 802.1x 'timeoutEvt' Timer expired for station 68:96:7b:cd:89:1b and for message = M2
*dot1xMsgTask: Apr 27 21:46:20.760: 68:96:7b:cd:89:1b Retransmit 2 of EAPOL-Key M1 (length 121) for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.763: 68:96:7b:cd:89:1b Received EAPOL-Key from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.764: 68:96:7b:cd:89:1b Received EAPOL-key in PTK_START state (message 2) from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:20.764: 68:96:7b:cd:89:1b Received EAPOL-key M2 with invalid MIC from mobile 68:96:7b:cd:89:1b
*osapiBsnTimer: Apr 27 21:46:21.160: 68:96:7b:cd:89:1b 802.1x 'timeoutEvt' Timer expired for station 68:96:7b:cd:89:1b and for message = M2
*dot1xMsgTask: Apr 27 21:46:21.160: 68:96:7b:cd:89:1b Retransmit 3 of EAPOL-Key M1 (length 121) for mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:21.164: 68:96:7b:cd:89:1b Received EAPOL-Key from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:21.164: 68:96:7b:cd:89:1b Received EAPOL-key in PTK_START state (message 2) from mobile 68:96:7b:cd:89:1b
*Dot1x_NW_MsgTask_0: Apr 27 21:46:21.164: 68:96:7b:cd:89:1b Received EAPOL-key M2 with invalid MIC from mobile 68:96:7b:cd:89:1b
=============================
qh
thanks in advance!Can anyone help me?
-
Max no of conversation 100 exceed
Hi all,
We are now in SAP R/3 version 4.70 running on Oracle 9.i with HPUX
11.23.Currently we are facing CPIC error that mention about the Error
max no of 100 conversation exceed.
I have read though all the SAP note as show below:
0000074141 Resource Management for tRFC and aRFC
0000314530 Number of RFC/CPIC connections for external clients
0000316877 Maximum number of conversation exceeded
0001054121 The SAP Ecosystem in a Nutshell
And since this RFC connection error is occurs at the jave level,it is the
responsibility of RFC caller to close the connection. A client program opens the connection for calling funtion module(s) and has to close this connection, as soon as this connection is in use any more.
So i would like to know the BAPI Function module so that i can initiate it from the the RFC caller.I hope if possible recommend me a way to terminate this RFC connection in Java.
hereby is the attached screenshot for the error.
http://www.sendspace.com/file/z3qn85
Message was edited by:
yeong kah feiHi,
ideally your application uses client pools. If so, then you have to make sure that after acquiring a client from the connection pool (<client>=JCO.getClient(<poolname)) and executing the RFC's for the given thread, you have to return the client to the pool (JCO.releaseClient(<client>)).
This should be sufficient when using client pools. If you have individual RFC connections not managed via a client pool, then you can close the connection once it's no longer used (jcoClient.disconnect()).
Hope this helps.
Best wishes, harald -
I'm working on with a customer on a 2106 controller with 1130 series ap's. Everyting seems fine until the client does a reauthentication. At this point the clients send a stream of authentication attempts to the RADIUS server (40 or so a second). The RADIUS (Microsoft IAS) is passing the authetication. The Controller has the error: DOT1X-1-INVALID_WPA_KEY_STATE: Received EAPOL-key message while in invalid state (0) - version 1, type 3, descriptor 254 with the mac address of the offending client in the log, at the same rate of the authentication storm. The clients have current drivers. We are using the Microsoft supplicant and have the Microsoft updates (SP2 and relevant wireless patches) installed.
I'm currently testing using the Intel supplicant, but have not been doing it long enough to see if it is an issue with that supplicant.Okay.... for this wlan ssid, you selected WPA+WPA2. Here you should define either WPA w/ tkip or WPA2 w/ AES.... or both. WPA2 performs better than WPA, but that depends on your client supporting WPA2. Since you selected PSK, you must of entered a pre-shared key. So in the AAA server tab, you don't have to enable local eap authentication.
For local eap, you need to choose wpa+wpa2 and 802.1x. This will also require a certificate on the WLC. I won't go into this too much because you are using PSK. Now on the client side, you would configure the ssid and either wpa tkip or wpa2 aes and psk... not enterprise. Enter you pre-shared key in the client and you should be good to go! -
Max no of 100 conversations exceeded / CPIC-CALL
Hi All,
There are more than 4000 messages in SMQ2 Tcode and when we checked the SLDCHECK we got this error-:
RFC ping returned exception with message:
max no of 100 conversations exceeded / CPIC-CALL: 'ThSAPCMRCV' : cmRc=17 thRc=45
After increasing the value for parameter CPIC_MAX_CONV 1000 it started working but after 1 min SLDCHECK again gave the same error.
We have already checked and implemented the SAP Note :316877.
I have one doubt this Note says that CPIC_MAX_CONV value should be 5000,is it really required?
I have checked the SLDCHECK with value 1000 for CPIC_MAX_CONV .
Pls suggest the solution.
Regards,
Prashant
Edited by: Prashant Shukla on Jan 27, 2009 12:50 PMCPIC_MAX_CONV value should be 5000,is it really required?
No, this is not mandatory. You should set it as per the load on your system.
What is the error when you perform SLDCHECK?
Regards,
Prateek -
CPIC_MAX_CONV - ERROR max no of 100 conversations exceeded
I recvd the "ERROR max no of 100 conversations exceeded" and I could resolve it by setting the environment variable CPIC_MAX_CONV to a higher value for my <sid>adm per note 316877.
What I want to know is where can i check to see if this environment variable actually took effect WITHIN IN SAP (I can see it set in env and when I echo the variable) ? Can I see this anywhere within the SAP land ... in its server logs , property files etc ?
Also in general when we make changes to environment variables at the OS level pertinent to SAP then where within SAP does this get absorbed and where I can see the new values.
Pls advise.
thank you
regards
LaxmiHi Laxmi,
Please check the below thread. I have given a possible solution in the thread.
Tcode SLDCHECK error
Cheers...,
Raghu -
ERROR:max no of 100 conversations exceeded
Dear All,
I m tring to comfigure SAP XI(2004sr2) in 2nd step of SLD system : Connect SLD TO SEN (if CEN Present). I m getting following error
Element 'BAPI_SLD_SUPPLIER_CONFIG_SET':Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=XIDEV SYSNR=00 GWHOST=XIDEV GWSERV=sapgw00 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR max no of 100 conversations exceeded
TIME Fri May 08 14:58:46 2009
RELEASE 700
COMPONENT CPIC (TCP/IP) with Unicode
VERSION 3
RC 466
MODULE r3cpic.c
LINE 10713
COUNTER 1
Element 'SAPDEMO.XID.Backend.Unclassified':!AbapConfigurationWriter.FM_CALL!BAPI_SLD_SUPPLIER_CONFIG_SET!AbapConfigurationWriter.FAILED!
Regards,
HitenHi Hiten,
Make sure that you have set the parameter CPIC_MAX_CONV under Environment variables --> system Variables.
For XI, the recommended value for this parameter is 400.
Regards,
Gopinathan. -
URGENT : "max no of 100 conversations exceeded".
Hi.
We developed RFC Java iView for SAP R/3.
This iview connect SAP R/3 and call RFC FM in SAP R/3.
We got connection error during high load.
Error is
"max no of 100 conversations exceeded".
So, I checked SAPFactory properties using Visual Admin but I think we got enough conenction.
Here is parameter.
Expiration : Checked
Connection Lifetime : 2
Maximum Connections : 1000
Cleanup Thread : 10
Maximum Time to wait for connection : 4
JEE System has below error :
#1.5#000F203CC23C002000007C33000050550004145E2C7DAE0A#1148294628636#/System/Server#sap.com/irj#com.sap.portal.connectors.R3#rtst018#54224##hhie01_E01_4224450#rtst018#d888e6e0e97f11da9210000f203cc23c#SAPEngine_Application_Thread[impl:3]_7##0#0#Error#1#com.sap.portal.connectors.R3#Plain###(R3/BW) Failed to get connection. Please contact your admin. #
#1.5#000F203CC23C00110000883F000050550004145E2C7DB625#1148294628638#/System/Server#sap.com/irj#com.sap.portal.connectors.R3#rtst417#54127####d9c05570e97f11dab72a000f203cc23c#SAPEngine_Application_Thread[impl:3]_16##0#0#Error#1#com.sap.portal.connectors.R3#Plain###(R3/BW) Failed to get connection. Please contact your admin. #
How can fix this problem ?
Regards, Arnold.Hi Arnold
When The external RFC/CPIC server cannot open any additioanl connections than u get
"ERROR max no of 100 conversations exceeded"
By setting the environment variables CPIC_MAX_CONV the library can manage more parallel connections
If an RFC server program registers with, for example, 100 threads at the R/3 gateway, 100 connections are initially kept in the server program. Every RFC running on this type of connection creates an additional entry in the connection list of the RFC server program. This means that, under full load, a maximum of 200 entries are possible.
I have not sure idea about "Maximum Connections" properties for SAPFactory in Connect Service
regards,
kaushal -
"SYSTEM FAILURE" during JCo call. max no of 100 conversations exceeded
Hi Experts,
My scernario is : RFC->File Asynch
When i do testing this scenario in Configuration (ID) -> tools-> test configuration I got below error.
Interface Mapping
Runtime error
"SYSTEM FAILURE" during JCo call. max no of 100 conversations exceeded / CPIC-CALL: 'ThSAPCMRCV' : cmRc=17 thRc=45
1) I have created incremented 100 to 300: Set the following environment variable CPIC_MAX_CONV=300
2) In sender RFC communication channel i have all correct parameters like: gateway service,Program ID, client number, password, userid etc
Pleas help me out.
thanks
siva grandhihi,
se this
/thread/174978 [original link is broken]
Look at SAP note 314530,316877
set this enviroment Variables:
set CPIC_MAX_CONV = 500 (WINDOWS)
setenv CPIC_MAX_CONV 500 (unix)
also check the rfc destination JCO_RUNTIME_JCOSERVER
AI_RUNTIME_JCOSERVER. if u have any error in this RFC plz refer to this link
http://help.sap.com/saphelp_nw04s/helpdata/en/9b/da0f41026df223e10000000a155106/frameset.htm
Thanks
Rodrigo
ps:reward points if useful
Edited by: Rodrigo Pertierra on Mar 26, 2008 11:59 AM -
Multiple Key Puts derived from single Client Put
Hi
I have a use case where a storage disabled member performs a single put into a distributed cache and at the Cache processing level (based on certain logic) I may wish to add extra keys into the cache for this value all within the same synchronous put.
So client performs...
cache.put("key1","value1")
In the Cache layer...(Trigger, Listener, LocaCache override?)
value 1 == some test then ...
cache.put("key2","value1")
cache.put("key3","value1")
cache.put("key4","vaue1")
I've tried to implement this by extending a LocalCache (that acts as an internal cache store for a ReadWriteBacking Map) and intercepting the single put, performing my logic and calling extra super.puts with the new keys. However I fallen foul of exceptions where the member performing the operation is not the owner. This is despite KeyAssociation being implemented on the keys, so I assume that all operations should be performed by the same member? I have confirmed that all the keys conform to the association.
The exception string...
"An entry was inserted into the backing map for the partitioned cache "london/env1/type1" that is not owned by this member; the entry will be removed."
So my question to any kind soul out thre is....what is the safest way to implement this functionality?
I could perform the extra puts within the client, however I wish to shield this storage disabled JVM from the logic and perform it somewhere on a cache thread.
To add further complexity the code that performs the logic to decide whether or not to add extra keys must have access to a JDBC connection or CacheLoader possibly?
Kind Regards
DaveyHi Davey,
While your scenario is rather advanced and requires caution, it's definitely feasible. The only explanation I have for the "is not owned by this member" message is that your key affinity was not configured/written the way you intended. As a result, the internal map listener Coherence utilizes to "watch" backing map operations prevented this from happening. If your test case small enough to be posted here, I'd be happy to review it; otherwise I would suggest opening a corresponding service request.
Regards,
Gene -
IO Exception: Lock timeout exceeded for documents , wait time = 60014
Hi,
We are getting an error while uploading any document on portal in KM content area. The full error details as follows
#D27E2001B003002500000D210005D0D20004520E6FF2B6FB#1216121868039#com.sapportals.wcm.repository.service.accessstatistic.AccessStatisticManager#sap.com/irj#com.sapportals.wcm.repository.service.accessstatistic.AccessStatisticManager#BMERRON#71986##<host name>_7664450#BMERRON#3f730c80526211ddb0fcd27e2001b003#SAPEngine_Application_Thread[impl:3]_4##0#0#Error##Plain###error while handling event - com.sapportals.wcm.WcmException: IO Exception: Lock timeout exceeded for <documents>, wait time = 60006
at com.sapportals.wcm.repository.service.appproperties.PropertiesService.setProperty(PropertiesService.java:984)
at com.sapportals.wcm.repository.service.appproperties.PropertiesService.setProperty(PropertiesService.java:1203)
at com.sapportals.wcm.repository.service.appproperties.PropertiesManager.setProperty(PropertiesManager.java:176)
at com.sapportals.wcm.repository.service.accessstatistic.AccessStatisticManager.updateLastReadDate(AccessStatisticManager.java:177)
at com.sapportals.wcm.repository.service.accessstatistic.AccessStatisticManager.received(AccessStatisticManager.java:253)
at com.sapportals.wcm.util.events.ReceiverEntry.doSend(ReceiverEntry.java:223)
at com.sapportals.wcm.util.events.EventBroker.send(EventBroker.java:86)
at com.sapportals.wcm.util.events.TransactionalEventBroker.send(TransactionalEventBroker.java:56)
at com.sapportals.wcm.repository.manager.ResourceEventBroker.send(ResourceEventBroker.java:219)
at com.sapportals.wcm.repository.manager.AbstractRepositoryManager.sendEvent(AbstractRepositoryManager.java:322)
at com.sapportals.wcm.repository.RMAdapter.sendEvent(RMAdapter.java:342)
at com.sapportals.wcm.repository.ResourceImpl.sendEvent(ResourceImpl.java:4206)
at com.sapportals.wcm.repository.ContentImpl.getInputStream(ContentImpl.java:119)
at com.sapportals.wcm.repository.ContentImpl.getInputStream(ContentImpl.java:132)
at com.sapportals.wcm.service.xmlforms.transformation.ResourceDemultiplexer.getContentStream(ResourceDemultiplexer.java:71)
at com.sapportals.wcm.service.xmlforms.transformation.Transformation.render(Transformation.java:209)
at com.sapportals.wcm.app.xmlforms.PreviewServlet.sendForm(PreviewServlet.java:165)
at com.sapportals.wcm.app.xmlforms.PreviewServlet.doGetAction(PreviewServlet.java:130)
at com.sapportals.wcm.app.xmlforms.XFBaseServlet.doGet(XFBaseServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sapportals.wcm.app.xmlforms.XFBaseServlet.service(XFBaseServlet.java:134)
at com.sapportals.wcm.portal.proxy.PCProxyServlet.service(PCProxyServlet.java:333)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sapportals.portal.prt.core.broker.ServletComponentItem$ServletWrapperComponent.doContent(ServletComponentItem.java:110)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
at java.security.AccessController.doPrivileged(AccessController.java:242)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:215)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Any Help?
Regards,
SreeHi sreedhar Gunda,
Check whether the repositories are in active and running mode or not. If they are running fine. then check the authorization is sufficient from BASIS people.
points if useful
Thanks
Suresh -
DpVmCheck: max number of priv VMs exceeded (1 0, timeout)
Hello,
In our CRM system EHP1 FOR CRM 7 ABAP ,users get this screen mainly for big contracts at different stages like collision run,saving.
Status before error started
I have already gone through notes 1757252
But the parameter rdisp/max_vm_priv_time and rdisp/max_vm_priv_no doesn't exist in our system. Instead is there any other parameter which we can use in our release ?
I could find these errors when the timeout screen occurred :
DEV_DISP
Wed Jul 23 15:26:08 2014
DpVmCheck: max number of priv VMs exceeded (1 > 0, timeout), reset T59/M0/U13880/V4
Wed Jul 23 15:26:28 2014
DpVmCheck: max number of priv VMs exceeded (1 > 0, timeout), reset T59/M0/U13880/V4
Wed Jul 23 15:26:46 2014
*** ERROR => DpRqCheck: T59 in state TM_SLOT_FREE [dpxxdisp.c 8006]
***LOG Q0G=> DpRqBadHandle, bad_req ( DIA) [dpxxdisp.c 6125]
*** ERROR => DpRqBadHandle: BAD REQUEST - Reason: DpRqCheck failed (line 7037): [dpxxdisp.c 6127]
-IN-- sender_id DISPATCHER tid 59 wp_ca_blk -1 wp_id -1
-IN-- action SEND_TO_WP uid 13880 appc_ca_blk -1 type DIA
-IN-- new_stat NO_CHANGE mode 0 len 0 rq_id 24366
-IN-- req_info DP_CANCEL_PRIV
-IN-- msg_name -
*** ERROR => DpRqCheck: T59 in state TM_SLOT_FREE [dpxxdisp.c 8006]
***LOG Q0G=> DpRqBadHandle, bad_req ( DIA) [dpxxdisp.c 6125]
*** ERROR => DpRqBadHandle: BAD REQUEST - Reason: DpRqCheck failed (line 7037): [dpxxdisp.c 6127]
-IN-- sender_id DISPATCHER tid 59 wp_ca_blk -1 wp_id -1
-IN-- action SEND_TO_WP uid 13880 appc_ca_blk -1 type DIA
-IN-- new_stat NO_CHANGE mode 0 len 0 rq_id 24502
-IN-- req_info DP_CANCEL_PRIV
-IN-- msg_name -
*** ERROR => DpRqCheck: T59 in state TM_SLOT_FREE [dpxxdisp.c 8006]
***LOG Q0G=> DpRqBadHandle, bad_req ( DIA) [dpxxdisp.c 6125]
*** ERROR => DpRqBadHandle: BAD REQUEST - Reason: DpRqCheck failed (line 7037): [dpxxdisp.c 6127]
-IN-- sender_id DISPATCHER tid 59 wp_ca_blk -1 wp_id -1
-IN-- action SEND_TO_WP uid 13880 appc_ca_blk -1 type DIA
-IN-- new_stat NO_CHANGE mode 0 len 0 rq_id 24691
-IN-- req_info DP_CANCEL_PRIV
-IN-- msg_name -
sm21:
Q0 G Request (type DIA) cannot be processed
work process trace
please check the image
Thanks
ShradhaHello Divyanshu
It didnt create dev_vm.trc and VM_STACK_TRACE
And I am unable to provide dev_disp and dev_w* here due to size of the trace
But could the error be due to any of these parameters :
Parameters
Current
Changed
rdisp/max_vm_priv_time
2400
SERVLET=2400, RFC=2400
isp/max_vm_priv_no
3
SERVLET=3, RFC=3
rdisp/max_priv_time
600
3600
Maximum hold time for work processes in PRIV mode
rdisp/max_debug_lazy_time
600
3600
Maximum hold time for work processes in DEBUG mode
rdisp/appc_ca_blk_no
1000
1058
Buffer Size for CPI-C Communications
rdisp/wp_ca_blk_no
300
1058
Work Process Communication Blocks
vmcj/option/ps
960M
1460M
poolsize for the VMC
vmcj/option/gc/sharedWaterMark
90
70
VMC: watermark for shared garbage collector
vmcj/max_vm_heap_MB
64
128
max. vm heap
rdisp/keepalive
1200
3600
Timer for check of unused connections
rdisp/keepalive_timeout
60
150
Timeout for connection to SAPGUI
rdisp/wppriv_max_no
DEFAULT
16
Maximum number of work processes in PRIV mode -
Decrypt errors occurred for client
I am getting error messages for clients:
11 Mon Jun 14 09:11:56 2010 Decrypt errors occurred for client 00:13:ce:54:57:3c using WPA key on 802.11b/g interface of AP 00:16:9c:91:97:c0
12 Mon Jun 14 09:11:56 2010 Decrypt errors occurred for client 00:16:6f:91:d8:60 using WPA2 key on 802.11b/g interface of AP 00:16:9c:91:97:c0
These are only occuring for clients that are disconnecting....
They can reconnect after a WLC reboot....
We have swapped APs.....
I have seen this error in other forums but it says not to worry about it. There has to be a connection between this and clients getting disconnected. We have anywhere between 10-50 clients on the system at any one time.
Is this a client issue (nic firmware, version) or is this an error in the controller??
AIR-WLC2106-K9
IOS ver: 6.0.196.0
ThanksThis means that the client is using a different key than the one he agreed on using with the AP. There were bugs about this long time ago but nothing recent.
I've seen this happening a lot with old/not updated clients. It rarely happens on intel adapters with latest drivers for example.
So I'd suggest checking the client pattern (are the clients facing this all having old wireless drivers ?).
It can also happen if you offer funny encryption combinations that client doesn't like (wpa1+aes, wpa2+tkip). Try to only enable wpa2/aes and see if it helps.
Nicolas -
Dears,
I use to have wireless infrastructure based on autonomous APs 1142n, auth w/ 802.1x and everything was fine.
My Company decided to implement WLC 5508, and I changed only 2nd floor (2 APs) as lightweight and implement WLC over there as pilot testing...
Now All persons here (around 35 clients) are complaining about disconnections, poor signal...
Both APs are distant each other maximim of 15 meters... Our office has a medium open spaced room, with (20 X 15 meters) only 2 "Pilaster" in the middle of the room.
I am facing this message at WLC logs
Thu Nov 1 16:03:57 2012
Coverage hole pre alarm for client[1] 00:37:6d:eb:67:44 on 802.11a interface of AP 00:26:cb:4c:8e:b0 (AP01-RJOBTF). Hist: 1 0 3 4 1 1 2 7 2 9 10 13 4 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Thu Nov 1 15:55:21 2012
Rogue AP : 7c:4f:b5:ed:27:a1 detected on Base Radio MAC : 1c:aa:07:6e:93:20 Interface no:0(802.11b/g) on Channel 11 with RSSI: -92 and SNR: 1 and Classification: unclassified
Thu Nov 1 15:50:27 2012
Coverage hole pre alarm for client[1] 28:e0:2c:6d:11:58 on 802.11b/g interface of AP 00:26:cb:4c:8e:b0 (AP01-RJOBTF). Hist: 0 0 2 5 11 16 9 2 5 12 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Is there any best practices I should perform over here ?
Any specific configuration with the signal itself ? In my opinion we dont have a big room here .. 2 APs should work very well... but they are not...
I also can see many Rogue APs... I am not sure if that rogues aps have anything to do with this problem.... also I didnt change anything at 3rd floor (not sure if the
Thanks in advance!!!Actually I am using both APs as lightweight in 2nd floor.
How about this power level? where I can find those parameters ?
At 3rd floor all APs are autonomous, I accessed one of them and find this parameter
CCK Transmitter Power (dBm): Max
OFDM Transmitter Power (dBm): Max
Client Power (dBm): Max
is that the parameter you talked about ?
At WLC I found this screen
Tx Power Level Assignment Algorithm
Power Level Assignment Method
Automatic
On Demand
Fixed
1 2 3 4 5
Maximum Power Level Assignment (-10 to 30 dBm)
Minimum Power Level Assignment (-10 to 30 dBm)
Power Assignment Leader
Last Power Level Assignment
Power Threshold (-80 to -50 dBm)
Power Neighbor Count
Should I check anything else ?
Thanks in advance!!! -
ERP Package for client deletion
Hi experts,
I have a problem when I do the client deletion using the process type"ERP Package for client deletion".
After the first time execution of deleting the datas of table TD09P_*...,
I received the follows below.
State of sub-activity State Sub-activities
Aborted 5
Completed successfully 10,203
Completed with warning 0
Completed with error 0
Running (In process) 0
Not yet started 0
There are 5 aborted jobs
(TD09P_T313I
TD09P_T313J
TD09P_T313K
TD09P_T313L
TD09P_T313LD).
I checked the logs, which said all these 5 like this:
Message text
Job started
Step 001 started (program /TDM/9_300_90007_02208_C, variant &0000000000007, user ID LEEE03)
Error while reading cluster CNVMBTCLU, Key 0144703489
Job cancelled
I searched in note1175565 and found that it was fixed since I have updated to sp11 already.
Also I tried to re-run the cancelled jobs manually using sm37, the error is like this:
Job started
Step 001 started (program /TDM/9_300_90007_02208_C, variant &0000000000007, user ID LEEE03)
Session ID C1290007000000000010 is not valid
Job cancelled
according to these above, could anyone tell me the reason?
Thanks& Best Regards,
EricHi
I had the exact same issue, and what i have found was that the tool drop all the authorization data and if you had specified a cust profile that handle the RFC authorization then the RFC connection to the receiver system then no longer works.
The way I managed to solve the issue was to change the SAP_TDMS_MASTER role and added in object S_RFCACL with all permissions and generated and activated it.
This allowed the RFC to work again and then you could restart the process from the central system
Regards
Alex Tender
Maybe you are looking for
-
Hye, I'm trying to make Windows on-screen keyboard open right after any text box is getting focus, right now, as default, the user must click the text box twice to activate the keyboard which is a problem, becasue it's on a tablet and not always the
-
Valuated stock for a certain period
Hi all, Using transaction MC.9 (Material Analysis: Stock), you can search for a material for a certain period (ea. 04.2007). The outcome gives you the Valuated Stock for that period. In which table is this Valuated stock stored? How can I fetch this
-
Adobe flash player 11 does not work with 64-bit vista - is there a fix? it works with 64-bit windows 7. When I try to watch videos, I get the message 'this video is no longer available' - I cannot find access to previous versions
-
How to put KF's and Char's in order
Hi, As per requirement i need to show the Char's and KF's in the below order. 1. Sales Org 2. Sold-to party 3. Bill-to party 4. Cust PO Nbr 5. Sales Document
-
Can't see computers in Q administrator
I found a video tutorial on how to set it up which I've followed. However only my main machine shows up in Qadministator and not the other machine (connected via ethernet) Any suggestions please?