From nhofmeyr at sysmocom.de Thu Mar 1 12:27:07 2018 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Thu, 1 Mar 2018 13:27:07 +0100 Subject: Data Rate of EGPRS is Too Low In-Reply-To: References: Message-ID: <20180301122707.GA18710@my.box> On Wed, Feb 28, 2018 at 12:53:21AM +0000, XINKE ZHANG wrote: > Hi all, > > > I have set up the EGPRS network using software bundles (osmo-nitb + osmo-bts-trx + osmo-trx + osmo-pcu + osmo-sgsn + openggsn) based on the USRP B210 platform. Now the cell phone can connect to the EGPRS network, but the network is not stable and the data rate is too low (only about 8kbs). - do you have a proper timing source connected to the B210? - what's your timeslot config? ~N -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From xinke.zhang at hotmail.com Thu Mar 1 13:40:56 2018 From: xinke.zhang at hotmail.com (XINKE ZHANG) Date: Thu, 1 Mar 2018 13:40:56 +0000 Subject: Data Rate of EGPRS is Too Low In-Reply-To: <20180301122707.GA18710@my.box> References: , <20180301122707.GA18710@my.box> Message-ID: GPSDO is mounted upon the B210. And I executes this command "./osmo-trx -g -e". My timeslot config is 3 TCH/F + 3 PDCH. ________________________________ From: Neels Hofmeyr Sent: Thursday, March 1, 2018 12:27 To: XINKE ZHANG Cc: osmocom-net-gprs at lists.osmocom.org Subject: Re: Data Rate of EGPRS is Too Low On Wed, Feb 28, 2018 at 12:53:21AM +0000, XINKE ZHANG wrote: > Hi all, > > > I have set up the EGPRS network using software bundles (osmo-nitb + osmo-bts-trx + osmo-trx + osmo-pcu + osmo-sgsn + openggsn) based on the USRP B210 platform. Now the cell phone can connect to the EGPRS network, but the network is not stable and the data rate is too low (only about 8kbs). - do you have a proper timing source connected to the B210? - what's your timeslot config? ~N -------------- next part -------------- An HTML attachment was scrubbed... URL: From nhofmeyr at sysmocom.de Fri Mar 2 03:01:27 2018 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Fri, 2 Mar 2018 04:01:27 +0100 Subject: Data Rate of EGPRS is Too Low In-Reply-To: References: <20180301122707.GA18710@my.box> Message-ID: <20180302030127.GA3507@my.box> On Thu, Mar 01, 2018 at 01:40:56PM +0000, XINKE ZHANG wrote: > > GPSDO is mounted upon the B210. And I executes this command "./osmo-trx -g -e". Make sure that your B210 actually contains a GPSDO, I myself once thought I had one, but all I did was connect a GPS antenna to a dead socket on the B210. So a B210 even though it has a connector for a GPSDO may have no GPSDO inside... Also the -g option won't tell you if there is no GPSDO inside, it'll just all work the same as before, i.e. unreliably. > My timeslot config is 3 TCH/F + 3 PDCH. Would you mind posting your entire config... I don't really remember what rates I got out of GPRS, IIRC about 10 kbyte/s with 3 PDCH was the ballpark. I Never actually tried EGPRS but I assume it should be at least marginally faster?? Does anyone else know more details? ~N -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From xinke.zhang at hotmail.com Sat Mar 3 12:18:52 2018 From: xinke.zhang at hotmail.com (XINKE ZHANG) Date: Sat, 3 Mar 2018 12:18:52 +0000 Subject: Data Rate of EGPRS is Too Low In-Reply-To: <20180302030127.GA3507@my.box> References: <20180301122707.GA18710@my.box> , <20180302030127.GA3507@my.box> Message-ID: I'm sure that B210 has a GPSDO. I execute 'uhd_usrp_probe' to prove it. My entire config files are attached here. Pls help check it. Thanks. From: Neels Hofmeyr Sent: Friday, March 2, 2018 3:01 To: XINKE ZHANG Cc: osmocom-net-gprs at lists.osmocom.org Subject: Re: Data Rate of EGPRS is Too Low On Thu, Mar 01, 2018 at 01:40:56PM +0000, XINKE ZHANG wrote: > > GPSDO is mounted upon the B210. And I executes this command "./osmo-trx -g -e". Make sure that your B210 actually contains a GPSDO, I myself once thought I had one, but all I did was connect a GPS antenna to a dead socket on the B210. So a B210 even though it has a connector for a GPSDO may have no GPSDO inside... Also the -g option won't tell you if there is no GPSDO inside, it'll just all work the same as before, i.e. unreliably. > My timeslot config is 3 TCH/F + 3 PDCH. Would you mind posting your entire config... I don't really remember what rates I got out of GPRS, IIRC about 10 kbyte/s with 3 PDCH was the ballpark. I Never actually tried EGPRS but I assume it should be at least marginally faster?? Does anyone else know more details? ~N -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: C41738DCEB4943B7B9CD20762F5EBB88.png Type: image/png Size: 161 bytes Desc: C41738DCEB4943B7B9CD20762F5EBB88.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: config.tar.gz Type: application/gzip Size: 1409 bytes Desc: config.tar.gz URL: From nhofmeyr at sysmocom.de Mon Mar 5 22:15:14 2018 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Mon, 5 Mar 2018 23:15:14 +0100 Subject: Data Rate of EGPRS is Too Low In-Reply-To: References: <20180301122707.GA18710@my.box> <20180302030127.GA3507@my.box> Message-ID: <20180305221514.GA7166@my.box> On Sat, Mar 03, 2018 at 12:18:52PM +0000, XINKE ZHANG wrote: > I'm sure that B210 has a GPSDO. I execute 'uhd_usrp_probe' to prove it. I'm not familiar with it, but if you say so. > My entire config files are attached here. Pls help check it. Thanks. It all looks good to me. Two minor notes: - the pcu config once needed 'two-phase-access' to function reliably, but this is no longer needed. - you seem to be running an old version of the ggsn. The new one is called osmo-ggsn with a config file style and vty interface like the other osmo programs. However, this should not affect your downlink throughput. - you also seem to run osmo-nitb, we have moved to separate programs, being osmo-hlr, osmo-msc and osmo-bsc. Refer to http://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_In_The_Box This should, however, not affect your downlink throughput, either. So yeah, sorry, but I have nothing of weight to add. Maybe someone else here has deeper knowledge of EGPRS and SDR based BTS? ~N -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From ssuellid at gmail.com Thu Mar 29 13:44:23 2018 From: ssuellid at gmail.com (Dave Ellis) Date: Thu, 29 Mar 2018 14:44:23 +0100 Subject: Data throughput issues. Increasing throughput. Message-ID: Hi, I need to increase the throughput through the GTP tunnels to around 9Gb/s. I have two servers and they are connected using two GTP tunnels over a Mellanox 25Gb/s link. Via the tunnels I am seeing a total of 4.2 Gb/s to 4.5 Gb/s using iPerf. If data is sent without the tunnels I see a throughput of around 24.5Gb/s. I have tried various tweaks to improve the throughput over the GTP tunnels and have only made marginal gains. I have tried iPerf 2.0.9 and iPerf3 and see the same results. Wireshark shows the iPerf MTU is reflected in the pcap logs. I have tried changing the txqueuelen on the tunnels, changing osmo-ggsn niceness, network buffer sizes etc. The restriction seems to be osmo-ggsn as that is taking up to 92% CPU on one of the cores when the throughput tests are running. I'm hoping I have made a mistake in the configuration of OsmoGGSN and sgsnemu. -- The servers are running Ubuntu 16.04 desktop. 16GB RAM - 12.6GB free when running throughput tests. Intel E52620v3. Mellanox MCX516A-CCAT network adapter. 25Gb direct attach copper connecting the two servers OsmoGGSN version 1.1.0.75-3e44-dirty. For one of the servers: - Mellanox interface details ens3f0 Link encap:Ethernet HWaddr ec:0d:9a:a0:1d:7c inet addr:172.16.8.1 Bcast:172.16.255.255 Mask:255.255.0.0 inet6 addr: fe80::8f38:33e3:bd46:dd65/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 RX packets:142373677 errors:0 dropped:0 overruns:0 frame:0 TX packets:157500406 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:10000 RX bytes:793825609487 (793.8 GB) TX bytes:879898325287 (879.8 GB) Tunnel interface details S1Utun Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:10.1.1.2 P-t-P:10.1.1.2 Mask:255.255.255.0 inet6 addr: fe80::b3fc:3d43:b751:bcbf/64 Scope:Link UP POINTOPOINT RUNNING MTU:9000 Metric:1 RX packets:4640412 errors:0 dropped:0 overruns:0 frame:0 TX packets:2272797 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:37729672063 (37.7 GB) TX bytes:118866016 (118.8 MB) X2Utun Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:10.1.2.2 P-t-P:10.1.2.2 Mask:255.255.255.0 inet6 addr: fe80::6ed8:8a79:b3e9:a51d/64 Scope:Link UP POINTOPOINT RUNNING MTU:9000 Metric:1 RX packets:1824011 errors:0 dropped:0 overruns:0 frame:0 TX packets:3856238 errors:0 dropped:4229 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:95648485 (95.6 MB) TX bytes:31367266755 (31.3 GB) client side iperf server1 iperf3 -c 10.1.2.1 -i1 -t 30 -M8100 -w 2048K -P8 server2 iperf3 -c 10.1.2.1 -i1 -t 30 -M8100 -w 2048K -P8 server1 and 2 iperf server iperf3 -s -i1 osmo-ggsn -c /home/osmo-ggsn.cfg -g 172.16.1.1 contents of osmo-ggsn.cfg ! ! OpenGGSN (0.94.1-adac) configuration saved from vty !! ! log stderr logging filter all 1 logging color 1 logging print category 0 logging timestamp 0 logging level ip info logging level tun info logging level ggsn info logging level sgsn notice logging level icmp6 notice logging level lglobal notice logging level llapd notice logging level linp notice logging level lmux notice logging level lmi notice logging level lmib notice logging level lsms notice logging level lctrl notice logging level lgtp info logging level lstats notice logging level lgsup notice logging level loap notice logging level lss7 notice logging level lsccp notice logging level lsua notice logging level lm3ua notice logging level lmgcp notice ! stats interval 5 ! line vty no login ! ggsn X2Uggsn gtp state-dir /tmp gtp bind-ip 172.16.8.1 gtp gtp0-port 3386 gtp gtp1c-port 2123 gtp gtp1u-port 2153 gtp gtp1uremot-port 2153 apn X2U gtpu-mode tun tun-device X2Utun type-support v4 ip prefix dynamic 10.1.2.0/24 ip dns 0 192.168.100.1 ip dns 1 8.8.8.8 ip ifconfig 10.1.2.2/24 no shutdown default-apn X2U no shutdown ggsn ggsn S1Uggsn gtp state-dir /tmp gtp bind-ip 172.16.8.1 gtp gtp0-port 3387 gtp gtp1c-port 2124 gtp gtp1u-port 2152 gtp gtp1uremot-port 2152 apn S1U gtpu-mode tun tun-device S1Utun type-support v4 ip prefix dynamic 10.1.1.0/24 ip dns 0 192.168.100.1 ip dns 1 8.8.8.8 ip ifconfig 10.1.1.2/24 no shutdown default-apn S1U no shutdown ggsn sgsnemu -l 127.0.0.2 -r 172.16.8.1 --contexts 1 -a S1U -m 4412345678 -q 0x00000000000b921f --defaultroute --pingcount 0 --gtpteid=8 --gtpversion=1 --gsnuip 172.16.1.1 --enduserip 10.1.1.1 --gtp0port 3387 --gtp1cport 2124 --nsapi 1 sgsnemu -l 127.0.0.3 -r 172.16.8.1 --contexts 1 -a X2U -m 4412345678 -q 0x00000000000b921f --defaultroute --pingcount 0 --gtpteid=3 --gtpversion=1 --gsnuip 172.16.1.1 --enduserip 10.1.2.1 --gtp0port 3386 --gtp1cport 2123 --nsapi 2 Hopefully I have provided enough information. Any ideas on how to increase tunnel throughput? Thanks Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From pespin at sysmocom.de Thu Mar 29 14:14:54 2018 From: pespin at sysmocom.de (Pau Espin Pedrol) Date: Thu, 29 Mar 2018 16:14:54 +0200 Subject: Data throughput issues. Increasing throughput. In-Reply-To: References: Message-ID: <0e39f17b-557e-2e2a-6f28-0eb9d6b5afe1@sysmocom.de> Hi Dave, I never personally used it, but as far as I know you should be able to get more performance by using "gtpu-mode kernel-gtp" instead of "gtpu-mode tun" in your config, to avoid doing all packet processing in userspace. Please someone else confirm this. I think you need a capable kernel and libgtpnl to be able to use it. Also, it would be nice if you could provide a linux "perf" output on osmo-ggsn while running your test setup so we can spot possible optimizations to improve osmo-ggsn performance. -- - Pau Espin Pedrol http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte