Changes between Version 2 and Version 3 of shadownetexp23


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

--

Legend:

Unmodified
Added
Removed
Modified
  • shadownetexp23

    v2 v3  
    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.[[BR]]
    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[[BR]]
     5a) PC / VMs used can only be from the Utah Testbed with its physical 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]]
    76
    8 
    9 (Below stuff in shadownet_stitch.notes)
    10 
     7b) Currently this involves manually editing the rspec to add vlan tags . This support is not available when using FLACK. So this experiment has to be created using the protogeni Test Scripts[[BR]]
    118
    129Lets create such an experiment using the rspec below.
    13 (insert shadownet_stitch_utah.rspec here)
     10[attachment:shadownet_stitch_utah.rspec XML]
    1411
    1512If you look at this rspec, you notice that we request three raw-pc nodes and three virtual devices called emulab-bbg from the Utah Testbed. The emulab-bbg devices are vlan reservations requested for each link utilizing this emulab-bbg device with a pc node.
     
    1815
    1916use the PG script
    20 
     17{{{
    2118./createsliver -n shadow-demo -m https://www.emulab.net/protogeni/xmlrpc/cm shadownet_stitch_utah.rspec
    22 
     19}}}
    2320
    2421Save the manifest
    25 
     22{{{
    2623./sliverstatus -n shadow-demo -m https://www.emulab.net/protogeni/xmlrpc/cm until sliverstatus returns a ready state.
     24}}}
    2725
    2826Once we have a ready state, we now look at the manifest returned and note down all the "vlantag= " returned for each link
     
    3230Replace the VlanId attributes in each link with the relevant Vlan Tags and the IP addresses on the each link in the juniper section.
    3331
    34 Look at the shadownet_stitch.rspec
     32Look at the [attachment:shadownet_stitch_shadownet.rspec XML ]
    3533
    3634submit this to the shadownet CM
    37 
     35{{{
    3836./createsliver -n shadow-demo -m https://shadownet.uky.emulab.net/protogeni/xmlrpc/cm shadownet_stitch.rspec
    39 
     37}}}
    4038Save the manifest
    41 
     39{{{
    4240./sliverstatus -n shadow-demo -m https://www.emulab.net/protogeni/xmlrpc/cm until sliverstatus returns a ready state.
    43 
     41}}}
    4442
    4543Once the experiment is up and running, we have to setup routing on the routers and the pcs to talk to each other.
     
    4745The set of commands and its output for this example are shown in the files attached below.
    4846
    49 WASH_Router.output
     47[attachment:WASH_Router.output Text]
    5048KANS_Router.output
    5149SLC_Router.output