Available online at www.sciencedirect.

com
Available online at www.sciencedirect.com
ScienceDirect
ScienceDirect
Procedia Computer Science 00 (2018) 000–000
Available online at www.sciencedirect.com
Procedia Computer Science 00 (2018) 000–000 www.elsevier.com/locate/procedia
www.elsevier.com/locate/procedia
ScienceDirect
Procedia Computer Science 135 (2018) 526–533

3rd International Conference on Computer Science and Computational Intelligence 2018

3rd International Conference on Computer Science and Computational Intelligence 2018
Design and Evaluation of Enterprise Network with Converged
Design and Evaluation of Enterprise Network with Converged
Services
Services
Giovanniaa, Nico Suranthabb
Giovanni , Nico Surantha
a,b
Computer Science Department, BINUS Graduate Program – Master of Computer Science,
a,b
Computer ScienceBina NusantaraBINUS
Department, University, Jakarta,
Graduate Indonesia,
Program 11480
– Master of Computer Science,
Bina Nusantara University, Jakarta, Indonesia, 11480

Abstract
Abstract
The need to run various media through one infrastructure is the primary reason of the emergence of converged network. The
The
reasonneed to run various
is because company media
wantsthrough one investment
to reduce infrastructureandismaintenance
the primary costreason
by of the emergence
investing on singleofintegrated
convergednetwork
network.rather
The
than traditional
reason is becauseseparated
companytelecommunication, broadcasting
wants to reduce investment and and internet network.
maintenance In this research,
cost by investing on singlewe use top network
integrated down network
rather
than
designtraditional
approach separated telecommunication,
to create converged broadcasting
network design and to
that tailored internet network.
fulfill the In thisfrom
requirement research, we and
business use technical
top downaspects.
network
It
design approach
is started to create
by analyzing converged
design network
requirement, design logical
perform that tailored to fulfilldesign,
and physical the requirement from
and perform business
design and Both
testing. technical
data aspects. It
and voice
traffic should
is started be working
by analyzing wellrequirement,
design in convergedperform
network. In order
logical and to optimize
physical the network
design, design,
and perform the quality
design testing.ofBoth
service
data(QoS) will
and voice
traffic
be should beIt working
considered. welltoinaccomodate
will be used converged network. In order
various kind to optimize
of traffic the network
in this network. design, the
Simulation and quality of service
experiment results(QoS)
show will
that
be considered.
the It will design
proposed network be usedcan
to accomodate various
satisfy required QoSkind of traffic service
of converged in this network.
network.Simulation andnetwork
The proposed experiment
designresults
alsoshow that
performs
better availability
the proposed compared
network designtocan
thesatisfy
existing network
required QoSdesign.
of converged service network. The proposed network design also performs
better availability compared to the existing network design.
© 2018 The Authors. Published by Elsevier Ltd.
© 2018
© 2018
This The
is an Authors.
open
The Published
accessPublished
Authors. by Elsevier
article under
by Elsevier Ltd.
the CC BY-NC-ND
Ltd. license (https://creativecommons.org/licenses/by-nc-nd/4.0/)
This is an open access article under the CC BY-NC-ND license (https://creativecommons.org/licenses/by-nc-nd/4.0/)
This is an and
Selection openpeer-review
access article under
under the CC BY-NC-ND
responsibility of the 3rdlicense (https://creativecommons.org/licenses/by-nc-nd/4.0/)
International Conference on Computer Science and Computational
Selection and peer-review under responsibility of the 3rd International Conference on Computer Science and Computational
Selection
Intelligenceand peer-review
2018.
Intelligence 2018. under responsibility of the 3rd International Conference on Computer Science and Computational
Intelligence 2018.
Keywords: Converged Network; Enterprise Network; Top-Down Network Design; QoS
Keywords: Converged Network; Enterprise Network; Top-Down Network Design; QoS

1. Introduction
1. Introduction
Today, IT is growing and becoming a necessity for the sustainability of the company's business operation. Every
Today,unit,
business IT ise.g.
growing
humanand becoming
resources, a necessity
finance, marketingfor the sustainability
uses of the company's
network connected applicationbusiness operation.
to perform Every
the business
business
operation.unit, e.g. human
It results resources, dependence
in increasing finance, marketing uses network
of business operationconnected application
to network to perform
infrastructure. Thethe business
various IT
operation. It results
infrastructures in increasing
in a company dependence
are almost entirely of businesstooperation
connected to and
the network network
makeinfrastructure. The various the
the network infrastructure IT
infrastructures in a company
basis for IT sustainability are the
within almost entirelyIt connected
company. occurs duetotothethenetwork
needs ofand makeapplications
certain the networkorinfrastructure
services that the
are
basis for ITorsustainability
distributed in the clientwithin
serverthe company.
model. It occursthe
For example, dueuse
to the needs of
of analog certainsuch
devices applications
as PABXorisservices that are
now starting to
distributed
change. or in companies
Various the client server model.toFor
have started example,
switch to thethe use of phones
IP-based analog known
devicesassuch
VoIPas(Voice
PABXover
is now starting
IP) or to
devices
change. Various companies have started to switch to the IP-based phones known as VoIP (Voice over IP) or devices
1877-0509 © 2018 The Authors. Published by Elsevier Ltd.
This is an open
1877-0509 access
© 2018 Thearticle under
Authors. the CC BY-NC-ND
Published license (https://creativecommons.org/licenses/by-nc-nd/4.0/)
by Elsevier Ltd.
Selection
This is an and
openpeer-review under
access article responsibility
under of the 3rdlicense
the CC BY-NC-ND International Conference on Computer Science and Computational Intelligence 2018.
(https://creativecommons.org/licenses/by-nc-nd/4.0/)
Selection and peer-review under responsibility of the 3rd International Conference on Computer Science and Computational Intelligence 2018.

1877-0509 © 2018 The Authors. Published by Elsevier Ltd.

This is an open access article under the CC BY-NC-ND license (https://creativecommons.org/licenses/by-nc-nd/4.0/)
Selection and peer-review under responsibility of the 3rd International Conference on Computer Science and Computational
Intelligence 2018.
10.1016/j.procs.2018.08.205
 Giovanni et al. / Procedia Computer Science 135 (2018) 526–533 527
2 Giovanni, Nico Surantha/ Procedia Computer Science 00 (2018) 000–000

called IP-Phone. This phenomena does not stop there, the camera devices like CCTV are also converted into IP-
based device. The use of voice over IP (VoIP), video surveillance, smart meeting room that run using single
infrastructure can be the solution to reduce the investment cost but in the other side can increase the demand in the
network.
Converged network is a technology that can merge multiple heterogeneous networks1. Converged network
sometimes can be called as next generation network, that can transport multiple kind of traffic such as data, video,
and voice in the network 2. By implementing on single converged network, the company can reduce the investment
and maintenance cost. There are some works have been done on this topics. Ranaweera, et. al. proposed an
integrated LTE and 10GEPON network that can ensure that various desired quality of service (QoS) for various
applications can be satisfied 3. In another work, Jun Huang, et. al. proposed a QoS-aware Service composition
method for converged network-cloud service provisioning. They formulated the service composition as a variant of
multi-constrinted optimal path (MCOP) problem4. The simulation results show the proposed method achieves better
performance compared to the the current available MCOP approach. Finally, Chung-Shih Tang, et. al. proposed a
converged network architecture for ICT and IoT combined applications 5. In this research, they developed a testbed
based on the proposed architecture to perform experiment.
In this paper we propose the converge network design for a government related organization. The organization is
connected with more than 100 branch office located all over Indonesia. Therefore, the reliable and high performance
network is urgently required. The top down network approach is used in order to create the new network design. The
converged network term is very general, in order to specify the purpose we need to identify the requirement and by
using the top down approach, we can create optimal network design tailored the network to the requirements. The
approach is started by analyzing the design requirement, performing logical and physical design, and finally
performing evaluation of the design.
Implementation of Quality of Service (QoS) will be discussed to justify the level of service given by the design.
QoS is an ability of the network to convey with different treatment for specific traffic that already defined in order to
prioritize some specific one 6. QoS implementation goal is to increase the overall quality of the network by giving
priority to some specific traffic. The quantitative parameters in QoS are bandwidth, jitter, delay and throughput 7. In
the end of the paper, performance and availability evaluation is performed. Evaluation is performed through the
GNS3 simulation and experiment using the actual device.
Finally, The paper is organized as follow. The second section discusses the implementation of top down network
design methodology in our work. In the third section, we discuss about evaluation result and discussion. Finally, the
result of this paper is concluded in the fourth section.

2. Methodology

The top down network design approach is used in order to create the new design. This approach consists of four
phases, i.e. (1) analyze requirement, (2) logical network design, (3) physical network design, (4) test and optimize of
the network design8. In this paper, we limit our scope into the first three phases

2.1. Analyze Requirement

We begin the first phase by collecting information from the user. The user consists of IT division head and the
staffs. The information about existing logical and physical topology is collected along with future needs of the
company. From our client documentation we collect the information of current physical network and logical design.
From the meeting with IT division head and the staff, following information is collected.
1) Redundancy in the network already applied in devices by using HSRP and L2 redundancy
2) Redundancy in link already applied for connectivity to and from core switch. On the other hand, redundancy
in link between access switch is not applied.
3) Redundant of Internet Service Provider and WAN link already applied in the network.
4) The user access switch connectivity is cascading in the same floor, it can lead to single point of failure if
access switch that is in the middle fail to operate, the other access switch that relies in it will be disconnected
from the network too.
5) The used of VPN remote access is already implemented in the network by using VPN concentrator devices.
528 Giovanni et al. / Procedia Computer Science 135 (2018) 526–533
Giovanni, et. Al. / Procedia Computer Science 00 (2018) 000–000 3

6) Existing network already used VoIP & CCTV based on IP in the network but in small scale (most of the
users use PABX with different network) and for this purpose they are using different switch
7) User gateway lies in Core Switch, whereas server gateway lies in FWSM (Firewall module in the Core
Switch)

