cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
186
Views
0
Helpful
3
Replies

Cisco 3802 AP is continuously dis-jointing from Controller

I've setup 1 x Controller and and 2 x APs. All of them are Cisco 3802 and all of them have same software 8.5.140.0 and Mobility Express capable. All of the APs are connected to same switch with and same access Vlan. These APs were bench tested and no issue (dis-connecting) found at that time. There were shipped to Melbourne and now after booting, one of the AP has continuously connecting to dis-connecting the Controller. The other AP connected to Controller and has been solid. Same configuration for both APs (client). The AP (in question) doesn't drop from the switch and MAC address is present all the time on the switch port. All the APs have static IPs

 

Could any of you expert advise what can I try to resolve this. Below are logs 

 

Aug 20 06:03:11 kernel: [*08/20/2019 06:03:11.6856] CAPWAP State: Join
Aug 20 06:03:11 kernel: [*08/20/2019 06:03:11.6869] Sending Join request to 10.100.51.212 through port 5256
Aug 20 06:03:11 kernel: [*08/20/2019 06:03:11.6893] Join Response from 10.100.51.212
Aug 20 06:03:11 kernel: [*08/20/2019 06:03:11.7873]
Aug 20 06:03:11 kernel: [*08/20/2019 06:03:11.7873] CAPWAP State: Image Data
Aug 20 06:03:11 kernel: [*08/20/2019 06:03:11.8253] do NO_UPGRADE, part2 is active part
Aug 20 06:03:11 kernel: [*08/20/2019 06:03:11.8290]
Aug 20 06:03:11 kernel: [*08/20/2019 06:03:11.8290] CAPWAP State: Configure
Aug 20 06:03:11 kernel: [*08/20/2019 06:03:11.8311] DOT11_CFG[0] Radio Mode is changed from FlexConnect to FlexConnect
Aug 20 06:03:11 kernel: [*08/20/2019 06:03:11.8316] DOT11_CFG[1] Radio Mode is changed from FlexConnect to FlexConnect
Aug 20 06:03:12 kernel: [*08/20/2019 06:03:12.5944]
Aug 20 06:03:12 kernel: [*08/20/2019 06:03:12.5944] CAPWAP State: Run
Aug 20 06:03:12 kernel: [*08/20/2019 06:03:12.6913] AP has joined controller LAV-Controller
Aug 20 06:03:12 kernel: [*08/20/2019 06:03:12.6982] Flexconnect Switching to Connected Mode!
Aug 20 06:03:13 syslog: Password for user changed
Aug 20 06:03:13 kernel: [*08/20/2019 06:03:13.0186] Password for user changed
Aug 20 06:03:13 kernel: [*08/20/2019 06:03:13.0701] save_on_failure is set to 1
Aug 20 06:03:13 kernel: [*08/20/2019 06:03:13.0704] save_on_failure is set to 1
Aug 20 06:03:13 root: SYS-COND: Retrigger good condition, 5 power
Aug 20 06:03:28 FIPS[19034]: *** shell: FIPS Mode = disabled ***
Aug 20 06:03:40 NCI: I0: openSensor(slot=0)
Aug 20 06:03:40 kernel: [*08/20/2019 06:03:40.6256] set cleanair [slot0][band0] enabled
Aug 20 06:03:40 kernel: [*08/20/2019 06:03:40.6270] set cleanair [slot0][band1] enabled
Aug 20 06:03:40 kernel: [*08/20/2019 06:03:40.6282] set cleanair [slot1][band1] enabled
Aug 20 06:03:41 NCI: I0: SensorApp=1.15.4
Aug 20 06:03:41 NCI: I0: SensorHdw=1.2.3.0
Aug 20 06:03:41 NCI: I0: Hardware Radio Band = [4890, 5935] MHz, BW=150625
Aug 20 06:03:41 NCI: I0: Hardware Radio Band = [2400, 2500] MHz, BW=150625
Aug 20 06:03:41 NCI: slot=0 mode=2 chanCnt=1 cw=1
Aug 20 06:03:41 NCI: chans: 1 0 0 0 0 0 0 0 0 0 0
Aug 20 06:03:41 NCI: I0: channel map channels: in=1 cloned=1
Aug 20 06:03:41 NCI: I0: Requesting MonBand [2412, 2412] bw=20MHz/0 ant=0xbc
Aug 20 06:03:41 NCI: I0: Monitoring (cf=2412, span=20), RadioUsage=3%
Aug 20 06:03:41 NCI: I0: dwell=25000us, update=1000ms, resBW=78126
Aug 20 06:03:41 NCI: CLEANAIR: Slot 0 enabled
Aug 20 06:03:41 NCI: I1: openSensor(slot=1)
Aug 20 06:03:42 NCI: I1: SensorApp=1.15.4
Aug 20 06:03:42 NCI: I1: SensorHdw=1.2.3.0
Aug 20 06:03:42 NCI: I1: Hardware Radio Band = [4890, 5935] MHz, BW=150625
Aug 20 06:03:42 NCI: slot=1 mode=2 chanCnt=4 cw=4
Aug 20 06:03:42 NCI: chans: 100 104 108 112 0 0 0 0 0 0 0
Aug 20 06:03:42 NCI: I1: channel map channels: in=4 cloned=4
Aug 20 06:03:42 NCI: I1: Requesting MonBand [5530, 5530] bw=80MHz/0 ant=0xbc
Aug 20 06:03:42 NCI: I1: Monitoring (cf=5530, span=79), RadioUsage=3%
Aug 20 06:03:42 NCI: I1: dwell=20000us, update=1000ms, resBW=312502
Aug 20 06:03:42 NCI: CLEANAIR: Slot 1 enabled
Aug 20 06:04:16 kernel: [*08/20/2019 06:04:15.9997] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=19, NumofPendingMsgs=3
Aug 20 06:04:16 kernel: [*08/20/2019 06:04:15.9997]
Aug 20 06:04:18 kernel: [*08/20/2019 06:04:18.8506] Re-Tx Count=2, Max Re-Tx Value=5, SendSeqNum=19, NumofPendingMsgs=3
Aug 20 06:04:18 kernel: [*08/20/2019 06:04:18.8506]
Aug 20 06:04:21 kernel: [*08/20/2019 06:04:21.7026] Re-Tx Count=3, Max Re-Tx Value=5, SendSeqNum=19, NumofPendingMsgs=3
Aug 20 06:04:21 kernel: [*08/20/2019 06:04:21.7026]
Aug 20 06:04:24 kernel: [*08/20/2019 06:04:24.5524] Re-Tx Count=4, Max Re-Tx Value=5, SendSeqNum=19, NumofPendingMsgs=3
Aug 20 06:04:24 kernel: [*08/20/2019 06:04:24.5524]
Aug 20 06:04:27 kernel: [*08/20/2019 06:04:27.4033] Re-Tx Count=5, Max Re-Tx Value=5, SendSeqNum=19, NumofPendingMsgs=3
Aug 20 06:04:27 kernel: [*08/20/2019 06:04:27.4033]
Aug 20 06:04:30 kernel: [*08/20/2019 06:04:30.2542] Re-Tx Count=6, Max Re-Tx Value=5, SendSeqNum=19, NumofPendingMsgs=3
Aug 20 06:04:30 kernel: [*08/20/2019 06:04:30.2542]
Aug 20 06:04:30 kernel: [*08/20/2019 06:04:30.2542] Max retransmission count exceeded, going back to DISCOVER mode.
Aug 20 06:04:30 kernel: [*08/20/2019 06:04:30.2545] Flexconnect Switching to Standalone Mode!
Aug 20 06:04:30 kernel: [*08/20/2019 06:04:30.2564]
Aug 20 06:04:30 kernel: [*08/20/2019 06:04:30.2564] CAPWAP State: DTLS Teardown
Aug 20 06:04:31 NCI: CLEANAIR: Slot 0 CAPWAP down
Aug 20 06:04:31 NCI: I0: shutdownNci
Aug 20 06:04:31 NCI: CLEANAIR: Slot 1 CAPWAP down
Aug 20 06:04:31 NCI: I1: shutdownNci

3 REPLIES 3
Highlighted
Hall of Fame Community Legend

Re: Cisco 3802 AP is continuously dis-jointing from Controller

Raise a TAC Case and see if you're hitting any of the following bugs: CSCvh57266, CSCvh63417 or CSCvh54235

Re: Cisco 3802 AP is continuously dis-jointing from Controller

Thanks Leo for the suggestion. 

 

I have two questions here...

 

- We didn't buy the products with support. Would you think Cisco will still allow me to open case?

- Out of curiosity, if this was bug then wouldn't have affected during initial configuration (bench test phase)?

 

Thanks

Hall of Fame Community Legend

Re: Cisco 3802 AP is continuously dis-jointing from Controller

Talk to the vendor who sold you the gear and see if they can raise a TAC Case in your behalf.
CreatePlease to create content
Content for Community-Ad
August's Community Spotlight Awards