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 21 and Version 22 of Old/WiMAX/04/01


Ignore:
Timestamp:
Dec 8, 2010, 11:24:47 PM (10 years ago)
Author:
hmussman
Comment:

Legend:

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

    v21 v22  
     1[[PageOutline]]
     2
    13= 5.  Case 1:  Software Installation, Configuration and Operation =
    24
    35
    4 == WiMAX OID and IP Address Assignment ==
     6== 5.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
     23== 5.2  Key Configuration Parameters ==
     24
     25These are the key parameters, that are gathered and then held in the yaml configuration file
     26
     27
     28  asngw:
     29   if: eth1
     30   ip: 192.168.1.50
     31   port: 2231
     32   id: ASNGW000
     33   tecnh: 3
     34   dsc: IP-Config-Mgmt
     35
     36  click:
     37    def_gw: 10.41.0.1
     38    net_mask: 255.255.0.0
     39    def_ip: 10.41.0.254
     40
     41  bs:
     42   ip: 192.168.1.10
     43   mask: 255.255.255.0
     44   bsid: 00:00:04:00:00:01
     45   frequency: 2590000                           
     46
     47
     48
     49==  5.3 Base Station Server Installation ==
     50
     51
     52=== 5.3.1 Expected OS: Ubuntu 9.04 ===
     53
    2854   {{{
    2955   lsb_release -a
     
    3460   Codename:       jaunty
    3561   }}}   
    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
     62
     63=== 5.3.2  Setup Ethernet Interfaces ===
     64
     65It 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
    3766   reflect the correct physical ports. The '''/etc/network/interfaces''' file should look similar to this:
    3867   {{{
     
    6897   }}}
    6998
    70 === Install Required Packages ===
     99=== 5.3.3 Install Required Packages ===
    71100
    72101 1. Configure apt/sources to include mytestbed.net and orbit-lab.org. Edit the '''/etc/apt/sources.list''' and add the following lines:
     
    83112    sudo apt-get install asn-gw0.9.0 click1.6.0 omf-wimaxrf-aggmgr-5.2
    84113    }}}
     114
     115 1. Install SAM.rb from reposiotry into home directory
     116
    85117    This will install 333MB or so worth of packages. You will need to confirm some of the packages from our repository.
    86 
    87 
    88 
    89118
    90119[wiki:/Software/Create Create Debian Package][[BR]]
     
    92121
    93122
    94 == Setting up the NEC BTS ==
     123== 5.4  Setup NEC BTS ==
    95124
    96125Please 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.
    97126
    98 === Step1 Configuring the IP ===
     127=== 5.4.1:  Step 1 Configuring the IP ===
    99128
    100129We'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.
     
    134163 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.
    135164
    136 === Step 2a Configure The BS software ===
     165=== 5.4.2  Step 2  Configure the BTS software ===
     166
    137167  1. ssh to the new IP of the DSP machine. ssh !root@10.3.x.1
    138168  1. Use wiset commands below to correct configuration on the BTS:
     
    172202
    173203
    174 === Step 2b  BTS Configuration ===
     204
     205
     206== 5.5 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== 5.6 Configuration of ASN-GW Controller ==
     218
     219Configuration of software both for the ASN-GW and the WiMAX BTS is done through a single yaml configuration file on the ASN.
     220
     221To 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/'''.
     222
     223Edit this file change settings (if needed)
     224{{{
     225# NOTE: use only 'spaces' to indent !
     226# ('tab' indents are not supported by the ruby yaml parser used to read this file)
     227#
     228# This is the Config file for the WiMAXRF GridService
     229#
     230---
     231wimaxrf:
     232
     233  asngw:
     234   if: eth1
     235   ip: 192.168.1.50
     236   port: 2231
     237   id: ASNGW000
     238   tecnh: 3
     239   dsc: IP-Config-Mgmt
     240
     241  click:
     242    def_gw: 10.41.0.1
     243    net_mask: 255.255.0.0
     244    def_ip: 10.41.0.254
     245
     246  bs:
     247   ip: 192.168.1.10
     248   mask: 255.255.255.0
     249   bsid: 00:00:04:00:00:01
     250   frequency: 2590000                           
     251}}}
     252
     253Making changes in this file should propagate changes to the ASN software and the BTS (IDU) software.
     254
     255
     256These are the files which are located in the /etc directory on the asn-gw machine.
     257
     258In this section we will describe the changes required to the default configuration files for accommodating custom settings and IPs.
     259
     260
     261
     262==== asnctrl ====
     263The points that need to be changed in the asnctrl.conf file are:
     264{{{
     265R6_BSID[0] = 00:00:04:00:00:00      // BSID allocated as per GENI
     266R6_BSAddress[0] = [10.3.0.61]:2231  //IP address of the IDU
     267TunnelEndpoint = [10.3.0.71]:0      //IP of the ASN - GW
     268}}}
     269
     270==== asnctrl_ASNGW000 ====
     271{{{
     272R4_BSID[0][0]=00:00:04:00:00:00
     273}}}
     274
     275==== asnctrl_common ====
     276No changes are required in this file.
     277
     278==== asnctrl_gre ====
     279This 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.
     280
     281==== asnctrl_service_class ====
     282This file contains the mapping of the mac address to the service class. Sample entries are as shown below:
     283{{{
     28400:18:41:85:5e:a3       IP-Config-Mgmt
     28500:12:cf:b2:ad:9a       IP-Config-Mgmt
     28600:12:cf:b2:a4:e8       IP-Config-Mgmt
     28700:12:cf:b2:9c:73       IP-Config-Mgmt
     28800:1b:8b:54:02:9a       IP-Config-Mgmt
     28900:1b:8b:54:02:84       IP-Config-Mgmt
     29000:1d:e1:0a:5e:87       IP-Config-Mgmt
     291}}}
     292
     293==== clasify-ctrl ====
     294This file is located here: /usr/share/asngw/classify-ctrl.sh
     295IP addresses need to be updated here based on the settings used:
     296{{{
     297: ${DEV_R3:="eth0"}
     298: ${DEV_R6R4:="eth1"}
     299: ${MSADDR:="10.42.0.0/16"}
     300: ${R3_NETWORK:="10.41.0.0/16"}
     301: ${R3_ADDR:="10.41.0.3"}   
     302: ${R6R4_NETWORK:="192.168.1.0/24"}
     303: ${R6R4_ADDR:="192.168.1.50"} 
     304}}}
     305
     306
     307==== trapctrl ====
     308No changes are required in this file.
     309
     310==== epctrl ====
     311{{{
     312R3LocalDevice = eth0
     313R4LocalDevice = eth1
     314R6LocalDevice = eth1
     315}}}
     316
     317== Testing ==
     318
     319=== Simple Checks ===
     320
     321A few simple checks to make sure things are working:
     322 1. You should be able to ping the Base Station, it was assigned the fixed IP 192.168.1.10.
     323 1. Some log files should start filling up in '''/var/log''':
     324  1. asnctrl.log
     325  1. epctrl.log
     326 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:
     327    {{{
     328    /etc/init.d/asn-gw stop
     329    /etc/init.d/asn-gw start
     330    }}}
     331 1. There should be 3 running processes:
     332    {{{
     333    root      3128     1  0 19:10 ?        00:00:00 trapctrl
     334    root      3137     1  0 19:10 ?        00:00:02 asnctrl
     335    root      3227     1  0 19:10 ?        00:00:02 epctrl
     336    }}}
     337
     338
     339=== Prerequisites ===
     340
     3411. Confirm that all hardware and software has been properly installed.
     342
     343
     344=== Hardware connectivity check ===
     345
     346Login through the console on the ASN-GW and test the following.
     347
     3481. Is the BTS is reachable from the ASN-GW. with the default IP setting
     349    - ping the BTS interface
     350    - measure the round trip times
     351
     3522. Power cycle the BTS through the use of stop and start scripts.
     353   - Perform a hard reset if required (if updated parameter values are not reflected).
     354
     3553. Ping the outside interface and see if the DMZ gateway is reachable from the ASN-GW
     356
     357After successful completion we know that the ASN is able to send traffic both downlink to the IDU
     358and outbound towards the internet.
     359
     360=== Test the RF Transmission ===
     361
     3621. 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.
     363
     364Configure driver at the client to ensure all required parameters are configured correctly.
     365   - Change the /etc/asnctrl_service_class.conf to include client and service class information.
     366   - possibly include SSID to match with the BTS
     367   - Check center frequency to match with the BTS
     368   - Enable (locks) if any
     369   - Disable wifi if operating on a dual mode card (since quite a few times they work in a mutually exclusive mode)
     370   - Enable a static IP setting at the client to allow for baseline IP connectivity
     371
     372
     3732. If possible sweep the spectrum through an analyzer to determine proper transmission at the center frequency.
     374   - 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.
     375
     376
     377
     378= 6.  Case 1:  Operation =
     379
     380== IDU (base station) Software Configuration ==
    175381
    176382Cat the following code to a shell script and execute after sshing into the BTS at the default ip: 192.168.1.10.
     
    199405
    200406
    201 
    202 
    203 == Manual Configuration Of SAMrb ==
    204 
    205 Note these instructions need to be followed if you are using just the SAMrb instead of the full omf-wimaxrf-aggmgr-5.2 webservice.
    206 
    207 Once you untar and enter in the SAMrb directory you can edit the file SimpleAuthManager.rb.
    208 
    209 In this file please change the following to reflect your network settings:
    210 1. The $ips hash table should be updated to include your client mac to IP mapping.
    211 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.
    212 
    213 == Configuration of ASN-GW Controller and NEC IDU ==
    214 
    215 Configuration of software both for the ASN-GW and the WiMAX BTS is done through a single yaml configuration file on the ASN.
    216 
    217 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/'''.
    218 
    219 Edit this file change settings (if needed)
    220 {{{
    221 # NOTE: use only 'spaces' to indent !
    222 # ('tab' indents are not supported by the ruby yaml parser used to read this file)
    223 #
    224 # This is the Config file for the WiMAXRF GridService
    225 #
    226 ---
    227 wimaxrf:
    228 
    229   asngw:
    230    if: eth1
    231    ip: 192.168.1.50
    232    port: 2231
    233    id: ASNGW000
    234    tecnh: 3
    235    dsc: IP-Config-Mgmt
    236 
    237   click:
    238     def_gw: 10.41.0.1
    239     net_mask: 255.255.0.0
    240     def_ip: 10.41.0.254
    241 
    242   bs:
    243    ip: 192.168.1.10
    244    mask: 255.255.255.0
    245    bsid: 00:00:04:00:00:01
    246    frequency: 2590000                           
    247 }}}
    248 
    249 Making changes in this file should propagate changes to the ASN software and the BTS (IDU) software.
    250 
    251 
    252 
    253 
    254 == Testing ==
    255 
    256 === Simple Checks ===
    257 
    258 A few simple checks to make sure things are working:
    259  1. You should be able to ping the Base Station, it was assigned the fixed IP 192.168.1.10.
    260  1. Some log files should start filling up in '''/var/log''':
    261   1. asnctrl.log
    262   1. epctrl.log
    263  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:
    264     {{{
    265     /etc/init.d/asn-gw stop
    266     /etc/init.d/asn-gw start
    267     }}}
    268  1. There should be 3 running processes:
    269     {{{
    270     root      3128     1  0 19:10 ?        00:00:00 trapctrl
    271     root      3137     1  0 19:10 ?        00:00:02 asnctrl
    272     root      3227     1  0 19:10 ?        00:00:02 epctrl
    273     }}}
    274 
    275 
    276 === Prerequisites ===
    277 
    278 1. Confirm that all hardware and software has been properly installed.
    279 
    280 
    281 === Hardware connectivity check ===
    282 
    283 Login through the console on the ASN-GW and test the following.
    284 
    285 1. Is the BTS is reachable from the ASN-GW. with the default IP setting
    286     - ping the BTS interface
    287     - measure the round trip times
    288 
    289 2. Power cycle the BTS through the use of stop and start scripts.
    290    - Perform a hard reset if required (if updated parameter values are not reflected).
    291 
    292 3. Ping the outside interface and see if the DMZ gateway is reachable from the ASN-GW
    293 
    294 After successful completion we know that the ASN is able to send traffic both downlink to the IDU
    295 and outbound towards the internet.
    296 
    297 === Test the RF Transmission ===
    298 
    299 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.
    300 
    301 Configure driver at the client to ensure all required parameters are configured correctly.
    302    - Change the /etc/asnctrl_service_class.conf to include client and service class information.
    303    - possibly include SSID to match with the BTS
    304    - Check center frequency to match with the BTS
    305    - Enable (locks) if any
    306    - Disable wifi if operating on a dual mode card (since quite a few times they work in a mutually exclusive mode)
    307    - Enable a static IP setting at the client to allow for baseline IP connectivity
    308 
    309 
    310 2. If possible sweep the spectrum through an analyzer to determine proper transmission at the center frequency.
    311    - 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.
    312 
    313 
    314 
    315 = 6.  Case 1:  Operation =
    316 
    317 == IDU (base station) Software Configuration ==
    318 
    319 Cat the following code to a shell script and execute after sshing into the BTS at the default ip: 192.168.1.10.
    320 If ssh does not work, try with a serial console.
    321 
    322 {{{
    323 /usr/sbin/wimax/cmd_app 3 authgw_id 0x41534E4757303030
    324 /usr/sbin/wimax/cmd_app 3 authgw_port 0x08B7
    325 /usr/sbin/wimax/cmd_app 3 asngw_id 0x41534E4757303030
    326 /usr/sbin/wimax/cmd_app 3 asngw_dp_port  0x08B7
    327 /usr/sbin/wimax/cmd_app 3 asngw_ep_port 0x08B7
    328 /usr/sbin/wimax/cmd_app 3 bs_rx_port 0x08B7
    329 /usr/sbin/wimax/cmd_app 3 bsid 0x000004000000
    330 /usr/sbin/wimax/cmd_app 3 frequency  2551500
    331 /usr/sbin/wimax/cmd_app 3 bs_tx_power 40
    332 /usr/sbin/wimax/cmd_app 3 bw_mode 0
    333 /usr/sbin/wimax/cmd_app 3 dlul_ratio 2
    334 /usr/sbin/wimax/cmd_app 3 ttg 296
    335 /usr/sbin/wimax/cmd_app 3 rtg 168
    336 /usr/sbin/wimax/cmd_app 3 framesync_mode 2
    337 /usr/sbin/wimax/cmd_app 3 antenna_gain 0
    338 /usr/sbin/wimax/cmd_app 3 authgw_ip 0xC0A80132
    339 /usr/sbin/wimax/cmd_app 3 asngw_dp_ip 0xC0A80132
    340 /usr/sbin/wimax/cmd_app 3 asngw_ep_ip 0xC0A80132
    341 }}}
    342 
    343 
    344407== ASN-GW Controller Configuration Files ==
    345408