Chapter 3 Characterizing The Existing Internetwork
Chapter 3 Characterizing The Existing Internetwork
Design
Chapter Three
1
Where Are We?
• Characterize the exiting internetwork in
terms of:
– Network infrastructure ( logical & physical )
– Addressing and naming
– Wiring and media
– Architectural and environmental constraints
– Health
2
Information to Collect
• A network map is the first thing to work on
• This map should include
– Geographic locations
– WAN connections between sites
• Labeled with type/speed/protocols/media/service provider
– Buildings and floors where equipment will be
– Connections between buildings and floors
• Labeled with type/speed/protocols/media
– Location of connection points like routers and
switches
– Internet connections
– Remote access points
3
Characterize internetwork
infrastructure
Logical structure:
• modularity
• hierarchy
• Topology
(Using tools for developing network maps:
HP open view, IBMTivoli, Whatsup Gold
, Microsoft Visio and others..)
Physical structure
4
Get a Network Map
Site A Site B
Fast Ethernet Fast Ethernet
50 users 30 users
Frame Relay Frame Relay
CIR = 56 Kbps CIR = 56 Kbps
DLCI = 5 DLCI = 4
Gigabit Company
HQ
Ethernet 16 Mbps
Cite C Token Ring
Fast Ethernet
75 users
FEP
(Front End
Processor)
Network map for an
electronics manufacturing company IBM
Mainframe
T1
Web/FTP server
Site D
Ethernet T1 Internet
20 users
committed information rate (CIR) 5
data link connection identifier (DLCI)
CIR & DLCI
• Committed Information Rate
CIR is the guaranteed bandwidth or data transfer rate
that a network service provider promises to provide for a
particular connection or service.
• Data Link Connection Identifier
DLCI is like a tag on data frames in Frame Relay
networks. It tells the network where to send the data by
identifying the specific virtual channel it belongs to
among many channels sharing the same physical
connection.
6
Characterize Addressing and
Naming
• IP addressing for major devices, client
networks, server networks, and so on
• Any addressing oddities, such as
discontiguous subnets?
• Any strategies for addressing and
naming?
– For example, sites may be named using
airport codes
• San Francisco = SFO, Oakland = OAK
7
Discontiguous Subnets
Area 0
Network
192.168.49.0
Router A Router B
Area 1 Area 2
Subnets 10.108.16.0 - Subnets 10.108.32.0 -
10.108.31.0 10.108.47.0
Wallplate
Telecommunications
Wiring Closet
wire length:
Less 100m
Vertical
Wiring
(Building
Backbone)
Campus
Building A - Headquarters Backbone Building B
10
Architectural & Environmental
Constraints
• Make sure the following are sufficient:
– Air conditioning
– Heating
– Ventilation
– Power
– Protection from electromagnetic
interference
– Doors that can lock
11
Architectural Constraints
• Make sure there’s space for:
– Cabling conduits
– Patch panels
– Equipment racks
• Absorption
• Refraction
• Diffraction
13
Wireless Site Survey
• Determine optimal locations for access points (APs)
based on coverage requirements.
• Evaluate signal propagation characteristics within
the deployment area to identify potential areas of
signal attenuation, reflection, or interference.
• Measure signal strength levels to ensure adequate
coverage
• Assess the accuracy and quality of the wireless
signal to ensure reliable connectivity and
performance.
14
Check the Health of the Existing
Internetwork
• Performance
• Availability
• Bandwidth utilization
• Accuracy
• Efficiency
• Response time
• Status of major routers, switches, and
firewalls 15
Develop baseline of network
performance
• Multiple days required to get accurate
analysis
• Avoid periods with large traffic- end of
financial year, Xmas time, . . Etc
– Latency increases in these times
• Do not have time to spend days on
analysis
– Other commitments
16
Network availability checking
• Gather any statistics that the customer has
on the MTBF and MTTR for the
internetwork as a whole as well as major
network segments
• Compare your stats with MTBF and MTRR
goals
– Customer expectations on MTBF and MTRR
17
Characterize Availability
Enterprise
Segment 2
Segment n
18
MTBF & MTTR
• MTBF ==> Mean Time Between Failures
• MTTR ==> Mean Time To Recovery
16:43:00
16:46:00
16:49:00
16:52:00
Time
16:55:00 Series1
16:58:00
17:01:00
17:04:00
17:07:00
17:10:00
0 1 2 3 4 5 6 7
Utilization
14:00:00
Time
15:00:00 Series1
16:00:00
17:00:00
21
• Changing time intervals to long periods
can be misleading and would give the
wrong results.
22
Measuring bandwidth utilization
Place a protocol analyzer or remote
monitoring ( RMON ) probe on each major
network segment and fill out a chart.
If the analyzer supports relative and
absolute percentages, specify the
bandwidth used by protocols as relative
and absolute.
23
Bandwidth Utilization by
Protocol
Relative Absolute Multicast
Broadcast
Network Network Rate
Rate
Utilization Utilization
Protocol 2
Protocol 3
Protocol n
Relative usage: how much BW is used by the protocol in comparison to the total BW currently in use on the segment.
Absolute usage: how much BW is used by protocol in comparison to the total capacity of the segment (100Mbps Fast
Ethernet)
24
Broadcast Vs Multicast
• Broadcast
A transmission to multiple, unspecified
recipients. On Ethernet, a broadcast packet is a
special type of multicast packet which all nodes
on the network are always willing to receive.
• Multicast addressing
Ethernet addressing scheme used to send
packets to devices of a certain type or for
broadcasting to all nodes. The least significant
bit of the most significant byte of a multi-cast
address is one. 25
Analyzing network efficiency
• Bandwidth utilization is optimized for
efficiency
– Applications and protocols configured to send
large amount of data per frame minimizing
number of frames and round-trip delays
required per transaction
– Receiver configured with large receive
window allowing to accept multiple frames
before sending acknowledgment
26
Network Efficiency:
Characterize Packet Sizes
28
Characterize Response Time
Response time measurements
X
Node A 80ms 90ms 70ms
X
Node B
Node C X
Node D X