Out

ABSTRACT
PERFORMANCE ANALYSIS of IPv4 VERSUS IPv6 IN A SIMPLE CAMPUS

NETWORK
BY
Vinay Kumar Muniyappa
May 2012
We present in this thesis a simulation study comparing
the use of IPv4 versus IPv6 in campus networks.
The File
Transfer Protocol (FTP) has been simulated in the above

said networks to investigate IPv4 versus IPv6 throughput,
end-to-end packet delay via Ethernet connection and
response time.
Video Conferencing is also simulated in the
above mentioned network and investigation of end-to-end

delay and Packet delay variation is carried out.
The OPNET Modeler has been used to carry out the
simulation of the IPv4/IPv6 on simple campus networks.
The
results obtained from OPNET simulation of FTP show that an

IPv4 network gives a better throughput than IPv6 network.
The IPv4 network has more delay and the IPv6 network shows
better response time.
Similarly results obtained from the

1
OPNET simulation of video conferencing show that

variation in packet delay for IPv6 networks is larger and
the packet end-to-end delay is larger for IPv4 networks.
Interestingly, even though IPv4 and IPv6 networks show
variations in their performance, the differences are quite
small, and for typical users may be insignificant.
PERFORMANCE ANALYSIS of IPv4 VERSUS IPv6 IN A SIMPLE CAMPUS
NETWORK
A THESIS
Presented to the Department of Computer Engineering
and Computer Science
California State University, Long Beach
In Partial Fulfillment
of the Requirements for the Degree
Master of Science in Computer Science
Option in Computer Science
Committee Members:
Tracy Bradley Maples, Ph.D. (Chair)
Burkhard Englert, Ph.D.
Shui Lam, Ph.D.
College Designee:
Burkhard Englert, Ph.D.
By Vinay Kumar Muniyappa

B.E., 2006, Visvesvaraya Technological University
May 2012
UMI Number: 1517745
All rights reserved

INFORMATION TO ALL USERS
The quality of this reproduction is dependent on the quality of the copy submitted.
In the unlikely event that the author did not send a complete manuscript
and there are missing pages, these will be noted. Also, if material had to be removed,
a note will indicate the deletion.
UMI'
Dissertation Publishing
UMI 1517745
Copyright 2012 by ProQuest LLC.
All rights reserved. This edition of the work is protected against
unauthorized copying under Title 17, United States Code.
uest
ProQuest LLC.
789 East Eisenhower Parkway
P.O. Box 1346
Ann Arbor, Ml 48106 - 1346
ACKNOWLEDGEMENTS
I would like to express my sincere gratitude to my
thesis chair Dr Tracy Bradley Maples for her immense
knowledge, guidance, patience and encouragement that took
me in the precise direction and kept me motivated
throughout the completion of this thesis.
I am sincerely thankful to my thesis committee members
Dr Shui Lam and Dr Burkhard Englert for their kind support
and valuable time.
I am very grateful towards my parents V Muniyappa, N
Lakshmi Devi and my sister Reshma B M for their continuous
love, support and being there for me throughout my life.
My sincere thanks go to Aditi Bhatnagar, Ankush Dongre,
Anirudha Mulik, Ajay Srivastava, Brianna Huntsinger,
Darshan Ananadappa Dimplu, Frank Homsany, Geethma, Krishna
Chaitanya, Kiran Muniswamappa, Jayanth Raghuram, Rohit
Gowda, Naveen Mylarappa, Shraddha Salvi, Joycee Fernandes,
Sandesh Jayram, Surendra reddy, Bhargav Narayan, Sugandhar
Babu, Vikram Rajshekar, Sethil Rajamani, Amreesh, Sunil
Shivamallu, Arvind Pal Singh, Saketh Peri, Sai Raghuveer,

Aswin Raghavan and all my roommates and all my friends
whose name I am missing here.
Special thanks to Jon Lee and Kishore Murarka for
their support.
I am thankful to Bob Weaver and all the staff members
of Facility Services for their support during my stay in
California State University, Long Beach.
Last but not the least, I would like to dedicate this
thesis to MILO who had been the best part of my life.
iv
TABLE OF CONTENTS
Page
ACKNOWLEDGEMENTS
iii
LIST OF FIGURES
vii
CHAPTER
1. INTRODUCTION
IPv4
IPv6
5
6
2. IPv4 VERSUS IPv6
IPV4 Packet and Field Descriptions

IPv6 Packet and Field Descriptions
Advantages of IPv6 over IPv4
3. NETWORK MODEL
8
11
14
20
Simple Network
Campus Network
21
21
4. INTRODUCTION TO OPNET
26
Workflow of OPNET
38
5. SIMULATION RESULTS
41
Simulation of IPv4 and IPv6 Networks with FTP

Traffic
Simulation of IPv4 and IPv6 Networks with
Video Conferencing Having FTP and
Database as Background Traffic
Simple Network IPv4 and IPv6 Throughput
v
41
41
42
Page
CHAPTER
Simple Network IPv4/IPv6 Throughput Packets
per Second
Simple Network IPv4/IPv6 Ethernet Delay
Simple Network IPv4/IPv6 Response Time
Campus Network IPv4/IPv6 Throughput
Campus Network IPv4/IPv6 Throughput Packets
Per Second
Campus Network IPv4/IPv6 Ethernet Delay
Campus Network IPv4/IPv6 Response Time
Simple Network IPv4/IPv6 Packet Delay
Variation without Background Traffic
Simple Network IPv4/IPv6 Packet End to End
Delay without Background Traffic
Simple Network IPv4/IPv6 Packet Delay
Variation with Background traffic
Simple Network IPv4/IPv6 Packet End to End
Delay with Background Traffic
Campus Network IPv4/IPv6 Packet Delay
Variation without Background Traffic
Campus Network IPv4/IPv6 Packet End to End
Delay without Background Traffic
Campus Network IPv4/IPv6 Packet Delay
Variation with Background Traffic
Campus Network IPv4/IPv6 Packet End to End
Delay with Background Traffic
6. CONCLUSION
43
44
46
47
47
49
49
49
51
51
52
53
54
55
57
58
APPENDICES
61
A. CONFIGURING FTP IN OPNET MODELER
62
B. CONFIGURING VIDEO CONFERENCING WITH BACKGROUND

TRAFFIC IN OPNET MODELLER
85
REFERENCES
92
vi
LIST OF FIGURES
FIGURE
Page
I. IPv4 packet format
2. IPv6 packet format
12
3. Simple network
22
4. Campus network
23
5. Node editor
28
6. Process editor
29
7. Simulation sequence editor
31
8. Analysis tool
31
9. Project editor workspace
32
10. Menu bar
33
II. Shortcut menu
36
12. Status message bar
38
13. OPNET work flow
39
14. IPv4 vs. IPv6 throughput in simple network
42
15. IPv4 vs. IPv6 packet throughput in simple

network
43
16. IPv4 vs. IPv6 Ethernet delay in simple network
44
17. IPv4 vs. IPv6 throughput in campus network
45
vii
FIGURE
Page
18. IPv4 vs. IPv6 throughput in campus network
46
19. IPv4 vs. IPv6 packet throughput in campus

network
48
20. IPv4 vs. IPv6 Ethernet delay in campus

network
48
21. IPv4 vs. IPv6 response time in campus network
50
22. Packet delay variation in seconds without

background traffic in the simple network
50
23 . Packet end to end delay in seconds without

background traffic in the simple network
52
24. Packet delay variation in seconds with

background traffic in simple network
53
25. Packet end-to-end delay in seconds with

background traffic in simple network
54
26. Packet delay variation in seconds without

background traffic in Campus network
55
27. Packet end-to-end delay in seconds without

background traffic in campus network
56
28. Packet delay variation in seconds with

56
29. Packet end-to-end delay in seconds with

57
30. Object palette
63
31. Experimental campus network
64
32. Application configuration attributes
66
33. FTP attribute and values table
67
viii
FIGURE
Page
34. Profile definition attributes
68
35. FTP attributes
69
36. Server configuration attributes
70
37. FTP service activation
71
38. Client configuration attribute
72
39. Application destination preferences
73
40. Actual name table
74
41. Client application supported profile
74
42. Client and server interface information table
75
43. IPv6 configuration table........
76
44. Global address table
77
45. TCP parameters
77
46. Bridge parameter table
78
47. Configuring performance metrics for IP cloud
79
48. IP cloud IPv6 interface information table
80
49. IP processing information table
82
50. IP interface information of IPv6 router (CSULB)
82
51. IP interface information of IPv4 router (CSULB)
83
52. Simple network configured with video
86
ix
FIGURE
Page
53 . Application definition with 3 applications

video, ftp and database
87
54. Video conferencing attributes
88
55. FTP attributes
89
56. Database attributes
89
57. Profile configuration
90
CHAPTER 1
INTRODUCTION
The Internet Protocol (IP) is the primary protocol
used for relaying the network packets from source to
destination through the Internet.
It was initially
designed in 1974 by Vint Cerf and Bob Kahn to connect

systems that are in different geographical locations [1].
The term "Internet," simply means Internetwork, that is, a
connection between multiple networks. During the early
stages of development, this protocol was used only by the
military and research universities, but gradually,
computers from companies and additional universities were
added.
Today, much of the world's population is becoming
more connected to and reliant on the Internet.

Internet Protocol is the backbone of the Internet.
It
specifies how independent networks can work together to

form a global network.
Each of the hosts connected to the
Internet has an associated IP address.

exchanged between these hosts.
Packets are
A source and a destination
IP address are assigned with in a packet and forwarded into

1
the network.
When packets are sent to a host, which is not
located within the same network as the source host,

networking devices such as routers, are used to receive
packets from the source host and forward it one step closer
to the location of the network where the destination host
resides [2].
The concept of forwarding packets arrived as a new
idea to early research scientists.
The telephone network
was a global network which did not use the concept of

packet forwarding.
Telephone networks used a circuit
switch implementation, consisting of a fixed circuit source

arid destination.
connection.
All the traffic was sent over this
With the advent of IP, packets do not travel
along established fixed circuits.
The packets are
addressed with a source and destination address; then

forwarded through the network [2].
IP allows a packet to be forwarded through different
networks in order to reach the destination.
These
individual networks may define their own rules of sending

data through their routing devices with each network
adhering to their respective rules.
IP allows a packet to
adapt to each of the individual networks as it traverses.

The size of the packet may vary from network to network.
2
The IP allows a packet to be fragmented and then

reassembled at the destination [2].
Addressing and fragmentation are the two basic
functions implemented by the IP.
Network modules within
the Internet use included addresses within a data packet to

transmit that data to its destinations.
The Field option
in the packet header contains information necessary to

perform fragmentation and reassembly of the data packet.
This is useful in the transmission of a. packet through
small packet networks [3].
Internet Corporation for Assigned Name and Numbers
(ICANN) controls the allocation of IP addresses.
ICANN
delegates a large portion of IP address space to Regional

Internet Registries (RIR)..
Each RIR then allocates the
portion of IP address space obtained from ICANN to the

