Networkers 2003 - Deploying MPLS-VPN.pdf

(3698 KB) Pobierz
RST-2061 V2.PDF
Deploying MPLS-VPN
Session RST-2061
RST-2061
8181_05_2003_c2
© 2003, Cisco Systems, Inc. All rights reserved.
2
Copyright © 2003, Cisco Systems, Inc. All rights reserved. Printed in USA.
8181_05_2003_c2
376766839.006.png 376766839.007.png 376766839.008.png 376766839.009.png
Agenda
Prerequisites
Background
Theory
Practice
Route Reflectors
Carrier’s Carrier
Inter-AS
Import/Export Maps
RST-2061
8181_05_2003_c2
© 2003, Cisco Systems, Inc. All rights reserved.
3
Prerequisites
Must understand basic IP routing,
especially BGP
Must understand MLPLS basics (push,
pop, swap, label stacking)
RST-2061
8181_05_2003_c2
© 2003, Cisco Systems, Inc. All rights reserved.
4
Copyright © 2003, Cisco Systems, Inc. All rights reserved. Printed in USA.
8181_05_2003_c2
376766839.001.png
Recommended Reading
MPLS and VPN
Architectures by Jim
Guichard and Ivan
Pepelnjak
ISBN: 1-58705-002-1
RST-2061
8181_05_2003_c2
© 2003, Cisco Systems, Inc. All rights reserved.
5
Agenda
Prerequisites
Background
Theory
Practice
Route Reflectors
Carrier’s Carrier
Inter-AS
Import/Export Maps
RST-2061
8181_05_2003_c2
© 2003, Cisco Systems, Inc. All rights reserved.
6
Copyright © 2003, Cisco Systems, Inc. All rights reserved. Printed in USA.
8181_05_2003_c2
376766839.002.png 376766839.003.png
Background—Why Have MPLS-VPNs?
Tag switching came about from Ipsilon’s IP
switching
Cisco’s tag switching begat MPLS
One of the fundaments of tag switching was
label stacking
Label stacking allows the network to transport
data across it without needing routing
information in the core
Like a frame relay network doesn’t need IP routing
MPLS-VPN = label stacking + BGP extensions
RST-2061
8181_05_2003_c2
© 2003, Cisco Systems, Inc. All rights reserved.
7
Overlay vs. Peer Networks
Overlay network: customer’s IP network is
overlaid on top of the provider’s network
Provider’s IP transport (FR, ATM, etc.) creates
private IP network for customer
Most technologies that carry IP are p2p
Large p2p networks are hard to maintain
N^2 provisioning vs. inefficient routing
Even with hub and spoke, need lots of stuff
at the hub
RST-2061
8181_05_2003_c2
© 2003, Cisco Systems, Inc. All rights reserved.
8
Copyright © 2003, Cisco Systems, Inc. All rights reserved. Printed in USA.
8181_05_2003_c2
376766839.004.png
Overlay Network
Provider sells a circuit service
Customers purchases circuits to
connect sites, runs IP
N sites, (N*(N-1))/2 circuits for
full mesh—expensive
The big scalability issue
here is routing peers—
N sites, each site has N-1 peers
Hub and spoke is popular,
suffers from the same N-1
number of routing peers
Hub and spoke with static routes
is simpler, still buying N-1
circuits from hub to spokes
Spokes distant from hubs could
mean lots of long-haul circuits
Provider
(FR, ATM, etc.)
RST-2061
8181_05_2003_c2
© 2003, Cisco Systems, Inc. All rights reserved.
9
Peer Network
Provider and customer exchange IP routing
information directly
Customer only has one routing peer per site
Need to separate customer’s IP network from
provider’s network
Customer A and Customer B need to not talk to
each other
Customer A and Customer B may have the same
address space (10.0.0.0/8, 161.44.0.0/16, etc.)
VPN is provisioned and run by the provider
MPLS-VPN does this without p2p connections
RST-2061
8181_05_2003_c2
© 2003, Cisco Systems, Inc. All rights reserved.
1110
Copyright © 2003, Cisco Systems, Inc. All rights reserved. Printed in USA.
8181_05_2003_c2
376766839.005.png
Zgłoś jeśli naruszono regulamin