CANNOT ADD WLC 5508 HA MODE IN PRIME INFRASTRUCTURE 2
I have two 5508 7.5.102 in HA mode and i am trying to add theme in cisco prime infrastructure 2 but i am taking back unreachable. Controller can ping the prime. I adding the controller using the management ip address of controller. Have anyone meat thise issue ? I also have problem when adding switches in stack mode (WS-C2960S-48TD-L)
Hello!
Check, that the service-port of the wlc is not in the same subnet, as Prime ip address
Similar Messages
-
Cannot add WLC 5508 to Prime Infrastructure 2.1
Regards,
I've been migrating / implementing a WCS to PI 2.1. I had several problems at first to add the 11 WLC we have to PI which I could be solving by trying and testing as I have not found many references by Cisco when it comes to troubleshooting when deploying PI.
I have several queries:
1. The WCS was added 11 WLC using different SNMP communities are configured on each of them. At first when trying to add the WLC had PI SNMP communication problems. I performed the test to eliminate any of the WLC added to WCS and add it again with some communities already existing R / W without any problem. At the end, I could not add the WLC so I had to create an SNMP community with the IP of Prime in the WLC so that they can be added. Does anyone know what is the cause of this?
2. I could not add a WLC 5508 IOS 7.3 using this method, even creating an SNMP community and IP mask 0.0.0.0 / 0. No access list or FW in between the WLC These WLC are spread over several countries but i was able to add the other WLC adding a community in each WLC pointing to the IP of Prime. It is similar to this case:
https://supportforums.cisco.com/discussion/12232506/cannot-add-wlc-5508-v761200-prime-infrastructure-21
Thanks for the help.It turns out that this situation was caused by a bug in 7.6.120.0 (CSCuo73572).
TAC handed me an escalation image (7.6.120.16) that fixed this.
Added the controllers sucessfully on the first try.
Phill -
Cannot add WLC 5508 7.2.111.3 to Cisco Prime Infrastructure 2.0
Though the Cisco Prime Infrastructure Compatibility Matrix list out that 7.2.111.3 is supported for PI 2.0
I am not able to add the controller to the PI 2.0.
The Reachability Status always shown "Unknow" and SNMP Status always shown "No response for SNMP Get".
There is no firewall between the WLC and PI.
And ping test shows it is reachable.
If I try to add controller by non-management port (I know it is not work but I want to try the reachability), the Reachability Status shown "Reachable" but the SNMP Status always shown error.
And if I use some SNMP testing software to test the SNMP port. SNMP can be quoted.
I have try to lower down the "Maximum VarBinds per Get PDU" but no luck.
Any thing I can do to troubleshoot the problem?Yes, I follow the procedure but it does not work.
Another update:
I add another WLC with version 7.0.98.0. It is fine.
And I setup another new PI 2.0 and new temporary WLC5508 with 7.2.111.3 to test. It work fine also......
So, I am wondering the existing 7.2 WLC have problem in responsing the SNMP Get. But I dont have any idea to test....
Do anyone have idea to test the snmp connection between PI and WLC? -
Cannot add WLC 5508 v7.6.120.0 into Prime Infrastructure 2.1
Hi everyone
Hope you can help us with this issue.
We already configure the WLC using this guide: http://mrncciew.com/2013/02/14/configuring-snmp-on-wlc/
snmp v2: enable
snmp v1: enable
default port values
community: incaenic with ip and mask 0.0.0.0 to allow access from any network or ip
traps receiver: community: incaenic ip: 10.100.100.15
when we try to discover the WLC with the PI it gave the error "SNMP Connectivity Fail"
WLC is on subnet 10.100.102.0/24 and PI in 10.100.100.0/24; there is a Catalyst 3850 between then with no access list on then.
Did someone can guide us with this?
Best Regards.
Alvaro RugamaHi,
Which version of SNMP are you using?
If you are using v1/v2 you should be using community string rather than local database credentials?
Regarding the service port what is the ip address assigned on the service port. From the configuration guide "Prime Infrastructure uses the preferred management IP address from the loop back interface. If the device does not have a loopback interface, Prime Infrastructure uses similar logic to the OSPF algorithm to select the router’s preferred management IP address."
Hope that helps.
Regards
Najaf -
WCS cannot add WLC over slow link
I have a WCS running at our main data center. We recently added a WLAN Controller (4402)in a remote office that is located over a VPN tunnel.
The WCS can PING the WLC (but it is slow at about 250ms), and I can access the controller's web interface from the WCS server. I just cannot add the controller, it gives me the error "No response from device, check SNMP communities, version or network for issues."
Any thoughts on what I can try?
I have also verified the SNMP communities and removed and re-added them on both the WCS and WLC, and I've tried both the RO and RW strings. No difference.
Thanks.Here is what appears in the log when I try to connect via SNMP v2c.
*Oct 13 13:26:19.552: %SIM-3-MACADDR_GET_FAIL: sim.c:1147 Interface 1 source MAC address is not found.
*Oct 13 13:26:03.546: %SIM-3-MACADDR_GET_FAIL: sim.c:1147 Interface 1 source MAC address is not found.
*Oct 13 13:25:55.548: %SIM-3-MACADDR_GET_FAIL: sim.c:1147 Interface 1 source MAC address is not found.
*Oct 13 13:25:51.560: %SIM-3-MACADDR_GET_FAIL: sim.c:1147 Interface 1 source MAC address is not found.
*Oct 13 13:25:44.483: %USMDB-4-MSGTAG027: usmdb_wcp.c:221 usmDbWcpGetParentRouterName(): Non-Doberman platform.
*Oct 13 13:25:44.483: %USMDB-4-MSGTAG022: usmdb_wcp.c:95 usmDbWcpGetControllerSlotPort(): Non-Doberman platform.
*Oct 13 13:25:44.482: %USMDB-4-MSGTAG023: usmdb_wcp.c:119 usmDbWcpGetPeersPortAndIp(): Non-Doberman platform.
*Oct 13 13:25:44.481: %USMDB-4-MSGTAG022: usmdb_wcp.c:95 usmDbWcpGetControllerSlotPort(): Non-Doberman platform.
*Oct 13 13:25:44.480: %USMDB-4-MSGTAG023: usmdb_wcp.c:119 usmDbWcpGetPeersPortAndIp(): Non-Doberman platform.
I tried an extended ping from the WCS's default gateway and if I increase the datagram size to 1500, I get the âMâ = could not fragment reply. However a size of 1300 works fine. -
AP 360021 cannot join WLC 5508
Dears,
I have a cisco 5508 WLC and 40 cisco 360021 APs.
I configured the WLC and assign the management interface IP and also configured a DHCP pool on my Cisco 4507 core switch wit option 43.
But the problem that the APs connot join the WLC.
The below message appears:-
Nov 7 09:08:28.953: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Nov 7 09:08:28.954: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Nov 7 09:08:38.968: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Nov 7 09:08:39.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: x.x.x.x pe6
*Nov 7 09:08:39.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
Please support me to solve this issue.
Regards,Dears,
Also find the attched debug and the requirements that you asked for.
AP cisco debug:
*Oct 13 01:33:32.691: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Oct 13 01:33:34.691: %LINK-3-UPDOWN: Interface BVI1, changed state to up
*Oct 13 01:33:35.691: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
*Oct 13 01:33:35.691: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 255.255.255.255 started - CLI initiated
*Oct 13 01:33:37.815: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Oct 13 01:33:37.903: status of voice_diag_test from WLC is false
*Oct 13 01:33:37.907: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!
*Oct 13 01:33:37.907: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Oct 13 01:33:38.815: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Oct 13 01:33:38.867: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Oct 13 01:33:38.875: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Oct 13 01:33:39.191: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Oct 13 01:33:39.223: %DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigned DHCP address 10.10.107.58, mask 255.255.255.0, hostname APfc99.47a2.2ef7
*Oct 13 01:33:39.223: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Oct 13 01:33:39.899: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Oct 13 01:33:40.899: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Oct 13 01:33:43.191: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Oct 13 01:33:43.259: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.10.107.58, mask 255.255.255.0, hostname APfc99.47a2.2ef7
*Oct 13 01:33:43.259: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Oct 13 01:33:47.907: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
*Oct 13 01:33:47.907: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4
*Oct 13 01:33:47.907: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
*Oct 13 01:33:47.907: %CAPWAP-3-ERRORLOG: Failed to process timer message.
*Oct 13 01:33:48.315: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Oct 13 01:33:48.379: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to ad
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (10.10.18.1) (10.10.18.100)
ministratively down
*Oct 13 01:33:48.467: status of voice_diag_test from WLC is false
*Oct 13 01:33:48.471: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Oct 13 01:33:49.379: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Oct 13 01:33:49.431: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Oct 13 01:33:49.439: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Oct 13 01:33:49.471: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Oct 13 01:33:49.471: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Oct 13 01:33:50.463: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Oct 13 01:33:51.463: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Oct 13 01:33:52.475: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Oct 13 01:33:52.483: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Oct 13 01:33:53.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Oct 13 01:33:53.507: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Oct 13 01:33:54.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 23 23:47:46.583: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
*Mar 23 23:47:46.583: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
*Mar 23 23:47:46.583: %MESH-6-LINK_UPDOWN: Mesh station fc99.47a2.2ef7 link Down
*Mar 23 23:47:47.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.10.107.5:5246
*Mar 23 23:47:48.055: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Mar 23 23:47:48.119: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Mar 23 23:47:48.211: status of voice_diag_test from WLC is false
*Mar 23 23:47:48.211: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 23 23:47:49.119: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 23 23:47:49.171: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 23 23:47:49.179: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 23 23:47:50.207: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 23 23:47:51.207: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 23 23:47:51.215: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 23 23:47:51.223: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 23 23:47:52.215: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 23 23:47:52.247: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 23 23:47:53.247: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.10.107.5
*Mar 24 00:25:36.579: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
*Mar 24 00:25:36.579: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
*Mar 24 00:25:36.579: %MESH-6-LINK_UPDOWN: Mesh station fc99.47a2.2ef7 link Down
APfc99.47a2.2ef7#
%CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Mar 24 00:33:27.519: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Mar 24 00:33:28.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 00:33:28.035: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 00:33:28.043: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 00:33:28.051: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 00:33:29.079: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 00:33:30.079: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 24 00:33:32.519: %CAPWAP-5-SENDJOIN: sending Join Request to 10.10.107.5
*Mar 24 00:33:32.523: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 00:33:32.531: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 00:33:33.523: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 00:33:33.555: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 00:33:34.555: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radi
The Time on AP is not same time on the WLC
Oct 13 01:34:13.411: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Mar 24 02:02:36.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.10.107.5 peer_port: 5246
*Mar 24 02:02:36.003: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
User Access Verification
Username:
*Mar 24 02:02:36.011: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:02:37.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:02:37.035: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:02:38.035: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
Username:
*Mar 24 02:03:05.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2051 Max retransmission count reached!
Username: Cisco
Password:
APfc99.47a2.2ef7>
*Oct 13 01:34:13.411: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Mar 24 02:02:36.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.10.107.5 peer_port: 5246
*Mar 24 02:02:36.003: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
User Access Verification
Username:
*Mar 24 02:02:36.011: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:02:37.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:02:37.035: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:02:38.035: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
Username:
*Mar 24 02:03:05.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2051 Max retransmission count reached!
Username: Cisco
Password:
APfc99.47a2.2ef7>
*Mar 24 02:04:31.603: %IP-4-DUPADDR: Duplicate address 10.10.107.5 on BVI1, sourced by 0006.f661.d880?
memory set memory parameters
APfc99.47a2.2ef7#set
*Mar 24 02:04:33.103: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-start
*Mar 24 02:04:33.207: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
*Mar 24 02:04:33.207: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4
*Mar 24 02:04:33.207: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
*Mar 24 02:04:33.207: %CAPWAP-3-ERRORLOG: Failed to process timer messag
APfc99.47a2.2ef7#
*Mar 24 02:04:38.159: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Mar 24 02:04:38.223: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Mar 24 02:04:38.315: status of voice_diag_test from WLC is false
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar 24 02:04:38.315: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:04:39.223: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:04:39.275: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 02:04:39.283: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
%DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.10.107.5:5246
*Mar 24 02:06:58.999: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Mar 24 02:05:59.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.10.107.5 peer_port: 5246
*Mar 24 02:05:59.003: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 02:05:59.011: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:06:00.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:06:00.039: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:06:01.039: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
APfc99.47a2.2ef7#
APfc99.47a2.2ef7#
*Mar 24 02:09:50.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2051 Max retransmission count reached!
APfc99.47a2.2ef7#
APfc99.47a2.2ef7#
APfc99.47a2.2ef7#
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar 24 02:10:20.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.10.107.5:5246
*Mar 24 02:10:21.055: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Mar 24 02:10:21.123: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Mar 24 02:10:21.207: status of voice_diag_test from WLC is false
*Mar 24 02:10:21.211: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:10:22.123: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:10:22.175: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 02:10:22.183: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:10:23.211: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:10:24.211: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 24 02:10:25.787: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
*Mar 24 02:10:25.787: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
*Mar 24 02:10:25.787: %MESH-6-LINK_UPDOWN: Mesh station fc99.47a2.2ef7 link Down
*Mar 24 02:10:30.211: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Mar 24 02:10:30.215: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 02:10:30.223: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:10:31.215: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:10:31.251: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:10:32.251: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar 24 02:10:49.211: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Mar 24 02:10:49.215: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 02:10:49.223: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:10:50.215: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:10:50.251: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:10:51.251: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar 24 02:11:08.211: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Mar 24 02:11:08.215: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 02:11:08.223: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:11:09.215: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:11:09.247: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:11:10.247: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 24 02:11:16.607: %IP-4-DUPADDR: Duplicate address 10.10.107.5 on BVI1, sourced by 0006.f661.d880
*Mar 24 02:11:18.107: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Mar 24 02:11:18.211: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
*Mar 24 02:11:18.211: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4
*Mar 24 02:11:18.211: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
*Mar 24 02:11:18.211: %CAPWAP-3-ERRORLOG: Failed to process timer message.
*Mar 24 02:11:23.163: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Mar 24 02:11:23.227: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Mar 24 02:11:23.319: status of voice_diag_test from WLC is false
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar 24 02:11:23.319: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:11:24.227: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:11:24.275: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 02:11:24.283: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:11:25.311: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:11:26.311: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 24 02:11:33.319: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Mar 24 02:11:33.323: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 02:11:33.331: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:11:34.323: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:11:34.355: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:11:35.355: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 24 02:11:43.319: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Mar 24 02:12:43.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.10.107.5 peer_port: 5246
*Mar 24 02:12:43.003: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 02:12:43.011: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:12:44.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:12:44.035: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:12:45.035: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar 24 02:17:05.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.10.107.5:5246
*Mar 24 02:17:06.055: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Mar 24 02:17:06.119: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Mar 24 02:17:06.203: status of voice_diag_test from WLC is false
*Mar 24 02:17:06.207: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:17:07.119: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:17:07.171: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 02:17:07.179: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:17:08.203: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:17:09.203: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 24 02:17:10.787: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
*Mar 24 02:17:10.787: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
*Mar 24 02:17:10.787: %MESH-6-LINK_UPDOWN: Mesh station fc99.47a2.2ef7 link Down
*Mar 24 02:17:15.207: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Mar 24 02:17:15.211: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 02:17:15.219: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:17:16.211: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:17:16.247: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:17:17.247: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 24 02:17:53.207: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Mar 24 02:17:53.211: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 02:17:53.219: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:17:54.211: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:17:54.247: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:17:55.247: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 24 02:18:01.607: %IP-4-DUPADDR: Duplicate address 10.10.107.5 on BVI1, sourced by 0006.f661.d880
*Mar 24 02:18:03.107: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Mar 24 02:18:03.207: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
*Mar 24 02:18:03.207: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Even
Show requirement for AP:-
APfc99.47a2.2ef7#show version
Cisco IOS Software, C3600 Software (AP3G2-K9W8-M), Version 12.4(25e)JA, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2012 by Cisco Systems, Inc.
Compiled Fri 27-Jan-12 21:27 by prod_rel_team
ROM: Bootstrap program is C3600 boot loader
BOOTLDR: C3600 Boot Loader (AP3G2-BOOT-M) LoaderVersion 12.4(23c)JY, RELEASE SOFTWARE (fc1)
APfc99.47a2.2ef7 uptime is 7 minutes
System returned to ROM by power-on
System image file is "flash:/ap3g2-k9w8-mx.124-25e.JA/ap3g2-k9w8-mx.124-25e.JA"
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
cisco AIR-CAP3602I-A-K9 (PowerPC) processor (revision A0) with 167926K/81920K bytes of memory.
Processor board ID FGL1644Z15P
PowerPC CPU at 800Mhz, revision number 0x2151
Last reset from power-on
LWAPP image version 7.2.1.72
1 Gigabit Ethernet interface
2 802.11 Radio(s)
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: FC:99:47:A2:2E:F7
Part Number : 73-14521-02
PCA Assembly Number : 800-37501-02
PCA Revision Number : A0
PCB Serial Number : FOC16414A83
Top Assembly Part Number : 800-35852-02
Top Assembly Serial Number : FGL1644Z15P
Top Revision Number : C0
Product/Model Number : AIR-CAP3602I-A-K9
Configuration register is 0xF
show inventry
NAME: "AP3600", DESCR: "Cisco Aironet 3600 Series (IEEE 802.11n) Access Point"
PID: AIR-CAP3602I-A-K9 , VID: V01, SN: FGL1644Z15P
show requirement on WLC
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.4.100.0
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS
System Name...................................... Cisco_61:d8:84
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
Redundancy Mode.................................. Disabled
IP Address....................................... 10.10.107.5
Last Reset....................................... Software reset
System Up Time................................... 0 days 1 hrs 4 mins 25 secs
System Timezone Location......................... (GMT +3:00) Baghdad
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
Configured Country............................... IQ - Iraq
Operating Environment............................ Commercial (0 to 40 C)
--More-- or (q)uit
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +40 C
External Temperature............................. +24 C
Fan Status....................................... OK
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 1
Number of Active Clients......................... 0
Memory Current Usage............................. Unknown
Memory Average Usage............................. Unknown
CPU Current Usage................................ Unknown
CPU Average Usage................................ Unknown
Burned-in MAC Address............................ 00:06:F6:61:D8:80
Power Supply 1................................... Present, OK
Power Supply 2................................... Absent
Maximum number of APs supported.................. 100
WLC after debug enable
*spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery resp:AC Name message element length = 58
*spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery resp: WTP Radio Information msg length = 67
*spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery resp: CAPWAP Control IPV4 Address len = 77
*spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery resp: CAPWAP Control IPV6 Address len = 99
*spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery resp: Mwar type payload len = 110
*spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery resp: Time sync payload len = 125
*spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery Response sent to 10.10.107.60:8944
*spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery Response sent to 10.10.107.60:8944
*spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 WTP already released
*spamApTask2: Mar 24 04:56:19.133: fc:99:47:a2:2e:f7 CAPWAP Control Msg Received from 10.10.107.5:8944
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 packet received of length 123 from 10.10.107.5:8944
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Msg Type = 1 Capwap state = 0
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery Request from 10.10.107.5:8944
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 20
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Total msgEleLen = 94
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 msgEleLength = 40 msgEleType = 39
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Total msgEleLen = 50
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 41
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Total msgEleLen = 45
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 44
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Total msgEleLen = 40
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 msgEleLength = 10 msgEleType = 37
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Vendor specific payload from AP 54:78:1A:43:CA:D0 validated
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Total msgEleLen = 26
(Cisco Controller) >*sshpmLscTask: Mar 24 05:02:01.461: sshpmLscTask: LSC Task received a message 4
*Oct 13 01:33:48.191: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
User Access Verification
Username:
Username:
Username:
*Oct 13 01:33:50.191: %LINK-3-UPDOWN: Interface BVI1, changed state to up
*Oct 13 01:33:50.191: %IP-4-DUPADDR: Duplicate address 10.10.107.5 on BVI1, sourced by 0006.f661.d880
*Oct 13 01:33:51.191: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
*Oct 13 01:33:52.019: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
*Oct 13 01:33:52.019: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4
*Oct 13 01:33:52.019: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
*Oct 13 01:33:52.019: %CAPWAP-3-ERRORLOG: Failed to process timer message.
*Oct 13 01:33:53.251: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Oct 13 01:33:53.315: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to ad
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)ministratively down
*Oct 13 01:33:53.407: status of voice_diag_test from WLC is false
*Oct 13 01:33:53.411: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Oct 13 01:33:54.315: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Oct 13 01:33:54.367: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Oct 13 01:33:54.375: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Oct 13 01:33:55.399: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Oct 13 01:33:56.399: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 msgEleLength = 22 msgEleType = 37
nable
(Cisco Controller) >*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Vendor specific payload from AP 54:78:1A:43:CA:D0 validated
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Total msgEleLen = 0
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Join Priority Processing status = 0, Incoming Ap's Priority 4, MaxLrads = 100, joined Aps =0
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 1. 0 0
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 2. 232 3
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 3. 0 0
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 4. 100 0
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery resp: AC Descriptor message element len = 40
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 acName = Cisco_61:d8:84
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery resp:AC Name message element length = 58
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery resp: WTP Radio Information msg length = 67
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery resp: CAPWAP Control IPV4 Address len = 77
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery resp: CAPWAP Control IPV6 Address len = 99
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery resp: Mwar type payload len = 110
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery resp: Time sync payload len = 125
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery Response sent to 10.10.107.5:8944
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery Response sent to 10.10.107.5:8944
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 WTP already released
*spamApTask6: Mar 24 04:56:28.440: fc:99:47:a2:2e:f7 CAPWAP Control Msg Received from 10.10.107.60:8945
*spamApTask6: Mar 24 04:56:28.440: 54:78:1a:43:ca:d0 packet received of length 123 from 10.10.107.60:8945
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Msg Type = 1 Capwap state = 0
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Discovery Request from 10.10.107.60:8945
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 20
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 94
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 40 msgEleType = 39
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 50
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 41
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 45
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 44
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 40
*spamApTask7: Mar 24 04:56:28.441: fc:99:47:a2:2e:f7 CAPWAP Control Msg Received from 10.10.107.61:8945
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 10 msgEleType = 37
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 packet received of length 123 from 10.10.107.61:8945
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Vendor specific payload from AP 54:78:1A:43:CA:D0 validated
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Msg Type = 1 Capwap state = 0
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 26
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 22 msgEleType = 37
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Discovery Request from 10.10.107.61:8945
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 20
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Vendor specific payload from AP 54:78:1A:43:CA:D0 validated
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 94
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 40 msgEleType = 39
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 0
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 50
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 41
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Join Priority Processing status = 0, Incoming Ap's Priority 4, MaxLrads = 100, joined Aps =0
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 45
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 44
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 1. 0 0
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 40
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 2. 232 3
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 10 msgEleType = 37
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 3. 0 0
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Vendor specific payload from AP 54:78:1A:43:CA:D0 validated
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 4. 100 0
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 26
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 22 msgEleType = 37
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Discovery resp: AC Descriptor message element len = 40
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Vendor specific payload from AP 54:78:1A:43:CA:D0 validated
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 acName = Cisco_61:d8:84
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 0
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Discovery resp:AC Name message element length = 58
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Discovery resp: WTP Radio Information msg length = 67
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Join Priority Processing status = 0, Incoming Ap's Priority 4, MaxLrads = 100, joined Aps =0
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 1. 0 0
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 2. 232 3
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Discovery resp: CAPWAP Control IPV4 Address len = 77
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 3. 0 0 -
Cannot add MSE 7.4 VM to Prime 1.3.20
Hi,
How do I add the MSE 7.4 VM to Prime 1.3.20?
The Prime uses https or http when trying to add the MSE. But those ports are closed on the MSE. The MSE seems to expect traffic on tcp 8001.
We did not change the default NCS-username/password in the startup-wizard.
C:\Windows\System32>nmap 192.168.0.211
22/tcp open ssh
1099/tcp open rmiregistry
1521/tcp open oracle
8001/tcp open vcom-tunnel
9001/tcp open tor-orport
9002/tcp open dynamid
[root@mse ~]# /etc/init.d/msed status
STATUS:
Health Monitor is running
Starting MSE Platform, Waiting to check the status.
MSE services are up, getting the status
Server Config
Product name: Cisco Mobility Service Engine
Version: 7.4.100.0
Health Monitor Ip Address: 1.1.1.1
High Availability Role: 1
Hw Version: V01
Hw Product Identifier: AIR-MSE-VA-K9
Hw Serial Number: mse.demo.com_12b3f26e-c129-11e2-88bb-
Use HTTP: false
Legacy HTTPS: false
Legacy Port: 8001
Log Modules: -1
Log Level: INFO
Days to keep events: 2
Session timeout in mins: 30
DB backup in days: 2
Services
Service Name: Context Aware Service
Service Version: 7.4.0.38
Admin Status: Enabled
Operation Status: Up
Service Name: WIPS
Service Version: 1.0.4041.0
Admin Status: Disabled
Operation Status: Down
Service Name: Mobile Concierge Service
Service Version: 2.0.0.37
Admin Status: Disabled
Operation Status: Down
Service Name: Location Analytics Service
Service Version: 1.0.0.12
Admin Status: Disabled
Operation Status: Down
Server Monitor
Server start time: Mon May 20 10:54:21 CEST 2013
Server current time: Mon May 20 11:08:42 CEST 2013
Server timezone: Europe/Stockholm
Server timezone offset: 3600000
Restarts: 1
Used Memory (bytes): 124321616
Allocated Memory (bytes): 514523136
Max Memory (bytes): 514523136
DB virtual memory (kbytes): 0
DB virtual memory limit (bytes): 0
DB disk memory (bytes): 2037786176
DB free size (kbytes): 0
Active Sessions
Session ID: 29374
Session User ID: 1
Session IP Address: 192.168.0.212
Session start time: Mon May 20 11:01:14 CEST 2013
Session last access time: Mon May 20 11:02:06 CEST 2013
Context Aware Service
Total Active Elements(Wireless Clients, Tags, Rogue APs, Rogue Clients, Interfer
ers, Wired Clients): 0
Active Wireless Clients: 0
Active Tags: 0
Active Rogue APs: 0
Active Rogue Clients: 0
Active Interferers: 0
Active Wired Clients: 0
Active Elements(Wireless Clients, Rogue APs, Rogue Clients, Interferers, Wired C
lients, Tags) Limit: 100
Active Sessions: 1
Wireless Clients Not Tracked due to the limiting: 0
Tags Not Tracked due to the limiting: 0
Rogue APs Not Tracked due to the limiting: 0
Rogue Clients Not Tracked due to the limiting: 0
Interferers Not Tracked due to the limiting: 0
Wired Clients Not Tracked due to the limiting: 0
Total Elements(Wireless Clients, Rogue APs, Rogue Clients, Interferers, Wired Cl
ients) Not Tracked due to the limiting: 0
Context Aware Sub Services
Subservice Name: Aeroscout Tag Engine
Admin Status: Disabled
Operation Status: Down
Subservice Name: Cisco Tag Engine
Admin Status: Enabled
Operation Status: Up
[root@mse ~]#
Thanks in advanceThanks for your input. Here is the result:
[root@mse ~]# /etc/init.d/msed reload
Stopping MSE Platform
Shutting down framework and services ...
Shutting down framework and services ...........
iptables v1.3.5: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.3.5: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.3.5: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.3.5: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
Starting MSE Platform
iptables v1.3.5: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.3.5: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.3.5: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.3.5: can't initialize iptables table `nat': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.3.5: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
Starting Health Monitor, Waiting to check the status.
Health Monitor successfully started
Starting Admin process...
Started Admin process.
Database started successfully. Starting framework and services ...
Database started successfully. Starting framework and services ...........
Framework and services successfully started
[root@mse ~]#
[root@mse ~]#
[root@mse ~]# /etc/init.d/msed status
STATUS:
Health Monitor is running
Starting MSE Platform, Waiting to check the status.
MSE services are up, getting the status
Server Config
Product name: Cisco Mobility Service Engine
Version: 7.4.100.0
Health Monitor Ip Address: 1.1.1.1
High Availability Role: 1
Hw Version: V01
Hw Product Identifier: AIR-MSE-VA-K9
Hw Serial Number: mse.demo.com_12b3f26e-c129-11e2-88bb-
Use HTTP: false
Legacy HTTPS: false
Legacy Port: 8001
Log Modules: -1
Log Level: INFO
Days to keep events: 2
Session timeout in mins: 30
DB backup in days: 2
Services
Service Name: Context Aware Service
Service Version: 7.4.0.38
Admin Status: Enabled
Operation Status: Up
Service Name: WIPS
Service Version: 1.0.4041.0
Admin Status: Disabled
Operation Status: Down
Service Name: Mobile Concierge Service
Service Version: 2.0.0.37
Admin Status: Disabled
Operation Status: Down
Service Name: Location Analytics Service
Service Version: 1.0.0.12
Admin Status: Disabled
Operation Status: Down
Server Monitor
Server start time: Mon May 20 14:31:03 CEST 2013
Server current time: Mon May 20 14:46:10 CEST 2013
Server timezone: Europe/Stockholm
Server timezone offset: 3600000
Restarts: 2
Used Memory (bytes): 118345992
Allocated Memory (bytes): 514523136
Max Memory (bytes): 514523136
DB virtual memory (kbytes): 0
DB virtual memory limit (bytes): 0
DB disk memory (bytes): 2048272000
DB free size (kbytes): 0
Context Aware Service
Total Active Elements(Wireless Clients, Tags, Rogue APs, Rogue Clients, Interfer
ers, Wired Clients): 0
Active Wireless Clients: 0
Active Tags: 0
Active Rogue APs: 0
Active Rogue Clients: 0
Active Interferers: 0
Active Wired Clients: 0
Active Elements(Wireless Clients, Rogue APs, Rogue Clients, Interferers, Wired C
lients, Tags) Limit: 100
Active Sessions: 0
Wireless Clients Not Tracked due to the limiting: 0
Tags Not Tracked due to the limiting: 0
Rogue APs Not Tracked due to the limiting: 0
Rogue Clients Not Tracked due to the limiting: 0
Interferers Not Tracked due to the limiting: 0
Wired Clients Not Tracked due to the limiting: 0
Total Elements(Wireless Clients, Rogue APs, Rogue Clients, Interferers, Wired Cl
ients) Not Tracked due to the limiting: 0
Context Aware Sub Services
Subservice Name: Aeroscout Tag Engine
Admin Status: Disabled
Operation Status: Down
Subservice Name: Cisco Tag Engine
Admin Status: Enabled
Operation Status: Up
[root@mse ~]# -
Prime Infrastructure 2.1 updating 5508 controllers in HA mode
I'm having the same issue from PI 2.1 trying to import 7.6.130 for my 5508 controllers and it saying "Image not Applicable for this Device" even though I know that image is applicable.
Also, has anyone ever updated 5508 controllers in HA mode from Prime Infrastructure?Your combination of PI (are you sure it's 2.1? not 1.2?), WLC and MSE is not supported.
You may want to have a look at this matrix:
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html
Regards
Stefan
PS: Today PI 1.3 and MSE 7.4 have been released - these support WLC code 7.4 -
Hi,
I have upgraded my WLC 5508 from 7.0 to 7.4 and the AP 1310 no longer can associate to WLC.
Seems that the AP doesn't work with WLC ver 7.4
Except changing these APs to autonomous mode, any other alternatives?
Besides, if we change them to autonomous mode, can Prime Infrastructure manage/monitor these APs?
thanks.The 1310 last support is on v7.0.x of the WLC. See the matrix below.
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html
Prime Infrastructure can monitor the Autonomous access point but will not do anything else than monitor. Config changes is done via the bridge/AP itself.
Sent from Cisco Technical Support iPhone App -
Only 1 Virtual domain per user in Cisco Prime Infrastructure ?
Hello,
I wanted to add several Virtual Domains in Cisco Prime Infrastructure 1.3 (the UI allows it). But then I observe that the user can only see the first Virtual Domain (the first par alphabetical order).
Is it normal (by design), or is it a bug, or is there something that understand wrong ?
Many thanks in advance,
Best regards,
DavidA user can have multiple virtual domain assigned , but only one is active at login.
Anyway the user can change the current virtual domain using the virtual domain drop-down list at the right top of the page. -
Will Prime Infrastructure 2.0 monitor server 2008?
Prime Infrastructure 2.0 monitor server 2008? Will any of the future versions include system monitoring?
Thanks, ScottIt can do so in a limited way now. You need to enable the SNMP service on your server and set community strings etc.
Once you do that, you can add it as a device in Prime Infrastructure. I doubt it will ever be a complete system monitor like a server management tool. PI is fundamentally a network management tool.
FYI here are the steps for enabling SNMP agent on your Windows server:
http://technet.microsoft.com/en-us/library/bb726987.aspx
Make sure to add your Prime server as an authorized host and setup the community string. Once you've done that, you should be able to sync with it as an added device in Device Center. Here is my Windows 2008 R2 server added thus in PI 2.0: -
AIR-CAP1602i cannot join a WLC 5508 controller
Hello,
I'm managing a large number of access points on a Cisco wlc 5508 controller.
We've recently purchased a bunch of new AIR-CAP1602I-E-K9.
note that we already have AIR-CAP1602I-E-K9 and other models in production.
These A.P are not able to join the controller for some reason, I've tried a lot of different things but I am now at a loss.
I have checked the regulatory domain, upgraded the FUS, manually upgraded the software version of the LAP to match the version on the other A.P.
I even downgraded/upgraded the WLC code (version 7.4.x and 8.0)
I use the dhcp option 43 to to send the controller IP.
Here are the info that can help:
errors:
#on A.P
*Dec 12 09:24:49.659: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Dec 12 09:24:49.659: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Dec 12 09:24:49.659: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
#on WLC
Lwapp join request rejected (WLC version 7.6.130.0)
Failed to add database entry (WLC version 8.0)
WLC sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.6.130.0
Bootloader Version............................... 1.0.20
Field Recovery Image Version..................... 7.6.101.1
Firmware Version................................. FPGA 1.7, Env 1.8, USB console 2.2
Build Type....................................... DATA + WPS
System Name...................................... XXX
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
Redundancy Mode.................................. Disabled
IP Address....................................... XXX
Last Reset....................................... Software reset
System Up Time................................... 6 days 4 hrs 16 mins 27 secs
System Timezone Location.........................
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
Configured Country............................... Multiple Countries:CA,FR
Operating Environment............................ Commercial (0 to 40 C)
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +41 C
External Temperature............................. +22 C
Fan Status....................................... OK
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 7
Number of Active Clients......................... 1977
Burned-in MAC Address............................ A4:93:4C:B0:E4:C0
Power Supply 1................................... Present, OK
Power Supply 2................................... Present, OK
Maximum number of APs supported.................. 250
AP sh version
AP58f3.9cb8.3701#sh version
Cisco IOS Software, C1600 Software (AP1G2-K9W8-M), Version 15.2(4)JB6, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Fri 22-Aug-14 10:56 by prod_rel_team
ROM: Bootstrap program is C1600 boot loader
BOOTLDR: C1600 Boot Loader (AP1G2-BOOT-M) LoaderVersion 15.2(2)JAX, RELEASE SOFTWARE (fc1)
AP58f3.9cb8.3701 uptime is 31 minutes
System returned to ROM by power-on
System image file is "flash:/ap1g2-k9w8-mx.152-4.JB6/ap1g2-k9w8-mx.152-4.JB6"
Last reload reason:
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
cisco AIR-CAP1602I-E-K9 (PowerPC) processor (revision B0) with 229366K/32768K bytes of memory.
Processor board ID FGL1832X5QU
PowerPC CPU at 533MHz, revision number 0x2151
Last reset from power-on
LWAPP image version 7.6.100.0
1 Gigabit Ethernet interface
2 802.11 Radios
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 58:F3:9C:B8:37:01
Part Number : 73-14671-04
PCA Assembly Number : 000-00000-00
PCA Revision Number :
PCB Serial Number : FOC183171L4
Top Assembly Part Number : 800-38552-01
Top Assembly Serial Number : FGL1832X5QU
Top Revision Number : A0
Product/Model Number : AIR-CAP1602I-E-K9
AP sh inventory
NAME: "AP1600", DESCR: "Cisco Aironet 1600 Series (IEEE 802.11n) Access Point"
PID: AIR-CAP1602I-E-K9 , VID: V01, SN: FGL1832X5QU
Thanks for your help !Hi Olivier,
The error messages that you have on the debugs:
*Dec 12 09:24:49.659: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Dec 12 09:24:49.659: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Dec 12 09:24:49.659: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
It is related to the bug: CSCuh46442
https://tools.cisco.com/bugsearch/bug/CSCuh46442/?referring_site=ss
This bug is resolved in version : 8.0.100.0
http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn80.html#pgfId-1163951
Can you please paste here "show ap auth-list" from the controller CLI?
I suggest to enable MIC if it is not enabled, and then check if the AP's will join or not.
Kind Regards
Mohammad Setan -
Can we upgrade IOS in WLC 5508 through CISCO prime?
I have CISCO prime 2.0 and CISCO WLC 5508 HA SSO pair.
I would like to upgrade the software code for the WLC HA pair.
Can I do through the CISCO prime ......
As per the link :http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/7-5/High_Availability_DG.html#pgfId-43571
1. After the WLCs are configured in the HA setup, the Standby WLC cannot be upgraded directly from the TFTP/FTP server.
Prime do the upgrade through FTP server , so will it be ok if we do the upgrade through it, for HA WLC.Please check this link to upgrade wLC software in HA setup.
http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/7-5/High_Availability_DG.html
Once the Primary WLC complete the upgrade , it will transfer the entire image to the Standby WLC via the Redundant Port.
Regards
Dont forget to rate helpful posts -
WLC 5508 Discovery in Prime Infrastructure
I have newly deployed a Prime Infrastructure (PI) in my network, and i want to add my wirless controller in it.
I get an error SNMP time out whenever i add my controller to PI through SNMP.
There are default SNMP configurations in the controller and i am simply adding them in PI with their private/public SNMP string.
Is there something i am missing?
WLC 5508 is connected to my core switch and PI is connected to another switch which is directly connected to core switch via Layer 3.
Is there any configuration required to be done on the switch side.?Hello,
Please go through the below link, it may help you to add WLC in Prime Infrastructure (PI)
https://supportforums.cisco.com/docs/DOC-29006 -
Cisco Prime Infrastructure is a damned nightmare of browser bugs (some features work in IE8, some in IE9, and some only in Firefox). And I am not sure if what I am experiencing is a browser bug - or a real bug - or something that I was able to do before and can't any more? I would love for someone to either explain why this is happening to me, or reproduce the bug!
I'm running Prime 2.1.1. I am doing this ...
Configure > Controller Template Launchpad
System > Dynamic Interface
Select a command > Add interface (GO)
Enter all the properties - roll to the bottom of the page, and click Apply to Controllers
I have four controllers. And normally I would add an interface for each controller. But I can only create two out of the four. It doesn't matter which two I choose. When I click Add under Manage Interfaces for the third controller, I cannot click the Done button to apply it (see screenshot, attached). I have found that if I change the VLAN to something else, it will let me save it. But ... why? I went back and reviewed all of my existing interface templates and I am not doing anything different. Although, they were all created a long while ago using WCS 7.x.
Any help, guidance, or confirmation of insanity would be appreciated.
-Steve BallantyneI doubt I will get any hits on this here but I always try. I opened a TAC case. I will come back and comment on whatever they find.
Maybe you are looking for
-
Best practices on number of pipelines in a single project/app to do forging
Hi experts, I need couple of clarification from you regarding endeca guided search for enterprise application. 1)Say for example,I have a web application iEndecaApp which is created by imitating the jsp reference application. All the necessary presen
-
I'm having an issue with using SVE. I'm using LV 8.6 (cannot upgrade to 2010 at this time, have to "make it work"). I've used shared variables before with an HMI and PXI but my setup is different now: PXI (called my target) that "talks" to different
-
Rippling Distotion in iPhoto export
Hi all - I have seen some discussion of this, but no real resolution. I am attempting to export a slideshow from iPhoto to a DV file and when I do so I get a strange rippling distortion (almost a moire pattern) as the ken burns effect pans across the
-
Music videos didnt get transfered from iTunes 6 to 7
How come I installed iTunes 7 but I cant see my videos that i bought in iTunes 5. All I see when I turn on the video it is a green screen that is freaking out, and when I put my mouse on the video screen it turns all black. Can some one please help,
-
When I try to boot the CDROM from the ok Prompt I get an error. Below is the error I get from my E450: ? 'mfg-options' environment variable invalid Can't open input device. screen not found. Can't open input device. Keyboard not present. Using ttya f