05-19-2011 02:01 AM - edited 07-03-2021 08:13 PM
Hi,
I have a number of air-lap1142n-e-k9 access points, so far they have all been deployed successfully aprt from this one unit.
When I deployed it, it joined the wlc as normal, downloaded the image, and I was able to rename it etc.. but then a couple of min's later it's status changed to down. It's details on the wlc had changed to name: blank, mac address 0000.0000.0000
I've tried restarting it a couple of times with no luck, below is the output from the console:
Press RETURN to get started!
*Mar 1 00:00:06.711: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self test passed
*Mar 1 00:00:06.722: *** CRASH_LOG = YES
Security Core found.
Base Ethernet MAC address: 50:3D:E5:BE:E8:F8
*Mar 1 00:00:08.683: ERROR: wait 3 failed
*Mar 1 00:00:09.190: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 1
*Mar 1 00:00:09.199: Unsupported radio found of type 0
*Mar 1 00:00:09.236: %LWAPP-3-CLIENTEVENTLOG: Read and initialized AP event log (contains, 1024 messages)
*Mar 1 00:00:10.295: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:11.374: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:11.419: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C1140 Software (C1140-K9W8-M), Version 12.4(21a)JHB1, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Wed 11-Aug-10 15:45 by prod_rel_team
*Mar 1 00:00:11.419: %SNMP-5-COLDSTART: SNMP agent on host AP503d.e5be.e8f8 is undergoing a cold start
*Mar 1 00:13:37.040: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Mar 1 00:13:37.040: bsnInitRcbSlot: slot 0 has venus radio(UNSUPPORT)
*Mar 1 00:13:37.055: bsnUnlockDevice: not bring radio up: radio 0 is in admin disable state
*Mar 1 00:13:37.232: %SSH-5-ENABLED: SSH 2.0 has been enabled
*Mar 1 00:13:37.233: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:13:37.235: Writing radio coredump to 'flash:/r0.rcore'
*Mar 1 00:13:37.407: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Mar 1 00:13:38.239: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Mar 1 00:13:48.469: %DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigned DHCP address 172.31.44.41, mask 255.255.252.0, hostname AP503d.e5be.e8f8
*Mar 1 00:13:49.264: Interface Dot11Radio0: not starting because stop-on-failure set
*Mar 1 00:13:55.919: Interface Dot11Radio0: not starting because stop-on-failure set
*Mar 1 00:13:56.289: Logging LWAPP message to 255.255.255.255.
*Mar 1 00:13:59.364: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
*Mar 1 00:13:59.385: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:14:00.384: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Mar 1 00:14:00.384: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 255.255.255.255 started - CLI initiated
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (192.168.134.251) (192.168.70.51)
*Mar 1 00:14:06.925: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Mar 1 00:14:06.930: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Mar 1 00:14:16.931: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*May 19 08:07:23.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.18.1.40 peer_port: 5246
*May 19 08:07:23.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*May 19 08:07:23.778: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.18.1.40 peer_port: 5246
*May 19 08:07:23.778: %CAPWAP-5-SENDJOIN: sending Join Request to 172.18.1.40
*May 19 08:07:23.779: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*May 19 08:07:28.778: %CAPWAP-5-SENDJOIN: sending Join Request to 172.18.1.40
*May 19 08:08:05.436: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
*May 19 08:08:23.000: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 172.18.1.40:5246
*May 19 08:08:23.040: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*May 19 08:08:23.041: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*May 19 08:08:23.041: bsnInitRcbSlot: slot 0 has venus radio(UNSUPPORT)
*May 19 08:08:23.046: bsnUnlockDevice: not bring radio up: radio 0 is in admin disable state
*May 19 08:08:23.077: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*May 19 08:08:24.077: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*May 19 08:08:33.055: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*May 19 08:08:33.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.18.1.40 peer_port: 5246
*May 19 08:08:33.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*May 19 08:08:33.785: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.18.1.40 peer_port: 5246
*May 19 08:08:33.786: %CAPWAP-5-SENDJOIN: sending Join Request to 172.18.1.40
*May 19 08:08:33.786: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*May 19 08:08:38.786: %CAPWAP-5-SENDJOIN: sending Join Request to 172.18.1.40
I've tried re-imaging the AP a couple of times, with no luck. Is it dead or just in need of help?
Any ideas.
Thanks
Dylan
Solved! Go to Solution.
05-19-2011 02:18 AM
Hi,
We are hitting the software bug and the bug ID is CSCsz56711
The issue is related to PCI componenet on the AP hardware and log that points to that is..
bsnInitRcbSlot: slot 0 has venus radio(UNSUPPORT)
The Replacement is the resolution and please contact your reseller or partner and if ur are the partner then RMA ids the resolution..
Lemme know if this answered ur question and please dont forget to rate the usefull posts!!
Regards
Surendra
05-19-2011 02:18 AM
Hi,
We are hitting the software bug and the bug ID is CSCsz56711
The issue is related to PCI componenet on the AP hardware and log that points to that is..
bsnInitRcbSlot: slot 0 has venus radio(UNSUPPORT)
The Replacement is the resolution and please contact your reseller or partner and if ur are the partner then RMA ids the resolution..
Lemme know if this answered ur question and please dont forget to rate the usefull posts!!
Regards
Surendra
06-13-2011 07:10 AM
Hi Surendra,
Sorry for the delay in responding but I just wanted to wait until I had a solid outcome for this. You were correct it was the bug. The unit was RMA'ed back to Cisco and has now been replaced.
Cheers
Dylan
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide