Ass4276 network designassignment

For Help Contact Information:

Harinath Reddy

Phone: +91-9502542081(IND) (Whats App, Viber)

phone: +1-2089086040 (US)

Email:  [email protected]

Network Design Project: Case study of

Everlast and Riddell Sport

1

Table of Contents

1. Introduction.........................................................................................................................................3

2. Existing and Future network design and problems..............................................................................3

2.1 Existing network design issues.....................................................................................................4

2.2 Proposed network design............................................................................................................4

3. Network architecture of proposed network diagram..........................................................................5

4. Everlast Corporate Intranet connections.............................................................................................7

5. Virtualized server environment...........................................................................................................9

6. Storage utilization issues...................................................................................................................11

7. IP addressing plan..............................................................................................................................13

8. LAN Connection Media......................................................................................................................15

9. Website Migration Issues..................................................................................................................17

10. Switching back to site....................................................................................................................18

11. Network security requirements.....................................................................................................19

References.................................................................................................................................................20

2

1. Introduction

Aim of the current report is to propose a complex network design environment, while discussing

the key network infrastructure requirements, LAN connections, Server, workstations, routers and

security. Case study of Everlast and Riddell sport is considered over the current network design

and it is assumed that, this proposal is developed to meet the future network enhancements of the

existing network of Everlast and adopt the complex design to meet the business and IT needs of

both the companies. From the case study problem given it is clear that, Everlast purchase another

company, Riddell sport and the main concern is to integrate and form a separate network and

LAN connectivity, such that networking requirements of both the companies will be solved

against the current problem associated. Riddell sport has a website www.riddellsport.com and

Everlast still lacks wen applications and thus this network design also considers the website,

domain and the corresponding hosting activities. It is assumed that a new domain and website

named www.everlast.com will be setup and now the current network consultant team is assigned

the job to review the existing network design and propose the future design and the key network

design is done with OPNET modeler and Cisco standard IP address allocation, domain

allocation, workstation and server configuration and the corresponding procedure is as explained.

2. Existing and Future network design and problems

3

2.1 Existing network design issues

From the case study of Everlast and Riddell sport following existing design considerations are

reviewed

Prior to the new proposed network design, Everlast has two building, where the corporate

office building was operated with 4 floors. First floor contains 30 workstations and they

are connected to a single switch and second floor contains 65 workstations, where 35 of

them support Engineering and 30 of them support HR departments respectively.

Corporate database applications are accessed via 6 servers and Email applications are

accessed via 4 physical servers and these two servers are also connected to same switch,

where the first floor workstations are connected. Additionally another router is also

connected to the switch and it is assumed that the server storage capacity is 2TB, out of

which 90% of the utilization is noticed.

Third and Fourth floor are empty as of now and are just used for storage, where the

manufacturing operations are supported by 12 different physical servers and the existing

problem with these servers is that, they are out of support and suffered with frequent

hardware failures. Thus now the network consultant team is advised to deploy cloud

based solutions to get rid of the existing hardware and server failures.

Riddell sport also has two buildings, where one acts as office building and other serves

the manufacturing needs over different locations. Office building has 2 floors and 20

workstations and they are connected to one switch via a single router on the first floor.

Second floor has the webhosting services, where load balancing is handled by 6 web

servers and 6 database servers. Due to the geographical constraints, building are located

faraway and thus proper virtualization of the hardware is required in this context and it is

suggested to deploy cloud based solutions

Network diagram of the existing network of Everlast Company over Philadelphia and Dallas are

as shown below and is developed using Microsoft Visio tool

4

Fig 2.1.1: Existing network design at Philadelphia

5

Fig 2.1.2: Existing network of Dallas office

From the above two network diagrams it is clear that, two networks at Dallas and Philadelphia

are designed using MS Visio tool. For the first network over Philadelphia, three floors are

designed based on the network architecture, where first floor is composed of 20 workstations for

HR department and they interconnected via LAN and is connected using Ethernet cabling.

Second floor is composed of a four important servers, where the first server represents the

application server and rest of the three servers are used to represent the web server, which are

connected to the Ethernet cabling and thus connected to the first floor as well. Third floor is

composed of main network components like web development team workstations, where the

entire network is connected to the Everlast network via the VPN cloud.

When the case with Dallas office network is considered, a typical 2 floor plan, where the first

