You are on page 1of 100

MPLS WAN
Technology Design Guide
December 2013

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...................................................................................................... 6
MPLS Dynamic Design Model................................................................................................. 6
Dual MPLS Design Model........................................................................................................ 7
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

..... 86 Configuring QoS...................................................................................................................................................................................................................................................................................................17 Remote Sites—MPLS CE Router Selection...........................................................................................................19 Deployment Details ... 86 Appendix A: Product List..............86 Deployment Details............................. 33 Adding a Secondary MPLS Link on an Existing MPLS CE Router.......................................................................94 Appendix C: Changes....... 22 Configuring the MPLS CE Router...................................................................................................................................................... 75 Connecting the Single or Primary Remote-Site Router to the Distribution Layer..................................................91 Appendix B: Device Configuration Files............................................................................ 75 Connecting the Secondary Remote-Site Router to the Distribution Layer...............................................................Deploying an MPLS WAN........................................................ 59 Deploying a WAN Remote-Site Distribution Layer....................................... 17 Design Overview..................................................................................................................................17 WAN-Aggregation—MPLS CE Routers.................................................................95 Table of Contents ............... 81 Deploying WAN Quality of Service......................................................................................................................................................................................................................................................................................................................................75 Deployment Details................ 18 Design Details............................................................................................. 22 Configuring the Remote-Site MPLS CE Router......... 54 Configuring the Secondary Remote-Site Router.......................................................................................................................................................

48. • Solution design guides integrate or reference existing CVDs. For the most recent CVD guides.255. and applications to address customer needs. more reliable. Both CVD types provide a tested starting point for Cisco partners or customers to begin designing and deploying systems using their own setup and configuration. This section describes the conventions used to specify commands that you must enter. as follows: interface Vlan64 ip address 10. see the following site: http://www. Enter them as one command: police rate 10000 pps burst 10000 packets conform-action set-discard-classtransmit 48 exceed-action transmit Noteworthy parts of system output or device configuration files appear highlighted. information about validated products and software. How to Read Commands Many CVD guides tell you how to use a command-line interface (CLI) to configure network devices.255.5 255. but also include product features and functionality across Cisco products and may include information about third-party integration. CVDs include two guide types that provide tested and validated design and deployment details: • Technology design guides provide deployment details. Commands to enter at a CLI appear as follows: configure terminal Commands that specify a value for a variable appear as follows: ntp server 10.17 Commands with variables that you must define appear as follows: class-map [highest class name] Commands at a CLI or script prompt appear as follows: Router# enable Long commands that line wrap are underlined. They incorporate a broad set of technologies.com/go/cvd/wan Preface December 2013 1 . Cisco engineers have comprehensively tested and documented each CVD in order to ensure faster.10.5.0 Comments and Questions If you would like to comment on a guide or ask questions. please use the feedback form.204.cisco. features. and best practices for specific types of technology.Preface Cisco Validated Designs (CVDs) provide the foundation for systems design based on common use cases or current engineering system priorities. and fully predictable deployment.

the proficiency or experience recommended.com/go/cvd/wan CVD Navigator December 2013 2 .CVD Navigator The CVD Navigator helps you determine the applicability of this guide by summarizing its key elements: the use cases. Related CVD Guides VALIDATED DESIGN For more information. For more details. 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. This section is a quick reference only. implementing. the scope or breadth of the technology covered. see the “Use Cases” section in this guide. Proficiency This guide is for people with the following technical proficiencies—or equivalent experience: • CCNP Routing and Switching—3 to 5 years planning. and troubleshooting local and widearea networks To view the related CVD guides. 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. and CVDs related to this guide. see the Introduction. click the titles or visit the following site: http://www.cisco. verifying. see the “Design Overview” section in this guide.

As organizations move into multinational or global business markets. • 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 December 2013 3 . The ability to easily scale bandwidth or to add additional sites or resilient links makes MPLS an effective WAN transport for growing organizations. 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. the WAN architecture requires a flexible design. The ubiquity of carrier-provided MPLS networks makes it a required consideration for an organization building a WAN.Introduction The MPLS WAN Technology Design Guide. To reduce the time needed to deploy new technologies that support emerging business applications and communications. Related Reading The Layer 2 WAN Technology Design Guide provides guidance and configuration for a VPLS or Metro Ethernet transport. video. the WAN must support the convergence of voice. the WAN design must provide a common resource access experience to the workforce. Technology Use Cases For remote-site users to effectively support the business. centrally managed infrastructure. The VPN WAN Technology Design Guide provides guidance and configuration for broadband or Internet transport in a both a primary or backup role. organizations require that the WAN provide sufficient performance and reliability. To control operational costs. Although most of the applications and services that the remote-site worker uses are centrally located. and data transport onto a single. 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 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 flexible guidance and configuration for Multiprotocol Label Switching (MPLS) transport. regardless of location.

The chosen architecture designates a primary WAN-aggregation site that is analogous to the hub site in a traditional hub-and-spoke design. You can integrate this economical solution seamlessly over any existing infrastructure. The primary WAN-aggregation site is coresident with the data center and usually the primary campus or LAN as well.Design Overview This guide. 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. such as IP. the site uses network equipment scaled for high performance and redundancy. intelligent networks that deliver a wide variety of advanced. the WAN is an IP network. the MPLS WAN Technology Design Guide. or Ethernet. Ethernet WAN Both of the WAN transports mentioned previously use Ethernet as a standard media type. value-added services over a single infrastructure. 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. The usage of an Internet VPN transport to provide a redundant topology option for resiliency is covered in the VPN WAN Technology Design Guide. OC-3. The WAN leverages MPLS VPN as a primary WAN transport or as a backup WAN transport (to an alternate MPLS VPN primary). MPLS WAN Transport Cisco IOS Software Multiprotocol Label Switching (MPLS) enables enterprises and service providers to build next-generation. Frame Relay. This site has direct connections to both WAN transports and high-speed connections to the selected service providers. Subscribers who need to transport IP multicast traffic can enable Multicast VPNs (MVPNs). which can result in significant cost savings and a reduction in operational complexity for enterprises. provides a design that enables highly available. and these transports can be easily integrated to the design. but they are not explicitly discussed. Introduction December 2013 4 . DS-3. and optimized connectivity for multiple remote-site LANs. Much of the discussion in this guide can also be applied to non-Ethernet media (such as T1/E1. ATM. secure. and so on). This peer-to-peer model allows enterprise subscribers to outsource routing information to service providers. MPLS Layer 3 VPNs use a peer-to-peer VPN Model that leverages the Border Gateway Protocol (BGP) to distribute VPN-related information. In addition. The WAN is the networking infrastructure that provides an IP-based interconnection between remote sites that are separated by large geographic distances.

they are typically known as customer edge (CE) routers. and these devices should also connect into the distribution layer. The various design models are contrasted in the following table. tasks such as IP route summarization are performed at the distribution layer. Each of the design models is shown with LAN connections into either a collapsed core/distribution layer or a dedicated WAN distribution layer. Each MPLS carrier terminates to a dedicated WAN router with a primary goal of eliminating any single points of failure.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. A similar method of connection and configuration is used for both. All of the WAN edge routers connect into a distribution layer. The primary differences between the various designs are the usage of routing protocols and the overall scale of the architecture. A single VPN hub router is used across both designs. For each design model.WAN-Aggregation Designs The WAN-aggregation (hub) designs include two or more WAN edge routers. There are no functional differences between these two methods from the WAN-aggregation perspective. In all of the WAN-aggregation designs. When WAN edge routers are referred to in the context of the connection to a carrier or service provider. Each transport connects to a dedicated CE router. There are other various devices supporting WAN edge services. Introduction December 2013 5 . This design guide documents multiple WAN-aggregation design models that are statically or dynamically routed with either single or dual MPLS carriers. Table 1 . The WAN transport options include MPLS VPN used as a primary or secondary transport. you can select several router platforms with differing levels of performance and resiliency capabilities.

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 MPLS 2183 Static Routing or BGP Dynamic Routing MPLS Dynamic Design Model • Supports up to 100 remote sites • Has a single MPLS VPN carrier • Uses BGP routing with MPLS VPN carrier The MPLS Dynamic design model is shown in Figure 1. Figure 1 . Introduction December 2013 6 .MPLS Static Design Model • Supports up to 50 remote sites • Has a single MPLS VPN carrier • Uses static routing with MPLS VPN carrier The MPLS Static design model is shown in the following figure.

Figure 2 . and they are based on various combinations of WAN transports mapped to the site specific requirements for service levels and redundancy.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.Dual MPLS Design Model • Supports up to 500 remote sites • Has multiple MPLS VPN carriers • Uses BGP routing with MPLS VPN carrier • Typically used with a dedicated WAN distribution layer The Dual MPLS design model is shown in the following figure. Figure 3 .WAN remote-site designs MPLS WAN Nonredundant MPLS-A MPLS-B Redundant Links & Routers MPLS-A MPLS-B 2117 MPLS Redundant Links Introduction December 2013 7 .

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

December 2013

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

December 2013

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

December 2013

10

which then forwards the traffic to the proper destination. 69. to support both a routed point-to-point link to allow EIGRP routing with the distribution switch.1Q VLAN Trunk (64. a traffic flow from a remote-site host might be sent to a destination reachable via the alternate WAN transport (for example. EOT of IP SLA probes is implemented in conjunction with HSRP so that in the case of WAN transport failure. This topology works well with either a single or dual router WAN edge. Introduction December 2013 11 . The primary WAN transport router then forwards the traffic out the same data interface to send it to the alternate WAN transport router. an MPLS A + MPLS B remote site communicating with an MPLS-B-only remote site).Transit HSRP VLANs VLAN 64 . No additional router interfaces are required with this design modification because the 802. to provide a transit network for direct communication between the WAN routers.Figure 6 . 99) Active HSRP Router HSRP is configured to be active on the router with the highest priority WAN transport. There are no hosts connected to the transit network. and it is only used for router-router communication. the routers should connect via EtherChannel links to the distribution switch.Data VLAN 69 . and in the dual router design.1Q VLAN trunk configuration can easily accommodate an additional subinterface. These EtherChannel links are configured as 802. To implement this design. 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). This is more effective than simply monitoring the status of the WAN interface. 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. The routing protocol runs between router subinterfaces assigned to the transit network.Voice 2142 802.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 .1Q VLAN trunks. the standby HSRP router associated with the lower priority (alternate) WAN transport becomes the active HSRP router. This is referred to as hairpinning. The dual router designs also warrant an additional component that is required for proper routing in certain scenarios. In these cases. 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.

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

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

20. 12. 22 2 2 Operation. 30 3 3 Broadcast video CS5 40 4 4 Low-latency data AF21. 23 18. This table is included as a reference. 13 10. 42. 28.The QoS classifications in the following table are applied throughout this design. 43 34. 36. administration. 32. and maintenance (OAM) CS2 16 2 2 Bulk data AF11. Table 5 . 33 26. 38 4 4 Real-time interactive CS4 32 4 4 Multimedia streaming AF31. 12. 22. 14 1 1 Scavenger CS1 8 1 1 Default “best effort” DF 0 0 0 December 2013 14 .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.

The single WAN transport routing functions as follows. only encrypted traffic to other DMVPN sites is permitted to use the Internet link. Symmetric routing simplifies troubleshooting because bidirectional traffic flows always traverse the same links. a default route is advertised to the WAN remote sites in addition to the internal routes from the data center and campus. Deploying the WAN December 2013 15 . • Connects to any other site—The route is through the primary site. dual-link must be able tolerate the loss of either WAN transport. 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). for this design. dual-link must be able to tolerate the loss of either an edge router or a WAN transport. with traffic flowing along the same path in both directions. This model is referred to as a centralized Internet model. LAN Access All remote sites are to support both wired LAN access. 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. 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. It is worth noting that sites with Internet/DMVPN for backup transport could potentially provide local Internet capability. 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.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. there is no local Internet access for web browsing or cloud services. This type of configuration provides symmetric routing. The use of the dual WAN transports is specifically tuned to behave in an active/standby manner. • Remote sites classified as single-router. however. In the centralized Internet model. • Remote sites classified as dual-router.

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

