Cisco ASR1002 - ASR 1002 Router User manual

Cisco Network Positioning System Configuration Guide for the
Cisco ASR 1000 Router, Release 1.0
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: [phone]
800 553-NETS (6387)
Fax: [phone]
Text Part Number: OL-25794-01

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,
INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH
THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,
CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version
of the UNIX operating system. All rights reserved. Copyright ©1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS.
CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT
LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://
www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown
for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
©2011 Cisco Systems, Inc. All rights reserved.

CONTENTS
Preface Preface v
Changes to This Document v
Obtaining Documentation and Submitting a Service Request v
CHAPTER 1 General Configuration of the Network Positioning System 1
Configuring Basic Networking on a PE 1
CHAPTER 2 Configuring the XMPP Server 3
Configuring the XMPP Server 3
CHAPTER 3 Configuring Service Placement 5
Information About the Service Resolution Engine 5
Service Resolution Engine Ranking Requirements 6
Service Resolution Engine Configuration 6
Service Resolution Configuration Examples 7
show service-resolution dc command: example 7
show service-resolution service-requests command: example 8
CHAPTER 4 Configuring the Capability Directory 9
Configuring the Capability Directory 9
CHAPTER 5 Configuring Performance Metrics to Select a Service 11
Prerequisites for the Performance Manager 11
Performance Manager Limitations 11
Information About the Performance Manager 11
Extensible Messaging and Presence Protocol Client Registration 12
Performance Manager Message Processing 13
Cisco Network Positioning System Configuration Guide for the Cisco ASR 1000 Router, Release 1.0
OL-25794-01 iii

How to Configure the Performance Manager 14
Configuring the Performance Manager on a DC-Facing PE 14
Configuring the Performance Manager on a CE-Facing PE 15
CHAPTER 6 Configuring the Routing Protocols Used for Network Proximity 19
Information About Network Routing Proximity 19
PXE Data Elements 20
PXE Peering and Ranking 20
How to Configure Routing Protocols 21
Configuring OSPF for Proximity Calculations 21
Configuring BGP for Proximity Calculations 22
Configuring IS-IS for Proximity Calculations 24
CHAPTER 7 NPS Configuration Examples 27
CE-Facing PE Configuration Example 27
DCE-Facing PE Configuration: Example 28
Cisco Network Positioning System Configuration Guide for the Cisco ASR 1000 Router, Release 1.0
iv OL-25794-01
Contents

Preface
This book presents configuration information and examples for the Network Positioning System for the
Cisco ASR 1000 Router. The preface consists of these sections:
•Changes to This Document, page v
•Obtaining Documentation and Submitting a Service Request, page v
Changes to This Document
This table lists the technical changes made to this document since it was first printed.
Table 1: Changes to This Document
Change SummaryDateRevision
Initial release of this document.November 2011OL-25794-01
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information,
see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco
technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed
and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free
service and Cisco currently supports RSS version 2.0.
Cisco Network Positioning System Configuration Guide for the Cisco ASR 1000 Router, Release 1.0
OL-25794-01 v

Cisco Network Positioning System Configuration Guide for the Cisco ASR 1000 Router, Release 1.0
vi OL-25794-01
Preface
Obtaining Documentation and Submitting a Service Request

CHAPTER 1
GeneralConfigurationoftheNetworkPositioning
System
Configuration of the Network Positioning System (NPS) involves these tasks:
1Configure your router so that it can communicate with the NPS. This includes assigning a hostname to
the router.
2Configure the Extensible Messaging and Presence Protocol (XMPP) server on one data center (DC)-facing
provider edge router (PE).
3Configure the Service Resolution Engine (SRE) on one DC-facing PE.
4Configure the Capability Directory (CD) on the same DC-facing PE on which the SRE is configured.
5Configure the Performance Manager (PFM) running on your router. This configuration changes depending
on whether you are configuring a DC-facing or customer edge router (CE)-facing PE.
6Configure the routing protocols on your router so that the Proximity Engine (PXE) can use these for
proximity calculations.
This module covers the basic configuration required so that your router can communicate with the NPS.
Refer to the remaining modules in this book for information on other configuration tasks.
•Configuring Basic Networking on a PE, page 1
Configuring Basic Networking on a PE
To enable the XMPP server to access each CE-facing and DC-facing PE in the system, you must perform this
configuration:
Cisco Network Positioning System Configuration Guide for the Cisco ASR 1000 Router, Release 1.0
OL-25794-01 1

