LN-630acn verbindet sich nicht mit WLC-4006+

Forum zum LANCOM WLC-4100, WLC-4025+, WLC-4025 und WLC-4006 WLAN-Controller

Moderator: Lancom-Systems Moderatoren

Antworten
RambaZambaa
Beiträge: 3
Registriert: 05 Nov 2018, 08:47

LN-630acn verbindet sich nicht mit WLC-4006+

Beitrag von RambaZambaa »

Hallo,

einer meiner Access-Points mag sich nicht mehr mit dem Wlan-Controller verbinden. Ich habe den AC bereits (mehrmals) zurückgesetzt, es mit statischer IP, DHCP etc. probiert. Automatisches annehmen neuer ACs ist aktiviert (und eine default Config vorhanden). Eine explizite Config für diesen AC wurde auch testweise gesetzt. Ändert nichts.

Andere Access-Points (alles L-321er) verbinden sich problemlos. Auch habe ich alle ausgestellten Zertifikate nach Anleitung gelöscht, da der fehlerhafte AccessPoint in der Vergangenheit bereits einmal verbunden war. Das hat funktioniert und alle bereits verbundenen APs (7 Stück) haben nach kurzer Zeit neue Zertifikate ausgestellt bekommen - ..bis auf den nicht kooperierenden LN-630acn.

AP und WLC laufen auf der neuste Firmware (10.20.0298RU2).

Hier ein Auszug aus dem CAPWAP/SCEP Trace. Ein Ping von AP zu WLC und zurück funktioniert. Laut Trace besteht auch Kommunikation (?).
Vielleicht kann mir ja jemand helfen, ich bin mit meinem Latein am Ende.
Danke!

Code: Alles auswählen

DEVICE:                LANCOM LN-630acn dual Wireless
HW-RELEASE:            H
VERSION:               10.20.0298RU2 / 08.12.2018

[Sysinfo] 2019/01/18 08:40:49,352
Result of command: "sysinfo"

DEVICE:                LANCOM LN-630acn dual Wireless
HW-RELEASE:            H
SERIAL-NUMBER:         4005082918100669
MAC-ADDRESS:           00a05740f8bc
IP-ADDRESS:            192.0.0.72
IP-NETMASK:            255.255.255.0
INTRANET-ADDRESS:      0.0.0.0
INTRANETMASK:          0.0.0.0
VERSION:               10.20.0298RU2 / 08.12.2018
VERSION-GIT:           469789bb13d86753738863b185fdacc04a3c8536
NAME:                  
CONFIG-STATUS:         177184;0;2749ef4ba405aaf5ebcd0ef40a657a4be69b73b6.07274418012019.63
FIRMWARE-STATUS:       1;1.4;1.1;10.20.0259RU1.17112018.3;10.20.0298RU2.08122018.4
LOADER:                4.46.0001Rel
WLC-ADDRESS:           0.0.0.0
HW-MASK:               00001100000000000000000000000010
FEATUREWORD:           00000000000000000100000000010000
REGISTERED-WORD:       00000000000000000100000000010000
FEATURE-LIST:          04/F
FEATURE-LIST:          0e/F
FEATURE-LIST:          2b/F
TIME:                  08405118012019
HTTP-PORT:             80
HTTPS-PORT:            443
TELNET-PORT:           23
TELNET-SSL-PORT:       992
SSH-PORT:              22
SNMP-PORT:             161
TFTP-PORT:             69
Production-Date:       2018-09-06
MOD-Level:             H0
LOCATION:              
COUNTRY-CODE:          0/0 (NA)
COMMENT:               
EXTENDED-NAME:         LANCOM LN-630acn dual Wireless
WLAN-1 MAC:            00a0573fcd4a 
WLAN-2 MAC:            00a0573fe8de 
SNMP-PASSWORD-REQ:     0
OEM:                   
VENDOR:                LANCOM Systems
OEMFILE:               1.00;"LANCOM Systems";"LANCOM LN-630acn dual Wireless"
IRQ:                   OK(AR9382-abgn);OK(QCA9880-anac)
PROJECT:               nwapp2 ln630
OpenSSL:               OpenSSL 1.0.2p  14 Aug 2018
HW-ID:                 NWAPP2

