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

Timestamp:

Nov 30, 2010, 4:35:14 PM (13 years ago)

Author:

hmussman

Comment:

—

Old/WiMAX/04/01

@@ -1 @@
-== Steps for setting up the WiMAX BTS on ORBIT ==
+= Case 1 or 2 Installation =
+
+
+== WiMAX OID and IP Address Assignment ==
+
+
+|| Campus || OID || IP Range ||
+|| WINLAB || 44:51:DB:00:00:XX || 10.3.0.XX ||
+|| NECLabs || 44:51:DB:00:01:XX || 10.3.1.XX ||
+|| BBN || 44:51:DB:00:02:XX || 10.3.2.XX ||
+|| Stanford || 44:51:DB:00:03:XX || 10.3.3.XX ||
+|| Poly || 44:51:DB:00:04:XX || 10.3.4.XX ||
+|| UMass || 44:51:DB:00:05:XX || 10.3.5.XX ||
+|| Columbia || 44:51:DB:00:06:XX || 10.3.6.XX || 
+|| UColorado || 44:51:DB:00:07:XX || 10.3.7.XX || 
+|| UWisconsin || 44:51:DB:00:08:XX || 10.3.8.XX || 
+|| UCLA || 44:51:DB:00:09:XX || 10.3.9.XX || 
+
+Each 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 
+
+== Setting up the NEC IDU on ORBIT ==
 
 Please 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.
@@ -76 +96 @@
 
 This [http://www.kloth.net/services/iplocate.php site] converts dot quad to hex. 
+
+
+==  IDU Installation ==
+
+
+==  Base Station Server Installation ==
+
+
+=== Prerequisites ===
+
+ * Expected OS: Ubuntu 9.04
+   {{{
+   lsb_release -a
+   No LSB modules are available.
+   Distributor ID: Ubuntu
+   Description:    Ubuntu 9.04
+   Release:        9.04
+   Codename:       jaunty
+   }}}   
+ * 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 
+   reflect the correct physical ports. The '''/etc/network/interfaces''' file should look similar to this:
+   {{{
+   # This file describes the network interfaces available on your system
+   # and how to activate them. For more information, see interfaces(5).
+   
+   # The loopback network interface
+   auto lo
+   iface lo inet loopback
+
+   # This interface connect to the Base Station
+
+   auto eth1
+   iface eth1 inet static
+   address 192.168.1.50
+   network 192.168.1.0
+   netmask 255.255.255.0
+   broadcast 192.168.1.255
+
+   #This is the gateway interface, it should get a routeable address from DHCP
+   
+   auto eth2
+   iface eth2 inet dhcp
+
+   #Reserved for future USE
+
+   auto eth0
+   iface eth0 inet static
+   address 10.41.0.3
+   network 10.41.0.0
+   netmask 255.255.0.0
+   broadcast 10.41.255.255
+   }}}
+
+=== Install Required Packages ===
+
+ 1. Configure apt/sources to include mytestbed.net and orbit-lab.org. Edit the '''/etc/apt/sources.list''' and add the following lines:
+    {{{
+    deb http://pkg.mytestbed.net/ubuntu karmic/
+    deb http://packages.orbit-lab.org/ubuntu jaunty main
+    }}}
+ 1. Update information based on the changed sources.list.
+    {{{
+     sudo apt-get update
+    }}}
+ 1. Now install the ASN-GW software 
+    {{{
+    sudo apt-get install asn-gw0.9.0 click1.6.0 omf-wimaxrf-aggmgr-5.2
+    }}}
+    This will install 333MB or so worth of packages. You will need to confirm some of the packages from our repository. 
+
+== Configuration of ASN-GE Controller and NEC IDU ==
+
+Configuration of software both for the ASN-GW and the WiMAX BTS is done through a single yaml configuration file on the ASN.
+
+To 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/'''.
+
+Edit this file change settings (if needed)
+{{{
+# NOTE: use only 'spaces' to indent !
+# ('tab' indents are not supported by the ruby yaml parser used to read this file)
+#
+# This is the Config file for the WiMAXRF GridService
+#
+---
+wimaxrf:
+
+  asngw:
+   if: eth1
+   ip: 192.168.1.50
+   port: 2231
+   id: ASNGW000
+   tecnh: 3
+   dsc: IP-Config-Mgmt
+
+  click:
+    def_gw: 10.41.0.1
+    net_mask: 255.255.0.0
+    def_ip: 10.41.0.254
+
+  bs:
+   ip: 192.168.1.10
+   mask: 255.255.255.0
+   bsid: 00:00:04:00:00:01
+   frequency: 2590000                           
+}}}
+
+Making changes in this file should propagate changes to the ASN software and the BS (IDU) software.
+
+== [Optional] Manual Configuration Of SAMrb ==
+
+Note these instructions need to be followed if you are using just the SAMrb instead of the full omf-wimaxrf-aggmgr-5.2 webservice.
+
+Once you untar and enter in the SAMrb directory you can edit the file SimpleAuthManager.rb.
+
+In this file please change the following to reflect your network settings:
+1. The $ips hash table should be updated to include your client mac to IP mapping.
+2. The $def_gw = "10.41.0.1"   and $net_mask = "255.255.0.0" settings should be used to reflect the CSN side settings.
+
+
+
+== Testing ==
+
+=== Simple Checks ===
+
+A few simple checks to make sure things are working:
+ 1. You should be able to ping the Base Station, it was assigned the fixed IP 192.168.1.10.
+ 1. Some log files should start filling up in '''/var/log''':
+  1. asnctrl.log
+  1. epctrl.log
+ 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:
+    {{{
+    /etc/init.d/asn-gw stop
+    /etc/init.d/asn-gw start
+    }}}
+ 1. There should be 3 running processes: 
+    {{{
+    root      3128     1  0 19:10 ?        00:00:00 trapctrl
+    root      3137     1  0 19:10 ?        00:00:02 asnctrl
+    root      3227     1  0 19:10 ?        00:00:02 epctrl
+    }}}
+
+
+=== Prerequisites ===
+
+1. Confirm that all hardware and software has been properly installed.
+
+
+=== Hardware connectivity check ===
+
+Login through the console on the ASN-GW and test the following.
+
+1. Is the BTS is reachable from the ASN-GW. with the default IP setting
+    - ping the BTS interface
+    - measure the round trip times
+
+2. Power cycle the BTS through the use of stop and start scripts.
+   - Perform a hard reset if required (if updated parameter values are not reflected).
+
+3. Ping the outside interface and see if the DMZ gateway is reachable from the ASN-GW
+
+After successful completion we know that the ASN is able to send traffic both downlink to the IDU
+and outbound towards the internet.
+
+=== Test the RF Transmission ===
+
+1. 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.
+
+Configure driver at the client to ensure all required parameters are configured correctly.
+   - Change the /etc/asnctrl_service_class.conf to include client and service class information.
+   - possibly include SSID to match with the BTS
+   - Check center frequency to match with the BTS
+   - Enable (locks) if any
+   - Disable wifi if operating on a dual mode card (since quite a few times they work in a mutually exclusive mode)
+   - Enable a static IP setting at the client to allow for baseline IP connectivity
+
+
+2. If possible sweep the spectrum through an analyzer to determine proper transmission at the center frequency.
+   - 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.
+