SUMMARY STEPS
1. hostname hostname
2. ip host hostname ip-address
3. ip name-server ip-address
4. interface interface-name
5. ip address ip-address mask
6. no shutdown
DETAILED STEPS
PurposeCommand or Action
Configures a hostname for the router.
hostname hostname
Example:
server(config)# hostname ccnsr.com
Step 1
Specifies the IP address of the running XMPP server.
ip host hostname ip-address
Example:
server(config)# ip host ccnsr.com 172.16.0.2
Step 2
Specifies the address of the name server. This
command is required only if the ip host command is
not used.
ip name-server ip-address
Example:
server(config)# ip name-server
Step 3
Enters interface configuration mode to enable an
interface.
interface interface-name
Example:
server(config)# interface eth0
server(config-if)#
Step 4
Configures the IP address of the interface.
ip address ip-address mask
Example:
server(config-if)# ip address 172.17.0.3
255.255.255.0
Step 5
Enables the interface.no shutdown
Example:
server(config-if)# no shutdown
Step 6
What to Do Next
Configure the XMPP server.
Cisco Network Positioning System Configuration Guide for the Cisco ASR 1000 Router, Release 1.0
2OL-25794-01
General Configuration of the Network Positioning System
Configuring Basic Networking on a PE

CHAPTER 2
Configuring the XMPP Server
The Extensible Messaging and Presence Protocol (XMPP) is an open, XML-based standard for near real-time
communication. Because XMPP provides near real-time communication among different platforms for
information distribution, it is the primary communications and transport protocol used between NPS
components.
Jabber is the implementation of XMPP that is installed with the NPS software. The configuration of Jabber
is described in this module.
•Configuring the XMPP Server, page 3
Configuring the XMPP Server
Jabber is used to facilitate communication between PE routers for the purposes of service resolution. Use this
task to configure the Jabber server on one of the PE routers in your system. It is also used by the capability
directory (CD) to get device capabilities through the XMPP pubsub protocol. Generally, the Jabber server is
installed on the DCE-facing PE where the service resolution engine (SRE) is installed.
SUMMARY STEPS
1. jabber server
2. domain domain-name
3. ipaddr ipv4 ip-address
4. log-level level
DETAILED STEPS
PurposeCommand or Action
Enters Jabber configuration mode to configure the XMPP
server on the router.
jabber server
Example:
switch(config)# jabber server
Step 1
Cisco Network Positioning System Configuration Guide for the Cisco ASR 1000 Router, Release 1.0
OL-25794-01 3

PurposeCommand or Action
Specifies the domain name of the Jabber server.
domain domain-name
Example:
switch(config-jabber)# domain ccnsr.com
Step 2
Specifies the IP address to use for the Jabber server.
ipaddr ipv4 ip-address
Example:
switch(config-jabber)# ipaddr ipv4 172.16.0.2
Step 3
Specifies the notifications to display. Possible options are:
log-level level
Step 4
Example:
switch(config-jabber)# log-level info
•debug
•error
•info
•verbose
•warn
What to Do Next
Configure the SRE.
Cisco Network Positioning System Configuration Guide for the Cisco ASR 1000 Router, Release 1.0
4OL-25794-01
Configuring the XMPP Server
Configuring the XMPP Server

