Network Analysis, Architecture, and Design, Third Edition

1. NETWORK
DESIGN & ANALYSIS
Dr. Liyth Nissirat

2. REQUIREMENTS ANALYSIS: CONCEPTS

3. REQUIREMENTS ANALYSIS: CONCEPTS
• USER REQUIREMENTS
• APPLICATION REQUIREMENTS
• DEVICE REQUIREMENTS
• NETWORK REQUIREMENTS
• OTHER REQUIREMENTS
• THE REQUIREMENTS SPECIFICATION AND MAP

4. USER REQUIREMENTS

5. USER REQUIREMENTS

6. REQUIREMENTS ANALYSIS: CONCEPTS
• USER REQUIREMENTS
• APPLICATION REQUIREMENTS
• DEVICE REQUIREMENTS
• NETWORK REQUIREMENTS
• OTHER REQUIREMENTS
• THE REQUIREMENTS SPECIFICATION AND MAP

7. APPLICATION REQUIREMENTS
• APPLICATION TYPES
• APPLICATION GROUPS
• APPLICATION LOCATIONS

8. APPLICATION TYPES
BASED ON SERVICE AND PERFORMANCE REQUIREMENTS, WE TYPE APPLICATIONS
AS MISSION-CRITICAL, RATE-CRITICAL, OR REAL-TIME/INTERACTIVE, WHERE
• MISSION-CRITICAL APPLICATIONS HAVE PREDICTABLE, GUARANTEED, AND/OR HIGH
PERFORMANCE RMA REQUIREMENTS
• RATE-CRITICAL APPLICATIONS HAVE PREDICTABLE, GUARANTEED, AND/OR HIGH-
PERFORMANCE CAPACITY REQUIREMENTS
• REAL-TIME AND INTERACTIVE APPLICATIONS HAVE PREDICTABLE, GUARANTEED,
AND/OR HIGH PERFORMANCE DELAY REQUIREMENTS

9. APPLICATION TYPES
RELIABILITY, MAINTAINABILITY, AVAILABILITY
(RMA)
A loss of any part of RMA in some applications may be serious or disastrous, such
as:
• Loss of revenue or customers. examples include applications that handle
lots of transactions and money, such as investment banking, airline
reservation, or credit card processing applications.
• Unrecoverable information or situation. telemetry processing and
teleconferencing applications are good examples of this type of reliability.
• Loss of sensitive data. examples include customer id/billing and intelligence
gathering applications.
• Loss of life. examples include transportation or health-care monitoring
applications.

10. APPLICATION TYPES
CAPACITY
• There are some applications that require a predictable, bounded, or high degree
of capacity. such applications, termed here rate-critical applications, include
voice, non-buffered video, and some “tele∗service” applications.
• Rate-critical applications may require thresholds, limits, or guarantees on
minimum, peak, and/or sustained capacities.
• In file transfer (such as in ftp running over TCP), the application receives
whatever capacity is available from the network, based on the state of the
network at that time as well as interactions between TCP and the lower layers.

11. APPLICATION TYPES
DELAY

12. APPLICATION GROUPS
• Telemetry/Command-and-control Applications.
• Visualization Applications.
• Distributed-computing Applications.
• Web Development, Access, And Use Applications.
• Bulk Data Transport Applications.
• Tele∗Service Applications.
• Operations, Administration, Maintenance, And Provisioning (Oam&p)
Applications.
• Client–Server Applications.

13. APPLICATION LOCATIONS

14. REQUIREMENTS ANALYSIS: CONCEPTS
• USER REQUIREMENTS
• APPLICATION REQUIREMENTS
• DEVICE REQUIREMENTS
• NETWORK REQUIREMENTS
• OTHER REQUIREMENTS
• THE REQUIREMENTS SPECIFICATION AND MAP

15. DEVICE REQUIREMENTS
• DEVICE TYPES
• PERFORMANCE CHARACTERISTICS
• DEVICE LOCATIONS

16. DEVICE TYPES

17. DEVICE TYPES

18. PERFORMANCE CHARACTERISTICS

