Unit 5 Seminar

1. Unit 5 Seminar Unit 5 Chapter 6, plus Lab 10 for next week Course Name – IT482 Network Design Instructor – David Roberts Contact Information: droberts@kaplan.edu Office Hours: Tuesday 9:00 PM ET and Thursday 11:00 PM ET

2. UNIT 4 Review Covered last week in Seminar • Chapter 4 and 5 in the textbook • Chapter 4 – Flow Analysis • Individual and Composite Flows, Critical Flows, Identifying and Developing Flows, Data Sources and Sinks, • Flow Models and Flow Prioritization • Chapter 5 – Network Architecture • Network Architecture versus Network Design, Component Architectures, Reference Architectures, Architectural Models, Systems and Network Architectures

3. Unit 4 Review Quick check of Unit 4 • Quickly type your response to these three questions: • Example: type #1 and then your answer • #1 Describe a Data Source. Describe a Data Sink. • #2 What is a Flow Model? Name two. • #3 What does FCAPS stand for? What component is it a part of?

4. UNIT 5 - Chapter 6 Addressing and Routing Architecture Routed Protocol? Routing Protocol?

5. UNIT 5 - Chapter 6 Addressing and Routing Architecture Routed Protocol? IP, Appletalk, IPX Routing Protocol? OSPF, EIGRP, RIP, BGP What is the difference?

6. UNIT 5 - Chapter 6 Addressing and Routing Architecture Routed Protocol? IP, Appletalk, IPX Routing Protocol? OSPF, EIGRP, RIP, BGP What is the difference? Routed – protocol that carries data and addressing information from a device to another device Routing – carries routing information from router to router – information about which routes are available and the best routes for destinations

7. UNIT 5 - Chapter 6 Addressing and Routing Architecture Router – Protocol-Dependent or protocol-independent? How about a switch?

8. UNIT 5 - Chapter 6 Addressing and Routing Architecture Router – Protocol-Dependent or protocol-independent? How about a switch? Router is protocol-dependent and a switch is protocol-independent

9. UNIT 5 - Chapter 6 Addressing and Routing Architecture • Network Address - the address identifier used to locate a device on a network. An address mask identifies which bits in the address are considered part of the network and which are part of the device. • IPv4 • Decimal value 128 64 32 16 8 4 2 1

10. UNIT 5 - Chapter 6 Addressing and Routing Architecture Class B Address – 138.50.0.0/16 or 138.50.0.0/255.255.0.0 Broken into 24 bit networks 138.50.20.0 255.255.255.0 138.50.24.0 255.255.255.0 138.50.28.0 255.255.255.0 In the future 138.50.20.0 255.255.254.0 (which would encompass 138.50.20.0 through 138.50.21.255) Giving us useful space of 138.50.20.1 to 138.50.21.254

11. UNIT 5 - Chapter 6 Addressing Mechanisms • Classful Addressing – applying predetermined mask lengths to addresses to support a range of network sizes (A, B, C, D and E) • Subnetting – using part of the device (host) address space to create another level of hierarchy (subnet mask) • Variable-Length Subnetting – subnetting where multiple variable-length subnet masks (VLSM) are used to create subnets of different sizes • Supernetting – aggregating network addresses • Private Addressing and NAT – private IP addresses cannot be advertised or forwarded. NAT (Network Address Translation) maps IP addresses between public and private address space

12. UNIT 5 - Chapter 6 IP Forwarding If the destination address is local, then a lower-layer mechanism transports the packet. If the destination address is remote then a router can forward the packet toward its destination.

13. UNIT 5 - Chapter 6 Routing Fundamentals Routing – learning about reachability within and between networks and applying the information to forward IP packets to their destination

14. UNIT 5 - Chapter 6 Routing Mechanisms Establishing Routing Flows Begins with the flow analysis process. Consists of segmenting into functional areas (FA) and workgroups

15. UNIT 5 - Chapter 6 Routing Mechanisms Identifying and Classifying Routing Boundaries Routing boundaries are physical or logical separations of a network. Physical: isolation LANs or demilitarized zones (DMZs); physical interfaces or physical security Logical: functional areas (FA), workgroups, autonomous systems (AS)

16. UNIT 5 - Chapter 6 Routing Mechanisms Routing boundaries are physical or logical separations of a network. Hard Boundary versus Soft Boundary Hard: routing boundary where exterior gateway protocols (EGPs) communicate routing information between ASs Soft: routing boundary where interior gateway protocols (IGPs) communicate routing information between ASs

17. UNIT 5 - Chapter 6 Manipulating Routing Flows Default route - the route used when there is no other route for that destination Default route propagation - used to inform the network of the default path Route filtering - technique of applying route filters to hide networks from the rest of an AS. Router filter statement Route aggregation - technique of exchanging routing information between ASs – between service providers with transit networks or between large customers Policies – higher-level abstractions of the route filter technique – typically across hard boundaries

18. UNIT 5 - Chapter 6 Routing Strategies Evaluating Routing Protocols - determining the hierarchy and diversity of the network helps determine the complexity and features of the routing protocol – RIP versus OSPF Static routes – configured manually Stub network – only one path into or out

19. UNIT 5 - Chapter 6 Evaluating Routing Protocols Distance-vector or link-state routing algorithms Distance-vector routing algorithm - each router maintains the "distance" (a metric to weight each hop) between itself and possible destinations. A vector (or list) of these distances is computed from distance information received from other participating routers. Link-state routing algorithm - each router learns about itself, its links to next-hop routers (its neighbors), and the state of each link.

20. UNIT 5 - Chapter 6 Architectural Considerations Internal Relationships Example of interactions within Addressing/ Routing Architecture

21. UNIT 5 - Chapter 6 Architectural Considerations External Relationships - common external relationships between addressing/routing and each of the other component architectures: Interactions between addressing/routing and network management - can be used to configure boundaries for network management. Autonomous system (AS) boundaries indicate where one management domain ends and another begins. Interactions between addressing/routing and performance - can be closely coupled with addressing/routing through mechanisms such as MPLS, Differentiated and Integrated Services, and RSVP. Interactions between addressing/routing and security - security mechanisms are often intrusive as they intercept, inspect, and control network access and traffic.

22. Lab 10 Lab 10 in Experiments Manual Queuing Disciplines Order of Packet Transmission and Dropping The objective of this lab is to examine the effect of different queuing disciplines on packet delivery and delay for different services Various queuing disciplines can be used to control which packets get transmitted (bandwidth allocation) and which packets get dropped (buffer space).