1. Campus Networking Best Practices GARNET/NSRC Workshop This document is a result of work by the Network Startup Resource Center (NSRC at http://www.nsrc.org). This document may be freely copied, modified, and otherwise re-used on the condition that any re-use acknowledge the NSRC as the original source.www.nsrc.org

2. Instructors Sebastian BuettrichIT University of Copenhagen/NSRC Kevin ChegeKENET – Kenya Education Network Trust Jose DominguezUniversity of Oregon/NSRC Steve HuterUniversity of Oregon/NSRC Dale SmithUniversity of Oregon/NSRC

3. Week at a Glance MondayIntroduction and Campus Network Overview TuesdayLayer 2 in-building concepts + Lab WednesdayNetwork Management and Monitoring + Lab ThursdayWireless FridayMore wireless

4. Daily Schedule 8:30am-10:30amMorning Session 1 10:30am-11:00amTea Break 11:00am-1:00pmMorning Session 2 1:00pm-2:00pmLunch 2:00pm-4:00pmAfternoon Session 1 4:00pm-4:30pmTea Break 4:30pm-6:00pmAfternoon Session 2

5. Today 8:30am-10:30amIntroduction 10:30am-11:00amTea Break 1:00am-1:00pmCampus core and Edge 1:00pm-2:00pmLunch 2:00pm-4:00pmCampus Cabling 4:00pm-4:30pmTea Break 4:30pm-6:00pmGhana campus networks

6. Why Are We Doing This? Our goal is to build networking capacity to support Research and Education –Remember: University = Research & Education The end game is regional, national, and larger Research and Education Networks (RENs) All RENs start with campus networks – they are the foundation of the REN

7. Justification Design Goals Reliability/Resiliency performance Manageability Scalability Layering

8. Why a REN? Enable research or services that could not be accomplished otherwise Cost Savings (buyers club) –Aggregate demand from multiple parties Vision of building alliances Successful RENs find that there are unanticipated benefits

9. REN Services What services are provisioned? Various models: –REN provides all Internet connectivity –Peering network to exchange traffic between members –Advanced peering network that might Develop or peer with a local commercial exchange Provide international connections (GEANT, etc) –Other services (video conferencing)

10. REN as Peering Network Internet REN Member

11. REN as Internet Service Provider Internet REN Member Internet exchange point Other REN Networks

12. RENs Around the World United States – Two National RENs –Both provide peering, but have access to lots of commercial peering and other REN peering US Regional RENs (usually one per state) –Different models, but many act as ISP Europe – GEANT across Europe –Peering only. Much more restrictive on commercial traffic

13. REN Financial Models Some pay for bandwidth per Mb (typical for ISP model only) Some have membership fee with “eat as much as you want” Some pay on size of connection and can “eat up to the size of the connection” Some have combination REN needs staff and circuits

14. GARNET What model makes sense? REN as peering network? –But, is there significant traffic between your Universities? –How about having the REN attach to a commercial peering point – access to Google REN as ISP requires trust and possibly different licensing

15. IP Addressing

16. Who Needs Public IP Space? Every campus must have Public IP address space – Where do you get it? GARNET needs to get IP address space If GARNET becomes ISP, it must have address space for its “customers” Any University can get their own IP address space.

17. Provider Independent IP Addresses What are provider independent IP addresses? –Public IP addresses that are not allocated to you by your Internet Service Provider. Can move between service providers without changing IP addresses If GARNET gets space, then addresses provided by GARNET is not provider independent

18. NAT is a reality NAT is common technique to reduce number of public IP addresses required NAT makes some things hard. –NAT breaks things like SIP (standard-based VoIP), which you have to work around –NAT translation device needs to know about applications. Stifles innovation. –Makes it harder to track down viruses and hackers

19. Who Needs Public IP and ASN? NREN –Must have both ASN and Public IP Campus Network –All campuses must have Public IP –Only need ASN if campus is multi-homed How much IP address space?

20. General Notes on IP Addressing IP version 4 addresses are 32 bits long IP address blocks allocated in powers of 2 –Blocks of addresses: 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, 4096, etc. CIDR notation: Address blocks are described with a notation of /number. /32 = 1 address, /31 = 2, /30 = 4, …. /24 = 256

21. Logical Network UbuntuNet University Member NREN University Member University Member University Member GEANT Other NREN Peers

22. Examining the NREN Internet Exchange NREN Member Campus Network Member Campus Network Member Campus Network UbuntuNet

23. NREN IP Addressing Every member connected with a point to point link –Every point to point link requires at least a /30 (4 addresses) NREN will address space for –Network management equipment –Services such as web, video conferencing Build a spreadsheet that details all the above

24. A Simple (Small) REN Example Member Campus Network Member Campus Network NREN Router Member Campus Network Member Campus Network NREN Router

25. Simple (Small) REN Example NetworkHosts CIDR blockSizeQtyTotal Point to point links2 /304728 Server network for network Mgmt40 /26641 Server network for Services40 /26641 Future network for services40 /26641 Future customer links2 /304416 Total236 You can't get a CIDR block of 236 addresses - rounding up, you get 256 or a /24

26. That isn’t all for the REN If the REN is going to act as an ISP –REN needs IP address space to allocate to customers. –If customers NAT, don’t need as much, but still need space. –In application to AfriNIC (www.afrinic.net), you will want to apply for space for your customers.www.afrinic.net

27. Campus Network IP Addressing Build a spreadsheet –One row for every building on your campus –Write down how many computers will be in each building –Round up to the nearest power of 2 –Add a row for servers –Add a row for wireless

28. A Simple Campus Example Core Router

29. A Simple Campus Example BuildingHostsCIDR BlockSizeQtyTotal Administration Building68 /251281 Physics Building220 /242561 Chemistry Building120 /242561 Computer Science200 /242561 Literature Building44 /26641 Server Network20 /2732264 Additional Buildings Medium100 /251283384 Additional Buildings Large200 /242562512 Wireless Network500 /235121 Total2432 Round 2432 up to the next CIDR block gives you 4096 or a /20

30. Applications to AfriNIC AAU has negotiated a 50% discount on fees with AfriNIC FRENIA funds are available to pay the other 50% for the first year (first year is free) There is no barrier to getting space When you apply for V4 address space, also apply for V6 space

31. Why Focus on Campus Networks? The Campus Network is the foundation for all Research and Education activity Without a good campus network, the Research and Education Network can’t work as well as it should Ad-hoc campus networks work OK with VSAT uplinks, but moving to high speed external links, they start to fail.

32. Why Focus on Campus Networks? Your campus network is the foundation that all services are provisioned on Ad hoc networks just don’t work well. They are unreliable and hard to maintain. If you don’t have a plan, how will you know where are going?

33. Campus Network Personnel Every campus should have at least one person who does nothing but work on the network. Not email systems. Not course management systems. Just networks. Larger campuses will need more University of Oregon has 9 people just doing networking plus 3 doing security (26,000 network connections) –Started small 20 years ago with 2 people

34. Questions?