CAP702 with CT2504
Hi,
we have purchase one CT2504 with 4 nos of CAP702i, but at the time of installation, APs are not joining in controller, in status showing " unknown ap "
Please suggest me what should i do...
Thanks
Debu
HI Debu,
7.5.102.0 is deffered by cisco, so it would be good to download 7.6.120.0 from this link and upload to wlc to connect 702i AP.
Todownlod it you must have CCO account otherwise you nee dto contatc to IR support partnet or your supplier.
Here is the link:
http://software.cisco.com/download/release.html?mdfid=283848165&flowid=24841&softwareid=280926587&release=7.6.120.0&relind=AVAILABLE&rellifecycle=ED&reltype=latest
Hope it helps
Regards
Dont forget to rate helpful posts
Similar Messages
-
Config storage confusion 2504 controller with CAP702I
HI all,
I've been tasked with the rollout of the above mentioned hardware, and I've managed to get so far, but it seems I cannot do a 'copy running-config startup-config' on the CAP702I Aironet access points.
ive got then registered with the controller and radios turned on but the problem is that it the power is cycled the radios turn off, I can SSH into each AP and manually turn them on and it works all fine except I shouldn't need to do that.
If anyone could give me a clue as to how to change the ap config to either store the config with radios enabled on restart on the device itself or guide me through storing the config on the 2504 controller and pointing to it on the ap devices for their startup, it would be much appreciated.So simply wireless clients are not getting ip address from the DHCP scope defined for them on AD DHCP server.
few facts about DHCP handling on WLC:
- With DHCP proxy enabled , the controller acts as relay agent.
Simply you configure primary or may be secondary DHCP server under the interface config.
When the client starts the DHCP process the controller will rekay the clients DHCP packets
in unicast form.
- With DHCP proxy disabled , the controller will not intervene at all, and the client traffic will be sent
as broadcast. If the DHCP server is on different VLAN , you have to configure relay agent under the gateway
of the client vlan so that it can reach the DHCP server.
Please make sure to rate correct answer -
AIR-CT2504-50-K9 with out DHCP Static config
We have AIR-CT2504-50-K9 and AIR-CAP1602I-TK910 30 devices we want config trough controller to AP with out DHCP
#Yes, you can use internal dhcp server on WLC-2500 to lease IPs to the connected APs using L2/Broadcast, once AP gets an ip then you can make those IPs as static on those APs via check box from AP's general tab after it joins the WLC.
#Remeber, WLC dhcp doesn't support option 43, if the AP and WLC management are L3, be sure to use ip-helper at L3 for wlc discovery. Also, don't think AP may receive ip from WLC dhcp server when it is L3 and dhcp proxy is used instead of broadcast. -
Issue with Wireless AP.
Hi All,
Greetings.
we have an issue with user who says that he is unable to connect to AP and he need to re-boot it everytime to re-connect to it.
But when i check from WLC all the AP uptime is more than 150 days and the AP associate time of respective AP's is also more than 150 days.we are using cisco AIR-CT2504-K9 wlc and all the AP's are connected to Cisco 3750X and cisco4510R+E.please suggest.
pasting logs from wlc below.
Tue Feb 26 17:06:05 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 207) for client 88:53:95:7b:8f:56 / user 'unknown'
1 Tue Feb 26 17:06:05 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
2 Tue Feb 26 17:06:05 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
3 Tue Feb 26 17:06:05 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 206) for client 60:c5:47:44:4d:d7 / user 'unknown'
4 Tue Feb 26 17:06:05 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 191) for client 88:53:95:7b:8f:56 / user 'unknown'
5 Tue Feb 26 17:06:05 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
6 Tue Feb 26 17:06:05 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
7 Tue Feb 26 17:06:05 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 190) for client 60:c5:47:44:4d:d7 / user 'unknown'
8 Tue Feb 26 16:51:24 2013 User guest logged Out. Client MAC:8c:a9:82:ae:a2:4a, Client IP:10.40.101.33, AP MAC:0c:85:25:c7:dc:e0, AP Name:NTW100-AP07
9 Tue Feb 26 16:45:16 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
10 Tue Feb 26 16:45:16 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
11 Tue Feb 26 16:45:16 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 44) for client 10:40:f3:5e:3b:26 / user 'unknown'
12 Tue Feb 26 16:45:16 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
13 Tue Feb 26 16:45:16 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
14 Tue Feb 26 16:45:16 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 204) for client 10:40:f3:5e:3b:26 / user 'unknown'
15 Tue Feb 26 16:05:29 2013 RADIUS server 10.12.2.34:1813 activated in global list
16 Tue Feb 26 16:05:29 2013 RADIUS server 10.12.2.33:1813 deactivated in global list
17 Tue Feb 26 16:05:29 2013 RADIUS server 10.12.2.33:1813 deactivated in global list
18 Tue Feb 26 16:05:29 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 113) for client b8:c7:5d:e0:48:be / user 'unknown'
19 Tue Feb 26 16:05:29 2013 RADIUS server 10.12.2.33:1813 activated in global list
20 Tue Feb 26 16:05:29 2013 RADIUS server 10.19.3.104:1813 deactivated in global list
21 Tue Feb 26 16:05:29 2013 RADIUS server 10.19.3.104:1813 deactivated in global list
22 Tue Feb 26 16:05:29 2013 RADIUS server 10.19.3.104:1813 failed to respond to request (ID 132) for client b8:c7:5d:e0:48:be / user 'unknown'
23 Tue Feb 26 16:05:17 2013 User guest logged Out. Client MAC:00:22:fa:95:d2:58, Client IP:10.40.101.69, AP MAC:0c:85:25:c7:dc:e0, AP Name:NTW100-AP07
24 Tue Feb 26 15:42:36 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
25 Tue Feb 26 15:42:36 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
26 Tue Feb 26 15:42:36 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 111) for client 7c:c5:37:18:ca:2b / user 'unknown'
27 Tue Feb 26 15:35:53 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 247) for client 68:a8:6d:e9:7d:36 / user 'unknown'
28 Tue Feb 26 15:35:53 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
29 Tue Feb 26 15:35:53 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
30 Tue Feb 26 15:35:53 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 246) for client 68:a8:6d:e9:7d:36 / user 'unknown'
31 Tue Feb 26 15:35:53 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 137) for client 68:a8:6d:e9:7d:36 / user 'unknown'
32 Tue Feb 26 15:35:53 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
33 Tue Feb 26 15:35:53 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
34 Tue Feb 26 15:35:53 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 136) for client 68:a8:6d:e9:7d:36 / user 'unknown'
35 Tue Feb 26 15:06:17 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
36 Tue Feb 26 15:06:17 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
37 Tue Feb 26 15:06:17 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 67) for client 24:ab:81:af:2f:da / user 'unknown'
38 Tue Feb 26 14:49:54 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
39 Tue Feb 26 14:49:54 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
40 Tue Feb 26 14:49:54 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 245) for client b8:17:c2:49:d5:37 / user 'unknown'
41 Tue Feb 26 14:49:54 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 229) for client c0:9f:42:65:37:af / user 'unknown'
42 Tue Feb 26 14:49:54 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
43 Tue Feb 26 14:49:54 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
44 Tue Feb 26 14:49:54 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 230) for client 60:fa:cd:b6:f6:d6 / user 'unknown'
45 Tue Feb 26 14:49:54 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
46 Tue Feb 26 14:49:54 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
47 Tue Feb 26 14:49:54 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 228) for client b8:17:c2:49:d5:37 / user 'unknown'
48 Tue Feb 26 14:49:54 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 243) for client c0:9f:42:65:37:af / user 'unknown'
49 Tue Feb 26 14:49:54 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
50 Tue Feb 26 14:49:54 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
51 Tue Feb 26 14:49:54 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 242) for client 60:fa:cd:b6:f6:d6 / user 'unknown'
52 Tue Feb 26 14:14:41 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 227) for client 0c:77:1a:a7:97:6e / user 'unknown'
53 Tue Feb 26 14:14:41 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
54 Tue Feb 26 14:14:41 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
55 Tue Feb 26 14:14:41 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 226) for client 0c:77:1a:a7:97:6e / user 'unknown'
56 Tue Feb 26 14:14:41 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 226) for client 0c:77:1a:a7:97:6e / user 'unknown'
57 Tue Feb 26 14:14:41 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
58 Tue Feb 26 14:14:41 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
59 Tue Feb 26 14:14:41 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 225) for client 0c:77:1a:a7:97:6e / user 'unknown'
60 Tue Feb 26 14:13:57 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
61 Tue Feb 26 14:13:57 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
62 Tue Feb 26 14:13:57 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 34) for client ec:85:2f:a2:4d:ba / user 'unknown'
63 Tue Feb 26 14:13:57 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
64 Tue Feb 26 14:13:57 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
65 Tue Feb 26 14:13:57 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 225) for client ec:85:2f:a2:4d:ba / user 'unknown'
66 Tue Feb 26 13:22:55 2013 Radar signals have been cleared on channel 52 by 802.11a radio with MAC: 00:1f:ca:cc:f0:00 and slot 1
67 Tue Feb 26 13:20:02 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 214) for client e8:8d:28:7f:0e:5a / user 'unknown'
68 Tue Feb 26 13:20:02 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
69 Tue Feb 26 13:20:02 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
70 Tue Feb 26 13:20:02 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 213) for client e8:8d:28:7f:0e:5a / user 'unknown'
71 Tue Feb 26 13:20:02 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 33) for client e8:8d:28:7f:0e:5a / user 'unknown'
72 Tue Feb 26 13:20:02 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
73 Tue Feb 26 13:20:02 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
74 Tue Feb 26 13:20:02 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 32) for client e8:8d:28:7f:0e:5a / user 'unknown'
75 Tue Feb 26 12:52:55 2013 AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:00:1f:ca:cc:f0:00 Cause=Radio channel set. Status:NA
76 Tue Feb 26 12:52:54 2013 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1f:ca:cc:f0:00 Cause=Radio channel set. Status:NA
77 Tue Feb 26 12:52:54 2013 Radar signals have been detected on channel 52 by 802.11a radio with MAC: 00:1f:ca:cc:f0:00 and slot 1
78 Tue Feb 26 12:48:34 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 164) for client 7c:c5:37:18:ca:2b / user 'unknown'
79 Tue Feb 26 12:48:34 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
80 Tue Feb 26 12:48:34 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
81 Tue Feb 26 12:48:34 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 163) for client 7c:c5:37:18:ca:2b / user 'unknown'
82 Tue Feb 26 12:48:34 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 212) for client 7c:c5:37:18:ca:2b / user 'unknown'
83 Tue Feb 26 12:48:34 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
84 Tue Feb 26 12:48:34 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
85 Tue Feb 26 12:48:34 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 211) for client 7c:c5:37:18:ca:2b / user 'unknown'
86 Tue Feb 26 12:45:09 2013 AP NTW100-AP07[1] (0c:85:25:c7:dc:e0) Device ID: 0x2019, Type: WiFi Invalid Channel[31], Severity: 2, Channels: 161, Cluster ID: 1c:75:a0:02:41:22, Previous Cluster ID: 1c:75:a0:02:41:22, Event: Clear
87 Tue Feb 26 12:42:07 2013 AP NTW100-AP07[1] (0c:85:25:c7:dc:e0) Device ID: 0x2019, Type: WiFi Invalid Channel[31], Severity: 3, Channels: 161, Cluster ID: 1c:75:a0:02:41:22, Previous Cluster ID: 1c:75:a0:02:41:22, Event: Set
88 Tue Feb 26 12:41:25 2013 AP NTW100-AP07[1] (0c:85:25:c7:dc:e0) Device ID: 0x2018, Type: WiFi Invalid Channel[31], Severity: 2, Channels: 161, Cluster ID: 1c:75:a0:02:41:22, Previous Cluster ID: 1c:75:a0:02:41:22, Event: Clear
89 Tue Feb 26 12:37:38 2013 AP NTW100-AP07[1] (0c:85:25:c7:dc:e0) Device ID: 0x2018, Type: WiFi Invalid Channel[31], Severity: 2, Channels: 161, Cluster ID: 1c:75:a0:02:41:22, Previous Cluster ID: 1c:75:a0:02:41:22, Event: Set
90 Tue Feb 26 12:35:47 2013 AP NTW100-AP07[1] (0c:85:25:c7:dc:e0) Device ID: 0x2017, Type: WiFi Invalid Channel[31], Severity: 2, Channels: 161, Cluster ID: 1c:75:a0:02:41:01, Previous Cluster ID: 1c:75:a0:02:41:01, Event: Clear
91 Tue Feb 26 12:20:01 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 115) for client e8:8d:28:7f:0e:5a / user 'unknown'
92 Tue Feb 26 12:20:01 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
93 Tue Feb 26 12:20:01 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
94 Tue Feb 26 12:20:01 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 114) for client e8:8d:28:7f:0e:5a / user 'unknown'
95 Tue Feb 26 12:20:01 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 162) for client e8:8d:28:7f:0e:5a / user 'unknown'
96 Tue Feb 26 12:20:01 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
97 Tue Feb 26 12:20:01 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
98 Tue Feb 26 12:20:01 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 161) for client e8:8d:28:7f:0e:5a / user 'unknown'
99 Tue Feb 26 12:18:26 2013 User inventiv-guest logged in. Client MAC:8c:a9:82:ae:a2:4a, Client IP:10.40.101.33, AP MAC:0c:85:25:c7:dc:e0, AP Name:NTW100-AP07
100 Tue Feb 26 12:11:01 2013 RADIUS server 10.12.50.52:1813 failed to respond to request (ID 106) for client a4:67:06:dd:ed:6a / user 'unknown'
101 Tue Feb 26 12:11:01 2013 RADIUS server 10.19.3.104:1813 activated in global list
102 Tue Feb 26 12:11:01 2013 RADIUS server 10.12.50.52:1813 deactivated in global list
103 Tue Feb 26 12:11:01 2013 RADIUS server 10.12.50.52:1813 deactivated in global list
104 Tue Feb 26 12:11:01 2013 RADIUS server 10.12.50.52:1813 failed to respond to request (ID 105) for client a4:67:06:dd:ed:6a / user 'unknown'
105 Tue Feb 26 12:11:01 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 108) for client a4:67:06:dd:ed:6a / user 'unknown'
106 Tue Feb 26 12:11:01 2013 RADIUS server 10.12.50.52:1813 activated in global list
107 Tue Feb 26 12:11:01 2013 RADIUS server 10.19.3.108:1813 deactivated in global list
108 Tue Feb 26 12:11:01 2013 RADIUS server 10.19.3.108:1813 deactivated in global list
109 Tue Feb 26 12:11:01 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 107) for client a4:67:06:dd:ed:6a / user 'unknown'
110 Tue Feb 26 12:10:12 2013 AP NTW100-AP07[1] (0c:85:25:c7:dc:e0) Device ID: 0x2017, Type: WiFi Invalid Channel[31], Severity: 0, Channels: 161, Cluster ID: 1c:75:a0:02:41:01, Previous Cluster ID: 1c:75:a0:02:41:01, Event: Set
111 Tue Feb 26 11:45:29 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 68) for client 28:e0:2c:38:64:b3 / user 'unknown'
112 Tue Feb 26 11:45:29 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
113 Tue Feb 26 11:45:29 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
114 Tue Feb 26 11:45:29 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 67) for client 28:e0:2c:38:64:b3 / user 'unknown'
115 Tue Feb 26 11:45:29 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 113) for client 28:e0:2c:38:64:b3 / user 'unknown'
116 Tue Feb 26 11:45:29 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
117 Tue Feb 26 11:45:29 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
118 Tue Feb 26 11:45:29 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 112) for client 28:e0:2c:38:64:b3 / user 'unknown'
119 Tue Feb 26 11:42:27 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
120 Tue Feb 26 11:42:27 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
121 Tue Feb 26 11:42:27 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 183) for client 7c:c5:37:18:ca:2b / user 'unknown'
122 Tue Feb 26 11:14:06 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
123 Tue Feb 26 11:14:06 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
124 Tue Feb 26 11:14:06 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 65) for client 7c:c5:37:18:ca:2b / user 'unknown'
125 Tue Feb 26 11:06:56 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 93) for client ec:85:2f:a2:4d:ba / user 'unknown'
126 Tue Feb 26 11:06:56 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
127 Tue Feb 26 11:06:56 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
128 Tue Feb 26 11:06:56 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 92) for client ec:85:2f:a2:4d:ba / user 'unknown'
129 Tue Feb 26 11:06:56 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 200) for client ec:85:2f:a2:4d:ba / user 'unknown'
130 Tue Feb 26 11:06:56 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
131 Tue Feb 26 11:06:56 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
132 Tue Feb 26 11:06:56 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 199) for client ec:85:2f:a2:4d:ba / user 'unknown'
133 Tue Feb 26 10:54:54 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
134 Tue Feb 26 10:54:54 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
135 Tue Feb 26 10:54:54 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 16) for client 34:15:9e:f0:00:bf / user 'unknown'
136 Tue Feb 26 10:54:54 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
137 Tue Feb 26 10:54:54 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
138 Tue Feb 26 10:54:54 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 90) for client 34:15:9e:f0:00:bf / user 'unknown'
139 Tue Feb 26 10:46:56 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
140 Tue Feb 26 10:46:56 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
141 Tue Feb 26 10:46:56 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 38) for client ec:85:2f:eb:d0:0b / user 'unknown'
142 Tue Feb 26 10:46:56 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
143 Tue Feb 26 10:46:56 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
144 Tue Feb 26 10:46:56 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 15) for client ec:85:2f:a2:4d:ba / user 'unknown'
145 Tue Feb 26 10:46:56 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 31) for client 60:fa:cd:b6:f6:d6 / user 'unknown'
146 Tue Feb 26 10:46:56 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
147 Tue Feb 26 10:46:56 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
148 Tue Feb 26 10:46:56 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 32) for client ec:85:2f:eb:d0:0b / user 'unknown'
149 Tue Feb 26 10:46:56 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 35) for client ec:85:2f:a2:4d:ba / user 'unknown'
150 Tue Feb 26 10:46:56 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
151 Tue Feb 26 10:46:56 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
152 Tue Feb 26 10:46:56 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 34) for client 60:fa:cd:b6:f6:d6 / user 'unknown'
153 Tue Feb 26 10:41:10 2013 AP NTW100-AP17[0] (18:33:9d:b7:a0:70) Device ID: 0x319a, Type: WiFi Invalid Channel[31], Severity: 2, Channels: 6, Cluster ID: 1c:75:a0:02:40:c7, Previous Cluster ID: 1c:75:a0:02:40:c7, Event: Clear
154 Tue Feb 26 10:38:54 2013 AP NTW100-AP17[0] (18:33:9d:b7:a0:70) Device ID: 0x319a, Type: WiFi Invalid Channel[31], Severity: 2, Channels: 6, Cluster ID: 1c:75:a0:02:40:c7, Previous Cluster ID: 1c:75:a0:02:40:c7, Event: Set
155 Tue Feb 26 10:24:39 2013 AP NTW100-AP17[0] (18:33:9d:b7:a0:70) Device ID: 0x3197, Type: WiFi Invalid Channel[31], Severity: 2, Channels: 6, Cluster ID: 1c:75:a0:02:40:c1, Previous Cluster ID: 1c:75:a0:02:40:c1, Event: Clear
156 Tue Feb 26 10:22:46 2013 AP NTW100-AP17[0] (18:33:9d:b7:a0:70) Device ID: 0x3197, Type: WiFi Invalid Channel[31], Severity: 2, Channels: 6, Cluster ID: 1c:75:a0:02:40:c1, Previous Cluster ID: 1c:75:a0:02:40:c1, Event: Set
157 Tue Feb 26 10:15:02 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 13) for client b4:f0:ab:06:25:b6 / user 'unknown'
158 Tue Feb 26 10:15:02 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
159 Tue Feb 26 10:15:02 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
160 Tue Feb 26 10:15:02 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 12) for client b4:f0:ab:06:25:b6 / user 'unknown'
161 Tue Feb 26 10:15:02 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 30) for client b4:f0:ab:06:25:b6 / user 'unknown'
162 Tue Feb 26 10:15:02 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
163 Tue Feb 26 10:15:02 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
164 Tue Feb 26 10:15:02 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 29) for client b4:f0:ab:06:25:b6 / user 'unknown'
165 Tue Feb 26 09:59:58 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 38) for client ec:85:2f:eb:d0:0b / user 'unknown'
166 Tue Feb 26 09:59:58 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
167 Tue Feb 26 09:59:58 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
168 Tue Feb 26 09:59:58 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 37) for client ec:85:2f:eb:d0:0b / user 'unknown'
169 Tue Feb 26 09:59:58 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 11) for client ec:85:2f:eb:d0:0b / user 'unknown'
170 Tue Feb 26 09:59:58 2013 RADIUS server 10.19.3.108:1813 activated on WLAN 1
171 Tue Feb 26 09:59:58 2013 RADIUS server 10.12.2.33:1813 deactivated on WLAN 1
172 Tue Feb 26 09:59:58 2013 RADIUS server 10.12.2.33:1813 failed to respond to request (ID 10) for client ec:85:2f:eb:d0:0b / user 'unknown'
173 Tue Feb 26 09:49:25 2013 RADIUS server 10.12.2.33:1813 activated on WLAN 1
174 Tue Feb 26 09:49:25 2013 RADIUS server 10.12.2.34:1813 deactivated on WLAN 1
175 Tue Feb 26 09:49:25 2013 RADIUS server 10.12.2.34:1813 failed to respond to request (ID 156) for client 8c:58:77:8e:a3:f6 / user 'unknown'
176 Tue Feb 26 09:46:41 2013 RADIUS server 10.12.2.34:1813 activated on WLAN 1
177 Tue Feb 26 09:46:41 2013 RADIUS server 10.19.3.108:1813 deactivated on WLAN 1
178 Tue Feb 26 09:46:41 2013 RADIUS server 10.19.3.108:1813 failed to respond to request (ID 16) for client 24:ab:81:af:2f:da / user 'unknown'Can you post the output to the command "debug client "?
Can you try if the client has any issues if he was connected to an SSID with OPEN authentication?
Is the wireless NIC drivers updated? -
N+1 redundancy with 2504-HA
Hello,
I have question regarding N+1 redundancy with 2504-HA WLC.
Can I use 2504-HA unit for H+1 redundancy? SSO is not needed
I have two wireless network:
1. With WLC 5508 with about 40 AP(1262), all them are A regulatory domain
2. With WLC 2504, with about 30 Mesh AP(1552), all of them are E regulatory domain
I plan to use two 2504-HA units for backups, one for network with WLC5508 and second for network with WLC2504.
In case N+1 redundancy is management with Prime mandatory ?Hi,
Better to use same model and same software.
Case1: You have 5508WLC
Solution from my side: You must buy a another WLC with HA SKU license(Zero AP license). This wlc can work as N+1 and AP SSO as well as Client SSO but with higher version of code(7.5 or higher).
Case2: You have 2504 WLC
Solution: You must buy a another 2504 HA WLC: AIR-CT2504-HA-K9, that only supports N+1(No AP SSO and NO Client SSO)
http://www.cisco.com/c/en/us/td/docs/wireless/technology/hi_avail/N1_High_Availability_Deployment_Guide/N1_HA_Overview.html
More info:
http://www.cisco.com/c/en/us/products/collateral/wireless/aironet-1130-ag-series/qa_c67-714540.pdf
Regards
Dont forget to rate helpful posts -
Anyone got the AIR-CT2504-HA-K9 to work on N+1 Redundancy ?
Hi Guys,
Seems like the new Part #AIR-CT2504-HA-K9 needs some kinda licensing...to work... otherwise the redundancy is same as it was ealier with mobility groups.
The documentation seems to be wrong in the case of 2504, i cannot find the redundancy button in the Wireless tab too, When i apply the Evaluation license redundancy is working.... did anyone else face the same Issue ?
Regards,
Vinui cannot find the redundancy button in the Wireless tab too
You mean AP SSO?
WLC 2500 will not support this feature. -
What is the Smartnet service for the 2504 license upgrade LIC-CT2504-UPG ?
Hi guys,
Can some one explain me what is this service for ? I have the LIC-CT2504-UPG, with the LIC-CT2504-5A (5 AP licenses adder) and I don't understeand what are the SMARTNet services for this licenses ?
Are they needed if I already have the SMARTNet service for the hardware controller ?
Do these services provide something additional on top of the hardware service ?
Thank you.HI,
Smartnet Service Contract:
Reduce downtime with fast, expert technical support, flexible hardware coverage, and smart, proactive device diagnostics with SMARTnet Service. Your IT staff has anytime access to Cisco engineers in the Technical Assistance Center (TAC) and an extensive range of resources, tools and training.
What You Get by having this contract :
Global 24-hour access to experts in the Cisco Technical Assistance Center (TAC)
Self-help support through online communities, resources, and tools
Hardware replacement options, including 2-hour, 4-hour and next business day
software updates and download from cisco website fro your controller.
Hope you got the point :)
Regards
Dont forget to rate helpful posts -
WLC CT2504: Interface IP can not be used as internal DHCP server IP
Hello all,
I've got a new CT2504 controller with software version 7.0.220.0
Regarding to
http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a0080af5d13.shtml
I've tried to configure the internal DHCP on a dynamic-interface, but this is not possible:
(Cisco Controller) >config interface dhcp dynamic-interface vlan401 primary 172.16.x.3
vlan401 Interface IP can not be used as internal DHCP server IP
It works, if I use another IP (aka DHCP server) in the same subnet or in another subnet. It works also for the management interface.
(Cisco Controller) >show interface detailed management
Interface Name................................... management
MAC Address...................................... d0:c2:82:xx:xx:xx
IP Address....................................... 10.2.x.135
IP Netmask....................................... 255.255.255.240
IP Gateway....................................... 10.2.x.129
External NAT IP State............................ Disabled
External NAT IP Address.......................... 0.0.0.0
VLAN............................................. 400
Quarantine-vlan.................................. 0
Active Physical Port............................. 1
Primary Physical Port............................ 1
Backup Physical Port............................. Unconfigured
Primary DHCP Server.............................. 10.2.x.135
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
ACL.............................................. Unconfigured
AP Manager....................................... Yes
Guest Interface.................................. No
L2 Multicast..................................... Disabled
Scopes are defined and Proxy is enabled.
(Cisco Controller) >show dhcp summary
Scope Name Enabled Address Range
ap Yes 10.2.x.137 -> 10.2.x.140
intern Yes 172.16.x.20 -> 172.16.x.30
(Cisco Controller) >show dhcp proxy
DHCP Proxy Behaviour: enabled
Has somebody an explanation for this issue?
Thanks in advance,
Regard,
RobertYou can use the internal dhcp, but you need to set the primary dhcp as the management ip. So in your dynamic interface, your primary dhcp is configure with the wlc management ip address. Dhcp proxy also needs to be enabled and is enabled by default.
Thanks,
Scott Fella
Sent from my iPhone -
Wireless Config for AIR-CT2504-5AP
Dear Team,
i have 2 * AIR-CT2504 with 10AP license each , both running on 7.4 verison
Can i convert 1 AIR-CT2504 manually with or without addition of license , since i am able to see any part for HA licenseYes. You can configure them individually.
-
One WLC AIR-CT2504-K9 for Main office and 3 Branches
Hi ,
I need to configure a WLC AIR-CT2504-K9 with the followings requiremets:
1.- There is a main officce where the WLC and 7 LAPs will be installed.
2.- There are 3 branches; one LAPs in every branch will be installed.
3.- SSIDs for internal users and guest will be the same in each office.
Is it possible to set this scenario ?? (see complete info in table)
In the past I configure some WLC 2100 but I noticed some difference with this new WLC-CT2504
one of the differences that kept my attention were regarding ap-manager interface (not shown)
and virtual interface ( shown as NOT SUPPORTED)
Should I set ap-manager interface or is enough with managment interface ?
why the message "Not support" in virtual interface ??
How can I use one port for two interfaces (as is proposed in table), if I try to do this a message error is displayed
"Error setting AP Manager interface".
iF I set one interface and associate to one port (Enable) I can not set second interface in the same port so remains disable
This model of WLC just has 4 Ports.
I have read last config guide but is not clear for me because there is no examples of this kind of scenario.Hi Scott,
I configured virtual interface from startup configuration wizard.
(Cisco Controller) >show interface detailed virtual
Interface Name................................... virtual
MAC Address...................................... d0:c2:82:e3:8e:c1
IP Address....................................... 1.1.1.1
DHCP Option 82................................... Disabled
Virtual DNS Host Name............................ Disabled
AP Manager....................................... No
Guest Interface.................................. No
regards, -
New LWAPP 1702i not joining new CT2504 WLC
Have three new products on Test Bench:
CT2504 WLC w/ver 8.0.100.0
1702i LWAPP w/ver 15.3(3) JA
SG300-28MP Switch w/ver 1.3.7.18 (DHCP configured on switch with Option 43.)
(no DNS server available)
All three devices can ping each other but thats as far as it gets. The AP continuously loops w/DTLS error. I can issue CAPWAP
commands from the CLI telling AP IP of WLC and assigning the AP it's own IP but AP just continually loops without joining.
Console output of AP boot sequence attached.Thanks Rasiki, I opened a case today. Going over the compatibility documents I also noticed that the 1702i LWAPP software I am running, 15.3(3)JA, may need to be upgraded to the current 15.3(3)JAB.
All the configuration / reference material for the 1702i on the Cisco Support Site is in reference to "Autonomous" mode. I cannot find any written information for "Lightweight" mode. Is the procedure for upgrading the firmware on the LWAPP the same, i.e. TFTP, TAR files, etc.??? How does the AP know I want to upgrade in lightweight mode? -
AIR-CT2504-5-K9 capacity adder license error
Hi, i have AIR-CT2504-5-K9, with 5 access point license support. I buy capacity adder license LIC-CT2504-5A for add 5 access points more. When i try download licence file from tftp server on WLC system i see message "License 1 Failed 1" on WLC. TFTP server message downloading OK.
In what could be the problem?As far as I'm aware, the 2500 can support 5, 15, 25, 50 or 75 APs. And here's where logic does not apply: So if you have WLC with 5 AP, the next adder license you can get is 15. If you need more, you need to get 25. And that's it.
So all in all, if you have a WLC with 5 APs, the highest you can get is 45 AP support. You cannot get another 25 adder license.
This is how it works. I know it doesn't make sense. I don't make the rules.
NOTE: One guy, George, was able to do something about this. He RMA-ed his WLC and they gave him the same model but modified some stuff that he was able to get the maximum. -
Unable to integrate WLC with cisco ACS
Hi,
I am not able to integrate Cisco Tacas with WLC
Below are the error logs in Juniper firewall
WLC IP: 10.210.126.133
Cisco ACS: 10.116.45.131
Date/Time
Source Address/Port
Destination Address/Port
Translated Source Address/Port
Translated Destination Address/Port
Service
Duration
Bytes Sent
Bytes Received
Close Reason
2013-11-04 16:31:03
10.210.126.133:49098
10.116.45.131:49
10.210.126.133:49098
10.116.45.131:49
TCP PORT 49
2 sec.
591
428
Close - TCP FIN
2013-11-04 16:31:03
10.210.126.133:51759
10.116.45.131:49
10.210.126.133:51759
10.116.45.131:49
TCP PORT 49
2 sec.
525
326
Close - TCP FIN
2013-11-04 16:31:09
10.210.126.133:51759
10.116.45.131:49
10.210.126.133:51759
10.116.45.131:49
TCP PORT 49
9 sec.
475
238
Close - TCP FIN
2013-11-04 16:31:09
10.210.126.133:49098
10.116.45.131:49
10.210.126.133:49098
10.116.45.131:49
TCP PORT 49
9 sec.
519
318
Close - TCP FIN
Pls suggest further whether any changes needs to be done in any end
Cisco ACS Srver
11/04/2013
16:31:01
Author failed
ads.shalder
DCN-BANG2&BANG5-RW
127.0.0.1
Service denied
service=ciscowlc protocol=common
10.210.126.133
ads.shalder
No
1
10.210.126.133
Pls suggest further
Br/SubhojitHi,
we are getting this error on WLC side debug
(Cisco Controller) >*tplusTransportThread: Nov 05 09:51:32.683: Forwarding request to 10.116.45.131 port=49
*tplusTransportThread: Nov 05 09:51:32.689: tplus auth response: type=1 seq_no=2 session_id=5b675ca1 length=16 encrypted=0
*tplusTransportThread: Nov 05 09:51:32.689: TPLUS_AUTHEN_STATUS_GETPASS
*tplusTransportThread: Nov 05 09:51:32.689: auth_cont get_pass reply: pkt_length=25
*tplusTransportThread: Nov 05 09:51:32.689: processTplusAuthResponse: Continue auth transaction
*tplusTransportThread: Nov 05 09:51:32.700: tplus auth response: type=1 seq_no=4 session_id=5b675ca1 length=6 encrypted=0
*tplusTransportThread: Nov 05 09:51:32.700: tplus_make_author_request() from tplus_authen_passed returns rc=0
*tplusTransportThread: Nov 05 09:51:32.700: Forwarding request to 10.116.45.131 port=49
*tplusTransportThread: Nov 05 09:51:32.705: author response body: status=16 arg_cnt=0 msg_len=0 data_len=0
*tplusTransportThread: Nov 05 09:51:32.705: Tplus authorization for ads.shalder failed status=16
WLC hardware is: AIR-CT2504-K9V01
Br/Subhojit -
AIR-CT2504-5-K9 has 4 Gig ports with a note "Access point directly connected to the controller is not currently supported."
So what is the idea for these ports? Just an etherchannel to provide 4 Gig of bandwidth or some other uses?Hello,
The ports on the 2500 can be used for multiple deployment scenarios. You can have port 2 be a backup port in case the connection on port 1 fails (redundancy). You can also send different vlan traffic out a different physical port (guest segment, etc). The 2500 does not support Link Aggregation, so you cannot configure the ports in an etherchannel bundle.
At this time, connecting APs directly to the WLC is not a supported scenario.
For additional details, please see the following section of the 2500 deployment guide:
http://www.cisco.com/en/US/products/ps11630/products_tech_note09186a0080b8450c.shtml#scenarios
-Pat -
AIR-CT2504-5-K9 data encryption
All,
I am looking important info , I am going to order AIR-CT2504-5-K9 WLC . with software AIR-CT2504-SW-7.6.
1) would like to check the image AIR-CT2504-SW-7.6 has a inbuilt DTLS ( datagram transport layer security ) ?? . like in WLC 5500 series the image SWC5500K9-74 DTLS (Datagram Transport Layer Security) for encrypting CAPWAP data packets is enabled in this image.
2) on the AIR-CT2504-5-K9 , shall I need to order additionally 2504 Data DTLS License LIC-CT25-DTLS-K9 ?
please let me know
Regards
LernerAs long as they ship you a 2504 that doesn't have the LDPE software version, or else you will have to obtain the free DTLS license and convert the image to a non-LDPE code.
https://supportforums.cisco.com/discussion/11421191/2504-wlc-dtls-license
Scott
Maybe you are looking for
-
How to create a link to multiple links in pdf file
how to create a link to multiple links or a button to multiple links in pdf file. this links is goto diferent pages, no web. sorry for my english.
-
Help with JTree's opaque methods
I have been looking through the methods provided for JTree in Netbeans GUIBuilder and I do not see accessor methods for actions like insertion, retrieval, deletion and replacement. I am looking for something like this. JTree.insert('object', JTree.ge
-
Issue with new 'Display Summary Type in Table' Attribute
JHeadstart Version: 10.1.3.1.26 JDeveloper Version: 10.1.3.1 We have configured our top level groups in our JHS Application Definition Editor to have each table's first column (Primary Key) set to 'count' for the 'Display Summary Type In Table' field
-
Urgent help -can not access Documents (windows 7)
After some one renamed one profile and my documents (roaming profile and my documents redirected to network path too through group policy). Now , I can not open Documents. I got this message: "can't open this item It might have been moved, renamed
-
Dom0 Disk Device Name Changed... how to rename in vdsdev?
Good Morning, We had a server "incident" yesterday that left our Solaris ldom host rebooted. When it came back up, one of our guests (ldg1) refuses to bind with the error: Path /dev/rdsk/emcpower3c is not valid on service domain primary Sure enough,