After discussion about existing network condition with the customers, there are some thing that needs to be
improved from the network,
1) VPN Remote Access – incompatibility issue with newer device/end-point (existing: using Cisco VPN Client
that only compaitible until Windows 7, newer Windows cannot run this application)
2) Voice traffic integration in the network for large scale deployment, we need to prepare replacement for
PABX in the network
3) Increase the availability of the network, we will redesign the network to minimize down time in case some
devices fails to run.
From this information, we make the new logical and physical design to achieve the three points that mentioned
above.

2.2. Logical Network Design

In this section, we discuss about the proposed logical network design. The logical network design process
includes the design of network topology, the selection of routing protocol, and the selection of redundancy method
for increasing availability We used hierarchical network design concept that has some benefits such it can reduce
network device load by limiting number of device interconnection and broadcast domain. It also can reduce cost by
using appropriate specification per layered device. Finally, it can reduce time to identify problem and resolution by
identifying per layer9
VPN- Remote Sites:
WAN/DMVPN
INTERNET RemoteAccess :
10.1.0.0/16
10.0.7.0/24
.66-126

ISP 1 ISP 2
Inside: 10.0.252.26 Inside: 10.0.252.30
Outside: IP Public Outside: IP Public DMVPN Tunnel0:
.26 .30 10.0.254.64/26
OUTSIDE-ISP1: .25
OUTSIDE-ISP2: .29
INTERNET FIREWALL
.65
Outside-ISP-1: 10.0.252.24/30
DMZ Outside-ISP-2: 10.0.252.28/30 VPN-HUB
DMZ: 10.71.252.20/30
10.0.4.0/24
VPN: 10.0.254.0/30
Mgmt: .1 VPN .2
Mgmt(Vlan
Stack 20) P2P VPN Hub-Internet-
: 10.71.0.3
10.71.0.13-16
VPN-RemoteAccess: 10.0.7.0/24 10.0.254.0/30
DMZ-A: 10.0.4.0/24DTBOT- Active : 10.71.252.10
Firewall: 10.0.254.0/30
DMZSW Inside: Stby : 10.71.252.11
10.0.252.8/29 Tunnel0: 10.0.254.64/26
Active: .18
Standby: .19
VLAN 303:
WAN-1 WAN-2
10.0.252.16/29 Inside: 10.0.255.0 Inside: 10.0.255.4
.17 Outside: IP WAN Outside: IP WAN
.2 .6
EDGE
.1 10.0.255.0/30
EDGE-InternetFW 10.0.252.16/29
EDGE-Core via BW: 10.0.252.8/29 .5 10.0.255.4/30
EDGE-WAN-1:Stack
10.0.255.0/30
EDGE-WAN-2: 10.0.255.4/30
.10