floor has 20 workstations connected to each other via Ethernet LAN and second floor holds the

application and web servers respectively. All these servers are connected to the Admin control

Mainframe system and thus connected to the manufacturing site using typical VPN cloud

connectivity. For both the Philadelphia and Dallas office a single router and switch are used for

the required internal and external connectivity as shown in the network design. Actual design

flaws and the proposed network design for the Riddell and Everlast is as discussed below

6

2.2 Proposed network design

Following are the key aspects of proposed design challenges to the network consultant team and

ideas of both Everlast and Riddell sport companies

Current office building of Everlast and the corresponding operations are expanded to four

floors, where the HR team operations are moved to the 4th floor and a separate LAN setup

is used in this context.

Existing Riddell office will be moved to the current office building of Everlast and the

required interconnections will be done to integrate the current corporate operations

Corporate connectivity is enabled with new network connection infrastructure, where

additional internet backup is added in case of failures and the existing manufacturing

building will continue with the current operations with 12 workstations each

Hosting services to the Riddell domain will be shifted to the new location, where the

corresponding domain and server configurations will be done and both the domains of

Everlast and Riddell will be facilitated in this context.

Network administration will be done using additional 12 workstations and third floor of

Everlast building will be equipped with 10 more LAN workstations, which will be used

for both engineering and website development activities.

Unauthorized network access will be protected using the firewall routers, where the

current routers will be replaced.

Everlast intranet will be allocated Class B and Class C IP addressing, where the required

traffic capacity for LAN-to-LAN connectivity is given using the link configurations and

supports almost 1.5 Mbps.

Based on the existing network issues and proposed network goals, required corporate network of

Everlast and Riddell will be integrated and created, where the basic network connections are

simulated using MS Visio the proposed network design is as shown below

7

3. Network architecture of proposed network diagram

Based on the existing network and proposed network design it can be analyzed that,

configuration of additional LAN, servers, workstations, routers, switches and firewall need to be

done at the corporate office of Everlast intranet and internet level. Both the routers are connected

to the Ethernet switch and as per case study it is clear that HR department and Engineering

departments operate from the three floors and it is assumed over the current network design that,

four applications are used by both the departments and they are Email, Database, Print and Http

(Web)

All the four applications are created over the application configuration object shown in

the above network design and the profiles of the respective applications are configured

over the profile configuration object, by which the desired application traffic is floated

across the proposed intranet of Everlast

Email and Database backup is done over these servers with a time interval of 100sec and

the corresponding values are configured over profile configurations

Database application server and Print server are connected to the first router, to which the

first two floors are connected and thus this design assumes that workstations of first two

floors use the database and print applications, where the TCP traffic is integrated with the

respective application traffic

Email application server and HTTP (Web) application server are connected to the second

router, to which the third floor of the building is connected and this design assumes that

third floor users or workstations will generate and support the respective applications,

where the CBR traffic is integrated with the respective application traffic(Nitnaware,

2010) and the proposed network of four floors is as shown below

8

Fig 3.1: Final proposed network with 4 floors

4. Everlast Corporate Intranet connections

Based on the assumptions and case study network constraints, it is clear that, with the existing

issues of the current design, external network architecture aspects are considered to create the

desired intranet. From the case study it is clear that, there are 4 floors over the corporate building

and 3 floors are configured with the workstations, application servers, and routers and switch

respectively. Now the 4th floor is added with the HR department users and the respective intranet

network design with the current network design changes is as shown below

9

Fig 4.1: Everlast corporate intranet and manufacturing site connections

Both the offices of Philadelphia and Dallas and the manufacturing sites are connected via the

intranet. Firewall router is added to the current corporate network, where the web and application

server are connected via the MPLS VPN connectivity server. External router is connected to the

Dallas subsidiary office and the corresponding manufacturing site, as shown in the above

network design. 10BaseT LAN object shown in the above network diagram are used to represent

floors of the corporate office building and at the initial network design considered, first two

floors of the building are connected to one router and the third floor of the building is connected

to the other.

Two switches are connected the Hub and a separate instructor PC is also installed to the 4 th floor

of Everlast, which acts as the administration site. Within the IP address range allocated to the

workstations, number of required clients are added to each of the switch and entire architecture is

connected to the external cloud network, as shown in the above network diagram. Now the

required external connections are supported via the internet based cloud i.e. IP32Cloud object as

