Riordan Network Report
Added on 2019-10-09
9 Pages2084 Words232 Views
RIORDAN NETWORK REPORT 1Riordan Network ReportNAMEAugust 14, 2016
RIORDAN NETWORK REPORTCompany BackgroundRiordan Manufacturing is a global plastics manufacturer that employs 550 people and is headquartered in San Jose, California, having facilities worldwide. (Tavangaran, 2016). To enable communication among these geographically spread offices we build upon our recommendations as in previous two reports.Network DesignEach office's LAN will be configured with a VPN router to serve as endpoints in the VPN architecture. Using their exiting Internet connection, the VPN router will create a per-session 'tunnel' in the public Internet, using which the encrypted user data is encapsulated in tunnel packets and routed as usual on the Internet. The Internet routes these packets as usual and the endpoint computers read the data encapsulated inside the tunnel packets, decrypt it and process it ("How VPN Works: Virtual Private Network (VPN)", 2016).Office 1 LANOffice 2 LANOffice 3 LANVPN GatewayVPN GatewayVPN GatewayInternetInternet
RIORDAN NETWORK REPORTWe expect our VPN to be set up for initial testing in under a week and after testing and removingany implementation issues, we expect the network to be usable in about three weeks.Design Approach and RationaleWe select Virtual Private Network (VPN) over public Internet under intranet site-to-site configuration for our company's networking requirement. Protocols used will be TCP/IP (Transmission Control Protocol/Internet Protocol), as this is the protocol of Internet and most computers and network devices are capable of communicating in this (Tyson & Crawford, 2011).We choose this solution as it is cost-effective, is scalable and provides security (by using encryption) and does not violate any network performance parameters like latency, response timeand jitter for our data requirements.Performance in Data Rate and Other ParametersAlso, latency in the recommended design is acceptable and is a tradeoff in our chosen network. We lose control of or a minimum Service Level Agreement (SLA) on latency as some users in the network may not have sufficient bandwidth. "Latency guarantees are hard to come by because they're hard to implement" ("The Solution - "How do I turn the network I've got into the network I need"", 2016).The response time of the recommended time is acceptable. We do not have a guarantee ofresponse time in our chosen network, due to the wide variety of speed and quality of the underlying Internet routes. We consider this a reasonable tradeoff since the company will primarily be sharing emails, files, and other non-live data.As per jitter, the recommendation meets this requirement as well. As mentioned earlier, the company is mainly working with data that is not latency sensitive, thus any jitter is unlikely to have any noticeable effect on user interface (Hruska, 2015).
End of preview
Want to access all the pages? Upload your documents or become a member.
Related Documents
Riordan Manufacturing Computer Network Reportlg...
|5
|1272
|118
Network Analysislg...
|6
|1286
|218
Riordan Network Security Recommendations Assignmentlg...
|5
|923
|161
Network Infrastructure Component 2022 Reportlg...
|10
|2182
|17
VPN Applications and Significancelg...
|8
|1128
|307
VPN Security Issues - CSC332 - Case Studylg...
|8
|3117
|62