[CAPWAP-CTRL] 2019/01/18 08:41:14,673  Devicetime: 2019/01/18 08:41:16,331
CAPWAP Silent Interval timeout:

[CAPWAP-CTRL] 2019/01/18 08:41:14,673  Devicetime: 2019/01/18 08:41:16,331
Change WTP State: Discovery ==> WaitForCertificate

[SCEP-Client] 2019/01/18 08:41:14,673  Devicetime: 2019/01/18 08:41:16,332
SCEP-Client info: [CAPWAP-WTP-Task] SCEPclient-Interface: is certificate available?

[SCEP-Client] 2019/01/18 08:41:14,673  Devicetime: 2019/01/18 08:41:16,332
SCEP-Client info: [CAPWAP-WTP-Task] SCEPclient-Interface: isCertificateAvailable: requested certificate is not configured cert id 0 caid 0

[CAPWAP-CTRL] 2019/01/18 08:41:14,673  Devicetime: 2019/01/18 08:41:16,331
SCEP-Client: not configured

[CAPWAP-CTRL] 2019/01/18 08:41:14,673  Devicetime: 2019/01/18 08:41:16,332
	try anonymous connection

[CAPWAP-CTRL] 2019/01/18 08:41:14,673  Devicetime: 2019/01/18 08:41:16,332
Change WTP State: WaitForCertificate ==> DNS

[CAPWAP-CTRL] 2019/01/18 08:41:14,673  Devicetime: 2019/01/18 08:41:16,332

add local Domain: 'intern' to 'WLC-Address'
start DNS resolve for 'WLC-Address.intern' (RtgTag:0)

[CAPWAP-CTRL] 2019/01/18 08:41:14,673  Devicetime: 2019/01/18 08:41:16,333
DnsResolve:WLC-Address==>192.0.0.254, pending 1

[CAPWAP-CTRL] 2019/01/18 08:41:14,673  Devicetime: 2019/01/18 08:41:16,334

create connection (192.0.0.72 => 192.0.0.254 VLan-Id:0)

create connection (192.0.0.72 => 192.168.10.2 VLan-Id:0)

create broadcast connection (192.0.0.72 => 192.0.0.255 VLan-Id:0)

[CAPWAP-CTRL] 2019/01/18 08:41:14,673  Devicetime: 2019/01/18 08:41:16,337
Change WTP State: DNS ==> Discovery

[CAPWAP-CTRL] 2019/01/18 08:41:14,673  Devicetime: 2019/01/18 08:41:16,337
start discovery delay timer with 18.476s

[CAPWAP-CTRL] 2019/01/18 08:41:14,673  Devicetime: 2019/01/18 08:41:16,338
Set CapWap State: ==> Idle  (Discovery,ConnId: 807)

[CAPWAP-CTRL] 2019/01/18 08:41:14,673  Devicetime: 2019/01/18 08:41:16,339
Set CapWap State: ==> Idle  (Discovery,ConnId: 808)

[CAPWAP-CTRL] 2019/01/18 08:41:14,673  Devicetime: 2019/01/18 08:41:16,339
Set CapWap State: ==> Idle  (Discovery,ConnId: 809)


[CAPWAP-CTRL] 2019/01/18 08:41:33,123  Devicetime: 2019/01/18 08:41:34,814
CAPWAP Discovery Interval timeout (0,0):

[CAPWAP-CTRL] 2019/01/18 08:41:33,123  Devicetime: 2019/01/18 08:41:34,814
start discovery delay timer with 11.693s