shown in the above. As the current design focus on the network integration of Riddell, external

10

applications like VoIP and Video Conferencing with the respective connections are added to the

4th floor HR department employees.

5. Virtualized server environment

As mentioned over the key issues of the current network of Everlast and Riddell, it is clear that,

due to the hardware failures and the required infrastructure support, hardware and server support

can be migrated to a typical virtualized server environment. From the literature proposed in this

context, virtualized server penetration will always save 50% of the workload on the current

hardware and server configuration used. Cloud based solutions can be used to virtualize the

infrastructure requirements of both Everlast and Riddell, where additional security and business

requirements can be handled without any extra throughput or bandwidth requirements to the

current network design (Zissis, 2012). Security is the main concern while moving the current

server and hardware to the cloud environment and in this context, the key issues considered are

as listed below

Security concerns of client

Security concerns of applications servers like database, email, print and Http

Anti-virus for the current workstations over all the buildings and the respective floors

Server isolation performance will be evaluated against the client consumption metrics

and thus in this context, following aspects will be considered over the server

virtualization over cloud process

o VMware ESXi and vSphere hypervisor will be used for required virtual appliance

for server environment

o Virtual appliance for the client access will be provided using the deployment

models of Xen hypervisor and Citrix XenServer

o Data storage and load issues on the virtual server cloud will be handled using the

Microsoft Hyper-V hypervisor

11

Entire virtualization server using the cloud solution will be done complex policy

management and the corresponding issues are as listed

o F-Secure Policy Manager interface and configuration which will support both the

virtual Windows and Linux environment (Katsaros, 2009)

Thus the proposed virtual server using cloud based solution is as shown below

Fig 5.1: Proposed virtualization server architecture of Everlast and Riddell (Katsaros,

2009)

6. Storage utilization issues

From the given current case of Everlast and Riddell network design; there are ample storage

utilization issues against providing the required capabilities to the clients from various buildings.

12

As it is assumed that, there are four important applications like Email, Http, Print and Database

over the four floors and additional workstations added to the corporate network, following

features of storage utilization solutions are considered

Open architecture can used to solve the current storage utilization issues and from the

above proposed virtualization server environment, following network storage aspects will

be considered

o Network storage protocols like iSCSI, FCoE and FC will be utilized for better

storage access via the proposed open architecture

o Virtual and Physical server environments will be configured with the protocols as

listed above

o Couple of complex enterprise operating systems support will be utilized to

support the storage requirements and will include the full versions and patches of

Microsoft Windows, AIX, HP-UX and Solaris (Druschel, 2010)

Data mobility models will be integrated over the virtual server environment configuration

done and as explained above. Required data of both the Everlast and Riddell will be

moved randomly over the SAN array for more replication and security integration. With

this level of data mobility and migrations, more number of application users and end-to-

end computing requirements will be handled. Equipment required in this context will be

ordered based on the current budget constraints and the choice can be made over

equipment end-of lease and class storage application options (Salehi, 2007)

Data replication against the WAN optimization technique will be adopted to resolve the

complex networking storage utilization problems. Any-to-any WAN optimization

technique by replicating the desired data on the vendor site can be adopted in this context.

MicroSan technology will be configured with the current storage utilization requirements,

where the extreme data traffic will be reduced to 95% against the bandwidth costs and the

respective monthly plans.

Stretched clustering technique is another important option available in this context, HA

(High Availability) configuration will be enabled. In general HA configuration can be

used to site-to-site disaster problems with the level of recovery options available based on

the actual latency requirements i.e. up to 5mi. Thus clustering can stretch geographically

13

up to 100 kilometer using the HA configuration technique and thus a better protection

mechanism can be integrated with the current storage utilization architecture.

Support from VMware will also be used to solve the issues associated with storage

servers on the Everlast, where the required configurations will be done using the VMware

site recovery manager against the number of disk arrays utilized against the VMware

Hardware Certification List processing

Extended support of VAAI will be integrated with VMware and thus the wide range of

storage arrays and the corresponding protocols will be enabled for better data mobility

and disparate storage environment.

Complex data storage utilization technologies like Automated DR and RecoverTrac will

be configured over the data arrays for automating the key tasks against the recovering

boundaries of business data and IT data as well. P2V (Physical to Virtual) and V2P

(Virtual-to-Physical) and V2V (Virtual-to-Virtual) storage recovery configurations will

