 
| Subject: | |
| From: | |
| Reply To: | |
| Date: | Wed, 30 Sep 2009 15:19:16 +0000 |
| Content-Type: | text/plain |
| Parts/Attachments: |
|
|
For those interested in the result, we have made some progress on this issue after long hours of troubleshooting.
=> this is a supported combination
=> WLAN AAA override feature MUST be disabled !
We now see something this in logs :
2009-09-30 19:02:51.151 +0400 TRACE com.perfigo.wlan.web.sms.snmp4j.SwitchTrapReceiver - Received a SNMP TRAP/INFORM packet: Type = -89: TRAP[requestID=163, errorStatus=Success(0), errorIndex=0, VBS[1.3.6.1.2.1.1.3.0 = 0:17:21.00; 1.3.6.1.6.3.1.1.4.1.0 = 1.3.6.1.4.1.9.9.599.0.2; 1.3.6.1.4.1.9.9.599.1.3.1.1.1.0.28.191.122.140.23 = 00:1c:bf:7a:8c:17; 1.3.6.1.4.1.9.9.599.1.3.1.1.3.0.28.191.122.140.23 = skolkovo; 1.3.6.1.4.1.9.9.599.1.3.1.1.10.0.28.191.122.140.23 = 0.0.0.0; 1.3.6.1.4.1.9.9.599.1.3.1.1.8.0.28.191.122.140.23 = 00:23:5d:0e:5d:50; 1.3.6.1.4.1.9.9.599.1.3.1.1.12.0.28.191.122.140.23 = 2511; 1.3.6.1.4.1.9.9.599.1.3.1.1.13.0.28.191.122.140.23 = 511]]
2009-09-30 19:02:51.151 +0400 TRACE com.perfigo.wlan.web.sms.snmp4j.SwitchTrapReceiver - Received SNMP v2/v3 trap from 10.2.130.8.
2009-09-30 19:02:51.151 +0400 TRACE com.perfigo.wlan.web.sms.snmp4j.SwitchTrapReceiver - GET LWAPP TRAP: 1.3.6.1.4.1.9.9.599.0.2
2009-09-30 19:02:51.151 +0400 TRACE com.perfigo.wlan.web.sms.snmp4j.SwitchTrapReceiver - WLC Trap: client mac = 00:1C:BF:7A:8C:17
2009-09-30 19:02:51.151 +0400 TRACE com.perfigo.wlan.web.sms.snmp4j.SwitchTrapReceiver - WLC Trap: ssid = skolkovo
2009-09-30 19:02:51.151 +0400 TRACE com.perfigo.wlan.web.sms.snmp4j.SwitchTrapReceiver - WLC Trap: client ip = 0.0.0.0
2009-09-30 19:02:51.151 +0400 TRACE com.perfigo.wlan.web.sms.snmp4j.SwitchTrapReceiver - WLC Trap: ap mac = 00:23:5D:0E:5D:50
2009-09-30 19:02:51.151 +0400 TRACE com.perfigo.wlan.web.sms.snmp4j.SwitchTrapReceiver - WLC Trap: quaratine vlan = 2511
2009-09-30 19:02:51.151 +0400 TRACE com.perfigo.wlan.web.sms.snmp4j.SwitchTrapReceiver - WLC Trap: access vlan = 511
2009-09-30 19:02:51.151 +0400 INFO com.perfigo.wlan.web.sms.SnmpTrapListener - Received trap event WlcTrapEvent [type=LWAPP_ASSOC wlc_ip=10.2.130.8 mac=00:1C:BF:7A:8C:17 ip=0.0.0.0 ssid=skolkovo apmac=00:23:5D:0E:5D:50 qvlan=2511 avlan=511]
2009-09-30 19:02:51.151 +0400 DEBUG com.perfigo.wlan.web.sms.SnmpRunnable - SnmpRunnable com.perfigo.wlan.web.sms.task.WlcNotificationTask id=33 is created: WlcTrapEvent [type=LWAPP_ASSOC wlc_ip=10.2.130.8 mac=00:1C:BF:7A:8C:17 ip=0.0.0.0 ssid=skolkovo apmac=00:23:5D:0E:5D:50 qvlan=2511 avlan=511]
And an entry in wireless discovered clients.
-----Original Message-----
From: Cisco Clean Access Users and Administrators [mailto:[log in to unmask]] On Behalf Of Michaud, Matthieu
Sent: mardi 29 septembre 2009 17:20
To: [log in to unmask]
Subject: NAC 4.6(1) + WLC 6.0.182.0
Hello,
Has anyone made working NAC Appliance 4.6(1) in conjunction with WLC 6.0.182.0 ?
I'm stuck with the CAM receiving the trap from WLC but nothing in discovered clients.
Do you know if it is a known working or not working combination ?
Something in the logs is ticking me :
2009-09-29 17:52:09.807 +0400 TRACE com.perfigo.wlan.web.sms.snmp4j.SwitchTrapReceiver - Received a SNMP TRAP/INFORM packet: Type = -89: TRAP[requestID=1969, errorStatus=Success(0), errorIndex=0, VBS[1.3.6.1.2.1.1.3.0 = 74 days, 19:40:28.00; 1.3.6.1.6.3.1.1.4.1.0 = 1.3.6.1.4.1.14179.2.6.3.53; 1.3.6.1.4.1.14179.2.6.2.35.0 = 00:23:ab:bf:ea:40; 1.3.6.1.4.1.14179.2.6.2.36.0 = 0; 1.3.6.1.4.1.14179.2.6.2.34.0 = 00:1d:e0:36:d3:f3; 1.3.6.1.4.1.14179.2.6.2.43.0 = 0.0.0.0; 1.3.6.1.4.1.14179.2.2.1.1.3.0 = AP0022.901c.4034; 1.3.6.1.4.1.14179.2.6.2.39.0 = wireless1]]
2009-09-29 17:52:09.807 +0400 TRACE com.perfigo.wlan.web.sms.snmp4j.SwitchTrapReceiver - Received SNMP v2/v3 trap from 10.2.130.8.
2009-09-29 17:52:09.808 +0400 TRACE com.perfigo.wlan.web.sms.snmp4j.SwitchTrapReceiver - Unknown SNMP TRAP packet: TRAP[requestID=1969, errorStatus=Success(0), errorIndex=0, VBS[1.3.6.1.2.1.1.3.0 = 74 days, 19:40:28.00; 1.3.6.1.6.3.1.1.4.1.0 = 1.3.6.1.4.1.14179.2.6.3.53; 1.3.6.1.4.1.14179.2.6.2.35.0 = 00:23:ab:bf:ea:40; 1.3.6.1.4.1.14179.2.6.2.36.0 = 0; 1.3.6.1.4.1.14179.2.6.2.34.0 = 00:1d:e0:36:d3:f3; 1.3.6.1.4.1.14179.2.6.2.43.0 = 0.0.0.0; 1.3.6.1.4.1.14179.2.2.1.1.3.0 = AP0022.901c.4034; 1.3.6.1.4.1.14179.2.6.2.39.0 = wireless1]]
Any idea of what might be the root cause ?
Missing OIDs ?
Any help appreciated !
Thanks
Matthieu Michaud
|
|
|