[CAPWAP-CTRL] 2019/01/18 08:41:33,123  Devicetime: 2019/01/18 08:41:34,815
CAPWAP Message to transmit:
Job-PID: 2826
UdpConn: L:192.0.0.72:5143  R:192.0.0.254:1027 (RtgTag:0)
Message content:
 Message type: Discovery Request
 Sequence Num: 1
 Flags       : 0
   Discovery Type:            'DNS'
   WTP Board Data:
     Vendor ID:               2356
     WTP Model Number:        LANCOM LN-630acn dual Wireless
     WTP Serial Number:       4005082918100669
     Board ID:                nwapp2
     Board Revision:          H
   WTP Descriptor:
     Max Radios:              2
     Radios in use:           0
     Encrypt Capability:      0x0
     Vendor ID:               2356
     Hardware Version:        
     Vendor ID:               2356
     Software Version:        10.20.0298 / 08.12.2018
     Vendor ID:               2356
     Boot Version:            4.46
   WTP Frame Tunnel Mode:      LocalBridging,
   WTP MAC Type:              'Local MAC'
   Vendor Specific Payload: 'LAN MAC' (1)
     MAC-Addr:       00:a0:57:40:f8:bc

[CAPWAP-CTRL] 2019/01/18 08:41:33,123  Devicetime: 2019/01/18 08:41:34,818
CAPWAP Message to transmit:
Job-PID: 2827
UdpConn: L:192.0.0.72:5144  R:192.168.10.2:1027 (RtgTag:0)
Message content:
 Message type: Discovery Request
 Sequence Num: 1
 Flags       : 0
   Discovery Type:            'Static Configuration'
   WTP Board Data:
     Vendor ID:               2356
     WTP Model Number:        LANCOM LN-630acn dual Wireless
     WTP Serial Number:       4005082918100669
     Board ID:                nwapp2
     Board Revision:          H
   WTP Descriptor:
     Max Radios:              2
     Radios in use:           0
     Encrypt Capability:      0x0
     Vendor ID:               2356
     Hardware Version:        
     Vendor ID:               2356
     Software Version:        10.20.0298 / 08.12.2018
     Vendor ID:               2356
     Boot Version:            4.46
   WTP Frame Tunnel Mode:      LocalBridging,
   WTP MAC Type:              'Local MAC'
   Vendor Specific Payload: 'LAN MAC' (1)
     MAC-Addr:       00:a0:57:40:f8:bc

[CAPWAP-CTRL] 2019/01/18 08:41:33,123  Devicetime: 2019/01/18 08:41:34,820
CAPWAP Message to transmit:
Job-PID: 2828
UdpConn: L:192.0.0.72:5145  R:192.0.0.255:1027 (RtgTag:0)
Message content:
 Message type: Discovery Request
 Sequence Num: 1
 Flags       : 0
   Discovery Type:            'Unknown'
   WTP Board Data:
     Vendor ID:               2356
     WTP Model Number:        LANCOM LN-630acn dual Wireless
     WTP Serial Number:       4005082918100669
     Board ID:                nwapp2
     Board Revision:          H
   Vendor Specific Payload: 'LAN MAC' (1)
     MAC-Addr:       00:a0:57:40:f8:bc

[CAPWAP-CTRL] 2019/01/18 08:41:33,123  Devicetime: 2019/01/18 08:41:34,820
New discovery requests were sent, expecting 2 responses

[CAPWAP-CTRL] 2019/01/18 08:41:33,123  Devicetime: 2019/01/18 08:41:34,822
Change CapWap State: Idle ==> Idle  (Discovery,ConnId: 807)

[CAPWAP-CTRL] 2019/01/18 08:41:33,123  Devicetime: 2019/01/18 08:41:34,822
CAPWAP Message received
Job-PID: 2826
State..: Discovery 
UdpConn: L:192.0.0.72:5143  R:192.0.0.254:1027 (LAN-1, INTRANET)
Message content:
 Message type: Discovery Response
 Sequence Num: 1
 Flags       : 0
   Result Code:               Success
   AC Name Index:             'WLC-4006+' (Idx:1)
   Vendor Specific Payload: 'WLC Preference' (48)
     Preference: 0
   Vendor Specific Payload: 'CPU Load' (49)
     CPU load 5s:     0.79%
     CPU load 60s:    2.11%
     CPU load 300s:   2.40%
   AC Timestamp:              2019/1/18 7:41:35
   AC Descriptor:
     Stations:       0
     Limit:          65535
     Active WTPs:    6
     Max WTPs:       6
     Security:       X.509 Certificate Based,
     R-MAC Field:    yes
     Reserved1:      0x0
     DTLS Policy:    Clear Text Data Channel,
     Vendor ID:               2356
     Hardware Version:        
     Vendor ID:               2356
     Software Version:        10.20.0298 / 07.12.2018
   Vendor Specific Payload: 'Control Encrypt Type' (2)
     Ctrl-Encrypt:   DTLS
   CAPWAP Control IPv4 Addr:
     IP-Addr:           192.0.0.254
     WTP Count:         6
   Vendor Specific Payload: 'LAN MAC' (1)
     MAC-Addr:       00:a0:57:2b:bb:ec

