ITEC 275 Computer Networks – Switching, Routing, and WANs

1. ITEC 275 Computer Networks – Switching, Routing, and WANs Week 2 Robert D’Andrea 2013 Some slides provide by Priscilla Oppenheimer and used with permission

2. Agenda • Review Chapter #1 • Business Goals • Business Constraints • Analyzing Technical Goals • Technical Goals • Technical Constraints • Introduce homework problems

3. Business Goals • Increase revenue • Reduce operating costs • Improve communications • Shorten product development cycle • Expand into worldwide markets • Build partnerships with other companies • Offer better customer support or new customer services

4. Top-Down Network Design Steps Analyze requirements Monitor and optimize network performance Develop logical design Develop physical design Implement and test network Test, optimize, and document design

5. Network Design Steps • Phase 1 – Analyze Requirements • Analyze business goals and constraints • Analyze technical goals and tradeoffs • Characterize the existing network • Characterize network traffic

6. Network Design Steps • Phase 2 – Logical Network Design • Design a network topology • Design models for addressing and naming • Select switching and routing protocols • Develop network security strategies • Develop network management strategies

7. Network Design Steps • Phase 3 – Physical Network Design • Select technologies and devices for campus networks • Select technologies and devices for enterprise networks

8. Network Design Steps • Phase 4 – Testing, Optimizing, and Documenting the Network Design • Test the network design • Optimize the network design • Document the network design

9. The PDIOO Network Life Cycle Plan Design Retire Optimize Implement Operate

10. Business Goals • Increase revenue • Reduce operating costs • Improve communications • Shorten product development cycle • Expand into worldwide markets • Build partnerships with other companies • Offer better customer support or new customer services

11. Recent Business Priorities • Mobility • Security • Resiliency (fault tolerance) • Business continuity after a disaster • Network projects must be prioritized based on fiscal goals • Networks must offer the low delay required for real-time applications such as VoIP

12. Business Constraints • Budget • Staffing • Schedule • Politics and policies

13. Technical Goals • Scalability • Availability • Performance • Security • Manageability • Usability • Adaptability • Affordability

14. Scalability • Scalability refers to the ability to grow Large companies expand more rapidly (users, applications, external networks, and new sites) • Expanding Access to Data 1970 -1980 data stored on mainframes 1980 – 1990 data stored on servers 1990 – present data stored on centralized mainframes and servers

15. Scalability • 80/20 Rule 80 percent local use and 20 percent external use At the present time, this rule is moving to the other side of the scale Some companies allow access with other companies, resellers, suppliers, and strategic customers. Introduction of extranet.

16. Scalability The business goal of making data available to more departments often results in a technical goal of using the mainframe as a powerful database server. • Some technologies are more scalable Flat network designs at Layer 2 switches, for example, don’t scale well Top-down network design is an iterative process. Scalability goals and solutions are reevaluated on a regular basis throughout the phases of the network design process.

17. Scalability • Extract from the customer information about their site - Number of sites to be added - What will be needed at each of these sites - How many users will be added - How many more servers will be added

18. Availability • Availability can be expressed as a percent uptime per year, month, week, day, or hour, compared to the total time in that period For example: • 24/7 operation • Network is up for 165 hours in the 168-hour week • Availability is 98.21% • Different applications may require different levels • Some enterprises may want 99.999% or “Five Nines” availability

19. Availability From a customers perspective, they want to know how much time the network is operational. Availability is linked to reliability. • Reliability addresses a variety of issues, which include accuracy, error rates, stability, and the time between failures.

20. Availability Availability is linked to redundancy. • Redundancy is a solution to a goal of high availability. In this manner, redundancy means adding duplicate links or devices to a network to avoid network outages. • Disaster Recovery Natural disaster – floods, dires, hurricanes, and earth quakes. Satellite outages – meteorite stormes, collisions in space, solar flares, and system failures

21. Availability Unnatural disaster – bombs, terrorist attacks, riots, or hostage situation. A main goal in the planning process would be to recognize which parts of the network are critical and must be maintained. The disaster recovery plan should include the keeping data backed up in one or more places that are unlikely to be affected by the disaster. Secondly, the technologies affected by the disaster should be switched to another site with similar technologies.

22. Availability • Testing It is important to require employees to be part of drills in the event of a disaster. This includes visiting remotes sites, and utilizing the available equipment. Keeping the remote equipment hardware and software at release levels similar to the main operations center. • Availability Requirements Uptime 99.95 % - network is down 5 minutes per week Uptime Five Nines - hard to achieve. Involves staff, equipment redundancy, and software.

23. Availability • 24/7 equals 8760 hours - Hot swappable boards - Triple Redundancy One active One active standby One standby or maintenance • Cost of Downtime • Each critical application should be documented how much money the company loses per minute/hour of downtime. • Third party network management

