NET 221 -Network Management & Design
Course code : NET221 .
Lecture 2: Introduction
Lecturer: T.CHAMDIMBA
Class: Year 2
Outline
▪ Systems Methodology
▪ Service Characteristics
▪ Service Metrics
A Systems Methodology (1/3)
▪ Viewing the network architecting and designing, that you designing
as a system
▪ System are sets of services
• levels of performance and function that are offered by the network to the
rest of the system
▪ System
• set of components that work together to support or provide connectivity,
communications, and services to users of the system
A Systems Methodology (2/3)
Generic components of a system(McCabe, 2007 –pp49)
A Systems Methodology (3/3)
Comparison of OSI Layers to System Levels (McCabe,2007, pp50)
Service Description
▪ Network services
• levels of performance and function in the network
▪ Two ways to view services
• Services being offered by the network to the rest of the system
• Sets of requirements from the network that are expected by the users,
applications, or devices
Service Requests and Requirements
▪ identified by the degree of predictability needed from the
service by the rest of the system
• Best of effort
• Predictable
• Guaranteed
Best of Effort Service
▪ No control of how the network will satisfy the service requests
▪ Rest of the system will have to adapt to the state of the network at
any given time
▪ Services will be both un-predictable and unreliable
▪ Variable performance across a range of values
▪ No specific performance requirements
Guaranteed Service
▪ These services are predictable and reliable
▪ They imply a contract between the user and the provider
▪ If a contract is broken the provider is accountable
• must account for loss of service
• Must compensate the user.
Predictable Services
▪ Lie between best of effort and guaranteed services
▪ They offer some degree of predictability and yet are not
accountable
▪ based on some prior knowledge of and control over the state of the
system
▪ services must have clear set of service requirements
▪ requirements must be configurable , measurable and verifiable
Service Characteristics
▪ Goal of network analysis
• characterize services so that they can be designed into the network
and purchased from vendors and service providers
▪ Examples
• Defining a security or privacy level for a group of users or an
organization
• Providing 1.5 Mb/s peak capacity to a remote user
• Guaranteeing a maximum round-trip delay of 100 ms to servers in a
server farm
▪ Measured using service metrics
Service Metrics
▪ Threshold values
• a value for a performance characteristic that is a boundary
between two regions of conformance
▪ Limit
• a boundary between conforming and non conforming regions
• taken as an upper or lower limit for a performance
characteristic.
• More dangerous than thresholds and result in severe actions
Performance Characteristics
▪ Capacity
▪ Delay
▪ RMA
Capacity
▪ A measure of the systems ability to transfer information
▪ Bandwidth
• Maximum amount of data that can be transmitted/transferred through
a channel in theory
• Think of it as the maximum throughput you can achieve
▪ Throughput
• How much data can be transferred from one location to another in a
given amount of time
▪ Goodput
• Application-level throughput (rate at which useful data is transferred in
a given amount of time)
• If network is not congested; goodput = throughput
Delay
▪ The time difference in the transmission of information
across the system.
▪ Sources of delay
• Propagation delay
• Transmission delay
• Queuing and processing delay
Delay continued…
▪ Measures
• RTT
• Length of tie it takes for a signal to be sent + length of time
it takes for an acknowledgement of the signal to be received
• Latency
• Measures the time it takes for some data to get to its
destination
RMA (1/3)
▪ Reliability
• Is a statistical indicator of the frequency of failures of the
network and its components
• requires some degree of predictability.
• The delivery of information must occur within well known time
boundaries.
• When delivery time varies greatly , the confidence in the network
is lost and hence is considered less reliable
RMA (2/3)
▪ Maintainability
• Is a statistical measure of the time to restore the system
to fully operational mode after it has experienced a fault
• Generally expressed as MTTR (mean time to repair)
• total time taken for detection, isolation of the failure to a
component that can be replaced, delivery of necessary parts
into the location of the failed component (logistic time),
replace the component, test it and restore full service
RMA (3/3)
▪ Availability
• Is a relationship between the frequency of mission
critical failures and the time to the restore service
𝐴 = 𝑀𝑇𝐵𝐹/ (𝑀𝑇𝐵𝐹 + 𝑀𝑇𝑇𝑅)
• 𝑀𝑇𝐵𝐹 = 𝑚𝑒𝑎𝑛 𝑡𝑖𝑚𝑒 𝑏𝑒𝑡𝑤𝑒𝑒𝑛 𝑓𝑎𝑖𝑙𝑢𝑟𝑒𝑠
• 𝑀𝑇𝑇𝑅 = 𝑚𝑒𝑎𝑛 𝑡𝑖𝑚𝑒 𝑡𝑜 𝑟𝑒𝑝𝑎𝑖𝑟
• 𝐴 = 𝑎𝑣𝑎𝑖𝑙𝑎𝑏𝑖𝑙𝑖𝑡𝑦
Performance Envelope
▪ a combination of two or more performance requirements,
with thresholds and upper and lower limits for each
Network Supportability
▪ The 80/20 rule applies here
• 80% of the cost of a network is its operation
and support
• Only 20% is the cost of designing and implementing it
▪ So, plan for:
• easy operation,
• maintenance,
• and upgrade of the network
Reference
▪ McCabe, James D. (2003). Network Analysis, Architecture & Design
(2nd Ed.). San Francisco: Morgan Kaufmann Publishers. [Chapters 1]
Thank you
Any More Questions?