[CAPWAP-CTRL] 2019/01/18 08:41:33,123  Devicetime: 2019/01/18 08:41:34,822
Local time is updated to received WLC time.

[CAPWAP-CTRL] 2019/01/18 08:41:33,123  Devicetime: 2019/01/18 08:41:34,823

Got answer to unicast discovery request

[CAPWAP-CTRL] 2019/01/18 08:41:33,124  Devicetime: 2019/01/18 08:41:34,823
Discovery response received: outstanding 2, received 0

[CAPWAP-CTRL] 2019/01/18 08:41:33,124  Devicetime: 2019/01/18 08:41:34,823
wait 5 seconds for further discovery responses

[CAPWAP-CTRL] 2019/01/18 08:41:33,124  Devicetime: 2019/01/18 08:41:34,823
Change CapWap State: Idle ==> Discovery  (Discovery,ConnId: 807)

[CAPWAP-CTRL] 2019/01/18 08:41:33,124  Devicetime: 2019/01/18 08:41:34,824
Change CapWap State: Idle ==> Idle  (Discovery,ConnId: 808)

[CAPWAP-CTRL] 2019/01/18 08:41:33,124  Devicetime: 2019/01/18 08:41:34,826
Change CapWap State: Idle ==> Discovery  (Discovery,ConnId: 808)

[CAPWAP-CTRL] 2019/01/18 08:41:33,124  Devicetime: 2019/01/18 08:41:34,827
Change CapWap State: Idle ==> Idle  (Discovery,ConnId: 809)

[CAPWAP-CTRL] 2019/01/18 08:41:33,124  Devicetime: 2019/01/18 08:41:34,827
CAPWAP Message received
Job-PID: 2828
State..: Discovery 
UdpConn: L:192.0.0.72:5145  R:192.0.0.255:1027 (LAN-1, INTRANET)
Message content:
 Message type: Discovery Response
 Sequence Num: 1
 Flags       : 0
   Result Code:               Failure
   AC Name Index:             'WLC-4006+' (Idx:1)
   Vendor Specific Payload: 'WLC Preference' (48)
     Preference: 0
   Vendor Specific Payload: 'CPU Load' (49)
     CPU load 5s:     0.79%
     CPU load 60s:    2.11%
     CPU load 300s:   2.40%
   AC Timestamp:              2019/1/18 7:41:35

[CAPWAP-CTRL] 2019/01/18 08:41:33,124  Devicetime: 2019/01/18 08:41:34,827
Local time is updated to received WLC time.

[CAPWAP-CTRL] 2019/01/18 08:41:33,124  Devicetime: 2019/01/18 08:41:34,827

Got answer to broadcast discovery request

[CAPWAP-CTRL] 2019/01/18 08:41:33,124  Devicetime: 2019/01/18 08:41:34,828
Change CapWap State: Idle ==> Discovery  (Discovery,ConnId: 809)

[CAPWAP-CTRL] 2019/01/18 08:41:36,110  Devicetime: 2019/01/18 08:41:37,818
CAPWAP Retransmit timeout
Job-PID: 2827
State..: Discovery 
UdpConn: L:192.0.0.72:5144  R:192.168.10.2:1027 (RtgTag:0)

