Changes between Version 21 and Version 22 of Tutorials/g0WmLTE/Tutorial5


Ignore:
Timestamp:
May 31, 2016, 10:14:47 PM (8 years ago)
Author:
msherman
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Tutorials/g0WmLTE/Tutorial5

    v21 v22  
    11=== !AmariSoft LTE ===
    2 
    3 [[TOC(noheading, Tutorials/g0WmLTE*, depth=2)]]
    42
    53[[Include(Documentation/Short/Prereq)]]
    64
    7 This tutorial also assumes basic familiarity with [http://en.wikipedia.org/wiki/LTE_%28telecommunication%29 LTE standard]. It uses [http://www.openairinterface.org/ OpenAirInterface] open source software implementation of LTE basestation (eNodeB or eNB) and modem (user equipment or UE) developed at [http://www.eurecom.fr/en Eurecom]. The tutorial given here is based on the [https://twiki.eurecom.fr/twiki/bin/view/OpenAirInterface/HowToConnectOAIENBWithOAIUEWithoutS1Interface] tutorial.
     5The image used for this experiment is 'baseline.ndz'. In this tutorial we will use nodes equipped with Netgear AC341u LTE dongles. The basestation is Amarisoft running on Bsc03out.
    86
    9 The image used for this experiment is 'oai-nos1.ndz'. The image uses Ubuntu 14.04 and has low-latency 3.13 kernel install and UHD drivers needed for B210/X310 USRPs (UHD 3.8.2)) as well as the !OpenAirInteface source code installed in /root/openairinterface5g/. More details on various build options are available on [https://twiki.eurecom.fr/twiki/bin/view/OpenAirInterface/AutoBuild OpenAirInterface build page].
    10 
    11 In this tutorial we will use nodes equipped with USRP B210 and have the basestation on node1-1 and modem on node1-2 on sandbox 1.
    12 
    13 === Quickstart Option ===
    14 We have an image available, named {{{oai-dev.ndz}}}. It has all the necessary driver and software pre-installed, and two scripts available to immediately boot up the eNB and UE.
    15 
    16 1. To proceed, after having a reservation, load the following image.
    17  * {{{omf load -t node1-1,node1-2 -i oai-dev.ndz}}}
    18  * The nodes will automatically turn off when imaging is completed.
    19 1. Turn the nodes on.
    20  * {{{omf tell -a on -t node1-1,node1-2}}}
    21 1. Open a terminal to each node. You must enable X11 Forwarding to see the GUI and statistics screens.
    22  1. This is a two step process, to extend the tunnel to your local machine. SSH with tunnel to the console, and then again with the tunnel from the console to the node.
    23  1. Linux: Simply use the -X or -Y flags, e.g.
    24   1. {{{ssh -Y -t sb1.orbit-lab.org ssh -Y -t node1-1}}}
    25   1. {{{ssh -Y -t sb1.orbit-lab.org ssh -Y -t node1-2}}}
    26   1. If you get an error about ssh keys not matching, you MUST follow the instructions about running ssh-keygen -f. It will not allow X11 forwarding until fixed.
    27  1. Windows: You must either use an X11 capable ssh client, such as mobaXterm or bitvise ssh, or install a standalone x11 client, such as FIXME
    28   1. Start x11 capable client
    29   1. SSH to console
    30   1. SSH to node
    31  1. Mac: You must use an X11 capable ssh client such as FIXME, or install a standalone X11 client such as FIXME
    32   1. Start x11 capable client
    33   1. SSH to console
    34   1. SSH to node
    35 1. On the first node, execute script {{{./CompandRuneNB}}}
    36 1. On the second node, execute script {{{./CompandRunUE}}}
    37 1. For subsequent runs, execute {{{./runeNB}}} or {{{./runUE}}} instead, to avoid recompiling.
    38 1. These scripts will create interface {{{oai0}}} and assign an address.
    39  1. Use {{{ifconfig}}} or {{{ip a}}} to see the address assigned.
    40 1. You should be able to ping from one node to the other on these addresses.
    41 1. For throughput testing
    42  1. On one node, execute {{{iperf -s}}}
    43  1. On the second node, execute {{{iperf -c Put_other_oai_IP_here}}}
    44 
    45 
    46 === Prepare the nodes ===
    47 
    48 ORBIT Images with preloaded OAI software have been made available. If you prefer to prepare a new image starting from a baseline,
    49 
    50 1a. Load the image with the !OpenAirInterface code on the nodes. After imaging the nodes are '''turned off automatically'''. [[CollapsibleStart(omf load -i oai-nos1.ndz -t all)]] [[Include(Documentation/Short/LoadImage)]][[CollapsibleEnd]]
    51 2a. Turn ON the nodes that successfully imaged (give them some time and check their status with '''omf stat''' before proceeding). [[CollapsibleStart(omf tell -a on -t all)]][[Include(Documentation/Short/TellOn)]][[CollapsibleEnd]]
    52 3a. [OPTIONAL] Upgrade to the latest code and compile
    53 
    54 {{{
    55 oai
    56 git pull
    57 cd cmake_targets
    58 ./build_oai -I --install-optional-packages -w USRP
    59 
    60 #If updating eNB
    61 ./build_oai --eNB -C -w USRP
    62 
    63 #If updating UE
    64 ./build_oai --UE -C -w USRP
    65 }}}
    66 
    67 1b. [ALTERNATIVE METHOD] [[CollapsibleStart(Compile from scratch)]][[Include(Documentation/Short/CompileOAI)]][[CollapsibleEnd]]
    68 === Execute the experiment ===
    69 
    70 Primary objective is to establish the LTE connection between the UE and eNB.
    71   1. '''ssh into nodes:''' Open two ssh sessions from the console to the two nodes
    72   2. '''Prepare configuration files:''' The configuration file used for eNB is ''enb.band5.tm1.usrpb210.conf'', located at ''/root/openinterface5g/targets/PROJECTS/GENERIC-LTE-EPC/CONF/''. Another configuration may be used, or a new configuration file can be created using one of the existing ones, so that the parameters can be adjusted.
    73   3. '''Run the lte-softmodem:''' The following commands need to be run in order the execute the LTE softmodem. By default, the IP address of eNB is 10.0.1.1, and the IP of UE is 10.0.1.9. These parameters can be changed in ''/root/openinterface5g/targets/bin/init_nas_nos1''. The user can also choose whether to run the version with or without the graphical analyzer. In order to run the experiment with the graphical analyzer, make sure you have used the '-X' flag to ssh into the console and then into the nodes.
    74 
    75     a. On both nodes, run
    76 
    77 {{{
    78 source /root/openairinterface5g/targets/bin/init_nas_nos1
    79 }}}
    80 
    81     b. On eNB (node1-1), run
    82 
    83 {{{
    84 sh /root/openairinterface5g/targets/bin/init_nas_nos1 eNB
    85 
    86 /root/openairinterface5g/targets/bin/oailtenoviz -d -O /root/enb.band3.tm1.usrpb210.conf 2>&1 | tee ENB.log
    87 }}}
    88 
    89 or, to run it without the graphical analyzer
    90 
    91 {{{
    92 /root/openairinterface5g/targets/bin/lte-softmodem-nos1.Rel10 -d -O /root/enb.band3.tm1.usrpb210.conf 2>&1 | tee ENB.log
    93 }}}
    94 
    95     c. On UE (node1-2), run
    96 
    97 {{{
    98 /root/openairinterface5g/targets/bin/lte-softmodem-nos1.Rel10 -U -C1865000000 -r25 --ue-scan-carrier --ue-txgain 100 --ue-rxgain 110 -A 0 2>&1 | tee UE.log
    99 }}}
    100 
    101 The output on the two consoles should look like:
    102 
    103  ||  node1-1 (eNB)  ||  node1-2 (UE)  ||
    104  ||  [[Image(node1-1.jpg, width=450)]]  ||  [[Image(node1-2.jpg, width=450)]]  ||
    105  
    106 The connection should now be established. As a simple test, you should be able to ping the eNB node from the UE node by running the following command in a separate terminal window:
    107 
    108 {{{
    109 ping 10.0.1.1
    110 }}}
    111 
    112 If the eNB was run using the graphical analyzer, after the connection is established and the pinging starts, the analyzer should look similar to the one shown on the picture below.
    113 
    114 [[Image(analyzer.png, width=500)]]
     7You will run the following commands on node7-1.grid.orbit-lab.org