organizations operating in different geographical areas.
This process ensures that each address allotted to a host
is unique.
American Registry for Internet Numbers (ARIN)
controls IP address allocation within the United States.

Internet Service Providers (ISP), universities and large
corporations are a few of the organizations that apply to
their respective RIR for their geographical location in
order to receive an IP address.
3
This system promotes
efficient distribution of IP address space.
This is
significant since IP address space is a valuable resource,

illustrated by the high yearly fees paid for IP address
blocks.
RIR makes sure that the requesting organization
properly documents the necessary requirements to obtain IP

address space.
This regulates an organization from buying
IP address blocks simply because they can afford it [2].

Grouping of similar IP addresses has a positive
effect.
This helps in efficient routing of packets along
the network. When IP addresses are assigned randomly, the

router has to record each individual location of an IP
address.
When large blocks of IP addresses are allocated
to a particular region, a router may only maintain a single

route for the block [2].
IP addresses in the range 224.0.0.0 to 239.255.255.255
are considered as multicast addresses.
These IP addresses
represent a group of hosts, which subscribe to a specific

stream of data.
255.255.255.255 is known as a special
broadcast address of which anyone can listen to given they

are in broadcast domain.
IP addresses in the range 1.0.0.0
to 223.255.255.255 are called unicast addresses.

represent an IP address for a single host.
Some of these
addresses are reserved for private networks.

4
These
Private
networks basically sit behind firewalls and do not connect

to the global network [2].
IPv4
It was soon evident that implementation of IPv4 was
not possible with the rapid growth of the Internet.
Quantity of IP addresses in IPv4 was not sufficient to keep
up with the proliferation of devices on the Internet [4].
A 32-bit address length gives us 4.2 billion IP addresses.
When IPv4 was written, it appeared to be a sufficient
amount of IP addresses.
However, as time progressed, the
Internet grew with the advent of new networking devices

such as phones, televisions and gaming consoles, which were
IP-capable.
This lead to the exhaustion of IP address
spaces [5].
Temporary solutions were found to overcome the
exhaustion of IPv4 address spaces.
The first solution was
Classless InterDomain Routing (CIDR) which is the method

for allocating IP addresses and routing IP packets.
The
goal here was to decrease the growth of routing tables

within the Internet in order to restrict the rapid
exhaustion of IPv4 addresses.
The second solution was a
technique termed Network Address Translation (NAT) in which

one IP address could be translated to multiple hosts within
5
the NAT network.
The third solution is termed Dynamic Host
Configuration Protocol (DHCP) which is used on IP networks

as the automatic configuration protocol.
However, in CIDR,
the need for larger routing tables in routers became

evident, which resulted in routing difficulties.
The NAT
solution breaks the principle of the Internet and is not

supported by some applications [6].
These three
technologies were designed as solutions but made the

networks much slower and complex [5].
In addition, these
three technologies did not overcome the problem of IPv4

address exhaustion, but only delayed it.
Project
exhaustion dates of IPv4 address space for ARIN is November

20, 2013 [7].
IPv6
Finally, the solution for the IP address exhaustion
was resolved.
The Internet Engineering Task Force (IETF)
came up with a resolution called IP: next generation

(IPng).
IETF.
IPng was a result of the proposals reviewed by
IPng was not a complete protocol, but was a product
which had to be reviewed considering the features and

limitations.
After multiple reviews and changes to IPng,
IPv6 was developed [8].
The IPv6 address size is 12 8 bits compared to the 32bit address in IPv4.
The 128-bit size gives approximately
1500 addresses per square foot of the earth's surface.

Even if every device around you is IP capable, 1500
addresses per square foot overly sufficient.
Thus, IPv6
has provided a solution to IP address exhaustion.

Internet registries are making the block of IPv6
available and are present in most of the recent operating
systems.
IPv6.
The Internet community is taking time to adapt to
The main reason would be that it is difficult for
IPv4 and IPv6 to coexist.
Whenever an IPv6 host wants to
communicate with an IPv4 host, it has to use tunneling

mechanisms where an IPv6 packet is encapsulated within an
IPv4 packet.
It may be predicted that when IPv4 addresses
are exhausted the Internet community will be forced to

adopt IPv6 conversion at a faster rate.
CHAPTER 2
IPv4 VERSUS IPv6
Version
IHL
Type of Service
Identification
Time to Live
Total Length
Flags
Protocol
Fragment Offset
He ader Checksum
Source Address
Destination Address
Options
Padding
FIGURE 1. IPv4 packet format.
The Version field is 4 bits long.
This field
specifies the format of the Internet header.

binary format.
It is set in
The value would be 4 in case of IPv4 and 6
in case of IPv6.
Internet Header Length (IHL) specifies the length of
Internet header in 32 bit words and is pointing to the
8
beginning of the word.
Minimum value for a correct Header
is 5 [3].
The Type of Service (TOS) Field specifies the type of
service desired and has an 8-bit length.
IP priority.
TOS specifies the
Several networks have service precedence in
which high precedence traffic is considered more important.

Sometimes during high load, routers accept traffic above a
defined precedence.
Delay, throughput, and reliability are
other parameters available to define the precedence [3].

The Total Length is a 16-bit field.
Total Length is
the length of the packet including Internet header and

data.
It is measured in octets.
Packets up to 65,535
octets in length are allowed in this field. But packets of

such length are impractical.
It is recommended in rfc791
that packets be greater than 576 octets in addition to

header information [3] .
The Identification field has a 16-bit length.
This
aids in assembling the fragments of packets at the

destination [3].
The Flags field has a 32-bit length.
reserved and must be set to zero.
The first bit is
The second bit specifies
whether or not fragmentation is required.
A 0 value means
fragmentation may be required otherwise a 1 value signifies

9
no fragmentation required.
The third bit specifies whether
or not this is the last fragment of the packet.
If this
bit is 0 then it is the last fragment, if the bit is 1 then

more fragments are to follow [3].
The Fragment offset field has a 13-bit length.
measured in units of 8 octets.
offset zero.
It is
The first fragment has
It specifies where this fragment fits in the
packet [3].
Time to Live field has a 8-bit length.
It indicates
the maximum time a packet is allowed to stay alive in the

Internet.
Whenever a packet arrives at the router this
field value is reduced by 1.
When the value becomes zero
the packet is discarded [3].

The protocol field has an 8-bit length.
This field
specifies the protocol used in the data portion of the

Internet packet and the values are maintained by the
"Internet Assigned Numbers Authority" [3].
Header checksum is 16-bit field.
Checksum is
performed on the header only, since the data field remains

the same while traveling towards the destination [3].
The Source Address is a 32-bit field.
the source address of the packet.
change during transmission [3].
10
It specifies
This value does not
The Destination Address is a 32 bit field.
It
specifies the final destination address of the packet.

This value does not change during transmission along the
route [3].
The Option filed is variable in length.
zero or more options.
every IP packet.
There may be
This field is not mandatory for
The following are the possible options:
end of option list, no operation, security, loose source

routing, strict source routing, record route, stream ID and
Internet timestamp [3].
The Padding field like option is of variable length.
It ensures the Internet header ends on a 32-bit boundary
[3].
In the IPv6 header format the fields such as
Identification, IHL, Flag, Header checksum, Fragmentation
Offset and Total Length Present in IPv4 header have been
removed.
The Version has a 4-bit length.
the format of the Internet header.
format.
This field specifies
It is set in binary
The number would be 4 in case of IPv4 packet and 6
for an IPv6 packet.
11
Version
Traffic Class
Flow Label
Payload Length
Nest Header
Hop Limit
Source Address
Destination Address
FIGURE 2. IPv6 packet format.

The Traffic Class has a 8-bit length and has replaced
"Type of Service" in the IPv4 packet. It is used by source
nodes and routers on the path to the destination in order
to distinguish Between different priority packets.
General
requirements that apply to the Traffic Class field are as

follows.
Interface to IPv6 service must allow the upper
layer protocol to provide the values to the Traffic Class

bits of a packet, which is originated at the upper layer
protocol.
Secondly, the nodes must be permitted to change
the traffic class bits.
Nodes should ignore these traffic
class bits if they have no specified use. Lastly, the value

in the Traffic Class Field should not be assumed unchanged
by upper layers on the protocol stack when the packet is
received [9].
12
The Flow label has a 20-bit length.
This field is
used by the source to label the sequence of packets in

order to get special handling from routers.
The Flow Label
is checked at the router, values are changed based on the

next interface and then packets are forwarded.
If routers
do not support this field then it would just forward the

packet and the field value is left unchanged.
This saves
unnecessary delays such as routing table look up [10].

The Payload field has a 16-bit length.
replaced the Total Length field in IPv4.
This field has
This specifies
the length of the payload following the IPv6 header.
It is
expressed in octets [9].

The Next Header field has a 8-bit length.
It uses the
same values that are used in the IPv4 field and is used tc
identify the next header to follow [9].
The Hop Limit is similar to "Time to Live" field in
the IPv4 header.
the time interval.
It does not perform the calculation of

Whenever a packet passes through a node
the value in hop limit is decreased by 1.
When the value
in this field is zero, the packet gets discarded.

The Source Address has a 128-bit length.
This field
contains the address of the source from where this packet

has originated.
13
The Destination Address has a 128-bit length.
This
field contains the address of the destination where this

packet will finally reach.
Advantages of IPv6 over IPv4
IPv6 has been inundated with a wide variety of
features that were not available in IPv4.
This section
will put light on those features and how they are

responsible for increasing the efficiency of the IPv6.
Address Length
The increase in the address length from 32-bit to 128
bit resulted in a large quantity of available addresses_
Even if a single utilizes thousands of IP capable devices,
the IP addresses would not get exhausted.
With the
increase in the quantity of IP addresses the requirement

for NAT was eliminated.
Availability of IP addresses
resulted in a more efficient assignment of addresses to the

networks and as well as a more simplistic routing
procedure.
The routing tables in IPv6 have fewer entries
compared to IPv4, thereby enabling quick look-ups.
With
the increase in the number of IP addresses more peer to

peer applications were designed with improved speed and
reliability [11].
14
Address Auto Configuration
DHCP was used to obtain IPv4 addresses and the domain

name server.
DHCPv6 was published for IPv6.
The most
important feature of IPv6 is to automatically configure

itself.
The Neighbor Discovery feature in IPv6 enables the
hosts to know the availability of routers on the network,

whereas in IPv4, hosts must wait until a router advertises
its address.
In IPv6 the host broadcasts the router
solicitation message and waits for a response from a router

indicating its; presence.
Through the router solicitation
message a host gets the network prefix from a router on the

local network.
The host then use's the network prefix with
its MAC address to know its IP address.
This procedure
enables a host to keep the IP- addresses the same while

changing networks [12] [13].
Simplified Header
IETF designed a simplified header format for IPv6.
This header was stripped of non essential fields that were
available in IPv4.
This format increased the performance
and efficiency at the nodes.