[CAPWAP-CTRL] 2019/01/18 08:41:36,110  Devicetime: 2019/01/18 08:41:37,818
CAPWAP Message to transmit:
Job-PID: 2827
UdpConn: L:192.0.0.72:5144  R:192.168.10.2:1027 (RtgTag:0)
Message content:
 Message type: Discovery Request
 Sequence Num: 1
 Flags       : 0
   Discovery Type:            'Static Configuration'
   WTP Board Data:
     Vendor ID:               2356
     WTP Model Number:        LANCOM LN-630acn dual Wireless
     WTP Serial Number:       4005082918100669
     Board ID:                nwapp2
     Board Revision:          H
   WTP Descriptor:
     Max Radios:              2
     Radios in use:           0
     Encrypt Capability:      0x0
     Vendor ID:               2356
     Hardware Version:        
     Vendor ID:               2356
     Software Version:        10.20.0298 / 08.12.2018
     Vendor ID:               2356
     Boot Version:            4.46
   WTP Frame Tunnel Mode:      LocalBridging,
   WTP MAC Type:              'Local MAC'
   Vendor Specific Payload: 'LAN MAC' (1)
     MAC-Addr:       00:a0:57:40:f8:bc
   Vendor Specific Payload: 'Trigger to use Router once again' (72)
     Use Router Trigger

[CAPWAP-CTRL] 2019/01/18 08:41:38,114  Devicetime: 2019/01/18 08:41:39,824
CAPWAP Discovery Interval timeout (1,1):

[CAPWAP-CTRL] 2019/01/18 08:41:38,114  Devicetime: 2019/01/18 08:41:39,824
Error: have no valid controller address

[CAPWAP-CTRL] 2019/01/18 08:41:38,114  Devicetime: 2019/01/18 08:41:39,824
start silent interval with 30s

[CAPWAP-CTRL] 2019/01/18 08:41:38,114  Devicetime: 2019/01/18 08:41:39,825
Change CapWap State: Discovery ==> Sulking  (Discovery,ConnId: 807)

[CAPWAP-CTRL] 2019/01/18 08:41:38,114  Devicetime: 2019/01/18 08:41:39,825
Change CapWap State: Discovery ==> Sulking  (Discovery,ConnId: 808)

[CAPWAP-CTRL] 2019/01/18 08:41:38,114  Devicetime: 2019/01/18 08:41:39,826
Change CapWap State: Discovery ==> Sulking  (Discovery,ConnId: 809)


[CAPWAP-CTRL] 2019/01/18 08:42:08,165  Devicetime: 2019/01/18 08:42:09,824
CAPWAP Silent Interval timeout:

[CAPWAP-CTRL] 2019/01/18 08:42:08,165  Devicetime: 2019/01/18 08:42:09,825
Change WTP State: Discovery ==> WaitForCertificate

[SCEP-Client] 2019/01/18 08:42:08,165  Devicetime: 2019/01/18 08:42:09,825
SCEP-Client info: [CAPWAP-WTP-Task] SCEPclient-Interface: is certificate available?

[SCEP-Client] 2019/01/18 08:42:08,165  Devicetime: 2019/01/18 08:42:09,825
SCEP-Client info: [CAPWAP-WTP-Task] SCEPclient-Interface: isCertificateAvailable: requested certificate is not configured cert id 0 caid 0

[CAPWAP-CTRL] 2019/01/18 08:42:08,165  Devicetime: 2019/01/18 08:42:09,825
SCEP-Client: not configured

[CAPWAP-CTRL] 2019/01/18 08:42:08,165  Devicetime: 2019/01/18 08:42:09,825
	try anonymous connection

[CAPWAP-CTRL] 2019/01/18 08:42:08,165  Devicetime: 2019/01/18 08:42:09,826
Change WTP State: WaitForCertificate ==> DNS

[CAPWAP-CTRL] 2019/01/18 08:42:08,165  Devicetime: 2019/01/18 08:42:09,826

add local Domain: 'intern' to 'WLC-Address'
start DNS resolve for 'WLC-Address.intern' (RtgTag:0)

