Changes between Version 22 and Version 23 of Old/WiMAX/04/01

Timestamp:

Dec 8, 2010, 11:46:17 PM (13 years ago)

Author:

hmussman

Comment:

—

Old/WiMAX/04/01

@@ -25 +25 @@
 These are the key parameters, that are gathered and then held in the yaml configuration file
 
+{{{
+# 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:
@@ -44 +52 @@
    bsid: 00:00:04:00:00:01
    frequency: 2590000                           
-
+}}}
 
 
@@ -315 +323 @@
 }}}
 
-== 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:
+== 5.7  Configuration of CLICK ==
+
+Configuration of the CLICK router is done by SAM.rb.
+
+Here is an example configuration when no MSs are registered:
+
+(sample)
+
+Here is an example configuration when one MS is registered:
+
+
+== 5.8 Operations and Testing ==
+
+
+=== 5.8.1 Login to Base Station Server ===
+
+Login through the console on the Base Station Server (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; it was assigned the fixed IP 192.168.1.10.
+    - 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).
+   - 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
     }}}
+
+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.
+
+
+=== 5.8.2  Login to BTS ===
+
+ 1.  To login:  (sample)
+
+ 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).
+   - 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
+    }}}
+
+
+=== 5.8.3  ASN GW Operation ===
+
+
+To control the WiMAX base station, run the stop and start scripts as follows:
+
+Start script:
+{{{
+/etc/init.d/snmpd start
+/etc/rc.d/init.d/trapctrl start
+sleep 1
+/etc/rc.d/init.d/asnctrl start
+sleep 1
+/etc/rc.d/init.d/epctrl start
+#sleep 1
+}}}
+
+
+Stop script:
+{{{
+/etc/rc.d/init.d/epctrl stop
+/etc/rc.d/init.d/asnctrl stop
+/etc/rc.d/init.d/trapctrl stop
+/etc/init.d/snmpd stop
+pkill -9 asnctrl
+pkill -9 epctrl
+}}}
+
+A few simple checks to make sure things are working:
+
+
  1. There should be 3 running processes: 
     {{{
@@ -336 +411 @@
     }}}
 
-
-=== 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. Some log files should start filling up in '''/var/log''':
+  1. asnctrl.log
+  1. epctrl.log
+
+
+
+=== 5.8.4 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.
@@ -373 +432 @@
 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.
+
+=== 5.8.5 SAM Monitoring ===
+
+
+=== 5.8.6 CLICK Modular Router Monitoring ===
+
+
+=== 5.8.9  Mobile Station Registration ===
+
+
+=== 5.8.10  Traffic Monitoring ===
+
+Install wireshark on ethernet interfaces.