1 / 68

Campus Network Design

Brittany Cunningham Victor Antonov Trevor Marsh 8 December 2009 . Campus Network Design. Table of Contents. Design Decisions Population & Needs Wide-Area Network Routing Protocol Main Campus Satellite Campuses Remote Campuses. Remote Access VoIP Wireless

marci
Télécharger la présentation

Campus Network Design

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Brittany Cunningham Victor Antonov Trevor Marsh 8 December 2009 Campus Network Design

  2. Table of Contents • Design Decisions • Population & Needs • Wide-Area Network • Routing Protocol • Main Campus • Satellite Campuses • Remote Campuses • Remote Access • VoIP • Wireless • Security and Authentication • Network Management • Costs Evaluation Campus Network Design

  3. Brittany Cunningham Design Decisions

  4. Why a Hierarchical Design? • Route summarization • Distributed routing and switching • Simplified implementation and management • Broadcast domain control • Infrastructure changes • Quality of Service Campus Network Design

  5. Core and Distribution Layers Campus Network Design

  6. Victor Antonov Population and Needs Campus Network Design

  7. User Groups • Students • WWW, e-mail, multimedia access • Staff • E-mail, VoIP, WWW • Faculty • E-mail, VoIP, multimedia/WWW • Research • VoIP, e-mail, multimedia

  8. Students • Most student access will come from the dorms but some will be from academic access points • Student needs will be mostly in download bandwidth • Upload (disregarding video upload) is not expected to be great. Illegal upload needs to be discouraged.

  9. Student Traffic Estimations * Estimated 15,000 students Campus Network Design

  10. Public Access Traffic Estimations

  11. Staff / Administration • Least amount of traffic generated • VoIP telephony important • Higher UL rate because of audio and video links

  12. Staff / Administration

  13. Research • Most research organizations and universities are connected via Internet2 – a research network • Internet2 is developing and deploying advanced network applications and technologies for research and higher education • Internet2 recreates the partnerships of academia, industry, and government that helped foster today’s Internet in its infancy. • Research partnership gives access to (anonymized) traffic data unavailable from commercial networks

  14. Research Needs • Some areas of research can generate huge amounts of data • A separate line will be dedicated to the research needs and access to Internet2 • Needs for some areas of research are described in the next slides

  15. Physics Research • Dependant on the area of physics but usually produces large amounts of data • Russian example on High Energy Physics research • In 2003 produced ~30 TB • Predicted needed connectivity for 2006 was 1-2.5 Gbps • While a university might not produce all this data and exchange it with the world, it is safe to assume that in 2009-2010 all educational physics research might need ~2 Gbps connection • Some examples of physics research applications: • Large, high-quality images of the sky (astrophysics) • Complex 3D models (fluid/air dynamics)

  16. Biology/Medicine • Audio and visual information on species, habitats, conditions • DNA models, genetic sequences • Neuroinformatics - neuroimaging resources, including multi-scale imaging • Protein identification, characterization, quantification

  17. Other Areas • Other areas of research that will produce a lot of traffic over the network: • Weather science • High-performance computing • Chemistry • Geography

  18. Victor Antonov Wide-Area Network

  19. Wide-Area Network • Main Campus • 4 Secondary Campuses • In the same metro area as main campus • 50+ satellite campuses • Nationwide • Connections to the Internet and Internet2 • Serving main and secondary campuses • Redundancy of the WAN

  20. WAN Connection • Metro Ethernet technology to connect smaller campuses • EVPL (Ethernet Virtual Private Line) topology with point-to-point Ethernet virtual connections • Multiple EVCs to enable hub and spoke configuration • Bandwidth of 1Gb (which can be later scaled up for growing bandwidth needs) • Two providers for redundancy: COX and Verizon

  21. Metro Ethernet • Cost-effectiveness • Scalable bandwidth (1Gb and higher) • Low operating, maintenance, administration costs • Simplicity of native Ethernet format over traditional WAN technologies • Customer controls IP addressing and routing

  22. MAN Implementation • Layer 2/3 switches and/or routers • Highly redundant network • Full mesh topology • MPLS backbone • Costly • Highly reliable and scalable

  23. Multiprotocol Label Switching • Benefits of MPLS (basic) • Node-to-node connections (virtual links) • Highly scalable • Independent of any Data Link layer technology • Less overhead (no segmentation and reassembly) • Highly compatible with IP

  24. MPLS • Benefits of MPLS • Connections are unidirectional • A bi-directional traffic will use two connections which allows a link failure to ideally affect only one of the traffic directions • Multi-level tunneling • Fast recovery time – MPLS Fast Reroute offers recovery time of <50 ms • Geared towards real-time application (VoIP) support

  25. MPLS-based Ethernet MAN • Ethernet interface on fiber (100BASE-FX) • Ethernet over MPLS over Ethernet • Customers’ Ethernet packets are transported over MPLS and the service provider network uses Ethernet again as the underlying technology to transport MPLS • Fast Reroute Implemented

  26. Advantages of an MPLS-based Metro Ethernet • Scalability • pure Ethernet MAN are limited to a maximum of 4,096 VLANs for the whole network, when using MPLS, Ethernet VLANs have local meaning only • Resiliency • 30 to 1 sec convergence for pure Ethernet vs 50 msec for MPLS-based MAN (Fast Reroute) • Multiprotocolconvergence • an MPLS-based Metro Ethernet can backhaul not only IP/Ethernet traffic but virtually any type of traffic coming from customer networks or other access networks • End to End administration and maintenance • MPLS-based MAN offers a wider set of troubleshooting and OAM MPLS-based tools which can effectively troubleshoot and diagnose network problems • MAC ping, MAC traceroute, LSP ping etc.

  27. MAN Design • University is the provider itself • It will receive internet access and provide it to main and secondary campuses • Can provide access for closely related organizations – research foundation , R&D sites, high schools • Operates and administers its own network • Can freely implement policies • Main campus is closely connected with the core network • Customers are secondary campuses and an related organizations (see above)

  28. WAN Redundancy • Two providers of the metro-ethernet services • COX and Verizon • Ethernet solutions: EVPL (Ethernet Virtual Private Lines) topology with point-to-point Ethernet virtual connections (EVCs) • Multiple EVCs will be used to enable hub-and-spoke configuration to interconnect campuses.

  29. Satellite Campuses • Separate internet access • OC-1 lines offering ~50Mbps transmission speeds • Main BW consumer is distance learning video links • Assuming roughly 120 students per remote campus, this is 30 Mbps traffic at peak times • Access to university resources achieved through VPN

  30. WAN Overview MetroEthernet Area Network (main and secondary campuses) Cox Verizon Satellite Campuses

  31. Brittany Cunningham Routing Protocol

  32. Convergence What determines convergence time? • Time to detect path loss • Time to detect new best path • Time to update routes and tables Campus Network Design

  33. How does EIGRP help? • Stubby areas • Hierarchical design limits queries • Fast convergence • Cisco hardware is optimized for EIGRP Campus Network Design

  34. Route Summarization • Fewer queries to core • Allows traffic filtering • Control multicast traffic • Smaller routing tables • Naturally synergizes with hierarchical design Campus Network Design

  35. Keeping Multicasts to a Minimum • Rendezvous point near multicast source • Auto-rendezvous on all other L3 switches • IGMP snooping • No cross-campus VLANs Campus Network Design

  36. Brittany Cunningham Main Campus

  37. Main Campus Considerations • 15 buildings • Approximately 750 faculty and staff • Approximately 15,000 students • Electronic records • VoIP phone system • Complete wireless coverage • Research Campus Network Design

  38. Access Layer in a Single Building Campus Network Design

  39. Server Farm Campus Network Design

  40. Research Considerations • WAN links to partnered universities • High-performance computing clusters Campus Network Design

  41. Brittany Cunningham Satellite Campuses

  42. Satellite Campuses • 1-4 buildings each • Approximately 250 faculty and staff • Approximately 8,000 students • VoIP phone system • Complete wireless coverage • Backups from main server farm • WAN links to main campus Campus Network Design

  43. Brittany Cunningham Remote Campuses and Access

  44. Remote Campuses • 50+ remote sites • Approximately 2,000 students • Local staff with access to university resources Campus Network Design

  45. Remote Access • Faculty and Staff must have secure access to files and other resources • Access must be available anywhere with an internet connection Solution: VPNs Campus Network Design

  46. VPNs • Consider: • What resources should require a VPN? • What resources could be supported by web VPNs? • How can we make connecting as easy as possible? • Adaptive Security Appliance Campus Network Design

  47. Brittany Cunningham VoIP

  48. VoIP • Main and satellite campuses only • Traffic is in separate traffic VLAN • 802.1Q VLAN tagging to ensure QoS Campus Network Design

  49. Trevor Marsh Wireless

More Related