|Version 87 (modified by 7 years ago) ( diff ),|
0. Getting Started
Before you can complete any of the tutorials, you will need to have followed these prerequisites:
Make a reservation
Login into reserved domain
Login into reserved domain
During your approved time slot, you will be able to ssh into the console of the respective domain. A console is a dedicated machine that allows access to all resources in that domain.
For example, to access the sandbox1:
yourhost>ssh email@example.com Using username "username". Authenticating with public key "xxxxxxxxx" Welcome to Ubuntu 12.04.1 LTS (GNU/Linux 3.2.0-36-generic x86_64) * Documentation: https://help.ubuntu.com/ System information as of Mon Jan 28 20:25:50 EST 2013 System load: 0.0 Processes: 93 Usage of /: 2.7% of 69.43GB Users logged in: 0 Memory usage: 6% IP address for eth0: 10.50.18.10 Swap usage: 0% IP address for eth1: 10.18.0.10 Graph this data and manage this system at https://landscape.canonical.com/ 9 packages can be updated. 0 updates are security updates. |-----------------------------------------------------------------| | *** For authorized use only *** | | This system is for the use of authorized users only. All users | | are expected to comply with the "Acceptable Use Policy" availa- | | ble at http://www.orbit-lab.org/AUP.html | | Individuals using this computer system, are subject to having | | all of their activities on this system monitored and recorded | | by system personnel. | | | | Anyone using this system expressly consents to such monitoring | | and is advised that if such monitoring reveals possible | | evidence of criminal activity, system personnel may provide the | | evidence of such monitoring to law enforcement officials. | | | | Email question, comments or problems to firstname.lastname@example.org | |-----------------------------------------------------------------| email@example.com:~$
Check the status
This omf command is used to display the power status of the node/domain.
Usage: omf help stat
firstname.lastname@example.org:omf-5.4 help 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 grid
Individual 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
email@example.com:~# omf stat 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
1. Basic Tutorial
1.1 Tutorials on controlling the testbed nodes
- How to load (install) a disk image on a set of nodes
- How to save an existing disk image from one node
- How to switch On/Off a set of nodes
1.2 Introductory Experiments
This section gives an introduction to the ORBIT testbed, its capabilities and its operations. It also presents the basic knowledge required to write and execute experiments for the testbed.
If you are new to the ORBIT testbeds, reading and running the tutorial in this section should help you getting started.
The first part of this tutorial briefly describes the ORBIT Testbed, its system architecture and its hardware and software components. The second part presents and describes a simple "Hello World" experiment with one sender and one receiver. The third and concluding part covers the collection an interpretation of measurements and results of an experiments on the ORBIT testbed.
- Brief tour of the Testbed
- First Experiment: the "Hello World" Example
- How measurements are collected
- How to post-process these measurements
2. Additional refrences
After completing the above basic tutorial, you should have a better understanding of using the ORBIT testbed to experiment your ideas, algorithms, or protocols. The tutorials in this second section further explore the various ORBIT functions that will help you write and execute more advanced experiments.
Finally, some more detailed information and references can be found on the Documentation page
More documentation on the GNURadio can be found here
The WiMAX resource center can be found at http://wimax.orbit-lab.org.
The OMF project has further documentation at http://mytestbed.net/projects/omf.
If you are new to the ORBIT testbeds, these tutorials will give you an introduction to the ORBIT testbed, its capabilities and its operations.
- Brief tour of the Testbed - the tutorial that briefly describes the ORBIT Testbed, its system architecture and its hardware and software components.
- Basic testbed operations and node management - overview of basic OMF commands and usage examples.
- First Experiment: the "Hello World" Example - a simple wireless "Hello World" with one sender and one receiver.
- How to post-process the measurements
Bluetooth and ZigBee Tutorials
WiMAX and LTE Tutorials
Wide area network experimentation in ORBIT currently supports two types of wireless technologies: WiMAX and LTE. Both technologies, in addition to devices deployed in various domains of the testbed, are also deployed on two Rutgers University campuses as part of GENI 4G deployment addressing the two key research issues:
- providing campus-wide GENI wireless coverage for opt-in users;
- offering programmable wireless networking capabilities
While initial focus was on developing and deploying wide-area wireless experimentation services with WiMAX technology, subsequent efforts were concentrated on introducing LTE. At the core of both types of deployment are technology kits typically consisting of a commercial basestation and PC-based controller running custom software that manages the basestation and performs layer 2 and layer 3 processing of client packets. More details on the 4G deployments can be found at GENI 4G pages. The most recent addition to the LTE experimentation capabilities are fully software-based (SDR) open (and closed) source implementations.
A wide variety of wireless experiments and tutorials are available for the GENI community. To try them out, please follow these Steps to access Wireless resources via GENI
- SDR Tutorials
The ORBIT testbed is home to a collection of software defined radio (SDR) device platforms including WARP, rtl-sdr, Ettus Research ( USRP (1), USRP N210, USRP X310, USRP B210), RTL-SDR, Nutaq ZeptoSDR and PicoSDR, and Avnet Zynq SDR. While most of the devices are in the grid, number of sandboxes are also equipped with SDR platforms and are suggested target for SDR learning and running tutorials (especially given that they are usually less busy than the main grid).
Most of the available SDR tutorials are using one of the three software platforms:
- Stand-alone C/C++ programs: USRP2 configration and OML data collection with wiserd, Observing the spectrum and transmitting wideband signals using USRP X310
- GNURadio: As the "workhorse" of the SDR community, GNURadio . The available tutorials that are mostly scripted with [OEDL (version 5.4)] are: Getting Started with GNURadio, working with USRP2 on sandbox3, data transfer using basic modulation or OFDM, MAC protocols adaption, creating custom GNURadio blocks for Nutaq platform and using a bot emulating primary user transmission
- Iris: The OFDM transport and ALOHA MAC tutorials
The MobilityFirst project was started in 2010 with funding from the National Science Foundation's Future Internet Architecture (FIA) program as one of the four clean-slate architectures. The major design goals of this new architecture are:
- mobility as the norm (with dynamic host and network mobility at scale)
- robustness with respect to intrinsic properties of wireless medium
- trustworthiness in the form of enhanced security and privacy (for both mobile networks and wired infrastructure)
- usability features such as support for context-aware pervasive mobile services, evolvable network services, manageability and economic viability.
The design is also informed by technology factors such as radio spectrum scarcity, wired bandwidth abundance, continuing Moore’s law improvements to computing, and energy constraints in mobile and sensor devices.