field was removed.
The Internet Header length
Likewise Total length is replaced by
payload Length, which refers to the size of the payload

after header.
Further fields removed are Fragmentation

15
Offset and Flag, since IPv6 packets do not undergo

fragmentation.
Limit.
The Time to Live field was replaced by Hop
This avoided the calculation of the time interval.
Flow Label field is used to label the packets belonging to

the same data flow.
Unlike IPv4, IPv6 does not contain IP
checksum; therefore, checksum need not be calculated at

every router.
The main reason for eliminating IP checksum
is due to the fact that link layer technologies already

have checksum and error handling capabilities [14].
Flow Label
This is one of the fields present in the IPv6 header,
which indicates the routers that will handle the packets
travelling from source to destination in a special manner.
The flow on the network is identified by Flow Label and the
source address of the packet.
Specific flow indicates that
the packets originated from the same source.
The packets
originating from the same source belonging to a flow will

have the same kind of requirement.
The requirements of the
packets are decided before they are transmitted onto the

network.
Once it is on the network, routers check the flow
label to identify the special handling requirements of the

packet.
Packets belonging to the same flow will have the
16
same source, destination address and routing options. This

enables the router to process at a faster rate [4].
Extension Headers
Most of the extension headers are processed by
destination nodes, so routers have less processing to be
done.
The Hop-by-Hop options header is the only header
that has to be processed by all nodes.

follows the IPv6 header.
It immediately
Each of these extension headers
may occur only once, but Destination options header may

occur twice in different positions [15].
Hop-by-Hop Options Header
It is used to carry optional information that has to
be processed by each and every node.
The Next header field
is set to zero in the IPv6 header to indicate the presence

of the Hop-by-Hop field.
It always appears after the IPv6
header [15].
Destination Options Header
This header holds the content that has to be processed
by destination node.
This header appears after the Hop-by-
Hop and before upper layer headers [15].

Routing Header
This header holds the information specified by the
IPv6 source.
IPv6 source specifies the intermediate nodes

17
that the packet will have to travel in order to reach its

destination.
The Routing Header helps in getting the
maximum transmission unit of the next link known.
If the
link maximum transmission unit is smaller than the packet

size then the router sends the ICMP message to the source
indicating the packet is too big
and has to be limited to
a smaller size [9] [15].

Fragment Header
Fragmentation procedure implemented in IPv6 is
different from that of IPv4.
In IPv4 packets are
fragmented by the routers if the maximum transmission unit

is too large compared to the maximum transmission unit of
the link on which it has to traverse".
In IPv6 when the
packets whose size is bigger than the maximum transmission.

unit of the link, then, the packet is discarded and ICMP
message is sent to the source node indicating the maximum
transmission unit of a packet that will be accepted.
The
source will then fragment the packet accordingly and

transmit it [15].
Authentication Header
This header helps in checking the packets authenticity
and integrity when it arrives at the destination.
18
MDA5 and
SUA algorithms are used to protect the packets against

deliberate modifications [15].
Encrypted Security Payload
When this header is used it has to be the last one on
the header chain.
This header hides the entire upper level
payload and the Next Headers.
The default encryption used
in IPv6 is DES-CBC, which is a data encryption standard

algorithm in cipher block chaining mode [15].
19
CHAPTER 3
NETWORK MODEL
This section describes the network model that will be
used, and measurements that will be gathered from these
networks during the simulation.
Two different networks
have been modeled; one is a simple network consisting of

one client, a router and a FTP or Video Server.
The second
one is modeled keeping a campus network in mind.
This
network is assumed to consist of LANs, routers, IP cloud,

switches and servers.
The network consists of three
departments, which are Computer Science, Electrical

Engineering and Business Administration.
Each of these
departments consists of two computers making a small local

area network.
Every other department consists of a switch
to which their respective computers are connected.
Three
switches from each of these departments are connected to

the router named CSULB_router.
connected to the Internet.
This router in turn is
There is an FTP server that is
accessed by all three departments which is present across

20
the Internet and is connected through a router named

Server_router.
The two different networks have been
duplicated to accommodate both IP versions, therebyallowing us to simulate and compare the results of both on
a network environment.
Simple Network
The design of the simple network is provide in Figure
3.
The experimental setup consists of a client, router,
and a FTP or Video Server.
Interconnection between client,
router, and server is established using a 10 baseT link.

The same network design will be used for both IPv4 and IPv6"
simulations.
Packet sizes are set uneqtial for IPv4 and
IPv6 due to the increased payload capability in IPv6.

Buffer sizes for both the client and server are set to 8760
bytes.
The router is configured to forward the packets at
the rate of 50,000 packets per second.
The packet
switching rate is at 500,000 packets per second and is set

to support central processing.
Detailed configuration of
the network will be presented in Appendix A.

Campus Network
The design of the campus network is provide in Figure
4.
The experimental setup consists of 3 LANs named CS, EE,
21
i TH scvf
fM-nt
Setve?
FIGURE 3. Simple network.
and MBA standing for Computer Science, Electrical

Engineering and Master in Business Administration,
respectively.
Each of these LANs consists of 2 computers.
The computers are configured to support different packet

sizes according to IPv4 and IPv6 implementations.
The
buffer size for individual computers on the campus network

is set to 8760 bytes.
FTP or Video Services.
The server is configured to provide

All the links used for
interconnection are 10 baseT except for a PPP DS3 link used

for connections between CSULB router to Internet and
Internet to Server router.
Three switches have been used
for three different department LANs.
The rate at which
packets are switched from the switch processor to the

appropriate output port is set to 500,000 packets per
22
second.
Switches are also set to support IEEE's 802.lw
rapid spanning tree protocol.
Two routers are configured
to forward the packets at the rate of 50,000 packets per

second.
Packet switching rate is 500,000 packets per
second and both the routers are set to support central

processing.
IP routing protocol involving the setup of
maximum transmission unit, configuring interfaceinformation and detailed configuration of the network will
be presented in Appendix A.
tmttm
FTP Server/
I4M2|
FIGURE 4.
Campus network.
23
Smcr
Since the Internet backbone is made up of IPv4

networks, it will take a certain time for the Internet to
adapt to IPv6 networks.
This research implementation will
include a behavioral study of experimental IPv4 versus IPv6

networks varied payloads.
The simple network and campus
network are configured to support the FTP services first

and then Video conferencing.
Detailed configuration of how
to set up the FTP traffic and Video traffic is explained in

Appendix A and B.
The statistics collected for Simple IPv4 and IPv6
networks include:
1. FTP throughput in bytes per second.
2. FTP throughput in packets per second.
3. Ethernet delay in seconds.
4. Response time in seconds.
5. Video Conferencing packet end-to-end delay in
seconds.
6. Packet delay Variations in seconds.
The statistics collected for Campus IPv4 and IPv6
networks include:
1. FTP throughput in bytes per second.
2. FTP throughput in packets per second.
3. Ethernet delay in seconds.
24
4. Response time in seconds.

5. Video Conferencing packet end-to-end delay in
seconds.
6. Packet Delay Variations in seconds.
By implementing and running the above mentioned
configurations to the components of the network, resultant
data will provide me with an opportunity to analyze the
performance output of IPv4 versus IPv6 networks.
25
CHAPTER 4
INTRODUCTION TO OPNET
OPNET stands for "Optimized Network Engineering Tool."
It is a comprehensive engineering system capable of
simulating large communications networks with detailed
protocol modeling and performance analysis [11]. Presence
of features like a graphical user friendly interface,
object based modeling, integrated data analysis tool, and
dynamic event scheduled simulation kernel have made OPNET a
sophisticated tool for workstation based modeling and
simulation.
In the real world environment setting up test case
scenarios using the networking devices is very difficult
and could be time consuming.
The time consumption is
impractical if we decide on implementing a network with the

real physical networking devices. To reduce expenses and
involved time consumption in setting up a real network,
network simulation tools have been used.
These are the
applications that are used to model and simulate a real

network in a computer system. This tool does not require
26
physical networking devices to set up the network.
Every
networking device is incorporated in network simulation

tool in the form of a software program and is available to
users in the form a GUI.
Users need only drag and drop
these icons to setup the network.
After the network is
simulated results are obtained that can be used to analyze

the behavior of a network under various conditions.
There
are wide varieties of network simulation tools available in

the market.
After detailed requirements gathering of this
study Optimized Network Engineering Tool by OPNET

Technologies, Inc. has been chosen.
The OPNET application consists of the following tools
1. Network Editor is a tool mainly used to build
network models.
A network can be constructed in such a way
that it contains sub networks connected with nodes through

links,.
The idea of incorporating sub networks helps in
distinguishing and managing the network model.
It also
makes it faster for duplication of a certain sub network,

avoiding unnecessary delays caused by developing a sub
network from scratch.
2. Node Editor is a tool used for creating models of
nodes.
Behavior of each network object is defined by this
node editor.
Node instances are created in the network

27
using node models. Packet streams and statistic wires are

connected with different modules to define a node. These
connections between the modules enable the flow of packets
and status information. OPNET node models have an internal
modular structure.
,2 Mom
.a-'*
File Edit View Interfaces Objects Windows Help
seiaoi / ^ sans
Packet Streams
Statistic Wire
FIGURE 5. Node editor.
28
3. Process Editor is a tool that allows you to create

process models.
These models are represented in the form
of finite state machines.
These finite state machines
consist of states and transitions .in the form of Icons and

lines respectively.
H Process Modesspjwpjrf
File Edit Merfeces FSM Code Blocks Compife
ic3s??
Help
vi. ;vJ -:*?'\r:
:~r ":r
^
c..jtftt: \ - s Vv ic r - >r -<-

ransitions
FIGURE 6. Process editor.
29
|t
j$ p\ . r -
4. Packet Format Editor is a tool that allows you to

define the internal structure of the packet fields.
Here
the size of the box of a specific field varies with respect

to the number of bit defined for it.
5. Probability Density Function Editor allows us to
explain the spread of probability over a wide range of
outcomes.
It is used to create, edit, and view probability
density functions.
6. When the network is constructed and simulated it
becomes necessary to collect resultant data to analyze the
working of the network. Probe editor is one such tool used
to specify what data has to be collected from the
simulation output.
7. Simulation Sequence Editor is used to add
constraints to the simulations.
It provides the options to
specify the duration and other attributes on the particular

simulation set to get the required results.
8. Analysis tool provides the results of the
simulation in graphical format. It is used for analyzing
the simulation results.
9. Filter tool is used to apply filters in Analysis
tool to generate new sets of data.
30
IkoiiS
ConHg-^/Ryn DES; Vjes!>s5e2-te -t .ic t-J

Number of runs: 1
Pfeva&w Simulation Set j
Commofi
Common
f - inputs
f - Outputs
' -
hour's^.
Duration: ;0.5
j ;f-- Bêcubon
fcnier
Seed: .128
Runtime Displays
Seed Values...
Values per statistic: 1CC

Update interval: |5GQGGG
events
Simulation Kernel: i Optimized
Simulation set name: ;scenario

