Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Designing Real-World Networks - Lesson 1

Lesson 1
by

Nicola Arnoldi

on 14 October 2015

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Designing Real-World Networks - Lesson 1

Useful Informations
Text 2
Text 4
Designing Real-World Networks
a practical perspective
Faculty of Engineering
B.Eng - Telecommunications Engineering

Nicola Arnoldi, M.Eng.

Office hours: after class or by appointment
Contact: through the course moodle
Course material:
prezi e-handouts
Cisco CCENT Official Exam Certification Guide
http://docwiki.cisco.com/
Objectives
understand
troubleshoot
plan
design
Course Requirements
are you familiar with the ISO/OSI Stack?
can you explain how packets travel in an IP network?
tx data flows top-down
rx data flows bottom-up
layers exchange data only with adjacent layers
is destination IP in my ARP table?
send frame to destination MAC address
destination IP in my subnet?
yes
yes
ARP query
what's your MAC address?
no
send a frame to my DG
no
is my DG IP in my ARP table?
no
yes
What do you mean with Default Gateway?
a.k.a. Gateway of LAST RESORT
the DG is an IP address!
a SVI interface on a multilayer switch
an interface on a router
an IP shared between FHRP
(First Hop Redundancy Protocols)
devices are categorized on a
feature-basis
forwarding packets across different subnets
forwarding frames across collision domains
both forwarding across different subnets and c.d.
ROUTER
SWITCH
MULTILAYER
SWITCH
Collision Domain
Given two hosts,
A
and
B
.
Let's suppose that
A

and

B
transmit a frame
simultaneously at time
t
.
If the two frames collide, then A and B belong
to the same collision domain.
Broadcast Domain
Given two hosts,
A
and
B
.
Let's suppose that
A

transmits a broadcast IP packet.
If node B receives the packet, A and B belong to the same broadcast domain.
A group of devices that receive all broadcast messages
from members of that group is called a
broadcast domain. Network broadcast domains
typically are segmented with Layer 3 devices (routers).
every switch/router port is a collision domain
a hub does NOT break collision domains
(phy repeater)
a switch does NOT break broadcast domains
1 routed port = 1 subnet = 1 broadcast domain
collision domains are split by switches
broadcast domains are split by routers
requirement: different hosts to be configured on different IP subnets
do I need a separate infrastructure? (switches, cabling....)
NO!
Problem
Virtual LANs (VLANs)
logical separation between LANs in a switching domain
each VLAN is given an ID number (VLAN - ID) - 4 byte ethernet additional header
every switchport is configured to exchange traffic on a specific ID
inter-switch ports carry traffic from multiple VLANs (Trunk Ports - 802.1q)
same of having multiple switches (one for every VLAN)
how do we separate frames belonging to different vlans?
802.1q encapsulation
L2 Redundancy and STP
Switches
high port-density
don't care about source or destination IP!
which port should I forward this L2 frame to?
if destination MAC is not in the MAC Address Table
FLOOD IT ON EVERY PORT
Routers
low port-density
every port has one (or more) IP address
routes packets according to the Routing Table
Network Design Criteria
Performance
Robustness
ROI
throughput
latency
jitter
QoS
physical redundancy
geographical redundancy
L2/L3 redundancy
scalability
SLA
infrastructure lifetime
L2 redundancy
redundant links are loops
sometimes loops are unwanted...

Problems that a switch has to solve
mac address learning
end-station separation
forwarding and filtering
what is this piece of hardware capable of?
Full transcript