WLC 2504 problem z dodawaniem AP

Wszystko co się wiąże z technologiami bezprzewodowymi
Wiadomość
Autor
ukaszq
wannabe
wannabe
Posty: 149
Rejestracja: 12 cze 2011, 21:53

WLC 2504 problem z dodawaniem AP

#1

#1 Post autor: ukaszq »

Witam,

Mam WLC 2504 z IOS 7.6.120 podłączone do switcha Cisco 2960X z vlanem 123 i adresem IP: 10.10.28.5. W drugiej lokalizacji mam podłączone AP 2702l. Mam problem z dodaniem APs do kontrolera. W tej lokalizacji APs są podłączone też do vlana 123 o adresacji 10.10.27.0/24. Również podłączone do Cisco 2960X. Ping do kontrolera jest, z kontrolera do AP tez. Cały czas pojawia mi się w AP błąd:

Kod: Zaznacz cały

*Dec  4 13:18:17.007: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Dec  4 13:18:27.007: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Dec  4 13:18:27.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.10.28.6 peer_port: 5246
*Dec  4 13:18:56.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2176 Max retransmission count reached!
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Dec  4 13:19:26.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.10.28.6:5246
*Dec  4 13:19:26.999: %SYS-3-MGDTIMER: Uninitialized timer, timer stop, timer = 3AFD270. -Process= "CAPWAP CLIENT", ipl= 0, pid= 73
-Traceback= 119AF80z 12A89C8z 12AA11Cz 16F512Cz 17645ECz 16FF088z 172810Cz 17299B4z 1720150z 1720228z 17204ECz 1717E50z 172F6A0z 173075Cz 1324C90z 1309B58z
*Dec  4 13:19:26.999: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Dec  4 13:19:26.999: %LWAPP-3-CLIENTERRORLOG: Config load from flash failed. Initialising Cfg

*Dec  4 13:19:26.999: %CAPWAP-3-ERRORLOG: Failed to load configuration from flash. Resetting to default config
*Dec  4 13:19:27.007: %LWAPP-3-CLIENTERRORLOG: Config load from flash failed. Initialising Cfg
AP:

APf44e.0580.e31c#show capwap ip config

Kod: Zaznacz cały

LWAPP Static IP Configuration
IP Address         10.10.27.40
IP netmask         255.255.255.0
Default Gateway    10.10.27.2
Primary Controller 10.10.28.5

Kod: Zaznacz cały

cisco AIR-CAP2702I-E-K9 (PowerPC) processor (revision A0) with 204790K/57344K bytes of memory.
Processor board ID FCZ1843J29L
PowerPC CPU at 800MHz, revision number 0x2151
Last reset from power-on
LWAPP image version 7.6.100.0
1 Gigabit Ethernet interface

32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: F4:4E:05:80:E3:1C
Part Number                          : 73-15824-03
PCA Assembly Number                  : 000-00000-00
PCA Revision Number                  :
PCB Serial Number                    : FOC18400CDL
Top Assembly Part Number             : 800-41174-01
Top Assembly Serial Number           : FCZ1843J29L
Top Revision Number                  : A0
Product/Model Number                 : AIR-CAP2702I-E-K9
Co może być powodem, że nie mogę ich dodać?
Proszę o pomoc.

kanar
member
member
Posty: 39
Rejestracja: 10 lut 2014, 21:51

#2

#2 Post autor: kanar »

hej

Problem z ustanowieniem szyfrowanego połączenia.

Mógłbyś wrzucić output z AP :

debug dtls client error

oraz

debug dtls client events

Awatar użytkownika
Grzegorz
wannabe
wannabe
Posty: 161
Rejestracja: 27 paź 2003, 12:01
Lokalizacja: PL

#3

#3 Post autor: Grzegorz »

skąd różnica?
w logu jest 10.10.28.6
a w konfiguracji AP 10.10.28.5
Pozdrawiam
Grzegorz

ukaszq
wannabe
wannabe
Posty: 149
Rejestracja: 12 cze 2011, 21:53

#4

#4 Post autor: ukaszq »

Witam,

10.10.28.6 to AP-Manager na WLC.
10.10.28.5 - mng WLC

