Changes between Version 27 and Version 28 of GENIExperimenter/ExperimentExample-stitching


Ignore:
Timestamp:
07/18/13 14:01:10 (11 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIExperimenter/ExperimentExample-stitching

    v27 v28  
    133133 (2) Sticher.py contacts the Stitching Computation Service (SCS) and returns the list of AMs that are needed to establish the stitching path in addition to the Internet2/ION aggregate.[[BR]]
    134134 (3) Stitcher.py generates a request RSpec for each of the aggregates in the path to request both network and compute resources. [[BR]]
    135  (4) Creates sliver at each aggregate (path & end-points)
     135 (4) Creates sliver at each aggregate (path & end-points) [[BR]]
    136136 (5) Request at Internet2/ION waits for DCN circuits. If this request fails, stitcher.py will try again after 600 seconds. [[BR]]
    137137 (6) A combined manifest rspec is assembled by the stitcher.py to show all aggregates and VLANs used in the sliver.
    … …  
    327327At this point the experiment has been set up and you may determine the login information at each compute aggregate:
    328328{{{
    329 $ readyToLogin.py ig-gpo-ig-utah -a ig-gpo       
     329$ readyToLogin.py gpo2utah -a ig-gpo
    330330...
    331331server-gpo's geni_status is: ready (am_status:ready)
    332332User lnevers logs in to server-gpo using:
    333333
    334         ssh -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pcvm2-14.instageni.gpolab.bbn.com
    335 
    336 
    337 $ readyToLogin.py ig-gpo-ig-utah -a ig-utah
     334        ssh -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pcvm2-9.instageni.gpolab.bbn.com
     335
     336
     337$ readyToLogin.py gpo2utah -a ig-utah
    338338
    339339client-utah's geni_status is: ready (am_status:ready)
    340340User lnevers logs in to client-utah using:
    341         ssh -p 30522  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc1.utah.geniracks.net
     341        ssh -p 30010  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc1.utah.geniracks.net
    342342
    343343}}}
    … …  
    345345We will use the ''server-gpo'' login to determine the routable IP address that was requested for the Web Server:
    346346{{{
    347 $ ssh -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pcvm2-14.instageni.gpolab.bbn.com
     347$ ssh -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pcvm2-9.instageni.gpolab.bbn.com
    348348[lnevers@server-gpo ~]$ /sbin/ifconfig
    349 eth999    Link encap:Ethernet  HWaddr 02:1A:B9:6C:51:18 
    350           inet addr:192.1.242.151  Bcast:192.1.242.255  Mask:255.255.255.128 <==(a)
     349eth999    Link encap:Ethernet  HWaddr 02:95:5A:60:81:53 
     350          inet addr:192.1.242.150  Bcast:192.1.242.255  Mask:255.255.255.128 <==(a)
    351351          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    352           RX packets:17379 errors:0 dropped:0 overruns:0 frame:0
    353           TX packets:9372 errors:0 dropped:0 overruns:0 carrier:0
     352          RX packets:17401 errors:0 dropped:0 overruns:0 frame:0
     353          TX packets:11652 errors:0 dropped:0 overruns:0 carrier:0
    354354          collisions:0 txqueuelen:0
    355           RX bytes:25441630 (24.2 MiB)  TX bytes:509859 (497.9 KiB)
    356 
    357 eth3748   Link encap:Ethernet  HWaddr 02:73:1F:92:9B:C6 
     355          RX bytes:25455837 (24.2 MiB)  TX bytes:649907 (634.6 KiB)
     356
     357eth3748   Link encap:Ethernet  HWaddr 02:01:C4:83:9D:2B 
    358358          inet addr:192.168.4.1  Bcast:192.168.4.255  Mask:255.255.255.0
    359359          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    360           RX packets:68 errors:0 dropped:0 overruns:0 frame:0
    361           TX packets:52 errors:0 dropped:0 overruns:0 carrier:0
     360          RX packets:57977 errors:0 dropped:0 overruns:0 frame:0
     361          TX packets:32719 errors:0 dropped:0 overruns:0 carrier:0
    362362          collisions:0 txqueuelen:0
    363           RX bytes:3901 (3.8 KiB)  TX bytes:27928 (27.2 KiB)
    364 
    365 }}}
    366  (a) publically routable IP address
    367 
    368 You may also use the ''client-utah'' login to verify connectivity between to the ''server-gpo'':
    369 {{{
    370 $ ssh -p 30522  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc1.utah.geniracks.net
     363          RX bytes:83362299 (79.5 MiB)  TX bytes:1785072 (1.7 MiB)
     364
     365
     366}}}
     367 (a) publically routable IP address is 192.1.242.150
     368
     369We can now connected to the web server to verify that iperf tests were run and that client completed wget operations:
     370
     371[[Image(web-server.jpg)]]
     372
     373[[BR]]
     374
     375Select the ''' ''Web Server Statistics'' ''' link and verify that wget was sucessfull for images:
     376
     377[[Image(web-server-stats.jpg)]]
     378
     379[[BR]]
     380
     381Next, select the ''' ''Iperf Server Logs'' ''' link to verify that the iperf test completed:
     382
     383[[Image(web-server-iperf.jpg)]]
     384
     385Before starting the PingPlus portion of the experiment, verify that no information existing for PingPlus by selecting the link ''' ''Layer 2 PingPlus Statistics'' '''.
     386
     387Now we start the PingPlus experiment, by logging into the ''client-utah'' determining its dataplane MAC address and then shutting down IP on that interface:
     388{{{
     389$ ssh -p 30010  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc1.utah.geniracks.net
    371390[lnevers@client-utah ~]$ /sbin/ifconfig
    372 eth874    Link encap:Ethernet  HWaddr 02:16:D6:8B:87:01 
     391eth973    Link encap:Ethernet  HWaddr 02:B6:06:CF:92:79 
    373392          inet addr:192.168.4.2  Bcast:192.168.4.255  Mask:255.255.255.0
    374393          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    375           RX packets:55 errors:0 dropped:0 overruns:0 frame:0
    376           TX packets:260 errors:0 dropped:0 overruns:0 carrier:0
     394          RX packets:32745 errors:0 dropped:0 overruns:0 frame:0
     395          TX packets:58027 errors:0 dropped:0 overruns:0 carrier:0
    377396          collisions:0 txqueuelen:0
    378           RX bytes:3434 (3.3 KiB)  TX bytes:323831 (316.2 KiB)
    379 
    380 eth999    Link encap:Ethernet  HWaddr 02:DF:E2:D1:9E:24 
    381           inet addr:172.17.1.4  Bcast:172.31.255.255  Mask:255.240.0.0
     397          RX bytes:1761582 (1.6 MiB)  TX bytes:83465168 (79.5 MiB)
     398
     399eth999    Link encap:Ethernet  HWaddr 02:C0:05:4F:14:5E 
     400          inet addr:172.17.1.1  Bcast:172.31.255.255  Mask:255.240.0.0
    382401          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    383           RX packets:15802 errors:0 dropped:0 overruns:0 frame:0
    384           TX packets:7917 errors:0 dropped:0 overruns:0 carrier:0
     402          RX packets:16505 errors:0 dropped:0 overruns:0 frame:0
     403          TX packets:8041 errors:0 dropped:0 overruns:0 carrier:0
    385404          collisions:0 txqueuelen:0
    386           RX bytes:22849021 (21.7 MiB)  TX bytes:421874 (411.9 KiB)
    387 
    388 lo        Link encap:Local Loopback 
    389           inet addr:127.0.0.1  Mask:255.0.0.0
    390           UP LOOPBACK RUNNING  MTU:16436  Metric:1
    391           RX packets:2 errors:0 dropped:0 overruns:0 frame:0
    392           TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
    393           collisions:0 txqueuelen:0
    394           RX bytes:196 (196.0 b)  TX bytes:196 (196.0 b)
    395 
    396 [lnevers@client-utah ~]$ ping -c 5 192.168.4.1
    397 PING 192.168.4.1 (192.168.4.1) 56(84) bytes of data.
    398 64 bytes from 192.168.4.1: icmp_req=1 ttl=64 time=80.4 ms
    399 64 bytes from 192.168.4.1: icmp_req=2 ttl=64 time=80.4 ms
    400 64 bytes from 192.168.4.1: icmp_req=3 ttl=64 time=80.3 ms
    401 64 bytes from 192.168.4.1: icmp_req=4 ttl=64 time=80.3 ms
    402 64 bytes from 192.168.4.1: icmp_req=5 ttl=64 time=80.3 ms
    403 
    404 --- 192.168.4.1 ping statistics ---
    405 5 packets transmitted, 5 received, 0% packet loss, time 4001ms
    406 rtt min/avg/max/mdev = 80.376/80.395/80.436/0.180 ms
     405          RX bytes:22910002 (21.8 MiB)  TX bytes:431936 (421.8 KiB)
     406
     407[lnevers@client-utah ~]$ sudo /sbin/ifconfig eth973 0
    407408[lnevers@client-utah ~]$
    408409}}}
    409410
    410 We can now connected to the web server to verify that iperf tests were run and that client completed wget operations:
    411 
    412 [[Image(web-server.jpg)]]
    413 
    414 [[BR]]
    415 
    416 Select the ''' ''Web Server Statistics'' ''' link and verify that wget was sucessfull for images:
    417 
    418 [[Image(web-server-stats.jpg)]]
    419 
    420 [[BR]]
    421 
    422 Next, select the ''' ''Iperf Server Logs'' ''' link to verify that the iperf test completed:
    423 
    424 [[Image(web-server-iperf.jpg)]]
     411Now on the server, shutdown IP on the dataplane interface and run PingPLus:
     412{{{
     413[lnevers@server-gpo ~]$ sudo /sbin/ifconfig eth3748 0
     414[lnevers@server-gpo ~]$ sudo /local/scripts/runPingPlus.sh 02:B6:06:CF:92:79  eth3748
     415[lnevers@server-gpo ~]$
     416}}}
     417
     418Now go back to the web server and select the ''' ''Layer 2 PingPlus Statistics'' ''' link and you will find statistics:
     419
     420[[Image(web-server-pingplus.jpg)]]
     421
     422We have now completed the experiment.
    425423
    426424== 3. Finish the Stitching Experiment ==
    … …  
    430428}}}
    431429
    432 Now that the experiment is completed, we can release all resources:
     430Now that the experiment is completed, we release all resources:
    433431{{{
    434432$ stitcher.py deletesliver ig-gpo-ig-utah