= [../Setup  Understanding the AM API using Named Data Networking] = 
 	 
{{{ 
#!html 
	 	 
<div style="text-align:center; width:495px; margin-left:auto; margin-right:auto;"> 
<img id="Image-Maps_5201305222028436" src="http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/Tutorials/Graphics/Execute.jpg?format=raw" usemap="#Image-Maps_5201305222028436" border="0" width="495" height="138" alt="" /> 
<map id="_Image-Maps_5201305222028436" name="Image-Maps_5201305222028436"> 
<area shape="rect" coords="18,18,135,110" href="./Setup" alt="" title=""    /> 
<area shape="rect" coords="180,18,297,111" href="./Execute" alt="" title=""    /> 
<area shape="rect" coords="344,17,460,110" href="./Finish" alt="" title=""    /> 
<area shape="rect" coords="493,136,495,138" href="http://www.image-maps.com/index.php?aff=mapped_users_5201305222028436" alt="Image Map" title="Image Map" /> 
</map> 
<!-- Image map text links - End - --> 
 
</div> 
}}} 
 
== 4 Wait for resources to be ready == 
 
You can tell whether your nodes are ''ready'' by using a script built on `omni` called `readyToLogin`. 
 
{{{ 
#!html 
<ol type='a'> 
  <li> 
    Please use the command: 
<pre> 
readyToLogin -a AM_NICKNAME SLICE_NAME
<pre> 
where (as before) <tt>AM_NICKNAME</tt> and <tt> SLICE_NAME </tt> are your aggregate 
manager nickname and your slice name. 
  </li> 
  <li>If it reports that the sliver is not yet ready (for example, it might say that the status is "changing"), then wait a minute 
or two and try again.  Once everything is complete, <tt>readyToLogin</tt> 
will give output that should look something like this: 
<pre> 
... 
rschr's geni_status is: ready (am_status:ready)  
User example logs in to rschr using: 
        ssh  -p 32768 -i /Users/example/.ssh/geni_key_portal example@pc1.utah.geniracks.net 
User example logs in to collar using: 
        ssh -p 32769 -i /Users/example/.ssh/geni_key_portal example@pc1.utah.geniracks.net 
... 
</pre> 
 
  </li> 
</ol> 
}}} 
 
== 5 Trying out the NDN application == 
 
In this experiment, you will be able to see in-network caching in action. Our experiment consists of the following nodes: 
   * A data source node, called {{{Custodian}}} that holds data in the namespace /nytimes
   * A node, called {{{Internet Router}}} that forwards {{{Interest}}} and {{{Data}}} packets to and from the {{{Custodian}}}. 
   * A node, called {{{Campus Router}}} that forwards {{{Interest}}} and {{{Data}}} packets to and from the university nodes.
   * A principal investigator node, called {{{PI}}} and a experimenter node, called {{{Experimenter}}} that will send {{{Interest}}} requests to the {{{Custodian}}} via UDP tunnels.

 	 	 	 
Once the topology is up, logon to the {{{Custodian}}} node and restart the NDN Forwarding Daemon. 
     {{{  
     $ cd /local
     $ sudo ./install_script.sh
     }}}


=== 5.1 Run the NDN application on the entire topology === 
We are now ready to run our experiment.[[br]]
On the {{{Custodian}}} node, start the {{{producer}}} application ^([#hn note: you can try other namespaces as well])^ [[br]]
The producer application will listen for {{{Interest}}} requests of a namespace {{{-n}}} and reply with {{{Data}}} packets.
     {{{
     $ sudo python /local/producer.py -n /nytimes 
     }}}

SSH to the {{{Experimenter}}} node, and start the consumer application
     {{{
     $ sudo python /local/consumer.py -u /nytimes/science
     }}}
The {{{Interest}}} packet travels the entire topology, leaving breadcrumbs. The {{{Data}}} packet follows the breadcrumbs back to the {{{consumer}}}, leaving cached versions of the content. This is call in-network caching and it is one of the most important features in {{{Information Centric Networking (ICN)}}}
You can check this phenomenon by running the same consumer application in the {{{PI}}} node.
SSH to the {{{PI}}} node and start the consumer application
     {{{
     $ sudo python /local/consumer.py -u /nytimes/science
     }}}
This time your {{{PI}}} node gets the content back, but nothing happens on the {{{Custodian}}} because the requested content is cached in the {{{Campus Router}}} node.[[br]]
Note that the {{{Data}}} was retrieved much faster.[[br]]
You can repeat the experiment with different namespaces
     {{{ 
     $ sudo python /local/consumer.py -u /nytimes/math
     }}}
This time you see that the {{{Interest}}} request is served by the {{{Custodian}}}.
[[br]]
Feel free to explore different {{{namespaces}}}.

=== 5.2 (Optional) Visualize experiment data flows === 
   To use the GENI Desktop to visualize the data flows in your network, continue with the instructions [wiki:GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ndn/Procedure/Execute/GEMINI here]. 


---- 

= [wiki:GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ndn/Procedure/Setup Setup] = 
= [wiki:GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ndn/Procedure/Finish Next:  Finish] =