Comments. ~ ' "
Simple...
OO...Cancel | km
j Edi Simulation Sequence..
FIGURE 7. Simulation sequence editor.
FIGURE 8. Analysis tool.

31
j* ji
Project Editor Workspace

Project Editor Work Space consists of several areas that
are important for successful modeling and execution of a
network model.
vjja! >* k- -r-d If#.kotrawYt r4- n-'>/>*,

Tie [sil Vispvif
iui
TssfSa.
Seuiuri
a #% d vi
am"k%A
flwAmytK 0E3 WisHivsv.2 \ c>

Pi p ! ^
?;oae
r..
'S#Sp:li
y
Caia..* i--!st."trfc
f'i It
'
4-
,-*i
wl
4il
t'C H -teste**
!
I". . , ?&&&
fuv.
^
\ - "H fsCCl
\ S -nb$i
mvi oik ^ro" Ar??.
ma
*5?
rU fc. -S
^ ,
mlfiS.
ae
!!l*li!lllllllllll
liilliiiiliiilll
*5
I *4^S'*S
^^
! lil
lilllll
iiililiipili
iS-gslfe NsiwkEk^se;?s e
FIGURE 9. Project editor work space
32
Menu Bar
File
Edit
View
Scenarios
Topology
Traffic
Services
Protocols
Flow Analysts
DES
Windows
Help
FIGURE 10. Menu bar.
Basic operations provided by each of the tools above

are spread over the menu bar.
The Menu bar for the project
editor consists of
1. File operations:
This involves creating a new
file, opening an existing file, and closing a file. It has

printing options, options to delete the project, and a list
of recent opened files.
2. Edit operations:
This provides editing of
individual objects in the workspace.
Options include cut,
copy, paste, and delete network objects.

3. View operations such as viewing the subnets, paths,
demands and links helps in visualizing protocol
configuration and network configuration.
It provides an
option to view the network from a bird's eye view angle.

4. Scenario provides an environment where user can
duplicate, create, and manage the scenarios.
The switching
between the scenarios is available as well as generation of

a scenario web report and bit map.
Importing and exporting
of scenario components is also provided.

33
5. Topology gives options to create all types of

subnets.
Verifying the links in the workspace, rapid
configuration of the network, importing topology from:

circuit switch text file, VNE server, xml file, as well as
exporting the topology to:
and network whiteboard.
EMA, spreadsheet, Visio, xml
Deleting unconnected nodes,
deploying wireless network, defining the trajectory,

failing the selected node and recovering the failed node
are also available.
6. Traffic is imported from spreadsheet, erlang, text
files and ACE analyst.
and TR2.
Traffic is exported to spreadsheet
Creation of traffic flows of IP unicast, IP
multicast, VOIP and MPLS VPN, conversion of link loads and

LSP loads to flows and import/export node aliases from/to
text files respectively.
7. Services provide creation of service and service
user groups, visualization/clearance of the service status
and import/export from/to files.
8. Protocols provide the list of protocols that can be
implemented in the network, options for configuring the
protocols, and the model usage guide which guides us
through the implementation and use of defined protocols.
34
9. Flow analysis options are provided in this menu.

Options for performing the survivability analysis, log
viewing, results of flow analysis, and panel operations are
also available.
10. Discrete Event Simulation (DES) provides
Individual statistics of network components, which may be
selected before running the simulation. Recording of the
packet flow in 2D of a subnet, simulation performance,
results and logs of the discrete event simulation, and an
option to play the recorded 2D animation and panel
operations are also incorporated.
11. Windows provides options to switch between
different editors, configuring, showing and floating the
tool bars, and a feature which informs you about the
project you are working on.
12. Help provides access to product documentation,
viewing OPNET modeler tutorials, links to:
OPNET home,
support center, frequently asked questions section and list

of contributed models.
It displays error and session logs
as well as provides the general information about the

application.
35
Shortcut Menu
12345 6
78
9 1 0 It 12 13 1 4 15 W 1 7 IS & 2 B
FIGURE 11. Shortcut menu.

1. New.
By clicking this icon an option to create a
new project is displayed.

2. Open.
This icon opens the existing project file.
3. Save.
Any change to a network in the workspace is
saved.
4. Print.
A shortcut menu to print the objects on the
workspace is provided.
5. Object palette.
This shortcut menu opens the object
palette in a new window displaying all the network objects

that available to build different kinds of networks.
6 . Fail Object.
This Icon makes the selected
networking object inactive.

7. Recover Object.
The entire selected networking
objects are active when the recover object button is

clicked.
8. Parent subnet. This is an icon which takes you to
the parent subnet.
9. Zoom in.
Magnifies the network to have a clear

36
view.
10.Zoom out.
Gives us the entire view of the network
by zooming out.
11.Import topology form ACE, Network topology is
imported from Application Characterization Environment.
12.
Import topology from VNE server.
Network
topology is imported from Virtual Network Environment

server.
13.
Traffic center.
Opens the traffic center in a
separate window.
14.
Network difference report.
Generates the network
difference report when there are more than one scenario in

single project.
15.
Configure/Run flow analysis.
This Icon helps in
configuring the flow analysis and running it.

16.
Configure/Run survivability analysis.
When one
or more of the networking objects are made inactive this

icon is used to configure and run survivability analysis.
17.
Configure/ Run Discrete event simulation.
in configuring and running the simulation of the

constructed network.
18.
View results.
Provides the results in the
graphical form.
37
Helps
19.
Hide/ show graph panels.
20.
Network Inventory.
This Icon generates the
network inventory summary.

Status Message Bar
At the bottom of the project editor window status
message bar is present.
Wrote Project:fC:\Users'.way\op_modds%Thro^sxji1_Rnd.project\Througbpiii.\Wm po.<- iPvi

I. StatusMessage
FIGURE 12. Status message bar..
1 Status message of the OPNET tool is displayed.

2. Displays the x :and y coordinates of the mouse.
Values change when the mouse is moved.
3 . Message buffer, when messages are too long and
cannot be read in the status message bar the message buffer
Icon at the bottom right corner of the OPNET tool may be
clicked, displaying a window containing all the status
messages.
Workflow of OPNET
After getting to know about the tool, workflow of the
tool needs to be understood. Workflow of an OPNET is
38
divided mainly into four steps; creating new network

models, choosing individual statistics, running simulations
and viewing/analyzing the results.
-i
fry mtwm
iM
Cfcoose
1 IMmihmt r
mtMrn
Set t*se i
-V 'J,.
^
r - -% MtSmktutm * *
Pamnn^m
*K
-X /S
wii* <*11
FIGURE 13. OPNET work flow.
1. Creating Network Model.
All the necessary network
components are selected from the object palette and a

network is created on the workspace.
2. Setting the parameters for network components and
choosing the applications.
In this step the parameters of
the network components are set such as IP address of the

hosts, packet and buffer sizes.
Different types of
applications required, for the network are created.

39
3. Choose individual statistics.
Once the network is
ready the statistics required for our simulation are

chosen.
4. Set simulation parameters.
Parameters such as
duration for which the simulation is run and values per

statistics are set.
5. Run Simulations.
Simulation is run for the
specified time set in the previous step.

6. Errors.
All the errors encountered during
simulation are displayed in the simulation window. Errors

are usually caused due to parameter settings in which case
simulation process is repeated from step 2. Absence of
errors takes us to the next step of the simulation process.
7.. View and analyze the results.
In this step results
are analyzed to determine the efficiency and deficiency of

the network.
8. Rerun with different set of parameters.
If not
satisfied with the results or are not able to analyze

network activity under different parameter settings.
The
entire procedure from step 2 is repeated.

9. End of simulation.
The simulation is said to be
completed when the user is satisfied with the results.
40
CHAPTER 5
SIMULATION RESULTS
In this chapter the properties of IPv4 and IPv6 are
examined in a simple network that operates with a minimal
configuration.
IPv4 and IPv6 protocols are first
implemented in simple network and then simulated on the

campus network.
Simulation of IPv4 and IPv6 Networks with FTP Traffic
Both the simple and campus networks are loaded with
FTP traffic beginning at 50 bytes up to 1 GB with an interrequest time of 2000 seconds.
The performance metrics of
both IP networks are then measured and analyzed.

Simulation of IPv4 and IPv6 Networks with Video
Conferencing Having FTP and Database as Background Traffic
Initially both the simple and campus wired IP networks
are loaded with video data with no background traffic.
The
packet delay variation and packet end-to-end delay are then

measured.
Then both the networks are loaded with FTP
transaction and database query as background traffic and
41
the performance metrics for packet delay variation and

packet end-to-end delay are measured.
IPv4 vs. IPv6 Throughput in bits per

second
12000000
jfc 10000000
XI
8000000
c 6000000
1 4000000
2000000
Payload size
FIGURE 14. IPV4 VS. IPV6 throughput in simple network.
Simple Network IPv4 and IPv6 Throughput

Figure 14 shows the two graphs which compares the
throughput statistics of IPv4 and IPv6 over a simple
network.
FTP is the data traffic used for simulating the
network.
The network is loaded with FTP traffic beginning
at 50 bytes up to 1 GB with an inter-request time of 2000

seconds.
The difference in throughput of an IPv4 and IPv6
network is small when the FTP traffic is low.
As the
volume of the FTP data traffic crosses 3 KB with an inter42
request time of 2000 seconds, throughput of the IPv4

network increases in comparison to the IPv6 network.
Any
increase in the FTP data traffic from 50MB per 2000 seconds
onward will not affect the throughput of IPv4 and IPv6
network due to the bandwidth limitation of the link.
At
this point the buffers in the switch are full and

additional packets are dropped.
IPv4 vs. IPv6 Packet Throughput

oto 2500
iA
m
% 1500
Ok
1000
/'
IPv4
if
HlhHPV6
1 ^00
D
I 0
Paload Size
FIGURE 15. IPv4 vs. IPv6 packet throughput in simple

network.
Simple Network IPv4/IPv6 Throughput Packets per Second

Figure 15 gives the simulation results between IPv4
and IPv6 over simple network in terms of packet throughput
43
Packet throughput is a small amount higher for IPv6

compared to IPv4 network when FTP data sent is between 50
bytes through 500 bytes with an inter-request time of 2000
seconds.
Again, the difference is very low, but as the FTP
traffic crosses 100 KB with an inter-request time of 2000

seconds, IPv4 packet throughput almost doubles in
comparison to IPv6 packet throughput.
The packet
throughput remains constant as it reaches the limit of the

1ink bandwidth.
Simple Network IPv4/IPv6 Ethernet Delay
Figure 16 presents IPv4 and IPv6 delay on an Ethernet
cable over a simple network.
The graph shows the end-to-.'-
IPv4 vs. IPv6 Ethernet Delay in

Seconds
0.0025
5 0.002
0
$ 0.0015
0.001
1 0.0005
jpyfi
Payload Size
FIGURE 16. IPv4 vs. IPv6 Ethernet"delay in simple network.

44
end delay of all packets received by all the stations in

the network.
Increase in the FTP traffic increases the
number of packets thereby increasing the delay of the

network.
Delay is 0.11 ms and 0.12 ms for IPv4 and IPv6
network respectively.
When the FTP data volume increases
the number of packets in IPv4 increases, which results in

further delay in the IPv4.network.
Delay in IPv6 network
is lower than IPv4 due to lesser number of packets in the

network.
Delay on an Ethernet cable of both IPv4 and IPv6
network increases along with increase in data.
IPv4 vs. IPv6 Response time in

seconds
v*
2 SOO
|2000
"
"
I1500
'
f 1000
I
500
- - I P v 4
H*~IPv6
^ 4? ** ^ ^
^c/ ^
Payload Size
FIGURE 17. IPv4 vs. IPv6 response time in simple network,
45
Simple Network IPv4/IPv6 Response Time

Figure 17 shows the statistics of the IPv4 and IPv6
Response time.
The Response time is measured from the time
a client application sends a request to the server, to the

time it receives a response packet.
When the FTP traffic
sent is between 50 bytes to 10 KB with an inter-request

time of 2000 seconds, the response time is low for the IPv4
network in comparison with the IPv6 network.
However, an
increase in data traffic gradually increases the response

time for IPv4 network.
The difference in response time of
an IPv4 and an IPv6 network is small.
IPv4 vs. IPv6 Throughput in bits per

second
u
10000000
SOOOOOO
H 6000000 -
4000000
ssmis^ssssss: Ip"y
-I 2000000
0 -
Paytoad Size
FIGURE 18. IPv4 vs. IPv6 throughput in campus network.
46
Campus Network IPv4/lPv6 Throughput

After simulating IPv4 and IPv6 over a simple network,
simulation on IPv4 and IPv6 over a campus network is
analyzed.
Figure 18 shows the simulation results of an
IPv4 versus IPv6 network in a graph form.
The throughput
of IPv4 and IPv6 networks gradually increase after 100KB

per 2000 seconds and remain stable from 50MB per 2000
seconds onward.
IPv4 has lower throughput between 50 bytes
to 1024 bytes with an inter-request time of 2000 seconds,

and higher throughput between 100 KB to 1GB with an interrequest time of 2,000 seconds.
IPv6 has higher throughput
between 50 bytes to 1KB with an inter-request, time of 2000

seconds, and lower throughput between 1 MB to 1GB with an
inter-request time of 2,000 seconds.
Campus Network IPv4/IPv6 Throughput Packets Per Second
Packet throughput of IPv4 versus IPv6 network is
presented in graph form in Figure 19.
A difference between
the packet throughput of IPv4 and IPv6 is visible in the

graph from 100 KB with an inter-request time of 2,000
seconds.
Similar to the statistics of packet throughput in
the simple network, the IPv4 has a better throughput than

IPv6.
Throughput is stabilized once it reaches the link
bandwidth limit.
47
IPv4 vs. IPv6 Packet Throughput

2500
2000
<y
u 1S00
flu
1000
3
--HIS1
a.
soo
oo
3
o
0 >*XTw
J? T p #.#,#<#
t#^
f# *V
^#
t# \
%
^
V?v N ^ ^^
^
V #>
^
<5^
cF
Q
<0 ^ ^
-IPv4
-IPv6
Paylo&d She
FIGURE 19. IPv4 vs. IPv6 packet throughput in campus

network.
IPv4 vs. IPv6 Ethernet Delay in

Seconds
0,002 S
0.002
0.001S
0.001
'
0.0005
-IPv6
//7 # &
fpy-Jf
#
%
<|r
Payload Size
FIGURE 20. IPv4 vs. IPv6 Ethernet delay in campus network.
48
Campus Network IPv4/IPv6 Ethernet Delay

IPv4 versus IPv6 Ethernet delay of a campus network is
presented in Figure 20.
It is clear from the graph that
IPv6 has a lower delay for different values of data traffic

due to the presence of fewer packets in the network.
Differences in Ethernet delay between the IPv4 and the IPv6
network is very small.
Campus Network IPv4/lPv6 Response Time
Figure 21 shows the response time in seconds of an
IPv4 and IPv6 network.
Similar to the statistic of a
response time in the simple network, response time of the

IPv4 and IPv6 version of campus network has minute
differences, but the response time has .increased in the
campus network simulation.
This shows that response time
changes as the network grows in size.

Simple Network IPv4/IPv6 Packet Delay Variation without
Background Traffic
Figure 22 shows the graphs of the IPv4 versus IPv6
Packet Delay Variation (PDV) of a simple network .in absence
of background traffic.
are implemented as
FTP and database query applications
background traffic.
Video traffic is
generated across the network starting with the flow of

interactive multimedia in its low resolution format and
49
ending with high resolution video.
IPv4 vs. IPv6 Response time in

seconds
*IPv4
-XT
&
#&
^v"</
MPvS
Payload Size
FIGURE 21. IPv4 vs. IPv6 response time in campus network.
IPv4 vs. IPv6 Packet Delay Variation

in seconds
3.5E-U
xr 3E-11
S
0
wU 2.5E-11
t/i
c 2E-11
IS 1.5E-11
IPv4
1E-11
IPV6
5E-3.2
0
1024
bytes
3072
bytes
5120
17280
34560
bytes
bytes
bytes
Fayloacl Size
&*
FIGURE 22. Packet delay variation in seconds without

background traffic
in the simple
50
network.
PDV of IPv4 and IPv6 continues to be stable for

different loads of video traffic.
This stability is due to
the absence of background traffic, the difference between

the PDV of IPv4 and IPv6 is negligible.
Simple Network IPv4/IPv6 Packet End to End Delay without
Background Traffic
Figure 23 gives the
statistics of IPv4 versus IPv6
packet end to end delay in the absence of background

traffic.
The packet end to end delay is stable until the
network is loaded with 5120 bytes of video traffic with an

interarrival time of 10 frames/second. After which the endto-end delay for both IPv4 and IPv6 increases.
As it is
clear from the graph, there is a very minimal difference in

packet end-to-end delay.
Simple Network IPv4/lPv6 Packet Delay Variation with

Background Traffic
IPv4 versus IPv6 PDV is presented in Figure 24.
Here
background traffic is varied from 10% to 60% of the link

bandwidth.
The PDV is almost the same for both IPv4 and
IPv6 until 40% of the background traffic is present in the

network.
The PDV of IPv4 and IPv6 increases with the
increase in background traffic.

of packets in the network.
This is due to the number
The differences in PDV of IPv4
and IPv6 network are in terms of ms, and is very

negligible.
IPv4 vs. IPv6 Packet End to End

Delay in seconds
0.035
0.03
% 0.025
t/i
.S (ICJ2
JT 0.015
0 0-01
|Py4
I
0.005
w
o
*o
c
UUt
&
1024
bytes
3072
bytes
5120
bytes
17280
bytes
34550
bytes
Payload size
a*
FIGURE 23. Packet end to end delay in seconds without

background traffic
in the simple
network.
Simple Network IPv4/lPv6 Packet End to End Delay with

Background Traffic
The graph in Figure 25 gives the statistical
representation between IPv4 and IPv6 Packet End to End
Delay of a Simple Network.

background traffic the
For a lower volume of
packet end-to-end delay
is
constant for both IPv4 and IPv6. There is a slight increase

in the curve when
background traffic is increased to 40%

52
bandwidth.
IPv4 has a little higher delay during high
background traffic and the difference in the packet end-toend delay is miniscule.
Pv4 vs. IPv6 Packet delay Variation in

seconds
0.000025
0.00002.
5|0.000015
|
j
0.00001
0.000005
0
10%
20%
30%
40%
50%
60%
Background Traffic
FIGURE 24 . Packet delay vax~iation in seconds with

background traffic in simple network.
Campus Network IPv4/IPv6 Packet Delay Variation without

Background Traffic
Figure 26 gives the statistics between IPv4 and IPv6
PDV of a campus network in absence of background traffic.
When video traffic is flowing between the client and server
in its low resolution format the PDV of IPv4 and IPv6 is
negligible, but when interactive display of high resolution
53
video takes place PDV increases. This could be due to a

delay in the packet arrival rate. Even though IPv4 has a
bit higher PDV than IPv6, it is negligible.
IPv4 vs. IPv6 Packet End toEnd Delay

in seconds
* 0-0172
1 0.017
1 0-0168
0.0166
f. 0.0164
f 0.0162
O
0.016
" IPv6
o 0.0156
0.0154
UJ
m
10%
20%
30% .
40%
50%.
60%
Background Traffic
FIGURE 25. Packet end-to-end delay in seconds with

background traffic in Simple network.
Campus Network IPv4/IPv6 Packet End to End Delay without

Background Traffic
The Figure 27 shows the packet end-to-end delay of a
Campus Network in absence of background traffic.
The
packet end-to-end delay is increasing gradually with the

increase in volume of video traffic.
54
For high resolution
video frames significant processing is required, which may

be a possible factor in the longer delay in IPv4.
IPv4 vs. IPv6 Packet Delay Variation in

seconds
0.000006
0.000005
* o >000004
0.000003
- IPv4
|
0.000002
HE IPV6
> O.OGOOOi
m
1024 bytes
3072 bytes
5120 bytes 17280 bytes
Payload Size
FIGURE 26. Packet delay variation in seconds without

background traffic
in campus
network.
Campus Network IPv4/IPv6 Packet Delay Variation with

Background Traffic
Figure 28 shows the comparision of IPv4 versus IPv6
packet delay variation of campus network in the presence of
background traffic.
both IP versions.
The PDV continues to be constant for

Here we can see the PDV has increased in
the presence of background traffic. IPv6 has

than IPv4 and the difference is
55
few ms.
higher PDV
IPv4 vs. IPv6 Packet End to End Delay

in seconds
0.06
*0
O 0 OS
w
m
jg 0.04
0.03
D
iyc
4*
1
v-w/if/mm fPY4
0.02
IPv6
0.(31
0
1024 bytes
3072 bytes
mU
gl
5120 bytes
1/280 bytes
Payload size
FIGURE 27. Packet end-to-end delay
in seconds without
background traffic in campus network.
IPv4 vs. IPv6 Packet Delay Variation in

seconds
*0
C
o
om
0.00002 S
0,00002
m
0.000015
c
o
>
0.00000s
JI
D
u
CLft*
? Pv 4
0,00001
-IPv6
10%
20%
bo%
m%
50%
em
so%
Bdctcgrouiid Traffic
FIGURE 28. Packet delay variation in seconds with

56
Campus Network IPv4/IPv6 Packet End-to-Bnd Delay with

Background Traffic
Figure 29 gives the graph of IPv4 versus IPv6 packet
end-to-end delay
of a campus network in the presence of
background traffic.
There is no change observed in the
packet end-to-end delay
for IPv4 and IPv6.
Again the
difference is on the order of ms. We do not see an increase

in delay time because the network may not have had enough
bandwidth, exhausting its full capacity, hence delay is
constant for both IP versions.
IPv4 vs. IPv6 Packet End to End Delay

"in seconds
0.054
mi
2 0.052
f.
0.05
>*
f 0.048
.
; 1 0.046
f O
f
Z 0.044
;
a
10%
i
<p
*i
*5
20%
30%
IPv4
**1Pv6
40%
50%
60%
80%
Background Traffic
FIGURE 29. Packet end-to-end delay
in seconds with
57
CHAPTER 6
CONCLUSION
This thesis studies the behaviour of IPv4 and IPv6
networks.
Two types of networks simple and campus network
are modeled for each version of IP.

of 10Mbps and 44.73Mbps links.
The network consists
The networks are loaded
with FTP traffic to analyze their throughput, packet

throughput, Delay over Ethernet, and response time.
Video
traffic and background traffic are also added to the

network to see the changes in packet end-to-end delay and
packet delay variation.
When simple network is loaded with FTP traffic the
throughput is low for IPv4 compared to IPv6 during the low
load and the difference is very small.
When the FTP
traffic increases throughput of both IPv4 and IPv6

increases.
The throughput for IPv4 and IPv6 is constant
when the FTP traffic reaches the link bandwidth. Packet

throughput is initially low for IPv4 than for IPv6, due to
low FTP traffic.
As the volume of data increases the
58
number of packets in the IPv4 network is more than the IPv6

network. Similarly in the campus network the throughput and
packet throughput is low and almost negligible, but as the
FTP traffic increases throughput and number of packets
increases. During high load of FTP traffic the number of
packets in the IPv4 network is double than that in the IPv6
network.
The end-to-end delay on Ethernet connection is almost
the same for IPv4 and IPv6 networks during low load.
In
the simple network model the delay is low and negligible

when traffic load is low.
When the volume of FTP traffic
is increased the delay in the IPv4 network is more than

that of IPv6 because the IPv4 network has a higher number
of packets to be processed than the IPv6 network.
Similarly in the campus network end-to-end delay on
Ethernet is negligible for low FTP traffic but the delay is
more for the IPv4 network when FTP traffic is increased.
The response time in the simple and campus network
modules are almost the same, there is no observation of
significant differences.
Response time
in the campus
network model is more than that observed in the simple

network model because the volume of data sent in the campus
network is more than the simple network.
59
The simple network and campus network model were

loaded with video data in its low resolution and high
resolution format.
In the absence of background traffic
the packet delay variation and packet end-to-end delay was

negligible for both versions of IP network.
Similarly in
campus network the packet delay variation of IPv4 and IPv6

networks were almost the same.
When the IPv4 and IPv6 networks were loaded with
background traffic in the range of 10%, 20% 30%, 40%, 50%
and 60 % of bandwidth, the packet delay variation and
packet end-to-end delay increased with the increase in
background traffic.
Again the difference in packet delay
variation and packet end-to-end delay of IPv4 and IPv6

networks was small.
Packet delay variation and packet end-
to-end delay was higher for Campus Network when compared

with simple network.
Thus, the analysis of IPv4 and IPv6 networks presents
us with their performance characteristics through
statistical analysis.
The statistics obtained from
simulation tells us that the performance of IPv4 and IPv6

are almost the same and the difference is neglible.
performs better under specific circumstances.
Future work
can be done on wireless IPv4 and IPv6 networks.

60
IPv6
APPENDICES
61
APPENDIX A
CONFIGURING FTP IN OPNET MODELLER
62
Simple Network Designed Using Modeler

OPNET modeler is the tool used to study and perform the
simulation of IPv4 and IPv6 networks.
With OPNET tool any
kind of network can be designed by just dragging and

dropping the networking devices from object palette on to
the project workspace.
The network parameters can be
varied to analyze their behavior.
Object
Tree. Testl2~>
J;>( Search by name: f|
Dmg model or subnet icon into workspace

Mode Models
1C C CBaseX_J_AN
^ 1CC BaseT^12M.N
1| 1CBaseT_J_AN"
J 3Com CB35CQ
Application Cordig
_s!2
H AS j G R F ^ L C 4 s _ a 2 _ a e
Bav Networks Ceniifison 122
2j Cisco OSC
J eth 18_eihch1SJf ddi 16tr 1SjzV'Mch
elh 2JFddi2__tr2_svvit eh
eth^_eth!ane4_fddi4_tr4j:!lane^_s*/dtch
BJ
eth^fddiJfcr4_swa:ch
>k
^
^
*':
|
p:
If
U
jP
If
eth 8_jeihch SJddiSjtrB^svviteh

ethemet 1S__svvstch
ethsmet2siip 8Jfirewall
ethemet 32Jiub
ethemet^ silo 8 otwy
ethernet^server
ethemei_vvkstn
IP .Attribute Confsg
IP VPN Config
c*22__cloud
ppp_server
ppp_wkstri
Profile Confia
Fixed Node
Fixed Node
Fixed Node
Rxed Node
Fixed Node
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Fixed
Freed
Node
Node
Node
Node
Node
Node
Node
Node
Node
Node
Node
Node
Node
Logical Subnet
Satellite Subnet
Node
Node
Node
Node
Mobile Subnet
Subnet
jstom Model..
Close
FIGURE 30. Object palette.
63
Help
Object palette consists of Profile Configuration and

Application Configuration that are used in this study; they
are used in configuring the network applications.
Switches, routers, Links, IP cloud, workstations and
servers have been used from the object palette to build the
network.
The configuration done to Profile configuration
and Application configuration are same incase of both

simple and campus networks.
FIGURE 31. Experimental campus network.
The above figure shows the experimental setup of campus

network.
64
CS1, CS2 , EE1, EE2, MBA1 and MBA2 are the standalone
personal computer requesting the FTP services from the
server.
It supports one Ethernet connection at 10 Mbps,
100 Mbps, or 1000 Mbps.
These standalone computers have
been connected to 3 switches switchl, switch2 and switch3.

This switch supports up to 16 Ethernet interfaces and
implements the spanning tree algorithm to ensure loop free
network topology.
router.
The switches are then connected to CSULB
Two routers are used in this network design one is
CSULB router and other is Server router.
It supports 4
Ethernet hub interfaces and 8 serial line interfaces.

Packets arriving on the interface are routed to the
appropriate outgoing interface based on the destination IP
address.
CSULB router is connected to IP cloud which
serves as the Internet.
IP cloud supports up to 32 serial
line interface line interfaces at a selectable data rate

through which IP traffic can be modeled.
When traffic is
passing through cloud it requires certain time to route

each of the packets and this is determined by Packet
Latency attribute of the IP cloud.
connected to the Server router.
Further the IP cloud is
Server router has the same
routing configuration as that of CSULB router.
The packets
are then routed from the Server router to Server Switch

65
which also has the same configuration as that of other

three switches.
Packets are then finally routed to its
destination, FTP server.

Configuring FTP
Application Definition specifies the type of
application that is supported in the network.
Applications
supported in the network may be database, http, email, FTP,

print, remote Login, video conferencing, voice and custom
application.
This scenario is configured to support FTP
application.
!a
i&PPhJZONHQi A:: Type:;utility
Value
APPLjCOMFIG
Attribute
(J)
r name
(J) t Application Definitions
C-.)
j- Number of Rows
1 FTP
|<2>
Description
(J)
I- Custom
1
<$}
<s>
Off
'
'Email
--Ftp
Http
Pnni
Off
CD
m
\m
FTP
(...)
Off
J-Wwfie
(J)
Off
Remote Login
#
' -
Off
Off
.ear'
Udes :C&r#erancng '
L Yoksm
Off
MOS
<J> Voice Encoder Schemes
Mi Schemes
n fiijdmmmoed
<D I
Apply to selected objects
^ Exact match
OK
FIGURE 32. Application configuration attributes.

66
Cancel
Q (Ftp.! Table
j ]Msibute
Command Mix Get/Total)
Value
100%
Inter-Request Time {seconds; constant ;2CCC;

File Sfee (bytes;
constant (512Z)
Symbolic Server Name
FTP Server
Type of Service
Best Effort ;C;
RSVP Parameters
Pane
Back-End Custom Application Not Used
OK
Cancel
FIGURE 33. FTP attribute and values table.
FTP attributes and value table is used to configure

the FTP based on network requirements.
Command Mix denotes
the percentage of get commands to the total FTP commands.

The remaining percentage of commands would.be FTP put
operation.
Inter request time denotes the time between the
file transfers.
bytes.
File size defines the size of the file in
Symbolic server name is the name of the FTP server.
Type of service selected is best effort.
It is the session
attribute that allows the packets to be processed faster in

IP queues.
Configuring Profile Definition
It allows us to specify different user profiles.
These profiles are then used by individual workstation to
create application traffic.
Custom profile is created for

67
this scenario and is set to use FTP services.
Operation
mode is set to Serial since there is no other application

in the profile other than FTP.
Start time defines the
start of the profile during the simulation.
Duration tell
us the time for which the profile is active for entire run
of simulation.
O < PRC:-"LE.CONFIG; Arributes

...
Type:|Utilities
lvalue
Attribute
(f)
name
j- Number of Rows
(...)
1
| Profile Name
FTP
+ Applications
U.
(J) - Profile Configuration
Serial
Operation Made"
<2>
:<S>
prmmd)
End of Simulation
j- Duration (seconds^
d>
uniform i\Wr'l W)
I- Start Time (seconds)
(-}
+ Repeatability
<2>
PROFILEjCONFiG
jj
j " Advanced
filter
<acf match
f"" Apply to selected objects

OK
FTGURE 34. Profile definition attributes.

68
Cencei
(Applicationsj T*;!e
'Name
Start Time Offset
'seconds)
uniform |5,1i|
FTP FTP
Rows
. Duration
Repeatablstv
Second?;
jOnce at Stat Time
Bid of Profile
.j
R/ Show row iabete
OK
Cancel
FIGURE 35. FTP attributes.
Start time offset time defines the inter application

time.
It has been set to default values1.
Duration is set
to the End of Profile which means the application will

abort when the profile ends.
Repeatability is set to Once
at a Start Time since the application aborts when

simulation ends.
Server Configuration
Server is providing the FTP services to the standalone
computer.
It supports one Ethernet connection at 10 Mbps,
100 Mbps, or 1 Gbps.
Speed at which server is operating
depends on the data rate of the link.
69
I p * tsJ
(SERVER) Attributes
I ype:|server
Attribute
Value
' rfimm
SERVER
V",
(J)
+: Application: PCE Tier Configuration
Unspecified
(J)
t Application: Destination Preferences
None
(J)
* Application: Supported Profiles
None
Application: Supported Services
8 H323
+ CPU
+ VPN
^ DHCP
* IP Multicasting
II:
ill
m ip
? NHRP
+ Reports
111:
* SIP
111!-.
(f)
Aiito Assigned
Server Address
+ Servers
* TCP
iiUTP '
:* Advanced
Fitter
T Apply to selected objects
f" Exact match
OK
Cancel
FIGURE 36. Server configuration attributes.
Application supported services define the parameters

to start and setup services for various applications at
this server.
70
(Application: Supported Services)Table

Description
- Name
Supported
FTP FTP
Rows
_i
OK
W Show row labels
Cancel
FIGURE 37. FTP service activation.
FTP service is selected from the list of available

services and is set to Supported.
By setting service
status to Enabled,, FTP services are activated in this

server.
Client Configuration
Client workstations are requesting for FTP services
from the server.
The workstation supports one underlying
Ethernet connection at 10 Mbps, 100 Mbps, or 1000 Mbps.

Packets are routed on the first come first serve basis and
speed of client depends on the transmission rate of output
interface.
71
iCSlj Attributes
Type: ^workstation
.-rvtv.'e
: Vilue
name
CS1
~ Applications
:f
(D
application: ACE Tier Configuration
Unspecified
tllllllS
(J) ? Application: Supported Profiles
L-I
(J)
Application: Supported Sen/ices
None
(J) i? Application: Transport Protocol SpecifL. Default
B H323
^CPU
(D
+ Application: Destination Preferences
0 j- Client Address
Auto Assigned
* VPN
t DHCP
f IP Multicasting
+ IP
+ NHRP
* Reports
* SIP
:'iii Servers
+ TCP
+ L2TP
P Advariced
(j)
Rfier
_j
F" Exact match

OK
Cancel
FIGURE 38. Client configuration attribute.
Client has a list of configuration attributes through

which individual workstations can be set to operate in
different way.
72
Application
pip FTP
Server
Rows fiefete
Details
Jr:-!r;c
Actus! Name
Symbolic Name
FTP
Duplicate
5? Shov ry;: iebes
us -oe.
FIGURE 39. Application destination preferences
FTP is chosen from list of application. Symbolic name

is set to FTP server.
Actual Name defines the name of
Destination Server and its selection.
73
lJ
(Actâ* Name)Table
Selection Weight
L Name
.Network.SERVER Campus Network.SERVER
]1S
J
1
Rows
ps*ails
_IJ2
Cancel
OK '
,|
B? Show row labels
FIGURE 40. Actual name table.
Name specifies the destination address of the server,

Selection weicrht is set to 10..
k^S'LmJ
ffSSP
{Application: :;;pooro Pioiles Tsbje

|Profile Name
"ftp* ftp
Traffic Type
Application Delay Tracking
Ml Discrete
Disabled
"1
Rows
IV Show row labels
OJS
FIGURE 41. Client application supported profile.

74
Cancel
Profile name is set to FTP. This was the profile

created in profile-configuration. Traffic type is discrete.
Application Delay Tracking has been disabled,
15 interface Information) Table

jMribuie
IliSM
Value
jffafie
IIF
Address
2CMB:0:0:4:C:C^:2
Subnet Mask
Auto Assigned
MTU fsytes;
12SC
; Compression
Information None
IPv6 Parameters
Descnpfcion
. .
Layer 2 Mappings
|
.
N/A
None
Jlj
I
!'
OK
Cancel
FIGURE 42. Client and server interface information table.
Client and Server IP and TCP Settings

Based on the IPv4 or IPv6 network, Address attribute
is set.
Subnet Mask is set to auto assigned. Maximum
transmission unit (MTU) is set to 1280 bytes.
Based on
IPv4 and IPv6 networks the value of MTU will change.
75
IS (IPv6 Pararreters; Table

Attribute
Value
Link local Address
Default EUi-6^
Global Addresses;
Rotifer Solicitation Parameters Default
Neighbor Cache Parameter?
Default
MTU fr/tesl
fcthemet
d
OK
Caned
FIGURE 43. IPv6 configuration table.
IPv6 parameters are configured only when the IPv6

networks are simulated.
default EUI-64.
Link local address is set to
Router solicitation and Neighbor cache
parameters are set to default values.
Router solicitation
gives us the number of times the solicitation messages are

sent if response is received.
Workstation concludes that
there is no router in the network if no response message is

received.
Neighbor solicitation attempts, queue size can
be configured in Neighbor Cache parameters.

Global address is explicitly specified here. Prefix is
set to 64 bits and Address type is set to non EUI-64.
Unique interface ID is formed using these three attributes.
76
hi|giig
ff2 (Global Addresses)} . dba

j Address
2C^5:D:iioi:C:3" 2C5:C:C:3:C:G:C:3
Prefix Length
Address Type
64
Non E'JI-64
Rows
Cancel
OK
I (7 Show row labels
FIGURE 44. Global address table.
Atribute
Value
Maximum Segment Size ijbytes}

Receive Buffer kbytes)
&jto-Asstgned
8760
Receive Buffer Adjustment
None
Receive Buffer Usage Threshold id RCV BUFF} C.C

Delayed fiCK Mechanism
Segmeni/Ctack Based
Maximum ACK Delay isec)
0.2OD
MOTmuRi ACK Segments
Slow-Start Initial Count (MSS;
Si!!:
Cancel'
Promote
FIGURE 45. TCP parameters.
Maximum Segment Size has been set to Auto assigned.

Receiver Buffer is set to 8760 bytes. Maximum ACK delay is
set to 200 msec for windows operating system.
77
It is set to
use segment/clock based delayed ACK mechanism which

generates ACK for every other segment received or else if
two segments are not received within the time interval.
Receiver buffer usage threshold is set to 0.0, this
implementation models the TCP in which advertisement of
constant buffer size is done by the receiver.
US (Bridge Parameters) Tafa.^

^
Value
Priority
32766
Spanning Tree Protocol
RSTP $2.1w)
QoS Parameters
None
Timers
i \
BPDU Service Rate jpackete/$ec}
Packet Service Rate jackets/sec)
vuu** wv
OK
"1
ryance!i
FIGURE 46. Bridge parameter table.
Switch Configuration
Priority help in selecting the bridge, it is set to
its default value 32 768. IEEE's 802.lw rapid spanning tree
protocol is used.
A timer is used to create and spanning
tree, it is set to its default values.
Bridge protocol
data Units service rate is set to 100000 packets/sec.
78
Packets are switched at a rate of 500000 packets/second by

