Riverbed Modeler
Riverbed Modeler
Riverbed Modeler
Academic Edition:
Common procedures when using Riverbed Modeler Academic Edition
Objective
This tutorial introduces the methodologies, capabilities, and features of Riverbed Modeler
Academic Edition.
The following topics are covered:
3. This shows a list of example projects that are shipped with the software. You may use these
projects to explore different configurations.
4. From the list of example projects, scroll down and select to open the RIP project.
5. Notice that the first scenario opened after launching this project is called README. Such
scenarios are included in example projects to describe the purpose and configuration of the
project. You may double click into any of the booklet icons for more information. Note that
in you may see such README booklets in example scenarios, and these usually contain
helpful information about the scenario.
6. Now explore the other scenarios contained in this project from the Scenarios> Switch to
scenario menu option.
7. Note that you may ceate new scenarios in a project from the scenarios menu, and even
duplicate an existing scenario. Duplicating scenarios is very useful when only a small input
change is needed to run a new experiment. Hence, instead of creating a new scenario and
redeploying the network, you may simply duplicate one that is closest to what you would like
to simulate.
3. Building a topology
There are two ways to create the network topology in Modeler:
Rapid configuration
Selecting nodes from the object palette
1. Rapid Configuration is the fastest way to create a network. This can be done from the
Topology> Rapid Configuration menu. You may select the network type (e.g. star, mesh
etc.) that provides the best foundation of your intended network. After the deployment, yuu
can then fine-tune the network to represent your exact toplogy.
2. Object Palette provides all the different nodes that can be used in Modeler. Open the object
palette from the Topology> Object Palette menu.
3. Search for the appropriate node/link/utility in the object palette, or browse through the
categories.
4. You may also create custom devices using device creator if a specific device of interest does
not exist in the object palette. This can be done from the Topology> Device Creator
menu.
5. Once you have created a topology, you may then start editing the attributes of objects in your
network. To illustrate this, open the RIPv1 scenario in the RIP example project as described
in the steps from the initial sections.
6. Notice the scenario contains a well laid out network. Double click on the ReadMe icon to
understand the scenario purpose and configuration.
7. Now, confirm the basic configuration in this scenario by studying the node attributes. For
example check the IP address settings for the Central router in the WestNet subnet. Doubleclick into the WestNet subnet then right click on the router and select Edit Atrribiutes. Drill
down to the the Interface information as shown in the image below:
3. Notice that you may also create statistic reports from this window through the Reports tab.
6. Notice that you can compare results for different nodes and even projects/scenarios by
stacking them on the same plot. You may even right click on a plot to export the results to a
spreadsheet program (after clicking on show at the bottom right corner).
6. Troubleshooting tips
Once in a while things are bound to go astray during your modeling. Because of the numerous
configuration options, having a sound troubleshooting plan is very important when resolving
such problems. Some common resources when troubleshooting problems include:
1. Simulation results: The results can help understand any possible misconfigurations in
the network. For example, looking at the TCP retransmissions can help understand why
the application response times are quite high, and this might be as a result of an incorrect
bandwidth link used at some point in the topology.
2. DES Log: This is a message log that contains warnings, errors, and information
pertaining to the simulation run. It is accessible from the DES> Open DES Log menu.
This should always be among the first places to check for any hints on improper
configurations.
3. Error Log: The error log documents any warnings and errors from the kernel. These are
not project/scenario specific and could include problems such as crashes when using a
utility in the software. This can be accessed from the Help> Error Log> Open menu.
HAPPY MODELING!