WAN Architectures and Design
Principles
BRKRST-2041
Stephen Lynn
[email protected]
Consulting Systems Architect
2
Agenda
• WAN Technologies & Solutions
– WAN Transport Technologies
– WAN Overlay Technologies
– WAN Optimization
– Wide Area Network Quality of Service
• WAN Architecture Design Considerations
– WAN Design and Best Practices
– Secure WAN Communication with GETVPN
– Intelligent WAN Deployment
• Summary
Presentation_ID
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
3
The Architectural Continuum
Mid 1990s-Early
2000s
Early-Mid 1990s
Early
Networking
•
Flat/Bridged
•
Multiprotocol
•
Large Scale
•
Experimental
Networks
•
Business
Enabling
•
Mission Critical
Architectural
Lessons
•
Protocols required
for Scale &
Restoration
Architectural
Lessons
Architectural
Lessons
•
Path Diversity
•
Redundancy
•
Route First,
Bridge only if Must
•
Build to Scale
1960
© 2014 Cisco and/or its affiliates. All rights reserved.
•
Global Scale
•
IP Ubiquity
•
Advanced Techs
•
Business Survival
Planning
?
2010+
Time
BRKRST-2041
Today
Cisco Public
4
The Challenge
• Build a network that can adapt to a quickly changing business and technical
environment
• Realize rapid strategic advantage from new technologies
–
–
–
–
–
IPv6: global reachability
Cloud: flexible diversified resources
Bring Your Own Device (BYOD)
Internet of Things
What’s next?
• Adapt to business changes rapidly and smoothly
– Mergers & divestures
– Changes in the regulatory & security requirements
– Changes in public perception of services
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
5
Network Design Modularity
Data Center
/HQ
Core
Regional
hub
Distribution
Access
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Spoke
Site 1
Cisco Public
...
6
Regional
hub
Spoke
Site N
Spoke
Site 1’
...
Spoke
Site N’
Hierarchical Network Design
• Hierarchical design used to be…
– Three routed layers
– Core, distribution, access
– Only one hierarchical structure end-to-end
• Hierarchical design has become any design that…
–
–
–
–
Splits the network up into “places,” or “regions”
Separates these “regions” by hiding information
Organizes these “regions” around a network core
“hub and spoke” at a macro level
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
7
MPLS L3VPN Topology
Definition
Spoke
Site 1
Spoke
Site Y
Spoke
Site 2
SP-Provided
MPLS IP WAN
Spoke
Site X
Hub Site
(The Network)
Equivalent to
Spoke
Site 1
Spoke
Site N
Spoke
Site 2
Spoke
Site X
Spoke
Site Y
Spoke
Site N
• MPLS WAN is provided by a service provider
• As seen by the enterprise network, every site is one IP “hop” away
• Equivalent to a full mesh, or to a “hubless” hub-and-spoke
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
8
Virtual Routing and Forwarding Instance (VRF)
• Provides Network Virtualization and Path Isolation
VRF
VRF
VRF
VRF
VRF
VRF
 Virtualization at Layer 3 forwarding
 Associates to one or more Layer 3 interfaces on router/switch
 Each VRF has its own
Forwarding table (CEF)
Routing process (RIP, OSPF, BGP)
 VRF-Lite
Hop-by-hop
 MPLS VPN
Multi-hop
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
9
! PE Router – Multiple VRFs
ip vrf blue
rd 65100:10
route-target import 65100:10
route-target export 65100:10
ip vrf yellow
rd 65100:20
route-target import 65100:20
route-target export 65100:20
!
interface GigabitEthernet0/1.10
ip vrf forwarding blue
interface GigabitEthernet0/1.20
ip vrf forwarding yellow
MPLS VPN Design Trends
• Single Carrier Designs:
–
–
–
–
Enterprise will home all sites into a single carrier to provide L3 MPLS VPN connectivity.
Pro: Simpler design with consistent features
Con: Bound to single carrier for feature velocity
Con: Does not protect against MPLS cloud failure with Single Provider
• Dual Carrier Designs:
– Enterprise will single or dual home sites into one or both carriers to provide L3 MPLS VPN
connectivity.
– Pro: Protects against MPLS service failure with Single Provider
– Pro: Potential business leverage for better competitive pricing
– Con: Increased design complexity due to Service Implementation Differences (e.g. QoS, BGP AS
Topology)
– Con: Feature differences between providers could force customer to use least common denominator
features.
• Variants of these designs and site connectivity:
– Encryption Overlay (e.g. IPSec, DMVPN, GET VPN, etc.)
– Sites with On-demand / Permanent backup links
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
10
Single Carrier Site Types (Non-Transit)
AS 64517
CE5
CE3
 Dual Homed Non Transit
CE4
Only advertise local prefixes (^$)
Typically with Dual CE routers
BGP design:
AS 200
eBGP to carrier
iBGP between CEs
Redistribute cloud learned routes
into site IGP
CE2
CE1
Site IGP
 Single Homed Non Transit
C2
C1
AS 64512
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Advertise local prefixes and
optionally use default route.
Cisco Public
11
Dual Carrier: Transit vs. Non Transit
 To guarantee single homed site
reachability to a dual homed
site experiencing a failure,
transit sites had to be elected.
Cisco Public
CE4
Transit
AS 100
AS 200
CE2
CE1
Site
IGP
 To minimize latency costs of
transits, transits need to be
selected with geographic
diversity (e.g. from the East,
West and Central US.)
© 2014 Cisco and/or its affiliates. All rights reserved.
CE5
CE3
AS 64545
 Transit sites would act as a
BGP bridge transiting routes
between the two provider
clouds.
BRKRST-2041
AS 64517
C2
C1
AS 64512
Prefix X
Prefix Y
Prefix Z
12
Single vs. Dual Carriers
Single Provider
Dual Providers
Pro: Common QoS support
model
Pro: More fault domains
Pro: Only one carrier to “tune”
Pro: More product offerings to
business
Pro: Reduced head end circuits
Pro: Ability to leverage vendors
for better pricing
Pro: Overall simpler design
Pro: Nice to have a second
vendor option
Con: Carrier failure could be
catastrophic
Con: Increased Bandwidth
“Paying for bandwidth twice”
Con: Do not have another
carrier “in your pocket”
Con: Increased overall design
complexity
Con: May be reduced to
“common denominator” between
carriers
Resiliency Drivers vs. Simplicity
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
13
Metro Ethernet Service (L2VPN)
E-Line (Point-to-Point)
Replaces TDM private line
Point-to-point EVCs offer predictable
performance for applications
One or more EVCs allowed per
single physical interface (UNI)
Ideal for voice, video, and real-time
data
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public




14
E-LAN (Point-to-Multipoint)
Offers point to multipoint for any-toany connectivity
Transparent to VLANs and Layer 2
control protocols
4 or 6 classes of QoS support
Ideal for LAN-to-LAN bulk data
MPLS (L3VPN) vs. Metro Ethernet (L2VPN)
MPLS Layer 3 Service
MetroE Layer 2 Service
• Routing protocol dependent on the
carrier
• Routing protocol and network
topology independent of the
carrier
• Layer 3 capability depends on
carrier offering
• Customer manages layer 3 QoS
– QoS (4 classes/6 classes)
– IPv6 adoption
• Capable of transport IP and
none-IP traffic.
• Transport IP protocol only
• Routing protocol determines
scalability in point-to-multipoint
topology
• Highly scalable and ideal for large
network
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
15
Agenda
• WAN Technologies & Solutions
– WAN Transport Technologies
– WAN Overlay Technologies
– WAN Optimization
– Wide Area Network Quality of Service
• WAN Architecture Design Considerations
– WAN Design and Best Practices
– Secure WAN Communication with GETVPN
– Intelligent WAN Deployment
• Summary
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
16
Types of Overlay Service
Layer 2 Overlays
Layer 3 Overlays
• Layer 2 Tunneling Protocol—Version 3
(L2TPv3)
• IPSec—Encapsulating Security Payload
(ESP)
– Layer 2 payloads (Ethernet, Serial,…)
– Pseudowire capable
– Strong encryption
– IP Unicast only
• Other L2 overlay technologies –
OTV, VxLAN
• Generic Routing Encapsulation (GRE)
– IP Unicast, Multicast, Broadcast
– Multiprotocol support
• Other L3 overlay technologies –
MPLSomGRE, LISP, OTP
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
17
Tunneling
GRE and IPSec Transport and Tunnel Modes
IP HDR
IP Payload
GRE packet with new IP header: Protocol 47 (forwarded using new IP dst)
IP HDR
GRE
20 bytes
4 bytes
IP HDR
IP Payload
2 bytes
IPSec Transport mode
IP HDR
20 bytes
ESP HDR
IP Payload
20 bytes
BRKRST-2041
ESP HDR
54 bytes
© 2014 Cisco and/or its affiliates. All rights reserved.
ESP
Trailer Auth
Encrypted
Authenticated
30 bytes
2 bytes
IPSec Tunnel mode
IP HDR
ESP
IP Payload
IP HDR
Encrypted
Authenticated
Cisco Public
18
ESP
ESP
Trailer Auth
Locator/Identifier Separation Protocol (LISP)
Dynamic Tunneling Analogous to a DNS but for Network Infrastructure
 DNS resolves IP addresses for URLs