20 Gbps. The most critical devices are the WAN routers that are responsible for reliable IP forwarding and QoS. Cisco ASR 1000 Series Aggregation Services Routers represent the next-generation. 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 router’s alignment with the suggested design model. The amount of bandwidth required at the WAN-aggregation site determines which model of router to use. and scaling. with the flexibility to support a wide range of 3. servicesintegrated Cisco routing platform. The Cisco ASR 1000 Series is fully modular from both hardware and software perspectives. and 36 Gbps • Cisco ASR 1002 router configured with an embedded service processor 5 (ESP5) • Cisco ASR 1001 router fixed configuration with a 2.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. Table 7 . and the routers have all the elements of a true carrier-class routing product that serves both enterprise and service-provider networks.5. modular. You should consider the following: the forwarding performance of the router using an Ethernet WAN deployment with broad services enabled. and the number of remote sites.5 Gbps embedded service processor • Cisco 3945 Integrated Services Router • Cisco 3925 Integrated Services Router All of the design models can be constructed using any of the MPLS CE routers listed in Table 7.WAN aggregation—MPLS CE router options Service Cisco 3925 Cisco 3945 ASR 1001 ASR 1002 ASR 1002-X Ethernet WAN with services 100 Mbps 150 Mbps 250 Mbps 500 Mbps 500Mbps-1. They are specifically designed for WAN aggregation.0 Gbps. 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.to 40-Gbps system bandwidth performance. 2.to 16-mpps (millions of packets per second) packet-forwarding capabilities.5Gbps Software Redundancy Option None None Yes Yes Yes Redundant power supply Option Option Default Default Default Supported Design Models All All All All All Suggested Design Model MPLS Static MPLS Static MPLS Dynamic Dual MPLS Dual MPLS Suggested Number of Remote Sites 25 50 100 250 250+ Deploying an MPLS WAN December 2013 17 .

However. 4. enough module slots.WAN remote-site Cisco Integrated Services Router options 881V1 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 4-port LAN switch) 0 0 0 0 0 0 0 On-board GE ports4 0 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 MPLS CE routers at the WAN remote sites connect in the same manner as the MPLS CE routers at the WAN-aggregation site. dual-link remote-site requires four router interfaces when using a port-channel to connect to an access or distribution layer. Cisco tested multiple integrated service router models as MPLS CE routers. You also need to make sure that you have enough interfaces.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 key to the initial deployment. Table 8 . 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. MPLS VPN-connected sites require static routing in order to be handled by the carrier. single-link remote sites with VoIP requirements. There are many factors to consider in the selection of the WAN remote-site routers. Among those. or you can use it to support a more complex LAN topology by connecting the CE router directly to a distribution layer. 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. single-link remote sites. The single link MPLS WAN remote site is the most basic of building blocks for any remote location. The 1941 is recommended for use at single-router. and any changes or modifications require a change request to the carrier. is the ability to process the expected amount and type of traffic. 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. and the expected performance is shown in the following table. Not all service modules are supported in Cisco 4451-X ISR. You can use this design with the CE router connected directly to the access layer. 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. The Cisco 881 Integrated Services Router is recommended for use at single-router. 2. Some service modules are double-wide. 3. 5. 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. 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. 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. Deploying an MPLS WAN December 2013 18 .

The router can automatically detect failure of the primary link and reroute traffic to the secondary path. Deploying an MPLS WAN December 2013 19 . Figure 10 . By adding an additional link. dual-link design continues to improve upon the level of high availability for the site. All devices use EtherChannel connections consisting of two port bundles. 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. You can accomplish additional forwarding performance by increasing the number of physical links within an EtherChannel. you provide the first level of high availability for the remote site. 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.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. Figure 9 .MPLS WAN remote site (single-router.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. This design provides both resiliency and additional forwarding performance. Design Details All WAN-aggregation MPLS CE routers connect to the same resilient switching device in the distribution layer.

The PE routers propagate the routing information within the carrier network and in turn re-advertise the routes back to other CE routers. MPLS VPNs require a link between a PE router and a CE router. and at every MPLS WAN-connected remote site. an MPLS CE router must be connected both to the distribution layer and to its respective MPLS carrier. you need to install and configure MPLS CE routers at every location. and their configurations are not included in this guide. BGP is most commonly used for this purpose. At the WAN-aggregation site. Other media types are commonly used (such as T1/E1). Figure 11 . The various CE routers advertise their routes to the PE routers. A static routing option is also included to support smaller scale requirements that do not require a dynamic routing protocol. The PE and CE routers are considered IP neighbors across this link. and interface type. The IP routing details for the single and dual MPLS carrier WAN-aggregation topology with dynamic routing are shown in the following figure.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. Due to the multiplicity of potential choices for transport. Multiple routing protocols (EIGRP and BGP) are used to exchange routing information. Deploying an MPLS WAN December 2013 20 . we decided to limit the focus of this design guide. The Dual MPLS and MPLS Dynamic designs use dynamic PE-CE routing with BGP. 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. CE routers are only able to communicate with other CE routers across the WAN via intermediate PE routers. 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). and can rely on static routing because there is only a single path to any destination. and the routing protocol configurations are tuned from their default settings to influence traffic flows to their desired behavior.WAN transport via Ethernet is the only media type tested and included in the configuration section. you typically need to use a routing protocol. media type. Sites with only a single WAN transport (a single-homed site) do not require dynamic PE-CE routing. Static routing is used in the MPLS Static design model. including the WAN-aggregation site. Cisco did not test the PE routers. but may not be universally available across all MPLS VPN carriers. Documentation of additional variants is available in other guides. To maintain this routing information. For an MPLS VPN WAN deployment. and these technologies are reliable and well understood. Tech Tip EIGRP and Open Shortest Path First (OSPF) Protocol are also effective as PE-CE routing protocols. This design recommends dynamic PE-CE routing to provide consistency with configurations across both single-homed and dual-homed sites.

and reduce convergence time associated with a link failure. EIGRP-100 is used 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. and memory necessary to carry large route tables. You should program IP summarization on links where logical boundaries exist. In this design.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. By performing IP summarization.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. such as distribution layer links to the wide area or to a core.Figure 12 . you can reduce the amount of bandwidth. has flexible summarization and filtering. and can scale to large networks. processor. Deploying an MPLS WAN December 2013 21 . does not require a large amount of planning. the number of IP prefixes or routes in the routing tables grows as well. EIGRP process 100 is the primary EIGRP process and is referred to as EIGRP-100. Figure 13 .

2/30 CE-ASR1001-2 10. BGP scales well and you can use it to advertise IP aggregate addresses for remote sites.4. Table 9 . Deployment Details The procedures in this section provide examples for some settings. we use a private ASN (65511) as designated by the Internet Assigned Numbers Authority (IANA).242/32 10. The private ASN range is 64512 to 65534.4. Redistribute WAN routes into EIGRP 6.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. Configure the WAN Aggregation Platform 3. Configure connectivity to the LAN 4.32. To use BGP. Configure the distribution switch 2.32.Parameters used in the deployment examples Hostname Loopback IP Address Port Channel IP Address CE-ASR1002-1 10. Configure BGP 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. Only the procedures required to support the integration of the WAN-aggregation router into the deployment are included.4.32. In this role.6/30 PROCESS Configuring the MPLS CE Router 1.241/32 10. you must select an Autonomous System Number (ASN). The actual settings and values that you use are determined by your current network configuration. In this design. Deploying an MPLS WAN December 2013 22 . Connect to MPLS PE router 5.32.4. A dual-carrier MPLS design requires an iBGP connection between the CE routers to properly retain routing information for the remote sites. BGP is straightforward to configure and requires little or no maintenance.

Step 1:  Configure the Layer 3 port-channel interface and assign the IP address.32. The number for the port-channel and channel-group must match. 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. router eigrp 100 no passive-interface Port-channel1 Deploying an MPLS WAN December 2013 23 . so you configure EtherChannel statically.255. Tech Tip As a best practice.255.The LAN distribution switch is the path to the organization’s main campus and data center.252 ip pim sparse-mode logging event link-status carrier-delay msec 0 no shutdown Step 2:  Configure EtherChannel member interfaces. A Layer 3 portchannel interface connects to the distribution switch to the WAN-aggregation router and the internal routing protocol peers across this interface. Not all router platforms can support Link Aggregation Control Protocol (LACP) to negotiate with the switch.1 255. interface Port-channel1 description CE-ASR1002-1 no switchport ip address 10. Configure the physical interfaces to tie to the logical port-channel by using the channel-group command. Also.4. GigabitEthernet2/0/1 no switchport macro apply EgressQoS carrier-delay msec 0 channel-group 1 mode on logging event link-status logging event trunk-status logging event bundle-status no shutdown Step 3:  Allow the routing protocol to form neighbor relationships across the port channel interface. use the same channel numbering on both sides of the link where possible. apply the egress QoS macro that was defined in the platform configuration procedure to ensure traffic is prioritized appropriately.

Step 4:  On the distribution layer switch, configure the layer 3 interface connected to the LAN core to summarize
the WAN network range.

Tech Tip
It is a best practice to summarize IP routes from the WAN distribution layer towards the
core.
interface Port-channel38
description Link to C6500-VSS
ip summary-address eigrp 100 10.4.32.0 255.255.248.0
ip summary-address eigrp 100 10.4.128.0 255.255.240.0
ip summary-address eigrp 100 10.4.160.0 255.255.252.0
ip summary-address eigrp 100 10.5.0.0 255.255.0.0
Step 5:  On the distribution layer switch, configure the layer 3 interfaces connected to the WAN aggregation
routers to summarize the WAN remote-site network range.

Tech Tip
It is a best practice to summarize IP routes from the WAN distribution layer towards the
MPLS WAN.
interface Port-channel1
description CE-ASR1002-1
ip summary-address eigrp 100 10.5.0.0 255.255.0.0
Repeat this step as needed for additional WAN aggregation routers.

Procedure 2

Configure the WAN Aggregation Platform

Within this design, there are features and services that are common across all WAN aggregation routers. These
are system settings that simplify and secure the management of the solution.
Step 1:  Configure the device host name. This makes it easy to identify the device.
hostname CE-ASR1002-1

Deploying an MPLS WAN

December 2013

24

Step 2:  Configure local login and password.
The local login account and password provides basic access authentication to a router, which provides only
limited operational privileges. The enable password secures access to the device configuration mode. By
enabling password encryption, you prevent the disclosure of plain text passwords when viewing configuration
files.
username admin password c1sco123
enable secret c1sco123
service password-encryption
aaa new-model
Step 3:  By default, HTTPS access to the router uses the enable password for authentication.
Step 4:  (Optional) Configure centralized user authentication.
As networks scale in the number of devices to maintain it poses an operational burden to maintain local user
accounts on every device. A centralized authentication, authorization, and accounting (AAA) service reduces
operational tasks per device and provides an audit log of user access for security compliance and root cause
analysis. When AAA is enabled for access control, all management access to the network infrastructure devices
(SSH and HTTPS) is controlled by AAA.
TACACS+ is the primary protocol used to authenticate management logins on the infrastructure devices to
the AAA server. 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.
tacacs server TACACS-SERVER-1
address ipv4 10.4.48.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.
Secure HTTP (HTTPS) and Secure Shell (SSH) are secure replacements for the HTTP and Telnet protocols. 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. Both
protocols are encrypted for privacy and the unsecure protocols, Telnet and HTTP, are turned off.

Deploying an MPLS WAN

December 2013

25

Specify the transport preferred none on vty lines to prevent errant connection attempts from the CLI prompt.
Without this command, if the ip name-server is unreachable, long timeout delays may occur for mistyped
commands.
ip domain-name cisco.local
ip ssh version 2
no ip http server
ip http secure-server
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, console log messages
are displayed on the console after interactive CLI output is displayed or printed. With this command, you can
continue typing at the device console when debugging is enabled.
line con 0
logging synchronous
Step 7:  Enable Simple Network Management Protocol (SNMP). This allows the network infrastructure devices
to be managed by a Network Management System (NMS). SNMPv2c is configured both for a read-only and a
read-write community string.
snmp-server community cisco RO
snmp-server community cisco123 RW
Step 8:  If operational support is centralized in your network, you can increase network security by using an
access list to limit the networks that can access your device. In this example, only devices on the 10.4.48.0/24
network will be able to access the device via SSH or SNMP.
access-list 55 permit 10.4.48.0 0.0.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.

Step 9:  Configure a synchronized clock.
The Network Time Protocol (NTP) is designed to synchronize a network of devices. An NTP network usually gets
its time from an authoritative time source, such as a radio clock or an atomic clock attached to a time server.
NTP then distributes this time across the organizations network.

Deploying an MPLS WAN

December 2013

26

48. EIGRP is configured facing the LAN distribution or core layer. Allocate the loopback address from the IP address block that the distribution switch summarizes to the rest of the network. In this design.4.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. either in a single network statement or in multiple network statements. The network range must include both interface IP addresses. Because of this capability. you can cross-reference events in a network.241 255.32.32.1. By configuring console messages. the port-channel interface and the loopback must be EIGRP interfaces.4. The loopback address is commonly a host address with a 32-bit address mask. SSH.4. and debug output to provide time stamps on output. TACACS+ and NTP to the loopback interface address. the loopback address is the best way to manage the switch in-band.0 0. router eigrp 100 network 10. 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.0.255 ip pim sparse-mode Step 11:  Bind the device processes for SNMP. 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.255.You should program network devices to synchronize to a local NTP server in the network. Deploying an MPLS WAN December 2013 27 . Using IP Multicast is much more efficient than using multiple individual unicast streams or a broadcast stream that would propagate everywhere. ntp server 10.255. The local NTP server typically references a more accurate clock feed from an outside source. logs. PIM.241 Step 13:  Configure IP Multicast routing. interface Loopback 0 ip address 10.255. The loopback may remain a passive interface. 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. This design uses a best practice of assigning the router ID to a loopback address.4. IP Telephony MOH and IP Video Broadcast Streaming are two examples of IP Multicast applications. Layer 3 process and features are also bound to the loopback interface to ensure process resiliency.255 no auto-summary passive-interface default eigrp router-id 10.