VLAN 303:
10.0.252.8/29

Bandwidth Management
Outside: VLAN 303
Inside: VLAN 302

WLC

MGMT: 10.0.2.10 VLAN 302:

10.0.252.8/29

.9

CORE
Mgmt(Vlan 20)
Server Farm Firewall : 10.71.0.1
NET MGMT 10.0.2.0/24
Stack WRLS MGT 10.0.100.0/24
DATA LT 1 10.0.101.0/24
.1
VOICE LT 1DTBOT-
10.0.201.0/24
VLAN Server B: 10.0.28.0/24 CORE
DATA LT 2 10.0.102.0/24 VOICE LT 2 10.0.202.0/24
VLAN ServerVlanC:301:
10.0.29.0/24 DATA LT 3 10.0.103.0/24 VOICE LT 3 10.0.203.0/24
VLAN 301: DATA LT 4 10.0.104.0/24 VOICE LT 4 10.0.204.0/24
.1 DATA LT 5 10.0.105.0/24 VOICE LT 5 10.0.205.0/24
VLAN Server D: 10.0.29.0/24
10.71.252.2

VLAN Server E: 10.0.40.0/24 .2 10.0.252.0/30 DATA LT 6 10.0.106.0/24 VOICE LT 6 10.0.206.0/24

10.0.255.16/30
VLAN Server X: 10.0.15.0/24 DATA LT 7 10.0.107.0/24 VOICE LT 7 10.0.207.0/24
Mgmt: DATA LT 8 10.0.108.0/24 VOICE LT 8 10.0.208.0/24
VLAN Server Y: 10.0.38.0/24
10.71.0.10-12
Vlan 302 : DATA LT 9 10.0.109.0/24 VOICE LT 9 10.0.209.0/24
VLAN Server Z: 10.0.42.0/24
10.71.252.5
.5 DATA LT 10 10.0.110.0/24VOICE LT 10 10.0.210.0/24
WRLS-STAFF 10.0.64.0/22 WRLS-GUEST 10.0.68.0/22

