Changes between Version 34 and Version 35 of GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-ADM-1


Ignore:
Timestamp:
05/26/12 09:43:49 (7 years ago)
Author:
chaos@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-ADM-1

    v34 v35  
    55''This page is GPO's working page for performing EG-ADM-1.  It is public for informational purposes, but it is not an official status report.  See [wiki:GENIRacksHome/ExogeniRacks/AcceptanceTestStatus] for the current status of ExoGENI acceptance tests.''
    66
    7 ''Last substantive edit of this page: 2012-05-23''
     7''Last substantive edit of this page: 2012-05-26''
    88
    99== Page format ==
     
    2525|| 2C         || [[Color(orange,Blocked)]]      ||                      ||                    || blocked on 2B                                                                                                                                  ||
    2626|| 3A         || [[Color(green,Pass)]]          || 2012-05-10           ||                    ||                                                                                                                                                ||
    27 || 3B         || [[Color(#B0E0E6,Complete)]]    ||                      || exoticket:20       || (exoticket:10) [[BR]] access works properly for `xoadmins` members, but not for `bbnadmins`                                                    ||
     27|| 3B         || [[Color(#B0E0E6,Complete)]]    ||                      || exoticket:20,exoticket:32       || (exoticket:10) [[BR]] access works properly for `xoadmins` members and for `bbnadmins`; DNS from bbn-hn to switches is not defined ||
    2828|| 3C         || [[Color(green,Pass)]]          || 2012-05-10           ||                    ||                                                                                                                                                ||
    2929|| 3D         || [[Color(green,Pass)]]          || 2012-05-11           ||                    ||                                                                                                                                                ||
     
    236236
    237237In summary, all of the access works for me because i am in `xoadmins`, but Tim is not able to login because `bbnadmins` does not have access. 
     238
     239==== Results of testing step 3B: 2012-05-26 ====
     240
     241Testing assertion that exoticket:20 has been resolved, so my site admin account, `cgolubit`, should be able to run this test.
     242
     243 * Per e-mail from Chris, the 8052 is 192.168.103.2, and the 8264 is 192.168.103.4.  The 8052 also has the public IP address 192.1.242.4.
     244
     245Testing the 8052:
     246 * Login from bbn-hn to 192.168.103.2 works:
     247{{{
     248(cgolubit) bbn-hn,[~],13:18(0)$ ssh 192.168.103.2
     249The authenticity of host '192.168.103.2 (192.168.103.2)' can't be established.
     250DSA key fingerprint is 89:b6:13:30:a5:74:e3:3e:a6:aa:71:7a:91:6e:80:fd.
     251Are you sure you want to continue connecting (yes/no)? yes
     252Warning: Permanently added '192.168.103.2' (DSA) to the list of known hosts.
     253Enter radius password:
     254
     255IBM Networking Operating System RackSwitch G8052.
     256
     257
     2588052.bbn.xo>
     259}}}
     260 * Enable access is not granted, as Chris said:
     261{{{
     2628052.bbn.xo>enable
     263
     264Enable access using (oper) credentials restricted to admin accounts only.
     2658052.bbn.xo>
     266}}}
     267 * The full running-config can't be viewed in oper mode:
     268{{{
     2698052.bbn.xo>show running-config
     270                  ^
     271% Invalid input detected at '^' marker.
     2728052.bbn.xo>
     273}}}
     274 * The MAC address table can be viewed in oper mode:
     275{{{
     2768052.bbn.xo>show mac-address-table
     277Mac address Aging Time: 300
     278
     279Total number of FDB entries : 26
     280...
     281}}}
     282 * Some information about VLANs can be viewed in oper mode.  Both of these work:
     283{{{
     284show interface information
     285show vlan information
     286}}}
     287 and i believe that, between these, i can get as much information about vlan configurations of interfaces as i could from show running-config.
     288
     289Testing the 8064:
     290 * Login from bbn-hn to 192.168.103.4 works:
     291{{{
     292(cgolubit) bbn-hn,[~],13:31(255)$ ssh 192.168.103.4
     293The authenticity of host '192.168.103.4 (192.168.103.4)' can't be established.
     294DSA key fingerprint is f0:55:24:77:00:f2:5c:cd:69:86:4c:28:ac:f8:52:26.
     295Are you sure you want to continue connecting (yes/no)? yes
     296Warning: Permanently added '192.168.103.4' (DSA) to the list of known hosts.
     297Enter radius password:
     298
     299IBM Networking Operating System RackSwitch G8264.
     300
     301
     3028264.bbn.xo>
     303}}}
     304 * Entering enable mode does not work:
     305{{{
     3068264.bbn.xo>enable
     307
     308Enable access using (oper) credentials restricted to admin accounts only.
     3098264.bbn.xo>
     310}}}
     311 * Full running config cannot be viewed:
     312{{{
     3138264.bbn.xo>show running-config
     314                  ^
     315% Invalid input detected at '^' marker.
     316}}}
     317 * Mac address table (which is empty here) can be viewed:
     318{{{
     3198264.bbn.xo>show mac-address-table
     320Mac address Aging Time: 300
     321
     322FDB is empty.
     323}}}
     324 * Openflow informaton can be viewed, including DPID and controllers for an active instance:
     325{{{
     3268264.bbn.xo>show openflow 1         
     327Open Flow Instance ID: 1
     328        DataPath ID: 0x640817f4b52a00
     329...
     330Configured Controllers:
     331        IP Address: 192.168.103.10
     332                State: Active
     333                Port: 6633
     334                Retry Count: 0
     335        Configured Controller Count 1
     336}}}
     337
     338Back to control switch, looking at public IP address:
     339 * Login from capybara (BBN network) to 192.1.242.4 appears to work identically:
     340{{{
     341capybara,[~],09:35(255)$ ssh cgolubit@192.1.242.4
     342Enter radius password:
     343
     344IBM Networking Operating System RackSwitch G8052.
     345
     346
     3478052.bbn.xo>enable
     348
     349Enable access using (oper) credentials restricted to admin accounts only.
     3508052.bbn.xo>
     351}}}
     352
     353One more thing: per Wednesday's call, the switch control IPs ''should'' have the hostnames `8052.bbn.xo` and `8064.bbn.xo`, but these do not work either forward or reverse:
     354{{{
     355bbn-hn,[~],13:39(0)$ nslookup
     356> server
     357Default server: 152.54.1.66
     358Address: 152.54.1.66#53
     359Default server: 192.1.249.10
     360Address: 192.1.249.10#53
     361> 8052.bbn.xo
     362Server:         152.54.1.66
     363Address:        152.54.1.66#53
     364
     365** server can't find 8052.bbn.xo: NXDOMAIN
     366> 8064.bbn.xo
     367Server:         152.54.1.66
     368Address:        152.54.1.66#53
     369
     370** server can't find 8064.bbn.xo: NXDOMAIN
     371> 192.168.103.2
     372Server:         152.54.1.66
     373Address:        152.54.1.66#53
     374
     375** server can't find 2.103.168.192.in-addr.arpa.: NXDOMAIN
     376> 192.168.103.4
     377Server:         152.54.1.66
     378Address:        152.54.1.66#53
     379
     380** server can't find 4.103.168.192.in-addr.arpa.: NXDOMAIN
     381}}}
     382Having clarified that this should work, i'll make a ticket for it now.
    238383
    239384=== Step 3C: GPO requests access to worker nodes running under !OpenStack ===