the distributed keyword is required.2 255.In order to receive a particular IP Multicast data stream. This design. ip pim autorp listener Step 15:  Enable sparse mode multicast operation for all Layer 3 interfaces in the network. 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 number for the port-channel and channel-group must match. 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. uses Auto RP for a simple yet scalable way to provide a highly resilient RP environment. ip multicast-routing distributed Step 14:  Configure every Layer 3 switch and router to discover the IP Multicast RP with autorp. ip multicast-routing If you are using a Cisco ASR 1000 Series router. Use the ip pim autorp listener command to allow for discovery across sparse mode links. interface Port-channel1 ip address 10.252 ip pim sparse-mode no shutdown Step 2:  Configure EtherChannel member interfaces. In a traditional IP Multicast design.32. 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. end hosts must join a multicast group by sending an IGMP message to their local multicast router.4. Step 1:  Configure Layer 3 interface. Not all router platforms can support LACP to negotiate with the switch. Enable IP Multicast routing on the platforms in the global configuration mode. GigabitEthernet0/0/1 no ip address channel-group 1 no shutdown Deploying an MPLS WAN December 2013 28 .255. Configure the physical interfaces to tie to the logical port-channel by using the channel-group command. so you configure EtherChannel statically.255. This configuration provides for future scaling and control of the IP Multicast environment and can change based on network needs and design. which is based on sparse mode multicast operation.

Or. or do not wish to have your MPLS carrier make changes or modifications. router eigrp 100 no passive-interface Port-channel1 Procedure 4 Connect to MPLS PE router Step 1:  Assign the interface bandwidth. This is the recommended approach. Allow EIGRP to form neighbor relationships across the interface to establish peering adjacencies and exchange route tables. The example shows a Gigabit interface (1000 Mbps) with a subrate of 300 Mbps. interface GigabitEthernet0/0/3 ip address 192. use the policed rate from the carrier. interface GigabitEthernet0/0/3 bandwidth 300000 Tech Tip Command reference: bandwidth kbps (300 Mbps = 300.255. if you are using a subrate service.252 is used.Step 3:  Configure the EIGRP interface. If you have a remote-site design that includes sites with dual WAN links.168. The IP addressing used between CE and PE routers must be negotiated with your MPLS carrier. The bandwidth value should correspond to the actual interface speed.1 255. then use the BGP option.000 kbps) Step 2:  Assign the IP address and netmask of the WAN interface.255. The MPLS carrier is responsible for configuring static IP routing within the MPLS network. We do not recommend the use of CDP on external interfaces. If your remote-site design only uses single WAN links and you don’t anticipate adding or modifying IP networks at the remote sites.252 Step 3:  Administratively enable the interface and disable CDP.255. Deploying an MPLS WAN December 2013 29 .255.3. Typically a pointto-point netmask of 255. 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. then you can use the statically routed option.

otherwise. only the bandwidth and delay values are used for metric calculation. An inbound distribute-list with a route-map is used to limit which routes are accepted for installation into the route table. Table 10 . It is important to tightly control how routing information is shared between different routing protocols when you use this configuration. you may need to block more tags. This design uses mutual route redistribution: BGP routes are distributed into EIGRP and EIGRP routes are distributed into BGP (covered inProcedure 6). you might experience route flapping. 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. Site-specific routing details must be shared with your MPLS carrier. The specific route tags in use are shown below. The WAN-aggregation MPLS CE routers are configured to only accept routes that do not originate from the MPLS or DMVPN WAN sources. Depending on the actual design of your network. To accomplish this task.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. Deploying an MPLS WAN December 2013 30 . router eigrp [as number] default-metric [bandwidth (Kbps)] [delay (usec)] 255 1 1500 redistribute bgp [BGP ASN] Step 2:  Configure route-map and inbound distribute-list for EIGRP.Tech Tip If you do not use dynamic routing with BGP. Option 1: BGP dynamic routing with MPLS carrier Step 1:  Redistribute BGP into EIGRP. By default. 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). A default metric redistributes the BGP routes into EIGRP. where certain routes are repeatedly installed and withdrawn from the device routing tables. you must create a route-map that matches any routes originating from the WAN indicated by a specific route tag. Proper route control ensures the stability of the routing table. 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. This method allows for dynamic identification of the various WAN routes.

route-map BLOCK-TAGGED-ROUTES deny 10 match tag 65401 65402 65512 ! route-map BLOCK-TAGGED-ROUTES permit 20 ! router eigrp 100 distribute-list route-map BLOCK-TAGGED-ROUTES in default-metric 100000 100 255 1 1500 redistribute bgp 65511 Option 2: Static routing with service provider Step 1:  Configure static routes to remote sites’ LANs on the WAN-aggregation CE router.255. It is a best practice to summarize the remote-site network ranges into a single route when possible. for troubleshooting.0. A default metric redistributes these routes into EIGRP. router eigrp [as number] default-metric [bandwidth (Kbps)] [delay (usec)] 255 1 1500 redistribute static Deploying an MPLS WAN December 2013 31 .3.2 Step 2:  It is desirable to advertise a route for the MPLS PE-CE links. tagging.0. It is a best practice to summarize the PE-CE link ranges into a single route when possible.5.0 255.3.168. A single summary route for the loopback range may be used when possible.3.168.255.0 192.3. By default.168.0 255.2 Step 4:  Configure EIGRP to advertise the remote-site static routes.0 192. which includes the CE routers’ WAN interfaces.0 192.255. which can cause instability.255. ip route 10. route-flapping may occur.255.255. and filtering. ip route 10. so you can use this to determine router reachability. only the bandwidth and delay values are used for metric calculation.0 255.Tech Tip If you configure mutual route redistribution without proper matching.2 Step 3:  Configure routes to the remote-site router loopback addresses.251.168. ip route 192.

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

dual-link design. Configure WAN routing 4. Configure remote-site DHCP 7. Deploying an MPLS WAN December 2013 33 . Connect router to access-layer switch 5. Configure the WAN Remote Router 2.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 the transit network 9. Configure access-layer routing 6. Configure access-layer HSRP 8. 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. Configure BGP 11. Connect to the MPLS PE Router PROCESS 3. Configure EIGRP (LAN side) 10. dual-link design or for configuring the first router of the dual-router.

Configure Transit Network Router 4. Configure EIGRP (LAN Side)) 11. Dual Link 1. Configure Access Layer Routing 6. Dual Link (1st Router) Remote-Site MPLS CE Router Single Router. Connect nnect Router to Access Layer Switch Remote-Site Router to Distribution Layer Procedures 1. Configure the WAN Remote Router 2. Single Link Remote-Site MPLS CE Router Configuration Procedures Remote-Site MPLS CE Router Dual Router. Connect to MPLS PE Router 3.Remote-site MPLS CE router configuration flowchart Remote-Site MPLS CE Router Single Router.The following flowchart provides details about the configuration process for a remote-site MPLS CE router. Connect to Distribution Layer 2. Configure Transit Network 3 8. Configure BGP for Dual Rout 9. Configure BGP for Dual Router December 2013 34 . Figure 14 . 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 WAN Routing Distribution Layer Design? NO YES 4. Configure Remote-Site DHCP (Optional) YES NO RP 7. Configure Access Layer HSRP 3. Configure EIGRP (LAN Side) NO Dual Router Design? YES Dual Router Design? 5.

Step 1:  Configure the device host name to make it easy to identify the device. Telnet and HTTP. you prevent the disclosure of plain text passwords when viewing configuration files. They use Secure Sockets Layer (SSL) and Transport Layer Security (TLS) to provide device authentication and data encryption. Deploying an MPLS WAN December 2013 35 . The local login account and password provides basic access authentication to a router that provides only limited operational privileges. A centralized authentication. hostname [hostname] Step 2:  Configure the local login and password. tacacs server TACACS-SERVER-1 address ipv4 10. and accounting (AAA) service reduces operational tasks per device and provides an audit log of user access for security compliance and root cause analysis. The enable password secures access to the device configuration mode. Both protocols are encrypted for privacy and the unsecure protocols. authorization. it can be 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 5:  Configure device management protocols. When AAA is enabled for access control. 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. Secure management of the network device is enabled through the use of the SSH and HTTPS protocols.4. 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. TACACS+ is the primary protocol used to authenticate management logins on the infrastructure devices to the AAA server. are turned off. there are features and services that are common across all WAN remote-site routers. As networks scale in the number of devices to maintain. https access to the router uses the enable password for authentication.48.Procedure 1 Configure the WAN Remote Router Within this design. Step 4:  (Optional) Configure centralized user authentication. By enabling password encryption. Secure HTTP (HTTPS) and Secure Shell (SSH) are secure replacements for the HTTP and Telnet protocols. all management access to the network infrastructure devices (SSH and HTTPS) is controlled by AAA.

line con 0 logging synchronous Step 7:  Enable Simple Network Management Protocol (SNMP). Deploying an MPLS WAN December 2013 36 .4. Configure SNMPv2c both for a read-only and a readwrite community string.48.0 0.0/24 network will be able to access the device via SSH or SNMP.48. if the ip name-server is unreachable. access-list 55 permit 10. Step 9:  Configure a synchronized clock. such as a radio clock or an atomic clock attached to a time server. With this command. NTP then distributes this time across the organization’s network. long timeout delays may occur for mistyped commands. snmp-server community cisco RO snmp-server community cisco123 RW Step 8:  If your network operational support is centralized. console log messages are displayed on the console after interactive CLI output is displayed or printed. The Network Time Protocol (NTP) is designed to synchronize a network of devices.Specify the transport preferred none on vty lines to prevent errant connection attempts from the CLI prompt. Without this command. ip domain-name cisco.local ip ssh version 2 no ip http server ip http secure-server line vty 0 15 transport input ssh transport preferred none Step 6:  Enable synchronous logging. An NTP network usually gets its time from an authoritative time source. When synchronous logging of unsolicited messages and debug output is turned on.0. you can increase network security by using an access list to limit the networks that can access your device.4. you can continue typing at the device console when debugging is enabled.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.0. In this example. This allows the network infrastructure devices to be managed by a Network Management System (NMS). only devices on the 10.

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. and debug output to provide time stamps on output. Because of this capability. ip multicast-routing Deploying an MPLS WAN December 2013 37 . the loopback address is the best way to manage the switch in-band. The loopback address is commonly a host address with a 32-bit address mask.255 ip pim sparse-mode Step 11:  Bind the device processes for SNMP.You should program network devices to synchronize to a local NTP server in the network.4. 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. SSH. logs. interface Loopback 0 ip address [ip address] 255. Auto RP is used to provide a simple yet scalable way to provide a highly resilient RP environment. Using IP Multicast is much more efficient than multiple individual unicast streams or a Broadcast stream that would propagate everywhere. end hosts must join a multicast group by sending an IGMP message to their local multicast router. In a traditional IP Multicast design. IP Telephony MOH and IP Video Broadcast Streaming are two examples of IP Multicast applications. In this design. ntp server 10. Enable IP Multicast routing on the platforms in the global configuration mode.255. you can cross-reference events in a network.48.255.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. To receive a particular IP Multicast data stream. By configuring console messages. Layer 3 process and features are also bound to the loopback interface to ensure process resiliency. 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. which is based on sparse mode multicast operation. 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. Allocate the loopback address from a unique network range that is not part of any other internal network summary range. The local NTP server typically references a more accurate clock feed from an outside source.

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

this configuration is considered an external BGP (eBGP) connection. use the BGP option. To complete this step. • The route is redistributed into BGP (not applicable in the remote-site use case). Option 1: BGP dynamic routing with MPLS carrier Step 1:  Enable BGP. router bgp 65511 no synchronization bgp router-id [IP address of Loopback0] bgp log-neighbor-changes no auto-summary Step 2:  Configure eBGP. then you can use the statically routed option. 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. 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. 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. so you should include this network in a network statement. Similarly. Configure BGP with the MPLS carrier PE device. Tech Tip If you do not use dynamic routing with BGP. Consult with your MPLS carrier on the requirements for the ASN. It is desirable to advertise a route for the PE-CE link. Deploying an MPLS WAN December 2013 39 . Site-specific routing details must be shared with your MPLS carrier. Because the carrier PE router uses a different ASN. you must configure BGP to advertise the loopback network for the router. If your remote-site design only uses single WAN links and you don’t anticipate adding or modifying IP networks at the remote site. You might be able to reuse the same value used on the MPLS VPN CE from the WAN-aggregation site. You can use this to determine router reachability. and assumes that the WAN-aggregation CE router has already been configured for BGP. This is the recommended approach. The MPLS carrier must provide their ASN (the ASN in the previous step is the ASN identifying your site). a BGP ASN is required. for troubleshooting.Procedure 3 Configure WAN routing The remote-site CE routers are configured either for dynamic routing with BGP or are statically routed.

