API tools faq
paste
abhisheksha

DHCP Success

abhisheksha
May 13th, 2014
320
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 26.01 KB | None | 0 0
raw download clone embed print report
  1.  
  2. (Cisco Controller) >
  3. (Cisco Controller) >
  4. (Cisco Controller) >
  5. (Cisco Controller) >*apfMsConnTask_3: May 13 15:33:27.136: 38:48:4c:22:52:16 Association received from mobile on AP f0:29:29:eb:50:a0
  6. *apfMsConnTask_3: May 13 15:33:27.136: 38:48:4c:22:52:16 0.0.0.0 RUN (20) Changing IPv4 ACL 'PERMIT_ALL_TRAFFIC' (ACL ID 5) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1697)
  7. *apfMsConnTask_3: May 13 15:33:27.136: 38:48:4c:22:52:16 0.0.0.0 RUN (20) Changing IPv6 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1864)
  8. *apfMsConnTask_3: May 13 15:33:27.136: 38:48:4c:22:52:16 apfApplyWlanPolicy: Retaining the ACL recieved in AAA attributes 255 on mobile
  9. *apfMsConnTask_3: May 13 15:33:27.136: 38:48:4c:22:52:16 Applying site-specific Local Bridging override for station 38:48:4c:22:52:16 - vapId 2, site 'default-group', interface 'employee'
  10. *apfMsConnTask_3: May 13 15:33:27.136: 38:48:4c:22:52:16 Applying Local Bridging Interface Policy for station 38:48:4c:22:52:16 - vlan 930, interface id 11, interface 'employee'
  11. *apfMsConnTask_3: May 13 15:33:27.136: 38:48:4c:22:52:16 processSsidIE statusCode is 0 and status is 0
  12. *apfMsConnTask_3: May 13 15:33:27.136: 38:48:4c:22:52:16 processSsidIE ssid_done_flag is 0 finish_flag is 0
  13. *apfMsConnTask_3: May 13 15:33:27.136: 38:48:4c:22:52:16 STA - rates (8): 140 18 152 36 176 72 96 108 12 18 24 96 0 0 0 0
  14. *apfMsConnTask_3: May 13 15:33:27.136: 38:48:4c:22:52:16 suppRates statusCode is 0 and gotSuppRatesElement is 1
  15. *apfMsConnTask_3: May 13 15:33:27.136: 38:48:4c:22:52:16 Processing RSN IE type 48, length 20 for mobile 38:48:4c:22:52:16
  16. *apfMsConnTask_3: May 13 15:33:27.136: 38:48:4c:22:52:16 Received RSN IE with 0 PMKIDs from mobile 38:48:4c:22:52:16
  17. *apfMsConnTask_3: May 13 15:33:27.136: 38:48:4c:22:52:16 Found an cache entry for BSSID f0:29:29:eb:50:a1 in PMKID cache at index 0 of station 38:48:4c:22:52:16
  18. *apfMsConnTask_3: May 13 15:33:27.136: 38:48:4c:22:52:16 Removing BSSID f0:29:29:eb:50:a1 from PMKID cache of station 38:48:4c:22:52:16
  19. *apfMsConnTask_3: May 13 15:33:27.136: 38:48:4c:22:52:16 Resetting MSCB PMK Cache Entry 0 for station 38:48:4c:22:52:16
  20. *apfMsConnTask_3: May 13 15:33:27.136: 38:48:4c:22:52:16 Setting active key cache index 0 ---> 8
  21. *apfMsConnTask_3: May 13 15:33:27.136: 38:48:4c:22:52:16 unsetting PmkIdValidatedByAp
  22. *apfMsConnTask_3: May 13 15:33:27.137: 38:48:4c:22:52:16 pemApfDeleteMobileStation2: APF_MS_PEM_WAIT_L2_AUTH_COMPLETE = 0.
  23. *apfMsConnTask_3: May 13 15:33:27.137: 38:48:4c:22:52:16 0.0.0.0 RUN (20) Deleted mobile LWAPP rule on AP [f0:29:29:eb:50:a0]
  24. *apfMsConnTask_3: May 13 15:33:27.137: 38:48:4c:22:52:16 Updated location for station old AP f0:29:29:eb:50:a0-0, new AP f0:29:29:eb:50:a0-1
  25. *apfMsConnTask_3: May 13 15:33:27.137: 38:48:4c:22:52:16 apfMsRunStateDec
  26. *apfMsConnTask_3: May 13 15:33:27.137: 38:48:4c:22:52:16 apfMs1xStateDec
  27. *apfMsConnTask_3: May 13 15:33:27.137: 38:48:4c:22:52:16 0.0.0.0 RUN (20) Change state to START (0) last state RUN (20)
  28.  
  29. *apfMsConnTask_3: May 13 15:33:27.137: 38:48:4c:22:52:16 pemApfAddMobileStation2: APF_MS_PEM_WAIT_L2_AUTH_COMPLETE = 0.
  30. *apfMsConnTask_3: May 13 15:33:27.137: 38:48:4c:22:52:16 0.0.0.0 START (0) Initializing policy
  31. *apfMsConnTask_3: May 13 15:33:27.137: 38:48:4c:22:52:16 0.0.0.0 START (0) Change state to AUTHCHECK (2) last state RUN (20)
  32.  
  33. *apfMsConnTask_3: May 13 15:33:27.137: 38:48:4c:22:52:16 0.0.0.0 AUTHCHECK (2) Change state to 8021X_REQD (3) last state RUN (20)
  34.  
  35. *apfMsConnTask_3: May 13 15:33:27.137: 38:48:4c:22:52:16 0.0.0.0 8021X_REQD (3) DHCP required on AP f0:29:29:eb:50:a0 vapId 2 apVapId 2for this client
  36. *apfMsConnTask_3: May 13 15:33:27.137: 38:48:4c:22:52:16 Not Using WMM Compliance code qosCap 00
  37. *apfMsConnTask_3: May 13 15:33:27.137: 38:48:4c:22:52:16 0.0.0.0 8021X_REQD (3) Plumbed mobile LWAPP rule on AP f0:29:29:eb:50:a0 vapId 2 apVapId 2
  38. *apfMsConnTask_3: May 13 15:33:27.137: 38:48:4c:22:52:16 apfPemAddUser2 (apf_policy.c:268) Changing state for mobile 38:48:4c:22:52:16 on AP f0:29:29:eb:50:a0 from Associated to Associated
  39.  
  40. *apfMsConnTask_3: May 13 15:33:27.137: 38:48:4c:22:52:16 Stopping deletion of Mobile Station: (callerId: 48)
  41. *apfMsConnTask_3: May 13 15:33:27.137: 38:48:4c:22:52:16 Sending Assoc Response to station on BSSID f0:29:29:eb:50:a0 (status 0) ApVapId 2 Slot 1
  42. *apfMsConnTask_3: May 13 15:33:27.137: 38:48:4c:22:52:16 apfProcessAssocReq (apf_80211.c:6290) Changing state for mobile 38:48:4c:22:52:16 on AP f0:29:29:eb:50:a0 from Associated to Associated
  43.  
  44. *pemReceiveTask: May 13 15:33:27.140: 38:48:4c:22:52:16 0.0.0.0 Removed NPU entry.
  45. *dot1xMsgTask: May 13 15:33:27.141: 38:48:4c:22:52:16 Disable re-auth, use PMK lifetime.
  46. *dot1xMsgTask: May 13 15:33:27.141: 38:48:4c:22:52:16 dot1x - moving mobile 38:48:4c:22:52:16 into Connecting state
  47. *dot1xMsgTask: May 13 15:33:27.142: 38:48:4c:22:52:16 Sending EAP-Request/Identity to mobile 38:48:4c:22:52:16 (EAP Id 1)
  48. *Dot1x_NW_MsgTask_6: May 13 15:33:27.162: 38:48:4c:22:52:16 Received EAPOL EAPPKT from mobile 38:48:4c:22:52:16
  49. *Dot1x_NW_MsgTask_6: May 13 15:33:27.162: 38:48:4c:22:52:16 Received Identity Response (count=1) from mobile 38:48:4c:22:52:16
  50. *Dot1x_NW_MsgTask_6: May 13 15:33:27.162: 38:48:4c:22:52:16 EAP State update from Connecting to Authenticating for mobile 38:48:4c:22:52:16
  51. *Dot1x_NW_MsgTask_6: May 13 15:33:27.162: 38:48:4c:22:52:16 dot1x - moving mobile 38:48:4c:22:52:16 into Authenticating state
  52. *Dot1x_NW_MsgTask_6: May 13 15:33:27.162: 38:48:4c:22:52:16 Entering Backend Auth Response state for mobile 38:48:4c:22:52:16
  53. *Dot1x_NW_MsgTask_6: May 13 15:33:27.166: 38:48:4c:22:52:16 Processing Access-Challenge for mobile 38:48:4c:22:52:16
  54. *Dot1x_NW_MsgTask_6: May 13 15:33:27.166: 38:48:4c:22:52:16 Entering Backend Auth Req state (id=189) for mobile 38:48:4c:22:52:16
  55. *Dot1x_NW_MsgTask_6: May 13 15:33:27.166: 38:48:4c:22:52:16 WARNING: updated EAP-Identifier 1 ===> 189 for STA 38:48:4c:22:52:16
  56. *Dot1x_NW_MsgTask_6: May 13 15:33:27.166: 38:48:4c:22:52:16 Sending EAP Request from AAA to mobile 38:48:4c:22:52:16 (EAP Id 189)
  57. *Dot1x_NW_MsgTask_6: May 13 15:33:27.187: 38:48:4c:22:52:16 Received EAPOL EAPPKT from mobile 38:48:4c:22:52:16
  58. *Dot1x_NW_MsgTask_6: May 13 15:33:27.187: 38:48:4c:22:52:16 Received EAP Response from mobile 38:48:4c:22:52:16 (EAP Id 189, EAP Type 3)
  59. *Dot1x_NW_MsgTask_6: May 13 15:33:27.187: 38:48:4c:22:52:16 Entering Backend Auth Response state for mobile 38:48:4c:22:52:16
  60. *Dot1x_NW_MsgTask_6: May 13 15:33:27.189: 38:48:4c:22:52:16 Processing Access-Challenge for mobile 38:48:4c:22:52:16
  61. *Dot1x_NW_MsgTask_6: May 13 15:33:27.189: 38:48:4c:22:52:16 Entering Backend Auth Req state (id=190) for mobile 38:48:4c:22:52:16
  62. *Dot1x_NW_MsgTask_6: May 13 15:33:27.189: 38:48:4c:22:52:16 Sending EAP Request from AAA to mobile 38:48:4c:22:52:16 (EAP Id 190)
  63. *Dot1x_NW_MsgTask_6: May 13 15:33:27.205: 38:48:4c:22:52:16 Received EAPOL EAPPKT from mobile 38:48:4c:22:52:16
  64. *Dot1x_NW_MsgTask_6: May 13 15:33:27.205: 38:48:4c:22:52:16 Received EAP Response from mobile 38:48:4c:22:52:16 (EAP Id 190, EAP Type 25)
  65. *Dot1x_NW_MsgTask_6: May 13 15:33:27.205: 38:48:4c:22:52:16 Entering Backend Auth Response state for mobile 38:48:4c:22:52:16
  66. *Dot1x_NW_MsgTask_6: May 13 15:33:27.207: 38:48:4c:22:52:16 Processing Access-Challenge for mobile 38:48:4c:22:52:16
  67. *Dot1x_NW_MsgTask_6: May 13 15:33:27.207: 38:48:4c:22:52:16 Entering Backend Auth Req state (id=191) for mobile 38:48:4c:22:52:16
  68. *Dot1x_NW_MsgTask_6: May 13 15:33:27.207: 38:48:4c:22:52:16 Sending EAP Request from AAA to mobile 38:48:4c:22:52:16 (EAP Id 191)
  69. *Dot1x_NW_MsgTask_6: May 13 15:33:27.211: 38:48:4c:22:52:16 Received EAPOL EAPPKT from mobile 38:48:4c:22:52:16
  70. *Dot1x_NW_MsgTask_6: May 13 15:33:27.211: 38:48:4c:22:52:16 Received EAP Response from mobile 38:48:4c:22:52:16 (EAP Id 191, EAP Type 25)
  71. *Dot1x_NW_MsgTask_6: May 13 15:33:27.211: 38:48:4c:22:52:16 Entering Backend Auth Response state for mobile 38:48:4c:22:52:16
  72. *Dot1x_NW_MsgTask_6: May 13 15:33:27.212: 38:48:4c:22:52:16 Processing Access-Challenge for mobile 38:48:4c:22:52:16
  73. *Dot1x_NW_MsgTask_6: May 13 15:33:27.212: 38:48:4c:22:52:16 Entering Backend Auth Req state (id=192) for mobile 38:48:4c:22:52:16
  74. *Dot1x_NW_MsgTask_6: May 13 15:33:27.212: 38:48:4c:22:52:16 Sending EAP Request from AAA to mobile 38:48:4c:22:52:16 (EAP Id 192)
  75. *Dot1x_NW_MsgTask_6: May 13 15:33:27.215: 38:48:4c:22:52:16 Received EAPOL EAPPKT from mobile 38:48:4c:22:52:16
  76. *Dot1x_NW_MsgTask_6: May 13 15:33:27.215: 38:48:4c:22:52:16 Received EAP Response from mobile 38:48:4c:22:52:16 (EAP Id 192, EAP Type 25)
  77. *Dot1x_NW_MsgTask_6: May 13 15:33:27.215: 38:48:4c:22:52:16 Entering Backend Auth Response state for mobile 38:48:4c:22:52:16
  78. *Dot1x_NW_MsgTask_6: May 13 15:33:27.217: 38:48:4c:22:52:16 Processing Access-Challenge for mobile 38:48:4c:22:52:16
  79. *Dot1x_NW_MsgTask_6: May 13 15:33:27.217: 38:48:4c:22:52:16 Entering Backend Auth Req state (id=193) for mobile 38:48:4c:22:52:16
  80. *Dot1x_NW_MsgTask_6: May 13 15:33:27.217: 38:48:4c:22:52:16 Sending EAP Request from AAA to mobile 38:48:4c:22:52:16 (EAP Id 193)
  81. *Dot1x_NW_MsgTask_6: May 13 15:33:27.245: 38:48:4c:22:52:16 Received EAPOL EAPPKT from mobile 38:48:4c:22:52:16
  82. *Dot1x_NW_MsgTask_6: May 13 15:33:27.245: 38:48:4c:22:52:16 Received EAP Response from mobile 38:48:4c:22:52:16 (EAP Id 193, EAP Type 25)
  83. *Dot1x_NW_MsgTask_6: May 13 15:33:27.245: 38:48:4c:22:52:16 Entering Backend Auth Response state for mobile 38:48:4c:22:52:16
  84. *Dot1x_NW_MsgTask_6: May 13 15:33:27.255: 38:48:4c:22:52:16 Processing Access-Challenge for mobile 38:48:4c:22:52:16
  85. *Dot1x_NW_MsgTask_6: May 13 15:33:27.255: 38:48:4c:22:52:16 Entering Backend Auth Req state (id=194) for mobile 38:48:4c:22:52:16
  86. *Dot1x_NW_MsgTask_6: May 13 15:33:27.255: 38:48:4c:22:52:16 Sending EAP Request from AAA to mobile 38:48:4c:22:52:16 (EAP Id 194)
  87. *Dot1x_NW_MsgTask_6: May 13 15:33:27.257: 38:48:4c:22:52:16 Received EAPOL EAPPKT from mobile 38:48:4c:22:52:16
  88. *Dot1x_NW_MsgTask_6: May 13 15:33:27.257: 38:48:4c:22:52:16 Received EAP Response from mobile 38:48:4c:22:52:16 (EAP Id 194, EAP Type 25)
  89. *Dot1x_NW_MsgTask_6: May 13 15:33:27.257: 38:48:4c:22:52:16 Entering Backend Auth Response state for mobile 38:48:4c:22:52:16
  90. *Dot1x_NW_MsgTask_6: May 13 15:33:27.258: 38:48:4c:22:52:16 Processing Access-Challenge for mobile 38:48:4c:22:52:16
  91. *Dot1x_NW_MsgTask_6: May 13 15:33:27.258: 38:48:4c:22:52:16 Entering Backend Auth Req state (id=195) for mobile 38:48:4c:22:52:16
  92. *Dot1x_NW_MsgTask_6: May 13 15:33:27.258: 38:48:4c:22:52:16 Sending EAP Request from AAA to mobile 38:48:4c:22:52:16 (EAP Id 195)
  93. *Dot1x_NW_MsgTask_6: May 13 15:33:27.269: 38:48:4c:22:52:16 Received EAPOL EAPPKT from mobile 38:48:4c:22:52:16
  94. *Dot1x_NW_MsgTask_6: May 13 15:33:27.269: 38:48:4c:22:52:16 Received EAP Response from mobile 38:48:4c:22:52:16 (EAP Id 195, EAP Type 25)
  95. *Dot1x_NW_MsgTask_6: May 13 15:33:27.269: 38:48:4c:22:52:16 Entering Backend Auth Response state for mobile 38:48:4c:22:52:16
  96. *Dot1x_NW_MsgTask_6: May 13 15:33:27.270: 38:48:4c:22:52:16 Processing Access-Challenge for mobile 38:48:4c:22:52:16
  97. *Dot1x_NW_MsgTask_6: May 13 15:33:27.270: 38:48:4c:22:52:16 Entering Backend Auth Req state (id=196) for mobile 38:48:4c:22:52:16
  98. *Dot1x_NW_MsgTask_6: May 13 15:33:27.270: 38:48:4c:22:52:16 Sending EAP Request from AAA to mobile 38:48:4c:22:52:16 (EAP Id 196)
  99. *Dot1x_NW_MsgTask_6: May 13 15:33:27.273: 38:48:4c:22:52:16 Received EAPOL EAPPKT from mobile 38:48:4c:22:52:16
  100. *Dot1x_NW_MsgTask_6: May 13 15:33:27.273: 38:48:4c:22:52:16 Received EAP Response from mobile 38:48:4c:22:52:16 (EAP Id 196, EAP Type 25)
  101. *Dot1x_NW_MsgTask_6: May 13 15:33:27.273: 38:48:4c:22:52:16 Entering Backend Auth Response state for mobile 38:48:4c:22:52:16
  102. *Dot1x_NW_MsgTask_6: May 13 15:33:27.278: 38:48:4c:22:52:16 Processing Access-Challenge for mobile 38:48:4c:22:52:16
  103. *Dot1x_NW_MsgTask_6: May 13 15:33:27.278: 38:48:4c:22:52:16 Entering Backend Auth Req state (id=197) for mobile 38:48:4c:22:52:16
  104. *Dot1x_NW_MsgTask_6: May 13 15:33:27.278: 38:48:4c:22:52:16 Sending EAP Request from AAA to mobile 38:48:4c:22:52:16 (EAP Id 197)
  105. *Dot1x_NW_MsgTask_6: May 13 15:33:27.281: 38:48:4c:22:52:16 Received EAPOL EAPPKT from mobile 38:48:4c:22:52:16
  106. *Dot1x_NW_MsgTask_6: May 13 15:33:27.281: 38:48:4c:22:52:16 Received EAP Response from mobile 38:48:4c:22:52:16 (EAP Id 197, EAP Type 25)
  107. *Dot1x_NW_MsgTask_6: May 13 15:33:27.281: 38:48:4c:22:52:16 Entering Backend Auth Response state for mobile 38:48:4c:22:52:16
  108. *Dot1x_NW_MsgTask_6: May 13 15:33:27.283: 38:48:4c:22:52:16 Processing Access-Challenge for mobile 38:48:4c:22:52:16
  109. *Dot1x_NW_MsgTask_6: May 13 15:33:27.283: 38:48:4c:22:52:16 Entering Backend Auth Req state (id=198) for mobile 38:48:4c:22:52:16
  110. *Dot1x_NW_MsgTask_6: May 13 15:33:27.283: 38:48:4c:22:52:16 Sending EAP Request from AAA to mobile 38:48:4c:22:52:16 (EAP Id 198)
  111. *Dot1x_NW_MsgTask_6: May 13 15:33:27.288: 38:48:4c:22:52:16 Received EAPOL EAPPKT from mobile 38:48:4c:22:52:16
  112. *Dot1x_NW_MsgTask_6: May 13 15:33:27.288: 38:48:4c:22:52:16 Received EAP Response from mobile 38:48:4c:22:52:16 (EAP Id 198, EAP Type 25)
  113. *Dot1x_NW_MsgTask_6: May 13 15:33:27.288: 38:48:4c:22:52:16 Entering Backend Auth Response state for mobile 38:48:4c:22:52:16
  114. *Dot1x_NW_MsgTask_6: May 13 15:33:27.295: 38:48:4c:22:52:16 Processing Access-Accept for mobile 38:48:4c:22:52:16
  115. *Dot1x_NW_MsgTask_6: May 13 15:33:27.295: 38:48:4c:22:52:16 Resetting web IPv4 acl from 255 to 255
  116.  
  117. *Dot1x_NW_MsgTask_6: May 13 15:33:27.295: 38:48:4c:22:52:16 0.0.0.0 8021X_REQD (3) Changing IPv4 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1697)
  118. *Dot1x_NW_MsgTask_6: May 13 15:33:27.295: 38:48:4c:22:52:16 0.0.0.0 8021X_REQD (3) Changing IPv6 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1864)
  119. *Dot1x_NW_MsgTask_6: May 13 15:33:27.295: 38:48:4c:22:52:16 apfApplyWlanPolicy: Retaining the ACL recieved in AAA attributes 255 on mobile
  120. *Dot1x_NW_MsgTask_6: May 13 15:33:27.295: 38:48:4c:22:52:16 Inserting AAA Override struct for mobile
  121. MAC: 38:48:4c:22:52:16, source 4
  122.  
  123. *Dot1x_NW_MsgTask_6: May 13 15:33:27.295: 38:48:4c:22:52:16 0.0.0.0 8021X_REQD (3) Changing IPv4 ACL 'none' (ACL ID 255) ===> 'PERMIT_ALL_TRAFFIC' (ACL ID 5) --- (caller apf_policy.c:1750)
  124. *Dot1x_NW_MsgTask_6: May 13 15:33:27.295: 38:48:4c:22:52:16 Setting re-auth timeout to 1800 seconds, got from WLAN config.
  125. *Dot1x_NW_MsgTask_6: May 13 15:33:27.295: 38:48:4c:22:52:16 Station 38:48:4c:22:52:16 setting dot1x reauth timeout = 1800
  126. *Dot1x_NW_MsgTask_6: May 13 15:33:27.295: 38:48:4c:22:52:16 Creating a PKC PMKID Cache entry for station 38:48:4c:22:52:16 (RSN 2)
  127. *Dot1x_NW_MsgTask_6: May 13 15:33:27.295: 38:48:4c:22:52:16 Resetting MSCB PMK Cache Entry 0 for station 38:48:4c:22:52:16
  128. *Dot1x_NW_MsgTask_6: May 13 15:33:27.295: 38:48:4c:22:52:16 Setting active key cache index 8 ---> 8
  129. *Dot1x_NW_MsgTask_6: May 13 15:33:27.295: 38:48:4c:22:52:16 Setting active key cache index 8 ---> 0
  130. *Dot1x_NW_MsgTask_6: May 13 15:33:27.296: 38:48:4c:22:52:16 Adding BSSID f0:29:29:eb:50:ae to PMKID cache at index 0 for station 38:48:4c:22:52:16
  131. *Dot1x_NW_MsgTask_6: May 13 15:33:27.296: New PMKID: (16)
  132.  
  133. *Dot1x_NW_MsgTask_6: May 13 15:33:27.296: [0000] 76 92 6c 9a 6c a0 a5 11 f0 f1 15 f4 d3 b9 d8 33
  134.  
  135. *Dot1x_NW_MsgTask_6: May 13 15:33:27.296: 38:48:4c:22:52:16 Disabling re-auth since PMK lifetime can take care of same.
  136. *Dot1x_NW_MsgTask_6: May 13 15:33:27.296: 38:48:4c:22:52:16 unsetting PmkIdValidatedByAp
  137. *Dot1x_NW_MsgTask_6: May 13 15:33:27.296: 38:48:4c:22:52:16 PMK sent to mobility group
  138. *Dot1x_NW_MsgTask_6: May 13 15:33:27.296: 38:48:4c:22:52:16 Sending EAP-Success to mobile 38:48:4c:22:52:16 (EAP Id 198)
  139. *Dot1x_NW_MsgTask_6: May 13 15:33:27.296: 38:48:4c:22:52:16 Found an cache entry for BSSID f0:29:29:eb:50:ae in PMKID cache at index 0 of station 38:48:4c:22:52:16
  140. *Dot1x_NW_MsgTask_6: May 13 15:33:27.296: 38:48:4c:22:52:16 Found an cache entry for BSSID f0:29:29:eb:50:ae in PMKID cache at index 0 of station 38:48:4c:22:52:16
  141. *Dot1x_NW_MsgTask_6: May 13 15:33:27.296: Including PMKID in M1 (16)
  142.  
  143. *Dot1x_NW_MsgTask_6: May 13 15:33:27.296: [0000] 76 92 6c 9a 6c a0 a5 11 f0 f1 15 f4 d3 b9 d8 33
  144.  
  145. *Dot1x_NW_MsgTask_6: May 13 15:33:27.296: 38:48:4c:22:52:16 Starting key exchange to mobile 38:48:4c:22:52:16, data packets will be dropped
  146. *Dot1x_NW_MsgTask_6: May 13 15:33:27.296: 38:48:4c:22:52:16 Sending EAPOL-Key Message to mobile 38:48:4c:22:52:16
  147. state INITPMK (message 1), replay counter 00.00.00.00.00.00.00.00
  148. *Dot1x_NW_MsgTask_6: May 13 15:33:27.296: 38:48:4c:22:52:16 Entering Backend Auth Success state (id=198) for mobile 38:48:4c:22:52:16
  149. *Dot1x_NW_MsgTask_6: May 13 15:33:27.296: 38:48:4c:22:52:16 Received Auth Success while in Authenticating state for mobile 38:48:4c:22:52:16
  150. *Dot1x_NW_MsgTask_6: May 13 15:33:27.296: 38:48:4c:22:52:16 dot1x - moving mobile 38:48:4c:22:52:16 into Authenticated state
  151. *Dot1x_NW_MsgTask_6: May 13 15:33:27.302: 38:48:4c:22:52:16 Received EAPOL-Key from mobile 38:48:4c:22:52:16
  152. *Dot1x_NW_MsgTask_6: May 13 15:33:27.302: 38:48:4c:22:52:16 Received EAPOL-key in PTK_START state (message 2) from mobile 38:48:4c:22:52:16
  153. *Dot1x_NW_MsgTask_6: May 13 15:33:27.302: 38:48:4c:22:52:16 PMK: Sending cache add
  154. *Dot1x_NW_MsgTask_6: May 13 15:33:27.302: 38:48:4c:22:52:16 Stopping retransmission timer for mobile 38:48:4c:22:52:16
  155. *Dot1x_NW_MsgTask_6: May 13 15:33:27.302: 38:48:4c:22:52:16 Sending the random GTK in M3 for WPA2 client 38:48:4c:22:52:16
  156. *Dot1x_NW_MsgTask_6: May 13 15:33:27.303: 38:48:4c:22:52:16 Sending EAPOL-Key Message to mobile 38:48:4c:22:52:16
  157. state PTKINITNEGOTIATING (message 3), replay counter 00.00.00.00.00.00.00.01
  158. *Dot1x_NW_MsgTask_6: May 13 15:33:27.310: 38:48:4c:22:52:16 Received EAPOL-Key from mobile 38:48:4c:22:52:16
  159. *Dot1x_NW_MsgTask_6: May 13 15:33:27.310: 38:48:4c:22:52:16 Received EAPOL-key in PTKINITNEGOTIATING state (message 4) from mobile 38:48:4c:22:52:16
  160. *Dot1x_NW_MsgTask_6: May 13 15:33:27.310: 38:48:4c:22:52:16 apfMs1xStateInc
  161. *Dot1x_NW_MsgTask_6: May 13 15:33:27.310: 38:48:4c:22:52:16 0.0.0.0 8021X_REQD (3) Change state to L2AUTHCOMPLETE (4) last state RUN (20)
  162.  
  163. *Dot1x_NW_MsgTask_6: May 13 15:33:27.310: 38:48:4c:22:52:16 0.0.0.0 L2AUTHCOMPLETE (4) DHCP required on AP f0:29:29:eb:50:a0 vapId 2 apVapId 2for this client
  164. *Dot1x_NW_MsgTask_6: May 13 15:33:27.310: 38:48:4c:22:52:16 Not Using WMM Compliance code qosCap 00
  165. *Dot1x_NW_MsgTask_6: May 13 15:33:27.310: 38:48:4c:22:52:16 0.0.0.0 L2AUTHCOMPLETE (4) Plumbed mobile LWAPP rule on AP f0:29:29:eb:50:a0 vapId 2 apVapId 2
  166. *Dot1x_NW_MsgTask_6: May 13 15:33:27.310: 38:48:4c:22:52:16 apfMsRunStateInc
  167. *Dot1x_NW_MsgTask_6: May 13 15:33:27.310: 38:48:4c:22:52:16 0.0.0.0 L2AUTHCOMPLETE (4) Change state to RUN (20) last state RUN (20)
  168.  
  169. *Dot1x_NW_MsgTask_6: May 13 15:33:27.310: 38:48:4c:22:52:16 0.0.0.0 RUN (20) Reached PLUMBFASTPATH: from line 5362
  170. *Dot1x_NW_MsgTask_6: May 13 15:33:27.262: 38:48:4c:22:52:16 0.0.0.0 RUN (20) Adding Fast Path rule
  171. type = Airespace AP Client
  172. on AP f0:29:29:eb:50:a0, slot 1, interface = 2, QOS = 0
  173. IPv4 ACL ID = 5, IPv6 ACL ID = 255, Jum
  174. *Dot1x_NW_MsgTask_6: May 13 15:33:27.310: 38:48:4c:22:52:16 0.0.0.0 RUN (20) Fast Path rule (contd...) 802.1P = 0, DSCP = 0, TokenID = 7006 Local Bridging Vlan = 930, Local Bridging intf id = 11
  175. *Dot1x_NW_MsgTask_6: May 13 15:33:27.310: 38:48:4c:22:52:16 0.0.0.0 RUN (20) Successfully plumbed mobile rule (IPv4 ACL ID 5, IPv6 ACL ID 255)
  176. *Dot1x_NW_MsgTask_6: May 13 15:33:27.310: 38:48:4c:22:52:16 Stopping retransmission timer for mobile 38:48:4c:22:52:16
  177. *pemReceiveTask: May 13 15:33:27.311: 38:48:4c:22:52:16 0.0.0.0 Added NPU entry of type 1, dtlFlags 0x0
  178. *pemReceiveTask: May 13 15:33:27.311: 38:48:4c:22:52:16 Pushing IPv6: fe80:0000:0000:0000: 0811:016e:54d2:433f , and MAC: 38:48:4C:22:52:16 , Binding to Data Plane. SUCCESS !!
  179. *DHCP Socket Task: May 13 15:33:28.359: 38:48:4c:22:52:16 DHCP received op BOOTREQUEST (1) (len 308,vlan 910, port 2, encap 0xec03)
  180. *DHCP Socket Task: May 13 15:33:28.359: 38:48:4c:22:52:16 DHCP selecting relay 1 - control block settings:
  181. dhcpServer: 0.0.0.0, dhcpNetmask: 0.0.0.0,
  182. dhcpGateway: 0.0.0.0, dhcpRelay: 0.0.0.0 VLAN: 0
  183. *DHCP Socket Task: May 13 15:33:28.359: 38:48:4c:22:52:16 DHCP selected relay 1 - 192.168.1.1 (local address 192.168.3.1, gateway 192.168.3.10, VLAN 930, port 1)
  184. *DHCP Socket Task: May 13 15:33:28.359: 38:48:4c:22:52:16 DHCP transmitting DHCP DISCOVER (1)
  185. *DHCP Socket Task: May 13 15:33:28.359: 38:48:4c:22:52:16 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 1
  186. *DHCP Socket Task: May 13 15:33:28.359: 38:48:4c:22:52:16 DHCP xid: 0x2a19d8d7 (706336983), secs: 1, flags: 0
  187. *DHCP Socket Task: May 13 15:33:28.359: 38:48:4c:22:52:16 DHCP chaddr: 38:48:4c:22:52:16
  188. *DHCP Socket Task: May 13 15:33:28.359: 38:48:4c:22:52:16 DHCP ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
  189. *DHCP Socket Task: May 13 15:33:28.359: 38:48:4c:22:52:16 DHCP siaddr: 0.0.0.0, giaddr: 192.168.3.1
  190. *DHCP Socket Task: May 13 15:33:28.359: 38:48:4c:22:52:16 DHCP selecting relay 2 - control block settings:
  191. dhcpServer: 0.0.0.0, dhcpNetmask: 0.0.0.0,
  192. dhcpGateway: 0.0.0.0, dhcpRelay: 192.168.3.1 VLAN: 930
  193. *DHCP Socket Task: May 13 15:33:28.359: 38:48:4c:22:52:16 DHCP selected relay 2 - NONE
  194. *DHCP Proxy Task: May 13 15:33:28.360: 38:48:4c:22:52:16 DHCP received op BOOTREPLY (2) (len 572,vlan 0, port 0, encap 0x0)
  195. *DHCP Proxy Task: May 13 15:33:28.360: 38:48:4c:22:52:16 DHCP setting server from OFFER (server 192.168.1.1, yiaddr 192.168.3.40)
  196. *DHCP Proxy Task: May 13 15:33:28.360: 38:48:4c:22:52:16 DHCP sending REPLY to STA (len 418, port 2, vlan 910)
  197. *DHCP Proxy Task: May 13 15:33:28.360: 38:48:4c:22:52:16 DHCP transmitting DHCP OFFER (2)
  198. *DHCP Proxy Task: May 13 15:33:28.360: 38:48:4c:22:52:16 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
  199. *DHCP Proxy Task: May 13 15:33:28.360: 38:48:4c:22:52:16 DHCP xid: 0x2a19d8d7 (706336983), secs: 0, flags: 0
  200. *DHCP Proxy Task: May 13 15:33:28.360: 38:48:4c:22:52:16 DHCP chaddr: 38:48:4c:22:52:16
  201. *DHCP Proxy Task: May 13 15:33:28.360: 38:48:4c:22:52:16 DHCP ciaddr: 0.0.0.0, yiaddr: 192.168.3.40
  202. *DHCP Proxy Task: May 13 15:33:28.360: 38:48:4c:22:52:16 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
  203. *DHCP Proxy Task: May 13 15:33:28.360: 38:48:4c:22:52:16 DHCP server id: 1.1.1.1 rcvd server id: 192.168.1.1
  204. *DHCP Socket Task: May 13 15:33:29.399: 38:48:4c:22:52:16 DHCP received op BOOTREQUEST (1) (len 308,vlan 910, port 2, encap 0xec03)
  205. *DHCP Socket Task: May 13 15:33:29.399: 38:48:4c:22:52:16 DHCP selecting relay 1 - control block settings:
  206. dhcpServer: 192.168.1.1, dhcpNetmask: 0.0.0.0,
  207. dhcpGateway: 0.0.0.0, dhcpRelay: 192.168.3.1 VLAN: 930
  208. *DHCP Socket Task: May 13 15:33:29.399: 38:48:4c:22:52:16 DHCP selected relay 1 - 192.168.1.1 (local address 192.168.3.1, gateway 192.168.3.10, VLAN 930, port 1)
  209. *DHCP Socket Task: May 13 15:33:29.399: 38:48:4c:22:52:16 DHCP transmitting DHCP REQUEST (3)
  210. *DHCP Socket Task: May 13 15:33:29.399: 38:48:4c:22:52:16 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 1
  211. *DHCP Socket Task: May 13 15:33:29.399: 38:48:4c:22:52:16 DHCP xid: 0x2a19d8d7 (706336983), secs: 2, flags: 0
  212. *DHCP Socket Task: May 13 15:33:29.399: 38:48:4c:22:52:16 DHCP chaddr: 38:48:4c:22:52:16
  213. *DHCP Socket Task: May 13 15:33:29.399: 38:48:4c:22:52:16 DHCP ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
  214. *DHCP Socket Task: May 13 15:33:29.399: 38:48:4c:22:52:16 DHCP siaddr: 0.0.0.0, giaddr: 192.168.3.1
  215. *DHCP Socket Task: May 13 15:33:29.399: 38:48:4c:22:52:16 DHCP requested ip: 192.168.3.40
  216. *DHCP Socket Task: May 13 15:33:29.399: 38:48:4c:22:52:16 DHCP server id: 192.168.1.1 rcvd server id: 1.1.1.1
  217. *DHCP Socket Task: May 13 15:33:29.399: 38:48:4c:22:52:16 DHCP selecting relay 2 - control block settings:
  218. dhcpServer: 192.168.1.1, dhcpNetmask: 0.0.0.0,
  219. dhcpGateway: 0.0.0.0, dhcpRelay: 192.168.3.1 VLAN: 930
  220. *DHCP Socket Task: May 13 15:33:29.399: 38:48:4c:22:52:16 DHCP selected relay 2 - NONE
  221. *DHCP Proxy Task: May 13 15:33:29.399: 38:48:4c:22:52:16 DHCP received op BOOTREPLY (2) (len 572,vlan 0, port 0, encap 0x0)
  222. *DHCP Proxy Task: May 13 15:33:29.400: 38:48:4c:22:52:16 192.168.3.40 RUN (20) DHCP Address Re-established
  223. *DHCP Proxy Task: May 13 15:33:29.400: 38:48:4c:22:52:16 192.168.3.40 RUN (20) Reached PLUMBFASTPATH: from line 6091
  224. *DHCP P: May 13 15:33:29.400: 38:48:4c:22:52:16 192.168.3.40 RUN (20) Replacing Fast Path rule
  225. type = Airespace AP Client
  226. on AP f0:29:29:eb:50:a0, slot 1, interface = 2, QOS = 0
  227. IPv4 ACL ID = 5, IPv6 ACL ID =
  228. *DHCP Proxy Task: May 13 15:33:29.400: 38:48:4c:22:52:16 192.168.3.40 RUN (20) Fast Path rule (contd...) 802.1P = 0, DSCP = 0, TokenID = 7006 Local Bridging Vlan = 930, Local Bridging intf id = 11
  229. *DHCP Proxy Task: May 13 15:33:29.400: 38:48:4c:22:52:16 192.168.3.40 RUN (20) Successfully plumbed mobile rule (IPv4 ACL ID 5, IPv6 ACL ID 255)
  230. *DHCP Proxy Task: May 13 15:33:29.400: 38:48:4c:22:52:16 Assigning Address 192.168.3.40 to mobile
  231. *DHCP Proxy Task: May 13 15:33:29.400: 38:48:4c:22:52:16 DHCP success event for client. Clearing dhcp failure count for interface employee.
  232. *DHCP Proxy Task: May 13 15:33:29.400: 38:48:4c:22:52:16 DHCP sending REPLY to STA (len 418, port 2, vlan 910)
  233. *DHCP Proxy Task: May 13 15:33:29.400: 38:48:4c:22:52:16 DHCP transmitting DHCP ACK (5)
  234. *DHCP Proxy Task: May 13 15:33:29.400: 38:48:4c:22:52:16 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
  235. *DHCP Proxy Task: May 13 15:33:29.400: 38:48:4c:22:52:16 DHCP xid: 0x2a19d8d7 (706336983), secs: 0, flags: 0
  236. *DHCP Proxy Task: May 13 15:33:29.400: 38:48:4c:22:52:16 DHCP chaddr: 38:48:4c:22:52:16
  237. *DHCP Proxy Task: May 13 15:33:29.400: 38:48:4c:22:52:16 DHCP ciaddr: 0.0.0.0, yiaddr: 192.168.3.40
  238. *DHCP Proxy Task: May 13 15:33:29.400: 38:48:4c:22:52:16 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
  239. *DHCP Proxy Task: May 13 15:33:29.400: 38:48:4c:22:52:16 DHCP server id: 1.1.1.1 rcvd server id: 192.168.1.1
  240. *pemReceiveTask: May 13 15:33:29.401: 38:48:4c:22:52:16 192.168.3.40 Added NPU entry of type 1, dtlFlags 0x0
  241. *pemReceiveTask: May 13 15:33:29.401: 38:48:4c:22:52:16 Pushing IPv6: fe80:0000:0000:0000: 0811:016e:54d2:433f , and MAC: 38:48:4C:22:52:16 , Binding to Data Plane. SUCCESS !!
Advertisement
Add Comment
Please, Sign In to add comment
Public Pastes
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!