be done to support varying network and storage issues (Foster, 2002).

Logical storage capacity of 3 TB to 500TB will be supported over the virtual storage

configuration and the required connectivity to the remote data storage server will be

established with iSCSI

Required download specifications will be enabled against the typical standards of NSS

(Network Storage Server) Gateway and NSS Virtual Appliance.

7. IP addressing plan

IP addressing plays the main role in defining the required class of IP addresses, subnet mask and

addressing of virtual machines and the required schema followed for Everlast and Riddell

companies is as discussed. Private IP addressing schema will be adopted for the current network

design as it is restricted to limited subnets, workstations and servers configured over the

buildings and the respective floors as discussed in the network design above. Required private

address to all the workstations over the subnets will be done using the Class A and Class B

private address range. Class B block set with in the range 189.16.0.0 to 189.31.255.255 against

16 private address blocks will be utilized in this context, where a total of 1048576 addresses will

14

be available by which all the workstations and servers will be assigned the required IPV4

addressing scheme (Sun, 2004).

Now the Class A private address block to the new set of floors over the Everlast buildings will be

done based on the 24 bit block set, where it is assumed that the IP address from the range of

10.0.0.0 to 10.255.255.255 along with the subnet masking will be allocated to the HR and

Engineering departments respectively and thus 16777215 private individual workstations can be

allocated with the respective Class A IP address. With the these public IP addresses allocation a

secured intranet connectivity among all the workstations and servers can be done and can’t be

accessed via the external internet due to the private Class B and Class IP addressing schema used

in this context. IP address blocks and the respective subnet mask configuration done for the

corresponding locations is shown in the below table

Philadelphia VLAN Subnet

First Floor All the workstations 10.10.10.0/12

Second Floor Email and Database server 10.10.11.0/12

Third Floor Application Servers 10.10.12.0/12

Fourth Floor VLAN Private Cloud 10.10.13.0/12

Dallas VLAN Subnet

First Floor All the workstations 10.10.11.0/12

Second Floor Email and Database server 10.10.12.0/12

Third Floor Application servers 10.10.13.0/12

Fourth Floor Switch and Router connections 10.10.14.0/12

15

Fig 7.1: IP address allocation methodology (Culler, 2007)

To access the Everlast and Riddell network from the public internet, current Class A and Class B

IP addressing done and thus always public Class IP addressing scheme is required in this context.

To meet the requirements of growing business conditions of the companies and deploy the public

networks, DMZ server configuration will be adopted to provide the required public internet

access. Public IP addressing schema will used to provide access to the external components like

Mails severs, DNS Servers, Web servers and other data servers, where the main constraint

considered here is to provide static IP address to the respective servers as it will again become

tedious job of the servers location change during course of time. Either static IP address

allocation or ISP automatic allocation will be adopted and configured based on the future plans

of network design (Culler, 2007). Part of Class C IP addresses will be purchased to provide

public internet access to the external users, where the required block of IP addresses will vary

within the range of 5, 10 and 25, where 256 variant class C configurations will be used in this

context. Traditional subnet settings will be done using the Class C network IP addressing, where

almost 254 addresses are split into 8 subnets those are allocated to 30 hosts respectively. VLSM

(Variable Length Subnet Masking) methodology will be followed to selecting the actual subnet

masking procedures and following routing protocols will be implemented (Fahiem, 2007)

OSPF (Open Shortest Path First)

EIGRP (Enhanced Interior Gateway Routing Protocol)

BGP 4(Border Gateway Protocol)

RIP 2 (Routing Information Protocol)

8. LAN Connection Media

Choosing LAN connection media against the required network design plays the key role in

accessing the further infrastructure and networking requirements as well. In general there variant

16

types of LAN media connections are available and were used for connecting the Ethernet

workstations, servers, routers and switches and thus Ethernet LAN connections are used over the

proposed network design. Thus initial Ethernet LAN connection requirements will be met using

the below physical layer options

802.3ae will be used against meeting the 10 Gigabit Ethernet

802.3u will be used against meeting the Fast Ethernet requirements

802.3ab will be used against meeting the Gigabit Ethernet over UTP

802.3z will be used against meeting the Gigabit Ethernet over Fiber (Chae, 2002)

All these Ethernet LAN cabling will be done against the typical OSI (Open System

Interconnection) model standards and the possible physical layer deployment that can be done

