Network Simulator Version 2

1
Network SimulatorVersion 2

• George Lee

2
Overview (1)

• The LNBL Network Simulator, ns, is a simulation
  tool developed by the Network Research Group at
  the Lawrence Berkeley National Laboratory.
• Ns is an extensible, easily configured and
  programmed event-driven simulation engine, with
  support for several flavors of TCP (include SACK,
  Tahoe and Reno) and router scheduling algorithms.

3
Overview (2)

• The ns simulation description language is an
  extension of the Tool Command Language, Tcl.
• Using the ns command, a network topology is
  defined, traffic sources and sinks are
  configured, statistics are collected, and the
  simulation is invoked.
• A release of ns version 2 is available from UC
  Berkeley. Ns version 2 has a new architecture
  that uses MIT's Object Tcl instead of Tcl, and
  uses a finer grained object decomposition.

4
Useful Links

• http//www-nrg.ee.lbl.gov/ns/
• http//www.isi.edu/nsnam/ns/

5
Introduction (1)

• Ns is a discrete event simulator targeted at
  networking research.
• Ns provides substantial support for simulation of
  TCP, routing, and multicast protocols over wired
  and wireless (local and satellite) networks.

6
Introduction (2)

• Ns began as a variant of the REAL network
  simulator in 1989.
• In 1995 ns development was supported by DARPA
  through the VINT project at LBL, Xerox PARC, UCB,
  and USC/ISI.
• Currently ns development is support through DARPA
  with SAMAN and through NSF with CONSER, both in
  collaboration with other researchers including
  ACIRI.
• Ns has always included substantial contributions
  from other researchers, including wireless code
  from the UCB Daedelus and CMU Monarch projects
  and Sun Microsystems.
• For documentation on recent changes, see the
  version 2 change log.

7
Introduction (3)

• Users of ns are responsible for verifying for
  themselves that their simulations are not
  invalidated by bugs. We are working to help the
  user with this by significantly expanding and
  automating the validation tests and demos.
• Similarly, users are responsible for verifying
  for themselves that their simulations are not
  invalidated because the model implemented in the
  simulator is not the model that they were
  expecting. The ongoing Ns Manual should help in
  this process.

8
Building Ns

• The Network Simulator Building Ns
• http//www.isi.edu/nsnam/ns/ns-build.html
• Installing ns on Windows ME/2000
• http//www.public.iastate.edu/magico/nsFiles/Inst
  allNS1.html

9
The ns Manual

• The ns Manual
• http//www.isi.edu/nsnam/ns/ns-documentation.html
• The ns Manual (formerly known as ns Notes and
  Documentation) is the main source of
  documentation.
• It is available in three formats
• ns manual html format
• ns manual gzip'ed postscript format
• ns manual pdf format

10
Ns tutorial

• Ns tutorial
• http//www.isi.edu/nsnam/ns/tutorial/index.html
• Marc Greis
• The purpose of these pages is to make it easier
  for new ns users
• to use ns and nam,
• to create their own simulation scenarios for
  these tools,
• and to eventually add new functionality to ns.

11
NS by Example

• NS by Example
• http//nile.wpi.edu/NS/
• Jae Chung and Mark Claypool
• The purpose of this project is to give a new user
  some basic idea of
• how the simulator works,
• how to setup simulation networks,
• where to look for further information about
  network components in simulator codes,
• how to create new network components, etc.,
• mainly by giving simple examples and brief
  explanations based on our experiences.

12
Contributed Code

• Contributed Code
• http//www.isi.edu/nsnam/ns/ns-contributed.html
• The ns code that is maintained by users and that
  has not been incorporated into the ns
  distributions.

13
Research using Ns

• Research using Ns
• http//www.isi.edu/nsnam/ns/ns-research.html

14
The CMU Monarch Project

• The CMU Monarch Project
• http//www.monarch.cs.cmu.edu/cmu-ns.html
• The CMU Monarch Project has made substantial
  extensions to the ns-2 network simulator that
  enable it to accurately simulate mobile nodes
  connected by wireless network interfaces,
  including the ability to simulate multi-hop
  wireless ad hoc networks.