PROJECT REPORTGNS3 AS A FEASIBLE TEACHING,

TESTING AND DESIGNING TOOL FOR

NETWORK DESIGN

WINTER 2012

JAMES MAHON s00092597

SYSTEMS & NETWORKING

PRJ401

B.Sc. in Computing (SYSTEMS & NETWORKING) Level 8 Year 4

PAUL FLYNN

Chapter 1

What is Network Simulation?‘Network simulators attempt to model real world networks. The idea being that if a system can be

modeled, then features of the model can be changed and the results analyzed. As the process of

model modification is relatively cheap then a wide variety of scenarios can be analyzed at low cost

(relative to making changes to a real network).

One word of warning. Network simulators are not perfect. They will NOT perfectly model your

network. They will, however, be close enough so as to give you a meaningful insight into how your

network is working, and how changes will effect its operation.’

(Jack Hughes on Fri, 2009/02/20 - 14:15 http://www.openxtra.co.uk/articles/network-

simulation) accessed on 3/1/2012

Why should you be interested in Network Simulation?‘If you are the manager of a growing network, with ever greater demands being placed upon your

network, then network simulators are an area you should seriously consider investigating.

Making changes to your network are expensive. Mistakes can cost you a lot of money to rectify.

If you had a tool that allowed you to model your current network, then make changes to it to see

what happened. That would be useful wouldn’t it? The network simulator would remove some of

the uncertainty surrounding the changes you were making. Of course, it won’t remove all of the

uncertainty, but at least it will remove some of it.Network simulators are most useful when used to

model large networks. Modeling two machines, whilst interesting as a tutorial exercise, is probably

not worth the effort. Modeling changes to a large network however is a worthwhile activity.’

