eemoon
asked on
WLC cannot see LAP
Hi, Please see the diagram in attachment. Now the WLC can ping the switch and AP(10.5.5.16), and I already configured interface vlan 5 in the WLC, which is mapped to wlan, but the WLC still cannot see the AP. Anyone can give some suggestion ? Thank you.
(Cisco Controller) >show interface su
Interface Name Port Vlan Id IP Address Type Ap Mgr Guest
-------------------------- ------ ---- -------- --------------- ------- ------ -----
10.5.5.0 1 5 10.5.5.2 Dynamic No No
add30 1 30 172.16.30.3 Dynamic No No
ap-manager 1 60 192.168.60.3 Static Yes No
management 1 60 192.168.60.2 Static No No
service-port N/A N/A 172.16.10.5 Static No No
virtual N/A N/A 1.1.1.1 Static No No
(Cisco Controller) >
Capture.PNG
(Cisco Controller) >show interface su
Interface Name Port Vlan Id IP Address Type Ap Mgr Guest
--------------------------
10.5.5.0 1 5 10.5.5.2 Dynamic No No
add30 1 30 172.16.30.3 Dynamic No No
ap-manager 1 60 192.168.60.3 Static Yes No
management 1 60 192.168.60.2 Static No No
service-port N/A N/A 172.16.10.5 Static No No
virtual N/A N/A 1.1.1.1 Static No No
(Cisco Controller) >
Capture.PNG
ASKER
Great! Thank you for your fast reply. After changing vlan to 60, the WLC can see the AP. Then I am trying to find how to use anther way to tell the AP what IP of the WLC's management interface is. I could not find it. What is it?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
it is very good link. However, i do know why the WLC suddenly can not see the AP again. I follow the guides below, and answer the questions. but I still cannot find the reason
----------------------
Can the AP and the WLC communicate? Yes
Make sure the AP is getting an address from DHCP (check the DHCP server leases for the AP’s MAC address). in same subnet
Try pinging the AP from the controller. it is ok
----------------------
Can the AP and the WLC communicate? Yes
Make sure the AP is getting an address from DHCP (check the DHCP server leases for the AP’s MAC address). in same subnet
Try pinging the AP from the controller. it is ok
What version of code is on the WLC?
What model AP do you have?
What model AP do you have?
ASKER
I got it again after trying several times! it looks like the management interface and AP-manager interface should be at the same vlan. When the wlc could not see the ap, I got message from the AP as below:
In below, what is Interface Dot11Radio0?
Nov 20 18:14:12.104: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Nov 20 18:14:12.104: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Nov 20 18:14:12.167: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Nov 20 18:14:12.167: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Nov 20 18:14:12.177: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Nov 20 18:14:12.196: status of voice_diag_test from WLC is false
*Nov 20 18:14:12.196: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Nov 20 18:14:12.210: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
In below, what is Interface Dot11Radio0?
Nov 20 18:14:12.104: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Nov 20 18:14:12.104: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Nov 20 18:14:12.167: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Nov 20 18:14:12.167: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Nov 20 18:14:12.177: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Nov 20 18:14:12.196: status of voice_diag_test from WLC is false
*Nov 20 18:14:12.196: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Nov 20 18:14:12.210: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
Thanks.
What do you get in the trap log on the WLC?
What do you get in the trap log on the WLC?
ASKER
Manufacturer's Name...................... ........ Cisco Systems Inc.
Product Name...................... .......... ..... Cisco Controller
Product Version................... .......... ..... 7.0.220.0
RTOS Version................... .......... ........ 7.0.220.0
Bootloader Version................... .......... .. 4.0.217.0
Emergency Image Version................... ....... N/A
Build Type...................... .......... ....... DATA + WPS
System Name...................... .......... ...... C4402
System Location.................. .......... ......
AP: 1142N
Do you think if management interface and AP-manager interface should be at the same subnet ?
Product Name......................
Product Version...................
RTOS Version...................
Bootloader Version...................
Emergency Image Version...................
Build Type......................
System Name......................
System Location..................
AP: 1142N
Do you think if management interface and AP-manager interface should be at the same subnet ?
Yes, the ap-manager interface MUST be on the management subnet. You have it configured correctly.
Dot11radio0 is the 2.4GHz radio.
Dot11radio1 is the 5GHz radio.
Can you post the output from the WLC trap log please?
Dot11radio0 is the 2.4GHz radio.
Dot11radio1 is the 5GHz radio.
Can you post the output from the WLC trap log please?
ASKER
Can you post the output from the WLC trap log please?
How to do that?
On the first page you see (the Monitor page) on the WLC there's a "View All" link by the bottom-right of the screen. Click that link then screenshot the output.
ASKER
Log System Time Trap
0 Fri Nov 20 23:12:14 2015 AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:35:bd:c8:7e:b2:e0 Cause=Radio channel set. Status:NA
1 Fri Nov 20 23:12:14 2015 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:35:bd:c8:7e:b2:e0 Cause=Radio channel set. Status:NA
2 Fri Nov 20 23:12:14 2015 Channel changed for Base Radio MAC: 35:bd:c8:7e:b2:e0 on 802.11b/g radio. Old Channel: 1. New Channel: 11. Why: Interference. Energy before/after change: -67/-82. Noise before/after change: -82/-82. Interference before/after change: -67/-118.
3 Fri Nov 20 23:12:06 2015 Interference Profile Updated to Pass for Base Radio MAC: 35:bd:c8:7e:b2:e0 and slotNo: 0
4 Fri Nov 20 23:09:06 2015 Interference Profile Failed for Base Radio MAC: 35:bd:c8:7e:b2:e0 and slotNo: 0
5 Fri Nov 20 23:06:06 2015 Rogue AP : c8:a7:0a:a7:57:f6 detected on Base Radio MAC : 35:bd:c8:7e:b2:e0 Interface no:1(802.11n(5 GHz)) on Channel 132 with RSSI: -86 and SNR: 11 and Classification: unclassified
6 Fri Nov 20 23:03:05 2015 Rogue AP : c8:a7:0a:a7:57:f8 detected on Base Radio MAC : 35:bd:c8:7e:b2:e0 Interface no:0(802.11n(2.4 GHz)) on Channel 1 with RSSI: -70 and SNR: 23 and Classification: unclassified
7 Fri Nov 20 22:57:05 2015 AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:35:bd:c8:7e:b2:e0 Cause=Radio interface reset. Status:NA
8 Fri Nov 20 22:57:05 2015 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:35:bd:c8:7e:b2:e0 Cause=Radio interface reset. Status:NA
9 Fri Nov 20 22:57:05 2015 AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:35:bd:c8:7e:b2:e0 Cause=Radio interface reset. Status:NA
10 Fri Nov 20 22:57:05 2015 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:35:bd:c8:7e:b2:e0 Cause=Radio interface reset. Status:NA
11 Fri Nov 20 22:57:02 2015 AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:35:bd:c8:7e:b2:e0 Cause=Radio reset due to Init. Status:NA
12 Fri Nov 20 22:57:02 2015 AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:35:bd:c8:7e:b2:e0 Cause=Radio channel set. Status:NA
13 Fri Nov 20 22:57:01 2015 AP 'AP30f7.0d8c.bf12=1', MAC: 35:bd:c8:7e:b2:e0 disassociated previously due to AP Reset. Uptime: 0 days, 00 h 24 m 13 s . Last reset reason: operator changed 11g mode.
14 Fri Nov 20 22:52:58 2015 Controller time base status - Controller is out of sync with the central timebase.
15 Fri Nov 20 22:52:49 2015 Cold Start:
16 Fri Nov 20 22:52:13 2015 Link Up: Slot: 0 Port: 1 Admin Status: Enable Oper Status: Link Up
17 Fri Nov 20 22:52:07 2015 A RF group member has been added on 802.11a network on controller with IP 192.168.60.2(MAC 00:2b:d5:68:ca:00)
18 Fri Nov 20 22:52:07 2015 A RF group member has been added on 802.11b/g network on controller with IP 192.168.60.2(MAC 00:2b:d5:68:ca:00)
0 Fri Nov 20 23:12:14 2015 AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:35:bd:c8:7e:b2:e0 Cause=Radio channel set. Status:NA
1 Fri Nov 20 23:12:14 2015 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:35:bd:c8:7e:b2:e0 Cause=Radio channel set. Status:NA
2 Fri Nov 20 23:12:14 2015 Channel changed for Base Radio MAC: 35:bd:c8:7e:b2:e0 on 802.11b/g radio. Old Channel: 1. New Channel: 11. Why: Interference. Energy before/after change: -67/-82. Noise before/after change: -82/-82. Interference before/after change: -67/-118.
3 Fri Nov 20 23:12:06 2015 Interference Profile Updated to Pass for Base Radio MAC: 35:bd:c8:7e:b2:e0 and slotNo: 0
4 Fri Nov 20 23:09:06 2015 Interference Profile Failed for Base Radio MAC: 35:bd:c8:7e:b2:e0 and slotNo: 0
5 Fri Nov 20 23:06:06 2015 Rogue AP : c8:a7:0a:a7:57:f6 detected on Base Radio MAC : 35:bd:c8:7e:b2:e0 Interface no:1(802.11n(5 GHz)) on Channel 132 with RSSI: -86 and SNR: 11 and Classification: unclassified
6 Fri Nov 20 23:03:05 2015 Rogue AP : c8:a7:0a:a7:57:f8 detected on Base Radio MAC : 35:bd:c8:7e:b2:e0 Interface no:0(802.11n(2.4 GHz)) on Channel 1 with RSSI: -70 and SNR: 23 and Classification: unclassified
7 Fri Nov 20 22:57:05 2015 AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:35:bd:c8:7e:b2:e0 Cause=Radio interface reset. Status:NA
8 Fri Nov 20 22:57:05 2015 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:35:bd:c8:7e:b2:e0 Cause=Radio interface reset. Status:NA
9 Fri Nov 20 22:57:05 2015 AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:35:bd:c8:7e:b2:e0 Cause=Radio interface reset. Status:NA
10 Fri Nov 20 22:57:05 2015 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:35:bd:c8:7e:b2:e0 Cause=Radio interface reset. Status:NA
11 Fri Nov 20 22:57:02 2015 AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:35:bd:c8:7e:b2:e0 Cause=Radio reset due to Init. Status:NA
12 Fri Nov 20 22:57:02 2015 AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:35:bd:c8:7e:b2:e0 Cause=Radio channel set. Status:NA
13 Fri Nov 20 22:57:01 2015 AP 'AP30f7.0d8c.bf12=1', MAC: 35:bd:c8:7e:b2:e0 disassociated previously due to AP Reset. Uptime: 0 days, 00 h 24 m 13 s . Last reset reason: operator changed 11g mode.
14 Fri Nov 20 22:52:58 2015 Controller time base status - Controller is out of sync with the central timebase.
15 Fri Nov 20 22:52:49 2015 Cold Start:
16 Fri Nov 20 22:52:13 2015 Link Up: Slot: 0 Port: 1 Admin Status: Enable Oper Status: Link Up
17 Fri Nov 20 22:52:07 2015 A RF group member has been added on 802.11a network on controller with IP 192.168.60.2(MAC 00:2b:d5:68:ca:00)
18 Fri Nov 20 22:52:07 2015 A RF group member has been added on 802.11b/g network on controller with IP 192.168.60.2(MAC 00:2b:d5:68:ca:00)
13 Fri Nov 20 22:57:01 2015 AP 'AP30f7.0d8c.bf12=1', MAC: 35:bd:c8:7e:b2:e0 disassociated previously due to AP Reset. Uptime: 0 days, 00 h 24 m 13 s . Last reset reason: operator changed 11g mode.
A change made on the WLC caused the AP to disassociate.
ASKER
Thank you !
Either put the AP on VLAN 60 or use one of the WLC discovery methods to tell the AP what the IP of the WLC's management interface is.