[CAPWAP-CTRL] 2019/01/18 08:42:08,168  Devicetime: 2019/01/18 08:42:09,827
DnsResolve:WLC-Address==>192.0.0.254, pending 1

[CAPWAP-CTRL] 2019/01/18 08:42:08,168  Devicetime: 2019/01/18 08:42:09,828

create connection (192.0.0.72 => 192.0.0.254 VLan-Id:0)

create connection (192.0.0.72 => 192.168.10.2 VLan-Id:0)

create broadcast connection (192.0.0.72 => 192.0.0.255 VLan-Id:0)

[CAPWAP-CTRL] 2019/01/18 08:42:08,168  Devicetime: 2019/01/18 08:42:09,831
Change WTP State: DNS ==> Discovery

[CAPWAP-CTRL] 2019/01/18 08:42:08,169  Devicetime: 2019/01/18 08:42:09,831
start discovery delay timer with 9.042s

[CAPWAP-CTRL] 2019/01/18 08:42:08,169  Devicetime: 2019/01/18 08:42:09,832
Set CapWap State: ==> Idle  (Discovery,ConnId: 810)

[CAPWAP-CTRL] 2019/01/18 08:42:08,169  Devicetime: 2019/01/18 08:42:09,833
Set CapWap State: ==> Idle  (Discovery,ConnId: 811)

[CAPWAP-CTRL] 2019/01/18 08:42:08,169  Devicetime: 2019/01/18 08:42:09,833
Set CapWap State: ==> Idle  (Discovery,ConnId: 812)


[CAPWAP-CTRL] 2019/01/18 08:42:17,180  Devicetime: 2019/01/18 08:42:18,873
CAPWAP Discovery Interval timeout (0,0):

[CAPWAP-CTRL] 2019/01/18 08:42:17,180  Devicetime: 2019/01/18 08:42:18,874
start discovery delay timer with 5.021s
Als Ergänzung hier noch ein Auszug aus dem Trace vom WLC4006+:

Code: Alles auswählen

[CAPWAP-CTRL] 2019/01/18 09:13:21,336  Devicetime: 2019/01/18 09:13:23,463
CAPWAP Message received
Job-PID: 4201 
State..: Idle 
UdpConn: L:192.0.0.254:1027  R:192.0.0.72:5389 (LAN-1, INTRANET)
Message content:
 Message type: Discovery Request
 Sequence Num: 1
 Flags       : 0
   Discovery Type:            'DNS'
   WTP Board Data:
     Vendor ID:               2356
     WTP Model Number:        LANCOM LN-630acn dual Wireless
     WTP Serial Number:       4005082918100669
     Board ID:                nwapp2
     Board Revision:          H
   WTP Descriptor:
     Max Radios:              2
     Radios in use:           0
     Encrypt Capability:      0x0
     Vendor ID:               2356
     Hardware Version:        
     Vendor ID:               2356
     Software Version:        10.20.0298 / 08.12.2018
     Vendor ID:               2356
     Boot Version:            4.46
   WTP Frame Tunnel Mode:      LocalBridging,
   WTP MAC Type:              'Local MAC'
   Vendor Specific Payload: 'LAN MAC' (1)
     MAC-Addr:       00:a0:57:40:f8:bc

[CAPWAP-CTRL] 2019/01/18 09:13:21,336  Devicetime: 2019/01/18 09:13:23,463

Searching script for profile 'JS-WLAN' and version '10.20' -> no script found

[CAPWAP-CTRL] 2019/01/18 09:13:21,336  Devicetime: 2019/01/18 09:13:23,463
Script search result for MAC 00 a0 57 40 f8 bcis 1