VLAN 300:
10.0.252.4/30
Lantai 1 Lantai 2 Lantai N

Net MGMT: 10.0.2.1X Net MGMT: 10.0.2.2X Net MGMT: 10.0.2.NX

.6
Data Lt.1 10.0.101.0/24 Data Lt.2 10.0.102.0/24 ... Data Lt.N 10.0.10N.0/24
Vlan 302:
Server Farm
10.71.252.6 Voice Lt.1 10.0.201.0/24 Voice Lt.2 10.0.202.0/24 Voice Lt.N 10.0.20N.0/24
WRLS MGMT 10.0.100.0/24 WRLS MGMT 10.0.100.0/24 WRLS MGMT 10.0.100.0/24
WRLS-STAFF 10.0.64.0/22 WRLS-STAFF 10.0.64.0/22 WRLS-STAFF 10.0.64.0/22
Net MGMT: 10.0.2.2 WRLS-GUEST 10.0.68.0/22 WRLS-GUEST 10.0.68.0/22 WRLS-GUEST 10.0.68.0/22
Mgmt:
VLAN Server A: 10.0.3.0/24
10.71.0.2
.1

Legends:
Layer 3
Layer 2 Access
Layer 2 Trunk
Tunnel

Fig. 1. Proposed Logical Topology

 Giovanni et al. / Procedia Computer Science 135 (2018) 526–533 529