[ who is lisp.cisco.com] ?
DNS
Server
host
DNS
URL Resolution
[153.16.5.29, 2610:D0:110C:1::3 ]
 LISP resolves locators for queried identities
[ where is 2610:D0:110C:1::3] ?
LISP
router
LISP
Mapping
System
[ location is 128.107.81.169 ]
LISP
Identity-to-location
Map Resolution
This Topic Is Covered in Detail in BRKRST-3045
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
19
LISP Overview - Terminologies
 EID (Endpoint Identifier) is the IP address of a host – just as it is today
 RLOC (Routing Locator) is the IP address of the LISP router for the host
 EID-to-RLOC mapping is the distributed architecture that maps EIDs to RLOCs
ITR – Ingress Tunnel Router
ETR – Egress Tunnel Router
• Receives packets from site-facing interfaces
• Encap to remote LISP sites, or native-fwd to
non-LISP sites
• Receives packets from core-facing interfaces
• De-cap, deliver packets to local EIDs at site
Provider X
12.0.0.0/8
Provider A
10.0.0.0/8
xTR-1
ETR
ITR
ITR
packet flow
S
packet flow
ETR
ETR
ITR
ITR
xTR-2
Provider Y
13.0.0.0/8
Provider B
11.0.0.0/8
LISP Site 1
BRKRST-2041
xTR-1
ETR
© 2014 Cisco and/or its affiliates. All rights reserved.
xTR-2
LISP Site 2
Cisco Public
20
D
LISP Operation Example
LISP Data Plane - Unicast Packet Forwarding
Map-Cache Entry
3
EID-prefix: 2001:db8:2::/48
Locator-set:
12.0.0.2, priority: 1, weight: 50 (D1)
This policy controlled
by the destination site
13.0.0.2, priority: 1, weight: 50 (D2)
PI EID-prefix
2001:db8:1::/48
11.0.0.2 -> 12.0.0.2
LISP Site 1
6
2001:db8:1::1 -> 2001:db8:2::1
PI EID-prefix
2001:db8:2::/48
LISP Site 2
7
2001:db8:1::1 -> 2001:db8:2::1
2001:db8:1::1 -> 2001:db8:2::1
ETR
2
ITR
Provider X
12.0.0.0/8
Provider A
10.0.0.0/8
xTR-1
xTR-1
5
10.0.0.2
ETR
4
12.0.0.2
11.0.0.2 -> 12.0.0.2
ITR
2001:db8:1::1 -> 2001:db8:2::1
S
ETR
ITR
13.0.0.2
11.0.0.2
xTR-2
ITR
Provider Y
13.0.0.0/8
Provider B
11.0.0.0/8
1
DNS entry:
D.abc.com AAAA
BRKRST-2041
ETR
2001:db8:2::1
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
21
xTR-2
D
LISP Use Cases
IPv6 Transition
Efficient Multi-Homing
v6
PxTR
v4 v6
IPv4 Core
Internet
IPv6
Internet
v6 service
xTR
IPv4
Internet
LISP
Site
v6




IPv6-over-IPv4, IPv6-over-IPv6
IPv4-over-IPv6, IPv4-over-IPv4
Legacy Site
LISP Site
IP Portability
Ingress Traffic Engineering Without BGP
Data Center/ VM Mobility
Virtualization/Multi-tenancy
Legacy Site
LISP
routers
Legacy Site
Data
Center 1
Data
Center 2
Internet
PxTR
IP Network
LISP
routers
Mapping
DB
LISP
routers
VM move
West
DC

BRKRST-2041
East
DC

Large Scale Segmentation
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
22
VM
VM
a.b.c.1
a.b.c.1
Cloud / Layer 3 VM Move
EIGRP Over-the-Top (OTP) Overview
EIGRP Over-the-Top (OTP) extend end-to-end visibility over WAN
• EIGRP “end-to-end” solution with:
– NO routing protocol on CE/PE link
– NO special requirement on Service
Provider
– NO need for route redistribution
– NO special requirement on Enterprise
EIGRP RR
CE1
172.16.1.1
172.16.2.1
MPLS – L3 VPN
EIGRP
AS 100
192.168.2.1
BRKRST-2041
CE4
Control Plane: EIGRP “Over-the-Top” control plane
Data Plane: LISP encapsulation
© 2014 Cisco and/or its affiliates. All rights reserved.
EIGRP
AS 100
192.168.1.1
CE2


CE3
Cisco Public
23
EIGRP OTP Operation
Routing Table
10.10.20.0/24 next-hop 172.16.2.1 metric 100
10.10.20.0/24 next-hop 192.168.2.1 metric 200
Routing Table
10.10.10.0/24 next-hop 172.16.1.1, metric 100
10.10.10.0/24 next-hop 192.168.1.1, metric 200
EIGRP RR
SRC172.16.2.1
= DP
DST172.16.1.1
PE
PE
= CP
CE1
172.16.1.1
172.16.2.1
CE3
EIGRP
AS 100
EIGRP
AS 100
192.168.2.1
10.10.20.0/24
CE2
SRC192.168.2.1
BRKRST-2041
PE
PE
DST192.168.1.1
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
24
192.168.1.1
CE4
10.10.10.0/24
EIGRP OTP Enables Transport Agnostic Design
= DP
PE
PE
= CP
MPLS – L3 VPN
CE1
172.16.1.1
172.16.2.1
EIGRP
AS 100
CE3
EIGRP
AS 100
EIGRP RR
192.168.2.1
CE2
PE
PE
192.168.1.1
CE4
Backup Path





BRKRST-2041
Simple configuration and deployment for both IPv4 and IPv6
End-to-end routing domain convergence is not dependant on Service Provider
Routes are carried over the Service Provider’s network, not though it
Works with both traditional managed and non-managed internet connections
Complements an L3 any-to-any architecture (optional hair pinning of traffic)
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
25
VPN Technology
Positioning EzVPN/FlexVPN, DMVPN, GETVPN
EzVPN
FlexVPN
• LAN-like Encrypted VPN experience
for a diverse set of VPN client
including software clients
• Enhances interoperability by
consolidating tunnels from
teleworkers, retail stores, or branch
offices
• Centralized policy and management
control
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
DMVPN
GETVPN
• On-demand point to multipoint
Encrypted VPNs
• Simplified branch to branch
connectivity solutions
• OPEX reduction using zero-touch
deployment
• Resilient VPN solution combining both
crypto and routing control plane
• Tunnel-less Encrypted VPNs
• Any-to-Any VPN connectivity suitable
for IP VPNs
• No overlay routing
• Simplified QoS integration with Crypto
• Reduced latency and jitter due to
direct communication with no central
hub
• Eliminates P2P IKE relationship with
Group Encryption Keys
Cisco Public
26
Cisco Site to Site VPN Technologies Comparison
Features
DMVPN
FlexVPN
GET VPN
Infrastructure Network
 Public or Private Transport
 Overlay Routing
 IPv4/IPv6 dual Stack
 Public or Private Transport
 Overlay Routing
 Private IP Transport
 Flat/Non-Overlay IP
Routing
Network Style
 Large Scale Hub and Spoke
with dynamic Any-to-Any
 Converged Site to Site and
Remote Access
 Any-to-Any;
(Site-to-Site)
 Active/Active based on
Dynamic Routing
 Dynamic Routing or IKEv2 Route
Distribution
 Server Clustering
 Transport Routing
 COOP Based on GDOI
 Unlimited
 3000+ Client/Srv
 Unlimited
 3000+ Client/Srv
 3000 GM total
 1000 GM/KS
 Multicast replication at hub
 Multicast replication at hub
 Multicast replication in
IP WAN network
 Per Tunnel QoS, Hub to Spoke
 Per SA QoS, Hub to Spoke
 Per SA QoS, Spoke to Spoke
 Transport QoS
 Locally Managed
 Centralized Policy Management
 Locally Managed
 Tunneled VPN
 Multi-Point GRE Tunnel
 IKEv1 & IKEv2
 Tunneled VPN
 Point to Point Tunnels
 IKEv2 Only
 Tunnel-less VPN
 Group Protection
 IKEv1
