You are on page 1of 103

MPLS WAN

Technology Design Guide
August 2014 Series

Table of Contents
Preface.........................................................................................................................................1
CVD Navigator..............................................................................................................................2
Use Cases................................................................................................................................... 2
Scope.......................................................................................................................................... 2
Proficiency................................................................................................................................... 2
Introduction..................................................................................................................................3
Related Reading........................................................................................................................... 3
Technology Use Cases................................................................................................................ 3
Use Case: Site-to-Site Communications Using MPLS L3VPN Services.................................. 3
Design Overview.......................................................................................................................... 4
WAN Design............................................................................................................................ 4
MPLS WAN Transport.............................................................................................................. 4
Ethernet WAN.......................................................................................................................... 4
WAN-Aggregation Designs...................................................................................................... 5
MPLS Static Design Model...................................................................................................... 5
MPLS Dynamic Design Model................................................................................................. 6
Dual MPLS Design Model........................................................................................................ 6
WAN Remote-Site Designs..................................................................................................... 7
WAN/LAN Interconnection....................................................................................................... 8
WAN Remote Sites—LAN Topology......................................................................................... 9
Layer 2 Access....................................................................................................................... 9
Distribution and Access Layer................................................................................................11
IP Multicast.............................................................................................................................13
Quality of Service.......................................................................................................................13
Deploying the WAN....................................................................................................................15
Overall WAN Architecture Design Goals..................................................................................... 15
IP Routing.............................................................................................................................. 15
LAN Access.......................................................................................................................... 15
High Availability...................................................................................................................... 15
Path Selection Preferences................................................................................................... 15
Quality of Service (QoS)........................................................................................................ 16
Design Parameters................................................................................................................ 16
Table of Contents

Deploying an MPLS WAN............................................................................................................ 17
Design Overview.........................................................................................................................17
WAN-Aggregation—MPLS CE Routers....................................................................................17
Remote Sites—MPLS CE Router Selection............................................................................. 18
Design Details....................................................................................................................... 20
Deployment Details.................................................................................................................... 23
Configuring the MPLS CE Router.......................................................................................... 23
Configuring the Remote-Site MPLS CE Router...................................................................... 35
Adding a Secondary MPLS Link on an Existing MPLS CE Router.......................................... 54
Configuring the Secondary Remote-Site Router.................................................................... 58
Deploying a WAN Remote-Site Distribution Layer....................................................................... 74
Deployment Details.....................................................................................................................74
Connecting the Single or Primary Remote-Site Router to the Distribution Layer.....................74
Connecting the Secondary Remote-Site Router to the Distribution Layer............................. 82
Deploying WAN Quality of Service..............................................................................................89
Deployment Details.................................................................................................................... 89
Configuring QoS.................................................................................................................... 89
Appendix A: Product List............................................................................................................95
Appendix B: Device Configuration Files.......................................................................................98
Appendix C: Changes.................................................................................................................99

Table of Contents

please visit the CVD Foundation web site. data center. complete system. and best practices for specific types of technology. CVDs include two guide types that provide tested design details: • Technology design guides provide deployment details. WAN. Both CVD types provide a tested starting point for Cisco partners or customers to begin designing and deploying systems. • Solution design guides integrate existing CVDs but also include product features and functionality across Cisco products and sometimes include information about third-party integration. information about validated products and software. more reliable. The CVD Foundation series incorporates wired and wireless LAN. you should use guides that belong to the same release. Each series describes a lab-validated. To ensure the compatibility of designs in the CVD Foundation. Using the CVD Foundation simplifies system integration. Cisco engineers have comprehensively tested and documented each design in order to ensure faster. CVD Foundation Series This CVD Foundation guide is a part of the August 2014 Series. and network management technologies. features. and applications that address customer needs. This approach assures that the guides in a series are fully compatible with one another. Preface August 2014 Series 1 . in the same network lab. the guides themselves are tested together. For the most recent CVD Foundation guides. Comments and Questions If you would like to comment on a guide or ask questions. CVDs incorporate a broad set of technologies. security. please use the feedback form.Preface Cisco Validated Designs (CVDs) present systems that are based on common use cases or engineering priorities. allowing you to select solutions that solve an organization’s problems—without worrying about the technical complexity. and fully predictable deployment. As Cisco develops a CVD Foundation series.

implementing. This section is a quick reference only. Proficiency This guide is for people with the following technical proficiencies—or equivalent experience: • CCNP Routing and Switching—3 to 5 years planning. see the “Design Overview” section in this guide. and CVDs related to this guide. the scope or breadth of the technology covered. and troubleshooting local and widearea networks To view the related CVD guides. Related CVD Guides VALIDATED DESIGN For more information.CVD Navigator The CVD Navigator helps you determine the applicability of this guide by summarizing its key elements: the use cases. click the titles or visit the CVD Foundation web site. verifying. see the Introduction. Scope VALIDATED DESIGN Campus Wired LAN Technology Design Guide GET VPN Technology Design Guide This guide covers the following areas of technology and products: • WAN design using Layer 3 MPLS services for central and remote sites VALIDATED DESIGN VPN WAN Technology Design Guide • Remote-site WAN redundancy options • Routing policy and control for WAN aggregation and remote sites • WAN quality of service (QoS) design and configuration For more information. For more details. the proficiency or experience recommended. CVD Navigator August 2014 Series 2 . Use Cases This guide addresses the following technology use cases: • Site-to-Site Communications Using MPLS L3VPN Services— Many organizations are deploying Multiprotocol Label Switching (MPLS) WAN services in order to connect remote locations over private cloud Layer 3 VPN-based providermanaged MPLS networks. see the “Use Cases” section in this guide.

To control operational costs.Introduction The MPLS WAN Technology Design Guide provides flexible guidance and configuration for Multiprotocol Label Switching (MPLS) transport. regardless of location. the WAN design must provide a common resource access experience to the workforce. Use Case: Site-to-Site Communications Using MPLS L3VPN Services This guide helps organizations deploy WAN services in order to connect remote locations over private cloud Layer 3 VPN-based provider managed MPLS services. centrally managed infrastructure. The ubiquity of carrier-provided MPLS networks makes it a required consideration for an organization building a WAN. Technology Use Cases For remote-site users to effectively support the business. • Support for Layer 2 or Layer 3 distribution switching designs • Support for IP multicast using Multicast VPN (mVPN) service provider-based offering • QoS for WAN traffic such as Voice over IP (VoIP) and business critical applications Introduction August 2014 Series 3 . the WAN architecture requires a flexible design. As organizations move into multinational or global business markets. and data transport onto a single. organizations require that the WAN provide sufficient performance and reliability. Related Reading The Layer 2 WAN Technology Design Guide provides guidance and configuration for a VPLS or Metro Ethernet transport. To reduce the time needed to deploy new technologies that support emerging business applications and communications. Although most of the applications and services that the remote-site worker uses are centrally located. the WAN must support the convergence of voice. video. The VPN WAN Technology Design Guide provides guidance and configuration for broadband or Internet transport in a both a primary or backup role. The ability to easily scale bandwidth or to add additional sites or resilient links makes MPLS an effective WAN transport for growing organizations. This design guide enables the following network capabilities: • IP any-to-any WAN connectivity for up to 500 remote sites and one or two central hub site locations • Deployment of single or dual MPLS service providers for resiliency using single or dual routers in remote site locations • Static routing or dynamic Border Gateway Protocol (BGP) peering with the MPLS service provider for site-to-site communications. they require a flexible network design that allows for country-specific access requirements and controls complexity.