over the proposed Ethernet is as shown below

Fig 8.1: Ethernet Physical Layer architecture (Chae, 2002)

When the initial design constraints are ready against deploying the required Ethernet LAN

deployment more infrastructures, cost and controlling aspects are considered. Following Ethernet

technologies will be used over connecting the respective building, floors and the offices

10Mbps Ethernet speed will be configured at the access layer requirements and thus

optimize the LAN connectivity performance

Network devices and the access layer will be connected with Gigabit Ethernet, where

segmented level traffic aggregations can be done

17

Fast Ethernet will be deployed to avoid the associated bottleneck problems with client-

server performance and thus always an effective solution can be provided against slow

networks

Required connections between the application core and distributed layer of the current

network will be done using Gigabit Ethernet links, where dual links among the routers

and switches will also be done at this level

Switches and backbone network will be connected using the 10 Gigabit Ethernet, as it is

always required to implement fastest media at this level to support the complex switch

conditions (Maltz, 2009)

Thus based on the Ethernet connectivity requirements analyzed, the actual connection media that

will be used for the proposed network design is as listed

100BaseFX to connect the servers and routers

1000BaseT to connect the buildings and intranet cloud

1000BaseLX to connect the intranet to the public internet

10Base2 to connect the workstations and the routers

10BaseT to connect the servers and routers (Fossaceca, 2008)

9. Website Migration Issues and DSN Changes

Website migration is one of the complex issues while hosting the DSN server against meeting

the business needs of any organization. In general website migration from one host to other

consumer constraints against fast transfer, downtime and load balancing issues are considered

and these issues will be analyzed and resolved using the below mechanism for the current

network design proposal

To avoid the downtime of the website where the risks like loss of files and database, all

the required content of the current website to the new host prior to cancellation

18

All the required backup files will be downloaded to a virtualized server over cloud

environment, where the popular website control panel tools like PleskPanel and cPanel

will used in this context and thus, data backup and restoration can be done very quickly

Main page of the current website like public.html and the respective folders will be

floated over the associated subdomains and this type of backup will be done using the

MYSQL databases.

Restore and Backup will be done at two levels like to the home directory and MySQL

directory based on the number of backup download pages on the current website hosting

process

Security constraints against website migration will be handled using the database backup

file analysis, where the files containing the information of usernames and passwords will

be deleted over the new hosting site location (Wang, 2009).

To accomplish the changes with the DNS server, Everlast will use the new address

www.everlast.com and it an arbitrary IP address within the range 25.123.21.44 is

allocated to the corporate network of Philadelphia’s gateway

“CNAME” command of UNIX will be used to change the DNS and static IP addresses of

both the Riddell sport and Everlast, such that, the URL entry will be automatically

redirected to www.riddellsport.com and www.everlast.com respectively

Once the webpages, file, information and database is migrated to the new host, now the

new name servers will be assigned to these attributes respectively. Once the propagation

process is completed, any changes to the new website will be done and the corresponding

discussion is as given below

10. Switching back to site

19

In case of website fail or malfunction, it is always required to switch back to the old website,

where the actual hosting is done. This can be done using manually by using some of the tools

and the common procedure followed in this context is as listed below

Duplicator plugins available will be downloaded and installed, where once the

installation is activated required site package of the new and old website can be done

Any sort of future information in form of messages in case of website failure will be

added to the duplicator interface panel.

Now the duplicator plugin that is installed will scan all the files related to server, database

and other files and will detect the suspicious files and those won’t be reloaded in case of

website failure

A new and dedicated server will be configured to store the required information and zip

files of the current website and the IP address schema added will load the corresponding

server in case of current website failure and during the switching process (Wo, 2008)

Now the site installer will run and enable the required functionality and a sample

snapshot of the Wordpress duplicator is as shown below

Fig 10.1: Duplicator plugin configuration and installation process (Wo, 2008)

20

11. Testing the Website Migration issues