Failover Redundancy
Scalability
IP Multicast
QoS
Policy Control
Technology
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
27
Dynamic Multipoint VPN (DMVPN)
• Branch spoke sites establish an IPsec tunnel to and
register with the hub site
SECURE ON-DEMAND TUNNELS
• IP routing exchanges prefix information for each site
ASR 1000
Hub
• BGP or EIGRP are typically used for scalability
• With WAN interface IP address as the tunnel
source address, provider network does not
need to route customer internal IP prefixes
• Per-tunnel QOS is applied to prevent hub site
oversubscription to spoke sites
Cisco Public
ISR G2
Branch 1
• When traffic flows between spoke sites, the hub
assists the spokes to establish a site-to-site tunnel
© 2014 Cisco and/or its affiliates. All rights reserved.
ISR G2
ISR G2
• Data traffic flows over the DMVPN tunnels
BRKRST-2041
Branch n
IPsec
VPN
28
Branch 2
Traditional Static Tunnels
DMVPN On-Demand Tunnels
Static Known IP Addresses
Dynamic Unknown IP Addresses
Dynamic Multipoint VPN (DMVPN)
Operational Example
Data packet
NHRP Redirect
NHRP Resolution
NHRP mapping
192.168.0.1/24
192.168.0.0/24  Conn.
192.168.1.0/24  10.0.0.11
192.168.2.0/24  10.0.0.12
Physical: 172.17.0.1
Tunnel0:
10.0.0.1
CEF FIB Table
10.0.0.11  172.16.1.1
10.0.0.12  172.16.2.1
CEF Adjacency
Physical: 172.16.2.1
(dynamic)
Tunnel0: 10.0.0.12
Physical: 172.16.1.1
(dynamic)
Tunnel0: 10.0.0.11
192.168.1.1/24
Spoke B
Spoke A
192.168.2.0/24  Conn.
192.168.0.0/16  10.0.0.1
192.168.1.0/24  Conn.
192.168.0.0/16  10.0.0.1
10.0.0.1  172.17.0.1
10.0.0.1  172.17.0.1
© 2014 Cisco and/or its affiliates. All rights reserved.
192.168.2.1/24
10.0.0.1  172.17.0.1
10.0.0.1
 172.17.0.1
192.168.2.1  ???
BRKRST-2041
 172.16.1.1
 172.16.2.1
10.0.0.11
10.0.0.12
Cisco Public
29
Dynamic Multipoint VPN (DMVPN)
Operational Example (cont.)
Data packet
NHRP Redirect
NHRP Resolution
NHRP mapping
192.168.0.1/24
192.168.0.0/24  Conn.
192.168.1.0/24  10.0.0.11
192.168.2.0/24  10.0.0.12
Physical: 172.17.0.1
Tunnel0:
10.0.0.1
CEF FIB Table
10.0.0.11  172.16.1.1
10.0.0.12  172.16.2.1
CEF Adjacency
Physical: 172.16.2.1
(dynamic)
Tunnel0: 10.0.0.12
Physical: 172.16.1.1
(dynamic)
Tunnel0: 10.0.0.11
192.168.1.1/24
Spoke B
Spoke A
192.168.2.0/24  Conn.
192.168.0.0/16  10.0.0.1
192.168.1.0/24  Conn.
192.168.0.0/16  10.0.0.1
10.0.0.1  172.17.0.1
10.0.0.11  172.16.1.1
10.0.0.1  172.17.0.1
© 2014 Cisco and/or its affiliates. All rights reserved.
192.168.2.1/24
10.0.0.1  172.17.0.1
10.0.0.11  172.16.1.1
10.0.0.1
 172.17.0.1
192.168.2.1  ???
BRKRST-2041
 172.16.1.1
 172.16.2.1
10.0.0.11
10.0.0.12
Cisco Public
30
DMVPN Network Designs
Spoke-to-hub tunnels
Spoke-to-spoke tunnels
2547oDMVPN tunnels
Spoke-to-spoke
VRF-lite
Server Load Balancing
Hierarchical
2547oDMVPN
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
31
Increase in Scale
BRKRST-2041
Hub and spoke
Any-to-Any Encryption
Before and After GETVPN
Public/Private WAN
Private WAN
Before: IPSec P2P Tunnels
After: Tunnel-Less VPN
WAN
Multicast
 Scalability—an issue (N^2 problem)
 Overlay routing
 Any-to-any instant connectivity can’t


BRKRST-2041
be done to scale
Limited QoS
Inefficient Multicast replication
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
 Scalable architecture for any-to-any




32
connectivity and encryption
No overlays—native routing
Any-to-any instant connectivity
Enhanced QoS
Efficient Multicast replication
Group Security Functions
Key Server
Key Server
 Validate Group Members
 Manage Security Policy
 Create Group Keys
 Distribute Policy/Keys
Routing Member
 Forwarding
 Replication
 Routing
Group
Member
Routing
Members
Group
Member
Group
Member
Group Member
 Encryption Devices
 Route Between Secure/
Unsecure Regions
 Multicast Participation
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Group
Member
Cisco Public
33
Group Security Elements
Key Servers
Group Policy
KS Cooperative
Protocol
Key Encryption Key
(KEK)
Traffic Encryption
Key (TEK)
Group
Member
Routing
Members
Group
Member
Group
Member
RFC3547:
Group Domain of
Interpretation
(GDOI)
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Group
Member
Cisco Public
34
GETVPN - Group Key Technology
Operation Example
GM3
GM4
GM2
 Step 1: Group Members (GM)
“register” via GDOI (IKE) with the
Key Server (KS)
GM5
GM1
GM6
GM9
– KS authenticates and authorizes the GM
– KS returns a set of IPsec SAs
for the GM to use
KS
GM8
GM3
GM7
GM4
GM2
 Step 2: Data Plane Encryption
GM5
GM1
– GM exchange encrypted traffic using the
group keys
– The traffic uses IPSec Tunnel Mode with
“address preservation”
GM6
GM9
KS
GM8
GM3
 Step 3: Periodic Rekey of Keys
© 2014 Cisco and/or its affiliates. All rights reserved.
GM4
GM2
– KS pushes out replacement IPsec
keys before current IPsec keys expire;
This is called a “rekey”
BRKRST-2041
GM7
Cisco Public
GM5
GM1
GM6
GM9
35
KS
GM8
GM7
GETVPN Virtualization Deployment Model
GETVPN Segmented WAN
CE
PE
PE
CE
MPLS VPN
LISP with GETVPN
CE
PE
PE
GET Encrypted LISP
LISP over GETVPN
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
36
CE
MACsec Layer 2 Encryption for WAN
 Ethernet is not only in the campus and data center any longer
ASR 1001-X XE3.14
 Ethernet is growing rapidly as a WAN & Metro “transport” service
 WAN/Metro SP offerings are replacing existing T1, ATM/FR, and SONET OC-x
options
 Ethernet services apply to many areas of the WAN/MAN:
– WAN links for core, edge, remote branch
– PE-CE links (leveraging L3 VPN services)
– Metro-E service hand-offs (P2P, P2MP)
 Cisco’s goal is to integrate MACsec as part of new Ethernet interface/LC
development moving forward on routers leveraged in WAN, MAN, Branch
BRKRST-2041
Market Transition – Ethernet WAN Transport
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
MACSec - Line Rate Encryption L2 Solution
What is MACSec?
IEEE 802.1AE standard for strong cryptographic protection at Layer 2
DMAC
SMAC
802.1Q
802.1AE Header
ß
Authenticated
Encrypted
CMD
ETYPE
PAYLOAD
ICV
CRC
802.1Q tag in clear
Simple
• Easy to configure. Simple configuration on interface level only. No GRE Tunnel establishment.
• Reduced interoperability issues with other L3 Features
Secure
• Leverage NSA Approved Suite B algorithms with MKA. DP, CP (ECC, SHA-2), CBC
Line Rate Encryption
• Leverages “line rate” Ethernet performance of the port (PHY). Speeds 1/10G, 40G, 100G
• Ethernet WAN deployments driving increasing need for higher crypto bandwidths.
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
MACsec Routing Peer Model
Point to Point E-LINE Service
Physical View
Logical View
IPv4/v6
IPv4/v6
CE2
CE2
CE1
Carrier Ethernet
Service
E-LINE (P2P)
Routers peer per
VLAN subinterface per PW
P2P Ethernet
Pseudo-wire
Service
CE4
CE3
Ethernet Sub-interface with
802.1q support
CE4
IPv4/v6
CE3
Ethernet Sub-interface with
802.1q support
 Challenge: Requires a PHYSICAL interface per terminated Ethernet link
 Solution: Leverage logical nature of 802.1Q tag support (full/partial-mesh)
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
IPv4/v6
Agenda
 WAN Technologies & Solutions
– WAN Transport Technologies
– WAN Overlay Technologies
– WAN Optimization
– Wide Area Network Quality of Service
 WAN Architecture Design Considerations
– WAN Design and Best Practices
– Secure WAN Communication with GETVPN
– Intelligent WAN Deployment
 Summary
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
40
The WAN Is the Barrier to Branch
Application Performance
 Applications are
designed to work
well on LAN’s
Round Trip Time ~ 0ms
– High bandwidth
– Low latency
– Reliability
 WANs have
opposite
characteristics
Client
Client
LAN
Switch
WAN Packet Loss and Latency =
Slow Application Performance =
Keep and manage servers in branch offices ($$$)
© 2014 Cisco and/or its affiliates. All rights reserved.
Server
Round Trip Time ~ Many milliseconds
– Low bandwidth
– High latency
– Packet loss
BRKRST-2041
LAN Switch
Cisco Public
41
WAN
LAN Switch
Server
TCP Behavior
Return to maximum
throughput could take a
very long time!
Window
Size
Packet loss
Slow start
Packet loss
Packet loss
Congestion avoidance
Time (RTT)
RFC1323 - TCP Extensions for High Performance
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
Packet loss
42
TCP
WAAS—TCP Performance Improvement
 Transport Flow Optimization (TFO) overcomes TCP and WAN bottlenecks
 Shields nodes connections from WAN conditions
