= Stanford University Stitching Confirmation Tests = This pages capture the detailed test logs for each test defined in the [wiki:GeniNetworkStitchingConfirmationTests New Site Stitching Confirmation Tests] page. For the sites status see the [wiki:GeniNetworkStitchingConfirmationTestStatus New Site Stitching Confirmation Tests Status] page. == IG-ST-1 New Site to GPO IG topology == The Stanford site advertises the following stitching details: {{{ protogeni chainANDTree false false 2014-01-29T19:10:48Z 2014-01-29T19:10:48Z 1000000 1000000 1000 1 urn:publicid:IDN+ion.internet2.edu+interface+rtr.salt:xe-0/1/1:stanford-ig 10 1000000 1000000 1000 1 l2sc ethernet 9000 1630-1639 false }}} Experimenter may not need any of this data, but it is helpful to reference when trying to determine how many VLANs are delegated for stitching at the site or how much bandwidth can be requested. Create a slice and then create the stitched slivers with the RSpec [http://groups.geni.net/geni/browser/trunk/stitch-examples/Stanford/IG-ST-1-ion.rspec IG-ST-1-ion.rspec]: {{{ $ vi IG-ST-1-ion.rspec lnevers@sendaria:~/gcf-2.4.1/stitch-test/Stanford$ omni.py createslice IG-ST-1 14:16:27 INFO omni: Loading agg_nick_cache file '/home/lnevers/.gcf/agg_nick_cache' 14:16:27 INFO omni: Loading config file /home/lnevers/.gcf/omni_config 14:16:27 INFO omni: Using control framework portal 14:16:27 INFO omni: Created slice with Name IG-ST-1, URN urn:publicid:IDN+ch.geni.net:ln-prj+slice+IG-ST-1, Expiration 2014-02-05 19:16:27 14:16:27 INFO omni: ------------------------------------------------------------ 14:16:27 INFO omni: Completed createslice: Args: createslice IG-ST-1 Result Summary: Created slice with Name IG-ST-1, URN urn:publicid:IDN+ch.geni.net:ln-prj+slice+IG-ST-1, Expiration 2014-02-05 19:16:27 14:16:27 INFO omni: ============================================================ stitcher.py createsliver IG-ST-1 IG-ST-1-ion.rspec -o #REDO not enought raw-pc# }}} Determined login information at each Stanford and GPO aggregate: {{{ $ readyToLogin.py IG-ST-1 -a stanford-ig .... $ readyToLogin.py IG-ST-1 -a gpo-ig .... }}} == IG-ST-2 New Site to GPO IG Loop topology == Create a slice and then create the stitched slivers with the RSpec [http://groups.geni.net/geni/browser/trunk/stitch-examples/Stanford/IG-ST-2.rspec IG-ST-2.rspec]: {{{ $ omni.py createslice IG-ST-2 14:19:44 INFO omni: Loading agg_nick_cache file '/home/lnevers/.gcf/agg_nick_cache' 14:19:44 INFO omni: Loading config file /home/lnevers/.gcf/omni_config 14:19:44 INFO omni: Using control framework portal 14:19:45 INFO omni: Created slice with Name IG-ST-2, URN urn:publicid:IDN+ch.geni.net:ln-prj+slice+IG-ST-2, Expiration 2014-02-05 19:19:45 14:19:45 INFO omni: ------------------------------------------------------------ 14:19:45 INFO omni: Completed createslice: Args: createslice IG-ST-2 Result Summary: Created slice with Name IG-ST-2, URN urn:publicid:IDN+ch.geni.net:ln-prj+slice+IG-ST-2, Expiration 2014-02-05 19:19:45 14:19:45 INFO omni: ============================================================ stitcher.py createsliver IG-ST-2 IG-ST-2.rspec -o }}} Determined login information at each Stanford and GPO aggregate: {{{ $ readyToLogin.py IG-ST-2 -a stanford-ig .... $ readyToLogin.py IG-ST-2 -a gpo-ig .... }}} Login to each host and ping the remote on each of the two interfaces. Below is the ping output for the GPO site: {{{ ping 10.10.4.2 -c 60 -q ping 192.168.4.2 -c 60 -q }}}