Changes between Version 2 and Version 3 of shadownetexp23
- Timestamp:
- 11/09/12 16:19:58 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
shadownetexp23
v2 v3 3 3 This type experiment has two major limitations 4 4 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]] 5 a) 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]] 7 6 8 9 (Below stuff in shadownet_stitch.notes) 10 7 b) 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]] 11 8 12 9 Lets create such an experiment using the rspec below. 13 (insert shadownet_stitch_utah.rspec here) 10 [attachment:shadownet_stitch_utah.rspec XML] 14 11 15 12 If 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. … … 18 15 19 16 use the PG script 20 17 {{{ 21 18 ./createsliver -n shadow-demo -m https://www.emulab.net/protogeni/xmlrpc/cm shadownet_stitch_utah.rspec 22 19 }}} 23 20 24 21 Save the manifest 25 22 {{{ 26 23 ./sliverstatus -n shadow-demo -m https://www.emulab.net/protogeni/xmlrpc/cm until sliverstatus returns a ready state. 24 }}} 27 25 28 26 Once we have a ready state, we now look at the manifest returned and note down all the "vlantag= " returned for each link … … 32 30 Replace the VlanId attributes in each link with the relevant Vlan Tags and the IP addresses on the each link in the juniper section. 33 31 34 Look at the shadownet_stitch.rspec32 Look at the [attachment:shadownet_stitch_shadownet.rspec XML ] 35 33 36 34 submit this to the shadownet CM 37 35 {{{ 38 36 ./createsliver -n shadow-demo -m https://shadownet.uky.emulab.net/protogeni/xmlrpc/cm shadownet_stitch.rspec 39 37 }}} 40 38 Save the manifest 41 39 {{{ 42 40 ./sliverstatus -n shadow-demo -m https://www.emulab.net/protogeni/xmlrpc/cm until sliverstatus returns a ready state. 43 41 }}} 44 42 45 43 Once the experiment is up and running, we have to setup routing on the routers and the pcs to talk to each other. … … 47 45 The set of commands and its output for this example are shown in the files attached below. 48 46 49 WASH_Router.output 47 [attachment:WASH_Router.output Text] 50 48 KANS_Router.output 51 49 SLC_Router.output