CHAPTER 3
Configuring Service Placement
In Cisco NPS, the Service Resolution Engine (SRE) performs service placement recommendations. In other
words, this is the selection of a data center from a number of data centers that support a requested service.
The SRE receives a service request that contains the parameters for the desired service; for example, the
activation of the devices in a virtual data center (vDC). The SRE returns a list of the physical data centers
that can fulfill the request, ordered according to parameters defined in the service resolution policy.
•Information About the Service Resolution Engine, page 5
•Service Resolution Engine Configuration, page 6
Information About the Service Resolution Engine
The main functionality of the SRE is to recommend where a service should be placed within the network. The
SRE takes in a service request containing the required service parameters, which might include:
• Desired Virtual Data Center (vDC) resources in terms of computing power
• Storage capacity
• Network services such as firewall and load balancer
• Logical topology of the service
• Policy handle
The SRE then returns a list of data centers (DCs) capable of fulfilling these requirements, ordered according
to the relevant policies and ordering preferences provided by the user. For example, a recommended order of
data centers might be listed according to the network proximity between the service origination point and the
physical data centers; or, it could be done according to performance metrics between the service origination
point and the physical data centers.
SRE interfaces with the external policy server to fetch the relevant policies, and also interacts with internal
components such as the NGN Capability Directory (NCD),Performance Manager (PFM), and Proximity
Engine (PXE) to retrieve the data needed to perform the service recommendation.
Cisco Network Positioning System Configuration Guide for the Cisco ASR 1000 Router, Release 1.0
OL-25794-01 5

Service Resolution Engine Ranking Requirements
If a service request asks for proximity ranking, the SRE supports the ranking of data centers according to the
network proximity between the service-origination point and the data centers.
Ranking Proximity
In Cisco NPS, proximity ranking is based on the network distance between customer edge devices facing
provider edge devices and data center devices facing provider edge devices.
Ranking Performance
If a service request asks for performance ranking, the SRE supports the ranking of data centers according to
performance.
In Cisco NPS, performance ranking is based on the performance attribute values measured between customer
edge devices facing provider edge devices and data center devices facing provider edge devices. A user can
assign different ranking priorities to different performance attributes. SRE supports these attributes:
• Traffic delay
• Traffic loss
A user can select a combination of different performance attributes and assign different ranking priorities to
them.
Service Resolution Engine Configuration
Perform this configuration on a provider edge router (PE) to enable the service resolution engine (SRE). Cisco
recommends running the SRE on a DCE-facing PE in your network.
SUMMARY STEPS
1. service-resolution web-service address ip-address [port port]
2. service-resolution web-service username username password password
3. service-resolution dc id pe-address address
4. service-resolution exclude dc id
5. service-resolution service-request timeout timeout-interval
DETAILED STEPS
PurposeCommand or Action
Configures the hostname or IP address and port for the service
resolution API web service. The address can be configured explicitly.
service-resolution web-service address ip-address
[port port]
Step 1
Example:
switch(config)# service-resolution
web-service address 10.0.0.1 port 10000
•ip-address—IP address that the external world uses to reach the
service resolution API.
Cisco Network Positioning System Configuration Guide for the Cisco ASR 1000 Router, Release 1.0
6OL-25794-01
Configuring Service Placement
Service Resolution Engine Ranking Requirements

PurposeCommand or Action
•port—Port within the web server address that the external world
uses to reach the API.
Configures the username and password for the service resolution API
user authentication. Only one username and password pair can be
service-resolution web-service username username
password password
Step 2
configured. If you do not configure a username and password, user
authentication is disabled.
Example:
SR(config)# service-resolution web-service
username foo password 1234
•username—Service resolution API username to be added.
•password—Password associated with this username.
Configures data center (DC)/PE pairs. Data centers entered in this
command are used for the DC candidate list as well as being associated
with a PE connected to the DC.
service-resolution dc id pe-address address
Example:
SR(config)# service-resolution dc att-west
Step 3
•id—Unique data center identifier.
pe-address 5.5.5.5 •address—IP address of the PE used to access the DC. This
address is used as an end-point in the various types of rankings
(performance, proximity, etc.).
SR(config)# service-resolution dc DC1
pe-address 2.2.2.2
SR(config)# service-resolution dc DC1
pe-address 3.3.3.3
SR(config)# service-resolution dc DC2
pe-address 4.4.4.4
SR(config)# service-resolution dc DC2
pe-address 1.1.1.1
Adds data centers to a global exclusion list, in other words a list of
data centers to be excluded from the service placement
service-resolution exclude dc id
Example:
switch(config)# service-resolution exclude
dc att_west
Step 4
recommendation operation. A common use for exclusion is when
data centers are down for maintenance.
•id—Identifier of the data center to be excluded.
Specifies the service request timeout interval in seconds. Values can
range from 1 to 3600. The default is 30 seconds.
service-resolution service-request timeout
timeout-interval
Example:
switch(config)# service-resolution
service-request timeout 90
Step 5
Service Resolution Configuration Examples
show service-resolution dc command: example
SR-1# show service-resolution dc
Cisco Network Positioning System Configuration Guide for the Cisco ASR 1000 Router, Release 1.0
OL-25794-01 7
Configuring Service Placement
Service Resolution Configuration Examples