– Clients experience fast acknowledgement
– Minimize perceived packet loss
– Eliminate need to use inefficient congestion handling
WAN
LAN TCP
Behavior
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Window Scaling
Large Initial Windows
Congestion Mgmt
Improved Retransmit
Cisco Public
43
LAN TCP
Behavior
WAAS Advanced Compression
DRE and LZ Manage Bandwidth Utilization
Data Redundancy Elimination
(DRE)
Persistent LZ Compression
•Application-agnostic compression
•Up to 100:1 compression
•WAAS 4.4: Context Aware DRE
Benefits
•Session-based
compression
• Application-agnostic
compression
•Up
compression
• Uptoto10:1
100:1
compression
•Works
DREDRE
cache
• WAASeven
4.4: during
Contextcold
Aware
WAN
LZ
DRE
DRE
Synchronized
Compression
History
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
LZ
Cisco Public
44
Comparing TCP and Transport
Flow Optimization
Cisco TFO Provides Significant Throughput
Improvements over Standard TCP Implementations
Window
Size
TFO
TCP
Slow start
Congestion avoidance
Time (RTT)
TFO is using RFC2018, RFC1323, RFC3390 and BIC-TCP
http://netsrv.csc.ncsu.edu/export/bitcp.pdf
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
45
Cisco WAAS: WAN Optimization Deployment
Virtual Private Cloud
WAAS
Express
Branch Office
vWAAS
WAE
Server
VMs
Nexus 1000v
vPATH
VMware ESXi Server
Branch Office
WAAS
Service
Module/ UCSe
WAN
Nexus 1000v VSM
UCS /x86 Server
FC SAN
Branch Office
WAAS
Appliance
Regional Office
WAAS
Appliance
Internet
Data Center or
Private Cloud
WAAS
Appliances
AppNav +
WAAS
VMware ESXi
Regional Office
BRKRST-2041
WAAS-XE
on 4451
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
vWAAS
Appliances
Server VMs
Agenda
 WAN Technologies & Solutions
– WAN Transport Technologies
– WAN Overlay Technologies
– WAN Optimization
– Wide Area Network Quality of Service
 WAN Architecture Design Considerations
– WAN Design and Best Practices
– Secure WAN Communication with GETVPN
– Intelligent WAN Deployment
 Summary
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
47
Quality of Service Operations
How Does It Work and Essential Elements
Classification and
Marking
Queuing and
Dropping
Post-Queuing
Operations
 Classification and Marking:
– The first element to a QoS policy is to classify/identify the traffic that is to be treated differently.
Following classification, marking tools can set an attribute of a frame or packet to a specific value.
 Policing:
– Determine whether packets are conforming to administratively-defined traffic rates and take action
accordingly. Such action could include marking, remarking or dropping a packet.
 Scheduling (including Queuing and Dropping):
BRKRST-2041
– Scheduling tools determine how a frame/packet exits a device. Queuing algorithms are activated only
when a device is experiencing congestion and are deactivated when the congestion clears.
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
48
Enabling QoS in the WAN
Traffic Profiles and SLA Requirements
Voice





Smooth
Benign
Drop sensitive
Delay sensitive
UDP priority
Bandwidth per Call
Depends on Codec,
Sampling-Rate,
and Layer 2 Media
 Latency ≤ 150 ms
 Jitter ≤ 30 ms
 Loss ≤ 1%
 Bandwidth (30-128Kbps)
One-Way Requirements
BRKRST-2041
Telepresence
SD Video Conf










Bursty
Greedy
Drop sensitive
Delay sensitive
UDP priority
HD/VC has Tighter
Requirements than
VoIP in terms of jitter,
and BW varies based
on the resolutions
 Latency ≤ 150 ms
 Jitter ≤ 30 ms
 Loss ≤ 0.05%
 Bandwidth (1Mbps)
One-Way Requirements
 Latency ≤ 200 ms
 Jitter ≤ 20 ms
 Loss ≤ 0.10%
 Bandwidth (5.5-16Mbps)
One-Way Requirements
Cisco Public
49





Bursty
Drop sensitive
Delay sensitive
Jitter sensitive
UDP priority
SD/VC has the Same
Requirements as
VoIP, but Has
Radically Different
Traffic Patterns
(BW Varies Greatly)
© 2014 Cisco and/or its affiliates. All rights reserved.
Data
Smooth/bursty
Benign/greedy
Drop insensitive
Delay insensitive
TCP retransmits
Traffic patterns for
Data Vary Among
Applications





Data Classes:
Mission-Critical Apps
Transactional/Interactive Apps
Bulk Data Apps
Best Effort Apps (Default)
Scheduling Tools
policy-map CBWFQ
class NETWORK-CONTROL
bandwidth percent 5
class CALL-SIGNALING
bandwidth percent 5
class OAM
bandwidth percent 5
class MM-CONFERENCING
bandwidth percent 10
fair-queue
…
LLQ/CBWFQ Subsystems
IOS Interface Buffers
Network Control CBWFQ
Call Signaling CBWFQ
FQ
Packets
In
Multimedia Conferencing CBWFQ
FQ
Multimedia Streaming CBWFQ
Tx-Ring
FQ
Transactional Data CBWFQ
FQ
Bulk Data CBWFQ
FQ
FQ
Best Effort / Default CBWFQ
Pre-Sorters
Scavenger CBWFQ
BRKRST-2041
CBWFQ
Scheduler
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
50
Packets
Out
Scheduling Tools
LLQ/CBWFQ Subsystems
IOS Interface Buffers
1 Mbps
VoIP
Policer
5 Mbps
LLQ
RT-Interactive
Policer
policy-map MULTI-LLQ
class VOIP
priority 1000
class REALTIME-INTERACTIVE
priority 5000
…
Packets
Out
Packets
In
CBWFQ
Scheduler
Tx-Ring
CBWFQ
http://www.cisco.com/en/US/docs/solutions/Enterprise/WAN_and_MAN/QoS_SRND_40/QoSWAN_40.html#wp129469
51
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
BRKRST-2041
Traffic Shaping
Line
Rate
Without Traffic Shaping
With Traffic Shaping
Shaped
Rate
Traffic Shaping Limits the Transmit Rate to a Value Lower Than Line Rate
 Policers typically drop traffic
 Shapers typically delay excess traffic, smoothing bursts
and preventing unnecessary drops
 Very common with Ethernet WAN, as well as NonBroadcast Multiple-Access (NBMA) network topologies
such as Frame-Relay and ATM
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
52
Hierarchical QoS For Subrate Service
H-QoS Policy on WAN Interface, Shaper = CIR
Two Levels MQC
Policy-map PARENT
class class-default
shape average 150000000
service-policy output CHILD
Gig 0/1
Service Level
Policy-map CHILD
class Voice
police cir percent 10
priority level 1
class Video
police cir percent 20
priority level 2
class Control
bandwidth remaining ration 1
class class-default
bandwidth remaining ratio 9
Best Effort
150 Mbps
Video
Control
Voice
Interface gigabitethernet 0/1
service-policy output PARENT
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
53
MPLS VPN QoS Considerations
MPLS VPN Port QoS Roles
Campus VPN
Block
Branch 1
E
F
F
E
MPLS VPN
E
F
F
E
Branch 2
CE Routers
PE Routers
CE Routers
Enterprise Subscriber (Unmanaged CE Routers)
E Outbound Policies:
Inbound Policies:
HQoS Shaper (if required)
+ LLQ for VoIP (EF)
+ LLQ or CBWFQ for RT-Interactive (CS4)
+ Remark RTI (if necessary)
+ CBWFQ for Signaling (CS3)
+ Remark Signaling (if necessary)
≤ 33%
of BW
Service Provider:
Outbound Policies:
BRKRST-2041
+ Restore RT-Interactive to CS4 (if necessary)
+ Restore Signaling to CS3 (if necessary)
Inbound Policies:
F
+ LLQ for Real-Time
CBWFQ
for Critical
© 2014 Cisco+and/or
its affiliates.
All rights Data
reserved.
Trust DSCP
Cisco Public
Trust DSCP
54Police on a per-Class Basis
GRE/IPSec QoS Consideration
ToS Byte Preservation
ToS
ToS byte is copied to
the new IP Header
IP HDR
IP Payload
GRE
HDR
IP HDR
ToS
ToS
GRE Tunnel
IP HDR
IP Payload
IP HDR
BRKRST-2041
ESP HDR
© 2014 Cisco and/or its affiliates. All rights reserved.
ToS
ToS
IPSec Tunnel mode
IP HDR
Cisco Public
IP Payload
55
ESP
Trailer
ESP
Auth
GRE and IPsec Network QoS Design
Direction of Packet Flow
DSCP CS5
Packet initially marked to
DSCP AF41according to
RFC-4594
DSCP CS5
DSCP AF41
DSCP CS5
DSCP CS5
By default, ToS values are
copied to IPsec header
Topmost ToS value is
rewritten on egress to match
service provider classes
 Remark DSCP on egress to align with each SP’s
SLA class of service requirements
 H-QOS with shaping to offered rate on egress
 Hub per tunnel QOS to minimize spoke
