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 8 and Version 9 of Old/WiMAX/05/01


Ignore:
Timestamp:
Dec 9, 2010, 6:48:32 PM (13 years ago)
Author:
hmussman
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Old/WiMAX/05/01

    v8 v9  
    1 = 7.  Case 2:  Software Installation and Configuration =
    2 
    3 
    4 == WiMAX OID and IP Address Assignment ==
     1[[PageOutline]]
     2
     3= 6.  Case 2:  Software Installation, Configuration and Operation =
     4
     5
     6== 6.1  WiMAX OID and IP Address Assignment ==
    57
    68
    … …  
    1921Each 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
    2022
    21 
    22 ==  Base Station Server Installation ==
    23 
    24 
    25 === Prerequisites ===
    26 
    27  * Expected OS: Ubuntu 9.04
     23Issue:  Should all use BBN OID, since it is the only one offically regsitered?  Also, that all MSs would use same OID?
     24
     25
     26
     27== 6.2  Key Configuration Parameters ==
     28
     29These are the key parameters, that are gathered and then held in the yaml configuration file
     30
     31{{{
     32# NOTE: use only 'spaces' to indent !
     33# ('tab' indents are not supported by the ruby yaml parser used to read this file)
     34#
     35# This is the Config file for the WiMAXRF GridService
     36#
     37---
     38wimaxrf:
     39
     40  asngw:
     41   if: eth1
     42   ip: 192.168.1.50
     43   port: 2231
     44   id: ASNGW000
     45   tecnh: 3
     46   dsc: IP-Config-Mgmt
     47
     48  click:
     49    def_gw: 10.41.0.1
     50    net_mask: 255.255.0.0
     51    def_ip: 10.41.0.254
     52
     53  bs:
     54   ip: 192.168.1.10
     55   mask: 255.255.255.0
     56   bsid: 00:00:04:00:00:01
     57   frequency: 2590000                           
     58}}}
     59
     60
     61==  6.3 Base Station Server Installation ==
     62
     63
     64=== 6.3.1 Expected OS: Ubuntu 9.04 ===
     65
    2866   {{{
    2967   lsb_release -a
    … …  
    3472   Codename:       jaunty
    3573   }}}   
    36  * 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
     74
     75=== 6.3.2  Setup Ethernet Interfaces ===
     76
     77It 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
    3778   reflect the correct physical ports. The '''/etc/network/interfaces''' file should look similar to this:
    3879   {{{
    … …  
    68109   }}}
    69110
    70 === Install Required Packages ===
     111=== 6.3.3 Install Required Packages ===
    71112
    72113 1. Configure apt/sources to include mytestbed.net and orbit-lab.org. Edit the '''/etc/apt/sources.list''' and add the following lines:
    … …  
    83124    sudo apt-get install asn-gw0.9.0 click1.6.0 omf-wimaxrf-aggmgr-5.2
    84125    }}}
     126 1. Install SAM.rb from repository into home directory
     127
    85128    This will install 333MB or so worth of packages. You will need to confirm some of the packages from our repository.
    86129
    87 
    88 == Setting up the NEC BTS ==
     130[wiki:/Software/Create Create Debian Package][[BR]]
     131[wiki:/Software/Configuration Create Package Site][[BR]]
     132
     133
     134== 6.4  Setup NEC BTS ==
    89135
    90136Please 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.
    91137
    92 === Step1 Configuring the IP ===
     138=== 6.4.1:  Step 1 Configuring the IP ===
    93139
    94140We'll need to adjust the ip's of both interfaces. They're managed via two independent files which exists on two different machines/ip combos.
    … …  
    103149     #MAC0
    104150     export INTERFACE_0=eth0
    105      export IPADDR_0=10.3.X.1
     151     export IPADDR_0=10.3.Y.1
    106152     export NETMASK_0=255.255.0.0
    107153     export BROADCAST_0=10.3.255.255
    108      export GATEWAY_0=10.3.X.1
     154     export GATEWAY_0=10.3.YX.1
    109155     export NAMESERVER_0=8.8.8.8
    110156     }}}
    … …  
    115161 1. The "Network" Machine
    116162  1. Telnet to the N/W card at 192.168.1.42/24. User root as the username, you will not be asked for a password.
    117   1. Edit the /etc/network/interfaces eth1 entry to organisations Address Structure. It should be of the form 10.3.X.2, for the first BTS. The entry should look
     163  1. Edit the /etc/network/interfaces eth1 entry to organisations Address Structure. It should be of the form 10.3.Y.2, for the first BTS. The entry should look
    118164     similar to:
    119165     {{{
    120166     auto eth1
    121167     iface eth1 inet static
    122      address 10.3.X.2
     168     address 10.3.Y.2
    123169     network 10.3.0.0
    124170     netmask 255.255.0.0
    125171     broadcast 10.3.255.255
    126      gateway 10.3.X.1
     172     gateway 10.3.Y.1
    127173     }}}
    128174 1. Finally you'll need to configure your own interface to be in the same subnet as the BS Ip's. For the first BS it should be of the form 10.3.X.254.
    129175
    130 === Step 2a Configure The BS software ===
    131   1. ssh to the new IP of the DSP machine. ssh !root@10.3.x.1
     176=== 6.4.2  Step 2  Configure the BTS software ===
     177
     178  1. ssh to the new IP of the DSP machine.
     179
     180      {{{
     181      ssh !root@10.3.Y.1
     182      }}}
     183
    132184  1. Use wiset commands below to correct configuration on the BTS:
    133185   1. Enter these '''Verbatim'''
    … …  
    139191      wiset asngw_ep_port 0x08B7
    140192      wiset bs_rx_port 0x08B7
    141       wiset frequency  2551500
     193      wiset frequency  2551500    or ??
    142194      wiset bs_tx_power 40
    143195      wiset bw_mode 0
    … …  
    166218
    167219
    168 === Step 2b  BTS Configuration ===
    169 
    170 Cat the following code to a shell script and execute after sshing into the BTS at the default ip: 192.168.1.10.
    171 If ssh does not work, try with a serial console.
    172 
    173 {{{
    174 /usr/sbin/wimax/cmd_app 3 authgw_id 0x41534E4757303030
    175 /usr/sbin/wimax/cmd_app 3 authgw_port 0x08B7
    176 /usr/sbin/wimax/cmd_app 3 asngw_id 0x41534E4757303030
    177 /usr/sbin/wimax/cmd_app 3 asngw_dp_port  0x08B7
    178 /usr/sbin/wimax/cmd_app 3 asngw_ep_port 0x08B7
    179 /usr/sbin/wimax/cmd_app 3 bs_rx_port 0x08B7
    180 /usr/sbin/wimax/cmd_app 3 bsid 0x000004000000
    181 /usr/sbin/wimax/cmd_app 3 frequency  2551500
    182 /usr/sbin/wimax/cmd_app 3 bs_tx_power 40
    183 /usr/sbin/wimax/cmd_app 3 bw_mode 0
    184 /usr/sbin/wimax/cmd_app 3 dlul_ratio 2
    185 /usr/sbin/wimax/cmd_app 3 ttg 296
    186 /usr/sbin/wimax/cmd_app 3 rtg 168
    187 /usr/sbin/wimax/cmd_app 3 framesync_mode 2
    188 /usr/sbin/wimax/cmd_app 3 antenna_gain 0
    189 /usr/sbin/wimax/cmd_app 3 authgw_ip 0xC0A80132
    190 /usr/sbin/wimax/cmd_app 3 asngw_dp_ip 0xC0A80132
    191 /usr/sbin/wimax/cmd_app 3 asngw_ep_ip 0xC0A80132
    192 }}}
    193 
    194 
    195 
    196 
    197 == Manual Configuration Of SAMrb ==
    198 
    199 Note these instructions need to be followed if you are using just the SAMrb instead of the full omf-wimaxrf-aggmgr-5.2 webservice.
    200 
    201 Once you untar and enter in the SAMrb directory you can edit the file SimpleAuthManager.rb.
    202 
    203 In this file please change the following to reflect your network settings:
    204 1. The $ips hash table should be updated to include your client mac to IP mapping.
    205 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.
    206 
    207 == Configuration of ASN-GW Controller and NEC IDU ==
     220== 6.5 Configuration of ASN-GW Controller and WiMAX RF Agg Mgr ==
    208221
    209222Configuration of software both for the ASN-GW and the WiMAX BTS is done through a single yaml configuration file on the ASN.
    … …  
    244257
    245258
    246 
    247 
    248 == Testing ==
    249 
    250 === Simple Checks ===
     259These are the files which are located in the /etc directory on the asn-gw machine.
     260
     261In this section we will describe the changes required to the default configuration files for accommodating custom settings and IPs.
     262
     263
     264
     265==== asnctrl ====
     266The points that need to be changed in the asnctrl.conf file are:
     267{{{
     268R6_BSID[0] = 00:00:04:00:00:00      // BSID allocated as per GENI
     269R6_BSAddress[0] = [10.3.Y.61]:2231  //IP address of the IDU
     270TunnelEndpoint = [10.3.Y.71]:0      //IP of the ASN - GW
     271}}}
     272
     273==== asnctrl_ASNGW000 ====
     274{{{
     275R4_BSID[0][0]=00:00:04:00:00:00
     276}}}
     277
     278==== asnctrl_common ====
     279No changes are required in this file.
     280
     281==== asnctrl_gre ====
     282This is an output file which shows the mapping of the client MAC address to the uplink and downlink GRE tunnel. This file does not need any configuration.
     283
     284==== asnctrl_service_class ====
     285This file contains the mapping of the mac address to the service class. Sample entries are as shown below:
     286{{{
     28700:18:41:85:5e:a3       IP-Config-Mgmt
     28800:12:cf:b2:ad:9a       IP-Config-Mgmt
     28900:12:cf:b2:a4:e8       IP-Config-Mgmt
     29000:12:cf:b2:9c:73       IP-Config-Mgmt
     29100:1b:8b:54:02:9a       IP-Config-Mgmt
     29200:1b:8b:54:02:84       IP-Config-Mgmt
     29300:1d:e1:0a:5e:87       IP-Config-Mgmt
     294}}}
     295
     296==== clasify-ctrl ====
     297This file is located here: /usr/share/asngw/classify-ctrl.sh
     298IP addresses need to be updated here based on the settings used:
     299{{{
     300: ${DEV_R3:="eth0"}
     301: ${DEV_R6R4:="eth1"}
     302: ${MSADDR:="10.42.0.0/16"}
     303: ${R3_NETWORK:="10.41.0.0/16"}
     304: ${R3_ADDR:="10.41.0.3"}   
     305: ${R6R4_NETWORK:="192.168.1.0/24"}
     306: ${R6R4_ADDR:="192.168.1.50"} 
     307}}}
     308
     309
     310==== trapctrl ====
     311No changes are required in this file.
     312
     313==== epctrl ====
     314{{{
     315R3LocalDevice = eth0
     316R4LocalDevice = eth1
     317R6LocalDevice = eth1
     318}}}
     319
     320== 6.6  Configuration of CLICK ==
     321
     322Configuration of the CLICK router is done by SAM.rb.
     323
     324Here is an example configuration when no MSs are registered:
     325
     326(sample)
     327
     328Here is an example configuration when one MS is registered:
     329
     330(sample)
     331
     332
     333== 6.7 Operations and Testing ==
     334
     335
     336=== 6.7.1 Login to Base Station Server ===
     337
     338Login through the console on the Base Station Server (ASN-GW) and test the following.
     339
     3401. The BTS should be reachable from the ASN-GW with the default IP setting:
     341    - ping the BTS interface; it was assigned the fixed IP 192.168.1.10.
     342    - measure the round trip times
     343
     3442. Power cycle the BTS through the use of stop and start scripts.
     345   - Perform a hard reset if required (if updated parameter values are not reflected).
     346   - There should also be a green light on the IDU after a software power cycle of the IDU.
     347   - The software power cycle can be preformed by the following commands:
     348    {{{
     349    /etc/init.d/asn-gw stop
     350    /etc/init.d/asn-gw start
     351    }}}
     352
     3533. Ping the outside interface and see if the DMZ gateway is reachable from the ASN-GW
     354
     355After successful completion we know that the ASN is able to send traffic both downlink to the IDU
     356and outbound towards the internet.
     357
     358
     359=== 6.7.2  Login to BTS ===
     360
     361 1.  To login: 
     362
     363(sample)
     364
     365 2. Power cycle the BTS through the use of stop and start scripts.
     366   - Perform a hard reset if required (if updated parameter values are not reflected).
     367   - There should also be a green light on the IDU after a software power cycle of the IDU.
     368   - The software power cycle can be preformed by the following commands:
     369    {{{
     370    /etc/init.d/asn-gw stop
     371    /etc/init.d/asn-gw start
     372    }}}
     373
     374
     375=== 6.7.3  ASN GW Operation ===
     376
     377
     378To control the WiMAX base station, run the stop and start scripts as follows:
     379
     380Start script:
     381{{{
     382/etc/init.d/snmpd start
     383/etc/rc.d/init.d/trapctrl start
     384sleep 1
     385/etc/rc.d/init.d/asnctrl start
     386sleep 1
     387/etc/rc.d/init.d/epctrl start
     388#sleep 1
     389}}}
     390
     391
     392Stop script:
     393{{{
     394/etc/rc.d/init.d/epctrl stop
     395/etc/rc.d/init.d/asnctrl stop
     396/etc/rc.d/init.d/trapctrl stop
     397/etc/init.d/snmpd stop
     398pkill -9 asnctrl
     399pkill -9 epctrl
     400}}}
    251401
    252402A few simple checks to make sure things are working:
    253  1. You should be able to ping the Base Station, it was assigned the fixed IP 192.168.1.10.
     403
     404
     405 1. There should be 3 running processes:
     406    {{{
     407    root      3128     1  0 19:10 ?        00:00:00 trapctrl
     408    root      3137     1  0 19:10 ?        00:00:02 asnctrl
     409    root      3227     1  0 19:10 ?        00:00:02 epctrl
     410    }}}
     411
    254412 1. Some log files should start filling up in '''/var/log''':
    255413  1. asnctrl.log
    256414  1. epctrl.log
    257  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:
    258     {{{
    259     /etc/init.d/asn-gw stop
    260     /etc/init.d/asn-gw start
    261     }}}
    262  1. There should be 3 running processes:
    263     {{{
    264     root      3128     1  0 19:10 ?        00:00:00 trapctrl
    265     root      3137     1  0 19:10 ?        00:00:02 asnctrl
    266     root      3227     1  0 19:10 ?        00:00:02 epctrl
    267     }}}
    268 
    269 
    270 === Prerequisites ===
    271 
    272 1. Confirm that all hardware and software has been properly installed.
    273 
    274 
    275 === Hardware connectivity check ===
    276 
    277 Login through the console on the ASN-GW and test the following.
    278 
    279 1. Is the BTS is reachable from the ASN-GW. with the default IP setting
    280     - ping the BTS interface
    281     - measure the round trip times
    282 
    283 2. Power cycle the BTS through the use of stop and start scripts.
    284    - Perform a hard reset if required (if updated parameter values are not reflected).
    285 
    286 3. Ping the outside interface and see if the DMZ gateway is reachable from the ASN-GW
    287 
    288 After successful completion we know that the ASN is able to send traffic both downlink to the IDU
    289 and outbound towards the internet.
    290 
    291 === Test the RF Transmission ===
     415
     416
     417
     418=== 6.7.4 RF Transmission ===
    292419
    2934201. 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.
    … …  
    295422Configure driver at the client to ensure all required parameters are configured correctly.
    296423   - Change the /etc/asnctrl_service_class.conf to include client and service class information.
    297    - possibly include SSID to match with the BTS
     424   - Possibly include SSID to match with the BTS
    298425   - Check center frequency to match with the BTS
    299426   - Enable (locks) if any
    … …  
    305432   - 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.
    306433
     434=== 6.7.5 SAM Monitoring ===
     435
     436
     437=== 6.7.6 CLICK Modular Router Monitoring ===
     438
     439
     440=== 6.7.7  Mobile Station Registration ===
     441
     442
     443=== 6.7.8  Traffic Monitoring ===
     444
     445Install wireshark on ethernet interfaces.