4 Giovanni, Nico Surantha/ Procedia Computer Science 00 (2018) 000–000

In making the design of the network needs to be considered to minimize broadcast domain. The method is to
implement the concept of VLAN division. By using managed switches, we can create multiple VLANs inside a
switch while minimizing broadcast domains. Therefore, not all users are put into the same network. Application of
this VLAN can also be utilized when we have several different switches, we can unify the network although using
different switches. In making the design for this customer, utilized orientation of division of VLAN per floor (for
user). In this design is also separated between data, voice, and wireless, as well as in-band management of wired and
wireless devices.
In order to increase the availability of the network, we need to implement technology that support the high
availability such as Cisco Stackwise. The Cisco Stackwise technology is tested with the integration of link
aggregation control protocol (LACP). The performance of LACP and stackwise integration is compared and
discussed with the conventional way by utilizing HSRP and rely on spanning tree to achieve convergence in the
network if active device is failed.
For layer 2 spanning tree, we utilize the rapid spanning tree protocol (RSTP) that can achieve convergence time
faster than regular spanning tree protocol/ Per-VLAN Spanning Tree (PVST). We use separation of VLAN in order
to minimize broadcast domain, only appropriate switch has the VLAN that they needed to prevent unnecessary
transmission layer 2 packet. Layer 3 communication utilize dynamic routing protocol because of large number of
branch of this company. More than 100 branch exist when the proposal created for this customer. The routing
protocol used for this design is open shortest path first (OSPF) is link state routing protocol and its open standard, so
it can communicate with many different devices not only for specific vendor devices. The link state routing protocol
such as OSPF can give advantages such as preserve bandwidth by only sending advertisement if there is an update
in their link and they know the entire network to calculate the best path 10. From all the consideration described
above, we create a logical network design can be seen in figure 1. To be noted, lantai 1, 2, N correspond to floor 1,2,
N, respectively.

Wall Plate
TABLE 1 DEVICE SPECIFICATION

Device
Role Feature
Type
Wall Plate
Access-Switch
Dual Power Supply, Stackwise
Core Switch
support, 48 Port 10G SFP Support
Etherchannel
4x10Gbps
Access Point
Layer 3 Server Farm Dual Power Supply, Stackwise
Nth floor Switch Switch support, 24 Port 10G SFP Support
Edge-Switch Dual Power Supply, Stackwise
Internet Firewall
Edge Switch
support, 8 Port 10G SFP Support
Etherchannel
2x10Gbps

Etherchannel
24/48 Port with PoE Support,
4x10Gbps
Layer 2 Access Switch
Etherchannel
Core-Switch Etherchannel Stackwise support
Switch
4x10Gbps
2x10Gbps

DMZ Switch 24/48 Port, Stackwise support

Server Farm-
Internet Router Dual Power Supply
Etherchannel
4x10Gbps Server Farm
Switch Etherchannel Firewall

Router VPN Router Dual Power Supply

4x10Gbps

Etherchannel
2x10Gbps WAN Router Dual Power Supply
4U
Data Center
Internet Remote Access VPN, Firewall, IPS
Firewall built in, Active-standby mode
Legend: Security
Server Farm
FO Multimode (OM3/OM4)
Firewall, IPS Built-in, Cluster
UTP CAT6
Firewall
Stack Cable

Fig. 2. Proposed Cabling Design Infrastructure

2.3. Physical Network Design

This phase will begin by selecting the appropriate interconnection/conducted media for this new network design.
There are two options available, by using twisted pair or fiber optic. The fiber optic option is focused only on LED
(multimode) because the furthest distance in one building is not exceeding 300 meters. The comparison between the
two medias can be seen in table 1. Both of conducted media has advantage and disadvantage, but we need to
consider the long term planning for this case, because the network device usually will be rejuvenated every four to
seven years but the cabling infrastructure did not. Therefore, we’d rather go to use the LED fiber optic for the inter-
floor connectivity, and in the intra-floor connectivity we’ll go with UTP because the end device didnt have support
530 Giovanni et al. / Procedia Computer Science 135 (2018) 526–533
Giovanni, et. Al. / Procedia Computer Science 00 (2018) 000–000 5

