Changes between Version 1 and Version 2 of GENIEducation/SampleAssignments/TcpAssignment/onepage


Ignore:
Timestamp:
08/09/13 12:23:10 (11 years ago)
Author:
epittore@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIEducation/SampleAssignments/TcpAssignment/onepage

    v1 v2  
    3232= Set Up =
    3333
    34 If you are using Portal, create a sliver with the {{{tcp-openvz}}} rspec on InstaGENI. For ExoGENI, download the rspec [http://www.gpolab.bbn.com/experiment-support/TCPExampleExperiment/tcp-pc.rspec here]
     34If you are using Portal, create a sliver with the {{{tcp-openvz}}} rspec on InstaGENI. For ExoGENI, download the rspec [http://www.gpolab.bbn.com/experiment-support/TCPExampleExperiment/tcp-pc.rspec here] and specify {{{-a eg-gpo}}} in {{{omni}}} to specify which aggregate manager to use.
     35
     36'''Note: when you try to login the nodes, you might encounter errors like the following: '''
     37{{{
     38@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
     39@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
     40@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
     41IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
     42Someone could be eavesdropping on you right now (man-in-the-middle attack)!
     43It is also possible that a host key has just been changed.
     44The fingerprint for the RSA key sent by the remote host is
     4512:3b:a0:19:db:b8:62:46:5d:a3:e2:06:27:eb:de:e2.
     46Please contact your system administrator.
     47Add correct host key in /Users/shuang/.ssh/known_hosts to get rid of this message.
     48Offending RSA key in /Users/shuang/.ssh/known_hosts:20
     49RSA host key for 192.1.242.65 has changed and you have requested strict checking.
     50Host key verification failed.
     51}}}
     52This type of error happens when you have previously logged in a machine with the same IP address and that machine happens not to be the same one as the VM you want to log in. [[BR]]
     53As a result, this error might happen a lot, especially if you have done experiments on ExoGENI before (since it always uses the same IP range for its VMs and each VM is different from each other, i.e., with different RSA keys). [[BR]]
     54In this case, simply open ''~/.ssh/known_hosts'' and remove the line corresponding to the IP address you are trying to login. In our case here, find ''192.1.242.65'' and remove that line. [[BR]]
     55'''Note that the nodes are ready to login does not mean the interfaces are up and well configured. Users may need to wait for up to 5 minutes after nodes are up. '''