ukaszq
wannabe
wannabe
Posty: 149
Rejestracja: 12 cze 2011, 21:53

#5

#5 Post autor: ukaszq »

Oto logi z debug:

Kod: Zaznacz cały

*Dec  5 10:38:16.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2176 Max retransmission count reached!
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Dec  5 10:38:46.999: DTLS_CLIENT_EVENT: dtls_disconnect: Disconnecting DTLS connection 0x58AC004
*Dec  5 10:38:46.999: DTLS_CLIENT_EVENT: dtls_send_Alert: Sending FATAL : Close notify Alert
*Dec  5 10:38:46.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.35.5:5246
*Dec  5 10:38:46.999: DTLS_CLIENT_EVENT: wtpDtlsCallback: DTLS-Ctrl Connection 0x58AC004 closed
*Dec  5 10:38:46.999: DTLS_CLIENT_EVENT: dtls_free_connection: Done... for connection 0x58AC004
*Dec  5 10:38:46.999: DTLS_CLIENT_EVENT: dtls_connectionDB_del_connection:
DTLS connection deleted from connection DB, count=0

*Dec  5 10:38:46.999: DTLS_CLIENT_EVENT: dtls_connectionDB_del_connection: Deleted Connection details, server 5.110.53.120:5246, client 5.110.53.152:3634

*Dec  5 10:38:46.999: %SYS-3-MGDTIMER: Uninitialized timer, timer stop, timer = 3AFD270. -Process= "CAPWAP CLIENT", ipl= 0, pid= 73
-Traceback= 119AF80z 12A89C8z 12AA11Cz 16F512Cz 17645ECz 16FF088z 172810Cz 17299B4z 1720150z 1720228z 17204ECz 1717E50z 172F6A0z 173075Cz 1324C90z 1309B58z
*Dec  5 10:38:46.999: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Dec  5 10:38:46.999: %LWAPP-3-CLIENTERRORLOG: Config load from flash failed. Initialising Cfg

*Dec  5 10:38:46.999: %CAPWAP-3-ERRORLOG: Failed to load configuration from flash. Resetting to default config
*Dec  5 10:38:47.007: %LWAPP-3-CLIENTERRORLOG: Config load from flash failed. Initialising Cfg


*Dec  5 10:38:56.007: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Dec  5 10:39:06.007: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Dec  5 10:39:06.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.35.5 peer_port: 5246
*Dec  5 10:39:06.000: DTLS_CLIENT_EVENT: dtls_connectionDB_add_connection: Connection added 10.10.27.40, E32, 192.168.35.5, 147E

*Dec  5 10:39:07.999: DTLS_CLIENT_EVENT: dtls_connection_retransmit: Retransmit handshake record to 192.168.35.5:5246
*Dec  5 10:39:11.999: DTLS_CLIENT_EVENT: dtls_connection_retransmit: Retransmit handshake record to 192.168.35.5:5246
*Dec  5 10:39:19.999: DTLS_CLIENT_EVENT: dtls_connection_retransmit: Retransmit handshake record to 192.168.35.5:5246
*Dec  5 10:39:35.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2176 Max retransmission count reached!
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Dec  5 10:40:05.999: DTLS_CLIENT_EVENT: dtls_disconnect: Disconnecting DTLS connection 0x58AC004
*Dec  5 10:40:05.999: DTLS_CLIENT_EVENT: dtls_send_Alert: Sending FATAL : Close notify Alert
*Dec  5 10:40:05.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.35.5:5246
*Dec  5 10:40:05.999: DTLS_CLIENT_EVENT: wtpDtlsCallback: DTLS-Ctrl Connection 0x58AC004 closed
*Dec  5 10:40:05.999: DTLS_CLIENT_EVENT: dtls_free_connection: Done... for connection 0x58AC004
*Dec  5 10:40:05.999: DTLS_CLIENT_EVENT: dtls_connectionDB_del_connection:
DTLS connection deleted from connection DB, count=0

*Dec  5 10:40:05.999: DTLS_CLIENT_EVENT: dtls_connectionDB_del_connection: Deleted Connection details, server 5.110.53.120:5246, client 5.110.53.152:3634