oversubscription
Re-marks the DSCP value on the
encrypted and encapsulated header on
the egress interface
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
56
DSCP CS5
Packet decapsulated to
reveal the original ToS byte
policy-map WAN-SP-CLASS-OUTPUT
class VOICE
priority percent 10
class VIDEO-INTERACTIVE
priority percent 23
set dscp af41
class NETWORK-MGMT
bandwidth percent 5
service-policy MARK-BGP
class class-default
bandwidth percent 25
random-detect
!
policy-map Int-Gig-Agg-HE
class class-default
shape average 1000000000
service-policy WAN-Out
56
Per Site Traffic Shaping to Avoid Overruns
DMVPN Per-Tunnel QoS
 User NHRP group to dynamically provision HQoS
policy on a DMVPN hub per-spoke basis
Campus
Data Center/HQ
Spoke: Configure NHRP group name
Hub: NHRP group name mapped to QoS template policy
Multiple spokes with same NHRP group mapped to
individual instances of same QoS template policy
 GRE ,IPsec &L2 header are included in
calculations for shaping and bandwidth.
CE
150 Mbps
50 Mbps
 Queuing and shaping is performed at the outbound
physical interface
20 Mbps
10 Mbps
 Can be used with DMVPN with or without IPSec.
 7200/ISR G1/G2 – 12.4(22)T or later
 ASR1000 – IOS XE RLS 3.6
IOS Configuration Reference for Per-Tunnel QoS for DMVPN:
Remote
Branches
57
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
http://www.cisco.com/en/US/docs/ios/sec_secure_connectivity/configuration/guide/sec_per_tunnel_qos.html
10 Mbps
Per-tunnel QoS
For Your
Reference
Configurations
class-map match-all typeA_voice
match access-group 100
class-map match-all typeB_voice
match access-group 100
class-map match-all typeA_Routing
match ip precedence 6
class-map match-all typeB_Routing
match ip precedence 6
Hub
policy-map typeA
class typeA_voice
priority 1000
class typeA_Routing
bandwidth percent 20
policy-map typeB
class typeB_voice
priority percent 20
class typeB_Routing
bandwidth percent 10
policy-map typeA_parent
class class-default
shape average 3000000
service-policy typeA
policy-map typeB_parent
class class-default
shape average 2000000
service-policy typeB
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
interface Tunnel0
ip address 10.0.0.1 255.255.255.0
…
ip nhrp map group typeA service-policy output typeA_parent
ip nhrp map group typeB service-policy output typeB_parent
…
ip nhrp redirect
no ip split-horizon eigrp 100
ip summary-address eigrp 100 192.168.0.0 255.255.192.0 5
…
interface Tunnel0
ip address 10.0.0.11 255.255.255.0
…
ip nhrp group typeA
ip nhrp map multicast 172.17.0.1
ip nhrp map 10.0.0.1 172.17.0.1
ip nhrp nhs 10.0.0.1
…
interface Tunnel0
ip address 10.0.0.12 255.255.255.0
…
ip nhrp group typeB
ip nhrp map multicast 172.17.0.1
ip nhrp map 10.0.0.1 172.17.0.1
ip nhrp nhs 10.0.0.1
…
interface Tunnel0
ip address 10.0.0.13 255.255.255.0
…
ip nhrp group typeA
ip nhrp map multicast 172.17.0.1
ip nhrp map 10.0.0.1 172.17.0.1
ip nhrp nhs 10.0.0.1
…
Cisco Public
58
Hub (cont)
Spoke1
Spoke2
Spoke3
Adaptive QoS
How To Compute Available BW & Adjust Shapers
Shaper towards this spoke
Egress shaper
=5
3 Mbps (offered)
(available)
=6
4 Mbps (offered)
(available)
DMVPN
DMVPN
Benefits -

Accurate view of available
BW in non SLA environments

Adapting business critical
applications to what is
available on link

No more indiscriminate drops
- tighter control of business
policies for IWAN
Hub Site
Spoke Site
5 Mbps
Internet
6 Mbps
Available BW check:
Tunnel Rx Loss,
Rx/Tx compute
Available downstream BW
= 4 Mbps
Compute
Available
BW function of
the router
Available upstream BW
= 3 Mbps
Algorithm to compute available upstream
and downstream BW
ASR1000, ISR4000 15.5(1)S/XE3.14
ISR G2 15.5(1)T
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
Adaptive QoS for DMVPN
For Your
Reference
Configuration (Hub)
interface Tunnel1
policy-map qos
class class-default
ip address 192.168.1.1 255.255.255.0
no ip redirects
ip nhrp authentication GetDm0
ip nhrp group 1
ip nhrp map multicast dynamic
shape adaptive upper-bound 6000000 lower-bound 2000000
service-policy child
policy-map child
class prec5
priority percent 20
class class-default
bandwidth percent 80
ip nhrp map group 1 service-policy output qos
ip nhrp network-id 1
ip tcp adjust-mss 1360
load-interval 30
cdp enable
tunnel source Loopback1
tunnel mode gre multipoint
tunnel key 10001
tunnel protection ipsec profile P1
Adaptive Shaper on Parent Class Not allowed to configuring in Child Class
Policy on DMVPN Tunnel Assigned per NHRP spoke - consistent with Per Tunnel QoS
Hub->Spoke, Spoke-Hub
- Adaptive shapers supported on hub->spoke & spoke->hub
- spoke->spoke in roadmap
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
shape adaptive upper-bound <<bps> | percent <value>>
[lower-bound <<bps> | percent <value>>]
upper-bound : Mandatory (max ceiling for shaper)
lower-bound : Optional (0 if not specified)
Cisco Public
Adaptive QoS for DMVPN
For Your
Reference
Configuration (Spoke)
policy-map qos
class class-default
interface Tunnel1
shape adaptive upper-bound 6000000 lower-bound 2000000
ip address 192.168.1.2 255.255.255.0
no ip redirects
ip nhrp authentication GetDm0
ip nhrp group 1
ip nhrp map 192.168.1.1 11.1.1.1
ip nhrp map multicast 11.1.1.1
service-policy child
policy-map child
class class-default
bandwidth percent 80
service-policy grand_child
ip nhrp map group 1 service-policy output qos
ip nhrp network-id 1
ip nhrp nhs 192.168.1.1
ip nhrp server-only
ip nhrp hold-time 360
ip tcp adjust-mss 1360
load-interval 30
cdp enable
tunnel source Loopback1
tunnel mode gre multipoint
tunnel key 10001
tunnel protection ipsec profile P1
Policy on DMVPN Tunnel -
policy-map grand_child
class class-default
Adaptive Shaper on Parent Class Not allowed to configuring in Child Class
shape adaptive upper-bound <<bps> | percent <value>>
[lower-bound <<bps> | percent <value>>]
Assigned per NHRP spoke - consistent with Per Tunnel QoS
Hub->Spoke, Spoke-Hub
- Adaptive shapers supported on hub->spoke & spoke->hub
- spoke->spoke in roadmap
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
upper-bound : Mandatory (max ceiling for shaper)
lower-bound : Optional (0 if not specified)
Cisco Public
Agenda
 WAN Technologies & Solutions
– WAN Transport Technologies
– WAN Overlay Technologies
– WAN Optimization
– Wide Area Network Quality of Service
 WAN Architecture Design Considerations
– WAN Design and Best Practices
– Secure WAN Communication with GETVPN
– Intelligent WAN Deployment
 Summary
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
62
Cisco Validate Design
MPLS WAN Technology Design Guide
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
63
WAN Aggregation Reference Design
Campus/
Data Center
Data
Center/
Campus
WAAS Service
WAN
Key
Servers
Services/
Distribution
VPN Termination
WAN Edge
MPLS A
MPLS B
Internet
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
64
Remote Branch
Transport & Redundancy Options
Redundant-Links
Non-Redundant
MPLS
MPLS
MPLS
MPLS
Internet
Redundant-Links
& Routers
MPLS
MPLS
MPLS WAN
MPLS +
Internet WAN
Internet
Internet
Internet WAN
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
65
Internet
MPLS
Internet
Routing Topology at WAN Aggregation
Campus/
Data Center
Core Layer
WAN Distribution
Layer
EIGRP AS 100
Summaries+
Default
DMVPN Hub
Routers
EIGRP AS = 100
BGP AS = 65511
iBGP
EIGRP AS = 100
MPLS CE
Routers
BGP AS = 65511
Internet Edge
eBGP
MPLS A
BRKRST-2041
EIGRP AS = 100
MPLS B
© 2014 Cisco and/or its affiliates. All rights reserved.
EIGRP AS = 200
Layer 2 WAN
CE Router
Layer 2
WAN
Cisco Public
DMVPN 1 DMVPN 2
66
Internet
WAN Edge
Connection Methods Compared
Recommended
Core/Distribution
Core/Distribution
Core/Distribution
Si
WAN
Edge
Router
WAN

WAN
WAN
All:
 Single Logical
Control Plane
‒ No static routes
 Port-Channel for H/A
‒ No FHRPs
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
67
Optimize Convergence and Redundancy
Multichassis EtherChannel
VSS/3850
Stacks
Si
Layer 3
Si
P-to-P Link
Channel
Member
Removed
IGP recalc
 Link redundancy achieved through
