Date: Fri, 29 Mar 2024 07:02:20 +0100 (CET)
Message-ID: <672055431.6308.1711692140833@k5115.pixsoftware.de>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_6307_635107179.1711692140833"
------=_Part_6307_635107179.1711692140833
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Best Practice: Requirements for trace recording
Best Practice: Requirements for trace recording
Description:
This article describes the aspects which have to be taken into account f=
or trace recording in order for the traces to be expressive and useful for =
error analysis.
Requirements:
General requirements:
- A trace always has to be recorded in the error state.<=
/li>
- The exact time has to be noted, when the error occured=
, so that the trace analysis can be focused on this time.
Specific requirements for certain topics:
ePaper:
- When connection problems between an ePaper access point and the=
ePaper server occur, the IP addresses of the access point=
and the server are necessary for analysis.
VPN:
- If the VPN connection is between two LANCOM routers, t=
he traces have to be recorded on both routers at the same time.
- The traces have to be recorded locally and not via the=
VPN connection as otherwise important information would be lost after a di=
sconnect of the VPN connection!
- If multiple VPN connections are established on a router, the VPN-IKE trace has to be filtered to the pub=
lic IP address of the other VPN member.
VoIP:
- The involved telephone numbers have to noted, so that =
the trace analysis can be focused on these.
- When the followin=
g problems occur an additional Wireshark trace h=
as to be recorded of the Internet connection as well as from the local netw=
ork, where the SIP user is located. The procedure is described in<=
span> this Knowledge Base ar=
ticle.=20
- One-sided voice transmission
- Missing voice transmission
WLAN:
- If the behaviour canno=
t be narrowed down to a single access point, the traces ha=
ve to be recorded on all of the potentially affected access points=
.
- The MAC address of the affected WiFi device has to be entered a=
s the Trace MAC.
- The MAC address of the affected WiFi device is necessa=
ry for the trace analysis.
WLAN Controller Scenario:
- The traces have to be recorded on the WLAN Controller and an af=
fected access point at the same time in the error state.
- The CAPWAP-CTRL trace<=
/strong> on the WLAN Controller has to be filtered to the IP addres=
s of an affected access point, so that the trace output is limited=
to this specific access point.
------=_Part_6307_635107179.1711692140833--