Changes between Version 186 and Version 187 of WiMAXInteg


Ignore:
Timestamp:
05/07/10 15:08:44 (10 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WiMAXInteg

    v186 v187  
    401401=== 6.6  Server Hardware ===
    402402
    403 Fig 1-2a)  Hardware and Networking  [[BR]]
    404 [[Image(Visio-111309b_WiMAXSystemOverview_Page_2.jpg, 90%)]]  [[BR]]
    405 
    406 Figure 1-2a) shows the full configuration with three servers: [[BR]]
    407  ASNGW-03, that provides combined ASN GW functions. [[BR]]
    408  ASNGW-02, that provides virtualized ASN GW functions, for separate slices. [[BR]]
    409  OMF-04, that provides a set of OMF/OML functions. [[BR]]
    410 
    411 In some cases, a campus already has a set of OMF/OML functions, and would likely not require the OMF-04 server:[[BR]]
    412  Rutgers, WINLAB[[BR]]
    413  Rutgers, Bush Campus[[BR]]
    414  Polytechnic Institute of NYU[[BR]]
    415  
    416 For the initial bringup, it should be possible to load all functions into one server.[[BR]]
    417 
    418 Recommended server hardware for one-server solution: [[BR]]
     403Per Section 6.1, the system can be configured with as many as three servers, but will be configured with one server for initial bringup, per Figure 2-1c).[[BR]]
     404
     405The recommended server hardware for the one-server configuration is: [[BR]]
    419406 * [http://groups.geni.net/geni/attachment/wiki/WiMAXInteg/041510%20%20Quote_5018368.pdf  Line item 2:  HP DL160 G6 dual-processor server]  [[BR]]
    420407 * [http://www.intel.com/Products/Server/Adapters/PRO1000PT-DualPort/PRO1000PT-DualPort-overview.htm  Intel PRO/1000 PT dual-port server adaptor]  [[BR]]
     
    445432=== 6.10  Control and Management  ===
    446433
     434Control and management of each WiMAX testbed will be done via OMF;  see Figure 1-5):
     435
    447436Fig 1-5)  Control and Management  [[BR]]
    448437[[Image(Visio-111309b_WiMAXSystemOverview_Page_7.jpg, 90%)]]  [[BR]]
     
    451440=== 6.11  Backbone Network Access ===
    452441
    453 
     442Each WiMAX testbed must be connected to a L2 and/or L3 backbone network to handle experiment data flows;  see Figure 2-1a).  The VLANs associated with each slice must be switched to the appropriate backbone VLAN, or to the backbone L3 network.  [[BR]]
     443
     444The Rutgers WINLAB testbed has been connected to the Internet2 backbone network, and has used the ION service to extend L2 (VLAN) connections to the NICTA and BBN testbeds.  Thus, Internet2 is the preferred backbone for all WimAX testbeds.[[BR]]
    454445
    455446=== 6.12  Federation  ===
    456447
    457 During initial bringup, each WiMAX testbed will operate as a self-contained OMF-controlled testbed.
    458 
    459 Then, various WiMAX testbeds will be federated, by implementing:  [[BR]]
    460  Coordinated OMF control of two or more testbeds by one experimenter.[[BR]]
     448During initial bringup, each WiMAX testbed will operate as a self-contained OMF-controlled testbed.  [[BR]]
     449
     450Then, various WiMAX testbeds will be federated, by:  [[BR]]
     451 Connecting the Management and Control Networks of the testbeds together using a multipoint VLAN provided by the GENI backbone, to permit coordinated OMF control of two or more testbeds by one experimenter.[[BR]]
    461452 Connecting experiment data from testbeds together, using a VLAN carried by a GENI backbone.[[BR]]
    462453
    463 Issue:  How will federation among WiMAX testbeds be accomplished?
    464 
    465 Issue:  How will WiAMX tesbeds be connected together, using a VLAN carried by a GENI backbone?
    466454
    467455=== 6.13  Monitoring and Management ===