User Tools

Site Tools


wings-testbeds

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
wings-testbeds [2008/09/23 22:27]
pratap
wings-testbeds [2008/09/23 22:29]
pratap
Line 1: Line 1:
-About+===== About =====
 The WiNGS wireless testbed consists of about 100 nodes, deployed in the Department of Computer Sciences building. This wireless testbed is part of the WiNGS lab, of which Prof. Suman Bannerjee is the founder. The WiNGS wireless testbed consists of about 100 nodes, deployed in the Department of Computer Sciences building. This wireless testbed is part of the WiNGS lab, of which Prof. Suman Bannerjee is the founder.
-Accesss+ 
 +===== Access =====
 The testbed is for research purposes only, and access is restricted. Only students and researchers affiliated to WiNGS lab are allowed. The testbed is for research purposes only, and access is restricted. Only students and researchers affiliated to WiNGS lab are allowed.
-Contact+ 
 +===== Contact ​=====
 Contact viveks at cs or shravan at cs, for all questions. Contact viveks at cs or shravan at cs, for all questions.
-Testbed Usage Policy+ 
 +===== Testbed Usage Policy ​=====
 TODO TODO
  
-Test-bed details +===== Test-bed details ​===== 
-Controller details+ 
 +==== Controller details ​==== 
 The controller viveks-unsup.cs is housed in the WiNGS lab, room #3360 All access to the nodes go through the controller. To gain acces to the nodes the user should ssh to the controllder,​ and then ssh to the nodes. The controller should not be shutdown for any reason. However, if it has to rebooted, please follow these instructions given below to bring the testbed online. The controller viveks-unsup.cs is housed in the WiNGS lab, room #3360 All access to the nodes go through the controller. To gain acces to the nodes the user should ssh to the controllder,​ and then ssh to the nodes. The controller should not be shutdown for any reason. However, if it has to rebooted, please follow these instructions given below to bring the testbed online.
  
Line 15: Line 20:
     * ./​execute_server ( This will start the NFS daemon on the controller)     * ./​execute_server ( This will start the NFS daemon on the controller)
  
-Nodes+==== Nodes ==== 
 Most of the nodes are Soekris, model 4826 . They are placed on the office rooms in the 3rd, 4th, 5th, 6th and 7th floors of the building. Both the main tower, and the condor tower house these nodes. Placing of nodes and configuring is a tedious process that has to go through CSL. See below for contact information. We use Power Over Ethernet (POE) to for power control of these nodes. They are connected to 5 POE switches Most of the nodes are Soekris, model 4826 . They are placed on the office rooms in the 3rd, 4th, 5th, 6th and 7th floors of the building. Both the main tower, and the condor tower house these nodes. Placing of nodes and configuring is a tedious process that has to go through CSL. See below for contact information. We use Power Over Ethernet (POE) to for power control of these nodes. They are connected to 5 POE switches
  
Line 25: Line 31:
  
 All the nodes can be accessed through the IP address or hostname node-. The nodes are fitted with 802.11 abg wireless cards. All the nodes can be accessed through the IP address or hostname node-. The nodes are fitted with 802.11 abg wireless cards.
-Node Mapping+==== Node Mapping ​==== 
 The mapping of which nodes are mapped to which OS is given in /​etc/​bootptab so a line like node34:​tc=.client:​ht=1:​ha=000024C711A8:​ip=128.105.102.164:​ means that node 34 is booted in the "​client"​ os, that could be found in /​tftpboot/​client The mapping of which nodes are mapped to which OS is given in /​etc/​bootptab so a line like node34:​tc=.client:​ht=1:​ha=000024C711A8:​ip=128.105.102.164:​ means that node 34 is booted in the "​client"​ os, that could be found in /​tftpboot/​client
-Port Mapping+==== Port Mapping ​==== 
 Mapping of nodes to particular ports can be found in /​usr/​sbin/​poe_control Please do not change this mapping unless the nodes are specifically moved from one location to another. Then still you should consult Vivek or Shravanme before you change anything. Mapping of nodes to particular ports can be found in /​usr/​sbin/​poe_control Please do not change this mapping unless the nodes are specifically moved from one location to another. Then still you should consult Vivek or Shravanme before you change anything.
-How does one create/use a different image for a node?+==== How does one create/use a different image for a node? ==== 
 Any user should try to use the existing setup, and try to work with that, unless, creating a new image is necessary. By default, the node should use the os named expt_client (see inside /​tftpboot/​). We dont have space to allow everyone to create their own images for experimentation. As I said earlier you can decide which node boots to which OS by changing entries in /​etc/​bootptab. Any user should try to use the existing setup, and try to work with that, unless, creating a new image is necessary. By default, the node should use the os named expt_client (see inside /​tftpboot/​). We dont have space to allow everyone to create their own images for experimentation. As I said earlier you can decide which node boots to which OS by changing entries in /​etc/​bootptab.
-How to install a new driver on a node?+ 
 +==== How to install a new driver on a node? ====
 TODO TODO
  
 +==== How to add a new node? ====
  
-How to add a new node? 
 TODO TODO
  
- +===== Scripts for normal user =====
-Scripts for normal user+
  
     * convert_to_ap,​ convert _to_client is run on the soekris nodes to convert them to ap and client respectively.     * convert_to_ap,​ convert _to_client is run on the soekris nodes to convert them to ap and client respectively.
wings-testbeds.txt · Last modified: 2008/09/23 23:19 by suman