24. Availability • MTBF is mean time before failure • 4000 hours goal • MTTR is mean time to repair • One hour goal • MTBF and MTTR are used to calculate available goals when the customers wants to specify explicit periods of uptime and downtime, rather than a simple percent uptime value. Availability = MTBF / (MTBF + MTTR)

25. Network Performance • Common performance factors include • Bandwidth • Throughput • Bandwidth utilization • Offered load • Accuracy • Efficiency • Delay (latency) and delay variation • Response time

26. Network Performance • Throughput is the quantity of error-free data that is transmitted per unit of time. The assessment of the amount of data that can be transmitted per unit of time. Throughput is typically the same as capacity. Customers specify throughput goals in terms of number packets per second (pps). Vendor use pps based on their independent tests conduced on their product. Many internetwork devices can forward packets a theoretical maximum, which is called wire speed.

27. Network Performance • Bandwidth is a means capacity and is normally fixed. A measure of the width of a range of frequencies. Example: PVC pipe with water running through it. • Capacity depends on the physical ISO layer. The capacity of a network should be adequate to handle bursts of data loads.

28. Network Performance • Application Layer Throughput Vendors refer to the application layer throughput as goodput. Being called goodput, heightens the fact that it is a measure of good and relevant application layer data transmitted per unit of time. Throughput means bytes per second. Applications using throughput as goodput would file transfers and data base applications.

29. Network Performance • See page 37 for factors that constrain application layer throughput. • Accuracy is paramount when sending and receiving data. The data is expected to be identical when comparing both ends of a transmission. - Data errors - Power surges or spikes - Impedance mismatches - Poor physical connections - Failing devices - Noise from electrical devices

30. Network Performance • Accuracy refers to the number of error-free frames transmitted relative to the total number of frames transmitted. • Efficiency is a measurement of how effective an operation is in comparison to the cost in effort, energy, time, and money. • Response delays are expected to be minimal. • Variations in delay, called jitter

31. Network Performance - Jitter causes disruptions in voice and video streams. - Telnet protocol - Customer perspective on running any delay-sensitive applications

32. Network Performance • Propagation delay  is the amount of time it takes for the head of the signal to travel from the sender to the receiver (186,000 miles per second) • Serial delay is the time to put digital data onto a transmission line. • Packet-switching delay is the latency accrued when switches and routers forward data. • DRAM • SRAM

33. Network Performance • Queuing delay  is the time a job waits in a queue until it can be executed. A good rule is to inform the customer that they should experience less than delay 1 or 2 percent • Response time is the network performance goal that users are interested in. Users begin to get frustrated if the response is longer then 1/10th (100 MS) of a second.

34. Security • Focus on requirements first • Detailed security planning later (Chapter 8) • Identify network assets • Including their value and the expected cost associated with losing them due to a security problem. • Analyze security risks • Hackers compromise a network device, such as a switch, router, server, firewall, or IDS.

35. Network Assets • Hardware • Software • Applications • Data • Intellectual property • Trade secrets • Company’s reputation

36. Security Risks • Hacked network devices • Data can be intercepted, analyzed, altered, or deleted • User passwords can be compromised • Device configurations can be changed • Reconnaissance attacks • Denial-of-service attacks • Security should not disrupt the company’s business.

37. Manageability • Fault management – detecting, isolating, and correcting problems. • Configuration management – controlling, operating, identifying, and collecting data • Accounting management – accounting of network usage to allocate costs to network users and/or plan for changes in capacity requirements. • Performance management – analyze traffic and application behavior to optimize a network, meet service-level agreements, and plan for expansion. • Security management- Monitoring and testing security and protection policies, maintaining passwords, encryption keys, and auditing adherence to security policies.

38. Usability • Usability: the ease of use with which network users can access the network and services • Networks should make users’ jobs easier • Some design decisions will have a negative affect on usability: • Strict security, for example

39. Adaptability • Avoid incorporating any design elements that would make it hard to implement new technologies in the future • Change can come in the form of new protocols, new business practices, new fiscal goals, new legislation • A flexible design can adapt to changing traffic patterns and Quality of Service (QoS) requirements

40. Affordability • A network should carry the maximum amount of traffic possible for a given financial cost • Affordability is especially important in campus network designs • WANs are expected to cost more, but costs can be reduced with the proper use of technology • Quiet routing protocols, for example

41. Making Tradeoffs • Scalability 20 • Availability 30 • Network performance 15 • Security 5 • Manageability 5 • Usability 5 • Adaptability 5 • Affordability 15 Total (must add up to 100)100

42. This Week’s Outcomes • Business Goals • Business Constraints • Technical Goals • Technical Constraints

43. Due this week • 1-3 – Concept questions 1

44. Next week • Read Chapters3 and 4 in Top-Down Network Design • 2-1 – Concept questions 2

45. Q & A • Questions, comments, concerns?