for fiber optic media. The details of the cabling infrastructure can be seen in figure 2.
After completed the previous step, we continue to chose the device needed for this implementation. The device
will be differentiate to four category, there are layer 3 switch, layer 2 switch, router, and security devices. Table 2
will give the device specification that needs to be prepared for this implementation with the detailed specification
needed. We used Cisco Device to utilize the stackwise feature to achieve high availability.
The physical network design will be generated after completed the previous step. To achieve availability aspect,
we make sure that the device in backbone have redundant component and interconnection between them must have
redundancy.

Table 2 Device Naming & Hardware Detail Table 3 Device Naming & Hardware Detail for Performance Testing

Name Hardware Quantity Interval Number

Packet Frequenc
Codec Between of
WS-C3750X- Payload y
2 Packets Packets
CORE 24T-S
WS-C2960+ G.711 mu-
1 160 + 12 Once every
Access03 48TC-L Law 20 ms 1000
RTP bytes 1 minute
ISR4331- (g711ulaw)
1
Router SEC/K9 G.711 A-
160 + 12 Once every
FIREWALL CCR1016-12G 1 Law 20 ms 1000
RTP bytes 1 minute
(g711alaw)
G.729A 20 + 12 Once every
20 ms 1000
(g729a) RTP bytes 1 minute

3. Evaluation Result & Discussion

After we complete the design, we perform the the evaluation of the design. We evaluate the design of network in
terms of performance and availability. We perform the availability evaluation using GNS3 simulator. On the other
hand, we perform performance evaluation by simulating using the real device due to the limitation of GNS3
simulator in generating the data that resembles the actual situation.

3.1. Performance Testing

In order to test the performance of the network design, we create testing environment by using several device to
make sure that voice traffic can be accomodated in the design proposed to the customer. The reason we need to
create testing environment, because from the GNS-3 simulator the significant performance degradation happened.
The topology created for this testing purpose can be seen in figure 3. The details of devices used and the naming can
be seen in table 3.
CORE consist of two 3750 switches that configured as single logical by using stackwise feature from Cisco. We
use redundant link as device interconnection. Device interconnection is configured as one logical interface by using
link aggregation control protocol (LACP). LACP is shown by oval symbol in Fig. 3. The Firewall is a mikrotik
router with firewall capability.
Router is configured by using virtual routing and forwarding (VRF) feature. By using this feature, one router can
be simulated as five instances by separating the routing table using VRF. Link between Core and Access03 is
configured as a trunk to allow multiple VLAN accross this interface. It will be used to make multiple instances in
this topology. Figure 4 shows the logical topology of this design.
The reason we used router as endpoint because we need a way to obtain statistical data for specific traffic by
utilizing IP SLA feature in the Cisco Router. We need to make sure the reachability between VRF A to main VRF
in order to begin the testing and make sure the communication is sending and receiving correct VRF
IP SLA is used to measure the peformance for VoIP traffic. VoIP traffic is used for sampling in converged
 Giovanni et al. / Procedia Computer Science 135 (2018) 526–533 531
6 Giovanni, Nico Surantha/ Procedia Computer Science 00 (2018) 000–000

network because it has the tightest criteria in term of latency and jitter and should be prioritized in the network. By
using IP SLA UDP jitter operation, we can measure round-trip delay, one-way delay, one-way jitter, one-way packet
loss, and connectivity in network11. In order to simulate VoIP traffic we’re generating similar traffic with codec
G.711 mu-Law that is similar to one minute phone call. The source for this testing is VRF A and the destination is
Main VRF. Properties of this codec that IP SLA can be seen in table 3.

Eth3
Firewall .2 10.0.254.0/30 .1
Router
.1 Main VRF
G0/1/0: 10.0.254.1

10.0.255.0/30

CORE
.2

CORE
Stack

VLAN 10:Stack
10.0.10.1
VLAN 201: 10.0.201.1
VLAN 202: 10.0.202.1

Trunk
Vlan 10,201,202

Access03
VLAN 10:
10.0.10.103

