12

CHAPTER3

REQUIREMENT SPECIFICATION

3.1 HARDWARE REQUIREMENTS

Processor : Pentium IV 1.13GHz

Hard Disk : 40 GB
RAM : 512MB

3.2 SOFTWARE REQUIREMENTS

Operating System : FEDORA 13(LINUX)

Front end : NS2 simulator 2.35
Scripting Language :Tool Command Language

3.3 SOFTWARE DESCRIPTION

3.3.1 NS2 Overview

Network Simulator (NS2) is a discrete event driven simulator

developed at UC Berkeley. It is part of the VINT project. The goal of NS2 is to support
networking research and education. It is suitable for designing new protocols, comparing
different protocols and traffic evaluations. NS2 is developed as a collaborative environment. It
is distributed freely and open source. A large amount of institutes and people in development
and research use, maintain and develop NS2. This increases the confidence in it. Versions are
available for FreeBSD, Linux, Solaris, Windows and Mac OS X.
 13

NS2 is built using object oriented methods in C++ and OTcl (object oriented variant of
Tcl).

FIGURE 3.1 SIMPLIFIED USER’S VIEW OF NS2

can see in Fig 3.1, NS2 interprets the simulation scripts written in OTcl. A user has to set the
different components (e.g. event scheduler objects, network components libraries and setup
module libraries) up in the simulation environment. The user writes his simulation as a OTcl
script, plumbs the network components together to the complete simulation. If he needs new
network components, he is free to implement them and to set them up in his simulation as
well. The event scheduler as the other major component besides network components triggers
the events of the simulation (e.g. sends packets, starts and stops tracing). Some parts of NS2
are written in C++ for efficiency reasons. The data path (written in C++) is separated from the
control path (written in OTcl). Data path object are compiled and then made available to the
OTcl interpreter through an OTcl linkage (tclcl) which maps methods and member variables
of the C++ object to methods and variables of the linked OTcl object. The C++ objects are
controlled by OTcl objects. It is possible to add methods and member variables to a C++
linked OTcl object.
 14

3.3.1.1 FUNCTIONALITIES OF NS2.35

Functionalities for wired, wireless networks, tracing, and visualization are

available in NS2.

• Support for the wired world include

– Routing DV, LS, and PIM-SM.

– Transport protocols: TCP and UDP for unicast and SRM for multicast.

– Traffic sources: web, ftp, telnet, cbr (constant bit rate), stochastic, real audio.

– Different types of Queues: drop-tail, RED, FQ, SFQ, DRR.

– Quality of Service: Integrated Services and Differentiated Services.

– Emulation.

• Support for the wireless world include

– Ad hoc routing with different protocols, e.g. AODV, DSR, DSDV, TORA

– Wired-cum-wireless networks

– Mobile IP

– Directed diffusion

– Satellite

– Senso-MAC

– Multiple propagation models (Free space, two-ray ground, shadowing)

– Energy models
 15

• Tracing

• Visualization

– Network Animator (NAM)

– Trace Graph

• Utilities

– Mobile Movement Generator

FIGURE 3.2 OTCL AND C++: THE DUALITY

3.3.1.2 MOBILE NETWORKING IN NS2.35

 16

This section describes the wireless model that was originally ported as CMU’s

Monarch group’s mobility extension to NS2. The first section covers the original mobility

model ported from CMU/Monarch group. In this section, we cover the internals of a mobile

node, routing mechanisms and network components that are used to construct the network

stack for a mobile node. The components that are covered briefly are Channel, Network

interface, Radio propagation model, MAC protocols, Interface Queue, Link layer and Address

resolution protocol model (ARP). CMU trace support and Generation of node movement and

traffic scenario files are also covered in this section. The original CMU model allows

simulation of pure wireless LANs or multihop ad-hoc networks. Further extensions were made

to this model to allow combined simulation of wired and wireless networks. MobileIP was

also extended to the wireless model.

3.3.2THE BASIC WIRELESS MODEL IN NS

The wireless model essentially consists of the MobileNode at the core, with

additional supporting features that allows simulations of multi-hop ad-hoc networks, wireless

LANs etc. The MobileNode object is a split object. The C++ class MobileNode is derived

from parent class Node. A MobileNode thus is the basic Node object with added

functionalities of a wireless and mobile node like ability to move within a given topology,

ability to receive and transmit signals to and from a wireless channel etc. A major difference

between them, though, is that a MobileNode is not connected by means of Links to other

nodes or mobilenodes. In this section we shall describe the internals of MobileNode, its
 17

routing mechanisms, the routing protocols dsdv, aodv, tora and dsr, creation of network stack

allowing channel access in MobileNode, brief description of each stack component, trace

support and movement/traffic scenario generation for wireless simulations.

3.3.2.1MOBILE NODE: CREATING WIRELESS TOPOLOGY

Mobile Node is the basic ns Node object with added functionalities

like movement, ability to transmit and receive on a channel that allows it to be used to create

mobile, wireless simulation environments. The class Mobile Node is derived from the base

class Node. Mobile Node is a split object. The mobility features including node movement,

periodic position updates, maintaining topology boundary etc are implemented in C++ while

plumbing of network components within Mobile Node itself (like classifiers, dmux , LL, Mac,

Channel etc) have been implemented in Otcl.

Option Available Values Default

General

Address type Flat, Hierarchical Flat

MPLS ON,OFF OFF

Both Satellite and Wireless Oriented

Wired Routing ON,OFF OFF

II Type LL,LL/sat OFF

Mac Type Mac/802_11,Mac/Csma/Ca, OFF

 18

Mac/Sat/Unslotted/Aloha,Mac/Tdma

ifq Type Queue/DropTail, Queue/Droptail/PriQueue OFF

Phy Type Phy/wirelessPhy,Physat OFF

Option Available Values Default

Satellite Oriented

satNodeType Polar,Geo,Terminal,Geo-repeater OFF

downlinkBW <bandwidth value, e.g “2MB”> OFF

Wireless Oriented

Adhoc Routing DIFFUSION/RATE,DIFFUSION/PROB, OFF

DSDV,FLOODING,OMNICAST,AODV,TORA

propType Propagation/2RayGround,Propagation Shadowing OFF

propInstance Propagation/2RayGround,Propagation Shadowing OFF

antType Antenna/Omni Antenna OFF

Channel Channel/Wireless Channel,Channel/sat OFF

topoInstance <toplogy file> OFF

MobileIP ON,OFF OFF

Energy model Energy model OFF

Initial Energy <value in joules> OFF

rxPower <value in W> OFF

txPower <value in W> OFF

Idle Power <value in W> OFF

AgentTrace ON,OFF OFF

 19

routerTrace ON,OFF OFF

macTrace ON,OFF OFF

movementTrace ON,OFF OFF

Errproc UniformErrorProc OFF
FECProc ? ?
toraDebug ON,OFF OFF

TABLE 3.1: AVAILABLE OPTIONS FOR NODE CONFIGURATION