Changes between Version 5 and Version 6 of GeniNetworkStitchingConfirmationTestStatus/Utah-stitch


Ignore:
Timestamp:
06/03/15 16:28:43 (5 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniNetworkStitchingConfirmationTestStatus/Utah-stitch

    v5 v6  
    296296From NPS host ping the remote on each of the two interfaces.  Below is the ping output for the GPO site:
    297297{{{
    298 remote-execute.py IG-ST-2 -a nps-ig -m "ping 10.10.4.2 -c 60 -q ;ping 192.168.4.2 -c 60 -q"
     298$ remote-execute.py IG-ST-2 -a nps-ig -m "ping 10.10.4.2 -c 60 -q ;ping 192.168.4.2 -c 60 -q"
     2991. Find login Info for hosts in slice IG-ST-2
     300Key file [/home/lnevers/.ssh/lnevers-id_rsa] does NOT exist.
     3012. Send command 'ping 10.10.4.2 -c 60 -q ;ping 192.168.4.2 -c 60 -q' to ig-nps
     302
     303PING 10.10.4.2 (10.10.4.2) 56(84) bytes of data.
     304
     305--- 10.10.4.2 ping statistics ---
     30660 packets transmitted, 60 received, 0% packet loss, time 59099ms
     307rtt min/avg/max/mdev = 21.530/22.291/44.761/3.030 ms
     308PING 192.168.4.2 (192.168.4.2) 56(84) bytes of data.
     309
     310--- 192.168.4.2 ping statistics ---
     31160 packets transmitted, 60 received, 0% packet loss, time 59103ms
     312rtt min/avg/max/mdev = 21.435/22.187/45.988/3.109 ms
     313... Done with command 'ping 10.10.4.2 -c 60 -q ;ping 192.168.4.2 -c 60 -q' at ig-nps
     314$
    299315}}}
    300316
    301317== IG-ST-3 IG-ST-3 New Site 3 node linear topology ==
    302318
    303 Create a slice and then create slivers for the topology ''' Utah PC<->Utah DDC IG<-> Utah IG''':
     319Create a slice and then create slivers for the topology ''' Utah PG<->Utah DDC IG<-> Utah IG''':
    304320{{{
    305321$ stitcher.py createsliver IG-ST-3 IG-ST-3.rspec -o
     
    334350$ readyToLogin.py IG-ST-3 --useSliceAggregates
    335351  ....
     352ddc's geni_status is: ready
     353User lnevers logs in to ddc using:
     354        ssh -p 33850  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc4.utahddc.geniracks.net
     355...
     356ig-utah's geni_status is: ready
     357User lnevers logs in to ig-utah using:
     358        ssh -p 30522  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc3.utah.geniracks.net
     359...
     360pg-utah's geni_status is: ready
     361User lnevers logs in to pg-utah using:
     362        ssh -p 30778  -i /home/lnevers/.ssh/geni_cert_portal_key lnevers@pc430.emulab.net
    336363
    337364}}}
    338365Login to the Utah DDC IG host and pinged each remote:
    339366{{{
    340 #ping GPO IG
    341 ping 192.168.2.1 -c 60 -q
     367#ping Utah PG
     368lnevers@ddc:~$ ping 192.168.2.1 -c 20 -q
     369PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
     370
     371--- 192.168.2.1 ping statistics ---
     37220 packets transmitted, 20 received, 0% packet loss, time 19023ms
     373rtt min/avg/max/mdev = 0.899/1.191/2.267/0.259 ms
     374
    342375# Utah IG
    343 ping 192.168.4.1 -c 60 -q
     376
     377lnevers@ddc:~$ ping 192.168.4.1 -c 20 -q
     378PING 192.168.4.1 (192.168.4.1) 56(84) bytes of data.
     379
     380--- 192.168.4.1 ping statistics ---
     38120 packets transmitted, 20 received, 0% packet loss, time 19025ms
     382rtt min/avg/max/mdev = 0.982/1.108/1.847/0.175 ms
     383lnevers@ddc:~$
    344384}}}
    345385