provides a design that enables highly available. the WAN is an IP network. and these transports can be easily integrated to the design. In addition. such as IP. which can result in significant cost savings and a reduction in operational complexity for enterprises. The chosen architecture designates a primary WAN-aggregation site that is analogous to the hub site in a traditional hub-and-spoke design. OC-3. Subscribers who need to transport IP multicast traffic can enable Multicast VPNs (MVPNs). The WAN leverages MPLS VPN as a primary WAN transport or as a backup WAN transport (to an alternate MPLS VPN primary). ATM. This site has direct connections to both WAN transports and high-speed connections to the selected service providers. This peer-to-peer model allows enterprise subscribers to outsource routing information to service providers.Design Overview This guide. and so on). You can integrate this economical solution seamlessly over any existing infrastructure. or Ethernet. Introduction August 2014 Series 4 . Much of the discussion in this guide can also be applied to non-Ethernet media (such as T1/E1. and optimized connectivity for multiple remote-site LANs. DS-3. Frame Relay. MPLS WAN Transport Cisco IOS Software Multiprotocol Label Switching (MPLS) enables enterprises and service providers to build next-generation. Ethernet WAN Both of the WAN transports mentioned previously use Ethernet as a standard media type. This document shows you how to deploy the network foundation and services to enable the following: • MPLS WAN connectivity for up to 500 remote sites • Primary and secondary links to provide redundant topology options for resiliency • Wired LAN access at all remote sites WAN Design The primary focus of the design is to allow usage of the following commonly deployed WAN transports: • Multiprotocol Label Switching (MPLS) Layer 3 VPN (primary) • Multiprotocol Label Switching (MPLS) Layer 3 VPN (secondary) • Internet VPN (secondary) At a high level. MPLS Layer 3 VPNs use a peer-to-peer VPN Model that leverages BGP to distribute VPN-related information. the MPLS WAN Technology Design Guide. but they are not explicitly discussed. the site uses network equipment scaled for high performance and redundancy. intelligent networks that deliver a wide variety of advanced. The WAN is the networking infrastructure that provides an IP-based interconnection between remote sites that are separated by large geographic distances. secure. The primary WAN-aggregation site is coresident with the data center and usually the primary campus or LAN as well. The usage of an Internet VPN transport to provide a redundant topology option for resiliency is covered in the VPN WAN Technology Design Guide. value-added services over a single infrastructure. Ethernet is becoming a dominant carrier handoff in many markets and it is relevant to include Ethernet as the primary media in the tested architectures.

The primary differences between the various designs are the usage of routing protocols and the overall scale of the architecture. Each MPLS carrier terminates to a dedicated WAN router with a primary goal of eliminating any single points of failure. they are typically known as customer edge (CE) routers. Each of the design models is shown with LAN connections into either a collapsed core/distribution layer or a dedicated WAN distribution layer. A similar method of connection and configuration is used for both. The WAN transport options include MPLS VPN used as a primary or secondary transport.WAN-aggregation design models MPLS Static MPLS Dynamic Dual MPLS Remote sites Up to 50 Up to 100 Up to 500 WAN links Single Single Dual Edge routers Single Single Dual WAN routing protocol None (static) BGP (dynamic) BGP (dynamic) Transport 1 MPLS VPN A MPLS VPN A MPLS VPN A Transport 2 — — MPLS VPN B The characteristics of each design are discussed in the following sections. and these devices should also connect into the distribution layer. This design guide documents multiple WAN-aggregation design models that are statically or dynamically routed with either single or dual MPLS carriers. In all of the WAN-aggregation designs. A single VPN hub router is used across both designs. Table 1 . For each design model.WAN-Aggregation Designs The WAN-aggregation (hub) designs include two or more WAN edge routers. Each transport connects to a dedicated CE router. Introduction August 2014 Series 5 . When WAN edge routers are referred to in the context of the connection to a carrier or service provider. The various design models are contrasted in the following table. tasks such as IP route summarization are performed at the distribution layer. you can select several router platforms with differing levels of performance and resiliency capabilities. All of the WAN edge routers connect into a distribution layer. There are no functional differences between these two methods from the WAN-aggregation perspective. There are other various devices supporting WAN edge services.

• Has a single MPLS VPN carrier.MPLS Static Design Model The MPLS Static design model (Figure 1): • Supports up to 50 remote sites. MPLS Dynamic Design Model The MPLS Dynamic design model (Figure 1): • Supports up to 100 remote sites. Figure 1 . • Has a single MPLS VPN carrier. • Uses static routing with MPLS VPN carrier.MPLS Static and MPLS Dynamic design models (single MPLS carrier) Core Layer Distribution Layer Collapsed Core/ Distribution Layer MPLS CE Router MPLS CE Router MPLS Introduction MPLS 2183 Static Routing or BGP Dynamic Routing August 2014 Series 6 . • Uses BGP routing with MPLS VPN carrier.

WAN remote-site designs MPLS WAN Nonredundant MPLS-A MPLS-B Redundant Links & Routers MPLS-A MPLS-B 2117 MPLS Redundant Links Introduction August 2014 Series 7 . • Has multiple MPLS VPN carriers. • Is typically used with a dedicated WAN distribution layer.Dual MPLS design model Core Layer Collapsed Core/ Distribution Layer MPLS CE Routers Distribution Layer MPLS CE Routers MPLS A BGP Dynamic Routing MPLS B MPLS A MPLS B 2184 BGP Dynamic Routing WAN Remote-Site Designs This guide documents multiple WAN remote-site designs. Figure 2 .Dual MPLS Design Model The Dual MPLS design model (Figure 2): • Supports up to 500 remote sites. Figure 3 . and they are based on various combinations of WAN transports mapped to the site specific requirements for service levels and redundancy. • Uses BGP routing with MPLS VPN carrier.

The remote-site designs include single or dual WAN edge routers. These are always MPLS CE routers.
Most remote sites are designed with a single router WAN edge; however, certain remote-site types require a
dual router WAN edge. Dual router candidate sites include regional office or remote campus locations with large
user populations, or sites with business critical needs that justify additional redundancy to remove single points
of failure.
The overall WAN design methodology is based on a primary WAN-aggregation site design that can
accommodate all of the remote-site types that map to the various link combinations listed in the following table.
Table 2 - WAN remote-site transport options
WAN remote-site routers

WAN transports

Primary transport

Secondary transport

Single

Single

MPLS VPN A

Single

Dual

MPLS VPN A

MPLS VPN B

Dual

Dual

MPLS VPN A

MPLS VPN B

The modular nature of the network design enables you to create design elements that you can replicate
throughout the network.
Both WAN-aggregation designs and all of the WAN remote-site designs are standard building blocks in the
overall design. Replication of the individual building blocks provides an easy way to scale the network and allows
for a consistent deployment method.

WAN/LAN Interconnection
The primary role of the WAN is to interconnect primary site and remote-site LANs. The LAN discussion within
this guide is limited to how the WAN-aggregation site LAN connects to the WAN-aggregation devices and how
the remote-site LANs connect to the remote-site WAN devices. Specific details regarding the LAN components
of the design are covered in the Campus Wired LAN Technology Design Guide.
At remote sites, the LAN topology depends on the number of connected users and physical geography of the
site. Large sites may require the use of a distribution layer to support multiple access-layer switches. Other sites
may only require an access-layer switch directly connected to the WAN remote-site routers. The variants that
are tested and documented in this guide are shown in the following table.
Table 3 - WAN remote-site LAN options
WAN remote-site routers

WAN transports

LAN topology

Single

Single

Access only
Distribution/access

Single

Dual

Access only
Distribution/access

Dual

Dual

Access only
Distribution/access

Introduction

August 2014 Series

8

WAN Remote Sites—LAN Topology
For consistency and modularity, all WAN remote sites use the same VLAN assignment scheme, which is shown
in the following table. This design guide uses a convention that is relevant to any location that has a single access
switch and this model can also be easily scaled to additional access closets through the addition of a distribution
layer.
Table 4 - WAN remote-sites—VLAN assignment
VLAN

Usage

Layer 2 access

Layer 3 distribution/ access

VLAN 64

Data

Yes

VLAN 69

Voice

Yes

VLAN 99

Transit

Yes

Yes

(dual router only)

(dual router only)

VLAN 50

Router link (1)

Yes

VLAN 54

Router link (2)

Yes
(dual router only)

Layer 2 Access
WAN remote sites that do not require additional distribution layer routing devices are considered to be flat or
from a LAN perspective they are considered unrouted Layer 2 sites. All Layer 3 services are provided by the
attached WAN routers. The access switches, through the use of multiple VLANs, can support services such as
data and voice. The design shown in the following figure illustrates the standardized VLAN assignment scheme.
The benefits of this design are clear: all of the access switches can be configured identically, regardless of the
number of sites in this configuration.
Access switches and their configuration are not included in this guide. The Campus Wired LAN Technology
Design Guide provides configuration details on the various access switching platforms.
IP subnets are assigned on a per-VLAN basis. This design only allocates subnets with a 255.255.255.0 netmask
for the access layer, even if less than 254 IP addresses are required. (This model can be adjusted as necessary
to other IP address schemes.) The connection between the router and the access switch must be configured
for 802.1Q VLAN trunking with subinterfaces on the router that map to the respective VLANs on the switch. The
various router subinterfaces act as the IP default gateways for each of the IP subnet and VLAN combinations.
Figure 4 - WAN remote site—Flat Layer 2 LAN (single router)

MPLS

VLAN 64 - Data
VLAN 69 - Voice

802.1Q VLAN Trunk (64, 69)

Introduction

2118

No HSRP
Required

August 2014 Series

9

A similar LAN design can be extended to a dual-router edge as shown in the following figure. This design change
introduces some additional complexity. The first requirement is to run a routing protocol. You need to configure
Enhanced Interior Gateway Protocol (EIGRP) between the routers. For consistency with the primary site LAN, use
EIGRP process 100.
Because there are now two routers per subnet, a First Hop Redundancy Protocol (FHRP) must be implemented.
For this design, Cisco selected Hot Standby Router Protocol (HSRP) as the FHRP. HSRP is designed to allow for
transparent failover of the first-hop IP router. HSRP ensures high network availability by providing first-hop routing
redundancy for IP hosts configured with a default gateway IP address. HSRP is used in a group of routers for
selecting an active router and a standby router. When there are multiple routers on a LAN, the active router is the
router of choice for routing packets; the standby router is the router that takes over when the active router fails or
when preset conditions are met.
Figure 5 - WAN remote site—Flat Layer 2 LAN (dual router)

MPLS

MPLS

iBGP
EIGRP
VLAN99 - Transit

HSRP VLANs
Active HSRP Router

VLAN 64 - Data

802.1Q VLAN Trunk (64, 69, 99)

2119

VLAN 69 - Voice

Enhanced Object Tracking (EOT) provides a consistent methodology for various router and switching features to
conditionally modify their operation based on information objects available within other processes. The objects
that can be tracked include interface line protocol, IP route reachability, and IP service-level agreement (SLA)
reachability, as well as several others.
The IP SLA feature provides a capability for a router to generate synthetic network traffic that can be sent to a
remote responder. The responder can be a generic IP endpoint that can respond to an Internet Control Message
Protocol (ICMP) echo (ping) request, or can be a Cisco router running an IP SLA responder process, that can
respond to more complex traffic such as jitter probes. The use of IP SLA allows the router to determine endto-end reachability to a destination and also the roundtrip delay. More complex probe types can also permit the
calculation of loss and jitter along the path. IP SLA is used in tandem with EOT within this design.
In order to improve convergence times after an MPLS WAN failure, HSRP has the capability to monitor the
reachability of a next-hop IP neighbor through the use of EOT and IP SLA. This combination allows for a router
to give up its HSRP Active role if its upstream neighbor becomes unresponsive. This provides additional network
resiliency.

Introduction

August 2014 Series

10

1Q VLAN trunk configuration can easily accommodate an additional subinterface. 69. The dual router designs also warrant an additional component that is required for proper routing in certain scenarios. an MPLS A + MPLS B remote site communicating with an MPLS-B-only remote site). EOT of IP SLA probes is implemented in conjunction with HSRP so that in the case of WAN transport failure. 99) Active HSRP Router HSRP is configured to be active on the router with the highest priority WAN transport. a traffic flow from a remote-site host might be sent to a destination reachable via the alternate WAN transport (for example. These EtherChannel links are configured as 802. In these cases. This is more effective than simply monitoring the status of the WAN interface. which then forwards the traffic to the proper destination.Voice 2142 802.1Q VLAN Trunk (64.1Q VLAN trunks. The primary WAN transport router then forwards the traffic out the same data interface to send it to the alternate WAN transport router.Figure 6 . to support both a routed point-to-point link to allow EIGRP routing with the distribution switch. To implement this design. This topology works well with either a single or dual router WAN edge.Transit HSRP VLANs VLAN 64 . to provide a transit network for direct communication between the WAN routers. The routing protocol runs between router subinterfaces assigned to the transit network. and it is only used for router-router communication.WAN remote-site—IP SLA probe to verify upstream device reachability Detailed View IP SLA Probe as Tracked Object WAN IP SLA Probe WAN Interface Upstream Interface WAN WAN R1 EIGRP VLAN 99 . Distribution and Access Layer Large remote sites may require a LAN environment similar to that of a small campus LAN that includes a distribution layer and access layer. There are no hosts connected to the transit network. the routers should connect via EtherChannel links to the distribution switch. No additional router interfaces are required with this design modification because the 802. Introduction August 2014 Series 11 . The appropriate method to avoid sending the traffic out the same interface is to introduce an additional link between the routers and designate the link as a transit network (VLAN 99). The IP SLA probes are sent from the MPLS CE router to the MPLS Provider Edge (PE) router in order to ensure reachability of the next hop router. the standby HSRP router associated with the lower priority (alternate) WAN transport becomes the active HSRP router. This is referred to as hairpinning. and in the dual router design.Data VLAN 69 .

Router 2 Link VLAN 99 . zz) 802.WAN remote site—Connection to distribution layer WAN WAN 802. A full distribution and access-layer design is shown in the following figure.1Q Trunk (yy.Voice VLAN zz .1Q Trunk (50.Router 1 Link VLAN 54 . Figure 8 .Router 1 Link 802.Router 2 Link VLAN 99 .Figure 7 .Data VLAN xx . 99) 802. zz) VLAN ww . No HSRP is required when the design includes a distribution layer. xx) VLAN 50 .Data VLAN yy .1Q Trunk (50) 802.1Q Trunk (54.1Q Trunk (ww.Router 1 Link VLAN 54 .1Q Trunk (ww. xx) 802.1Q Trunk (54. 99) 802.1Q Trunk (yy.Transit August 2014 Series 12 .1Q Trunk (yy. zz) VLAN 50 . xx) 802. 99) The distribution switch handles all access-layer routing. with VLANs trunked to access switches. 99) 802.1Q Trunk (50.Transit 2007 802.Voice No HSRP Required Introduction 2144 VLAN 50 .WAN remote site—Distribution and access layer (dual router) WAN 802.1Q Trunk (ww.

IP telephony Music On Hold (MOH) and IP video broadcast streaming are two examples of IP Multicast applications. The design uses an Anycast RP implementation strategy. delay. and congestion mechanisms as part of the integrated QoS to help ensure optimal use of network resources. QoS enables a multitude of user services and applications. either during the initial deployment or later with minimum system impact and engineering effort. and loss parameters. time-sensitive applications are affected by jitter. jitter. and delaysensitive data to coexist on the same network. queuing. and loss. QoS is an essential function of the network infrastructure devices used throughout this architecture. end hosts must join a multicast group by sending an Internet Group Management Protocol (IGMP) message to their local multicast router. Introduction August 2014 Series 13 . The goal of this design is to provide sufficient classes of service to allow you to add voice. there are wired and wireless connectivity options that provide advanced classification.” While it is true that IP networks forward traffic on a best-effort basis by default. Two RPs share the load for source registration and the ability to act as hot backup routers for each other. Within the architecture. the distribution layer performs the RP function. including real-time voice. measurable. and sometimes guaranteed services. This design is fully enabled for a single global scope deployment of IP Multicast. In reality. the network affects all traffic flows and must be aware of end-user requirements and services being offered. In order for the network to provide predictable. The RP is a control-plane operation that should be placed in the core of the network or close to the IP Multicast sources on a pair of Layer 3 switches or routers. delay. Quality of service (QoS) enables a multitude of user services and applications to coexist on the same network. ensuring that each has the appropriate share of the network resources to protect the user experience and ensure the consistent operations of business critical applications. and management traffic to the network. and subinterfaces. IP PIM SM is enabled on all interfaces including loopbacks. This functionality allows for the differentiation of applications. Even if you do not require QoS for your current applications. IP Multicast is much more efficient than multiple individual unicast streams or a broadcast stream that would propagate everywhere. However networks are multiservice by design and support real-time voice and video as well as data traffic. To receive a particular IP Multicast data stream. interactive video. Many sum this up as just “speeds and feeds. delay. Even with unlimited bandwidth. this type of routing only works well for applications that adapt gracefully to variations in latency. prioritizing. it must manage bandwidth. IP Multicast routing begins at the distribution layer if the access layer is Layer 2 and provides connectivity to the IP Multicast RP. high-quality video. Quality of Service Most users perceive the network as just a transport utility mechanism to shift data from point A to point B as fast as it can. jitter. and packet loss.IP Multicast IP Multicast allows a single IP data stream to be replicated by the infrastructure (routers and switches) and sent from a single source to multiple receivers. and jitter parameters. the local router consults another router in the network that is acting as a rendezvous point (RP) to map the receivers to active sources so that they can join their streams. you can use QoS for management and network protocols to protect the network functionality and manageability under normal and congested traffic conditions. This strategy provides load sharing and redundancy in Protocol Independent Multicast sparse mode (PIM SM) networks. VLANs. In designs without a core layer. The benefit of this strategy from the WAN perspective is that all IP routing devices within the WAN use an identical configuration referencing the Anycast RPs. critical data applications. In a traditional IP Multicast design. The difference is that real-time applications require packets to be delivered within specified loss.

QoS service class mappings Introduction Service class Per-hop behavior (PHB) Differentiated services code point (DSCP) IP precedence (IPP) Class of service (CoS) Network layer Layer 3 Layer 3 Layer 3 Layer 2 Network control CS6 48 6 6 Telephony EF 46 5 5 Signaling CS3 24 3 3 Multimedia conferencing AF41. 14 1 1 Scavenger CS1 8 1 1 Default “best effort” DF 0 0 0 August 2014 Series 14 . 38 4 4 Real-time interactive CS4 32 4 4 Multimedia streaming AF31. Table 5 . and maintenance (OAM) CS2 16 2 2 Bulk data AF11. 23 18. 28. 30 3 3 Broadcast video CS5 40 4 4 Low-latency data AF21. This table is included as a reference. 32.The QoS classifications in the following table are applied throughout this design. 12. 22 2 2 Operation. administration. 33 26. 42. 36. 22. 12. 43 34. 20. 13 10.

In the centralized Internet model. The single WAN transport routing functions as follows. High Availability The network must tolerate single failure conditions including the failure of any single WAN transport link or any single network device at the primary WAN-aggregation site. only encrypted traffic to other DMVPN sites is permitted to use the Internet link. LAN Access All remote sites are to support both wired LAN access. • Remote sites classified as single-router. there is no local Internet access for web browsing or cloud services. • Connects to any other site—The route is through the primary site. for this design. dual-link must be able to tolerate the loss of either an edge router or a WAN transport. however. for ease of troubleshooting and to prevent oversubscription of IP telephony Call Admission Control (CAC) limits • Provide site-site remote routing via the primary WAN-aggregation site (hub-and-spoke model) • Permit optimal direct site-site remote routing when carrier services allow (spoke-to-spoke model) • Support IP Multicast sourced from the primary WAN-aggregation site At the WAN remote sites.Deploying the WAN Overall WAN Architecture Design Goals IP Routing The design has the following IP routing goals: • Provide optimal routing connectivity from primary WAN-aggregation sites to all remote locations • Isolate WAN routing topology changes from other portions of the network • Ensure active/standby symmetric routing when multiple paths exist. with traffic flowing along the same path in both directions. Symmetric routing simplifies troubleshooting because bidirectional traffic flows always traverse the same links. MPLS VPN-connected site: • Connects to a site on the same MPLS VPN—The optimal route is direct within the MPLS VPN (traffic is not sent to the primary site). Path Selection Preferences There are many potential traffic flows based on which WAN transports are in use and whether or not a remote site is using a dual WAN transport. Deploying the WAN August 2014 Series 15 . • Remote sites classified as dual-router. It is worth noting that sites with Internet/DMVPN for backup transport could potentially provide local Internet capability. This model is referred to as a centralized Internet model. a default route is advertised to the WAN remote sites in addition to the internal routes from the data center and campus. The use of the dual WAN transports is specifically tuned to behave in an active/standby manner. dual-link must be able tolerate the loss of either WAN transport. This type of configuration provides symmetric routing.

4.15 Network Time Protocol (NTP) server 10. MPLS VPN primary + MPLS VPN secondary dual-connected site: • Connects to a site on the same MPLS VPN—The optimal route is direct within the MPLS VPN (traffic is not sent to the primary site). • Connects to any other site—The route is through the primary site.48. DHCP server 10.48.48.10 Cisco Secure Access Control System (ACS) 10.local Active Directory. Traffic must be classified and queued and the WAN connection must be shaped to operate within the capabilities of the connection.4.Universal design parameters Network service IP address Domain name cisco. Design Parameters This design guide uses certain standard design parameters and references various network infrastructure services that are not located within the WAN. When the WAN design uses a service provider offering with QoS.The design assumes that one of the MPLS VPN WAN transports is designated as the primary transport. which is the preferred path in most conditions. the WAN edge QoS classification and treatment must align to the service provider offering to ensure consistent end-toend QoS treatment of traffic. These parameters are listed in the following table. DNS server.4. Table 6 .17 Deploying the WAN August 2014 Series 16 . Quality of Service (QoS) The network must ensure that business applications perform across the WAN during times of network congestion.

and the routers have all the elements of a true carrier-class routing product that serves both enterprise and service-provider networks. The amount of bandwidth required at the WAN-aggregation site determines which model of router to use. servicesintegrated Cisco routing platform. modular. 2. with the flexibility to support a wide range of 3. and scaling. and 36 Gbps • Cisco ASR 1002 router configured with an embedded service processor 5 (ESP5) • Cisco ASR 1001 router fixed configuration with a 2. The choice of whether to implement a single router or dual router is determined by the number of carriers that are required in order to provide connections to all of the remote sites. The most critical devices are the WAN routers that are responsible for reliable IP forwarding and QoS.5. You should consider the following: the forwarding performance of the router using an Ethernet WAN deployment with broad services enabled.5 Gbps embedded service processor • Cisco 4451X Integrated Services Router All of the design models can be constructed using any of the MPLS CE routers listed in Table 7.0 Gbps. Table 7 . Cisco ASR 1000 Series Aggregation Services Routers represent the next-generation.to 16-mpps (millions of packets per second) packet-forwarding capabilities. 20 Gbps. and the number of remote sites.WAN aggregation—MPLS CE router options Service Cisco 4451X ASR 1001 ASR 1002 ASR 1002-X Ethernet WAN with services 300 Mbps 500 Mbps 750 Mbps 1Gbps Software Redundancy Option None Yes Yes Yes Redundant power supply Option Default Default Default Supported Design Models All All All All Suggested Design Model MPLS Static MPLS Dynamic Dual MPLS Dual MPLS Suggested Number of Remote Sites 25 100 250 250+ Deploying an MPLS WAN August 2014 Series 17 . They are specifically designed for WAN aggregation. This design uses the following routers as MPLS CE routers: • Cisco ASR 1002-X router configured with an embedded service processor (ESP) default bandwidth of 5 Gbps upgradable with software licensing options to 10 Gbps. The Cisco ASR 1000 Series is fully modular from both hardware and software perspectives. the router’s alignment with the suggested design model.Deploying an MPLS WAN Design Overview WAN-Aggregation—MPLS CE Routers The MPLS WAN designs are intended to support up to 500 remote sites with a combined aggregate WAN bandwidth of up to 1.to 40-Gbps system bandwidth performance.

4. or you can use it to support a more complex LAN topology by connecting the CE router directly to a distribution layer. 3. dual-link remote-site requires four router interfaces when using a port-channel to connect to an access or distribution layer. The single link MPLS WAN remote site is the most basic of building blocks for any remote location. The MPLS CE routers at the WAN remote sites connect in the same manner as the MPLS CE routers at the WAN-aggregation site. is the ability to process the expected amount and type of traffic. The IP routing is straightforward and can be handled entirely by using static routes at the WAN-aggregation site and static default routes at the remote site. and a properly licensed Cisco IOS Software image that supports the set of features that is required by the topology. Dynamic routing makes it easy to add or modify IP networks at the remote site because any changes are immediately propagated to the rest of the network. Not all service modules are supported in Cisco 4451-X ISR. A single-router. The ability to implement this solution with a variety of potential router choices is one of the benefits of a modular design approach. single-link remote sites. Add the EHWIC-1GE-SFP-CU to the Cisco 2900 and 3900 Series Integrated Services Routers in order to provide the additional WAN-facing interface. there is significant value to configuring this type of site with dynamic routing and this approach is used for the MPLS Dynamic and Dual MPLS designs. The performance numbers are conservative numbers obtained when the router is passing IMIX traffic with heavy services configured and the CPU utilization is under 75 percent. There are many factors to consider in the selection of the WAN remote-site routers. However. 2. 5. MPLS VPN-connected sites require static routing in order to be handled by the carrier. You can use this design with the CE router connected directly to the access layer. The 1941 is recommended for use at single-router. Cisco tested multiple integrated service router models as MPLS CE routers.WAN remote-site Cisco Integrated Services Router options 8911 19412 2911 2921 2951 3925 3945 4451-X 8 Mbps 25 Mbps 35 Mbps 50 Mbps 75 Mbps 100 Mbps 150 Mbps 1 Gbps On-board FE ports 1 (and 8-port LAN switch) 0 0 0 0 0 0 0 On-board GE ports4 1 2 3 3 3 3 3 4 Service module slots5 0 0 1 1 2 2 4 2 Redundant power supply option No No No No No Yes Yes Yes Ethernet WAN with services3 Notes: 1. The Cisco 891 Integrated Services Router is recommended for use at single-router. enough module slots. Deploying an MPLS WAN August 2014 Series 18 .Remote Sites—MPLS CE Router Selection The actual WAN remote-site routing platforms remain unspecified because the specification is tied closely to the bandwidth required for a location and the potential requirement for the use of service module slots. and any changes or modifications require a change request to the carrier. Table 8 . Some service modules are double-wide. and key to the initial deployment. You also need to make sure that you have enough interfaces. Among those. single-link remote sites. and the expected performance is shown in the following table.

The smaller scale MPLS Static design uses static routing and relies on the carrier to configure the additional required static routes on the PE routers. single-link) MPLS VPN MPLS VPN Static Routing Dynamic Routing MPLS Dynamic MPLS Static 2124 Static Routing You can augment the basic single-link design by adding an alternate WAN transport that uses a secondary MPLS carrier and either connects on the same router or on an additional router. Figure 9 . you provide the first level of high availability for the remote site.MPLS WAN remote site (single-router. It is mandatory to run dynamic routing when there are multiple paths and the Dual MPLS or MPLS Dynamic design models are used. This design can tolerate the loss of the primary router because the secondary router reroutes traffic via the alternate path. The routing protocols are tuned to ensure the proper path selection. Figure 10 .MPLS WAN dual-carrier remote site (dual-link options) MPLS VPN B MPLS VPN A Dual MPLS Design Model Only MPLS VPN B 2125 MPLS VPN A The dual-router. The router can automatically detect failure of the primary link and reroute traffic to the secondary path. Deploying an MPLS WAN August 2014 Series 19 . dual-link design continues to improve upon the level of high availability for the site. Tech Tip We recommend that you select the Dual MPLS or MPLS Dynamic designs if you intend to use resilient WAN links or want to be able to modify your routing configuration without carrier involvement. By adding an additional link.

Deploying an MPLS WAN August 2014 Series 20 . but may not be universally available across all MPLS VPN carriers. The various CE routers advertise their routes to the PE routers. you typically need to use a routing protocol. we decided to limit the focus of this design guide. All devices use EtherChannel connections consisting of two port bundles. Due to the multiplicity of potential choices for transport. Other media types are commonly used (such as T1/E1). and their configurations are not included in this guide. you need to install and configure MPLS CE routers at every location. This also allows for easy transition from a single-homed to a dual-homed remote-site design by adding an additional link to an existing remote site. The PE routers propagate the routing information within the carrier network and in turn re-advertise the routes back to other CE routers. A static routing option is also included to support smaller scale requirements that do not require a dynamic routing protocol. CE routers are only able to communicate with other CE routers across the WAN via intermediate PE routers.MPLS VPN (PE-CE connections) MPLS Carrier PE Direct Adjacencies Only Between CE and PE Routers PE CE Direct Adjacencies Only Between CE and PE Routers 2126 CE Both the PE and CE routers are required to have sufficient IP-routing information in order to provide end-toend reachability. For an MPLS VPN WAN deployment. MPLS VPNs require a link between a PE router and a CE router. WAN transport via Ethernet is the only media type tested and included in the configuration section. and can rely on static routing because there is only a single path to any destination. Sites with only a single WAN transport (a single-homed site) do not require dynamic PE-CE routing. including the WAN-aggregation site. The Dual MPLS and MPLS Dynamic designs use dynamic PE-CE routing with BGP.Design Details All WAN-aggregation MPLS CE routers connect to the same resilient switching device in the distribution layer. You can accomplish additional forwarding performance by increasing the number of physical links within an EtherChannel. This design recommends dynamic PE-CE routing to provide consistency with configurations across both single-homed and dual-homed sites. BGP is most commonly used for this purpose. and these technologies are reliable and well understood. Documentation of additional variants is available in other guides. Cisco did not test the PE routers. This design provides both resiliency and additional forwarding performance. media type. Figure 11 . Static routing is used in the MPLS Static design model. Tech Tip EIGRP and Open Shortest Path First (OSPF) Protocol are also effective as PE-CE routing protocols. and at every MPLS WAN-connected remote site. This propagation of routing information is known as dynamic PE-CE routing and it is essential when any sites have multiple WAN transports (often referred to as dual-homed or multi-homed). The PE and CE routers are considered IP neighbors across this link. and interface type. To maintain this routing information.

MPLS Static Design—MPLS CE routing detail WAN Distribution EIGRP Static Routing MPLS CE Router MPLS 2128 Static Routing EIGRP Cisco chose EIGRP as the primary routing protocol because it is easy to configure. As networks grow. processor. such as distribution layer links to the wide area or to a core. and reduce convergence time associated with a link failure. You should program IP summarization on links where logical boundaries exist. you can reduce the amount of bandwidth. By performing IP summarization. and memory necessary to carry large route tables. the number of IP prefixes or routes in the routing tables grows as well. Figure 12 . and can scale to large networks.Dual MPLS and MPLS Dynamic designs—MPLS CE routing detail WAN Distribution WAN Distribution EIGRP EIGRP MPLS CE Routers iBGP eBGP eBGP MPLS A MPLS B eBGP MPLS Dual MPLS MPLS Dynamic 2127 MPLS CE Routers EIGRP The IP routing details for the single MPLS carrier WAN-aggregation topology with static routing are shown in the following figure. and the routing protocol configurations are tuned from their default settings to influence traffic flows to their desired behavior. an MPLS CE router must be connected both to the distribution layer and to its respective MPLS carrier. Multiple routing protocols (EIGRP and BGP) are used to exchange routing information. has flexible summarization and filtering. The IP routing details for the single and dual MPLS carrier WAN-aggregation topology with dynamic routing are shown in the following figure. does not require a large amount of planning. Figure 13 .At the WAN-aggregation site. Deploying an MPLS WAN August 2014 Series 21 .

BGP scales well and you can use it to advertise IP aggregate addresses for remote sites. BGP is straightforward to configure and requires little or no maintenance. To use BGP. Named mode EIGRP includes features such as wide metrics. EIGRP Wide Metric support is on by default and backward compatible with existing routes. In this design. supporting larger multi-gigabit links. this guide uses EIGRP named mode.With the advances in EIGRP. The EIGRP LAN process is configured at the WAN-aggregation site to connect to the primary site LAN distribution layer and at WAN remote sites with dual WAN routers or with distribution-layer LAN topologies. The use of named mode EIGRP allows related EIGRP configurations to be centrally located in the configuration. EIGRP neighbor authentication has been implemented to prevent unauthorized neighbor associations. In this role. For added security. A dual-carrier MPLS design requires an iBGP connection between the CE routers to properly retain routing information for the remote sites. The private ASN range is 64512 to 65534. Deploying an MPLS WAN August 2014 Series 22 . the primary EIGRP process (AS 100) is referred to as EIGRP LAN and uses EIGRP named configuration. you must select an Autonomous System Number (ASN). BGP Cisco chose BGP as the routing protocol for PE and CE routers to connect to the MPLS VPNs because it is consistently supported across virtually all MPLS carriers. In this design. Tech Tip With EIGRP named mode configuration. we use a private ASN (65511) as designated by the Internet Assigned Numbers Authority (IANA).

4. Configure BGP Deploying an MPLS WAN August 2014 Series 23 .48.17 Commands with variables that you must define: class-map [highest class name] Noteworthy parts of system output (or of device configuration files) are highlighted: interface Vlan64 ip address 10. Connect to MPLS PE router 5.Deployment Details How to Read Commands This guide uses the following conventions for commands that you enter at the command-line interface (CLI).255.0 The procedures in this section provide examples for some settings. Redistribute WAN routes into EIGRP 6. Enter them as one command: police rate 10000 pps burst 10000 packets conform-action Commands that specify a value for a variable: ntp server 10.242/32 10. Table 9 .Parameters used in the deployment examples Hostname Loopback IP Address Port Channel IP Address CE-ASR1002-1 10.241/32 10.255.6/30 PROCESS Configuring the MPLS CE Router 1. Configure the distribution switch 2. Configure the WAN aggregation platform 3. Configure connectivity to the LAN 4.32.10.32. Commands at a CLI or script prompt: Router# enable Commands to enter at a CLI prompt: configure terminal Long commands that line wrap are underlined.5 255.32.204.4.4.5.4. The actual settings and values that you use are determined by your current network configuration.2/30 CE-ASR1001-2 10.32.

The LAN distribution switch is the path to the organization’s main campus and data center. interface Port-channel1 description CE-ASR1002-1 no switchport ip address 10. GigabitEthernet2/0/1 no switchport carrier-delay msec 0 Deploying an MPLS WAN August 2014 Series 24 .4. apply the egress QoS macro that was defined in the platform configuration procedure to ensure traffic is prioritized appropriately.255. interface GigabitEthernet1/0/1 description CE-ASR1002-1 Gig0/0/0 ! interface GigabitEthernet2/0/1 description CE-ASR1002-1 Gig0/0/1 ! interface range GigabitEthernet1/0/1. use the same channel numbering on both sides of the link where possible. Configure the physical interfaces to tie to the logical port-channel by using the channel-group command. so you configure EtherChannel statically.1 255. A Layer 3 portchannel interface connects to the distribution switch to the WAN-aggregation router and the internal routing protocol peers across this interface.255. Only the procedures required to support the integration of the WAN-aggregation router into the deployment are included. Also. Not all router platforms can support Link Aggregation Control Protocol (LACP) to negotiate with the switch. Tech Tip As a best practice.252 ip pim sparse-mode logging event link-status carrier-delay msec 0 load-interval 30 no shutdown Step 2:  Configure EtherChannel member interfaces. Step 1:  Configure the Layer 3 port-channel interface and assign the IP address.Procedure 1 Configure the distribution switch Reader Tip This process assumes that the distribution switch has already been configured following the guidance in the Campus Wired LAN Technology Design Guide. The number for the port-channel and channel-group must match.32.

252. router eigrp LAN address-family ipv4 unicast autonomous-system 100 no eigrp stub exit-address-family Step 5:  On the distribution layer switch. Tech Tip It is a best practice to summarize IP routes from the WAN distribution layer towards the core.0.240.255.4.4.0 255.channel-group 1 mode on logging event link-status logging event trunk-status logging event bundle-status no shutdown load-interval 30 macro apply EgressQoS Step 3:  Allow the routing protocol to form neighbor relationships across the port channel interface. router eigrp LAN address-family ipv4 unicast autonomous-system 100 af-interface Port-channel1 no passive-interface authentication mode md5 authentication key-chain LAN-KEY exit-af-interface exit-address-family Step 4:  If it is necessary to disable EIGRP stub routing on the WAN distribution switch.4.0 255.0 summary-address 10.0 255.0 summary-address 10.128. router eigrp LAN address-family ipv4 unicast autonomous-system 100 af-interface Port-channel38 summary-address 10.248.0 summary-address 10.0 exit-af-interface exit-address-family Deploying an MPLS WAN August 2014 Series 25 .32.255. enter the following configuration. configure the layer 3 EIGRP interfaces connected to the LAN core to summarize the WAN network range.255.0 255.0.5.255.160.

router eigrp LAN address-family ipv4 unicast autonomous-system 100 af-interface Port-channel1 summary-address 10. When AAA is enabled for access control. authorization. hostname CE-ASR1002-1 Step 2:  Configure local login and password. Step 1:  Configure the device host name.Step 6:  On the distribution layer switch. all management access to the network infrastructure devices (SSH and HTTPS) is controlled by AAA.0 255. which provides only limited operational privileges.0. A centralized authentication. Procedure 2 Configure the WAN aggregation platform Within this design. there are features and services that are common across all WAN aggregation routers.255. you prevent the disclosure of plain text passwords when viewing configuration files. This makes it easy to identify the device. HTTPS access to the router uses the enable password for authentication. The local login account and password provides basic access authentication to a router. Tech Tip It is a best practice to summarize IP routes from the WAN distribution layer towards the MPLS WAN. username admin password c1sco123 enable secret c1sco123 service password-encryption aaa new-model Step 3:  By default. configure the Layer 3 EIGRP interface connected to the WAN aggregation routers to summarize the WAN remote-site network range. Deploying an MPLS WAN August 2014 Series 26 . These are system settings that simplify and secure the management of the solution. and accounting (AAA) service reduces operational tasks per device and provides an audit log of user access for security compliance and root cause analysis. By enabling password encryption.5. Step 4:  (Optional) Configure centralized user authentication.0 exit-af-interface exit-address-family Repeat this step as needed for additional WAN aggregation routers. The enable password secures access to the device configuration mode. As networks scale in the number of devices to maintain it poses an operational burden to maintain local user accounts on every device.0.

line con 0 transport preferred none logging synchronous Deploying an MPLS WAN August 2014 Series 27 . Specify the transport preferred none on vty lines to prevent errant connection attempts from the CLI prompt. Secure Copy Protocol is enabled. Without this command.48. Both protocols are encrypted for privacy and the unsecure protocols. tacacs server TACACS-SERVER-1 address ipv4 10. which allows the use of code upgrades using Prime Infrastructure via SSH-based SCP protocol. A local AAA user database is also defined in Step 2 on each network infrastructure device to provide a fallback authentication source in case the centralized TACACS+ server is unavailable. Secure HTTP (HTTPS) and Secure Shell (SSH) are secure replacements for the HTTP and Telnet protocols.4. long timeout delays may occur for mistyped commands.15 key SecretKey ! aaa group server tacacs+ TACACS-SERVERS server name TACACS-SERVER-1 ! aaa authentication login default group TACACS-SERVERS local aaa authorization exec default group TACACS-SERVERS local aaa authorization console ip http authentication aaa Step 5:  Configure device management protocols.local ip ssh version 2 no ip http server ip http secure-server ip scp server enable line vty 0 15 transport input ssh transport preferred none Step 6:  Enable synchronous logging. When synchronous logging of unsolicited messages and debug output is turned on. you can continue typing at the device console when debugging is enabled. They use Secure Sockets Layer (SSL) and Transport Layer Security (TLS) to provide device authentication and data encryption. Secure management of the network device is enabled through the use of the SSH and HTTPS protocols. console log messages are displayed on the console after interactive CLI output is displayed or printed. ip domain-name cisco. if the ip name-server is unreachable. are turned off. Telnet and HTTP.TACACS+ is the primary protocol used to authenticate management logins on the infrastructure devices to the AAA server. With this command.

NTP then distributes this time across the organizations network. This allows the network infrastructure devices to be managed by a Network Management System (NMS). The local NTP server typically references a more accurate clock feed from an outside source. logs.255 ip pim sparse-mode Deploying an MPLS WAN August 2014 Series 28 .255. The loopback address is commonly a host address with a 32-bit address mask. such as a radio clock or an atomic clock attached to a time server. An NTP network usually gets its time from an authoritative time source.0/24 network will be able to access the device via SSH or SNMP.241 255.0 0. SNMPv2c is configured both for a read-only and a read-write community string.4. The loopback interface is a logical interface that is always reachable as long as the device is powered on and any IP interface is reachable to the network.4.0.255 line vty 0 15 access-class 55 in ! snmp-server community cisco RO 55 snmp-server community cisco123 RW 55 Tech Tip If you configure an access-list on the vty interface you may lose the ability to use ssh to login from one router to the next for hop-by-hop troubleshooting. you can increase network security by using an access list to limit the networks that can access your device.4. snmp-server community cisco RO snmp-server community cisco123 RW Step 8:  If operational support is centralized in your network. The Network Time Protocol (NTP) is designed to synchronize a network of devices. You should program network devices to synchronize to a local NTP server in the network. interface Loopback 0 ip address 10.32. access-list 55 permit 10.17 ! clock timezone PST -8 clock summer-time PDT recurring ! service timestamps debug datetime msec localtime service timestamps log datetime msec localtime Step 10:  Configure an in-band management interface.48.4.Step 7:  Enable Simple Network Management Protocol (SNMP). you can cross-reference events in a network. Allocate the loopback address from the IP address block that the router summarizes to the rest of the network. In this example.255. ntp server 10.48.0. the loopback address is the best way to manage the router in-band. only devices on the 10. Layer 3 process and features are also bound to the loopback interface to ensure process resiliency. By configuring console messages.48. Because of this capability. and debug output to provide time stamps on output. Step 9:  Configure a synchronized clock.

the distributed keyword is required. uses Auto RP for a simple yet scalable way to provide a highly resilient RP environment. This provides optimal resiliency: snmp-server trap-source Loopback0 ip ssh source-interface Loopback0 ip pim register-source Loopback0 ip tacacs source-interface Loopback0 ntp source Loopback0 Step 12:  Configure IP unicast routing authentication key to be used for EIGRP neighbor authentication. This design uses a best practice of assigning the router ID to a loopback address. Using IP Multicast is much more efficient than using multiple individual unicast streams or a broadcast stream that would propagate everywhere.255 eigrp router-id 10.32.0 0.Step 11:  Bind the device processes for SNMP. ip multicast-routing distributed Deploying an MPLS WAN August 2014 Series 29 . Enable IP Multicast routing on the platforms in the global configuration mode. PIM.0. The network range must include both interface IP addresses. the port-channel interface and the loopback must be EIGRP interfaces.255.1. EIGRP is configured facing the LAN distribution or core layer. TACACS+ and NTP to the loopback interface address. ip multicast-routing If you are using a Cisco ASR 1000 Series router. This design. IP Multicast allows a single IP data stream to be replicated by the infrastructure (routers and switches) and sent from a single source to multiple receivers. In this design. end hosts must join a multicast group by sending an IGMP message to their local multicast router.4. In order to receive a particular IP Multicast data stream. key chain LAN-KEY key 1 key-string cisco Step 13:  Configure IP unicast routing using EIGRP named mode. either in a single network statement or in multiple network statements. The loopback may remain a passive interface.241 nsf exit-address-family Step 14:  Configure IP Multicast routing.4. SSH. router eigrp LAN address-family ipv4 unicast autonomous-system 100 af-interface default passive-interface exit-af-interface network 10. the local router consults another router in the network that is acting as an RP to map the receivers to active sources so they can join their streams. which is based on sparse mode multicast operation. IP Telephony MOH and IP Video Broadcast Streaming are two examples of IP Multicast applications. In a traditional IP Multicast design.

router eigrp LAN address-family ipv4 unicast autonomous-system 100 af-interface Port-channel1 no passive-interface authentication mode md5 authentication key-chain LAN-KEY exit-af-interface exit-address-family Deploying an MPLS WAN August 2014 Series 30 . Use the ip pim autorp listener command to allow for discovery across sparse mode links. so you configure EtherChannel statically. In this step. interface GigabitEthernet0/0/0 description WAN-D3750X Gig1/0/1 ! interface GigabitEthernet0/0/1 description WAN-D3750X Gig2/0/1 ! interface range GigabitEthernet0/0/0.Step 15:  Configure every Layer 3 switch and router to discover the IP Multicast RP with autorp.252 ip pim sparse-mode no shutdown Step 2:  Configure EtherChannel member interfaces. ip pim autorp listener Step 16:  Enable sparse mode multicast operation for all Layer 3 interfaces in the network.32. GigabitEthernet0/0/1 no ip address channel-group 1 no shutdown Step 3:  Configure the EIGRP interface. Not all router platforms can support LACP to negotiate with the switch. This configuration provides for future scaling and control of the IP Multicast environment and can change based on network needs and design. configure EIGRP authentication by using the authentication key specified in the previous procedure. Allow EIGRP to form neighbor relationships across the interface to establish peering adjacencies and exchange route tables. interface Port-channel1 description WAN-D3750X ip address 10.255.255.4. ip pim sparse-mode Procedure 3 Configure connectivity to the LAN Any links to adjacent distribution layers should be Layer 3 links or Layer 3 EtherChannels.2 255. Step 1:  Configure Layer 3 interface. Configure the physical interfaces to tie to the logical port-channel by using the channel-group command. The number for the port-channel and channel-group must match.

255. Typically a pointto-point netmask of 255. if you are using a subrate service. use the policed rate from the carrier. then use the BGP option. The IP addressing used between CE and PE routers must be negotiated with your MPLS carrier. The example shows a Gigabit interface (1000 Mbps) with a subrate of 300 Mbps.Procedure 4 Connect to MPLS PE router Step 1:  Assign the interface bandwidth.3.255.168. If your remote-site design only uses single WAN links and you don’t anticipate adding or modifying IP networks at the remote sites. Deploying an MPLS WAN August 2014 Series 31 .255. The MPLS carrier is responsible for configuring static IP routing within the MPLS network. This is the recommended approach. then you can use the statically routed option. The bandwidth value should correspond to the actual interface speed. We do not recommend the use of CDP on external interfaces. interface GigabitEthernet0/0/3 no cdp enable no shutdown Procedure 5 Redistribute WAN routes into EIGRP The WAN-aggregation CE routers are configured either for dynamic routing with BGP or are statically routed.252 is used. interface GigabitEthernet0/0/3 description MPLS PE Router bandwidth 300000 Tech Tip Command reference: bandwidth kbps (300 Mbps = 300.000 kbps) Step 2:  Assign the IP address and netmask of the WAN interface.255. Or.1 255. interface GigabitEthernet0/0/3 ip address 192. or do not wish to have your MPLS carrier make changes or modifications. If you have a remote-site design that includes sites with dual WAN links.252 Step 3:  Administratively enable the interface and disable CDP.

Proper route control ensures the stability of the routing table. router eigrp LAN address-family ipv4 unicast autonomous-system 100 topology base default-metric 300000 100 255 1 1500 redistribute bgp 65511 exit-af-topology exit-address-family Step 2:  Configure route-map and inbound distribute-list for EIGRP.Tech Tip If you do not use dynamic routing with BGP. It is important to tightly control how routing information is shared between different routing protocols when you use this configuration. Deploying an MPLS WAN August 2014 Series 32 . A default metric redistributes the BGP routes into EIGRP. you may need to block more tags. The WAN-aggregation MPLS CE routers are configured to only accept routes that do not originate from the MPLS or DMVPN WAN sources. you must create a route-map that matches any routes originating from the WAN indicated by a specific route tag. then the MPLS carrier must configure a set of static routes on its PE routers for the WAN-aggregation site and for each of the remote sites. This design uses mutual route redistribution: BGP routes are distributed into EIGRP and EIGRP routes are distributed into BGP (covered in Procedure 6).Route tag information for WAN-aggregation MPLS CE routers Tag Route source Tag method action 65401 MPLS VPN A implicit block 65402 MPLS VPN B implicit block 300 Layer 2 WAN explicit accept 65512 DMVPN hub routers explicit block This example includes all WAN route sources in the reference design. This method allows for dynamic identification of the various WAN routes. only the bandwidth and delay values are used for metric calculation. Table 10 . Option 1: BGP dynamic routing with MPLS carrier Step 1:  Redistribute BGP into EIGRP. By default. Site-specific routing details must be shared with your MPLS carrier. you might experience route flapping. To accomplish this task. otherwise. Depending on the actual design of your network. BGP-learned routes are implicitly tagged with their respective source AS and other WAN routes are explicitly tagged by their WAN-aggregation router (documented in a separate procedure). The specific route tags in use are shown below. where certain routes are repeatedly installed and withdrawn from the device routing tables. An inbound distribute-list with a route-map is used to limit which routes are accepted for installation into the route table.

router eigrp LAN address-family ipv4 unicast autonomous-system 100 topology base default-metric 300000 100 255 1 1500 redistribute static exit-af-topology exit-address-family Deploying an MPLS WAN August 2014 Series 33 . tagging. and filtering.5.0.255. which can cause instability.168.0 192.0. It is a best practice to summarize the remote-site network ranges into a single route when possible.168. A single summary route for the loopback range may be used when possible. ip route 192. so you can use this to determine router reachability.250. route-flapping may occur.It is important when creating the route-map that you include a permit statement at the end in order to permit the installation of routes with non-matching tags.0 192.2 Step 4:  Configure EIGRP to advertise the remote-site static routes. route-map BLOCK-TAGGED-ROUTES deny 10 match tag 65401 65402 65512 ! route-map BLOCK-TAGGED-ROUTES permit 20 ! router eigrp LAN address-family ipv4 unicast autonomous-system 100 topology base distribute-list route-map BLOCK-TAGGED-ROUTES in exit-af-topology exit-address-family Option 2: Static routing with service provider Step 1:  Configure static routes to remote sites’ LANs on the WAN-aggregation CE router. which includes the CE routers’ WAN interfaces. A default metric redistributes these routes into EIGRP.255. only the bandwidth and delay values are used for metric calculation.5. Tech Tip If you configure mutual route redistribution without proper matching. for troubleshooting.168.5. ip route 10.168. By default.2 Step 3:  Configure routes to the remote-site router loopback addresses. ip route 10.255.255.255.255.0 192.2 Step 2:  It is desirable to advertise a route for the MPLS PE-CE links.5.0 255.0 255. It is a best practice to summarize the PE-CE link ranges into a single route when possible.0 255.5.

This design uses iBGP peering using device loopback addresses. It is most efficient if you summarize these routes before they are advertised to the CE router.242 remote-as 65511 neighbor 10.32.4.0 redistribute eigrp 100 Step 4:  If you have dual MPLS carriers. Because BGP does not propagate a default route via redistribution. The private ASN range is 64512 to 65534. All EIGRP routes learned by the CE router. You can use this to determine router reachability. complete this procedure. but you may be permitted to use a private ASN as designated by IANA. router bgp 65511 no synchronization bgp router-id 10.32. You can consult with your MPLS carrier on the requirements for the ASN.2 remote-as 65401 Step 3:  Redistribute EIGRP into BGP. this configuration is considered an internal BGP (iBGP) connection.255. you must use a BGP ASN.32. You must configure BGP with the MPLS carrier PE device. router bgp 65511 network 0.0 in a network statement. should be advertised into the WAN. The MPLS carrier must provide their ASN (the ASN in the previous step is the ASN identifying your site). router bgp 65511 neighbor 10.252 neighbor 192.0 mask 255.3.0. including routes from the core and for other WAN sites.168. Because the carrier PE router uses a different ASN. which requires the update-source and next-hop-self-configuration options. Step 1:  Enable BGP.255. Because the CE routers are using the same ASN. router bgp 65511 network 192.168.242 next-hop-self Deploying an MPLS WAN August 2014 Series 34 .Procedure 6 Configure BGP If you are using BGP dynamic routing with the MPLS carrier.4.4.3. • The route is redistributed into BGP.0.4. It is desirable to advertise a route for the PE-CE link.242 update-source Loopback0 neighbor 10.0.241 bgp log-neighbor-changes no auto-summary Step 2:  Configure eBGP. for troubleshooting.0. configure a BGP link between the CE routers. so you should include this network in a network statement.32. you must explicitly specify 0. this configuration is considered an external BGP (eBGP) connection. To complete this step. The CE router advertises only network routes to the PE via BGP when: • The route is specified in network statements and is present in the local routing table.

Configure the transit network 9. Configure BGP 11. Connect to the MPLS PE router PROCESS 3.Configuring the Remote-Site MPLS CE Router 1. Enable enhanced object tracking Use this process for the configuration of any of the following: • MPLS CE router for an MPLS WAN remote site (single router. Configure remote-site DHCP 7. dual-link design. Configure access-layer HSRP 8. Configure EIGRP (LAN side) 10. Deploying an MPLS WAN August 2014 Series 35 . Configure access-layer routing 6. Configure WAN routing 4. dual-link design or for configuring the first router of the dual-router. single link) • MPLS WAN Dual Carrier remote site Use the following procedures when performing the initial configuration of a dual-connected MPLS CE in the single-router. Connect router to access-layer switch 5. Configure the WAN remote router 2.

Connect to Distribution Layer 2. Configure Transit Network Router 4. Configure BGP for Dual Router August 2014 Series 36 . Connect to MPLS PE Router 3.Remote-site MPLS CE router configuration flowchart Remote-Site MPLS CE Router Single Router. Configure Transit Network 3 8. Configure Access Layer HSRP 3. Enable ble Enhanced O bject Tra acking Object Tracking MPLS CE Spoke Router Configuration Complete Deploying an MPLS WAN e Second Configure Remote-Site Router MPLS CE Router Configuration Complete Configure Second C Remote-Site Router 2129 uter 10. Configure EIGRP (LAN Side) Dual Router Design? NO YES Dual Router Design? 5. Connect nnect Router to Access Layer Switch Remote-Site Router to Distribution Layer Procedures 1. Configure the WAN Remote Router 2. Configure WAN Routing Distribution Layer Design? NO YES 4. Dual Link 1. Configure EIGRP (LAN Side)) 11.The following flowchart provides details about the configuration process for a remote-site MPLS CE router. Configure Access Layer Routing 6. Figure 14 . Single Link Remote-Site MPLS CE Router Configuration Procedures Remote-Site MPLS CE Router Dual Router. Configure Remote-Site DHCP (Optional) YES NO RP 7. Configure BGP for Dual Rout 9. Dual Link (1st Router) Remote-Site MPLS CE Router Single Router.

Step 4:  (Optional) Configure centralized user authentication. They use Secure Sockets Layer (SSL) and Transport Layer Security (TLS) to provide device authentication and data encryption. TACACS+ is the primary protocol used to authenticate management logins on the infrastructure devices to the AAA server.15 key SecretKey ! aaa group server tacacs+ TACACS-SERVERS server name TACACS-SERVER-1 ! aaa authentication login default group TACACS-SERVERS local aaa authorization exec default group TACACS-SERVERS local aaa authorization console ip http authentication aaa Step 5:  Configure device management protocols. When AAA is enabled for access control. you prevent the disclosure of plain text passwords when viewing configuration files. Both protocols are encrypted for privacy and the unsecure protocols. A local AAA user database is also defined in Step 2 on each network infrastructure device in order to provide a fallback authentication source in case the centralized TACACS+ server is unavailable. As networks scale in the number of devices to maintain. A centralized authentication. The local login account and password provides basic access authentication to a router that provides only limited operational privileges.Procedure 1 Configure the WAN remote router Within this design.48. https access to the router uses the enable password for authentication. there are features and services that are common across all WAN remote-site routers. authorization. Telnet and HTTP. Secure management of the network device is enabled through the use of the SSH and HTTPS protocols. Secure Copy Deploying an MPLS WAN August 2014 Series 37 . Secure HTTP (HTTPS) and Secure Shell (SSH) are secure replacements for the HTTP and Telnet protocols. The enable password secures access to the device configuration mode. and accounting (AAA) service reduces operational tasks per device and provides an audit log of user access for security compliance and root cause analysis. By enabling password encryption. it can be an operational burden to maintain local user accounts on every device. Step 1:  Configure the device host name to make it easy to identify the device. username admin password c1sco123 enable secret c1sco123 service password-encryption aaa new-model Step 3:  By default. These are system settings that simplify and secure the management of the solution. hostname [hostname] Step 2:  Configure the local login and password. all management access to the network infrastructure devices (SSH and HTTPS) is controlled by AAA. are turned off.4. tacacs server TACACS-SERVER-1 address ipv4 10.

snmp-server community cisco RO snmp-server community cisco123 RW Step 8:  If your network operational support is centralized. if the ip name-server is unreachable. console log messages are displayed on the console after interactive CLI output is displayed or printed. line con 0 transport preferred none logging synchronous Step 7:  Enable Simple Network Management Protocol (SNMP). access-list 55 permit 10.4. Without this command. which allows the use of code upgrades using Prime Infrastructure via SSH-based SCP protocol. With this command.0. The Network Time Protocol (NTP) is designed to synchronize a network of devices. you can increase network security by using an access list to limit the networks that can access your device.48. you can continue typing at the device console when debugging is enabled.0/24 network will be able to access the device via SSH or SNMP. long timeout delays may occur for mistyped commands. Specify the transport preferred none on vty lines to prevent errant connection attempts from the CLI prompt. In this example.Protocol is enabled. An NTP network usually gets its time from an authoritative time source. Step 9:  Configure a synchronized clock. Configure SNMPv2c both for a read-only and a readwrite community string. This allows the network infrastructure devices to be managed by a Network Management System (NMS). When synchronous logging of unsolicited messages and debug output is turned on.local ip ssh version 2 no ip http server ip http secure-server ip scp server enable line vty 0 15 transport input ssh transport preferred none Step 6:  Enable synchronous logging. such as a radio clock or an atomic clock attached to a time server.0 0.4.0. only devices on the 10.48. Deploying an MPLS WAN August 2014 Series 38 . ip domain-name cisco.255 line vty 0 15 access-class 55 in ! snmp-server community cisco RO 55 snmp-server community cisco123 RW 55 Tech Tip If you configure an access-list on the vty interface you may lose the ability to use ssh to log in from one router to the next for hop-by-hop troubleshooting.

IP Telephony MOH and IP Video Broadcast Streaming are two examples of IP Multicast applications. Using IP Multicast is much more efficient than multiple individual unicast streams or a Broadcast stream that would propagate everywhere. and debug output to provide time stamps on output. the loopback address is the best way to manage the router in-band. By configuring console messages. Because of this capability. you can cross-reference events in a network. interface Loopback 0 ip address [ip address] 255. which is based on sparse mode multicast operation. SSH.255. Allocate the loopback address from a unique network range that is not part of any other internal network summary range. In a traditional IP Multicast design.48.NTP then distributes this time across the organization’s network.4. PIM. In this design. IP Multicast allows a single IP data stream to be replicated by the infrastructure (routers and switches) and sent from a single source to multiple receivers. Auto RP is used to provide a simple yet scalable way to provide a highly resilient RP environment. The local NTP server typically references a more accurate clock feed from an outside source. The loopback address is commonly a host address with a 32-bit address mask.255. logs. TACACS+ and NTP to the loopback interface address for optimal resiliency: snmp-server trap-source Loopback0 ip ssh source-interface Loopback0 ip pim register-source Loopback0 ip tacacs source-interface Loopback0 ntp source Loopback0 Step 12:  Configure IP Multicast routing.255 ip pim sparse-mode Step 11:  Bind the device processes for SNMP. end hosts must join a multicast group by sending an IGMP message to their local multicast router. To receive a particular IP Multicast data stream. You should program network devices to synchronize to a local NTP server in the network. ntp server 10. Layer 3 process and features are also bound to the loopback interface to ensure process resiliency. Enable IP Multicast routing on the platforms in the global configuration mode. ip multicast-routing Deploying an MPLS WAN August 2014 Series 39 . the local router consults another router in the network that is acting as an RP to map the receivers to active sources so they can join their streams. The loopback interface is a logical interface that is always reachable as long as the device is powered on and any IP interface is reachable to the network.17 ntp update-calendar ! clock timezone PST -8 clock summer-time PDT recurring ! service timestamps debug datetime msec localtime service timestamps log datetime msec localtime Step 10:  Configure an in-band management interface.

Use the ip pim autorp listener command to allow for discovery across sparse mode links. interface [interface type] [number] no cdp enable no shutdown Example interface GigabitEthernet0/0 bandwidth 10000 ip address 192. you should use the policed rate from the carrier. you’d use a point-to-point netmask of 255.255. The IP addressing used between CE and PE routers must be negotiated with your MPLS carrier.252 no cdp enable no shutdown Deploying an MPLS WAN August 2014 Series 40 .255.255. The use of CDP on external interfaces is not recommended. The example shows a Gigabit interface (1000 Mbps) with a subrate of 10 Mbps. interface [interface type] [number] ip address [IP address] [netmask] Step 3:  Administratively enable the interface and disable CDP. ip pim sparse-mode Procedure 2 Connect to the MPLS PE router Step 1:  Assign the interface bandwidth. The bandwidth value should correspond to the actual interface speed. Typically.3. if you are using a subrate service.9 255. Or.252.168. interface [interface type] [number] bandwidth [bandwidth (kbps)] Tech Tip Command Reference: bandwidth kbps 10 Mbps = 10.255.Step 13:  Configure every Layer 3 switch and router to discover the IP Multicast RP with autorp.000 kbps Step 2:  Assign the IP address and netmask of the WAN interface. ip pim autorp listener Step 14:  Enable sparse mode multicast operation for all Layer 3 interfaces in the network. This configuration provides for future scaling and control of the IP Multicast environment and can change based on network needs and design.

If your remote-site design only uses single WAN links and you don’t anticipate adding or modifying IP networks at the remote site. so you should include this network in a network statement. The MPLS carrier must provide their ASN (the ASN in the previous step is the ASN identifying your site). you must configure BGP to advertise the loopback network for the router. Similarly. You can use this to determine router reachability. Because the carrier PE router uses a different ASN. You might be able to reuse the same value used on the MPLS VPN CE from the WAN-aggregation site. Deploying an MPLS WAN August 2014 Series 41 . a BGP ASN is required. then the MPLS carrier must configure a set of static routes on its PE routers for the WAN-aggregation site and for each of the remote sites. Consult with your MPLS carrier on the requirements for the ASN. Site-specific routing details must be shared with your MPLS carrier. Configure BGP with the MPLS carrier PE device.Procedure 3 Configure WAN routing The remote-site CE routers are configured either for dynamic routing with BGP or are statically routed. then you can use the statically routed option. To complete this step. for troubleshooting. The CE router advertises only network routes to the PE via BGP in the following cases: • The route is specified in network statements and is present in the local routing table. use the BGP option. and assumes that the WAN-aggregation CE router has already been configured for BGP. Option 1: BGP dynamic routing with MPLS carrier Step 1:  Enable BGP. If you have a remote-site design that includes sites with dual WAN links or you do not want to have your MPLS carrier make changes or modifications. The MPLS carrier is responsible for configuring static IP routing within the MPLS network. router bgp 65511 no synchronization bgp router-id [IP address of Loopback0] bgp log-neighbor-changes no auto-summary Step 2:  Configure eBGP. this configuration is considered an external BGP (eBGP) connection. This is the recommended approach. Tech Tip If you do not use dynamic routing with BGP. It is desirable to advertise a route for the PE-CE link. • The route is redistributed into BGP (not applicable in the remote-site use case).

255.255 network [DATA network] mask [netmask] network [VOICE network] mask [netmask] aggregate-address [summary IP address] [summary netmask] summary-only neighbor [IP address of PE] remote-as [carrier ASN] Example router bgp 65511 no synchronization bgp router-id 10.0 summary-only neighbor 192.206 mask 255.8.255.5.0 aggregate-address 10.255.255.248.255.255.255. provide the remote-site specific IP range and the chosen loopback IP address for the router.0 255.251.168.206 bgp log-neighbor-changes network 192.0 0. you must list each individually.255. router bgp 65511 network [PE-CE link network] mask [PE-CE link netmask] network [Loopback network] mask 255.0 mask 255.168. The aggregate address configured below suppresses the more specific routes.255.0 192.168.255.255.255 network 10.3. the aggregate is advertised to the MPLS PE. which offers a measure of resiliency.3.8 mask 255.0.5. the WAN-aggregation CE router must have a corresponding static host route for that site’s loopback address. The IP assignment for the remote sites was designed so that all of the networks in use can be summarized within a single aggregate route. You must add a separate network statement for the loopback address.0.252 network 10.0.255.0 network 10.255. If the various LAN networks cannot be summarized. Step 1:  Enter a default route for traffic forwarded to the WAN-aggregation site.10 Step 2:  For the MPLS carrier for each remote site. Tech Tip For each remote site with static routing.10 remote-as 65401 no auto-summary Option 2: Static routing with service provider This option has remote sites using static routing to the MPLS WAN to forward all traffic to the WAN-aggregation site.13. If any LAN network is present in the route table.251.12.3. This properly configures the static routes to the remote site.5.0 mask 255.You must advertise the remote-site LAN networks. ip route 0. Deploying an MPLS WAN August 2014 Series 42 .0.

skip to the “Deploying a WAN Remote-Site Distribution Layer” chapter of this guide. see the Campus Wired LAN Technology Design Guide. If you are using a remote-site distribution layer.1Q trunk interfaces to the LAN access layer.Procedure 4 Connect router to access-layer switch Reader Tip This guide includes only the additional steps to complete the distribution-layer configuration. Not all router platforms can support LACP to negotiate with the switch. or in the case of the Cisco Catalyst 4507R+E distribution layer. The VLAN numbering is locally significant only. so you configure EtherChannel statically. the remote sites use collapsed routing. If your access-layer device is a single. The physical interfaces that are members of a Layer 2 EtherChannel are configured prior to configuring the logical port-channel interface. The number for the port-channel and channel-group must match. a simple Layer 2 trunk between the router and switch is used. Layer 2 EtherChannels are used to interconnect the CE router to the access layer in the most resilient method possible. interface GigabitEthernet0/1 description RS206-A2960X Gig1/0/24 ! interface GigabitEthernet0/2 description RS206-A2960X Gig2/0/24 ! interface range GigabitEthernet0/1. interface Port-channel1 description EtherChannel link to RS206-A2960X no shutdown Step 2:  Configure EtherChannel member interfaces on the router. fixed-configuration switch. In the access-layer design. Deploying an MPLS WAN August 2014 Series 43 . Doing the configuration in this order allows for minimal configuration and reduces errors because most of the commands entered to a port-channel interface are copied to its members’ interfaces and do not require manual replication. Connect the router EtherChannel uplinks to separate switches in the access layer switch stack. to separate redundant modules for additional resiliency. GigabitEthernet0/2 no ip address channel-group 1 no shutdown Step 3:  Configure EtherChannel member interfaces on the access-layer switch. Configure the physical interfaces to tie to the logical port-channel by using the channel-group command. with 802. Option 1: Layer 2 EtherChannel from router to access-layer switch Step 1:  Configure port-channel interface on the router. For complete access-layer configuration details.

interface GigabitEthernet1/0/24 description Link to RS206-3925-1 Gig0/1 interface GigabitEthernet2/0/24 description Link to RS206-3925-1 Gig0/2 ! interface range GigabitEthernet1/0/24. and the number must match the channel group configured in Step 3.69. so you configure EtherChannel statically. When using EtherChannel.Configure two physical interfaces to be members of the EtherChannel. GigabitEthernet2/0/24 switchport channel-group 1 mode on logging event link-status logging event trunk-status logging event bundle-status load-interval 30 macro apply EgressQoS Step 4:  Configure EtherChannel trunk on the access-layer switch.99 switchport mode trunk ip arp inspection trust spanning-tree portfast trunk logging event link-status logging event trunk-status ip dhcp snooping trust no shutdown load-interval 30 The Cisco Catalyst 3750 Series Switch requires the switchport trunk encapsulation dot1q command. Not all connected router platforms can support LACP to negotiate with the switch. Prune the VLANs allowed on the trunk to only the VLANs that are active on the access-layer switch. Use an 802. interface Port-channel1 description EtherChannel link to RS206-3925-1 switchport trunk allowed vlan 64. Also. interface GigabitEthernet0/2 description RS202-A3560X Gig1/0/24 no ip address no shutdown Deploying an MPLS WAN August 2014 Series 44 . Option 2: Layer 2 trunk from router to access-layer switch Step 1:  Enable the physical interface on the router.1Q trunk for the connection. the interface type is port-channel. Set DHCP Snooping and Address Resolution Protocol (ARP) inspection to trust. which allows the router to provide the Layer 3 services to all the VLANs defined on the access-layer switch. apply the egress QoS macro that was defined in the LAN switch platform configuration procedure to ensure traffic is prioritized appropriately.

Prune the VLANs allowed on the trunk to only the VLANs that are active on the access-layer switch.1 255.48. After you have enabled the physical interface or port-channel. When using a centralized DHCP server. Procedure 5 Configure access-layer routing Option 1: Layer 2 EtherChannel or Layer 2 trunk Step 1:  Create subinterfaces and assign VLAN tags. but making them the same simplifies the overall configuration. This requires a modified IP configuration on each subinterface. you can map the appropriate data or voice subinterfaces to the VLANs on the LAN switch. This design uses an IP addressing convention with the default gateway router assigned an IP address and IP mask combination of N. The subinterface number does not need to equate to the 802.255.4.10 ip pim sparse-mode Deploying an MPLS WAN August 2014 Series 45 . which allows the router to provide the Layer 3 services to all the VLANs defined on the access-layer switch. routers with LAN interfaces connected to a LAN using DHCP for endstation IP addressing must use an IP helper. This is the preferred method. Use an 802.0 where N.69 switchport mode trunk ip arp inspection trust spanning-tree portfast trunk logging event link-status logging event trunk-status ip dhcp snooping trust no shutdown load-interval 30 macro apply EgressQoS The Cisco Catalyst 3750 Series Switch requires the switchport trunk encapsulation dot1q command. interface GigabitEthernet1/0/24 description Link to RS201-2911 Gig0/2 switchport trunk allowed vlan 64. Set DHCP Snooping and Address Resolution Protocol (ARP) inspection to trust. interface [type][number].N. If the remote-site router is the first router of a dual-router design.[sub-interface number] encapsulation dot1Q [dot1q VLAN tag] Step 2:  Configure IP settings for each subinterface.[sub-interface number] description [usage] ip address [LAN network 1] [LAN network 1 netmask] ip helper-address 10.255.Step 2:  Configure the trunk on the access-layer switch.N.1Q trunk for the connection. then HSRP is configured at the access layer.N is the IP network and 1 is the IP host. interface [type][number]. An alternate option for local DHCP server configuration is shown in the following procedure. The subinterface portion of the configuration should be repeated for all data or voice VLANs.1Q tag.N.

4.Example interface GigabitEthernet0/2.1 domain-name cisco. excluding DHCP assignment for the first 19 addresses in the subnet. such as a centralized DHCP server.local dns-server 10. excluding DHCP assignment for the first 19 addresses in the subnet. and other endpoint devices.255.255.64 description Wired Data encapsulation dot1Q 64 ip address 10.4.255.255. users’ laptop and desktop computers.5. This procedure uses a local DHCP service on the router in order to assign basic network configuration for IP phones.0 default-router 10. complete this procedure.5.48.4.4.1 255.4.0 ip helper-address 10.10 Step 3:  Configure a DHCP scope for voice endpoints.5.19 ip dhcp pool DHCP-Wired-Data network 10.48. ip dhcp excluded-address 10. Step 1:  Remove the previously configured ip helper-address commands for any interface that uses a local DHCP server.1 10. Options for resilient DHCP at the remotesite include using IOS on a distribution-layer switch stack or implementing a dedicated DHCP server solution. Deploying an MPLS WAN August 2014 Series 46 .11. you should use a resilient DHCP solution.5.68. Step 2:  Configure a DHCP scope for data endpoints.4.0 255. Tech Tip If you intend to use a dual-router remote-site design. If you choose to run a local DHCP server on the remote-site router instead of centralizing the DHCP service. wireless access points.10 ip pim sparse-mode Procedure 6 Configure remote-site DHCP (Optional) The previous procedure assumes the DHCP service has been configured centrally and uses the ip helperaddress command to forward DHCP requests to the centralized DHCP server.

19 ip dhcp pool DHCP-Wired-Voice network 10.5. The HSRP active router is the MPLS CE router connected to the primary MPLS carrier. Tech Tip The HSRP priority and PIM DR priority are shown in the previous table to be the same value. ip dhcp excluded-address 10.11. The dual-router access-layer design requires a modification for resilient multicast. The PIM designated router (DR) should be on the HSRP active router.2 110 110 MPLS CE (secondary) or DMVPN spoke Standby . The relevant HSRP parameters for the router configuration are shown in the following table. Table 11 . The router with the higher standby priority value is elected as the HSRP active router.4.3 105 105 The assigned IP addresses override those configured in the previous procedure. so the number may vary based on the voice product you choose (for example.5.5.255. and it has no awareness of the HSRP configuration.48.0 255. without waiting for a scenario where there is no router in the HSRP active state.local dns-server 10.5. however.Step 4:  Voice endpoints require an option field to tell them where to find their initial configuration. You can influence the PIM DR election by explicitly setting the DR priority on the LAN-facing subinterfaces for the routers. In this procedure. you are not required to use identical values. you configure the HSRP active router with a standby priority that is higher than the HSRP standby router. so the default gateway IP address remains consistent across locations with single or dual routers.255. and the HSRP standby router is the router connected to the secondary MPLS carrier or backup link. The DR is normally elected based on the highest IP address.1 domain-name cisco.0 default-router 10.5.5.1 10. In this design. complete this procedure.10 Procedure 7 through Procedure 11 are only relevant for the dual-router design. Deploying an MPLS WAN August 2014 Series 47 .1 .WAN remote-site HSRP parameters (dual-router design) Router HSRP role Virtual IP address (VIP) Real IP address HSRP priority PIM DR priority MPLS CE (primary) Active . Cisco uses DHCP option 150).1 . Procedure 7 Configure access-layer HSRP If you are using a dual-router design. Different vendors use different option fields. The preempt option allows a router with a higher priority to become the HSRP active. assigning the HSRP active router a lower real IP address than the HSRP standby router requires a modification to the PIM configuration. You need to configure HSRP in order to enable the use of a virtual IP (VIP) address as a default gateway that is shared between two routers.5.

48. Example: Layer 2 link interface GigabitEthernet0/2 no ip address no shutdown ! interface GigabitEthernet0/2.5.Step 1:  Configure HSRP.0 ip helper-address 10.13.2 255.10 ip pim dr-priority 110 ip pim sparse-mode standby version 2 standby 1 ip 10.69 description Voice encapsulation dot1Q 69 ip address 10.10 ip pim dr-priority 110 ip pim sparse-mode standby version 2 standby 1 ip 10.1 standby 1 priority 110 standby 1 preempt standby 1 authentication md5 key-string c1sco123 Deploying an MPLS WAN August 2014 Series 48 .64 description Data encapsulation dot1Q 64 ip address 10.255.255.1 standby 1 priority 110 standby 1 preempt standby 1 authentication md5 key-string c1sco123 ! interface GigabitEthernet0/2.5.4.13.[sub-interface number] ip address [LAN network 1 address] [LAN network 1 netmask] ip pim dr-priority 110 standby version 2 standby 1 ip [LAN network 1 gateway address] standby 1 priority 110 standby 1 preempt standby 1 authentication md5 key-string c1sco123 Step 2:  Repeat this procedure for all data or voice subinterfaces. interface [type][number].12.2 255.4.12.5.0 ip helper-address 10.5.255.48.255.

Procedure 8 Configure the transit network If you are using a dual-router design. add the transit network VLAN. configure the transit network interface.8.1 255. interface GigabitEthernet1/0/24 switchport trunk allowed vlan add 99 Procedure 9 Configure EIGRP (LAN side) If you are using a dual-router design.255. interface [type][number].99 description Transit Net encapsulation dot1Q 99 ip address 10. so HSRP and DHCP are not required.5. This ensures that the HSRP active router has full reachability information for all WAN remote sites. complete this procedure. The transit network is configured between the two routers.255. Step 1:  On the primary MPLS CE router. All interfaces except the transit-network subinterface should remain passive. This network is used for router-router communication and to avoid hairpinning. configure the EIGRP LAN process facing the access layer. router eigrp LAN address-family ipv4 unicast autonomous-system 100 af-interface default passive-interface Deploying an MPLS WAN August 2014 Series 49 . This design uses a best practice of assigning the router ID to a loopback address. There are no end stations connected to this network.252 ip pim sparse-mode Step 2:  On the access-layer switch. Do not include the WAN interface (MPLS PE-CE link interface) as an EIGRP interface. Step 1:  On the router. The network range must include all interface IP addresses either in a single network statement or in multiple network statements. all LAN-facing interfaces and the loopback must be EIGRP interfaces. You must configure a routing protocol between the two routers. In this design. The transit network should use an additional subinterface on the router interface that is already being used for data or voice. complete this procedure.[sub-interface number] encapsulation dot1Q [dot1q VLAN tag] ip address [transit net address] [transit net netmask] ip pim sparse-mode Example interface GigabitEthernet0/2. vlan 99 name Transit-net Step 3:  Add the transit network VLAN to the existing access-layer switch trunk.

A default metric redistributes the BGP routes into EIGRP. key chain LAN-KEY key 1 key-string cisco ! router eigrp LAN address-family ipv4 unicast autonomous-system 100 af-interface [interface type] [number] authentication mode md5 authentication key-chain LAN-KEY no passive-interface exit-af-interface exit-address-family Step 3:  On the router. only the WAN bandwidth and delay values are used for metric calculation. Deploying an MPLS WAN August 2014 Series 50 .exit-af-interface af-interface [Transit link interface] no passive-interface exit-af-interface network [network] [inverse mask] eigrp router-id [IP address of Loopback0] exit-address-family Step 2:  Configure EIGRP neighbor authentication. By default. router eigrp LAN address-family ipv4 unicast autonomous-system 100 topology base default-metric [WAN bandwidth] [WAN delay] 255 1 1500 redistribute bgp 65511 exit-af-topology exit-address-family Tech Tip Command Reference: default-metric bandwidth delay reliability loading mtu bandwidth—Minimum bandwidth of the route in kilobytes per second delay—Route delay in tens of microseconds. Neighbor authentication enables the secure establishment of peering adjacencies and exchange route tables over the DMVPN tunnel interface. redistribute BGP into the EIGRP LAN process.

By default. In the dual-MPLS design. it is a best practice to disable the site from becoming a transit site. providing access between the two carriers.255.99 authentication mode md5 authentication key-chain LAN-KEY no passive-interface exit-af-interface topology base default-metric 100000 100 255 1 1500 redistribute bgp 65511 exit-af-topology network 10.0 0. which requires the next-hop-self-configuration option. The dual-carrier MPLS design requires that a BGP link is configured between the CE routers. Step 1:  On both remote-site MPLS CE routers.251.0. router bgp 65511 neighbor [iBGP neighbor Transit Net IP] remote-as 65511 neighbor [iBGP neighbor Transit Net IP] next-hop-self Step 2:  Configure BGP to prevent the remote site from becoming a transit AS. You must use a route-map and an as-path access-list filter.255 eigrp router-id 10. complete this procedure. Deploying an MPLS WAN August 2014 Series 51 .0.1.255. This design uses iBGP peering using the transit network. In certain cases. Unless the remote site has been specifically designed for this type of routing behavior. You must complete this step on both remote-site MPLS CE routers. this configuration is considered an internal BGP (iBGP) connection.0 0. remote sites will advertise themselves as a transit autonomous system. this means that MPLS-A routes will be advertised to MPLS-B and vice-versa. You need to apply this route-map on both remote-site MPLS CE routers.255 network 10.0.4. Because the CE routers are using the same ASN.Example router eigrp LAN address-family ipv4 unicast autonomous-system 100 af-interface default passive-interface exit-af-interface af-interface GigabitEthernet0/2.255.255. when a link to a MPLS hub has failed. the iBGP session will not be established until you complete the transit network and EIGRP (LAN-side) steps. with a high bandwidth connection. configure iBGP and enable the next-hop-self configuration option.206 exit-address-family Procedure 10 Configure BGP If you are using a dual-router design. BGP readvertises all BGP-learned routes. Note.

Accomplishing the design goal of deterministic routing and primary/secondary routing behavior necessitates tuning BGP. Step 4:  Add a loopback network for the secondary router. Step 3:  Tune BGP routing to prefer the primary MPLS carrier. In this example.255 Deploying an MPLS WAN August 2014 Series 52 . The MPLS dual-carrier design in many cases provides two equal cost paths.Each router will apply this outbound to the neighbor for its respective MPLS carrier. and it is likely that the first path selected will remain the active path unless the routing protocol detects a failure. This requires the use of a route-map and an as-path access-list filter. router bgp 65511 network [Secondary router loopback network] mask 255. the BGP local preference is 200 for the primary MPLS carrier.255. router bgp 65511 neighbor [IP address of PE] route-map NO-TRANSIT-AS out ip as-path access-list 10 permit ^$ ! route-map NO-TRANSIT-AS permit 10 match as-path 10 Tech Tip The regular expression ^$ corresponds to routes originated from the remote-site. Routes originated from the secondary MPLS carrier continue to use their default local preference of 100. BGP uses a well-known rule set in order to determine the “best path” when the same IP route prefix is reachable via two different paths. router bgp 65511 neighbor [IP address of PE] route-map PREFER-MPLS-A in Apply a route-map inbound to the neighbor for the primary MPLS carrier only. ip as-path access-list 1 permit _65401$ ! route-map PREFER-MPLS-A permit 10 match as-path 1 set local-preference 200 ! route-map PREFER-MPLS-A permit 20 Tech Tip The regular expression _65401$ corresponds to routes originated from the AS 65401 (MPLS-A). This type of filter allows for only the locally originated routes to be advertised.255. This allows BGP to selectively modify the routing information for routes originated from this AS.

This is sub-optimal routing. the HSRP active router would learn an alternate path through the transit network to the HSRP standby router and begin to forward traffic across the alternate path.Procedure 11 Enable enhanced object tracking If you are using a dual-router design. Step 1:  Enable the IP SLA probe.69 standby 1 track 50 decrement 10 ! track 50 ip sla 100 reachability ! ip sla 100 icmp-echo 192.3. the HSRP priority is decremented by the configured priority. The HSRP active router (primary MPLS CE) can use the IP SLA feature to send echo probes to its MPLS PE router. The HSRP active router remains the active router unless the router is reloaded or fails. the destination address is the same as the BGP neighbor address configured in Procedure 3. If you are using the MPLS PE router as the probe destination.168. and you can address it by using EOT. Having the HSRP router remain as the active router can lead to undesired behavior. The object being tracked is the reachability success or failure of the probe. This procedure is valid only on the router connected to the primary transport (MPLS VPN). If the status is down. If the primary MPLS VPN transport were to fail. ip sla 100 icmp-echo [probe destination IP address] source-interface [WAN interface] threshold 1000 timeout 1000 frequency 15 ip sla schedule 100 life forever start-time now Step 2:  Configure EOT based on the IP SLA probe. All data or voice subinterfaces should enable HSRP tracking. and then send standard ICMP echo (ping) probes at 15-second intervals. If the decrease is large enough. If the probe is successful. track 50 ip sla 100 reachability Step 3:  Link HSRP with the tracked object. interface [interface type] [number]. HSRP can monitor the tracked object status. the HSRP standby router preempts. complete this procedure.[sub-interface number] standby 1 track 50 decrement 10 Example interface GigabitEthernet 0/2. the tracked object status is Down. then the router can lower its HSRP priority.64 standby 1 track 50 decrement 10 interface GigabitEthernet 0/2. and if the PE router becomes unreachable. the tracked object status is Up.10 source-interface GigabitEthernet0/0 timeout 1000 Deploying an MPLS WAN August 2014 Series 53 . if it fails. so that the HSRP standby router can preempt and become the HSRP active router. Responses must be received before the timeout of 1000 ms expires.

The following figure provides details on how to add a second MPLS backup link on an existing remote-site MPLS CE router. Configure BGP for Dual-link link Site Complete Deploying an MPLS WAN 2130 NO August 2014 Series 54 .PROCESS threshold 1000 frequency 15 ip sla schedule 100 life forever start-time now Adding a Secondary MPLS Link on an Existing MPLS CE Router 1. Only the additional procedures to add an additional MPLS link to the running MPLS CE router are included here. Figure 15 . Configure BGP for dual-link design This process includes the additional steps necessary to complete the configuration of an MPLS CE router for an MPLS WAN dual-carrier remote site (single-router. The following procedures assume that the configuration of an MPLS CE router for an MPLS WAN remote site (single-router. dual-link).Flowchart for adding an MPLS backup configuration MPLS CE Router Configuration Complete Adding Second MPLS Link on Existing MPLS CE Router Configuration Procedures YES Add MPLS Secondary Link? 1. Connect to MPLS PE router 2. Connect to MPLS PE Router uter 2. single-link) has already been completed and BGP dynamic routing has been configured.

13 255.168.255. The IP addressing used between CE and PE routers must be negotiated with your MPLS carrier. If you are using a subrate service.255.255. use the policed rate from the carrier. interface [interface type] [number] ip address [IP address] [netmask] Step 3:  Administratively enable the interface and disable Cisco Discovery Protocol. interface [interface type] [number] no cdp enable no shutdown Example interface GigabitEthernet0/1 bandwidth 10000 ip address 192.Procedure 1 Connect to MPLS PE router This procedure applies to the interface used to connect the secondary or additional MPLS carrier. Typically.252 is used. Step 1:  Assign an interface bandwidth value that corresponds to the actual interface speed.255.000 kbps Step 2:  Assign the IP address and netmask of the WAN interface.4.252 ip pim sparse-mode no cdp enable no shutdown Deploying an MPLS WAN August 2014 Series 55 . It is not recommended that you use the Cisco Discovery Protocol on external interfaces. a point-to-point netmask of 255. The example shows a Gigabit interface (1000 Mbps) with a subrate of 10 Mbps. interface [interface type] [number] bandwidth [bandwidth (kbps)] Tech Tip Command Reference: bandwidth kbps 10 Mbps = 10.

To do this. this means that MPLS-A routes are advertised to MPLS-B and vice-versa. This type of filter allows for only the locally originated routes to be advertised. Unless the remote site has been specifically designed for this type of routing behavior. it is a best practice to disable the site from becoming a transit site. In certain cases. The remote-site LAN networks are already advertised based on the configuration already completed in the “Configuring the Remote-Site MPLS CE Router” process. This requires the use of a route-map and an as-path access-list filter. so you should include this network in a network statement. By default. The MPLS carrier must provide their ASN (the ASN in this step is the ASN identifying your site). Step 3:  Tune BGP routing to prefer the primary MPLS carrier.Procedure 2 Configure BGP for dual-link design Step 1:  Configure eBGP to add an additional eBGP neighbor and advertise the PE-CE link. you need to use a route-map and an as-path access-list filter. The MPLS dual-carrier design in many cases provides two equal cost paths. Because the carrier PE router uses a different ASN. In the dual-MPLS design. for troubleshooting. BGP must be configured with the MPLS carrier PE device. remote sites will advertise themselves as a transit autonomous system. providing access between the two carriers. and it is likely that the first path selected will remain the active path unless the routing protocol detects a failure. this configuration is considered an external BGP (eBGP) connection. router bgp 65511 neighbor [IP address of PE] route-map PREFER-MPLS-A in Deploying an MPLS WAN August 2014 Series 56 . You can use it to determine router reachability. when a link to a MPLS hub has failed. with a high bandwidth connection. router bgp 65511 network [PE-CE link 2 network] mask [PE-CE link 2 netmask] neighbor [IP address of PE 2] remote-as [carrier ASN] Step 2:  Configure BGP to prevent the remote site from becoming a transit AS. Apply this route-map outbound to the neighbors for both MPLS carriers. Accomplishing the design goal of deterministic routing and primary/secondary routing behavior necessitates tuning BGP. router bgp 65511 neighbor [IP address of PE] route-map NO-TRANSIT-AS out neighbor [IP address of PE 2] route-map NO-TRANSIT-AS out ip as-path access-list 10 permit ^$ ! route-map NO-TRANSIT-AS permit 10 match as-path 10 Tech Tip The regular expression ^$ corresponds to routes originated from the remote-site. BGP uses a well-known rule set in order to determine the “best path” when the same IP route prefix is reachable via two different paths. It is desirable to advertise a route for the PE-CE link. BGP readvertises all BGP-learned routes.

168.4.168. Apply this route-map inbound to the neighbor for the primary MPLS carrier only.168.14 route-map NO-TRANSIT-AS out neighbor 192.4.252 neighbor 192. This allows BGP to selectively modify the routing information for routes originated from this AS.3. ip as-path access-list 1 permit _65401$ ! route-map PREFER-MPLS-A permit 10 match as-path 1 set local-preference 200 ! route-map PREFER-MPLS-A permit 20 Tech Tip The regular expression _65401$ corresponds to routes originated from the AS 65401 (MPLS-A). In this example.14 route-map NO-TRANSIT-AS out ! ip as-path access-list 1 permit _65401$ ip as-path access-list 10 permit ^$ ! route-map NO-TRANSIT-AS permit 10 match as-path 10 ! route-map PREFER-MPLS-A permit 10 match as-path 1 set local-preference 200 ! route-map PREFER-MPLS-A permit 20 Deploying an MPLS WAN August 2014 Series 57 .4.168.255.168. the BGP local preference is 200 for the primary MPLS carrier.14 route-map PREFER-MPLS-A in neighbor 192.Step 4:  Apply a route map inbound to the neighbor for the primary MPLS carrier only.255.12 mask 255. Routes originated from the secondary MPLS carrier continue to use their default local preference of 100.14 remote-as 65402 neighbor 192.3. Example router bgp 65511 network 192.

Configure access-layer HSRP 7. Configure Access Layer HSRP 7.Remote-site MPLS CE router 2 configuration flowchart Remote-Site MPLS CE Router Dual Router. Dual Link (2nd Router) Remote-Site Router (Dual Router . Configure EIGRP (LAN Side) 6. Connect router to access-layer switch 5. Configure access-layer routing 6. Configure WAN Routing NO O Distribution Layer Design? YES Y Remote-Site Router to Distribution Layer (Router 2) ccess Layer Switch 4. Configure Transit Network Site Complete Deploying an MPLS WAN Site Complete 2131 8 gu e EIGRP G ((LAN Side) S de) 8. complete this procedure in order to configure the secondary router in the MPLS WAN remote site. Configure WAN routing 4. dual-link design. Configure EIGRP (LAN side) If you are using a dual-router. Connect to the MPLS PE router 3. Configure the transit network 8.Configuring the Secondary Remote-Site Router PROCESS 1. C Connectt R Router 5.Router 2) Configuration Procedures 1. Configure the WAN Remote Router 2. Co Configure August 2014 Series 58 . Configure Access Layer Routing 2. Connect to MPLS PE Router 3. Figure 16 . Configure the WAN remote router 2. Connect Router to Access 1 t to Distribution Layer 1. The following flowchart provides details about how to configure a secondary remote-site MPLS CE router.

tacacs server TACACS-SERVER-1 address ipv4 10. By enabling password encryption.48. there are features and services that are common across all WAN remote-site routers. Step 1:  Configure the device host name. Step 3:  (Optional) Configure centralized user authentication. A local AAA user database is also defined in Step 2 on each network infrastructure device to provide a fallback authentication source in case the centralized TACACS+ server is unavailable. The enable password secures access to the device configuration mode. and accounting (AAA) service reduces operational tasks per device and provides an audit log of user access for security compliance and root cause analysis. all management access to the network infrastructure devices (SSH and HTTPS) is controlled by AAA.4. When AAA is enabled for access control. As networks scale in the number of devices to maintain it poses an operational burden to maintain local user accounts on every device.15 key SecretKey ! aaa group server tacacs+ TACACS-SERVERS server name TACACS-SERVER-1 ! aaa authentication login default group TACACS-SERVERS local aaa authorization exec default group TACACS-SERVERS local aaa authorization console ip http authentication aaa Step 4:  Configure device management protocols. username admin password c1sco123 enable secret c1sco123 service password-encryption aaa new-model By default. Secure HTTP (HTTPS) and Secure Shell (SSH) are secure replacements for the HTTP and Telnet protocols. A centralized authentication. authorization. hostname [hostname] Step 2:  Configure local login and password. Deploying an MPLS WAN August 2014 Series 59 . They use Secure Sockets Layer (SSL) and Transport Layer Security (TLS) to provide device authentication and data encryption. TACACS+ is the primary protocol used to authenticate management logins on the infrastructure devices to the AAA server. This makes it easy to identify the device. The local login account and password provides basic access authentication to a router. HTTPS access to the router uses the enable password for authentication. you prevent the disclosure of plain text passwords when viewing configuration files.Procedure 1 Configure the WAN remote router Within this design. and this access provides only limited operational privileges. These are system settings that simplify and secure the management of the solution.

snmp-server community cisco RO snmp-server community cisco123 RW Step 7:  If operational support is centralized in your network. ip domain-name cisco.4. SNMPv2c is configured both for a read-only and a read-write community string.local ip ssh version 2 no ip http server ip http secure-server ip scp server enable line vty 0 15 transport input ssh transport preferred none Step 5:  Enable synchronous logging.0. Telnet and HTTP. SCP is enabled. Specify the transport preferred none on vty lines to prevent errant connection attempts from the CLI prompt.255 line vty 0 15 access-class 55 in ! snmp-server community cisco RO 55 snmp-server community cisco123 RW 55 Tech Tip If you configure an access-list on the vty interface you may lose the ability to use ssh to login from one router to the next for hop-by-hop troubleshooting.0. With this command. if the ip name-server is unreachable. console log messages are displayed on the console after interactive CLI output is displayed or printed. only devices on the 10.4. Without this command. you can increase network security by using an access list to limit the networks that can access your device.0/24 network will be able to access the device via SSH or SNMP. This allows the network infrastructure devices to be managed by a Network Management System (NMS). Deploying an MPLS WAN August 2014 Series 60 . access-list 55 permit 10.0 0.Secure management of the network device is enabled through the use of the SSH and HTTPS protocols. which allows the use of code upgrades using Prime Infrastructure via the SSH-based SCP protocol. long timeout delays may occur for mistyped commands. Both protocols are encrypted for privacy. line con 0 transport preferred none logging synchronous Step 6:  Enable Simple Network Management Protocol (SNMP). and the unsecure protocols.48. are turned off.48. you can continue typing at the device console when debugging is enabled. When synchronous logging of unsolicited messages and debug output is turned on. In this example.

the loopback address is the best way to manage the router in-band. Allocate the loopback address from a unique network range that is not part of any other internal network summary range.17 ntp update-calendar ! clock timezone PST -8 clock summer-time PDT recurring ! service timestamps debug datetime msec localtime service timestamps log datetime msec localtime Step 9:  Configure an in-band management interface. You should program network devices to synchronize to a local NTP server in the network. An NTP network usually gets its time from an authoritative time source. Because of this capability. The loopback interface is a logical interface that is always reachable as long as the device is powered on and any IP interface is reachable to the network. PIM. logs. interface Loopback 0 ip address [ip address] 255. IP Telephony MOH and IP Video Broadcast Streaming are two examples of IP Multicast applications. IP Multicast allows a single IP data stream to be replicated by the infrastructure (routers and switches) and sent from a single source to multiple receivers. NTP then distributes this time across the organizations network.255 ip pim sparse-mode Bind the device processes for SNMP. you can cross-reference events in a network. end hosts must join a multicast group by sending an IGMP message to their local multicast router.255. Layer 3 process and features are also bound to the loopback interface to ensure process resiliency. Deploying an MPLS WAN August 2014 Series 61 . the local router consults another router in the network that is acting as an RP to map the receivers to active sources so they can join their streams. TACACS+ and NTP to the loopback interface address for optimal resiliency.48. SSH. To receive a particular IP Multicast data stream. The loopback address is commonly a host address with a 32-bit address mask. ntp server 10. which is based on sparse mode multicast operation. In a traditional IP Multicast design. The local NTP server typically references a more accurate clock feed from an outside source. By configuring console messages.Step 8:  Configure a synchronized clock.4. Using IP Multicast is much more efficient than multiple individual unicast streams or a Broadcast stream that would propagate everywhere. The Network Time Protocol (NTP) is designed to synchronize a network of devices. and debug output to provide time stamps on output. snmp-server trap-source Loopback0 ip ssh source-interface Loopback0 ip pim register-source Loopback0 ip tacacs source-interface Loopback0 ntp source Loopback0 Step 10:  Configure IP Multicast routing. such as a radio clock or an atomic clock attached to a time server.255. Auto RP is used to provide a simple yet scalable way to provide a highly resilient RP environment. In this design.

ip pim sparse-mode Procedure 2 Connect to the MPLS PE router Step 1:  Assign an interface bandwidth value that corresponds to the actual interface speed. interface [interface type] [number] ip address [IP address] [netmask] Step 3:  Administratively enable the interface and disable Cisco Discovery Protocol. ip multicast-routing Step 11:  Configure every Layer 3 switch and router to discover the IP Multicast RP with autorp. interface [interface type] [number] no cdp enable no shutdown Example interface GigabitEthernet0/0 bandwidth 25000 ip address 192.000 kbps Step 2:  Assign the IP address and netmask of the WAN interface.9 255.252 no cdp enable no shutdown Deploying an MPLS WAN August 2014 Series 62 . Use the ip pim autorp listener command to allow for discovery across sparse mode links. If you are using a subrate service.Enable IP Multicast routing on the platforms in the global configuration mode.255. ip pim autorp listener Step 12:  Enable sparse mode multicast operation for all Layer 3 interfaces in the network. It is not recommend that you use Cisco Discovery Protocol on external interfaces. Typically.168. use the policed rate from the carrier.255.252 is used. The example shows a Gigabit interface (1000 Mbps) with a subrate of 10 Mbps. interface [interface type] [number] bandwidth [bandwidth (kbps)] Tech Tip Command Reference: bandwidth kbps 10 Mbps = 10.4. This configuration provides for future scaling and control of the IP Multicast environment and can change based on network needs and design.255. a pointto-point netmask of 255.255. You must negotiate the IP addressing used between CE and PE routers with your MPLS carrier.

The MPLS carrier must provide their ASN (the ASN in the previous step is the ASN identifying your site).255 network [Secondary router loopback network] mask 255. the aggregate is advertised to the MPLS PE. This is required for loopback resiliency. you must list each individually. router bgp 65511 no synchronization bgp router-id [IP address of Loopback0] bgp log-neighbor-changes no auto-summary Step 2:  Configure eBGP. router bgp 65511 network [PE-CE link network] mask [PE-CE link netmask] network [Primary router loopback network] mask 255. you must use a BGP ASN. which offers a measure of resiliency. Tech Tip On the primary MPLS CE router. The aggregate address configured below suppresses the more specific routes. To ensure reachability of the loopback interfaces in a dual-router design. You can use this to determine router reachability. • The route is redistributed into BGP (not applicable in the remote-site use case). If the various LAN networks cannot be summarized. The IP assignment for the remote sites was designed so that all of the networks in use can be summarized within a single aggregate route. The CE router advertises only network routes to the PE via BGP in the following cases: • The route is specified in network statements and is present in the local routing table.255. for troubleshooting. you must add a network statement for the loopback address of the secondary MPLS CE router. so you should include this network in a network statement. You must configure BGP with the MPLS carrier PE device. Because the carrier PE router uses a different ASN.255.255. It is desirable to advertise a route for the PE-CE link. To complete this step. you must list the loopbacks of both the primary and secondary routers as BGP networks. this configuration is considered an external BGP (eBGP) connection. You might be able to reuse the same value used on the MPLS VPN CE from the WAN-aggregation site. The remote-site routers have in-band management configured via the loopback interface. Consult with your MPLS carrier on the requirements for the ASN.255. The remote-site LAN networks must be advertised.Procedure 3 Configure WAN routing Step 1:  Enable BGP. If any LAN network is present in the route table.255 network [DATA network] mask [netmask] network [VOICE network] mask [netmask] aggregate-address [summary IP address] [summary netmask] summary-only neighbor [IP address of PE] remote-as [carrier ASN] Deploying an MPLS WAN August 2014 Series 63 .

the iBGP session will not be established until you complete the transit network and EIGRP (LAN side) steps. providing access between the two carriers.12. Example: MPLS CE Router (secondary) router bgp 65511 no synchronization bgp router-id 10.255 network 10. The dual-carrier MPLS design requires that a BGP link is configured between the CE routers.255.206 mask 255. Each router applies this route map outbound to the neighbor for its respective MPLS carrier. Because the CE routers are using the same ASN.168.255.255.0 255. it is a best practice to disable the site from becoming a transit site.8.0 aggregate-address 10. remote sites will advertise themselves as a transit autonomous system.Step 3:  Configure iBGP between the remote-site MPLS CE routers. when a link to an MPLS hub has failed.168. Unless the remote site has been specifically designed for this type of routing behavior.8.252. with a high bandwidth connection.168.5.5. You need to apply this route map on both remote-site MPLS CE routers.0 summary-only neighbor 10.4.8 mask 255.255. router bgp 65511 neighbor [IP address of PE 2] route-map NO-TRANSIT-AS out ip as-path access-list 10 permit ^$ ! route-map NO-TRANSIT-AS permit 10 match as-path 10 Tech Tip The regular expression ^$ corresponds to routes originated from the remote-site.255.255.252 network 10.255.10 route-map NO-TRANSIT-AS out no auto-summary ! ip as-path access-list 10 permit ^$ Deploying an MPLS WAN August 2014 Series 64 . this configuration is considered an internal BGP (iBGP) connection.255.1 remote-as 65511 neighbor 10. By default.0 mask 255. router bgp 65511 neighbor [iBGP neighbor Transit Net IP] remote-as 65511 neighbor [iBGP neighbor Transit Net IP] next-hop-self Step 4:  Configure BGP to prevent the remote site from becoming a transit AS.255.5.1 next-hop-self neighbor 192.255.206 mask 255.13. Note.206 bgp log-neighbor-changes network 192.8.4.255.255. In the dual-MPLS design.251.252.4. You must use a route-map and an as-path access-list filter.5.10 remote-as 65402 neighbor 192.0 mask 255.0 network 10.5. In certain cases. BGP readvertises all BGP learned routes.255.255 network 10. this means that MPLS-A routes will be advertised to MPLS-B and vice-versa.255. This type of filter allows for only the locally originated routes to be advertised.248.

GigabitEthernet0/2 no ip address channel-group 2 no shutdown Step 3:  Configure EtherChannel member interfaces on the access-layer switch Connect the router EtherChannel uplinks to separate switches in the access layer switch stack. the remote sites use collapsed routing.1Q trunk interfaces to the LAN access layer. to separate redundant modules for additional resiliency. then skip to the “Deploying a WAN Remote-Site Distribution Layer” chapter of this guide. Configure the physical interfaces to tie to the logical port-channel by using the channel-group command. The number for the port-channel and channel-group must match. The VLAN numbering is locally significant only. If the access-layer device is a single. interface Port-channel2 description EtherChannel link to RS206-A2960X no shutdown Step 2:  Configure EtherChannel member interfaces on the router. fixed-configuration switch. interface GigabitEthernet0/1 description RS206-A2960X Gig1/0/23 ! interface GigabitEthernet0/2 description RS206-A2960X Gig2/0/23 ! interface range GigabitEthernet0/1. Layer 2 EtherChannels are used to interconnect the CE router to the access layer in the most resilient method possible. or in the case of the Cisco Catalyst 4507R+E distribution layer. For complete access-layer configuration details. with 802. so you configure EtherChannel statically. a simple Layer 2 trunk between the router and switch is used. Deploying an MPLS WAN August 2014 Series 65 . In the access-layer design. If you are using a remote-site distribution layer. Not all router platforms can support LACP to negotiate with the switch. see the Campus Wired LAN Technology Design Guide.! route-map NO-TRANSIT-AS permit 10 match as-path 10 Procedure 4 Connect router to access-layer switch Reader Tip This guide includes only the additional steps to complete the distribution-layer configuration. Option 1: Layer 2 EtherChannel from router to access-layer switch Step 1:  Configure a port-channel interface on the router.

interface Port-channel2 description EtherChannel link to RS206-3925-2 switchport trunk allowed vlan 64. Prune the VLANs allowed on the trunk to only the VLANs that are active on the access-layer switch.99 switchport mode trunk ip arp inspection trust spanning-tree portfast trunk ip dhcp snooping trust no shutdown The Cisco Catalyst 3750 Series Switch requires the switchport trunk encapsulation dot1q command. so you configure EtherChannel statically. Doing the configuration in this order allows for minimal configuration and reduces errors because most of the commands entered to a port-channel interface are copied to its members’ interfaces and do not require manual replication. Set DHCP Snooping and Address Resolution Protocol (ARP) inspection to trust. Use an 802. Not all connected router platforms can support LACP to negotiate with the switch.1Q trunk for the connections. the interface type is port-channel. Configure two or more physical interfaces to be members of the EtherChannel.The physical interfaces that are members of a Layer 2 EtherChannel are configured prior to configuring the logical port-channel interface. Deploying an MPLS WAN August 2014 Series 66 . When using EtherChannel. interface GigabitEthernet1/0/23 description Link to RS206-3925-2 Gig0/1 interface GigabitEthernet2/0/23 description Link to RS206-3925-2 Gig0/2 ! interface range GigabitEthernet1/0/23. It is recommended that they are added in multiples of two. This allows the router to provide the Layer 3 services to all the VLANs defined on the access-layer switch. and the number must match the channel group configured in Step 2. apply the egress QoS macro that was defined in the platform configuration procedure in order to ensure traffic is prioritized appropriately. Also. GigabitEthernet2/0/23 switchport macro apply EgressQoS channel-group 2 mode on logging event link-status logging event trunk-status logging event bundle-status Step 4:  Configure EtherChannel trunk on the access-layer switch.69.

This allows the router to provide the Layer 3 services to all the VLANs defined on the access-layer switch. When using a centralized DHCP server.[sub-interface number] encapsulation dot1Q [dot1q VLAN tag] Step 2:  Repeat the subinterface portion of the previous step for all data or voice VLANs. and HSRP is configured at the access layer.1Q tag.69.0 where N. but making them the same simplifies the overall configuration. you can map the appropriate data or voice subinterfaces to the VLANs on the LAN switch. Step 3:  Configure IP settings for each subinterface. Deploying an MPLS WAN August 2014 Series 67 .255. routers with LAN interfaces connected to a LAN using DHCP for endstation IP addressing must use an IP helper.N.1 255. The actual interface IP assignments are configured in the following procedure.Option 2: Layer 2 trunk from router to access-layer switch Step 1:  Enable the physical interface on the router. interface [type][number].N.99 switchport mode trunk ip arp inspection trust spanning-tree portfast trunk logging event link-status logging event trunk-status ip dhcp snooping trust no shutdown load-interval 30 macro apply EgressQoS The Cisco Catalyst 3750 Series Switch requires the switchport trunk encapsulation dot1q command.255. After the physical interface or port-channel has been enabled.N. Prune the VLANs allowed on the trunk to only the VLANs that are active on the access-layer switch.1Q trunk for the connection. Use an 802. and then set DHCP Snooping and Address Resolution Protocol (ARP) inspection to trust. Procedure 5 Configure access-layer routing This remote-site MPLS CE router is the second router of a dual-router design. The subinterface number does not need to equate to the 802. This design uses an IP addressing convention with the default gateway router assigned an IP address and IP mask combination of N. Step 1:  Create subinterfaces and assign VLAN tags. interface GigabitEthernet1/0/23 description Link to RS206-3925-2 Gig0/2 switchport trunk allowed vlan 64. interface GigabitEthernet0/2 description RS206-A2960X Gig1/0/23 no ip address no shutdown Step 2:  Configure the trunk on the access-layer switch.N is the IP network and 1 is the IP host.

64 description Data encapsulation dot1Q 64 ip helper-address 10.4.48.69 description Voice encapsulation dot1Q 69 ip helper-address 10.[sub-interface number] description [usage] ip helper-address 10.10 ip pim sparse-mode Example: Layer 2 EtherChannel interface Port-channel2 no ip address no shutdown ! hold-queue 150 in ! interface Port-channel2.4.10 ip pim sparse-mode Deploying an MPLS WAN August 2014 Series 68 .48.This remote-site MPLS CE router is the second router of a dual-router design and HSRP is configured at the access layer.4.64 description Data encapsulation dot1Q 64 ip helper-address 10.69 description Voice encapsulation dot1Q 69 ip helper-address 10.4.10 ip pim sparse-mode ! interface GigabitEthernet0/2.10 ip pim sparse-mode ! interface Port-channel2.10 ip pim sparse-mode Example: Layer 2 Trunk interface GigabitEthernet0/2 no ip address no shutdown ! interface GigabitEthernet0/2. The actual interface IP assignments will be configured in the following procedure. interface [type][number].48.48.4.48.

The relevant HSRP parameters for the router configuration are shown in the following table. Step 1:  Configure HSRP. The PIM designated router (DR) should be on the HSRP active router. and the HSRP standby router is the router connected to the secondary MPLS carrier or backup link. In this design. without waiting for a scenario where there is no router in the HSRP active state. Table 12 . you configure the HSRP active router with a standby priority that is higher than the HSRP standby router.Procedure 6 Configure access-layer HSRP Configure HSRP to use a virtual IP (VIP) as a default gateway that is shared between two routers. The DR is normally elected based on the highest IP address. You can influence the PIM DR election by explicitly setting the DR priority on the LAN-facing subinterfaces for the routers. Tech Tip The HSRP priority and PIM DR priority are shown in the previous table to be the same value. you are not required to use identical values. and it has no awareness of the HSRP configuration. assigning the HSRP active router a lower real IP address than the HSRP standby router requires a modification to the PIM configuration.2 110 110 MPLS CE (secondary) or DMVPN Spoke Standby .3 105 105 The dual-router access-layer design requires a modification for resilient multicast.1 . The HSRP active router is the MPLS CE router connected to the primary MPLS carrier. interface [type][number]. however. In this procedure.1 . The preempt option allows a router with a higher priority to become the HSRP active.WAN remote-site HSRP parameters (dual-router design) Router HSRP role Virtual IP address (VIP) Real IP address HSRP priority PIM DR priority MPLS CE (primary) Active . The router with the higher standby priority value is elected as the HSRP active router.[sub-interface number] ip address [LAN network 1 address] [LAN network 1 netmask] ip pim dr-priority 105 standby version 2 standby 1 ip [LAN network 1 gateway address] standby 1 priority 105 standby 1 preempt standby 1 authentication md5 key-string c1sco123 Deploying an MPLS WAN August 2014 Series 69 .

255.64 description Data encapsulation dot1Q 64 ip address 10.0 ip helper-address 10. Example: MPLS CE Router (Secondary) with Layer 2 EtherChannel interface Port-channel2 no ip address no shutdown ! interface Port-channel2.Step 2:  Repeat this procedure for all data or voice subinterfaces.12.10 ip pim dr-priority 105 ip pim sparse-mode standby version 2 standby 1 ip 10.255.5.3 255.255.5.1 Deploying an MPLS WAN August 2014 Series 70 .48.5.12.69 description Voice encapsulation dot1Q 69 ip address 10.48.1 standby 1 priority 105 standby 1 preempt standby 1 authentication md5 key-string c1sco123 ! interface Port-channel2.255.3 255.0 ip helper-address 10.10 ip pim dr-priority 105 ip pim sparse-mode standby version 2 standby 1 ip 10.255.13.12.4.13.1 standby 1 priority 105 standby 1 preempt standby 1 authentication md5 key-string c1sco123 Example: MPLS CE Router (Secondary) with Layer 2 Trunk interface GigabitEthernet0/2 no ip address no shutdown ! interface GigabitEthernet0/2.5.0 ip helper-address 10.48.4.64 description Data encapsulation dot1Q 64 ip address 10.5.12.4.5.255.10 ip pim dr-priority 105 ip pim sparse-mode standby version 2 standby 1 ip 10.3 255.

4. The transit network should use an additional subinterface on the router interface that is already being used for data or voice.1 standby 1 priority 105 standby 1 preempt standby 1 authentication md5 key-string c1sco123 Procedure 7 Configure the transit network Configure the transit network between the two routers.48.8.255.13.255. There are no end stations connected to this network.5.0 ip helper-address 10.255.[sub-interface number] encapsulation dot1Q [dot1q VLAN tag] ip address [transit net address] [transit net netmask] ip pim sparse-mode Example interface GigabitEthernet0/2.2 255.standby 1 priority 105 standby 1 preempt standby 1 authentication md5 key-string c1sco123 ! interface GigabitEthernet0/2.5.252 ip pim sparse-mode Deploying an MPLS WAN August 2014 Series 71 . You use this network for router-router communication and to avoid hairpinning. interface [interface type][number]. configure the transit network interface.3 255.5.10 ip pim dr-priority 105 ip pim sparse-mode standby version 2 standby 1 ip 10. so HSRP and DHCP are not required.69 description Voice encapsulation dot1Q 69 ip address 10.99 description Transit Net encapsulation dot1Q 99 ip address 10. Step 1:  On the secondary MPLS CE router.255.13.

All interfaces except the transit-network subinterface should remain passive. all LAN-facing interfaces and the loopback must be EIGRP interfaces. Neighbor authentication enables the secure establishment of peering adjacencies and exchange route tables over the DMVPN tunnel interface. Step 1:  On the router. key chain LAN-KEY key 1 key-string cisco ! router eigrp LAN address-family ipv4 unicast autonomous-system 100 af-interface [interface type] [number] authentication mode md5 authentication key-chain LAN-KEY no passive-interface exit-af-interface exit-address-family Deploying an MPLS WAN August 2014 Series 72 .Procedure 8 Configure EIGRP (LAN side) You must configure a routing protocol between the two routers. This design uses a best practice of assigning the router ID to a loopback address. The network range must include all interface IP addresses either in a single network statement or in multiple network statements. In this design. configure the EIGRP LAN process facing the access layer. Do not include the WAN interface (MPLS PE-CE link interface) as an EIGRP interface. This ensures that the HSRP active router has full reachability information for all WAN remote sites. router eigrp LAN address-family ipv4 unicast autonomous-system 100 af-interface default passive-interface exit-af-interface af-interface [Transit link interface] no passive-interface exit-af-interface network [network] [inverse mask] eigrp router-id [IP address of Loopback0] exit-address-family Step 2:  Configure EIGRP neighbor authentication.

Step 3:  On the router.0.255. router eigrp LAN address-family ipv4 unicast autonomous-system 100 topology base default-metric [WAN bandwidth] [WAN delay] 255 1 1500 redistribute bgp 65511 exit-af-topology exit-address-family Tech Tip Command Reference: default-metric bandwidth delay reliability loading mtu bandwidth—Minimum bandwidth of the route in kilobytes per second delay—Route delay in tens of microseconds. redistribute BGP into the EIGRP LAN process.99 authentication mode md5 authentication key-chain LAN-KEY no passive-interface exit-af-interface topology base default-metric 100000 100 255 1 1500 redistribute bgp 65511 exit-af-topology network 10.255 eigrp router-id 10.4. only the WAN bandwidth and delay values are used for metric calculation. Example router eigrp LAN address-family ipv4 unicast autonomous-system 100 af-interface default passive-interface exit-af-interface af-interface GigabitEthernet0/2.1.255.252.206 exit-address-family Deploying an MPLS WAN August 2014 Series 73 . A default metric redistributes the BGP routes into EIGRP.0 0. By default.

Deploying a WAN Remote-Site
Distribution Layer

PROCESS

Deployment Details
Connecting the Single or Primary Remote-Site Router to the
Distribution Layer
1. Connect router to distribution layer
2. Configure EIGRP (LAN side)
3. Configure the transit network
4. Configure BGP
If you are configuring an MPLS WAN remote-site that uses a single-router, single link design or a dual-router,
dual-link design, complete this process. This process includes all required procedures in order to connect either
the single-router in a single-link design or the primary router in a dual-link design to a LAN distribution layer.
Both distribution-layer remote-site options are shown in the following figure.
Figure 17 - WAN remote site—Connection to distribution layer
WAN

WAN

R1

802.1Q Trunk
(50)

802.1Q Trunk (xx-xx)

R2

802.1Q Trunk
(50, 99)

802.1Q Trunk (64, 69)

VLAN 50 - Router 1 Link

Deploying a WAN Remote-Site Distribution Layer

802.1Q Trunk
(54, 99)

802.1Q Trunk (xx-xx)

VLAN 50 - Router 1 Link
VLAN 54 - Router 2 Link
VLAN 99 - Transit

August 2014 Series

2185

R1

74

Procedure 1

Connect router to distribution layer

Reader Tip
This guide includes only the additional steps to complete the distribution-layer
configuration. For complete distribution-layer configuration details, see the Campus
Wired LAN Technology Design Guide.

Layer 2 EtherChannels are used to interconnect the CE router to the distribution layer in the most resilient
method possible. This connection allows for multiple VLANs to be included on the EtherChannel as necessary.
Step 1:  Configure a port-channel interface on the router.
interface Port-channel1
description EtherChannel link to RS200-D4500X-VSS
no shutdown
Step 2:  Configure the port channel subinterfaces and assign IP addresses.
After you have enabled the interface, map the appropriate subinterfaces to the VLANs on the distributionlayer switch. The subinterface number does not need to equate to the 802.1Q tag, but making them the same
simplifies the overall configuration.
The subinterface configured on the router corresponds to a VLAN interface on the distribution-layer switch.
Traffic is routed between the devices with the VLAN acting as a point-to-point link.
interface Port-channel1.50
description R1 routed link to distribution layer
encapsulation dot1Q 50
ip address 10.5.0.1 255.255.255.252
ip pim sparse-mode
Step 3:  On the router, configure EtherChannel member interfaces.
Configure the physical interfaces to tie to the logical port-channel by using the channel-group command. The
number for the port-channel and channel-group must match. Not all router platforms can support LACP to
negotiate with the switch, so you configure EtherChannel statically.
interface GigabitEthernet0/1
description RS200-D4500X-VSS Ten1/1/1
!
interface GigabitEthernet0/2
description RS200-D4500X-VSS Ten2/1/1
!
interface range GigabitEthernet0/1, GigabitEthernet0/2
no ip address
channel-group 1
no shutdown

Deploying a WAN Remote-Site Distribution Layer

August 2014 Series

75

Step 4:  On the distribution-layer switch, configure the VLAN.
vlan 50
name R1-link
Step 5:  On the distribution-layer switch, configure Layer 3.
Configure a VLAN interface, also known as a switch virtual interface (SVI), for the new VLAN added. The SVI is
used for point-to-point IP routing between the distribution layer and the WAN router.
interface Vlan50
ip address 10.5.0.2 255.255.255.252
ip pim sparse-mode
no shutdown
Step 6:  On the distribution-layer switch, configure EtherChannel member interfaces.
Connect the router EtherChannel uplinks to separate switches in the distribution layer.
If you are using a Cisco Catalyst 4507R+E chassis in the distribution layer, connect the uplinks to separate
redundant modules. This provides additional resiliency.
The physical interfaces that are members of a Layer 2 EtherChannel are configured prior to configuring the
logical port-channel interface. Doing the configuration in this order allows for minimal configuration and reduces
errors because most of the commands entered to a port-channel interface are copied to its member interfaces
and do not require manual replication.
Configure two or more physical interfaces to be members of the EtherChannel. It is recommended that they
are added in multiples of two. Also, apply the egress QoS macro that was defined in the platform configuration
procedure to ensure traffic is prioritized appropriately.
Not all connected router platforms can support LACP to negotiate with the switch, so you configure EtherChannel
statically.
interface GigabitEthernet1/0/1
description Link to RS200-3925-1 Gig0/1
interface GigabitEthernet2/0/1
description Link to RS200-3925-1 Gig0/2
!
interface range GigabitEthernet1/0/1, GigabitEthernet2/0/1
switchport
channel-group 1 mode on
logging event link-status
logging event trunk-status
logging event bundle-status
load-interval 30
macro apply EgressQoS

Deploying a WAN Remote-Site Distribution Layer

August 2014 Series

76

configure the EIGRP LAN process facing the distribution layer. The network range must include all interface IP addresses either in a single network statement or in multiple network statements. Neighbor authentication enables the secure establishment of peering adjacencies and exchange route tables over the DMVPN tunnel interface. key chain LAN-KEY key 1 key-string cisco ! router eigrp LAN address-family ipv4 unicast autonomous-system 100 af-interface [interface type] [number] authentication mode md5 authentication key-chain LAN-KEY Deploying a WAN Remote-Site Distribution Layer August 2014 Series 77 . This allows the router to provide the Layer 3 services to all the VLANs defined on the distribution-layer switch. . Use an 802. the interface type is port-channel. When using EtherChannel. All other interfaces should remain passive. configure an EtherChannel trunk. This design uses a best practice of assigning the router ID to a loopback address. Prune the VLANs allowed on the trunk to only the VLANs that are active on the distribution-layer switch. Step 1:  On the router.Step 7:  On the distribution-layer switch. In this design. interface Port-channel1 description EtherChannel link to RS200-3925-1 switchport trunk allowed vlan 50 switchport mode trunk spanning-tree portfast trunk no shutdown The Cisco Catalyst 3750 Series Switch requires the switchport trunk encapsulation dot1q command.1Q trunk for the connection. router eigrp LAN address-family ipv4 unicast autonomous-system 100 af-interface default passive-interface exit-af-interface af-interface [Routed link interface] no passive-interface exit-af-interface network [network] [inverse mask] eigrp router-id [IP address of Loopback0] exit-address-family Step 2:  Configure EIGRP neighbor authentication. all distribution-layer-facing subinterfaces and the loopback must be EIGRP interfaces. Procedure 2 Configure EIGRP (LAN side) You must configure a routing protocol between the router and distribution layer. and the number must match the channel group configured in Step 3.

redistribute BGP into the EIGRP LAN process. router eigrp LAN address-family ipv4 unicast autonomous-system 100 topology base default-metric [WAN bandwidth] [WAN delay] 255 1 1500 redistribute bgp 65511 exit-af-topology exit-address-family On the distribution-layer switch VLAN interface. Step 6:  Configure a BGP network statement with a mask matching the distribution-layer EIGRP summary route. EIGRP is already configured on the distribution-layer switch. enter the following configuration. only the WAN bandwidth and delay values are used for metric calculation. you will need to add an EIGRP summary on the distribution switch. router eigrp LAN address-family ipv4 unicast autonomous-system 100 af-interface Vlan50 summary-address [Summary address] exit-af-interface exit-address-family Step 5:  On the router. router eigrp LAN address-family ipv4 unicast autonomous-system 100 af-interface Vlan50 authentication mode md5 authentication key-chain LAN-KEY no passive-interface exit-af-interface exit-address-family Step 4:  If it is necessary to define additional IP networks on the distribution-layer switch. By default. enable EIGRP. If the additional IP networks are outside the existing remote-site summary range. advertise the new IP network in BGP. The VLAN interface that connects to the router must be configured for EIGRP neighbor authentication and as a non-passive EIGRP interface.no passive-interface exit-af-interface exit-address-family Step 3:  On the router. A default metric redistributes the BGP routes into EIGRP. router bgp 65511 network [network and mask] Deploying a WAN Remote-Site Distribution Layer August 2014 Series 78 .

0 mask 255.251.0.254 eigrp stub connected summary redistributed nsf exit-address-family Deploying a WAN Remote-Site Distribution Layer August 2014 Series 79 .0 authentication mode md5 authentication key-chain LAN-KEY no passive-interface exit-af-interface topology base exit-af-topology network 10.24.26.0.255.Example (router configuration) router bgp 65511 network 10.5.255.50 authentication mode md5 authentication key-chain LAN-KEY no passive-interface exit-af-interface topology base default-metric 100000 100 255 1 1500 redistribute bgp 65511 exit-af-topology network 10.248.128 ! router eigrp LAN address-family ipv4 unicast autonomous-system 100 af-interface default passive-interface exit-af-interface af-interface Vlan50 summary-address 10.0 0.0 ! router eigrp LAN address-family ipv4 unicast autonomous-system 100 af-interface default passive-interface exit-af-interface af-interface Port-channel1.5.0.5.0.255.4.248.0 0.255.255.7.5.255 eigrp router-id 10.5.1 255.255.255 eigrp router-id 10.24.255.255 network 10.1.0.0 255.255.0 0.255.200 exit-address-family Example (distribution switch configuration) interface Vlan153 description Server Room RS-200 ip address 10.

The transit network must be a non-passive EIGRP interface. configure the transit network VLAN. You use this network for router-router communication and to avoid hairpinning. vlan 99 name Transit-net Step 4:  Add the transit network VLAN to the existing distribution-layer switch EtherChannel trunk.Procedure 3 Configure the transit network If you are using a dual-router design. complete this procedure. The dual-carrier MPLS design requires that a BGP link is configured between the CE routers. configure the transit net interface. so no SVI is required. This design uses iBGP peering and requires the next-hop-self-configuration option.99 authentication mode md5 authentication key-chain LAN-KEY no passive-interface exit-af-interface exit-address-family Step 3:  On the distribution-layer switch. interface Port-channel1 switchport trunk allowed vlan add 99 Procedure 4 Configure BGP If you are using a dual-router design. Step 1:  Configure iBGP between the remote-site MPLS CE routers. router eigrp LAN address-family ipv4 unicast autonomous-system 100 af-interface Port-channel1.255. enable EIGRP on the transit network interface.255. interface Port-channel1.5. complete this procedure. so HSRP and DHCP are not required. Deploying a WAN Remote-Site Distribution Layer August 2014 Series 80 . Because the CE routers are using the same ASN. There are no end stations connected to this network. The transit network should use an additional subinterface on the EtherChannel interface that is already used to connect to the distribution layer.252 ip pim sparse-mode Step 2:  On the router. Configure the transit network between the two routers.9 255. The transit network uses Layer 2 pass-through on the distribution-layer switch.99 description Transit Net encapsulation dot1Q 99 ip address 10. this configuration is considered an internal BGP (iBGP) connection. Step 1:  On the router.0.

Each router applies this outbound to the neighbor for its respective MPLS carrier. providing access between the two carriers. the iBGP session will not be established until you complete the transit network and EIGRP (LAN side) steps. Unless the remote site has been specifically designed for this type of routing behavior. router bgp 65511 neighbor [IP address of PE] route-map PREFER-MPLS-A in Step 4:  Apply a route-map inbound to the neighbor for the primary MPLS carrier only. You must use a route-map and an as-path access-list filter. router bgp 65511 neighbor [iBGP neighbor Transit Net IP] remote-as 65511 neighbor [iBGP neighbor Transit Net IP] next-hop-self Step 2:  Configure BGP to prevent the remote site from becoming a transit AS. and it is likely that the first path selected will remain the active path unless the routing protocol detects a failure. The MPLS dual-carrier design in many cases provides two equal cost paths. Accomplishing the design goal of deterministic routing and primary/secondary routing behavior necessitates tuning BGP. with a high bandwidth connection. Note. By default. ip as-path access-list 1 permit _65401$ ! route-map PREFER-MPLS-A permit 10 match as-path 1 set local-preference 200 ! route-map PREFER-MPLS-A permit 20 Deploying a WAN Remote-Site Distribution Layer August 2014 Series 81 . BGP uses a well-known rule set in order to determine the “best path” when the same IP route prefix is reachable via two different paths. remote sites advertise themselves as a transit autonomous system. This type of filter allows for only the locally originated routes to be advertised. You need to apply this route-map on both remote-site MPLS CE routers. In certain cases. BGP readvertises all BGP learned routes. this means that MPLS-A routes are advertised to MPLS-B and vice-versa. router bgp 65511 neighbor [IP address of PE] route-map NO-TRANSIT-AS out ip as-path access-list 10 permit ^$ ! route-map NO-TRANSIT-AS permit 10 match as-path 10 Tech Tip The regular expression ^$ corresponds to routes originated from the remote-site. This requires the use of a route-map and an as-path access-list filter. In the dual-MPLS design.You must complete this step on both remote-site MPLS CE routers. it is a best practice to disable the site from becoming a transit site. Step 3:  Tune BGP routing to prefer the primary MPLS carrier. when a link to an MPLS hub has failed.

Router 2 Link VLAN 99 . Connect router to distribution layer 2. Routes originated from the secondary MPLS carrier continue to use their default local preference of 100. distribution layer-remote-site design is shown in the following figure. the BGP local preference is 200 for the primary MPLS carrier.1Q Trunk (50. Figure 18 . Configure EIGRP (LAN side) If you are using dual-carrier design for the MPLS WAN remote site.Tech Tip The regular expression _65401$ corresponds to routes originated from the AS 65401 (MPLS-A).255.255.1Q Trunk (54. This allows BGP to selectively modify the routing information for routes originated from this AS. Step 5:  Add a loopback network for the secondary router. 99) 802. dual-link design. 99) 802. zz) 2132 802.Transit 802. This design uses a separate routed link from the second router of the dual-router scenario to the LAN distribution-layer switch. In this example. PROCESS router bgp 65511 network [Secondary router loopback network] mask 255. This process connects the distribution layer to the second router of the dual-router. xx) R2 Deploying a WAN Remote-Site Distribution Layer August 2014 Series 82 .1Q Trunk (ww.1Q Trunk (yy. The dual-router.Router 1 Link VLAN 54 .255 Connecting the Secondary Remote-Site Router to the Distribution Layer 1. complete this process.WAN remote site—Connection to distribution layer WAN R1 VLAN 50 .

interface GigabitEthernet0/1 description RS200-D4500X-VSS Ten1/1/2 ! interface GigabitEthernet0/2 description RS200-D4500X-VSS Ten2/1/2 ! Deploying a WAN Remote-Site Distribution Layer August 2014 Series 83 . but making them the same simplifies the overall configuration. interface Port-channel2.255. configure the transit network interface.255. Step 1:  On the secondary router.252 ip pim sparse-mode Step 3:  On the router.0. The number for the port-channel and channel-group must match.0. map the appropriate subinterfaces to the VLANs on the distributionlayer switch. configure the EtherChannel member interfaces. This guide only includes the additional steps to complete the distribution layer configuration.54 description R2 routed link to distribution layer encapsulation dot1Q 54 ip address 10.252 ip pim sparse-mode Step 4:  On the router.99 description Transit Net encapsulation dot1Q 99 ip address 10.1Q tag.5. Traffic is routed between the devices with the VLAN acting as a point-to-point link. interface Port-channel2 description EtherChannel link to D4500X-VSS no shutdown Step 2:  Configure the port channel subinterfaces and assign IP address.10 255.5. Not all router platforms can support LACP to negotiate with the switch.255. interface Port-channel2. This connection allows for multiple VLANs to be included on the EtherChannel as necessary. The subinterface number does not need to equate to the 802.5 255. After you have enabled the interface. configure a port-channel interface. Layer 2 EtherChannels are used to interconnect the CE router to the distribution layer in the most resilient method possible. so you configure EtherChannel statically. Configure the physical interfaces to tie to the logical port-channel using by the channel-group command.Procedure 1 Connect router to distribution layer Reader Tip Please refer to the Campus Wired LAN Technology Design Guide for complete distribution layer configuration details. The subinterface configured on the router corresponds to a VLAN interface on the distribution-layer switch.255.

The SVI is used for point-to-point IP routing between the distribution layer and the WAN router.interface range GigabitEthernet0/1.255. Configure two or more physical interfaces to be members of the EtherChannel. configure a VLAN. It is recommended that they are added in multiples of two. and in the case of the Cisco Catalyst 4507R+E distribution layer.5.6 255. configure Layer 3. Configure a VLAN interface. configure EtherChannel member interfaces.252 ip pim sparse-mode no shutdown Step 7:  On the distribution-layer switch. Not all connected router platforms can support LACP to negotiate with the switch. vlan 54 name R2-link Step 6:  On the distribution-layer switch. interface Vlan54 ip address 10. so you configure EtherChannel statically. The physical interfaces that are members of a Layer 2 EtherChannel are configured prior to configuring the logical port-channel interface. apply the egress QoS macro that was defined in the platform configuration procedure to ensure traffic is prioritized appropriately. GigabitEthernet0/2 no ip address channel-group 2 no shutdown Step 5:  On the distribution-layer switch. GigabitEthernet2/0/2 switchport channel-group 2 mode on logging event link-status logging event trunk-status logging event bundle-status load-interval 30 macro apply EgressQoS Deploying a WAN Remote-Site Distribution Layer August 2014 Series 84 . interface GigabitEthernet1/0/2 description Link to RS200-3925-2 Gig0/1 interface GigabitEthernet2/0/2 description Link to RS200-3925-2 Gig0/2 ! interface range GigabitEthernet1/0/2. for the new VLAN added. Doing the configuration in this order allows for minimal configuration and reduces errors because most of the commands entered to a port-channel interface are copied to its member interfaces and do not require manual replication.255. to separate redundant modules for additional resiliency. Also.0. also known as a switch virtual interface (SVI). Connect the router EtherChannel uplinks to separate switches in the distribution layer switches or stack.

Use an 802. all distribution-layer-facing subinterfaces and the loopback must be EIGRP interfaces. and the number must match the channel group configured in Step 4. This allows the router to provide the Layer 3 services to all the VLANs defined on the distribution-layer switch. All other interfaces should remain passive. router eigrp LAN address-family ipv4 unicast autonomous-system 100 af-interface default passive-interface exit-af-interface af-interface [Routed link interface] no passive-interface exit-af-interface af-interface [Transit link interface] no passive-interface exit-af-interface network [network] [inverse mask] eigrp router-id [IP address of Loopback0] exit-address-family Deploying a WAN Remote-Site Distribution Layer August 2014 Series 85 .99 switchport mode trunk spanning-tree portfast trunk no shutdown The Cisco Catalyst 3750 Series Switch requires the switchport trunk encapsulation dot1q command.Step 8:  On the distribution-layer switch. In this design. configure an EtherChannel trunk. interface Port-channel2 description EtherChannel link to RS200-3925-2 switchport trunk allowed vlan 54. Procedure 2 Configure EIGRP (LAN side) You must configure a routing protocol between the router and distribution layer. Prune the VLANs allowed on the trunk to only the VLANs that are active on the distribution-layer switch. When using EtherChannel. configure the EIGRP LAN process facing the distribution layer. the interface type is port-channel. The network range must include all interface IP addresses either in a single network statement or in multiple network statements. Step 1:  On the router. This design uses a best practice of assigning the router ID to a loopback address.1Q trunk for the connection.

key chain LAN-KEY key 1 key-string cisco ! router eigrp LAN address-family ipv4 unicast autonomous-system 100 af-interface [interface type] [number] authentication mode md5 authentication key-chain LAN-KEY no passive-interface exit-af-interface exit-address-family Step 3:  On the router. The VLAN interface that connects to the router must be configured as a non-passive EIGRP interface. only the WAN bandwidth and delay values are used for metric calculation. A default metric redistributes the BGP routes into EIGRP. router eigrp LAN address-family ipv4 unicast autonomous-system 100 topology base default-metric [WAN bandwidth] [WAN delay] 255 1 1500 redistribute bgp 65511 exit-af-topology exit-address-family Step 4:  On the distribution-layer switch VLAN interface. redistribute BGP into the EIGRP LAN process. enable EIGRP. router eigrp LAN address-family ipv4 unicast autonomous-system 100 af-interface Vlan54 summary-address [New Summary address] exit-af-interface exit-address-family Deploying a WAN Remote-Site Distribution Layer August 2014 Series 86 .Step 2:  Configure EIGRP neighbor authentication. router eigrp LAN address-family ipv4 unicast autonomous-system 100 af-interface Vlan54 authentication mode md5 authentication key-chain LAN-KEY no passive-interface exit-af-interface exit-address-family Step 5:  If it is necessary to define additional IP networks on the distribution-layer switch. EIGRP is already configured on the distribution-layer switch. Neighbor authentication enables the secure establishment of peering adjacencies and exchange route tables over the DMVPN tunnel interface. enter the following configuration. By default. If the additional IP networks are outside the existing remote-site summary range. you will need to add an EIGRP summary on the distribution switch.

255. Configure a BGP network statement with a mask matching the distribution-layer EIGRP summary.0.0 255.0 mask 255.24.255.0 0.0 ! router eigrp LAN address-family ipv4 unicast autonomous-system 100 af-interface default passive-interface exit-af-interface af-interface Port-channel1.5.Step 6:  On the router.255.255.0.54 authentication mode md5 authentication key-chain LAN-KEY no passive-interface exit-af-interface af-interface Port-channel1.255 eigrp router-id 10.248.0.24.248.252.252 ip pim sparse-mode ! router eigrp LAN address-family ipv4 unicast autonomous-system 100 af-interface default passive-interface exit-af-interface af-interface Vlan50 summary-address 10.255 network 10.5. advertise the new IP network in BGP.6 255.0.255.255.200 exit-address-family Example (Distribution switch configuration) interface Vlan54 ip address 10.5. router bgp 65511 network [network and mask] Example (router configuration) router bgp 65511 network 10.255.0.0 authentication mode md5 authentication key-chain LAN-KEY Deploying a WAN Remote-Site Distribution Layer August 2014 Series 87 .5.99 authentication mode md5 authentication key-chain LAN-KEY no passive-interface exit-af-interface topology base default-metric 500000 100 255 1 1500 redistribute bgp 65511 exit-af-topology network 10.0 0.255.

0 authentication mode md5 authentication key-chain LAN-KEY no passive-interface exit-af-interface topology base exit-af-topology network 10.254 eigrp stub connected summary redistributed nsf exit-address-family Deploying a WAN Remote-Site Distribution Layer August 2014 Series 88 .5.255.7.255.248.5.24.0 255.no passive-interface exit-af-interface af-interface Vlan54 summary-address 10.0.1.255 eigrp router-id 10.4.0 0.

The class-map command sets the match logic. Create the QoS Maps to Classify Traffic 2. Step 1:  For each of the six WAN classes of service listed in Table 13. This keyword is followed by the name you want to assign to the class of service. In this case. class-map match-any [class-map name] match dscp [dcsp value] [optional additional dscp value(s)] Deploying WAN Quality of Service August 2014 Series 89 . After you have configured the class-map command. you are defining how traffic egresses your network. You do not need to explicitly configure the default class. Define a policy map that defines the queuing policy 4. the match-any keyword indicates that the maps match any of the specified criteria. you define specific values. It is critical that the classification. Use the following steps to configure the required WAN class maps and matching criteria. You use the following two forms of the match command: match dscp and match protocol. Deployment Details PROCESS Configuring QoS 1. create a class map for DSCP matching. Apply the shaping and queuing policy to a physical interface Procedure 1 Create the QoS Maps to Classify Traffic The class-map command defines a traffic class and identifies traffic to associate with the class name. marking.Deploying WAN Quality of Service When configuring the WAN-edge QoS. Create the policy map that marks BGP traffic 3. These class names are used when configuring policy maps that define actions you wish to take against the traffic type. to match with the match command. Configure shaping and queuing policy 5. such as DSCP and protocols. and bandwidth allocations align to the service provider offering to ensure consistent QoS treatment end to end.

af41 23 (PQ) — CRITICAL-DATA Highly interactive (such as Telnet. Citrix. cs6. operations. cs2 3 — default Best effort other 25 random Step 2:  If you are using a WAN-aggregation MPLS CE router or a WAN remote-site MPLS CE router that is using BGP. class-map match-any [class-map name] match ip protocol [protocol name] Example class-map match-any VOICE match dscp ef ! class-map match-any INTERACTIVE-VIDEO match dscp cs4 af41 ! class-map match-any CRITICAL-DATA match dscp af31 cs3 ! class-map match-any DATA match dscp af21 ! class-map match-any SCAVENGER match dscp af11 cs1 ! class-map match-any NETWORK-CRITICAL match dscp cs6 cs2 ! class-map match-any BGP-ROUTING match protocol bgp Deploying WAN Quality of Service August 2014 Series 90 .QoS classes of service Class of service Traffic type DSCP values Bandwidth % Congestion avoidance VOICE Voice traffic ef 10 (PQ) — INTERACTIVEVIDEO Interactive video (such as video conferencing) cs4. administration and maintenance (OAM) traffic. cs1 5 — NETWORKCRITICAL Routing protocols. Use NBAR to match BGP by protocol. cs3 15 DSCP-based DATA Data af21 19 DSCP-based SCAVENGER Scavenger af11. and Oracle thin clients) af31. BGP traffic is not explicitly tagged with a DSCP value.Table 13 . create a class map for BGP protocol matching.

and then assign it a DSCP value of cs6. To ensure proper treatment of BGP routing traffic in the WAN. policy-map [policy-map-name] Step 2:  Apply the previously created class map. Although the class map you created in the previous step matches all BGP traffic to the class named BGP. One additional default class defines the minimum allowed bandwidth available for best-effort traffic. Step 1:  Create the parent policy map. you must configure a policy map to assign the required DSCP value to all BGP traffic. Step 1:  Create a policy map. The local router policy maps define seven classes while most service providers offer only six classes of service. This specification is accomplished with the use of a policy map. The WAN policy map references the class names you created in the previous procedures and defines the queuing behavior along with the maximum guaranteed bandwidth allocated to each class. complete this procedure. policy-map MARK-BGP class BGP-ROUTING set dscp cs6 Procedure 3 Define a policy map that defines the queuing policy This procedure applies to all WAN routers. assigns a percentage of bandwidth. and associates a specific traffic class to that queue. This is implicitly included within classdefault as shown in Procedure 4. Then. bandwidth percent [percentage] Step 4:  (Optional) Define the priority queue for the class.Tech Tip You do not need to configure a best-effort class. priority percent [percentage] Deploying WAN Quality of Service August 2014 Series 91 . The NETWORK-CRITICAL policy map is defined in order to ensure the correct classification. class [class-name] Step 3:  (Optional) Assign the maximum guaranteed bandwidth for the class. marking. each class within the policy map invokes an egress queue. you must assign a DSCP value of cs6. the network-critical traffic is typically remapped by the service provider into the critical data class. Procedure 2 Create the policy map that marks BGP traffic If you are using a WAN-aggregation MPLS CE router or a WAN remote-site MPLS CE router that uses BGP. and queuing of network-critical traffic on egress to the WAN. After the traffic has been transmitted to the service provider. Most providers perform this remapping by matching on DSCP values cs6 and cs2.

Deploying WAN Quality of Service August 2014 Series 92 . it is important to consider your actual traffic requirements per class and adjust the bandwidth settings accordingly. random-detect [type] Step 7:  Repeat Step 2 through Step 6 for each class in Table 13.Step 5:  (Optional) Apply the child service policy. including class-default. This is an optional step only for the NETWORK-CRITICAL class of service with the MARK-BGP child service policy. Example policy-map WAN class VOICE priority percent 10 class INTERACTIVE-VIDEO priority percent 23 class CRITICAL-DATA bandwidth percent 15 random-detect dscp-based class DATA bandwidth percent 19 random-detect dscp-based class SCAVENGER bandwidth percent 5 class NETWORK-CRITICAL bandwidth percent 3 service-policy MARK-BGP class class-default bandwidth percent 25 random-detect Tech Tip Although these bandwidth assignments represent a good baseline. service-policy [policy-map-name] Step 6:  (Optional) Define the congestion mechanism.

Instead. a specified amount of access bandwidth is contracted with the service provider. This shaping is accomplished with a QoS service policy. class [class-name] shape [average | peak] [bandwidth (bps)] Step 3:  Apply the child service policy. policy-map WAN-INTERFACE-G0/0 class class-default shape average 20000000 service-policy WAN ! policy-map WAN-INTERFACE-G0/1 class class-default shape average 10000000 service-policy WAN Deploying WAN Quality of Service August 2014 Series 93 . This is called a hierarchical Class-Based Weighted Fair Queuing (HCBWFQ) configuration. ensure that the value matches the contracted bandwidth rate from your service provider. As a best practice. service-policy [policy-map-name] Example This example shows a router with a 20-Mbps link on interface GigabitEthernet0/0 and a 10-Mbps link on interface GigabitEthernet0/1. This procedure applies to all WAN routers. you need to configure shaping on the physical interface. and this parent policy includes a shaper that then references a second or subordinate (child) policy that enables queuing within the shaped rate. You configure a QoS service policy on the outside Ethernet interface. To ensure the offered load to the service provider does not exceed the contracted rate that results in the carrier discarding traffic. the demarcation point between the enterprise and service provider may no longer have a physical-interface bandwidth constraint. Step 1:  Create the parent policy map.Procedure 4 Configure shaping and queuing policy With WAN interfaces using Ethernet as an access technology. When you configure the shape average command. embed the interface name within the name of the parent policy map. You can repeat this procedure multiple times to support devices that have multiple WAN connections attached to different interfaces. policy-map [policy-map-name] Step 2:  Configure the shaper.

You can repeat this procedure multiple times to support devices that have multiple WAN connections attached to different interfaces. Step 1:  Select the WAN interface. service-policy output [policy-map-name] Example interface GigabitEthernet0/0 service-policy output WAN-INTERFACE-G0/0 ! interface GigabitEthernet0/1 service-policy output WAN-INTERFACE-G0/1 Deploying WAN Quality of Service August 2014 Series 94 . This procedure applies to all WAN routers.Procedure 5 Apply the shaping and queuing policy to a physical interface To invoke shaping and queuing on a physical interface. interface [interface type] [number] Step 2:  Apply the WAN QoS policy in the outbound direction. you must apply the parent policy that you configured in the previous procedure.

SEC. SEC.2SM. 256MB CF.3(3)M3 securityk9 feature set datak9 feature set Cisco 891 Router CISCO891W-AGN-A-K9 WAAS-Express/AVC/Advanced IP with upgrade up to 1GB DRAM for Cisco 800 Series Routers FL-C800-APP 15. AX license with. 1 SM.3(3)M3 securityk9 feature set datak9 feature set Fixed WAN Remote-site Router Appendix A: Product List August 2014 Series 95 . AVC and WAAS-Express C1941-AX/K9 15. IP Base. AVC. DATA. 2SM. AVC. and WAAS/vWAAS with 1300 connection RTU C2921-AX/K9 Cisco ISR 2911 w/ 3 GE. 1GBDRAM. and WAAS/vWAAS with 1300 connection RTU C2951-AX/K9 Cisco ISR 2921 w/ 3 GE. DATA. SEC.4(2)S securityk9 feature set WAN Remote Site Functional Area Product Description Part Numbers Software Modular WAN Remote-site Router Cisco ISR 4451 w/ 4GE.4(2)S securityk9 feature set appxk9 feature set Cisco ISR 3945 w/ SPE150.3NIM.5GB DRAM. DATA. 4DSP. AX license with: DATA. SEC. 1GB DRAM. 4EHWIC. 2. AX license with. IP Base. 256MB CF.4 EHWIC. DATA. 3 DSP. 2 SM. 256MB CF. ISR-WAAS with 2500 connection RTU ISR4451-X-AX/K9 IOS-XE 15. 1GBDRAM. 4EHWIC. 1 SM. 3GE. IP Base. 4G DRAM. AVC and WAAS/vWAAS with 1300 connection RTU C2911-AX/K9 Unified Communications Paper PAK for Cisco 2900 Series SL-29-UC-K9 Cisco ISR 1941 Router w/ 2 GE. AVC. 256MBCF. IP Base. AVC.8G FLASH. IP Base.5G-VPNK9 IOS-XE 15. and WAAS/vWAAS with 2500 connection RTU C3945-AX/K9 Cisco ISR 3925 w/ SPE100 (3GE.4(2)S Advanced Enterprise feature set Cisco ISR 4451-X Security Bundle w/SEC license PAK ISR4451-X-SEC/K9 IOS-XE 15. 3 DSP.Appendix A: Product List WAN Aggregation Functional Area Product Description Part Numbers Software WAN-aggregation Router Aggregation Services 1002X Router ASR1002X-5G-VPNK9 Aggregation Services 1002 Router ASR1002-5G-VPN/K9 Aggregation Services 1001 Router ASR1001-2. 4 EHWIC. WAAS/vWAAS with 2500 connection RTU C3925-AX/K9 15. 1GB DRAM. 256MB CF. AX license with. 4SM. DATA. AXlicenses with. AX license with. 1GB DRAM. IP Base. 4 EHWIC. AVC. DATA. 2 DSP. 256MBCF. SEC. SEC.3(3)M3 securityk9 feature set datak9 feature set uck9 feature set Unified Communications Paper PAK for Cisco 3900 Series SL-39-UC-K9 Cisco ISR 2951 w/ 3 GE. 2 EHWIC slots. AX licenses with. IP Base. 4DSP. SEC.

1.1EZ3) IP Base feature set 3.3.3SE(15.3SE(15.5.2(1)E3 IP Base feature set 15.1XO(15.1EZ3) IP Base feature set 15.3.2.UPoE ports WS-X4748-UPOE+E Cisco Catalyst 4500E 48 Ethernet 10/100/1000 (RJ45) PoE+ ports WS-X4648-RJ45V+E Cisco Catalyst 3850 Series Stackable 48 Ethernet 10/100/1000 PoE+ ports WS-C3850-48F Cisco Catalyst 3850 Series Stackable 24 Ethernet 10/100/1000 PoE+ Ports WS-C3850-24P Cisco Catalyst 3850 Series 2 x 10GE Network Module C3850-NM-2-10G Cisco Catalyst 3850 Series 4 x 1GE Network Module C3850-NM-4-1G Cisco Catalyst 3650 Series 24 Ethernet 10/100/1000 PoE+ and 2x10GE or 4x1GE Uplink WS-C3650-24PD Cisco Catalyst 3650 Series 24 Ethernet 10/100/1000 PoE+ and 4x1GE Uplink WS-C3650-24PS Cisco Catalyst 3650 Series Stack Module C3650-STACK Cisco Catalyst 3750-X Series Stackable 48 Ethernet 10/100/1000 PoE+ ports WS-C3750X-48PF-S Cisco Catalyst 3750-X Series Stackable 24 Ethernet 10/100/1000 PoE+ ports WS-C3750X-24P-S Cisco Catalyst 3750-X Series Two 10GbE SFP+ and Two GbE SFP ports network module C3KX-NM-10G Cisco Catalyst 3750-X Series Four GbE SFP ports network module C3KX-NM-1G Cisco Catalyst 2960-X Series 24 10/100/1000 Ethernet and 2 SFP+ Uplink WS-C2960X-24PD Cisco Catalyst 2960-X FlexStack-Plus Hot-Swappable Stacking Module C2960X-STACK Cisco Catalyst 3650 Series 24 Ethernet 10/100/1000 PoE+ and 4x1GE Uplink WS-C3650-24PS Stackable Access Layer Switch Standalone Access Layer Switch Appendix A: Product List 3.LAN Access Layer Functional Area Product Description Part Numbers Software Modular Access Layer Switch Cisco Catalyst 4500E Series 4507R+E 7-slot Chassis with 48Gbps per slot WS-C4507R+E 3.01EZ3) IP Base feature set August 2014 Series 96 .0.0.3E(15.0(2)EX5 LAN Base feature set 3.3. 520Gbps WS-X45-SUP7L-E Cisco Catalyst 4500E 48 Ethernet 10/100/1000 (RJ45) PoE+.3.1E3) IP Base feature set 3.1XO1) IP Base feature set Cisco Catalyst 4500E Supervisor Engine 8-E.3at PoE+ 10/100/1000 (RJ-45) WS-X4748-RJ45V+E Cisco Catalyst 4500E Series 4507R+E 7-slot Chassis with 48Gbps per slot WS-C4507R+E Cisco Catalyst 4500E Supervisor Engine 7L-E.3SE(15. Unified Access. 928Gbps WS-X45-SUP8-E Cisco Catalyst 4500E 12-port 10GbE SFP+ Fiber Module WS-X4712-SFP+E Cisco Catalyst 4500E 48-Port 802.

3E(15.1E3) Enterprise Services feature set 15.3.3SE(15.LAN Distribution Layer Functional Area Product Description Part Numbers Software Modular Distribution Layer Virtual Switch Pair Cisco Catalyst 6800 Series 6807-XL 7-Slot Modular Chassis C6807-XL Cisco Catalyst 6500 VSS Supervisor 2T with 2 ports 10GbE and PFC4 VS-S2T-10G 15.2(1)E3 IP Services feature set August 2014 Series 97 .1(2)SY3 IP Services feature set 3.1(2)SY3 IP Services feature set Cisco Catalyst 6500 4-port 40GbE/16-port 10GbE Fiber Module w/DFC4 WS-X6904-40G-2T Cisco Catalyst 6500 4-port 10GbE SFP+ adapter for WX-X6904-40G module CVR-CFP-4SFP10G Cisco Catalyst 6500 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX Cisco Catalyst 6500 Distributed Forwarding Card 4 WS-F6K-DFC4-A Cisco Catalyst 6500 Series 6506-E 6-Slot Chassis WS-C6506-E Cisco Catalyst 6500 VSS Supervisor 2T with 2 ports 10GbE and PFC4 VS-S2T-10G Cisco Catalyst 6500 4-port 40GbE/16-port 10GbE Fiber Module w/DFC4 WS-X6904-40G-2T Cisco Catalyst 6500 4-port 10GbE SFP+ adapter for WX-X6904-40G module CVR-CFP-4SFP10G Cisco Catalyst 6500 48-port GigE Mod (SFP) WS-X6748-SFP Cisco Catalyst 6500 Distributed Forwarding Card 4 WS-F6K-DFC4-A Cisco Catalyst 6500 24-port GigE Mod (SFP) WS-X6724-SFP Cisco Catalyst 6500 Distributed Forwarding Card 4 WS-F6K-DFC4-A Extensible Fixed Distribution Layer Virtual Switch Pair Cisco Catalyst 6800 Series 6880-X Extensible Fixed Aggregation Switch (Standard Tables) C6880-X-LE Cisco Catalyst 6800 Series 6880-X Multi Rate Port Card (Standard Tables) C6880-X-LE-16P10G Modular Distribution Layer Virtual Switch Pair Cisco Catalyst 4500E Series 4507R+E 7-slot Chassis with 48Gbps per slot WS-C4507R+E Cisco Catalyst 4500E Supervisor Engine 7-E.2.0.5.3at PoE+ 10/100/1000 (RJ-45) WS-X4748-RJ45V+E Fixed Distribution Layer Virtual Switch Pair Cisco Catalyst 4500-X Series 32 Port 10GbE IP Base Frontto-Back Cooling WS-C4500X-32SFP+ 3.2.3E(15. 848Gbps WS-X45-SUP7-E Cisco Catalyst 4500E 12-port 10GbE SFP+ Fiber Module WS-X4712-SFP+E Cisco Catalyst 4500E 48-Port 802.5.1EZ3) IP Services feature set Cisco Catalyst 3850 Series 4 x 1GE Network Module C3850-NM-4-1G Cisco Catalyst 3850 Series 2 x 10GE Network Module C3850-NM-2-10G Cisco Catalyst 3750-X Series Stackable 12 GbE SFP ports WS-C3750X-12S-E Cisco Catalyst 3750-X Series Two 10GbE SFP+ and Two GbE SFP ports network module C3KX-NM-10G Cisco Catalyst 3750-X Series Four GbE SFP ports network module C3KX-NM-1G Appendix A: Product List 15.1E3) Enterprise Services feature set Stackable Distribution Layer Switch Cisco Catalyst 3850 Series Stackable Switch with 12 SFP Ethernet WS-C3850-12S 3.

please go to the following URL: http://cvddocs.com/fw/240-14b Appendix B: Device Configuration Files August 2014 Series 98 .Appendix B: Device Configuration Files To view the configuration files from the CVD lab devices that we used to test this guide.

• We added EIGRP Authentication configurations. Appendix C: Changes August 2014 Series 99 . • We added the ip scp server enable command. • We added EIGRP Named mode configurations.Appendix C: Changes This appendix summarizes the changes Cisco made to this guide since its last edition.

THE DESIGNS DO NOT CONSTITUTE THE TECHNICAL OR OTHER PROFESSIONAL ADVICE OF CISCO. San Jose. LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THE DESIGNS. STATEMENTS. CONSEQUENTIAL. phone numbers.” WITH ALL FAULTS. INCLUDING. SPECIFICATIONS. ALL DESIGNS. OR INCIDENTAL DAMAGES. and other countries. (1110R) B-0000245-1 08/14 . Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Ltd. “DESIGNS”) IN THIS MANUAL ARE PRESENTED “AS IS. WITHOUT LIMITATION.cisco. Singapore Europe Headquarters Cisco Systems International BV Amsterdam. Inc. CA Asia Pacific Headquarters Cisco Systems (USA) Pte. OR TRADE PRACTICE. Third-party trademarks mentioned are the property of their respective owners. ITS SUPPLIERS OR PARTNERS. RESULTS MAY VARY DEPENDING ON FACTORS NOT TESTED BY CISCO. Americas Headquarters Cisco Systems. The Netherlands Cisco has more than 200 offices worldwide. CISCO AND ITS SUPPLIERS DISCLAIM ALL WARRANTIES.cisco. SPECIAL. and fax numbers are listed on the Cisco Website at www. THE DESIGNS ARE SUBJECT TO CHANGE WITHOUT NOTICE. go to this URL: www. Any examples. WITHOUT LIMITATION. Addresses. USAGE. command display output. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT. AND RECOMMENDATIONS (COLLECTIVELY.Feedback Please use the feedback form to send comments and suggestions about this guide. Any use of actual IP addresses in illustrative content is unintentional and coincidental.S. All rights reserved. To view a list of Cisco trademarks. THE WARRANTY OF MERCHANTABILITY. INCLUDING. and figures included in the document are shown for illustrative purposes only. © 2014 Cisco Systems.com/go/trademarks. FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING. USERS SHOULD CONSULT THEIR OWN TECHNICAL ADVISORS BEFORE IMPLEMENTING THE DESIGNS. EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U. INFORMATION. Inc. The use of the word partner does not imply a partnership relationship between Cisco and any other company. USERS ARE SOLELY RESPONSIBLE FOR THEIR APPLICATION OF THE DESIGNS.com/go/offices.