Changes between Version 7 and Version 8 of Tutorials/4G5G/Inter Digital-5G


Ignore:
Timestamp:
Mar 1, 2020, 4:02:56 PM (4 years ago)
Author:
seskar
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Tutorials/4G5G/Inter Digital-5G

    v7 v8  
    88[[Image(InterDigital-5G-NR-Tut.png, 800px)]]
    99
    10 TODDO Setup Description:
    11  * gNodeB and UE
    12  * Two nodes for controling them
    13  * Three subnets as shown
    14  * routing
     10As can be seen from the figure, the setup consists of one gNodeB and one UE unit and the two sandbox 1 servers (in this case srv3-lg1.sb1.cosmos-lab.org and srv4-lg1.sb1.cosmos-lab.org). The first server (srv3-lg1) acts as a gateway while the second one is acting as a UE computing platform (to which a UE modem is attached). The 5G Platform devices and the nodes are connected to the sandbox 1 data 1 network and relies on IP routing to ensure that the traffic flow from the client follows the dashed red line in the figure. To intended route is devided in three segment (IP subnets):
     11 * gNodeB Subnet (192.168.1.X) - connecting gateway to the gNodeB device
     12 * UE Subnet (192.168.2.X) - connects client node to the UE device
     13 * 5G Subnet (192.168.3.X) - connects UE to the gNodeB over the 5G link
     14This setup requires configuring the routing tables on all 4 devices to ensure appropriate traffic flow (in addition to a common '''Data 1''' Ethernet that is shared between all 4 units, the server nodes also have a second direct Ethernet connection through the '''Control''' network that is used for node management and results collection). 
    1515
    1616== Prerequisites ==
    … …  
    2222 1. If you don't have one already, sign up for a [https://www.cosmos-lab.org/portal-2/ COSMOS account]
    2323 1. [Documentation/Short/CreateRes Create a resource reservation] on sandbox 1
    24  1. Prepare 5G-NR status page access: either prepare [wiki:/Documentation/ssh_tyunnel ssh tunnel] thought console to gNodeB server node, port 3005 (i.e. map localhost:8080 to srv3-lg1.sb1.cosmos-lab.org:3005) or follow the instructions to establish a [wiki:/Documentation/VPN VPN tunnel] to the [wiki:/hardware/Domains/sb1 COSMOS sandbox 1]. This will be used by the browser to connect to a web server running on the server nodes.
     24 1. Prepare your computer (i.e. laptop) for 5G-NR status page access: either prepare [wiki:/Documentation/ssh_tunnel ssh tunnel] thought the sandbox 1 console to gNodeB server node, port 3005 (i.e. map localhost:8080 to srv3-lg1.sb1.cosmos-lab.org:3005) or follow the instructions to establish a [wiki:/Documentation/VPN VPN tunnel] to the [wiki:/hardware/Domains/sb1 COSMOS sandbox 1]. This will be used by the browser to connect to a web server running on the server nodes.
    2525 1. [Documentation/Short/Login Login] into sandbox 1 console (console.sb1.cosmos-lab.org) with two SSH sessions. The first session will be used for access to gNodeB while the second will be dedicated to handling UE.
    2626 1. Load the images on the computing nodes: in each of the two session, start the [Documentation/Short/LoadImage  omf image loading] commands:
    … …  
    9393{{{#!td
    9494{{{
    95 #!/bin/bash
    96 # Start the UE on the MPU
    97 sshpass -p "root" ssh -o StrictHostKeyChecking=no root@192.168.2.1 "sh /home/root/start_all.sh &"
    98 # Turn on routing
     95#!/bin/bash                                                                                                   
     96echo "---------------"
     97echo "Make sure to start the UE modem on the MPU by logging in with:"
     98echo "sshpass -p "root" ssh -o StrictHostKeyChecking=no root@192.168.2.1"
     99echo "and running:"
     100echo "root@NR-SW-MPU-UE:~# ./start_all.sh"
     101echo "----------------"
     102# Turn on routing                                                                                             
    99103echo 1 > /proc/sys/net/ipv4/ip_forward
    100104sysctl -w net.ipv4.ip_no_pmtu_disc=1
    101 # Route all internal 5G traffic through MPU
     105# Route all internal 5G traffic through the UE  MPU                                                           
     106ip route add 192.168.3.0/24 via 192.168.2.1 dev eth0
    102107ip route add 192.168.1.0/24 via 192.168.2.1 dev eth0
    103 # Except for the testbed bound traffic
     108# Testbed bound traffic stil goes over the control subnet                                                     
    104109ip r add 10/8 dev eth1
    105 # Everything else goes over 5G ink
    106 ip r add default via 192.168.1.1
     110# Everything else goes over the 5G link                                                                       
     111# (remove default over control network)                                                                       
     112ip r del default dev eth1
     113ip r add default via 192.168.2.1 dev eth0
    107114}}}
    108115}}}
    … …  
    136143}}}
    137144
    138 The two scripts will start the appropriate firmware on both NR Platform devices. The NR Platform will automatically “connect” a link between the gNB and UR. This can be verified via the NR GUI
     145The two scripts will start the appropriate firmware on both NR Platform devices. The NR Platform will automatically “connect” a link between the gNB and UR. This can be verified via the NR GUI.
     146
     147=== Check the Routing ===
     148
     149Use '''mtr''' utility to confirm that traffic is going through the NR link:
     150{{{
     151root@srv4-lg1:~# mtr -c 1 -r 8.8.8.8
     152Start: Sat Feb 29 14:32:31 2020
     153HOST: srv4-lg1.sb1.cosmos-lab.org Loss%   Snt   Last   Avg  Best  Wrst StDev
     154  1.|-- 192.168.2.1                0.0%     1    0.2   0.2   0.2   0.2   0.0
     155  2.|-- 192.168.3.1                0.0%     1    1.1   1.1   1.1   1.1   0.0
     156  3.|-- 192.168.1.1                0.0%     1    1.3   1.3   1.3   1.3   0.0
     157  4.|-- ???                       100.0     1    0.0   0.0   0.0   0.0   0.0
     158  5.|-- vlan-102-ar01-winlab-fsci  0.0%     1    2.2   2.2   2.2   2.2   0.0
     159  6.|-- xe-1-0-6-2000-dr10-lor-cd  0.0%     1    1.8   1.8   1.8   1.8   0.0
     160  7.|-- ae14-2000-cr10-fsci-nbp.r  0.0%     1    1.8   1.8   1.8   1.8   0.0
     161  8.|-- ae17-2000-cr10-hill-nbp.r  0.0%     1    2.3   2.3   2.3   2.3   0.0
     162  9.|-- ae16-2000-cr02-halsey-nwk  0.0%     1    2.7   2.7   2.7   2.7   0.0
     163 10.|-- ae17-0-er10-halsey-ext.ru  0.0%     1    2.8   2.8   2.8   2.8   0.0
     164 11.|-- gateway-pni.google.com     0.0%     1    4.0   4.0   4.0   4.0   0.0
     165 12.|-- 108.170.248.65             0.0%     1    3.0   3.0   3.0   3.0   0.0
     166 13.|-- ???                       100.0     1    0.0   0.0   0.0   0.0   0.0
     167 14.|-- dns.google                 0.0%     1    2.9   2.9   2.9   2.9   0.0
     168root@srv4-lg1:~#
     169}}}
    139170
    140171=== GUI Setup & Instructions ===
    … …  
    147178The following commands are provided as an example of how to send Downlink iperf data traffic on the NR 28GHz mmW OTA link via the compute machines that are attached to the gNB and UE platforms
    148179
     180
    149181 * In the UE console session start the iperf server
    150182{{{
    151 root@srv4.lg1:~$ iperf3 -s -i 1
    152 }}}
    153 
     183iperf3 -s -i 1
     184}}}
    154185 * In the gNodeB session strat the iperf client
    155186{{{
    156 root@srv3-lg1:~# iperf3 -c 192.168.2.1 -i 1 -u -b 86M -l 1472 -t 3600
     187iperf3 -c 192.168.2.2 -i 1 -u -b 20M -l 1472 -t 3
     188}}}
     189
     190The results should be (the actual link performance will also depend on the physical antenna alignment):
     191
     192{{{#!td align=center
     193'''gNodeB''' (srv3-lg1)
     194}}}
     195{{{#!td align=center
     196'''UE''' (srv4-lg1)
     197}}}
     198|---------------
     199|---------------
     200{{{#!td align=left valign=top
     201{{{
     202root@srv3-lg1:/# iperf3 -c 192.168.2.2 -i 1 -u -b 20M -l 1472 -t 3
     203Connecting to host 192.168.2.2, port 5201
     204[  4] local 192.168.1.1 port 57961 connected to 192.168.2.2 port 5201
     205[ ID] Interval           Transfer     Bandwidth       Total Datagrams
     206[  4]   0.00-1.00   sec  2.15 MBytes  18.0 Mbits/sec  1532 
     207[  4]   1.00-2.00   sec  2.39 MBytes  20.0 Mbits/sec  1699 
     208[  4]   2.00-3.00   sec  2.39 MBytes  20.0 Mbits/sec  1699 
     209- - - - - - - - - - - - - - - - - - - - - - - - -
     210[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
     211[  4]   0.00-3.00   sec  6.92 MBytes  19.4 Mbits/sec  0.808 ms  37/4930 (0.75%) 
     212[  4] Sent 4930 datagrams
     213
     214iperf Done.
     215root@srv3-lg1:/#
     216}}}
     217}}}
     218{{{#!td align=left valign=top
     219{{{
     220root@srv4-lg1:~# iperf3 -s -i 1
     221-----------------------------------------------------------
     222Server listening on 5201
     223-----------------------------------------------------------
     224Accepted connection from 192.168.1.1, port 33190
     225[  5] local 192.168.2.2 port 5201 connected to 192.168.1.1 port 57961
     226[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
     227[  5]   0.00-1.00   sec  1.42 MBytes  11.9 Mbits/sec  6.137 ms  12/1025 (1.2%) 
     228[  5]   1.00-2.00   sec  1.66 MBytes  13.9 Mbits/sec  6.106 ms  11/1190 (0.92%) 
     229[  5]   2.00-3.00   sec  1.65 MBytes  13.9 Mbits/sec  5.470 ms  14/1191 (1.2%) 
     230[  5]   3.00-4.00   sec  1.72 MBytes  14.4 Mbits/sec  1.280 ms  0/1225 (0%) 
     231[  5]   4.00-4.24   sec   430 KBytes  14.4 Mbits/sec  0.808 ms  0/299 (0%) 
     232- - - - - - - - - - - - - - - - - - - - - - - - -
     233[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
     234[  5]   0.00-4.24   sec  6.92 MBytes  13.7 Mbits/sec  0.808 ms  37/4930 (0.75%) 
     235-----------------------------------------------------------
     236Server listening on 5201
     237-----------------------------------------------------------
     238}}}
    157239}}}
    158240