close Warning: Can't synchronize with repository "(default)" (/common/SVN/wimax does not appear to be a Subversion repository.). Look in the Trac log for more information.

Changes between Version 11 and Version 12 of Old/WiMAX/04/01


Ignore:
Timestamp:
Nov 30, 2010, 4:35:14 PM (10 years ago)
Author:
hmussman
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Old/WiMAX/04/01

    v11 v12  
    1 == Steps for setting up the WiMAX BTS on ORBIT ==
     1= Case 1 or 2 Installation =
     2
     3
     4== WiMAX OID and IP Address Assignment ==
     5
     6
     7|| Campus || OID || IP Range ||
     8|| WINLAB || 44:51:DB:00:00:XX || 10.3.0.XX ||
     9|| NECLabs || 44:51:DB:00:01:XX || 10.3.1.XX ||
     10|| BBN || 44:51:DB:00:02:XX || 10.3.2.XX ||
     11|| Stanford || 44:51:DB:00:03:XX || 10.3.3.XX ||
     12|| Poly || 44:51:DB:00:04:XX || 10.3.4.XX ||
     13|| UMass || 44:51:DB:00:05:XX || 10.3.5.XX ||
     14|| Columbia || 44:51:DB:00:06:XX || 10.3.6.XX ||
     15|| UColorado || 44:51:DB:00:07:XX || 10.3.7.XX ||
     16|| UWisconsin || 44:51:DB:00:08:XX || 10.3.8.XX ||
     17|| UCLA || 44:51:DB:00:09:XX || 10.3.9.XX ||
     18
     19Each campus can have up to 127 basestations (each BS needs two addresses) and/or multiple ASN gateways. The basestations are assigned OIDs and IPs starting from 1 and counting up while ASN gateway machines are assigned IP addresses that are assigned starting from 254 and counting down. For example, first basestation in WINLAB gets IP address on primary controller of 10.3.0.1 and the IP address for the networking card of 10.3.0.2 while the gateway machine gets 10.3.0.254
     20
     21== Setting up the NEC IDU on ORBIT ==
    222
    323Please note: Do not restart BTS until all changes are complete. If you do happen to restart, you will have to use the serial interface to connect to the BTS.
     
    7696
    7797This [http://www.kloth.net/services/iplocate.php site] converts dot quad to hex.
     98
     99
     100==  IDU Installation ==
     101
     102
     103==  Base Station Server Installation ==
     104
     105
     106=== Prerequisites ===
     107
     108 * Expected OS: Ubuntu 9.04
     109   {{{
     110   lsb_release -a
     111   No LSB modules are available.
     112   Distributor ID: Ubuntu
     113   Description:    Ubuntu 9.04
     114   Release:        9.04
     115   Codename:       jaunty
     116   }}}   
     117 * It is expected that there be 3 wired Ethernet interfaces named: eth0, eth1, eth2. You may need to edit '''/etc/udev/rules.d/70-persistent-net.rules''' to make the names
     118   reflect the correct physical ports. The '''/etc/network/interfaces''' file should look similar to this:
     119   {{{
     120   # This file describes the network interfaces available on your system
     121   # and how to activate them. For more information, see interfaces(5).
     122   
     123   # The loopback network interface
     124   auto lo
     125   iface lo inet loopback
     126
     127   # This interface connect to the Base Station
     128
     129   auto eth1
     130   iface eth1 inet static
     131   address 192.168.1.50
     132   network 192.168.1.0
     133   netmask 255.255.255.0
     134   broadcast 192.168.1.255
     135
     136   #This is the gateway interface, it should get a routeable address from DHCP
     137   
     138   auto eth2
     139   iface eth2 inet dhcp
     140
     141   #Reserved for future USE
     142
     143   auto eth0
     144   iface eth0 inet static
     145   address 10.41.0.3
     146   network 10.41.0.0
     147   netmask 255.255.0.0
     148   broadcast 10.41.255.255
     149   }}}
     150
     151=== Install Required Packages ===
     152
     153 1. Configure apt/sources to include mytestbed.net and orbit-lab.org. Edit the '''/etc/apt/sources.list''' and add the following lines:
     154    {{{
     155    deb http://pkg.mytestbed.net/ubuntu karmic/
     156    deb http://packages.orbit-lab.org/ubuntu jaunty main
     157    }}}
     158 1. Update information based on the changed sources.list.
     159    {{{
     160     sudo apt-get update
     161    }}}
     162 1. Now install the ASN-GW software
     163    {{{
     164    sudo apt-get install asn-gw0.9.0 click1.6.0 omf-wimaxrf-aggmgr-5.2
     165    }}}
     166    This will install 333MB or so worth of packages. You will need to confirm some of the packages from our repository.
     167
     168== Configuration of ASN-GE Controller and NEC IDU ==
     169
     170Configuration of software both for the ASN-GW and the WiMAX BTS is done through a single yaml configuration file on the ASN.
     171
     172To enable the features we will need to copy the '''wimaxrf.yaml''' from '''/etc/omf-aggmgr-5.2/available''' to '''/etc/omf-aggmgr-5.2/enabled/'''.
     173
     174Edit this file change settings (if needed)
     175{{{
     176# NOTE: use only 'spaces' to indent !
     177# ('tab' indents are not supported by the ruby yaml parser used to read this file)
     178#
     179# This is the Config file for the WiMAXRF GridService
     180#
     181---
     182wimaxrf:
     183
     184  asngw:
     185   if: eth1
     186   ip: 192.168.1.50
     187   port: 2231
     188   id: ASNGW000
     189   tecnh: 3
     190   dsc: IP-Config-Mgmt
     191
     192  click:
     193    def_gw: 10.41.0.1
     194    net_mask: 255.255.0.0
     195    def_ip: 10.41.0.254
     196
     197  bs:
     198   ip: 192.168.1.10
     199   mask: 255.255.255.0
     200   bsid: 00:00:04:00:00:01
     201   frequency: 2590000                           
     202}}}
     203
     204Making changes in this file should propagate changes to the ASN software and the BS (IDU) software.
     205
     206== [Optional] Manual Configuration Of SAMrb ==
     207
     208Note these instructions need to be followed if you are using just the SAMrb instead of the full omf-wimaxrf-aggmgr-5.2 webservice.
     209
     210Once you untar and enter in the SAMrb directory you can edit the file SimpleAuthManager.rb.
     211
     212In this file please change the following to reflect your network settings:
     2131. The $ips hash table should be updated to include your client mac to IP mapping.
     2142. The $def_gw = "10.41.0.1"   and $net_mask = "255.255.0.0" settings should be used to reflect the CSN side settings.
     215
     216
     217
     218== Testing ==
     219
     220=== Simple Checks ===
     221
     222A few simple checks to make sure things are working:
     223 1. You should be able to ping the Base Station, it was assigned the fixed IP 192.168.1.10.
     224 1. Some log files should start filling up in '''/var/log''':
     225  1. asnctrl.log
     226  1. epctrl.log
     227 1. There should also be a green light on the IDU after a software power cycle of the IDU. The software power cycle can be preformed by the following commands:
     228    {{{
     229    /etc/init.d/asn-gw stop
     230    /etc/init.d/asn-gw start
     231    }}}
     232 1. There should be 3 running processes:
     233    {{{
     234    root      3128     1  0 19:10 ?        00:00:00 trapctrl
     235    root      3137     1  0 19:10 ?        00:00:02 asnctrl
     236    root      3227     1  0 19:10 ?        00:00:02 epctrl
     237    }}}
     238
     239
     240=== Prerequisites ===
     241
     2421. Confirm that all hardware and software has been properly installed.
     243
     244
     245=== Hardware connectivity check ===
     246
     247Login through the console on the ASN-GW and test the following.
     248
     2491. Is the BTS is reachable from the ASN-GW. with the default IP setting
     250    - ping the BTS interface
     251    - measure the round trip times
     252
     2532. Power cycle the BTS through the use of stop and start scripts.
     254   - Perform a hard reset if required (if updated parameter values are not reflected).
     255
     2563. Ping the outside interface and see if the DMZ gateway is reachable from the ASN-GW
     257
     258After successful completion we know that the ASN is able to send traffic both downlink to the IDU
     259and outbound towards the internet.
     260
     261=== Test the RF Transmission ===
     262
     2631. Scan on the client and check if the basestation's signal is seen using the procedure described below. If we are able to connect step 2 can be ignored. Else try step 2.
     264
     265Configure driver at the client to ensure all required parameters are configured correctly.
     266   - Change the /etc/asnctrl_service_class.conf to include client and service class information.
     267   - possibly include SSID to match with the BTS
     268   - Check center frequency to match with the BTS
     269   - Enable (locks) if any
     270   - Disable wifi if operating on a dual mode card (since quite a few times they work in a mutually exclusive mode)
     271   - Enable a static IP setting at the client to allow for baseline IP connectivity
     272
     273
     2742. If possible sweep the spectrum through an analyzer to determine proper transmission at the center frequency.
     275   - Vary transmit power at the BTS using wiset calls on the BTS or through the web interface and then measure the corresponding changes on the analyzer.
     276