*Dec  5 10:40:05.999: %SYS-3-MGDTIMER: Uninitialized timer, timer stop, timer = 3AFD270. -Process= "CAPWAP CLIENT", ipl= 0, pid= 73
-Traceback= 119AF80z 12A89C8z 12AA11Cz 16F512Cz 17645ECz 16FF088z 172810Cz 17299B4z 1720150z 1720228z 17204ECz 1717E50z 172F6A0z 173075Cz 1324C90z 1309B58z
*Dec  5 10:40:05.999: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Dec  5 10:40:05.999: %LWAPP-3-CLIENTERRORLOG: Config load from flash failed. Initialising Cfg

*Dec  5 10:40:05.999: %CAPWAP-3-ERRORLOG: Failed to load configuration from flash. Resetting to default config
*Dec  5 10:40:06.007: %LWAPP-3-CLIENTERRORLOG: Config load from flash failed. Initialising Cfg


*Dec  5 10:40:15.007: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Dec  5 10:40:25.007: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Dec  5 10:40:25.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.35.5 peer_port: 5246
*Dec  5 10:40:25.000: DTLS_CLIENT_EVENT: dtls_connectionDB_add_connection: Connection added 10.10.27.40, E32, 192.168.35.5, 147E

*Dec  5 10:40:26.999: DTLS_CLIENT_EVENT: dtls_connection_retransmit: Retransmit handshake record to 192.168.35.5:5246
*Dec  5 10:40:30.999: DTLS_CLIENT_EVENT: dtls_connection_retransmit: Retransmit handshake record to 192.168.35.5:5246
*Dec  5 10:40:38.999: DTLS_CLIENT_EVENT: dtls_connection_retransmit: Retransmit handshake record to 192.168.35.5:5246
*Dec  5 10:40:54.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2176 Max retransmission count reached!
192.168.35.5 - to jeden z interfaceow w WLC.

jachu_87
CCIE
CCIE
Posty: 100
Rejestracja: 22 cze 2010, 16:27

#6

#6 Post autor: jachu_87 »

Sprawdź na WLC czy akceptujesz Self-Signed Certificates albo MIC (Manufactured Installed Certicate).

Pozdrawiam,

kanar
member
member
Posty: 39
Rejestracja: 10 lut 2014, 21:51

#7

#7 Post autor: kanar »

Moja rada: jeżeli opcja 43 w pakietach dhcp informuje ap o kontrolerze to zmień wartość na 10.10.28.5 - Mgmt WLC. Niestety nie wiem czy nowe releasy coś zmieniły w tej kwestii ale zawsze odnosiło się to do adresu management kontrolera.

Takie dośc istotne info w troubleshootingu:
AP wydane po 2005 maja MIC a przed 2005 SSC.

Seba
CCIE/CCDE Site Admin
CCIE/CCDE Site Admin
Posty: 6223
Rejestracja: 15 lip 2004, 20:35
Lokalizacja: Warsaw, PL

#8

#8 Post autor: Seba »

Koledzy słusznie zauważają, że coś nie do końca jest tak jeśli chodzi o definicje IP WLC.
W statycznej konfiguracji, a tak w metodach dynamicznych (ption 43, DNS, ip helper-address) używamy IP interfejsu management.

Może być, że trafiłeś na bug CSCuo35247; obejście wymaga zmiany softu na 7.6.130 lub 8.0
"Two things are infinite: the universe and human stupidity; and I'm not sure about the universe."
A. Einstein

golisz
member
member
Posty: 30
Rejestracja: 30 sty 2015, 21:45

#9

#9 Post autor: golisz »

Mialem pare razy problemy z 3602 ale po zaktualizowaniu firmware na controlerze do najnowszego nie mialem juz wiecej tego problemu.
Mialem ten problem z 5508. Pracowalem nad projektem dla szkol gdzie na controllerach mialem ponad 6K - 1142 access pointow. Client sobie zarzyczyl 3602 i wtedy wlasnie zaczal sie moj problem. Po aktualizacji i kilkunastu ticketach do cisco, przekierowaniach do roznych tecow i kilkunastu dniach rozmow wkoncu udalo sie znalesc problem ktory zostal rozwiazany w nowym update.

ODPOWIEDZ