the switch processor to the output port.
mam
gg 'Iff*: RNl
Type: |cloud
Attribute
1
INTERNET
r-name
+ IP Routing Protocols
* Reports
t CPU
^ Device Metrics
(D
j- Packet Discard Ratio
%.%%
\^
j- Packet Latency ;secs]
constant :C.C2;
iilji
! Performance File Duplicate Entry Proc... Minimum

L
(J)
Performance Metrics File
Unaligned
+ VPN
+ DHCP
f- System Management
- IP Multicasting
% IP
t: Security
I
a .MPLS
f NHRP
* RSVP
(J) + System Information
(...)
P Advanced
<f>
Niter
Exact match

OK
Cancel
FIGURE 47. Configuring performance metrics for ip cloud.
IP Cloud Configuration
Packet discard ratio is set to 0,0%. Packet latency is
set 0.02 seconds.
It specifies the latency experienced by

79
the packets traversing through the IP cloud.
Performance
file entry duplicate processing is set to Minimum, which

specifies how the processing of multiple entries
corresponding to same data is handled.
jj Mr
Ilifl
Irli
lUtta
MsiEM
Hefelirtd
msm
ttyhrCMt siiefe
fee
Fffns
Mil
fori
FIGURE 48. IP cloud IPv6 interface information table.
2 interfaces are configured according the network