redundant L3 paths
 Provide Link Redundancy and reduce
peering complexity
 Flow based load-balancing through CEF
forwarding across
 Tune L3/L4 load-balancing
hash to achieve maximum utilization
 Routing protocol reconvergence when uplink  No L3 reconvergence required when
member link failed
failed
 Convergence time may depends on routing  No individual flow can go faster than
the speed of an individual member of
protocol used and the size of routing entries
the link
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
68
Link Recovery Comparison
ECMP vs. Multichassis EtherChannel
 ECMP convergence is dependent on the number of
routes
Si
Layer 3
P-to-P Link
 MEC convergence is consistent, independent of the
number of routes
2.5
ECMP
MEC Max
sec of lost voice
2
VSS/3850
Stacks
1.5
1
0.5
0
1000
3000
6000
9000
Number of Routes - Sup720C
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
69
12000
Si
Redundancy vs. Convergence Time
More Is Not Always Better
 In principle, redundancy is easy
 Any system with more parallel paths
through the system will fail less
often
 Increasing parallel paths increases
routing complexity, therefore
increasing convergence times
2.5
Seconds
 The problem is a network isn’t really
a single system but a group of
interacting systems
0
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
70
Routes
10000
Best Practice —
Summarize at Service Distribution
 It is important to force summarization
at the distribution towards WAN Edge
and towards campus & data center
Campus/
Data Center
Summary
10.5.0.0/16
 Summarization provides topology
change isolation.
 Summarization reduce routing table
size.
Summaries +
Default
10.4.0.0/16
0.0.0.0/0.0.0.0
interface Port-channel1
description Interface to MPLS-A-CE
no switchport
ip address 10.4.128.1 255.255.255.252
ip pim sparse-mode
ip summary-address eigrp 100 10.5.0.0 255.255.0.0
MPLS A
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
71
MPLS B
Best Practice –
Preventing Routing Loops with Route Tag and Filter
 Mutual route redistribution between protocols can
cause routing loops without preventative measures
 Use route-map to set tags and then redistribute
based on the tags
 Routes are implicitly tagged when distributed from
eBGP to EIGRP/OSPF with carrier AS
IGP Domain
(EIGRP/OSPF)
Campus
 Use route-map to block re-learning of WAN routes
via the distribution layer (already known via iBGP)
router eigrp 100
distribute-list route-map BLOCK-TAGGED-ROUTES in
default-metric [BW] 100 255 1 1500
redistribute bgp 65500
route-map BLOCK-TAGGED-ROUTES deny 10
match tag 65401 65402
BGP Domain
route-map BLOCK-TAGGED-ROUTES permit 20
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
MPLS WAN
72
Dual Carriers with BGP as CE-PE Protocol
Use iBGP for Path Selection

Run iBGP between the CE routers to
exchange prefixes associated with each
carrier

CE routers will use only BGP path selection
information to select both the primary and
secondary preferences for any destinations
announced by the IGP and BGP