Whenever the primary website is migrated from a location to another location, lot of issues need to be considered and tested, which include the testing of both the primary and backup sites as well. All the incoming traffic to the websites is analyzed prior to the actual migration process, where the respective channels are tested to estimate the overall migration process. Typical binary GATE models can be used, where ON and OFF states of the website are indicated with 1 and 0 respectively. Multiple GATE conditions can be used in this context to analyze the required hosting services for both the locations. Switching among the sites of Dallas and Philadelphia will be done using the new domain configurations done for Everlast Company and thus the required public and private configurations will be done at the GATE switching conditions. Two GATES can be used in this context, where first GATE with 0 or ON conditions will represent Dallas and GATE with 1 or OFF will represent the Philadelphia locations respectively.

12. Network security requirements

As the current network of Everlast and Riddell is composed of database, email, print and Http

applications being deployed over number of workstations, server, routers and switches, providing

network security is one of the important network design issues (Gurung, 2001). It is assumed that

firewall based protection will be used to protect the network and the current Ethernet routers will

be replaced with the Firewall routers and the required configuration that will be done in this

context is as shown below

21

Fig 11.1: Firewall based protection added to the current network (Gurung, 2001)

Protection of network is always required when connecting to the external internet as the chances

of various attacks is high and thus in this context, one of the existing routers will be replaced

with firewall router SonicWALL 200 with IP address 10.120.16.1 as shown in the above figure

(Gurung, 2001)

References

Chang-Joon Chae. (2002). Optical CSMA/CD media access scheme for Ethernet over

passive optical network. Photonics Technology Letters, IEEE . 14 (5), p99-112

Culler. (2007). Extending IP to Low-Power, Wireless Personal Area Networks. Internet

Computing, IEEE . 12 (4), p50-72

22

Dimitrios Zissis. (2012). Addressing cloud computing security issues. Future Generation

Computer Systems. 28 (3), p16-23.

Fahiem, M. (2007). IP Address Space Management using Aggregated Fixed Length

Subnet Masking. Electrical Engineering, 2007. ICEE '07. International Conference

on, 10(1), 16-29.

Fossaceca. (2008). The PathStar access server: Facilitating carrier-scale packet telephony.

Bell Labs Technical Journal . 3 (4), P16-19

Foster. (2002). Decoupling computation and data scheduling in distributed data-intensive

applications. High Performance Distributed Computing, 2002. HPDC-11 2002.

Proceedings. 11th IEEE International Symposium on. 11 (1), p71-82.

Gurung. (2001). Automatic management of network security policy. DARPA Information

Survivability Conference & Exposition II, 2001. DISCEX '01. Proceedings. 2 (1), p116-

123

Katsaros. (2009). Cloud Computing: Distributed Internet Computing for IT and Scientific

Research. Internet Computing, IEEE . 13 (5), p54-59

Maltz, D. (2009). VL2: A scalable and flexible data center network. Proceedings of the

ACM SIGCOMM 2009 Conference on Data Communication, 51(2), 9-17

Nitnaware, D. (2010). Performance Evaluation of Energy Consumption of Reactive

Protocols under Self- Similar Traffic. International Journal of Computer Science &

Communication,1(1), 16-23

Peter Druschel. (2010). Storage management and caching in PAST, a large-scale,

persistent peer-to-peer storage utility. Proceedings of the eighteenth ACM symposium on

Operating systems principles. 12 (6), p212-218

Qing Bo Wang. (2009). GreenCloud: a new architecture for green data center.

Proceedings of the 6th international conference industry session on Autonomic

computing and communications industry session. 10 (3), p29-28.

Salehi, A. (2007). Infrastructure for Data Processing in Large-Scale Interconnected

Sensor Networks. Mobile Data Management, 2007 International Conference on, 36(8),

12-20

23

Tianyu Wo . (2008). HyperMIP: Hypervisor Controlled Mobile IP for Virtual Machine

Live Migration across Networks. High Assurance Systems Engineering Symposium,

2008. HASE 2008. 11th IEEE. 3 (1), p10-25.

Yuan Sun. (2004). A study of dynamic addressing techniques in mobile ad hoc networks.

Wireless Communications and Mobile Computing . 4 (2), p89-92.

#NetworkDesignAssignmentHelp

#CyberSecurityAssignment

#AssignmentHelp

#ManagementAssignmentHelp

#AssignmentsHelp

#ProjectsHelp

#HomeworkHelp

#DissertationsHelp

#ThesisHelp

#AcademicAvenue

#AcademicsHelp

#FrustratedWithAssignments

#MarketingAssignmentHelp

#ResearchProposalHelp

#CaseStudyHelp

#ResearchReportHelp

#SurveyHelp

24