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
To Next Page
Loading...
Need help?
General
