This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.
Harald Welte gerrit-no-reply at lists.osmocom.orgHarald Welte has submitted this change and it was merged. Change subject: Describe gsmtap log destination ...................................................................... Describe gsmtap log destination Change-Id: If34e1640d1033daacc955f4285013b8c1be644d2 Fixes: OS#2608 --- M .gitignore M common/chapters/logging.adoc A common/images/wireshark-gsmtap-log.png 3 files changed, 25 insertions(+), 1 deletion(-) Approvals: Harald Welte: Looks good to me, approved Jenkins Builder: Verified diff --git a/.gitignore b/.gitignore index 67c2f69..3c72c7f 100644 --- a/.gitignore +++ b/.gitignore @@ -1,6 +1,5 @@ *.html *.svg -*.png *.pdf *.sw? *.bak diff --git a/common/chapters/logging.adoc b/common/chapters/logging.adoc index 85975bb..beb1341 100644 --- a/common/chapters/logging.adoc +++ b/common/chapters/logging.adoc @@ -144,6 +144,31 @@ In the example above 98 is the desired size of the ring buffer (number of messages). Once it's filled, the incoming log messages will push out the oldest messages available in the buffer. +==== Logging via gsmtap + +When debugging complex issues it's handy to be able to reconstruct exact chain of events. This is enabled by using GSMTAP +log output where frames sent/received over the air are intersperced with the log lines. It also simplifies the bug handling +as users don't have to provide separate .pcap and .log files anymore - everything will be inside self-contained packet dump. + +It's configured as follows: +---- +OsmoBSC> enable +OsmoBSC# configure terminal +OsmoBSC(config)# log gsmtap 192.168.2.3 +OsmoBSC(config-log)# +---- + +The hostname/ip argument is optional: if omitted the default 127.0.0.1 will be used. The log strings inside GSMTAP are already +supported by Wireshark. Capturing for `port 4729` on appropriate interface will reveal log messages including source file +name and line number as well as application. This makes it easy to consolidate logs from several different network components +alongside the air frames. You can also use Wireshark to quickly filter logs for a given subsystem, severity, file name etc. + +[[fig-wireshark-gsmtap-log]] +.Wireshark with logs delivered over GSMTAP +image::../common/images/wireshark-gsmtap-log.png[] + +Note: the logs are also duplicated to stderr when GSMTAP logging is configured. + ==== Logging to a file As opposed to Logging to the VTY, logging to files is persistent and diff --git a/common/images/wireshark-gsmtap-log.png b/common/images/wireshark-gsmtap-log.png new file mode 100644 index 0000000..12fde6f --- /dev/null +++ b/common/images/wireshark-gsmtap-log.png Binary files differ -- To view, visit https://gerrit.osmocom.org/5639 To unsubscribe, visit https://gerrit.osmocom.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: If34e1640d1033daacc955f4285013b8c1be644d2 Gerrit-PatchSet: 3 Gerrit-Project: osmo-gsm-manuals Gerrit-Branch: master Gerrit-Owner: Max <msuraev at sysmocom.de> Gerrit-Reviewer: Harald Welte <laforge at gnumonks.org> Gerrit-Reviewer: Jenkins Builder