Changes between Version 1 and Version 2 of shadownetexp23


Ignore:
Timestamp:
11/09/12 16:04:21 (7 years ago)
Author:
Hussamuddin Nasir
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • shadownetexp23

    v1 v2  
    1 Experiment with Junipers connected to pcs/vms using VLAN'ed links
    2 --------------------
     1== Experiment with Junipers connected to pcs/vms using VLAN'ed links ==
     2
    33This type experiment has two major limitations
    44
    5 a) PC/VMs used can only be from the Utah Testbed with its phsyical location being either at the University of Utah or any of the internet2 POP where the Utah Testbed's HP Procurve switch is located.
    6 b) Currently this involves manully editing the rspec to add vlantags . This support is not available when using FLACK. So this experiment has to be created using the protogeni Test Scripts
     5a) PC/VMs used can only be from the Utah Testbed with its phsyical location being either at the University of Utah or any of the internet2 POP where the Utah Testbed's HP Procurve switch is located.[[BR]]
     6b) Currently this involves manully editing the rspec to add vlantags . This support is not available when using FLACK. So this experiment has to be created using the protogeni Test Scripts[[BR]]
    77
    88
     
    1010
    1111
    12 Lets create such an experiment using the rspec below. 
     12Lets create such an experiment using the rspec below.
    1313(insert shadownet_stitch_utah.rspec here)
    1414
     
    2626./sliverstatus -n shadow-demo -m https://www.emulab.net/protogeni/xmlrpc/cm until sliverstatus returns a ready state.
    2727
    28 
    2928Once we have a ready state, we now look at the manifest returned and note down all the "vlantag= " returned for each link
    3029
    3130Now create a copy of the original rspec and comment out all the utah sections and uncomment all shadownet sections.
     31
    3232Replace the VlanId attributes in each link with the relevant Vlan Tags and the IP addresses on the each link in the juniper section.
    3333
     
    4343
    4444
     45Once the experiment is up and running, we have to setup routing on the routers and the pcs to talk to each other.
    4546
    46 Once the experiment is up and running, we have to setup routing on the routers and the pcs to talk to each other.
    47 The set of commands and its output for this example are shown below.
     47The set of commands and its output for this example are shown in the files attached below.
    4848
    4949WASH_Router.output