1. P ART 4 T ESTING, O PTIMIZING AND D OCUMENTING Y OUR N ETWORK D ESIGN 1

2. C HAPTER T WELVE T ESTING Y OUR N ETWORK D ESIGN Copyright 2010 Cisco Press & Priscilla Oppenheimer 2

3. R EASONS TO T EST Verify that the design meets key business and technical goals Validate LAN and WAN technology and device selections Verify that a service provider provides the agreed- up service Identify bottlenecks or connectivity problems Determine optimization techniques that will be necessary Prove to yourself and your customers that your solution meets the goals and is the best choice. 3

4. T ESTING Y OUR N ETWORK D ESIGN Use industry testing services Build and test a prototype system Use third-party and Cisco tools 4

5. I NDUSTRY T ESTING S ERVICES Some respected, independent testing labs The Interoperability Lab at the University of New Hampshire (IOL) ICSA Labs Miercom Labs AppLabs The Tolly Group Suitable for simple, standard and test results published networks devices and network structures. But most of their tests are component test. 5

6. Prototype Network System A prototype is an initial implementation of a new system that provides a model on which the final implementation will be patterned. It’s functional but don’t need to implement a full-scale system. A prototype should verify important capabilities and functions that might not perform adequately. 6

7. Scope of a prototype system A prototype can be implemented in three ways Test network in a lab Integrated into a production network but tested during off hours Integrated into a production network but tested during normal business hours 7

8. C OMPONENTS OF A T EST P LAN Test objectives and acceptance criteria The types of tests that will be run Network equipments and other resources required Testing scripts The timeline and milestones for the testing project 8

9. T EST O BJECTIVES AND A CCEPTANCE C RITERIA (most important step) Specific and concrete Based on business and technical goals Clear criteria for declaring that a test passed or failed If appropriate, reference a baseline 9

10. Example of specific objectives and acceptance criteria Measure the response time for Application XYZ during peak usage hours. The acceptance criterion is that the response time must be <=0.1 s. 10

11. T YPES OF T ESTS Application response-time tests Throughput tests Availability tests Regression tests, makes sure the new system doesn’t break any applications or components that were known to work and perform to a certain level before the new system was installed. 11

12. R ESOURCES N EEDED FOR T ESTING Network topology and list of devices List of test tools Scheduled time in a lab either at your site or the customer’s site Power, air conditioning, rack space, and other physical resources Help from coworkers or customer staff Help from users to test applications Network addresses and names 12

13. E XAMPLE T EST S CRIPT Network ANetwork B Server 1 Firewall Protocol Analyzer Workstations Protocol Analyzer 13

14. E XAMPLE T EST S CRIPT ( CONTINUED ) Test objective. Assess the firewall’s capability to block Application ABC traffic, during both light and moderately heavy load conditions. Acceptance criterion. The firewall should block the TCP SYN request from every workstation on Network A that attempts to set up an Application ABC session with Server 1 on Network B. The firewall should send each workstation a TCP RST (reset) packet. 14

15. E XAMPLE T EST S CRIPT ( CONTINUED ) Test steps 1. Start capturing network traffic on the protocol analyzer on Network A. 2. Start capturing network traffic on the protocol analyzer on Network B. 3. Run Application ABC on a workstation located on Network A and access Server 1 on Network B. 4. Stop capturing network traffic on the protocol analyzers. 5. Display data on Network A’s protocol analyzer and verify that the analyzer captured a TCP SYN packet from the workstation. Verify that the network layer destination address is Server 1 on Network B, and the destination port is port 1234 (the port number for Application ABC). Verify that the firewall responded to the workstation with a TCP RST packet. 15

16. E XAMPLE T EST S CRIPT ( CONTINUED ) 6. Display data on Network B’s protocol analyzer and verify that the analyzer did not capture any Application-ABC traffic from the workstation. 7. Log the results of the test in the project log file. 8. Save the protocol-analyzer trace files to the project trace-file directory. 9. Gradually increase the workload on the firewall, by increasing the number of workstations on Network A one at a time, until 50 workstations are running Application ABC and attempting to reach Server 1. Repeat steps 1 through 8 after each workstation is added to the test. 16

17. T OOLS FOR T ESTING A N ETWORK D ESIGN Types of tools Network-management and monitoring tools Traffic generation tools Modeling and simulation tools QoS and service-level management tools http://www.topdownbook.com/tools.html 17

18. Benefits of using simulation software to test Lower overall cost Flexibility Scalability Control

19. Limitations of using simulation software to test the design: Limited functionality Unrealistic performance

20. S UMMARY An untested network design probably won’t work. It’s often not practical to test the entire design. However, by using industry testing services and tools, as well as your own testing scripts, you can (and should) test the complex, risky, and key components of a network design. 20

21. R EVIEW Q UESTIONS Why is it important to test your network design? Why is regression testing important? What are some characteristics of well-written acceptance criteria? What are some characteristics of a good network simulation tool? 21

