Changes between Version 1 and Version 2 of GENIRacksHome/InstageniRacks/ConfirmationTestStatus/UKentucky


Ignore:
Timestamp:
03/07/13 16:18:59 (6 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIRacksHome/InstageniRacks/ConfirmationTestStatus/UKentucky

    v1 v2  
    1 [[PageOutline(1-2)]]
     1[[PageOutline]]
    22
    33= University of Kentucky InstaGENI Confirmation Tests =
    44
    5 For details about the tests in this page, see the '''[wiki:GENIRacksHome/InstageniRacks/SiteConfirmationTests ExoGENI Confirmation Tests]''' page.[[BR]]
     5For details about the tests in this page, see the '''[wiki:GENIRacksHome/InstageniRacks/SiteConfirmationTests InstaGENI Confirmation Tests]''' page.[[BR]]
    66For site status see the '''[wiki:GENIRacksHome/InstageniRacks/ConfirmationTestStatus InstaGENI New Site Confirmation Tests Status]''' page.
    77
     8__Note:__ Omni nick_names for site aggregate used for these tests are:
     9{{{
     10ig-uky=,http://lan.sdn.uky.edu:12369/protogeni/xmlrpc/am
     11ig-gpo=,http://instageni.gpolab.bbn.com:12369/protogeni/xmlrpc/am/2.0
     12ig-of-uky=,h:ttps://foam.instageni.northwestern.edu:3626/foam/gapi/1
     13ig-of-gpo=,https://foam.gpolab.bbn.com:3626/foam/gapi/1
     14}}}
     15
    816
    917== IG-CT-1 - Access to New Site VM resources ==
     18Got Aggregate version, which showed AM API V1, V2, and V3 are supported and V2 is default:
     19{{{
     20$ omni.py getversion -a ig-uky
     21}}}
     22
     23The InstaGENI version in" 'code_tag':'99a2b1f03656cb665918eebd2b95434a6d3e50f9'" is the same as the other two available InstaGENI site (GPO and Utah):
     24{{{
     25IG GPO:         {   'code_tag': '99a2b1f03656cb665918eebd2b95434a6d3e50f9'
     26IG Kentucky:{   'code_tag': '99a2b1f03656cb665918eebd2b95434a6d3e50f9',
     27IG Utah:        {   'code_tag': '99a2b1f03656cb665918eebd2b95434a6d3e50f9'
     28}}}
     29
     30Get list of "available" compute resources:
     31{{{
     32$ omni.py -a ig-uky listresources --available -o
     33}}}
     34
     35Verified that Advertisement RSpec only includes available resources, as requested:
     36{{{
     37$ egrep "node comp|available now" rspec-instageni-kentucky-edu-protogeniv2.xml
     38}}}
     39
     40Created a slice:
     41{{{
     42$ omni.py createslice IG-CT-1
     43}}}
     44
     45Created a 4 VMs sliver using the RSpec [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/Kentucky/IG-CT-1-uky.rspec IG-CT-1-nw.rspec]:
     46{{{
     47$ omni.py createsliver -a ig-uky IG-CT-1 IG-CT-1-uky.rspec
     48}}}
     49The following is login information for the sliver:
     50{{{
     51$ readyToLogin.py -a ig-uky IG-CT-1
     52<...>
     53
     54}}}
     55
     56=== Measurements ===
     57
     58Log into specified host and collect iperf and ping statistics. All measurements are collected over 60 seconds, using default images and default link bandwidth:
     59
     60'''Iperf InstaGENI Kentucky VM-2 to VM-1 (TCP) - TCP window size: 16.0 KB '''
     61
     62''Collected: 2013-XX-XX''
     63
     64__One Client_
     65{{{
     66
     67}}}
     68
     69__Five Clients__
     70{{{
     71
     72}}}
     73
     74__Ten Clients__
     75{{{
     76
     77}}}
     78
     79'''Iperf InstaGENI Kentucky VM-2 to the VM-1 (UDP) - 1470 byte datagrams & UDP buffer size: 136 KByte '''
     80{{{
     81
     82}}}
     83
     84'''Ping from InstaGENI Kentucky VM-2 to the VM-1 '''
     85{{{
     86
     87}}}
     88
    1089== IG-CT-2 - Access to New Site bare metal and VM resources ==
     90Create a slice:
     91{{{
     92$ omni.py createslice IG-CT-2
     93}}}
     94
     95Created a sliver with one VM and one Raw PC using RSpec [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/Kentucky/IG-CT-2-uky.rspec IG-CT-2-nw.rspec]
     96{{{
     97$ omni.py createsliver -a ig-uky IG-CT-2 IG-CT-2-uky.rspec
     98
     99
     100}}}
     101
     102Determined login information:
     103{{{
     104$ readyToLogin.py -a ig-uky IG-CT-2
     105<...>
     106
     107}}}
     108
     109
     110=== Measurements ===
     111
     112Log into specified host and collect iperf and ping statistics. All measurements are collected over 60 seconds, using default images and default link bandwidth:
     113
     114'''Iperf InstaGENI Kentucky PC to VM (TCP) - TCP window size: 16.0 KB '''
     115
     116''Collected: 2013-XX-XX''
     117
     118__One Client_
     119{{{
     120
     121}}}
     122
     123__Five Clients__
     124{{{
     125
     126}}}
     127
     128__Ten Clients__
     129{{{
     130
     131}}}
     132
     133'''Iperf InstaGENI Kentucky PC to the VM (UDP) - 1470 byte datagrams & UDP buffer size: 136 KByte '''
     134{{{
     135
     136}}}
     137
     138'''Ping from InstaGENI Kentucky PC to VM '''
     139{{{
     140
     141}}}
     142
     143
     144
     145'''Iperf InstaGENI Kentucky PC to PC (TCP) - TCP window size: 16.0 KB '''
     146
     147Even though not part of this test, ran an experiment with 2 raw pcs to capture performance between dedicated devices.
     148
     149
     150''Collected: 2013-02-20''
     151
     152__One Client__
     153{{{
     154
     155}}}
     156
     157__Five Clients__
     158{{{
     159
     160}}}
     161
     162__Ten Clients__
     163{{{
     164
     165}}}
     166
     167'''Iperf InstaGENI Kentucky PC to the PC (UDP) - 1470 byte datagrams & UDP buffer size: 136 KByte '''
     168{{{
     169
     170}}}
     171
     172'''Ping from InstaGENI Kentucky PC to PC '''
     173{{{
     174
     175}}}
     176
     177
    11178== IG-CT-3 - Multiple sites experiment  ==
     179
     180Create a slice:
     181{{{
     182$ omni.py createslice IG-CT-3
     183
     184}}}
     185
     186Create a sliver with one VM at Kentucky and one VM at GPO using RSpec [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/Kentucky/IG-CT-3-uky.rspec IG-CT-3-nw.rspec].
     187First created the InstaGENI Kentucky sliver:
     188{{{
     189$ omni.py createsliver IG-CT-3 -a ig-uky IG-CT-3-uky.rspec
     190
     191}}}
     192Then creates the InstaGENI GPO sliver:
     193{{{
     194$ omni.py createsliver IG-CT-3 -a ig-gpo IG-CT-3-uky.rspec
     195
     196}}}
     197
     198Determined login information at each Kentucky and GPO aggregate:
     199{{{
     200$ readyToLogin.py IG-CT-3 -a ig-uky
     201  ....
     202
     203$ readyToLogin.py IG-CT-3 -a ig-gpo
     204  ....
     205}}}
     206
     207=== Measurements ===
     208
     209'''Iperf InstaGENI GPO VM-2 to Kentucky VM-1 (TCP) - TCP window size: 16.0 KB '''
     210
     211''Collected: 2013-XX-XX''
     212
     213__One Client_
     214{{{
     215
     216}}}
     217
     218__Five Clients__
     219{{{
     220
     221}}}
     222
     223__Ten Clients__
     224{{{
     225
     226}}}
     227
     228'''Iperf InstaGENI GPO VM-2 to GPO VM-1 (UDP) - 1470 byte datagrams & UDP buffer size: 136 KByte '''
     229{{{
     230
     231}}}
     232
     233'''Ping from InstaGENI GPO VM-2 to the GPO VM-1 '''
     234{{{
     235
     236}}}
     237
     238
     239'''Iperf InstaGENI Kentucky VM-1 to GPO VM-2 (TCP) - TCP window size: 16.0 KB '''
     240
     241''Collected: 2013-XX-XX''
     242
     243__One Client_
     244{{{
     245
     246}}}
     247
     248__Five Clients__
     249{{{
     250
     251}}}
     252
     253__Ten Clients__
     254{{{
     255
     256}}}
     257
     258'''Iperf InstaGENI Kentucky VM-1 to GPO VM-2 (UDP) - 1470 byte datagrams & UDP buffer size: 136 KByte '''
     259{{{
     260
     261}}}
     262
     263'''Ping from InstaGENI Kentucky VM-1 to GPO VM-2 '''
     264{{{
     265
     266}}}
     267
    12268== IG-CT-4 - Multiple sites !OpenFlow experiment and interoperability ==
     269
     270This confirmation test creates a sliver at each of the following aggregates using the RSpec specified:
     271
     272 * Kentucky InstaGENI with two VMs on shared VLAN 1750 using [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/Kentucky/IG-CT-4-ig-gpo.rspec IG-CT-4-ig-gpo.rspec] RSpec.
     273 * Kentucky FOAM [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/Kentucky/IG-CT-4-openflow-ig-uky.rspec IG-CT-4-openflow-ig-nw.rspec] RSpec.
     274 * GPO InstaGENI with two VMs on shared VLAN 1750 using [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/Kentucky/IG-CT-4-ig-gpo.rspec IG-CT-4-ig-gpo.rspec] RSpec.
     275 * GPO InstaGENI FOAM [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/Kentucky/IG-CT-4-openflow-ig-gpo.rspec IG-CT-4-openflow-ig-gpo.rspec] RSpec.
     276 * GPO Site aggregate [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/Kentucky/IG-CT-4-openflow-gpo.rspec IG-CT-4-openflow-gpo.rspec] RSpec.
     277 * ProtoGENI Utah with 2 WAPG nodes located at Rutgers and using one VM on shared VLAN 1750 [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/Kentucky/IG-CT-4-rutgers-wapg-pg-utah.rspec IG-CT-4-rutgers-wapg-pg-utah.rspec].
     278 * Rutgers FOAM [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/Kentucky/IG-CT-4-openflow-rutgers.rspec IG-CT-4-openflow-rutgers.rspec].
     279 * UEN FOAM [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/Kentucky/IG-CT-4-openflow-uen.rspec IG-CT-4-openflow-uen.rspec].
     280 * RENCI ExoGENI with 2 VMs on shared VLAN 1750 [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/Kentucky/IG-CT-4 IG-CT-4-eg-renci.rspec IG-CT-4 IG-CT-4-eg-renci.rspec]
     281 * RENCI ExoGENI FOAM [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/Kentucky/IG-CT-4-openflow-eg-renci.rspec  IG-CT-4-openflow-eg-renci.rspec]
     282 * !OpenFlow Core:
     283   - NLR FOAM [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/Kentucky/IG-CT-4-openflow-nlr.rspec IG-CT-4-openflow-nlr.rspec].
     284   - Internet2 FOAM [http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral5/RSpecs/ConfirmationTests/Kentucky/IG-CT-4-openflow-internet2.rspec IG-CT-4-openflow-internet2.rspec].
     285
     286[[BR]]
     287Following is the command sequence that is executed to setup the topology for this confirmation test:
     288
     289{{{
     290# Create the slice to be used for this confirmation test:
     291$ omni.py createslice IG-CT-4
     292
     293# Create the FOAM slivers at the Internet and NLR FOAM
     294$ omni.py createsliver -a of-i2 IG-CT-4 IG-CT-4-openflow-internet2.rspec -V1
     295$ omni.py createsliver -a of-nlr IG-CT-4 IG-CT-4-openflow-nlr.rspec -V1
     296
     297# Create the slivers at InstaGENI GPO to request nodes on shared VLAN 1750
     298$ omni.py createsliver -a ig-gpo IG-CT-4 IG-CT-4-ig-gpo.rspec
     299$ omni.py createsliver -a ig-of-gpo IG-CT-4 IG-CT-4-openflow-ig-gpo.rspec -V1
     300
     301# Create the sliver at GPO Site aggregate
     302$ omni.py createsliver -a of-gpo IG-CT-4 IG-CT-4-openflow-gpo.rspec -V1
     303
     304# Create the slivers at InstaGENI Kentucky to request nodes on shared VLAN 1750
     305$ omni.py createsliver -a ig-uky IG-CT-4 IG-CT-4-ig-uky.rspec
     306$ omni.py createsliver -a ig-of-uky IG-CT-4 IG-CT-4-openflow-ig-uky.rspec
     307
     308
     309# Create the sliver at PG Utah to request one WAPG Node at Rutgers and one VM at PG Utah on shared VLAN 1750.
     310$ omni.py createsliver -a pg-utah IG-CT-4  IG-CT-4-rutgers-wapg-pg-utah.rspec
     311
     312# Create FOAM Sliver at UEN regional for path from Utah to GENI backbone
     313$ omni.py createsliver -a of-uen IG-CT-4  IG-CT-4-openflow-uen.rspec  -V1
     314
     315# Create FOAM Sliver at Rutgers FOAM for WAPG node pg51
     316$ omni.py createsliver -a of-rutgers IG-CT-4 IG-CT-4-openflow-rutgers.rspec -V1
     317
     318# Create the slivers at RENCI ExoGENI to request nodes on shared VLAN 1750
     319# to be added when ExoGENI exits maintenance
     320
     321$ omni.py createsliver -a eg-renci IG-CT-4 IG-CT-4-eg-renci.rspec
     322$ omni.py createsliver -a eg-of-renci IG-CT-4 IG-CT-4-openflow-eg-renci.rspec
     323}}}
     324
     325Determine login for each of compute resources:
     326{{{
     327$ readyToLogin.py -a ig-uky IG-CT-4
     328<...>
     329
     330$ readyToLogin.py -a ig-gpo IG-CT-4
     331<...>
     332
     333$ readyToLogin.py -a pg-utah IG-CT-4
     334<...>
     335
     336
     337$ readyToLogin.py -a eg-renci IG-CT-4
     338<...>
     339
     340}}}
     341
     342=== Measurements ===
     343This section captures measurements collected between the following endpoints:
     344{{{
     345 0. InstaGENI Kentucky VM and InstaGENI Kentucky VM
     346 1. InstaGENI Kentucky VM and InstaGENI GPO VM
     347 1a.InstaGENI GPO VM to InstaGENI Kentucky
     348 2. InstaGENI Kentucky VM and the PG Utah VM
     349 3. InstaGENI Kentucky VM and ExoGENI RENCI VM
     350 4. InstaGENI Kentucky VM and the WAPG node at Rutgers
     351}}}
     352
     3530. The measurements collected for InstaGENI Kentucky VM to the InstaGENI Kentucky VM:
     354
     355'''Iperf Kentucky GPO VM to the Kentucky GPO VM (TCP) - TCP window size: 16.0 KB '''
     356
     357''Collected: 2013-XX-XX''
     358
     359__One Client_
     360{{{
     361
     362}}}
     363
     364__Five Clients__
     365{{{
     366
     367}}}
     368
     369__Ten Clients__
     370
     371{{{
     372
     373}}}
     374
     375'''Iperf InstaGENI Kentucky VM to the InstaGENI Kentucky VM  (UDP) - 1470 byte datagrams & UDP buffer size: 136 KByte '''
     376{{{
     377
     378}}}
     379
     380'''Ping from InstaGENI Kentucky VM to the InstaGENI Kentucky VM'''
     381{{{
     382
     383}}}
     384
     385
     3861. The measurements collected for InstaGENI Kentucky VM to the InstaGENI GPO VM:
     387
     388'''Iperf InstaGENI Kentucky VM to the InstaGENI GPO VM (TCP) - TCP window size: 16.0 KB '''
     389
     390''Collected: 2013-XX-XX''
     391
     392__One Client_
     393{{{
     394
     395}}}
     396
     397__Five Clients__
     398{{{
     399
     400}}}
     401
     402__Ten Clients__
     403
     404{{{
     405
     406}}}
     407
     408'''Iperf InstaGENI Kentucky VM to the InstaGENI GPO VM  (UDP) - 1470 byte datagrams & UDP buffer size: 136 KByte '''
     409{{{
     410
     411}}}
     412
     413'''Ping from InstaGENI Kentucky VM to the InstaGENI GPO VM'''
     414{{{
     415
     416}}}
     417
     418
     4191a. The measurements collected for InstaGENI Kentucky VM to the InstaGENI GPO VM:
     420
     421''Collected: 2013-XX-XX''
     422
     423'''Iperf InstaGENI GPO VM to the InstaGENI Kentucky VM (TCP) - TCP window size: 16.0 KB '''
     424
     425__One Client_
     426{{{
     427
     428}}}
     429
     430__Five Clients__
     431{{{
     432
     433
     434}}}
     435
     436__Ten Clients__
     437
     438{{{
     439
     440}}}
     441
     442'''Iperf InstaGENI GPO VM to the InstaGENI Kentucky VM  (UDP) - 1470 byte datagrams & UDP buffer size: 136 KByte '''
     443{{{
     444
     445}}}
     446
     447'''Ping from InstaGENI GPO VM to the InstaGENI Kentucky VM'''
     448{{{
     449
     450
     451}}}
     452
     453
     454
     4552. The measurements collected for InstaGENI Kentucky VM to the PG Utah VM
     456
     457''Collected: 2013-XX-XX''
     458
     459'''Iperf InstaGENI Kentucky VM to the PG Utah VM (TCP) - TCP window size: 16.0 KB '''
     460
     461__One Client_
     462{{{
     463
     464}}}
     465
     466__Five Clients__
     467{{{
     468
     469}}}
     470
     471__Ten Clients__
     472
     473{{{
     474
     475
     476}}}
     477
     478'''Iperf InstaGENI Kentucky VM to the PG Utah VM  (UDP) - 1470 byte datagrams & UDP buffer size: 136 KByte '''
     479{{{
     480
     481}}}
     482
     483'''Ping from InstaGENI Kentucky VM to the PG Utah VM'''
     484{{{
     485
     486}}}
     487
     4883. The measurements collected for InstaGENI Kentucky VM to the ExoGENI RENCI VM:
     489
     490'''Iperf InstaGENI Kentucky VM to the ExoGENI RENCI VM (TCP) - TCP window size: 16.0 KB '''
     491
     492''Collected: 2013-XX-XX''
     493
     494__One Client_
     495{{{
     496
     497}}}
     498
     499__Five Clients__
     500{{{
     501
     502}}}
     503
     504__Ten Clients__
     505
     506{{{
     507
     508}}}
     509
     510'''Iperf InstaGENI Kentucky VM to the ExoGENI RENCI VM  (UDP) - 1470 byte datagrams & UDP buffer size: 136 KByte '''
     511{{{
     512
     513}}}
     514
     515'''Ping from InstaGENI Kentucky VM to the ExoGENI RENCI VM'''
     516{{{
     517
     518}}}
     519
     5204. The measurements collected for InstaGENI Kentucky VM to the WAPG Rutgers:
     521
     522''Collected: 2013-XX-XX''
     523
     524'''Iperf InstaGENI Kentucky VM to the WAPG Rutgers (TCP) - TCP window size: 16.0 KB '''
     525
     526__One Client_
     527{{{
     528
     529}}}
     530
     531__Five Clients__
     532{{{
     533
     534}}}
     535
     536__Ten Clients__
     537{{{
     538
     539}}}
     540
     541'''Iperf InstaGENI Kentucky VM to the WAPG Rutgers (UDP) - 1470 byte datagrams & UDP buffer size: 136 KByte '''
     542{{{
     543
     544}}}
     545
     546'''Ping from InstaGENI Kentucky VM to the WAPG Rutgers'''
     547{{{
     548
     549}}}
     550
     551
     552
     553
    13554== IG-CT-5 - Experiment Monitoring ==
     555Reviewed content of the GMOC Monitoring page for [https://gmoc-db.grnoc.iu.edu/protected-openid/index.pl?method=aggregates aggregates], but there is only a FOAM aggregate, there is no compute resources, see InstaGENI [http://groups.geni.net/instageni/ticket/94 ticket 94].
     556
     557<<< Compute resource aggregate captures to be added when instaticket:94 is resolved>>>
     558
     559The Kentucky InstaGENI FOAM resources aggregate details:
     560
     561[[Image(Kentucky-FOAMAggregate.jpg)]]
     562
     563Active !OpenFlow Slivers:
     564
     565[[Image(Kentucky-OFSlivers.jpg)]]
     566
     567List of !OpenFlow Resources in use:
     568
     569[[Image(Kentucky-OFResources.jpg)]]
     570
     571Monitoring should show Aggregate measurement for CPU utilization, Disk Utilization, Network Statistics and OF Datapath and Sliver Statistics. At the time of this test these measurements were not available.
     572
     573[[Image(Kentucky-OFMonitoring.jpg)]]
     574
     575
     576
     577
    14578== IG-CT-6 - Administrative Tests ==
     579
     580Followed instructions at [https://users.emulab.net/trac/protogeni/wiki/RackAdminAccounts Admin Accounts on InstaGeni Racks] page for account request. A local admin account was create and also had to join the ''emulab-ops'' group at https://www.instageni.kentucky.edu/joinproject.php3?target_pid=emulab-ops.   Once account was create and membership to emulab-ops was approved proceeded to execute administrative tests. 
     581
     582
     583{{{
     584LNM:~$ ssh lnevers@control.instageni.kentucky.edu
     585
     586}}}
     587
     588Also access the node via the PG Boss alias:
     589{{{
     590LNM:~$ ssh boss.instageni.kentucky.edu
     591}}}
     592
     593Further verified access by ssh from ops.instageni.gpolab.bbn.com to boss.instageni.gpolab.bbn.com, which is usually restricted for non-admin users:
     594{{{
     595LNM:~$ ssh ops.instageni.kentucky.edu
     596
     597}}}
     598From boss node accessed each of the experiment nodes that support VMs:
     599{{{
     600[lnevers@boss ~]$ for i in pc1 pc2; do ssh $i "echo -n '===> Host: ';hostname;sudo whoami;uname -a;echo"; done
     601
     602}}}
     603
     604In order to access Dedicated Nodes some experiment must be running on the raw-pc device. At the time of this capture two raw-pc nodes were in use (pcX and pcY):
     605{{{
     606[lnevers@boss ~]$ sudo ssh pcX
     607[root@pcX ~]# sudo whoami
     608root
     609[root@pcX ~]# exit
     610logout
     611Connection to pcX.instageni.kentucky.edu closed.
     612[lnevers@boss ~]$ sudo ssh pcY
     613[root@pc ~]# sudo whoami
     614root
     615[root@pc ~]#
     616}}}
     617
     618Access infrastructure Switches using documented password. First connect to the switch named procurve1 the control network switch:
     619{{{
     620[lnevers@boss ~]$ sudo more /usr/testbed/etc/switch.pswd
     621XXXXXXXXX
     622[lnevers@boss ~]$ telnet procurve1
     623
     624
     625}}}
     626
     627Connect to the switch named procurve2 the dataplane network switch via ssh using the documented password:
     628{{{
     629[lnevers@boss ~]$ sudo more /usr/testbed/etc/switch.pswd
     630xxxxxxx
     631[lnevers@boss ~]$ ssh manager@procurve2
     632}}}
     633
     634Access the FOAM VM and gather information for version
     635{{{
     636LNM:~$ ssh lnevers@foam.instageni.kentucky.edu
     637
     638sudo foamctl admin:get-version  --passwd-file=/etc/foam.passwd
     639
     640}}}
     641Check FOAM configuration for  site.admin.email, geni.site-tag, email.from settings:
     642{{{
     643foamctl config:get-value --key="site.admin.email"  --passwd-file=/etc/foam.passwd
     644
     645foamctl config:get-value --key="geni.site-tag"  --passwd-file=/etc/foam.passwd
     646
     647foamctl config:get-value --key="email.from"  --passwd-file=/etc/foam.passwd
     648
     649# check if FOAM auto-approve is on. Value 2 = auto-approve is on.
     650
     651foamctl config:get-value --key="geni.approval.approve-on-creation"  --passwd-file=/etc/foam.passwd
     652
     653}}}
     654
     655Show FOAM slivers and details for one sliver:
     656
     657{{{
     658foamctl geni:list-slivers --passwd-file=/etc/foam.passwd
     659
     660}}}
     661Access the FlowVisor VM and gather version information:
     662{{{
     663
     664ssh lnevers@flowvisor.instageni.kentucky.edu
     665}}}
     666Check the !FlowVisor version, list of devices, get details for a device, list of active slices, and details for one of the slices:
     667{{{     
     668
     669fvctl --passwd-file=/etc/flowvisor.passwd ping hello
     670
     671# Devices
     672fvctl --passwd-file=/etc/flowvisor.passwd listDevices
     673
     674fvctl --passwd-file=/etc/flowvisor.passwd getDeviceInfo 06:d6:6c:3b:e5:68:00:00
     675
     676#Slices
     677fvctl --passwd-file=/etc/flowvisor.passwd listSlices
     678
     679fvctl --passwd-file=/etc/flowvisor.passwd getSliceInfo 5c956f94-5e05-40b5-948f-34d0149d9182
     680
     681}}}
     682
     683Check the FlowVisor setting:
     684{{{
     685fvctl --passwd-file=/etc/flowvisor.passwd dumpConfig /tmp/flowvisor-config
     686more /tmp/flowvisor-config
     687
     688}}}
     689
     690
     691Verify alerts for the compute resource Aggregate Manager are being reported to the [http://monitor.gpolab.bbn.com/nagios/cgi-bin/status.cgi GPO Tango GENI Nagios monitoring] and that all alerts have status OK.
     692
     693
     694[[Image(Kentucky-nagios.jpg)]]
     695
     696Verify alerts for the FOAM Aggregate Manager are being reported to the [http://monitor.gpolab.bbn.com/nagios/cgi-bin/status.cgi GPO Tango GENI Nagios monitoring] and that all alerts have status OK.
     697
     698[[Image(Kentucky-OF-nagios.jpg)]]
     699
     700
    15701
    16702----