Access03 Vlan 201 Vlan 201

F0/35
F0/36

Vlan 202 Vlan 202

Gi0/0/0
Gi0/0/1

Router Router Router Router

VRF A VRF B VRF C VRF D

Router Gi0/1/0 Gi0/0/0.201: 10.0.201.2/24 Gi0/0/0.202: 10.0.202.2/24 Gi0/0/1.201: 10.0.201.3/24 Gi0/0/1.202: 10.0.202.3/24

Fig. 3. Physical Topology using Cisco and Mikrotik Device Fig. 4. Logical Topology

We also activated SNMP parameter in the router in order to gather periodic data from IP SLA operation in this
router. The SNMP will be used for PRTG Network Monitor to gather periodic data in IP SLA operation. There are
two scenarios that will be tested in our environment. Both scenarios will be run in congested condition – the
bandwidth limit is 10Mbps and the bandwidth utilization is fluctuative between 8-10Mbps.
In our first experiment, we do not implement the QoS in the devices. All traffic sent through the mikrotik firewall
is treated equally including this voice traffic generated by IP SLA. We’ve monitored the output from PRTG
Network Monitor to get the periodic data per 1 minute so we can monitor the fluctuation of the network.
Latency report shown from figure 5 shows that the average latency per period (1 period = 1 minute) from source
to destination vary from 0-487 msec with average of 196 msec. From the opposite direction we can measure that the
latency can vary from 0-477 msec with average of 184 msec. Figure 6 shows the fluctuative value of average jitter
for source to destination per period can vary from 19 to 24 msec, with average of 22 msec and from the opposite
direction we can investigate the jitter vary from 17 to 20 msec with average of 18 msec. Figure 7 shows that the
packet loss can vary from 0% to 3,5% with the average of 2%.
Then, after we implement the QoS, we measure the latency, jitter and packet loss once again with the same
procedure. Figure 8 shows the latency report. In this figure we can see that latency from source to destination can
vary from 0 to 7 msec with average of 0 msec. And from opposite direction the latency can vary from 0 to 19 msec
with average of 0 msec. It shows improvement performance in latency after the QoS implemented in this network.

Fig. 5. Latency Report without QoS Fig. 6. Jitter Report without QoS
532 Giovanni et al. / Procedia Computer Science 135 (2018) 526–533
Giovanni, et. Al. / Procedia Computer Science 00 (2018) 000–000 7

Fig. 7. Packet Loss Report without QoS Fig. 9. Jitter Report with QoS

Fig. 8. Latency Report with QoS Fig. 10. Packet Loss Report with QoS

In figure 9, we measure the average jitter per period. For both direction, shown improvement of the average jitter
per minute is 1 msec, and average from aggregate record is also 1msec. The packet loss percentage shown in figure
10 shows improvement that the packet loss is dropped to 0% all the time. The result shows that the implementation
of QoS can improve the performance of network design in terms of latency, jitter, and packet loss.

Root Bridge CORE

Forwarding Stack
Trunk
Core-1 Core-2 VLAN 10: 10.0.10.1/24
HSRP
VLAN 10: 10.0.2.2/24
10.0.2.1
VLAN 10: 10.0.2.3/24
Trunk Trunk
Trunk
Forwarding
Trunk

Blocking

LACP LACP

ACCESS02 ACCESS03 Access02 Access03

VLAN 10: 10.0.2.102/24 VLAN 10: 10.0.2.103/24 VLAN 10: 10.0.10.102/24 VLAN 10: 10.0.10.103/24
Fig. 11. Simulation Based on Existing Network Fig. 12. Testing Environment Based on New Network Design

3.2. Availability Testing

