| Version 26 (modified by , 8 years ago) ( diff ) |
|---|
OpenAirInterface LTE
Prerequisites
This tutorial series assumes you have an ORBIT account, have scheduled a session on the ORBIT testbed, are familiar with SSH'ing into the testbed itself, and are familiar with the basics of running ORBIT experiments. If you have not done these things yet, you may wish to do so before taking a look at this slightly more advanced experiment. If you are unfamiliar with or are entirely new to ORBIT, you may wish to start here.
This tutorial also assumes basic familiarity with LTE standard. It uses OpenAirInterface open source software implementation of LTE basestation (eNodeB or eNB) and modem (user equipment or UE) developed at Eurecom. The tutorial given here is based on the OAI_real-time_LTEsoftmodem tutorial.
The image used for this experiment is oai-trunk-head.ndz. Image uses Ubunutu 14.04 and has low-latency 3.19 kernel install and UHD drivers needed for B210/X310 USRPs (UHD 3.8.2)). This image was derived from vanilla image ubuntu-14-04-64bit-3.19-lowlatency.ndz (that was created based on OpenAir instructions) from ubutbu-14-04-64bit.ndz (baseline.ndz). In addition to installation steps in OpenAir documentation, once low latency kernel was installed, drivers for Broadcom and Netgear devices had to be manually re-installed.
Two images were created based on git cloning instructions and compiling instructions:
- oai-master.ndz - master branch clone from git in /root
- oai-develop.ndz - develop branch clone from git in /root
The openair-cn (EPC) was installed with default passwords of oai and default choice of "N" for optional packages (freeDiameter, asn1c pach and xtables_addons_oai). xtables_addons_oai was pulled out of git but not installed.
Update for oai-develop.ndz: The openair-cn (EPC) was installed with default passwords of oai and default choice of "Y" for optional packages (freeDiameter, asn1c pach and xtables_addons_oai). xtables_addons_oai was pulled out of git and installed.
Quickstart Option
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. This quickstart assumes use of Sandbox1, nodes 1-1, and 1-2.
- To proceed, after having a reservation, load the following image.
omf load -t node1-1,node1-2 -i oai-dev.ndz- The nodes will automatically turn off when imaging is completed.
- Turn the nodes on.
omf tell -a on -t node1-1,node1-2
- Open a terminal to each node. You must enable X11 Forwarding to see the GUI and statistics screens.
- 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.
- Linux: Simply use the -X or -Y flags, e.g.
ssh -Y -t sb1.orbit-lab.org ssh -Y -t node1-1ssh -Y -t sb1.orbit-lab.org ssh -Y -t node1-2- 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.
- 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
- Start x11 capable client
- SSH to console
- SSH to node
- Mac: You must use an X11 capable ssh client such as FIXME, or install a standalone X11 client such as FIXME
- Start x11 capable client
- SSH to console
- SSH to node
- On the first node, execute script
./CompandRuneNB - On the second node, execute script
./CompandRunUE - For subsequent runs, execute
./runeNBor./runUEinstead, to avoid recompiling. - These scripts will create interface
oai0and assign an address.- Use
ifconfigorip ato see the address assigned. - By default the eNB has address 10.0.1.1, and the UE has addresss 10.0.1.9, but you should double check.
- Use
- You should be able to ping from one node to the other on these addresses.
- From UE,
ping 10.0.1.1or to see live statisticsmtr 10.0.1.1
- From UE,
- For throughput testing
- On the eNB, execute
iperf -s - On the UE, execute
iperf -c 10.0.1.1
- On the eNB, execute
The code was compiled with USRP support i.e. with:
cd trunk/targets/bin; build_oai.bash -l ENB -c -w USRP
More details on various build options are available on OpenAirInterface build page.
In this tutorial we will use nodes with USRP b310 and have the basestation on node9-1 and modem on node6-20.
Prepare the nodes
- Load the image with the OpenAirInterface code on the nodes that have USRP B210 attached. After imaging the nodes are turned off automatically.
omf load -t inventory:topo:B210 -i oai-master.ndz
Load an Image
- Before we begin using the nodes, it's a good idea to check their status first. This is done with the omf stat command.
omf stat
This omf command is used to display the power status of the node/domain.
Usage: omf stat
username@consoles.outdoor:omf stat Returns the status of the nodes in a testbed Usage: omf-5.4 stat [-h] [-s] [-t TOPOLOGY] [-c AGGREGATE] With: -h, --help print this help message -s, --summary print a summary of the node status for the testbed -c, --config AGGREGATE use testbed AGGREGATE -t, --topology TOPOLOGY a valid topology file or description (defaults to 'system:topo:all') Some Examples: omf-5.4 stat omf-5.4 stat -s omf-5.4 stat -t omf.nicta.node1,omf.nicta.node2 -c sb1 omf-5.4 stat -t system:topo:all -c gridIndividual nodes are identified in the output of stat command by their fully qualified domain name (FQDN). This establishes their "coordinates" and the "domain" to which they belong. Nodes in different domains typically can NOT see each other. Node can be in 1 of 3 states:
POWEROFF Node is Available for use but turned off POWERON Node is Available and is on NOT REGISTERED Node is not Available for use Example: omf stat on the outdoor domain
user@console.outdoor:~# omf stat -t all INFO NodeHandler: OMF Experiment Controller 5.4 (git 6d34264) INFO NodeHandler: Slice ID: default_slice (default) INFO NodeHandler: Experiment ID: default_slice-2012-10-14t14.42.15-04.00 INFO NodeHandler: Message authentication is disabled INFO Experiment: load system:exp:stdlib INFO property.resetDelay: value = 210 (Fixnum) INFO property.resetTries: value = 1 (Fixnum) INFO Experiment: load system:exp:eventlib INFO Experiment: load system:exp:stat INFO Topology: Loading topology ''. INFO property.nodes: value = "system:topo:all" (String) INFO property.summary: value = false (FalseClass) INFO Topology: Loading topology 'system:topo:all'. Talking to the CMC service, please wait ----------------------------------------------- Domain: outdoor.orbit-lab.org Node: node3-6.outdoor.orbit-lab.org State: NOT REGISTERED Node: node3-3.outdoor.orbit-lab.org State: POWEROFF Node: node2-10.outdoor.orbit-lab.org State: POWEROFF Node: node1-10.outdoor.orbit-lab.org State: POWEROFF Node: node1-8.outdoor.orbit-lab.org State: POWERON Node: node1-6.outdoor.orbit-lab.org State: POWERON Node: node3-2.outdoor.orbit-lab.org State: POWEROFF Node: node3-1.outdoor.orbit-lab.org State: POWEROFF Node: node1-3.outdoor.orbit-lab.org State: POWERON Node: node3-5.outdoor.orbit-lab.org State: POWEROFF Node: node2-5.outdoor.orbit-lab.org State: NOT REGISTERED Node: node1-2.outdoor.orbit-lab.org State: POWERON ----------------------------------------------- INFO Experiment: Switching ON resources which are OFF INFO EXPERIMENT_DONE: Event triggered. Starting the associated tasks. INFO NodeHandler: INFO NodeHandler: Shutting down experiment, please wait... INFO NodeHandler: INFO run: Experiment default_slice-2012-10-14t14.42.15-04.00 finished after 0:6
- It is recommended that the node be in the POWEROFF state prior to any experiment process. If the node is in the POWERON state you can use the omf tell command to get the node into the off state.
omf tell
OMF command to control the power state/reset the nodes.
Usage: omf tell
user@console:omf tell Switch ON/OFF and reboot the nodes in a testbed Usage: omf tell [-h] -t TOPOLOGY -a ACTION [-c AGGREGATE] With: -h, --help print this help message -a, --action ACTION specify an action ACTION: on turn node(s) ON offs turn node(s) OFF (soft) offh turn node(s) OFF (hard) reboot reboots node(s) (soft) reset resets node(s) (hard) -h, --help print this help message -t, --topology TOPOLOGY a valid topology file or description (MANDATORY) -c, --config AGGREGATE use testbed AGGREGATE Some Examples: omf tell -a reset -t node1-1.grid.orbit-lab.org omf tell -a on -t system:topo:all -c grid omf tell -a reboot -t node1-1 omf tell -a offh -t [1..2,1..5] omf tell -a offh -t system:topo:all omf tell -a reset -t system:topo:imagedThe commands are: on, offh (equivalent to pulling out the power cord), offs (software shutdown), reboot (software reboot) and reset (hardware reset).
Example: turn off node1-1 on the outdoor domain
user@console.outdoor:~# omf tell -a offh -t node1-1 INFO NodeHandler: OMF Experiment Controller 5.4 (git 3fb37b9) INFO NodeHandler: Reading configuration file /etc/omf-expctl-5.4/services.yaml INFO NodeHandler: Add domain http - http://internal1.orbit-lab.org:5054/ INFO NodeHandler: Add domain http - http://repository1.orbit-lab.org:5054/ INFO NodeHandler: Slice ID: default_slice (default) INFO NodeHandler: Experiment ID: default_slice-2014-09-30t00.24.28.504-04.00 INFO NodeHandler: Message authentication is disabled INFO Experiment: load system:exp:stdlib INFO property.resetDelay: resetDelay = 230 (Fixnum) INFO property.resetTries: resetTries = 1 (Fixnum) INFO Experiment: load system:exp:eventlib INFO Experiment: load system:exp:winlib INFO Experiment: load system:exp:tell INFO property.nodes: nodes = "node1-1" (String) INFO property.command: command = "offh" (String) Talking to the CMC service, please wait ----------------------------------------------- Node: node1-1.outdoor.orbit-lab.org Reply: OK ----------------------------------------------- INFO EXPERIMENT_DONE: Event triggered. Starting the associated tasks. INFO NodeHandler: INFO NodeHandler: Shutting down experiment, please wait... INFO NodeHandler: INFO run: Experiment default_slice-2014-09-30t00.24.28.504-04.00 finished after 0:10
- Once node set is on an POWEROFF state, load an image with omf load command
omf load
Load command is used to put an image onto the hard disk of the node.
Usage: omf load
Install a given disk image on the nodes in a testbed Usage: omf-5.4 load [-h] [-i IMAGE_PATH] [-o TIMEOUT] [-t TOPOLOGY] [-c AGGREGATE] With: -h, --help print this help message -c, --config AGGREGATE use testbed AGGREGATE -t, --topology TOPOLOGY a valid topology file or description (defaults to 'system:topo:all') (if a file 'TOPOLOGY' doesn't exist, interpret it as a comma-separated list of nodes) -i, --image IMAGE disk image to load (default is 'baseline.ndz', the latest stable baseline image) -o, --timeout TIMEOUT a duration (in sec.) after which imageNodes should stop waiting for nodes that have not finished their image installation (default is 800 sec, i.e. 13min 20sec) --outpath PATH Path where the resulting Topologies should be saved (default is '/tmp') --outprefix PREFIX Prefix to use for naming the resulting Topologies (default is your experiment ID) Some Examples: omf-5.4 load omf-5.4 load -t system:topo:all -i baseline-2.4.ndz omf-5.4 load -t omf.nicta.node1 -i wireless-2.6.ndz omf-5.4 load -t omf.nicta.node1,omf.nicta.node2 -i baseline.ndz -o 400 omf-5.4 load -t system:topo:circle -i my_Own_Image.ndz omf-5.4 load -t my_Own_Topology -i baseline-2.2.ndz -t 600 -c grid omf-5.4 load -t my_Own_Topology --outpath ./ --outprefix my_Own_PrefixTwo important arguments are TOPOLOGY describing the set of nodes one wishes to image , and !IMAGE specifying the name of the image one wants to load the nodes with. If the imaging process does not does not finish within the default timeout period, that period can be increase by using the -o flag (e.g. -o 1600). Typical command to load both nodes of sandbox 1 with the baseline image would look like:
If the node is in the NOT REGISTERED state, you may need to wait for it to recover the POWEROFF state (it some times requires a few moments for the services to sync up). If the node takes more than 60 seconds to come out of the NODE NOT AVAILABLE state please report it to an administrator.Example: omf load-i baseline.ndz -t node1-1
username@console.sb3:~$ omf load -i baseline.ndz -t node1-1 DEBUG FQDN:console.sb3.orbit-lab.org: INFO NodeHandler: OMF Experiment Controller 5.4 (git 861d645) INFO NodeHandler: Reading configuration file /etc/omf-expctl-5.4/services.yaml INFO NodeHandler: Add domain http - http://internal1.orbit-lab.org:5054/ INFO NodeHandler: Add domain http - http://repository1.orbit-lab.org:5054/ INFO NodeHandler: Add domain http - http://external1.orbit-lab.org:5054/ INFO NodeHandler: Slice ID: pxe_slice INFO NodeHandler: Experiment ID: pxe_slice-2018-08-08t13.41.37.814-04.00 INFO NodeHandler: Message authentication is disabled INFO Experiment: load system:exp:stdlib INFO property.resetDelay: resetDelay = 230 (Fixnum) INFO property.resetTries: resetTries = 1 (Fixnum) INFO Experiment: load system:exp:eventlib INFO Experiment: load system:exp:winlib INFO Experiment: load system:exp:imageNode INFO property.nodes: nodes = "node1-1" (String) INFO property.image: image = "baseline.ndz" (String) INFO property.domain: domain = "sb3.orbit-lab.org" (String) INFO property.outpath: outpath = "/tmp" (String) INFO property.outprefix: outprefix = "pxe_slice-2018-08-08t13.41.37.814-04.00" (String) INFO property.timeout: timeout = 800 (Fixnum) INFO property.resize: resize = nil (NilClass) INFO Topology: Loaded topology 'system:topo:registered'. INFO property.resetDelay: resetDelay = 100 (Fixnum) INFO Experiment: Resetting resources INFO stdlib: Waiting for nodes (Up/Down/Total): 0/1/1 - (still down: node1-1.sb3.orbit-lab.org) [0 sec.] INFO stdlib: Waiting for nodes (Up/Down/Total): 0/1/1 - (still down: node1-1.sb3.orbit-lab.org) [10 sec.] INFO stdlib: Waiting for nodes (Up/Down/Total): 0/1/1 - (still down: node1-1.sb3.orbit-lab.org) [20 sec.] INFO stdlib: Waiting for nodes (Up/Down/Total): 0/1/1 - (still down: node1-1.sb3.orbit-lab.org) [30 sec.] INFO stdlib: Waiting for nodes (Up/Down/Total): 0/1/1 - (still down: node1-1.sb3.orbit-lab.org) [40 sec.] INFO stdlib: Waiting for nodes (Up/Down/Total): 0/1/1 - (still down: node1-1.sb3.orbit-lab.org) [50 sec.] INFO exp: Progress(0/0/1): 0/0/0 min(node1-1.sb3.orbit-lab.org)/avg/max (59) - Timeout: 790 sec. INFO ALL_UP: Event triggered. Starting the associated tasks. INFO BRING_UP: Event triggered. Starting the associated tasks. INFO Experiment: Bringing up resources INFO exp: Progress(0/0/1): 50/50/50 min(node1-1.sb3.orbit-lab.org)/avg/max (59) - Timeout: 780 sec. INFO exp: Progress(0/0/1): 80/80/80 min(node1-1.sb3.orbit-lab.org)/avg/max (59) - Timeout: 770 sec. INFO exp: Progress(1/0/1): 100/100/100 min()/avg/max (59) - Timeout: 760 sec. INFO exp: ----------------------------- INFO exp: Imaging Process Done INFO exp: 1 node successfully imaged - Topology saved in '/tmp/pxe_slice-2018-08-08t13.41.37.814-04.00-topo-success.rb' INFO exp: ----------------------------- INFO EXPERIMENT_DONE: Event triggered. Starting the associated tasks. INFO NodeHandler: INFO NodeHandler: Shutting down experiment, please wait... INFO NodeHandler: INFO NodeHandler: Shutdown flag is set - Turning Off the resources INFO run: Experiment pxe_slice-2018-08-08t13.41.37.814-04.00 finished after 1:44
- Before we begin using the nodes, it's a good idea to check their status first. This is done with the omf stat command.
- Turn ON the nodes that successfully imaged (give them some time and check their status with omf stat before proceeding).
omf tell -a on -t system:topo:imaged
Turn the Nodes ON
To turn the nodes on use omf tell command:
omf tell
OMF command to control the power state/reset the nodes.
Usage: omf tell
user@console:omf tell Switch ON/OFF and reboot the nodes in a testbed Usage: omf tell [-h] -t TOPOLOGY -a ACTION [-c AGGREGATE] With: -h, --help print this help message -a, --action ACTION specify an action ACTION: on turn node(s) ON offs turn node(s) OFF (soft) offh turn node(s) OFF (hard) reboot reboots node(s) (soft) reset resets node(s) (hard) -h, --help print this help message -t, --topology TOPOLOGY a valid topology file or description (MANDATORY) -c, --config AGGREGATE use testbed AGGREGATE Some Examples: omf tell -a reset -t node1-1.grid.orbit-lab.org omf tell -a on -t system:topo:all -c grid omf tell -a reboot -t node1-1 omf tell -a offh -t [1..2,1..5] omf tell -a offh -t system:topo:all omf tell -a reset -t system:topo:imagedThe commands are: on, offh (equivalent to pulling out the power cord), offs (software shutdown), reboot (software reboot) and reset (hardware reset).
Example: turn off node1-1 on the outdoor domain
user@console.outdoor:~# omf tell -a offh -t node1-1 INFO NodeHandler: OMF Experiment Controller 5.4 (git 3fb37b9) INFO NodeHandler: Reading configuration file /etc/omf-expctl-5.4/services.yaml INFO NodeHandler: Add domain http - http://internal1.orbit-lab.org:5054/ INFO NodeHandler: Add domain http - http://repository1.orbit-lab.org:5054/ INFO NodeHandler: Slice ID: default_slice (default) INFO NodeHandler: Experiment ID: default_slice-2014-09-30t00.24.28.504-04.00 INFO NodeHandler: Message authentication is disabled INFO Experiment: load system:exp:stdlib INFO property.resetDelay: resetDelay = 230 (Fixnum) INFO property.resetTries: resetTries = 1 (Fixnum) INFO Experiment: load system:exp:eventlib INFO Experiment: load system:exp:winlib INFO Experiment: load system:exp:tell INFO property.nodes: nodes = "node1-1" (String) INFO property.command: command = "offh" (String) Talking to the CMC service, please wait ----------------------------------------------- Node: node1-1.outdoor.orbit-lab.org Reply: OK ----------------------------------------------- INFO EXPERIMENT_DONE: Event triggered. Starting the associated tasks. INFO NodeHandler: INFO NodeHandler: Shutting down experiment, please wait... INFO NodeHandler: INFO run: Experiment default_slice-2014-09-30t00.24.28.504-04.00 finished after 0:10
Execute the experiment
Primary objective is to establish the LTE connection between the UE and eNB. In order to that we need to prepare configuration files on two nodes: node9-1 and node6-20.
- ssh into nodes: Open the two ssh sessions from the console to the two nodes
 |
|
- Prepare configuration files: Make sure to have correct parameters in oai.conf file in roots home directory on the node (/root) as follows:
- Operating frequency band parameters:
- E-UTRA band
- Corresponding duplex mode (e.g. FDD/TDD),
- Downlink frequency [Hz], uplink frequency offset [Hz] (which is given in reference to the downlink frequency).
- LTE bandwidth: N_RB_DL = {6,15,25,50,75,100} corresponding to bandwidth = {1.4,3,5,10,15,20} MHz
For example:
////////// Physical parameters: component_carriers = ( { frame_type = "FDD"; eutra_band = 7; downlink_frequency = 2660000000L; uplink_frequency_offset = -120000000; N_RB_DL = 25; #N_RB_DL choice: 6,15,25,50,75,100 } );In this example, LTE operates in E-UTRA band 7 which allows the FDD mode. LTE operates at 5 MHz bandwidth around downlink and uplink center frequencies which are at 2660 MHz and 2540 MHz, respectively.
- Operating frequency band parameters:
Parameters in oai.conf can be varied as long as they are within predefined set of values which can be found in file ~/rel_0.1_26.10.2014/openair2/ENB_APP/enb_config.c or ~/trunk/openair2/ENB_APP/enb_config.c
- Make sure to have correct IP address configuration for parameters "ENB_IPV4_ADDRESS_FOR_S1_MME" and "ENB_IPV4_ADDRESS_FOR_S1U" to match node numbers. For example, for nodeX-Y, these IP address parameters become as "10.10.X.Y/16". So for our basestation node the relevant sections in the oai.conf file in /root directory on the nodes we should look like (we don't want MME support and have to adjust the ip addresses to match what we have on the control interface of the node):
////////// MME parameters: mme_ip_address = ( { ipv4 = "10.10.0.100"; ipv6 = "10:10:0::100"; active = "no"; preference = "ipv4"; } ); NETWORK_INTERFACES : { ENB_INTERFACE_NAME_FOR_S1_MME = "eth1"; ENB_IPV4_ADDRESS_FOR_S1_MME = "10.10.9.1/24"; ENB_INTERFACE_NAME_FOR_S1U = "eth1"; ENB_IPV4_ADDRESS_FOR_S1U = "10.10.9.1/24"; ENB_PORT_FOR_S1U = 2152; # Spec 2152 };
- Run the lte-softmodem: Depending on whether you want to run it with or without mme, execute lte-softmodem on corresponding nodes:
On the eNB node (node9-1) On the UE node (node6-20) w/o MME lte-softmodem-nomme -Ooai.conf -Vlte-softmodem -U -Ooai.conf -C 2660000000 -Vw MME lte-softmodem -Ooai.conf -Vlte-softmodem -U -Ooai.conf -C 2660000000 -V
If the above commands are executed with the "-d" flag and if X11 forwarding is enabled for the current ssh session, the signal tracer will pop out as shown in Figure 1 (not that this requires relatively high bandwidth).
The output on both consoles should look something like this:
[RRC][I][eNB 0] Init (UE State = RRC_IDLE)... [RRC][I][eNB 0] Checking release [RRC][I][eNB 0] Rel8 RRC [RRC][I][eNB 0] Configuration SIB2/3 [MAC][I][rrc_mac_config_req] [CONFIG][eNB 0] Configuring MAC/PHY [MAC][I][rrc_mac_config_req] [CONFIG]SIB2/3 Contents (partial) [MAC][I][rrc_mac_config_req] [CONFIG]pusch_config_common.n_SB = 1 [MAC][I][rrc_mac_config_req] [CONFIG]pusch_config_common.hoppingMode = 0 [MAC][I][rrc_mac_config_req] [CONFIG]pusch_config_common.pusch_HoppingOffset = 0 [MAC][I][rrc_mac_config_req] [CONFIG]pusch_config_common.enable64QAM = 0 [MAC][I][rrc_mac_config_req] [CONFIG]pusch_config_common.groupHoppingEnabled = 1 [MAC][I][rrc_mac_config_req] [CONFIG]pusch_config_common.groupAssignmentPUSCH = 0 [MAC][I][rrc_mac_config_req] [CONFIG]pusch_config_common.sequenceHoppingEnabled = 0 [MAC][I][rrc_mac_config_req] [CONFIG]pusch_config_common.cyclicShift = 1 [RRC][I][eNB 0] OPENAIR RRC IN.... [SCTP][I][sctp_handle_new_association_req] Setsockopt SOL_SOCKET socket bound to : eth1 [SCTP][I][sctp_handle_new_association_req] Converted ipv4 address 10.10.0.100 to network type [SCTP][I][sctp_handle_new_association_req] connectx assoc_id 1 in progress..., used 1 addresses [SCTP][I][sctp_handle_new_association_req] Inserted new descriptor for sd 56 in list, nb elements 1, assoc_id 1 [SCTP][I][sctp_eNB_flush_sockets] Found data for descriptor 56 [SCTP][I][sctp_eNB_read_from_socket] Received notification for sd 56, type 32769 [SCTP][I][sctp_eNB_read_from_socket] Client association changed: 0 [SCTP][I][sctp_get_peeraddresses] ---------------------- [SCTP][I][sctp_get_peeraddresses] Peer addresses: [SCTP][I][sctp_get_peeraddresses] - [10.10.0.100] [SCTP][I][sctp_get_peeraddresses] ---------------------- [SCTP][I][sctp_get_sockinfo] ---------------------- [SCTP][I][sctp_get_sockinfo] SCTP Status: [SCTP][I][sctp_get_sockinfo] assoc id .....: 1 [SCTP][I][sctp_get_sockinfo] state ........: 3 [SCTP][I][sctp_get_sockinfo] instrms ......: 8 [SCTP][I][sctp_get_sockinfo] outstrms .....: 64 [SCTP][I][sctp_get_sockinfo] fragmentation : 1452 [SCTP][I][sctp_get_sockinfo] pending data .: 0 [SCTP][I][sctp_get_sockinfo] unack data ...: 0 [SCTP][I][sctp_get_sockinfo] rwnd .........: 106496 [SCTP][I][sctp_get_sockinfo] peer info : [SCTP][I][sctp_get_sockinfo] state ....: 2 [SCTP][I][sctp_get_sockinfo] cwnd .....: 4380 [SCTP][I][sctp_get_sockinfo] srtt .....: 0 [SCTP][I][sctp_get_sockinfo] rto ......: 3000 [SCTP][I][sctp_get_sockinfo] mtu ......: 1500 [SCTP][I][sctp_get_sockinfo] ---------------------- [SCTP][I][sctp_eNB_read_from_socket] Comm up notified for sd 56, assigned assoc_id 1 [S1AP][I][s1ap_eNB_generate_s1_setup_request] 3584 -> 00e000 [SCTP][I][sctp_send_data] Successfully sent 53 bytes on stream 0 for assoc_id 1 [SCTP][I][sctp_eNB_flush_sockets] Found data for descriptor 56 [SCTP][I][sctp_eNB_read_from_socket] Received notification for sd 56, type 32777 [SCTP][I][sctp_eNB_flush_sockets] Found data for descriptor 56 [SCTP][I][sctp_eNB_read_from_socket] [1][56] Msg of length 27 received from port 36412, on stream 0, PPID 18 [S1AP][I][s1ap_decode_s1ap_s1setupresponseies] Decoding message S1ap_S1SetupResponseIEs (/root/trunk/targets/RT/USER/objs/openair-cn/S1AP/s1ap_decoder.c:3544) [ENB_APP][I][eNB_app_task] [eNB 0] Received S1AP_REGISTER_ENB_CNF: associated MME 1 Waiting for eNB application to be ready [HW][I][SCHED] eNB TX thread 0 started on CPU 5 [HW][I][SCHED][eNB] eNB RX thread 0 started on CPU 0 [HW][I][SCHED] eNB TX thread 1 started on CPU 0 [HW][I][SCHED][eNB] eNB RX thread 1 started on CPU 5 [HW][I][SCHED] eNB TX thread 2 started on CPU 2 [HW][I][SCHED][eNB] eNB RX thread 2 started on CPU 0 [HW][I][SCHED] eNB TX thread 3 started on CPU 5 [HW][I][SCHED][eNB] eNB RX thread 3 started on CPU 5 [HW][I][SCHED] eNB TX thread 4 started on CPU 4 [HW][I][SCHED][eNB] eNB RX thread 4 started on CPU 1 [HW][I][SCHED] eNB TX thread 5 started on CPU 4 [HW][I][SCHED][eNB] eNB RX thread 5 started on CPU 4 [HW][I][SCHED] eNB TX thread 6 started on CPU 0 [HW][I][SCHED][eNB] eNB RX thread 6 started on CPU 1 [HW][I][SCHED] eNB TX thread 7 started on CPU 1 [HW][I][SCHED][eNB] eNB RX thread 7 started on CPU 0 [HW][I][SCHED] eNB TX thread 8 started on CPU 1 [HW][I][SCHED][eNB] eNB RX thread 8 started on CPU 0 [HW][I][SCHED] eNB TX thread 9 started on CPU 0 [HW][I][SCHED][eNB] eNB RX thread 9 started on CPU 1 Creating main eNB_thread [SCHED][eNB] Started eNB main thread on CPU 4 eNB_thread: mlockall in ... eNB_thread: mlockall out ... waiting for sync (eNB_thread) TYPE <CTRL-C> TO TERMINATE Entering ITTI signals handler
The command line parameters of lte-softmodem
Relevant (i.e. for USRP command line parameters for the lte-softmodem command are:
- -O file: eNB configuration file (this is the preferred way to pass basic parameters and there are several examples in $OPENAIR_TARGETS/PROJECTS/GENERIC-LTE_EPC/CONF/
- -g LEVEL: set the level of debug for the log generation (-g7 is quite high and useful to trace bugs in the procedures/protocols, -g9 even dumps packets at all levels of the protocol stack)
- -d: enables xforms signal tracer
- -U: start as UE (default: eNB)
- -C freq: set carrier frequency to f0 for all chains (extension to independent frequencies trivial)
- -V: enables the VCD debugging tool (this is a temporal event tracer, which is useful for real-time debugging using GTKWave)
- -K file: ITTI logfile. ITTI is an intertask tracing utility which helps debugging with an EPC. It can traces all exchanges between RRC↔S1AP, RRC↔PDCP, PDCP↔S1
- -S: do not exit for the missing slots, instead increment the counter.
- —debug-ue-prach: only send prach but do not connect
- —no-L2-connect: only runs rx, does not send prach
More details on running lte-softmodem are available on OpenAirInterface real-time LTE softmodem page.
Note:
See TracWiki
for help on using the wiki.