--------------------------------------------------------------------
DC
PE-name PE-address
--------------------------------------------------------------------
DC1
PE1 1.1.1.1
PE2 2.2.2.2
PE3 3.3.3.3
DC2
PE4 4.4.4.4
PE1 1.1.1.1
my-data-center-14
my-pe-22 22.22.22.22
my-pe-28 111.111.111.111
show service-resolution service-requests command: example
SR-1# show service-resolution service-requests
Service-Request:
ID: 00000001
vdc_id: 22222
user_handle: my_handle_1
URI: https://sr.foobar.net/sr/serv_req_00000001
state: DONE
Message: Service-request '000000001' processing successfully completed.
Detail: n/a
CE-address: 10.10.10.1
PE-address: 10.10.10.2
Ranked DC list:
DC: amazon_west
PE-address: 30.30.30.2
PE-address: 20.20.20.1
DC: att_west
PE-address: 50.50.50.1
PE-address: 60.60.60.1
PE-address: 40.40.40.1
Service-Request:
ID: 00000050
vdc_id: 12345
user_handle: h2
URI: https://sr.foobar.net/sr/serv_req_00000050
state: PENDING
Message: Waiting for ranking processing to complete
Detail: n/a
Service-Request:
ID: 00001000
vdc_id: 7890
user_handle: handle3
URI: https://sr.foobar.net/sr/serv_req_00001000
state: ERROR
Message: Performance Manager Error
Detail: n/a
Cisco Network Positioning System Configuration Guide for the Cisco ASR 1000 Router, Release 1.0
8OL-25794-01
Configuring Service Placement
show service-resolution service-requests command: example

CHAPTER 4
Configuring the Capability Directory
The Capability Directory (CD) is responsible to keep track of the services available in each data center and
to provide the SRE with a list of available data centers with sufficient capabilities to meet the requirements
of each request..
•Configuring the Capability Directory, page 9
Configuring the Capability Directory
Configure the capability directory (CD) on the DC-facing PE on which the SRE is installed.
SUMMARY STEPS
1. cd xmpp username user password pass
2. xmpp server type cd host hostname
DETAILED STEPS
PurposeCommand or Action
Configures a username and password for the CD.
cd xmpp username user password pass
Example:
switch(config)# cd xmpp username user-xyz password pass
Step 1
Specifies to the CD process how to connect to the
XMPP server.
xmpp server type cd host hostname
Example:
switch(config)# xmpp server type cd host ccnsr.com
Step 2
What to Do Next
Configure the PFM.
Cisco Network Positioning System Configuration Guide for the Cisco ASR 1000 Router, Release 1.0
OL-25794-01 9

Cisco Network Positioning System Configuration Guide for the Cisco ASR 1000 Router, Release 1.0
10 OL-25794-01
Configuring the Capability Directory
Configuring the Capability Directory

CHAPTER 5
Configuring Performance Metrics to Select a
Service
The performance manager (PFM) is a platform-independent sub-component that provides performance data
(delay, jitter and reachability) between the service origination point and each candidate DC.
•Prerequisites for the Performance Manager, page 11
•Performance Manager Limitations, page 11
•Information About the Performance Manager, page 11
•How to Configure the Performance Manager, page 14
Prerequisites for the Performance Manager
To ensure that the PFM can be implemented and operate correctly, these conditions must exist:
• The Extensible Messaging and Presence Protocol (XMPP) is supported on the PE device.
•Performance Routing (PfR) information can be accessed by a Web Service Management Agent (WSMA).
Performance Manager Limitations
The performance manager (PFM) should be set up with prefix maps and active probes in an NPS deployment.
Note that such active probes are limited to jitter and echo. With regard to echo probes, the PFM does not
receive loss statistics. With regard to jitter probes, the DCE-PEs should be set up as IP SLA responders.
Information About the Performance Manager
The Performance Subsystem (PFS) is a component of the Network Positioning System (NPS) that evaluates
performance data and presents a ranking of data centers to the service resolution engine (SRE). The PFS
evaluates performance data such as:
• Delay—end-to-end packet delay over a period of time
Cisco Network Positioning System Configuration Guide for the Cisco ASR 1000 Router, Release 1.0
OL-25794-01 11