19. PERFORMANCE CHARACTERISTICS
• Storage performance, that is, flash, disk-drive, or tape performance
• Processor (CPU) performance
• Memory performance (access times)
• Bus performance (bus capacity and arbitration efficiency)
• OS performance (effectiveness of the protocol stack and APIs, e.g., the number
of memory copies in the protocol stack, or the cost of execution of a given OS
on a particular processor)
• Device driver performance

20. DEVICE LOCATIONS

21. REQUIREMENTS ANALYSIS: CONCEPTS
• USER REQUIREMENTS
• APPLICATION REQUIREMENTS
• DEVICE REQUIREMENTS
• NETWORK REQUIREMENTS
• OTHER REQUIREMENTS
• THE REQUIREMENTS SPECIFICATION AND MAP

22. NETWORK REQUIREMENTS
• EXISTING NETWORKS AND MIGRATION
• NETWORK MANAGEMENT AND SECURITY

23. EXISTING NETWORKS AND MIGRATION
• Scaling dependencies
• Location dependencies
• Performance constraints
• Network, system, and support service dependencies
• Interoperability dependencies
• Network obsolescence

24. NETWORK MANAGEMENT AND SECURITY
There are four categories of network management tasks:
• Monitoring for event notification
• Monitoring for metrics and planning
• Network configuration
• Troubleshooting

25. NETWORK MANAGEMENT AND SECURITY
Network management requirements
• Monitoring methods
• Instrumentation methods. these include the network management protocols
(SNMPV3, CMIP, RMON), parameter lists (MIBS), monitoring tools, and access
methods
• Sets of characteristics for monitoring
• In-band versus out-of-band monitoring
• Centralized versus distributed monitoring
• Performance requirements

26. NETWORK MANAGEMENT AND SECURITY

27. REQUIREMENTS ANALYSIS: CONCEPTS
• USER REQUIREMENTS
• APPLICATION REQUIREMENTS
• DEVICE REQUIREMENTS
• NETWORK REQUIREMENTS
• OTHER REQUIREMENTS
• THE REQUIREMENTS SPECIFICATION AND MAP

28. OTHER REQUIREMENTS
• SUPPLEMENTAL PERFORMANCE REQUIREMENTS
• FINANCIAL REQUIREMENTS
• ENTERPRISE REQUIREMENTS

29. SUPPLEMENTAL PERFORMANCE
REQUIREMENTS
• Three characteristics of performance that reflect the customer’s impact on our
network design are operational suitability, supportability, and confidence.
• Operational suitability is a measure of how well our network design can be
configured, monitored, and adjusted by the customer’s operators.
• Supportability is a measure of how well the customer can keep the system
performing, as designed, over the entire life of the system.
• Confidence is a measure of the ability of the network to deliver data without
error or loss at the required throughput.

30. FINANCIAL REQUIREMENTS
• Funding is often bounded by an overall cost limit, consisting of both one-time
and recurring components.
• One-time costs are based on the actual planning and construction of the
network and consist of network architecture, design, procurement, deployment,
integration, and testing, and all hardware/software components, as well as the
initial installation or establishment of any services from service providers.
• Recurring costs are for tasks and items that are expected to occur or be
replaced/upgraded on a periodic basis.

31. ENTERPRISE REQUIREMENTS
• There may be times when you have to consider requirements for the network
that are commonly considered to be enterprise requirements, such as phone,
fax, voice, and video.
• The integration of these types of requirements over the same transmission
infrastructure as data is becoming common, and such enterprise requirements
need to be considered as part of the overall requirements for the network.

32. REQUIREMENTS ANALYSIS: CONCEPTS
• USER REQUIREMENTS
• APPLICATION REQUIREMENTS
• DEVICE REQUIREMENTS
• NETWORK REQUIREMENTS
• OTHER REQUIREMENTS
• THE REQUIREMENTS SPECIFICATION AND MAP

33. THE REQUIREMENTS SPECIFICATION AND MAP

34. THE REQUIREMENTS SPECIFICATION AND MAP

35. THE REQUIREMENTS SPECIFICATION AND MAP

36. THE REQUIREMENTS SPECIFICATION AND MAP

37. THE REQUIREMENTS SPECIFICATION AND MAP

38. THANK YOU