We continue to test availability aspect of the network in using two separate environment. The first one is using
GNS3 to simulate the existing network (the setting can be seen in figure 11) and the second one we modify our
existing testing environment as shown in figure 12. We measure the downtime when failover occur in Core Switch
if the active one having issue such as reboot itself or failure that causes downtime for the active Core.
Ping is used to compare the convergence time in existing network and the testing environment using real network
devices. Before we start the scenario we already execute the ping for 1000 times in order to monitor the
convergence time of the network when failure occured. There are two scenarios that will be used, i.e. (1) Turn off /
unplug the forwarding interface; (2) Reboot the active core
The reason we choose to do something with the active core rather than standby one because we need to measure
the convergence time if the worst case scenario happened.
8 Giovanni, Nico Surantha/ Procedia Computer Science 00 (2018) 000–000
Giovanni et al. / Procedia Computer Science 135 (2018) 526–533 533

In our simulation based on existing network, we measure that the convergence time when we unplug the
connection between Core-1 and ACCESS03. We obtain the convergence time of 3 request timeout in 1000 times of
ping. It is approximately 6 seconds (1 timeout = 2 seconds) of timeout. And we try the second scenario, to reboot the
Core-1 (Active Core) and got the result of 18 request timeout in 1000 times of ping which are approximately 36
seconds of convergence time by utilizing rapid spanning tree.
In our testing environment to simulate the new network which utilize stack and LACP port channel that can be
seen in figure 12, we’ve done the same procedure. First procedure that we remove the connection between Core(1)
and Access03, we measure there is 1 request timeout that is 2 seconds. And we continue to reboot the active Core,
and got 2 request timeout. Summary of availability testing can be seen in table 4. In overall, the convergence time
can be improved by implementation of stackwise in new network.

Table 4
Result of Availability Testing
Convergence Time in Existing Convergence Time in New
No. Scenario
Network Network
1 Turn off the Active Core 18 RTO (36 Seconds) 2 RTO (4 Seconds)
Turn off link between Active Core and
2 3 RTO (6 Seconds) 1 RTO (2 Seconds)
Access03

4. Conclusion

Converged network that can transport multiple kind of traffic is believed to add more load to the network. One
way to ensure every service is delivered with different treatment tailored to the characteristic and needs for each
one is by using QoS. The implementation of QoS especially in congested or limited capacity link ensure the service
can be delivered as requested.The converged network design created already surpass the criteria to deliver voice
traffic according to our test, therefore we can propose this design to be implemented in the customers. The
availability aspect already improved from previous design that is implemented too by significant value if the active
core having trouble.

Acknowledgements

This publication of this paper is fully supported by Bina Nusantara University.

References

1. Argyroudis P, Mcadoo R, Toner S, Doyle L, Mahony DO. Analysing the Security Threats against Network Convergence Architectures.
2007;241–6.
2. Ayokunle OO. Integrating Voice over Internet Protocol ( VoIP ) Technology as a Communication Tool on a Converged Network in
Nigeria. 2012;2(11):829–37.
3. Ranaweera C, Wong E, Lim C, Nirmalathas A. Next generation optical-wireless converged network architectures. IEEE Netw.
2012;26(2):22–7.
4. Huang J, Liu G. QoS-Aware Service Composition for Converged Network – Cloud Service Provisioning. 2014;
5. Tang C-S, Chiang Y-K, Tsou Y-D, Ju J-H, Twu C-Y. A converged network architecture for ICT and IoT combined applications. In:
2016 18th Asia-Pacific Network Operations and Management Symposium (APNOMS) [Internet]. IEEE; 2016 [cited 2018 Jul 7]. p. 1–
4. Available from: http://ieeexplore.ieee.org/document/7737284/
6. Karakus M, Durresi A. Author ’ s Accepted Manuscript Quality of Service ( QoS ) in Software Defined Reference : J Netw Comput
Appl. 2016;
7. Newton PC, Arockiam L. A Quality of Service Performance Evaluation Strategy for Delay Classes in General Packet Radio Service.
2013;50:91–8.
8. Oppenheimer P, Design T-DN. Cisco Press. ISBN. 2011;1:57069–870.
9. Cisco Networking Academy. Routing and Switching Essentials Companion Guide. 1st ed. Indianapolis: Cisco Press; 2014. 864 p.
10. Teare D, Paquet C. Campus Network Design Fundamentals. Design. Cisco Press; 2005.
11. Cisco. Cisco IOS IP SLAs Configuration Guide. 12.4. San Jose; 2008.