(Jack Hughes on Fri, 2009/02/20 - 14:15 http://www.openxtra.co.uk/articles/network-simulation)

accessed on 3/1/2012

CHAPTER 2

Who are the Players in the Network Simulation World?‘Network simulation has been around for a while. There are a number of players, both open source

and commercial. I don’t have any experience of the commercial tools, so I am loathe to recommend

anything I haven’t first hand experience of.

You will, of course, need relatively deep pockets to sample the delights of the commercial tools.

Though, if you have a large network, the commercial tools may well be worth the money in order to

get hold of technical support’.

(Jack Hughes on Fri, 2009/02/20 - 14:15 http://www.openxtra.co.uk/articles/network-

simulation) accessed on 3/1/2012

Open Source Network Simulation PlayersA number of open source network simulators are available like GNS3 (which this thesis concentrates on), Cisco packet tracer, NS2, SSFNet, OMNet & JSim.

GNS3

This simulator is examined in detail in this thesis and is mentioned here as a comparison to other popular open source simulators.

CISCO PACKET TRACER

Cisco packet tracer is Cisco’s easy option and is mainly used for CCNA training purposes and has

no outside connectivity .i.e being able to connect to the real internet. Packet tracer works perfectly

within its own enviroment allowing access to all its devices IOS’s so there is no need to have to get

any more software or plugins to use all its functions. Where packet tracer fails is it doesn’t feel real,

you do not have to wait for convergence and everything can be configured through a GUI interface

option although you can choose not to use it and configure normally through command line using

IOS commands as opposed to using the easy way where you can do any lab without doing any

command line configurations so you miss out on learning theses commands. The GUI should only

be available at the very beginning stage or basic networking. Packet tracer starts to get restricted

when you want to progress to CCNP labs as most of the advanced commands are not available this

is probably your best time to start to use network simulators like GNS3 which accommodate CCNP

labs. The transition from Packet Tracer to GNS3 is a steep learning curve and will mean hours of

relearning and no GUI alternative to fall back on but if persevered will allow you to progress from

Packet Tracer to GNS3. Weather you want to use Packet Tracer during your CCNA training and

then progress to GNS3 for your CCNP or are only interested in the fundamentals of network design

Cisco Packet Tracer is the perfect choice as all CCNA labs on the Cisco Academy use Packet Tracer

and Packet Tracer is well capable of catering for the entire CCNA coarse material.

NS2

‘NS2 uses scripting languages to simulate a network In order to visualise an ns simulation, you

need to have the NAM tool installed. You could either simply download the nam binary for your

platform or download the nam distribution and build in your machine. The link for getting nam

binaries as well as nam source is http://www.isi.edu/nsnam/nam.’

(http://www.isi.edu/nsnam/ns/doc/node642.html) accessed 7/1/2012

‘The NS simulator covers numerous number of applications, protocols, network types, elements and

traffic models The goal here is to learn to use the NS simulator and to understand the operations of

some of the simulated objects using simulations. Eitan Altman’s pdf provides notes for students

engineers or researchers who do not have much background in programming or who just want to

learn through simple examples on how to analyse some simulated objects. In this pdf there are

examples of tcl scripts there are also many within NS or you can get them by various tutorials all

details are in the pdf.’

http://www-sop.inria.fr/members/Eitan.Altman/COURS-NS/n3.pdf

For more information about the idea of scripting languages and split-language programming, see

Ousterhout's article in IEEE Computer details are in appendices.

SSFNet

‘The SSFNet is a mature network simulation tool started in 1998. Most SSFNet components are

licensed under the GNU General Public License. SSFNet is made up of the following components:

• Scalable Simulation Framework (SSF): a discrete event simulation of large complex systems

written in Java and C++. The SSF is open source.

• Domain Modeling Language (DML): a language for describing the model of your network

you wish to simulate. The DML is open source.

• Integrated Development Environments (IDEs): a range of tools to make the process of

building your model easier. Some of the IDEs are free, some are not.

A number of tutorials are available on the website.’

(Jack Hughes on Fri, 2009/02/20 - 14:15 http://www.openxtra.co.uk/articles/network-simulation) accessed on 3/1/2012

J-Sim

‘J-Sim is a network simulator with a Java™ based simulation engine. J-Sim can be extended using

Java classes. Models can also be constructed using Java too, though most people will probably

prefer to use one of a number of supported scripting languages to do the modeling, like Perl, TCL or

Python. A new Java based GUI tool is also available for constructing models.

Of the two tools described here, J-Sim is aimed towards people who are comfortable with their

favorite programming language. SSFNet does have a language to learn, but it is not as onerous a

task as learning a language like Perl or Python. Having said that, the GUI modeling tool available as

part of the J-Sim package looks promising. If GUI modeling tool delivers then you will be relieved

of the burden of learning a language like Perl. This will certainly lower the threshold necessary to

use the J-Sim tool’.

(Jack Hughes on Fri, 2009/02/20 - 14:15http://www.openxtra.co.uk/articles/network-simulation) accessed on 3/1/2012

Commercial Network Simulation Players

OPNET® Modeler

‘Claims to be the first commercial available network simulator tool. It was first developed at MIT.

The website does a good job of explaining the tool with a nice web-based demo. The tool looks just

the job, with a nice graphical editor for all of your network modeling needs’.

‘OPNET Modeler® accelerates the R&D process for analyzing and designing communication

networks, devices, protocols, and applications. Users can analyze simulated networks to compare

the impact of different technology designs on end-to-end behavior. Modeler incorporates a broad

suite of protocols and technologies, and includes a development environment to enable modeling of

all network types and technologies including:’

• VoIP• TCP• OSPFv3• MPLS• IPv6• Others

Create network models intuitively using a series of hierarchical editors that parallel the structure of real networks, equipment, and protocols.

Key Features

• Fastest discrete event simulation engine among leading industry solutions• Hundreds of protocol and vendor device models with source code (complete OPNET Model

Library)• Object-oriented modeling• Hierarchical modeling environment• Discrete Event, Hybrid, and optional Analytical simulation• 32-bit and 64-bit fully parallel simulation kernel• Grid computing support for distributed simulation• Optional System-in-the-Loop to interface simulations with live systems• Realistic Application Modeling and Analysis• Open interface for integrating external object files, libraries, and other simulators• Integrated, GUI-based debugging and analysis

Predict application performance using real traffic in a simulated mode.

(Jack Hughes on Fri, 2009/02/20 - 14:15http://www.openxtra.co.uk/articles/network-simulation) accessed on 3/1/2012

BOSON NETSIM

‘The Boson NetSim® Network Simulator®, which includes the Boson Router Simulator®, is

unique

compared to all others on the market because of the functionality it supports and its features.

NetSim

utilizes Boson’s proprietary Network Simulator, Router Simulator®, and EROUTER® software

technologies, along with the Boson Virtual Packet Technology® engine, to create individual

packets.

These packets are routed and switched through the simulated network, allowing NetSim to build an

appropriate virtual routing table and simulate true networking. Other simulation products on the

market do not support this level of functionality.

NetSim is a Windows®-based product that simulates a wide variety of Cisco® routers, including

the 2500 series, 2600 series, 2800 series, and 3600 series routers, as well as the Cisco Catalyst 1900

series, 2900 series, and 3500 series switches. NetSim supports multiple routing protocols, including

RIP, IGRP, EIGRP,BGP, and OSPF. It supports different LAN/WAN protocols, including

PPPCHAP, ISDN, and FrameRelay. The labs in NetSim require only the devices and functionality

included with NetSim—they do not require access to any external router or switch hardware.

NetSim supports many, but not all, of the IOS commands available on a physical router or switch.

All the commands referenced in the available labs are supported by NetSim.

Achieving Cisco CCENT, CCNA®, or CCNP® certification is the goal of many people who use

this product. The Boson NetSim covers not only the new SWITCH (642-813), TSHOOT (642-832),

and ROUTE (642-902) certifications but also the ICND1 (640-822), ICND2 (640-816), and CCNA

(640-802) certifications, among others. The included labs guide you through the configuration of

routers, switches, and workstations in a variety of scenarios. Installed labs are made available

(unlocked) depending on the activation key used to activate the product. All labs are downloaded

and kept up to date after installation regardless of the activation key used. Activation keys unlock

labs and increase the number of available commands. Beginning with the Demo version of NetSim

8, the command set is limited to those necessary to perform the steps in the lab. For example, if you

start your studies with a CCENT activation key, you will have the command set and labs available

that are necessary to study for that exam. When you are ready to study for either the CCNA or

CCNP exam, you will need to purchase a new activation key, deactivate NetSim, and then reactivate

with the new CCNA or CCNP activation key; then, more labs and a larger command set become

available.

The labs available in the Sequential lab pack when a CCENT activation key has been used to

activate NetSim 8 are shown below. A CCENT activation key also unlocks a selection of labs from

the Stand-Alone and Scenario lab packs. A small lock icon is displayed next to unavailable labs.

Higher-level activation keys allow you to work through all labs unlocked by lower level activation

keys. All labs are unlocked when a CCNP-level activation key is used.’

http://www.boson.com/network-simulator/ccnp-cisco-network-simulator?EID=DBCA3C46-

DCE2-4A93-8241-1C5F2E6FCBA3&gclid=CLTGmO6Uvq0CFQRP4Qodl1RBAg) accessed on

7/1/2012

CCNP Network Simulator & Router Simulator

NetSim for CCNP 8.0 is designed to help you learn the Cisco IOS command structure, and it

supports the technologies and skills required for the recently revised CCNP certification.

NetSim for CCNP also contains all of the NetSim for CCNA labs, which makes it the best value for

individuals studying for the CCNA and CCNP certification exams.

NetSim for CCNP includes new labs for the ROUTE, SWITCH and TSHOOT technologies. In

addition to new content, NetSim for CCNP 8.0 contains a new and improved interface that makes

completing labs, compiling new labs and designing network topologies easier than ever before. The

network topology, device consoles and lab instructions can share the screen in NetSim 8.0 with

easy-to-use panes. NetSim 8.0 also supports multiple monitors.

Everything you need to create and compile new labs – from the NetMap topology designer, to the

device configuration window, to the saving and merging of files – are all in one easily navigable

window. Completing NetSim labs and creating your own labs have never been so easy.

NetSim 8.0 minimum requirements – NetSim requires one of the following Operating Systems:

Windows 7, Windows Vista or Windows XP.

Additional Resources see appendices

NetSim for CCNP 8.0 Enhancements

• Vastly improved user interface

• External lab document viewer enables the use of multiple monitors

• Telnet mode enables the user to open a separate Telnet session for each device in the

simulated topology

• New labs supporting ROUTE, SWITCH and TSHOOT technologies

• Supports EIGRP debugging

• Improved EIGRP – less processor intensive

• Support for HSRP, MHSRP and VRRP

See a full list of supported technologies.

Boson NetSim for CCNP 8.0 Network Simulator Offers

• Hands-on experience without the hardware

• A Network Designer that supports 42 routers and 6 switches

• Up to 200 devices per network

• Virtual Packet Technology: software-created packets that are routed and switched through

the simulated network

• The ability to populate the WAN slots with a broad range of Network Modules

• A Telnet mode that allows you to configure devices in the simulated topology using the

Windows Telnet program

• The functionality of a full rack of equipment on your laptop

• Automatic lab-grading capability

• The ability to load and save your network configurations

• The ability to paste real router configurations into the devices

• The ability to configure your own ISDN and Frame Relay switch mappings

• The benefit of connecting your devices over simulated WANs without expensive ISP gear

• Support for IPv6 addressing

NetSim for CCNP 8.0 Devices

• 42 Routers (Cisco devices)

• 6 Switches (Cisco devices)

• 5 PCs: TFTP, Traffic generator, AAA Server, VPN Client, workstation

• 48 total Cisco devices

• 54 total devices

New CCNP Labs Include

• Configuring EIGRP III

• EIGRP and Frame Relay

• Influence EIGRP Path Selection

• Optimizing EIGRP

• EIGRP Authentication

• Configuring Hot Standby Router Protocol

• Configuring Virtual Router Redundancy Protocol

• Configuring Multiple Hot Standby Router Protocol

• Troubleshooting EIGRP Routing

• Troubleshooting Hot Standby Router Protocol

• Configuring Hot Standby Router Protocol (HSRP)

• Configuring Virtual Router Redundancy Protocol (VRRP)

• Configuring Multiple Hot Standby Router Protocol (MHSRP)

See a complete list of the NetSim CCNP-level labs.

CCNP Certification Revised 2010

Cisco has updated its Cisco CCNP certification, which now places a greater focus on complex

routing and switching and network troubleshooting for network engineers. This revision emphasizes

the competencies that are needed to plan, implement, and troubleshoot the routed and switched

networks of today and is designed to be more predictive of job readiness.

(http://www.boson.com/network-simulator/ccnp-cisco-network-simulator?

EID=DBCA3C46-

DCE2-4A93-8241-1C5F2E6FCBA3&gclid=CLTGmO6Uvq0CFQRP4Qodl1RBAg) accessed on

7/1/2012

How do you get Started in Network Simulation?‘A good first bet is to find yourself a spare machine somewhere. Visit the various open source tool

websites and see which suits you best. Then give it a go. Try some of the tutorials and gradually

build up your confidence.

If you find yourself in trouble, join a tool mailing list and ask away. I’m sure that you will receive a

warm welcome.

If you require phone support etc, or would like printed manuals, then you may want to move onto a

commercial tool’.

(Jack Hughes on Fri, 2009/02/20 - 14:15 http://www.openxtra.co.uk/articles/network-simulation) accessed on 3/1/2012

If Network Simulation is so good why isn’t everybody doing it?

‘Well, as ever people are so busy fighting fires that they rarely have the luxury of actually planning

things. Things are expected to be delivered now.’

‘Money is often a problem, though with so many high quality open source tools available, that

really isn’t a valid excuse. You can have a high quality network simulator for the price of a little

time installing an open source offering like SSFNet.’

‘Learning a network simulation tool, either open source or commercial is a large undertaking. In

order to justify that time you need to know that the time saved experimenting on your physical

network is longer and more expensive than the time taken to learn your chosen network simulation

tool and perform the necessary modeling.’

‘Perhaps what holds network simulation tools back is that network managers underestimate the

amount of time they spend making unnecessary changes to their physical network’.

(Jack Hughes on Fri, 2009/02/20 - 14:15 http://www.openxtra.co.uk/articles/network-simulation) accessed on 3/1/2012

CHAPTER 3

The history of GNS3 and the features in previous releases as well as the basic configuration

and startup procedures

WHAT IS GNS3

‘GNS3 is a graphical network simulator that allows simulation of complex networks. To provide

complete and accurate simulations, GNS3 is strongly linked with

• Dynamips - a Cisco IOS emulator

• Quemu - a generic and open source machine emulator and virtualiser

• Virtual Box - a free and powerful virtualisation software

GNS3 is an excellent complementary tool to real labs for network engineers, administrators and

people wanting to study for certification such Cisco CCNA, CCNP, CCIP and CCIE as well as

Juniper JNCIA, JNCIS and JNCIE.

It can also be used to experiment features of Cisco IOS, Juniper JunOS or to check configurations

that need to be deployed later on real routers.

Thanks to Virtual Box integration now even system engineers and administrators can take

advantage of GNS3 to study Redhat (RHCE, RHCT), Microsoft (MSCE, MSCA), Novell (CLP)

and many other vender certifications.

This Project is an open source free program that may be used on multiple operating systems

including Windows, Linux and Mac OSX.

FEATURES OVERVIEW

• Design of high quality and complex network topologies

• Emulation of many Cisco IOS router platforms, IPS,PIX and ASA firewalls, junOS

• Simulation of simple Ethernet, ATM and Frame Relay switches

• Connection of the simulated network to the real world

• Packet capture using Wireshark

Important notice: users have to provide their own IOS, IPS, PIX, ASA, JunOS to use GNS3.’

(http://www.gns3.net/home accessed 1/11/2011)

A LITTLE GNS3 HISTORY

‘ In the beginning (2005) there was Dynamips, a cisco router emulator written by Chistophe Fillot.

It emulates 1700, 2600, 3600, 3700 and 7200 hardware platforms, and runs standard IOS images.

You could run Dynamips from the command line with appropriate command line switches and have

an emulated Cisco router running on a PC. But not very useful, having just one router on a PC. To

get a network running, you would have to start two instances of the program with a bunch of

carefully constructed command line options. It would also make your CPU run at 100%.

Then (2006) came version 0.2.5, which made it possible to run Dynamips in “hypervisor” mode,

which allowed multiple routers to be simulated in a single instance and added an “Idle-PC” option,

which allowed you to fine tune your PCs CPU utilization. But more importantly the “hypervisor”

feature allowed Greg Anuzelli to put a front end to all those command line options with his program

called Dynagen. This is where the “.net” file format was created, and GNS3 uses the dynagen

libraries. In fact, the console dock at the bottom of the standard GNS3 screen is an adapted

Dynagen console.

Now Dynamgen was good, but maintaining your .net file was a nightmare - one single mistake in a

connection definition and the hypervisor wouldn’t start.

September 2007 saw the first release of GNS3-version 0.3. New names like Jeremy Grossmann and

Xavier Alt were added to the new fairly large co-operative of contributors. Suddenly you could drag

icons around a screen and join routers with click-and-drag options, and GNS3 would go and build

the appropriate .net file for dynagen to do its magic with dynamips which would drive the routers.

And GNS3 added some extra config to the .net file (now called topology.net by default) so it could

remember where all the objects had been placed and re-draw the screen when you loaded your

project the next time.

And in an other part of the world around 2007, Mirnshi developed a little application called VPCs

which gave us simulated PCs that could easily tie in with our Virtual GNS3 networks.

Since then, each new version of GNS3 has added functionality to the previous version to an ever

increasing grateful community of users, but still many users were/are having difficulties installing

and maintaining GNS3, especially in a Windows environment.’

(CW(RedNectar) http://rednectar.net/gns3-workbench/a-little-gns3-history/ )accessed 4/11/2011

GETTING STARTED AND INITAL SETUP (WINDOWS)

• The first thing to do is download the GNS3 software from the GNS3 website this is straight

forward enough and downloads very fast. If you are using windows download the all in one

option as this will give you all the necessary software to begin to use GNS3.

• After the download has finished double-click to start to instal the software.

• You will be presented with a setup wizard this is just a case of clicking next and agreeing to

terms.

• There are other applications that need to be installed as well these are WinPCAP this is a program

that GNS3 needs to communicate with real networks through a physical network internal

controller. The other applications are Dynamips and Qemu make sure that all the applications are

checked and then click next (fig 1)

fig 1

• When this complete GNS3 should now be able to run.

• When you first open GNS3 you are asked whether you want to start a new project or whether you

want to open an existing one make sure that the two options that ask about saving the

configuration files are ticked. This will ensure that any configurations are saved.

• The next thing to do is connect GNS3 to all of your IOS images these are not included with GNS3

and need to be obtained by the user. Cisco will only provide IOS files if the user already owns the

hardware with which the software corresponds to. You will not be able to create anything in

GNS3 without these files. If you have the IOS files you are ready to begin on the edit menu

choose IOS image and hypervisors. You will be faced with a display similar to (fig 2)

fig 2

In settings you need to click box image file and direct this to where you have stored the IOS file of

the particular router you want to work with. You do this to all the images you want to use in your

project it is a good idea to do this now but isn’t essential as you can add images as you work and

when you need them. The other choices are straight forward just make sure the platform and the

model match i.e c3600 platform would be used to run the c3640 model router. When you have

completed this task for all images click save and GNS3 will save all your images in the right

location so that the router or object you place in the topology is ready to use and the relative

software is loaded for that router or object.

• There is one thing left that is very important when setting up. Each time you add a router to your

topology right-click on the router this will list different router options and is where you will spend

a lot of time. One of these options is IDLE PC (see fig 3 )which means that when the router is not

in use that it does not use up any of the systems CPU. Click on the IDLE PC option and a scroll-

down list appears choose the first one that has a (*) see fig 5 at the beginning of a line of numbers.

fig 3

fig 3 showing the router options when you apply a right click on the router.

As you can see there are a lot of options but for now we will only look at the configure which is

where you select the interface cards from make sure you choose an adapter that has the ports that

you need see fig 4

fig 4

fig 4 This shows the available slots where you can load in your adapters this will vary and depends

on the router model this router has 4 slots and can house 4 different or the same adapters. Pull down

each slot to choose your adapter from the list.

fig 5

fig 5 Shows the IDLE PC value set up as you can see a line of numbers has been selected and at the beginning of these is an astrix (*) so this seems to be fine. click ok to set this value if there is no (*)

then pick the first line of numbers. To test the values especially if there is no (*) you can use Windows Task Manager and select the performance tab and then turn the router on by choosing the

start option from the router options. As you can see above in fig 5 the CPU usage history before IDLE PC was set which read off the scale and then after it was set which now reads 1%. This will

be vital when adding to your topology you must constantly referring to check CPU status to ensure a fast trouble free network simulation. As a teaching or testing environment this is one feature of

GNS3 that gives a real feel as apposed to a virtual feel making it a realistic representation of the

hardware that you are using within the GNS3 environment.

This concludes the initial installation, set-up and basic configuration of GNS3 and allows you to

select a router place it on the topology screen, optimise the CPU on your computer to work with the

routers within GNS3 and get the router the right adapters. You are now ready to start using GNS3

using the routers.

http://www.gns3.net/gns3-quick-start-windows accessed on 4/11/2011

How to configure a simple network lab in gns3

1. ‘Drag as many routers as u need (2 for this module) from the

nodes type into the topology workspace and configure them as

discussed in the previous section.

2. To connect the routers click on the icon and select manual

option.

3. Now left click on the router and select the interface to be

connected. and then click on other router to connect the wire.

4. Now the routers are connected to each other physically.

fig 6

5. Give each interface an ip address and subnet mask.

6. Issue an no auto summary command.

7. Give each router an appropriate protocol (must use the same) i.e. eigrp, Rip, Rip v2 or ospf

8. Advertise each network on both routers.

fig 7

Building A Simple Topology with client nodes

1. Configure and connect the routers (router1, router2) with theclouds N1, N2, N3, and N4.

2. Configure RIP protocol to enable routing between the two routers as follows: Since each router is

connected to

3 different wired Ethernet wires. We need to configure the interfaces on each router such that there

are at least 3 Fast Ethernet slots. Open telnet console session for Router 1 Answer ‘No’ for initial

configuration option.

‘>‘ is non-privileged mode

‘enable’ to enter into privileged mode ‘#’.

‘show ip int brief‘ to get the brief list of all the interfaces present on router.

‘config terminal‘ to configure the router type

‘int fa <intface_id>’ Eg. Int fa 0/0 to configure the interface IP address

‘Ip address <ip add> <subnet_mask>‘ to assign the ip.

eg. ip address 192.168.1.1 255.255.255.0

Similarly assign to all the three interfaces.

fig 8

Note: use the command

‘no shutdown‘ on all the interfaces and

‘exit‘ command to come back to the global configuration mode.

All the interfaces of both the routers must be assigned appropriate IP addresses and no shutdown

‘copy run start‘ to save the configuration

‘Router rip‘ to enable RIP routing.

‘Version 2‘ to use RIP v2

‘Network <ip address>‘ to enable rip on those particular IP configured interfaces.

Do these steps on both the routers and the routing will start. Note: you may have to set the default

gateway for the Virtual boxes to the router’s interface IP.

Note: You can also add Ethernet Switches provided in the GNS3 to build switched networks.

Thus now the Virtual boxes with different subnets are able to communicate with each other.’

(http://geexhq.com/wp-content/uploads/2009/11/simulating-network-lab.pdf) accessed on

10/12/2011

Frame relay and how to configure it within GNS3

What is frame relay

Frame relay uses virtual circuits which are provided by the service provider who will issue the

customer with a dlci number which the routers will use to transfer traffic within a frame relay cloud.

The service provider will look after the traffic that travels through the cloud i.e. bandwidth which is

agreed upon when installing the frame relay. No outside traffic can use the connection so the

customer always gets full bandwidth. the lab below shows a Head Quarters and 2 Sub Offices

which goes through the frame relay cloud this is used for long distance communication where

conventional cabling can be very expensive.

In the diagram below is the topology of the HQ with 2 sub offices the HQ can communicate directly

to the sub offices and the 2 sub offices can directly communicate with each other. Three physical

ports (1/1, 2/1 and 2/2) are used to interconnect the three routers.

Here is the commands for each router and an explanation of each command on the right

HQ EDMONTON ROUTER

router>enable moves to privileged mode

router*config t moves to global configuration mode

router(config)*host HQ sets the host name

HQ(config)*no ip domain-lookup turns off DNS queries so that spelling mistakes

mistakes do not slow you down

HQ(config)*enable secret cisco sets the encrypted password to cisco

HQ(config)*line con 0 moves to line console configuration mode

HQ(config-line)*login the user will be prompted for a password

HQ(config-line)*password class sets the console line password to class

HQ(config-line)*logging synchronous the command being entered will be appended a

new line

HQ(config-line)*exit returns to global configuration mode

HQ(config)*interface fastethernet 0/0 moves to interface configuration mode using

port fastethernet 0/0

HQ(config-if)*ip address 192.168.20.1 assigns an ip address and subnetmask

255.255.255.0

HQ(config-if)*no shut enables the interface

HQ(config-if)*interface serial 0/0/0 moves the serial interface 0/0/0 into

configuration mode

HQ(config-if)*encapsulation frame - relay turns on frame relay encapsulation

HQ(config-if)*no shut enables the interface

HQ(config-if)*interface serial 0/0/0.12 creates subinterface 12

point-to-point

HQ(config-subif)*description link to creates a locally significant description

suboffice 2 router DLSI 12 of the interface

HQ(config-subif)*ip address 192.168.1.1 assigns an ip address and subnet mask to the

255.255.255.0 subinterface 12

HQ(config-subif)*frame-relay interface-dlci assigns a DLSI number 12

12 point-to-point

HQ(config-subif)*interface serial 0/0/0.21 creates subinterface 21

HQ(config-subif)*description link to creates a locally significant description

suboffice 1 router DLSI 21 of the interface

HQ(config-subif)*ip address 192.168.3.1 assigns an ip address and subnet mask to the

255.255.255.0 subinterface 21

HQ(config-subif)*frame-relay interface-dlci assigns a DLSI number 21

21 point-to-point

HQ(config-subif)*exit returns interface to configuration mode

HQ(config-if)*exit returns to global configuration mode

HQ(config)*router eigrp 100 turns the eigrp routing process to 100

HQ(config-router)*network 192.168.1.0 advertises network 192.168.1.0 which

connects to suboffice 2

HQ(config-router)*network 192.168.3.0 advertises network 192.168.1.0 which

connects to suboffice 1

HQ(config-router)*network 192.168.20.0 advertises network 192.168.20.0 which

is directly connected to the local

fastethernet 0/0 interface

HQ(config-router)*(CTRL-Z) returns to privileged mode

HQ*copy running-config startup config saves the configuration to NVRAM

SUB OFFICE 2 WINNIPEG ROUTER

router>enable moves to privileged mode

router*config t moves to global configuration mode

router(config)*host sub2 sets the host name

sub2(config)*no ip domain-lookup turns off DNS queries so that spelling mistakes

do not slow you down

sub2(config)*enable secret cisco sets the encrypted password to cisco

sub2(config)*line con 0 moves to line console configuration mode

sub2(config-line)*login the user will be prompted for a password to access the

console port

sub2(config-line)*password class sets the console line password to class

sub2(config-line)*logging synchronous the command being entered will be appended

sub2(config-line)*exit returns to global configuration mode

sub2(config)*interface fastethernet 0/0 moves to interface configuration mode

sub2(config-if)*ip address 192.168.30.1 assigns an ip address and subnet mask

255.255.255.0

sub2(config-if)*no shut enables the interface

sub2(config-if)*interface serial 0/0/0 moves to interface configuration mode

sub2(config-if)*encapsulation turns on frame relay encapsulation

frame-relay

sub2(config-if)*no shut enables the interface

sub2(config-if)*interface serial creates subinterface 11

0/0/0.11 point-to-point

sub2(config-subif)*description link to creates a locally significant description

sub1 router DLCI 11 of the interface

sub2(config-subif)*ip address 192.168. assigns an ip address and subnet mask

1.2 255.255.255.0

sub2(config-subif)*frame-relay interface assigns a DLCI number

-dlci 11

sub2(config-subif)*interface serial 0/0.21 creates subinterface 21

point-to-point

sub2(config-subif)*description link to creates a locally significant description

sub1 router dlci 21 of the interface

sub2(config-subif)*ip address assigns an ip address and subnet mask

192.168.4.2

255.255.255.0

sub2(config-subif)*frame-relay interface assigns a DLCI number

-dlci 21

sub2(config-subif)*exit returns to interface configuration mode

sub2(config-if)*exit returns to global configuration mode

sub2(config)*router eigrp 100 turns on eigrp routing process 100

sub2(config-router)*network 192.168.1.0 advertises network 192.168.1.0 to HQ

sub2(config-router)*network 192.168.4.0 advertises network 192.168.4.0 to sub1

sub2(config-router)*network 192.168.30.0 advertises network 192.168.30.0 directly

connected to fastethernet 0/0

sub2(config-router)*CTRL Z returns directly to privileged mode

sub2*copy running-config startup config saves the configurations to NVRAM

SUB OFFICE 1 CALGARY ROUTER

router>enable moves to privileged mode

router*config t moves to global configuration mode

router(config)*host sub1 sets the host name

sub1(config)*no ip domain-lookup turns off DNS queries so that spelling mistakes

do not slow you down

sub1(config)*enable secret cisco sets the encrypted password to cisco

sub1(config)*line con 0 moves to line console configuration mode

sub1(config-line)*login the user will be prompted for a password to access the

console port

sub1(config-line)*password class sets the console line password to class

sub1(config-line)*logging synchronous the command being entered will be appended

sub1(config-line)*exit returns to global configuration mode

sub1(config)*interface fastethernet 0/0 moves to interface configuration mode

sub1(config-if)*ip address 192.168.40.1 assigns an ip address and subnet mask

255.255.255.0

sub1(config-if)*no shut enables the interface

sub1(config-if)*interface serial 0/0/0 moves to interface configuration mode

sub1(config-if)*encapsulation turns on frame relay encapsulation

frame-relay

sub1(config-if)*no shut enables the interface

sub1(config-if)*interface serial creates subinterface 11

0/0/0.11 point-to-point

sub1(config-subif)*description link to creates a locally significant description

sub1 router DLCI 11 of the interface

sub1(config-subif)*ip address 192.168. assigns an ip address and subnet mask

3.2 255.255.255.0

sub1(config-subif)*frame-relay interface assigns a DLCI number

-dlci 11

sub1(config-subif)*interface serial 0/0.12 creates subinterface 12

point-to-point

sub1(config-subif)*description link to creates a locally significant description

sub1 router dlci 12 of the interface

sub1(config-subif)*ip address assigns an ip address and subnet mask

192.168.4.1

255.255.255.0

sub1(config-subif)*frame-relay interface assigns a DLCI number

-dlci 12

sub1(config-subif)*exit returns to interface configuration mode

sub1(config-if)*exit returns to global configuration mode

sub1(config)*router eigrp 100 turns on eigrp routering process 100

sub1(config-router)*network 192.168.3.0 advertises network 192.168.3.0 to HQ

sub1(config-router)*network 192.168.4.0 advertises network 192.168.4.0 to sub1

sub1(config-router)*network 192.168.40.0 advertises network 192.168.40.0 directly

connected to fastethernet 0/0

sub1(config-router)*CTRL Z returns directly to privileged mode

sub1*copy running-config startup config saves the configurations to NVRAM

(Empson, Scott. (2010) pp261 CCNA portable command guide, second edition: Paul Boger)

CONFIGURING GNS3 TO WORK WITH ORACLE VIRTUALBOX

Connecting Virtual Machines to the routers

It’s possible to connect Virtual Machines running on VMware to be

connected to the routers. This is done using a cloud in the nodes.

With the support of Oracle VirtualBox in GNS3 we can now get a better experience while working

with GNS3. We can now add PCs to our topology with their own operating systems. To get started

we will create a virtual machine running Windows XP pro with service pack 2 .You will need to

obtain an image file of the operating system and have it stored in a location that is easy to find. Then

You need to open up VirtualBox and create a virtual machine pointing to the image of Windows XP

you have saved.

Install virtual box and create a virtual machine start by selecting new in the virtual box tool bar and

follow the wizard through the steps to install the operating system. Do this twice one for each

virtual machine this will take some time as it goes through the same procedure as installing a real

operating system on a real PC.

• When this is done and before starting up the virtual machine choose the platform from the

list

• Click settings from the toolbar

• Then choose Network

• On this option select adapter 1

• Make sure that enable network adapter is checked

• Attach to is set to Host only Adapter

• And Name is VirtualBox Host Only Ethernet Adapter

• Leave the Advanced option as it is

Next we need to configure GNS3 by

• Open a new project and save it to your working directory

• Drag and drop a cloud object into the topology area it would be a good idea to change the

cloud symbol to a PC symbol by right clicking on the cloud and selecting change symbol

and then selecting a PC symbol from the list.

• Double click on the cloud and select NIO Ethernet tab.

• Choose the VirtualBox Host-Only Network and click the add button.

Next we need to create and configure our router in GNS3.

• Drag and drop a router from our router list making sure we have the router pointing to its

image file (see earlier procedure).

• Start up the router and perform the Idle PC procedure from earlier

• Configure the interfaces on the router by applying it with the ip address of 192.168.1.1 on

the fastethernet port.

• We now have a router with a network 192.168.1.0 and 172.30.30.0 each using the .1

address as its default gateway

• Give network a /24 subnet mask

• And make sure a no shut command is applied.

• Exit the Global configuration mode and implement a show ip int brief command

• You should see that the protocol and Admin are both up

Next start up the virtual machine and configure the ip address

• Start up the virtual machine and go to the control panel

• Select Network options

• Right click on the connection

• Select properties

• Click on TCP/IP

• And enter in the following info

ip address 192.168.1.2

Subnet mask 255.255.255.0

Default gateway 192.168.1.1

• Go to gns3 and go to the cable tool bar and select manual and connect PC1 to fastethernet

port 0/0 on the router and PC2 to the fastethernet port 0/0 on the router .

• Check connectivity from PC to gateway and back again by pinging using the console of the

router and command line on each PC.

You should now have full connectivity between a virtual PC and the GNS3 Network simulator.

(http://altibiz.wordpress.com/2010/02/03/gns3-and-virtualbox/) accessed 19/11/2011

Connecting GNS3 emulated routers to physical routers

This is how you can connect emulated routers with physical routers using GNS3 and the Ethernet NIO. This is a cheap method for expanding your home networking lab. This tutorial is done using Windows but the procedure is the same for any operating systems

1. add a cloud, bind it to your NIC as an ethernet NIO, and connect it to a router. It's really that simple. I'll show a couple of screenshots though to demonstrate.

Here's the network layout:

fig 9

Here's the configuration for the cloud:

fig 10

As you can see from the prompt of GNS_R1, it can see the cisco AS2509-RJ plugged into the

Ethernet port of a laptop but any router connected to the ethernet port will show the same output:

GNS3_R1#config tEnter configuration commands, one per line. End with CNTL/Z.GNS3_R1(config)#int fast 0/0GNS3_R1(config-if)#ip address 192.168.1.3 255.255.255.0GNS3_R1(config-if)#no shutGNS3_R1#show*Mar 1 00:02:07.575: %SYS-5-CONFIG_I: Configured from console by consoleGNS3_R1#show cdp neighborsCapability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge S - Switch, H - Host, I - IGMP, r - Repeater

Device ID Local Intrfce Holdtme Capability Platform Port IDaccess Fas 0/0 127 R AS2509-RJ Eth 0GNS3_R1#ping 192.168.1.1

Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 4/36/108 ms

(http://pookey.co.uk/wordpress/archives/216-getting-real-with-gns3-connecting-to-real-networks)

accessed on 11/12/2011

GNS3 Emulating Pix Firewalls

‘GNS3 is also capable of emulating PIX firewalls. Once again, you’ll need to provide your own

PIX image. If you want to run more than a restricted license, you’ll also need to have a valid serial

number and activation keys.’

Configuring Qemuwrapper and Cisco PIX image

‘go to Preferences on the Edit menu in GNS3. Click on Qemu in the left pane. The default path to

the Qemuwrapper should be fine. You may want to specify a different working directory. Note that

Qemuwrapper is shipped with Pemu, therefore you do not need Qemu to emulate PIX.

On PIX tab, use the button next to Binary image to specify the location of your PIX operating

system image. You may also change other settings like RAM or the number of interfaces. Once you

are finished with the settings, click on Save.’

fig 11

fig 12

‘You may use the default Key and Serial number, if necessary. This will provide a restricted license

with limited features. You will need a valid serial number and activation keys to access additional

features. The graphic below on the left (fig 13) is a restricted image. Failover, VPN-DES, and

VPN-3DES-AES are disabled. You are also limited to 6 physical interfaces and 25 VLANs. The

graphic below on the right (fig 14) is unrestricted. With an unrestricted license, these features are

enabled along with support for additional interfaces and VLANs.’

fig 13 fig 14

‘If you have a serial number and valid activation keys, you may move from a restricted license to an unrestricted license. Type in the activation keys separated by commas with no spaces. Use all lower case. Be sure your serial number is converted to hexadecimal. It is usually in decimal in a show version command. Use a calculator to convert from decimal to hexadecimal if necessary.’

Using Cisco PIX

‘Click OK to return to the GNS3 main interface. Drag a PIX firewall icon from the Nodes Types

pane into the workspace. Right-click FW1 and choose Start, then right-click on FW1 again and

choose Console.

Once you console into your PIX firewall, issue a show version command. If the activation keys do

not show up properly, then issue the following command from privileged mode (enable mode):’

pixfirewall# activation-key 0x12345678 0x12345678 0x12345678 0x12345678

fig 15

‘The command is issued on one line with spaces between the activation keys. Save the

configuration using either the write command or copy run start. Stop the device and restart it.

Congratulations! Your PIX firewall is up and running.’

‘Interfaces on the PIX are Ethernet interfaces. To connect to other devices, you’ll need to use either

Ethernet or FastEthernet interfaces. You may not connect to a serial interface.’

‘You may connect to other PIX firewalls, routers, and switches. You may not connect to a cloud.

Consequently, to connect to a real network or to a Virtual PC, you’ll need to connect from the PIX

to a switch, and then from the switch to your Cloud.’

CPU usage with PIX

‘Just as with routers, CPU usage is an issue when emulating PIX firewalls on your computer. You

will note that your CPU usage is most likely 100%. There are no idle-pc values available for PIX

firewalls at this time. Instead, you may use third-party software to control your CPU usage. There

are a variety of products on the market. The one that I use for Windows is called BES and is a free

download.’

‘Complete documentation is available on the Web site along with the program download. Once you

start your PIX firewall, start BES. Click the Target button. Choose the pemu.exe process and click

the Limit this button. A confirmation screen will appear (fig 16).’

‘Click the Control button to control how much CPU limiting will be used. I’ve set mine to reduce

CPU usage by 50%. If you are running multiple firewalls, you will want to limit each one. This

program may also limit other processes running on your Windows computer.’

(http://www.gns3.net/gns3-pix-firewall-emulation) accessed on 11/12/2011

ConclusionAlthough GNS3 is quite capable of a teaching and studying tool for Cisco certification in acquiring

CCNA, CCNP and CCIE it does have its drawbacks. The main drawback of GNS3 is that the

program does not equip you with the necessary ios images. This is essential as the program is

virtually useless without these. The fact that Cisco’s own tool packet tracer is alright for CCNA

study but when it comes to CCNP and CCIE packet tracer falls with its limited functionality.

Although packet tracer does provide all the necessary ios images to run all its devices without any

external configuration to do to start building networks and also offers a GUI so that anybody can

build a network even if they have little network experience and are unfamiliar with using a

command-line interface.

Another contender in the network simulation software area is Boson this tool does everything that

GNS3 can do but provides all the ios’s needed to build any network and is the only tool that is not

free and is not cheap and costs around $180 for the CCNA certification version and $300 for the

CCNP and CCIE version. These alternative solutions though equip you with exam preparation

material and practice exams which are very extensive and will provide excellent value for money in

the long run with a pass guarantee or your money back. You can download a demo and when you

need to progress or upgrade you purchase a key or you can just go straight in and purchase the full

version either way Boson netsim provides everything needed for each Cisco exam plus a full

comprehensive exam preparation program for every stage.

GNS3 is not suited to anyone beginning building networks and a substantial knowledge is essential

even with simplest of topology designs and it can easily get very overwhelmed. The way GNS3

shines is its realism as it emulates devices exactly this is why they use the same operating systems

as the physical hardware which are only available from the manufacturer’s website. This is the

reason why these ios’s are hard to acquire because there is still licensing problems with various

manufacturer’s. GNS3 is free for anyone to use and there are no other costs involved and is a cost

effective way to study for your CCNA, CCNP or CCIE without having to buy the physical

equipment. GNS3 has a realistic feel when configuring the various devices which converge the

same as the physical equipment although can be irritating sometimes but this is true when using real

physical routers. The new features within GNS 3.07 are extensive and provide compatibility with

more network layers with the inclusion of switches, vmware, firewalls and being able to extend out

to the physical network making GNS3 more powerful.

Which ever tool you choose as they all have their good and bad points Cisco’s simple packet tracer

or the more advanced GNS3 or the expensive Boson they all do what they intend to do and provide

the user with valuable practical experience when designing or testing networks without interfering

with essential important hardware devices.

APPENDICES

GNS3

TEAM/ DEVELOPERS

• ‘Jeremy Grossmann (GPL Project Leader ), EPITECH Paris (Class of 2008), France

• Benjamin Marsili, EPITECH Paris, France

• Xavier Alt, Thammi, Luxenbourg

• Alexey Eromenko, alias “ Technologov “ from Isreal

FORMER DEVELOPERS

These people have moved on from GNS3

• David Ruiz, EPITECH Paris (class of 2008), France

• Romain Lamaison, EPITECH Paris (class of 2008), France

• Aurelien Levesque, EPITECH Paris (class of 2008), France

CONTRIBUTORS

• Fabien Le-mentec from EPITECH Paris, France

• Mike Fuszner from St. Charles Community College, Cottleville, Missouri, USA

• Greg Anuzelli from Philadelphia, Pennsylvania, USA

• Pavel Skovajsa from Slovakia

• Christophe Fillot from the University of Technology of Compiegne, France

• Jaakko Rautanen from Finland

• Leonard Bernstein from USA

• Thomas Pani

TRANSLATORS

• Erik Wenzel from Germany: German Translator (code: de)

• Huan Ji from Wuhan, China: Chinese Translator (code: cn)

• Jose Sen from Buenos Aires, Argentina: Spanish Translator (code: es)

• Mark Soe Min from Tokyo, Japan: Japanese Translator (code: jp)

• Aboulgasem Albusaifi from Tarabulus, Libya: Arabic translation (code: ar)

• Mario de Freitas Minicz from Soa Jose dos Campos, SP, Brazil: Brazillian-Portuguese translation

(code: pt_br)

• Hasan Agirol Aksoy from Antalya, Turkey: Turkish translation (code: tr)

• Ivakin Dmitriy from Moscow, Russia: Russian translation (code: ru)

• Hyeonjin Kim from Seol, Korea: Korean translation (code: kr)

• Pavel Skovajsa form Slovakia: Slovak translation (code:sk)

• Micheal Zielinski from Plock, Poland: Polish translation (code: pl)

• Veljko Dzodic: Serbian translation (code: sr)

• Abalfazl Meshki from Iran: Farsi translation (code: fa)

• Ondrej Filip: Czech translation (code: cz)

• Lyubomir Tsekov: Bulgarian translation (code: bg)

• Andrea Riela & Vincenzo Reale: Italian translation (code: it)

• Kyryl Tumanov from Kyiv, Ukraine: Ukrainian translation (code: uk)

• Romanian translation: tranzitwww (code: ro)

• Dionissys Anyfantis: Greek translation (code: gr)’

(http//:www.gns3.net/team) accessed 2/11/2011

NS2

(John Ousterhout. Scripting: Higher-level programming for the 21st century. IEEE Computer,

31(3):23-30, March 1998.)

For more information about split level programming for network simulation, see the ns paper

(Sandeep Bajaj, Lee Breslau, Deborah Estrin, Kevin Fall, Sally Floyd, Padma Haldar, Mark Handley, Ahmed Helmy, John Heidemann, Polly Huang, Satish Kumar, Steven McCanne, Reza Rejaie, Puneet Sharma, Kannan Varadhan, Ya Xu, Haobo Yu, and Daniel Zappala. Improving simulation for network research. Technical Report 99-702b, University of Southern California, March 1999. (revised September 1999).

BOSON NetSim

NetSim 8.0 User Manual (PDF)

How to compile a lab using NetSim 8.0 (PDF)

Network Simulator Product Comparison

NetSim for CCENT

NetSim for CCNA

NetSim for CCNP

Price $99 $179 $349

Labs 44 94 163

Lab Grading Function

Device Types 44 44 48

Exams Covered 1 2 6

Point-to-Point Serial

Point-to-Multi-Point serial

Crossover Cables

Straight-through Cables

ISDN (BRI)

ISDN (PRI)

Legacy DDR

Slot-based Devices with Ability to Change Modules

RIP

RIP v2

RIPng v3 for IPV6

IGRP

EIGRP

EIGRP Summarization

EIGRP Authentication

EIGRP and Wildcard Mask

VLSM

OSPF (Single Area)

OSPF (Multi-Area)

OSPF Route Summarization

OSPF Stub andTotally Stubby Areas

OSPFv3 Using IPv6 Addresses

SDM Simulation

OSPF Authentication

IPv6 Addressing

Multicasting Configuration

IS-IS

Policy Routing

Route Redistribution

BGP

AAA

DHCP

PPP

PAP

CHAP

Dialer Profiles

Low Latency Queuing

IPSEC

Site-to-Site VPNusing Preshared Keys

Custom Queuingand Compression

VLANs

VTP

Trunking

Spanning Tree

Spanning Tree Protocol(STP) Configuration

PortFast

UplinkFast

Per-VLAN Spanning Tree (PVST)

Enable Routing on Distribution Switches

Configuring QoS

VLAN Access Control Lists

Network Baseline Discovery

Troubleshooting Based on Gathered Symptoms

Troubleshooting Physicaland Data Link Layer Problems

Troubleshooting Network Layer Problems

Troubleshooting Transport and Application Layer Problems

Troubleshooting Problems at All Logical Layers

HSRP

VRRP

( http://www.boson.com/netsim-cisco-network-simulator ) accessed on 6/1/2012

OPNET MODELER

List of supported Protocols / Technologies

Standard / Specialized ModelsContributed**APPLICATIONCBRCustomDatabaseEmailFTPHTTPMOS Dejitter Buffer PrintRemote Login / TELNETSelf-Similar Traffic (RPG)VBR VoiceVoIP – SIP, RTP, H.323, AS-SIP VideoMegaco (H.248)cRTPMPEG-2SIP in the 3GPP IMSSnoopVideo On DemandSIP & MIP integration within IMSTRANSPORTTCP (ECN, Reno, New Reno, SACK, Tahoe)UDPPerformance Enhancing Proxy (PEP) Accelerator 4000 SCPS-TP (TAO)Stop-N-WaitROUTING

BGPEIGRPDistance Vector (for ATM Networks) IGRPISISOSPFOSPFv3PNNI (for ATM Networks)RIPRIPngStatic RoutesDSBMDynamic DistributedOBGP+ Static Distributed

MULTICASTINGIGMP PIM-SMStatic RP / Auto RP  NETWORKIPv4 IPv6 Juniper DiffServ WREDMobile IPv4Mobile IPv6  HSRPRSVP

ASIMultistage   Interconnection  NetworkNetwork Initiated   Handover (NIHO) REAPMPLS CSPFFast RerouteIGP Extensions (OSPF-TE / ISIS-TE)Signaling (LDP / RSVP-TE)Tunneling Over MPLS (6PE)VPN QUALITYof SERVICE802.1pCAR / PolicingCQDWFQ / CBWFQDWRR / MDRR/ MWRR

FIFOLLQ with Rate LimitPQ TOS / DSCP - based classificationWRED/ RED MACATM (including IMA)ATM Hierarchical PVP CSMA, CSMA/CA, CSMA/CDDPT / SRP Ethernet (coax, 10baseT, 100baseT,                  1000baseX, 10 Gbps)FDDIFiber ChannelFrame RelayLANELAPBLink Aggregation (including EtherChannel)SNASpanning TreeToken RingVLAN Port-based (PVSTP, MSTP, RSTP)X.25Banyan Multistage   Cell SwitchCAN CFDAMA-PBDCCPDelay-Sensitive   Polling SchemeDQDB WAN (802.6) Ethernet OAM Firewire IEEE 1394bRPR (802.17)Slotted ALOHADOCSISMedia Redundancy Protocol (MRP)TDMAN/TTC-39A(V)3 AN/TTC-39A(V)4 AN/TTC-39D AN/TTC-39E (CDS)  AN/TTC-42 AN/TTC-46 (LENS) AN/TTC-47 (NCS)  AN/TTC-48 (SENS)  DNVT DSVT ISDN VTCMedia Gateway (PSTN to VoIP, VoATM) REDCOM HDX REDCOM IGX SB-3865 

SMU STU-III Circuit SwitchingSS7PHYSICALCustom Link Models (OPNET Pipeline Stages)DSLISDNPPPSLIPSONETDVB-DAVICDVB-TInfinibandIrDAJ1850Linear LightwaveUPnPMULTIPLEXERSAN/FCC-100(V)7  AN/FCC-100(V)9  IDNX-20, IDNX-90  Promina 100   Promina 200  Promina 400  Promina 800  Promina Device Creator Promina (Ethernet/ATM) Timeplex CX-1500 Timeplex Link/2+***   ENCRYPTIONHAIPEKG-82  KG-84 KG-84A KG-84C KG-94 KG-94A  KG-175-E10 KG-175-E100 KG-194 KG-194A KIV-7 KIV-7HS  KIV-7HSA KIV-7HSB KIV-19 KIV-19A KIV-19M KG-75 KG-95-2 

KG-175 (TACLANE)  KY-57 Motorola NES Red Eagle INE 100Thales SONET Datacryptor    

Implies optional model to be purchased separately.

JCSS (formerly NETWARS) model- Restricted availability. Authorization from the US Dept. of Defense is required to obtain this model. Please contact OPNET Sales for more information.

Government-Off-The-Shelf (GOTS) model. Restricted availability. Authorization from the US Dept. of Defense is required to obtain this model. Please contact OPNET Sales for more information.**Support and advice provided by OPNET user community.***Developed by Service Organization (SPAWAR, AFCA).Wireless

Standard / Specialized Models 

Contributed**

MACWireless LAN (802.11a, b, e, g, n) WiMAX (802.16-2004 and 802.16e-2005) LTE (model development consortium)UMTS  SMART MACTDMAZigBee (802.15.4)

 WiMAX (802.16) Mesh Mode WiMedia (802.15.3b) GPRSGSMBluetoothAd hoc SMART MAC AMPSCDPDGilbert-Elliot BER Interworked WLAN_UMTSLSMF MBMS-enabled UMTS  network

MANET/ROUTINGAODVDSRGRPOLSROSPFv3TORAMobile Mesh RoutingM-TCPTDMA v2TETRAPOL Wireless MANWLAN handover modelMODULATIONBPSKCCKDPSKFSKGMSKMSKPSKQAMQPSK MOBILITY Arbitrary trajectoriesHLA mobility updatesRandom Waypoint  Mobility Pattern GeneratorsRandom DirectionPROPAGATION CCIRFree SpaceHata Longley-RiceTIREM Walfish-IkegamiRayleighRiceanTwo-RayTERRAIN  DEMDTEDOpenFlight™  ANTENNAPATTERNS Antenna Pattern – 9 vendor specific with pattern viewer and editorAntenna conversion from 2D definitions to 3DAntenna APIs for complex antenna patterns

IsotropicUMTS Cell UMTS Sector  TACTICAL RADIOSAN/ARC-114*** AN/ARC-190*** AN/ARC-204*** AN/ARC-230*** AN/PSC-5 (A,C,D) EPLRS (Discrete Event) EPLRS Falcon II Generic UHF/VHF/HF Radios    (Long range HF communication) Harris Megastar 155 Harris RF 7800w HaveQuick INC JTIDs*** JREAP Link 11 Link 16 (Discrete Event) Link 16 & JRE Gateway *** MBITR SINCGARS Waveform Translation Gateway  MULTIPLEXERSAN/GRC-226 AN/GRC-239 AN/MRC-142 AN/TRC-170(V)2*** AN/TRC-170(V)3*** SRC-57  SATELLITECAPABILITY Amplifier BandwidthAmplifier GainAmplifier Noise FigureAntenna APIs for complex antenna patternsAntenna conversion from 2D definitions to 3D Antenna Pattern – 9 standard vendor models, with pattern  viewer and editorChannel Characteristics (Bandwidth, Data Rate, Frequency, Unlimited Partitions, Signal Power, Spreading Code)Modulation Schemes – 19 standard with editor for   customizationOrbital Trajectory – 6 degreesOrbital ViewingSatellite PhaseSatellite Start / Stop timeSTK Integration – Orbital Data

AN/FSC-78 AN/GSC-39 AN/GSC-52 AN/TSC-85B AN/TSC-85C AN/TSC-93B AN/TSC-93C AN/TSC-94A AN/TSC-100A AN/TSC-152 AN/USC-59 AN/USC-60A AN/WSC-6(V)***  Bent Pipe Satellite Links CSCO Satellite node model (TSSP partial, TDM and FDMA) DSCS, CSCI DSCS Satellite node model (TSSP partial, TDMA and FDMA) FDMA Satellite (no longer partial) GBS GBS Satellite node GBS Satellite Links GBS Satellite Terminal node Generic Terminal and Space Segment JIPM (Joint IP Modem) Low Earth Orbit Satellite**Standard Tactical Entry Point Satellite IP Backbone**TCP Protocol Enhancing Proxy (PEP) Teleport TSC-94 Satellite Terminal node TSC-85 Satellite Terminal node TSSP, ETSSP, ETSSP3G (TDMA and FDMA) TSR-4 GBS UHF DAMA*** UHF DAMA Satellite System*** UHF DAMA with SRAP UHF Satellite node model (TSSP partial, TDMA and FDMA)   

Implies optional model to be purchased separately.

JCSS (formerly NETWARS) model. Restricted availability. Authorization from the US Dept. of Defense is required to obtain this model. Please contact OPNET Sales for more information.

Government-Off-The-Shelf (GOTS) model. Restricted availability. Authorization from the US Dept. of Defense is required to obtain this model. Please contact OPNET Sales for more information.**Support and advice provided by OPNET user community.***Developed by Service Organization (SPAWAR, AFCA).

 

Vendor Devices

Standard / Specialized ModelsROUTERS& SWITCHES3ComAlcatel-Lucent Avici BrocadeCabletron (now part of Siemens) CiscoCoyote PointExtremeF5FORE (now part of Ericsson)HPJuniper MotorolaNECNortelRadware (including Alteon) Any custom model using Device CreatorSERVERS AMDCompaqDell HPIBM IntelSunANTENNA AntelDapaEms  FIREWALLS Checkpoint Cisco ASA Cisco FWSM Cisco PIX Juniper NetScreen SideWinder G2 Firewall   

Implies optional model to be purchased separately.

JCSS (formerly NETWARS) model. Restricted availability. Authorization from the US Dept. of Defense is required to obtain this model. Please contact OPNET Sales for more information.

Government-Off-The-Shelf (GOTS) model.Restricted availability. Authorization from the US Dept. of Defense is required to obtain this model. Please contact OPNET Sales for more information.**Support and advice provided by OPNET user community.***Developed by Service Organization (SPAWAR, AFCA). 

Integration with 3rd Party Products

Standard / Specialized ModelsTOPOLOGY / CONFIGURATION AlterPoint Device AuthorityATM ASCII FilesCiscoWorks Network Automation   Systems (NAS)CiscoWorks LMSCisco WAN ManagerDevice Configuration FilesHP Network Node ManagerLucent Naviscore

Opsware Network Automation SystemsSMARTS In-Charge XMLTRAFFIC ASCII fileCisco NetFlow CollectorCFlowdFluke Networks OptiView ConsoleNavisXtend NetScout nGeniusSpreadsheetLOADS ASCII fileConcord eHealth (CA)HP Openview Performance InsightInfoVista ServerMRTGStatseekerXML (with topology import)SERVERS BMC Patrol PerformBMC Patrol VisualizerCA Unicenter NSMHP Openview Performance AgentHP Openview Performance ManagerNetIQ AppManager

Microsoft PerfmonXMLSATELLITE AGI STK  EXTERNAL INTERFACES Co-simSystem-in-the-Loop ETS API (External Tool Support)HLA 

BIBLIOGRAPHY

(Jack Hughes on Fri, 2009/02/20 - 14:15 http://www.openxtra.co.uk/articles/network-simulation)

accessed on 3/1/2012

(http://www.isi.edu/nsnam/ns/doc/node642.html) accessed on 7/1/2012

(http://www-sop.inria.fr/members/Eitan.Altman/COURS-NS/n3.pdf) accessed on 5/1/2012

http://www.boson.com/network-simulator/ccnp-cisco-network-simulator?EID=DBCA3C46-

DCE2-4A93-8241-1C5F2E6FCBA3&gclid=CLTGmO6Uvq0CFQRP4Qodl1RBAg) accessed on

7/1/2012

(http://www.gns3.net/home accessed 1/11/2011)

(CW(RedNectar) http://rednectar.net/gns3-workbench/a-little-gns3-history/ )accessed 4/11/2011

(http://www.gns3.net/gns3-quick-start-windows) accessed on 4/11/2011

(http://geexhq.com/wp-content/uploads/2009/11/simulating-network-lab.pdf) accessed on

10/12/2011

(Empson, Scott. (2010) pp261 CCNA portable command guide, second edition: Paul Boger)

(http://altibiz.wordpress.com/2010/02/03/gns3-and-virtualbox/) accessed 19/11/2011

(http://pookey.co.uk/wordpress/archives/216-getting-real-with-gns3-connecting-to-real-networks) accessed on 11/12/2011

(http://www.gns3.net/gns3-pix-firewall-emulation) accessed on 11/12/2011

(http//:www.gns3.net/team) accessed 2/11/2011

( http://www.boson.com/netsim-cisco-network-simulator ) accessed on 6/1/2012