Deploying an MPLS WAN December 2013 40 .8 mask 255.8.0 255.0 network 10. Tech Tip For each remote site with static routing.5.0.0 192. ip route 0. the aggregate is advertised to the MPLS PE.5.255.0 summary-only neighbor 192. which offers a measure of resiliency.251.255. This properly configures the static routes to the remote site. You must add a separate network statement for the loopback address.You must advertise the remote-site LAN networks.255.0 0.252 network 10.248.0.206 bgp log-neighbor-changes network 192.5.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.168.12.0.0 mask 255. router bgp 65511 network [PE-CE link network] mask [PE-CE link netmask] network [Loopback network] mask 255.0.255 network 10. If the various LAN networks cannot be summarized. you must list each individually.168.255.206 mask 255. provide the remote-site specific IP range and the chosen loopback IP address for the router.3.255.255.255. Step 1:  Enter a default route for traffic forwarded to the WAN-aggregation site.0 mask 255.255.255.0 aggregate-address 10.255.13. If any LAN network is present in the route table.255. 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 WAN-aggregation CE router must have a corresponding static host route for that site’s loopback address.255.255. The aggregate address configured below suppresses the more specific routes.10 Step 2:  For the MPLS carrier for each remote site.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.168.3.3.251.

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

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

interface FastEthernet0 switchport trunk native vlan 999 switchport trunk allowed vlan 1.2.1002-1005 switchport mode trunk no ip address no shutdown Tech Tip The embedded switch on the Cisco 881 Integrated Services Router requires that the default VLANs be allowed on trunks. which allows the router to provide the Layer 3 services to all the VLANs defined on the access-layer switch. vlan 64 name Wired-Data vlan 69 name Wired-Voice vlan 999 name Native Step 2:  Configure the remote-site router’s connection to the remote-site Ethernet switch. Prune the VLANs allowed on the trunk to only the VLANs that are active on the access-layer switch. these VLANs (1. Set DHCP Snooping and Address Resolution Protocol (ARP) inspection to trust.1Q trunk for the connection. Option 3: Layer 2 trunk from Cisco 881 router to access-layer switch This option uses a single Ethernet connection in order to connect the remote-site Cisco 881 Integrated Services Router to a single-member access switch.69 switchport mode trunk ip arp inspection trust spanning-tree portfast trunk macro apply EgressQoS logging event link-status logging event trunk-status ip dhcp snooping trust no shutdown The Cisco Catalyst 2960-S Series and 4500 Series switches do not require the switchport trunk encapsulation dot1q command. This option differs significantly from the previous options because an embedded Ethernet switch provides the LAN connectivity of the Cisco 881 router. and 1005) are pruned on the access-switch side of the trunk. 1004. interface GigabitEthernet1/0/24 description Link to RS201-2911 Gig0/2 switchport trunk encapsulation dot1q switchport trunk allowed vlan 64. 1002.Step 2:  Configure the trunk on the access-layer switch.69. To maintain security and configuration consistency.64. 1003. Step 1:  Configure necessary VLANs on the embedded switch of the remote-site router. Use an 802. Deploying an MPLS WAN December 2013 43 . 2.

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

255.255.0 ip helper-address 10.5.1 255.1 255. When using a centralized DHCP server.12.N.48.4.13.10 ip pim sparse-mode Example: Layer 2 EtherChannel interface Port-channel1 no ip address no shutdown ! interface Port-channel1.10 ip pim sparse-mode Deploying an MPLS WAN December 2013 45 .N.4. interface [VLAN number] description [usage] ip address [LAN network 1] [LAN network 1 netmask] ip helper-address 10. routers with LAN interfaces connected to a LAN using DHCP for endstation IP addressing must use an IP helper.255.69 description Voice encapsulation dot1Q 69 ip address 10.0 ip helper-address 10.48.64 description Data encapsulation dot1Q 64 ip address 10. This is the preferred method.1 255. This design uses an IP addressing convention with the default gateway router assigned an IP address and IP mask combination of N.N.10 ip pim sparse-mode ! interface Port-channel1.N is the IP network and 1 is the IP host.4.255.255.48.255.Option 2: Layer 2 trunk from Cisco 881 router to access-layer switch Step 1:  Configure IP settings for each subinterface.0 where N. An alternate option for local DHCP server configuration is shown in the following procedure.5.

4.13.5.48.255.255. If you choose to run a local DHCP server on the remote-site router instead of centralizing the DHCP service. complete this procedure.29.5.5.4. wireless access points. Deploying an MPLS WAN December 2013 46 .5.255.10 ip pim sparse-mode Example: Layer 2 Link from Cisco 881 ISR interface Vlan64 description Data ip address 10.255.10 ip pim sparse-mode ! interface GigabitEthernet0/2. users’ laptop and desktop computers.10 ip pim sparse-mode ! interface Vlan69 description Voice ip address 10.1 255.12. This procedure uses a local DHCP service on the router in order to assign basic network configuration for IP phones.0 ip helper-address 10.48.48.48.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.0 ip helper-address 10.255.1 255.28.69 description Voice encapsulation dot1Q 69 ip address 10. and other endpoint devices.255.4.Example: Layer 2 Link interface GigabitEthernet0/2 no ip address no shutdown ! interface GigabitEthernet0/2.0 ip helper-address 10.64 description Data encapsulation dot1Q 64 ip address 10.0 ip helper-address 10.255.255.1 255.1 255.4.

4.5.48.1 10.5.255.Tech Tip If you intend to use a dual-router remote-site design.5.4. complete this procedure. such as a centralized DHCP server.local dns-server 10.0 default-router 10.11. Options for resilient DHCP at the remotesite include using IOS on a distribution-layer switch stack or implementing a dedicated DHCP server solution. Different vendors use different option fields.255. Cisco uses DHCP option 150).0 default-router 10. excluding DHCP assignment for the first 19 addresses in the subnet.1 domain-name cisco. Step 2:  Configure a DHCP scope for data endpoints. you should use a resilient DHCP solution. excluding DHCP assignment for the first 19 addresses in the subnet.5.19 ip dhcp pool DHCP-Wired-Voice network 10. ip dhcp excluded-address 10.5.255. The HSRP active router is the MPLS CE router connected to the primary MPLS carrier.4.10 Procedure 7 through Procedure 11 are only relevant for the dual-router design.4.48.0 255. and the HSRP standby router is the router connected to the secondary MPLS carrier or backup link.1 domain-name cisco.5. Step 4:  Voice endpoints require an option field to tell them where to find their initial configuration.19 ip dhcp pool DHCP-Wired-Data network 10. Procedure 7 Configure access-layer HSRP If you are using a dual-router design. so the number may vary based on the voice product you choose (for example.1 10.local dns-server 10.0 255. Deploying an MPLS WAN December 2013 47 . ip dhcp excluded-address 10.4.5.10 Step 3:  Configure a DHCP scope for voice endpoints.4.255.11. 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.5.5. Step 1:  Remove the previously configured ip helper-address commands for any interface that uses a local DHCP server.

Tech Tip The HSRP priority and PIM DR priority are shown in the previous table to be the same value. The relevant HSRP parameters for the router configuration are shown in the following table. and it has no awareness of the HSRP configuration.3 105 105 The assigned IP addresses override those configured in the previous procedure. you are not required to use identical values.[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 Deploying an MPLS WAN December 2013 48 . The preempt option allows a router with a higher priority to become the HSRP active. In this design.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 . Table 11 . The PIM designated router (DR) should be on the HSRP active router. You can influence the PIM DR election by explicitly setting the DR priority on the LAN-facing subinterfaces for the routers.1 . so the default gateway IP address remains consistent across locations with single or dual routers. The DR is normally elected based on the highest IP address. The router with the higher standby priority value is elected as the HSRP active router. The dual-router access-layer design requires a modification for resilient multicast. without waiting for a scenario where there is no router in the HSRP active state. Step 1:  Configure HSRP.1 . interface [type][number]. you configure the HSRP active router with a standby priority that is higher than the HSRP standby router. assigning the HSRP active router a lower real IP address than the HSRP standby router requires a modification to the PIM configuration. however.2 110 110 MPLS CE (secondary) or DMVPN spoke Standby .In this procedure.

complete this procedure. Example: Layer 2 link interface GigabitEthernet0/2 no ip address no shutdown ! interface GigabitEthernet0/2.48.5. This network is used for router-router communication and to avoid hairpinning.10 ip pim dr-priority 110 ip pim sparse-mode standby version 2 standby 1 ip 10.13.255.0 ip helper-address 10.255.4.2 255.1 standby 1 priority 110 standby 1 preempt standby 1 authentication md5 key-string c1sco123 ! interface GigabitEthernet0/2. configure the transit network interface.5. Step 1:  On the primary MPLS CE router.12. The transit network should use an additional subinterface on the router interface that is already being used for data or voice.10 ip pim dr-priority 110 ip pim sparse-mode standby version 2 standby 1 ip 10.[sub-interface number] encapsulation dot1Q [dot1q VLAN tag] ip address [transit net address] [transit net netmask] ip pim sparse-mode Deploying an MPLS WAN December 2013 49 .48.5.12.69 description Voice encapsulation dot1Q 69 ip address 10.4. interface [type][number]. There are no end stations connected to this network.1 standby 1 priority 110 standby 1 preempt standby 1 authentication md5 key-string c1sco123 Procedure 8 Configure the transit network If you are using a dual-router design.2 255.255.64 description Data encapsulation dot1Q 64 ip address 10.13.0 ip helper-address 10. The transit network is configured between the two routers.255.Step 2:  Repeat this procedure for all data or voice subinterfaces.5. so HSRP and DHCP are not required.

All interfaces except the transit-network subinterface should remain passive. A default metric redistributes the BGP routes into EIGRP. This design uses a best practice of assigning the router ID to a loopback address. In this design.1 255.255. router eigrp 100 network [network] [inverse mask] passive-interface default no passive-interface [Transit interface] eigrp router-id [IP address of Loopback0] no auto-summary Step 2:  Redistribute BGP into EIGRP-100. add the transit network VLAN. all LAN-facing interfaces and the loopback must be EIGRP interfaces. interface GigabitEthernet1/0/24 switchport trunk allowed vlan add 99 Procedure 9 Configure EIGRP (LAN side) If you are using a dual-router design.8.252 ip pim sparse-mode Step 2:  On the access-layer switch. The network range must include all interface IP addresses either in a single network statement or in multiple network statements.5.Example interface GigabitEthernet0/2. By default. vlan 99 name Transit-net Step 3:  Add the transit network VLAN to the existing access-layer switch trunk.255. 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. You must configure a routing protocol between the two routers. complete this procedure. Step 1:  Enable EIGRP-100 facing the access layer. router eigrp 100 default-metric [WAN bandwidth] [WAN delay] 255 1 1500 redistribute bgp 65511 Deploying an MPLS WAN December 2013 50 . only the WAN bandwidth and delay values are used for metric calculation.99 description Transit Net encapsulation dot1Q 99 ip address 10.

which requires the next-hop-self-configuration option. Example router eigrp 100 default-metric 100000 100 255 1 1500 network 10.0. The dual-carrier MPLS design requires that a BGP link is configured between the CE routers.1.0.255.255.0.206 no auto-summary Procedure 10 Configure BGP If you are using a dual-router design.255.0 0.255 network 10. complete this procedure. router bgp 65511 neighbor [iBGP neighbor Transit Net IP] remote-as 65511 neighbor [iBGP neighbor Transit Net IP] next-hop-self Deploying an MPLS WAN December 2013 51 . configure iBGP and enable the next-hop-self configuration option. This design uses iBGP peering using the transit network. Because the CE routers are using the same ASN.255 redistribute bgp 65511 passive-interface default no passive-interface GigabitEthernet0/2.255.99 eigrp router-id 10. Note. the iBGP session will not be established until you complete the transit network and EIGRP (LAN-side) steps.251.4. You must complete this step on both remote-site MPLS CE routers.0 0. Step 1:  On both remote-site MPLS CE routers. this configuration is considered an internal BGP (iBGP) connection.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.

remote sites will advertise themselves as a transit autonomous system. when a link to a MPLS hub has failed. 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. BGP readvertises all BGP-learned routes. it is a best practice to disable the site from becoming a transit site.Step 2:  Configure BGP to prevent the remote site from becoming a transit AS. The MPLS dual-carrier design in many cases provides two equal cost paths. Step 3:  Tune BGP routing to prefer the primary MPLS carrier. with a high bandwidth connection. You must use a route-map and an as-path access-list filter. 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. and it is likely that the first path selected will remain the active path unless the routing protocol detects a failure. 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 an MPLS WAN December 2013 52 . This requires the use of a route-map and an as-path access-list filter. In the dual-MPLS design. By default. providing access between the two carriers. this means that MPLS-A routes will be advertised to MPLS-B and vice-versa. Unless the remote site has been specifically designed for this type of routing behavior. Each router will apply this outbound to the neighbor for its respective MPLS carrier. In certain cases. 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. You need to apply this route-map on both remote-site MPLS CE routers. Accomplishing the design goal of deterministic routing and primary/secondary routing behavior necessitates tuning BGP. This type of filter allows for only the locally originated routes to be advertised.

and if the PE router becomes unreachable. and then send standard ICMP echo (ping) probes at 15-second intervals.Tech Tip The regular expression _65401$ corresponds to routes originated from the AS 65401 (MPLS-A). if it fails.255 Procedure 11 Enable Enhanced Object Tracking If you are using a dual-router design. If you are using the MPLS PE router as the probe destination. complete this procedure. the destination address is the same as the BGP neighbor address configured in Procedure 3. If the primary MPLS VPN transport were to fail. the tracked object status is Up. Having the HSRP router remain as the active router can lead to undesired behavior. This procedure is valid only on the router connected to the primary transport (MPLS VPN). If the probe is successful. the BGP local preference is 200 for the primary MPLS carrier. router bgp 65511 network [Secondary router loopback network] mask 255.255. Step 5:  Add a loopback network for the secondary router. Responses must be received before the timeout of 1000 ms expires. This is sub-optimal routing. and you can address it by using EOT. the tracked object status is Down. then the router can lower its HSRP priority. track 50 ip sla 100 reachability Deploying an MPLS WAN December 2013 53 . so that the HSRP standby router can preempt and become the HSRP active router. The object being tracked is the reachability success or failure of the probe. This allows BGP to selectively modify the routing information for routes originated from this AS. 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. Step 1:  Enable the IP SLA probe.255. In this example. Routes originated from the secondary MPLS carrier continue to use their default local preference of 100. 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. The HSRP active router remains the active router unless the router is reloaded or fails. The HSRP active router (primary MPLS CE) can use the IP SLA feature to send echo probes to its MPLS PE router.

single-link) has already been completed and BGP dynamic routing has been configured. dual-link). interface [interface type] [number]. the HSRP priority is decremented by the configured priority. HSRP can monitor the tracked object status. If the decrease is large enough.Step 3:  Link HSRP with the tracked object. All data or voice subinterfaces should enable HSRP tracking. the HSRP standby router preempts. The following procedures assume that the configuration of an MPLS CE router for an MPLS WAN remote site (single-router. Deploying an MPLS WAN December 2013 54 . Only the additional procedures to add an additional MPLS link to the running MPLS CE router are included here.[sub-interface number] standby 1 track 50 decrement 10 Example PROCESS interface GigabitEthernet 0/2.64 standby 1 track 50 decrement 10 interface GigabitEthernet 0/2. If the status is down.69 standby 1 track 50 decrement 10 ! track 50 ip sla 100 reachability ! ip sla 100 icmp-echo 192. Connect to MPLS PE router 2.3.10 source-interface GigabitEthernet0/0 timeout 1000 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. 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.168.

Configure BGP for Dual-link link Site Complete Procedure 1 2130 NO Connect to MPLS PE router This procedure applies to the interface used to connect the secondary or additional MPLS carrier.The following figure provides details on how to add a second MPLS backup link on an existing remote-site MPLS CE router. Figure 15 . interface [interface type] [number] bandwidth [bandwidth (kbps)] Deploying an MPLS WAN December 2013 55 . The example shows a Gigabit interface (1000 Mbps) with a subrate of 10 Mbps. Connect to MPLS PE Router uter 2. use the policed rate from the carrier. If you are using a subrate service.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. Step 1:  Assign an interface bandwidth value that corresponds to the actual interface speed.

so you should include this network in a network statement.252 ip pim sparse-mode no cdp enable no shutdown Procedure 2 Configure BGP for dual-link design Step 1:  Configure eBGP to add an additional eBGP neighbor and advertise the PE-CE link. It is desirable to advertise a route for the PE-CE link.Tech Tip Command Reference: bandwidth kbps 10 Mbps = 10.000 kbps Step 2:  Assign the IP address and netmask of the WAN interface. The remote-site LAN networks are already advertised based on the configuration already completed in the “Configuring the Remote-Site MPLS CE Router” process.13 255. interface [interface type] [number] no cdp enable no shutdown Example interface GigabitEthernet0/1 bandwidth 10000 ip address 192. interface [interface type] [number] ip address [IP address] [netmask] Step 3:  Administratively enable the interface and disable Cisco Discovery Protocol. The IP addressing used between CE and PE routers must be negotiated with your MPLS carrier.168. 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] Deploying an MPLS WAN December 2013 56 . for troubleshooting.4. Typically.255. It is not recommended that you use the Cisco Discovery Protocol on external interfaces. this configuration is considered an external BGP (eBGP) connection. Because the carrier PE router uses a different ASN.252 is used. a point-to-point netmask of 255. You can use it to determine router reachability.255. BGP must be configured with the MPLS carrier PE device. The MPLS carrier must provide their ASN (the ASN in this step is the ASN identifying your site).255.255.

