Hello, We have a difficulties connecting AIR-LAP1131AG-E-K9 to AIR-WLC2106-K9 , probably becouse of " ETSI CNFG" of AP. What do you think , is it possible to configure AP in the way to behave as "FCC CNFG" ?
Some "debug capwap error" from controller and AP controller: *Jul 14 21:28:15.497: 00:1d:71:e1:76:90 Received an unsupported channel 36 for slot 1 from AP 00:1D:71:E1:76:90 *Jul 14 21:28:15.497: 00:1d:71:e1:76:90 Received an unsupported channel 40 for slot 1 from AP 00:1D:71:E1:76:90 *Jul 14 21:28:15.497: 00:1d:71:e1:76:90 Received an unsupported channel 44 for slot 1 from AP 00:1D:71:E1:76:90 *Jul 14 21:28:15.497: 00:1d:71:e1:76:90 Received an unsupported channel 48 for slot 1 from AP 00:1D:71:E1:76:90 *Jul 14 21:28:15.497: 00:1d:71:e1:76:90 Received an unsupported channel 52 for slot 1 from AP 00:1D:71:E1:76:90 *Jul 14 21:28:15.497: 00:1d:71:e1:76:90 Received an unsupported channel 56 for slot 1 from AP 00:1D:71:E1:76:90 *Jul 14 21:28:15.497: 00:1d:71:e1:76:90 Received an unsupported channel 60 for slot 1 from AP 00:1D:71:E1:76:90 *Jul 14 21:28:15.497: 00:1d:71:e1:76:90 Received an unsupported channel 64 for slot 1 from AP 00:1D:71:E1:76:90 *Jul 14 21:28:15.497: 00:1d:71:e1:76:90 Received an unsupported channel 100 for slot 1 from AP 00:1D:71:E1:76:90 *Jul 14 21:28:15.497: 00:1d:71:e1:76:90 Received an unsupported channel 104 for slot 1 from AP 00:1D:71:E1:76:90 *Jul 14 21:28:15.497: 00:1d:71:e1:76:90 Received an unsupported channel 108 for slot 1 from AP 00:1D:71:E1:76:90 *Jul 14 21:28:15.497: 00:1d:71:e1:76:90 Received an unsupported channel 112 for slot 1 from AP 00:1D:71:E1:76:90 *Jul 14 21:28:15.497: 00:1d:71:e1:76:90 Received an unsupported channel 116 for slot 1 from AP 00:1D:71:E1:76:90 *Jul 14 21:28:15.500: 00:1d:71:e1:76:90 Received an unsupported channel 132 for slot 1 from AP 00:1D:71:E1:76:90 *Jul 14 21:28:15.500: 00:1d:71:e1:76:90 Received an unsupported channel 136 for slot 1 from AP 00:1D:71:E1:76:90 *Jul 14 21:28:15.500: 00:1d:71:e1:76:90 Received an unsupported channel 140 for slot 1 from AP 00:1D:71:E1:76:90 ap: *Jul 14 21:28:28.789: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY *Jul 14 21:28:28.790: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY *Jul 14 21:28:28.802: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down *Jul 14 21:28:28.814: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up *Jul 14 21:28:28.814: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up *Jul 14 21:28:28.815: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down *Jul 14 21:28:28.816: CAPWAP_DETAIL: Vendor specific payload validated. *Jul 14 21:28:28.816: CAPWAP_DETAIL: Vendor specific payload validated. *Jul 14 21:28:28.848: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up *Jul 14 21:28:28.876: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up *Jul 14 21:28:28.907: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up *Jul 14 21:28:38.830: %CAPWAP-3-ERRORLOG: Go join a capwap controller *Jul 14 21:28:39.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.3.2 peer_port: 5246 *Jul 14 21:28:39.001: %CAPWAP-5-CHANGED: CAPWAP changed state to *Jul 14 21:28:40.650: CAPWAP_DETAIL: Dtls Event = 39 Capwap State = 3. *Jul 14 21:28:40.650: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.16.3.2 peer_port: 5246 *Jul 14 21:28:40.652: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.3.2 *Jul 14 21:28:40.652: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN *Jul 14 21:28:40.658: CAPWAP_DETAIL: Vendor specific payload validated. *Jul 14 21:28:40.734: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG *Jul 14 21:28:40.734: %CAPWAP-3-ERRORLOG: Starting config timer *Jul 14 21:28:40.741: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.16.3.2 *Jul 14 21:28:40.741: %DTLS-5-PEER_DISCONNECT: Peer 172.16.3.2 has closed connection. *Jul 14 21:28:40.742: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 172.16.3.2:5246 *Jul 14 21:28:40.742: CAPWAP_DETAIL: Dtls Event = 38 Capwap State = 8. -- Best Regards, _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
