260 | | * License status [[BR]] |
261 | | * Location and backhaul [[BR]] |
262 | | * Mobility and handover [[BR]] |
263 | | * Add OMF/OML [[BR]] |
264 | | * Connect to I2 backbone network [[BR]] |
265 | | |
266 | | * Planned local experiments [[BR]] |
267 | | |
268 | | [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/ucla%20%20%202012-July-10-GEC.pptx slides] [[BR]] |
| 263 | |
| 264 | * Status [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/ucla%20%20%202012-July-10-GEC.pptx slides] [[BR]] |
| 265 | |
| 266 | * License [[BR]] |
| 267 | * Renewed Experimental License [[BR]] |
| 268 | * Coordination with Clearwire Started [[BR]] |
| 269 | |
| 270 | * Airspan Installation [[BR]] |
| 271 | * About 4 additional Weeks [[BR]] |
| 272 | * 2 Weeks to Power [[BR]] |
| 273 | * 2 Weeks for Installation [[BR]] |
| 274 | * Delays may come if Facility des not bring Power. [[BR]] |
| 275 | |
| 276 | * Connection to Mesoscale Infrastructure [[BR]] |
| 277 | * 3-4 weeks depending on the Facility management [[BR]] |
| 278 | * Preliminary setup of the VLAN (backbone side) could start in about 1.5 weeks. [[BR]] |
| 279 | |
| 280 | * Experiments [[BR]] |
| 281 | * Planning multiple-path network-coded tcp experiments with MIT [[BR]] |
| 282 | * Once Connected to ION we will be able to run Nation Wide experiments. [[BR]] |
| 283 | |
281 | | * License status [[BR]] |
282 | | * Location and backhaul [[BR]] |
283 | | * Mobility and handover [[BR]] |
284 | | |
285 | | * Planned local experiments [[BR]] |
286 | | |
287 | | [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/GEC14-WiMAX-Clemson.ppt slides] [[BR]] |
| 296 | |
| 297 | * Status: [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/WiMAXDeploymentsAndExperiments/GEC14-WiMAX-Clemson.ppt slides] [[BR]] |
| 298 | |
| 299 | * Project Status |
| 300 | |
| 301 | * General Installation: |
| 302 | * Server currently being installed with Windows Server 2008 R2 |
| 303 | * Awaiting CCIT to complete installation process |
| 304 | * Additional machine ready to handle OMF/OML |
| 305 | * Two VLANs created for client and management traffic |
| 306 | * Tunnel established to Rutgers to enable temporary use of Netspan software |
| 307 | |
| 308 | * Clemson campus location: |
| 309 | * Base station installed |
| 310 | * Both VLANs run to base station |
| 311 | * Initial configuration performed using Rutgers’ Netspan installation |
| 312 | * Largely mirrored from Rutgers’ installation |
| 313 | * 10 MHz channel centered at 2507.5 MHz |
| 314 | * One transmitter is reporting low output power due to RF fault |
| 315 | * Unable to detect a signal from the base station in line-of-sight |
| 316 | * Obtaining spectrum analyzer to verify signal output |
| 317 | |
| 318 | * Project Status |
| 319 | * Greenville location: |
| 320 | * Mounting equipment, electrical, and fiber installation estimated by July 10th |
| 321 | * One base station untested, one experiencing startup failure |
| 322 | |
| 323 | * Startup failure: |
| 324 | * One base station does not properly boot up |
| 325 | * Upon applying power, a single UDP packet is transmitted to 192.168.0.1:6666 |
| 326 | * This packet reveals a console session to an embedded Linux installation on the base station |
| 327 | * No web interface is available for basic configuration |
| 328 | * In communication with Airspan regarding repair |
| 329 | * Hoping that another working base station can be used to reimage |
| 330 | |
| 331 | Other observations |
| 332 | * After configuration, base station needed to be reset after losing Netspan connection due to power failure |
| 333 | |
| 334 | |
| 335 | |