design.
IF1 and IFO are name of the interfaces.
MTU is
set to Ethernet which refers to 1280 bytes for IPv6.
Link
local address is set to Default EUI-64 to automatically

configure its address.
Routing protocol used is RIPng.
Router Advertisement parameters and Neighbor- cache

80
fa
parameters are set to their default values.
IPv6 enabled
interface should have one Global address in addition to

local address.
Each interface is defined with a Global
address.
Router Configuration
Out of the 2 routers one is connected to switches and
IP Cloud and other is present between server switch and IP
Cloud.
It supports 4 Ethernet hub interfaces and 8 serial
line interfaces.
Packets arriving on the interface are
routed to the appropriate outgoing interface based on the

destination IP address.
Processing scheme is set to central processing; it
refers to processing of packets by single server with
single queue.
Datagram switching Rate is set to 500000
packets per second.
Number of packets processed by the
forwarding processor is set to 50000.
A unit for
forwarding rate is set to packets/second.
Memory size
specifies the memory used to store the packets being

processed by processor or the packets waiting to be
processed.
It is set to 16 MB.
81
MijiS
0 iSRVERJÔU*"F" AU-=I 1.1Type
router
i Value
Ailrihute
im
SERVER..ROUTER
name
IP
* APS Parameter
<D !
<2>
<S>
<$>
j- Processing Scheme
Centra! Processing
I- Backplane Transfer Rate |bfts/seco.

