LANCOM Support Knowledgebase Document No. 1904.0413.1049.RHOO - V1.90

Ready-made trace configurations for different types of error



Description:

This document contains ready-made trace configurations that can be used for diagnosing a wide variety of error types.

How to perform a trace with a ready-made trace configuration is described in the following Knowledge Base document: Recording a trace with a prefabricated trace configuration


The Support Knowledge Base also provides useful troubleshooting guides to help you solve problems.

To find these documents, please use the full-text search and enter the term “troubleshooting”.



Troubleshooting unusual device behavior:

BehaviorTrace fileComment
The LANCOM device has a very high CPU load.
The LANCOM device restarts regularly/irregularly with a watchdog.The memory analysis should always be performed three times:

· Immediately after starting the device

· After about 5 minutes of operation

· As soon as the free memory in the device becomes significantly lower


Troubleshooting a site-to-site VPN connection:

BehaviorTrace fileComment
A site-to-site VPN connection cannot be established or disconnects on a regular/irregular basis.
No DNS resolution over a site-to-site connection.This trace is unsuitable for connections to LANCOM central-site devices that operate more than 10 active VPN connections.
Problems with the data throughput in the VPN tunnel.
VPN connection problems in combination with XAUTH and Dynamic VPN
VPN connection problems when operating a VPN load balancer.

Troubleshooting a client-to-site VPN connection:

BehaviorTrace fileComment
A client-to-site VPN connection cannot be established or disconnects on a regular/irregular basis.
No DNS resolution over a site-to-site connection.This trace is unsuitable for connections to LANCOM central-site devices that operate more than 10 active VPN connections.
Problems with the data throughput in the VPN tunnel.
VPN connection problems in combination with XAUTH and Dynamic VPN
VPN connection problems when operating a VPN load balancer.

Troubleshooting routing problems:

BehaviorTrace fileComment
Problems with the dynamic route exchange via RIP.
Problems using the border gateway protocol (BGP).
A backup scenario using the VRRP protocol does not work as expected.
In a VRRP scenario, RIP-related problems occur.
Problems in a scenario that operates VRRP, RIP, and VPN in combination.

Troubleshooting VoIP-telephony problems:

For VoIP troubleshooting, you should always capture a Wireshark trace (e.g. with LCOSCAP) from the receive and transmit interfaces (see Notes link).

BehaviorTrace fileComment
Problems when making a call when using the SIP-ALG:
One-way voice communication only.
Problems with telephony (inbound and outbound) with ISDN devices.This trace is also useful when fax communication on an ISDN connection is not working.
Problems with telephony (inbound and outbound) with analog devices.
General problems when making calls (e.g. calls not being established, or disconnecting).

Troubleshooting local area network (LAN) problems:

BehaviorTrace fileComment
Problems resolving IP addresses or communicating with IP addresses that are available on the network.
Contrary to the configuration, IP packets are not passed on correctly between logical interfaces (e.g. a Wi-Fi client cannot reach a client in the LAN).

Troubleshooting in a Wi-Fi scenario (without WLAN controller):

BehaviorTrace fileComment
Client connection issues, both when associating and with connections that function initially.

Roaming problems can be traced too.
and
A point-to-point link cannot be establish or disconnects again and again.
Problems with the Wi-Fi performance (e.g. poor data throughput).
802.1x (RADIUS) dial-in to Wi-Fi is not working properly.
An access point does not broadcast any SSID.
One or more LANCOM ePaper Displays cannot connect to the access point or the display content is not updated.
The Wi-Fi is unstable or very slow when running IP-TV, or IP-TV does not work over Wi-Fi.
Public Spot login is not working properly.
The PMS (Fidelio) interface is not working properly.This trace should always be combined with the Public Spot login trace.



Troubleshooting a controller-based Wi-Fi Scenario:

BehaviorTrace fileComment
One or more access points lose connection to the WLAN controller.
Trace on the controller:
WLC-CAPWAP-CTRL.lcgWLC-CAPWAP-CTRL.lcg

Trace on the access point(s):
AP-CAPWAP-CTRL.lcgAP-CAPWAP-CTRL.lcg
An access point cannot connect to the WLAN controller via AUTO-WDS.This trace should be executed on the controller and on the access point.
One or more access points are not accepted by the WLAN controller.
Trace on the controller:
WLC - Analyse.lcgWLC - Analyse.lcg

Trace on the access point(s):
AP.lcgAP.lcg
Make sure that the AP and WLC can reach one another by IP (e.g. by ping) and that the correct time is configured on the WLC.
Check whether the WLAN controller is refusing to accept new access points due to expired certificates.
Trace on the controller:
WLC_Cert_abgelaufen.lcgWLC_Cert_abgelaufen.lcg
Client steering does not work as expected or is causing problems.
Trace on the controller:
WLC - Client steering.lcgWLC - Client steering.lcg
The WLAN controller does not roll out firmware updates to the access points.
Trace on the controller:
WLC - zentrales-Firmware-update.lcgWLC - zentrales-Firmware-update.lcg

Trace on the access point(s):
AP-Firmwareupdate.lcgAP-Firmwareupdate.lcg
Public Spot login is not working properly.
The PMS (Fidelio) interface is not working properly.This trace should always be combined with the Public Spot login trace (see above).


Troubleshooting problems on the WAN (Internet):

BehaviorTrace fileComment
Problems with VDSL connection establishment, disconnects, or poor data rates.For all devices with built-in VDSL modem (e.g. 179x, 1781VAx, 883/884, 730VA)
Problems with ADSL2+ connection establishment, disconnects, or poor data rates.For all devices with built-in ADSL modem (e.g. 1781A, 831A)
Problems with VDSL connection establishment with devices of the 1906VA series, disconnects, or poor data rates.This trace is for use with the devices LANCOM 1906VA and LANCOM 1906VA-4G.
Problems with IPoE connection establishment.
A cellular connection (UMTS/3G/4G) cannot be establish or disconnects again and again.
The content-filter module does not work as expected (e.g. pages are blocked or not blocked contrary to expectation).
DYN DNS address not updating.
Action table entries do not work as expected.


Catchwords: trace configuration; trace; traces; error; problem; troubleshooting
Please review this document! This document was helpful This document was not helpful