This requires the use of a route-map and an as-path access-list filter. In the dual-MPLS design. you need to use a route-map and an as-path access-list filter. and it is likely that the first path selected will remain the active path unless the routing protocol detects a failure. 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. BGP readvertises all BGP-learned routes. this means that MPLS-A routes are advertised to MPLS-B and vice-versa. Unless the remote site has been specifically designed for this type of routing behavior. The MPLS dual-carrier design in many cases provides two equal cost paths. By default. Accomplishing the design goal of deterministic routing and primary/secondary routing behavior necessitates tuning BGP. This type of filter allows for only the locally originated routes to be advertised. when a link to a MPLS hub has failed. In certain cases. 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. Step 3:  Tune BGP routing to prefer the primary MPLS carrier. it is a best practice to disable the site from becoming a transit site.Step 2:  Configure BGP to prevent the remote site from becoming a transit AS. providing access between the two carriers. remote sites will advertise themselves as a transit autonomous system. with a high bandwidth connection. 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 an MPLS WAN December 2013 57 . Apply this route-map outbound to the neighbors for both MPLS carriers. To do this. 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.

14 route-map NO-TRANSIT-AS out neighbor 192.255.3. Routes originated from the secondary MPLS carrier continue to use their default local preference of 100.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 December 2013 58 .4.168.168. This allows BGP to selectively modify the routing information for routes originated from this AS.168. Example router bgp 65511 network 192.14 remote-as 65402 neighbor 192.4.Tech Tip The regular expression _65401$ corresponds to routes originated from the AS 65401 (MPLS-A).14 route-map PREFER-MPLS-A in neighbor 192. the BGP local preference is 200 for the primary MPLS carrier. In this example.3. Apply this route-map inbound to the neighbor for the primary MPLS carrier only.252 neighbor 192.168.12 mask 255.255.4.168.

Configure the WAN remote router 2. Configure the transit network 8. complete this procedure in order to configure the secondary router in the MPLS WAN remote site. Configure EIGRP (LAN Side) If you are using a dual-router. Configure access-layer routing 6.Configuring the Secondary Remote-Site Router PROCESS 1. dual-link design. Configure access-layer HSRP 7. Deploying an MPLS WAN December 2013 59 . Connect router to access-layer switch 5. Connect to the MPLS PE router 3. Configure WAN routing 4.

Step 1:  Configure the device host name. Configure Transit Network Site Complete Procedure 1 Site Complete 2131 8 gu e EIGRP G ((LAN Side) S de) 8. hostname [hostname] Deploying an MPLS WAN December 2013 60 . This makes it easy to identify the device.The following flowchart provides details about how to configure a secondary remote-site MPLS CE router. Configure Access Layer Routing 2. Connect Router to Access 1 t to Distribution Layer 1. there are features and services that are common across all WAN remote-site routers. Configure the WAN Remote Router 2. Configure Access Layer HSRP 7. Dual Link (2nd Router) Remote-Site Router (Dual Router . Configure WAN Routing NO O Distribution Layer Design? YES Y Remote-Site Router to Distribution Layer (Router 2) ccess Layer Switch 4. Figure 16 . Configure EIGRP (LAN Side) 6.Remote-site MPLS CE router 2 configuration flowchart Remote-Site MPLS CE Router Dual Router. Connect to MPLS PE Router 3. Co Configure Configure the WAN remote router Within this design. These are system settings that simplify and secure the management of the solution. C Connectt R Router 5.Router 2) Configuration Procedures 1.

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. are turned off. Deploying an MPLS WAN December 2013 61 . all management access to the network infrastructure devices (SSH and HTTPS) is controlled by AAA. They use Secure Sockets Layer (SSL) and Transport Layer Security (TLS) to provide device authentication and data encryption. Secure HTTP (HTTPS) and Secure Shell (SSH) are secure replacements for the HTTP and Telnet protocols. Secure management of the network device is enabled through the use of the SSH and HTTPS protocols. you prevent the disclosure of plain text passwords when viewing configuration files. HTTPS access to the router uses the enable password for authentication. The enable password secures access to the device configuration mode. The local login account and password provides basic access authentication to a router. TACACS+ is the primary protocol used to authenticate management logins on the infrastructure devices to the AAA server. A centralized authentication. authorization.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. When AAA is enabled for access control. tacacs server TACACS-SERVER-1 address ipv4 10. By enabling password encryption. and the unsecure protocols.Step 2:  Configure local login and password. Both protocols are encrypted for privacy. username admin password c1sco123 enable secret c1sco123 service password-encryption aaa new-model By default. and accounting (AAA) service reduces operational tasks per device and provides an audit log of user access for security compliance and root cause analysis. Telnet and HTTP. Step 3:  (Optional) Configure centralized user authentication.4.48. As networks scale in the number of devices to maintain it poses an operational burden to maintain local user accounts on every device. and this access provides only limited operational privileges.

48.4. only devices on the 10. NTP then distributes this time across the organizations network. In this example.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). Step 8:  Configure a synchronized clock. line con 0 logging synchronous Step 6:  Enable Simple Network Management Protocol (SNMP). An NTP network usually gets its time from an authoritative time source. you can increase network security by using an access list to limit the networks that can access your device. long timeout delays may occur for mistyped commands. With this command. Without this command. such as a radio clock or an atomic clock attached to a time server. access-list 55 permit 10. When synchronous logging of unsolicited messages and debug output is turned on.0 0.0. SNMPv2c is configured both for a read-only and a read-write community string. The Network Time Protocol (NTP) is designed to synchronize a network of devices.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.48. snmp-server community cisco RO snmp-server community cisco123 RW Step 7:  If operational support is centralized in your network. if the ip name-server is unreachable. ip domain-name cisco. Deploying an MPLS WAN December 2013 62 . console log messages are displayed on the console after interactive CLI output is displayed or printed.4.0.local ip ssh version 2 no ip http server ip http secure-server line vty 0 15 transport input ssh transport preferred none Step 5:  Enable synchronous logging.Specify the transport preferred none on vty lines to prevent errant connection attempts from the CLI prompt. you can continue typing at the device console when debugging is enabled.

end hosts must join a multicast group by sending an IGMP message to their local multicast router. Auto RP is used to provide a simple yet scalable way to provide a highly resilient RP environment. ntp server 10. To receive a particular IP Multicast data stream.255. 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. The local NTP server typically references a more accurate clock feed from an outside source. By configuring console messages. Allocate the loopback address from a unique network range that is not part of any other internal network summary range. Because of this capability. Layer 3 process and features are also bound to the loopback interface to ensure process resiliency. SSH. logs. Enable IP Multicast routing on the platforms in the global configuration mode.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.255 ip pim sparse-mode Bind the device processes for SNMP. 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. 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. you can cross-reference events in a network. ip multicast-routing Deploying an MPLS WAN December 2013 63 . In this design. In a traditional IP Multicast design. interface Loopback 0 ip address [ip address] 255. TACACS+ and NTP to the loopback interface address for optimal resiliency. the loopback address is the best way to manage the switch in-band. and debug output to provide time stamps on output. which is based on sparse mode multicast operation.255. IP Telephony MOH and IP Video Broadcast Streaming are two examples of IP Multicast applications. PIM.48.4.You should program network devices to synchronize to a local NTP server in the network. 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. Using IP Multicast is much more efficient than multiple individual unicast streams or a Broadcast stream that would propagate everywhere. The loopback address is commonly a host address with a 32-bit address mask.

