Changes between Version 20 and Version 21 of dSite


Ignore:
Timestamp:
08/17/15 15:20:48 (2 years ago)
Author:
seskar
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • dSite

    v20 v21  
    33[[TOC(WikiStart, aaOperations*, aWiMAX*, cLTE*, dSite*, depth=2)]] 
    44 
    5 Depending on the number of site basestations , standard GENI 4G wireless deployment typically belongs to one of the two configurations: 1) '''single-BS site''' with OMF services on the (yellow) console node as shown in Figure 1, and  2) '''multi-BS site''' with dedicated BS controller(s) as shown in Figure 2 . The [wiki:./hardwaresetuplink hardware setup] establishes the wiring layout and switching requirements for nodes and the console. The nodes can be easily distinguished from the console by the number of Ethernet ports they have. Consoles require 4 ports while nodes have only 3. The console node acts as an authenticated gateway that only allows registered authenticated users to login to client node resources. The different networks are: 
    6  
    7  * CM network - admin management of nodes, power cycle them remotely 
    8  * Control - experimenters issue commands over this network 
    9  * Data - actual interface that allows client nodes and the WiMAX BS to send data to nodes and/or resources in GENI 
    10  
     5Depending on the number of site basestations , standard GENI 4G wireless deployment typically belongs to one of the two configurations: 1) '''single-BS site''' with OMF services on the (yellow) console node as shown in Figure 1, and  2) '''multi-BS site''' with dedicated BS controller(s) as shown in Figure 2. The OMF part of the setup consists of a console and 3 (yellow) nodes. The nodes can be easily distinguished from the console by the number of Ethernet ports they have. Consoles require 4 ports while nodes have only 3. The console node acts as an authenticated gateway, that only allows registered authenticated users to login to client node resources. Each site might also require temporary setup server (that is used for initial basestation configuration); optionally, sites can chose to use global (GENI wide) installation/configuration server (requires GENI Control subnet). 
    116 
    127 === Single BS Site === 
     8 
    139{{{#!imagebox 
    14 [[Image(GENI Setup - simple.jpg, width=600)]] 
    15 Typical Single Basestation Setup 
     10[[Image(GENI Setup - simple.jpg, width=800)]] 
     11 
     12Figure 1: Typical Single Basestation Setup 
    1613}}} 
    17 .  
    1814 
    19 In the figure, the data network can either reach the public internet via the Console gateway or resources in GENI via Layer 2 VLANs. 
     15In this configuration all of the OMF/BS services are running on the console which also has access to all subnets. 
    2016 
    21 Possible Network switch configurations for different networks 
     17 === Multiple Basestations Site === 
     18{{{#!imagebox 
     19[[Image(GENI Setup - big.jpg, width=800)]] 
    2220 
    23   || [[Image(SWa.jpg, width=200)]] || [[Image(SWb.jpg, width=200)]] || [[Image(SWc.jpg, width=200)]] || 
     21Figure 2: Typical Multi-Basestation Setup 
     22}}} 
    2423 
    25 The 3 networks can be setup in different ways. The three recommended ways for GENI sites are as follows: 
     24In this configuration due to performance requirements of multi-BS management. dedicated server(s) are used for basestation management. Typically, other OMF services are running on the console (sites with large number on nodes can decide to further split OMF services among multiple servers). Typically, only BS controller(s) have access to global VLANs. 
    2625 
    27  * Single managed switch with different networks setup for all nodes via trunk VLANs for the entire campus path. 
    28  * Single unmanaged switch per network setup via access VLANs for the entire campus path. 
    29  * Single managed switch per node with all networks trunked on a single upstream campus switch 
     26  
     27 === Networking Configurations === 
    3028 
    31  === Complex Site === 
     29The different networks for the GENI Wireless site are: 
    3230 
    33 [[Image(GENI Setup - big.jpg, width=600)]].  
     31 * '''Local CM''' - admin management of nodes, power cycle them remotely, access console etc. 
     32 * '''Local Control''' - experimenters issue commands over this network 
     33 * '''Local Data''' - actual interface that allows client nodes unrestricted communications and is under full control of the experimenter. It is used by both fixed Ethernet interfaces (eth0) on the nodes as well as by the wireless clients on the nodes (through the basestation). 
     34 * '''GENI Wireless Data''' - dedicated GENI-wide subnet that, through multi-point AL2S, connects all wireless sites into single L2 broadcast domain end enables large scale experimentation.  
     35 * '''GENI Wireless Control''' - another multi-point AL2S subnet that is used for global BS management/control (netspan, asn-gw and ePC). 
     36 
     37{{{#!imagebox 
     38  ||  [[Image(SWa.jpg, width=200)]]  ||  [[Image(SWc.jpg, width=200)]]  ||  [[Image(SWb.jpg, width=200)]]  || 
     39 
     40Figure 3: Possible (Local) Network Switch Configurations 
     41}}} 
     42The 3 OMF related networks can be setup in various ways. The three recommended ways for GENI sites are as follows (Figure 3): 
     43 
     44 * ''Single managed switch per site'' with different networks setup for all nodes via trunk VLANs for the entire local/campus path. This is the recommended configuration that implies three wires to each of the nodes. 
     45 * ''Single (low port count) managed switch per node'' with all networks ''trunk-ed'' to a upstream campus switch (this configuration is appropriate if there are issues with running multiple wires to the node location but requires uniformed VLAN assignment across campus network). 
     46 * ''Single unmanaged switch per subnet'' setup: each of the 3 local paths has a separate switch (please note that this configuration does not support connections for the 2 global GENI paths to the console node and are here only for reference). 
     47 
     48In all configurations, external access is assumed to be through Console node. The three local subnets can either reach the public internet via the Console gateway or directly (in which case fire-walling the subnets is strongly recommended); resources in GENI are accessible to the console or BS controller server directly via Layer 2 VLANs. 
    3449 
    3550 == Installation == 
    36 The site software installation process has three major phases. All of the software setup is done on the console since the nodes have their operating system pushed onto them via the OMF imaging infrastructure that we are going to build on the console. 
     51The site software installation process has three major phases. All of the software setup is done on the console since the nodes have their operating system pushed onto them via the OMF imaging infrastructure (that we are going to build on the console). To setup the console software, we have to: 1.) [wiki:./b0OS install a base operating system] (based on Ubuntu 12.04/14.04), 2.)[wiki:./c0OMF install the omf services] and 3.) configure the installed [wiki:./e0LDAP OS srevices] and [wiki:./k0Inv OMF services] and test the deployment. The services that need to be configured are: DNS/DHCP, LDAP, xmpp and a range of OMF Aggregate Managers: Inventory, Account Management, CMC, etc. Last step in the installation process is to [wiki:./mConnectivity connect the site to GENI backbone] and [wiki:./oGeniPortal enable GENI portal based access]. 
    3752 
    38 To setup the console software, we have to [wiki:./b0OS install a base operating system] (based on Ubuntu 12.04), [wiki:./c0OMF install and configure the omf services] and test the deployment. The services that need to be configured are: DNS/DHCP, LDAP, xmpp and a range of OMF Aggregate Managers: Inventory, Account Management, CMC, etc. 
    39  
    40 Once these services are properly function, the GENI site is ready to be used for experiments.