h Datagram Switching Rate packets...
Meal Used
] Datagram Forwarding Rate
<3>
packets/second
I-- Forwarding Rate UnitsL- Memory Srse (bytes)
<S>
I
<5>
fit IP tlcS Parameters
<s>
f|! NAT P-arsiêters

;
IP Rcutlng ProteJs
1 MB
None
>" IP Routing Parameters
IPv6 Parameters
Not Configured
5 IF Multicasting
(/PN
* Reports
Performance Metrics
DHCP
1 s,.- =. Pw+^îe.
%
<f>
Fitter
Advanced
!""" Exact match
OK
Cancel
FIGURE 49. IP processing information table.
55?
i:ilt
$&?
"En
11 :-i
E\
re n;
lite; 'DfeslMit
yfeU
%$.
niku&i feet Mm
dsHpjfe BhsrA
mm
Ce&E'j$ u
Hfffcijfccca Eta
nfkffijkto Mi
mm L;
?swi*
?:ts
RiFrc
BFrs
If5
%#$ftscre ILfete -mm

Rcaer
Ar.ffjrcr-: rs r-rm
*8316(8$
D&ii
'fM
Dekl
Dili
m
'm
fee H?'5
Mm
Mm
ltd
rob
m
m
m
m
.,L.
FIGURE bO. IP interface information of ipv6 router (CSULB)

82
Router configuration is same for all the routers in

the network.
router.
4 interfaces have been created in CSULB
MTU are set to Ethernet which indicates it is 1280
bytes in size for IPv6 network.

RIPng.
Routing protocol used is
Router Advertisement parameters and Neighbor cache
parameters are set to their default values.
IPv6 enabled
interface should have one Global address in addition to

local address.
Each interface is defined with a Global
address.
8itefetertaf-ii
fe
kis
wirilm
bxmm
Os
kdsfMkt Si
R-m Frdocc PJtyes
feoira
fester
Mfve
Iter
1S2C3.1
?'B5SC
*i
Mv'S
iiier
2s" I5C 255 C
Ft
f1 T:
*iV3
mm
mil
fe
EH
Ma's
IP
kie
IP
Erenei
kite!
km
Efj
Br&ti
IP
rri
kltei
;#
ffi P
to
kite:
hMkwd
k&kwpd
kn ^ ed
Mckpd
Afc.-ssg'ed
Srer,s
klki
k:<e
Pf
%'Jsk
fee
;D
kne
R?
*p
!#
Her
kite
if
:P
f2 R
M'3
kite
fas
85
BP.
Mi
kfe
fes
HP
ip
ip
FF
Fi:B:
fll 111
M'S
Lci
!&4
.%5
HE
!,
H2.:iI
2^5 Z55 255 J
life
km
r:p
ip-
,tlcAsagned
k:
kfe
kie
El
ip
Cm!
U
Dfsu
Sdai
1/
Well
Dfcu
Ccil
L]
Md
-re;
5? fc'ss stele
FIGURE bl. IP interface information of ipv4 router (CSULB).
83
IFO, IF1, IF2 and IF10 are the 4 interfaces used by

the CSULB router.
The above said interfaces have been
assigned with appropriate address and subnet mask.
Routing
protocol used is set to routing information protocol (RIP).

Maximum Transfer Unit (MTU) is set to Ethernet which is 576
bytes for IPv4 network.
84
APPENDIX B
CONFIGURING VIDEO CONFERENCING WITH BACKGROUND TRAFFIC
OPNET MODELLER
85
APP^ca-.O":
PR-: p'.S '
FIGURE 52. Simple network configured with video

conferencing having a FTP and database background traffic.
The configuration of the workstation, server, router,

switches are same for all the network design in this study
except for few changes in attributes like address,
interface information, routing protocol and few others in
IPv4 and IPv6 networks. The changes in network design for
video conferencing are the inclusion of Video server with
FTP server and Database server as background traffic.
86
Application Configuration
In this network design
FTP,
database and video
conferencing applications have been created.
Among them
Video conferencing is made as the main stream application

and other two have been assigned as background traffic.
Each of the applications is enabled.
4P*JCAT1CN Atr?
Type: (utility
Attribute
Value
(f) r name
(f)
APPLICATION
Application Definitions
h Number or Rows
i-
t VIDEO
> FTP
DATABASE
^ MOS
(J)
* Voice Encoder Scheme?
Ail Schemes
i'"'#dvanced
Filter
Exact match
r Apply to selected objects

OK
Cancel
FIGURE 53. Application definition with 3 applications

video,
FTP
and database.
87
B (V r cec Conferencing) Tabie

iMribute
Frame Interarrival Tmne information 1Z frarnes/sec
FIGURE 54.
Frame Size Information ijbytes)
128X128 pixels
Symbolic Destination Name
Video Destination
Type of Sen/ice
Interactive Multimedia (5)
RSVF Parameters
None
Traffic Me: ;%}
Ail Discrete
Video conferencing attributes.
Frame Interarrival time has been set to 10 frames/sec

for incoming and outgoing streams.
Frame size has been
kept at 128*120 pixels which is equivalent to 17280 bytes.

Name of the Video Destination is given.
set as interactive
discreet.
Multimedia.
Type of service is
Traffic type is set to
Here Interarrival time and Frame size is varied
to get the desired results.

The FTP application serves as background traffic.
Command Mix is set to 50%, which configures the FTP to
include 50% of PUT operation and remaining percent of GET
operation. Inter-Request time is set to exponential (30).
File Size is set in bytes and varied for desired results.
FTP server name is specified for Symbolic Server Name
attribute. Type of services is set as Background.
88
85
(Ftp) Table
.^tribute
Value
Command Mix (Get/Total)
50%
&:>
Inter-Request Time (seconds) exponential (3G;)

File Size fetes)
constant (#134304}
FTP Server
Type of Service
Background (1)
RSVP Parameters
None
Back-Bid Custom Application Not Used
.J
|
FIGURE 55.
OK
Caned
FTP attributes.
MEM
(Database* -ab;e
Value
(Mribute
Transaction Mix (Queries/Total Transactions) 5Z%

Transaction fnteranival Time (seconds'
exponential (3;
Transaction Size (bytes;
constant 18433$
Database Server
Type of Sen/ice
Background fl!
RSVP Parameters
None
Back-End Custom Application
Not Used
OK
J
Cancel
j
FIGURE 56. Database attributes.
The Database application serves as background traffic.

Transaction Mix is set to 50%, which indicates the
percentage of query transactions to total transactions.
Interarrival time is set to exponential (30).
size is specified in bytes.
Transaction
Application is given the
89
symbolic server name.
Database application is configured
as background traffic.
Profile Configuration
Profile configuration specifies the user's application
usage profile.
Profile named STUDENT is created for both
simple and campus networks.
All the workstations in campus
network are configured with STUDENT profile.
fproflk
|
t-:i
Ccrmursto"' Table
!Profile Name
Applications
"STUDIMT'STUDENT
Operate Mode
SfrruJianeous
% j? i
Start Time Seconds') Duration fseconds) Repeatability

uniform flGD.110} Sid of Simulation Unlimited
" ;i
r1
Cancel
...J ^ Show row tebete

FIGURE 57. Profile configuration.
Profile name is set to STUDENT.
Three applications
have been configured for this profile.
Operation mode is
set to simultaneous, where all. three start at the same

time.
Start time of the profile is set to uniform
(100,110),
simulation.
The Duration of the profile is until the end of

Repeatability is set to unlimited, which
90
indicates the profile will run for unlimited number

times in a serial manner.
91
REFERENCES
92
REFERENCES
[1] ICANN,"Internet Corporation for Assigned Names and
Numbers,"2012; www.icann.org/en/biog/cerf.htm
[2] Jeanna Matthews, Computer Networking: Internet
Protocols in Action, Wiley, 2005.
[3] Internet Engineering Task Force," IETF Tools,"Feb.2012;
tools.ietf.org/html/rfc79l#section-1.1
[4] William Stallings,"IPv6: The New Internet Protocol,"
IEEE Communications Magazine, July 1996, 96-108.
[5] Latif Ladid,"IPv6 - The Next Big Bail-Out: Will IPv6
Save The Internet?" Proc.International Conference on
Computer Systems and Technologies and Workshop for PhD
Students in Computing (CompSysTech109), 2009, PP 21-27.
[6] Alain Durand,"Deploying IPv6,"TREE Internet Computing,
Jan-Feb 2001, 79-81.
[7] Geoff Huston,"IPv4 Address Report," 7 November 2010;
www.potaroo.net/tools/ipv4/index.html
[8] S. Bradner, and A. Mankin,"The Recommendation for the
IP Next Generation Protocol,"(Internet RFCs RFC 1752),
1995;http://tools.ietf.org/html/rfcl752
[9] S. Deering and R. Hinden,"Internet Protocol Version 6
(IPv6)Specification,"1998;www.ietf.org/rfc/rfc2460.txt
[10]William Stallings,Data and Computer Communications,
5th ed., Prentice Hall International, 1997.
[11]Jun Tian, and Zhongcheng Li,"The next generation
Internet protocol and its test,"Proc. IEEE
International Conference on Communications, 2001,PP
210-215.
93
[12]Nazir Ahmad Chaudhary,"Introduction to Mobile IP

Technology Tutorials," OPNETWORK, 2005.
[13]Alcatel,"Technical Paper. The Move to IPv6," 2002;
http://www.cu.ipv61f.org/pdf/ipv6_a4_tp.pdf
[14]Martin Levy,"Six Benefits of IPv6," Network Computing,
June 2011;www.networkcomputing.com/ ipv6/230500009
[15]Silvano Gai, IPv6: The New Protocol for Internet and
Intranets, 2007;www.ip6.com/us/book/
[16]John Amoss and Daniel Minoli, Handbook of IPv4 to IPv6
Transition: Methodologies for Institutional and
Corporate Networks, CRC Press, 2008.
[17]CISCO,"IPv6 Tunnel Through an IPv4 Network," August
2006;www.cisco.com/en/US/tech/tk872/
technologies_configuration_example09186a00800b49a5.
Shtml
[18]R. Hinden and S. Deering, "IP Version 6 Addressing
Architecture" (Internet RFCs RFC 1884), 1995;
http://tools.ietf.org/html/rfc4291
[19]Irene Katzela, Modelling and Simulating Communication
Networks: A Hands-On Approach Using OPNET, Prentice
Hall, 1999.
[20]Potaroo, "IPv4 Address Report," 2012;
www.potaroo.net/tools/ipv4/ index.html
[21]OPNET Technologies, "OPNET MODELER 16.0," 2010;
http://www.opnet.com/university_program/
94

Out

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Out

Caricato da

Copyright:

Formati disponibili

ABSTRACT

PERFORMANCE ANALYSIS of IPv4 VERSUS IPv6 IN A SIMPLE CAMPUS

Transfer Protocol (FTP) has been simulated in the above

Video Conferencing is also simulated in the

above mentioned network and investigation of end-to-end

results obtained from OPNET simulation of FTP show that an

Similarly results obtained from the

OPNET simulation of video conferencing show that

PERFORMANCE ANALYSIS of IPv4 VERSUS IPv6 IN A SIMPLE CAMPUS

By Vinay Kumar Muniyappa

UMI Number: 1517745

All rights reserved

Shivamallu, Arvind Pal Singh, Saketh Peri, Sai Raghuveer,

2. IPv4 VERSUS IPv6

IPV4 Packet and Field Descriptions

Simulation of IPv4 and IPv6 Networks with FTP

A. CONFIGURING FTP IN OPNET MODELER

B. CONFIGURING VIDEO CONFERENCING WITH BACKGROUND

I. IPv4 packet format

2. IPv6 packet format

7. Simulation sequence editor

9. Project editor workspace

10. Menu bar

II. Shortcut menu

12. Status message bar

13. OPNET work flow

14. IPv4 vs. IPv6 throughput in simple network

15. IPv4 vs. IPv6 packet throughput in simple

16. IPv4 vs. IPv6 Ethernet delay in simple network

17. IPv4 vs. IPv6 throughput in campus network

18. IPv4 vs. IPv6 throughput in campus network

19. IPv4 vs. IPv6 packet throughput in campus

20. IPv4 vs. IPv6 Ethernet delay in campus

21. IPv4 vs. IPv6 response time in campus network

22. Packet delay variation in seconds without

23 . Packet end to end delay in seconds without

24. Packet delay variation in seconds with

25. Packet end-to-end delay in seconds with

26. Packet delay variation in seconds without

27. Packet end-to-end delay in seconds without

28. Packet delay variation in seconds with

29. Packet end-to-end delay in seconds with

30. Object palette

31. Experimental campus network

32. Application configuration attributes

33. FTP attribute and values table

34. Profile definition attributes

35. FTP attributes

36. Server configuration attributes

37. FTP service activation

38. Client configuration attribute

39. Application destination preferences

40. Actual name table

41. Client application supported profile

42. Client and server interface information table

43. IPv6 configuration table........

44. Global address table

45. TCP parameters

46. Bridge parameter table

47. Configuring performance metrics for IP cloud

48. IP cloud IPv6 interface information table

49. IP processing information table

50. IP interface information of IPv6 router (CSULB)

51. IP interface information of IPv4 router (CSULB)