interface [interface type] [number] bandwidth [bandwidth (kbps)] Tech Tip Command Reference: bandwidth kbps 10 Mbps = 10. This configuration provides for future scaling and control of the IP Multicast environment and can change based on network needs and design.4.255.252 no cdp enable no shutdown Deploying an MPLS WAN December 2013 64 . You must negotiate the IP addressing used between CE and PE routers with your MPLS carrier. It is not recommend that you use Cisco Discovery Protocol on external interfaces.9 255. Typically.255.000 kbps Step 2:  Assign the IP address and netmask of the WAN interface. use the policed rate from the carrier. If you are using a subrate service.255.Step 11:  Configure every Layer 3 switch and router to discover the IP Multicast RP with autorp. interface [interface type] [number] ip address [IP address] [netmask] Step 3:  Administratively enable the interface and disable Cisco Discovery Protocol. 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. a pointto-point netmask of 255.252 is used. 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 25000 ip address 192. The example shows a Gigabit interface (1000 Mbps) with a subrate of 10 Mbps.168.255. ip pim autorp listener Step 12:  Enable sparse mode multicast operation for all Layer 3 interfaces in the network.

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

You must use a route-map and an as-path access-list filter. the iBGP session will not be established until you complete the transit network and EIGRP (LAN side) steps. providing access between the two carriers.4.4.255.255.8.255.255.255. when a link to an MPLS hub has failed. You need to apply this route map on both remote-site MPLS CE routers.5.0 summary-only neighbor 10.206 bgp log-neighbor-changes network 192.5. this configuration is considered an internal BGP (iBGP) connection.4.248.255.8 mask 255.255. with a high bandwidth connection.252.5.206 mask 255.168.Step 3:  Configure iBGP between the remote-site MPLS CE routers.13.0 255.255.0 mask 255.255.8.255 network 10.0 aggregate-address 10.255. This type of filter allows for only the locally originated routes to be advertised.10 remote-as 65402 neighbor 192. In the dual-MPLS design.12. 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. Because the CE routers are using the same ASN. Each router applies this route map outbound to the neighbor for its respective MPLS carrier.8. Unless the remote site has been specifically designed for this type of routing behavior.1 next-hop-self neighbor 192. this means that MPLS-A routes will be advertised to MPLS-B and vice-versa.251.255. The dual-carrier MPLS design requires that a BGP link is configured between the CE routers.168.5. Example: MPLS CE Router (secondary) router bgp 65511 no synchronization bgp router-id 10.255. Note. 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. By default.255 network 10. it is a best practice to disable the site from becoming a transit site.10 route-map NO-TRANSIT-AS out no auto-summary ! Deploying an MPLS WAN December 2013 66 .252.5. remote sites will advertise themselves as a transit autonomous system.206 mask 255.1 remote-as 65511 neighbor 10.255.255.0 network 10.168.252 network 10. BGP readvertises all BGP learned routes.0 mask 255. In certain cases.

interface Port-channel2 description EtherChannel link to RS206-A2960S no shutdown Step 2:  Configure EtherChannel member interfaces on the router. For complete access-layer configuration details. If the access-layer device is a single. a simple Layer 2 trunk between the router and switch is used. the remote sites use collapsed routing. interface GigabitEthernet0/1 description RS206-A2960S Gig1/0/23 ! interface GigabitEthernet0/2 description RS206-A2960S Gig2/0/23 ! interface range GigabitEthernet0/1. so you configure EtherChannel statically. see the Campus Wired LAN Technology Design Guide. with 802. If you are using a remote-site distribution layer. Layer 2 EtherChannels are used to interconnect the CE router to the access layer in the most resilient method possible. 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. then skip to the “Deploying a WAN Remote-Site Distribution Layer” chapter of this guide.1Q trunk interfaces to the LAN access layer. In the access-layer design. GigabitEthernet0/2 no ip address channel-group 2 no shutdown Deploying an MPLS WAN December 2013 67 . Not all router platforms can support LACP to negotiate with the switch. The VLAN numbering is locally significant only. Option 1: Layer 2 EtherChannel from router to access-layer switch Step 1:  Configure a port-channel interface on the router. fixed-configuration switch.ip as-path access-list 10 permit ^$ ! 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.

and the number must match the channel group configured in Step 2. so you configure EtherChannel statically.1Q trunk for the connections. Not all connected router platforms can support LACP to negotiate with the switch.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. When using EtherChannel. The physical interfaces that are members of a Layer 2 EtherChannel are configured prior to configuring the logical port-channel interface. 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. Use an 802.99 switchport mode trunk ip arp inspection trust spanning-tree portfast trunk ip dhcp snooping trust no shutdown The Cisco Catalyst 2960-S Series and 4500 Series switches do not require the switchport trunk encapsulation dot1q command. Deploying an MPLS WAN December 2013 68 . This allows the router to provide the Layer 3 services to all the VLANs defined on the access-layer switch. Set DHCP Snooping and Address Resolution Protocol (ARP) inspection to trust. 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. interface Port-channel2 description EtherChannel link to RS206-3925-2 switchport trunk encapsulation dot1q switchport trunk allowed vlan 64. Configure two or more physical interfaces to be members of the EtherChannel. Also.69. 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. to separate redundant modules for additional resiliency. or in the case of the Cisco Catalyst 4507R+E distribution layer. the interface type is port-channel. apply the egress QoS macro that was defined in the platform configuration procedure in order to ensure traffic is prioritized appropriately. It is recommended that they are added in multiples of two. Prune the VLANs allowed on the trunk to only the VLANs that are active on the access-layer switch.

255.N. 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.N is the IP network and 1 is the IP host. Step 1:  Create subinterfaces and assign VLAN tags.1 255. interface GigabitEthernet1/0/23 description Link to RS206-3925-2 Gig0/2 switchport trunk encapsulation dot1q switchport trunk allowed vlan 64.255. Procedure 5 Configure access-layer routing This remote-site MPLS CE router is the second router of a dual-router design.N. but making them the same simplifies the overall configuration.0 where N. Use an 802. This allows the router to provide the Layer 3 services to all the VLANs defined on the access-layer switch.Option 2: Layer 2 trunk from router to access-layer switch Step 1:  Enable the physical interface on the router.[sub-interface number] encapsulation dot1Q [dot1q VLAN tag] Step 2:  Repeat the subinterface portion of the previous step for all data or voice VLANs. After the physical interface or port-channel has been enabled.1Q tag. interface GigabitEthernet0/2 description RS206-A2960S Gig1/0/23 no ip address no shutdown Step 2:  Configure the trunk on the access-layer switch. The actual interface IP assignments are configured in the following procedure.1Q trunk for the connection.99 switchport mode trunk ip arp inspection trust spanning-tree portfast trunk macro apply EgressQoS logging event link-status logging event trunk-status ip dhcp snooping trust no shutdown The Cisco Catalyst 2960-S Series and 4500 Series switches do not require the switchport trunk encapsulation dot1q command. interface [type][number]. Deploying an MPLS WAN December 2013 69 . Prune the VLANs allowed on the trunk to only the VLANs that are active on the access-layer switch. The subinterface number does not need to equate to the 802. Step 3:  Configure IP settings for each subinterface.69.N. and HSRP is configured at the access layer. and then set DHCP Snooping and Address Resolution Protocol (ARP) inspection to trust.

10 ip pim sparse-mode Deploying an MPLS WAN December 2013 70 .69 description Voice encapsulation dot1Q 69 ip helper-address 10. routers with LAN interfaces connected to a LAN using DHCP for endstation IP addressing must use an IP helper.48.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. The actual interface IP assignments will be configured in the following procedure.48.4.4.10 ip pim sparse-mode Example: Layer 2 Trunk interface GigabitEthernet0/2 no ip address no shutdown ! interface GigabitEthernet0/2.4.48.[sub-interface number] description [usage] ip helper-address 10.When using a centralized DHCP server. This remote-site MPLS CE router is the second router of a dual-router design and HSRP is configured at the access layer.69 description Voice encapsulation dot1Q 69 ip helper-address 10.64 description Data encapsulation dot1Q 64 ip helper-address 10. interface [type][number].48.10 ip pim sparse-mode ! interface GigabitEthernet0/2.64 description Data encapsulation dot1Q 64 ip helper-address 10.48.10 ip pim sparse-mode ! interface Port-channel2.4.

