Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Best Practices:
Core and Edge Networks
Dale Smith
University of Oregon/NSRC
dsmith@uoregon.edu
This document is a result of work by the Network Startup Resource Center (NSRC at http://www.nsrc.org). This document may be
freely copied, modified, and otherwise re-used on the condition that any re-use acknowledge the NSRC as the original source.
Edge Networks
Make every network look like this:
Fiber link to
core router
Link to
another
building
Link to adjacent building
Switch in core
location
Cat5e
or fiber
Hub
Hub
Collision
Switch
Switch
Switch
VLANs
Virtual LANs reduce scope of broadcast
domain and separate traffic
Tagging identifying the VLAN
associated with a packet. Ports are
configured as Tagged or untagged.
Trunking Carrying traffic for multiple
VLANs on a single link. Must use tagging.
VLANs
Tagging on Trunks must tag
Single link carrying 3 VLANS
ARP
Address Resolution Protocol
Builds a mapping of IP address to
Ethernet Address
ARP Protocol
Broadcast ARP Request (who has this IP?)
Owner of IP address in ARP Request issues
ARP reply
ARP
10.0.0.1
00:00:11:00:00:aa
10.0.0.2
00:00:11:00:00:bb
10.0.0.3
00:00:11:00:00:cc
DHCP
Dynamic Host Configuration Protocol
Used to assign IP address and provide basic
IP configuration to a host.
Simple protocol
Client broadcasts a DHCP DISCOVER
Server(s) unicast back a DHCP OFFER
Client selects an offer and sends a REQUEST
Server sends back a DHCP ACK to client
Spanning Tree
Eliminates loops in Layer 2 networks
Several flavors
Original Spanning Tree 802.1D
Rapid Spanning Tree (RSTP) 802.1w
Multiple Spanning Tree (MSTP) 802.1s and
802.1Q-2003
Link Aggregation
Bonds multiple channels together to
provide more bandwidth
Issues:
Compatibility
How traffic is scheduled
3 separate links
aggregated as one
Failure Modes
ARP spoofing
Loops in your network
Rogue DHCP servers
Duplex mis-match
100Mbs late collisions and CRC
1000Mbs cant establish link
Core Network
Core Network
Reliability is the key
remember many users and possibly your whole network relies on the core
Core Network
At the core of your network should be routers you must
route, not switch.
Routers give isolation between subnets
A simple core:
Border Router
Firewall/
Traffic Shaper
Core Router
All router
interfaces on a
separate subnet
Central
Servers for
campus
Firewall/
Traffic Shaper
Core Router
All router
interfaces on a
separate subnet
Servers
in core
Border Router
Connects to outside world
RENs and Peering are the reason you need
them
Must get Provider Independent IP address
space to really make this work right
Internet
Exchange
REN
Campus
Network
Border
Router
REN switch
Traffic Shaper
Core
Router
Core Servers
Notes on IP Addressing
Get your own Public IP address space (get
your V6 block when you get your V4 one)
Make subnet IP space large enough for
growth
Use DHCP to assign addresses to
individual PCs
Use static addressing for switches,
printers, and servers
Core
Switch
Core Servers
Firewall/
Traffic Shaper
Core Switch
Local Internet
exchange switch
Core Router
Core Router
Border
Router
REN switch
Traffic Shaper
Core
Router
Core Servers
Questions?
This document is a result of work by the Network Startup Resource Center (NSRC at http://www.nsrc.org). This
document may be freely copied, modified, and otherwise re-used on the condition that any re-use acknowledge the
NSRC as the original source.