Appendix for the Understanding the AM API using Content Centric Networking Exercise

5.2 Visualizing your Content Centric Networking (CCN) application using the GENI Desktop

These are instructions for the optional part of the Understanding the AM API using a Content Centric Networking application tutorial. Make sure you have completed the instructions at Run the CCN application before you continue.

5.2.1 Launch the GENI Desktop

  1. Find your slice in the GENI Portal and click on the GENI Desktop button

Figure 5-1 Click on the GENI Desktop button in the Slice Tools section of your Slice page.
  1. Before the GENI Desktop launches, it will ask for authorization. Follow the instructions to click on the button.

Figure 5-2 Click on the Authorize the GENI Desktop button.
  1. It will ask for you to choose your member authority.

Figure 5-3 Click on your member authority.
  1. On the next screen, choose the Add Global Node button.

Figure 5-4 Click on Add Global Node.
  1. The next screen will welcome you to the GENI Desktop. Wait until the tool is ready. This may take several minutes to complete. It should look like the image on the right when it is done.

Figure 5-5 GENI Desktop Welcome.

5.2.2 Setting up the visualization

We are now ready to graph traffic on the four links of the topology.

  1. Click on the Passive Graphs Lite in the menu that pops up.
  1. On the GEMINI Graphs menu that pops up, deselect all boxes and select linkoctets. We will be graphing the number of bytes (a.k.a octets) on the links.
  1. Select all of the links in the experiment: (1) Press the SHIFT button and then click on all of the links in turn to select them and (2) Click on Add Graphs with Title. For each link you will get a graph showing the number of octets going in and out of each interface on the link. (See figure.)
  2. You can close the GEMINI Graphs menu.

5.2.3 Visualizing your Experiment

  1. At this point you will see four graphs showing traffic on each of the four links on your experiment. The traffic you see on the links is broadcast traffic from the switch on the rack to which these nodes connect. It is not related to your experiment.
  1. Go back to the ssh window you used to log into the researcher node (a.k.a. user) when you did the CCN exercise.
  2. Use the /opt/ccnx-atmos/ program to fetch precipitation data for a time period you had not previously fetched. This is to make sure the data will be fetched from the data source (data) and not from the cache at some node. The time period must be between 1 Jan 1902 and 31 Jan 1902.
  1. Your graphs should now show traffic on the router-dsrc1 and link0 links (see example below). The graph on the left is the network being quiet, while the graph on the right shows traffic flowing. This is because the precipitation data was not cached anywhere and had to be fetched from the data source. Please take note that the graphs are not scaled for direct comparison and take careful note of whether the max Y values are in bytes or kilobytes.

  1. Fetch the same data again. Notice there is no experiment traffic on the links. This is because the data was fetched from the cache on the node user.
  1. You can investigate the CCN application further:
    1. Log into the collaborator node (user-1) to fetch data that was previously fetched by the researcher node (user). Can you tell from where the data is fetched based on the graphs?
    2. From the collaborator node fetch data that was not previously fetched by the researcher. Where did the data come from this time?

Cleaning up

Go back to the CCN exercise to free up the resources you used in this experiment.

Last modified 7 years ago Last modified on 06/16/16 17:27:31

Attachments (9)