• Loss—statistics on packet loss to a destination
• Reachability—statistics on packets sent to an unreachable destination
The PFS uses Performance Routing (PfR) to obtain this data. The PFS parses requests that it receives from
the SRE and derives data from PfR to satisfy the requests.
Figure 1: Performance Subsystem
The PFS contains two main components:
•Performance Manager (PFM)—Platform independent sub-component that provides performance data
(delay, jitter, and reachability) between the service origination point and each candidate data center. The
PFM runs on both CE-facing and DCE-facing PE routers.
•Performance Adapter (PFA)—Platform dependent adapter that retrieves performance data for the PFM
from the Performance Data Provider (PDP), which is a platform-dependent service located outside the
performance subsystem. The PFA and PDP only run on CE-facing PE routers.
Extensible Messaging and Presence Protocol Client Registration
PFM peers that are located on different PE devices communicate with each other using the Extensible Messaging
and Presence Protocol (XMPP). XMPP uses the request-response mechanism. Therefore, each peer must be
recognizable to the XMPP server (in other words, have a Jabber ID [JID]) before a connection can be
established.
The information in peer notifications includes:
Cisco Network Positioning System Configuration Guide for the Cisco ASR 1000 Router, Release 1.0
12 OL-25794-01
Configuring Performance Metrics to Select a Service
Extensible Messaging and Presence Protocol Client Registration

• Hostname—Hostname or IP address of the PE device.
• PFMID—ID of the PFM entity.
• PE Type—Either a CE or DCE device. If the device is configured with a local CE table, it should be a
CE device facing a PE device.
• Jabber ID—ID of the XMPP client.
Performance Manager Message Processing
The SRE starts a Cisco NPS message flow. The message flow is processed sequentially by the performance
subsystem (PFM and PFA) and PDP.
Figure 2: PFM Message Flow
Cisco Network Positioning System Configuration Guide for the Cisco ASR 1000 Router, Release 1.0
OL-25794-01 13
Configuring Performance Metrics to Select a Service
Performance Manager Message Processing

A PFM process gets and caches performance data from a PFA every 10 seconds. Every PFM entity shares
the cached tables as the latest data source.
How to Configure the Performance Manager
Configuring the Performance Manager on a DC-Facing PE
The performance subsystem (PFS) on a DC-facing PE runs the PFM only. It sends all received requests to a
CE-facing PE for processing. The PFM on a DC-facing PE is responsible to:
• Receive requests from the SRE.
•Locate the corresponding CE-facing PE, from which it receives performance data through the Extensible
Messaging and Presence Protocol (XMPP).
• Send the final performance data to the SRE.
Configure the PFM on all DC-facing PEs.
SUMMARY STEPS
1. xmpp server type pfm hostname
2. pfm local-host ip-address
3. pfm dce-facing
DETAILED STEPS
PurposeCommand or Action
Specifies the name of the XMPP server for PFM.
xmpp server type pfm hostname
Example:
xmpp server type pfm ccnsr.com
Step 1
Arbitrarily specifies the IP address to get to one of the DCs;
this value is used to generate a jabber ID for XMPP
communication.
pfm local-host ip-address
Example:
(config)# pfm local-host 10.4.1.1
Step 2
Enables the performance manager running in a DCE-facing
PE.
pfm dce-facing
Example:
(config)# pfm dce-facing
Step 3
What to Do Next
Configure all CE-facing PEs.
Cisco Network Positioning System Configuration Guide for the Cisco ASR 1000 Router, Release 1.0
14 OL-25794-01
Configuring Performance Metrics to Select a Service
How to Configure the Performance Manager