22. C HAPTER T HIRTEEN O PTIMIZING Y OUR N ETWORK D ESIGN Copyright 2010 Cisco Press & Priscilla Oppenheimer 22

23. R EASONS TO O PTIMIZE Meet key business and technical goals Use bandwidth efficiently Control delay and jitter (essential for multimedia applications)delay and jitter Reduce serialization delay (T f Transmission time) Serialization Delay = Size of Packet (bits) / Transmission Rate (bps) Meet Quality of Service (QoS) requirements 23 Jitter is the undesired deviation from true periodicity of an assumed periodic signal in electronics and telecommunications

24. IP M ULTICAST H ELPS O PTIMIZE B ANDWIDTH U SAGE With IP multicast, you can send a high- volume multimedia stream just once instead of once for each user Requires support for Multicast addressing Multicast registration (IGMP) Multicast routing protocols 24

25. A F EW T ECHNOLOGIES FOR M EETING Q O S R EQUIREMENTS Internet Engineering Task Force Internet Engineering Task Force (IETF) controlled load service IETF guaranteed service IP precedence IP differentiated services 25

26. T RAFFIC S HAPING Manage and control network traffic to avoid bottlenecks Avoid overwhelming a downstream router or link Reduce outbound traffic for a flow to a configured bit rate Queue bursts of traffic for that flow 26

27. S UMMARY Optimization provides the high bandwidth, low delay, and controlled jitter required by many critical business applications To minimize bandwidth utilization by multimedia applications, use IP multicast To reduce serialization delay, use link fragmentation and compressed RTP To support QoS and optimize performance, use IP precedence, DSCP, 802.1p. advanced switching and queuing methods, RED, CAR, etc. 27

28. R EVIEW Q UESTIONS Why is it important to optimize your network? What has become of the IP type of service field? What are some methods for marking packets to identify the need for priority handling? Compare and contrast Cisco queuing services. 28

29. C HAPTER F OURTEEN D OCUMENTING Y OUR N ETWORK D ESIGN Copyright 2010 Cisco Press & Priscilla Oppenheimer 29

30. D OCUMENTING Y OUR D ESIGN If you are given a request for proposal (RFP), respond to the request in the exact format that the RFP specifies If no RFP, you should still write a design document Describe your customer’s requirements and how your design meets those requirements Document the budget for the project Explain plans for implementing the design 30

31. T YPICAL RFP R ESPONSE T OPICS A network topology for the new design Information on the protocols, technologies, and products that form the design An implementation plan A training plan Support and service information Prices and payment options Qualifications of the responding vendor or supplier Recommendations from other customers Legal contractual terms and conditions 31

32. Your report could be written in this way. C ONTENTS OF A N ETWORK D ESIGN D OCUMENT Executive summary Project goal Project scope Design requirements Current state of the network New logical and physical design Results of network design testing Implementation plan Project budget 32

33. 33

34. D ESIGN R EQUIREMENTS Business goals explain the role the network design will play in helping an organization succeed Technical goals include scalability, performance, security, manageability, usability, adaptability, and affordability 34

35. L OGICAL AND P HYSICAL D ESIGN Logical design Topology Models for addressing and naming Switching and routing protocols Security strategies Network management strategies Physical design Actual technologies and devices 35

36. I MPLEMENTATION P LAN Recommendations for deploying the network design Project schedule Including any dates and times for service provider installations Any plans for outsourcing Training Risks A fallback plan if the implementation should fail A plan for evolving the design as new requirements arise 36

37. P LAN FOR THE I NTERNETWORK I MPLEMENTATION Determine the best installation method: New installation Phased installation Complete replacement

38. P LAN FOR THE I NTERNETWORK I MPLEMENTATION Estimate timelines and resources

39. P LAN FOR THE I NTERNETWORK I MPLEMENTATION Create an installation schedule based on maintenance windows and downtime allowances

40. P LAN FOR THE I NSTALLATION Prepare the cost estimate by creating a Bill of Material: Order new and replacement parts Identify additional devices Identify upgrades to existing devices Identify software requirements

41. P RESENT THE N ETWORK P ROPOSAL TO THE C USTOMER Complete the proposal and develop a proposal presentation

42. P RESENT THE N ETWORK P ROPOSAL TO THE C USTOMER Present the network design proposal to the class and gain sign-off from the instructor: Include slides or other visual aids Incorporate presentation best practices

43. P OSSIBLE A PPENDIXES Detailed topology maps Device configurations Addressing and naming details Network design testing results Contact information Pricing and payment options More information about the company that is presenting the design Annual reports, product catalogs, press releases Legal contractual terms and conditions 43

44. S UMMARY When a customer provides an RFP, make sure to follow the prescribed format When not bound by an RFP, develop a design document that describes requirements, the existing network, the logical and physical design, an implementation plan, and the budget Be sure to include an executive summary In some cases, you should also include appendixes with detailed information 44

45. R EVIEW Q UESTIONS Why is it important to document your network design? Why is it important to submit an RFP proposal in the exact format prescribed? What are the major topics in a design document? What are some possible appendixes for a design document? 45

46. 46