[[PageOutline]] == 1.3 GENI WiMAX Site Operations Resources == === 1.3.1 GENI WiMAX Operations Objectives === 1) Each GENI WiMAX site must operate in accordance with their FCC Experimental License and/or agreement with Clearwire, to avoid interference with others (particularly Clearwire) operating in the BRS/EBS spectrum. 2) Each GENI WiMAX site must cooperate with others (particularly Clearwire) if interference is suspected, to resolve the issue. This may involve temporarily going off-the-air, to see if they are or are not the source of the observed interference. 3) Each GENI WiMAX site must verify and maintain the accuracy of the information in the tables listed below, and follow the operations procedures listed below. It is essential that each site have a responsive local "Ops" contact, as listed in the table below. 3a) Task: All entries in tables below must be verified by 12/15/12. 4) Each GENI WiMAX site must install the site monitoring software, included in the latest WiMAX RF AggMgr, so that they are automatically forwarding operating paramaters to the OML Server at Rutgers WINLAB, who will then use the data to populate the [http://oml.orbit-lab.org:4040/tab/home_tab GENI WiMAX Monitoring] site. 4a) Task: Rutgers WINLAB must provide the new latest WiMAX RF AggMgr, that automatically forwards operating parameters to the OML Server at Rutgers WINLAB, by 1/15/13. [[BR]] 4b) Task: All sites must install the new latest WiMAX RF AggMgr, and commence forwarding operating parameters to the OML Server at Rutgers WINLAB, by 2/15/13. 5) Each GENI WiMAX site is expected to make their resources available to GENI experimenters. === 1.3.2 GENI WiMAX Operations Procedures === (to be filled in) === 1.3.3 GENI WiMAX Operations Contacts === GENI WiMAX operations mailing list: [[BR]] [mailto:wimax-operator@email1.winlab.rutgers.edu mail to all site contacts and operations contacts] [[BR]] [http://email1.winlab.rutgers.edu/cgi-bin/mailman/subscribe/wimax-operator subscribe] [[BR]] [http://lists.winlab.rutgers.edu/cgi-bin/mailman/private/wimax-operator mailman archive] [[BR]] GENI WiMAX Operations Contacts: ||= Index =||= Organizations =||= Contacts =||= Comments =||= Last Verified =|| || 1.1 ||Rutgers WINLAB|| [mailto:seskar@winlab.rutgers.edu Ivan Seskar] || - || || || 1.2 ||Rutgers WINLAB|| || - || || || 1.3 ||Rutgers WINLAB|| || - || || || 1.4 ||Rutgers WINLAB|| || - || || || 2.1 ||GPO (at BBN Technologies)||[mailto:agosain@bbn.com Manu Gosain] || - || || || 2.2 ||GPO (at BBN Technologies)||[mailto:hmussman@bbn.com Harry Mussman] || - || || || 2.3 ||GPO (at BBN Technologies)|| || - || || || 2.4 ||GPO (at BBN Technologies)|| || - || || || 3.1 ||GMOC (at IU)|| || - || || || 3.2 ||GMOC (at IU)|| || - || || || 3.3 ||GMOC (at IU)|| || - || || || 3.4 ||GMOC (at IU)|| || - || || || 4.1 || Clearwire ||[mailto:paul.mccarthy@clearwire.com Paul McCarthy] || - || || || 4.2 || Clearwire ||[mailto: Don White] || - || || || 4.3 || Clearwire ||[mailto: Josh LaVerne] || - || || || 4.4 || Clearwire || || - || || === 1.3.4 GENI WiMAX Site Monitoring === Each GENI WiMAX site forwrds operating paramaters to an OML Server at Rutgers WINLAB, which uses the data to populate the: [[BR]] [http://oml.orbit-lab.org:4040/tab/home_tab GENI WiMAX Monitoring] site. [[BR]] ==== Wimax Base-station Statistics Monitoring ==== Periodically,the wimaxbase stations across the campuses report numerical data like frequency, power, number of users, UL/DL transfer rates, number of clients etc to the Global OML (Orbit Lab). The following documentation includes details about how these statistics can be visualized and monitored. ==== Base-station statistics database ==== * IDB1 in orbit-lab collects the sqlite database of statistics for each of the basestation sites. IDB1 can be accessed from the gateway. The sqlite data resides in the /var/lib/oml2 directory. * import.py script takes an sqlite database and converts it into csv. Change the code to make it point to the database you want to convert. * parse_wimaxbs_relations.py reads from the csv and prints out the relation_cache.txt. It contains the mapping between sender id and the campus name. * Change parse_wimaxbs_relations.py to point towards the csv created the previous step. * Other changes made included, adding the following files. * parse_basestations_relations (original) * report wimax_basestations_relations: Added a basestation "node" resource to each aggregate * The parsing script is run as a cron job every 5 minutes. Every 5 minutes, a new txt file is created. * The gmoc client script (gmoc.py) was changed to account for the new wimax base station metrics. A new class 'wimaxbasestationStats' was added. It specifies the metric that are being reported by the Wimax basestation statistics. * To run the script (s1/ parse_wimaxbs_relations) use the following format {{{ python s1.py -oml_sender_id 0 -oml_seq 0 -oml_ts_client 0 -oml_ts_server 0 -frequency 0 -power 0 -noclient 0 -ulsdu= 0 -ulpdu= 0 -dlsdu 0 -dlpdu 0 }}} === 1.3.5 GENI WiMAX Sites and Contacts === ||= Index =||= Campus =||= Location =||= CW Table =||= CW Srvc =||= CW Agree =||= FCC Exp Lic =||= Type =||= Lower Freq (MHz) =||= Upper Freq (MHz) =||= Status =||= Contacts =||= Comments =||= Last Verified =|| || 0a ||Rutgers WINLAB||Piscataway (MIDDLESEX), NJ; NL 40-31-17; WL 74-27-40; xxdeg azim; yyft height || - || Yes || - || [https://apps.fcc.gov/els/GetAtt.html?id=127868&x=. WE2XWE]; thru 12/5/13 || [wiki:NECBS NEC] || 2585 || 2595 || On-the-air || Ops:[mailto:admin@orbit-lab.org ORBIT Admin]; PI:[http://www.winlab.rutgers.edu/~seskar Ivan Seskar] ||At WINLAB || 6/20/13 || || 0b || - ||Piscataway (MIDDLESEX), NJ; NL 40-31-17; WL 74-27-40|| - || - || - || - || [wiki:NECBS NEC] || 2585 || 2595 ||Non-radiating testbed [http://www.orbit-lab.org/wiki/Hardware/gDomains/dSB4 sanbox4] || - ||At WINLAB || 6/20/13 || || 0c || - ||North Brunswick (MIDDLESEX), NJ; NL 40-28-05; WL 74-26-44; xxdeg azim; yyft height || - || Yes || - || [https://apps.fcc.gov/els/GetAtt.html?id=127868&x=. WE2XWE]; thru 12/5/13 || [wiki:AirBS Airspan] || 2605 || 2615 || On-the-air || - ||On Busch Campus || 6/20/13 || || 2a || Raytheon BBN Tech ||Cambridge (MIDDLESEX), MA; NL 42-23-18; WL 71-08-57; xxdeg azim; yyft height || - || Yes || - || [https://apps.fcc.gov/oetcf/els/reports/442_Print.cfm?mode=current&application_seq=43846&license_seq=44316 WF2XHS]; thru 3/26/14 || - || 2512.5 || 2517.5 || Not in use (per CW request) || Ops:[mailto:agosain@bbn.com Manu Gosain]; PI:[mailto:agosain@bbn.com Manu Gosain] || || 6/14/2013 || || 2b || - ||Cambridge (MIDDLESEX), MA; NL 42-23-18; WL 71-08-57; xxdeg azim; yyft height || - || Yes || - || [https://apps.fcc.gov/els/GetAtt.html?id=122612&x=. WF2XHD]; thru 2/24/14 || - || 2585 || 2595 || Not in use (per CW request) || - || || || || 2c || - ||Cambridge (MIDDLESEX), MA; NL 42-23-18; WL 71-08-57; xxdeg azim; yyft height || - || Yes || - || [https://apps.fcc.gov/oetcf/els/reports/442_Print.cfm?mode=current&application_seq=53182&license_seq=53707 WG2XJH]; thru 9/19/15 || [wiki:NECBS NEC] alternating [wiki:AirBS Airspan] || 2573 || 2583 || On-the-air (freq per CW suggest) || - || || 6/14/2013 || || 4a || NYU Poly || Brooklyn, NY; NEC - NL 40-41-40.25; WL 73-59-9.5; 187 xxdeg azim; 60 yyft height from ground level; Airspan - NL 40-41-41; WL 73-59-09; 277 xxdeg azim; 60 yyft height from ground level; || [http://wimax.orbit-lab.org/attachment/wiki/WiMAX/00/01/042312%20NYU%20Poly%20%20GENI%20-%20Clearwire.doc Yes] || Yes || - || [https://apps.fcc.gov/els/GetAtt.html?id=124115&x=. WF2XJM]; thru 4/1/14 || [wiki:NECBS NEC] or [wiki:AirBS Airspan] || 2590 || 2600 || On-the-air || Ops:[mailto:ffund01@students.poly.edu Fraida Fund]; PI:[mailto:korakis@poly.edu Thanasis Korakis] || || || || 4b || - || Brooklyn, NY; NL 40-41-41; WL 73-59-09; xxdeg azim; yyft height; NL 40-41-39; WL 73-59-10; xxdeg azim; yyft height || [http://wimax.orbit-lab.org/attachment/wiki/WiMAX/00/01/042312%20NYU%20Poly%20%20GENI%20-%20Clearwire.doc Yes] || Yes || - || [https://apps.fcc.gov/els/GetAtt.html?id=124115&x=. WF2XJM]; thru 4/1/14 || || 2610 || 2620 || Not in use (per CW request) || - || || || || 4c || - || Brooklyn, NY; NL 40-41-41; WL 73-59-09; xxdeg azim; yyft height; NL 40-41-39; WL 73-59-10; xxdeg azim; yyft height || [http://wimax.orbit-lab.org/attachment/wiki/WiMAX/00/01/042312%20NYU%20Poly%20%20GENI%20-%20Clearwire.doc Yes] || Yes || - || [https://apps.fcc.gov/els/GetAtt.html?id=124114&x=. WF2XKY]; thru 6/1/14 || || 2535 || 2540 || Not in use (per CW request) || - || || || || 5 || UMass Amherst || Amherst (HAMPSHIRE); MA - NL 42-23-37; WL 72-31-55; xxdeg azim; yyft height || [http://wimax.orbit-lab.org/attachment/wiki/WiMAX/00/01/040512_UMassAmherst_ClearwireSpectrumAllocationRequestForm.XLSX Yes] || Yes || - || [https://apps.fcc.gov/els/GetAtt.html?id=105119&x=. WF2XGQ]; thru 3/1/13 || [wiki:NECBS NEC] || 2590 || 2600 || On-the-air || Ops:[mailto:cwang@ecs.umass.edu Cong Wang]; PI:[mailto:zink@ecs.umass.edu Mike Zink] || || 3/3/2013 || || 6 || Columbia Univ || New York (Manhattan), NY; NL 40-48-34; WL 73-57-36; 270° azim; 170ft height (16th floor) || [http://wimax.orbit-lab.org/attachment/wiki/WiMAX/00/01/042312%20%20Columbia%20%20GENI%20-%20Clearwire.doc Yes] || Yes || - || [https://apps.fcc.gov/oetcf/els/reports/405_Print.cfm?mode=current&application_seq=48804 WF2XIU]; thru 4/1/13 || [wiki:NECBS NEC] || 2590 || 2596 || On-the-air ||Ops:[mailto:janakj@cs.columbia.edu Jan Janak]; PI:[mailto:hgs@cs.columbia.edu Henning Schulzrinne] || || 3/3/2013 || || 7 || Univ Colorado, Boulder || Boulder (BOULDER), CO; NL 39-59-53; WL 105-15-07; xxdeg azim; yyft height; NL 40-00-24; WL 105-16-17; xxdeg azim; yyft height; NL 40-00-26; WL 105-15-47; xxdeg azim; yyft height; NL 40-00-29; WL 105-16-04; xxdeg azim; yyft height || - || ? || - || [https://apps.fcc.gov/els/GetAtt.html?id=125661&x=. WF2XJV]; thru 5/1/14 || [wiki:NECBS NEC] || 2572 || 2584 || On-the-air || Ops:; PI:[mailto:grunwald@cs.colorado.edu Dirk Grunwald] || || || || 8a || Univ Wisconsin, Madison || Madison (DANE), WI; NL 43-04-17; WL 89-24-24; xxdeg azim; yyft height || - || Yes || - || [https://apps.fcc.gov/els/GetAtt.html?id=122362&x=. WF2XXF]; thru 3/30/13 || [wiki:CiscoBs Cisco] || 2584.5 || 2589.5 || On-the-air || Ops:[mailto:dmeyer@cs.wisc.edu Derek Meyer]; PI:[mailto:suman@cs.wisc.edu Suman Banerjee] || || 5/28/2013 || || 8b || - || Madison (DANE), WI; NL 43-04-31; WL 89-24-24; xxdeg azim; yyft height || - || Yes || - || [https://apps.fcc.gov/els/GetAtt.html?id=122362&x=. WF2XXF]; thru 3/30/13 || [wiki:NECBS NEC] || 2544.5 || 2554.5 || On-the-air || - || || 5/28/2013 || || 8c || - || Madison (DANE), WI; NL 43-04-34; WL 89-25-34; xxdeg azim; yyft height || - || Yes || - || [https://apps.fcc.gov/els/GetAtt.html?id=122362&x=. WF2XXF]; thru 3/30/13 || [wiki:AirBS Airspan] || 2585.5 || 2595.5 || On-the-air || - || || 5/28/2013 || || 8d || - || Kemp Station (VILAS); WI - NL 45-50-22; WL 89-40-33; xxdeg azim; yyft height || - || Yes || - || [https://apps.fcc.gov/els/GetAtt.html?id=122362&x=. WF2XXF]; thru 3/30/13 || [wiki:NECBS NEC] || 2544.5 || 2554.5 || On-the-air || - || || 5/28/2013 || || 8e || - || Madison (DANE), WI; NL 43-07-30; WL 89-38-20; xxdeg azim; yyft height || - || Yes || - || [https://apps.fcc.gov/els/GetAtt.html?id=122362&x=. WF2XXF]; thru 3/30/13 || [wiki:AirBS Airspan] || 2568 || 2578 || On-the-air || - || || 5/28/2013 || || 9a || UCLA || Los Angeles (LOS ANGELES), CA; NL 34-04-09; WL 118-26-36; xxdeg azim; 80ft height || - || Yes || - || [https://apps.fcc.gov/els/GetAtt.html?id=125216&x=. WF2XLG]; thru 6/1/14 || [wiki:NECBS NEC] || 2567 || 2577 || On-the-air || Ops: [mailto:davidepesa@ucla.edu Davide Pesavento]; PI: [mailto:gpau@cs.ucla.edu Giovanni Pau] || || 7/1/2013 || || 9b || - || Los Angeles (LOS ANGELES), CA; NL 34-04-09; WL 118-26-36; xxdeg azim; yyft height || - || Yes || - || [https://apps.fcc.gov/els/GetAtt.html?id=125216&x=. WF2XLG]; thur 6/1/14 || [wiki:AirBS Airspan] || 2585 || 2595 || Not yet deployed || - || || 7/1/2013 || || 10a || Clemson Univ || Greenville (GREENVILLE), SC; NL 34-49-31; WL 82-18-26; 20deg azim; <6ft height || - || Yes || Yes; thru 3/1/15 || [https://apps.fcc.gov/oetcf/els/reports/442_Print.cfm?mode=current&application_seq=50498&license_seq=51025 WG2XCG]; thru 2/10/14 || [wiki:AirBS Airspan] || 2502 || 2535 || On-the-air || Ops:[mailto:rizard@clemson.edu Ryan Izard]; PI:[mailto:kwang@clemson.edu K-C Wang ] || || 4/20/2013 || || 10b || - || Greenville (GREENVILLE), SC; NL 34-49-31; WL 82-18-26; 200deg azim; <6ft height || - || Yes || Yes; thru 3/1/15 || [https://apps.fcc.gov/oetcf/els/reports/442_Print.cfm?mode=current&application_seq=50498&license_seq=51025 WG2XCG]; thru 2/10/14 || [wiki:AirBS Airspan] || 2502 || 2535 || On-the-air || - || || 4/20/2013 || || 10c || - || Greenville (GREENVILLE), SC; NL 34-48-50; WL 82-19-38; 50deg azim; <6ft height || - || Yes || Yes; thru 3/1/15 || [https://apps.fcc.gov/oetcf/els/reports/442_Print.cfm?mode=current&application_seq=50498&license_seq=51025 WG2XCG]; thru 2/10/14 || [wiki:AirBS Airspan] || 2502 || 2535 || On-the-air || - || || 4/20/2013 || || 10d || - || Greenville (GREENVILLE), SC; NL 34-48-50; WL 82-19-38; 250deg azim; <6ft height || - || Yes || Yes; thru 3/1/15 || [https://apps.fcc.gov/oetcf/els/reports/442_Print.cfm?mode=current&application_seq=50498&license_seq=51025 WG2XCG]; thru 2/10/14 || [wiki:AirBS Airspan] || 2502 || 2535 || Not-in-use || - || || || || 10e || - || Clemson (PICKENS), SC; NL 34-40-37; WL 82-50-1; 50deg azim; <6ft height || - || Yes || Yes; thru 3/1/15 || [https://apps.fcc.gov/oetcf/els/reports/442_Print.cfm?mode=current&application_seq=50498&license_seq=51025 WG2XCG]; thru 2/10/14 || [wiki:AirBS Airspan] || 2502 || 2535 || Not-in-use || - || || || || 10f || - || Clemson (PICKENS), SC; NL 34-40-37; WL 82-50-1; 250deg azim; <6ft height || - || Yes || Yes; thru 3/1/15 || [https://apps.fcc.gov/oetcf/els/reports/442_Print.cfm?mode=current&application_seq=50498&license_seq=51025 WG2XCG]; thru 2/10/14 || [wiki:AirBS Airspan] || 2502 || 2535 || Not-in-use || - || || || || 10g || - || Clemson (PICKENS), SC; NL 34-40-31; WL 82-50-21; 50deg azim; <6ft height || - || Yes || Yes; thru 3/1/15 || [https://apps.fcc.gov/oetcf/els/reports/442_Print.cfm?mode=current&application_seq=50498&license_seq=51025 WG2XCG]; thru 2/10/14 || [wiki:AirBS Airspan] || 2502 || 2535 || Not-in-use || - || || || || 10h || - || Clemson (PICKENS), SC; NL 34-40-31; WL 82-50-21; 250deg azim; <6ft height || - || Yes || Yes; thru 3/1/15 || [https://apps.fcc.gov/oetcf/els/reports/442_Print.cfm?mode=current&application_seq=50498&license_seq=51025 WG2XCG]; thru 2/10/14 || [wiki:AirBS Airspan] || 2502 || 2535 || Not-in-use || - || || || || 11a || Wayne State Univ || Detroit, MI; Lat 42.357500; Long -83.065000; 270deg azim; 207ft height || [http://wimax.orbit-lab.org/attachment/wiki/WiMAX/00/01/042312%20%20Wayne%20State%20%20%20GENI%20-%20Clearwire.doc Yes] || Yes || Yes || - || [wiki:AirBS Airspan] || 2591 || 2601 || On-the-air || Ops:[mailto: ]; PI:[mailto:hongwei@wayne.edu Hongwei Zhang] || || 4/10/2013 || || 11b || - || Detroit, MI; Lat 42.357500; Long -83.065000; 30deg azim; 202ft height || [http://wimax.orbit-lab.org/attachment/wiki/WiMAX/00/01/042312%20%20Wayne%20State%20%20%20GENI%20-%20Clearwire.doc Yes] || Yes || Yes || - || [wiki:AirBS Airspan] || 2591 || 2601 || On-the-air || - || || 4/10/2013 || || 11c || - || Detroit, MI; Lat 42.357500; Long -83.065000; 150deg azim; 202ft height || [http://wimax.orbit-lab.org/attachment/wiki/WiMAX/00/01/042312%20%20Wayne%20State%20%20%20GENI%20-%20Clearwire.doc Yes] || Yes || Yes || - || [wiki:AirBS Airspan] || 2591 || 2601 || Not yet deployed || - || || || || 12 || Univ Michigan ||Ann Arbor, MI; NL 42-17-31.9992; WL 83-42-52.9986; xxdeg azim; yyft height || [http://wimax.orbit-lab.org/attachment/wiki/WiMAX/00/01/042312%20%20%20Michigan%20%20GENI%20-%20Clearwire.doc Yes] || Yes || Yes; thru 2/18/13 || - || [wiki:AirBS Airspan] || 2502 || 2512 || On-the-air || Ops:[mailto: ];PI:[mailto:zmao@umich.edu Morley Mao] || || 6/1/2013 || || 13a || Temple Univ || Philadelphia, PA; NL 39-57-35; WL 75-11-26 (39.98038, -75.15703); xxdeg azim; yyft height || [http://wimax.orbit-lab.org/attachment/wiki/WiMAX/00/01/042312%20%20Temple%20%20GENI%20-%20Clearwire.doc Yes] || Yes || Yes; thru 1/31/13 || - || [wiki:AirBS Airspan] || 2585 || 2595 || Deployed (Not-On-the-air) || Ops:;PI:[mailto:Shan.lin@temple.edu Shan Lin] || Freq shared with Drexel || 6/20/2013 || || 13b || - || Philadelphia, PA; NL 39-57-35; WL 75-11-26 (39.98038, -75.15703); xxdeg azim; yyft height || [http://wimax.orbit-lab.org/attachment/wiki/WiMAX/00/01/042312%20%20Temple%20%20GENI%20-%20Clearwire.doc Yes] || Yes || Yes; thru 1/31/13 || - || [wiki:AirBS Airspan] || 2603 || 2613 || Not yet deployed || - || Freq shared with Drexel || || || 14a || Drexel Univ || Philadelphia (PHILADELPHIA),PA; NL 39-57-35; WL 75-11-26; xxdeg azim; yyft height || [http://wimax.orbit-lab.org/attachment/wiki/WiMAX/00/01/042312%20Drexel%20%20GENI%20-%20Clearwire.doc Yes] || Yes || Yes; thru 1/31/13 || [https://apps.fcc.gov/oetcf/els/reports/442_Print.cfm?mode=current&application_seq=50559&license_seq=51086 WG2XBX]; thru 2/13/14 || [wiki:AirBS Airspan] || 2585 || 2595 || Not yet deployed || Ops:[mailto:ktw25@drexel.edu Kevin Wanuga]; PI:[mailto:dandekar@coe.drexel.edu Kapil Dandekar] || Freq shared with Temple || || || 14b || - || Philadelphia (PHILADELPHIA),PA; NL 39-57-35; WL 75-11-26; xxdeg azim; yyft height || [http://wimax.orbit-lab.org/attachment/wiki/WiMAX/00/01/042312%20Drexel%20%20GENI%20-%20Clearwire.doc Yes] || Yes || Yes; thru 1/31/13 || [https://apps.fcc.gov/oetcf/els/reports/442_Print.cfm?mode=current&application_seq=50559&license_seq=51086 WG2XBX]; thru 2/13/14 || [wiki:AirBS Airspan] || 2603 || 2613 || Not yet deployed || - || Freq shared with Temple || || [http://www.heavens-above.com/glossary.aspx?term=azimuth definition of azimuth] [[BR]] === 1.3.6 GENI WiMAX Site Experimenter Login Interfaces === Several GENI WiMAX sites support interfaces that allow an Experimenter to login, reserve resources, and then conduct experiments utilizing resources available at that site. See the following table for details. [[BR]] This login approach follows the method supported by the ORBIT testbed, although the exact login process varies as noted. [[BR]] ||= Index =||= Campus =||= Available? =||= url =||= Comments =|| || 0 || Rutgers WINLAB || Yes || ? || - || || 1 || NECLabs || NA || - || - || || 2 || Raytheon BBN Tech || Pending || - || - || || 3 || Stanford || NA || - || - || || 4 || Poly || Yes || ? || - || || 5 || UMass || No || - || - || || 6 || Columbia || No || - || - || || 7 || UColorado || No || - || - || || 8 || UWisconsin || Yes || ? || - || || 9 || UCLA || Yes || - || - || || 10 || Clemson || No || - || - || || 11 || Wayne State || No || - || - || || 12 || UMichigan || No || - || - || || 13 || Temple || No || - || - || || 14 || Drexel || No || - || - || === 1.3.7 GENI WiMAX Site Backbone Connections === Several GENI WiMAX sites have connections to the GENI backbone provided by Internet2, as summarized in the following table. [[BR]] ||= Index =||= Campus =||= I2 connection =||= ION ckt to Rutgers WINLAB =||= Support multi-site experiments? =|| || 0 || Rutgers WINLAB || Yes || Yes || Yes || || 1 || NECLabs || NA || - || - || || 2 || Raytheon BBN Tech || Yes || Yes || Yes || || 3 || Stanford || NA || - || - || || 4 || Poly || Yes || Yes || Yes || || 5 || UMass || No || - || - || || 6 || Columbia || No || - || - || || 7 || UColorado || No || - || - || || 8 || UWisconsin || Yes || Yes || - || || 9 || UCLA || Yes || Yes || Yes || || 10 || Clemson || Yes || Pending || Pending || || 11 || Wayne State || No || - || - || || 12 || UMichigan || No || - || - || || 13 || Temple || No || - || - || || 14 || Drexel || No || - || - || ION circuits provided by Internet2 are used to carry VLANs from the site to a routing server at Rutgers WINLAB, as summarized in the following table. [[BR]] || '''ION circuit''' || '''Status''' || '''Start Time''' || '''End Time''' || '''[#IONEndpoints Source ]''' || '''Source VLAN''' || '''[#IONEndpoints Destination]''' || '''Destination VLAN''' || '''Bandwidth''' || '''Details''' || || 10822 || active || 02/29/2012 || 10/03/2012 || bbn.newy.ion.internet2.edu || 3735 || NYU.newy.ion.internet2.edu || 4080 || 100 Mbps || I2 WiMAX BBN to NYU || || 11347 || active || 10/01/2012 || 11/07/2012 || bbn.newy.ion.internet2.edu || 3733 || MAGPI.wash.ion.internet2.edu || 3733 || 100 Mbps || I2 WiMAX BBN to Rutgers || || 14741 || active || 10/2/2012 || 1/7/2014 || MAGPI.wash.ion.internet2.edu || 194 || CalREN.losa.ion.internet2.edu || 3150 || 100 Mbps || I2 WiMAX Rutgers to UCLA || || 11322 || active || 9/11/2012 || 12/31/2012 || MAGPI.wash.ion.internet2.edu || 190 || NYU.newy.ion.internet2.edu || 4081 || 100 Mbps || I2 WiMAX Rutgers to NYU || || 11428 || active || 10/22/2012 || 12/31/2012 || MAGPI.wash.ion.internet2.edu || 195 || SOX.chic.ion.internet2.edu || 1780 || 100 Mbps || I2 WiMAX Rutgers to Clemson || || 14461 || active || 2/20/2013 || 1/7/2014 || MAGPI.wash.ion.internet2.edu || 196 || cic-force10.ion.internet2.edu || 915 || 100 Mbps || I2 WiMAX Rutgers to Wisconsin || || 18511 || active || 6/5/2013 || 1/7/2014 || MAGPI.wash.ion.internet2.edu || 198 || chic.ion.internet2.edu || 1815 || 100 Mbps || I2 WiMAX Rutgers to Wayne state University || This arrangement provides a private IP network between all of the connected sites, as summarized in the following figure. [[Image(i2connwimax62113.png)]] [[BR]] Private IP addresses are assigned at each site, as summarized in the following table. [[BR]] ||= Index =||= Campus =||= OID =||= BS IP Range =||= GENI Backbone Client Range =|| || 0 || Rutgers WINLAB || 44:51:DB:00:00:XX || 10.3.0.XX || 10.43.0.XX || || 1 || NECLabs || 44:51:DB:00:01:XX || 10.3.1.XX || 10.43.1.XX || || 2 || Raytheon BBN Tech || 44:51:DB:00:02:XX || 10.3.2.XX || 10.43.2.XX || || 3 || Stanford || 44:51:DB:00:03:XX || 10.3.3.XX || 10.43.3.XX || || 4 || Poly || 44:51:DB:00:04:XX || 10.3.4.XX || 10.43.4.XX || || 5 || UMass || 44:51:DB:00:05:XX || 10.3.5.XX || 10.43.5.XX || || 6 || Columbia || 44:51:DB:00:06:XX || 10.3.6.XX || 10.43.6.XX || || 7 || UColorado || 44:51:DB:00:07:XX || 10.3.7.XX || 10.43.7.XX || || 8 || UWisconsin || 44:51:DB:00:08:XX || 10.3.8.XX || 10.43.8.XX || || 9 || UCLA || 44:51:DB:00:09:XX || 10.3.9.XX || 10.43.9.XX || || 10 || Clemson || 44:51:DB:00:10:XX || 10.3.10.XX || 10.43.10.XX || || 11 || Wayne State || 44:51:DB:00:11:XX || 10.3.11.XX || 10.43.11.XX || || 12 || UMichigan || 44:51:DB:00:12:XX || 10.3.12.XX || 10.43.12.XX || || 13 || Temple || 44:51:DB:00:13:XX || 10.3.13.XX || 10.43.12.XX || || 14 || Drexel || 44:51:DB:00:14:XX || 10.3.14.XX || 10.43.13.XX || This allows the connected sites to participate in multi-site experiments. === R1 BRS/EBS BAND PLAN === {{{ #!html
Channel DesignationLower FrequencyUpper FrequencyComment
BRS 124952496Guard Band
BRS 124962502LBS
A125022507.5
A22507.52513
A325132518.5
B12518.52524
B225242529.5
B32529.52535
C125352540.5
C22540.52546
C325462551.5
D12551.52557
D225572562.5
D32562.52568
J25682572
A425722578MBS
B425782584
C425842590
D425902596
G425962602
F426022608
E426082614
K26142618
BRS 226182624Guard Band
E126242629.5UBS
E22629.52635
E326352640.5
F12640.52646
F226462651.5
F32651.52657
H126572662.5
H22662.52668
H326682673.5
G12673.52679
G226792684.5
G32684.52690
}}} === R2 WiMAX Site Deployments === [http://groups.geni.net/geni/wiki/SpiralFour#a4.GENIWiMAXMeso-ScaleDeployments GENI WiMAX Site Deployments wiki pages] == 1.4 GENI WiMAX Omf Site Setup == === 1.4.1 Network setup and configuration === A site will receive a console machine, which runs all the OMF aggregate manager services and three client resources. Two of these client resources will have a fixed power supply. The third client will have a 12 V power supply so that it can function as a mobile node. All services on the console machine will be configured to use the geni.net sub-domain and all IP addresses will be initially configured in the following scheme. * Data - 10.1.2.X/24 * CM - 10.1.0.X/24 * Control - 10.1.1.X/24 Three networks Data CM Control 3 switches, 1 partitioned switch, or single cable out. Each site is asked to provide an Ubuntu 12.04 Host to run the Wimax-rf software. This requirement is based on the fact that most deployments are in remote locations or higher elevation locations so keeping the base station software closer to the base station is the motivation. This host will have 2 interfaces * Public Internet Interface to communicate with the console machine. * Interface that connects to the base station or a switch connected to the base station. Setup networking as follows on the console host {{{ # 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 # The CM network interface auto eth1 iface eth1 inet static address 10.1.0.254 netmask 255.255.255.0 broadcast 10.1.0.255 # The Control network interface auto eth3 iface eth3 inet static address 10.1.1.254 netmask 255.255.255.0 broadcast 10.1.1.255 # The Data network interface auto eth0 iface eth0 inet static address 10.1.2.254 netmask 255.255.255.0 broadcast 10.1.2.255 # The primary network interface auto eth2 iface eth2 inet dhcp }}} ==== One unmanaged switch per subnet ==== [[Image(4Node_1.png, 600)]] ==== Single managed switch ==== [[Image(4Node_2.png, 600)]] ==== Single trunk per node ==== [[Image(4Node_3.png, 600)]] The console is called console.geni.net. You can ssh into it with the following credentials. {{{ username: native password: native101 }}} ==== 1.4.1.1 CMC Networking ==== * By design 'native' user needs to run sudo for omf commands. Or become root with: {{{ sudo su }}} Once you have the testbed set up as explained above, use the following commands to talk to the nodes or troubleshoot. 1. Testing network connections to the CM cards * '''omf stat''' can be used to find the status of the CM networked nodes. The manual page is shown below. {{{ > omf help stat Returns the status of the nodes in a testbed Usage: stat [-h] stat [-c] [DOMAIN] stat "[TOPOLOGY]" [DOMAIN] With: -h, --help print this help message -c, --count print a summary of the node status for the testbed DOMAIN (default is the testbed where this command is executed) TOPOLOGY a valid topology description or file without the trailing '.rb' (default is the entire set of nodes on the default testbed) Some Examples: stat all grid stat "[[1,2],[1,1]]" sb1 stat "[[1,1],[2..6,1..2]]" stat system:topo:all stat system:topo:circle stat topo_grid_active }}} Once all the networking of the nodes is as described above, you may provide power to your client nodes. It takes a couple minutes, but you should see State: POWEROFF as listed below. {{{ INFO NodeHandler: OMF Experiment Controller 5.4 (git 5385228) INFO NodeHandler: Slice ID: default_slice (default) INFO NodeHandler: Experiment ID: default_slice-2013-07-18t11.42.12.965-04.00 INFO NodeHandler: Message authentication is disabled INFO Experiment: load system:exp:stdlib INFO property.resetDelay: resetDelay = 90 (Fixnum) INFO property.resetTries: resetTries = 1 (Fixnum) INFO Experiment: load system:exp:eventlib INFO Experiment: load system:exp:winlib INFO Experiment: load system:exp:stat INFO property.nodes: nodes = "system:topo:all" (String) INFO property.summary: summary = false (FalseClass) INFO Topology: Loading topology 'system:topo:all'. Talking to the CMC service, please wait ----------------------------------------------- Node: node1.geni.net State: POWEROFF Node: node2.geni.net State: POWEROFF Node: node3.geni.net State: NOT REGISTERED ----------------------------------------------- INFO EXPERIMENT_DONE: Event triggered. Starting the associated tasks. INFO NodeHandler: INFO NodeHandler: Shutting down experiment, please wait... INFO NodeHandler: INFO run: Experiment default_slice-2013-07-18t11.42.12.965-04.00 finished after 0:5 }}} If you have power connected to your nodes and are still getting NOT REGISTERED for your state, check your networking connections or managed switch configurations. NOT REGISTERED means that your CMC service cannot communicate with your client nodes. Once you get State: POWEROFF, you can test powering on and off your nodes with an omf tell. 2. '''omf tell''' The manual page is shown below. {{{ > omf help tell Switch ON/OFF the nodes in a testbed Usage: tell [-h] tell [COMMAND] "[TOPOLOGY]" [DOMAIN] With: -h, --help print this help message COMMAND: on, -on, --turn-on turn node(s) ON offs, -offs, --turn-off-soft turn node(s) OFF (soft) offh, -offh, --turn-off-hard turn node(s) OFF (hard) TOPOLOGY a valid topology description or file (default is the entire set of nodes on the default testbed) Some Examples: tell on all grid tell on "1,1..2" tell offs "[[1,2],[1,1]]" sb1 tell offs "[[1,1],[2..6,1..2]]" tell offh system:topo:all tell offh topo_grid_active }}} Here is an example output of turning a node on: {{{ sudo omf tell -a on -t node1.geni.net INFO NodeHandler: OMF Experiment Controller 5.4 (git 5385228) INFO NodeHandler: Slice ID: default_slice (default) INFO NodeHandler: Experiment ID: default_slice-2013-07-29t17.29.03.703-04.00 INFO NodeHandler: Message authentication is disabled INFO Experiment: load system:exp:stdlib INFO property.resetDelay: resetDelay = 90 (Fixnum) INFO property.resetTries: resetTries = 1 (Fixnum) INFO Experiment: load system:exp:eventlib INFO Experiment: load system:exp:winlib INFO Experiment: load system:exp:tell INFO property.nodes: nodes = "node1.geni.net" (String) INFO property.command: command = "on" (String) INFO Topology: Loading topology 'node1.geni.net'. Talking to the CMC service, please wait ----------------------------------------------- Node: node1.geni.net Reply: OK ----------------------------------------------- INFO EXPERIMENT_DONE: Event triggered. Starting the associated tasks. INFO NodeHandler: INFO NodeHandler: Shutting down experiment, please wait... INFO NodeHandler: INFO run: Experiment default_slice-2013-07-29t17.29.03.703-04.00 finished after 0:5 }}} The same can be done to turn a node off by changing the parameter after the "-a" as listed in the help output listed above. ===== CMC Networking Troubleshooting ===== * Check your inventory database for correct ip address specified for the cmc interface. * Check your managed switch configuration. * Check to make sure you have the cmc interfaces plugged in to the correct ports/switch. * Check for link light when the nodes have power ran to them. The nodes do not have to be powered on. ==== Imaging ==== Since your client nodes did not come with images preloaded on them, you will have to image your nodes for the first time. This can be done with the '''omf load''' command. {{{ omf load output here. }}} === 1.4.2. Setting up Wimax-RF service for Airspan BS === == 1.5 GENI WiMAX Omf Site Setup ERRATA == === 1.5.1 Networking discrepencies === === 1.5.2 Imaging Issues === 1. Name resolution * The nodes are unable to find 'xmpp', which causes imaging to fail. * We used to use dnamasq with pointer records for this, are we moving to isc-dhcp and bind? * On the console node, nameservers are set to 127.0.0.1, 10.0.0.8, and 10.0.0.9