BRKRST-2041
Campus
Use IGP (OSPF/EIGRP) for prefix readvertisement will result in equal-cost paths
at remote-site
bn-br200-3945-1# sh ip bgp 10.5.128.0/21
BGP routing table entry for 10.5.128.0/21, version 71
Paths: (2 available, best #2, table default, RIB-failure(17))
Not advertised to any peer
65401 65402, (aggregated by 65511 10.5.128.254)
10.4.142.26 from 10.4.142.26 (192.168.100.3)
Origin IGP, localpref 100, valid, external, atomicaggregate
65402, (aggregated by 65511 10.5.128.254)
10.4.143.26 (metric 51456) from 10.5.0.10 (10.5.0.253)
Origin IGP, metric 0, localpref 100, valid, internal,
atomic-aggregate, best
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
73
10.5.128.0/21
iBGP
MPLS B
MPLS A
A
B
iBGP
10.5.128.0/21
Best Practice - Implement AS-Path Filter
Prevent Branch Site Becoming Transit Network
Campus
 Dual carrier sites can unintentionally become
transit network during network failure event and
causing network congestion due to transit traffic
 Design the network so that transit path between
two carriers only occurs at sites with enough
bandwidth
 Implement AS-Path filter to allow only locally
originated routes to be advertised on the
outbound updates for branches that should not
be transit
router bgp 65511
neighbor 10.4.142.26 route-map NO-TRANSIT-AS out
!
ip as-path access-list 10 permit ^$
!
route-map NO-TRANSIT-AS permit 10
match as-path 10
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
74
MPLS B
MPLS A
A
B
iBGP
Golden Rules
For Your
Reference
Route Preference for EIGRP & OSPF
EIGRP
OSPF
– Internal EIGRP – Admin Dist. 90
– External EIGRP – Admin Dist. 170
– Admin Dist. 110
 Route Preference
 Metric Calculation
metric = bandwidth + delay
1.
2.
3.
4.
– Bandwidth (in kb/s)
– Delay (in microseconds)
Intra-Area
Inter-Area
External E1 (Internal + External Cost)
External E2 (External Cost)
 Cost Calculation
Cost= Reference BW / Interface BW
Default Reference BW = 100Mbps
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
75
Best Practice – Use Delay Parameter to Influence
EIGRP Path Selection
 EIGRP uses the minimum bandwidth along the
path and the total delay to compute routing
metrics
 Does anything else use these values?
– EIGRP also uses interface Bandwidth parameter to avoid
congestion by pacing routing updates (default is 50% of bandwidth)
– Interface Bandwidth parameter is also used for QoS policy
calculation
– Performance Routing (PfR) leverages Bandwidth parameter for
traffic load sharing
 Delay parameter should always be used to
influence EIGRP routing decision
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
76
MPLS + Internet WAN
Prefer the MPLS Path over Internet
Campus
EIGRP
AS100
 Running same EIGRP AS for both campus and
DMVPN network would result in Internet path preferred
over MPLS path
10.4.128.2
eBGP
MPLS A
 eBGP routes are redistributed into EIGRP 100 as
external routes with default Admin Distance 170
Internet
EIGRP
AS100
10.5.48.0/21
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
77
MPLS + Internet WAN
Use Autonomous System for IGP Path Differentiation
Campus
D EX
EIGRP
AS100
10.4.128.2
10.5.48.0/21 [170/28416] via 10.4.128.2
 eBGP routes are redistributed into EIGRP 100 as
external routes with default Admin Distance 170
 Running same EIGRP AS for both campus and
DMVPN network would result in Internet path preferred
over MPLS path
eBGP
 Multiple EIGRP AS processes can be used to provide
control of the routing
MPLS A
 EIGRP 100 is used in campus location
EIGRP 200 over DMVPN tunnels
 Routes from EIGRP 200 redistributed into EIGRP 100 appear as
external route (distance = 170)
Internet
EIGRP
AS200
 Routes from both WAN sources are equal-cost paths.
To prefer MPLS path over DMVPN use eigrp delay to
modify path preference
MPLS CE router#
10.5.48.0/21
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
router eigrp 100
default-metric 1000000 10 255 1 1500
Cisco Public
78
MPLS VPN BGP Path with IGP Backdoor Path
Campus
 eBGP as the PE-CE Routing Protocol
 MPLS VPN as preferred path learned via
eBGP
R2
MPLS A
Internet
10.4.160.0/24
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
79
IGP Backup Link
 Default configuration the failover to backup
path works as expected
R1
eBGP
 Secondary path via backdoor IGP link
(EIGRP or OSPF) over tunneled connection
(DMVPN over Internet)
EIGRP
AS100
MPLS VPN BGP Path with IGP Backdoor Path
Campus
 After link restore, MPLS CE router receives
BGP advertisement for remote-site route.
 Does BGP route get (re)installed in the route
table?
R1
R2
MPLS A
Internet
R1# show ip route
B
10.4.144.0/24 [20/0] via 10.4.142.2, 01:30:06
B
10.4.145.0/24 [20/0] via 10.4.142.2, 01:30:06
D EX 10.4.160.0/24 [170/3584] via 10.4.128.9, 00:30:06
B
BRKRST-2041
10.4.160.0/24 [20/0]....
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
80
10.4.160.0/24
IGP Backup Link
eBGP
D EX 10.4.160.0/24 [170/3584]....
EIGRP
AS100
BGP Route Selection Algorithm
BGP Prefers Path with:
1. Highest Weight
2. Highest Local Preference
3. Locally originated (via network or aggregate BGP)
4. Shortest AS_PATH
5. Lowest Origin type
IGP>EGP>INCOMPLETE (redistributed into BGP)
6. Lowest Multi-Exit Discriminator (MED)
7. Prefer Externals (eBGP over iBGP paths)
8. Lowest IGP metric to BGP next hop (exit point)
9. Lowest Router ID for exit point
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
81
For Your
Reference
BGP Prefers Path with Highest Weight
 Routes redistributed into BGP are considered locally originated and get a default
weight of 32768
 The eBGP learned prefix has default weight of 0
 Path with highest weight is selected
ASR1004-1#show ip bgp 10.4.160.0 255.255.255.0
BGP routing table entry for 10.4.160.0/24, version 22
Paths: (3 available, best #3, table default)
Advertised to update-groups:
4
5
65401 65401
10.4.142.2 from 10.4.142.2 (192.168.100.3)
Origin IGP, localpref 200, valid, external
Local
10.4.128.1 from 0.0.0.0 (10.4.142.1)
Origin incomplete, metric 26883072, localpref 100, weight 32768, valid, sourced, best
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
82
Prefer the eBGP Path over IGP
Set the eBGP weight > 32768
 To resolve this issue set the weights on route learned via eBGP peer higher
than 32768
neighbor 10.4.142.2 weight 35000
ASR1004-1#show ip bgp 10.4.160.0 255.255.255.0
BGP routing table entry for 10.4.160.0/24, version 22
Paths: (1 available, best #1, table default)
Not advertised to any peer
65401 65401
10.4.142.2 from 10.4.142.2 (192.168.100.3)
Origin IGP, metric 0, localpref 100, weight 35000, valid, external, best
ASR1004-1#show ip route
....
B
10.4.160.0/24 [20/0] via 10.4.142.2, 05:00:06
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
83
Agenda
 WAN Technologies & Solutions
– WAN Transport Technologies
– WAN Overlay Technologies
– WAN Optimization
– Wide Area Network Quality of Service
 WAN Architecture Design Considerations
– WAN Design and Best Practices
– Secure WAN Communication with GETVPN
– Intelligent WAN Deployment
 Summary
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
84
Dual Carrier GETVPN Topology
COOP Key Server
Key Servers
GM
GM
MPLS A
MPLS B B
MPLS
MPLS A
GM
GM
BRKRST-2041
GM
© 2014 Cisco and/or its affiliates. All rights reserved.
GM
GM
Cisco Public
85
GM
Best Practice - High Availability with Cooperative Key Servers
 Two or more KSs known as COOP KSs manage a common set of keys and security policies for
GETVPN group members
 Group members can register to any one of the available KSs
 Cooperative KSs periodically exchange and synchronize group’s database, policy and keys
 Primary KS is responsible to generate and distribute group keys
Cooperative KS1
Cooperative KS2
Subnet 1
Subnet 2
GM 1
GM 2
IP Network
Subnet 3
Subnet 4
GM 4
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
GM 3
Cisco Public
86
Best Practice - Key Server Recommendations
For Your
Reference
 Maintain reliable KS communication:
–Insure multiple routing paths exist between all KS
–Use loopback interface for KS registration and Cooperative KS protocol Use
IKE keep-alive for KS-KS communication
 Use only globally applicable policies in KS proxy identifiers:
–Site specific policies should be applied at the GM
–Goal is to create symmetric policies on KS
–Exception policy development should be done on GM, not KS
 Use sufficiently long key lifetimes to minimize key transitions:
–Traffic Encryption Key (TEK) > 3600 sec
–Key Encryption Key (KEK) > 86400 sec
 Insure rekey interval extends longer than routing convergence time
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
87
Transition from Clear-text to GETVPN
SA Receive-Only Method
 Goal
–Incrementally deploy infrastructure
without encryption
–Immediate transition to encryption
controlled by KS
 Method
–Deploy KS with Receive-only SA’s
(don’t encrypt, allow decryption)
–Deploy GM throughout infrastructure
and monitor rekey processes
–Transition KS to Normal SA (encrypt,
decrypt)
permit ip 10.1.4.0 0.0.1.255 10.1.4.0 0.0.1.255
10.1.4.0/24
KS
GET
GM
10.1.5.0/24
Cisco Public
10.1.7.0/24
permit ip 10.1.4.0 0.0.3.255 10.1.4.0 0.0.3.255
10.1.4.0/24
KS
10.1.6.0/24
GM
GET
GM
GM
GM
10.1.5.0/24
© 2014 Cisco and/or its affiliates. All rights reserved.
GM
GM
 Assessment
–Pro: Simple transition to network-wide
encryption
–Con: Correct policies imperative
–Con: Deferred encryption until all CE
are capable of GM functions
BRKRST-2041
10.1.6.0/24
GM
88
10.1.7.0/24
For Your
Reference
Group Member
Secured Group Member Interface
interface Serial0/0
ip address 192.168.1.14 255.255.255.252
crypto map svn
access-group pack-filter out
<- WAN ENCRYPTION
<- ALLOW IPsec and Control
Packet filter (after encryption)
ip access-list extended pack-filter
permit esp any any
permit ip host 192.168.1.14 host 192.168.1.13
permit tcp host 192.168.1.14 eq ssh any
<- ALLOW IPsec
<- ALLOW ROUTE ADJACENCY
<- ALLOW SECURE SHELL
Crypto Map Association to Group Security
crypto map svn 10 gdoi<- GROUP CRYPTO MAP ENTRY
set group secure-wan
<- GROUP MEMBERSHIP
match address control_plane
<- LOCAL POLICY (EXCLUDE)
Group Member Policy Exceptions
ip access-list extended control_plane
<- CONTROL PLANE PROTOCOLS
deny ip host 192.168.1.14 host 192.168.1.13 <- PE-CE LINK (BGP, ICMP)
deny tcp host 192.168.1.14 eq ssh any
<- MANAGEMENT SECURE SHELL
Group Member Association
crypto gdoi group secure-wan
identity number 3333
server address ipv4 <ks1_address>
server address ipv4 <ks2_address>
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
<<<<Cisco Public
GROUP ENCRYPTION
MEMBER’S GROUP IDENTITY
KS ADDRESS TO REGISTER
ALTERNATE KS REGISTRATION
89
For Your
Reference
Key Server
crypto gdoi group secure-wan
identity number 3333
<- GROUP ID
server local
<- KEY SERVER
rekey retransmit 40 number 3
<- REKEY RETRANSMITS
rekey authentication mypubkey rsa my_rsa <- KS MSG AUTHENTICATION
rekey transport unicast
<- Unicast Rekey
saipsec 10
<- SECURITY ASSOCIATION
profile GETVPN-GDOI-PROFILE
<- CRYPTO ATTRIBUTES SELECTION
match address ipv4ipsec-policy
<- ENCRYPTION POLICY
no replay
<- NO ANTI-REPLAY
address ipv4 <ks_address>
<- KS ADDRESS
Crypto Attributes
crypto ipsec profile GETVPN-GDOI-PROFILE
set security-association lifetime seconds 7200
set transform-set AES256/SHA
<- AES256 for Encryption and SHA for Hash
Encryption IPsec Proxy ID’s (mandatory)
ip access-list extended ipv4ipsec-policy
deny udp any eq 848 any eq 848
permit ip 10.0.0.0 0.255.255.255 10.0.0.0 0.255.255.255
permit ip 10.0.0.0 0.255.255.255 232.0.0.0 0.255.255.255
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
90
<<<<-
ENCRYPTION POLICY
ALLOW GDOI
UNICAST
MULTICAST
Agenda
 WAN Technologies & Solutions
– WAN Transport Technologies
– WAN Overlay Technologies
– WAN Optimization
– Wide Area Network Quality of Service
 WAN Architecture Design Considerations
– WAN Design and Best Practices
– Secure WAN Communication with GETVPN
– Intelligent WAN Deployment
 Summary
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
91
Internet Becoming an Extension of Enterprise WAN
Commodity Transports Viable Now
Dramatic Bandwidth, Price Performance Benefits
Higher Network Availability
Improved Performance Over Internet
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
92
https://www.google.com/get/videoqualityreport/
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
93
Intelligent WAN Solution Components
AVC
Private
Cloud
MPLS
Virtual
Private
Cloud
3G/4G-LTE
Branch
Internet
WAAS
Public
Cloud
PfR
Control & Management with Automation
Transport
Independent
• Consistent operational model
Intelligent
Path Control
•
Dynamic Application best
path based on policy
•
Application visibility with
performance monitoring
•
Load balancing for full
utilization of bandwidth
•
•
Improved availability
Application acceleration
and bandwidth
optimization
• Simple provider migrations
• Scalable and modular design
• IPsec routing overlay design
BRKRST-2041
Application
Optimization
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
Secure
Connectivity
•
Certified strong encryption
•
Cloud Managed Security for
secure direct Internet access
•
Comprehensive threat
defense
Hybrid WAN Designs
Traditional and IWAN
TRADITIONAL HYBRID
IWAN HYBRID
Active/Standby
WAN Paths
Active/Active
WAN Paths
Primary With Backup
Data Center
Two IPsec Technologies
GETVPN/MPLS
DMVPN/Internet
Data Center
ASR 1000
ASR 1000
SP V
ISP A
Two WAN Routing
Domains
DMVPN
GETVPN
MPLS
Internet
ASR 1000
ASR 1000
ISP A
SP V
DMVPN
DMVPN
DMVPN
MPLS
Internet
One WAN
Routing Domain
MPLS: eBGP or Static
Internet: iBGP, EIGRP or OSPF
Route Redistribution
Route Filtering Loop Prevention
iBGP, EIGRP, or OSPF
Minimal route filtering
ISR-G2
BRKRST-2041
One IPsec Overlay
© 2014 Cisco and/or its affiliates. All rights reserved.
Branch
Cisco Public
ISR-G2
Branch
DMVPN Deployment over Internet
Multiple Default Routes for VPN Headend
 VPN Headend has a default
route to ASA firewall’s VPNDMZ interface to reach Internet
 Remote site policy requires
centralized Internet access
default
INSIDE
Internet Edge
Block
default
 Enable EIGRP between VPN
headend & Campus core to
propagate default to remote
default
VPN-DMZ
OUTSIDE
 Static default (admin dist=0)
remains active,
Internet
Internet
 VPN-DMZ is wrong firewall
interface for user traffic
Internet
 Adjust admin distance so
EIGRP route installed (to core)
default
 VPN tunnel drops
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
96
default
DMVPN Deployment over Internet




BRKRST-2041
The RED-VRF contains the
default route to VPN-DMZ
Interface needed for Tunnel
Establishment
default
EIGRP

Enable FVRF with DMVPN
to separate out the two
default routes
default
default
A 2nd default route exist on
the Global Routing Table
used by the user data traffic
to reach Internet
VPN-DMZ
OUTSIDE
default
Internet
To prevent split tunneling the
default route is advertised to
spokes via Tunnel
Internet
default
Spoke’s tunnel drops due to
2nd default route conflict with
the one learned from ISP
© 2014 Cisco and/or its affiliates. All rights reserved.
INSIDE
Internet Edge
Block
Cisco Public
97
default
Best Practice – VRF-aware DMVPN
Keeping the Default Routes in Separate VRFs
No Split Tunneling at Branch location
 Enable FVRF DMVPN on the
Spokes
EIGRP
 Allow the ISP learned Default
Route in the RED-VRF and
used for tunnel establishment
default
default
INSIDE
Internet
Edge Block
default
 Global VRF contains Default
Route learned via tunnel.
User data traffic follow Tunnel
to INSIDE interface on firewall
VPN-DMZ
OUTSIDE
 Allow for consistency for
implementing corporate
security policy for all users
default
Internet
Internet
default
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
98
default
DMVPN and FVRF
Configuration Example
Clear-text packets forward
using Global Routing Table
VRF-RED
Interface
mGRE
Interface
ip vrf RED
rd 65512:1
!
crypto keyring DMVPN-KEYRING vrf RED
pre-shared-key address 0.0.0.0 0.0.0.0 key cisco123
!
crypto isakmp policy 10
encr aes 256
authentication pre-share
group 2
!
crypto isakmp keepalive 30 5
!
crypto isakmp profile FVRF-ISAKMP-RED
keyring DMVPN-KEYRING
match identity address 0.0.0.0 RED
!
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
Internet
interface GigabitEthernet0/1
ip vrf forwarding RED
ip address dhcp
!
interface Tunnel10
ip address 10.4.132.201 255.255.254.0
….
tunnel mode gre multipoint
tunnel vrf RED
tunnel protection ipsec profile DMVPN-PROFILE
!
router eigrp 200
network 10.4.132.0 0.0.0.255
network 10.4.163.0 0.0.0.127
eigrp router-id 10.4.132.201
!
BRKRST-2041
Default
Interface
Global
Routing Table
IPsec
Default
GRE+IPsec
99
Increase Routing Scalability and Stability
EIGRP Stub
• Marking the spokes as stubs allows the STUBs to
signal hub A and B that they are not valid transit
paths
• A will not query stubs, reducing the total number
of queries in this example to one
• Marking the remotes as stubs also reduces the
complexity of this topology
• Router B now believes it only has one path to
10.1.1.0/24 (through A), rather than five
router#config t
router(config)#router eigrp 100
router(config-router)#eigrp stub connected
router(config-router)#
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
100
A
A
B
B
Dual Router Spoke Design
Routing Leaking thru STUBs
EIGRP Hub and Spoke Stub Route Leaking
• EIGRP offers additional control over routes advertised by Stubs
• Some deployments have a single remote site with two
routers and we want to mark the entire site
as a “stub site”
• Normally stubs C and D won’t advertise learned routes
to each other, to override this, add the “leak-map”
configuration
route-map LeakList permit 10
match ip address 1
match interface e0/0
route-map LeakList permit 20
match ip address 2
match interface e1/0
!
access-list 1 permit 10.1.1.0
access-list 2 permit 0.0.0.0
!
router eigrp IWAN
address-family ipv4 autonomous-system 100
eigrp stub leak-map LeakList
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
101
A
A
BB
0.0.0.0/0
0.0.0.0/0
No Advertisements
C
C
DD
10.1.1.0/24
Remote Site
Best Practices —
Avoid Fragmentation with IPSec VPN
GRE+IPsec
MTU 1500
MTU 1400
MTU 1500
Tunnel Setting (AES256+SHA)
Minimum MTU
Recommended MTU
GRE/IPSec (Tunnel Mode)
1414 bytes
1400 bytes
GRE/IPSec (Transport Mode)
1434 bytes
1400 bytes
• IP fragmentation will cause CPU and memory overhead and resulting in lowering
throughput performance
• When one fragment of a datagram is dropped, the entire original IP datagram will
have to be resent
• Use ‘mode transport’ on transform-set
– NHRP needs for NAT support and saves 20 bytes
• Avoid MTU issues with the following best practices
– ip mtu 1400
– ip tcp adjust-mss 1360
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
102
Best Practices — Enable Dead Peer Detection (DPD)
Improve DMVPN Network Convergence
 Dead Peer Detection (DPD) is a mechanism for
detecting unreachable IKE peers
 Each peer’s DPD state is independent of the others
 Without DPD spoke routers will continue to encrypt
traffic using old SPI which would be dropped at the
hub. May take up to 60 minutes for spokes to
reconverge
 Use ISAKMP keepalives on spokes
crypto isakmp keepalives <initial> <retry>
– ISAKMP invalid-SPI-recovery is not useful with DMVPN
– ISAKMP keepalive timeout should be greater than
routing protocol hellos
 Not recommended for Hub routers – may cause an
increase of CPU overhead with large number of peers
Informational RFC 3706
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
103
tun10
Internet
Best Practices — Enable PIM NBMA-Mode
Multicast over DMVPN

By default router uses OIL to correlate multicast
group join to interface

This causes problem when hub is connected to
multiple spokes over NBMA network

Any spoke that leaves a multicast group would case
all the spokes to be pruned off the multicast group

Enable PIM NBMA mode under tunnel interface on
hubs and spokes
Multicast
PIM
Prune
towards
RP
Internet
ip pim nbma-mode
‒
‒

Allows the router to track multicast joins based on IP
address instead of interface
Applies only to PIM sparse-mode
Router treats NBMA network as a collection of pointto-point circuits, allowing remote sites to be pruned
off traffic flows
PIM
Prune
IGMP
Leave
Receiver
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
105
Receiver
IWAN Transport Best Practices
 Private peering with Internet providers
– Use same Internet provider for hub and spoke sites
– Avoids Internet Exchange bottlenecks between providers
– Reduces round trip latency
IWAN HYBRID
 DMVPN
–
–
–
–
DMVPN Phase 2 for dynamic tunnels with PfR
Separate DMVPN network per provider for path diversity
Per tunnel QOS
NG Encryption – IKEv2 + AES-GCM-256 encryption
 Transport settings
– Use the same MTU size on all WAN paths
– Bandwidth settings should match offered rate
Data Center
ISP A
DMVPN
Purple
Internet
SP V
DMVPN
Green
MPLS
 Routing overlay
– iBGP or EIGRP for high scale (1000+ sites)
– Single routing process, simplified operations
– Front-side VRF to isolate external interfaces
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
106
Branch
Agenda
 WAN Technologies & Solutions
– WAN Transport Technologies
– WAN Overlay Technologies
– WAN Optimization
– Wide Area Network Quality of Service
 WAN Architecture Design Considerations
– WAN Design and Best Practices
– Secure WAN Communication with GETVPN
– Intelligent WAN Deployment
 Summary
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
107
Modern Hierarchical Global WAN Design
East Theater
Tier 1
West Theater
Tier 2
Global
IP/MPLS Core
In-Theater
IP/MPLS Core
West Region
East Region
Tier 3
Internet
Cloud
Public Voice/Video Mobility
Private
IP
Service
BRKRST-2041
Metro
Service
© 2014 Cisco and/or its affiliates. All rights reserved.
Public
IP
Service
Cisco Public
108
Metro
Service
Key Takeaways
 Understand how WAN characteristics can affect your applications.
– Bandwidth, latency, loss
 A modular hierarchical network infrastructure is the foundation for a solid WAN
architecture.
 Encryption is a foundation component of all WAN designs and can be deployed
transparently.
 Understand how to build wide area network leveraging Internet transport with
Intelligent WAN.
 Design a network with consistent behavior that provides predictable
performance.
 More is not always better. Keep it simple!
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
109
Complete Your Online Session Evaluation
• Give us your feedback and you
could win fabulous prizes. Winners
announced daily.
• Complete your session evaluation
through the Cisco Live mobile app
or visit one of the interactive kiosks
located throughout the convention
center.
Don’t forget: Cisco Live sessions will be available
for viewing on-demand after the event at
CiscoLive.com/Online
BRKRST-2041
© 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
110
111