In this procedure. 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. The relevant HSRP parameters for the router configuration are shown in the following table. assigning the HSRP active router a lower real IP address than the HSRP standby router requires a modification to the PIM configuration.Procedure 6 Configure access-layer HSRP Configure HSRP to use a virtual IP (VIP) as a default gateway that is shared between two routers. you are not required to use identical values. Tech Tip The HSRP priority and PIM DR priority are shown in the previous table to be the same value. The router with the higher standby priority value is elected as the HSRP active router. Example: MPLS CE Router (Secondary) with Layer 2 EtherChannel interface Port-channel2 no ip address no shutdown ! Deploying an MPLS WAN December 2013 71 . you configure the HSRP active router with a standby priority that is higher than the HSRP standby router.1 .3 105 105 The dual-router access-layer design requires a modification for resilient multicast. and it has no awareness of the HSRP configuration. and the HSRP standby router is the router connected to the secondary MPLS carrier or backup link.2 110 110 MPLS CE (secondary) or DMVPN Spoke Standby .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 preempt option allows a router with a higher priority to become the HSRP active. The HSRP active router is the MPLS CE router connected to the primary MPLS carrier. In this design.1 . Step 1:  Configure HSRP. without waiting for a scenario where there is no router in the HSRP active state.[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 Step 2:  Repeat this procedure for all data or voice subinterfaces. The PIM designated router (DR) should be on the HSRP active router. Table 12 . interface [type][number]. however.

5.12.5.5.10 ip pim dr-priority 105 ip pim sparse-mode standby version 2 standby 1 ip 10.4.48.64 description Data encapsulation dot1Q 64 ip address 10.13.255.13.3 255.interface Port-channel2.12.48.4.3 255.5.0 ip helper-address 10.255.3 255.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.10 ip pim dr-priority 105 ip pim sparse-mode standby version 2 standby 1 ip 10.69 description Voice encapsulation dot1Q 69 ip address 10.69 description Voice encapsulation dot1Q 69 Deploying an MPLS WAN December 2013 72 .0 ip helper-address 10.1 standby 1 priority 105 standby 1 preempt standby 1 authentication md5 key-string c1sco123 ! interface Port-channel2.12.255.255.5.1 standby 1 priority 105 standby 1 preempt standby 1 authentication md5 key-string c1sco123 ! interface GigabitEthernet0/2.48.12.5.255.0 ip helper-address 10.4.255.10 ip pim dr-priority 105 ip pim sparse-mode standby version 2 standby 1 ip 10.64 description Data encapsulation dot1Q 64 ip address 10.

10 ip pim dr-priority 105 ip pim sparse-mode standby version 2 standby 1 ip 10.4.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. This ensures that the HSRP active router has full reachability information for all WAN remote sites.2 255. The transit network should use an additional subinterface on the router interface that is already being used for data or voice.13.5. All interfaces except the transit-network subinterface should remain passive.8. all LAN-facing interfaces and the loopback must be EIGRP interfaces. This design uses a best practice of assigning the router ID to a loopback address.ip address 10. so HSRP and DHCP are not required. Step 1:  On the secondary MPLS CE router.5.255.0 ip helper-address 10.13.99 description Transit Net encapsulation dot1Q 99 ip address 10.252 ip pim sparse-mode Procedure 8 Configure EIGRP (LAN Side) You must configure a routing protocol between the two routers. In this design. There are no end stations connected to this network.[sub-interface number] encapsulation dot1Q [dot1q VLAN tag] ip address [transit net address] [transit net netmask] ip pim sparse-mode Example interface GigabitEthernet0/2. router eigrp 100 network [network] [inverse mask] passive-interface default no passive-interface [Transit interface] eigrp router-id [IP address of Loopback0] no auto-summary Deploying an MPLS WAN December 2013 73 . Do not include the WAN interface (MPLS PE-CE link interface) as an EIGRP interface.255.3 255. You use this network for router-router communication and to avoid hairpinning.5. interface [interface type][number].255. configure the transit network interface. The network range must include all interface IP addresses either in a single network statement or in multiple network statements.255. Step 1:  Enable EIGRP-100 facing the access layer.

Example router eigrp 100 default-metric 100000 100 255 1 1500 network 10. By default.0. A default metric redistributes the BGP routes into EIGRP.Step 2:  Redistribute BGP into EIGRP-100.1. router eigrp 100 default-metric [WAN bandwidth] [WAN delay] 255 1 1500 redistribute bgp 65511 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.255 redistribute bgp 65511 passive-interface default no passive-interface GigabitEthernet0/2. only the WAN bandwidth and delay values are used for metric calculation.4.252.255.99 eigrp router-id 10.255.206 no auto-summary Deploying an MPLS WAN December 2013 74 .0 0.

complete this process.Router 1 Link Deploying a WAN Remote-Site Distribution Layer 802. single link design or a dual-router. 99) 802. 69) VLAN 50 .WAN remote site—Connection to distribution layer WAN WAN R1 802. Figure 17 . Connect router to distribution layer 2.Transit December 2013 2185 R1 75 . 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.1Q Trunk (xx-xx) VLAN 50 .1Q Trunk (50.Router 1 Link VLAN 54 .1Q Trunk (64.1Q Trunk (xx-xx) R2 802.Deploying a WAN Remote-Site Distribution Layer PROCESS Deployment Details Connecting the Single or Primary Remote-Site Router to the Distribution Layer 1. Configure BGP If you are configuring an MPLS WAN remote-site that uses a single-router. Configure EIGRP (LAN side) 3. Both distribution-layer remote-site options are shown in the following figure. dual-link design. 99) 802.1Q Trunk (54. Configure the transit network 4.Router 2 Link VLAN 99 .1Q Trunk (50) 802.

see the Campus Wired LAN Technology Design Guide. The number for the port-channel and channel-group must match. After you have enabled the interface. Not all router platforms can support LACP to negotiate with the switch. map the appropriate subinterfaces to the VLANs on the distributionlayer switch. The subinterface configured on the router corresponds to a VLAN interface on the distribution-layer switch. interface Port-channel1 description EtherChannel link to RS200-D3750X no shutdown Step 2:  Configure the port channel subinterfaces and assign IP addresses. This connection allows for multiple VLANs to be included on the EtherChannel if necessary. configure EtherChannel member interfaces.5. GigabitEthernet0/2 no ip address channel-group 1 no shutdown Deploying a WAN Remote-Site Distribution Layer December 2013 76 . Traffic is routed between the devices with the VLAN acting as a point-to-point link. Configure the physical interfaces to tie to the logical port-channel by using the channel-group command.1Q tag.50 description R1 routed link to distribution layer encapsulation dot1Q 50 ip address 10. For complete distribution-layer configuration details.252 ip pim sparse-mode Step 3:  On the router. so you configure EtherChannel statically.Procedure 1 Connect router to distribution layer Reader Tip This guide includes only the additional steps to complete the distribution-layer configuration.0.255. interface GigabitEthernet0/1 description RS200-D3750X Gig1/0/1 ! interface GigabitEthernet0/2 description RS200-D3750X Gig2/0/1 ! interface range GigabitEthernet0/1.1 255. Layer 2 EtherChannels are used to interconnect the CE router to the distribution layer in the most resilient method possible. The subinterface number does not need to equate to the 802. interface Port-channel1.255. but making them the same simplifies the overall configuration. Step 1:  Configure a port-channel interface on the router.

Configure a VLAN interface. Configure two or more physical interfaces to be members of the EtherChannel. configure the VLAN.255. for the new VLAN added. also known as a switch virtual interface (SVI). The SVI is used for point-to-point IP routing between the distribution layer and the WAN router. vlan 50 name R1-link Step 5:  On the distribution-layer switch.Step 4:  On the distribution-layer switch.0. interface Vlan50 ip address 10. 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.2 255. 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. so you configure EtherChannel statically. connect the uplinks to separate redundant modules. Not all connected router platforms can support LACP to negotiate with the switch.5. It is recommended that they are added in multiples of two. Connect the router EtherChannel uplinks to separate switches in the distribution layer.255. apply the egress QoS macro that was defined in the platform configuration procedure to ensure traffic is prioritized appropriately. This provides additional resiliency. Also. configure Layer 3. configure EtherChannel member interfaces. If you are using a Cisco Catalyst 4507R+E chassis in the distribution layer. GigabitEthernet2/0/1 switchport macro apply EgressQoS channel-group 1 mode on logging event link-status logging event trunk-status logging event bundle-status Deploying a WAN Remote-Site Distribution Layer December 2013 77 .252 ip pim sparse-mode no shutdown Step 6:  On the distribution-layer switch.

router eigrp [as number] default-metric [WAN bandwidth (Kbps)] [WAN delay (usec)] 255 1 1500 redistribute bgp 65511 Deploying a WAN Remote-Site Distribution Layer December 2013 78 . only the WAN bandwidth and delay values are used for metric calculation.0.255 network 10. This design uses a best practice of assigning the router ID to a loopback address. all distribution-layer-facing subinterfaces and the loopback must be EIGRP interfaces. enable EIGRP-100 facing the distribution layer. The network range must include all interface IP addresses either in a single network statement or in multiple network statements. Procedure 2 Configure EIGRP (LAN side) You must configure a routing protocol between the router and distribution layer.5.0 0. In this design. Use an 802.255.255 passive-interface default no passive-interface [interface] eigrp router-id [IP address of Loopback0] no auto-summary Step 2:  On the router.0. router eigrp 100 network 10. All other interfaces should remain passive. configure an EtherChannel trunk. Step 1:  On the router. When using EtherChannel.0. This allows the router to provide the Layer 3 services to all the VLANs defined on the distribution-layer switch.Step 7:  On the distribution-layer switch. . interface Port-channel1 description EtherChannel link to RS200-3925-1 switchport trunk encapsulation dot1q switchport trunk allowed vlan 50 switchport mode trunk spanning-tree portfast trunk no shutdown Cisco Catalyst 4500 Series switches do not require the switchport trunk encapsulation dot1q command. A default metric redistributes the BGP routes into EIGRP. redistribute BGP into EIGRP-100.1Q trunk for the connection.0 0. and the number must match the channel group configured in Step 3. Prune the VLANs allowed on the trunk to only the VLANs that are active on the distribution-layer switch. the interface type is port-channel.255.0. By default.255.

252 ip pim sparse-mode Step 2:  On the router.0.0 0.0 0. so no SVI is required.255. Configure the transit network between the two routers. The VLAN interface that connects to the router must be configured as a non-passive EIGRP interface. EIGRP is already configured on the distribution-layer switch.5.200 no auto-summary Step 3:  On the distribution-layer switch VLAN interface.255.0. There are no end stations connected to this network. complete this procedure. enable EIGRP on the transit network interface.99 description Transit Net encapsulation dot1Q 99 ip address 10.255. The transit network must be a non-passive EIGRP interface.50 eigrp router-id 10.5. The transit network should use an additional subinterface on the EtherChannel interface that is already used to connect to the distribution layer. configure the transit network VLAN. interface Port-channel1.0.255 passive-interface default no passive-interface Port-channel1. The transit network uses Layer 2 pass-through on the distribution-layer switch.0. interface Port-channel1 switchport trunk allowed vlan add 99 Deploying a WAN Remote-Site Distribution Layer December 2013 79 .255. vlan 99 name Transit-net Step 4:  Add the transit network VLAN to the existing distribution-layer switch EtherChannel trunk.255. enable EIGRP. so HSRP and DHCP are not required.251.99 Step 3:  On the distribution-layer switch.255 network 10. Step 1:  On the router.0. router eigrp 100 no passive-interface Vlan50 Procedure 3 Configure the transit network If you are using a dual-router design.9 255.Example router eigrp 100 default-metric 100000 100 255 1 1500 network 10. You use this network for router-router communication and to avoid hairpinning. router eigrp 100 no passive-interface Port-channel1.255. configure the transit net interface.

In the dual-MPLS design. complete this procedure. remote sites advertise themselves as a transit autonomous system. which requires the update-source and next-hop-selfconfiguration options. 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.Procedure 4 Configure BGP If you are using a dual-router design. This requires the use of a route-map and an as-path access-list filter. 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. when a link to an MPLS hub has failed. Accomplishing the design goal of deterministic routing and primary/secondary routing behavior necessitates tuning BGP. Step 1:  Configure iBGP between the remote-site MPLS CE routers. Each router applies this outbound to the neighbor for its respective MPLS carrier. By default. The MPLS dual-carrier design in many cases provides two equal cost paths. and it is likely that the first path selected will remain the active path unless the routing protocol detects a failure. You need to apply this route-map on both remote-site MPLS CE routers. BGP readvertises all BGP learned routes. Note. router bgp 65511 neighbor [IP address of PE] route-map PREFER-MPLS-A in Deploying a WAN Remote-Site Distribution Layer December 2013 80 . You must use a route-map and an as-path access-list filter. This type of filter allows for only the locally originated routes to be advertised. You must complete this step on both remote-site MPLS CE routers. The dual-carrier MPLS design requires that a BGP link is configured between the CE routers. this means that MPLS-A routes are advertised to MPLS-B and vice-versa. Unless the remote site has been specifically designed for this type of routing behavior. with a high bandwidth connection. the iBGP session will not be established until you complete the transit network and EIGRP (LAN side) steps. this configuration is considered an internal BGP (iBGP) connection. it is a best practice to disable the site from becoming a transit site. providing access between the two carriers. Because the CE routers are using the same ASN. 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. This design uses iBGP peering using device loopback addresses. In certain cases. Step 3:  Tune BGP routing to prefer the primary MPLS carrier.

Deploying a WAN Remote-Site Distribution Layer December 2013 81 .255.Step 4:  Apply a route-map inbound to the neighbor for the primary MPLS carrier only. Step 5:  Add a loopback network for the secondary router. This allows BGP to selectively modify the routing information for routes originated from this AS. Connect router to distribution layer 2. In this example. This design uses a separate routed link from the second router of the dual-router scenario to the LAN distribution-layer switch. complete this process. dual-link design. This process connects the distribution layer to the second router of the dual-router. 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). PROCESS router bgp 65511 network [Secondary router loopback network] mask 255. Routes originated from the secondary MPLS carrier continue to use their default local preference of 100.255 Connecting the Secondary Remote-Site Router to the Distribution Layer 1. Configure EIGRP (LAN side) If you are using dual-carrier design for the MPLS WAN remote site. the BGP local preference is 200 for the primary MPLS carrier.255.

1Q tag. configure a port-channel interface. xx) R2 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.1Q Trunk (50. interface Port-channel2 description EtherChannel link to RS200-D3750X no shutdown Step 2:  Configure the port channel subinterfaces and assign IP address. map the appropriate subinterfaces to the VLANs on the distributionlayer switch.1Q Trunk (yy. Layer 2 EtherChannels are used to interconnect the CE router to the distribution layer in the most resilient method possible. Figure 18 .Router 1 Link VLAN 54 .Transit 802. Deploying a WAN Remote-Site Distribution Layer December 2013 82 . After you have enabled the interface.1Q Trunk (54. distribution layer-remote-site design is shown in the following figure. 99) 802. The subinterface number does not need to equate to the 802.WAN remote site—Connection to distribution layer WAN R1 VLAN 50 . This connection allows for multiple VLANs to be included on the EtherChannel if necessary.1Q Trunk (ww. but making them the same simplifies the overall configuration. zz) 2132 802. 99) 802. Step 1:  On the secondary router.The dual-router.Router 2 Link VLAN 99 . This guide only includes the additional steps to complete the distribution layer configuration.

Traffic is routed between the devices with the VLAN acting as a point-to-point link.5 255.0.5.255. Configure a VLAN interface. The number for the port-channel and channel-group must match. interface GigabitEthernet0/1 description RS200-D3750X Gig1/0/2 ! interface GigabitEthernet0/2 description RS200-D3750X Gig2/0/2 ! interface range GigabitEthernet0/1. so you configure EtherChannel statically.0. interface Port-channel2.255. configure the transit network interface. configure Layer 3. Deploying a WAN Remote-Site Distribution Layer December 2013 83 .255. also known as a switch virtual interface (SVI). Connect the router EtherChannel uplinks to separate switches in the distribution layer switches or stack. interface Port-channel2.252 ip pim sparse-mode Step 4:  On the router. The SVI is used for point-to-point IP routing between the distribution layer and the WAN router. configure a VLAN. and in the case of the Cisco Catalyst 4507R+E distribution layer.255.5.99 description Transit Net encapsulation dot1Q 99 ip address 10. GigabitEthernet0/2 no ip address channel-group 2 no shutdown Step 5:  On the distribution-layer switch.255.5. Configure the physical interfaces to tie to the logical port-channel using by the channel-group command. configure EtherChannel member interfaces.10 255.6 255.255.54 description R2 routed link to distribution layer encapsulation dot1Q 54 ip address 10.The subinterface configured on the router corresponds to a VLAN interface on the distribution-layer switch.252 ip pim sparse-mode no shutdown Step 7:  On the distribution-layer switch. vlan 54 name R2-link Step 6:  On the distribution-layer switch.252 ip pim sparse-mode Step 3:  On the router. to separate redundant modules for additional resiliency. Not all router platforms can support LACP to negotiate with the switch. configure the EtherChannel member interfaces.0. for the new VLAN added. interface Vlan54 ip address 10.

interface Port-channel2 description EtherChannel link to RS200-3925-2 switchport trunk encapsulation dot1q switchport trunk allowed vlan 54. Deploying a WAN Remote-Site Distribution Layer December 2013 84 . It is recommended that they are added in multiples of two. Use an 802. the interface type is port-channel. so you configure EtherChannel statically. Also. 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. GigabitEthernet2/0/2 switchport macro apply EgressQoS channel-group 2 mode on logging event link-status logging event trunk-status logging event bundle-status Step 8:  On the distribution-layer switch. apply the egress QoS macro that was defined in the platform configuration procedure to ensure traffic is prioritized appropriately. 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. Configure two or more physical interfaces to be members of the EtherChannel.99 switchport mode trunk spanning-tree portfast trunk no shutdown Cisco Catalyst 4500 Series switches do not require the switchport trunk encapsulation dot1q command. Not all connected router platforms can support LACP to negotiate with the switch.1Q trunk for the connection. This allows the router to provide the Layer 3 services to all the VLANs defined on the distribution-layer switch. Prune the VLANs allowed on the trunk to only the VLANs that are active on the distribution-layer switch. When using EtherChannel. configure an EtherChannel trunk. and the number must match the channel group configured in Step 4.The physical interfaces that are members of a Layer 2 EtherChannel are configured prior to configuring the logical port-channel interface.

0 0.255 network 10.5.255. A default metric redistributes the BGP routes into EIGRP.0. By default.0. enable EIGRP-100 facing the distribution layer. router eigrp 100 no passive-interface Vlan54 Deploying a WAN Remote-Site Distribution Layer December 2013 85 .54 no passive-interface Port-channel2. This design uses a best practice of assigning the router ID to a loopback address.0 0.255.252. router eigrp [as number] default-metric [WAN bandwidth (Kbps)] [WAN delay (usec)] 255 1 1500 redistribute bgp 65511 Example router eigrp 100 default-metric 500000 100 255 1 1500 network 10. The network range must include all interface IP addresses either in a single network statement or in multiple network statements.255. Step 1:  On the router.0. only the WAN bandwidth and delay values are used for metric calculation.255 passive-interface default no passive-interface [routed link interface] no passive-interface [transit net interface] eigrp router-id [IP address of Loopback0] no auto-summary Step 2:  On the router.0.255.255 network 10. EIGRP is already configured on the distribution-layer switch.Procedure 2 Configure EIGRP (LAN side) You must configure a routing protocol between the router and distribution layer.255 passive-interface default no passive-interface Port-channel2.0.0. enable EIGRP.5.255.200 no auto-summary Step 3:  On the distribution-layer switch VLAN interface.99 eigrp router-id 10.0 0. router eigrp 100 network 10.255. All other interfaces should remain passive. The VLAN interface that connects to the router must be configured as a non-passive EIGRP interface. all distribution-layer-facing subinterfaces and the loopback must be EIGRP interfaces. In this design.0 0. redistribute BGP into EIGRP-100.0.0.255.

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

and Oracle thin clients) af31. BGP traffic is not explicitly tagged with a DSCP value. operations. cs1 5 — NETWORK-CRITICAL Routing protocols.Table 13 . af41 23 (PQ) — CRITICAL-DATA Highly interactive (such as Telnet. 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 December 2013 87 . Use NBAR to match BGP by protocol. 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.QoS classes of service Class of service Traffic type DSCP values Bandwidth % Congestion avoidance VOICE Voice traffic ef 10 (PQ) — INTERACTIVE-VIDEO Interactive video (such as video conferencing) cs4. cs3 15 DSCP-based DATA Data af21 19 DSCP-based SCAVENGER Scavenger af11. administration and maintenance (OAM) traffic. create a class map for BGP protocol matching. Citrix. cs6.

bandwidth percent [percentage] Step 4:  (Optional) Define the priority queue for the class. policy-map [policy-map-name] Step 2:  Apply the previously created class map. complete this procedure. Step 1:  Create a policy map. each class within the policy map invokes an egress queue. 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. you must assign a DSCP value of cs6. 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. priority percent [percentage] Deploying WAN Quality of Service December 2013 88 . The local router policy maps define seven classes while most service providers offer only six classes of service. This is implicitly included within classdefault as shown in Procedure 4. and associates a specific traffic class to that queue. assigns a percentage of bandwidth. Then. This specification is accomplished with the use of a policy map. 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. the network-critical traffic is typically remapped by the service provider into the critical data class. marking. After the traffic has been transmitted to the service provider. Step 1:  Create the parent policy map. you must configure a policy map to assign the required DSCP value to all BGP traffic. and queuing of network-critical traffic on egress to the WAN. Most providers perform this remapping by matching on DSCP values cs6 and cs2. One additional default class defines the minimum allowed bandwidth available for best-effort traffic. To ensure proper treatment of BGP routing traffic in the WAN. class [class-name] Step 3:  (Optional) Assign the maximum guaranteed bandwidth for the class. and then assign it a DSCP value of cs6.Tech Tip You do not need to configure a best-effort class. Although the class map you created in the previous step matches all BGP traffic to the class named BGP. The NETWORK-CRITICAL policy map is defined in order to ensure the correct classification.

random-detect Procedure 4 Configure shaping and queuing policy With WAN interfaces using Ethernet as an access technology. You configure a QoS service policy on the outside Ethernet interface. it is important to consider your actual traffic requirements per class and adjust the bandwidth settings accordingly. a specified amount of access bandwidth is contracted with the service provider. ensure that the value matches the contracted bandwidth rate from your service provider. Instead. service-policy [policy-map-name] Step 6:  (Optional) Define the congestion mechanism.Step 5:  (Optional) Apply the 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 Tech Tip Although these bandwidth assignments represent a good baseline. This is an optional step only for the NETWORK-CRITICAL class of service with the MARK-BGP child service policy. including class-default. When you configure the shape average command. This shaping is accomplished with a QoS service policy. This is called a hierarchical Class-Based Weighted Fair Queuing (HCBWFQ) configuration. Deploying WAN Quality of Service December 2013 89 . 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. random-detect [type] Step 7:  Repeat Step 2 through Step 6 for each class in Table 13. the demarcation point between the enterprise and service provider may no longer have a physical-interface bandwidth constraint. To ensure the offered load to the service provider does not exceed the contracted rate that results in the carrier discarding traffic.

policy-map [policy-map-name] Step 2:  Configure the shaper. 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 Procedure 5 Apply the shaping and queuing policy to a physical interface To invoke shaping and queuing on a physical 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 December 2013 90 . embed the interface name within the name of the parent policy map. Step 1:  Create the parent policy map. As a best practice. you must apply the parent policy that you configured in the previous procedure. 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. class [class-name] shape [average | peak] [bandwidth (bps)] Step 3:  Apply the child service policy. interface [interface type] [number] Step 2:  Apply the WAN QoS policy in the outbound direction. You can repeat this procedure multiple times to support devices that have multiple WAN connections attached to different interfaces. You can repeat this procedure multiple times to support devices that have multiple WAN connections attached to different interfaces. This procedure applies to all WAN routers. Step 1:  Select the WAN interface.This procedure applies to all WAN routers.

Bundle. PVDM3-32.2(4)M4 securityk9 license datak9 license Data Paper PAK for Cisco 3900 series SL-39-DATA-K9 Cisco 2951 Voice Sec.3(3)S securityk9 license Cisco 3945 Voice Sec. PVDM3-32. Bundle. UC and SEC License PAK C3925-VSEC/K9 15. PVDM3-64.11n FCC Compliant C881SRST-K9 15. UC and SEC License PAK C2911-VSEC/K9 Data Paper PAK for Cisco 2900 series SL-29-DATA-K9 1941 WAAS Express only Bundle C1941-WAASX-SEC/K9 Data Paper PAK for Cisco 1900 series SL-19-DATA-K9 Cisco 881 SRST Ethernet Security Router with FXS FXO 802.2(4)M4 securityk9 license datak9 license December 2013 91 .5G-VPNK9 IOS-XE 15. Bundle.Appendix A: Product List WAN Remote Site Functional Area Product Description Part Numbers Software Modular WAN Remote-site Router Cisco ISR 4451-X Security Bundle w/SEC license PAK ISR4451-X-SEC/K9 15. PVDM3-32.2(4)M4 securityk9 license datak9 license 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. UC and SEC License PAK C3945-VSEC/K9 Cisco 3925 Voice Sec. UC and SEC License PAK C2921-VSEC/K9 Cisco 2911 Voice Sec.3(3)S Advanced Enterprise license Cisco 3945 Security Bundle w/SEC license PAK CISCO3945-SEC/K9 Cisco 3925 Security Bundle w/SEC license PAK CISCO3925-SEC/K9 Data Paper PAK for Cisco 3900 series SL-39-DATA-K9 Fixed WAN Remote-site Router WAN Aggregation WAN-aggregation Router Appendix A: Product List 15. UC and SEC License PAK C2951-VSEC/K9 Cisco 2921 Voice Sec. PVDM3-64. Bundle. Bundle.

4.0-1EX1) IP Base license 15.0(2)SE2 IP Base license 15.0(2)SE2 IP Base license 15.2.1SE(15.LAN Access Layer Functional Area Product Description Part Numbers Software Modular Access Layer Switch Cisco Catalyst 4507R+E 7-slot Chassis with 48Gbps per slot WS-C4507R+E 3.0.1-2SG) IP Base license Cisco Catalyst 4500 E-Series Supervisor Engine 7L-E WS-X45-SUP7L-E Cisco Catalyst 4500 E-Series 48 Ethernet 10/100/1000 (RJ45) PoE+ ports WS-X4648-RJ45V+E Cisco Catalyst 4500 E-Series 48 Ethernet 10/100/1000 (RJ45) PoE+.0(2)SE2 LAN Base license December 2013 92 .UPoE ports WS-X4748-UPOE+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 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 3560-X Series Standalone 48 Ethernet 10/100/1000 PoE+ ports WS-C3560X-48PF-S Cisco Catalyst 3560-X Series Standalone 24 Ethernet 10/100/1000 PoE+ ports WS-C3560X-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-S Series 48 Ethernet 10/100/1000 PoE+ ports and Two 10GbE SFP+ Uplink ports WS-C2960S-48FPD-L Cisco Catalyst 2960-S Series 48 Ethernet 10/100/1000 PoE+ ports and Four GbE SFP Uplink ports WS-C2960S-48FPS-L Cisco Catalyst 2960-S Series 24 Ethernet 10/100/1000 PoE+ ports and Two 10GbE SFP+ Uplink ports WS-C2960S-24PD-L Cisco Catalyst 2960-S Series 24 Ethernet 10/100/1000 PoE+ ports and Four GbE SFP Uplink ports WS-C2960S-24PS-L Cisco Catalyst 2960-S Series Flexstack Stack Module C2960S-STACK Stackable Access Layer Switch Standalone Access Layer Switch Stackable Access Layer Switch Appendix A: Product List 3.SG(15.

0(2)SE2 IP Services license December 2013 93 .4.SG(15. 848Gbps WS-X45-SUP7-E Cisco Catalyst 4500 E-Series 24-port GbE SFP Fiber Module WS-X4624-SFP-E Cisco Catalyst 4500 E-Series 12-port 10GbE SFP+ Fiber Module WS-X4712-SFP+E 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 Modular Distribution Layer Switch Stackable Distribution Layer Switch Appendix A: Product List 3.1-2SG) Enterprise Services license 15.1(1)SY IP services license 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 24-port GbE SFP Fiber Module w/DFC4 WS-X6824-SFP-2T Cisco Catalyst 4507R+E 7-slot Chassis with 48Gbps per slot WS-C4507R+E Cisco Catalyst 4500 E-Series Supervisor Engine 7-E.LAN Distribution Layer Functional Area Product Description Part Numbers Software Modular Distribution Layer Virtual Switch Pair Cisco Catalyst 6500 E-Series 6-Slot Chassis WS-C6506-E Cisco Catalyst 6500 VSS Supervisor 2T with 2 ports 10GbE and PFC4 VS-S2T-10G 15.0.

please go to the following URL: http://cvddocs.Appendix B: Device Configuration Files To view the configuration files from the CVD lab devices that we used to test this guide.com/fw/240-13 Appendix B: Device Configuration Files December 2013 94 .

• Added a WAN-facing summary route for the remote-site network range. The summary route ensures that default routing changes do not affect remote-site communication between WAN transports.Appendix C: Changes This appendix summarizes the changes to this guide since its last edition. • Added support for Cisco 4451-X Integrated Services Router platform. Appendix C: Changes December 2013 95 .

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