Changes between Version 25 and Version 26 of Tutorials/4G5G/Inter Digital-5G


Ignore:
Timestamp:
Sep 22, 2023, 5:18:28 PM (8 months ago)
Author:
prasanthi
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Tutorials/4G5G/Inter Digital-5G

    v25 v26  
    1010[[Image(InterDigital-5G-NR-Tut.png, 800px)]]
    1111
    12 As 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 srv1-in1.sb1.cosmos-lab.org and srv1-in2.sb1.cosmos-lab.org). The first server (srv1-in1) 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. The intended route is divided into three segment (IP subnets):
     12As 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 srv1-in1.sb1.cosmos-lab.org and srv1-in2.sb1.cosmos-lab.org). The first server (srv1-in1) 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 rely on IP routing to ensure that the traffic flow from the client follows the dashed red line in the figure. The intended route is divided into three segments (IP subnets):
    1313 * gNodeB Subnet (192.168.1.X) - connecting gateway to the gNodeB device
    1414 * UE Subnet (192.168.2.X) - connects client node to the UE device
     
    1717
    1818== Prerequisites ==
    19 In order to access the test bed, create a reservation and have it approved by the reservation service. Access to the resources are granted only after the reservation is confirmed. Please follow the process shown on [wiki:CosmosOverview/Workflow the COSMOS work flow page] to get started.
     19In order to access the test bed, create a reservation and have it approved by the reservation service. Access to the resources is granted only after the reservation is confirmed. Please follow the process shown on [wiki:CosmosOverview/Workflow the COSMOS work flow page] to get started.
    2020
    2121== Tutorial Setup ==
     
    3535 1. Turn the server nodes and NR platform devices on:
    3636{{{#!shell-session
    37 omf tell -a on -t srv1-in1,srv1-in2,rfdev2-1,rfdev2-2
     37omf tell -a on -t srv1-in1,srv1-in2,rfdev2-in1,rfdev2-in2
    3838}}}
    3939   
     
    8787ip route add 192.168.3.0/24 via 192.168.1.2
    8888# as well as for the measurements to come back from the UE over the wire
    89 ip route add 192.168.2.1 via 10.113.1.4 dev eth1
     89ip route add 192.168.2.1 via 10.37.1.4 dev eth1
    9090# and configure NAT for them
    9191iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE
     
    135135logout
    136136Connection to 192.168.1.2 closed.
    137 root@srv3-lg1:~#
     137root@srv1-in1:~#
    138138}}}
    139139 1. ssh into UE MPU at 192.168.2.1 with username "root" and password "root: and execute the setup script "start_all.sh":
    140140{{{#!shell-session
    141 root@srv4-lg1:~# sshpass -p "root" ssh -o StrictHostKeyChecking=no root@192.168.2.1
     141root@srv1-in2:~# sshpass -p "root" ssh -o StrictHostKeyChecking=no root@192.168.2.1
    142142root@NR-SW-MPU-UE:~# ./start_all.sh
    143143root@NR-SW-MPU-UE:~# metal: info:      metal_uio_dev_open: No IRQ for device 3ed80000.shm.
     
    146146logout
    147147Connection to 192.168.2.1 closed.
    148 root@srv4-lg1:~#
     148root@srv1-in2:~#
    149149}}}
    150150
     
    155155Use '''mtr''' utility to confirm that traffic is going through the NR link:
    156156{{{#!shell-session
    157 root@srv4-lg1:~# mtr -c 1 -r 8.8.8.8
    158 Start: Sat Feb 29 14:32:31 2020
    159 HOST: srv4-lg1.sb1.cosmos-lab.org Loss%   Snt   Last   Avg  Best  Wrst StDev
     157root@srv1-in2:~# mtr -c 1 -r 8.8.8.8
     158Start: Fri Sep 22 13:14:06 2023
     159HOST: srv1-in2.sb1.cosmos-lab.org Loss%   Snt   Last   Avg  Best  Wrst StDev
    160160  1.|-- 192.168.2.1                0.0%     1    0.2   0.2   0.2   0.2   0.0
    161161  2.|-- 192.168.3.1                0.0%     1    1.1   1.1   1.1   1.1   0.0
    162   3.|-- 192.168.1.1                0.0%     1    1.3   1.3   1.3   1.3   0.0
     162  3.|-- 192.168.1.1                0.0%     1    1.2   1.2   1.2   1.2   0.0
    163163  4.|-- ???                       100.0     1    0.0   0.0   0.0   0.0   0.0
    164   5.|-- vlan-102-ar01-winlab-fsci  0.0%     1    2.2   2.2   2.2   2.2   0.0
    165   6.|-- xe-1-0-6-2000-dr10-lor-cd  0.0%     1    1.8   1.8   1.8   1.8   0.0
    166   7.|-- ae14-2000-cr10-fsci-nbp.r  0.0%     1    1.8   1.8   1.8   1.8   0.0
    167   8.|-- ae17-2000-cr10-hill-nbp.r  0.0%     1    2.3   2.3   2.3   2.3   0.0
    168   9.|-- ae16-2000-cr02-halsey-nwk  0.0%     1    2.7   2.7   2.7   2.7   0.0
    169  10.|-- ae17-0-er10-halsey-ext.ru  0.0%     1    2.8   2.8   2.8   2.8   0.0
    170  11.|-- gateway-pni.google.com     0.0%     1    4.0   4.0   4.0   4.0   0.0
    171  12.|-- 108.170.248.65             0.0%     1    3.0   3.0   3.0   3.0   0.0
    172  13.|-- ???                       100.0     1    0.0   0.0   0.0   0.0   0.0
    173  14.|-- dns.google                 0.0%     1    2.9   2.9   2.9   2.9   0.0
    174 root@srv4-lg1:~#
     164  5.|-- ???                       100.0     1    0.0   0.0   0.0   0.0   0.0
     165  6.|-- vlan-102-ar01-winlab-fsci  0.0%     1    1.9   1.9   1.9   1.9   0.0
     166  7.|-- 172.29.50.14               0.0%     1    2.1   2.1   2.1   2.1   0.0
     167  8.|-- 172.29.6.25                0.0%     1    1.8   1.8   1.8   1.8   0.0
     168  9.|-- 172.29.6.58                0.0%     1    3.2   3.2   3.2   3.2   0.0
     169 10.|-- 172.29.6.96                0.0%     1    2.7   2.7   2.7   2.7   0.0
     170 11.|-- ???                       100.0     1    0.0   0.0   0.0   0.0   0.0
     171 12.|-- 142.251.249.125            0.0%     1    3.6   3.6   3.6   3.6   0.0
     172 13.|-- 216.239.40.167             0.0%     1    2.7   2.7   2.7   2.7   0.0
     173 14.|-- dns.google                 0.0%     1    2.8   2.8   2.8   2.8   0.0
     174root@srv1-in2:~#
    175175}}}
    176176
     
    242242{{{#!td align=left valign=top
    243243{{{#!shell-session
    244 root@srv3-lg1:/# iperf3 -c 192.168.2.2 -i 1 -u -b 20M -l 1472 -t 3
     244root@srv1-in1:~# iperf3 -c 192.168.2.2 -i 1 -u -b 20M -l 1472 -t 3
    245245Connecting to host 192.168.2.2, port 5201
    246 [  4] local 192.168.1.1 port 57961 connected to 192.168.2.2 port 5201
     246[  4] local 192.168.1.1 port 41249 connected to 192.168.2.2 port 5201
    247247[ ID] Interval           Transfer     Bandwidth       Total Datagrams
    248 [  4]   0.00-1.00   sec  2.15 MBytes  18.0 Mbits/sec  1532 
    249 [  4]   1.00-2.00   sec  2.39 MBytes  20.0 Mbits/sec  1699 
    250 [  4]   2.00-3.00   sec  2.39 MBytes  20.0 Mbits/sec  1699 
     248[  4]   0.00-1.00   sec  2.15 MBytes  18.0 Mbits/sec  1532
     249[  4]   1.00-2.00   sec  2.38 MBytes  20.0 Mbits/sec  1698
     250[  4]   2.00-3.00   sec  2.39 MBytes  20.0 Mbits/sec  1699
    251251- - - - - - - - - - - - - - - - - - - - - - - - -
    252252[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
    253 [  4]   0.00-3.00   sec  6.92 MBytes  19.4 Mbits/sec  0.808 ms  37/4930 (0.75%) 
    254 [  4] Sent 4930 datagrams
     253[  4]   0.00-3.00   sec  6.92 MBytes  19.3 Mbits/sec  0.141 ms  69/4929 (1.4%)
     254[  4] Sent 4929 datagrams
    255255
    256256iperf Done.
    257 root@srv3-lg1:/#
     257root@srv1-in1:~#
    258258}}}
    259259}}}
     
    264264Server listening on 5201
    265265-----------------------------------------------------------
    266 Accepted connection from 192.168.1.1, port 33190
    267 [  5] local 192.168.2.2 port 5201 connected to 192.168.1.1 port 57961
     266Accepted connection from 192.168.1.1, port 55250
     267[  5] local 192.168.2.2 port 5201 connected to 192.168.1.1 port 41249
    268268[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
    269 [  5]   0.00-1.00   sec  1.42 MBytes  11.9 Mbits/sec  6.137 ms  12/1025 (1.2%) 
    270 [  5]   1.00-2.00   sec  1.66 MBytes  13.9 Mbits/sec  6.106 ms  11/1190 (0.92%) 
    271 [  5]   2.00-3.00   sec  1.65 MBytes  13.9 Mbits/sec  5.470 ms  14/1191 (1.2%) 
    272 [  5]   3.00-4.00   sec  1.72 MBytes  14.4 Mbits/sec  1.280 ms  0/1225 (0%) 
    273 [  5]   4.00-4.24   sec   430 KBytes  14.4 Mbits/sec  0.808 ms  0/299 (0%) 
     269[  5]   0.00-1.00   sec  2.12 MBytes  17.7 Mbits/sec  0.130 ms  25/1532 (1.6%)
     270[  5]   1.00-2.00   sec  2.35 MBytes  19.7 Mbits/sec  0.142 ms  25/1698 (1.5%)
     271[  5]   2.00-3.00   sec  2.36 MBytes  19.8 Mbits/sec  0.141 ms  19/1699 (1.1%)
     272[  5]   3.00-3.04   sec  0.00 Bytes  0.00 bits/sec  0.141 ms  0/0 (-nan%)
    274273- - - - - - - - - - - - - - - - - - - - - - - - -
    275274[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
    276 [  5]   0.00-4.24   sec  6.92 MBytes  13.7 Mbits/sec  0.808 ms  37/4930 (0.75%) 
     275[  5]   0.00-3.04   sec  6.92 MBytes  19.1 Mbits/sec  0.141 ms  69/4929 (1.4%)
    277276-----------------------------------------------------------
    278277Server listening on 5201
     
    291290Turn off the server nodes and NR platform devices:
    292291{{{#!shell-session
    293 omf tell -a offh -t srv1-in1,srv1-in2,rfdev2-1,rfdev2-2
     292omf tell -a offh -t srv1-in1,srv1-in2,rfdev2-in1,rfdev2-in2
    294293}}}
    295294
     
    298297If you modify software on any of the server nodes save the image by the [omf save image commands] but don't forget to first prepare the node by executing (this is the example for srv3-lg1 node):
    299298{{{#!shell-session
    300 root@srv3-lg1:~# ./prepare.sh
     299root@srv1-in1:~# ./prepare.sh
    301300}}}
    302301This script will “clean” and “dump” old log files and any other unnecessary files that do not need to be saved as part of the image, thereby reducing the size of the saved image.
    303302At the end of this script, the node will shutdown (it might block your ssh window forcing you to open another one); once back on the console, you can save that node disk image with
    304303{{{#!shell-session
    305 username@console:~# omf save -n srv3-lg1.sb1.cosmos-lab.org
     304username@console:~# omf save -n srv1-in1.sb1.cosmos-lab.org
    306305}}}
    307306(please note the -n option and the FQDN for the node both of which are mandatory for successful saving operation).