[CAPWAP-CTRL] 2019/01/18 09:13:21,336  Devicetime: 2019/01/18 09:13:23,463
CAPWAP Message to transmit:
Job-PID: 4201
UdpConn: L:192.0.0.254:1027  R:192.0.0.72:5389 (LAN-1, INTRANET)
Message content:
 Message type: Discovery Response
 Sequence Num: 1
 Flags       : 0
   Result Code:               Success
   AC Name Index:             'WLC-4006+' (Idx:1)
   Vendor Specific Payload: 'WLC Preference' (48)
     Preference: 0
   Vendor Specific Payload: 'CPU Load' (49)
     CPU load 5s:     1.67%
     CPU load 60s:    0.89%
     CPU load 300s:   0.82%
   AC Timestamp:              2019/1/18 8:13:23
   AC Descriptor:
     Stations:       0
     Limit:          65535
     Active WTPs:    6
     Max WTPs:       6
     Security:       X.509 Certificate Based,
     R-MAC Field:    yes
     Reserved1:      0x0
     DTLS Policy:    Clear Text Data Channel,
     Vendor ID:               2356
     Hardware Version:        
     Vendor ID:               2356
     Software Version:        10.20.0298 / 07.12.2018
   Vendor Specific Payload: 'Control Encrypt Type' (2)
     Ctrl-Encrypt:   DTLS
   CAPWAP Control IPv4 Addr:
     IP-Addr:           192.0.0.254
     WTP Count:         6
   Vendor Specific Payload: 'LAN MAC' (1)
     MAC-Addr:       00:a0:57:2b:bb:ec

[CAPWAP-CTRL] 2019/01/18 09:13:21,338  Devicetime: 2019/01/18 09:13:23,466
CAPWAP Message received
Job-PID: 4202 
State..: Idle 
UdpConn: L:192.0.0.254:1027  R:192.0.0.72:5391 (LAN-1, INTRANET)
Message content:
 Message type: Discovery Request
 Sequence Num: 1
 Flags       : 0
   Discovery Type:            'Unknown'
   WTP Board Data:
     Vendor ID:               2356
     WTP Model Number:        LANCOM LN-630acn dual Wireless
     WTP Serial Number:       4005082918100669
     Board ID:                nwapp2
     Board Revision:          H
   Vendor Specific Payload: 'LAN MAC' (1)
     MAC-Addr:       00:a0:57:40:f8:bc

[CAPWAP-CTRL] 2019/01/18 09:13:21,338  Devicetime: 2019/01/18 09:13:23,466

Searching script for profile 'JS-WLAN' and version '' -> no script found

[CAPWAP-CTRL] 2019/01/18 09:13:21,338  Devicetime: 2019/01/18 09:13:23,466
Script search result for MAC 00 a0 57 40 f8 bcis 1

[CAPWAP-CTRL] 2019/01/18 09:13:21,338  Devicetime: 2019/01/18 09:13:23,466
CAPWAP Message to transmit:
Job-PID: 4202
UdpConn: L:192.0.0.254:1027  R:192.0.0.72:5391 (LAN-1, INTRANET)
Message content:
 Message type: Discovery Response
 Sequence Num: 1
 Flags       : 0
   Result Code:               Failure
   AC Name Index:             'WLC-4006+' (Idx:1)
   Vendor Specific Payload: 'WLC Preference' (48)
     Preference: 0
   Vendor Specific Payload: 'CPU Load' (49)
     CPU load 5s:     1.67%
     CPU load 60s:    0.89%
     CPU load 300s:   0.82%
   AC Timestamp:              2019/1/18 8:13:23
"Searching script for profile 'JS-WLAN' and version '' -> no script found" verwundert mich. Das Profil ist definitiv vorhanden (wird ja auch von mehreren APs genutzt).
RambaZambaa
Beiträge: 3
Registriert: 05 Nov 2018, 08:47

Re: LN-630acn verbindet sich nicht mit WLC-4006+

Beitrag von RambaZambaa »

Die Lösung ist etwas peinlich:
Es können sich ohne (günstige, nur ~600€..) Zusatzlizenz nur 6 APs koppeln. Alle weiteren sind dann einfach als "fehlende APs" im Lanmonitor eingetragen.

Schade, dass der Capwap-Trace nichts zielführendes dazu ausspuckt und auch im Lanmonitor keine Info ersichtlich ist.
Antworten

Zurück zu „Alles zum LANCOM WLC-4100, WLC-4025+, WLC-4025 und WLC-4006 WLAN-Controller“